CN112292899B - Method, apparatus and computer readable medium for data transmission without RRC connection - Google Patents
Method, apparatus and computer readable medium for data transmission without RRC connection Download PDFInfo
- Publication number
- CN112292899B CN112292899B CN201880094744.0A CN201880094744A CN112292899B CN 112292899 B CN112292899 B CN 112292899B CN 201880094744 A CN201880094744 A CN 201880094744A CN 112292899 B CN112292899 B CN 112292899B
- Authority
- CN
- China
- Prior art keywords
- resource
- terminal device
- network device
- data
- receiving
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active
Links
- 230000005540 biological transmission Effects 0.000 title claims abstract description 64
- 238000000034 method Methods 0.000 title claims abstract description 33
- 238000004891 communication Methods 0.000 claims description 49
- 230000004044 response Effects 0.000 claims description 40
- 101000741965 Homo sapiens Inactive tyrosine-protein kinase PRAG1 Proteins 0.000 claims description 16
- 102100038659 Inactive tyrosine-protein kinase PRAG1 Human genes 0.000 claims description 16
- 230000015654 memory Effects 0.000 claims description 14
- 238000004590 computer program Methods 0.000 claims description 8
- 230000011218 segmentation Effects 0.000 abstract description 5
- 230000011664 signaling Effects 0.000 abstract description 5
- 238000010586 diagram Methods 0.000 description 6
- 230000010267 cellular communication Effects 0.000 description 5
- 238000005516 engineering process Methods 0.000 description 4
- 230000006870 function Effects 0.000 description 3
- 230000003993 interaction Effects 0.000 description 3
- 238000012986 modification Methods 0.000 description 3
- 230000004048 modification Effects 0.000 description 3
- 238000012545 processing Methods 0.000 description 3
- 230000007774 longterm Effects 0.000 description 2
- 238000000926 separation method Methods 0.000 description 2
- 238000012546 transfer Methods 0.000 description 2
- 230000006978 adaptation Effects 0.000 description 1
- 239000000969 carrier Substances 0.000 description 1
- 230000001413 cellular effect Effects 0.000 description 1
- 238000013500 data storage Methods 0.000 description 1
- 238000011161 development Methods 0.000 description 1
- 230000018109 developmental process Effects 0.000 description 1
- 239000012634 fragment Substances 0.000 description 1
- 238000007726 management method Methods 0.000 description 1
- 230000003287 optical effect Effects 0.000 description 1
- 230000008569 process Effects 0.000 description 1
- 238000013468 resource allocation Methods 0.000 description 1
- 239000004065 semiconductor Substances 0.000 description 1
- 230000001360 synchronised effect Effects 0.000 description 1
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W48/00—Access restriction; Network selection; Access point selection
- H04W48/08—Access restriction or access information delivery, e.g. discovery data delivery
- H04W48/14—Access restriction or access information delivery, e.g. discovery data delivery using user query or user detection
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W72/00—Local resource management
- H04W72/20—Control channels or signalling for resource management
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W48/00—Access restriction; Network selection; Access point selection
- H04W48/08—Access restriction or access information delivery, e.g. discovery data delivery
- H04W48/12—Access restriction or access information delivery, e.g. discovery data delivery using downlink control channel
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Computer Security & Cryptography (AREA)
- Mobile Radio Communication Systems (AREA)
Abstract
Embodiments of the present disclosure provide methods, apparatuses, and computer readable media for data transmission without RRC connection. According to embodiments of the present disclosure, by introducing semi-static scheduling into early transmissions, segmentation of data packets can be transmitted without RRC connection establishment, thereby saving the consumption of signaling.
Description
Technical Field
Embodiments of the present disclosure relate generally to communication technology and, more particularly, relate to methods, apparatuses, and computer readable media for data transmission without an RRC connection.
Background
In a communication system, it is often necessary to establish a Radio Resource Control (RRC) connection between a terminal device and a network device. For example, in third generation wireless communication (3G) systems or Long Term Evolution (LTE) communication systems, a terminal device typically establishes an RRC connection with a network device before transmitting data to the network device. In the fifth generation wireless communication system (5G), a small amount of data may be transmitted to the network device before RRC connection establishment. But if the terminal device transmits a large data packet, an RRC connection is still required.
Disclosure of Invention
Embodiments of the present disclosure generally relate to a method for authenticating a terminal device, and corresponding network device and terminal device.
In a first aspect, embodiments of the present disclosure provide a method implemented at a terminal device for communication. The method comprises the following steps: information of a first resource allocated for transmission without Radio Resource Control (RRC) connection establishment between the terminal device and the network device is received from the network device. The method also includes transmitting a first portion of data to the network device using the first resource and a request for semi-persistently scheduling a second resource. The method further comprises the steps of: in response to receiving the downlink information indicating the allocation of the second resource, a second portion of the data is transmitted to the network device using the second resource.
In a second aspect, embodiments of the present disclosure provide a method implemented at a network device for communication. The method comprises the following steps: information of a first resource allocated for transmission without Radio Resource Control (RRC) connection establishment between the terminal device and the network device is transmitted to the terminal device. The method further comprises the steps of: in response to receiving a first portion of data from the terminal device using the first resource and a request to semi-persistently schedule the second resource, downlink information is sent to the terminal device indicating an allocation of the second resource. The method also includes receiving a second portion of the data from the terminal device using a second resource.
In a third aspect, embodiments of the present disclosure provide a terminal device. The terminal device includes: at least one processor; and at least one memory including computer program code. The at least one memory and the computer code are configured to, with the at least one processor, cause the terminal device to perform: receiving information of a first resource from a network device, the first resource being allocated for transmission without Radio Resource Control (RRC) connection establishment between the terminal device and the network device; transmitting a first portion of data and a request for semi-persistent scheduling of a second resource to a network device using the first resource; and in response to receiving the downlink information indicating the second resource allocation, transmitting a second portion of the data to the network device using the second resource.
In a fourth aspect, embodiments of the present disclosure provide a network device. The network device includes: 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 network device to perform: transmitting information of a first resource to the terminal device, the first resource being allocated for transmission without Radio Resource Control (RRC) connection establishment between the terminal device and the network device; transmitting downlink information indicating an allocation of the second resource to the terminal device in response to receiving a first portion of data from the terminal device using the first resource and a request for semi-persistent scheduling of the second resource; and receiving a second portion of the data from the terminal device using the second resource.
In a fifth aspect, embodiments of the present disclosure provide a computer-readable medium. The computer-readable medium has stored thereon instructions that, when executed by at least one processing unit of a machine, cause the machine to implement a method according to the first aspect of the present disclosure.
In a sixth aspect, embodiments of the present disclosure provide another computer-readable medium. The further computer-readable medium has stored thereon instructions that, when executed by at least one processing unit of a machine, cause the machine to implement a method according to the second aspect of the present disclosure.
In a seventh aspect, embodiments of the present disclosure provide an apparatus for communication. The apparatus includes means for receiving information of a first resource from a network device, the first resource being allocated for transmission without a Radio Resource Control (RRC) connection establishment between a terminal device and the network device. The apparatus also includes means for transmitting a first portion of data to the network device using the first resource and a request for semi-persistently scheduling a second resource. The apparatus also includes means for transmitting a second portion of data to the network device using the second resource in response to receiving the downlink information indicating the allocation of the second resource.
In an eighth aspect, embodiments of the present disclosure provide another apparatus for communication. The apparatus includes means for transmitting information of a first resource to a terminal device, the first resource being allocated for transmission without Radio Resource Control (RRC) connection establishment between the terminal device and a network device. The apparatus also includes means for transmitting downlink information indicating an allocation of the second resource to the terminal device in response to receiving a first portion of data from the terminal device using the first resource and a request for semi-persistent scheduling of the second resource. The apparatus also includes means for receiving a second portion of the data from the terminal device using a second resource.
Other features and advantages of embodiments of the present disclosure will be apparent from the following description of the particular embodiments, taken in conjunction with the accompanying drawings, which illustrate, by way of example, the principles of the embodiments of the disclosure.
Drawings
Some example embodiments will now be described with reference to the accompanying drawings, in which
Fig. 1 shows a schematic diagram of a communication system according to an embodiment of the present disclosure;
fig. 2 is a schematic diagram illustrating interactions between a terminal device and a network device according to an embodiment of the present disclosure;
fig. 3 shows a flow chart of a method for communication implemented at a terminal device according to an embodiment of the disclosure;
Fig. 4 illustrates a flow chart of a method implemented at a network device for communication according to an embodiment of the disclosure; and
Fig. 5 shows a schematic diagram of an apparatus according to an embodiment of the present disclosure.
The same or similar reference numbers will be used throughout the drawings to refer to the same or like elements.
Detailed Description
The subject matter described herein will now be discussed with reference to several example embodiments. It should be understood that these embodiments are discussed only for the purpose of enabling those skilled in the art to better understand and thus achieve the subject matter described herein, and are not meant to imply any limitation on the scope of the subject matter.
The terminology used herein is for the purpose of describing particular embodiments only and is not intended to be limiting of example embodiments. As used herein, the singular forms "a", "an" and "the" are intended to include the plural forms as well, unless the context clearly indicates otherwise. It will be further understood that the terms "comprises," "comprising," "includes," and/or "including," when used herein, specify the presence of stated features, integers, steps, operations, elements, and/or components, but do not preclude the presence or addition of one or more other features, integers, steps, operations, elements, components, and/or groups thereof.
It should also be noted that in some alternative implementations, the functions/acts noted may occur out of the order noted in the figures. For example, two functions or acts illustrated in succession may, in fact, be executed concurrently, or the acts may sometimes be executed in the reverse order, depending upon the functionality/acts involved.
As used herein, the term "communication network" refers to a network that conforms to any suitable communication standard, such as Long Term Evolution (LTE), LTE-advanced (LTE-a), wideband Code Division Multiple Access (WCDMA), high Speed Packet Access (HSPA), and the like. Furthermore, the communication between the terminal device and the network device in the communication network may be performed according to any suitable generation communication protocol, including, but not limited to, a first generation (1G) communication protocol, a second generation (2G) communication protocol, a 2.5G communication protocol, a 2.75G communication protocol, a third generation (3G) communication protocol, a fourth generation (4G) communication protocol, a 4.5G communication protocol, a future fifth generation (5G) communication protocol, and/or any other protocol currently known or to be developed in the future.
Embodiments of the present disclosure may be applied in various communication systems. In view of the rapid development of communications, there will, of course, also be future types of communication techniques and systems that can implement the present disclosure. The scope of the present disclosure should not be limited to only the above-described systems.
The term "network device" includes, but is not limited to, a Base Station (BS), gateway, management entity, and other suitable devices in a communication system. The term "base station" or "BS" means a node B (NodeB or NB), an evolved NodeB (eNodeB or eNB), a Remote Radio Unit (RRU), a Radio Header (RH), a Remote Radio Head (RRH), a relay, a low power node (e.g., femto, pico, etc.).
The term "terminal device" includes, but is not limited to, "User Equipment (UE)" and other suitable terminal devices capable of communicating with a network device. For example, a "terminal device" may refer to a terminal, mobile Terminal (MT), subscriber Station (SS), portable subscriber station, mobile Station (MS), or Access Terminal (AT).
The term "circuitry" as used herein may refer to one or more or all of the following:
(a) Pure hardware circuit implementations (such as implementations in analog and/or digital circuitry only); and
(B) A combination of hardware circuitry and software, such as (as applicable):
(i) Combination of analog and/or digital hardware circuitry and software/firmware, and
(Ii) Any portion of a hardware processor, software, and memory having software (including digital signal processors) that work in concert to cause a device, such as a mobile phone or server, to perform various functions; and
(C) Software (e.g., firmware) is required to run but may not exist as hardware circuitry and/or a processor, such as a microprocessor or portion of a microprocessor, when operation is not required.
This definition of "circuitry" applies to all uses of this term in this disclosure, including in any claims. As another example, as used in this disclosure, the term "circuitry" also covers an implementation of a pure hardware circuit or processor (or multiple processors) or a hardware circuit or processor and a portion of its (or their) accompanying software and/or firmware. The term "circuitry" also covers (e.g., and if applicable to the particular claim element) 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.
As described above, in a communication system, it is generally necessary to establish an RRC connection between a terminal device and a network device before transmitting data packets to the terminal device. The establishment of an RRC connection consumes a lot of signalling. Recently, early Data Transmission (EDT) has been proposed. In EDT, small amounts of data can be transferred without setup. But if the segmentation of the data packet is larger than the Transport Block Size (TBS) of the EDT, the terminal device still needs to use the legacy RRC connection. In particular, the terminal device needs to establish an RRC connection and start transmission of the multiple segments of the data packet through separate allocation of a Narrowband Physical Uplink Shared Channel (NPUSCH) via a Narrowband Physical Data Control Channel (NPDCCH). The consumption of signaling varies depending on the number of segments to be transmitted. Therefore, there is a need to save the consumption of signaling.
Now, some example embodiments of the present disclosure are described below with reference to the accompanying drawings. Those skilled in the art will readily appreciate that the detailed description given herein with respect to these figures is for explanatory purposes as the disclosure extends beyond these limited embodiments.
Fig. 1 illustrates a schematic diagram of a communication system in which embodiments of the present disclosure may be implemented. Communication system 100, which is part of a communication network, includes network device 120 and terminal device 110-1, terminal devices 110-2, … …, terminal device 110-N (which may be collectively referred to as "terminal device" 110). It should be understood that the number of network devices and terminal devices 110 shown in fig. 1 is given for illustration purposes and is not meant to be limiting. Communication system 100 may include any suitable number of network devices and terminal devices. It should be noted that communication system 100 may also include other elements that have been omitted for clarity. Network device 120 may communicate with terminal device 110.
Communications in communication system 100 may be implemented in accordance with any suitable communication protocol including, but not limited to, a first generation (1G) cellular communication protocol, a second generation (2G) cellular communication protocol, a third generation (3G) cellular communication protocol, a fourth generation (4G) cellular communication protocol, a fifth generation (5G) cellular communication protocol, etc., a wireless local area network communication protocol such as Institute of Electrical and Electronics Engineers (IEEE) 802.11, and/or any other protocol currently known or developed in the future. Moreover, the communication may utilize any suitable wireless communication technology, including, but not limited to: code Division Multiple Access (CDMA), frequency Division Multiple Access (FDMA), time Division Multiple Access (TDMA), frequency Division Duplex (FDD), time Division Duplex (TDD), multiple Input Multiple Output (MIMO), orthogonal Frequency Division Multiple Access (OFDMA), and/or any other technique currently known or developed in the future.
According to embodiments of the present disclosure, by introducing semi-persistent scheduling as part of early data transmission during the random access procedure, fragments of data packets may be transmitted without RRC connection establishment, thereby saving the consumption of signaling.
Fig. 2 is a schematic diagram illustrating interactions 200 between a terminal device and a network device according to an embodiment of the present disclosure. For purposes of illustration, FIG. 2 is described with reference to interactions between terminal device 110-1 and network device 120.
In some embodiments, network device 120 may send 2010 system information to terminal device 110-1. The system information may indicate data transmission before supporting the RRC connection in the communication system. For purposes of illustration, the term "Early Data Transfer (EDT)" is used herein as an example of a transfer prior to RRC connection. It should be noted that the data transmission prior to RRC connection may also include any other suitable type of transmission. The system information may also indicate that semi-persistent scheduling for EDT is supported. In this manner, if terminal device 110-1 needs to transmit a large amount of data (e.g., a TBS greater than the EDT), terminal device 110-1 may still transmit a portion of the data to network device 120.
If the terminal device 110-1 needs to schedule EDT semi-permanently, the terminal device 110-1 may send 2020 a request for EDT. For example, the terminal device 110-1 may send an EDT preamble to indicate that semi-persistent scheduling for EDT is required.
The network device 120 sends 2030 information of the resources allocated for EDT. For example, the network device 120 may send an uplink grant for EDT. The uplink grant may include a maximum TBS size for EDT. The network device 120 may also transmit the number of subcarriers that may be used for EDT. Alternatively or additionally, the network device 120 may send a Random Access Response (RAR) to the terminal device 110-1.
Terminal device 110-1 sends 2040 a first portion of data and a request for semi-persistently scheduled resources (referred to as "second resources") to a network device. As described above, the terminal device 110-1 may divide data to be transmitted into a plurality of parts. The terminal device 110-1 may transmit the first portion of the data as an EDT. Since the data is larger than the TBS of the EDT, the terminal device 110-1 needs to request more resources to send the remaining data.
In some embodiments, the request for the second resource sent by terminal device 110-1 may include an identification of terminal device 110-1. For example, terminal device 110-1 may generate a random identifier and send the random identifier to network device 120. In another example, the terminal device 110-1 may use the terminal device's international mobile equipment identity or a portion of the international mobile equipment identity as the terminal device's identity and send the terminal device's identity to the network device 120. In other embodiments, the bit of the identifier that the terminal device 110-1 may indicate may be used as part of semi-persistently scheduling radio network temporary identity (SPS-RNTI).
In another embodiment, the request may also include one or more parameters for the RRC connection. For example, the RRC parameters may include at least one of: UE identity, establishment cause, restoration identity, and restoration cause. In other embodiments, the request may include the size of the remaining data. For example, the terminal device 110-1 may send a Buffer Status Report (BSR) in the request to indicate the number of segments of the remaining portion of data.
If network device 120 determines to allocate the second resource to terminal device 110-1, network device 120 sends 2050 downlink information to terminal device 110-1. The downlink information may be scrambled using the SPS-RNTI such that only the terminal device 110-1 may decode the DCI. In some embodiments, the SPS-RNTI may be dynamically generated using bits of an SPS-RNTI prefix and an identifier of the terminal device 110-1. The network device 120 may also send downlink information to indicate that the second resource should be released after the transmission of the second portion is completed.
In an example embodiment, the downlink information may be transmitted on a Narrowband Physical Downlink Shared Channel (NPDSCH). In other embodiments, the downlink information may be transmitted on a Narrowband Physical Downlink Control Channel (NPDCCH). If the downlink information is transmitted on NPDCCH, the downlink information may be referred to as Downlink Control Information (DCI).
In some embodiments, the downlink information may include a number of resource blocks allocated in the second resource. The resource block allocation may be done in a semi-persistent manner. The term "resource block" as used herein refers to a time-frequency resource block. In other embodiments, the downlink information may indicate a starting subframe of the second resource. For example, the downlink information may indicate a start time of a first resource block in the second resource. Alternatively or additionally, the downlink information may indicate a time interval between two adjacent resource blocks. In some embodiments, the time interval may be longer than the duration of one resource block.
In another embodiment, the downlink information may also include a size of each resource block. For example, the downlink information may include a duration of each resource block. The downlink information may also include the number of subcarriers included in each resource block. In an example embodiment, the downlink information may also indicate that the resource block size in the second resource is the same as the resource block in the first resource. In this way, SPS of EDT may be implemented.
The terminal device 110-1 transmits 2060 a second portion of data using the second resource. For example, terminal device 110-1 may transmit the segments of the second portion of data using the resource blocks allocated by network device 120. In this way, terminal device 110-1 may send a large amount of data to network device 120 without establishment of an RRC connection.
In some embodiments, if network device 120 receives a segment of the second portion of data, network device 120 may send 2070 an ACK to terminal device 110-1. The ACK may be scrambled using a temporary cell RNTI (C-RNTI). The C-RNTI may be preconfigured to the network device 120 and the terminal device 110-1.
In another embodiment, if network device 120 does not receive a segment of the second portion of data, network device 120 may send 2070 a NACK to terminal device 110-1. The network device may also send an indication of a third resource to the terminal device 110-1, the third resource being used to retransmit the segment. If terminal device 110-1 receives a NACK and an indication of a third resource, terminal device 110-1 may retransmit the segment using the third resource. As described above, the time interval between two adjacent resource blocks may be greater than the duration of a resource block, and the terminal device 110-1 may retransmit the segment in a time interval before the next segment is transmitted.
In some embodiments, after terminal device 110-1 transmits the second portion to network device 120, terminal device 110 may wait for another downlink information. In some embodiments, the network device 120 may send 2090 another downlink information including an indication that one or more segments were not successfully received. In this case, the other downlink information may further include information of a fourth resource for retransmitting one or more segments. The further control information may comprise at least one of: the number of resource blocks, the start time of the fourth resource, the time interval of the resource blocks, etc.
If network device 120 determines that the second portion of the data has been successfully received, network device 120 may send downlink information to indicate that the second resource should be released.
Fig. 3 illustrates a flow chart of a method 300 according to an example of the present disclosure. The method 300 may be implemented at the terminal device 110-1.
At block 310, terminal device 110-1 receives information of a first resource from network device 120. The first resource is allocated for transmission without Radio Resource Control (RRC) connection establishment between the terminal device and the network device.
In some embodiments, terminal device 110-1 may receive system information from network device 120. The system information indicates that semi-persistent scheduling for transmission prior to RRC establishment is allowed. In another embodiment, in response to receiving the system information, the terminal device 110-1 may send a request to the network device for transmission prior to RRC establishment. In another embodiment, terminal device 110-1 may receive an uplink grant from network device 120 for transmission prior to RRC connection establishment.
At block 320, terminal device 110-1 sends a first portion of data to the network device using the first resource and a request for semi-persistently scheduling a second resource. In some embodiments, the request for the second resource may indicate an identity of the terminal device. In another embodiment, the request for the second resource may indicate at least one parameter for the RRC connection. Alternatively or additionally, the request for the second resource may indicate a size of the second portion of data.
At block 330, in response to receiving the downlink information, terminal device 110-1 transmits a second portion of the data to network device 120 using the second resource. The downlink information may indicate a number of resource blocks in the second resource. The downlink information may also indicate a starting subframe of the second resource. In some embodiments, the downlink information indicates an interval between adjacent resource blocks in the second resource. In another embodiment, the downlink information may indicate a size of each resource block in the second resource.
In some embodiments, in response to receiving a NACK regarding the segmentation in the second portion of data, terminal device 110-1 may receive an indication of an allocation of a third resource between adjacent resource blocks in the second resource. Terminal device 110-1 may retransmit the segment using the third resource.
In some embodiments, in response to receiving a NACK regarding at least one segment in the second portion of data, terminal device 110-1 may receive an indication of the allocation of the fourth resource. Terminal device 110-1 may retransmit the segment using the fourth resource.
In another embodiment, the terminal device 110-1 may release the second resource in response to an ACK for transmission of the second portion of data. In other embodiments, the terminal device 110-1 may release the second resource upon completion of the transmission of the second portion based on the downlink information.
In some embodiments, an apparatus (e.g., terminal device 110-1) for performing method 300 may include respective components for performing corresponding steps in method 300. These components may be implemented in any suitable manner. For example, it may be implemented by circuitry or software modules.
In some embodiments, the apparatus comprises: means for receiving information of a first resource from a network device, the first resource being allocated for transmission without Radio Resource Control (RRC) connection establishment between a terminal device and the network device; means for transmitting a first portion of data and a request for semi-persistent scheduling of a second resource to a network device using the first resource; and means for transmitting a second portion of the data to the network device using the second resource in response to receiving the downlink information indicating the allocation of the second resource.
In some embodiments, the means for receiving information of the first resource comprises: means for receiving system information from a network device, the system information indicating that semi-persistent scheduling is allowed for transmissions without RRC establishment; means for sending a request for transmission prior to RRC establishment to a network device in response to receiving the system information; and means for receiving an uplink grant from the network device for transmission prior to RRC connection establishment.
In some embodiments, the apparatus further comprises: means for receiving an indication of allocation of a third resource located between adjacent resource blocks in the second resource in response to receiving a NACK regarding the segmentation in the second portion of data; and means for retransmitting the segment using the third resource.
In some embodiments, the apparatus further comprises: means for receiving an indication of an allocation of a fourth resource in response to receiving a NACK for at least one segment in the second portion of data; and means for retransmitting the at least one segment using the fourth resource.
In some embodiments, the apparatus further comprises: means for releasing the second resource in response to an ACK regarding transmission of the second portion of data.
In some embodiments, the apparatus further comprises: means for releasing the second resource based on the downlink information after the transmission of the second portion is completed.
In some embodiments, the means for receiving downlink information comprises means for receiving downlink information via a Narrowband Physical Downlink Control Channel (NPDCCH). In some embodiments, the means for receiving downlink information comprises means for receiving downlink information via a Narrowband Physical Downlink Shared Channel (NPDSCH).
Fig. 4 illustrates a flow chart of a method 400 according to an example of the present disclosure. The method 400 may be implemented at the network device 120.
At block 410, network device 120 sends information of the first resource to terminal device 110-1. The first resource is allocated for transmission without a Radio Resource Control (RRC) connection establishment between the terminal device 110-1 and the network device 120.
In some embodiments, network device 120 may send information to terminal device 110-1. The system information indicates that semi-persistent scheduling of transmissions prior to establishment for RRC is allowed. In another embodiment, network device 120 may receive a request from terminal device 110-1 for semi-persistent scheduling of transmissions prior to RRC establishment. In another embodiment, the network device 120 may transmit an uplink grant for transmission prior to RRC connection establishment.
At block 420, in response to receiving the first portion of data and the request for the second resource from terminal device 110-1 using the first resource, network device 120 transmits downlink information to terminal device 110-1 indicating an allocation of the second resource. In some embodiments, the request for the second resource may indicate an identity of the terminal device. In another embodiment, the request for the second resource may indicate at least one parameter for the RRC connection. Alternatively or additionally, the request for the second resource may indicate a size of the second portion of data.
The downlink information may indicate a number of resource blocks in the second resource. The downlink information may also indicate a starting subframe of the second resource. In some embodiments, the downlink information indicates an interval between adjacent resource blocks in the second resource. In another embodiment, the downlink information may indicate a size of each resource block in the second resource.
At block 430, network device 120 receives a second portion of data from terminal device 110-1 using a second resource.
In some embodiments, if the network device 120 fails to receive a segment in the second portion of data, the network device 120 may transmit a NACK regarding the segment in the second portion of data. The network device 120 may also transmit an indication of an allocation of a third resource between adjacent resource blocks in the second resource. The third resource is used for retransmission segmentation.
In some embodiments, if the network device 120 fails to receive at least one segment in the second portion of data, the network device 120 may transmit a NACK regarding the at least one segment. The network device 120 may also transmit an indication of the allocation of the fourth resource. The fourth resource is used to retransmit the at least one segment.
In some embodiments, network device 120 may transmit downlink information. The downlink information indicates that the second resource is released when transmission of the second portion is completed.
In some embodiments, an apparatus (e.g., network device 120) for performing method 400 may include respective components for performing corresponding steps in method 400. These components may be implemented in any suitable manner. For example, it may be implemented by circuitry or software modules.
In some embodiments, the apparatus comprises: means for transmitting information of a first resource to the terminal device, the first resource being allocated for transmission prior to Radio Resource Control (RRC) connection establishment between the terminal device and the network device; means for transmitting downlink information indicating an allocation of the second resource to the terminal device in response to receiving a first portion of data from the terminal device using the first resource and a request for the second resource; and means for receiving a second portion of the data from the terminal device using the second resource.
In some embodiments, the means for transmitting information of the first resource comprises: means for transmitting system information to the terminal device, the system information indicating that semi-persistent scheduling for transmission prior to RRC establishment is allowed; means for sending an uplink grant for a transmission prior to RRC connection establishment to the terminal device in response to receiving the request for the transmission prior to RRC connection establishment.
In some embodiments, the apparatus further comprises: means for transmitting a NACK regarding the segments in the second portion of data in response to failing to receive the segments in the second portion of data; and means for transmitting an indication of an allocation of a third resource located between adjacent resource blocks in the second resource, the third resource being used to retransmit the segment.
In some embodiments, the apparatus further comprises: means for transmitting a NACK regarding at least one segment in the second portion of data in response to failing to receive the at least one segment in the second portion of data; and means for transmitting an indication of an allocation of a fourth resource for retransmitting the at least one segment.
In some embodiments, the apparatus further comprises means for transmitting downlink information indicating release of the second resource after completion of the transmission of the second portion.
In some embodiments, the means for transmitting downlink information comprises means for transmitting downlink information via a Narrowband Physical Downlink Control Channel (NPDCCH). In some embodiments, the means for transmitting downlink information comprises means for transmitting downlink information via a Narrowband Physical Downlink Shared Channel (NPDSCH).
Fig. 5 is a simplified block diagram of an apparatus 500 suitable for implementing embodiments of the present disclosure. Device 500 may be implemented at network device 120. Device 500 may also be implemented at terminal device 110-1. As shown, the apparatus 500 includes one or more processors 510, one or more memories 520 coupled to the processor(s) 510, one or more transmitters and/or receivers (TX/RX) 540 coupled to the processor(s) 510.
Processor 510 may be of any type suitable to the local technology network and may include, by way of non-limiting example, one or more of a general purpose computer, a special purpose computer, a microprocessor, a Digital Signal Processor (DSP), and a processor based on a multi-core processor architecture. The device 500 may have multiple processors, such as application specific integrated circuit chips, that are slaved in time to a clock that is synchronized to the master processor.
Memory 520 may be of any type suitable to the local technical network and may be implemented using any suitable data storage technology, such as non-transitory computer readable storage media, semiconductor-based memory devices, magnetic memory devices and systems, optical memory devices and systems, fixed memory, and removable memory, as non-limiting examples.
Memory 520 stores at least a portion of program 530. TX/RX 540 is used for two-way communication. TX/RX 540 has at least one antenna to facilitate communications, although in practice the access node referred to in the present application may have multiple antennas. The communication interface may represent any interface necessary to communicate with other network elements.
The program 530 is assumed to include program instructions that, when executed by the associated processor 510, enable the apparatus 500 to operate in accordance with embodiments of the present disclosure, as discussed herein with reference to fig. 2-4. That is, embodiments of the present disclosure may be implemented by computer software that may be executed by the processor 510 of the device 500, or by hardware, or by a combination of software and hardware.
In the context of this disclosure, computer program code or related data may be carried by any suitable carrier to enable an apparatus, device or processor to perform the various processes and operations described above. Examples of carriers include signals, computer readable media, and the like.
While this specification contains many specific implementation details, these should not be construed as limitations on the scope of any disclosure or of what may be claimed, but rather as descriptions of features specific to particular disclosure of particular implementations. Certain features that are described in this specification in the context of separate embodiments can also be implemented in combination in a single embodiment. Conversely, various features that are described in the context of a single embodiment can also be implemented in multiple embodiments separately or in any suitable subcombination. Furthermore, although features may be described above as acting in certain combinations and even initially claimed as such, one or more features from a claimed combination can in some cases be excised from the combination, and the claimed combination may be directed to a subcombination or variation of a subcombination.
Similarly, although operations are depicted in the drawings in a particular order, this should not be understood as requiring that such operations be performed in the particular order shown or in sequential order, or that all illustrated operations be performed, to achieve desirable results. As a result. In some cases, multitasking and parallel processing may be advantageous. Moreover, the separation of various system components in the embodiments described above should not be understood as requiring such separation in all embodiments, and it should be understood that the described program components and systems can generally be integrated in a single software product or packaged into multiple software products.
Various modifications, adaptations to the foregoing exemplary embodiments of this disclosure will become apparent to those skilled in the relevant arts in view of the foregoing description, when read in conjunction with the accompanying drawings. Any and all modifications will still fall within the scope of the non-limiting and exemplary embodiments of this disclosure. Moreover, other embodiments of the disclosure set forth herein will be apparent to those skilled in the art to which the disclosure relates from consideration of the specification and practice of the disclosure presented in the foregoing specification and the associated drawings.
Therefore, it is to be understood that the embodiments of the disclosure are not to be limited to the specific embodiments disclosed and that modifications and other embodiments are intended to be included within the scope of the appended claims. Although specific terms are employed herein, they are used in a generic and descriptive sense only and not for purposes of limitation.
Claims (12)
1. A method implemented at a terminal device, comprising:
Receiving information of a first resource from a network device, the first resource being allocated for transmission without Radio Resource Control (RRC) connection establishment between the terminal device and the network device;
Transmitting, using the first resource, a first portion of data and a request for semi-persistently scheduling a second resource to the network device; wherein the request for the second resource indicates at least a size of a second portion of the data;
transmitting the second portion of the data to the network device using the second resource in response to receiving downlink information indicating an allocation of the second resource;
In response to receiving a NACK regarding a segment in the second portion of the data, receiving an indication of allocation of a third resource located between adjacent resource blocks in the second resource; and
And retransmitting the segment by using the third resource.
2. The method of claim 1, wherein receiving the information of the first resource comprises:
Receiving system information from the network device, the system information indicating that semi-persistent scheduling is allowed for the transmission without RRC establishment;
in response to receiving the system information, sending a request to the network device for the transmission without RRC establishment; and
An uplink grant for the transmission without RRC connection establishment is received from the network device.
3. A method implemented at a network device, comprising:
Transmitting information of a first resource to a terminal device, the first resource being allocated for transmission without Radio Resource Control (RRC) connection establishment between the terminal device and the network device;
Transmitting downlink information indicating an allocation of a second resource to the terminal device in response to receiving a first portion of data from the terminal device using the first resource and a request for semi-persistent scheduling of the second resource; wherein the request for the second resource indicates at least a size of a second portion of the data;
receiving the second portion of the data from the terminal device using the second resource;
In response to failing to receive a segment in the second portion of the data, sending a NACK regarding the segment in the second portion of the data; and
An indication of an allocation of a third resource located between adjacent resource blocks in the second resource is sent, the third resource being used to retransmit the segment.
4. The method of claim 3, wherein transmitting the information of the first resource comprises:
Transmitting system information to the terminal device, the system information indicating that semi-persistent scheduling is allowed for the transmission without RRC establishment;
in response to receiving a request for the transmission prior to RRC connection establishment, an uplink grant for the transmission without RRC connection establishment is sent to the terminal device.
5. A terminal device, 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 terminal device to perform:
Receiving information of a first resource from a network device, the first resource being allocated for transmission without Radio Resource Control (RRC) connection establishment between the terminal device and the network device;
Transmitting a first portion of data and a request for semi-persistent scheduling of a second resource to the network device using the first resource; wherein the request for the second resource indicates at least a size of a second portion of the data;
transmitting the second portion of the data to the network device using the second resource in response to receiving downlink information indicating an allocation of the second resource;
In response to receiving a NACK regarding a segment in the second portion of the data, receiving an indication of allocation of a third resource located between adjacent resource blocks in the second resource; and
And retransmitting the segment by using the third resource.
6. The terminal device of claim 5, wherein receiving the information of the first resource comprises:
Receiving system information from the network device, the system information indicating that semi-persistent scheduling is allowed for the transmission without RRC establishment;
in response to receiving the system information, sending a request to the network device for the transmission without RRC establishment; and
An uplink grant for the transmission without RRC connection establishment is received from the network device.
7. A network device, 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 network device to perform:
Transmitting information of a first resource to a terminal device, the first resource being allocated for transmission without Radio Resource Control (RRC) connection establishment between the terminal device and the network device;
Transmitting downlink information indicating an allocation of a second resource to the terminal device in response to receiving a first portion of data from the terminal device using the first resource and a request for semi-persistent scheduling of the second resource; wherein the request for the second resource indicates at least a size of a second portion of the data;
receiving the second portion of the data from the terminal device using the second resource;
In response to failing to receive a segment in the second portion of the data, sending a NACK regarding the segment in the second portion of the data; and
An indication of an allocation of a third resource located between adjacent resource blocks in the second resource is sent, the third resource being used to retransmit the segment.
8. The network device of claim 7, wherein transmitting the information of the first resource comprises:
Transmitting system information to the terminal device, the system information indicating that semi-persistent scheduling is allowed for the transmission without RRC establishment;
in response to receiving a request for the transmission prior to RRC connection establishment, an uplink grant for the transmission without RRC connection establishment is sent to the terminal device.
9. A communication apparatus, comprising:
means for receiving information of a first resource from a network device, the first resource being allocated for transmission without Radio Resource Control (RRC) connection establishment between the communication apparatus and the network device;
Means for sending a first portion of data and a request for semi-persistent scheduling of a second resource to the network device using the first resource; wherein the request for the second resource indicates at least a size of a second portion of the data;
Means for transmitting the second portion of the data to the network device using the second resource in response to receiving downlink information indicating an allocation of the second resource;
Means for receiving an indication of allocation of a third resource located between adjacent resource blocks in the second resource in response to receiving a NACK regarding a segment in the second portion of the data; and
And means for retransmitting the segment using the third resource.
10. The apparatus of claim 9, wherein the means for receiving the information of the first resource comprises:
Means for receiving system information from the network device, the system information indicating that semi-persistent scheduling is allowed for the transmission without RRC establishment;
Means for sending a request for the transmission without RRC establishment to the network device in response to receiving the system information; and
Means for receiving an uplink grant from the network device for the transmission without RRC connection establishment.
11. A communication apparatus, comprising:
Means for transmitting information of a first resource to a terminal device, the first resource being allocated for transmission without Radio Resource Control (RRC) connection establishment between the terminal device and the communication apparatus;
Means for transmitting downlink information indicating an allocation of a second resource to the terminal device in response to receiving a first portion of data from the terminal device using the first resource and a request for semi-persistent scheduling of the second resource; wherein the request for the second resource indicates at least a size of a second portion of the data;
Means for receiving the second portion of the data from the terminal device using the second resource;
Means for transmitting a NACK regarding segments in the second portion of the data in response to failing to receive the segments in the second portion of the data; and
Means for transmitting an indication of an allocation of a third resource located between adjacent resource blocks in the second resource, the third resource being used for retransmitting the segment.
12. The apparatus of claim 11, wherein the means for sending the information of the first resource comprises:
Means for transmitting system information to the terminal device, the system information indicating that semi-persistent scheduling is allowed for the transmission without RRC establishment;
means for sending an uplink grant for the transmission without RRC connection establishment to the terminal device in response to receiving a request for the transmission prior to RRC establishment.
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| PCT/CN2018/083788 WO2019200593A1 (en) | 2018-04-19 | 2018-04-19 | Methods, devices and computer readable medium for data transmission without rrc connections |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN112292899A CN112292899A (en) | 2021-01-29 |
| CN112292899B true CN112292899B (en) | 2024-06-28 |
Family
ID=68240559
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201880094744.0A Active CN112292899B (en) | 2018-04-19 | 2018-04-19 | Method, apparatus and computer readable medium for data transmission without RRC connection |
Country Status (2)
| Country | Link |
|---|---|
| CN (1) | CN112292899B (en) |
| WO (1) | WO2019200593A1 (en) |
Family Cites Families (10)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20080051084A1 (en) * | 2006-08-23 | 2008-02-28 | Alessio Casati | Telecommunications system and method for early transmission of data |
| CN101765146B (en) * | 2008-12-23 | 2013-06-19 | 电信科学技术研究院 | Process scheduling method and process scheduling system in communication system |
| US9762356B2 (en) * | 2012-01-24 | 2017-09-12 | Interdigital Patent Holdings, Inc. | Systems and methods for improved uplink coverage |
| CN104284340B (en) * | 2013-07-08 | 2018-03-27 | 华为技术有限公司 | D2D communication means, user equipment and base station |
| CN104756571A (en) * | 2013-10-09 | 2015-07-01 | 华为技术有限公司 | Method and apparatus for scheduling semi-persistent shared resources |
| US9999039B2 (en) * | 2015-07-23 | 2018-06-12 | Qualcomm Incorporated | Semi-persistent scheduling for enhanced machine type communications |
| WO2017031648A1 (en) * | 2015-08-21 | 2017-03-02 | 华为技术有限公司 | Uplink data transmission method and apparatus |
| WO2017034505A1 (en) * | 2015-08-21 | 2017-03-02 | Intel IP Corporation | Methods and apparatus for fast uplink access |
| WO2017116132A1 (en) * | 2015-12-31 | 2017-07-06 | 엘지전자 주식회사 | Method for transmitting and receiving uplink signal in wireless communication system supporting unlicensed band and apparatus for supporting same |
| WO2018062957A1 (en) * | 2016-09-29 | 2018-04-05 | 삼성전자 주식회사 | Method and apparatus for transmitting data in rrc deactivated or activated state |
-
2018
- 2018-04-19 WO PCT/CN2018/083788 patent/WO2019200593A1/en active Application Filing
- 2018-04-19 CN CN201880094744.0A patent/CN112292899B/en active Active
Non-Patent Citations (1)
| Title |
|---|
| Qualcomm Incorporated. "R1-1712808 Early data transmission and SPS".3GPP tsg_ran\WG1_RL1.2017,第2、4、6节. * |
Also Published As
| Publication number | Publication date |
|---|---|
| CN112292899A (en) | 2021-01-29 |
| WO2019200593A1 (en) | 2019-10-24 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US9894654B2 (en) | Defining sub-subchannels for data communication using separately provided frequency and time resources and related wireless terminals and network nodes | |
| US20240039684A1 (en) | User equipment, base stations and wireless communications system for ultra-reliable communications | |
| CN114144983B (en) | Reporting of HARQ feedback in side link transmission | |
| CN110326344B (en) | Method for transmitting data, terminal device, network device and computer storage medium | |
| CN106716898B (en) | Method and apparatus for separating PUSCH/PUCCH with large number of aggregated carriers in wireless communication system | |
| CN108702595B (en) | Method and apparatus for performing uplink transmission | |
| CN113228544B (en) | Retransmission scheme and optimization for preconfigured uplink resources | |
| CN109600850B (en) | Method and apparatus for enhancing coverage | |
| EP3097649B1 (en) | Method for configuring transmission time interval bundling at a user equipment with multiple carriers and device therefor | |
| KR102172782B1 (en) | Method and apparatus for skipping transmission block transmission according to transmission of uplink control information | |
| EP3288327A1 (en) | Terminal device, base station device, integrated circuit, and communication method | |
| US20180324766A1 (en) | Method and device for sending and receiving feedback | |
| EP3099131A1 (en) | User terminal, wireless base station, and wireless communication method | |
| CN112740813B (en) | Communication method and device | |
| CN110771107A (en) | Method and apparatus for cross-digital basic configuration scheduling | |
| TWI779075B (en) | Device and method of handling flexible duplexing | |
| CN105227282A (en) | A kind of method and apparatus of LAA Resourse Distribute | |
| CN113906801A (en) | Method, apparatus and computer readable medium for multiple TRP transmission | |
| CN114258652A (en) | Reporting of HARQ feedback in sidelink transmissions | |
| CN113455089A (en) | Contention resolution in random access procedure | |
| CN110140372B (en) | Base station, terminal device, method, program, and recording medium | |
| KR102304385B1 (en) | Signal transmission method, related apparatus and system | |
| CN106102097A (en) | Process the device and method of the hybrid automatic repeat-request running of non-Licensed Bands | |
| CN113439463A (en) | Terminal and communication method | |
| KR20210057784A (en) | Random access procedure |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |