Confirmation feedback for positioning in RRC inactive state

Abstract

Embodiments of the present disclosure relate to devices, methods, apparatuses, and computer-readable storage media for confirmation feedback for positioning in an RRC inactive state. The method includes receiving information at a first device in a radio resource control RRC inactive state, the information at least indicating a delay requirement for the first device to transmit confirmation feedback for reception of a message, the message being associated with the positioning of the first device and being transmitted from a second device or a fourth device to the first device; and performing transmission of confirmation feedback for reception of the message based at least on the information without changing the RRC inactive state. Through the solution of the present disclosure, confirmation information reporting can be enabled to ensure the reliability of positioning assistance data reception. This is beneficial to the UE in terms of energy saving, end-to-end positioning delay reduction, and signaling overhead reduction.

Description

Technical Field

[0001] Embodiments of the present disclosure generally relate to the field of telecommunications, and in particular, to devices, methods, apparatuses, and computer-readable storage media for confirmation feedback of positioning in a radio resource control (RRC) inactive state. Background Art

[0002] New Radio (NR) introduces a new RRC state called "RRC Inactive (RRC_INACTIVE)" to meet the requirements of 5G services. Similar to the idle state, the inactive state is intended to limit the battery consumption of the UE, while the UE can reach the connected state with almost no signaling when it wants to send data. In the inactive state, from the perspective of the 5GC (5G Core Network), the UE maintains an Evolved Packet System Connection Management (ECM) connection, and therefore the Next Generation (NG) connection between the 5GC and the cell is maintained.

[0003] Currently, Small Data Transfer (SDT) has been agreed to be used as a way to transmit measurement reports in the RRC inactive state. In addition, some specific methods, measurements, signaling and procedures have been agreed to support positioning of UEs in the RRC inactive state for the positioning enhancement topic. Summary of the invention

[0004] Generally speaking, example embodiments of the present disclosure provide a solution for confirmation feedback of positioning in an RRC inactive state.

[0005] In a first aspect, there is a method. The method includes receiving, at a first device in a radio resource control (RRC) inactive state, information indicating at least a latency requirement for the first device to transmit a confirmation feedback for reception of a message, the message being associated with the positioning of the first device and being transmitted from a second device or a fourth device; and performing transmission of a confirmation feedback for reception of the message based on at least the information without changing the RRC inactive state.

[0006] In a second aspect, a method is provided. The method includes receiving, at a second device, information indicating a latency requirement for a first device to transmit an acknowledgment feedback for receipt of a message, the message being associated with the location of the first device and being transmitted from the second device or a fourth device; and transmitting the information to the first device.

[0007] In a third aspect, a method is provided. The method includes generating, at a fourth device, information indicating a latency requirement for a first device to transmit an acknowledgment feedback for receipt of a message, the message being associated with the location of the first device and being transmitted from a second device or a fourth device; and transmitting the information to the first device or the second device.

[0008] In a fourth aspect, a first device is provided. The first device comprises at least one processor; and at least one memory comprising computer program code; the at least one memory and the computer program code are configured to, together with the at least one processor, cause the first device to at least perform the method according to the first aspect.

[0009] In a fifth aspect, a second device is provided. The second device comprises at least one processor; and at least one memory comprising computer program code; the at least one memory and the computer program code are configured to, together with the at least one processor, cause the second device to at least perform the method according to the second aspect.

[0010] In a sixth aspect, a third device is provided. The third device comprises at least one processor; and at least one memory comprising computer program code; the at least one memory and the computer program code are configured to, together with the at least one processor, cause the third device to at least perform the method according to the third aspect.

[0011] In a seventh aspect, a device is provided, comprising a component for receiving, at a first device in a radio resource control (RRC) inactive state, information indicating at least a delay requirement for the first device to transmit confirmation feedback for reception of a message, the message being associated with the positioning of the first device and being transmitted from a second device or a fourth device; and a component for performing transmission of confirmation feedback for reception of the message based at least on the information without changing the RRC inactive state.

[0012] In an eighth aspect, a device is provided, comprising a component for receiving at a second device information indicating a delay requirement for a first device to transmit confirmation feedback for receipt of a message, the message being associated with the positioning of the first device and being transmitted from the second device or a fourth device; and a component for transmitting the information to the first device.

[0013] In a ninth aspect, a device is provided, comprising a component for generating, at a fourth device, information indicating a delay requirement for a first device to transmit confirmation feedback for receipt of a message, the message being associated with the positioning of the first device and being transmitted from a second device or a fourth device; and a component for transmitting the information to the first device or the second device.

[0014] In a tenth aspect, there is provided a computer readable medium having stored thereon a computer program which, when executed by at least one processor of a device, causes the device to perform the method according to the first aspect.

[0015] In an eleventh aspect, there is provided a computer readable medium having stored thereon a computer program which, when executed by at least one processor of a device, causes the device to perform the method according to the second aspect.

[0016] In a twelfth aspect, there is provided a computer readable medium having stored thereon a computer program which, when executed by at least one processor of a device, causes the device to perform the method according to the third aspect.

[0017] Other features and advantages of the embodiments of the present disclosure will also be apparent from the following description of specific embodiments when read in conjunction with the accompanying drawings, which illustrate, by way of example, the principles of the embodiments of the present disclosure. BRIEF DESCRIPTION OF THE DRAWINGS

[0018] Embodiments of the present disclosure are presented in an exemplary sense and their advantages are explained in more detail below with reference to the accompanying drawings, in which

[0019] Figure 1 An example environment is shown in which example embodiments of the present disclosure may be implemented;

[0020] Figure 2 A signaling diagram illustrating a procedure for confirmation feedback of positioning in an RRC inactive state according to some example embodiments of the present disclosure;

[0021] Figure 3 A signaling diagram illustrating a procedure for confirmation feedback of positioning in an RRC inactive state according to some example embodiments of the present disclosure;

[0022] Figure 4 A flowchart showing an example method for confirmation feedback of positioning in an RRC inactive state according to some example embodiments of the present disclosure;

[0023] Figure 5 A flowchart showing an example method for confirmation feedback of positioning in an RRC inactive state according to some example embodiments of the present disclosure;

[0024] Figure 6 A flowchart showing an example method for confirmation feedback of positioning in an RRC inactive state according to some example embodiments of the present disclosure;

[0025] Figure 7 shows a simplified block diagram of a device suitable for implementing an example embodiment of the present disclosure; and

[0026] Figure 8 A block diagram of an example computer-readable medium is shown in accordance with some embodiments of the present disclosure.

[0027] Throughout the drawings, the same or similar reference numerals refer to the same or similar elements. DETAILED DESCRIPTION

[0028] The principles of the present disclosure will now be described with reference to some example embodiments. It should be understood that the description of the example embodiments is only for the purpose of illustrating and helping those skilled in the art to understand and implement the present disclosure, and does not represent any limitation on the scope of the present disclosure. The disclosure described herein can be implemented in various other ways except for the way described below.

[0029] In the following description and claims, unless defined otherwise, all technical and scientific terms used herein have the same meaning as commonly understood by one of ordinary skill in the art to which this disclosure belongs.

[0030] References in this disclosure to "one embodiment," "an embodiment," "an example embodiment," etc. indicate that the described embodiment may include a particular feature, structure, or characteristic, but not every embodiment necessarily includes the particular feature, structure, or characteristic. Furthermore, such phrases do not necessarily refer to the same embodiment. Furthermore, when a particular feature, structure, or characteristic is described in conjunction with an example embodiment, it is considered to be within the knowledge of those skilled in the art to affect such feature, structure, or characteristic in conjunction with other embodiments (whether or not explicitly described).

[0031] It should be understood that although the terms "first" and "second" etc. may be used herein to describe various elements, these elements should not be limited by these terms. These terms are only used to distinguish the functions of the various elements. As used herein, the term "and / or" includes any and all combinations of one or more of the listed terms.

[0032] The terms used herein are for the purpose of describing specific embodiments only and are not intended to limit the exemplary embodiments. As used herein, the singular forms "a", "an", and "the" are intended to include the plural forms as well, unless the context clearly indicates otherwise. It will be further understood that the terms "comprise", "include", "have", "have", "include" and / or "comprising" when used herein specify the presence of the features, elements and / or components, etc., but do not exclude the presence or addition of one or more other features, elements, components and / or combinations thereof.

[0033] As used in this application, the term "circuitry" may refer to one, more, or all of the following:

[0034] (a) a pure hardware circuit implementation (such as an implementation using only analog and / or digital circuitry), and

[0035] (b) a combination of hardware circuitry and software such as (where applicable):

[0036] (i) a combination of analog and / or digital hardware circuits and software / firmware, and

[0037] (ii) any portion of hardware processor(s) (including digital signal processor(s)), software and memory(s) with software that work together to enable a device (such as a mobile phone or server) to perform various functions, and

[0038] (c) Hardware circuits and / or processor(s), such as microprocessor(s) or portions of microprocessor(s), that require software (e.g., firmware) to operate, but which may not be present when the software is not required for operation.

[0039] This definition of circuitry applies to all uses of the term in this application, including in any claims. As another example, as used in this application, the term circuitry also covers an implementation of only a hardware circuit or processor (or multiple processors) or a portion of a hardware circuit or processor and its (or their) accompanying software and / or firmware. For example, if applicable to a particular claim element, the term circuitry also covers a baseband integrated circuit or processor integrated circuit for a mobile device, or a similar integrated circuit in a server, cellular network device, or other computing or network device.

[0040] As used herein, the term "communication network" refers to a network that follows any suitable communication standard, such as a fifth generation (5G) system, long term evolution (LTE), advanced LTE (LTE-A), wideband code division multiple access (WCDMA), high speed packet access (HSPA), narrowband Internet of Things (NB-IoT), etc. In addition, the communication between the terminal device and the network device in the communication network can be performed according to the communication protocol of any suitable generation, including but not limited to the first generation (1G), the second generation (2G), 2.5G, 2.75G, the third generation (3G), the fourth generation (4G), 4.5G, the future fifth generation (5G) new radio (NR) communication protocol, and / or and / or any other protocol currently known or developed in the future. The embodiments of the present disclosure can be applied to various communication systems. In view of the rapid development of communication, there will certainly be communication technologies and systems of future types that can embody the present disclosure. It should not be considered that the scope of the present disclosure is limited to the above-mentioned system.

[0041] As used herein, the term "network device" refers to a node in a communication network via which a terminal device accesses the network and receives services from it. A network device may refer to a base station (BS) or an access point (AP), such as a NodeB (NodeB or NB), an evolved NodeB (eNodeB or eNB), a NR next-generation NodeB (gNB), a remote radio unit (RRU), a radio head (RH), a remote radio head (RRH), a relay, a low-power node (such as a femto, a pico), etc., depending on the terminology and technology applied. The RAN split architecture includes a gNB-CU (centralized unit, hosting RRC, SDAP, and PDCP) that controls multiple gNB-DUs (distributed units, hosting RLC, MAC, and PHY). A relay node may correspond to the DU portion of an IAB node.

[0042] The term "terminal device" refers to any terminal device that can perform wireless communication. As an example and not limitation, the terminal device may also be referred to as a communication device, a user equipment (UE), a subscriber station (SS), a portable subscriber station, a mobile station (MS) or an access terminal (AT). The terminal device may include, but is not limited to, a mobile phone, a cellular phone, a smart phone, a voice over IP (VoIP) phone, a wireless local loop phone, a tablet computer, a wearable terminal device, a personal digital assistant (PDA), a portable computer, a desktop computer, an image acquisition terminal device such as a digital camera, a game terminal device, a music storage and playback device, a vehicle-mounted wireless terminal device, a wireless endpoint, a mobile station, a laptop embedded device (LEE), a laptop mounted device (LME), a USB dongle, a smart device, a wireless client device (CPE), an Internet of Things (IoT) device, a watch or other wearable device, a head mounted display (HMD), a vehicle, a drone, medical equipment and applications (e.g., remote surgery), industrial equipment and applications (e.g., robots and / or other wireless devices operating in industrial and / or automated processing chain environments), consumer electronic devices, equipment operating on commercial and / or industrial wireless networks, etc. The terminal device may also correspond to the mobile termination (MT) part of an integrated access and backhaul (IAB) node (also known as a relay node). In the following description, the terms "terminal device", "communication device", "terminal", "user equipment" and "UE" may be used interchangeably.

[0043] Although the functions described herein may be performed in fixed and / or wireless network nodes in various example embodiments, in other example embodiments, the functions may be implemented in a user equipment device (such as a cellular phone or a tablet or a laptop or a desktop computer or a mobile IoT device or a fixed IoT device). For example, the user equipment device may be appropriately equipped with corresponding capabilities as described in conjunction with (multiple) fixed and / or wireless network nodes. The user equipment device may be a user device and / or a control device (such as a chipset or a processor) configured to control the user device when installed in the user device. Examples of such functions include boot server functions and / or home subscriber servers, which may be implemented in the user equipment device by providing software to the user equipment device, the software being configured to cause the user equipment device to perform operations from the perspective of these functions / nodes.

[0044] Figure 1 1 shows an example communication network 100 in which embodiments of the present disclosure may be implemented. Figure 1 As shown, the communication network 100 may include a terminal device 110 (hereinafter may also be referred to as UE 110 or first device 110). The communication network 100 may also include a network device 120-1 (hereinafter may also be referred to as gNB 120-1 or second device 120-1). The network device 120-1 may manage a cell 102-1 (hereinafter may also be referred to as an anchor cell 102-1).

[0045] In addition, the communication network 100 may also include a network device 120-2 (hereinafter may also be referred to as another gNB 120-2 or a third device 120-2). The network device 120-2 may manage a cell 102-2 (hereinafter may also be referred to as a last serving cell 102-2). Before transitioning to the RRC inactive mode, the UE 110 may be served by the last serving cell 102-2. As the UE 110 moves, the UE 110 may leave the coverage of the last serving cell 102-2 and enter the coverage of other cells, such as the coverage of the anchor cell 102-1.

[0046] It is also possible that the last serving cell and anchor cell of the UE are managed by the same gNB. In this case, network device 120-1 and network device 120-2 can be considered as the same network device. In some scenarios, network device 120-1 and network device 120-2 can also be collectively referred to as network device 120.

[0047] The communication network 100 may further include a location management function (LMF) 130 (hereinafter may also be referred to as a fourth device 130), which may communicate with the terminal device 110 and the network devices 120-1 and 120-2. The LMF 130 may be referred to as a management node in the core network.

[0048] Understandably, Figure 1 The number of network devices and terminal devices shown is given for illustrative purposes and does not imply any limitation. Communication network 100 may include any suitable number of network devices and terminal devices.

[0049] According to the communication technology, network 100 can be a code division multiple access (CDMA) network, a time division multiple access (TDMA) network, a frequency division multiple access (FDMA) network, an orthogonal frequency division multiple access (OFDMA) network, a single carrier frequency division multiple access (SC-FDMA) network, etc. The communication discussed in network 100 can meet any suitable standard, including but not limited to new radio access (NR), long term evolution (LTE), evolved LTE, advanced LTE (LTE-A), wideband code division multiple access (WCDMA), code division multiple access (CDMA), cdma2000 and global system for mobile communications (GSM), etc. In addition, the communication can be performed according to any generation of communication protocols currently known or to be developed in the future. Examples of communication protocols include but are not limited to first generation (1G), second generation (2G), 2.5G, 2.75G, third generation (3G), fourth generation (4G), 4.5G, fifth generation (5G) communication protocols. The technology described herein can be used for the above-mentioned wireless network and radio technology as well as other wireless networks and radio technologies. For clarity, certain aspects of the techniques are described below for LTE, and LTE terminology is used in much of the description below.

[0050] As mentioned above, the RRC inactive state has been introduced for 5G services. The UE can be configured to the inactive state from the connected state by its last serving cell, which can send an RRC suspend message including the applicable RAN Notification Area (RNA) to the UE. When the UE is in the inactive state, the last serving cell becomes the anchor cell for the UE to maintain the UE context.

[0051] In the inactive state, the location of the UE can be monitored by the RNA. In the RNA area, the UE can move across cells without basically any signaling unless it has data to send. When the UE moves out of the RNA, the UE can notify the anchor cell through the RRC location update message. In this case, if the UE is located in a new cell, the new cell can usually trigger the Xn context acquisition process to retrieve the UE context from the anchor cell. The anchor function is then relocated, and the new cell becomes the new anchor cell.

[0052] For positioning enhancement, it has been agreed that some specific methods, measurements, signaling and procedures can support positioning of UEs in RRC inactive state. It has also been agreed that SDT can be used as a way to transmit measurement reports in RRC inactive state. Some different types of SDT can be supported, such as 4-step random access channel (RACH) based SDT, 2-step RACH based SDT and configuration grant (CG) based SDT.

[0053] A Long Term Evolution (LTE) Positioning Protocol (LPP) message may be transmitted from a transmitting device to a receiving device for use in a positioning process of the receiving device. The LPP message may include an IE ackRequested set to TRUE, and a sequence number. When the receiving device can decode the ackRequested value and the sequence number, the receiving device may return an acknowledgment of the LPP message. The acknowledgment may include an IE ackIndicator set to the same sequence number as the sequence number in the received LPP message. When the transmitting device receives an acknowledgment of the transmitted LPP message and the acknowledgment may provide an ackIndicator IE that matches the sequence number in the transmitted LPP message, the transmitting device may transmit a subsequent LPP message to the receiving device.

[0054] Positioning assistance data can be transmitted in LPP messages. For positioning operations in NR, network equipment may need to deliver positioning assistance data to the positioning UE. The positioning assistance data involved in downlink (DL) and uplink (UL) positioning may include the following aspects: positioning reference signal (PRS) configuration, measurement and reporting configuration, etc. for DL ​​positioning process; UL PRS (e.g., sounding reference signal (SRS)) configuration initiated by the cell; capability and location information request initiated from LMF; and positioning SRS activation or deactivation signaling.

[0055] It has been proposed that positioning assistance data can be transmitted in the RRC inactive state for UE power saving and positioning delay reduction. For example, positioning assistance data can be transmitted as downlink small data in a new RACH process in the RRC inactive state. The network device will first page the device, and then the positioning device will initiate the RRC connection recovery process in the RRC inactive state for downlink data transmission.

[0056] Some methods are proposed that can deliver positioning assistance data through paging messages. For example, the UR can be awakened in the RRC idle / inactive state to start positioning measurement and reporting through a paging message, or the SRS for positioning configuration information can be carried in the paging message.

[0057] However, there is no mechanism that enables the UE to feed back confirmation of the reception of the positioning assistance data without entering the connected mode. Therefore, how to enable confirmation transmission after receiving the positioning assistance data may still need to be discussed.

[0058] The present disclosure proposes a solution for confirmation feedback of positioning in an RRC inactive state. In the solution, in the RRC inactive state, the UE can receive information at least indicating a delay requirement for the UE to transmit confirmation feedback for reception of an LPP message. The UE can perform transmission of confirmation feedback for reception of a message based at least on the information without changing the RRC inactive state.

[0059] Combine the following Figures 2 to 3 The principle and implementation of the present disclosure are described in detail. Figures 2 to 3 Schematic processes of confirmation feedback for positioning in an RRC inactive state are respectively shown.

[0060] Figure 2 A signaling diagram illustrating a process 200 for confirmation feedback of positioning in an RRC inactive state according to some example embodiments of the present disclosure is shown. For the purpose of discussion, reference will be made to Figure 1 Describe process 200. Process 200 may involve Figure 1 UE 110, anchor cell 102-1, last serving cell 102-2 and LMF 130 are shown. Anchor cell 102-1 may be managed by gNB 120-1, as shown in FIG. Figure 1 As shown, the last serving cell can be managed by gNB 120-1 or gNB120-2, as shown Figure 1 shown.

[0061] For situations where latency is critical, LMF 130 may provide corresponding QoS information, which may indicate the tolerable latency of the UE response. Figure 2 As shown, LMF 130 may transmit 202 to last serving cell 102-2 information indicating a delay requirement for UE 110 to transmit an acknowledgement feedback for reception of an LPP message. Hereinafter, information indicating the delay requirement of UE 110 may also be referred to as delay information.

[0062] In some example embodiments, latency information may be provided along with the positioning assistance data, for example, because the LMF 130 may deliver the positioning assistance data to the last serving cell 102 - 2 .

[0063] The last serving cell 102-2 may then transmit 204 the latency information to the anchor cell 102-1. In some example embodiments, the anchor cell 102-1 may obtain the latency information from the last serving cell 102-2 via a paging message. In a paging-triggered positioning assistance data transmission, the last serving cell 102-2 may instruct the cells in the RNA to page the UE 110 for the purpose of positioning assistance data transmission. Thus, the latency information may also be delivered to the cells in the RNA together with the paging trigger signaling.

[0064] The anchor cell 102-1 may also request latency information from the last serving cell 102-2. Upon receiving the RRC recovery request from the UE 110, the anchor cell 102-1 may request positioning assistance data from the last serving cell 102-2. The last serving cell 102-2 may then provide the positioning assistance data to the anchor cell 102-1. Thus, the latency information may also be provided along with the positioning assistance data delivery message from the last serving cell 102-2.

[0065] After receiving the latency information from the last serving cell 102-2, the anchor cell 102-1 may determine a transmission resource and a transmission mode for the UE to transmit an acknowledgement feedback (ie, an acknowledgement message) of the reception of the LPP message.

[0066] In some example embodiments, anchor cell 102-1 may determine that UE 110 may transmit a reception confirmation to anchor cell 102-1 via CG resources (eg, via CG resources used for SDT) in an RRC inactive or idle state.

[0067] In some example embodiments, anchor cell 102-1 may also determine that UE 110 may transmit a receipt acknowledgement to anchor cell 102-1 via RACH resources.

[0068] As another option, the anchor cell 102-1 may also determine that the UE 110 may transmit a reception confirmation to the anchor cell 102-1 through a physical uplink control channel (PUCCH) resource configured through system information.

[0069] The anchor cell 102-1 can use the latency information to determine whether any of the above transmission modes and corresponding resources are suitable for confirmation message transmission based on the QoS and the time when it sends the positioning assistance data, because the anchor cell 102-1 knows when the pre-configured CG or PUCCH or RACH resources occur. If any of the configured resources are not suitable, the anchor cell 102-1 can configure a new dedicated resource for confirmation message transmission.

[0070] Therefore, the anchor cell 102-1 may also determine that the UE 110 may transmit a reception confirmation to the anchor cell 102-1 via dedicated resources.

[0071] Once the transmission mode is determined, the corresponding transmission resources may also be determined.Based on the determined transmission mode and resources, anchor cell 102-1 may instruct UE 110 how to send the confirmation information.

[0072] The anchor cell 102-1 may then generate 206 feedback assistance information for the UE 110 to transmit a UL confirmation message based on the delay information received from the last serving cell 102-2 and the determined transmission mode and corresponding transmission resources.

[0073] In some example embodiments, the confirmation feedback assistance information may include a time window for UE 110 to transmit a UL confirmation message. For example, the time window may refer to a response time before which UE 110 must feedback the confirmation. Alternatively, the time window may refer to a transmission window within which UE 110 is allowed to attempt multiple times for confirmation transmission.

[0074] In some example embodiments, the confirmation feedback assistance information may also include a transmission mode and corresponding transmission resources for UL confirmation transmission of UE 110. For example, the transmission mode may be CG-SDT, RACH-based SDT, PUCCH, etc. Accordingly, the transmission resources may be CG resources, RACH resources, or PUCCH resources.

[0075] The anchor cell 102-1 may then transmit 208 the confirmation feedback assistance information to the UE 110. For example, the confirmation feedback assistance information may be transmitted from the anchor cell 102-1 to the UE 110, e.g., along with a DL positioning assistance data delivery message, which may be included in a DL MAC PDU along with the RRC release message.

[0076] Specifically, as an option, the confirmation feedback assistance information may be transmitted through a RACH message, such as message B (MsgB) for a 2-step RACH procedure or message 4 (Msg4) for a 4-step RACH procedure, for example, together with a DL positioning assistance data delivery message.

[0077] As another option, in response to receiving an RRC resume request through the CG resources configured for SDT, the confirmation feedback assistance information can be transmitted through the DL physical downlink shared channel (PDSCH), for example, together with the DL positioning assistance data delivery message.

[0078] After receiving the acknowledgment feedback assistance information, UE 110 may perform 210 UL acknowledgment transmission based on the acknowledgment feedback assistance information.

[0079] In some example embodiments, if UE 110 determines that the transmission resources are indicated in the confirmation feedback assistance information, UE 110 may use the configured transmission resources (i.e., 2-step / 4-step RACH resources or CG-SDT resources, PUCCH resources or dedicated resources) to transmit the confirmation message.

[0080] For example, if the cell indicates 2-step RACH-based SDT for confirmation transmission, UE 110 may transmit the confirmation transmission along with the RRC recovery request in message A (MsgA) for the 2-step RACH procedure.

[0081] In addition, UE 110 can obtain a time window associated with UL confirmation transmission from the confirmation feedback auxiliary information, where the time window may refer to a response time before which UE 110 must feedback confirmation, or the time window may refer to a transmission window within which UE 110 is allowed to attempt multiple times for confirmation transmission.

[0082] If UE 110 determines that a UL acknowledgment transmission may be performed on the transmission resources indicated in the acknowledgment feedback assistance information before the time window expires, UE 110 may transmit 212 a UL acknowledgment transmission to anchor cell 102-1.

[0083] In some example embodiments, UE 110 may transmit a UL acknowledgement transmission along with an RRC recovery request in MsgA for a 2-step RACH procedure, message 3 (Msg3) for a 4-step RACH procedure, or a CG PUSCH resource for SDT.

[0084] In some example embodiments, UE 110 may also indicate in an RRC message such as RRCResumeRequest that UE 110 requests transmission of a NAS message (e.g., an LPP message). The indication may also indicate that UE 110 did not request to enter RRC connected mode to provide NAS messages. Alternatively, the indication may also indicate a request to enter RRC connected mode due to transmission of a NAS message.

[0085] In some example embodiments, if the message size exceeds a certain message size threshold, the UE may be configured to enter RRC connected mode. The threshold may be set so that the UE may use pre-configured feedback resources to provide an LPP confirmation message.

[0086] If UE 110 determines that UL acknowledgment transmission is not performed on the transmission resources indicated in the acknowledgment feedback assistance information before the time window expires, UE 110 may transmit an LPP error message to anchor cell 102-1, which may include the received transaction ID and the error type.

[0087] For example, the error cause may be indicated as undefined, or a new error cause may be defined to indicate that a latency threshold was exceeded.

[0088] In some example embodiments, UE 110 may transmit the LPP error message to anchor cell 102-1 by entering RRC connected mode.

[0089] In this case, when the confirmation message is not successfully transmitted, UE 110 may discard the LPP message.

[0090] It is also possible that the transmission resource for UL confirmation transmission is not indicated in the confirmation feedback assistance information. In this case, UE 110 can autonomously select pre-configured resources for SDT (i.e., 2-step / 4-step RACH resources or CG-SDT resources or PUCCH). As another option, UE 110 can select the default transmission mode (i.e., RACH-based SDT). In this case, UE 110 can indicate signaling to the anchor cell to indicate that this is a confirmation message for positioning assistance data.

[0091] After receiving the confirmation message from UE 110, anchor cell 102-1 may forward 214 the confirmation message to last serving cell 102-2. Last serving cell 102-2 may further forward 216 the confirmation message to LMF 130.

[0092] use Figure 2 In the solution shown in process 200, the LMF may indicate the latency information of the anchor gNB (managing the anchor cell) to determine the transmission mode and transmission resources for the confirmation message transmission. The anchor gNB may indicate the transmission resources and transmission mode to the UE along with the LPP message (i.e., positioning assistance data) delivery. Therefore, the solution may dynamically allocate resources for the confirmation message transmission to achieve fast confirmation message transmission. In addition, when the LPP message is delivered to the UE, the transmission resources may also be pre-configured to the anchor gNB for the confirmation message.

[0093] As another option, LMF 130 may also indicate latency information to UE 110. If the UE has been configured to provide confirmation messages in a latency-critical manner, the UE may indicate latency information for UL resource configuration to the serving cell. This solution may refer to Figure 3 Give a description.

[0094] Reference now Figure 3 . Figure 3 A signaling diagram illustrating a process 300 for confirmation feedback of positioning in an RRC inactive state according to some example embodiments of the present disclosure is shown. For the purpose of discussion, reference will be made to Figure 1Describe process 300. Process 300 may involve Figure 1 UE 110, gNB 120 and LMF 130 are shown.

[0095] like Figure 3 As shown, LMF 130 may transmit 302 latency information to UE 110. For example, LMF 130 may transmit latency information to UE 110 via an LPP message. For example, latency information may be added as a new element information in an LPP message header to indicate whether the confirmation request is latency critical. Alternatively, latency information may be added as a new element information ackRequestedLatencyCritical indicated in the LPP message. It should be understood that element information may also be referred to as another parameter name having a similar function.

[0096] In some example embodiments, if latency information is included in an LPP message, the LPP message may be represented as follows.

[0097] Table 1: LPP messages

[0098]

[0099]

[0100] After receiving the LPP message, the UE 110 may know whether the confirmation request is latency critical and may determine 304 how and where to transmit the LPP confirmation message. When the UE is triggered to provide latency critical feedback, the UE may transmit the LPP confirmation message alone. That is, the UE 110 may not provide the LPP confirmation message as part of any other LPP message it may have in a transmission buffer.

[0101] In some example embodiments, if the UE determines that the currently available UL resources can meet the latency requirement, the UE 110 may transmit the confirmation message on the currently available UL resources. For example, the gNB 120 may pre-configure some RACH-SDT / CG-SDT resources for the UE 110 to transmit the LPP confirmation message.

[0102] In some example embodiments, if the UE determines that currently available UL resources do not meet latency requirements, UE 110 may indicate latency information for a new UL resource allocation to gNB 120. For example, UE 110 may transmit 306 latency information to gNB 120 to request a new UL resource allocation.

[0103] In some example embodiments, the transmission of latency information may be cell-specific or RNA-specific.When the UE reselects a new cell or a new RNA, the UE 110 may provide latency constraints / latency information to the reselected cell.

[0104] Based on the latency information, gNB 120 may determine 308 new UL resources to allocate to UE 110 for transmission of the confirmation message. gNB 120 may transmit 310 an indication of the allocated UL resources to UE 110. It should be understood that any other positioning-related messages to be transmitted from gNB 120 to UE 110 may also be followed by the UL resource configuration.

[0105] Through the solution of the present disclosure, confirmation information reporting can be enabled to ensure the reliability of positioning assistance data reception. After receiving the positioning assistance data, there is no RRC connection state transition from inactive state to connected state for confirmation information feedback. In addition, the delay information can be used to configure SDT resources for confirmation information reporting to ensure QoS requirements. This is beneficial to the UE in terms of energy saving, end-to-end positioning delay reduction and signaling overhead reduction.

[0106] Figure 4 FIG. 4 is a flowchart showing an example method 400 for confirmation feedback of positioning in an RRC inactive state according to some example embodiments of the present disclosure. The method 400 may be performed in a manner such as Figure 1 For the purpose of discussion, reference will be made to Figure 1 Method 400 is described.

[0107] At 410, the first device receives information in an RRC inactive state indicating at least a latency requirement for the first device to transmit an acknowledgment feedback for receipt of a message. The message is associated with the positioning of the first device and is transmitted from the second device or the fourth device.

[0108] In some example embodiments, the first device may receive the information via: message B during a 2-step random access procedure between the first device and the second device; message 4 during a 4-step random access procedure between the first device and the second device; or a data channel associated with a configuration grant for small data transmission between the first device and the second device.

[0109] At 420, the first device performs transmission of confirmation feedback for receipt of the message based at least on the information without changing the RRC inactive state.

[0110] In some example embodiments, if the information is received from the second device, the first device may determine a time window based on latency requirements; determine a transmission mode and resource for transmitting confirmation feedback for receipt of the message; and determine whether the confirmation feedback is allowed to be transmitted on the resource in the transmission mode before the time window expires. If the first device determines that the confirmation feedback is allowed to be transmitted on the resource in the transmission mode before the time window expires, the first device may transmit the confirmation feedback to the second device on the resource in the transmission mode.

[0111] In some example embodiments, the resources include at least one of: resources associated with a random access procedure between the first device and the second device, resources associated with a configuration authorization allocated to the first device, resources associated with a control channel between the first device and the second device, or resources dedicated to the first device transmitting confirmation feedback.

[0112] In some example embodiments, the transmission mode includes at least one of: small data transmission based on configuration grant, small data transmission based on a random access procedure, or transmission carried by a control channel between the first device and the second device.

[0113] In some example embodiments, the time window indicates one of: a response time before which the first device is required to transmit an acknowledgment; or a transmission window within which the first device is allowed to perform multiple attempts for transmission of acknowledgment feedback.

[0114] In some example embodiments, if the first device determines that confirmation feedback is not allowed to be transmitted on the resource in the transmission mode before the time window expires, the first device may transmit an indication of the received error to the second device.

[0115] In some example embodiments, the indication of the error includes a type of error.

[0116] In some example embodiments, the indication is transmitted in RRC connected mode.

[0117] In some example embodiments, if the information is received from the second device and if the first device determines that a resource for transmitting confirmation feedback for receipt of the message is not indicated in the information, the first device may select the resource from a set of candidate resources preconfigured for transmission.

[0118] In some example embodiments, the first device may transmit to the second device an indication that the first device did not request to enter RRC connected mode to transmit confirmation feedback.

[0119] In some example embodiments, if the information is received from a fourth device, the first device may determine whether a set of candidate resources available for transmission meets the latency requirement. If the first device determines that a set of candidate resources available for transmission of confirmation feedback by the first device does not meet the latency requirement, the first device may transmit a request to the second device for resources for transmission of confirmation feedback by the first device. If the first device determines that the resources for transmission of confirmation feedback by the first device have been allocated by the second device, the first device may transmit the confirmation feedback on the allocated resources.

[0120] In some example embodiments, if the first device determines that a set of candidate resources available for the first device to transmit an acknowledgment feedback meets latency requirements, the first device may select resources from the set of candidate resources for the first device to transmit the acknowledgment feedback and transmit the acknowledgment feedback on the selected resources.

[0121] In some example embodiments, the latency requirement includes at least one of: an expected time for confirmation feedback, or a latency threshold for providing confirmation feedback.

[0122] In some example embodiments, the first device comprises a terminal device, the second device comprises a network device, and the fourth device comprises a location management entity.

[0123] Figure 5 FIG. 5 is a flowchart showing an example method 500 for confirmation feedback of positioning in an RRC inactive state according to some example embodiments of the present disclosure. The method 500 may be performed in a manner such as Figure 1 The second device 120 is shown as being implemented. For the purpose of discussion, reference will be made to Figure 1 Method 500 is described.

[0124] At 510, the second device receives information indicating at least a latency requirement for the first device to transmit an acknowledgment feedback for receipt of a message. The message is associated with the location of the first device and is transmitted from the second device or the fourth device.

[0125] In some example embodiments, the second device may receive the information from the third device via paging signaling.

[0126] In some example embodiments, the second device may transmit a request for the information to the third device; and receive the information from the third device.

[0127] In some example embodiments, the second device may transmit the information along with the message to the first device.

[0128] In some example embodiments, the second device may determine, based on the information, resources and a transmission mode for the first device to transmit confirmation feedback; generate an indication of the resources and a transmission mode for the first device to transmit confirmation feedback; and transmit the indication included in the information to the first device.

[0129] In some example embodiments, the resources include at least one of: resources associated with a random access procedure between the first device and the second device, resources associated with a configuration authorization allocated to the first device, resources associated with a control channel between the first device and the second device, or resources dedicated to the first device transmitting confirmation feedback.

[0130] In some example embodiments, the transmission mode includes at least one of: small data transmission based on configuration grant, small data transmission based on a random access procedure, or transmission carried by a control channel between the first device and the second device.

[0131] At 520, the second device transmits the information to the first device.

[0132] In some example embodiments, the second device may transmit the information via at least one of: message B in a 2-step random access procedure between the first device and the second device, message 4 in a 4-step random access procedure between the first device and the second device, or a data channel associated with a configuration authorization for small data transmission between the first device and the second device.

[0133] In some example embodiments, the second device may receive an indication from the first device that the first device did not enter RRC connected mode to transmit the confirmation feedback.

[0134] In some example embodiments, the second device may receive a request from the first device for resources for the first device to transmit the acknowledgment feedback; and allocate the resources for the first device to transmit the acknowledgment feedback.

[0135] In some example embodiments, the latency requirement includes at least one of: an expected time for confirmation feedback, or a latency threshold for providing confirmation feedback.

[0136] In some example embodiments, the first device comprises a terminal device, the second device comprises a network device, and the fourth device comprises a location management entity.

[0137] Figure 6 FIG. 6 is a flowchart showing an example method 600 for confirmation feedback of positioning in an RRC inactive state according to some example embodiments of the present disclosure. The method 600 may be performed in a manner such as Figure 1 The fourth device 130 is shown as being implemented. For the purpose of discussion, reference will be made to Figure 1 Method 600 is described.

[0138] At 610, the fourth device generates information indicating a latency requirement for the first device to transmit an acknowledgment feedback for receipt of a message. The message is associated with the location of the first device and is transmitted from the second device or the fourth device.

[0139] At 620 , the fourth device transmits the information to the first device or the second device via the third device.

[0140] In some example embodiments, the fourth device may transmit the information along with the message.

[0141] In some example embodiments, the latency requirement includes at least one of: an expected time for confirmation feedback, or a latency threshold for providing confirmation feedback.

[0142] In some example embodiments, the first device comprises a terminal device, the second device comprises a network device, and the fourth device comprises a location management entity.

[0143] In some example embodiments, an apparatus capable of performing method 400 (e.g., implemented at UE 110) may include components for performing the corresponding steps of method 400. The components may be implemented in any suitable form. For example, the components may be implemented using a circuit system or a software module.

[0144] In some example embodiments, the apparatus includes a component for receiving, at a first device in a radio resource control (RRC) inactive state, information indicating at least a latency requirement for the first device to transmit confirmation feedback for reception of a message, the message being associated with the positioning of the first device and being transmitted from a second device or a fourth device; and a component for performing transmission of confirmation feedback for reception of the message based at least on the information without changing the RRC inactive state.

[0145] In some example embodiments, an apparatus capable of performing method 500 (e.g., implemented at gNB 120) may include components for performing the corresponding steps of method 500. The components may be implemented in any suitable form. For example, the components may be implemented in a circuit system or a software module.

[0146] In some example embodiments, the apparatus includes a component for receiving, at a second device, information indicating a latency requirement for a first device to transmit confirmation feedback for receipt of a message, the message being associated with the positioning of the first device and being transmitted from the second device or a fourth device; and a component for transmitting the information to the first device.

[0147] In some example embodiments, an apparatus capable of performing method 600 (e.g., implemented at LMF 130) may include components for performing the corresponding steps of method 600. The components may be implemented in any suitable form. For example, the components may be implemented using a circuit system or a software module.

[0148] In some example embodiments, the apparatus includes a component for generating, at a fourth device, information indicating a latency requirement for a first device to transmit confirmation feedback for receipt of a message, the message being associated with the positioning of the first device and being transmitted from a second device or a fourth device; and a component for transmitting the information to the first device or the second device.

[0149] Figure 7 700 is a simplified block diagram of a device 700 suitable for implementing an embodiment of the present disclosure. The device 700 may be provided to implement a communication device, such as Figure 1 UE 110, gNB 120 and LMF 130 are shown. As shown in the figure, the device 700 includes one or more processors 710, one or more memories 740 coupled to the processor 710, and one or more communication modules 740 coupled to the processor 710.

[0150] The communication module 740 is used for two-way communication. The communication module 740 has one or more communication interfaces to facilitate communication with one or more other modules or devices. The communication interface may represent any interface necessary for communication with other network elements. In some example embodiments, the communication module 740 may include at least one antenna.

[0151] Processor 710 may be of any type suitable for the local technology network, and may include, as non-limiting examples, one or more of a general purpose computer, a special purpose computer, a microprocessor, a digital signal processor (DSP), and a processor based on a multi-core processor architecture. Device 700 may have multiple processors, such as application specific integrated circuit chips that are time slaved to a clock synchronized with a main processor.

[0152] The memory 720 may include one or more non-volatile memories and one or more volatile memories. Examples of non-volatile memories include, but are not limited to, read-only memory (ROM) 724, electrically programmable read-only memory (EPROM), flash memory, hard disk, compact disk (CD), digital video disk (DVD), and other magnetic storage and / or optical storage. Examples of volatile memories include, but are not limited to, random access memory (RAM) 722 and other volatile memories that do not persist during power outages.

[0153] Computer program 730 includes computer executable instructions executed by associated processor 710. Program 730 may be stored in ROM 720. Processor 710 may perform any suitable actions and processes by loading program 730 into RAM 720.

[0154] The embodiments of the present disclosure can be implemented by means of program 730, so that the device 700 can execute the following steps: Figure 2-Figure 6 Any process of the present disclosure discussed. The embodiments of the present disclosure may also be implemented by hardware or a combination of software and hardware.

[0155] In some embodiments, the program 730 may be tangibly embodied in a computer-readable medium that may be included in the device 700 (such as in the memory 720) or in other storage devices accessible to the device 700. The device 700 may load the program 730 from the computer-readable medium to the RAM 722 for execution. The computer-readable medium may include any type of tangible non-volatile memory, such as ROM, EPROM, flash memory, hard disk, CD, DVD, etc. Figure 8 An example of a computer readable medium 800 in the form of a CD or DVD is shown. The computer readable medium has a program 730 stored thereon.

[0156] Generally, various embodiments of the present disclosure may be implemented using hardware or dedicated circuits, software, logic, or any combination thereof. Some aspects may be implemented using hardware, while other aspects may be implemented using firmware or software that may be executed by a controller, microprocessor, or other computing device. Although various aspects of the embodiments of the present disclosure are illustrated and described as block diagrams, flow charts, or using some other graphical representations, it should be understood that, as non-limiting examples, the blocks, devices, systems, techniques, or methods described herein may be implemented using hardware, software, firmware, dedicated circuits or logic, general-purpose hardware or controllers or other computing devices, or some combination thereof.

[0157] The present disclosure also provides at least one computer program product tangibly stored on a non-transitory computer-readable storage medium. The computer program product includes computer executable instructions, such as instructions included in a program module, which are executed in a device on a target real or virtual processor to perform the above referenced Figures 4 to 6 Methods 400-600 described herein. Typically, program modules include routines, programs, libraries, objects, classes, components, data structures, etc. that perform specific tasks or implement specific abstract data types. In various embodiments, the functions of program modules can be combined or split between program modules as needed. The machine executable instructions of program modules can be executed in local or distributed devices. In distributed devices, program modules can be located in both local and remote storage media.

[0158] The program code for executing the method of the present disclosure can be written in any combination of one or more programming languages. These program codes can be provided to a processor or controller of a general-purpose computer, a special-purpose computer or other programmable data processing device so that the program code enables the function / operation specified in the flow chart and / or block diagram to be realized when executed by the processor or controller. The program code can be executed completely on the machine, partially on the machine, as an independent software package, partially on the machine and partially on a remote machine, or completely on a remote machine or server.

[0159] In the context of the present disclosure, computer program codes or related data may be carried by any suitable carrier to enable a device, apparatus or processor to perform various processes and operations as described above. Examples of carriers include signals, computer readable media, etc.

[0160] The computer readable medium can be a computer readable signal medium or a computer readable storage medium. The computer readable medium can include, but is not limited to, electronic, magnetic, optical, electromagnetic, infrared or semiconductor systems, devices or equipment, or any suitable combination of the foregoing. A more specific example of a computer readable storage medium will include an electrical connection with one or more wires, a portable computer floppy disk, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disk read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing.

[0161] In addition, although the operations are described in a particular order, this should not be understood as requiring such operations to be performed in the particular order shown or in order or performing all the operations shown to obtain the desired result. In some cases, multitasking and parallel processing may be advantageous. Similarly, although several specific implementation details are included in the above discussion, these should not be interpreted as limitations on the scope of the present disclosure, but rather descriptions of features that may be specific to a particular embodiment. Certain features described in the context of a separate embodiment may also be implemented in combination in a single embodiment. On the contrary, the various features described in the context of a single embodiment may also be implemented in multiple embodiments individually or in any suitable sub-combination.

[0162] Although the present disclosure has been described in language specific to structural features and / or methodological acts, it should be understood that the present disclosure defined in the appended claims is not necessarily limited to the specific features or acts described above. Instead, the specific features and acts described above are disclosed as example forms of implementing the claims.

Claims

1. A method for communication, include: receiving, at a first device in a radio resource control (RRC) inactive state, information indicating at least a latency requirement for the first device to transmit an acknowledgement feedback for receipt of a message, the message being associated with positioning of the first device and being transmitted from a second device or a fourth device, wherein the message and the acknowledgement feedback are positioning protocol messages; as well as The transmitting of the acknowledgment feedback for the receipt of the message is performed based at least on the information without changing the RRC inactive state.

2. The method according to claim 1, wherein receiving the information include: The information is received from the second device by at least one of: message B in a 2-step random access process between the first device and the second device, message 4 in a 4-step random access procedure between the first device and the second device, or A data channel associated with a configuration grant for a small data transfer between the first device and the second device.

3. The method of claim 1 , wherein the information is received from the second device, and wherein the transmission of the confirmation feedback is performed include: determining, based on the latency requirement, a time window associated with the transmission of the acknowledgment feedback; obtaining from the information an indication of a transmission mode and resources for transmitting the confirmation feedback for the receipt of the message; determining whether the confirmation feedback is allowed to be transmitted on the resource in the transmission mode before expiration of the time window; as well as The confirmation feedback is transmitted to the second device on the resource in the transmission mode based on determining that the confirmation feedback is allowed to be transmitted on the resource in the transmission mode before the time window expires.

4. The method according to claim 3, wherein the resource comprises at least one of the following: resources associated with a random access procedure between the first device and the second device, resources associated with a configuration authorization assigned to the first device, resources associated with a control channel between the first device and the second device, or Resources dedicated to the first device transmitting the confirmation feedback.

5. The method according to claim 3, wherein the transmission mode comprises at least one of the following: Small data transmission based on configuration authorization, Small data transmission based on random access procedure, or A transmission carried by a control channel between the first device and the second device.

6. The method of claim 3, wherein the time window indicates one of the following: a response time before which the first device is required to transmit the acknowledgment; or A transmission window, within which the first device is allowed to perform multiple attempts for the transmission of the acknowledgment feedback.

7. The method according to claim 3, further comprising: include: Based on determining that the confirmation feedback is not allowed to be transmitted on the resource in the transmission mode before the expiration of the time window, an indication of the received error is transmitted to the second device.

8. The method of claim 1, wherein the information is received from the second device, and wherein the transmission of the confirmation feedback is performed include: Based on determining that the resource for transmitting the confirmation feedback for the receipt of the message is not indicated in the information, selecting the resource from a set of candidate resources pre-configured for the transmission.

9. The method according to claim 1, further comprising: include: An indication is transmitted to the second device that the first device has not requested to enter an RRC connected mode to transmit the confirmation feedback.

10. The method of claim 1, wherein the information is received from a fourth device, and wherein the transmitting of the confirmation feedback is performed include: Determining whether a candidate resource set available for the transmission meets the latency requirement; Transmitting, to the second device, a request for resources for the first device to transmit the confirmation feedback, based on determining that the candidate resource set available for the first device to transmit the confirmation feedback does not meet the latency requirement; as well as According to determining that the resource used for the first device to transmit the confirmation feedback has been allocated by the second device, the confirmation feedback is transmitted on the allocated resource.

11. The method according to claim 10, further comprising: include: According to determining that the candidate resource set available for the first device to transmit the confirmation feedback meets the latency requirement, selecting a resource for the first device to transmit the confirmation feedback from the candidate resource set; as well as The confirmation feedback is transmitted on the selected resource.

12. The method according to any one of claims 1 to 11, wherein the latency requirement comprises at least one of the following: the expected time of the confirmation feedback, or A delay threshold for providing the confirmation feedback.

13. The method according to any one of claims 1 to 11, wherein the first device comprises a terminal device, the second device comprises a network device, and the fourth device comprises a location management entity.

14. A method for communication, include: receiving, at a second device, information indicating at least a latency requirement for a first device to transmit an acknowledgment feedback for receipt of a message, the message being associated with positioning of the first device and being transmitted from a fourth device to the second device, wherein the message and the acknowledgment feedback are positioning protocol messages; and The information is transmitted to the first device.

15. The method according to claim 14, further comprising: include: Based on the information, determining resources and a transmission mode for the first device to transmit the confirmation feedback; generating an indication of resources and a transmission mode for the first device to transmit the confirmation feedback; and The indication included in the information is transmitted to the first device.

16. The method of claim 15, wherein the resource comprises at least one of the following: resources associated with a random access procedure between the first device and the second device, resources associated with a configuration authorization assigned to the first device, resources associated with a control channel between the first device and the second device, or Resources dedicated to the first device transmitting the confirmation feedback.

17. The method of claim 15, wherein the transmission mode comprises at least one of the following: Small data transmission based on configuration authorization, Small data transmission based on random access procedure, or A transmission carried by a control channel between the first device and the second device.

18. The method of claim 14, wherein transmitting the information include: The information is transmitted by at least one of the following: message B in a 2-step random access process between the first device and the second device, message 4 in a 4-step random access procedure between the first device and the second device, or A data channel associated with a configuration grant for a small data transfer between the first device and the second device.

19. The method according to claim 14, further comprising: include: An indication is received from the first device that the first device did not enter an RRC connected mode to transmit the confirmation feedback.

20. The method according to claim 14, further comprising: include: receiving, from the first device, a request for resources for the first device to transmit the confirmation feedback; The resource is allocated for the first device to transmit the confirmation feedback.

21. The method according to any one of claims 14 to 20, wherein the latency requirement comprises at least one of the following: the expected time of the confirmation feedback, or A delay threshold for providing the confirmation feedback.

22. The method according to any one of claims 14 to 20, wherein the first device comprises a terminal device, the second device comprises a network device, and the fourth device comprises a location management entity.

23. A method for communication, include: generating, at a fourth device, information indicating a latency requirement for a first device to transmit an acknowledgment feedback for receipt of a message, the message being associated with positioning of the first device and being transmitted from the fourth device or the second device to the first device, wherein the message and the acknowledgment feedback are positioning protocol messages; as well as The information is transmitted to the first device or the second device via a third device.

24. The method of claim 23, wherein transmitting the information to the first device include: The information is transmitted along with the message associated with the location of the first device.

25. The method according to claim 23 or 24, wherein the latency requirement comprises at least one of the following: the expected time of the confirmation feedback, or A delay threshold for providing the confirmation feedback.

26. The method of claim 23 or 24, wherein the first device comprises a terminal device, the second device comprises a network device, and the fourth device comprises a location management entity.

27. A device for communication, include: at least one processor; as well as at least one memory including computer program code; The at least one memory and the computer program code are configured to, together with the at least one processor, cause the apparatus to at least perform the method according to any one of claims 1 to 13, or the method according to any one of claims 14 to 22, or the method according to any one of claims 23 to 26.

28. A device for communication, include: Means for performing a method according to any one of claims 1 to 13, or a method according to any one of claims 14 to 22, or a method according to any one of claims 23 to 26.

29. A non-transitory computer-readable medium comprising program instructions for causing an apparatus to at least perform the method according to any one of claims 1 to 13, or the method according to any one of claims 14 to 22, or the method according to any one of claims 23 to 26.

Images