Planned configuration in wireless communication systems

The method allows wireless communication systems to autonomously update configurations based on criteria, addressing interference and resource allocation challenges, ensuring efficient communication without network infrastructure, and enabling seamless updates across devices.

JP2026090505APending Publication Date: 2026-06-02TOYOTA JIDOSHA KK

Patent Information

Authority / Receiving Office
JP · JP
Patent Type
Applications
Current Assignee / Owner
TOYOTA JIDOSHA KK
Filing Date
2026-02-25
Publication Date
2026-06-02

AI Technical Summary

Technical Problem

Wireless communication systems face challenges in efficiently managing communication resources due to interference and complex resource allocation, especially in scenarios where network infrastructure is unavailable or not needed, leading to difficulties in configuring devices for communication.

Method used

A method and system for applying configuration information in nodes using criteria-based updates, allowing devices to autonomously adjust their configurations based on current information such as date, location, and traffic load without requiring network signaling, thereby facilitating simultaneous updates across a large number of devices.

Benefits of technology

Enables efficient and reliable configuration updates in wireless communication systems, ensuring seamless communication even when devices are outside network coverage, reducing the need for infrastructure connections and software upgrades.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure 2026090505000001_ABST
    Figure 2026090505000001_ABST
Patent Text Reader

Abstract

Pre-configuration can be used appropriately in situations such as when a device cannot receive network signaling before accessing the communication medium. [Solution] The method is a method performed by a user terminal (UE), comprising the steps of obtaining at least one set of time information and configuration information relating to wireless communication synchronization resources from a network node communicating with the UE, wherein the time information includes the time at which the configuration information becomes available, and the steps of performing synchronization using the configuration information after the current time is after the time indicated in the time information.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] (Cross - reference to related applications) This application claims the benefit of priority of U.S. Provisional Patent Application No. 63 / 377,590, filed on September 29, 2022, the entire content of which is incorporated herein by reference.

[0002] This disclosure generally relates to communications, and more particularly, to methods, systems, and devices for planned configurations in wireless communication systems.

Background Art

[0003] Multi - user wireless and electrical communication systems may suffer from a lack of communication resources. Thus, wireless communication systems utilize geographical reuse of spectrum resources. In the context of terrestrial mobile communication systems, the solution is generally referred to as the cellular concept, but the same principle can also be applied to other systems such as satellite systems, ad - hoc networks, radio broadcast systems, and direct communication between transceivers such as peer - to - peer communication systems.

[0004] Spectrum reuse can facilitate efficient use of limited resources, but it can cause complex resource allocation problems due to mutual interference caused by potential contamination of the signal carrying information by the presence of another similar type of signal at the receiving antenna.

[0005] In mobile communication systems, radio resource control protocols and media access control protocols can solve some of these problems. When a network has a signaling connection with user equipment, radio resources are configured and then reconfigured according to time-varying interference and traffic conditions. If user equipment is idle and thereby temporarily unreachable by controlling network entities through the signaling connection, broadcasted system information configures resources for purposes such as random access, synchronization, and paging. This system information is further retrieved at regular intervals during cell re-selection.

[0006] If a device cannot receive network signaling before accessing the communication medium, more difficult scenarios may arise if providing such a configuration is difficult and / or too expensive, or if the network infrastructure is not used / needed. In such cases, pre-configurations can be used. Pre-configurations may be stored or hardcoded in the device software, or provided, for example, on a Universal Integrated Circuit Card (UICC). Similar problems may occur within network nodes, which do not necessarily benefit from operation and maintenance at a given time.

[0007] Third-Generation Partnership Project (3GPP) technologies are documented in 3GPP technical specifications and can be pre-configured in many use cases, as illustrated below.

[0008] (1) Uplink resources may be pre-configured for machine-to-machine communication devices.

[0009] (2) The home base station has pre-configured information for infrastructure connectivity. ru.

[0010] (3) Relay nodes may be pre-configured using information about the cells they are permitted to access.

[0011] (4) 5G Quality of Service (QoS) parameters can be pre-configured in the user equipment (UE).

[0012] (5) The UE may be pre-configured with information regarding differentiated handling of traffic for different networks in a network slicing deployment.

[0013] (6) The UE may use pre-configured information to discover relay nodes.

[0014] (7) The mapping of cell identification information in 3GPP non-terrestrial communications may be based on pre-configured information at the UE.

[0015] (8) Public safety and mission-critical push-to-talk devices may use pre-configured communication and synchronization resources.

[0016] (9) Sidelink communication devices and proximity services may be pre-configured for out-of-coverage autonomous resource selection, for example, by using pre-configured priority thresholds and pre-configured radio parameters for discontinuous reception.

[0017] (10) 3GPP Technical Specification (TS) 31.102 may be applied to Universal Mobile Communications Services (UMTS), Long-Term Evolution (LTE), and / or Fifth Generation (5G) using information stored in a Universal Subscriber Identification Module (USIM). This information may be updated, for example, by a Subscriber Identification Module (SIM) / USIM toolkit by a Home Public Land Mobile Network (PLMN). This information may be used for various operations, such as providing information to the user regarding security, network selection, or call costs. Note that other examples besides TS 31.102 may be possible for USIM information.

[0018] (11) The information may be received by the UE via non-access layer (NAS) messages, for example, by using 3GPP TS24.301 for LTE or 3GPP TS25.401 for 5G. [Overview of the Initiative] [Means for solving the problem]

[0019] In some embodiments, a method is provided for applying configuration information for use in a node. This method includes the step of determining current information. In the node, one or more sets of criteria and configuration information corresponding to each criterion are accessed. The current information is compared with one or more sets of criteria. On the condition that the current information matches at least one criterion from one or more sets of criteria, the configuration information corresponding to at least one matching criterion is applied for use in the node.

[0020] In some embodiments, a node is provided for applying configuration information for use in the node. The node includes memory configured to store instructions, and a processor, the processor executing instructions stored in memory to determine current information, accessing one or more sets of criteria and configuration information corresponding to each criterion in the node, comparing the current information with one or more sets of criteria, and the current information with one or more sets of criteria It is configured to apply configuration information corresponding to at least one matching criterion for use with the node, provided that it matches at least one of the following criteria.

[0021] In some embodiments, a non - transient computer - readable medium storing instructions executable by one or more processors of a node within a communication network to execute a method is provided. The method includes a step of determining current information. At the node, one or more sets of criteria and configuration information corresponding to each criterion are accessed. The current information is compared with the one or more sets of criteria. On the condition that the current information matches at least one criterion of the one or more sets of criteria, the configuration information corresponding to the at least one matching criterion is applied for use at the node.

[0022] The above and other aspects and their embodiments are described in more detail in the following description and drawings.

Brief Description of the Drawings

[0023] [Figure 1] It is a block diagram of a node in an embodiment of the present disclosure. [Figure 2] It is a flowchart of a method for applying configuration information for use at a node in an embodiment of the present disclosure.

Modes for Carrying Out the Invention

[0024] Here, typical embodiments are referred to in detail and examples thereof are shown in the drawings. The following description refers to the accompanying drawings in which the same numbers represent the same or similar elements in different drawings, unless otherwise indicated. The embodiments described in the following description of typical embodiments do not represent all embodiments consistent with the present disclosure. Instead, they are merely examples of apparatuses, systems, and methods consistent with aspects related to the subject matter that may be recited in the appended claims.

[0025] In some embodiments, the disclosed methods, systems, apparatuses, and devices generally relate to configurations in wireless and electrical communication systems and correspond to, but are not limited to, configuration use cases (such as pre-configuration use cases) as exemplified above for the set of 3GPP functions, architectures, and features that have been standardized so far.

[0026] Configurations can be difficult and time-consuming to change and can be particularly complex when changes need to be made simultaneously for a large user population. Also, it can be difficult to ensure that all devices have updated or changed their configurations. At least some of the disclosed embodiments can mitigate or eliminate the above difficulties.

[0027] In some embodiments, when a configuration is stored in a device (e.g., a node), it can be changed or updated by an infrastructure node, for example, before accessing a communication medium. Successfully updating the configuration information can include subscribing all devices to an operator service, staying within network coverage, acquiring system information, or frequently setting up a signaling connection with an infrastructure node.

[0028] In some embodiments, when configuration information is provided by a UICC or SIM, an end user or service personnel can update or change the card. Successfully changing or updating the configuration information may include changing or updating all cards in all deployed devices that use the configuration information.

[0029] As used herein, the term "configuration information" may also include information stored in a node (e.g., within the memory of the node, within a SIM card, or within a similar device), and information received by the node from a communication network (e.g., pre-configuration information as understood under 3GPP standards).

[0030] As used herein, the term “node” may include network nodes (e.g., advanced node B (eNB) or 5G node B (gNB)), roadside units (RSU), transit nodes, user equipment (UE), or mobile equipment (ME). In one embodiment, a node may be configured to communicate using sidelink communication.

[0031] node

[0032] Figure 1 is a block diagram of a node 100 in an embodiment of the present disclosure. The node 100 may be mounted in a fixed position on a moving vehicle (e.g., as a roadside unit (RSU)) or may be a mobile device carried by a person (e.g., as an UE). The node 100 can take any form, but is not limited to a vehicle, a vehicle-mounted component, an RSU, a laptop computer, a wireless terminal including a mobile phone, a wireless handheld device, a wireless personal device, or any other form. Referring to Figure 1, the node 100 may include an antenna 102 that can be used for transmitting and / or receiving electromagnetic signals to and from a base station or other nodes. The antenna 102 may include one or more antenna elements and can enable different input / output antenna configurations, including multiple input / multiple output (MIMO) configurations, multiple input / single output (MISO) configurations and single input / multiple output (SIMO) configurations. In some embodiments, the antenna 102 may include multiple (e.g., tens or hundreds) antenna elements and can enable multi-antenna functions such as beamforming. In some embodiments, the antenna 102 is a single antenna.

[0033] Node 100 may include a transceiver 104 coupled to antenna 102. The transceiver 104 may be a radio transceiver at node 100 and may communicate bidirectionally with a base station or other nodes. For example, the transceiver 104 may receive radio signals from a base station via downlink and transmit radio signals to the base station via uplink communication. The transceiver 104 may also receive radio signals from other nodes, such as UEs or RSUs, via sidelink communication and transmit radio signals to them. The transceiver 104 may include a modem for modulating packets, providing the modulated packets to antenna 102 for transmission, and demodulating packets received from antenna 102.

[0034] Node 100 may include memory 106. Memory 106 may be any type of computer-readable storage medium, including volatile or non-volatile memory devices, or a combination thereof. Computer-readable storage medium includes, but is not limited to, non-temporary computer storage medium. Non-temporary storage medium may be accessed by a general-purpose or dedicated computer. Examples of non-temporary storage medium include, but are not limited to, portable computer diskettes, hard disks, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM), electrically erasable programmable ROM (EEPROM), digital multipurpose disks (DVDs), flash memory, compact disk (CD)ROM or other optical disk storage devices, magnetic disk storage devices or other magnetic storage devices, etc. Non-temporary medium may be used to carry or store desired program code means (e.g., instructions and / or data structures) and may be accessed by a general-purpose or dedicated computer, or a general-purpose or dedicated processor. In some examples, software The code / program code may be transmitted from a remote source (e.g., a website, server, etc.) using coaxial cable, fiber optic cable, twisted pair, digital subscriber line (DSL), or wireless technologies such as infrared, radio, and microwave. In such examples, coaxial cable, fiber optic cable, twisted pair, DSL, or wireless technologies such as infrared, radio, and microwave are within the definition of a medium. Combinations of the above examples are also within the scope of a computer-readable medium.

[0035] Memory 106 can store identification information for node 100 and information about signals and / or data received by antenna 102. Memory 106 can also store post-processing signals and / or data. Memory 106 can also store computer-readable program instructions, mathematical models, and algorithms used in signal processing in transceiver 104 and calculations in processor 108. Memory 106 can further store computer-readable program instructions executed by processor 108 to operate node 100 to perform various functions described elsewhere in this disclosure, such as method 200 shown in the flowchart of Figure 2. In some examples, memory 106 may include a basic input / output system (BIOS) that can control basic hardware or software operations, such as interactions with peripheral components or devices.

[0036] The computer-readable program instructions of this disclosure may be assembler instructions, instruction set architecture (ISA) instructions, machine instructions, machine-dependent instructions, microcode, firmware instructions, state setting data, or source code or object code written in any combination of one or more programming languages, including object-oriented programming languages ​​and conventional procedural programming languages. The computer-readable program instructions can be executed on a computing device as a completely standalone software package, or partially on a first computing device and partially on a second computing device located remotely from the first computing device. In the latter scenario, the second remote computing device may be connected to the first computing device via any type of network, including a local area network (LAN) or a wide area network (WAN).

[0037] Node 100 may include a processor 108 which may include hardware devices having processing capabilities. The processor 108 may include at least one of the following: a general-purpose processor, a digital signal processor (DSP), a central processing unit (CPU), a graphics processing unit (GPU), a microcontroller, an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA), a programmable logic device, a discrete gate or transistor logic component, a discrete hardware component, or other programmable logic devices. Examples of general-purpose processors include, but are not limited to, a microprocessor, any conventional processor, a controller, a microcontroller, or a state machine. In some embodiments, the processor 108 may be implemented using a combination of devices (e.g., a combination of a DSP and a microprocessor, multiple microprocessors, one or more microprocessors combined with a DSP core, or any other such configuration). The processor 108 can receive downlink or sidelink signals from the transceiver 104 and further process the signals. The processor 108 can also receive data packets from the transceiver 104 and further process the packets. In some embodiments, the processor 108 may be configured to operate the memory using a memory controller. In some embodiments, the memory controller may be integrated into the processor 108. The processor 108 performs various functions on node 100. To achieve this, it may be configured to execute a set of computer-readable instructions stored in memory (for example, memory 106).

[0038] Node 100 may include a Global Positioning System (GPS) 110. The GPS 110 may be used to enable location-based services or other services based on the geographical location of Node 100 and / or for synchronization between nodes. The GPS 110 can receive Global Navigation Satellite System (GNSS) signals from a single satellite or multiple satellite signals via Antenna 102 and provide the geographical location of Node 100 (e.g., the coordinates of Node 100). In some embodiments, the GPS 110 may be omitted.

[0039] Node 100 may include an input / output (I / O) device 112 that can be used to communicate the results of signal processing and calculations to a user or another device. The I / O device 112 may include a user interface that includes a display and input devices for sending user commands to the processor 108. The display may be configured to show the status of signal reception in node 100, data stored in memory 106, the status of signal processing, and calculation results, etc. The display may include, but is not limited to, a cathode ray tube (CRT), liquid crystal display (LCD), light-emitting diode (LED), gas plasma display, touchscreen, or other image projection device for displaying information to the user. The input device may be any type of computer hardware equipment used to receive data and control signals from the user. The input device may include, but is not limited to, a keyboard, mouse, scanner, digital camera, joystick, trackball, cursor directional keys, touchscreen monitor, or audio / video commander, etc.

[0040] Node 100 may further include machine interfaces 114 such as an electric bus for connecting transceivers 104, memory 106, processor 108, GPS 110, and I / O devices 112.

[0041] In some embodiments, node 100 may be configured or programmed for sidelink communication. Processor 108 may be configured to execute instructions stored in memory 106 to perform a method for applying configuration information used by node 100, such as method 200 described in relation to Figure 2. Processor 108 is configured to execute instructions stored in memory 106 to determine current information, access one or more sets of criteria and configuration information corresponding to each criterion in the node (e.g., memory 106), compare the current information with one or more sets of criteria, and, on the condition that the current information matches at least one criterion from one or more sets of criteria, apply the configuration information corresponding to at least one matching criterion for use in node 100.

[0042] Apply configuration information

[0043] In some embodiments, if configuration information is provided in UICC or SIM, an end user or service personnel can update or modify the card. Successfully modifying or updating the configuration information may include modifying or updating all cards in all deployed devices that use the configuration information. In embodiments where nodes communicate using sidelink information, there may not be a control entity to instruct or command the node to use a particular frequency, for example. If no control entity exists, the node may rely on the configuration information to be able to communicate.

[0044] In some embodiments, configuration information can be successfully and reliably changed simultaneously to a large number of devices without setting up bidirectional signaling connections and contexts with network infrastructure entities, without registering devices with carrier services, without requiring software or hardware upgrades (e.g., UICC or SIM cards), or without repetitive work and maintenance for network infrastructure entities, even when the devices are outside the coverage area of ​​the wireless system.

[0045] At least some embodiments relate to methods, systems, apparatus, and devices for changing and updating configuration information in different types of equipment and infrastructure nodes in wireless and telecommunications systems. Herein, these equipment and infrastructure nodes are collectively referred to as “nodes” to include end-user equipment (e.g., UEs, MEs), routers, gateways, repeaters, relay nodes, satellites, roadside units, vehicle-mounted modules, modems, and network infrastructure nodes such as their base stations, controllers, access points, and subsystems.

[0046] In at least some embodiments, the disclosed methods, systems, apparatus, and devices may use a data structure that transmits a set of configuration information along with validity criteria. In some embodiments, the data structure may be a tabular data structure having one or more contents, e.g., rows. An example of an embodiment of such a data structure is a list having multiple instances or objects. Each content or row may contain one or more configurations. One or more validity criteria (e.g., columns) may be associated with the corresponding configuration information.

[0047] The configuration may include, for example, uplink radio resources for machine-to-machine communication, communication and synchronization resources for public safety communications, radio resource pools and bandwidth allocations for sidelink communications, quality of service (QoS) parameters, or configured radio parameters for discontinuous reception in sidelink group communications.

[0048] A node can evaluate one or more relevant validity criteria (e.g., columns) associated with one or more configurations (e.g., one or more rows), for example, by starting with a first configuration (e.g., rows) and scanning them one by one. When a node finds a configuration (e.g., a row) that satisfies the criteria, it can apply the configuration (e.g., the configuration of that row). If two or more criteria are associated with one (or more) configurations, in one embodiment, a logical "or" function can be used to evaluate validity between the multiple criteria. In another embodiment, a logical "exclusive OR" (XOR) function can be used. In yet another embodiment, a logical "and" function can be used. If three or more criteria are used, it is also possible to use any combination of the logical "or", "exclusive or", and / or "and" functions.

[0049] As used herein, the term “apply” corresponds to one or more of the following: use, implement, select, activate, or configure (e.g., configuration in active mode). In some embodiments, configuration information may be applied in the active mode of the node. In some embodiments, configuration information may be applied in the idle mode of the node.

[0050] In some embodiments, the node can use initial configuration information. For example, some wireless communication parameters can be set to “default settings” so that the node can establish initial communication with the network using default settings. In such embodiments, as described elsewhere in this disclosure, the current information is based on at least one criterion and If they match, the initial configuration information may be modified (i.e., different configuration information may be applied). In some embodiments, the initial configuration information may be stored in the node's memory, stored in a SIM within the node, or retrieved from a network communicating with the node. Note that when a node uses initial configuration information, not all possible settings or parameters of the node need to be indicated by the initial configuration information.

[0051] In some embodiments, the validity criterion includes date and time information. The criterion is compared with the current date and time information obtained by the node. The node may obtain date and time information from, for example, its own internal clock or from an external time reference such as a server on the Internet or a Global Navigation Satellite System (GNSS). The date and time information may be expressed in Coordinated Universal Time (UTC).

[0052] Some embodiments, including date and time information, can provide resource allocation for 3GPP sidelink and vehicle-to-vehicle (V2V) communication based on a specific point in time. The configuration can, for example, define a radio resource pool associated with GNSS date and time information to indicate the exact point in time when the resource pool is scheduled to be used / switched by all nodes in the future.

[0053] The configuration may also be a splitting between two or more spectral resources to constitute a ratio and / or proportion between two or more spectral resources in, for example, time, frequency, or code domain; a splitting between hardware resources such as transmitter chains, receiver chains, antennas, or antenna arrays; a splitting between resources from two or more radio access technologies (RATs); a splitting between different channels, such as time slots, frequency bands, codes, or antenna beams; or a combination thereof.

[0054] An example of a configuration data structure is shown in Table 1, where the first column is the validity criterion for UTC date and time information associated with the configured resource pool in the second column. A node can obtain date and time information from, for example, a GNSS system, scan the rows of the data structure, and evaluate the obtained date and time information against the validity criterion information. If the criterion is met, the node can use the corresponding resource pool in the same row until a new criterion is met.

[0055] In the example in Table 1, the resource pool is changed once a year. This means that all nodes with this data structure can simultaneously change their resource pool configuration with time precision in the same manner from GNSS, for example, without signaling connections to control cellular network entities.

[0056] For simplicity, Table 1 shows resource pools, indicated only by their names or indices. In some embodiments, the rows may include detailed resource configurations, for example, as defined in the 3GPP preconfiguration.

[0057] [Table 1] Example of a planned resource pool configuration based on UTC

[0058] In some embodiments, the effectiveness criterion includes geographic location information. The criterion is compared with current location information obtained by the node. For example, the configuration may be defined for a specific location or country. The node may obtain current location information from GNSS, or it may be provided by an end user, for example, in a vehicle.

[0059] Table 2 defines resource pools for each country. In this example, all nodes with this data structure will change their resource pool configuration in the same way based on their location, for example, without a signaling connection with a controlling cellular network entity. Other examples of geographic location information may include tracking areas or tracking area lists (for LTE) or registration areas (for 5G).

[0060] [Table 2] Example of a planned configuration of a location-based resource pool

[0061] In some embodiments, the effectiveness criterion includes the traffic load of multiple RATs (e.g., LTE sidelink (SL), New Radio (NR) SL) that may be operating on the same channel or frequency band. The criterion is compared to the traffic load of each RAT estimated by the node. This can be applied to a set measurement period (e.g., a predetermined time length) and / or geographical location. Each measurement period may be a relatively long period (e.g., several days, several weeks, several months) or a shorter period. For example, different resource pool configurations can be defined based on the ratio of traffic load between two RATs using the same channel (or the same frequency band), as shown in Table 3.

[0062] In this specification, the ratio of traffic load between two RATs, referred to as "RATa" and "RATb," can be calculated by dividing the channel busy rate of "RATa" by the channel busy rate of "RATb." If the calculation is based on averaging over a long period, all nodes will obtain the same value for the ratio. The configuration table may be constructed to handle different ratios, for example, where "RATa" has a low traffic load and "RATb" has a high traffic load. This example corresponds to the first row of Table 3. In that case, the traffic load ratio will be a lower value. The corresponding resource pool configuration for this exemplary use case can provide more resources to "RATb" than to "RATa." This means that the configured resource pool for "RATb," referred to as resource pool #1b, has more resources than the configured resource pool for "RATa," referred to as resource pool #1a.

[0063] Another exemplary use case is a situation where traffic loads are balanced between RATs with different ratios, and the resource pools can be the same size. This is illustrated in the second row of Table 3, where the resource pools are indexed to "RATa" and "RATb" as resource pool #2a and resource pool #2b, respectively.

[0064] Another exemplary use case is when the traffic load of "RATb" is reduced to the traffic of "RATa". This is a scenario with a higher load than the fixed load. This is illustrated in the third row of Table 3, where the resource pools are indexed to “RATa” and “RATb” as resource pool #3a and resource pool #3b, respectively. To account for the higher traffic load of “RATb” compared to “RATa”, resource pool #3b can have more resources than resource pool #3a. In this embodiment, common resources can be efficiently shared among different RATs by facilitating adaptation to long-term and / or slow fluctuations in traffic load between RATs.

[0065] [Table 3] Example of a planned resource pool configuration based on the measured traffic load ratio between two RATs.

[0066] In some embodiments, the effectiveness criterion includes the channel busy rate (CBR). The criterion is compared to the “long-term” CBR measured by the node. This can be applied to a set measurement period (e.g., a predetermined time length) and / or geographical location. The long-term CBR measurement period may be relatively long (e.g., several days, several weeks, several months) or shorter than the measurement period of the existing CBR metric for Release 14 / 15 LTE SL (100ms) and Release 16 / 17 NR SL (100ms or 100 slots). For example, different resource pool configurations can be defined based on the measured long-term CBR, as shown in Table 4. [Table 4] Example of a planned resource pool configuration based on long-term CBR

[0067] The effectiveness criteria may include a combination of several parameters, such as date and time information, geographical location, RAT traffic load, and / or long-term CBR.

[0068] In some embodiments, the validity criterion may include some information received by the node. For example, it may be a simple bit (e.g., 0 or 1) received by the node (e.g., from the network). This validity criterion may be received by the node separately from the relevant configuration information. In this way, the new configuration can be activated later with minimal resource overhead. This activation can use existing downlink messages, such as network-to-device messages.

[0069] In some embodiments, the validity criterion may include a specific action performed by the user (e.g., pressing a button, setting up a call, and / or transferring data).

[0070] In some embodiments, the validity criterion may include the fact that a configured resource has not received any transmissions from one of the RATs for a predetermined period of time. This enables a soft transition from one configuration to another in areas where a node transitions during the period from one configuration version to another.

[0071] Any embodiment described herein may be used in combination. For example, after the first configuration is enabled or planned, a second (new) configuration may be provided with a future first effective date and time, and a third configuration may be provided with a future (later) second effective date and time. The third configuration may be equivalent to the first configuration. In addition, additional criteria may be combined with the third configuration so that the third configuration becomes enabled only when the network sends a specific instruction to a node (in another embodiment, no instruction is sent). This makes it possible to automatically "revert to the previous / first configuration" if any problem occurs with the second configuration.

[0072] The embodiments described herein are not limited to selected specific examples and may be applied to other systems or RATs (e.g., 3GPP 6G). The features and results of this disclosure may include node configurations in wireless and telecommunication systems. These may be used in software installed in vehicles using vehicle-to-vehicle and vehicle-to-all (V2X) wireless technologies, but are not limited to these. Furthermore, the technologies described herein may be used for future 3GPP technologies using configuration mechanisms (e.g., 6G V2X).

[0073] Figure 2 is a flowchart of Method 200 for applying configuration information for use in a node in an embodiment of the present disclosure. Method 200 can be implemented, for example, by node 100 as described in relation to Figure 1.

[0074] Current information is determined (step 202). Current information may include any one or more of the following: date and time information from the node's internal clock or an external time reference, geographical information about the node from GNSS, traffic load information of RATs used by the node to communicate with the network, or CBR measured by the node. In some embodiments where the node is configured to use multiple RATs, current information may include traffic load information for each of the multiple RATs. While some specific examples of “current information” have been described above, in some embodiments the scope of “current information” may include information obtained or stored from the node, information about another node measured or determined by the node, or information received by the node from other nodes or the network.

[0075] One or more sets of criteria and configuration information corresponding to each criterion are accessed (step 204). The sets may be stored in memory 106 in Figure 1, for example, in any format as described elsewhere in this disclosure, for example, as a table (e.g., one or more of Table 1, Table 2, Table 3, or Table 4) or a similar data structure. The sets may contain multiple entries, each entry containing one or more criteria and corresponding configuration information. In some embodiments, the criteria include one or more ranges of values ​​for traffic load information, with each criterion corresponding to its respective range of values. In some embodiments, the criteria include one or more ranges of values ​​for CBR, with each criterion corresponding to its respective range of values. Each corresponds to a range of values.

[0076] The current information is compared with one or more sets of criteria (step 206). A determination is made as to whether the current information matches at least one criterion from the set of criteria (step 208). If the current information matches at least one criterion ("YES" in step 208), the configuration information corresponding to the matching criterion is applied by the node (step 210). If the current information does not match any of the criteria ("NO" in step 208), method 200 may be repeated from step 202.

[0077] Method 200 may be performed periodically by the node. For example, Method 200 may be performed by the node when it starts up (i.e., powered on) or after a predetermined idle period. As another example, Method 200 may be performed between one or more of the following conditions: when current information changes, for example when date and time information changes (e.g., at 12:00 a.m. on a given day); when the node moves to a different geographical area (e.g., a different cell); or when measured traffic load information or channel busy rate changes beyond a predetermined amount (e.g., beyond a threshold amount).

[0078] In some embodiments (which may include all the steps of Method 200), initial configuration information for a node can be obtained. The node may obtain initial configuration information from, for example, a network communicating with the node, the node's memory, or a SIM card within the node. In some embodiments, the initial configuration information may include pre-configuration information, such as that defined in the 3GPP standard. In embodiments including initial configuration information, the Method may include a step of applying the initial configuration information within the node on the condition that the current information does not match any criterion of one or more sets of criteria (for example, based on step 208 to determine).

[0079] As used in this disclosure, the use of the term "or" in a list of items indicates an inclusive list. A list of items may begin with a phrase such as "at least one" or "one or more." For example, a list of at least one A, B, or C includes A or B or C or AB (i.e., A and B) or AC or BC or ABC (i.e., A, B, and C). Also, as used in this disclosure, the phrase "based on" preceding a list of conditions should not be interpreted as "based solely on" the set of conditions, but rather as "based at least partially on" the set of conditions. For example, a result described as "based on condition A" may be based on both condition A and condition B without departing from the scope of this disclosure.

[0080] In this specification, the terms “comprise,” “include,” and “contain” may be used interchangeably, have the same meaning, and should be interpreted as comprehensive and open-ended. The terms “comprise,” “include,” and “contain” may be used before a list of elements to indicate that at least all of the listed elements in the list are present, but other elements not on the list may also be present. For example, if A contains B and C, then both {B, C} and {B, C, D} are within the scope of A.

[0081] This disclosure describes exemplary configurations in relation to the accompanying drawings, not representing all possible examples or configurations within the scope of this disclosure. The term “typical” should not be interpreted as “preferred” or “advantageous compared to other examples,” but rather as “example, case, or model.” By reading this disclosure, including the description of the embodiments and drawings, it should be understood that the technology disclosed herein may be implemented using alternative embodiments. This will be understood by those skilled in the art. Those skilled in the art will understand that by combining the embodiments, or specific features of the embodiments described herein, one can arrive at yet another embodiment for carrying out the technology described herein. Therefore, this disclosure should be given the broadest scope that is consistent with the principles and novel features disclosed herein, and is not limited to the examples and designs described herein.

[0082] The flowcharts and block diagrams in the figures illustrate examples of the architecture, function, and operation of possible embodiments of systems, methods, and devices according to various embodiments. Note that in some alternative embodiments, the functions described in the blocks may be performed in a different order than shown in the figures. For example, two blocks shown consecutively may actually be performed substantially simultaneously, or blocks may sometimes be performed in reverse order depending on the functions they relate to. Similarly, in methods consistent with various embodiments, additional steps may be included in such methods, and certain steps may be omitted or combined.

[0083] The embodiments described are not mutually exclusive, and it is understood that elements, components, materials, or steps described in relation to one exemplary embodiment may be combined with other embodiments in a suitable manner to achieve the desired design objective, or may be excluded from other embodiments.

[0084] Any reference in this specification to “some embodiments” or “some typical embodiments” means that certain features, structures, or characteristics described in relation to an embodiment may be included in at least one embodiment. Any occurrences of the phrases “one embodiment,” “some embodiments,” or “another embodiment” in various parts of this disclosure do not necessarily refer to the same embodiment, nor do they necessarily refer to separate or alternative embodiments that are mutually exclusive with each other.

[0085] Furthermore, the articles “a” and “an” used in this disclosure and the attached claims should generally be interpreted as meaning “one or more” unless otherwise specified or unless it is clear from the context that they refer to a singular form.

[0086] Unless otherwise specified, each number and range should be interpreted as an approximation, as if preceded by the word "approximately" or "about."

[0087] The elements in the claims of the following methods are listed in a specific order, if any; however, unless the enumeration of the claims specifically implies a particular order for implementing some or all of those elements, the elements are not necessarily intended to be limited to being implemented in that specific order.

[0088] For clarity, certain features of this disclosure described in the context of separate embodiments may be provided in combination in a single embodiment. Conversely, various features of this specification described in the context of a single embodiment for the sake of brevity may be provided separately, in any suitable partial combination, or as appropriate in any other described embodiment of this specification. Certain features described in the context of different embodiments are not essential features of those embodiments unless otherwise stated.

[0089] It will be further understood that various modifications, substitutions, and variations of the details, materials, and arrangement of the parts described and illustrated to illustrate the nature of the described embodiments can be made by those skilled in the art without departing from the scope of this disclosure. Accordingly, the following claims encompass all such substitutions, modifications, and variations included in the terms of the claims. Includes.

[0090] Clause 1: A method for applying configuration information for use in a node, The current steps for determining information, The steps include accessing one or more sets of criteria and configuration information corresponding to each criterion at a node, The current information is compared to one or more reference sets, A method comprising the steps of applying configuration information corresponding to at least one matching criterion for use in a node, on the condition that the current information matches at least one criterion from one or more sets of criteria. Clause 2: The method according to Clause 1, wherein the node is one of a network node, user equipment, or roadside unit. Clause 3: The method according to Clause 1, wherein one or more sets of criteria and configuration information are obtained from the node's subscriber identification module. Clause 4: The method according to Clause 1, wherein one or more sets of criteria and configuration information are obtained from a network communicating with a node. Clause 5: The method described in Clause 1, wherein the configuration information is pre-configured. Clause 6: Current information includes date and time information, The criteria include the date and time to which the configuration information should apply. The method described in Article 1. Clause 7: The method described in Clause 1, wherein current information includes the current geographical location of the node. Clause 8: The method described in Clause 1, wherein the current information includes traffic load information for radio access technologies (RATs) used by nodes to communicate with the network. Clause 9: The method described in Clause 8, wherein the node is configured to use multiple RATs, and the current information includes traffic load information for each of the multiple RATs. Clause 10: The method described in Clause 8, wherein the criteria include one or more ranges of values ​​for traffic load information, and each criterion corresponds to its respective range of values. Clause 11: The method according to Clause 1, wherein current information includes the channel busy rate measured by the node. Clause 12: The method according to Clause 11, wherein the criteria include one or more ranges of channel busy rate values, and each criterion corresponds to a range of values. Clause 13: A node for applying configuration information for use in a node, Memory configured to store instructions, A processor is included, and the processor executes instructions stored in memory. We are currently determining the information, At a node, access one or more sets of criteria and configuration information corresponding to each criterion. Compare the current information with one or more sets of criteria. A node configured to apply configuration information corresponding to at least one matching criterion for use by the node, on the condition that the current information matches at least one criterion from one or more sets of criteria. Clause 14: A node as described in Clause 13, where the node is one of a network node, user equipment, or roadside unit. Clause 15: A node as described in Clause 13, from which one or more criteria sets and configuration information are obtained from the node's subscriber identification module. Clause 16: A node as described in Clause 13, from which one or more sets of criteria and configuration information are obtained from a network communicating with the node. Clause 17: A node described in Clause 13 whose configuration information is pre-configured. Clause 18: Current information includes date and time information, The criteria include the date and time to which the configuration information should apply. The node described in Clause 13. Clause 19: The node described in Clause 13, whose current information includes the node's current geographical location. Clause 20: The node described in Clause 13, whose current information includes traffic load information for radio access technology (RAT) used by the node to communicate with the network. Clause 21: A node configured to use multiple RATs, and whose current information includes traffic load information for each of the multiple RATs, as described in Clause 20. Clause 22: A node as described in Clause 20, where the criteria include one or more ranges of values ​​for traffic load information, and each criterion corresponds to the respective range of values. Clause 23: The node described in Clause 13, whose current information includes the channel busy rate measured by the node. Clause 24: A node as described in Clause 23, where the criteria include one or more ranges of channel busy rate values, and each criterion corresponds to the respective range of values. Clause 25: A non-temporary computer-readable medium for storing instructions that can be executed by one or more processors of nodes in a communication network for performing a method, wherein the method is The current steps for determining information, The steps include accessing one or more sets of criteria and configuration information corresponding to each criterion at a node, The current information is compared to one or more reference sets, A non-temporary computer-readable medium, comprising the step of applying configuration information corresponding to at least one matching criterion for use in a node, on the condition that the current information matches at least one criterion from one or more sets of criteria.

Claims

1. A method performed by a user terminal (UE), A step of obtaining at least one set of time information and configuration information relating to wireless communication synchronization resources from a network node communicating with the UE, wherein the time information includes the time at which the configuration information becomes available. The steps include: performing synchronization using the configuration information after the current time is the time indicated in the time information; including, method.

2. The aforementioned configuration information is information for synchronizing with at least one node. The method according to claim 1.

3. The aforementioned at least one node is the target satellite. The method according to claim 2.

4. The aforementioned configuration information indicates configuration information necessary for the next communication, which is different from the configuration information currently used in the communication. The method according to claim 1.

5. moreover, If the current time is immediately after the time indicated in the time information, the use of the configuration information will begin. The method according to claim 1.

6. A user terminal (UE) comprising a control unit including at least one processor, The aforementioned processor, The UE obtains at least one set of time information and configuration information relating to wireless communication synchronization resources from a network node communicating with the UE, wherein the time information includes the time when the configuration information becomes available. The current time is after the time indicated in the time information, and the synchronization is performed using the configuration information. Configured to perform, UE.

7. The aforementioned configuration information is information for synchronizing with at least one node. The UE according to claim 6.

8. The aforementioned at least one node is the target satellite. The UE according to claim 7.

9. The aforementioned configuration information indicates configuration information necessary for the next communication, which is different from the configuration information currently used in the communication. The UE according to claim 6.

10. moreover, If the current time is immediately after the time indicated in the time information, the use of the configuration information will begin. The UE according to claim 6.

11. One or more processors cause the user terminal (UE) to execute the method A non-temporary computer-readable medium for storing executable instructions, The aforementioned method, A step of obtaining at least one set of time information and configuration information relating to wireless communication synchronization resources from a network node communicating with the UE, wherein the time information includes the time at which the configuration information becomes available. The steps include: performing synchronization using the configuration information after the current time is the time indicated in the time information; including, Non-temporary computer-readable media.

12. The aforementioned configuration information is information for synchronizing with at least one node. The non-temporary computer-readable medium according to claim 11.

13. The aforementioned at least one node is the target satellite. The non-temporary computer-readable medium according to claim 12.

14. The aforementioned configuration information indicates configuration information necessary for the next communication, which is different from the configuration information currently used in the communication. The non-temporary computer-readable medium according to claim 11.

15. A method that a network node performs, A step of providing a user terminal (UE) with at least one set of time information and configuration information relating to wireless communication synchronization resources, wherein the time information includes the time at which the configuration information becomes available. The current time is after the time indicated in the time information, so that the UE can use the configuration information to perform synchronization. method.