Communication method, device and system, storage medium and program product

Abstract

Provided in an embodiment of the present disclosure are a communication method, device, system, storage medium and program product, the method being executed by a first network element, the method comprising: receiving a first request message sent by a second network element, the first request message being used for requesting information of a terminal in an area and / or information of a PRU in the area from the first network element; and sending a first response message to the second network element, wherein the first response message is used for providing the information of the terminal in the region and / or the information of the PRU in the region for the second network element. In the embodiments of the present disclosure, the first network element provides the information of the terminal and / or the information of the PRU in the region to the second network element by sending the first response information to the second network element, thereby facilitating the second network element to identify the PRU according to the information of the terminal and / or the information of the PRU.

Description

Technical Field

[0001] This disclosure relates to the field of communication technology, and in particular to a communication method, device, system, storage medium, and program product. Background Technology

[0002] Currently, location management function (LMF) network elements can train positioning models by acquiring relevant data from terminals. The types of terminals include those that can be used as positioning reference units (PRUs) and terminals. The methods used by the LMF network element to acquire relevant data differ for PRUs and terminals. Summary of the Invention

[0003] This disclosure provides a communication method, device, system, storage medium, and program product to provide a second network element with information about terminals and / or PRUs within the area.

[0004] According to a first aspect of the embodiments of this disclosure, a communication method is provided, executed by a first network element, the method comprising:

[0005] Receive a first request message sent by the second network element. The first request message is used to request information of terminals in the area and / or information of positioning reference units (PRUs) in the area from the first network element.

[0006] Send a first response message to the second network element. The first response message is used to provide the second network element with information about terminals in the area and / or information about PRUs in the area.

[0007] In this embodiment of the disclosure, the first network element can learn that the second network element is requesting information about terminals and / or PRUs within the area from the second network element by receiving a first request message. Thus, by sending a first response message to the second network element, the first network element provides the information about terminals and / or PRUs within the area to the second network element, which helps the second network element to identify the PRU based on the terminal information and / or PRU information.

[0008] According to a second aspect of the embodiments of this disclosure, a communication method is provided, executed by a second network element, the method comprising:

[0009] Send a first request message to the first network element. The first request message is used to request information about terminals in the area and / or information about PRUs in the area from the first network element.

[0010] The system receives a first response message sent by a first network element. The first response message is used to provide the second network element with information about terminals within the area and / or information about PRUs within the area.

[0011] In this embodiment of the disclosure, the second network element requests information about terminals and / or PRUs within the area from the first network element by sending a first request message to the first network element, and then receives a first response message sent by the first network element, thereby obtaining information about terminals and / or PRUs within the area, which helps the second network element identify the PRU based on the terminal information and / or PRU information.

[0012] According to a third aspect of the embodiments of this disclosure, a communication method is proposed, executed by a third network element, the method comprising:

[0013] Receive the first notification message sent by the first network element;

[0014] The first notification message is used to request the establishment of an association between the PRU and the third network element, where the third network element is the serving network element selected by the first network element.

[0015] In this embodiment of the disclosure, the third network element receives a first notification message sent by the first network element, thereby enabling it to establish an association between the PRU and the third network element according to the instructions of the first notification message.

[0016] According to a fourth aspect of the embodiments of this disclosure, a communication method is proposed, executed by a fourth network element, the method comprising:

[0017] Receive a second request message sent by the first network element, the second request message being used to request subscription information for at least one PRU;

[0018] Send a second response message to the first network element. The second response message includes subscription information of at least one PRU. The subscription information of at least one PRU is used to verify whether at least one PRU has the function of a PRU and / or whether at least one PRU belongs to a fixed PRU.

[0019] In this embodiment of the disclosure, the fourth network element can learn from the first network element's request for at least one PRU through the second request message, and thus can provide the first network element with the subscription information of at least one PRU through the second response message.

[0020] According to a fifth aspect of the embodiments of this disclosure, a first network element is proposed, comprising:

[0021] The transceiver module is used to receive a first request message sent by the second network element. The first request message is used to request information of terminals in the area and / or information of PRUs in the area from the first network element.

[0022] The transceiver module is also used to send a first response message to the second network element. The first response message is used to provide the second network element with information about terminals within the area and / or information about PRUs within the area.

[0023] According to a sixth aspect of the embodiments of this disclosure, a second network element is proposed, comprising:

[0024] The transceiver module is used to send a first request message to the first network element. The first request message is used to request information of terminals within the area and / or information of PRUs within the area from the first network element.

[0025] The transceiver module is also used to receive a first response message sent by the first network element. The first response message is used to provide the second network element with information about terminals within the area and / or information about PRUs within the area.

[0026] According to a seventh aspect of the embodiments of this disclosure, a third network element is proposed, comprising:

[0027] The transceiver module is used to receive the first notification message sent by the first network element;

[0028] The first notification message is used to request the establishment of an association between the PRU and the third network element, where the third network element is the serving network element selected by the first network element.

[0029] According to an eighth aspect of the embodiments of this disclosure, a fourth network element is proposed, comprising:

[0030] The transceiver module is used to receive a second request message sent by the first network element. The second request message is used to request subscription information of at least one PRU.

[0031] The transceiver module is also used to send a second response message to the first network element. The second response message includes subscription information of at least one PRU. The subscription information of at least one PRU is used to verify whether at least one PRU has the function of a PRU and / or whether at least one PRU belongs to a fixed PRU.

[0032] According to a ninth aspect of the present disclosure, a communication system is provided, comprising: a first network element, a second network element, a third network element, and a fourth network element;

[0033] The first network element is configured to implement the method described in the optional implementation of the first aspect; the second network element is configured to implement the method described in the optional implementation of the second aspect; the third network element is configured to implement the method described in the optional implementation of the third aspect; and the fourth network element is configured to implement the method described in the optional implementation of the fourth aspect.

[0034] According to a tenth aspect of the present disclosure, a storage medium is provided that stores instructions, which, when executed on a communication device, cause the communication device to perform a method as described in an optional implementation of the first aspect, or a method described in an optional implementation of the second aspect, or a method described in an optional implementation of the third aspect, or a method described in an optional implementation of the fourth aspect.

[0035] According to an eleventh aspect of the present disclosure, a program product is provided, including a program and / or instructions, which, when executed by a communication device, implement the method described in the optional implementation of the first aspect, or the method described in the optional implementation of the second aspect, or the method described in the optional implementation of the third aspect, or the method described in the optional implementation of the fourth aspect. Attached Figure Description

[0036] To more clearly illustrate the technical solutions in the embodiments of this disclosure, the accompanying drawings required for the description of the embodiments are introduced below. The following drawings are only some embodiments of this disclosure and do not impose specific limitations on the protection scope of this disclosure.

[0037] Figure 1a This is a schematic diagram of the architecture of a communication system according to an embodiment of the present disclosure;

[0038] Figure 1b This is an exemplary interactive diagram of the PRU association process provided in the embodiments of this disclosure;

[0039] Figure 1c This is a flowchart of data collection by an LMF network element provided in an embodiment of this disclosure;

[0040] Figure 2a This is an exemplary interaction diagram of the communication method provided in this embodiment of the disclosure;

[0041] Figure 2b This is a second exemplary interaction diagram of the communication method provided in this embodiment of the disclosure;

[0042] Figure 2c This is an exemplary interaction diagram of the communication method provided in this embodiment. Figure 3 ;

[0043] Figure 3 This is an exemplary interaction diagram four of the communication method provided in the embodiments of this disclosure;

[0044] Figure 4a This is a schematic diagram of the structure of the first network element proposed in the embodiments of this disclosure;

[0045] Figure 4b This is a schematic diagram of the structure of the second network element proposed in an embodiment of this disclosure;

[0046] Figure 4c This is a schematic diagram of the structure of the third network element proposed in the embodiments of this disclosure;

[0047] Figure 4d This is a schematic diagram of the structure of the fourth network element proposed in the embodiments of this disclosure;

[0048] Figure 5a This is a schematic diagram of the structure of the communication device proposed in the embodiments of this disclosure;

[0049] Figure 5b This is a schematic diagram of the chip structure proposed in the embodiments of this disclosure. Detailed Implementation

[0050] This disclosure provides a communication method, device, system, storage medium, and program product to provide a second network element with information about terminals and / or PRUs within the area.

[0051] According to a first aspect of the embodiments of this disclosure, a communication method is provided, executed by a first network element, the method comprising:

[0052] Receive a first request message sent by a second network element, the first request message being used to request information of terminals within the area and / or information of PRUs within the area from the first network element;

[0053] Send a first response message to the second network element. The first response message is used to provide the second network element with information about terminals in the area and / or information about PRUs in the area.

[0054] In this embodiment of the disclosure, the first network element can learn that the second network element is requesting information about terminals and / or PRUs within the area from the second network element by receiving a first request message. Thus, by sending a first response message to the second network element, the first network element provides the information about terminals and / or PRUs within the area to the second network element, which helps the second network element to identify the PRU based on the terminal information and / or PRU information.

[0055] In conjunction with some embodiments of the first aspect, in some embodiments, the first request message is used to request at least one of the following from the first network element:

[0056] Information on PRUs within the region;

[0057] Indication of PRU within the area;

[0058] Identification of terminals within the area;

[0059] Location capability information of terminals within the area.

[0060] In this embodiment of the disclosure, the first network element can obtain at least one of the following by receiving the first request message sent by the second network element: information of PRUs in the area, indication of PRUs in the area, identifier of terminals in the area, and positioning capability information of terminals in the area. This helps the first network element to provide the second network element with the corresponding information more flexibly based on the information requested by the second network element.

[0061] In conjunction with some embodiments of the first aspect, in some embodiments, the method further includes:

[0062] Based on the first request message, determine the list of terminals within the area, and determine the information of the terminals within the area.

[0063] In this embodiment of the present disclosure, after receiving the first request message sent by the second network element, the first network element can determine the terminal list in the area and the terminal information in the area, thereby providing the second network element with the terminal list and terminal information in the area through the first response message, which helps the second network element to identify the PRU in the terminal list based on the terminal information in the area.

[0064] In conjunction with some embodiments of the first aspect, in some embodiments, the terminal list includes PRUs (Personal Request Units) to determine information about terminals within the area, including:

[0065] Based on the PRU information stored in the first network element, determine the PRU information in the terminal list.

[0066] In this embodiment of the present disclosure, the first network element can pre-store PRU information. After receiving the first request message sent by the second network element, it can determine the PRU information in the terminal list from the locally stored PRU information, thereby providing the terminal list and the PRU information in the terminal list to the second network element, which helps the second network element to identify the PRU in the terminal list based on the PRU information in the terminal list.

[0067] In conjunction with some embodiments of the first aspect, in some embodiments, the method further includes:

[0068] Upon receiving a PRU association request message from a PRU, the PRU is verified based on its subscription information to obtain a first verification result and / or a second verification result. The first verification result is used to indicate whether the PRU has PRU functionality; the second verification result is used to indicate whether the PRU belongs to a fixed PRU.

[0069] Store at least one of the following information: PRU identifier, PRU subscription information, first verification result, and second verification result.

[0070] In this embodiment of the disclosure, when the first network element receives a PRU association request message sent by the PRU, the first network element verifies the PRU and stores at least one of the following: the PRU's identifier, the PRU's subscription information, the first verification result, and the second verification result. Therefore, the first network element can provide the above-mentioned at least one piece of information to the second network element by retrieving the locally stored PRU information, which helps the second network element identify the PRU in the terminal list based on the above-mentioned at least one piece of information.

[0071] In conjunction with some embodiments of the first aspect, in some embodiments, the method further includes:

[0072] If the first verification result indicates that the PRU has PRU functionality, a first notification message is sent to the serving network element selected by the first network element.

[0073] The first notification message is used to request the establishment of an association between the PRU and the service network element; the service network element is either the second network element or the third network element.

[0074] In this embodiment of the disclosure, when the first verification result indicates that the PRU has PRU functionality, the first network element can trigger the establishment of an association between the PRU and the service network element by sending a first notification message to the selected service network element.

[0075] In conjunction with some embodiments of the first aspect, in some embodiments, the method further includes:

[0076] The system receives a second notification message sent by a serving network element. The second notification message includes at least one of the following: first indication information, PRU location, association identifier, and PRU identifier. The first indication information is used to indicate that the association between the PRU and the serving network element has been successfully established, and the association identifier is used to identify the serving network element and / or the association.

[0077] Store at least one of the following: first instruction information, PRU location, association identifier, and PRU identifier.

[0078] In this embodiment of the disclosure, when a successful association is established between the PRU and the serving network element, the first network element stores at least one of the following: first indication information, the location of the PRU, the association identifier, and the identifier of the PRU. Therefore, the first network element can provide the above-mentioned at least one piece of information to the second network element by retrieving the locally stored PRU information, which helps the second network element identify the PRU in the terminal list based on the above-mentioned at least one piece of information.

[0079] In conjunction with some embodiments of the first aspect, in some embodiments, the method further includes:

[0080] If the information of at least one PRU in the terminal list is not found in the PRU information stored in the first network element, a second request message is sent to the fourth network element. The second request message is used to request the subscription information of at least one PRU.

[0081] Receive a second response message sent by a fourth network element, the second response message including subscription information of at least one PRU.

[0082] Store subscription information for at least one PRU.

[0083] In this embodiment of the present disclosure, if the first network element does not find information of at least one PRU in the locally stored PRU information, it requests subscription information of at least one PRU from the fourth network element through a second request message and stores the subscription information of at least one PRU. This enables the second network element to provide the subscription information of at least one PRU to the second network element, which helps the second network element to identify at least one PRU in the terminal list based on the subscription information of at least one PRU.

[0084] In conjunction with some embodiments of the first aspect, in some embodiments, for any PRU in at least one PRU, the method further includes:

[0085] The PRU is verified based on its subscription information to obtain a first verification result and / or a second verification result; the first verification result is used to indicate whether the PRU has PRU functionality; the second verification result is used to indicate whether the PRU is a fixed PRU.

[0086] Store the first verification result and / or the second verification result.

[0087] In this embodiment of the present disclosure, the first network element verifies the PRU to obtain a first verification result and / or a second verification result, and stores the first verification result and / or the second verification result, thereby enabling the first verification result and / or the second verification result to be provided to the second network element, which helps the second network element to identify the PRU in the terminal list based on the first verification result and / or the second verification result.

[0088] In conjunction with some embodiments of the first aspect, in some embodiments, the first response message includes at least one of the following:

[0089] Identification of terminals within the area;

[0090] Location capability information of terminals within the area;

[0091] Terminal subscription information;

[0092] Information on PRUs within the region;

[0093] The second instruction information is used to indicate the PRU within the area.

[0094] In this embodiment of the disclosure, the first network element provides the above information to the second network element through a first response message, which helps the second network element to identify the PRU in the terminal list based on the above information.

[0095] In conjunction with some embodiments of the first aspect, in some embodiments, the PRU information includes at least one of the following:

[0096] The PRU identifier;

[0097] The subscription information of the PRU is used to verify whether the PRU has PRU functionality;

[0098] The first verification result is used to indicate whether the PRU has PRU functionality;

[0099] The second verification result is used to indicate whether the PRU belongs to a fixed PRU;

[0100] The first instruction message is used to indicate that the association between the PRU and the PRU's service network element has been successfully established;

[0101] Association identifier, used to identify the service network element of PRU, and / or the association relationship between PRUs and their service network elements;

[0102] Location of PRU.

[0103] In this embodiment of the present disclosure, the first network element provides the PRU information to the second network element through a first response message, which helps the second network element to identify the PRU in the terminal list based on the PRU information.

[0104] According to a second aspect of the embodiments of this disclosure, a communication method is provided, executed by a second network element, the method comprising:

[0105] Send a first request message to the first network element. The first request message is used to request information about terminals in the area and / or information about PRUs in the area from the first network element.

[0106] The system receives a first response message sent by a first network element. The first response message is used to provide the second network element with information about terminals within the area and / or information about PRUs within the area.

[0107] In this embodiment of the disclosure, the second network element requests information about terminals and / or PRUs within the area from the first network element by sending a first request message to the first network element, and then receives a first response message sent by the first network element, thereby obtaining information about terminals and / or PRUs within the area, which helps the second network element identify the PRU based on the terminal information and / or PRU information.

[0108] In conjunction with some embodiments of the second aspect, in some embodiments, the first request message is used to request at least one of the following from the first network element:

[0109] Information on PRUs within the region;

[0110] Indication of PRU within the area;

[0111] Identification of terminals within the area;

[0112] Location capability information of terminals within the area.

[0113] In this embodiment of the disclosure, the second network element, by sending a first request message to the first network element, instructs the second network element to request at least one of the following from the first network element: PRU information within the area, indication of PRUs within the area, identifier of terminals within the area, and positioning capability information of terminals within the area. This helps the first network element to provide the second network element with corresponding information more flexibly based on the information requested by the second network element.

[0114] In conjunction with some embodiments of the second aspect, in some embodiments, the method further includes:

[0115] Receive the first notification message sent by the first network element;

[0116] The first notification message is used to request the establishment of an association between the PRU and the second network element, where the second network element is the serving network element selected by the first network element.

[0117] In this embodiment of the disclosure, the second network element receives a first notification message sent by the first network element, thereby establishing an association between the PRU and the second network element according to the instructions of the first notification message.

[0118] In conjunction with some embodiments of the second aspect, in some embodiments, the method further includes:

[0119] If the association between the PRU and the second network element is successfully established, a second notification message is sent to the first network element. The second notification message includes at least one of the following: first indication information, the location of the PRU, the association identifier, and the identifier of the PRU. The first indication information is used to indicate that the association between the PRU and the second network element has been successfully established, and the association identifier is used to identify the second network element and / or the association.

[0120] In this embodiment of the disclosure, when the association between the PRU and the service network element is successfully established, the second network element provides the first network element with at least one of the following information through a second notification message: first instruction information, the location of the PRU, the association identifier, and the identifier of the PRU. This helps the first network element to provide the above-mentioned at least one piece of information to the second network element.

[0121] In conjunction with some embodiments of the second aspect, in some embodiments, the first response message includes at least one of the following:

[0122] Identification of terminals within the area;

[0123] Location capability information of terminals within the area;

[0124] Terminal subscription information;

[0125] Information on PRUs within the region;

[0126] The second instruction information is used to indicate the PRU within the area.

[0127] In this embodiment of the disclosure, the second network element can obtain the above information through the first response message, which helps the second network element to identify the PRU in the terminal list based on the above information.

[0128] In conjunction with some embodiments of the second aspect, in some embodiments, the PRU information includes at least one of the following:

[0129] The PRU identifier;

[0130] The subscription information of the PRU is used to verify whether the PRU has PRU functionality;

[0131] The first verification result is used to indicate whether the PRU has PRU functionality;

[0132] The second verification result is used to indicate whether the PRU belongs to a fixed PRU;

[0133] The first instruction message is used to indicate that the association between the PRU and the PRU's service network element has been successfully established;

[0134] Association identifier, used to identify the service network element of PRU, and / or the association relationship between PRUs and their service network elements;

[0135] Location of PRU.

[0136] In this embodiment of the disclosure, the second network element obtains the PRU information through the first response message, which helps the second network element identify the PRU in the terminal list based on the PRU information.

[0137] According to a third aspect of the embodiments of this disclosure, a communication method is proposed, executed by a third network element, the method comprising:

[0138] Receive the first notification message sent by the first network element;

[0139] The first notification message is used to request the establishment of an association between the PRU and the third network element, where the third network element is the serving network element selected by the first network element.

[0140] In this embodiment of the disclosure, the third network element receives a first notification message sent by the first network element, thereby enabling it to establish an association between the PRU and the third network element according to the instructions of the first notification message.

[0141] In conjunction with some embodiments of the third aspect, in some embodiments, the method further includes:

[0142] If the association between the PRU and the third network element is successfully established, a second notification message is sent to the first network element. The second notification message includes at least one of the following: first indication information, the location of the PRU, the association identifier, and the identifier of the PRU. The first indication information is used to indicate that the association between the PRU and the third network element has been successfully established, and the association identifier is used to identify the third network element and / or the association.

[0143] In this embodiment of the disclosure, when the association between the PRU and the service network element is successfully established, the third network element provides the first network element with at least one of the following information through the second notification message: first instruction information, the location of the PRU, the association identifier, and the identifier of the PRU. This helps the first network element to provide the above-mentioned at least one piece of information to the second network element.

[0144] According to a fourth aspect of the embodiments of this disclosure, a communication method is provided, executed by a fourth network element, the method comprising:

[0145] Receive a second request message sent by the first network element, the second request message being used to request subscription information for at least one PRU;

[0146] Send a second response message to the first network element. The second response message includes subscription information of at least one PRU. The subscription information of at least one PRU is used to verify whether at least one PRU has the function of a PRU and / or whether at least one PRU belongs to a fixed PRU.

[0147] In this embodiment of the disclosure, the fourth network element can learn from the first network element's request for at least one PRU through the second request message, and thus can provide the first network element with the subscription information of at least one PRU through the second response message.

[0148] According to a fifth aspect of the embodiments of this disclosure, a first network element is proposed, comprising:

[0149] The transceiver module is used to receive a first request message sent by the second network element. The first request message is used to request information of terminals in the area and / or information of PRUs in the area from the first network element.

[0150] The transceiver module is also used to send a first response message to the second network element. The first response message is used to provide the second network element with information about terminals within the area and / or information about PRUs within the area.

[0151] According to a sixth aspect of the embodiments of this disclosure, a second network element is proposed, comprising:

[0152] The transceiver module is used to send a first request message to the first network element. The first request message is used to request information of terminals within the area and / or information of PRUs within the area from the first network element.

[0153] The transceiver module is also used to receive a first response message sent by the first network element. The first response message is used to provide the second network element with information about terminals within the area and / or information about PRUs within the area.

[0154] According to a seventh aspect of the embodiments of this disclosure, a third network element is proposed, comprising:

[0155] The transceiver module is used to receive the first notification message sent by the first network element;

[0156] The first notification message is used to request the establishment of an association between the PRU and the third network element, where the third network element is the serving network element selected by the first network element.

[0157] According to an eighth aspect of the embodiments of this disclosure, a fourth network element is proposed, comprising:

[0158] The transceiver module is used to receive a second request message sent by the first network element. The second request message is used to request subscription information of at least one PRU.

[0159] The transceiver module is also used to send a second response message to the first network element. The second response message includes subscription information of at least one PRU. The subscription information of at least one PRU is used to verify whether at least one PRU has the function of a PRU and / or whether at least one PRU belongs to a fixed PRU.

[0160] According to a ninth aspect of the present disclosure, a communication system is provided, comprising: a first network element, a second network element, a third network element, and a fourth network element;

[0161] The first network element is configured to implement the method described in the optional implementation of the first aspect; the second network element is configured to implement the method described in the optional implementation of the second aspect; the third network element is configured to implement the method described in the optional implementation of the third aspect; and the fourth network element is configured to implement the method described in the optional implementation of the fourth aspect.

[0162] According to a tenth aspect of the present disclosure, a storage medium is provided that stores instructions, which, when executed on a communication device, cause the communication device to perform a method as described in an optional implementation of the first aspect, or a method described in an optional implementation of the second aspect, or a method described in an optional implementation of the third aspect, or a method described in an optional implementation of the fourth aspect.

[0163] According to an eleventh aspect of the present disclosure, a program product is provided, including a program and / or instructions, which, when executed by a communication device, implement the method described in the optional implementation of the first aspect, or the method described in the optional implementation of the second aspect, or the method described in the optional implementation of the third aspect, or the method described in the optional implementation of the fourth aspect.

[0164] It is understood that the aforementioned first network element, second network element, third network element, fourth network element, communication equipment, storage medium, program product, computer program, and chip are all used to execute the method proposed in the embodiments of this disclosure. Therefore, the beneficial effects that can be achieved can be referred to the beneficial effects in the corresponding methods, and will not be repeated here.

[0165] This disclosure provides communication methods, devices, systems, storage media, and program products.

[0166] In some embodiments, the terms communication method, request method, information request method, transmission method, and information processing method can be used interchangeably; the terms communication equipment, request equipment, information request equipment, transmission equipment, and information processing equipment can be used interchangeably; and the terms communication system, request system, information request system, transmission system, and information processing system can be used interchangeably.

[0167] This disclosure is not exhaustive, but merely illustrative of some embodiments, and is not intended to limit the scope of protection of this disclosure. Unless otherwise specified, each step in a particular 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 particular embodiment can also be implemented as an independent embodiment, and the order of the steps in a particular embodiment can be arbitrarily interchanged. Furthermore, the optional implementation methods in a particular embodiment can be arbitrarily combined; moreover, the embodiments can be arbitrarily combined, for example, some or all steps of different embodiments can be arbitrarily combined, and a particular embodiment can be arbitrarily combined with the optional implementation methods of other embodiments. In all embodiments of this disclosure, unless otherwise specified or logically conflicting, the terminology and / or descriptions between the embodiments are consistent and can be mutually referenced. Technical features in different embodiments can be combined to form new embodiments based on their inherent logical relationships.

[0168] The terminology used in the embodiments of this disclosure is for the purpose of describing particular embodiments only and is not intended to limit the scope of this disclosure.

[0169] In this embodiment of the disclosure, unless otherwise stated, elements expressed in the singular form, such as "a," "an," "the," "the," "the," "the," "the," "the," "this," etc., can mean "one and only one," or "one or more," "at least one," etc. For example, when using articles such as "a," "an," "the," etc. in translation, the noun following the article can be understood as either a singular expression or a plural expression.

[0170] In the embodiments disclosed herein, "multiple" refers to two or more.

[0171] In some embodiments, the terms “at least one of A or B, at least one of A and B”, “one or more”, “a plurality of”, “multiple”, etc., may be used interchangeably.

[0172] In some embodiments, the notation "at least one of A and B", "A and / or B", "A in one case, B in another", "in response to one case A, in response to another case B", etc., may include the following technical solutions depending on the situation: in some embodiments, A (execute A regardless of whether there is a branch B); in some embodiments, B (execute B regardless of whether there is a branch A); in some embodiments, execution is selected from A and B (A and B are selectively executed); in some embodiments, both A and B are executed. The same applies when there are more branches such as A, B, C, etc.

[0173] In some embodiments, the notation "A or B" may include the following technical solutions, depending on the situation: in some embodiments, A (execute A regardless of whether a branch B exists); in some embodiments, B (execute B regardless of whether a branch A exists); in some embodiments, execution is selected from A and B (A and B are selectively executed). The same applies when there are more branches such as A, B, and C.

[0174] The prefixes "first," "second," etc., used in the embodiments of this disclosure are merely for distinguishing different descriptive objects and do not impose restrictions on the position, order, priority, quantity, or content of the descriptive objects. The description of the descriptive objects is found in the claims or the context of the embodiments, and the use of prefixes should not constitute unnecessary restrictions. For example, if the descriptive object is a "field," the ordinal numbers preceding "field" in "first field" and "second field" do not restrict the position or order of the "fields." "First" and "second" do not restrict whether the "fields" they modify are in the same message, nor do they restrict the order of "first field" and "second field." Similarly, if the descriptive object is a "level," the ordinal numbers preceding "level" in "first level" and "second level" do not restrict the priority between "levels." Furthermore, the number of descriptive objects is not limited by ordinal numbers and can be one or more. For example, in "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 object being described is "device", then "first device" and "second device" can be the same device or different devices, and their types can be the same or different. Similarly, if the object being described is "information", then "first information" and "second information" can be the same information or different information, and their content can be the same or different.

[0175] In some embodiments, “including A,” “containing A,” “for indicating A,” and “carrying A” can be interpreted as directly carrying A or indirectly indicating A.

[0176] In some embodiments, terms such as “in response to…”, “in response to determining…”, “in the case of…”, “when…”, “when…”, “if…”, etc. can be used interchangeably. These descriptions all refer to the device making a corresponding action under certain objective circumstances. They do not necessarily limit the time, nor do they require the device to make a judgment action when implementing it, nor do they mean that there must be other limitations.

[0177] In some embodiments, the terms “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 lower than,” and “above” can be used interchangeably, as can the terms “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”.

[0178] In some embodiments, devices, etc., may be interpreted as physical or virtual, and their names are not limited to those described in the embodiments. Terms such as “device,” “equipment,” “circuit,” “network element,” “network function,” “network device,” “function,” “node,” “unit,” “section,” “system,” “network,” “chip,” “chip system,” “entity,” and “subject” are interchangeable.

[0179] In some embodiments, "network" can be interpreted as devices included in a network (e.g., access network devices, core network devices, etc.).

[0180] 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," and "bandwidth part (BWP)" can be used interchangeably.

[0181] 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 subscriberstation, access terminal, mobile terminal, wireless terminal, remote terminal, handset, user agent, mobile client, and client can be used interchangeably.

[0182] In some embodiments, access network devices, core network devices, or network devices can be replaced by terminals. For example, embodiments of this disclosure can also be applied to structures where communication between access network devices, core network devices, or network devices and terminals is replaced by communication between multiple terminals (e.g., device-to-device (D2D), vehicle-to-everything (V2X), etc.). In this case, the structure can also be configured such that the terminal has all or part of the functions of the access network device. Furthermore, terms such as "uplink" and "downlink" can be replaced with terms corresponding to communication between terminals (e.g., "sidelink"). For example, uplink channel, downlink channel, etc., can be replaced with sidelink channel, and uplink link, downlink, etc., can be replaced with sidelink link.

[0183] 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, core network device, or network device may also be configured to have all or some of the functions of the terminal.

[0184] In some embodiments, the acquisition of data, information, etc., may comply with the laws and regulations of the country where the location is situated.

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

[0186] Furthermore, each element, each row, or each column in the table of this disclosure can be implemented as an independent embodiment, and any combination of any element, any row, or any column can also be implemented as an independent embodiment.

[0187] Figure 1a This is a schematic diagram of the architecture of a communication system according to embodiments of this disclosure. Figure 1a As shown, the communication system 100 includes a terminal 101, an access network device 102, and a core network device 103.

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

[0189] In some embodiments, the access network device 102 may be a node or device that connects a terminal to a wireless network. The access network device may include at least one of the following in a 5G communication system: an evolved Node B (eNB), a next-generation eNB (ng-eNB), a next-generation Node B (gNB), a node B (NB), a home node B (HNB), a home evolved node B (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 RAN, a cloud RAN, a base station in other communication systems, and an access node in a Wi-Fi system, but is not limited thereto.

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

[0191] In some embodiments, the access network device may be composed of a central unit (CU) and a distributed unit (DU). The CU may also be called a control unit. The CU-DU structure can separate the protocol layer of the access network device. Some of the protocol layer functions are centrally controlled by the CU, while the remaining part or all of the protocol layer functions are distributed in the DU and centrally controlled by the CU. However, this is not the only possibility.

[0192] In some embodiments, the core network device 103 may be a single device, including a first network element 1031, a second network element 1032, a third network element 1033, a fourth network element 1034, etc., or it may be multiple devices or a group of devices, each including all or some of the first network element 1031, the second network element 1032, the third network element 1033, the fourth network element 1034, etc. Network elements may be virtual or physical. The core network may include, for example, at least one of the Evolved Packet Core (EPC), the 5G Core Network (5GCN), and the Next Generation Core (NGC).

[0193] It is understood that the communication system described in this disclosure is for the purpose of more clearly illustrating the technical solutions of this disclosure, and does not constitute a limitation on the technical solutions proposed in this disclosure. As those skilled in the art will know, with the evolution of system architecture and the emergence of new business scenarios, the technical solutions proposed in this disclosure are also applicable to similar technical problems.

[0194] The following embodiments of this disclosure can be applied to Figure 1a The communication system 100 shown, or a part thereof, but not limited to it. Figure 1a The entities shown are illustrative; a communication system may include... Figure 1a All or part of the main body, or may include Figure 1a Other entities besides the main body, the number and form of each entity are arbitrary, each entity can be physical or virtual, the connection relationship between the entities is an example, the entities can be unconnected or connected, and the connection can be in any way, it can be a direct connection or an indirect connection, it can be a wired connection or a wireless connection.

[0195] The embodiments disclosed herein 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), Futuregeneration radio access (FX), Global System for Mobile communications (GSM), CDMA2000, Ultra Mobile Broadband (UMB), IEEE 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), and IEEE 802.20, Ultra-Wideband (UWB), Bluetooth (a 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, systems utilizing other communication methods, and next-generation systems built upon them, etc. Furthermore, multiple systems can be combined (e.g., a combination of LTE or LTE-A with 5G).

[0196] A PRU is a dedicated device or functional entity that can assist in locating other terminals or network devices by providing positioning reference signals or reporting its own location.

[0197] In some embodiments, it is necessary to associate the PRU with a device that has location association capabilities, such as an LMF network element.

[0198] Figure 1b This is an exemplary interactive diagram illustrating the PRU association process provided in this embodiment of the disclosure. The PRU association process can be the initial PRU association between the PRU and the serving LMF network element, which may occur when the PRU first accesses the Home Public Land Mobile Network (HPLMN). The PRU association process can also be used to update the PRU association, such as notifying the serving LMF network element of the PRU's continued availability or notifying the serving LMF network element of changes in the PRU's location capabilities.

[0199] A PRU can perform a PRU association process in an HPLMN, provided that the PRU is already registered in the HPLMN. For the initial PRU association, the PRU can carry a route ID to indicate the serving LMF element; for subsequent PRU association update processes, the route ID is the route ID that the PRU has already obtained from the serving LMF element during the previous PRU association process.

[0200] In some embodiments, the routing ID and the association ID are different representations of the same ID. For example, the association ID can be used in service operations between Access and Mobility Management Function (AMF) network elements and LMF network elements, while the routing ID can be used in non-access stratum (NAS) messages sent between PRU and AMF network elements through the N1 reference point.

[0201] In some embodiments, routing IDs and association IDs have a mapping relationship. For example, association IDs can be used in service operations between Access and Mobility Management Function (AMF) network elements and LMF network elements. An AMF network element can map a routing ID to an association ID or an association ID to a routing ID. Routing IDs can be used in non-access strand (NAS) messages sent between PRU and AMF network elements through the N1 reference point.

[0202] like Figure 1b As shown, it includes the following steps:

[0203] Step S1201: Trigger a service request.

[0204] In some embodiments, the PRU can be a terminal device (e.g., a UE), so the service request can be called a UE-triggered service request. Initially, the connected management (CM) state of the PRU can be determined. If the PRU is in the connected management idle (CM-IDLE) state, a service request needs to be triggered to make the PRU enter the connected management connected (CM-CONNECTED) state from the CM-IDLE state.

[0205] In step S1202, the PRU sends an uplink non-access stratum transport (UL NAS TRANSPORT) message to the AMF network element. The UL NAS TRANSPORT message includes a PRU association request and a routing ID.

[0206] The PRU sends a supplementary service PRU association request to the AMF network element in the UL NAS TRANSPORT message. The PRU association request is included in the UL NAS TRANSPORT message at the NAS level.

[0207] A PRU association request may include at least one of the following pieces of information:

[0208] The reasons for PRU association can be, for example, the initial PRU association, or the PRU association update (e.g., changes in PRU location, changes in capabilities, etc., which necessitate PRU association).

[0209] The positioning capabilities of the PRU can be, for example, the positioning technology supported by the PRU;

[0210] The location of the PRU can be included in the PRU association request if the current location of the PRU is known.

[0211] PRU ON / OFF state.

[0212] The UL NAS TRANSPORT message may also include a route ID, which can be a pre-configured initial associated route ID or a route ID received during the previous PRU association process.

[0213] In step S1203, the AMF network element verifies the PRU and obtains the verification result.

[0214] On the one hand, AMF network elements can use the PRU's subscription information to verify whether the sender of the PRU association request is a PRU, that is, whether the PRU is a legally subscribed PRU; on the other hand, AMF network elements can verify whether a PRU can work as a fixed PRU based on the PRU's subscription information or local policies, that is, whether the PRU is a fixed PRU.

[0215] The subscription information for PRUs comes from Unified Data Management (UDM) network elements, and AMF network elements can proactively request PRU subscription information from UDM network elements. Fixed PRUs refer to PRUs with fixed locations.

[0216] In step S1204, the AMF network element selects the serving LMF network element and sends a notification message (e.g., Namf_Communication_N1MessageNotify) to the serving LMF network element.

[0217] When the AMF network element verifies that the sender of the PRU association request is a PRU, the AMF network element selects a serving LMF network element. In some embodiments, the AMF network element may select a serving LMF network element based on a preset protocol or based on a route ID.

[0218] After the AMF network element selects the serving LMF network element, the AMF network element uses the Namf_Communication_N1MessageNotify service operation to send the PRU association request to the serving LMF network element. Namf_Communication_N1MessageNotify may also include the PRU's Subscriber Permanent Identifier (SUPI), Tracking Area ID (TAI), cell ID, and indication information. This indication information is used to indicate the PRU's verification result, such as whether the sender of the PRU association request is a PRU and whether the PRU is a fixed PRU.

[0219] Steps S1205-S1206 describe the situation where the serving LMF network element accepts PRU association.

[0220] Step S1205: The serving LMF network element sends a Namf_Communication_N1N2MessageTransfer message to the AMF network element. The Namf_Communication_N1N2MessageTransfer message includes a PRU association accept message and an association ID.

[0221] If the serving LMF network element accepts the PRU association, it uses the Namf_Communication_N1N2MessageTransfer service operation to return a PRU association acceptance message to the AMF network element as a supplementary service message, along with an association ID. The association ID is assigned by the serving LMF network element and is used to identify the serving LMF network element and the optional PRU.

[0222] The PRU association acceptance message can also instruct the PRU and the serving LMF network element on the conditions for performing PRU association updates. These conditions may include, for example, periodic PRU association update timers, PRU location changes, PRU TAI changes, serving AMF network element changes, PRU on / off status changes, and so on. For PRUs in the off state, the PRU information is stored in the serving LMF network element.

[0223] In step S1206, the AMF network element sends a downlink non-access stratum transport (DL NAS TRANSPORT) message to the PRU. The DL NAS TRANSPORT message includes the PRU associated accept message and the routing ID.

[0224] In some embodiments, the route ID is equivalent to an association ID, and the PRU stores this route ID for further PRU association updates with serving LMF network elements. If the PRU previously stored a route ID, the route ID in the DL NAS TRANSPORT can overwrite the route ID previously stored in the PRU.

[0225] Steps S1207-S1208 represent the situation where the serving LMF network element refuses PRU association.

[0226] In step S1207, the serving LMF network element sends a Namf_Communication_N1N2MessageTransfer message to the AMF network element. The Namf_Communication_N1N2MessageTransfer message includes a PRU association reject message and a new routing ID.

[0227] If the serving LMF element rejects the PRU association, the serving LMF element uses the Namf_Communication_N1N2MessageTransfer service operation to return a PRU association rejection message to the AMF element, which may include a new route ID for attempting to establish a PRU association with the new LMF element.

[0228] In step S1208, the AMF network element sends a DL NAS TRANSPORT to the PRU. The DL NAS TRANSPORT message includes a PRU association rejection message and a new routing ID.

[0229] Step S1209: The LMF network element performs a location verification operation.

[0230] If the PRU is successfully associated with the serving LMF element, the serving LMF element can verify the PRU's location and perform a positioning operation to obtain a more precise location for the PRU. The serving LMF element can also store information about the received PRU, such as the PRU's positioning capabilities, location, and status. If the PRU association update only involves a change in the PRU's status, the serving LMF element can consider the previously verified PRU location to be valid.

[0231] Step S1210: The serving LMF network element sends a request message (Nnrf_NFManagement_NFUpdateRequest) to the NRF network element.

[0232] If the PRU is successfully associated with the serving LMF network element, and conditions 1 and 2 are met, the serving LMF can choose to initiate an Nnrf_NFManagement_NFUpdate request service operation to the NRF network element. This message includes an indication of the existence of the PRU associated with the TAI. The serving LMF network element also instructs the NRF network element to remove the PRU associated with the TAI when there are no longer any PRUs associated with this TAI in the serving LMF. Condition 1: This association process is an initial PRU association, or the process is a PRU association update and the PRU information has been changed; Condition 2: The PRU is a fixed PRU. Through this process, the serving LMF network element synchronizes the PRU information with the NRF network element, so other network elements can also learn about the existence of this PRU and the serving LMF network element of this PRU through the NRF network element.

[0233] Step S1211: The NRF network element sends a response message (Nnrf_NFManagement_NFUpdateResponse) to the serving LMF network element.

[0234] Step S1212: The PRU re-initiates the PRU association process.

[0235] If a serving LMF element rejects PRU association, and a new route ID is available, the PRU can initiate a PRU association process with other LMF elements based on the new route ID.

[0236] The PRU association process was described in the above embodiments. The data collection process will be described below with reference to the accompanying drawings.

[0237] LMF network elements are network elements with positioning management functions. By collecting relevant data, LMF network elements can train artificial intelligence (AI) models / machine learning (ML) models (hereinafter referred to as models) or monitor the performance of the models. Among them, the model can realize the positioning of terminal devices.

[0238] Figure 1c This is a flowchart of data collection by the LMF network element provided in this embodiment of the disclosure, such as... Figure 1c As shown, it includes the following steps:

[0239] In step S1301, the LMF network element determines that it needs to collect data from terminals in the region of interest.

[0240] Data collection by an LMF (Local Modem) network element refers to the collection of measurement data and tag data from terminals within the region of interest. This measurement and tag data can also be considered terminal information. Terminal measurement data may include, for example, the terminal's location, type, and the power of its transmitted location reference signal. Terminal tag data is real-world data, such as the terminal's actual location.

[0241] Terminals include those that can function as PRUs (Programmers for Utility Units) and those that cannot. Terminals that can function as PRUs can also be called PRUs. For PRUs, the LMF (Local Multi-Function) network element needs to collect PRU information.

[0242] The process of an LMF (Local Modem) network element determining that data collection is necessary can be proactively triggered by the LMF network element. For example, when an LMF network element needs to train an AI / ML model or detects poor performance of the AI / ML model, it needs to collect data to train the AI / ML model based on the collected data.

[0243] The process by which an LMF network element determines that data collection is necessary can be triggered by an NWDAF network element. For example, the NWDAF network element sends a request message to the LMF network element, which is used to request the initiation of data collection.

[0244] In some embodiments, the LMF network element may know the SUPIs of terminals in the region of interest, for example, when training an AI / ML model using a PRU, these PRUs are associated with the LMF network element performing data collection. The LMF network element may choose to initiate an NF discovery (Nnrf_NFDiscovery) request service operation to the NRF network element to identify the LMF network element of the PRU associated with a series of TAIs. The LMF network element may send an Nlmf_Location_MeasurementData request service operation to one or more other LMF network elements serving PRUs to obtain data collection and known PRU locations, then the LMF network element executes step S1307.

[0245] In step S1302, the LMF network element sends a request message to the NRF network element. The request message is used to request the service AMF network element to find the region of interest.

[0246] In step S1303, the NRF network element sends a response message to the LMF network element. The response message is used to indicate the serving AMF network element of the region of interest.

[0247] In some embodiments, the LMF network element may not know the SUPI of the terminal in the region of interest. The LMF network element may request the NRF network element to find the serving AMF network element in the region of interest and obtain the SUPI list of the terminal from the AMF network element.

[0248] In step S1304, the LMF network element sends a request message to the AMF network element. The request message is used to request the SUPI list of terminals in the region of interest.

[0249] This request message, also known as a subscription request message, is used to subscribe to an event. The object of this event can be any terminal, and the event can be a terminal entering or leaving the area of ​​interest. Through this request message, the LMF network element requests the SUPI list of terminals in the area of ​​interest from the AMF network element.

[0250] In step S1305, the AMF network element sends a response message to the LMF network element, which includes a list of SUPIs of terminals in the region of interest.

[0251] After receiving the request message, the AMF network element retrieves the SUPI list of terminals in the region of interest and then sends a response message to the LMF network element; correspondingly, the LMF network element receives the response message and obtains the SUPI list of terminals from the response message.

[0252] Step S1306: The LMF network element checks whether the terminals in the SUPI list agree to data collection.

[0253] The LMF network element can request data collection from the UDM network element to check whether the terminals in the SUPI list agree to data collection. The collected data is used to train AI / ML models. For any terminal in the SUPI list, if the terminal agrees to data collection, step S1307 is executed; if the terminal does not agree to data collection, the LMF network element does not execute step S1307 for the terminal UE, and the terminal will not participate in data collection, and its data will not be used to train AI / ML models.

[0254] Step S1307: If the terminal agrees to data collection, the LMF network element requests the terminal's data volume from the terminal.

[0255] In some embodiments, the terminal can send its measurement data to the LMF network element via NG-RAN pass-through; NG-RAN can also obtain the terminal's measurement data through interaction with the terminal, and then send the terminal's measurement data to the LMF network element. The LMF network element obtains the tag data corresponding to the measurement data from the terminal.

[0256] After receiving measurement data and label data, LMF network elements can train AI / ML models based on the measurement data and label data.

[0257] During the process where the LMF network element needs to collect terminal data for AI / ML model training, the LMF network element receives a SUPI list of regions of interest sent by the AMF network element. The SUPI list includes the IDs of terminals that can be used as PRUs (hereinafter referred to as PRUs) and the IDs of terminals that cannot be used as PRUs. The data collection operation performed by the LMF network element differs for these two types of devices. Therefore, the LMF needs to identify the PRUs in the SUPI list.

[0258] For terminals that cannot act as PRUs (Programmers, Utility Modelers), the LMF (Local Management Function) network element needs to perform a user consent check before collecting data from the terminal. This check determines whether the terminal agrees to the LMF network element collecting its data for AI / ML model training. Only if the terminal agrees to this data collection can the LMF network element collect it.

[0259] For PRUs, LMF network elements do not need to determine whether the PRU agrees to the collection of the PRU's data by the LMF network element. The LMF network element can directly collect the PRU's data for AI / ML model training.

[0260] On the other hand, for terminals that cannot act as PRUs, LMF network elements need to collect the terminal's data from the terminal through AMF network elements; for PRUs, LMF network elements need to collect the PRU's data through the PRU's serving network element.

[0261] In other words, the process of requiring user consent checks differs for the two different devices, and the methods by which LMF network elements acquire data from these two different devices also differ. Currently, after obtaining the SUPI list of the region of interest, the LMF network element cannot determine which PRUs are in the SUPI list, which may lead to data collection failures.

[0262] Based on this, the present disclosure provides a communication method in which, when a second network element requests a list of SUPIs for a region of interest, a first network element also provides information on terminals within the region and / or information on PRUs within the region, enabling the second network element to determine the PRUs in the region based on the information provided by the first network element, which helps the second network element to collect data.

[0263] Figure 2a This is an exemplary interaction diagram of the communication method provided in this disclosure embodiment. Please refer to [link / reference]. Figure 2a The method includes:

[0264] In step S2101, the PRU sends a PRU association request message to the first network element.

[0265] In some embodiments, the first network element may be, for example, an AMF network element.

[0266] In some embodiments, the PRU can be a terminal (e.g., a UE), and the PRU executes a service request triggered by the UE. If the PRU is in CM-IDLE state, a service request needs to be triggered to allow the PRU to transition from CM-IDLE state to CM-CONNECTED state.

[0267] A PRU can request to establish an association with a serving network element by sending a PRU association request message to the first network element.

[0268] In some embodiments, the PRU association request message can be carried in a UL NAS TRANSPORT. For example, when the PRU sends a UL NAS TRANSPORT message to the first network element, the UL NAS TRANSPORT message includes:

[0269] Payload container information indicates whether a UL NAS TRANSPORT message is a PRU-related message, i.e., whether the payload container is a PRU-related payload container.

[0270] Additional information, namely the route ID, which can be the pre-configured initial associated route ID or the route ID received during the previous PRU association process;

[0271] The payload container contains the PRU-related request messages.

[0272] The payload container type indicates that it is a location service message container.

[0273] Among them, the load container (i.e., the PRU association request message) in the UL NAS TRANSPORT message is unknown to the first network element, while other information is known to the first network element.

[0274] The PRU association request message may include at least one of the following pieces of information:

[0275] The reasons for PRU association can be, for example, the initial PRU association, or the PRU association update (e.g., changes in PRU location, changes in capabilities, etc., which necessitate PRU association).

[0276] The positioning capabilities of the PRU can be, for example, the positioning technology supported by the PRU;

[0277] The location of the PRU can be included in the PRU association request if the current location of the PRU is known.

[0278] The on / off state of PRU.

[0279] In step S2102, upon receiving a PRU association request message sent by a PRU, the first network element verifies the PRU based on the PRU's subscription information to obtain a first verification result and / or a second verification result.

[0280] For example, after receiving the UL NAS TRANSPORT message, the first network element can obtain the load container information and determine whether it has received the PRU association request message based on the load container information. For instance, if the PRU bit of the load container information IE is 1 (indicating that it is a load container associated with a PRU), it can be determined that a PRU association request message has been received.

[0281] When the first network element receives a PRU association request message, it can verify the PRU based on its subscription information to obtain a first verification result. This process can also be expressed as the first network element using the PRU's subscription information to verify whether the sender of the PRU association request is a PRU (i.e., the first verification result), that is, whether the PRU is a legitimately subscribed PRU. The first verification result indicates whether the PRU possesses PRU functionality and also whether the sender of the PRU association request message is a PRU, i.e., whether the current PRU can function as a PRU.

[0282] The PRU subscription information can be stored locally on the first network element or it can come from the UDM network element. The first network element can actively request the PRU subscription information from the UDM network element.

[0283] The first network element can also verify whether a PRU can function as a fixed PRU based on its subscription information or local policies, i.e., whether the PRU is a fixed PRU, which refers to a PRU with a fixed location. The second verification result is used to indicate whether the PRU belongs to the fixed PRU category.

[0284] In step S2103, the first network element stores at least one of the following information: the PRU identifier, the PRU subscription information, the first verification result, and the second verification result.

[0285] After the first network element performs verification on the PRU, it stores the PRU's identifier, PRU subscription information, first verification result, and second verification result. This information is stored locally as part of the PRU's information.

[0286] In step S2104, if the first verification result indicates that the PRU has PRU functionality, the first network element sends a first notification message to the third network element. The first notification message is used to request the establishment of an association between the PRU and the third network element.

[0287] In some embodiments, the third network element can be a network element with positioning management function, such as an LMF network element, or a sensing function (SF) network element.

[0288] When the sender of the PRU association request message verified by the first network element is a PRU (i.e., the first verification result indicates that the PRU has PRU functionality), the first network element selects the serving network element for that PRU. In some embodiments, the first network element may select the serving network element based on a preset protocol or based on a routing ID. The third network element is the serving network element selected by the first network element.

[0289] After the first network element selects the third network element as the serving network element, the first network element sends a first notification message to the third network element. The first notification message is used to request the establishment of an association between the PRU and the third network element.

[0290] In some embodiments, the first notification message may be, for example, a Namf_Communication_N1MessageNotify message.

[0291] In some embodiments, the first notification message may include the PRU's SubscriberPermanent Identifier (SUPI), Tracking Area ID (TAI), Cell ID, First Verification Result, Second Verification Result, etc.

[0292] If the serving network element accepts the PRU association, it can use the Namf_Communication_N1N2MessageTransfer service operation to return a PRU association acceptance message to the first network element as a supplementary service message, along with an association ID. The association ID is assigned by the serving network element and is used to identify the serving network element and the optional PRU.

[0293] In some embodiments, the PRU association acceptance message can also instruct the PRU and the serving network element to perform PRU association updates under certain conditions. These conditions may include, for example, a periodic PRU association update timer, changes in PRU location, changes in PRU TAI, changes in the serving network element, changes in the PRU's on / off state, and so on. For PRUs in a closed state, the PRU information is stored in the serving network element.

[0294] In some embodiments, the first network element may send a downlink non-access stratum transport (DL NAS TRANSPORT) message to the PRU. The DL NAS TRANSPORT message includes a PRU associated accept message and a routing ID.

[0295] In some embodiments, the route ID is equivalent to an association ID, and the PRU stores this route ID for further PRU association updates with serving network elements. If the PRU previously stored a route ID, the route ID in the DL NAS TRANSPORT can overwrite the route ID previously stored in the PRU.

[0296] In step S2105, after the third network element successfully associates with the PRU, the third network element sends a second notification message to the first network element. The second notification message includes at least one of the following: first instruction information, the location of the PRU, the association identifier, and the identifier of the PRU.

[0297] The first indication information is used to indicate that the association between the PRU and the third network element has been successfully established. The third network element sends a second notification message to the first network element, which may include the first indication information. Correspondingly, the first network element receives the second notification message sent by the third network element, obtains the first indication information from the second notification message, and can know that the association between the PRU and the third network element has been successfully established based on the first indication information.

[0298] The location of a PRU can include, for example, the PRU's coordinates, cell ID, TAI, etc. In some embodiments, the PRU's location can also be represented by its latitude and longitude coordinates and the region ID (different regions can be pre-divided and identified by different IDs). In some embodiments, the PRU's location can also be characterized by the phase position between the PRU and a reference point, such as a terminal, a base station, a fixed building, etc.

[0299] The third network element sends a second notification message to the first network element, which may include the location of the PRU; correspondingly, the first network element receives the second notification message sent by the third network element and learns the location of the PRU from the second notification message.

[0300] In some embodiments, the second notification message may be, for example, an Nlmf_Location_PRUNotify message.

[0301] In some embodiments, the association identifier can be used to identify the association between a third network element and / or a PRU. The third network element is the network element associated with the PRU, or a network element that has established an association with the PRU. In some embodiments, the PRU can establish an association with the third network element by initiating an initial PRU association process or by initiating a PRU association update process.

[0302] The third network element sends a second notification message to the first network element. The second notification message may include an association identifier. Correspondingly, the first network element receives the second notification message sent by the third network element, obtains the association identifier from the second notification message, and can know the third network element associated with the PRU and / or the association relationship established between the PRU and the third network element based on the association identifier.

[0303] In some embodiments, the association identifier can be a session or service identifier used to identify a session or service. The association identifier can also be a correlation ID, also known as an analytics ID, which can be used to identify sessions used for AI, sessions used for location, sessions used for sensing, etc. For example, an analytics ID is used to identify sessions used for AI; an association identifier is used to identify sessions used for location / sensing.

[0304] The identifier of a PRU is used to identify that PRU. This identifier can be temporary or permanent. For example, the identifier of a PRU can be the PRU's SUPI, or it can be the PRU's SubscriptionConcealed Identifier (SUCI).

[0305] Step S2106, the first network element stores at least one of the following: first indication information, PRU location, association identifier, and PRU identifier.

[0306] After receiving the second notification message, the first network element can store at least one of the following information: first indication information, PRU location, association identifier, and PRU identifier. This information is stored locally as part of the PRU's information.

[0307] In some embodiments, after the PRU and the service network element have successfully established an association, the service network element can perform a location verification operation.

[0308] If the PRU is successfully associated with the serving network element, the serving network element can verify the PRU's location and perform a positioning operation to obtain a more precise location for the PRU. The serving network element can also store information about the received PRU, such as the PRU's positioning capabilities, location, and status. If the PRU association update only involves a change in the PRU's status, the serving network element can consider the previously verified PRU location to be valid.

[0309] If the PRU is successfully associated with the serving network element, and conditions 1 and 2 are met, the service can choose to initiate an Nnrf_NFManagement_NFUpdate request service operation to the NRF network element. This message includes an indication of the existence of the PRU associated with the TAI. The serving network element also instructs the NRF network element to remove the PRU associated with the TAI when there are no longer any PRUs associated with this TAI in the service. Condition 1: This association process is an initial PRU association, or the process is a PRU association update and the PRU information has been changed; Condition 2: The PRU is a fixed PRU. Through this process, the serving network element synchronizes the PRU information with the NRF network element, so other network elements can also learn about the existence of this PRU and the serving network element of this PRU through the NRF network element. Optionally, the NRF network element sends a response message (Nnrf_NFManagement_NFUpdateResponse) to the serving network element.

[0310] In step S2107, the second network element sends a first request message to the first network element. The first request message is used to request information about terminals within the area and / or information about PRUs within the area from the first network element.

[0311] In some embodiments, the second network element can be a network element with positioning management capabilities, such as an LMF network element, or a sensing function (SF) network element. In some scenarios, the second network element may need to collect PRU information, for example, to train AI / ML models or monitor the performance of AI / ML models, where the AI / ML model can be used to locate the terminal. In some embodiments, the PRU information can also be referred to as PRU data.

[0312] The second network element sends a first request message to the first network element. The first request message is used to request information about terminals within the area and / or information about PRUs within the area from the first network element.

[0313] In some embodiments, the first request message may be, for example, a Namf_EventExposure_Subscriber_Request message.

[0314] This area can also be called the region of interest. In some embodiments, if the second network element needs to collect relevant data of a certain region of interest A, it can send a first request message to the first network element to request to subscribe to the information of terminals in region A and / or the information of PRUs in region A.

[0315] This area may include one or more terminals, including terminals that can function as PRUs and terminals that cannot. In other words, a PRU can be a type of terminal; for some terminals, if a terminal possesses PRU functionality, then that terminal can be called a PRU.

[0316] In some embodiments, the first request message may be used to request at least one of the following 1.1 to 1.4:

[0317] 1.1 Information on PRUs within the region.

[0318] Information about a PRU within a region refers to relevant information about PRUs located within that region. For any PRU within that region, the PRU's information may include, for example, one or more of the following: PRU identifier; PRU subscription information; a first verification result indicating whether the PRU possesses PRU functionality; a second verification result indicating whether the PRU is a fixed PRU; a first indication message indicating that a successful association relationship has been established between the PRU and its serving network element; an association relationship identifier identifying the PRU's serving network element, and / or the association relationship between the PRU and its serving network element; and the PRU's location.

[0319] The second network element sends a first request message to the first network element, which requests information about PRUs within the area. Correspondingly, the first network element receives the first request message from the second network element and can then determine that the second network element is requesting PRU information within the area. The first network element can respond to the second network element's request by providing the second network element with the PRU information within the area.

[0320] 1.2 Indication of PRU within the area.

[0321] The indication of PRUs within a region is a type of indication information used to indicate which terminals within the region can act as PRUs, i.e., which devices within the region are PRUs.

[0322] The second network element sends a first request message to the first network element, which requests an indication of the PRUs within the area. Correspondingly, the first network element receives the first request message from the second network element and can then determine that the second network element is requesting an indication of the PRUs within the area. The first network element can respond to the second network element's request by providing an indication of the PRUs within the area.

[0323] 1.3 Identification of terminals within the area.

[0324] Terminal identifiers can be used to identify terminals. For example, terminal identifiers may include terminal SUPI, terminal SUCI, etc.

[0325] The second network element sends a first request message to the first network element, which requests the identifier of a terminal within the area. Correspondingly, the first network element receives the first request message from the second network element and can then determine from the message that the second network element is requesting the identifier of a terminal within the area. The first network element can respond to the second network element's request by providing the identifier of the terminal within the area to the first network element.

[0326] 1.4. Positioning capability information of terminals within the region.

[0327] The positioning capability information of terminals within the area is used to indicate the positioning capabilities of terminals within the area. The positioning capabilities of terminals may include control plane positioning capabilities or user plane positioning capabilities.

[0328] The second network element sends a first request message to the first network element, which requests the location capability information of terminals within the area. Correspondingly, the first network element receives the first request message from the second network element and can then determine that the second network element is requesting the location capability information of terminals within the area. The first network element can respond to the second network element's request by providing the location capability information of terminals within the area to the first network element.

[0329] In step S2108, the first network element determines the list of terminals in the area and the information of the terminals in the area based on the first request message.

[0330] After receiving the first request message, the first network element can determine the terminal list within the area based on the first request message, such as the SUPI list of terminals within the area. This terminal list includes available terminals within the area, wherein the terminals in the terminal list include terminals that can act as PRUs (hereinafter referred to as PRUs) and terminals that cannot act as PRUs.

[0331] Based on the first request message, the first network element determines the list of PRUs within the region and the information of the PRUs within the region.

[0332] The first network element determines the PRU list in the terminal list and the information of the PRUs in the terminal list based on the terminal list in the area.

[0333] For terminals that cannot be used as PRUs, the first network element stores information about the terminal, such as context information. Therefore, the first network element can determine the information of this type of terminal based on the information stored locally.

[0334] For a PRU, the first network element may or may not have stored its information locally. Therefore, the first network element can determine the PRU information in the terminal list based on the PRU information stored within it. Specifically, the first network element searches its stored PRU information based on the identifier of the PRU in the terminal list and uses the retrieved PRU information as the PRU information in the terminal list.

[0335] In some embodiments, the first network element may retrieve information on all PRUs in the terminal list from the PRU information stored in the first network element. In this case, the first network element has completed the operation of determining the terminal information within the area. In some embodiments, the first network element may retrieve information on only some PRUs in the terminal list from the PRU information stored in the first network element. In this case, steps S2109 and S2120 need to be executed.

[0336] In step S2109, if the information of at least one PRU in the terminal list is not found in the PRU information stored in the first network element, the first network element sends a second request message to the fourth network element. The second request message is used to request the subscription information of at least one PRU.

[0337] Since no information for at least one PRU was found in the first network element, the first network element sends a second request message to the fourth network element to request subscription information for the at least one PRU. In some embodiments, the fourth network element may be, for example, a UDM network element. Accordingly, the fourth network element receives the second request message sent by the first network element, and can learn from the second request message that the first network element requests subscription information for at least one PRU.

[0338] In some embodiments, the second request message may be, for example, an Ndum_SDM_Get request message.

[0339] In step S2110, the fourth network element sends a second response message to the first network element, the second response message including subscription information of at least one PRU.

[0340] In some embodiments, the second request message may further include the identifier of at least one PRU, and the fourth network element can look up the subscription information of at least one PRU based on the identifier of at least one PRU. Then, the fourth network element sends a second response message to the first network element, the second response message including the subscription information of at least one PRU; correspondingly, the first network element receives the second response message sent by the fourth network element, and can obtain the subscription information of at least one PRU from the second response message.

[0341] In some embodiments, the second response message may be, for example, an Ndum_SDM_Get response message.

[0342] Step S2111: The first network element stores subscription information for at least one PRU.

[0343] The first network element can store subscription information of at least one PRU, and use it as part of the information of at least one PRU.

[0344] In step S2112, the first network element verifies the PRU based on the PRU's subscription information to obtain a first verification result and / or a second verification result.

[0345] For any PRU in at least one PRU, after obtaining the subscription information of the PRU, the first network element can verify the PRU based on the subscription information to obtain a first verification result and / or a second verification result.

[0346] The first verification result indicates whether the PRU possesses PRU functionality; the second verification result indicates whether the PRU is a fixed PRU. The process by which the first network element verifies the PRU based on its subscription information can be found in [link to documentation]. Figure 2a The relevant content in step S2102 will not be repeated here.

[0347] Step S2113: The first network element stores the first verification result and / or the second verification result.

[0348] After the first network element performs verification on the PRU, the first network element stores the first verification result and / or the second verification result of the PRU. This information is stored locally as part of the information of the PRU.

[0349] In step S2114, the first network element sends a first response message to the second network element. The first response message is used to provide the second network element with information about terminals within the area and / or information about PRUs within the area.

[0350] In some embodiments, the first response message may be, for example, the Namf_EventExposure_Subscriber_Response message.

[0351] In some embodiments, the first response message includes at least one of the following:

[0352] 2.1 Identification of terminals within the area.

[0353] A terminal identifier within an area refers to the identifier of a terminal located within that area. The identifier is used to indicate the terminals within that area. A terminal identifier within an area can include a permanent identifier or a temporary identifier. For example, a terminal identifier within an area could be its SUPI (Supplemental Identity Registry), SUCI (Supplemental Identity Registry), and so on.

[0354] 2.2. Location capability information of terminals within the region.

[0355] The positioning capability information of terminals within the area is used to indicate the positioning capability of terminals within that area. The positioning capability of terminals within that area can be either user plane positioning capability or control plane positioning capability.

[0356] 2.3 Terminal subscription information.

[0357] The terminal's subscription information could be, for example, the subscription information obtained during the terminal's registration process.

[0358] 2.4 Information on PRUs within the region.

[0359] In some embodiments, the terminal within the area includes terminals that cannot be used as PRUs within the area and / or PRUs within the area. The information of the PRUs within the area is information related to the PRUs within the area, such as the type, location, on / off status, etc. of the PRUs.

[0360] In some embodiments, the information of the PRU within the region includes at least one of the following a to f:

[0361] a. PRU identifier.

[0362] The identifier of a PRU is used to indicate the PRU within that area. A PRU may include a permanent identifier for the PRU or a temporary identifier for the PRU. The identifier of a PRU may be, for example, the SUPI of the PRU, the SUCI of the PRU, and so on.

[0363] b. PRU subscription information, used to verify whether the PRU has PRU functionality.

[0364] In some embodiments, for any PRU, the PRU's subscription information can be stored in the fourth network element, and the first network element can request the PRU's subscription information from the fourth network element; the PRU's subscription information can also be stored locally by the first network element.

[0365] c. The first verification result is used to indicate whether the PRU has PRU functionality.

[0366] d. The second verification result is used to indicate whether the PRU belongs to a fixed PRU.

[0367] For any PRU, after obtaining the subscription information of the PRU, the first network element can verify the PRU based on the subscription information to obtain a first verification result and / or a second verification result.

[0368] The first verification result indicates whether the PRU possesses PRU functionality; the second verification result indicates whether the PRU is a fixed PRU. The process by which the first network element verifies the PRU based on its subscription information can be found in [link to documentation]. Figure 2a The relevant content in step S2102 will not be repeated here.

[0369] e. First indication information, used to indicate that the association between PRU and PRU service network elements has been successfully established.

[0370] By receiving the first response message, which includes first indication information, the second network element can know that the association between the PRU and its serving network element has been successfully established, which helps the second network element identify the PRU from the terminal list.

[0371] f. Association identifier, used to identify the service network element of a PRU, and / or the association relationship between PRUs and their service network elements;

[0372] In some embodiments, the association identifier can be used to identify the service network element of the PRU, and / or the association relationship between the service network element of the PRU and the PRU.

[0373] In some embodiments, correlation ID(s) can be identifiers for sessions or services, used to identify a session or service. Correlation IDs can also be called analytics ID(s), and can be used to identify sessions for AI, sessions for location, sessions for sensing, etc. For example, analytics IDs are used to identify sessions for AI; correlation IDs are used to identify sessions for location / sensing.

[0374] The location of h.PRU.

[0375] The location of a PRU can be characterized by various parameters, such as the PRU's coordinates, cell ID, and Tracking Area ID (TAI). In some embodiments, the PRU's location can also be represented by its latitude and longitude coordinates and the area ID (different areas can be pre-divided and identified by different IDs). In some embodiments, the PRU's location can also be characterized by its phase position relative to a reference point, such as a terminal, a base station, a fixed building, etc.

[0376] In some embodiments, if the region includes multiple PRUs, each with a corresponding location, the locations of the multiple PRUs can be represented as a location list. For example, the locations of the PRUs may include a list of TAIs, which includes the TAIs of multiple PRUs.

[0377] 2.5 Second indication information, used to indicate PRUs within the area.

[0378] In some embodiments, the first network element can directly indicate the PRUs within the area to the second network element. For example, the first network element sends a first response message to the second network element, the first response message including second indication information; correspondingly, the second network element receives the first response message sent by the first network element, obtains the second indication information from the first response message, and is thus able to determine the PRUs within the area based on the second indication information.

[0379] The first network element sends a first response message to the second network element. The first response message may include information about terminals within the area and / or information about PRUs within the area. Correspondingly, the second network element receives the first response message sent by the first network element and obtains the terminal information and / or information about PRUs within the area from the first response message.

[0380] Based on terminal information and / or PRU information within the area, the second network element can determine which devices are PRUs from the terminal list provided by the first network element. For a PRU, the second network element can identify its serving network element and then collect its data from that serving network element. This data collection by the second network element does not require the PRU's consent. For terminals that cannot act as PRUs, the second network element can obtain their data from the terminal through the AMF network element. Again, this data collection requires the terminal's consent. In other words, data can only be collected with the terminal's consent. The collected data can be used for AI / ML model training or performance evaluation.

[0381] The subscription method involved in the embodiments of this disclosure may include at least one of steps S2101 to S2114. For example, step S2107 + step S2114 can be implemented as an independent embodiment, step S2107 + step S2108 + step S2114 can be implemented as an independent embodiment, step S2107 + step S2108 + step S2109 + step S2110 + step S2111 + step S2114 can be implemented as an independent embodiment, and step S2107 + step S2108 + step S2109 + step S2110 + step S2111 + step S2112 + step S2113 + step S2114 can be implemented as an independent embodiment, but is not limited thereto.

[0382] In some embodiments, steps S2101, S2102, S2103, S2104, S2105, S2106, S2108, S2109, S2110, S2111, S2112, and S2113 are optional, and one or more of these steps may be omitted or substituted in different embodiments.

[0383] In some embodiments, the steps and their optional implementations in other embodiments described before or after this embodiment, as well as other related parts in the specification, can be referred to, and will not be repeated here.

[0384] Figure 2b This is an exemplary interaction diagram 2 of the communication method provided in this disclosure embodiment. Please refer to [link / reference]. Figure 2b The method includes:

[0385] In step S2201, the PRU sends a PRU association request message to the first network element.

[0386] In some embodiments, optional implementations of step S2201 can be found in [reference needed]. Figure 2a The optional implementation methods of step S2101, and Figure 2a Other related parts in the embodiments involved will not be described in detail here.

[0387] In step S2202, upon receiving a PRU association request message sent by a PRU, the first network element verifies the PRU based on the PRU's subscription information to obtain a first verification result and / or a second verification result.

[0388] In some embodiments, optional implementations of step S2202 can be found in [reference needed]. Figure 2a The optional implementation methods of step S2102, and Figure 2a Other related parts in the embodiments involved will not be described in detail here.

[0389] In step S2203, the first network element stores at least one of the following information: the PRU identifier, the PRU subscription information, the first verification result, and the second verification result.

[0390] In some embodiments, optional implementations of step S2203 can be found in [reference needed]. Figure 2a The optional implementation methods of step S2103, and Figure 2a Other related parts in the embodiments involved will not be described in detail here.

[0391] In step S2204, if the first verification result indicates that the PRU has PRU functionality, the first network element sends a first notification message to the second network element. The first notification message is used to request the establishment of an association between the PRU and the second network element.

[0392] When the sender of the PRU association request message verified by the first network element is a PRU (i.e., the first verification result indicates that the PRU has PRU functionality), the first network element selects the serving network element for that PRU. In some embodiments, the first network element may select the serving network element based on a preset protocol or based on a routing ID. The second network element is the serving network element selected by the first network element.

[0393] After the first network element selects the second network element as the serving network element, the first network element sends a first notification message to the second network element. The first notification message is used to request the establishment of an association between the PRU and the second network element.

[0394] In some embodiments, the first notification message may include the PRU's SUPI, TAI, cell ID, first verification result, second verification result, etc.

[0395] In step S2205, after the second network element successfully associates with the PRU, the second network element sends a second notification message to the first network element. The second notification message includes at least one of the following: first instruction information, the location of the PRU, the association identifier, and the identifier of the PRU.

[0396] The first indication information is used to indicate that the association between the PRU and the second network element has been successfully established. The second network element sends a second notification message to the first network element, which may include the first indication information; correspondingly, the first network element receives the second notification message sent by the second network element, obtains the first indication information from the second notification message, and can know from the first indication information that the association between the PRU and the second network element has been successfully established.

[0397] The location of a PRU may include, for example, the PRU's coordinates, cell ID, TAI, etc. In some embodiments, the PRU's location may also be represented by its latitude and longitude coordinates and the region ID where the PRU is located. In some embodiments, the PRU's location may also be characterized by the phase position between the PRU and a reference point, such as a terminal, a base station, a fixed building, etc.

[0398] The second network element sends a second notification message to the first network element, which may include the location of the PRU; correspondingly, the first network element receives the second notification message sent by the second network element and learns the location of the PRU from the second notification message.

[0399] In some embodiments, the association identifier can be used to identify the association between the second network element and / or the PRU. The second network element is the network element associated with the PRU, or the network element that has established an association with the PRU. In some embodiments, the PRU can establish an association with the second network element by initiating an initial PRU association process or by initiating a PRU association update process.

[0400] The second network element sends a second notification message to the first network element. The second notification message may include an association identifier. Correspondingly, the first network element receives the second notification message sent by the second network element, obtains the association identifier from the second notification message, and can know the second network element associated with the PRU and / or the association relationship established between the PRU and the second network element based on the association identifier.

[0401] In some embodiments, the association identifier can be a session or service identifier used to identify a session or service. The association identifier can also be called an analytics identifier, and can be used to identify sessions used for AI, sessions used for location, sessions used for sensing, etc. For example, an analytics identifier can be used to identify sessions used for AI; an association identifier can be used to identify sessions used for location / sensing.

[0402] The identifier of a PRU is used to indicate that PRU. This identifier can be a temporary identifier or a permanent identifier. For example, the identifier of a PRU can be the SUPI of the PRU, or the SUCI of the PRU.

[0403] Step S2206, the first network element stores at least one of the following: first indication information, PRU location, association identifier, and PRU identifier.

[0404] In some embodiments, optional implementations of step S2206 can be found in [reference needed]. Figure 2a Optional implementations of step S2106, and Figure 2a Other related parts in the embodiments involved will not be described in detail here.

[0405] In step S2207, the second network element sends a first request message to the first network element. The first request message is used to request information about terminals within the area and / or information about PRUs within the area from the first network element.

[0406] In some embodiments, optional implementations of step S2207 can be found in [reference needed]. Figure 2a Optional implementations of step S2107, and Figure 2a Other related parts in the embodiments involved will not be described in detail here.

[0407] In step S2208, the first network element determines the list of terminals in the area and the information of the terminals in the area based on the first request message.

[0408] In some embodiments, optional implementations of step S2208 can be found in [reference needed]. Figure 2a Optional implementations of step S2108, and Figure 2a Other related parts in the embodiments involved will not be described in detail here.

[0409] In step S2209, if the information of at least one PRU in the terminal list is not found in the PRU information stored in the first network element, the first network element sends a second request message to the fourth network element. The second request message is used to request the subscription information of at least one PRU.

[0410] In some embodiments, optional implementations of step S2209 can be found in [reference needed]. Figure 2a Optional implementations of step S2109, and Figure 2a Other related parts in the embodiments involved will not be described in detail here.

[0411] In step S2210, the fourth network element sends a second response message to the first network element, the second response message including subscription information of at least one PRU.

[0412] In some embodiments, optional implementations of step S2210 can be found in [reference needed]. Figure 2a The optional implementation methods of step S2110, and Figure 2a Other related parts in the embodiments involved will not be described in detail here.

[0413] Step S2211: The first network element stores subscription information for at least one PRU.

[0414] In some embodiments, optional implementations of step S2211 can be found in [reference needed]. Figure 2a The optional implementation methods of step S2111, and Figure 2a Other related parts in the embodiments involved will not be described in detail here.

[0415] In step S2212, the first network element verifies the PRU based on the PRU's subscription information to obtain a first verification result and / or a second verification result.

[0416] In some embodiments, optional implementations of step S2212 can be found in [reference needed]. Figure 2a The optional implementation methods of step S2112, and Figure 2a Other related parts in the embodiments involved will not be described in detail here.

[0417] Step S2213: The first network element stores the first verification result and / or the second verification result.

[0418] In some embodiments, optional implementations of step S2213 can be found in [reference needed]. Figure 2a The optional implementation methods of step S2113, and Figure 2a Other related parts in the embodiments involved will not be described in detail here.

[0419] In step S2214, the first network element sends a first response message to the second network element. The first response message is used to provide the second network element with information about terminals within the area and / or information about PRUs within the area.

[0420] In some embodiments, optional implementations of step S2214 can be found in [reference needed]. Figure 2a The optional implementation methods of step S2114, and Figure 2a Other related parts in the embodiments involved will not be described in detail here.

[0421] The subscription method involved in the embodiments of this disclosure may include at least one of steps S2201 to S2214. For example, step S2207 + step S2214 can be implemented as an independent embodiment, step S2207 + step S2208 + step S2214 can be implemented as an independent embodiment, step S2207 + step S2208 + step S2209 + step S2210 + step S2211 + step S2214 can be implemented as an independent embodiment, and step S2207 + step S2208 + step S2209 + step S2210 + step S2211 + step S2212 + step S2213 + step S2214 can be implemented as an independent embodiment, but is not limited thereto.

[0422] In some embodiments, steps S2201, S2202, S2203, S2204, S2205, S2206, S2208, S2209, S2210, S2211, S2212, and S2213 are optional, and one or more of these steps may be omitted or substituted in different embodiments.

[0423] In some embodiments, the steps and their optional implementations in other embodiments described before or after this embodiment, as well as other related parts in the specification, can be referred to, and will not be repeated here.

[0424] Figure 2c This is an exemplary interaction diagram of the communication method provided in this embodiment. Figure 3 Please see Figure 2c The method includes:

[0425] Step S2301: The PRU sends a PRU association request message to the first network element.

[0426] In some embodiments, optional implementations of step S2301 can be found in [reference needed]. Figure 2a The optional implementation methods of step S2101, and Figure 2a Other related parts in the embodiments involved will not be described in detail here.

[0427] In step S2302, upon receiving a PRU association request message sent by a PRU, the first network element verifies the PRU based on the PRU's subscription information to obtain a first verification result and / or a second verification result.

[0428] In some embodiments, optional implementations of step S2302 can be found in [reference needed]. Figure 2a The optional implementation methods of step S2102, and Figure 2a Other related parts in the embodiments involved will not be described in detail here.

[0429] In step S2303, the first network element stores at least one of the following information: the PRU identifier, the PRU subscription information, the first verification result, and the second verification result.

[0430] In some embodiments, optional implementations of step S2303 can be found in [reference needed]. Figure 2a The optional implementation methods of step S2103, and Figure 2a Other related parts in the embodiments involved will not be described in detail here.

[0431] In step S2304, the second network element sends a first request message to the first network element. The first request message is used to request information about terminals within the area and / or information about PRUs within the area from the first network element.

[0432] In some embodiments, optional implementations of step S2304 can be found in [reference needed]. Figure 2a Optional implementations of step S2107, and Figure 2a Other related parts in the embodiments involved will not be described in detail here.

[0433] In step S2305, the first network element determines the list of terminals in the area and the information of the terminals in the area based on the first request message.

[0434] In some embodiments, optional implementations of step S2305 can be found in [reference needed]. Figure 2a Optional implementations of step S2108, and Figure 2a Other related parts in the embodiments involved will not be described in detail here.

[0435] In step S2306, if the information of at least one PRU in the terminal list is not found in the PRU information stored in the first network element, the first network element sends a second request message to the fourth network element. The second request message is used to request the subscription information of at least one PRU.

[0436] In some embodiments, optional implementations of step S2306 can be found in [reference needed]. Figure 2a Optional implementations of step S2109, and Figure 2a Other related parts in the embodiments involved will not be described in detail here.

[0437] In step S2307, the fourth network element sends a second response message to the first network element, the second response message including subscription information of at least one PRU.

[0438] In some embodiments, optional implementations of step S2307 can be found in [reference needed]. Figure 2a The optional implementation methods of step S2110, and Figure 2a Other related parts in the embodiments involved will not be described in detail here.

[0439] Step S2308: The first network element stores subscription information for at least one PRU.

[0440] The first network element can store subscription information of at least one PRU, and use it as part of the information of at least one PRU.

[0441] In step S2309, the first network element verifies the PRU based on the PRU's subscription information to obtain a first verification result and / or a second verification result.

[0442] In some embodiments, optional implementations of step S2309 can be found in [reference needed]. Figure 2a The optional implementation methods of step S2112, and Figure 2a Other related parts in the embodiments involved will not be described in detail here.

[0443] Step S2310: The first network element stores the first verification result and / or the second verification result.

[0444] The first network element can store the first verification result and / or the second verification result of at least one PRU, and use them as part of the information of at least one PRU.

[0445] In step S2311, the first network element sends a first response message to the second network element. The first response message is used to provide the second network element with information about terminals within the area and / or information about PRUs within the area.

[0446] In some embodiments, optional implementations of step S2311 can be found in [reference needed]. Figure 2aThe optional implementation methods of step S2114, and Figure 2a Other related parts in the embodiments involved will not be described in detail here.

[0447] The subscription method involved in the embodiments of this disclosure may include at least one of steps S2301 to S2311. For example, step S2304 + step S2311 may be implemented as a standalone embodiment, step S2304 + step S2308 + step S2311 may be implemented as a standalone embodiment, and step S2304 + step S2305 + step S2306 + step S2307 + step S2308 + step S2311 may be implemented as a standalone embodiment, but is not limited thereto.

[0448] In some embodiments, steps S2301, S2302, S2303, S2305, S2306, S2308, S2309, and S2310 are optional, and one or more of these steps may be omitted or substituted in different embodiments.

[0449] In some embodiments, the steps and their optional implementations in other embodiments described before or after this embodiment, as well as other related parts in the specification, can be referred to, and will not be repeated here.

[0450] Figure 3 This is an exemplary interaction diagram four of the communication method provided in this disclosure embodiment. Please refer to [link / reference]. Figure 3 The method includes:

[0451] Step S301: The second network element sends a first request message to the first network element. The first request message is used to request information about terminals within the area and / or information about PRUs within the area from the first network element.

[0452] In some embodiments, the first network element may be, for example, an AMF network element. In some embodiments, the second network element may be, for example, an LMF network element or a sensing function network element.

[0453] After receiving the first request message, the first network element can determine the terminal list within the area based on the first request message, such as the SUPI list of terminals within the area. This terminal list includes available terminals within the area, wherein the terminals in the terminal list include terminals that can act as PRUs (hereinafter referred to as PRUs) and terminals that cannot act as PRUs.

[0454] For terminals that cannot be used as PRUs, the first network element stores information about the terminal, such as context information. Therefore, the first network element can determine the information of this type of terminal based on the information stored locally.

[0455] For a PRU, the first network element may or may not have stored its information locally. Therefore, the first network element can determine the PRU information in the terminal list based on the PRU information stored within it. Specifically, the first network element searches its stored PRU information based on the identifier of the PRU in the terminal list and uses the retrieved PRU information as the PRU information in the terminal list.

[0456] In step S302, the first network element sends a first response message to the second network element. The first response message is used to provide the second network element with information about terminals within the area and / or information about PRUs within the area.

[0457] The first network element sends a first response message to the second network element. The first response message may include information about terminals within the area and / or information about PRUs within the area. Correspondingly, the second network element receives the first response message sent by the first network element and obtains the terminal information and / or information about PRUs within the area from the first response message.

[0458] Based on terminal information and / or PRU information within the area, the second network element can determine which devices are PRUs from the terminal list provided by the first network element. For a PRU, the second network element can identify its serving network element and then collect its data from that serving network element. This data collection by the second network element does not require the PRU's consent. For terminals that cannot act as PRUs, the second network element can obtain their data from the terminal through the AMF network element. Again, this data collection requires the terminal's consent. In other words, data collection from a terminal is only possible with its consent.

[0459] The subscription method involved in the embodiments of this disclosure may include at least one of steps S301 to S302. For example, step S301 may be implemented as a standalone embodiment, but is not limited thereto.

[0460] In some embodiments, step S302 is optional, and one or more of these steps may be omitted or substituted in different embodiments.

[0461] In some embodiments, the steps and their optional implementations in other embodiments described before or after this embodiment, as well as other related parts in the specification, can be referred to, and will not be repeated here.

[0462] In some embodiments, the steps and their optional implementations in other embodiments described before or after this embodiment, as well as other related parts in the specification, can be referred to, and will not be repeated here.

[0463] This disclosure also proposes an apparatus (also referred to as a communication device, etc.) for implementing any of the above methods. For example, an apparatus is proposed, which includes units or modules for implementing the steps performed by the first network element in any of the above methods. Furthermore, another apparatus is proposed, which includes units or modules for implementing the steps performed by the second network element in any of the above methods.

[0464] It should be understood that the division of units or modules in the above device is only a logical functional division. In actual implementation, they can be fully or partially integrated into a single physical entity, or they can be physically separated. Furthermore, the units or modules in the device can be implemented by a processor calling software: for example, the device includes a processor connected to a memory containing instructions. The processor calls the instructions stored in the memory to implement any of the above methods or to implement the functions of the units or modules in the above device. The processor can be, for example, a general-purpose processor, such as a Central Processing Unit (CPU) or a microprocessor, and the memory can be internal or external to the device. Alternatively, the units or modules in the device can be implemented in the form of hardware circuits. The functionality of some or all of the units or modules can be achieved through the design of these hardware circuits, which can be understood as one or more processors. For example, in one implementation, the hardware circuit is an application-specific integrated circuit (ASIC). The functionality of some or all of the units or modules is achieved through the design of the logical relationships between the components within the circuit. In another implementation, the hardware circuit can be implemented using a programmable logic device (PLD). Taking a field-programmable gate array (FPGA) as an example, it can include a large number of logic gates. The connection relationships between the logic gates are configured through configuration files, thereby achieving the functionality of some or all of the units or modules. All units or modules of the above device can be implemented entirely through processor-called software, entirely through hardware circuits, or partially through processor-called software with the remaining parts implemented through hardware circuits.

[0465] In this embodiment, the processor is a circuit with signal processing capabilities. In one implementation, the processor can be a circuit with instruction read and execute 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 relationships of hardware circuits. The logical relationships of the aforementioned hardware circuits are fixed or reconfigurable. For example, the processor is a hardware circuit implemented using 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 configuring the hardware circuit 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 hardware circuits designed for artificial intelligence, which can be understood as ASICs, such as Neural Network Processing Units (NPUs), Tensor Processing Units (TPUs), and Deep Learning Processing Units (DPUs).

[0466] Figure 4a This is a schematic diagram of the structure of the first network element proposed in an embodiment of this disclosure. The first network element 4100 is used to perform any of the above methods. In some embodiments, such as Figure 4a As shown, the first network element 4100 may include at least one of a transceiver module 4101 and a processing module 4102, wherein:

[0467] The transceiver module 4101 is used to receive a first request message sent by the second network element. The first request message is used to request information of terminals in the area and / or information of PRUs in the area from the first network element.

[0468] The transceiver module 4101 is also used to send a first response message to the second network element. The first response message is used to provide the second network element with information about terminals in the area and / or information about PRUs in the area.

[0469] In some embodiments, the first request message is used to request at least one of the following from the first network element:

[0470] Information on PRUs within the region;

[0471] Indication of PRU within the area;

[0472] Identification of terminals within the area;

[0473] Location capability information of terminals within the area.

[0474] In some embodiments, the processing module 4102 is configured to:

[0475] Based on the first request message, determine the list of terminals within the area, and determine the information of the terminals within the area.

[0476] In some embodiments, the terminal list includes PRUs, and the processing module 4102 is specifically used for:

[0477] Based on the PRU information stored in the first network element, determine the PRU information in the terminal list.

[0478] In some embodiments, the processing module 4102 is further configured to:

[0479] Upon receiving a PRU association request message from a PRU, the PRU is verified based on its subscription information to obtain a first verification result and / or a second verification result. The first verification result is used to indicate whether the PRU has PRU functionality; the second verification result is used to indicate whether the PRU belongs to a fixed PRU.

[0480] Store at least one of the following information: PRU identifier, PRU subscription information, first verification result, and second verification result.

[0481] In some embodiments, the transceiver module 4101 is further configured to:

[0482] If the first verification result indicates that the PRU has PRU functionality, a first notification message is sent to the serving network element selected by the first network element.

[0483] The first notification message is used to request the establishment of an association between the PRU and the service network element; the service network element is either the second network element or the third network element.

[0484] In some embodiments,

[0485] The transceiver module 4101 is also used to receive a second notification message sent by the serving network element. The second notification message includes at least one of the following: first indication information, PRU location, association identifier, and PRU identifier. The first indication information is used to indicate that the association between the PRU and the serving network element has been successfully established. The association identifier is used to identify the serving network element and / or the association.

[0486] The processing module 4102 is also used to store at least one of the following: first indication information, the location of the PRU, the association identifier, and the identifier of the PRU.

[0487] In some embodiments, the transceiver module 4101 is further configured to send a second request message to a fourth network element when no information of at least one PRU in the terminal list is found in the PRU information stored in the first network element; the second request message is used to request subscription information of at least one PRU; and receive a second response message sent by the fourth network element, the second response message including subscription information of at least one PRU.

[0488] The processing module 4102 is also used to store subscription information for at least one PRU.

[0489] In some embodiments, for any PRU in at least one PRU, the processing module 4102 is further configured to:

[0490] The PRU is verified based on its subscription information to obtain a first verification result and / or a second verification result; the first verification result is used to indicate whether the PRU has PRU functionality; the second verification result is used to indicate whether the PRU is a fixed PRU.

[0491] Store the first verification result and / or the second verification result.

[0492] In some embodiments, the first response message includes at least one of the following:

[0493] Identification of terminals within the area;

[0494] Location capability information of terminals within the area;

[0495] Terminal subscription information;

[0496] Information on PRUs within the region;

[0497] The second instruction information is used to indicate the PRU within the area.

[0498] In some embodiments, the PRU information includes at least one of the following:

[0499] The PRU identifier;

[0500] The subscription information of the PRU is used to verify whether the PRU has PRU functionality;

[0501] The first verification result is used to indicate whether the PRU has PRU functionality;

[0502] The second verification result is used to indicate whether the PRU belongs to a fixed PRU;

[0503] The first instruction message is used to indicate that the association between the PRU and the PRU's service network element has been successfully established;

[0504] Association identifier, used to identify the service network element of PRU, and / or the association relationship between PRUs and their service network elements;

[0505] Location of PRU.

[0506] Optionally, the transceiver module 4101 is used to perform at least one of the communication steps such as sending and / or receiving performed by the first network element 4100 in any of the above methods (e.g., steps S2101, S2104, S2105, S2107, S2109, S2110, S2114, S2201, S2204, S2205, S2207, S2209, S2210, S2214, S2301, S2304, S2306, S2307, S2311, S301, S302, but not limited thereto), which will not be elaborated here. Optionally, the processing module 4102 is used to execute at least one of the other steps executed by the first network element 4100 in any of the above methods (e.g., steps S2102, S2103, S2106, S2108, S2111, S2112, S2113, S2202, S2203, S2206, S2208, S2211, S2212, S2213, S2302, S2303, S2305, S2308, S2309, S2310, but not limited thereto), which will not be elaborated here.

[0507] Figure 4b This is a schematic diagram of the structure of the second network element proposed in an embodiment of this disclosure. The second network element 4200 is used to perform any of the above methods. In some embodiments, such as Figure 4b As shown, the second network element 4200 may include:

[0508] The transceiver module 4201 is used to send a first request message to the first network element. The first request message is used to request information of terminals in the area and / or information of PRUs in the area from the first network element.

[0509] The transceiver module 4201 is also used to receive a first response message sent by the first network element. The first response message is used to provide the second network element with information about terminals in the area and / or information about PRUs in the area.

[0510] In some embodiments, the first request message is used to request at least one of the following from the first network element:

[0511] Information on PRUs within the region;

[0512] Indication of PRU within the area;

[0513] Identification of terminals within the area;

[0514] Location capability information of terminals within the area.

[0515] In some embodiments, the transceiver module 4201 is further configured to:

[0516] Receive the first notification message sent by the first network element;

[0517] The first notification message is used to request the establishment of an association between the PRU and the second network element, where the second network element is the serving network element selected by the first network element.

[0518] In some embodiments, the transceiver module 4201 is further configured to:

[0519] If the association between the PRU and the second network element is successfully established, a second notification message is sent to the first network element. The second notification message includes at least one of the following: first indication information, the location of the PRU, the association identifier, and the identifier of the PRU. The first indication information is used to indicate that the association between the PRU and the second network element has been successfully established, and the association identifier is used to identify the second network element and / or the association.

[0520] In some embodiments, the first response message includes at least one of the following:

[0521] Identification of terminals within the area;

[0522] Location capability information of terminals within the area;

[0523] Terminal subscription information;

[0524] Information on PRUs within the region;

[0525] The second instruction information is used to indicate the PRU within the area.

[0526] In some embodiments, the PRU information includes at least one of the following:

[0527] The PRU identifier;

[0528] The subscription information of the PRU is used to verify whether the PRU has PRU functionality;

[0529] The first verification result is used to indicate whether the PRU has PRU functionality;

[0530] The second verification result is used to indicate whether the PRU belongs to a fixed PRU;

[0531] The first instruction message is used to indicate that the association between the PRU and the PRU's service network element has been successfully established;

[0532] Association identifier, used to identify the service network element of PRU, and / or the association relationship between PRUs and their service network elements;

[0533] Location of PRU.

[0534] Optionally, the transceiver module 4201 is used to perform at least one of the communication steps such as sending and / or receiving performed by the second network element 4200 in any of the above methods (e.g., steps S2107, S2114, S2204, S2205, S2207, S2214, S2304, S2311, S301, S302, but not limited thereto), which will not be elaborated here.

[0535] Figure 4c This is a schematic diagram of the structure of the third network element proposed in an embodiment of this disclosure. The third network element 4300 is used to perform any of the above methods. In some embodiments, such as Figure 4c As shown, the third network element 4300 may include a transceiver module 4301, wherein:

[0536] The transceiver module 4301 is used to receive the first notification message sent by the first network element;

[0537] The first notification message is used to request the establishment of an association between the PRU and the third network element, where the third network element is the serving network element selected by the first network element.

[0538] In some embodiments, the transceiver module 4301 is further configured to:

[0539] If the association between the PRU and the third network element is successfully established, a second notification message is sent to the first network element. The second notification message includes at least one of the following: first indication information, the location of the PRU, the association identifier, and the identifier of the PRU. The first indication information is used to indicate that the association between the PRU and the third network element has been successfully established, and the association identifier is used to identify the third network element and / or the association.

[0540] Optionally, the transceiver module 4301 is used to perform at least one of the communication steps (such as step S2104, step S2105, but not limited thereto) performed by the third network element 4300 in any of the above methods, which will not be elaborated here.

[0541] Figure 4d This is a schematic diagram of the structure of the fourth network element proposed in an embodiment of this disclosure. The fourth network element 4400 is used to perform any of the above methods. In some embodiments, such as Figure 4dAs shown, the fourth network element 4400 may include:

[0542] The transceiver module 4401 is used to receive a second request message sent by the first network element. The second request message is used to request subscription information of at least one PRU.

[0543] The transceiver module 4401 is also used to send a second response message to the first network element. The second response message includes subscription information of at least one PRU. The subscription information of at least one PRU is used to verify whether at least one PRU has the function of a PRU and / or whether at least one PRU belongs to a fixed PRU.

[0544] Optionally, the transceiver module 4401 is used to perform at least one of the communication steps such as sending and / or receiving performed by the fourth network element 4400 in any of the above methods (e.g., steps S2109, S2110, S2209, S2210, S2306, S2307, but not limited thereto), which will not be elaborated here.

[0545] Figure 5a This is a schematic diagram of the structure of the communication device 5100 proposed in this embodiment. The communication device 5100 can be a network device (e.g., access network device, core network device, etc.), a terminal (e.g., user equipment, etc.), a chip, chip system, or processor that supports the network device in implementing any of the above methods, or a chip, chip system, or processor that supports the terminal in implementing any of the above methods. The communication device 5100 can be used to implement the methods described in the above method embodiments; for details, please refer to the descriptions in the above method embodiments.

[0546] like Figure 5a As shown, the communication device 5100 is used to execute any of the above methods. In some embodiments, the communication device 5100 includes one or more processors 5101. The processor 5101 may be a general-purpose processor or a special-purpose processor, such as a baseband processor or a central processing unit. The baseband processor may be used to process communication protocols and communication data, and the central processing unit may be used to control communication devices (e.g., base stations, baseband chips, terminals, terminal chips, DUs or CUs, etc.), execute programs, and process program data. Optionally, the communication device 5100 is used to execute any of the above methods. Optionally, one or more processors 5101 are used to invoke instructions to cause the communication device 5100 to execute any of the above methods.

[0547] In some embodiments, the communication device 5100 further includes one or more transceivers 5102. When the communication device 5100 includes one or more transceivers 5102, the transceivers 5102 perform communication steps such as sending and / or receiving in the above method (e.g., steps S2101, S2104, S2105, S2107, S2109, S2110, S2114, S2201, S2204, S2205, S2207, S2209, S2210, S2214, S2301, S2304, S2306, S2307, S2311, S3). At least one of steps S1, S302, but not limited thereto, is performed by processor 5101, which executes at least one of other steps (e.g., steps S2102, S2103, S2106, S2108, S2111, S2112, S2113, S2202, S2203, S2206, S2208, S2211, S2212, S2213, S2302, S2303, S2305, S2308, S2309, S2310, but not limited thereto). In optional embodiments, the transceiver may include a receiver and / or a transmitter, which may be separate or integrated together. Optionally, terms such as transceiver, transceiver unit, transceiver, transceiver circuit, interface circuit, and interface can be used interchangeably; terms such as transmitter, transmitter unit, transmitter, and transmitter circuit can be used interchangeably; and terms such as receiver, receiver unit, receiver, and receiver circuit can be used interchangeably.

[0548] In some embodiments, the communication device 5100 further includes one or more memories 5103 for storing data and / or instructions. Optionally, one or more processors 5101 are used to invoke instructions stored in the memory 5103 to cause the communication device 5100 to perform any of the above methods. Optionally, all or part of the memory 5103 may also be located outside the communication device 5100. In an optional embodiment, the communication device 5100 may include one or more interface circuits 5104. Optionally, the interface circuit 5104 is connected to the memory 5103 and can be used to receive data and / or instructions from the memory 5103 or other devices, and can be used to send data and / or instructions to the memory 5103 or other devices. For example, the interface circuit 5104 can read data and / or instructions stored in the memory 5103 and send the data and / or instructions to the processor 5101.

[0549] The communication device 5100 described in the above embodiments may be a network device or a terminal, but the scope of the communication device 5100 described in this disclosure is not limited thereto, and the structure of the communication device 5100 may vary. Figure 5a The limitations. The communication device may be a standalone device or part of a larger device. For example, the communication device may be: (1) a standalone integrated circuit IC, or chip, or chip system or subsystem; (2) a collection of one or more ICs, optionally including storage components for storing data, programs and / or instructions; (3) an ASIC, such as a modem; (4) a module that can be embedded in other devices; (5) a receiver, terminal, smart terminal, cellular phone, wireless device, handheld device, mobile unit, vehicle-mounted device, network device, cloud device, artificial intelligence device, etc.; (6) others, etc.

[0550] Figure 5b This is a schematic diagram of the structure of chip 5200 according to an embodiment of this disclosure. For cases where the communication device 5100 can be a chip or a chip system, please refer to... Figure 5b The diagram shown is a schematic representation of the structure of chip 5200, but it is not limited to this.

[0551] Chip 5200 includes one or more processors 5201. Chip 5200 is used to perform any of the methods described above.

[0552] In some embodiments, chip 5200 further includes one or more interface circuits 5202. Optionally, terms such as interface circuit, interface, and transceiver pin can be used interchangeably. In some embodiments, chip 5200 further includes one or more memories 5203 for storing data and / or instructions. Optionally, all or part of the memories 5203 may be located outside of chip 5200. Optionally, the interface circuit 5202 is connected to the memories 5203, and the interface circuit 5202 can be used to receive data and / or instructions from the memories 5203 or other devices, and the interface circuit 5202 can be used to send data and / or instructions to the memories 5203 or other devices. For example, the interface circuit 5202 can read data and / or instructions stored in the memories 5203 and send the data and / or instructions to the processor 5201.

[0553] In some embodiments, the interface circuit 5202 performs at least one of the communication steps such as sending and / or receiving in the above-described method (e.g., steps S2101, S2104, S2105, S2107, S2109, S2110, S2114, S2201, S2204, S2205, S2207, S2209, S2210, S2214, S2301, S2304, S2306, S2307, S2311, S301, S302, but not limited thereto). The interface circuit 5202 performing the communication steps such as sending and / or receiving in the above-described method refers, for example, to the interface circuit 5202 performing data and / or instruction interaction between the processor 5201, chip 5200, memory 5203, or transceiver device. In some embodiments, the processor 5201 performs at least one of other steps (e.g., steps S2102, S2103, S2106, S2108, S2111, S2112, S2113, S2202, S2203, S2206, S2208, S2211, S2212, S2213, S2302, S2303, S2305, S2308, S2309, S2310, but is not limited thereto).

[0554] The modules and / or devices described in the various embodiments, such as virtual devices, physical devices, and chips, can be combined or separated arbitrarily as needed. Optionally, some or all steps can also be performed collaboratively by multiple modules and / or devices, which is not limited here.

[0555] This disclosure also proposes a storage medium storing instructions that, when executed on a communication device, cause the communication device to perform 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 not limited thereto; it may also be a storage medium readable by other devices. Optionally, the storage medium may be a non-transitory storage medium, but not limited thereto; it may also be a temporary storage medium.

[0556] This disclosure also proposes a program product, including a program and / or instructions, which, when executed by a communication device, cause the communication device to perform any of the above methods. Optionally, the program product is a computer program product. Optionally, the program product is stored on the storage medium.

[0557] This disclosure also proposes a computer program that, when run on a computer, causes the computer to perform any of the above methods.

[0558] Those skilled in the art will recognize that the units and algorithm steps of the various examples described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are implemented in hardware or software depends on the specific application and design constraints of the technical solution. Those skilled in the art can use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of this disclosure.

[0559] Those skilled in the art will understand that, for the sake of convenience and brevity, the specific working processes of the systems, devices, and units described above can be referred to the corresponding processes in the foregoing method embodiments, and will not be repeated here.

[0560] The above are merely specific embodiments of this disclosure, but the scope of protection of this disclosure is not limited thereto. Any variations or substitutions that can be easily conceived by those skilled in the art within the scope of the technology disclosed in this disclosure should be included within the scope of protection of this disclosure. Therefore, the scope of protection of this disclosure should be determined by the scope of the claims.

Claims

1. A communication method, characterized in that, The method, executed by the first network element, includes: Receive a first request message sent by a second network element, the first request message being used to request information of terminals in the area and / or information of positioning reference units (PRUs) in the area from the first network element; Send a first response message to the second network element. The first response message is used to provide the second network element with information about terminals in the area and / or information about PRUs in the area.

2. The method according to claim 1, characterized in that, The first request message is used to request at least one of the following from the first network element: Information about PRUs within the region; Indication of PRU within the area; The identifier of the terminal within the area; The location capability information of terminals within the area.

3. The method according to claim 1 or 2, characterized in that, The method further includes: Based on the first request message, a list of terminals within the region is determined, as well as information about the terminals within the region.

4. The method according to claim 3, characterized in that, The terminal list includes PRUs, and the information for determining the terminals within the area includes: Based on the PRU information stored in the first network element, the PRU information in the terminal list is determined.

5. The method according to claim 4, characterized in that, The method further includes: Upon receiving a PRU association request message from a PRU, the PRU is verified based on its subscription information to obtain a first verification result and / or a second verification result. The first verification result indicates whether the PRU has PRU functionality; the second verification result indicates whether the PRU is a fixed PRU. Store at least one of the following information: the identifier of the PRU, the subscription information of the PRU, the first verification result, and the second verification result.

6. The method according to claim 5, characterized in that, The method further includes: If the first verification result indicates that the PRU has the PRU function, a first notification message is sent to the serving network element selected by the first network element. The first notification message is used to request the establishment of an association between the PRU and the service network element; the service network element is the second network element or the third network element.

7. The method according to claim 6, characterized in that, The method further includes: The system receives a second notification message sent by the serving network element. The second notification message includes at least one of the following: first indication information, the location of the PRU, an association identifier, and the identifier of the PRU. The first indication information is used to indicate that the association between the PRU and the serving network element has been successfully established, and the association identifier is used to identify the serving network element and / or the association. Store at least one of the following: the first indication information, the location of the PRU, the association identifier, and the identifier of the PRU.

8. The method according to claim 4, characterized in that, The method further includes: If the information of at least one PRU in the terminal list is not found in the PRU information stored in the first network element, a second request message is sent to the fourth network element. The second request message is used to request the subscription information of the at least one PRU. Receive a second response message sent by the fourth network element, wherein the second response message includes subscription information of the at least one PRU; Store the subscription information of the at least one PRU.

9. The method according to claim 8, characterized in that, For any PRU in the at least one PRU, the method further includes: The PRU is verified based on its subscription information to obtain a first verification result and / or a second verification result; the first verification result is used to indicate whether the PRU has PRU functionality; the second verification result is used to indicate whether the PRU is a fixed PRU. Store the first verification result and / or the second verification result.

10. The method according to any one of claims 1-9, characterized in that, The first response message includes at least one of the following: The identifier of the terminal within the area; Location capability information of terminals within the area; Terminal subscription information; Information about PRUs within the region; The second indication information is used to indicate the PRU within the area.

11. The method according to claim 10, characterized in that, The information of the PRU includes at least one of the following: The identifier of the PRU; The subscription information of the PRU is used to verify whether the PRU has PRU functionality; The first verification result is used to indicate whether the PRU has PRU functionality; The second verification result is used to indicate whether the PRU belongs to a fixed PRU; The first indication information is used to indicate that the association relationship between the PRU and the PRU's serving network element has been successfully established; Association identifier, used to identify the service network element of the PRU, and / or the association relationship between the PRU and the service network element of the PRU; The location of the PRU.

12. A communication method, characterized in that, The method, executed by the second network element, includes: Send a first request message to the first network element, the first request message being used to request information of terminals within the area and / or information of PRUs within the area from the first network element; The system receives a first response message sent by the first network element. The first response message is used to provide the second network element with information about terminals in the area and / or information about PRUs in the area.

13. The method according to claim 12, characterized in that, The first request message is used to request at least one of the following from the first network element: Information about PRUs within the region; Indication of PRU within the area; The identifier of the terminal within the area; The location capability information of terminals within the area.

14. The method according to claim 12 or 13, characterized in that, The method further includes: Receive the first notification message sent by the first network element; The first notification message is used to request the establishment of an association between the PRU and the second network element, where the second network element is the serving network element selected by the first network element.

15. The method according to claim 14, characterized in that, The method further includes: If the association between the PRU and the second network element is successfully established, a second notification message is sent to the first network element. The second notification message includes at least one of the following: first indication information, the location of the PRU, the association identifier, and the identifier of the PRU. The first indication information is used to indicate that the association between the PRU and the second network element has been successfully established, and the association identifier is used to identify the second network element and / or the association.

16. The method according to any one of claims 12-15, characterized in that, The first response message includes at least one of the following: The identifier of the terminal within the area; Location capability information of terminals within the area; Terminal subscription information; Information about PRUs within the region; The second indication information is used to indicate the PRU within the area.

17. The method according to claim 16, characterized in that, The information of the PRU includes at least one of the following: The identifier of the PRU; The subscription information of the PRU is used to verify whether the PRU has PRU functionality; The first verification result is used to indicate whether the PRU has PRU functionality; The second verification result is used to indicate whether the PRU belongs to a fixed PRU; The first indication information is used to indicate that the association relationship between the PRU and the PRU's serving network element has been successfully established; Association identifier, used to identify the service network element of the PRU, and / or the association relationship between the PRU and the service network element of the PRU; The location of the PRU.

18. A communication method, characterized in that, The method, executed by a third network element, includes: Receive the first notification message sent by the first network element; The first notification message is used to request the establishment of an association between the PRU and the third network element, wherein the third network element is the serving network element selected by the first network element.

19. The method according to claim 18, characterized in that, The method further includes: If the association between the PRU and the third network element is successfully established, a second notification message is sent to the first network element. The second notification message includes at least one of the following: first indication information, the location of the PRU, the association identifier, and the identifier of the PRU. The first indication information is used to indicate that the association between the PRU and the third network element has been successfully established, and the association identifier is used to identify the third network element and / or the association.

20. A communication method, characterized in that, The method, executed by the fourth network element, includes: Receive a second request message sent by a first network element, the second request message being used to request subscription information for at least one PRU; A second response message is sent to the first network element. The second response message includes subscription information of the at least one PRU. The subscription information of the at least one PRU is used to verify whether the at least one PRU has the function of a PRU and / or whether the at least one PRU belongs to a fixed PRU.

21. A first network element, characterized in that, include: The transceiver module is used to receive a first request message sent by a second network element. The first request message is used to request information of terminals within the area and / or information of PRUs within the area from the first network element. The transceiver module is further configured to send a first response message to the second network element, the first response message being configured to provide the second network element with information about terminals within the area and / or information about PRUs within the area.

22. A second network element, characterized in that, include: The transceiver module is used to send a first request message to the first network element, wherein the first request message is used to request information of terminals within the area and / or information of PRUs within the area from the first network element; The transceiver module is further configured to receive a first response message sent by the first network element, the first response message being used to provide the second network element with information about terminals within the area and / or information about PRUs within the area.

23. A third network element, characterized in that, include: The transceiver module is used to receive the first notification message sent by the first network element; The first notification message is used to request the establishment of an association between the PRU and the third network element, wherein the third network element is the serving network element selected by the first network element.

24. A fourth network element, characterized in that, include: The transceiver module is used to receive a second request message sent by the first network element, the second request message being used to request subscription information of at least one PRU; The transceiver module is further configured to send a second response message to the first network element. The second response message includes subscription information of the at least one PRU. The subscription information of the at least one PRU is used to verify whether the at least one PRU has the function of a PRU and / or whether the at least one PRU belongs to a fixed PRU.

25. A communication device, characterized in that, The communication device is used to perform the communication method according to any one of claims 1 to 20.

26. A communication system, characterized in that, include: The first network element, the second network element, the third network element, and the fourth network element; Wherein, the first network element is configured to implement the communication method of any one of claims 1-11; the second network element is configured to implement the communication method of any one of claims 12-17; the third network element is configured to implement the communication method of any one of claims 18-19; and the fourth network element is configured to implement the communication method of claim 20.

27. A storage medium storing instructions, characterized in that, When the instruction is executed on the communication device, the communication device performs the communication method as described in any one of claims 1-20.

28. A program product comprising a program and / or instructions, characterized in that, When the program and / or instructions are executed by the communication device, the communication method as described in any one of claims 1-20 is implemented.

Images