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

By defining multiple resource pools in wireless communication and dynamically adjusting resource usage, the problems of high latency and low reliability of emergency notification and high QoS priority data transmission in wireless communication are solved, and emergency messages with low latency and high reliability are achieved transmission.

CN112640546BActive Publication Date: 2024-12-03KONINKLIJKE PHILIPS NV
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN201980057292.3
Authority / Receiving Office
CN · China
Patent Type
Patents(China)
Current Assignee / Owner
Priority Date
2018-08-10
Filing Date
2019-08-08
Publication Date
2024-12-03
Estimated Expiration
2039-08-08

AI Technical Summary

Technical Problem

In wireless communications, especially in V2X and D2D communications, the emergency notification and high QoS priority URLLC data transmission has problems of high latency and low reliability, especially in abnormal situations such as radio link failures. It is difficult to achieve low latency and high reliability communication.

Method used

By defining multiple resource pools, including the first resource pool and the second resource pool, the user equipment uses different resource pools to transmit messages when sending emergency notifications, and dynamically adjusts resource usage after receiving the corresponding notifications to ensure that High reliability and low latency transmission of emergency messages. Specific measures include sending a critical communication notification in the first resource pool, instructing the sending of a second message in the second resource pool, and avoiding sending any content in the fourth resource pool after receiving the corresponding notification, in order to prioritize the use of the exception pool or Resources of regular pools.

Benefits of technology

Real-time resource pool access in emergencies is achieved, ensuring low latency and high reliability transmission of high-priority data, reducing sensing cycles, improving communication reliability and efficiency, and avoiding resource congestion and conflicts.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN112640546B_ABST
    Figure CN112640546B_ABST
Patent Text Reader

Abstract

A user device for wireless communication is provided. The user device includes a transmitter (152) and a receiver (154). A first resource pool includes a first plurality of resources for transmission. A 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 send 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 sent in the second resource pool. In addition, the transmitter (152) is configured to send a second message in the second resource pool after sending the first critical communication notification or while sending the first critical communication notification. A third resource pool includes a third plurality of resources for transmission. A 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 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.
Need to check novelty before this filing date? Find Prior Art

Description

[0001] The present invention relates to the field of wireless communication networks and more specifically to concepts for transmitting data in wireless communication networks. In particular, the present invention relates to user equipment and methods with improved critical communications in wireless communication. Critical communications may for example be emergency notifications, for example in V2X (Vehicle to Everything) or D2D (Device to Device), or may for example involve other types of communications requiring very low latency and / or high reliability.

[0002] In mobile communications, different entities can communicate with each other. For example, some possible communications between different entities can be classified into 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 can be transmitted in the same subframe or in different / subsequent subframes.

[0003] Typically, the communication takes place using an uplink, e.g. from a user equipment (UE = User Equipment / User Entity) to a base station, or using a downlink, e.g. from a base station to the user equipment. The base station may be, e.g., any kind of NodeB, e.g., an eNB (evolved Node B). Sidelink transmissions, e.g., between two user equipments, without a link to a base station are a relatively new concept that is becoming increasingly important.

[0004] Detailed information on V2X, V2V, D2D (device-to-device) and sidelink can be found, for example, in [1], [3], [4]. Information on ungranted transmissions in the sidelink (transmission modes 2 and 4, D2D), i.e. pre-configured resources, can be found, for example, in [2] and [5]. According to [1], the UE shall randomly select a cyclic shift n in {0, 3, 6, 9} in each Physical Sidelink Control Channel (PSCCH) transmission. cs,λ .

[0005] The current V2X specification of 3GPP (3rd Generation Partnership Project) in Long Term Evolution (LIE) supports two modes, Mode 3 and Mode 4. In 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).

[0006] In Mode 3, resource provisioning is done via a base station. A user equipment (UE) connects to a base station that supports V2X operations and obtains its resources from the base station.

[0007] Mode 4 is an autonomous mode with distributed scheduling. The UE is required to detect the appropriate resources by itself. Currently, in Mode 4, a one-second sensing operation is required before any resources are used for transmission.

[0008] The concept of emergency pool includes the existence of special resource pools, special resource configurations, special resource pool configurations, special (common) bandwidth parts (BWP) that can be used for very limited purposes, such as during handover / radio link failure (RLF) by UEs that do not have dedicated granted resources-grants for transmission. In this case, these configured / preconfigured resources are called shared resource pools or shared / commonly configured grants or common bandwidth parts (BWP), i.e., they can also be conventional exception pools for V2X, normal shared pools or configured grants in full bandwidth, sub-bandwidth or bandwidth parts (BWP).

[0009] In V2X, a shared resource pool, common configured resources or common BWP for sidelink (SL) communication is primarily defined to communicate in exceptional situations, whenever resources cannot be configured / preconfigured (e.g., during radio link failure, during switching a user equipment from connected to idle, when sensing results are not available, or during handover). This is valid for both scheduling modes: network controlled grant-based resource selection in mode 3 and autonomous resource selection in mode 4. In LTE (Long Term Evolution) Release 15, exceptional resource pools (shared resource pools or shared / commonly configured grants or common bandwidth parts (BWPs)) are only accessible with random resource selection.

[0010] Therefore, 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 immediately during the exception situation to avoid any congestion in the exception pool. The transmission of large PDCP (Packet Data Convergence Protocol) PDUs (Protocol Data Units) over the sidelink in the exception pool is not supported to allow opening resources for other UEs and avoid higher collision probability.

[0011] For example, an exception pool is a resource pool including multiple resources for transmission, an authorized or common bandwidth portion (BWP) of a shared resource pool or a shared / common configuration, and also a traditional exception pool.

[0012] In [6], a request for autonomous unauthorized transmission for V2X for mission-critical and emergency notifications is described (e.g., can be used for ultra-reliable low-latency communication, URLLC, packets with high Quality of Service (QoS) flows and requirements).

[0013] To ensure successful emergency notification (Emergency Notification = EN) for V2X, low latency and high reliability are mandatory.

[0014] Therefore, it would be highly appreciated if improved concepts for emergency notification could be provided.

[0015] The object of the present invention is to provide an improved concept for emergency notification and high QoS priority URLLC data transmission in wireless communication. The object of the present 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.

[0016] A user equipment for wireless communication is provided. The user equipment includes a transmitter and a receiver. A first resource pool defined by a first resource pool configuration includes a first plurality of resources for transmission. A second resource pool defined by a 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 send a first critical communication notification as a first message in the first resource pool, wherein the first critical communication notification indicates that the second message is to be sent in the second resource pool. In addition, the transmitter is configured to send a second message in the second resource pool after sending the first critical communication notification or while sending the first critical communication notification. A third resource pool defined by a third resource pool configuration includes a third plurality of resources for transmission. A fourth resource pool defined by a 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 the third resource pool, wherein the second critical communication notification indicates that the fourth message is to be sent in the 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.

[0017] In addition, a method for wireless communication is provided. A first resource pool includes a first plurality of resources for transmission. A 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. A third resource pool includes a third plurality of resources for transmission. A 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 includes:

[0018] - sending, by a transmitter of the 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,

[0019] - after sending the first critical communication notification or while sending the first critical communication notification, the transmitter sends a second message in the second resource pool,

[0020] - receiving a second critical communication notification as a third message, the second critical communication notification being sent by a receiver of the user equipment 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. And:

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

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

[0023] The embodiments are based on a new concept applicable to direct D2D communication for very low latency and high reliable access. The new concept may also be partially applicable to critical communication notifications in uplink, for example.

[0024] The new concept may, for example, include the transmission of an autonomous, unauthorized EN using specific signal characteristics (e.g., increased power settings). For example, a unique signal indicating an emergency may be sent. Critical communication notifications may, for example, be sent in the frequency / time domain without being used in the currently defined frame structure. Retransmissions may, for example, be defined to ensure the requested reliability or QoS (Quality of Service). Upon receiving an EN, neighboring UEs may, for example, be configured to stop transmissions in a continuous D2D pool to avoid interference with the retransmitted EN. When an EN is sent, UEs that do not receive the EN due to simultaneous transmissions are notified, for example, using randomized time-frequency resources to avoid repeated interference in subsequent TTIs (TTI=Transmission Time Interval), or also referred to as subframes (SFs). Conveying critical communication notifications may, for example, be applied to notify additional remote UEs.

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

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

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

[0028] According to an embodiment, resources may be released, for example, as indicated in the exception pool: in this case, any resources reserved for high priority data in the exception poll are no longer allowed to be used by any other UE, even if the resources had been scheduled / sensed as idle before receiving the indication in the exception pool.

[0029] In an embodiment, if the base station is responsible for resource allocation (e.g., in mode 3), a user entity (UE) / user equipment (UE) requesting high priority data transmission may, for example, be provided with transmission on an exception pool (with limited resources for control or data or both), or, for example, transmission on a regular pool, or, for example, both (transmission on both the exception pool and the regular pool).

[0030] For example, an exception pool is a resource pool including a plurality of resources for transmission.

[0031] For example, the regular pool is another resource pool including another plurality of resources used for transmission.

[0032] Depending on the implementation, if the UE is responsible for requesting resource allocation for high priority data transmission (e.g., in mode 4), the UE may, for example, transmit on an exception pool (having limited resources for control or data or both), or may, for example, transmit on a regular pool or both (transmission on both the exception pool and the regular pool).

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

[0034] Embodiments ensure reliable and low latency communications for transmission of urgent / high priority messages.

[0035] The implementation is based on immediate, very short-term notification, including indication of which resources are to remain open to any other UE, even if already allocated / scheduled. These resources that remain open may, for example, be reserved for the transmission of emergency / high priority messages.

[0036] In an embodiment, UEs receiving the notification may, for example, be configured to interrupt their active transmissions or defer their scheduled resources if they successfully decode the notification.

[0037] It is assumed that all UEs belonging to LTE / 5G / NR (NR=New Radio) can decode the exception pool / exceptional preconfigured resources and repetitions on the regular pool.

[0038] According to an embodiment, latency is reduced and reliability is increased for high priority notifications.

[0039] Regarding latency, long sensing cycles are avoided by employing "critical" resource reservation.

[0040] The UE may, for example, be allowed to access resources in a resource pool / resource pool configuration (except emergency / exceptional resources / pools) without the one-second sensing required in current specifications.

[0041] Regarding reliability, UEs with lower priority payloads may, for example, be prohibited from sending even already scheduled transmissions to prioritize high priority data to avoid interference and thus result in higher reliability for high priority data transmissions.

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

[0043] -PPPP (ProSe per packet priority)

[0044] -PPPR (ProSe per packet reliability)

[0045] -Packet delay budget

[0046] -Packet Error Rate

[0047] -QoS-Flow

[0048] - Any combination of previous indicators.

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

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

[0051] Some embodiments may, for example, notify other UEs of resources on the shared resource pool on a very short term basis to keep the resources (in notification) free. Advantages may be, for example, that any high priority / urgent messages may be transmitted grant-free (e.g., with very low latency) with high reliability, since other UEs may, for example, be prevented from using the indicated resources.

[0052] Some implementations may, for example, enhance the use of exception / emergency pools to allow low latency communications.

[0053] In some embodiments, if data has been sent via an exception / emergency pool, the subchannel size and / or subchannel offset and / or SPS period (SPS = semi-persistent scheduling) can be sent, for example, by SCI (Sidelink Control Information), and / or a preconfigured period can be sent, for example, by SCI (Sidelink Control Information).

[0054] Some embodiments may transmit, for example, without sensing, by transmitting on the exception pool and (eg, simultaneously) by parallel transmission on the regular pool with variable power until some time (eg, until some time T_max_P).

[0055] For example, implementations may be employed in the fields of V2X, D2D, mMTC (massive machine type communications), URLLC, and in delay-critical / reliability-critical communications.

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

[0057] Embodiments of the present invention are described in more detail below with reference to the accompanying drawings, in which:

[0058] Figure 1 shows a user equipment for wireless communication according to an embodiment,

[0059] Figure 2 A schematic representation of an example of a wireless communication system is shown,

[0060] Figure 3 shows a cell with two different overlapping networks such as Figure 2 Schematic representation of cells in a macrocell network, i.e. a macrocell network comprising macrocells and a smallcell network comprising smallcell base stations connected to the macrocell base station via backhaul links,

[0061] Figure 4 Shown with Figure 3Another schematic representation of a plurality of small cells of a similar macro cell, wherein the small cell base stations are connected to each other and to a core network via backhaul links,

[0062] Figure 5 shows an example of a computer system 500 according to an embodiment,

[0063] Figure 6 shows cross-carrier scheduling via SCI transmission on an abnormal resource pool according to an embodiment,

[0064] Figure 7 shows intra-carrier scheduling via SCI transmission on an abnormal resource pool according to an embodiment,

[0065] Figure 8 shows SPS duplication and SCI redundancy according to an embodiment,

[0066] Fig. 9 shows SPS data below the control information repeated in the exception pool and the normal pool according to an embodiment,

[0067] Fig.10 shows the same component carrier scheduling of emergency data and regular data according to an embodiment,

[0068] Fig.11a shows different component carrier scheduling of emergency data and regular data according to an embodiment,

[0069] Fig.11b shows different component carrier scheduling of emergency data and regular data according to another embodiment,

[0070] Fig.12 shows a sidelink subframe configuration forwarded out of coverage for emergency monitoring according to an embodiment, and

[0071] Fig.13 A system for wireless communication according to an embodiment is shown.

[0072] In the following description, a number of details are set forth to provide a more complete description of embodiments of the present invention. However, it will be apparent to those skilled in the art that embodiments of the present invention may be implemented without these specific details. In other cases, in order to avoid obscuring embodiments of the present invention, known structures and devices are shown in block diagram form rather than in detail. In addition, unless otherwise specifically noted, the features of the different embodiments described below may be combined with each other.

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

[0074] Figure 2 1 is a schematic representation of an example of a wireless network 100 including a core network 102 and a radio access network 104. The radio access network 104 may include a plurality of base stations eNB 1 To eNB 5 Each base station serves a corresponding cell 106 1 Up to 106 5 A specific area around a base station schematically represented. Base stations are provided to serve users within the cell. Users can be fixed devices or mobile devices. In addition, the wireless communication system can be accessed by mobile or fixed IoT devices (IoT = Internet of Things) connected to the base station or the users. Mobile devices or IoT devices can include physical devices, ground-based vehicles (such as robots or cars), aircraft (such as manned or unmanned aerial vehicles (UAV), the latter also known as drones), buildings and other items embedded with electronic devices, software, sensors, actuators, etc., as well as network connections that enable these devices to collect and exchange data through existing network infrastructure. Figure 2 An exemplary view of only five cells is shown, however, the wireless communication system may include many more such cells. Figure 2 Shown in cell 106 2 and by the base station eNB 2 Two UEs served 1 and UE 2 , also called user equipment (UE). Another user UE 3 is shown in the base station eNB 4 Serving Residential Areas 106 4 In. Arrow 108 1 , 108 2 and 108 3 Schematically represents the method for receiving a signal from a user UE 1 ,UE 2 and UE 3 To the base station eNB 2 、eNB 4 Send data or use it from the base station eNB 2 、eNB 4 To user UE 1 ,UE 2 ,UE 3 Uplink / downlink connection for sending data. In addition, Figure 2 In the community 106 4 Two IoT devices 110 are shown, which may be fixed or mobile devices. 1 and 110 2 As shown in arrow 112 1 Schematically represented, IoT device 110 1 Via base station eNB4 Access the wireless communication system to receive and send data. 2 Schematically represented, IoT device 110 2 Via user UE 3 Access the wireless communication system. The corresponding base station eNB 1 To eNB 5 For example, via the S1 interface, via Figure 2 The corresponding backhaul link 114 is schematically represented by an arrow pointing to the "core" in FIG. 1 Up to 114 5 The core network 102 may be connected to one or more external networks. In addition, the corresponding base station eNB 1 To eNB 5 Some or all of them may be connected, for example, via an X1 or X2 interface, via Figure 2 The corresponding backhaul link 116 is schematically represented by an arrow pointing to "eNB" in FIG. 1 Up to 116 5 Connect with each other.

[0075] Figure 2 The wireless network or communication system depicted in the figure may be a heterogeneous network having two different overlapping networks, namely, each macro cell includes a macro base station such as a base station eNB. 1 To eNB 5 The macro cell network and small cell base station ( Figure 2 ) such as a network of femto or pico base stations.

[0076] There are multiple resources for transmission. For data transmission, a physical resource grid can be used. The physical resource grid may include a set of resource elements to which various physical channels and physical signals are mapped. For example, a physical channel may include a physical downlink and uplink shared channel (PDSCH, PUSCH) carrying user-specific data (also referred to as downlink and uplink payload data), a physical broadcast channel (PBCH) carrying, for example, a master information block (MIB) and a system information block (SIB), a physical downlink and uplink control channel (PDCCH, PUCCH) carrying, for example, downlink control information (DCI), etc. For the uplink, the physical channel may also include a physical random access channel (PRACH or RACH) used by the UE to access the network once the UE is synchronized and obtains the MIB and SIB. Physical signals may include reference signals (RS), synchronization signals, etc. The resource grid may include a frame having a specific duration in the time domain, such as 10 milliseconds, and a given bandwidth in the frequency domain. The frame may have a certain number of subframes of a predefined length, for example, 2 subframes of 1 millisecond in length. Each subframe may include two slots of 6 or 7 OFDM symbols depending on the cyclic prefix (CP) length.

[0077] For sidelink communications (e.g., for UEs connected to a radio resource controller (RRC) after successful association with a base station, or for idle or remote UEs in a dedicated frequency band, for example), there is a physical sidelink shared channel (PSSCH) for data. In addition, control on the sidelink requires a physical sidelink control channel (PSCCH).

[0078] Both channels PSSCH and PSCCH are transmitted between UEs over a time / frequency resource grid. For sidelink transmissions, the resource pool / pre-configured resources can be on a dedicated carrier or in a frequency band with LTE and NR along with the uplink channels.

[0079] The wireless communication system can 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 CP, such as DFT-s-OFDM. Other waveforms can be used, such as non-orthogonal waveforms for multiple access, such as filter bank multi-carrier (FBMC), generalized frequency division multiplexing (GFDM), or universal filtering multi-carrier (UFMC). The wireless communication system can be operated, for example, according to the LTE-Advanced pro standard or the 5G or NR (new radio) standard. In LTE, the sidelink communication uses a DFT-s-OFDM waveform. In NR, the sidelink can use two waveforms, namely DFT-s-OFDM and / or OFDMA.

[0080] In such Figure 2 In the wireless communication network shown, the radio access network 104 may be a heterogeneous network including a network of primary cells, each of which includes a main base station, also called a macro base station. In addition, a plurality of secondary base stations, also called small cell base stations, may be provided for each of the macro cells. Figure 3 is a cell with two different overlapping networks such as Figure 2 Cell 106 1 The network includes a macro cell 106. 1 macrocell network and small cell network. Figure 3 Only a single macro cell is represented, but it should be noted that Figure 2 One or more of the other cells in the small cell network may also use an overlapping network. The small cell network includes multiple small cell base stations SeNB 1 To SeNB 5 Each small cell base station is in the corresponding area 120 1 Up to 120 5 The small cell base station SeNB works within the coverage area of ​​the small cell. 1 To SeNB 5 The macro cell base station MeNB 1 Control, the corresponding small cell base station SeNB 1 To SeNB 5 Via the corresponding backhaul link 122 1 Up to 122 5 Connect to the macro cell base station MeNB 1 Instead of connecting the small cell base stations to the macro cell base stations via the backhaul links, one or more of the small cell base stations may be coupled to the core network via corresponding backhaul links. Figure 3 Also shown is a user equipment UE as shown by arrow 124 1 The macro cell base station MeNB indicated 1 Services, as well as arrow 124 2 The schematically indicated small cell base station SeNB 1 Serve.

[0081] Figure 4 A plurality of small cells 120 are macro cells (not shown) 1 Up to 120 3 A macro cell can be similar to Figure 3 Each small cell can serve one or more UEs. Figure 3 The corresponding small cell base station SeNB 1 、SeNB 2 、SeNB 3 , ... via a backhaul link or connection 102 1Up to 102 3 Connected to the core network 102. The corresponding small cell 102 1 Up to 102 3 can be directly connected to each other via the X2 interface, such as Figure 4 The transport network connecting the corresponding small cells to the core network 102 may be a fiber optic network including one or more points of presence (PoPs), where a plurality of small cells are connected to the transport network. Figure 4 Additional details of the backhaul architecture are shown.

[0082] The small cell (also called a secondary mobile communication cell SC) forms an overlay network to the macro cell network (also called a primary mobile communication cell PC). The small cell can be connected to the macro cell ( Figure 3 ) and / or core network ( Figure 4 ). The backhaul link may be a wired or wireless link, and in the case where the small cell is connected to the core network via the backhaul link, the point of presence (PoP) ( Figure 4 ) can act as an interface to the core network. Each small cell can be connected via a wireless access link (AL) 124 2 Serving multiple mobile users UE within its coverage area. In addition, the UE may be connected to the primary cell, for example to receive control signals, and this connection may be referred to as a control link (CL).

[0083] Next, embodiments of the present invention are described.

[0084] Figure 1 A user equipment for wireless communication according to an embodiment is shown.

[0085] The user equipment includes a transmitter 152 and a receiver 154 .

[0086] User equipment has specific capabilities:

[0087] In the first case, the user equipment announces a critical communication with a first message. The critical communication is followed by a second message. In such a case:

[0088] A first resource pool defined by a first resource pool configuration includes a first plurality of resources for transmission. A second resource pool defined by a 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.

[0089] 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.

[0090] An example for the first message is Figure 6 Message 651, Figure 7 Message 751, Figure 8 Messages 851 and 853, Fig. 9 Messages 951, 953 and 955, Fig.10 Messages 1051 and 1054, Fig.11a Messages 1151 and 1154 and Fig.11b Messages 1156 and 1157.

[0091] An example for the second message is Figure 6 News 661, Figure 7 News 761, Figure 8 Messages 861, 862, 863, 864 and 865, Fig. 9 Messages 961, 962, 963, 964 and 965, Fig.10 Messages 1061, 1062, 1063 and 1064 in FIG. 11, messages 1161, 1162, 1163, 1164 in FIG. 11, and Fig.11b 1166 and 1167.

[0092] A resource pool configuration may be, for example, an authorization of a resource configuration.

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

[0094] Furthermore, the transmitter 152 is configured to send a second message in the second resource pool after sending the first critical communication notification or simultaneously with sending the first critical communication notification.

[0095] In the second case, the user equipment receives a notification of a critical communication in the third resource pool from another communication entity, wherein the notification reserves a fourth resource pool for critical communication. The user equipment adjusts its behavior and does not send its own message in the (reserved) fourth resource pool, which is reserved by the notification for critical communication. The critical communication from the other communication entity itself follows. In such a case:

[0096] A third resource pool defined by the third resource pool configuration includes a third plurality of resources for transmission. A 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.

[0097] 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.

[0098] 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.

[0099] As for the first message, an example for the third message is Figure 6 Message 651, Figure 7 Message 751, Figure 8 Messages 851 and 853, Fig. 9 Messages 951, 953 and 955, Fig.10 Messages 1051 and 1054, Fig.11a Messages 1151 and 1154 and Fig.11b Messages 1156 and 1157.

[0100] As for the fourth message, the example for the second message is Figure 6 News 661, Figure 7 News 761, Figure 8 Messages 861, 862, 863, 864 and 865, Fig. 9 Messages 961, 962, 963, 964 and 965, Fig.10 Messages 1061, 1062, 1063 and 1064 in FIG. 11, messages 1161, 1162, 1163, 1164 in FIG. 11, and Fig.11b 1166 and 1167.

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

[0102] 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 positions and time positions of the second message. Alternatively, the first message includes a pointer to the second message in the second resource pool, the pointer defining one or more frequency positions and time positions and a repetition period of the second message.

[0103] And / or, the third message includes a pointer to a fourth message in a fourth resource pool, the pointer defining one or more frequency positions and time positions of the fourth message. Alternatively, the third message includes a pointer to a fourth message in a fourth resource pool, the pointer defining one or more frequency positions and time positions and a repetition period of the fourth message.

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

[0105] In an embodiment, the second resource pool may be defined as a resource pool for communication or preconfigured communication resources or allocated bandwidth portion or dynamically authorized resources, for example. And / or the fourth resource pool is defined as a resource pool for communication or preconfigured communication resources or allocated bandwidth portion or dynamically authorized resources.

[0106] In an embodiment, the first resource pool may, for example, include a first plurality of preconfigured resources for sidelink transmission, the second resource pool may, for example, include a second plurality of resources for sidelink transmission, the third resource pool may, for example, include a third plurality of resources for sidelink transmission, and the fourth resource pool may, for example, include a fourth plurality of resources for sidelink transmission.

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

[0108] In an embodiment, the transmitter 152 may be configured, for example, to send the second message in the second resource pool 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.

[0109] According to an embodiment, the transmitter 152 may be configured, for example, to send a first critical communication notification including an indication of a resource in the second plurality of resources for transmission of a transmission for a second resource pool. In such an embodiment, the transmitter 152 may be configured, for example, to send a second message in the resource for transmission indicated by the indication, wherein the indication includes a pointer to the resource for transmission, or includes a subframe indication indicating a subframe, or includes a frequency indication indicating a frequency, or includes a component carrier indication indicating a component carrier.

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

[0111] According to an embodiment, the fifth message may, for example, be scheduled for transmission in the fourth resource pool. In such an embodiment, 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.

[0112] In an embodiment, the first resource pool may be, for example, an exception pool for providing a first plurality of resources for a transmission having a high priority, the exception pool being a shared pool or a configuration authorization in the full bandwidth, sub-bandwidth, or bandwidth portion. The second resource pool may be, for example, a regular pool for providing a second plurality of resources for a transmission having a priority lower than the high priority. The transmitter 152 may, for example, be configured to send a second message having a high priority in the exception pool, the exception pool being a configuration authorization in the shared pool or the full bandwidth, sub-bandwidth, or bandwidth portion. The transmitter 152 may, for example, be configured to send a sixth message having a low priority in the regular pool.

[0113] According to an embodiment, the third resource pool may be, for example, an exception pool for providing a third plurality of resources to a transmission having a high priority. In such an embodiment, the fourth resource pool may be, for example, a regular pool for providing a fourth plurality of resources to a transmission having a priority lower than the high priority. In addition, in such an embodiment, the transmitter 152 may, for example, be configured to send a second message having a high priority in the exception pool. In addition, in such an embodiment, the transmitter 152 may, for example, be configured to send a sixth message having a low priority in the regular pool.

[0114] 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.

[0115] According to an embodiment, after sending the first critical communication notification for the first time, the transmitter 152 may, for example, be configured to resend the first critical communication notification one or more times in the first resource pool.

[0116] In an embodiment, in response to the receiver 154 receiving the second critical communication notification, the transmitter 152 may be configured to transmit the second critical communication notification to one or more other user devices ( Figure 1 (not shown) sends a third message, where the third message may, for example, indicate that the fourth message is to be sent in a fourth resource pool.

[0117] According to an embodiment, the transmitter 152 may be configured to send a first critical communication notification at a first transmission power, wherein the transmitter 152 may be configured to send a second message at a second transmission power, wherein the first transmission power may be greater than the second transmission power.

[0118] In an embodiment, at least one of the first critical communication notification and the second critical communication notification may be, for example, side link control information including one or more side link control information data elements, wherein the side link control information data element includes at least one of a component carrier index, a subframe index, an SPS period, a transmission offset, a subchannel size, and an indication of whether frequency hopping is allowed.

[0119] According to an embodiment, each of the first resource pool and the second resource pool and the third resource pool and the fourth resource pool can, for example, be allocated to multiple component carriers, wherein the first resource pool can, for example, be allocated to a first component carrier among the multiple component carriers, and wherein the second resource pool can, for example, be allocated to a second component carrier among the multiple component carriers, wherein the second component carrier can, for example, be different from the first component carrier.

[0120] In another embodiment, each of the first resource pool and the second resource pool and the third resource pool and the fourth resource pool can, for example, be allocated to multiple component carriers, wherein the first resource pool can, for example, be allocated to a first component carrier of the multiple component carriers, and wherein the second resource pool can, for example, also be allocated to the first component carrier.

[0121] 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 the base station, the receiver 154 of the user equipment is configured to receive a subframe bitmap from the base station, and the transmitter 152 of the user equipment is configured to send the subframe bitmap received from the base station to another vehicle outside the coverage of the base station.

[0122] 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.

[0123] 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.

[0124] Fig.13 A system for wireless communication according to an embodiment is shown.

[0125] 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 above-mentioned embodiments. The plurality of user equipments 150 , 250 comprises a first user equipment 150 and a second user equipment 250 .

[0126] 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 the first resource pool configuration or is equal to the first resource pool configuration.

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

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

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

[0130] The transmitter 152 of the first user equipment 150 is configured to send a second message in the second resource pool after sending the critical communication notification or simultaneously with sending the critical communication notification.

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

[0132] First, a control channel design and reservation process for exception pool notification of data in a regular pool according to an embodiment is described.

[0133] In an embodiment, the control data in the exception pool may be used to process and reserve transmission or retransmission or periodic repetition in the regular resource pool.

[0134] The concepts presented can be compared to some extent to interrupt handling in computer science, with a distinction between first-level and second-level interrupt handlers.

[0135] If an emergency occurs, the first level part corresponds to the sidelink control information (SCI) transmitted immediately via the preconfigured exception pool. The SCI includes information about the component carrier, the subframe and / or subchannel location of the announced data transmission, and the repetition period / pattern of data transmission, possibly in a semi-persistent scheduling (SPS) manner.

[0136] The second level part consists of scheduled data transmissions via the normal resource pool.A scheduled data transmission may, for example, consist of a single transmission.

[0137] Alternatively, the scheduled data transmission may, for example, include an initial transmission followed by further retransmissions according to a predefined pattern. For example, the initial transmission may be followed by periodic transmissions. The first level transmission may, for example, carry information about the transmission interval t interval And each transmission T i The length of T, where T can be defined as T=N*ST_duration, for example.

[0138] In the current 3GPP specification, all UEs are authorized to receive any data transmission in the exception pool.

[0139] According to an embodiment, all UEs may, for example, mute or skip their intended transmissions in case they collide with the second stage partial (delayed / scheduled) data transmissions.

[0140] In an embodiment, the normal (or exception) pool for data transmission opportunities after sending an SCI using the exception pool may be selected based on, for example, CBR (Channel Busy Rate).

[0141] 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. Considering that some UEs may have to re-tune their local oscillators to the component carrier that schedules the delayed data transmission, the next possible subframe may refer to the next subframe that all UEs are able to read, for example.

[0142] The SCI data element may, for example, include one or more of the following elements:

[0143] - Component Carrier (CC) index; for example, the same CC ID is used by default. If the ERPs are in the same CC, the CC ID may not be used or set to zero. Otherwise, different CC IDs may have any pre-configured value.

[0144] - As defined in section 3.3.1.1 of [5], the IE ServCellIndex refers to a short identifier that identifies the serving cell (e.g., PCell or SCell). The value 0 applies to the PCell, while the previously assigned ServCellIndex applies to the SCell:

[0145] The ServCellIndex information element may be defined, for example, as:

[0146] --ASN

[0147] --ASN1START

[0148] ServCellIndex-r10::=INTEGER(0..7)

[0149] ServCellIndex-r13::=INTEGER(0..31)

[0150] --ASN1STOP

[0151] - Subframe index or offset of the initial data transmission after the emergency control announcement (second level (payload) transmission).

[0152] -SPS cycle; in the normal resource pool and / or the abnormal / emergency pool. It defines a interval The cycle and T max The maximum transmission period.

[0153] - PRB index n of the initial second level (data payload and control information) transmission (PRB = Physical Resource Block) subCHRBstart Transmission offset.

[0154] -Subchannel size n subCHsize It is a plurality of PRBs, for example, 2 control PRBs + X data PRBs.

[0155] - Resource Indication Value (RIV) indicating the start of resource allocation.

[0156] - For SPS transmission, whether frequency hopping with an indicated pattern is applied. Optionally, if blind detection is not possible, the pattern ID may be in the SCI information.

[0157] - For preconfigured resources for, e.g., mode 3 (ungranted transmission), RIV, subchannel and transmission period / reservation may be indicated.

[0158] - Whether the second level transfer is a single transfer.

[0159] Once other UEs capture the SCI information in the abnormal resource pool (ERP), they can, for example, all tune to receive the announced second level data transmission. Therefore, they must stop sending new data or old data in the buffer.

[0160] In the following, an exception pool (EP) access for data announcement according to an embodiment is described, wherein control information is sent in an exception pool of announced data in the same pool or a regular pool.

[0161] If the MAC (Medium Access Control / Media Access Control) PDU is large enough, then instead of sending the complete MAC PDU in the emergency pool, only a "pointer" to the resource carrying the MAC PDU is sent. The MAC PDU itself may be sent, for example, in the same subframe (the same subframe may for example relate to the same time) or on another sequential subframe (at a different time) outside the emergency pool in a parallel sidelink regular resource pool.

[0162] Figure 6 The cross-carrier scheduling via SCI transmission on an abnormal resource pool according to an embodiment is shown. In particular, Figure 6 An exception pool 611 and two resource pools 621, 622 are shown. In the exception pool 611, a first message 651 is sent as a critical communication notification. A second message 661, i.e. the notified critical communication, is later sent in the regular pool 622. The resource pool 611 can be defined, for example, as a shared resource pool or a commonly configured authorization or a commonly accessed bandwidth portion or an abnormally configured pool. The resource pools 621, 622 can be defined, for example, as a resource pool for communication or a preconfigured communication resource or an allocated bandwidth portion or a dynamically authorized resource.

[0163] Figure 7 Intra-carrier scheduling via SCI transmission on an abnormal resource pool according to an embodiment is shown. In particular, Figure 7 An exception pool 711 and a resource pool 721 are shown. In the exception pool 711, a first message 751 is sent as a critical communication notification. A second message 761, i.e., the notified critical communication, is later sent in the regular pool 721. The resource pool 711 can be defined, for example, as a shared resource pool or a commonly configured authorization or a commonly accessed bandwidth portion or an abnormally configured pool. The resource pool 721 can be defined, for example, as a resource pool for communication or a preconfigured communication resource or an allocated bandwidth portion or a dynamically authorized resource.

[0164] It should be noted that Figure 6 and Figure 7 The resource pools depicted are highly abstract. For example, a resource pool does not necessarily include consecutive subframes or adjacent control and data channels.

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

[0166] According to the implementation, the SCI (or any other information data to mute 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, for example, one or more retransmissions. Such retransmissions enhance robustness.

[0167] In the following, an embodiment is described which ensures that the control information can be implemented as a single transmission or as multiple transmissions, possibly with a repeated period in the normal pool and / or the exception pool.

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

[0169] 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 remain unused: 5-2=3 PRBs (according to the current specification). These unused RBs will be located under the SCI transmission in the exception pool. The data PRBs can, for example, be used to carry repeated SCIs, which may be scrambled to enhance robustness. The data PRBs can, for example, be used to carry information to enhance the decoding probability of the second-level data transmission, such as (redundant) bits / redundancy versions (RVs) obtained from the output of the channel coding of the secondary transmission.

[0170] In some embodiments, alternatively or additionally, the SCI may also be repeated, for example in a control channel, if urgent data is to be sent.

[0171] Figure 8 SPS repetition and SCI redundancy according to an embodiment are shown. In particular, Figure 8 An abnormal pool 811 and a (normal) resource pool 821 are shown. In the abnormal pool 811, a first message 851 is sent as a critical communication notification. The first message 851 announces messages 861, 862, 863, 864, and 865. The announced critical messages 861, 862, 863, 864, and 865 are sent later in the (normal) resource pool 821. In addition, the first message 851 is repeated as a message 853 to announce at least the remaining critical messages 863, 864, and 865. The resource pool 811 can be defined, for example, as a shared resource pool or a commonly configured authorization or a commonly accessed bandwidth portion or an abnormally configured pool. The resource pool 821 can be defined, for example, as a resource pool for communication or a preconfigured communication resource or an allocated bandwidth portion or a dynamically authorized resource.

[0172] Three or more resources may be filled with data, for example in the first transmission. Multiple transmissions of PSSCH (Physical Sidelink Shared Channel) (with or without control) may be repeated, for example, in consecutive subframes with a repetition period T. Some of the transmitted PSSCH may, for example, include data (as described above, repeating the same emergency SCI) and / or some of the transmitted PSSCH may, for example, be only emergency data PSSCH (see Figure 8 ). Some of the transmitted PSSCH may, for example, include different versions of data, the same data or different redundancy versions of emergency data. Alternatively or in addition, the originally transmitted UE-vehicle or the forwarding UE-vehicle may, for example, repeat the SCI only in the exception pool after a transmission period Tp3 (see Figure 8 ).

[0173] Fig. 9 The SPS data below the control information repeated in the abnormal pool and the normal pool according to an embodiment is shown. In particular, Fig. 9 An exception pool 911 and a regular resource pool 921 are shown. In the exception pool 911, a first message 951 is sent as a critical communication notification. The first message 951 announces messages 961, 962, 963 and 964. The announced critical messages 961, 962, 963 and 964 are later sent 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 message 965, wherein the announced message 965 is later sent in the regular resource pool 921. The resource pool 911 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 921 can be defined, for example, as a resource pool for communication or a preconfigured communication resource or an allocated bandwidth portion or a dynamically authorized resource.

[0174] According to the implementation mode, the data PSSCH may also be transmitted, for example, in the exception pool with a possible repetition period Tp. The SCI contains resources in both the normal pool and the exception pool (see Fig. 9 ).

[0175] In the following, embodiments are described for prioritizing the transmission of urgent data when arriving within a time window before regular data transmission.

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

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

[0178] The transmission of the emergency SCI (in the exception pool) and the associated emergency data PSSCH (with or without a copy of the SCI) may be transmitted, for example, in the same subframe or in two consecutive subframes as previously described. Non-critical data transmission may be muted, for example, until the emergency is over or postponed to a later subframe.

[0179] For the same component carrier (CC) scheduling, emergency data and non-emergency data can coexist on different (offset) subframes with different transmission periods (if SPS transmission is configured).

[0180] Fig.10 The same component carrier (CC) scheduling of emergency data and regular data according to an embodiment is shown. In particular, Fig.10 An exception pool 1011 and two resource pools 1021 are shown. 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 announced critical messages 1061, 1062, 1063, and 1064 are later sent in the (normal) resource pool 1021. In addition, the first message 1051 is repeated as a message 1054 to announce at least the remaining critical messages 1063 and 1064.

[0181] 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 announced messages 1061 , 1062 , 1063 , and 1064 will not be interfered by the other messages 1071 , 1072 , and 1073 .

[0182] In some embodiments, upon receiving the first message 1051 , the user equipment will not send other messages 1071 , 1072 , and 1073 planned to be sent in the regular pool 1021 , so that the announced messages 1061 , 1062 , 1063 , and 1064 will not be interfered with by the other messages 1071 , 1072 , and 1073 planned to be sent.

[0183] For different component carrier (CC) scheduling, emergency data and non-emergency data can coexist on different CCs on the same (or offset) subframes with the same transmission period or different transmission period (if SPS transmission is configured).

[0184] Fig.11aDifferent component carrier (CC) scheduling for emergency data and regular data according to an embodiment is shown. In particular, Fig.11a An exception pool 1111 and two resource pools 1121, 1122 are shown. In the exception pool 1111, a first message 1151 is sent as a critical communication notification. The first message 1151 announces messages 1161, 1162, 1163 and 1164 with high priority. The announced 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 a message 1154 to announce at least the remaining critical messages 1163 and 1164. Other messages 1171, 1172, 1173, 1174 with 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 critical messages 1161 , 1162 , 1163 , and 1164 of announcements having a high priority.

[0185] The transmission of the emergency signal may have a priority of Pri1 and a transmission power of Pow1, while the transmission of normal data may have a priority of Pri2 and a transmission power of Pow2. Herein, Pri1>Pri2 and Pow1>=Pow2.

[0186] Fig.11b Different component carrier scheduling of emergency data and regular data according to another embodiment is shown. In the exception pool 1111, a first message 1156 is sent as a critical communication notification. The first message 1156 announces a message 1166 with a high priority. The announced critical message 1166 is sent later in the exception resource pool 1111. In addition, in the exception pool 1111, another message 1157 is sent as a critical communication notification. The other message 1157 announces a message 1167 with a high priority. The announced 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. The other messages 1176 and 1177 with low priority can be sent, for example, at a lower power than the announced critical messages 1166 and 1167 with high priority.

[0187] In the following, arrangements for sidelink access band transmissions to deliver emergency messages to a greater number of users are described according to embodiments. In particular, access on different frequency bands with different transmission powers and bandwidths is described.

[0188] In order to access the channel for emergency notifications, the vehicle-UE may, for example, perform a series of accesses / attempts to acquire the channel for emergency transmissions to other vehicles. By doing so, the chances of receiving emergency data and control should be increased.

[0189] The emergency pool access process according to an embodiment may be, for example, as follows:

[0190] In case of emergency, if the vehicle is able to connect to multiple bands, e.g. with or without multiple TX / RX chains:

[0191] oFirst, after the emergency group arrives

[0192] ■ Start from a dedicated frequency band (<6 GHz, e.g. ITS band around 5.9 GHz) and start the emergency transmission process

[0193] o Otherwise if the band transmission is not allowed or is insufficient (after a short waiting period Ts)

[0194] ■Switch to a lower frequency (<6GHz) sidelink band on a configured or pre-configured bitmap and start the emergency transmission process

[0195] o Otherwise if the band transmission is not allowed or is insufficient (after a short waiting period Ts)

[0196] ■Switch to the higher frequency (mmWave) ITS band (63GHz) and start the emergency transmission process

[0197] o Otherwise if the band transmission is not allowed or is insufficient (after a short waiting period Ts)

[0198] ■Switch to a higher frequency (mmWave) licensed band on a configured or pre-configured bitmap and start the emergency transmission process

[0199] oOtherwise, end the process

[0200] (mmWave=millimeter wave)

[0201] (ITS = Intelligent Transportation System)

[0202] In the following, embodiments for broadcasting a bitmap in emergency control information from covered UEs to non-covered (autonomous) vehicles are described. In particular, the preconfigured map may be selectable, for example, to reduce the number of bitmap broadcast bits in sidelink control information (SCI).

[0203] Fig.12 A sidelink subframe configuration forwarding out of coverage for emergency monitoring is shown according to an embodiment.

[0204] Next, consider the PSCCH subframe and resource block pool.

[0205] If a vehicle handles an 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 adjust to monitor emergency data. The bitmap can be sent, for example, via SCI emergency control information.

[0206] As in existing systems, the bitmap is configured according to a periodic (pre-configured) pattern, called a bitmap (Subframe Bitmap-r12 is introduced in the SL-FR-ResourceConfig field in section 6.3.8 of [5]. The length of Subframe Bitmap-r12 is 40 bits. These 40 bits can be transmitted, for example, on Uu to convey an index T_RPT indicating the bitmap sequence used.

[0207] Similarly, subframe bitmap-r12 must be forwarded to out-of-coverage vehicles to allow remote UEs to monitor emergency notifications and data transmissions on scheduled resources (see Fig.12 ). In order to reduce data transmission on SCI (via the exception pool), subframe bitmap-r12 can 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 number of index bits).

[0208] 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, wherein a block or device corresponds to a method step or a feature of a method step. Similarly, aspects described in the context of a method step also represent a description of a corresponding block or item or a feature of a corresponding apparatus.

[0209] The various elements and features of the present invention can be implemented in hardware (using analog and / or digital circuits), in software (by executing instructions by one or more general or special purpose processors), or as a combination of hardware and software. For example, embodiments of the present invention can be implemented in the environment of a computer system or another processing system.

[0210] Figure 5An example of a computer system 500 according to an embodiment is shown. The steps of the methods performed by these units or modules and these units can be performed on one or more computer systems 500. The computer system 500 includes one or more processors 502, such as a dedicated or general-purpose digital signal processor. The processor 502 is connected to a communication infrastructure 504, such as a bus or a network. The computer system 500 includes a main memory 506, such as a random access memory (RAM) and an auxiliary memory 508, such as a hard drive and / or a removable storage drive. The auxiliary memory 508 can allow a computer program or other instructions to be loaded into the computer system 500. The computer system 500 can also include a communication interface 510 to allow software and data to be transmitted between the computer system 500 and an external device. The communication can be in the form of electronic, electromagnetic, optical or other signals that can be processed by the communication interface. The communication can use wires or cables, optical fibers, telephone lines, cellular phone links, RF links and other communication channels 512.

[0211] The terms "computer program medium" and "computer readable medium" are generally used to refer to tangible storage media, such as a removable storage unit or a hard disk installed in a hard drive. These computer program products are devices for providing software to the computer system 500. Computer programs (also called computer control logic) are stored in the main memory 506 and / or the auxiliary memory 508. The computer program can also be received via the communication interface 510. The computer program enables the computer system 500 to implement the present invention when executed. In particular, the computer program enables the processor 502 to implement the processing of the present invention, such as any method described herein, when executed. Therefore, such a computer program can represent a controller of the computer system 500. In the case of implementing the present disclosure using software, the software can be stored in a computer program product and loaded into the computer system 500 using a removable storage drive, an interface (such as the communication interface 510).

[0212] The implementation in hardware or software can 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 can cooperate) with a programmable computer system to perform the corresponding method. Therefore, the digital storage medium can be computer readable.

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

[0214] Generally, embodiments of the present invention can be implemented as a computer program product with a program code, wherein the program code is operative for performing one of the methods when the computer program product runs on a computer. The program code may, for example, be stored on a machine readable carrier.

[0215] Other embodiments comprise the computer program for performing one of the methods described herein, stored on a machine readable carrier. In other words, an embodiment of the inventive method is, therefore, a computer program with a program code for performing one of the methods described herein, when said computer program runs on a computer.

[0216] Therefore, another embodiment of the method of the present invention is a data carrier (or digital storage medium, or computer readable medium), including a computer program for performing one of the methods described herein recorded thereon. Therefore, another embodiment of the method of the present invention is a data stream or signal sequence representing a computer program for performing one of the methods described herein. The data stream or signal sequence can be configured to be connected via a data communication, for example, via the Internet transmission. Another embodiment includes a processing device such as a computer or a programmable logic device configured to or suitable for performing one of the methods described herein. Another embodiment includes a computer having a computer program for performing one of the methods described herein installed thereon.

[0217] In some embodiments, a programmable logic device (e.g., a field programmable gate array) can be used to perform some or all of the functions in the methods described herein. In some embodiments, a field programmable gate array can collaborate with a microprocessor to perform one of the methods described herein. Typically, the method is preferably performed by any hardware device.

[0218] The above embodiments are merely for illustrating the principles of the present invention. It should be understood that modifications and variations of the arrangements and details described herein will be apparent to other persons skilled in the art. Therefore, it is intended that the scope of the appended patent claims be limited only, rather than being limited by the specific details presented by the description and illustration of the embodiments herein.

[0219] abbreviation:

[0220] Abbreviation: Meaning:

[0221] BS: Base Station

[0222] CBR: Channel Busy Rate

[0223] D2D: Device to Device

[0224] EN:Emergency notification (example for critical communication notification)

[0225] eNB: Evolved Node B (base station)

[0226] FDM: Frequency Division Multiplexing

[0227] LTE: Long Term Evolution

[0228] PC5: Interface for D2D communication using sidelink channels

[0229] PPPP: ProSe per packet priority

[0230] PPPR: ProSe per packet reliability

[0231] PRB: Physical Resource Block

[0232] ProSe: Proximity Services

[0233] RA: Resource Allocation

[0234] SCI: Sidelink Control Information

[0235] SL: Sidelink

[0236] sTTI: short transmission time interval

[0237] TDM: Time Division Multiplexing

[0238] TDMA: Time Division Multiple Access

[0239] UE: User Entity (User Terminal)

[0240] URLLC: Ultra-Reliable Low-Latency Communications

[0241] V2V: Vehicle to Vehicle

[0242] V2I: Vehicle to Infrastructure

[0243] V2P: Vehicle to Pedestrian

[0244] V2N: Vehicle to Network

[0245] V2X: Vehicle to everything, such as V2V, V2I, V2P, V2N

[0246] References:

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

[0248] [2]TS 36.331Evolved Universal Terrestrial Radio Access(E-UTRA)-RadioResource Control(RRC);V14.

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

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

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

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

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

Claims

1. A user equipment for wireless communication, in, The user equipment comprises: Launcher (152; 252) and 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 first critical communication notification indicates a repetition period of repetition of the second message, 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; 721; 821; 921; 1021; 1121) 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, 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, 861). 62, 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), wherein the second critical communication notification indicates a repetition period of repetition of the fourth message, and wherein the second critical communication notification and the fourth message are sent simultaneously, 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, Wherein, the first resource pool is defined as a shared resource pool or a commonly configured authorization or a commonly accessed bandwidth portion or an abnormally configured pool, and / or The third resource pool is defined as a shared resource pool or a commonly configured authorization or a commonly accessed bandwidth portion or an abnormally configured pool.

2. The user equipment according to claim 1, in, The second resource pool is defined as a resource pool for communication or a preconfigured communication resource or an allocated bandwidth portion or a dynamically authorized resource, and / or The fourth resource pool is defined as a resource pool for communication or pre-configured communication resources or allocated bandwidth portion or dynamically authorized resources.

3. The user equipment according to claim 1, in, The first message includes a pointer to the second message in the second resource pool, the pointer defining one or more frequency positions and time positions of the second message; or wherein the first message includes a pointer to the second message in the second resource pool, the pointer defining one or more frequency positions and time positions of the second message and the repetition period; and / or The third message includes a pointer to the fourth message in the fourth resource pool, and the pointer defines one or more frequency positions and time positions of the fourth message; or the third message includes a pointer to the fourth message in the fourth resource pool, and the pointer defines one or more frequency positions and time positions of the fourth message and the repetition period.

4. The user equipment according to claim 1, in, The first resource pool (611; 711; 811; 911; 1011; 1111) includes a first plurality of preconfigured resources for sidelink transmission, wherein the second resource pool (622; 721; 821; 921; 1021; 1121) includes a second plurality of resources for sidelink transmission, wherein the third resource pool (611; 711; 811; 911; 1011; 1111) includes a third plurality of resources for sidelink transmission, and wherein the fourth resource pool (622; 721; 821; 921; 1021; 1121) includes a fourth plurality of resources for sidelink transmission.

5. The user equipment according to claim 1, in, The transmitter (152; 252) is configured to be in the second resource pool (622; 721; 821; 921; 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) is sent in the process.

6. The user equipment according to claim 1, in, The transmitter (152; 252) is configured to send a signal including an indication of the second plurality of resources for transmission of the second resource pool (622; 721; 821; 921; 1021; 1121) of an indication of resources for transmission, 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 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.

7. The user equipment according to claim 1, in, 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.

8. The user equipment according to claim 1, in, A fifth message (1071, 1072, 1073) is scheduled for transmission in the fourth resource pool (1021), 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.

9. The user equipment according to claim 1, in, 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 configured grant in a full bandwidth, a sub-bandwidth or a bandwidth portion, 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) with a high priority in the exception pool, the exception pool being a shared pool or a configured authorization in a full bandwidth, a sub-bandwidth or a bandwidth portion, Wherein, the transmitter (152; 252) is configured to send a sixth message (1171, 1176, 1177) having a low priority in the regular pool.

10. The user equipment according to claim 1, in, 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 the high priority, wherein the transmitter (152; 252) is configured to send a fourth message (1166, 1167) with 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.

11. The user equipment according to claim 1, in, 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.

12. The user equipment according to claim 1, in, After sending the first critical communication notification for the first time, the transmitter (152; 252) is configured to resend the first critical communication notification one or more times in the first resource pool (611; 711; 811; 911; 1011; 1111).

13. The user equipment according to claim 1, in, 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 (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).

14. The user equipment according to claim 1, in, The transmitter (152; 252) is configured to send the first critical communication notification at a first transmission power, 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) at a second transmission power, wherein the first transmission power is greater than the second transmission power.

15. The user equipment according to claim 1, in, At least one of the first critical communication notification and the second critical communication notification is side link control information including one or more side link control information data elements, wherein the side link control information data elements include at least one of a component carrier index, a subframe index, an SPS period, a transmission offset, a subchannel size, and an indication of whether frequency hopping is allowed.

16. The user equipment according to claim 1, in, 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, The first resource pool (611; 711; 811; 911; 1011; 1111) is allocated to a first component carrier among the multiple component carriers, and The second resource pool (622; 721; 821; 921; 1021; 1121) is allocated to a second component carrier among the multiple component carriers, wherein the second component carrier is different from the first component carrier.

17. The user equipment according to claim 1, in, 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, The first resource pool (611; 711; 811; 911; 1011; 1111) is allocated to a first component carrier among the multiple component carriers, and The second resource pool (622; 721; 821; 921; 1021; 1121) is also allocated to the first component carrier.

18. The user equipment according to claim 1, in, 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; 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 send the subframe bitmap received from the base station to another vehicle outside the coverage of the base station.

19. The user equipment according to claim 1, in, 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.

20. The user equipment according to claim 1, in, 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.

21. A system for wireless communication, in, 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 claim 1, The multiple user equipments (150, 250) include a first user equipment (150) and a second user equipment (250). wherein a first resource pool (611; 711; 811; 911; 1011; 1111) comprises a first plurality of resources for transmission, and wherein a second resource pool (622; 721; 821; 921; 1021; 1121) comprises a second plurality of resources for transmission, wherein a 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 a second message (661; 7 ... 61; 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; 721; 821; 921; 1021; 1121), and wherein the critical communication notification indicates a repetition period of repetition of the second message, 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 transmit 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) simultaneously with sending the critical communication notification, Therein, the first resource pool is defined as a shared resource pool or a commonly configured authorization or a commonly accessed bandwidth portion or an abnormally configured pool.

22. A method for wireless communication, in, 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; 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 method comprises: A first critical communication notification is sent by a transmitter (152; 252) of a user equipment 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) are to be sent in the second resource pool (622; 721; 821; 921; 1021; 1121), wherein the first critical communication notification indicates a repetition period of repetition of the second message, said 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 sent by said transmitter (152; 252) in said second resource pool (622; 721; 821; 921; 1021; 1121) simultaneously with said 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 by a receiver (154; 254) of the user equipment 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; 866; 867; 868; 869; 870; 871; 872; 873; 874; 875; 876; 877; 878; 879; 880; 881; 882; 883; 884; 885; 886; 887; 888; 889; 890; 891; 892; 893; 894; 895 63, 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), wherein the second critical communication notification indicates a repetition period of repetition of the fourth message, and wherein the second critical communication notification and the fourth message are sent simultaneously, 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), Wherein, the first resource pool is defined as a shared resource pool or a commonly configured authorization or a commonly accessed bandwidth portion or an abnormally configured pool, and / or The third resource pool is defined as a shared resource pool or a commonly configured authorization or a commonly accessed bandwidth portion or an abnormally configured pool.

23. A computer program product comprising a computer program for implementing the method according to claim 22 when it is executed on a computer or a signal processor.