Patent Description:
US patent application <CIT> discloses techniques for efficiently reducing wireless communication interference caused by devices inside or outside a vehicle wherein a first router included in the first vehicle acquires power information from at least one wireless device located inside the first vehicle and from a second vehicle having a second router, determines whether interference occurs in near field wireless communication based on the power information, and requests power adjustment to either at least one wireless device or the second router such that the interference is mitigated.

Japanese patent application <CIT> discloses vehicle-to-vehicle communication systems for performing transmission and reception of information wirelessly between multiple vehicles.

The present disclosure provides a user equipment for wireless communication according to claim <NUM>, a user equipment for wireless communication according to claim <NUM>, a method of wireless communication according to claim <NUM>, and a method of wireless communication according to claim <NUM>. Specific embodiments are subject of the dependent claims.

Controller/processor <NUM> of base station <NUM>, controller/processor <NUM> of UE <NUM>, and/or any other component(s) of <FIG> may perform one or more techniques associated with inter-vehicle wireless in-vehicle network interference management, as described in more detail elsewhere herein. For example, controller/processor <NUM> of base station <NUM>, controller/processor <NUM> of UE <NUM>, and/or any other component(s) of <FIG> may perform or direct operations of, for example, process <NUM> of <FIG>, process <NUM> of <FIG>, and/or other processes as described herein. Memories <NUM> and <NUM> may store data and program codes for base station <NUM> and UE <NUM>, respectively. In some aspects, memory <NUM> and/or memory <NUM> may include a non-transitory computer-readable medium storing one or more instructions (e.g., code and/or program code) for wireless communication. For example, the one or more instructions, when executed (e.g., directly, or after compiling, converting, and/or interpreting) by one or more processors of the base station <NUM> and/or the UE <NUM>, may cause the one or more processors, the UE <NUM>, and/or the base station <NUM> to perform or direct operations of, for example, process <NUM> of <FIG>, process <NUM> of <FIG>, and/or other processes as described herein. In some aspects, executing instructions may include running the instructions, converting the instructions, compiling the instructions, and/or interpreting the instructions, among other examples.

In some aspects, UE <NUM> may include means for transmitting a wireless in-vehicle network (wIVN) capability indication that indicates that the UE is associated with a vehicle that includes a wIVN, means for receiving a response to the wIVN capability indication from another UE, means for providing configuration information to a wIVN control unit of the vehicle associated with configuring the wIVN based at least in part on the response, and/or the like. In some aspects, such means may include one or more components of UE <NUM> described in connection with <FIG>, such as controller/processor <NUM>, transmit processor <NUM>, TX MIMO processor <NUM>, MOD <NUM>, antenna <NUM>, DEMOD <NUM>, MIMO detector <NUM>, receive processor <NUM>, and/or the like.

In some aspects, UE <NUM> may include means for receiving a wireless in-vehicle network (wIVN) capability indication that indicates that another UE is associated with a vehicle that includes a wIVN, means for transmitting a response to the wIVN capability indication to the other UE, and/or the like. In some aspects, such means may include one or more components of UE <NUM> described in connection with <FIG>, such as controller/processor <NUM>, transmit processor <NUM>, TX MIMO processor <NUM>, MOD <NUM>, antenna <NUM>, DEMOD <NUM>, MIMO detector <NUM>, receive processor <NUM>, and/or the like.

<FIG> is a diagram illustrating an example <NUM> of sidelink communications, in accordance with the present disclosure.

As shown in <FIG>, a first UE <NUM>-<NUM> may communicate with a second UE <NUM>-<NUM> (and one or more other UEs <NUM>) via one or more sidelink channels <NUM>. The UEs <NUM>-<NUM> and <NUM>-<NUM> may communicate using the one or more sidelink channels <NUM> for P2P communications, D2D communications, V2X communications (e.g., which may include V2V communications, V2I communications, V2P communications, and/or the like), mesh networking, and/or the like. In some aspects, the UEs <NUM> (e.g., UE <NUM>-<NUM> and/or UE <NUM>-<NUM>) may correspond to one or more other UEs described elsewhere herein, such as UE <NUM>. In some aspects, the one or more sidelink channels <NUM> may use a PC5 interface and/or may operate in a high frequency band (e.g., the <NUM> band). Additionally, or alternatively, the UEs <NUM> may synchronize timing of transmission time intervals (TTIs) (e.g., frames, subframes, slots, symbols, and/or the like) using global navigation satellite system (GNSS) timing.

As further shown in <FIG>, the one or more sidelink channels <NUM> may include a physical sidelink control channel (PSCCH) <NUM>, a physical sidelink shared channel (PSSCH) <NUM>, and/or a physical sidelink feedback channel (PSFCH) <NUM>. The PSCCH <NUM> may be used to communicate control information, similar to a physical downlink control channel (PDCCH) and/or a physical uplink control channel (PUCCH) used for cellular communications with a base station <NUM> via an access link or an access channel. The PSSCH <NUM> may be used to communicate data, similar to a physical downlink shared channel (PDSCH) and/or a physical uplink shared channel (PUSCH) used for cellular communications with a base station <NUM> via an access link or an access channel. In some aspects, the PSCCH <NUM> may carry sidelink control information (SCI) <NUM>, which may indicate various control information used for sidelink communications, such as one or more resources (e.g., time resources, frequency resources, spatial resources, and/or the like) like a transport block (TB) <NUM> that may be carried on the PSSCH <NUM>. The TB <NUM> may include data. The PSFCH <NUM> may be used to communicate sidelink feedback <NUM>, such as hybrid automatic repeat request (HARQ) feedback (e.g., acknowledgement or negative acknowledgement (ACK/NACK) information), transmit power control (TPC), a scheduling request (SR), and/or the like.

In some aspects, the one or more sidelink channels <NUM> may use resource pools. For example, a scheduling assignment (e.g., included in SCI <NUM>) may be transmitted in subchannels using specific resource blocks (RBs) across time. In some aspects, data transmissions (e.g., on the PSSCH <NUM>) associated with a scheduling assignment may occupy adjacent RBs in the same subframe as the scheduling assignment (e.g., using frequency division multiplexing). In some aspects, a scheduling assignment and associated data transmissions are not transmitted on adjacent RBs.

In some aspects, a UE <NUM> may operate using a transmission mode where resource selection and/or scheduling is performed by the UE <NUM> (e.g., rather than a base station <NUM>). In some aspects, the UE <NUM> may perform resource selection and/or scheduling by sensing channel availability for transmissions. For example, the UE <NUM> may measure a received signal strength indicator (RSSI) parameter (e.g., a sidelink-RSSI (S-RSSI) parameter) associated with various sidelink channels, may measure a reference signal received power (RSRP) parameter (e.g., a PSSCH-RSRP parameter) associated with various sidelink channels, may measure a reference signal received quality (RSRQ) parameter (e.g., a PSSCH-RSRQ parameter) associated with various sidelink channels, and/or the like, and may select a channel for transmission of a sidelink communication based at least in part on the measurement(s).

Additionally, or alternatively, the UE <NUM> may perform resource selection and/or scheduling using SCI <NUM> received in the PSCCH <NUM>, which may indicate occupied resources, channel parameters, and/or the like. Additionally, or alternatively, the UE <NUM> may perform resource selection and/or scheduling by determining a channel busy rate (CBR) associated with various sidelink channels, which may be used for rate control (e.g., by indicating a maximum number of resource blocks that the UE <NUM> can use for a particular set of subframes).

In the transmission mode where resource selection and/or scheduling is performed by a UE <NUM>, the UE <NUM> may generate sidelink grants, and may transmit the grants in SCI <NUM>. A sidelink grant may indicate, for example, one or more parameters (e.g., transmission parameters) to be used for an upcoming sidelink transmission, such as one or more resource blocks to be used for the upcoming sidelink transmission on the PSSCH <NUM> (e.g., for TBs <NUM>), one or more subframes to be used for the upcoming sidelink transmission, a modulation and coding scheme (MCS) to be used for the upcoming sidelink transmission, and/or the like. In some aspects, a UE <NUM> may generate a sidelink grant that indicates one or more parameters for semi-persistent scheduling (SPS), such as a periodicity of a sidelink transmission. Additionally, or alternatively, the UE <NUM> may generate a sidelink grant for event-driven scheduling, such as for an on-demand sidelink message.

<FIG> is a diagram illustrating an example <NUM> of sidelink communications and access link communications, in accordance with the present disclosure.

As shown in <FIG>, a transmitter (Tx) UE <NUM> and a receiver (Rx) UE <NUM> may communicate with one another via a sidelink, as described above in connection with <FIG>. As further shown, in some sidelink modes, a base station <NUM> may communicate with the Tx UE <NUM> via a first access link. Additionally, or alternatively, in some sidelink modes, the base station <NUM> may communicate with the Rx UE <NUM> via a second access link. The Tx UE <NUM> and/or the Rx UE <NUM> may correspond to one or more UEs described elsewhere herein, such as the UE <NUM> of <FIG>. Thus, "sidelink" may refer to a direct link between UEs <NUM>, and "access link" may refer to a direct link between a base station <NUM> and a UE <NUM>. Sidelink communications may be transmitted via the sidelink, and access link communications may be transmitted via the access link. An access link communication may be either a downlink communication (from a base station <NUM> to a UE <NUM>) or an uplink communication (from a UE <NUM> to a base station <NUM>).

<FIG> is a diagram illustrating an example <NUM> of inter-vehicle wireless in-vehicle network interference, in accordance with the present disclosure. As shown in <FIG>, a number of vehicles (shown as "vehicle A <NUM>," "vehicle B <NUM>," and "vehicle C <NUM>") may travel in proximity to one another.

The vehicle A <NUM> may include a plurality of sensors <NUM> that may transmit and/or receive wireless communications via a wireless in-vehicle network (wIVN) <NUM>. The wIVN may include a wIVN control unit <NUM> that controls aspects of the operation of the wIVN <NUM>. As shown in <FIG>, the vehicle B <NUM> also may include a plurality of sensors <NUM> and a wIVN control unit <NUM> that may transmit and/or receive wireless communications via a wIVN <NUM>. The vehicle C <NUM> also may include a plurality of sensors <NUM> and a wIVN control unit <NUM> that may transmit and/or receive wireless communications via a wIVN <NUM>.

In-vehicle communications (e.g., by sensors and/or other vehicle components) on one or more of the wIVNs <NUM>, <NUM>, or <NUM> may interfere with communications on one or more of the other wIVNs <NUM>, <NUM>, or <NUM>. The interference between two or more of the wIVNs <NUM>, <NUM>, or <NUM> may be more disruptive when the associated vehicles are adjacent one another. This interference may inhibit the functioning of the wIVNs <NUM>, <NUM>, and/or <NUM> and/or sensors <NUM>, <NUM>, and/or <NUM>.

Some aspects described herein enable a UE to transmit a wIVN capability indication that indicates that the UE is associated with a vehicle that includes a wIVN, thereby alerting another UE associated with another vehicle that includes another wIVN of the presence of the wIVN. The indication and a subsequent response from the other UE may facilitate and thereby enable proactive mitigation steps to be taken by controllers of the respective wIVNs, which improves the operation of the respective wIVNs. In some aspects, a set of application layer information elements (IEs) may be used to describe a vehicle's wIVN capability, thereby enabling inter-vehicle negotiation for interference management.

<FIG> is a diagram illustrating an example <NUM> of inter-vehicle wireless in-vehicle network interference management, in accordance with the present disclosure.

As shown in <FIG>, a UE A <NUM> and a UE B <NUM> communicate with one another. The UE A <NUM> and the UE B <NUM> may communicate with one another using cellular communications, sidelink communications, and/or the like. For example, UE A <NUM> and the UE B <NUM> may communicate using one or more sidelink channels for D2D communications, which may include V2X communications (e.g., V2V communications, V2I communications, V2P communications, and/or the like), a dedicated short range communication (DSRC) network, and/or the like.

As shown by reference number <NUM>, the UE A <NUM> transmits, and the UE B <NUM> receives, a wireless in-vehicle network (wIVN) capability indication that indicates that the UE A <NUM> is associated with a vehicle <NUM> that includes a wIVN <NUM>. The UE A <NUM> may transmit the wIVN capability indication using an application layer message in a D2D communication. In some aspects, the UE A <NUM> may transmit the wIVN capability indication using an application layer message in a cellular vehicle-to-everything (C-V2X) network, a DSRC network, and/or the like.

The application layer message may be an existing type of application layer message (e.g., an application layer message already specified in a communication protocol standard). For example, the application layer message may include a basic safety message (BSM), a cooperative awareness message (CAM), and/or the like. In some aspects, the application layer message may include a new type of message (e.g., a message that is dedicated to the purpose of carrying a wIVN capability indication).

As shown in <FIG>, the wIVN capability indication may include a capability parameter <NUM>. The capability parameter <NUM> may be transmitted using an information element (IE) (shown as "DE _wIVN") that indicates whether the vehicle associated with the UE A <NUM> includes a wIVN. The term information element (IE) may be interchangeable, herein, with "data element" (DE). In some aspects, the capability parameter <NUM> may include a binary value set by a single bit. Additionally, or alternatively, the wIVN capability indication may include a preliminary set of wIVN parameters. The term "preliminary set of wIVN parameters" refers to a first set of wIVN parameters that is indicated during a negotiation between UEs. A preliminary set of wIVN parameters may include a current set of wIVN parameters (e.g., a set of wIVN parameters corresponding to a current operation of a UE), a requested set of wIVN parameters (e.g., a set of wIVN parameters that a UE requests to use for a future operation), a set of capabilities, or a combination thereof. The preliminary set of wIVN parameters may be transmitted in the capability indication using application layer IEs. In some aspects, the preliminary set of wIVN parameters may be transmitted in a message that is separate from the wIVN capability indication.

The preliminary set of wIVN parameters may include a set <NUM> of requested operating parameters for the wIVN <NUM>. The set <NUM> of requested operating parameters may indicate a requested usage for the wIVN <NUM>. In some aspects, the set <NUM> of requested operating parameters may correspond, at least in part, to a current operation of the wIVN <NUM>. For example, if the wIVN <NUM> is operating according to a set of parameters at a time when the UE A <NUM> transmits the wIVN capability indication, the set <NUM> of requested operating parameters may indicate a request to continue operating according to at least one of the same parameters. In some aspects, the set <NUM> of requested operating parameters may correspond, at least in part, to a future operation of the wIVN <NUM>. For example, the set <NUM> of requested operating parameters may indicate a request to operate according to at least one new parameter or parameters.

The set <NUM> of requested operating parameters may include frequency domain IEs, time domain IEs, signal characteristic IEs, and/or the like. In some aspects, the set <NUM> of requested operating parameters may include a requested channel start frequency for the wIVN <NUM> (shown as "DE_wIVNFreqStart"), a requested channel stop frequency for the wIVN <NUM> (shown as "DE_wIVNFreqStop"), a requested number of channels to be used for the wIVN <NUM> (shown as "DE_wIVNChannelCount"), a requested channel size to be used for the wIVN <NUM> (shown as "DE_wIVNChannelSize"), and/or the like. The set <NUM> of requested operating parameters may include a requested transmit power for the wIVN <NUM> (shown as "DE_wIVNTransmitPower"), a requested usage start time associated with the wIVN <NUM> (shown as "DF_DtimeStart"), a requested usage stop time associated with the wIVN <NUM> (shown as "DE_DtimeStop"), a requested usage duration associated with the wIVN <NUM> (shown as "DE_Duration"), and/or the like.

As shown in <FIG>, the preliminary set of wIVN parameters may include a set <NUM> of capability parameters indicating at least one operating capability of the wIVN <NUM>. The set <NUM> of capability parameters may include frequency domain IEs, time domain IEs, signal characteristic IEs, and/or the like. In some aspects, the set <NUM> of capability parameters may include an operating frequency range start frequency of the wIVN <NUM> (shown as "DE_wIVNFreqStart"), an operating frequency range stop frequency of the wIVN <NUM> (shown as "DE_wIVNFreqStop"), an operating frequency range of the wIVN <NUM> (not shown, but implicitly defined by DE_wIVNFreqStart and DE_wIVNFreqStop), an operating frequency channel width of the wIVN <NUM> (shown as "DE_wIVNChannelSize), and/or the like. In some aspects, IEs may be reused in different data fields, thereby reducing signaling overhead. For example, as shown, DE_wIVNFreqStart, DE_wIVNFreqStop, and DE_wIVNChannelSize may be used both for indicating capability parameters and requested operating parameters.

As shown by reference number <NUM>, the UE A <NUM> may transmit, and the UE B <NUM> may receive, a status message. The status message may include a location indication that indicates a current location of the UE A <NUM>. The status message may include a trajectory indication that indicates a current trajectory of the UE A <NUM>, a predicted trajectory of the UE A <NUM>, and/or the like. In some aspects, the status message may include a C-V2X status message (e.g., a BSM, a CAM, and/or the like).

In some aspects, the UE B <NUM> may determine, based at least in part on at least one of the wIVN capability indication, the location indication, the trajectory indication, or a combination thereof, whether operation of the wIVN <NUM> presents a potential conflict (e.g., due to interference) with operation of another wIVN <NUM>, where the UE B <NUM> may be associated with another vehicle <NUM> that includes the other wIVN <NUM>. For example, UE B <NUM> may determine whether operation of the wIVN <NUM> presents a potential conflict with operation of wIVN <NUM> by receiving an indication of a potential conflict (or of no potential conflict) from a wIVN control unit <NUM> corresponding to the wIVN <NUM>.

In some aspects, the UE B <NUM> may determine that operation of the wIVN <NUM> does not present a potential conflict with operation of the wIVN <NUM> due to at least one of the location indication and/or the trajectory indication. For example, the UE B <NUM> may determine, based at least in part on the location indication, that the UE A <NUM> (and, thus, the vehicle <NUM>) is not close enough to the vehicle <NUM> for the wIVN <NUM> to cause interference with the wIVN <NUM>. The UE B <NUM> may also determine that the trajectory and/or the predicted trajectory of the UE A <NUM> will not result in the UE A <NUM> being close enough to cause the interference.

In some aspects, the UE B <NUM> may determine that operation of the wIVN <NUM> does present a potential conflict with operation of the wIVN <NUM> due to the wIVN capability indication, the location indication, the trajectory indication, and/or the like. As shown by reference number <NUM>, the UE B <NUM> may provide configuration information to the wIVN control unit <NUM> associated with configuring the wIVN <NUM> based at least in part on the wIVN capability indication, the location indication, the trajectory indication, and/or the like. The UE B <NUM> may provide the configuration information to the wIVN control unit <NUM> in response to a successful negotiation, to obtain a proposed set of parameters to transmit to the UE A <NUM>, and/or the like.

As indicated above, the UE A <NUM> and UE B <NUM> may negotiate to establish mutually-compatible parameters by which the respective wIVNs <NUM> and <NUM> may operate. As shown by reference number <NUM>, the UE B <NUM> may transmit, and the UE A <NUM> may receive, a response to the wIVN capability indication. In some aspects, the UE B <NUM> may transmit the response using an application layer message in a D2D communication, over a C-V2X network, a DSRC network, and/or the like. The application layer message may be an existing type of application layer message (e.g., a BSM, a CAM, and/or the like), a new type of application layer message, and/or the like.

In some aspects, the response may indicate acceptance of the preliminary set of parameters, rejection of the preliminary set of wIVN parameters, a different set of wIVN parameters, and/or the like. For example, the response may include a wIVN parameter acceptance message from the UE B <NUM> that indicates acceptance of a set of wIVN parameters (e.g., a set of requested operating parameters for the wIVN <NUM>). In some aspects, the response may include a wIVN parameter rejection message that indicates rejection of a proposed set of wIVN parameters (e.g., a preliminary set of wIVN parameters including a set of requested operating parameters for the wIVN <NUM>). In some aspects, the response may include a proposed set of wIVN parameters.

As shown by reference number <NUM>, the UE A <NUM> provides configuration information to a wIVN control unit <NUM> of the vehicle <NUM> associated with configuring the wIVN <NUM> based at least in part on the response. The UE A <NUM> may provide the configuration information to the wIVN control unit <NUM> in response to a successful negotiation (e.g., in response to receiving a wIVN parameter acceptance message from UE B <NUM> that indicates acceptance of a set of parameters), to obtain a proposed set of parameters to transmit to the UE B <NUM>, and/or the like.

Some aspects of the inter-vehicle wIVN network interference management techniques described above may enable a UE to transmit wIVN capability information that indicates a vehicle's wIVN capability, specific operation parameters, requested operating parameters, and/or the like. In this way, aspects of the techniques described herein may facilitate inter-vehicle negotiation for interference management by allowing UEs to exchange information to determine mutually compatible wIVN parameters. In some aspects, the IEs discussed above for indicating parameters may be transmitted in existing application layer messages, thereby enabling interference management without increasing signaling overhead.

As shown in <FIG>, a UE A <NUM> and a UE B <NUM> communicate with one another. The UE A <NUM> and the UE B <NUM> may communicate with one another using cellular communications, sidelink communications, and/or the like. For example, UE A <NUM> and the UE B <NUM> may communicate using one or more sidelink channels for D2D communications, which may include V2X communications (e.g., V2V communications, V2I communications, V2P communications, and/or the like).

As shown by reference number <NUM>, the UE A <NUM> transmits, and the UE B <NUM> receives, a wIVN capability indication that indicates that the UE A <NUM> is associated with a vehicle that includes a wIVN. The UE A <NUM> may transmit the wIVN capability indication using an application layer message in a D2D communication over a C-V2X network, a DSRC network, and/or the like. The application layer message may be an existing type of application layer message (e.g., a BSM, a CAM, and/or the like), a new type of message, and/or the like.

As shown by reference number <NUM>, the UE B <NUM> transmits, and the UE A <NUM> receives, a response to the wIVN capability indication. The response may include a request for preliminary parameters. As shown by reference number <NUM>, the UE A <NUM> may transmit, and the UE B <NUM> may receive, a preliminary set of wIVN parameters. The UE A <NUM> may transmit the preliminary set of wIVN parameters in response to receiving the request for preliminary parameters. The preliminary set of wIVN parameters may include at least one of a set of requested operating parameters for the wIVN, a set of capability parameters indicating at least one operating capability of the wIVN, or a combination thereof.

As shown by reference number <NUM>, the UE B <NUM> may transmit, and the UE A <NUM> may receive, a parameter rejection message. The parameter rejection message may include a proposed set of wIVN parameters for compatible operation by the wIVN. As shown by reference number <NUM>, the UE A <NUM> may transmit, and the UE B <NUM> may receive, a wIVN parameter acceptance message to indicate acceptance of the proposed set of parameters. In some aspects, the UE A <NUM> and UE B <NUM> may exchange any number of messages, proposed sets of wIVN parameters, and/or the like, to facilitate negotiation of compatible wIVN parameters.

Some aspects of the inter-vehicle wIVN network interference management signaling described above may facilitate inter-vehicle negotiation for interference management by allowing UEs to exchange information to determine mutually compatible wIVN parameters. In some aspects, the IEs discussed above for indicating parameters may be transmitted in existing application layer messages, thereby facilitating interference management without increasing signaling overhead.

<FIG> is a diagram illustrating an example process <NUM> performed, for example, by a UE, in accordance with the present disclosure. Example process <NUM> is an example where the UE (e.g., UE <NUM> and/or the like) performs operations associated with inter-vehicle wireless in-vehicle network interference management.

As shown in <FIG>, process <NUM> includes transmitting a wIVN capability indication that indicates that the UE is associated with a vehicle that includes a wIVN (block <NUM>). For example, the UE (e.g., using transmit processor <NUM>, controller/processor <NUM>, memory <NUM>, and/or the like) may transmit a wIVN capability indication that indicates that the UE is associated with a vehicle that includes a wIVN, as described above.

As further shown in <FIG>, process <NUM> includes receiving a response to the wIVN capability indication from another UE (block <NUM>). For example, the UE (e.g., using receive processor <NUM>, controller/processor <NUM>, memory <NUM>, and/or the like) may receive a response to the wIVN capability indication from another UE, as described above.

As further shown in <FIG>, process <NUM> includes providing configuration information to a wIVN control unit of the vehicle associated with configuring the wIVN based at least in part on the response (block <NUM>). For example, the UE (e.g., using controller/processor <NUM>, memory <NUM>, and/or the like) may provide configuration information to a wIVN control unit of the vehicle associated with configuring the wIVN based at least in part on the response, as described above.

In a first aspect, the wIVN capability indication is transmitted using an application layer message in a device-to-device (D2D) communication.

In a second aspect, alone or in combination with the first aspect, the wIVN capability indication is transmitted using an application layer message in a cellular vehicle-to-everything (C-V2X) network.

In a third aspect, alone or in combination with one or more of the first and second aspects, the wIVN capability indication is transmitted in at least one of a basic safety message (BSM), a cooperative awareness message (CAM), or a combination thereof.

In a fourth aspect, alone or in combination with one or more of the first through third aspects, the wIVN capability indication includes a set of parameters that indicate a requested usage for the wIVN.

In a fifth aspect, alone or in combination with one or more of the first through fourth aspects, the response indicates acceptance of the set of parameters, rejection of the set of parameters, a different set of parameters, or a combination thereof.

In a sixth aspect, alone or in combination with one or more of the first through fifth aspects, the wIVN capability indication includes a set of parameters that indicate at least one of: an operating frequency range of the wIVN, an operating frequency range start frequency of the wIVN, an operating frequency range stop frequency of the wIVN, an operating frequency channel width of the wIVN, a requested channel start frequency for the wIVN, a requested channel stop frequency for the wIVN, a requested number of channels to be used for the wIVN, a requested channel size to be used for the wIVN, a requested transmit power for the wIVN, a requested usage start time associated with the wIVN, a requested usage stop time associated with the wIVN, a requested usage duration associated with the wIVN, or a combination thereof.

In a seventh aspect, alone or in combination with one or more of the first through sixth aspects, process <NUM> includes receiving, from the other UE, a proposed set of parameters for the wIVN; determining that the proposed set of parameters is supported by the wIVN; transmitting a wIVN parameter acceptance message to the other UE to indicate acceptance of the proposed set of parameters; and providing an indication of the proposed set of wIVN parameters to the wIVN control unit.

In an eighth aspect, alone or in combination with one or more of the first through seventh aspects, process <NUM> includes transmitting, to the other UE, a preliminary set of wIVN parameters, and the preliminary set of wIVN parameters comprises at least one of: a set of requested operating parameters for the wIVN, a set of capability parameters indicating at least one operating capability of the wIVN, or a combination thereof.

In a ninth aspect, alone or in combination with one or more of the first through eighth aspects, the wIVN capability indication includes the preliminary set of wIVN parameters.

In a tenth aspect, alone or in combination with one or more of the first through ninth aspects, the preliminary set of wIVN parameters is transmitted to the other UE based at least in part on the response, and the response includes a request for preliminary parameters.

In an eleventh aspect, alone or in combination with one or more of the first through tenth aspects, the set of requested operating parameters corresponds to a current operation of the wIVN.

In a twelfth aspect, alone or in combination with one or more of the first through eleventh aspects, process <NUM> includes receiving, in the response, an initial proposed set of wIVN parameters for compatible operation by the wIVN; determining that the initial proposed set of wIVN parameters is not supported by the wIVN; and transmitting a wIVN parameter rejection message to the other UE to indicate rejection of the initial proposed set of wIVN parameters.

In a thirteenth aspect, alone or in combination with one or more of the first through twelfth aspects, the wIVN parameter rejection message comprises an alternative proposed set of wIVN parameters.

As shown in <FIG>, process <NUM> includes receiving a wIVN capability indication that indicates that another UE is associated with a vehicle that includes a wIVN (block <NUM>). For example, the UE (e.g., using receive processor <NUM>, controller/processor <NUM>, memory <NUM>, and/or the like) may receive a wIVN capability indication that indicates that another UE is associated with a vehicle that includes a wIVN, as described above.

As further shown in <FIG>, process <NUM> includes transmitting a response to the wIVN capability indication to the other UE (block <NUM>). For example, the UE (e.g., using transmit processor <NUM>, controller/processor <NUM>, memory <NUM>, and/or the like) may transmit a response to the wIVN capability indication to the other UE, as described above.

In a first aspect, the wIVN capability indication includes a set of parameters that indicate a requested usage for the wIVN.

In a second aspect, alone or in combination with the first aspect, the response indicates acceptance of the set of parameters, rejection of the set of parameters, a different set of parameters, or a combination thereof.

In a third aspect, alone or in combination with one or more of the first and second aspects, the wIVN capability indication includes a set of parameters that indicate at least one of: an operating frequency range of the wIVN, an operating frequency range start frequency of the wIVN, an operating frequency range stop frequency of the wIVN, an operating frequency channel width of the wIVN, a requested channel start frequency for the wIVN, a requested channel stop frequency for the wIVN, a requested number of channels to be used for the wIVN, a requested channel size to be used for the wIVN, a requested transmit power for the wIVN, a requested usage start time associated with the wIVN, a requested usage stop time associated with the wIVN, a requested usage duration associated with the wIVN, or a combination thereof.

In a fourth aspect, alone or in combination with one or more of the first through third aspects, process <NUM> includes transmitting, to the other UE, a proposed set of parameters for the wIVN, wherein the UE is being associated with another vehicle that includes another wIVN; receiving a wIVN parameter acceptance message from the other UE that indicates acceptance of the proposed set of parameters; and providing configuration information to a wIVN control unit of the other vehicle associated with configuring the other wIVN based at least in part on the wIVN parameter acceptance message.

In a fifth aspect, alone or in combination with one or more of the first through fourth aspects, the process <NUM> includes receiving, from the other UE, a preliminary set of wIVN parameters, the preliminary set of wIVN parameters comprises at least one of: a set of requested operating parameters for the wIVN, a set of capability parameters indicating at least one operating capability of the wIVN, or a combination thereof.

In a sixth aspect, alone or in combination with one or more of the first through fifth aspects, the wIVN capability indication includes the preliminary set of wIVN parameters.

In a seventh aspect, alone or in combination with one or more of the first through sixth aspects, the response to the wIVN capability indication includes a request for preliminary parameters, and the preliminary set of wIVN parameters is transmitted to the UE based at least in part on the response.

In an eighth aspect, alone or in combination with one or more of the first through seventh aspects, the set of requested operating parameters corresponds to a current operation of the wIVN.

In a ninth aspect, alone or in combination with one or more of the first through eighth aspects, process <NUM> includes transmitting, in the response, an initial proposed set of wIVN parameters for compatible operation by the wIVN; and receiving a wIVN parameter rejection message from the other UE that indicates rejection of the initial proposed set of wIVN parameters by the other UE.

In a tenth aspect, alone or in combination with one or more of the first through ninth aspects, the wIVN parameter rejection message comprises an alternative proposed set of wIVN parameters.

In an eleventh aspect, alone or in combination with one or more of the first through tenth aspects, process <NUM> includes receiving, from the other UE, a location indication that indicates a current location of the other UE and a trajectory indication that indicates at least one of a current trajectory of the other UE, a predicted trajectory of the UE, or a combination thereof; determining, based at least in part on at least one of the wIVN capability indication, the location indication, the trajectory indication, or a combination thereof, that operation of the wIVN presents a potential conflict with operation of another wIVN, wherein the UE is being associated with another vehicle that includes the other wIVN; and providing configuration information to a wIVN control unit of the other vehicle associated with configuring the other wIVN based at least in part on at least one of the wIVN capability indication, the location indication, the trajectory indication, or a combination thereof.

In a twelfth aspect, alone or in combination with one or more of the first through eleventh aspects, the wIVN capability indication is transmitted using an application layer message in a D2D communication.

In a thirteenth aspect, alone or in combination with one or more of the first through twelfth aspects, the wIVN capability indication is transmitted using an application layer message on a cellular V2X network.

In a fourteenth aspect, alone or in combination with one or more of the first through thirteenth aspects, the wIVN capability indication is transmitted in at least one of a BSM, a CAM, or a combination thereof.

Claim 1:
A user equipment, UE (<NUM>; <NUM>; <NUM>, <NUM>), for wireless communication, comprising:
a memory (<NUM>); and
one or more processors (<NUM>, <NUM>, <NUM>, <NUM>) operatively coupled to the memory, the one or more processors configured to:
transmit (<NUM>; <NUM>) a wireless in-vehicle network, wIVN, capability indication (<NUM>) that indicates that the UE is associated with a vehicle (<NUM>, <NUM>, <NUM>; <NUM>) that includes a wIVN (<NUM>, <NUM>, <NUM>; <NUM>);
receive (<NUM>; <NUM>; <NUM>) a response to the wIVN capability indication from another UE; and
provide (<NUM>; <NUM>) configuration information to a wIVN control unit (<NUM>, <NUM>, <NUM>; <NUM>) of the vehicle associated with configuring the wIVN based at least in part on the response,
wherein the wIVN capability indication (<NUM>) includes a set of parameters (<NUM>, <NUM>) that indicate at least one of:
an operating frequency range of the wIVN,
an operating frequency range start frequency of the wIVN,
an operating frequency range stop frequency of the wIVN,
an operating frequency channel width of the wIVN,
a requested channel start frequency for the wIVN,
a requested channel stop frequency for the wIVN,
a requested number of channels to be used for the wIVN,
a requested channel size to be used for the wIVN,
a requested usage start time associated with the wIVN,
a requested usage stop time associated with the wIVN, or
a requested usage duration associated with the wIVN.