Small data transmission method and communication apparatus

Through the access management network element, the access network device determines whether to use the small data transmission method, which solves the problem that the terminal device needs to enter the connected state to receive downlink small data when it is not connected, and realizes energy saving and resources save.

WO2024234964A1PCT designated stage expired Publication Date: 2024-11-21HUAWEI TECH CO LTD

Patent Information

Application Number
PCT/CN2024/089818
Authority / Receiving Office
WO · WO
Patent Type
Applications
Current Assignee / Owner
Priority Date
2023-05-12
Filing Date
2024-04-25
Publication Date
2024-11-21

AI Technical Summary

Technical Problem

The prior art lacks a small data transmission (MT SDT) scheme that supports mobile termination, resulting in terminal devices entering the connected state to receive downlink small data in a non-connected state, affecting energy saving and increasing signaling overhead.

Method used

Through the access management network element, the access network device determines whether to transmit data through small data transmission (SDT), and supports MT SDT to avoid unnecessary signaling overhead and resource waste.

Benefits of technology

It realizes energy saving of terminal equipment, reduces signaling overhead and resource waste, and improves transmission efficiency.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN2024089818_21112024_PF_FP_ABST
    Figure CN2024089818_21112024_PF_FP_ABST
Patent Text Reader

Abstract

Provided in the embodiments of the present application are a small data transmission (SDT) method and a communication apparatus. In the method, an access management network element may take a QoS flow as the granularity and provide the data size to an access network device, and the access network device may thus determine to transmit the data of the QoS flow by means of SDT. In this way, MT SDT can be supported, thereby facilitating the energy saving of a terminal device. In addition, the unnecessary transmission of data size can be avoided, that is, unnecessary signaling overheads can be avoided, thereby saving on transmission resources.
Need to check novelty before this filing date? Find Prior Art

Description

Small data transmission method and communication device

[0001] This application claims priority to the Chinese patent application filed with the State Intellectual Property Office of China on May 12, 2023, with application number 202310544098.6 and invention name “Method and communication device for small data transmission”, the entire contents of which are incorporated by reference into this application. Technical Field

[0002] The present application relates to the field of communications, and more particularly, to a method and a communication device for transmitting small data. Background Art

[0003] In a communication system, a terminal device in a non-connected state (idle or deactivated state) can perform small data transmission (SDT) without switching the radio resource control (RRC) state. This can extend the time the terminal device is in the non-connected state and save power consumption of the terminal device.

[0004] Based on the initiator of SDT, SDT can be divided into mobile originated (MO) SDT and mobile terminated (MT) SDT. MO SDT refers to the UE as a mobile terminal spontaneously initiating a service. For example, the application layer on the UE generates data and needs to send this data to the network. In this case, SDT starts when the UE initiates an uplink transmission. MT SDT refers to the network side sending data to the UE. In this case, SDT starts when the network side initiates a downlink transmission.

[0005] However, the current protocol lacks research on MT SDT solutions, which means that terminal devices still need to enter the connected state to receive small downlink data, which is not conducive to energy saving of terminal devices.

[0006] Summary of the Invention

[0007] The present application provides a method and a communication device for transmitting small data, which, on the one hand, can support MT SDT, which is beneficial to energy saving of terminal equipment, and on the other hand, can avoid unnecessary signaling overhead, thereby saving transmission resources.

[0008] In a first aspect, a method for transmitting small data is provided. The method can be executed by an access network device, or can be executed by a component configured in the access network device (for example, a module, circuit, chip or chip system), etc., and this application does not limit this.

[0009] The method includes: receiving first information from an access management network element, the first information including the size of data of a first quality of service (QoS) flow associated with a terminal device; and determining, based on the first information, whether to transmit the data of the first QoS flow via SDT. Alternatively, the method includes: receiving first information from an access management network element, the first information including the size of data of the first quality of service (QoS) flow associated with a terminal device; and using the first information to determine whether to transmit the data of the first QoS flow via SDT.

[0010] Based on the above solution, the access management network element can provide the access network device with the data size at the granularity of QoS flow, so that the access network device can determine to transmit the data of the QoS flow via SDT. In this way, on the one hand, MT SDT can be supported, which is beneficial to energy saving of terminal devices. On the other hand, it can avoid transmitting unnecessary data size, that is, avoid unnecessary signaling overhead, thereby saving transmission resources.

[0011] In combination with the first aspect, in some implementations of the first aspect, the method further includes: sending second information to the access management network element, where the second information is used to request the size of data of the first QoS flow.

[0012] Based on the above solution, the access network device can request the size of the data of the first QoS flow, so that the access network device can send the size of data required by the access network device according to the request, avoiding sending information that the access network device does not need, resulting in waste of transmission resources.

[0013] In combination with the first aspect, in some implementations of the first aspect, the first information includes an identifier of the first QoS flow.

[0014] Exemplarily, the terminal device is in an inactive state, and the inactive state extended discontinuous reception eDRX cycle of the terminal device is greater than 10.24 seconds.

[0015] In combination with the first aspect, in certain implementations of the first aspect, the method further includes: sending an N2 message to the access management network element, the N2 message does not include a new radio paging eDRX cycle NR Paging eDRX Cycle for RRC INACTIVE information element for the radio resource control inactive state, and the N2 message is used to instruct the session management network element or the user plane network element to release the data cache.

[0016] Optionally, the N2 message also includes a radio resource control state information RRC state Information element, and the value of the radio resource control state information is Inactive with enhanced eDRX. The value of the radio resource control state information is used to indicate that the terminal device is in an inactive state and the terminal device is configured with an inactive eDRX cycle greater than 10.24s.

[0017] Based on the above solution, the access network device can reuse the N2 message to instruct the session management network element or the user plane network element to release the data cache, so that SDT can proceed smoothly.

[0018] In combination with the first aspect, in some implementations of the first aspect, the first QoS flow is mapped to a first data radio bearer, and the first data radio bearer is used for small data transmission by the terminal device.

[0019] Based on the above solution, the access management network element provides the access network device with the data size of the SDT-related QoS flow, that is, it avoids providing the data size of the non-SDT-related QoS flow, thus avoiding useless information transmission and saving transmission resources.

[0020] On the second aspect, a method for transmitting small data is provided, which can be executed by an access management network element, or can also be executed by a component configured in the access management network element (for example, a module, circuit, chip or chip system), etc., and this application does not limit this.

[0021] The method includes: obtaining first information, where the first information includes the size of data of a first QoS flow associated with a terminal device; and sending the first information to an access network device.

[0022] In combination with the second aspect, in some implementations of the second aspect, the method further includes: receiving second information from the access network device, where the second information is used to request the size of data of the first QoS flow.

[0023] In combination with the second aspect, in some implementations of the second aspect, the first information includes an identifier of the first QoS flow.

[0024] Exemplarily, the terminal device is in an inactive state, and the inactive state extended discontinuous reception eDRX cycle of the terminal device is greater than 10.24 seconds.

[0025] In combination with the second aspect, in certain implementations of the second aspect, the method further includes: receiving an N2 message from an access network device, the N2 message does not include a new radio paging eDRX cycle NR Paging eDRX Cycle for RRC INACTIVE information element for the radio resource control inactive state, and the N2 message is used to instruct the session management network element or the user plane network element to release the data cache; and sending indication information to the session management network element or the user plane network element, where the indication information is used to instruct the session management network element or the user plane network element to release the data cache.

[0026] Optionally, the N2 message also includes a radio resource control state information RRC state Information element, and the value of the radio resource control state information is Inactive with enhanced eDRX. The value of the radio resource control state information is used to indicate that the terminal device is in an inactive state and the terminal device is configured with an inactive eDRX cycle greater than 10.24s.

[0027] In combination with the second aspect, in some implementations of the second aspect, the first QoS flow is mapped to a first data radio bearer, and the first data radio bearer is used for the terminal device to perform SDT.

[0028] It should be understood that the beneficial effects of the second aspect and its various implementation methods can refer to the first aspect and will not be repeated here.

[0029] On the third aspect, a method for transmitting small data is provided, which can be executed by an access network device, or can also be executed by a component configured in the access network device (for example, a module, circuit, chip or chip system), etc., and this application does not limit this.

[0030] The method includes: sending third information to an access management network element, the third information being used to indicate that a signaling radio bearer SRB2 configured by an access network device is used for SDT; receiving fourth information from the access management network element, the fourth information being used to indicate that downlink information of a terminal device is control signaling; and determining, based on the third and fourth information, to transmit control signaling via SDT, the control signaling being transmitted via SRB2. Alternatively, the method includes: sending third information to an access management network element, the third information being used to indicate that a signaling radio bearer SRB2 configured by an access network device is used for SDT; receiving fourth information from the access management network element, the fourth information being used to indicate that downlink information of a terminal device is control signaling; the third and fourth information being used to determine to transmit control signaling via SDT, the control signaling being transmitted via SRB2.

[0031] Based on the above solution, when SRB 2 configured on the access network device is used for SDT, and there is downlink control signaling to be sent, the access management network element can indicate to the access network device the presence of downlink control signaling from the terminal device, so that the access network device can determine to transmit the control signaling via SDT. This, on the one hand, supports MT SDT, which is beneficial for energy saving of the terminal device. On the other hand, when SRB 2 configured on the access network device is not used for SDT, the access management network element can not send the fourth information, thus avoiding unnecessary signaling overhead and saving transmission resources.

[0032] Exemplarily, the terminal device is in an inactive state, and an extended discontinuous reception eDRX cycle of the terminal device is greater than 10.24 seconds.

[0033] In combination with the third aspect, in certain implementations of the third aspect, the method further includes: sending an N2 message to the access management network element, the N2 message does not include a new radio paging eDRX cycle NR Paging eDRX Cycle for RRC INACTIVE information element for the radio resource control inactive state, and the N2 message is used to instruct the access management network element to cancel the mobile terminated communication processing.

[0034] Optionally, the N2 message also includes a radio resource control state information RRC state Information element, and the value of the radio resource control state information is Inactive with enhanced eDRX. The value of the radio resource control state information is used to indicate that the terminal device is in an inactive state and the terminal device is configured with an inactive eDRX cycle greater than 10.24s.

[0035] Based on the above solution, the access network device can reuse the N2 message to instruct the access management network element to release the mobile terminated communication process, so that SDT can proceed smoothly.

[0036] In the fourth aspect, a method for transmitting small data is provided. The method can be executed by an access management network element, or can be executed by a component configured in the access management network element (for example, a module, circuit, chip or chip system), etc. This application does not limit this.

[0037] The method includes: receiving third information from an access network device, the third information being used to indicate that a signaling radio bearer SRB2 configured by the access network device is used for SDT; and sending fourth information to the access network device, the fourth information being used to indicate that downlink information of the terminal device is control signaling.

[0038] Exemplarily, the terminal device is in an inactive state, and an extended discontinuous reception eDRX cycle of the terminal device is greater than 10.24 seconds.

[0039] In combination with the fourth aspect, in certain implementations of the fourth aspect, the method further includes: receiving an N2 message from an access network device, the N2 message does not include a new radio paging eDRX cycle NR Paging eDRX Cycle for RRC INACTIVE information element for the radio resource control inactive state, and the N2 message is used to instruct the access management network element to cancel the mobile terminated communication processing; and cancel the mobile terminated communication processing according to the N2 message.

[0040] Optionally, the N2 message also includes a radio resource control state information RRC state Information element, and the value of the radio resource control state information is Inactive with enhanced eDRX. The value of the radio resource control state information is used to indicate that the terminal device is in an inactive state and the terminal device is configured with an inactive eDRX cycle greater than 10.24s.

[0041] It should be understood that the beneficial effects of the fourth aspect and its various implementation methods can be referred to the third aspect and will not be repeated here.

[0042] In the fifth aspect, a method for transmitting small data is provided. The method can be executed by an access management network element, or can be executed by a component configured in the access management network element (for example, a module, circuit, chip or chip system), etc. This application does not limit this.

[0043] The method includes: obtaining first information, the first information including the size of the data of the first QoS flow of the terminal device; determining to transmit the data of the first QoS flow via SDT based on the first information; and sending fifth information to the access network device, the fifth information being used to instruct the access network device to transmit the data of the first QoS flow via SDT.

[0044] Based on the above solution, the access management network element can obtain the data size of the QoS flow granularity and determine whether to transmit the data of the QoS flow via SDT. The access management network element can then instruct the access network device to transmit the data of the QoS flow via SDT. This, on the one hand, can support MT SDT, which is beneficial for energy saving of terminal devices, and on the other hand, can avoid the size of the transmitted data, that is, avoid unnecessary signaling overhead, thereby saving transmission resources.

[0045] In combination with the fifth aspect, in some implementations of the fifth aspect, the first information includes an identifier of the first QoS flow.

[0046] Exemplarily, the terminal device is in an inactive state, and the inactive state extended discontinuous reception eDRX cycle of the terminal device is greater than 10.24 seconds.

[0047] In combination with the fifth aspect, in certain implementations of the fifth aspect, the first QoS flow is mapped to a first data radio bearer, and the first data radio bearer is used for the terminal device to perform SDT.

[0048] Based on the above solution, the access management network element provides the access network device with the data size of the SDT-related QoS flow, that is, it avoids providing the data size of the non-SDT-related QoS flow, thus avoiding useless information transmission and saving transmission resources.

[0049] In a sixth aspect, a method for transmitting small data is provided, the method comprising: an access management network element obtaining first information, the first information including the size of data of a first QoS flow associated with a terminal device; the access management network element sending the first information to an access network device; and the access network device determining, based on the first information, to transmit the data of the first QoS flow via SDT. Alternatively, the method comprises: an access management network element obtaining first information, the first information including the size of data of the first QoS flow associated with a terminal device; the access management network element sending the first information to the access network device; and the first information being used to determine to transmit the data of the first QoS flow via SDT.

[0050] In combination with the sixth aspect, in certain implementations of the sixth aspect, the method further includes: the access network device sends second information to the access management network element, where the second information is used to request the size of data of the first QoS flow.

[0051] In combination with the sixth aspect, in some implementations of the sixth aspect, the first information includes an identifier of the first QoS flow.

[0052] Exemplarily, the terminal device is in an inactive state, and the inactive state extended discontinuous reception eDRX cycle of the terminal device is greater than 10.24 seconds.

[0053] In combination with the sixth aspect, in certain implementations of the sixth aspect, the method further includes: the access network device sends an N2 message to the access management network element, the N2 message does not include a new radio paging eDRX cycle NR Paging eDRX Cycle for RRC INACTIVE information element for the radio resource control inactive state, and the N2 message is used to instruct the session management network element or the user plane network element to release the data cache.

[0054] Optionally, the N2 message also includes a radio resource control state information RRC state Information element, and the value of the radio resource control state information is Inactive with enhanced eDRX. The value of the radio resource control state information is used to indicate that the terminal device is in an inactive state and the terminal device is configured with an inactive eDRX cycle greater than 10.24s.

[0055] In combination with the sixth aspect, in certain implementations of the sixth aspect, the first QoS flow is mapped to a first data radio bearer, and the first data radio bearer is used for small data transmission by the terminal device.

[0056] In a seventh aspect, a method for transmitting small data is provided, the method comprising: an access network device sends third information to an access management network element, the third information being used to indicate that a signaling radio bearer SRB2 configured by the access network device is used for SDT; the access management network element sends fourth information to the access network device, the fourth information being used to indicate that downlink information of the terminal device is control signaling; the access network device determines, based on the third and fourth information, to transmit control signaling via SDT, and the control signaling is transmitted using SRB2. Alternatively, the method comprises: the access network device sends third information to the access management network element, the third information being used to indicate that a signaling radio bearer SRB2 configured by the access network device is used for SDT; the access management network element sends fourth information to the access network device, the fourth information being used to indicate that downlink information of the terminal device is control signaling; the third and fourth information are used to determine that control signaling is transmitted via SDT, and the control signaling is transmitted using SRB2.

[0057] Exemplarily, the terminal device is in an inactive state, and an extended discontinuous reception eDRX cycle of the terminal device is greater than 10.24 seconds.

[0058] In combination with the seventh aspect, in certain implementations of the seventh aspect, the method also includes: the access network device sends an N2 message to the access management network element, the N2 message does not include a new radio paging eDRX cycle NR Paging eDRX Cycle for RRC INACTIVE information element for the radio resource control inactive state, and the N2 message is used to instruct the access management network element to cancel the mobile terminated communication processing.

[0059] Optionally, the N2 message also includes a radio resource control state information RRC state Information element, and the value of the radio resource control state information is Inactive with enhanced eDRX. The value of the radio resource control state information is used to indicate that the terminal device is in an inactive state and the terminal device is configured with an inactive eDRX cycle greater than 10.24s.

[0060] In the eighth aspect, a method for transmitting small data is provided, the method comprising: an access management network element obtains first information, the first information including the size of data of a first QoS flow of a terminal device; the access management network element determines to transmit the data of the first QoS flow via SDT based on the first information; the access management network element sends fifth information to an access network device, the fifth information being used to instruct the access network device to transmit the data of the first QoS flow via SDT; the access network device determines to transmit the data of the first QoS flow via SDT based on the fifth information.

[0061] In combination with the eighth aspect, in some implementations of the eighth aspect, the first information includes an identifier of the first QoS flow.

[0062] Exemplarily, the terminal device is in an inactive state, and the inactive state extended discontinuous reception eDRX cycle of the terminal device is greater than 10.24 seconds.

[0063] In combination with the eighth aspect, in certain implementations of the eighth aspect, the first QoS flow is mapped to a first data radio bearer, and the first data radio bearer is used for SDT by the terminal device.

[0064] In the ninth aspect, a communication device is provided, which may be an access network device, or may be a component configured in the access network device (for example, a module, circuit, chip or chip system), etc. This application does not limit this.

[0065] The apparatus includes: a transceiver unit configured to receive first information from an access management network element, the first information including the size of data of a first quality of service (QoS) flow associated with a terminal device; and a processing unit configured to determine, based on the first information, whether to transmit the data of the first QoS flow via SDT. Alternatively, the apparatus includes: a transceiver unit configured to receive first information from an access management network element, the first information including the size of data of a first quality of service (QoS) flow associated with a terminal device; and the first information used to determine whether to transmit the data of the first QoS flow via SDT.

[0066] In combination with the ninth aspect, in certain implementations of the ninth aspect, the transceiver unit is further used to: send second information to the access management network element, where the second information is used to request the size of the data of the first QoS flow.

[0067] In combination with the ninth aspect, in certain implementations of the ninth aspect, the first information includes an identifier of the first QoS flow.

[0068] Exemplarily, the terminal device is in an inactive state, and the inactive state extended discontinuous reception eDRX cycle of the terminal device is greater than 10.24 seconds.

[0069] In combination with the ninth aspect, in certain implementations of the ninth aspect, the transceiver unit is further used to: send an N2 message to the access management network element, the N2 message does not include a new radio paging eDRX cycle NR Paging eDRX Cycle for RRC INACTIVE information element for the radio resource control inactive state, and the N2 message is used to instruct the session management network element or the user plane network element to release the data cache.

[0070] Optionally, the N2 message also includes a radio resource control state information RRC state Information element, and the value of the radio resource control state information is Inactive with enhanced eDRX. The value of the radio resource control state information is used to indicate that the terminal device is in an inactive state and the terminal device is configured with an inactive eDRX cycle greater than 10.24s.

[0071] In combination with the ninth aspect, in certain implementations of the ninth aspect, the first QoS flow is mapped to a first data radio bearer, and the first data radio bearer is used for SDT by the terminal device.

[0072] In the tenth aspect, a communication device is provided, which may be an access management network element, or may be a component configured in the access management network element (for example, a module, circuit, chip or chip system), etc. This application does not limit this.

[0073] The device includes: a processing unit, used to obtain first information, where the first information includes the size of data of a first QoS flow associated with a terminal device; and a transceiver unit, used to send the first information to an access network device.

[0074] In combination with the tenth aspect, in certain implementations of the tenth aspect, the transceiver unit is further used to: receive second information from the access network device, where the second information is used to request the size of data of the first QoS flow.

[0075] In combination with the tenth aspect, in some implementations of the tenth aspect, the first information includes an identifier of the first QoS flow.

[0076] Exemplarily, the terminal device is in an inactive state, and the inactive state extended discontinuous reception eDRX cycle of the terminal device is greater than 10.24 seconds.

[0077] In combination with the tenth aspect, in certain implementations of the tenth aspect, the transceiver unit is further used to: receive an N2 message from an access network device, the N2 message does not include an NR Paging eDRX Cycle for RRC INACTIVE information element, and the N2 message is used to instruct the session management network element or the user plane network element to release the data cache; and send indication information to the session management network element or the user plane network element, where the indication information is used to instruct the session management network element or the user plane network element to release the data cache.

[0078] Optionally, the N2 message also includes a radio resource control state information RRC state Information element, and the value of the radio resource control state information is Inactive with enhanced eDRX. The value of the radio resource control state information is used to indicate that the terminal device is in an inactive state and the terminal device is configured with an inactive eDRX cycle greater than 10.24s.

[0079] In combination with the tenth aspect, in certain implementations of the tenth aspect, the first QoS flow is mapped to a first data radio bearer, and the first data radio bearer is used for SDT by the terminal device.

[0080] In the eleventh aspect, a communication device is provided, which may be an access network device, or may be a component configured in the access network device (for example, a module, circuit, chip or chip system), etc. This application does not limit this.

[0081] The device includes: a transceiver unit, configured to: send third information to an access management network element, the third information being used to indicate that the signaling radio bearer SRB2 configured by the access network device is used for SDT; receive fourth information from the access management network element, the fourth information being used to indicate that the downlink information of the terminal device is control signaling; a processing unit, configured to determine, based on the third information and the fourth information, to transmit the control signaling via SDT, the control signaling being transmitted via SRB2. Alternatively, the device includes: a transceiver unit, configured to: send third information to the access management network element, the third information being used to indicate that the signaling radio bearer SRB2 configured by the access network device is used for SDT; receive fourth information from the access management network element, the fourth information being used to indicate that the downlink information of the terminal device is control signaling; the third information and the fourth information being used to determine to transmit the control signaling via SDT, the control signaling being transmitted via SRB2.

[0082] Exemplarily, the terminal device is in an inactive state, and an extended discontinuous reception eDRX cycle of the terminal device is greater than 10.24 seconds.

[0083] In combination with the eleventh aspect, in certain implementations of the eleventh aspect, the transceiver unit is further used to: send an N2 message to the access management network element, the N2 message does not include a new radio paging eDRX cycle NR Paging eDRX Cycle for RRC INACTIVE information element for the radio resource control inactive state, and the N2 message is used to instruct the access management network element to cancel the mobile terminated communication processing.

[0084] Optionally, the N2 message also includes a radio resource control state information RRC state Information element, and the value of the radio resource control state information is Inactive with enhanced eDRX. The value of the radio resource control state information is used to indicate that the terminal device is in an inactive state and the terminal device is configured with an inactive eDRX cycle greater than 10.24s.

[0085] In the twelfth aspect, a communication device is provided, which may be an access management network element, or may be a component configured in the access management network element (for example, a module, circuit, chip or chip system), etc. This application does not limit this.

[0086] The device includes: a transceiver unit, used to: receive third information from an access network device, the third information is used to indicate that the signaling radio bearer SRB2 configured by the access network device is used for SDT; send fourth information to the access network device, the fourth information is used to indicate that the downlink information of the terminal device is control signaling.

[0087] Exemplarily, the terminal device is in an inactive state, and an extended discontinuous reception eDRX cycle of the terminal device is greater than 10.24 seconds.

[0088] In combination with the twelfth aspect, in certain implementations of the twelfth aspect, the transceiver unit is further used to: receive an N2 message from an access network device, the N2 message does not include a new radio paging eDRX cycle NR Paging eDRX Cycle for RRC INACTIVE information element for the radio resource control inactive state, and the N2 message is used to instruct the access management network element to cancel the mobile terminated communication processing; the processing unit is further used to: cancel the mobile terminated communication processing according to the N2 message.

[0089] Optionally, the N2 message also includes a radio resource control state information RRC state Information element, and the value of the radio resource control state information is Inactive with enhanced eDRX. The value of the radio resource control state information is used to indicate that the terminal device is in an inactive state and the terminal device is configured with an inactive eDRX cycle greater than 10.24s.

[0090] In the thirteenth aspect, a communication device is provided, which may be an access management network element, or may be a component configured in the access management network element (for example, a module, circuit, chip or chip system), etc. This application does not limit this.

[0091] The device includes: a processing unit, used to obtain first information, the first information including the size of the data of the first QoS flow of the terminal device; determine to transmit the data of the first QoS flow via SDT based on the first information; a transceiver unit, used to send fifth information to the access network device, the fifth information is used to instruct the access network device to transmit the data of the first QoS flow via SDT.

[0092] In combination with the thirteenth aspect, in some implementations of the thirteenth aspect, the first information includes an identifier of the first QoS flow.

[0093] Exemplarily, the terminal device is in an inactive state, and the inactive state extended discontinuous reception eDRX cycle of the terminal device is greater than 10.24 seconds.

[0094] In combination with the thirteenth aspect, in certain implementations of the thirteenth aspect, the first QoS flow is mapped to a first data radio bearer, and the first data radio bearer is used for SDT by the terminal device.

[0095] In a fourteenth aspect, a communication device is provided, comprising a transceiver and a processor, wherein the processor is configured to control the transceiver to transmit and receive signals, and the processor is configured to execute a computer program, causing the communication device to perform the method of any one of the first to fifth aspects or any possible implementation thereof. Optionally, the communication device may further comprise a memory configured to store the computer program, and the processor is further configured to retrieve and execute the computer program from the memory.

[0096] Optionally, there are one or more processors and one or more memories.

[0097] Optionally, the memory may be integrated with the processor, or the memory may be provided separately from the processor.

[0098] Optionally, the communication device further includes a transmitter (transmitter) and a receiver (receiver).

[0099] In a fifteenth aspect, a chip is provided, comprising at least one processor configured to execute a computer program, causing a communication device equipped with the chip system to perform the method of any one of the first to fifth aspects or any possible implementation thereof. Optionally, the chip further comprises a memory coupled to the processor, the memory configured to store the computer program, and the processor further configured to call the computer program from the memory.

[0100] The chip may include an input circuit or interface for sending information or data, and an output circuit or interface for receiving information or data.

[0101] In the sixteenth aspect, a computer-readable storage medium is provided, which stores a computer program or code. When the computer program or code is run on a computer, the computer executes the method of any one of the above-mentioned first to fifth aspects or any possible implementation thereof.

[0102] In the seventeenth aspect, a computer program product is provided, comprising: a computer program code, which, when executed by a terminal device, enables the terminal device to execute the method in any one of the above-mentioned first to fifth aspects or any possible implementation thereof.

[0103] In the eighteenth aspect, a communication system is provided, comprising the communication devices of the aforementioned ninth and tenth aspects, or the communication devices of the eleventh and twelfth aspects, or the communication device and access network equipment of the thirteenth aspect, wherein the access network equipment is used to receive the fifth information in the thirteenth aspect. BRIEF DESCRIPTION OF THE DRAWINGS

[0104] FIG1 is a schematic diagram of a network architecture applicable to an embodiment of the present application.

[0105] FIG2 is a schematic diagram of an eDRX cycle applicable to an embodiment of the present application.

[0106] FIG3 is a schematic diagram of a paging process applicable to an embodiment of the present application.

[0107] FIG4 is a flow chart of mobile terminated communication processing applicable to an embodiment of the present application.

[0108] FIG5 is a flow chart of mobile terminated communication processing applicable to an embodiment of the present application.

[0109] FIG6 is a flow chart of a RACH-based SDT process applicable to an embodiment of the present application when the UE context does not change location.

[0110] FIG7 is a schematic diagram of a RACH-based SDT process applicable to an embodiment of the present application when the UE context location is changed.

[0111] FIG8 is a schematic diagram of a process of MT EDT applicable to an embodiment of the present application.

[0112] FIG9 is a schematic flowchart of a method for transmitting small data provided in an embodiment of the present application.

[0113] FIG10 is another schematic flowchart of a small data transmission method provided in an embodiment of the present application.

[0114] FIG11 is another schematic flowchart of a small data transmission method provided in an embodiment of the present application.

[0115] FIG12 is another schematic flowchart of a small data transmission method provided in an embodiment of the present application.

[0116] FIG13 shows a schematic diagram of a communication device 2000 provided in an embodiment of the present application.

[0117] FIG14 shows a schematic diagram of another communication device 3000 provided in an embodiment of the present application. DETAILED DESCRIPTION

[0118] The technical solution in this application will be described below with reference to the accompanying drawings.

[0119] The technical solutions of the embodiments of the present application can be applied to various communication systems, such as: long term evolution (LTE) system, LTE frequency division duplex (FDD) system, LTE time division duplex (TDD) system, universal mobile telecommunication system (UMTS), fifth generation (5G) system or new radio (NR) or other evolved communication systems. The technical solutions provided in this application can also be applied to future communication systems, such as the sixth generation mobile communication system, etc., which are not limited in this application.

[0120] The technical solution provided in this application can also be applied to machine type communication (MTC), long term evolution-machine (LTE-M), device-to-device (D2D) network, machine-to-machine (M2M) network, Internet of Things (IoT) network or other networks. Among them, the IoT network can include, for example, the Internet of Vehicles. Among them, the communication mode in the Internet of Vehicles system is collectively referred to as vehicle to other devices (vehicle to X, V2X, X can represent anything), for example, the V2X can include: vehicle to vehicle (V2V) communication, vehicle to infrastructure (V2I) communication, vehicle to pedestrian (V2P) communication or vehicle to network (V2N) communication, etc.

[0121] As an example, Figure 1 shows a schematic diagram of a network architecture applicable to an embodiment of the present application. As shown in Figure 1, the network architecture takes the 5G system (5GS) as an example. The network architecture 100 may include but is not limited to: access and mobility management function (AMF), session management function (SMF), user equipment (UE), radio access network ((R)AN) equipment, user plane function (UPF), data network (DN). Optionally, as shown in Figure 1, the network architecture 100 may also include: network slice selection function (NSSF), authentication server function (AUSF), unified data management (UDM), policy control function (PCF), and application function (AF).

[0122] Among them, DN can be the Internet; NSSF, AUSF, UDM, NEF, PCF, AF, AMF, SMF, and UPF are network elements in the core network (CN). Figure 1 takes the 5G system as an example, and the core network can be called the 5G core network (5GC or 5GCN).

[0123] The following is a brief introduction to each network element shown in FIG1 .

[0124] 1. User equipment (UE): can be called terminal equipment, access terminal, user unit, user station, mobile station, mobile station, remote station, remote terminal, mobile device, user terminal, terminal, wireless communication equipment, user agent or user device.

[0125] The terminal device can be a device that provides voice / data to users, for example, a handheld device or vehicle-mounted device with a wireless connection function. At present, some examples of terminals are: mobile phones, tablet computers, laptop computers, PDAs, mobile internet devices (MIDs), wearable devices, virtual reality (VR) devices, augmented reality (AR) devices, wireless terminals in industrial control, wireless terminals in self-driving, wireless terminals in remote medical surgery, wireless terminals in smart grids, wireless terminals in transportation safety, wireless terminals in smart cities, wireless terminals in smart homes, cellular phones, cordless phones, session initiation protocol (SIP) phones, wireless local loop (WLL) stations, personal digital assistants (PDAs), handheld devices with wireless communication capabilities, computing devices or other processing devices connected to wireless modems, wearable devices, terminal devices in 5G networks or future evolved public land mobile communication networks (PLMNs). The terminal equipment in the network (PLMN), etc., is not limited to this in the embodiments of the present application.

[0126] As an example and not a limitation, in the embodiment of the present application, the terminal device may also be a wearable device. Wearable devices may also be called wearable smart devices, which are a general term for wearable devices that are intelligently designed and developed using wearable technology for daily wear, such as glasses, gloves, watches, clothing, and shoes. A wearable device is a portable device that is worn directly on the body or integrated into the user's clothes or accessories. Wearable devices are not only hardware devices, but also achieve powerful functions through software support, data interaction, and cloud interaction. Broadly speaking, wearable smart devices include those that are fully functional, large in size, and can achieve complete or partial functions without relying on smartphones, such as smart watches or smart glasses, as well as those that only focus on a certain type of application function and need to be used in conjunction with other devices such as smartphones, such as various smart bracelets and smart jewelry for vital sign monitoring.

[0127] In addition, in the embodiments of the present application, the terminal device can also be a terminal device in an IoT system. IoT is an important part of the future development of information technology. Its main technical feature is to connect objects to the network through communication technology, thereby realizing an intelligent network that interconnects people and machines and things.

[0128] It should be noted that the terminal device and the access network device can communicate with each other using a certain air interface technology (such as NR or LTE technology). The terminal devices can also communicate with each other using a certain air interface technology (such as NR or LTE technology).

[0129] In the embodiments of the present application, the device for implementing the function of the terminal device can be the terminal device, or it can be a device that can support the terminal device to implement the function, such as a chip system or chip, which can be installed in the terminal device. In the embodiments of the present application, the chip system can be composed of a chip, or it can include a chip and other discrete devices.

[0130] 2. (Radio) Access Network (R)AN) equipment: This equipment provides authorized terminal devices in a specific area with access to the communications network. R)AN equipment can include wireless network equipment in 3rd Generation Partnership Project (3GPP) networks and access points in non-3GPP networks. For ease of description, the term "AN" is used below.

[0131] AN equipment can adopt different radio access technologies. There are two types of current radio access technologies: 3GPP access technology (for example, the radio access technology used in the third generation (3G), fourth generation (4G) or 5G systems) and non-3GPP (non-3GPP) access technology. 3GPP access technology refers to access technology that complies with 3GPP standard specifications. For example, the access network equipment in the 5G system is called the next generation Node Base station (gNB) or the next generation radio access network (NG-RAN) equipment. Non-3GPP access technologies may include air interface technologies represented by access points (APs) in wireless fidelity (WiFi), worldwide interoperability for microwave access (WiMAX), code division multiple access (CDMA), etc. AN equipment can also be an open access network (open RAN, O-RAN or ORAN), a cloud radio access network (CRAN), or devices of two or more of the above networks.

[0132] AN equipment is responsible for radio resource management, quality of service (QoS) management, data compression and encryption, etc. on the air interface side. AN equipment provides access services to terminal devices and forwards control signals and user data between terminal devices and the core network.

[0133] AN equipment may include, but is not limited to, a macro base station, a micro base station (also known as a small station), a radio network controller (RNC), a node B (NB), a base station controller (BSC), a base transceiver station (BTS), a home base station (e.g., a home evolved NodeB, or home Node B, HNB), a baseband unit (BBU), an AP in a WiFi system, a wireless relay node, a wireless backhaul node, a transmission point (TP), or a transmission and reception point (TRP), etc. It may also be a transmission point (TRP or TP) in a 5G (e.g., NR) system, one or a group of antenna panels (including multiple antenna panels) of a base station in a 5G system, or a module or unit constituting a gNB or a transmission point, such as a distributed unit (DU), a centralized unit (CU), or a radio unit (RU). Alternatively, it may be a base station in a next-generation communication 6G system, or it may be a core network device that performs base station functions in a future network. The embodiments of the present application do not limit the specific technology and specific device form adopted by the AN device. The CU here completes the functions of the radio resource control protocol and the packet data convergence protocol (PDCP) of the base station, and can also complete the function of the service data adaptation protocol (SDAP); the DU completes the functions of the radio link control layer and the medium access control (MAC) layer of the base station, and can also complete the functions of part of the physical layer or all of the physical layer. For the specific description of the above-mentioned various protocol layers, please refer to the relevant technical specifications of the 3rd Generation Partnership Project (3GPP). The CU and DU can be set separately, or they can be included in the same network element, such as a baseband unit (BBU). The RU can be included in a radio frequency device or a radio frequency unit, such as a remote radio unit (RRU), an active antenna unit (AAU) or a remote radio head (RRH).In different systems, CU, DU, or RU may have different names, but those skilled in the art will understand their meanings. For example, in the ORAN system, CU may also be called O-CU (Open CU), DU may also be called O-DU, and RU may also be called O-RU. Any of the CU (or CU-CP, CU-UP), DU, and RU in this application may be implemented through a software module, a hardware module, or a combination of a software module and a hardware module.

[0134] In some deployments, the gNB may include a centralized unit (CU) and a DU. The gNB may also include an active antenna unit (AAU). The CU implements some gNB functions, while the DU implements some gNB functions. For example, the CU is responsible for processing non-real-time protocols and services, and implementing the functions of the radio resource control (RRC) and packet data convergence protocol (PDCP) layers. The DU is responsible for processing physical layer protocols and real-time services, and implementing the functions of the radio link control (RLC), medium access control (MAC), and physical (PHY) layers. The AAU implements some physical layer processing functions, RF processing, and active antenna-related functions. Because RRC layer information ultimately becomes PHY layer information, or is converted from PHY layer information, in this architecture, higher-layer signaling, such as RRC layer signaling, can also be considered to be sent by the DU, or by both the DU and the AAU.

[0135] 3. Access management network element: mainly used for access control, mobility management, attachment and detachment functions.

[0136] In a 5G communication system, the access management network element may be an access and mobility management function (AMF) network element. In future communication systems, the access management network element may still be an AMF network element, or may have other names, which are not limited in this application.

[0137] 4. Session management network element: mainly used for user plane network element selection, user plane network element redirection, Internet protocol (IP) address allocation for terminal devices, as well as session establishment, modification and release and QoS control.

[0138] In a 5G communication system, the session management network element may be a session management function (SMF) network element. In future communication systems, the session management network element may still be an SMF network element, or may have other names, which are not limited in this application.

[0139] 5. User plane network element: also known as user plane function or user plane network element or user plane function network element, used for packet routing and forwarding, or quality of service (QoS) processing of user plane data.

[0140] In a 5G communication system, the user plane network element may be a user plane function (UPF) network element. In future communication systems, the user plane network element may still be a UPF network element, or may have other names, which are not limited in this application.

[0141] The UPF can be specifically divided into the intermediate-UPF (I-UPF) and the anchor-UPF (A-UPF). The I-UPF is connected to the access network RAN, and the A-UPF is the session anchor UPF, which can also be called the protocol data unit (PDU) session anchor (PSA).

[0142] 6. Policy control network element: Mainly used to guide the unified policy framework of network behavior and provide policy rule information for control plane network elements (such as AMF, SMF, etc.).

[0143] In a 5G communication system, the policy control network element may be a policy control function (PCF) network element. In future communication systems, the policy control network element may still be a PCF network element, or may have other names, which are not limited in this application.

[0144] 7. Application network element: mainly used to provide services to the 3GPP network, such as interacting with PCF for policy control.

[0145] In a 5G communication system, the application network element may be an application function (AF) network element. In future communication systems, the application network element may still be an AF network element, or may have other names, which are not limited in this application.

[0146] 8. NSSF: Mainly used for network slice selection.

[0147] 9. Data management network element: mainly used for UE contract data management, including storage and management of UE identification, UE access authorization, etc.

[0148] In a 5G communication system, the data management network element may be a unified data management (UDM) network element. In future communication systems, the unified data management may still be a UDM network element, or may have other names, which are not limited in this application.

[0149] 10. Data network: Operator network primarily used to provide data services to UEs, such as the Internet, third-party service networks, and IP Multimedia Service (IMS) networks.

[0150] In a 5G communication system, the data network may be a data network (DN). In future communication systems, the data network may still be a DN, or may have other names, which are not limited in this application.

[0151] 11. Authentication server network element: mainly used for user authentication, etc.

[0152] In a 5G communication system, the authentication server network element may be an authentication server function network element (AUSF) network element. In future communication systems, the authentication server network element may still be an AUSF network element, or may have other names, which are not limited in this application.

[0153] Optionally, the network architecture 100 may further include: a network exposure function (NEF).

[0154] In the network architecture 100, N1 is the interface between the terminal device and AMF; N2 is the interface between (R)AN and AMF, which is used for sending non-access stratum (NAS) messages, etc.; N3 is the interface between (R)AN and UPF, which is used for transmitting user plane data, etc.; N4 is the interface between SMF and UPF, which is used for transmitting information such as tunnel identification information of N3 connection, data cache indication information, and downlink data notification messages; N5 is the interface between PCF and AF; N6 is the interface between UPF and DN, which is used for transmitting user plane data, etc.; N7 is the interface between SMF and PCF; N8 is the interface between AMF and UDM; N10 is the interface between SMF and UDM; N11 is the interface between AMF and SMF; N12 is the reference point between AMF and AUSF; N22 is the interface between AMF and NSSF; N25 is the interface between UDM and PCF; N33 is the interface between AF and NEF.

[0155] It should be noted that the names of the various network elements and the communication interfaces between network elements involved in Figure 1 are simply described using the current protocol as an example, but do not limit the application of the embodiments of the present application to only currently known communication systems. Therefore, the standard names that appear when describing the current protocol as an example are all functional descriptions. This application does not limit the specific names of network elements, interfaces, or signaling, but only represents the functions of network elements, interfaces, or signaling, which can be correspondingly extended to other systems, such as 2G, 3G, 4G, or future communication systems.

[0156] It should be understood that the network architecture shown in Figure 1 above is only an example, and the network architecture applicable to the embodiments of the present application is not limited to this. Any network architecture that can realize the functions of the above-mentioned network elements is applicable to the embodiments of the present application.

[0157] It should also be understood that the AMF, SMF, UPF, PCF, NSSF, AUSF, UDM, etc. shown in Figure 1 can be understood as network elements used to implement different functions in the core network, for example, they can be combined into network slices as needed. These core network network elements can be independent devices or integrated into the same device to implement different functions. This application does not limit the specific form of the above network elements.

[0158] For ease of understanding, the concepts involved in this application are first briefly introduced. It should be understood that the basic concepts introduced below are briefly explained using the basic concepts specified in the NR protocol as an example, but the embodiments of this application are not limited to being applicable only to NR systems. Therefore, the standard names that appear when describing the NR system as an example are all functional descriptions. The specific names are not limited, but only indicate the functions of the equipment, and can be extended to other systems accordingly, such as the second generation (2G), third generation (3G), fourth generation (4G) or future communication systems.

[0159] 1.RRC status

[0160] 1) The terminal device is in the radio resource control connected (RRC CONNECTED) state, which means that an RRC connection is established between the terminal device and the access network device, and the access network device stores the terminal device's information (for example, one or more of the terminal device's access layer context information, radio configuration information, etc.). The RRC connection is a dedicated connection such as a data radio bearer (DRB) or a signaling radio bearer 2 (SRB2), and does not include the public connection of SRB0. The radio resource control connected state can be simply referred to as the RRC connected state or connected state.

[0161] 2) The terminal device is in the radio resource control idle (RRC IDLE) state, which means there is no RRC connection between the terminal device and the access network device, and the access network device does not store any information about the terminal device. The radio resource control idle state can be simply referred to as the RRC idle state or the idle state.

[0162] 3) The terminal device is in the radio resource control inactive (RRC INACTIVE) state, which means that the terminal device moves within the radio access network based notification area (RNA) and can be unaware of the access network device. The terminal device saves its own context, and the last serving access network device (for example, the last serving gNB) saves the context of the terminal device and the next generation (NG) interface connection with the access and mobility management function (AMF) and the user plane function (UPF). In RRC INACTIVE, the dedicated RRC connection between the terminal device and the access network device is suspended and can be restored later. For example, the terminal device restores the RRC connection by initiating the RRC resume process. The radio resource control inactive state can be simply referred to as the RRC inactive state or inactive state.

[0163] It should be understood that the last serving base station refers to the base station that releases the terminal device from the connected state to the inactive state, which retains the context of the terminal device and is sometimes also called an anchor base station.

[0164] Among them, the inactive state and the idle state can both be regarded as non-connected states.

[0165] 2. Paging and discontinuous reception (DRX)

[0166] Paging can be used to notify idle or inactive devices to establish a connection. Paging is divided into CN paging and RAN paging. CN paging is initiated by the core network and is mainly used to page idle devices. RAN paging is initiated by access network equipment and is used to page inactive devices.

[0167] When the terminal device is in an idle state, the network can page the terminal device based on the registration area. For example, after the terminal device successfully accesses the random access, when registering, the core network will allocate a registration area for the terminal device, which includes a tracking area identity (TAI) list, and the TAI list includes at least one tracking area (TA), and each tracking area TA includes at least one cell. When the terminal device is in an idle state, the core network sends a paging message to all cells under all TAs in the TAI list. In the terrestrial network (TN) and the non-terrestrial network (NTN), the paging scheme is determined based on which TA the terminal device is located. In many implementations, the network will first try to page in the last known cell, and if no terminal device responds, it will continue to try to page in the TA.

[0168] When the terminal device is in an inactive state, the RAN may page the terminal device based on a RAN-based notification area (RNA).

[0169] A terminal device in a non-connected state can monitor paging messages to determine whether it needs to enter a connected state.

[0170] In order to save power consumption when a terminal device monitors paging messages, a DRX mechanism is introduced into the communication protocol. The DRX mechanism can be divided into connected DRX and non-connected DRX.

[0171] In connected DRX, each DRX cycle consists of two periods: the On Duration and the Opportunity for DRX (also known as the Sleep period). During the On Duration, the terminal device is in the Active state, monitoring and receiving the Physical Downlink Control Channel (PDCCH). During the Opportunity period, the terminal device is in the Sleep state and does not monitor the PDCCH to reduce power consumption.

[0172] In non-connected DRX, there is no definition of duration and DRX opportunity. The terminal device wakes itself up in a set time unit according to a certain non-connected DRX cycle and listens for paging. If paging is detected, the terminal device switches to the active state, otherwise, it continues to maintain the current state. The time unit can be called a paging occasion (PO), which is determined by negotiation between the network device and the terminal device. For example, in LTE, a paging frame (PF) includes 10 subframes, indexed from 0 to 9. The time domain position of PO can be the subframe with index 7 in PF; in NR, PO is a set of PDCCH monitoring occasions, which is obtained based on the search space. The PO is located in the paging frame or the starting position of the PO is located in the paging frame.

[0173] According to the source of the paging message, the non-connected DRX configuration can be divided into an idle DRX for CN paging (IDLE DRX for CN paging) configuration and an inactive DRX for RAN paging (INACTIVE DRX for RAN paging) configuration.

[0174] Among them, the access network device can send the network default DRX configuration to the terminal device through the system information block (SIB) 1. Therefore, the default DRX cycle configured by SIB1 always exists. Even if the terminal device does not use the dedicated idle DRX (specific IDLE DRX) configuration or the dedicated inactive DRX (specific INACTIVE DRX) configuration, it still has an available DRX cycle.

[0175] If the terminal device needs to use a specific IDLE DRX configuration, such as a shorter DRX cycle, the terminal device can use NAS signaling to negotiate with the core network. The core network can configure a dedicated DRX cycle (specific DRX cycle configured by CN) for the terminal device. The terminal device can use the smaller cycle of the specific DRX cycle configured by CN and the default DRX cycle configured by SIB1 to monitor paging messages.

[0176] If the terminal device needs to use a specific INACTIVE DRX configuration, such as a shorter DRX cycle, the access network device can provide the terminal device with a dedicated DRX cycle (specific DRX cycle configured by RAN) when releasing the terminal device to an inactive state. In particular, at this time, the non-connected terminal device may also need to use the IDLE DRX configuration to monitor CN paging to cope with the special situation where the RRC states between the network and the terminal device are not aligned. Therefore, when the terminal device is configured with a specific DRX cycle configured by CN (specific DRX cycle configured by CN if configured), the terminal device can use the smaller cycle among the specific DRX cycle configured by CN if configured, the default DRX cycle configured by SIB1, and the specific DRX cycle configured by RAN to monitor paging messages.

[0177] In LTE, for a non-connected terminal device, after determining the DRX cycle T according to the above method, the paging frame PF (paging frame) and the paging occasion PO (paging occasion) can be further determined.

[0178] To further conserve power, the communication protocol introduces an extended DRX mechanism, which extends the DRX cycle and allows UEs to remain in sleep mode for longer periods. For example, the eDRX mechanism can extend the IDLE eDRX cycle to over three hours. Considering the potential for errors introduced by prolonged sleep, the concept of a paging time window (PTW) has been introduced to improve paging reliability.

[0179] FIG2 is a schematic diagram of an eDRX cycle applicable to an embodiment of the present application. As shown in FIG2 , taking IDLE eDRX as an example, in each eDRX cycle T eDRX_CN In the DRX cycle, there is a PTW, which can cover multiple DRX cycles T. The terminal device monitors paging according to the PO in the DRX cycle during the PTW. In Figure 2, the shaded time is the PO.

[0180] In a longer eDRX cycle, the terminal device can first determine the hyperframe number (H-SFN) corresponding to the paging hyperframe (PH) where the PTW is located, and then determine the frame number corresponding to the starting position of the PTW within the hyperframe. The terminal device can then determine the location of the complete PTW, including the starting and ending positions of the PTE. The PTW includes multiple DRX cycles T, and the terminal device can monitor the paging message for the PF and PO confirmed in each DRX cycle T.

[0181] It should be understood that the eDRX cycle T eDRX_CN The unit is a superframe, corresponding to 1024 radio frames. If a radio frame is 10ms long, a superframe is 10.24s. For narrowband Internet of Things (NB-IoT) and NR terminals, the number of superframes in an eDRX cycle ranges from 2, 4, …, to 1024. Since 1024 * 10.24s = 10485.76s ≈ 2.9h, the eDRX cycle can exceed 3 hours. Alternatively, the eDRX cycle can be 1 superframe (10.24s, PTW is not used in NR, but is used in LTE), 0.5 superframes (5.12s, PTW is not used in either NR or LTE), or even 0.25 superframes (2.56s, a new value introduced by NR and not present in LTE, but PTW is not used in this case).

[0182] Currently, the configuration of inactive eDRX only discusses the case where the eDRX cycle is no longer than 10.24s. The use of the eDRX cycle is the same as the use of the DRX cycle. The terminal device wakes up every inactive eDRX cycle and listens for paging messages.

[0183] FIG3 is a schematic diagram of a paging process applicable to an embodiment of the present application. As shown in FIG3 , the process 200 includes the following steps.

[0184] S201, data or signaling arrives at the last serving base station of the terminal device.

[0185] S202: Finally, the serving base station notifies other base stations in the RNA (e.g., gNB2) to initiate RAN paging.

[0186] S203, finally the serving base station and other base stations in RNA (such as gNB2) all initiate paging at the UE's PO time.

[0187] S204, the UE sends an RRC resume request message.

[0188] When the UE monitors its own paging message, it responds to the paging message and initiates connection recovery from another base station (e.g., gNB2), i.e., sends an RRC recovery request message to gNB2.

[0189] S205: gNB2 sends a context acquisition message to the last serving base station to obtain the UE context.

[0190] S206: Finally, the serving base station sends the UE context to gNB2.

[0191] S207: gNB2 restores the connection for the UE based on the UE context and sends an RRC recovery message to the UE.

[0192] S208: The UE completes connection recovery and sends an RRC resume complete message to gNB2.

[0193] S209: gNB2 initiates a path switch procedure to the AMF.

[0194] To further reduce power consumption, a potential approach is to extend the inactive eDRX cycle beyond 10.24s and, by analogy with the idle eDRX mechanism, introduce post-transition waiting (PTW) to allow the UE to sleep longer. To avoid excessive data buffering at the gNB due to extended sleep times, data can be cached at the UPF, as shown in Figure 4.

[0195] FIG4 is a flow chart of a mobile terminated communication process applicable to an embodiment of the present application. As shown in FIG4 , the process 300 includes the following steps.

[0196] In step S301, the UE registers with the network and negotiates with the network the idle DRX and eDRX configuration information, including the IDLE eDRX cycle. The AMF provides the UE's idle eDRX cycle to the NG-RAN via the RRC INACTIVE Assistance Info message for configuring the UE's INACTIVE eDRX.

[0197] The network here may refer to a CN, such as an AMF.

[0198] S302: The NG-RAN determines to initiate CN-based connection inactive mobile terminated (MT) communication handling.

[0199] Specifically, the CN and NG-RAN can determine to release the UE to the inactive state. "CN-based connection inactive MT communication processing" means that when the UE is in the inactive state, when the AMF in the CN receives downlink (DL) signaling from other CN network elements, it will reject the downlink signaling request, indicating that the UE's NAS signaling is unreachable. At the same time, the AMF will instruct the SMF and UPF to enable data caching instead of sending the data directly to the UE, that is, indicating that the UE's data is unreachable.

[0200] The NG-RAN may determine an inactive eDRX cycle value of the UE, where the inactive eDRX cycle value is greater than 10.24s.

[0201] S303: NG-RAN sends the UE's inactive eDRX configuration to the UE.

[0202] The NG-RAN may send an RRC release message to the UE to release the UE to the inactive state, and carry the UE's inactive eDRX configuration in the message, where the inactive eDRX configuration includes the inactive eDRX cycle value.

[0203] Optionally, the RRC release message may further include SDT configuration (SDT configuration).

[0204] Optionally, S303 may be executed after S302 or after S309.

[0205] S304: NG-RAN sends the UE's inactive eDRX configuration to the AMF via the N2 message.

[0206] Among them, the inactive eDRX configuration can be used by the AMF to determine the UE reachability.

[0207] In this application, UE reachability refers to whether the UE can monitor paging messages sent by the network. If the UE can monitor paging messages sent by the network, for example, the UE is in the time domain position corresponding to the PH, PF, and PO determined according to the inactive eDRX configuration, the UE is reachable. The AMF may request the NG-RAN to page the UE when the UE is reachable.

[0208] The NG-RAN may also request the AMF to activate CN-based MT communication handling for a UE that is in RRC_INACTIVE state and has eDRX exceeding 10.24 seconds through an N2 message (e.g., MT communication handling request message).

[0209] S305, AMF sends a PDU session update context request (Nsmf_PDUSession_UpdateSM Context request) message to SMF.

[0210] The PDU session update context request message can instruct the UPF to enable data caching.

[0211] S306, SMF and UPF perform N4 session modification (N4 session modification) process.

[0212] That is, based on the instructions of AMF, SMF can instruct UPF to enable data caching through the N4 session modification request message, and UPF can return the N4 session modification response message to SMF.

[0213] S307, UPF enables data caching.

[0214] S308, SMF sends a PDU session update context response (Nsmf_PDUSession_UpdateSM Context response) message to AMF.

[0215] This message may carry confirmation information for enabling data caching.

[0216] S309: AMF sends an N2 response message to NG-RAN.

[0217] This message may carry confirmation information for enabling data caching.

[0218] After S309 (if S303 is executed after S309, it is after S303), the UE is in an inactive state, the inactive eDRX cycle value of the UE is greater than 10.24s, and both the NG-RAN and the AMF store the inactive eDRX cycle value of the UE.

[0219] When the UPF receives downlink data, the SMF or UPF buffers it, and the SMF and AMF confirm whether data transmission is possible. If the UE's data or signaling is reachable, the UPF can send data to the UE, or the AMF can send signaling to the UE. This is shown in Figure 5.

[0220] FIG5 is a flow chart of a mobile terminated communication process applicable to an embodiment of the present application. As shown in FIG5 , the flow chart 400 includes the following steps.

[0221] S401, UPF receives downlink data and sends a data notification message to AMF.

[0222] S402, SMF sends an MT enable UE reachability request (MT_EnableUERechability request) message to AMF.

[0223] The MT enable UE reachability request message may carry information indicating that there is downlink data to be transmitted.

[0224] S403, AMF returns an MT enable UE reachability response (MT_EnableUERechability response) message to SMF.

[0225] The AMF determines whether the UE is reachable (i.e., determines the reachability of the UE) based on the stored inactive eDRX cycle value. If the UE is reachable, the AMF may indicate that the UE is reachable in the MT Enable UE Reachable Response message, and further, the AMF may execute S405. If the UE is not reachable, the AMF may estimate the maximum waiting time based on the inactive eDRX cycle value, provide its estimated maximum waiting time in the MT Enable UE Reachable Response message, and skip S405-S409.

[0226] S404, SMF returns a data notification response to UPF.

[0227] If the UE is reachable, the SMF may indicate to the UPF that the UE is reachable. If the UE is not reachable, the SMF may provide the UPF with a maximum waiting time.

[0228] S405: The AMF sends an N2 message to the NG-RAN. The N2 message can be used to request the NG-RAN to page the UE to enable connection recovery of the UE.

[0229] If the UE is reachable, the AMF triggers S405. At this point, the core network sends a message to the access network via the N2 interface to initiate RAN paging and request the UE's connection recovery, that is, the UE migrates to the RRC connected state, or the UE remains in the RRC inactive state but can perform SDT.

[0230] The N2 message may be a downlink data notification message (DL data notification), used to indicate that there is downlink data cached in the 5GC or that there is downlink signaling in the 5GC that needs to be sent to the UE.

[0231] S406: NG-RAN sends a paging message to the UE.

[0232] S407: The UE triggers a connection recovery request process.

[0233] Specifically, the UE responds to the paging message and restores the RRC connection, and the AMF notifies the UPF to release the data cache. Then, the UPF, NG-RAN, and UE may execute S408, or the AMF, NG-RAN, and UE may execute S409.

[0234] S408: UPF sends the downlink data to the UE via NG-RAN.

[0235] In step S409, the AMF sends the downlink signaling to the UE via the NG-RAN.

[0236] The downlink signaling may be a NAS PDU packet.

[0237] 4. Small data transmission (SDT) technology

[0238] Before the advent of SDT, if a terminal device in a non-connected state needed to transmit data, it would first trigger the RRC connection recovery process to switch to a connected state. Figure 5 shows an example. SDT technology enables terminal devices to transmit data in a non-connected state (e.g., inactive state), extending the time the terminal device is in the non-connected state and avoiding the signaling overhead and energy consumption caused by frequently triggering the RRC connection recovery process.

[0239] SDT can be used in a variety of scenarios, including smartphone-related services, such as heartbeat packets or push messages from applications (APPs); and non-smartphone-related services, such as periodic data from wearable devices (such as heartbeat packets) and periodic data sent by industrial wireless sensor networks. In addition, the specific size of small data in the embodiments of the present application is not limited. For example, data between 100 and 300 bytes can be considered small data.

[0240] It can be understood that the data transmission and small data transmission described below in the embodiments of the present application may refer to SDT, and the uplink data, downlink data and data described in the embodiments of the present application may all be small data.

[0241] In addition, although SDT refers to small data transmission, for signaling, as long as the SDT requirements are met, it can also be transmitted via SDT.

[0242] According to the initiator of SDT, SDT can be divided into mobile originated (MO) SDT and mobile terminated (MT) SDT. MO SDT means that the UE, as a mobile terminal, needs to spontaneously initiate a service. For example, the application layer on the UE side generates data and needs to send the data to the network side. That is, SDT starts when the UE initiates uplink transmission. When performing MO SDT, after the access network receives the SDT data or signaling from the UE, it can be forwarded to the core network by a pre-configured DRB or SRB used for SDT. MT SDT means that the network side has data or signaling that needs to be sent to the UE. That is, SDT starts when the network side initiates downlink transmission.

[0243] It should be understood that for MO SDT, after the start of SDT, since the SDT communication link already exists, if there is downlink data or signaling, it can also be transmitted via SDT. Similarly, for MT SDT, after the start of SDT, since the SDT communication link already exists, if there is uplink data or signaling, it can also be transmitted via SDT.

[0244] The existing NR only considers MO SDT, not MT SDT. According to the resources used, MO SDT can be divided into SDT based on random access channel (RACH) (i.e., configured through system information) and SDT based on configured grant Type 1 (Type 1CG) (configured through dedicated signaling in the RRC release message). Among them, Type 1 CG is the configured grant Type 1 in the uplink physical shared channel (PUSCH). RACH-based SDT is divided into RACH-based SDT without UE context relocation and RACH-based SDT with UE context relocation according to the location of the UE context. The processes are shown in Figures 6 and 7 respectively. It should be understood that "UE context has not changed location", that is, the UE context is still stored in the last serving base station, and "UE context changes location", that is, the UE context is no longer stored by the last serving base station.

[0245] FIG6 is a flow chart of RACH-based SDT when the UE context does not change location, applicable to an embodiment of the present application. As shown in FIG6 , the flow 500 includes the following steps.

[0246] S501: An inactive UE sends an RRC recovery request message to a receiving gNB.

[0247] The receiving base station refers to the base station corresponding to the cell currently accessed by the UE.

[0248] The RRC recovery request message may include uplink (UL) SDT data and / or uplink SDT signaling. The uplink signaling may be a NAS PDU packet.

[0249] S502: The receiving base station sends a retrieve UE context request message to the last serving base station of the UE.

[0250] The Get UE Context Request message may carry an SDT indication and other auxiliary information, such as a single packet or multiple packets.

[0251] S503: Finally, the serving base station determines that it stores the UE context.

[0252] Optionally, the last serving base station makes a decision based on the auxiliary information. For example, in the case of a single packet, the last serving base station may determine that it will continue to store the UE context instead of sending the UE context to the receiving base station.

[0253] S504: Finally, the serving base station sends a partial UE context transfer message to the UE.

[0254] The partial UE context transfer message may include SDT RLC configuration information but does not include UE context.

[0255] S505: The receiving base station sends a partial UE context transfer acknowledgement message to the last serving base station.

[0256] Based on the partial UE context transfer message, the receiving base station knows that the UE context is still stored in the last serving base station. Therefore, subsequent data transmission still needs to go through the last serving base station. Therefore, the receiving base station establishes the SDT RLC entity, while the last serving base station can retain its PDCP entity for subsequent UE information transmission.

[0257] After S502 to S505, the UE context is still stored in the last serving base station. Next, the receiving base station can send the uplink data obtained in S501 to the last serving base station, which is then sent to the UPF. Alternatively, the receiving base station sends the uplink signaling obtained in S501 to the last serving base station, which is then sent to the AMF.

[0258] Subsequently, if the UE still has uplink SDT data or uplink SDT signaling, the UE can continue to send it to the receiving base station, and the receiving base station sends the data to the UPF through the last serving base station and sends the signaling to the AMF.

[0259] In addition, if there is downlink SDT data, the UPF can also be sent to the receiving base station through the last serving base station, and then sent to the UE by the receiving base station.

[0260] S506: Finally, the serving base station sends a retrieve UE context failure message to the receiving base station.

[0261] The UE context acquisition failure message may include an RRC release message, instructing the UE to continue to remain in the inactive state.

[0262] S507: The receiving base station sends an RRC release message to the UE.

[0263] The RRC release message may include a suspend indication, instructing the UE to continue to remain in the inactive state.

[0264] After executing S507, the UE is still in the inactive state.

[0265] FIG7 is a flow chart of RACH-based SDT when the UE context location is changed, which is applicable to an embodiment of the present application. As shown in FIG7 , the flow 600 includes the following steps.

[0266] S601: An inactive UE sends an RRC recovery request message to a receiving base station.

[0267] S602: The receiving base station sends a UE context acquisition request message to the last serving base station of the UE.

[0268] S601 and S602 may refer to S501 and S602 and are not described in detail here.

[0269] S603: Finally, the serving base station sends a retrieve UE context response message to the receiving base station, which includes the UE context.

[0270] For example, in the case of multiple packets, the serving base station may finally determine not to continue storing the UE context, but send the UE context to the receiving base station.

[0271] S604: The receiving base station determines to continue to perform SDT when the UE is in an inactive state.

[0272] After S602 to S603, the UE context is transferred to the receiving base station. Next, the receiving base station can directly send the uplink data obtained in S601 to the UPF.

[0273] Furthermore, the receiving base station may send an Xn-U address indication to the last serving base station. Subsequently, if the last serving base station receives downlink SDT data from the UPF, the last serving base station will send it to the receiving base station, which will then send it to the UE.

[0274] Subsequently, if the UE still has uplink SDT data, the UE can continue to send it to the receiving base station, which then directly sends it to the UPF.

[0275] S605: The receiving base station sends a path switch request message to the AMF.

[0276] S606: The AMF sends a path switch request acknowledgement message to the receiving base station.

[0277] After S605 and S606, the path between the UE and the core network has been switched from the last serving base station to the receiving base station. Next, the receiving base station can send the uplink signaling obtained in S601 directly to the AMF, for example, through a UL NAS transfer message.

[0278] Subsequently, if there is other downlink SDT data for the UE, the UPF will send it directly to the receiving base station, which will then send it to the UE.

[0279] Subsequently, if the UE still has uplink SDT data, the UE can continue to send it to the receiving base station, which then directly sends it to the UPF.

[0280] S607: The receiving base station determines to stop performing SDT.

[0281] S608: The receiving base station sends an RRC release message to the UE. The RRC release message may include a suspend configuration, instructing the UE to continue to remain in an inactive state.

[0282] S609: The receiving base station sends a UE context release message to the last serving base station, instructing the last serving base station to release the UE context.

[0283] After executing S609, the UE is still in the inactive state.

[0284] Existing NRs do not include MT SDT, but LTE uses the MT early data transmission (EDT) method. EDT is basically similar to SDT. Its purpose is to enable terminal devices in an inactive state to transmit data in LTE to save power. Specifically, when both the UE and the network support MT EDT and there is downlink data for the UE, the mobility management entity (MME) initiates the MT EDT process. Taking the MT EDT process based on the control plane as an example, its process is shown in Figure 8.

[0285] FIG8 is a flow chart of MT EDT applicable to an embodiment of the present application. As shown in FIG8 , the flow 700 includes the following steps.

[0286] S701, the serving gateway (S-GW) sends downlink data size information to the MME, which carries the size of the downlink data.

[0287] S702: The MME sends an S1-AP paging message to the eNB.

[0288] Specifically, after the MME receives the DL data size information from the S-GW, the MME sends an S1-AP paging message to the eNB, carrying the DL data size information, to assist the eNB in ​​determining whether MT EDT is required. If MT EDT is required, the eNB may execute S703.

[0289] Optionally, before S702 , the UE exchanges information about its support for MT EDT with the CN through NAS signaling.

[0290] S703: The eNB sends a paging message to the UE.

[0291] Specifically, the eNB may carry the MT EDT indication in the paging message, where the MT EDT indication is used to instruct the UE to perform the MO EDT process based on the control plane, that is, to multiplex the MO EDT process.

[0292] In conjunction with the methods of Figures 4, 5, and 8, one possible implementation for implementing MT SDT is to carry data size information in the N2 message shown in Figure 5 (i.e., in S405) to indicate the size of the downlink data packet. However, this implementation has the following problems: some services are always small packet services and do not need to carry data size information. By default, SDT can be used for them. Alternatively, the DRBs corresponding to some services are non-SDT and cannot be transmitted via SDT. For such services, data size does not need to be provided.

[0293] In other words, AMF always provides the data size to NG-RAN, which may cause unnecessary signaling overhead and waste transmission resources in some cases.

[0294] Based on this, the present application proposes a method and a communication device for small data transmission, which, on the one hand, can support MT SDT, which is beneficial to energy saving of terminal equipment, and on the other hand, can avoid unnecessary signaling overhead, thereby saving transmission resources.

[0295] FIG9 is a schematic flow chart of a method for transmitting small data provided by an embodiment of the present application. As shown in FIG9 , the method 800 includes the following steps.

[0296] S810: Access a management network to obtain first information.

[0297] The first information includes the data size of a first quality of service (QoS) flow associated with the terminal device.

[0298] In this application, the first QoS flow may refer to one QoS flow or multiple QoS flows, that is, a QoS flow set.

[0299] Optionally, if the first QoS flow refers to multiple QoS flows, the multiple QoS flows can be mapped to the same DRB.

[0300] In the present application, the data of the first QoS flow can be understood as data transmitted through the first QoS flow.

[0301] In this application, the data size of the first QoS flow can be understood as the granularity of the data size based on the QoS flow. That is, the data volume to be transmitted in the first QoS flow. For example, the data volume size is 100 bits.

[0302] Optionally, the first information is associated with a PDU session identifier (PDU Session ID) and an identifier of the first QoS flow.

[0303] Optionally, the data of the first QoS flow refers to downlink data.

[0304] As an example, the first information can be an information element (IE), such as an MT SDT information IE, which directly carries the size of the data of the first QoS flow, which is associated with the PDU session identifier (PDU Session ID) and the QoS flow identifier (such as the QoS flow identifier (QoS folw identifier, QFI)), and is used to represent the size of the data of the first QoS flow (i.e., the QoS flow identified by the QoS flow identifier).

[0305] As another example, the first information may be indication information. There is a corresponding relationship between the value of the first information and the size of the data. The value of the first information may indicate the size of the data of the first QoS flow.

[0306] Optionally, the first information may include an identifier of the first QoS flow. For example, the identifier of the QoS flow is a QoS flow identifier (QoS flow identifier, QFI), and for another example, the identifier of the QoS flow is a 5G QoS identifier (5G QoS identifier, 5QI).

[0307] Optionally, the first information may further include an identifier of a PDU session associated with the first QoS flow (PDU session ID).

[0308] Optionally, the terminal device is in an inactive state, and an inactive eDRX cycle of the terminal device is greater than 10.24s.

[0309] For example, before S810, the access management network element or the access network device configures an inactive eDRX for the terminal device, and the configured inactive eDRX period is greater than 10.24s.

[0310] S820: The access management network element sends first information to the access network device. Correspondingly, the access network device receives the first information.

[0311] Exemplarily, in the NR system, the first information can be carried in the N2 message.

[0312] It should be understood that in the NR architecture, the N2 interface is a dedicated interface between the access management network element and the access network equipment, and the messages transmitted on this interface are collectively referred to as N2 messages.

[0313] Exemplarily, the N2 message can be used to trigger RAN paging, such as an N2 message triggered RAN paging (N2 message triggered RAN Paging), or a downlink data notification message (DL Data Notification). After receiving the N2 message, the access network device can perform RAN paging on the terminal device in the RRC_INACTIVE state.

[0314] S830: The access network device determines to transmit data of the first QoS flow by means of SDT according to the first information.

[0315] In this application, "transmission via SDT" means that when the access network device sends a paging message to the terminal device, it carries an SDT indication, so that the terminal device maintains a non-connected state (for example, an inactive state) to transmit data according to the indication in the paging message.

[0316] In this application, "SDT method" may refer to "MT SDT".

[0317] Specifically, the access network device can determine whether the size of the data of the first QoS flow meets the transmission requirements of SDT based on the first information. For example, the maximum amount of data supported by SDT is x. When the size of the data of the first QoS flow is less than or equal to x, the data of the first QoS flow can be transmitted via SDT.

[0318] Based on the above solution, the access management network element can provide the access network device with the data size at the granularity of QoS flow, so that the access network device can determine the data of the QoS flow to be transmitted via SDT. In this way, on the one hand, MT SDT can be supported, which is beneficial to energy saving of terminal devices. On the other hand, the size of unnecessary data can be transmitted, that is, unnecessary signaling overhead can be avoided, thereby saving transmission resources.

[0319] Optionally, the first QoS flow is mapped to a first data radio bearer, and the first data radio bearer is used for the terminal device to perform SDT. In other words, the first QoS flow is an SDT-related QoS flow.

[0320] It should be understood that data radio bearers (DRBs) can be divided into DRBs for SDT (i.e., DRB for SDT, referred to as SDT DRBs) and DRBs not used for SDT (i.e., DRB for non-SDT, referred to as non-SDT DRBs). In other words, the first QoS flow refers to the QoS flow mapped to the SDT DRB.

[0321] Based on the above solution, the access management network element provides the access network device with the data size of the SDT-related QoS flow, that is, it avoids providing the data size of the non-SDT-related QoS flow, thus avoiding useless information transmission and saving transmission resources.

[0322] Optionally, the method 800 further includes: S801, the access network device sends second information to the access management network element, and correspondingly, the access management network element receives the second information.

[0323] The second information is used to request the size of data of the first QoS flow.

[0324] Optionally, the second information includes an identifier of the first QoS flow.

[0325] For the description of the "first QoS flow", please refer to the previous text and will not be repeated here.

[0326] Optionally, if the first QoS flow is an SDT-related QoS flow, S801 can be understood as that the access network device requests the size of the data of the SDT-related QoS flow from the access management network element, that is, only when the SDT-related QoS flow has data to be transmitted, the session management network element or the user plane network element will provide the size of the data.

[0327] It should be understood that the size of the data requested for the first QoS flow may refer to the size of the data for starting to report the first QoS flow, or may refer to the size of the data for updating the first QoS flow.

[0328] In one case, before S801, the access network device did not request the data size of any QoS flow. At this time, S801 can be understood as the access network device requesting the access management network element to enable reporting of data size with QoS flow as the granularity, and the size of the data of the first QoS flow needs to be reported.

[0329] In another case, before S801, the access network device has requested the data size of other non-first QoS flows (for example, QoS flow 2). At this time, S801 can be understood as the access network device requesting the access management network element to report the data size of the first QoS flow (for example, QoS flow 1), that is, adding the data size of the first QoS flow to the list that needs to be reported.

[0330] Optionally, the second information may be carried in an N2 message. The N2 message may be a newly defined N2 message, for example, an MT communication handling request message.

[0331] Optionally, the N2 message sent in S801 also includes the inactive eDRX cycle of the terminal device. By carrying the inactive eDRX cycle of the terminal device, the N2 message can request the access management network element to start MT communication processing, or request the session management network element or the user plane network element to start data caching.

[0332] For example, the N2 message may include a new radio paging eDRX cycle for RRC INACTIVE (NR paging eDRX cycle for RRC INACTIVE) information element, which indicates that the reported eDRX cycle is an inactive eDRX cycle.

[0333] Optionally, the N2 message sent in S801 may further include a radio resource control state information (RRC state Information) information element, where the value of the information element is inactive or inactive with enhanced eDRX.

[0334] It should be understood that in the present application, the N2 message sent by the access network device to the access management network element may include an RRC state Information element.

[0335] In one possible implementation, the value of the RRC state information element may be any of the following: Connected, Inactive without enhanced eDRX, Inactive with enhanced eDRX, or Idle, as shown in Table 1. Connected and Inactive without enhanced eDRX may be combined into a single value, indicating that the UE's data or signaling is reachable. For example, if the UE is in the RRC CONNECTED state, the value of RRC state information may be Connected, as shown in the first row of Table 1. For another example, if the UE is in the RRC INACTIVE state but is configured with an INACTIVE eDRX cycle of no more than 10.24 seconds or is not configured with an INACTIVE eDRX cycle, the value of RRC state information may be Inactive without enhanced eDRX, as shown in the second row of Table 1. Inactive with enhanced eDRX indicates that the UE's data or signaling reachability depends on the UE's enhanced eDRX configuration, i.e., the UE's data or signaling is reachable under certain conditions, as shown in the third row of Table 1. In this case, the network side can determine whether the UE data or signaling is reachable based on the UE's enhanced eDRX configuration. For example, if the UE is in the RRC INACTIVE state but is configured with an INACTIVE eDRX cycle greater than 10.24s, the RRC state Information value is Inactive with enhanced eDRX. If the current superframe, radio frame, or monitoring opportunity meets the paging superframe, paging frame, or paging opportunity determined by the UE's enhanced eDRX configuration, the UE data or signaling is reachable; otherwise, the UE data or signaling is unreachable. Idle indicates that neither UE data nor signaling is reachable. For example, if the UE is in the RRC IDLE state, the RRC state Information value is Idle, as shown in row 4 of Table 1.

[0336] Optionally, only when the value of RRC state Information is Inactive with enhanced eDRX, the N2 message needs to carry the above-mentioned NR paging eDRX cycle for RRC INACTIVE information element.

[0337] Table 1

[0338] In this implementation, the value of the RRC state Information element in the N2 message sent in S801 is Inactive with enhanced eDRX, which is the case shown in row 3 of Table 1. The value "Inactive with enhanced eDRX" of the RRC state Information element indicates that the terminal device is in an inactive state and is configured with an inactive eDRX cycle greater than 10.24s.

[0339] In another possible implementation, the RRC state information value can be any of the following: Connected, Inactive, or IDLE, as shown in Table 2. Table 2 is similar to Table 1, except that Table 2 combines the RRC state information values ​​of Inactive with enhanced eDRX and Inactive without enhanced eDRX in Table 1 into one, that is, the RRC state information value is Inactive, as shown in rows 2 and 3 of Table 2.

[0340] Table 2

[0341] In this implementation, the value of the RRC state Information element in the N2 message sent in S801 is Inactive, which is the case shown in the third row of Table 2. The value "Inactive" of the RRC state Information element indicates that the terminal device is in an inactive state.

[0342] Among them, the RRC state Information information element is a mandatory (M) information element in the N2 message sent by the access network device to the access management network element, and the NR paging eDRX cycle for RRC INACTIVE information element is an optional (O) information element in the N2 message sent by the access network device to the access management network element.

[0343] It should be understood that the N2 message can be used in not only SDT but also non-SDT scenarios, as illustrated below. In the following example, the N2 message is described as an MT communication processing request message.

[0344] As an example, when RNA is updated, an INACTIVE UE configured with enhanced eDRX (e.g., an INACTIVE eDRX cycle of 20.48s) initiates a connection recovery request message, and the NG-RAN releases the UE back to RRC_Inactive, and no inactive eDRX configuration is configured (e.g., an INACTIVE DRX cycle of 0.64s), or only a Rel-17 inactive eDRX configuration (e.g., an INACTIVE eDRX cycle of 5.12s). In this case, the NG-RAN should trigger the sending of an MT communication handling request message to cancel the core network's MT communication handling and data buffering, indicating that the UE is now available for downlink data and / or signaling transmission. At this time, the RRC state information in the MT communication handling request is Inactive, but does not carry enhanced eDRX.

[0345] As another example, during RNA update, an INACTIVE UE configured with enhanced eDRX (e.g., an INACTIVE eDRX cycle of 20.48 seconds) initiates a Connection Recovery Request message. The NG-RAN releases the UE back to RRC_Inactive and updates the Rel-18 enhanced INACTIVE eDRX configuration, e.g., extending the INACTIVE eDRX cycle from 20.48 seconds to 40.96 seconds. At this point, the NG-RAN should trigger the sending of an MT Communication Handling Request message. In this case, the RRC state information in the MT Communication Handling Request is Inactive, but carries the updated enhanced eDRX cycle value, e.g., 40.96 seconds.

[0346] As another example, when RNA is updated, an INACTIVE UE configured with enhanced eDRX (for example, an INACTIVE eDRX cycle of 20.48s) initiates a connection recovery request message, and the NG-RAN moves the UE to RRC_IDLE. In this case, the NG-RAN should trigger the sending of an MT communication handling request message to cancel the MT communication handling and data caching of the core network associated with the configuration of the INACTIVE eDRX cycle of 20.48s. In addition, since the UE is in RRC_IDLE, the UE cannot directly transmit downlink data and / or signaling (the core network can follow traditional processing methods, such as caching UE data on demand, and paging the UE through CN paging for data transmission). At this time, the RRC state information in the MT communication handling request is Idle, and does not carry enhanced eDRX.

[0347] As another example, when the UE attempts to recover from RRC_INACTIVE, for example due to the arrival of MO service data, but is rejected by the NG-RAN, for example due to network congestion, the UE receives the RRC reject message (carrying the wait time) from the NG-RAN and remains in the RRC_INACTIVE state. At this time, the RRC state information in the MT communication handling request is INACTIVE, and whether to carry enhanced eDRX is determined based on the UE's INACTIVE eDRX configuration. That is, if the INACTIVE eDRX cycle is greater than 10.24s, the enhanced eDRX cycle value is carried, otherwise it is not carried.

[0348] As another example, when the UE recovers from RRC_INACTIVE and the NG-RAN responds to the recovery request message, and is eventually released and redirected by the NG-RAN (UE context migration), the UE may be in RRC CONNECTED, RRC IDLE or RRC INACTIVE. At this time, the value of the RRC state information in the MT communication handling request and whether enhanced eDRX is carried are similar to the above situation.

[0349] It should be understood that, in this application, UE data or signaling reachable means that the UE can receive data or signaling. Correspondingly, UE reachable means that the UE can monitor paging messages, for example, the UE is in the time domain position corresponding to PH, PF and PO.

[0350] It should also be understood that, in the present application, the access management network element enabling MT communication processing includes, when the access management network element receives downlink signaling from other core network elements, rejecting the downlink signaling request and indicating that the NAS signaling of the terminal device is unreachable. In addition, the access management network element enabling MT communication processing also includes the access management network element instructing the session management network element or the user plane network element to enable data caching instead of directly sending the data to the terminal device.

[0351] Based on the above solution, the access network device can request the size of the data of the first QoS flow, so that the access network device can send the size of data required by the access network device according to the request, avoiding sending information that the access network device does not need, resulting in waste of transmission resources.

[0352] Optionally, the N2 message may further include an identifier of a PDU session associated with the first QoS flow (PDU session ID).

[0353] As an implementation manner, the access management network element obtaining the first information may refer to the access management network element itself determining the first information.

[0354] In this application, "determining the first information" may refer to counting the size of the data in the first QoS flow.

[0355] As an example, the access management network element is AMF. When there is downlink data of the terminal device, UPF sends data size information to SMF, indicating the size of the data of QoS flow 1. SMF sends the size of the data of QoS flow 1 to AMF. AMF can count the size of the data of QoS flow 1 received multiple times (i.e., determine the first information). For example, at time 1, UPF sends a data packet of QoS flow 1 to AMF through SMF with a size of 50, and AMF determines that the size of the data packet received for QoS flow 1 is 50. At time 2, UPF sends a data packet of QoS flow 1 to AMF through SMF with a size of 30, then AMF will receive the updated data packet size of QoS flow 1, that is, it determines that the size of the data packet received for QoS flow 1 is 80.

[0356] Among them, as another implementation manner, the access management network element obtains the first information, which may also refer to the session management network element or the user plane network element determining the first information and sending the first information to the access management network element.

[0357] Similar to the access management network element determining the first information above, the session management network element or the user plane network element may also determine the first information, ie, count the size of the data in the first QoS flow and send the statistical result to the access management network element.

[0358] Optionally, in this implementation, if the first information is determined by the session management network element, the access management network element can send the second information to the session management network element, and the user plane network element can send the size of the downlink data to the session management network element when there is downlink data of the terminal device. Then, the session management network element can send the determined first information to the access management network element.

[0359] Optionally, in this implementation, if the first information is determined by the user plane network element, the access management network element can send the second information to the session management network element and the user plane network element. The user plane network element can count the size of the downlink data when there is downlink data of the terminal device, thereby determining the first information. Furthermore, the user plane network element can send the first information to the access management network element through the session management network element.

[0360] Therefore, optionally, in the present application, the method 800 further includes: the access management network element sends the second information to the session management network element, and the session management network element sends the second information to the user plane network element.

[0361] In the present application, the time period during which the access management network element obtains the first information in S810 may start with the moment when the access management network element instructs the session management network element or the user plane network element to enable data caching and end with the moment when the access management network element instructs the session management network element or the user plane network element to de-cache data. That is, the size of the statistical data is the total amount of data of the first QoS flow cached by the session management network element or the user plane network element.

[0362] Optionally, the method 800 further includes: S840, the access network device sends an N2 message to the access management network element, and correspondingly, the access management network element receives the N2 message.

[0363] Optionally, the N2 message is a newly defined N2 message, such as an MT communication processing request message or a radio resource control inactive state transmission report (RRC INACTIVE transition report) message.

[0364] In one implementation, the N2 message sent in S840 does not include the NR paging eDRX cycle for RRC INACTIVE information element. The N2 message can be used to instruct the session management network element or the user plane network element to release the data cache, or to instruct the access management network element to release the MT communication processing (MT conmunication handling).

[0365] Optionally, the N2 message may include an RRC state Information information element. If the value of the RRC state Information information element is as shown in Table 1, the value of the information element is Inactive with enhanced eDRX. If the value of the RRC state Information information element is as shown in Table 2, the value of the information element is Inactive. In other words, the N2 message sent by S840 can reuse the N2 message sent by S820, and instruct the session management network element or the user plane network element to release the data cache by not carrying the NR paging eDRX cycle for RRC INACTIVE information element in the N2 message sent by S840.

[0366] It should be understood that in this application, the access management network element releases the MT communication processing, including the access management network element releasing the signaling cache, and optionally, may also include the access management network element instructing the session management network element or the user plane network element to release the data cache.

[0367] It should also be understood that releasing data caching can be understood as stopping caching data, or starting downlink data transmission, or data of the terminal device being reachable.

[0368] In one implementation, the N2 message sent in S840 includes seventh information, and the seventh information can be used to instruct the session management network element or the user plane network element to release the data cache.

[0369] The seventh information may be an IE in an existing N2 message indicating that the UE can perform data or signaling transmission, ie, reusing an existing IE, or the seventh information may be a newly introduced IE, such as a buffering suspend IE.

[0370] Furthermore, the access management network element may send instruction information to the session management network element or the user plane network element to instruct the session management network element or the user plane network element to release the data cache.

[0371] Based on the above solution, the access network device can reuse the N2 message to instruct the session management network element or the user plane network element to release the data cache, so that SDT can proceed smoothly.

[0372] Optionally, the method 800 further includes: S850, the access network device sends a paging message to the terminal device, where the paging message includes an MT SDT indication.

[0373] Exemplarily, S850 may be executed after S830.

[0374] Exemplarily, S840 may be performed after S850, for example, after the terminal device completes RACH access or after the access network device receives a random access message 3 (msg 3) from the terminal device.

[0375] Optionally, as an alternative embodiment of the method 800, S830 in the method 800 may be replaced by the access network device determining, according to the first information, to transmit the data of the first QoS flow in a non-SDT manner.

[0376] Specifically, the access network device can determine whether the size of the data of the first QoS flow meets the transmission requirements of SDT based on the first information. For example, the maximum data amount supported by SDT is x. When the size of the data of the first QoS flow is greater than x, the data of the first QoS flow cannot be transmitted via SDT. Therefore, the access network device can determine to transmit the data of the first QoS flow via non-SDT.

[0377] Among them, in this application, "transmission by non-SDT means" means that when the access network device sends a paging message to the terminal device, it does not carry an SDT indication, so that the terminal device enters a connected state according to the paging message and transmits data in the connected state.

[0378] Exemplarily, in this alternative embodiment, the access network device may send a paging message to the terminal device, where the paging message does not include an MT SDT indication, so that the terminal device may enter a connected state to receive data of the first QoS flow.

[0379] Optionally, in this alternative embodiment, the first information may include not only the size of the data of the first QoS flow, but also the size of the data of the second QoS flow.

[0380] The second QoS flow is mapped to a second data radio bearer, which is used for non-SDT of the terminal device. In other words, the first QoS flow is a non-SDT-related QoS flow, or the second QoS flow refers to a QoS flow mapped to a non-SDT DRB.

[0381] Among them, the access network device determines to transmit the data of the first QoS flow in a non-SDT manner based on the first information, which may mean that the access network device determines that there is non-SDT-related QoS flow data in the data to be transmitted, and the access network device sends a paging message, which does not include the MT SDT indication, so that the terminal device can enter the connected state to receive the data of the first QoS flow and the second QoS flow.

[0382] Optionally, in this alternative embodiment, the second information may be used to request the sizes of data of the first QoS flow and the second QoS flow.

[0383] Exemplarily, the second information includes identifiers of the first QoS flow and the second QoS flow.

[0384] In other words, when the access network device makes a request to the access management network element, it may not distinguish between SDT-associated QoS flows and non-SDT-associated QoS flows, so that the access network device can determine whether to transmit data through SDT based on whether the first information only includes SDT-associated QoS flows and the size of the SDT-related QoS flows.

[0385] Based on the above solution, the access management network element can provide the access network device with the data size at the granularity of QoS flow, so that the access network device can determine whether to transmit the data of the QoS flow through SDT or non-SDT. In this way, on the one hand, MT SDT can be supported, which is beneficial to energy saving of terminal devices. On the other hand, it can avoid transmitting unnecessary data size, that is, avoid unnecessary signaling overhead, thereby saving transmission resources.

[0386] Optionally, as an alternative embodiment of the method 800, the second information may be used to request not to report the size of the data of the first QoS flow.

[0387] For example, if the terminal device is reconfigured to a DRB without SDT (for example, after the terminal device re-enters the connected state, or when the INACTIVE configuration of the terminal device is updated), the second information may request to turn off the data size of the first QoS flow, or in other words, to turn off the reporting of the data size at the QoS flow granularity.

[0388] Figure 10 is another schematic flow chart of a method for transmitting small data provided by an embodiment of the present application. As shown in Figure 10, the method 900 includes the following steps.

[0389] S910: The access network device sends third information to the access management network element. Correspondingly, the access management network element receives the third information.

[0390] The third information is used to indicate that the signaling radio bearer 2 (SRB2) configured by the access network device is used for SDT.

[0391] It should be understood that SRB 2 can be configured for SDT (i.e., SRB 2 for SDT), or may not be configured for SDT or may be configured for non-SDT (i.e., SRB 2 for non-SDT). In other words, the third information may indicate whether SRB2 is configured for SDT (indicate whether SRB2 is configured for SDT or not).

[0392] Exemplarily, the third information may be an SDT-SRB2-Indication information element. For example, the information element includes at least one bit of indication information, and different values ​​of the indication information may indicate whether SRB2 is configured for SDT.

[0393] Exemplarily, in the NR system, the third information may be carried in an N2 message, and the N2 message may be a newly defined N2 message, such as an MT communication handling request message.

[0394] Optionally, the N2 message also includes an inactive eDRX cycle of the terminal device.

[0395] For example, the N2 message may include an information element for NR paging eDRX cycle for RRC INACTIVE, which indicates that the reported eDRX cycle is an inactive eDRX cycle.

[0396] Optionally, the N2 message may further include an identifier of a PDU session associated with the first QoS flow (PDU session ID).

[0397] It should be understood that the structure of the N2 message sent in S910 is similar to that of the N2 message sent in S801. For a specific description, reference may be made to S801 and details will not be repeated here.

[0398] Optionally, the SRB2 is used for communication between the access network device and the terminal device.

[0399] Optionally, the terminal device is in an inactive state, and an inactive eDRX cycle of the terminal device is greater than 10.24s.

[0400] For example, before S910, the access management network element or the access network device configures an inactive eDRX for the terminal device, and the configured inactive eDRX period is greater than 10.24s.

[0401] S920: The access management network element sends fourth information to the access network device. Correspondingly, the access network device receives the fourth information.

[0402] The fourth information is used to indicate that the downlink information of the terminal device is control signaling, or in other words, the fourth information is used to indicate that there is downlink control signaling to be sent by the terminal device.

[0403] The control signaling may be a NAS PDU packet.

[0404] For example, when the access management network element determines that there is downlink control signaling to be sent, the access management network element may send fourth information to the access network device.

[0405] Exemplarily, the fourth information can be carried in an N2 message, and the N2 message can be used to trigger RAN paging, such as an N2 message triggered RAN paging (N2 message triggered RAN Paging), or a downlink data notification message (DL Data Notification). After receiving the N2 message, the access network device can perform RAN paging on the terminal device in the RRC_INACTIVE state.

[0406] S930: The access network device determines to transmit the control signaling by means of SDT according to the third information and the fourth information, and the control signaling is transmitted by means of SRB2.

[0407] Specifically, when SRB 2 configured in the access network device is for SDT, if the access network device receives an indication from the access management network element that the downlink information is control signaling, the access network device may determine to transmit the control signaling in SDT.

[0408] Based on the above solution, when SRB 2 configured on the access network device is used for SDT, and there is downlink control signaling to be sent, the access management network element can indicate to the access network device the presence of downlink control signaling from the terminal device, so that the access network device can determine to transmit the control signaling via SDT. This, on the one hand, supports MT SDT, which is beneficial for energy saving of the terminal device. On the other hand, when SRB 2 configured on the access network device is not used for SDT, the access management network element can not send the fourth information, thus avoiding unnecessary signaling overhead and saving transmission resources.

[0409] Optionally, the method 900 further includes: S940, the access network device sends an N2 message to the access management network element, and correspondingly, the access management network element receives the N2 message.

[0410] Optionally, the N2 message is a radio resource control inactive transition report (RRC INACTIVE transition report) message.

[0411] In one implementation, the N2 message sent in S940 does not include the NR paging eDRX cycle for RRC INACTIVE information element. The N2 message can be used to instruct the access management network element to release MT communication handling, or in other words, to instruct the access management network element to release the signaling cache.

[0412] It should be understood that the structure of the N2 message sent in S940 is similar to that of the N2 message sent in S840. For a detailed description, please refer to S840 and will not be repeated here.

[0413] Based on the above solution, the access network device can reuse the N2 message to instruct the access management network element to release the signaling buffer, so that SDT can proceed smoothly.

[0414] Optionally, the method 900 further includes: S950, the access network device sends a paging message to the terminal device, where the paging message includes an MT SDT indication.

[0415] Exemplarily, S950 may be executed after S930.

[0416] Exemplarily, S940 may be performed after S950, for example, after the terminal device completes RACH access, or after the access network device receives msg 3 of a random access from the terminal device.

[0417] Optionally, the fourth information may also include the size of the downlink signaling. Furthermore, in S930, the access network device determines to transmit the control signaling via SDT based on the third information and the fourth information. This may mean that when SRB2 is used for SDT and the size of the downlink signaling meets the transmission requirements of STD (for example, the maximum signaling supported by SDT is y, and the size of the downlink signaling is less than or equal to y), the control signaling can be transmitted via SDT.

[0418] Optionally, as an alternative embodiment of method 900, the third information in method 900 may be replaced by: the third information is used to indicate that the signaling radio bearer SRB2 configured by the access network device is not used for SDT.

[0419] In this alternative embodiment, S930 in method 900 may be replaced by the access network device determining, based on the third information and the fourth information, to transmit the control signaling in a non-SDT manner.

[0420] Specifically, when SRB 2 configured in the access network device is for non-SDT, if the access network device receives an indication from the access management network element that the downlink information is control signaling, the access network device may determine to transmit the control signaling in a non-SDT manner.

[0421] Optionally, as an alternative embodiment of method 900, if the access management network element determines, based on the third information, that SRB 2 configured by the access network device is for non-SDT, the access management network element may not execute S920. Further, when the access management network element determines that there is downlink control signaling to be sent, the access management network element may directly send the downlink control signaling to the access network device, so that when the terminal device is reachable, the access network device pages the terminal device to a connected state and transmits the control signaling to the terminal device in the connected state.

[0422] Figure 11 is another schematic flow chart of a method for transmitting small data provided by an embodiment of the present application. As shown in Figure 11, the method 1000 includes the following steps.

[0423] S1010: Access a management network element to obtain first information.

[0424] The first information includes the size of data of a first quality of service (QoS) flow associated with the terminal device.

[0425] S1010 can refer to S810 and will not be described in detail here.

[0426] S1020: The access management network element determines to transmit data of the first QoS flow by way of SDT according to the first information.

[0427] Specifically, the access management network element can determine whether the size of the data of the first QoS flow meets the transmission requirements of SDT based on the first information. For example, the maximum amount of data supported by SDT is x. When the size of the data of the first QoS flow is less than or equal to x, the data of the first QoS flow can be transmitted via SDT.

[0428] S1030: The access management network element sends fifth information to the access network device. Correspondingly, the access network device receives the fifth information.

[0429] The fifth information is used to instruct the access network device to transmit data of the first QoS flow through SDT.

[0430] Exemplarily, the fifth information may be an SDT indication or a total amount of SDT data (size).

[0431] Exemplarily, the fifth information may be carried in an N2 message, and the N2 message may be used to trigger RAN paging, for example, an N2 message triggered RAN paging (N2 message triggered RAN Paging).

[0432] Based on the above solution, the access management network element can obtain the data size of the QoS flow granularity and determine whether to transmit the data of the QoS flow via SDT. The access management network element can then instruct the access network device to transmit the data of the QoS flow via SDT. This, on the one hand, can support MT SDT, which is beneficial for energy saving of terminal devices, and on the other hand, can avoid the size of the transmitted data, that is, avoid unnecessary signaling overhead, thereby saving transmission resources.

[0433] Optionally, after S1030, the method 1000 further includes: S1040, the access network device sends a paging message to the terminal device, where the paging message includes an MT SDT indication.

[0434] Specifically, according to the indication of the fifth information, the access network device may determine to transmit the data of the first QoS flow by means of SDT, and then the access network device may send a paging message including an MT SDT indication to the terminal device.

[0435] Optionally, as an alternative embodiment of method 1000, S1020 in method 1000 may be replaced by the access management network element determining, based on the first information, to transmit the data of the first QoS flow in a non-SDT manner.

[0436] For example, the maximum data volume supported by SDT is x. When the size of the data of the first QoS flow is greater than x, the data of the first QoS flow cannot be transmitted via SDT. Therefore, the access management network element can determine to transmit the data of the first QoS flow via non-SDT.

[0437] Optionally, in this replacement embodiment, S1030 in method 1000 may be replaced by the access management network element sending the sixth information to the access network device, and correspondingly, the access network device receives the sixth information.

[0438] The sixth information is used to instruct the access network device to transmit downlink data in a non-SDT manner, where the downlink data includes data of the first QoS flow.

[0439] Illustratively, in this alternative embodiment, S1040 in method 1000 may be replaced by the access network device sending a paging message to the terminal device, where the paging message does not include the MT SDT indication.

[0440] Specifically, according to the indication of the sixth information, the access network device can determine to transmit the data of the first QoS flow in a non-SDT manner, and then, the access network device can send a paging message that does not include the MT SDT indication to the terminal device, so that the terminal device can enter the connected state to receive the data of the first QoS flow.

[0441] Optionally, in this alternative embodiment, the first information may include not only the data of the first QoS flow but also the data of the second QoS flow.

[0442] The second QoS flow is mapped to a second data radio bearer, which is used for non-SDT of the terminal device. In other words, the first QoS flow is a non-SDT-related QoS flow, or the second QoS flow refers to a QoS flow mapped to a non-SDT DRB.

[0443] Among them, the access management network element determines that the data of the first QoS flow is transmitted in a non-SDT manner based on the first information, which may mean that the access management network element determines that there is non-SDT-related QoS flow data in the data to be transmitted, thereby determining to transmit the data of the first QoS flow in a non-SDT manner.

[0444] In the case where the first information includes the second QoS flow, the sixth information is used to instruct the access network device to transmit downlink data in a non-SDT manner, where the downlink data includes data of the first QoS flow and data of the second QoS flow.

[0445] The method of the present application is further described below with reference to FIG12 .

[0446] Figure 12 is another schematic flow chart of a method for transmitting small data provided in an embodiment of the present application. The method 1100 shown in Figure 12 can be regarded as a specific implementation of the method 800. As shown in Figure 12, the method 1100 includes the following steps.

[0447] S1101, UE (an example of a terminal device) registers to the network and negotiates with the network for idle DRX and eDRX configuration information, including an idle eDRX cycle.

[0448] S1102: NG-RAN (an example of access network equipment) determines to initiate a communication process of connection inactivation mobile termination based on CN.

[0449] S1103: NG-RAN sends the UE's inactive eDRX configuration to the UE.

[0450] S1101 to S1103 may refer to S301 to S303 and will not be described in detail here.

[0451] S1104: NG-RAN sends the UE's inactive eDRX configuration to AMF (an example of an access management network element) through an N2 message.

[0452] Among them, the inactive eDRX configuration can be used by the AMF to determine the UE reachability.

[0453] The N2 message further includes information #1 (an example of second information), and the information #1 is used to request the data size of QoS flow #1 (an example of first QoS flow).

[0454] Among them, the N2 message may include the NR paging eDRX cycle for RRC INACTIVE information element.

[0455] S1104 can refer to S304 and S801.

[0456] S1105, AMF sends a PDU session update context request message to SMF.

[0457] The PDU session update context request message can instruct the UPF to enable data caching.

[0458] The PDU session update context request message may further include information #1.

[0459] S1106, SMF (an example of session management network element) and UPF (an example of user plane network element) perform N4 session modification process.

[0460] That is, based on the instructions of AMF, SMF can instruct UPF to enable data caching through the N4 session modification request message, and UPF can return the N4 session modification response message to SMF.

[0461] The N4 session modification request message may further include information #1.

[0462] S1107, UPF enables data caching.

[0463] S1108, SMF sends a PDU session update context response message to AMF.

[0464] S1109: AMF sends an N2 response message to NG-RAN.

[0465] S1107 to S1109 can refer to S306 to S309 and will not be repeated here.

[0466] After S1109 (if S1103 is executed after S1109, it is after S1103), the UE is in an inactive state, the inactive eDRX cycle value of the UE is greater than 10.24s, and both the NG-RAN and the AMF store the inactive eDRX cycle value of the UE.

[0467] When UPF receives downlink data, it buffers it and sends the data size to SMF, which then sends it to AMF for statistics. The specific process is as follows:

[0468] S1110, UPF receives downlink data and sends a data notification message to AMF.

[0469] The data notification message may carry the size of the data of the current QoS flow #1.

[0470] S1111, SMF sends an MT enable UE reachability request message to AMF.

[0471] The MT enabling UE reachability request message may carry the size of the data of the current QoS flow #1 sent by the UPF.

[0472] S1110 to S1111 may refer to S401 to S402 .

[0473] S1112, AMF returns an MT enable UE reachability response (MT_EnableUERechability response) message to SMF.

[0474] When there is downlink data, S1110 to S1112 can be executed multiple times, and AMF will receive the size of the data of QoS flow #1 each time. AMF can count the size of the data of QoS flow #1 obtained multiple times to obtain information #2, that is, the total amount of data of QoS flow #1 (an example of the first information).

[0475] Optionally, the MT enabling UE reachability response message includes a timer indicating a data buffering time.

[0476] S1112 can refer to S403 and S810.

[0477] S1113, SMF returns a data notification response to UPF.

[0478] UPF starts the countdown according to the timer time, and when the countdown ends, UPF will discard the cached data.

[0479] S1113 can refer to S404.

[0480] S1114: AMF sends an N2 message to NG-RAN.

[0481] The AMF may send the determined information #2 to the NG-RAN through an N2 message.

[0482] S1114 can refer to S820.

[0483] S1115, NG-RAN determines whether SDT can be performed based on information #2.

[0484] S1115 can refer to S830.

[0485] If SDT is possible, the NG-RAN may execute S1107.

[0486] S1116: NG-RAN sends a paging message to the UE, where the paging message carries an SDT indication.

[0487] S1116 can refer to S850.

[0488] S1117: The UE initiates RACH access.

[0489] Specifically, the UE responds to the paging message and initiates RACH access.

[0490] S1118, N2 message sent by NG-RAN to AMF.

[0491] For example, the N2 message is an RRC INACTIVE transition report message, and the N2 message does not include the NR paging eDRX cycle for RRC INACTIVE information element. According to the N2 message, the AMF can determine that it is necessary to notify the UPF to release the data cache.

[0492] S1118 can refer to S840.

[0493] S1119, AMF sends a PDU session update context request message to SMF, instructing UPF to release the data cache.

[0494] S1120, SMF and UPF perform N4 session modification process.

[0495] That is, SMF can instruct UPF to release data cache through N4 session modification request message based on the instruction of AMF, and UPF can return N4 session modification response message to SMF.

[0496] S1121, SMF sends a PDU session update context response message to AMF.

[0497] This message may carry confirmation information of releasing the data cache.

[0498] S1122: AMF sends an N2 response message to NG-RAN.

[0499] This message may carry confirmation information of releasing the data cache.

[0500] S1123: UPF sends the downlink data to the UE via NG-RAN, i.e., performs SDT.

[0501] S1124, the UE starts the SDT process.

[0502] Optionally, the UE needs to consider other restrictions when starting SDT, for example, the reference signal receiving power (RSRP) of the UE needs to be greater than the start threshold, otherwise, the UE enters the RRC recovery process, as shown in S407 in Figure 4.

[0503] It should be understood that this application is explained using the example of downlink data being cached in a user plane network element (UPF), but downlink data can also be cached in a session management network element (SMF). In this case, the session management network element can send the cached data to the user plane network element, which then sends it to the terminal device through the access network device.

[0504] It should also be understood that the various embodiments provided in this application can be implemented separately. However, in some cases, the various embodiments can also be combined with each other according to the actual application situation and the logical relationship between the embodiments. For example, method 800 and method 900 can be combined so that the downlink data and signaling of the terminal device can be transmitted by means of SDT. Specifically, as a possible implementation, if method 800 and method 900 are combined, S801 and S910 can be executed simultaneously, S820 and S920 can be executed simultaneously, S830 and S930 can be executed simultaneously, S840 and S940 can be executed simultaneously, and S850 and S950 can be executed simultaneously.

[0505] The method-side embodiment of the present application is described in detail above in conjunction with Figures 1 to 12 . The device-side embodiment of the present application will be described in detail below in conjunction with Figures 13 and 14 . It should be understood that the description of the device embodiment corresponds to the description of the method embodiment. Therefore, for portions not described in detail, reference can be made to the aforementioned method embodiment.

[0506] Figure 13 shows a schematic diagram of a communication device 2000 provided in an embodiment of the present application. As shown in Figure 13, the device 2000 includes a transceiver unit 2010 and a processing unit 2020. The transceiver unit 2010 can be used to implement corresponding communication functions and can also be called a communication interface or communication unit. The processing unit 2020 can be used to perform data processing.

[0507] Optionally, the device 2000 also includes a storage unit, which can be used to store instructions and / or data. The processing unit 2020 can read the instructions and / or data in the storage unit so that the device implements the actions of different devices in the aforementioned method embodiments, for example, the actions of an access network device or an access management network element.

[0508] As an example, the apparatus 2000 is used to execute the actions performed by the access network device (such as NG-RAN) in each of the method embodiments above. The apparatus 2000 may include a unit for executing the method performed by the access network device (such as NG-RAN) in each of the method embodiments above.

[0509] At this time, the device 2000 can be a component of an access network device (such as NG-RAN), the transceiver unit 2010 is used to perform the transceiver-related operations of the access network device (such as NG-RAN) in the above method embodiments (such as methods 800, 900, 1000, 1100), and the processing unit 2020 is used to perform the processing-related operations of the access network device (such as NG-RAN) in the above method embodiments (such as methods 800, 900, 1000, 1100).

[0510] The device 2000 can implement the steps or processes performed by the access network device (such as NG-RAN) in the method embodiment according to the embodiment of the present application.

[0511] It should be understood that the specific process of each unit executing the above corresponding steps has been described in detail in the above method embodiments, and for the sake of brevity, it will not be repeated here.

[0512] As an example, the device 2000 is used to execute the actions performed by the access management network element (such as AMF) in the above method embodiments, and the device 2000 may include a unit for executing the method performed by the access management network element (such as AMF) in the above method embodiments.

[0513] At this time, the device 2000 can be an access management network element (such as AMF) and its components, the transceiver unit 2010 is used to perform the transceiver-related operations of the access management network element (such as AMF) in the above method embodiments (such as methods 800, 900, 1000, 1100), and the processing unit 2020 is used to perform the processing-related operations of the access management network element (such as AMF) in the above method embodiments (such as methods 800, 900, 1000, 1100).

[0514] The device 2000 can implement the steps or processes performed by the access management network element (such as AMF) in the method embodiment according to the embodiment of the present application.

[0515] It should be understood that the specific process of each unit executing the above corresponding steps has been described in detail in the above method embodiments, and for the sake of brevity, it will not be repeated here.

[0516] It should also be understood that the apparatus 2000 herein is embodied in the form of a functional unit. The term "unit" herein may refer to an application specific integrated circuit (ASIC), an electronic circuit, a processor (e.g., a shared processor, a dedicated processor, or a group processor, etc.) and / or memory for executing one or more software or firmware programs, incorporating logic circuits, and / or other suitable components that support the described functionality.

[0517] The apparatus 2000 of each of the above-mentioned solutions has the function of implementing the corresponding steps performed by the access network device (such as NG-RAN) in the above-mentioned method, or the apparatus 2000 of each of the above-mentioned solutions has the function of implementing the corresponding steps performed by the access management network element (such as AMF) in the above-mentioned method. The functions can be implemented by hardware, or the corresponding software can be implemented by hardware. The hardware or software includes one or more modules corresponding to the above-mentioned functions; for example, the transceiver unit can be replaced by a transceiver (for example, the sending unit in the transceiver unit can be replaced by a transmitter, and the receiving unit in the transceiver unit can be replaced by a receiver), and other units, such as the processing unit, can be replaced by a processor to respectively perform the sending and receiving operations and related processing operations in each method embodiment.

[0518] In addition, the transceiver unit 2010 may also be a transceiver circuit (for example, may include a receiving circuit and a sending circuit), and the processing unit may be a processing circuit.

[0519] It should be noted that the apparatus 2000 may be a network element or device in the aforementioned embodiments, or may be a chip or chip system, such as a system on chip (SoC). The transceiver unit may be an input / output circuit or a communication interface; the processing unit may be a processor, microprocessor, or integrated circuit integrated on the chip. This is not limited here.

[0520] Figure 14 shows a schematic diagram of another communication device 1100 provided in an embodiment of the present application. As shown in Figure 14, the device 1100 includes a processor 3010 and a transceiver 3030, and the processor 3010 is used to control the transceiver 3030 to receive and / or send signals to execute the methods in the above method embodiments. Optionally, as shown in Figure 14, the device 1100 also includes a memory 3020, and the memory 3020 is used to store computer programs or instructions and / or data. Exemplarily, the processor 3010 can be coupled to the memory 3020, and the processor 3010 is used to execute the computer program or instructions stored in the memory 3020, or read the data stored in the memory 3020, to implement the methods in the above method embodiments.

[0521] Optionally, there are one or more processors 3010.

[0522] Optionally, the memory 3020 is one or more.

[0523] Optionally, the memory 3020 is integrated with the processor 3010 or provided separately.

[0524] Among them, the device 1100 is used to implement the operations performed by the access network device (such as NG-RAN) or the access management network element (such as AMF) in the above method embodiments.

[0525] For example, the processor 3010 is configured to execute a computer program or instruction stored in the memory 3020 to implement the relevant operations performed by the access network device (e.g., NG-RAN) in each of the above method embodiments. For example, the methods performed by the access network device in the embodiments shown in Figures 9, 10, and 11, or the method performed by the NG-RAN in the embodiment shown in Figure 12.

[0526] For another example, the processor 3010 is configured to execute a computer program or instruction stored in the memory 3020 to implement the relevant operations performed by the access management network element (such as AMF) in the above various method embodiments. For example, the method performed by the access management network element in the embodiments shown in Figures 9, 10, and 11, or the method performed by the AMF in the embodiment shown in Figure 12.

[0527] It should be understood that the processor mentioned in the embodiments of the present application may be a central processing unit (CPU), or may be other general-purpose processors, digital signal processors (DSP), application-specific integrated circuits (ASIC), field programmable gate arrays (FPGA) or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc. The general-purpose processor may be a microprocessor or any conventional processor, etc.

[0528] It should also be understood that the memory mentioned in the embodiments of the present application may be a volatile memory and / or a non-volatile memory. Among them, the non-volatile memory may be a read-only memory (ROM), a programmable read-only memory (PROM), an erasable programmable read-only memory (EPROM), an electrically erasable programmable read-only memory (EEPROM), or a flash memory. The volatile memory may be a random access memory (RAM). For example, RAM can be used as an external cache. By way of example and not limitation, RAM includes the following forms: static random access memory (SRAM), dynamic random access memory (DRAM), synchronous dynamic random access memory (SDRAM), double data rate synchronous dynamic random access memory (DDR SDRAM), enhanced synchronous dynamic random access memory (ESDRAM), synchronous link dynamic random access memory (SLDRAM), and direct rambus RAM (DR RAM).

[0529] It should be noted that when the processor is a general-purpose processor, DSP, ASIC, FPGA or other programmable logic device, discrete gate or transistor logic device, discrete hardware component, the memory (storage module) can be integrated into the processor.

[0530] It should also be noted that the memory described herein is intended to comprise, but not be limited to, these and any other suitable types of memory.

[0531] The present application also provides a computer-readable medium having a computer program stored thereon, which implements the functions of any of the above method embodiments when executed by a computer.

[0532] The present application also provides a computer program product, which implements the functions of any of the above method embodiments when executed by a computer.

[0533] The present application also provides a communication system, which includes the access network device and access management network element in the aforementioned embodiment, optionally.

[0534] In the above embodiments, all or part of the embodiments may be implemented by software, hardware, firmware, or any combination thereof. When implemented using software, all or part of the embodiments may be implemented in the form of a computer program product. The computer program product includes one or more computer instructions. When the computer instructions are loaded and executed on a computer, all or part of the processes or functions described in the embodiments of the present application are generated. The computer may be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device. The computer instructions may be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another computer-readable storage medium. For example, the computer instructions may be transmitted from one website, computer, server, or data center to another website, computer, server, or data center via a wired (e.g., coaxial cable, optical fiber, digital subscriber line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.) method. The computer-readable storage medium may be any available medium that a computer can access or a data storage device such as a server or data center that includes one or more available media integrated therein. The available medium may be a magnetic medium (eg, a floppy disk, a hard disk, a magnetic tape), an optical medium (eg, a high-density digital video disc (DVD)), or a semiconductor medium (eg, a solid state disk (SSD)).

[0535] In the embodiments of this application, words such as "exemplary" and "for example" are used to indicate examples, illustrations, or descriptions. Any embodiment or design described in this application as "exemplary" should not be construed as preferred or advantageous over other embodiments or designs. Rather, the use of the word "exemplary" is intended to present concepts in a concrete way.

[0536] It should be understood that references to "embodiments" throughout this specification mean that a particular feature, structure, or characteristic associated with the embodiment is included in at least one embodiment of the present application. Therefore, various embodiments throughout this specification do not necessarily refer to the same embodiment. Furthermore, these particular features, structures, or characteristics may be combined in any suitable manner in one or more embodiments.

[0537] It should be understood that in the various embodiments of the present application, the size of the sequence number of each process does not mean the order of execution, and the execution order of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiment of the present application. The names of all nodes and messages in this application are merely names set by this application for the convenience of description. The names in the actual network may be different. It should not be understood that this application limits the names of various nodes and messages. On the contrary, any name with the same or similar function as the node or message used in this application is regarded as the method or equivalent replacement of this application, and is within the scope of protection of this application.

[0538] It should also be understood that in this application, "when", "if" and "if" all mean that the UE or base station will take corresponding measures under certain objective circumstances. It does not limit the time, and does not require the UE or base station to take judgment actions when implementing it, nor does it mean that there are other limitations.

[0539] It should be noted that in the embodiments of the present application, "pre-setting", "pre-configuration", etc. can be achieved by pre-saving corresponding codes, tables or other methods that can be used to indicate relevant information in a device (for example, a terminal device). This application does not limit its specific implementation method, such as the preset rules, preset constants, etc. in the embodiments of the present application.

[0540] Additionally, the terms "system" and "network" are often used interchangeably herein.

[0541] As used herein, the term "at least one of" or "at least one of" refers to all or any combination of the listed items. For example, "at least one of A, B, and C" can mean: A alone, B alone, C alone, A and B together, B and C together, and A, B, and C together. As used herein, "at least one" means one or more. "A plurality" means two or more.

[0542] It should be understood that in the various embodiments of the present application, "B corresponding to A" means that B is associated with A and can be determined based on A. However, it should also be understood that determining B based on A does not mean determining B solely based on A; B can also be determined based on A and / or other information. The terms "include," "comprising," "having," and their variations all mean "including but not limited to," unless otherwise specifically emphasized.

[0543] It should be understood that in various embodiments of the present application, the first, second, and various numerical numbers are merely distinctions for ease of description and are not intended to limit the scope of the embodiments of the present application.

[0544] Those skilled in the art will appreciate that the units and algorithm steps of each example described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are performed in hardware or software depends on the specific application and design constraints of the technical solution. Professional and technical personnel can use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of this application.

[0545] Those skilled in the art will clearly understand that, for the convenience and brevity of description, the specific working processes of the systems, devices and units described above can refer to the corresponding processes in the aforementioned method embodiments and will not be repeated here.

[0546] In the several embodiments provided in this application, it should be understood that the disclosed systems, devices and methods can be implemented in other ways. For example, the device embodiments described above are merely schematic. For example, the division of the units is merely a logical function division. In actual implementation, there may be other division methods, such as multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be through some interfaces, indirect coupling or communication connection of devices or units, which can be electrical, mechanical or other forms.

[0547] The units described as separate components may or may not be physically separate, and the components shown as units may or may not be physical units, that is, they may be located in one place or distributed across multiple network units. Some or all of these units may be selected to achieve the purpose of this embodiment according to actual needs.

[0548] In addition, each functional unit in each embodiment of the present application may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit.

[0549] If the functions are implemented in the form of software functional units and sold or used as independent products, they can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present application, or the part that contributes to the prior art, or the part of the technical solution, can be embodied in the form of a software product. The computer software product is stored in a storage medium and includes several instructions for enabling a computer device (which can be a personal computer, a server, or a network device, etc.) to execute all or part of the steps of the method described in each embodiment of the present application. The aforementioned storage medium includes various media that can store program codes, such as a USB flash drive, a mobile hard disk, a read-only memory (ROM), a random access memory (RAM), a magnetic disk, or an optical disk.

[0550] The above description is merely a specific embodiment of the present application, but the scope of protection of the present application is not limited thereto. Any changes or substitutions that can be easily conceived by a person skilled in the art within the technical scope disclosed in this application should be included in the scope of protection of this application. Therefore, the scope of protection of this application should be based on the scope of protection of the claims.

Claims

1. A method for transmitting small data, characterized in that: include: Receiving first information from an access management network element, the first information including the size of data of a first quality of service QoS flow associated with the terminal device; Determine, according to the first information, to transmit the data of the first QoS flow in a small data transmission (SDT) manner.

2. The method according to claim 1, characterized in that The method further comprises: A first message is sent to the access management network element, where the first message includes an identifier (PDU session ID) of a protocol data unit session associated with the first QoS flow.

3. The method according to claim 1 or 2, characterized in that: The method further comprises: Sending second information to the access management network element, where the second information is used to request the size of data of the first QoS flow.

4. The method according to any one of claims 1 to 3, characterized in that The first information includes an identifier of the first QoS flow.

5. The method according to any one of claims 1 to 4, characterized in that The terminal device is in an inactive state, and the inactive state extended discontinuous reception eDRX cycle of the terminal device is greater than 10.24 seconds.

6. The method according to any one of claims 1 to 5, characterized in that The method further comprises: An N2 message is sent to the access management network element, where the N2 message does not include a new radio paging eDRX cycle NR Paging eDRX Cycle for RRC INACTIVE information element for the radio resource control inactive state, and the N2 message is used to instruct the session management network element or the user plane network element to release the data cache.

7. The method according to claim 6, characterized in that The N2 message also includes a radio resource control state information RRC state Information cell, the value of the radio resource control state information is Inactive with enhanced eDRX, and the value of the radio resource control state information is used to indicate that the terminal device is in an inactive state and the terminal device is configured with an inactive eDRX cycle greater than 10.24s.

8. The method according to any one of claims 1 to 7, characterized in that The first QoS flow is mapped to a first data radio bearer, and the first data radio bearer is used for the terminal device to perform SDT.

9. A method for transmitting small data, characterized in that: include: Acquire first information, where the first information includes a size of data of a first QoS flow associated with the terminal device; Send the first information to the access network device.

10. The method according to claim 9, characterized in that The method further comprises: A first message is received from the access network device, where the first message includes an identifier (PDU session ID) of a protocol data unit session associated with the first QoS flow.

11. The method according to claim 9 or 10, characterized in that: The method further comprises: Second information is received from the access network device, where the second information is used to request the size of data of the first QoS flow.

12. The method according to any one of claims 9 to 11, characterized in that The first information includes an identifier of the first QoS flow.

13. The method according to any one of claims 9 to 12, characterized in that The terminal device is in an inactive state, and the inactive state extended discontinuous reception eDRX cycle of the terminal device is greater than 10.24 seconds.

14. The method according to any one of claims 9 to 13, characterized in that The method further comprises: receiving an N2 message from the access network device, the N2 message not including a new radio paging eDRX cycle NR Paging eDRX Cycle for RRC INACTIVE information element for a radio resource control inactive state, and the N2 message is used to instruct a session management network element or a user plane network element to release data cache; Sending indication information to the session management network element or the user plane network element, where the indication information is used to instruct the session management network element or the user plane network element to release data cache.

15. The method according to claim 14, characterized in that The N2 message also includes a radio resource control state information RRC state Information cell, the value of the radio resource control state information is Inactive with enhanced eDRX, and the value of the radio resource control state information is used to indicate that the terminal device is in an inactive state and the terminal device is configured with an inactive eDRX cycle greater than 10.24s.

16. The method according to any one of claims 9 to 15, characterized in that The first QoS flow is mapped to a first data radio bearer, and the first data radio bearer is used for the terminal device to perform SDT.

17. A method for transmitting small data, characterized in that: include: receiving fourth information from the access management network element, where the fourth information is used to indicate that the downlink information of the terminal device is control signaling; According to the signaling radio bearer SRB2 configured by the access network device for SDT and the fourth information, it is determined that the control signaling is transmitted by way of SDT, and the control signaling is transmitted using the SRB2.

18. The method according to claim 17, characterized in that The method further comprises: The third information is sent to the access management network element, where the third information is used to indicate that the SRB2 configured by the access network device is used for SDT.

19. The method according to claim 17 or 18, characterized in that The terminal device is in an inactive state, and an extended discontinuous reception eDRX cycle of the terminal device is greater than 10.24 seconds.

20. A method for transmitting small data, characterized in that: include: receiving third information from an access network device, wherein the third information is used to indicate that a signaling radio bearer SRB2 configured by the access network device is used for SDT; Send fourth information to the access network device, where the fourth information is used to indicate that the downlink information of the terminal device is control signaling.

21. The method according to claim 20, characterized in that The terminal device is in an inactive state, and an extended discontinuous reception eDRX cycle of the terminal device is greater than 10.24 seconds.

22. A method for transmitting small data, characterized in that: include: The access management network element obtains first information, where the first information includes the size of data of a first QoS flow associated with the terminal device; The access management network element sends the first information to the access network device; The access network device determines, according to the first information, to transmit the data of the first QoS flow by means of small data transmission (SDT).

23. The method according to claim 22, characterized in that The method further comprises: The access network device sends second information to the access management network element, where the second information is used to request a size of data of the first QoS flow.

24. The method according to claim 22 or 23, characterized in that The method further comprises: The access network device sends an N2 message to the access management network element, the N2 message does not include a new radio paging eDRX cycle NR Paging eDRX Cycle for RRC INACTIVE information element for the radio resource control inactive state, and the N2 message is used to instruct the session management network element or the user plane network element to release the data cache.

25. A method for transmitting small data, characterized in that: include: The access network device sends third information to the access management network element, where the third information is used to indicate that the signaling radio bearer SRB2 configured by the access network device is used for SDT; The access management network element sends fourth information to the access network device, where the fourth information is used to indicate that the downlink information of the terminal device is control signaling; The access network device determines, based on the third information and the fourth information, that the control signaling is transmitted by way of SDT, and the control signaling is transmitted by using the SRB2.

26. A communication device, characterized in that: Comprising a unit for implementing the method as claimed in any one of claims 1 to 8, or comprising a unit for implementing the method as claimed in any one of claims 9 to 16, or comprising a unit for implementing the method as claimed in any one of claims 17 to 19, or comprising a unit for implementing the method as claimed in claim 20 or 21, or comprising a unit for implementing the method as claimed in any one of claims 22 to 24, or comprising a unit for implementing the method as claimed in claim 25.

27. A communication device, characterized in that: include: A processor, wherein the processor is used to execute a computer program so that the apparatus performs the method as claimed in any one of claims 1 to 8, or the apparatus performs the method as claimed in any one of claims 9 to 16, or the apparatus performs the method as claimed in any one of claims 17 to 19, or the apparatus performs the method as claimed in claim 20 or 21, or the apparatus performs the method as claimed in any one of claims 22 to 24, or the apparatus performs the method as claimed in claim 25.

28. A computer-readable storage medium, characterized in that: include: The computer-readable storage medium stores a computer program, which, when executed, enables the computer to execute the method as claimed in any one of claims 1 to 8, or the method as claimed in any one of claims 9 to 16, or the method as claimed in any one of claims 17 to 19, or the method as claimed in claim 20 or 21, or the method as claimed in any one of claims 22 to 24, or the method as claimed in claim 25.

29. A computer program product, characterized in that When the computer program product is executed by a communication device, it implements the method as claimed in any one of claims 1 to 8, or implements the method as claimed in any one of claims 9 to 16, or implements the method as claimed in any one of claims 17 to 19, or implements the method as claimed in claim 20 or 21, or implements the method as claimed in any one of claims 22 to 24, or implements the method as claimed in claim 25.

30. A communication system, characterized in that: The method comprises a first communication device and a second communication device, wherein the first communication device executes the method described in any one of claims 1 to 8, and the second communication device executes the method described in any one of claims 9 to 16, or the first communication device executes the method described in any one of claims 17 to 19, and the second communication device executes the method described in claim 20 or 21.

Citation Information

Patent Citations

  • Small data transmission method and communication device

    CN118945730A

  • Data transmission method and device and storage medium

    CN115190605A

  • Method, system and device for transmitting random downlink packet data and storage medium

    CN115297561A

  • Small data transmission method and related equipment

    CN115315027A

  • Method, device and computer storage medium of communication

    WO2023039732A1

Cited By

  • Terminal data sending method and related equipment

    CN119789243A

  • Communication method and apparatus

    WO2026124341A1

  • Communication method and communication apparatus

    WO2026149076A1