CN112640546A

CN112640546A - User equipment and method with improved critical communication notification in wireless communications

Info

Publication number: CN112640546A
Application number: CN201980057292.3A
Authority: CN
Inventors: 哈勒德·肖基·哈桑; 埃尔克·罗特-曼迪茨; 本雅明·扎肯罗伊特
Original assignee: Fraunhofer Gesellschaft zur Forderung der Angewandten Forschung eV
Current assignee: Koninklijke Philips NV
Priority date: 2018-08-10
Filing date: 2019-08-08
Publication date: 2021-04-09

Abstract

User equipment for wireless communication is provided. The user equipment comprises a transmitter (152) and a receiver (154). The first resource pool includes a first plurality of resources for transmission. The second resource pool includes a second plurality of resources for transmission. The second resource pool configuration is different from or equal to the first resource pool configuration. The transmitter (152) is configured to transmit a first critical communication notification as a first message in a first resource pool, wherein the first critical communication notification indicates that a second message is to be transmitted in a second resource pool. Further, the transmitter (152) is configured to send a second message in the second resource pool after or simultaneously with sending the first critical communication notification. The third resource pool includes a third plurality of resources for transmission. The fourth resource pool includes a fourth plurality of resources for transmission. The fourth resource pool configuration is different from or equal to the third resource pool configuration. The receiver (154) is configured to receive a second critical communication notification as a third message, the second critical communication notification being sent in a third resource pool, wherein the second critical communication notification indicates that a fourth message is to be sent in a fourth resource pool. The transmitter (152) is configured to not send anything in the fourth resource pool in response to the receiver (154) receiving the second critical communication notification.

Description

User equipment and method with improved critical communication notification in wireless communications

The present invention relates to the field of wireless communication networks, and more particularly to concepts for transmitting data in a wireless communication network. In particular, the present invention relates to user equipment and methods with improved critical communication in wireless communication. Critical communications may be, for example, emergency notifications, such as in V2X (vehicle-to-all) or D2D (device-to-device), or may involve, for example, other types of communications that require very low latency and/or high reliability.

In mobile communications, different entities may communicate with each other. For example, some possible communications between different entities may be classified as V2X (e.g., V2V (vehicle-to-vehicle)) and D2D communications. In V2X, data signaling and control signaling are always multiplexed in frequency or time. Data and control may be transmitted in the same subframe or different/subsequent subframes.

Typically, communication is performed using, for example, an uplink from a User Equipment (UE) to a base station or using, for example, a downlink from a base station to a user equipment. The base station may be, for example, any kind of NodeB, such as an eNB (evolved Node B). Sidelink transmissions without a link to a base station, e.g. between two user equipments, are relatively new concepts that are becoming more and more important.

Detailed information on V2X, V2V, D2D (device-to-device) and side links can be found, for example, in [1 ]]、[3]、[4]Is found in (1). The information about unlicensed transmission, i.e. preconfigured resources, in the sidelink (transmission modes 2 and 4, D2D) may be, for example, [2 []And [5]]Is found in (1). According to [1]The UE should randomly select a cyclic shift n in {0, 3, 6, 9} in each physical side link control channel (PSCCH) transmission_cs,λ。

The current V2X specification of 3GPP (third generation partnership project) in long term evolution (LIE) supports two modes, mode 3 and mode 4. In the New Radio (NR) fifth generation (5G), these modes are mainly centralized resource allocation (similar to mode 3) and autonomous resource allocation (similar to mode 4).

In mode 3, resource provisioning is performed via the base station. A User Equipment (UE) connects to a base station supporting V2X operation and obtains its resources from the base station.

Mode 4 is an autonomous mode employing distributed scheduling. The UE is required to detect the appropriate resource itself. Currently, in mode 4, one second of sensing operation is required before transmission using any resources.

The concept of an emergency pool includes the presence of a special resource pool, special resource configuration, special resource pool configuration, special (common) bandwidth part (BWP) that can be used for very limited purposes, e.g. used by UEs without dedicated granted resources-grants for transmission during handover/Radio Link Failure (RLF). In this case, these configured/preconfigured resources are referred to as shared resource pool or shared/commonly configured grant or common bandwidth part (BWP), i.e. it may also be a grant for configuration in the conventional exception pool, normal shared pool or full bandwidth, sub-bandwidth or bandwidth part (BWP) of V2X.

In V2X, a shared resource pool, common configuration resources, or a common BWP for Sidelink (SL) communication is mainly defined to communicate in abnormal situations whenever a resource cannot be configured/preconfigured (e.g. during radio link failure, during switching user equipment from connected to idle, when sensing results are not available, or during handover). This is valid for both scheduling modes: grant-based resource selection for network control in mode 3 and autonomous resource selection in mode 4. In LTE (long term evolution) release 15, an abnormal resource pool (shared resource pool or shared/commonly configured grant or common bandwidth part (BWP)) can only be accessed if resources are randomly selected.

Thus, the main goal of this exception pool (shared resource pool or shared/commonly configured grant or common bandwidth part (BWP)) is to be accessed only briefly and instantaneously during an exception situation to avoid any congestion in the exception pool. Large PDCP (packet data convergence protocol) PDUs (protocol data units) are not supported for transmission over sidelinks in the exception pool to allow resources to be opened for other UEs and to avoid higher collision probabilities.

For example, the exception pool is a resource pool comprising a plurality of resources for transmission, is a shared resource pool or a shared/commonly configured granted or common bandwidth part (BWP), and is also a conventional exception pool.

In [6], critical tasks and emergency notifications are described that request spontaneous unlicensed transmissions for V2X (e.g., packets that can be used for ultra-reliable low-latency communications, URLLC, flows with high quality of service (QoS) and requirements).

To ensure successful Emergency Notification (EN) for V2X, low latency and high reliability are mandatory.

It would therefore be highly appreciated if an improved concept for emergency notification could be provided.

It is an object of the present invention to provide an improved concept for emergency notification and high QoS priority URLLC data transmission in wireless communication. The object of the invention is solved by a user equipment according to claim 1, a system according to claim 23, a method according to claim 24 and a computer program according to claim 25.

A user equipment for wireless communication is provided. The user equipment includes a transmitter and a receiver. The first resource pool defined by the first resource pool configuration includes a first plurality of resources for transmission. The second resource pool defined by the second resource pool configuration includes a second plurality of resources for transmission. The second resource pool configuration is different from or equal to the first resource pool configuration. The transmitter is configured to transmit a first critical communication notification as a first message in a first resource pool, wherein the first critical communication notification indicates that a second message is to be transmitted in a second resource pool. Further, the transmitter is configured to send a second message in the second resource pool after or simultaneously with sending the first critical communication notification. The third resource pool defined by the third resource pool configuration includes a third plurality of resources for transmission. The fourth resource pool defined by the fourth resource pool configuration includes a fourth plurality of resources for transmission. The fourth resource pool configuration is different from or equal to the third resource pool configuration. The receiver is configured to receive a second critical communication notification as a third message, the second critical communication notification being sent in a third resource pool, wherein the second critical communication notification indicates that a fourth message is to be sent in a fourth resource pool. The transmitter is configured to not send anything in the fourth resource pool in response to the receiver receiving the second critical communication notification.

Further, a method for wireless communication is provided. The first resource pool includes a first plurality of resources for transmission. The second resource pool includes a second plurality of resources for transmission. The second resource pool configuration is different from or equal to the first resource pool configuration. The third resource pool includes a third plurality of resources for transmission. The fourth resource pool includes a fourth plurality of resources for transmission. The fourth resource pool configuration is different from or equal to the third resource pool configuration. The method comprises the following steps:

-sending, by a transmitter of a user equipment, a first critical communication notification as a first message in a first resource pool, wherein the first critical communication notification indicates that a second message is to be sent in a second resource pool,

-sending a second message in the second resource pool by the transmitter after or simultaneously with sending the first critical communication notification,

-receiving a second critical communication notification as a third message, the second critical communication notification being sent by the receiver of the user equipment in the third resource pool, wherein the second critical communication notification indicates that a fourth message is to be sent in the fourth resource pool. And:

-in response to the receiver receiving the second critical communication notification, the transmitter does not send anything in the fourth resource pool.

Furthermore, a computer program for implementing the above-described method when it is executed on a computer or signal processor is provided.

Embodiments are based on a new concept applicable to direct D2D communication for very low latency and high reliability access. The new concept may also be applied, for example, in part to critical communication notifications in the uplink.

The new concept may include, for example, transmitting spontaneous, unauthorized ENs using certain signal characteristics (e.g., increased power settings). For example, a unique signal indicating an emergency may be transmitted. The critical communication notification may be sent, for example, in the frequency/time domain and not used in the currently defined frame structure. Retransmissions may for example be defined to ensure requested reliability or QoS (quality of service). Upon receiving the ENs, the neighboring UEs may, for example, be configured to stop transmissions in the contiguous pool of D2D to avoid interference with retransmitted ENs. When an EN is transmitted, UEs that have not received the EN due to simultaneous transmissions are notified, e.g., using randomized time-frequency resources, to avoid repeated interference in subsequent TTIs (TTI ═ transmission time interval) or also referred to as Subframes (SF). Communicating critical communication notifications may be applied, for example, to notify additional remote UEs.

According to an embodiment, immediate resource pool access is provided to announce emergency transmissions or high priority data transmissions in parallel or in delayed time slots. For example, if the UE supports multiple component carriers, concurrent transmission of announcements and data transmissions may be possible, for example.

In an embodiment, the notification of the exception pool may, for example, provide an indication of the resources (e.g., one or more pointers, one or more offsets) used for transmission of the payload. The information may for example comprise a subframe indication and/or a frequency indication and/or a resource pool identified by a pool used for data transmission and/or a component carrier identification.

The resource pool may be defined, for example, abnormally for mission critical communications. The resource pool may be sent via an exception resource pool comprising new radio resources allocated by a pre-configured or configured grant (e.g., of new radio resources). Alternatively, a conventional LTE transmission or LTE band may be used, for example, for transmitting one or more short control messages and/or one or more short data packets. In LTE, the LTE Uu interface may be responsible for this configuration. If the resource pool (or the exception resource) is configured by the NR, it may use the NR Uu interface. (the Uu interface is the radio interface between the base station and the user equipment.)

According to an embodiment, resources may be freed, for example, as indicated in the exception pool: in this case, any resources reserved for high priority data in the anomalous poll are no longer allowed to be used by any other UE, even if the resources have been scheduled/sensed as idle before the indication is received in the anomalous pool.

In an embodiment, if the base station is responsible for resource allocation (e.g., in mode 3), the User Entity (UE)/User Equipment (UE) requesting high priority data transmission may for example provide for transmission on the abnormal pool (with limited resources for control or data or both), or for example on the normal pool, or for example both (transmission on the abnormal pool and the normal pool).

For example, an exception pool is a resource pool that includes a plurality of resources for transmission.

For example, a regular pool is another resource pool that includes another plurality of resources for transmission.

According to embodiments, if the UE is responsible for requesting resource allocation for high priority data transmission (e.g., in mode 4), the UE may send, for example, on the exception pool (with limited resources for control or data or both) or may send, for example, on the normal pool or both (transmissions on the exception pool and the normal pool).

In an embodiment, the high priority/critical traffic notification may be derived from, for example, PPPP (ProSe per packet priority) or packet delay budget, or from, for example, PPPR (ProSe per packet reliability), or from, for example, any combination of packet error rate, for example from previous metrics or different QoS flow indications.

Embodiments ensure reliable and low latency communication for the transmission of urgent/high priority messages.

Embodiments are based on immediate, very short-term notifications, including an indication of which resources are to remain clear to any other UE, even if already allocated/scheduled. These resources that remain clear may be reserved, for example, for transmission of emergency/high priority messages.

In embodiments, UEs receiving the notification may, for example, be configured to interrupt their active transmission or defer their scheduled resources if they successfully decode the notification.

It is assumed that all UEs belonging to LTE/5G/NR (NR ═ new radio) can decode the abnormal pool/the abnormal pre-configured resources and the repetitions over the regular pool.

According to an embodiment, the delay is reduced and the reliability is increased for high priority notifications.

With respect to latency, long sensing periods are avoided by employing "critical" resource reservations.

The UE may be allowed access to resources (other than the emergency/exception resources/pools) in the resource pool/resource pool configuration, for example, without the need for one second sensing required in current specifications.

With respect to reliability, UEs with lower priority payloads may, for example, be prohibited from transmitting even transmissions that have been scheduled to prioritize high priority data to avoid interference and thus result in higher reliability for high priority data transmissions.

For example, priority/critical communication may be derived using one of the following metrics or using a combination of two or more of the following metrics:

PPPP (ProSe per packet priority)

PPPR (ProSe per packet reliability)

-packet delay budget

-packet error rate

QoS flows

-any combination of previous indicators.

Some embodiments may implement multiplexing data and control, for example, over an exception pool (or any emergency/exception pool) that indicates future transmission resource periods, frequencies, and times.

Some embodiments may implement multiplexing data and control, for example, in an exception pool, and redundancy in an autonomous mode.

Some embodiments may notify other UEs of resources on the shared resource pool, e.g., on a very short term basis, to keep resources (in the notification) clear. An advantage may be that, for example, any high priority/emergency message may be transmitted without authorization (e.g., with very low latency) with high reliability, since other UEs may, for example, be prevented from using the indicated resources.

Some embodiments may, for example, enhance the use of the exception/emergency pool to allow low latency communications.

In some embodiments, if data has been sent via the exception/emergency pool, the subchannel size and/or subchannel offset and/or SPS period (SPS ═ semi-persistent scheduling) may be sent, for example, by SCI (sidelink routing information), and/or the preconfigured period may be sent, for example, by SCI (sidelink routing information).

Some embodiments may transmit, for example, without sensing, by transmission on the abnormal pool and (e.g., simultaneously) by parallel transmission on the regular pool at variable power up to a certain time (e.g., up to a certain time T _ max _ P).

Embodiments may be employed, for example, in the fields of V2X, D2D, mtc (large scale machine type communication), URLLC, and in delay-critical/reliability-critical communication.

In an embodiment, if a vehicle has an emergency request, and if the vehicle is within the coverage of a base station, a subframe bitmap received by the vehicle from the base station is sent (forwarded) from the vehicle to another vehicle that is outside the coverage of the base station.

Embodiments of the invention are described in more detail below with reference to the attached drawing figures, wherein:

figure 1 shows a user equipment for wireless communication according to an embodiment,

figure 2 shows a schematic representation of an example of a wireless communication system,

figure 3 shows a schematic representation of a cell with two different overlapping networks such as the cell in figure 2-i.e. a macro cell network comprising macro cells and a small cell network comprising small cell base stations connected to the macro cell base stations via backhaul links,

figure 4 shows a further schematic representation of a plurality of small cells of a macro cell similar to that of figure 3, wherein the small cell base stations are interconnected via backhaul links and connected to a core network,

figure 5 illustrates an example of a computer system 500 according to an embodiment,

figure 6 illustrates cross-carrier scheduling via SCI transmission on an abnormal resource pool according to an embodiment,

figure 7 illustrates intra-carrier scheduling via SCI transmission on an abnormal resource pool in accordance with an embodiment,

figure 8 illustrates SPS repetition and SCI redundancy in accordance with an embodiment,

figure 9 illustrates SPS data under control information repeated in an exception pool and a normal pool according to an embodiment,

figure 10 shows the same component carrier scheduling for emergency data and regular data according to an embodiment,

figure 11a shows different component carrier scheduling for emergency data and normal data according to an embodiment,

figure 11b shows different component carrier scheduling for emergency data and normal data according to another embodiment,

FIG. 12 shows a side link subframe configuration forwarded out of coverage for emergency monitoring, an

Fig. 13 illustrates a system for wireless communication according to an embodiment.

In the following description, numerous details are set forth to provide a more thorough explanation of embodiments of the present invention. It will be apparent, however, to one skilled in the art that embodiments of the invention may be practiced without these specific details. In other instances, well-known structures and devices are shown in block diagram form, rather than in detail, in order to avoid obscuring embodiments of the present invention. In addition, the features of the different embodiments described below may be combined with each other, unless specifically indicated otherwise.

Before describing embodiments of the present invention in detail, concepts on which the embodiments of the present invention are based are described.

Fig. 2 is a schematic representation of an example of a wireless network 100 comprising a core network 102 and a radio access network 104. The radio access network 104 may include a plurality of base stations, enbs₁To eNB₅Each base station serving a respective cell 106₁To 106₅Schematically represented as a certain area around the base station. A base station is provided to serve users within a cell. The user may be a fixed device or a mobile device. Furthermore, wireless communication systems may be accessed by mobile or fixed IoT devices (IoT) connected to base stations or users. Mobile devices or IoT devices may include physical devices, ground-based vehicles (e.g., robots or automobiles), aircraft (e.g., manned or Unmanned Aerial Vehicles (UAVs), which are also known as drones), buildings, and other items in which electronic devices, software, sensors, actuators, etc. are embedded, as well as network connections that enable these devices to collect and exchange data over existing network infrastructure. Fig. 2 shows an exemplary view of only five cells, however, a wireless communication system may include many more such cells. FIG. 2 shows a cell 106₂And by the base station eNB₂Serving two user UE₁And UE₂Also known as User Equipment (UE). Another user UE₃Is shown in a base station eNB₄Serving cell 106₄In (1). Arrow 108₁、108₂And 108₃Schematically representing a method for slave user UE₁、UE₂And UE₃To base station eNB₂、eNB₄For transmitting data or for transmitting data from base station eNB₂、eNB₄To user UE₁、UE₂、UE₃Uplink/downlink connections that transmit data. In addition, FIG. 2 shows a cell 106₄Two IoT devices 110 that may be fixed or mobile devices are shown₁And 110₂. As indicated by arrow 112₁Schematically represented, IoT devices 110₁Via base station eNB₄A wireless communication system is accessed to receive and transmit data. As indicated by arrow 112₂Schematically represented, IoT devices 110₂Via user UE₃A wireless communication system is accessed. Corresponding base station eNB₁To eNB₅The respective backhaul links 114, which may be schematically represented in fig. 2 by arrows pointing to "cores", e.g., via the S1 interface₁To 114₅Is connected to the core network 102. The core network 102 may be connected to one or more external networks. In addition, corresponding base station eNB₁To eNB₅Some or all of which may be connected, e.g., via X1 or X2 interfaces, via respective backhaul links 116 schematically represented in fig. 2 by arrows pointing to "enbs"₁To 116₅Are connected to each other.

The wireless network or communication system depicted in fig. 2 may be a heterogeneous network with two different overlapping networks, i.e. each macro cell comprises a macro base station, such as a base station eNB₁To eNB₅And a network of small cell base stations (not shown in figure 2), such as femto or pico base stations.

There are multiple resources for transmission. For data transmission, a physical resource grid may be used. The physical resource grid may include a collection of resource elements to which various physical channels and physical signals are mapped. For example, the physical channels may include physical downlink and uplink shared channels (PDSCH, PUSCH) carrying user-specific data (also referred to as downlink and uplink payload data), Physical Broadcast Channels (PBCH) carrying, for example, Master Information Blocks (MIB) and System Information Blocks (SIB), physical downlink and uplink control channels (PDCCH, PUCCH) carrying, for example, Downlink Control Information (DCI), and so on. For the uplink, the physical channels may also include a physical random access channel (PRACH or RACH) used by the UE to access the network once the UE synchronizes and obtains the MIB and SIBs. The physical signal may include a Reference Signal (RS), a synchronization signal, and the like. The resource grid may comprise frames having a certain duration, e.g. 10 milliseconds, in the time domain and a given bandwidth in the frequency domain. The frame may have a certain number of subframes of predefined length, e.g. 2 subframes of length 1 ms. Each subframe may include two slots of 6 or 7 OFDM symbols according to a Cyclic Prefix (CP) length.

For sidelink communications (e.g., for Radio Resource Controller (RRC) connected UEs after successful association with a base station, or for idle or remote UEs, e.g., in a dedicated band), there is a physical sidelink shared channel (pscch) for data. In addition, control on the sidelink requires a Physical Sidelink Control Channel (PSCCH).

Both channels psch and PSCCH are transmitted between UEs over a time/frequency resource grid. For sidelink transmission, the resource pool/pre-configured resources may be on a dedicated carrier or in a band with LTE and NR with an uplink channel.

The wireless communication system may be any single-tone or multi-carrier system using frequency division multiplexing, such as an Orthogonal Frequency Division Multiplexing (OFDM) system, an Orthogonal Frequency Division Multiple Access (OFDMA) system, or any other IFFT-based signal with or without a CP, such as DFT-s-OFDM. Other waveforms may be used, such as non-orthogonal waveforms for multiple access, e.g., filter bank multi-carrier (FBMC), Generalized Frequency Division Multiplexing (GFDM), or general purpose filtered multi-carrier (UFMC). The wireless communication system may for example operate according to the LTE-Advanced pro standard or the 5G or NR (new radio) standard. In LTE, the sidelink channel uses DFT-s-OFDM waveforms. In NR, the side-link may use two waveforms, namely DFT-s-OFDM and/or OFDMA.

In the wireless communication network shown in fig. 2, the radio access network 104 may be a heterogeneous network including a network of primary cells, each primary cell including packetsIncluding the master base station, also known as the macro base station. Further, a plurality of secondary base stations, also referred to as small cell base stations, may be provided for each of the macro cells. FIG. 3 is a cell, such as cell 106 in FIG. 2, with two different overlapping networks₁Including a macro cell 106₁A macro cell network and a small cell network. Although fig. 3 only represents a single macro cell, it should be noted that one or more of the other cells in fig. 2 may also use an overlay network. The small cell network comprises a plurality of small cell base stations SeNB₁To SeNB₅Each small cell base station is in a respective area 120₁To 120₅(also referred to as the coverage area of the small cell). Small cell base station SeNB₁To SeNB₅Can be composed of a macrocell base station MeNB₁Controlling, respective small cell base stations SeNB₁To SeNB₅Via respective backhaul links 122₁To 122₅Connecting to macrocell base station MeNB₁. Instead of connecting the small cell base stations to the macro cell base station via backhaul links, one or more of the small cell base stations may be coupled to the core network via respective backhaul links. Fig. 3 also shows a user equipment UE as arrow 124₁Indicated by macrocell base station MeNB₁Service, and as indicated by arrow 124₂Schematically indicated by small cell base station SeNB₁And (6) serving.

Figure 4 is a plurality of small cells 120 of a macro cell (not shown)₁To 120₃Is further schematically represented. The macro cell may be similar to the macro cell in fig. 3. Each small cell may serve one or more UEs. Unlike in figure 3, the corresponding small cell base station SeNB₁、SeNB₂、SeNB₃… … via a backhaul link or connection 102₁To 102₃Is connected to the core network 102. Corresponding small cell 102₁To 102₃May be directly connected to each other via an X2 interface, as schematically indicated in fig. 4. The transport network connecting the respective small cells to the core network 102 may be a fiber optic network comprising one or more points of presence (pops) at which a plurality of small cells are connected to the transport network. Reference to the literature[7]Additional details regarding the backhaul architecture as shown in fig. 4 are described.

The small cell (also referred to as secondary mobile communication cell SC) forms an overlay network to the macro cell network (also referred to as primary mobile communication cell PC). The small cell may be connected to the macro cell (figure 3) and/or the core network (figure 4) via a Backhaul Link (BL). The backhaul link may be a wired or wireless link, and in case the small cell is connected to the core network via the backhaul link, a point of presence (PoP) of the transport network (figure 4) may act as an interface to the core network. Each small cell may be via a wireless Access Link (AL)124₂Serving a plurality of mobile users UE within its coverage area. Further, the UE may connect to the primary cell, e.g., to receive control signals, and the connection may be referred to as a Control Link (CL).

Next, embodiments of the present invention are described.

Fig. 1 shows a user equipment for wireless communication according to an embodiment.

The user equipment includes a transmitter 152 and a receiver 154.

The user equipment has specific capabilities:

in the first case, the user equipment announces the critical communication with a first message. The critical communication is followed by a second piece of information. In such a case:

the first resource pool defined by the first resource pool configuration includes a first plurality of resources for transmission. The second resource pool defined by the second resource pool configuration includes a second plurality of resources for transmission. The second resource pool configuration is different from or equal to the first resource pool configuration.

The transmitter 152 is configured to transmit a first critical communication notification as a first message in the first resource pool, wherein the first critical communication notification indicates that a second message is to be transmitted in the second resource pool.

Examples for the first message are message 651 in fig. 6, message 751 in fig. 7,

messages

851 and 853 in fig. 8,

messages

951, 953 and 955 in fig. 9, messages 1051 and 1054 in fig. 10,

messages

1151 and 1154 in fig. 11a, and

messages

1156 and 1157 in fig. 11 b.

Examples for the second message are message 661 in fig. 6, message 761 in fig. 7,

messages

861, 862, 863, 864, and 865 in fig. 8,

messages

961, 962, 963, 964, and 965 in fig. 9,

messages

1061, 1062, 1063, and 1064 in fig. 10,

messages

1161, 1162, 1163, and 1164 in fig. 11, and

messages

1166 and 1167 in fig. 11 b.

The resource pool configuration may be, for example, an authorization of the resource configuration.

The first resource pool and/or the second resource pool and/or the third resource pool and/or the fourth resource pool may for example be configured in a whole band, a sub-band or a bandwidth part (BWP).

Further, the transmitter 152 is configured to send a second message in the second resource pool after or at the same time as sending the first critical communication notification.

In a second case, the user equipment receives an announcement of a critical communication within a third resource pool from another communication entity, wherein the announcement reserves a fourth resource pool for the critical communication. The user equipment adapts its behavior and does not send its own messages in the (reserved) fourth resource pool reserved by the announcement for critical communication. Followed by a critical communication from the other communication entity itself. In such a case:

the third resource pool defined by the third resource pool configuration includes a third plurality of resources for transmission. The fourth resource pool defined by the fourth resource pool configuration includes a fourth plurality of resources for transmission. The fourth resource pool configuration is different from or equal to the third resource pool configuration.

The receiver 154 is configured to receive a second critical communication notification as a third message, the second critical communication notification being sent in the third resource pool, wherein the second critical communication notification indicates that a fourth message is to be sent in the fourth resource pool.

The transmitter 152 is configured to not send anything in the fourth resource pool in response to the receiver 154 receiving the second critical communication notification.

As for the first message, examples for the third message are message 651 in fig. 6, message 751 in fig. 7,

messages

851 and 853 in fig. 8,

messages

951, 953 and 955 in fig. 9, messages 1051 and 1054 in fig. 10,

messages

1151 and 1154 in fig. 11a, and

messages

1156 and 1157 in fig. 11 b.

messages

861, 862, 863, 864 and 865 in fig. 8,

messages

961, 962, 963, 964 and 965 in fig. 9,

messages

1061, 1062, 1063 and 1064 in fig. 10,

messages

1161, 1162, 1163, 1164 in fig. 11 and

messages

1166 and 1167 in fig. 11b, as for the fourth message.

According to an embodiment, the third message comprises a pointer to a message in another resource pool, the pointer defining a frequency location and a time location for a single transmission, for example. Alternatively, the third message further defines a frequency location, a time location, and a repetition period for the repeated message; the notification may include a pointer to the message, control information, and/or a data transmission.

For example, according to an embodiment, the first message includes a pointer to the second message in the second resource pool, the pointer defining one or more frequency locations and time locations of the second message. Alternatively, the first message includes a pointer to a second message in the second resource pool, the pointer defining one or more frequency and time positions and a repetition period of the second message.

And/or the third message includes a pointer to a fourth message in the fourth resource pool that defines one or more frequency locations and time locations of the fourth message. Alternatively, the third message includes a pointer to a fourth message in the fourth resource pool that defines one or more frequency and time locations and a repetition period for the fourth message.

According to an embodiment, the first resource pool may be defined, for example, as a shared resource pool or a commonly configured granted or commonly accessed bandwidth portion or an abnormally configured pool. And/or the third resource pool may be defined, for example, as a shared resource pool or a commonly configured granted or commonly accessed bandwidth portion or an abnormally configured pool.

In an embodiment, the second resource pool may be defined, for example, as a resource pool for communication or a pre-configured communication resource or an allocated bandwidth portion or a dynamically granted resource. And/or the fourth resource pool is defined as a resource pool for communication or a pre-configured communication resource or an allocated bandwidth portion or a dynamically granted resource.

In an embodiment, the first resource pool may for example comprise a first plurality of pre-configured resources for sidelink transmissions, the second resource pool may for example comprise a second plurality of resources for sidelink transmissions, the third resource pool may for example comprise a third plurality of resources for sidelink transmissions, and the fourth resource pool may for example comprise a fourth plurality of resources for sidelink transmissions.

According to an embodiment, the transmitter 152 may for example be configured to send the first critical communication notification in the first resource pool in the first time slot. In such embodiments, the transmitter 152 may, for example, be configured to transmit the second message in the second resource pool in a second time slot after transmitting the first critical communication notification, the second time slot being a delayed time slot relative to the first time slot.

In an embodiment, the transmitter 152 may, for example, be configured to transmit the second message in the second resource pool at the same time slot when the first critical communication notification is transmitted or at a subsequent time slot after the first critical communication notification is transmitted.

According to an embodiment, the transmitter 152 may for example be configured to send the first critical communication notification comprising an indication indicating resources of the second plurality of resources for transmitting transmissions for the second resource pool. In such embodiments, the transmitter 152 may, for example, be configured to transmit a second message in the resources for transmission indicated by the indication, wherein the indication comprises a pointer to the resources for transmission, or comprises a subframe indication indicating a subframe, or comprises a frequency indication indicating a frequency, or comprises a component carrier indication indicating a component carrier.

In an embodiment, the transmitter 152 may, for example, be configured to stop sending the fifth message in the fourth resource pool in response to the receiver 154 receiving the second critical communication notification.

According to an embodiment, the fifth message may be scheduled for transmission in a fourth resource pool, for example. In such embodiments, the transmitter 152 may, for example, be configured to not send the fifth message in the fourth resource pool in response to the receiver 154 receiving the second critical communication notification.

In an embodiment, the first resource pool may be an exception pool, e.g. for providing the first plurality of resources for transmissions having a high priority, the exception pool being a grant of a configuration in a shared pool or a full bandwidth, sub-bandwidth or bandwidth part. The second resource pool may be, for example, a conventional pool for providing the second plurality of resources for transmissions having a lower priority than the high priority. The transmitter 152 may, for example, be configured to send the second message with a high priority in an exception pool that is a grant of configuration in a shared pool or full bandwidth, sub-bandwidth, or portion of bandwidth. The transmitter 152 may, for example, be configured to send a sixth message with a low priority in the regular pool.

According to an embodiment, the third resource pool may be an exception pool, e.g. for providing the third plurality of resources to transmissions having a high priority. In such an embodiment, the fourth resource pool may be, for example, a conventional pool for providing the fourth plurality of resources to transmissions having a lower priority than the high priority. Further, in such embodiments, the transmitter 152 may be configured to send the second message with a high priority in the exception pool, for example. Further, in such embodiments, the transmitter 152 may be configured to send a sixth message with a low priority in the regular pool, for example.

In an embodiment, the transmitter 152 may, for example, be configured to send the first critical communication notification in the first resource pool without sensing whether the first resource pool is occupied by another transmission.

According to an embodiment, after the first transmission of the first critical communication notification, the transmitter 152 may for example be configured to retransmit the first critical communication notification one or more times in the first resource pool.

In an embodiment, in response to the receiver 154 receiving the second critical communication notification, the transmitter 152 may, for example, be configured to send a third message to one or more other user equipments (not shown in fig. 1), wherein the third message may, for example, indicate that a fourth message is to be sent in the fourth resource pool.

According to an embodiment, the transmitter 152 may for example be configured to transmit the first critical communication notification at a first transmission power, wherein the transmitter 152 may for example be configured to transmit the second message at a second transmission power, wherein the first transmission power may for example be larger than the second transmission power.

In an embodiment, at least one of the first critical communication notification and the second critical communication notification may be, for example, sidelink control information comprising one or more sidelink control information data elements, wherein the sidelink control information data elements comprise at least one of a component carrier index, a subframe index, an SPS periodicity, a transmission offset, a subchannel size, and an indication indicating whether frequency hopping is allowed or not.

According to an embodiment, each of the first and second and third and fourth resource pools may for example be allocated to a plurality of component carriers, wherein the first resource pool may for example be allocated to a first component carrier of the plurality of component carriers, and wherein the second resource pool may for example be allocated to a second component carrier of the plurality of component carriers, wherein the second component carrier may for example be different from the first component carrier.

In another embodiment, each of the first and second and third and fourth resource pools may for example be allocated to a plurality of component carriers, wherein the first resource pool may for example be allocated to a first component carrier of the plurality of component carriers, and wherein the second resource pool may for example also be allocated to the first component carrier.

According to an embodiment, the user equipment is configured to be installed in a vehicle, and wherein, if the user equipment of the vehicle has an emergency request, and if the vehicle is within the coverage of a base station, the receiver 154 of the user equipment is configured to receive the subframe bitmap from the base station, and the transmitter 152 of the user equipment is configured to transmit the subframe bitmap received from the base station to another vehicle outside the coverage of the base station.

According to an embodiment, the first resource pool is located on the same component carrier as the second resource pool, or the third resource pool is located on the same component carrier as the fourth resource pool.

In another embodiment, the first resource pool is not located on the same component carrier as the second resource pool, or the third resource pool is not located on the same component carrier as the fourth resource pool.

The system comprises a plurality of

user devices

150, 250, wherein each of the plurality of

user devices

150, 250 is a user device according to one of the above embodiments. The plurality of

user devices

150, 250 includes a first user device 150 and a second user device 250.

The first resource pool includes a first plurality of resources for transmission defined by a first resource pool configuration. The second resource pool includes a second plurality of resources for transmission defined by a second pre-configuration. The second resource pool configuration is different from or equal to the first resource pool configuration.

The transmitter 152 of the first user equipment 150 is configured to transmit a critical communication notification as the first message in the first resource pool, wherein the critical communication notification indicates that the second message is to be transmitted in the second resource pool.

The receiver 254 of the second user device 250 is configured to receive a critical communication notification from the transmitter 152 of the first user device 150.

The transmitter 252 of the second user equipment 250 is configured to not send anything in the second resource pool in response to the receiver 254 of the second user equipment 250 receiving the critical communication notification.

The transmitter 152 of the first user equipment 150 is configured to send a second message in the second resource pool after or at the same time as sending the critical communication notification.

Hereinafter, specific embodiments of the present invention will be described in detail.

First, a control channel design and reservation procedure for abnormal pool notification of data in a regular pool according to an embodiment is described.

In an embodiment, the control data in the exception pool may be used to handle and reserve transmissions or retransmissions or periodic repetitions in the regular resource pool.

The concepts provided may be compared to interrupt handling in computer science to some extent with the distinction between first level and second level interrupt handlers.

The first level section corresponds to Sidelink Control Information (SCI) transmitted immediately via a preconfigured exception pool in case of an emergency. The SCI includes information about the component carriers, the subframe and/or subchannel locations of the advertised data transmission, and the repetition period/pattern of the data transmission, possibly in a semi-persistent scheduling (SPS) manner.

The second level part consists of scheduled data transmission via the normal resource pool. The scheduled data transmission may for example consist of a single transmission.

Alternatively, the scheduled data transmission may for example comprise an initial transmission followed by further retransmissions according to a predefined pattern. For example, the initial transmission may be followed by a periodic transmission. The first level of transmission may, for example, carry information about the transmission interval t_intervalAnd each transmission T_iWhere T may be defined, for example, as T × N ST _ duration.

In the current 3GPP specifications, all UEs are authorized to receive any data transmission in the abnormal pool.

Depending on the embodiment, all UEs may, for example, mute or skip their intended transmissions in case they collide with the second level partial (delayed/scheduled) data transmission.

In an embodiment, the normal (or exception) pool for data transmission opportunities after sending SCIs using the exception pool may be selected, for example, based on CBR (channel busy rate).

In an embodiment, the same or next possible subframe in the normal resource pool may be selected, for example, because the UE may be expected to have read the SCI from the abnormal control channel or from the normal resource pool. The next possible subframe may for example refer to the next subframe that all UEs can read, considering that some UEs have to retune their local oscillator to the component carrier scheduling the delayed data transmission.

SCI data elements may, for example, include one or more of the following elements:

-a Component Carrier (CC) index; for example, the same CC ID is defaulted. If ERP is in the same CC, the CC ID may not be used or set to zero. Otherwise, the different CC IDs may have any preconfigured values.

IE ServCellIndex, as defined in section 3.3.1.1 in [5], relates to short identification for identifying a serving cell (e.g., PCell or SCell). The value 0 applies to PCell, while the previously allocated ServCellIndex applies to SCell:

the ServCellIndex information element may be defined, for example, as:

--ASN

--ASN1START

ServCellIndex-r10::＝INTEGER(0..7)

ServCellIndex-r13::＝INTEGER(0..31)

--ASN1STOP

subframe index or offset of the initial data transmission after the emergency control announcement (second level (payload) transmission).

-an SPS period; in the normal resource pool and/or the abnormal/urgent pool. Therein is defined with interval t_intervalPeriod and T of_maxThe maximum transmission period of.

PRB index n for initial second level (data payload and control information) transmission (PRB ═ physical resource block)_subCHRBstartThe medium transmission offset.

-subchannel size n_subCHsizeFor a plurality of PRBs, e.g. 2 control PRBs + X data PRBs.

-a Resource Indication Value (RIV) indicating the start of resource allocation.

-whether to apply frequency hopping with an indication pattern for SPS transmissions. Alternatively, if blind detection is not possible, the pattern ID may be in the SCI information.

For pre-configured resources (unlicensed transmission) for e.g. mode 3 may be indicated with RIV, sub-channels and transmission periods/reservations.

-whether the second level transmission is a single transmission.

Once the SCI information in the anomalous resource pool (ERP) is captured by the other UEs, they may, for example, all tune to receive the advertised second level data transmission. Therefore, they must stop sending new or old data in the buffer.

In the following, Exception Pool (EP) access for data advertisement is described, according to an embodiment, wherein control information is sent in an exception pool of advertisement data in the same or a regular pool.

If a MAC (Medium access control/Medium access control) PDU is large enough, instead of transmitting the complete MAC PDU in the emergency pool, only a "pointer" to the resource carrying the MAC PDU is transmitted. The MAC PDUs themselves may be sent in the parallel sidelink regular resource pool outside the emergency pool, e.g. in the same subframe (the same subframe may e.g. be related to the same time) or on another sequential subframe (at a different time).

Fig. 6 illustrates cross-carrier scheduling via SCI transmission on an abnormal resource pool in accordance with an embodiment. In particular, FIG. 6 shows an exception pool 611 and two

resource pools

621, 622. In the exception pool 611, a first message 651 is sent as a critical communication notification. A second message 661, an announced critical communication, is sent later in the regular pool 622. Resource pool 611 may be defined, for example, as a shared resource pool or a commonly configured authorized or commonly accessed bandwidth portion or an abnormally configured pool. The resource pools 621, 622 may for example be defined as resource pools for communication or pre-configured communication resources or allocated bandwidth parts or dynamically granted resources.

Fig. 7 illustrates intra-carrier scheduling via SCI transmission on an abnormal resource pool, in accordance with an embodiment. In particular, FIG. 7 shows exception pool 711 and resource pool 721. In the exception pool 711, a first message 751 is sent as a critical communication notification. The second message 761, the announced critical communication, is sent later in the regular pool 721. Resource pool 711 can be defined, for example, as a shared resource pool or a commonly configured authorized or commonly accessed bandwidth portion or an abnormally configured pool. The resource pool 721 may be defined, for example, as a pool of resources for communication or pre-configured communication resources or allocated bandwidth portions or dynamically granted resources.

It should be noted that the resource pools depicted in fig. 6 and 7 are highly abstract. For example, the resource pool does not necessarily include contiguous subframes or adjacent control and data channels.

In [6], if the receiving UE detects a possible collision of the received announcement data transmission with its own transmission based on the SCI received via the exception pool, the receiving UE will skip/mute the transmission.

Depending on the embodiment, SCI (or any other information data muting other UEs) may also be transmitted on the control channel of the "normal" resource pool or any other possible abnormal pool or new resource pool. The original transmission may be followed by one or more retransmissions, for example. Such retransmission enhances robustness.

In the following, embodiments are described which ensure that the control information can be implemented as a single transmission or multiple transmissions, possibly with repeated cycles in the regular pool and/or the exception pool.

In some embodiments, for example, it may be advantageous to select a subchannel size sizesubchanel (currently supported > ═ 5 RBs, see [2]) as small as possible to accommodate the minimum payload size of each transmission/subchannel to avoid collisions with other UEs as much as possible. The subchannel size may refer to, for example, the total number of PRBs used for data signal transmission and control signal transmission.

In some embodiments, for example, if only SCI control data is transmitted, it may be advantageous to use only 2 PRBs (in the frequency domain) for burst transmission. However, the minimum allocated bandwidth, 1 subchannel, consists of 5 PRBs. This means that 3 RBs are not used yet: 5-2 ═ 3 PRBs (according to the current specification). These unused RBs will be under SCI transfer in the exception pool. The data PRBs may be used, for example, to carry repeated SCIs, possibly scrambled to enhance robustness. The data PRBs may for example be used to carry information to enhance the decoding probability of the second level data transmission, e.g. (redundancy) bits/Redundancy Version (RV) derived from the channel coded output of the second level transmission.

In some embodiments, the SCI may alternatively or additionally also be repeated in the control channel, for example, if emergency data is to be transmitted.

Fig. 8 illustrates SPS repetition and SCI redundancy, in accordance with an embodiment. In particular, FIG. 8 shows an exception pool 811 and a (regular) resource pool 821. In the exception pool 811, a first message 851 is sent as a critical communication notification. First message 851 advertises

messages

861, 862, 863, 864 and 865. Advertised

key messages

861, 862, 863, 864 and 865 are sent later in the (regular) resource pool 821. Further, the first message 851 is repeated as message 853 to advertise at least the remaining

critical messages

863, 864 and 865. Resource pool 811 can be defined, for example, as a shared resource pool or a commonly configured authorized or commonly accessed bandwidth portion or an abnormally configured pool. The resource pool 821 may be defined, for example, as a pool of resources for communication or pre-configured communication resources or allocated bandwidth portions or dynamically granted resources.

Three or more resources may be filled with data, for example, in a first transmission. Multiple transmissions of the psch (physical side link shared channel) (with or without control) may be repeated in successive sub-frames, e.g. with a repetition period T. Some of the transmitted pschs may for example comprise data (the same emergency SCI is repeated as previously described) and/or some of the transmitted pschs may for example be only emergency data pschs (see fig. 8). Some of the transmitted pschs may, for example, include different versions of data, the same data, or different redundancy versions of emergency data. Alternatively or additionally, the originally sent UE-vehicle or forwarding UE-vehicle may simply repeat the SCI in the exception pool (see fig. 8), e.g., after a transmission period Tp 3.

FIG. 9 illustrates SPS data under control information repeated in an exception pool and a normal pool, in accordance with an embodiment. In particular, FIG. 9 shows exception pool 911 and regular resources pool 921. In exception pool 911, a first message 951 is sent as a critical communication notification. The first message 951 advertises

messages

961, 962, 963, and 964. The advertised

critical messages

961, 962, 963 and 964 are sent later in the (regular) resource pool 921. In addition, the first message 951 is repeated as message 953 to announce at least the remaining

critical messages

963 and 964. Then, in the exception pool 911, another message 955 is sent as a critical communication notification, which announces a message 965, wherein the announced message 965 is sent later in the regular resource pool 921. Resource pool 911 may be defined, for example, as a shared resource pool or a commonly configured authorized or commonly accessed bandwidth portion or an abnormally configured pool. The resource pool 921 may be defined, for example, as a pool of resources for communication or pre-configured communication resources or allocated bandwidth portions or dynamically granted resources.

Depending on the embodiment, the data psch may also be transmitted with a possible repetition period Tp, for example in an exception pool. SCI contains resources in both the regular pool and the exception pool (see fig. 9).

In the following, embodiments are described for prioritizing the transmission of emergency data when within a time window is reached before regular data transmission.

The operation of emergency control and existing data transmission in an emergency start vehicle according to an embodiment may be performed, for example, as follows.

If the vehicle already has packets to send after the period Δ T1 and another emergency trigger announcement arrives in the same vehicle before the minimum possible channel access threshold Δ T2, the vehicle UE must prioritize the transmission of the emergency signal and announcement (through the SCI on the abnormal resource pool).

The transmission of the emergency SCI (in the exception pool) and the associated emergency data psch (with or without a copy of the SCI) may be transmitted in the same subframe or two consecutive subframes, for example as described previously. Non-critical data transmissions may, for example, be muted until the emergency is over or deferred until a later sub-frame.

For the same Component Carrier (CC) scheduling, emergency data and non-emergency data may coexist on different (offset) subframes with different transmission periodicity (if SPS transmission is configured).

Fig. 10 illustrates same Component Carrier (CC) scheduling for emergency data and normal data according to an embodiment. In particular, FIG. 10 shows an exception pool 1011 and two resource pools 1021. In the exception pool 1011, a first message 1051 is sent as a critical communication notification. The first message 1051 announces

messages

1061, 1062, 1063, and 1064. The advertised

key messages

1061, 1062, 1063, and 1064 are sent later in the (regular) resource pool 1021. In addition, the first message 1051 is repeated as message 1054 to announce at least the remaining

critical messages

1063 and 1064.

In some embodiments, upon receiving the first message 1051, the user equipment stops sending

other messages

1071, 1072, and 1073 in the regular pool 1021 so that the advertised

messages

1061, 1062, 1063, and 1064 will not be interfered with by

other messages

1071, 1072, and 1073.

In some embodiments, upon receiving the first message 1051, the user device will not transmit

other messages

1071, 1072, and 1073 scheduled to be transmitted in the regular pool 1021, such that the announced

messages

1061, 1062, 1063, and 1064 will not be interfered with by

other messages

1071, 1072, and 1073 scheduled to be transmitted.

For different Component Carrier (CC) scheduling, emergency data and non-emergency data may coexist on different CCs on the same (or offset) subframe with the same transmission periodicity or different transmission periodicities (if SPS transmission is configured).

Fig. 11a illustrates different Component Carrier (CC) scheduling for emergency data and regular data according to an embodiment. In particular, FIG. 11a shows an exception pool 1111 and two

resource pools

1121, 1122. In the exception pool 1111, a first message 1151 is sent as a critical communication notification. The first message 1151 advertises the

messages

1161, 1162, 1163, and 1164 having high priority. The advertised

critical messages

1161, 1162, 1163, and 1164 are sent later in the (regular) resource pool 1121. In addition, the first message 1151 is repeated as message 1154 to advertise at least the remaining

critical messages

1163 and 1164.

Other messages

1171, 1172, 1173, 1174 having a low priority are sent in another regular resource pool 1122.

Other messages

1171, 1172, 1173, 1174 having a low priority may be sent, for example, at a lower power than the advertised

critical messages

1161, 1162, 1163, 1164 having a high priority.

The transmission of the emergency signal may have a priority Pri1 and a transmission power Pow1, and the transmission of the normal data may have a priority Pri2 and a transmission power Pow 2. Herein, Pri1> Pri2 and Pow1> -Pow 2.

Fig. 11b illustrates different component carrier scheduling for emergency data and normal data according to another embodiment. In exception pool 1111, a first message 1156 is sent as a critical communication notification. The first message 1156 advertises a message 1166 having a high priority. The advertised critical message 1166 is sent later in the exception resource pool 1111. Further, in the exception pool 1111, another message 1157 is transmitted as a critical communication notification. The further message 1157 advertises a message 1167 having a high priority. The advertised critical message 1167 is sent later in the exception resource pool 1111.

Other messages

1176 and 1177 with low priority are sent in the regular resource pool 1121.

Other messages

1176 and 1177 with low priority may be sent, for example, at a lower power than the advertised

critical messages

1166 and 1167 with high priority.

In the following, arranging sidelink access band transmission to communicate emergency messages to a larger number of users according to embodiments is described. In particular, access over different frequency bands with different transmission powers and bandwidths is described.

To access the channel for emergency notification, the vehicle-UE may, for example, perform a series of accesses/attempts to acquire the channel for emergency transmission to other vehicles. By this, the opportunity to receive urgent data and control should increase.

The emergency pool access procedure according to an embodiment may for example be as follows:

● in case of emergency, if the vehicle is able to connect to multiple frequency bands, e.g. with or without multiple TX/RX chains:

o first, after the emergency packet arrives

■ start from a dedicated frequency band (<6GHz, e.g., the ITS band around 5.9 GHz) and start an emergency transmission procedure

o if otherwise band transmission is not allowed or not sufficient (after a short waiting period Ts)

■ switch to a lower frequency (<6GHz) sidelink band on a configured or preconfigured bitmap and begin an emergency transmission procedure

■ switch to the higher frequency (mmWave) ITS band (63GHz) and begin the emergency transmission procedure

■ switch to a higher frequency (mmWave) licensed band on a configured or preconfigured bitmap and begin an emergency transmission procedure

o otherwise end the procedure

(mmWave ═ millimeter wave)

(ITS is intelligent traffic system)

In the following, embodiments are described for broadcasting a bitmap from a covered UE to an uncovered (autonomous) vehicle in emergency control information. In particular, the preconfigured legend may be selectable, for example, to reduce the number of bitmap broadcast bits in the Sidelink Control Information (SCI).

Fig. 12 illustrates a side link subframe configuration that is forwarded out of coverage for emergency monitoring, according to an embodiment.

In the following, consider the PSCCH subframe and the pool of resource blocks.

If the vehicle processes the emergency request and is within coverage, the bitmap must be sent out of coverage. This process is performed to force all out-of-coverage vehicles to be adjusted to monitor for emergency data. The bitmap may be sent, for example, via SCI emergency control information.

As in existing systems, the bitmap is configured according to a periodic (pre-configured) pattern, called bitmap (subframe bitmap-r 12 is introduced in the SL-FR-ResourceConfig field in section [5] 6.3.8). The length of the sub-frame bitmap r12 is 40 bits. These 40 bits may be transmitted, for example, over Uu to convey an index T RPT indicating the bitmap sequence used.

Similarly, the sub-frame bitmap-r 12 must be forwarded to the out-of-coverage vehicle to allow the remote UE to monitor for emergency notifications and data transmissions on the scheduled resource (see fig. 12 for more details). To reduce data transmission on SCI (through the exception pool), the subframe bitmap-r 12 may be remapped to a shorter emergency pool, for example, by designing a smaller bitmap table or by fixing the emergency notification bitmap (e.g., with a shorter index bit number), for example.

Although some aspects of the described concepts have been described in the context of an apparatus, it is clear that these aspects also represent a description of a corresponding method, where a block or device corresponds to a method step or a feature of a method step. Similarly, aspects described in the context of method steps also represent a description of the respective block or item or a feature of the respective apparatus.

The various elements and features of the invention may be implemented in hardware (using analog and/or digital circuitry), in software (via the execution of instructions by one or more general-purpose or special-purpose processors), or as a combination of hardware and software. For example, embodiments of the invention may be implemented in the context of a computer system or another processing system.

FIG. 5 illustrates an example of a computer system 500 according to an embodiment. The units or modules and the steps of the methods performed by the units may be performed on one or more computer systems 500. The computer system 500 includes one or more processors 502, such as a special purpose or general purpose digital signal processor. The processor 502 is connected to a communication infrastructure 504, such as a bus or network. Computer system 500 includes a main memory 506, such as Random Access Memory (RAM), and a secondary memory 508, such as a hard disk drive and/or a removable storage drive. Secondary memory 508 may allow computer programs or other instructions to be loaded into computer system 500. Computer system 500 may also include a communications interface 510 to allow software and data to be transferred between computer system 500 and external devices. Communications may be in the form of electronic, electromagnetic, optical, or other signals capable of being processed by the communications interface. The communication may use wires or cables, fiber optics, a phone line, a cellular phone link, an RF link, and other communication channels 512.

The terms "computer program medium" and "computer-readable medium" are used to generally refer to tangible storage media such as removable storage units or hard disks installed in hard disk drives. These computer program products are means for providing software to computer system 500. Computer programs (also called computer control logic) are stored in main memory 506 and/or secondary memory 508. Computer programs may also be received via communications interface 510. The computer programs, when executed, enable the computer system 500 to implement the present invention. In particular, the computer programs, when executed, enable the processor 502 to implement the processes of the present invention, e.g., any of the methods described herein. Accordingly, such computer programs may represent controllers of computer system 500. Where the disclosure is implemented using software, the software may be stored in a computer program product and loaded into computer system 500 using a removable storage drive, an interface, such as communications interface 510.

Implementations in hardware or software may be performed using a digital storage medium such as: cloud storage, floppy disk, DVD, blu-ray, CD, ROM, PROM, EPROM, EEPROM or flash memory, on which electronically readable control signals are stored, which cooperate (or are capable of cooperating) with a programmable computer system such that the respective method is performed. Accordingly, the digital storage medium may be computer-readable.

Some embodiments according to the invention comprise a data carrier with electronically readable control signals capable of cooperating with a programmable computer system such that one of the methods described herein is performed.

In general, embodiments of the invention can be implemented as a computer program product having a program code operable to perform one of the methods when the computer program product runs on a computer. The program code may be stored, for example, on a machine-readable carrier.

Other embodiments include a computer program stored on a machine-readable carrier for performing one of the methods described herein. In other words, an embodiment of the inventive methods is thus a computer program with a program code for performing one of the methods described herein, when the computer program runs on a computer.

Thus, a further embodiment of the inventive method is a data carrier (or digital storage medium, or computer readable medium) comprising a computer program recorded thereon for performing one of the methods described herein. Thus, a further embodiment of the inventive method is a data stream or a signal sequence representing a computer program for performing one of the methods described herein. The data stream or the signal sequence may for example be configured to be transmitted via a data communication connection, for example via the internet. Further embodiments include a processing device, such as a computer or programmable logic device, configured or adapted to perform one of the methods described herein. Further embodiments include a computer having installed thereon a computer program for performing one of the methods described herein.

In some implementations, a programmable logic device (e.g., a field programmable gate array) may be used to perform some or all of the functions of the methods described herein. In some embodiments, a field programmable gate array may cooperate with a microprocessor to perform one of the methods described herein. In general, the method is preferably performed by any hardware device.

The above-described embodiments are merely illustrative of the principles of the present invention. It is to be understood that modifications and variations of the arrangements and details described herein will be apparent to others skilled in the art. It is the intention, therefore, to be limited only by the scope of the appended patent claims and not by the specific details presented by way of description and illustration of the embodiments herein.

Abbreviations:

abbreviations: the meaning is as follows:

BS: base station

CBR: channel busy rate

D2D: device to device

EN: emergency notifications (example for Critical communication notifications)

eNB: evolved Node B (base station)

FDM: frequency division multiplexing

LTE: long term evolution

PC 5: interface for D2D communication using sidelink channel

PPPP: ProSe per packet priority

PPPR: ProSe per packet reliability

PRB: physical resource block

And (3) ProSe: proximity services

RA: resource allocation

SCI: side link control information

SL: side link

sTTI: short transmission time interval

TDM: time division multiplexing

TDMA: time division multiple access

UE: user entity (user terminal)

URLLC: ultra-reliable low latency communication

V2V: vehicle-to-vehicle

V2I: vehicle-to-infrastructure

V2P: vehicle-to-pedestrian

V2N: vehicle-to-network

V2X: vehicle to everything, e.g. V2V, V2I, V2P, V2N

Reference documents:

[1]3GPP TS 36.213Evolved Universal Terrestrial Radio Access(E-UTRA)；Physical layer procedures；V14.5.0

[2]TS 36.331Evolved Universal Terrestrial Radio Access(E-UTRA)-Radio Resource Control(RRC)；V14.

[3]3GPP TS 36.211Evolved Universal Terrestrial Radio Access(E-UTRA)；Physical Channels and Modulation,v 14.3.0

[4]3GPP TS 36.212Evolved Universal Terrestrial Radio Access(E-UTRA)；Multiplexing and channel coding,v 14.3.0

[5]3GPP TS 36.321Evolved Universal Terrestrial Radio Access(E-UTRA)；Medium Access Control(MAC)protocol specification,v 14.3.0

[6]2017P59629 EP:Emergency Notification(URLLC)Requesting Spontaneous Grant Free Transmission for V2X

[7]NGMN Alliance AWhite Paper“Small Cell Backhaul Requirements”,Version 1.0,June 4,2012

Claims

1. a user equipment for wireless communication, wherein the user equipment comprises:

a transmitter (152; 252) and

a receiver (154; 254),

wherein a first resource pool (611; 711; 811; 911; 1011; 1111) defined by a first resource pool configuration comprises a first plurality of resources for transmission, and wherein a second resource pool (622; 721; 821; 921; 1021; 1121) defined by a second resource pool configuration comprises a second plurality of resources for transmission, wherein the second resource pool configuration is different from or equal to the first resource pool configuration,

wherein the transmitter (152; 252) of the user equipment is configured to send a first critical communication notification as a first message (651; 751; 851, 853; 951, 953, 955; 1051, 1054; 1151, 1154; 1156, 1157) in the first resource pool (611; 711; 811; 911; 1011; 1111), wherein the first critical communication notification indicates that a second message is to be sent in the second resource pool (622; 721; 821; 921; 1021; 1121),

wherein the transmitter (152; 252) of the user equipment is configured to send the second message (661; 761; 861, 862, 863, 864, 865; 961, 962, 963, 964, 965; 1061, 1062, 1063, 1064; 1161, 1162, 1163, 1164; 1166, 1167) in the second resource pool (622; 761; 861; 862; 1021; 1121) after or simultaneously with sending the first critical communication notification,

wherein a third resource pool (611; 711; 811; 911; 1011; 1111) defined by a third resource pool configuration comprises a third plurality of resources for transmission, and wherein a fourth resource pool (622; 721; 821; 921; 1021; 1121) defined by a fourth resource pool configuration comprises a fourth plurality of resources for transmission, wherein the fourth resource pool configuration is different from or equal to the third resource pool configuration,

wherein the receiver (154; 254) of the user equipment is configured to receive a second critical communication notification as a third message (651; 751; 851, 853; 951, 953, 955; 1051, 1054; 1151, 1154; 1156, 1157), the second critical communication notification being sent in the third resource pool (611; 711; 811; 911; 1011; 1111), wherein the second critical communication notification indicates a fourth message (661; 761; 861, 862, 863, 864, 865; 961, 962, 963, 964, 965; 1061, 1062, 1063, 1064; 1, 1162, 1163, 1164; 1166, 1167) to be sent in the fourth resource pool (622; 721; 821; 921; 1021; 1121), and

wherein the transmitter (152; 252) of the user equipment is configured to not send anything in the fourth resource pool (622; 721; 821; 921; 1021; 1121) in response to the receiver (154; 254) receiving the second critical communication notification.

2. The user equipment according to claim 1, wherein the user equipment,

wherein the first resource pool is defined as a shared resource pool or a commonly configured granted or commonly accessed bandwidth portion or an abnormally configured pool, and/or

Wherein the third resource pool is defined as a shared resource pool or a commonly configured granted or commonly accessed bandwidth portion or an abnormally configured pool.

3. The user equipment of claim 1 or 2,

wherein the second resource pool is defined as a resource pool for communication or a pre-configured communication resource or an allocated bandwidth part or a dynamically granted resource, and/or

Wherein the fourth resource pool is defined as a resource pool for communication or a pre-configured communication resource or an allocated bandwidth portion or a dynamically granted resource.

4. The user equipment according to one of the preceding claims,

wherein the first message includes a pointer to the second message in the second resource pool, the pointer defining one or more frequency locations and time locations of the second message; or wherein the first message comprises a pointer to the second message in the second resource pool, the pointer defining one or more frequency and time positions and a repetition period of the second message; and/or

Wherein the third message comprises a pointer to the fourth message in the fourth resource pool, the pointer defining one or more frequency locations and time locations of the fourth message; or wherein the third message comprises a pointer to the fourth message in the fourth resource pool, the pointer defining one or more frequency and time locations and a repetition period of the fourth message.

5. The user equipment according to one of the preceding claims,

wherein the first resource pool (611; 711; 811; 911; 1011; 1111) comprises a first plurality of preconfigured resources for side link transmission, wherein the second resource pool (622; 721; 821; 921; 1021; 1121) comprises a second plurality of resources for side link transmission, wherein the third resource pool (611; 711; 811; 911; 1011; 1111) comprises a third plurality of resources for side link transmission, and wherein the fourth resource pool (622; 721; 821; 921; 1021; 1121) comprises a fourth plurality of resources for side link transmission.

6. The user equipment according to one of the preceding claims,

wherein the transmitter (152; 252) is configured to send a first critical communication notification in the first resource pool (611; 711; 811; 911; 1011; 1111) in a first time slot, and

wherein the transmitter (152; 252) is configured to send the second message (661; 761; 861, 862, 863, 864, 865; 961, 962, 963, 964, 965; 1061, 1062, 1063, 1064; 1161, 1162, 1163, 1164; 1166, 1167) in the second resource pool (622; 721; 821; 921; 1021; 1121) in a second time slot after sending the first critical communication notification, the second time slot being a delayed time slot with respect to the first time slot.

7. The user equipment according to one of claims 1 to 5,

wherein the transmitter (152; 252) is configured to send the second message (661; 761; 861, 862, 863, 864, 865; 961, 962, 963, 964, 965; 1061, 1062, 1063, 1064; 1161, 1162, 1163, 1164; 1166, 1167) in the second resource pool (622; 761; 861, 862, 863, 864, 865; 961, 962, 963, 964; 1021, 1062, 1063, 1064) at the same time slot when the first critical communication notification is sent or at a subsequent time slot after the first critical communication notification is sent.

8. The user equipment according to one of the preceding claims,

wherein the transmitter (152; 252) is configured to transmit the first critical communication notification comprising an indication of resources of the second plurality of resources for transmission of transmissions for the second resource pool (622; 721; 821; 921; 1021; 1121), wherein the transmitter (152; 252) is configured to transmit the second message (661; 761; 861, 862, 863, 864, 865; 961, 962, 963, 964, 965; 1061, 1062, 1063, 1064; 1161, 1162, 1163, 1164; 1166, 1167) in the resources for transmission indicated by the indication, wherein the indication comprises a pointer to the resources for transmission or comprises a subframe indication indicating a subframe or comprises a frequency indication indicating a frequency or comprises a component carrier indication indicating a component carrier.

9. The user equipment according to one of the preceding claims,

wherein the transmitter (152; 252) is configured to stop sending a fifth message (1071, 1072, 1073) in the fourth resource pool (1021) in response to the receiver (154; 254) receiving the second critical communication notification.

10. The user equipment according to one of claims 1 to 8,

wherein a fifth message (1071, 1072, 1073) is scheduled for transmission in the fourth resource pool (1021),

wherein the transmitter (152; 252) is configured to not send the fifth message in the fourth resource pool (1021) in response to the receiver (154; 254) receiving the second critical communication notification.

11. The user equipment according to one of the preceding claims,

wherein the first resource pool (1111) is an exception pool for providing the first plurality of resources to transmissions having a high priority, the exception pool being a shared pool or a grant of configuration in full bandwidth, sub-bandwidth or bandwidth part,

wherein the second resource pool (1121) is a regular pool for providing the second plurality of resources to transmissions having a priority lower than a high priority,

wherein the transmitter (152; 252) is configured to send a second message (1166, 1167) having a high priority in the exception pool, which is a grant of a configuration in a shared pool or a full bandwidth, sub-bandwidth or bandwidth part,

wherein the transmitter (152; 252) is configured to send a sixth message (1171, 1176, 1177) having a low priority in the regular pool.

12. The user equipment according to one of claims 1 to 10,

wherein the third resource pool (1111) is an exception pool for providing the third plurality of resources to transmissions having a high priority,

wherein the fourth resource pool (1121) is a regular pool for providing the fourth plurality of resources to transmissions having a priority lower than a high priority,

wherein the transmitter (152; 252) is configured to send a fourth message (1166, 1167) having a high priority in the exception pool,

wherein the transmitter (152; 252) is configured to send a sixth message (1176, 1177) having a low priority in the regular pool.

13. The user equipment according to one of the preceding claims,

wherein the transmitter (152; 252) is configured to send the first critical communication notification in the first resource pool (611; 711; 811; 911; 1011; 1111) without sensing whether the first resource pool (611; 711; 811; 911; 1011; 1111) is occupied by another transmission.

14. The user equipment according to one of the preceding claims,

wherein, after the first transmission of the first critical communication notification, the transmitter (152; 252) is configured to retransmit the first critical communication notification one or more times in the first resource pool (611; 711; 811; 911; 1011; 1111).

15. The user equipment according to one of the preceding claims,

wherein, in response to the receiver (154; 254) receiving the second critical communication notification, the transmitter (152; 252) is configured to send the third message (651; 751; 851, 853; 951, 953, 955; 1051, 1054; 1151, 1154; 1156, 1157) to one or more other user devices, wherein the third message (651; 751; 851, 853; 951, 953, 955; 1051, 1054; 1151, 1154; 1156, 1157) indicates that the fourth message (651; 761; 861, 862, 863, 864, 865; 961, 962, 963, 964, 965; 1061, 1062, 1063, 1064; 1161, 1162, 1163, 1164; 1166, 1167) is to be sent in the fourth resource pool (622; 821; 721; 921; 1021; 1121).

16. The user equipment according to one of the preceding claims,

wherein the transmitter (152; 252) is configured to transmit the first critical communication notification at a first transmission power, wherein the transmitter (152; 252) is configured to transmit the second message (661; 761; 861, 862, 863, 864, 865; 961, 962, 963, 964, 965; 1061, 1062, 1063, 1064; 1161, 1162, 1163, 1164; 1166, 1167) at a second transmission power, wherein the first transmission power is greater than the second transmission power.

17. The user equipment according to one of the preceding claims,

wherein at least one of the first critical communication notification and the second critical communication notification is sidelink control information comprising one or more sidelink control information data elements, wherein the sidelink control information data elements comprise at least one of a component carrier index, a subframe index, an SPS periodicity, a transmission offset, a subchannel size, and an indication indicating whether frequency hopping is allowed or not.

18. The user equipment according to one of the preceding claims,

wherein each of the first resource pool (611; 711; 811; 911; 1011; 1111) and the second resource pool (622; 721; 821; 921; 1021; 1121) and the third resource pool (611; 711; 811; 911; 1011; 1111) and the fourth resource pool (622; 721; 821; 921; 1021; 1121) is allocated to a plurality of component carriers,

wherein the first resource pool (611; 711; 811; 911; 1011; 1111) is allocated to a first component carrier of the plurality of component carriers and

wherein the second resource pool (622; 721; 821; 921; 1021; 1121) is allocated to a second component carrier of the plurality of component carriers, wherein the second component carrier is different from the first component carrier.

19. The user equipment according to one of claims 1 to 17,

wherein the second resource pool (622; 721; 821; 921; 1021; 1121) is also allocated to the first component carrier.

20. The user equipment according to one of the preceding claims,

wherein the user equipment is configured to be installed in a vehicle, an

Wherein, if the user equipment of the vehicle has an emergency request and if the vehicle is within the coverage of a base station, the receiver (154; 254) of the user equipment is configured to receive a subframe bitmap from the base station and the transmitter (152; 252) of the user equipment is configured to transmit the subframe bitmap received from the base station to another vehicle outside the coverage of the base station.

21. The user equipment according to one of the preceding claims,

wherein the first resource pool is located on the same component carrier as the second resource pool, or

Wherein the third resource pool is located on the same component carrier as the fourth resource pool.

22. The user equipment according to one of claims 1 to 20,

wherein the first resource pool is not located on the same component carrier as the second resource pool, or

Wherein the third resource pool is not located on the same component carrier as the fourth resource pool.

23. A system for use in wireless communications is provided,

wherein the system comprises a plurality of user equipments (150, 250), wherein each of the plurality of user equipments (150, 250) is a user equipment according to one of the preceding claims,

wherein the plurality of user equipments (150, 250) comprises a first user equipment (150) and a second user equipment (250),

wherein the first resource pool (611; 711; 811; 911; 1011; 1111) comprises a first plurality of resources for transmission and wherein the second resource pool (622; 721; 821; 921; 1021; 1121) comprises a second plurality of resources for transmission, wherein the second resource pool configuration is different from or equal to the first resource pool configuration,

wherein the transmitter (152) of the first user equipment (150) is configured to send a critical communication notification as a first message (651; 751; 851, 853; 951, 953, 955; 1051, 1054; 1151, 1154; 1156, 1157) in the first resource pool (611; 711; 811; 911; 1011; 1111), wherein the critical communication notification indicates that a second message (661; 761; 861, 862, 863, 864, 865; 961, 962, 963, 964, 965; 1061, 1062, 1063, 1064; 1161, 1162, 1163, 1164; 1166, 1167) is to be sent in the second resource pool (622; 821; 721; 921; 1021; 1121),

wherein the receiver (254) of the second user equipment (250) is configured to receive the critical communication notification from the transmitter (152) of the first user equipment (150),

wherein the transmitter (252) of the second user equipment (250) is configured to not send anything in the second resource pool (622; 721; 821; 921; 1021; 1121) in response to the receiver (254) of the second user equipment (250) receiving the critical communication notification,

wherein the transmitter (152) of the first user equipment (150) is configured to send the second message (661; 761; 861, 862, 863, 864, 865; 961, 962, 963, 964, 965; 1061, 1062, 1063, 1064; 1161, 1162, 1163, 1164; 1166, 1167) in the second resource pool (622, 721; 821; 921; 1021; 1121) after or at the same time as sending the critical communication notification.

24. A method for wireless communication, wherein a first resource pool (611; 711; 811; 911; 1011; 1111) defined by a first resource pool configuration comprises a first plurality of resources for transmission, and wherein a second resource pool (622; 721; 821; 921; 1021; 1121) defined by a second resource pool configuration comprises a second plurality of resources for transmission, wherein the second resource pool configuration is different from or equal to the first resource pool configuration, wherein a third resource pool (611; 711; 811; 911; 1011; 1111) defined by a third resource pool configuration comprises a third plurality of resources for transmission, and wherein a fourth resource pool (622; 721; 821; 921; 1021) defined by a fourth resource pool configuration comprises a fourth plurality of resources for transmission, wherein the fourth resource pool configuration is different from or equal to the third resource pool configuration, wherein the method comprises the following steps:

sending, by a transmitter (152; 252) of a user equipment, a first critical communication notification as a first message (651; 751; 851, 853; 951, 953, 955; 1051, 1054; 1151, 1154; 1156, 1157) in the first resource pool (611; 711; 811; 911; 1011; 1111), wherein the first critical communication notification indicates a second message (661; 761; 861, 862, 863, 864, 865; 961, 962, 963, 964, 965; 1061, 1062, 1063, 1064; 1161, 1162, 1163, 1164; 1166, 1167) to be sent in the second resource pool (622; 721; 821; 921; 1021; 1121),

sending, by the transmitter (152; 252), the second message (661; 761; 861, 862, 863, 864, 865; 961, 962, 963, 964, 965; 1061, 1062, 1063, 1064; 1161, 1162, 1163, 1164; 1166, 1167) in the second resource pool (622; 721; 821; 921; 1021; 1121) after or simultaneously with sending the first critical communication notification,

receiving a second critical communication notification as a third message (651; 751; 851, 853; 951, 953, 955; 1051, 1054; 1151, 1154; 1156, 1157), the second critical communication notification being sent in the third resource pool (611; 711; 811; 911; 1011; 1111) by a receiver (154; 254) of the user equipment, wherein the second critical communication notification indicates that a fourth message (661; 761; 861, 862, 863, 864, 865; 961, 962, 963, 964, 965; 1061, 1062, 1063, 1064; 1161, 1162, 1163, 1164; 1166, 1167) is to be sent in the fourth resource pool (622; 721; 821; 921; 1021; 1121), and

in response to the receiver (154; 254) receiving the second critical communication notification, the transmitter (152; 252) does not send anything in the fourth resource pool (622; 721; 821; 921; 1021; 1121).

25. A computer program for implementing the method according to claim 24 when executed on a computer or signal processor.