Wireless resource allocation method, base station, base station program, wireless communication terminal and terminal program

Abstract

A lead UE (200) communicates a wireless guide identifier assigned to it via a base station (300). The lead UE (200) sends a request message containing the communicated wireless guide identifier to the base station. The base station receives the request message from the subscriber UE, determines a wireless guide resource assigned to the lead terminal based on the wireless guide identifier contained in the request message from the subscriber terminal, assigns a wireless resource whose timing is close to that of the wireless guide resource to the subscriber terminal as a wireless subscriber resource, and sends a response message indicating the wireless subscriber resource to the subscriber UE.

Description

Technical field

[0001] The present disclosure relates to the allocation or assignment of wireless resources. Background on the state of the art

[0002] There are cases where it is necessary to collect and process sensor data with low latency.

[0003] For example, in a case where acquisition data is used to control production equipment in a manufacturing line, or in a case where acquisition data is used to detect a player's actions in a game, the acquisition data must be collected and processed with low latency.

[0004] This takes into account a system for collecting data in real time.

[0005] This system includes a variety of sensors, a variety of 5G end devices (hereinafter referred to as UEs), a base station and a server.

[0006] The UEs are connected to the same base station.

[0007] Each sensor sends or transmits the acquisition data to the server via one of the UEs.

[0008] The server is installed in a 5G system and processes all individual data collections at the time that is the target for collection. Specifically, the server collectively processes a group of data collections that are acquired at approximately the same time.

[0009] Therefore, the latest time the server receives the collection data determines the time at which the processing of the group of collection data begins.

[0010] The time between when the UE sends collection data to the server and when the server completes processing the received collection data is defined as the processing delay time.

[0011] In this case, the processing delay time of the acquisition data is affected by variations in the reception times at the server, which occur between the sensor data transmitted by a large number of sensors at approximately the same time.

[0012] Configured Grant is a mechanism for 5G systems to achieve low-latency communication over an uplink.

[0013] With Configured Grant, a wireless resource used by a UE for uplink transmission is pre-assigned or allocated by the base station, instead of being requested by the UE each time transmission data is generated.

[0014] By using Configured Grant, it is possible to achieve low-latency communication for data transmitted over an uplink from a UE.

[0015] However, if wireless uplink resources are allocated separately to a large number of UEs via Configured Grant, the timings of the wireless resources can differ by more than one wireless frame time of the 5G system among the large number of UEs. For example, a difference of 10 milliseconds or more can occur.

[0016] Even when the 5G system's QoS function is used to control communication latency so that it is consistent across sessions between each user entity (UE) and the server, the following possibility arises if a difference occurs in the allocated timings of the wireless uplink resources. Specifically, if, among the individual data points collected and acquired by the numerous sensors at approximately the same time, there is a difference of more than the wireless frame time (10 milliseconds) between the earliest and latest reception times of the data received by the server, the server's start time for processing the acquired data is delayed by this difference. Consequently, the processing delay for the acquired data increases by this amount.

[0017] Configured Grant is defined in 3GPP TS 38.300, 3GPP TS 38.321 and 3GPP TS 38.331. 3GPP is a registered trademark.

[0018] Patent literature 1 discloses a configuration of a base station. The base station schedules a transmission timing within a specified time range for each user device (UD) in the same group to which a wireless uplink resource is assigned via Configured Grant. The UD receives scheduling information from the base station and performs the transmission at a timing based on the received scheduling information.

[0019] Patent literature 1 discloses an example in which a UE management table is used, which is managed by a control unit within a core network, and an example in which the UE specifies group identification information of the UE itself in a message that the UE sends to the base station. The UE management table shows the correspondence between each UE ID and the identification information of a group to which each UE belongs (group identification information).

[0020] However, patent literature 1 does not disclose a method for determining group identification information or a method for determining group identification information that is to be contained in a message that the UE sends to the base station.

[0021] The invention described in patent literature 1 requires means for determining the identification information of the group to which the UE belongs. Furthermore, in order to distinguish between a multitude of UE groups belonging to the same base station, it is necessary to determine the identification information of a group to which UEs belong in such a way that the identification information of a UE group is unique, at least within a single base station.

[0022] However, no method for this is disclosed in patent literature 1. Reference list patent literature

[0023] Patent Literature 1: JP 2018-191110 A Summary of the invention: Technical problem

[0024] One purpose of the present disclosure is to assign or allocate wireless uplink resources whose timings are as close as possible to a multitude of UEs belonging to a UE group. Solution to the problem

[0025] A wireless resource allocation method of the present disclosure is a wireless resource allocation method using a base station and a terminal group, wherein the terminal group consists of a wireless communication terminal serving as a lead terminal and one or more wireless communication terminals, each serving as a subscriber terminal other than the lead terminal, and the wireless resource allocation method comprises: Communication by the lead terminal of a wireless lead identifier assigned to the lead terminal by the base station; Sending a request message containing the wireless lead identifier communicated by each subscriber terminal except the lead terminal to the base station; Receiving, for each subscriber terminal except the lead terminal, the request message from the subscriber terminal; determining a wireless lead resource assigned to the lead terminal based on the wireless lead identifier contained in the request message from the subscriber terminal; assigning a wireless resource whose timing is close to that of the wireless lead resource to the subscriber terminal as a wireless subscriber resource; and sending a response message indicating the wireless subscriber resource to the subscriber terminal via the base station; and Received by each subscriber terminal except the lead terminal, the reply message to the subscriber terminal. Advantageous effects of the invention

[0026] According to the present disclosure, it is possible to allocate wireless uplink resources whose timings are as close as possible to a multitude of UEs belonging to a UE group. Brief description of the drawings Fig. Figure 1 is a configuration representation of a wireless communication system 100 in embodiment 1. Fig. Figure 2 is a configuration representation of a UE 200 in embodiment 1. Fig. Figure 3 is a configuration representation of a base station 300 in embodiment 1. Fig. Figure 4 is a flowchart of a wireless resource allocation process in embodiment 1. Fig. Figure 5 is a representation showing a group setting screen 221 in embodiment 1. Fig. Figure 6 is a representation showing a guide setting screen 222 in embodiment 1. Fig. Figure 7 is a representation showing a wireless resource management table 391 in embodiment 1. Fig. Figure 8 is a representation showing an identifier management table 392 in embodiment 1. Fig. Figure 9 is a representation showing a group information table 393 in embodiment 1. Fig. Figure 10 is a representation showing an Allocated Resource Management Table 394 in embodiment 1. Fig. Figure 11 is a representation showing an identifier message screen 223 in embodiment 1. Fig. Figure 12 is a representation showing an identifier input screen 224 in embodiment 1. Fig. Figure 13 is a representation showing an RRCSetupRequest message in embodiment 1. Fig. Figure 14 is a representation showing an example of the allocation of wireless uplink resource timings in the conventional way. Fig. Figure 15 is a configuration representation of the UE 200 in embodiment 2. Fig. Figure 16 is a flowchart of the wireless resource allocation process in embodiment 2. Fig. Figure 17 is a representation showing an RRCSetupRequest message in embodiment 2. Fig. Figure 18 is a hardware configuration representation of the UE 200 in its various embodiments. Fig. Figure 19 is a hardware configuration representation of the Base Station 300 in its various embodiments. Description of embodiments

[0027] In the embodiments and drawings, identical or corresponding elements are designated with the same reference numerals. The description of an element designated with the same reference numeral as an element already described is omitted or simplified as appropriate. Arrows in illustrations primarily indicate signal paths or processing sequences. Design 1

[0028] An embodiment in which wireless resources with closely spaced timings are allocated to a plurality of wireless communication terminals is described by the Fig. 1 to 13 described. *** Configuration Description ***

[0029] Based on Fig. Section 1 describes a configuration of the wireless communication system 100.

[0030] The wireless communication system 100 comprises a base station 300 and a number of UEs 200, which form an UE group. The UE 200 is a wireless communication terminal device.

[0031] In Fig. The wireless communication system 100 comprises the base station 300 and three UEs 200. Furthermore, the wireless communication system 100 includes individual sensors 110 for the UEs 200. The wireless communication system 100 also includes a 5G system 130 with a server 120. The data acquired by the sensor 110 is transmitted by the UE 200 to the server 120 via the base station 300.

[0032] Based on Fig. Section 2 describes a configuration of the UE 200.

[0033] The UE 200 is a computer that includes hardware such as a processor 201, main memory 202, an additional storage device 203, a communication device 204, and an input / output interface 205. These hardware components are interconnected via signal lines.

[0034] The Processor 201 is an integrated circuit (IC) that performs operational processing and controls other hardware components. The Processor 201 is, for example, a CPU.

[0035] IC is an abbreviation for Integrated Circuit.

[0036] CPU is an abbreviation for Central Processing Unit.

[0037] The main memory (RAM) 202 is a volatile or non-volatile memory device. It is also referred to as main memory or primary memory. For example, RAM 202 is a memory module. Data stored in RAM 202 is backed up to secondary memory 203 as needed.

[0038] RAM is an abbreviation for Random Access Memory.

[0039] The auxiliary storage device 203 is a non-volatile storage device. The auxiliary storage device 203 could be, for example, a ROM, an HDD, flash memory, or a combination thereof. Data stored in the auxiliary storage device 203 is loaded into the main memory 202 as needed.

[0040] ROM is an abbreviation for Read Only Memory.

[0041] HDD is the abbreviation for Hard Disk Drive.

[0042] The communication device 204 is both a receiver and a transmitter. For example, the communication device 204 is a communication chip or a NIC. Communication between the UE 200 and the communication device 204 is carried out by the communication device 204.

[0043] NIC is an abbreviation for Network Interface Card.

[0044] The input / output interface 205 is a port to which an input / output device, or an input device and an output device, are connected. An example of an input / output device is a display with a touch panel. Input to and output from the UE 200 are handled via the input / output interface 205.

[0045] The UE 200 includes elements such as a request control unit 211, a wireless communication unit 212, and a user interface unit 213. These elements are implemented through software.

[0046] The user interface unit 213 functions as a group setting unit and as an allocation acquisition unit.

[0047] The additional storage device 203 stores an end-device program to cause a computer to function as the request control unit 211, the wireless communication unit 212, and the user interface unit 213. The end-device program is loaded into the main memory 202 and executed by the processor 201.

[0048] The additional storage device 203 stores an operating system. At least part of the operating system is loaded into the main memory 202 and executed by the processor 201.

[0049] The 201 processor executes the end-device program while running the OS.

[0050] OS is an abbreviation for Operating System.

[0051] Input and output data of the terminal program are stored in a storage unit 290.

[0052] The main memory 202 functions as the memory unit 290. However, instead of the main memory 202, or in conjunction with the main memory 202, memory devices such as the auxiliary memory device 203, a register in the processor 201, and a cache memory in the processor 201 can also function as the memory unit 290.

[0053] The terminal program can be recorded (stored) in a computer-readable format on a non-volatile storage medium, such as an optical disc or flash memory.

[0054] Based on Fig. Section 3 describes a configuration of the base station 300.

[0055] The base station 300 is a computer comprising hardware such as a processor 301, a main memory 302, an additional storage device 303, a communication device 304, and an input / output interface 305. These hardware components are interconnected via signal lines.

[0056] The 301 processor is an integrated circuit (IC) that performs operational processing and controls other hardware components. The 301 processor is, for example, a CPU.

[0057] RAM 302 is a volatile or non-volatile memory device. It is also referred to as main memory or main storage. For example, RAM 302 is a memory module. Data stored in RAM 302 is backed up to auxiliary memory 303 as needed.

[0058] The auxiliary storage device 303 is a non-volatile storage device. The auxiliary storage device 303 can be, for example, a ROM, a hard disk drive (HDD), flash memory, or a combination thereof. Data stored in the auxiliary storage device 303 is loaded into the main memory 302 as needed.

[0059] The communication device 304 is both a receiver and a transmitter. For example, the communication device 304 is a communication chip or a NIC. Communication with the base station 300 is carried out via the communication device 304.

[0060] The input / output interface 305 is a port to which an input / output device, or an input device and an output device, are connected. Input to and output from the base station 300 are performed via the input / output interface 305.

[0061] The base station 300 includes elements such as an allocation unit 311 and a base station communication unit 312. These elements are implemented through software.

[0062] The auxiliary storage device 303 stores a base station program to cause a computer to operate as the allocation unit 311 and the base station communication unit 312. The base station program is loaded into the main memory 302 and executed by the processor 301.

[0063] Furthermore, the additional storage device 303 stores an operating system. At least part of the operating system is loaded into the main memory 302 and executed by the processor 301.

[0064] The 301 processor executes the base station program while running the OS.

[0065] Input and output data of the base station program are stored in a 390 memory unit.

[0066] The main memory 302 functions as the memory unit 390. However, instead of or in conjunction with the main memory 302, memory devices such as the auxiliary memory device 303, a register in the processor 301, and a cache memory in the processor 301 can also function as the memory unit 390.

[0067] The base station program can be recorded (stored) in a computer-readable format on a non-volatile storage medium, such as an optical disk or flash memory. *** Description of a Functionality ***

[0068] A process for operating the Base Station 300 and a multitude of UEs 200 is equivalent to a wireless resource allocation procedure. A process for operating the Base Station 300 is equivalent to a process for processing by the Base Station program, and a process for operating the UE 200 is equivalent to an operation for processing by the terminal program.

[0069] Based on Fig. Section 4 describes the wireless resource allocation method.

[0070] In step S110, a large number of the UEs 200 form a UE group.

[0071] The UE group consists of a large number of UE 200s, for which it is desirable to assign wireless uplink resource timings at times as close together as possible.

[0072] The UEs 200 that belong to the UE group are referred to as participant UEs. Details regarding step S110 will be described later.

[0073] The following processing is performed in each UE 200.

[0074] First, the request control unit 211 instructs the user interface unit 213 to display the request control unit 211. Then, the user interface unit 213 displays a group setting screen 221 on a display.

[0075] The group setting screen 221 is a screen for setting the UE group in the UE 200 and contains a user interface for setting the UE group.

[0076] Fig. Figure 5 shows an example of the group setting screen 221.

[0077] The group setting screen 221 contains a button that allows you to select whether the UE 200 should belong to the UE group or not.

[0078] Next, a user enters the UE group setting into the UE 200 by using the user interface on the group setting screen 221.

[0079] For example, it is assumed that the group setting screen 221 is from Fig. 5 is displayed on the UE 200's screen. If the UE 200 is to be included in the UE group, the user presses a "YES" button. If the UE 200 is not to be included in the UE group, the user presses a "NO" button.

[0080] After the UE group setting has been entered, the user interface unit 213 closes the group setting screen 221.

[0081] The request control unit 211 then registers the specification of the entered terminal group.

[0082] For example, if the “YES” button on the group setting screen 221 of Fig. When button 5 is pressed, the request control unit 211 registers information indicating that the UE 200 belongs to the UE group. If the "NO" button is pressed on the group assignment screen 221, Fig. When 5 is pressed, the request control unit 211 registers information indicating that the UE 200 does not belong to the UE group.

[0083] Referring again to Fig. 4, the description continues from step S120.

[0084] In step S120, the UE group selects a lead UE.

[0085] The lead UE is a UE 200, which is selected from the UE group as the lead UE.

[0086] Details regarding step S120 will be described later.

[0087] The following processing is performed in every UE 200 that belongs to the UE group.

[0088] First, the request control unit 211 instructs the user interface unit 213 to display a guide selection screen 222. Then, the user interface unit 213 displays the guide selection screen 222 on the display.

[0089] The guide selection screen 222 is a screen for setting the guide UE, and contains a user interface for setting the guide UE.

[0090] Fig. Figure 6 shows an example of the guide selection screen 222.

[0091] The guide selection screen 222 contains a button that can be used to select whether the UE 200 should be selected as the guide UE or not.

[0092] Next, the user enters the selection of the guide UE into the UE 200 by using the user interface on the guide selection screen 222.

[0093] For example, it is assumed that the group setting screen 222 is from Fig. 6 is displayed on the UE 200's screen. If the UE 200 is to be selected as the lead UE, the user presses a "YES" button. If the UE 200 is not to be selected as the lead UE, the user presses a "NO" button.

[0094] After the setting of the lead UE has been entered, the user interface unit 213 closes the lead setting screen 222.

[0095] The request control unit 211 then registers the selection of the lead UE that was entered.

[0096] For example, if the “YES” button is on the guide selection screen 222 of Fig. When button 6 is pressed, the request control unit 211 registers information indicating that UE 200 is the lead UE. If the "NO" button is pressed on the lead selection screen 222, Fig. When 6 is pressed, the request control unit 211 registers information indicating that the UE 200 is not the lead UE.

[0097] Referring again to Fig. 4, the description continues from step S130.

[0098] In step S130, the lead UE sends an allocation request message to the base station 300.

[0099] The allocation request message is a message that requests the allocation of a wireless UE identifier and a wireless uplink resource.

[0100] Details regarding step S130 will be described later.

[0101] The following processing is carried out in the lead unit.

[0102] The request control unit 211 instructs the wireless communication unit 212 to send an RRCSetupRequest message.

[0103] The wireless communication unit 212 sends the RRCSetupRequest message via the communication device 204 to the base station 300.

[0104] The RRCSetupRequest message is a message requesting allocation of a wireless uplink resource from Base Station 300 via a Configured Grant.

[0105] This RRCSetupRequest message does not contain CS-RNTI in the parameters.

[0106] The RRCSetupRequest message is equivalent to an allocation request message.

[0107] A CS-RNTI is equivalent to a wireless UE identifier. CS-RNTI is an abbreviation for Configured Scheduling Radio Network Temporary Identifier.

[0108] In step S140, the base station 300 receives the allocation request message from the lead UE.

[0109] Next, the base station 300 assigns a wireless UE identifier and a wireless uplink resource to the lead UE.

[0110] The wireless UE identifier assigned to the lead UE is referred to as a wireless lead identifier.

[0111] The wireless uplink resource assigned to the lead UE is referred to as the wireless lead resource.

[0112] The wireless conductor identifier and the wireless conductor resource are collectively referred to as the conductor allocation.

[0113] The base station 300 then sends an allocation response message to the lead UE, specifying the lead allocation.

[0114] The allocation response message is a response message that corresponds to the allocation request message.

[0115] Details regarding step S140 will be described later.

[0116] The following processing is performed in the base station 300.

[0117] First, the base station communication unit 312 receives the RRCSetupRequest message from the lead UE via the communication device 304.

[0118] Next, the Base Station Communication Unit 312 determines whether it is necessary to allocate a wireless uplink resource through a Configured Grant.

[0119] If it is necessary to allocate a wireless uplink resource, the base station communication unit 312 informs the allocation unit 311 of the received RRCSetupRequest message.

[0120] When the RRCSetupRequest message is transmitted, the allocation unit 311 assigns a CS-RNTI and a wireless uplink resource to the lead UE. The allocation unit 311 also informs the base station communication unit 312 of the CS-RNTI and wireless uplink resources being assigned to the lead UE.

[0121] The base station communication unit 312 then sends an RRCSetup message, indicating successful allocation, to the lead UE via the communication unit 304. This RRCSetup message specifies the CS-RNTI and wireless uplink resources allocated to the lead UE.

[0122] The RRCSetup message is equivalent to the allocation response message.

[0123] Details of the allocation of a CS-RNTI and a wireless uplink resource to the lead UE are described below.

[0124] First, since the RRCSetupRequest message does not contain CS-RNTI, allocation unit 311 determines that this RRCSetupRequest message is the RRCSetupRequest message from the lead UE.

[0125] Next, the allocation unit 311 refers to a wireless resource management table 391 and determines a wireless uplink resource to be assigned to the lead UE from the unassigned wireless uplink resources.

[0126] Furthermore, allocation unit 311 refers to identifier management table 392 and determines a CS-RNTI to be assigned to the lead UE from among the unassigned CS-RNTIs. Additionally, allocation unit 311 registers an allocated status for the determined CS-RNTI in identifier management table 392.

[0127] Subsequently, the allocation unit 311 registers the CS-RNTI allocated to the lead UE in a group information table 393.

[0128] Next, the allocation unit 311 informs the base station communication unit 312 of the CS-RNTI and wireless uplink resource to be allocated to the lead UE.

[0129] Then the base station communication unit 312 registers an allocated status for the reported wireless uplink resource in the wireless resource management table 391.

[0130] In addition, the base station communication unit 312 registers the communicated CS-RNTI and the wireless uplink resource in an allocated resource management table 394.

[0131] Fig. Figure 7 shows an example of the wireless resource management table 391.

[0132] The wireless resource management table 391 contains, for each pair of "subcarrier" and "transmit timing", a column "Allocated" which corresponds to the pair of "subcarrier" and "transmit timing".

[0133] A pair consisting of a subcarrier and a transmit timing is a wireless uplink resource.

[0134] The base station communication unit 312 sets "Yes" in the "Allocated" column, which corresponds to the wireless uplink resource assigned to the lead UE. "Yes" indicates an allocated status.

[0135] Fig. Figure 8 shows an example of the identifier management table 392.

[0136] The identifier management table 392 contains a column “Allocated” for each “CS-RNTI”, which corresponds to the “CS-RNTI”.

[0137] Allocation unit 311 sets "Yes" in the "Allocated" column, which corresponds to the CS-RNTI assigned or allocated to the lead unit. "Yes" indicates an allocated status.

[0138] Fig. Figure 9 shows an example of the group information table 393.

[0139] The group information table 393 has a column “CS-RNTI of the lead UE”, which corresponds to a column “CS-RNTI of the participant UE”.

[0140] Allocation unit 311 registers the CS-RNTI assigned to the lead UE in both the "CS-RNTI of the participant UE" column and the "CS-RNTI of the lead UE" column.

[0141] Fig. Figure 10 shows an example of the Allocated Resource Management table 394.

[0142] The Allocated Resource Management table 394 contains a column “Wireless Uplink Resource” which corresponds to a column “CS-RNTI”.

[0143] The base station communication unit 312 registers the CS-RNTI assigned to the lead UE in the column “CS-RNTI”, and registers the wireless uplink resource assigned to the lead UE in the column “Wireless Uplink Resource”.

[0144] Referring again to Fig. 4, the description continues from step S150.

[0145] In step S150, the lead UE receives the allocation response message from the base station 300.

[0146] The lead UE then registers the lead allocation (wireless lead identifier, wireless lead resource) specified in the allocation response message.

[0147] Details regarding step S150 will be described later.

[0148] The following processing is carried out in the lead unit.

[0149] First, the wireless communication unit 212 receives the allocation response message via the communication device 204 from the base station 300.

[0150] Next, the wireless communication unit 212 registers the CS-RNTI specified in the received allocation response message as the CS-RNTI of the UE 200 itself.

[0151] The wireless communication unit 212 also registers the wireless uplink resource specified in the received allocation response message as the wireless uplink resource of the UE 200 itself.

[0152] Next, the wireless communication unit 212 communicates the CS-RNTI specified in the received allocation response message to the request control unit 211.

[0153] Then the request control unit 211 registers the communicated CS-RNTI as the CS-RNTI of the lead UE.

[0154] In step S160, the lead UE communicates the wireless lead identifier.

[0155] Each participating UE (except for the lead UE) registers the communicated wireless lead identifier.

[0156] With regard to the guiding unit, the details of step S160 are described.

[0157] First, the request control unit 211 communicates the CS-RNTI of the lead UE and instructs the user interface unit 213 to display an identifier message screen 223.

[0158] Then the user interface unit 213 displays the identifier message screen 223 on the display.

[0159] The Identification Message Screen 223 is a screen for informing the user of the wireless routing identifier.

[0160] Fig. Figure 11 shows an example of the identifier message screen 223.

[0161] The Identification Message screen 223 displays a CS-RNTI value, which represents the wireless lead identifier, and includes a button to close the screen.

[0162] The user checks the wireless routing identifier displayed on the identifier message screen 223 and presses the "Close" button.

[0163] When the "Close" button is pressed, the user interface unit 213 closes the identifier message screen 223.

[0164] For each participant UE that is not the lead UE, the details of step S160 are described.

[0165] After step S120, the request control unit 211 instructs the user interface unit 213 to display an identifier input screen 224. The user interface unit 213 then displays the identifier message screen 224 on the display.

[0166] In particular, after pressing the “NO” button, the user interface unit 213 displays the following on the guide selection screen 222: Fig. 6 the identifier entry screen 224.

[0167] The identifier input screen 224 is a screen for accepting an input of the wireless lead identifier, and contains a user interface for accepting an input of the wireless lead identifier.

[0168] Fig. Figure 12 shows an example of the identifier input screen 224.

[0169] The identifier input screen 224 contains a text field into which the CS-RNTI value, representing the wireless conductor identifier, is entered.

[0170] The user enters the CS-RNTI of the lead UE into the participant UE using the identifier input screen 224.

[0171] For example, the user enters the CS-RNTI, communicated via the identifier message screen 223, into the text field on the identifier input screen 224 and presses the "OK" button. When the "OK" button is pressed, the user interface unit 213 closes the identifier message screen 223.

[0172] The user interface unit 213 then communicates the entered CS-RNTI to the request control unit 211.

[0173] Then the request control unit 211 registers the communicated CS-RNTI as the CS-RNTI of the lead UE.

[0174] Referring again to Fig. 4, the description continues from step S170.

[0175] In step S170, each participating UE (excluding the lead UE) sends an allocation request message to the base station 300.

[0176] This allocation request message contains the wireless route identifier in parameters.

[0177] Details regarding step S170 will be described later.

[0178] The following processing is carried out in every participant UE except the lead UE.

[0179] First, the request control unit 211 informs the wireless communication unit 212 of the CS-RNTI of the lead UE.

[0180] Then the wireless communication unit 212 sends an RRCSetupRequest message to the base station 300 via the communication device 204.

[0181] This RRCSetupRequest message contains the CS-RNTI of the lead UE as a parameter.

[0182] Fig. Figure 13 shows an example of an ASN.1 definition of the RRCSetupRequest message.

[0183] The RRCSetupRequest message contains the CS-RNTI as a parameter in the section enclosed by a bold frame.

[0184] Referring again to Fig. 4, the description continues from step S180.

[0185] In step S180, the base station 300 receives the allocation response message from the participant UE.

[0186] Next, the base station 300 assigns a wireless UE identifier to the subscriber UE.

[0187] The Base Station 300 also determines the wireless guide resource based on the wireless guide identifier contained in the allocation response message and assigns a wireless uplink resource to the subscriber UE whose timing is close to the timing of the wireless guide resource.

[0188] The wireless UE identifier assigned to the subscriber UE is referred to as a wireless subscriber identifier.

[0189] The wireless uplink resource assigned to the subscriber UE is referred to as a wireless subscriber resource.

[0190] The wireless subscriber identifier and the wireless subscriber resource are collectively referred to as a lead allocation.

[0191] The base station 300 then sends an allocation response message to the participant UE, specifying the participant allocation.

[0192] Details regarding step S180 will be described later.

[0193] The following processing is performed in the base station 300.

[0194] First, the base station communication unit 312 receives the RRCSetupRequest message from the subscriber UE via the communication device 304.

[0195] Next, the base station communication unit 312 determines whether it is necessary to allocate a wireless uplink resource through a Configured Grant.

[0196] If it is necessary to allocate a wireless uplink resource, the base station communication unit 312 informs the allocation unit 311 of the received RRCSetupRequest message.

[0197] When the RRCSetupRequest message is transmitted, allocation unit 311 assigns a CS-RNTI to the subscriber UE. Subscriber allocation unit 313 also assigns a wireless uplink resource to the subscriber UE, with a timing as close as possible to that of the wireless guide resource.

[0198] Next, the allocation unit 311 informs the base station communication unit 312 of the CS-RNTI and wireless uplink resource allocated to the subscriber UE.

[0199] The base station communication unit 312 then sends an RRCSetup message to the subscriber UE, indicating successful allocation. This RRCSetup message specifies the CS-RNTI and wireless uplink resources assigned to the subscriber UE.

[0200] Details of the allocation of a CS-RNTI and a wireless uplink resource to the subscriber UE are described below.

[0201] First, since the CS-RNTI is contained in the RRCSetupRequest message, allocation unit 311 determines that this RRCSetupRequest message is the RRCSetupRequest message from a different participant UE than the lead UE.

[0202] Next, the allocation unit 311 searches the allocated resource management table 394 using the CS-RNTI contained in the RRCSetupRequest message as a search key to locate the wireless guide resource.

[0203] Next, allocation unit 311 refers to wireless resource management table 391 and determines a wireless uplink resource to be assigned to the subscriber UE from among the unassigned wireless uplink resources. At this point, allocation unit 311 finds a wireless uplink resource whose timing is as close as possible to that of the wireless guide resource as the wireless uplink resource to be assigned to the subscriber UE.

[0204] Furthermore, allocation unit 311 refers to identifier management table 392 and determines a CS-RNTI to be assigned to the participant UE from among the unassigned CS-RNTIs. Allocation unit 311 also registers an allocated status for the specified CS-RNTI in identifier management table 392. Specifically, allocation unit 311 places the following entry in identifier management table 392: Fig. 8. Enter “YES” in the “Allocated” column, which corresponds to the CS-RNTI to be assigned to the participant UE.

[0205] Next, allocation unit 311 registers the CS-RNTI to be assigned to the participant UE in group information table 393 in conjunction with the CS-RNTI contained in the RRCSetupRequest message. Specifically, allocation unit 311 registers the CS-RNTI to be assigned to the participant UE in group information table 393. Fig. 9. The CS-RNTI to be assigned to the participant UE is entered in the "Participant UE CS-RNTI" column, and the CS-RNTI contained in the RRCSetupRequest message is entered in the "Leader UE CS-RNTI" column.

[0206] Next, the allocation unit 311 informs the base station communication unit 312 of the CS-RNTI and wireless uplink resource allocated to the subscriber UE.

[0207] The base station communication unit 312 then registers an allocated status for the reported wireless uplink resource in the wireless resource management table 391. Specifically, the base station communication unit 312 enters the following in the wireless resource management table 391: Fig. 7 in the “Allocated” column, which corresponds to the reported wireless uplink resource, set to “Yes”.

[0208] Furthermore, the base station communication unit 312 registers the reported CS-RNTI and the wireless uplink resource in the allocated resource management table 394. Specifically, the base station communication unit 312 registers the following in the allocated resource management table 394: Fig. 10. The reported CS-RNTI is entered in the "CS-RNTI" column and the reported wireless uplink resource is entered in the "Wireless Uplink Resource" column.

[0209] Referring again to Fig. 4, step S190 is described.

[0210] In step S190, the participant UE receives the allocation response message from the base station 300.

[0211] The participant UE then registers the participant allocation (wireless participant ID, wireless participant resource) specified in the allocation response message.

[0212] Details regarding step S190 will be described later.

[0213] The following processing is carried out in every participant UE except the lead UE.

[0214] First, the wireless communication unit 212 receives the RRCSetup message via the communication device 204 from the base station 300.

[0215] Next, the wireless communication unit 212 registers the CS-RNTI specified in the received RRCSetup message as the CS-RNTI of the UE 200 itself.

[0216] The wireless communication unit 212 also registers the wireless uplink resource specified in the received RRCSetup message as the wireless uplink resource of the UE 200 itself.

[0217] Next, the wireless communication unit 212 communicates the CS-RNTI specified in the received RRCSetup message to the request control unit 211.

[0218] Then the request control unit 211 determines a successful allocation of the wireless uplink resource.

[0219] The processing of the wireless resource allocation procedure ends after step S190.

[0220] After step S190, the lead UE establishes wireless communication via the base station 300 using the lead allocation. Every subscriber UE, except the lead UE, establishes wireless communication via the base station 300 using the subscriber allocation.

[0221] For example, each UE 200 transmits the acquisition data obtained from the sensor 110 to the server 120 via the base station 300, using its own wireless uplink resource. ***Effects of Implementation 1***

[0222] In embodiment 1, it is possible to determine the identification information of the group to which the UEs 200 belong in such a way that the identification information is unique within a base station 300.

[0223] However, if wireless uplink resources are allocated separately to a large number of UEs via Configured Grants, a difference equal to or greater than the wireless frame time of the 5G system can occur in the timings of the wireless resources of the large number of UEs. For example, a difference of 10 milliseconds or more can occur.

[0224] Fig. Figure 14 is a diagram that provides an example of the allocation of wireless uplink resource timings to three UEs.

[0225] By combining the base station processing described in embodiment 1 and patent reference 1, the following effects can be achieved. Wireless uplink resources can be allocated to a multitude of UEs 200 via Configured Grants. In this case, it is possible to allocate the wireless uplink resources to the multitude of UEs 200 at times that are as close together as possible. In this way, an increase in the processing delay of acquisition data caused by a difference between the reception time of the data received by the server 120 at the earliest time and the reception time of the data received by the server 120 at the latest time can be suppressed. Design 2.

[0226] With regard to an embodiment in which wireless resources are allocated to a plurality of wireless communication terminals such that a difference in the timings of the wireless resources is equal to or less than a permissible difference, differences from embodiment 1 are mainly based on the Fig. Described in sections 15 to 18. *** Configuration Description ***

[0227] Based on Fig. Section 15 describes a configuration of the UE 200.

[0228] The UE 200 includes an inter-terminal communication unit 214 instead of the user interface unit 213. The inter-terminal communication unit 214 functions as the group setting unit and as an allocation acquisition unit.

[0229] The terminal program causes a computer to operate as the Inter-Terminal Communication Unit 214 instead of the User Interface Unit 213.

[0230] The configuration of base station 300 is the same as the configuration in embodiment 1. *** Description of a Functionality ***

[0231] Based on Fig. Section 16 describes the wireless resource allocation method.

[0232] Steps S210 to S290 correspond to steps S110 to S190 in embodiment 1.

[0233] In step S210, a large number of the UEs 200 form an endpoint group. Details regarding step S210 will be described later.

[0234] The following processing is performed in each UE 200.

[0235] First, the request control unit 211 instructs the inter-terminal communication unit 214 to send a UE group.

[0236] Next, the inter-terminal communication unit 214 sends a participation request message, along with the terminal identifier of the UE 200 itself, via the communication device 204 to other UEs 200. The participation request message is a message that requests participation within the UE group. For example, the participation request message is repeatedly transmitted via broadcast communication at intervals during a time T1. The time T1 is preset as a parameter of the UE 200.

[0237] The device identifier is an identifier of the UE 200 itself when communicating with other UE 200s. In a wireless LAN, for example, a MAC address is used as the device identifier. LAN is an abbreviation for Local Area Network. MAC is an abbreviation for Media Access Control.

[0238] Next, the inter-terminal communication unit 214 receives participation request messages from other UEs 200 via the communication device 204 and registers the terminal identifiers of the senders of the received participation request messages.

[0239] The Inter-Terminal Communication Unit 214 then registers a set of recorded communication identifiers as a set of communication identifiers of subscriber UEs. For example, the Inter-Terminal Communication Unit 214 registers the set of communication identifiers of the subscriber UEs when time T1 has elapsed since the first transmission of the participation request message.

[0240] In step S220, the endpoint group selects the lead endpoint.

[0241] Details regarding step S220 will be described later.

[0242] The following processing is performed in each UE 200 that belongs to the terminal group.

[0243] First, the Inter-End Device Communication Unit 214 determines whether the UE 200 itself is selected as the lead UE, based on the terminal identifier of the UE 200 itself and the terminal identifier of each of the other participant UEs.

[0244] In particular, the bit sequence of the terminal identifier of each subscriber UE is treated as an unsigned binary integer. The inter-terminal communication unit 214 compares the terminal identifier of UE 200 itself with the terminal identifier of each of the other subscriber UEs. If the terminal identifier of UE 200 itself is greater than the terminal identifier of any of the other subscriber UEs, the inter-terminal communication unit 214 determines that UE 200 itself is the lead UE. If the terminal identifier of UE 200 itself is less than the terminal identifier of at least one of the other subscriber UEs, the inter-terminal communication unit 214 determines that UE 200 itself is not the lead UE.

[0245] The inter-terminal communication unit 214 then communicates the determination result to the request control unit 211.

[0246] Then the request control unit 211 registers the determination result.

[0247] In step S230, the lead UE sends an allocation request message to the base station 300.

[0248] Step S230 is the same as step S130 in embodiment 1.

[0249] In step S240, the base station 300 receives the allocation request message from the lead UE.

[0250] Next, the base station 300 assigns a wireless UE identifier and a wireless uplink resource to the lead UE.

[0251] The base station 300 then sends an allocation response message to the lead UE, specifying the lead allocation.

[0252] Step S240 is the same as step S140 in embodiment 1.

[0253] In step S250, the lead UE receives the allocation response message from the base station 300.

[0254] The lead UE then registers the lead allocation (wireless lead identifier, wireless lead resource) specified in the allocation response message.

[0255] Step S250 is the same as step S150 in embodiment 1.

[0256] In step S260, the lead UE communicates the wireless lead identifier.

[0257] Each participating UE (except for the lead UE) registers the communicated wireless lead identifier.

[0258] With regard to the guiding UE, the details of step S260 are described.

[0259] First, the request control unit 211 instructs the inter-terminal communication unit 214 to communicate the CS-RNTI of the lead UE.

[0260] Then the inter-terminal communication unit 214 sends an identification message to the other participant units via the communication device 204.

[0261] The identifier message is a message that communicates and contains the wireless routing identifier. The identifier message is transmitted via broadcast communication.

[0262] For each participant UE that is not the lead UE, the details of step S260 are described.

[0263] First, the inter-terminal communication unit 214 receives the identification message from the lead UE via the communication device 204.

[0264] Next, the Inter-End Communication Unit 214 informs the Request Control Unit 211 of the CS-RNTI contained in the received identifier message.

[0265] Then the request control unit 211 registers the communicated CS-RNTI as the CS-RNTI of the lead UE.

[0266] In step S270, each participating UE (excluding the lead UE) sends an allocation request message to the base station 300.

[0267] This allocation request message contains the wireless conductor identifier and a permissible difference Td as parameters.

[0268] The permissible difference Td specifies the longest permissible time difference between the timing of the wireless control resource and the timing of the wireless subscriber resource. The permissible difference Td is preset as a parameter for each UE 200.

[0269] Details regarding step S270 will be described later.

[0270] The following processing is carried out in every participant UE except the lead UE.

[0271] First, the request control unit 211 communicates the CS-RNTI of the lead UE and the permissible difference Td, and requests the wireless communication unit 212 to submit an allocation request.

[0272] Then the wireless communication unit 212 sends an RRCSetupRequest message to the base station 300 via the communication device 204.

[0273] This RRCSetupRequest message contains the CS-RNTI of the lead UE and the allowable difference Td in parameters.

[0274] Fig. Figure 17 shows an example of an ASN.1 definition of the RRCSetupRequest message.

[0275] The RRCSetupRequest message contains the CS-RNTI and the allowable difference Td as parameters in the section enclosed by a bold frame.

[0276] Referring again to Fig. 16, the description continues from step S280.

[0277] In step S280, the base station 300 receives the allocation response message from the subscriber UE.

[0278] Next, the base station 300 assigns a wireless UE identifier to the subscriber UE.

[0279] The Base Station 300 also determines the wireless guide resource based on the wireless guide identifier contained in the allocation request message and assigns a wireless uplink resource to the subscriber UE whose timing is such that any time difference to the timing of the wireless guide resource is equal to or less than the allowable difference Td. The Base Station 300 then sends an allocation response message to the subscriber UE.

[0280] If the allocation of a wireless subscriber resource was successful, an allocation response message is sent at that time, indicating the successful allocation and that the subscriber allocation was sent. If the allocation of a wireless subscriber resource failed, an allocation response message is sent indicating the failed allocation.

[0281] Regarding the details of step S280, the differences to step S180 in embodiment 1 are essentially described below.

[0282] Allocation unit 311 assigns a wireless uplink resource to the subscriber unit, the timing of which is such that a time difference to the timing of the wireless guide resource is equal to or less than the permissible difference Td.

[0283] If the wireless uplink resource is assigned to the subscriber UE, the base station communication unit 312 sends an RRCSetup message, indicating successful allocation, to the subscriber UE via the communication unit 304. This RRCSetup message specifies the CS-RNTI and the wireless uplink resource.

[0284] If a wireless uplink resource is not assigned to the subscriber UE, the base station communication unit 312 sends an RRCReject message to the subscriber UE indicating that allocation has failed.

[0285] Each of the RRCSetup message and the RRCReject message is equivalent to the allocation response message.

[0286] Regarding the details of the allocation of a wireless uplink resource to the subscriber UE, the following mainly describes the differences to step S180 in embodiment 1.

[0287] Next, allocation unit 311 refers to wireless resource management table 391 and determines a wireless uplink resource to be assigned to the subscriber UE from among the unassigned wireless uplink resources. At this point, allocation unit 311 finds a wireless uplink resource whose timing is such that the time difference to the timing of the wireless guide resource is equal to or less than the allowable difference Td, as determined by the wireless uplink resource to be assigned to the subscriber UE.

[0288] If the wireless uplink resource to be assigned to the subscriber UE can be found, the base station 300 registers the CS-RNTI and the wireless uplink resource assigned to the subscriber UE as described in step S180 in embodiment 1.

[0289] Referring again to Fig. Step S290 is described in section 16.

[0290] In step S290, the participant UE receives the allocation response message from the base station 300.

[0291] The participant UE then registers the participant allocation (wireless participant ID, wireless participant resource) specified in the allocation response message.

[0292] Details regarding step S290 will be described later.

[0293] The following processing is carried out in every participant UE except the lead UE.

[0294] The wireless communication unit 212 receives the RRCSetup message or the RRCReject message via the communication device 204.

[0295] If the RRCSetup message is received, the wireless communication unit 212 registers the CS-RNTI specified in the received RRCSetup message as the CS-RNTI of the UE 200 itself. The wireless communication unit 212 also registers the wireless uplink resource specified in the received RRCSetup message as the wireless uplink resource of the UE 200 itself. Furthermore, the wireless communication unit 212 informs the request control unit 211 of the CS-RNTI specified in the received RRCSetup message. The request control unit 211 then determines that the allocation of a wireless uplink resource was successful.

[0296] If the RRCReject message is received, the wireless communication unit 212 informs the request control unit 211 of a failed allocation. The request control unit 211 then determines that the allocation of a wireless uplink resource has failed.

[0297] The processing of the wireless resource allocation procedure ends after step S290. *** Effects of embodiment 2 ***

[0298] In embodiment 2, it is possible to determine the identification information of the group to which the UEs 200 belong in such a way that the identification information is unique within a base station 300.

[0299] Furthermore, it is possible to keep the time difference of the uplink transmit timings assigned to the UEs 200 belonging to the group by Configured Grants equal to or less than a specified value (Td).

[0300] By combining the base station processing described in embodiment 1 and patent reference 1, the following effects can be achieved. Wireless uplink resources can be allocated to a plurality of UEs 200 via Configured Grants. In this case, it is possible to allocate the wireless uplink resources to the plurality of UEs 200 at times that are as close together as possible. In this way, an increase in the processing delay of acquisition data caused by a difference between the reception time of the data received by the server 120 at the earliest time and the reception time of the data received by the server 120 at the latest time can be suppressed. *** Supplement to embodiments ***

[0301] Design 1 and design 2 can also be used in combination with each other.

[0302] For example, in embodiment 1, the wireless conductor identifier can be communicated via wireless communication between a plurality of the UEs 200 as in embodiment 2. Alternatively, in embodiment 2, the wireless conductor identifier can be communicated by displaying it on a screen as in embodiment 1.

[0303] For example, in embodiment 1, a UE group can be formed by wireless communication between a plurality of UEs 200 as in embodiment 2. In embodiment 2, a UE group can be set up via a user interface as in embodiment 1.

[0304] For example, in embodiment 1, the lead UE can be selected from a plurality of UEs 200 via wireless communication, as in embodiment 2. In this case, the lead UE can be selected based on the terminal identifier of each UE 200, as in embodiment 2. In embodiment 2, the lead UE can be selected via a user interface, as in embodiment 1.

[0305] Based on Fig. Section 18 describes a hardware configuration of the UE 200.

[0306] The UE 200 contains a processing circuit 209.

[0307] The processing circuit 209 is hardware that implements the request control unit 211, the wireless communication unit 212, the user interface unit 213 and the inter-device communication unit 214.

[0308] The processing circuit 209 can be dedicated hardware or it can be the processor 201, which executes programs stored in the main memory 202.

[0309] If the processing circuit 209 is purpose-built hardware, then the processing circuit 209 is, for example, a single circuit, a compound circuit, a programmed processor, a parallel programmed processor, an ASIC, an FPGA, or a combination thereof.

[0310] ASIC is an abbreviation for Application Specific Integrated Circuit.

[0311] FPGA is an abbreviation for Field Programmable Gate Array.

[0312] In the processing circuit 209, some functions may be implemented by dedicated hardware, and the remaining functions may be implemented by software or firmware.

[0313] As described above, the functions of the UE 200 can be implemented through hardware, software, firmware or a combination of these.

[0314] Based on Fig. Section 19 describes a hardware configuration of the base station 300.

[0315] The base station 300 contains a processing circuit 309.

[0316] The processing circuit 309 is a hardware component that implements the allocation unit 311 and the base station communication unit 312.

[0317] The processing circuit 309 can be dedicated hardware or it can be the processor 301, which executes programs stored in the main memory 302.

[0318] If the processing circuit 309 is purpose-built hardware, then the processing circuit 309 is, for example, a single circuit, a compound circuit, a programmed processor, a parallel programmed processor, an ASIC, an FPGA, or a combination thereof.

[0319] In the 309 processing circuit, some functions may be implemented by dedicated hardware, and the remaining functions may be implemented by software or firmware.

[0320] As described above, the functions of the Base Station 300 can be implemented through hardware, software, firmware, or a combination of these.

[0321] Each embodiment is an example of a preferred embodiment and is not intended to limit the technical scope of this disclosure. Each embodiment may be implemented partially or in combination with another embodiment. The processes described by means of the flowcharts and the like may be modified as necessary.

[0322] The “unit” of each element of the UE 200 and the base station 300 can be interpreted as “process”, “step”, “circuit” or “circuit”. Reference symbol list

[0323] 100: Wireless communication system; 110: Sensor; 120: Server; 130: 5G system; 200: UE; 201: Processor; 202: RAM; 203: Auxiliary storage device; 204: Communication device; 205: Input / output interface; 209: Processing circuit; 211: Request control unit; 212: Wireless communication unit; 213: User interface unit; 214: Inter-terminal communication unit; 221: Group assignment screen; 222: Line selection screen; 223: Identification message screen; 224: Identification input screen; 290: Storage unit; 300: Base station; 301: Processor; 302: RAM; 303: Auxiliary storage device; 304: Communication device; 305: Input / Output Interface; 309: Processing Circuit; 311: Allocation Unit; 312: Base Station Communication Unit; 390: Storage Unit; 391: Wireless Resource Management Table; 392: Identifier Management Table; 393: Group Information Table; 394: Allocated Resource Management Table. QUOTES INCLUDED IN THE DESCRIPTION

[0000] This list of documents cited by the applicant was automatically generated and is included solely for the reader's convenience. The list is not part of the German patent or utility model application. The DPMA accepts no liability for any errors or omissions. Cited patent literature

[0000] JP 2018-191110 A

[0023]

Claims

[1] Wireless resource allocation procedure by a base station and a terminal group, wherein the terminal group consists of a wireless communication terminal serving as the lead terminal and one or more wireless communication terminals, each serving as a subscriber terminal except for the lead terminal, wherein the wireless resource allocation procedure comprises: Communication by the lead terminal of a wireless lead identifier assigned to the lead terminal by the base station; Sending a request message containing the wireless lead identifier communicated by each subscriber terminal except the lead terminal to the base station; Receiving, for each subscriber terminal except the lead terminal, the request message from the subscriber terminal; determining a wireless lead resource assigned to the lead terminal based on the wireless lead identifier contained in the request message from the subscriber terminal; assigning a wireless resource whose timing is close to that of the wireless lead resource to the subscriber terminal as a wireless subscriber resource; and sending a response message indicating the wireless subscriber resource to the subscriber terminal via the base station; and Received by each subscriber terminal except the lead terminal, the reply message to the subscriber terminal. [2] Wireless resource allocation method according to claim 1, where the lead terminal sends a request message, which does not contain the wireless lead identifier, to the base station, wherein the base station receives the request message from the lead terminal, assigns the wireless lead identifier and the wireless lead resource to the lead terminal, and sends a response message specifying the wireless lead identifier and the wireless lead resource to the lead terminal, and wherein the lead terminal receives the reply message to the lead terminal and communicates the wireless lead identifier contained in the reply message that was received. [3] Wireless resource allocation method according to claim 1 or claim 2, wherein the base station assigns a wireless subscriber identifier to each subscriber terminal other than the lead terminal and sends a message indicating the wireless subscriber identifier and the wireless subscriber resource as the reply message to the subscriber terminal. [4] Wireless resource allocation method according to claim 3, where the request message is an RRCSetupRequest message, where both the wireless conductor identifier and the wireless subscriber identifier are a CS-RNTI, and where both the wireless guide resource and the wireless subscriber resource are assigned via a Configured Grant. [5] Wireless resource allocation method according to any one of claims 1 to 4, wherein each subscriber terminal, other than the lead terminal, sends a message to the base station containing the wireless lead identifier that was communicated and a permissible difference as the request message, and wherein the base station assigns to the subscriber terminal a wireless resource whose timing is equal to or less than the permissible difference to the timing of the wireless guide resource as the wireless subscriber resource. [6] Wireless resource allocation method according to any one of claims 1 to 5, wherein the lead terminal communicates the wireless lead identifier by displaying a screen showing the wireless lead identifier on a display, and where the wireless routing identifier that was communicated is set by a user in each subscriber terminal except the routing terminal. [7] Wireless resource allocation method according to any one of claims 1 to 5, wherein the lead terminal communicates the wireless lead identifier via wireless communication with each subscriber terminal except the lead terminal. [8] Wireless resource allocation method according to any one of claims 1 to 7, wherein each wireless communication terminal is assigned to the terminal group by specification via a user interface. [9] Wireless resource allocation method according to any one of claims 1 to 7, wherein a plurality of wireless communication terminal devices form the terminal group by means of wireless communication. [10] Wireless resource allocation method according to any one of claims 1 to 9, wherein one of the wireless communication terminals is selected as the lead terminal by specifying it via a user interface. [11] Wireless resource allocation method according to any one of claims 1 to 9, wherein a plurality of wireless communication terminals select the lead terminal by wireless communication. [12] Wireless resource allocation method according to claim 11, wherein each of the plurality of wireless communication terminals transmits a terminal identifier, which is individually determined, and determines whether each of the plurality of wireless communication terminals is selected as the lead terminal based on the terminal identifier of each of the plurality of wireless communication terminals and each terminal identifier of each other of the plurality of wireless communication terminals. [13] Base station to implement the wireless resource allocation method according to any one of claims 1 to 12 in conjunction with the terminal group. [14] Base station program to cause a computer to operate as the base station according to claim 13. [15] Wireless communication terminal for implementing the wireless resource allocation method according to any one of claims 1 to 12 in conjunction with the base station. [16] Terminal program to cause a computer to operate as the wireless communication terminal device according to claim 15.

Images