A method of controlling transmission and related apparatus

Abstract

The embodiment of the application provides a method for controlling transmission and a related device, the method comprises the following steps: when a first device is in a non-radio resource control (RRC) connected state, a first network device is sent first information or second information, the first information indicates that small packet data transmission (SDT) is requested to be stopped, the second information indicates that a gap configuration for SDT is requested, or the second information indicates that SDT is requested to be suspended. The embodiment of the application can be applied to the scenario that the first device may not continue SDT, and can avoid the case that the first network device continues to schedule resources for SDT when the first device no longer continues to listen to SDT, thereby saving air interface resources.

Description

TECHNICAL FIELD

[0001] The present application relates to the technical field of communication, and in particular to a method for controlling transmission and related apparatus. BACKGROUND

[0002] A communication protocol stack of a terminal and a network device includes a radio resource control (RRC) layer. Currently, the terminal can transmit small data with the network device without entering an RRC connected (RRC CONNECTED) state, for example, in an RRC idle (RRC IDLE) state or an RRC inactive (RRC INACTIVE) state, and such a process can be referred to as small data transmission (SDT).

[0003] When the terminal and the network device perform SDT, the terminal can fail to continue the SDT, but the network device can still schedule resources for the SDT, which can result in waste of air interface resources, and there is a lack of efficient transmission scheme that can be applied to the above scenario. For example, a multi-card terminal includes a sub-device A and a sub-device B, and the sub-device A and the sub-device B share a radio frequency transmitting chain and / or a radio frequency receiving chain, that is, the sub-device A and the sub-device B cannot simultaneously transmit information and / or receive information. When the sub-device A and the network device perform SDT, if the sub-device B has a data transmission requirement (for example, needs to perform data transmission other than SDT), the sub-device A needs to stop transmission to allow the sub-device B to transmit information, but the network device can still schedule resources for the SDT for the sub-device A. SUMMARY

[0004] Embodiments of the present application disclose a method for controlling transmission and related apparatus, which can avoid the case that the network device continues to schedule resources for small data transmission when the device no longer monitors the small data transmission, thereby saving air interface resources.

[0005] In a first aspect, embodiments of the present application provide a method for controlling transmission, applied to a first device, and the method includes: sending first information to a first network device when in a non-radio resource control (RRC) connected state, the first information indicating a request to stop small data transmission (SDT).

[0006] In some embodiments, the first device sends the first information to the first network device when the first device initiates the SDT under the first network device.

[0007] In the present application, the first device can send the first information to the first network device, and the first information indicates a request to stop the SDT, so as to avoid the case that the first network device still schedules resources for the SDT for the first device when the first device stops monitoring the SDT, thereby saving air interface resources.

[0008] In a possible implementation, the first device is a multi-card terminal, the first device includes a first sub-device and a second sub-device, the first sub-device and the second sub-device share a radio frequency sending chain and / or a radio frequency receiving chain, and the sending of the first information to the first network device includes: sending the first information to the first network device by the first sub-device; and the first information indicates that the first sub-device requests to stop the SDT, or the first information indicates that the SDT of the first sub-device is requested to be stopped.

[0009] In a possible implementation, the sending of the first information to the first network device includes: when the second sub-device needs to enter an RRC connected state from a non-RRC connected state, the first information is sent to the first network device by the first sub-device; or the sending of the first information to the first network device includes: when the first device needs to switch from SDT service to RRC connected state service, the first information is sent to the first network device; or the sending of the first information to the first network device includes: the first information is sent to the first network device due to a multi-card reason.

[0010] In a possible implementation, the first device is a first sub-device included in a multi-card terminal, the multi-card terminal further includes a second sub-device, the first sub-device and the second sub-device share a radio frequency sending chain and / or a radio frequency receiving chain, the first information indicates that the first device requests to stop the SDT, or the first information indicates that the SDT of the first device is requested to be stopped.

[0011] In a possible implementation, the sending of the first information to the first network device includes: when the second sub-device needs to enter an RRC connected state from a non-RRC connected state, the first information is sent to the first network device; or the sending of the first information to the first network device includes: when the multi-card terminal needs to switch from SDT service to RRC connected state service, the first information is sent to the first network device; or the sending of the first information to the first network device includes: the first information is sent to the first network device due to a multi-card reason.

[0012] In this application, the first information can be applied to various scenarios of a multi-card terminal, and the application scenarios are wide and the product usability is high.

[0013] In a possible implementation, the first sub-device is in an RRC inactive state; and the method further includes: starting a first timer by the first sub-device when the first information is sent to the first network device; and the method further includes: stopping the first timer by the first sub-device if the first response message sent by the first network device is received before the first timer expires; and entering an RRC idle state by the first sub-device if the first response message sent by the first network device is not received when the first timer expires.

[0014] In a possible implementation, the method further includes: receiving first configuration information by the first sub-device before the first information is sent to the first network device, the first configuration information indicating reporting of the first information, and the receiving of the first configuration information by the first sub-device includes: receiving the first configuration information sent by the first network device through broadcast system information by the first sub-device; or, the receiving of the first configuration information by the first sub-device includes: receiving the first configuration information sent by the first network device through an RRC message by the first sub-device; or, the receiving of the first configuration information by the first sub-device includes: receiving the first configuration information sent by a second network device through an RRC message by the first sub-device, the second network device being an anchor device storing a user context of the first sub-device, and the first network device not storing the user context of the first sub-device; the first configuration information includes a time length of the first timer; or, the method further includes: receiving the time length of the first timer sent by the first network device through broadcast system information by the first sub-device; or, the method further includes: receiving the time length of the first timer sent by the first network device through an RRC message by the first sub-device; or, the method further includes: receiving the time length of the first timer sent by the second network device through an RRC message by the first sub-device, the second network device being an anchor device storing a user context of the first sub-device, and the first network device not storing the user context of the first sub-device; or, the time length of the first timer is predefined; and the first timer is used for listening to a response message of the first information by the first sub-device.

[0015] In this application, the first sub-device is configured with the first configuration information and / or the first timer in various ways, which can be used in different ways based on specific scenarios, and the application scenarios are wide and the use is more flexible.

[0016] In a possible implementation, before the first configuration information is received by the first sub-device, the method further includes: sending, by the first sub-device, a first request message, the first request message indicating a request for configuring reporting of the first information.

[0017] In the present application, the first device can first request configuration of reporting of the first information, and the network device receiving the request configures reporting of the first information for the first device, thereby avoiding resource waste caused by additional configuration when the first device does not need to configure reporting of the first information, and reducing unnecessary signaling overhead.

[0018] In a possible implementation, the first response message is an RRC release message.

[0019] In a possible implementation, the first information is sent by an RRC message carried by a dedicated control channel DCCH.

[0020] In a second aspect, an embodiment of the present application provides another method for controlling transmission, applied to a first network device, and the method includes: receiving first information sent by a first device, the first information indicating a request for stopping SDT.

[0021] In some embodiments, the first device is in a non-RRC connected state, and in some embodiments, the first device initiates SDT under the first network device.

[0022] In the present application, the first device can send first information to the first network device, and indicate a request for stopping SDT through the first information, so as to avoid the first network device still scheduling resources for the SDT for the first device when the first device stops listening to the SDT, thereby saving air interface resources.

[0023] In a possible implementation, the first device is a multi-card terminal, the first device includes a first sub-device and a second sub-device, the first sub-device and the second sub-device share a radio frequency sending chain and / or a radio frequency receiving chain, and the receiving of the first information sent by the first device includes: receiving the first information sent by the first sub-device; wherein: the first information indicates that the first sub-device requests to stop the SDT; or the first information indicates a request for stopping the SDT of the first sub-device.

[0024] In a possible implementation, the first information is sent by the first sub-device to the first network device when the second sub-device needs to enter an RRC connected state from a non-RRC connected state; or the first information is sent by the first device to the first network device when the first device needs to switch from an SDT service to an RRC connected state service; or the first information is sent by the first device to the first network device due to a multi-card reason.

[0025] In a possible implementation, the first device is a first sub-device included in a multi-card terminal, the multi-card terminal further includes a second sub-device, and the first sub-device and the second sub-device share a radio frequency sending chain and / or a radio frequency receiving chain; the first information indicates that the first device requests to stop the SDT; or the first information indicates that the first device requests to stop the SDT.

[0026] In a possible implementation, the first information is sent by the first device to the first network device when the second sub-device needs to enter an RRC connected state from a non-RRC connected state; or the first information is sent by the first device to the first network device when the multi-card terminal needs to switch from an SDT service to an RRC connected state service; or the first information is sent by the first device to the first network device due to a multi-card reason.

[0027] In this application, the first information can be applied to various scenarios of the multi-card terminal, and the application scenarios are wide and the product usability is high.

[0028] In a possible implementation, before receiving the first information sent by the first device, the method further includes: sending first configuration information to the first sub-device, and / or sending a time length of a first timer to the first sub-device, the first configuration information indicating reporting of the first information, and the first timer being used for the first sub-device to listen to a response message of the first information, where: the sending of the first configuration information to the first sub-device includes sending the first configuration information to the first sub-device through broadcast system information; or the sending of the first configuration information to the first sub-device includes sending the first configuration information to the first sub-device through an RRC message; the first configuration information includes the time length of the first timer; or the sending of the time length of the first timer to the first sub-device includes sending the time length of the first timer to the first sub-device through broadcast system information; or the sending of the time length of the first timer to the first sub-device includes sending the time length of the first timer to the first sub-device through an RRC message; or the time length of the first timer is predefined.

[0029] In this application, the first configuration information and / or the first timer configured for the first sub-device have various modes, different modes can be used based on specific scenarios, the application scenarios are wide, and the use is more flexible.

[0030] In a possible implementation, after receiving the first information sent by the first device, the method further includes: sending a first response message to the first sub-device before a timeout of the first timer.

[0031] In a possible implementation, the first network device does not store the user context of the first sub-device; after receiving the first information sent by the first device, the method further includes: sending a first message to a second network device, the first message including the first information, the second network device being an anchor device storing the user context of the first sub-device.

[0032] In a possible implementation, the method further includes: receiving a second message sent by a second network device, the second message including a first response message, the second network device being an anchor device storing the user context of the first sub-device, the second message being used for the first network device to send the first response message to the first sub-device.

[0033] In a possible implementation, after receiving the first information sent by the first device, the method further includes: receiving a third message sent by a second network device, the second network device being an anchor device storing the user context of the first sub-device, the user context of the first sub-device including a time length of a first timer, the third message including the time length of the first timer, the time length of the first timer being used for the first network device to send a first response message to the first sub-device before the first timer expires.

[0034] In some embodiments, the second message and the third message are the same. In other embodiments, the second message and the third message are different.

[0035] In a possible implementation, before receiving the second message sent by the second network device, the method further includes: sending a fourth message to the second network device, the fourth message including a time length of a first timer, the time length of the first timer being generated by the first network device, the time length of the first timer being used for the second network device to send the second message to the first network device.

[0036] In a possible implementation, before receiving the first information sent by the first device, the method further includes: receiving a fifth message sent by a second network device, the second network device being an anchor device storing the user context of the first sub-device, the fifth message including a time length of a first timer, the time length of the first timer being used for the first network device to send a first response message to the first sub-device before the first timer expires.

[0037] In this application, there are various ways to transmit the time length of the first timer between the first network device and the second network device, different ways can be used based on specific scenarios, and the application scenarios are wide and the use is more flexible.

[0038] In a possible implementation, before the first configuration information is sent to the first sub-device, the method further includes: receiving a first request message sent by the first sub-device, the first request message indicating that reporting of the first information is requested.

[0039] In the application, the first device can first request reporting of the first information, and the network device receiving the request configures the first information for the first device, thereby avoiding resource waste caused by additional configuration of the first information when the first device does not need to be configured with the first information, and reducing unnecessary signaling overhead.

[0040] In a possible implementation, the first response message is an RRC release message.

[0041] In a possible implementation, the first information is sent by an RRC message carried by a dedicated control channel DCCH.

[0042] In a third aspect, an embodiment of the application provides another method for controlling transmission, applied to a second network device, and the method includes: receiving a first message sent by a first network device, the first message including first information, the first information indicating that a first device requests to stop SDT, and the first network device not storing a user context of the first device, and the second network device being an anchor device storing the user context of the first device.

[0043] In some embodiments, the first information is sent by the first device to the first network device, optionally, sent by the first device when the first device is in an RRC non-connected state, and optionally, sent by the first device when the first device initiates SDT under the first network device.

[0044] In the application, the first device can send the first information to the first network device, and indicate a request to stop SDT through the first information, so as to avoid the first network device still scheduling resources for the SDT for the first device when the first device stops monitoring the SDT, thereby saving air interface resources.

[0045] In a possible implementation, the first device is a multi-card terminal, the first device includes a first sub-device and a second sub-device, the first sub-device and the second sub-device share a radio frequency sending chain and / or a radio frequency receiving chain, the first network device does not store a user context of the first device, including that the first network device does not store a user context of the first sub-device, and the second network device is an anchor device storing the user context of the first device, including that the second network device is an anchor device storing the user context of the first sub-device, the first information indicates that the first sub-device requests to stop the SDT, or the first information indicates a request to stop the SDT of the first sub-device.

[0046] In a possible implementation, the first information is sent by the first sub-device to the first network device when the second sub-device needs to enter an RRC connected state from a non-RRC connected state, or the first information is sent by the first device to the first network device when the first device needs to switch from SDT service to RRC connected state service, or the first information is sent by the first device to the first network device due to a multi-card reason.

[0047] In a possible implementation, the first device is a first sub-device included in a multi-card terminal, the multi-card terminal further includes a second sub-device, and the first sub-device and the second sub-device share a radio frequency sending chain and / or a radio frequency receiving chain; the first information indicates that the first device requests to stop the SDT, or the first information indicates that the SDT of the first device is requested to be stopped.

[0048] In a possible implementation, the first information is sent by the first device to the first network device when the second sub-device needs to enter an RRC connected state from a non-RRC connected state, or the first information is sent by the first device to the first network device when the multi-card terminal needs to switch from SDT service to RRC connected state service, or the first information is sent by the first device to the first network device due to a multi-card reason.

[0049] In this application, the first information can be applied to various scenarios of a multi-card terminal, and the application scenarios are wide and the product usability is high.

[0050] In a possible implementation, before receiving the first message sent by the first network device, the method further includes: sending first configuration information to the first sub-device through an RRC message, and / or sending a time length of a first timer to the first sub-device through an RRC message, the first configuration information indicating reporting of the first information, and the first timer being used for the first sub-device to listen to a response message of the first information; the first configuration information includes the time length of the first timer; or the time length of the first timer is predefined.

[0051] In this application, the first configuration information and / or the first timer configured for the first sub-device can be in various ways, and different ways can be used based on specific scenarios, so that the application scenarios are wide and the use is more flexible.

[0052] In a possible implementation, the method further includes: sending a second message to the first network device, the second message including a first response message, and the second message being used for the first network device to send the first response message to the first sub-device.

[0053] In a possible implementation, the method further includes: sending, to the first network device, a third message, where the third message includes a time length of a first timer, and the time length of the first timer is used by the first network device to send a first response message to the first sub-device before the first timer expires.

[0054] In some embodiments, the second message and the third message are the same. In other embodiments, the second message and the third message are different.

[0055] In a possible implementation, before the sending of the second message to the first network device, the method further includes: receiving a fourth message sent by the first network device, where the fourth message includes a time length of a first timer, the time length of the first timer is generated by the first network device, and the time length of the first timer is used by the second network device to send the second message to the first network device.

[0056] In a possible implementation, the method further includes: sending, to the first network device, a fifth message, where the fifth message includes a time length of a first timer, the fifth message is received by the first network device before the first network device receives the first information sent by the first sub-device, and the time length of the first timer is used by the first network device to send a first response message to the first sub-device before the first timer expires.

[0057] In this application, there are various ways to transmit the time length of the first timer between the first network device and the second network device, and different ways can be used based on specific scenarios. The application scenarios are wide, and the use is more flexible.

[0058] In a possible implementation, the first response message is an RRC release message.

[0059] In a possible implementation, the first information is sent by an RRC message carried by a dedicated control channel DCCH.

[0060] In a fourth aspect, an embodiment of the present application provides another method for controlling transmission, applied to a first device, and the method includes: when in an RRC non-connected state, sending second information to a first network device, where the second information indicates a request for a gap configuration for SDT, or the second information indicates a request for suspension of SDT.

[0061] In some embodiments, the first device sends the second information to the first network device in a case where the first device initiates SDT under the first network device.

[0062] In the present application, the first device can send second information to the first network device, and the second information indicates a request for suspending the SDT or a request for the gap configuration for the SDT, so as to avoid that the first network device still schedules resources for the SDT for the first device when the first device stops monitoring the SDT, and save air interface resources.

[0063] In a possible implementation, the first device is a multi-card terminal, and the first device includes a first sub-device and a second sub-device, and the first sub-device and the second sub-device share a radio frequency transmitting chain and / or a radio frequency receiving chain. The sending of the second information to the first network device includes: sending the second information to the first network device by the first sub-device. The second information indicates that the first sub-device requests the gap configuration for the SDT, or the second information indicates that the first sub-device requests the gap configuration for the SDT, or the second information indicates that the first sub-device requests to suspend the SDT, or the second information indicates that the first sub-device requests to suspend the SDT.

[0064] In a possible implementation, the sending of the second information to the first network device includes: when the second sub-device needs to send a system information request or receive a downlink message, the first sub-device sends the second information to the first network device, or the sending of the second information to the first network device includes: when the first device needs to switch from the SDT service to a service of sending a system information request or receiving a downlink message, the first device sends the second information to the first network device, or the sending of the second information to the first network device includes: the second information is sent to the first network device due to a multi-card reason.

[0065] In a possible implementation, the first device is a first sub-device included in a multi-card terminal, and the multi-card terminal further includes a second sub-device, and the first sub-device and the second sub-device share a radio frequency transmitting chain and / or a radio frequency receiving chain. The second information indicates that the first device requests the gap configuration for the SDT, or the second information indicates that the first device requests the gap configuration for the SDT, or the second information indicates that the first device requests to suspend the SDT, or the second information indicates that the first device requests to suspend the SDT.

[0066] In a possible implementation, the sending of the second information to the first network device comprises: sending the second information to the first network device when the second sub-device needs to send a system information request or receive a downlink message; or the sending of the second information to the first network device comprises: sending the second information to the first network device when the multi-card terminal needs to switch from an SDT service to a service of sending a system information request or receiving a downlink message; or the sending of the second information to the first network device comprises: sending the second information to the first network device due to a multi-card reason.

[0067] In the application, the first information can be applied to multiple scenarios of the multi-card terminal, and the application scenarios are wide and the product usability is high.

[0068] In a possible implementation, the first sub-device is in an RRC inactive state; the method further comprises: starting a second timer by the first sub-device when the second information is sent to the first network device; and the method further comprises: stopping the second timer by the first sub-device if a second response message sent by the first network device is received before the second timer expires, and processing the SDT by the first sub-device based on the second response message.

[0069] In a possible implementation, the second response message comprises third information, and the third information is used to indicate the gap configuration; and the processing of the SDT by the first sub-device based on the second response message comprises: stopping listening to the SDT by the first sub-device in a time period indicated by the gap configuration, and performing the SDT by the first sub-device in a time period outside the time period indicated by the gap configuration and the first network device.

[0070] In the application, the first device can not stop the current SDT, and the SDT can be continued when the SDT can be performed, so that the signaling overhead is reduced and the transmission efficiency is higher.

[0071] In a possible implementation, before the sending of the second information to the first network device, the method further includes: receiving, by the first sub-device, second configuration information, the second configuration information indicating reporting of the second information, wherein: the receiving, by the first sub-device, of the second configuration information includes: receiving, by the first sub-device, the second configuration information sent by the first network device through broadcast system information; or, the receiving, by the first sub-device, of the second configuration information includes: receiving, by the first sub-device, the second configuration information sent by the first network device through an RRC message; or, the receiving, by the first sub-device, of the second configuration information includes: receiving, by the first sub-device, the second configuration information sent by a second network device through an RRC message, the second network device being an anchor device storing a user context of the first sub-device, and the first network device not storing the user context of the first sub-device; the second configuration information includes a time length of a second timer; or, the method further includes: receiving, by the first sub-device, the time length of the second timer sent by the first network device through broadcast system information; or, the method further includes: receiving, by the first sub-device, the time length of the second timer sent by the first network device through an RRC message; or, the method further includes: receiving, by the first sub-device, the time length of the second timer sent by a second network device through an RRC message, the second network device being an anchor device storing a user context of the first sub-device, and the first network device not storing the user context of the first sub-device; or, the time length of the second timer is predefined; wherein the second timer is used for the first sub-device to listen to a response message of the second information.

[0072] In the present application, the first sub-device is configured with the second configuration information and / or the second timer in various ways, which can be used in different ways based on specific scenarios, and the application scenarios are wide and the use is more flexible.

[0073] In a possible implementation, before the receiving of the second configuration information by the first sub-device, the method further includes: sending, by the first sub-device, a second request message, the second request message indicating a request for configuration of reporting of the second information.

[0074] In the present application, the first device can first request configuration of reporting of the second information, and the network device receiving the request configures reporting of the second information for the first device, thereby avoiding resource waste caused by additional configuration when the first device does not need to configure reporting of the second information, and reducing unnecessary signaling overhead.

[0075] In a possible implementation, the second response message is an RRC reconfiguration message.

[0076] In a possible implementation, the second information is an RRC message sent through a dedicated control channel DCCH.

[0077] In a fifth aspect, an embodiment of the present application provides another method for controlling transmission, applied to a first network device, the method comprising: receiving second information sent by a first device, the second information indicating that a gap configuration for SDT is requested, or the second information indicating that SDT is requested to be suspended.

[0078] In some embodiments, the first device is in an RRC non-connected state, and in some embodiments, the first device initiates SDT under the first network device.

[0079] In the present application, the first device can send second information to the first network device, and the second information indicates that SDT is requested to be suspended or a gap configuration for SDT is requested, so as to avoid the first network device still scheduling resources for the SDT for the first device when the first device stops monitoring the SDT, and save air interface resources.

[0080] In a possible implementation, the first device is a multi-card terminal, the first device comprises a first sub-device and a second sub-device, the first sub-device and the second sub-device share a radio frequency sending chain and / or a radio frequency receiving chain, and the receiving of the second information sent by the first device comprises: receiving the second information sent by the first sub-device; wherein: the second information indicates that the first sub-device requests the gap configuration for the SDT; or, the second information indicates that the gap configuration for the SDT of the first sub-device is requested; or, the second information indicates that the first sub-device requests to suspend the SDT; or, the second information indicates that the SDT of the first sub-device is requested to be suspended.

[0081] In a possible implementation, the second information is sent by the first sub-device to the first network device when the second sub-device needs to send a system information request or receive a downlink message; or, the second information is sent by the first device to the first network device when the first device needs to switch from SDT service to a service of sending a system information request or receiving a downlink message; or, the second information is sent by the first device to the first network device due to multi-card reasons.

[0082] In a possible implementation, the first device is a first sub-device included in a multi-card terminal, the multi-card terminal further includes a second sub-device, and the first sub-device and the second sub-device share a radio frequency sending chain and / or a radio frequency receiving chain; the second information indicates that the first device requests the gap configuration for the SDT; or, the second information indicates that the gap configuration for the SDT of the first device is requested; or, the second information indicates that the first device requests to suspend the SDT; or, the second information indicates that the SDT of the first device is requested to be suspended.

[0083] In a possible implementation, the second information is sent by the first device to the first network device when the second sub-device needs to send a system information request or receive a downlink message; or, the second information is sent by the first device to the first network device when the multi-card terminal needs to switch from an SDT service to a service of sending a system information request or receiving a downlink message; or, the second information is sent by the first device to the first network device due to a multi-card reason.

[0084] In the application, the first information can be applied to various scenarios of the multi-card terminal, and the application scenarios are wide and the product usability is high.

[0085] In a possible implementation, before receiving the second information sent by the first device, the method further includes: sending second configuration information to the first sub-device, and / or sending a time length of a second timer to the first sub-device, the second configuration information indicating reporting of the second information, and the second timer being used for the first sub-device to listen to a response message of the second information, where: the sending of the second configuration information to the first sub-device includes: sending the second configuration information to the first sub-device through broadcast system information; or, the sending of the second configuration information to the first sub-device includes: sending the second configuration information to the first sub-device through an RRC message; the second configuration information includes the time length of the second timer; or, the sending of the time length of the second timer to the first sub-device includes: sending the time length of the second timer to the first sub-device through broadcast system information; or, the sending of the time length of the second timer to the first sub-device includes: sending the time length of the second timer to the first sub-device through an RRC message; or, the time length of the second timer is predefined.

[0086] In the application, the second configuration information and / or the second timer configured for the first sub-device can be configured in various ways, and different ways can be used based on specific scenarios, the application scenarios are wide, and the use is more flexible.

[0087] In a possible implementation, after receiving the second information sent by the first device, the method further includes: sending a second response message to the first sub-device before the second timer expires, the second response message being used for the first sub-device to process the SDT.

[0088] In a possible implementation, the second response message includes third information, the third information being used to indicate the gap configuration, the gap configuration being used to indicate a period of stopping monitoring the SDT.

[0089] In the present application, the first device can not stop the current SDT, and the SDT can be continued when the SDT can be performed, for example, stopping monitoring the SDT in the period indicated by the gap configuration, continuing the SDT outside the period indicated by the gap configuration, reducing signaling overhead, and being more efficient in transmission.

[0090] In a possible implementation, after receiving the second information sent by the first device, the method further includes: sending a sixth message to a second network device, the sixth message including the second information, the second network device being an anchor device storing a user context of the first sub-device; receiving a seventh message sent by the second network device, the seventh message including a second response message, the second response message being a response message of the second information, the seventh message being used for the first network device to send the second response message to the first sub-device.

[0091] In a possible implementation, after receiving the second information sent by the first device, the method further includes: receiving an eighth message sent by a second network device, the second network device being an anchor device storing a user context of the first sub-device, the user context of the first sub-device including a time length of a second timer, the eighth message including the time length of the second timer, the time length of the second timer being used for the first network device to send a second response message to the first sub-device before the second timer expires, the second response message being a response message of the second information.

[0092] In some embodiments, the seventh message and the eighth message are the same. In other embodiments, the seventh message and the eighth message are different.

[0093] In a possible implementation, before the receiving the seventh message sent by the second network device, the method further includes: sending a ninth message to the second network device, the ninth message including a time length of a second timer, the time length of the second timer being generated by the first network device, the time length of the second timer being used for the second network device to send the seventh message to the first network device, the seventh message being used for the first network device to send the second response message to the first sub-device before the second timer expires.

[0094] In a possible implementation, before the receiving the second information sent by the first device, the method further includes: receiving a tenth message sent by a second network device, the second network device being an anchor device storing a user context of the first sub-device, the tenth message including a time length of a second timer, the time length of the second timer being used for the first network device to send a second response message to the first sub-device before the second timer expires, the second response message being a response message of the second information.

[0095] In this application, the way of transmitting the time length of the second timer between the first network device and the second network device is various, different ways can be used based on specific scenarios, and the application scenarios are wide and the use is more flexible.

[0096] In a possible implementation, the second response message includes third information used to indicate the gap configuration, wherein: the third information is generated by the second network device based on the second information and the time length of the second timer, the time length of the second timer being used for the first network device to send the second response message to the first sub-device before the second timer expires; or, after the sending the sixth message to the second network device, the method further includes: receiving an eleventh message sent by the second network device, the eleventh message including the second information; generating the third information based on the second information in the eleventh message; sending a twelfth message to the second network device, the twelfth message including the third information.

[0097] In this application, the third information indicating the gap configuration can be generated by the second network device or the first network device, different ways can be used based on specific scenarios, and the use is more flexible.

[0098] In a possible implementation, before the sending the second configuration information to the first sub-device, the method further includes: receiving a second request message sent by the first sub-device, the second request message indicating a request to configure the reporting of the second information.

[0099] In the present application, the first device can first request configuration of reporting of the second information, and the network device receiving the request configures reporting of the second information for the first device, thereby avoiding resource waste caused by additional configuration when the first device does not need to configure reporting of the second information, and reducing unnecessary signaling overhead.

[0100] In a possible implementation, the second response message is an RRC reconfiguration message.

[0101] In a possible implementation, the second information is sent through an RRC message carried by a dedicated control channel DCCH.

[0102] In a sixth aspect, an embodiment of the present application provides another method for controlling transmission, applied to a second network device, and the method comprises the following steps.

[0103] In some embodiments, the second information is sent by the first device to the first network device, optionally, sent by the first device when the first device is in an RRC non-connected state, and optionally, sent by the first device when the first device initiates SDT under the first network device.

[0104] In the present application, the first device can send the second information to the first network device, and indicate the request for suspending SDT or the request for gap configuration for SDT through the second information, so as to avoid the first network device still scheduling resources for the SDT for the first device when the first device stops monitoring the SDT, and save air interface resources.

[0105] In a possible implementation, the first device is a multi-card terminal, the first device comprises a first sub-device and a second sub-device, the first sub-device and the second sub-device share a radio frequency sending chain and / or a radio frequency receiving chain, the first network device does not store user context of the first device, and the second network device is an anchor device storing user context of the first device. The second information indicates that the first sub-device requests the gap configuration for the SDT, or indicates the request for the gap configuration for the SDT of the first sub-device, or indicates that the first sub-device requests suspension of the SDT, or indicates the request for suspension of the SDT of the first sub-device.

[0106] In a possible implementation, the second information is sent by the first device to the first network device when the second sub-device needs to send a system information request or receive a downlink message; or, the second information is sent by the first device to the first network device when the multi-card terminal needs to switch from an SDT service to a service of sending a system information request or receiving a downlink message; or, the second information is sent by the first device to the first network device due to a multi-card reason.

[0107] In a possible implementation, the first device is a first sub-device included in a multi-card terminal, the multi-card terminal further includes a second sub-device, and the first sub-device and the second sub-device share a radio frequency sending chain and / or a radio frequency receiving chain; the second information indicates that the first device requests the gap configuration for the SDT; or, the second information indicates that the gap configuration for the SDT of the first device is requested; or, the second information indicates that the first device requests to suspend the SDT; or, the second information indicates that the SDT of the first device is requested to be suspended.

[0108] In a possible implementation, the second information is sent by the first device to the first network device when the second sub-device needs to send a system information request or receive a downlink message; or, the second information is sent by the first device to the first network device when the multi-card terminal needs to switch from an SDT service to a service of sending a system information request or receiving a downlink message; or, the second information is sent by the first device to the first network device due to a multi-card reason.

[0109] In the present application, the first information can be applied to various scenarios of a multi-card terminal, and has wide application scenarios and high product usability.

[0110] In a possible implementation, before receiving the sixth message sent by the first network device, the method further includes: sending second configuration information to the first sub-device through an RRC message, and / or sending a time length of a second timer to the first sub-device through an RRC message, the second configuration information indicating reporting of the second information, and the second timer being used for the first sub-device to listen to a response message of the second information; the second configuration information includes the time length of the second timer; or, the time length of the second timer is predefined.

[0111] In the present application, the second configuration information and / or the second timer configured for the first sub-device can be configured in various ways, and different ways can be used based on specific scenarios, so that the application scenarios are wide and the use is more flexible.

[0112] In a possible implementation, after receiving the sixth message sent by the first network device, the method further includes: generating a second response message based on a time length of a second timer, the second response message being a response message of the second information; and sending a seventh message to the first network device, the seventh message including the second response message, the seventh message being used for the first network device to send the second response message to the first sub-device before the second timer expires.

[0113] In a possible implementation, the user context of the first sub-device stored by the second network device includes a time length of a second timer; and the method further includes: sending an eighth message to the first network device, the eighth message including the time length of the second timer, the time length of the second timer being used for the first network device to send a second response message to the first sub-device before the second timer expires, the second response message being a response message of the second information.

[0114] In some embodiments, the seventh message and the eighth message are the same. In other embodiments, the seventh message and the eighth message are different.

[0115] In a possible implementation, before sending the seventh message to the first network device, the method further includes: receiving a ninth message sent by the first network device, the ninth message including a time length of a second timer, the time length of the second timer being generated by the first network device, the time length of the second timer being used for the second network device to send the seventh message to the first network device.

[0116] In a possible implementation, the method further includes: sending a tenth message to the first network device, the tenth message including a time length of a second timer, the tenth message being received by the first network device before the first network device receives the first information sent by the first sub-device, the time length of the second timer being used for the first network device to send a second response message to the first sub-device before the second timer expires, the second response message being a response message of the second information.

[0117] In this application, there are various ways to transmit the time length of the second timer between the first network device and the second network device, and different ways can be used based on specific scenarios. The application scenarios are wide and the use is more flexible.

[0118] In a possible implementation, the second response message includes third information, the third information being used to indicate the gap configuration, the gap configuration being used to indicate a period of stopping monitoring the SDT.

[0119] In the present application, the first device can not stop the current SDT, and continue the SDT when the SDT can be performed, for example, stop listening to the SDT in the period indicated by the gap configuration, and continue the SDT outside the period indicated by the gap configuration, thereby reducing signaling overhead and improving transmission efficiency.

[0120] In a possible implementation, the second response message includes third information, and the third information is used to indicate the gap configuration; wherein: the third information is generated by the second network device based on the second information and the length of the second timer; or, after receiving the sixth message sent by the first network device, the method further includes: sending an eleventh message to the first network device, the eleventh message including the second information, and the second information in the eleventh message is used by the first network device to generate the third information; and receiving a twelfth message sent by the first network device, the twelfth message including the third information.

[0121] In the present application, the third information indicating the gap configuration can be generated by the second network device or the first network device, and different ways can be used based on specific scenarios, which is more flexible.

[0122] In a possible implementation, the second response message is an RRC reconfiguration message.

[0123] In a possible implementation, the second information is sent by an RRC message carried by a dedicated control channel DCCH.

[0124] In a seventh aspect, the embodiments of the present application provide another method for controlling transmission, applied to a first communication system including a first device and a first network device, and the method includes: when the first device is in an RRC non-connected state, sending indication information to the first network device, the indication information indicating to stop listening to SDT.

[0125] In a possible implementation, the indication information is the first information in the method for controlling transmission provided by the first aspect to the third aspect and any one of the implementation manners of the first aspect to the third aspect of the embodiments of the present application, the first device is configured to execute the method for controlling transmission provided by the first aspect and any one of the implementation manners of the first aspect of the embodiments of the present application, and the first network device is configured to execute the method for controlling transmission provided by the second aspect and any one of the implementation manners of the second aspect of the embodiments of the present application.

[0126] In some embodiments, the first communication system further includes a second network device configured to execute the method for controlling transmission provided by the third aspect and any one of the implementation manners of the third aspect of the embodiments of the present application.

[0127] In a possible implementation, the indication information is the second information in the method for controlling transmission provided in the fourth aspect to the sixth aspect and any implementation of the fourth aspect to the sixth aspect of the embodiments of the present application. The first device is configured to execute the method for controlling transmission provided in the fourth aspect and any implementation of the fourth aspect of the embodiments of the present application. The first network device is configured to execute the method for controlling transmission provided in the fifth aspect and any implementation of the fifth aspect of the embodiments of the present application. In some embodiments, the first communication system further includes a second network device, and the second network device is configured to execute the method for controlling transmission provided in the sixth aspect and any implementation of the sixth aspect of the embodiments of the present application.

[0128] In an eighth aspect, the embodiments of the present application provide a network device, including a transceiver, a processor and a memory. The memory is configured to store computer program code, and the computer program code includes computer instructions. The processor is configured to invoke the computer instructions to enable the user equipment to execute the method for controlling transmission provided in the second aspect, the third aspect, the fifth aspect, the sixth aspect and the seventh aspect, and any implementation of the second aspect, the third aspect, the fifth aspect, the sixth aspect and the seventh aspect of the embodiments of the present application.

[0129] In a ninth aspect, the embodiments of the present application provide an electronic device, including a transceiver, a processor and a memory. The memory is configured to store computer program code, and the computer program code includes computer instructions. The processor is configured to invoke the computer instructions to enable the user equipment to execute the method for controlling transmission provided in the first aspect, the fourth aspect and the seventh aspect, and any implementation of the first aspect, the fourth aspect and the seventh aspect of the embodiments of the present application.

[0130] In a tenth aspect, the embodiments of the present application provide a communication apparatus, which can be a device or a chip in a device. The communication apparatus includes a processing unit configured to execute the method for controlling transmission provided in the first aspect to the seventh aspect, and any implementation of the first aspect to the seventh aspect of the embodiments of the present application.

[0131] In an eleventh aspect, the embodiments of the present application provide a computer storage medium, which stores a computer program. The computer program includes program instructions. When the program instructions are executed by a processor, the program instructions are configured to execute the method for controlling transmission provided in the first aspect to the seventh aspect, and any implementation of the first aspect to the seventh aspect of the embodiments of the present application.

[0132] In a twelfth aspect, the embodiments of the present application provide a computer program product. When the computer program product is run on a communication device, the computer program product is configured to enable the communication device to execute the method for controlling transmission provided in the first aspect to the seventh aspect, and any implementation of the first aspect to the seventh aspect of the embodiments of the present application.

[0133] In a thirteenth aspect, an electronic device is provided, which includes a method or apparatus as described in any of the embodiments of the present application. The electronic device is, for example, a chip. BRIEF DESCRIPTION OF DRAWINGS

[0134] The drawings used in the embodiments of the present application are described below.

[0135] Figure 1 is a schematic diagram of an architecture of a communication system provided by the embodiments of the present application;

[0136] Figure 2 is a schematic diagram of an architecture of a communication protocol stack of a user plane of new radio access (NR);

[0137] Figure 3 is a schematic diagram of an architecture of a communication protocol stack of a control plane of NR;

[0138] Figure 4 is a schematic diagram of a transition of a radio resource control (RRC) state of a user equipment (UE);

[0139] Figures 5-10 is a schematic diagram of a procedure of some small data transmission (SDT) provided by the embodiments of the present application;

[0140] Figures 11-12 is a schematic diagram of a procedure of some anchor point migration provided by the embodiments of the present application;

[0141] Figures 13-19 is a schematic diagram of a procedure of some method of control transmission provided by the embodiments of the present application. DETAILED DESCRIPTION

[0142] The technical solutions in the embodiments of the present application will be described clearly and thoroughly below with reference to the drawings. The terms used in the implementation part of the embodiments of the present application are only used to explain the specific embodiments of the present application, and are not intended to limit the present application.

[0143] First, the related devices and communication systems involved in the present application are introduced.

[0144] Network device: A network device can be a device for transmitting or receiving information. In some embodiments, a network device includes an access network device, such as, but not limited to, a base station, a user equipment (UE), a wireless access point (AP), a transmission and receiver point (TRP), a relay device, or other network device with the function of a base station, and the like. Among them, the base station is a device deployed in the radio access network (RAN) to provide wireless communication functions. In different wireless access systems, the name of the base station may be different, such as, but not limited to, the base transceiver station (BTS) in the global system for mobile communications (GSM) or code division multiple access (CDMA), node B (NB) in wideband code division multiple access (WCDMA), evolved node B (eNodeB) in long term evolution (LTE), and also can be the next generation base station (g node B, gNB) in the 5th generation mobile networks (5G), that is, new radio (NR), or the base station in other future network systems. In some embodiments, the network device includes a core network device, such as an authentication management function (AMF), a mobility management entity (MME), and the like.

[0145] Terminal: A terminal can be a device with wireless communication function. In some embodiments, the terminal is a UE. In some embodiments, the terminal can also be referred to as a mobile station, an access terminal, a user agent, and the like. Exemplarily, the terminal is a handheld device, a wearable device, a computing device, a portable device, a vehicle-mounted device, an industrial wireless sensor, or a smart meter, and the like. Exemplarily, the terminal is specifically a cellular phone, a smartphone, smart glasses, a laptop computer, a personal digital assistant, a cordless phone, a pressure sensor, a temperature sensor, a smart meter, and the like.

[0146] The terminal in the embodiments of the present application can be a multi-card terminal or a single-card terminal. The multi-card terminal can also be referred to as a multi-card device or a multi-card terminal device. In some embodiments, the multi-card terminal can be interpreted as a multiple universal subscriber identity module (Multi-USIM or MUSIM). In some embodiments, the multi-card terminal can also be interpreted as a multiple universal mobile telecommunications system (UMTS) subscriber identity module (Multi-USIM or MUSIM).

[0147] The multi-card terminal can include multiple sub-devices. For example, the multi-card terminal can be installed with multiple subscriber identity module (SIM) cards, universal subscriber identity module cards, and the like. Each card is a sub-device. The sub-devices included in the multi-card terminal can be devices with wireless communication functions. In some embodiments, the sub-devices are UEs. The multiple sub-devices included in the multi-card terminal can be registered with different networks, such as different access network devices and / or different core network devices. The multiple sub-devices included in the multi-card terminal can share a radio frequency transmission chain and / or a radio frequency reception chain. The radio frequency transmission chain can include, but is not limited to, at least one of the following: an antenna, a power amplifier, a filter, a transmit modulator, an envelope tracker, a low-noise amplifier, a filter, an antenna switch, an antenna tuner, and the like. The radio frequency reception chain can include, but is not limited to, at least one of the following: an antenna, a filter, a low-noise amplifier, a radio frequency interface, an antenna switch, an antenna tuner, an envelope tracker, and the like. Optionally, only one of the multiple sub-devices can use the shared radio frequency transmission chain and / or radio frequency reception chain for communication at any time. The multiple sub-devices cannot communicate (send information and / or receive information) at the same time. For example, the multi-card terminal is a smart phone installed with two cards. A user can only use one of the cards to make or receive a call, access the Internet, and the like at any time.

[0148] The single-card terminal is a concept relative to the multi-card terminal. The single-card terminal can be understood as a terminal including only one sub-device, i.e., the terminal itself. For example, a smart phone including only one card. In some embodiments, the single-card terminal is a UE.

[0149] The following embodiments take the network device as a base station, a single-card terminal as a UE, and any one sub-device included in a multi-card terminal as a UE as examples for description.

[0150] Please refer to Figure 1 , Figure 1 is a schematic diagram of an architecture of a communication system provided by an embodiment of the present application. The communication system can be, but is not limited to, a GSM, CDMA, wideband code division multiple access (WCDMA), time-division code division multiple access (TD-SCDMA), universal mobile telecommunications system (UMTS), LTE, NR, or other future network system.

[0151] As shown in Figure 1 , the communication system can include a UE 110, a UE 120, a base station 210, a base station 220, and a base station 230. In some embodiments, the UE 110 and the UE 120 are different single-card terminals. In other embodiments, the UE 110 is a single-card terminal, and the UE 120 is a multi-card terminal or a sub-device included in a multi-card terminal. In other embodiments, the UE 110 is a multi-card terminal or a sub-device included in a multi-card terminal, and the UE 120 is a single-card terminal. In other embodiments, the UE 110 and the UE 120 are two sub-devices included in the same multi-card terminal, for example, a multi-card terminal 100 as shown in Figure 1 .

[0152] In some embodiments, the communication system can further include a core network, which is a key control node in the communication system and is mainly responsible for signaling processing functions, such as, but not limited to, functions for implementing access control, mobility management, session management, and the like. In some embodiments, when a UE is in a cell covered by a certain base station, i.e., a current serving cell of the UE corresponds to the base station, the base station can provide wireless communication services for the UE. Optionally, the UE can transmit uplink data and / or downlink data with the base station. Optionally, the UE can transmit uplink data and / or downlink data with the core network through the base station. Optionally, the UE can transmit data with other devices through the base station.

[0153] In some embodiments, the UE 110 and the UE 120 can be registered to different networks, respectively, as shown in Figure 1As shown, the UE 110 can be connected with the base station 210 through an air interface (such as Uu), and the base station 210 can provide wireless communication services for the UE 110, and the UE 120 can be connected with the base station 220 through an air interface, and the base station 220 can provide wireless communication services for the UE 120.

[0154] In some embodiments, the base stations can communicate with each other, such as Figure 1 As shown, the base station 210 can communicate with the base station 230 through an Xn interface, and the messages transmitted through the Xn interface can be referred to as Xn interface messages.

[0155] Exemplarily, in NR, the core network can be referred to as a 5G core network (5GC), and the base station can be referred to as a gNB. At least one gNB can constitute a next generation-radio access network (NG-RAN) node. The NG-RAN node can include at least one gNB connected to the 5GC through an NG interface, and at least one gNB in the NG-RAN node can be connected and communicated through an Xn-C interface. The UE can be connected to the gNB through a Uu interface.

[0156] It should be noted that Figure 1 The forms and quantities of the UEs and base stations shown are only for example, and the embodiments of the present application are not limited thereto.

[0157] For the convenience of understanding, the embodiments of the present application are mainly described taking the LTE and / or NR as an applied communication system for example.

[0158] Next, the communication protocol stack of NR is exemplarily introduced.

[0159] Please refer to Figure 2 , Figure 2 is an architecture diagram of a user plane protocol stack of NR. The user plane protocol stack can include a physical (PHY) layer, a medium access control (MAC) layer, a radio link control (RLC) layer, a packet data convergence protocol (PDCP) layer, and a service data adaptation protocol (SDAP) layer.

[0160] Please refer to Figure 3 , Figure 3is a schematic diagram of an architecture of a control plane protocol stack of NR. The control plane protocol stack can include a PHY layer, a MAC layer, a RLC layer, a PDCP layer, a radio resource control (RRC) layer, a non access stratum (NAS).

[0161] Compared with the user plane protocol stack of LTE, the user plane protocol stack of NR adds an SDAP layer, but the architecture of other layers is consistent, and the specific description is similar. LTE is more mature and will not be described again.

[0162] As shown in Figure 2 and Figure 3 , the lower layer of the PDCP layer includes the RLC layer. The PDCP layer can process the RRC message on the control plane, and the PDCP layer can perform IP packet header compression to reduce the number of bits transmitted on the wireless interface. The PDCP layer is also responsible for the encryption of the control plane, the integrity protection of the transmitted data. At the receiving end, the PDCP layer performs corresponding decryption and decompression operations. One PDCP entity can be configured for each radio bearer. The RLC layer is responsible for segmentation / cascading, retransmission control and duplicate detection, etc., and the RLC layer provides services for the PDCP layer, and one RLC entity can be configured for each radio bearer. The MAC layer controls the multiplexing of logical channels, the retransmission of hybrid automatic repeat request, the scheduling of uplink and downlink, etc. The MAC layer provides services for the RLC layer in the form of logical channels. The PHY layer loads management encoding / decoding, modulation / demodulation, mapping of multiple antennas and other types of physical layer functions, and the PHY layer provides services for the MAC layer in the form of transmission channels.

[0163] As shown in Figure 2 and Figure 3As shown, the MAC layer can provide services to higher layers (such as the RLC layer) via logical channels (LCH). Based on the type of information transmitted, logical channels can be classified into control channels for transmitting control information in the control plane and traffic channels for transmitting user data in the user plane. Control channels may include, but are not limited to, common control channels (CCCH) and dedicated control channels (DCCH). Traffic channels may include, but are not limited to, dedicated traffic channels (DTCH). CCCH can always exist; UEs without an RRC connection to the RAN node can also use CCCH to transmit information. DCCH can be used to transmit dedicated control information between the UE and the RAN node. DTCH can be used to transmit user data between the UE and the RAN node. Typically, DCCH and DTCH do not always exist; they can only be used for communication between the UE and the base station after the base station connected to the UE restores the UE context. The UE context includes, but is not limited to, the terminal's identifier, radio bearer (RB) related configurations, PDCP layer context or functional configurations (e.g., security-related configurations for integrity protection and encryption), and quality of service (QoS) related configurations.

[0164] An RB can be a set of connection formats between a UE and a RAN node, and can include the configuration of physical channels, transport channels, and logical channels. RBs can be divided into signaling radio bearers (SRBs) used to transmit control information in the control plane and data radio bearers (DRBs) used to transmit user data in the user plane. A DRB can include a PDCP layer entity (PDCP entity), an RLC layer entity (RLC entity), and a logical channel.

[0165] like Figure 3 As shown, the RRC layer can be used to transmit RRC messages between the UE and the base station. For example, but not limited to, the RRC Resume Request in NR can be used by the UE to request the resumption of a suspended RRC connection in order to transmit data with the base station. The RRC layer belongs to the access stratum (AS).

[0166] For the RRC layer, there are currently three RRC states of the UE, which are RRC IDLE state, RRC INACTIVE state and RRC CONNECTED state. The operations performed by the UE in different RRC states are mostly different. The three states and the conversion process can be seen from the following examples. Figure 4

[0167] As shown in Figure 4 , when the UE is in the RRC CONNECTED state, the RRC connection is established between the UE and the base station. In some embodiments, when the UE is in the RRC CONNECTED state, the connection of the user plane and the control plane of the UE can be established between the 5GC and the NG-RAN, the NG-RAN and the UE can retain the UE context of the AS layer, the NG-RAN can obtain the cell to which the UE belongs, the UE can send or receive unicast data, and the network (for example, the NG-RAN) can control the mobility of the UE. Illustratively, the UE can measure the channel between the UE and the base station and can report the measurement result to the base station, and the base station can determine whether to switch the cell to which the UE belongs according to the measurement result. In other words, in the RRC CONNECTED state, the UE and the base station can not only normally transmit data, but also the base station can manage the UE. In some embodiments, if the UE in the RRC CONNECTED state needs to send uplink data to the base station, the UE needs to keep synchronization with the base station according to the timing advance (TA). If the UE in the RRC CONNECTED state does not obtain uplink synchronization, the UE can initiate random access (RA) to the base station. When the timing advance timer (TAT) of the UE is running, the UE keeps uplink synchronization. When the TAT of the UE is timed out, the uplink synchronization of the UE is invalid, and if the UE needs to send uplink data to the base station again, the UE needs to initiate RA to obtain a new TA. In some embodiments, when the UE is in the RRC CONNECTED state, the base station can allocate configured grant (CG) resources to the UE. When the UE has data transmission demand, the UE can use the CG resources to send uplink data to the base station. In some embodiments, the base station can configure the CG resources for the UE through an RRC message. The information of the configuration can include time-frequency position and period. Compared with the dynamic scheduling transmission resource, this way of transmitting data through the CG resource can reduce signaling overhead and transmission delay.

[0168] ​When there is no uplink resource but there is uplink data to be sent to the base station, the UE in the RRC CONNECTED state can trigger a buffer status reporting (BSR) to request the base station to schedule uplink resources. The BSR can be used to indicate the amount of data currently to be transmitted in the data buffer of the UE. The amount of data can be different at different times. For example, the UE is a smart phone, and the user can send messages to other users through a social application installed on the UE, but the type and amount of messages sent by the user at different times can be different. Sometimes the message sent can only be a text message, and sometimes the message sent can include multiple videos. Therefore, the size of the BSR sent by the UE to the base station at different times can also be different. The resource (referred to as BSR resource) used by the UE to send the BSR to the base station can be dynamically scheduled by the base station to the UE.

[0169] When the UE is in the RRC IDLE state, the RRC connection between the UE and the base station is not established. In some embodiments, when the UE is in the RRC IDLE state, the UE can perform selection of a public lands mobile network (PLMN), receive system information broadcast by the base station, perform cell re-selection, be called paging (Paging) initiated by the 5GC for downlink transmission, and discontinuous reception (DRX) configured by the NAS layer for core network paging, etc.

[0170] The RRC INACTIVE state is a newly added RRC state in NR. In some embodiments, for a UE with infrequent data transmission, the base station will usually let the UE stay in the RRC INACTIVE state. In some embodiments, when the UE is in the RRC INACTIVE state, the UE can perform selection of a PLMN, receive system information broadcast by the base station, perform cell reselection, be subject to paging initiated by the NG-RAN, manage a RAN-based notification area (RNA) by the NG-RAN, e.g., UE triggered RNA update (RNAU) to inform the base station of the current RNA in which the UE is located, be configured with a DRX for RAN paging by the NG-RAN, have a connection between the 5GC and the NG-RAN for the user plane and the control plane of the UE, have the UE context preserved at the AS layer by the NG-RAN, and have the RNA in which the UE is located acquired by the NG-RAN. In some embodiments, after the UE establishes an RRC connection with the base station, the UE enters the RRC CONNECTED state. If the UE in the RRC CONNECTED state has no data transmission requirement with the base station within a preset time period, the base station can instruct the UE to enter the RRC INACTIVE state. For example, the base station can send an RRC release (RRCRelease with suspend indication) message carrying a suspend indication to the UE, and after the UE receives the RRCRelease with suspend indication message, the UE retains its own context and enters the RRC INACTIVE state.

[0171] In some embodiments, the above three states at the RRC layer can be converted to each other, e.g., Figure 4In some embodiments, the UE is in the RRC IDLE state or the RRC INACTIVE state (which can be collectively referred to as a non-RRC connected state), and if data transmission is needed, the UE can initiate an RRC connection establishment procedure or an RRC connection resume procedure. For example, the UE in the RRC IDLE state can establish an RRC connection with the base station by performing RA, specifically sending an RRC setup request (RRCSetupRequest) message to the base station, and then receiving an RRC setup (RRCSetup) message sent by the base station. After receiving the RRCSetup message, the UE can establish an RRC connection with the base station and enter the RRC CONNECTED state. For example, the UE in the RRC INACTIVE state can send an RRCResumeRequest message to the base station, and then receive an RRC resume (RRCResume) message sent by the base station. After receiving the RRCResume message, the UE can enter the RRC CONNECTED state. In other embodiments, the UE in the non-RRC connected state can also perform an RRC connection establishment procedure or an RRC connection resume procedure in response to a paging message from the base station. For example, the core network can instruct the base station to send a paging message to the UE when there is data transmission to the UE.

[0172] In some embodiments, the UE can enter the RRC INACTIVE state or the RRC IDLE state from the RRC CONNECTED state at the instruction of the base station. In some embodiments, the base station can release the UE to enter the RRC INACTIVE state or the RRC IDLE state when the UE does not need to perform data subsequently, and specific examples are shown as follows.

[0173] Example one, the UE enters the RRC INACTIVE state from the RRC CONNECTED state at the instruction of the base station. In detail, the base station can send a release message with a suspend indication, such as an RRCRelease with suspend indication message, to the UE to make the UE enter the RRC INACTIVE state. At this time, the RRC connection between the UE and the base station is suspended, but at least one RAN node retains the UE context of the UE.

[0174] Example two, the UE enters the RRC IDLE state from the RRC CONNECTED state at the instruction of the base station. In detail, the base station can send a release message, such as an RRCRelease message, to the UE to make the UE enter the RRC IDLE state. At this time, the RRC connection between the UE and the base station is stopped, and the RAN node deletes the UE context of the UE.

[0175] In some embodiments, the UE can also enter the RRC IDLE state from the RRC INACTIVE state at the indication of the base station, for example, after the UE in the RRC INACTIVE state sends the RRC connection resume request, the base station can release the UE to enter the RRC IDLE state. It can be understood that the UE enters the RRC CONNECTED state from the RRC INACTIVE state faster than from the RRC IDLE state.

[0176] In some embodiments, when the UE is in the RRC IDLE state or the RRC INACTIVE state, if data transmission is needed, the UE can perform the RRC connection establishment procedure or the RRC connection resume procedure to request to enter the RRC CONNECTED state to transmit data, wherein if the UE in the RRC IDLE state or the RRC INACTIVE state does not have resources to send the RRCSetupRequest message or the RRCResumeRequest message, the UE needs to initiate a random access (RA) procedure. Next, the RA is exemplarily introduced.

[0177] In some embodiments, the UE can obtain the RA configuration of the current cell from the system information broadcast by the base station, for example, the configuration includes available random access preambles and RA resources for sending random access preambles, for example, the RA resources for sending random access preambles are time-frequency resources for the UE to send random access preambles, which can also be referred to as random access occasions (ROs). In some embodiments, the RA can include 4-step random access (4-step RA for short) and 2-step random access (2-step RA for short). The base station can broadcast the RA configuration corresponding to the 4-step RA and the RA configuration corresponding to the 2-step RA in the system information, or only broadcast the RA configuration corresponding to the 4-step RA in the system information, or only broadcast the RA configuration corresponding to the 2-step RA in the system information.

[0178] In some embodiments, the base station can broadcast the RA configuration corresponding to the 4-step RA and the RA configuration corresponding to the 2-step RA in system information. When the UE is not configured with the resource of contention free random access (CFRA), the UE can determine to initiate the 4-step RA or the 2-step RA based on the relative size of the current measured reference signal receiving power (RSRP) and the preset RSRP threshold. For example, when the current measured RSRP is greater than or equal to the preset RSRP threshold, the UE can initiate the 2-step RA. When the current measured RSRP is less than the preset RSRP threshold, the UE can initiate the 4-step RA.

[0179] In some embodiments, the message sent by the UE to the base station in the third step of the 4-step RA can be referred to as message 3, abbreviated as msg3. The message sent by the UE to the base station in the first step of the 2-step RA can be referred to as message A, abbreviated as msgA. In some embodiments, the above-mentioned msg3 or msgA can include an RRC message. The RRC message can be different when the UE is in different RRC states and in different service scenarios. For example, when the UE in the RRC INACTIVE state has data to send to the base station, the msg3 sent by the UE to the base station can include an RRCResumeRequest message, so as to request to resume the suspended RRC connection and enter the RRC CONNECTED state to transmit data with the base station.

[0180] It can be understood that, in general, when the UE in the non-RRC connected state has uplink data to send to the base station, or receives the paging message sent by the base station, the paging message is used to indicate that there is downlink data to send to the UE, the UE needs to re-establish or resume the RRC connection and enter the RRC CONNECTED state, and then transmit data with the base station in the RRC CONNECTED state. However, the above-mentioned method is more suitable for the case where the data amount transmitted between the UE and the base station is large. If the data packet is very small, such data packet can be referred to as small data, and the signaling required for the state switching process of the UE is even greater than the small data, thereby causing unnecessary power consumption and signaling overhead of the UE. Therefore, it is necessary to transmit small data to the base station when the UE is in the non-RRC connected state, for example, when the UE in the RRC INACTIVE state has uplink small data transmission requirement, the uplink small data can be transmitted to the base station.

[0181] In the embodiments of the present application, the small packet data can include, but is not limited to, a data packet with a data size less than a preset threshold (for example, the size of a transport block indicated by the base station), a data packet with a data label of small packet data, a data packet with a data type belonging to small packet data, and the like. The data packet that is not small packet data can be referred to as large packet data, and can include, but is not limited to, a data packet with a data size greater than or equal to the preset threshold, a data packet with a data label of large packet data, a data packet with a data type belonging to large packet data, and the like. The data label and / or the data type described above can be negotiated by the UE and the network device. For example, the data label can include large packet data and small packet data. For example, data with a data type of a heartbeat packet is small packet data, and data with a data type of a file, a video, or an audio is large packet data. For example, the small packet data is an instant messaging message of an application (APP) of the UE, a heartbeat packet of the APP, or a push message of the APP, and the like. For example, the small packet data is periodic data (for example, a heartbeat packet) of a wearable device such as a smart watch, and the like. For example, the small packet data is service data of an internet of things (IoT) device, and the like. For example, the small packet data is periodic reading of an industrial wireless sensor network, and the like. For example, the small packet data is periodic reading of a smart meter such as a smart meter, and the like.

[0182] In some embodiments, the transmission of the small packet data by the UE to the base station in the non-RRC connected state can include that the UE transmits the small data in the RA procedure without entering the RRC CONNECTED state to transmit the small data, which can be referred to as small data transmission (SDT) based on the RA, or RA-SDT. In some embodiments, the RA can include 4-step RA and 2-step RA, and the SDT can include 4-step SDT based on the 4-step RA and 2-step SDT based on the 2-step RA. For example, the process of the 4-step SDT can be referred to as the following Figure 5 and Figure 6 For example, the process of the 2-step SDT can be referred to as the following Figure 7 and Figure 8 The implementation of the RA-SDT is similar to that of the RA. For example, the UE can obtain the configuration of the RA-SDT from the system information broadcast by the base station. The UE can determine to initiate the 4-step SDT or the 2-step SDT based on the relative size of the currently measured RSRP and the preset RSRP threshold.

[0183] In some embodiments, the UE transmits the small data to the base station in the non-RRC connected state can further include that the UE transmits the small data through the pre-allocated CG resource or the pre-configured uplink resource (PUR) without entering the RRC CONNECTED state, and the transmission process can be referred to as CG-based SDT (CG-SDT). For details, refer to the following Figure 9 and Figure 10 .

[0184] In some embodiments, there are multiple different application scenarios for SDT, and different implementation manners of SDT can be used according to the application scenarios, such as RA-SDT or CG-SDT. For details, refer to the following examples:

[0185] Example 1: In CG-SDT, the resource (such as CG resource or PUR) indicated by the CG-SDT configuration is sent to the UE by the base station through dedicated control signaling, so the CG-SDT configuration is applicable to the UE in the cell covered by the base station, and the CG-SDT configuration provided in one cell cannot be reused by the UE in another cell. If the UE moves to the coverage of other network devices, the resource indicated by the CG-SDT configuration cannot be used any more. Based on this feature, it can be applied to the following scenarios: for IoT applications, the mobility of the UE is limited, and all connections are usually established in the same cell to transmit data, and the cell is rarely changed, so the UE in the IoT field can prefer to use CG-SDT.

[0186] Example 2: The configuration of the RA related to the configuration of the RA-SDT can be provided by the system information sent by the base station, and the UE can read and apply the configuration broadcasted by the system information whenever the UE reselects to a new cell. Based on this feature, it can be applied to the following scenarios: for instant messaging and other applications of smart phones, the mobility of the UE is relatively strong, and the UE can move from the coverage of one base station to the coverage of another base station. If the UE moves from the coverage of base station A to the coverage of base station B, and uses the resource indicated by the CG-SDT configuration sent by base station A before moving to perform SDT, data cannot be transmitted. Since the resource for sending the random access preamble in RA-SDT is broadcasted in real time by the base station, for the UE with strong mobility, RA-SDT can be preferred.

[0187] Of course, whether the UE uses CG-SDT or RA-SDT can also not be limited by the scenario, and which way to use for SDT can be determined based on the implementation of the UE.

[0188] Exemplarily, since the resource for performing CG-SDT is specially configured by the base station for the UE, the success rate of the UE performing CG-SDT is high. The random access resource of RA-SDT is broadcast by the network device, and the UE that can receive the broadcast message can initiate RA-SDT on the random access resource. Multiple UEs will compete for resources, which may cause a situation of competition failure. Therefore, the success rate of RA-SDT is not as high as that of CG-SDT, and CG-SDT is more effective than RA-SDT. Generally, the UE preferentially selects CG-SDT. The UE also needs to meet certain conditions to select CG-SDT. If the conditions are not met, the UE can select RA-SDT. For example, whether there is a resource indicated by CG-SDT configuration in the coverage of the normal uplink (NUL) carrier or the supplementary uplink (SUL) carrier currently occupied by the UE. If there is a resource indicated by CG-SDT configuration, and there is a valid resource in the resource indicated by CG-SDT configuration, the UE can select CG-SDT, otherwise, the UE selects RA-SDT.

[0189] In some embodiments, the RBs configured by the base station for the UE can include RBs for carrying small packet data (referred to as SDT RBs) and RBs for carrying large packet data (referred to as non-SDT RBs). The RBs can include DRBs for carrying data and SRBs for carrying control information. Only when small packet data carried by the SDT RBs arrives, the UE can initiate SDT. If large packet data carried by the non-SDT RBs arrives, the UE cannot initiate SDT.

[0190] Next, the transmission process of SDT is exemplarily introduced.

[0191] Please refer to Figure 5 , Figure 5 Exemplarily, a flowchart of a user plane 4-step SDT process is shown. Figure 5 The process shown can include but is not limited to the following steps:

[0192] S111: The UE sends a random access preamble to the base station.

[0193] In some embodiments, the base station can send a broadcast message to the UE, the broadcast message comprising first resource configuration information, the first resource configuration information being used to indicate random access resources for sending random access preambles. Optionally, the first resource configuration information can specifically indicate first random access resources for initiating normal random access, and optionally, the first resource configuration information can specifically indicate second random access resources for sending random access preambles in a RA-SDT procedure. Wherein, the random access preambles can be generated by the UE according to specific rules, but the base station can recognize the random access preambles generated by the UE.

[0194] In some embodiments, the random access preambles sent by the UE for RA-SDT can be different from the random access preambles sent by the UE for initiating normal RA without RA-SDT. That is, the base station can use different random access preambles to distinguish the intention of the UE, such as the intention of the UE is for RA-SDT or for initiating RA.

[0195] In other embodiments, the random access preambles sent by the UE for RA-SDT can also be the same as the random access preambles sent by the UE for initiating normal RA without RA-SDT.

[0196] In some embodiments, if the first resource configuration information specifically indicates first random access resources for initiating normal random access, and second random access resources for sending random access preambles in a RA-SDT procedure. The UE can send random access preambles on different random access resources based on different intentions, so that the base station can use different resources for receiving random access preambles to distinguish the intention of the UE. For example, when the UE intends to initiate RA, the random access preamble is sent on the first random access resource, and when the base station receives the random access preamble through the first random access resource, it can determine that the intention of the UE is to initiate RA. When the UE intends to perform RA-SDT, the random access preamble is sent on the second random access resource, and when the base station receives the random access preamble through the second random access resource, it can determine that the intention of the UE is to perform RA-SDT.

[0197] In some embodiments, the random access resource for the UE to send the random access preamble for the RA-SDT can be different from the random access resource for the UE to initiate the normal RA without the RA-SDT.

[0198] S112: In response to the random access preamble, the base station sends a random access response (RAR) to the UE.

[0199] Specifically, after the UE sends the random access preamble to the base station, the UE can listen to a physical downlink control channel (PDCCH) within a RAR time window to receive the RAR sent by the base station. If the UE does not receive the RAR sent by the base station within the RAR time window, the UE can determine that this RA fails. The RAR is used to schedule an uplink grant (UL grant) for the UE, so that the UE can send a msg3 (including the RRC request message in S113) on the resource scheduled by the RAR.

[0200] In some embodiments, the RAR can further include at least one of a temporary cell radio network temporary identifier (TC-RNTI) and a timing advance (TA). The TA is used for the UE to obtain uplink synchronization.

[0201] S113: The UE sends the uplink small packet data and the RRC request message to the base station on the resource scheduled by the RAR.

[0202] In some embodiments, the RRC request message can carry intention information indicating the intention of the UE sending the RRC request message, such as the intention of the UE to perform RA-SDT or to initiate RA. Illustratively, if the random access preamble that the UE wants to send to initiate RA-SDT is the same as the random access preamble that the UE wants to send to initiate normal RA without performing RA-SDT, or the random access resource that the UE wants to send the random access preamble to initiate RA-SDT is the same as the random access resource that the UE wants to send the random access preamble to initiate normal RA without performing RA-SDT, the RRC request message that the UE wants to send to perform RA-SDT can carry intention information indicating the intention of the UE to initiate RA-SDT rather than the intention of the UE to initiate normal RA.

[0203] In other embodiments, the UE can send a BSR when sending msg3 to the base station, and the base station can obtain the intention of the UE, such as the intention of the UE to perform RA-SDT or to initiate RA, through the BSR sent by the UE. Illustratively, if the random access preamble that the UE wants to send to perform RA-SDT is the same as the random access preamble that the UE wants to send to initiate normal RA without performing RA-SDT, and the random access resource that the UE wants to send the random access preamble to perform RA-SDT can also be the same as the random access resource that the UE wants to send the random access preamble to initiate normal RA without performing RA-SDT, if the UE wants to perform RA-SDT, a BSR can be sent when sending msg3 to the base station, and the BSR is used to indicate the data amount of small packet data, and the base station can obtain the intention of the UE to initiate RA-SDT rather than the intention of the UE to initiate normal RA through the received BSR.

[0204] In some embodiments, the RRC request message in msg3 can be different for UEs in different RRC states and in different traffic scenarios. For example, the RRC request message sent by a UE in RRC IDLE state (optionally, at this time the UE can store the UE context such as configuration information for obtaining the key for encrypting the above-mentioned uplink small packet data, or the terminal can also not store its context) can include an RRC connection request (RRCConnectionRequest) message, an RRC connection resume request (RRCConnectionResumeRequest) message, an RRC early data transmission request (RRCEarlyDataRequest) message, an RRCResumeRequest message, an RRCResumeRequest1 message, an RRC setup request (RRCSetupRequest) message, or other RRC messages with the same function but not standardized by the 3rd generation partnership project (3GPP). The RRC request message sent by a UE in RRC INACTIVE state can be an RRCConnectionRequest message, an RRCConnectionResumeRequest message, an RRCEarlyDataRequest message, an RRCResumeRequest message, an RRCResumeRequest1 message, an RRCSetupRequest message, or other RRC messages with the same function but not standardized by the 3GPP.

[0205] In some embodiments, the UE can send the uplink small packet data and the RRC request message to the base station to initiate the RRC connection resume procedure for 4-step SDT, and in some embodiments, the RRC request message for initiating the RRC connection resume procedure for 4-step SDT includes a resume cause (resumeCause) information element (IE), and the resumeCause IE can be set to mo-data.

[0206] In some embodiments, the UE first initializes an RRC connection resume procedure for the SDT, and then sends an RRC request message to the base station based on the 4-step SDT. In some embodiments, the msg3 can include an identity of the UE, for example, a unique identity of the UE at the core network. In some embodiments, the msg3 can include relevant information of the base station of the last connection of the UE, for example, an inactive temporary cell radio network temporary identifier (I-RNTI). In some embodiments, the msg3 can include information for encryption and integrity protection.

[0207] In some embodiments, the above small packet data can be transmitted on the DTCH, and the above RRC message can be transmitted on the CCCH. The MAC layer can encapsulate the small packet data and the RRC request message, and send them to the base station through the PHY layer.

[0208] S114: After receiving the RRC request message, the base station sends a contention resolution message to the UE.

[0209] In some embodiments, after receiving the uplink small packet data and the RRC request message, the base station can resume the UE context and send the received uplink small packet data to the core network.

[0210] In some embodiments, the contention resolution message is actually a contention resolution identity MAC control element (contention resolution Identity MAC CE), which can indicate that the UE contention resolution is successful. In some embodiments, the UE can determine whether the contention resolution Identity MAC CE and the msg3 sent in S113 are consistent, and if they are consistent, it is determined that the contention resolution corresponding to the current RA-SDT procedure is successful, or it is determined that the current RA-SDT procedure is successful.

[0211] S115: The base station sends an RRC response message to the UE.

[0212] In some embodiments, if there is downlink small packet data for the UE from the core network, the core network can send the downlink small packet data to the base station. Then, the base station can send the downlink small packet data to the UE together with the RRC response message. The downlink small packet data can be transmitted on the DTCH and multiplexed with the RRC response message transmitted on the DCCH at the MAC layer.

[0213] In some embodiments, the UE can determine whether the uplink small packet data is successfully transmitted according to the RRC response message, as shown in the following examples:

[0214] Example 1: The RRC response message sent by the base station is an RRC Connection Release (RRCConnectionRelease) message, an RRC Connection Resume (RRCConnectionResume) message, an RRC Connection Setup (RRCConnectionSetup) message, an RRC Release message, an RRC Resume message, or an RRC Setup message, or other RRC messages with the same function but not standardized by 3GPP. If the UE receives the above RRC response message, it can determine that the SDT transmission is successful.

[0215] Example 2: The RRC response message sent by the base station is an RRC Connection Reject (RRCConnectionReject) message, an RRC Reject (RRCReject) message, or other RRC messages with the same function but not standardized by 3GPP. If the UE receives the above RRC response message, it can determine that the SDT transmission fails.

[0216] In some embodiments, the UE can remain in the current RRC state or enter other RRC states according to the RRC response message, as shown in the following examples:

[0217] Example 1: If the core network has no further data transmission requirement, the RRC response message sent by the base station is an RRC data early transmission completion (RRCEarlyDataComplete) message, an RRC connection release (RRCConnectionRelease) message, an RRC release (RRCRelease) message with suspend configuration, an RRC release (RRCRelease) message, or other RRC messages with the same function but not standardized by 3GPP. In the case that the UE receives the above-mentioned RRC response message, it can be considered that the SDT transmission process is successful. In response to the above-mentioned RRC response message, the UE can remain in the current non-RRC connected state. Alternatively, the above-mentioned RRC response message (such as the RRC release message) can include the relevant configuration of the UE's next SDT initiation, for example, the next hop chaining count (NCC) and I-RNTI of the UE's encrypted small packet data.

[0218] Example 2: If the core network has further data transmission requirement, the core network can trigger the indication process of connection establishment, and the above-mentioned RRC response message sent by the base station is an RRC connection setup (RRCConnectionSetup) message, an RRC connection resume (RRCConnectionResume) message, an RRC setup (RRCSetup) message, an RRC resume (RRCResume) message, or other RRC messages with the same function but not standardized by 3GPP. In the case that the UE receives the above-mentioned RRC response message, it can be considered that the SDT transmission process is successful. In response to the above-mentioned RRC response message, the UE can enter the RRC CONNECTED state.

[0219] In some embodiments, if the UE does not receive the RRC response message in S115, it is considered that the small packet data transmission in S113 fails. If the UE receives the RRC response message in S115, it is considered that the small packet data transmission in S113 is successful. That is, the UE can use whether the RRC response message is received to determine whether the small packet data transmission in S113 is successful.

[0220] It should be noted that whether the core network has further data transmission requirement does not include the requirement of the base station to send downlink small packet data in S115.

[0221] Please refer to Figure 6 , Figure 6 An exemplary flowchart of a control plane 4-step SDT process is shown. Figure 6 The process shown can include but is not limited to the following steps:

[0222] S121: The UE sends a random access preamble to the base station.

[0223] S122: In response to the random access preamble, the base station sends a RAR to the UE.

[0224] Specifically, S121-S122 and Figure 5 S111-S112 of the S100 are similar, and thus are not described again.

[0225] S123: The UE sends a RRC request message carrying the uplink small packet data to the base station on the resource scheduled by the RAR.

[0226] Specifically, S123 and Figure 5 S113 of the S200 are similar, except that the uplink small packet data is not sent together with the msg3 after being encapsulated at the MAC layer, but is sent in the msg3. In some embodiments, the uplink small packet data can be carried in the msg3 and transmitted on the CCCH. For example, the uplink small packet data can be carried in the NAS layer related IE (such as the dedicatedInfoNAS IE) contained in the RRC EarlyDataRequest message and transmitted on the CCCH.

[0227] S124: After receiving the RRC request message, the base station sends a contention resolution message to the UE.

[0228] Specifically, S124 and Figure 5 S114 of the S200 are similar, except that the RRC request message received by the base station includes the uplink small packet data. In some embodiments, the base station can send the uplink small packet data to the core network through the msg3 carrying the uplink small packet data. For example, the base station can send the uplink small packet data to the core network by forwarding the NAS layer related IE contained in the msg3.

[0229] S125: The base station sends a RRC response message to the UE.

[0230] Specifically, S125 and Figure 5 S115 of the S200 are similar, and thus are not described again.

[0231] Figure 5 and Figure 6 The S111 and / or S121 are performed by the UE in the case where the uplink small packet data is sent to the base station, i.e., the UE initiatively initiates the transmission process of the small packet data. However, in the specific implementation, there is also a case where the UE passively initiates the transmission process of the small packet data under the indication of the base station, for example, the mobile terminated (MT) EDT (referred to as MT-EDT) in the LTE. The transmission process of this case is similar to Figure 5And Figure 6 The transmission process shown is similar, the difference is described as follows:

[0232] Before S111, when there is downlink small packet data sent by the core network to the UE, the core network can send a paging message to the base station. In some embodiments, the paging message can carry the data volume information of the downlink small packet data. In some embodiments, the base station can send a paging message to the UE, and the UE determines to initiate 4-step SDT based on the relative size of the currently measured RSRP and the preset RSRP threshold. Illustratively, the base station can trigger MT-EDT according to the paging message, and send a paging message carrying the MT-EDT indication to the UE, so that the UE triggers the MO-EDT for MT-EDT. Wherein, different from the above-mentioned transmission process of small packet data initiated by the UE, in S113, the UE can only send an RRC message to the base station, and does not send uplink small packet data, and can optionally also carry reason information triggering MT-EDT. Correspondingly, the base station can receive the downlink small packet data sent by the core network, and in S115, the base station can send an RRC response message and the downlink small packet data to the UE.

[0233] Similarly, before S121, when there is downlink small packet data sent by the core network to the UE, the core network can send a paging message to the base station. In some embodiments, the paging message can carry the data volume information of the downlink small packet data. In some embodiments, the base station can send a paging message to the UE, and the UE determines to initiate 4-step SDT based on the relative size of the currently measured RSRP and the preset RSRP threshold. Wherein, different from the above-mentioned transmission process of small packet data initiated by the UE, in S123, the RRC message sent by the UE to the base station can not carry uplink small packet data, and can optionally also carry reason information triggering MT-EDT. Correspondingly, the base station can receive the downlink small packet data sent by the core network. In S125, the RRC response message sent by the base station to the UE can carry the downlink small packet data.

[0234] See Figure 7 , Figure 7 An exemplary flowchart of a user plane 2-step SDT process is shown. Figure 7 The process shown can include but is not limited to the following steps:

[0235] S211: The UE sends a random access preamble, an RRC request message and uplink small packet data to the base station.

[0236] In some embodiments, the transmission resource of S211 performed by the UE can be obtained through the information broadcasted by the base station, for example, the UE can use the RA resource broadcasted by the base station to send a random access preamble, and the UE can use the PUSCH resource broadcasted by the base station to send an RRC request message.

[0237] In some embodiments, the base station can distinguish the intention of the UE by using different random access preambles, in other embodiments, the base station can distinguish the intention of the UE by using different resources for receiving random access preambles, in other embodiments, the base station can obtain the intention of the UE through the BSR sent by the UE, and in other embodiments, the RRC request message can carry intention information indicating the intention of the UE for sending the RRC request message, such as the intention of the UE is for RA-SDT or for initiating RA, which can be referred to the examples of S111 and S113 in the above Figure 5

[0238] In some embodiments, the RRC request message in the above msgA can be different when the UE is in different RRC states and in different traffic scenarios, which can be referred to the examples of RRC request message in msg3 in the above Figure 5

[0239] In some embodiments, the above RRC request message and the uplink small packet data can be carried in the physical uplink shared channel (PUSCH) load. The above uplink small packet data can be transmitted on the DTCH, and the above RRC message can be transmitted on the CCCH. The MAC layer can encapsulate the small packet data and the RRC request message and send them to the base station through the PHY layer.

[0240] In some embodiments, the UE can send uplink small packet data and an RRC request message to the base station to initiate an RRC connection resume procedure for 2-step SDT, and in some embodiments, the resumeCause IE in the RRC request message for initiating the RRC connection resume procedure for 2-step SDT can be set to mo-data.

[0241] In some embodiments, the UE first initializes the RRC connection resume procedure for SDT, and then sends an RRC request message to the base station based on 2-step SDT.

[0242] In some embodiments, the RRC request message and the uplink small packet data can be referred to the above Figure 5 ​​The description of the RRC request message and the uplink small packet data in S113 is omitted here.

[0243] S212: After receiving the RRC request message, the base station sends message B to the UE.

[0244] In some embodiments, after receiving the uplink small packet data and the RRC request message, the base station can restore the UE context and send the received uplink small packet data to the core network.

[0245] In some embodiments, the message sent by the base station to the UE in the second step of the 2-step RA can be referred to as message B (msgB). msgB can be understood as a response to msgA in the 2-step SDT process. In some embodiments, msgB can include a response for contention resolution, fallback indication, or backoff indication, for example, msgB includes a backoff indicator (backoffIndicator), a successRAR (successRAR), or a fallbackRAR (fallbackRAR).

[0246] In some embodiments, msgB includes successRAR, and the successRAR includes a contention resolution field, for example, the content included in the contention resolution MAC CE. After the UE receives the successRAR, it determines that the contention resolution corresponding to the current RA-SDT process is successful, or determines that the current RA-SDT process is successful. Alternatively, the contention resolution field in the successRAR can indicate that the UE contention resolution is successful. Alternatively, the UE can determine whether the contention resolution field in the successRAR is consistent with msgA sent in S211, and if it is consistent, it is determined that the contention resolution corresponding to the current RA-SDT process is successful, or it is determined that the current RA-SDT process is successful. In other embodiments, msgB includes fallbackRAR, and after the UE receives the fallbackRAR, it sends msg3 and uplink small packet data to the base station again.

[0247] S213: The base station sends an RRC response message to the UE.

[0248] In some embodiments, if there is downlink small packet data to be sent to the UE in the core network, the core network can send the downlink small packet data to the base station. Then, the base station can send the downlink small packet data to the UE together with the RRC response message.

[0249] The description of the RRC response message can refer to the description of the RRC response message in S115 of the above Figure 5 The description of the RRC response message can refer to the description of the RRC response message in S115 of the above

[0250] Please refer to Figure 8 , Figure 8 An exemplary flowchart of a control plane 2-step SDT procedure is shown. Figure 8 The procedure shown can include but is not limited to the following steps:

[0251] S221: The UE sends a random access preamble to the base station, and an RRC request message carrying uplink small packet data.

[0252] Specifically, S221 and S211 of the above are similar, except that the uplink small packet data is not sent together with the RRC request message in msgA, but is sent in the RRC request message in msgA. In some embodiments, the RRC request message carrying uplink small packet data can be carried in a physical uplink shared channel (PUSCH) load and can be transmitted on the CCCH. Figure 7 S222: After receiving the RRC request message, the base station sends msgB to the UE.

[0253] Specifically, S222 and S212 of the above are similar, except that the RRC request message received by the base station includes uplink small packet data. In some embodiments, the base station can send the above uplink small packet data to the core network through the above RRC request message carrying uplink small packet data. For example, the base station can send the above uplink small packet data to the core network by forwarding the RRCResumeRequest message carrying uplink small packet data.

[0254] Figure 7 S223: The base station sends an RRC response message to the UE.

[0255] Specifically, S223 and S213 of the above are similar, and will not be repeated.

[0256] Figure 7

[0257] Figure 7 and Figure 8 The above describes the case where the UE initiatively initiates the transmission process of small packet data, i.e., the case where the UE performs S211 and / or S221 in the presence of uplink small packet data to be sent to the base station. However, in specific implementation, there is also the case where the UE passively initiates the transmission process of small packet data under the indication of the base station. The transmission process of this case is similar to Figure 7 and Figure 8 ​​​The transmission procedures shown are similar, with the differences described as follows:

[0258] Before S211, when there is downlink small packet data from the core network to the UE, the core network can send a paging message to the base station. In some embodiments, the paging message can carry the data volume information of the downlink small packet data. In some embodiments, the base station can send a paging message to the UE, and the UE determines to initiate 2-step SDT based on the relative size of the currently measured RSRP and the preset RSRP threshold. For example, the base station can trigger MT-EDT according to the paging message and send a paging message carrying the MT-EDT indication to the UE to make the UE trigger the MO-EDT for MT-EDT. Different from the above-mentioned transmission process initiated by the UE, in S211, the UE can only send the random access preamble and the RRC request message to the base station, and does not send the uplink small packet data, and can optionally also carry the cause information triggering the MT-EDT. Correspondingly, the base station can receive the downlink small packet data sent by the core network, and in S213, the base station can send the RRC response message and the downlink small packet data to the UE.

[0259] Similarly, before S221, when there is downlink small packet data from the core network to the UE, the core network can send a paging message to the base station. In some embodiments, the paging message can carry the data volume information of the downlink small packet data. In some embodiments, the base station can send a paging message to the UE, and the UE determines to initiate 2-step SDT based on the relative size of the currently measured RSRP and the preset RSRP threshold. Different from the above-mentioned transmission process initiated by the UE, in S221, the RRC message sent by the UE to the base station can not carry the uplink small packet data, and can optionally also carry the cause information triggering the MT-EDT. Correspondingly, the base station can receive the downlink small packet data sent by the core network. In S223, the RRC response message sent by the base station to the UE can carry the downlink small packet data.

[0260] Without being limited to the above-mentioned examples, in other embodiments, the base station can also send the msgB and the RRC response message together to the UE.

[0261] In some embodiments, after the UE initiates the RA-SDT, the UE cannot complete the transmission of the small data by sending the msg3 or msgA once. The UE can complete the transmission of the subsequent small data through subsequent transmission, which can be performed after the UE receives the contention resolution and before the base station sends the RRC response message to the UE, for example, the aboveFigure 5 Between S114 and S115 Figure 7 Between S212 and S213. A specific example is shown as follows:

[0262] Example 1: The UE currently initiates the RA-SDT for transmitting one small data (for example, an instant messaging message), when the UE initiates the 4-step SDT, the UL grant indicated by the base station in the RAR is less than the sum of the resources for transmitting the small data and the RRC request message, or when the UE initiates the 2-step SDT, the UE acquires the transmission resource from the broadcast message, which is less than the sum of the resources for transmitting the random access preamble, the small data and the RRC request message. In this case, the UE can first transmit part of the small data through msg3 or msgA, and then transmit the remaining data of the small data in the subsequent transmission phase. For example, the base station can dynamically schedule uplink resources for the UE to perform subsequent transmission after sending the contention resolution to the UE.

[0263] Example 2: The UE currently initiates the RA-SDT for transmitting multiple small data, when the small data arrives, the UE can initiate the 4-step SDT or the 2-step SDT, and transmit the small data through msg3 or msgA, but in this SDT process, the UE acquires new small data, then the UE can transmit the new small data in the subsequent transmission phase. For example, the base station can dynamically schedule uplink resources for the UE to perform subsequent transmission after sending the contention resolution to the UE.

[0264] See Figure 9 , Figure 9 An exemplary flowchart of a user plane downlink CG-SDT procedure is shown. Figure 9 The procedure shown can include but is not limited to the following steps:

[0265] S311: The UE sends an RRC request message and uplink small packet data to the base station on a pre-configured resource.

[0266] Exemplarily, the pre-configured resource is a configured grant type 1 (CG Type 1) or a PUR. The CG Type 1 can be an uplink resource directly configured by an RRC layer, and can include, but is not limited to, a time-frequency resource position of the uplink resource and a resource period.

[0267] In some embodiments, when the base station and the UE both support CG-SDT, and the UE meets the condition of using CG-SDT, the UE can perform S311 without having to perform RA. The condition of using CG-SDT includes, for example, that the UE is in a non-RRC connected state, the UE has a transmission requirement of uplink small packet data, the UE has a pre-configured resource, meets an RSRP condition, and has a valid TA.

[0268] In some embodiments, the condition of the UE using CG-SDT includes at least one of the following:

[0269] Condition 1: TAT is running, that is, the TA of the UE is valid, the UE is in an uplink synchronization state with the base station, which can indicate that CG-SDT is valid, otherwise it is invalid.

[0270] Condition 2: On the premise that TAT is running, the current RSRP of the UE is greater than a preset first RSRP threshold (referred to as RSRP 1), which can indicate that CG-SDT is valid. Optionally, the RSRP 1 can be an RSRP at which the UE can initiate an SDT transmission. That is, the current RSRP of the UE being greater than the preset RSRP 1 indicates that the UE is close to the base station and the channel quality is good, and if CG-SDT is performed, the success rate is high, and CG-SDT is valid. The current RSRP of the UE being less than or equal to the preset RSRP 1 indicates that the UE is far from the base station and the channel quality is poor, and if CG-SDT is performed, the success rate is low. The RSRP 1 can be configured by the base station for CG-SDT and RA-SDT.

[0271] Condition 3: Within a preset time period of the last TA being valid, the increase or decrease of the RSRP of the UE is less than or equal to a preset second RSRP threshold (referred to as RSRP 2), which can indicate that CG-SDT is valid. That is, whether the UE moves can be determined according to the increase or decrease of the RSRP of the UE. If the increase or decrease of the RSRP is greater than or equal to the RSRP 2, it indicates that the UE moves or moves a large distance relative to the period when the last TA is valid, and if CG-SDT is performed, the success rate is low, and CG-SDT is invalid. If the increase or decrease of the RSRP is less than the RSRP 2, it indicates that the UE does not move or moves a small distance relative to the period when the last TA is valid, and if CG-SDT is performed, the success rate is high, and CG-SDT is valid.

[0272] Condition four: If the base station configures CG-SDT on SUL and / or NUL, the UE needs to compare the current RSRP with a third RSRP threshold (referred to as RSRP 3) preset by the base station, so as to determine whether the CG-SDT configured on SUL is valid or the CG-SDT configured on NUL is valid. Alternatively, assuming that CG-SDT is configured on both SUL and NUL, the UE compares the current RSRP with RSRP 3, and if the current RSRP is less than RSRP 3, the CG-SDT on SUL is selected, and if the current RSRP is greater than or equal to RSRP 3, the CG-SDT on NUL is selected. That is, if the base station configures CG-SDT on both SUL and NUL, if the current RSRP of the UE is less than RSRP 3, it indicates that the UE is far away from the base station, and the CG-SDT configured on SUL should be used, that is, the CG-SDT on SUL is valid, and the CG-SDT on NUL is invalid. If the current RSRP of the UE is greater than or equal to RSRP 3, it indicates that the UE is close to the base station, and the CG-SDT configured on NUL should be used, that is, the CG-SDT on NUL is valid, and the CG-SDT on SUL is invalid. Alternatively, assuming that the base station only configures CG-SDT on SUL, the UE compares the current RSRP with RSRP 3, and if the current RSRP is less than RSRP 3, the CG-SDT on SUL is selected, at this time the CG-SDT is valid, and if the current RSRP is greater than or equal to RSRP 3, the CG-SDT cannot be used, that is, the CG-SDT on SUL is invalid. That is, the base station configures CG-SDT on SUL, and the UE is far away from the base station, which can use the CG-SDT on SUL, otherwise the CG-SDT on SUL is invalid. Alternatively, assuming that the base station only configures CG-SDT on NUL, the UE compares the current RSRP with RSRP 3, and if the current RSRP is less than RSRP 3, the CG-SDT cannot be used, and if the current RSRP is greater than or equal to RSRP 3, the CG-SDT on NUL is selected, that is, the CG-SDT on NUL is valid. That is, the base station configures CG-SDT on NUL, and the UE is close to the base station, which can use the CG-SDT on NUL, otherwise the CG-SDT on NUL is invalid.

[0273] Condition five: The UE is in the coverage of the base station, and the base station has configured CG resources for CG-SDT for the UE.

[0274] In some embodiments, before S311, the UE can also request the base station to configure the pre-configured resource for initiating CG-SDT. For example, the UE sends a CG-SDT resource request message to the base station in RRC CONNECTED state. The CG-SDT resource request message is used to request the base station to configure for CG-SDT. For example, in LTE, the UE sends a PUR request configuration information (PURConfigurationRequest) message to the base station.

[0275] Optionally, the UE can send the CG-SDT resource request message to the base station at any time in RRC CONNECTED state. Optionally, the UE in RRC CONNECTED state can determine that there will be small packet data in the future, and then send the CG-SDT resource request message to the base station. Optionally, the UE is in RRC CONNECTED state, and the UE has no data transmission requirement with the base station within a preset time period, the UE determines that it will enter a non-RRC connected state soon, in order to transmit small packet data in the non-RRC connected state, the UE can send the CG-SDT resource request message to the base station.

[0276] In some embodiments, after the base station receives the request configuration information (such as the CG-SDT resource request message or the PURConfigurationRequest message), when the base station instructs the UE to switch from RRC CONNECTED state to a non-RRC connected state, the RRC response message sent by the base station to the UE can carry detailed CG-SDT configuration information. For example, when the base station instructs the UE to switch from RRC CONNECTED state to RRC INACTIVE state, the above-mentioned RRC response message is RRCRelease message, and the RRCRelease message can carry detailed CG resource configuration information. For example, when the base station instructs the UE to switch from RRC CONNECTED state to RRC IDLE state, the above-mentioned RRC response message is RRCRelease message, and the RRCRelease message can carry detailed PUR configuration information.

[0277] Not limited to the above-mentioned cases, in other embodiments, after the base station configures the CG-SDT for the UE, the base station can send an RRC response message carrying release indication information to the UE to release the configured CG-SDT. For example, the RRCRelease message can carry CG resource release indication information. For example, the RRCConnectionRelease message can carry PUR release indication information.

[0278] In some embodiments, the UE can send the uplink small packet data and the RRC request message to the network device to initiate the RRC connection resume procedure for the CG-SDT.

[0279] In some embodiments, the UE can send the uplink small packet data and the RRC request message to the base station to initiate the RRC connection resume procedure for the CG-SDT, and in some embodiments, the resumeCause IE in the RRC request message used to initiate the RRC connection resume procedure for the CG-SDT can be set to mo-data.

[0280] In some embodiments, the UE first initializes the RRC connection resume procedure for the SDT, and then sends the RRC request message to the base station based on the CG-SDT.

[0281] Without being limited to the above examples, in some other embodiments, the UE can only send small packet data in the process of performing the CG-SDT, for example, if the resource indicated by the CG-SDT configuration is a non-shared resource that is specific to the UE and is configured by the network device to the UE, the UE can only send small packet data in the resource indicated by the CG-SDT configuration in the process of performing the CG-SDT. In this way, the network device can identify the UE that sends the small packet data according to the resource in which the small packet data is received. For another example, if the resource indicated by the CG-SDT configuration is a shared resource configured by the network device to multiple UEs, the UE can send small packet data and an RRC request message in the resource indicated by the CG-SDT configuration in the process of performing the SDT, so that the network device can identify the UE by using the RRC message.

[0282] The descriptions of the RRC request message and the uplink small packet data can be referred to the descriptions of the RRC request message and the uplink small packet data in S113 above, and will not be repeated here. Figure 5

[0283] S312: The base station sends a feedback response message to the UE.

[0284] In some embodiments, the base station sends the feedback response message to the UE in response to the RRC request message sent by the UE. In some embodiments, the feedback response message is used to indicate that the transmission of the RRC request message is successful, in some embodiments, the feedback response message is used to indicate that the transmission of the RRC request message and the uplink small packet data sent together with the RRC request message is successful, and in some embodiments, the feedback response message is used to indicate that the transmission of the uplink small packet data is successful.

[0285] ​In some embodiments, the feedback response message is a Layer 1 Acknowledgement (Layer 1 Ack), i.e., a physical layer ACK.

[0286] In some embodiments, the feedback response message is downlink feedback information (DFI), i.e., CG-DFI.

[0287] In some embodiments, the feedback response message is a MAC CE of the MAC layer.

[0288] In some embodiments, the feedback response message is a RRC message of the RRC layer.

[0289] S313: The base station sends an RRC response message to the UE.

[0290] In some embodiments, if there is downlink small packet data sent to the UE by the core network, the core network can send the downlink small packet data to the base station. Then, the base station can send the downlink small packet data to the UE together when sending the RRC response message.

[0291] The description of the RRC response message can refer to the description of the RRC response message in S115 above, which will not be repeated here. Figure 5

[0292] In some embodiments, the RRC response message can include a CG-SDT configuration, for example, the CG-SDT configuration in S311 is used for the UE to transmit the small packet data in S311, and the CG-SDT configuration indicated by the RRC response message in S313 is used for the UE to transmit the small packet data next time.

[0293] In some embodiments, when the feedback response message in S312 is a RRC message of the RRC layer, the feedback response message in S312 and the RRC response message in S313 can be the same message, that is, the above-mentioned feedback response message can be the above-mentioned RRC response message, that is, S312 and S313 are the same step.

[0294] Please refer to Figure 10 , Figure 10 An exemplary flowchart of a control plane CG-SDT procedure is shown. Figure 10 The procedure shown can include but is not limited to the following steps:

[0295] S321: The UE sends a RRC request message carrying uplink small packet data to the base station on a pre-configured resource.

[0296] Specifically, S321 and Figure 9 ​S311 is similar to S311 of FIG. 3, except that the uplink small packet data is not sent together with the RRC request message, but is sent in the RRC request message.

[0297] S322: The base station sends a feedback response message to the UE.

[0298] S323: The base station sends an RRC response message to the UE.

[0299] Specifically, S322-S323 and Figure 9 S312-S313 of FIG. 3 are similar, and are not described again.

[0300] Figure 9 and Figure 10 For example, S311 and / or S321 are performed by the UE in the case where there is uplink small packet data to be sent to the base station, i.e., the UE initiates the transmission process of the small packet data actively. However, in a specific implementation, there is also a case where the UE initiates the transmission process of the small packet data passively under the indication of the base station. The transmission process of this case is similar to the transmission process shown in Figure 9 and Figure 10 The difference is described as follows:

[0301] Before S311, when there is downlink small packet data to be sent to the UE by the core network, the core network can send a paging message to the base station. In some embodiments, the paging message can carry the data volume information of the downlink small packet data. In some embodiments, the base station can send a paging message to the UE to make the UE initiate CG-SDT. Different from the above-mentioned transmission process of the UE initiating the transmission of the small packet data actively, in S311, the UE can only send an RRC request message to the base station, without sending uplink small packet data, and can optionally carry the reason information of triggering MT-EDT. Correspondingly, the base station can receive the downlink small packet data sent by the core network, and in S313, the base station can send an RRC response message and the downlink small packet data to the UE.

[0302] Similarly, before S321, when there is downlink small packet data to be sent to the UE by the core network, the core network can send a paging message to the base station. In some embodiments, the paging message can carry the data volume information of the downlink small packet data. In some embodiments, the base station can send a paging message to the UE to make the UE initiate CG-SDT. Different from the above-mentioned transmission process of the UE initiating the transmission of the small packet data actively, in S321, the RRC message sent by the UE to the base station can not carry uplink small packet data, and can optionally carry the reason information of triggering MT-EDT. Correspondingly, the base station can receive the downlink small packet data sent by the core network. In S323, the RRC response message sent by the base station to the UE can carry the downlink small packet data.

[0303] In a possible implementation, the network device corresponding to the current serving cell of the UE in the non-RRC connected state (such as the RRC INACTIVE state) does not save the context of the UE, which can be referred to as a service device, and the context of the UE is saved in another network device (which can be referred to as an anchor device). In some embodiments, the anchor device can maintain the context of one or more UEs in the non-RRC connected state, and in another embodiment, the anchor device can maintain the PDCP context or function (such as security-related configuration of integrity protection and encryption) of one or more UEs in the RRC INACTIVE state. In some embodiments, the anchor device can be the network device connected to the UE in the non-RRC connected state when the UE was last in the RRC CONNECTED state, and in another embodiment, the anchor device can be the network device that sent the RRCRelease message to the UE when the UE was last in the RRC CONNECTED state. The anchor device is, for example, a network device such as an NG-RAN node, a base station, and the like.

[0304] The following embodiments take the service device as a service base station and the anchor device as an anchor base station as an example for description.

[0305] In some embodiments, the UE can leave the coverage of the anchor base station storing the context of the UE and move to another service base station, and initiate SDT under the other service base station. For example, for a UE with frequent mobility, after moving to a service base station, the UE in the RRC INACTIVE state can initiate RA-SDT under the current service base station when there is a SDT transmission requirement. If the anchor base station does not send the context of the UE to the service base station, the role of the anchor base station does not change, and if the anchor base station sends the context of the UE to the service base station, the service base station becomes the anchor base station of the UE. For example, when the UE1 is in the coverage of the base station1, the base station1 stores the context of the UE1, when the UE1 moves out of the coverage of the base station1 and enters the coverage of the base station2, the base station2 is the service base station of the UE1, if the base station1 does not send the context of the UE1 to the base station2, the role of the base station1 does not change, and the base station1 remains the anchor base station of the UE1. When the UE1 moves out of the coverage of the base station2 and enters the coverage of the base station3 again, the base station3 is the service base station of the UE1, if the base station1 does not send the context of the UE1 to the base station3, the role of the base station1 does not change, and the base station1 remains the anchor base station of the UE1, but if the base station1 sends the context of the UE1 to the base station3, the base station1 is no longer the anchor base station of the UE1, and the base station3 becomes the anchor base station of the UE1. It can be understood that, in addition to the anchor base station storing the context of the UE, other base stations can also serve as the service base station of the UE.

[0306] Exemplarily, in NR, the anchor base station can be referred to as an anchor gNB (anchor gNB), also referred to as a last serving gNB (last serving gNB), and also referred to as an old gNB (old gNB). The serving base station can be referred to as a new serving gNB (new serving gNB), also referred to as a current serving gNB (current serving gNB), and also referred to as a new gNB (new gNB).

[0307] For the sake of simplicity of description, the following embodiments refer to the anchor base station as an old station and the serving base station as a new station.

[0308] In some embodiments, the old station decides to perform anchor relocation, and the new station can obtain the context of the UE from the old station. For example, the specific process can refer to the following Figure 11 In some embodiments, the old station decides not to perform anchor relocation, and the new station cannot obtain the context of the UE from the old station. For example, the specific process can refer to the following Figure 12 .

[0309] For example, the specific process can refer to the following Figure 11 , Figure 11 Exemplarily, a flowchart of an anchor relocation process is shown. Figure 11 The process shown can include, but is not limited to, the following steps:

[0310] S411: The UE sends an RRC request message to the new station.

[0311] Specifically, when the UE initiates SDT at the new station, the UE can send an RRC request message to the new station, for example, send an RRCResumeRequest message when initiating RA-SDT. For example, the RRC request message in the SDT process shown above is not limited thereto, and can also be other RRC messages for initiating SDT. Figures 5-10 The RRC request message in the SDT process shown above is not limited thereto, and can also be other RRC messages for initiating SDT.

[0312] S412: The new station sends a first Xn interface message to the old station.

[0313] In some embodiments, the new station can send a first Xn interface message to the old station through the Xn interface to request to obtain the context of the UE.

[0314] In some embodiments, the first Xn interface message is a RetrieveUEContextRequest message.

[0315] In some embodiments, the RRC request message sent by the UE to the new station includes information of the old station, and the new station can obtain the information of the old station through the RRC request message, for example, the new station can obtain the information of the old station according to the I-RNTI carried in the RRCResumeRequest message.

[0316] S413: The old station sends a second Xn interface message to the new station in response to the first Xn interface message sent by the new station.

[0317] In some embodiments, the old station can send the second Xn interface message to the new station through the Xn interface in response to the request of the new station to obtain the context of the UE.

[0318] In some embodiments, when the old station decides to perform anchor relocation (which can also be understood as when the old station decides to replace the anchor base station), the old station can send the second Xn interface message to the new station through the Xn interface. Optionally, the second Xn interface message can include the context of the UE.

[0319] In some embodiments, the second Xn interface message is a RetrieveUEContextResponse message. S414: The new station sends a path switching request message to the core network device.

[0320] S415: The core network device sends a path switching response message to the new station.

[0321] Specifically, after obtaining the context of the UE, the new station can perform path switching, for example, performing S414 and S415, where the core network device is, for example, an AMF. After the new station performs path switching, the new station can perform the above-mentioned SDT with the UE. For details, see the SDT process shown in Figures 5-10 , where the new station is a base station.

[0322] S416: The new station sends an RRC response message to the UE.

[0323] Specifically, the new station can generate an RRC response message and send it to the UE. Optionally, the RRC response message is used to end the SDT between the new station and the UE, for example, when the UE has no SDT requirement, the new station performs S416. For details, see the RRC response message in the SDT process shown in Figures 5-10 .

[0324] Please refer to Figure 12 , Figure 12 A flowchart schematically showing another anchor relocation process is shown in Figure 12 The process shown can include but is not limited to the following steps:

[0325] S421: The UE sends an RRC request message to the new station.

[0326] S422: The new station sends a first Xn interface message to the old station.

[0327] Specifically, S421-S422 and S411-S412 are similar, and for details, refer to the description of S411-S412 in Figure 11 Figure 11 S411-S412 in

[0328] S423: The old station sends a third Xn interface message to the new station in response to the first Xn interface message sent by the new station.

[0329] In some embodiments, the old station can send the third Xn interface message to the new station through the Xn interface in response to the request of the new station to obtain the context of the UE.

[0330] In some embodiments, when the old station decides not to perform anchor relocation (which can also be understood as when the old station decides not to replace the anchor base station), the old station sends the third Xn interface message to the new station through the Xn interface. Optionally, the third Xn interface message can not include the entire context of the UE, for example, the third Xn interface message can not include the PDCP layer related context of the UE, and only include the RLC layer related context of the UE.

[0331] In some embodiments, the third Xn interface message is a Retrieve UE Context Failure message. In other embodiments, the third Xn interface message is a Retrieve UE Context Response message.

[0332] S424: The new station establishes a transmission tunnel.

[0333] Specifically, when the new station receives the third Xn interface message, it can establish a data transmission tunnel (tunnel), which can also be understood as performing forwarding tunnel establishment. In some embodiments, the transmission tunnel can be used for the new station to forward information of the SDT process for the UE and the old station, such as for performing S425.

[0334] S425: The UE performs small packet data transmission.

[0335] Specifically, the UE performing small packet data transmission can include the new station forwarding information of the SDT process for the UE and the old station, and for details, refer to the description of S425 in Figures 5-10 ​The illustrated SDT procedure is similar, except that the base station is replaced by the new station and the old station, optionally, the new station is used to perform the steps of the base station transmitting information, and optionally, the old station is used to perform the steps of the base station generating information.

[0336] In some embodiments, the new station can forward the information of the above SDT procedure from the old station to the UE, for example, the new station can forward the RRC request message from the old station to the UE after receiving the RRC request message from the UE, for another example, the new station can forward the downlink small packet data from the old station to the UE after receiving the uplink small packet data from the UE, for another example, the new station can forward the information of the subsequent transmission stage from the old station to the UE.

[0337] In some embodiments, the new station can forward the information of the above SDT procedure from the old station to the UE, for example, the old station generates the RRC response message and sends it to the new station, and the new station can forward the RRC response message to the UE (e.g., S426), for another example, the new station can forward the downlink small packet data sent by the old station to the UE in S426, for another example, the new station can forward the information of the subsequent transmission stage sent by the old station to the UE.

[0338] S426: The new station sends the RRC response message to the UE.

[0339] Specifically, the new station can forward the RRC response message from the old station to the UE, wherein the RRC response message is generated by the old station, and optionally, the RRC response message is used to end the SDT between the new station and the UE, for example, the new station forwards the RRC response message when the UE has no need for SDT, and examples of the RRC response message can be referred to the above Figures 5-10 The RRC response message in the illustrated SDT procedure.

[0340] In some embodiments, the RRC response message sent by the old station to the new station is included in the third Xn interface message of S423, for example, the new station can first store the RRC response message after receiving the third Xn interface message, and then send the RRC response message to the UE when the UE has no need for SDT. For example, the RRC response message is an RRCRelease message.

[0341] In some embodiments, the RRC response message sent by the old station to the new station can be included in the third Xn interface message at S423, and can be included in other Xn interface messages, for example, when the old station determines that the UE has no SDT requirement, the old station sends an Xn interface message (for example, a UE CONTEXT RELEASE message, or an RRC TRANSFER message, or other existing Xn interface messages, or a new Xn interface message) including the RRC response message to the new station, and the new station sends the RRC response message to the UE based on the Xn interface message. Illustratively, Figure 1 In the illustrated communication system, the current serving cell of the UE 110 corresponds to the base station 210, but the base station 210 does not store the context of the UE 110, i.e., the base station 210 is a new station for the UE 110. Before the UE 110 moves to the base station 210, it is in the coverage of the base station 230, and the base station 230 stores the context of the UE 110, i.e., the base station 230 is an old station for the UE 110. When the UE 110 initiates SDT under the base station 210, the base station 210 can request the base station 230 to obtain the context of the UE 110. If the base station 230 decides to perform anchor relocation, the base station 210 can obtain the context of the UE 110, and the base station 210 can directly perform the above-mentioned SDT with the UE 110, for example, the above-mentioned RA-SDT or CG-SDT. Figure 11 In the illustrated communication system, the current serving cell of the UE 110 corresponds to the base station 210, but the base station 210 does not store the context of the UE 110, i.e., the base station 210 is a new station for the UE 110. Before the UE 110 moves to the base station 210, it is in the coverage of the base station 230, and the base station 230 stores the context of the UE 110, i.e., the base station 230 is an old station for the UE 110. When the UE 110 initiates SDT under the base station 210, the base station 210 can request the base station 230 to obtain the context of the UE 110. If the base station 230 decides to perform anchor relocation, the base station 210 can obtain the context of the UE 110, and the base station 210 can directly perform the above-mentioned SDT with the UE 110, for example, the above-mentioned RA-SDT or CG-SDT. Figure 12 In the illustrated communication system, the current serving cell of the UE 110 corresponds to the base station 210, but the base station 210 does not store the context of the UE 110, i.e., the base station 210 is a new station for the UE 110. Before the UE 110 moves to the base station 210, it is in the coverage of the base station 230, and the base station 230 stores the context of the UE 110, i.e., the base station 230 is an old station for the UE 110. When the UE 110 initiates SDT under the base station 210, the base station 210 can request the base station 230 to obtain the context of the UE 110. If the base station 230 decides to perform anchor relocation, the base station 210 can obtain the context of the UE 110, and the base station 210 can directly perform the above-mentioned SDT with the UE 110, for example, the above-mentioned RA-SDT or CG-SDT.

[0342] When the terminal and the network device perform SDT, the terminal can not be able to continue the SDT, and specific scenarios are shown as follows (assuming that the terminal is a multi-card terminal including a sub-device A and a sub-device B):

[0343] Scenario one: when the sub-device A and the network device perform SDT (for example, RA-SDT or CG-SDT), if the sub-device B has data transmission requirements and the data transmission requirements require the sub-device B to enter the RRC CONNECTED state, for example, to enter the RRC CONNECTED state for non-SDT data transmission, in order to perform the data transmission of the sub-device B, the device A needs to stop the current SDT.

[0344] Scenario two: when the child device A and the network device perform SDT (for example, RA-SDT or CG-SDT), if the child device B needs to send a system information request or receive downlink messages, such as paging, system information, periodic downlink messages of radio resource management (RRM), or other non-periodic downlink messages, in order to perform data transmission of the child device B, the child device A needs to stop the current SDT.

[0345] In the above case, the network device will still schedule resources for the SDT, for example, the network device in communication with the child device A cannot know that the child device A no longer continues to listen to the scheduling for the SDT, but performs service transmission of the child device B, and therefore will continue to schedule resources for the SDT for the child device A. That is, there is a problem of wasting air interface resources, and there is also a lack of an efficient transmission scheme that can be applied to the above case.

[0346] Embodiments of the present application provide a method for controlling transmission, which can be applied to a communication system, the communication system can include a first device and a first network device, and the first device can send information indicating that it no longer continues to listen to SDT to the first network device, thereby avoiding the case that the first network device continues to schedule resources for the SDT when the first device no longer listens to the SDT, and saving air interface resources.

[0347] Next, the method for controlling transmission provided by the embodiments of the present application is described based on the above description.

[0348] The method can be applied to a communication system, for example Figure 1 The communication system can include a first device and a first network device, and in some embodiments, the communication system further includes a second network device.

[0349] In some embodiments, the first device is a multi-card terminal, and the multi-card terminal includes a first child device, for example, the first device is a multi-card terminal 100 as shown in Figure 1 The first device can perform the method for controlling transmission through the first child device, that is, in the following method for controlling transmission, the first device can be replaced by the first child device, and the first device (performing steps) can be replaced by the first device performing steps through the first child device. In other embodiments, the first device is a child device included in a multi-card terminal, for example, the first device is a UE 110 or a UE 120 included in a multi-card terminal 100 as shown in Figure 1 The following embodiments take the first device as a child device included in a multi-card terminal as an example for description.

[0350] In some embodiments, the network device corresponding to the current serving cell of the first device is the first network device, and the first network device stores the user context of the first device. For example, the first device moves to the first network device, and the first network device obtains the user context of the first device from the anchor device when the SDT is initiated under the first network device. For specific examples, please refer to the flowchart shown in Figure 11 For example, the first device is the multi-card terminal 100 shown in Figure 1 or the UE 120 included in the multi-card terminal 100, and the first network device is the base station 220.

[0351] In some embodiments, the network device corresponding to the current serving cell of the first device is the first network device, and the first network device does not store the user context of the first device. The user context of the first device is stored in the second network device. For example, the first device moves to the first network device, and the first network device can request the second network device to obtain the user context of the first device when the SDT is initiated under the first network device. However, the second network device decides not to perform anchor relocation, that is, the second network device is still the anchor device of the first device. Therefore, the first network device does not obtain the user context of the first device from the second network device. For specific examples, please refer to the flowchart shown in Figure 12 That is, the first network device is a new station, and the second network device is an old station. For example, the first device is the multi-card terminal 100 shown in Figure 1 or the UE 120 included in the multi-card terminal 100, the first network device is the base station 210, and the second network device is the base station 230.

[0352] Please refer to Figure 13 , Figure 13 is a flowchart of a method for controlling transmission provided by an embodiment of the present application. The method includes but is not limited to the following steps:

[0353] S510: The first device receives first configuration information.

[0354] In some embodiments, S510 is an optional step.

[0355] In some embodiments, the first device is a multi-card terminal, the multi-card terminal includes a first sub-device, and the first device receives the first configuration information through the first sub-device. In some embodiments, the first device is a first sub-device included in a multi-card terminal, and the first device receives the first configuration information. The following description takes the first device as a first sub-device included in a multi-card terminal as an example.

[0356] In some embodiments, the first configuration information indicates reporting of the first information, optionally, the first configuration information indicates establishing and / or releasing reporting of the first information, optionally, the first configuration information indicates enabling and / or disabling reporting of the first information, optionally, the first configuration information indicates that the device (e.g., the first device) can report the first information, optionally, the first configuration information indicates that the current network device (e.g., the first network device) supports reporting of the first information by the device (e.g., the first device), optionally, the first configuration information indicates that the device (e.g., the first device) can report the first information in the RRC INACTIVE state. In some embodiments, the first information indicates a request to stop SDT, which can be seen from the description of the first information in S530, and will not be described in detail here.

[0357] In some embodiments, the first configuration information includes a time length of the first timer, in other embodiments, the time length of the first timer is sent to the first device through other messages, and in other embodiments, the time length of the first timer is predefined, for example, the time length of the first timer is defined in the 3GPP protocol. The first timer is used by the first device to listen for a response message of the first information.

[0358] In some embodiments, the first timer can be a third timer used by the multi-card terminal to report a request to leave the RRC CONNECTED state, and in other embodiments, the first timer can be a newly defined timer. For example, considering that the first device initiates RA-SDT, there can be signaling interaction (e.g., interaction of the time length of the first timer) between the first network device and the second network device, so the time length of the newly defined first timer is greater than that of the third timer.

[0359] In some embodiments, the first configuration information and the time length of the first timer can be configured in any of the following ways, but not limited to:

[0360] Method one: the first configuration information is sent to the first device through broadcast system information (e.g., system information block (SIB) 1), and the first configuration information includes the time length of the first timer.

[0361] In a possible implementation, the first device receives the first configuration information sent by the first network device through broadcast system information. For example, the first device moves to the first network device, and the first device reads the system information broadcast by the first network device.

[0362] In some embodiments, the first configuration information comprises a first field, and the first device can read the first field in the system information and the length of the first timer. The first field can indicate that the current network device (e.g., the first network device) supports the device (e.g., the first device) to report the first information, and / or the device (e.g., the first device) can report the first information. For example, the first configuration information indicates to enable and / or disable the reporting of the first information. The first field and the length of the first timer are optional fields in the SIB1, and both the first field and the length of the first timer are enumeration types. When the value of the first field in the SIB1 is "true", it indicates that "the current base station supports the UE to report the first information, and the UE can report the first information", and the length of the first timer is the length indicated in the SIB1.

[0363] In some other embodiments, the first configuration information indicates to establish and / or release the reporting of the first information. For example, when the first configuration information in the SIB1 indicates "establish", it indicates that "the current base station supports the UE to report the first information, and the UE can report the first information", and when the first configuration information in the SIB1 indicates "release", it indicates that "the current base station does not support the UE to report the first information, and the UE cannot report the first information". The first configuration information in the SIB1 comprises the length of the first timer.

[0364] In some other embodiments, the first configuration information does not comprise the first field. When the system information comprises the length of the first timer, it indicates that the current network device supports the device to report the first information, and / or the device can report the first information. For example, the length of the first timer is an optional field in the SIB1, the length of the first timer is an enumeration type, and the length of the first timer is the length indicated in the SIB1. When the SIB1 comprises the length of the first timer, it indicates that "the current base station supports the UE to report the first information, and the UE can report the first information".

[0365] Option 2: The first configuration information is sent to the first device through the broadcast system information (e.g., SIB1), and the length of the first timer is sent to the first device through the RRC message.

[0366] In a possible implementation, the first device receives the first configuration information sent by the first network device through the broadcast system information. For example, the first device moves to the first network device, and the first device reads the system information broadcast by the first network device.

[0367] In some embodiments, the first configuration information includes a first field, the first device can read the first field in the system information, the first field can indicate that the current network device supports the device to report the first information, and / or the device can report the first information. For example, the first configuration information indicates to enable and / or disable the reporting of the first information. The first field is an optional field in the SIB1, the first field is an enumeration type, and when the value of the first field in the SIB1 is "true", it indicates that "the current base station supports the UE to report the first information, and the UE can report the first information". In other embodiments, the first configuration information indicates to establish and / or release the reporting of the first information. For example, when the first configuration information in the SIB1 indicates "establish", it indicates that "the current base station supports the UE to report the first information, and the UE can report the first information", and when the first configuration information in the SIB1 indicates "release", it indicates that "the current base station does not support the UE to report the first information, and the UE cannot report the first information".

[0368] In a possible implementation, the first device receives the duration of the first timer sent by the first network device through an RRC message. For example, the RRC message is an RRC Reconfiguration message sent by the first network device when the first device and the first network device perform SDT.

[0369] In another possible implementation, the first device receives the duration of the first timer sent by the second network device through an RRC message. Optionally, the user context of the first device stored by the second network device includes the duration of the first timer. For example, the RRC message is an RRC Release message, and the first device enters the RRC INACTIVE state from the RRC CONNECTED state after receiving the RRC Release message. For another example, the RRC message is an RRC Release message used to end the SDT. For another example, the RRC message is an RRC Reconfiguration message sent by the second network device when the first device and the second network device perform SDT. For another example, the RRC message is an RRC Reconfiguration message sent by the second network device when the first device is in the RRC CONNECTED state. Optionally, the first device does not release the configured duration of the first timer when initiating a resume procedure corresponding to the SDT under the first network device.

[0370] In some embodiments, when the RRC message is an RRC Reconfiguration message, the duration of the first timer can be indicated by an OtherConfig IE in the RRC Reconfiguration message, and is not limited thereto. The duration of the first timer can also be indicated by other existing IEs or newly added IEs.

[0371] In some embodiments, when the RRC message is the RRCRelease message, the duration of the first timer can be indicated by a suspendconfig IE in the RRCRelease message, or the duration of the first timer can be indicated by an SDTConfig IE in the RRCRelease message, or the duration of the first timer can be indicated by other existing IEs or newly added IEs.

[0372] The RRC message is not limited to the above examples, and other types of RRC messages can also be used, such as the RRC response message of the SDT procedure shown in Figures 5-12 The present application does not limit the RRC response message of the SDT procedure.

[0373] Method three: the first configuration information is sent to the first device by an RRC message, and in some embodiments, the first configuration information includes the duration of the first timer, and in other embodiments, the duration of the first timer is sent to the first device by other RRC messages.

[0374] In a possible implementation, the first device receives first configuration information sent by the first network device through a first RRC message, and the first configuration information includes the duration of the first timer.

[0375] In another possible implementation, the first device receives first configuration information sent by the second network device through a second RRC message, and the first configuration information includes the duration of the first timer.

[0376] In another possible implementation, the first device receives first configuration information sent by the first network device through a first RRC message, and receives the duration of the first timer sent by the second network device through a second RRC message.

[0377] In another possible implementation, the first device receives the duration of the first timer sent by the first network device through a first RRC message, and receives first configuration information sent by the second network device through a second RRC message.

[0378] Examples of the first RRC message can refer to the RRC message used by the first network device to send the duration of the first timer in method two, and examples of the second RRC message can refer to the RRC message used by the second network device to send the duration of the first timer in method two.

[0379] In some embodiments, the first configuration information includes a first field and a length of the first timer, and the first device can read the first field and the length of the first timer in the RRC message. The first field can indicate that the device (e.g., the first device) can report the first information. For example, the first configuration information indicates to enable and / or disable the reporting of the first information. The first field and the length of the first timer are optional fields in the RRC message, and the first field and the length of the first timer are both enumerated types. When the value of the first field in the RRC message is "true", it indicates that "the UE can report the first information", and the length of the first timer is the length indicated in the RRC message.

[0380] In some other embodiments, the first configuration information indicates to establish and / or release the reporting of the first information. For example, when the first configuration information in the RRC message indicates "establish", it indicates that "the UE can report the first information", and when the first configuration information in the RRC message indicates "release", it indicates that "the UE cannot report the first information". The first configuration information in the RRC message includes the length of the first timer.

[0381] In some other embodiments, the first configuration information includes the length of the first timer but does not include the first field. When the RRC message includes the length of the first timer, it indicates that the device can report the first information. For example, the length of the first timer is an optional field in the RRC message, and the length of the first timer is an enumerated type. The length of the first timer is the length indicated in the RRC message, and when the RRC message indicates the length of the first timer, it indicates that "the UE can report the first information".

[0382] In some embodiments, the method further includes that the first device receives system information (e.g., SIB1) sent by the first network device, and the system information can indicate that the current network device (e.g., the first network device) supports the device (e.g., the first device) to report the first information. For example, when the value of the first support information in the SIB1 is "true", it indicates that "the current base station supports the UE to report the first information".

[0383] In some other embodiments, the first configuration information is sent to the first device through an RRC message, and the length of the first timer is sent to the first device through broadcast system information (e.g., SIB1).

[0384] In a possible implementation, the first device receives the first configuration information sent by the first network device through an RRC message. An example of the RRC message can be referred to the RRC message used by the first network device to send the length of the first timer in the manner two.

[0385] In yet another possible implementation, the first device receives the first configuration information sent by the second network device through an RRC message. An example of the RRC message can be referred to the RRC message used by the second network device to send the length of the first timer in way two.

[0386] In some embodiments, the first configuration information includes a first field, and the first device can read the first field in the RRC message. The first field can indicate that the device can report the first information. For example, the first configuration information indicates to enable and / or disable the reporting of the first information. The first field is an optional field in the RRC message, and the first field is an enumeration type. When the value of the first field in the RRC message is "true", it means that "the UE can report the first information".

[0387] In other embodiments, the first configuration information indicates to establish and / or release the reporting of the first information. For example, when the first configuration information in the RRC message indicates "establish", it means that "the UE can report the first information". When the first configuration information in the SIB1 indicates "release", it means that "the UE cannot report the first information".

[0388] In a possible implementation, the first device receives the length of the first timer sent by the first network device through broadcast system information. For example, the length of the first timer is an optional field in the SIB1, the length of the first timer is an enumeration type, and the length of the first timer is the length indicated in the SIB1. Optionally, when the system information includes the length of the first timer, it means that the current network device (such as the first network device) supports the device (such as the first device) to report the first information. For example, when the SIB1 indicates the length of the first timer, it means that "the current base station supports the UE to report the first information".

[0389] In some embodiments, the method further includes that the first device receives the system information (such as the SIB1) sent by the first network device, which can indicate that the current network device (such as the first network device) supports the device (such as the first device) to report the first information. For example, when the value of the first support information in the SIB1 is "true", it means that "the current base station supports the UE to report the first information".

[0390] Way five: the first configuration information is sent to the first device through an RRC message or broadcast system information, and the length of the first timer is predefined.

[0391] In some embodiments, the length of the first timer is a protocol predefined length. In other embodiments, the length of the first timer is pre-coordinated by the first device and the first network device. Optionally, the length of the first timer is pre-coordinated by the first device, the first network device, and the second network device.

[0392] In a possible implementation, the first device receives the first configuration information sent by the first network device through broadcast system information. For example, the first device moves under the first network device, and reads the broadcast system information of the first network device. In some embodiments, the description of the first configuration information can refer to the description of the first configuration information in Mode 2.

[0393] In another possible implementation, the first device receives the first configuration information sent by the first network device through an RRC message. For example, the RRC message used by the first network device to send the length of the first timer can refer to the RRC message in Mode 2. In another possible implementation, the first device receives the first configuration information sent by the second network device through an RRC message. For example, the RRC message used by the second network device to send the length of the first timer can refer to the RRC message in Mode 2. In some embodiments, the description of the first configuration information can refer to the description of the first configuration information in Mode 4.

[0394] In some embodiments, before the first device receives the first configuration information, and / or before the first device receives the length of the first timer, the first device can send a first request message. Optionally, the first device sends the first request message to the first network device. Optionally, the first device sends the first request message to the second network device. The first request message indicates a request for reporting the first configuration information. For example, the first device sends an on-demand system (ondemand SI) message, an RRC message (such as the RRC request message in the SDT shown in the above table or the RRC message carried by the DCCH) or a media access layer control element (MAC control element, MAC CE) to request the network device to report the first configuration information. Figures 5-10

[0395] S520: The first device performs the SDT.

[0396] In some embodiments, S520 is an optional step.

[0397] In some embodiments, the first device is a multi-card terminal including a first sub-device, the first sub-device in the first device is in the non-RRC connected state, and the first device initiates the SDT under the first network device through the first sub-device. In some embodiments, the first device is a multi-card terminal including a first sub-device, the first device is in the non-RRC connected state, and the first device initiates the SDT under the first network device. The following description takes the first device as an example of the first sub-device included in the multi-card terminal.

[0398] ​In some embodiments, the first device is currently served by a first network device storing a user context of the first device. When the first device initiates SDT under the first network device, the first device can directly perform SDT with the first network device, for example, the SDT procedure shown in FIG. 5A. Figures 5-10 In some embodiments, the first device is currently served by a first network device storing a user context of the first device. When the first device initiates SDT under the first network device, the first device can directly perform SDT with the first network device, for example, the SDT procedure shown in FIG. 5A.

[0399] In some embodiments, the first device is currently served by a first network device storing a user context of the first device. When the first device initiates SDT under the first network device, the first device can directly perform SDT with the first network device, for example, the SDT procedure shown in FIG. 5A. Figure 12 In some embodiments, the first device is currently served by a first network device storing a user context of the first device. When the first device initiates SDT under the first network device, the first device can directly perform SDT with the first network device, for example, the SDT procedure shown in FIG. 5A.

[0400] In some embodiments, the SDT is RA-SDT, and the specific procedure can refer to FIG. 5A. Figures 9-10 In some embodiments, the SDT is CG-SDT, and the specific procedure can refer to FIG. 5B. Figures 5-8

[0401] The order of S510 and S520 is not limited.

[0402] S530: The first device sends first information to the first network device.

[0403] Specifically, the first information indicates a request to stop SDT (e.g., the SDT in S520), and optionally, the request to stop SDT can be replaced by a desire to stop SDT.

[0404] In some embodiments, the first device is a multi-card terminal including a first sub-device, and the first device sends the first information to the first network device through the first sub-device. Optionally, the first information indicates that the first sub-device requests to stop SDT, and optionally, the first information indicates a request to stop SDT of the first sub-device. In some embodiments, the first device is a first sub-device included in a multi-card terminal, and the first device sends the first information to the first network device. Optionally, the first information indicates that the first device requests to stop SDT, and optionally, the first information indicates a request to stop SDT of the first device. The following description takes the first device as a first sub-device included in a multi-card terminal as an example.

[0405] ​In some embodiments, the first device sends the first information to the first network device when the first device is in the non-RRC connected state. In some embodiments, the first device can send the first information to the first network device in a case where the first device intends to initiate or initiates an SDT (such as the SDT in S520) under the first network device.

[0406] In some embodiments, the first device sends the first information to the first network device when the second sub-device needs to enter the RRC connected state from the non-RRC connected state, and optionally, the second sub-device is in the RRC non-connected state. In some embodiments, the first device sends the first information to the first network device when the multi-card terminal needs to switch from the SDT service to the RRC CONNECTED state service, which can also be referred to as the first device sending the first information to the first network device due to the multi-card reason. For specific examples, refer to the above-mentioned scenario one in which the terminal cannot continue the SDT when the terminal and the network device perform the SDT, which is not limited thereto, and can also be applied to scenario two and other scenarios.

[0407] For example, the multi-card terminal is a smart phone, which can be installed with two phone cards, i.e., the first sub-device and the second sub-device. When the user transmits instant messaging messages through one phone card (i.e., the first sub-device) on the smart phone and other terminals, for example, the mobile data of the first sub-device is used at this time, and the first network device and other terminals are communicated, the smart phone can receive an incoming call for the other phone card (i.e., the second sub-device). When the user answers the incoming call using the smart phone (of the second sub-device), the instant messaging messages cannot be continued to be transmitted through the first sub-device, and the first sub-device can send the first information to the first network device.

[0408] In a possible implementation, the first information can be sent through an RRC message carried by a DCCH, such as a user equipment assistance information (UEAssistanceInformation), a user equipment capability information (UECapabilityInformation), or other messages carried by a DCCH. In some embodiments, the first information can be an existing field in the RRC message carried by the DCCH. For example, the first information is a release preference (ReleasePreference) IE in the UEAssistanceInformation message, and the ReleasePreference IE can include a parameter: preferred RRC state (preferredRRC-State), the value of the preferredRRC-State can be idle, inactive, or connected, when the value of the preferredRRC-State is inactive, the first device can request the first network device to stop the current SDT. In other embodiments, the first information can be a newly added field in the RRC message carried by the DCCH. For example, the first information is a new IE (new IE) in the UEAssistanceInformation message.

[0409] In a possible implementation, the above SDT is a RA-SDT (for specific examples, refer to the above Figures 9-10 In some embodiments, the first device can send the first information to the first network device before receiving the contention resolution message or the msgB, for example, before sending the RRC request message, for example, when sending the RRC request message (for example, the RRC request message carries the first information). In other embodiments, the first device can send the first information in the subsequent transmission phase after receiving the contention resolution message or the msgB, for example, the first device sends the first information on the dynamically scheduled uplink resource. Not limited to the above examples, in other embodiments, if the first device intends to initiate the RA-SDT, it also intends to send the first information, for example, intends to send the first information before sending the RRC request message, whether to send the first information and whether to continue the current SDT can be determined according to the implementation, for example, not to send the first information, and cancel the current SDT (may not send the RRC request message).

[0410] In another possible implementation, the above SDT is a CG-SDT (for specific examples, refer to the above Figures 5-10), in some embodiments, the first device can send the first information to the first network device before receiving the feedback response message, for example, sending the first information before sending the RRC request message, for another example, sending the first information when sending the RRC request message, in other embodiments, the first device can send the first information in the subsequent transmission phase after receiving the feedback response message, for example, the first device sends the first information on the dynamically scheduled uplink resource, for another example, the first device sends the first information on the CG-SDT resource. Not limited to the above examples, in other embodiments, if the first device intends to initiate CG-SDT, it also intends to send the first information, for example, it intends to send the first information before sending the RRC request message, whether to send the first information and whether to continue the current SDT can be decided according to the implementation of the first device, for example, not sending the first information, and canceling the current SDT (may not send the RRC request message).

[0411] In some embodiments, when the first device sends the first information, the first timer is started, and optionally, the first timer is used for the first device to listen to the response message of the first information, and optionally, during the running of the first timer, the first device listens to the response message (for example, the first response message in S550) sent by the first network device. For examples of the response message in the SDT shown in the above Figures 11-12 The RRC response message in the SDT shown in the above

[0412] In some embodiments, if the first device receives the response message sent by the first network device (for example, the first network device performs S550) before the first timer expires, the first device can stop the first timer, which will not be described in detail for the moment. In other embodiments, if the first device has not received the response message (for example, the first response message in S550) sent by the first network device when the first timer expires, the first device can enter the RRC IDLE state.

[0413] In some embodiments, after the first device sends the first information, it will not listen to the scheduling of the SDT, but the second sub-device will perform data transmission.

[0414] S540: Transmission of the first information and other related information between the first network device and the second network device.

[0415] In some embodiments, S540 is an optional step.

[0416] In some embodiments, the first network device corresponding to the current serving cell of the first device does not store the user context of the first device, but the user context of the first device is stored in the second network device, that is, the first network device is the new station and the second network device is the old station. In this case, after receiving the first information sent by the first device, the first network device forwards the first information to the second network device. Optionally, S540 is executed in a scenario where the old station (second network device) decides not to perform anchor relocation, and the new station (first network device) cannot obtain the user context of the first device from the old station (second network device). Optionally, the SDT initiated by the first device is RA-SDT, that is, S540 is executed in a scenario of RA-SDT without changing the anchor device.

[0417] In some embodiments, the first network device and the second network device exchange information through Xn interface messages. The following description uses Xn interface messages as an example to illustrate the message exchanged between the first network device and the second network device.

[0418] In some embodiments, after receiving the first information sent by the first device, the first network device may send a first message to the second network device. The first message includes the first information. Optionally, the first message is the above... Figures 5-10 The first Xn interface message shown (e.g., the RetrieveUEContextRequest message), or other existing Xn interface messages, or new Xn interface messages.

[0419] In some embodiments, the first network device may receive a second message sent by the second network device. The second message includes a first response message. The second message is used by the first network device to send the first response message to the first network device before the first timer expires. For example, the second message is used by the first network device to execute S550. An example of the first response message can be found above. Figure 12 The RRC response message in the SDT shown is, for example, the RRC Release message. The second message is, for example, the above... Figure 12 The third Xn interface message shown (such as the RetrieveUEContextFailure message), or other existing Xn interface messages, or new Xn interface messages.

[0420] In some embodiments, before the first network device sends a first message to the second network device, it receives a second message sent by the second network device. Optionally, the second message is... Figure 12The third Xn interface message shown is, for example, a RetrieveUEContextFailure message. In other embodiments, after the first network device sends the first message to the second network device, the second network device sends the second message to the first network device. Optionally, the second network device can generate a first response message based on the first information in the first message, and generate the second message including the first response message.

[0421] In some embodiments, the first network device and the second network device can transmit a message including the duration of the first timer between them, as described below.

[0422] In one possible implementation, the first configuration information and the duration of the first timer are configured in the manner one or manner four in S510, i.e., the first timer used by the first device is configured for the first device by the first network device through broadcast system information (such as SIB1). In some embodiments, the duration of the first timer is generated by the first network device, and in other embodiments, the duration of the first timer is sent by the second network device to the first network device through a fifth message before the first timer is configured for the first device, and the fifth message includes the duration of the first timer.

[0423] In another possible implementation, the first configuration information and the duration of the first timer are configured in the manner two or manner three in S510, i.e., the first timer used by the first device is configured for the first device by the first network device or the second network device through an RRC message. In some embodiments, the first timer used by the first device is the first timer in the context of the first device stored by the second network device, and in other embodiments, the first timer used by the first device is configured for the first device by the first network device. In one possible case, the duration of the first timer is generated by the first network device, and in another possible case, the duration of the first timer is sent by the second network device to the first network device through a fifth message before the first timer is configured for the first device, and the fifth message includes the duration of the first timer.

[0424] In another possible implementation, the first configuration information and the duration of the first timer are configured in the manner five in S510, i.e., the duration of the first timer used by the first device is predefined, and the first network device and the second network device can not interact the duration of the first timer.

[0425] In some embodiments, the first timer used by the first device is a first timer in a context of the first device stored by the second network device. After the first network device receives the first information sent by the first device, the first network device can receive a third message sent by the second network device, the third message comprising a time length of the first timer, the time length of the first timer can be used for the first network device to send a first response message to the first device before the first timer expires, for example, the time length of the first timer is used for the first network device to perform S550. In one possible case, the second message comprising the first response message is not the third Xn interface message shown in FIG. 6, at this time the transmission process of the first network device and the second network device is as shown in FIG. 7. Figure 14 In another possible case, the second message comprising the first response message is the third Xn interface message shown in FIG. 6, at this time the transmission process of the first network device and the second network device is as shown in FIG. 8. Figure 12 In another possible case, the second message comprising the first response message is the third Xn interface message shown in FIG. 6, at this time the transmission process of the first network device and the second network device is as shown in FIG. 8. Figure 15 In another possible case, the second message comprising the first response message is the third Xn interface message shown in FIG. 6, at this time the transmission process of the first network device and the second network device is as shown in FIG. 8. Figure 12

[0426] In some embodiments, the first timer used by the first device is a first timer in a context of the first device stored by the second network device. After the first network device receives the first information sent by the first device, the first network device can receive a third message sent by the second network device, the third message comprising a time length of the first timer, the time length of the first timer can be used for the first network device to send a first response message to the first device before the first timer expires, for example, the time length of the first timer is used for the first network device to perform S550. In one possible case, the second message comprising the first response message is not the third Xn interface message shown in FIG. 6, at this time the transmission process of the first network device and the second network device is as shown in FIG. 7. Figure 16 In another possible case, the second message comprising the first response message is the third Xn interface message shown in FIG. 6, at this time the transmission process of the first network device and the second network device is as shown in FIG. 8. Figure 12 In another possible case, the second message comprising the first response message is the third Xn interface message shown in FIG. 6, at this time the transmission process of the first network device and the second network device is as shown in FIG. 8. Figure 12 In another possible case, the second message comprising the first response message is the third Xn interface message shown in FIG. 6, at this time the transmission process of the first network device and the second network device is as shown in FIG. 8.

[0427] ​In some embodiments, the first timer used by the first device is configured by the first network device for the first device, and the duration of the first timer is sent by the second network device to the first network device through a fifth message before the duration of the first timer is configured for the first device, and the fifth message includes the duration of the first timer. For example, in the Xn Setup Procedure, the second network device sends an XN SETUP RESPONSE message to the first network device, and the duration of the first timer is indicated through the XN SETUP RESPONSE message. For another example, in the NG RAN Node Configuration Update Procedure, the second network device sends an NGRAN CONFIGURATION UPDATE REQUEST message to the first network device, and the duration of the first timer is indicated through the NGRAN CONFIGURATION UPDATE REQUEST. Optionally, in this case, the first network device can not send the duration of the first timer to the second network device, and optionally, the order in which the first network device sends the first message including the first information to the second network device and the second network device sends the second message including the first response message to the first network device is not limited.

[0428] In some embodiments, the first network device can send the duration of the timer to the second network device through the Xn interface message multiple times, and specific examples can be referred to the examples of the fifth message described above. If the response message received by the first network device from the second network device does not include the duration of the timer, the first network device determines that the duration of the timer sent to the second network device as described above is the duration of the first timer. If the response message received by the first network device from the second network device includes the duration of the timer, the first network device determines that the duration of the timer sent by the second network device is the duration of the first timer.

[0429] In some other embodiments, the first timer used by the first device is predefined. In one possible case, the second message including the first response message is not the third Xn interface message shown in the above Figure 12 In some other embodiments, the first timer used by the first device is predefined. In one possible case, the second message including the first response message is not the third Xn interface message shown in the above Figures 5-10The third Xn interface message is shown. The first network device can send the first response message to the first device based on the length of the first timer, for example, before the first timer expires.

[0430] S550: The first network device sends a first response message (for example, an RRCRelease message) to the first device.

[0431] In some embodiments, S550 is an optional step.

[0432] In some embodiments, after the first device receives the first response message, the first timer is stopped. Optionally, the first device can wait for a subsequent re-initiation of the SDT.

[0433] Without being limited to the above example, in another embodiment, when the first device has not received the first response message sent by the first network device when the first timer expires, the first device enters the RRC IDLE state.

[0434] Examples of the first response message can be found in the above Figure 13 The RRC response message in the SDT is shown.

[0435] In some embodiments, the above device can report the first information, including: the device can report the first information in the RRC INACTIVE state, for example, the UE can report the first information, including: the UE can report the first information in the RRC INACTIVE state.

[0436] In Figure 14 In the method shown, the first device can send the first information to the first network device, indicating a request to stop the SDT through the first information, so as to avoid the first network device still scheduling resources for the SDT for the first device when the first device stops listening to the SDT, saving air interface resources.

[0437] Next, the specific implementation of S540 is exemplarily introduced.

[0438] In one possible implementation, the first timer used by the first device is the first timer in the context of the first device stored by the second network device, and the second message including the first response message is not the above Figure 14 The third Xn interface message is shown. In some embodiments, the first timer and the first response message can be sent to the second network device together, and the specific process is as follows Figure 14 As shown in (A) of FIG. 1, Figure 14 As shown in (B) of FIG. 1.

[0439] Please refer to Figure 13 (A), Figure 14FIG. 5B is an exemplary flowchart illustrating another method of controlling transmission. The method includes, but is not limited to, the following steps:

[0440] S5411: The second network device sends a third Xn interface message to the first network device.

[0441] S5412: The first network device sends a first message including the first information to the second network device.

[0442] The order of S5411 and S5412 is not limited, and optionally, the order of S530 and S540 is not limited. Figure 14 The order of S530 and S540 is not limited.

[0443] In some embodiments, S5411 is performed before S5412, for example, the first device initiates RA-SDT under the first network device, and the first device sends the first information to the first network device in the subsequent transmission phase after receiving the contention resolution message or msgB, and for another example, the first device initiates CG-SDT under the first network device, and the first device sends the first information to the first network device in the subsequent transmission phase after receiving the feedback response message. In this case, the first network device sends the first Xn interface message to the second network device and receives the third Xn interface message sent by the second network device before the first network device receives the first information sent by the first device. Optionally, in this case, part of the steps in S540 (such as S5411) is before S530, and part of the steps (such as S5412 and S5413) is after S530.

[0444] In other embodiments, S5411 is performed after S5412, for example, the first device initiates RA-SDT under the first network device, and the first device sends the first information to the first network device before receiving the contention resolution message or msgB, and for another example, the first device initiates CG-SDT under the first network device, and the first device sends the first information to the first network device before receiving the feedback response message. In this case, the first network device can first receive the first information sent by the first device, and then send the first Xn interface message to the second network device and receive the third Xn interface message sent by the second network device, and optionally, the first network device can send the first message including the first information to the second network device after receiving the first information sent by the first device, for example, the RetrieveUEContextRequest message or other first Xn interface message. Optionally, in this case, S530 is before S540.

[0445] S5413: The second network device sends, to the first network device, a message comprising the first response message and the length of the first timer.

[0446] In particular, the second message comprising the first response message and the third message comprising the length of the first timer are the same, for example, other existing Xn interface messages except the third Xn interface message, or a new Xn interface message.

[0447] In some embodiments, after receiving the first message, the second network device can generate the first response message based on the first information in the first message, and optionally, generate the first response message based on the length of the first timer and the first information. In some embodiments, the second network device can send, to the first network device, the second message comprising the first response message based on the length of the first timer. Optionally, in the above case, the first network device can send the first response message to the first device before the first timer expires.

[0448] In some embodiments, after receiving the Xn interface message comprising the first response message and the length of the first timer, the first network device can send the first response message to the first device before the first timer expires.

[0449] In other embodiments, the second network device can not send the length of the first timer, but a first length determined according to the length of the first timer. Considering that the interaction of the Xn interface message needs some time, the first length can be less than the length of the first timer. Optionally, the first network device can send the first response message to the first device within the first length after receiving the first information sent by the first device.

[0450] Please refer to Figure 14 (B), Figure 12 (B) of the above-mentioned (A) exemplary shows another method of controlling transmission. The method comprises but is not limited to the following steps:

[0451] S5421: The second network device sends, to the first network device, a third Xn interface message comprising the length of the first timer.

[0452] S5422: The first network device sends, to the second network device, a first message comprising the first information.

[0453] The description of S5411 and S5412 of the above-mentioned (A) is similar to that of S5421 and S5422, and will not be repeated here. Figure 15

[0454] S5423: The second network device sends, to the first network device, a second message comprising the first response message.​

[0455] Specifically, the second message including the first response message and the third message including the length of the first timer are different, the third message is a third Xn interface message, the second message is other existing Xn interface message or new Xn interface message, etc.

[0456] In some embodiments, after receiving the first message, the second network device can generate the first response message based on the first information in the first message, and optionally, generate the first response message based on the length of the first timer. In some embodiments, the second network device can send the second message including the first response message to the first network device based on the length of the first timer. Optionally, in the above case, the first network device can send the first response message to the first device before the first timer expires.

[0457] In some embodiments, after receiving the second message including the first response message, the first network device can send the first response message to the first device before the first timer indicated by the third Xn interface message expires.

[0458] In some other embodiments, after receiving the second message including the first response message, the first network device can send the first response message to the first device within a second length after receiving the first information sent by the first device, wherein considering that the interaction of Xn interface messages needs some time, the second length can be less than the length of the first timer.

[0459] In another possible implementation, the first timer used by the first device is the first timer in the context of the first device stored by the second network device, and the second message including the first response message is the third Xn interface message shown in (A). In some embodiments, the first timer can be sent to the second network device through an Xn interface message other than the third Xn interface message, and the specific process is as shown in (A) of (B) below. Figure 15 Figure 15 In some other embodiments, the first timer and the first response message can be sent to the second network device together, and the specific process is as shown in (B) of (A) below. Figure 15

[0460] Please refer to Figure 14 (A), Figure 15 (A) of (B) below.

[0461] S5431: The second network device sends a third Xn interface message including the first response message to the first network device.

[0462] ​​S5432: The first network device sends, to the second network device, a first message including the first information.

[0463] The descriptions of S5431 and S5432 and the above Figure 15 The descriptions of S5411 and S5412 of (A) are similar, except that the third Xn interface message in S5431 includes the first response message, the specifics of which are not repeated here.

[0464] S5433: The second network device sends, to the first network device, a third message including a duration of the first timer.

[0465] Specifically, the second message including the first response message and the third message including the duration of the first timer are different, the second message is the third Xn interface message, and the third message is other existing Xn interface messages other than the third Xn interface message or a new Xn interface message, etc.

[0466] In some embodiments, after the first network device receives the third message including the duration of the first timer, the first network device can send the first response message to the first device before the first timer expires.

[0467] In other embodiments, the second network device can not send the duration of the first timer, but a third duration determined according to the duration of the first timer, considering that the interaction of Xn interface messages requires some time, the third duration can be less than the duration of the first timer. Optionally, the first network device can send the first response message to the first device within the third duration after receiving the first information sent by the first device.

[0468] See Figure 14 (B) of (A), Figure 16 (B) of (A) exemplarily shows a flowchart of another method of controlling transmission. The method includes but is not limited to the following steps:

[0469] S5441: The second network device sends, to the first network device, a third Xn interface message including the first response message and a duration of the first timer.

[0470] S5442: The first network device sends, to the first network device, a first message including the first information.

[0471] The descriptions of S5441 and S5442 and the above Figure 16 The descriptions of S5411 and S5412 of (A) are similar, except that the third Xn interface message in S5441 includes the first response message and the duration of the first timer, the specifics of which are not repeated here.

[0472] Specifically, the second message including the first response message and the third message including the duration of the first timer are the same, which are the third Xn interface message.

[0473] In some embodiments, after the first network device receives the third Xn interface message including the first response message and the length of the first timer, the first network device can send the first response message to the first device before the first timer expires.

[0474] In yet another possible implementation, the first timer used by the first device is configured for the first device by the first network device, and the length of the first timer is generated by the first network device. The second message including the first response message is not the third Xn interface message, and the specific flow is as follows Figure 16 .

[0475] See Figures 11-12 , Figure 17 An exemplary flowchart of a method of controlling transmission is shown. The method includes but is not limited to the following steps:

[0476] S5451: The first network device sends a fourth message including the length of the first timer to the second network device.

[0477] S5452: The first network device sends a first message including the first information to the second network device.

[0478] Exemplarily, the fourth message is the first Xn interface message (for example, the RetrieveUEContextRequest message) shown in Figure 17 . When the first network device requests the user context of the first device from the second network device, the length of the first timer can be indicated through the first Xn interface message.

[0479] Exemplarily, the fourth message is the Xn Setup Request (XN SETUP REQUEST) message. In the Xn Setup Procedure, the first network device sends the XN SETUP REQUEST message to the second network device, and indicates the length of the first timer through the XN SETUP REQUEST message.

[0480] Exemplarily, the fourth message is the NGRAN CONFIGURATION UPDATE REQUEST message. In the NG RAN Node Configuration Update Procedure, the first network device sends the NGRAN CONFIGURATION UPDATE REQUEST message to the second network device, and indicates the length of the first timer through the NGRAN CONFIGURATION UPDATE REQUEST message.

[0481] The fourth message, which is not limited to the above example, can also be an existing Xn interface message or a new Xn interface message.

[0482] In some embodiments, the first message can be an existing Xn interface message, optionally a first Xn interface message, such as a RetrieveUEContextRequest message. Optionally, after receiving the first information sent by the first device, the first network device can indicate the duration of the first timer and the first information through the first Xn interface message when the first network device requests the user context of the first device from the second network device.

[0483] The order of S5451 and S5452 is not limited.

[0484] S5453: The second network device sends a second message including the first response message to the first network device.

[0485] In some embodiments, after receiving the first message, the second network device can generate the first response message based on the first information in the first message. In some embodiments, the second network device can send the second message including the first response message to the first network device based on the duration of the first timer indicated by the fourth message, so that the first network device can send the first response message to the first device before the first timer expires.

[0486] The first information, which is not limited to the above example, indicates a request to suspend SDT in some embodiments, and indicates a request to suspend SDT and not enter the RRC CONNECTED state in some embodiments. The specific description is similar to the first information of the above example.

[0487] See Figure 13 , Figure 13 is a flow diagram of another method for controlling transmission provided by the embodiments of the present application. The method can include but is not limited to the following steps:

[0488] S610: The first device receives second configuration information.

[0489] In some embodiments, S610 is an optional step.

[0490] S610 and Figure 13S510, the difference is that in S610, the first configuration information is replaced by the second configuration information, the first information is replaced by the second information, and the first timer is replaced by the second timer. In some embodiments, the second information indicates a request for a gap configuration for the SDT. In some embodiments, the second information indicates a request to suspend the SDT. For details, see the description of the second information in S630. For other descriptions, see the description of S510. Figure 13 S510.

[0491] S620: The first device performs the SDT.

[0492] In some embodiments, S620 is an optional step.

[0493] S620 and Figure 13 S520 is similar to S520. Figure 13 S520.

[0494] S630: The first device sends second information to the first network device.

[0495] In some embodiments, the second information indicates a request to suspend the SDT (such as the SDT in S620). Alternatively, the request to suspend the SDT can also be replaced by a desire to suspend the SDT. In some embodiments, the second information indicates a request for a gap configuration for the SDT (such as the SDT in S620).

[0496] In some embodiments, the first device is a multi-card terminal including a first sub-device, and the first device sends the second information to the first network device through the first sub-device. Alternatively, the second information indicates that the first sub-device requests to suspend the SDT. Alternatively, the second information indicates a request to suspend the SDT of the first sub-device. Alternatively, the second information indicates that the first sub-device requests a gap configuration for the SDT. Alternatively, the second information indicates a request for a gap configuration for the SDT of the first sub-device.

[0497] In some embodiments, the first device is a first sub-device included in a multi-card terminal, and the first device sends the second information to the first network device. Alternatively, the second information indicates that the first device requests to suspend the SDT. Alternatively, the second information indicates a request to suspend the SDT of the first device. Alternatively, the second information indicates that the first device requests a gap configuration for the SDT. Alternatively, the second information indicates a request for a gap configuration for the SDT of the first device.

[0498] The following description takes the first device as an example of a first sub-device included in a multi-card terminal.

[0499] S630 and Figures 11-12S530, the difference is that in S630, the first information is replaced by the second information, the first timer is replaced by the second timer, the first response message is replaced by the second response message, and the second response message is a response message (for example, an RRCReconfiguration message) of the second information. In some embodiments, when the second timer expires, the first device does not enter the RRC IDLE state, but decides according to its own implementation how to handle the SDT, for example, stopping the SDT, and for example, pausing the SDT. The description of the second information can be referred to in the following description, and the description of the other can be referred to in the description of S530. Figures 5-10 The description of S530.

[0500] In some embodiments, when the second sub-device needs to send a system information request or receive a downlink message, the first device sends the second information to the first network device, and optionally, the second sub-device is in the RRC non-connected state. In some embodiments, when the multi-card terminal needs to switch from the SDT service to the service of sending a system information request or receiving a downlink message, the first device sends the second information to the first network device, which can also be referred to as the first device sending the second information to the first network device due to the multi-card reason. Specific examples can be referred to in the above-mentioned scenario two in which the terminal cannot continue the SDT when the terminal and the network device perform the SDT, which is not limited thereto, and can also be applied to scenario one and other scenarios. Among them, the downlink message is, for example, a periodic downlink message such as paging, system information, RRM, or other non-periodic downlink messages.

[0501] For example, the multi-card terminal is a smart phone, which can be installed with two phone cards, i.e., the first sub-device and the second sub-device. When the user transmits instant messaging messages through one phone card (i.e., the first sub-device) on the smart phone and other terminals, for example, at this time, the mobile data of the first sub-device is used to communicate with other terminals through the first network device, the other phone card (i.e., the second sub-device) of the smart phone needs to listen to the downlink message sent by the network device, such as a paging message, and the smart phone cannot continue to transmit instant messaging messages through the first sub-device. The first sub-device can send the second information to the first network device.

[0502] In a possible implementation, the second information includes the above-mentioned gap configuration, which in some embodiments can indicate a period in which the first device stops listening to the SDT, and in some embodiments, the gap configuration is generated for the service of the second sub-device, and can indicate a period in which the second sub-device transmits data.

[0503] In some embodiments, the gap configuration in the second information can include a start time, a duration and a traffic period for periodic traffic of the second sub-device, and in other embodiments, the gap configuration in the second information can include a start time and a duration for aperiodic traffic of the second sub-device. In yet other embodiments, the gap configuration in the second information can include a start time and a duration for traffic of the second sub-device, such as periodic traffic and aperiodic traffic.

[0504] Wherein, the first device stops monitoring the SDT when the traffic of the second sub-device is running.

[0505] In some embodiments, the period in which the first device stops monitoring the SDT can also be referred to as the occupied period of the second sub-device.

[0506] Without being limited to the above example, in other embodiments, the gap configuration can also indicate a period in which the first device monitors the SDT, and the present application takes the example of the gap configuration indicating a period in which the first device stops monitoring the SDT for illustration.

[0507] In some embodiments, the first device can send the second information according to its own implementation decision. For example, the traffic of the second sub-device is only periodic traffic, and the first device can send the second information (such as the traffic period) corresponding to the periodic traffic. For another example, the traffic of the second sub-device is only aperiodic traffic, and the first device can send the second information (such as the occupied period) corresponding to the aperiodic traffic. For yet another example, the traffic of the second sub-device includes periodic traffic and aperiodic traffic, and the first device can calculate the occupied period of the traffic and send it to the first network device through the second information.

[0508] S640: The first network device and the second network device transmit the second information and other related information.

[0509] In some embodiments, S640 is an optional step.

[0510] In some embodiments, the first device currently serves a cell corresponding to the first network device which does not store the user context of the first device, and the user context of the first device is stored in the second network device, i.e., the first network device is a new station and the second network device is an old station. In this case, after receiving the second information sent by the first device, the first network device forwards the second information to the second network device. Optionally, S640 is performed in a scenario where the old station (the second network device) decides not to perform anchor relocation, and the new station (the first network device) cannot obtain the user context of the first device from the old station (the second network device). Optionally, the SDT initiated by the first device is RA-SDT, i.e., S640 is performed in a scenario of RA-SDT and no anchor device replacement.

[0511] In some embodiments, the first network device and the second network device exchange information through Xn interface messages. The following description takes the messages exchanged between the first network device and the second network device as examples of Xn interface messages.

[0512] In some embodiments, after receiving the second information sent by the first device, the first network device can send a sixth message to the second network device, and the sixth message includes the second information. Optionally, the sixth message is an Xn interface message, such as the first Xn interface message (e.g., the RetrieveUEContextRequest message) shown in FIG. 6A, or other existing Xn interface messages, or a new Xn interface message. Figure 11 In some embodiments, after receiving the second information sent by the first device, the first network device can send a sixth message to the second network device, and the sixth message includes the second information. Optionally, the sixth message is an Xn interface message, such as the first Xn interface message (e.g., the RetrieveUEContextRequest message) shown in FIG. 6A, or other existing Xn interface messages, or a new Xn interface message.

[0513] In some embodiments, after sending the sixth message to the second network device, the first network device can receive a seventh message sent by the second network device, and the seventh message includes a second response message. The seventh message is used for the first network device to send the second response message to the first device before the second timer expires, e.g., the seventh message is used for the first network device to perform S650. Examples of the second response message can be found in the RRC response message in the SDT, e.g., the RRCReconfiguration message shown in FIG. 6B. Figure 12 In some embodiments, after sending the sixth message to the second network device, the first network device can receive a seventh message sent by the second network device, and the seventh message includes a second response message. The seventh message is used for the first network device to send the second response message to the first device before the second timer expires, e.g., the seventh message is used for the first network device to perform S650. Examples of the second response message can be found in the RRC response message in the SDT, e.g., the RRCReconfiguration message shown in FIG. 6B. Figure 12 In some embodiments, after sending the sixth message to the second network device, the first network device can receive a seventh message sent by the second network device, and the seventh message includes a second response message. The seventh message is used for the first network device to send the second response message to the first device before the second timer expires, e.g., the seventh message is used for the first network device to perform S650. Examples of the second response message can be found in the RRC response message in the SDT, e.g., the RRCReconfiguration message shown in FIG. 6B. Figure 14 In some embodiments, after sending the sixth message to the second network device, the first network device can receive a seventh message sent by the second network device, and the seventh message includes a second response message. The seventh message is used for the first network device to send the second response message to the first device before the second timer expires, e.g., the seventh message is used for the first network device to perform S650. Examples of the second response message can be found in the RRC response message in the SDT, e.g., the RRCReconfiguration message shown in FIG. 6B.

[0514] In some embodiments, the first network device and the second network device can transmit a message including the duration of the second timer, as described below.

[0515] In a possible implementation, the second configuration information and the duration of the second timer are configured in the manner one or manner four in S610, i.e., the second timer used by the first device is configured for the first device by the first network device through broadcast system information (e.g., SIB1). In some embodiments, the duration of the second timer is generated by the first network device, and in other embodiments, the duration of the second timer is sent by the second network device to the first network device through the tenth message before the duration of the second timer is configured for the first device, and the tenth message includes the duration of the second timer.

[0516] In another possible implementation, the second configuration information and the duration of the second timer are configured in the manner two or manner three in S610, i.e., the second timer used by the first device is configured for the first device by the first network device or the second network device through an RRC message. In some embodiments, the second timer used by the first device is the second timer in the context of the first device stored by the second network device, and in other embodiments, the second timer used by the first device is configured for the first device by the first network device, and in a possible case, the duration of the second timer is generated by the first network device, and in another possible case, the duration of the second timer is sent by the second network device to the first network device through the tenth message before the duration of the second timer is configured for the first device, and the tenth message includes the duration of the second timer.

[0517] In another possible implementation, the second configuration information and the duration of the second timer are configured in the manner five in S610, i.e., the duration of the second timer used by the first device is predefined, and the first network device and the second network device can not interact the duration of the second timer.

[0518] In some embodiments, the second timer used by the first device is the second timer in the context of the first device stored by the second network device. After the first network device receives the second information sent by the first device, the first network device can receive the eighth message sent by the second network device, and the eighth message includes the duration of the second timer, which can be used by the first network device to send the second response message to the first device before the second timer expires, e.g., the duration of the second timer is used by the first network device to perform S650. In a possible case, the seventh message including the second response message is not the third Xn interface message shown in FIG. 6B, and in this case, the transmission processes of the first network device and the second network device are similar to those in S650. Figure 12 In another possible case, the seventh message including the second response message is the third Xn interface message shown in FIG. 6B, and in this case, the transmission processes of the first network device and the second network device are similar to those in S650. Figure 15 In another possible case, the seventh message including the second response message is the third Xn interface message shown in FIG. 6B, and in this case, the transmission processes of the first network device and the second network device are similar to those in S650. Figure 12 In another possible case, the seventh message including the second response message is the third Xn interface message shown in FIG. 6B, and in this case, the transmission processes of the first network device and the second network device are similar to those in S650. Figure 16 In another possible case, the seventh message including the second response message is the third Xn interface message shown in FIG. 6B, and in this case, the transmission processes of the first network device and the second network device are similar to those in S650.

[0519] In some embodiments, the second timer used by the first device is configured by the first network device for the first device, and the duration of the second timer is generated by the first network device. In one possible case, the seventh message including the second response message is the third Xn interface message shown in FIG. 6. The first network device can send a ninth message to the second network device, the ninth message including the duration of the second timer, and the second network device can send the seventh message to the first network device based on the duration of the second timer in the ninth message, at which time the transmission procedure of the first network device and the second network device is similar to that shown in FIG. 5. Figure 12 In another possible case, the seventh message including the second response message is the third Xn interface message shown in FIG. 7. The first network device can not send the duration of the second timer to the second network device. Optionally, in this case, the order in which the first network device sends the sixth message including the second information to the second network device and the second network device sends the seventh message including the second response message to the first network device is not limited. Figure 12 In another possible case, the seventh message including the second response message is the third Xn interface message shown in FIG. 7. The first network device can not send the duration of the second timer to the second network device. Optionally, in this case, the order in which the first network device sends the sixth message including the second information to the second network device and the second network device sends the seventh message including the second response message to the first network device is not limited. Figure 12 In another possible case, the seventh message including the second response message is the third Xn interface message shown in FIG. 7. The first network device can not send the duration of the second timer to the second network device. Optionally, in this case, the order in which the first network device sends the sixth message including the second information to the second network device and the second network device sends the seventh message including the second response message to the first network device is not limited.

[0520] In some embodiments, the second timer used by the first device is configured by the first network device for the first device, and the duration of the second timer is generated by the first network device. In one possible case, the seventh message including the second response message is the third Xn interface message shown in FIG. 6. The first network device can send a ninth message to the second network device, the ninth message including the duration of the second timer, and the second network device can send the seventh message to the first network device based on the duration of the second timer in the ninth message, at which time the transmission procedure of the first network device and the second network device is similar to that shown in FIG. 5.

[0521] In some embodiments, the first network device can send the length of the timer to the second network device multiple times through the Xn interface message, and specific examples can refer to the examples of the tenth message described above. If the response message received by the first network device from the second network device does not include the length of the timer, the first network device determines that the length of the second timer is the length of the timer sent to the second network device described above. If the response message received by the first network device from the second network device includes the length of the timer, the first network device determines that the length of the second timer is the length of the timer sent by the second network device.

[0522] In another embodiment, the second timer used by the first device is predefined. In one possible case, the seventh message including the second response message is not the third Xn interface message shown in FIG. 6B. The second network device can generate the second response message based on the length of the second timer and send the seventh message to the first network device. The first network device can send the second response message to the first device based on the length of the second timer, for example, before the second timer expires. Figure 18 In another embodiment, the second timer used by the first device is predefined. In one possible case, the seventh message including the second response message is not the third Xn interface message shown in FIG. 6B. The second network device can generate the second response message based on the length of the second timer and send the seventh message to the first network device. The first network device can send the second response message to the first device based on the length of the second timer, for example, before the second timer expires. Figure 19 In another embodiment, the second timer used by the first device is predefined. In one possible case, the seventh message including the second response message is not the third Xn interface message shown in FIG. 6B. The second network device can generate the second response message based on the length of the second timer and send the seventh message to the first network device. The first network device can send the second response message to the first device based on the length of the second timer, for example, before the second timer expires.

[0523] In one possible implementation, the second response message includes third information, and the third information indicates the gap configuration described above. For details, please refer to the description of S650, which is not described here. In some embodiments, the third information is generated by the second network device based on the second information, and the specific process is as follows Figures 5-10 In another embodiment, the third information is generated by the first network device based on the second information, and the specific process is as follows Figure 17 In another embodiment, the third information is generated by the first network device based on the second information, and the specific process is as follows

[0524] S650: The first network device sends a second response message (for example, an RRCReconfiguration message) to the first device.

[0525] In some embodiments, S650 is an optional step.

[0526] In some embodiments, after the first device receives the second response message, the first device can process the SDT based on the second response message, and optionally, the second timer can be stopped. In some embodiments, the second response message includes third information, and the third information indicates the gap configuration. For details, please refer to the description of the gap configuration included in the second information in S630.

[0527] In some embodiments, the gap configuration indicated by the third information can indicate a first time period during which the first device stops monitoring the SDT. After receiving the second response message, the first device can stop monitoring the SDT during the first time period, and monitor the SDT (e.g., perform the SDT) during a time period outside the first time period. Optionally, the gap configuration is for a periodic service of the second sub-device, and after receiving the second response message, the first device can periodically stop monitoring the SDT, that is, can stop monitoring the SDT during a service period of the periodic service, and continue the SDT outside the service period. Optionally, the gap configuration is for an aperiodic service of the second sub-device, and after receiving the second response message, the first device can stop monitoring the SDT during a time period occupied by the aperiodic service, and continue the SDT during other time periods.

[0528] Without being limited to the above examples, in some other embodiments, when the second timer expires without the first device receiving the second response message sent by the first network device, the first device can decide how to handle the SDT according to its own implementation, for example, stop the SDT, or for example, pause the SDT.

[0529] In some embodiments, the second response message is an RRC message, for example, an RRCReconfiguration message. Without being limited thereto, in some other embodiments, the second response message can also be an RRC message as shown in the SDT procedure in the above examples. Figure 18 In some embodiments, the second response message is an RRC message, for example, an RRCReconfiguration message. Without being limited thereto, in some other embodiments, the second response message can also be an RRC message as shown in the SDT procedure in the above examples.

[0530] Not limited to the above examples, in other embodiments, the first device can also not be configured with the second timer, for example, S610 does not involve the second timer, in one possible case, the second configuration information can be sent to the first device through the broadcast system information (such as SIB1), at this time, the description of the second configuration information can refer to the description of the second configuration information in the second way of S610. In another possible case, the second configuration information can be sent to the first device through the RRC message, at this time, the description of the second configuration information can refer to the description of the second configuration information in the fourth way of S610. Optionally, in the case of sending the second configuration information to the first device through the RRC message, the method can further include: the first device receives the system information (such as SIB1) sent by the first network device (broadcast), which can indicate that the current network device supports the device to report the second information, for example, when the value of the second support information in the SIB1 is "true", it means that the current base station supports the UE to report the second information. And the first device also does not use the second timer, for example, S630 does not involve the second timer, accordingly, the first device can directly decide how to process the SDT according to its own implementation, for example, stop the SDT, and for example, pause the SDT, without waiting for the second response message based on the second timer.

[0531] In Figure 18 In the method shown, the first device can send the second information to the first network device, and through the second information, indicate the request to pause the SDT or request the gap configuration for the SDT, so as to avoid that when the first device stops listening to the SDT, the first network device still schedules the resource for the SDT for the first device, and save the air interface resource.

[0532] And the first device can not stop the current SDT, and continue the SDT when it can be performed (for example, the first device continues the SDT in the period other than the periodic service of the second sub-device), reduce the signaling overhead, and the transmission efficiency is higher.

[0533] In some embodiments, when the first device determines to stop the current SDT, it can send the first information indicating the request to stop the SDT, and the subsequent SDT will not be continued, and optionally, the first device can subsequently re-initiate a new SDT. For example, the first device is the first sub-device included in a multi-card terminal, and the multi-card terminal further includes a second sub-device. The first device can stop the current SDT and let the second sub-device enter the RRC connected state. When the second sub-device enters the non-RRC connected state, the first device can re-initiate a new SDT.

[0534] In some embodiments, the first device determines to suspend the current SDT, and sends the first information indicating a request to suspend the SDT (optionally and without entering the RRC CONNECTED state), or the second information indicating a request to suspend the SDT, or the second information indicating a request for a gap configuration for the SDT, in one possible case, the first device can continue the SDT later, in another possible case, the first device can re-initiate a new SDT later. For example, the first device is a first sub-device included in a multi-card terminal, the multi-card terminal further includes a second sub-device, the first device can suspend the current SDT, and the second sub-device can perform periodic or aperiodic data transmission (such as still in the non-RRC connected state to transmit data), the first device can continue the current SDT in a period other than the period in which the second sub-device performs periodic data transmission, or the first device can continue the current SDT after the second sub-device performs aperiodic data transmission.

[0535] Next, the specific implementation of S640 is exemplarily introduced.

[0536] In some embodiments, the third information indicating the gap configuration in the second response message is generated by the second network device based on the second information, and the specific process is as follows Figure 18 as shown.

[0537] Please refer to Figure 19 , Figure 19 An exemplary flowchart of another method of controlling transmission is shown. The method includes but is not limited to the following steps:

[0538] S6411: The first network device sends a sixth message including the second information to the second network device.

[0539] In some embodiments, after the first network device receives the second information sent by the first device, the first network device can forward the second information to the second network device.

[0540] S6412: The second network device can generate the third information based on the second information in the sixth message.

[0541] In some embodiments, the second network device can generate the third information based on the specific content of the second information in the sixth message. In some embodiments, the second network device generates a second response message including the third information.

[0542] In some embodiments, the second network device can generate the third information based on the length of the second timer and the second information, and in some embodiments, the second network device can generate a second response message including the third information based on the length of the second timer. Optionally, in the above case, the first network device can send the second response message to the first device before the second timer expires.

[0543] S6413: The second network device sends, to the first network device, a seventh message including the second response message.

[0544] In some embodiments, the second network device can send, to the first network device, the seventh message including the second response message based on the length of the second timer, optionally so that the first network device can send the second response message to the first device before the second timer expires.

[0545] In some embodiments, the second network device can further send, to the first network device, specific content of the gap configuration, for example, send an Xn interface message including the third information, and the first network device can obtain the specific content of the gap configuration based on the Xn interface message. Optionally, the first network device can perform scheduling of the SDT based on the specific content of the gap configuration.

[0546] In some embodiments, after the first network device receives the seventh message, the first network device can send the second response message to the first device before the second timer expires.

[0547] In some other embodiments, the third information indicating the gap configuration in the second response message is generated by the first network device based on the second information, and the specific process is as follows Figure 19 as shown.

[0548] Please refer to ​ , ​ An exemplary flowchart of another method of controlling transmission is shown. The method includes but is not limited to the following steps:

[0549] S6421: The first network device sends, to the second network device, a sixth message including the second information.

[0550] In some embodiments, after the first network device receives the second information of the first device, the first network device can forward the second information to the second network device.

[0551] S6422: The second network device sends, to the first network device, an eleventh message including the second information.

[0552] In some embodiments, the second network device can send, to the first network device, the eleventh message including specific content of the second information, and in some embodiments, the first network device can obtain the specific content of the second information based on the eleventh message.

[0553] S6423: The first network device generates third information based on the second information.

[0554] In some embodiments, the first network device can generate the third information based on the obtained specific content of the second information.

[0555] S6424: The first network device sends, to the second network device, a twelfth message including the third information.

[0556] S6425: The second network device sends, to the first network device, a seventh message including the second response message.

[0557] In some embodiments, after receiving the twelfth message including the third information, the second network device generates the second response message including the third information. In some embodiments, the second network device can generate the second response message including the third information based on the length of the second timer. Optionally, in the above case, the first network device can send the second response message to the first device before the second timer expires.

[0558] In some embodiments, the second network device can send, to the first network device, the seventh message including the second response message based on the length of the second timer. Optionally, in the above case, the first network device can send the second response message to the first device before the second timer expires.

[0559] Exemplarily, the sixth message is a first Xn interface message (e.g., a RetrieveUEContextRequest message), and the seventh message is a second Xn interface message (e.g., a RetrieveUEContextResponse message) or a third Xn interface message (e.g., a RetrieveUEContextFailure message). Without limitation, the sixth message can also be other existing or new Xn interface messages. The seventh message can also be other existing or new Xn interface messages.

[0560] Exemplarily, the eleventh message is a first Xn interface message (e.g., a RetrieveUEContextRequest message), and the twelfth message is a second Xn interface message (e.g., a RetrieveUEContextResponse message) or a third Xn interface message (e.g., a RetrieveUEContextFailure message). Without limitation, the eleventh message can also be other existing or new Xn interface messages. The twelfth message can also be other existing or new Xn interface messages.

[0561] It can be understood that the communication system architecture and service scenarios described in the present application are for more clearly illustrating the technical solutions of the present application, and do not constitute a limitation on the technical solutions provided by the present application. Those skilled in the art can know that, with the evolution of the communication system architecture and the appearance of new service scenarios, the technical solutions provided by the present application are also applicable to similar technical problems. Those skilled in the art can understand that all or part of the processes in the above-mentioned embodiment methods can be completed by a computer program related hardware, and the computer program can be stored in a computer readable storage medium. When the computer program is executed, the processes of the above-mentioned method embodiments can be included. The foregoing storage medium includes read-only memory (ROM) or random access memory (RAM), magnetic disk or optical disk and various media that can store computer program codes.

Claims

1. A method for controlling transmission, characterized in that, Applied to a first device, the method includes: When in a non-Radio Resource Control (RRC) connected state, a first message is sent to the first network device, indicating a request to stop Small Packet Data Transmission (SDT). The first device is a multi-SIM terminal or a first sub-device included in a multi-SIM terminal. The multi-SIM terminal includes the first sub-device and a second sub-device. The first sub-device and the second sub-device share a radio frequency transmission chain and / or a radio frequency reception chain. The first information is sent under any of the following circumstances: the second sub-device needs to enter the RRC connection state from a non-RRC connection state, the multi-SIM terminal needs to switch from SDT service to RRC connection state service, or there is a multi-SIM reason.

2. The method as described in claim 1, characterized in that, The first device is the multi-SIM terminal. The first device includes a first sub-device and a second sub-device. The first sub-device and the second sub-device share a radio frequency transmission chain and / or a radio frequency reception chain. Sending the first information to the first network device includes: sending the first information to the first network device through the first sub-device; wherein: The first information indicates that the first sub-device requests to stop the SDT; or, the first information indicates a request to stop the SDT of the first sub-device.

3. The method as described in claim 2, characterized in that, Sending the first information to the first network device includes: when the second sub-device needs to enter the RRC connection state from a non-RRC connection state, sending the first information to the first network device through the first sub-device; or... Sending the first information to the first network device includes: sending the first information to the first network device when the first device needs to switch from SDT service to RRC connected state service; or... Sending the first information to the first network device includes: sending the first information to the first network device due to multiple SIM cards.

4. The method as described in claim 2, characterized in that, The state of being in a non-Radio Resource Control (RRC) connected state includes: the first sub-device being in an RRC inactive state; the method further includes: When sending the first information to the first network device, the first sub-device starts the first timer; After sending the first information to the first network device, the method further includes: If a first response message is received from the first network device before the first timer expires, the first sub-device stops the first timer; If the first response message is not received from the first network device when the first timer expires, the first sub-device enters the RRC idle state.

5. The method according to any one of claims 2-4, characterized in that, Before sending the first information to the first network device, the method further includes: The first configuration information is received through the first sub-device, wherein the first configuration information indicates the reporting of the first information, and: Receiving the first configuration information through the first sub-device includes: receiving the first configuration information sent by the first network device through broadcast system information through the first sub-device; or, receiving the first configuration information through the first sub-device includes: receiving the first configuration information sent by the first network device through an RRC message through the first sub-device; or, receiving the first configuration information through the first sub-device includes: receiving the first configuration information sent by a second network device through an RRC message through the first sub-device, wherein the second network device is an anchor device that stores the user context of the first sub-device, and the first network device does not store the user context of the first sub-device; The first configuration information includes the duration of a first timer; or, the method further includes: receiving the duration of a first timer sent by the first network device via broadcast system information through the first sub-device; or, the method further includes: receiving the duration of a first timer sent by the first network device via an RRC message through the first sub-device; or, the method further includes: receiving the duration of a first timer sent by a second network device via an RRC message through the first sub-device, wherein the second network device is an anchor device storing the user context of the first sub-device, and the first network device does not store the user context of the first sub-device; or, the duration of the first timer is predefined; wherein, the first timer is used by the first sub-device to listen for the response message of the first information.

6. The method as described in claim 5, characterized in that, Before receiving the first configuration information through the first sub-device, the method further includes: The first request message is sent through the first sub-device, and the first request message indicates a request to configure the reporting of the first information.

7. A method for controlling transmission, characterized in that, Applied to a first network device, the method includes: The system receives a first message sent by a first device, the first message indicating a request to stop SDT (Signal Distribution Detection), wherein the first device is a multi-SIM terminal or a first sub-device included in a multi-SIM terminal, the multi-SIM terminal includes the first sub-device and a second sub-device, the first sub-device and the second sub-device share a radio frequency transmission chain and / or a radio frequency reception chain; the first message is sent under any of the following circumstances: the second sub-device needs to enter the RRC (Receiving Controlled Transmission) connection state from a non-RRC (Receiving Controlled Transmission) connection state, the multi-SIM terminal needs to switch from SDT service to RRC connection state service, or there is a multi-SIM reason.

8. The method as described in claim 7, characterized in that, The first device is the multi-card terminal. The first device includes a first sub-device and a second sub-device. The first sub-device and the second sub-device share a radio frequency transmission chain and / or a radio frequency reception chain. Receiving the first information sent by the first device includes: receiving the first information sent by the first sub-device; wherein: The first information indicates that the first sub-device requests to stop the SDT; or, the first information indicates a request to stop the SDT of the first sub-device.

9. The method as described in claim 8, characterized in that, The first information is sent by the first sub-device to the first network device when the second sub-device needs to transition from a non-RRC connection state to an RRC connection state; or, The first information is sent by the first device to the first network device when the first device needs to switch from SDT service to RRC connected state service; or, The first information is sent by the first device to the first network device due to the presence of multiple SIM cards.

10. The method as described in claim 8, characterized in that, Before receiving the first information sent by the first device, the method further includes: Send first configuration information to the first sub-device, and / or send the duration of a first timer to the first sub-device, wherein the first configuration information indicates the reporting of the first information, and the first timer is used by the first sub-device to listen for response messages to the first information, wherein: Sending the first configuration information to the first sub-device includes: sending the first configuration information to the first sub-device via broadcast system information; or, sending the first configuration information to the first sub-device includes: sending the first configuration information to the first sub-device via an RRC message; The first configuration information includes the duration of the first timer; or, sending the duration of the first timer to the first sub-device includes: sending the duration of the first timer to the first sub-device via broadcast system information; or, sending the duration of the first timer to the first sub-device includes: sending the duration of the first timer to the first sub-device via an RRC message; or, the duration of the first timer is predefined.

11. The method according to any one of claims 8-10, characterized in that, After receiving the first information sent by the first device, the method further includes: Before the first timer expires, a first response message is sent to the first sub-device.

12. The method according to any one of claims 8-10, characterized in that, The first network device does not store the user context of the first sub-device; after receiving the first information sent by the first device, the method further includes: Send a first message to a second network device, the first message including the first information, the second network device being an anchor device storing the user context of the first sub-device.

13. The method according to any one of claims 8-10, characterized in that, The method further includes: The first network device receives a second message sent by a second network device, the second message including a first response message. The second network device is an anchor device that stores the user context of the first sub-device. The second message is used by the first network device to send the first response message to the first sub-device.

14. The method according to any one of claims 8-10, characterized in that, After receiving the first information sent by the first device, the method further includes: The system receives a third message from a second network device, which is an anchor device storing the user context of the first sub-device. The user context of the first sub-device includes the duration of a first timer. The third message includes the duration of the first timer, which is used by the first network device to send a first response message to the first sub-device before the first timer expires.

15. The method as described in claim 13, characterized in that, Before receiving the second message sent by the second network device, the method further includes: A fourth message is sent to the second network device. The fourth message includes the duration of a first timer, which is generated by the first network device. The duration of the first timer is used by the second network device to send the second message to the first network device.

16. The method according to any one of claims 8-10, characterized in that, Before receiving the first information sent by the first device, the method further includes: The system receives a fifth message from a second network device, which is an anchor device storing the user context of the first sub-device. The fifth message includes the duration of a first timer, which is used by the first network device to send a first response message to the first sub-device before the first timer expires.

17. The method as described in claim 10, characterized in that, Before sending the first configuration information to the first sub-device, the method further includes: Receive a first request message sent by the first sub-device, the first request message indicating a request to configure the reporting of the first information.

18. A method for controlling transmission, characterized in that, Applied to a second network device, the method includes: The first network device receives a first message, which includes first information indicating that the first device requests to stop SDT. The first network device does not store the user context of the first device, and the second network device is an anchor device that stores the user context of the first device.

19. The method as described in claim 18, characterized in that, The first device is a multi-SIM terminal. The first device includes a first sub-device and a second sub-device. The first sub-device and the second sub-device share a radio frequency transmission chain and / or a radio frequency reception chain. The first network device does not store the user context of the first device, including: the first network device does not store the user context of the first sub-device. The second network device is an anchor device that stores the user context of the first device, including: the second network device is an anchor device that stores the user context of the first sub-device. The first information indicates that the first sub-device requests to stop the SDT; or, the first information indicates a request to stop the SDT of the first sub-device.

20. The method as described in claim 19, characterized in that, The first information is sent by the first sub-device to the first network device when the second sub-device needs to transition from a non-RRC connection state to an RRC connection state; or, The first information is sent by the first device to the first network device when the first device needs to switch from SDT service to RRC connected state service; or, The first information is sent by the first device to the first network device due to the presence of multiple SIM cards.

21. The method as described in claim 19 or 20, characterized in that, Before receiving the first message sent by the first network device, the method further includes: Send first configuration information to the first sub-device via RRC message, and / or send the duration of the first timer to the first sub-device via RRC message. The first configuration information indicates the reporting of the first information, and the first timer is used by the first sub-device to listen for the response message of the first information. The first configuration information includes the duration of the first timer; or, the duration of the first timer is predefined.

22. The method as described in claim 19 or 20, characterized in that, The method further includes: Send a second message to the first network device, the second message including a first response message, the second message being used by the first network device to send the first response message to the first sub-device.

23. The method as described in claim 19 or 20, characterized in that, The method further includes: A third message is sent to the first network device, the third message including the duration of a first timer, the duration of which is used by the first network device to send a first response message to the first sub-device before the first timer expires.

24. The method as described in claim 22, characterized in that, Before sending the second message to the first network device, the method further includes: The system receives a fourth message sent by the first network device. The fourth message includes the duration of a first timer, which is generated by the first network device. The duration of the first timer is used by the second network device to send the second message to the first network device.

25. The method as described in claim 19 or 20, characterized in that, The method further includes: A fifth message is sent to the first network device. The fifth message includes the duration of a first timer. The fifth message is received by the first network device before it receives the first information sent by the first sub-device. The duration of the first timer is used by the first network device to send a first response message to the first sub-device before the first timer expires.

26. A network device, characterized in that, It includes a transceiver, a processor, and a memory, the memory being used to store a computer program, and the processor calling the computer program to perform the method as described in any one of claims 7-25.

27. An electronic device, characterized in that, It includes a transceiver, a processor, and a memory, the memory being used to store a computer program, and the processor calling the computer program to perform the method as described in any one of claims 1-6.

28. A computer storage medium, characterized in that, The computer storage medium stores a computer program, which, when executed by a processor, implements the method described in any one of claims 1-25.

Images