Methods, devices, and computer storage media for communication

Abstract

Embodiments of the present disclosure relate to a method, device and computer readable medium for communication. A network device sends a configuration of a bandwidth part to a terminal device, the bandwidth part being used for transmission of uplink data in an inactive state, the configuration comprising a configured grant. When the terminal device decides to transmit uplink data in the inactive state, the terminal device determines the configured grant from the configuration of the bandwidth part, and transmits the uplink data to the network device based on the configured grant in the inactive state. In this way, small data transmission based on the configured grant can be enhanced.

Description

TECHNICAL FIELD

[0001] Embodiments of the present disclosure generally relate to the field of telecommunications, and particularly relate to a communication method, device and computer storage medium for data transmission in an inactive state of a terminal device. BACKGROUND

[0002] Typically, a terminal device in an inactive state can still have small and infrequent data traffic to be transmitted. Before the third generation partnership project (3GPP) Release 16, the inactive state cannot support data transmission, and the terminal device has to resume the connection (i.e., enter the connected state) for any downlink data and uplink data. This will result in unnecessary power consumption and signaling overhead.

[0003] In this case, the 3GPP Release 17 has approved small data transmission (SDT) in an inactive state. Thereby, the signaling overhead can be reduced. In this case, how to perform SDT in an inactive state has become a hot issue. SUMMARY

[0004] Generally, embodiments of the present disclosure provide a method, device and computer storage medium for communication.

[0005] In a first aspect, a method for communication is provided. The method comprises: determining, at a terminal device, a configured grant from a configuration of a bandwidth part for transmission of uplink data in an inactive state according to a determination that the uplink data is to be transmitted in the inactive state; and transmitting, to a network device, the uplink data in the inactive state based on the configured grant.

[0006] In a second aspect, a method for communication is provided. The method comprises: transmitting, to a terminal device at a network device, a configuration of a bandwidth part for transmission of uplink data from the terminal device in an inactive state, the configuration comprising a configured grant; and receiving the uplink data from the terminal device based on the configured grant, the uplink data being transmitted by the terminal device in the inactive state.

[0007] In a third aspect, a terminal device is provided. The terminal device comprises a processor and a memory coupled to the processor. The memory stores instructions which, when executed by the processor, cause the terminal device to perform the method according to the first aspect of the present disclosure.

[0008] In a fourth aspect, a network device is provided. The network device comprises a processor and a memory coupled to the processor. The memory stores instructions which, when executed by the processor, cause the network device to perform the method according to the second aspect of the present disclosure.

[0009] In a fifth aspect, a computer readable medium having instructions stored thereon is provided. The instructions, when executed on at least one processor, cause the at least one processor to perform the method according to the first aspect of the present disclosure.

[0010] In a sixth aspect, a computer readable medium having instructions stored thereon is provided. The instructions, when executed on at least one processor, cause the at least one processor to perform the method according to the second aspect of the present disclosure.

[0011] Other features of the present disclosure will become apparent from the following description. BRIEF DESCRIPTION OF DRAWINGS

[0012] The above and other objects, features and advantages of the present disclosure will become more apparent from the following description when taken in conjunction with the accompanying drawings, in which:

[0013] Figure 1 An example communication network in which some embodiments of the present disclosure can be implemented is illustrated;

[0014] Figure 2A A schematic diagram illustrating a communication procedure during CG-based SDT under contention resolution mechanism according to an embodiment of the present disclosure is shown;

[0015] Figure 2B A schematic diagram illustrating a communication procedure during CG-based SDT under contention resolution mechanism according to an embodiment of the present disclosure is shown;

[0016] Figure 2C A schematic diagram illustrating a communication procedure during CG-based SDT under contention resolution mechanism according to an embodiment of the present disclosure is shown;

[0017] Figure 3 A schematic diagram illustrating a medium access control control element (MAC CE) for CG-based SDT according to an embodiment of the present disclosure is shown;

[0018] Figure 4 A schematic diagram illustrating a medium access control protocol data unit (MAC PDU) for CG-based SDT according to an embodiment of the present disclosure is shown;

[0019] Figure 5 A schematic diagram illustrating a MAC PDU for CG-based SDT according to an embodiment of the present disclosure is shown;

[0020] Figure 6 A schematic diagram illustrating a MAC PDU for CG-based SDT according to an embodiment of the present disclosure is shown;

[0021] Figure 7 An example communication method implemented at a network device is shown, according to some embodiments of the present disclosure;

[0022] Figure 8 An example communication method implemented at a network device is shown, according to some embodiments of the present disclosure; and

[0023] Figure 9 FIG. 1 is a simplified block diagram of a device suitable for implementing embodiments of the present disclosure.

[0024] In all the drawings, like or similar elements are referred to by like or similar reference numerals. DETAILED DESCRIPTION

[0025] The principles of the present disclosure will now be described with reference to some embodiments. It should be understood that the embodiments are described for illustrative purposes only and help the skilled person to understand and implement the present disclosure, without implying any limitation on the scope of the disclosure. The disclosure described herein can be implemented in various ways different from those described below.

[0026] 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.

[0027] As used herein, the term “terminal device” refers to any device having wireless or wired communication capabilities. Examples of terminal devices include, but are not limited to, a user equipment (UE), a personal computer, a desktop computer, a mobile computer, a cellular phone, a cell phone, a smart phone, a personal digital assistant (PDA), a portable computer, a tablet computer, a wearable device, an Internet of Things (IoT) device, an Internet of Everything (IoE) device, a machine type communication (MTC) device, a vehicle-mounted device for V2X communication (where X denotes a pedestrian, a vehicle, or infrastructure / network), or an image capture device such as a digital camera, a gaming device, a music storage and playback appliance, or an Internet appliance allowing wireless or wired Internet access and browsing, etc. The term “terminal device” can be used interchangeably with UE, mobile station, subscriber station, mobile terminal, user terminal, or wireless device. In addition, the term “network device” refers to a device capable of providing or hosting a cell or coverage in which a terminal device can communicate. Examples of network devices include, but are not limited to, a NodeB (NodeB or NB), an evolved NodeB (eNodeB or eNB), a next-generation NodeB (gNB), a transmit receive point (TRP), a remote radio unit (RRU), a radio head (RH), a remote radio head (RRH), a low power node such as a femto node, a pico node, etc.

[0028] In one embodiment, a terminal device can connect with a first network device and a second network device. One of the first network device and the second network device can be a master node, and the other can be a secondary node. The first network device and the second network device can use different radio access technologies (RATs). In one embodiment, the first network device can be a first RAT device and the second network device can be a second RAT device. In one embodiment, the first RAT device is an eNB and the second RAT device is a gNB. Information related to different RATs can be transmitted from at least one of the first network device and the second network device to the terminal device. In one embodiment, first information can be transmitted from the first network device to the terminal device, and second information can be transmitted from the second network device to the terminal device directly or via the first network device. In one embodiment, information related to configuration of the terminal device configured by the second network device can be transmitted from the second network device via the first network device. Information related to reconfiguration of the terminal device configured by the second network device can be transmitted from the second network device to the terminal device directly or via the first network device.

[0029] 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. The term "includes" and variations thereof are to be read as open terms that mean "including, but not limited to." The term "based on" is to be construed as "based at least in part on." The term "one embodiment" and "an embodiment" are to be read as "at least one embodiment." The term "another embodiment" is to be read as "at least one other embodiment." The terms "first," "second," etc. can refer to different or the same objects. Other explicit or implicit definitions can be included below.

[0030] In some examples, a value, process, or apparatus is referred to as "optimal," "minimum," "maximum," "best," etc. It should be understood that such a description is intended to indicate that a choice can be made in a number of used functional alternatives, and that such a choice is not necessarily better, smaller, higher, or more preferred than other choices.

[0031] Currently, there are various applications that involve small and infrequent exchange of data. For example, in some applications of mobile devices, SDT can include traffic from instant messaging (IM) services, e.g., heartbeats or keep-alive traffic from IM or email clients and other services, push notifications in various applications, traffic from wearable devices including, e.g., periodic positioning information, etc. In some applications of non-mobile devices, SDT can include sensor data (e.g., temperature, pressure readings transmitted periodically or in event-triggered fashion in IoT networks), metering and alarm information transmitted from smart meters, etc.

[0032] Traditionally, there are two mechanisms for transmission using preconfigured uplink resources (PUR), dedicated PUR and shared PUR. Shared PUR allows up to two users to transmit simultaneously and brings savings in transmission resources. In this case, it is of great interest how to perform SDT with PUR, especially for shared PUR.

[0033] Furthermore, it has been agreed that a RRC-less solution (i.e. SDT without RRC message) can be investigated for CGs with lower priority. In this case, it is also needed to investigate how to support SDT for RRC-less. In addition, the use of contention-based PUR can lead to significant savings in transmission resources. Therefore, it is also involved how to support the use of contention-based PUR in SDT.

[0034] In view of this, the embodiments of the present disclosure provide a scheme for SDT (herein also referred to as CG-based SDT) according to configured grant (CG). The scheme can implement CG-based SDT, and also implement contention resolution and backoff mechanisms for CG. The principles and implementations of the present disclosure will be described in detail below with reference to the accompanying drawings.

[0035] Examples of communication networks

[0036] Figure 1 A schematic diagram illustrating an example communication network 100 in which some embodiments of the present disclosure can be implemented is shown. As Figure 1 shown, the communication network 100 can include a terminal device 110 and a network device 120. The terminal device 110 can be served by the network device 120. It should be understood that Figure 1 the number of devices in the communication network 100 is given for illustrative purposes and does not imply any limitation to the present disclosure. The communication network 100 can include any suitable number of network devices and / or terminal devices suitable for implementing the present disclosure.

[0037] As Figure 1 shown, the terminal device 110 can communicate with the network device 120 via a channel such as a wireless communication channel. The communication in the communication network 100 can conform to 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), Code Division Multiple Access (CDMA), GSM EDGE Radio Access Network (GERAN), Machine Type Communication (MTC), etc. Furthermore, the communication can be performed in accordance with any generation of communication protocol currently known or to be developed in the future. Examples of communication protocols include but are not limited to: first generation (1G), second generation (2G), 2.5G, 2.75G, third generation (3G), fourth generation (4G), 4.5G, fifth generation (5G) communication protocols.

[0038] In some cases, the terminal device 110 can perform CG-based SDT when the terminal device 110 has small and infrequent data traffic to send. That is, the terminal device 110 can send uplink data to the network device 120 on a CG in an inactive state. In some embodiments, the CG can be a dedicated PUR. Of course, the CG can also be a shared PUR. In some embodiments, the shared PUR can be a contention-free PUR. Of course, the shared PUR can be a contention-based PUR. In some embodiments, the CG-based SDT can be performed with an RRC message. Of course, the CG-based SDT can also be performed without an RRC message.

[0039] Example implementation of CG-based SDT

[0040] In view of this, embodiments of the present application provide improved communication schemes to support CG-based SDT. The following will describe a communication procedure 200A during CG-based SDT according to embodiments of the present disclosure. Figures 2A to 2C with reference to the accompanying drawings. Figure 2A A schematic diagram of the communication procedure 200A during CG-based SDT according to embodiments of the present disclosure is shown. For the purpose of discussion, the procedure 200A will be described with reference to the terminal device 110 and the network device 120 as shown in Figure 1 Figure 1

[0041] As shown in Figure 2A , the network device 120 can send 201 a configuration of a bandwidth part (BWP) to the terminal device 110. The BWP configuration is specifically configured for SDT. In some embodiments, the BWP configuration includes a CG for SDT. In some embodiments, the BWP is different from an initial BWP. In this way, the traffic load of the initial BWP can be mitigated.

[0042] In some embodiments, the network device 120 can send the BWP configuration in a dedicated message. For example, in some embodiments, the BWP configuration can include a dedicated CG. In these embodiments, the BWP configuration can be specifically provided to the terminal device 110 when the terminal device 110 is in a connected state. Alternatively, the BWP configuration can be specifically provided to the terminal device 110 when the terminal device 110 is put into an inactive state. In this case, the SDT based on the dedicated CG can be performed on a BWP other than the initial BWP. Therefore, the SDT based on the dedicated CG can be configured at a BWP other than the initial BWP.

[0043] ​​Alternatively, the network device 120 can send the BWP configuration in system information. For example, in some embodiments, the BWP configuration can include a shared CG. In these embodiments, the BWP configuration can be provided to the terminal device 110 in system information. In this case, the shared CG based SDT can be performed on a BWP other than the initial BWP. Alternatively, for the shared CG based SDT, the network device 120 can broadcast another one or more dedicated BWPs other than the initial BWP that can be used for the SDT, the another one or more dedicated BWPs having CG resources.

[0044] In some embodiments, the BWP configuration for the SDT can include a candidate set for the CG. For example, multiple CG resources with different grant sizes / periods can be configured. In this way, at least for the shared CG, the terminal device 110 is allowed to select one of the CG resources to perform the SDT.

[0045] When the terminal device 110 has uplink data to transmit and decides to transmit the uplink data in the inactive state, the terminal device 110 can determine 202 a CG according to the BWP configuration. In some embodiments where the BWP configuration includes a candidate set for the CG, the terminal device 110 can select a CG from the candidate set based on a packet size associated with the uplink data. As another example, the terminal device 110 can select a CG from the candidate set based on a traffic pattern associated with the uplink data.

[0046] After determining the CG, the terminal device 110 transmits 203 the uplink data to the network device 120 in the inactive state based on the CG. In some embodiments, the CG based SDT can be triggered if the terminal device 110 has a valid timing advance (TA) for a serving cell of the network device 120.

[0047] In this way, the CG based SDT can be performed on an SDT specific BWP.

[0048] In some embodiments, the SDT can be performed with a radio resource control (RRC) message. For example, the uplink data for the SDT can be sent with an RRC resume request (RRCResumeRequest) message or an RRC resume request 1 (RRCResumeRequestl) message. As another example, the downlink data for the SDT can be sent with an RRC message such as an RRC release (RRCRelease) message and a TA command MAC CE.

[0049] In some alternative embodiments, SDT can be performed without RRC messages (i.e., RRC-less). For example, for CG-based SDT, uplink data can be transmitted directly on the dedicated CG resources configured to the terminal device 110. As another example, the uplink data can be transmitted with a MAC CE containing information of the terminal device 110. For example, the information of the terminal device 110 can be an Inactive Radio Network Temporary Identifier (I-RNTI). Of course, the information can also be a short Resume ShortMAC-I. In some embodiments, downlink data can be transmitted with one or more MAC CEs containing at least one of a contention resolution identity, a TA command, or a Cell Radio Network Temporary Identifier (C-RNTI).

[0050] In some embodiments, considering that CG-based SDT generally occurs on the network device 120 with the context of the terminal device 110, the RRC layer of the terminal device 110 can always provide a short I-RNTI value (24 bits) to the MAC layer. Figure 3 A schematic diagram 300 of a MAC CE for CG-based SDT according to embodiments of the disclosure is shown. In some embodiments, the MAC CE can include a short I-RNTI, as shown in MAC CE 301 of Figure 3 In some embodiments, the MAC CE can also include a ResumeMAC-I, as shown in MAC CE 302 of Figure 3 Alternatively, the ResumeMAC-I and the short I-RNTI can be included in two separate MAC CEs, as shown by reference 303 of Figure 3

[0051] In some embodiments, the network device 120 can indicate 204 to the terminal device 110 whether to use a full I-RNTI. If the network device 120 indicates not to use the full I-RNTI, the RRC layer of the terminal device 110 can provide 205 a short I-RNTI value (24 bits) to the MAC layer and transmit 206 a MAC CE including the short I-RNTI (also referred to herein as a second MAC CE) to the network device 120. If the network device 120 indicates to use the full I-RNTI, the RRC layer of the terminal device 110 can provide a full I-RNTI value (40 bits) to the MAC layer and transmit 206’ a MAC CE including the full I-RNTI (also referred to herein as a first MAC CE) to the network device 120. In some embodiments, the MAC CE can include the full I-RNTI, as shown in MAC CE 304 of Figure 3 ​MAC CE 304. In some embodiments, the MAC CE can also include a resume MAC-I, as shown in FIG. 3B. Figure 3 MAC CE 305. Alternatively, the resume MAC-I and the full I-RNTI can be included in two separate MAC CEs, as shown in FIG. 3C. Figure 3 MAC CE 305. Alternatively, the resume MAC-I and the full I-RNTI can be included in two separate MAC CEs, as shown in FIG. 3C.

[0052] In this way, a MAC CE design is provided for RRC-less CG-based SDT.

[0053] After a CG-based SDT transmission on the uplink, the terminal device 110 can monitor a downlink control channel, e.g., a physical downlink control channel (PDCCH), under control of a timer (also referred to herein as a first timer). In some embodiments, the terminal device 110 can start 207 the first timer upon transmission of uplink data. In some embodiments, the terminal device 110 can only monitor the PDCCH addressed to a CG-based SDT RNTI while the first timer is running. For example, while in a connected state, the terminal device 110 can only monitor the PDCCH addressed to a new RNTI for CG-based SDT, or a reused CS-RNTI for CG-based SDT, or a reused C-RNTI for the UE.

[0054] In some embodiments, the terminal device 110 can reuse a CG transmission timer as the first timer. Of course, the terminal device 110 can introduce a new timer as the first timer.

[0055] In some embodiments, the network device 120 can send 208 a schedule for retransmission of the CG-based SDT to the terminal device 110. For example, the schedule for retransmission can be sent by an uplink grant addressed to the CG-based SDT RNTI. In these embodiments, the terminal device 110 can restart 209 the first timer in response to receiving the schedule for retransmission.

[0056] In some embodiments, the network device 120 can send 210 an indication to the terminal device 120 at expiry of the first timer indicating whether the SDT was successful or failed. In this case, if the indication indicates that the transmission was successful at expiry of the first timer, the terminal device 110 can determine 211 that the SDT was successful at expiry of the first timer. For example, this can apply to dedicated CG-based SDT. If the indication indicates that the SDT failed at expiry of the first timer, the terminal device 110 can determine 211’ that the SDT failed at expiry of the first timer. For example, this can apply to dedicated CG-based SDT and shared CG-based SDT.

[0057] In some embodiments, the network device 120 can transmit 212 a MAC PDU indicating that the uplink data was successfully transmitted. Upon receiving the MAC PDU, the terminal device 110 can stop 213 the first timer. For example, for dedicated CG based SDT, the terminal device 110 can stop the first timer if the PDCCH transmission is addressed to its CG based SDT RNTI and the MAC PDU is successfully decoded. In this case, the terminal device 110 can consider the CG based SDT as successful and indicate the CG based SDT success to upper layer.

[0058] In this way, UE behavior for PDCCH monitoring after CG based SDT is provided.

[0059] Example implementation of CG-based SDT in contention resolution case

[0060] In case multiple terminal devices use the same CG for SDT, contention resolution will be needed. This will be described with reference to Figure 2B . Figure 2B A schematic diagram illustrating a communication procedure 200B during CG based SDT under contention resolution mechanism according to embodiments of the disclosure is shown. For the purpose of discussion, the procedure 200B will be described with reference to Figure 1 the terminal device 110 and the network device 120 as shown in Figure 1 .

[0061] As shown in Figure 2B , the terminal device 110 can start 214 a timer (also referred to as second timer here) for contention resolution upon transmission of uplink data. In this way, the timer can be started for contention resolution after each CG transmission.

[0062] In some embodiments, the second timer can be the same as the first timer. Of course, the second timer can be a separate timer.

[0063] In some embodiments, the network device 120 can transmit 215 scheduling for retransmission of CG based SDT to the terminal device 110. For example, the scheduling for retransmission can be transmitted by an uplink grant addressed to the CG based SDT RNTI. In these embodiments, the terminal device 110 can restart 216 the second timer in response to receiving the scheduling for retransmission.

[0064] In some embodiments, the terminal device 110 can determine 217 that the contention resolution is unsuccessful if the second timer expires.

[0065] In some embodiments, while the second timer is running, the network device 120 can transmit 218 a MAC PDU to the terminal device 110. In some embodiments, the terminal device 110 can stop 219 the second timer upon receiving the MAC PDU. For example, the terminal device 110 can stop the second timer if the MAC PDU is received and the MAC PDU is successfully decoded. Of course, the terminal device 110 can also not stop the second timer upon receiving the MAC PDU.

[0066] In some embodiments, upon receiving the MAC PDU, the terminal device 110 can determine 220 whether the MAC PDU includes a first identification associated with the contention resolution. For example, the terminal device 110 can determine whether the MAC PDU includes a MAC CE for contention resolution identification. If the MAC PDU includes the first identification, the terminal device 110 can determine 221 whether the first identification matches the second identification of the terminal device 110 in the transmission of the uplink data. For example, the terminal device 110 can determine whether the UE content in the MAC CE matches the UE ID information (such as I-RNTI) in the uplink transmission. In some embodiments, the UE contention resolution identification MAC CE for the random access procedure can be reused.

[0067] In the case of CG-based SDT with RRC message, the MAC CE can include all or part of the UL CCCH SDU. In the case of CG-based SDT without RRC message, the MAC CE can include all or part of the information in the UL MAC CE with UE ID information (such as I-RNTI).

[0068] If the first identification matches the second identification, the terminal device 110 can determine 222 that the contention resolution is successful. Accordingly, the terminal device 110 can determine that the CG-based SDT is successful. In this case, if the terminal device 110 receives a TA command in the MAC PDU, the terminal device 110 can execute 223 the TA command. In some embodiments, the terminal device 110 can also receive a C-RNTI in the MAC PDU for the terminal device 110 to use. In some embodiments, one or more of the first identification, the TA command, and the C-RNTI can be included in a single MAC CE. Of course, the first identification, the TA command, and the C-RNTI can also be included in separate MAC CEs.

[0069] If the first identifier does not match the second identifier, terminal device 110 can determine that contention resolution for 224 was unsuccessful. In these embodiments, terminal device 110 can discard the MAC PDU. In this case, terminal device 110 can discard the TA command and C-RNTI (if present).

[0070] In some embodiments, if it is determined that contention resolution is unsuccessful, terminal device 110 may determine that CG-based SDT is unsuccessful. For example, terminal device 110 may indicate to the upper layer that CG-based SDT is unsuccessful.

[0071] In some alternative embodiments, if terminal device 110 determines that contention resolution is unsuccessful, terminal device 110 may perform a CG-based SDT retransmission 225 and restart the second timer. Terminal device 110 may increment the number of CG transmissions, and if the number of CG transmissions equals a predetermined number, terminal device 110 may determine that the CG-based SDT was unsuccessful.

[0072] Example implementation of CG-based SDT in backoff mechanism

[0073] To avoid further contention, when terminal device 110 determines that contention resolution is unsuccessful, terminal device 110 may start a timer during which CG-based SDT on the corresponding CG resource is not allowed. (See below for reference.) Figure 2C Describe it. Figure 2C A schematic diagram illustrating the communication process 200C during a CG-based SDT under a backoff mechanism according to an embodiment of the present disclosure is shown. For discussion purposes, reference will be made to... Figure 1 Describe process 200C. Process 200C may involve, for example: Figure 1 The terminal device 110 and network device 120 are shown.

[0074] like Figure 2C As shown, terminal device 110 can start timer 226 (also referred to herein as the third timer), during which CG-based SDT on the corresponding CG resource is not allowed. That is, terminal device 110 can suspend uplink data transmission on the corresponding CG resource until the third timer expires. After the third timer expires, terminal device 110 can perform 227 SDT based on the corresponding CG resource in an inactive state. In some embodiments, terminal device 110 can retransmit data packets associated with uplink data to network device 120 on the corresponding CG resource. In some embodiments, terminal device 110 can continue to send new data packets associated with uplink data to network device 120 on the corresponding CG resource.

[0075] Regarding the duration of the third timer, network device 120 may send 228 an indicator (also referred to herein as a backoff indicator) for the duration of the third timer. In some embodiments, network device 120 may pre-configure this indicator to terminal device 110 in an RRC message. In some alternative embodiments, network device 120 may send this indicator in a MAC PDU.

[0076] In some embodiments, the MAC PDU may include a header and a MAC CE carrying the indicator, the header including a Logical Channel Identifier (LCID). This allows the use of the current DL MAC PDU format. Figure 4 A schematic diagram 400 of a MAC PDU for a CG-based SDT is shown, according to an embodiment of the present disclosure. Figure 4 As shown, reference numeral 410 indicates an example of a MAC PDU. This MAC PDU may include a MAC subPDU 411, and the MAC subPDU 411 may include a subheader (also referred to herein as a header) 411-1 and a MAC CE 411-2. The header 411-1 may include an LCID for an indicator of a CG-based SDT, and the MAC CE 411-2 may include this indicator. Reference numeral 420 indicates an example of a MAC CE carrying a 4-bit backoff indicator, where the R field 421 represents reserved bits and the BI field 422 represents the backoff indicator. Reference numeral 430 indicates an example of a MAC CE carrying a 5-bit backoff indicator, where the R field 431 represents reserved bits and the BI field 432 represents the backoff indicator.

[0077] In some alternative embodiments, the MAC PDU may include a header and bits indicating the presence of an indicator, the header including the indicator. For example, the first bit may be used to indicate the presence of the indicator. Figure 5 A schematic diagram 500 of a MAC PDU for a CG-based SDT is shown, according to an embodiment of the present disclosure. Figure 5 As shown, reference numeral 510 indicates an example of a MAC PDU. The MAC PDU includes a MAC sub-PDU 511, which contains only the MAC sub-header. Reference numeral 520 indicates an example of a MAC sub-header for a 4-bit backoff indicator. In this example, field B 521 indicates the presence of the backoff indicator, field R 522 indicates reserved bits, and field BI 523 indicates the backoff indicator. For example, field B 521 can be set to "1" to indicate the presence of a backoff indicator field in the sub-header. Of course, field B 521 can also be set to any other suitable value to indicate the presence of a backoff indicator field in the sub-header.

[0078] The reference sign 530 represents an example of a MAC subheader for a 5-bit backoff indicator. In this example, the B field 531 indicates the presence of the backoff indicator, the R field 532 indicates a reserved bit, and the BI field 533 indicates the backoff indicator. For example, the B field 531 can be set to "1" indicating the presence of the backoff indicator field in the subheader. Of course, the B field 531 can also be set to any other suitable value to indicate the presence of the backoff indicator field in the subheader.

[0079] In some alternative embodiments, the indicator can be included in a predetermined byte of the MAC PDU. For example, the indicator can be included in the first byte of the MAC PDU. Figure 6 A schematic diagram 600 illustrating a MAC PDU for CG-based SDT according to embodiments of the present disclosure is shown. As Figure 6 shown, the reference sign 610 represents an example of a MAC PDU. The MAC PDU includes a MAC subPDU 611 which only includes a MAC subheader carrying an indicator. The reference sign 620 represents an example of a MAC subheader for a 4-bit backoff indicator. In this example, the R field 621 represents a reserved bit, and the BI field 622 represents the backoff indicator. The reference sign 630 represents an example of a MAC subheader for a 5-bit backoff indicator. In this example, the R field 631 represents a reserved bit, and the BI field 632 represents the backoff indicator.

[0080] In this way, the terminal device 110 can obtain an indicator for the duration of the third timer. Returning Figure 2C to the example of FIG. 6, the terminal device 110 can then determine 229 the duration of the third timer based on the indicator. In some embodiments, the terminal device 110 can obtain, based on a predefined table, a maximum backoff value corresponding to a value (also referred to as a first value) included in the indicator. An example of the predefined table is shown in Table 1 below. This is merely an example and does not limit the present disclosure.

[0081] Table 1 Example of backoff parameter values

[0082]

[0083] In some embodiments, the terminal device 110 can select a value according to a uniform distribution between zero and the maximum backoff value, and take the selected value as the duration of the third timer. In some embodiments, the backoff parameter values in Table 1 can also be extended as shown in Table 2.

[0084] Table 2 Example of extended backoff parameter values

[0085]

[0086] In some embodiments, terminal device 110 may determine a second value between zero and a first value included in the indicator, and determine the duration of a third timer based on the second value and the period of CG. For example, the backoff indicator is an integer N. Terminal device 110 may select a random integer value n based on a uniform distribution between 0 and the first value. The resulting duration is a fraction of CG. Period. Thus, for the next n CG transmission opportunities, SDT based on shared CG is not allowed on the corresponding CG resources.

[0087] In some embodiments, the backoff indicator may not be obtained by the terminal device 110. In these embodiments, the terminal device 110 may set the duration of the third timer to 0.

[0088] This can reduce competition among multiple terminal devices during the next CG timing.

[0089] It should be noted that Figures 2A to 2C The actions shown are not always necessary for implementing embodiments of the invention, but can be adjusted to more or fewer actions as needed.

[0090] Example implementation of a method

[0091] This disclosure provides a communication method implemented at a terminal device and a network device. The following will refer to... Figures 7 to 8 Describe these methods.

[0092] Figure 7 An example communication method 700 implemented at a terminal device according to some embodiments of the present disclosure is illustrated. For example, method 700 can be implemented in, for example, Figure 1 The terminal device 110 shown is executed. For the purposes of discussion, reference will be made below. Figure 1 Method 700 is described. It should be understood that method 700 may include additional boxes not shown and / or some boxes shown may be omitted, and the scope of this disclosure is not limited thereto. In this example, it is assumed that terminal device 110 decides to send uplink data in an inactive state.

[0093] At block 710, terminal device 110 determines CG from the configuration of BWP for uplink data transmission in an inactive state. In some embodiments, terminal device 110 may obtain this configuration from system information or from a dedicated message received from network device 120, and determine CG based on this configuration. In some embodiments, terminal device 110 may determine a candidate set for CG from the configuration, and determine CG from the candidate set.

[0094] At block 720, the terminal device 110 transmits uplink data to the network device 120 in the inactive state based on CG. In some embodiments, the terminal device 110 can also transmit, to the network device 120, a MAC CE including a short I-RNTI of the terminal device 110.

[0095] In this way, traffic load on the initial BWP can be mitigated.

[0096] In some embodiments, the terminal device 110 can determine, from system information received from the network device 120, whether to use a full I-RNTI of the terminal device 110. If it is determined to use the full I-RNTI, the terminal device 110 can also transmit, to the network device 120, a first MAC CE including the full I-RNTI. If it is determined not to use the full I-RNTI, the terminal device 110 can also transmit, to the network device 120, a second MAC CE including the short I-RNTI.

[0097] In this way, RRC-less can be supported for CG-based SDT.

[0098] In some embodiments, the terminal device 110 can start a first timer at transmission of the uplink data, the first timer being for monitoring a downlink control channel. In these embodiments, if a scheduling for retransmission of the uplink data is received, the terminal device 110 can restart the first timer.

[0099] In some embodiments, the terminal device 110 can receive, from the network device 120, an indication indicating whether the transmission is successful or failed at expiry of the first timer. If the indication indicates that the transmission is successful at expiry of the first timer, the terminal device 110 can determine that the transmission is successful at expiry of the first timer. If the indication indicates that the transmission is failed at expiry of the first timer, the terminal device 110 can determine that the transmission is failed at expiry of the first timer.

[0100] In some embodiments, the terminal device 110 can stop the first timer upon receiving a MAC PDU indicating that the uplink data is successfully transmitted.

[0101] In this way, downlink control channel monitoring after CG transmission can be performed.

[0102] In some embodiments, the terminal device 110 can start a second timer for contention resolution at transmission of the uplink data. In some embodiments, if it is determined that the second timer expires, the terminal device 110 can determine that the contention resolution is unsuccessful.

[0103] In some embodiments, if the MAC PDU is received from the network device 120, the terminal device 110 can determine whether the MAC PDU includes a first identifier associated with the contention resolution. If it is determined that the MAC PDU includes the first identifier, the terminal device 110 can determine whether the first identifier matches a second identifier of the terminal device in the transmission of the uplink data. If it is determined that the first identifier matches the second identifier, the terminal device 110 can determine that the contention resolution is successful, and determine that the transmission of the uplink data is successful.

[0104] In some embodiments, the terminal device 110 can stop the second timer upon receiving the MAC PDU. In some embodiments, in accordance with a determination that the transmission of the uplink data is successful, the terminal device 110 can determine a TA command from the MAC PDU and execute the TA command. In some embodiments, the terminal device 110 can also receive a C-RNTI for the terminal device 110 in the MAC PDU from the network device 120.

[0105] In some embodiments, if it is determined that the MAC PDU does not include the first identifier or the first identifier does not match the second identifier, the terminal device 110 can discard the MAC PDU, and determine that the contention resolution is not successful.

[0106] In some embodiments, if it is determined that the contention resolution is not successful, the terminal device 110 can determine that the transmission of the uplink data is not successful. In some alternative embodiments, if it is determined that the contention resolution is not successful, the terminal device 110 can retransmit the uplink data in the inactive state; and restart the second timer; and if it is determined that the number of transmissions is equal to a predetermined number, the terminal device 110 can determine that the transmission of the uplink data is not successful.

[0107] In this way, a contention resolution mechanism for CG-based SDT can be implemented.

[0108] In some embodiments, if it is determined that the contention resolution is not successful, the terminal device 110 can start a third timer, suspend the transmission of the uplink data on the CG until the third timer expires, and perform the transmission of the uplink data based on the CG in the inactive state after the third timer expires.

[0109] In some embodiments, the terminal device 110 can receive an indicator for a duration of the third timer from the network device 120, determine the duration of the third timer based on the indicator, and start the third timer with the duration. In some alternative embodiments, the terminal device 110 can receive an RRC message including the indicator from the network device 120, and obtain the indicator from the RRC message.

[0110] In some embodiments, terminal device 110 may determine a second value between zero and a first value included in the indicator, and determine the duration of a third timer based on the second value and a configured authorized period.

[0111] In some embodiments, terminal device 110 may receive a MAC PDU including an indicator from network device 120 and obtain the indicator from the MAC PDU. In some embodiments, terminal device 110 may determine a header including an LCID for the indicator from the MAC PDU and determine the indicator from the MAC CE corresponding to the header. In some alternative embodiments, terminal device 110 may determine the header from the MAC PDU and determine the indicator from the header, the header including bits indicating the presence of the indicator. In some alternative embodiments, terminal device 110 may determine the indicator from predetermined bytes of the MAC PDU.

[0112] This enables a backoff mechanism in case of contention and reduces contention among multiple terminal devices during the next CG timing.

[0113] Figure 8 An example method 800 for communication implemented at a network device according to some embodiments of the present disclosure is illustrated. For example, method 800 can be implemented in, for example, Figure 1 The network device shown is executed at location 120. For discussion purposes, reference will be made below. Figure 1 Method 800 is described. It should be understood that method 800 may include additional boxes not shown and / or some boxes shown may be omitted, and the scope of this disclosure is not limited thereto.

[0114] like Figure 8 As shown in block 810, network device 120 sends a configuration for a BWP (Background Reader) used for uplink data transmission from terminal device 110 in an inactive state. This configuration includes a CG (Current Access Control). In some embodiments, the configuration may include a candidate set for CGs. In some embodiments, network device 120 may send this configuration in system information.

[0115] In some embodiments, network device 120 may receive a MAC CE including the short I-RNTI of terminal device 110 from terminal device 110. In some embodiments, network device 120 may indicate to terminal device 110 in system information whether to use the full I-RNTI of terminal device 110. When network device 120 indicates to use the full I-RNTI, network device 120 may receive a first MAC CE including the full I-RNTI from terminal device 110. When network device 120 indicates not to use the full I-RNTI, network device 120 may receive a second MAC CE including the short I-RNTI from terminal device 110.

[0116] In some embodiments, the network device 120 can transmit, to the terminal device 110, an indication indicating whether the transmission of the uplink data is successful or failed upon expiration of the first timer. In these embodiments, the first timer is used for the monitoring of the downlink control channel. In some embodiments, the network device 120 can transmit, to the terminal device 110, a MAC PDU indicating that the uplink data is successfully transmitted. In some embodiments, the network device 120 can transmit, to the terminal device 110, a scheduling for retransmission of the uplink data.

[0117] In some embodiments, the network device 120 can transmit, to the terminal device 110, a MAC PDU including the first identity associated with the contention resolution. In some embodiments, the network device 120 can further transmit, to the terminal device 110, a TA command in the MAC PDU. That is, the MAC PDU can further include the TA command. In some embodiments, the network device 120 can further transmit, to the terminal device 110, a C-RNTI in the MAC PDU. That is, the MAC PDU can further include the C-RNTI. In some embodiments, one or more of the first identity, the TA command, and the C-RNTI can be transmitted in the same MAC CE. In some embodiments, the first identity, the TA command, and the C-RNTI can be respectively transmitted in separate MAC CEs.

[0118] In some embodiments, the network device 120 can transmit, to the terminal device 110, an indicator for a duration of a third timer. In these embodiments, the third timer is used for suspending the transmission of the uplink data on the CG. In some embodiments, the network device 120 can transmit the indicator in a RRC message. In some alternative embodiments, the network device 120 can transmit the indicator in a MAC PDU.

[0119] In some embodiments, the MAC PDU can include a header including the LCID and a MAC CE carrying the indicator. In some alternative embodiments, the MAC PDU can include a header including the indicator and a bit indicating the presence of the indicator. In some alternative embodiments, the indicator is included in a predetermined byte of the MAC PDU.

[0120] Figures 7 to 8 Implementations of the methods described in this specification can comprise terminal devices 110 and network devices 120 that operate according to the methods, apparatuses, and / or systems described in this specification. As described above, the terminal devices 110 and network devices 120 can each comprise one or more of the components shown with reference to any one of Figs. 1-3. Figures 2A to 2C The processes described in this specification can be implemented using the terminal devices 110 and network devices 120 described above. Also, the processes described in this specification can be implemented using the terminal devices 110 and network devices 120 described above.

[0121] Example implementation of a device

[0122] Figure 9is a simplified block diagram of a device 900 suitable for implementing embodiments of the present disclosure. The device 900 can be considered as another example implementation of the terminal device 110 or the network device 120 as shown in Figure 1 Thus, the device 900 can be implemented at or as at least a part of the terminal device 110 or the network device 120.

[0123] As shown, the device 900 includes a processor 910, a memory 920 coupled to the processor 910, a suitable transmitter (TX) and receiver (RX) 940 coupled to the processor 910, and a communication interface coupled to the TX / RX 940. The memory 910 stores at least a portion of a program 930. The TX / RX 940 is for bidirectional communication. The TX / RX 940 has at least one antenna to facilitate communication, although in practice the access node mentioned in this application can have several antennas. The communication interface can represent any interface needed for communication with other network elements, such as an X2 / Xn interface for bidirectional communication between eNBs / gNBs, an S1 / NG interface for communication between a mobility management entity (MME) / access and mobility management function (AMF) / SGW / UPF and eNBs / gNBs, an Un interface for communication between an eNB / gNB and a relay node (RN), or a Uu interface for communication between an eNB / gNB and a terminal device.

[0124] The program 930 is assumed to include program instructions that, when executed by the associated processor 910, enable the device 900 to operate in accordance with the embodiments of this disclosure, as discussed herein with reference to Figures 1 to 8 The embodiments herein can be implemented through computer software executable by the processor 910 of the device 900, or by hardware, or by a combination of software and hardware. The processor 910 can be configured to implement various embodiments of the present application. Further, the combination of the processor 910 and the memory 920 can form a processing means suitable to implement various embodiments of the present disclosure.

[0125] Memory 920 can be of any type suitable to the local technical network, and can be implemented using any suitable data storage technology, such as nonvolatile memory, semiconductor-based memory devices, magnetic memory devices and systems, optical memory devices and systems, fixed memory and removable memory, as non-limiting examples. While only one memory 920 is shown in device 900, there can be several physically distinct memory modules in device 900. As a non-limiting example, processor 910 can be of any type suitable to the local technical network, and can include one or more of general purpose computers, special purpose computers, microprocessors, digital signal processors (DSPs) and processors based on multi-core processor architectures, as non-limiting examples. Device 900 can have multiple processors such as in a special purpose integrated circuit chip that is time-synchronized to a clock that synchronizes the master processor.

[0126] In general, the various embodiments of the disclosure can be implemented in hardware or special-purpose circuits, software, logic or any combination thereof. Some aspects can be implemented in hardware, while other aspects can be implemented in firmware or software which can be executed by a controller, microprocessor or other computing device, although the disclosure is not limited thereto. While various aspects of embodiments of this disclosure can be illustrated and described as block diagrams, flow charts, or using some other pictorial representation, it is well understood that these blocks, apparatus, systems, techniques or methods described herein can be implemented in, as non-limiting examples, hardware, software, firmware, special purpose circuits or logic, general purpose hardware or controller or other computing devices, or some combination thereof.

[0127] The disclosure also provides at least one computer program product which is tangibly stored on a non-transitory computer-readable storage medium. The computer program product includes instructions that are executed by devices on target real or virtual processors to perform processes or methods as described above with reference to Figures 2A to 2C and Figures 7 to 8 The processes or methods described above, can generally be implemented using computer executable instructions, such as program modules, being executed by devices on target real or virtual processors. Generally, program modules include routines, programs, libraries, objects, classes, components, data structures, or the like that perform particular tasks or implement particular abstract data types. The functionality of the program modules can be combined or split between program modules as desired in various embodiments. The machine executable instructions can be executed within a local or distributed device. In a distributed device, the program modules can be located in both local and remote memory storage devices.

[0128] Program code for carrying out methods of the present disclosure can be written in any combination of one or more programming languages. The program code can be provided to a processor or controller of a general purpose computer, special purpose computer, or other programmable data processing apparatus to produce a machine, such that the program code, when executed by the processor or controller, causes the machine to implement the functions / acts specified in the flowcharts and / or block diagrams. The program code can be stored in a machine-readable medium temporarily, permanently, in whole or in part, on a machine such as a computer or other programmable data processing apparatus. Program code stored in a machine-readable medium can cause a machine, such as a computer or other programmable data processing apparatus, to implement processes when it reads out a

[0129] The program code can be embodied on a machine readable medium, which can be any tangible media that can contain, or store instructions which can be used by an instruction execution system, apparatus, or device to produce machine.

[0130] Furthermore, although operations have been described as being in a specific order, this is not meant to be limiting, but is for clarity. Some operations can be performed in a different order or simultaneously. Some operations can be performed in parallel. Also, some operations can be omitted. In some instances, additional operations can be added. Operations can be combined. Furthermore, although the features of the present disclosure are described in the context of particular implementations, it is not intended that the present disclosure be limited to these implementations. On the contrary, it is intended to cover all alternatives, modifications, and equivalents as can be included within the spirit and scope of the present disclosure as defined by the appended claims. Some features of the present disclosure are described in the context of separate embodiments. However, these features can also be implemented in a single embodiment. Conversely, various features of the present disclosure, which are described in the context of a single embodiment, can also be implemented in multiple embodiments. Similarly, some features of the present disclosure can be written in different combinations or modes than described and practiced. Also, every feature that is added or implemented in the course of making or using the present disclosure can also be described as being part of the present disclosure.

[0131] While the present disclosure has been described with structural features and / or methodological acts in a particular order, it should be understood that the present disclosure defined in the appended claims can be practiced in other orders than those described, or practices concurrently. Furthermore, it should be appreciated that structural features and / or methodological acts can be combined in ways not specifically mentioned in the foregoing description.

Claims

1. A method for communication executed by a terminal device, the method comprising: When inactive, perform small data transfer SDT for configuration-authorized CG; When the transmission for the CG-based SDT is executed, the first timer and the second timer are started. The first timer is a retransmission timer, and the second timer is used to detect SDT failures; If the first timer is not running, perform a retransmission for the CG-based SDT; as well as While the second timer is running, the control channel is monitored.

2. The method according to claim 1, further comprising: When the retransmission for the CG-based SDT is executed, the first timer is restarted.

3. The method according to claim 1, wherein the control channel is a physical downlink control channel (PDCCH) addressed to the configuration scheduling radio network temporary identifier (CS-RNTI) and the cell radio network temporary identifier (C-RNTI).

4. The method according to claim 3, further comprising: Stop configuring the authorization timer when the PDCCH addressed to the C-RNTI is received.

5. The method according to claim 1, further comprising: Receive the bandwidth portion BWP configuration for the CG-based SDT, wherein the BWP configuration includes information indicating the CG configuration set; as well as Based on the CG configuration set, the transmission for the CG-based SDT and the retransmission for the CG-based SDT are performed.

6. A method for communication performed by a network device, the method comprising: When the terminal device is inactive, a transmission for a Small Data Transmission Dependency Based on a Configuration Authorization Code (CG) is received from the terminal device, wherein when the transmission for the CG-based CG SDT is executed, a first timer and a second timer are started. The first timer is a retransmission timer, and the second timer is used to detect SDT failures; If the first timer is not running, a retransmission for the CG-based SDT is received from the terminal device; as well as A control channel is sent to the terminal device, wherein the control channel is monitored while the second timer is running.

7. The method of claim 6, wherein the first timer is restarted when the retransmission for the CG-based SDT is performed.

8. The method of claim 6, wherein the control channel is a physical downlink control channel (PDCCH) addressed to a configuration scheduling radio network temporary identifier (CS-RNTI) and a cell radio network temporary identifier (C-RNTI).

9. The method of claim 8, wherein the configuration authorization timer is stopped when the PDCCH addressed to the C-RNTI is received by the terminal device.

10. The method of claim 6, further comprising: Send the bandwidth portion BWP configuration for the CG-based SDT, wherein the BWP configuration includes information indicating the CG configuration set.

11. A terminal device, comprising: At least one computer-readable storage device is configured to store program instructions; as well as At least one processor, when executing the program instructions, performs the following operations: When inactive, perform small data transfer SDT for configuration-authorized CG; When the transmission for the CG-based SDT is executed, the first timer and the second timer are started. The first timer is a retransmission timer, and the second timer is used to detect SDT failures; If the first timer is not running, perform a retransmission for the CG-based SDT; as well as While the second timer is running, the control channel is monitored.

12. The terminal device of claim 11, wherein the at least one processor further performs the operation of restarting the first timer when the retransmission for the CG-based SDT is performed.

13. The terminal device of claim 11, wherein the control channel is a physical downlink control channel (PDCCH) addressed to a configuration scheduling radio network temporary identifier (CS-RNTI) and a cell radio network temporary identifier (C-RNTI).

14. The terminal device of claim 13, wherein the at least one processor further performs the following operations: The configuration authorization timer is stopped when the PDCCH addressed to the C-RNTI is received.

15. The terminal device of claim 11, wherein the at least one processor further performs the following operations: Receive the bandwidth portion BWP configuration for the CG-based SDT, wherein the BWP configuration includes information indicating the CG configuration set; and Based on the CG configuration set, the transmission for the CG-based SDT and the retransmission for the CG-based SDT are performed.

Images