Techniques for prioritizing sidelink positioning information

Abstract

Techniques are described relating to prioritizing sidelink positioning reference signals (SL PRSs) for sidelink positioning in a novel radio (NR) system. In one embodiment, a method of managing communications for a user equipment (UE) includes detecting a set of overlapping symbols between an SL PRS and a message in a slot for a frame in a time domain of an NR system, extracting priority information of the SL PRS from a data storage device, and determining a scheduling schedule for transmission or reception of the SL PRS and the message based on the priority information. Other embodiments are also described and claimed.

Description

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS

[0002] This application claims the benefit of and priority to U.S. Provisional Patent Application No. 63 / 494,646, previously filed on April 6, 2023, entitled “MECHANISMS ON PRIORITIZATION OF SL-PRS TRANSMISSION OR RECEPTION FOR SIDELINK POSITIONING,” and U.S. Provisional Patent Application No. 63 / 394,482, previously filed on August 2, 2022, entitled “MECHANISMS ON PRIORITIZATION OF SL-PRS TRANSMISSION OR RECEPTION FOR SIDELINK POSITIONING,” both of which are incorporated herein by reference in their entirety. Background Art

[0003] New Radio (NR) vehicle-to-vehicle (V2V) or vehicle-to-anything (V2X) sidelink communications are synchronized communications systems that utilize distributed resource allocation. The user equipment (UE) autonomously selects resources for sidelink communications (including transmission and / or reception) based on a predefined sensing and resource selection process. The sensing and resource selection process is designed to reduce potential conflicts (e.g., collisions or half-duplex conflicts) in sidelink communications or resource reservations. However, when conflicts occur between sidelink communications or other signals, the UE requires improved techniques to resolve the conflicts to avoid or reduce the collisions. Therefore, there is a need to resolve the UE's conflict decisions, thereby improving the overall reliability of NR V2V or V2X sidelink communications. BRIEF DESCRIPTION OF THE DRAWINGS

[0004] To easily identify the discussion of any particular element or act, the most significant digit or digits in a reference number refer to the figure number in which the element is first introduced.

[0005] Figure 1 A wireless communication system according to one embodiment is shown.

[0006] Figure 2 A second wireless communication system according to an embodiment is shown.

[0007] Figure 3 An operating environment according to one embodiment is shown.

[0008] Figure 4 An operating environment according to one embodiment is shown.

[0009] Figure 5 An operating environment according to one embodiment is shown.

[0010] Figure 6 An operating environment according to one embodiment is shown.

[0011] Figure 7 An operating environment according to one embodiment is shown.

[0012] Figure 8 An apparatus according to one embodiment is shown.

[0013] Fig. 9 A logic flow according to one embodiment is shown.

[0014] Fig.10 A logic flow according to one embodiment is shown.

[0015] Fig.11 A logic flow according to one embodiment is shown.

[0016] Fig.12 A logic flow according to one embodiment is shown.

[0017] Fig.13 A message flow according to one embodiment is shown.

[0018] Fig.14 A first network according to one embodiment is shown.

[0019] Fig.15 A second network according to one embodiment is shown.

[0020] Fig.16 A third network according to one embodiment is shown.

[0021] Fig.17 A computer-readable storage medium according to one embodiment is shown. DETAILED DESCRIPTION

[0022] The following detailed description refers to the accompanying drawings. The same reference numerals may be used to identify the same or similar elements in different drawings. In the following description, for the purpose of explanation rather than limitation, specific details, such as specific structures, architectures, interfaces, technologies, etc., are described to provide a thorough understanding of various aspects of various embodiments. However, those skilled in the art who benefit from the present disclosure will appreciate that various aspects of various embodiments can be practiced in other examples that deviate from these specific details. In some cases, the description of known devices, circuits, and methods is omitted to avoid blurring the description of various embodiments with unnecessary details. For the purposes of this document, the phrases "A or B" and "A / B" refer to (A), (B), or (A and B).

[0023] Embodiments may generally relate to the field of wireless communication systems. Some embodiments particularly relate to techniques for prioritizing the transmission or reception of sidelink positioning reference signals (SL PRS) for sidelink positioning in fifth generation (5G) or sixth generation (6G) new radio (NR) wireless systems. In one embodiment, for example, the UE configures a priority value for the transmission or reception of the SL PRS. The UE determines whether the SL PRS communication has a higher priority than other types of communications based on the priority information (e.g., the priority value configured for the UE or other types of communications). The UE then generates a scheduling arrangement for communicating some or all of the SL PRS or other types of communications based on the priority information.

[0024] Mobile communications have evolved from early voice systems to today's highly complex integrated communications platforms. Next-generation wireless communication systems, such as 5G or 6G New Radio (NR), will provide a variety of users and applications with ready access to information and sharing of data. NR is expected to be a unified network / system designed to meet very different and sometimes conflicting performance dimensions and services. Such diverse multi-dimensional specifications are driven by different services and applications. In general, NR will be based on the 3rd Generation Partnership Project (3GPP) Long Term Evolution (LTE) and LTE evolved with other potential new radio access technologies (RATs) to enrich people's lives with better, simple, and seamless wireless connectivity solutions. NR will enable everything to be wirelessly connected and provide fast, rich content and services.

[0025] NR supports high-precision positioning in both vertical and horizontal dimensions, which relies on timing-based, angle-based, power-based, or hybrid techniques to estimate the user position in the network. With the wide bandwidth and beamforming capabilities for positioning signals in the millimeter wave (mmWave) bands, higher positioning accuracy can be achieved through RAT-dependent positioning techniques. Note that in 3GPP Release 16 (Rel-16), the downlink positioning reference signal (DL-PRS) and uplink sounding reference signal (UL-SRS) for positioning were introduced as enablers to achieve the target performance characteristics.

[0026] 3GPP Release 18 (Rel-18) addresses use cases such as positioning based on autonomous driving, sidelink, or vehicle-to-everything (V2X). More specifically, sidelink positioning needs to consider various scenarios, including in-network coverage, partial coverage, and out-of-network coverage. In order to meet the positioning accuracy specifications, it is envisioned that new sidelink reference signals will be introduced, such as the Sidelink Positioning Reference Signal (SL PRS).

[0027] SL PRS is a special type of reference signal used for positioning purposes in sidelink (SL) transmissions in cellular communication systems. It was introduced as part of the 5G NR standard and is designed to provide accurate and reliable positioning information for devices within the same network. In 5G NR, sidelink refers to direct communication between user equipment (UE) devices without going through a central base station. This direct device-to-device (D2D) communication allows low-latency and efficient data exchange, which is particularly beneficial in scenarios such as vehicular communications, public safety, and Internet of Things (IoT) applications. SL PRS is used to assist in determining the location of devices, which is critical for a variety of location-based services and applications. It helps calculate the distance between devices and enables time and frequency synchronization, allowing accurate triangulation of locations. SL PRS is sent periodically by devices, and other nearby devices can use the received signals to estimate their relative positions. This allows devices to perform co-location, where each device assists other devices in determining their locations. By leveraging SL PRS and other information related to positioning, 5G NR enables accurate and robust positioning capabilities, facilitating the implementation of location-based services and applications that require precise device location information.

[0028] In the NR sidelink, 3GPP defines priority rules between SL communications (transmission and reception) and other types of communications, such as uplink (UL) transmissions. Typically, the random access (RA) procedure on the physical random access channel (PRACH) is assigned a higher priority relative to SL transmission or reception. In one case, this includes certain types of messages, such as PRACH data, such as Message 3 (Msg3) of 4-step RACH (4SR) Physical Uplink Shared Channel (PUSCH) initial transmission and retransmission, Message A (MsgA) 2-step RACH (2SR) enhancement of PUSCH, Physical Uplink Control Channel (PUCCH) carrying Hybrid Automatic Repeat Request (HARQ) Acknowledgement (HARQ-ACK) information of corresponding Message B (MsgB) PDSCH transmission, Message 4 (Msg4) of 4SR, etc. Some or all of these message types may have a higher priority than SL communications. In the case where the UE cannot simultaneously perform transmission on the UL and transmission / reception on the SL in one carrier or two corresponding carriers, the UE transmits only the uplink channel and discards the sidelink communication (eg, transmission and / or reception).

[0029] For sidelink positioning operations, the SL PRS may overlap with other sidelink communications or uplink transmissions in the time domain. When the UE does not support simultaneous sidelink transmission or reception and / or uplink transmission, some or all symbols of the SL PRS and other sidelink communications or uplink transmissions may need to be discarded or canceled. Therefore, it may be necessary to define certain mechanisms for how to prioritize the SL PRS and other sidelink transmissions / receptions or uplink transmissions.

[0030] Techniques for prioritizing SL PRS for sidelink positioning in an NR system are described. In one embodiment, for example, a method for managing communications for a user equipment (UE) includes: detecting a set of overlapping symbols between an SL PRS and a message in a time slot for a frame in a time domain of the NR system; extracting priority information for the SL PRS from a data storage device; and determining a scheduling arrangement for sending or receiving the SL PRS and the message based on the priority information. Some or all symbols of the SL PRS and / or the message are communicated based on the scheduling arrangement. In this way, the UE reduces potential conflicts while maintaining the throughput of higher priority communications within the NR system. Therefore, the UE or other device within the NR system improves sidelink positioning in the device or NR system while requiring fewer computing resources, memory resources, bandwidth resources, and other scarce and valuable resources in the device or NR system. Other embodiments are described and claimed.

[0031] In one embodiment, the term "SL communication" may refer to symbols of SL communication transmitted between a first UE and a second UE, such as sending symbols of SL communication from the first UE to the second UE or receiving symbols of SL communication by the first UE from the second UE, or vice versa. In one embodiment, the term "UL communication" may refer to sending symbols of UL communication from a UE to one or more network entities in an NR system (e.g., a radio access network (RAN)). In one embodiment, the term "DL communication" may refer to receiving symbols of DL communication by a UE from a network entity such as a RAN.

[0032] In one embodiment, for example, "SL PRS transmitted symbol" or "SL PRS transmission" may refer to a symbol corresponding to a SL PRS resource. Alternatively, "SL PRS transmitted symbol" or "SL PRS transmission" may refer to a symbol corresponding to a SL PRS resource set (which resource set may be mapped to one or more occasions of a SL PRS resource pool). As another alternative, "SL PRS transmitted symbol" or "SL PRS transmission" may refer to a symbol corresponding to an occasion of a SL PRS resource pool. In another example, "SL PRS transmitted symbol" or "SL PRS transmission" may refer to a symbol corresponding to an occasion of a SL PRS resource pool when the SL PRS resource pool is configured for UE autonomous resource selection.

[0033] In one embodiment, for example, "SL PRS received symbols" or "SL PRS received" may refer to symbols corresponding to SL PRS resources. Alternatively, "SL PRS received symbols" or "SL PRS received" may refer to symbols corresponding to SL PRS resource sets (which may be mapped to one or more opportunities of a SL PRS resource pool). As another alternative, "SL PRS received symbols" or "SL PRS received" may refer to symbols corresponding to opportunities of a SL PRS resource pool. In another example, "SL PRS received symbols" or "SL PRS received" may refer to symbols corresponding to opportunities of a SL PRS resource pool when the SL PRS resource pool is configured for UE autonomous resource selection.

[0034] Reference is now made to the accompanying drawings, in which the same reference numerals are used throughout to refer to the same elements. In the following description, for the purpose of explanation, many specific details are proposed to provide a comprehensive understanding of the present application. However, novel embodiments can be practiced without these specific details. In other cases, known structures and devices are shown in block diagram form to facilitate their description. The purpose is intended to cover all modifications, equivalents, and alternatives consistent with the claimed subject matter.

[0035] Figure 1 An example of a wireless communication system 100 is shown. For convenience and not limitation, the example wireless communication system 100 is described in the context of Long Term Evolution (LTE) and fifth generation (5G) new radio (NR) (5G NR) or 6G NR cellular network communication standards. The 5G NR or 6G NR system may be defined, at least in part, by various 3rd Generation Partnership Project (3GPP) technical standards (TS), technical reports (TR), and / or work items (WI).

[0036] The various embodiments discussed herein may be implemented in a wireless communication system 100 defined in 3GPP TS 38.212 entitled “Technical Specification Group Radio Access Network; NR; Multiplexing and channel coding” (version 17.5.0 released in March 2023 (“3GPP TS38.212”) and 3GPP TS 38.213 entitled “Technical Specification Group Radio Access Network; NR; Physical layer procedures for control” (version 17.6.0 released in June 2023 (“3GPP TS28.213”); and may be implemented in a wireless communication system 100 defined in any descendant, revision, or variant of the above two. It will be appreciated that these embodiments may be implemented in accordance with other 3GPP TS, TR, and WI and other wireless standards issued by other standard entities. The embodiments are not limited in this context.

[0037] The wireless communication system 100 includes a UE 102a and a UE 102b (collectively referred to as "UE 102"). In this example, the UE 102 is shown as a smartphone (eg, a handheld touch screen mobile computing device that can connect to one or more cellular networks). In other examples, any of the UEs 102 may include other mobile or non-mobile computing devices, such as consumer electronic devices, cellular phones, smart phones, feature phones, tablet computers, wearable computer devices, personal digital assistants (PDAs), pagers, wireless handheld devices, desktop computers, laptop computers, in-vehicle infotainment (IVI) devices, in-vehicle entertainment (ICE) devices, instrument clusters (ICs), heads-up display (HUD) devices, on-board diagnostics (OBD) devices, dashboard mobile equipment (DME), mobile data terminals (MDTs), electronic engine management systems (EEMS), electronic / engine control units (ECUs), electronic / engine control modules (ECMs), embedded systems, microcontrollers, control modules, engine management systems (EMS), networked or “smart” appliances, machine type communication (MTC) devices, machine-to-machine (M2M) devices, Internet of Things (IoT) devices, or combinations thereof, etc.

[0038] In some implementations, any of the UEs 102 may be an IoT UE, which may include a network access layer designed for low-power IoT applications that utilize short-term UE connections. The IoT UE may utilize technologies such as M2M or MTC to exchange data with an MTC server or device using, for example, a public land mobile network (PLMN), proximity services (ProSe), device-to-device (D2D) communication, a sensor network, an IoT network, or a combination thereof. The M2M or MTC data exchange may be a machine-initiated data exchange. The IoT network describes interconnecting IoT UEs using short-term connections, which may include uniquely identifiable embedded computing devices (within the Internet infrastructure). The IoT UE may execute background applications (e.g., keep-alive messages or status updates) to facilitate connectivity to the IoT network.

[0039] The UE 102 is configured to be connected (e.g., communicatively coupled) to a radio access network (RAN) 112. In some implementations, the RAN 112 may be a next generation RAN (NG RAN), an evolved UMTS terrestrial radio access network (E-UTRAN), or a legacy RAN such as a UMTS terrestrial radio access network (UTRAN) or a GSM EDGE radio access network (GERAN). As used herein, the term “NG RAN” may refer to the RAN 112 operating in a 5G NR wireless communication system 100, and the term “E-UTRAN” may refer to the RAN 112 operating in an LTE or 4G wireless communication system 100.

[0040] To connect to the RAN 112, the UE 102 utilizes connections (or channels) 118 and 120, respectively, each of which may include a physical communication interface or layer, as described below. In this example, the connections 118 and 120 are shown as air interfaces to achieve communication coupling, and may conform to a cellular communication protocol, such as a Global System for Mobile Communications (GSM) protocol, a Code Division Multiple Access (CDMA) network protocol, a Push-to-Talk (PTT) protocol, a PTT over Cellular (POC) protocol, a Universal Mobile Telecommunications System (UMTS) protocol, a 3GPP LTE protocol, a 5G NR protocol, or a combination thereof, as well as other communication protocols.

[0041] UE 102b is shown as being configured to access an access point (AP) 104 (also referred to as "WLAN node 104," "WLAN 104," "WLAN terminal 104," "WT 104," etc.) using a connection 122. Connection 122 may include a local wireless connection, such as a connection compliant with any IEEE 802.11 protocol, where AP 104 would include a Wireless Fidelity (Wi-Fi) router. In this example, AP 104 is shown as being connected to the Internet and not to a core network of a wireless system, as described in further detail below.

[0042] The RAN 112 may include one or more nodes that enable connections 118 and 120, such as RAN nodes 106a and 106b (collectively referred to as "RAN nodes 106"). As used herein, the terms "access node", "access point", etc. may describe equipment that provides radio baseband functions for data or voice connections or both between a network and one or more users. These access nodes may be referred to as base stations (BS), gNodeBs, gNBs, eNodeBs, eNBs, NodeBs, RAN nodes, roadside units (RSUs), transmit receive points (TRxPs or TRPs), etc., and may include ground stations (e.g., terrestrial access points) or satellite stations that provide coverage within a geographic area (e.g., a cell), etc. As used herein, the term "NG RAN node" may refer to a RAN node 106 (e.g., a gNB) operating in a 5G NR wireless communication system 100, and the term "E-UTRAN node" may refer to a RAN node 106 (e.g., an eNB) operating in an LTE or 4G wireless communication system 100. In some implementations, the RAN node 106 may be implemented as one or more of a dedicated physical device (e.g., a macrocell base station) or a low power (LP) base station (for providing a femtocell, picocell, or other similar cell with a smaller coverage area, smaller user capacity, or higher bandwidth than a macrocell).

[0043] In some implementations, some or all of the RAN nodes 106 may be implemented as one or more software entities running on a server computer as part of a virtual network (which may be referred to as a cloud RAN (CRAN) or a virtual baseband unit pool (vBBUP)). The CRAN or vBBUP may implement a RAN functional split, such as a packet data convergence protocol (PDCP) split, where the radio resource control (RRC) and PDCP layers are operated by the CRAN / vBBUP, while other layer 2 (e.g., data link layer) protocol entities are operated by individual RAN nodes 106; a medium access control (MAC) / physical layer (PHY) split, where the RRC, PDCP, MAC, and radio link control (RLC) layers are operated by the CRAN / vBBUP, while the PHY layer is operated by individual RAN nodes 106; or a “lower PHY” split, where the RRC, PDCP, RLC, and MAC layers and the upper portion of the PHY layer are operated by the CRAN / vBBUP, while the lower portion of the PHY layer is operated by individual RAN nodes 106. This virtualization framework allows the freed processor cores of the RAN node 106 to execute, for example, other virtualized applications. In some implementations, a separate RAN node 106 may be represented using a separate F1 interface ( Figure 1The RAN 112 may include a separate gNB distributed unit (DU) (not shown) connected to a gNB central unit (CU). In some implementations, the gNB-DU may include one or more remote radio heads or RFEMs, and the gNB-CU may be operated by a server (not shown) located in the RAN 112 or by a server pool in a manner similar to a CRAN / vBBUP. In addition, or alternatively, one or more RAN nodes 106 may be next-generation eNBs (ng-eNBs), including RAN nodes that provide E-UTRA user plane and control plane protocol termination to the UE 102 and connect to a 5G core network (e.g., core network 114) using a next-generation interface.

[0044] In a vehicle-to-everything (V2X) scenario, one or more RAN nodes 106 may be or act as an RSU. The term "roadside unit" or "RSU" refers to any traffic infrastructure entity used for V2X communications. The RSU may be implemented in or by a suitable RAN node or a stationary (or relatively stationary) UE, wherein an RSU implemented in or by a UE may be referred to as a "UE-type RSU", an RSU implemented in or by an eNB may be referred to as an "eNB-type RSU", an RSU implemented in or by a gNB may be referred to as a "gNB-type RSU", and so on. In some implementations, the RSU is a computing device coupled to a radio frequency circuit located at the roadside that provides connectivity support to a passing vehicle UE 102 (vUE 102). The RSU may also include internal data storage circuitry for storing intersection map geometry, traffic flow statistics, media, and applications or other software for sensing and controlling ongoing vehicle and pedestrian traffic flows. The RSU can operate on the 5.9 GHz direct short-range communication (DSRC) band to provide very low latency communications required for high-speed events such as collision avoidance, traffic flow warnings, etc. In addition, or alternatively, the RSU can operate on the cellular V2X band to provide the above-mentioned low latency communications as well as other cellular communication services. In addition, or alternatively, the RSU can operate as a Wi-Fi hotspot (2.4 GHz band) or provide connection to one or more cellular networks to provide uplink and downlink communications, or both. Some or all of the RF circuits and (one or more) computing devices of the RSU can be encapsulated in a weatherproof enclosure suitable for outdoor installation, and a network interface controller can be included to provide a wired connection to a traffic flow signal controller or a backhaul network (e.g., Ethernet) or both.

[0045] Any RAN node 106 may terminate the air interface protocol and may be the first point of contact for the UE 102. In some implementations, any RAN node 106 may implement various logical functions of the RAN 112, including but not limited to Radio Network Controller (RNC) functions such as radio bearer management, uplink and downlink dynamic radio resource management and data packet scheduling, and mobility management.

[0046] In some implementations, the UEs 102 may be configured to communicate with each other or with any RAN node 106 using orthogonal frequency division multiplexing (OFDM) communication signals on a multi-carrier communication channel according to various communication techniques, such as, but not limited to, OFDMA communication techniques (e.g., for downlink communications) or SC-FDMA communication techniques (e.g., for uplink communications), although the scope of the techniques described herein is not limited in this respect. OFDM signals may include multiple orthogonal subcarriers.

[0047] The RAN node 106 may transmit to the UE 102 via various channels. Various examples of downlink communication channels include a physical broadcast channel (PBCH), a physical downlink control channel (PDCCH), and a physical downlink shared channel (PDSCH). Other types of downlink channels are also possible. The UE 102 may transmit to the RAN node 106 via various channels. Various examples of uplink communication channels include a physical uplink shared channel (PUSCH), a physical uplink control channel (PUCCH), and a physical random access channel (PRACH). Other types of uplink channels are also possible.

[0048] In some implementations, a downlink resource grid may be used for downlink transmissions from any RAN node 106 to a UE 102, while uplink transmissions may utilize similar techniques. The grid may be a time-frequency grid, referred to as a resource grid or a time-frequency resource grid, which is the physical resource in the downlink for each time slot. This representation of the time-frequency plane is common practice for OFDM systems, which makes radio resource allocation intuitive. Each column and row of the resource grid corresponds to an OFDM symbol and an OFDM subcarrier, respectively. The duration of the resource grid in the time domain corresponds to a time slot in a radio frame. The smallest time-frequency unit in the resource grid is represented as a resource element. Each resource grid includes a plurality of resource blocks, which describe the mapping of certain physical channels to resource elements. Each resource block includes a set of resource elements; in the frequency domain, this may represent the minimum amount of resources that may currently be allocated. There are several different physical downlink channels, which are transmitted using such resource blocks.

[0049] The PDSCH carries user data and higher layer signaling for the UE 102. The PDCCH carries information about, among other things, the transport format and resource allocation associated with the PDSCH channel. It may also inform the UE 102 about the transport format, resource allocation, and hybrid automatic repeat request (HARQ) associated with the uplink shared channel. Downlink scheduling (e.g., assigning control and shared channel resource blocks to UEs 102b within a cell) may be performed at any RAN node 106 based on channel quality information fed back from any UE 102. Downlink resource assignment information may be sent on the PDCCH for (e.g., assigned to) each UE 102.

[0050] PDCCH uses control channel elements (CCE) to transmit control information. Before being mapped to resource elements, PDCCH complex symbols can first be organized into quadruplets, which can then be permuted using a sub-block interleaver for rate matching. In some implementations, each PDCCH can be sent using one or more of these CCEs, where each CCE can correspond to nine groups of physical resource elements (collectively referred to as resource element groups (REGs)), each REG including four physical resource elements. Four orthogonal phase shift keying (QPSK) symbols can be mapped to each REG. PDCCH can be sent using one or more CCEs, depending on the size of the downlink control information (DCI) and channel conditions. In LTE, four or more different PDCCH formats can be defined using different numbers of CCEs (e.g., aggregation levels, L=1, 2, 4, or 8).

[0051] Some implementations may use concepts of resource allocation for control channel information that are extensions of the above concepts. For example, some implementations may utilize an enhanced PDCCH (EPDCCH), which uses PDSCH resources for control information transmission. EPDCCH may be transmitted using one or more enhanced CCEs (ECCEs). Similar to the above, each ECCE may correspond to nine groups of physical resource elements (collectively referred to as enhanced REGs (EREGs)), each EREG comprising four physical resource elements. ECCEs may have other numbers of EREGs.

[0052] The RAN nodes 106 are configured to communicate with each other using an interface 132. In an example such as when the wireless communication system 100 is an LTE system (e.g., when the core network 114 is an evolved packet core (EPC) network), the interface 132 may be an X2 interface 132. The X2 interface may be defined between two or more RAN nodes 106 (e.g., two or more eNBs, etc.) connected to the EPC 114 or between two sub-eNBs connected to the EPC 114, or both. In some implementations, the X2 interface may include an X2 user plane interface (X2-U) and an X2 control plane interface (X2-C). The X2-U may provide a flow control mechanism for user data packets transmitted over the X2 interface, and may be used to communicate information about the delivery of user data between eNBs. For example, X2-U can provide: specific sequence number information of user data transmitted from the primary eNB to the secondary eNB; information about PDCP protocol data units (PDUs) that successfully delivered user data in sequence from the secondary eNB to the UE 102; information about PDCP PDUs that were not delivered to the UE 102; information about the current minimum expected buffer size at the secondary eNB for sending user data to the UE, and other information. X2-C can provide intra-LTE access mobility functions, including: context transfer or user plane transmission control from the source eNB to the target eNB; load management functions; inter-cell interference coordination functions, and other functions.

[0053] In some implementations, such as when the wireless communication system 100 is a 5G NR system (e.g., when the core network 114 is a 5G core network), the interface 132 may be an Xn interface 132. The Xn interface may be defined between two or more RAN nodes 106 (e.g., two or more gNBs, etc.) connected to the 5G core network 114, between a RAN node 106 and an eNB connected to the 5G core network 114, or between two eNBs connected to the 5G core network 114, or a combination thereof. In some implementations, the Xn interface may include an Xn user plane (Xn-U) interface and an Xn control plane (Xn-C) interface. The Xn-U may provide non-guaranteed delivery of user plane PDUs and support / provide data forwarding and flow control functions. The Xn-C may provide management and error handling functions, functions for managing the Xn-C interface; mobility support for UE 102 in connected mode (e.g., CM-CONNECTED), including functions for managing the mobility of UEs in connected mode between one or more RAN nodes 106; and other functions. Mobility support may include context transfer from the old (source) service RAN node 106 to the new (target) service RAN node 106 and control of the user plane tunnel between the old (source) service RAN node 106 and the new (target) service RAN node 106. The protocol stack of Xn-U may include a transport network layer built on the Internet Protocol (IP) transport layer and a GPRS tunneling protocol for a user plane (GTP-U) layer carrying user plane PDUs on the user datagram protocol (UDP) layer or the IP layer or both. The Xn-C protocol stack may include an application layer signaling protocol (referred to as the Xn application protocol (Xn AP or XnAP)) and a transport network layer (TNL) built on the stream control transmission protocol (SCTP). SCTP may be located above the IP layer and may provide guaranteed delivery of application layer messages. At the transport IP layer, point-to-point transmission is used to deliver signaling PDUs. In other implementations, the Xn-U protocol stack or the Xn-C protocol stack or both may be the same or similar to the user plane and / or control plane protocol stacks shown and described herein.

[0054] RAN 112 is shown as being communicatively coupled to a core network 114 (referred to as "CN 114"). CN 114 includes multiple network elements, such as network element 108a and network element 108b (collectively referred to as "network elements 108"), which are configured to provide various data and telecommunication services to customers / subscribers (e.g., users of UE 102) connected to CN 114 using RAN 112. The components of CN 114 can be implemented in one physical node or different physical nodes, and can include components for reading instructions from a machine-readable or computer-readable medium (e.g., a non-transitory machine-readable storage medium) and executing. In some implementations, network function virtualization (NFV) can be used to virtualize some or all of the network node functions described herein using executable instructions stored in one or more computer-readable storage media, as described in detail below. A logical instantiation of CN 114 can be referred to as a network slice, and a logical instantiation of a portion of CN 114 can be referred to as a network sub-slice. NFV architecture and infrastructure can be used to virtualize one or more network functions (which are instead performed by proprietary hardware) onto physical resources including a combination of industry-standard server hardware, storage hardware, or switches. In other words, the NFV system can be used to perform virtual or configurable implementations of one or more network components or functions, or both.

[0055] The application server 110 may be an element that provides applications using IP bearer resources using a core network (e.g., UMTS packet service (PS) domain, LTE PS data service, etc.). The application server 110 may also be configured to support one or more communication services (e.g., VoIP sessions, PTT sessions, group communication sessions, social network services, etc.) for the UE 102 using the CN 114. The application server 110 may communicate with one or more network elements 108a using an IP communication interface 130.

[0056] In some implementations, CN 114 may be a 5G core network (referred to as "5GC 114" or "5G core network 114"), and RAN 112 may be connected to CN 114 using a next generation interface 124. In some implementations, the next generation interface 124 may be divided into two parts: a next generation user plane (NG-U) interface 114, which carries traffic data between the RAN node 106 and the user plane function (UPF); and an S1 control plane (NG-C) interface 126, which is a signaling interface between the RAN node 106 and the access mobility management function (AMF). CN 114 is an example of a 5G core network and will be discussed in more detail with reference to the following figures.

[0057] In some implementations, the CN 114 may be an EPC (referred to as “EPC 114”, etc.), and the RAN 112 may be connected to the CN 114 using an S1 interface 124. In some implementations, the S1 interface 124 may be divided into the following two parts: an S1 user plane (S1-U) interface 128, which carries traffic data between the RAN node 106 and a serving gateway (S-GW); and an S1-MME interface 126, which is a signaling interface between the RAN node 106 and a mobility management entity (MME).

[0058] Figure 2 A wireless communication system 200 is shown. The wireless communication system 200 is Figure 1 . The wireless communication system 200 depicts an example of sidelink positioning operations and signals for a set of anchor UEs 222 and target UEs 220. In this example, the target UE 220 represents a UE to be positioned, and the anchor UE 222 represents a UE that supports positioning of the target UE 220 (e.g., by sending and / or receiving SL PRS 230 and providing positioning related information). Note that the SL PRS 230 can be sent between the anchor UE 222 and the target UE 220 and between the target UE 220 and the anchor UE 222 for sidelink positioning operations.

[0059] In 5G NR, sidelink communication refers to direct communication between UEs (such as smart phones or IoT devices) without the need for traditional centralized base stations (such as gNodeBs). This form of communication can be used for various applications, such as vehicle communication, public safety, and peer-to-peer sharing. In general, the target UE 220 and the anchor UE 222 establish sidelink communication through a sidelink process including sidelink capability discovery, resource allocation, and resource selection (e.g., time, frequency, and space resources). Once the anchor UE 222 selects the resource, the anchor UE 222 performs data transmission, and the target UE 220 receives the data sent by the anchor UE 222. After decoding the data received from the anchor UE 222, if the data is successfully received, the target UE 220 sends an acknowledgment (ACK), and if the data is not successfully received, the target UE 220 sends a negative acknowledgment (NACK). Once the sidelink communication is completed, the anchor UE 222 releases the resources used for the sidelink transmission.

[0060] SL PRS 230 is used for sidelink communication between anchor UE 222 and target UE 220 to provide accurate positioning information. This is particularly important in V2V or V2X communication in autonomous driving or safety-critical scenarios where precise location information is required. Anchor UE 222 sends SL PRS 230 in the allocated sidelink resources. The signal contains a specific pattern or code that enables it to be distinguished from other types of signals. SL PRS 230 is used for both communication and positioning of the UE.

[0061] The target UE 220 receives the SL PRS 230 from the anchor UE 222. If the SL PRS 230 has known properties, the target UE 220 can analyze the received signal and compare it with the expected signal. The target UE 220 calculates the time difference between the time when the anchor UE 222 sends the SL PRS 230 and the time when the target UE 220 receives the SL PRS 230. The target UE 220 then calculates the distance between the anchor UE 222 and the target UE 220 based on the time difference. This calculation typically involves determining the time of arrival (ToA) or the time difference of arrival (TDoA) of the signal. Based on the calculated distance and the known transmission direction (if available), the target UE 220 can estimate the position of the anchor UE 222.

[0062] If the target UE 220 receives SL PRS 230 from multiple anchor UEs 222, the target UE 220 can use multilateration to calculate more accurate location information. Multilateration is a navigation and monitoring technology used to determine the location of an object by measuring the TDoA of signals from the object to multiple known locations, and is commonly used for positioning in navigation systems such as GPS and cellular networks.

[0063] The target UE 220 may then use this positioning information for various applications that rely on the precise location of the UE, such as autonomous driving, traffic flow management, emergency services, etc.

[0064] In addition to the SL PRS 230 , sidelink communications may also involve other types of reference signals, such as a Sidelink Synchronization Signal (SLSS) for synchronization purposes or a Demodulation Reference Signal (DMRS) for data demodulation.

[0065] In the NR sidelink, 3GPP defines priority rules between sidelink communications (e.g., transmission and / or reception) and uplink transmissions. As mentioned earlier, PRACH communications have a higher priority than SL communications. For example, Msg3 for 4SRPUSCH initial transmission and retransmission, 2SR MsgA PUSCH, PUCCH carrying HARQ-ACK information sent by the corresponding MsgB PDSCH, and Msg4 of 4SR all have a higher priority level than SL transmission or reception. When the UE cannot simultaneously transmit on the UL and transmit / receive on the SL on one or both carriers, the UE only transmits the uplink channel and discards the sidelink transmission / reception.

[0066] For sidelink positioning, SL PRS230 may overlap with other sidelink transmissions / receptions and uplink transmissions in the time domain. If the UE does not support simultaneous sidelink transmission or reception and / or uplink transmission, it may be necessary to discard or cancel one of the SL PRS230 and other sidelink transmissions / receptions or uplink transmissions. In this case, it may be necessary to define certain mechanisms on how to prioritize SL PRS230 and other sidelink transmissions / receptions or uplink transmissions.

[0067] To address these and other challenges, various embodiments described herein provide a mechanism for prioritizing the transmission or reception of SL PRS230 for sidelink positioning. In one embodiment, for example, it is assumed that one or more symbols transmitted or received by SL PRS230 overlap with another sidelink transmission or reception or uplink transmission with a higher priority in the time domain. If the UE cannot simultaneously transmit / receive SL PRS230 and another sidelink transmission / reception or uplink transmission in one or two carriers, the UE can cancel or discard one or more symbols transmitted or received by SL PRS230 accordingly. Note that one or more symbols may include automatic gain control (AGC) symbols (before SL PRS230 transmission / reception) and / or protection symbols (after SL PRS230 transmission / reception). Examples of sidelink transmission or reception may include one or more of the following channels / signals: PSCCH / PSSCH, PSFCH, S-SS / PSBCH, and / or SLPRS230.

[0068] Although one or more overlapping symbols are discarded, the UE can still send or receive SLPRS 230 in non-overlapping symbols. This preserves some information of SLPRS 230.

[0069] Figures 3 to 7Various use cases and examples are shown where the UE transmits SL PRS 230 or receives SL PRS 230. It will be appreciated that those examples involving the UE transmitting SL PRS 230 are also applicable to the UE receiving SL PRS 230, and vice versa. The embodiments are not limited in this context.

[0070] Figure 3 An operating environment 302 is shown. The operating environment 302 shows an example of partial cancellation of the SL PRS 230 in overlapping symbols.

[0071] The operating environment 302 shows a time slot 308 of a frame from a 5G NR interface before and after the overlapping symbols are cancelled. The time slot 308 represents a specific time unit on the 5G NR interface. In a wireless communication system, the frame structure defines the way information (e.g., data and control information) is organized for transmission on the radio frequency (RF) spectrum. Frames in 5G NR are typically 10 milliseconds (ms) long and include subframes and time slots. The number of time slots in a frame or subframe depends on the parameter set used (e.g., subcarrier spacing). At a subcarrier spacing of 15 kilohertz (kHz) (referred to as parameter set 0), there are 10 subframes per frame, and each subframe includes 2 time slots. At larger subcarrier spacing, there can be more time slots in a frame. For example, at a subcarrier spacing of 30kHz (parameter set 1), there are 20 time slots in a frame. In the example shown in the operating environment 302, the subcarrier spacing is 15kHz (parameter set 0). Therefore, the time slot 308 includes 14 symbols 304 and lasts for 1ms.

[0072] In operating environment 302, UE sends SL PRS 230 and message 306 in time slot 308. In this example, message 306 is MsgA PUSCH. SL PRS 230 includes 7 symbols 304, and message 306 includes 6 symbols 304. As shown in time slot 308, SL PRS 230 and message 306 have a set of overlapping symbols 312 and a set of non-overlapping symbols 314. A set of overlapping symbols 312 includes 2 symbols 304, in this case, these symbols are symbols 8 and 9 in time slot 308. A set of non-overlapping symbols 314 includes 4 symbols 304, in this case, these symbols are symbols 4 to 7. It is assumed that message 306 is assigned a higher priority in 5G NR. Based on this assumption, the UE sends the entire set of 6 symbols 304 of message 306 and discards 2 symbols 304 of overlapping symbols 312 including symbols 8 and 9 in SL PRS 230. However, the UE continues to transmit non-overlapping symbols 314 of the SL PRS 230 , including symbols 4 through 7 , and all 6 symbols 304 of the message 306 .

[0073] Operational environment 302 illustrates an example where the UE performs partial cancellation of SL PRS 230 in the case of overlapping symbols 312. In another embodiment, the UE performs complete cancellation of SL PRS 230 in the case of overlapping symbols 312. Figure 4 This situation is shown in .

[0074] Figure 4 An operating environment 402 is shown. The operating environment 402 shows an example of complete cancellation of the SL PRS 230 in the overlapping symbol 312.

[0075] Assume that one or more symbols for SL PRS230 transmission or reception overlap with a sidelink transmission or reception or uplink transmission with a higher priority in the time domain. If the UE cannot perform SLPRS230 transmission / reception and sidelink transmission / reception or uplink transmission in one or two carriers at the same time, the UE may decide to cancel or discard all symbols 304 transmitted or received by SLPRS230. Note that the symbol 304 may include an AGC symbol (located before the SL PRS230 transmission / reception) and / or a protection symbol (located after the SL PRS230 transmission / reception).

[0076] Operational context 402 illustrates an example of cancellation of the entire SL PRS 230 transmission. As with the previous example discussed with reference to the operational context 302, the operational context 402 illustrates a case where a set of overlapping symbols 312 in a time slot 308 includes two symbols 304, namely symbols 8 and 9. In this case, given that the message 306 (e.g., MsgA PUSCH) has a higher priority relative to the SL PRS 230, the UE discards all 7 symbols 304 transmitted by the SL PRS 230 and transmits only 6 symbols 304 of the MsgA PUSCH.

[0077] Operating environment 302 and operating environment 302 illustrate message 306 as a MsgA PUSCH transmission. In another embodiment, it is assumed that message 306 is one of PRACH, Msg3 PUSCH initial transmission and retransmission, MsgA PUSCH, PUCCH carrying HARQ-ACK information transmitted by corresponding MsgB PDSCH, or Msg4. In all of these examples, it is further assumed that message 306 has a higher priority than the transmission or reception of SL PRS230. In this case, when message 306 overlaps with the transmission or reception of SL PRS230, if the UE cannot simultaneously perform the transmission / reception of SL PRS230 and uplink transmission in one or two carriers, the entire SL PRS230 transmission or reception can be discarded or canceled. Alternatively, one or more overlapping symbols 312 transmitted or received by SL PRS230 can be discarded or canceled.

[0078] In another embodiment, a measurement gap may be configured for reception of SL PRS 230. During the measurement gap, the UE may receive only SL PRS 230 for sidelink positioning. The measurement gap may be configured according to a system frame duration, a subframe duration, or a physical time slot.

[0079] In another embodiment, the measurement gap may be configured according to a logical index of a time slot configured for the SL PRS resource pool. More specifically, the measurement gap may be configured within the SL PRS resource pool for a dedicated SL PRS resource pool in which only the SL PRS and possibly any associated PSCCH may be transmitted. Alternatively, when a shared resource pool is configured for sidelink communications and SL PRS 230 transmission / measurement, the measurement gap may be configured according to a logical index of a time slot configured for the sidelink communications resource pool. In addition, the measurement gap may be activated or deactivated via a medium access control-control element (MAC-CE) or a sidelink control information (SCI) format.

[0080] In another embodiment, the SL PRS processing window for SLPRS 230 reception may be provided to the UE through higher layer (pre) configuration and / or dynamic indication. In another example, the UE may perform SL PRS 230 measurements outside of a measurement gap but within the SL PRS processing window.

[0081] The SL PRS processing window may be configured based on a subframe index or a physical time slot index. In another option, when a dedicated SL PRS resource pool is configured for SL PRS230 transmission and measurement, the SL PRS processing window may be configured based on a logical index of a time slot configured for the SL PRS resource pool. Alternatively, when a shared resource pool is configured for sidelink communication and SL PRS230 transmission / measurement, the SL PRS processing window may be configured based on a logical time slot configured for the sidelink communication resource pool.

[0082] In addition, the SL PRS processing window may be activated or deactivated through a Medium Access Control-Control Element (MAC-CE) or Sidelink Control Information (SCI) format.

[0083] In addition, priority parameters for SL PRS measurement may be configured for the UE via a higher layer configuration. In one option, when the UE receives SL PRS 230 within the SL PRS processing window and the UE determines that SL PRS 230 has a higher priority than a sidelink physical channel / signal or an uplink physical channel / signal, the UE is expected to receive SL PRS 230, and the UE is not expected to send or receive other sidelink physical channels / signals and / or send uplink physical channels or signals. Otherwise, the UE is not expected to measure SL PRS 230 within the SL PRS processing window, and the UE is expected to send or receive other sidelink physical channels / signals and / or send uplink physical channels / signals.

[0084] In some aspects, the SL PRS processing window or measurement gap may not be provided to the UE.In addition, the priority value of the SLPRS 230 transmission or reception may be provided to the UE.

[0085] In another option, when the UE receives the SL PRS 230 within the SL PRS processing window and the UE determines that the SL PRS has a higher priority than the sidelink physical channel / signal or the uplink physical channel / signal, the UE is expected to measure the SLPRS 230, but the UE is not expected to send or receive other sidelink physical channels / signals and / or send uplink physical channels / signals. Otherwise, the UE is not expected to measure the SL PRS 230 in the overlapping symbol 304, but the UE is expected to send or receive other sidelink physical channels / signals and / or send uplink physical channels / signals.

[0086] In another option, the UE may report the ability to support multiple priority states (e.g., 1 to 3 priority states) for SL PRS reception. When one priority state is supported, the priority of receiving the SL PRS 230 and possible PSCCHs in the resource pool configured with SL PRS resources is higher than the priority of any PSCCH, PSSCH, PSFCH, or SL-CSI-RS in another resource pool. When two priority states are supported, the two states are defined as: (1) State 1: The priority of receiving the SL PRS 230 and possible PSCCHs in the resource pool configured with SL PRS resources is higher than the priority of any PSCCH, PSSCH, PSFCH, or SL-CSI-RS; and (2) State 2: The priority of receiving the SL PRS 230 and possible PSCCHs in the resource pool configured with SL PRS resources is lower than the priority of any PSCCH, PSSCH, PSFCH, or SL-CSI-RS. When three priority states are supported, the three states are defined as: (1) State 1: The priority of receiving SL PRS 230 and possible PSCCHs in the resource pool configured with SL PRS resources is higher than the priority of any PSCCH, PSSCH, PSFCH, or SL-CSI-RS in another resource pool; (2) State 2: The priority of receiving SL PRS 230 and possible PSCCHs in the resource pool configured with SL PRS resources is lower than any phase 1 PSCCH and phase 2 PSCCH, PSSCH, PSFCH with higher priority, and higher than any phase 2 PSCCH, PSSCH, and PSFCH not associated with high priority; and (3) State 3: The priority of receiving SL PRS 230 and possible PSCCHs in the resource pool configured with SL PRS resources is lower than the priority of any PSCCH, PSSCH, PSFCH, or SL-CSI-RS. Based on the capabilities of the UE, if the UE can support up to two or three priority states, the UE can be configured or preconfigured with one of these states.

[0087] The following provides an embodiment of prioritizing SL PRS transmission or reception for sidelink positioning when no priority level is defined for SL-PTRS transmission or reception. In one embodiment, no priority level is defined for SL PRS230 transmission or reception. In this case, for the priority ranking between SL PRS230 transmission / reception and UL transmission other than PRACH, or PUSCH and its retransmission scheduled by UL grant in RAR, or PUSCH and its retransmission corresponding to type 2 random access process, or PUCCH with sidelink HARQ-ACK information report, if the UL transmission is for PUCCH or PUSCH with priority index 1, then in one option, the UL transmission has a higher priority than the SL PRS230 transmission or reception. In another option, the SL PRS230 transmission or reception has a higher priority than the UL transmission.

[0088] Figure 5 An operating environment 502 is shown. The operating environment 502 shows an example of complete cancellation of the SL PRS 230 in the overlapping symbols 312 when the uplink transmission has a higher priority than the SLPRS 230.

[0089] Operation environment 502 shows an example of prioritizing SL PRS 230 and uplink transmissions with higher priority. In this example, it is assumed that message 306 is a PUCCH transmission with a high priority level. The overlapping symbols 312 between SL PRS 230 and PUCCH transmissions with high priority include all 6 symbols 304 of SL PRS 230 in time slot 308. Based on the above options, PUCCH transmissions with priority index 1 or high priority have higher priority than SL PRS 230 transmissions. In this case, the UE discards all 6 symbols 304 (symbols 4 to 9) of SL PRS 230 transmissions and only transmits PUCCH transmissions with priority index 1 or higher priority.

[0090] In another option, whether UL transmission has a higher priority than SL PRS 230 transmission or reception can be configured or preconfigured by a higher layer. In one example, when the parameter is configured, UL transmission has a higher priority than SL PRS 230 transmission or reception. Otherwise, SL PRS 230 transmission has a higher priority than UL transmission.

[0091] In another embodiment, no priority level is defined for SL PRS230 transmission or reception. In this case, for the priority ranking between SL PRS230 transmission / reception and UL transmission other than PRACH, or PUSCH and its retransmission scheduled by UL grant in RAR, or PUSCH and its retransmission corresponding to type 2 random access procedure, or PUCCH with sidelink HARQ-ACK information report, if the UL transmission is for PUCCH or PUSCH with priority index 0, in one option, the UL transmission has a higher priority than the SL PRS230 transmission or reception. In another option, the SL PRS230 transmission or reception has a higher priority than the UL transmission.

[0092] In another option, whether UL transmission has a higher priority than SL PRS230 transmission or reception can be configured or preconfigured by a higher layer. In one example, when the parameter is configured, UL transmission has a higher priority than SL PRS230 transmission or reception. Otherwise, SL PRS230 transmission has a higher priority than UL transmission. Note that the parameters can be configured for UL transmissions with priority indexes 0 and 1, respectively.

[0093] In another embodiment, no priority level is defined for SL PRS230 transmission or reception. In this case, for the priority order between SL PRS230 transmission / reception and PUCCH or PUSCH transmission with sidelink HARQ-ACK information reporting, if the priority value of PUCCH transmission is less than a threshold, then PUCCH transmission has a higher priority than SL PRS230 transmission or reception, and the threshold can be configured or pre-configured by a higher layer. Otherwise, SL PRS230 transmission has a higher priority than PUCCH transmission.

[0094] Figure 6 An operating environment 602 is shown. Operating environment 602 shows an example of a complete transmission of SLPRS 230 in overlapping symbols 312 when SL PRS 230 has a higher priority level than uplink transmission (uplink transmission has a lower priority than SL PRS 230). As with operating environment 502, operating environment 602 shows a set of overlapping symbols 312 between SLPRS 230 and message 306 in time slot 308, and the set of overlapping symbols 312 includes all 6 symbols 304 of SL PRS 230.

[0095] Operational environment 602 shows an example of prioritizing SL PRS 230 and uplink transmissions with lower priority. In this example, it is assumed that message 306 is a PUCCH transmission with a SL HARQ-ACK report with a lower priority level. In this example, it is assumed that the priority value of the PUCCH transmission is 4 and the UE is configured with a defined priority threshold (whose value is 3). Based on the above options, the SL PRS 230 transmission has a higher priority than the PUCCH transmission. In this case, all 11 symbols 304 of the PUCCH with SL HARQ-ACK report are discarded, and the UE sends all 6 symbols 304 of the SL PRS 230.

[0096] In another option, a PUCCH or PUSCH transmission with sidelink HARQ-ACK information reporting always has a higher priority than a SLPRS 230 transmission or reception. In another option, a SL PRS 230 transmission has a higher priority than a PUCCH or PUSCH transmission with sidelink HARQ-ACK information reporting.

[0097] In another option, whether PUCCH or PUSCH transmission with sidelink HARQ-ACK information reporting has higher priority than SLPRS 230 transmission or reception may be configured or pre-configured by higher layers.

[0098] In another embodiment, no priority level is defined for SL PRS230 transmission or reception. In this case, for the priority ranking between SL PRS230 transmission / reception and SL transmission including PSSCH / PSCCH, S-SS / PSBCH blocks, and PSFCH of SL communication or SL reception including S-SS / PSBCH blocks and PSFCH, if the priority value of SL transmission or reception of SL communication is less than a threshold value (which can be configured or preconfigured by a higher layer), SL transmission or reception of SL communication has a higher priority than SLPRS230 transmission or reception. Otherwise, SL PRS230 transmission has a higher priority than SL transmission or reception of SL communication.

[0099] In another option, SL transmission or reception of SL communications always has higher priority than SL PRS 230 transmission or reception. In another option, SL PRS 230 transmission has higher priority than SL transmission or reception of SL communications.

[0100] In another option, whether SL transmission or reception of SL communication has higher priority than SL PRS 230 transmission or reception may be configured or pre-configured by a higher layer.

[0101] The following provides an embodiment of prioritizing the transmission or reception of SL PRS 230 for sidelink positioning when priority levels are defined for the transmission or reception of SL PRS 230. In one embodiment, one or more priorities may be defined for the transmission / reception of SL PRS 230 for sidelink positioning. In addition, a field may be included in the first stage (1 st Stage 2) or Stage 3 nd The SL PRS 230 may include a priority value in the SCI format of the SL PRS 230 (phase) to indicate the priority value sent by the SL PRS 230. Note that this may apply to Mode 1 and / or Mode 2 resource allocations of the SL PRS 230.

[0102] In one example, two priority values ​​may be defined for SL PRS 230 transmission and reception. st A one-bit field may be included in the Phase SCI format. Specifically, a bit "1" may indicate that the SL PRS 230 transmission has a high priority, while a bit "0" may indicate that the SL PRS 230 transmission has a low priority.

[0103] In another embodiment, when one or more priority values ​​are defined for SL PRS230 transmission and / or reception, for the priority sorting between SL PRS230 transmission / reception and UL transmission other than PRACH, or PUSCH and its retransmission scheduled by UL grant in RAR, or PUSCH and its retransmission corresponding to type 2 random access process, or PUCCH with sidelink HARQ-ACK information report, if the UL transmission is for PUCCH or PUSCH with priority index 1, then when the priority value of SLPRS230 transmission or reception is less than the priority threshold (the priority threshold can be configured or pre-configured by a higher layer), SL PRS230 transmission or reception has a higher priority than UL transmission; otherwise, UL transmission has a higher priority than SL PRS230 transmission or reception.

[0104] If no priority threshold is configured for SL PRS 230 transmission, UL transmission has a higher priority than SL PRS 230 transmission or reception.

[0105] In another option, UL transmissions always have a higher priority than SL PRS 230 transmissions or receptions. In another option, SL PRS 230 transmissions or receptions always have a higher priority than UL transmissions.

[0106] In another option, whether UL transmission has a higher priority than SL PRS 230 transmission or reception can be configured or preconfigured by a higher layer. In one example, when the parameter is configured, UL transmission has a higher priority than SL PRS 230 transmission or reception. Otherwise, SL PRS transmission has a higher priority than UL transmission.

[0107] In another embodiment, when one or more priority values ​​are defined for SL PRS230 transmission and / or reception, for the priority ranking between SL PRS230 transmission / reception and UL transmission other than PRACH, or PUSCH and its retransmission scheduled by UL grant in RAR, or PUSCH and its retransmission corresponding to type 2 random access procedure, or PUCCH with sidelink HARQ-ACK information report, if the UL transmission is for PUCCH or PUSCH with priority index 0, then when the priority value of SLPRS230 transmission or reception is less than the priority threshold (the priority threshold can be configured or preconfigured by a higher layer), SL PRS230 transmission or reception has a higher priority than UL transmission; otherwise, UL transmission has a higher priority than SL PRS230 transmission or reception. Note that the priority threshold can be configured for UL transmissions with priority indexes 0 and 1, respectively.

[0108] If no priority threshold is configured, UL transmission has higher priority than SL PRS 230 transmission or reception.

[0109] In another option, UL transmissions always have a higher priority than SL PRS 230 transmissions or receptions. In another option, SL PRS 230 transmissions or receptions always have a higher priority than UL transmissions.

[0110] In another option, whether UL transmission has a higher priority than SL PRS 230 transmission or reception can be configured or preconfigured by a higher layer. In one example, when the parameter is configured, UL transmission has a higher priority than SL PRS 230 transmission or reception. Otherwise, SL PRS 230 transmission has a higher priority than UL transmission.

[0111] In another embodiment, when one or more priority values ​​are defined for SL PRS230 transmission and / or reception, for the priority sorting between SL PRS230 transmission / reception and PUCCH or PUSCH transmission with sidelink HARQ-ACK information report, if the priority value of PUCCH or PUSCH transmission is less than the priority value of SL PRS230 transmission or reception, the PUCCH or PUSCH transmission has a higher priority than the SL PRS230 transmission or reception; otherwise, the SL PRS230 transmission or reception has a higher priority than the PUCCH or PUSCH transmission.

[0112] Figure 7 An operating environment 702 is shown. Operating environment 702 shows an example of complete cancellation of SLPRS 230 in overlapping symbols 312 when SL PRS 230 has a lower priority level than uplink transmission (uplink transmission has a higher priority than SL PRS 230). As with operating environment 602, operating environment 702 shows a set of overlapping symbols 312 between SLPRS 230 and message 306 in time slot 308, and the set of overlapping symbols 312 includes all 6 symbols 304 of SL PRS 230.

[0113] It is assumed that the message 306 is a PUCCH with a SL HARQ-ACK report. Figure 7 An example of prioritizing the SL PRS 230 and the PUCCH with SL HARQ-ACK report is shown when more than one priority value is defined for the SL PRS 230. In this example, the priority value of the PUCCH transmission is set to priority level 2, and the priority value of the SL PRS 230 transmission is set to priority level 3. Based on the above options, the PUCCH transmission has a higher priority than the SL PRS 230 transmission. In this case, all 6 symbols 304 of the SL PRS 230 are discarded, and the UE transmits all 11 symbols 304 of the PUCCH with the SL HARQ-ACK report.

[0114] In another embodiment, when one or more priority values ​​are defined for SL PRS230 transmission and / or reception, for the priority sorting between SL PRS230 transmission / reception and SL transmission of SL communication including PSSCH / PSCCH, S-SS / PSBCH blocks, and PSFCH, or SL reception including S-SS / PSBCH blocks and PSFCH, if the priority value of SL transmission or reception of SL communication is less than the priority value of SL PRS230 transmission or reception, the SL transmission or reception of SL communication has a higher priority than SL PRS230 transmission or reception; otherwise, SL PRS230 transmission has a higher priority than SL transmission or reception of SL communication.

[0115] In another option, SL transmission or reception of SL communications always has higher priority than SL PRS 230 transmission or reception. In another option, SL PRS 230 transmission has higher priority than SL transmission or reception of SL communications.

[0116] In another option, whether SL transmission or reception of SL communication has higher priority than SL PRS 230 transmission or reception may be configured or preconfigured by a higher layer or indicated by the SCI format.

[0117] In some aspects, the above-described embodiments may be applied to one or both of a shared resource pool for SL communication and SL positioning and a dedicated resource pool for SLPRS 230 .

[0118] In another embodiment, in the case of a shared resource pool for SL communication and SL positioning, the priority value of the SL communication and the priority value of the SL PRS 230 may be determined based on a function of the priority value of the SL communication and the priority value of the SL PRS 230. st The value of the Priority field indicated in the Phase SCI.

[0119] In certain aspects, this may apply to situations where both PSSCH and SL PRS 230 are scheduled in a shared resource pool.

[0120] In one example, 1 st The value of the priority field indicated in the phase SCI may correspond to a higher one of the priority value of the SL communication and the priority value of the SL PRS 230 .

[0121] In another option, when the SL PRS 230 is not scheduled in the shared resource pool and 1 st Phase SCI indicates a new 2 associated with the SLPRS 230 schedule nd When the SCI format is in stage 1 st The value of the priority field indicated in the phase SCI may correspond to the priority value of the SL communication.

[0122] In another option, when SL PRS 230 is scheduled but the PSSCH carrying SL-SCH is not scheduled in the shared resource pool, 1 st The value of the priority field indicated in the phase SCI may correspond to the priority value of the SL PRS 230 .

[0123] In another option, for a shared resource pool, the priority field may be included in 2 nd In some aspects, the new 2 nd Phase SCI format can be used 1 st The code point “11” in the phase SCI indicates that: In addition, the value of the priority field may correspond to the priority value of the SL PRS 230 .

[0124] In another option, if the SL PRS 230 can be multiplexed in the time slot indicated by the SL resource grant after resource selection, then 1 st The priority value indicated in the phase SCI may correspond to the priority value of the SL communication.

[0125] As a further extension, when the SL PRS 230 is not scheduled in the shared resource pool, the priority field can still be nd In this case, the receiving UE can ignore 2 nd The priority field in the Phase SCI.

[0126] In another embodiment, for a dedicated resource pool, when only the PSCCH and the SL PRS 230 are included, a priority field may be included in a single SCI format, wherein the value of the priority field may correspond to the priority value of the SL PRS 230 .

[0127] Figure 8 An apparatus 800 suitable for implementing any logic supporting the embodiments described herein is shown. In one embodiment, for example, the apparatus 800 is implemented by a UE, such as an anchor UE 222 or a target UE 220 in a V2V or V2X network.

[0128] like Figure 8As shown, an apparatus 800 for a user equipment (UE) includes: a memory interface 806, which is used to send or receive priority information 824 to or from a data storage device 810, and the priority information 824 is used to schedule the transmission or reception of SL PRS230 in an NR system (such as the wireless communication system 100 or the wireless communication system 200). The apparatus 800 also includes: a processor circuit 802, which is communicatively coupled to the memory interface 806. The processor circuit 802 implements logic for a detector 804, a decoder 820, and a scheduler 826. The detector 804 operates to detect a group of overlapping symbols 312 between a message 306 and a SL PRS230 in a time slot 308 for a frame in the time domain of the NR system. In one embodiment, the message 306 includes data for SL transmission or UL transmission. The decoder 820 decodes the priority information 824 of the SL PRS230 from the SCI 828 and stores the priority information 824 in the data storage device 810 for subsequent extraction from the data storage device 810. The scheduler 826 determines a schedule for transmission or reception of the SL PRS 230 and the message 306 based on the priority information 824 of the SLPRS 230. The processor circuit 802 sends an instruction about transmission or reception of the SL PRS 230 or the message 306 to the radio frequency (RF) circuit 818 through the interface 812 according to the schedule. The RF circuit 818 transmits or receives the SL PRS 230 and / or the message 306 as an RF signal through the wireless communication system 100 or the wireless communication system 200.

[0129] In one embodiment, the priority information 824 includes the priority information of the SL PRS 230, the priority information of the message 306, or the priority information of both the SL PRS 230 and the message 306. The priority information 824 may include a priority level defined in a priority mechanism defined for the wireless communication system 100 or the wireless communication system 200. The priority information 824 may also include a threshold value defined for the defined priority level. The scheduler 826 may compare the priority value of the SL PRS 230 or the message 306 with the defined threshold value, and schedule the transmission or reception of the SL PRS 230 or the message 306 based on the comparison result.

[0130] The apparatus 800 may also include a scheduler 826 of the processor circuit 802 to determine that the SLPRS 230 has a lower priority and the message 306 has a higher priority based on the priority information 824. The scheduler 826 then schedules the message 306 with the higher priority for transmission or reception. The scheduler 826 discards or cancels a group of overlapping symbols 312 of the SL PRS 230 with the lower priority. The scheduler 826 schedules a group of non-overlapping symbols 314 of the SL PRS 230 for transmission or reception through the RF circuit 818.

[0131] The apparatus 800 may also include a scheduler 826 of the processor circuit 802 to determine that the SLPRS 230 has a lower priority and the message 306 has a higher priority based on the priority information 824. In this case, the scheduler 826 schedules the message 306 with the higher priority to be transmitted or received by the RF circuit 818. The scheduler 826 also schedules to discard or cancel all symbols 304 of the SLPRS 230 with the lower priority.

[0132] The apparatus 800 may also include a scheduler 826 of the processor circuit 802 to determine that the SLPRS 230 has a higher priority and the message 306 has a lower priority based on the priority information 824. The scheduler 826 schedules the SLPRS 230 with a higher priority to be transmitted or received by the RF circuit 818. The scheduler 826 also schedules to discard all symbols 304 of the message 306 with a lower priority.

[0133] Apparatus 800 may also include scheduler 826 of processor circuit 802 to determine that SL PRS 230 does not have a priority level based on priority information 824 or by the absence of priority information 824 in data storage device 810. Scheduler 826 schedules message 306 for transmission or reception via RF circuit 818 according to a default priority setting.

[0134] The apparatus 800 may also include a decoder 820 of the processor circuit 802 to extract from a physical sidelink control channel (PSCCH) having a first stage (1 st The SCI 828 of the second stage (2 nd The SCI 828 in the SCI format of the stage) decodes the sidelink scheduling information 832 of the SL PRS 230. In one embodiment, 1 st Stage SCI format or 2 nd One or more information fields of the Phase SCI format indicate priority information 824 of the SL PRS 230. The decoder 820 decodes data from the PSCCH or PSSCH and extracts the priority information 824 from the information field. The decoder 820 then stores the priority information 824 in the data storage device 810 of the apparatus 800.

[0135] The apparatus 800 may also include a decoder 820 of the processor circuit 802 to extract from a physical sidelink control channel (PSCCH) having a first stage (1 stThe SCI 828 of the SCI format 1-B of the first stage decodes the sidelink scheduling information 832 of the SL PRS 230. In one embodiment, for example, the SCI format 1-B includes an information field for a priority, a source identifier (ID), a destination ID, a cast type indicator, or a resource reservation period Nrsv-period, where if a higher layer parameter sl-PRSResourceReservePeriodList is configured, then Nrsv-period is the number of entries in the higher layer parameter sl-PRSResourceReservePeriodList, otherwise Nrsv-period is 0 bits.

[0136] The apparatus 800 may also include a decoder 820 of the processor circuit 802 to extract from the physical sidelink shared channel (PSSCH) the second stage (2 nd The SCI 828 of the SCI format 2-D of the first stage decodes the sidelink scheduling information 832 of the SL PRS 230. In one embodiment, for example, the SCI format 2-D includes an information field for a hybrid automatic repeat request (HARQ) process number including 4 bits, a new data indicator including 1 bit, a redundancy version including 2 bits, a source identifier (ID) including 8 bits, a destination ID including 16 bits, or a HARQ feedback enable / disable indicator including 1 bit.

[0137] As previously referenced Figure 1As described, the various embodiments discussed herein may be implemented in a wireless communication system defined in 3GPP TS 38.212 entitled “Technical Specification Group Radio Access Network; NR; Multiplexing and channel coding” (version 17.5.0 released in March 2023 (“3GPP TS 38.212”)); may be implemented in a wireless communication system defined in 3GPP TS 38.213 entitled “Technical Specification Group Radio Access Network; NR; Physical layer procedures for control” (version 17.6.0 released in June 2023 (“3GPP TS28.213”); may be implemented in a wireless communication system defined in any descendant, revision, or variant of the above two. It will be understood that these embodiments may be implemented in accordance with other 3GPP TS, TR and WI and other wireless standards issued by other standard entities. The embodiments are not limited in this context.

[0138] For example, with respect to 3GPP TS 38.212, the embodiments may be implemented as part of 3GPP TS 38.212 Release 18. By way of example and not limitation, these embodiments may be implemented in Section 8.3.1.2 entitled "SCI format 1-B" and Section 8.4.1.4 entitled "SCI format 2-D" of Release 18 of 3GPP TS 38.212. Section 8.4 entitled "Sidelink control information on PSSCH", where the proposed Section 8.3.1.2 is reproduced as follows:

[0139] 8.3.1.2 SCI Format 1-B

[0140] SCI format 1-B is used for scheduling of SL PRS.

[0141] The following information is sent via SCI Format 1-B:

[0142] - Priority—x bits, as defined in clause xx of [12, TS 23.287] and clause xx of [8, TS 38.321].

[0143] - Source ID—x bits, as defined in clause xx of [6, TS 38.214].

[0144] - Destination ID—x bits, as defined in clause xx of [6, TS 38.214].

[0145] - Broadcast type indicator—2 bits, as defined in clause xx of [6, TS 38.214].

[0146] -Resource reservation period—[log2N rsv-period ] bits, as defined in clause xx of [5, TS 38.213], where, if the higher layer parameter sl-PRSResourceReservePeriodList is configured, Nrsv-period is the number of entries in the higher layer parameter sl-PRSResourceReservePeriodList; otherwise Nrsv-period is 0 bits.

[0147] Section 8.4 entitled "Sidelink control information on PSSCH", in which the proposed section 8.4.1.4 is reproduced as follows:

[0148] 8.4.1.4 SCI Format 2-D

[0149] SCI format 2-D is used for decoding of PSSCH and scheduling of SL PRS.

[0150] The following information is sent via SCI Format 2-D:

[0151] -HARQ process number—several bits.

[0152] - New data indicator—1 bit.

[0153] - Redundancy Version—2 bits, as defined in Table 7.3.1.1.1-2.

[0154] - Source ID—8 bits, as defined in clause 8.1 of [6, TS 38.214].

[0155] - Destination ID—16 bits, as defined in clause 8.1 of [6, TS 38.214].

[0156] - HARQ feedback enable / disable indicator—1 bit, as defined in clause 16.3 of [5, TS 38.213].

[0157] The operation of the disclosed embodiments may be further described with reference to the following figures. Some of the figures may include logic flows. Although the figures presented herein may include specific logic flows, it is understood that the logic flows only provide examples of how the general functions described herein may be implemented. In addition, unless otherwise stated, a given logic flow does not necessarily have to be performed in the order presented. In addition, in some embodiments, not all actions shown in the logic flow are required. In addition, a given logic flow may be implemented by hardware elements, software elements executed by a processor, or any combination thereof. The embodiments are not limited in this context.

[0158] Fig. 9 An embodiment of a logic flow 900 is shown. The logic flow 900 may represent some or all operations performed by one or more embodiments described herein. For example, the logic flow 900 may include some or all operations performed by a device or entity (such as the apparatus 800) within the wireless communication system 100 or the wireless communication system 200. The embodiments are not limited in this context.

[0159] In block 902, the logic flow 900 detects a set of overlapping symbols between a message in a time slot for a frame and a sidelink (SL) positioning reference signal (PRS) (SL PRS) in a time domain of a new radio (NR) system. For example, the detector 804 of the processor circuit 802 of the apparatus 800 detects a set of overlapping symbols between a message 306 in a time slot 308 for a frame and the SL PRS 230 in a time domain of the NR system (e.g., the wireless communication system 100 or the wireless communication system 200). The message 306 may include data for SL communication or UL communication.

[0160] At block 904 , the logic flow 900 retrieves the priority information of the SL PRS from the data storage device. For example, the scheduler 826 of the processor circuit 802 of the apparatus 800 retrieves the priority information 824 of the SL PRS 230 from the data storage device 810 .

[0161] At block 906 , the logic flow 900 determines a schedule for sending or receiving the SL PRS and the message based on the priority information. For example, the scheduler 826 determines a schedule for sending or receiving the SL PRS 230 and the message 306 based on the priority information 824 .

[0162] Fig.10An embodiment of a logic flow 1000 is shown. The logic flow 1000 may represent some or all operations performed by one or more embodiments described herein. For example, the logic flow 1000 may include some or all operations performed by a device or entity (such as the apparatus 800) within the wireless communication system 100 or the wireless communication system 200. The embodiments are not limited in this context.

[0163] In block 1002, logic flow 1000 detects a set of overlapping symbols between a message and a sidelink (SL) positioning reference signal (PRS) (SL PRS) in a time slot for a frame in a time domain of a new radio (NR) system. In block 1004, logic flow 1000 extracts priority information of the SL PRS from a data storage device. In block 1006, logic flow 1000 determines a schedule for transmission or reception of the SL PRS and the message based on the priority information. The examples of blocks 1002, 1004, and 1006 are similar to the examples given for blocks 902, 904, and 906 of logic flow 900, respectively.

[0164] At block 1008 , the logic flow 1000 determines that the SL PRS has a lower priority and the message has a higher priority. For example, the scheduler 826 determines based on the priority information 824 that the SL PRS 230 has a lower priority and the message has a higher priority.

[0165] At block 1010 , the logic flow 1000 schedules the message with the higher priority for transmission or reception. For example, the scheduler 826 schedules the message 306 with the higher priority for transmission or reception via the RF circuit 818 .

[0166] At block 1012, the logic flow 1000 discards a set of overlapping symbols of the SL PRS having a lower priority. For example, the scheduler 826 schedules the SL PRS 230 to discard a set of overlapping symbols 312 of the SL PRS 230 having a lower priority.

[0167] At block 1014 , the logic flow 1000 schedules a set of non-overlapping symbols of the SL PRS for transmission or reception. For example, the scheduler 826 schedules a set of non-overlapping symbols 314 of the SL PRS 230 for transmission or reception by the RF circuit 818 .

[0168] Fig.11 An embodiment of a logic flow 1100 is shown. The logic flow 1100 may represent some or all operations performed by one or more embodiments described herein. For example, the logic flow 1100 may include some or all operations performed by a device or entity (such as the apparatus 800) within the wireless communication system 100 or the wireless communication system 200. The embodiments are not limited in this context.

[0169] In block 1102, logic flow 1100 detects a set of overlapping symbols between a message and a sidelink (SL) positioning reference signal (PRS) (SL PRS) in a time slot for a frame in a time domain of a new radio (NR) system. In block 1104, logic flow 1100 extracts priority information of the SL PRS from a data storage device. In block 1106, logic flow 1100 determines a schedule for transmission or reception of the SL PRS and the message based on the priority information. The examples of blocks 1102, 1104, and 1106 are similar to the examples given for blocks 902, 904, and 906 of logic flow 900, respectively.

[0170] At block 1108 , the logic flow 1100 determines that the SL PRS has a lower priority and the message has a higher priority. For example, the scheduler 826 determines based on the priority information 824 that the SL PRS 230 has a lower priority and the message 306 has a higher priority.

[0171] At block 1110 , the logic flow 1100 schedules the message with the higher priority for transmission or reception. For example, the scheduler 826 schedules the message 306 with the higher priority for transmission or reception via the RF circuit 818 .

[0172] At block 1112, the logic flow 1100 discards all symbols of the SL PRS having a lower priority. For example, the scheduler 826 schedules the SL PRS 230 to discard all symbols 304 of the SL PRS 230 having a lower priority.

[0173] Fig.12 An embodiment of a logic flow 1200 is shown. The logic flow 1200 may represent some or all operations performed by one or more embodiments described herein. For example, the logic flow 1200 may include some or all operations performed by a device or entity (such as the apparatus 800) within the wireless communication system 100 or the wireless communication system 200. The embodiments are not limited in this context.

[0174] In block 1202, logic flow 100 detects a set of overlapping symbols between a message and a sidelink (SL) positioning reference signal (PRS) (SL PRS) in a time slot for a frame in a time domain of a new radio (NR) system. In block 1204, logic flow 1200 extracts priority information of the SL PRS from a data storage device. In block 1206, logic flow 1200 determines a schedule for transmission or reception of the SL PRS and the message based on the priority information. The examples of blocks 1202, 1204, and 1206 are similar to the examples given for blocks 902, 904, and 906 of logic flow 900, respectively.

[0175] At block 1208 , the logic flow 1200 determines that the SL PRS has a higher priority and the message has a lower priority. For example, the scheduler 826 determines based on the priority information 824 that the SL PRS 230 has a higher priority and the message 306 has a lower priority.

[0176] At block 1210 , the logic flow 1200 schedules the SL PRS with a higher priority for transmission or reception. For example, the scheduler 826 schedules the SL PRS 230 with a higher priority for transmission or reception through the RF circuit 818 .

[0177] At block 1212, the logic flow 1200 discards all symbols of messages having a lower priority. For example, the scheduler 826 schedules the SL PRS 230 to discard all symbols 304 of the messages 306 having a lower priority.

[0178] Fig.13 A message flow 1300 is shown. The message flow 1300 provides an example of messages supporting logic flow 900, logic flow 1000, logic flow 1100, or logic flow 1200 in a NR system (e.g., wireless communication system 100 or wireless communication system 200).

[0179] like Fig.13 As shown, at block 1302, UE 1316 generates information suitable for SL PRS 230. For example, assume that UE 1316 is anchor UE 222. UE 1316 sends message 1304 as SL PRS 230 to UE 1320 implemented as target UE 220. At some time before or after UE 1320 receives message 1304, assume that RAN 1318 generates information suitable for sidelink scheduling information 832 and sends message 1306 with sidelink scheduling information 832. UE 1320 decodes sidelink scheduling information 832 from message 1306 and stores it in data storage device 810 of apparatus 800.

[0180] At some point, UE 1320 decides to send a set of overlapping messages 1310, wherein the first message 1310 includes SL communication for UE 1316 and the second message 1310 includes UL communication for RAN 1318. The SL communication may include SL PRS 230 or another type of SL communication. Assume that the first message and the second message have overlapping symbols 312 in the physical time slot 308 of the subframe of the frame used for SL communication. UE 1320 implements the priority technique described in reference logic flow 900, logic flow 1000, logic flow 1100, or logic flow 1200 to determine whether the first message or the second message has a higher priority level or a lower priority level relative to each other. At block 1324, UE 1320 schedules the transmission of the first message or the second message based on the given priority technique. For example, UE 1320 schedules to transmit some or all symbols 304 of the first message, transmit some or all symbols 304 of the second message, cancel some or all symbols 304 of the first message, or cancel some or all symbols 304 of the second message.

[0181] The message flow 1300 may also be applicable to conflicting message reception and message transmission.Embodiments are not limited to a particular message direction, priority scheme, or number of symbols 304 to be passed or cancelled.

[0182] Figures 10 to 13 Various systems, devices, and components are shown that can implement various aspects of the disclosed embodiments. These systems, devices, and components can be used with reference to Figure 1 The systems, devices, or components described are the same or similar.

[0183] Fig.14 A network 1400 according to various embodiments is shown. The network 1400 may operate in a manner consistent with the 3GPP technical specifications for LTE or 5G / NR systems. However, the example embodiments are not limited in this regard, and the described embodiments may be applied to other networks that benefit from the principles described herein, such as future 3GPP systems, etc.

[0184] The network 1400 may include a UE 1402, which may include any mobile or non-mobile computing device designed to communicate with the RAN 1430 over an air connection. The UE 1402 may be communicatively coupled to the RAN 1430 via a Uu interface. The UE 1402 may be, but is not limited to, a smartphone, a tablet, a wearable computer device, a desktop computer, a laptop computer, an in-vehicle infotainment device, an in-vehicle entertainment device, a dashboard, a head-up display device, an on-board diagnostic device, a dashboard mobile equipment, a mobile data terminal, an electronic engine management system, an electronic / engine control unit, an electronic / engine control module, an embedded system, a sensor, a microcontroller, a control module, an engine management system, a networked appliance, a machine type communication device, an M2M or D2D device, an IoT device, etc.

[0185] In some embodiments, the network 1400 may include multiple UEs directly coupled to each other via a sidelink interface. The UE may be an M2M / D2D device that communicates using a physical sidelink channel (e.g., but not limited to, PSBCH, PSDCH, PSSCH, PSCCH, PSFCH, etc.).

[0186] In some embodiments, UE 1402 may additionally communicate with AP 1404 over the air. AP 1404 may manage a WLAN connection, which may be used to offload some / all network traffic from RAN 1430. The connection between UE 1402 and AP 1404 may conform to any IEEE 1402.11 protocol, where AP 1404 may be a Wireless Fidelity Router. In some embodiments, UE 1402, RAN 1430, and AP 1404 may utilize cellular WLAN aggregation (eg, LWA / LWIP). Cellular WLAN aggregation may involve configuring UE 1402 by RAN 1430 to utilize both cellular radio resources and WLAN resources.

[0187] RAN 1430 may include one or more access nodes, such as AN 1460. AN 1460 may terminate the air interface protocol of UE 1402 by providing access layer protocols including RRC, PDCP, RLC, MAC, and L1 protocols. In this way, AN 1460 may enable data / voice connections between CN 1418 and UE 1402. In some embodiments, AN 1460 may be implemented in a discrete device or as one or more software entities running on a server computer (as part of a virtual network, such as a CRAN or a virtual baseband unit pool). AN 1460 may be referred to as a BS, gNB, RAN node, eNB, ng-eNB, NodeB, RSU, TRxP, TRP, etc. AN 1460 may be a macro cell base station or a low power base station for providing a femto cell, a pico cell, or other similar cells with a smaller coverage area, a smaller user capacity, or a higher bandwidth than a macro cell.

[0188] In an embodiment where the RAN 1430 includes multiple ANs, they may be coupled to each other via an X2 interface (if the RAN 1430 is an LTE RAN) or an Xn interface (if the RAN 1430 is a 5G RAN). In some embodiments, the X2 / Xn interface may be divided into a control / user plane interface, which may allow the AN to communicate information related to handover, data / context transfer, mobility, load management, interference coordination, etc.

[0189] The ANs of the RAN 1430 may each manage one or more cells, cell groups, component carriers, etc., to provide an air interface for network access to the UE 1402. The UE 1402 may simultaneously connect to multiple cells provided by the same or different ANs of the RAN 1430. For example, the UE 1402 and the RAN 1430 may use carrier aggregation to allow the UE 1402 to connect to multiple component carriers, each corresponding to a Pcell or Scell. In a dual-connectivity scenario, the first AN may be a primary node providing an MCG, and the second AN may be a secondary node providing an SCG. The first / second AN may be any combination of eNBs, gNBs, ng-eNBs, etc.

[0190] RAN 1430 can provide an air interface on a licensed spectrum or an unlicensed spectrum. In order to operate in an unlicensed spectrum, a node can use LAA, eLAA, and / or feLAA mechanisms based on CA technology and PCell / Scell. Before accessing the unlicensed spectrum, a node can perform a medium / carrier sensing operation based on, for example, a listen-before-talk (LBT) protocol.

[0191] In the V2X scenario, the UE 1402 or AN 1460 may be or act as an RSU, which may refer to any traffic infrastructure entity used for V2X communication. The RSU may be implemented in or by a suitable AN or a stationary (or relatively stationary) UE. The RSU may be implemented in or by a UE, which may be referred to as a "UE-type RSU"; the RSU may be implemented in or by an eNB, which may be referred to as an "eNB-type RSU"; the RSU may be implemented in or by a gNB, which may be referred to as a "gNB-type RSU"; and so on. In one example, the RSU is a computing device coupled to a radio frequency circuit located on the roadside, which provides connection support for passing vehicle UEs. The RSU may also include internal data storage circuits to store intersection map geometry, traffic flow statistics, media, and applications / software for sensing and controlling ongoing vehicle and pedestrian traffic flows. The RSU may provide very low latency communications required for high-speed events such as collision avoidance, traffic flow warnings, etc. In addition, or alternatively, the RSU may provide other cellular / WLAN communication services. The components of the RSU may be packaged in a weatherproof enclosure suitable for outdoor installation and may include a network interface controller to provide a wired connection to a traffic flow signal controller or a backhaul network (e.g., Ethernet).

[0192] In some embodiments, the RAN 1430 may be an LTE RAN 1426 with an eNB (e.g., eNB 1454). The LTE RAN 1426 may provide an LTE air interface with the following characteristics: SCS of 15 kHz; CP-OFDM waveform for DL ​​and SC-FDMA waveform for UL; turbo codes for data and TBCC for control; etc. The LTE air interface may rely on CSI-RS for CSI acquisition and beam management; rely on PDSCH / PDCCH DMRS for PDSCH / PDCCH demodulation; and rely on CRS for cell search and initial acquisition, channel quality measurement, and channel estimation to achieve coherent demodulation / detection at the UE. The LTE air interface may operate on frequency bands below 6 GHz.

[0193] In some embodiments, the RAN 1430 may be a NG-RAN 1428 having a gNB (e.g., gNB 1456) or an ng-eNB (e.g., ng-eNB 1458). The gNB 1456 may be connected to a 5G-enabled UE using a 5GNR interface. The gNB 1456 may be connected to the 5G core via an NG interface, which may include an N2 interface or an N3 interface. The ng-eNB 1458 may also be connected to the 5G core via an NG interface, but may also be connected to the UE via an LTE air interface. The gNB 1456 and the ng eNB 1458 may be connected to each other via an Xn interface.

[0194] In some embodiments, the NG interface can be divided into two parts: an NG user plane (NG-U) interface (e.g., N3 interface), which carries traffic data between the nodes of NG-RAN 1428 and UPF 1438; and an NG control plane (NG-C) interface (e.g., N2 interface), which is a signaling interface between the nodes of NG-RAN 1428 and AMF 1434.

[0195] NG-RAN 1428 may provide a 5G-NR air interface with the following features: variable SCS; CP-OFDM for DL, CP-OFDM and DFT-s-OFDM for UL; polar code, repetition code, simple code, and Reed-Muller code for control and LDPC for data. The 5G-NR air interface may rely on CSI-RS, PDSCH / PDCCH DMRS similar to the LTE air interface. The 5G-NR air interface may not use CRS, but may use PBCH DMRS for PBCH demodulation; use PTRS for PDSCH phase tracking; and use tracking reference signals for time tracking. The 5G-NR air interface may operate on a FR1 band including bands below 6 GHz or a FR2 band including bands from 24.25 GHz to 52.6 GHz. The 5G-NR air interface may include an SSB, which is an area of ​​a downlink resource grid including PSS / SSS / PBCH.

[0196] In some embodiments, the 5G-NR air interface may utilize BWP for various purposes. For example, BWP may be used for dynamic adaptation of SCS. For example, UE 1402 may be configured with multiple BWPs, each of which is configured with a different SCS. When a BWP change is indicated to UE 1402, the SCS sent also changes. Another use case example of BWP is related to energy saving. Specifically, UE 1402 may be configured with multiple BWPs with different numbers of frequency resources (e.g., PRBs) to support data transmission in different traffic load scenarios. BWPs containing fewer PRBs may be used for data transmission with smaller traffic loads while allowing energy saving at UE 1402 and in some cases gNB 1456. BWPs containing more PRBs may be used in scenarios with higher traffic loads.

[0197] RAN 1430 is communicatively coupled to CN 1418, which includes network elements that provide various functions to support data and telecommunication services for customers / subscribers (e.g., users of UE 1402). The components of CN 1418 may be implemented in one physical node or in different physical nodes. In some embodiments, NFV may be used to virtualize any or all functions provided by the network elements of CN 1418 onto physical computing / storage resources in servers, switches, etc. A logical instantiation of CN 1418 may be referred to as a network slice, and a logical instantiation of a portion of CN 1418 may be referred to as a network sub-slice.

[0198] In some embodiments, CN 1418 may be LTE CN 1424, which may also be referred to as EPC. LTE CN 1424 may include MME 1406, SGW 1408, SGSN 1414, HSS 1416, PGW 1410, and PCRF 1412 coupled to each other via interfaces (or "reference points"), as shown. The functions of the elements of LTE CN 1424 may be briefly described as follows.

[0199] The MME 1406 may implement mobility management functions to track the current location of the UE 1402 to facilitate paging, bearer activation / deactivation, handover, gateway selection, authentication, etc.

[0200] The SGW 1408 may terminate the S1 interface to the RAN and route data packets between the RAN and the LTE CN 1424. The SGW 1408 may be a local mobility anchor for handovers between RAN nodes and may also provide an anchor for inter-3GPP mobility. Other responsibilities may include lawful interception, charging, and some policy enforcement.

[0201] SGSN 1414 can track the location of UE 1402 and perform security functions and access control. In addition, SGSN 1414 can perform inter-EPC node signaling for mobility between different RAT networks; PDN and S-GW selection specified by MME 1406; MME selection for handover; etc. The S3 reference point between MME 1406 and SGSN 1414 can enable user and bearer information exchange for mobility between 3GPP access networks in idle / active states.

[0202] The HSS 1416 may include a database for network users (including subscription related information) to support the handling of communication sessions by network entities. The HSS 1416 may provide support for routing / roaming, authentication, authorization, naming / addressing resolution, location dependency, etc. The S6A reference point between the HSS 1416 and the MME 1406 may enable the transmission of subscription and authentication data for authenticating / authorizing user access to the LTE CN 1418.

[0203] The PGW 1410 may terminate the SGi interface towards a data network (DN) 1422, which may include an application / content server 1420. The PGW 1410 may route data packets between the LTE CN 1424 and the data network 1422. The PGW 1410 may be coupled to the SGW 1408 via an S5 reference point to facilitate user plane tunneling and tunnel management. The PGW 1410 may also include a node (e.g., PCEF) for policy enforcement and charging data collection. In addition, the SGi reference point between the PGW 1410 and the data network 1422 may be, for example, an operator-external public, private PDN, or an operator-internal packet data network for providing IMS services. The PGW 1410 may be coupled to the PCRF 1412 via a Gx reference point.

[0204] PCRF 1412 is the policy and charging control element of LTE CN 1424. PCRF 1412 may be communicatively coupled to application / content server 1420 to determine appropriate QoS and charging parameters for service flows. PCRF 1410 may provide the relevant rules to PCEF (via Gx reference point) with appropriate TFT and QCI.

[0205] In some embodiments, CN 1418 may be 5GC 1452. 5GC 1452 may include AUSF 1432, AMF 1434, SMF 1436, UPF 1438, NSSF 1440, NEF 1442, NRF 1444, PCF 1446, UDM 1448, and AF 1450 coupled to each other via interfaces (or "reference points"), as shown. The functions of the elements of 5GC 1452 may be briefly described as follows.

[0206] AUSF 1432 may store data for authentication of UE 1402 and handle authentication-related functions. AUSF 1432 may facilitate a common authentication framework for various access types. In addition to communicating with other elements of 5GC 1452 via reference points as shown, AUSF 1432 may also present an interface based on NAUSF services.

[0207] AMF 1434 may allow other functions of 5GC 1452 to communicate with UE 1402 and RAN 1430, and subscribe to notifications about mobility events relative to UE 1402. AMF 1434 may be responsible for registration management (e.g., for registering UE 1402), connection management, reachability management, mobility management, lawful interception of AMF-related events, and access authentication and authorization. AMF 1434 may provide for the transmission of SM messages between UE 1402 and SMF 1436, and act as a transparent proxy for routing SM messages. AMF 1434 may also provide for the transmission of SMS messages between UE 1402 and SMSF. AMF 1434 may interact with AUSF 1432 and UE 1402 to perform various security anchor and context management functions. In addition, AMF 1434 can be the termination point of the RAN CP interface, which can include or be the N2 reference point between RAN 1430 and AMF 1433; AMF 1434 can be the termination point of NAS (N1) signaling and perform NAS encryption and integrity protection. AMF 1434 can also support NAS signaling with UE 1402 through the N3 IWF interface.

[0208] SMF 1436 may be responsible for: SM (e.g., session establishment, tunnel management between UPF 1438 and AN 1460); UE IP address allocation and management (including optional authorization); selection and control of UP functions; configuring traffic steering at UPF 1438 to route traffic to the appropriate destination; terminating the interface to the policy control function; policy enforcement, charging, and QoS of the control part; lawful interception (for SM events and interface to LI system); terminating the SM part of the NAS message; downlink data notification; initiating AN-specific SM information, which is sent to AN 1460 over N2 via AMF 1434; and determining the SSC mode of the session. SM may refer to the management of a PDU session, and a PDU session or "session" may refer to a PDU connection service that provides or enables the exchange of PDUs between UE 1402 and data network 1422.

[0209] The UPF 1438 may serve as an anchor point for intra-RAT and inter-RAT mobility, an external PDU session point interconnecting with the data network 1422, and a branch point to support multi-homed PDU sessions. The UPF 1438 may also perform packet routing and forwarding, perform packet inspection, perform the user plane portion of policy rules, lawful interception of packets (UP collection), perform traffic usage reporting, perform QoS processing for the user plane (e.g., packet filtering, gating, UL / DL rate enforcement), perform uplink traffic validation (e.g., SDF to QoS flow mapping), transport level packet marking in uplink and downlink, and perform downlink packet buffering and downlink data notification triggering. The UPF 1438 may include an uplink classifier to support routing of traffic flows to the data network.

[0210] NSSF 1440 may select a set of network slice instances to serve UE 1402. NSSF 1440 may also determine the allowed NSSAI and the mapping to the subscribed S-NSSAI, if necessary. NSSF 1440 may also determine a set of AMFs or a list of candidate AMFs for serving UE 1402 based on appropriate configuration and possibly by querying NRF 1444. The selection of a set of network slice instances for UE 1402 may be triggered by AMF 1434 (with which UE 1402 registers by interacting with NSSF 1440), which may result in a change of AMF. NSSF 1440 may interact with AMF 1434 via the N22 reference point; and may communicate with another NSSF in the visited network via the N31 reference point (not shown). In addition, NSSF 1440 may present an interface based on Nnssf services.

[0211] NEF 1442 can securely expose services and capabilities provided by 3GPP network functions for third parties, internal exposure / re-exposure, AF (e.g., AF 1450), edge computing or fog computing systems, etc. In such an embodiment, NEF 1442 can authenticate, authorize, or throttle AF. NEF 1442 can also translate information exchanged with AF 1450 and information exchanged with internal network functions. For example, NEF 1442 can translate between AF service identifiers and internal 5GC information. NEF 1442 can also receive information from other NFs based on the exposed capabilities of other NFs. The information can be stored at NEF 1442 as structured data, or stored in a data storage NF using a standardized interface. The stored information can then be re-exposed to other NFs and AFs by NEF 1442, or used for other purposes (such as analysis). In addition, NEF 1442 can present an interface based on Nnef services.

[0212] NRF 1444 may support service discovery functionality, receive NF discovery requests from NF instances, and provide information about discovered NF instances to NF instances. NRF 1444 also maintains information about available NF instances and their supported services. As used herein, the terms "instantiate," "instantiate," etc. may refer to the creation of an instance, and "instance" may refer to the specific occurrence of an object, which may occur, for example, during the execution of a program code. In addition, NRF 1444 may present an interface based on Nnrf services.

[0213] PCF 1446 can provide policy rules to the control plane functions to enforce them, and can also support a unified policy framework for governing network behavior. PCF 1446 can also implement a front end to access subscription information related to policy decisions in the UDR of UDM 1448. In addition to communicating with functions through reference points as shown, PCF 1446 also presents an interface based on Npcf services.

[0214] The UDM 1448 may process subscription-related information to support the processing of communication sessions by network entities, and may store subscription data of the UE 1402. For example, subscription data may be communicated between the UDM 1448 and the AMF 1434 via the N8 reference point. The UDM 1448 may include two parts: an application front end and a UDR. The UDR may store structured data of subscription data and policy data of the UDM 1448 and PCF 1446 and / or exposure and application data of the NEF 1442 (including PFD for application detection, application request information of multiple UEs 1402). The Nudr service-based interface may be presented by the UDR 221 to allow the UDM 1448, PCF 1446, and NEF 1442 to access a specific set of stored data and read, update (e.g., add, modify), delete, and subscribe to notifications about changes in related data in the UDR. The UDM may include a UDM-FE, which is responsible for handling credentials, location management, subscription management, etc. Several different front ends can provide services to the same user in different transactions. UDM-FE accesses subscription information stored in UDR and performs authentication credential processing, user identity processing, access authorization, registration / mobility management, and subscription management. In addition to communicating with other NFs through reference points as shown, UDM 1448 can also present an interface based on Nudm services.

[0215] The AF 1450 can provide application influence on traffic routing, provide access to the NEF, and interact with the policy framework for policy control.

[0216] In some embodiments, 5GC 1452 can enable edge computing by selecting an operator / third-party service that is geographically close to the point where UE 1402 attaches to the network. This can reduce latency and load on the network. In order to provide an edge computing implementation, 5GC 1452 can select a UPF 1438 close to UE 1402 and perform traffic steering from UPF 1438 to data network 1422 through the N6 interface. This can be based on UE subscription data, UE location, and information provided by AF 1450. In this way, AF1450 can affect UPF (re)selection and traffic routing. Based on operator deployment, when AF 1450 is regarded as a trusted entity, the network operator can allow AF 1450 to interact directly with relevant NFs. In addition, AF 1450 can present an interface based on Naf services.

[0217] The data network 1422 may represent various network operator services, Internet access, or third-party services, which may be provided by one or more servers including, for example, the application / content server 1420 .

[0218] Fig.15 Schematically illustrated is a wireless network 1500 according to various embodiments. The wireless network 1500 may include a UE 1502 in wireless communication with an AN 1524. The UE 1502 and AN 1524 may be similar to and substantially interchangeable with like-named components described elsewhere herein.

[0219] UE 1502 may be communicatively coupled to AN 1524 via connection 1546. Connection 1546 is shown as an air interface that enables the communicatively coupled and may be consistent with a cellular communication protocol, such as a 5G NR protocol or an LTE protocol operating at mmWave or sub-6 GHz frequencies.

[0220] UE 1502 may include a host platform 1504 coupled to a modem platform 1508. Host platform 1504 may include application processing circuitry 1506, which may be coupled to protocol processing circuitry 1510 of modem platform 1508. Application processing circuitry 1506 may run various applications that generate / aggregate application data for UE 1502. Application processing circuitry 1506 may also implement one or more layer operations for sending application data to or receiving application data from a data network. These layer operations may include transport (e.g., UDP) operations and Internet (e.g., IP) operations.

[0221] The protocol processing circuit 1510 may implement one or more layer operations for facilitating sending or receiving data over the connection 1546. The layer operations implemented by the protocol processing circuit 1510 may include, for example, MAC, RLC, PDCP, RRC, and NAS operations.

[0222] The modem platform 1508 may also include digital baseband circuitry 1512, which may implement one or more layer operations that are "below" the layer operations performed by the protocol processing circuitry 1510 in the network protocol stack. These operations may include, for example, PHY operations that include one or more of the following: HARQ-ACK functionality, scrambling / descrambling, encoding / decoding, layer mapping / demapping, modulation symbol mapping, received symbol / bit metric determination, multi-antenna port precoding / decoding (which may include one or more of space-time, space-frequency, or spatial coding), reference signal generation / detection, preamble sequence generation and / or decoding, synchronization sequence generation / detection, control channel signal blind decoding, and other related functions.

[0223] The modem platform 1508 may also include a transmit circuit 1514, a receive circuit 1516, an RF circuit 1518, and an RF front end (RFFE) 1520, which may include or be connected to one or more antenna panels 1522. In brief, the transmit circuit 1514 may include a digital-to-analog converter, a mixer, an intermediate frequency (IF) component, etc.; the receive circuit 1516 may include an analog-to-digital converter, a mixer, an IF component, etc.; the RF circuit 1518 may include a low noise amplifier, a power amplifier, a power tracking component, etc.; the RFFE 1520 may include a filter (e.g., a surface / bulk acoustic wave filter), a switch, an antenna tuner, a beamforming component (e.g., a phased array antenna component), etc. The selection and arrangement of the components of the transmit circuit 1514, the receive circuit 1516, the RF circuit 1518, the RFFE 1520, and the antenna panel 1522 (collectively referred to as "transmit / receive components") may be specific to the details of a particular implementation (e.g., whether the communication is TDM or FDM, using millimeter waves or using frequencies below 6 gHz, etc.). In some embodiments, the transmit / receive components may be arranged in multiple parallel transmit / receive chains, may be provided in the same or different chips / modules, and so on.

[0224] In some embodiments, the protocol processing circuit 1510 may include one or more control circuit instances (not shown) for providing control functionality for the transmit / receive components.

[0225] UE reception may be established through antenna panel 1522, RFFE 1520, RF circuitry 1518, receive circuitry 1516, digital baseband circuitry 1512, and protocol processing circuitry 1510. In some embodiments, antenna panel 1522 may receive transmissions from AN 1524 via receive-beamformed signals received by multiple antennas / antenna elements of one or more antenna panels 1522.

[0226] UE transmission can be established through protocol processing circuit 1510, digital baseband circuit 1512, transmit circuit 1514, RF circuit 1518, RFFE 1520, and antenna panel 1522. In some embodiments, the transmit component of UE 1524 can apply a spatial filter to the data to be transmitted to form a transmit beam transmitted by the antenna elements of antenna panel 1522.

[0227] Similar to UE 1502, AN 1524 may include a host platform 1526 coupled to a modem platform 1530. Host platform 1526 may include application processing circuitry 1528 coupled to protocol processing circuitry 1532 of modem platform 1530. The modem platform may also include digital baseband circuitry 1534, transmit circuitry 1536, receive circuitry 1538, RF circuitry 1540, RFFE circuitry 1542, and antenna panel 1544. The components of AN 1524 may be similar to and substantially interchangeable with the components of the same name of UE 1502. In addition to performing data transmission / reception as described above, the components of host platform 1504 may also perform various logical functions, including, for example, RNC functions such as radio bearer management, uplink and downlink dynamic radio resource management, and data packet scheduling.

[0228] Fig.16 is a block diagram illustrating components capable of reading instructions from a machine-readable or computer-readable medium (e.g., a non-transitory machine-readable storage medium) and performing any one or more of the methods discussed herein, according to some example embodiments. Specifically, Fig.16 A diagram of hardware resources 1630 is shown, including one or more processors (or processor cores) 1610, one or more memory / storage devices 1622, and one or more communication resources 1626, each of which may be communicatively coupled via a bus 1620 or other interface circuitry. For embodiments utilizing node virtualization (e.g., NFV), a hypervisor 1602 may be executed to provide an execution environment utilizing hardware resources 1630 for one or more network slices / subslices.

[0229] Processor 1610 may include, for example, processor 1612 and processor 1614. Processor 1610 may be, for example, a central processing unit (CPU), a reduced instruction set computing (RISC) processor, a complex instruction set computing (CISC) processor, a graphics processing unit (GPU), a DSP such as a baseband processor, an ASIC, an FPGA, a radio frequency integrated circuit (RFIC), another processor (including those discussed herein), or any suitable combination thereof.

[0230] The memory / storage device 1622 may include main memory, disk storage, or any suitable combination thereof. The memory / storage device 1622 may include, but is not limited to, any type of volatile, nonvolatile, or semi-volatile memory, such as dynamic random access memory (DRAM), static random access memory (SRAM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), flash memory, solid-state storage, etc.

[0231] The communication resources 1626 may include interconnect or network interface controllers, components, or other suitable devices for communicating with one or more peripheral devices 1604 or one or more databases 1606 or other network elements via the network 1608. For example, the communication resources 1626 may include wired communication components (e.g., for coupling via USB, Ethernet, etc.), cellular communication components, NFC components, (or low power consumption ) components, components, and other communication components.

[0232] The instructions 106, 1618, 1624, 1628, 1632 may include software, programs, applications, applet, applications, or other executable code for causing at least any processor 1610 to perform any one or more of the methods discussed herein. The instructions 106, 1618, 1624, 1628, 1632 may reside in whole or in part in at least one of the processor 1610 (e.g., in a cache memory of the processor), the memory / storage device 1622, or any suitable combination thereof. In addition, any portion of the instructions 106, 1618, 1624, 1628, 1632 may be transferred to the hardware resources 1630 from any combination of the peripheral device 1604 or the database 1606. Therefore, the memory of the processor 1610, the memory / storage device 1622, the peripheral device 1604, and the database 1606 are examples of computer-readable and machine-readable media.

[0233] For one or more embodiments, at least one of the components described in one or more of the preceding figures may be configured to perform one or more operations, techniques, processes, and / or methods described in the following example section. For example, the baseband circuitry as described above in conjunction with one or more of the preceding figures may be configured to operate according to one or more of the examples listed below. For another example, circuitry associated with a UE, a base station, a network element, etc., as described above in conjunction with one or more of the preceding figures, may be configured to operate according to one or more of the examples described in the following example section.

[0234] Fig.17 A computer-readable storage medium 1700 is shown. The computer-readable storage medium 1700 may include any non-transitory computer-readable storage medium 1700 or machine-readable storage medium 1700, such as an optical, magnetic, or semiconductor storage medium. In various embodiments, the computer-readable storage medium 1700 may include an article of manufacture. In some embodiments, the computer-readable storage medium 1700 may store computer-executable instructions 1702 that a circuit may execute. For example, the computer-executable instructions 1702 may include computer-executable instructions 1702 for implementing the operations described with respect to the logic flow 900, the logic flow 1000, the logic flow 1100, the logic flow 1200, or the message flow 1300. Examples of computer-readable storage media 1700 or machine-readable storage media 1700 may include any tangible medium capable of storing electronic data, including volatile or non-volatile memory, removable or non-removable memory, erasable or non-erasable memory, writable or rewritable memory, and the like. Examples of computer-executable instructions 1702 may include any suitable type of code, such as source code, compiled code, interpreted code, executable code, static code, dynamic code, object-oriented code, visual code, and the like.

[0235] First set of examples

[0236] Example 1 may include a wireless communication method for a fifth generation (5G) or new radio (NR) system: a UE configures a priority value for sending or receiving a sidelink positioning reference signal (SL PRS); and the UE determines, based on the configured priority value, whether the SL PRS sending or receiving has a higher priority than other sending or receiving.

[0237] Example 2 may include the method of Example 1 or some other examples in this document, wherein, when one or more symbols of SL PRS transmission or reception overlap with a sidelink transmission or reception or uplink transmission with a higher priority in the time domain, if the UE cannot simultaneously perform SL PRS transmission / reception and sidelink transmission / reception or uplink transmission in one or two carriers, the UE may cancel or discard one or more symbols of SL PRS transmission or reception accordingly; wherein the UE may send or receive SL PRS in non-overlapping symbols.

[0238] Example 3 may include the method of Example 1 or some other examples in this document, wherein, when one or more symbols of SL PRS transmission or reception overlap with a sidelink transmission or reception or uplink transmission with a higher priority in the time domain, if the UE cannot simultaneously perform SL PRS transmission / reception and sidelink transmission / reception or uplink transmission in one or two carriers, the UE may cancel or discard the entire SL PRS transmission or reception.

[0239] Example 4 may include the method of Example 1 or some other examples in this document, wherein PRACH, Msg3 PUSCH initial transmission and retransmission, MsgA PUSCH, PUCCH carrying HARQ-ACK information sent by corresponding MsgB PDSCH, or Msg4 has a higher priority than SL PRS transmission or reception.

[0240] Example 5 may include the method of Example 1 or some other examples herein, wherein a measurement gap may be configured for SL PRS reception.

[0241] Example 6 may include the method of Example 1 or some other examples herein, wherein the measurement gap may be configured according to a system frame duration, a subframe duration, or a physical time slot.

[0242] Example 7 may include the method of Example 1 or some other examples herein, wherein the measurement gap may be configured according to a logical index of a time slot configured for the SL PRS resource pool.

[0243] Example 8 may include the method of Example 1 or some other examples herein, wherein the measurement gap may be activated or deactivated via a medium access control-control element (MAC-CE) or sidelink control information (SCI) format.

[0244] Example 9 may include the method of Example 1 or some other examples herein, wherein the SL PRS processing window for SL PRS reception may be provided to the UE via higher layer (pre) configuration and / or dynamic indication.

[0245] Example 10 may include the method of Example 1 or some other examples herein, wherein the SL PRS processing window may be configured according to a subframe index or a physical slot index.

[0246] Example 11 may include the method of Example 1 or some other examples herein, wherein, in a case where a dedicated SL PRS resource pool is configured for SL PRS transmission and measurement, the SL PRS processing window may be configured according to a logical index of a time slot configured for the SL PRS resource pool.

[0247] Example 12 may include the method of Example 1 or some other examples in this document, wherein the SL PRS processing window can be activated or deactivated via a medium access control-control element (MAC-CE) or sidelink control information (SCI) format.

[0248] Example 13 may include the method of Example 1 or some other examples herein, wherein, when the UE receives the SL PRS within the SL PRS processing window and when the UE determines that the SL PRS has a higher priority than a sidelink physical channel / signal or an uplink physical channel / signal, the UE is expected to measure the SL PRS, and the UE is not expected to send or receive other sidelink physical channels / signals and / or send uplink physical channels or signals.

[0249] Example 14 may be the method of Example 1 or some other examples herein, wherein no priority level is defined for SL PRS transmission or reception.

[0250] Example 15 may include a method of Example 1 or some other examples herein, wherein, for priority sorting between SL PRS transmission / reception and UL transmission other than PRACH, or PUSCH and its retransmission scheduled by UL grant in RAR, or PUSCH and its retransmission corresponding to type 2 random access procedure, or PUCCH with sidelink HARQ-ACK information report, if the UL transmission is for PUCCH or PUSCH with priority index 1, the UL transmission has a higher priority than SL PRS transmission or reception.

[0251] Example 16 may include a method of Example 1 or some other examples in the present document, wherein no priority level is defined for SL PRS transmission or reception; wherein, for the priority ranking between SL PRS transmission / reception and UL transmission other than PRACH, or PUSCH and its retransmission scheduled by UL grant in RAR, or PUSCH and its retransmission corresponding to type 2 random access procedure, or PUCCH with sidelink HARQ-ACK information report, if the UL transmission is for PUCCH or PUSCH with priority index 0, the UL transmission has a higher priority than SL PRS transmission or reception.

[0252] Example 17 may include the method of Example 1 or some other examples in the present document, wherein no priority level is defined for SL PRS transmission or reception; wherein, for priority sorting between SL PRS transmission / reception and PUCCH or PUSCH transmission with sidelink HARQ-ACK information report, if the priority value of the PUCCH transmission is less than a threshold, the PUCCH transmission has a higher priority than the SL PRS transmission or reception, and the threshold may be configured or pre-configured by a higher layer.

[0253] Example 18 may include the method of Example 1 or some other examples herein, wherein PUCCH or PUSCH transmission with sidelink HARQ-ACK information reporting always has higher priority than SL PRS transmission or reception.

[0254] Example 19 may include the method of Example 1 or some other examples in this document, wherein, for priority sorting between SL PRS transmission / reception and SL communication including PSSCH / PSCCH, S-SS / PSBCH blocks, and PSFCH, or SL reception including S-SS / PSBCH blocks and PSFCH, if the priority value of SL transmission or reception of SL communication is less than a threshold, the SL transmission or reception of SL communication has a higher priority than SL PRS transmission or reception, and the threshold may be configured or pre-configured by a higher layer.

[0255] Example 20 may include a method of Example 1 or some other examples herein, wherein one or more priorities may be defined for the transmission / reception of a SL PRS for sidelink positioning; wherein one of the fields may be included in a first or second stage SCI format to indicate a priority value for the SL PRS transmission.

[0256] Example 21 may include a method of Example 1 or some other examples herein, wherein, when one or more priority values ​​are defined for SL PRS transmission and / or reception, for priority sorting between SL PRS transmission / reception and UL transmissions other than PRACH, or PUSCH and its retransmissions scheduled by UL grant in RAR, or PUSCH and its retransmissions corresponding to type 2 random access process, or PUCCH with sidelink HARQ-ACK information report, if the UL transmission is for PUCCH or PUSCH with priority index 1, then when the priority value of SL PRS transmission or reception is less than a priority threshold, the SL PRS transmission or reception has a higher priority than the UL transmission, and the priority threshold may be configured or preconfigured by a higher layer.

[0257] Example 22 may include a method of Example 1 or some other examples herein, wherein, when one or more priority values ​​are defined for SL PRS transmission and / or reception, for priority sorting between SL PRS transmission / reception and UL transmissions other than PRACH, or PUSCH and its retransmissions scheduled by UL grant in RAR, or PUSCH and its retransmissions corresponding to type 2 random access process, or PUCCH with sidelink HARQ-ACK information report, if the UL transmission is for PUCCH or PUSCH with priority index 0, then when the priority value of SL PRS transmission or reception is less than a priority threshold, the SL PRS transmission or reception has a higher priority than the UL transmission, and the priority threshold may be configured or preconfigured by a higher layer.

[0258] Example 23 may include a method of Example 1 or some other examples herein, wherein, when one or more priority values ​​are defined for SL PRS transmission and / or reception, for priority sorting between SL PRS transmission / reception and PUCCH or PUSCH transmission with sidelink HARQ-ACK information reporting, if the priority value of the PUCCH or PUSCH transmission is less than the priority value of the SLPRS transmission or reception, the PUCCH or PUSCH transmission has a higher priority than the SL PRS transmission or reception.

[0259] Example 24 may include the method of Example 1 or some other examples in the present document, wherein, when one or more priority values ​​are defined for SL PRS transmission and / or reception, for the priority sorting between SL PRS transmission / reception and SL transmission of SL communication including PSSCH / PSCCH, S-SS / PSBCH blocks, and PSFCH, or SL reception including S-SS / PSBCH blocks and PSFCH, if the priority value of SL transmission or reception of SL communication is less than the priority value of SL PRS transmission or reception, the SL transmission or reception of SL communication has a higher priority than the SL PRS transmission or reception.

[0260] Example 25 may include the method of Example 1 or some other examples herein, wherein, in the case of a shared resource pool for SL communication and SL positioning, the value of the priority field indicated in the first stage SCI can be determined based on a function of the priority value of SL communication and the priority value of SL PRS.

[0261] Example 26 may include the method of Example 1 or some other examples herein, wherein the value of the priority field indicated in the first stage SCI may correspond to a higher one of a priority value of the SL communication and a priority value of the SL PRS.

[0262] Example 27 may include a method of Example 1 or some other examples herein, wherein, when no SL PRS is scheduled in the shared resource pool and the first stage SCI indicates a new second stage SCI format associated with the SL PRS scheduling, the value of the priority field indicated in the first stage SCI may correspond to the priority value of the SL communication.

[0263] Example 28 may include the method of Example 1 or some other examples in this document, wherein, when SL PRS is scheduled in the shared resource pool but PSSCH carrying SL-SCH is not scheduled, the value of the priority field indicated in the first stage SCI may correspond to the priority value of the SL PRS.

[0264] Example 29 may include the method of Example 1 or some other examples herein, wherein when no SL PRS is scheduled in the shared resource pool, a priority field may still be present in the second stage SCI.

[0265] Example 30 may include the method of Example 1 or some other examples herein, wherein, for a dedicated resource pool, when only PSCCH and SL PRS are included, a priority field may be included in a single SCI format, wherein the value of the priority field may correspond to the priority value of the SL PRS.

[0266] Example 31 may include a wireless communication method, comprising: determining that one or more symbols sent or received by a sidelink positioning reference signal (SL PRS) overlap with a sidelink transmission or reception or uplink transmission of a user equipment (UE); determining, based on a priority rule, that one or more symbols sent or received by the SL PRS, the sidelink transmission or reception, or the uplink transmission is a priority communication; communicating the priority communication with the UE; and discarding at least one of the one or more symbols sent or received by the SL PRS, the sidelink transmission or reception, or the uplink transmission that is not a priority communication.

[0267] Example 32 may include the method of Example 31 or some other examples in this document, wherein the SL PRS transmission partially overlaps with the uplink transmission; discarding one or more symbols of the SL PRS transmission or reception, the sidelink transmission or reception, or at least one of the uplink transmissions that is not a priority communication includes: discarding only the portion of the SL PRS transmission that overlaps with the uplink transmission.

[0268] Example 33 may include the method of Example 31 or some other examples in this document, wherein the SL PRS transmission partially overlaps with the uplink transmission; discarding one or more symbols of the SL PRS transmission or reception, the sidelink transmission or reception, or at least one of the uplink transmissions that is not a priority communication includes: discarding all SL PRS transmissions.

[0269] Example 34 may include the method of Example 32 or Example 33, wherein the uplink transmission is at least one of a physical uplink shared channel (PUSCH) transmission or a physical uplink control channel (PUCCH) transmission.

[0270] Example 35 may include a method of Example 31 or some other examples herein, wherein the priority communication is an SLPRS transmission, one or more symbols of an SL PRS transmission or reception, a sidelink transmission or reception, or at least one of an uplink transmission that is not a priority communication is an uplink transmission, and wherein the method further includes: measuring the SL PRS transmission.

[0271] Example 36 may include the method of Example 31 or some other examples herein, wherein, for a shared resource pool for SL communication and SL positioning, the value of the priority field in the first stage SCI is determined based on a function of a first priority value of SL communication and a second priority value of SL PRS.

[0272] Example 37 may include the method of Example 31 or some other examples herein, wherein the value of the priority field corresponds to a higher of the first priority value and the second priority value.

[0273] Second set of examples

[0274] In one example, a method for managing communications for a user equipment (UE) includes detecting a set of overlapping symbols between a sidelink (SL) positioning reference signal (PRS) (SL PRS) and a message in a time slot for a frame in a time domain of a new radio (NR) system, extracting priority information of the SL PRS from a data storage device, and determining a scheduling arrangement for sending or receiving the SL PRS and the message based on the priority information.

[0275] The method may also include, wherein the message includes data for SL transmission or uplink (UL) transmission.

[0276] The method may also include determining that the SL PRS has a lower priority and the message has a higher priority, scheduling the message with the higher priority for transmission or reception, discarding a set of overlapping symbols of the SL PRS with the lower priority, and scheduling a set of non-overlapping symbols of the SL PRS for transmission or reception.

[0277] The method may further include determining that the SL PRS has a lower priority and the message has a higher priority, scheduling the message with the higher priority for transmission or reception, and discarding all symbols of the SL PRS with the lower priority.

[0278] The method may further include determining that the SL PRS has a higher priority and the message has a lower priority, scheduling the SL PRS with the higher priority for transmission or reception, and discarding all symbols of the message with the lower priority.

[0279] The method may also include determining that the SL PRS has no priority level, and scheduling the message for transmission or reception by default.

[0280] The method may also include: receiving a first phase (1) from a physical sidelink control channel (PSCCH) st Sidelink Control Information (SCI) in the SCI format or from the physical sidelink shared channel (PSSCH) with the second stage (2 nd Stage) SCI format sidelink control information (SCI) decoding SL PRS sidelink scheduling information, where 1 st Stage SCI format or 2 nd An information field of the phase SCI format indicates priority information of the SL PRS, the priority information is extracted from the information field, and the priority information is stored in the data storage device.

[0281] The method may also include: receiving a first phase (1) from a physical sidelink control channel (PSCCH) st The sidelink control information (SCI) of SCI format 1-B in the first stage decodes the sidelink scheduling information of SL PRS, and SCI format 1-B includes information fields for priority, source identifier (ID), destination ID, broadcast type indicator, or resource reservation period, where, if a higher layer parameter sl-PRSResourceReservePeriodList is configured, Nrsv-period is the number of entries in the higher layer parameter sl-PRSResourceReservePeriodList, otherwise Nrsv-period is 0 bits.

[0282] The method may also include: receiving a second phase (2 nd The sidelink control information (SCI) of the sidelink control information (SCI) of the SCI format 2-D of the stage) decodes the sidelink scheduling information of the SL PRS, and the SCI format 2-D includes an information field for a hybrid automatic repeat request (HARQ) process number including 4 bits, a new data indicator including 1 bit, a redundant version including 2 bits, a source identifier (ID) including 8 bits, a destination ID including 16 bits, or a HARQ feedback enable / disable indicator including 1 bit. Other technical features can be easily derived by those skilled in the art from the following drawings, descriptions, and claims.

[0283] In one aspect, an apparatus for a user equipment (UE) includes: a memory interface for sending or receiving priority information for transmission or reception of a sidelink positioning reference signal (SL PRS) in a new radio (NR) system to or from a data storage device. The apparatus also includes a processor circuit communicatively coupled to the memory interface, the processor circuit for: detecting a set of overlapping symbols between a SL PRS and a message in a time slot for a frame in a time domain of the NR system, extracting priority information of the SL PRS from the data storage device, and determining a scheduling arrangement for transmission or reception of the SL PRS and the message based on the priority information of the SL PRS.

[0284] The apparatus may also include a processor circuit for determining that the SL PRS has a lower priority and the message has a higher priority, scheduling the message with the higher priority for transmission or reception, discarding a set of overlapping symbols of the SL PRS with the lower priority, and scheduling a set of non-overlapping symbols of the SL PRS for transmission or reception.

[0285] The apparatus may also include a processor circuit for determining that the SL PRS has a lower priority and the message has a higher priority, scheduling the message with the higher priority for transmission or reception, and discarding all symbols of the SLPRS with the lower priority.

[0286] The apparatus may further include a processor circuit for determining that the SL PRS has a higher priority and the message has a lower priority, scheduling the SL PRS with the higher priority for transmission or reception, and discarding all symbols of the message with the lower priority.

[0287] The apparatus may also include a processor circuit for determining that the SL PRS does not have a priority level and scheduling the message for transmission or reception by default.

[0288] The apparatus may also include a processor circuit configured to: receive a first-stage (1 st The sidelink control information (SCI) of SCI format 1-B in the first stage decodes the sidelink scheduling information of SL PRS, and SCI format 1-B includes information fields for priority, source identifier (ID), destination ID, broadcast type indicator, or resource reservation period, where, if a higher layer parameter sl-PRSResourceReservePeriodList is configured, Nrsv-period is the number of entries in the higher layer parameter sl-PRSResourceReservePeriodList, otherwise Nrsv-period is 0 bits.

[0289] The apparatus may also include a processor circuit configured to: receive a second phase (2 nd The sidelink control information (SCI) of the sidelink control information (SCI) of the SCI format 2-D of the stage) decodes the sidelink scheduling information of the SL PRS, and the SCI format 2-D includes an information field for a hybrid automatic repeat request (HARQ) process number including 4 bits, a new data indicator including 1 bit, a redundant version including 2 bits, a source identifier (ID) including 8 bits, a destination ID including 16 bits, or a HARQ feedback enable / disable indicator including 1 bit. Other technical features can be easily derived by those skilled in the art from the following drawings, descriptions, and claims.

[0290] In one aspect, a non-transitory computer-readable storage medium includes instructions that, when executed by a computer, cause the computer to: detect a set of overlapping symbols between a sidelink (SL) positioning reference signal (PRS) (SL PRS) and a message in a time slot for a frame in a time domain of a new radio (NR) system, extract priority information of the SL PRS from a data storage device, and determine a scheduling arrangement for sending or receiving the SL PRS and the message based on the priority information.

[0291] The computer-readable storage medium may also include instructions for the following operations: determining that the SL PRS has a lower priority and the message has a higher priority, scheduling the message with the higher priority for transmission or reception, discarding a set of overlapping symbols of the SL PRS with the lower priority, and scheduling a set of non-overlapping symbols of the SL PRS for transmission or reception.

[0292] The computer-readable storage medium may also include instructions for determining that the SL PRS has a lower priority and the message has a higher priority, scheduling the message with the higher priority for transmission or reception, and discarding all symbols of the SL PRS with the lower priority.

[0293] The computer-readable storage medium may also include instructions for determining that the SL PRS has a higher priority and the message has a lower priority, scheduling the SL PRS with the higher priority for transmission or reception, and discarding all symbols of the message with the lower priority.

[0294] The computer-readable storage medium may also include instructions for the following operations: from a physical sidelink control channel (PSCCH) carried by the first stage (1 st The sidelink control information (SCI) of SCI format 1-B in the first stage decodes the sidelink scheduling information of SLPRS, and SCI format 1-B includes information fields for priority, source identifier (ID), destination ID, broadcast type indicator, or resource reservation period, where if a higher layer parameter sl-PRSResourceReservePeriodList is configured, Nrsv-period is the number of entries in the higher layer parameter sl-PRSResourceReservePeriodList, otherwise Nrsv-period is 0 bits.

[0295] The computer-readable storage medium may also include instructions for the following operations: from a second stage (2 ndThe sidelink control information (SCI) of the SCI format 2-D of the stage) decodes the sidelink scheduling information of the SLPRS, and the SCI format 2-D includes an information field for a hybrid automatic repeat request (HARQ) process number including 4 bits, a new data indicator including 1 bit, a redundant version including 2 bits, a source identifier (ID) including 8 bits, a destination ID including 16 bits, or a HARQ feedback enable / disable indicator including 1 bit. Other technical features can be easily derived by those skilled in the art from the following drawings, descriptions, and claims.

[0296] the term

[0297] For the purposes of this document, the following terms and definitions apply to the examples and embodiments discussed herein.

[0298] The term "circuit" as used herein refers to a hardware component configured to provide the described functions, is part of these hardware components, or includes these hardware components, such as electronic circuits, logic circuits, processors (shared, dedicated, or group processors) and / or memories (shared, dedicated, or group memories), application specific integrated circuits (ASICs), field programmable devices (FPDs) (e.g., field programmable gate arrays (FPGAs), programmable logic devices (PLDs), complex PLDs (CPLDs), high capacity PLDs (HCPLDs), structured ASICs, or programmable SoCs), digital signal processors (DSPs), etc. In some embodiments, the circuit can execute one or more software or firmware programs to provide at least some of the described functions. The term "circuit" can also refer to a combination of one or more hardware elements (or a combination of circuits used in electrical or electronic systems) and program code for performing the functions of the program code. In these embodiments, the combination of hardware elements and program code can be referred to as a specific type of circuit.

[0299] The term "processor circuit" used herein refers to a circuit that can automatically perform a series of arithmetic or logical operations or record, store, and / or transmit digital data in sequence, is part of such a circuit, or includes such a circuit. The processing circuit may include one or more processing cores for executing instructions and one or more memory structures for storing program and data information. The term "processor circuit" may refer to one or more application processors, one or more baseband processors, a physical central processing unit (CPU), a single-core processor, a dual-core processor, a triple-core processor, a quad-core processor, and / or any other device capable of executing or otherwise operating computer executable instructions (such as program code, software module, and / or functional process). The processing circuit may include more hardware accelerators, which may be microprocessors, programmable processing devices, etc. One or more hardware accelerators may include, for example, computer vision (CV) and / or deep learning (DL) accelerators. The terms "application circuit" and / or "baseband circuit" may be considered synonymous with "processor circuit" and may also be referred to as "processor circuit".

[0300] As used herein, the term "interface circuit" refers to a circuit that is capable of exchanging information between two or more components or devices, is part of such a circuit, or includes such a circuit. The term "interface circuit" may refer to one or more hardware interfaces, such as a bus, an I / O interface, a peripheral component interface, a network interface card, etc.

[0301] The term "user equipment" or "UE" as used herein refers to a device with radio communication capabilities and can describe a remote user of network resources in a communication network. The term "user equipment" or "UE" can be considered as a synonym for a client, a mobile device, a mobile device, a mobile terminal, a user terminal, a mobile unit, a mobile station, a mobile user, a subscriber, a user, a remote station, an access agent, a user agent, a receiver, a radio equipment, a reconfigurable radio equipment, a reconfigurable mobile device, etc., and can also be referred to as these terms. In addition, the term "user equipment" or "UE" can include any type of wireless / wired device or any computing device that includes a wireless communication interface.

[0302] The term "network element" as used herein refers to a physical or virtualized device and / or infrastructure used to provide wired or wireless communication network services. The term "network element" may be considered a synonym for networked computers, networked hardware, network equipment, network nodes, routers, switches, hubs, bridges, radio network controllers, RAN equipment, RAN nodes, gateways, servers, virtual VNFs, NFVIs, etc., and may also be referred to as such terms.

[0303] As used herein, the term "computer system" refers to any type of interconnected electronic devices, computer devices, or components thereof. In addition, the terms "computer system" and / or "system" may refer to various components of a computer that are communicatively coupled to each other. In addition, the terms "computer system" and / or "system" may refer to multiple computer devices and / or multiple computing systems that are communicatively coupled to each other and configured to share computing and / or network resources.

[0304] As used herein, the terms "appliance", "computer appliance", etc. refer to a computer device or computer system with program code (e.g., software or firmware) specifically designed to provide specific computing resources. A "virtual appliance" is a virtual machine image implemented by a device equipped with a hypervisor that virtualizes or emulates a computer appliance or is otherwise dedicated to providing specific computing resources.

[0305] The term "resource" as used herein refers to a physical or virtual device, a physical or virtual component in a computing environment, and / or a physical or virtual component within a specific device, such as a computer device, a mechanical device, a memory space, a processor / CPU time, a processor / CPU usage, a processor and accelerator load, a hardware time or usage, power, input / output operations, a port or network socket, a channel / link allocation, throughput, memory usage, a storage device, a network, a database and an application, a workload unit, etc. "Hardware resources" may refer to computing, storage, and / or network resources provided by (one or more) physical hardware elements. "Virtualized resources" may refer to computing, storage, and / or network resources provided by a virtualized infrastructure to an application, device, system, etc. The term "network resources" or "communication resources" may refer to resources that a computer device / system can access through a communication network. The term "system resources" may refer to any type of shared entity that provides a service, and may include computing and / or network resources. System resources may be considered to be a set of related functions, network data objects, or services that can be accessed through a server, wherein these system resources reside on a single host or multiple hosts and can be clearly identified.

[0306] The term "channel" as used herein refers to any tangible or intangible transmission medium for communicating data or data streams. The term "channel" may be used interchangeably with "communication channel", "data communication channel", "transmission channel", "data transmission channel", "access channel", "data access channel", "link", "data link", "carrier", "radio frequency carrier", and / or any other similar terms representing a path or medium for communicating data. In addition, the term "link" as used herein refers to a connection between two devices over a RAT for sending and receiving information.

[0307] As used herein, the terms "instance", "instantiation" and the like refer to the creation of an instance. "Instance" also refers to a specific occurrence of an object, such as might occur during the execution of program code.

[0308] The terms "coupled", "communicative coupling" and their derivatives are used herein. The term "coupled" may mean that two or more elements are in direct physical or electrical contact with each other, may mean that two or more elements are in indirect contact with each other but still cooperate or interact with each other, and / or may mean that one or more other elements are coupled or connected between these elements (referred to as being coupled to each other). The term "directly coupled" may mean that two or more elements are in direct contact with each other. The term "communicative coupling" may mean that two or more elements may be in contact with each other by means of communication, including by wired or other interconnected connections, by wireless communication channels or links, etc.

[0309] The term "information element" refers to a structured element that contains one or more fields. The term "field" refers to the individual contents of an information element or a data element that contains content.

[0310] The term "SMTC" refers to the SSB-based measurement timing configuration configured by SSB-MeasurementTimingConfiguration.

[0311] The term "SSB" refers to SS / PBCH block.

[0312] The term "primary cell" refers to an MCG cell operating on a primary frequency, in which the UE performs an initial connection establishment procedure or initiates a connection re-establishment procedure.

[0313] The term "primary SCG cell" refers to an SCG cell in which a UE performs random access when performing reconfiguration for DC operation through a synchronization procedure.

[0314] The term "secondary cell" refers to a cell that provides additional radio resources over a special cell for a UE configured with CA.

[0315] The term "secondary cell group" refers to a subset of serving cells including a PSCell and zero or more secondary cells for a DC-configured UE.

[0316] The term "serving cell" refers to a primary cell for a UE in RRC_CONNECTED state without CA / DC configured, and there is only one serving cell including the primary cell.

[0317] The term "serving cell" or "serving cells" refers to a group of cells including a special cell and all secondary cells for a UE configured with CA in the RRC_CONNECTED state.

[0318] The term "special cell" refers to a PCell of an MCG or a PSCell of an SCG for DC operation; otherwise, it refers to a Pcell.

Claims

1. An apparatus for a user equipment (UE), comprising: A memory interface for sending or receiving priority information for transmission or reception of a sidelink positioning reference signal (SL PRS) in a new radio (NR) system to or from a data storage device; and a processor circuit communicatively coupled to the memory interface, the processor circuit configured to: Detecting a set of overlapping symbols between a SL PRS and a message in a time slot for a frame in a time domain of the NR system; extracting priority information of the SL PRS from a data storage device; as well as A schedule for transmission or reception of the SL PRS and the message is determined based on the priority information of the SL PRS.

2. The device according to claim 1, wherein: The processor circuit is configured to: determining that the SL PRS has a lower priority and the message has a higher priority; scheduling the message having a higher priority for transmission or reception; discarding a set of overlapping symbols of the SL PRS having a lower priority; as well as A set of non-overlapping symbols of the SL PRS are scheduled for transmission or reception.

3. The device according to claim 1, wherein: The processor circuit is configured to: determining that the SL PRS has a lower priority and the message has a higher priority; scheduling the message having a higher priority for transmission or reception; and All symbols of the SL PRS having a lower priority are discarded.

4. The device according to claim 1, wherein: The processor circuit is configured to: determining that the SL PRS has a higher priority and the message has a lower priority; scheduling the SL PRS having a higher priority for transmission or reception; and All symbols of said message having a lower priority are discarded.

5. The device according to any one of claims 1 to 4, wherein: The processor circuit is used to: receive a first-stage (1 st The sidelink scheduling information of the SL PRS is decoded in the sidelink control information (SCI) format 1-B, wherein the SCI format 1-B includes a priority, a source identifier (ID), a destination ID, a broadcast type indicator, or a resource reservation period [log2N rsυ-period ] information field, where, if the higher layer parameter sl-PRSResourceReservePeriodList is configured, Nrsv-period is the number of entries in the higher layer parameter sl-PRSResourceReservePeriodList, otherwise Nrsv-period is 0 bits.

6. The device according to any one of claims 1 to 4, wherein: The processor circuit is used to: receive a second phase (2 nd The SCI format 2-D of the sidelink control information (SCI) format decodes the sidelink scheduling information of the SL PRS in the stage, and the SCI format 2-D includes an information field for a hybrid automatic repeat request (HARQ) process number including 4 bits, a new data indicator including 1 bit, a redundant version including 2 bits, a source identifier (ID) including 8 bits, a destination ID including 16 bits, or a HARQ feedback enable / disable indicator including 1 bit.

7. A computer-readable storage medium comprising instructions which, when executed by a computer, cause the computer to: detecting a set of overlapping symbols between a sidelink (SL) positioning reference signal (PRS) (SL PRS) and a message in a time slot for a frame in a time domain of a new radio (NR) system; extracting priority information of the SL PRS from a data storage device; and A schedule for transmission or reception of the SL PRS and the message is determined based on the priority information.

8. The computer-readable storage medium of claim 7, comprising instructions for: determining that the SL PRS has a lower priority and the message has a higher priority; scheduling the message having a higher priority for transmission or reception; discarding a set of overlapping symbols of the SL PRS having a lower priority; and A set of non-overlapping symbols of the SL PRS are scheduled for transmission or reception.

9. The computer-readable storage medium of claim 7, comprising instructions for: determining that the SL PRS has a lower priority and the message has a higher priority; scheduling the message having a higher priority for transmission or reception; and All symbols of the SL PRS having a lower priority are discarded.

10. The computer-readable storage medium of claim 7, comprising instructions for: determining that the SL PRS has a higher priority and the message has a lower priority; scheduling the SL PRS having a higher priority for transmission or reception; and All symbols of said message having a lower priority are discarded.

11. The computer-readable storage medium according to any one of claims 7 to 10, comprising instructions for the following operations: st The sidelink scheduling information of the SL PRS is decoded in the sidelink control information (SCI) format 1-B, wherein the SCI format 1-B includes a priority, a source identifier (ID), a destination ID, a broadcast type indicator, or a resource reservation period [log2N rsυ-period ] information field, where If the higher layer parameter sl-PRSResourceReservePeriodList is configured, Nrsv-period is the number of entries in the higher layer parameter sl-PRSResourceReservePeriodList, otherwise Nrsv-period is 0 bits.

12. The computer-readable storage medium according to any one of claims 7 to 10, comprising instructions for the following operations: from a second phase (2 nd The SCI format 2-D of the sidelink control information (SCI) format decodes the sidelink scheduling information of the SL PRS in the stage, and the SCI format 2-D includes an information field for a hybrid automatic repeat request (HARQ) process number including 4 bits, a new data indicator including 1 bit, a redundant version including 2 bits, a source identifier (ID) including 8 bits, a destination ID including 16 bits, or a HARQ feedback enable / disable indicator including 1 bit.

13. A method for managing communications for a user equipment (UE), comprising: detecting a set of overlapping symbols between a sidelink (SL) positioning reference signal (PRS) (SL PRS) and a message in a time slot for a frame in a time domain of a new radio (NR) system; extracting priority information of the SL PRS from a data storage device; and A schedule for transmission or reception of the SL PRS and the message is determined based on the priority information.

14. The method according to claim 13, comprising: determining that the SL PRS has a lower priority and the message has a higher priority; scheduling the message having a higher priority for transmission or reception; discarding a set of overlapping symbols of the SL PRS having a lower priority; as well as A set of non-overlapping symbols of the SL PRS are scheduled for transmission or reception.

15. The method according to claim 13, comprising: determining that the SL PRS has a lower priority and the message has a higher priority; scheduling the message having a higher priority for transmission or reception; as well as All symbols of the SL PRS having a lower priority are discarded.

16. The method according to claim 13, comprising: determining that the SL PRS has a higher priority and the message has a lower priority; Scheduling the SL PRS with a higher priority for transmission or reception; as well as All symbols of said message having a lower priority are discarded.

17. The method according to claim 13, comprising: Determining that the SL PRS does not have a priority level; as well as The message is scheduled by default for sending or receiving.

18. The method according to claim 13, comprising: From the physical sidelink control channel (PSCCH) carried by the first stage (1 st The sidelink scheduling information of the SL PRS is decoded from the SCI in the sidelink control information (SCI) format of the second stage (2 nd The sidelink scheduling information of the SL PRS is decoded in the SCI format of the SCI stage, wherein the 1 st Stage SCI format or the 2 nd An information field in the phase SCI format indicates the priority information of the SL PRS; extracting the priority information from the information field; and The priority information is stored in the data storage device.

19. A method according to any one of claims 13 to 18, comprising: From the physical sidelink control channel (PSCCH) carried by the first stage (1 st The sidelink scheduling information of the SL PRS is decoded in the sidelink control information (SCI) format 1-B, wherein the SCI format 1-B includes a priority, a source identifier (ID), a destination ID, a broadcast type indicator, or a resource reservation period [log2N rsυ-period ] information field, where, if the higher layer parameter sl-PRSResourceReservePeriodList is configured, Nrsv-period is the number of entries in the higher layer parameter sl-PRSResourceReservePeriodList, otherwise Nrsv-period is 0 bits.

20. The method according to any one of claims 13 to 18, comprising: The second phase (2 nd The SCI format 2-D of the sidelink control information (SCI) format decodes the sidelink scheduling information of the SL PRS in the stage, and the SCI format 2-D includes an information field for a hybrid automatic repeat request (HARQ) process number including 4 bits, a new data indicator including 1 bit, a redundant version including 2 bits, a source identifier (ID) including 8 bits, a destination ID including 16 bits, or a HARQ feedback enable / disable indicator including 1 bit.

Images