Positioning-reference-unit disassociation method, and terminal, network device and storage medium

Abstract

The present disclosure relates to the technical field of communications, in particular to a positioning-reference-unit disassociation method, and a terminal, a network device and a storage medium. The positioning-reference-unit disassociation method comprises: recording slice-related information; and sending the slice-related information to a network device. In the present disclosure, a terminal can record slice-related information, and then send the slice-related information to a network device. On this basis, the network device can relatively and comprehensively determine the applicability of a slice to the terminal on the basis of the slice-related information, such that the slice is rationally deployed to appropriately serve a service of the terminal, thereby ensuring a good communication effect of the service.

Description

Positioning reference unit association removal method, terminal, network device and storage medium Technical Field

[0001] The present disclosure relates to the field of communication technology, and in particular to a positioning reference unit de-association method, a terminal, a network device, and a storage medium. Background Art

[0002] The Positioning Reference Unit (PRU) can be used to locate other devices. To this end, the PRU needs to be associated with the Location Management Function (LMF) through a PRU association operation. The PRU association operation can be performed through the control plane (Control Plane) and / or the user plane (User Plane). If a PRU association request is sent to the LMF through the user plane, the Access Management Function (AMF) may be unable to perform the PRU verification operation.

[0003] Summary of the Invention

[0004] The embodiments of the present disclosure propose a positioning reference unit association removal method, terminal, network device and storage medium to solve the technical problem in the related art that sending a PRU association request to the LMF through the user may cause the AMF to be unable to perform the PRU verification operation.

[0005] According to a first aspect of an embodiment of the present disclosure, a positioning reference unit (PRU) association disassociation method is proposed, which is executed by a first device. The method includes: receiving a first message from a second device via a user plane, where the first message is used to instruct the first device to perform a positioning reference unit (PRU) association disassociation operation with the second device; and sending a second message to a third device, where the second message is used to request the third device to perform a PRU verification operation.

[0006] According to a second aspect of an embodiment of the present disclosure, a positioning reference unit association disassociation method is proposed, which is executed by a second device. The method includes: determining to perform a PRU association disassociation operation through a user plane; sending a first message to a first device through the user plane, wherein the first message is used to instruct the first device to perform a positioning reference unit PRU association disassociation operation with the second device, so that the second device sends a second message to a third device, wherein the second message is used to request the third device to perform a PRU verification operation.

[0007] According to a third aspect of an embodiment of the present disclosure, a positioning reference unit association disassociation method is proposed, which is executed by a third device. The method includes: receiving a second message from a first device, the second message being used to request execution of a positioning reference unit PRU verification operation, the second message being sent by the second device in response to receiving a first message from the first device through a user plane, the first message being used to instruct the first device to perform a PRU association disassociation operation with the second device.

[0008] According to a fourth aspect of an embodiment of the present disclosure, a positioning reference unit association release device is proposed, the device comprising: a transceiver module for receiving a first message from a second device through a user plane, the first message being used to instruct the first device to perform a positioning reference unit PRU association release operation with the second device; the transceiver module is further used to send a second message to a third device, the second message being used to request the third device to perform a PRU verification operation.

[0009] According to a fifth aspect of an embodiment of the present disclosure, a positioning reference unit association release device is proposed, the device including: a processing module, used to determine whether to perform a PRU association release operation through a user plane; a transceiver module, used to send a first message to a first device through the user plane, the first message being used to instruct the first device to perform a positioning reference unit PRU association release operation with the second device, so that the second device sends a second message to a third device, the second message being used to request the third device to perform a PRU verification operation.

[0010] According to the sixth aspect of an embodiment of the present disclosure, a positioning reference unit association release device is proposed, the device including: a transceiver module for receiving a second message from a first device, the second message being used to request execution of a positioning reference unit PRU verification operation, the second message being sent by the second device in response to receiving a first message from the first device through a user plane, the first message being used to instruct the first device to perform a PRU association release operation with the second device; and a processing module for executing the PRU verification operation.

[0011] According to a seventh aspect of an embodiment of the present disclosure, a terminal is proposed, comprising: one or more processors; a memory coupled to the processor, the memory storing executable instructions, wherein the executable instructions, when executed by the processor, cause the terminal to execute the positioning reference unit association decoupling method described in the second aspect above.

[0012] According to an eighth aspect of an embodiment of the present disclosure, an access network device is proposed, comprising: one or more processors; a memory coupled to the processor, the memory storing executable instructions, wherein the executable instructions, when executed by the processor, cause the access network device to execute the positioning reference unit association decoupling method described in the second aspect above.

[0013] According to the ninth aspect of the embodiments of the present disclosure, a core network device is proposed, comprising: one or more processors; a memory coupled to the processor, the memory storing executable instructions, wherein the executable instructions, when executed by the processor, enable the core network device to execute the positioning reference unit association decoupling method described in the first and / or third aspects above.

[0014] According to a tenth aspect of an embodiment of the present disclosure, a communication system is proposed, comprising a first device, a second device, and a third device, wherein the first device is configured to implement the positioning reference unit association decoupling method described in the first aspect, the second device is configured to implement the positioning reference unit association decoupling method described in the second aspect, and the third device is configured to implement the positioning reference unit association decoupling method described in the third aspect.

[0015] According to an eleventh aspect of an embodiment of the present disclosure, a storage medium is proposed, which stores instructions. When the instructions are executed on a communication device, the communication device executes the positioning reference unit association removal method described in the first, second or third aspect above.

[0016] In the above embodiment, when the serving LMF receives a PRU disassociation request from the second device through the user plane, it may first send a PRU verification request to the serving AMF to perform a PRU verification operation on the second device. Accordingly, whether to perform the PRU disassociation operation on the second device can be determined based on the PRU verification result of the second device, thereby avoiding the LMF from performing the disassociation operation on non-PRU devices, saving communication resources and power consumption. BRIEF DESCRIPTION OF THE DRAWINGS

[0017] In order to more clearly illustrate the technical solutions in the embodiments of the present disclosure, the following briefly introduces the drawings required for use in the description of the embodiments. Obviously, the drawings described below are only some embodiments of the present disclosure. For ordinary technicians in this field, other drawings can be obtained based on these drawings without any creative work.

[0018] FIG1 is a schematic diagram showing the architecture of a communication system according to an embodiment of the present disclosure.

[0019] FIG2 is an interactive schematic diagram illustrating a method for disassociating a positioning reference unit according to an embodiment of the present disclosure.

[0020] FIG3A is a schematic flowchart illustrating a method for disassociating a positioning reference unit according to an embodiment of the present disclosure.

[0021] FIG3B is a schematic flowchart illustrating a method for disassociating a positioning reference unit according to an embodiment of the present disclosure.

[0022] FIG4 is a schematic flowchart showing a method for disassociating a positioning reference unit according to an embodiment of the present disclosure.

[0023] FIG5 is a schematic flowchart showing a method for disassociating a positioning reference unit according to an embodiment of the present disclosure.

[0024] FIG6 is a schematic block diagram showing the apparatus structure of a first device according to an embodiment of the present disclosure.

[0025] FIG7 is a schematic block diagram showing the structure of a second device according to an embodiment of the present disclosure.

[0026] FIG8 is a schematic block diagram showing the apparatus structure of a third device according to an embodiment of the present disclosure.

[0027] FIG9 is a schematic structural diagram of a communication device proposed in an embodiment of the present disclosure.

[0028] FIG10 is a schematic diagram of the structure of a chip proposed in an embodiment of the present disclosure. DETAILED DESCRIPTION

[0029] Embodiments of the present disclosure provide a positioning reference unit de-association method, a terminal, a network device, and a storage medium.

[0030] In a first aspect, an embodiment of the present disclosure proposes a positioning reference unit association disassociation method, which is executed by a first device, and the method includes: receiving a first message from a second device through a user plane, the first message being used to instruct the first device to perform a positioning reference unit PRU association disassociation operation with the second device; and sending a second message to a third device, the second message being used to request the third device to perform a PRU verification operation.

[0031] In the above embodiment, when the serving LMF receives a PRU disassociation request from the second device through the user plane, it may first send a PRU verification request to the serving AMF to perform a PRU verification operation on the second device. Accordingly, whether to perform the PRU disassociation operation on the second device can be determined based on the PRU verification result of the second device, thereby avoiding the LMF from performing the disassociation operation on non-PRU devices, saving communication resources and power consumption.

[0032] In conjunction with some embodiments of the first aspect, in some embodiments, the first message is a message using a user plane positioning protocol; wherein the user plane positioning protocol may include at least one of the following: Location Service User Plane Protocol LCS-UPP; Secure User Plane Positioning SUPL protocol.

[0033] In combination with some embodiments of the first aspect. In some embodiments, the first message is further used to indicate at least one of the following: a first device identifier, the first device identifier being a device identifier corresponding to the first device; a second device identifier, the second device identifier being a device identifier corresponding to the second device; first indication information, the first indication information being used to indicate that the second device is a PRU; and a PRU association release request.

[0034] In combination with some embodiments of the first aspect. In some embodiments, the second message is an access and mobility management function AMF service message of the control plane.

[0035] In combination with some embodiments of the first aspect. In some embodiments, the second message is further used to indicate at least one of the following: a first device identifier, the first device identifier being a device identifier corresponding to the first device; a second device identifier, the second device identifier being a device identifier corresponding to the second device; first indication information, the first indication information being used to indicate that the second device is a PRU; and a PRU association release request.

[0036] In combination with some embodiments of the first aspect, in some embodiments, the second device identifier includes at least one of the following: a Subscription Hidden Identity (SUCI); a Subscription Permanent Identity (SUPI); a General Public User Identity (GPSI); or an application layer identifier.

[0037] In combination with some embodiments of the first aspect, in some embodiments, the PRU association release request includes second indication information, where the second indication information is used to indicate whether a confirmation message corresponding to the PRU association release request is expected to be received.

[0038] In combination with some embodiments of the first aspect, in some embodiments, the method further includes: receiving a third message from the third device, the third message being used to indicate a PRU verification result, wherein the PRU verification result is obtained by the third device after performing the PRU verification operation.

[0039] In combination with some embodiments of the first aspect. In some embodiments, the third message is further used to indicate at least one of the following: a first device identifier, the third device identifier is a device identifier corresponding to the first device; a second device identifier, the second device identifier is a device identifier corresponding to the second device; first indication information, the first indication information is used to indicate that the second device supports the PRU function; and the PRU verification result.

[0040] In combination with some embodiments of the first aspect. In some embodiments, the third message is an AMF service message of the control plane.

[0041] In combination with some embodiments of the first aspect, in some embodiments, the PRU verification result is verification failure, and the third message is further used to indicate the reason for the verification failure.

[0042] In combination with some embodiments of the first aspect, in some embodiments, the PRU verification result is used to determine whether the device corresponding to the second device identifier is a PRU.

[0043] In combination with some embodiments of the first aspect, in some embodiments, the method further includes: determining whether the first device is associated with the second device.

[0044] In combination with some embodiments of the first aspect, in some embodiments, the method further includes: determining a result of disassociating the first device from the second device; and sending a fourth message to the second device, where the fourth message is used to indicate a result of disassociating the first device from the second device.

[0045] In combination with some embodiments of the first aspect, in some embodiments, sending the fourth message to the second device includes: determining that the first message is used to indicate an expectation to receive a confirmation message corresponding to the PRU association release request, and sending the fourth message to the second device.

[0046] In combination with some embodiments of the first aspect, in some embodiments, the fourth message is a message using a user plane positioning protocol; wherein the user plane positioning protocol may include at least one of the following: Location Service User Plane Protocol LCS-UPP; Secure User Plane Positioning SUPL protocol.

[0047] In combination with some embodiments of the first aspect. In some embodiments, the fourth message is further used to indicate at least one of the following: a first device identifier, the first device identifier is a device identifier corresponding to the first device; a second device identifier, the second device identifier is a device identifier corresponding to the second device; first indication information, the first indication information is used to indicate that the second device supports the PRU function; a PRU association release response, the PRU association release response is used to indicate the result of the association release between the first device and the second device.

[0048] In combination with some embodiments of the first aspect, in some embodiments, the second device is a location management function LMF.

[0049] In combination with some embodiments of the first aspect, in some embodiments, the third device is an AMF.

[0050] In the second aspect, an embodiment of the present disclosure proposes a positioning reference unit association disassociation method, which is executed by a second device, and the method includes: determining to perform a PRU association disassociation operation through a user plane; sending a first message to a first device through the user plane, wherein the first message is used to instruct the first device to perform a positioning reference unit PRU association disassociation operation with the second device, so that the first device sends a second message to a third device, and the second message is used to request the third device to perform a PRU verification operation.

[0051] In combination with some embodiments of the second aspect. In some embodiments, the first message is further used to indicate at least one of the following: a first device identifier, the first device identifier being a device identifier corresponding to the first device; a second device identifier, the second device identifier being a device identifier corresponding to the second device; first indication information, the first indication information being used to indicate that the second device is a PRU; and a PRU association release request.

[0052] In combination with some embodiments of the second aspect, in some embodiments, the method further includes: receiving a fourth message from the first device, where the fourth message is used to indicate a result of disassociation between the first device and the second device.

[0053] In conjunction with some embodiments of the second aspect, in some embodiments, the fourth message is a message using a user plane positioning protocol; wherein the user plane positioning protocol may include at least one of the following: Location Service User Plane Protocol LCS-UPP; Secure User Plane Positioning SUPL protocol.

[0054] In combination with some embodiments of the second aspect. In some embodiments, the fourth message is further used to indicate at least one of the following: a first device identifier, the first device identifier is a device identifier corresponding to the first device; a second device identifier, the second device identifier is a device identifier corresponding to the second device; first indication information, the first indication information is used to indicate that the second device supports the PRU function; a PRU association release response, the PRU association release response is used to indicate the result of the association release between the first device and the second device.

[0055] In a third aspect, an embodiment of the present disclosure proposes a positioning reference unit association disassociation method, which is executed by a third device, and the method includes: receiving a second message from a first device, the second message being used to request execution of a positioning reference unit PRU verification operation, the second message being sent by the second device after receiving a first message from the first device through a user plane, the first message being used to instruct the first device to perform a PRU association disassociation operation with the second device; and executing the PRU verification operation.

[0056] In combination with some embodiments of the third aspect. In some embodiments, the second message is further used to indicate at least one of the following: a first device identifier, the first device identifier being a device identifier corresponding to the first device; a second device identifier, the second device identifier being a device identifier corresponding to the second device; first indication information, the first indication information being used to indicate that the second device is a PRU; and a PRU association release request.

[0057] In combination with some embodiments of the third aspect, in some embodiments, the method further includes: sending a third message to the first device, where the third message is used to indicate a PRU verification result obtained after the third device performs the PRU verification operation.

[0058] In combination with some embodiments of the third aspect. In some embodiments, the third message is further used to indicate at least one of the following: a first device identifier, the third device identifier is a device identifier corresponding to the first device; a second device identifier, the second device identifier is a device identifier corresponding to the second device; first indication information, the first indication information is used to indicate that the second device supports the PRU function; and the PRU verification result.

[0059] In conjunction with some embodiments of the third aspect, in some embodiments, the PRU verification result is verification failure, and the third message is further used to indicate the reason for the verification failure.

[0060] In a fourth aspect, a positioning reference unit association de-association device is proposed, the device comprising: a transceiver module for receiving a first message from a second device through a user plane, the first message being used to instruct the positioning reference unit association device to perform a positioning reference unit PRU association de-association operation with the second device; the transceiver module is also used to send a second message to a third device, the second message being used to request the third device to perform a PRU verification operation.

[0061] In the fifth aspect, a positioning reference unit association release device is proposed, which includes: a processing module, used to determine whether to perform a PRU association release operation through a user plane; a transceiver module, used to send a first message to a first device through the user plane, and the first message is used to instruct the first device to perform a positioning reference unit PRU association release operation with the positioning reference unit association device, so that the first device sends a second message to a third device, and the second message is used to request the third device to perform a PRU verification operation.

[0062] In the sixth aspect, a positioning reference unit association release device is proposed, and the device includes: a transceiver module for receiving a second message from a first device, the second message is used to request to perform a positioning reference unit PRU verification operation, the second message is sent by the second device after receiving the first message from the first device through the user plane, and the first message is used to instruct the first device and the second device to perform a PRU association release operation; a processing module for performing the PRU verification operation.

[0063] In the seventh aspect, a terminal is proposed, comprising: one or more processors; a memory coupled to the processor, the memory storing executable instructions, wherein when the executable instructions are executed by the processor, the terminal executes the positioning reference unit association decoupling method described in the second aspect and the optional embodiment of the second aspect.

[0064] In the eighth aspect, an access network device is proposed, comprising: one or more processors; a memory coupled to the processor, the memory storing executable instructions, wherein when the executable instructions are executed by the processor, the access network device executes the positioning reference unit association disassociation method described in the second aspect and the optional embodiment of the second aspect.

[0065] In the ninth aspect, a core network device is proposed, comprising: one or more processors; a memory coupled to the processor, the memory storing executable instructions, wherein when the executable instructions are executed by the processor, the core network device executes the positioning reference unit association decoupling method described in the first and third aspects, and the optional embodiments of the first and third aspects.

[0066] In the tenth aspect, an embodiment of the present disclosure proposes a communication device, which includes: one or more processors; a memory coupled to the processor, on which executable instructions are stored, wherein when the executable instructions are executed by the processor, the processor calls the executable instructions so that the communication device executes the positioning reference unit association decoupling method described in the first aspect, the second aspect and the third aspect, and the optional embodiments of the first aspect, the second aspect and the third aspect.

[0067] In the eleventh aspect, an embodiment of the present disclosure proposes a communication system, which includes: a first device, a second device and a third device; wherein the first device is configured to execute the method described in the first aspect and the optional embodiment of the first aspect, the second device is configured to execute the method described in the second aspect and the optional embodiment of the second aspect, and the third device is configured to execute the method described in the third aspect and the optional embodiment of the third aspect.

[0068] In the twelfth aspect, an embodiment of the present disclosure proposes a storage medium, which stores instructions. When the instructions are executed on a communication device, the communication device executes the methods described in the first, second and third aspects, as well as the optional embodiments of the first, second and third aspects.

[0069] In the thirteenth aspect, an embodiment of the present disclosure proposes a program product. When the program product is executed by a communication device, the communication device executes the method described in the first, second and third aspects, as well as the optional embodiments of the first, second and third aspects.

[0070] In the fourteenth aspect, an embodiment of the present disclosure proposes a computer program, which, when executed on a computer, enables the computer to execute the methods described in the first, second and third aspects, as well as the optional embodiments of the first, second and third aspects.

[0071] It is understandable that the above-mentioned terminals, network devices, communication devices, communication systems, storage media, program products, and computer programs are all used to execute the methods proposed in the embodiments of the present disclosure. Therefore, the beneficial effects that can be achieved can refer to the beneficial effects of the corresponding methods and will not be repeated here.

[0072] The disclosed embodiments provide a method for disassociating a positioning reference unit, a terminal, a network device, and a storage medium. In some embodiments, the terms "information sending method," "information receiving method," "information processing method," and "communication method" are interchangeable; the terms "terminal," "network device," "information processing device," and "communication device" are interchangeable; and the terms "information processing system" and "communication system" are interchangeable.

[0073] The embodiments of the present disclosure are not exhaustive and are merely illustrative of some embodiments, and are not intended to be a specific limitation on the scope of protection of the present disclosure. In the absence of contradiction, each step in a certain embodiment can be implemented as an independent embodiment, and the steps can be arbitrarily combined. For example, a solution after removing some steps in a certain embodiment can also be implemented as an independent embodiment, and the order of the steps in a certain embodiment can be arbitrarily exchanged. In addition, the optional embodiments in a certain embodiment can be arbitrarily combined; in addition, the embodiments can be arbitrarily combined. For example, some or all steps of different embodiments can be arbitrarily combined, and a certain embodiment can be arbitrarily combined with the optional embodiments of other embodiments.

[0074] In each embodiment of the present disclosure, unless otherwise specified or provided for by logic, the terms and / or descriptions between the embodiments are consistent and can be referenced by each other. The technical features in different embodiments can be combined to form a new embodiment based on their inherent logical relationships.

[0075] The terms used in the embodiments of the present disclosure are only for the purpose of describing specific embodiments and are not intended to limit the present disclosure.

[0076] In the embodiments of the present disclosure, unless otherwise specified, elements expressed in the singular form, such as "a", "an", "the", "above", "said", "aforementioned", "this", etc., may mean "one and only one", or "one or more", "at least one", etc.

[0077] For example, when using articles such as “a”, “an”, and “the” in English in translation, the noun following the article can be understood as a singular expression or a plural expression.

[0078] In the embodiments of the present disclosure, “plurality” refers to two or more.

[0079] In some embodiments, the terms "at least one," "one or more," "a plurality of," "multiple," etc. may be used interchangeably.

[0080] In some embodiments, descriptions such as "at least one of A and B," "A and / or B," "A in one case, B in another case," or "in response to one case A, in response to another case B" may include the following technical solutions depending on the situation: in some embodiments, A (A is executed independently of B); in some embodiments, B (B is executed independently of A); in some embodiments, execution is selected from A and B (A and B are selectively executed); and in some embodiments, A and B (both A and B are executed). The above is also applicable when there are more branches such as A, B, and C.

[0081] In some embodiments, "A or B" and other descriptions may include the following technical solutions depending on the situation: in some embodiments, A (A is executed independently of B); in some embodiments, B (B is executed independently of A); in some embodiments, execution is selected from A and B (A and B are selectively executed). The above is also applicable when there are more branches such as A, B, C, etc.

[0082] The prefixes such as "first" and "second" in the embodiments of the present disclosure are only used to distinguish different description objects and do not constitute any restrictions on the position, order, priority, quantity or content of the description objects. For the statement of the description objects, please refer to the description in the context of the claims or embodiments, and no unnecessary restrictions should be constituted due to the use of prefixes.

[0083] For example, if the description object is "field," the ordinal number preceding "field" in "first field" and "second field" does not restrict the position or order of the "fields." "First" and "second" do not restrict whether the modified "fields" are in the same message, nor do they restrict the order of the "first field" and "second field." For another example, if the description object is "level," the ordinal number preceding "level" in "first level" and "second level" does not restrict the priority of the "levels." For another example, the number of description objects is not restricted by the ordinal number and can be one or more. For example, in the case of "first device," the number of "devices" can be one or more. Furthermore, the objects modified by different prefixes can be the same or different. For example, if the description object is "device," "first device" and "second device" can be the same or different devices, and their types can be the same or different. For another example, if the description object is "information," "first information" and "second information" can be the same or different information, and their content can be the same or different.

[0084] In some embodiments, “including A,” “comprising A,” “used to indicate A,” and “carrying A” can be interpreted as directly carrying A or indirectly indicating A.

[0085] In some embodiments, terms such as "in response to...", "in response to determining...", "in the case of...", "at the time of...", "when...", "if...", "if...", etc. can be used interchangeably.

[0086] In some embodiments, terms such as "greater than", "greater than or equal to", "not less than", "more than", "more than or equal to", "not less than", "higher than", "higher than or equal to", "not less than", and "above" can be replaced with each other, and terms such as "less than", "less than or equal to", "not greater than", "less than", "less than or equal to", "not more than", "lower than", "lower than or equal to", "not higher than", and "below" can be replaced with each other.

[0087] In some embodiments, devices and the like can be interpreted as physical or virtual, and their names are not limited to those in the embodiments.

[0088] The recorded names, "device", "equipment", "device", "circuit", "network element", "node", "function", "unit", "section", "system", "network", "chip", "chip system", "entity", "subject" and other terms can be used interchangeably.

[0089] In some embodiments, "network" can be interpreted as devices included in the network (eg, access network equipment, core network equipment, etc.).

[0090] In some embodiments, the terms "access network device (AN device)", "radio access network device (RAN device)", "base station (BS)", "radio base station" "fixed station", "node", "access point", "transmission point (TP)", "reception point (RP)", "transmission / reception point (TRP)", "panel", "antenna panel", "antenna array", "cell", "macro cell", "small cell", "femto cell", "pico cell", "sector", "cell group", "serving cell", "carrier", "component carrier", "bandwidth part (BWP)" and the like may be used interchangeably.

[0091] In some embodiments, the terms "terminal", "terminal device", "user equipment (UE)", "user terminal", "mobile station (MS)", "mobile terminal (MT)", subscriber station, mobile unit, subscriber unit, wireless unit, remote unit, mobile device, wireless device, wireless communication device, remote device, mobile subscriber station, access terminal, mobile terminal, wireless terminal, remote terminal, handset, user agent, mobile client, client, etc. can be used interchangeably.

[0092] In some embodiments, the access network device, the core network device, or the network device can be replaced by a terminal. For example, the various embodiments of the present disclosure can also be applied to a structure in which the communication between the access network device, the core network device, or the network device and the terminal is replaced by communication between multiple terminals (for example, device-to-device (D2D), vehicle-to-everything (V2X), etc.). In this case, it is also possible to set the structure in which the terminal has all or part of the functions of the access network device. In addition, terms such as "uplink" and "downlink" can also be replaced by terms corresponding to communication between terminals (for example, "side"). For example, uplink channels, downlink channels, etc. can be replaced by side channels, and uplinks, downlinks, etc. can be replaced by side links.

[0093] In some embodiments, the terminal may be replaced by an access network device, a core network device, or a network device. In this case, the access network device, the core network device, or the network device may have a structure that has all or part of the functions of the terminal.

[0094] In some embodiments, obtaining data, information, etc. may comply with the laws and regulations of the country where the data is obtained.

[0095] In some embodiments, data, information, etc. may be obtained with the user's consent.

[0096] In addition, each element, each row, or each column in the table of the embodiment of the present disclosure can be implemented as an independent embodiment, and the combination of any elements, any rows, and any columns can also be implemented as an independent embodiment.

[0097] FIG1 is a schematic diagram showing the architecture of a communication system according to an embodiment of the present disclosure.

[0098] As shown in FIG1 , the communication system 100 includes a first device 101 , a second device 102 and a third device 103 , wherein the second device 102 may be a terminal or an access network device, and the first device 101 and the third device 103 may be core network devices.

[0099] In some embodiments, the terminal includes, for example, a mobile phone, a wearable device, an Internet of Things device, a car with communication function, a smart car, a tablet computer, a computer with wireless transceiver function, a virtual reality (VR) terminal device, an augmented reality (AR) terminal device, a wireless terminal device in industrial control, a wireless terminal device in self-driving, a wireless terminal device in remote medical surgery, a wireless terminal device in a smart grid, a wireless terminal device in transportation safety, a wireless terminal device in a smart city, and at least one of a wireless terminal device in a smart home, but is not limited thereto.

[0100] In some embodiments, the access network device is, for example, a node or device that accesses a terminal to a wireless network. The access network device may include an evolved NodeB (eNB), a next generation evolved NodeB (ng-eNB), a next generation NodeB (gNB), a node B (NB), a home node B (HNB), a home evolved nodeB (HeNB), a wireless backhaul device, a radio network controller (RNC), a base station controller (BSC), a base transceiver station (BTS), a base band unit (BBU), a mobile switching center, a base station in a 6G communication system, an open base station (Open RAN), a cloud base station (Cloud RAN), a base station in other communication systems, and at least one of an access node in a Wi-Fi system, but is not limited thereto.

[0101] In some embodiments, a core network device may be a device including one or more network elements, or may be multiple devices or device groups, each including all or part of the one or more network elements. The network element may be virtual or physical. The core network may include, for example, at least one of an Evolved Packet Core (EPC), a 5G Core Network (5GCN), and a Next Generation Core (NGC).

[0102] In some embodiments, the technical solution of the present disclosure can be applied to the Open RAN architecture. In this case, the interfaces between or within the access network devices involved in the embodiments of the present disclosure can be transformed into internal interfaces of the Open RAN, and the processes and information interactions between these internal interfaces can be implemented through software or programs.

[0103] In some embodiments, the access network device can be composed of a centralized unit (CU) and a distributed unit (DU), where the CU can also be called a control unit. The CU-DU structure can be used to split the protocol layer of the access network device, with the functions of some protocol layers centrally controlled by the CU, and the functions of the remaining part or all of the protocol layers distributed in the DU, which is centrally controlled by the CU, but is not limited to this.

[0104] It can be understood that the communication system described in the embodiment of the present disclosure is for the purpose of more clearly illustrating the technical solution of the embodiment of the present disclosure, and does not constitute a limitation on the technical solution proposed in the embodiment of the present disclosure. Ordinary technicians in this field can know that with the evolution of the system architecture and the emergence of new business scenarios, the technical solution proposed in the embodiment of the present disclosure is also applicable to similar technical problems.

[0105] The following embodiments of the present disclosure may be applied to the communication system 100 shown in FIG1 , or a portion thereof, but are not limited thereto. The entities shown in FIG1 are illustrative only. The communication system may include all or part of the entities shown in FIG1 , or may include other entities outside of FIG1 . The number and form of the entities are arbitrary, and the entities may be physical or virtual. The connection relationships between the entities are illustrative only. The entities may be connected or disconnected, and the connection may be in any manner, including direct or indirect, wired or wireless.

[0106] The embodiments of the present disclosure can be applied to Long Term Evolution (LTE), LTE-Advanced (LTE-A), LTE-Beyond (LTE-B), SUPER 3G, IMT-Advanced, 4th generation mobile communication system (4G), 5th generation mobile communication system (5G), 5G new radio (NR), future radio access (FRA), new radio access technology (RAT), new radio (NR), new radio access (NX), future generation radio access (FX), Global System for Mobile communications (GSM (registered trademark)), CDMA2000, Ultra Mobile Broadband (UMB), IEEE 802.11 (Wi-Fi (registered trademark)), IEEE 802.16 (WiMAX (registered trademark)), IEEE 802.20, Ultra-WideBand (UWB), Bluetooth (registered trademark), Public Land Mobile Network (PLMN) networks, Device-to-Device (D2D) systems, Machine-to-Machine (M2M) systems, Internet of Things (IoT) systems, Vehicle-to-Everything (V2X), systems utilizing other communication methods, and next-generation systems based on and extending these methods. Furthermore, multiple systems may be combined (for example, a combination of LTE or LTE-A with 5G).

[0107] FIG2 is an interactive schematic diagram illustrating a method for disassociating a positioning reference unit according to an embodiment of the present disclosure.

[0108] As shown in FIG2 , the method for disassociating the positioning reference unit includes:

[0109] In step S201 , the second device 102 sends a first message to the first device 101 .

[0110] In some embodiments, before sending the first message to the first device, the second device may first decide to use the user plane and / or the control plane to perform the RPU association release operation.

[0111] In some embodiments, the second device 102 may send a first message to the first device 101 via a user, where the first message is used to instruct the first device to perform a positioning reference unit (PRU) de-association operation with the second device.

[0112] In some embodiments, the second device 102 may send the first message to the first device 101 using a user plane positioning protocol; wherein the user plane positioning protocol may include at least one of the following: location service user plane protocol LCS-UPP; secure user plane positioning SUPL protocol.

[0113] In some embodiments, the first message is also used to indicate at least one of the following: a first device identifier, the first device identifier is a device identifier corresponding to the first device; a second device identifier, the second device identifier is a device identifier corresponding to the second device; first indication information, the first indication information is used to indicate that the second device is a PRU; a PRU association release request.

[0114] In some embodiments, the second device identifier may include at least one of the following: a subscription hidden identifier SUCI; a subscription permanent identifier SUPI; a general public user identifier GPSI; or an application layer identifier.

[0115] In some embodiments, the PRU association release request includes second indication information, where the second indication information is used to indicate whether it is expected to receive a confirmation message corresponding to the PRU association release request.

[0116] Step S202 : The first device 101 sends a second message to the third device 103 .

[0117] In some embodiments, after receiving the first message from the second device, the first device may send a second message to the third device, where the second message is used to request the third device to perform a PRU verification operation.

[0118] In some embodiments, after receiving the first message from the second device, the first device may determine whether the first device is associated with the second device; if it is determined that the first device is associated with the second device, the second message is sent to the third device.

[0119] In some embodiments, the second message is an access and mobility management function AMF service message of the control plane.

[0120] In some embodiments, the second message is also used to indicate at least one of the following: a first device identifier, the first device identifier is a device identifier corresponding to the first device; a second device identifier, the second device identifier is a device identifier corresponding to the second device; first indication information, the first indication information is used to indicate that the second device is a PRU; a PRU association release request.

[0121] In step S203 , the third device 103 performs a verification operation.

[0122] In some embodiments, in response to receiving the second message from the first device, the third device may perform a PRU verification operation.

[0123] In some embodiments, the third device performing the PRU verification operation in response to receiving the second message may include verifying whether the device corresponding to the second device identifier, that is, the second device, is a PRU, and the obtained PRU verification result is used to determine whether the device corresponding to the second device identifier is a PRU. If it is determined that the device corresponding to the second device identifier is a PRU, the obtained PRU verification result may be a verification success; if it is determined that the device corresponding to the second device identifier is not a PRU, the obtained PRU verification result may be a verification failure.

[0124] Step S204 : The third device 103 sends a third message to the first device 101 .

[0125] In some embodiments, after performing a PRU verification operation and obtaining a PRU verification result, the third device may send a third message to the first device, where the third message is used to indicate the PRU verification result, wherein the PRU verification result is obtained by the third device after performing the PRU verification operation.

[0126] In some embodiments, the third message is an AMF service message of the control plane.

[0127] In some embodiments, the third message is also used to indicate at least one of the following: a first device identifier, the third device identifier is a device identifier corresponding to the first device; a second device identifier, the second device identifier is a device identifier corresponding to the second device; first indication information, the first indication information is used to indicate that the second device supports the PRU function; and the PRU verification result.

[0128] In some embodiments, the PRU verification result is verification failure, and the third message is further used to indicate the reason for the verification failure.

[0129] In step S205 , the first device 101 performs a disassociation operation.

[0130] In some embodiments, in response to receiving the third message from the third device, the first device may perform a PRU association release operation and determine a PRU association release result with the second device.

[0131] In some embodiments, if the PRU verification result indicated by the third message is a successful verification, the first device may further determine whether to perform a PRU association release operation and obtain a PRU association release result. If the PRU verification result indicated by the third message is a failed verification, the first device may determine not to perform the PRU association release operation.

[0132] In some embodiments, the first device determines whether to perform a PRU association release operation, which may include determining whether the first device is associated with the second device; if the first device is associated with the second device, performing the PRU association release operation; if not, not performing the PRU association release operation.

[0133] Step S206 : The first device 101 sends a fourth message to the second device 102 .

[0134] In some embodiments, after determining the result of the disassociation between the first device and the second device, the first device 101 may send a fourth message to the second device, where the fourth message is used to indicate the result of the disassociation between the first device and the second device.

[0135] In some embodiments, after determining the result of the disassociation between the first device and the second device, the first device 101 can first determine whether a confirmation message corresponding to the PRU disassociation request is expected to be received from the second device; if it is determined that a confirmation message corresponding to the PRU disassociation request is expected to be received, for example, the first message includes second indication information for indicating that the confirmation message corresponding to the PRU disassociation request is expected to be received, then a fourth message is sent to the second device.

[0136] In some embodiments, the fourth message is a message using a user plane positioning protocol; wherein the user plane positioning protocol may include at least one of the following: Location Service User Plane Protocol LCS-UPP; Secure User Plane Positioning SUPL protocol.

[0137] In some embodiments, the fourth message is also used to indicate at least one of the following: a first device identifier, the first device identifier is a device identifier corresponding to the first device; a second device identifier, the second device identifier is a device identifier corresponding to the second device; first indication information, the first indication information is used to indicate that the second device supports the PRU function; a PRU association release response, the PRU association release response is used to indicate the result of the association release between the first device and the second device.

[0138] In some embodiments, the second device is a location management function LMF.

[0139] In some embodiments, the third device is an AMF.

[0140] The communication method involved in the embodiments of the present disclosure may include at least one of steps S201 to 206. For example, any one of steps S201-S206 may be implemented as an independent embodiment, or any two or more of steps S201-S206 may be combined and implemented as an independent embodiment, but the present invention is not limited thereto.

[0141] In some embodiments, steps S201 - S206 may be executed in a swapped order or simultaneously.

[0142] In some embodiments, step S201 is optional, and one or more of these steps may be omitted or replaced in different embodiments.

[0143] In some embodiments, step S202 is optional, and one or more of these steps may be omitted or replaced in different embodiments.

[0144] In some embodiments, step S203 is optional, and one or more of these steps may be omitted or replaced in different embodiments.

[0145] In some embodiments, step S204 is optional, and one or more of these steps may be omitted or replaced in different embodiments.

[0146] In some embodiments, step S205 is optional, and one or more of these steps may be omitted or replaced in different embodiments.

[0147] In some embodiments, step S206 is optional, and one or more of these steps may be omitted or replaced in different embodiments.

[0148] In some embodiments, reference may be made to other optional embodiments described before or after the description corresponding to FIG. 2 .

[0149] In some embodiments, devices in the network can be located based on a Positioning Reference Unit (PRU). The second device serving as the PRU needs to be associated with a corresponding first device having a location management function, where the first device may be a Location Management Function (LMF) in a core network device. The LMF corresponding to the second device may provide services for the second device and may also be referred to as the service LMF of the second device. For simplicity, the following embodiments are all illustrated by taking the service LMF of the second device as the first device.

[0150] In some embodiments, the second device that can serve as the PRU may be a terminal, such as a user equipment (UE), or a network device, such as an access network device.

[0151] In some embodiments, the second device may perform a PRU association operation with the serving LMF through a control plane and / or a user plane, where the PRU association operation may include a PRU association release operation.

[0152] In some embodiments, the second device may perform a PRU association removal operation with the serving LMF via the control plane. The PRU association removal operation on the control plane may include: the second device sending a PRU association removal request to the serving LMF via the control plane, so that the serving LMF performs the PRU association removal operation with the second device.

[0153] The second device sending a PRU association release request by controlling the service-oriented LMF may include: the second device sending a PRU association release request by controlling the corresponding third device, the third device may be a network device with access and mobility management functions, for example, it may be an access and mobility management function (AMF) in a core network device, the AMF corresponding to the second device may provide services for the second device, and may also be referred to as a service AMF. For simplicity, in the following embodiments, the service AMF of the second device is used as the third device for illustration;

[0154] In response to receiving a PRU association release request from the second device, the service AMF may perform a PRU verification operation on the second device that sends the PRU association request. The PRU verification operation may include verifying whether the second device is a PRU and / or verifying whether the second device is a stationary PRU (stationary PRU); if the obtained PRU verification result is that the second device is determined to be a PRU and / or a stationary PRU, the service AMF may forward the PRU association release request to the service LMF so that the service LMF performs the PRU association release operation; otherwise, the PRU association release request is not forwarded to the service LMF.

[0155] In some embodiments, the second device may also perform a PRU association release operation with the service LMF through the user plane. The PRU association release operation on the user plane may include: the second device sends a PRU association release request through the user-facing service LMF, so that the service LMF performs the PRU association release operation on the second device. When the second device sends the PRU association release request through the user-facing service LMF, since there is no need to forward the PRU association release request through the service AMF, the PRU verification operation cannot be performed on the second device. If the second device is not a PRU, it will cause the LMF to perform an association release operation on the non-PRU device, thereby causing a waste of communication resources.

[0156] In a first aspect, embodiments of the present disclosure provide a method for disassociating a positioning reference unit. Figure 3 is a schematic flow chart illustrating a method for disassociating a positioning reference unit according to an embodiment of the present disclosure. The method for disassociating a positioning reference unit illustrated in this embodiment can be performed by a first device. The first device can be a network device with location management functionality, such as a LMF in a core network device.

[0157] As shown in FIG3A , the method for disassociating a positioning reference unit may include the following steps:

[0158] In step S301, a first message is received from a second device via a user plane, where the first message is used to instruct the first device to perform a positioning reference unit (PRU) de-association operation with the second device.

[0159] In some embodiments, the second device may be a terminal or a network device that supports the function of the PRU. For the sake of simplicity, the following embodiments are all described by taking a terminal as an example.

[0160] In some embodiments, the functions of the PRU may include at least one of the following: supporting service level PRU association establishment, PRU association update and PRU association release with the serving LMF; supporting PRU association with multiple LMFs, for example, the second device is located in a service area where multiple LMFs overlap.

[0161] The PRU information involved in the PRU association establishment and PRU association update may include at least one of the following: PRU positioning capability; PRU location information; and PRU switch (ON / OFF) status. The PRU switch status is used to indicate the availability of the PRU function of the second device on the serving LMF.

[0162] In some embodiments, a terminal accessing a mobile network, such as a 5G network, via a New Radio (NR) interface shall not be used as a PRU.

[0163] In some embodiments, the data transmission mode for performing the PRU association release operation may be determined by the second device, and the second device may decide to use the user plane and / or the control plane to perform the PRU association release operation. Furthermore, the second device may make a decision based on the acquired control plane positioning capability, the protocol data unit (PDU) session status and the user connection status, pre-configured information and policy parameters, etc. The control plane positioning capability may be defined in the received 5G system mobility management capability information element (5G System Mobility Management capability Information Element, 5GMM capability IE) and the 5G system network feature support information element (5G System network feature support Information Element, 5GS network feature support IE).

[0164] In some embodiments, the second device may decide to use the user plane to perform the PRU disassociation operation.

[0165] In some embodiments, the second device may decide to use the control plane to perform the PRU disassociation operation.

[0166] In some embodiments, the second device may decide to use the user plane and the control plane to perform the PRU association release operation, and the user plane and the control plane respectively transmit all or part of the PRU association information that needs to be transmitted during the PRU association release operation.

[0167] In some embodiments, a first device may receive a first message from a second device via a user plane, and the first message may be used to instruct the first device to perform a PRU association release operation with the second device, and the first message may carry all or part of the PRU association information transmitted by the second device to the first device when performing the PRU association release operation.

[0168] In step S302, a second message is sent to a third device, where the second message is used to request the third device to perform a PRU verification operation.

[0169] In some embodiments, in response to receiving a first message from a second device via a user plane, the first message being used to instruct the first device to perform a PRU disassociation operation with the second device, the first device may send a second message to a third device, the second message being used to request the third device to perform a PRU verification operation. If the PRU verification operation results in a PRU verification result of successful verification, the first device may further determine whether to perform the PRU disassociation operation with the second device; if the PRU verification result is a verification failure, the first device may not perform the PRU disassociation operation.

[0170] For example, take the first device as LMF1, the second device as terminal T1, and the third device as AMF1 as an example. When terminal T1 determines to use the user plane to perform the PRU association release operation, terminal T1 can send a first message M1 to LMF1 through the user plane. The first message M1 is used to indicate that the PRU association release operation is to be performed with terminal T1. In response to receiving the first message M1, LMF1 can send a second message M2 to AMF1 through the control plane. The second message M2 is used to indicate that a PRU verification operation is to be performed; if the PRU verification result obtained by the PRU verification operation is a successful verification, LMF1 further determines whether to perform the PRU association release operation with terminal T1; if the PRU verification result is a failed verification, LMF1 will not perform the PRU association release operation with terminal T1.

[0171] It should be noted that the embodiment shown in FIG. 3A can be implemented independently or in combination with at least one other embodiment in the present disclosure. The specific selection can be made as needed and the present disclosure does not limit it.

[0172] In the above embodiment, when the serving LMF receives a PRU disassociation request from the second device through the user plane, it may first send a PRU verification request to the serving AMF to perform a PRU verification operation on the second device. Accordingly, whether to perform the PRU disassociation operation on the second device can be determined based on the PRU verification result of the second device, thereby avoiding the LMF from performing the disassociation operation on non-PRU devices, saving communication resources and power consumption.

[0173] In some embodiments, a first device may receive a first message from a second device using a user plane positioning protocol, where the first message is used to instruct a PRU disassociation operation to be performed with the second device. Furthermore, the user plane positioning protocol may include at least one of the following: a Location Service User Plane Protocol (LCS-UPP); or a Secure User Plane Location (SUPL) protocol. For example, the first device may receive the first message from the second device using LCS-UPP; or the first device may receive the first message from the second device using the SUPL protocol.

[0174] In some embodiments, the first message received by the first device from the second device through the user plane may be further used to indicate at least one of the following: a first device identifier; a second device identifier; first indication information; or a PRU association release request.

[0175] Among them, the first device identifier is the device identifier corresponding to the first device or the device identifier corresponding to the service LMF of the second device. The first device identifier can be represented by a routing identifier (Routing ID) or a correlation identifier (Correlation ID). For example, the first device identifier can be represented by a Correlation ID in a message transmitted between an AMF and an LMF, and can be represented by a Routing ID in a message transmitted between the second device and the LMF.

[0176] The second device identifier is a device identifier corresponding to the second device. For example, if the second device is a terminal, it can be represented by a terminal identifier (UE ID). Furthermore, the second device identifier can specifically use at least one of the following identifiers corresponding to the second device: a subscription concealed identifier (SUCI); a subscription permanent identifier (SUPI); a generic public subscription identifier (GPSI); or an application layer identifier (Application Layer ID).

[0177] The first indication information is used to indicate that the second device may be a PRU. For example, the first indication information may be represented by a PRU indication (PRU Indication). Furthermore, the first indication information may be explicitly indicated by a specific parameter or a specific value of an existing parameter, or may be implicitly indicated by a name of a request included in the first message. For example, if the first message includes a PRU association release request, it is equivalent to indicating that the second device may be a PRU.

[0178] The PRU association release request may be used to request the first device to perform a PRU association release operation. Further, the PRU association release request includes second indication information (AckIndication), which is used to indicate whether to expect to receive an acknowledgment message corresponding to the PRU association release request.

[0179] The above-mentioned information carried by the first message can be encapsulated in various ways in the first message. In some embodiments, a new PRU association release request message can be used as the first message. The new PRU association release request message can carry the first device identifier, the second device identifier, the first indication information and the existing PRU association request. The PRU association request can also include the second indication information AckIndication.

[0180] In some embodiments, the first device identifier, the second device identifier, the first indication information, etc. can be used as parameters in the PRU association release request. For example, an existing PRU association release request message can be used, and the PRU association release request message can carry a PRU association release request. The PRU association release request may include: the first device identifier, the second device identifier, the first indication information, and the second indication information AckIndication.

[0181] In some embodiments, the first device identifier, the second device identifier, and the first indication information may be transmitted together with the PRU association release request.

[0182] In some embodiments, in response to receiving a first message from a second device through a user plane for instructing the first device to perform a positioning reference unit (PRU) de-association operation with the second device, the first device may send a second message to a third device through a control plane, where the second message is used to request the third device to perform a PRU verification operation. Furthermore, the second message sent by the first device to the third device through the control plane may be an AMF service message of the control plane, where the AMF service message is used to trigger the AMF to perform a PRU verification operation. For example, the second message may be named a Namf_Location_PRUVerify message.

[0183] In some embodiments, the second message sent by the first device to the third device through the control surface may include at least one of the following: a first device identification Correlation ID; a second device identification UE ID; first indication information PRU Indication; or a PRU association release request.

[0184] In the above embodiment, after the first device receives the first message sent by the second device through the user plane to instruct the PRU association release operation, it can send the second message for instructing the execution of the PRU verification operation to the third device through the control plane, so that the PRU verification operation can be performed on the second device before the PRU association operation is performed, so as to avoid the first device performing the association operation on the non-PRU device, thereby saving communication resources and power consumption.

[0185] In some embodiments, the first device can receive a first message from the second device through the user plane; then send a second message to the third device through the control plane, so that the third device performs a PRU verification operation in response to receiving the second message and obtains a PRU verification result; then the first device can receive a third message from the third device through the control plane, and the third message is used to indicate the PRU verification result obtained after the third device performs the PRU verification operation.

[0186] In some embodiments, the third message may be an AMF service message of the control plane, which is used to inform the first device of the PRU verification result obtained by the PRU verification operation. For example, the third message may be named Namf_Location_PRUVerify message.

[0187] In some embodiments, the third device performing the PRU verification operation in response to receiving the second message may include verifying whether the device corresponding to the second device identifier, that is, the second device, is a PRU, and the obtained PRU verification result is used to determine whether the device corresponding to the second device identifier is a PRU. If it is determined that the device corresponding to the second device identifier is a PRU, the obtained PRU verification result may be a verification success; if it is determined that the device corresponding to the second device identifier is not a PRU, the obtained PRU verification result may be a verification failure.

[0188] For example, AMF1 receives a second message M2 from LMF1, and the second message M2 is used to instruct a PRU verification operation, and the second message M2 includes a second device identifier ID2 corresponding to the terminal T1. AMF1 can verify whether the device corresponding to ID2 (terminal T1) is a PRU based on the obtained PRU subscription information or local policy to obtain a PRU verification result. The subscription information of the PRU can be obtained from a unified data management entity (UDM); the local policy can maintain a device identifier list, which includes the device identifiers corresponding to each PRU. If it is determined that the terminal T1 is a PRU, the obtained PRU verification result is a successful verification; if it is determined that the terminal T1 is not a PRU, the obtained PRU verification result is a failed verification.

[0189] Furthermore, AMF1 can also determine whether the device corresponding to ID2 (terminal T1) is a static PRU based on the obtained PRU subscription information or local policy. If it is determined that terminal T1 is a static PRU, the obtained PRU verification result is verification success; if it is determined that terminal T1 is not a static PRU, the obtained PRU verification result is verification failure. For the sake of simplicity, the following embodiments are all illustrated by verifying whether the device corresponding to the second device identifier is a PRU.

[0190] In some embodiments, the third message may be further used to indicate at least one of the following: a first device identifier Correlation ID; a second device identifier UE ID; first indication information PRU Indication; or the PRU verification result.

[0191] In some embodiments, if the PRU verification result obtained after the third device performs the RPU verification operation is a verification failure, the failure reason of the verification failure can also be determined; accordingly, the third message received by the first device from the third device through the control plane can also include the failure reason of the verification failure.

[0192] Furthermore, the first device may receive a third message from a third device via a control plane, and the third message may include at least one of the following: a first device identifier, Correlation ID; a second device identifier, UE ID; a first indication information, PRU Indication; a PRU verification result; or a failure reason for verification failure.

[0193] In the above embodiment, the first device can send a second message to the third device, causing the third device to perform a PRU verification operation and send the obtained PRU verification result back to the first device. The first device can then determine whether to perform a PRU disassociation operation on the second device based on the PRU verification result. This can prevent the first device from erroneously performing a PRU disassociation operation on a non-PRU device, saving communication resources and power consumption.

[0194] In some embodiments, a first device may determine whether the first device is associated with a second device.

[0195] In some embodiments, after receiving a first message from a second device via a user plane that instructs the first device to perform a PRU disassociation operation with the second device, the first device may first determine whether the first device is associated with the second device, and then send a second message to the third device to request the third device to perform a PRU verification operation. For example, if the first device determines that the first device is associated with the second device, the second message is sent to the third device; if the first device determines that the first device is not associated with the second device, it indicates that there is no need to perform a PRU disassociation operation, and there is no need to send the second message to the third device.

[0196] In some embodiments, after receiving a first message from a second device via a user plane that instructs the first device to perform a PRU disassociation operation with the second device, the first device may first send a second message to a third device to request the third device to perform a PRU verification operation; the first device may receive a third message from the third device that indicates a PRU verification result; and the first device may then further determine whether the first device is associated with the second device, and determine whether to perform a PRU disassociation operation with the second device based on the obtained association result. For example, if the PRU verification result indicated by the third message received by the first device from the third device is a successful verification, the first device may further determine whether the first device is associated with the second device, and if it is determined that the first device and the second device are already associated, perform a PRU disassociation operation with the second device; if the PRU verification result indicated by the third message received by the first device from the third device is a successful verification, but it is determined that the first device and the second device are not associated, the first device may not perform the PRU disassociation operation; if the PRU verification result indicated by the third message received by the first device from the third device is a failed verification, the first device does not need to determine whether the first device and the second device are associated, and does not need to perform the PRU disassociation operation.

[0197] In the above embodiment, before performing the PRU disassociation operation, the first device can first determine whether the first device is associated with the second device. If the first device and the second device are not associated, the PRU disassociation operation does not need to be performed. Accordingly, the first device can avoid performing the PRU disassociation operation with the unassociated second device, saving communication resources and power consumption.

[0198] In some embodiments, after receiving a third message from a third device and obtaining the PRU verification result carried in the third message, the first device can determine whether to perform the PRU association disassociation operation between the first device and the second device, and obtain the PRU association disassociation result with the second device, and then send a fourth message to the second device, where the fourth message is used to indicate the PRU association disassociation result between the first device and the second device.

[0199] In some embodiments, a first device may receive a first message from a second device via a user plane for instructing the first device to perform a positioning reference unit PRU de-association operation with the second device; then, the first device may send a second message to a third device via a control plane to instruct the third device to perform a PRU verification operation; the first device may receive a third message from the third device via a control plane to obtain a PRU verification result; in response to receiving the third message, the first device may determine whether the first device is associated with the second device, and determine whether to perform a PRU de-association operation between the first device and the second device to obtain a PRU de-association result with the second device, and then send a fourth message to the second device, where the fourth message is used to indicate a PRU de-association result between the first device and the second device.

[0200] In some embodiments, a first device may receive a first message from a second device via a user plane for instructing the first device to perform a positioning reference unit PRU disassociation operation with the second device; then, when determining that the first device is associated with the second device, the first device sends a second message to a third device via a control plane to instruct the third device to perform a PRU verification operation; the first device may receive a third message from the third device via a control plane to obtain a PRU verification result; in response to receiving the third message, the first device may determine whether to perform a PRU disassociation operation with the first device and the second device to obtain a PRU disassociation result with the second device, and then send a fourth message to the second device, where the fourth message is used to indicate a PRU disassociation result with the first device and the second device.

[0201] In some embodiments, the first device may determine whether to send the fourth message to the second device based on whether second indication information indicating an expectation to receive a confirmation message corresponding to the PRU association release request is received from the second device.

[0202] In some embodiments, the first message received by the first device from the second device carries second indication information, and the second indication information is used to indicate whether it is expected to receive a confirmation message corresponding to the PRU association release request; if the received second indication information is used to indicate that it is expected to receive a confirmation message corresponding to the PRU association release request, then the first device may send a fourth message to the second device after determining the result of the association release between the first device and the second device in response to receiving the third message; if the second indication information is not received, or the received second indication information is used to indicate that it is not expected to receive a confirmation message corresponding to the PRU association release request, then the first device does not send the fourth message to the second device after determining the result of the association release with the second device in response to receiving the third message.

[0203] In some embodiments, the first device may send the fourth message to the second device through the user.

[0204] In some embodiments, the first device may send the fourth message to the second device using a user plane positioning protocol. Furthermore, the user plane positioning protocol may include at least one of the following: a Location Services User Plane Protocol (LCS-UPP); or a Secure User Plane Positioning (SUPL) protocol. For example, the first device may send the fourth message to the second device using LCS-UPP; or the first device may send the fourth message to the second device using the SUPL protocol.

[0205] In some embodiments, the fourth message sent by the first device to the second device through the user can also be used to indicate at least one of the following: the first device identifier Routing ID; the second device identifier UE ID; the first indication information PRU Indication; or the PRU association release response.

[0206] The PRU association release response is used to indicate the result of the PRU association release with the second device. Further, the PRU association release response may include at least one of the following: the PRU association release result; or a failure reason for the PRU association release failure.

[0207] The above-mentioned information carried by the fourth message can be encapsulated in various ways in the fourth message. In some embodiments, a new PRU association release response message can be used as the fourth message. The new PRU association release response message can carry the first device identifier, the second device identifier, the first indication information and the PRU association release response. The PRU association release response may include the PRU association release result and the failure reason of the PRU association release failure.

[0208] In some embodiments, the first device identifier, the second device identifier, the first indication information, etc. can be used as parameters in the PRU association release response. For example, an existing PRU association release response message can be used, and the PRU association release response message can carry a PRU association release response. The PRU association release response may include: the first device identifier, the second device identifier, the first indication information, the PRU association release result, and the failure reason of the PRU association release failure.

[0209] In some embodiments, the first device identifier, the second device identifier, and the first indication information may be transmitted together with a PRU association release response, and the PRU association release response may include a PRU association release result and a failure reason for the PRU association release failure.

[0210] For example, when the terminal T1 determines to use the user plane to perform the PRU association operation, the terminal T1 may send a first message M1 to the LMF1 through the user plane, where the first message M1 is used to indicate that a PRU association release operation is to be performed with the terminal T1, and the first message M1 includes a second indication message, where the second indication message is used to indicate that a confirmation message corresponding to the PRU association release request is expected to be received; in response to receiving the first message M1, the LMF1 may send a second message M2 to the AMF1 through the control plane, where the second message M2 is used to indicate that a PRU verification operation is to be performed; in response to receiving the second message M2, the AMF1 performs a PRU verification operation on the terminal T1 to determine whether the terminal T1 is a PRU; and after obtaining the second message M2, the AMF1 performs a PRU verification operation on the terminal T1 to determine whether the terminal T1 is a PRU. After receiving the PRU verification result, the third message M3 is sent to LMF1 through the control surface, and the third message M3 is used to indicate the PRU verification result; LMF1 determines whether to perform the PRU association release operation with the terminal T1 according to the PRU verification result indicated by the received third message; if the PRU verification result is a successful verification, it is determined whether the first device is associated with the second device; if the first device is associated with the second device, it is further determined whether to perform the PRU association release operation with the terminal T1, and a fourth message is sent to the terminal T1 through the user surface, and the fourth message can be used to indicate that the PRU association is successful; if the PRU verification result indicated by the third message M3 received by LMF1 is a failed verification, LMF1 may not perform the PRU association release operation with the terminal T1, and send a fourth message to the terminal T1, and the fourth message can be used to indicate that the PRU association release failed, and the fourth message can also be used to indicate the failure reason of the association release failure.

[0211] In the above embodiment, the first device can determine whether to perform the PRU association disassociation operation with the second device based on the PRU verification result received from the third device, thereby avoiding the first device from performing association operations with non-PRU devices, saving communication resources and power consumption.

[0212] FIG3B is a schematic flow chart of a method for disassociating a positioning reference unit according to an embodiment of the present disclosure. As shown in FIG3B , the method for disassociating a positioning reference unit may include the following steps:

[0213] S310 , determining the Connected Management (CM) state of the terminal T1 . If the terminal T1 is in the CM_IDLE state, it is necessary to trigger a service request to convert the terminal T1 from the CM_IDLE state to the CM_CONNECTED state.

[0214] S311. Terminal T1 may decide to use the user plane and / or control plane to perform the PRU association disassociation operation. If the terminal decides to use the user plane to transmit all or part of the PRU association information, steps S312a-S317a are executed; if the terminal decides to use the control plane to transmit all or part of the PRU association information, steps S312b-S317b are executed. Furthermore, when deciding to use the user plane to transmit all or part of the PRU association information, if there is no available user plane connection, terminal T1 may first trigger the user plane connection establishment process.

[0215] S312a. Terminal T1 sends a first message via the user-facing LMF, where the first message is used to instruct the execution of a PRU deassociation operation for terminal T1. The first message may include: a Routing ID, a UE ID corresponding to terminal T1, a PRU Indication, and a PRU deassociation request. The PRU deassociation request may include: second indication information AckIndication, where the second indication information is used to indicate whether an acknowledgment message corresponding to the PRU deassociation request is expected to be received.

[0216] S313a. In response to receiving the first message, the LMF may send a second message to the AMF, where the second message is used to request the third device to perform a PRU verification operation. The second message may include: a Correlation ID, a UE ID, a PRU Indication, and a PRU disassociation request; the Correlation ID is the same as the Routing ID in the first message.

[0217] S314a. In response to receiving the second message, the AMF performs a PRU verification operation to determine whether the device corresponding to the UE ID, that is, the terminal T1, is a PRU; if the terminal T1 is a PRU, the obtained PRU verification result is a successful verification; if the terminal T1 is not a PRU, the obtained PRU verification result is a failed verification.

[0218] S315a. After performing the PRU verification operation and obtaining the PRU verification result, the AMF may send a third message to the LMF, where the third message indicates the PRU verification result. The third message may include the Correlation ID, UE ID, PRU Indication, and the PRU verification result. If the PRU verification result is a failure, the third message may also include the failure reason.

[0219] S316a, LMF can perform PRU check on terminal T1 to determine whether the LMF is associated with terminal T1; if it is determined that the LMF is associated with terminal T1, execute S317a; if it is determined that the LMF is not associated with terminal T1, directly execute S318.

[0220] The execution order of step S316a and steps S312a-S315 can be interchanged.

[0221] S317a. The LMF determines the PRU disassociation result and sends a fourth message to the terminal T1 through the user. The fourth message is used to indicate the result of the disassociation with the second device. The fourth message may include: Routing ID, UE ID, PRU Indication, and PRU Disassociation Response. The PRU Disassociation Response is used to indicate the result of the PRU disassociation with the terminal T1. If the PRU disassociation result indicated by the RU Disassociation Response is a disassociation failure, the PRU Disassociation Response may also include the failure reason for the PRU disassociation failure.

[0222] Among them, the LMF can first determine whether it has received second indication information from the terminal T1, indicating that it expects to receive a confirmation message corresponding to the PRU association release request; if the received second indication information is used to indicate that it expects to receive a confirmation message corresponding to the PRU association release request, then the LMF can send a fourth message to the terminal T1 after determining the result of the association release with the second device in response to receiving the third message; if the second indication information is not received, or the received second indication information is used to indicate that it does not expect to receive a confirmation message corresponding to the PRU association release request, then the LMF may not send the fourth message to the terminal T1 after determining the result of the association release with the second device in response to receiving the third message.

[0223] S312b. Terminal T1 sends an uplink non-access stratum transport (UL NAS TRANSPORT) message to the AMF through the control plane to send a PRU association release request as a supplementary service. The PRU association release request may include second indication information AckIndication.

[0224] S313b. AMF performs a PRU verification operation to determine whether terminal T1 is a PRU and obtains a PRU verification result.

[0225] S314b. The AMF selects a serving LMF based on a preset protocol or the Routing ID received from the terminal T1, and sends a PRU disassociation request to the serving LMF using the Namf_Communication_N1MessageNotify service operation. The Namf_Communication_N1MessageNotify service message may include third indication information, which is used to indicate the PRU verification result, as well as the SUPI, Tracking Area Identity (TAI), and cell identity corresponding to the terminal T1.

[0226] S315b, LMF can perform PRU check on terminal T1 to determine whether the LMF is associated with terminal T1; if it is determined that the LMF is associated with terminal T1, execute S316b; if it is determined that the LMF is not associated with terminal T1, execute S318 directly.

[0227] S316b. If the PRU verification result is successful, the LMF further determines whether to perform a disassociation operation with terminal T1 to obtain a disassociation result. If the PRU disassociation result is successful, the LMF uses the Namf_Communication_N1N2MessageTransfer service operation to return a PRU association response as a supplementary service message and a Correlation ID to the AMF. The Correlation ID is allocated by the LMF and can be used to identify the LMF and terminal T1.

[0228] S317b. AMF sends a downlink non-access stratum transport (DL NAS TRANSPORT) message to terminal T1 through the control plane to send a PRU association release response and Routing ID.

[0229] S318. If the LMF has sent a fourth indication message to the Network Repository Function (NRF) during the previous PRU association establishment operation or association update operation, the fourth indication message is used to indicate the existence of the PRU associated with the TAI corresponding to the terminal T1; if after the current PRU association release operation, there is no longer a PRU associated with the TAI among the PRUs associated with the LMF, then the LMF can call the Nnrf_NFManagement_NFUpdate request service operation message to instruct the NRF to delete the fourth indication message, so that the NRF can remove the existence of the PRU related to the TAI.

[0230] S319. The NRF returns a confirmation response to the LMF.

[0231] In a second aspect, embodiments of the present disclosure provide a method for disassociating a positioning reference unit. Figure 4 is a schematic flow chart illustrating a method for disassociating a positioning reference unit according to an embodiment of the present disclosure. The method for disassociating a positioning reference unit illustrated in this embodiment can be performed by a second device. The second device can be a terminal or network device that supports PRU functionality.

[0232] As shown in FIG4 , the method for disassociating a positioning reference unit may include the following steps:

[0233] In step S401, it is determined to perform a PRU association release operation through a user plane.

[0234] In some embodiments, the data transmission mode for performing the PRU association release operation may be determined by the second device, and the second device may decide to use the user plane and / or the control plane to perform the PRU association release operation. Furthermore, the second device may make a decision based on the acquired control plane positioning capability, the protocol data unit (PDU) session status and the user connection status, pre-configured information and policy parameters, etc. The control plane positioning capability may be defined in the received 5G system mobility management capability information element (5G System Mobility Management capability Information Element, 5GMM capability IE) and the 5G system network feature support information element (5G System network feature support Information Element, 5GS network feature support IE).

[0235] In some embodiments, the second device may decide to use the user plane to perform the PRU disassociation operation.

[0236] In some embodiments, the second device may decide to use the control plane to perform the PRU disassociation operation.

[0237] In some embodiments, the second device may decide to use the user plane and the control plane to perform the PRU association release operation, and the user plane and the control plane respectively transmit all or part of the PRU association information that needs to be transmitted during the PRU association release operation.

[0238] In step S402, a first message is sent to the first device via the user, where the first message is used to instruct the positioning reference unit PRU association removal operation to be performed with the second device, so that the second device sends a second message to the third device, where the second message is used to request the third device to perform a PRU verification operation.

[0239] In some embodiments, the second device may send a first message to the first device through a user, and the first message may be used to instruct the first device to perform a PRU association release operation with the second device. The first message may carry all or part of the PRU association information transmitted by the second device to the first device when performing the PRU association release operation.

[0240] In some embodiments, the first device may be a network device having a location management function, for example, an LMF in a core network device.

[0241] In some embodiments, in response to receiving a first message from a second device via a user plane, the first message being used to instruct the first device to perform a PRU disassociation operation with the second device, the first device may send a second message to a third device, the second message being used to request the third device to perform a PRU verification operation. If the PRU verification operation results in a PRU verification result of successful verification, the first device may further determine whether to perform the PRU disassociation operation with the second device; if the PRU verification result is a verification failure, the first device may not perform the PRU disassociation operation.

[0242] For example, take the first device as LMF1, the second device as terminal T1, and the third device as AMF1 as an example. When terminal T1 determines to use the user plane to perform the PRU association release operation, terminal T1 can send a first message M1 to LMF1 through the user plane. The first message M1 is used to indicate that the PRU association release operation is to be performed with terminal T1. In response to receiving the first message M1, LMF1 can send a second message M2 to AMF1 through the control plane. The second message M2 is used to indicate that a PRU verification operation is to be performed; if the PRU verification result obtained by the PRU verification operation is a successful verification, LMF1 further determines whether to perform the PRU association release operation with terminal T1; if the PRU verification result is a failed verification, LMF1 will not perform the PRU association release operation with terminal T1.

[0243] It should be noted that the embodiment shown in FIG. 4 can be implemented independently or in combination with at least one other embodiment in the present disclosure. The specific selection can be made as needed and the present disclosure does not limit it.

[0244] In the above embodiment, when the serving LMF receives a PRU disassociation request from the second device through the user plane, it may first send a PRU verification request to the serving AMF to perform a PRU verification operation on the second device. Accordingly, whether to perform the PRU disassociation operation on the second device can be determined based on the PRU verification result of the second device, thereby avoiding the LMF from performing the disassociation operation on non-PRU devices, saving communication resources and power consumption.

[0245] In some embodiments, a first device may receive a first message from a second device using a user plane positioning protocol, where the first message is used to instruct a PRU disassociation operation to be performed with the second device. Furthermore, the user plane positioning protocol may include at least one of the following: a Location Service User Plane Protocol (LCS-UPP); or a Secure User Plane Location (SUPL) protocol. For example, the first device may receive the first message from the second device using LCS-UPP; or the first device may receive the first message from the second device using the SUPL protocol.

[0246] In some embodiments, the first message received by the first device from the second device through the user plane may be further used to indicate at least one of the following: a first device identifier; a second device identifier; first indication information; or a PRU association release request.

[0247] The first device identifier is a device identifier corresponding to the first device or a device identifier corresponding to the service LMF of the second device, and can be represented by a routing identifier (Routing ID) or a correlation identifier (Correlation ID).

[0248] The second device identifier is a device identifier corresponding to the second device. For example, if the second device is a terminal, it can be represented by a terminal identifier (UE ID). Furthermore, the second device identifier can specifically use at least one of the following identifiers corresponding to the second device: a subscription concealed identifier (SUCI); a subscription permanent identifier (SUPI); a generic public subscription identifier (GPSI); or an application layer identifier (Application Layer ID).

[0249] The first indication information is used to indicate that the second device may be a PRU. For example, the first indication information may be represented by a PRU indication (PRU Indication).

[0250] The PRU association release request may be used to request the first device to perform a PRU association release operation. Further, the PRU association release request includes second indication information (AckIndication), which is used to indicate whether to expect to receive an acknowledgment message corresponding to the PRU association release request.

[0251] The above-mentioned information carried by the first message can be encapsulated in various ways in the first message. In some embodiments, a new PRU association release request message can be used as the first message. The new PRU association release request message can carry the first device identifier, the second device identifier, the first indication information and the existing PRU association request. The PRU association request can also include the second indication information AckIndication.

[0252] In some embodiments, the first device identifier, the second device identifier, the first indication information, etc. can be used as parameters in the PRU association release request. For example, an existing PRU association release request message can be used, and the PRU association release request message can carry a PRU association release request. The PRU association release request may include: the first device identifier, the second device identifier, the first indication information, and the second indication information AckIndication.

[0253] In some embodiments, the first device identifier, the second device identifier, and the first indication information may be transmitted together with the PRU association release request.

[0254] In some embodiments, in response to receiving a first message from a second device through a user plane for instructing to perform a positioning reference unit (PRU) deassociation operation with the second device, the first device may send a second message to a third device through a control plane, where the second message is used to request the third device to perform a PRU verification operation. Furthermore, the second message sent by the first device to the third device through the control plane may be an AMF service message of the control plane, where the AMF service message is used to trigger the AMF to perform the PRU verification operation.

[0255] In some embodiments, the second message sent by the first device to the third device through the control surface may include at least one of the following: a first device identification Correlation ID; a second device identification UE ID; first indication information PRU Indication; or a PRU association release request.

[0256] In the above embodiment, after the second device sends a first message to the first device through the user surface for instructing to perform a PRU association disassociation operation, the first device can send a second message to the third device through the control surface for instructing to perform a PRU verification operation, so that the PRU verification operation can be performed on the second device before the PRU association operation is performed, so as to avoid the first device performing an association operation on a non-PRU device, thereby saving communication resources and power consumption.

[0257] In some embodiments, the second device may send a first message to the first device via the user interface, causing the first device to send a second message to the third device via the control interface. In response to receiving the second message, the third device performs a PRU verification operation to obtain a PRU verification result, and may send a third message to the first device via the control interface, the third message indicating the PRU verification result obtained after the third device performs the PRU verification operation.

[0258] In some embodiments, the third message may be an AMF service message of the control plane, which is used to inform the first device of the PRU verification result obtained by the PRU verification operation.

[0259] In some embodiments, the third device performing the PRU verification operation in response to receiving the second message may include verifying whether the device corresponding to the second device identifier, that is, the second device, is a PRU, and the obtained PRU verification result is used to determine whether the device corresponding to the second device identifier is a PRU. If it is determined that the device corresponding to the second device identifier is a PRU, the obtained PRU verification result may be a verification success; if it is determined that the device corresponding to the second device identifier is not a PRU, the obtained PRU verification result may be a verification failure.

[0260] In some embodiments, the third message may be further used to indicate at least one of the following: a first device identifier Correlation ID; a second device identifier UE ID; first indication information PRU Indication; or the PRU verification result.

[0261] In some embodiments, if the PRU verification result obtained after the third device performs the RPU verification operation is verification failure, the failure reason of the verification failure can also be determined; accordingly, the third message can also include the failure reason of the verification failure.

[0262] Furthermore, the first device may receive a third message from a third device via a control plane, and the third message may include at least one of the following: a first device identifier, Correlation ID; a second device identifier, UE ID; a first indication information, PRU Indication; a PRU verification result; or a failure reason for verification failure.

[0263] In the above embodiment, the first device can send a second message to the third device, causing the third device to perform a PRU verification operation and send the obtained PRU verification result back to the first device. The first device can then determine whether to perform a PRU disassociation operation on the second device based on the PRU verification result. This can prevent the first device from erroneously performing a PRU disassociation operation on a non-PRU device, saving communication resources and power consumption.

[0264] In some embodiments, a first device may determine whether the first device is associated with a second device.

[0265] In some embodiments, after receiving a first message from a second device through a user plane to instruct a PRU disassociation operation with the second device, the first device can first determine whether the first device is associated with the second device, and then send a second message to the third device to request the third device to perform a PRU verification operation.

[0266] In some embodiments, after receiving a first message from a second device through a user plane to indicate a PRU disassociation operation with the second device, the first device may first send a second message to a third device to request the third device to perform a PRU verification operation; the first device may receive a third message from the third device, and the third message is used to indicate a PRU verification result; then the first device may further determine whether the first device is associated with the second device, and determine whether to perform a PRU disassociation operation with the second device based on the obtained association result.

[0267] In the above embodiment, before performing the PRU disassociation operation, the first device can first determine whether the first device is associated with the second device. If the first device and the second device are not associated, the PRU disassociation operation does not need to be performed. Accordingly, the first device can avoid performing the PRU disassociation operation with the unassociated second device, saving communication resources and power consumption.

[0268] In some embodiments, the second device may receive a fourth message from the first device, where the fourth message is used to indicate a PRU association release result obtained after performing a PRU association release operation with the first device.

[0269] In some embodiments, the second device may send a first message to the first device via the user plane to instruct a positioning reference unit PRU de-association operation with the second device; then, the first device may send a second message to the third device via the control plane to instruct the third device to perform a PRU verification operation; the first device may receive a third message from the third device via the control plane to obtain a PRU verification result; in response to receiving the third message, the first device may determine whether the first device is associated with the second device, and determine whether to perform a PRU de-association operation with the second device to obtain a PRU de-association result with the second device; then the second device may receive a fourth message sent by the first device.

[0270] In some embodiments, the second device can send a first message to the first device through the user plane to instruct the positioning reference unit PRU disassociation operation with the second device, so that when the first device determines that the first device is associated with the second device, it can send a second message to the third device through the control plane to instruct the third device to perform a PRU verification operation; the first device can receive a third message from the third device through the control plane to obtain a PRU verification result; in response to receiving the third message, the first device can determine whether to perform a PRU disassociation operation with the second device to obtain a PRU disassociation result with the second device; and then the second device can receive a fourth message sent by the first device.

[0271] In some embodiments, the second device may determine whether to receive the fourth message from the first device based on whether second indication information indicating an expectation to receive a confirmation message corresponding to the PRU association release request is sent to the first device.

[0272] In some embodiments, the first message sent by the second device to the first device carries second indication information, and the second indication information is used to indicate whether it is expected to receive a confirmation message corresponding to the PRU association release request; if the second indication information is used to indicate that it is expected to receive a confirmation message corresponding to the PRU association release request, the second device will receive a fourth message sent by the first device; if the second indication information is used to indicate that it is not expected to receive a confirmation message corresponding to the PRU association release request, the second device will not receive the fourth message.

[0273] In some embodiments, the second device may receive the fourth message from the first device through the user plane.

[0274] In some embodiments, the second device may receive the fourth message from the first device using a user plane positioning protocol. Further, the user plane positioning protocol may include at least one of the following: Location Service User Plane Protocol (LCS-UPP); or Secure User Plane Positioning (SUPL) protocol.

[0275] In some embodiments, the fourth message received by the second device from the first device through the user plane may also be used to indicate at least one of the following: a first device identifier Routing ID; a second device identifier UE ID; first indication information PRU Indication; or a PRU association release response.

[0276] The PRU association release response is used to indicate the result of the PRU association release with the second device. Further, the PRU association release response may include at least one of the following: the PRU association release result; or a failure reason for the PRU association release failure.

[0277] The above-mentioned information carried by the fourth message can be encapsulated in various ways in the fourth message. In some embodiments, a new PRU association release response message can be used as the fourth message. The new PRU association release response message can carry the first device identifier, the second device identifier, the first indication information and the PRU association release response. The PRU association release response may include the PRU association release result and the failure reason of the PRU association release failure.

[0278] In some embodiments, the first device identifier, the second device identifier, the first indication information, etc. can be used as parameters in the PRU association release response. For example, an existing PRU association release response message can be used, and the PRU association release response message can carry a PRU association release response. The PRU association release response may include: the first device identifier, the second device identifier, the first indication information, the PRU association release result, and the failure reason of the PRU association release failure.

[0279] In some embodiments, the first device identifier, the second device identifier, and the first indication information may be transmitted together with a PRU association release response, and the PRU association release response may include a PRU association release result and a failure reason for the PRU association release failure.

[0280] In the above embodiment, the first device can determine whether to perform the PRU association disassociation operation with the second device based on the PRU verification result received from the third device, thereby avoiding the first device from performing association operations with non-PRU devices, saving communication resources and power consumption.

[0281] In a third aspect, embodiments of the present disclosure provide a method for disassociating a positioning reference unit. Figure 5 is a schematic flow chart illustrating a method for disassociating a positioning reference unit according to an embodiment of the present disclosure. The method for disassociating a positioning reference unit illustrated in this embodiment can be performed by a third device. The third device can be a network device with access management functionality, such as an AMF in a core network device.

[0282] As shown in FIG5 , the method for disassociating a positioning reference unit may include the following steps:

[0283] In step S501, a second message is received from a first device, where the second message is used to request a positioning reference unit (PRU) verification operation. The second message is sent by the second device in response to receiving a first message from the first device through a user plane. The first message is used to instruct the first device to perform a PRU association disassociation operation with the second device.

[0284] In step S502, the PRU verification operation is performed.

[0285] In some embodiments, a first device may receive a first message from a second device via a user plane, where the first message may be used to instruct the first device to perform a PRU disassociation operation with the second device; a third device may then receive a second message from the first device, where the second message is used to request the third device to perform a PRU verification operation. After performing the PRU verification operation, the third device may send the obtained PRU verification result to the first device; if the PRU verification result is a successful verification, the first device may further determine whether to perform a PRU disassociation operation with the second device; if the PRU verification result is a failed verification, the first device may not perform the PRU disassociation operation.

[0286] For example, take the first device as LMF1, the second device as terminal T1, and the third device as AMF1 as an example. When terminal T1 determines to use the user plane to perform the PRU association release operation, terminal T1 can send a first message M1 to LMF1 through the user plane. The first message M1 is used to indicate that the PRU association release operation is to be performed with terminal T1. In response to receiving the first message M1, LMF1 can send a second message M2 to AMF1 through the control plane. The second message M2 is used to indicate that a PRU verification operation is to be performed; if the PRU verification result obtained by the PRU verification operation is a successful verification, LMF1 further determines whether to perform the PRU association release operation with terminal T1; if the PRU verification result is a failed verification, LMF1 will not perform the PRU association release operation with terminal T1.

[0287] It should be noted that the embodiment shown in FIG. 5 can be implemented independently or in combination with at least one other embodiment in the present disclosure. The specific selection can be made as needed and the present disclosure does not limit it.

[0288] In the above embodiment, when the serving LMF receives a PRU disassociation request from the second device through the user plane, it may first send a PRU verification request to the serving AMF to perform a PRU verification operation on the second device. Accordingly, whether to perform the PRU disassociation operation on the second device can be determined based on the PRU verification result of the second device, thereby avoiding the LMF from performing the disassociation operation on non-PRU devices, saving communication resources and power consumption.

[0289] In some embodiments, the first device may receive a first message from the second device using a user plane positioning protocol, where the first message is used to instruct the second device to perform a PRU disassociation operation. Further, the user plane positioning protocol may include at least one of the following: a Location Service User Plane Protocol (LCS-UPP); or a Secure User Plane Location (SUPL) protocol.

[0290] In some embodiments, the first message received by the first device from the second device through the user plane may be further used to indicate at least one of the following: a first device identifier; a second device identifier; first indication information; or a PRU association release request.

[0291] In some embodiments, the second message sent by the first device to the third device through the control surface may include at least one of the following: a first device identification Correlation ID; a second device identification UE ID; first indication information PRU Indication; or a PRU association release request.

[0292] Among them, the first device identifier is the device identifier corresponding to the first device or the device identifier corresponding to the service LMF of the second device. The first device identifier can be represented by a routing identifier (Routing ID) or a correlation identifier (Correlation ID). For example, the first device identifier can be represented by a Correlation ID in a message transmitted between an AMF and an LMF, and can be represented by a Routing ID in a message transmitted between the second device and the LMF.

[0293] The second device identifier is a device identifier corresponding to the second device. For example, if the second device is a terminal, it can be represented by a terminal identifier (UE ID). Furthermore, the second device identifier can specifically use at least one of the following identifiers corresponding to the second device: a subscription concealed identifier (SUCI); a subscription permanent identifier (SUPI); a generic public subscription identifier (GPSI); or an application layer identifier (Application Layer ID).

[0294] The first indication information is used to indicate that the second device may be a PRU. Furthermore, the first indication information may be explicitly indicated by a specific parameter or a specific value of an existing parameter, or may be implicitly indicated by a name of a request included in the first message.

[0295] The PRU association release request may be used to request the first device to perform a PRU association release operation. Further, the PRU association release request includes second indication information (AckIndication), which is used to indicate whether to expect to receive an acknowledgment message corresponding to the PRU association release request.

[0296] In some embodiments, the second message received by the third device from the first device through the control plane may be an AMF service message of the control plane, which is used to trigger the AMF to perform a PRU verification operation.

[0297] In the above embodiment, after the first device receives the first message sent by the second device through the user plane to instruct the PRU association release operation, it can send the second message for instructing the execution of the PRU verification operation to the third device through the control plane, so that the PRU verification operation can be performed on the second device before the PRU association operation is performed, so as to avoid the first device performing the association operation on the non-PRU device, thereby saving communication resources and power consumption.

[0298] In some embodiments, the third device performs a PRU verification operation in response to receiving the second message. After obtaining the PRU verification result, it can send a third message to the first device through the control surface. The third message is used to indicate the PRU verification result obtained after the third device performs the PRU verification operation.

[0299] In some embodiments, the third message may be an AMF service message of the control plane, which is used to inform the first device of the PRU verification result obtained by the PRU verification operation.

[0300] In some embodiments, the third device performing the PRU verification operation in response to receiving the second message may include verifying whether the device corresponding to the second device identifier, that is, the second device, is a PRU, and the obtained PRU verification result is used to determine whether the device corresponding to the second device identifier is a PRU. If it is determined that the device corresponding to the second device identifier is a PRU, the obtained PRU verification result may be a verification success; if it is determined that the device corresponding to the second device identifier is not a PRU, the obtained PRU verification result may be a verification failure.

[0301] For example, AMF1 receives a second message M2 from LMF1, and the second message M2 is used to instruct a PRU verification operation, and the second message M2 includes a second device identifier ID2 corresponding to the terminal T1. AMF1 can verify whether the device corresponding to ID2 (terminal T1) is a PRU based on the obtained PRU subscription information or local policy to obtain a PRU verification result. The subscription information of the PRU can be obtained from a unified data management entity (UDM); the local policy can maintain a device identifier list, which includes the device identifiers corresponding to each PRU. If it is determined that the terminal T1 is a PRU, the obtained PRU verification result is a successful verification; if it is determined that the terminal T1 is not a PRU, the obtained PRU verification result is a failed verification.

[0302] Furthermore, AMF1 can also determine whether the device corresponding to ID2 (terminal T1) is a static PRU based on the obtained PRU subscription information or local policy. If it is determined that terminal T1 is a static PRU, the obtained PRU verification result is verification success; if it is determined that terminal T1 is not a static PRU, the obtained PRU verification result is verification failure. For the sake of simplicity, the following embodiments are all illustrated by verifying whether the device corresponding to the second device identifier is a PRU.

[0303] In some embodiments, the third message may be further used to indicate at least one of the following: a first device identifier Correlation ID; a second device identifier UE ID; first indication information PRU Indication; or the PRU verification result.

[0304] In some embodiments, if the PRU verification result obtained after the third device performs the RPU verification operation is verification failure, the failure reason of the verification failure can also be determined; accordingly, the third message can also include the failure reason of the verification failure.

[0305] Furthermore, the third message sent by the third device to the first device through the control surface includes at least one of the following: the first device identification Correlation ID; the second device identification UE ID; the first indication information PRU Indication; the PRU verification result; or the failure reason of the verification failure.

[0306] In the above embodiment, the first device can send a second message to the third device, causing the third device to perform a PRU verification operation and send the obtained PRU verification result back to the first device. The first device can then determine whether to perform a PRU disassociation operation on the second device based on the PRU verification result. This can prevent the first device from erroneously performing a PRU disassociation operation on a non-PRU device, saving communication resources and power consumption.

[0307] In some embodiments, the names of information, etc. are not limited to the names described in the embodiments, and terms such as "information", "message", "signal", "signaling", "report", "configuration", "indication", "instruction", "command", "channel", "parameter", "domain", "field", "symbol", "symbol", "codeword", "codebook", "codeword", "codepoint", "bit", "data", "program", and "chip" can be used interchangeably.

[0308] In some embodiments, terms such as "moment", "time point", "time", and "time position" can be replaced with each other, and terms such as "duration", "period", "time window", "window", and "time" can be replaced with each other.

[0309] In some embodiments, the terms "component carrier (CC)", "cell", "frequency carrier", "carrier frequency" and the like can be used interchangeably.

[0310] In some embodiments, "obtain", "get", "get", "receive", "transmit", "bidirectional transmission", "send and / or receive" can be interchangeable, and can be interpreted as receiving from other entities, obtaining from protocols, obtaining from higher layers, obtaining by self-processing, autonomous implementation, etc.

[0311] In some embodiments, terms such as "send", "transmit", "report", "download", "transmit", "bidirectional transmission", "send and / or receive" can be used interchangeably.

[0312] Corresponding to the aforementioned embodiment of the method for disassociating a positioning reference unit, the present disclosure also provides embodiments of a terminal and a network device.

[0313] An embodiment of the present disclosure further proposes a terminal, comprising: one or more processors; a memory coupled to the processor, the memory storing executable instructions, wherein when the executable instructions are executed by the processor, the network device executes the positioning reference unit association decoupling method described in the above embodiment.

[0314] An embodiment of the present disclosure further proposes an access network device, comprising: one or more processors; a memory coupled to the processor, the memory storing executable instructions, wherein when the executable instructions are executed by the processor, the network device executes the positioning reference unit association decoupling method described in the above embodiment.

[0315] An embodiment of the present disclosure also proposes a core network device, comprising: one or more processors; a memory coupled to the processor, the memory storing executable instructions, wherein when the executable instructions are executed by the processor, the network device executes the positioning reference unit association decoupling method described in the above embodiment.

[0316] FIG6 is a schematic block diagram of a terminal device structure according to an embodiment of the present disclosure. As shown in FIG6 , the terminal may be a positioning reference unit association removal device, and the device includes a transceiver module 601 and a processing module 602 .

[0317] In some embodiments, the transceiver module 601 is used to receive a first message from a second device through a user plane, where the first message is used to instruct the positioning reference unit association device to perform a positioning reference unit PRU association removal operation with the second device; the transceiver module 601 is also used to send a second message to a third device, where the second message is used to request the third device to perform a PRU verification operation.

[0318] In some embodiments, the first message is a message using a user plane positioning protocol; wherein the user plane positioning protocol may include at least one of the following: Location Service User Plane Protocol LCS-UPP; Secure User Plane Positioning SUPL protocol.

[0319] In some embodiments, the first message is also used to indicate at least one of the following: a first device identifier, the first device identifier is a device identifier corresponding to the first device; a second device identifier, the second device identifier is a device identifier corresponding to the second device; first indication information, the first indication information is used to indicate that the second device is a PRU; a PRU association release request.

[0320] In some embodiments, the second message is an access and mobility management function AMF service message of the control plane.

[0321] In some embodiments, the second message is also used to indicate at least one of the following: a first device identifier, the first device identifier is a device identifier corresponding to the first device; a second device identifier, the second device identifier is a device identifier corresponding to the second device; first indication information, the first indication information is used to indicate that the second device is a PRU; a PRU association release request.

[0322] In some embodiments, the second device identifier includes at least one of the following: a subscription hidden identifier SUCI; a subscription permanent identifier SUPI; a general public user identifier GPSI; or an application layer identifier.

[0323] In some embodiments, the PRU association release request includes second indication information, where the second indication information is used to indicate whether it is expected to receive a confirmation message corresponding to the PRU association release request.

[0324] In some embodiments, the transceiver module 601 is further used to receive a third message from the third device, where the third message is used to indicate a PRU verification result, wherein the PRU verification result is obtained by the third device after performing the PRU verification operation.

[0325] In some embodiments, the third message is also used to indicate at least one of the following: a first device identifier, the third device identifier is a device identifier corresponding to the first device; a second device identifier, the second device identifier is a device identifier corresponding to the second device; first indication information, the first indication information is used to indicate that the second device supports the PRU function; and the PRU verification result.

[0326] In some embodiments, the third message is an AMF service message of the control plane.

[0327] In some embodiments, the PRU verification result is verification failure, and the third message is further used to indicate the reason for the verification failure.

[0328] In some embodiments, the PRU verification result is used to determine whether the device corresponding to the second device identifier is a PRU.

[0329] In some embodiments, the processing module 602 is configured to determine whether the first device is associated with the second device.

[0330] In some embodiments, the processing module 602 is also used to determine the result of the disassociation between the first device and the second device; the transceiver module 601 is also used to send a fourth message to the second device, and the fourth message is used to indicate the result of the disassociation between the first device and the second device.

[0331] In some embodiments, the transceiver module 601 is configured to determine that the first message is used to indicate an expectation to receive a confirmation message corresponding to the PRU association release request, and to send a fourth message to the second device.

[0332] In some embodiments, the fourth message is a message using a user plane positioning protocol; wherein the user plane positioning protocol may include at least one of the following: Location Service User Plane Protocol LCS-UPP; Secure User Plane Positioning SUPL protocol.

[0333] In some embodiments, the fourth message is also used to indicate at least one of the following: a first device identifier, the first device identifier is a device identifier corresponding to the first device; a second device identifier, the second device identifier is a device identifier corresponding to the second device; first indication information, the first indication information is used to indicate that the second device supports the PRU function; a PRU association release response, the PRU association release response is used to indicate the result of the association release between the first device and the second device.

[0334] In some embodiments, the second device is a location management function LMF.

[0335] In some embodiments, the third device is an AMF.

[0336] It should be noted that the modules included in the first device are not limited to the modules described in the above embodiments, and may also include other modules, such as a storage module, a display module, etc.

[0337] FIG7 is a schematic block diagram of a network device according to an embodiment of the present disclosure. As shown in FIG7 , the network device may be a positioning reference unit association removal device, and the device includes a transceiver module 701 and a processing module 702 .

[0338] In some embodiments, the processing module 702 is used to determine whether to perform a PRU association release operation through the user plane; the transceiver module 701 is used to send a first message to the first device through the user plane, and the first message is used to instruct the first device to perform a positioning reference unit PRU association release operation with the position reference unit association device, so that the first device sends a second message to the third device, and the second message is used to request the third device to perform a PRU verification operation.

[0339] In some embodiments, the first message is also used to indicate at least one of the following: a first device identifier, the first device identifier is a device identifier corresponding to the first device; a second device identifier, the second device identifier is a device identifier corresponding to the second device; first indication information, the first indication information is used to indicate that the second device is a PRU; a PRU association release request.

[0340] In some embodiments, the transceiver module 701 is used to receive a fourth message from the first device, where the fourth message is used to indicate a result of the disassociation between the first device and the second device.

[0341] In some embodiments, the fourth message is a message using a user plane positioning protocol; wherein the user plane positioning protocol may include at least one of the following: Location Service User Plane Protocol LCS-UPP; Secure User Plane Positioning SUPL protocol.

[0342] In some embodiments, the fourth message is also used to indicate at least one of the following: a first device identifier, the first device identifier is a device identifier corresponding to the first device; a second device identifier, the second device identifier is a device identifier corresponding to the second device; first indication information, the first indication information is used to indicate that the second device supports the PRU function; a PRU association release response, the PRU association release response is used to indicate the result of the association release between the first device and the second device.

[0343] It should be noted that the modules included in the second device are not limited to the modules described in the above embodiments, and may also include other modules, such as a storage module, a display module, etc.

[0344] FIG8 is a schematic block diagram illustrating a device structure of a network device according to an embodiment of the present disclosure. As shown in FIG8 , the network device may be a positioning reference unit association removal device, and the device includes a transceiver module 801 and a processing module 802 .

[0345] In some embodiments, the transceiver module 801 is used to receive a second message from a first device, where the second message is used to request a positioning reference unit PRU verification operation, and the second message is sent by the second device after receiving the first message from the first device through the user plane, and the first message is used to instruct the first device to perform a PRU association removal operation with the second device; the processing module 802 is used to perform the PRU verification operation.

[0346] In some embodiments, the second message is also used to indicate at least one of the following: a first device identifier, the first device identifier is a device identifier corresponding to the first device; a second device identifier, the second device identifier is a device identifier corresponding to the second device; first indication information, the first indication information is used to indicate that the second device is a PRU; a PRU association release request.

[0347] In some embodiments, the method further includes: sending a third message to the first device, where the third message is used to indicate a PRU verification result obtained after the third device performs the PRU verification operation.

[0348] In some embodiments, the third message is also used to indicate at least one of the following: a first device identifier, the third device identifier is a device identifier corresponding to the first device; a second device identifier, the second device identifier is a device identifier corresponding to the second device; first indication information, the first indication information is used to indicate that the second device supports the PRU function; and the PRU verification result.

[0349] In some embodiments, the PRU verification result is verification failure, and the third message is further used to indicate the reason for the verification failure.

[0350] It should be noted that the modules included in the third device are not limited to the modules described in the above embodiments, and may also include other modules, such as a storage module, a display module, etc.

[0351] For the device embodiment, since it basically corresponds to the method embodiment, the relevant parts can be referred to the partial description of the method embodiment. The device embodiment described above is merely illustrative, wherein the modules described as separate components may or may not be physically separated, and the components displayed as modules may or may not be physical modules, that is, they may be located in one place, or they may be distributed on multiple network modules. Some or all of the modules can be selected according to actual needs to achieve the purpose of the scheme of this embodiment. Those of ordinary skill in the art can understand and implement it without paying any creative work.

[0352] An embodiment of the present disclosure further proposes a communication device, comprising: one or more processors; a memory coupled to the processor, the memory storing executable instructions, wherein when the executable instructions are executed by the processor, the processor calls the executable instructions so that the communication device executes the positioning reference unit association decoupling method described in the above optional embodiment.

[0353] An embodiment of the present disclosure further proposes a communication system, including a terminal and a network device, wherein the terminal is configured to implement the positioning reference unit association release method described in the above optional embodiment, and the network device is configured to implement the positioning reference unit association release method described in the above optional embodiment.

[0354] An embodiment of the present disclosure further provides a storage medium storing instructions. When the instructions are executed on a communication device, the communication device executes the positioning reference unit de-association method described in the above optional embodiment.

[0355] The embodiments of the present disclosure further provide an apparatus for implementing any of the above methods. For example, an apparatus is provided, comprising units or modules for implementing each step performed by a terminal in any of the above methods. For another example, another apparatus is provided, comprising units or modules for implementing each step performed by a network device (e.g., an access network device, a core network function node, a core network device, etc.) in any of the above methods.

[0356] It should be understood that the division of the various units or modules in the above device is merely a division of logical functions. In actual implementation, they may be fully or partially integrated into a physical entity, or they may be physically separated. In addition, the units or modules in the device may be implemented in the form of a processor calling software: for example, the device includes a processor, the processor is connected to a memory, and the memory stores instructions. The processor calls the instructions stored in the memory to implement any of the above methods or implement the functions of the various units or modules of the above device, wherein the processor is, for example, a general-purpose processor, such as a central processing unit (CPU) or a microprocessor, and the memory is a memory within the device or a memory outside the device. Alternatively, the units or modules in the device can be implemented in the form of hardware circuits, and the functions of some or all of the units or modules can be realized by designing the hardware circuits. The above-mentioned hardware circuits can be understood as one or more processors; for example, in one implementation, the above-mentioned hardware circuit is an application-specific integrated circuit (ASIC), which realizes the functions of some or all of the above units or modules by designing the logical relationship of the components in the circuit; for example, in another implementation, the above-mentioned hardware circuit can be realized by a programmable logic device (PLD). Taking a field programmable gate array (FPGA) as an example, it can include a large number of logic gate circuits, and the connection relationship between the logic gate circuits is configured by configuring the configuration file, thereby realizing the functions of some or all of the above units or modules. All units or modules of the above devices can be realized in the form of software called by the processor, or in the form of hardware circuits, or in part by the form of software called by the processor, and the rest by hardware circuits.

[0357] In the embodiments of the present disclosure, the processor is a circuit with signal processing capabilities. In one implementation, the processor can be a circuit with instruction reading and execution capabilities, such as a central processing unit (CPU), a microprocessor, a graphics processing unit (GPU) (which can be understood as a microprocessor), or a digital signal processor (DSP). In another implementation, the processor can implement certain functions through the logical relationship of the hardware circuit. The logical relationship of the above-mentioned hardware circuit is fixed or reconfigurable. For example, the processor is a hardware circuit implemented by an application-specific integrated circuit (ASIC) or a programmable logic device (PLD), such as an FPGA. In a reconfigurable hardware circuit, the process of the processor loading a configuration document and implementing the hardware circuit configuration can be understood as the process of the processor loading instructions to implement the functions of some or all of the above units or modules. In addition, it can also be a hardware circuit designed for artificial intelligence, which can be understood as an ASIC, such as a neural network processing unit (NPU), a tensor processing unit (TPU), a deep learning processing unit (DPU), etc.

[0358] Figure 9 is a schematic diagram of the structure of a communication device 9100 proposed in an embodiment of the present disclosure. Communication device 9100 can be a network device (e.g., an access network device, a core network device, etc.), a terminal (e.g., a user device, etc.), a chip, a chip system, or a processor that supports a network device to implement any of the above methods, or a chip, a chip system, or a processor that supports a terminal to implement any of the above methods. Communication device 9100 can be used to implement the methods described in the above method embodiments. For details, please refer to the description of the above method embodiments.

[0359] As shown in Figure 9, the communication device 9100 includes one or more processors 9101. The processor 9101 can be a general-purpose processor or a dedicated processor, for example, a baseband processor or a central processing unit. The baseband processor can be used to process communication protocols and communication data, and the central processing unit can be used to control the communication device (such as a base station, a baseband chip, a terminal device, a terminal device chip, a DU or a CU, etc.), execute programs, and process program data. The processor 9101 is used to call instructions to enable the communication device 9100 to perform any of the above methods.

[0360] In some embodiments, the communication device 9100 further includes one or more memories 9102 for storing instructions. Optionally, all or part of the memories 9102 may be located outside the communication device 9100.

[0361] In some embodiments, the communication device 9100 further includes one or more transceivers 9103. When the communication device 9100 includes one or more transceivers 9103, the communication steps such as sending and receiving in the above method are performed by the transceiver 9103, and the other steps are performed by the processor 9101.

[0362] In some embodiments, a transceiver may include a receiver and a transmitter, which may be separate or integrated. Optionally, the terms transceiver, transceiver unit, transceiver, and transceiver circuit may be used interchangeably; the terms transmitter, transmitting unit, transmitter, and transmitting circuit may be used interchangeably; and the terms receiver, receiving unit, receiver, and receiving circuit may be used interchangeably.

[0363] Optionally, the communication device 9100 further includes one or more interface circuits 9104, which are connected to the memory 9102. The interface circuits 9104 can be used to receive signals from the memory 9102 or other devices, and can be used to send signals to the memory 9102 or other devices. For example, the interface circuits 9104 can read instructions stored in the memory 9102 and send the instructions to the processor 9101.

[0364] The communication device 9100 described in the above embodiments may be a network device or a terminal, but the scope of the communication device 9100 described in the present disclosure is not limited thereto, and the structure of the communication device 9100 may not be limited by FIG. 9 . The communication device may be an independent device or may be part of a larger device. For example, the communication device may be: 1) an independent integrated circuit IC, or a chip, or a chip system or subsystem; (2) a collection of one or more ICs, optionally, the above IC collection may also include a storage component for storing data or programs; (3) an ASIC, such as a modem; (4) a module that can be embedded in other devices; (5) a receiver, a terminal device, an intelligent terminal device, a cellular phone, a wireless device, a handheld device, a mobile unit, an in-vehicle device, a network device, a cloud device, an artificial intelligence device, etc.; (6) others, etc.

[0365] FIG10 is a schematic diagram of the structure of a chip 10200 according to an embodiment of the present disclosure. If the communication device 9100 can be a chip or a chip system, reference can be made to the schematic diagram of the structure of the chip 10200 shown in FIG10 , but the present disclosure is not limited thereto.

[0366] Chip 10200 includes one or more processors 10201, and processor 10201 is used to call instructions to enable chip 10200 to execute any of the above methods.

[0367] In some embodiments, the chip 10200 further includes one or more interface circuits 10202, which are connected to the memory 10203. The interface circuit 10202 can be used to receive signals from the memory 10203 or other devices, and can be used to send signals to the memory.

[0368] 10203 or other devices to send signals. For example, the interface circuit 10202 can read the instructions stored in the memory 10203 and send the instructions to the processor 10201. Optionally, the terms interface circuit, interface, transceiver pin, transceiver, etc. can be used interchangeably.

[0369] In some embodiments, the chip 10200 further includes one or more memories 10203 for storing instructions. Alternatively, all or part of the memories 10203 may be outside the chip 10200.

[0370] The present disclosure also proposes a storage medium having instructions stored thereon, which, when executed on the communication device 9100, causes the communication device 9100 to execute any of the above methods. Optionally, the storage medium is an electronic storage medium. Optionally, the storage medium is a computer-readable storage medium, but is not limited thereto and may also be a storage medium readable by other devices. Optionally, the storage medium may be a non-transitory storage medium, but is not limited thereto and may also be a temporary storage medium.

[0371] The present disclosure also provides a program product, which, when executed by the communication device 9100, enables the communication device 7100 to perform any of the above methods. Optionally, the program product is a computer program product.

[0372] The present disclosure also proposes a computer program, which, when executed on a computer, causes the computer to perform any one of the above methods.

Claims

1. A method for disassociating a positioning reference unit, characterized in that: Executed by a first device, the method includes: receiving a first message from a second device through a user plane, where the first message is used to instruct the first device to perform a positioning reference unit PRU association disassociation operation with the second device; A second message is sent to a third device, where the second message is used to request the third device to perform a PRU verification operation.

2. The method according to claim 1, characterized in that The first message is a message using a user plane positioning protocol; The user plane positioning protocol includes at least one of the following: Location service user plane protocol LCS-UPP; Secure User Plane Location SUPL protocol.

3. The method according to any one of claims 1-2, characterized in that: The first message is further used to indicate at least one of the following: A first device identifier, where the first device identifier is a device identifier corresponding to the first device; A second device identifier, where the second device identifier is a device identifier corresponding to the second device; first indication information, where the first indication information is used to indicate that the second device is a PRU; PRU disassociation request.

4. The method according to any one of claims 1 to 3, characterized in that: The second message is an access and mobility management function AMF service message of the control plane.

5. The method according to any one of claims 1 to 4, characterized in that: The second message is further used to indicate at least one of the following: A first device identifier, where the first device identifier is a device identifier corresponding to the first device; A second device identifier, where the second device identifier is a device identifier corresponding to the second device; first indication information, where the first indication information is used to indicate that the second device is a PRU; PRU disassociation request.

6. The method according to claim 3 or 5, characterized in that: The second device identification includes at least one of the following: Sign the hidden logo SUCI; Sign the permanent logo SUPI; General Public User Identity GPSI; Application layer identifier.

7. The method according to claim 3 or 5, characterized in that: The PRU association release request includes second indication information, where the second indication information is used to indicate whether it is expected to receive a confirmation message corresponding to the PRU association release request.

8. The method according to any one of claims 1 to 7, characterized in that: The method further comprises: A third message is received from the third device, where the third message is used to indicate a PRU verification result, wherein the PRU verification result is obtained by the third device after performing the PRU verification operation.

9. The method according to claim 8, characterized in that The third message is further used to indicate at least one of the following: a first device identifier, wherein the third device identifier is a device identifier corresponding to the first device; A second device identifier, where the second device identifier is a device identifier corresponding to the second device; first indication information, where the first indication information is used to indicate that the second device supports a PRU function; The PRU verifies the result.

10. The method according to claim 8, characterized in that The third message is the AMF service message of the control plane.

11. The method according to claim 8, characterized in that The PRU verification result is verification failure, and the third message is also used to indicate the reason for the verification failure.

12. The method according to claim 8, characterized in that The PRU verification result is used to determine whether the device corresponding to the second device identifier is a PRU.

13. The method according to any one of claims 8 to 12, characterized in that: The method further comprises: Determine whether the first device is associated with the second device.

14. The method according to any one of claims 8 to 13, characterized in that: The method further comprises: Determine a result of disassociating the first device from the second device; A fourth message is sent to the second device, where the fourth message is used to indicate a result of releasing the association between the first device and the second device.

15. The method according to claim 14, characterized in that The sending a fourth message to the second device includes: Determine that the first message is used to indicate that an acknowledgement message corresponding to the PRU association release request is expected to be received, and send a fourth message to the second device.

16. The method according to claim 14, characterized in that The fourth message is a message using a user plane positioning protocol; The user plane positioning protocol includes at least one of the following: Location service user plane protocol LCS-UPP; Secure User Plane Location SUPL protocol.

17. The method according to claim 16, characterized in that The fourth message is further used to indicate at least one of the following: A first device identifier, where the first device identifier is a device identifier corresponding to the first device; A second device identifier, where the second device identifier is a device identifier corresponding to the second device; first indication information, where the first indication information is used to indicate that the second device supports a PRU function; A PRU association release response, where the PRU association release response is used to indicate a result of the association release between the first device and the second device.

18. The method according to any one of claims 1 to 17, characterized in that: The second device is a location management function LMF.

19. The method according to any one of claims 1 to 18, characterized in that: The third device is AMF.

20. A method for removing association of a positioning reference unit, characterized in that: Executed by a second device, the method includes: Determining to perform a PRU association disassociation operation through a user plane; A first message is sent to the first device via a user, where the first message is used to instruct the first device to perform a positioning reference unit PRU association removal operation with the second device.

21. The method according to claim 20, characterized in that The first message is further used to indicate at least one of the following: A first device identifier, where the first device identifier is a device identifier corresponding to the first device; A second device identifier, where the second device identifier is a device identifier corresponding to the second device; first indication information, where the first indication information is used to indicate that the second device is a PRU; PRU disassociation request.

22. The method according to claim 20, characterized in that The method further comprises: A fourth message is received from the first device, where the fourth message is used to indicate a result of the disassociation between the first device and the second device.

23. The method according to claim 22, characterized in that The fourth message is a message using a user plane positioning protocol; The user plane positioning protocol includes at least one of the following: Location service user plane protocol LCS-UPP; Secure User Plane Location SUPL protocol.

24. The method according to claim 22, characterized in that The fourth message is further used to indicate at least one of the following: A first device identifier, where the first device identifier is a device identifier corresponding to the first device; A second device identifier, where the second device identifier is a device identifier corresponding to the second device; first indication information, where the first indication information is used to indicate that the second device supports a PRU function; A PRU association release response, where the PRU association release response is used to indicate a result of the association release between the first device and the second device.

25. A method for removing the association of a positioning reference unit, characterized in that: Executed by a third device, the method includes: receiving a second message from a first device, where the second message is used to request to perform a positioning reference unit (PRU) verification operation, where the second message is sent by the second device after receiving a first message from the first device through a user plane, where the first message is used to instruct the first device to perform a PRU association release operation with the second device; The PRU verification operation is performed.

26. The method according to claim 25, characterized in that The second message is further used to indicate at least one of the following: A first device identifier, where the first device identifier is a device identifier corresponding to the first device; A second device identifier, where the second device identifier is a device identifier corresponding to the second device; first indication information, where the first indication information is used to indicate that the second device is a PRU; PRU disassociation request.

27. The method according to claim 25 or 26, characterized in that The method further comprises: Sending a third message to the first device, wherein the third message is used to instruct the third device to execute the PRU The PRU verification result obtained after the verification operation.

28. The method according to claim 27, characterized in that The third message is further used to indicate at least one of the following: a first device identifier, wherein the third device identifier is a device identifier corresponding to the first device; A second device identifier, where the second device identifier is a device identifier corresponding to the second device; first indication information, where the first indication information is used to indicate that the second device supports a PRU function; The PRU verifies the result.

29. The method according to claim 28, characterized in that The PRU verification result is verification failure, and the third message is also used to indicate the reason for the verification failure.

30. A positioning reference unit association device, characterized in that: The device comprises: a transceiver module, configured to receive a first message from a second device through a user plane, wherein the first message is used to instruct the positioning reference unit associating apparatus to perform a positioning reference unit PRU association removal operation on the second device; The transceiver module is further used to send a second message to the third device, where the second message is used to request the third device to perform a PRU verification operation.

31. A positioning reference unit association device, characterized in that: The device comprises: A processing module, used for determining to perform a PRU association release operation through a user plane; The transceiver module is used to send a first message to the first device through a user, wherein the first message is used to instruct the first device to perform a positioning reference unit PRU association removal operation with the position reference unit association device.

32. A positioning reference unit association device, characterized in that: The device comprises: a transceiver module, configured to receive a second message from a first device, where the second message is used to request to perform a positioning reference unit PRU verification operation, where the second message is sent after the second device receives a first message from the first device through a user plane, and the first message is used to instruct the first device to perform a PRU association release operation with the second device; A processing module is used to perform the PRU verification operation.

33. A terminal, characterized in that: include: one or more processors; A memory coupled to the processor, wherein the memory stores executable instructions, wherein when the executable instructions are executed by the processor, the terminal executes the positioning reference unit association release method described in any one of claims 20-24.

34. An access network device, characterized in that: include: one or more processors; A memory coupled to the processor, wherein the memory stores executable instructions, wherein when the executable instructions are executed by the processor, the access network device executes the information receiving method described in any one of claims 20-24.

35. A core network device, characterized in that: include: one or more processors; A memory coupled to the processor, wherein the memory stores executable instructions, wherein when the executable instructions are executed by the processor, the core network device executes the information receiving method described in any one of claims 1-19 and / or the positioning reference unit association release method described in any one of claims 25-29.

36. A communication device, characterized in that: include: one or more processors; A memory coupled to the processor, wherein the memory stores executable instructions, wherein when the executable instructions are executed by the processor, the processor is used to call instructions so that the communication device executes the positioning reference unit association release method described in any one of claims 1 to 19, and / or the positioning reference unit association release method described in any one of claims 20 to 24, and / or the positioning reference unit association release method described in any one of claims 25 to 29.

37. A communication system, characterized in that: The method comprises a first device, a second device and a third device, wherein the first device is configured to implement the positioning reference unit association decoupling method described in any one of claims 1 to 19, the second device is configured to implement the positioning reference unit association decoupling method described in any one of claims 20 to 24, and the third device is configured to implement the positioning reference unit association decoupling method described in any one of claims 25 to 29.

38. A storage medium storing instructions, characterized in that: When the instruction is executed on a communication device, the communication device executes the positioning reference unit association release method described in any one of claims 1 to 19, and / or the positioning reference unit association release method described in any one of claims 20 to 24, and / or the positioning reference unit association release method described in any one of claims 25 to 29.

Images