Transmission method and device of sidelink positioning protocol message and computer readable medium

Abstract

A wireless communication method is disclosed. A wireless communication method includes determining, by a user equipment (UE), a configuration of at least one radio bearer of the user equipment for transmitting an SLPP (sidelink positioning protocol) message; and transmitting, by the UE, an SLPP message carried by at least one radio bearer according to the configuration, wherein the at least one radio bearer includes at least one of a DRB (Data Radio Bearer) or an SRB (Signaling Radio Bearer).

Description

Technical Field

[0001] The present disclosure generally relates to sidelink communication, and more particularly, to the transmission of sidelink positioning protocol messages. Background Art

[0002] Wireless communication technology is a key component of an increasingly interconnected global communication network. Wireless communication relies on precisely allocated time and frequency resources to transmit and receive wireless signals. Sidelink transmission allows two or more user equipments (UEs) to communicate with each other. SLPP (sidelink positioning protocol) is newly introduced for conveying control signaling for sidelink positioning. However, the mechanism for transmitting SLPP messages is not yet mature. Summary of the Invention

[0003] This summary is a brief description of some aspects of the present disclosure. It is not intended to limit the scope of the present disclosure.

[0004] According to one or more embodiments of the present disclosure, a wireless communication method is disclosed. The method includes determining, by a user equipment (UE), a configuration of at least one radio bearer of the UE for transmitting an SLPP (sidelink positioning protocol) message; and transmitting, by the UE according to the configuration, the SLPP message carried by the at least one radio bearer, where the at least one radio bearer includes at least one of a DRB (data radio bearer) or an SRB (signaling radio bearer).

[0005] According to one or more embodiments of the present disclosure, another wireless communication method is disclosed. The method includes obtaining, by a user equipment (UE), a MAC PDU carrying an SLPP message; and filtering, by a MAC layer of the UE, the MAC PDU based on two different predefined conditions to determine whether to send the MAC PDU to an upper layer of the UE.

[0006] According to some embodiments of the present disclosure, one or more wireless communication methods are further disclosed. These methods include combinations (in a general view or a specific view) of certain methods, aspects, elements, and steps disclosed in various embodiments of the present disclosure.

[0007] Another embodiment of the present disclosure provides a wireless communication device, including a memory storing one or more programs and one or more processors electrically coupled to the memory and configured to execute the one or more programs to perform any method, step, or combination thereof in the present disclosure.

[0008] Another embodiment of the present disclosure provides a non-transitory computer-readable storage medium storing one or more programs, which are configured to cause any method, step, or combination thereof in the present disclosure to be executed when executed by one or more processors.

[0009] The above aspects and other aspects and their embodiments are described in more detail in the drawings, the detailed description, and the claims. Description of the Drawings

[0010] Various exemplary embodiments of the present disclosure will be described in detail below with reference to the drawings. The drawings are provided for illustrative purposes only and depict only the exemplary embodiments of the present disclosure to facilitate the understanding of the present disclosure. Therefore, the drawings should not be regarded as limiting the breadth, scope, or applicability of the present disclosure. It should be noted that these drawings are not necessarily drawn to scale for clarity and ease of illustration.

[0011] Figure 1 is a schematic diagram of the hardware of a wireless communication device according to an embodiment of the present disclosure;

[0012] Figure 2 is a structural diagram of a device for sidelink communication according to an embodiment of the present disclosure;

[0013] Figure 3 is a structural diagram of a communication system according to an embodiment of the present disclosure;

[0014] Figures 4 - 5 is a schematic diagram of a UE for sidelink transmission;

[0015] Figure 6 shows an example schematic diagram of the filtering operation of the MAC layer of a receiving UE when the broadcast type of the UE is set to multicast or broadcast in the SCI;

[0016] Figure 7 shows an example schematic diagram of the filtering operation of the MAC layer of a receiving UE when the broadcast type of the UE is set to unicast in the SCI; and

[0017] Figures 8 - 9 is a schematic diagram of a UE for sidelink transmission. Detailed Description

[0018] Figure 1 is a schematic diagram of a wireless communication device according to an embodiment of the present disclosure. As Figure 1As shown, the terminal device may include a mobile terminal, such as a mobile phone, a smart phone, a laptop computer, a digital broadcast receiver, a personal digital assistant (PDA), a PAD, a portable media player (PMP), and a navigation device, as well as a fixed terminal, such as a digital television (TV) and a desktop computer. Hereinafter, it is assumed that the terminal is a mobile terminal. However, those skilled in the art will understand that the configuration according to the embodiments of the present disclosure can also be applied to a fixed terminal except for the components specifically for mobile purposes.

[0019] The terminal device may include a wireless communication unit. For example, the wireless communication unit may specifically be composed of a transmitter 61, a receiver 62, a memory 64, a processor 63, and a power supply unit 65 in the figure. Figure 1 A terminal device with various components is shown. However, it should be understood that not all of the shown components need to be implemented. On the contrary, more or fewer components may be implemented. In an embodiment, the foregoing transmitter may be a physical component of a transmission module.

[0020] Figure 2 is a structural diagram of a terminal device for sidelink communication according to an embodiment of the present disclosure. As Figure 2 shown, the terminal device 130 includes a memory 1303 and a processor 1304. The terminal device 130 may further include an interface 1301 and a bus 1302. The interface 1301, the memory 1303, and the processor 1304 are connected through the bus 1302. The memory 1303 is configured to store one or more instructions or one or more programs. The processor 1304 is configured to read the instructions to execute the technical solutions of the methods or steps disclosed in the present disclosure. The implementation principles and technical effects are similar, and will not be repeated here.

[0021] Figure 3 is a structural diagram of a communication system according to an embodiment of the present disclosure. As Figure 3 shown, in this embodiment, an example in which the network side device includes a base station (BS) 101 and the terminal device may include UEs 110, 120, or 130 is used to provide the description. The foregoing BS and UEs have the same functions as those in the foregoing embodiments, and will not be repeated here. The above devices or systems are configured to execute any steps or methods or combinations thereof disclosed in the present disclosure.

[0022] In sidelink applications, UEs (such as Figure 3The UEs 110, 120, and 130) in may need to perform sidelink positioning to notify other UEs of their location information. The SLPP (Sidelink Positioning Protocol) is introduced to convey the control signaling for sidelink positioning. The SLPP message can carry the positioning information of the UE, and it typically has sidelink (SL) positioning capabilities, auxiliary data transfer, and position measurement result transfer. For example, the capability transfer includes sidelink positioning capabilities that can be requested from a first UE to another second UE; the sidelink positioning capabilities of the first UE can be transferred from the first UE to the second UE. The auxiliary data includes at least one of SL-PRS (sidelink-positioning reference signal) configuration, the location information of the anchor UE, and other information helpful for sidelink UE positioning; the auxiliary data can be transferred between the first UE and the second UE. The measurement report transfer includes transferring the sidelink positioning measurement results or sidelink positioning position estimates from the first UE to the second UE. The SLPP message can be generated at the NAS (non-access stratum) layer and sent via the PC5 interface between UEs. In addition, in the AS (access stratum) layer, the SLPP message can be sent as an SL-SRB (signaling radio bearer) according to the control plane procedure, or alternatively as part of an SL-DRB (data radio bearer) according to the user plane procedure. To introduce the procedures for the NAS layer and the AS layer to send SLPP messages, among other things, the present disclosure provides the association of the broadcast types of SLPP messages between the NAS layer and the AS layer, and detailed solutions on how to send SLPP messages as a traditional SL-SRB, a new SL-SRB, or a dedicated SL-DRB in the AS layer.

[0023] According to one or more embodiments of the present disclosure, a new SL-SRB can be introduced for the SLPP message, and the upper layer of the UE can indicate the broadcast type of the SLPP message to the AS layer.

[0024] For SLPP messages, dedicated SL-SRBs specifically for SLPP messages (instead of the traditional SL-SRB0 to SL-SRB4) can be introduced in the AS layer. To convey SLPP messages, SL-SRBs can be generated in the SLPP layer (or NAS layer). As described above, SLPP messages can include capability transfer, auxiliary data transfer, and measurement report transfer. For example, capability transfer includes sidelink positioning capabilities that can be requested from a first UE to another second UE; the sidelink positioning capabilities of the first UE can be transferred from the first UE to the second UE. Auxiliary data includes at least one of SL-PRS (sidelink positioning reference signal) configuration, location information of the anchor UE, and other information helpful for sidelink UE positioning; the auxiliary data can be transferred between the first UE and the second UE. Measurement report transfer includes transferring sidelink positioning measurement results or sidelink positioning location estimates from the first UE to the second UE.

[0025] According to some examples, SLPP messages can support the transmission of all broadcast types, including broadcast, multicast, and / or unicast. When delivering an SLPP message from the NAS layer to the AS layer for transmission, the upper layer (e.g., NAS layer or SLPP layer) can indicate the broadcast type of the SLPP message to the lower layer (e.g., AS layer). Accordingly, the SL-SRB used to convey the SLPP message and transfer between AS layers can adopt the broadcast type indicated by the NAS layer. The supported broadcast types include "broadcast and multicast" and / or "unicast". The NAS layer can also indicate the broadcast type as "broadcast", "multicast", and / or "unicast" to distinguish "broadcast" from "multicast".

[0026] According to some examples, the broadcast type allocated by the NAS layer may be aligned with the destination layer 2 (L2) ID also allocated by the NAS layer. According to some examples, different broadcast types correspond to different types of destination L2 IDs. When the NAS layer allocates a broadcast type, the NAS layer may need to ensure that the allocated broadcast type is aligned with the type of the allocated destination L2 ID. The mapping between the type of the destination L2 ID and the broadcast type may be determined by the NAS layer of the transmitting UE (Tx UE). The destination L2 ID may identify the target of the data in the sidelink communication. For sidelink communication, the destination L2 ID may have a length of 24 bits. The destination L2 ID may be split into two bit strings in the MAC layer. One bit string may be the LSB part (16 bits) of the destination L2 ID, and this bit string may be forwarded to the physical layer of the Tx UE. It may identify the target of the expected data in the sidelink control information, and it is used for packet filtering in the physical layer of the Rx UE. The second bit string is the MSB part (8 bits) of the destination L2 ID, and this part may be carried in the MAC header. It is used for packet filtering in the MAC layer of the receiver. The source L2 ID may identify the sender of the data in the NR sidelink communication. The source L2 ID may have a length of 24 bits, and it may be split into two bit strings in the MAC layer. The first bit string is the LSB part (8 bits) of the source L2 ID, and it may be forwarded to the physical layer of the Tx UE. It identifies the source of the expected data in the sidelink control information and is used for packet filtering in the physical layer of the Rx UE. The second bit string is the MSB part (16 bits) of the source L2 ID, and the second bit string may be carried within the MAC header. This is used for packet filtering in the MAC layer of the Rx UE.

[0027] For example, as Figure 4As shown, a new side link signaling radio bearer SL-SRB5 can be introduced to convey SLPP messages. The broadcast type of the SLPP message conveyed by SL-SRB5 can be indicated by the NAS layer as "broadcast". The destination L2 ID is also set to a broadcast-like destination L2 ID for alignment. The use of the SLPP message can be capability transfer, auxiliary data transfer, or SL-PRS configuration transfer. Then, on the transmitting UE side (Tx UE), the PDCP (Packet Data Convergence Protocol), RLC (Radio link control), MAC (Medium Access Control), and PHY (Physical) layers of the Tx UE can control data or SL-SRB5 or SLPP messages according to the broadcast mode in AS transmission. On the receiver side (Rx UE), the PDCP, RLC, MAC, and PHY layers of the Rx UE can also control data or SL-SRB5 or SLPP messages in a broadcast mode.

[0028] In other examples, the broadcast type of the SLPP message conveyed by SL-SRB5 can be indicated by the NAS layer as "unicast". At the same time, the destination L2 ID is also set to a unicast-like destination L2 ID for alignment, and the use of the SLPP message can be capability transfer, auxiliary data transfer, SL-PRS configuration transfer, or location measurement transfer. Then, on the transmitting UE side (Tx UE), the PDCP, RLC, MAC, and PHY layers of the Tx UE can control data / SL-SRB5 / SLPP messages in a unicast mode in AS transmission. On the receiver side (Rx UE), the PDCP, RLC, MAC, and PHY layers of the Rx UE can control data / SL-SRB5 / SLPP messages in a unicast mode.

[0029] In addition, if the NAS layer indicates to process the SL-SRB in a multicast or broadcast manner, the sidelink control channel (SCCH) configuration used by the SL-SRB for SLPP messages can be the same as the configuration of the predefined SL-SRB0 or SL-SRB4; alternatively, if the NAS layer indicates to process the SL-SRB in a unicast manner, the SCCH configuration used by the SL-SRB for SLPP messages can be the same as the configuration of SL-SRB1, SL-SRB2, or SL-SRB3.

[0030] According to one or more embodiments of the present disclosure, a new SL-SRB can be introduced for transmitting SLPP messages. On the transmitting UE side (Tx UE), the AS layer treats all SLPP messages as a presumed broadcast type agreed upon by the service provider. On the receiver UE side (UE Rx), the MAC layer performs two filtering operations based on two different conditions.

[0031] To handle SLPP messages, a dedicated SL-SRB can be introduced in the AS layer instead of the predefined SL-SRB0 to SL-SRB4 to convey SLPP messages generated at the NAS layer (e.g., the SLPP layer). The SLPP messages can include capability transfer, auxiliary data transfer, or measurement report transfer.

[0032] SLPP messages can support all broadcast types. Depending on the different destination L2 ID settings of the SLPP messages at the NAS layer (e.g., the SLPP layer), the SLPP messages generated at the NAS layer (e.g., the SLP layer) can be broadcast or multicast to multiple receiving UEs, or unicast to a single receiving UE. However, during AS layer transmission, the broadcast type of the SLPP message and its corresponding SL-SRB can always be assumed by each AS layer (including the PDCP, RLC, MAC, and PHY layers) to be one of the "broadcast", "broadcast and / or multicast", or "unicast" broadcast types. According to some examples, the broadcast type cannot be dynamically indicated by the upper layer; instead, the broadcast type can be predefined among service providers. According to some examples, the broadcast type of the SLPP message and the corresponding SL-SRB do not change over time or according to the SLPP message content. In Figure 5 these examples shown, the broadcast type of the SL-SRB5 containing the SLPP message does not need to be aligned with the destination L2 ID assigned by the upper layer NAS layer. Regardless of whether the destination L2 ID is assigned by the upper layer as a broadcast-like, multicast-like, or unicast-like destination L2 ID, the SLPP message and its corresponding SL-SRB can always be treated or assumed by the PDCP, RLC, MAC, and PHY layers as a single broadcast type (broadcast, multicast, broadcast / multicast, or unicast). In addition, the SCCH configuration used by the SL-SRB can be the same as that of SL-SRB0 or SL-SRB4.

[0033] Since the destination L2 ID may not be aligned with the broadcast type as usual, a new method is introduced to identify the transmission block (TB) for a specific UE. According to some embodiments of the present disclosure, if the broadcast type indicator of the SLPP message and / or the broadcast type indicator of the corresponding SL-SRB is one of "broadcast" or "multicast" (which means that the broadcast type indicator in the SCI (sidelink control information) scheduling the PSSCH containing the SLPP message is set to "broadcast" or "multicast"), the receiving MAC layer may first determine whether any of the following conditions is met:

[0034] (1) The DST field of the decoded MAC PDU subheader is equal to the 8 most significant bits (MSB) of any one of the UE's destination layer 2 IDs, and the 16 least significant bits (LSB) of this destination layer 2 ID of the UE are equal to the target ID in the corresponding SCI; and

[0035] (2) The DST field of the decoded MAC PDU subheader is equal to the 8 MSB of any one of the UE's source layer 2 IDs, the 16 LSB of this source layer 2 ID of the UE are equal to the destination ID in the corresponding SCI, and the SRC field of the decoded MAC PDU subheader is equal to the 16 MSB of any one of the UE's destination layer 2 IDs, and the 8 LSB of this destination layer 2 ID of the UE are equal to the source ID in the corresponding SCI.

[0036] If any of the above conditions (1) and (2) is met, the MAC entity of the receiving UE may deliver the decoded MAC PDU (from the received packet) to the disassembling and demultiplexing entity. If the broadcast type indicator of the SLPP message or the corresponding SL-SRB is set to one of "broadcast", "multicast" or "broadcast and / or multicast" in the SCI, the receiving MAC entity may need to filter the received MAC PDU twice not only according to condition (1) but also according to condition (2). Only when none of these conditions is met can the receiving UE discard the transmission block (TB) and not process the next step or deliver it to the higher layer.

[0037] Figure 6 An example schematic diagram showing the filtering operation of the MAC layer of the receiving UE when the broadcast type of the UE is set to multicast or broadcast in the SCI is shown. Generally, the transmitting UE (Tx UE) provides the source L2 ID (24 bits) and the destination L2 ID (24 bits) associated with the SLPP message; the source L2 ID and the destination L2 ID can be assigned by the NAS layer of the Tx UE.

[0038] On the other hand, to receive the TB, the receiving UE (Rx UE) also has a source L2 ID (24 bits) and a destination L2 ID (24 bits). The source L2 ID and the destination L2 ID of the Rx UE can be given by the NAS layer or the application layer (a layer higher than the NAS layer) of the Rx UE. The source L2 ID and the destination L2 ID of the Rx UE are configured independently of the source L2 ID and the destination L2 ID of the SLPP message on the Tx UE side.

[0039] When sending a TB with an SLPP message, the Tx UE will set the 8 MSB bits of the destination L2 ID in the MAC PDU sub-header and set the 16 bits of the destination L1 ID in the transmitted SCI. The Tx UE will set the 16 MSB bits of the source L2 ID in the MAC PDU sub-header and set the 8 LSB bits of the source L1 ID in the transmitted DCI.

[0040] In condition (1), after the Rx UE receives the TB of the SLPP message, the MAC layer of the Rx UE will check or determine whether the 8 MSB bits of the received destination L2 ID in the MAC PDU sub-header are equal to or match any of the 8 MSB bits of the destination L2 ID of the Rx UE. According to some examples, the prerequisite for condition (1) is that the Rx UE should be a UE whose 16 LSB (least significant bit) destination L2 ID is equal to or matches the destination L1 ID in the corresponding SCI.

[0041] In condition (2), after the Rx UE receives the TB of the SLPP message, the MAC entity of the Rx UE will check whether the 8 MSB bits of the received destination L2 ID in the MAC PDU sub-header are equal to any of the 8 MSB bits of the source L2 ID of the Rx UE, and check whether the 16 MSB bits of the received source L2 ID in the MAC PDU sub-header are equal to any of the 16 MSB bits of the destination layer 2 ID of the Rx UE. The prerequisite for condition 2 is that the Rx UE should be a UE whose 16 LSB (least significant bit) source L2 ID is equal to the destination L1 ID in the corresponding SCI, and the Rx UE should be a UE whose 8 LSB of the destination L2 ID is equal to the source L1 ID in the corresponding SCI.

[0042] According to some embodiments of the present disclosure, if the broadcast type of the SLPP message and / or the corresponding SL-SRB is unicast (for example, when the broadcast type indicator in the SCI scheduling the PSSCH containing the SLPP message is "unicast"), the receiving MAC entity may need to first determine whether one of the following conditions is met:

[0043] (1) The DST field of the decoded MAC PDU sub-header is equal to any one of the 8 MSBs of the destination layer 2 ID of the UE, and the 16 LSBs of the destination layer 2 ID of the UE are equal to the destination ID in the corresponding SCI; and

[0044] (2) The DST field of the decoded MAC PDU sub-header is equal to any one of the 8 MSBs of the source layer 2 ID of the UE, the 16 LSBs of the source layer 2 ID of the UE are equal to the destination ID in the corresponding SCI, and the SRC field of the decoded MAC PDU sub-header is equal to the 16 MSBs of any one of the destination layer 2 IDs of the UE, and the 8 LSBs of the destination layer 2 ID of the UE are equal to the source ID in the corresponding SCI.

[0045] Figure 7 The example schematic diagram shows the filtering operation of the MAC layer of the receiving UE when the broadcast type of the UE is set to unicast in the SCI. The operations under condition (1) and condition (2) have been described above and will not be repeated here.

[0046] If any one of condition (1) or condition (2) is satisfied, the MAC entity of the receiving UE can deliver the decoded MAC PDU to the disassembling and demultiplexing entity. If the broadcast type indicator of the SLPP message and / or the broadcast type indicator of the corresponding SL-SRB are set to "unicast" in the SCI, the receiving MAC entity of the receiving UE may need to filter the decoded MAC PDU twice to determine that not only condition (2) is satisfied, but also condition (1). Alternatively, if neither condition (1) nor condition (2) is satisfied, the receiving UE can discard the TB (transport block) and not process the next step or deliver it to the higher layer, because the receiving UE determines that the received TB is not for the receiving UE.

[0047] Table 1 below shows the filtering conditions for identifying the TB received by the intended destination in different SCI indicators and destination L2 IDs. For example, when the SCI indicates that the TB is sent under the broadcast broadcast type, the receiving UE can use the above condition (1) when the destination L2 ID is the broadcast destination L2 ID. The receiving UE can use the above condition (1) when the destination L2 ID is the multicast destination L2 ID. The receiving UE may need to use the above two conditions (1) and (2) when the destination L2 ID is the unicast destination L2 ID, which means that if any one of condition (1) or condition (2) is satisfied, the MAC layer of the receiving UE will provide the MAC PDU for further processing.

[0048] Table 1

[0049]

[0050] According to some embodiments of the present disclosure, the SCI may include a new broadcast type indicator (in addition to traditional broadcast, multicast, and unicast), and the broadcast type indicator is dedicated to the SLPP message. If the new broadcast type indicator in the SCI is received, the MAC of the receiving UE will read the new broadcast type indicator in the SCI and perform two filtering operations based on the above conditions (1) and (2). When either condition (1) or (2) is met, the MAC of the receiving UE may provide the MAC PDU to the upper layer.

[0051] According to Figure 8 Some embodiments of the present disclosure as shown may introduce two dedicated SL-SRBs for the SLPP message. Optionally, one of the new SL SRBs may be used to convey broadcast or multicast SLPP messages; the other SL-SRB may be used to convey unicast SLPP messages.

[0052] According to some examples, two dedicated SL-SRBs may be introduced in the AS layer (optionally, instead of SL-SRB0 to SL-SRB4) to convey SLPP messages generated at the SLPP layer (NAS layer). The SLPP messages may include capability transfer, auxiliary data transfer, or measurement report transfer.

[0053] Between the two SL-SRBs, one SL-SRB (e.g., SL-SRB5) may be used to convey broadcast and / or multicast SLPP messages; the other SL-SRB (e.g., SL-SRB6) may be used to convey unicast SLPP messages. The mapping of the SL-SRB to the corresponding broadcast type may be predefined by the service provider. For example, SL-SRB5 may be used for broadcast and / or multicast SLPP messages, and SL-SRB6 may be used for unicast SLPP message delivery.

[0054] Additionally or alternatively, the SCCH configuration used by the broadcast or multicast SL-SRB may be the same as the SCCH configuration of SL-SRB0 or SL-SRB4. The SCCH configuration used by the unicast SL-SRB may be the same as the SCCH configuration of SL-SRB1, SL-SRB2, or SL-SRB3.

[0055] According to some embodiments of the present disclosure, the SLPP message may be conveyed by any one of SL-SRB0 to SL-SRB4.

[0056] According to some examples, different SRBs are used to convey different types of control signaling. For example, a sidelink SRB (e.g., SL-SRB0) can be used to send PC5-S messages before PC5-S security is established, where the sidelink transmission can be broadcast or multicast. Alternatively, another sidelink SRB (e.g., SL-SRB1) can be used to send PC5-S messages to establish PC5-S security, where the sidelink transmission is unicast. Alternatively, a sidelink SRB (e.g., SL-SRB2) can be used to send PC5-S messages after PC5-S security has been established, where the transmission is protected and the broadcast type is unicast. Alternatively, a sidelink SRB (e.g., SL-SRB3) can be used to send PC5-RRC signaling, where the transmission is protected and is sent only after PC5-S security has been established, and where the broadcast type of the transmission is unicast.

[0057] According to some examples, SL-SRB0 or SL-SRB4 can be used to convey broadcast and / or multicast SLPP messages; SL-SRB1, SL-SRB2, or SL-SRB3 can be used to convey unicast SLPP messages. In these examples, the SLPP messages are multiplexed with the original messages in SL-SRB0 / 1 / 2 / 3 / 4. Alternatively or additionally, SL-SRB0 / 1 / 2 / 3 / 4 are used to send SLPP messages during a specific period, and at other times, the same SL-SRB0 / 1 / 2 / 3 / 4 can be used to send original messages other than SLPP messages. In the AS layer transmission according to these examples, the broadcast type of the SLPP message can follow the broadcast type of the SL-SRB used to convey the SLPP message. Similarly, in the AS layer transmission according to these examples, the transmission settings of the SLPP message can follow the transmission settings of the SL-SRB used to convey the SLPP message.

[0058] In addition, the SL-SRB can indicate whether the current SL-SRB is used to send SLPP messages (or multiplexed with SLPP messages). An indication can be added in the SCCH configuration (i.e., each SL-SRB configuration / format). For example, the NAS layer can indicate whether the SL-SRB is used to send SLPP messages or multiplexed with SLPP messages.

[0059] According to some embodiments, the operations of different layers for the transmission of SLPP messages are described as follows.

[0060] PDCP at the Tx UE. When the PDCP layer of the Tx UE receives a PDCP SDU from the upper layer, each received SL-SRB can be associated with a PDCP entity. According to some embodiments, the PDCP layer knows the broadcast type of the current SLPP message and / or its associated SL-SRB.

[0061] For the SLPP message (received from the upper layer) and / or the associated SL-SRB, the PDCP layer of the Tx UE may determine whether encryption and / or integrity protection should be performed on the SL-SRB, or may determine the PDCP data PDU format for the SL-SRB. For the transmitting PDCP entity, the PDCP layer may determine whether encryption and / or integrity protection should be performed on the SL-SRB. For example, if the SL-SRB is a unicast SL-SRB, encryption and / or integrity protection may be performed. If the SL-SRB is a broadcast SL-SRB and / or a multicast SL-SRB, encryption and / or integrity protection may not be performed.

[0062] The PDCP layer of the Tx UE may also determine the PDU format of the PDCP data for the SL-SRB. It should be noted that the PDCP PDU format may be applied to both the transmitting PDCP entity and the receiving PDCP entity. For example, if the SL-SRB is a broadcast or multicast SL-SRB, the data PDU formats for the multicast and broadcast sidelink DRBs and for sidelink SL-SRB0 and sidelink SL-SRB4 should be applied to the SL-SRB. Alternatively, if the SL-SRB is a unicast SL-SRB, the data PDU format for the unicast sidelink SL-SRB may be applied to the SL-SRB.

[0063] RLC at the Tx UE. After the PDCP layer, the PDCP PDU corresponding to the SL-SRB (which contains the SLPP message) will become the input of the RLC layer. The RLC layer may determine the UM (Unacknowledged Mode) RLC mode or the AM (Acknowledged Mode) RLC mode according to the broadcast type of the SLPP message / PDCP PDU / RLC SDU / SL-SRB. In some examples, if the SLPP message is broadcast or multicast, only the UM mode is applied.

[0064] Additionally or alternatively, the RLC determines the RLC PDUs for different AM, UM, or TM modes. In some examples, the broadcast / multicast SLPP message may use the UMD (unacknowledged mode data) PDU with a 6- or 12-bit SN (sequence number). The unicast SLPP message should use the AMD (acknowledged mode data) PDU with a 12-bit or 18-bit SN. It should be noted that the RLC PDU format may be used for both the transmitting RLC entity and the receiving RLC entity. The output of the RLC layer is the RLC PDU.

[0065] MAC at the Tx UE. After that, the RLC PDU will become the input of the MAC layer, and the MAC layer can process the RLC PDU. The MAC layer can determine, for example, the source L2 ID, destination L2 ID, and broadcast type of the SLPP message according to the indication from the upper layer. A new LCID can be introduced for the SLPP message, for example, the value 20. Table 2 below shows a list of LCID examples with the newly introduced LCID.

[0066] Table 2

[0067]

[0068] PHY layer at the Tx UE. The broadcast type, source L1 ID, and destination L1 ID can be set by the UE in the level 2 SCI according to the indication from the MAC layer. Then, the Physical Sidelink Control Channel (PSCCH) containing the SCI and the corresponding Physical Sidelink Shared Channel (PSSCH) containing the data scheduled by the SCI with the SLPP message will be sent to other UEs in the PC5 interface.

[0069] PHY layer at the Rx UE. The Rx UE receives the SCI and the corresponding PSSCH containing the SLPP message, and then the Rx UE delivers the received material to the upper layer.

[0070] MAC layer at the Rx UE. According to different broadcast types (e.g., broadcast / multicast or unicast) indicated in the SCI, the MAC layer of the Rx UE decodes the LCID and filters the destination L2 ID and / or source L2 ID using the corresponding filtering rules (e.g., the above conditions (1) and (2)). If the MAC layer verifies that the received TB is for the current UE, the TB will be further processed and finally delivered to the upper layer.

[0071] RLC at the Rx UE. If the SLPP message is a multicast or broadcast SLPP message, when setting the parameter RX_Next_Reasmbly, the Rx UM RLC entity can set the SN of the first received UMD PDU containing the SN. When setting the parameter RX_Next_Highest, the Rx UM RLC entity can be set to the SN of the first received UMD PDU containing the SN.

[0072] PDCP at the Rx UE. The PDCP layer of the Rx UE may determine whether to send a PDCP SDU with an indication to the upper layer. Specifically, in order to receive an SL-SRB, the PDCP layer of the Rx UE may later send the corresponding PDCP SDU with an indication to the upper layer, where the indication indicates that the PDCP PDU is a PC5-S message, a sidelink discovery message, or an SLPP message. The PDCP layer of the Rx UE may determine whether decryption and / or integrity verification should be performed on the SL-SRB. Regarding RX_NEXT, for a broadcast or multicast SLPP message, the initial value of the SN part of RX_NEXT is (x + 1) modulo (2 [sl-PDCP-SN-Size] ), where x is the SN of the first received PDCP data PDU. Regarding RX_DELIV, the initial value of the SN part of RX_DELIV is (x – 0.5 × 2[sl-PDCP-SN-Size–1]) modulo (2[sl-PDCP-SN-Size]), where x is the SN of the first received PDCP data PDU.

[0073] According to some embodiments of the present disclosure, a priority indicator may be introduced to indicate that the SLPP message has a higher priority. An indication may be introduced to identify the user data bearer containing the SLPP message.

[0074] According to some examples, the SLPP message may be conveyed by the user plane to be sent to one or more UEs. The signaling flow in the Tx UE is, in sequence, the NAS layer (SLPP layer), the SDAP layer, the PDCP layer, the RLC layer, the MAC layer, and the PHY layer. After the Rx UE receives the SLPP message contained in the PSSCH at the PHY layer, the signaling flow in the Rx UE is, in sequence, the PHY layer, the MAC layer, the RLC layer, the PDCP layer, the SDAP layer, and the NAS layer (SLPP layer).

[0075] The purpose of the SDAP layer is to map one or more PC5 QoS flows to an SL-DRB. One PC5 QoS flow is mapped to only one SL-DRB for transmission at a time on the NR sidelink. Multiple PC5 QoS flows may be mapped to one SL-DRB.

[0076] The core network configures the user data transmission manner in the AS layer (including SDAP, PDCP, RLC, MAC, and PHY) from the Tx UE to the Rx UE via Uu RRC signaling, pre-configuration signaling, or PC5 RRC signaling.

[0077] In Uu RRC configuration or pre-configuration, each QoS flow can be associated with a corresponding QoS profile and QoS flow ID (up to 2048 per UE). The QoS profile has a standard QoS PQI (up to 255) and a non-standard PQI (PC5 QoS identifier), and the QoS profile includes the priority of the corresponding QoS flow (with a value from 1 to 8). Multiple QoS profiles can be mapped to one SL-DRB, and multiple QoS profiles can have a signaling type configured in the SL-SDAP configuration, which means that one SL-DRB can have one signaling type. In the PC5-RRC configuration, UE A indicates that a specific number (up to 64) of QoS flows with the same destination are mapped to one SL-DRB. Figure 7 An example structure of Uu RRC signaling, pre-configuration, and PC5-RRC signaling for SL-DRB configuration is shown.

[0078] An SL-DRB can have two priorities.

[0079] QoS flow priority. If the priority level of the QoS flow priority is not presented in the PC5 QoS profile, the default value will be applied. The priority indication can be provided to the QoS feature mapping via the default PQI. According to some examples, the lower the packet delay budget, the lower the numerical value of the priority. Here, a lower number means a higher priority. Alternatively, the PQI can be used together with the indicated priority of the application, which can override the default priority level of the PQI.

[0080] Logical channel priority. The logical channel priority can be included in the SL-LogicalChannelConfig parameter to indicate the priority of the logical channel for transmitting SLPP messages. If the SLPP message generated at the NAS layer is multiplexed with user data, the SDAP layer will also map the QoS flow containing the SLPP message to the SL-DRB. There are several ways to ensure that the SLPP message contained in the user data will have a higher priority.

[0081] An identifier dedicated to the PC5 QoS flow or SL-DRB can be introduced. This identifier indicates whether the PC5 QoS flow or SL-DRB contains an SLPP message, enabling the NAS layer to notify the lower layer that the QoS flow containing the SLPP message is different from other QoS flows. The lower layer can assign a different priority to the SL-DRB containing the SLPP message compared to other SL-DRBs without the SLPP message. Additionally, the identifier may come from the NAS layer to the AS layer. For example, the identifier can be indicated in the SL-QoS-Profile or sl-PQI. Alternatively, the identifier can be indicated in the PQI value. Thus, some PC5 QoS flows containing SLPP messages are treated differently. The identifier can be included in the SL-SDAP-Config or SL-RadioBearerConfig parameters in the RRC signaling or pre-configuration. The identifier can also be included in the SL-SDAP-ConfigPC5 or slrb-Config parameters in the PC5-RRC signaling. For example, the identifier can be a boolean value.

[0082] For the QoS flow containing the SLPP message, a new QoS flow to SL-DRB mapping rule can be introduced in at least one of the RRC signaling, pre-configuration, or PC5-RRC signaling. The SDAP layer can map the QoS flow containing the SLPP message to one or more dedicated SL-DRBs according to the upper layer indication. The new mapping rule of the QoS flow to the SL-DRB can be configured in the SL-SDAP-Config or SL-SDAP-ConfigPC5 signaling.

[0083] Alternatively or additionally, for the SL-DRB or PC5 QoS flow containing the SLPP message, the SL-DRB shall be mapped to the highest logical channel priority (the same as the priority of the SCCH, and the value of the logical channel priority is 1). Additionally, this mapping can be configured in the SL-RLC-BearerConfig.

[0084] Alternatively or additionally, the NAS layer maps the SLPP message to the highest priority user data packet (e.g., the QoS flow with a priority index equal to 1). Additionally, the SLPP message and the highest priority user data packet can have the same source L2 ID, destination L2 ID, and broadcast type.

[0085] Alternatively or additionally, a priority indication for the SL-DRB may be introduced. An IE (information element) may be introduced in SL-SDAP-Config, SL-SDAP-ConfigPC5, SL-RadioBearerConfig, or slrb-Config to indicate the priority level of the corresponding SL-DRB. For example, the priority level value may be selected from {1, 2, 3, 4, 5, 6, 7, 8}, where 1 indicates the highest priority. In addition, among all SL-DRBs, the highest priority value may be assigned to one or more SL-DRBs that contain the SLPP message.

[0086] Alternatively or additionally, the PDCP layer may be indicated via RRC signaling, pre-configuration signaling, or PC5-RRC signaling to map the QoS flow containing the SLPP message to the default SL-DRB for one destination. In addition, the default SL-DRB that contains the SLPP message may be assigned the highest logical channel priority or SL-DRB priority.

[0087] According to some embodiments of the present disclosure, a wireless communication method is provided. The method includes determining, by a user equipment (UE), a configuration of at least one radio bearer of the UE for transmitting a SLPP (sidelink positioning protocol) message; and transmitting, by the UE according to the configuration, the SLPP message carried by the at least one radio bearer, where the at least one radio bearer includes at least one of a DRB (data radio bearer) or an SRB (signaling radio bearer).

[0088] According to some exemplary embodiments of various embodiments, the SRB is dedicated to carrying the SLPP message.

[0089] According to some exemplary embodiments of various embodiments, the wireless communication method further includes determining, by the UE, an LCID (logical channel identity) dedicated to the SRB.

[0090] According to some exemplary embodiments of various embodiments, the configuration of the at least one radio bearer includes an indication of the broadcast type of the SLPP message from the NAS layer to the AS layer of the UE.

[0091] According to some exemplary embodiments of various embodiments, the broadcast type indication indicates at least one of unicast, multicast, or broadcast.

[0092] According to some exemplary embodiments of various embodiments, the wireless communication method further includes transmitting, by the UE according to the configuration, the SLPP message carried by the SRB, where the configuration includes a predefined broadcast type of the SRB.

[0093] According to some exemplary embodiments of various embodiments, the wireless communication method further includes transmitting, by a UE according to a configuration, an SLPP message carried by two SRBs. The configuration includes a predefined broadcast type for each of the two SRBs. The predefined broadcast type of one of the two SRBs is at least one of broadcast or multicast, and the predefined broadcast type of the other SRB of the two SRBs is unicast.

[0094] According to some exemplary embodiments of various embodiments, at least one SRB corresponding to at least one radio bearer is at least one of SL-SRB0, SL-SRB1, SL-SRB 2, SL-SRB3, or SL-SRB4.

[0095] According to some exemplary embodiments of various embodiments, the wireless communication method further includes sending, by an AS layer of a UE to a NAS layer of the UE, a first indication to indicate whether at least one SRB is used to send an SLPP message.

[0096] According to some exemplary embodiments of various embodiments, the first indication is indicated in a sidelink control channel configuration.

[0097] According to some exemplary embodiments of various embodiments, each SRB of at least one SRB corresponding to each radio bearer of at least one radio bearer has a different SRB type.

[0098] According to some exemplary embodiments of various embodiments, a radio bearer includes at least one DRB, and the configuration includes a second indication to indicate whether the at least one DRB contains an SLPP message.

[0099] According to some exemplary embodiments of various embodiments, a radio bearer includes at least one DRB, and the configuration includes a third indication for indicating whether a QoS flow corresponding to the DRB contains an SLPP message.

[0100] According to some exemplary embodiments of various embodiments, a radio bearer includes at least one DRB, and the configuration includes a fourth indication for indicating the priority of the DRB.

[0101] According to some exemplary embodiments of various embodiments, a radio bearer includes at least one DRB, and the configuration includes a QoS flow to DRB mapping rule for a QoS flow including an SLPP message.

[0102] According to some exemplary embodiments of various embodiments, the configuration includes the priority of a logical channel of a DRB or the priority of a QoS flow of an SLPP message, where the priority of a physical channel of the DRB or the priority of a QoS flow of the SLPP message has the highest priority.

[0103] According to some embodiments of the present disclosure, a wireless communication method is disclosed. The method includes: obtaining, by a user equipment (UE), a MAC PDU carrying an SLPP message; and filtering, by a MAC layer of the UE, the MAC PDU based on two different predefined conditions to determine whether to send the MAC PDU to a disassembling and demultiplexing entity.

[0104] According to some exemplary implementations of various embodiments, filtering the MAC PDU includes determining at least one of the following two predefined conditions: (1) the DST field of the decoded MAC PDU sub-header is equal to the 8 MSBs of any one of the destination layer 2 IDs of the UE, where the 16 LSBs of the destination layer 2 ID of the UE are equal to the destination ID in the corresponding SCI (sidelink control information); or (2) the DST field of the decoded MAC PDU sub-header is equal to the 8 MSBs of any one of the source layer 2 IDs of the UE, where the 16 LSBs of the source layer 2 ID of the UE are equal to the destination ID in the corresponding SCI, and the SRC field of the decoded MAC PDU sub-header is equal to the 16 MSBs of any one of the destination layer 2 IDs of the UE, where the 8 LSBs of the destination layer 2 ID of the UE are equal to the source ID in the corresponding SCI.

[0105] According to some embodiments of the present disclosure, various wireless communication methods are disclosed. The wireless communication methods include any possible combination of the selection of any of the steps, elements, or methods, aspects, and their general derivatives disclosed in the present disclosure.

[0106] The present disclosure is described with reference to the accompanying drawings to enable those of ordinary skill in the art to make and use the present disclosure. The present disclosure is not limited to the exemplary embodiments and applications described and illustrated herein. In addition, the specific order and / or hierarchy of the steps in the methods disclosed herein are merely exemplary methods. Based on design preferences, the specific order or hierarchy of the steps of the disclosed methods or processes can be rearranged while remaining within the scope of the present disclosure. Thus, those of ordinary skill in the art will understand that the methods and techniques disclosed herein present various steps or actions in an exemplary order and that the present disclosure is not limited to the specific order or hierarchy presented unless otherwise expressly stated.

[0107] The present disclosure aims to cover any possible variations, uses, combinations, or adaptive changes of the present disclosure that follow the general principles of the present disclosure, and includes knowledge and conventional technical means that are well known in the art and not disclosed in this application.

[0108] It should be understood that the present disclosure is not limited to the exact structures or operations described above and shown in the drawings, and various modifications and changes can be made without departing from the scope of the present application. The scope of the present application is only limited by the appended claims.

[0109] The above-described methods, devices, processes, circuits, and logics can be implemented in many different ways and in many different combinations of hardware and software. For example, all or part of the embodiments can be circuits including an instruction processor or controller, such as a central processing unit (CPU), a microcontroller, or a microprocessor; or as an application specific integrated circuit (ASIC), a programmable logic device (PLD), or a field programmable gate array (FPGA); or as a circuit including discrete logic or other circuit components, including analog circuit components, digital circuit components, or both; or any combination thereof. For example, the circuit can include discrete interconnected hardware components, or can be combined on a single integrated circuit die, distributed among multiple integrated circuit dies, or implemented in a multi-chip module (MCM) of multiple integrated circuit dies in a common package.

[0110] Accordingly, the circuit can store or access instructions for execution, or can implement its functions only in hardware. The instructions can be stored in a tangible storage medium other than transient signals, such as flash memory, random access memory (RAM), read only memory (ROM), erasable programmable read only memory (EPROM); or stored on a magnetic disk or an optical disk, such as a compact disc read only memory (CDROM), a hard disk drive (HDD), or other magnetic disk or optical disk; or in or on another machine-readable medium. A product, such as a computer program product, can include a storage medium and instructions stored in the medium or on the medium, and when the instructions are executed by a circuit in a device, the instructions can cause the device to implement any of the processes described above or shown in the drawings.

[0111] These embodiments may be distributed. For example, a circuit may include multiple different system components, such as multiple processors and memories, and may span multiple distributed processing systems. Parameters, databases, and other data structures may be stored and managed separately, may be incorporated into a single memory or database, may be logically and physically organized in many different ways, and may be implemented in many different ways. Example embodiments include linked lists, program variables, hash tables, arrays, records (e.g., database records), objects, and implicit storage mechanisms. Instructions may form part of a single program (e.g., a subroutine or other code segment), may form multiple separate programs, may be distributed across multiple memories and processors, and may be implemented in many different ways. Example embodiments include stand-alone programs, as well as part of a library, such as a shared library like a Dynamic Link Library (DLL). For example, the library may contain shared data and one or more shared programs that include instructions for performing any of the processing described above or shown in the figures when executed by the circuit.

[0112] In some examples, each unit, subunit, and / or module of the system may include a logic component. Each logic component may be hardware or a combination of hardware and software. For example, each logic component may include an application specific integrated circuit (ASIC), a field programmable gate array (FPGA), digital logic circuitry, analog circuitry, a combination of discrete circuits, gates, or any other type of hardware or a combination thereof. Alternatively or additionally, each logic component may include memory hardware, such as a portion of a memory, for example, that includes instructions executable by a processor or other processor to implement one or more of the characteristics of the logic component. When any of the logic components includes a portion of a memory that includes instructions executable by a processor, the logic component may or may not include a processor. In some examples, each logic component may simply be a portion of a memory or other physical memory that includes instructions executable by a processor or other processor to implement the characteristics of the corresponding logic component, and the logic component does not include any other hardware. Because each logic component includes at least some hardware even when the included hardware includes software, each logic component may be interchangeably referred to as a hardware logic component.

[0113] The second act can be said to be "responsive to" the first act, regardless of whether the second act is directly or indirectly caused by the first act. The second act can occur at a much later time than the first act and still be responsive to the first act. Similarly, even if intermediate acts occur between the first act and the second act, and even if one or more intermediate acts directly cause the second act to be performed, the second act can still be said to be responsive to the first act. For example, if the first act sets a flag, a third act later initiates the second act, and whenever the flag is set, the second act can be responsive to the first act.

[0114] For clarification and notice hereby given to the public, the phrase " , , … and <n>at least one of "or"< / n> , ,… <n>or at least one of its combinations "or"< / n> , ,… and / or <n>"is defined by the applicant in the broadest sense and replaces any other implicit definition above or below, and is used to represent one or more elements selected from a group including A, B, … and N, unless the applicant expressly states to the contrary. In other words, the phrase represents any combination of one or more elements among elements A, B, … or N, including any single element alone or a combination of that one element with one or more other elements, and the other elements may also combinatorially include additional elements not listed."< / n>

Claims

1. A wireless communication method, comprising: determining, by a user equipment (UE), a configuration of at least one radio bearer of the UE for transmitting a SLPP (Sidelink Positioning Protocol) message; and transmitting, by the UE according to the configuration, the SLPP message carried by the at least one radio bearer, wherein the at least one radio bearer includes at least one of a DRB (Data Radio Bearer) or an SRB (Signaling Radio Bearer).

2. The method according to claim 1, wherein The SRB is specifically used to carry the SLPP message.

3. The method according to claim 2, further comprising: determining, by the UE, an LCID (Logical Channel Identity) dedicated to the SRB.

4. The method according to claim 2, wherein, The configuration of the at least one radio bearer includes a broadcast type indication of the SLPP message from the NAS layer to the AS layer of the UE.

5. The method according to claim 4, wherein The broadcast type indication indicates at least one of unicast, multicast, or broadcast.

6. The method according to claim 2, further comprising: transmitting, by the UE according to the configuration, the SLPP message carried by the SRB, wherein the configuration includes a predefined broadcast type of the SRB.

7. The method according to claim 2, further comprising: transmitting, by the UE according to the configuration, the SLPP message carried by two SRBs, wherein the configuration includes a predefined broadcast type for each of the two SRBs, the predefined broadcast type of one SRB within the two SRBs is at least one of broadcast or multicast, and the predefined broadcast type of the other SRB within the two SRBs is unicast.

8. The method according to claim 1, wherein At least one SRB corresponding to the at least one radio bearer is at least one of SL-SRB0, SL-SRB1, SL-SRB2, SL-SRB3, or SL-SRB4.

9. The method according to claim 8, further comprising: sending, by the AS layer of the UE, a first indication to the NAS layer of the UE for indicating whether the at least one SRB is used to transmit the SLPP message.

10. The method according to claim 9, wherein, The first indication is indicated in the sidelink control channel configuration.

11. The method according to claim 1, wherein, Each SRB among the at least one SRB corresponding to each radio bearer among the at least one radio bearer has a different SRB type.

12. The method according to claim 1, wherein, The radio bearer includes the at least one DRB, and the configuration includes a second indication for indicating whether the at least one DRB contains the SLPP message.

13. The method according to claim 1, wherein The radio bearer includes the at least one DRB, and the configuration includes a third indication for indicating whether a QoS flow corresponding to the DRB contains the SLPP message.

14. The method according to claim 1, wherein, The radio bearer includes the at least one DRB, and the configuration includes a fourth indication for indicating the priority of the DRB.

15. The method according to claim 1, wherein, The radio bearer includes the at least one DRB, and the configuration includes a QoS flow to DRB mapping rule of a QoS flow containing the SLPP message.

16. The method according to claim 1, wherein The configuration includes the priority of the logical channel of the DRB or the priority of the QoS flow of the SLPP message, where the priority of the logical channel of the DRB or the priority of the QoS flow of the SLPP message is the highest priority.

17. A wireless communication method, comprising: obtaining, by a user equipment (UE), a MAC PDU carrying an SLPP message; and filtering, by the MAC layer of the UE, the MAC PDU based on two different predefined conditions to determine whether to send the MAC PDU to a disassembling and demultiplexing entity.

18. The method according to claim 17, wherein, Filtering the MAC PDU includes determining at least one of the following two predefined conditions: the DST field of the decoded MAC PDU sub-header is equal to the 8 MSBs of any one of the destination layer 2 IDs of the UE, where the 16 LSBs of the destination layer 2 ID of the UE are equal to the destination ID in the corresponding SCI side link control information (SCI); or the DST field of the decoded MAC PDU sub-header is equal to the 8 MSBs of any one of the source layer 2 IDs of the UE, where the 16 LSBs of the source layer 2 ID of the UE are equal to the destination ID in the corresponding SCI, and the SRC field of the decoded MAC PDU sub-header is equal to the 16 MSBs of any one of the destination layer 2 IDs of the UE, where the 8 LSBs of the destination layer 2 ID of the UE are equal to the source ID in the corresponding SCI.

19. The method according to claim 17 or 18, further comprising sending the MAC PDU to the disassembling and demultiplexing entity when any one of the predefined conditions is met.

20. A wireless communication device, comprising a memory storing one or more programs and one or more processors, the one or more processors being electrically coupled to the memory and configured to execute the one or more programs to perform the method according to any one of claims 1 to 19.

21. A non-transitory computer-readable storage medium storing one or more programs, the one or more programs being configured to, when executed by one or more processors, cause the execution of the method according to any one of claims 1 to 19.

Images