Methods, apparatus, equipment and media for processing positioning reference signal (PRS)

Abstract

This application discloses a method, apparatus, device, and medium for processing a Positioning Reference Signal (PRS), belonging to the field of communication technology. The PRS processing method of this application includes: a terminal receiving a PRS configuration; the terminal receiving the PRS at a first time-domain location according to the PRS configuration, and / or receiving other downlink objects at a second time-domain location; wherein the overlap relationship between the PRS and the second time-domain location is related to at least one of the following: the association relationship between the PRS and other downlink objects, and relevant information related to PRS processing; other downlink objects include at least one of the following: other downlink signals, other downlink channels; other downlink signals are signals other than the PRS; other downlink channels are channels for transmitting signals other than the PRS.

Description

Technical Field

[0001] This application belongs to the field of communication technology, and specifically relates to a PRS processing method, apparatus, device and medium. Background Technology

[0002] In R17 NR positioning enhancement, when there is no measurement gap (MG) configuration (or outside the MG), it is necessary to consider the UE performing PRS measurements within the active BWP.

[0003] To ensure low latency in PRS processing by the User Equipment (UE) and prevent it from being affected by other downlink signals, PRS generally has high priority (e.g., by defining a PRS processing window, in which PRS has high priority throughout the entire time range of the PRS processing window or within the PRS symbol time range). Thus, PRS processing (including at least one of reception, processing, or measurement) can affect or interrupt the transmission of other downlink signals or other downlink channels.

[0004] For example, depending on the impact of PRS processing on other downlink signals or other downlink channels, if the type of PRS processing (or PRS processing window) is a certain type (e.g., per UE or per band), then PRS processing will cause the interruption of downlink signals or channels on other carriers. Summary of the Invention

[0005] This application provides a PRS processing method, apparatus, device, and medium that can solve the problem of downlink signal or channel interruption on other carriers caused by PRS processing.

[0006] In a first aspect, a method for processing a PRS is provided, the method comprising: a terminal receiving a PRS configuration; the terminal receiving a PRS at a first time domain location and / or receiving other downlink objects at a second time domain location according to the PRS configuration; wherein the overlap relationship between the PRS and the second time domain location is related to at least one of the following: the association relationship between the PRS and the other downlink objects, and relevant information related to PRS processing; the other downlink objects include at least one of the following: other downlink signals, other downlink channels; the other downlink signals are signals other than the PRS; the other downlink channels are channels for transmitting signals other than the PRS.

[0007] Secondly, a PRS processing apparatus is provided, the apparatus comprising: a first receiving module for receiving a PRS configuration; and a second receiving module for receiving a PRS at a first time domain location and / or receiving other downlink objects at a second time domain location according to the PRS configuration received by the first receiving module; wherein the overlap relationship between the PRS and the second time domain location is related to at least one of the following: the association relationship between the PRS and the other downlink objects, and relevant information related to PRS processing; the other downlink objects include at least one of the following: other downlink signals, and other downlink channels; the other downlink signals are signals other than the PRS; and the other downlink channels are channels for transmitting signals other than the PRS.

[0008] Thirdly, a PRS processing method is provided, the method comprising: a first network-side device sending a PRS processing window related configuration to a second network-side device or a terminal; wherein the PRS processing window related configuration is used by the second network-side device to retrieve other downlink objects; the other downlink objects include at least one of the following: other downlink signals, other downlink channels; the other downlink signals are signals other than PRS; the other downlink channels are channels for transmitting signals other than PRS.

[0009] Fourthly, a PRS processing apparatus is provided, the apparatus comprising: a transmitting module, configured to transmit PRS processing window-related configuration to a second network-side device or a terminal; wherein the PRS processing window-related configuration is used by the second network-side device to retrieve other downlink objects; the other downlink objects include at least one of the following: other downlink signals, other downlink channels; the other downlink signals are signals other than PRS; the other downlink channels are channels for transmitting signals other than PRS.

[0010] Fifthly, a method for processing PRS is provided, the method comprising: a second network-side device receiving configuration related to a PRS processing window from a first network-side device; the second network-side device retrieving other downlink objects based on the configuration related to the PRS processing window; wherein the other downlink objects include at least one of the following: other downlink signals, other downlink channels; the other downlink signals are signals other than PRS; the other downlink channels are channels for transmitting signals other than PRS.

[0011] In a sixth aspect, a PRS processing apparatus is provided, the apparatus comprising: a receiving module, configured to receive configuration related to a PRS processing window from a first network-side device; and a second network-side device to retrieve other downlink objects based on the configuration related to the PRS processing window; wherein the other downlink objects include at least one of the following: other downlink signals, other downlink channels; the other downlink signals are signals other than PRS; and the other downlink channels are channels for transmitting signals other than PRS.

[0012] In a seventh aspect, a terminal is provided, the terminal including a processor, a memory, and a program or instructions stored in the memory and executable on the processor, wherein the program or instructions, when executed by the processor, implement the steps of the method described in the first aspect.

[0013] Eighthly, a terminal is provided, including a processor and a communication interface, wherein the communication interface is configured to receive a PRS at a first time domain location and / or receive other downlink objects at a second time domain location according to the PRS configuration; wherein the overlap relationship between the PRS and the second time domain location is related to at least one of the following: the association relationship between the PRS and the other downlink objects and relevant information related to PRS processing; the other downlink objects include at least one of the following: other downlink signals, other downlink channels; the other downlink signals are signals other than the PRS; the other downlink channels are channels for transmitting signals other than the PRS.

[0014] A ninth aspect provides a network-side device including a processor, a memory, and a program or instructions stored in the memory and executable on the processor, wherein the program or instructions, when executed by the processor, implement the steps of the method as described in the third or fifth aspect.

[0015] In a tenth aspect, a network-side device is provided, including a processor and a communication interface, wherein:

[0016] The communication interface is used to send PRS processing window related configurations to the second network-side device or terminal; wherein, the PRS processing window related configurations are used by the second network-side device to retrieve other downlink objects; the other downlink objects include at least one of the following: other downlink signals, other downlink channels; the other downlink signals are signals other than PRS; the other downlink channels are channels that transmit signals other than PRS.

[0017] And / or,

[0018] The communication interface is used to receive configuration related to the PRS processing window from the first network-side device; the second network-side device retrieves other downlink objects based on the configuration related to the PRS processing window; wherein, the other downlink objects include at least one of the following: other downlink signals, other downlink channels, wherein the other downlink signals are signals other than PRS; and the other downlink channels are channels for transmitting signals other than PRS.

[0019] Eleventhly, a readable storage medium is provided, on which a program or instructions are stored, which, when executed by a processor, implement the steps of the method described in the first aspect, or implement the steps of the method described in the first, third, or fifth aspect.

[0020] In a twelfth aspect, a chip is provided, the chip including a processor and a communication interface coupled to the processor, the processor being configured to run programs or instructions to implement the methods described in the first, third, or fifth aspects.

[0021] In a thirteenth aspect, a computer program / program product is provided, the computer program / program product being stored in a non-volatile storage medium, the program / program product being executed by at least one processor to perform the steps of the method as described in the first, third, or fifth aspect.

[0022] In this embodiment, after receiving the PRS configuration, the terminal can receive the PRS at a first time domain location and / or receive other downlink objects (i.e., at least one of other downlink signals and other downlink channels) at a second time domain location based on the PRS configuration. Since the overlap between the PRS and the second time domain location is related to at least one of the correlation between the PRS and the other downlink objects and the relevant information of the PRS processing, the impact of PRS processing on the transmission of other downlink objects can be reduced, thereby avoiding interruptions to the transmission of other downlink objects and improving system communication energy efficiency. Attached Figure Description

[0023] Figure 1 This is a possible system architecture diagram of a communication system provided in an embodiment of this application;

[0024] Figure 2 This is one of the flowcharts illustrating a PRS processing method provided in an embodiment of this application;

[0025] Figure 3 This is one of the schematic diagrams illustrating the overlap relationship between PRS and a second time-domain location provided in the embodiments of this application;

[0026] Figure 4 This is a second schematic diagram illustrating the overlap relationship between a PRS and a second time-domain location, provided in an embodiment of this application.

[0027] Figure 5 This is the third schematic diagram illustrating the overlap relationship between PRS and a second time-domain location provided in this application embodiment;

[0028] Figure 6 This is the fourth schematic diagram illustrating the overlap relationship between PRS and a second time-domain location provided in the embodiments of this application;

[0029] Figure 7 This is the fifth schematic diagram illustrating the overlap relationship between PRS and a second time-domain location provided in the embodiments of this application;

[0030] Figure 8 This is the sixth schematic diagram illustrating the overlap relationship between PRS and a second time-domain location provided in the embodiments of this application;

[0031] Figure 9 This is the seventh schematic diagram illustrating the overlap relationship between PRS and a second time-domain location provided in the embodiments of this application;

[0032] Figure 10 This is the eighth schematic diagram illustrating the overlap relationship between PRS and a second time-domain location provided in the embodiments of this application;

[0033] Figure 11 This is the ninth schematic diagram illustrating the overlap relationship between PRS and a second time-domain location provided in the embodiments of this application;

[0034] Figure 12 This is the tenth schematic diagram illustrating the overlap relationship between PRS and a second time-domain location provided in the embodiments of this application;

[0035] Figure 13 This is eleventh of the schematic diagrams illustrating the overlap relationship between PRS and a second time-domain location provided in the embodiments of this application;

[0036] Figure 14 This is the twelfth schematic diagram illustrating the overlap relationship between PRS and a second time-domain location provided in the embodiments of this application;

[0037] Figure 15 This is the thirteenth schematic diagram of the overlap relationship between PRS and the second time domain location provided in the embodiments of this application;

[0038] Figure 16 This is the fourteenth schematic diagram illustrating the overlap relationship between PRS and a second time-domain location provided in the embodiments of this application;

[0039] Figure 17 This is the fifteenth schematic diagram illustrating the overlap relationship between PRS and a second time-domain location provided in the embodiments of this application;

[0040] Figure 18 This is a second schematic flowchart of a PRS processing method provided in an embodiment of this application;

[0041] Figure 19 This is the third flowchart illustrating a PRS processing method provided in this application embodiment;

[0042] Figure 20 This is one of the structural schematic diagrams of a PRS processing device provided in the embodiments of this application;

[0043] Figure 21 This is a second schematic diagram of the structure of a PRS processing device provided in an embodiment of this application;

[0044] Figure 22 This is the third schematic diagram of a PRS processing device provided in the embodiments of this application;

[0045] Figure 23 This is the fourth schematic diagram of a PRS processing device provided in the embodiments of this application;

[0046] Figure 24 This is a schematic diagram of the structure of a communication device provided in an embodiment of this application;

[0047] Figure 25 This is a schematic diagram of the structure of a terminal provided in an embodiment of this application;

[0048] Figure 26 This is a schematic diagram of the structure of a network-side device provided in an embodiment of this application. Detailed Implementation

[0049] The technical solutions of the embodiments of this application will be clearly described below with reference to the accompanying drawings. Obviously, the described embodiments are only some, not all, of the embodiments of this application. All other embodiments obtained by those skilled in the art based on the embodiments of this application are within the scope of protection of this application.

[0050] The terms "first," "second," etc., used in the specification and claims of this application are used to distinguish similar objects and not to describe a specific order or sequence. It should be understood that such terms can be used interchangeably where appropriate so that embodiments of this application can be implemented in orders other than those illustrated or described herein, and the objects distinguished by "first" and "second" are generally of the same class, not limited in number; for example, a first object can be one or more. Furthermore, in the specification and claims, "and / or" indicates at least one of the connected objects, and the character " / " generally indicates that the preceding and following objects are in an "or" relationship.

[0051] It is worth noting that the technologies described in this application are not limited to Long Term Evolution (LTE) / LTE-Advanced (LTE-A) systems, but can also be used in other wireless communication systems, such as Code Division Multiple Access (CDMA), Time Division Multiple Access (TDMA), Frequency Division Multiple Access (FDMA), Orthogonal Frequency Division Multiple Access (OFDMA), Single-carrier Frequency-Division Multiple Access (SC-FDMA), and other systems. The terms "system" and "network" in this application are often used interchangeably, and the described technologies can be used with the systems and radio technologies mentioned above, as well as with other systems and radio technologies. The following description describes New Radio (NR) systems for illustrative purposes, and the term NR is used in most of the following description; however, these technologies can also be applied to applications other than NR systems, such as 6th generation (6G) radio systems. th Generation 6G communication system.

[0052] Figure 1This diagram illustrates a block diagram of a wireless communication system applicable to embodiments of this application. The wireless communication system includes a terminal 11 and a network-side device 12. The terminal 11 can be a UE, mobile phone, tablet computer, laptop computer (also called a notebook computer), personal digital assistant (PDA), handheld computer, netbook, ultra-mobile personal computer (UMPC), mobile internet device (MID), augmented reality (AR) / virtual reality (VR) device, robot, wearable device, vehicle-mounted device (VUE), pedestrian terminal (PUE), smart home (home appliances with wireless communication capabilities, such as refrigerators, televisions, washing machines, or furniture), etc. Wearable devices include: smartwatches, smart bracelets, smart headphones, smart glasses, smart jewelry (smart bracelets, smart chains, smart rings, smart necklaces, smart anklets, smart anklets, etc.), smart wristbands, smart clothing, game consoles, etc. It should be noted that the specific type of terminal 11 is not limited in this application embodiment. The network-side device 12 can be a base station or a core network. The base station can be referred to as a node B, evolved node B, access point, base transceiver station (BTS), radio base station, radio transceiver, basic service set (BSS), extended service set (ESS), B node, evolved B node (eNB), home B node, home evolved B node, WLAN access point, WiFi node, transmitting and receiving point (TRP), or any other suitable term in the field. As long as the same technical effect is achieved, the base station is not limited to specific technical terms. It should be noted that this application embodiment only uses a base station in an NR system as an example, but does not limit the specific type of base station.

[0053] The following will explain the technical terms involved in the technical solutions provided in the embodiments of this application:

[0054] 1. Measurement gap (MG) used in positioning.

[0055] In NR positioning, a Positioning Reference Signal (PRS) is introduced for UE positioning measurements. To complete a positioning operation, the UE needs to measure the PRS transmitted by multiple cells. Typically, to ensure high positioning accuracy, network-side equipment configures a large-bandwidth PRS (generally, the larger the PRS bandwidth, the higher the positioning accuracy). Since a large-bandwidth PRS can sometimes exceed the range of the UE's currently active Baseframe Working Device (BWP), the UE can use a Memory Gauge (MG) to measure the PRS outside the active BWP in order to measure the PRS outside the active BWP.

[0056] Before measuring PRS, the UE can send a request signaling to the serving gNB to request the configuration of the MG. The serving gNB decides how to configure the MG and then sends the MG configuration to the UE. The UE can then use the configured MG to measure PRS. If the MG is not configured, the UE is not required to measure PRS.

[0057] It is important to note that in the R-16 protocol, the PRS configuration is sent directly to the UE by the location server via LTE Positioning Protocol (LPP) signaling. The serving gNB is unaware of the specific PRS configuration information sent by neighboring cells. Therefore, when the UE needs to use the MG to measure the PRS, it needs to request the MG from the serving gNB. This request signaling carries the UE's desired MG configuration information (e.g., MG period, MG length, MG period offset, and the frequency information of the positioning frequency layer associated with the MG).

[0058] In addition, the current configuration of the MG used for positioning measurement and the procedure for PRS measurement are as follows:

[0059] 1) The LMF sends PRS configuration (i.e., location assistance data) to the UE, and the UE obtains the location assistance data.

[0060] 2) The LMF sends a location measurement request message to the UE, and the UE receives the location measurement request message.

[0061] 3) After receiving the location measurement request message, the UE will request the serving gNB to measure the PRS in the MG.

[0062] 4) The service gNB configures the appropriate MG to the UE (the UE receives the MG configuration information).

[0063] 5) The UE performs PRS measurements in the MG based on the MG configuration information.

[0064] Therefore, the UE can only request MG and receive MG configuration after receiving PRS configuration and location measurement requests. The delay between MG request and MG configuration is approximately 20ms, which is a very significant delay. Furthermore, the mismatch between the MG period and the PRS period causes an extension of the PRS measurement period, further increasing the delay.

[0065] 2. Positioning without using MG

[0066] Considering the increased latency caused by using MG (Meaning Gauge), the Rel-17 phase proposed an MG-less scheme to reduce latency. That is, when the UE measures PRS (Pulse Resistant Signal), it can measure PRS without using MG and can do so on the active DL BWP (Browser-Wide Platform). However, to ensure latency (i.e., the UE does not process other signals / channels simultaneously while processing PRS), the UE needs to process PRS within a PRS processing window. Furthermore, within the PRS processing window, PRS has a higher priority. For example, during the entire duration of the PRS processing window or at the location of the PRS symbol (depending on UE capabilities), the transmission of DL signals / channels for all or some CCs will be interrupted. Currently, the PRS processing window is still under discussion. From the UE's perspective, this PRS processing window may be implicitly indicated (e.g., through indication of the PRS time-domain location in the existing PRS configuration) or explicitly indicated.

[0067] 3. Similarities and differences between PRS processing window and MG

[0068] The PRS processing window has many similarities with MG. For example, the PRS processing window will interrupt the transmission of other DL channels / signals, so that the UE can process the PRS with full force.

[0069] The commonalities are (see Table 1 below for details):

[0070] Within the MG (Model Memory) and PRS (Pulse Responsibility) processing window, the UE can only process PRS and cannot process other DL (Digital Channel) signals / channels. The PRS processing window needs to inform the gNB (Garden Node B) so that the gNB does not schedule data within the PRS processing window. This behavior is similar to MG; the MG request needs to include the UE's desired MG-related configurations. Here, 'window' simply represents the temporal location of the PRS (in UE-specific configurations). Furthermore, 'window' can be implicitly or explicitly configured.

[0071] The differences are as follows (see Table 1 below for details):

[0072] 1) The MG has a transition time of 0.5ms before and after, during which the UE can perform operations such as RF retuning (but the transition time is included in the total length of the window); while the PRS processing window does not have this transition time.

[0073] 2) In MG, UE can measure PRS that does not match the active BWP; while PRS processing window can only measure PRS that matches the active BWP;

[0074] 3) The MG type is per FR or per UE; the PRS processing window type is not necessarily per UE, it could be per UE / PFL / carrier / band. That is, within the PRS processing window, PRS may be able to receive data simultaneously with data on another carrier.

[0075] 4) The MG time is based on the serving cell; for the PRS processing window time, if configured by the LMF, it may be based on the RSTD reference cell instead of the serving cell; if configured by the serving gNB, it may be based on the serving cell.

[0076] 5) The MG is explicitly configured for the UE; the PRS processing window may be explicit or implicit.

[0077] 6) During the PRS processing window, the timing priority of PRS and other signals may need to be considered;

[0078] 7) MG requires requests and configuration; PRS processing window should minimize requests and configuration (e.g., implicitly) to reduce latency.

[0079] 8) MG cannot contain uplinks, but PRS processing window may contain uplinks.

[0080] 9) MG does not require PRS distribution aggregation; the PRS processing window does require PRS distribution aggregation. In other words, the PRS processing window is different for different channels / UEs. Different channels or different UEs may measure different periods and durations of PRS.

[0081] Table 1

[0082]

[0083]

[0084] 4. Technical issues

[0085] As mentioned earlier, within the PRS processing window, or within the PRS symbol timeframe, PRS has a higher priority, and PRS reception can cause interruptions to other DL signals or channels. For example, when the PRS processing window type is per UE or per band, the PRS processing window will cause interruptions to DL signals / channels on other carriers. When a UE receives PRS on an active DL BWP in a serving cell, the PRS processing window needs to include the occupancy of symbols or slots caused by the expected RSTD+uncertainty (which may be related to UE capabilities).

[0086] In addition, considering that different carriers may not have the same SFN0 and SCS, it is necessary to clarify which other carriers and slots / symbols cannot transmit DL signals / channels due to the PRS processing window (or the scheduling restrictions on other DL signals / channels caused by PRS need to be clarified).

[0087] To address the aforementioned issues, embodiments of this application provide a PRS processing method, apparatus, device, and medium. After receiving a PRS configuration, the terminal can, based on this configuration, receive the PRS at a first time domain location and / or, at a second time domain location, receive other downlink objects (i.e., at least one of other downlink signals and other downlink channels). Since the overlap between the PRS and the second time domain location is related to at least one of the correlation between the PRS and the other downlink objects and the relevant information of the PRS processing, the impact of PRS processing on the transmission of other downlink objects can be reduced, thereby avoiding interruptions to the transmission of other downlink objects and improving system communication energy efficiency.

[0088] Meanwhile, when the UE receives a PRS in an active DL BWP of a certain serving cell, the received PRS specifies how other downlink signals or channels of that serving cell and other serving cells will be interrupted. This ensures that the UE and the network-side equipment have a consistent understanding and can accurately transmit and receive other downlink objects, as well as process the PRS.

[0089] 5. It should be noted that the term "received" as mentioned in this application includes at least one of the following: receiving, processing, and measuring. For example, PRS receiving includes at least one of the following: PRS receiving, PRS processing, and PRS measurement.

[0090] The processing methods, apparatus, devices, and media of PRS provided in this application will be described in detail below with reference to the accompanying drawings and through some embodiments and application scenarios.

[0091] This application provides a method for processing PRS, such as... Figure 2 As shown, the PRS processing method includes the following steps 201 and 202:

[0092] Step 201: The terminal receives the PRS configuration.

[0093] Step 202: The terminal receives the PRS at the first time domain location according to the PRS configuration, and / or receives other downlink objects at the second time domain location.

[0094] In this embodiment of the application, the aforementioned other downlink objects include at least one of the following: other downlink signals, and other downlink channels. Wherein, other downlink signals are signals other than the PRS; and other downlink channels are channels that transmit signals other than the PRS.

[0095] For example, the other downlink objects mentioned above include, but are not limited to, at least one of the following: Channel State Information (CSI) Reference Signal (CSI-RS), Synchronization Signal and PBCH block (SSB), Demodulation Reference Signal (DMRS), Phase-tracking Reference Signal (PTRS), Physical downlink shared channel (PDSCH), and Physical downlink control channel (PDCCH).

[0096] In this embodiment, the terminal measures PRS within the activated downlink BWP.

[0097] In the embodiments of this application, the aforementioned PRS can be: a set of PRS, a PRS over a period of time, a set of aggregated PRS, a PRS occasion (transmission timing), or a PRS within a PRS processing window. It should be noted that a set of PRS can come from the same or different PRS resource sets, the same or different TRPs, or the same or different frequency layers.

[0098] It should be noted that the PRS processing window involved in this application embodiment can also be represented as: PRS measurement window, PRS priority window, etc. In one example, the PRS processing window can be applied outside of MG or when MG is not configured.

[0099] Optionally, in this embodiment of the application, the above-mentioned PRS processing window is used to indicate that the PRS priority is higher than other downlink objects during the time period (or, the terminal does not need to listen to other downlink objects during the time period, or the transmission of other downlink objects is affected during the time period, or the transmission of other downlink objects is interrupted during the time period).

[0100] Optionally, in this embodiment, the aforementioned PRS can be a PRS transmitted by at least one TRP. Furthermore, the at least one TRP can originate from the same frequency layer or different frequency layers.

[0101] Optionally, in the embodiments of this application, the time unit corresponding to the first time domain position is one of a symbol, a time slot, or a subframe.

[0102] Optionally, in the embodiments of this application, the time unit or granularity corresponding to the first time domain location can be determined by at least one of the following: network indication, protocol agreement, terminal selection.

[0103] Optionally, in the embodiments of this application, the time unit corresponding to the second time domain position is one of a symbol, a time slot, or a subframe.

[0104] Optionally, in the embodiments of this application, the time unit or granularity corresponding to the second time domain location can be determined by at least one of the following: network indication, protocol agreement, terminal selection.

[0105] Optionally, in the embodiments of this application, the time units or granularity of the first time domain position and the second time domain position may be the same or different, and the embodiments of this application do not limit this.

[0106] In some possible embodiments, terminal selection refers to selection based on terminal capabilities. For example, if the terminal supports symbol-level, slot-level, or subframe-level receive / process / buffer (buffer) PRS, then the unit of the first time-domain position is symbol, slot, or subframe.

[0107] In some possible embodiments, the terminal reports its capabilities to the network-side device.

[0108] In some possible embodiments, if the terminal supports multiple receive / process / buffer PRS capabilities, the network side may further indicate the unit of the first time domain location.

[0109] Optionally, in the embodiments of this application, the PRS and other downlink objects are located in the same or different frequency domain positions.

[0110] Optionally, in the embodiments of this application, the overlap relationship between the above-mentioned PRS and the second time-domain location is related to at least one of the following:

[0111] The relationship between PRS and other downlink objects

[0112] PRS processes related information.

[0113] The overlap relationship between the PRS and the second time domain location includes: the PRS and the second time domain location overlap, or the PRS and the second time domain location do not overlap.

[0114] Optionally, in this embodiment of the application, the association relationship between the PRS and other downlink objects includes at least one of the following:

[0115] Priority relationship between PRS and other downlink objects;

[0116] Frequency domain positional relationship between PRS and other downlink objects.

[0117] Optionally, in this embodiment of the application, the relevant information of the above-mentioned PRS processing includes at least one of the following:

[0118] The first type of PRS processing capability;

[0119] PRS processing type.

[0120] In some possible embodiments, the first PRS processing capability described above is the terminal's ability to process PRS when there is no MG.

[0121] In some possible embodiments, the type of the first PRS processing capability described above includes one of the following:

[0122] Processing capacity per terminal (Per terminal);

[0123] Processing capacity per FR;

[0124] Processing capacity per band;

[0125] Processing capacity per carrier;

[0126] Processing capacity of each resource block (RB).

[0127] It should be noted that the type of the first PRS processing capability mentioned above is related to the degree of influence of 'processing downlink objects in other frequency domain locations based on PRS', which is different from the general processing type.

[0128] In some possible embodiments, the above-mentioned PRS processing type is the type of PRS processed by the terminal when there is no MG;

[0129] The PRS processing type includes at least one of the following:

[0130] Per terminal type;

[0131] Per FR type;

[0132] Types of Per bands;

[0133] Types of Per Carrier;

[0134] Per RB block type.

[0135] It should be noted that the above PRS processing type can also be a PRS processing window type.

[0136] It should be noted that the above PRS processing type is related to the 'impact of downlink objects at other frequency domain locations based on PRS processing', and is different from general processing types.

[0137] For example, the interpretations of the processing capabilities per UE, per FR, per band, per carrier, and per RB block mentioned above include the following:

[0138] In some possible embodiments, the processing capability of the Per UE mentioned above refers to the ability of PRS processing to interrupt (or affect) the transmission of all other DL objects at the PRS occupancy time or the first time domain location.

[0139] In some possible embodiments, the processing capability of the Per FR mentioned above refers to the ability of PRS processing to interrupt (or affect) the transmission of other DL objects within the FR during PRS occupancy time or at the first time domain location.

[0140] In some possible embodiments, the processing capability of the Per band mentioned above refers to the ability of the PRS to interrupt (or affect) the transmission of all other DL objects within the band during the PRS occupancy time or at the first time domain location.

[0141] In some possible embodiments, the processing capability of the Per carrier mentioned above refers to the ability of the PRS to interrupt (or affect) the transmission of all other DL objects within the carrier during the PRS occupancy time or at the first time domain location.

[0142] In some possible embodiments, the processing capability of the Per RB block mentioned above refers to the ability of PRS processing to interrupt (or affect) the transmission of all other DL objects within the RB block during PRS occupancy time or at the first time domain location.

[0143] or,

[0144] In some possible embodiments, the processing capability of the above Per UE refers to the ability of the PRS to have a higher priority than the DL object and to interrupt (or affect) the transmission of all other DL objects at the PRS occupancy time or the first time domain location.

[0145] In some possible embodiments, the processing capability of the Per FR mentioned above refers to the ability of the PRS to have a higher priority than the DL object and to interrupt (or affect) the transmission of other DL objects within the FR that have PRS occupancy time or the first time domain location.

[0146] In some possible embodiments, the processing capability of the Per band mentioned above refers to the ability of the PRS to have a higher priority than the DL object and to interrupt (or affect) the transmission of all other DL objects within the band during the PRS occupancy time or at the first time domain position.

[0147] In some possible embodiments, the processing capability of the above-mentioned Per carrier refers to the ability of the PRS to have a higher priority than the DL object and to interrupt (or affect) the transmission of all other DL objects within the carrier during the PRS occupancy time or at the first time domain location.

[0148] In some possible embodiments, the processing capability of the Per RB block refers to the ability of the PRS to have a higher priority than the DL object and to interrupt (or affect) the transmission of all other DL objects within the RB block during the PRS occupancy time or at the first time domain position.

[0149] or,

[0150] In some possible embodiments, the processing type described above for Per UE refers to: PRS processing interrupts (or affects) the transmission of all other DL objects at the PRS occupancy time or the first time domain location.

[0151] In some possible embodiments, the processing type of Per FR mentioned above refers to: PRS processing interrupts (or affects) the transmission of other DL objects within the FR during PRS occupancy time or at the first time domain location.

[0152] In some possible embodiments, the processing type of the Per band mentioned above refers to: PRS processing interrupts (or affects) the transmission of all other DL objects within the band during PRS occupancy time or at the first time domain location.

[0153] In some possible embodiments, the processing type of the Per carrier mentioned above refers to: PRS processing interrupts (or affects) the transmission of all other DL objects within the carrier during the PRS occupancy time or at the first time domain location.

[0154] In some possible embodiments, the processing type of the Per RB block mentioned above refers to: PRS processing interrupts (or affects) the transmission of all other DL objects within the RB block during the PRS occupancy time or at the first time domain location.

[0155] or,

[0156] In some possible embodiments, the processing type per UE mentioned above refers to: PRS having a higher priority than the DL object, and PRS processing interrupting (or affecting) the transmission of all other DL objects at the PRS occupancy time or the first time domain location.

[0157] In some possible embodiments, the processing type of Per FR mentioned above refers to: PRS having a higher priority than the DL object, and PRS processing interrupting (or affecting) the transmission of other DL objects within the FR that occupy PRS time or the first time domain position.

[0158] In some possible embodiments, the processing type of the above Per band refers to: PRS has a higher priority than the DL object, and PRS processing interrupts (or affects) the transmission of all other DL objects within the band that have PRS occupancy time or the first time domain position.

[0159] In some possible embodiments, the processing type per carrier mentioned above refers to: the PRS has a higher priority than the DL object, and the PRS processing interrupts (or affects) the transmission of all other DL objects within the carrier during the PRS occupancy time or at the first time domain position.

[0160] In some possible embodiments, the processing type of the Per RB block mentioned above refers to: the PRS has a higher priority than the DL object, and the PRS processing interrupts (or affects) the transmission of all other DL objects within the RB block at the PRS occupancy time or the first time domain position.

[0161] Optionally, in this embodiment, the PRS processing type is related to the type of the first PRS processing capability.

[0162] In some possible embodiments, the priority relationship between the PRS and other downlink objects is that the PRS has a higher priority than the other downlink objects. Furthermore, the priority between the PRS and other downlink objects can be determined by at least one method, such as protocol agreement, network indication, or terminal selection.

[0163] In some possible embodiments, the frequency domain positional relationship between the PRS and other downlink objects includes: the frequency domain position of the other downlink objects is the same as the frequency domain position of the PRS; or, the frequency domain position of the other downlink objects is different from the frequency domain position of the PRS.

[0164] In some possible embodiments, the frequency domain location of other downlink objects is the same as the frequency domain location of the PRS, including at least one of the following:

[0165] PRS and other downlink objects are on the same carrier;

[0166] PRS and other downlink objects are located in the same BWP;

[0167] PRS and other downlink objects are located at overlapping RB positions.

[0168] In some possible embodiments, the frequency domain location of other downlink objects differs from the frequency domain location of the PRS, including at least one of the following:

[0169] PRS and other downlink objects are located on carriers in different frequency ranges of FR;

[0170] PRS and other downlink objects are carriers in different frequency bands within the same frequency range FR;

[0171] PRS and other downlink objects are located on carriers in the same frequency band but different carriers;

[0172] PRS and other downlink objects are located on non-overlapping RB positions in the same BWP on the same carrier;

[0173] PRS and other downlink objects are located on carriers in different frequency bands;

[0174] The carrier of the PRS includes: the carrier that receives the PRS, or the carrier in which the PRS is located, or the carrier in which the active DL BWP that receives the PRS is located.

[0175] Optionally, in the embodiments of this application, the overlap relationship between the PRS and the second time domain position includes: the PRS overlaps with the second time domain position, and the PRS does not overlap with the second time domain position.

[0176] Optionally, in this embodiment, if the PRS and the second time-domain location do not overlap, the transmission of other downlink objects at the time-domain location corresponding to the PRS is interrupted. Here, the aforementioned non-overlap can also be understood as a scheduling restriction on other downlink objects.

[0177] Optionally, in the embodiments of this application, the non-overlapping of the PRS and the second time domain position can also be expressed as: the reception (or transmission) of other downlink objects is affected by the PRS reception (or processing, measurement) (e.g., interrupted by PRS reception / processing / measurement); or affected by the PRS reception (or processing, measurement) (e.g., interrupted by PRS reception / processing / measurement), and the terminal can only receive other downlink objects at a time domain position that does not overlap with the PRS.

[0178] Optionally, in the embodiments of this application, when the PRS overlaps with the second time domain position, the frequency domain position of the PRS is different from that of other downlink objects, and the transmission of other downlink objects is allowed at the time domain position corresponding to the PRS.

[0179] Optionally, in the embodiments of this application, the overlap relationship between the aforementioned PRS and other downlink objects is determined based on at least one of the following methods:

[0180] If the PRS has a higher priority than other downlink objects, and the frequency domain positional relationship between the PRS and other downlink objects satisfies the limitation of the first PRS processing capability type or the frequency domain range corresponding to the PRS processing type, then the PRS does not overlap with other downlink objects; in other words, during the time occupied by the PRS or the time of the first time domain position, the UE does not want to receive other downlink objects, or the transmission of other downlink objects is interrupted.

[0181] If the PRS has a higher priority than other downlink objects, and the frequency domain positional relationship between the PRS and other downlink objects does not meet the limitation of the type of processing capability of the first PRS or the frequency domain range corresponding to the PRS processing type, then the PRS can overlap with other downlink objects.

[0182] If the PRS priority is equal to the other downlink objects, and the frequency domain positional relationship between the PRS and the other downlink objects does not satisfy the limitation of the type of the first PRS processing capability or the frequency domain range corresponding to the PRS processing type, then the PRS and the other downlink objects may overlap.

[0183] If the PRS has a lower priority than the other downlink objects, and the frequency domain positional relationship between the PRS and the other downlink objects does not satisfy the limitation of the type of the first PRS processing capability or the frequency domain range corresponding to the PRS processing type, then the PRS and the other downlink objects may overlap.

[0184] If the PRS priority is equal to the other downlink objects, and the frequency domain positional relationship between the PRS and the other downlink objects satisfies the limitation of the type of the first PRS processing capability or the frequency domain range corresponding to the PRS processing type, then the PRS and the other downlink objects can overlap; in other words, within the frequency range limitation, the UE can simultaneously receive the PRS and the other downlink objects.

[0185] If the PRS has a lower priority than the other downlink objects, and the frequency domain positional relationship between the PRS and the other downlink objects satisfies the limitation of the type of the first PRS processing capability or the frequency domain range corresponding to the PRS processing type, then the PRS and the other downlink objects can overlap; in other words, within the frequency range limitation, the UE can simultaneously receive the PRS and the other downlink objects.

[0186] If the PRS priority is equal to that of the other downlink objects, and the frequency domain position relationship between the PRS and the other downlink objects satisfies the limitation of the type of the first PRS processing capability or the frequency domain range corresponding to the PRS processing type, then the PRS and the other downlink objects do not overlap; in other words, within the frequency range limitation, during the time period of the second time domain position corresponding to the other downlink objects, the UE does not expect to receive the PRS, or the PRS reception is interrupted, or the PRS is dropped.

[0187] If the PRS has a lower priority than the other downlink objects, and the frequency domain position relationship between the PRS and the other downlink objects satisfies the limitation of the type of the first PRS processing capability or the frequency domain range corresponding to the PRS processing type, then the PRS and the other downlink objects do not overlap; in other words, within the frequency range limitation, during the time period of the second time domain position corresponding to the other downlink objects, the UE does not expect to receive the PRS, or the PRS reception is interrupted, or the PRS is dropped.

[0188] If the frequency domain position relationship between the PRS and the other downlink objects is the same, then the PRS and the other downlink objects can overlap.

[0189] If the frequency domain position relationship between the PRS and the other downlink objects is the same, then the PRS and the other downlink objects do not overlap.

[0190] If the frequency domain positional relationship between the PRS and the other downlink objects is different, then the PRS and the other downlink objects may overlap.

[0191] If the frequency domain positional relationship between the PRS and the other downlink objects is different, then the PRS and the other downlink objects do not overlap.

[0192] In one example, the 'satisfying the frequency range limitation' may include at least one of the following: the UE processing capability or PRS processing type is per band, and the other downlink objects are located in the same band as the PRS (the frequency range is limited to this band); or, the UE processing capability or PRS processing type is per FR, and the other downlink objects are located in the same FR as the PRS (the frequency range is limited to this FR); or, the UE processing capability or PRS processing type is per carrier, and the other downlink objects are located in the same carrier (the frequency range is limited to this carrier) or BWP as the PRS; or, the UE processing capability or PRS processing type is per RB block, and the other downlink objects are located in the same RB block as the PRS (the frequency range is limited to this RB block); or, the UE processing capability or PRS processing type is per UE, and the frequency domain position relationship between the PRS and other downlink objects is not limited (the frequency range is limited to all frequency domain positions).

[0193] Regarding the non-overlapping of PRS and second time domain locations:

[0194] In some possible embodiments, the non-overlapping of the PRS with the second time-domain location includes at least one of the following:

[0195] The first time domain location and the second time domain location do not overlap.

[0196] The time occupied by PRS does not overlap with the second time domain location.

[0197] In some possible embodiments, the PRS and the second time-domain location are not overlapped in a manner determined based on at least one of the following: network indication, protocol agreement, UE selection.

[0198] In some possible embodiments, where the PRS and the second time-domain location do not overlap, meaning the first time-domain location and the second time-domain location do not overlap, the aforementioned non-overlapping of the first time-domain location and the second time-domain location includes at least one of the following:

[0199] When other downlink objects are located on the same carrier (or serving cell) as the PRS, or when other downlink objects are located on the same BWP as the PRS, the first time domain location and the second time domain location do not overlap;

[0200] If other downlink objects are located on different carriers (or serving cells) from the PRS, then the second time-domain location does not contain the first time unit if the boundary of the first time-domain location at least partially overlaps with the first time unit (i.e., a time unit, such as a symbol, slot, or subframe) of the carriers associated with other downlink objects.

[0201] Of course, apart from the boundary, the intermediate positions of the first time domain location and the second time domain location will not overlap. For example, if the second time domain location may contain the time units adjacent to the first time unit (e.g., symbol, slot, or subframe), and the adjacent time units do not overlap with the first time domain location at all.

[0202] For example, if other downlink objects are located on different carriers (or serving cells) from the PRS, and the boundary of the first time-domain location at least partially overlaps with a time unit (e.g., symbol, slot, or subframe) of a carrier (or serving cell) associated with other downlink signals and / or channels (or the boundary falls in the middle of a symbol, slot, or subframe of another carrier (or serving cell), then the second time-domain location does not include that time unit (or, no other DL signals / channels are transmitted in that time unit).

[0203] For example, if the starting boundary of the first time-domain position at least partially overlaps with a time unit (e.g., symbol, slot, or subframe) of a carrier (or serving cell, which is the carrier of other downlink objects) (or the boundary falls in the middle of a symbol, slot, or subframe of that carrier (or serving cell), then the second time-domain position does not include that time unit and the preceding adjacent time unit (or, the preceding L adjacent time units); and / or, if the ending boundary of the time occupied by the PRS at least partially overlaps with a time unit (e.g., symbol, slot, or subframe) of that carrier (or serving cell) (or the boundary falls in the middle of a symbol, slot, or subframe of that carrier (or serving cell), then the second time-domain position does not include that time unit and the following adjacent time unit (or, the following K adjacent time units). Here, L and K can be determined by at least one of protocol agreement, network indication, or terminal selection. Optionally, L = K.

[0204] For example, the time unit mentioned above is Symbol, and slot or subframe can be determined by at least one of the following: protocol agreement, network instruction, or terminal selection.

[0205] For example, the SFN0 of the carrier (or serving cell) associated with other downlink objects may be the same as or different from the SFN0 of the carrier (or serving cell) of the PRS.

[0206] For example, the SFN0 of the carrier (or serving cell) associated with other downlink objects may be synchronized or not synchronized with the SFN0 of the carrier (or serving cell) of the PRS.

[0207] For example, the SCS of other downlink objects may be the same as or different from the SCS of the active BWP receiving the PRS.

[0208] Optionally, if the UE does not expect to receive PRS, or PRS reception is interrupted, or PRS is dropped during the time period of the second time domain location corresponding to other downlink objects, the non-overlapping of the first time domain location and the second time domain location includes at least one of the following:

[0209] When other downlink objects are located on the same carrier (or serving cell) as the PRS, or when other downlink objects are located on the same BWP as the PRS, the first time domain location and the second time domain location do not overlap;

[0210] If other downlink objects and the PRS are located on different carriers (or serving cells), then the first time domain location does not contain the first time unit if the boundary of the second time domain location at least partially overlaps with the target time unit (i.e., a time unit such as a symbol, slot, or subframe) of the carrier receiving the PRS. In other words, the UE does not expect to process the PRS in the target time unit.

[0211] Of course, apart from the boundary, the midpoint between the first time domain position and the second time domain position will not overlap.

[0212] In some possible embodiments, when the PRS and the second time domain location do not overlap, meaning the time occupied by the PRS does not overlap with the second time domain location, the non-overlapping of the time occupied by the PRS and the second time domain location includes at least one of the following:

[0213] If other downlink objects are located on the same carrier as the PRS, or if other downlink objects are located on the same BWP as the PRS, then the second time domain location does not include the third time unit if the boundary of the time occupied by the PRS at least partially overlaps with the third time unit of the carrier.

[0214] If other downlink objects are located on different carriers (or on different BWPs) from the PRS, the second time-domain location does not include the fourth time unit if the boundary of the time occupied by the PRS at least partially overlaps with the fourth time unit of the carrier associated with other downlink objects.

[0215] Of course, apart from the boundary, the time occupied by PRS will not overlap with the middle position of the second time domain location.

[0216] For example, other downlink objects are located on the same carrier (or serving cell) and the same BWP as the PRS. Then, if the boundary of the time occupied by the PRS at least partially overlaps with a time unit (e.g., symbol, slot, or subframe) of the carrier (or serving cell) (or the boundary falls in the middle of a symbol, slot, or subframe of the carrier (or serving cell), then the second time-domain location does not include that time unit (or, no other DL signals / channels are transmitted on that time unit).

[0217] For example, if other downlink objects are located on different carriers (or serving cells) from the PRS, and the boundary of the time occupied by the PRS at least partially overlaps with a certain time unit (e.g., symbol, slot, or subframe) of the carrier (or serving cell) associated with the other downlink object (or the boundary falls in the middle of a certain symbol, slot, or subframe of the other carrier (or serving cell), then the second time-domain location does not include that time unit (or, no other DL signals / channels are transmitted in that time unit).

[0218] For example, if the starting boundary of the time occupied by the PRS at least partially overlaps with a time unit (e.g., symbol, slot, or subframe) of a carrier (or serving cell, which is the carrier of other downlink objects) (or the boundary falls in the middle of a symbol, slot, or subframe of that carrier (or serving cell), then the second time-domain position does not include that time unit and the preceding adjacent time unit (or, the preceding N adjacent time units); and / or, if the ending boundary of the time occupied by the PRS at least partially overlaps with a time unit (e.g., symbol, slot, or subframe) of that carrier (or serving cell) (or the boundary falls in the middle of a symbol, slot, or subframe of that carrier (or serving cell), then the second time-domain position does not include that time unit and the following adjacent time unit (or, the following M adjacent time units). Where N and M are positive integers. N and M can be determined by at least one of the following: protocol agreement, network indication, or terminal selection. Optionally, N = M.

[0219] For example, the second time-domain location may include the time units adjacent to the third or fourth time unit (e.g., symbol, slot, or subframe), and the adjacent time units do not overlap with the first time-domain location at all.

[0220] For example, the time unit mentioned above is Symbol, and slot or subframe can be determined by at least one of the following: protocol agreement, network instruction, or terminal selection.

[0221] For example, the SFN0 of the carrier (or serving cell) associated with other downlink objects may be the same as or different from the SFN0 of the carrier (or serving cell) of the PRS.

[0222] For example, the SFN0 of the carrier (or serving cell) associated with other downlink objects may be synchronized or not synchronized with the SFN0 of the carrier (or serving cell) of the PRS.

[0223] For example, the SCS of other downlink objects may be the same as or different from the SCS of the active BWP receiving the PRS.

[0224] In some possible embodiments, the unit (or granularity) of the time occupied by PRS is one of the following: ns, us, ms, s, Ts, Tc, UTC, symbol, or slot. Furthermore, the unit (or granularity) of the time occupied by PRS can be determined by at least one of network indication, protocol agreement, or terminal selection.

[0225] In some possible embodiments, the time occupied by the PRS only considers the PRS time-domain location and uncertainty. However, after considering the PRS time-domain location and uncertainty, if the PRS start time and / or end time happen to be in the middle of a certain time unit, then that time unit can be included in the first time-domain location.

[0226] In some possible embodiments, the time occupied by the PRS mentioned above includes the time corresponding to the PRS processing window.

[0227] In some possible embodiments, the time occupied by the PRS mentioned above includes: absolute time (e.g., UTC time) or relative time;

[0228] The relative time includes at least one of the following:

[0229] The relative time of PRS with respect to the first serving cell SFN0;

[0230] PRS is relative to a specific or designated time point in the first serving cell;

[0231] The relative time of PRS to a certain point in the timing of the first serving cell;

[0232] PRS is the relative time of a predefined / preconfigured absolute point in time.

[0233] It should be noted that the aforementioned first service cell can be determined by at least one method, such as network instruction, protocol agreement, or terminal selection.

[0234] In one example, the first serving cell mentioned above can be the serving cell where the active BWP for the terminal to receive the PRS is located.

[0235] In some possible embodiments, the time occupied by the above-mentioned PRS is related to at least one of the following:

[0236] PRS time-domain location configuration

[0237] The TRP for sending the PRS is offset from the SFN0 of the serving cell and / or reference cell.

[0238] The SFN0 offset between the serving cell and the reference cell (e.g., nr-DL-PRS-SFN0-Offset).

[0239] The TRP for sending the PRS is related to the expected RSTD of the serving cell and / or reference cell (e.g., nr-DL-PRS-ExpectedRSTD).

[0240] The uncertainty of the TRP sending the PRS and the expected RSTD of the serving cell and / or reference cell (e.g., nr-DL-PRS-ExpectedRSTD-Uncertainty).

[0241] Reference cell TRP and serving cell TRP expected RSTD

[0242] The expected RSTD uncertainty of the reference cell TRP and the serving cell TRP,

[0243] Second PRS processing capability

[0244] PRS processing time

[0245] SFN0 service time for the community

[0246] SCS serving the community.

[0247] In some possible embodiments, the second PRS processing capability described above includes the first PRS processing capability described above.

[0248] In some possible embodiments, when the PRS does not overlap with the second time domain location, the priority of the PRS also needs to be considered.

[0249] For example, if the PRS has a high priority, the enable scheduling restriction (within the frequency range specified by the processing capability or processing type, no other channels / signals can be received at any frequency location within the time domain location range of the PRS).

[0250] It should be noted that the PRS has the same priority as other downlink objects and is subject to a disabled scheduling restriction, meaning that the PRS will not interrupt the transmission of other downlink channels or signals within the frequency domain range specified by the processing capability or processing type. For example, when the frequency domain positions are different, within the specified frequency domain range, the UE can simultaneously receive the PRS and other downlink signals or channels; or, when the frequency domain positions are different, within the specified frequency domain range, the UE may wish to receive other downlink signals or signals without receiving the PRS.

[0251] For example, PRS has low priority and disables scheduling restrictions, meaning that PRS does not interrupt the transmission of other downlink channels or signals within the frequency domain range specified by processing capability or processing type. For instance, when the frequency domain positions are different, within the specified frequency domain range, the UE can simultaneously receive PRS and other downlink signals or channels; or, when the frequency domain positions are different, within the specified frequency domain range, the UE expects to receive other downlink signals or signals without receiving PRS.

[0252] Furthermore, the priority information or terminal behavior of the aforementioned PRS can be determined by at least one of the following: network indication (first network-side device or second network-side device), protocol agreement, or terminal selection.

[0253] In some possible embodiments, when the PRS does not overlap with the second time-domain location, the frequency-domain relationship between the PRS and other downlink objects includes at least one of the following:

[0254] Other downlink objects are carriers in different frequency ranges (FR) from the PRS;

[0255] Other downlink objects are carriers in different frequency bands within the same frequency range as the PRS;

[0256] Other downlink objects are on different carriers in the same frequency band as PRS;

[0257] Other downlink objects are carriers located in different frequency bands from the PRS;

[0258] Other downlink objects and PRS are located on the same BWP on the same carrier, with non-overlapping RB positions;

[0259] Other downlink objects and PRS are located on the same BWP on the same carrier, with overlapping RB positions.

[0260] For example, when the PRS does not overlap with the second time domain location, it further includes at least one of the following embodiments:

[0261] Other downlink objects and PRS are located on carriers in different FRs, and the PRS does not overlap with the second time domain location; one possible implementation is that other downlink objects in different FRs are interrupted by PRS reception, for example, outside the MG (or without the MG), the terminal supports per-UE (PRS processing window) processing capability, or outside the MG (or without the MG), the PRS processing type is per-UE, or the PRS processing window type is per-UE.

[0262] Other downlink objects are located on carriers in different bands of the same FR as the PRS, and the PRS does not overlap with the second time domain location; one possible implementation is that other downlink objects in different bands of the same FR are interrupted by PRS reception, for example, outside the MG (or without the MG), the terminal supports per-FR (PRS processing window) processing capability, or outside the MG (or without the MG), the PRS processing type is per-FR, or the PRS processing window type is per-FR;

[0263] Other downlink objects are located in the same band but on different carriers as the PRS, and the PRS does not overlap with the second time domain location; one possible implementation is that other downlink objects in the same band but on different carriers are interrupted by PRS reception, for example, outside the MG (or without the MG), the terminal supports per-band (PRS processing window) processing capability, or outside the MG (or without the MG), the PRS processing type is per-band, or the PRS processing window type is per-band;

[0264] Other downlink objects are located on carriers in different bands from the PRS, and the PRS does not overlap with the second time domain location; one possible implementation is that other downlink objects in different bands are interrupted by PRS reception, for example, outside the MG (or without the MG), the terminal supports per-UE or per-FR (PRS processing window) processing capability, or outside the MG (or without the MG) the PRS processing type is per-band, or the PRS processing window type is per-band;

[0265] Other downlink objects are located in the same carrier and BWP as PRS, with non-overlapping RB positions, and PRS does not overlap with the second time domain position; one possible implementation is: other downlink objects in the same carrier are interrupted by PRS reception, for example, outside of MG (or without MG), the terminal supports per-carrier (or per CC (component carrier), perserving cell) (PRS processing window) processing capability, or outside of MG (or without MG) the PRS processing type is per-carrier, or the PRS processing window type is per-carrier;

[0266] Other downlink objects are located on the same carrier and in the same BWP as the PRS, with overlapping RB positions, and the PRS does not overlap with the second time domain position; one possible implementation is: other downlink objects at the same RB position are interrupted by PRS reception, outside the MG (or without the MG), the terminal supports per RB or RB block (PRS processing window) processing capability, or outside the MG (or without the MG) the PRS processing type is per RB or RB block, or the PRS processing window type is per RB or RB block.

[0267] Regarding the overlap between the PRS and the second time domain location:

[0268] In some possible embodiments, when the PRS overlaps with a second time-domain location, the frequency-domain relationship between the PRS and other downlink objects includes at least one of the following:

[0269] Other downlink objects are carriers in different frequency ranges from the PRS;

[0270] Other downlink objects are carriers in different frequency bands within the same frequency range as the PRS.

[0271] Other downlink objects are on different carriers in the same frequency band as PRS;

[0272] Other downlink objects are carriers located in different frequency bands from the PRS;

[0273] Other downlink objects and PRS are located on the same BWP on the same carrier, with non-overlapping RB positions.

[0274] For example, the RB positions mentioned above could be X consecutive RBs occupied by the PRS, and Y consecutive RBs occupied by other signals / channels, with X and Y not overlapping. It should be noted that the RB positions here can also be represented as RB blocks, where an RB block contains multiple consecutive PRBs.

[0275] For example, the aforementioned non-overlapping RB locations can also be represented as PRS occupying different RB blocks from other signals / channels.

[0276] For example, when the upper PRS overlaps with the second time domain location, it also includes at least one of the following implementations:

[0277] Other downlink objects are located on carriers of different FRs from the PRS, and the PRS overlaps with the second time domain location; one possible implementation is that other downlink objects in different FRs are not affected by PRS processing. For example, outside the MG (or without the MG), the terminal supports per carrier, per band, or per FR (PRS processing window) processing capabilities, or outside the MG (or without the MG), the PRS processing type is per carrier, per band, or per FR, or the processing window type is per carrier, per band, or per FR.

[0278] Other downlink objects are located on carriers in the same FR but different bands as the PRS, and the PRS overlaps with the second time domain location; one possible implementation is that other downlink objects in the same FR but different bands are not affected by PRS processing. For example, outside the MG (or without the MG), the PRS processing window capability is supported for per carrier or per band, or outside the MG (or without the MG), the PRS processing type is per carrier or per band, or the processing window type is per carrier or per band.

[0279] Other downlink objects are located in the same band but on different carriers as the PRS, and the PRS overlaps with the second time domain location; one possible implementation is that other downlink objects in the same band but on different carriers are not affected by PRS processing. For example, outside the MG (or when there is no MG), the terminal supports per-carrier PRS processing window processing capability, or outside the MG (or when there is no MG), the PRS processing type is per-carrier, or the processing window type is per-carrier.

[0280] Other downlink objects are located on carriers in different bands from the PRS, and the PRS overlaps with the second time domain location; one possible implementation is that other downlink objects in different bands are not affected by PRS processing, for example, outside the MG (or without the MG), the terminal supports PRS processing window processing capabilities per-carrier, per band or per FR, or PRS processing type outside the MG (or without the MG).

[0281] Other downlink objects are located on the same carrier and in the same BWP as the PRS, with non-overlapping RB positions, and the PRS overlaps with the second time domain position; one possible implementation is that other downlink objects at non-overlapping RB positions on the same carrier are not affected by PRS processing, for example, outside of MG (or without MG), the terminal supports PRS processing window processing capability per RB block, or outside of MG (or without MG) PRS processing type.

[0282] It should be noted that terminal support capabilities are categorized into at least one of the following: per RB / RB block, per carrier, per band, and per FR. Specifically, if a terminal supports per RB / RB block capabilities, it naturally supports per carrier, per band, and per FR capabilities; if a terminal supports per carrier capabilities, it naturally supports per band and per FR capabilities; and if a terminal supports per band capabilities, it naturally supports per FR capabilities.

[0283] In some possible embodiments, the overlap of the PRS with the second time domain location includes at least one of the following: the first time domain location overlaps with the second time domain location, and the time occupied by the PRS overlaps with the second time domain location.

[0284] In some possible embodiments, the PRS overlaps with the second time-domain location, meaning that the reception (or transmission) of other downlink objects is unaffected by the PRS. In other words, the priority of other downlink objects is higher than or equal to that of the PRS.

[0285] Optionally, in this embodiment of the application, step 202, "receiving PRS at the first time domain location," may include step 202a:

[0286] Step 202a: The terminal receives PRS at a first time domain location based on at least one of the timing information of the serving cell and the time unit of the serving cell occupied by the subcarrier interval.

[0287] It is understandable that when a terminal receives a PRS at the first time domain location, it can receive it based on the timing of the serving cell and / or the symbol, slot, or subframe of the serving cell occupied by the subcarrier interval.

[0288] It should be noted that the aforementioned serving cell can also be a carrier or component carrier.

[0289] In some possible embodiments, the serving cell is the serving cell where the active DL BWP receiving the PRS is located; and / or, the subcarrier spacing is the subcarrier spacing corresponding to the active DL BWP receiving the PRS.

[0290] Optionally, in embodiments of this application, the first time-domain location is associated with at least one of the following:

[0291] PRS time-domain location configuration

[0292] The TRP for sending the PRS is offset from the SFN0 of the serving cell and / or reference cell.

[0293] The SFN0 offset between the serving cell and the reference cell (e.g., nr-DL-PRS-SFN0-Offset).

[0294] The TRP that sends the PRS is associated with the expected RSTD of the serving cell and / or reference cell (e.g., nr-DL-PRS-ExpectedRSTD).

[0295] The uncertainty of the TRP sending the PRS and the expected RSTD of the serving cell and / or reference cell (e.g., nr-DL-PRS-ExpectedRSTD-Uncertainty).

[0296] Reference cell TRP and serving cell TRP expected RSTD

[0297] The expected RSTD uncertainty of the reference cell TRP and the serving cell TRP,

[0298] Second PRS processing capability

[0299] PRS processing time

[0300] SFN0 service time for the community

[0301] SCS serving the community.

[0302] In some possible embodiments, the time-domain location configuration of the PRS includes, but is not limited to, one of the following: PRS period, period offset, PRS repetition, PRS subcarrier spacing, PRS pattern, and PRS processing window configuration.

[0303] In some possible embodiments, the aforementioned SFN0 offset may be a subframe-level offset (e.g., coarse-grained, offset in UE-assisted positioning, etc.) or a UTC-level offset (e.g., fine-grained, offset in UE-based positioning).

[0304] In some possible embodiments, the second PRS processing capability described above includes at least one of the following:

[0305] The ability to handle PRS;

[0306] PRS has the capability to handle window-related tasks.

[0307] In some possible embodiments, the above-described ability to process PRS includes at least one of the following:

[0308] Slot-level or symbol-level processing capabilities;

[0309] PRS processing capacity (N, T).

[0310] In some possible embodiments, the capabilities related to the PRS processing window mentioned above include at least one of the following: a first capability and a second capability; wherein the first capability includes PRS priority over all other downlink objects among all symbols within the PRS processing window; and the second capability includes PRS priority over other downlink objects only among PRS symbols within the PRS processing window. The terminal supports the first capability, where the first time-domain position or PRS occupancy time includes all symbols within a certain duration (e.g., within the PRS processing window) of the PRS symbols; the terminal supports the second capability, where the first time-domain position or PRS occupancy time includes the time occupied by the PRS symbols.

[0311] For example, the first capability mentioned above could be: the PRS can process all symbols within the processing window but cannot process other DL signals or channels; the second capability mentioned above could be: the PRS can process only the symbol where the PRS is located within the processing window but cannot process other DL signals or channels.

[0312] Optionally, in this embodiment of the application, the terminal may also obtain the PRS time range based on the PRS time domain location configuration. The time range corresponds to the time of the serving cell timing and / or subcarrier interval (with the serving cell symbol, slot or subframe as the granularity), which is the first time domain location.

[0313] Optionally, in the embodiments of this application, if the transmission start time and / or transmission end time of the PRS at least partially overlap with the first time unit, the first time domain location includes the first time unit;

[0314] And / or,

[0315] When the transmission start time of the PRS at least partially overlaps with the first time unit, the first time domain location includes the first time unit and the time unit adjacent to the first time unit.

[0316] And / or,

[0317] When the transmission end time of the PRS at least partially overlaps with the first time unit, the first time domain location includes the first time unit and a time unit adjacent to the first time unit.

[0318] In some possible embodiments, the first time-domain location includes the time unit when the PRS start time and / or end time at least partially overlap with (or happen to be in the middle of) a time unit (e.g., symbol, slot, or subframe).

[0319] In some possible embodiments, when the PRS start time at least partially overlaps with (or happens to be in the middle of) a time unit (e.g., a symbol, slot, or subframe), the first time domain position includes that time unit and the preceding adjacent time unit; and / or, when the PRS end time at least partially overlaps with (or happens to be in the middle of) a time unit (e.g., a symbol, slot, or subframe), the first time domain position includes that time unit and the following adjacent time unit.

[0320] Optionally, in this embodiment of the application, step 202, "receiving other downlink objects at the second time domain location," may include step 202b:

[0321] Step 202b: The terminal receives other downlink objects at the second time domain position based on at least one of the timing information of the serving cell and the time unit of the serving cell occupied by the subcarrier interval.

[0322] It should be noted that when the terminal receives other downlink objects in the second time domain, it can receive them based on the timing of the serving cell and / or the symbol, slot, or subframe of the serving cell occupied by the subcarrier interval.

[0323] It should be noted that the aforementioned serving cell can also be a carrier or component carrier.

[0324] In some possible embodiments, the serving cell is the serving cell where the active DL BWP receiving the PRS is located; and / or, the subcarrier spacing is the subcarrier spacing corresponding to the active DL BWP receiving the PRS.

[0325] The following examples illustrate the overlap between the PRS and the second time-domain location.

[0326] Example 1:

[0327] This embodiment mainly addresses the scenario where the PRS and the second time domain position do not overlap, meaning that the first time domain position and the second time domain position do not overlap.

[0328] For example, in serving cell 1 (or carrier 1), the terminal receives the PRS; in serving cell 2, 3, 4, or 5 (or carrier 2, 3, 4, or 5), the terminal receives other downlink channels or signals. Where the PRS boundary lies precisely in the middle of a slot or symbol, then the first time-domain position (including that slot or symbol) is defined.

[0329] It should be noted that, Figures 3 to 10 In the diagram, diagonal stripes indicate the first time-domain location, white indicates the second time-domain location, and gray indicates symbols or slots where other serving cells are interrupted. Furthermore, the time occupied by the PRS (i.e., the PRS with arrows) can be explicitly or implicitly configured. In one example, explicit configuration can be achieved through the PRS processing window (details below).

[0330] In addition, a square in the diagram represents a slot or a symbol.

[0331] Specifically, the non-overlapping of the first and second time domain locations can be divided into two cases:

[0332] Case 1: Serving cell 1 is synchronized with serving cells 2 / 3 / 4 / 5 (where serving cells 2 / 3 / 4 / 5 represent serving cells of different SCSs).

[0333] In case 1, such as Figure 3 As shown, Figure 3 The serving cell 1 in the signal is 15kHz.

[0334] In case 1, such as Figure 4 As shown, Figure 4 The serving cell 1 in the signal is 30kHz.

[0335] In case 1, such as Figure 5 As shown, Figure 5 The serving cell 1 in the signal is 60kHz.

[0336] In case 1, such as Figure 6 As shown, Figure 6 The serving cell 1 in the signal is 120kHz.

[0337] Scenario 2: Serving cell 1 is not synchronized with serving cells 2 / 3 / 4 / 5 (where serving cells 2 / 3 / 4 / 5 represent serving cells of different SCSs).

[0338] In case 2, such as Figure 7 As shown, Figure 7 The serving cell 1 in the signal is 15kHz.

[0339] In case 2, such as Figure 8 As shown, Figure 8 The serving cell 1 in the signal is 30kHz.

[0340] In case 2, such as Figure 9 As shown, Figure 9 The serving cell 1 in the signal is 60kHz.

[0341] In case 2, such as Figure 10 As shown, Figure 10 The serving cell 1 in the signal is 120kHz.

[0342] Example 2:

[0343] This embodiment mainly addresses the scenario where the PRS and the second time domain position do not overlap: the time occupied by the PRS does not overlap with the second time domain position.

[0344] For example, in serving cell 1 (or carrier 1), the terminal receives the PRS; in serving cell 2, 3, 4, or 5 (or carrier 2, 3, 4, or 5), the terminal receives other downlink channels or signals. Where the PRS boundary lies precisely in the middle of a slot or symbol, then the first time-domain position (including that slot or symbol) is defined.

[0345] It should be noted that, Figures 11 to 17 In the diagram, diagonal stripes represent the first time-domain position, white represents the second time-domain position, gray represents symbols or slots where other serving cells are interrupted, and vertical stripes represent the PRS occupancy time. Furthermore, the PRS occupancy time shown in the diagram (i.e., the PRS with arrows) can be explicitly or implicitly configured. In one example, explicit configuration can be achieved through the PRS processing window.

[0346] In addition, a square in the diagram represents a slot or a symbol.

[0347] Specifically, the non-overlapping time occupied by PRS and the second time domain position can be divided into two cases:

[0348] Case 1: Serving cell 1 is synchronized with serving cells 2 / 3 / 4 / 5 (where serving cells 2 / 3 / 4 / 5 represent serving cells of different SCSs).

[0349] Example 1: The time occupied by PRS is a time-domain position relative to a certain 'reference time'. In one example, this 'reference time' is the SFN0 of a serving cell, a specific point in time within the serving cell's timing, or a certain absolute time. See details... Figures 11 to 13 As shown.

[0350] Example 2: The time occupied by PRS is the absolute time domain location. See details... Figure 14 As shown.

[0351] Example 3: The UE receives the PRS in serving cell 1. In serving cell 1, other downlink channels / signals can only be transmitted in the white area; in other serving cells, other downlink channels / signals can be transmitted in the white area, only needing to consider whether they collide with the PRS boundary, without needing to consider collisions with the first time domain location. See details... Figure 15 As shown.

[0352] Example 4: The UE receives the PRS in serving cell 1, and the first time domain position is aligned with the PRS boundary. See details... Figure 16 As shown.

[0353] Scenario 2: Serving cell 1 is asynchronous with serving cells 2 / 3 / 4 / 5 (where serving cells 2 / 3 / 4 / 5 represent serving cells of different SCSs). See details below. Figure 17 As shown.

[0354] Optionally, in this embodiment, the configuration related to the PRS processing window can be explicitly configured or implicitly configured, and this embodiment does not limit this.

[0355] It should be noted that in the embodiments of this application, the PRS processing window may be explicitly configured to the terminal or implicitly configured to the terminal. Simultaneously, the terminal may support the capability (e.g., Capability 1) that the PRS has a higher priority than other downlink objects throughout the entire duration of the PRS processing window. In implicit configuration, after receiving the PRS configuration, the terminal needs to specify or have the same understanding as the network side regarding which time period the PRS has a higher priority than other DL signals / channels (or which time period the terminal does not need to listen to other downlink objects), or what assumptions should be made regarding which time period should be considered the PRS processing window. This embodiment of the application limits this. For example, the terminal may assume that within a PRS cycle, between the earliest and latest PRS symbols, the PRS has a higher priority than other downlink objects.

[0356] Of course, the network side can determine whether to explicitly configure the PRS processing window based on the terminal's capabilities. For example, if the terminal supports Capability 1, the PRS processing window will be explicitly configured, while if the terminal supports Capability 2, the PRS processing window will be implicitly configured. See below for more details.

[0357] Optionally, in this embodiment of the application, the above-mentioned PRS configuration includes: configuration related to the PRS processing window.

[0358] In some possible embodiments, the configuration related to the PRS processing window is configured by a first network-side device or a second network-side device.

[0359] In some possible embodiments, the configuration related to the PRS processing window includes at least one of the following:

[0360] The PRS processing window label;

[0361] Types of PRS processing windows;

[0362] The PRS associated with the PRS processing window includes at least one of the following: at least one positioning frequency layer identifier, TRP identifier, PRS resource set identifier, and PRS resource identifier.

[0363] Priority information of PRS within the PRS processing window;

[0364] The frequency domain location information associated with PRS within the PRS processing window;

[0365] The first PRS resource and / or the last PRS resource within the PRS processing window must have at least one of the following: PRS resource identifier, timestamp corresponding to the PRS resource;

[0366] PRS processing window temporal location information;

[0367] PRS time-domain location information.

[0368] In some possible embodiments, the timestamp corresponding to the PRS resource includes at least one of the following: the index of the subframe corresponding to the PRS resource, the index of the system frame corresponding to the PRS resource, and the index of the time slot corresponding to the PRS resource. In one example, the timestamp may also be: the index of the subframe corresponding to the start position of the first PRS resource in the PRS processing window, or the index of the subframe corresponding to the end position of the last PRS resource. For example, the timing of the timestamp is based on the RSTD reference cell, the cell transmitting the PRS, or other designated cells.

[0369] In one example, the PRS resource identifier mentioned above includes at least one of the following: PRS resource set identifier, PRS resource identifier, and PRS identifier (DL-PRS ID, such as TRP identifier).

[0370] In some possible embodiments, the type of the PRS processing window mentioned above includes, but is not limited to, one of Per UE, Per FR, Per CC, Per band, or Per RB block.

[0371] In some possible embodiments, the type of the PRS processing window described above corresponds to the terminal capability of the PRS processing window. That is, the type of the PRS processing window can also be expressed as the type of terminal capability.

[0372] In some possible embodiments, the frequency domain location information associated with the PRS within the PRS processing window can also be represented as the frequency domain location information associated with the PRS processing window, which may include at least one of the following: associated frequency point, such as ARFCN, or DL ​​PRSpointA; frequency range indication, such as FR1 or FR2; band identifier, such as band indicator; carrier identifier; PRS bandwidth; PRS SCS; PRS start PRB.

[0373] In some possible embodiments, the priority information of PRS within the PRS processing window includes, but is not limited to, the priority relationship between PRS and at least one of the following signals: SSB, CSI-RS, SIB1, SIBx, DMRS, TRS, PTRS, paging, PDSCH, PDCCH.

[0374] Optionally, the configuration information related to the PRS processing window should include at least one PRS processing window configuration.

[0375] In some possible embodiments, the temporal location information of the PRS processing window includes at least one of the following:

[0376] Window length of the PRS processing window;

[0377] The cycle of the PRS processing window;

[0378] The interval between adjacent PRS processing windows;

[0379] The number of PRS processing windows;

[0380] The start time of the PRS processing window;

[0381] PRS processing window time reference point information.

[0382] The unit or granularity of the PRS processing window.

[0383] In some possible embodiments, the start time of the PRS processing window is the start time of the first PRS processing window, which can be an absolute time (such as UTC time) or a relative time. In one example, the relative time can be a time offset relative to a certain time reference point.

[0384] In some possible embodiments, when the configuration related to the PRS processing window is provided by a first network-side device, the time reference point of the PRS processing window is: absolute time, or a first target time point based on the timing of the target network-side device (e.g., a gNB) or the target cell (e.g., RSTD reference cell).

[0385] In some possible embodiments, the aforementioned first target time point may be indicated by a first network-side device and / or agreed upon by a protocol.

[0386] In some possible embodiments, the target network-side device or target cell may be indicated and / or agreed upon by the first network-side device.

[0387] In some possible embodiments, the first target time point mentioned above also includes an indication of the SFN0 offset between the target network-side device and the serving gNB.

[0388] In some possible embodiments, when the configuration related to the PRS processing window is provided by a second network-side device, the time reference point for the PRS processing window is: absolute time, or a second target time point based on the timing of the second network-side device (e.g., the serving gNB).

[0389] In some possible embodiments, the aforementioned second target time point may be indicated by a second network-side device and / or agreed upon by a protocol.

[0390] In some possible embodiments, the timing of the aforementioned second network-side device can be the timing of a Pcell, Pscell, or a certain scell. Furthermore, the timing based on which serving cell is determined can be agreed upon by a protocol or instructed by the network.

[0391] In some possible embodiments, the first target time point mentioned above is one of the following:

[0392] SFN0;

[0393] The subframe start point closest to the start time of the PRS processing window (e.g., indicating: SFN and at least one of the subframe index);

[0394] The starting point of the nearest subframe before the start time of the PRS processing window;

[0395] The slot or symbol start point closest to the start time of the PRS processing window (e.g., indicating at least one of SFN, subframeindex, slot index, symbol index, or SCS);

[0396] The nearest slot or symbol start point before the start time of the PRS processing window;

[0397] Other specified / indicated time points.

[0398] For example, the above-mentioned SCS or the SCS that determines the slot / symbol is consistent with the SCS of the serving cell (or PRS) that receives the PRS.

[0399] In some possible embodiments, the second target time point is one of the following:

[0400] SFN0;

[0401] The subframe start point closest to the start time of the PRS processing window (e.g., indicating: SFN and at least one of the subframe index);

[0402] The starting point of the nearest subframe before the start time of the PRS processing window;

[0403] The slot or symbol start point closest to the start time of the PRS processing window (e.g., indicating at least one of SFN, subframeindex, slot index, symbol index, or SCS);

[0404] The nearest slot or symbol start point before the start time of the PRS processing window;

[0405] Other specified / indicated time points.

[0406] For example, the SCS described above, or the SCS that determines the slot or symbol, is consistent with the SCS of the serving cell (or PRS) that receives the PRS.

[0407] In some possible embodiments, the above-mentioned PRS time-domain location information includes at least one of the following:

[0408] TRP-level time-domain configuration;

[0409] PRS resource set-level time-domain configuration;

[0410] PRS resource-level time-domain configuration;

[0411] The effective time of the PRS or PRS time window;

[0412] Information on the effective time window of the PRS or PRS time window.

[0413] In one example, the above TRP-level time-domain configuration includes at least one of the following: SFN0-offset between TRPs, expected-RSTD+-uncertain.

[0414] In one example, the aforementioned PRS resource set-level time-domain configuration includes at least one of the following: resource set period, resource set period offset, repetition configuration, and muting configuration (including type 1 muting pattern and / or type 2 muting pattern). In another example, the offset information of the aforementioned PRS resource set-level time-domain configuration may be an offset relative to the PRS processing window.

[0415] In one example, the above PRS resource-level time-domain configuration includes at least one of the following: PRS resourceslot offset, symbol offset, symbol number.

[0416] In one example, the effective time of the aforementioned PRS or PRS time window indicates that the PRS or PRS time window is effective within this time period. Furthermore, within this PRS time window, gNB scheduling of other DL signals and / or channels will be restricted.

[0417] In one example, the aforementioned PRS or PRS time window effective time window information indicates that the PRS or PRS time window is effective within that time window. Furthermore, within the PRS time window of that time window, gNB scheduling of other DL signals and / or channels will be restricted.

[0418] In one example, the effective time of the aforementioned PRS or PRS time window contains information similar to that contained in the effective time window information of the PRS or PRS time window.

[0419] In one example, the aforementioned effective time or effective time window can be further triggered by signaling.

[0420] Furthermore, the PRS in the PRS processing window may be received along with data from other carriers. Therefore, the MG request may only need to provide the network side with specific time-domain information; while the PRS processing window may need to provide both frequency-domain and time-domain information, allowing the network side to determine which carriers or bands can transmit data.

[0421] Thus, in the absence of MG configuration, this application embodiment introduces a PRS processing window to avoid interruptions or scheduling restrictions on the transmission of DL signals / channels of other serving cells when the terminal uses a certain serving cell to receive PRS.

[0422] Optionally, in this embodiment of the application, before the terminal measures the PRS, the PRS processing method provided in this embodiment of the application may further include the following step 302:

[0423] Step 302: The terminal sends its capabilities to the network-side device.

[0424] The aforementioned terminal capabilities include at least one of the following:

[0425] Does it support measuring PRS within an active DL BWP?

[0426] Does it support measuring PRS using a PRS processing window?

[0427] Does it support measuring PRS using measurement intervals?

[0428] In some possible embodiments, the network-side device can be a first network-side device or a second network-side device.

[0429] In some possible embodiments, if PRS measurement using a PRS processing window is supported, the terminal may further indicate capabilities related to the PRS processing window.

[0430] In some possible embodiments, the terminal sends its capabilities to the second network-side device, either directly to the second network-side device or first to the first network-side device, and then from the first network-side device to the second network-side device.

[0431] Optionally, in this embodiment of the application, when the first time-domain location does not explicitly include the configuration information of the PRS processing window, the PRS processing method provided in this embodiment of the application may further include the following step 303:

[0432] Step 303: Based on the first information, the terminal determines that the PRS processing window satisfies at least one of the following (or, based on the first information, the terminal determines that at least one of the following assumptions holds):

[0433] Assumption 1: Within a positioning frequency layer, a period of PRS constitutes a PRS processing window, and the range of the PRS processing window is from the first PRS resource to the last PRS resource in a period of PRS.

[0434] Assumption 2: Within a positioning frequency layer, PRS of the same period, a period of PRS constitutes a PRS processing window, and the range of the PRS processing window is from the first PRS resource to the last PRS resource in a period of PRS.

[0435] Assumption 3: A period of PRS within a PRS resource set constitutes a PRS processing window, and the range of the PRS processing window is from the first PRS resource to the last PRS resource in the PRS resource set.

[0436] Assumption 4: Within a positioning frequency layer, adjacent first PRS within one cycle constitute a PRS processing window, and the distance between adjacent first PRS does not exceed the first threshold.

[0437] Assumption 5: Within a positioning frequency layer, PRS with the same period, adjacent second PRS within one period constitute a PRS processing window, and the distance between adjacent second PRS does not exceed the first threshold.

[0438] Assumption 6: Within a positioning frequency layer cycle, the earliest PRS resource and the latest PRS resource constitute a PRS processing window.

[0439] Assumption 7: Within the same PRS resource set, PRS from different periods belong to different PRS processing windows;

[0440] Assumption 8: PRS at different positioning frequency layers belong to different PRS processing windows;

[0441] Assumption 9: PRS of different periods within a positioning frequency layer belong to different PRS processing windows.

[0442] In some possible implementations, the terminal can enable this assumption based on an instruction from the network side. For example, if the terminal receives 1 bit of this instruction, the assumption is valid.

[0443] In some possible embodiments, if a frequency layer contains multiple periods of PRS resource sets, the period of the frequency layer can be a minimum co-multiple of the multiple PRS resource sets.

[0444] In some possible embodiments, the first information described above is used to indicate at least one of the following:

[0445] The terminal is allowed to use BWP to measure PRS;

[0446] The terminal is not explicitly configured with a PRS processing window;

[0447] The terminal was not configured with a measurement interval MG;

[0448] The terminal receives an instruction to enable the aforementioned hypothesis;

[0449] The terminal capability supports the first capability in the second PRS processing capability (the first capability includes: PRS takes precedence over all other downlink objects in all symbols within the PRS processing window);

[0450] Enable scheduling constraints;

[0451] The terminal receives an instruction that the PRS processing mode is to prioritize all other downlink objects in all symbols within the duration containing the PRS symbol (within the PRS processing window).

[0452] It should be noted that the phrase “forming a PRS processing window” mentioned in this application can be expressed as: during the duration of the process, the PRS takes precedence over all other downlink objects of all symbols during the duration.

[0453] Furthermore, this duration does not overlap with the second time-domain location associated with other downlink objects.

[0454] Optionally, in this embodiment of the application, the PRS processing method provided in this embodiment of the application may further include the following step 304:

[0455] Step 304: If the PRS configuration includes a PRS processing window configuration, then when the terminal enters the active or idle state, the terminal ignores the PRS processing window configuration, or the terminal ignores the scheduling restrictions imposed by the PRS processing window.

[0456] Optionally, in this embodiment of the application, the PRS processing method provided in this embodiment of the application may further include the following step 305:

[0457] Step 305: When the terminal is in an active or idle state, the terminal does not expect the PRS configuration to include the PRS processing window configuration, and / or the terminal ignores the PRS scheduling restrictions.

[0458] Optionally, in this embodiment of the application, before the terminal receives the PRS, the PRS processing method provided in this embodiment of the application may further include the following step 306:

[0459] Step 306: The terminal receives the first instruction information from the network-side device.

[0460] The aforementioned first instruction information is used to indicate at least one of the following:

[0461] Allows the terminal to receive PRS within the active DL BWP.

[0462] Allows the terminal to process PRS within the PRS processing window.

[0463] Enable PRS scheduling constraints.

[0464] Disable PRS scheduling restrictions.

[0465] Optionally, in this embodiment of the application, before the terminal receives the PRS, the PRS processing method provided in this embodiment of the application may further include the following step 307:

[0466] Step 307: The terminal sends a second instruction message to the network-side device.

[0467] The aforementioned second instruction information is used to indicate at least one of the following:

[0468] The terminal expects to be allowed to receive PRS within an active DL BWP.

[0469] The terminal expects to be allowed to process PRS within the PRS processing window.

[0470] In the PRS processing method provided in this application embodiment, after receiving the PRS configuration, the terminal can receive the PRS at a first time domain location based on the PRS configuration, and / or receive other downlink objects (i.e., at least one of other downlink signals and other downlink channels) at a second time domain location. Since the overlap between the PRS and the second time domain location is related to at least one of the correlation between the PRS and the other downlink objects and the relevant information of PRS processing, the impact of PRS processing on the transmission of other downlink objects can be reduced, thereby avoiding the interruption of the transmission of other downlink objects and improving the system communication energy efficiency.

[0471] This application provides a method for processing PRS, such as... Figure 18 As shown, the PRS processing method includes the following steps 401:

[0472] Step 401: The first network-side device sends the configuration related to the PRS processing window to the second network-side device or terminal.

[0473] The aforementioned PRS processing window-related configuration is used by the second network-side device to retrieve other downlink objects; these other downlink objects include at least one of the following: other downlink signals, other downlink channels; other downlink signals are signals other than PRS; other downlink channels are channels that transmit signals other than PRS.

[0474] Optionally, in this embodiment of the application, after step 401 above, the PRS processing method provided in this embodiment of the application further includes the following step 402:

[0475] Step 402: The first network-side device sends an activation instruction for the PRS processing window to the second network-side device.

[0476] In some possible embodiments, the activation instruction described above includes at least one of the following:

[0477] Activation identifier;

[0478] The effective time of the PRS processing window;

[0479] The time of the first PRS transmission when the PRS processing window takes effect.

[0480] The activation identifier is used to request the activation of the PRS processing window; the effective time of the processing window includes at least one of the following: start effective time, end effective time, and effective duration.

[0481] The time of the first PRS transmission when the aforementioned PRS processing window takes effect indicates that the PRS processing window begins to take effect at that PRS transmission time.

[0482] For example, after the first network-side device sends the relevant configuration of the PRS processing window to the second network-side device, it can send an activation instruction for the PRS processing window. The PRS processing window is assumed to be active only after the second network-side device receives the activation instruction.

[0483] It should be noted that the descriptions of "PRS processing window related configuration" and other related content mentioned in this embodiment can be found above. To avoid repetition, they will not be repeated here.

[0484] In the PRS processing method provided in this application embodiment, the first network-side device sends a PRS processing window-related configuration to the second network-side device or terminal, so that the second network-side device can retrieve other downlink objects (i.e., at least one of other downlink signals and other downlink channels) based on the PRS processing window-related configuration. This not only reduces the impact of PRS processing on the transmission of other downlink objects but also avoids interruptions to the transmission of other downlink objects, thus improving system communication energy efficiency.

[0485] This application provides a method for processing PRS, such as... Figure 19 As shown, the PRS processing method includes the following steps 501 and 502:

[0486] Step 501: The second network-side device receives the configuration related to the PRS processing window from the first network-side device.

[0487] Step 502: The second network-side device retrieves other downlink objects based on the configuration related to the PRS processing window.

[0488] Among them, the other downlink objects mentioned above include at least one of the following: other downlink signals, other downlink channels; other downlink signals are signals other than PRS; other downlink channels are channels that transmit signals other than PRS.

[0489] Optionally, in this embodiment of the application, after step 501 above, the PRS processing method provided in this embodiment of the application further includes the following step 503:

[0490] Step 503: The second network-side device sends the configuration related to the PRS processing window to the terminal.

[0491] Optionally, in this embodiment of the application, the PRS processing method provided in this embodiment of the application further includes the following step 504:

[0492] Step 504: The second network-side device receives target indication information from the first network-side device or terminal.

[0493] The aforementioned target indication information is used to indicate that the terminal is allowed to measure PRS within the activated DL BWP.

[0494] It should be noted that the descriptions of "PRS processing window related configuration" and other related content mentioned in this embodiment can be found above. To avoid repetition, they will not be repeated here.

[0495] In the PRS processing method provided in this application embodiment, the second network-side device receives the configuration related to the PRS processing window from the first network-side device, and then retrieves other downlink objects (i.e., at least one of other downlink signals and other downlink channels) based on the configuration related to the PRS processing window. In this way, not only can the impact of PRS processing on the transmission of other downlink objects be reduced, but the interruption of the transmission of other downlink objects can also be avoided, thereby improving the system communication energy efficiency.

[0496] It should be noted that the PRS processing method provided in this application embodiment can be executed by a PRS processing device or a control module within that PRS processing device for executing the PRS processing method. This application embodiment uses the execution of the PRS processing method by a PRS processing device as an example to illustrate the PRS processing device provided in this application embodiment.

[0497] This application provides a PRS processing apparatus, such as... Figure 20 As shown, the PRS processing device 600 includes: a first receiving module 601 and a second receiving module 602, wherein:

[0498] A first receiving module 601 is used to receive a PRS configuration; a second receiving module 602 is used to receive a PRS at a first time domain location and / or receive other downlink objects at a second time domain location according to the PRS configuration received by the first receiving module 601; wherein the overlap relationship between the PRS and the second time domain location is related to at least one of the following: the association relationship between the PRS and the other downlink objects, and relevant information related to PRS processing; the other downlink objects include at least one of the following: other downlink signals, other downlink channels; the other downlink signals are signals other than the PRS; the other downlink channels are channels for transmitting signals other than the PRS.

[0499] In some possible embodiments, the association between the PRS and the other downlink objects includes at least one of the following:

[0500] The priority relationship between the PRS and the other downlink objects;

[0501] The frequency domain positional relationship between the PRS and the other downlink objects.

[0502] In some possible embodiments, the relevant information of the PRS processing includes at least one of the following:

[0503] The first type of PRS processing capability;

[0504] PRS processing type.

[0505] In some possible embodiments, the first PRS processing capability is the terminal's ability to process PRS when there is no MG;

[0506] The type of the first PRS processing capability includes at least one of the following:

[0507] Processing capacity of each terminal;

[0508] Processing capacity of each FR;

[0509] Processing capacity of each band;

[0510] The processing capacity of each carrier;

[0511] Processing capacity of each RB block.

[0512] In some possible embodiments, the PRS processing type is the type of PRS that the terminal processes when there is no MG;

[0513] The PRS processing type includes at least one of the following:

[0514] The type of Per UE;

[0515] Per FR type;

[0516] Types of Per bands;

[0517] Types of Per Carrier;

[0518] Per RB block type.

[0519] In some possible embodiments, the priority relationship between the PRS and the other downlink objects is that the PRS has a higher priority than the other downlink objects.

[0520] In some possible embodiments, the relationship between the frequency domain position of the other downlink object and the frequency domain position of the PRS includes at least one of the following: the frequency domain position of the other downlink object is the same as the frequency domain position of the PRS; or, the frequency domain position of the other downlink object is different from the frequency domain position of the PRS.

[0521] In some possible embodiments, the frequency domain location of the other downlink object is the same as the frequency domain location of the PRS, including at least one of the following:

[0522] The PRS is located on the same carrier as the other downlink objects;

[0523] The PRS is located in the same BWP as the other downlink objects;

[0524] The PRS and the other downlink objects are located at overlapping RB positions.

[0525] In some possible embodiments, the frequency domain location of the other downlink object differs from the frequency domain location of the PRS, including at least one of the following:

[0526] The PRS and the other downlink objects are located on carriers in different frequency ranges (FR);

[0527] The PRS and the other downlink objects are carriers located in different frequency bands within the same frequency range FR;

[0528] The PRS and the other downlink objects are located on carriers in the same frequency band but different carriers;

[0529] The PRS and the other downlink objects are located at non-overlapping RB positions in the same BWP on the same carrier;

[0530] The PRS and the other downlink objects are located on carriers in different frequency bands;

[0531] The carrier of the PRS includes: the carrier that receives the PRS, or the carrier in which the PRS is located, or the carrier in which the activated DL BWP of the PRS is located.

[0532] In some possible embodiments, the overlap between the PRS and the other downlink objects is determined based on at least one of the following:

[0533] If the PRS has a higher priority than the other downlink objects, and the frequency domain positional relationship between the PRS and the other downlink objects satisfies the limitation of the type of the first PRS processing capability or the frequency domain range corresponding to the PRS processing type, then the PRS and the other downlink objects do not overlap.

[0534] If the PRS has a higher priority than the other downlink objects, and the frequency domain positional relationship between the PRS and the other downlink objects does not satisfy the limitation of the type of the first PRS processing capability or the frequency domain range corresponding to the PRS processing type, then the PRS and the other downlink objects may overlap.

[0535] In some possible embodiments, the PRS processing device 600 measures the PRS within an activated downlink BWP.

[0536] In some possible embodiments, the PRS does not overlap with the second time-domain location.

[0537] In some possible embodiments, the non-overlapping of the PRS with the second time-domain location includes at least one of the following:

[0538] The first time domain location and the second time domain location do not overlap.

[0539] The time occupied by the PRS does not overlap with the second time domain position.

[0540] In some possible embodiments, the PRS and the second time-domain location are not overlapped in a manner determined based on at least one of the following: network indication, protocol agreement, UE selection.

[0541] In some possible embodiments, the non-overlapping of the first time domain location and the second time domain location includes at least one of the following:

[0542] When the other downlink objects are located on the same carrier as the PRS, or when the other downlink objects are located on the same BWP as the PRS, the first time domain position and the second time domain position do not overlap;

[0543] If the other downlink object is located on a different carrier than the PRS, and the boundary of the first time domain location at least partially overlaps with the first time unit of the carrier associated with the other downlink object, then the second time domain location does not include the first time unit.

[0544] In some possible embodiments, the time occupied by the PRS does not overlap with the second time-domain location, including at least one of the following:

[0545] If the other downlink object is located on the same carrier as the PRS, or if the other downlink object is located on the same BWP as the PRS, then the second time domain location does not include the second time unit if the boundary of the time occupied by the PRS at least partially overlaps with the second time unit of the carrier.

[0546] If the other downlink object is located on a different carrier than the PRS, and the boundary of the time occupied by the PRS at least partially overlaps with the third time unit of the carrier associated with the other downlink object, then the second time domain location does not include the third time unit.

[0547] In some possible embodiments, the time occupied by PRS includes the time corresponding to the PRS processing window.

[0548] In some possible embodiments, the time occupied by the PRS is related to at least one of the following:

[0549] PRS time-domain location configuration

[0550] The TRP for sending the PRS is offset from the SFN0 of the serving cell and / or reference cell.

[0551] SFN0 offset between serving cell and reference cell

[0552] The TRP that sends the PRS is related to the expected RSTD of the serving cell and / or reference cell.

[0553] The uncertainty of the TRP for sending the PRS and the expected RSTD of the serving cell and / or reference cell.

[0554] Reference cell TRP and serving cell TRP expected RSTD

[0555] The expected RSTD uncertainty of the reference cell TRP and the serving cell TRP,

[0556] Second PRS processing capability

[0557] PRS processing time

[0558] SFN0 service time for the community

[0559] SCS serving the community.

[0560] In some possible embodiments, when the PRS does not overlap with the second time-domain location, the frequency-domain relationship between the PRS and the other downlink objects includes at least one of the following:

[0561] The other downlink objects are carriers located in different frequency ranges (FR) from the PRS;

[0562] The other downlink objects are carriers in different frequency bands of the same frequency range FR as the PRS;

[0563] The other downlink objects are located on different carriers in the same frequency band as the PRS;

[0564] The other downlink objects are carriers located in different frequency bands from the PRS;

[0565] The other downlink objects and the PRS are located at non-overlapping RB positions in the same BWP on the same carrier;

[0566] The other downlink objects are located at overlapping RB positions with the PRS in the same BWP on the same carrier.

[0567] In some possible embodiments, the second receiving module 602 is specifically configured to: receive PRS at a first time domain location based on at least one of the timing information of the serving cell and the time unit of the serving cell occupied by the subcarrier interval.

[0568] In some possible embodiments, the first time-domain location is associated with at least one of the following:

[0569] PRS time-domain location configuration

[0570] The TRP that sends the PRS is offset from the SFN0 system frame of the serving cell and / or reference cell.

[0571] SFN0 offset between serving cell and reference cell

[0572] The TRP that sends the PRS is related to the expected RSTD of the serving cell and / or reference cell.

[0573] The uncertainty of the TRP for sending the PRS and the expected RSTD of the serving cell and / or reference cell.

[0574] Reference cell TRP and serving cell TRP expected RSTD

[0575] The expected RSTD uncertainty of the reference cell TRP and the serving cell TRP,

[0576] Second PRS processing capability

[0577] PRS processing time

[0578] SFN0 service time for the community

[0579] SCS serving the community.

[0580] In some possible embodiments, the time-domain location configuration of the PRS includes, but is not limited to, one of the following: PRS period, period offset, PRS repetition, PRS subcarrier spacing, PRS pattern, and PRS processing window configuration.

[0581] In some possible embodiments, the second PRS processing capability includes at least one of the following:

[0582] The ability to handle PRS;

[0583] PRS has the capability to handle window-related tasks.

[0584] In some possible embodiments, the first time domain location includes the fourth time unit if the transmission start time and / or transmission end time of the PRS at least partially overlap with the fourth time unit.

[0585] And / or,

[0586] When the transmission start time of the PRS at least partially overlaps with the fourth time unit, the first time domain position includes the fourth time unit and a time unit adjacent to the fourth time unit.

[0587] And / or,

[0588] When the transmission end time of the PRS at least partially overlaps with the fourth time unit, the first time domain location includes the fourth time unit and a time unit adjacent to the fourth time unit.

[0589] In some possible embodiments, the second receiving module 602 is specifically configured to: receive other downlink objects at a second time-domain location based on at least one of the timing information of the serving cell and the time unit of the serving cell occupied by the subcarrier interval.

[0590] In some possible embodiments, the PRS configuration includes: configuration related to the PRS processing window.

[0591] In some possible embodiments, the configuration related to the PRS processing window is configured by a first network-side device or a second network-side device.

[0592] In some possible embodiments, the configuration associated with the PRS processing window includes at least one of the following:

[0593] The identifier of the PRS processing window;

[0594] The type of the PRS processing window;

[0595] The PRS associated with the PRS processing window includes at least one of the following: at least one positioning frequency layer identifier, TRP identifier, PRS resource set identifier, and PRS resource identifier.

[0596] The priority information of PRS within the PRS processing window;

[0597] The frequency domain location information associated with PRS within the PRS processing window;

[0598] The first PRS resource and / or the last PRS resource in the PRS processing window shall be at least one of the following: PRS resource identifier, timestamp corresponding to the PRS resource;

[0599] The temporal location information of the PRS processing window;

[0600] PRS time-domain location information.

[0601] In some possible embodiments, the temporal location information of the PRS processing window includes at least one of the following:

[0602] The window length of the PRS processing window;

[0603] The period of the PRS processing window;

[0604] The spacing between adjacent windows of the PRS processing window and the PRS processing window;

[0605] The start time of the PRS processing window;

[0606] The time reference point information of the PRS processing window.

[0607] The unit or granularity of the PRS processing window.

[0608] In some possible embodiments, when the configuration associated with the PRS processing window is provided by a first network-side device, the time reference point of the PRS processing window is: absolute time, or a first target time point based on the timing of the target network-side device or the target cell.

[0609] In some possible embodiments, when the configuration associated with the PRS processing window is provided by a second network-side device, the time reference point of the PRS processing window is: absolute time, or, based on a second target time point in the timing of the second network-side device.

[0610] In some possible embodiments, the first target time point is one of the following:

[0611] SFN0;

[0612] The starting point of the subframe closest to the start time of the PRS processing window;

[0613] The nearest subframe start point before the start time of the PRS processing window;

[0614] The time slot or symbol start point closest to the start time of the PRS processing window.

[0615] In some possible embodiments, the second target time point is one of the following:

[0616] SFN0;

[0617] The starting point of the subframe closest to the start time of the PRS processing window;

[0618] The nearest subframe start point before the start time of the PRS processing window;

[0619] The time slot or symbol start point closest to the start time of the PRS processing window.

[0620] In some possible embodiments, the method further includes, prior to measuring the PRS:

[0621] The terminal sends its capabilities to the network-side device.

[0622] The terminal capabilities include at least one of the following:

[0623] Does it support measuring PRS within an active DL BWP?

[0624] Does it support measuring PRS using a PRS processing window?

[0625] Does it support measuring PRS using measurement intervals?

[0626] In some possible embodiments, combined Figure 20 ,like Figure 21 As shown, the device 600 further includes an execution module 603, wherein the execution module 603 is configured to determine, based on the first information, that the PRS processing window satisfies at least one of the following:

[0627] Within a positioning frequency layer, a PRS cycle constitutes a PRS processing window, the range of which is from the first PRS resource to the last PRS resource in the PRS cycle.

[0628] Within a positioning frequency layer, PRS of the same period, and PRS of one period constitute a PRS processing window, the range of which is from the first PRS resource to the last PRS resource in the PRS of one period.

[0629] A period of PRS within a PRS resource set constitutes a PRS processing window, the range of which is from the first PRS resource to the last PRS resource in the PRS resource set.

[0630] Within a positioning frequency layer, adjacent first PRS within one cycle constitute a PRS processing window, and the distance between adjacent first PRS does not exceed a first threshold.

[0631] Within a positioning frequency layer, PRS with the same period, adjacent second PRS within a period constitute a PRS processing window, and the distance between adjacent second PRS does not exceed the first threshold.

[0632] Within a positioning frequency layer cycle, the earliest PRS resource and the latest PRS resource constitute a PRS processing window.

[0633] Within the same PRS resource set, PRS from different PRS resource sets belong to different PRS processing windows.

[0634] PRS at different positioning frequency layers belong to different PRS processing windows;

[0635] PRS of different periods within a positioning frequency layer belong to different PRS processing windows.

[0636] In some possible embodiments, the execution module 603 is further configured to: if the PRS configuration includes a PRS processing window configuration, then when the terminal enters an active state or an idle state, ignore the PRS processing window configuration, or ignore the scheduling restrictions corresponding to the PRS processing window.

[0637] In some possible embodiments, the execution module 603 is further configured to: when the terminal is in an active or idle state, not expect the PRS configuration to include the PRS processing window configuration, and / or ignore the PRS scheduling restrictions.

[0638] In some possible embodiments, combined Figure 20 ,like Figure 21As shown, the device 600 further includes: a third receiving module 604; the third receiving module 604 is also used to receive first indication information from the network-side device;

[0639] Wherein, the first indication information is used to indicate at least one of the following:

[0640] The terminal is allowed to receive PRS within the activated DL BWP.

[0641] The terminal is allowed to process PRS within the PRS processing window.

[0642] Enable PRS scheduling constraints.

[0643] PRS scheduling restrictions are disabled.

[0644] In some possible embodiments, combined Figure 20 ,like Figure 21 As shown, the device 600 further includes: a sending module 605; the sending module 605 is used to send second indication information to the network-side device;

[0645] Wherein, the second indication information is used to indicate at least one of the following:

[0646] The terminal expects to be allowed to receive PRS within an active DL BWP.

[0647] The terminal expects to be allowed to process PRS within a PRS processing window.

[0648] In the PRS processing apparatus provided in this application embodiment, after receiving the PRS configuration, the apparatus can receive the PRS at a first time domain location based on the PRS configuration, and / or receive other downlink objects (i.e., at least one of other downlink signals and other downlink channels) at a second time domain location. Since the overlap between the PRS and the second time domain location is related to at least one of the correlation between the PRS and the other downlink objects and the relevant information of the PRS processing, the impact of PRS processing on the transmission of other downlink objects can be reduced, thereby avoiding interruptions to the transmission of other downlink objects and improving system communication energy efficiency.

[0649] This application provides a PRS processing apparatus, such as... Figure 22 As shown, the PRS processing device 700 includes: a transmission module 701, wherein:

[0650] The sending module 701 is used to send PRS processing window related configuration to a second network-side device or terminal; wherein, the PRS processing window related configuration is used by the second network-side device to retrieve other downlink objects; the other downlink objects include at least one of the following: other downlink signals, other downlink channels; the other downlink signals are signals other than PRS; the other downlink channels are channels for transmitting signals other than PRS.

[0651] In some possible embodiments, the sending module 701 is also used to send an activation indication of the PRS processing window to the second network-side device.

[0652] In some possible embodiments, the activation instruction includes at least one of the following:

[0653] Activation identifier;

[0654] The effective time of the PRS processing window;

[0655] The time of the first PRS transmission when the PRS processing window takes effect.

[0656] The activation identifier is used to request the activation of the PRS processing window;

[0657] The effective time of the processing window includes at least one of the following: start effective time, end effective time, and effective duration.

[0658] In some possible embodiments, the configuration associated with the PRS processing window includes at least one of the following:

[0659] The identifier of the PRS processing window;

[0660] The type of the PRS processing window;

[0661] The PRS associated with the PRS processing window includes at least one of the following: at least one positioning frequency layer identifier, TRP identifier, PRS resource set identifier, and PRS resource identifier.

[0662] The priority information of PRS within the PRS processing window;

[0663] The frequency domain location information associated with PRS within the PRS processing window;

[0664] The first PRS resource and / or the last PRS resource in the PRS processing window shall be at least one of the following: PRS resource identifier, timestamp corresponding to the PRS resource;

[0665] The temporal location information of the PRS processing window;

[0666] PRS time-domain location information.

[0667] In some possible embodiments, the temporal location information of the PRS processing window includes at least one of the following:

[0668] The window length of the PRS processing window;

[0669] The period of the PRS processing window;

[0670] The spacing between adjacent windows of the PRS processing window and the PRS processing window;

[0671] The start time of the PRS processing window;

[0672] The time reference point information of the PRS processing window.

[0673] The unit or granularity of the PRS processing window.

[0674] In some possible embodiments, the time reference point of the PRS processing window is: absolute time, or a first target time point based on the timing of the target network-side device or the target cell.

[0675] In the PRS processing apparatus provided in this application embodiment, the apparatus sends a PRS processing window-related configuration to a second network-side device or terminal, enabling the second network-side device to retrieve other downlink objects (i.e., at least one of other downlink signals and other downlink channels) based on the PRS processing window-related configuration. This not only reduces the impact of PRS processing on the transmission of other downlink objects but also avoids interruptions to the transmission of other downlink objects, thus improving system communication energy efficiency.

[0676] This application provides a PRS processing apparatus, such as... Figure 23 As shown, the PRS processing device 800 includes: a receiving module 801 and an execution module 802, wherein:

[0677] The receiving module 801 is used to receive configuration related to the PRS processing window from the first network-side device; the execution module 802 is used to retrieve other downlink objects based on the configuration related to the PRS processing window received by the receiving module 801; wherein, the other downlink objects include at least one of the following: other downlink signals, other downlink channels; the other downlink signals are signals other than PRS; the other downlink channels are channels for transmitting signals other than PRS.

[0678] In some possible embodiments, the device further includes a sending module for sending configuration related to the PRS processing window to the terminal.

[0679] In some possible embodiments, the receiving module 801 is further configured to receive target indication information from the first network-side device or terminal; wherein the target indication information is used to indicate that the terminal is allowed to measure PRS within the activated DL BWP.

[0680] In some possible embodiments, the configuration associated with the PRS processing window includes at least one of the following:

[0681] The identifier of the PRS processing window;

[0682] The type of the PRS processing window;

[0683] The PRS associated with the PRS processing window includes at least one of the following: at least one positioning frequency layer identifier, TRP identifier, PRS resource set identifier, and PRS resource identifier.

[0684] The priority information of PRS within the PRS processing window;

[0685] The frequency domain location information associated with PRS within the PRS processing window;

[0686] The first PRS resource and / or the last PRS resource in the PRS processing window shall be at least one of the following: PRS resource identifier, timestamp corresponding to the PRS resource;

[0687] The temporal location information of the PRS processing window;

[0688] PRS time-domain location information.

[0689] In some possible embodiments, the temporal location information of the PRS processing window includes at least one of the following:

[0690] The window length of the PRS processing window;

[0691] The period of the PRS processing window;

[0692] The spacing between adjacent windows of the PRS processing window and the PRS processing window;

[0693] The start time of the PRS processing window;

[0694] The time reference point information of the PRS processing window.

[0695] The unit or granularity of the PRS processing window.

[0696] In some possible embodiments, the time reference point of the PRS processing window is: absolute time, or, based on a second target time point in the timing of the second network-side device.

[0697] In the PRS processing apparatus provided in this application embodiment, the apparatus receives PRS processing window-related configuration from a first network-side device, and then retrieves other downlink objects (i.e., at least one of other downlink signals and other downlink channels) based on the PRS processing window-related configuration. This not only reduces the impact of PRS processing on the transmission of other downlink objects, but also avoids interruptions to the transmission of other downlink objects, thus improving system communication energy efficiency.

[0698] The PRS processing device in this application embodiment can be a device, a device or electronic device with an operating system, or a component, integrated circuit, or chip in a terminal. The device or electronic device can be a mobile terminal or a non-mobile terminal. For example, a mobile terminal can include, but is not limited to, the types of terminals 11 listed above, while a non-mobile terminal can be a server, network attached storage (NAS), personal computer (PC), television (TV), ATM, or self-service machine, etc. This application embodiment does not impose specific limitations.

[0699] The PRS processing apparatus provided in this application embodiment can achieve Figures 2 to 19 The various processes implemented in the method embodiments achieve the same technical effect, and will not be described again here to avoid repetition.

[0700] Optional, such as Figure 24 As shown, this application embodiment also provides a communication device 900, including a processor 901, a memory 902, and a program or instructions stored in the memory 902 and executable on the processor 901. For example, when the communication device 900 is a terminal, the program or instructions executed by the processor 901 implement the various processes of the method embodiment of the above-described PRS processing method and achieve the same technical effect. When the communication device 900 is a network-side device, the program or instructions executed by the processor 901 implement the various processes of the method embodiment of the above-described PRS processing method and achieve the same technical effect. To avoid repetition, further details are omitted here.

[0701] This application embodiment also provides a terminal, including a processor and a communication interface. The communication interface is used to receive PRS configuration; and is also used to receive PRS at a first time domain location and / or receive other downlink objects at a second time domain location according to the PRS configuration; wherein the overlap relationship between the PRS and the second time domain location is related to at least one of the following: the association relationship between the PRS and the other downlink objects and relevant information related to PRS processing; the other downlink objects include at least one of the following: other downlink signals, other downlink channels; the other downlink signals are signals other than the PRS; the other downlink channels are channels for transmitting signals other than the PRS. This terminal embodiment corresponds to the above-described terminal-side method embodiment, and all implementation processes and methods of the above-described method embodiments can be applied to this terminal embodiment and can achieve the same technical effect. Specifically, Figure 25 A schematic diagram of the hardware structure of a terminal to implement an embodiment of this application.

[0702] The terminal 100 includes, but is not limited to, at least some of the following components: radio frequency unit 101, network module 102, audio output unit 103, input unit 104, sensor 105, display unit 106, user input unit 107, interface unit 108, memory 109, and processor 110.

[0703] Those skilled in the art will understand that the terminal 100 may also include a power supply (such as a battery) for supplying power to various components. The power supply may be logically connected to the processor 110 through a power management system, thereby enabling functions such as managing charging, discharging, and power consumption through the power management system. Figure 25 The terminal structure shown does not constitute a limitation on the terminal. The terminal may include more or fewer components than shown, or combine certain components, or have different component arrangements, which will not be elaborated here.

[0704] It should be understood that, in this embodiment, the input unit 104 may include a graphics processing unit (GPU) 1041 and a microphone 1042. The GPU 1041 processes image data of still images or videos obtained by an image capture device (such as a camera) in video capture mode or image capture mode. The display unit 106 may include a display panel 1061, which may be configured in the form of a liquid crystal display, an organic light-emitting diode, or the like. The user input unit 107 includes a touch panel 1071 and other input devices 1072. The touch panel 1071 is also called a touch screen. The touch panel 1071 may include a touch detection device and a touch controller. Other input devices 1072 may include, but are not limited to, a physical keyboard, function keys (such as volume control buttons, power buttons, etc.), a trackball, a mouse, and a joystick, which will not be described in detail here.

[0705] In this embodiment, the radio frequency unit 101 receives downlink data from the network-side device and processes it for the processor 110; additionally, it sends uplink data to the network-side device. Typically, the radio frequency unit 101 includes, but is not limited to, an antenna, at least one amplifier, a transceiver, a coupler, a low-noise amplifier, a duplexer, etc.

[0706] The memory 109 can be used to store software programs or instructions and various data. The memory 109 may primarily include a program or instruction storage area and a data storage area. The program or instruction storage area may store the operating system, application programs or instructions required for at least one function (such as sound playback, image playback, etc.). Furthermore, the memory 109 may include high-speed random access memory and non-volatile memory, which may be read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), or flash memory. For example, at least one disk storage device, flash memory device, or other non-volatile solid-state storage device.

[0707] Processor 110 may include one or more processing units; optionally, processor 110 may integrate an application processor and a modem processor, wherein the application processor mainly handles the operating system, user interface, and applications or instructions, and the modem processor mainly handles wireless communication, such as a baseband processor. It is understood that the aforementioned modem processor may also not be integrated into processor 110.

[0708] The radio frequency unit 101 is configured to receive PRS configuration; the radio frequency unit 101 is also configured to receive PRS at a first time domain location and / or receive other downlink objects at a second time domain location according to the PRS configuration; wherein the overlap relationship between the PRS and the second time domain location is related to at least one of the following: the association relationship between the PRS and the other downlink objects, and relevant information related to PRS processing; the other downlink objects include at least one of the following: other downlink signals, other downlink channels; the other downlink signals are signals other than the PRS; the other downlink channels are channels for transmitting signals other than the PRS.

[0709] In some possible embodiments, the association between the PRS and the other downlink objects includes at least one of the following:

[0710] The priority relationship between the PRS and the other downlink objects;

[0711] The frequency domain positional relationship between the PRS and the other downlink objects.

[0712] In some possible embodiments, the relevant information of the PRS processing includes at least one of the following:

[0713] The first type of PRS processing capability;

[0714] PRS processing type.

[0715] In some possible embodiments, the first PRS processing capability is the terminal's ability to process PRS when there is no MG;

[0716] The type of the first PRS processing capability includes at least one of the following:

[0717] Processing capacity of each terminal;

[0718] Processing capacity of each FR;

[0719] Processing capacity of each band;

[0720] The processing capacity of each carrier;

[0721] Processing capacity of each RB block.

[0722] In some possible embodiments, the PRS processing type is the type of PRS that the terminal processes when there is no MG;

[0723] The PRS processing type includes at least one of the following:

[0724] The type of Per UE;

[0725] Per FR type;

[0726] Types of Per bands;

[0727] Types of Per Carrier;

[0728] Per RB block type.

[0729] In some possible embodiments, the priority relationship between the PRS and the other downlink objects is that the PRS has a higher priority than the other downlink objects.

[0730] In some possible embodiments, the relationship between the frequency domain position of the other downlink object and the frequency domain position of the PRS includes at least one of the following: the frequency domain position of the other downlink object is the same as the frequency domain position of the PRS; or, the frequency domain position of the other downlink object is different from the frequency domain position of the PRS.

[0731] In some possible embodiments, the frequency domain location of the other downlink object is the same as the frequency domain location of the PRS, including at least one of the following:

[0732] The PRS is located on the same carrier as the other downlink objects;

[0733] The PRS is located in the same BWP as the other downlink objects;

[0734] The PRS and the other downlink objects are located at overlapping RB positions.

[0735] In some possible embodiments, the frequency domain location of the other downlink object differs from the frequency domain location of the PRS, including at least one of the following:

[0736] The PRS and the other downlink objects are located on carriers in different frequency ranges (FR);

[0737] The PRS and the other downlink objects are carriers located in different frequency bands within the same frequency range FR;

[0738] The PRS and the other downlink objects are located on carriers in the same frequency band but different carriers;

[0739] The PRS and the other downlink objects are located at non-overlapping RB positions in the same BWP on the same carrier;

[0740] The PRS and the other downlink objects are located on carriers in different frequency bands;

[0741] The carrier of the PRS includes: the carrier that receives the PRS, or the carrier in which the PRS is located, or the carrier in which the activated DL BWP of the PRS is located.

[0742] In some possible embodiments, the overlap between the PRS and the other downlink objects is determined based on at least one of the following:

[0743] If the PRS has a higher priority than the other downlink objects, and the frequency domain positional relationship between the PRS and the other downlink objects satisfies the limitation of the type of the first PRS processing capability or the frequency domain range corresponding to the PRS processing type, then the PRS and the other downlink objects do not overlap.

[0744] If the PRS has a higher priority than the other downlink objects, and the frequency domain positional relationship between the PRS and the other downlink objects does not satisfy the limitation of the type of the first PRS processing capability or the frequency domain range corresponding to the PRS processing type, then the PRS and the other downlink objects may overlap.

[0745] In some possible embodiments, the terminal measures the PRS within an activated downlink BWP.

[0746] In some possible embodiments, the PRS does not overlap with the second time-domain location.

[0747] In some possible embodiments, the non-overlapping of the PRS with the second time-domain location includes at least one of the following:

[0748] The first time domain location and the second time domain location do not overlap.

[0749] The time occupied by the PRS does not overlap with the second time domain position.

[0750] In some possible embodiments, the PRS and the second time-domain location are not overlapped in a manner determined based on at least one of the following: network indication, protocol agreement, UE selection.

[0751] In some possible embodiments, the non-overlapping of the first time domain location and the second time domain location includes at least one of the following:

[0752] When the other downlink objects are located on the same carrier as the PRS, or when the other downlink objects are located on the same BWP as the PRS, the first time domain position and the second time domain position do not overlap;

[0753] If the other downlink object is located on a different carrier than the PRS, and the boundary of the first time domain location at least partially overlaps with the first time unit of the carrier associated with the other downlink object, then the second time domain location does not include the first time unit.

[0754] In some possible embodiments, the time occupied by the PRS does not overlap with the second time-domain location, including at least one of the following:

[0755] If the other downlink object is located on the same carrier as the PRS, or if the other downlink object is located on the same BWP as the PRS, then the second time domain location does not include the second time unit if the boundary of the time occupied by the PRS at least partially overlaps with the second time unit of the carrier.

[0756] If the other downlink object is located on a different carrier than the PRS, and the boundary of the time occupied by the PRS at least partially overlaps with the third time unit of the carrier associated with the other downlink object, then the second time domain location does not include the third time unit.

[0757] In some possible embodiments, the time occupied by PRS includes the time corresponding to the PRS processing window.

[0758] In some possible embodiments, the time occupied by the PRS is related to at least one of the following:

[0759] PRS time-domain location configuration

[0760] The TRP for sending the PRS is offset from the SFN0 of the serving cell and / or reference cell.

[0761] SFN0 offset between serving cell and reference cell

[0762] The TRP that sends the PRS is related to the expected RSTD of the serving cell and / or reference cell.

[0763] The uncertainty of the TRP for sending the PRS and the expected RSTD of the serving cell and / or reference cell.

[0764] Reference cell TRP and serving cell TRP expected RSTD

[0765] The expected RSTD uncertainty of the reference cell TRP and the serving cell TRP,

[0766] Second PRS processing capability

[0767] PRS processing time

[0768] SFN0 service time for the community

[0769] SCS serving the community.

[0770] In some possible embodiments, when the PRS does not overlap with the second time-domain location, the frequency-domain relationship between the PRS and the other downlink objects includes at least one of the following:

[0771] The other downlink objects are carriers located in different frequency ranges (FR) from the PRS;

[0772] The other downlink objects are carriers in different frequency bands of the same frequency range FR as the PRS;

[0773] The other downlink objects are located on different carriers in the same frequency band as the PRS;

[0774] The other downlink objects are carriers located in different frequency bands from the PRS;

[0775] The other downlink objects and the PRS are located on the same BWP of the same carrier, and at non-overlapping RB positions;

[0776] The other downlink objects and the PRS are located on the same BWP on the same carrier, with overlapping RB positions.

[0777] In some possible embodiments, the radio frequency unit 101 is specifically configured to: receive PRS at a first time domain location based on at least one of the timing information of the serving cell and the time units of the serving cell occupied by the subcarrier interval.

[0778] In some possible embodiments, the first time-domain location is associated with at least one of the following:

[0779] PRS time-domain location configuration

[0780] The TRP that sends the PRS is offset from the SFN0 system frame of the serving cell and / or reference cell.

[0781] SFN0 offset between serving cell and reference cell

[0782] The TRP that sends the PRS is related to the expected RSTD of the serving cell and / or reference cell.

[0783] The uncertainty of the TRP for sending the PRS and the expected RSTD of the serving cell and / or reference cell.

[0784] Reference cell TRP and serving cell TRP expected RSTD

[0785] The expected RSTD uncertainty of the reference cell TRP and the serving cell TRP,

[0786] Second PRS processing capability

[0787] PRS processing time

[0788] SFN0 service time for the community

[0789] SCS serving the community.

[0790] In some possible embodiments, the time-domain location configuration of the PRS includes, but is not limited to, one of the following: PRS period, period offset, PRS repetition, PRS subcarrier spacing, PRS pattern, and PRS processing window configuration.

[0791] In some possible embodiments, the second PRS processing capability includes at least one of the following:

[0792] The ability to handle PRS;

[0793] PRS has the capability to handle window-related tasks.

[0794] In some possible embodiments, the first time domain location includes the fourth time unit if the transmission start time and / or transmission end time of the PRS at least partially overlap with the fourth time unit.

[0795] And / or,

[0796] When the transmission start time of the PRS at least partially overlaps with the fourth time unit, the first time domain position includes the fourth time unit and a time unit adjacent to the fourth time unit.

[0797] And / or,

[0798] When the transmission end time of the PRS at least partially overlaps with the fourth time unit, the first time domain location includes the fourth time unit and a time unit adjacent to the fourth time unit.

[0799] In some possible embodiments, the radio frequency unit 101 is specifically configured to: receive other downlink objects at a second time-domain location based on at least one of the timing information of the serving cell and the time units of the serving cell occupied by the subcarrier interval.

[0800] In some possible embodiments, the PRS configuration includes: configuration related to the PRS processing window.

[0801] In some possible embodiments, the configuration related to the PRS processing window is configured by a first network-side device or a second network-side device.

[0802] In some possible embodiments, the configuration associated with the PRS processing window includes at least one of the following: the identifier of the PRS processing window; the type of the PRS processing window; at least one of the following associated with the PRS within the PRS processing window: at least one positioning frequency layer identifier, TRP identifier, PRS resource set identifier, and PRS resource identifier; priority information of the PRS within the PRS processing window; frequency domain location information associated with the PRS within the PRS processing window; at least one of the following of the first PRS resource and / or the last PRS resource within the PRS processing window: PRS resource identifier and timestamp corresponding to the PRS resource; time domain location information of the PRS processing window; and PRS time domain location information.

[0803] In some possible embodiments, the temporal location information of the PRS processing window includes at least one of the following: the window length of the PRS processing window; the period of the PRS processing window; the interval between the adjacent windows of the PRS processing window and the PRS processing window; the start time of the PRS processing window; the time reference point information of the PRS processing window; and the unit or granularity of the PRS processing window.

[0804] In some possible embodiments, when the configuration associated with the PRS processing window is provided by a first network-side device, the time reference point of the PRS processing window is: absolute time, or a first target time point based on the timing of the target network-side device or the target cell.

[0805] In some possible embodiments, when the configuration associated with the PRS processing window is provided by a second network-side device, the time reference point of the PRS processing window is: absolute time, or, based on a second target time point in the timing of the second network-side device.

[0806] In some possible embodiments, the first target time point is one of the following:

[0807] SFN0;

[0808] The starting point of the subframe closest to the start time of the PRS processing window;

[0809] The nearest subframe start point before the start time of the PRS processing window;

[0810] The time slot or symbol start point closest to the start time of the PRS processing window.

[0811] In some possible embodiments, the second target time point is one of the following:

[0812] SFN0;

[0813] The starting point of the subframe closest to the start time of the PRS processing window;

[0814] The nearest subframe start point before the start time of the PRS processing window;

[0815] The time slot or symbol start point closest to the start time of the PRS processing window.

[0816] In some possible embodiments, the method further includes, prior to measuring the PRS:

[0817] The terminal sends its capabilities to the network-side device.

[0818] The terminal capabilities include at least one of the following:

[0819] Does it support measuring PRS within an active DL BWP?

[0820] Does it support measuring PRS using a PRS processing window?

[0821] Does it support measuring PRS using measurement intervals?

[0822] In some possible embodiments, processor 110 is configured to determine, based on first information, that the PRS processing window satisfies at least one of the following:

[0823] Within a positioning frequency layer, a PRS cycle constitutes a PRS processing window, the range of which is from the first PRS resource to the last PRS resource in the PRS cycle.

[0824] Within a positioning frequency layer, PRS of the same period, and PRS of one period constitute a PRS processing window, the range of which is from the first PRS resource to the last PRS resource in the PRS of one period.

[0825] A period of PRS within a PRS resource set constitutes a PRS processing window, the range of which is from the first PRS resource to the last PRS resource in the PRS resource set.

[0826] Within a positioning frequency layer, adjacent first PRS within one cycle constitute a PRS processing window, and the distance between adjacent first PRS does not exceed a first threshold.

[0827] Within a positioning frequency layer, PRS with the same period, adjacent second PRS within a period constitute a PRS processing window, and the distance between adjacent second PRS does not exceed the first threshold.

[0828] Within a positioning frequency layer cycle, the earliest PRS resource and the latest PRS resource constitute a PRS processing window.

[0829] Within the same PRS resource set, PRS from different PRS resource sets belong to different PRS processing windows.

[0830] PRS at different positioning frequency layers belong to different PRS processing windows;

[0831] PRS of different periods within a positioning frequency layer belong to different PRS processing windows.

[0832] In some possible embodiments, the processor 110 is further configured to: if the PRS configuration includes a PRS processing window configuration, then when the terminal enters an active state or an idle state, ignore the PRS processing window configuration, or ignore the scheduling restrictions imposed by the PRS processing window.

[0833] In some possible embodiments, the processor 110 is further configured to: not expect the PRS processing window configuration to be included in the PRS configuration when the terminal is in an active or idle state, and / or ignore PRS scheduling restrictions.

[0834] In some possible embodiments, the radio frequency unit 101 is also configured to receive first indication information from a network-side device;

[0835] Wherein, the first indication information is used to indicate at least one of the following: allowing the terminal to receive PRS within an active DL BWP, allowing the terminal to process PRS within a PRS processing window, enabling PRS scheduling restrictions, and disabling PRS scheduling restrictions.

[0836] In some possible embodiments, the radio frequency unit 101 is also used to send second indication information to the network-side device;

[0837] Wherein, the second indication information is used to indicate at least one of the following:

[0838] The terminal expects to be allowed to receive PRS within an active DL BWP.

[0839] The terminal expects to be allowed to process PRS within a PRS processing window.

[0840] In the terminal provided in this application embodiment, after receiving the PRS configuration, the terminal can receive the PRS at a first time domain location based on the PRS configuration, and / or receive other downlink objects (i.e., at least one of other downlink signals and other downlink channels) at a second time domain location. Since the overlap between the PRS and the second time domain location is related to at least one of the correlation between the PRS and the other downlink objects and the relevant information of the PRS processing, the impact of PRS processing on the transmission of other downlink objects can be reduced, thereby avoiding the interruption of the transmission of other downlink objects and improving the system communication energy efficiency.

[0841] This application embodiment also provides a network-side device, including a processor and a communication interface, wherein:

[0842] The communication interface is used to send PRS processing window related configurations to the second network-side device or terminal; wherein, the PRS processing window related configurations are used by the second network-side device to retrieve other downlink objects; the other downlink objects include at least one of the following: other downlink signals, other downlink channels.

[0843] And / or,

[0844] The communication interface is used to receive configuration related to the PRS processing window from the first network-side device; the processor is used to retrieve other downlink objects based on the configuration related to the PRS processing window received by the communication interface; wherein, the other downlink objects include at least one of the following: other downlink signals, other downlink channels.

[0845] This network-side device embodiment corresponds to the above-described network-side device method embodiment. All implementation processes and methods of the above-described method embodiment can be applied to this network-side device embodiment and can achieve the same technical effect.

[0846] Specifically, embodiments of this application also provide a network-side device. For example... Figure 26 As shown, the network-side device 1100 includes: an antenna 111, a radio frequency (RF) device 112, and a baseband device 113. The antenna 111 is connected to the RF device 112. In the uplink direction, the RF device 112 receives information through the antenna 111 and transmits the received information to the baseband device 113 for processing. In the downlink direction, the baseband device 113 processes the information to be transmitted and sends it to the RF device 112. The RF device 112 processes the received information and transmits it through the antenna 111.

[0847] The aforementioned frequency band processing device can be located in the baseband device 113. The method executed by the network-side device in the above embodiments can be implemented in the baseband device 113, which includes a processor 114 and a memory 115.

[0848] Baseband device 113 may include, for example, at least one baseband board on which multiple chips are disposed, such as Figure 26 As shown, one of the chips, for example, is a processor 114, which is connected to a memory 115 to call the program in the memory 115 and execute the network-side device operations shown in the above method embodiments.

[0849] The baseband device 113 may also include a network interface 116 for exchanging information with the radio frequency device 112, such as a common public radio interface (CPRI).

[0850] Specifically, the network-side device in this embodiment of the invention further includes: instructions or programs stored in memory 115 and executable on processor 114, wherein processor 114 calls the instructions or programs in memory 115 to execute. Figure 22 or Figure 23 The methods executed by each module shown achieve the same technical effect, and to avoid repetition, they will not be described in detail here.

[0851] This application also provides a readable storage medium storing a program or instructions that, when executed by a processor, implement the various processes of the above-described PRS processing method and achieve the same technical effect. To avoid repetition, these will not be described again here.

[0852] The processor mentioned above is the processor in the terminal described in the above embodiments. The readable storage medium includes computer-readable storage media, such as computer read-only memory (ROM), random access memory (RAM), magnetic disk, or optical disk.

[0853] This application embodiment also provides a chip, which includes a processor and a communication interface. The communication interface is coupled to the processor. The processor is used to run programs or instructions to implement the various processes of the above-described PRS processing method embodiment and achieve the same technical effect. To avoid repetition, it will not be described again here.

[0854] It should be understood that the chip mentioned in the embodiments of this application may also be referred to as a system-on-a-chip, system chip, chip system, or system-on-a-chip, etc.

[0855] It should be noted that, in this document, the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such a process, method, article, or apparatus. Without further limitations, an element defined by the phrase "comprising one..." does not exclude the presence of other identical elements in the process, method, article, or apparatus that includes that element. Furthermore, it should be noted that the scope of the methods and apparatuses in the embodiments of this application is not limited to performing functions in the order shown or discussed, but may also include performing functions substantially simultaneously or in the reverse order, depending on the functions involved. For example, the described methods may be performed in a different order than described, and various steps may be added, omitted, or combined. Additionally, features described with reference to certain examples may be combined in other examples.

[0856] Through the above description of the embodiments, those skilled in the art can clearly understand that the methods of the above embodiments can be implemented by means of software plus necessary general-purpose hardware platforms. Of course, they can also be implemented by hardware, but in many cases the former is a better implementation method. Based on this understanding, the technical solution of this application, in essence, or the part that contributes to the prior art, can be embodied in the form of a computer software product. This computer software product is stored in a storage medium (such as ROM / RAM, magnetic disk, optical disk) and includes several instructions to cause a terminal (which may be a mobile phone, computer, server, air conditioner, or network-side device, etc.) to execute the methods described in the various embodiments of this application.

[0857] The embodiments of this application have been described above with reference to the accompanying drawings. However, this application is not limited to the specific embodiments described above. The specific embodiments described above are merely illustrative and not restrictive. Those skilled in the art can make many other forms under the guidance of this application without departing from the spirit and scope of the claims, and all of these forms are within the protection scope of this application.

Claims

1. A method of processing positioning reference signals, PRS, the method comprising: The method includes: The terminal receives the PRS configuration; The terminal receives the PRS at the first time domain location and / or receives other downlink objects at the second time domain location, based on the PRS configuration and the overlap relationship between the PRS and the second time domain location. The overlap relationship between the PRS and the second time-domain location is determined based on the following two factors: the association relationship between the PRS and the other downlink objects, and relevant information processed by the PRS; the overlap relationship is used to characterize whether the PRS restricts the transmission of the other downlink objects. The other downlink objects include at least one of the following: other downlink signals, other downlink channels; The other downlink signals are signals other than PRS; The other downlink channels are channels for transmitting signals other than PRS; The relationship between the PRS and the other downlink objects includes: the priority relationship between the PRS and the other downlink objects, and the frequency domain position relationship between the PRS and the other downlink objects; the relevant information of the PRS processing includes the PRS processing type, which is the type of PRS processing by the terminal when there is no MG.

2. The method according to claim 1, characterized in that, The PRS processing type includes at least one of the following: The type of each terminal; Type of each frequency domain range; The type of each frequency band; The type of each carrier; The type of each RB block.

3. The method of claim 1, wherein, The priority relationship between the PRS and the other downlink objects is that the PRS has a higher priority than the other downlink objects.

4. The method of claim 1, wherein, The relationship between the frequency domain position of the other downlink object and the frequency domain position of the PRS includes at least one of the following: the frequency domain position of the other downlink object is the same as the frequency domain position of the PRS; or, the frequency domain position of the other downlink object is different from the frequency domain position of the PRS.

5. The method of claim 4, wherein, The frequency domain location of the other downlink objects is the same as the frequency domain location of the PRS, including at least one of the following: The PRS is located on the same carrier as the other downlink objects; The PRS is located in the same bandwidth portion (BWP) as the other downlink objects; The PRS and the other downlink objects are located at overlapping RB positions; And / or, The frequency domain location of the other downlink objects differs from the frequency domain location of the PRS, including at least one of the following: The PRS and the other downlink objects are located on carriers in different frequency ranges; The PRS and the other downlink objects are carriers in different frequency bands within the same frequency range; The PRS and the other downlink objects are located on different carriers in the same frequency band; The PRS and the other downlink objects are located at non-overlapping RB positions in the same BWP on the same carrier; The PRS and the other downlink objects are located on carriers in different frequency bands; The carrier of the PRS includes: the carrier that receives the PRS, or the carrier in which the PRS is located, or the carrier in which the activated DL BWP of the PRS is located.

6. The method of claim 1, wherein, The overlap between the PRS and the other downlink objects is determined based on at least one of the following methods: If the PRS has a higher priority than the other downlink objects, and the frequency domain positional relationship between the PRS and the other downlink objects satisfies the limitation of the type of the first PRS processing capability or the frequency domain range corresponding to the PRS processing type, then the PRS and the other downlink objects do not overlap. If the PRS has a higher priority than the other downlink objects, and the frequency domain positional relationship between the PRS and the other downlink objects does not satisfy the limitation of the type of the first PRS processing capability or the frequency domain range corresponding to the PRS processing type, then the PRS and the other downlink objects may overlap.

7. The method of claim 1, wherein, The terminal measures the PRS within the activated downlink BWP.

8. The method of claim 1, wherein, The PRS does not overlap with the second time domain location; Wherein, the PRS and the second time-domain location do not overlap include at least one of the following: The first time domain location and the second time domain location do not overlap. The time occupied by the PRS does not overlap with the second time domain position.

9. The method according to claim 8, characterized in that, The first time-domain location and the second time-domain location do not overlap, including at least one of the following: When the other downlink objects are located on the same carrier as the PRS, or when the other downlink objects are located on the same BWP as the PRS, the first time domain position and the second time domain position do not overlap; If the other downlink object is located on a different carrier than the PRS, and the boundary of the first time domain location at least partially overlaps with the first time unit of the carrier associated with the other downlink object, then the second time domain location does not include the first time unit.

10. The method of claim 8, wherein, The time occupied by the PRS does not overlap with the second time domain location, including at least one of the following: If the other downlink object is located on the same carrier as the PRS, or if the other downlink object is located on the same BWP as the PRS, then the second time domain location does not include the second time unit if the boundary of the time occupied by the PRS at least partially overlaps with the second time unit of the carrier. If the other downlink object is located on a different carrier than the PRS, and the boundary of the time occupied by the PRS at least partially overlaps with the third time unit of the carrier associated with the other downlink object, then the second time domain location does not include the third time unit.

11. The method of claim 8, wherein, The time occupied by the PRS is related to at least one of the following: PRS time-domain location configuration The TRP that sends the PRS is offset from the SFN0 system frame of the serving cell and / or reference cell. SFN0 offset between serving cell and reference cell The TRP that sends the PRS is related to the expected RSTD of the serving cell and / or reference cell. The uncertainty of the TRP for sending the PRS and the expected RSTD of the serving cell and / or reference cell. Reference cell TRP and serving cell TRP expected RSTD The expected RSTD uncertainty of the reference cell TRP and the serving cell TRP, Second PRS processing capability PRS processing time SFN0 service time for the community Subcarrier spacing (SCS) of the serving cell.

12. The method of claim 8, wherein, When the PRS does not overlap with the second time-domain position, the frequency-domain relationship between the PRS and the other downlink objects includes at least one of the following: The other downlink objects are carriers in different frequency ranges from the PRS; The other downlink objects are carriers in different frequency bands within the same frequency range as the PRS; The other downlink objects are located on different carriers in the same frequency band as the PRS; The other downlink objects are carriers located in different frequency bands from the PRS; The other downlink objects and the PRS are located on the same BWP of the same carrier, and at non-overlapping RB positions; The other downlink objects and the PRS are located on the same BWP on the same carrier, with overlapping RB positions.

13. The method of claim 1, wherein, Receiving PRS at the first time domain location includes: The PRS is received at a first time-domain location based on at least one of the timing information of the serving cell and the time unit of the serving cell occupied by the subcarrier interval.

14. The method of claim 1, wherein, The first time-domain location is associated with at least one of the following: PRS time-domain location configuration The TRP that sends the PRS is offset from the SFN0 system frame of the serving cell and / or reference cell. SFN0 offset between serving cell and reference cell The TRP that sends the PRS is related to the expected RSTD of the serving cell and / or reference cell. The uncertainty of the TRP for sending the PRS and the expected RSTD of the serving cell and / or reference cell. Reference cell TRP and serving cell TRP expected RSTD The expected RSTD uncertainty of the reference cell TRP and the serving cell TRP, Second PRS processing capability PRS processing time SFN0 service time for the community SCS serving the community.

15. The method of claim 11, wherein, The second PRS processing capability includes at least one of the following: The ability to handle PRS; PRS has the capability to handle window-related tasks.

16. The method according to claim 1, characterized in that, If the transmission start time and / or transmission end time of the PRS at least partially overlap with the fourth time unit, the first time domain location includes the fourth time unit. And / or, When the transmission start time of the PRS at least partially overlaps with the fourth time unit, the first time domain position includes the fourth time unit and a time unit adjacent to the fourth time unit. And / or, When the transmission end time of the PRS at least partially overlaps with the fourth time unit, the first time domain location includes the fourth time unit and a time unit adjacent to the fourth time unit.

17. The method of claim 1, wherein, Receiving other downlink objects at the second time domain location includes: Other downlink objects are received at a second time-domain location based on at least one of the timing information of the serving cell and the time unit of the serving cell occupied by the subcarrier interval.

18. The method of claim 1, wherein, The PRS configuration includes: configurations related to the PRS processing window; The configuration related to the PRS processing window includes at least one of the following: The identifier of the PRS processing window; The type of the PRS processing window; The PRS associated with the PRS within the PRS processing window includes at least one of the following: at least one positioning frequency layer identifier, TRP identifier, PRS resource set identifier, and PRS resource identifier. The priority information of PRS within the PRS processing window; The frequency domain location information associated with PRS within the PRS processing window; The first PRS resource and / or the last PRS resource in the PRS processing window shall be at least one of the following: PRS resource identifier, timestamp corresponding to the PRS resource; The temporal location information of the PRS processing window; PRS time-domain location information.

19. The method of claim 18, wherein, The temporal location information of the PRS processing window includes at least one of the following: The window length of the PRS processing window; The period of the PRS processing window; The spacing between adjacent windows of the PRS processing window and the PRS processing window; The start time of the PRS processing window; The time reference point information of the PRS processing window; The unit or granularity of the PRS processing window.

20. The method of claim 19, wherein, When the configuration related to the PRS processing window is provided by the first network-side device, the time reference point of the PRS processing window is: absolute time, or, based on the first target time point in the timing of the target network-side device or the target cell; The first target time point is one of the following: SFN0; The starting point of the subframe closest to the start time of the PRS processing window; The nearest subframe start point before the start time of the PRS processing window; The time slot or symbol start point closest to the start time of the PRS processing window.

21. The method of claim 19, wherein, When the configuration related to the PRS processing window is provided by a second network-side device, the time reference point of the PRS processing window is: absolute time, or, based on a second target time point in the timing of the second network-side device; The second target time point is one of the following: SFN0; The starting point of the subframe closest to the start time of the PRS processing window; The nearest subframe start point before the start time of the PRS processing window; The time slot or symbol start point closest to the start time of the PRS processing window.

22. The method of claim 1, wherein, The method further includes the following steps prior to measuring the PRS: The terminal sends its capabilities to the network-side device. The terminal capabilities include at least one of the following: Does it support measuring PRS within an active DL BWP? Does it support measuring PRS using a PRS processing window? Does it support measuring PRS using measurement intervals? 23. The method of claim 1, wherein, The method further includes: Based on the first information, the terminal determines that the PRS processing window satisfies at least one of the following: Within a positioning frequency layer, a PRS cycle constitutes a PRS processing window, the range of which is from the first PRS resource to the last PRS resource in the PRS cycle. Within a positioning frequency layer, PRS of the same period are defined as a PRS processing window. The range of the PRS processing window is from the first PRS resource to the last PRS resource in the PRS of the same period. A PRS in a period within a PRS resource set constitutes a PRS processing window, the range of which is from the first PRS resource to the last PRS resource in the PRS resource set. Within a positioning frequency layer, adjacent first PRS within one cycle constitute a PRS processing window, and the distance between adjacent first PRS does not exceed a first threshold. Within a positioning frequency layer, PRS with the same period, adjacent second PRS within a period constitute a PRS processing window, and the distance between adjacent second PRS does not exceed the first threshold. Within a positioning frequency layer cycle, the earliest PRS resource and the latest PRS resource constitute a PRS processing window. Within the same PRS resource set, PRS from different PRS resource sets belong to different PRS processing windows. PRS at different positioning frequency layers belong to different PRS processing windows; PRS of different periods within a positioning frequency layer belong to different PRS processing windows.

24. The method of claim 1, wherein, The method further includes: If the PRS configuration includes a PRS processing window configuration, then when the terminal enters an active state or an idle state, the terminal ignores the PRS processing window configuration, or the terminal ignores the scheduling restrictions corresponding to the PRS processing window. And / or, When the terminal is in an active or idle state, the terminal does not expect the PRS processing window configuration to be included in the PRS configuration, and / or the terminal ignores the PRS scheduling restrictions.

25. The method of claim 1, wherein, Before the terminal receives the PRS, the method further includes: The terminal receives first indication information from the network-side device; And / or, The terminal sends a second instruction message to the network-side device; Wherein, the first indication information is used to indicate at least one of the following: The terminal is allowed to receive PRS within the activated DL BWP. The terminal is allowed to process PRS within the PRS processing window. Enable PRS scheduling constraints. PRS scheduling restrictions are prohibited; The second indication information is used to indicate at least one of the following: The terminal expects to be allowed to receive PRS within an active DL BWP. The terminal expects to be allowed to process PRS within a PRS processing window.

26. A method of processing a positioning reference signal (PRS), the method comprising: The method includes: The first network-side device sends the configuration related to the PRS processing window to the second network-side device or terminal; The configuration related to the PRS processing window is used by the second network-side device to retrieve other downlink objects; The other downlink objects include at least one of the following: other downlink signals, other downlink channels; The other downlink signals are signals other than PRS; The other downlink channels are channels for transmitting signals other than PRS; The overlap relationship between the PRS configured in the configuration and the second time domain location is determined based on the following two factors: the association relationship between the PRS and the other downlink objects, and the relevant information of PRS processing. The relationship between the PRS and the other downlink objects includes: the priority relationship between the PRS and the other downlink objects, and the frequency domain position relationship between the PRS and the other downlink objects; the relevant information of the PRS processing includes the PRS processing type, which is the type of PRS processing by the terminal when there is no MG. The overlap relationship is used to characterize whether the PRS restricts the transmission of other downlink objects.

27. The method of claim 26, wherein, After the first network-side device sends the PRS processing window-related configuration to the second network-side device or the terminal, the method further includes: The first network-side device sends an activation instruction for the PRS processing window to the second network-side device; The activation indication includes at least one of the following: Activation identifier; The effective time of the PRS processing window; The time of the first PRS transmission when the PRS processing window takes effect. The activation identifier is used to request the activation of the PRS processing window; The effective time of the processing window includes at least one of the following: start effective time, end effective time, and effective duration.

28. The method of claim 26, wherein, The configuration related to the PRS processing window includes at least one of the following: The identifier of the PRS processing window; The type of the PRS processing window; The PRS associated with the PRS within the PRS processing window includes at least one of the following: at least one positioning frequency layer identifier, TRP identifier, PRS resource set identifier, and PRS resource identifier. The priority information of PRS within the PRS processing window; The frequency domain position information associated within the PRS processing window; The first PRS resource and / or the last PRS resource in the PRS processing window shall be at least one of the following: PRS resource identifier, timestamp corresponding to the PRS resource; The temporal location information of the PRS processing window; PRS time-domain location information.

29. The method of claim 28, wherein, The temporal location information of the PRS processing window includes at least one of the following: The window length of the PRS processing window; The period of the PRS processing window; The spacing between adjacent windows of the PRS processing window and the PRS processing window; The start time of the PRS processing window; The time reference point information of the PRS processing window; The unit or granularity of the PRS processing window; The time reference point of the PRS processing window is: absolute time, or, based on the first target time point in the timing of the target network-side device or the target cell.

30. A method of processing a positioning reference signal (PRS), the method comprising: The method includes: The second network-side device receives the configuration related to the PRS processing window from the first network-side device; The second network-side device retrieves other downlink objects based on the configuration related to the PRS processing window; The other downlink objects include at least one of the following: other downlink signals, other downlink channels; The other downlink signals are signals other than PRS; The other downlink channels are channels for transmitting signals other than PRS; The overlap relationship between the configured PRS and the second time domain location is related to the following two factors: the association relationship between the PRS and the other downlink objects, and the relevant information of PRS processing. The relationship between the PRS and the other downlink objects includes: the priority relationship between the PRS and the other downlink objects, and the frequency domain position relationship between the PRS and the other downlink objects; the relevant information of the PRS processing includes the PRS processing type, which is the type of PRS processed by the terminal when there is no MG. The overlap relationship is used to characterize whether the PRS restricts the transmission of other downlink objects.

31. The method of claim 30, wherein, After the second network-side device receives the PRS processing window-related configuration from the first network-side device, the method further includes: The second network-side device sends the configuration related to the PRS processing window to the terminal.

32. The method of claim 30, wherein, The method further includes: The second network-side device receives target indication information from the first network-side device or the terminal; The target indication information is used to indicate that the terminal is allowed to measure PRS within the activated DL BWP.

33. The method of claim 30, wherein, The configuration related to the PRS processing window includes at least one of the following: The identifier of the PRS processing window; The type of the PRS processing window; The PRS associated with the PRS within the PRS processing window includes at least one of the following: at least one positioning frequency layer identifier, TRP identifier, PRS resource set identifier, and PRS resource identifier. The priority information of PRS within the PRS processing window; The frequency domain location information associated with PRS within the PRS processing window; The first PRS resource and / or the last PRS resource in the PRS processing window shall be at least one of the following: PRS resource identifier, timestamp corresponding to the PRS resource; The temporal location information of the PRS processing window; PRS time-domain location information.

34. The method of claim 30, wherein, The temporal location information of the PRS processing window includes at least one of the following: The window length of the PRS processing window; The period of the PRS processing window; The spacing between adjacent windows of the PRS processing window and the PRS processing window; The start time of the PRS processing window; The time reference point information of the PRS processing window; The unit or granularity of the PRS processing window; The time reference point of the PRS processing window is: absolute time, or, based on the second target time point in the timing of the second network-side device.

35. An apparatus for processing PRS, the apparatus comprising: The device includes: The first receiving module is used to receive PRS configuration; The second receiving module is configured to receive the PRS at the first time domain position based on the PRS configuration received by the first receiving module and the overlap relationship between the PRS and the second time domain position, and / or receive other downlink objects at the second time domain position. The overlap relationship between the PRS and the second time domain location is determined based on the following two factors: the association relationship between the PRS and the other downlink objects, and the relevant information processed by the PRS. The other downlink objects include at least one of the following: other downlink signals, other downlink channels; The other downlink signals are signals other than PRS; The other downlink channels are channels for transmitting signals other than PRS; The relationship between the PRS and the other downlink objects includes: the priority relationship between the PRS and the other downlink objects, and the frequency domain position relationship between the PRS and the other downlink objects; the relevant information of the PRS processing includes the PRS processing type, which is the type of PRS processed by the terminal when there is no MG. The overlap relationship is used to characterize whether the PRS restricts the transmission of other downlink objects.

36. An apparatus for processing PRS, the apparatus comprising: The device includes: The sending module is used to send the configuration related to the PRS processing window to the second network-side device or terminal; The configuration related to the PRS processing window is used by the second network-side device to retrieve other downlink objects; the other downlink objects include at least one of the following: other downlink signals, other downlink channels; The other downlink signals are signals other than PRS; The other downlink channels are channels for transmitting signals other than PRS; The overlap relationship between the PRS configured in the configuration and the second time domain location is determined based on the following two factors: the association relationship between the PRS and the other downlink objects, and the relevant information of PRS processing. The relationship between the PRS and the other downlink objects includes: the priority relationship between the PRS and the other downlink objects, and the frequency domain position relationship between the PRS and the other downlink objects; the relevant information of the PRS processing includes the PRS processing type, which is the type of PRS processing by the terminal when there is no MG. The overlap relationship is used to characterize whether the PRS restricts the transmission of other downlink objects.

37. An apparatus for processing PRS, the apparatus comprising: The device includes: The receiving module is used to receive configurations related to the PRS processing window from the first network-side device; The execution module is used to retrieve other downlink objects based on the configuration related to the PRS processing window received by the receiving module; The other downlink objects include at least one of the following: other downlink signals, other downlink channels; The other downlink signals are signals other than PRS; The other downlink channels are channels for transmitting signals other than PRS; The overlap relationship between the PRS configured in the configuration and the second time domain location is determined based on the following two factors: the association relationship between the PRS and the other downlink objects, and the relevant information of PRS processing. The relationship between the PRS and the other downlink objects includes: the priority relationship between the PRS and the other downlink objects, and the frequency domain position relationship between the PRS and the other downlink objects; the relevant information of the PRS processing includes the PRS processing type, which is the type of PRS processed by the terminal when there is no MG. The overlap relationship is used to characterize whether the PRS restricts the transmission of other downlink objects.

38. A terminal, characterized by It includes a processor, a memory, and a program or instructions stored in the memory and executable on the processor, wherein the program or instructions, when executed by the processor, implement the steps of the processing method of PRS as described in any one of claims 1 to 25.

39. A network-side device, comprising: It includes a processor, a memory, and a program or instructions stored in the memory and executable on the processor, wherein the program or instructions, when executed by the processor, implement the PRS processing method as described in any one of claims 26 to 29, or the steps of the PRS processing method as described in any one of claims 30 to 34.

40. A readable storage medium characterized by, The readable storage medium stores a program or instructions that, when executed by a processor, implement the PRS processing method as described in any one of claims 1 to 25, or the PRS processing method as described in any one of claims 26 to 29, or the steps of the PRS processing method as described in any one of claims 30 to 34.

Images