Communication for small-scale data transmission

Abstract

The embodiment of the present disclosure relates to communication for an SDT. A first device sends a resume request for an SDT to a second device. The second device sends a message to the first device to reject the resume request for a first part of data transmission including the SDT. In this way, a resume procedure for a non-SDT may still be possible. Furthermore, even in the case of an RRC rejection procedure, resources for an SDT or a non-SDT may be used without congestion. Furthermore, services are not delayed.

Description

Technical Field

[0001] Embodiments of the present disclosure generally relate to the field of telecommunication, and more particularly, to methods, devices, apparatuses, and computer-readable storage media for communication for small data transmission (SDT).

Background Art

[0002] Typically, for a terminal device in an inactive state, the data traffic to be transmitted may still be small-scale and infrequent. In this case, the 3rd Generation Partnership Project (3GPP (registered trademark)) Release 17 approved SDT based on the random access channel (RACH) and configured grant (CG) scheme in the inactive state so as to avoid signaling overhead and delay associated with the transition from the inactive state to the connected state.

[0003] During SDT based on these schemes, a radio resource control (RRC) resume request for SDT may be sent from the terminal device to the network device. Currently, all possible RRC responses to the RRC resume request have not yet been determined. One possible response is an RRC reject message, but there is a problem that it is not optimal for the SDT procedure in the current form because all RRC resume requests will stop even when not in the SDT procedure.

Summary of the Invention

[0004] Generally, exemplary embodiments of the present disclosure provide an improved solution for communication for SDT.

[0005] In a first aspect, a first device is provided. The first device comprises at least one processor and at least one memory including computer program code, and the at least one memory and the computer program code are configured to cause the at least one processor to send a request to resume SDT to a second device and receive, from the second device, a message for rejecting a request to resume a part of data transmission including SDT.

[0006] In a second aspect, a second device is provided. The second device comprises at least one processor and at least one memory including computer program code, and the at least one memory and the computer program code are configured to cause the at least one processor to receive, at the second device, a request to resume SDT from a first device and send, to the first device, a message for rejecting a request to resume a part of data transmission including SDT.

[0007] In a third aspect, a communication method is provided. The method includes sending, at a first device, a request to resume SDT to a second device and receiving, from the second device, a message for rejecting a request to resume a part of data transmission including SDT.

[0008] In a fourth aspect, a communication method is provided. The method includes receiving, at a second device, a request to resume SDT from a first device and sending, to the first device, a message for rejecting a request to resume a part of data transmission including SDT.

[0009] In a fifth aspect, a communication device is provided. The device comprises means for sending, at a first device, a request to resume SDT to a second device and means for receiving, from the second device, a message for rejecting a request to resume a part of data transmission including SDT.

[0010] In a sixth aspect, a communication device is provided. The device includes, in a second device, means for receiving, from a first device, a request to resume SDT, and means for transmitting, to the first device, a message for rejecting a request to resume a part of data transmission that includes SDT.

[0011] In a seventh aspect, a non-transitory computer-readable medium is provided. The non-transitory computer-readable medium includes program instructions for causing a device to execute the method according to the third aspect.

[0012] In an eighth aspect, a non-transitory computer-readable medium is provided. The non-transitory computer-readable medium includes program instructions for causing a device to execute the method according to the fourth aspect.

[0013] It should be understood that the summary section is not intended to identify key features or essential features of embodiments of the present disclosure, nor is it intended to be used to limit the scope of the present disclosure. Other features of the present disclosure will become readily apparent through the following description.

Brief Description of the Drawings

[0014] Next, some exemplary embodiments will be described with reference to the accompanying drawings.

Figure 1

Figure 2

Figure 3

Figure 4

Figure 5

Figure 6

Figure 7

Figure 8

DETAILED DESCRIPTION OF THE INVENTION

[0015] Next, the principles of the present disclosure will be described with reference to several exemplary embodiments. It should be understood that these embodiments are described for purposes of illustration and are helpful for those skilled in the art to understand and implement the present disclosure, and do not imply any limitation on the scope of the present disclosure. The disclosure described herein can be implemented in various forms other than those described below.

[0016] In the following description and claims, unless otherwise defined, all technical and scientific terms used herein have the same meaning as commonly understood by one of ordinary skill in the art to which this disclosure belongs.

[0017] References to "one embodiment", "an embodiment", "exemplary embodiment", etc. in this disclosure indicate that the described embodiments may include certain features, structures, or characteristics, but do not necessarily indicate that all embodiments include the specific features, structures, or characteristics. Further, such expressions do not necessarily refer to the same embodiment. Additionally, if a specific feature, structure, or characteristic is described in relation to an embodiment, it should be noted that it is within the knowledge of those skilled in the art to affect such features, structures, or characteristics in relation to other embodiments, whether explicitly described or not.

[0018] In this specification, terms such as "first" and "second" may be used to describe various elements, but it should be understood that these elements should not be limited by these terms. These terms are only used to distinguish one element from another. For example, without departing from the scope of the exemplary embodiments, the first element can be referred to as the second element, and similarly, the second element can be referred to as the first element. As used herein, the term "and / or" includes any and all combinations of one or more of the listed terms.

[0019] The terms used in this specification are for the sole purpose of describing particular embodiments and are not intended to limit the exemplary embodiments. As used herein, the singular forms "a", "an", and "the" are intended to include the plural forms as well, unless the context clearly indicates otherwise. As used herein, the terms "comprises", "comprising", "has", "having", "includes" and / or "including" identify the presence of the described features, elements, and / or components, etc., but do not preclude the presence or addition of one or more other features, elements, components, and / or combinations thereof.

[0020] As used in this application, the term "circuit" may refer to one or more or all of the following: (a) A circuit implementation consisting only of hardware (such as an implementation consisting only of analog circuits and / or digital circuits), and (b) A combination of a hardware circuit and software, for example (where applicable), (i) A combination of analog and / or digital hardware circuits and software / firmware, and (ii) Part of a hardware processor that includes software (including a digital signal processor), software, and memory (s), and that cooperates to cause a device such as a mobile phone or a server to perform various functions. (c) One or more hardware circuits (such as one or more microprocessors or a part of one or more microprocessors) and one or more processors that require software (such as firmware) to operate, but may not have software when it is not required for operation.

[0021] This definition of a circuit applies to all uses of this term in this application, including all claims. As a further example, as used in this application, the term "circuit" also encompasses a hardware circuit or a processor (or multiple processors) or a part of a hardware circuit or a processor, and the implementation of the software and / or firmware associated therewith (or therewith). Also, the term "circuit" is applicable, for example, to a baseband integrated circuit or a processor integrated circuit for a mobile device, or a similar integrated circuit in a server, a cellular network device, or other computing or network device, if applicable to the elements of a particular claim.

[0022] As used herein, the term "communication network" refers to a network that complies with any suitable communication standard, such as the 5th generation (5G) system, Long-Term Evolution (LTE), LTE-Advanced (LTE-A), Wideband Code Division Multiple Access (WCDMA (registered trademark)), High-Speed Packet Access (HSPA), Narrowband Internet of Things (NB-IoT), etc. Further, the communication between the terminal device and the network device in the communication network can be carried out according to any appropriate generation of communication protocols, including but not limited to the 1st generation (1G), 2nd generation (2G), 2.5G, 2.75G, 3rd generation (3G), 4th generation (4G), 4.5G, 5th generation (5G) New Radio (NR) communication protocol, and / or other protocols known currently or developed in the future. Embodiments of the present disclosure can be applied to various communication systems. Considering the rapid development of communication, of course, there will also be future communication technologies and systems in which the present disclosure can be embodied. The scope of the present disclosure should not be regarded as limited only to the aforementioned systems.

[0023] As used herein, the term "network device" refers to a node of a communication network through which a terminal device accesses the network and receives services therefrom. Network devices may refer to base stations (BSs) or access points (APs) depending on the terms and technologies applied, such as Node B (NodeB or NB), evolved NodeB (eNodeB or eNB), NR NB (also referred to as gNB), Remote Radio Unit (RRU), Radio Header (RH), Remote Radio Head (RRH), relay, integrated access backhaul (IAB) node, low-power nodes such as femto and pico. The RAN split architecture includes a gNB-CU (centralized unit, hosting RRC, SDAP, PDCP) that controls multiple gNB-DUs (distributed units, hosting RLC, MAC, PHY). The relay node corresponds to the DU part of the IAB node.

[0024] The term "terminal device" refers to any terminal device capable of wireless communication. By way of example and not limitation, a terminal device may also be referred to as a communication device, a user equipment (UE), a subscriber station (SS), a mobile subscriber station, a mobile station (MS), or an access terminal (AT). Terminal devices include, but are not limited to, cellular phones, smartphones, voice over IP (VoIP) phones, telephones, wireless local loop phones, tablets, wearable terminal devices, personal digital assistants (PDAs), portable computers, desktop computers, image capture terminal devices such as digital cameras, game terminal devices, music storage and playback devices, in-vehicle wireless terminal devices, wireless endpoints, mobile stations, laptop embedded equipment (LEE), laptop-mounted equipment (LME), USB dongles, smart devices, wireless customer premise equipment (CPE), Internet of Things (IoT) devices such as watches, wearable devices such as heads-up displays (HMDs), vehicles, drones, medical devices and applications (e.g., remote surgery), industrial devices and applications (e.g., robots and / or other wireless devices operating in the context of an industrial and / or automated processing chain), consumer electronics devices, devices operating in commercial and / or industrial wireless networks, etc. Further, a terminal device may correspond to the mobile termination (MT) part of an integrated access backhaul (IAB) node (so-called relay node). In the following description, the terms "terminal device", "communication device", "terminal", "user equipment", and "UE" may be used interchangeably.

[0025] Currently, there are various applications involving small-scale and low-frequency data exchanges. For example, in some applications of mobile devices, SDT includes traffic from instant message (IM) services, such as heartbeats or keep-alive traffic from an IM or email client and other services, push notifications from various applications, traffic from wearables (e.g., including periodic positioning information), etc. In some applications of non-mobile devices, SDT includes sensor data (e.g., temperature, pressure measurements sent periodically or in an event-triggered manner in an IoT network), measurement and warning information sent from smart meters, and / or the like.

[0026] As described above, for an RRC resume request of SDT, one possible response is an RRC reject message. According to the conventional solution, when receiving an RRC reject message for an RRC resume request, the terminal device remains in the inactive state. If the RRC reject message includes a waiting time, the terminal device waits until the waiting time expires before a new RRC resume request is attempted.

[0027] It can be seen that the current form of RRC rejection may stop the RRC resume request of SDT and prevent one or more additional SDT or non-SDT RRC resume requests within the waiting time. In fact, when the system is congested, the network device may want to admit non-SDT but not SDT, which may be because SDT and non-SDT may target different services (e.g., SDT usually targets background messages), and it is not beneficial not to permit all resources during the waiting time.

[0028] Taking this into consideration, embodiments of the present disclosure provide an improved solution for the RRC rejection procedure of SDT. This solution can reject the resume procedure for a part of data transmission including SDT. In this way, the resume procedure for non-SDT can still be made possible. Furthermore, even in the case of the RRC rejection procedure, non-congested resources for SDT or non-SDT may be used. Also, the service for the terminal device is not delayed. Hereinafter, with reference to the drawings, the principles and embodiments of the present disclosure will be described in detail.

[0029] Example of a communication network FIG. 1 shows a schematic diagram of an exemplary communication network 100 in which some embodiments of the present disclosure may be implemented. As shown in FIG. 1, the communication network 100 may include a first device 110 and a second device 120. In some embodiments, the first device 110 may be a terminal device, and the second device 120 may be a network device.

[0030] For the purpose of illustration only, and without suggesting any limitation as to the scope of the present disclosure, some embodiments will be described in the situation where the first device 110 is a terminal device and the second device 120 is a network device. It should be understood that in other embodiments, the first device 110 may be a network device, and the second device 120 may be a terminal device. In other words, the principles and spirit of the present disclosure can be applied to both uplink transmission and downlink transmission.

[0031] It should be understood that the number and type of the first and second devices as shown in FIG. 1 are for illustrative purposes only and do not suggest any limitation. The network 100 may include any suitable number and type of the first and second devices suitable for implementing the embodiments of the present disclosure.

[0032] As shown in FIG. 1, the first device 110 can communicate with the second device 120 via a channel such as a wireless communication channel. Communication in the communication network 100 can comply with any suitable standard including, but not limited to, Global System for Mobile Communications (GSM), Long Term Evolution (LTE), LTE-Evolution, LTE-Advanced (LTE-A), Wideband Code Division Multiple Access (WCDMA (registered trademark)), Code Division Multiple Access (CDMA), GSM Edge Radio Access Network (GERAN), Machine-Type Communication (MTC), etc. Further, the communication can be performed according to any generation of communication protocol known currently or developed in the future. Examples of communication protocols include, but are not limited to, the first generation (1G), second generation (2G), 2.5G, 2.75G, third generation (3G), fourth generation (4G), 4.5G, fifth generation (5G) communication protocols.

[0033] In some scenarios, the first device 110 may want to send data such as small-scale and low-frequency data traffic to the second device 120 in an inactive state. In some embodiments, the first device 110 can execute a non-SDT procedure to send data. In some embodiments, the first device 110 can execute an SDT procedure to send data. For example, the first device 110 can execute a non-SDT procedure or an SDT procedure based on a random access procedure. This will be described in relation to FIGS. 2 and 3.

[0034] In some embodiments, the random access procedure may be a 4-step RACH procedure. FIG. 2 shows an exemplary 4-step RACH procedure 200 according to some embodiments of the present disclosure. For convenience, the procedure 200 will be described with reference to FIG. 1. The procedure 200 can include the first device 110 and the second device 120 as shown in FIG. 1.

[0035] As shown in FIG. 2, the first device 110 can transmit a random access preamble (also referred to as Msg1) 210 to the second device 120 on the physical random access channel (PRACH). The second device 120 can transmit a random access response (also referred to as Msg2) 220 to the second device 120 on the physical downlink shared channel (PDSCH). Next, the first device 110 can transmit a scheduled transmission (also referred to as Msg3) 230 to the second device 120 on the physical uplink shared channel (PUSCH). The second device 120 can transmit a contention resolution (also referred to as Msg4) 240 to the first device 110 on the PDSCH.

[0036] In some embodiments, the first device 110 can transmit an RRC resume request or an RRC setup request for non-SDT in Msg3. In this way, a non-SDT procedure based on the 4-step RACH can be started. When receiving an RRC resume message from the second device 120, the first device 110 can transmit data in a non-SDT procedure based on the 4-step RACH.

[0037] In some embodiments, the first device 110 can transmit an RRC resume request for SDT in Msg3. In this way, an SDT procedure based on the 4-step RACH can be started. In some embodiments, the first device 110 can transmit an RRC resume request in Msg3 and transmit data in a subsequent transmission. In some embodiments, the first device 110 can transmit an RRC resume request and a part of the data in Msg3 and transmit the remaining part of the data in a subsequent transmission. In some embodiments, the second device 120 can transmit a message for rejecting the RRC resume request to the first device 110 in Msg4.

[0038] In some embodiments, the random access procedure may be a two-step RACH procedure. FIG. 3 shows an exemplary two-step RACH-based SDT procedure 300 according to some embodiments of the present disclosure. For convenience, procedure 300 will be described with reference to FIG. 1. As shown in FIG. 1, procedure 300 may include a first device 110 and a second device 120.

[0039] As shown in FIG. 3, the first device 110 may transmit a random access preamble and a PUSCH payload (also referred to as MsgA) 310 to the second device 120. The random access preamble may be transmitted on a physical random access channel (PRACH), and the PUSCH payload may be transmitted on the PUSCH. Next, the second device 120 may transmit a contention resolution 320 (also referred to as MsgB) to the first device 110 on the PDSCH.

[0040] In some embodiments, the first device 110 may transmit a non-SDT RRC resume request with MsgA. In this way, a non-SDT procedure based on the two-step RACH can be started. When receiving an RRC resume message from the second device 120, the first device 110 may transmit data in a non-SDT procedure based on the two-step RACH.

[0041] In some embodiments, the first device 110 can send a request to resume SDT with MsgA. In this way, the SDT procedure based on the two-step RACH can be started. In some embodiments, the first device 110 can send data together with an RRC resume request in MsgA. In some embodiments, the first device 110 can send an RRC resume request with MsgA and send data in a subsequent transmission. In some embodiments, the first device 110 can send an RRC resume request and a part of the data with MsgA and send the remaining part of the data in a subsequent transmission. In some embodiments, the second device 120 can send a message for rejecting the RRC resume request to the first device 110 with MsgB.

[0042] In some embodiments, the first device 110 can execute the SDT procedure based on a CG method (not shown) to send data. For example, the first device 110 can send an RRC resume request for SDT and data within the CG resource. As another example, the first device 110 can send the RRC resume request for SDT and the data separately with different CG resources. As a response to the RRC resume request for SDT, the second device 120 can send a message for rejecting the RRC resume request to the first device 110.

[0043] Embodiments of the present application provide a solution for rejecting an RRC resume request for SDT. This solution will be described in detail with reference to FIG. 4.

[0044] Example of Rejection of SDT Resume Request FIG. 4 is a schematic diagram showing a process 400 for communication according to an embodiment of the present disclosure. For the purpose of explanation, the process 400 will be described with reference to FIG. 1. The process 400 can include the first device 110 and the second device 120 as shown in FIG. 1.

[0045] As shown in FIG. 4, the first device 110 transmits a resume request 410 for SDT to the second device 120. For example, when data such as small-scale and low-frequency data traffic reaches the first device 110, the first device 110 can transmit a resume request for SDT. The data may be any suitable data, and it should be understood that the present disclosure does not limit this aspect.

[0046] In some embodiments, the resume request may be an RRCResumeRequest message. In some embodiments, the resume request may be an RRCResumeRequest1 message. In some embodiments, the resume request may include a resume cause that notifies the SDT. The resume request may adopt any other suitable manner, and it should be noted that the present disclosure does not limit this aspect.

[0047] Upon receiving the resume request, the second device 120 can know that the resume request is for SDT. In some embodiments, when the resume request is transmitted on a random access resource reserved for SDT, the second device 120 can determine that the resume request is for SDT. In some embodiments, when Msg3 includes an indication that the resume request is for SDT, the second device 120 can determine that the resume request is for SDT. In some embodiments, when data is transmitted together with the resume request, the second device 120 can determine that the resume request is for SDT.

[0048] In this case, the second device 120 transmits a message 420 for rejecting some resume requests for data transmission. Some of the data transmission includes SDT. In some embodiments, the message may be an RRCReject message. Of course, any other suitable form can also be realized.

[0049] In this way, it is also possible to resume the non-SDT procedure. Further, even in the case of the RRC rejection procedure, resources for SDT or non-SDT may be used without congestion. Further, the service for the terminal device is not delayed. Hereinafter, several exemplary embodiments will be described in accordance with Embodiments 1 to 6.

[0050] Embodiment 1 In this embodiment, the message can notify that the resume request is rejected in SDT but not rejected in non-SDT.

[0051] In some embodiments, there may be a dedicated message defined to specifically notify that the resume request is rejected in SDT but not rejected in non-SDT. In some embodiments, the message can include information (for convenience, also referred to as first information in this specification) notifying that the resume request is rejected for SDT. For example, the message can include a bit for notifying this information. Of course, this is merely an example, and the message can adopt any other appropriate format.

[0052] In this way, the second device 120 can reject the SDT procedure so that only the resume request for SDT is not permitted and the resume request for non-SDT is still permitted.

[0053] Embodiment 2 In this embodiment, the second device 120 can explicitly reject one or more SDT procedures that are not permitted.

[0054] In some embodiments, the message may include information (for convenience, also referred to as second information in this specification) notifying that the resume request is rejected for one or more predetermined types of SDT.

[0055] In some embodiments, a predetermined type of SDT may include an RACH-based SDT. For example, the predetermined type of SDT may be a two-step RACH-based SDT. As another example, the predetermined type of SDT may be a four-step RACH-based SDT. In some embodiments, the predetermined type of SDT may include a CG-based SDT. It should be understood that the present disclosure does not impose any limitation on the type of SDT, and any other suitable type is also feasible.

[0056] In some alternative embodiments, a dedicated message can be defined to specifically notify that a restart request for a specific type of SDT is rejected.

[0057] Therefore, a specific type of SDT may not be permitted, while other specific types of SDT may be permitted. For example, if the above-mentioned other specific types of SDT are not indicated by the second information, the first device can determine that the above-mentioned other specific types of SDT are permitted. A message from the second device (i.e., a rejection message that rejects at least a specific type of SDT) can also notify, additionally or alternatively, which types of SDT are permitted.

[0058] Embodiment 3 In this embodiment, one or more waiting times for various data transmissions can be notified by a message.

[0059] In some embodiments, the message can include information (hereinafter also referred to as the third information for convenience) that notifies at least one of a waiting time for SDT (hereinafter also referred to as the first waiting time for convenience in this specification), a waiting time for one or more predetermined types of SDT (hereinafter also referred to as the second waiting time for convenience in this specification), or a waiting time for non-SDT (hereinafter also referred to as the third waiting time for convenience in this specification). The first device 110 can start a timer for the waiting time for a specific data transmission. When the timer is operating, the first device 110 is prohibited from transmitting a resume request for the specific data transmission.

[0060] In some embodiments, the first, second, and third waiting times can be set to different values. In some embodiments, two or more of the first, second, and third waiting times may be set to the same value. It should also be understood that the number of waiting times is not limited to three, and it is possible to have more or less.

[0061] In some embodiments, different waiting times (i.e., different values of the second waiting time) may be set for different predetermined types of SDT. For example, a predetermined type of SDT may include at least one of a RACH-based SDT or a CG-based SDT. The RACH-based SDT may include at least one of a two-step RACH-based SDT or a four-step RACH-based SDT. Of course, any other suitable type is also feasible. In some alternative embodiments, the same waiting time can be set for different predetermined types of SDT.

[0062] Embodiment 4 In this embodiment, the message can notify whether the first device 110 transitions to an idle state or remains in a non-active state.

[0063] In some embodiments, the message may include information (for convenience, also referred to as fourth information herein) for notifying whether the first device 110 transitions to an idle state or remains in an inactive state. For example, the second device 120 can cause the message to include a bit or field to notify that the first device 110 transitions to an idle state, and cause the message not to include a bit or field to notify that the first device 110 remains in an inactive state.

[0064] As another example, the second device 120 can set a first value of a bit or field included in the message to notify that the first device 110 transitions to an idle state, and set a second value of the bit or field to notify that the first device 110 remains in an inactive state. Of course, these are merely examples, and any other suitable method can also be implemented.

[0065] In some embodiments, the dedicated message can be defined to specifically notify that the first device 110 transitions to an idle state. In some embodiments, other dedicated messages can be defined to specifically notify that the first device 110 remains in an inactive state.

[0066] Embodiment 5 In this embodiment, when receiving a message for rejecting a resume request of SDT, the first device 110 can start a non-SDT procedure for transmitting data to the second device 120.

[0067] In some embodiments, the message can adopt the existing format of the RRC rejection message. In some embodiments, the message may be a dedicated message newly defined to notify a rejection of SDT, for example, an SDT rejection message. Of course, other suitable formats are also suitable for the message.

[0068] In some embodiments where data transmission using SDT is rejected, upon receiving an RRC rejection message, the first device 110 may initiate a non - SDT procedure to transmit data to the second device 120. In some embodiments where data is transmitted with a rejected resume request, the first device 110 may initiate a non - SDT procedure to transmit data to the second device 120. In some embodiments where all data that was scheduled to be transmitted using the SDT procedure is not transmitted with the rejected SDT resume request, the first device 110 may also initiate a non - SDT procedure to transmit data to the second device 120. In some embodiments where data is not transmitted with the rejected SDT resume request, the first device 110 may also initiate a non - SDT procedure to transmit data to the second device 120. The data transmitted using the non - SDT procedure may include the data transmitted with the SDT resume request and / or the remaining data not transmitted with the resume request.

[0069] In some embodiments, upon receiving an RRC rejection message, the first device 110 may initiate a non - SDT procedure for transmitting subsequent data that arrives at the first device 110 to the second device 120. The non - SDT procedure may be executed in a manner similar to that described in FIGS. 2 and 3, and thus will not be repeated here.

[0070] In some embodiments, the first device 110 may not be permitted to execute SDT upon receiving an RRC rejection message, but may only initiate a non - SDT resume procedure when there is a resume event, regardless of whether it is for an SDT RB, or a non - SDT RB, or whether other criteria are met. In some embodiments, the first device 110 may consider the SDT waiting time to be infinite upon receiving an RRC rejection message.

[0071] In some embodiments, the first device 110 is not permitted to execute SDT upon receiving an RRC rejection message and can only initiate non-SDT procedures. In some examples, upon receiving an RRC rejection message, the first device 110 enters the IDLE mode (i.e., the idle state), and can trigger non-SDT establishment procedures if there is an establishment event regardless of whether it is for an SDT RB, a non-SDT RB, or other criteria are met. In some examples, upon receiving an RRC rejection message, the first device 110 enters the INACTIVE mode (i.e., the inactive state), and can trigger non-SDT resume procedures if there is a resume event regardless of whether it is for an SDT RB, a non-SDT RB, or other criteria are met. Alternatively, the first device 110 can trigger SDT resume procedures when there is a resume event for an SDT RB or regardless of whether other criteria are met. To avoid the possibility of security threats, in some examples, the first device 110 can notify in non-SDT resume procedures or SDT resume procedures that a security key update is required, that the current key is being reused, or that the current key is being used multiple times in the resume procedure. Based on such a notification, the second device 120 can update one or more security keys before new data is transmitted.

[0072] Embodiment 6 In this embodiment, the second device 120 can explicitly specify not to permit a specific radio bearer (RB) for SDT.

[0073] In some embodiments, the message may include information (hereinafter also referred to as fifth information for convenience) notifying that a resume request is rejected for one or more predetermined types of RBs associated with the first device 110. In some embodiments, the predetermined type of RB may include a signaling radio bearer (SRB). In some embodiments, the predetermined type of RB may include a data radio bearer (DRB).

[0074] In some embodiments, the fifth information may notify that the resume request is rejected for the SDT RB. For example, the fifth information may notify that the resume request is rejected for the SDT SRB. As another example, the fifth information may notify that the resume request is rejected for a specific SDT DRB. In some embodiments, the fifth information may notify that the resume request is rejected for an RB other than the SDT. It should be noted that these are merely examples and are not intended to limit the present disclosure.

[0075] In some alternative embodiments, a dedicated message can be defined to specifically notify that a resume request is rejected for a specific type of RB.

[0076] So far, the solution to the RRC rejection of the SDT according to the present disclosure has been described. Thus, the resume procedure for non-SDT is still possible. Furthermore, even in the case of the RRC rejection procedure, non-contended resources for SDT or non-SDT may be used. Also, the service to the terminal device will not be delayed.

[0077] Examples of the method Next, some exemplary methods according to the embodiments of the present disclosure will be described in detail with reference to FIGS. 5 to 8. However, those skilled in the art will easily understand that the detailed description provided herein with respect to these figures is for illustrative purposes only, as the present disclosure extends beyond these limited embodiments.

[0078] FIG. 5 shows a flowchart of a communication method 500 implemented on a first device according to an exemplary embodiment of the present disclosure. The method 500 can be implemented on the first device 110 shown in FIG. 1. For the sake of explanation, the method 500 will be described with reference to FIG. 1. The method 500 may further include additional blocks (not shown) and / or may omit some of the illustrated blocks, and it should be understood that the scope of the present disclosure is not limited in this regard.

[0079] As shown in FIG. 5, at block 510, the first device 110 transmits a resume request for the SDT to the second device 120.

[0080] At block 520, the first device 110 receives from the second device 120 a message for rejecting a resume request for a part of data transmission that includes the SDT. In some embodiments, the message can notify that the resume request is rejected for the SDT but not for non-SDT. In some embodiments, the message may include first information notifying that the resume request is rejected for the SDT.

[0081] In some embodiments, the first device 110 can receive the message by receiving second information notifying that the resume request is rejected for one or more predetermined types of SDT. In other words, the message may include the second information.

[0082] In some embodiments, the first device 110 can receive the message by receiving third information notifying at least one of a first waiting time for the SDT, a second waiting time for one or more predetermined types of SDT, or a third waiting time for non-SDT. In other words, the message may include the third information. In some embodiments, one or more predetermined types of SDT may include at least one of a RACH-based SDT or a CG-based SDT.

[0083] In some embodiments, the first device 110 can receive a message by receiving fourth information that notifies whether the first device 110 transitions to an idle state or remains in a non-active state.

[0084] In some embodiments, the first device 110 can initiate a non-SDT procedure for transmitting data to the second device 120 in response to receiving the message. In some embodiments, the data may at least include data that has been rejected from being transmitted using small-scale data transmission. In some embodiments, the data may include data transmitted together with a resume request.

[0085] In some embodiments, the first device 110 can receive a message by receiving fifth information that notifies that a resume request is rejected for a predetermined type of RB associated with the first device 110.

[0086] The operations in the method of FIG. 5 correspond to the operations in the process described in FIG. 4, and thus other details are omitted here for brevity. In the method of FIG. 5, non-SDT resume procedures are also possible. Further, even in the case of an RRC rejection procedure, non-converging resources for SDT or non-SDT can be used. Further, the service for the first device 110 is not delayed.

[0087] Correspondingly, embodiments of the present disclosure also provide a method of communication implemented in a second device. FIG. 6 shows a flowchart of a method 600 of communication implemented in a second device according to an exemplary embodiment of the present disclosure. The method 600 can be implemented in the second device 120 shown in FIG. 1. For the sake of explanation, the method 600 will be described with reference to FIG. 1. The method 600 may further include additional blocks (not shown) and / or some of the illustrated blocks may be omitted, and it should be understood that the scope of the present disclosure is not limited in this regard.

[0088] As shown in FIG. 6, in block 610, the second device 120 receives a resume request for SDT from the first device 110.

[0089] In block 620, the second device 120 transmits a message to the first device 110 to reject the resume request for a part of the data transmission that includes the SDT. In some embodiments, the message may notify and instruct that the resume request is rejected for the SDT but not for non - SDT. In some embodiments, the message may include first information notifying that the resume request is rejected for the SDT.

[0090] In some embodiments, the second device 120 can transmit the message by transmitting second information notifying that the resume request is rejected for one or more predetermined types of SDT. In other words, the message may include the second information.

[0091] In some embodiments, the second device 120 can transmit the message by transmitting third information notifying at least one of a first waiting time for SDT, a second waiting time for one or more predetermined types of SDT, or a third waiting time for non - SDT. In other words, the message may include the third information. In some embodiments, one or more predetermined types of SDT may include at least one of a RACH - based SDT or a CG - based SDT.

[0092] In some embodiments, the second device 120 can transmit the message by transmitting fourth information notifying whether the first device 110 transitions to an idle state or remains in a non - active state.

[0093] In some embodiments, the second device 120 can send a message by sending fifth information notifying that a resume request is rejected for a predetermined type of RB associated with the first device 110.

[0094] The operations in the method of FIG. 6 correspond to the operations in the process described in FIG. 4, and thus other details are omitted here for brevity. In the method of FIG. 6, the resume procedure for SDT is rejected, but the resume procedure for non-SDT may be permitted.

[0095] Examples of Apparatus and Devices In some embodiments, an apparatus (e.g., the first device 110) capable of executing the method 500 can include means for executing each step of the method 500. The means can be implemented in any suitable form. For example, the means may be implemented as a circuit or a software module.

[0096] In some embodiments, the apparatus can include means for sending a resume request for SDT to the second device in the first device, and means for receiving, from the second device, a message for rejecting a resume request for a part of data transmission that includes SDT.

[0097] In some embodiments, a message for rejecting a resume request can notify that the resume request is rejected for SDT but not for non-SDT. In some embodiments, a message for rejecting a resume request may include first information notifying that the resume request is rejected for SDT.

[0098] In some embodiments, the means for receiving a message can comprise means for receiving second information notifying that a resume request has been rejected for one or more predetermined types of SDTs. In some embodiments, the means for receiving a message can comprise means for receiving third information notifying at least one of a first waiting time for an SDT, a second waiting time for one or more predetermined types of SDTs, or a third waiting time for a non-SDT. In some embodiments, one or more predetermined types of SDTs can include at least one of a RACH-based SDT or a CG-based SDT.

[0099] In some embodiments, the means for receiving a message can comprise means for receiving fourth information notifying whether the first device transitions to an idle state or remains in a non-active state.

[0100] In some embodiments, the apparatus can further comprise means for initiating a non-SDT procedure for transmitting data to a second device in response to receiving a message. In some embodiments, the data can at least include data for which transmission using an SDT has been rejected. In some embodiments, the data can include data transmitted together with a resume request.

[0101] In some embodiments, the means for receiving a message can comprise means for receiving fifth information notifying that a resume request has been rejected for a predetermined type of radio bearer associated with the first device.

[0102] In some embodiments, an apparatus (e.g., the second device 120) capable of executing method 600 can comprise means for executing each step of method 600. The means can be implemented in any suitable form. For example, the means can be implemented in a circuit or a software module.

[0103] In some embodiments, the apparatus can comprise, in a second device, means for receiving, from a first device, a resume request for SDT, and means for transmitting, to the first device, a message for rejecting a resume request for a part of data transmission that includes the SDT.

[0104] In some embodiments, the message for rejecting the resume request can notify that the resume request is rejected for SDT but not for non-SDT. In some embodiments, the message for rejecting the resume request can include first information notifying that the resume request is rejected for SDT.

[0105] In some embodiments, the means for transmitting the message can comprise means for transmitting second information notifying that the resume request is rejected for one or more predetermined types of SDT. In some embodiments, the means for transmitting the message can comprise means for transmitting third information notifying at least one of a first waiting time for SDT, a second waiting time for one or more predetermined types of SDT, or a third waiting time for non-SDT. In some embodiments, one or more predetermined types of SDT can include at least one of a RACH-based SDT or a CG-based SDT.

[0106] In some embodiments, the means for transmitting the message can comprise means for transmitting fourth information notifying whether the first device transitions to an idle state or remains in a non-active state.

[0107] In some embodiments, the means for transmitting the message can comprise means for transmitting fifth information notifying that the resume request is rejected for a predetermined type of radio bearer associated with the first device.

[0108] FIG. 7 is a simplified block diagram of a device 700 suitable for implementing an embodiment of the present disclosure. The device 700 may be provided to implement a first device or a second device, such as the first device 70 or the second device 120 as shown in FIG. 1. As shown, the device 700 includes one or more processors 710, one or more memories 720 connected to the processor 710, and one or more communication modules 740 (such as a transmitter and / or a receiver) connected to the processor 710.

[0109] The communication module 740 is for two-way communication. The communication module 740 has at least one antenna to facilitate communication. The communication interface can represent any interface necessary for communication with other network elements.

[0110] The processor 710 may be of any type suitable for a local technical network and may include, by way of non-limiting example, one or more of a general-purpose computer, a special-purpose computer, a microprocessor, a digital signal processor (DSP), and a processor based on a multi-core processor architecture. The device 700 can have multiple processors, such as an application-specific integrated circuit chip that is time-slaved to a clock that synchronizes the main processor.

[0111] The memory 720 can include one or more non-volatile memories and one or more volatile memories. Examples of non-volatile memories include, but are not limited to, read-only memory (ROM) 724, electrically programmable read-only memory (EPROM), flash memory, hard disk, compact disk (CD), digital video disk (DVD), and other magnetic storage devices and / or optical storage devices. Examples of volatile memories include, but are not limited to, random access memory (RAM) 722 and other volatile memories that do not persist during power-down times.

[0112] The computer program 730 includes computer-executable instructions that are executed by a related processor 710. The program 730 may be stored in the ROM 724. The processor 710 can execute any appropriate operations and processes by loading the program 730 into the RAM 722.

[0113] Embodiments of the present disclosure can be implemented by the program 730 such that the device 700 can execute any process of the present disclosure, as described with reference to FIGS. 1-6. Embodiments of the present disclosure can also be implemented by hardware, or by a combination of software and hardware.

[0114] In some embodiments, the program 730 can be tangibly embodied on a computer-readable medium that can be included in the device 700 (such as within the memory 720) or other storage devices accessible by the device 700. The device 700 can load and execute the program 730 from the computer-readable medium into the RAM 722. The computer-readable medium can include any type of tangible non-volatile storage device such as ROM, EPROM, flash (registered trademark) memory, hard disk, CD, DVD, etc. FIG. 8 shows an example of a computer-readable medium 800 in the form of a CD or DVD. The program 730 is stored on this computer-readable medium.

[0115] Generally, various embodiments of the present disclosure may be implemented in hardware or special-purpose circuitry, software, logic, or any combination thereof. Some aspects may be implemented in hardware, while other aspects may be implemented in firmware or software executable by a controller, microprocessor, or other computing device. Various aspects of the embodiments of the present disclosure are illustrated and described using block diagrams, flowcharts, or other graphical representations, but the blocks, devices, systems, techniques, or methods described herein may be implemented, by way of non-limiting example, in hardware, software, firmware, special-purpose circuitry or logic, general-purpose hardware or controllers, or other computing devices, or any combination thereof.

[0116] The present disclosure also provides at least one computer program product tangibly stored on a non-transitory computer-readable storage medium. The computer program product includes computer-executable instructions, such as those included in program modules, that are executed on a device on a target real or virtual processor to perform methods 500-600 as described above with reference to FIGS. 5-6. Generally, program modules include routines, programs, libraries, objects, classes, components, data structures, etc., and perform specific tasks or implement specific abstract data types. The functions of program modules may be combined or divided among program modules as desired in various embodiments. The machine-executable instructions of program modules may be executed within a local or distributed device. In a distributed device, program modules may be located on both local and remote storage media.

[0117] The program code for implementing the method of the present disclosure can be described in any combination of one or more programming languages. These program codes can be provided to a processor or a controller of a general-purpose computer, a special-purpose computer, or other programmable data processing devices, so that when the program code is executed by the processor or the controller, the functions / operations specified in the flowchart and / or block diagram are implemented. The program code may be executed entirely on the machine, partially on the machine, executed as a stand-alone software package, partially executed on the machine and partially executed on a remote machine, or executed entirely on a remote machine or server.

[0118] In the context of the present disclosure, the computer program code or related data can be carried by any suitable carrier in order to enable a device, apparatus, or processor to execute various processes and operations as described above. Examples of carriers include signals, computer-readable media, and the like.

[0119] The computer-readable medium may be a computer-readable signal medium or a computer-readable storage medium. The computer-readable medium includes, but is not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any suitable combination of the foregoing. More specific examples of computer-readable storage media include electrical connections having one or more wires, portable computer diskettes, hard disks, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM or flash (registered trademark) memory), optical fiber, portable compact disk read-only memory (CD-ROM), optical storage devices, magnetic storage devices, or any suitable combination of the foregoing.

[0120] Furthermore, the operations are depicted in a particular order, but this should not be construed as requiring that such operations be performed in the particular order shown, or sequentially, or that all of the illustrated operations be performed, to achieve the desired result. In certain circumstances, multitasking and parallel processing may be advantageous. Similarly, although some specific implementation details are included in the above discussion, these should not be construed as limiting the scope of the present disclosure, but rather as explanations of features that may be specific to a particular embodiment. Specific features described in the context of separate embodiments may also be implemented in combination in a single embodiment. Conversely, various features described in the context of a single embodiment may also be implemented separately, or in any suitable subcombination, in a plurality of embodiments.

[0121] The present disclosure has been described in language specific to structural features and / or methodological acts, but it is to be understood that the present disclosure as defined in the appended claims is not necessarily limited to the specific features or acts described above. Rather, the specific features and acts described above are disclosed as exemplary forms of implementing the claims.

Claims

1. A first device, comprising: at least one processor; and at least one memory including computer program code, wherein the at least one memory and the computer program code are configured to cause the at least one processor to cause the first device to send a resume request for at least one radio bearer for small-scale data transmission and at least one radio bearer for non-small-scale data transmission to a second device, receive, from the second device, a message that rejects the resume request for the at least one radio bearer for small-scale data transmission and does not reject the resume request for the at least one radio bearer for non-small-scale data transmission, and perform the above.

2. The first device according to claim 1, wherein the message for rejecting the resume request notifies that the resume request is rejected for small-scale data transmission but not for non-small-scale data transmission.

3. The first device according to claim 1 or 2, wherein the message for rejecting the resume request includes first information notifying that the resume request is rejected for small-scale data transmission.

4. The first device, receives second information notifying that the resume request is rejected for one or more predetermined types of small-scale data transmission, whereby the message is received.

5. The first device, receives third information notifying at least one of a first waiting time for small-scale data transmission, a second waiting time for one or more predetermined types of small-scale data transmission, and a third waiting time for non-small-scale data transmission, whereby the message is received.

6. The one or more predetermined types of small-scale data transmission include random access-based small-scale data transmission, configured grant-based small-scale data transmission, at least one of which is included.

7. The first device, receives fourth information notifying whether the first device transitions to an idle state or remains in a non-active state. The first device according to claim 1, which is adapted to receive the message by

8. The first device further starts a non-small-scale data transmission procedure for transmitting data to the second device in response to receiving the message, The first device according to claim 1, which is adapted to perform

9. The first device according to claim 8, wherein the data at least includes data for which transmission using the small-scale data transmission has been rejected.

10. The first device according to claim 8 or 9, wherein the data includes data transmitted together with the restart request.

11. The first device receives fifth information notifying that the restart request is rejected for a predetermined type of radio bearer associated with the first device, The first device according to claim 1, which is adapted to receive the message by

12. The first device according to claim 1, wherein the first device is a terminal device and the second device is a network device.

13. A second device, comprising at least one processor, and at least one memory including computer program code, wherein the at least one memory and the computer program code cause the at least one processor to cause the second device to receive a restart request for at least one radio bearer for small-scale data transmission and at least one radio bearer for non-small-scale data transmission from a first device, send a message to the first device rejecting the restart request for the at least one radio bearer for small-scale data transmission and not rejecting the restart request for the at least one radio bearer for non-small-scale data transmission, A second device configured to perform

14. The second device according to claim 13, wherein the message for rejecting the restart request notifies that the restart request is rejected for small-scale data transmission but not for non-small-scale data transmission.

15. The second device according to claim 13 or 14, wherein the message for rejecting the restart request includes first information notifying that the restart request is rejected for small-scale data transmission.

16. The second device Transmitting second information notifying that the resumption request is rejected for one or more predetermined types of small-scale data transmissions The second device according to claim 13, wherein the message is transmitted thereby

17. The second device transmits third information notifying at least one of a first waiting time for small-scale data transmission, a second waiting time for one or more predetermined types of small-scale data transmissions, and a third waiting time for non-small-scale data transmission whereby the message is transmitted, the second device according to claim 13

18.

18. The one or more predetermined types of small-scale data transmissions include at least one of random access-based small-scale data transmission and configured grant-based small-scale data transmission the second device according to claim 16 or 17

19. The second device transmits fourth information notifying whether the first device shifts to an idle state or remains in a non-active state whereby the message is transmitted, the second device according to claim 13

20. The second device transmits fifth information notifying that the resumption request is rejected for a predetermined type of radio bearer associated with the first device whereby the message is transmitted, the second device according to claim 13

21. The first device is a terminal device and the second device is a network device, the second device according to claim 13

22. In a first device, transmitting a resumption request for at least one radio bearer for small-scale data transmission and at least one radio bearer for non-small-scale data transmission to a second device Receiving, from the second device, a message rejecting the resumption request for the at least one radio bearer for small-scale data transmission and not rejecting the resumption request for the at least one radio bearer for non-small-scale data transmission A communication method including this

23. The message for rejecting the resumption request notifies that the resumption request is rejected for small-scale data transmission but not for non-small-scale data transmission, the method according to claim 22

24. The method according to claim 22 or 23, wherein the message for rejecting the resume request includes first information notifying that the resume request is rejected for small data transmission. **Claim 25** Receiving the message includes receiving second information notifying that the resume request is rejected for one or more predetermined types of small data transmission. The method according to claim 22. **Claim 26** Receiving the message includes receiving third information notifying at least one of a first waiting time for small data transmission, a second waiting time for one or more predetermined types of small data transmission, and a third waiting time for non-small data transmission. The method according to claim 22. **Claim 27** The one or more predetermined types of small data transmission include at least one of random access-based small data transmission, configured grant-based small data transmission. The method according to claim 25 or 26. **Claim 28** Receiving the message includes receiving fourth information notifying whether the first device transitions to an idle state or remains in a non-active state. The method according to claim 22. **Claim 29** The method according to claim 22, further including starting a non-small data transmission procedure for transmitting data to the second device in response to receiving the message. **Claim 30** The method according to claim 29, wherein the data at least includes data for which transmission using the small data transmission is rejected. **Claim 31** The method according to claim 29 or 30, wherein the data includes data transmitted together with the resume request. **Claim 32** Receiving the message includes receiving fifth information notifying that the resume request is rejected for a predetermined type of radio bearer associated with the first device. The method according to claim 22. **Claim 33** The method according to claim 22, wherein the first device is a terminal device and the second device is a network device. **Claim 34** In a second device, receiving a resume request for at least one radio bearer for small data transmission and at least one radio bearer for non-small data transmission from a first device Transmit a message that rejects the resume request for the at least one radio bearer for small-scale data transmission to the first device and does not reject the resume request for the at least one radio bearer for non-small-scale data transmission. A communication method including this.

35. The method according to claim 34, wherein the message for rejecting the resume request notifies that the resume request is rejected for small-scale data transmission but not for non-small-scale data transmission.

36. The method according to claim 34 or 35, wherein the message for rejecting the resume request includes first information notifying that the resume request is rejected for small-scale data transmission.

37. Transmitting the message includes transmitting second information notifying that the resume request is rejected for one or more predetermined types of small-scale data transmission. The method according to claim 34.

38. Transmitting the message includes transmitting third information notifying at least one of a first waiting time for small-scale data transmission, a second waiting time for one or more predetermined types of small-scale data transmission, and a third waiting time for non-small-scale data transmission. The method according to claim 34.

39. The method according to claim 37 or 38, wherein the one or more predetermined types of small-scale data transmission include at least one of random access-based small-scale data transmission and configured grant-based small-scale data transmission.

40. Transmitting the message includes transmitting fourth information notifying whether the first device transitions to an idle state or remains in a non-active state. The method according to claim 34.

41. Transmitting the message includes transmitting fifth information notifying that the resume request is rejected for a predetermined type of radio bearer associated with the first device. The method according to claim 34.

42. The method according to claim 34, wherein the first device is a terminal device and the second device is a network device.

43. A non-transitory computer-readable medium including program instructions for causing an apparatus to execute the method according to any one of claims 22 to 33.

44. ​ ​ A non-transitory computer-readable medium including program instructions for causing an apparatus to execute the method according to any one of claims 34 to 42.

Images