Terminal device for efficiently changing communication parameters according to traffic characteristics

Abstract

A terminal device recognizes a first packet and an end packet when a frame generated by an application executed by the terminal device is divided into a plurality of packets and transmitted, measures the reception time of the first packet, calculates a frame period and fluctuations in the frame period on the basis of the measurement result, and reports the calculation result to a base station device. A terminal device acquires, from a base station device, information relating to a frame to be reported.

Description

Technical Field

[0001] The present invention relates to a technique for changing communication parameters in a cellular communication system. Background Art

[0002] The cellular communication system may use functions for efficiently communicating by periodically allocating radio resources, such as a configured grant (CG) function and a semi-persistent scheduling (SPS) function. In the version 17 standard of , a technology has been proposed that improves communication capacity by optimizing parameters of the CG function and the SPS function according to the business model of the application (Non-Patent Document 1).

[0003] Prior art literature

[0004] Non-patent literature

[0005] Non-patent document 1: 3GPP written document, RP-220285, March 2022 Summary of the invention

[0006] Problem that the invention aims to solve

[0007] In actual application business, it is assumed that communications in various business modes will be performed simultaneously.

[0008] Means used to solve problems

[0009] The present invention provides an appropriate communication control technology suitable for such business mode under the above circumstances.

[0010] According to one aspect of the present invention, a terminal device comprises: an identification unit that identifies a head packet and a tail packet when a frame generated by an application executed by the terminal device is divided into multiple packets and sent; a measuring unit that measures the reception time of the head packet identified by the identification unit; a calculation unit that calculates a frame period and a fluctuation of the frame period based on a measurement result based on the measuring unit; a reporting unit that reports the calculation result to a base station device; and an acquisition unit that acquires information related to a frame that should be a report object based on the reporting unit from the base station device.

[0011] According to one aspect of the present invention, a terminal device includes: a sending unit, which sends uplink data through a configured authorization; an acquisition unit, which acquires the configured authorization period and wireless resource block allocation information from a base station device through layer 3 signaling; a receiving unit, which receives a change indication of the configured authorization period and resource block allocation information from the base station device through layer 1 or layer 2 signaling; and a request unit, which requests the base station device to change the allocation timing of the wireless resource block.

[0012] Effects of the Invention

[0013] According to the present invention, appropriate communication control suitable for the business model can be performed.

[0014] Other features and advantages of the present invention will be apparent from the following description in conjunction with the accompanying drawings. Note that throughout the accompanying drawings, the same reference numerals represent the same or similar components. BRIEF DESCRIPTION OF THE DRAWINGS

[0015] The accompanying drawings, which are incorporated in and constitute a part of the specification, illustrate embodiments of the present invention and, together with the description, serve to explain the principles of the present invention.

[0016] Figure 1 is a diagram showing an exemplary configuration of a wireless communication network.

[0017] Figure 2 is a diagram showing exemplary changes in SPS parameters.

[0018] Figure 3 is a diagram showing exemplary changes in CG parameters.

[0019] Figure 4A is a diagram showing exemplary changes to CDRX parameters.

[0020] Figure 4B is a diagram showing exemplary changes to CDRX parameters.

[0021] Figure 5 is a diagram showing exemplary control of multiple DRX parameters.

[0022] Figure 6 is a diagram showing an exemplary hardware configuration of the apparatus.

[0023] Figure 7 is a diagram showing an exemplary functional configuration of a base station apparatus.

[0024] Figure 8 is a diagram showing an exemplary functional configuration of a terminal device.

[0025] Fig. 9 is a diagram illustrating an exemplary flow of a process performed in a wireless communication network. DETAILED DESCRIPTION

[0026] Hereinafter, the embodiments will be described in detail with reference to the accompanying drawings. Note that the following embodiments are not intended to limit the scope of the claimed invention, nor are they intended to limit the invention requiring the combination of all the features described in the embodiments. Two or more of the multiple features described in the embodiments may be appropriately combined. In addition, the same reference numerals are given to the same or similar configurations, and their redundant descriptions are omitted.

[0027] (System Configuration)

[0028] Figure 1 An exemplary configuration of a wireless communication system according to an embodiment of the present invention is shown. The wireless communication system may be, for example, compliant with the Third Generation Partnership Project The wireless communication system is a wireless communication system of the fifth generation (5G) cellular communication standard. The wireless communication system includes, for example, a base station device 101, a terminal device 111, a core network device 121, and an application server 131. In one example, the terminal device 111 exchanges user data related to the application service with the application server 131 via the base station device 101 and the core network device 121.

[0029] Application business is a business generated by an application and needs to be sent to another device, or received from another device for use by the application, and can take various forms. For example, data is generated and sent / received by various applications, such as applications that implement video streaming, cloud games, tactile communication, tactile communication, and metaverse. Here, application business can be interpreted as a collection of multiple data fragments, which are different from each other in terms of characteristics and data occurrence cycles. For example, in the case where the application is a game application, the application business contains video information, sound information, operation information, etc. In addition, for example, in the case where the application is a video streaming application, the application business can be defined as a collection of video information and sound information. In addition, video information can be classified into different types of video frames, such as I pictures (I frames), P pictures (P frames), and B pictures (B frames), which are constructed as a group of pictures (GOP). Note that I frames, P frames, and B frames are exchanged at different cycles (for example, between the terminal device 111 and the application server 131).

[0030] The above-mentioned multiple types of data to be exchanged included in the application service may include delay-tolerant data and delay-intolerant data. For example, among the above-mentioned I frames, P frames, and B frames, the I frame is a frame that has no dependency on other frames and can be decoded and generate images independently, while the P frame is obtained by encoding the difference from the data predicted from the previous frame, and the B frame is obtained by encoding the difference from the data predicted from the previous frame and the forward frame; therefore, the P frame and the B frame depend on other frames. That is, since the accurate decoding of the P frame and the B frame is achieved by accurately receiving the I frame without delay, it can be said that the I frame is delay-intolerant data. On the other hand, for P frames and B frames, it is not always the case that delays cannot be tolerated. With respect to this application service, it is necessary to periodically allocate wireless resources in conjunction with data that is intolerant of delays, thereby preventing the occurrence of delays. At the same time, although the parameters of the CG function and the SPS function can be set so that wireless resources are also periodically allocated in conjunction with delay-tolerant data, this situation may result in unnecessary periodic wireless resource assurance. Therefore, this may cause a situation in which wireless resources have been secured for data transmission that does not necessarily require wireless resources to be secured within one cycle, resulting in a shortage of wireless resources that can be allocated to delay-intolerant data requested to be transmitted by another terminal device.

[0031] In an embodiment of the present invention, in view of the above-mentioned problem, when it is envisaged that various business modes of communication are carried out simultaneously, a business mode related to data that significantly affects the operation of the application is specified, such as the above-mentioned I frame (key frame). Then, resource allocation is performed so that the transmission / reception delay, transmission / reception cycle, jitter (periodic fluctuation), etc. are kept at or below a specified value. A technology that can achieve such business mode specification and allocation of wireless resources is described below. Note that although the following may mention exemplary cases where video frame data segments corresponding to I frames, P frames, and B frames, respectively, are exchanged as application services, these are merely examples of data, and the following discussion is applicable to application services consisting of a combination of various forms of data.

[0032] In an embodiment of the present invention, for example, the core network device 121 determines the frame type for which the service mode is to be specified. In this case, the core network device 121 notifies the base station device 101 of information related to the frame type for which the service mode is to be specified (for example, at least one of the I frame, the P frame, and the B frame). In addition, at this time, the core network device 121 may notify the base station device 101 of frame characteristic information indicating the characteristics of the frame for which the service mode is to be specified. The frame characteristic information contains, for example, at least one of the frame rate (frames per second or fps), the data rate (Mbps), the quality of service (QoS), the priority, the maximum value of the transmission delay of the packet (packet delay budget), the packet error rate (packet error loss rate), the number of packets per frame, the number of PDUs, etc. In addition, the notification of the above information related to the frame type for which the service mode is to be specified and the associated frame characteristic information may be provided in the downlink direction (application server 131 → terminal device 111) and the uplink direction (terminal device 111 → application server 131), respectively. In this way, for example, when using a TDD communication method in which uplink transmission is a bottleneck, it is possible to optimize the parameters of the CG function, etc. by specifying a service mode related to uplink communication in the signal transmission direction from the terminal device 111 to the base station device 101. In addition, in order to specify the service mode in the uplink direction (terminal device 111 → application server 131), the terminal device 111 needs to obtain information related to the frame type of a specific object and the associated frame characteristic information. In this case, the terminal device 111 obtains the necessary information from, for example, the base station device 101 or the core network device 121.

[0033] The frame sent from the application server 131 is sent to the terminal device 111 via the core network device 121 and the base station device 101. Each time the base station device 101 receives a frame for which a service mode is to be specified from the core network device 121, it records the reception time of the frame and the data size of the received frame. The base station device 101 calculates the period and jitter (periodic fluctuation) of the received frame based on the recorded reception time. The base station device 101 can then use the information of the calculated frame period to determine the parameters of the SPS and CG. At this time, in the case where there are multiple frame periods and frame data sizes, the base station device 101 can apply statistical processing to these multiple frame periods and frame data sizes. For example, the base station device 101 can specify the mode or mean and standard deviation of multiple frame periods, use the mode or mean as the frame period for the data for which a service mode is to be specified, and use the standard deviation as the jitter (periodic fluctuation) of the data for which a service mode is to be specified.

[0034] As an embodiment, different PDU sessions can be established between the base station device 101 and the terminal device 111 for different frame types. In this case, the base station device 101 counts the reception time of the frame received in each PDU session and the size of the received frame. This allows the base station device 101 to easily distinguish multiple types of frames from each other using the PDU session, and count the frame reception time and frame size of each frame type. In addition, as another embodiment, different QoS flows can be established for different frame types within the same PDU session. In this case, the base station device 101 counts the reception time of the frame received for each QoS flow and the size of the received frame. This allows the base station device 101 to easily distinguish multiple types of frames from each other using the QoS flow, and count the frame reception time and frame size of each frame type. In addition, user data fragments of multiple types of frames can also be exchanged within the same QoS flow. In this case, in the device processing the upper layer, such as the application server 131 and the core network device 121, an identifier for identifying the frame type is attached to the user data fragment. Then, one of the functional units constituting the base station apparatus 101, such as PDCP, RLC, and MAC, identifies the frame type based on the attached identifier, and counts the frame reception time and the size of the received frame for each frame type. In addition, different network slices can be assigned to different frame types. In this case, the data exchanged in the PDU session used by the network slice corresponding to the type of frame to be counted can be counted. Note that in the case where one network slice is implemented by multiple PDU sessions, the data fragments exchanged in all PDU sessions associated with the network slice can be counted. In the above embodiment, the application server 131, the core network apparatus 121, and the base station apparatus 101 can be an application function (AF), a user plane function (UPF), and a gNB, respectively.

[0035] The frame received by the base station device 101 from the core network device 121 may be burst data that is transmitted / received after dividing one frame into a plurality of packets. In this case, the base station device 101 needs to identify which packet is the packet at the beginning of the frame (the packet received first), and which packet is the packet at the end of the frame (the packet received last). To this end, for example, the core network device 121 may determine the frame type, whether the packet is the packet at the beginning of the frame, and whether the packet is the packet at the end of the frame based on the information of the RTP header of each packet. As a result of this determination, for example, the core network device 121 may attach identifiers to the packet at the beginning and the packet at the end of each frame, respectively. The base station device 101 may determine whether the packet is the packet at the beginning of the frame or the packet at the end of the frame based on the attached identifier. In addition, in another embodiment, the core network device 121 may notify the base station device 101 of the number of packets per frame; in this case, the base station device 101 may specify the packet at the beginning and the packet at the end based on the information of the number of packets per frame notified. Base station apparatus 101 can specify the frame period by, for example, counting only the reception time of the first packet. In addition, when the number of packets per frame changes dynamically, core network apparatus 121 can notify base station apparatus 101 of the number of packets per frame when such a change is recognized.

[0036] In one embodiment, the base station apparatus 101 instructs the terminal apparatus 111 to specify a service mode and measure a frame period. In this case, the base station apparatus 101 may notify the terminal apparatus 111 of the frame type for which the service mode is to be specified. In this case, the base station apparatus 101 may also notify the terminal apparatus 111 of the above-mentioned frame characteristic information, such as the frame rate (number of frames per second or fps) of the service mode for specifying the video frame. In addition, the base station apparatus 101 may notify the terminal apparatus 111 of information related to the period and time period of the report on the specified service mode and the format and style of the report. Based on the notified information, the terminal apparatus 111 measures the service mode and frame period of the frame of the specified type of the object in the frame to be sent to the base station apparatus 101. Then, the terminal apparatus 111 may report the measurement result to the base station apparatus 101 using the format and style specified by the base station apparatus 101 within the period and time period specified by the base station apparatus 101. Note that the base station apparatus 101 may instruct the terminal apparatus 111 to perform statistical processing on the measurement data of multiple frame periods that have been measured. For example, base station apparatus 101 sends an instruction to terminal apparatus 111 to report statistical information of the frame period, such as the average, maximum, minimum, mode, and standard deviation. In addition, base station apparatus 101 may report all measured data of the measured frame period, or partial data matching a specific condition.

[0037] In addition, in one example, the application server 131 may notify the base station device 101 via the core network device 121 of the acceptable value of the jitter (period fluctuation) of the data transmitted in each frame and the maximum value of the transmission delay of the packet (packet delay budget). In this case, the base station device 101 compares the standard deviation and jitter (frame period fluctuation) of the frame period that have been actually measured with the acceptable value of the acceptable jitter notified from the core network device 121, and notifies the core network device 121 of the comparison result. Note that the base station device 101 may notify the core network device 121 of the standard deviation and jitter (frame period fluctuation) of the frame period that have been actually measured. In this case, the comparison between the measured value and the acceptable value may be performed by the core network device 121 and the application server 131. When the line required for the application is established, the application server 131 may notify the base station device 101 via the core network device 121 of the acceptable value of the jitter and the maximum value of the transmission delay of the packet. In this case, base station apparatus 101 can determine whether the communication quality required for the line required by the application can be ensured based on jitter and delay actually measured in the past, and notify core network apparatus 121 and application server 131 of the determination result.

[0038] In addition, when establishing a line required for an application, the application server 131 may notify the terminal device 111 of an acceptable value of jitter and a maximum value of a transmission delay of a packet via the core network device 121 and the base station device 101. In this case, the terminal device 111 may determine whether the communication quality required for the line required for the application can be guaranteed based on the jitter and delay that have been actually measured in the past, and notify the base station device 101, the core network device 121, and the application server 131 of the determination result. Note that the frame period may be measured in a plurality of internal function blocks within the base station device 101 and the terminal device 111, such as the service data adaptation protocol (SDAP), the packet data convergence protocol (PDCP), the radio link control (RLC), and the media access control (MAC). In addition, jitter (frame period fluctuation) may be similarly measured in a plurality of internal function blocks within the base station device 101 and the terminal device 111. In addition, the measured value and the acceptable value of the transmission delay of the packet may also vary depending on how the transmission delay is defined in each of the base station device 101 and the terminal device 111. As an example, the transmission delay can be defined as the time period from when the service data adaptation protocol (SDAP) functional block of the base station device 101 has received a frame from the core network device 121 to when the PDSCH containing the frame starts to be transmitted. However, this is just an example, and other definitions are naturally possible. In view of this, in order to allow the core network device 121, the application server 131 and the base station device 101 or the terminal device 111 to use the same definition of frame period, jitter (frame period fluctuation) and transmission delay, the core network device 121 and the application server 131 can notify the base station device 101 and the terminal device 111 of information related to the definition of frame period, jitter amount (frame period variation) and transmission delay.

[0039] In an embodiment of the present invention, when using semi-persistent scheduling (SPS), the base station apparatus 101 periodically allocates wireless resources for transmitting frames of downlink to the terminal apparatus 111 based on the service mode and frame period specified by itself. For example, in each frame period, the base station apparatus 101 can configure the setting of resource blocks sufficient to be allocated for the downlink to transmit data constituting one frame to the terminal apparatus 111. Semi-persistent scheduling (SPS) for periodically allocating resources is performed using signaling in layer 3 (RRC reconfiguration message), and the resource allocation period for the downlink can be set based on the periodicity contained in the SPS-configuration in the RRC reconfiguration information. Note that in the case where the frame period changes during communication, the base station apparatus 101 can change the period of resource allocation using signaling in layer 1 or layer 2. In addition, the base station apparatus 101 can pre-set multiple periods using signaling in layer 3, and issue an indication of the period actually used using signaling in layer 1 or layer 2. In addition, the base station device 101 can determine the resource blocks to be allocated to the terminal device 111 according to the specified service mode, and issue an instruction to the terminal device 111 using the downlink control information (DCI) included in the physical downlink control channel (PDCCH). It is assumed here that Figure 2 As indicated by "1" and "2" in the figure, 5ms and 20ms are set as the first SPS period and the second SPS period respectively through layer 3 signaling. Note that "ms" means "milliseconds". Figure 2 A subframe in corresponds to 1ms. Here we assume that Figure 2 As indicated by the "1" in , while the SPS period of 5 ms is used, the period of the application service has changed to 20 ms. In this case, using the DCI sent via the PDCCH, the base station apparatus 101 can send a DCI to the terminal apparatus 111 for changing the SPS period from the first period of 5 ms to Figure 2 In the example of FIG. 1 , an indication of a second period of 20 ms indicated by the "2" in FIG. 1 is provided. In addition, in the case where the frame sent to the terminal device 111 is burst data that is sent after dividing the frame into a plurality of packets, the base station device 101 may issue an indication for starting periodic resource allocation based on the transmission period of the packet at the beginning of the frame, that is, enabling semi-persistent scheduling (SPS). In addition, the base station device 101 may issue an indication for ending periodic resource allocation based on the transmission timing of the packet at the end of the frame, that is, disabling semi-persistent scheduling (SPS). Note that although the above description of the embodiment has been provided with respect to an example of periodically sending DCI, in the case where the size of the frames sent in each period is the same or falls within a specific size range, the size and position of the resource blocks periodically allocated for sending may be the same; in this case, the sending of DCI may be omitted.

[0040] In another embodiment, the base station device 101 measures the time period required from when it has received a frame from the core network device 121 to when the frame is actually transmitted to the terminal device 111. Figure 2 In the examples of "1" and "2" in , when SFN = 0 or 2 and subframe = 1, the base station apparatus 101 receives a frame to be transmitted to the terminal apparatus 111 from the core network apparatus 121. Then, when subframe = 5 in the same SFN, the base station apparatus 101 transmits control information for downlink data transmission to the terminal apparatus 111 via the PDCCH, and transmits downlink data of the frame to the terminal apparatus 111 via the physical downlink shared channel (PDSCH) in the time period of subframe = 6 to 8 in the same SFN. In this case, 4 ms are required from when the base station apparatus 101 receives the frame from the core network apparatus 121 to when the frame starts to be transmitted to the terminal apparatus 111. The base station apparatus 101 changes the timing of the transmission of downlink data to the terminal apparatus 111 so that the measurement time period required before the start of transmission is maintained at or below the maximum value of the transmission delay of the packet notified from the core network apparatus 121 (packet delay budget) . For example, the base station apparatus 101 changes the timing of downlink data transmission by changing the transmission timing of downlink control information (DCI) included in the physical downlink control channel (PDCCH). Figure 2 In the state of communicating with "2" in the figure, the packet transmission delay is defined as the time period from the completion of the arrival of the application data to the start of the transmission of the PDSCH, and the maximum value of the packet transmission delay (packet delay budget) is 2ms. In this case, Figure 2 As indicated by "3" in , after transmitting the PDSCH at SFN = 0 and subframe = 8, the base station apparatus 101 shifts the next transmission timing of the PDCCH from the timing at SFN = 2 and subframe = 5 to the timing at SFN = 2 and subframe = 2. The length of a subframe is 1 ms; therefore, the delay period can be shortened to 1 ms, which is equal to or shorter than the packet delay budget of 2 ms. In addition, although Figure 2The transmission timing of the PDCCH is adjusted in the data transmission, but it is not intended to be limited by this. For example, the base station device 101 can shift the transmission timing of the data by transmitting the PDCCH at a timing of SFN=1 and subframe=5, and setting the transmission timing of the PDSCH specified by the PDCCH to a timing of SFN=2 and subframe=2 to 4. This can also shorten the delay time period to a packet delay budget of 2ms or less. In addition, in the case where the data sent to the terminal device 111 is burst data, when semi-persistent scheduling (SPS) is enabled, the base station device 101 can use downlink control information (DCI) to issue an indication of the transmission timing of the PDCCH and PDSCH, which is an indication for enabling semi-persistent scheduling (SPS). In this case, an indication for changing the timing can be issued, thereby minimizing the measurement time period required before transmission. Note that although the packet transmission delay has been described above as the time period from the completion of the arrival of application data to the start of transmission of PDSCH, the packet transmission delay may be defined in other forms; for example, the packet transmission delay may be from the start of the arrival of application data to the completion of transmission of PDSCH, or may be from the completion of the arrival of application data to the start of transmission of PDCCH.

[0041] In addition, in one embodiment, based on the traffic pattern and frame period reported from the terminal device 111, the base station device 101 can use the configured grant (CG) to periodically allocate wireless resources for the terminal device 111 to send uplink frames to the base station device 101. For example, in each frame period, the base station device 101 can configure the setting of resource blocks sufficient to send data constituting one frame to the terminal device 111 for uplink. The base station device 101 can use the signaling in layer 3 (RRC reconfiguration message) to configure the setting of the CG for periodic resource allocation. In this case, the setting related to the uplink resource block can be configured using the timeDomainOffset, timeDomainAllocation, and frequencyDomainAllocation included in the rrc ConfiguredPlunkGrant in the rrc reconfiguration message. In addition, the period of resource allocation can be set using the periodicity included in the ConfiguredGrantConfig in the RRC reconfiguration message. Note that in the case where the period and size of the frame are changed during communication, the base station device 101 can use the signaling in layer 1 or layer 2 to change the period of resource allocation and the resource blocks to be allocated. In addition, the base station apparatus 101 may pre-set multiple resource allocation cycles and multiple patterns of allocated resource blocks using signaling in layer 3, and issue an instruction about the settings to be actually used using signaling in layer 1 or layer 2. It is assumed here that Figure 3As indicated by "1" and "2" in the figure, 5ms and 20ms are set as the first CG period and the second CG period respectively through layer 3 signaling. Figure 3 In , a subframe also corresponds to 1ms. Here we assume that Figure 3 Indicated by the "1" in, for example, while a CG period of 5 ms is used, the period of the application service has become 20 ms. In this case, for example, when SFN = 0 and subframe = 5, in response to the reception of data (physical uplink shared channel (PUSCH)), when SFN = 0 and subframe = 6, the base station device 101 sends a PDCCH containing a DCI indicating an ACK / NACK to the PUSCH to the terminal device 111. At this time, using the DCI, the base station device 101 can send information to the terminal device 111 indicating that the CG period is changed from a first period of 5 ms to a second period of 20 ms. In addition, in the case where the frame sent by the terminal device 111 is burst data sent after dividing a frame into multiple packets, the base station device 101 can issue an indication for starting periodic resource allocation and enabling CG based on the transmission period of the packet at the beginning of the frame. Then, the base station device 101 can issue an indication for ending periodic resource allocation and disabling CG based on the transmission timing of the packet at the end of the frame.

[0042] Furthermore, in another embodiment, the terminal device 111 measures the time period required from when the occurrence of a frame to be transmitted to the base station device 101 is recognized to when the frame is actually transmitted to the base station device 101. For example, the terminal device 111 may request the base station device 101 to correct the transmission timing of the uplink frame so that the measurement time period required before transmission is maintained at or below the maximum value of the transmission delay of the packet notified from the core network device 121 (packet delay budget). In this case, the terminal device 111 may calculate a correction value so that the standby time period from the recognition of the occurrence of the transmission frame to the actual transmission of the frame becomes the shortest, or is maintained at or below the packet delay budget, and notify the base station device 101 of the correction value. The base station device 101 changes the allocation timing of the resource block based on the correction value received from the terminal device 111. The base station apparatus 101 can instruct the terminal apparatus 111 to change the transmission timing by, for example, specifying a positive / negative offset (expressed by frame(s) or symbol(s)) or a system frame number (SFN) from the current transmission timing using signaling in layer 1 or layer 2. Figure 3 In the case of communication with "2" in the packet delay budget is 2ms. Figure 3As indicated by "3" in the figure, the terminal device 111 sends a request for timing correction to the base station device 101 using a correction value that has been specified (e.g., -3ms), so that when signaling in layer 1 or layer 2 is used, when SFN=0 and subframe=5, the delay in the transmission timing of the PUSCH is equal to or shorter than 2ms. Based on the correction value included in the request, the base station device 101 shifts the transmission timing of the PUSCH from the timing of SFN=2 and subframe=5 to the timing of SFN=2 and subframe=2. At this time, the base station device 101 can return information to the terminal device indicating whether the correction value from the terminal device 111 will be complied with. In addition, in the case where the base station device 101 uses a value different from the correction value notified from the terminal device 111 for correction, the base station device 101 can notify the terminal device 111 of the value. In addition, the terminal device 111 may report the standby time period from recognizing the occurrence of a transmission frame to actually transmitting the frame to the base station device 101, and the base station device 101 may determine a correction value so that the standby time period becomes the shortest or remains at or below the packet delay budget, and change the transmission timing. Figure 3In the examples of "1" and "2" in , the terminal device 111 can notify the base station device 101 of a standby time period of 3ms, and the base station device 101 can determine the shift amount (e.g., 2ms or 3ms) of the allocation timing of the PUSCH by comparing the standby time period with the value of the packet delay budget (2ms) maintained in itself. Then, the base station device 101 can shift the allocation timing of the PUSCH by the determined shift amount, and also notify the terminal device 111 of information including the shift in the PUSCH allocation timing, the value indicating the shift amount, etc. Note that, for example, the base station device 101 can notify the terminal device 111 of this information using a PDCCH including a DCI for sending ACK / NACK to the PUSCH received at the timing of SFN=0 and subframe=5. Using the above method, the allocation timing of the PUSCH can be changed from the timing of SFN=2 and subframe=5 to the timing of SFN=2 and subframe=2, and the PUSCH can be sent at the timing that satisfies the packet delay budget (=2ms). Note that the above embodiment is described under the assumption that the terminal device 111 measures the time period from the recognition of the occurrence of a frame to be sent to the base station device 101 to the actual transmission of the frame to the base station device 101 as a transmission delay. In practice, this can be performed as a result of the terminal device 111 recognizing the occurrence of a frame to be sent in multiple internal functional blocks, such as the service data adaptation protocol (SDAP), the packet data convergence protocol (PDCP), the radio link control (RLC), and the media access control (MAC). In addition, "the time to actually send the frame" can be interpreted in a variety of ways: the time to the start of PDSCH transmission of the frame, the time to the completion of PDSCH transmission of the frame, or the time to receive the HARQ-ACK of the PDSCH of the frame. Therefore, the base station device 101 can notify the terminal device 111 of information related to the definition of the transmission delay, so that the terminal device 111 and the base station device 101 can recognize the same definition of the transmission delay.

[0043] In addition, in a case where a large number of terminal devices are connected to the base station device 101 and it is difficult for the base station device 101 to periodically allocate wireless resources to the terminal device 111 using a specific application using CG, dynamic allocation of wireless resources can be applied to the terminal device 101. In the dynamic allocation of wireless resources, before sending uplink data, the terminal device 111 uses a buffer status report (BSR) to notify the base station device 101 of the transmission data size and the transmission buffer size. Then, the base station device 101 allocates wireless resources for the uplink used by the terminal device 111 based on the notified transmission buffer size. The BSR is configured to use one of the values ​​defined in the two types of buffer size tables specified by the 3GPP standard to inform the transmission buffer size. In contrast, in one embodiment of the present invention, another customized buffer size table for the frame data size specified by the base station device 101 can be used to provide notification about the transmission buffer size via the BSR. For example, in the case where the buffer size table has 5 bits, the minimum value of the frame data size measured by the base station apparatus 101 can be determined as the minimum value of the buffer size table, and the value obtained by dividing the difference between the maximum value and the minimum value of the buffer size table by 25-1=31 is used as the amplitude step indicating the buffer size. In this case, the base station apparatus 101 notifies the terminal apparatus 111 of the number of bits in the buffer size table and the minimum value and the maximum value of the buffer size table. Then, based on the information obtained from the base station apparatus 101, the terminal apparatus 111 specifies the buffer size table and uses the buffer size table to encode the transmission buffer size when the BSR is transmitted. In this way, the buffer size table can be shared between the base station apparatus 101 and the terminal apparatus 111, and the base station apparatus 101 can decode the transmission buffer size indicated by the received BSR based on the buffer size table shared with the terminal apparatus 111. The base station apparatus 101 can notify the terminal apparatus 111 of information related to multiple buffer size tables. In this case, the terminal device 111 may notify the base station device 101 which of the notified multiple buffer size tables has been used to indicate the transmission buffer size when the BSR is transmitted. In addition, when the BSR is transmitted, the terminal device 111 may notify the base station device 101 of the standby time period from when the terminal device 111 recognizes the occurrence of transmitting a frame to the base station device 101 to when the frame is actually transmitted together with the transmission buffer size. Note that although an example in which the base station device 101 sets a buffer size table for BSR has been described above, it is not intended to be limiting. That is, the terminal device 111 may request the base station device 101 to set the buffer size table. In this case, the terminal device 111 may notify the base station device 101 of the number of bits in the buffer size table and the minimum and maximum values ​​of the buffer size table.Furthermore, at this time, the terminal apparatus 111 may notify the base station apparatus 101 of the number of bits in the buffer size table and the median value of the buffer size table, and the buffer size indicated by one bit.

[0044] In addition, in one embodiment, the base station device 101 may change parameters related to the connected discontinuous reception (CDRX) based on the specified service mode and frame period. As an example, an exemplary case will be used to describe the method of changing the parameters. In the exemplary case, Figure 4A As indicated by "1" in the figure, CDRX operates under shortDRX-Cycle (short DRX cycle) = 5ms, onDurationTimer (a timer for controlling DRX ON for a period of time) = 2ms, and drx-inactivityTimer (a DRX inactivity timer activated after receiving PDCCH to keep DRX ON for a certain period of time) = 3ms. The base station device 101 identifies the frame cycle by measuring the time when the frame is received from the core network device 121. According to Figure 4A , the transmission frames to the terminal device 111 appear at 1ms, 21ms, and 41ms (subframe = 1 under SFN = 0, 2, or 4), and the base station device 101 recognizes that the frames appear at a period of 20ms. For example, the base station device 101 can change the shortDRX-Cycle from 5ms to 16ms based on the frame period, such as Figure 4A In addition, the base station device 101 can reset drx SlotOffset = 16ms, such as Figure 4BIndicated by the "3" in . In addition, the base station device 101 can change the parameters by setting drx-inactivityTimer and shortDRX-Cycle to 0ms and 20ms, respectively. When SFN=0 and subframe=5, the base station device 101 can use, for example, DCI sent via PDCCH to instruct the terminal device 111 to change the parameters. In addition, the base station device 101 can use the signaling in Layer 3 to pre-set multiple setting values ​​for shortDRX-Cycle, drx-SlotOffset and drx-inactivityTimer, and use DCI to issue an indication of the setting value actually to be used. Note that in the case where the specified service mode is not an integer multiple of the subframe, multiple shortDRX-Cycles can be repeated a specific number of times by setting shortDRX-Cycle=16ms, shortDRX-Cycle=16ms and shortDRX-Cycle=17ms. In this case, the DRX mode can be set on the terminal device 111 using the first DRX cycle, the number of times the first DRX cycle is repeated, the second DRX cycle, and the number of times the second DRX cycle is repeated. Note that in this case, an indication of the number of repetitions of the DRX cycle can be issued using DCI. In addition, multiple values ​​can be set for multiple drx-SlotOffset and drx-inactivityTimer instead of shortDRX-Cycle, and each value can be repeatedly used corresponding to a specific number of repetitions.

[0045] In addition, the base station apparatus 101 may notify the terminal apparatus of an offset value for adjusting the timing of DRX ON and DRX OFF, thereby minimizing the transmission delay of the downlink frame to the terminal apparatus 111 caused by the DRX OFF period. Figure 4A and Figure 4B In the example of , without adjustment, a transmission frame occurs when SFN=2 and subframe=1, a PDCCH (DCI) for transmitting the frame is transmitted when SFN=2 and subframe=5, and the frame is actually transmitted when SFN=2 and subframe=6, as shown in FIG. Figure 4A In this case, a delay of 5 ms occurs. In this case, the base station apparatus 101 can use the case where SFN = 0 and subframe = 5 (such as Figure 4B 4 in the figure), and sends an indication indicating an offset value = 13ms until DRX ON (used only once after the drx inactivityTimer expires). Upon receiving the offset value until DRX ON (used only once) starts, the terminal device 111 receives the offset value until DRX ON (used only once) starts, and the terminal device 111 receives the offset value until DRX ON (used only once) starts. Figure 4B) causes DRX ON when the base station device 101 receives the transmission frame (indicated by "4" in the figure). Therefore, after the transmission frame appears, the base station device 101 can send the PDCCH (DCI) for sending downlink data without delay. Note that although an example has been described above in which an offset value for adjusting the timing of DRX ON and DRX OFF is determined so that the PDCCH (DCI) for sending downlink data can be sent immediately after the transmission frame arrives at the base station device 101, it is not intended to be limiting. That is, the base station device 101 can determine the offset value within a range that remains within the packet delay budget or is lower than the packet delay budget. When the application is in use, the base station device 101 can periodically confirm the delay time period that changes dynamically depending on the transmission status of the downlink frame, determine an appropriate offset value as needed each time the confirmation is made, and instruct the terminal device 111 to change the timing of DRX ON and DRX OFF.

[0046] Although the above describes an example of changing the parameters related to CDRX based on the cycle of the downlink application frame periodically transmitted from the base station apparatus 101 to the terminal apparatus 111, the parameters related to CDRX may be changed based on the cycle of the uplink application frame periodically transmitted from the terminal apparatus 111 to the base station apparatus 101. In this case, the base station apparatus 101 changes shortDRX-Cycle, drx-SlotOffset, and drx-inactivityTimer based on the business mode and frame cycle reported from the terminal apparatus 111. In addition, the terminal apparatus 111 may request the base station apparatus 111 to correct the timing of DRX ON and DRX OFF, thereby minimizing the transmission delay of the uplink frame from the terminal apparatus 111 to the base station apparatus 101 that occurs due to the time period of DRX OFF. At this time, the terminal apparatus 111 may notify the base station apparatus 101 of a correction value indicating to what extent the timing correction should be performed. As an example, when the terminal device 111 sends the timing of PUSCH to the base station device 101 using signaling in layer 1 or layer 2, it informs the offset value before the start of DRX ON (used only once after the drx inactivityTimer expires) and requests the base station device 101 to correct the timing of DRX ON and DRX OFF.

[0047] Furthermore, the traffic patterns and frame periods to be considered can be of two types. Figure 5 As shown, in the case where a frame of a 20ms period (service 1) and a frame of a 10ms period (service 2) appear at the same time, DRX control can be performed on the frame of each period, and the terminal device 111 can be controlled so that when the DRX of one of the periods is ON (OR condition), that is, in Figure 5The PDCCH is monitored during the 2ms to 10ms, 17ms to 30ms, and 37ms to 49ms intervals. Figure 5 In the case of, the terminal device 111 can be controlled so that the DRX ON period can be extended by aligning the transmission timing of the PDCCH (DCI) for transmitting the frame (service 1) with a 20ms period with the transmission timing of the PDCCH for the frame (service 2) with a 10ms period, instead of tolerating the transmission delay. In addition, for example, Figure 5 The 20ms period frame (service 1) shown in the figure can be a CG-based DRX control, which is the transmission period of the uplink frame; the 10ms period frame (service 2) can be an SPS-based DRX control, which is the transmission period of the downlink frame.

[0048] Note that although control for a case where there are two types of frame periods has been described above, there may be two or more types of frame periods. In this case, the base station device 101 may configure multiple DRX settings on the terminal device 111, for example, using signaling in layer 3 (such as RRC reconfiguration), and dynamically issue an indication of which DRX setting to activate or deactivate using signaling in layer 1 or layer 2 (such as DCI). In the case where the indication indicates that there are multiple DRX settings to be activated, the terminal device 111 may operate so as to monitor the PDCCH for one of these DRX settings during DRX ON. In addition, in order to minimize the power consumed, control may be performed so that only one of the multiple DRX settings is activated, thereby limiting the time period during which the terminal device 111 monitors the PDCCH, rather than tolerating a transmission delay.

[0049] In addition, in the case where the frame transmitted from the terminal device 111 to the base station device 101 is burst data transmitted after dividing one frame into a plurality of packets, or in the case where the frame transmitted from the base station device 101 to the terminal device 111 is burst data, the period of the burst data and the duration of the burst data can be specified based on the transmission period of the packet at the head of the frame and the transmission timing of the packet at the end of the frame. The period of DRX ON, the duration of DRX ON, the time period for performing periodic resource allocation based on CG and SPS, the time period for not performing such periodic resource allocation, the time period for transmitting BSR, and the time period for not transmitting BSR can be determined based on the period of the burst data and the duration of the burst data. In addition, sr-prohibitTimer, which is a timer for controlling the time period for prohibiting BSR transmission, can be determined based on the period of the burst data and the duration of the burst data. In addition, in the case where the core network device 121 and the application server 131 notify the base station device 101 of the period of the burst data, the number of received data packets per period of the burst data, and the size of the received data packets, the duration of the burst data can be calculated theoretically based on the information of these notifications and the transmission speed in the wireless section.

[0050] Note that in an embodiment of the present invention, the base station apparatus 101 may provide / configure notifications, instructions, and settings to the terminal apparatus 111 via signaling in layer 1 using downlink control information (DCI) and signaling in layer 2 using downlink media access control and control elements (DL MAC CE). In addition, the terminal apparatus 111 may provide notifications, requests, and reports to the base station apparatus 101 via signaling in layer 1 using uplink control information (UCI) and signaling in layer 2 using uplink media access control and control elements (UL MAC CE). In addition, the base station apparatus may be notified of capability information (UE capabilities) related to each of the above-mentioned functions related to the designation of a service mode, the determination of a frame period, and the transmission delay, and the functions of changing the period and timing of SPS, CG, and DRX, setting a buffer size table, etc. In this case, the base station apparatus 101 may instruct the terminal apparatus 111 to perform each function based on the capability information notified from the terminal apparatus 111.

[0051] (Device Configuration)

[0052] Will use Figure 6Describe an exemplary hardware configuration of a base station device and a terminal device. In one example, the base station device and the terminal device are configured to include a processor 201, a ROM 202, a RAM 203, a storage device 204, and a communication circuit 205. The processor 201 is a computer configured to include one or more processing circuits (such as a general-purpose central processing unit (CPU) and an application-specific integrated circuit (ASIC)), and performs processing of the entire device and each type of processing described above by reading out a program stored in the ROM 202 and the storage device 204 and executing the program. ROM 202 is a read-only memory that stores information about programs related to the processing performed by the base station device and the terminal device, various types of parameters, and the like. RAM 203 is a random access memory that is used as a workspace when the processor 201 executes the program, and stores temporary information. The storage device 204 is composed of, for example, an attachable / removable external storage device, etc. The communication circuit 205 is composed of, for example, a circuit for wireless communication according to 5G and subsequent standards. Note that although Figure 6 The figure shows one communication circuit 205, but for example, the base station device and the terminal device may include two or more communication circuits. In addition, for example, the base station device and the terminal device may include an antenna shared with a wireless communication circuit for 5G and its subsequent standards. Note that the base station device and the terminal device may include an antenna for 5G and an antenna for its subsequent standards, respectively. In addition, the terminal device may include a communication circuit for another wireless communication network such as a wireless LAN. Note that the base station device and the terminal device may include individual communication circuits corresponding to a plurality of available frequency bands, respectively, or may include a shared communication circuit for at least a portion of these frequency bands. Note that in an embodiment of the present invention, it is assumed that the terminal device includes a plurality of communication circuits that can communicate in the same frequency band. In addition, the base station device may also include a wired communication circuit for communicating with another base station device and a node of a core network.

[0053] Figure 7 301, a packet data convergence protocol (PDCP) functional unit 302, a radio link control (RLC) functional unit 303, a medium access control (MAC) functional unit 304, a traffic mode determination unit 305, and a communication parameter control unit 306. Figure 7 In the figure, only functional components particularly related to the embodiments of the present invention are illustrated, and illustrations of various other types of functional components that may be included in the base station device are omitted. For example, the base station device naturally includes other functional components that are generally included in the base station device according to 5G and subsequent standards. In addition, Figure 7The functional blocks are schematically illustrated; the individual functional blocks can be implemented in an integrated manner or can be further refined. In addition, Figure 7 Each function of can be realized by, for example, the processor 201 executing a program stored in the ROM 202 and the storage device 204, or can be realized by, for example, the processor existing inside the communication circuit 205 executing predetermined software. Note that regarding the details of the processing performed by each functional unit, the above details are not described below, and only an overview of its general functions is provided.

[0054] Each of the SDAP function unit 301, the PDCP function unit 302, the RLC function unit 303, and the MAC function unit 304, after receiving a transmission frame to the terminal device 111 from a function unit located in an upper layer, specifies the time of the reception and the data size of the frame, and notifies the specified information to the service mode determination unit 305. Note that these function units are equivalent to the protocol stack in the user plane; the SDAP function unit 301 corresponds to the highest layer among these function units, the PDCP function unit 302 corresponds to the second upper layer, the RLC function unit 303 corresponds to the third upper layer, and the MAC function unit 304 corresponds to the lowest layer among these function units. The service mode determination unit 305 calculates the service period based on the reception time and performs statistical processing for the calculated multiple frame periods. The service mode determination unit 305 calculates, for example, statistical information such as the average value, maximum value, minimum value, mode, and standard deviation of the frame period. In addition, also with respect to the data size, the service mode determination unit 305 can calculate statistical information such as the average value, maximum value, minimum value, mode, and standard deviation. In addition, in the case where the frame generated by the application is burst data that is sent after dividing the frame into a plurality of packets, the service mode measurement unit 305 obtains the reception time of the leading packet and the trailing packet from the SDAP function unit 301, the PDCP function unit 302, the RLC function unit 303, and the MAC function unit 304. In this way, the service mode measurement unit 305 calculates the period of the burst data and the duration of the burst data in each functional unit. Regarding the period of the burst data and the duration of the burst data, it is expected that a plurality of pieces of data will be obtained, and the service mode measurement unit 305 calculates statistical information such as the average value, the maximum value, the minimum value, the mode, and the standard deviation. In addition, the service mode measurement unit 305 can request each functional unit to provide measurement data such as the reception time of the frame while focusing only on information related to the specific frame to be measured. In this case, each functional unit provides data related to the PDU session, the QoS flow, and the network slice related to the specific frame as needed. Each functional unit can determine the frame to be measured based on the identifier attached by the upper layer such as the application server 131 and the core network device 121, and record the reception time of the frame.

[0055] The traffic mode determination unit 305 notifies the communication parameter control unit 306 of information such as the frame cycle, frame size, cycle of burst data, duration of burst data, etc. Based on the received information, the communication parameter control unit 306 determines the parameters of SPS, CG, and DRX, and uses these parameters to configure the settings of the terminal device 111. When notified of new information by the traffic mode determination unit 305 during communication, the communication parameter control unit 306 determines whether each parameter needs to be changed based on the notified information. Then, in the case where the communication parameter control unit 306 has determined that a change is required, it requests the terminal device 111 to change the setting.

[0056] Figure 8 4 is a diagram showing an exemplary functional configuration of a terminal device. The terminal device includes an SDAP function unit 401, a PDCP function unit 402, an RLC function unit 403, a MAC function unit 404, and a traffic mode determination unit 405 as its functional components. Figure 8 In the embodiment, only functional components particularly related to the embodiments of the present invention are shown, and illustrations of various other types of functional components that may be included in the terminal device are omitted. For example, the terminal device naturally includes other functional components that are generally included in terminal devices according to 5G and subsequent standards. In addition, Figure 8 The functional blocks are schematically illustrated; the individual functional blocks can be implemented in an integrated manner or can be further segmented. In addition, Figure 8 Each function of can be realized by, for example, the processor 201 executing a program stored in the ROM 202 and the storage device 204, or can be realized by, for example, the processor existing inside the communication circuit 205 executing predetermined software. Note that regarding the details of the processing performed by each functional unit, the above details are not described below, and only an overview of its general functions is provided.

[0057] The SDAP function unit 401, the PDCP function unit 402, the RLC function unit 403, and the MAC function unit 404 are similar to the corresponding function units in the base station device, and correspond to the layers of the protocol stack in the user plane, respectively. The service mode measurement unit 405 receives an instruction for specifying a service mode and measuring a frame period from the base station device. Based on the instruction from the base station device, the service mode measurement unit 405 requests the SDAP function unit 401, the PDCP function unit 402, the RLC function unit 403, and the MAC function unit 404 to provide data related to the measurement. As an example, the data related to the measurement may be the time when each function unit receives a frame from a function unit in the upper layer, the frame size, and the delay time period from when each function unit receives a frame from the upper layer to when the frame is sent to the function unit in the lower layer. In addition, the delay time period measured in the MAC function unit 404 may include the transmission of the BSR of the frame sent to the base station device, and the time period from when the base station device receives the BSR until the uplink radio resource is actually allocated. Regarding the data segments acquired from the corresponding functional units, the traffic pattern determination unit 405 calculates statistical information such as the average value, maximum value, minimum value, mode, and standard deviation as necessary, and reports the acquired data segments and the calculation results of the statistical information to the base station apparatus.

[0058] The traffic mode measurement unit 405 notifies the MAC function unit 404 of information such as the frame period, the frame size, the period of burst data, the duration of burst data, etc. Based on the information obtained from the traffic mode measurement unit 405, the MAC function unit 404 determines the setting of the appropriate buffer size table, and notifies the base station device of the number of bits in the buffer size table and the minimum and maximum values ​​of the buffer size table (which are examples of the determination results). In addition, the MAC function unit 404 can request the base station device 101 to correct the transmission timing of the uplink frame so that the measured delay time period required before transmission is maintained at or below the maximum value of the transmission delay of the packet notified from the core network device and the base station device (packet delay budget).

[0059] (Processing Flow)

[0060] Next, we will use Fig. 9 An exemplary flow of processing performed in a wireless communication system is described below. Figure 1An example of a situation in which the terminal device 111 connected to the base station device 101 requests correction of the transmission timing of the uplink frame is shown, that is, the terminal device 111 requests the base station device 101 to correct the transmission timing of the uplink so that the actually measured transmission delay time period remains at the maximum value of the transmission delay of the packet (packet delay budget) or lower than the maximum value of the transmission delay of the packet (packet delay budget).

[0061] First, the terminal device 111 obtains information related to the frame type for which the service mode is to be specified and frame characteristic information from the base station device 101 (S901). For example, the base station device 101 notifies the terminal device 111 of the logical channel identifier (LCID), DRB identifier, PDU session ID and QFI value (QoS flow) used in the transmission / reception of the frame for which the service mode is to be specified. At this time, it is also possible to use, for example, layer 3 signaling such as RRC reconfiguration to additionally provide notifications about characteristic information of the video frame for which the formulation is to be performed, such as frame rate (frames per second or fps), data rate (Mbps), quality of service (QoS), priority, maximum value of the transmission delay of the packet (packet delay budget), packet error rate (packet error loss rate), number of packets per frame and number of PDUs (e.g., video frames). In the case where there are multiple frames for which the service mode is to be specified, for example, a notification about a list of the same number of frames for which the service mode is to be specified can be provided, such as a packet delay budget = 2ms for LCID = 1 and a packet delay budget = 5ms for LCID = 2.

[0062] The terminal device 111 measures the time period required from the time when the occurrence of the transmission frame is recognized to the time when the frame is actually transmitted to the base station device 101 (S902). As an example, the terminal device 111 measures the time period required from the timing when the MAC function unit in the terminal device 111 receives the transmission frame from the RLC function unit in the upper layer to the timing of the actual transmission of the PUSCH containing the frame. Note that the timing of the start of the measured time period is not limited to the time when the frame is received by the MAC function unit, and can be the time when the RLC function unit, PDCP function unit, SDAP function unit, etc. receive the frame from the function unit located in the upper layer, or the time when the frame is transmitted to the function unit located in the lower layer. In addition, the timing of the end of the measured time period can be one of the time when the terminal device 111 receives the DCI containing information related to the allocation of wireless resources for frame transmission, the time when the frame transmission via the PUSCH is started, and the time when the frame transmission via the PUSCH is ended.

[0063] Using the above-mentioned measured value and the maximum value of the transmission delay of the packet (packet delay budget), the terminal device 111 determines a correction value for the transmission timing of the uplink frame (S903). Here, in the case where there are multiple measured values, the terminal device 111 can use the average value and the mode to determine the correction value, or can determine the correction value without using the packet delay budget. The correction value can be expressed using a positive / negative offset from the current transmission timing, and the positive / negative offset is expressed by a frame number or a symbol number or a system frame number (SFN).

[0064] The terminal device 111 requests the base station device 101 to change the transmission timing (S904). For example, the terminal device 111 may notify the base station device 101 of the request to change the transmission timing using signaling in layer 1 or layer 2. At this time, the terminal device 111 may also notify the base station device 101 of the determined correction value. In addition, the request to change the transmission timing and the notification of the correction value may be provided using the BSR.

[0065] The base station apparatus 101 determines whether it will comply with the request for changing the transmission timing from the terminal apparatus 111, and returns the determination result to the terminal apparatus 111 (S905). For example, the base station apparatus 101 returns information indicating whether it will comply with the correction value from the terminal apparatus 111 to the terminal apparatus. In addition, in the case where the base station apparatus 101 performs correction using a value different from the correction value notified from the terminal apparatus 111, the base station apparatus 101 may notify the terminal apparatus 111 of the different correction value. In addition, as an alternative to the response, the base station apparatus 101 may provide a notification of the timing of allocation of radio resources of the PUSCH to be allocated to the terminal apparatus 111 via the PDCCH.

[0066] As described above, in the case where it is expected that communications of various business modes will be performed simultaneously in actual application business, embodiments of the present invention can provide appropriate communication control suitable for these business modes. This makes it possible to contribute to Goal 9 of the Sustainable Development Goals (SDGs) led by the United Nations, namely, "Build resilient infrastructure, promote inclusive and sustainable industrialization, and foster innovation."

[0067] The present invention is not limited to the above-described embodiments, and various changes / alterations are possible within the spirit and scope of the present invention.

[0068] This application claims priority to and the benefit of Japanese Patent Application No. 2022-152532, filed on September 26, 2022, which is hereby incorporated by reference in its entirety.

Claims

1. A terminal device, characterized in that: The terminal device comprises: an identification unit for identifying a head packet and a tail packet when a frame generated by an application executed by the terminal device is divided into a plurality of packets and transmitted; a measuring unit configured to measure a reception time of the leading packet identified by the identifying unit; a calculation unit for calculating a frame period and a fluctuation of the frame period based on a measurement result of the measurement unit; a reporting unit, which reports the calculation result to the base station device; as well as The acquisition unit acquires information on a frame to be reported by the reporting unit from the base station apparatus.

2. A terminal device, characterized in that: The terminal device comprises: A sending unit, which sends uplink data through a configured grant; An acquisition unit, which acquires the configured authorized period and allocation information of the radio resource block from the base station device through layer 3 signaling; a receiving unit, which receives a change indication of the configured authorized period and resource block allocation information from the base station device through layer 1 or layer 2 signaling; as well as The request unit requests the base station apparatus to change the allocation timing of the radio resource blocks.

3. A terminal device, characterized in that: The terminal device comprises: a notification unit that notifies the base station apparatus of the transmission buffer size through a buffer status report (BSR); and An acquiring unit is configured to acquire a lowest value, a number of bits, and a 1-bit step size of a buffer size table used for notification of the BSR.

4. The terminal device according to claim 3, characterized in that: The terminal device also has: a reporting unit, which reports a sending waiting time to the base station device in the BSR, and the sending waiting time is from the identification of sending data in the function of the media access control (MAC) included in the terminal device to the sending data in the physical uplink shared channel (PUSCH).

Images