Terminal device, base station, and communication method

By measuring and transmitting packet residence times to the base station, the terminal device facilitates effective scheduling, achieving low-latency and high-performance wireless communication in cellular networks.

JP2024157381AInactive Publication Date: 2024-11-07SONY GROUP CORP
View PDF 1 Cites 0 Cited by

Patent Information

Application Number
JP2023071712
Authority / Receiving Office
JP · JP
Patent Type
Applications
Current Assignee / Owner
Filing Date
2023-04-25
Publication Date
2024-11-07
Estimated Expiration
Not applicable · inactive patent

AI Technical Summary

Technical Problem

The scheduling of uplink communications in cellular networks is challenging due to the base station's inability to grasp the residence time of packets within the terminal device, leading to difficulties in meeting latency requirements.

Method used

The terminal device measures the residence time of packets and transmits this information to the base station, allowing the base station to schedule uplink communications effectively and meet latency requirements.

Benefits of technology

This approach enables low-latency wireless communication by allowing the base station to schedule uplink transmissions based on accurate residence time information, resulting in stable and high-performance communication.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure 2024157381000001_ABST
    Figure 2024157381000001_ABST
Patent Text Reader

Abstract

To propose a terminal device, a base station, and a communication method capable of realizing low-delay wireless communication.SOLUTION: A terminal device connected to a base station, the terminal device comprises: a measurement unit that measures residence times of one or more packets transmitted by the terminal device for the respective packets; a specification unit that specifies a maximum value of the residence times; and a transmission unit that transmits residence time information including at least information regarding the maximum value of the residence times to the base station.SELECTED DRAWING: Figure 15
Need to check novelty before this filing date? Find Prior Art

Description

[Technical field]

[0001] The present disclosure relates to a terminal device, a base station, and a communication method. [Background technology]

[0002] Recent mobile networks (e.g., cellular networks such as 5G) require high communication performance (e.g., connection stability, low latency, high reliability, high throughput, low power consumption, low processing load, etc.). Among these, realizing low latency is a very important element in realizing new communication services that have emerged in recent years (e.g., device control in IoT, real-time communication in games and VR, etc.). [Prior art documents] [Non-patent literature]

[0003] [Non-Patent Document 1] JP 2012-34407 A Summary of the Invention [Problem to be solved by the invention]

[0004] One of the causes of delay is the waiting time for scheduling at the base station. In downlink communication, the network side (e.g., the core network and / or the base station) can grasp the residence time of the packet. Therefore, it is assumed that the base station can schedule the downlink communication so as to satisfy the delay requirement. However, in uplink communication, the base station side cannot grasp the residence time of the packet in the terminal device. Therefore, it is not easy for the base station to schedule the uplink communication so as to satisfy the delay requirement.

[0005] Therefore, the present disclosure proposes a terminal device, a base station, and a communication method that can realize low-latency wireless communication.

[0006] It should be noted that the above problem or objective is merely one of several problems or objectives that can be solved or achieved by several embodiments disclosed in this specification. [Means for solving the problem]

[0007] In order to solve the above problems, a terminal device of one embodiment according to the present disclosure is a terminal device connected to a base station, and includes a measurement unit that measures a residence time of one or more packets transmitted by the terminal device for each packet, an identification unit that identifies a maximum residence time, and a transmission unit that transmits residence time information including at least information regarding the maximum residence time to the base station. [Brief description of the drawings]

[0008] [Figure 1] This is an excerpt from 3GPP TS 23.501 Table 5.7.4-1. [Diagram 2] FIG. 1 is a diagram for explaining scheduling of downlink communication. [Diagram 3] FIG. 1 is a diagram for explaining scheduling of downlink communication. [Figure 4] 1 is a diagram showing a configuration of a communication system according to an embodiment of the present invention; [Diagram 5] FIG. 2 is a diagram illustrating a configuration example of a server according to an embodiment of the present disclosure. [Figure 6] FIG. 2 is a diagram illustrating a configuration of a management device according to the present embodiment. [Figure 7] FIG. 2 is a diagram illustrating a configuration of a base station according to the present embodiment. [Figure 8] FIG. 2 is a diagram illustrating a configuration of a terminal device according to the present embodiment. [Figure 9] FIG. 2 is a functional block diagram of a terminal device according to the first embodiment. [Figure 10] FIG. 13 is a diagram showing an example of a format of a BSR capable of storing residence time information. [Figure 11] FIG. 13 is a diagram showing an example of a format of a BSR capable of storing residence time information. [Figure 12]FIG. 13 is a diagram showing another example of a BSR format capable of storing residence time information. [Figure 13] FIG. 13 is a diagram showing another example of a BSR format capable of storing residence time information. [Figure 14] FIG. 4 is a sequence diagram showing a communication process according to the first embodiment. [Figure 15] FIG. 13 is a diagram for explaining scheduling taking into account residence time. [Figure 16] FIG. 11 is a functional block diagram of a terminal device according to a second embodiment. [Figure 17] FIG. 11 is a functional block diagram of a base station according to the second embodiment. [Figure 18] 11 is a diagram illustrating an example of a format of a PDU capable of storing a timestamp. [Figure 19] FIG. 13 is a diagram for explaining the measurable granularity of delay time. [Figure 20] FIG. 11 is a sequence diagram showing a communication process according to the second embodiment. [Figure 21] FIG. 11 is a diagram for explaining scheduling taking delay time into consideration. [Figure 22] FIG. 11 is a functional block diagram of a communication system according to a third embodiment. [Figure 23] FIG. 11 is a functional block diagram of a terminal device according to a third embodiment. [Figure 24] FIG. 11 is a functional block diagram of a server according to a third embodiment. [Diagram 25] FIG. 4 is a sequence diagram showing a communication process according to the first embodiment. [Figure 26] FIG. 11 is a sequence diagram for explaining a method for identifying a residence time. [Figure 27] FIG. 2 is a diagram for explaining an external device. [Figure 28] FIG. 1 illustrates an example of an O-RAN architecture. [Figure 29] FIG. 1 is a sequence diagram showing communication processing using O-RAN. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0009] Hereinafter, embodiments of the present disclosure will be described in detail with reference to the drawings. In the following embodiments, the same components are designated by the same reference numerals, and duplicated descriptions will be omitted.

[0010] In addition, in this specification and drawings, multiple components having substantially the same functional configuration may be distinguished by adding different letters or numbers after the same reference numeral. For example, multiple components having substantially the same functional configuration may be distinguished as necessary, such as terminal devices 401, 402, and 403. However, when there is no particular need to distinguish between multiple components having substantially the same functional configuration, only the same reference numeral may be added. For example, when there is no particular need to distinguish between terminal devices 401, 402, and 403, they are simply referred to as terminal device 40.

[0011] One or more embodiments (including examples and modified examples) described below can be implemented independently. Meanwhile, at least a part of the embodiments described below may be implemented in appropriate combination with at least a part of another embodiment. These embodiments may include novel features different from each other. Thus, these embodiments may contribute to solving different purposes or problems and may provide different effects.

[0012] <<1. Overview>> Before describing this embodiment in detail, an overview of this embodiment will be given.

[0013] <1-1. Issues> Recent mobile networks (e.g., cellular networks such as 5G) require high communication performance (e.g., connection stability, low latency, high reliability, high throughput, low power consumption, low processing load, etc.). Among these, realizing low latency is a very important element in realizing new communication services that have emerged in recent years (e.g., device control in IoT, real-time communication in games and VR, etc.).

[0014] One of the causes of delay is the waiting time for scheduling in a MAC (Medium Access Control) scheduler in a base station. This occurs because the amount of data that can be transmitted / multiplexed at one time is limited by the system bandwidth and the radio wave propagation environment of the terminal device. In particular, for services (e.g., Bearer, Slice, Session, or QoS Flow) for which a PDB (Packet Delay Budget) is defined in an SLA (Service Level Agreement) or the like, the base station needs to perform scheduling so as not to exceed the PDB (hereinafter simply referred to as Delay Budget). Figure 1 is an excerpt from TS 23.501 Table 5.7.4-1 of 3GPP (registered trademark). In a cellular network, the delay target value of a service is set in the core network / base station (gNB / eNB) as QoS (Quality of Service) information.

[0015] For the downlink (DL), the residence time of each packet can be measured on the network side (e.g., a core network and / or a base station). Therefore, it is assumed that the base station can perform scheduling so that the residence time of a packet does not exceed a delay budget defined by an SLA or the like.

[0016] FIG. 2 is a diagram for explaining the scheduling of downlink communication. In the example of FIG. 2, three terminal devices (A, B, and C shown in FIG. 2) are connected to a base station (gNB in ​​the example of FIG. 2). The base station receives packets for each terminal device from a core network (5GC in the example of FIG. 2). A timestamp or the like is added to the packet that the base station receives from the core network at the entrance of the core network. The base station calculates the residence time of each packet based on the timestamp. FIG. 2 shows multiple packets that are held in the gNB DL RLC buffer, and the residence time and budget margin time of each of the multiple packets. Then, the base station performs scheduling based on the information on the residence time. In the example of FIG. 2, a packet for terminal device A with a residence time of 13 ms has the least margin in the Delay Budget. Therefore, the base station performs scheduling to transmit packets for terminal device A first.

[0017] In the uplink (UL), too, it is expected that scheduling based on delay time will be performed in consideration of a delay budget defined in an SLA (Service Level Agreement) or the like. FIG. 3 is a diagram for explaining scheduling of downlink communication. Currently, a terminal device notifies a base station of the total buffer retention amount for each LCG (Logical Channel Group) in a BSR (Buffer Status Report). However, the terminal device does not notify the base station of information indicating how long each packet has been retained in the terminal device. The base station may be able to determine the time from when the buffer is 0 to when the packet is cleared. However, this is insufficient for SLA. In other words, in the uplink communication, the base station side cannot grasp the retention time of the packet in the terminal device. Therefore, it is not easy for the base station to schedule the uplink communication so as to satisfy the delay requirement.

[0018] <1-3. Overview of the solution> Therefore, in this embodiment, the above problem is solved as follows.

[0019] For example, the terminal device of the present embodiment measures the residence time of one or more uplink packets to be transmitted to the base station for each packet, and identifies the maximum residence time. For example, the terminal device identifies the maximum residence time (e.g., residence time in the terminal device / residence time in the RLC buffer) among RLC PDUs (Radio Link Control Protocol Data Units) remaining in the LCG when transmitting a BSR. Then, the terminal device transmits residence time information including at least information regarding the maximum residence time to the base station. For example, the terminal device provides a new area for storing residence time information in the BSR, and stores the residence time information in the area. Then, the terminal device transmits the BSR storing the residence time information to the base station. The base station extracts the residence time information from the received BSR. Then, the base station schedules uplink communication based on the residence time information.

[0020] This allows the base station to schedule uplink communication so as to satisfy the delay requirement. As a result, low-latency wireless communication is realized in uplink communication as well, so that the base station and the terminal device can realize wireless communication with high communication performance (for example, stable low-latency wireless communication).

[0021] The outline of this embodiment has been described above, and the communication system 1 of this embodiment will be described in detail below.

[0022] <<2. Communication System Configuration>> First, a specific description will be given of the configuration of the communication system 1. The configuration of the communication system 1 described below is common to the first to third embodiments.

[0023] FIG. 4 is a diagram showing a configuration of a communication system 1 according to the present embodiment. The communication system 1 includes a server 10, a management device 20, a base station 30, and a terminal device 40. The communication system 1 provides a wireless network (mobile network) that enables mobile communication to a user by the wireless communication devices constituting the communication system 1 operating in cooperation with each other. The wireless network of the present embodiment may be, for example, a cellular network composed of a radio access network RAN ​​and a core network CN. The mobile network may include a terminal device 40. In the present embodiment, a wireless communication device is a device having a wireless communication function, and in the example of FIG. 4, the wireless communication device corresponds to the base station 30 and the terminal device 40.

[0024] The communication system 1 may include a plurality of servers 10, management devices 20, base stations 30, and terminal devices 40. In the example of Fig. 4, the communication system 1 includes a server 101 and a server 102 as the servers 10, and a management device 201 and a management device 202 as the management devices 20. The communication system 1 also includes a base station 301, a base station 302, and a base station 303 as the base stations 30, and a terminal device 401, a terminal device 402, and a terminal device 403 as the terminal devices 40.

[0025] The terminal device 40 may be configured to connect to a network using a radio access technology (RAT) such as LTE (Long Term Evolution), NR (New Radio), 6G, Wi-Fi, Bluetooth (registered trademark), etc. In this case, the terminal device 40 may be configured to be able to use different radio access technologies (wireless communication methods). For example, the terminal device 40 may be configured to be able to use NR and Wi-Fi. Also, the terminal device 40 may be configured to be able to use different cellular communication technologies (for example, LTE, NR, or 6G). In the following description, the terminal device 40 may be referred to as UE (User Equipment).

[0026] LTE and NR are types of cellular communication technologies that enable mobile communication for terminal devices by arranging multiple areas covered by base stations in the form of cells. 6G, as a type of cellular communication technology, may also be a technology that enables mobile communication for terminal devices by arranging multiple areas covered by base stations in the form of cells.

[0027] In the following description, "LTE" includes LTE-Advanced (LTE-A), LTE-A Pro (LTE-Advanced Pro), and EUTRA (Evolved Universal Terrestrial Radio Access). NR includes New Radio Access Technology (NRAT) and Further EUTRA (FEUTRA). A single base station 30 may manage multiple cells. In the following description, a cell compatible with LTE is referred to as an LTE cell, and a cell compatible with NR is referred to as an NR cell.

[0028] NR is the next generation (5th generation) radio access technology after LTE (4th generation communication including LTE-Advanced and LTE-Advanced Pro). NR is a radio access technology that can support various use cases including eMBB (Enhanced Mobile Broadband), mMTC (Massive Machine Type Communications) and URLLC (Ultra-Reliable and Low Latency Communications). NR was standardized in Rel-15 of 3GPP (registered trademark) as a technical framework that supports the usage scenarios, requirements, and deployment scenarios in these use cases. Furthermore, Beyond 5G and 6G are required to simultaneously realize multiple axes of high speed and large capacity, low latency and high reliability, and multiple simultaneous connections.

[0029] 6G is the next generation of cellular communication technology after NR and 5GS (5G system), which are the fifth generation mobile communications. 6G includes radio access technology and network technology between base stations, core networks, and data networks. 6G also includes technologies for the enhancement (extreme connectivity) of eMBB, mMTC, and URLLC, which were the main use cases or requirements in NR. 6G also includes new technologies in new aspects. For example, 6G may include technologies related to AI (cognitive network, AI native air interface), sensing (including radar sensing and network as a sensor), and terahertz communication.

[0030] The wireless network may support at least one of radio access technologies (RATs) such as LTE (Long Term Evolution), NR (New Radio), and 6G. LTE, NR, and 6G are types of cellular communication technologies, and enable mobile communication of terminal devices by arranging a plurality of areas covered by base stations in the form of cells. The wireless access method used by the communication system 1 is not limited to LTE, NR, and 6G, and may be other wireless access methods such as W-CDMA (Wideband Code Division Multiple Access), cdma2000 (Code Division Multiple Access 2000), etc.

[0031] In addition, the base station 30 may be a terrestrial station or a non-terrestrial station. The non-terrestrial station may be a satellite station or an aircraft station. If the non-terrestrial station is a satellite station, the wireless network may be a bent-pipe (transparent) type mobile satellite communication system.

[0032] In this embodiment, the terrestrial station and terrestrial base station refer to base stations and relay stations installed on the ground. Here, "terrestrial" has a broad definition of terrestrial, including not only land but also underground, on water, and underwater. In the following description, the term "terrestrial station" may be replaced with "gateway."

[0033] Note that an LTE base station may be referred to as an eNodeB (Evolved Node B) or eNB. Also, an NR base station may be referred to as a gNodeB or gNB. Also, a 6G base station may be referred to as a 6G NodeB (6GNB). Also, in LTE, NR, and 6G, a terminal device (also referred to as a mobile station or terminal) may be referred to as a UE (User Equipment). Note that a terminal device is a type of communication device, and is also referred to as a mobile station or terminal.

[0034] The terminal device 40 may be able to connect to the network using a wireless access technology (wireless communication method) other than LTE, NR, 6G, Wi-Fi, and Bluetooth. For example, the terminal device 40 may be able to connect to the network using LPWA (Low Power Wide Area) communication. The terminal device 40 may also be able to connect to the network using wireless communication of a proprietary standard.

[0035] Here, LPWA communication refers to wireless communication that enables wide-range communication with low power. For example, LPWA wireless refers to IoT (Internet of Things) wireless communication using a specific low-power radio (e.g., 920 MHz band) or an ISM (Industry-Science-Medical) band. The LPWA communication used by the terminal device 40 may be compliant with the LPWA standard. Examples of the LPWA standard include ELTRES, ZETA, SIGFOX, LoRaWAN, and NB-Iot. Of course, the LPWA standard is not limited to these, and may be another LPWA standard.

[0036] Each wireless communication device shown in Fig. 4 may be considered as a device in a logical sense. That is, a part of each wireless communication device may be realized by a virtual machine (VM), a container such as Docker, or the like, and these may be physically implemented on the same hardware.

[0037] In this embodiment, the concept of a wireless communication device includes not only a portable mobile device (terminal device) such as a mobile terminal, but also a device installed in a structure or a mobile body. The structure or the mobile body itself may be regarded as a wireless communication device. In addition, the concept of a wireless communication device includes not only a terminal device 40 but also a base station 30. A wireless communication device is a type of processing device or information processing device. A wireless communication device can also be referred to as a transmitting device or a receiving device.

[0038] Below, we will specifically explain the configuration of each wireless communication device that makes up the communication system 1. Note that the configuration of each wireless communication device shown below is merely an example. The configuration of each wireless communication device may be different from the configuration shown below.

[0039] <2-1. Server configuration> First, the configuration of the server 10 will be described.

[0040] The server 10 is an information processing device (computer) that provides various services to the terminal device 40. For example, the server 10 is an application server or a Web server. The server 10 may be a PC server, a mid-range server, or a mainframe server. The server 10 may also be an information processing device that performs data processing (edge ​​processing) near a user or a terminal. For example, the server 10 may be an information processing device (computer) attached to or built into a base station. Of course, the server 10 may be an information processing device that performs cloud computing. The server 10 of this embodiment can function as an application function.

[0041] The server 10 is connected to the management device 20 via a network N. Although only one network N is shown in the example of FIG. 4, there may be a plurality of networks N. Here, the network N is, for example, a public network such as the Internet. Note that the network N is not limited to the Internet, and may be, for example, a Local Area Network (LAN), a Wide Area Network (WAN), a cellular network, a landline telephone network, or a regional Internet Protocol (IP) network. The network N may include a wired network or a wireless network.

[0042] Fig. 5 is a diagram showing a configuration example of the server 10 according to an embodiment of the present disclosure. The server 10 includes a communication unit 11, a storage unit 12, and a control unit 13. The configuration shown in Fig. 5 is a functional configuration, and the hardware configuration may be different from this. In addition, the functions of the server 10 may be distributed and implemented in multiple physically separated configurations. For example, the server 10 may be composed of multiple information processing devices.

[0043] The communication unit 11 is a communication interface for communicating with other devices. For example, the communication unit 11 is a network interface. For example, the communication unit 11 is a LAN (Local Area Network) interface such as a NIC (Network Interface Card). The communication unit 11 may be a wired interface or a wireless interface. The communication unit 11 functions as a communication means of the server 10. The communication unit 11 communicates with the management device 20, the base station 30, the terminal device 40, and other servers 10 under the control of the control unit 13.

[0044] The storage unit 12 is a data readable / writable storage device such as a dynamic random access memory (DRAM), a static random access memory (SRAM), a flash memory, or a hard disk. The storage unit 12 functions as a storage means of the server 10. The storage unit 12 stores a learning model (prediction model) for predicting the future quality of a mobile network. The learning model will be described later.

[0045] The control unit 13 is a controller that controls each part of the server 10. The control unit 13 may be realized by a processor such as a central processing unit (CPU) or a micro processing unit (MPU). In detail, the control unit 13 may be realized by a processor executing various programs stored in a storage device inside the management device 20 using a random access memory (RAM) or the like as a working area. The control unit 13 may be realized by an integrated circuit such as an application specific integrated circuit (ASIC) or a field programmable gate array (FPGA). The control unit 13 may also be realized by a graphics processing unit (GPU). The CPU, MPU, ASIC, FPGA, and GPU can all be regarded as controllers. The control unit 13 may be configured by a plurality of physically separated objects. For example, the control unit 13 may be configured by a plurality of semiconductor chips.

[0046] <2-2. Management device configuration> Next, the configuration of the management device 20 will be described.

[0047] The management device 20 is an information processing device (computer) that manages a wireless network. For example, the management device 20 is an information processing device that manages communication of the base station 30. The management device 20 may be, for example, a device having a function as an MME (Mobility Management Entity). The management device 20 may be a device having a function as an AMF (Access and Mobility Management Function) and / or an SMF (Session Management Function). The MME, AMF, and SMF are control plane network function nodes in a core network. The management device 20 may be a device having a function as a control plane network function (6G CPNF) in 6G. The 6G CPNF may be composed of one or more logical nodes.

[0048] Of course, the functions of the management device 20 are not limited to MME, AMF, SMF, and 6G CPNF. The management device 20 may be a device having functions as a Network Slice Selection Function (NSSF), an Authentication Server Function (AUSF), a Policy Control Function (PCF), and a Unified Data Management (UDM). The management device 20 may also be a device having functions as a Home Subscriber Server (HSS).

[0049] The management device 20 may have a gateway function. For example, the management device 20 may have a function as an S-GW (Serving Gateway) or a P-GW (Packet Data Network Gateway). The management device 20 may have a UPF (User Plane Function) function. In this case, the management device 20 may have multiple UPFs. The management device 20 may be a device having a function as a 6G User Plane Network Function (6G UPNF).

[0050] The core network is composed of multiple network functions, and each network function may be consolidated in one physical device or distributed across multiple physical devices. That is, the management device 20 may be distributed across multiple devices. Furthermore, this distributed arrangement may be controlled so as to be executed dynamically. The base station 30 and the management device 20 constitute one network, and provide wireless communication services to the terminal device 40. The management device 20 is connected to the Internet, and the terminal device 40 can use various services provided via the Internet via the base station 30.

[0051] Note that the management device 20 does not necessarily have to be a device that constitutes a core network. For example, the core network is assumed to be a W-CDMA (Wideband Code Division Multiple Access) or cdma2000 (Code Division Multiple Access 2000) core network. In this case, the management device 20 may be a device that functions as an RNC (Radio Network Controller).

[0052] Fig. 6 is a diagram showing the configuration of a management device 20 according to this embodiment. The management device 20 includes a communication unit 21, a storage unit 22, and a control unit 23. The configuration shown in Fig. 6 is a functional configuration, and the hardware configuration may be different from this. Furthermore, the functions of the management device 20 may be statically or dynamically distributed and implemented in a plurality of physically separated configurations. The management device 20 may be composed of a plurality of server devices.

[0053] The communication unit 21 is a communication interface for communicating with a wireless communication device (for example, the base station 30). The communication unit 21 may be a network interface or a device connection interface. The communication unit 21 may be a LAN (Local Area Network) interface such as a NIC (Network Interface Card), or a Universal Serial Bus (USB) host controller or a USB interface configured by a USB port or the like. The communication unit 21 may be a wired interface or a wireless interface. The communication unit 21 functions as a communication means of the management device 20. The communication unit 21 is controlled by the control unit 23.

[0054] The storage unit 22 is a readable and writable storage device such as a DRAM, an SRAM, a flash memory, or a hard disk. The storage unit 22 functions as a storage means of the management device 20. The storage unit 22 stores, for example, the connection state of the terminal device 40. The storage unit 22 stores the state of the RRC (Radio Resource Control) of the terminal device 40 and the ECM (EPS Connection Management), or the state of the 5G System CM (Connection Management). The storage unit 22 may function as a home memory that stores the location information of the terminal device 40. The storage unit 22 also stores a learning model (prediction model) for predicting the future quality of the mobile network. The learning model will be described later.

[0055] The control unit 23 is a controller that controls each part of the management device 20. The control unit 23 may be realized by a processor such as a CPU or MPU. In detail, the control unit 23 may be realized by a processor executing various programs stored in a storage device inside the management device 20 using a RAM or the like as a working area. The control unit 23 may be realized by an integrated circuit such as an ASIC or an FPGA. The control unit 23 may also be realized by a GPU. The CPU, MPU, ASIC, FPGA, and GPU can all be considered as controllers. The control unit 23 may be composed of multiple physically separated objects. For example, the control unit 23 may be composed of multiple semiconductor chips.

[0056] <2-3. Base station configuration> Next, the configuration of the base station 30 will be described.

[0057] The base station 30 is a wireless communication device that performs wireless communication with other wireless communication devices (for example, a terminal device 40 or another base station 30). The base station 30 may perform wireless communication with the terminal device 40 via a relay station, or may perform wireless communication directly with the terminal device 40.

[0058] The base station 30 is a device equivalent to a wireless base station (Base Station, Node B, eNB, gNB, 6GNB, etc.) or a wireless access point. The base station 30 may be a wireless relay station. The base station 30 may be an optical extension device called an RRH (Remote Radio Head). The base station 30 may be a receiving station such as an FPU (Field Pickup Unit). The base station 30 may be an IAB (Integrated Access and Backhaul) donor node that provides wireless access lines and wireless backhaul lines by time division multiplexing, frequency division multiplexing, or space division multiplexing, or an IAB relay node.

[0059] The wireless access technology used by the base station 30 may be a cellular communication technology. The wireless access technology used by the base station 30 may be a wireless LAN technology. The wireless access technology used by the base station 30 may be a low power wide area (LPWA) communication technology. However, the wireless access technology used by the base station 30 is not limited to these, and may be other wireless access technologies. The wireless communication used by the base station 30 may be wireless communication using millimeter waves, or wireless communication using terahertz waves. The wireless communication used by the base station 30 may be wireless communication using radio waves, or wireless communication using infrared rays or visible light (optical wireless). In addition, the base station 30 may be capable of NOMA (Non-Orthogonal Multiple Access) communication with the terminal device 40. Here, NOMA communication refers to communication (transmission, reception, or both) using non-orthogonal resources. In addition, the base station 30 may be capable of NOMA communication with other base stations 30.

[0060] The base station 30 may be capable of communicating with the core network via a base station-core network interface (e.g., NG Interface, S1 Interface, etc.). This interface may be either wired or wireless. The base station may be capable of communicating with other base stations via an inter-base station interface (e.g., Xn Interface, X2 Interface, F1 Interface, etc.). This interface may be either wired or wireless.

[0061] The concept of a base station (also called "base station device") includes not only a donor base station but also a relay base station (also called "relay station"). A relay base station may be any one of an RF Repeater, a Smart Repeater, and an Intelligent Surface. The concept of a base station includes not only a structure having the functions of a base station but also a device installed in the structure.

[0062] Examples of structures include buildings such as high-rise buildings, houses, steel towers, station facilities, airport facilities, port facilities, office buildings, school buildings, hospitals, factories, commercial facilities, and stadiums. The concept of a structure includes not only buildings, but also non-building structures such as tunnels, bridges, dams, fences, and steel pillars, as well as equipment such as cranes, gates, and windmills. The concept of a structure includes not only land (ground in the narrow sense) or underground structures, but also water-based structures such as piers or megafloats, and underwater structures such as marine observation facilities. A base station can also be referred to as an information processing device.

[0063] The base station 30 may be a donor station or a relay station (relay station). The base station 30 may be a fixed station or a mobile station. The mobile station is a wireless communication device (for example, a base station) configured to be movable. In this case, the base station 30 may be a device installed in a mobile body, or may be the mobile body itself. For example, a relay station having mobility can be regarded as the base station 30 as a mobile station. In addition, devices that are originally capable of mobility and have the functions of a base station (at least a part of the functions of a base station), such as vehicles, UAVs (Unmanned Aerial Vehicles) represented by drones, and smartphones, also correspond to the base station 30 as a mobile station.

[0064] Here, the moving body may be a mobile terminal such as a smartphone or a mobile phone. The moving body may be a moving body moving on land (ground in the narrow sense) (for example, a vehicle such as an automobile, bicycle, bus, truck, motorcycle, train, or linear motor car), or a moving body moving underground (for example, in a tunnel) (for example, a subway). The moving body may also be a moving body moving on water (for example, a ship such as a passenger ship, a cargo ship, or a hovercraft), or a moving body moving underwater (for example, a submarine such as a submarine, a submarine, or an unmanned submersible). The moving body may also be a moving body moving in the atmosphere (for example, an aircraft such as an airplane, an airship, or a drone).

[0065] The base station 30 may be a terrestrial base station (ground station) installed on the ground. The base station 30 may be a base station arranged on a structure on the ground, or may be a base station installed on a mobile body moving on the ground. The base station 30 may be an antenna installed on a structure such as a building and a signal processing device connected to the antenna. The base station 30 may be a structure or a mobile body itself. The term "ground" refers not only to land (ground in the narrow sense) but also to ground, water, and water in a broad sense. The base station 30 is not limited to a terrestrial base station. When the communication system 1 is a satellite communication system, the base station 30 may be an aircraft station. From the viewpoint of a satellite station, an aircraft station located on the earth is a ground station.

[0066] The base station 30 is not limited to a ground station. The base station 30 may be a non-terrestrial base station device (non-terrestrial station) that can float in the air or space. The base station 30 may be an aircraft station or a satellite station.

[0067] The satellite station is a satellite station capable of floating outside the atmosphere. The satellite station may be a device mounted on a space vehicle such as an artificial satellite, or may be the space vehicle itself. The space vehicle is a vehicle that moves outside the atmosphere. Examples of the space vehicle include artificial celestial bodies such as an artificial satellite, a spacecraft, a space station, or a probe. The satellite that becomes the satellite station may be any of a low earth orbit (LEO: Low Earth Orbiting) satellite, a medium earth orbit (MEO: Medium Earth Orbiting) satellite, a geostationary (GEO: Geostationary Earth Orbiting) satellite, or a highly elliptical orbit (HEO: Highly Elliptical Orbiting) satellite. The satellite station may be a device mounted on a low earth orbit satellite, a medium earth orbit satellite, a geostationary satellite, or a highly elliptical orbit satellite.

[0068] An aircraft station is a wireless communication device capable of floating in the atmosphere of an aircraft or the like. The aircraft station may be a device mounted on an aircraft or the like, or may be the aircraft itself. The concept of an aircraft includes not only heavier than air vehicles such as airplanes or gliders, but also lighter than air vehicles such as balloons or airships. The concept of an aircraft includes not only heavier than air vehicles or lighter than air vehicles, but also rotorcraft such as helicopters or autogyros. An aircraft station, or an aircraft equipped with an aircraft station, may be an unmanned aerial vehicle such as a drone.

[0069] The concept of unmanned aerial vehicles also includes Unmanned Aircraft Systems (UAS) and tethered UAS. The concept of unmanned aerial vehicles also includes Lighter than Air UAS (LTA) and Heavy than Air UAS (HTA). The concept of unmanned aerial vehicles also includes High Altitude UAS Platforms (HAPs).

[0070] The size of the coverage of the base station 30 may be relatively large, such as a macrocell, or relatively small, such as a picocell. The size of the coverage of the base station 30 may be extremely small, such as a femtocell. The base station 30 may have a beamforming function. The base station 30 may form a cell or a service area for each beam. Additionally or alternatively, the base station 30 may have a function of pinpointing a desired wave to a specific point by further considering distance information from the antenna of the base station 30, in addition to beamforming that gives directionality to the beam. This function may be called beam focusing or point forming.

[0071] Fig. 7 is a diagram showing the configuration of a base station 30 according to this embodiment. The base station 30 includes a wireless communication unit 31, a storage unit 32, and a control unit 33. However, the configuration shown in Fig. 7 is a functional configuration, and the hardware configuration may be different from this. Furthermore, the functions of the base station 30 may be distributed and implemented in multiple physically separated configurations.

[0072] The wireless communication unit 31 is a signal processing unit for wireless communication with other wireless communication devices (for example, a terminal device 40 or another base station 30). The wireless communication unit 31 is controlled by the control unit 33. The wireless communication unit 31 supports one or more wireless access methods. The wireless communication unit 31 may support at least one of NR, LTE, and 6G. The wireless communication unit 31 may support W-CDMA, cdma2000, and the like in addition to NR, LTE, and 6G. The wireless communication unit 31 may support an automatic retransmission technique such as HARQ (Hybrid Automatic Repeat reQuest).

[0073] The wireless communication unit 31 includes a transmission processing unit 311, a reception processing unit 312, and an antenna 313. The wireless communication unit 31 may include a plurality of transmission processing units 311, reception processing units 312, and antennas 313. When the wireless communication unit 31 supports a plurality of wireless access methods, each unit of the wireless communication unit 31 may be configured separately for each wireless access method. The transmission processing unit 311 and the reception processing unit 312 may be configured separately for LTE, NR, and 6G. The antenna 313 may be configured with a plurality of antenna elements, for example, a plurality of patch antennas. The wireless communication unit 31 may have a beamforming function. For example, the wireless communication unit 31 may have a polarization beamforming function using vertical polarization (V polarization) and horizontal polarization (H polarization) (or a polarization beamforming function using dual polarization in polarization directions of 45 degrees and -45 degrees from the vertical direction).

[0074] The transmission processing unit 311 performs a transmission process of the downlink control information and the downlink data. For example, the transmission processing unit 311 performs coding on the downlink control information and the downlink data input from the control unit 33 using a coding method such as block coding, convolution coding, turbo coding, or the like. Here, the coding may be performed using a polar code or a low density parity check code (LDPC code). Then, the transmission processing unit 311 modulates the coded bits using a predetermined modulation method such as BPSK, QPSK, 16QAM, 64QAM, 356QAM, or the like. In this case, the signal points on the constellation do not necessarily have to be equidistant. The constellation may be a non-uniform constellation (NUC). Then, the transmission processing unit 311 multiplexes the modulation symbols of each channel and the downlink reference signal, and arranges them in a predetermined resource element. Then, the transmission processing unit 311 performs various signal processes on the multiplexed signal. For example, the transmission processing unit 311 performs processes such as conversion to the frequency domain by fast Fourier transform, addition of a guard interval (cyclic prefix), generation of a baseband digital signal, conversion to an analog signal, quadrature modulation, up-conversion, removal of unnecessary frequency components, power amplification, etc. The signal generated by the transmission processing unit 311 is transmitted from an antenna 313.

[0075] The reception processing unit 312 processes the uplink signal received via the antenna 313. For example, the reception processing unit 312 performs down-conversion, removal of unnecessary frequency components, control of amplification level, orthogonal demodulation, conversion to a digital signal, removal of a guard interval (cyclic prefix), extraction of a frequency domain signal by fast Fourier transform, and the like, on the uplink signal. Then, the reception processing unit 312 separates uplink channels such as PUSCH (Physical Uplink Shared Channel) and PUCCH (Physical Uplink Control Channel) and an uplink reference signal from the signal that has been subjected to these processes. In addition, the reception processing unit 312 demodulates the received signal using a modulation method such as BPSK (Binary Phase Shift Keying) and QPSK (Quadrature Phase Shift Keying) for the modulation symbols of the uplink channel. The modulation method used for demodulation may be 16QAM (Quadrature Amplitude Modulation), 64QAM, or 356QAM. In this case, the signal points on the constellation do not necessarily have to be equidistant. The constellation may be a non-uniform constellation (NUC). Then, the reception processing unit 312 performs a decoding process on the coded bits of the demodulated uplink channel. The decoded uplink data and uplink control information are output to the control unit 33.

[0076] The antenna 313 is an antenna device that converts between electric current and radio waves. The antenna 313 may be configured with one antenna element, for example, one patch antenna. The antenna 313 may be configured with multiple antenna elements, for example, multiple patch antennas. When the antenna 313 is configured with multiple antenna elements, the wireless communication unit 31 may have a beamforming function. The wireless communication unit 31 may be configured to generate a directional beam by controlling the directivity of a wireless signal using multiple antenna elements. The antenna 313 may be a dual polarized antenna. When the antenna 313 is a dual polarized antenna, the wireless communication unit 31 may use vertical polarization (V polarization) and horizontal polarization (H polarization) (or dual polarization with polarization directions of 45 degrees and -45 degrees from the vertical direction) when transmitting a wireless signal. The wireless communication unit 31 may control the directivity of a wireless signal transmitted using vertical polarization and horizontal polarization (or dual polarization with polarization directions of 45 degrees and -45 degrees from the vertical direction). Furthermore, the wireless communication unit 31 may transmit and receive spatially multiplexed signals via multiple layers each composed of multiple antenna elements.

[0077] The storage unit 32 is a readable / writable storage device such as a DRAM, an SRAM, a flash memory, a hard disk, etc. The storage unit 32 functions as a storage means of the base station 30.

[0078] The control unit 33 is a controller that controls each unit of the base station 30. The control unit 33 controls the wireless communication unit so as to perform wireless communication with other wireless communication devices (for example, the terminal device 40 or another base station 30). The control unit 33 may be realized by a processor such as a CPU or an MPU. Specifically, the control unit 33 may be realized by a processor executing various programs stored in a storage device inside the base station 30 using a RAM or the like as a working area. The control unit 33 may be realized by an integrated circuit such as an ASIC or an FPGA. The control unit 33 may also be realized by a GPU. The CPU, the MPU, the ASIC, the FPGA, and the GPU can all be regarded as controllers. The control unit 33 may be configured by a plurality of physically separated objects. For example, the control unit 33 may be configured by a plurality of semiconductor chips.

[0079] The control unit 33 includes a transmission unit 331, a reception unit 332, and a scheduling unit 333. Each block (transmission unit 331 to scheduling unit 333) constituting the control unit 33 is a functional block indicating a function of the control unit 33. These functional blocks may be software blocks or hardware blocks. For example, each of the above-mentioned functional blocks may be a software module realized by software (including a microprogram), or may be a circuit block on a semiconductor chip (die). Of course, each functional block may be a processor or an integrated circuit. The control unit 33 may be configured by a functional unit different from the above-mentioned functional blocks. The method of configuring the functional blocks is arbitrary.

[0080] In some embodiments, the base station 30 may be configured by a set of multiple physical or logical devices. As an example, the base station 30 of this embodiment may be divided into multiple devices such as a BBU (Baseband Unit) and a RU (Radio Unit). The base station 30 may be interpreted as a set of these multiple devices. Furthermore, the base station may be either a BBU or a RU, or may be both. The BBU and the RU may be connected by a predetermined interface such as eCPRI (enhanced Common Public Radio Interface).

[0081] The RU may be referred to as an RRU (Remote Radio Unit) or an RD (Radio DoT). The RU may correspond to a gNB-DU (gNB Distributed Unit) described later. The BBU may correspond to a gNB-CU (gNB Central Unit) described later. The RU may be a device formed integrally with an antenna. The antenna of the base station 30, for example, an antenna formed integrally with the RU, may employ an Advanced Antenna System and support, for example, MIMO such as FD-MIMO or beamforming. The antenna of the base station 30 may include, for example, 64 transmitting antenna ports and 64 receiving antenna ports.

[0082] The antenna mounted on the RU may be an antenna panel composed of one or more antenna elements, and the RU may be equipped with one or more antenna panels. The RU may be equipped with two types of antenna panels, a horizontally polarized antenna panel and a vertically polarized antenna panel. The RU may be equipped with two types of antenna panels, a right-handed circularly polarized antenna panel and a left-handed circularly polarized antenna panel, or an antenna panel with a polarization direction of 45 degrees from the vertical direction and an antenna panel with a polarization direction of -45 degrees. Multiple antennas with these multiple polarization directions may be mounted on a single antenna panel. The RU may form and control an independent beam for each antenna panel.

[0083] A plurality of base stations 30 may be connected to each other. One or a plurality of base stations 30 may be included in a radio access network (RAN). In this case, the base station 30 may be simply referred to as a RAN, a RAN node, an AN (Access Network), an AN node, or the like. The RAN in LTE may be referred to as an Enhanced Universal Terrestrial RAN (EUTRAN). The RAN in NR may be referred to as an NGRAN. Furthermore, the RAN in 6G may be referred to as a 6GRAN. The RAN in W-CDMA (UMTS) may be referred to as a UTRAN.

[0084] The LTE base station 30 may be referred to as an eNodeB (Evolved Node B) or eNB. In this case, the EUTRAN includes one or more eNodeBs (eNBs). The NR base station 30 may be referred to as a gNodeB or gNB. In this case, the NGRAN includes one or more gNBs. The 6G base station may be referred to as a 6GNodeB, 6gNodeB, 6GNB, or 6gNB. In this case, the 6GRAN includes one or more 6GNBs. The EUTRAN may include a gNB (en-gNB) connected to a core network (EPC) in an LTE communication system (EPS). The NGRAN may include an ng-eNB connected to a core network 5GC in a 5G communication system (5GS).

[0085] When the base station 30 is an eNB, a gNB, a 6GNB, or the like, the base station 30 may be referred to as a 3GPP access. When the base station 30 is a wireless access point, the base station 30 may be referred to as a non-3GPP access. The base station 30 may be a radio extension device called an RRH (Remote Radio Head). When the base station 30 is a gNB, the base station 30 may be a combination of the above-mentioned gNB-CU and gNB-DU, or may be either a gNB-CU or a gNB-DU.

[0086] Here, the gNB-CU hosts multiple upper layers (e.g., Radio Resource Control (RRC), Service Data Adaptation Protocol (SDAP), and Packet Data Convergence Protocol (PDCP)) in the Access Stratum for communication with the UE. On the other hand, the gNB-DU hosts multiple lower layers (e.g., Radio Link Control (RLC), Medium Access Control (MAC), and Physical layer (PHY)) in the Access Stratum. That is, of the messages / information described below, RRC signaling (semi-static notification) may be generated by the gNB-CU, while MAC CE and DCI (dynamic notification) may be generated by the gNB-DU. Alternatively, of the RRC configuration (semi-static notification), some configurations such as IE:cellGroupConfig may be generated by the gNB-DU, and the remaining configurations may be generated by the gNB-CU. These configurations may be transmitted and received via the F1 interface described below.

[0087] The base station 30 may be configured to be able to communicate with other base stations. When the multiple base stations 30 are eNBs or a combination of an eNB and an en-gNB, the base stations 30 may be connected to each other via an X2 interface. When the multiple base stations 30 are gNBs or a combination of a gn-eNB and a gNB, the base stations 30 may be connected to each other via an Xn interface. When the multiple base stations 30 are a combination of a gNB-CU and a gNB-DU, the base stations 30 may be connected to each other via the above-mentioned F1 interface. Messages / information (e.g., RRC signaling, MAC CE (MAC Control Element), or DCI (Downlink Control Information), etc.) described later may be transmitted between the multiple base stations 30 via, for example, an X2 interface, an Xn interface, or an F1 interface.

[0088] A cell provided by the base station 30 may be referred to as a serving cell. The concept of a serving cell includes a PCell (Primary Cell) and a SCell (Secondary Cell). When dual connectivity is provided to the terminal device 40, a PCell provided by a MN (Master Node) and zero or more SCells may be referred to as a master cell group. Examples of dual connectivity include EUTRA-EUTRA Dual Connectivity, EUTRA-NR Dual Connectivity (ENDC), EUTRA-NR Dual Connectivity with 5GC, NR-EUTRA Dual Connectivity (NEDC), and NR-NR Dual Connectivity. Further examples of dual connectivity include NR-6G Dual Connectivity and 6G-NR Dual Connectivity.

[0089] The serving cell may include a PSCell (Primary Secondary Cell, or Primary SCG Cell). When dual connectivity is provided to the terminal device 40, the PSCell provided by the SN (Secondary Node) and zero or more SCells may be referred to as an SCG (Secondary Cell Group). Unless a special configuration (e.g., PUCCH on SCell) is performed, the physical uplink control channel (PUCCH) is transmitted by the PCell and PSCell, but not by the SCell. Radio link failure is detected by the PCell and PSCell, but is not detected (does not need to be detected) by the SCell. Thus, the PCell and PSCell are also referred to as SpCells (Special Cells) since they play a special role among the serving cells.

[0090] One cell may be associated with one downlink component carrier and one uplink component carrier. The system bandwidth corresponding to one cell may be divided into multiple BWPs (Bandwidth Parts). At this time, one or multiple BWPs may be set to the terminal device 40, and one BWP may be used by the terminal device 40 as an active BWP. Radio resources that the terminal device 40 can use, such as a frequency band, a numerology (subcarrier spacing), or a slot format (Slot configuration), may differ for each cell, each component carrier, or each BWP.

[0091] <2-4. Terminal device configuration> Next, the configuration of the terminal device 40 will be described.

[0092] The terminal device 40 is a wireless communication device that performs wireless communication with other wireless communication devices (for example, the base station 30 or other terminal devices 40). The terminal device 40 may be any type of information processing device (computer). For example, the terminal device 40 may be a mobile terminal such as a mobile phone, a smart device (smartphone or tablet), a PDA (Personal Digital Assistant), or a notebook PC. The terminal device 40 may also be an imaging device (for example, a camcorder) equipped with a communication function. The terminal device 40 may also be a motorcycle or a mobile broadcasting vehicle equipped with a communication device such as an FPU (Field Pickup Unit). The terminal device 40 may also be an M2M (Machine to Machine) device or an IoT (Internet of Things) device. The terminal device 40 may also be a wearable device such as a smart watch.

[0093] Furthermore, the terminal device 40 may be an xR device such as an AR (Augmented Reality) device, a VR (Virtual Reality) device, or an MR (Mixed Reality) device. In this case, the xR device may be a glasses-type device such as AR glasses or MR glasses, or a head-mounted device such as a VR head-mounted display. When the terminal device 40 is an xR device, the terminal device 40 may be a standalone device consisting of only a part worn by a user (e.g., a glasses part). Furthermore, the terminal device 40 may be a terminal-linked device consisting of a part worn by a user (e.g., a glasses part) and a terminal part linked to the part (e.g., a smart device).

[0094] The terminal device 40 may be capable of NOMA communication with the base station 30. The terminal device 40 may be able to use an automatic repeat technique such as HARQ when communicating with the base station 30. The terminal device 40 may be capable of sidelink communication with another terminal device 40. The terminal device 40 may be able to use an automatic repeat technique such as HARQ when performing sidelink communication. The terminal device 40 may be capable of NOMA communication when performing sidelink communication with another terminal device 40. The terminal device 40 may be capable of LPWA communication with other wireless communication devices such as the base station 30. The wireless communication used by the terminal device 40 may be wireless communication using millimeter waves. The wireless communication used by the terminal device 40, including sidelink communication, may be wireless communication using radio waves, or wireless communication using infrared rays or visible light, i.e., optical wireless.

[0095] The terminal device 40 may be a wireless communication device that can be moved, that is, a mobile device. The terminal device 40 may be a wireless communication device installed in a mobile device, or may be the mobile device itself. The terminal device 40 may be a vehicle that moves on a road, such as an automobile, a bus, a truck, or a motorcycle, or may be a wireless communication device mounted on the vehicle. The mobile device may be a mobile terminal, or may be a mobile device that moves on land (ground in the narrow sense), underground, on water, or underwater. The mobile device may be a mobile device that moves within the atmosphere, such as an airplane, an airship, a balloon, or a helicopter, or may be a mobile device that moves outside the atmosphere, such as an artificial satellite. The mobile device may be a UAV (Unmanned Aerial Vehicle) such as a drone. The terminal device 40 may be a wireless communication device mounted on a mobile device.

[0096] The terminal device 40 may be capable of connecting to and communicating with a plurality of base stations 30 or a plurality of cells at the same time. When one base station 30 supports a communication area via a plurality of cells (for example, pCell or sCell), the plurality of cells can be bundled together and communication can be performed between the base station 30 and the terminal device 40 by using a carrier aggregation (CA) technology, a dual connectivity (DC) technology, a multi-connectivity (MC) technology, or the like. Alternatively, communication can be performed between the terminal device 40 and the plurality of base stations 30 via cells of different base stations 30 by a coordinated multi-point transmission and reception (CoMP) technology.

[0097] The terminal device 40 may be a relay terminal that relays communications to a remote terminal.

[0098] Fig. 8 is a diagram showing the configuration of a terminal device 40 according to this embodiment. The terminal device 40 includes a wireless communication unit 41, a storage unit 42, a control unit 43, and an external interface 44. The configuration shown in Fig. 8 is a functional configuration, and the hardware configuration may be different from this. Furthermore, the functions of the terminal device 40 may be distributed and implemented in multiple physically separated configurations.

[0099] The wireless communication unit 41 is a signal processing unit for wireless communication with other wireless communication devices (e.g., the base station 30 or other terminal devices 40). The wireless communication unit 41 is controlled by the control unit 43. The wireless communication unit 41 supports one or more wireless access methods. The wireless communication unit 41 may support at least one of NR, LTE, and 6G. The wireless communication unit 41 may support W-CDMA, cdma2000, etc. in addition to NR, LTE, and 6G. The wireless communication unit 41 may support an automatic retransmission technique such as HARQ (Hybrid Automatic Repeat reQuest).

[0100] The wireless communication unit 41 includes a transmission processing unit 411, a reception processing unit 412, and an antenna 413. The wireless communication unit 41 may include a plurality of transmission processing units 411, reception processing units 412, and antennas 413. When the wireless communication unit 41 supports a plurality of wireless access methods, each unit of the wireless communication unit 41 may be configured separately for each wireless access method. The transmission processing unit 411 and the reception processing unit 412 may be configured separately for LTE, NR, and 6G. The antenna 413 may be configured with a plurality of antenna elements, for example, a plurality of patch antennas. The wireless communication unit 41 may have a beamforming function. For example, the wireless communication unit 41 may have a polarized beamforming function using vertically polarized waves (V polarized waves) and horizontally polarized waves (H polarized waves) (or a polarized beamforming function using dual polarized waves in polarization directions of 45 degrees and -45 degrees from the vertical direction).

[0101] The storage unit 42 is a readable / writable storage device such as a DRAM, an SRAM, a flash memory, a hard disk, etc. The storage unit 42 functions as a storage unit of the terminal device 40.

[0102] The control unit 43 is a controller that controls each unit of the terminal device 40. The control unit 43 controls the wireless communication unit so as to perform wireless communication with other wireless communication devices (for example, the base station 30 or other terminal devices 40). The control unit 43 may be realized by a processor such as a CPU or MPU. In detail, the control unit 23 may be realized by a processor executing various programs stored in a storage device inside the terminal device 40 using a RAM or the like as a working area. The control unit 43 may be realized by an integrated circuit such as an ASIC or FPGA. The CPU, MPU, ASIC, and FPGA can all be considered as controllers. The control unit 43 may be realized by a GPU. The CPU, MPU, ASIC, FPGA, and GPU can all be considered as controllers. The control unit 43 may be configured by multiple physically separated objects. For example, the control unit 43 may be configured by multiple semiconductor chips.

[0103] The control unit 43 includes a transmitting unit 431, a receiving unit 432, a measuring unit 433, and an identifying unit 434. Each block (the transmitting unit 431 to the identifying unit 434) constituting the control unit 43 is a functional block indicating a function of the control unit 43. These functional blocks may be software blocks or hardware blocks. For example, each of the above-mentioned functional blocks may be a software module realized by software (including a microprogram), or may be a circuit block on a semiconductor chip (die). Of course, each functional block may be a processor or an integrated circuit. The control unit 43 may be configured by a functional unit different from the above-mentioned functional blocks. The method of configuring the functional blocks is arbitrary.

[0104] The external interface 44 is a communication interface for connecting the terminal device 40 to another terminal device (external device). The external interface 44 may be a wired interface such as a Universal Serial Bus (USB) or a wired LAN, or a wireless interface such as a wireless LAN or Bluetooth.

[0105] The configuration of the communication system 1 has been described above. Next, the operation of the communication system 1 of this embodiment will be described.

[0106] <<3. Embodiment 1>> First, the operation of the communication system 1 according to the first embodiment will be described.

[0107] <3-1. Example of functional configuration> First, there will be shown an example of a functional configuration of the communication device according to embodiment 1. The communication device (terminal device 40) according to embodiment 1 can be configured as follows.

[0108] Fig. 9 is a functional block diagram of the terminal device 40 according to the first embodiment. The terminal device 40 includes a block for performing processing of a Packet Data Convergence Protocol (PDCP) layer (PDCP shown in Fig. 9), a block for performing processing of a Radio Link Control (RLC) layer (RLC shown in Fig. 9), a block for performing processing of a Medium Access Control (MAC) layer (MAC shown in Fig. 9), and a block for performing processing of a physical layer (PHY shown in Fig. 9). These blocks can be realized by, for example, the wireless communication unit 41 and the control unit 43 shown in Fig. 8. The terminal device 40 also includes an RLC buffer. This block can be realized by, for example, the storage unit 42 shown in Fig. 8.

[0109] The terminal device 40 also includes a data transmission / reception unit. This block can be realized, for example, by the transmission unit 431 and reception unit 432 shown in FIG. 8. The terminal device 40 also includes a time information management unit. This block can be realized, for example, by the measurement unit 433 and storage unit 42 shown in FIG. 8. The time information management unit notifies the RLC of time information. The time information managed by the time information management unit may be, for example, a frame number, or a free-running clock managed by a processor. If the time information is a frame number, the time information management unit may be synchronized with the PHY.

[0110] <3-2. Operation details> Next, the operation of the communication device (terminal device 40) according to the first embodiment will be described.

[0111] In the first embodiment, the terminal device 40 measures the residence time of one or more packets to be transmitted to another communication device for each packet. For example, the terminal device 40 measures the residence time of one or more uplink packets to be transmitted to the base station 30 for each packet. Then, the terminal device 40 transmits residence time information including information on the residence time to the base station 30. The base station 30 schedules the uplink communication based on the received residence time information. More specifically, the operation of this communication system 1 (the base station 30 and the terminal device 40) can be described as the following means 1-1 to means 1-3. Note that the above-mentioned or later-described packet may be a collection of data (e.g., bit string, bit sequence) that can be processed or transmitted per unit time. For example, the above-mentioned or later-described packet may be a Protocol Data Unit (PDU) or Service Data Unit (SDU) in a certain layer (e.g., PDCP, RLC, MAC, PHY). A PDU is a collection of data (e.g., bit string) in which a header in a certain layer is added to an SDU in the certain layer. When a PDU is passed to a lower layer, it becomes an SDU of the lower layer. An SDU corresponds to a PDU provided from a higher layer of a certain layer, and is a collection of data (e.g., a bit string) to be processed in a certain layer. Additionally or alternatively, the above or below described packets may be called segments or frames.

[0112] (1) Means 1-1 (average residence time) The terminal device 40 measures the residence time of one or more uplink packets to be transmitted to the base station 30 for each packet, and determines the average residence time (hereinafter, also referred to as the average residence time) based on the measurement value for each packet. At this time, the RLC of the terminal device 40 may calculate the residence time of the remaining PDU at the timing when the MAC notifies the completion of the transmission of the RLC PDU, and may store the calculated average residence time in a buffer. The terminal device 40 may determine the average residence time for each LCG (Logical Channel Group) (or for each logical channel). Since information is stored in the BSR for each LCG, when the priorities of the logical channels mapped to the same LCG are different, the value of the logical channel to which the highest priority is set may be prioritized. The average residence time (average residence time) may be a moving average value.

[0113] This average value is assumed to be related to the resource allocation period for the terminal (LCG). The terminal device 40 transmits the residence time information including this average residence time to the base station 30. At this time, the terminal device 40 may transmit the residence time information to the base station by including it in the BSR. For example, the terminal device 40 acquires the average residence time at the timing when the transmission of the BSR is triggered. Then, the terminal device 40 transmits the residence time information including information on the average value to the base station 30 by including it in the BSR. When the residence time information is included in the BSR, a new area for storing the residence time information may be provided in the BSR. The base station 30 extracts the residence time information from the received BSR. Then, the base station 30 schedules the uplink communication based on the residence time information (for example, information on the average residence time).

[0114] (2) Means 1-2 (maximum residence time) The average residence time of the means 1-1 is calculated based on past measurement values. Therefore, the means 1-1 is assumed to be vulnerable to instantaneous delay fluctuations (jitter). Therefore, the terminal device 40 may transmit information on the maximum value of the residence time (hereinafter also referred to as the maximum residence time) to the base station 30.

[0115] For example, the terminal device 40 measures the residence time of one or more uplink packets to be transmitted to the base station 30 for each packet, and identifies the maximum residence time (maximum residence time) based on the measurement value for each packet. At this time, the RLC of the terminal device 40 may calculate the residence time of the remaining PDU at the timing when the MAC notifies the completion of the transmission of the RLC PDU, and may store the calculated maximum residence time in a buffer. The terminal device 40 may identify the maximum residence time for each LCG (or for each logical channel). The terminal device 40 identifies the maximum residence time among the residence times of multiple RLC PDUs that are retained in the LCG. Since information is stored in the BSR for each LCG, when the priorities of logical channels mapped to the same LCG are different, the value of the logical channel to which the highest priority is set may be prioritized.

[0116] The terminal device 40 transmits the hold time information including the maximum hold time to the base station 30. At this time, the terminal device 40 may include the hold time information in the BSR and transmit it to the base station. For example, the terminal device 40 acquires the maximum value of the hold time at the timing when the transmission of the BSR is triggered, and transmits the hold time information including the maximum value to the base station 30. The terminal device 40 may transmit the hold time information to the base station 30 every time the terminal device 40 transmits an uplink packet to the base station. For example, the terminal device 40 may load the BSR including the maximum hold time at the timing of transmitting the MAC PDU on the PUSCH in order to update the hold time information every time the terminal device 40 transmits the MAC PDU to the base station 30. When the hold time information is included in the BSR, a new area for storing the hold time information may be provided in the BSR. The base station 30 extracts the hold time information from the received BSR. Then, the base station 30 schedules the uplink communication based on the hold time information (for example, information on the maximum hold time).

[0117] (3) Measures 1-3 (hybrid of measures 1-1 and 1-2) It is assumed that multiple RLC PDUs are retained in the LCG. Therefore, if the terminal device 40 notifies the base station 30 of the longest retention time among the retention times of multiple RLC PDUs retained in the LCG, the base station 30 may apply that retention time to other RLC PDUs when scheduling. This problem can be avoided if the terminal device 40 transmits information on the average retention time to the base station in addition to information on the maximum retention time.

[0118] For example, the terminal device 40 specifies the average value of the residence time in addition to the maximum value of the residence time. Then, the terminal device 40 transmits residence time information including at least information on the maximum residence time and information on the average residence time to the base station 30. At this time, when transmitting the first PDU, the terminal device 40 includes information on the maximum residence time in the BSR, and when transmitting other PDUs, includes information on the average residence time in the BSR. As an application example, the terminal device 40 may notify the residence times for N PDUs. If the packet arrival frequency is known depending on the service, the management device 20, the base station 30, or the terminal device 40 may specify the value of N based on the BSR notification frequency.

[0119] (4) Other measures In the means 1-1 to 1-3, the terminal device 40 specifies the average value (average residence time) and / or the maximum value (maximum residence time) based on the measurement value for each packet. That is, in the means 1-1 to 1-3, the current or past value of the residence time of the packet is specified. However, the terminal device 40 may specify a future value (predicted value) of the residence time of the packet. For example, the terminal device 40 specifies a predicted value of the residence time (hereinafter, referred to as predicted residence time) in addition to the average value and / or maximum value of the residence time. At this time, the terminal device 40 may predict the future residence time using AI (Artificial Intelligence) / ML (Machine Learning). For example, the terminal device 40 may predict the future residence time by inputting the measurement value for each packet into a learning model that has been trained in advance using past data. In addition, the terminal device 40 may specify the predicted residence time for each LCG (or for each logical channel).

[0120] Then, the terminal device 40 transmits to the base station 30 the residence time information including information on the predicted residence time. The residence time information may include information on the maximum residence time and / or the maximum residence time described above. At this time, the terminal device 40 may transmit the residence time information to the base station by including it in the BSR. For example, the terminal device 40 acquires a predicted value of the residence time at the timing when the transmission of the BSR is triggered, and transmits the residence time information including information on the predicted value to the base station 30 by including it in the BSR. Note that the terminal device 40 may transmit the residence time information to the base station 30 every time it transmits an uplink packet to the base station. The base station 30 extracts the residence time information from the received BSR. Then, the base station 30 schedules the uplink communication based on the residence time information (for example, information on the maximum residence time and the predicted residence time).

[0121] The dwell time is not limited to the above times (maximum dwell time, average dwell time, predicted dwell time, and combinations thereof) and may be, for example, a representative value (for example, a maximum value for a certain period of time, etc.).

[0122] <3-3.BSR format example> As described above, the terminal device 40 transmits a BSR (Buffer Status Report) including the residence time information to the base station 30. At this time, a new area for storing the residence time information may be provided in the BSR.

[0123] Fig. 10 and Fig. 11 are diagrams showing an example of a BSR format capable of storing retention time information. Specifically, Fig. 10 and Fig. 11 show an example in which a new area for storing retention time information is provided in the format of the BSR MAC CE (Control Element) defined in 3GPP TS38.321 for NR. Fig. 10 shows an example of a short BSR, and Fig. 11 shows an example of a long BSR. In the examples of Fig. 10 and Fig. 11, a new area (Buffered Time area) for notifying a one-octet retention time is provided for each LCG ID (Logical Channel Group ID).

[0124] In addition, a new area (Buffered Time area) for notifying the retention time may be provided by compressing the Buffer Size area. Figs. 12 and 13 are diagrams showing other examples of BSR formats capable of storing retention time information. Fig. 12 shows an example of a Short BSR, and Fig. 13 shows an example of a Long BSR. In the examples of Figs. 12 and 13, a new area (Buffered Time area) for notifying the retention time is provided by compressing a one-octet Buffer Size area. Although the resolution is inferior to the examples shown in Figs. 10 and 11, fewer resources are required for notifying retention time information.

[0125] The value stored in the Buffered Time field may be a value at the initial transmission timing. Also, the value stored in the Buffered Time field may be a value in msec, slot, or subframe units. Also, the value stored in the Buffered Time field may be a table lookup value.

[0126] The terminal device 40 may use the region (Buffered Time region) by default, or may use the region only when a predetermined condition is satisfied. That is, the terminal device 40 may transmit the retention time information to the base station 30 only when a predetermined condition is satisfied. For example, when the delay request satisfies a predetermined criterion (for example, when the Packet Delay Budget requirement is XX msec or less (for example, 10 msec or less) in 5QI / QCI), the terminal device 40 may include the retention time information in the BSR and transmit it to the base station 30. Alternatively, when the slice used is a low-delay slice, the terminal device 40 may include the retention time information in the BSR and transmit it to the base station 30. Of course, the terminal device 40 may be configured to transmit the retention time to the base station 30 regardless of whether the delay request satisfies the predetermined criterion or not.

[0127] <3-4. Sequence example> Based on the above, the communication process executed by the communication system 1 of the first embodiment will be described.

[0128] Fig. 14 is a sequence diagram showing the communication process of the first embodiment. The terminal device 40 shown in Fig. 14 is configured so that data to be transmitted is generated internally (APP Layer in the figure). The terminal device 40 is also configured so that the data to be transmitted is received from another communication device (e.g., another terminal device 40) via an external interface (Ext IF in the figure). In the following description, the data to be transmitted may be referred to as transmission data. The communication process of the first embodiment will be described below with reference to Fig. 14.

[0129] The terminal device 40, the base station 30, and the core network (e.g., the management device 20) execute processes (e.g., initial settings and initial connection processes) for starting a communication service (step S101). The cellular modem (e.g., the wireless communication unit 41 and / or the control unit 43) of the terminal device 40, the base station 30, and the core network construct a low-latency slice (step S102).

[0130] When transmission data is generated inside the terminal device 40 (or when transmission data is received from another communication device), the terminal device 40 transmits the data to the cellular modem (step S103). When the cellular modem of the terminal device 40 receives the data, it timestamps the reception time of the data. For example, the cellular modem (e.g., the measurement unit 433) may add the reception time of the data to the received data, or may manage the data reception time separately from the data. The terminal device 40 then stores the received data (packet) in a buffer. Thereafter, the terminal device 40 repeats this operation (hereinafter, description of this operation will be omitted).

[0131] Next, the terminal device 40 makes a scheduling request to the base station 30 (step S104). The base station 30 schedules uplink communication and issues a scheduling grant to the terminal device 40 (step S105).

[0132] Next, the terminal device 40 specifies the residence time of the data (packets) stored in the buffer. For example, the terminal device 40 specifies at least one of the average residence time, the maximum residence time, and the predicted residence time (step S106). In the following description, it is assumed that the terminal device 40 specifies the maximum residence time as an example. The terminal device 40 transmits residence time information including information on the maximum residence time to the base station 30 by including it in the BSR (step S107).

[0133] The base station 30 receives the staying time information from each of the multiple terminal devices 40. The base station 30 that has received the staying time information performs scheduling based on the staying time information (for example, the maximum staying time) (step S108). The base station 30 may hold the time when the staying time information is received and correct the received staying time information at the scheduling timing.

[0134] Fig. 15 is a diagram for explaining scheduling that takes retention time into consideration. By receiving retention time information from the terminal device 40, the base station 30 can recognize which buffer in the terminal device 40 has the longest data retention time. The base station 30 can use the retention time information as a scheduling coefficient. In the example of Fig. 15, the retention time of the terminal device 402 is 20 ms, which is the longest, so the base station 30 allocates radio resources to the terminal device 402 with priority.

[0135] Returning to FIG. 14, the base station 30 issues a scheduling grant to the terminal device 40 based on the scheduling result (step S109).

[0136] Next, the terminal device 40 identifies the retention time of the data (packets) stored in the buffer (step S110). Then, the terminal device 40 stores retention time information including information on the maximum retention time in the BSR. The terminal device 40 transmits the data together with the BSR to the base station 30 based on the scheduling grant (step S111).

[0137] The base station 30 receives the BSR transmitted together with the data (packet) from the terminal device 40. Then, the base station 30 performs scheduling based on the residence time information included in the BSR (step S112). Based on the scheduling result, the base station 30 issues a scheduling grant to the terminal device 40 (step S113).

[0138] The terminal device 40 identifies the retention time of the data (packets) stored in the buffer (step S114). Then, the terminal device 40 transmits the data to the base station 30 together with the BSR storing the retention time information (step S115).

[0139] According to the first embodiment, the base station 30 can grasp the retention of data buffered in each terminal device 40. This allows the base station 30 to perform scheduling taking into consideration the retention time. As a result, low-latency wireless communication is realized even in uplink communication, so that the communication system 1 can realize wireless communication with high communication performance (for example, stable low-latency wireless communication).

[0140] <<4. Second embodiment>> Next, the operation of the communication system 1 according to the second embodiment will be described.

[0141] <4-1. Example of functional configuration> First, there will be shown an example of a functional configuration of a communication device according to embodiment 2. The communication device (terminal device 40, base station 30) according to embodiment 2 can be configured as follows.

[0142] <Example of terminal device functional configuration> FIG. 16 is a functional block diagram of a terminal device 40 according to the second embodiment. The terminal device 40 includes a block for performing PDCP layer processing (PDCP shown in FIG. 16), a block for performing RLC layer processing (RLC shown in FIG. 16), a block for performing MAC layer processing (MAC shown in FIG. 16), and a block for performing physical layer processing (PHY shown in FIG. 16). These blocks can be realized, for example, by the wireless communication unit 41 and the control unit 43 shown in FIG. 8. The terminal device 40 also includes a data transmission / reception unit. This block can be realized, for example, by the transmission unit 431 and the reception unit 432 shown in FIG. 8. The terminal device 40 also includes a time information management unit. This block can be realized, for example, by the measurement unit 433 and the storage unit 42 shown in FIG. 8. The time information management unit notifies the PDCP of time information. The time information managed by the time information management unit is, for example, a frame number. The time information management unit synchronizes the frame number with the PHY.

[0143] <Example of base station functional configuration> FIG. 17 is a functional block diagram of the base station 30 according to the second embodiment. The base station 30 includes a block for performing PDCP layer processing (PDCP shown in FIG. 17), a block for performing RLC layer processing (RLC shown in FIG. 17), a block for performing MAC layer processing (MAC shown in FIG. 17), and a block for performing physical layer processing (PHY shown in FIG. 17). These blocks can be realized by, for example, the wireless communication unit 31 and the control unit 33 shown in FIG. 7. The base station 30 also includes a data transmission / reception unit. This block can be realized by, for example, the transmission unit 331 and the reception unit 332 shown in FIG. 7. The base station 30 also includes a time information management unit. This block can be realized by, for example, the control unit 33 and the storage unit 32 shown in FIG. 7. The time information management unit notifies the PDCP of time information. The time information managed by the time information management unit is, for example, a frame number. The time information management unit synchronizes the frame number with the PHY.

[0144] <4-2. Operation details> Next, the operation of the communication device (terminal device 40, base station 30) according to the second embodiment will be described.

[0145] In the second embodiment, the terminal device 40 assigns time information (hereinafter also referred to as a timestamp) to each of one or more packets to be transmitted to another communication device. For example, the terminal device 40 assigns a timestamp to each of one or more packets to be transmitted to the base station 30. For example, when generating a PDU in PDCP or RLC, the terminal device 40 assigns a timestamp (for example, the generation time of the PDU) to the PDU. When the terminal device 40 receives a packet (PDCP SDU) from the data transmission / reception unit, it may assign a timestamp (current time) to the beginning of the SDU.

[0146] In this case, the timestamp may be SFN (System Frame Number) / HFN (Hyper Frame Number) or may be a subframe number. For example, the timestamp may be the lower 12 bits of HFN (Hyper Frame Number) and a subframe number estimated in the PDCP layer. The terminal device 40 may use a slot number as the timestamp instead of a subframe number. When using a slot number as the timestamp, the terminal device 40 extends the timestamp area according to SCS (SubCarrier Spacing), as described later.

[0147] The HFN is treated as a free-running counter in the PDCP layer. When the subframe number / slot number is used as a timestamp, the terminal device 40 may determine the subframe number / slot number based on the time elapsed since the HFN counter was updated. For example, if the timing at which the process is executed is 2 msec after the HFN was updated, the terminal device 40 sets the subframe number to 1. Here, the subframe number is in 1 msec units and starts from 0.

[0148] The base station 30 synchronizes the time with the terminal device 40 in advance. For example, the base station 30 synchronizes the terminal device 40 with the SFN / HFN in advance using an RRC message or the like. When the base station 30 receives a packet from the terminal device 40, the base station 30 identifies the time required for transmitting the packet (hereinafter referred to as the transmission delay time) based on the timestamp added to the packet. For example, when the PDCP of the base station 30 generates a PDCP SDU from a packet, the PDCP extracts a timestamp (e.g., SFN / HFN / subframe number / slot number) from the packet. Then, the base station 30 identifies the transmission delay time of the packet from the difference between the timestamp and the current time (e.g., SFN / HFN / subframe number / slot number). The terminal device 40 may estimate the subframe number / slot number to be the current time based on the time elapsed since the HFN count-up timing.

[0149] Then, the base station 30 schedules the terminal device 40 based on the information of the identified transmission delay time. For example, the PDCP of the base station 30 notifies the MAC scheduler of the information of the identified transmission delay time. The MAC scheduler schedules uplink communication based on the information of the transmission delay time.

[0150] <4-3.PDU format> As described above, the terminal device 40 transmits a PDU to which a timestamp is added to the base station 30. At this time, a new area for storing the timestamp may be provided in the PDU. Fig. 18 is a diagram showing an example of a format of a PDU capable of storing a timestamp. Specifically, Fig. 18 shows an example of a format of an RLC AM (Acknowledge Mode) PDU in which an area for storing a timestamp (hereinafter, referred to as a timestamp area) is newly provided. In Fig. 18, a 2-octet timestamp area is newly provided in the PDU.

[0151] (Expansion of timestamp area) In LTE, the subframe number is unified at 1 msec, but in NR, the actual transmission unit is a slot. In addition, the slot length differs depending on the SCS (SubCarrier Spacing) of the target RAT, so the measurable granularity of the delay time differs. FIG. 19 is a diagram for explaining the measurable granularity of the delay time. FIG. 19 was created with reference to TS38.211 Table 4.3.2-1 of 3GPP. The time (62.5 usec to 1 msec) shown in parentheses in the figure is the time of one communication opportunity when the communication scheme described in the reference is applied. When notifying the minimum measurement unit, the terminal device 40 extends the above-mentioned time stamp area. In addition, in the case of μ=0, the terminal device 40 may prepare a time stamp area of ​​3 octets, set Reserved to 8 bits, and combine it with other μ. In addition, whether to extend the time stamp area may be set in advance by system settings, etc.

[0152] <4-4. Sequence example> Based on the above, the communication process executed by the communication system 1 of the second embodiment will be described.

[0153] FIG. 20 is a sequence diagram showing communication processing of the second embodiment. The terminal device 40 shown in FIG. 20 is configured to generate data to be transmitted internally (APP Layer in the figure). The terminal device 40 is also configured to receive data to be transmitted from another communication device (e.g., another terminal device 40) via an external interface (Ext IF in the figure). In the following description, data to be transmitted may be referred to as transmission data. In the example of FIG. 20, it is assumed that the HFNs of the base station 30 and the terminal device 40 are synchronized by an RRC message or the like. Hereinafter, the communication processing of the first embodiment will be described with reference to FIG. 20.

[0154] The terminal device 40, the base station 30, and the core network (for example, the management device 20) execute processes for starting a communication service (for example, initial setting and initial connection processes, etc.) (step S201).

[0155] When transmission data is generated inside the terminal device 40 (or when transmission data is received from another communication device), the terminal device 40 generates an SDU based on the transmission data and transmits the SDU to the PDCP (step S202). The PDCP of the terminal device 40 generates a PDU based on the received SDU and assigns a timestamp to the PDU (step S203). Then, the PDCP of the terminal device 40 transmits the PDU with the timestamp assigned to the cellular modem (step S204). Then, the cellular modem stores the received PDU in a buffer. Thereafter, the terminal device 40 repeats this operation (hereinafter, description of this operation will be omitted).

[0156] Next, the terminal device 40 makes a scheduling request to the base station 30 (step S205). The base station 30 schedules uplink communication and issues a scheduling grant to the terminal device 40 (step S206). The terminal device 40 transmits a BSR to the base station 30 based on the grant (step S207). The base station 30 schedules uplink communication and issues a scheduling grant to the terminal device 40 (step S208). The terminal device 40 transmits data (a PDU with a timestamp attached) to the base station 30 based on the grant (step S209). At this time, the terminal device 40 may transmit a BSR together with the data.

[0157] The base station 30 receives data (PDUs with timestamps) from each of the multiple terminal devices 40. The base station 30 extracts the timestamps from the PDUs and identifies a delay time based on the timestamps (step S210). Then, the base station 30 performs scheduling based on the identified delay time (for example, maximum delay time / average delay time).

[0158] FIG. 21 is a diagram for explaining scheduling that takes delay time into consideration. The base station 30 specifies the transmission delay time of the PDU from the difference between the timestamp extracted from the PDU and the current time (for example, HFN). The delay time specified by the base station 30 may be the average delay time of multiple packets or the maximum delay time of multiple packets. The delay time specified by the base station 30 may be the delay time for each LCG (average delay time / maximum delay time). The base station 30 can recognize which terminal device 40 has a large delay time by receiving delay time information from the terminal device 40. The base station 30 can use the delay time information as a scheduling coefficient. In the example of FIG. 21, the delay time of the terminal device 402 is 20 ms, which is the longest, so the base station 30 allocates radio resources to the terminal device 402 with priority.

[0159] 20, the base station 30 issues a scheduling grant to the terminal device 40 based on the scheduling result (step S211). The terminal device 40 transmits data (a PDU with a timestamp added) to the base station 30 based on the grant (step S212).

[0160] According to the second embodiment, the base station 30 can grasp the transmission delay time of each terminal device 40. This allows the base station 30 to perform scheduling taking the delay time into consideration. As a result, low-latency wireless communication is realized even in uplink communication, so that the communication system 1 can realize wireless communication with high communication performance (for example, stable low-latency wireless communication).

[0161] <<5. Embodiment 3>> Next, the operation of the communication system 1 according to the third embodiment will be described.

[0162] <5-1. Example of functional configuration> First, there will be shown an example of a functional configuration of a communication system according to embodiment 3. The communication system according to embodiment 3 (communication system 1) can be configured as follows.

[0163] <Example of functional configuration of a communication system> FIG. 22 is a functional block diagram of a communication system 1 according to the third embodiment. The communication system 1 includes an application function (AF shown in FIG. 22), a core network (Core shown in FIG. 22), a radio access network (RAN shown in FIG. 22), a block for performing application layer processing (App shown in FIG. 22), and a wireless communication function of a user device (UE Modem shown in FIG. 22). The AF may be realized by, for example, the server 10 shown in FIG. 4. The Core may be realized by, for example, the management device 20 shown in FIG. 4. The RAN may be realized by, for example, the base station 30 shown in FIG. 4. The App and the UE Modem may be realized by, for example, the terminal device 40 shown in FIG. 4. The App and the UE Modem may be configured by one terminal device 40 or may be configured by separate terminal devices 40. The UE Modem can be rephrased as a cellular modem.

[0164] <Example of terminal device functional configuration> As described above, the UE Modem may be realized by the terminal device 40. FIG. 23 is a functional block diagram of the terminal device 40 according to the third embodiment. The terminal device 40 includes a data transmission / reception unit, a time information management unit, a packet processing unit, a block for performing RLC layer processing (RLC shown in FIG. 16), a block for performing MAC layer processing (MAC shown in FIG. 16), and a block for performing physical layer processing (PHY shown in FIG. 16). The packet processing unit includes a block for performing PDCP layer processing (PDCP shown in FIG. 23). The data transmission / reception unit may be realized by, for example, the transmission unit 431 and the reception unit 432 shown in FIG. 8. The time information management unit may be realized by, for example, the measurement unit 433 and the storage unit 42 shown in FIG. 8. The packet processing unit to the PHY may be realized by, for example, the wireless communication unit 41 and the control unit 43 shown in FIG. 8.

[0165] The data transmission / reception unit is an interface with the App. The data transmission destination / data reception source of the data transmission / reception unit may be a communication device (external App) in a housing separate from the terminal device 40. Also, the data transmission destination / data reception source of the data transmission / reception unit may be an internal block (internal App) of the terminal device 40. For example, the data transmission destination / data reception source may be an App processor or a sensor in the same housing.

[0166] The time information management unit manages the time autonomously. Alternatively, the time information management unit manages the time based on an external source. Since it is only necessary for the terminal device 40 to know the difference between the two times (the residence time of the data (packets) stored in the buffer), the time information management unit may manage the time with a autonomous clock as long as the relative time can be managed correctly.

[0167] When the packet processor receives a UL packet from the data transmitter / receiver, it stores the time. The packet processor then receives from the MAC the time when the last (or first) MAC PDU of multiple MAC PDUs related to the packet was transmitted. The packet processor then calculates the residence time of the data (packet) stored in the buffer based on the reception time of the UL packet and the transmission time of the MAC PDU. The packet processor notifies the AF of the residence time at regular intervals.

[0168] <Server functional configuration example> As described above, AF may be realized by the server 10. Note that AF may be part of the functions of the core network. In this case, AF may be realized by the management device 20. Of course, AF may be realized by an information processing device (computer) other than the server 10 and the management device 20. In the following description, as an example, AF is assumed to be realized by the server 10.

[0169] Fig. 24 is a functional block diagram of the server 10 according to the third embodiment. The server 10 includes a data transmission / reception unit, a residence time storage unit, a QoS management unit, a priority control unit, and a NEF (Network Exposure Function) / SCEF (Service Capability Exposure Function) interface unit. These blocks can be realized by, for example, the communication unit 11, the storage unit 12, and the control unit 13 shown in Fig. 5.

[0170] The data transmitter / receiver has a function of receiving the residence time notified from the packet processor of the terminal device 40. The data transmitter / receiver may also function as an interface with the NEF / SCEF of the core network. These two functions may be independent.

[0171] The staying time storage unit stores the staying time notified from the terminal device 40. The staying time storage unit manages, for each terminal device 40, a representative value (for example, a maximum value for a certain period of time, etc.).

[0172] The QoS management unit manages the target service level (target delay time) of the service / application that the terminal device 40 is using.

[0173] The priority control unit compares the residence time stored in the residence time management unit with the service level managed by the QoS management unit for each terminal device 40. The priority control unit notifies the NEF / SCEF interface unit to increase the priority of a terminal device 40 that does not meet the service level. The priority control unit may also determine to lower the priority of a terminal device 40 that fully meets the service level.

[0174] The NEF / SCEF interface unit notifies the core network of the change in target priority for the terminal device 40 that has been notified of the change in priority, using an API (Application Programming Interface).

[0175] <5-2. Operation details> Next, the operation of the communication system 1 according to the second embodiment will be described.

[0176] In the third embodiment, the terminal device 40 measures the residence time of one or more packets to be transmitted to another communication device (e.g., the base station 30) for each packet. Then, the terminal device 40 notifies the AF (e.g., the server 10) of residence time information including information on the residence time. Note that, as in the first embodiment, the residence time notified to the AF may be an average residence time, a maximum residence time, a predicted residence time, or a combination of these times. Also, the residence time may be a representative value (e.g., a maximum value for a certain period of time, etc.). Note that the residence time notified to the AF may be a residence time for each LCG (or for each logical channel).

[0177] Based on the notified information on the residence time, the AF resets the QoS (Quality of Service) for the terminal device 40. For example, based on the information on the residence times of the terminal devices 40 and the SLA (Service Level Agreement) of each service, the AF resets the QoS (CQI / 5QI) using NEF_AfsessionWithQoS in accordance with the Delay Budget set for each service. The base station 30 schedules uplink communications based on the changed QoS.

[0178] <5-3. Sequence example> Based on the above, the communication process executed by the communication system 1 of the third embodiment will be described.

[0179] Fig. 25 is a sequence diagram showing the communication process of the first embodiment. The terminal device 40 shown in Fig. 25 is configured so that data to be transmitted is generated internally (APP Layer in the figure). The terminal device 40 is also configured so that the data to be transmitted is received from another communication device (e.g., another terminal device 40) via an external interface (Ext IF in the figure). In the following description, the data to be transmitted may be referred to as transmission data. The communication process of the third embodiment will be described below with reference to Fig. 25.

[0180] The terminal device 40, the base station 30, and the core network (e.g., the management device 20) execute processes (e.g., initial settings and initial connection processes) for starting a communication service (step S301). The cellular modem (e.g., the wireless communication unit 41 and / or the control unit 43) of the terminal device 40, the base station 30, and the core network construct a low-latency slice (step S302).

[0181] When transmission data occurs inside the terminal device 40 (APP Layer) (or when the external interface 44 receives transmission data from another communication device), the terminal device 40 transmits the data to the cellular modem inside the terminal device 40 (step S303). The terminal device 40 converts the data into packets (SDU / PDU) in a predetermined format and stores the converted packets in a buffer. Then, based on a grant issued by the base station 30, the terminal device 40 transmits the packets in the buffer to the base station 30 (step S304). Thereafter, the terminal device 40 repeats this operation (hereinafter, description of this operation will be omitted).

[0182] Next, the terminal device 40 specifies the residence time of one or more packets stored in the buffer (step S305). For example, the terminal device 40 calculates the waiting time of the packet in the RLC layer / MAC layer. The residence time specified by the terminal device 40 may be an average residence time, a maximum residence time, a predicted residence time, or a combination of these times, as in the first embodiment. The residence time may be a representative value (for example, a maximum value for a certain period of time, etc.). The residence time notified to the AF may be a residence time for each LCG (or for each logical channel). The terminal device 40 notifies the AF (for example, the server 10) of information on the specified residence time (hereinafter, referred to as residence time information) (step S306). Thereafter, the terminal device 40 periodically repeats this operation (steps S305 to S306) (hereinafter, description of this operation will be omitted).

[0183] The AF receives waiting time information from the terminal device 40. Then, the AF determines whether the communication of the terminal device 40 (e.g., communication related to a service provided by the AF) satisfies the delay requirement based on the waiting time information. For example, the AF determines whether the communication of the terminal device 40 (e.g., uplink communication) satisfies a packet delay budget (PDB) based on the request of the service. If the waiting time is long compared to the PDB (e.g., if the waiting time does not satisfy a first criterion), the AF sets the scheduling priority of the terminal device 40 high. If the waiting time is sufficiently satisfied (if the waiting time satisfies a second criterion that is stricter than the first criterion), the AF sets the scheduling priority of the terminal device 40 low within a range where the PDB can be assumed to be satisfied.

[0184] Then, the AF notifies the core network of the change in target priority for the terminal device 40 whose priority has been changed (step S307). For example, the AF reconfigures the QoS (Quality of Service) for the terminal device 40 using a predetermined API. For example, the AF updates the QoS (for example, 5QI (5G QoS Identifier) ​​or QCI (QoS Class Identifier), or its Priority Level or Packet Delay Budget) set in the core network using a NEF API (for example, AFsessionWithQoS) or a SCEF API (for example, AsSessionWithQoS). The core network (for example, the management device 20) and / or the base station 30 updates the QoS for the terminal device 40 based on the notification from the AF (step S308). The base station 30 performs scheduling for the terminal device 40 based on the changed QoS. After that, the AF, the core network, and the base station 30 repeat this operation (steps S307 to S308).

[0185] Usually, the base station 30 / core network performs scheduling to satisfy the set QoS, but depending on the congestion situation, the QoS may not be satisfied. In that case, the weighting of the scheduling metric may be dynamically changed by making the QoS setting of the service more pronounced. This allows the base station 30 / core network to achieve the target delay time.

[0186] According to the third embodiment, the AF can grasp the retention of data buffered in each terminal device 40. This allows the AF to reconfigure the QoS taking into account the retention time. As a result, low-latency wireless communication is realized even in uplink communication, so that the communication system 1 can realize wireless communication with high communication performance (for example, stable low-latency wireless communication).

[0187] <<6. Modifications>> The above-described embodiment is merely an example, and various modifications and applications are possible.

[0188] <6-1. Modifications regarding determination of residence time> In the above-described embodiments (embodiments 1 and 3), the terminal device 40 specifies the residence time of a packet to be transmitted to another communication device within the terminal device 40. This residence time can also be specified (calculated) as follows.

[0189] 26 is a sequence diagram for explaining a method for specifying the residence time. In the diagram, MAC / L1 is the MAC layer / physical layer of the terminal device 401 that transmits data to the base station 30. The measurement start point is, for example, any one of the following (1) to (3).

[0190] (1) PDCP / RLC layer boundary (3GPP protocol boundary) (2) Smartphone (app and OS boundary), router, or IoT module interface (3) External device connected to terminal device 401

[0191] Here, the external device may be a communication device (for example, the terminal device 402) that generates packets / data and is connected to the terminal device 401 by tethering / LAN or the like. FIG. 27 is a diagram for explaining an external device. In the example of FIG. 27, the external device (terminal device 402) is a camera. In this case, the terminal device 401 may specify the time from when data is generated in the external device as the residence time. Of course, the terminal device 401 may specify the time from when a packet is generated in an application in the terminal device 401 as the residence time. In addition, the terminal device 401 may specify the time from when a packet arrives at a predetermined protocol layer (for example, a PDCP layer or an RLC layer) in the terminal device 401 as the residence time.

[0192] A method for identifying the residence time will be described below with reference to the sequence diagram of FIG.

[0193] First, the measurement start point and the MAC / L1 synchronize their times (step S401). The measurement start point and the MAC / L1 may periodically share a common counter (for example, a CPU counter) or time information.

[0194] Next, when the transmission packet arrives at the measurement start point, the measurement start point assigns an arrival time to the transmission packet (step S402). The timing at which the transmission packet arrives at the measurement start point becomes the measurement start timing for the residence time. The measurement start point transmits the packet with the assigned arrival time to the MAC / L1.

[0195] Next, MAC / L1 calculates the residence time of the transmitted packet in terminal device 40 (step S404). Here, the measurement end timing of the residence time is set to the first transmission time of the BSR (for example, the SFN / Subframe / Slot when the BSR is transmitted for the first time). In other words, MAC / L1 specifies the time from the arrival time (measurement start timing) to the first transmission time of the BSR (measurement end timing) as the residence time. The BSR is transmitted at a timing assigned to the base station 30. Therefore, MAC / L1 can uniquely determine the first transmission time of the BSR when creating the BSR. MAC / L1 notifies the base station 30 of the specified residence time by the BSR (step S405).

[0196] The base station 30 calculates the processing waiting time (scheduling waiting time) at the base station 30 based on the initial transmission time of the BSR and the time (estimated time) at which the scheduling information related to the BSR is transmitted to the terminal device 40. The base station 30 updates the residence time based on this processing waiting time (step S406). The base station 30 performs scheduling based on the updated residence time information.

[0197] <6-2. Modifications regarding transmission of residence time information> In the above-described embodiment (embodiment 1), the terminal device 40 notifies other communication devices (e.g., the base station 30) of the staying time information using BSR. However, the terminal device 40 may notify other communication devices of the staying time information (e.g., the average staying time / the predicted staying time) using a means other than BSR. The staying time information may include the maximum staying time. The notifying means may be any of the following means A to C.

[0198] <Means A> As described in the third embodiment, the terminal device 40 notifies the AF of the residence time information.

[0199] <Method B> The terminal device 40 notifies RRM (Radio Resource Management) of the residence time information in a Measurement Report (L3 message).

[0200] The RRM updates various parameters of the MAC scheduler and notifies the MAC scheduler of the base station 30. At this time, the RRM does not need to change the QoS parameters because they are parameters of the core network (PCRF (Policy and Charging Rules Function) / PCF (Policy Control function)). The base station 30 performs priority control of UE / LCH (Logical Channel) closed within the base station 30.

[0201] RRM notifies the core network of the residence time information. A specific function in the core network (e.g., a function that determines policy such as PCRF / PCF) updates the QoS information in the PDU Session. This causes the core network to change the scheduling priority.

[0202] The O-CU-CP (RRC layer) defined in O-RAN (Open Radio Access Network) notifies the rAPP via O1. Or, the O-CU-CP (RRC layer) defined in O-RAN notifies the xAPP via E2. Here, the O-CU-CP is the O-RAN Central Unit Control Plane. Also, the rApp is a Non-RT RIC Application, and the xAPP is a Near-RT RIC Application. The rApp and / or the xApp configure the MAC scheduler (DU (Distributed Unit)) via the E2 node.

[0203] <Means C> FIG. 28 is a diagram showing an example of an O-RAN architecture. A terminal device 40 notifies xApp / rApp (RIC (RAN Intelligent Controller) / SMO (Service Management and Orchestration)) defined in O-RAN (Open Radio Access Network) of residence time information. Here, rApp is a Non-RT RIC Application, and xAPP is a Near-RT RIC Application. The xApp / rApp (RIC / SMO) sets a MAC scheduler (DU (Distributed Unit)) via an E2 node. At this time, the terminal device 40 may provide an interface (via O2) with an external network in the SMO and notify the residence time information using a public line such as the Internet.

[0204] Fig. 29 is a sequence diagram showing communication processing using O-RAN. Specifically, Fig. 29 is a sequence diagram for explaining a scheduling method using xApp / rApp (RIC / SMO). In Fig. 29, UE (User Equipment) is, for example, a terminal device 40. Also, CU (Central Unit) / DU (Distributed Unit) is, for example, a base station 30. Hereinafter, communication processing using O-RAN will be described with reference to Fig. 29.

[0205] The UE transmits the residence time information to the SMO via the Internet / cloud, etc. The residence time notified to the SMO may be an average residence time, a maximum residence time, a predicted residence time, or a combination of these times, as in the first embodiment. The residence time may be a representative value (e.g., a maximum value for a certain period of time, etc.). The residence time notified to the AF may be a residence time for each LCG (or for each logical channel).

[0206] The SMO notifies the received residence time information to the rApp or xApp in the SMO. Here, rApp is used in use cases where a slow update cycle is acceptable, and xApp is used in use cases where a fast update cycle is required. If either App can be realized architecturally, it is generally realized by xApp. The rAPP / xAPP compares the residence time for each service (for each LCH or LCG) / UE, and identifies the service (LCH or LCG) / UE that should be prioritized for scheduling. Then, the rAPP / xAPP determines the QoS parameters / scheduling parameters based on the identified information.

[0207] The rAPP / xAPP notifies the CU / DU of the determined QoS parameters / scheduling parameters. The CU / DU reflects the determined QoS parameters / scheduling parameters in the MAC scheduler.

[0208] <6-3. Modifications regarding transmission of information related to scheduling> In the above-described embodiment, the terminal device 40 transmits information on the residence time (e.g., maximum residence time / average residence time / predicted residence time) to another communication device (base station 30 / AF / SMO), but the terminal device 40 may notify information on the amount of information of packets in addition to the residence time information. For example, the terminal device 40 identifies the residence time and information amount of each uplink packet in addition to the maximum residence time. Then, the terminal device 40 transmits residence time information including at least information on the maximum residence time and information on the residence time and information amount of each uplink packet to the other communication device (e.g., base station 30 / AF / SMO). The residence time information may include information on the total amount of information of multiple packets remaining in the buffer.

[0209] At this time, the uplink packets may be buffered for each LCG (Logical Channel Group). Then, the terminal device 40 may transmit retention time information for each LCG to the base station. The retention time information may include information on the total amount of information for each LCG.

[0210] More specifically, the terminal device 40 may notify other communication devices (e.g., the base station 30 / AF / SMO) of the number of bits separating the PDCP SDUs and their respective retention times using a BSR, etc. For example, it is assumed that the amount of information and retention time of each of multiple packets (PKT#1 to PKT#1) retained in the buffer are as follows:

[0211] PKT♯1: 100byte, 45msc PKT♯2: 200bytes, 25msc PKT♯3: 150byte, 15msc PKT♯4: 200bytes, 10msc

[0212] At this time, the terminal device 40 may notify the following content in the BSR.

[0213] Total 550byte / Max Buffered time 45msec 100bytes / 45mec 200bytes / 25msec 150bytes / 15msec 100bytes / 10msec

[0214] This enables the base station 30 to perform more accurate scheduling.

[0215] <6-4. Other variations> In the above embodiment, the base station 30 schedules uplink communication based on information (residence time information / timestamp) transmitted from the terminal device 40. However, the scheduling performed by the base station 30 is not limited to scheduling uplink communication. For example, the base station 30 may schedule sidelink communication of the terminal device 40 based on information (residence time information / timestamp) transmitted from the terminal device 40. Of course, the base station 30 may schedule downlink communication of the terminal device 40.

[0216] Furthermore, the communication device that performs the scheduling is not limited to the base station 30. For example, the communication device that performs the scheduling may be another terminal device 40. For example, the communication device that performs the scheduling may be a master UE that manages sidelink communication of one or more terminal devices 40 (slave UEs). In this case, the terminal device 40 (slave UE) may transmit information regarding the retention of packets (retention time information / timestamp) to the other terminal device 40 (master UE).

[0217] The server 10, the management device 20, the base station 30, or the control device that controls the terminal device 40 in this embodiment may be realized by a dedicated computer system or a general-purpose computer system.

[0218] For example, a communication program for executing the above-mentioned operations is stored in a computer-readable recording medium such as an optical disk, a semiconductor memory, a magnetic tape, or a flexible disk and distributed. Then, for example, the program is installed in a computer and the above-mentioned processing is executed to configure a control device. In this case, the control device may be an external device (e.g., an externally connected computer) of the server 10, the management device 20, the base station 30, or the terminal device 40. Also, the control device may be an internal device (e.g., the control unit 13, the control unit 23, the control unit 33, or the control unit 43) of the server 10, the management device 20, the base station 30, or the terminal device 40.

[0219] The communication program may also be stored in a disk device provided in a server on a network such as the Internet, and may be made available for downloading to a computer. The above-mentioned functions may also be realized by cooperation between an OS (Operating System) and application software. In this case, the parts other than the OS may be stored on a medium and distributed, or the parts other than the OS may be stored on a server and made available for downloading to a computer.

[0220] Furthermore, among the processes described in the above embodiments, all or part of the processes described as being performed automatically can be performed manually, or all or part of the processes described as being performed manually can be performed automatically by a known method. In addition, the information including the processing procedures, specific names, various data and parameters shown in the above documents and drawings can be changed arbitrarily unless otherwise specified. For example, the various information shown in each drawing is not limited to the illustrated information.

[0221] In addition, each component of each device shown in the figure is a functional concept, and does not necessarily have to be physically configured as shown in the figure. In other words, the specific form of distribution / integration of each device is not limited to that shown in the figure, and all or part of them can be functionally or physically distributed or integrated in any unit according to various loads, usage conditions, etc. This distribution or integration configuration may be performed dynamically.

[0222] The above-described embodiments can be combined as appropriate in the areas where the processing contents are not contradictory. The order of the steps shown in the flowcharts and sequence diagrams of the above-described embodiments can be changed as appropriate.

[0223] Furthermore, for example, the present embodiment can be implemented as any configuration that constitutes an apparatus or system, such as a processor as a system LSI (Large Scale Integration), a module using multiple processors, a unit using multiple modules, a set in which other functions are added to a unit, etc. (i.e., a configuration of a part of an apparatus).

[0224] In this embodiment, a system means a collection of multiple components (devices, modules (parts), etc.), regardless of whether all the components are in the same housing. Therefore, multiple devices housed in separate housings and connected via a network, and a single device in which multiple modules are housed in a single housing, are both systems.

[0225] Also, for example, this embodiment can have a cloud computing configuration in which one function is shared and processed jointly by a plurality of devices via a network.

[0226] <<7. Conclusion>> The terminal device 40 measures the residence time of one or more uplink packets to be transmitted to the base station 30 for each packet, and identifies the residence time of the packet in the terminal device 40 (for example, the maximum residence time). Then, the terminal device 40 transmits information on the residence time to the base station 30. The base station 30 schedules the uplink communication of the terminal device 40 based on the received residence time information.

[0227] This allows the base station 30 to schedule uplink communication so as to satisfy the delay requirement. As a result, low-latency wireless communication is realized in uplink communication as well, so that the communication system 1 can realize wireless communication with high communication performance (for example, stable low-latency wireless communication).

[0228] Although the embodiments of the present disclosure have been described above, the technical scope of the present disclosure is not limited to the above-described embodiments, and various modifications are possible without departing from the gist of the present disclosure. In addition, components of different embodiments and modifications may be appropriately combined.

[0229] Furthermore, the effects of each embodiment described in this specification are merely examples and are not limiting, and other effects may also be provided.

[0230] The present technology can also be configured as follows. (1) A terminal device connected to a base station, a measuring unit that measures a residence time of one or more packets transmitted by the terminal device for each of the packets; A determination unit that determines a maximum value of the residence time; a transmission unit that transmits, to the base station, residence time information including at least information regarding a maximum value of the residence time; A terminal device comprising: (2) The measurement unit measures a residence time of one or more uplink packets transmitted by the terminal device for each of the uplink packets, The transmission unit transmits the residence time information to the base station. The terminal device according to (1) above. (3) The measurement unit measures a time from when the uplink packet is generated in an application in the terminal device as the residence time. The terminal device according to (2) above. (4) The measurement unit measures a time from when the uplink packet arrives at a predetermined protocol layer as the residence time. The terminal device according to (2) above. (5) The measurement unit measures a time from when the uplink packet is generated on another communication device connected to the terminal device as the residence time. The terminal device according to (2) above. (6) The transmission unit includes the residence time information in a BSR and transmits the BSR to the base station. The terminal device according to any one of (2) to (5). (7) At a timing when the transmission of the BSR is triggered, a maximum value of the residence time is obtained, and the residence time information including information on the maximum value is included in the BSR and transmitted to the base station. The terminal device according to (6) above. (8) The uplink packets are buffered for each LCG (Logical Channel Group), The identification unit identifies a maximum value of the residence time for each of the LCGs, The transmission unit transmits the residence time information including information on a maximum value of the residence time for each LCG to the base station. The terminal device according to any one of (2) to (7). (9) The determination unit determines an average value of the residence time in addition to the maximum value of the residence time, The transmission unit transmits the residence time information including at least information regarding a maximum value of the residence time and information regarding an average value of the residence time to the base station. The terminal device according to any one of (2) to (8). (10) The uplink packets are buffered for each LCG (Logical Channel Group), The identification unit identifies an average residence time for each of the LCGs, The transmission unit transmits the residence time information including information regarding an average value of the residence time for each LCG to the base station. The terminal device according to (9) above. (11) The determination unit determines a predicted value of the residence time in addition to the maximum value of the residence time, The transmission unit transmits the residence time information including at least information regarding a maximum value of the residence time and information regarding a predicted value of the residence time to the base station. The terminal device according to any one of (2) to (10). (12) The uplink packets are buffered for each LCG (Logical Channel Group), The identification unit identifies a predicted value of the residence time for each of the LCGs, The transmission unit transmits the residence time information including information regarding a predicted value of the residence time for each LCG to the base station. The terminal device according to (11) above. (13) The determination unit determines a residence time and an information amount for each of the uplink packets in addition to the maximum residence time, The transmission unit transmits, to the base station, the residence time information including at least information regarding the maximum residence time and information regarding the residence time and an information amount for each uplink packet. The terminal device according to any one of (2) to (12). (14) The uplink packets are buffered for each LCG (Logical Channel Group), The transmission unit transmits the residence time information for each LCG to the base station. The terminal device according to (13) above. (15) The transmission unit transmits the residence time information to the base station. The terminal device according to any one of (2) to (14). (16) The transmission unit includes the residence time information in a BSR and transmits the BSR to the base station. The terminal device according to (15) above. (17) The transmitter transmits the residence time information to the base station every time the transmitter transmits the uplink packet to the base station. The terminal device according to any one of (2) to (16). (18) A base station connected to a terminal device, a receiving unit that receives, from the terminal device, residence time information including at least information regarding a maximum residence time of one or more packets transmitted by the terminal device; A scheduling unit that schedules uplink communication of the terminal device based on residence time information; A base station comprising: (19) A communication method executed by a terminal device connected to a base station, comprising: Measure a residence time of one or more packets transmitted by the terminal device for each of the packets; Identifying the maximum residence time; transmitting residence time information including at least information regarding a maximum value of the residence time to the base station; Communication methods. (20) A communication method executed by a base station connected to a terminal device, comprising: receiving, from the terminal device, residence time information including at least information regarding a maximum residence time of one or more packets transmitted by the terminal device; scheduling uplink communication of the terminal device based on the residence time information; Communication methods. [Explanation of symbols]

[0231] 1. Communication Systems 10 Server 20 Management device 30 base station 40 Terminal Equipment 11, 21 Communications Department 31, 41 Wireless Communication Section 12, 22, 32, 42 storage section 13, 23, 33, 43 Control section 44 External Interface 311, 411 Transmission processing unit 312, 412 Receiving processing unit 313, 413 Antenna 331, 431 Transmitter 332, 432 Receiver 333 Scheduling Department 433 Measurement Division 434 Specific part RAN Radio Access Network CN Core Network

Claims

1. A terminal device connected to a base station, a measuring unit that measures a residence time of one or more packets transmitted by the terminal device for each of the packets; A determination unit that determines a maximum value of the residence time; a transmission unit that transmits, to the base station, residence time information including at least information regarding a maximum value of the residence time; A terminal device comprising:

2. The measurement unit measures a residence time of one or more uplink packets transmitted by the terminal device for each of the uplink packets, The transmission unit transmits the residence time information to the base station. The terminal device according to claim 1 .

3. The measurement unit measures a time from when the uplink packet is generated in an application in the terminal device as the residence time. The terminal device according to claim 2.

4. The measurement unit measures a time from when the uplink packet arrives at a predetermined protocol layer as the residence time. The terminal device according to claim 2.

5. The measurement unit measures a time from when the uplink packet is generated on another communication device connected to the terminal device as the residence time. The terminal device according to claim 2.

6. The transmission unit includes the residence time information in a BSR and transmits the BSR to the base station. The terminal device according to claim 2.

7. a maximum value of the residence time is obtained at a timing when the transmission of the BSR is triggered, and the residence time information including information on the maximum value is included in the BSR and transmitted to the base station; The terminal device according to claim 6.

8. The uplink packets are buffered for each LCG (Logical Channel Group), The identification unit identifies a maximum value of the residence time for each of the LCGs, The transmission unit transmits the residence time information including information regarding a maximum value of the residence time for each LCG to the base station. The terminal device according to claim 2.

9. The determination unit determines an average value of the residence time in addition to the maximum value of the residence time, The transmission unit transmits the residence time information including at least information regarding a maximum value of the residence time and information regarding an average value of the residence time to the base station. The terminal device according to claim 2.

10. The uplink packets are buffered for each LCG (Logical Channel Group), The identification unit identifies an average value of the residence time for each of the LCGs, The transmission unit transmits the residence time information including information regarding an average value of the residence time for each LCG to the base station. The terminal device according to claim 9.

11. The determination unit determines a predicted value of the residence time in addition to the maximum value of the residence time, The transmission unit transmits the residence time information including at least information regarding a maximum value of the residence time and information regarding a predicted value of the residence time to the base station. The terminal device according to claim 2.

12. The uplink packets are buffered for each LCG (Logical Channel Group), The identification unit identifies a predicted value of the residence time for each of the LCGs, The transmission unit transmits the residence time information including information regarding a predicted value of the residence time for each LCG to the base station. The terminal device according to claim 11.

13. The determination unit determines a residence time and an information amount for each of the uplink packets in addition to the maximum residence time, The transmission unit transmits, to the base station, the residence time information including at least information regarding the maximum residence time and information regarding the residence time and an information amount for each uplink packet. The terminal device according to claim 2.

14. The uplink packets are buffered for each LCG (Logical Channel Group), The transmission unit transmits the residence time information for each LCG to the base station. The terminal device according to claim 13.

15. The transmission unit transmits the residence time information to the base station. The terminal device according to claim 2.

16. The transmission unit includes the residence time information in a BSR and transmits the BSR to the base station. The terminal device according to claim 15.

17. The transmitter transmits the residence time information to the base station every time the transmitter transmits the uplink packet to the base station. The terminal device according to claim 2.

18. A base station connected to a terminal device, a receiving unit that receives, from the terminal device, residence time information including at least information regarding a maximum residence time of one or more packets transmitted by the terminal device; A scheduling unit that schedules uplink communication of the terminal device based on residence time information; A base station comprising:

19. A communication method executed by a terminal device connected to a base station, comprising: measuring a residence time of one or more packets transmitted by the terminal device for each of the packets; Identifying the maximum residence time; transmitting residence time information including at least information regarding a maximum value of the residence time to the base station; Communication methods.

20. A communication method executed by a base station connected to a terminal device, comprising: receiving, from the terminal device, residence time information including at least information regarding a maximum residence time of one or more packets transmitted by the terminal device; scheduling uplink communication of the terminal device based on the residence time information; Communication methods.

Citation Information

Patent Citations

  • Mobile station, base station device, communication control method, and mobile communication system

    JP2012034407A