WO2019154223A1 - Communication processing method for non-scheduled resource, and related device - Google Patents

Abstract

Provided is a communication processing method for a non-scheduled resource. A terminal side device feeds time-domain information of the uplink data back to the access network side device, so that the access network side device is able to learn whether the allocated non-scheduled resource is suitable, so as to optimize resource allocation.

Description

Communication processing method and related device for non-scheduled resources

The present application claims the priority of the priority of the priority application Serial No. 2011.

Technical field

The embodiments of the present application relate to the field of wireless communications, and in particular, to a communication processing technology for non-scheduled resources.

Background technique

The wireless communication system includes a terminal side device and an access network side device that serves the terminal side device. According to the protocol layer, they include a physical (PHY) layer, a medium access control (MAC) layer, a radio link control (RLC) layer, and a packet data convergence protocol. , PDCP) and radio resource control (RRC) layer and so on.

After the terminal side device establishes the establishment with the access network side device, the access network side device may configure the non-scheduling function in advance by using the RRC message of the RRC layer for the terminal side device. A period is set in the non-scheduled function, wherein the non-scheduled function includes a semi-persistent scheduling (SPS) function or a grant free function. In a transmission time interval (TTI), the access network side device indicates activation and use of the non-scheduled function in a physical downlink control channel (PDCCH) of the physical layer. Non-scheduled resources. Since the non-scheduled resource has the characteristics of “one time allocation, multiple use”, the terminal side device and the access network side use the non-scheduled resource to transmit data on each cycle. Therefore, "non-scheduled" may also be referred to as "pre-scheduled", "disabled" or "semi-statically scheduled". After the data transmission is completed, the non-scheduled resources may be re-allocated or released.

Summary of the invention

The embodiment of the present application provides a communication processing method for a non-scheduled resource, which enables the access network side device to know whether the allocated non-scheduled resource is suitable, so as to optimize resource allocation.

A first aspect of the embodiments of the present application provides a communication processing method for a non-scheduled resource performed by a terminal side device. The terminal device may be an independent terminal itself, or may be a circuit system that implements the communication processing method of the non-scheduled resource in at least one chip or terminal in the terminal.

In the communication processing method of the non-scheduled resource provided by the first aspect, the terminal side device receives, by the access network side device, first configuration information, which is used to indicate an uplink non-scheduled resource for uplink data transmission, and the uplink data. The time domain information is notified to the access network side device.

The time domain information of the uplink data includes at least one of the following:

The time interval between the arrival time of the uplink data and the successful transmission of the uplink data, the time domain location adjacent to the arrival time of the uplink data in the uplink non-scheduled resource, and the uplink non-scheduled resource The interval between the time domain location adjacent to the arrival time of the uplink data and the arrival time of the uplink data, the arrival time of the uplink data, where the uplink data is sent for the first time in the non-scheduled resource The interval between the time domain location and the time domain location where the uplink data was last successfully transmitted; the waiting time when the uplink data is transmitted.

Optionally, the time domain information of the uplink data is carried in an RRC message, a PHY message or a MAC message sent by the terminal side device to the access network side device.

Optionally, in the communication processing method of the non-scheduled resource, the terminal side device may receive a PDCCH for indicating whether the non-scheduling function is activated. When the non-scheduling function is activated, the PDCCH carries the first configuration information.

Applying the technical solution provided by the first aspect, the time domain information of the uplink data is fed back to the access network side device by the terminal side device, so that the access network side device can learn the allocated non-scheduling resource. Is it appropriate to optimize resource allocation?

In a first possible implementation manner of the first aspect, the method further includes: the terminal side device receiving the adjustment information sent by the access network side device, so that the uplink non-scheduled resource The uplink data is sent to the access network side device in the adjusted time domain location or frequency domain location.

Optionally, the adjustment information may be carried in an RRC message, a PHY message or a MAC message sent by the access network side device to the terminal side device.

In a first possible implementation manner of the first aspect, the access network side device may adjust the uplink non-scheduled resource in response to the time domain information of the uplink data that is fed back by the terminal device. As soon as the uplink non-scheduled resources come, the data transmission efficiency is improved.

Based on the first aspect or the first possible implementation manner of the first aspect, in a second possible implementation manner of the first aspect, the method further includes: the terminal side device notifying the access network side device Before the time domain information of the uplink data, the terminal side device receives the request information sent by the network device, where the request information is used to request time domain information of the uplink data.

The technical solution provided by the second possible implementation of the first aspect is that the terminal side device triggers the sending of the time domain information of the uplink data based on the request of the access network side device.

In a third possible implementation manner of the first aspect, the method further includes: notifying the access network side device Before the time domain information of the uplink data, the second configuration information sent by the access network side device is received, and the second configuration information indicates that the time domain information of the uplink data is notified to the access network side device. The condition, wherein the condition includes: notifying a period of the time domain information or a threshold exceeding the time domain information when the time domain information is notified.

The technical solution provided by the third possible implementation of the first aspect clarifies that the terminal side device notifies the triggering condition of the time domain information.

In a fourth possible implementation manner of the first aspect, the method further includes: the terminal side device receiving the access network The third configuration information sent by the side device, the third configuration information indicating to notify the access network side device of at least one of a period and a time-frequency resource used by the time domain information of the uplink data.

The technical solution provided by the fourth possible implementation of the first aspect is that the terminal side device can feed back the uplink based on the periodic or time-frequency resources configured by the access network side device by using the third configuration information. Time domain information for the data. In a possible implementation, the third configuration information may be carried in the request sent by the access network side device in the second possible implementation manner of the first aspect.

In a fifth possible implementation manner of the first aspect, the method further includes:

Sending, to the access network side device, request information for requesting notification of time domain information of the uplink data, and receiving response information sent by the access network side device to the request information.

Optionally, an interval between an arrival time of the uplink data and a successfully sent uplink data, a time domain location adjacent to an arrival time of the uplink data in the uplink non-scheduled resource, and the uplink data. The interval between the arrival times of the non-scheduled resources, when the interval between the time domain location in which the uplink data is first sent and the time domain location in which the uplink data is successfully transmitted in the non-scheduled resource exceeds a certain threshold, The terminal side device sends the request information. Optionally, the threshold may be configured by the access network side device to the terminal side device.

The technical solution provided by the fifth possible implementation of the first aspect is to implement the sending of the time domain information of the uplink data based on the request of the terminal side device and the response of the access network side device.

In a sixth possible implementation manner of the first aspect, in the sixth possible implementation manner of the first aspect, the terminal side notifying the access network side device of the Time domain information of the uplink data, including:

The terminal side device sends the time domain information of the uplink data to the access network side device on the uplink resource scheduled by the access network side device for the data transmission request of the terminal side device.

In the technical solution provided by the sixth possible implementation of the first aspect, the uplink resource that is dynamically scheduled by the access network side device is usually allocated based on the data transmission request of the terminal side device, so resource usage efficiency Higher, it is more reasonable than the allocation of non-scheduled resources. Therefore, the terminal side device can send the time domain information of the uplink data to the access network side device on the uplink resource dynamically scheduled by the access network side device, The access network side device learns the time domain information of the uplink data more conveniently and efficiently. In a specific implementation, when the terminal-side device sends a buffer data report to the uplink resource scheduled by the terminal-side device, the terminal-side device also uses the scheduled uplink resource to send the uplink data. The domain information, so that the access network side device can report the uplink data of the uplink data for the terminal side device again according to the buffered data report and further refer to the time domain information of the uplink data.

In a seventh possible implementation manner of the first aspect, the method further includes: the terminal side device accessing the access The network side device notifies the identifier of the uplink non-scheduled resource corresponding to the time domain information, so that the access network side device learns which uplink non-scheduled resource corresponding to the time domain information fed back by the terminal side device.

The second aspect of the present application provides a communication processing method for a non-scheduled resource performed by an access network side device. The access network side device may be an independent access network side device itself, or may be implemented in at least one chip of the access network side device or the access network side device to implement the non-scheduled resource. The circuit system of the communication processing method.

In the communication processing method of the non-scheduled resource provided by the second aspect, the access network side device sends, to the terminal side device, first configuration information indicating an uplink non-scheduled resource for uplink data transmission, and receives the Time domain information of the uplink data sent by the terminal side device;

The time domain information of the uplink data includes at least one of: an interval between an arrival time of the uplink data and a successfully sent uplink data, and an arrival time of the uplink data in the uplink non-scheduled resource. An interval between the time domain location adjacent to the arrival time of the uplink data and the arrival time of the uplink data in the uplink time domain location, the arrival time of the uplink data, The interval between the time domain location where the uplink data is sent for the first time and the time domain location where the uplink data is successfully sent for the first time in the non-scheduled resource; the waiting time when the uplink data is sent.

Optionally, the time domain information of the uplink data is carried in an RRC message, a PHY message or a MAC message sent by the terminal side device to the access network side device.

Optionally, in the communication processing method of the non-scheduled resource, the access network side device may send a PDCCH for indicating whether the non-scheduling function is activated. When the non-scheduling function is activated, the PDCCH carries the first configuration information.

Applying the technical solution provided by the second aspect, the time domain information of the uplink data is fed back to the access network side device by the terminal side device, so that the access network side device can learn the allocated non-scheduling resource. Is it appropriate to optimize resource allocation?

According to the second aspect, in a first possible implementation manner of the second aspect, the communication processing method of the non-scheduled resource further includes: the access network side device sends the adjustment information to the terminal side device, where the adjusting The information is used to adjust at least one of a time domain location and a frequency domain location of the uplink non-scheduled resource; where the uplink non-scheduled resource is adjusted in a time domain location or a frequency domain location, the access network The side device receives the uplink data sent by the terminal side device.

Optionally, the adjustment information is carried in an RRC message, a PHY message or a MAC message sent by the access network side device to the terminal side device.

In a first possible implementation manner of the second aspect, the access network side device may adjust the uplink non-scheduled resource in response to the time domain information of the uplink data that is fed back by the terminal device. As soon as the uplink non-scheduled resources come, the data transmission efficiency is improved.

In a second possible implementation manner of the second aspect or the second aspect, in a second possible implementation manner of the second aspect, the communication processing method of the non-scheduled resource further includes: the access network side device is Before receiving the time domain information of the uplink data sent by the terminal device, sending, to the terminal device, request information, where the request information is used to request time domain information of the uplink data.

The technical solution provided by the second possible implementation of the second aspect is that the terminal side device implements the sending of the time domain information of the uplink data based on the request of the access network side device.

In a third possible implementation manner of the second aspect, the method further includes: sending the second configuration information to the terminal side device And the second configuration information indicates a condition for notifying the access network side device of the time domain information of the uplink data, where the condition includes: notifying the period of the time domain information or notifying the time domain The threshold at which the time domain information exceeds the information.

The technical solution provided by the third possible implementation of the second aspect defines a trigger condition for the terminal side device to notify the time domain information.

In a fourth possible implementation manner of the second aspect, the communication processing method of the non-scheduled resource further includes: the access network The side device sends the third configuration information to the terminal side device, where the third configuration information indicates at least one of a period and a time-frequency resource used by the terminal-side device to send the time domain information of the uplink data.

The technical solution provided by the third possible implementation of the second aspect is to clarify the period or time when the access network side device configures, by using the third configuration information, the time domain information of the uplink data to be configured for the terminal side device. Frequency resources come. In a possible implementation, the third configuration information may be carried in the request sent by the access network side device in the second possible implementation manner of the second aspect.

In a fifth possible implementation manner of the second aspect, the method further includes:

Receiving request information for requesting notification of time domain information of the uplink data sent by the terminal device, and transmitting response information for the request information to the terminal device.

Optionally, an interval between an arrival time of the uplink data and a successfully sent uplink data, a time domain location adjacent to an arrival time of the uplink data in the uplink non-scheduled resource, and the uplink data. The interval between the arrival times of the non-scheduled resources, when the interval between the time domain location in which the uplink data is first sent and the time domain location in which the uplink data is successfully transmitted in the non-scheduled resource exceeds a certain threshold, The terminal side device sends the request information. Optionally, the threshold may be configured by the access network side device to the terminal side device.

The technical solution provided by the fifth possible implementation of the first aspect is to trigger the sending of the time domain information of the uplink data based on the request of the terminal side device and the response of the access network side device.

According to any one of the second aspect to the fifth possible implementation manner of the second aspect, in a sixth possible implementation manner of the second aspect, the access network side device receives the And the time domain information of the uplink data, where the access network side device receives the uplink resource scheduled by the terminal side device, where the access network side device is the uplink resource scheduled by the terminal side device Time domain information of the uplink data.

The technical solution provided by the sixth possible implementation manner of the second aspect corresponds to the technical solution provided by the sixth possible implementation manner of the first aspect, and thus the beneficial effects generated by the sixth possible implementation manner of the first aspect are also similar.

In a seventh possible implementation manner of the second aspect, the method further includes: the terminal side device and the core network side device Receiving the service information of the terminal side device that is sent by the core network side device, where the service information indicates the size of the uplink data, the sending duration of the uplink data, and the uplink data. The period and the start time of the uplink data are at least one item; and the first configuration information is determined according to the service information of the terminal side device.

Applying the technical solution provided by the seventh possible implementation manner of the second aspect, in the process of establishing the connection between the terminal side device and the core network side device, the access network side device receives the information received from the core network side device The service information of the terminal side device is configured to configure the uplink non-scheduled resource, so that the accuracy of resource configuration is further improved before the uplink data transmission, which is beneficial to improving resource utilization.

A third aspect of the embodiments of the present application provides a terminal side device, where the terminal side device includes: a receiving unit, a processing unit, and a sending unit. The receiving unit is configured to perform the receiving action of any one of the possible implementation manners of the first aspect to the first aspect, and the processing unit is configured to perform processing such as determining the first aspect to any one of the possible implementation manners of the first aspect. The action, the sending unit unit is configured to perform an action such as sending of any of the possible implementations of the first aspect to the first aspect. In a specific physical implementation, the receiving unit may be a receiving circuit or a receiver, the processing unit may be a processing circuit or a processor, and the transmitting unit may be a transmitting circuit or a transmitter. Optionally, the terminal device may be an independent terminal device, or may be a chip or a circuit system in the terminal device, where the chip or the circuit system includes multiple gate circuits to implement the foregoing The function of each functional unit. The communication processing device provided by the third aspect can achieve the beneficial effects achieved by any one of the foregoing first aspect to the first possible implementation manner of the first aspect, and details are not repeatedly described herein.

A fourth aspect of the embodiments of the present application provides an access network side device, where the access network side device includes: a sending unit and a receiving unit. The sending unit is configured to perform a sending action in any one of the possible implementation manners of the second aspect to the second aspect, and the receiving unit is configured to perform the receiving action of any one of the possible implementation manners of the second aspect to the second aspect. In a specific physical implementation, the transmitting unit may be a transmitting circuit, and the receiving unit may be a receiving circuit. Optionally, the access network side device may be an independent access network side device (for example, a base station), or may be a chip or a circuit system in the access network side device, where the chip or the circuit The system includes a plurality of gates to implement the functions of the various functional units described above. The communication processing device provided by the fourth aspect can achieve the beneficial effects achieved by any of the foregoing possible implementations of the second aspect to the second aspect, and details are not repeatedly described herein.

A fifth aspect of the embodiments of the present application provides a communication apparatus, including a processor and a memory, where the memory stores an instruction code, and when the code is invoked by the processor, implementing various possible implementations of the first aspect to the first aspect Any of the modes, or the method of any one of the second aspect to the second aspect, each possible implementation. Optionally, the communication device provided by the fifth aspect may be a chip system, or a terminal side device or an access network side device including the chip system. The communication device provided by the fifth aspect may implement any one of the foregoing possible implementation manners of the first aspect to the first aspect, or the beneficial effects achieved by any one of the second aspect to the second aspect, and may not be described in detail. .

A sixth aspect of the present application provides a computer storage medium, wherein the computer storage medium stores a code for implementing any one of the possible implementation manners of the first aspect to the first aspect, or the second aspect to the second Aspects of any of the possible implementations of any of the methods described. The computer storage medium provided by the sixth aspect may be included in a chip system or a terminal side device or an access network side device including the chip system. The computer storage medium provided by the sixth aspect may implement any one of the foregoing possible aspects to the first aspect to the first aspect, or the beneficial effects achieved by any one of the second aspect to the second aspect. Narration.

DRAWINGS

FIG. 1 is a schematic structural diagram of a wireless communication system according to an embodiment of the present application;

2 is a schematic diagram of system interaction of a communication processing method for a non-scheduled resource according to an embodiment of the present disclosure;

3 to FIG. 9 are schematic diagrams of allocation of a non-scheduled resource according to an embodiment of the present application;

FIG. 10 is a schematic diagram of system interaction of a communication processing method for a non-scheduled resource according to an embodiment of the present disclosure;

FIG. 11 is a schematic structural diagram of a unit of a communication processing apparatus according to an embodiment of the present disclosure;

FIG. 12 is a schematic structural diagram of a physical structure of a communication processing apparatus according to an embodiment of the present disclosure.

Detailed ways

The wireless communication system shown in FIG. 1 includes an access network side device and a terminal side device, and optionally also a core network side device. The access network side device may be a transmission and reception point (TRP) of the base station, the WLAN access point, and the like, and provides the terminal side device with the access service under the licensed spectrum or the access under the unlicensed spectrum. service. The access network side device is connected to the core network side device by wire or wirelessly. The terminal side device includes a User Equipment (UE), which is a device that provides voice and/or data connectivity to the user, for example, a handheld device with a wireless connection function, an in-vehicle device, and the like. Common terminal-side devices include, for example, mobile phones, tablets, notebook computers, PDAs, mobile internet devices (MIDs), wearable devices, such as smart watches, smart bracelets, pedometers, and the like.

The terminal side device and the access network side device respectively transmit uplink data and downlink data on the air interface according to the protocol layer on the uplink and the downlink. The access network side device may be used as a standalone device, or may be split into different devices according to a protocol layer. For example, after the access network side device is split according to the protocol layer, the access network side device may include a control unit (CU) and at least one distributed unit (DU). The CU is configured to implement the functions of the PDCP layer, the RRC layer, and the protocol layer of the access network side device; the DU is used to implement the RLC layer, the MAC layer, and the PHY layer of the access network side device. Features. A person skilled in the art may understand that, in the following implementation manners, the functions of the access network side device at the PDCP layer, the RRC layer or the foregoing protocol layer may be performed by the CU; for the access network side device at the RLC layer, the MAC The function of the layer or PHY layer is performed by the at least one DU.

The wireless communication system shown in FIG. 1 may be a New Radio (NR) system (also referred to as a 5G system), an LTE (long term evolution, LTE), or an advanced long term evolution (LTE-A) system. A wireless communication system such as an evolved long term evolution (eLTE) system.

In various embodiments of the present application, the access network side device may be a base station, a wireless local area network access point itself, or a chip in the base station or the wireless local area network access point or The circuit system; the terminal side device may be the user equipment itself, or a chip or a circuit system in the user equipment.

In various embodiments of the present application, non-scheduled resources are generally used for transmission of periodic data of substantially constant size, for example, industrial automation data with a period of 1 ms, and a period of 20 ms, and a packet size of about 100 bytes. Voice over internet protocol (VOIP) data and the like. The scheduling resource is a resource allocated by the access network side device in response to a resource scheduling request of the terminal side device (for example, a scheduling request transmitted through a random access procedure or a physical uplink control channel). The non-scheduled resource is opposite to the scheduling resource, and resources allocated by the access network side device for the terminal side device, such as SPS resources and grant free resources, are not required, and the resource scheduling request of the terminal side is not required.

In order to use the transmission of the periodic data, the access network side device configures the non-scheduled resource for at least one period, and the terminal side device may use the same period as the data period to be transmitted in at least one period. Transmitting the data. The access network side device may perform the primary allocation of the unscheduled resource for the terminal side device, and the terminal side device may be multiple times in the subsequent multiple TTIs before the non-scheduled resource is re-allocated or released. The signaling overhead on the PDCCH can be saved without using the access network side device to allocate the scheduling resources through the PDCCH in each TTI of the data to be transmitted. The access network side device does not know whether the time domain location of the scheduling resource allocated by the terminal side device is appropriate. If not, for example, the terminal side device takes a long time to wait for the non-scheduled resource to arrive. Will result in low data transmission efficiency.

For example, the allocation of the existing SPS has a problem that the resource arrival time and the data arrival time do not match: when an uplink data packet arrives at the terminal side device, there may be no allocated SPS resources, and the terminal side device will wait for the SPS. The uplink data packet is sent after the resource arrives. For VoIP data, since one data packet is sent every 20 ms, the data packet is sent out within 20 ms, usually without affecting the user experience. However, for industrial automation data, it takes 1 ms to send a data packet. If the waiting delay is too long, even more than 50% of the period (greater than 0.5 ms), the user experience will be seriously affected. Since the waiting time is extended, the time for actually transmitting the data packet is short, resulting in a decrease in data transmission efficiency, which also seriously affects the stability of data transmission.

In view of the above technical problem, the first embodiment of the present application provides a communication processing method for a non-scheduled resource, which is applied to a scenario in which an access network side device allocates a non-scheduled resource to a terminal for uplink data transmission. The system interaction diagram shown in Figure 2 includes the following content.

The access network side device sends the first configuration information to the terminal side device, where the first configuration information indicates the uplink non-scheduled resource, where the uplink non-scheduled resource is used for the uplink data of the terminal side device. transmission.

As the terminal side device moves in the wireless communication system, the terminal side device establishes a connection (eg, an RRC connection) with the access network side device by using a random access procedure, the access The network side device may configure an uplink non-scheduling function for the terminal side device through the connection (for example, an RRC message transmitted by using an RRC connection), and indicate a period of the uplink non-scheduled resource in the uplink non-scheduled function.

Optionally, the access network side device may indicate the first configuration information in the non-uplink scheduling function in the process of configuring the uplink non-scheduling function for the terminal side device.

Optionally, the access network side device indicates a time domain location of the uplink non-scheduled resource by carrying the first configuration information in the PDCCH, where the terminal side device acquires the first A configuration information, as shown in Figure 3, is a resource allocation diagram. The PDCCH further indicates activation of the uplink non-scheduled function and a frequency domain location of the uplink non-scheduled resource.

202. The terminal side device determines time domain information of the uplink data.

In 201 and 202, as a possible implementation manner, the uplink non-scheduled resource configured by the first configuration information includes at least two uplink non-scheduled resources, where different resource types (eg, grant free resources and SPS) The uplink non-scheduled resources of the resources are different kinds, or the same resource types (for example, all SPS resources) but different periods are also different. The terminal side device may use all kinds of uplink non-scheduled resources or select the first one of the at least two uplink non-scheduled resources (for example, SPS resources) for the transmission of the uplink data, and determine the first type of uplink. The time domain information corresponding to the non-scheduled resource.

If the interval between the arrival time of a certain data packet of the uplink data and the earliest time domain location of the first uplink non-scheduled resource exceeds a certain threshold (optionally, the threshold may be configured by the access network side device) And the second uplink non-scheduled resource (for example, the grant free resource) may arrive in advance to transmit the data packet, and the terminal side device may use the second uplink non-scheduled resource The access network side device sends the data packet. Optionally, the terminal side device may send the data packet by using only the second uplink non-scheduled resource, or may send the data packet by using the second uplink non-scheduled resource. After the uplink non-scheduled resource arrives, the data packet is sent by using the first non-scheduled resource to improve the reliability of data transmission. Other data packets for the upstream data may be processed as described above.

Optionally, the first type of uplink non-scheduled resource is a dedicated resource that is used by the terminal side device, and the second type of non-scheduled resource is a resource shared by the terminal side device and other terminal side devices. Terminal-side devices can compete to use shared resources). It can be seen that, in a general case, the usage priority of the first type of uplink non-scheduled resources is higher than the usage priority of the second type of non-scheduled resources.

In 202, the time domain information of the uplink data includes at least one of the following:

a) The arrival time of the uplink data.

The arrival time of the uplink data may specifically be the arrival time of the Mth uplink data packet of the uplink data. Specifically, the Mth uplink data packet may be generated by the application layer of the terminal side device, and the PDCP layer and the RLC layer of the terminal side device are sent from the time sent by the application layer of the terminal device. The time of the MAC layer or the PHY layer, the generation time of the PDCP layer, the RLC layer, the MAC layer or the PHY layer of the terminal side device, or the PDCP layer, the RLC layer, the MAC layer of the terminal side device or The time sent by the PHY layer.

Where M is a positive integer not less than one. The arrival time of the Mth uplink data packet may be calculated according to the arrival time of the first uplink data packet and the period of the data transmission. The time unit of the time domain information may be milliseconds, microseconds, nanoseconds, or may be a positive integer multiple of one TTI, such as at least one time domain symbol, at least one slot, at least one subframe. (sub-frame) or at least one frame (frame) and the like. Optionally, the terminal side device may use the bit value to indicate the time domain information. Assuming that the time unit of the time domain information is a time domain symbol and 14 symbols are included in one TTI, the time domain information may use 4 bits (a total of 16 bit values) to indicate a specific time value in the time domain information. .

And b) a time domain location adjacent to an arrival time of the uplink data in the uplink non-scheduled resource, for example, adjacent to an arrival time of the Mth uplink data packet in the uplink non-scheduled resource Time domain location. The adjacent time domain location may be (b-1) the latest time domain location in the uplink non-scheduled resource before the arrival time of the Mth uplink data packet, or (b-2) the uplink The most recent time domain location in the non-scheduled resource after the arrival time of the Mth uplink packet, as shown in FIG. Optionally, for case b), the time domain information of the uplink data may further indicate which of the (b-1) and (b-2) the adjacent time domain location is.

c) an interval between the time domain location adjacent to the arrival time of the uplink data and the arrival time of the uplink data in the uplink non-scheduled resource. For example, an interval between a time domain location adjacent to a time domain location of the Mth uplink packet and a time domain location of the Mth uplink packet in the uplink non-scheduled resource, as shown in FIG. 5 Shown.

d) an interval between the arrival time of the uplink data and the time when the uplink data packet is successfully transmitted. For example, the interval between the arrival time of the Mth uplink data packet and the time when the Mth uplink data packet is successfully transmitted. The time for successfully transmitting the Mth uplink data packet may be the time when the Mth uplink data packet is successfully sent, that is, the Mth uplink data packet is successfully sent in the uplink non-scheduled resource. The time domain location), or the time when the terminal side device receives the indication information from the access network side device for notifying the successful reception of the Mth uplink data packet, as shown in FIG. 6.

And e) an interval between the time domain location where the uplink data is sent for the first time and the time domain location where the uplink data is successfully sent for the first time in the non-scheduled resource. For example, the interval between the time domain location where the Mth uplink data packet is sent and the time domain location where the Mth uplink data packet was last successfully sent is sent for the first time in the non-scheduled resource. For ease of implementation, the interval between the time domain location where the Mth uplink data is sent for the first time and the time domain location where the Mth uplink data packet is successfully sent may be the period or the non-scheduled resource period. The number of repeated transmissions of the Mth uplink data packet is in units, as shown in FIG.

f) Waiting time when the uplink data arrives. For example, the interval between the arrival of the Mth uplink data packet of the uplink data and the transmission of the Mth uplink data packet is the waiting time. For ease of implementation, in this case, M=1 can be set.

Optionally, any of the cases b)-e) may be determined by the terminal side device according to a time domain location of the uplink non-scheduled resource.

Optionally, the terminal side device may further notify the access network side device of the identifier of the non-scheduled resource to which the time domain information belongs. For example, if the non-scheduled resource is an SPS resource, the identifier of the SPS resource may be an SPS cell wireless network temporary identifier (C-RNTI). If the non-scheduled resource is a grant free resource, the identifier of the grant free resource may be a group identifier of the terminal group where the terminal-side device is located. The access network side device may configure different non-scheduled resources for different uplink data of the terminal side device, and the terminal side device may send time domain information of different uplink data to the access network side device, and And indicating non-scheduled resources corresponding to the time domain information of the different uplink data respectively.

In an optional implementation manner, after the Mth uplink data packet arrives, the terminal side device starts a timer, and obtains the time domain information by using a timer duration of the timer. Specifically, the timer may be generated by the terminal side device to generate or issue protocol layer maintenance of the Mth data packet, thereby separately recording the foregoing various intervals.

Optionally, the time domain information of the uplink data may also be a resource adjustment value determined by the terminal side according to any one of the foregoing situations a)-d), for the access network side device to At least one of the time domain location and the frequency domain location of the non-scheduled resource is adjusted.

203. The terminal side device notifies the access network side device of time domain information of the uplink data.

In 203, the terminal side device may notify time domain information of the uplink data by using an RRC message, a MAC message, or a PHY message. The terminal device uses the RRC message to notify that the time domain information has high reliability, and uses the PHY message to notify the time domain information that the delay is short, and uses the MAC message to notify the time domain information. It is somewhere in between.

In the step 201-203, the access network side device can learn whether the allocated uplink non-scheduled resource is suitable by using the time domain information that is notified by the terminal device, thereby facilitating the improvement of data transmission efficiency.

As a possible implementation, the method further includes: 202', before the 203, the terminal side device receives the request information of the access network side device, where the request information is used to request the uplink data Domain information. Among them, 202 and 202' have no chronological order. Optionally, when the terminal-side device detects that the non-scheduled resource is to be sent or the waiting time exceeds a certain threshold, the terminal-side device sends the time domain of the uplink data to the access network-side device. information. Optionally, the access network side device may indicate whether the terminal side device performs the foregoing detection when configuring an uplink non-scheduling function.

As another possible implementation, the method further includes: 202", before the 203, the terminal side device sends request information to the access network side device, where the request information is used to request to notify the uplink data. The time domain information, and receiving the response information sent by the access network side device to the request information, wherein the response information indicates an allow notification. wherein 202 and 202" have no chronological order, and 202" And 202' is an alternative implementation.

Optionally, the method further includes: the access network side device sends the second configuration information to the terminal side device, where the second configuration information indicates that the uplink data is notified to the access network side device The condition of the time domain information, wherein the condition includes: a period of notifying the time domain information or a threshold exceeding the time domain information when the time domain information is notified.

Optionally, the method further includes: before the terminal side device notifies the access network side device of the time domain information of the uplink data, the terminal side device receives the sending by the access network side device And the third configuration information indicates at least one of a period and a time-frequency resource used by the access network side device to notify the time domain information of the uplink data.

Optionally, in order to further improve the data transmission efficiency, the terminal side device may implement the notification of the time domain information during uplink scheduling resource allocation and use by the access network side device.

Specifically, before 203, the method further includes: 2031, the terminal side device notifying the access network side device that the uplink data is to be sent, and requesting the access network side device to schedule an uplink resource; 2032. The access network side device schedules, by the terminal side device, a first uplink resource, and notifies the scheduled first uplink resource to the terminal side device. In 203, the terminal side device sends the time domain information and a buffer status report (BSR) to the access network side device by using the scheduled first uplink resource, where the BSR includes The amount of data to be transmitted of the uplink data in the terminal side device. Optionally, the time domain information is included in the BSR. Further, 2033, the access network side device schedules the second uplink resource for the terminal side device according to the data volume to be transmitted of the uplink data, and notifies the terminal side device of the scheduled second uplink resource; 2034 The terminal side device sends the uplink data by using the scheduled second uplink resource. Among them, 202 and 2031, 2032 have no chronological order. In this optional implementation manner, when the uplink data is generated, the uplink non-scheduled resource may take a long time to arrive, so the terminal side device will notify the access network side device how much data is to be sent. The domain information is also sent to the access network side device, and the uplink data is further transmitted by using the uplink scheduling resource allocated by the access network side device according to the data volume to be transmitted of the uplink data, and the uplink data may be reduced. The transmission delay increases the efficiency of data transmission. After the access network side device acquires the time domain information of the uplink data, in order to further improve the data transmission efficiency, the access network side device may use the time domain information of the uplink data to the uplink non- The scheduling resources are adjusted so that the adjusted uplink non-scheduled resources can arrive as early as possible. Therefore, the embodiment further includes the following method steps.

204. The access network side device determines, according to the time domain information of the uplink data, the adjustment information, where the adjustment information is used to adjust at least one of a time domain location and a frequency domain location of the uplink non-scheduled resource.

205. The access network side device sends the adjustment information to the terminal side device.

(m) in the case that the time domain information of the uplink data is a time domain location adjacent to an arrival time of the Mth uplink data packet in the uplink non-scheduled resource:

In an optional implementation, the access network side device determines that the adjustment amount of the time domain location of the uplink non-scheduled resource is the interval in the case (m), and sends the interval to the access network side device. The adjustment information indicates that adjustment is allowed. Optionally, the interval is not included in the adjustment information.

In another optional implementation manner, the access network side device is configured according to the time domain information, the load condition of the access network side device, and the configuration of the non-scheduled resource. The adjustment information of the non-scheduled resource is described to reduce the interval, so that the uplink non-scheduled resource arrives as soon as possible. The load situation includes: the number of all terminal side devices that the access network side device has accessed, the use of the uplink non-scheduled resource by other terminal side devices, and the like. The configuration of the non-scheduled resource includes: at least two resource configurations of the non-scheduled resource configured by the access network side device, where each resource configuration indicates a period corresponding to each resource configuration and the non-scheduled resource is Time-frequency position within the period. The access network side device may select one resource configuration (for example, the highest data transmission efficiency) from the at least two resource configurations, and indicate the selected resource configuration in the adjustment information, so that the terminal side The device uses the selected resource configuration for uplink data transmission, as shown in FIG. Specifically, the adjustment information may carry the selected identifier of the resource configuration, or according to the resource configuration and the offset currently configured in the time domain or the frequency domain.

(n) in the case where the time domain information is the interval between the arrival time of the Mth data packet of the uplink data and the time when the Mth data packet is successfully transmitted on the uplink non-scheduled resource:

In an optional implementation, the access network side device determines whether the interval in the condition (y) exceeds a preset threshold. If not exceeded, the access network side device may determine that the unscheduled resource does not need to be adjusted. If the access network side device determines that the number of retransmissions of the Mth data packet is excessive, and the resource conflict occurs on the non-scheduled resource, the access network side device determines that the non-relay is required. The scheduling resource is adjusted, and the adjustment information of the non-scheduled resource is sent to the terminal side device. Optionally, the adjustment information is specifically an indication cell, where the indication cell identifies a time-frequency resource location to which the non-scheduled resource is to be adjusted. Optionally, the access network side device may determine an adjustment amount of the non-scheduled resource in a time domain location, or determine an adjustment amount in a frequency domain location, and indicate, by using the adjustment information, the adjustment amount notification The terminal side device, where the terminal side device performs adjustment on the unadjusted non-scheduled resource according to the adjustment amount. Optionally, when the adjustment network information is sent by the access network side device, the terminal side device is further notified of the effective time of the adjustment information. The effective time indicates that the adjustment information is valid after the Xth period of the uplink non-scheduled resource after receiving the adjustment information, where X is an integer (exemplarily, X is less than or equal to 0, indicating that it is effective immediately)

Optionally, the uplink non-scheduled resource may belong to a certain resource group, and the access network side device performs adjustment of a time domain location or a frequency domain location according to the entire resource group. For ease of description, as shown in FIG. 9, the resource allocation diagram assumes that the resource group includes different uplink non-scheduled resources A, B, and C (which may or may not be continuous), optionally in the same period. , B, C can send duplicate packets to enhance signal transmission. If the access network side device determines to adjust the time domain location or the frequency domain location of the uplink non-scheduled resource A, all other non-scheduled resources (B and C) in the resource group to which the uplink non-scheduled resource A belongs are required. Make the same adjustments as A.

206. The terminal side device determines, according to the adjustment information, a time domain location or a frequency domain location where the uplink non-scheduled resource is adjusted.

The access network side device may notify the adjustment information by using an RRC message, a MAC message, or a PHY message. The access network side device uses the RRC message to notify that the time domain information has high reliability, and the PHY message is used to notify the time domain information that the delay is short, and the MAC message is used to notify the time. The domain information is somewhere in between.

207. The terminal side device sends the uplink data to the access network side device in a time domain location or a frequency domain location after the uplink non-scheduling resource is adjusted.

The second embodiment of the present application provides a communication processing method for a non-scheduled resource, as shown in FIG. 10, which includes the following contents. The second embodiment of the present application may be performed independently of the first embodiment, or may be performed before the step 201 provided by the first embodiment, thereby being used in combination with the method steps of the first embodiment.

1001. The terminal side device initiates connection establishment with the core network side device.

1002. After the connection establishment process or the connection establishment is complete, the access network side device acquires service information of the terminal side device.

1002 (A) The process of establishing a connection between the terminal side device, the access network side device, and the core network side device (for example, an RRC connection), the access network side device receiving the service information of the terminal side device from the core network side device, And configuring, according to the service information, the non-scheduled resource in a targeted manner for the terminal side device:

After receiving the connection establishment request (for example, carrying the Non-Access Stratum (NAS) layer signaling), the core network side device receives the connection establishment request transparently transmitted by the access network side device (for example, carrying the Non-Access Stratum (NAS) layer signaling) Sending an indication message to the access network side device, where the indication message indicates that the access network side device establishes a radio bearer on the air interface for the terminal side device, and further includes uplink data of the terminal side device or The start time of the downlink data.

Optionally, the start time of the uplink data is that the first uplink data packet arrives at the terminal side device time (for example, an application layer or another protocol layer that reaches the terminal side device, and the application device layer from the terminal side device device Or the time that other protocol layers are generated or issued). The other protocol layers may be a PDCP layer, an RLC layer, a MAC layer, or a PHY layer. The start time of the data may also be an offset from a system frame number of a certain frame (for example, the frame number is 0).

Optionally, the start time of the downlink data is that the first downlink data packet arrives at the access network side device (for example, a PDCPC layer, an RLC layer, a MAC layer, or a PHY layer that reaches the access network side device). Time, or from the PDCP layer of the access network side device, the time of generation or transmission of the RLC layer, the MAC layer or the PHY layer) or from the core network side device (for example, from a protocol layer of the core network side device) time. The start time of the downlink data may also be an offset of a system frame number of a certain frame (for example, a frame number is 0).

The time unit of the start time may be milliseconds, microseconds, nanoseconds, or may be a positive integer multiple of one TTI, such as at least one time domain symbol, at least one slot, at least one subframe. (sub-frame) or at least one frame (frame) and the like.

In a possible implementation manner, the terminal side device may carry the identifier of the terminal side device in the connection establishment request, and the core network side device reads the terminal side according to the identifier of the terminal side device a context of the device, where the context of the terminal-side device includes the start time of the uplink data or the downlink data of the terminal-side device, and in another possible implementation manner, the terminal-side device may be in the connection The start time of the uplink data or the downlink data of the terminal side device is carried in the request, so that the core network device notifies the service network information to the access network side device.

1002 (B) after the connection is established:

After the connection establishment is completed, the terminal side device may send the service information to the core network side device by using the non-access stratum signaling, so that the core network side device sends the service information to the access Network side equipment.

Optionally, in particular, for the characteristics of the industrial automation data, the uplink data and the downlink data usually have a fixed time offset, so the start time of the uplink data may be according to the start time of the downlink data and the terminal side. The device determines the processing time of the downlink data.

It should be noted that, in the second embodiment, the implementation of one of 1002 (A) and 1002 (B) may be performed, or after the implementation of 1002 (A) is performed, the implementation of 1002 (B) is still performed. Method to realize.

1003. The access network side determines, according to the service information, a configuration for transmitting a non-scheduled resource of at least one of the uplink data and the downlink data, so as to notify the terminal side device of the configuration of the non-scheduled resource.

Applying the technical solution provided by the second embodiment of the present application, before the data transmission, the access network side device can learn the start time of the uplink data or the downlink data of the terminal side device from the core network side device in advance, thereby Configuring the non-scheduled resource according to the service information, in particular, for the data originally transmitted by the terminal device in the communication system, the configuration of the non-scheduled resource may be reduced, which is beneficial to data transmission. Increased efficiency.

A third embodiment of the present invention provides a communication processing method for a non-scheduled resource. The method may be performed independently of the first embodiment, or may be further specifically refined as 201 and 202 in the first embodiment.

(A) The access network side device configures at least two types of uplink non-scheduled resources for the terminal side device (for example, indicated by the first configuration information in the first embodiment). The uplink non-scheduled resources of different resource types (for example, grant free resources and SPS resources) are different types, or the same resource types (for example, all SPS resources) but different types of different periods.

(B) The terminal side device uses all kinds of uplink non-scheduled resources or selects the first one of the at least two uplink non-scheduled resources (for example, SPS resources) for transmission of the uplink data.

Optionally, the first type of uplink non-scheduled resource has a feature that the usage priority is high, or is specific to the terminal side device (prived by the terminal side device). The terminal side device preferentially uses the first type of non-scheduled resource. If the reliability of the uplink data is required to be improved; or the interval between the arrival time of a certain data packet of the uplink data and the earliest arrival time domain location of the first uplink non-scheduled resource exceeds a certain threshold (optionally The threshold may be configured by the access network side device, and the second uplink non-scheduled resource (eg, grant free resource) may arrive in advance for transmitting the data packet; or the size of the uplink data If the channel becomes large, or the channel between the terminal-side device and the access network-side device is deteriorated, the terminal-side device may use the second uplink non-scheduled resource to send the Each packet of upstream data meets the data transmission needs. Optionally, the second uplink non-scheduled resource has a lower priority than the first type of uplink non-scheduled resource, or is shared by multiple terminal-side devices (other terminal-side devices can use the second uplink through competition). Features of non-scheduled resources).

Optionally, the terminal side device may send the data packet by using only the second uplink non-scheduled resource, or may continue to use the data packet while sending the data packet by using the second uplink non-scheduled resource. The first type of non-scheduled resource sends this packet to improve the reliability of data transmission. Other data packets for the upstream data may be processed as described above.

With the technical solution provided by the third embodiment, the access network side device can be configured to use the uplink non-scheduled resource for the terminal side device to send uplink data for the terminal side device, so that the transmission efficiency and stability of the uplink data can be improved.

The fourth embodiment of the present application provides a communication processing apparatus 1100, which is a schematic structural diagram of a communication processing apparatus unit shown in FIG. 11, and the communication processing apparatus 1100 includes a receiving unit 1101 and a transmitting unit 1102.

The communication processing apparatus 1100 provided by the fourth embodiment of the present application may be the terminal side device in the first embodiment, the second embodiment, or the third embodiment, and execute the method performed by the terminal side device. Correspondingly, the communication processing device 1100 further includes a processing unit 1103. Specifically, the receiving unit 1101 is configured to perform the receiving action of the terminal side device in the first embodiment, the second embodiment, or the third embodiment, where the sending unit 1102 is configured to perform the sending action of the terminal side device, and the processing unit 1103 is used to perform processing operations such as determining the terminal side device. For details, refer to the content described in the first embodiment, the second embodiment, and the third embodiment.

The communication processing apparatus 1100 provided by the fourth embodiment of the present application may also be an access network side device, which is used to implement the method performed by the access network side device in the first embodiment, the second embodiment, or the third embodiment. Specifically, the receiving unit 1101 is configured to perform the receiving action of the access network side device, and the sending unit 1102 is configured to perform the sending action of the access network side device, specifically, refer to the first embodiment, the second embodiment, and The content described in the third embodiment.

In a specific hardware implementation, as shown in the hardware structure of the communication processing device shown in FIG. 12, the function of the receiving unit 1101 may be implemented by the receiver 1201, and the sending unit 1102 may be implemented by the transmitter 1202. The function of the processing unit 1103 can be specifically implemented by the processor 1203. The communication processing device may also include various electronic circuits, such as bus 1204, memory 1205, communication interface 1206, and the like. The memory may include an instruction code, where the instruction code is used by the processor 1203 to implement the first embodiment, the access network side device or the terminal in the second embodiment or the third embodiment. The function of the side device.

The communication interface can be a wired communication interface, a wireless communication interface or a combination, wherein the wired communication interface can be, for example, an Ethernet interface. The Ethernet interface can be an optical interface, an electrical interface, or a combination thereof; the wireless communication interface can be a wireless local area network interface.

The bus can be a peripheral component interconnect (PCI) bus or an extended industry standard architecture (EISA) bus. The bus can be divided into an address bus, a data bus, a control bus, and the like.

Those skilled in the art will appreciate that embodiments of the present application can be provided as a method, system, or computer program product. Thus, the present application can take the form of an entirely hardware embodiment, an entirely software embodiment, or an embodiment in combination of software and hardware. Moreover, the application can take the form of a computer program product embodied on one or more computer-usable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) including computer usable program code.

The present application is described with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of the present application. It will be understood that each flow and/or block of the flowchart illustrations and/or FIG. These computer program instructions can be provided to a processor of a general purpose computer, special purpose computer, embedded processor, or other programmable data processing device to produce a machine for the execution of instructions for execution by a processor of a computer or other programmable data processing device. Means for implementing the functions specified in one or more of the flow or in a block or blocks of the flow chart.

The computer program instructions can also be stored in a computer readable memory that can direct a computer or other programmable data processing device to operate in a particular manner, such that the instructions stored in the computer readable memory produce an article of manufacture comprising the instruction device. The apparatus implements the functions specified in one or more blocks of a flow or a flow and/or block diagram of the flowchart.

These computer program instructions can also be loaded onto a computer or other programmable data processing device such that a series of operational steps are performed on a computer or other programmable device to produce computer-implemented processing for execution on a computer or other programmable device. The instructions provide steps for implementing the functions specified in one or more of the flow or in a block or blocks of a flow diagram.

Claims (27)

A communication processing method for a non-scheduled resource, which is used in a terminal device, and includes: Receiving, by the access network side device, first configuration information, where the first configuration information indicates an uplink non-scheduled resource, and the uplink non-scheduled resource is used for uplink data transmission; Determining time domain information of the uplink data, and notifying the access network side device of time domain information of the uplink data; The time domain information of the uplink data includes at least one of the following: The time interval between the arrival time of the uplink data and the successful transmission of the uplink data, the time domain location adjacent to the arrival time of the uplink data in the uplink non-scheduled resource, and the uplink non-scheduled resource The interval between the time domain location adjacent to the arrival time of the uplink data and the arrival time of the uplink data, the arrival time of the uplink data, where the uplink data is sent for the first time in the non-scheduled resource The interval between the time domain location and the time domain location where the uplink data was last successfully transmitted, and the waiting time when the uplink data is transmitted. The method of claim 1 further comprising: Receiving, by the access network side device, the adjustment information, where the adjustment information is used to adjust at least one of a time domain location and a frequency domain location of the uplink non-scheduled resource; Sending the uplink data to the access network side device in a time domain location or a frequency domain location after the uplink non-scheduled resource is adjusted. The method of claim 2 wherein The time domain information of the uplink data is carried in a physical layer message or a medium access control layer message sent by the terminal side device to the access network side device; and/or, The adjustment information is carried in a physical layer message or a medium access control layer message sent by the access network side device to the terminal side device. The method of any of claims 1-3, further comprising: Before requesting the access network side device to notify the time domain information of the uplink data, receiving request information sent by the access network side device, where the request information is used to request time domain information of the uplink data. The method of any of claims 1-4, further comprising: Notifying the access network side device of the identifier of the uplink non-scheduled resource corresponding to the time domain information. The method of any of claims 1-5, further comprising: Before the time domain information of the uplink data is notified to the access network side device, receiving second configuration information sent by the access network side device, where the second configuration information indicates to the access network side The device notifies the condition of the time domain information of the uplink data, where the condition includes: a period of notifying the time domain information or a threshold exceeding the time domain information when the time domain information is notified. A communication processing method for a non-scheduled resource, which is used for accessing a network side device, and includes: Sending, to the terminal side device, first configuration information, where the first configuration information indicates an uplink non-scheduled resource, and the uplink non-scheduled resource is used for uplink data transmission; Receiving time domain information of the uplink data sent by the terminal side device; The time domain information of the uplink data includes at least one of the following: The time interval between the arrival time of the uplink data and the successful transmission of the uplink data, the time domain location adjacent to the arrival time of the uplink data in the uplink non-scheduled resource, and the uplink non-scheduled resource The interval between the time domain location adjacent to the arrival time of the uplink data and the arrival time of the uplink data, the arrival time of the uplink data, where the uplink data is sent for the first time in the non-scheduled resource The interval between the time domain location and the time domain location where the uplink data was last successfully transmitted, and the waiting time when the uplink data is transmitted. The method of claim 7 further comprising: Transmitting, to the terminal side device, adjustment information, where the adjustment information is used to adjust at least one of a time domain location and a frequency domain location of the uplink non-scheduled resource; The uplink data sent by the terminal side device is received at a time domain location or a frequency domain location where the uplink non-scheduled resource is adjusted. The method of claim 8 wherein The time domain information of the uplink data is carried in a physical layer message or a medium access control layer message sent by the terminal side device to the access network side device; and/or, The adjustment information is carried in a physical layer message or a medium access control layer message sent by the access network side device to the terminal side device. The method of any of claims 7-9, further comprising: Before receiving the time domain information of the uplink data sent by the terminal side device, sending, to the terminal side device, request information, where the request information is used to request time domain information of the uplink data. The method of any of claims 7-9, further comprising: And receiving, by the terminal side device, an identifier of the uplink non-scheduled resource corresponding to the time domain information. The method of any of claims 7-11, further comprising: Transmitting, to the terminal side device, second configuration information, where the second configuration information indicates a condition for notifying the access network side device of the time domain information of the uplink data, where the condition includes: notifying the The period of the time domain information or the threshold over which the time domain information exceeds when the time domain information is notified. A method according to any of claims 7-12, wherein Receiving, in the connection establishment process of the terminal side device and the core network side device, the service information of the terminal side device that is sent by the core network side device, where the service information includes a start time of the uplink data; Determining the first configuration information according to the service information of the terminal side device. A terminal side device, comprising: a receiving unit, configured to receive first configuration information that is sent by the access network side device, where the first configuration information indicates an uplink non-scheduled resource, and the uplink non-scheduled resource is used for uplink data transmission; a processing unit, configured to determine time domain information of the uplink data; a sending unit, configured to notify the access network side device of time domain information of the uplink data; The time domain information of the uplink data includes at least one of the following: The time interval between the arrival time of the uplink data and the successful transmission of the uplink data, the time domain location adjacent to the arrival time of the uplink data in the uplink non-scheduled resource, and the uplink non-scheduled resource The interval between the time domain location adjacent to the arrival time of the uplink data and the arrival time of the uplink data, the arrival time of the uplink data, where the uplink data is sent for the first time in the non-scheduled resource The interval between the time domain location and the time domain location where the uplink data was last successfully transmitted, and the waiting time when the uplink data is transmitted. The terminal side device according to claim 14, wherein The receiving unit is further configured to receive the adjustment information that is sent by the access network side device, where the adjustment information is used to adjust at least one of a time domain location and a frequency domain location of the uplink non-scheduled resource; The sending unit is further configured to send the uplink data to the access network side device in a time domain location or a frequency domain location after the uplink non-scheduling resource is adjusted. The terminal side device according to claim 15, wherein The time domain information of the uplink data is carried in a physical layer message or a medium access control layer message sent by the terminal side device to the access network side device; and/or, The adjustment information is carried in a physical layer message or a medium access control layer message sent by the access network side device to the terminal side device. A terminal-side device according to any one of claims 13 to 16, characterized in that The receiving unit is further configured to: before requesting the access network side device of the time domain information of the uplink data, receive request information sent by the network device, where the request information is used to request the uplink data. Time domain information. A terminal-side device according to any one of claims 13-17, characterized in that The sending unit is further configured to notify the access network side device of the identifier of the uplink non-scheduled resource corresponding to the time domain information. A terminal-side device according to any one of claims 13 to 18, characterized in that Before the sending unit notifies the access network side device of the time domain information of the uplink data, the receiving unit is further configured to receive second configuration information sent by the access network side device, where the second a condition for notifying the access network side device of the time domain information of the uplink data in the configuration information, where the condition includes: notifying the period of the time domain information or the time when the time domain information is notified The threshold for domain information to exceed. An access network side device, comprising: a sending unit, configured to send first configuration information to the terminal side device, where the first configuration information indicates an uplink non-scheduled resource, and the uplink non-scheduled resource is used for uplink data transmission; a receiving unit, configured to receive time domain information of the uplink data sent by the terminal side device; The time domain information of the uplink data includes at least one of the following: The time interval between the arrival time of the uplink data and the successful transmission of the uplink data, the time domain location adjacent to the arrival time of the uplink data in the uplink non-scheduled resource, and the uplink non-scheduled resource The interval between the time domain location adjacent to the arrival time of the uplink data and the arrival time of the uplink data, the arrival time of the uplink data, where the uplink data is sent for the first time in the non-scheduled resource The interval between the time domain location and the time domain location where the uplink data was last successfully transmitted, and the waiting time when the uplink data is transmitted. The access network side device according to claim 20, wherein The sending unit is further configured to send, to the terminal side device, adjustment information, where the adjustment information is used to adjust at least one of a time domain location and a frequency domain location of the uplink non-scheduled resource; The receiving unit is further configured to receive the uplink data sent by the terminal side device in a time domain location or a frequency domain location after the uplink non-scheduling resource is adjusted. The access network side device according to claim 21, wherein The time domain information of the uplink data is carried in a physical layer message or a medium access control layer message sent by the terminal side device to the access network side device; The adjustment information is carried in a physical layer message or a medium access control layer message sent by the access network side device to the terminal side device. The access network side device according to any one of claims 20 to 22, characterized in that The sending unit is further configured to: before receiving the time domain information of the uplink data sent by the terminal side device, send request information to the terminal side device, where the request information is used to request the uplink data Domain information. The access network side device according to any one of claims 20-23, characterized in that The sending unit is further configured to send the second configuration information to the terminal side device, where the second configuration information indicates a condition for notifying the access network side device of the time domain information of the uplink data, where The condition includes: notifying a period of the time domain information or a threshold exceeding the time domain information when the time domain information is notified. The access network side device according to any one of claims 20-24, characterized in that The receiving unit is further configured to receive, according to the connection establishment process of the terminal side device to the core network side device, the service information of the terminal side device that is sent by the core network side device, where the service information is the uplink data. Starting time The access network side device further includes a processing unit, configured to determine the first configuration information according to the service information of the terminal side device. A terminal-side device comprising a memory and a processor, wherein the memory stores an instruction code, the instruction code being invoked by the processor to implement the method of any of claims 1-6. An access network side device comprising a memory and a processor, wherein the memory stores an instruction code, the instruction code being invoked by the processor to implement the method of any one of claims 7-13.

Images