A method of contention-based data transmission in non terrestropheral network based communication system and an apparatus performing the same

Abstract

A method for transmitting uplink data to a base station to process traffic generated by a terminal in a communication system according to one embodiment disclosed in this specification comprises: obtaining resource map information related to available contention-based resources from the base station; transmitting a scheduling request message, control information, and at least a portion of the uplink data to the base station based on the obtained resource map information; and determining whether the transmission of the at least portion of the uplink data is successful, wherein the control information may include information regarding the contention-based resources used for the transmission of the at least portion of the uplink data.

Description

Technology Field

[0001] The present invention relates to a contention-based data transmission method in a non-terrestrial network-based communication system and an electronic device for performing the same. Background Technology

[0002] Looking back at the evolution of wireless communication through successive generations, technologies have been developed primarily for human-oriented services, such as voice, multimedia, and data. Following the commercialization of 5G (5th-generation) communication systems, connected devices, which have been increasing explosively, are expected to be connected to communication networks. Examples of networked objects include vehicles, robots, drones, home appliances, displays, smart sensors installed in various infrastructures, construction machinery, and factory equipment. Mobile devices are expected to evolve into various form factors, such as augmented reality glasses, virtual reality headsets, and holographic devices. In the 6G (6th-generation) era, efforts are underway to develop improved 6G communication systems to connect hundreds of billions of devices and objects to provide diverse services. For this reason, 6G communication systems are referred to as "beyond 5G" systems.

[0003] In a 6G communication system, the maximum transmission speed is approximately 1 tera (i.e., 1,000 giga) bps, and the wireless latency is approximately 100 microseconds (μsec). In other words, compared to a 5G communication system, the transmission speed in a 6G communication system is 50 times faster and the wireless latency is reduced to one-tenth.

[0004] To achieve such high data transmission speeds and ultra-low latency, the implementation of 6G communication systems in the terahertz band (e.g., the 95 GHz to 3 THz band) is being considered. In the terahertz band, due to more severe path loss and atmospheric absorption phenomena compared to the millimeter wave (mmWave) band introduced in 5G, the importance of technologies capable of guaranteeing signal reach, or coverage, is expected to increase. As key technologies to guarantee coverage, radio frequency (RF) devices, antennas, new waveforms superior in terms of coverage to orthogonal frequency division multiplexing (OFDM), beamforming, and multi-antenna transmission technologies such as massive multiple-input and multiple-output (massive MIMO), full-dimensional MIMO (FD-MIMO), array antennas, and large-scale antennas must be developed. In addition to this, new technologies such as metamaterial-based lenses and antennas, high-dimensional spatial multiplexing technology using orbital angular momentum (OAM), and reconfigurable intelligent surface (RIS) are being discussed to improve coverage of terahertz band signals.

[0005] In addition, to improve frequency efficiency and system network, development is underway in 6G communication systems for full duplex technology, in which uplink and downlink simultaneously utilize the same frequency resources at the same time; network technology that integrates satellites and HAPS (high-altitude platform stations); network structure innovation technology that supports mobile base stations and enables network operation optimization and automation; dynamic spectrum sharing technology through collision avoidance based on spectrum usage prediction; AI-based communication technology that utilizes AI (artificial intelligence) from the design stage and internalizes end-to-end AI support functions to realize system optimization; and next-generation distributed computing technology that realizes services of complexity exceeding the limits of terminal computing capabilities by utilizing ultra-high performance communication and computing resources (mobile edge computing (MEC), cloud, etc.). In addition, attempts are continuing to further strengthen connectivity between devices, further optimize networks, promote the softwareization of network entities, and increase the openness of wireless communication through the design of new protocols to be used in 6G communication systems, the implementation of hardware-based security environments, the development of mechanisms for the safe utilization of data, and the development of technologies regarding privacy maintenance methods.

[0006] Due to the research and development of such 6G communication systems, it is expected that a new dimension of hyper-connected experience will become possible through the hyper-connectivity of 6G communication systems, which encompasses not only connections between objects but also connections between people and objects. Specifically, it is projected that 6G communication systems will enable the provision of services such as truly immersive extended reality (truly immersive XR), high-fidelity mobile holograms, and digital replicas. Furthermore, services such as remote surgery, industrial automation, and emergency response, which are provided through 6G communication systems with enhanced security and reliability, will be applied in various fields including industry, healthcare, automotive, and home appliances.

[0007] In terrestrial network-based mobile communication systems, terminals can utilize communication services by connecting to a nearby base station among the multiple base stations installed within the service area. While 4G / 5G base stations are designed to guarantee connectivity for terminals up to a distance of 100 km, a sufficient number of base stations are being installed to ensure connectivity for terminals within a few km to ensure seamless service. Considering a maximum communication distance of 100 km, propagation delay occurs by 0.03 ms, and at typical communication distances, the value is much smaller. In 4G / 5G communication systems, to ensure organic operation between the base station and the terminal, the terminal operates in synchronization with the base station's time; consequently, processing delay may occur when the terminal receives signaling from the base station and transmits data. To prevent such processing and propagation delays, 4G / 5G mobile communication systems operate with a time gap between the base station's signaling operation and the terminal's actual transmission process, and this time gap is typically assumed to be approximately 1 to 4 ms. In terrestrial-based mobile communication systems, since processing delay is much greater than propagation delay, the time gap value is typically set to be similar to the maximum processing delay.

[0008] Recently, standardization has begun for non-terrestrial mobile communication systems utilizing 5G NR technology and satellites. Furthermore, non-terrestrial mobile communication technologies are expected to be utilized in next-generation mobile communication systems such as 6G. In the case of low-orbit satellites, since the distance between the terminal and the satellite is up to 2,157 km (assuming a satellite altitude of 700 km and an elevation angle of 10 degrees), propagation delay of up to 7.2 ms can occur. Additionally, if the low-orbit satellite merely acts as a relay for signals transmitted from the ground gateway, the maximum propagation delay of 7.2 ms between the low-orbit satellite and the ground gateway must also be considered. Therefore, the maximum propagation delay from the terminal through the satellite to the ground gateway can reach 14.4 ms. Moreover, the aforementioned maximum propagation delay may increase further depending on the actual altitude of the satellite. As such, when utilizing non-terrestrial mobile communication technologies, the value of propagation delay between the terminal and the base station can be very large. Here, the term "base station" may refer to a satellite if it includes base station functions, or to a terrestrial gateway acting as a base station in a terrestrial network if the satellite does not include base station functions and merely serves as a delay. Additionally, in non-terrestrial network communication, reception performance may be very low due to the very long communication distance between the terminal and the satellite. Therefore, non-terrestrial network communication may have a very low transmission rate and is expected to be used for the continuous generation of low-capacity data, such as voice, or for transmitting low-capacity one-time information, such as text or IoT sensing data. The problem to be solved

[0009] In non-terrestrial network communication, when using a scheduling-based data transmission method primarily used in existing terrestrial network-based mobile communication systems, scheduling delays can become very large. In this regard, an existing scheduling-based data transmission method in non-terrestrial network communication is described with reference to FIG. 12. Referring to FIG. 12, a terminal (110) is allocated resources for data transmission through signaling with a base station (120), and can transmit data using the allocated resources.

[0010] When data to be transmitted occurs as traffic occurs, the terminal (110) can transmit a scheduling request (SR) message to the base station (120). By transmitting the scheduling request message, the terminal (110) can notify the base station (120) of the occurrence of data to be transmitted. The scheduling request message is control information of a very small size (e.g., 1 bit) and can be transmitted using resources that the base station (120) periodically allocates to the terminal (110) for the transmission of the scheduling request message.

[0011] When the base station (120) receives a scheduling request message from the terminal (110), the base station (120) does not know the amount of resources required by the terminal (110), so it may allocate resources for a buffer status report (BSR) to determine the traffic situation of the terminal (110). The terminal (110) can request the amount of resources required for data transmission from the base station (120) using the allocated resources, and only then can the base station (120) determine the resource requirements of the terminal (110).

[0012] The base station (120) can allocate appropriate resources to the terminal (110) only after receiving a buffer status report from the terminal (110), and the terminal (110) can transmit data according to traffic to the base station (120) using the allocated resources.

[0013] In the case of following this process, a scheduling delay may occur from the time traffic is generated at the terminal (110) until data corresponding to the generated traffic begins to be transmitted to the base station (120). As in the case of non-terrestrial network communication, if the distance between the base station (120) and the terminal (110) is substantial, the scheduling delay may become very large and may cause inefficiency in the communication system. means of solving the problem

[0014] A method for transmitting uplink data to a base station to process traffic generated by a terminal in a communication system according to one embodiment disclosed in this specification comprises: obtaining resource map information related to available contention-based resources from the base station; transmitting a scheduling request message, control information, and at least a portion of the uplink data to the base station based on the obtained resource map information; and determining whether the transmission of the at least portion of the uplink data is successful, wherein the control information may include information regarding the contention-based resources used for the transmission of the at least portion of the uplink data.

[0015] In addition, a method for a base station to perform scheduling for uplink data transmission of a terminal in a communication system according to one embodiment disclosed in this specification may include the steps of: transmitting resource map information related to available contention-based resources to the terminal; receiving a scheduling request message from the terminal; determining whether to receive control information and at least a portion of the uplink data, respectively; and determining whether to allocate resources to the terminal based at least on whether to receive the control information and whether to receive the at least portion of the uplink data, wherein the control information may include information regarding the contention-based resources that the terminal has determined to use for the transmission of at least a portion of the uplink data.

[0016] Additionally, a terminal that transmits uplink data to a base station to process traffic generated in a communication system according to one embodiment disclosed in this specification comprises a transceiver for transmitting the uplink data to the base station and at least one processor connected to the transceiver, wherein the at least one processor is configured to obtain resource map information related to available contention-based resources from the base station, transmit a scheduling request message, control information, and at least a portion of the uplink data to the base station based on the obtained resource map information, and determine whether the transmission of the at least portion of the uplink data is successful, and wherein the control information includes information regarding the contention-based resources used for the transmission of the at least portion of the uplink data. Effects of the invention

[0017] According to the embodiments disclosed herein, scheduling delays in uplink data transmission of a terminal can be reduced. This can increase the efficiency of the communication system. In addition, various effects that can be identified directly or indirectly through this specification may be provided. Brief explanation of the drawing

[0018] FIG. 1 illustrates a non-terrestrial network communication system according to one embodiment. FIG. 2 shows a resource structure according to a non-terrestrial network communication technology standard according to one embodiment. FIG. 3 is a flowchart illustrating a method for a terminal to transmit uplink data to a base station according to one embodiment. FIG. 4 illustrates the transmission of resource map information according to one embodiment. FIG. 5 illustrates uplink data transmission of a terminal based on resource map information according to one embodiment. FIG. 6a illustrates a case in which a base station fails to receive all signaling transmitted from a terminal, according to one embodiment. FIG. 6b illustrates a case in which a base station receives a scheduling request message from a terminal according to one embodiment. FIG. 6c illustrates a case in which a base station receives a scheduling request message and control information from a terminal according to one embodiment. FIG. 6d illustrates a case in which a base station receives at least a portion of a scheduling request message, control information, and uplink data from a terminal, according to one embodiment. FIG. 7a illustrates the operation of a terminal when the base station fails to receive all signaling transmitted from the terminal, according to one embodiment. FIG. 7b illustrates the operation of a terminal when a base station receives a scheduling request message from a terminal, according to one embodiment. FIG. 7c illustrates the operation of a terminal when a base station receives a scheduling request message and control information from a terminal, according to one embodiment. FIG. 7d illustrates the operation of a terminal when a base station receives at least a portion of a scheduling request message, control information, and uplink data from a terminal, according to one embodiment. FIG. 8 is a flowchart illustrating a method for transmitting uplink data to a base station to process traffic generated by a terminal in a communication system according to one embodiment. FIG. 9 is a flowchart illustrating a method in which a base station in a communication system performs scheduling for uplink data transmission of a terminal according to one embodiment. FIG. 10 is a block diagram of a terminal according to one embodiment. FIG. 11 is a block diagram of a base station according to one embodiment. Figure 12 illustrates a conventional scheduling-based data transmission method in non-terrestrial network communication. In relation to the description of the drawings, the same or similar reference numerals may be used for identical or similar components. Specific details for implementing the invention

[0019] FIG. 1 illustrates a non-terrestrial network communication system according to one embodiment.

[0020] Referring to FIG. 1, a non-ground network communication system may be composed of a terminal (110) and a base station (120, 120-1). According to various embodiments, the terminal (110) may form a non-ground network communication system with a first base station (120) at a low track, or may form a non-ground network communication system with a second base station (120-1) at a high track.

[0021] The first base station (120) may be a low earth orbit (LEO) satellite orbiting the Earth at an altitude of approximately 200 to 2000 km above the Earth's surface. The first base station (120) may orbit at a speed of 6.9 to 7.8 km / s relative to the surface. The distance between the first base station (120) and the terminal (110) may vary as the first base station (120) orbits. Accordingly, the delay time that occurs when data is transmitted from the terminal (110) communicating with the first base station (120) may vary depending on the location of the first base station (120).

[0022] The second base station (120-1) may be a geostationary orbit (GEO) satellite orbiting the Earth at an altitude of approximately 35,786 km above the Earth's surface. The second base station (120-1) may appear to be stationary relative to the Earth. That is, the second base station (120-1) may appear to always be in the same position relative to the Earth by orbiting at the same angle as the Earth rotates. Accordingly, the distance between the second base station (120-1) and the terminal (110) may always be constant, and the delay time that occurs when the terminal (110) communicating with the second base station (120-1) transmits data may be constant regardless of the location of the second base station (120-1).

[0023] Recently, as geostationary satellites have reached saturation, there is an increasing demand for satellite communication methods using low-orbit satellites such as the first base station (120). Hereinafter, the description of the base station (120, 120-1) and the terminal (110) in this specification may be described on the premise that it is the first base station (120) for convenience, but it is obvious to those skilled in the art that the description of the first base station (120) can be applied in the same or similar way to the second base station (120-1).

[0025] FIG. 2 shows a resource structure according to a non-terrestrial network communication technology standard according to one embodiment.

[0026] Referring to FIG. 2, a plurality of frames (221, 222) are illustrated as a structure of a contention-based resource according to DVB-RCS2, a non-terrestrial communication technology standard. In DVB-RCS2, a base station can define traffic bursts with various structures for each frame (221, 222) and can set a time slot number for each traffic burst. In DVB-RCS2, the frames (221, 222) can have various structures, and a plurality of frames (221, 222) that are repeated with the same structure can form a superframe (210).

[0027] The length of a superframe (210) is approximately 25 to 750 ms, and the base station can inform the terminal whether the traffic burst corresponding to each time slot of the frame (221, 222) in each superframe (210) is a resource used on a contention basis. For example, the base station can transmit information to the terminal about the contention-based resources available to the terminal in each superframe (210). Through this, the terminal can check the existence of a traffic burst included in the superframe (210) on a superframe (210) basis and determine whether each traffic burst is a resource available on a contention basis.

[0028] Through this, the terminal generating traffic can attempt to transmit data without scheduling using the relevant contention-based resource. Transmitting data using contention-based resources can be efficient for transmitting low-capacity, one-time information.

[0029] This specification discloses various embodiments of a method for a terminal to transmit uplink data by efficiently utilizing the contention-based resources described above. Through this, the scheduling delay of the terminal can be reduced and the efficiency of the communication system can be increased.

[0031] FIG. 3 is a flowchart illustrating a method for a terminal to transmit uplink data to a base station according to one embodiment.

[0032] Referring to FIG. 3, a method for a terminal (110) to transmit uplink data to a base station (120) may include steps 301 through 307. According to various embodiments, the method is not limited to that shown in FIG. 3 and may include additional steps not shown in FIG. 3, or omit some of the steps shown in FIG. 3. Also, what is indicated by an arrow in FIG. 3 is not necessarily considered to represent the transmission of information or signals.

[0033] In step 301, the base station (120) may perform configuration for contention-based resources. For example, the base station (120) may generate resource map information related to information about available contention-based resources and transmit the generated resource map information to the terminal (110). The resource map information may include information about the location, area, or size, etc., of a resource available to the terminal (110) as a contention-based resource among the specified resources.

[0034] In step 303, the terminal (110) can recognize and use contention-based resources. For example, the terminal (110) can obtain information about the location, area, or size of available contention-based resources based on resource map information obtained from the base station (120) in step 301.

[0035] In one embodiment, the terminal (110) may determine the location, area, or size of a resource to be used to transmit a scheduling request message. In one embodiment, the terminal (110) may determine the location, area, or size of a resource to be used for transmitting uplink data to process traffic that will occur. In one embodiment, the terminal (110) may determine the location, area, or size of a resource to be used to transmit control information for transmitting the uplink data. In one embodiment, the control information may include information regarding the location, area, or size of a resource to be used by the terminal (110).

[0036] Through this, the terminal (110) can use contention-based resources to transmit at least a portion of the scheduling request message, the control information, and the uplink data to the base station (120) based on the acquired resource map information. In one embodiment, the terminal (110) can transmit at least a portion of the scheduling request message, the control information, and the uplink data to the base station (120) using the same signaling. For example, the terminal (110) can transmit at least a portion of the scheduling request message, the control information, and the uplink data to the base station (120) simultaneously.

[0037] In step 305, the base station (120) may perform appropriate signaling based on the result of the contention-based transmission of the terminal (110). According to various embodiments, the base station (120) may succeed in receiving at least all of the scheduling request message, control information, and uplink data transmitted by the terminal (110) in step 303, or may fail to receive said all. According to various embodiments, the base station (120) may succeed in receiving only some of the scheduling request message, control information, and uplink data transmitted by the terminal (110) in step 303, and fail to receive the remaining part.

[0038] In various embodiments, the base station (120) may determine information to transmit to the terminal (110) based on information successfully received from the terminal (110). For example, if the base station (120) successfully receives only a scheduling request message, the base station (120) may perform resource allocation for transmitting a buffer status report (BSR) to receive a buffer status report from the terminal (110). In another example, if the base station (120) successfully receives at least all of the scheduling request message, control signals, and uplink data, the base station (120) may transmit an acknowledgment (ACK) to indicate the successful reception of the uplink data. In this way, the base station (120) may determine signaling for the terminal (110) based on the information successfully received and perform the determined signaling. More specific embodiments of step 305 are described in detail in FIGS. 6a through 6d.

[0039] In step 307, the terminal (110) can determine whether the contention-based transmission of the terminal (110) (i.e., the transmission performed in step 303) is successful based on the signaling of the base station (120) performed in step 305. For example, if the base station (120) allocates resources only for the transmission of a buffer status report, the terminal (110) can determine that among the information transmitted in step 303, only the transmission of the scheduling request message is successful, and the transmission of at least some of the control information and uplink data is a failure. In another example, if the base station (120) transmits an acknowledgment, the terminal (110) can determine that the transmission of all the information transmitted in step 303 is successful. According to various embodiments, the terminal (110) may perform additional signaling to the base station (120) or terminate the procedure depending on whether the transmission of the information transmitted in step 303 is successful. More specific embodiments of step 307 are described in detail in FIGS. 7a through 7d.

[0041] FIG. 4 illustrates the transmission of resource map information according to one embodiment.

[0042] Referring to FIG. 4, the base station (120) can transmit resource map information related to available contention-based resources to the terminal (110). In various embodiments, the transmission of resource map information by the base station (120) can be understood as the same or similar as the base station (120) attempting scheduling using the resource map information, and accordingly, can be understood as the same or similar as the base station (120) performing map scheduling.

[0043] According to one embodiment, the base station (120) may transmit resource map information to the terminal (110) periodically or non-periodically. For example, the base station (120) may transmit resource map information to the terminal (110) periodically according to a specified time interval. In another example, the base station (120) may transmit resource map information to the terminal (110) non-periodically in response to the satisfaction of specific conditions. For example, the base station (120) may transmit resource map information to the terminal (110) when conditions such as a request from the terminal (110) or the occurrence of a contention-based resource of a specified size or larger are satisfied.

[0044] According to one embodiment, the resource map information may include the size of the entire designated resource area (10) (e.g., a range in the time domain or a range in the frequency domain) and information about a plurality of resources included in the designated resource area (10). For example, the resource map information may include information about the location, use, availability, etc., of each of the plurality of resources included in the designated resource area (10).

[0045] According to various embodiments, the designated resource area (10) may include a scheduling request resource (11), a resource occupied by a first terminal (12a), a resource occupied by a second terminal (12b), a contention-based control resource (13), and a contention-based data resource (14).

[0046] According to one embodiment, the first terminal and the second terminal are different from the terminal (110), and the occupied resources (12a) of the first terminal and the occupied resources (12b) of the second terminal may be understood as contention-based resources that the terminal (110) cannot use. In various embodiments, the designated resource area (10) may not include the occupied resources (12a) of the first terminal and / or the occupied resources (12b) of the second terminal depending on the state of the first terminal and the second terminal, unlike as shown in FIG. 4. Additionally, the designated resource area (10) may include additional occupied resources of terminals, unlike as shown in FIG. 4. The scheduling request resource (11) is a resource that the base station (120) has pre-allocated to each terminal (e.g., terminal (110)), and may be understood as a resource used for requesting resources when traffic occurs to the terminal. According to one embodiment, the scheduling request resource (11) and the resources occupied by other terminals (12a, 12b) may be marked or set as contention-based resources that the terminal (110) cannot use.

[0047] According to one embodiment, the contention-based control resource (13) may be understood as a resource for transmitting control information. According to one embodiment, the control information may include information about the contention-based resource used for transmitting uplink data and other information necessary for transmitting uplink data (e.g., buffer status report (BSR)). In one embodiment, the information about the contention-based resource used for transmitting uplink data may be understood as self-scheduling (SS) information. According to one embodiment, the self-scheduling information may include the ID (identification) of the terminal (110), the location of the contention-based data resource (14) that the terminal (110) intends to use, and modulation and coding scheme (MCS) information.

[0048] According to various embodiments, the base station (120) can determine whether a specific terminal (e.g., terminal (110)) attempts to transmit data based on competition by performing blind decoding on the competition-based control resource (13). To this end, the competition-based control resource (13) may be placed at a specific location in a designated resource area (10) based on the number of terminals, the traffic pattern of the terminals, etc.

[0049] According to one embodiment, the contention-based data resource (14) may be understood as a contention-based resource that the terminal (110) can use to transmit uplink data. In one embodiment, the terminal (110) may use not only the contention-based data resource (14) but also available contention-based control resources (13) to transmit uplink data. For example, the terminal (110) may determine a contention-based control resource (13) to use for transmitting control information, and the remaining contention-based control resources (13), excluding the determined contention-based control resource (13), may be used as contention-based resources for transmitting uplink data.

[0050] According to one embodiment, the terminal (110) can directly determine the size of the contention-based data resource (14) to be used for the transmission of uplink data. In one embodiment, the terminal (110) can determine a relative area based on the contention-based control resource (13) used as the contention-based data for the transmission of uplink data. For example, the terminal (110) can decide to use the first contention-based control resource (13) for the transmission of control information for the transmission of uplink data. The terminal (110) can decide to transmit uplink data using the contention-based resource corresponding to a rectangular area with x on the time axis and y on the frequency axis, with the first contention-based control resource (13) as the reference (e.g., the first vertex). In one embodiment, information about the resource area determined by the terminal (110) for the transmission of uplink data, such as information about the location of the resource area or information about x and y, may be included in the control information, and the terminal (110) can transmit the control information to the base station (120).

[0051] According to one embodiment, the terminal (110) may directly determine the location of the resource area determined for the transmission of uplink data, or may select it based on information included in information transmitted from the base station (120) (e.g., resource map information). For example, information regarding the range of x and y for determining the resource area for the transmission of uplink data, or information regarding a set of possible (x, y), may be transmitted from the base station (120) or pre-set in advance through RRC information, etc. The terminal (110) may determine the resource area for the transmission of uplink data based on information transmitted from the base station (120) or pre-set in advance through RRC information, etc. According to one embodiment, when the terminal (110) determines the resource area for the transmission of uplink data, the base station (120) may set a limit on the terminal (110)'s determination of the resource area. For example, the base station (120) may limit the maximum size of resources that a terminal (110) can use or the probability of transmission attempts, etc., by considering the number of terminals currently connected within the cell and traffic patterns, etc., in order to prevent resource conflicts between terminals. The above limit may be included in resource map information transmitted from the base station (120) to the terminal (110), or may be pre-set with RRC information, etc.

[0052] According to one embodiment, the base station (120) may transmit multiple different resource map information to the terminal (110). In this case, each resource area according to each of the different resource map information may be an independent area separated by a frequency axis. According to one embodiment, the base station (120) may configure each terminal to use different resource map information when multiple terminals attempt to transmit contention-based data. For example, the base station (120) may configure terminals within different distance ranges to use different resource map information based on the distance between the terminal (110) and the base station (120). As another example, the base station (120) may divide terminals into multiple groups based on channel conditions and configure terminals in different groups to use different resource map information. Since allocating similar resources to terminals with similar distances or similar channel conditions can help improve the communication performance of the entire communication system, the performance of the entire communication system can be improved through such a method.

[0054] FIG. 5 illustrates uplink data transmission of a terminal based on resource map information according to one embodiment.

[0055] Referring to FIG. 5, when traffic occurs, the terminal (110) can transmit at least a portion of uplink data to the base station (120) to process the traffic based on resource map information obtained from the base station (120).

[0056] According to one embodiment, as described in FIG. 4, the resource map information obtained from the base station (120) includes information about a designated resource area (10), and the designated resource area (10) may include a scheduling request resource (11), a resource occupied by a first terminal (12a), a resource occupied by a second terminal (12b), a contention-based control resource (13), and a contention-based data resource (14).

[0057] According to one embodiment, a terminal (110) may transmit a scheduling request message using an allocated scheduling request resource (11) to notify the occurrence of traffic. The terminal (110) may determine a resource area for transmitting uplink data and transmit at least a portion of control information and uplink data using the determined resource area. According to one embodiment, the designated resource area (10) may include a first resource area (21) for transmitting a scheduling request message and a second resource area (22) for transmitting at least a portion of control information and uplink data. The first resource area (21) may not overlap with the second resource area (22). The second resource area (22) may include at least one contention-based control resource (13). The terminal (110) can transmit control information using some of at least one contention-based control resource (13) included in the second resource area (22), and can transmit at least some of the uplink data using the remaining resources in the second resource area (22) excluding the contention-based control resource (13) for transmitting the control information.

[0058] According to one embodiment, the terminal (110) can compare the size of the uplink data for processing the generated traffic with the size of the available contention-based resources.

[0059] In one embodiment, if the size of the uplink data to process the generated traffic is smaller than or equal to the size of the available contention-based resource, the terminal (110) can transmit all of the uplink data to the base station (120) using the available contention-based resource. That is, in this case, the terminal (110) can transmit a scheduling request message, control information, and all of the uplink data to the base station (120). The scheduling request message, control information, and all of the uplink data can be transmitted to the base station (120) through the same signaling. In other words, the scheduling request message, control information, and all of the uplink data can be transmitted to the base station (120) simultaneously. In this case, the control information may include self-scheduling information, and the self-scheduling information may include information regarding the size of the uplink data to be transmitted. Through this, the base station (120) that has successfully received the control information can obtain information regarding the size of the uplink data even if it fails to receive the uplink data.

[0060] In one embodiment, if the size of the uplink data to process the generated traffic is larger than the size of the available contention-based resource, the terminal (110) may transmit a portion of the uplink data to the base station (120) using the available contention-based resource. That is, in this case, the terminal (110) may transmit a scheduling request message and control information to the base station (120), and transmit only a portion of the uplink data corresponding to the size of the available contention-based resource to the base station (120). In this case, the terminal (110) may include buffer status report (BSR) information in the control information along with self-scheduling information. The self-scheduling information may include information regarding the size of the portion of the uplink data to be transmitted, and the buffer status report information may include information regarding the total size of the uplink data that the terminal (110) intends to transmit or the size of the uplink data remaining that the terminal (110) cannot transmit. In this case, the scheduling request message, control information, and the portion of the uplink data may be transmitted to the base station (120) through the same signaling. In other words, a scheduling request message, control information, and a portion of the uplink data can be transmitted to the base station (120) simultaneously. The base station (120) can obtain information regarding the size of a portion of the uplink data currently being transmitted via signaling, information regarding the total size of the uplink data that the terminal (110) intends to transmit, and information regarding the size of the uplink data that has not yet been transmitted from the terminal (110) through self-scheduling information and buffer status report information. Through this, the base station (120), having successfully received the control information, can obtain information regarding the size of the uplink data even if it fails to receive the uplink data.

[0061] According to various embodiments, even if a scheduling request message, control information, and uplink data are transmitted simultaneously by the same signaling, the robustness of transmission for each piece of information may differ. That is, the robustness of transmission for the scheduling request message may be higher than that of transmission for the control information, and the robustness of transmission for the control information may be higher than that of transmission for uplink data. Accordingly, at the base station, the probability of receiving the scheduling request message may be highest, and the probability of receiving the uplink data may be lowest.

[0062] As described above, in an embodiment according to the present disclosure, the terminal (110) can simultaneously transmit at least a portion of control information and uplink data along with a scheduling request message, thereby reducing the delay time for the transmission of uplink data.

[0064] FIG. 6a illustrates a case in which, according to one embodiment, a base station fails to receive all signaling transmitted from a terminal. FIG. 6b illustrates a case in which, according to one embodiment, a base station receives a scheduling request message from a terminal. FIG. 6c illustrates a case in which, according to one embodiment, a base station receives a scheduling request message and control information from a terminal. FIG. 6d illustrates a case in which, according to one embodiment, a base station receives a scheduling request message, control information, and at least a portion of uplink data from a terminal.

[0065] Referring to FIGS. 6a through 6d, a base station may succeed in receiving only some of the information transmitted from a terminal, such as a scheduling request message, control information, and uplink data, or may succeed in receiving or fail to receive all of the information. As previously explained in FIG. 5, the robustness of transmission for each of the scheduling request message, control information, and uplink data may differ. Therefore, the base station may fail to receive all of the information (Fig. 6a), succeed in receiving only the scheduling request message with the highest robustness among the information (Fig. 6b), fail to receive only the uplink data with the lowest robustness among the information (Fig. 6c), or succeed in receiving all of the information (Fig. 6d). In various embodiments, the operation of the base station regarding the information transmitted from the terminal may differ depending on the information that the base station succeeds in receiving.

[0066] Referring to FIG. 6a, the base station may fail to receive information transmitted from the terminal, such as a scheduling request message, control information, and uplink data. In this case, the base station may not perform a corresponding operation because it has not received any signaling. The base station may transmit resource map information to the terminal again periodically or non-periodically and may wait until it successfully receives at least one of the scheduling request message, control information, and uplink data from the terminal.

[0067] Referring to FIG. 6b, the base station may successfully receive only the scheduling request message among the information transmitted from the terminal, such as the scheduling request message, control information, and uplink data. The scheduling request message may be transmitted using a specific resource allocated to each terminal at a specific location or using a specific code, etc. at a specific location. To verify whether each terminal has transmitted the scheduling message, the base station may attempt to decode the specific resources, thereby confirming that the scheduling request message has been received from a specific terminal.

[0068] In one embodiment, since the base station has failed to receive control information and uplink data, it may not know the amount of uplink data that the terminal intends to transmit or the amount of resources required for the terminal to transmit uplink data. In this case, the terminal may allocate resources corresponding to a scheduling request message, and since the allocated resources are resources for transmitting buffer status reports, they may have a size less than or equal to a specified level.

[0069] Referring to FIG. 6c, a base station may successfully receive the scheduling request message and control information among the information transmitted from the terminal, such as the scheduling request message, control information, and uplink data, while failing to receive the uplink data. The control information may include information regarding the terminal ID to indicate the identification of the terminal. For example, the control information may include self-scheduling information, and the self-scheduling information may include information regarding the terminal ID. The base station may identify the terminal to which the control information was transmitted by using the information regarding the terminal ID included in the received control information.

[0070] In one embodiment, even if the base station fails to receive uplink data, it succeeds in receiving control information, so it can obtain information regarding the amount of uplink data that the terminal intends to transmit or the amount of resources required for the terminal to transmit uplink data. According to various embodiments, the control information may or may not include buffer status report (BSR) information.

[0071] In one embodiment, if the control information received from the terminal does not include buffer status report information, the base station may determine that the terminal has transmitted all of the uplink data for processing the generated traffic. In this case, the base station may obtain information regarding the amount of resources required for the terminal to transmit uplink data by using the self-scheduling information included in the control information. That is, since the self-scheduling information may include information regarding contention-based resources used for the transmission of uplink data, such as the location, area, or size of the contention-based resources, the base station may obtain information regarding the amount of resources required for the terminal to transmit uplink data. In this case, the base station may decide to omit the allocation of resources for the transmission of the buffer status report and immediately allocate resources for the transmission of uplink data.

[0072] In one embodiment, if the control information received from the terminal includes buffer status report information, the base station may determine that the terminal has transmitted only a portion of the uplink data for processing the generated traffic. In this case, the base station may obtain information regarding the amount of resources required for the terminal to transmit uplink data by utilizing the self-scheduling information and buffer status report information included in the control information. For example, the self-scheduling information may include information regarding contention-based resources used for transmitting a portion of the uplink data, such as the location, area, or size of the contention-based resources, and the buffer status report information may include information regarding the amount of resources required to transmit the remaining uplink data. Through this, the base station may obtain information regarding the amount of resources required for the terminal to transmit all of the uplink data. In this case, the base station may decide to omit the allocation of resources for transmitting the buffer status report and immediately allocate resources for transmitting the uplink data.

[0073] Referring to FIG. 6d, the base station can successfully receive all information transmitted from the terminal, such as a scheduling request message, control information, and uplink data. The uplink data is transmitted using a contention-based data resource, and the area of ​​the contention-based data resource may be adjacent to the area of ​​the same terminal's contention-based control resource. Since the base station can identify the transmitting terminal for the control information through the terminal's ID, it can use this to identify the transmitting terminal for the received uplink data as well.

[0074] In one embodiment, when a base station receives uplink data from a terminal, regardless of whether there is any uplink data remaining for the terminal to transmit, the base station may transmit an acknowledgment (ACK) to the terminal in response to the terminal's scheduling request message.

[0075] According to various embodiments, control information received from a terminal may or may not include buffer status report (BSR) information. In one embodiment, if the control information received from the terminal does not include buffer status report information, the base station may determine that the terminal has transmitted all of the uplink data for processing the generated traffic. In this case, the base station may determine that there are no more resources required by the terminal and may decide not to allocate resources to the terminal. In one embodiment, if the control information received from the terminal includes buffer status report information, the base station may determine that the terminal has transmitted only a portion of the uplink data for processing the generated traffic. In this case, the base station may use the buffer status report information included in the control information to obtain information regarding the amount of resources the terminal requires to transmit the remainder of the uplink data. Based on the received buffer status report information, the base station may decide to allocate resources to the terminal.

[0077] FIG. 7a illustrates the operation of a terminal when a base station fails to receive all signaling transmitted from a terminal, according to one embodiment. FIG. 7b illustrates the operation of a terminal when a base station receives a scheduling request message from a terminal, according to one embodiment. FIG. 7c illustrates the operation of a terminal when a base station receives a scheduling request message and control information from a terminal, according to one embodiment. FIG. 7d illustrates the operation of a terminal when a base station receives a scheduling request message, control information, and at least a portion of uplink data from a terminal, according to one embodiment.

[0078] Referring to FIGS. 7a through 7d, the operation of the base station (120) depends on whether each of the information transmitted from the terminal (110) is received, and the operation of the terminal (110) accordingly may also vary depending on the different operations of the base station (120). For example, if the base station (120) fails to receive all the information, the terminal (110) may not receive any signaling from the base station (120) (Fig. 7a), and if the base station (120) succeeds in receiving only the scheduling request message, the terminal (110) may be allocated only the resources for the buffer status report (BSR) from the base station (120) (Fig. 7b). Alternatively, if the base station (120) successfully receives the scheduling request message and control information, the terminal (110) may be allocated resources for uplink data (Fig. 7c), and if the base station (120) successfully receives the scheduling request message, control information, and all of the uplink data, the terminal (110) may receive an acknowledgment (ACK) (Fig. 7d). In various embodiments, the operation of the terminal (110) may vary depending on the signaling of the base station (120).

[0079] Referring to FIG. 7a, the base station (120) may fail to receive information transmitted from the terminal (110), such as a scheduling request message, control information, and the entire uplink data, and may not perform any signaling to the terminal (110). According to one embodiment, the terminal (110) may determine whether it has received a message related to the transmitted scheduling request message from the base station (120) within a specified time. In one embodiment, if the message is not received from the base station (120) within a specified time, the terminal (110) may determine that the transmission of uplink data, including the previously transmitted scheduling request message and control information, has failed.

[0080] In one embodiment, the terminal (110) may attempt to retransmit information because it has determined that the transmission of previously transmitted information has failed. The terminal (110) may reacquire resource map information from the base station (120) and, based on the reacquired resource map information, retransmit a scheduling request message, control information, and uplink data to the base station (120). In one embodiment, the operation of retransmitting the information may be the same or similar to the operation of previously transmitting the information.

[0081] Referring to FIG. 7b, the base station (120) may successfully receive only the scheduling request message among the information transmitted from the terminal (110), such as the scheduling request message, control information, and uplink data, and the terminal (110) may be allocated resources for transmitting a buffer status report (BSR) from the base station (120) within a specified time without an acknowledgment (ACK). According to one embodiment, the terminal (110) may be allocated resources corresponding to the scheduling request message from the base station (120) within a specified time and may determine that the size of the allocated resources is less than or equal to a specified level. In this case, the terminal (110) may determine that the allocated resources are resources for transmitting the buffer status report and that only the scheduling request message among the previously transmitted information was received by the base station (120). Additionally, since the terminal (110) did not receive an acknowledgment from the base station (120), it may determine that the transmission of uplink data also failed.

[0082] In one embodiment, the terminal (110) is allocated only resources for transmitting a buffer status report, so it can transmit the buffer status report using the allocated resources. In this case, the base station (120) can allocate resources for transmitting uplink data based on the buffer status report transmitted from the terminal (110), and the terminal (110) can transmit uplink data using the allocated resources.

[0083] Referring to FIG. 7c, the base station (120) may successfully receive information transmitted from the terminal (110), such as a scheduling request message, control information, and uplink data, specifically the scheduling request message and control information, and the terminal (110) may receive resources from the base station (120) within a specified time without an acknowledgment (ACK). According to one embodiment, the terminal (110) may receive resources corresponding to the scheduling request message from the base station (120) within a specified time, and may determine that the size of the allocated resources is greater than a specified level. In this case, the terminal (110) may determine that the allocated resources are resources for transmitting uplink data, and may determine that the scheduling request message and control information among the previously transmitted information have been received by the base station (120). Additionally, since the terminal (110) did not receive an acknowledgment from the base station (120), it may determine that the transmission of uplink data has failed.

[0084] In one embodiment, since the terminal (110) has been allocated resources for the transmission of uplink data, it can transmit uplink data using said allocated resources. In this case, the base station (120) can receive the uplink data and transmit an acknowledgment to the terminal (110). The terminal (110) can receive the acknowledgment and confirm that the transmission of the uplink data was successful.

[0085] Referring to FIG. 7d, the base station (120) may successfully receive information transmitted from the terminal (110), such as a scheduling request message, control information, and the entire uplink data, and the terminal (110) may receive an acknowledgment (ACK) from the base station (120) within a specified time. By receiving the acknowledgment, the terminal (110) may determine that the transmission of the uplink data, including the scheduling request message and control information, has been successful.

[0086] According to one embodiment, the terminal (110) may be allocated resources upon receiving the acknowledgment within a specified time. The allocated resources may be determined to correspond to the request for insufficient resources made by the terminal (110) during the initial transmission of uplink data. That is, in this case, the terminal (110) may have additional uplink data to transmit. The terminal (110) may use the allocated resources to transmit the remaining uplink data that was not transmitted during the initial transmission to the base station (120).

[0088] FIG. 8 is a flowchart illustrating a method for transmitting uplink data to a base station to process traffic generated by a terminal in a communication system according to one embodiment.

[0089] Referring to FIG. 8, a method (800) for a terminal in a communication system to transmit uplink data to a base station may include steps 801 through 805. According to various embodiments, the method (800) is not limited to that shown in FIG. 8 and may include additional steps not shown in FIG. 8, or may omit steps shown in FIG. 8. In various embodiments, the method (800) may be understood to be performed by a terminal (e.g., terminal (110) of FIG. 1) or a processor included in the terminal (e.g., processor (1030) of FIG. 10).

[0090] In step 801, the terminal may obtain resource map information from the base station. The resource map information may be information related to available contention-based resources. For example, the resource map information may include information about the location, area, or size of available contention-based resources among a specified resource area.

[0091] In step 803, the terminal may transmit a scheduling request message, control information, and at least a portion of uplink data based on the acquired resource map information. The control information may include information about a contention-based resource used for the transmission of the at least portion of the uplink data.

[0092] According to one embodiment, the size of the available contention-based resource based on resource map information may be smaller than the size of the uplink data that the terminal intends to transmit, and in this case, the terminal may transmit only a portion of the uplink data along with a scheduling request message and control information. In one embodiment, if the size of the available contention-based resource is smaller than the size of the uplink data that the terminal intends to transmit, the terminal may transmit a buffer status report (BSR) to the base station for the remaining portion of the uplink data that could not be transmitted.

[0093] According to one embodiment, the terminal can directly determine at least one of the location, area, and size of a contention-based resource used for the transmission of uplink data among available contention-based resources. Information regarding at least one of the determined location, area, and size of the contention-based resource may be included in control information and transmitted to a base station.

[0094] In step 805, the terminal can determine whether transmission is successful for at least a portion of the uplink data transmitted to the base station. For example, the terminal can determine whether it has received a message related to a scheduling request message from the base station within a specified time. If the terminal does not receive said message from the base station within the specified time, the terminal can determine that the transmission has failed. As another example, the terminal can receive an acknowledgment corresponding to the scheduling request message from the base station within the specified time, and in this case, the terminal can determine that the transmission has succeeded. As yet another example, the terminal may not receive an acknowledgment corresponding to the scheduling request message from the base station within the specified time, but may be allocated resources from the base station. In this case, the terminal can determine that the transmission of the uplink data has failed because the acknowledgment was not received.

[0095] In various embodiments, the terminal can determine whether the transmission of uplink data is successful and, if it fails, perform retransmission. When the terminal receives an acknowledgment from the base station regarding the retransmission, the terminal can terminate the transmission of uplink data.

[0097] FIG. 9 is a flowchart illustrating a method in which a base station in a communication system performs scheduling for uplink data transmission of a terminal according to one embodiment.

[0098] Referring to FIG. 9, a method (900) in which a base station in a communication system performs scheduling for uplink data transmission of a terminal may include steps 901 through 907. According to various embodiments, the method (900) is not limited to that shown in FIG. 9 and may include additional steps not shown in FIG. 9, or may omit the steps shown in FIG. 9. In various embodiments, the method (900) may be understood to be performed by a base station (e.g., base station (120) of FIG. 1) or a processor included in the base station (e.g., processor (1130) of FIG. 11).

[0099] In step 901, the base station may transmit resource map information to the terminal. The resource map information may be information related to available contention-based resources. For example, the resource map information may include information about the location, area, or size of available contention-based resources among a specified resource area. The base station may transmit the resource map information periodically or non-periodically.

[0100] In step 903, the base station may receive a scheduling request message from a terminal. In one embodiment, the base station may receive the scheduling request message and identify the terminal that transmitted the received scheduling request message.

[0101] In step 905, the base station may determine whether to receive control information and whether to receive uplink data, respectively. In one embodiment, the base station may not receive both control information and uplink data, may receive only some of the control information and uplink data, or may receive both control information and uplink data.

[0102] In step 907, the base station may determine whether to allocate resources to the terminal. In various embodiments, the base station may determine whether to allocate resources to the terminal based at least on whether control information and uplink data have been received. For example, if neither control information nor uplink data has been received, the base station may determine to allocate resources to the terminal for the transmission of a buffer status report (BSR). In another example, if only control information has been received, the base station may determine to allocate resources of the size required for the transmission of uplink data to the terminal. In yet another example, if both control information and uplink data have been received, the base station may send an acknowledgment to the terminal and determine whether to allocate resources based on whether the control information includes a buffer status report (BSR). For example, if the control information includes a buffer status report, the base station may determine that the terminal requires additional resources, and thus may determine to allocate resources to the terminal.

[0104] FIG. 10 is a block diagram of a terminal according to one embodiment.

[0105] Referring to FIG. 10, the terminal of the present disclosure may include a processor (1030), a transceiver (1010), and a memory (1020). However, the components of the terminal are not limited to the examples described above. For example, the terminal may include more components or fewer components than the components described above. In addition, the processor (1030), the transceiver (1010), and the memory (1020) may be implemented in the form of a single chip.

[0106] According to one embodiment, the processor (1030) can control a series of processes that allow the terminal to operate according to the embodiments of the present disclosure described above. For example, the processor (1030) can control the components of the terminal for the transmission of uplink data according to the embodiments of the present disclosure. There may be a plurality of processors (1030), and the processor (1030) can perform the operation of transmitting uplink data of the present disclosure described above by executing a program stored in memory (1020).

[0107] The transceiver (1010) can transmit and receive signals with a base station. The signals transmitted and received with the base station may include control information and data. The transceiver (1010) may be composed of an RF transmitter that up-converts and amplifies the frequency of a transmitted signal, and an RF receiver that low-noise amplifies a received signal and down-converts the frequency. However, such a transceiver (1010) is merely an example of an embodiment, and the components of the transceiver (1010) are not limited to an RF transmitter and an RF receiver. Additionally, the transceiver (1010) can receive a signal through a wireless channel and output it to a processor (1030), and transmit the signal output from the processor (1030) through a wireless channel.

[0108] According to one embodiment, the memory (1020) may store programs and data necessary for the operation of the terminal. Additionally, the memory (1020) may store control information or data included in signals transmitted and received by the terminal. The memory (1020) may be composed of a storage medium or a combination of storage media such as ROM, RAM, hard disk, CD-ROM, and DVD. Additionally, there may be multiple memory (1020). According to one embodiment, the memory (1020) may store a program for performing an operation to transmit uplink data, which is one of the embodiments of the present disclosure described above.

[0110] FIG. 11 is a block diagram of a base station according to one embodiment.

[0111] Referring to FIG. 11, the base station of the present disclosure may include a processor (1130), a transceiver (1110), and a memory (1120). However, the components of the base station are not limited to the examples described above. For example, the base station may include more components or fewer components than the components described above. In addition, the processor (1130), the transceiver (1110), and the memory (1120) may be implemented in the form of a single chip.

[0112] The processor (1130) can control a series of processes to enable the base station to operate according to the embodiments of the present disclosure described above. For example, it can control the components of the base station so that the terminal performs the operation of transmitting uplink data in the communication system according to the embodiments of the present disclosure. There may be multiple processors (1130), and the processor (1130) can perform the operations of the base station for the terminal to perform the operation of transmitting uplink data in the communication system of the present disclosure described above by executing a program stored in the memory (1120).

[0113] The transceiver (1110) can transmit and receive signals with a terminal. The signals transmitted and received with the terminal may include control information and data. The transceiver (1110) may be composed of an RF transmitter that up-converts and amplifies the frequency of a transmitted signal, and an RF receiver that low-noise amplifies a received signal and down-converts the frequency. However, such a transceiver (1110) is merely an example of an embodiment, and the components of the transceiver (1110) are not limited to an RF transmitter and an RF receiver. Additionally, the transceiver (1110) can receive a signal through a wireless channel and output it to a processor (1130), and transmit the signal output from the processor (1130) through a wireless channel.

[0114] According to one embodiment, the memory (1120) may store programs and data necessary for the operation of a base station. Additionally, the memory (1120) may store control information or data included in signals transmitted and received by the base station. The memory (1120) may be composed of a storage medium or a combination of storage media such as ROM, RAM, hard disk, CD-ROM, and DVD. Additionally, there may be multiple memory (1120). According to one embodiment, the memory (1120) may store programs for base station operations for a terminal to perform an operation of transmitting uplink data in a communication system, which is one of the embodiments of the present disclosure described above.

[0116] A method for transmitting uplink data to a base station to process traffic generated by a terminal in a communication system according to one embodiment disclosed in this specification comprises: obtaining resource map information related to available contention-based resources from the base station; transmitting a scheduling request message, control information, and at least a portion of the uplink data to the base station based on the obtained resource map information; and determining whether the transmission of the at least portion of the uplink data is successful, wherein the control information may include information regarding the contention-based resources used for the transmission of the at least portion of the uplink data.

[0117] According to one embodiment, the method may further include the step of determining at least one of the location, area, and size of the competition-based resource used based on the acquired resource map information.

[0118] According to one embodiment, the method may further include the step of comparing the size of the uplink data with the size of the available contention-based resource and the step of transmitting a buffer status report (BSR) to the base station when the size of the uplink data is greater than the size of the available contention-based resource.

[0119] According to one embodiment, the method may further include the step of determining whether at least a message related to the scheduling request message was received from the base station within a specified time, and the step of determining that the transmission of at least a portion of the uplink data has failed based on the determination that the message was not received from the base station within the specified time. In one embodiment, the method may further include the step of reacquiring resource map information related to available contention-based resources from the base station, and the step of retransmitting the scheduling request message, the at least portion of the uplink data, and the control information to the base station based on the reacquired resource map information.

[0120] According to one embodiment, the method may further include the steps of: receiving a resource corresponding to the scheduling request message from a base station within a specified time; and, if the size of the allocated resource is less than or equal to a specified level, determining that the transmission of at least a portion of the uplink data has failed and transmitting a buffer status report (BSR) to the base station.

[0121] According to one embodiment, the method may further include the step of determining that the transmission of at least a portion of the uplink data has been successful when an acknowledgment (ACK) corresponding to the scheduling request message is received from a base station within a specified time. In one embodiment, the method may further include the step of allocating a resource corresponding to the scheduling request message from a base station within the specified time, and the step of transmitting the remainder of the uplink data, excluding at least a portion, to the base station using the allocated resource.

[0122] According to one embodiment, the method may further include the step of determining that the transmission of at least a portion of the uplink data has failed when an acknowledgment (ACK) corresponding to the scheduling request message is not received from a base station within a specified time and a resource corresponding to the scheduling request message is allocated, and the step of transmitting the uplink data to the base station using the allocated resource.

[0123] According to one embodiment, the robustness of the transmission of the scheduling request message may be higher than the robustness of the transmission of the control information, and the robustness of the transmission of the control information may be higher than the robustness of the transmission of at least a portion of the uplink data.

[0124] In addition, a method for a base station to perform scheduling for uplink data transmission of a terminal in a communication system according to one embodiment disclosed in this specification may include the steps of: transmitting resource map information related to available contention-based resources to the terminal; receiving a scheduling request message from the terminal; determining whether to receive control information and at least a portion of the uplink data, respectively; and determining whether to allocate resources to the terminal based at least on whether to receive the control information and whether to receive the at least portion of the uplink data, wherein the control information may include information regarding the contention-based resources that the terminal has determined to use for the transmission of at least a portion of the uplink data.

[0125] According to one embodiment, the method may further include the step of transmitting an acknowledgment (ACK) corresponding to the scheduling request message to the terminal when it is determined that at least a portion of the control information and the uplink data has been received. In one embodiment, the method may further include the step of determining to allocate resources to the terminal based on the received buffer status report (BSR) when the received control information includes a buffer status report (BSR). In one embodiment, the method may further include the step of determining not to allocate resources to the terminal when the received control information does not include a buffer status report.

[0126] According to one embodiment, the method may further include the step of determining that the control information has been received and determining that at least a portion of the uplink data has not been received, determining to allocate a resource to the terminal. In one embodiment, if the received control information includes a buffer status report (BSR), the size of the resource allocated to the terminal may be determined based on the information regarding the contention-based resource included in the control information and the buffer status report. In one embodiment, if the received control information does not include a buffer status report (BSR), the size of the resource allocated to the terminal may be determined based on the information regarding the contention-based resource included in the control information.

[0127] Additionally, a terminal that transmits uplink data to a base station to process traffic generated in a communication system according to one embodiment disclosed in this specification comprises a transceiver for transmitting the uplink data to the base station and at least one processor connected to the transceiver, wherein the at least one processor is configured to obtain resource map information related to available contention-based resources from the base station, transmit a scheduling request message, control information, and at least a portion of the uplink data to the base station based on the obtained resource map information, and determine whether the transmission of the at least portion of the uplink data is successful, and wherein the control information includes information regarding the contention-based resources used for the transmission of the at least portion of the uplink data.

[0128] According to one embodiment, the at least one processor may be configured to determine at least one of the location, area, and size of the contention-based resource used based on the acquired resource map information.

[0129] According to one embodiment, the at least one processor may be configured to compare the size of the uplink data and the size of the available contention-based resource, and if the size of the uplink data is larger than the size of the available contention-based resource, to transmit a buffer status report (BSR) to the base station.

[0131] The various embodiments of this document and the terms used therein are not intended to limit the technical features described in this document to specific embodiments, and should be understood to include various modifications, equivalents, or substitutions of said embodiments. In connection with the description of the drawings, similar reference numerals may be used for similar or related components. The singular form of a noun corresponding to an item may include one or more of said items unless the relevant context clearly indicates otherwise. In this document, each of phrases such as "A or B," "at least one of A and B," "at least one of A or B," "A, B or C," "at least one of A, B and C," and "at least one of A, B, or C" may include any one of the items listed together in the corresponding phrase, or all possible combinations thereof. Terms such as “first,” “second,” or “first” or “second” may be used simply to distinguish a component from another component and do not limit the components in any other aspect (e.g., importance or order). Where any (e.g., first) component is referred to as “coupled” or “connected” to another (e.g., second) component, with or without the terms “functionally,” “electrically,” or “communicationally,” it means that said component may be connected to said other component directly (e.g., wired), wirelessly, or through a third component.

[0132] The term “module” as used in the various embodiments of this document may include a unit implemented in hardware, software, or firmware, and may be used interchangeably with terms such as logic, logic block, component, or circuit, for example. A module may be a component formed integrally, or a minimum unit of said component or a part thereof that performs one or more functions. For example, according to one embodiment, a module may be implemented in the form of an application-specific integrated circuit (ASIC).

[0133] Various embodiments of this document may be implemented as software comprising one or more instructions stored on a storage medium readable by a machine. For example, the processor of the machine may call at least one of the one or more instructions stored from the storage medium and execute it. This enables the machine to operate to perform at least one function according to the at least one called instruction. The one or more instructions may include code generated by a compiler or code that can be executed by an interpreter. The storage medium readable by a machine may be provided in the form of a non-transitory storage medium. Here, "non-transitory" simply means that the storage medium is a tangible device and does not contain a signal (e.g., electromagnetic waves), and this term does not distinguish between cases where data is stored semi-permanently and cases where it is stored temporarily in the storage medium.

[0134] According to one embodiment, the method according to the various embodiments disclosed herein may be provided by being included in a computer program product. The computer program product may be traded between a seller and a buyer as a product. The computer program product may be distributed in the form of a device-readable storage medium (e.g., compact disc read-only memory (CD-ROM)), or distributed online (e.g., download or upload) through an application store (e.g., Play Store™) or directly between two user devices (e.g., smartphones). In the case of online distribution, at least a portion of the computer program product may be temporarily stored or temporarily created on a device-readable storage medium, such as the memory of a manufacturer's server, an application store's server, or a relay server.

[0135] According to various embodiments, each component (e.g., module or program) of the components described above may include a singular or multiple entities, and some of the multiple entities may be separated and placed in other components. According to various embodiments, one or more of the components or operations among the aforementioned components may be omitted, or one or more other components or operations may be added. Generally or additionally, multiple components (e.g., module or program) may be integrated into a single component. In this case, the integrated component may perform one or more functions of each of the multiple components in the same or similar manner as those performed by the corresponding component among the multiple components prior to integration. According to various embodiments, operations performed by the module, program, or other components may be executed sequentially, in parallel, iteratively, or heuristically, or one or more of the operations may be executed in a different order, omitted, or one or more other operations may be added.

Claims

Claim 1 A method performed by a user equipment (UE) in a non-terrestrial network (NTN) communication system to reduce scheduling delay of said UE comprises: acquiring resource map information related to available contention-based resources from a base station (BS); said available contention-based resources having a resource structure based on NTN standards and including scheduling request resources, contention-based control resources, and contention-based data resources; and, based on said acquired resource map information, transmitting a scheduling request message, control information, and at least a portion of uplink data to said base station; and determining whether said at least a portion of the uplink data has been successfully transmitted; wherein said control information includes information regarding contention-based resources used to transmit said at least a portion of the uplink data. Claim 2 A method according to claim 1, further comprising the step of determining at least one of the location, area, and size of the competition-based resource used based on the acquired resource map information. Claim 3 A method according to claim 1, further comprising: a step of comparing the size of the uplink data with the size of the available contention-based resource; and a step of transmitting a buffer status report (BSR) to the base station when the size of the uplink data is greater than the size of the available contention-based resource. Claim 4 A method according to claim 1, further comprising: a step of determining whether at least a message related to the scheduling request message is received from the base station within a specified time; and a step of determining that the transmission of at least a portion of the uplink data has failed based on the determination that the message was not received from the base station within the specified time. Claim 5 A method according to claim 4, further comprising: a step of reacquiring resource map information related to available contention-based resources from the base station; and a step of retransmitting the scheduling request message, the at least part of the uplink data, and the control information to the base station based on the reacquired resource map information. Claim 6 A method according to claim 1, further comprising: a step of receiving a resource corresponding to the scheduling request message from a base station within a specified time; and a step of determining that the transmission of at least a portion of the uplink data has failed and transmitting a buffer status report (BSR) to the base station when the size of the allocated resource is less than or equal to a specified level. Claim 7 The method of claim 1 further comprises the step of determining that the transmission of at least a portion of the uplink data has been successful when an acknowledgment (ACK) corresponding to the scheduling request message is received from a base station within a specified time. Claim 8 A method according to claim 7, further comprising: a step of receiving a resource corresponding to the scheduling request message from a base station within the specified time; and a step of transmitting the remainder of the uplink data, excluding at least a portion thereof, to the base station using the allocated resource. Claim 9 The method of claim 1 further comprises: a step of determining that the transmission of at least a portion of the uplink data has failed when an acknowledgment (ACK) corresponding to the scheduling request message is not received from a base station within a specified time and a resource corresponding to the scheduling request message is allocated; and a step of transmitting the uplink data to the base station using the allocated resource. Claim 10 A method according to claim 1, wherein the robustness of the transmission of the scheduling request message is higher than the robustness of the transmission of the control information, and the robustness of the transmission of the control information is higher than the robustness of the transmission of at least a portion of the uplink data. Claim 11 A method performed by a base station (BS) to reduce the scheduling delay of user equipment (UE) in a non-terrestrial network (NTN) communication system, comprising: transmitting resource map information related to available contention-based resources to said UE; said available contention-based resources having a resource structure based on NTN standards and including a scheduling request resource, a contention-based control resource, and a contention-based data resource; receiving a scheduling request message from said UE; determining whether to receive control information and at least a portion of uplink data, respectively; and determining whether to allocate resources to said UE based at least on whether to receive the control information and whether to receive the at least portion of the uplink data, wherein the control information includes information about the contention-based resources that said UE has decided to use to transmit the at least portion of the uplink data. Claim 12 A method according to claim 11, further comprising the step of transmitting an acknowledgment (ACK) corresponding to the scheduling request message to the UE when it is determined that at least a portion of the control information and the uplink data has been received. Claim 13 A method according to claim 12, further comprising the step of determining to allocate resources to the UE based on the received buffer status report (BSR) when the received control information includes a buffer status report (BSR). Claim 14 A method according to claim 12, further comprising the step of determining not to allocate resources to the UE if the received control information does not include a buffer status report. Claim 15 A method according to claim 11, further comprising the step of determining to allocate resources to the UE when it is determined that the control information has been received and when it is determined that at least a portion of the uplink data has not been received. Claim 16 In claim 15, a method wherein, when the received control information includes a buffer status report (BSR), the size of the resource allocated to the UE is determined based on the information regarding the contention-based resource included in the control information and the buffer status report. Claim 17 In claim 15, a method wherein, when the received control information does not include a buffer status report (BSR), the size of the resource allocated to the UE is determined based on information regarding the contention-based resource included in the control information. Claim 18 For reducing scheduling delay of user equipment (UE) in a non-terrestrial network (NTN) communication system, the UE comprises: at least one transceiver; and at least one processor coupled to communicate with the at least one transceiver. and at least one memory coupled to communicate with the at least one processor and storing instructions that can be executed by the at least one processor; wherein the instructions cause the UE to perform the following operations when executed by the at least one processor: acquiring resource map information related to available contention-based resources from a base station (BS), wherein the available contention-based resources have a resource structure based on NTN standards and include a scheduling request resource, a contention-based control resource, and a contention-based data resource; wherein, based on the acquired resource map information, the UE transmits a scheduling request message, control information, and at least a portion of uplink data to the base station; and determines whether the at least portion of the uplink data has been successfully transmitted, wherein the control information includes information regarding the contention-based resources used to transmit the at least portion of the uplink data. Claim 19 In claim 18, the instructions cause the UE to perform the following operations when executed by the at least one processor: the UE determining at least one of the location, area, and size of the contention-based resource used based on the acquired resource map information. Claim 20 In claim 18, the instructions, when executed by the at least one processor, cause the UE to perform the following operations further: comparing the size of the uplink data and the size of the available contention-based resource, and if the size of the uplink data is greater than the size of the available contention-based resource, transmitting a buffer status report (BSR) to the base station.

Images