Method performed by wireless user equipment, wireless user equipment and system

Abstract

The present invention provides a method, wireless user equipment, and system performed by a wireless user equipment. The method performed by the wireless user equipment includes: selecting a first transmission format associated with a first Tx profile based on a transmission Tx profile for one or more data packets that were not received, wherein the one or more data packets are used for transmission between wireless user equipment, and wherein the first transmission format is configured to use a first MCS index range included in a second modulation and coding scheme MCS index range configured for a second transmission format; and transmitting the one or more data packets from the wireless user equipment to one or more wireless user equipment based on the selected first transmission format.

Description

[0001] This application is a divisional application of the Chinese patent application with the application date of July 23, 2019, application number: 201980048859.0, and invention name: "Method and device for performing wireless communication in a wireless communication system supporting vehicle communication". Technical Field

[0002] The present disclosure relates to a method and apparatus for performing wireless communication in a wireless communication system supporting vehicle communication.

[0003] Related fields

[0004] Vehicle-to-everything (V2X) communication refers to a communication scheme that exchanges or shares information such as traffic conditions while communicating with road infrastructure and other vehicles during driving. V2X communication can include vehicle-to-vehicle (V2V) communication, which refers to communication based on Long Term Evolution (LTE), vehicle-to-pedestrian (V2P) communication, which refers to communication based on LTE between a vehicle and a terminal that can be carried by an individual user, and vehicle-to-infrastructure / network (V2I / N), which refers to communication based on LTE between a vehicle and a roadside unit / network. Here, a roadside unit (RSU) can be a transportation infrastructure entity implemented by a base station or a fixed terminal. For example, an RSU can be an independent entity that sends speed notifications to a vehicle.

[0005] Detailed description

[0006] Technical issues

[0007] One aspect of the present disclosure provides one or more methods and apparatuses that address issues such as unsuccessful reception of one or more packets by a V2X terminal in a wireless communication system supporting vehicular communications.

[0008] One aspect of the present disclosure provides one or more methods and apparatuses for transmitting and receiving one or more packets between terminals supporting different versions of a wireless communication system supporting vehicular communication.

[0009] Technical Solution

[0010] According to one aspect of the present disclosure, a method for performing wireless communication by a terminal in a wireless communication system is provided. The method may include generating a first message and transmitting the generated first message. A transmission format for transmitting the first message may be determined based on whether transmission (Tx) profile information is transmitted from a higher layer of the terminal.

[0011] Beneficial effects

[0012] According to one aspect of the present invention, one or more methods and apparatuses may address an issue such as unsuccessful reception of one or more packets by a V2X terminal in a wireless communication system supporting vehicular communications.

[0013] According to an aspect of the present disclosure, one or more methods and apparatuses may be provided so that one or more packets may be transmitted and received between terminals supporting different versions of a wireless communication system supporting vehicular communication.

[0014] The various advantageous effects of one or more features of the present disclosure are not limited to the above-mentioned effects, and given the one or more features of the present disclosure described below, a person of ordinary skill in the art will easily understand other various advantageous effects not explicitly discussed in the present disclosure. BRIEF DESCRIPTION OF THE DRAWINGS

[0015] Figure 1 An example of a wireless communication system according to an exemplary embodiment is shown.

[0016] Figure 2 An example of a link considered in Vehicle-to-Everything (V2X) is shown according to an example embodiment.

[0017] Figure 3 Another example of a link considered in V2X according to an example embodiment is shown.

[0018] Figure 4a An example is shown in which a base station transmits signals to a plurality of vehicles according to an example embodiment.

[0019] Figure 4b An example is shown in which a UE transmits a sidelink signal to a plurality of vehicles according to an example embodiment.

[0020] Figure 5 An example of a device-to-device (D2D) communication scenario according to an example embodiment is shown.

[0021] Figure 6 Another example of a D2D communication scenario according to an example embodiment is shown.

[0022] Figure 7 An example of an overall configuration of V2X communication according to an example embodiment is shown.

[0023] Figure 8 An example is shown in which the type of communication protocol supported by a user equipment (UE) and the type of application supported by the UE are different according to an exemplary embodiment.

[0024] Figure 9 is a flow chart illustrating an example of UE operation according to an example embodiment.

[0025] Figure 10 is a block diagram illustrating an example of a configuration of a UE device according to an exemplary embodiment. DETAILED DESCRIPTION

[0026] Hereinafter, the embodiments of the present disclosure will be described in detail so that those skilled in the art can easily perform the embodiments with reference to the accompanying drawings. However, the present disclosure can be implemented in many different forms and is not limited to the embodiments described herein.

[0027] In the following description of the embodiments of the present disclosure, when known functions and configurations incorporated herein may make the subject matter of the present disclosure unclear, their detailed description will be omitted. Parts of the drawings that are not related to the description of the present disclosure are omitted, and similar parts are represented by similar reference numerals.

[0028] In the present disclosure, when an element is referred to as being "connected," "coupled," or "connected" to another element, it should be understood that it includes not only a direct connection relationship but also an indirect connection relationship. In addition, when an element is referred to as "including" or "having" another element, it means not only excluding the other element but also including the other element.

[0029] In this disclosure, the terms first, second, etc. are used only to distinguish one element from another and do not limit the order or importance of the elements unless otherwise specified. Therefore, within the scope of this disclosure, a first component in one embodiment may be referred to as a second component in another embodiment, and similarly, a second component in one embodiment may be referred to as a second component in another embodiment.

[0030] In this disclosure, components that are distinguished from each other are intended to clearly illustrate each feature and do not necessarily mean that the components are separate. That is, multiple components can be integrated into one hardware or software unit, or a single component can be distributed across multiple hardware or software units. Therefore, unless otherwise specified, these integrated or distributed embodiments are also included in the scope of this disclosure.

[0031] In the present disclosure, the components described in the various embodiments do not necessarily mean essential components, but some may be optional components. Therefore, embodiments consisting of a subset of the components described in the embodiments are also included in the scope of the present disclosure. In addition, embodiments that include other components in addition to the components described in the various embodiments are also included in the scope of the present disclosure.

[0032] In addition, the description described herein relates to a wireless communication network, and the operations performed in the wireless communication network can be performed in a process in which a system (e.g., a base station) that controls the wireless network controls the network and sends data, or can be performed in a user device connected to the wireless communication network.

[0033] Obviously, in a network including a base station and multiple network nodes, various operations performed for communicating with a terminal may be performed by the base station or other network nodes other than the base station. Here, the term "base station (BS)" may be used interchangeably with other terms, such as a fixed station, Node B, eNode B (eNB), gNode B (gNB), and access point (AP). In addition, the term "terminal" may be used interchangeably with other terms, such as user equipment (UE), mobile station (MS), mobile subscriber station (MSS), subscriber station (SS), and non-AP station (non-AP STA).

[0034] Here, sending or receiving a channel includes the meaning of sending or receiving information or signals through the corresponding channel. For example, sending a control channel means sending control information or signals through the control channel. Similarly, sending a data channel means sending data information or signals through the data channel.

[0035] Figure 1 is a diagram illustrating a wireless communication system to which the present disclosure is applied.

[0036] Figure 1 The network structure shown in the figure may be a network structure of an Evolved Universal Mobile Telecommunications System (E-UMTS). E-UMTS may include a Long Term Evolution (LTE) system, an LTE-A system, etc., or may include a 5G mobile communication network, a New Radio (NR), etc.

[0037] Reference Figure 1 In a wireless communication system 10, a base station (BS) 11 and a user equipment (UE) 12 can wirelessly transmit and receive data. Furthermore, the wireless communication system 10 can support device-to-device (D2D) communication between UEs. Hereinafter, UEs include terminal devices used by general users, such as smartphones, as well as terminal devices installed in vehicles. D2D communication in the wireless communication system will be described later.

[0038] BS 11 in wireless communication system 10 can provide communication services to UEs located within the coverage area of ​​BS 11 via a predetermined frequency band. The coverage area in which the BS provides services is also called a site. The site may include various areas 15a, 15b, and 15c, which may be referred to as sectors. The sectors included in the site may be identified by different identifiers. Each sector 15a, 15b, and 15c may be interpreted as a portion of the area covered by BS 11.

[0039] BS 11 may generally refer to a station that communicates with UE 12 and may be referred to as an evolved Node B (eNode B), a base transceiver system (BTS), an access point, a femto eNode B, a home eNode B (HeNode B), a repeater, a remote radio head (RRH), etc.

[0040] UE 12 may be a fixed or mobile entity and may be referred to as a mobile station (MS), mobile terminal (MT), user terminal (UT), subscriber station (SS), wireless device, personal digital assistant (PDA), wireless modem, handheld device, etc.

[0041] In addition, based on the size of the coverage provided by the corresponding BS, the BS 11 may be referred to as a "megacell," "macrocell," "microcell," "picocell," "femtocell," etc. Cell may be used as a term indicating a frequency band provided by a BS, coverage of a BS, or a BS.

[0042] Hereinafter, downlink (DL) indicates communication or a communication path from BS 11 to UE 12, and uplink (UL) indicates communication or a communication path from UE 12 to BS 11. In the downlink, the transmitter may be part of BS 11 and the receiver may be part of UE 12, and in the uplink, the transmitter may be part of UE 12 and the receiver may be part of BS 11.

[0043] The multiple access scheme applied to the wireless communication system 10 is not limited to a specific scheme. For example, the wireless communication system can use various multiple access schemes such as code division multiple access (CDMA), time division multiple access (TDMA), frequency division multiple access (FDMA), orthogonal frequency division multiple access (OFDMA), single carrier-FDMA (SC-FDMA), OFDM-FDMA, OFDM-TDMA, OFDM-CDMA, etc. Uplink transmission and downlink transmission can be performed based on a time division duplex (TDD) scheme in which transmission is performed at different times, or based on a frequency division duplex (FDD) scheme in which transmission is performed at different frequencies.

[0044] The acronyms used in this specification are defined below in Tables 1 and 2. For example, V2X represents V2V, V2P, and V2I / N, and is associated with wireless communications such as LTE and LTE-A. Each acronym may cover the following features.

[0045] Table 1

[0046]

[0047] Table 2

[0048]

[0049] V2X Downlink (DL), Uplink (UL) and Sidelink (SL)

[0050] Figure 2 、 Figure 3and FIG. 4 show examples of downlink, uplink, and sidelink in vehicle-to-everything (V2X).

[0051] For details, refer to Figure 2 , a V2X-enabled communication system may only support PC5 links, which are links between UEs and are defined in device-to-device (D2D) (proximity-based service (ProSe)).

[0052] The PC5 link refers to an interface defined between UEs and may be defined as a side link (SL) in the radio access layer. The side link refers to a link in the radio access layer for direct communication between vehicles for vehicle communication; however, it is not limited thereto.

[0053] Figure 3 Another example of a link considered in V2X is shown.

[0054] refer to Figure 3 , a communication system supporting V2X may only support a Uu link, which is a link between a base station (e.g., an eNodeB) and a UE or a link between a radio access network (e.g., an Evolved Universal Terrestrial Access Network (E-UTRAN)) and a UE. The Uu link may include an uplink (UL) and a downlink (DL), where the UL is a path through which the UE sends a signal to the base station, and the DL is a path through which the base station sends a signal to the UE.

[0055] Figure 4a and 4b Another example of a link considered in V2X is shown.

[0056] refer to Figure 4a and 4b , all the aforementioned PC5 links and Uu links can be considered, including road side units (RSU) in the form of UE. Figure 4a An example is shown in which a base station (e.g., an eNB and a gNB) transmits a signal to a plurality of vehicles. Figure 4b An example is shown in which a UE (RSU) transmits a side link (SL) signal to a plurality of vehicles.

[0057] D2D communication refers to technologies that enable direct data transmission and reception between UEs. Hereinafter, it is assumed that the UE supports D2D communication. Furthermore, D2D communication can be interchangeably referred to as Proximity-Based Services (ProSe) or ProSe-D2D communication. The term "ProSe" for D2D communication indicates that proximity-based services can be added, without changing the aforementioned meaning of direct data transmission and reception between UEs.

[0058] D2D communication can be classified into a discovery process for communication between in-coverage UEs or out-of-coverage UEs and a direct communication process for sending and receiving control data and / or business data between UEs, where an in-coverage UE is a UE located within the coverage of the network, and an out-of-coverage UE is a UE located outside the coverage of the network. In the following, a UE that sends a signal based on D2D communication is referred to as a transmitting UE (Tx UE), and a UE that receives a signal based on D2D communication is referred to as a receiving UE (RxUE). A Tx UE can send a discovery signal, and an Rx UE can receive a discovery signal. The roles of a Tx UE and an Rx UE can be switched. A signal sent from a Tx UE can be received at two or more Rx UEs.

[0059] D2D communication can be used for various purposes. For example, it can be used for public safety, transportation network services, ultra-low latency services, and commercial services within the network coverage of commercial frequencies. However, in the case of frequencies dedicated to transportation networks, D2D communication using those frequencies can be used only for transportation network communications and traffic safety, regardless of network coverage.

[0060] When UEs within close proximity perform D2D communication in a cellular system, the load on the base station's radio resources can be distributed. Furthermore, when UEs in close proximity perform D2D communication, they can transmit data at a relatively short distance, reducing the UE's transmit power and transmission delay. Furthermore, from the perspective of the entire system, existing cellular-based communications and D2D communications use the same resources. Therefore, frequency resource efficiency can be improved unless UEs spatially overlap.

[0061] D2D communication scenarios

[0062] D2D communication can be classified into communication between in-coverage UEs existing in the network coverage, such as the coverage of a base station, communication between out-of-coverage UEs located outside the network coverage, and communication between in-coverage UEs and out-of-coverage UEs.

[0063] Figure 5 An example of a D2D communication scenario according to an example embodiment is shown.

[0064] exist Figure 5In the embodiment, it is assumed that the first UE (V2X UE 1) and the second UE (V2X UE 2) are located in the network coverage and are therefore able to communicate with the base station. The first UE and the second UE may send and receive data for vehicle communication services through the base station (Uu interface). That is, the first UE and the second UE may send and / or receive data for each other's vehicle communication services through UL data transmission and DL data reception. Here, when it is assumed that the third UE (V2X UE 3) and the fourth UE (V2X UE 4) are located outside the network coverage and exist in a position where D2D communication with the first UE and the second UE is not possible, the third UE and the fourth UE may not exchange data for vehicle communication services with the first UE and the second UE. The UE may not communicate with another UE, base station, server, etc. that exist in an area where the signal cannot physically reach.

[0065] However, when the fourth UE located outside the network coverage needs to connect to the network due to vehicle communication services or commercial services and is able to perform D2D communication with the UE-type RSU present in the coverage of the network service through D2D communication, the UE-type RSU can be used as a relay, and the fourth UE located outside the network coverage can send data to and receive data from the base station through an indirect path. That is, since the UE-type RSU performs the relay function, the fourth UE sends vehicle communication service data to the UE-type RSU through the side link (SL), and the UE-type RSU sends vehicle communication service data to the base station through the uplink (UL) of the Uu interface. The vehicle communication service data of the fourth UE is received at / by a UE within the coverage including the first UE and the second UE through the downlink (DL) of the Uu interface.

[0066] UEs located outside the network service coverage, including a fourth UE, and capable of performing D2D communication with the UE-type RSU, can transmit the vehicle communication service data of the fourth UE to UEs located within the network service coverage through the UE-type RSU.

[0067] Figure 6 Another example of a D2D communication scenario according to an example embodiment is shown.

[0068] Reference Figure 6, vehicle communication service data transmitted from a fourth UE (V2X UE4) to a UE-type RSU needs to be transmitted directly to a UE located outside the coverage area of ​​the network service, where D2D communication with the fourth UE is not possible (but D2D communication with the UE-type RSU is possible). Since V2X services are susceptible to latency, it is necessary to reduce the latency incurred when initially transmitting data to the base station and then to the UE-type RSU. Therefore, the UE-type RSU needs to prepare to transmit data received from the fourth UE to the base station via the Uu (LTE uplink) interface, as well as to prepare to transmit data via the sidelink (SL). Therefore, when the UE-type RSU operates in a mode in which SL resources are controlled by the base station, the vehicle communication service data received from the fourth UE needs to be treated as data to be included in the LTE-side buffer status report (BSR) and, at the same time, as data to be included in the SLBSR. That is, when the vehicle communication service data received from the fourth UE is transmitted to the packet data convergence protocol (PDCP) / radio link control (RLC) layer in the LTE-side radio bearer (RB), the same information needs to be transmitted to the PDCP / RLC layer in the SL-side RB.

[0069] Here, in the case of proximity-based service per-packet priority (PPPP) for data sent to the SL-side RB, the priority of the received packet is maintained as is. If there is no SL-side RB mapped to the priority of the received packet, the UE-type RSU itself configures a new RB supporting the priority and sends the packet.

[0070] V2X resource control method

[0071] Hereinafter, a resource control method of V2X according to an exemplary embodiment is described.

[0072] Here, it is assumed that each time a cell of the corresponding carrier is detected based on a specific standard, the UE is present in the reception coverage of the carrier used for V2X sidelink communication. When the UE applied for V2X sidelink communication is present in the coverage of the frequency used for V2X sidelink communication, or when the base station provides a V2X sidelink configuration at the frequency (including the case where the UE is out of coverage at the frequency), the UE uses resource allocation scheduled based on the base station configuration or UE autonomous resource selection. When the UE is out of coverage of the frequency used for V2X sidelink communication and the base station does not provide a V2X sidelink configuration corresponding to the frequency, the UE may use a set of Tx and Rx resource pools pre-configured for the UE. Here, the UE using scheduled resource allocation may be defined as mode 3, and the UE using UE autonomous resource selection may be defined as mode 4.

[0073] Mode 3 (Base Station Resource Control Method)

[0074] Mode 3 refers to the base station's D2D resource control method. A UE can request Tx resources from the base station to transmit data. In response to the request, the base station schedules Tx resources and provides the scheduled Tx resources to the UE. The UE can use the scheduled Tx resources to perform V2X sidelink transmissions. The transmission format can be determined differently based on the supported version, as described below. (In the case of Rel-14 UEs, the transmission format is determined based on base station scheduling information; in the case of Rel-15 UEs, the UE itself determines the transmission format based on the V2X service type.)

[0075] In mode 3, the base station sends V2X-specific configuration information as shown in Table 3 to the UE. To this end, a signaling procedure in the radio resource control (RRC) layer, such as an RRC connection reconfiguration message, may be used.

[0076] Table 3

[0077]

[0078]

[0079]

[0080] Mode 4 (UE resource control method)

[0081] Mode 4 refers to a D2D resource control method performed by a UE. Detailed configuration information about a Tx resource pool for Mode 4 may be configured to be the same as detailed configuration information about a Tx resource pool for Mode 3.

[0082] Here, in Mode 4, multiple pieces of Tx resource pool information can be provided in a list format (SL-CommTxPoolListV2X). If necessary, the base station can configure a new Tx resource pool operable in Mode 4, or can send an RRC connection reconfiguration message to release a portion of the pre-configured Tx resource pool. In addition, the UE can autonomously select a portion of the resources included in the Tx resource pool to be used for actual V2X data transmission, and the base station can send reference parameter information to the UE, which is the standard for this selection.

[0083] For example, in mode 4, the base station may provide the UE with information as shown in Table 3 through an RRC connection reconfiguration message, which is similar to that in mode 3.

[0084] As another example, in mode 4, a UE in RRC idle mode may receive a system information block including information associated with a vehicle communication service (referred to as V2X service-related system information) from a base station, and the UE may configure a Tx resource pool based on the information by itself.

[0085] For example, the V2X service-related system information block may be SIB21 in Table 2 and SIB22 in Table 3.

[0086] SIB21 of Table 4 may include various configuration information regarding V2X sidelink communication (hereinafter referred to as V2X common configuration information (V2X-ConfigCommon)). Additional information not included in SIB21 may be configured in SIB22 of Table 5.

[0087] For example, SIB21 and SIB22 may include the same carrier information, or may include different carrier information. If SIB21 and SIB22 include the same carrier information, carrier configuration information not included in SIB21 may be included in SIB22. That is, only incremental information may be included in SIB22. If SIB21 and SIB22 include different carrier configuration information, different carrier configuration information may be included in each SIB.

[0088] Table 4

[0089]

[0090] -anchorCarrierFreqList: describes the carrier frequencies including the inter-carrier resource configuration for V2X sidelink communication.

[0091] -cbr-CommonTxConfigList: describes a common list of channel busy rate (CBR) ranges and a physical sidelink shared channel (PSSCH) transmission parameter configuration list, which enables configuration of UE congestion control for V2X sidelink communications.

[0092] -offsetDFN: describes the timing offset used by the UE to determine the Direct Frame Number (DFN) timing when the PCell-based timing uses the Global Navigation Satellite System (GNSS).

[0093] -p2x-CommTxPoolNormalCommon: Describes a resource that enables the UE to transmit P2X-related V2X sidelink communications. No area ID is configured in the pool of this field.

[0094] -ThresSL-TxPriorification: describes the threshold used to determine packet priority when SL V2X transmissions overlap in time with uplink transmissions. This value overrides the three SL-Tx priorities configured in the SL-V2X pre-configuration.

[0095] -TypeTxSync: describes the priority synchronization type (i.e., eNB or GNSS) used to perform V2X sidelink communications on the broadcasted carrier frequency.

[0096] -v2x-CommRxPool: describes the resources allowed to receive V2X sidelink communications when the UE is in RRC_IDLE and RRC_CONNECTED modes.

[0097] -v2x-CommTxPoolException: describes a resource that enables the UE to send V2X sidelink communications under abnormal conditions.

[0098] -v2x-CommTxPoolNormalCommon: Describes a resource that is capable of sending P2X-related V2X sidelink communications when the UE is in RRC_IDLE or RRC_CONNECTED mode and is used when sending V2X sidelink communications on frequencies other than the primary frequency. E-UTRAN configures a single resource pool for each area.

[0099] -v2x-InterFreqInfoList: describes the adjacent frequency synchronization and resource allocation configuration for V2X sidelink communication.

[0100] -v2x-ResourceSelectionConfig: describes a V2X sidelink communication resource for UE to select resources independently.

[0101] -v2x-SyncConfig: Describes the configuration that allows the UE to receive and transmit synchronization information for V2X sidelink communication. The E-UTRAN configures the v2x SyncConfig including transmission parameters when configuring the UE to transmit synchronization information.

[0102] -zoneConfig: describes the zone configuration used for V2X sidelink communication.

[0103] Table 5

[0104]

[0105] -cbr-pssch-TxConfigList: describes the mapping between PPP, CBR range, and PSSCH transmission parameters and CR restrictions, using entry indexes of cbr-RangeCommonConfigList included in SIB21 and entry indexes of sl-CBR-PSSCH-TxConfigList included in SIB21. The configuration of this field applies to all resource pools of all carriers used for V2X sidelink communication transmission included in SIB22.

[0106] -slss-TxMultiFreq: Describes whether the UE can transmit SLSS in multiple carriers for V2X sidelink communication. If this field is empty, the UE can only transmit SLSS in the synchronized carrier.

[0107] -SyncFreqList: describes the list of candidate carriers for V2X sidelink communication synchronization.

[0108] -v2x-FreqSelectionConfigList: describes the configuration information about carrier selection for V2X sidelink communication transmission.

[0109] -v2x-PacketDuplicationConfig: describes the configuration information about the sidelink packet duplication of V2X sidelink communication.

[0110] -v2x-InterFreqInfoList: If this field includes carriers included in SIB21 and part of the configuration of the corresponding carrier is already included in SIB21, this field does not include the configuration corresponding to the corresponding carrier.

[0111] If the reference parameter information cannot be received from the base station, such as when the base station does not provide the reference parameter information or when the UE is in RRC idle mode or out of network coverage, the UE may perform resource selection within the Tx resource pool based on parameter information stored in internal memory. This V2X preconfiguration information is represented by Table 6 (SL-V2X-Preconfiguration Information Element).

[0112] Table 6

[0113]

[0114]

[0115]

[0116]

[0117] Information signaling to SIB21 and SIB22 may be included in pre-configuration information.

[0118] In addition, the reference parameter information or the parameter information stored in the UE may include information on a reference value of the reference signal received power (RSRP) of the PSSCH required for selecting resources in the Tx resource pool. Here, RSRP may correspond to the energy level of the signal in the V2X system.

[0119] In addition, Tx profile information that determines the sidelink transmission format may be included. Tx profile information is further described below.

[0120] -v2x-TxProfileList: Describes the transport format used as a Tx profile pointer index in each Tx profile. For each entry, the value REL14 indicates that the UE can use a Release 14 compatible format to send V2X packets. The value REL15 indicates that the UE can use a Release 15 format to send V2X packets.

[0121] Based on SIB21, SIB22 or pre-configured information, a Mode 4 UE may select resources by itself as described below.

[0122] Initially, the concept of region is used for UE to select resources by itself. The region can be configured by the base station or can be preconfigured. When configuring or preconfiguring the region, the geographical area of ​​the earth is divided into geographical regions using a single fixed reference point (i.e., geographic coordinates (0, 0)), length, and width. Each divided area can be defined as a region. The UE uses the length and width of each region, the number of regions, a single fixed reference point, and the geographic coordinates of the UE's current location to determine the region ID. Regions can exist within and outside the network coverage. If the UE is within the network coverage, the length and width of each region and the number of regions can be provided to the UE from the base station. If the UE is outside the network coverage, the UE can use the preconfigured region information.

[0123] Based on the mapping relationship between Tx resources and areas, the UE can select a V2X sidelink resource pool for the area in which the UE is located. The UE can select sidelink resources by performing sensing based on the selected resource pool. Here, sensing refers to the resource selection mechanism, in which the UE selects or reselects certain specific sidelink resources based on the sensing results and reserves Tx resources. A maximum of two Tx resource reservation processes are allowed for the UE, and here, the Tx resource reservation processes are performed in parallel. However, the UE can only perform a single resource selection for V2X sidelink transmission.

[0124] In the case of Mode 3 UE and Mode 4 UE, the method of determining the sidelink transmission format may be different based on the UE version, which will be described below. Hereinafter, the UE version is described, and the method of determining the sidelink transmission format based on the UE version is described.

[0125] First type UE, second type UE

[0126] Currently, a V2X UE may be either a Type 1 UE or a Type 2 UE. For example, a Type 1 UE may be a V2X UE that supports the Release 14 specification. Furthermore, a Type 2 UE may be a V2X UE that supports the Release 15 specification. However, this is provided as an example only. Compared to a Release 14 V2X UE, a Release 15 V2X UE may have the following features.

[0127] -Carrier aggregation (CA) support

[0128] When a V2X UE supporting sidelink i) verifies that at least two carriers or serving cells (i.e., carriers or serving cells that can provide V2X services and provide at least one piece of Tx resource pool information or Rx resource pool information through SIB) can be used as sidelinks, and ii) is capable of simultaneously transmitting and receiving data through the verified carriers or serving cells, the corresponding V2X UE can be described as supporting sidelink CA.

[0129] Alternatively, when a V2X UE supporting sidelink verifies that i) at least two serving cells can be used as a sidelink, and ii) each serving cell provides available V2X carrier configuration information, and iii) data can be simultaneously transmitted and received through the verified serving cells, the corresponding V2X UE can be described as supporting sidelink CA.

[0130] Sidelink CA can be supported by all in-coverage V2X UEs and out-of-coverage V2X UEs. In the case of carrier selection, the UE can select multiple carriers based on the CBR value and PPPP value of the V2X message to be sent.

[0131] A UE supporting sidelink CA can perform packet replication, sending duplicate packets over different carriers. Here, the proximity-based per-packet reliability (PPPR) of each V2X packet can be used as a reference for activating / deactivating packet replication. PPPR can indicate the reliability of a V2X packet. That is, the UE can verify the required reliability of a packet based on the PPPR value. In the case of a packet requiring high reliability, the UE can perform packet replication and send the packet using a different carrier. In this way, the reliability requirements of the packet can be met.

[0132] - New transmission format support

[0133] The new transmission format can be used to support evolving V2X services such as platooning (9) and remote driving. The second type of V2X UE can support the maximum data transmission rate and can use a high level of modulation and coding scheme (MCS) to enhance V2X performance.

[0134] Compared to the first type of V2X UE, the second type of V2X UE may also support new transmission formats. However, considering V2X services that are directly related to driver safety, such as preventing collisions between vehicles and notifying risk factors of driving paths, all UEs need to receive messages for safety-related services, regardless of UE version / type.

[0135] However, if the second-type V2X UE applies a new transmission format, the first-type V2X UE may not receive the corresponding message. Here, the new transmission format may be a new MCS range available for the second-type UE. That is, the first-type UE may support MCS indices from 0 to 28, and the second-type UE may support MCS indices from 0 to 31. Therefore, compared to the first-type UE, the second-type UE may support a new MCS range from 29 to 31. That is, since the first-type UE does not support MCS indices from 29 to 31, the first-type UE may not receive messages sent using an MCS corresponding to any of the unsupported MCS indices. Therefore, UEs supporting different types or versions may not coexist. To address this issue, a Tx profile may be used. The following describes the Tx profile and a method for determining a transmission format using the Tx profile.

[0136] -Transmission format determination method for the second type of UE (Tx profile):

[0137] The Tx profile can be used to ensure compatibility between first-type UEs and second-type UEs using different transmission formats. For example, a UE can determine the transmission format of a V2X message based on the index value indicated by the Tx profile. The Tx profile can be applied to each V2X message transmitted over the PC5 interface. The application layer can determine the Tx profile index value based on the priority of each V2X message.

[0138] For example, in the case of safety-related V2X messages, all UEs may need to receive V2X messages, regardless of UE type or release version. Therefore, the application layer may need to configure a Tx profile for a first type so that the UE can apply the first type of transmission format. For example, the first type may indicate Release 14, while the second type may indicate Release 15. However, this is provided merely as an example.

[0139] In the case of V2X messages related to services applied between UEs of previous versions, such as V2X messages related to platooning and remote driving, Type 1 UEs do not need to receive these messages. Therefore, Type 2 V2X UEs can support the maximum data transmission rate and use the new transmission format to enhance V2X performance. In this case, the UE's application layer can configure the Tx profile so that the UE can apply the Type 2 transmission format.

[0140] Here, the Tx profile may indicate the first type transmission format or the second type transmission format using an index value. Tx profile 1 may indicate the first type transmission format, and Tx profile 2 may indicate the second type transmission format.

[0141] That is, if Tx Profile 1 is provided for each V2X message that the UE desires to transmit, the UE may set a single MCS value using the first type MCS table and may apply the set MCS value for transmission. If Tx Profile 2 is provided, the UE may set a single MCS value using the second type MCS table and may transmit the corresponding V2X message by applying rate matching and a transport block size (TBS) scaling function. Here, selecting a single MCS value from among the values ​​included in the MCS table may be subject to UE implementation.

[0142] The first type MCS table may be provided as shown in Table 6 below. The MCS for the first type may have an MCS range corresponding to indexes 0 to 31. The minimum and maximum values ​​of the MCS range may be set by RRC signaling or pre-configuration information. Here, minimum MCS-PSSCH and maximum MCS-PSSCH parameters may be enabled. The UE may select a single MCS index based on UE implementation from the MCS range defined based on such parameters. However, if the base station instructs the first type UE to use a specific MCS index through an SL grant, the UE may apply a transport format corresponding to the specific MCS index.

[0143] The first type UE may determine the modulation scheme and TBS size based on the selected MCS index. m ) determines the modulation scheme and can be based on the parameter I representing the allocated resource block TBS and N PRB To determine the TBS size.

[0144] Table 7

[0145]

[0146] The second type MCS table may be provided as shown in Table 8 below. The MCS for the second type may have an MCS range corresponding to indexes 0 to 31. The minimum and maximum values ​​of the MCS range may be set by RRC signaling or pre-configuration information. Here, minimum MCS-PSSCH and maximum MCS-PSSCH parameters may be used. The UE may select a single MCS index based on UE implementation from the MCS range defined based on such parameters. In the same manner as the first type transport format selection method, the UE may determine the modulation scheme and TBS size based on the selected MCS index. The MCS may be selected based on Q′=min(4, Q′ m ) determines the modulation scheme and can be based on the parameter I representing the allocated resource block TBS and N PRB To determine the TBS size.

[0147] Table 8

[0148]

[0149] However, if multiple V2X messages are multiplexed into a single MAC PDU, the transmission format for MAC PDU transmission may be determined based on the Tx profile of the V2X message with the highest priority.

[0150] That is, in the case where the V2X message is always transmitted through the PC5 interface, the UE can determine the transmission format based on the Tx profile and then transmit the V2X message.

[0151] -Transmission format determination method for first type UE

[0152] A Type-1 V2X UE may only apply a single transmission format for the Type-1 service. For example, if the base station instructs the UE to apply a specific MCS value, the UE may determine the transmission format based on the specific MCS value. If the base station does not instruct the UE to apply a specific MCS value, the UE may select and apply a single MCS value from among the values ​​within the Type-1 MCS range based on UE implementation.

[0153] Hereinafter, the entire UE operation based on the application layer setting the Tx profile is described.

[0154] -V2X UE operation method

[0155] Figure 7 An example of an overall configuration of V2X communication according to an example embodiment is shown.

[0156] refer to Figure 7, V2X UEs can be configured with V2X applications and communication protocol stacks. Communication between UEs can be performed over PC5 links, and communication between UEs and base stations can be performed over Uu links. Communication between V2X applications can be performed over V5 links.

[0157] When a UE wishes to transmit a V2X message via the PC5 interface, it may determine the transmission method based on the settings of the application layer. The application layer may set the PPPP and Tx profile and / or Tx profile value for the generated V2X message and may send it to the access stratum (AS) layer.

[0158] For example, when a V2X message generated by a UE application is a safety-related message, the application layer may set Tx Profile 1 so that all UEs can receive the corresponding V2X message. Furthermore, the application layer may set the PPPP, which indicates the message priority of each V2X message, and may optionally set the PPPR, which indicates the message reliability. The UE application layer may transmit the V2X message, Tx Profile, and PPPP to the AS layer, and may optionally transmit the PPPR to the AS layer.

[0159] In response to receiving the Tx profile, PPPP, PPPR, and V2X message, the AS layer can verify the priority and reliability of the V2X message and map the V2X message to be transmitted to the appropriate sidelink radio bearer (SLRB). The PDCP, RLC, MAC, and PHY layers of the UE can receive the V2X message through the AS layer, prepare to send the V2X message, and then perform transmission.

[0160] The PDCP layer of the UE may compress the IP header and perform encryption. Next, the PDCP layer of the UE may send the corresponding packet to the RLC layer. The RLC layer of the UE may receive the packet and perform segmentation / concatenation of the packet.

[0161] In addition, the UE may select a logical channel for transmitting the V2X message based on the PPPP of the V2X message, and may select a carrier for transmitting the V2X message based on the PPPP and CBR value. Here, the carrier refers to a frequency band.

[0162] In addition, the UE determines the activation or deactivation of the sidelink packet replication based on the PPPR of the V2X message. Here, PPPR can be provided selectively.

[0163] In addition, the UE may determine the transmission format based on the Tx profile of the V2X message.

[0164] However, here, PPPR and Tx profile may only apply to second-type V2X UEs, and the application layer supporting first-type UEs may not set this value. Furthermore, PPPR may be used only for packet duplication. Therefore, even an application layer supporting second-type UEs may not set a PPPR value for packets that do not require packet duplication. That is, if the PPPR value is not set, the UE may not perform packet duplication. However, since the PPPP value is associated with the selection of a logical channel and a carrier, the PPPP value must always be set by the application layer for each V2X message, regardless of the UE version. Furthermore, the Tx profile may always need to be set as a standard for second-type V2X UEs to determine the transmission format of each V2X message.

[0165] Example

[0166] Implementing V2X communication requires various development areas, such as applications, roads, data security, and wireless communications. Therefore, development of each technology can be performed independently. This can lead to mismatched support versions. For example, considering future application updates, an application implemented as Rel-14 may be released even though wireless communications support the Rel-15 standard.

[0167] Alternatively, the Rel-14 V2X UE can be updated with the Rel-15 version. In this case, as described above, since the development of wireless communication and the development of applications can be performed separately, although the Rel-15 V2X wireless communication standard is supported, the application can be Rel-14.

[0168] Alternatively, the primary purpose of a vehicle application is to control the vehicle. If a new application version of the vehicle control system encounters an error, the UE's application layer can be converted to an existing, security-guaranteed application version to ensure vehicle safety. In this case, while the Rel-15 V2X wireless communication standard is supported, the application may be Rel-14.

[0169] Figure 8 An example is shown in which the type of communication protocol supported by the UE and the type of application supported by the UE are different according to an exemplary embodiment.

[0170] refer to Figure 8 A second type V2X UE may be configured using a communication protocol supporting the second type V2X and an application supporting the first type V2X operation. For example, as described above, the first type may be Rel-14, and the second type may be Rel-15. However, this is provided as an example only. That is, it is applicable to situations where the type of communication protocol supporting V2X operation differs from the type of application supporting V2X operation.

[0171] For example, a Type-2 V2X UE may not receive Tx profile information and PPPR information. As described above, the optional provision of PPPR allows Type-2 V2X UEs to operate smoothly. However, if a Tx profile is not provided, it may be difficult for the corresponding UE to determine the transmission format. If the UE randomly selects the transmission format, some UEs may not receive important messages, which could cause serious problems. Therefore, to prevent this problem, UE operation without Tx profile provision is proposed.

[0172] Figure 9 is a flow chart illustrating an example of UE operation according to an example embodiment based on the foregoing description.

[0173] According to this exemplary embodiment, if the V2X UE does not receive Tx profile information from the upper layer, a default transmission format may be applied so that all UEs can always receive V2X messages. Here, the default transmission format refers to the first type transmission format.

[0174] Described in detail, the second type V2X UE may operate as follows.

[0175] For example, in operation S910, the UE may generate a notification message, such as a V2X message, by detecting a dangerous situation through a sensor under a specific situation. Figures 1 to 8 The UE's application layer may verify the service associated with the V2X message. If the UE's application layer supports the second type of V2X, then in operation S920, the application layer may set PPPP and Tx profile values ​​for the V2X message. The UE's application layer may transmit the set PPPP and Tx profile values ​​along with the V2X message to the AS layer, and the UE may perform the following operations to send the V2X message.

[0176] For example, a Mode 3 UE can request Tx resources from the base station via a sidelink BSR. Based on the sidelink BSR, the base station can verify the amount of data the UE intends to transmit and determine the resources required for transmission. The base station can use the configured SL-V-RNTI to schedule the Tx resources and sidelink control information required for data transmission and provide the scheduled Tx resources to the UE. Upon receiving the resources, the UE can configure a MAC PDU based on the allocated scheduled resources and, in operation S930, determine the transmission format based on the Tx profile of the data with the highest priority in the MAC PDU. Furthermore, it can perform sidelink transmission in operation S950. In other words, a Mode 3 UE can determine the transmission format based on Tx profile information rather than using the base station's scheduling information. Here, sidelink communication can be performed in subframes defined as the UE's sidelink control period. The sidelink control period refers to the period during which resources allocated to a cell for sidelink control information and sidelink data transmission occur. During the sidelink control period, the UE can transmit sidelink data and sidelink control information. The control information can include Layer 1 ID, MCS, TA value, and resource location information.

[0177] As another example, a Mode 4 UE may select resources from a resource pool configured by the base station based on system information or a preconfigured resource pool. Each resource pool is associated with one or more PPPPs. Therefore, in operation S930, the UE may select a Tx resource pool based on the PPPP of the logical channel with the highest priority in the MAC PDU to be transmitted, and may determine the transport format based on the Tx profile value of the V2X message with the highest priority. The MCS range (first type transport format or second type transport format) may be determined based on the Tx profile value received from the application layer, and the UE may select a single value from the MCS range. In operation S950, the UE may perform sidelink transmission based on the resource pool and transport format selected in the sidelink control period. Here, once a resource pool is selected, the resource pool is only valid during the sidelink control period. After the sidelink control period expires, the UE may perform the resource pool selection process again.

[0178] That is, there is a difference between Mode 3 UE and Mode 4 UE regarding a Tx resource selection method, and a similarity in that a transmission format is determined based on a Tx profile value of the UE without base station control.

[0179] However, if the UE's application layer does not support the second type of V2X functionality, then in operation S920, the UE's application layer may only transmit the V2X message and the PPPP value. In this case, the UE may not know the purpose of the V2X message, the service associated with the V2X message, or the receiver of the V2X message, and thus may not be able to easily determine the transmission format of the V2X message. Therefore, UE operation is required to apply the appropriate transmission format without receiving a Tx profile.

[0180] That is, in operation S940, if the UE does not receive the Tx profile value for the V2X message to be transmitted, the UE may perform transmission by applying a default transmission format, such as the first type transmission format, so that all UEs may receive the V2X message in operation S940.

[0181] In detail, the second type UE can apply all of the first type transmission format and the second type transmission format. That is, the second type UE can send a V2X message by applying a single transmission format between the first type transmission format and the second type transmission format.

[0182] Here, the UE may consider the message recipient as a criterion for selecting a transmission format. If all V2X UEs, including first-type UEs and second-type UEs, need to receive a transmitted V2X message, the second-type UEs may apply the first-type transmission format. If the transmitted V2X message is addressed to a second-type UE, the UE may apply the second-type transmission format.

[0183] Here, the receiver of the message can be determined based on the V2X service. The V2X service can be determined by whether the UE's application layer supports the corresponding service, and the UE's application layer can verify the service of the generated V2X message. For example, if the UE's application layer supports a safety service as one of the first type of V2X functions, and the UE generates a V2X message for security, the UE's application layer can instruct the UE to use a first type of transmission format through the Tx profile so that all V2X UEs can receive the V2X message. When the UE's application layer supports a platooning / remote driving service as a second type of V2X function and the UE generates a V2X message for this service, the UE's application layer can instruct the UE to use a second type of transmission format through the Tx profile. This allows for enhanced transmission performance using relatively small amounts of resources and high throughput.

[0184] However, if a fallback to existing V2X applications occurs due to a vehicle control system error, the UE's application layer may not support the second-type V2X functionality, even though the UE supports all first-type and second-type transmission formats. Here, the service of the second-type V2X functionality is not supported at the UE, and therefore, even the second-type UE may not generate messages for this service. Furthermore, the Tx profile is not supported.

[0185] Therefore, in this case, the V2X message generated by the second-type UE can be a message intended for all V2X UEs, similar to the V2X message generated by the first-type UE. However, as described above, regardless of whether the application layer supports the second-type V2X functionality, the second-type UE can still use the first-type transmission format and the second-type transmission format. Therefore, if the UE arbitrarily selects a transmission format in this case, even for data intended for all V2X UEs, the UE can transmit the V2X message using the second-type transmission format. However, some UEs, such as the second-type UE, may not receive the V2X message, which can cause problems.

[0186] In this case, the second type of UE should not freely select the transport format based on the UE implementation. The second type of UE can verify that when the Tx profile information is not available, the UE's application layer does not support the second type of function. Here, it is necessary to define the UE operation so that the UE can always apply the first type of transport format.

[0187] In case that the MAC PDU is transmitted through the above-mentioned transmission method, all UEs can successfully receive the MAC PDU regardless of the UE version.

[0188] Figure 10 A block diagram illustrating an example of a configuration of a UE device according to an example embodiment.

[0189] The UE according to an example embodiment may be based on Figure 10 UE device to operate.

[0190] For example, refer to Figure 10, the UE device 1010 may include a processor 1020, an antenna unit 1050, a transceiver 1060, and a memory 1070. Here, the above components may be selectively included and are not limited thereto. For example, the processor 1020 performs baseband-related signal processing and may include upper layer processing 1030 and PHY layer processing 1040. The upper layer processing 1030 may process operations of the media access control (MAC) layer, the radio resource control (RRC) layer, or higher layers. The PHY layer processing 1040 may process operations of the PHY layer, such as MAC PDU transmission. The antenna unit 1050 may include at least one physical antenna. When the antenna 1050 includes multiple antennas, the antenna unit 1050 may support multiple-input multiple-output (MIMO) transmission and reception. The transceiver 1060 may include a radio frequency (RF) transmitter and an RF receiver. The memory 1070 may store operation processing information of the processor 1020, applications, OS, software, etc. associated with UE operations, and may also include components such as a buffer. The above-mentioned components may be software configurations as logical entities.

[0191] The processor 1020 of the UE device 1010 may be configured to implement UE operations in the example embodiments described herein. For example, the UE device 1010 may use a MAC PDU generator 1034 included in the upper layer processing 1030 to generate a MAC PDU based on the V2X message and Tx profile information received from the application layer, and may use a transport format applier 1038 to apply a transport format. The UE device 1010 may send this information to the PHY layer processing 1040, which may transmit the MAC PDU via a PC5 link. However, if no Tx profile information corresponding to the V2X message is received from the application layer, the transport format applier 1038 may apply a default format.

[0192] According to an exemplary embodiment of the present disclosure, the application layer may verify data arrival and then determine (set or configure) Tx profile information based on the service. The application layer determines the transport format for data transmission based on the set Tx profile information and controls the data to be sent using the determined transport format. Here, the process of determining the transport format for data transmission may include selecting an MCS index group including indexes of different ranges based on the Tx profile information.

[0193] For example, according to an example of the present disclosure, when the Tx profile information is determined to be 1, the process of determining the Tx profile information includes selecting a first type of transmission format for data. The first type of transmission format may select one of the MCS indices ranging from 0 to 28. Meanwhile, when the Tx configuration information is determined to be 2, the process of determining the Tx configuration information includes selecting a second type of transmission format. The second type of transmission format may include selecting one of the MCS indices ranging from 0 to 31.

[0194] Here, the process of determining Tx profile information as 2 can be used to transmit data and service messages for evolved V2X services such as platooning and remote driving. At the same time, the process of determining Tx profile information as 1 can be used to support default V2X services to ensure safety.

[0195] Therefore, the application layer of the Tx UE can determine the PPPP and PPPR for data and the Tx profile information for data transmission according to the service, and can transmit the determined PPPP, PPPR and Tx profile information to the AS layer, and therefore, can control the MAC PDU generator 1034 to generate MAC PDU and control the transport format applier 1038 to apply the transport format.

[0196] Here, the Tx UE may determine that the Tx profile information is 1 for non-specific Rx UEs in the cell and may set Tx profile information 1 as the default Tx format. The Tx UE may select transmission resources from a configured transmission resource pool based on the PPPP of logical channels with data priority, and may select a transmission profile based on the Tx profile value of the V2X message with the highest priority. The determined transmission format for data transmission may be broadcast to non-specific UEs within the cell.

[0197] Meanwhile, the upper layer processing 1030 and the PHY layer processing 1040 of the processor 1020 may be software configurations. Therefore, the aforementioned components may not necessarily be used, but may be selectively used to configure the UE device 1010. That is, the aforementioned components may be illustrated as logical configurations in the drawings to describe the operations according to the example embodiments in detail, and may not necessarily be included and implemented thereby. Here, for the sake of clarity of description, a configuration for performing detailed operations is described, and is not limited to the above-described example embodiments.

[0198] In the above-mentioned example method, the process is described as a series of operations based on the flow chart, and aspects of the present disclosure are not limited to the order or sequence shown. Some operations can be processed in different orders or can be processed substantially simultaneously. In addition, it will be understood that the operations shown in the flow chart do not necessarily exclude other operations. Other operations can be included and one or more operations can be omitted without departing from the spirit and scope of the present disclosure.

[0199] The various embodiments of the present disclosure are not all possible combinations and are used to explain representative aspects of the present disclosure. Therefore, it will be apparent that the descriptions made in the various embodiments can be applied independently or in combination with at least two of them.

[0200] In addition, various embodiments of the present disclosure may be implemented by hardware, firmware, software, or a combination thereof. In the case of hardware implementation, the embodiments may be implemented by one or more application specific integrated circuits (ASICs), digital signal processors (DSPs), digital signal processing devices (DSPDs), programmable logic devices (PLDs), field programmable gate arrays (FPGAs), general purpose processors, controllers, microcontrollers, microprocessors, and the like.

[0201] The scope of the present disclosure includes software or machine-executable instructions (e.g., OS, applications, firmware, programs, etc.) that enable the operations of the methods of various embodiments to be performed on a device or computer, as well as non-transitory computer-readable media that store such software or instructions for execution on a device or computer.

[0202] Industrial Applicability

[0203] Aspects of the present disclosure may be applied to various systems.

Claims

1. A method performed by a wireless user equipment, the method comprising: selecting a first transmission format associated with a first Tx profile based on a transmission Tx profile for one or more data packets not being received from the application layer, wherein the one or more data packets are for vehicle-to-everything (V2X) transmission between wireless user equipment, and wherein the first transmission format is configured to use a first MCS index range included in a second modulation and coding scheme (MCS) index range configured for a second transmission format; as well as The one or more data packets are transmitted from the wireless user equipment to one or more wireless user equipment based on the selected first transmission format.

2. The method according to claim 1, in, The wireless user equipment is configured to support the first transmission format and the second transmission format; as well as The application layer of the wireless user equipment is not configured to indicate the transmission profile for the one or more data packets to the access layer (AS) layer of the wireless user equipment.

3. The method according to claim 1 or 2, further comprising: It is determined that the Tx profile for the one or more data packets is not configured by an upper layer of the wireless user equipment.

4. The method according to claim 1, further comprising: determining a Tx profile for the one or more second data packets based on a service type with respect to the one or more second data packets; selecting a transmission format associated with the Tx profile for the one or more second data packets; as well as The one or more second data packets are transmitted from the wireless user device to one or more wireless user devices based on the selected transmission format associated with the Tx profile for the one or more second data packets.

5. The method according to claim 4, further comprising: The determined Tx profile for the one or more second data packets is provided from the application layer to the access layer.

6. The method according to claim 4, further comprising: At least one of: a ProSe per-packet priority (PPPP) associated with the one or more second data packets and a ProSe per-packet reliability (PPPR) associated with the one or more second data packets is provided from the application layer to the access layer.

7. The method according to claim 1, further comprising: determining a plurality of Tx profiles for the plurality of second data packets based on one or more service types with respect to the plurality of second data packets; selecting a transmission format associated with a Tx profile among the plurality of Tx profiles; as well as The plurality of second data packets are transmitted based on the selected transmission format associated with the Tx profile of the plurality of Tx profiles.

8. The method according to claim 7, wherein: The selecting the transmission format associated with the Tx profile of the plurality of Tx profiles is based on priorities of logical channels associated with the plurality of second data packets.

9. The method according to claim 8, wherein The priority of the logical channel associated with the plurality of second data packets is a highest priority in a Medium Access Control Protocol Data Unit (MAC PDU).

10. The method according to claim 1, wherein The second transmission format is associated with at least one of: a platooning service and a remote driving service.

11. The method according to claim 1, wherein The first transmission format is associated with a road safety service.

12. The method according to claim 1, wherein The first transmission format is a default transmission format.

13. A non-transitory computer-readable medium storing instructions, which, when executed by a wireless user device, cause the method of any one of claims 1 to 12 to be performed.

14. A wireless user equipment, comprising: transceiver; one or more processors; as well as The memory stores instructions, which, when executed by the one or more processors, cause the wireless user equipment to perform the method according to any one of claims 1 to 12.

15. A system comprising: The wireless user equipment according to claim 14; as well as The base station is configured to send resource information to the wireless user equipment.

16. A wireless user equipment, comprising: transceiver; one or more processors; as well as a memory storing instructions that, when executed by the one or more processors, cause the wireless user device to: Receive a sidelink vehicle-to-everything transmission profile list SL-V2X-TxProfileList indicating a transmission Tx profile; Sending, from the application layer of the wireless user equipment to the access layer of the wireless user equipment, a ProSe per-packet priority (PPPP) and a ProSe per-packet reliability (PPPR); as well as A medium access control MAC protocol data unit (PDU) is generated based on the PPPP, the PPPR and the Tx profile.

17. A system comprising: The wireless user equipment according to claim 16; as well as The base station is configured to send resource information to the wireless user equipment.

Images