Resource configuration for NB-IOT

Abstract

Embodiments of the present disclosure relate to resource configuration for narrowband Internet of Things (NB‑IoT). A method for resource configuration for NB‑IoT includes determining at a network device whether a preconfigured uplink resource (PUR) for transmission from a terminal device to the network device is to be adjusted; in response to determining that the PUR is to be adjusted, determining a set of resources to be allocated for another transmission from the terminal device to the network device based on a transmission block size (TBS) associated with the other transmission from the terminal device to the network device; generating reconfiguration information for the PUR based on the set of resources; and transmitting the reconfiguration information to the terminal device. In this way, resource configuration can be determined and adjusted more efficiently and flexibly than in traditional ways.

Description

Technical Field

[0001] Embodiments of the present disclosure generally relate to the field of telecommunications, and more particularly to resource configuration for narrowband Internet of Things (NB-IoT). Background Art

[0002] Some research improvements are proposed to improve uplink (UL) transmission efficiency and / or user equipment (UE) power consumption, for example, specifying support for transmission in pre-configured resources in idle and / or connected mode based on single carrier frequency division multiple access (SC-FDMA) waveform for UEs with effective timing advance.

[0003] Currently, it has been considered to remove the need for Message 1 (MESSAGE 1) and Message 2 (MESSAGE 2) in the access process by using PUR (Preconfigured Uplink Resources). Specifically, a dedicated PUR (D-PUR) is defined as a narrow physical uplink shared channel (NPUSCH) resource that can be used by a single UE and is contention-free. It is decided that an evolved Node B (eNB) can configure a dedicated PUR via radio resource control (RRC) dedicated signaling, and periodic D-PUR with a duration can be supported. Summary of the invention

[0004] In general, example embodiments of the present disclosure provide a solution for resource configuration of NB-IoT.

[0005] In a first aspect, a method for resource configuration for NB-IoT is provided. The method includes determining at a network device whether a preconfigured uplink resource (PUR) for transmission from a terminal device to the network device is to be adjusted; in response to determining that the PUR is to be adjusted, determining a set of resources to be allocated for another transmission from the terminal device to the network device based on a transport block size (TBS) associated with the other transmission; generating reconfiguration information of the PUR based on the set of resources; and transmitting the reconfiguration information to the terminal device.

[0006] In a second aspect, a resource configuration method for NB-IoT is provided. The method includes receiving, at a terminal device, reconfiguration information of a preconfigured uplink resource (PUR) from a network device, the PUR being used for transmission from the terminal device to the network device, the reconfiguration information being generated by the network device based on a set of resources to be allocated for additional transmission from the terminal device to the network device, the set of resources being determined by the network device in response to determining that the PUR is to be adjusted based on a transport block size (TBS) associated with the additional transmission; and performing additional transmission based on the reconfiguration information.

[0007] In a third aspect, a network device for NB-IoT resource configuration is provided. The device includes at least one processor; and at least one memory containing computer program code; the at least one memory and the computer program code are configured to, together with the at least one processor, cause the device to at least: determine at the network device whether a preconfigured uplink resource (PUR) network device for transmission from a terminal device to the network device is to be adjusted; in response to determining that the PUR is to be adjusted, determine a set of resources to be allocated for the additional transmission based on a transmission block size (TBS) associated with the additional transmission from the terminal device to the network device; generate reconfiguration information of the PUR based on a set of resources; and transmit the reconfiguration information to the terminal device.

[0008] In a fourth aspect, a terminal device for NB-IoT resource configuration is provided. The device includes at least one processor; and at least one memory containing computer program code; at least one memory and computer program code are configured to, together with at least one processor, cause the device to at least: receive reconfiguration information of a preconfigured uplink resource (PUR) from a network device at the terminal device, the PUR being used for transmission from the terminal device to the network device, the reconfiguration information being generated by the network device based on a set of resources to be allocated for additional transmission from the terminal device to the network device, the set of resources being determined by the network device in response to determining that the PUR is to be adjusted based on a transport block size (TBS) associated with the additional transmission; and performing additional transmission based on the reconfiguration information.

[0009] In a fifth aspect, there is provided an apparatus comprising means for performing the steps of the method according to the first aspect. The apparatus comprises: means for determining at a network device whether a preconfigured uplink resource (PUR) for transmission from a terminal device to the network device is to be adjusted; means for determining, in response to determining that the PUR is to be adjusted, a set of resources to be allocated for another transmission from the terminal device to the network device based on a transport block size (TBS) associated with the other transmission; means for generating reconfiguration information of the PUR based on the set of resources; and means for transmitting the reconfiguration information to the terminal device.

[0010] In a sixth aspect, a device is provided, comprising a component for performing the steps of the method according to the second aspect. The device comprises: a component for receiving, at a terminal device, reconfiguration information of a preconfigured uplink resource (PUR) from a network device, the PUR being used for transmission from the terminal device to the network device, the reconfiguration information being generated by the network device based on a set of resources to be allocated for additional transmission from the terminal device to the network device, the set of resources being determined by the network device in response to determining that the PUR is to be adjusted based on a transport block size (TBS) associated with the additional transmission; and a component for performing additional transmission based on the reconfiguration information.

[0011] In a seventh aspect, there is provided a computer readable medium having stored thereon a computer program which, when executed by at least one processor of a device, causes the device to perform the method according to the first aspect.

[0012] In an eighth aspect, there is provided a computer readable medium having stored thereon a computer program which, when executed by at least one processor of a device, causes the device to perform the method according to the second aspect.

[0013] It should be understood that the invention summary is not intended to identify the key or essential features of the 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 understood through the following description. BRIEF DESCRIPTION OF THE DRAWINGS

[0014] Some example embodiments will now be described with reference to the accompanying drawings, in which:

[0015] Figure 1 An example communication network 100 is shown in which example embodiments of the present disclosure may be implemented;

[0016] Figure 2 A diagram showing an example process 200 for resource configuration for NB-IoT according to some example embodiments of the present disclosure;

[0017] Figure 3 A flowchart illustrating an example method 300 for resource configuration for NB-IoT according to some embodiments of the present disclosure is shown;

[0018] Figure 4 A flow chart illustrating an example method 400 for resource configuration for NB-IoT according to some embodiments of the present disclosure;

[0019] Figure 5 is a simplified block diagram of a device suitable for implementing embodiments of the present disclosure; and

[0020] Figure 6A diagram of an example computer-readable medium is illustrated in accordance with some embodiments of the present disclosure.

[0021] Throughout the drawings, the same or similar reference numerals refer to the same or similar elements. DETAILED DESCRIPTION

[0022] The principles of the present disclosure will now be described with reference to some example embodiments. It should be understood that these embodiments are described only for illustrative purposes and to help those skilled in the art understand and implement the present disclosure without suggesting any limitation to the scope of the present disclosure. In addition to the methods described below, the disclosure described herein can be implemented in various ways.

[0023] In the following description and claims, unless defined otherwise, 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.

[0024] As used herein, the term "communication network" refers to a network that complies with any suitable communication standard or protocol and adopts any suitable communication technology, suitable communication standards or protocols such as Long Term Evolution (LTE), Advanced LTE (LTE-A) and 5G NR, suitable communication technologies include, for example, multiple-input multiple-output (MIMO), OFDM, time division multiplexing (TDM), frequency division multiplexing (FDM), code division multiplexing (CDM), Bluetooth, ZigBee, machine type communication (MTC), eMBB, mMTC and uRLLC technology. For the purpose of discussion, in some embodiments, LTE network, LTE-A network, 5GNR network or any combination thereof are taken as examples of communication networks.

[0025] As used herein, the term "network device" refers to any suitable device on the network side of a communication network. The network device may include any suitable device in the access network of the communication network, such as a base station (BS), a relay, an access point (AP), a node B (NodeB or NB), an evolved NodeB (eNodeB or eNB), a gigabit node B (gNB), a remote radio module (RRU), a radio head (RH), a remote radio head (RRH), a low-power node (such as a femto, a micro), etc. For the purpose of discussion, in some embodiments, an eNB is used as an example of a network device.

[0026] The network equipment may also include any suitable equipment in the core network, for example, including multi-standard radio (MSR) radio equipment such as MSR BS, network controllers (BSC) such as radio network controllers (RNC) or base station controllers, multi-cell / multicast coordination entities (MCEs), mobile switching centers (MSCs) and MMEs, operations and management (O&M) nodes, operations support system (OSS) nodes, self-organizing network (SON) nodes, positioning nodes such as enhanced serving mobile positioning center (E-SMLC) and / or mobile data terminals (MDTs).

[0027] As used herein, the term "terminal device" refers to a device that can be used, configured for, arranged for and / or operable to communicate with a network device or another terminal device in a communication network. The communication may involve the use of electromagnetic signals, radio waves, infrared signals and / or other types of signals suitable for conveying information through the air to transmit and / or receive wireless signals. In some embodiments, the terminal device can be configured to transmit and / or receive information without direct human interaction. For example, when triggered by an internal or external event, or in response to a request from the network side, the terminal device can transmit information to the network device according to a predetermined schedule.

[0028] Examples of terminal devices include, but are not limited to, user equipment (UE) such as a smart phone, a wireless-enabled tablet, a laptop embedded device (LEE), a laptop mounted device (LME), and / or wireless customer premises equipment (CPE). For the purpose of discussion, some embodiments will be described below with reference to UE as an example of a terminal device, and the terms "terminal device" and "user equipment" (UE) may be used interchangeably in the context of the present disclosure.

[0029] As used herein, the term "cell" refers to an area covered by radio signals transmitted by network equipment. Terminal equipment within the cell can be served by the network equipment and access the communication network via the network equipment.

[0030] As used herein, the term "circuitry" may refer to one or more or all of the following:

[0031] (a) pure hardware circuit implementation (such as implementation in analog and / or digital circuitry only) and

[0032] (b) a combination of hardware circuitry and software, such as (where applicable): (i) a combination of (one or more) analog and / or digital hardware circuitry and software / firmware, and (ii) any portion of a hardware processor(s) with software (including (one or more) digital signal processors), software and memory(s) that work together to enable a device such as a mobile phone or server to perform various functions) and

[0033] (c) Hardware circuit(s) and / or processor(s) that require software (e.g., firmware) to operate, such as microprocessor(s) or portion(s) of microprocessor(s), but the software may not be present when it is not required for operation.

[0034] This definition of circuitry applies to all uses of the term in this application, including all uses in any claims. As a further example, as used in this application, the term circuitry also covers an implementation of only a hardware circuit or processor (or multiple processors) or a portion of a hardware circuit or processor and its (or their) accompanying software and / or firmware. By way of example and where applicable to a particular claim element, the term circuitry also covers a baseband integrated circuit or processor integrated circuit for a mobile device, or a similar integrated circuit in a server, cellular network device, or other computing or network device.

[0035] 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 "including" and its variations should be interpreted as open terms meaning "including but not limited to". The term "based on" should be interpreted as "based at least in part on". The terms "one embodiment" and "an embodiment" should be interpreted as "at least one embodiment". The term "another embodiment" should be interpreted as "at least one other embodiment". Other definitions, whether explicit or implicit, may be included below.

[0036] Figure 1 The communication network 100 in which the embodiments of the present disclosure can be implemented is illustrated. The communication network 100 can comply with any suitable protocol or standard that already exists or will be developed in the future. In some embodiments, the communication network 100 can be an LTE (or LTE-A) network, an NR network, or a combination thereof.

[0037] The communication network 100 includes a network device 110. The network device 110 serves a terminal device 120 in a cell 111. It should be understood that the number of network devices and terminal devices is shown only for illustrative purposes, and no limitation is suggested. The communication network 100 may include any suitable number of network devices and terminal devices. The communication between the network device 110 and the terminal device 120 may utilize any suitable technology that already exists or will be developed in the future.

[0038] Currently, it has been considered to remove the need for Message 1 and Message 2 in the access procedure by using PUR (Preconfigured Uplink Resources). Dedicated PUR (D-PUR) is defined as a narrow physical uplink shared channel (NPUSCH) resource and can be allocated to a specific UE to avoid contention. It has been decided that the eNB can configure a dedicated PUR via RRC signaling, and periodic D-PUR with a duration can be supported.

[0039] Compared with scheduling-based resource allocation, D-PUR is a reserved method without accurate buffer size exchange. FFS is a method for eNB to obtain information to help configure dedicated pre-configured uplink resources to UE. Improper resource allocation method will lead to resource waste.

[0040] In addition, when the eNB allocates a D-PUR to the UE, the D-PUR information can be stored in both the eNB and the UE. How to create and maintain the information has not been discussed yet.

[0041] One approach proposed is that the PUR may reuse the same maximum transport block size (TBS) and the same UL TBS table specified for Early Data Transmission (EDT) in the Random Access (RA) procedure.

[0042] Another method proposed is to limit the PUR TBS to the maximum TBS supported by the UE category. EDT does not have an accurate TBS allocation step and performs eNB-dependent blind decoding. EDT is a single transmission, and if the EDT method is reused for D-PUR, it is not efficient, especially for periodic services.

[0043] Another approach proposed is to add the data size to the subscription-based UE differentiation information from the MME to the eNB to help it determine the TBS. Obtaining the data size as part of the subscription data is inflexible and only works when the MCS is fixed for the UE and known by the eNB.

[0044] In addition, since the UE applying D-PUR is in idle mode, the D-PUR information may not be stored in the eNB as UE context. There is currently no solution for D-PUR information storage.

[0045] Therefore, an embodiment of the present disclosure proposes a method for resource configuration of NB-IoT. The resource configuration process may include an initial phase (ie, a configuration phase) and an adjustment phase (ie, a reconfiguration phase). Both the eNB and the UE may trigger the resource configuration process.

[0046] The following will refer to Figure 2 Describe the principles and implementation of the present disclosure in detail. Figure 2 A process 200 is shown according to an example embodiment of the present disclosure. For the purpose of discussion, reference will be made to Figure 1 To describe process 200. Process 200 may involve resource configuration of NB-IoT.

[0047] like Figure 2 As shown in , the network device 110 can determine which cell can support PUR. In some embodiments, a cell with EDT capability can be considered as a candidate cell for PUR, for example Figure 1 The network device may then generate a PUR indication in the EDT TBS parameters to indicate whether these EDT TBS parameters can be used by the terminal device 120 served by the cell 111.

[0048] The network device 110 may also transmit a D-PUR indication in a system information block (SIB) 205 to inform the terminal device 120 that the cell 111 may support D-PUR to reuse the TBS information of the EDT.

[0049] The network device 110 may then determine the configuration of the PUR. In some embodiments, the configuration of the PUR may be determined by the network device 110 based on the coverage extension level (CEL) of the terminal device 120 detected by the network device 110. As another option, the terminal device 120 may request the configuration of the PUR based on the amount of data to be transmitted to the network device 110 and the coverage extension level (CEL) of the terminal device 120. With reference to actions 210 to 230, two situations of the initial stage (i.e., the configuration stage) may be explained in detail.

[0050] If the initial phase is triggered by the terminal device 120, the terminal device 120 may determine 210 a desired TBS based on the coverage extension level (CEL) and the amount of data from a higher layer. The desired TBS used herein may indicate a size required for transmitting data from the terminal device 120.

[0051] In this case, terminal device 120 may determine different desired TBS and periodicity details based on multiple D-PUR services from network device 110. In addition to D-PUR service flows, terminal device 120 may also indicate services requiring PUR whose traffic patterns and possible TBS sizes are uncertain.

[0052] The terminal device 120 may transmit 215 a request for configuration of a PUR to the network device 110. The request may include a desired TBS and may be transmitted via RRC signaling. If the network device 110 receives the request, the network device 120 may determine the configuration of the PUR based on the initial TBS and the channel state (e.g., CEL) between the terminal device and the network device. This configuration of the PUR may be considered a dedicated PUR (D-PUR), which means that the configuration of the PUR can only be used for a specific terminal device, such as the terminal device 120.

[0053] In some embodiments, the identifier of the service is encapsulated in a NAS message in the RRC signaling for the D-PUR request.

[0054] In some embodiments, the configuration includes at least a TBS configured for uplink transmission, a set of resources to be allocated for uplink transmission, and a PUR Radio Network Temporary Identifier (RNTI). The PUR RNTI may be assigned to the terminal device 120 to instruct the terminal device to monitor the NPDCCH scrambled by the PUR RNTI to determine whether it needs to perform a mode transition to receive a reconfiguration.

[0055] The network device 110 may transmit 220 the configuration of the PUR to the terminal device 120 and create 225 a D-PUR context accordingly. Accordingly, the terminal device 120 may also create 230 a D-PUR context after receiving the configuration of the PUR. In some embodiments, the context may include an identification of the terminal device, an identification of the service, allocated resources, a TBS, and a number of repetitions for transmission.

[0056] Alternatively, if the initial phase is triggered by the network device 110, the network device 110 may assign resources to each service flow with a resource allocation configuration and a TBS configured for a service with a fixed traffic pattern, and determine the configuration of the PUR based on the allocated resources. Such allocated resources may be considered a shared PUR.

[0057] In some embodiments, for services requiring uplink transmissions with timing uncertainty, network device 110 may assign a maximum TBS to resources and a smaller TBS supported in these shared resources. Network device 110 may also use EDTTBS as the configured TBS to be used for the shared PUR.

[0058] Similarly, for this case, the network device 110 may transmit 220 the configuration of the PUR to the terminal device 120 and create 225 a D-PUR context accordingly. Accordingly, the terminal device 120 may also create 230 a D-PUR context after receiving the configuration of the PUR. In some embodiments, the context may include an identifier of the terminal device, an identifier of the service, allocated resources, a TBS, and a number of repetitions for transmission.

[0059] In this way, both the terminal device 120 and the network device 110 can trigger the configured process. In addition, the D-PUR information can be stored in both the terminal device 120 and the network device 110 according to the D-PUR context.

[0060] In some embodiments, if the amount of service data or channel conditions need to change, the terminal device 120 may intend to adjust the configuration of the PUR. Alternatively, if the network device 110 detects that the terminal device 120 requests more resources than it actually needs or an incorrect TBS, the network device 110 can also trigger a PUR reconfiguration (i.e., an adjustment phase).

[0061] For the case where network device 110 triggers a PUR reconfiguration, terminal device 120 may perform 235 an uplink data transmission. Based on the data transmission, network device 110 may determine 240 whether the configuration of the PUR is to be adjusted.

[0062] In some embodiments, the network device 110 may determine the TBS for data transmission and compare the TBS with the configured TBS indicated in the configuration of the PUR. If the TBS is less than the configured TBS, it means that the terminal device 120 may not be able to effectively use the configured TBS. That is, the configuration of the PUR needs to be adjusted and the network device 110 may reconfigure the PUR.

[0063] The network device 110 may determine a set of resources for the additional transmission.For example, the network device 110 may determine a set of resources for the additional transmission based on the TBS, the coverage extension level (CEL), and the number of repetitions for the additional transmission.

[0064] The network device 110 may then transmit 245 an indication to the terminal device 120 to transition to connected mode in an initial phase via a narrow physical downlink control channel (NPDCCH) scrambled with a PUR RNTI assigned to the terminal device 120. The assigned PUR RNTI may enable the terminal device 120 to monitor the NPDCCH after performing 235 an uplink data transmission.

[0065] If the terminal device 120 receives an indication for a mode transition in the NPDCCH, the terminal device 120 may re-establish an RRC connection with the network device to receive a reconfiguration. The terminal device 120 may then transmit 255 a request for reconfiguration information for the PUR to the network device 110 via the re-established RRC connection. The network device 110 may generate reconfiguration information for the PUR based on a set of resources to be allocated for further transmissions, and transmit 260 the reconfiguration information to the terminal device 120. For example, the reconfiguration information may indicate a set of resources, a TBS, and a number of repetitions for subsequent transmissions. The network device 110 may then update 265 the D-PUR context.

[0066] The terminal device may determine 270 a new TBS based on the reconfiguration information and also update 275 the D-PUR context.

[0067] Alternatively, if the service data volume or channel conditions need to change, the terminal device 120 may trigger a PUR reconfiguration.The terminal device 120 may determine 250 a desired TBS for the further transmission.

[0068] The terminal device 120 may then transmit 255 a request for reconfiguration information of the PUR to the network device 110 via RRC signaling. The request may indicate a desired TBS. The network device 110 may obtain the desired TBS from the request and determine a set of resources based on the desired TBS. The network device 110 may generate the reconfiguration information of the PUR based on a set of resources to be allocated for subsequent transmissions, the desired TBS, and the number of repetitions for subsequent transmissions. The network device 110 may then transmit 260 the reconfiguration information to the terminal device 120. The network device 110 may then update 265 the D-PUR context. The terminal device 120 may also update 275 the D-PUR context based on the received reconfiguration information.

[0069] In this manner, both the terminal device 120 and the network device 110 can initiate the reconfiguration process, so that the PUR and TBS of each service can be configured more efficiently and flexibly compared to EDT.

[0070] Alternatively, the network device 110 may also modify the TBS or resources used for the shared PUR. To this end, the network device 110 may initiate paging to the terminal devices 120 mapped to these resources to initiate a network-triggered reconfiguration.

[0071] For more details of example embodiments according to the present disclosure, please refer to Figure 3-Figure 4 Give a description.

[0072] Figure 31 is a flow chart showing an example method 300 for a random access procedure according to some example embodiments of the present disclosure. The method 300 may be implemented in Figure 2 For discussion purposes, reference will be made to the network device 110 shown in FIG. Figure 2 Method 300 is described.

[0073] At 310, the network device 110 determines whether to adjust a preconfigured uplink resource (PUR) for transmissions from the terminal device to the network device.

[0074] In some example embodiments, network device 110 may determine the TBS based on a transmission received from a terminal device and may determine whether the TBS is less than a configured TBS that is predetermined by the network device for the transmission. If network device 110 determines that the TBS is less than the configured TBS, network device 110 may determine that the PUR is to be adjusted.

[0075] In some example embodiments, if network device 110 receives a request for reconfiguration information of a PUR from a terminal device, network device 110 may determine that the PUR is to be adjusted.

[0076] At 320, if network device 110 determines that the PUR is to be adjusted, network device 110 determines a set of resources to be allocated for the additional transmission from the terminal device to the network device based on a transport block size (TBS) associated with the additional transmission.

[0077] In some example embodiments, network device 110 may determine a TBS and a coverage extension level (CEL), and determine a repetition number for additional transmissions based on the TBS and the CEL. Network device 110 may also determine a set of resources based on the TBS and the repetition number.

[0078] In some example embodiments, the network device 110 may transmit to the terminal device an indication that the terminal device is to transition from idle mode to connected mode via a narrow physical downlink control channel (NPDCCH) scrambled with a PUR radio network temporary identifier (RNTI) allocated to the terminal device.

[0079] In some example embodiments, network device 110 may obtain a desired TBS from a request for reconfiguration information from a terminal device, and determine a set of resources based on the desired TBS.

[0080] At 330 , the network device 110 generates reconfiguration information for the PUR based on a set of resources.

[0081] At 340 , the network device 110 transmits the reconfiguration information to the terminal device.

[0082] In some example embodiments, if network device 110 receives a request for reconfiguration information of a PUR from a terminal device, network device 110 may generate reconfiguration information indicating a set of resources, a TBS, and a number of repetitions for additional transmissions, and transmit the reconfiguration information to the terminal device.

[0083] In some example embodiments, if network device 110 receives a request for reconfiguration information of a PUR from a terminal device, network device 110 may generate reconfiguration information indicating a set of resources, a TBS, and a number of repetitions for additional transmissions, and transmit the reconfiguration information to the terminal device. A set of resources may be determined based on the desired TBS indicated by the request for reconfiguration information of the PUR.

[0084] Furthermore, in some example embodiments, network device 110 may determine a configuration of a PUR for transmission and transmit the configuration of the PUR to the terminal device.

[0085] In some example embodiments, if network device 110 receives a request for configuration from a terminal device, network device 110 may obtain an initial TBS for transmission from the request, and determine a configuration of the PUR based on the initial TBS and a coverage extension level (CEL), the initial TBS being determined by the terminal device, the configuration including at least the configured TBS for transmission, a set of resources to be allocated for transmission, and a PUR radio network temporary identifier (RNTI) allocated to the terminal device.

[0086] In some example embodiments, network device 110 may determine a configured TBS for a transmission and a set of resources to be allocated for the transmission, and determine a configuration of the PUR based on the configured TBS.

[0087] In some example embodiments, network device 110 may obtain a reference TBS from an early data transmission (EDT) and determine a configured TBS based on the reference TBS.

[0088] Figure 4 4 is a flowchart showing an example method 400 for a random access procedure according to some example embodiments of the present disclosure. The method 300 may be implemented in Figure 2 For discussion purposes, reference will be made to the terminal device 120. Figure 2 Method 400 is described.

[0089] At 410, the terminal device 120 receives reconfiguration information of a preconfigured uplink resource (PUR) from a network device, the PUR being used for transmission from the terminal device to the network device, the reconfiguration information being generated by the network device based on a set of resources to be allocated for additional transmission from the terminal device to the network device, the set of resources being determined by the network device based on a transport block size (TBS) associated with the additional transmission in response to determining that the PUR is to be adjusted.

[0090] At 420, the terminal device 120 performs additional transmissions based on the reconfiguration information.

[0091] In some example embodiments, the terminal device 120 may receive an indication from the network device indicating that the terminal device is to transition from idle mode to connected mode via a narrow physical downlink control channel scrambled with a PUR radio network temporary identifier (RNTI) allocated to the terminal device. The terminal device 120 may transmit a request for reconfiguration information of the PUR to the network device based on the high-layer signaling indicating the reestablishment.

[0092] In some example embodiments, if the data volume or coverage extension level (CEL) of the further transmission is to be changed, the terminal device 120 may determine a desired TBS for the further transmission and transmit a request for reconfiguration information PUR to the network device, the request indicating the desired TBS.

[0093] In some example embodiments, if terminal device 120 receives a system information block (SIB) from a network device indicating that a PUR is available in a cell served by the network device, terminal device 120 may determine an initial TBS for transmission based on an amount of data for transmission and a coverage extension level (CEL). Terminal device 120 may transmit a request for configuration of a PUR to the network device, the request indicating the initial TBS and the CEL, and receive a configuration of the PUR from the network device, the configuration of the PUR being determined by the network device based on the initial TBS and the CEL.

[0094] In some example embodiments, the terminal device 120 may receive a configuration of a PUR from a network device, the configuration of the PUR being determined by the network device based on the transmitted configured TBS.

[0095] In some example embodiments, an apparatus capable of performing method 300 (e.g., network device 110) may include a component for performing each step of method 300. The component may be implemented in any suitable form. For example, the component may be implemented in a circuit or a software module.

[0096] In some example embodiments, the apparatus includes: a component for determining, at a network device, whether a preconfigured uplink resource (PUR) for transmission from a terminal device to the network device is to be adjusted; a component for determining, in response to determining that the PUR is to be adjusted, a set of resources to be allocated for an additional transmission from the terminal device to the network device based on a transmission block size (TBS) associated with the additional transmission; a component for generating reconfiguration information for the PUR based on the set of resources; and a component for transmitting the reconfiguration information to the terminal device.

[0097] In some example embodiments, the components for determining whether the PUR is to be adjusted include components for determining the TBS based on a transmission received from a terminal device; components for determining whether the TBS is less than a configured TBS, which is predetermined by a network device for the transmission; and components for determining that the PUR is to be adjusted in response to determining that the TBS is less than the configured TBS.

[0098] In some example embodiments, the means for determining whether the PUR is to be adjusted comprises means for determining that the PUR is to be adjusted in response to receiving a request for reconfiguration information of the PUR from the terminal device.

[0099] In some example embodiments, means for determining a set of resources includes means for determining a TBS and a coverage extension level (CEL); means for determining a number of repetitions for additional transmissions based on the TBS and the CEL; and means for determining a set of resources based on the TBS and the number of repetitions.

[0100] In some example embodiments, the means for determining a set of resources also includes means for transmitting to the terminal device an indication that the terminal device is to transition from an idle mode to a connected mode via a narrow physical downlink control channel (NPDCCH) scrambled with a PUR radio network temporary identifier (RNTI) allocated for the terminal device.

[0101] In some example embodiments, means for determining a set of resources includes means for obtaining a desired TBS from a request for reconfiguration information from a terminal device; and means for determining a set of resources based on the desired TBS.

[0102] In some example embodiments, the means for transmitting reconfiguration information includes means for generating reconfiguration information indicating a set of resources, a TBS, and a number of repetitions for additional transmissions in response to receiving a request for reconfiguration information of a PUR from a terminal device; and means for transmitting the reconfiguration information to the terminal device.

[0103] In some example embodiments, the component for transmitting the reconfiguration information includes a component for generating reconfiguration information indicating a set of resources, a TBS, and a number of repetitions for additional transmissions in response to receiving a request for reconfiguration information for a PUR from a terminal device, the set of resources being determined based on a desired TBS indicated by the request for reconfiguration information for the PUR; and a component for transmitting the reconfiguration information to the terminal device.

[0104] In some example embodiments, the apparatus may further include means for determining a configuration of the PUR for transmission; and means for transmitting the configuration of the PUR to the terminal device.

[0105] In some example embodiments, the component for determining the configuration includes a component for obtaining an initial TBS for transmission from a request for configuration received from a terminal device in response to the request, the initial TBS being determined by the terminal device; and a component for determining a configuration of the PUR based on the initial TBS and a coverage extension level (CEL), the configuration including at least the configured TBS for transmission, a set of resources to be allocated for transmission, and a PUR radio network temporary identifier (RNTI) allocated to the terminal device.

[0106] In some example embodiments, means for determining the configuration includes means for determining a configured TBS for transmission and a set of resources to be allocated for transmission; and means for determining the configuration of the PUR based on the configured TBS.

[0107] In some example embodiments, means for determining the configured TBS includes means for acquiring a reference TBS from an early data transmission (EDT); and means for determining the configured TBS based on the reference TBS.

[0108] In some example embodiments, an apparatus capable of executing method 400 (e.g., terminal device 120) may include a component for executing each step of method 400. The component may be implemented in any suitable form. For example, the component may be implemented in a circuit or a software module.

[0109] In some example embodiments, the apparatus includes: a component for receiving, at a terminal device, reconfiguration information of a preconfigured uplink resource (PUR) from a network device, the PUR being used for transmission from the terminal device to the network device, the reconfiguration information being generated by the network device based on a set of resources to be allocated for additional transmission from the terminal device to the network device, the set of resources being determined by the network device based on a transport block size (TBS) associated with the additional transmission in response to determining that the PUR is to be adjusted; and a component for performing the additional transmission based on the reconfiguration information.

[0110] In some example embodiments, the apparatus may further include: a component for receiving an indication from a network device indicating that a terminal device will transition from an idle mode to a connected mode via a narrow physical downlink control channel scrambled with a PUR radio network temporary identifier (RNTI) allocated to the terminal device; and a component for transmitting a request for reconfiguration information of the PUR to the network device via high-layer signaling reestablished based on the indication.

[0111] In some example embodiments, the apparatus may further include: a component for determining a desired TBS for an additional transmission in response to the amount of data of the additional transmission or the coverage extension level (CEL) being changed; and a component for transmitting a request for reconfiguration information of the PUR to a network device, the request indicating the desired TBS.

[0112] In some example embodiments, the apparatus may further include: a component for determining an initial TBS for transmission based on an amount of data for transmission and a coverage extension level (CEL) in response to receiving a system information block (SIB) from the network device indicating that the PUR is available in a cell served by the network device; a component for transmitting a request for configuration of the PUR to the network device, the request indicating the initial TBS and the CEL; and a component for receiving a configuration of the PUR from the network device, the configuration of the PUR being determined by the network device based on the initial TBS and the CEL.

[0113] In some example embodiments, the apparatus may further include means for receiving a configuration of the PUR from the network device, the configuration of the PUR being determined by the network device based on the transmitted configured TBS.

[0114] Figure 5 5 is a simplified block diagram of a device 500 suitable for implementing embodiments of the present disclosure. The device 500 may be provided to implement Figure 1 The terminal device 110 or the network device 120 shown in FIG. As shown in the figure, the device 500 includes one or more processors 510, one or more memories 520 coupled to the processor 510, and one or more transmitters and / or receivers (TX / RX) 540 coupled to the processor 510.

[0115] TX / RX 540 is used for bidirectional communication. TX / RX 540 has at least one antenna to facilitate communication. The communication interface may represent any interface required to communicate with other network elements.

[0116] Processor 510 may be of any type suitable for the local technology network, and may include, as non-limiting examples, 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. Device 500 may have multiple processors, such as application specific integrated circuit chips that are time slaved to a clock synchronized with a main processor.

[0117] The memory 520 may 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) 524, electrically programmable read-only memory (EPROM), flash memory, hard disk, compact disk (CD), digital video disk (DVD), and other magnetic storage and / or optical storage. Examples of volatile memories include, but are not limited to, random access memory (RAM) 522 and other volatile memories that will not persist for the duration of a power outage.

[0118] Computer program 530 includes computer executable instructions executed by associated processor 510. Program 530 may be stored in ROM 524. Processor 510 may perform any suitable actions and processes by loading program 530 into RAM 522.

[0119] The exemplary embodiments of the present disclosure may be implemented by the program 530 so that the device 500 may execute the Figures 2 to 4 Any process of the present disclosure discussed. The embodiments of the present disclosure may also be implemented by hardware or by a combination of software and hardware.

[0120] In some example embodiments, program 530 may be tangibly embodied in a computer-readable medium that may be included in device 500 (such as in memory 520) or in other storage devices accessible to device 500. Device 500 may load program 530 from the computer-readable medium to RAM 522 for execution. Computer-readable media may include any type of tangible non-volatile memory, such as ROM, EPROM, flash memory, hard disk, CD, DVD, etc. Figure 6 An example of a computer readable medium 600 in the form of a CD or DVD is shown. The computer readable medium has a program 530 stored thereon.

[0121] Generally, various example embodiments of the present disclosure may be implemented in hardware or dedicated circuits, software, logic, or any combination thereof. Some aspects may be implemented in hardware, while other aspects may be implemented in firmware or software that may be executed by a controller, microprocessor, or other computing device. For example, in some embodiments, various examples of the present disclosure (e.g., methods, devices, or equipment) may be implemented in part or in full on a computer-readable medium. Although various aspects of the embodiments of the present disclosure are illustrated and described as block diagrams, flow charts, or using some other illustrations, it should be understood that, as non-limiting examples, the boxes, devices, systems, techniques, or methods described herein may be implemented in hardware, software, firmware, dedicated circuits or logic, general-purpose hardware or controllers or other computing devices, or some combination thereof.

[0122] The units included in the apparatus and / or device of the present disclosure can be implemented in various ways, including software, hardware, firmware or any combination thereof. In one embodiment, one or more units can be implemented using software and / or firmware, such as machine executable instructions stored on a storage medium. In addition to or in place of machine executable instructions, some or all of the units in the apparatus and / or device can be implemented at least in part by one or more hardware logic components. For example, but not limited to, illustrative types of hardware logic components that can be used include field programmable gate arrays (FPGAs), application specific integrated circuits (ASICs), application specific standard products (ASSPs), system-on-chip systems (SOCs), complex programmable logic devices (CPLDs), etc.

[0123] As an example, embodiments of the present disclosure may be described in the context of computer executable instructions, such as those included in program modules, which are executed in a device on a target real or virtual processor. Typically, program modules include routines, programs, libraries, objects, classes, components, data structures, etc. that perform specific tasks or implement specific abstract data types. In various embodiments, the functionality of program modules may be combined or split between program modules as desired. Machine executable instructions for program modules may be executed in local devices or distributed devices. In distributed devices, program modules may be located in local and remote storage media.

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

[0125] In the context of the present disclosure, a computer-readable medium may be any tangible medium that may contain or store a program used by or in conjunction with an instruction execution system, device, or apparatus. A computer-readable medium may be a machine-readable signal medium or a machine-readable storage medium. A computer-readable medium may include, but is not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, device, or device, or any suitable combination of the foregoing. More specific examples of machine-readable storage media would include: an electrical connection with one or more wires, a portable computer floppy disk, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disk read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing.

[0126] In addition, although the operations are depicted in a particular order, this should not be understood as requiring that such operations be performed in the particular order shown or in a continuous order, or that all illustrated operations be performed to achieve the desired result. In some scenarios, multitasking and parallel processing may be advantageous. Similarly, although the above discussion includes several specific example embodiment details, these should not be interpreted as limitations on the scope of the present disclosure, but rather as descriptions of features that may be specific to a particular embodiment. Certain features described in the context of separate embodiments may also be implemented in combination in a single embodiment. On the contrary, the various features described in the context of a single embodiment may also be implemented separately in multiple embodiments or in any suitable sub-combination.

[0127] Although the disclosure has been described in language specific to structural features and / or methodological acts, it should be understood that the disclosure 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 example forms of implementing the claims.

Claims

1. A method for communication, comprising: At a network device, determining, based on data transmission from a terminal device to the network device, that a preconfigured uplink resource (PUR) is to be adjusted; responsive to determining that the PUR is to be adjusted, determining a set of resources to be allocated for the additional transmission based on a transport block size (TBS) associated with the additional transmission from the terminal device to the network device; transmitting to the terminal device via a narrow physical downlink control channel (NPDCCH) scrambled with a PUR radio network temporary identifier (RNTI) allocated for the terminal device an indication that the terminal device is to transition from an idle mode to a connected mode; as well as In response to the terminal device re-establishing a connection mode connection with the network device based on the terminal device receiving the indication from the network device, the method further includes: generating reconfiguration information of the PUR based on the set of resources; as well as The reconfiguration information is transmitted to the terminal device.

2. The method of claim 1 , wherein determining whether the PUR is to be adjusted comprises: determining the TBS based on the transmission received from the terminal device; determining whether the TBS is less than a configured TBS, the configured TBS being predetermined by the network device for the transmission; as well as In response to determining that the TBS is less than the configured TBS, it is determined that the PUR is to be adjusted.

3. The method of claim 1 , wherein determining whether the PUR is to be adjusted comprises: In response to receiving a request for reconfiguration information of the PUR from the terminal device, it is determined that the PUR is to be adjusted.

4. The method of claim 1 , wherein determining the set of resources comprises: Determining the TBS and coverage extension level (CEL); determining a number of repetitions for the additional transmission based on the TBS and the CEL; as well as The set of resources is determined based on the TBS and the number of repetitions.

5. The method of claim 1 , wherein determining the set of resources comprises: Acquire a desired TBS from a request for the reconfiguration information from the terminal device; as well as The set of resources is determined based on the desired TBS.

6. The method of claim 1 , wherein transmitting the reconfiguration information comprises: generating, in response to receiving a request for the reconfiguration information for the PUR from the terminal device, the reconfiguration information indicating the set of resources, the TBS, and the number of repetitions for the additional transmission; as well as The reconfiguration information is transmitted to the terminal device.

7. The method of claim 1 , wherein transmitting the reconfiguration information comprises: generating, in response to receiving a request for the reconfiguration information for the PUR from the terminal device, the reconfiguration information indicating the set of resources, the TBS, and the number of repetitions for the additional transmission, the set of resources being determined based on the desired TBS indicated by the request for the reconfiguration information for the PUR; as well as The reconfiguration information is transmitted to the terminal device.

8. The method according to claim 1, further comprising: determining a configuration of the PUR for the transmission; as well as The configuration of the PUR is transmitted to the terminal device.

9. The method of claim 8, wherein determining the configuration comprises: In response to receiving a request for the configuration from the terminal device, obtaining an initial TBS for the transmission from the request, the initial TBS being determined by the terminal device; and The configuration of the PUR is determined based on the initial TBS and a coverage extension level (CEL), the configuration comprising at least a configured TBS for the transmission, a set of resources to be allocated for the transmission, and a PUR Radio Network Temporary Identifier (RNTI) allocated to the terminal device.

10. The method of claim 8, wherein determining the configuration comprises: determining a configured TBS for the transmission and a set of resources to be allocated for the transmission; The configuration of the PUR is determined based on the configured TBS.

11. The method of claim 10, wherein determining the configured TBS comprises: Obtaining a reference TBS from an Early Data Transmission (EDT); as well as The configured TBS is determined based on the reference TBS.

12. A method for communication, comprising: receiving, at a terminal device, an indication from a network device via a narrow physical downlink control channel scrambled with a PUR Radio Network Temporary Identifier (RNTI) allocated for the terminal device, indicating that the terminal device is to transition from an idle mode to a connected mode; reestablishing a connected mode connection with the network device in response to receiving the indication from the network device; transmitting, via the reestablished connected mode connection, a request for reconfiguration information of the PUR to the network device; receiving, at a terminal device, from a network device, reconfiguration information of a preconfigured uplink resource (PUR), the PUR being used for transmission from the terminal device to the network device, the reconfiguration information being generated by the network device based on a set of resources to be allocated for an additional transmission from the terminal device to the network device, the set of resources being determined by the network device based on a transport block size (TBS) associated with the additional transmission in response to determining that the PUR is to be adjusted; and The additional transmitting is performed based on the reconfiguration information.

13. The method according to claim 12, further comprising: responsive to a data amount or a coverage extension level (CEL) of the further transmission being to be changed, determining a desired TBS for the further transmission; as well as A request for the reconfiguration information of the PUR is transmitted to the network device, the request indicating the desired TBS.

14. The method according to claim 12, further comprising: determining, in response to receiving a system information block (SIB) from the network device indicating that the PUR is available in a cell served by the network device, an initial TBS for the transmission based on an amount of data for the transmission and a coverage extension level (CEL); transmitting a request for the configuration of the PUR to the network device, the request indicating the initial TBS and the CEL; and The configuration of the PUR is received from the network device, the configuration of the PUR being determined by the network device based on the initial TBS and the CEL.

15. The method according to claim 12, further comprising: A configuration of the PUR is received from the network device, the configuration of the PUR being determined by the network device based on the transmitted configured TBS.

16. A device for communication, comprising: at least one processor; and at least one memory including computer program code; The at least one memory and the computer program code are configured to, with the at least one processor, cause the apparatus to at least: At a network device, determining, based on data transmission from a terminal device to the network device, that a preconfigured uplink resource (PUR) is to be adjusted; responsive to determining that the PUR is to be adjusted, determining a set of resources to be allocated for the additional transmission based on a transport block size (TBS) associated with the additional transmission from the terminal device to the network device; transmitting to the terminal device an indication that the terminal device is to transition from an idle mode to a connected mode via a narrow physical downlink control channel (NPDCCH) scrambled with a PUR radio network temporary identifier (RNTI) allocated for the terminal device; and In response to the terminal device re-establishing a connection mode connection with the network device based on the terminal device receiving the indication from the network device: generating reconfiguration information of the PUR based on the set of resources; as well as The reconfiguration information is transmitted to the terminal device.

17. The apparatus of claim 16, wherein the apparatus is caused to determine whether the PUR is to be adjusted by: determining the TBS based on the transmission received from the terminal device; determining whether the TBS is less than a configured TBS, the configured TBS being predetermined by the network device for the transmission; as well as In response to determining that the TBS is less than the configured TBS, it is determined that the PUR is to be adjusted.

18. The apparatus of claim 16, wherein the apparatus is caused to determine whether the PUR is to be adjusted by: In response to receiving a request for reconfiguration information of the PUR from the terminal device, it is determined that the PUR is to be adjusted.

19. The apparatus of claim 16, wherein the apparatus is caused to determine the set of resources by: determining the TBS and coverage extension level (CEL); and determining a number of repetitions for the additional transmission based on the TBS and the CEL; and The set of resources is determined based on the TBS and the number of repetitions.

20. The apparatus of claim 16, wherein the apparatus is caused to determine the set of resources by: acquiring a desired TBS from a request for the reconfiguration information from the terminal device; and The set of resources is determined based on the desired TBS.

21. The apparatus of claim 16, wherein the apparatus is caused to transmit the reconfiguration information by: generating, in response to receiving a request for the reconfiguration information for the PUR from the terminal device, the reconfiguration information indicating the set of resources, the TBS, and the number of repetitions for the additional transmission; and The reconfiguration information is transmitted to the terminal device.

22. The apparatus of claim 16, wherein the apparatus is caused to transmit the reconfiguration information by: generating, in response to receiving a request for the reconfiguration information for the PUR from the terminal device, the reconfiguration information indicating the set of resources, the TBS, and the number of repetitions for the additional transmission, the set of resources being determined based on the desired TBS indicated by the request for the reconfiguration information for the PUR; and The reconfiguration information is transmitted to the terminal device.

23. The apparatus of claim 16, wherein the apparatus is further caused to: determining a configuration of the PUR for the transmission; and The configuration of the PUR is transmitted to the terminal device.

24. The apparatus of claim 23, wherein the apparatus is caused to determine the configuration by: In response to receiving a request for the configuration from the terminal device, obtaining an initial TBS for the transmission from the request, the initial TBS being determined by the terminal device; and The configuration of the PUR is determined based on the initial TBS and a coverage extension level (CEL), the configuration comprising at least a configured TBS for the transmission, a set of resources to be allocated for the transmission, and a PUR Radio Network Temporary Identifier (RNTI) allocated to the terminal device.

25. The apparatus of claim 23, wherein the apparatus is caused to determine the configuration by: determining a configured TBS for the transmission and a set of resources to be allocated for the transmission; The configuration of the PUR is determined based on the configured TBS.

26. The apparatus of claim 25, wherein the apparatus is caused to determine the configured TBS by: derive a reference TBS from an Early Data Transmission (EDT); and The configured TBS is determined based on the reference TBS.

27. A device for communication, comprising: at least one processor; and at least one memory including computer program code; The at least one memory and the computer program code are configured to, with the at least one processor, cause the apparatus to at least: receiving, at a terminal device, an indication from a network device via a narrow physical downlink control channel scrambled with a PUR Radio Network Temporary Identifier (RNTI) allocated for the terminal device, indicating that the terminal device is to transition from an idle mode to a connected mode; reestablishing a connected mode connection with the network device in response to receiving the indication from the network device; transmitting, via the reestablished connected mode connection, a request for reconfiguration information of the PUR to the network device; receiving, at a terminal device, from a network device, reconfiguration information of a preconfigured uplink resource (PUR), the PUR being used for transmission from the terminal device to the network device, the reconfiguration information being generated by the network device based on a set of resources to be allocated for additional transmission from the terminal device to the network device, the set of resources being determined by the network device based on a transport block size (TBS) associated with the additional transmission in response to determining that the PUR is to be adjusted; and The additional transmitting is performed based on the reconfiguration information.

28. The apparatus of claim 27, wherein the apparatus is further caused to: responsive to a data volume or coverage extension level (CEL) of the further transmission being to be changed, determining a desired TBS for the further transmission; and A request for the reconfiguration information of the PUR is transmitted to the network device, the request indicating the desired TBS.

29. The apparatus of claim 27, wherein the apparatus is further caused to: In response to receiving a system information block (SIB) from the network device indicating that the PUR is available in a cell served by the network device, determining an initial TBS for the transmission based on an amount of data for the transmission and a coverage extension level (CEL); and transmitting a request for the configuration of the PUR to the network device, the request indicating the initial TBS and the CEL; and The configuration of the PUR is received from the network device, the configuration of the PUR being determined by the network device based on the initial TBS and the CEL.

30. The apparatus of claim 27, wherein the apparatus is further caused to: A configuration of the PUR is received from the network device, the configuration of the PUR being determined by the network device based on the transmitted configured TBS.

31. An apparatus for communication, comprising: means for determining, at a network device, based on data transmission from a terminal device to said network device, that a preconfigured uplink resource (PUR) is to be adjusted; means for determining, in response to determining that the PUR is to be adjusted, a set of resources to be allocated for an additional transmission from the terminal device to the network device based on a transport block size (TBS) associated with the additional transmission; means for transmitting to the terminal device an indication that the terminal device is to transition from an idle mode to a connected mode via a narrow physical downlink control channel (NPDCCH) scrambled with a PUR radio network temporary identity (RNTI) allocated for the terminal device; as well as In response to the terminal device re-establishing a connection mode connection with the network device based on the terminal device receiving the indication from the network device, the apparatus further includes: means for generating reconfiguration information for said PUR based on said set of resources; and A component for transmitting the reconfiguration information to the terminal device.

32. An apparatus for communication, comprising: means for receiving, at a terminal device, from a network device via a narrow physical downlink control channel scrambled with a PUR Radio Network Temporary Identifier (RNTI) allocated for the terminal device, an indication that the terminal device is to transition from an idle mode to a connected mode; means for re-establishing a connection mode connection with the network device in response to receiving the indication from the network device; means for transmitting, via the reestablished connected mode connection, to the network device a request for reconfiguration information for the PUR; means for receiving, at a terminal device, from a network device, reconfiguration information of a preconfigured uplink resource (PUR), the PUR being used for transmission from the terminal device to the network device, the reconfiguration information being generated by the network device based on a set of resources to be allocated for a further transmission from the terminal device to the network device, the set of resources being determined by the network device based on a transport block size (TBS) associated with the further transmission in response to determining that the PUR is to be adjusted; as well as Means for performing the additional transmitting based on the reconfiguration information.

33. A non-transitory computer-readable medium comprising program instructions, wherein the program instructions are used to cause an apparatus to at least perform the method according to any one of claims 1-11.

34. A non-transitory computer-readable medium comprising program instructions, wherein the program instructions are used to cause an apparatus to at least perform the method according to any one of claims 12-15.

Images