Subscription method, apparatus, and system, storage medium, and program product

Abstract

Embodiments of the present application provide a subscription method, apparatus, and system, a storage medium, and a program product. The method is executed by a first network element, and comprises: sending a first request to a second network element, wherein the first request is used for subscribing to an event of a positioning reference unit (PRU) in an area, and / or information of the PRU in the area. The solution in the embodiments of the present application can reduce the signaling overhead of a first network element acquiring information of a PRU in an area.

Description

Subscription methods, devices, systems, storage media, and program products Technical Field

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

[0002] A positioning reference unit (PRU) is a fixed or semi-fixed device that assists in locating a terminal device by transmitting reference signals or reporting its own position. In some cases, the location management function (LMF) network element can also acquire PRU information and train a positioning model based on the PRU information to achieve the positioning of the terminal device. Summary of the Invention

[0003] This disclosure provides a subscription method, apparatus, system, storage medium, and program product to reduce the signaling overhead of a first network element acquiring PRU information.

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

[0005] Send a first request to the second network element. The first request is used to subscribe to events of the localization reference unit (PRU) in the region and / or to subscribe to information of the PRU in the region.

[0006] In this embodiment of the disclosure, the first network element can subscribe to events and / or information of PRUs in the region by sending a first request to the second network element. When such events and / or PRU information change, the first network element can obtain the information of PRUs in the region through the subscription process without requesting the second network element, thereby saving the signaling overhead of the first network element in obtaining the information of PRUs in the region.

[0007] According to a second aspect of the embodiments of this disclosure, a subscription method is proposed, executed by a second network element, the method comprising:

[0008] Receive a first request sent by a first network element, the first request being used to subscribe to events of PRUs in the area, and / or to subscribe to information of PRUs in the area.

[0009] In this embodiment of the disclosure, the second network element can subscribe to the events and / or information of PRUs in the region by receiving a first request sent by the first network element. When the events and / or information of PRUs in the region change, the first network element does not need to request the second network element, and the second network element can actively send the information of the PRUs in the region to the first network element, thereby saving the signaling overhead of the second network element in sending the information of the PRUs in the region.

[0010] According to a third aspect of the embodiments of this disclosure, a subscription device is provided, comprising:

[0011] The transceiver module is used to send a first request to the second network element. The first request is used to subscribe to events of PRUs in the area and / or to subscribe to information of PRUs in the area.

[0012] According to a fourth aspect of the embodiments of this disclosure, a subscription device is provided, comprising:

[0013] The transceiver module is used to receive a first request sent by a first network element. The first request is used to subscribe to events of PRUs in the area and / or to subscribe to information of PRUs in the area.

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

[0015] One or more processors;

[0016] The first network element is used to execute the method described in the optional implementation of the first aspect.

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

[0018] One or more processors;

[0019] The second network element is used to execute the method described in the optional implementation of the second aspect.

[0020] According to a seventh aspect of the embodiments of this disclosure, a subscription system is proposed, comprising: a first network element and a second network element;

[0021] 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.

[0022] According to an eighth 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 as described in an optional implementation of the second aspect.

[0023] According to a ninth 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. Attached Figure Description

[0024] 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.

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

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

[0027] Figure 1c is a flowchart of data collection by an LMF network element according to an embodiment of this disclosure;

[0028] Figure 2a is an exemplary interactive schematic diagram of the subscription method provided in an embodiment of this disclosure;

[0029] Figure 2b is an exemplary interactive schematic diagram of the subscription method provided in this embodiment of the present disclosure;

[0030] Figure 2c is an exemplary interactive schematic diagram of the subscription method provided in this embodiment of the present disclosure;

[0031] Figure 2d is an exemplary interactive schematic diagram of the subscription method provided in this embodiment of the present disclosure;

[0032] Figure 3 is an exemplary interactive diagram of the subscription method provided in an embodiment of this disclosure;

[0033] Figure 4a is a schematic diagram of the structure of the subscription device proposed in an embodiment of this disclosure;

[0034] Figure 4b is a schematic diagram of the subscription device proposed in an embodiment of this disclosure;

[0035] Figure 5a is a schematic diagram of the structure of the communication device proposed in an embodiment of this disclosure;

[0036] Figure 5b is a schematic diagram of the chip structure proposed in an embodiment of this disclosure. Detailed Implementation

[0037] This disclosure provides a subscription method, apparatus, system, storage medium, and program product to reduce the signaling overhead of a first network element acquiring PRU information.

[0038] According to a first aspect of the embodiments of this disclosure, a subscription method is proposed, executed by a first network element, the method comprising:

[0039] Send a first request to the second network element. The first request is used to subscribe to events of the localization reference unit (PRU) in the region and / or to subscribe to information of the PRU in the region.

[0040] In this embodiment of the disclosure, the first network element can subscribe to events and / or information of PRUs in the region by sending a first request to the second network element. When such events and / or PRU information change, the first network element can obtain the information of PRUs in the region through the subscription process without requesting the second network element, thereby saving the signaling overhead of the first network element in obtaining the information of PRUs in the region.

[0041] In conjunction with some embodiments of the first aspect, in some embodiments, the event includes at least one of the following:

[0042] PRUs exist in the region;

[0043] PRU is not present in the region;

[0044] PRU enters the area;

[0045] PRU leaves the area;

[0046] The information of PRU in the region has changed.

[0047] In this embodiment of the disclosure, the event includes: the presence of a PRU in the area; the first network element subscribes to the event, thereby enabling it to receive information about the PRU in the area from the second network element when the PRU is present in the area (i.e., the event has occurred);

[0048] The event includes: no PRU exists in the area. The first network element subscribes to the event, thereby being able to receive information about the PRU in the area from the second network element even when no PRU exists in the area (i.e., the event has occurred).

[0049] The event includes: a PRU entering the area; the first network element subscribes to the event, thereby enabling it to receive information about the PRU entering the area (i.e., the event occurs) from the second network element.

[0050] The events include: a PRU leaving the area. The first network element subscribes to the event, thereby enabling it to receive information about the PRUs in the area from the second network element when a PRU leaves the area (i.e., the event occurs).

[0051] The event includes: the information of the PRU in the area changes, and the first network element subscribes to the event so that it can receive the information of the PRU in the area from the second network element when the information of the PRU in the area changes (i.e. the event occurs);

[0052] In summary, in this embodiment of the present disclosure, the first network element can obtain the information of the PRU in the region by subscribing to the events of the PRU in the region. When an event occurs, it does not need to request the second network element every time, thus reducing the signaling overhead of the first network element.

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

[0054] Types of PRUs;

[0055] Location of PRU;

[0056] The first indication information is used to indicate whether a PRU exists in the area;

[0057] The second network element stores PRU information.

[0058] In this embodiment of the disclosure, the first network element can receive the PRU information in the region from the second network element when the PRU information in the region changes, without having to actively request the PRU information from the second network element every time the PRU information in the region changes, thereby reducing the signaling overhead of the first network element.

[0059] In conjunction with some embodiments of the first aspect, in some embodiments, the first request includes at least one of the following:

[0060] The second instruction information is used to instruct the first network element to request information about the PRU in the region;

[0061] The third instruction information is used to instruct the first network element to request information from the third network element;

[0062] Association relationship identifier, used to identify the association relationship between the third network element and the PRU;

[0063] Information about the third network element;

[0064] Information about the event;

[0065] Information about the region;

[0066] The third network element is the network element associated with the PRU.

[0067] In this embodiment, the first network element can indicate the information it requests to obtain through the second and third indication information; it can indicate the third network element associated with the PRU through the association identifier and the third network element information; the event information can indicate the specific content of the event subscribed to by the first network element, which helps determine whether the event has occurred; and the area information helps determine whether the event of the PRU in the area has occurred and whether the information of the PRU in the area has changed. In summary, by sending a first request including the above information, the first network element helps the second network element determine whether the event of the PRU in the area has occurred and whether the information of the PRU in the area has changed, and can also indicate the information requested by the first network element in the event of the PRU in the area and / or the change of the PRU information in the area.

[0068] In conjunction with some embodiments of the first aspect, in some embodiments, the information of the third network element includes at least one of the following:

[0069] Types of third network elements;

[0070] The identifier of the third network element;

[0071] The identifier of a network element set is used to indicate the network element set to which the third network element belongs.

[0072] In this embodiment of the disclosure, the information of the third network element can be used to indicate the third network element associated with the PRU.

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

[0074] Event identifier;

[0075] The conditions for triggering the event;

[0076] The object of the event.

[0077] In this embodiment of the disclosure, the event subscribed to by the first network element can be identified by the event identifier, the event triggering condition helps to determine whether the event subscribed to by the first network element has occurred, and the event object helps to identify the PRU that can trigger the event. In summary, the above event information indicates the relevant information of the event subscribed to by the first network element, which helps the second network element determine whether the event has occurred.

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

[0079] Receive a first response sent by the second network element, the first response being used to indicate the result of the first network element subscribing to the event and / or PRU information;

[0080] The result of the first network element subscription event and / or PRU information is that the subscription was successful; or the result of the first network element subscription event and / or PRU information is that the subscription failed.

[0081] In this embodiment of the disclosure, the first network element receives a first response, thereby enabling it to determine the result of the first network element subscribing to events and / or PRU information based on the first response.

[0082] In conjunction with some embodiments of the first aspect, in some embodiments, the first response is used to indicate that the first network element successfully subscribed to the event and / or PRU information, and the first response includes at least one of the following:

[0083] The identifier of the subscription;

[0084] Time information is used to indicate the valid period of information for the first network element's subscription events and / or PRUs;

[0085] The identifier of the third network element; the third network element is the network element that establishes an association with the PRU.

[0086] The second network element stores PRU information.

[0087] In this embodiment of the disclosure, if the first network element successfully subscribes to the event and / or PRU information, the first network element can manage the subscription based on the subscription identifier, determine the valid time period of the first network element's subscription to the event and / or PRU information based on the time information, determine the third network element associated with the PRU based on the identifier of the third network element, and obtain the PRU information stored in the second network element for model training or model performance monitoring.

[0088] In conjunction with some embodiments of the first aspect, in some embodiments, the first response is used to indicate that the first network element subscription event and / or PRU information failed, and the first response includes:

[0089] The fourth instruction information is used to indicate that the first network element subscription event and / or PRU information failed; and / or,

[0090] The reason for the failure of the first network element subscription event and / or PRU information.

[0091] In this embodiment of the disclosure, the first network element can determine the failure of the first network element to subscribe to the event and / or PRU information based on the fourth instruction information; the first network element can obtain the reason for the failure of the first network element to subscribe to the event and / or PRU information, which helps the first network element to make the next decision.

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

[0093] Receive a notification message sent by the second network element, the notification message being used to notify of an event occurring; and / or,

[0094] The information of PRU in the region has changed.

[0095] In this embodiment of the present disclosure, the first network element can learn that an event involving a PRU in the region has occurred and / or that the information of the PRU in the region has changed by receiving the notification message.

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

[0097] The types of changes in PRU information;

[0098] The identifier of the third network element; the third network element is the network element that establishes an association with the PRU.

[0099] Information about PRU;

[0100] Information after the PRU changes;

[0101] The fifth instruction is used to indicate that the information of the PRU has changed.

[0102] In this embodiment of the disclosure, through the above-mentioned content included in the notification message, the first network element can obtain the PRU information, the information after the PRU changes, and also know the changes in the PRU information, the type of changes in the PRU information, the identifier of the third network element, etc., thereby helping the first network element to complete the PRU data collection based on the above information.

[0103] In conjunction with some embodiments of the first aspect, in some embodiments, the types of variation include at least one of the following:

[0104] Add PRU information;

[0105] Update PRU information;

[0106] Delete PRU information.

[0107] In this embodiment of the disclosure, the first network element can know what type of change has occurred in the PRU information by the change type of the PRU information, thereby helping the first network element to update the PRU information according to the change type.

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

[0109] Send a second request to the second network element. The second request is used to request information on the unsubscribe event and / or PRU.

[0110] In this embodiment of the disclosure, when the first network element does not need to collect PRU information, the first network element can send a second request to the second network element to request unsubscribing from the event and / or PRU information, thereby reducing signaling overhead.

[0111] In conjunction with some embodiments of the first aspect, in some embodiments, the second request includes a subscription identifier, which is used to indicate the events and / or PRU information subscribed to by the first network element.

[0112] In this embodiment of the disclosure, the first network element can be instructed to cancel the subscription by using the subscription identifier.

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

[0114] Receive a second response sent by the second network element, the second response being used to instruct the first network element on the result of unsubscribing from the event and / or PRU information;

[0115] The result of the first network element's unsubscription event and / or PRU information is that the unsubscription was successful; or the result of the first network element's unsubscription event and / or PRU information is that the unsubscription failed.

[0116] In this embodiment of the disclosure, the first network element receives a second response, thereby being able to obtain the results of the first network element's unsubscription event and / or PRU information based on the second response, which helps the first network element make subsequent decisions based on the results of the first network element's unsubscription event and / or PRU information.

[0117] According to a second aspect of the embodiments of this disclosure, a subscription method is proposed, executed by a second network element, the method comprising:

[0118] Receive a first request sent by a first network element, the first request being used to subscribe to events of PRUs in the area, and / or to subscribe to information of PRUs in the area.

[0119] In this embodiment of the disclosure, the second network element can subscribe to the events and / or information of PRUs in the region by receiving a first request sent by the first network element. When the events and / or information of PRUs in the region change, the first network element does not need to request the second network element, and the second network element can actively send the information of the PRUs in the region to the first network element, thereby saving the signaling overhead of the second network element in sending the information of the PRUs in the region.

[0120] In conjunction with some embodiments of the second aspect, in some embodiments, the event includes at least one of the following:

[0121] PRUs exist in the region;

[0122] PRU is not present in the region;

[0123] PRU enters the area;

[0124] PRU leaves the area;

[0125] The information of PRU in the region has changed.

[0126] In this embodiment of the disclosure, the event includes: the presence of a PRU in the area; the first network element subscribes to the event; and when the presence of a PRU in the area (i.e., the occurrence of the event) occurs, the second network element can actively send information about the PRU in the area to the first network element.

[0127] The events include: if no PRU exists in the region, the first network element subscribes to the event, and if no PRU exists in the region (i.e., the event occurs), the second network element can proactively send information about the PRU in the region to the first network element;

[0128] The events include: a PRU entering the area; the first network element subscribes to the event, and when a PRU enters the area (i.e., the event occurs), the second network element can proactively send information about the PRU in the area to the first network element.

[0129] The events include: PRU leaving the area. The first network element subscribes to the event, and when a PRU leaves the area (i.e., the event occurs), the second network element can actively send the information of the PRU in the area to the first network element.

[0130] The events include: changes in PRU information in the region; when the information of the PRU in the region changes (i.e., the event occurs), the first network element subscribes to the event, and the second network element can proactively send the information of the PRU in the region to the first network element.

[0131] In summary, in this embodiment of the present disclosure, the first network element subscribes to the events of PRUs in the region. When an event occurs, the second network element can proactively send the information of the PRUs in the region to the first network element without having to request it from the second network element each time, thereby reducing the signaling overhead of the second network element.

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

[0133] Types of PRUs;

[0134] Location of PRU;

[0135] The first indication information is used to indicate whether a PRU exists in the area;

[0136] The second network element stores PRU information.

[0137] In this embodiment of the disclosure, the second network element subscribes to the information of PRUs in the aforementioned region. When the information of PRUs in the region changes, the second network element can proactively send the information of PRUs in the region to the first network element. The first network element does not need to proactively request the information of PRUs from the second network element every time the information of PRUs in the region changes, thereby reducing signaling overhead.

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

[0139] The second instruction information is used to instruct the first network element to request information about the PRU in the region;

[0140] The third instruction information is used to instruct the first network element to request information from the third network element;

[0141] Association relationship identifier, used to identify the association relationship between the third network element and the PRU;

[0142] Information about the third network element;

[0143] Information about the event;

[0144] Information about the region;

[0145] The third network element is the network element associated with the PRU.

[0146] In this embodiment, the second network element can obtain the information requested by the first network element through the second and third indication information; it can obtain the third network element associated with the PRU through the association identifier and the information of the third network element; it can obtain the specific content of the event subscribed to by the first network element through the event information, which helps the second network element determine whether the event has occurred; and it can determine whether the PRU event in the region has occurred and whether the PRU information in the region has changed by receiving the first request, which includes the above information. In summary, by receiving the first request, which includes the above information, the second network element can determine whether the PRU event in the region has occurred and whether the PRU information in the region has changed, and it can also indicate the information requested by the first network element in the case of the PRU event occurring and / or the PRU information in the region changing.

[0147] In conjunction with some embodiments of the second aspect, in some embodiments, the information of the third network element includes at least one of the following:

[0148] Types of third network elements;

[0149] The identifier of the third network element;

[0150] The identifier of a network element set is used to indicate the network element set to which the third network element belongs.

[0151] In this embodiment of the disclosure, the information of the third network element can be used to indicate the third network element associated with the PRU.

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

[0153] Event identifier;

[0154] The conditions for triggering the event;

[0155] The object of the event.

[0156] In this embodiment of the disclosure, the event subscribed to by the first network element can be identified by the event identifier, the event triggering condition helps to determine whether the event subscribed to by the first network element has occurred, and the event object helps to identify the PRU that can trigger the event. In summary, the above event information indicates the relevant information of the event subscribed to by the first network element, which helps the second network element determine whether the event has occurred.

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

[0158] Send a first response to the first network element. The first response is used to indicate the result of the first network element subscribing to the event and / or PRU information.

[0159] The result of the first network element subscription event and / or PRU information is that the subscription was successful; or the result of the first network element subscription event and / or PRU information is that the subscription failed.

[0160] In this embodiment of the disclosure, the second network element can instruct the first network element to subscribe to the information of the event and / or PRU by sending a first response.

[0161] In conjunction with some embodiments of the second aspect, in some embodiments, sending a first response to the first network element includes:

[0162] If the first request sent by the first network element is accepted, a first response is sent to the first network element. The first response is used to indicate that the first network element has successfully subscribed to the event and / or PRU information.

[0163] The first response includes at least one of the following:

[0164] The identifier of the subscription;

[0165] Time information is used to indicate the valid period of information for the first network element's subscription events and / or PRUs;

[0166] The identifier of the third network element; the third network element is the network element that establishes an association with the PRU.

[0167] The second network element stores PRU information.

[0168] In this embodiment of the disclosure, when the second network element determines that it accepts the first request, the second network element sends a first response to indicate that the first network element has successfully subscribed to the event and / or PRU information. Further, the first response includes a subscription identifier, which helps manage the subscription based on the subscription identifier; the first response includes time information, thereby indicating the valid period for the first network element to subscribe to the event and / or PRU information; the first response includes an identifier of a third network element, which can indicate the third network element associated with the PRU; the first response includes information about the PRU stored by the second network element, which helps in model training or model performance monitoring.

[0169] In conjunction with some embodiments of the second aspect, in some embodiments, sending a first response to the first network element includes:

[0170] If it is determined that the first request sent by the first network element is rejected, a first response is sent to the first network element. The first response is used to indicate that the first network element has failed to subscribe to the event and / or PRU information.

[0171] The first response includes:

[0172] The fourth instruction information is used to indicate that the first network element subscription event and / or PRU information failed; and / or,

[0173] The reason for the failure of the first network element subscription event and / or PRU information.

[0174] In this embodiment of the disclosure, the second network element can indicate to the first network element that the subscription event and / or PRU information failed according to the fourth indication information; the second network element can indicate the reason for the failure of the first network element to subscribe to the event and / or PRU information, which helps the first network element to make the next decision.

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

[0176] Send a notification message to the first network element, the notification message being used to notify that an event has occurred; and / or, the notification message being used to notify that the information of the PRU in the area has changed.

[0177] In this embodiment of the disclosure, the second network element can notify the first network element that an event of PRU in the region has occurred and / or that the information of PRU in the region has changed by sending the notification message.

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

[0179] The types of changes in PRU information;

[0180] The identifier of the third network element; the third network element is the network element that establishes an association with the PRU.

[0181] Information about PRU;

[0182] Information after the PRU changes;

[0183] The fifth instruction is used to indicate that the information of the PRU has changed.

[0184] In this embodiment of the disclosure, through the above-mentioned content included in the notification message, the first network element can obtain the PRU information, the information after the PRU changes, and also know the changes in the PRU information, the type of changes in the PRU information, the identifier of the third network element, etc., thereby helping the first network element to complete the PRU data collection based on the above information.

[0185] In conjunction with some embodiments of the second aspect, in some embodiments, the types of variation include at least one of the following:

[0186] Add PRU information;

[0187] Update PRU information;

[0188] Delete PRU information.

[0189] In this embodiment of the disclosure, the second network element indicates the type of change in the PRU information by the change type of the PRU information, thereby helping the first network element to update the PRU information according to the change type.

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

[0191] Receive a second request sent by the first network element. The second request is used to request information on the unsubscribe event and / or PRU.

[0192] In this embodiment of the disclosure, the second network element can learn that the first network element does not need to collect PRU information by receiving the second request sent by the first network element, and thus unsubscribe from the event and / or PRU information, thereby reducing signaling overhead.

[0193] In conjunction with some embodiments of the second aspect, in some embodiments, the second request includes a subscription identifier, which is used to indicate the events and / or PRU information subscribed to by the first network element.

[0194] In this embodiment of the disclosure, the first network element can be instructed to cancel the subscription by using the subscription identifier.

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

[0196] Send a second response to the first network element, the second response being used to instruct the first network element to unsubscribe from the event and / or the result of the PRU information;

[0197] The result of the first network element's unsubscription event and / or PRU information is that the unsubscription was successful; or the result of the first network element's unsubscription event and / or PRU information is that the unsubscription failed.

[0198] In this embodiment of the disclosure, the second network element can send a second response to instruct the first network element on the result of the unsubscription event and / or PRU information, which helps the first network element make subsequent decisions based on the result of the first network element's unsubscription event and / or PRU information.

[0199] According to a third aspect of the embodiments of this disclosure, a subscription device is provided, comprising:

[0200] The transceiver module is used to send a first request to the second network element. The first request is used to subscribe to events of PRUs in the area and / or to subscribe to information of PRUs in the area.

[0201] According to a fourth aspect of the embodiments of this disclosure, a subscription device is provided, comprising:

[0202] The transceiver module is used to receive a first request sent by a first network element. The first request is used to subscribe to events of PRUs in the area and / or to subscribe to information of PRUs in the area.

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

[0204] One or more processors;

[0205] The first network element is used to execute the method described in the optional implementation of the first aspect.

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

[0207] One or more processors;

[0208] The second network element is used to execute the method described in the optional implementation of the second aspect.

[0209] According to a seventh aspect of the embodiments of this disclosure, a subscription system is proposed, comprising: a first network element and a second network element;

[0210] 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.

[0211] According to an eighth 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 as described in an optional implementation of the second aspect.

[0212] According to a ninth 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.

[0213] It is understood that the aforementioned subscription device, communication equipment, storage medium, program product, computer program, and chip are all used to execute the methods proposed in the embodiments of this disclosure. Therefore, the beneficial effects they can achieve can be referred to the beneficial effects in the corresponding methods, and will not be repeated here.

[0214] This disclosure presents subscription methods, apparatus, devices, systems, storage media, and program products.

[0215] In some embodiments, the terms subscription method and communication method, subscription request sending method, transmission method, subscription request transmission method, etc., can be used interchangeably; the terms subscription device and communication device, subscription request sending device, transmission device, subscription request device method, etc., can be used interchangeably; and the terms subscription system and communication system, subscription request sending system, transmission system, subscription request transmission system, subscription request transmission system, etc., can be used interchangeably.

[0216] 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.

[0217] 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.

[0218] 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.

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

[0220] 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.

[0221] 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.

[0222] 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.

[0223] 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.

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

[0225] 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.

[0226] 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”.

[0227] 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.

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

[0229] 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.

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

[0231] In some embodiments, access network devices, core network devices, or network devices can be replaced with terminal devices. 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 terminal devices is replaced with communication between multiple terminal devices (e.g., device-to-device (D2D), vehicle-to-everything (V2X), etc.). In this case, the terminal devices can also be configured to have all or part of the functions of the access network devices. Furthermore, terms such as "uplink" and "downlink" can be replaced with terms corresponding to communication between terminal devices (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.

[0232] In some embodiments, the terminal device 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 device.

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

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

[0235] 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.

[0236] Figure 1a is a schematic diagram of the architecture of a communication system according to an embodiment of the present disclosure. As shown in Figure 1a, the communication system 100 includes a PRU 101, an access network device 102, and a core network device 103.

[0237] In some embodiments, PRU101 may be a terminal device. In some embodiments, the terminal device 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 device, augmented reality (AR) terminal device, wireless terminal device in industrial control, wireless terminal device in self-driving, wireless terminal device in remote medical surgery, wireless terminal device in smart grid, wireless terminal device in transportation safety, wireless terminal device in smart city, and wireless terminal device in smart home.

[0238] In some embodiments, the access network device 102 may be a node or device that connects a terminal device 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 radio 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.

[0239] 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.

[0240] 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.

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

[0242] 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.

[0243] The following embodiments of this disclosure can be applied to the communication system 100 shown in FIG1a, or to some of the main bodies, but are not limited thereto. The main bodies shown in FIG1a are illustrative. The communication system may include all or some of the main bodies in FIG1a, or it may include other main bodies outside of FIG1a. The number and form of each main body are arbitrary. Each main body may be physical or virtual. The connection relationship between the main bodies is illustrative. The main bodies may not be connected or may be connected. The connection may be in any way, such as direct connection or indirect connection, wired connection or wireless connection.

[0244] 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), Future generation 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).

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

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

[0247] Figure 1b is an exemplary interactive diagram of the PRU association process provided in an embodiment of this disclosure. The PRU association process can be an initial PRU association between a PRU and a first 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 first LMF network element of the PRU's continued availability, or notifying the first LMF network element of changes in the PRU's positioning capabilities.

[0248] 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 first LMF element; for subsequent PRU association update processes, the route ID is the route ID of the first LMF element that the PRU has already obtained during the previous PRU association process.

[0249] 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 strand (NAS) messages sent between PRU and AMF network elements through the N1 reference point.

[0250] 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.

[0251] As shown in Figure 1b, the steps include:

[0252] Step S1201: Trigger a service request.

[0253] 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.

[0254] 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.

[0255] 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.

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

[0257] 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).

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

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

[0260] PRU ON / OFF state.

[0261] 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.

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

[0263] 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.

[0264] 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.

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

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

[0267] After the AMF network element selects the first LMF network element, the AMF network element uses the Namf_Communication_N1MessageNotify service operation to send the PRU association request to the first 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.

[0268] Steps S1205-S1206 represent the situation where the first LMF network element accepts PRU association.

[0269] In step S1205, the first 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.

[0270] If the first LMF network element accepts the PRU association, then the first LMF network element 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 first LMF network element and is used to identify the first LMF network element and the optional PRU.

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

[0272] 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.

[0273] 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 the first LMF network element. If the PRU previously stored a route ID, the route ID in the DL NAS TRANSPORT can overwrite the route ID previously stored by the PRU.

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

[0275] In step S1207, the first 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.

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

[0277] 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.

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

[0279] If the PRU is successfully associated with the first LMF network element, the first LMF network element can verify the PRU's location and perform a positioning operation to obtain a more precise location for the PRU. The first LMF 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 first LMF network element can consider the previously verified PRU location to be valid.

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

[0281] If the PRU is successfully associated with the first 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 first LMF network element also instructs the NRF network element to remove the PRU associated with the TAI when there is no longer a PRU 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 first LMF network element synchronizes the PRU information to the NRF network element, so other network elements can also learn about the existence of this PRU and the first LMF network element associated with this PRU through the NRF network element.

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

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

[0284] If the first LMF element rejects the 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.

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

[0286] 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.

[0287] Figure 1c is a flowchart of data collection by an LMF network element according to an embodiment of this disclosure. As shown in Figure 1c, it includes the following steps:

[0288] Step S1301: The second LMF network element determines that it needs to collect data from terminal devices in the region of interest.

[0289] Data collection by the second LMF network element refers to the collection of measurement data and tag data from terminal devices in the region of interest. This measurement and tag data can also be referred to as terminal device information. Terminal device measurement data may include, for example, the terminal device's location, type, and the power of its transmitted positioning reference signal, etc. Terminal device tag data is real-world data, such as the terminal device's actual location.

[0290] Terminal equipment includes terminal equipment that can function as a PRU and terminal equipment that cannot function as a PRU. Terminal equipment that can function as a PRU can also be called a PRU. For a PRU, the second LMF network element needs to collect the PRU's information.

[0291] The process of determining that the second LMF element needs to collect data can be actively triggered by the second LMF element. For example, if the second LMF element needs to train an AI / ML model or detects that the performance of the AI / ML model is poor, the second LMF element needs to collect data in order to train the AI / ML model based on the collected data.

[0292] The process by which the second LMF element determines that data collection is required can be triggered by the Network Data Analytics Function (NWDAF) element. For example, the NWDAF element sends a request message to the second LMF element to request the initiation of data collection.

[0293] Step S1302: The second LMF network element searches for the serving AMF network element in the region of interest.

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

[0295] In some embodiments, the second LMF network element may not know the SUPI of the terminal devices in the region of interest. The second 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 devices from the AMF network element.

[0296] In step S1303, the second LMF network element sends a request message to the AMF network element. The request message is used to request the SUPI list of terminal devices in the region of interest.

[0297] 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 device, and the event can be a terminal device entering or leaving the area of ​​interest. Through this request message, the second LMF network element requests the SUPI list of terminal devices in the area of ​​interest from the AMF network element.

[0298] In step S1304, the AMF network element sends a response message to the second LMF network element, the response message including a list of SUPIs of terminal devices in the region of interest.

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

[0300] Step S1305: The second LMF network element checks whether the terminal devices in the SUPI list agree to data collection.

[0301] The second LMF network element can check whether the terminal devices in the SUPI list agree to data collection by requesting the UDM network element. The collected data is used to train the AI / ML model. For any terminal device in the SUPI list, if the terminal device agrees to data collection, step S1306 is executed; if the terminal device does not agree to data collection, the second LMF network element does not execute step S1306 for the terminal device UE, and the terminal device will not participate in data collection, and its data will not be used to train the AI / ML model.

[0302] In step S1306, if the terminal device agrees to data collection, the second LMF network element requests measurement data from the terminal device from the NG-RAN or the terminal device.

[0303] In some embodiments, the terminal device can send its measurement data to the second LMF network element via NG-RAN pass-through; NG-RAN can also obtain the terminal device's measurement data through interaction with the terminal device, and then send the terminal device's measurement data to the second LMF network element.

[0304] Step S1307: The second LMF network element obtains the tag data corresponding to the measurement data from the terminal device.

[0305] After receiving measurement data and label data, the second LMF network element can train an AI / ML model based on the measurement data and label data.

[0306] Based on the above process, after successfully executing the PRU association process, the second LMF network element can update the PRU information by calling the Nnrf_NFManagement_NFUpdate service request operation to the NRF network element. During data collection, the second LMF network element can call the Nnrf_NFDiscovery service request operation to the NRF network element to obtain relevant information about PRUs within a specific area, such as PRU presence indications or the PRU's serving LMF.

[0307] However, the second LMF network element requests relevant information about PRUs within the area from the NRF network element during each data collection process, resulting in significant signaling overhead. Furthermore, during PRU association and deassociation processes, PRU information may be updated, further increasing signaling overhead.

[0308] Based on this, this disclosure provides a subscription method in which a first network element subscribes to events and / or information of PRUs in a region by sending a first request to a second network element. When such events and / or PRU information change, the first network element can obtain the information of the PRUs in the region through the subscription process without having to request it from the second network element, thus saving signaling overhead.

[0309] Figure 2a is an exemplary interactive schematic diagram of a subscription method provided in an embodiment of this disclosure. Referring to Figure 2a, the method includes:

[0310] In step S2101, the first network element sends a first request to the second network element. The first request is used to subscribe to the events of the PRU in the area.

[0311] In some embodiments, the first network element can be a network element with positioning management capabilities, such as a second LMF network element. In some embodiments, the first network element can also be a network element with sensing capabilities, such as a sensing function (SF) network element. In some scenarios, the first 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 terminal devices. In some embodiments, PRU information can also be referred to as PRU data.

[0312] In some embodiments, the second network element can be a network element responsible for the registration, discovery, and selection of network functions, such as an NRF network element. Each network function entity can register with the second network element, through which each network function can easily find and connect to the required services.

[0313] The first network element sends a first request to the second network element, and subscribes to the PRU events in the area through the first request; correspondingly, the second network element receives the first request sent by the first network element, and can learn about the PRU events in the area subscribed by the first network element through the first request.

[0314] In some embodiments, a PRU can be a type of terminal device. For certain terminal devices, if a terminal device has the function of a PRU, then the terminal device can be called a PRU.

[0315] This area can also be called the region of interest. In some embodiments, if the first network element needs to collect relevant data of a certain region of interest A, it can send a first request to the second network element to subscribe to the events of the PRU in region A.

[0316] The events of PRUs in this region refer to events related to PRUs in this region.

[0317] In some embodiments, the first request may also be referred to as a first request message, subscription message, subscription request, subscription request message, etc., for example, it may be an Nnrf_NFManagement_NFStatusSubscriberequest message.

[0318] In some embodiments, the events of the PRU in this region include at least one of the following 1.1 to 1.5:

[0319] 1.1. PRU exists in this area.

[0320] Events related to PRUs in a region include: if a PRU exists in the region, then the occurrence of the event can be determined if one or more PRUs exist in the region. If a first network element subscribes to the event from a second network element via a first request, then the second network element can determine whether the event has occurred if the subscription to the event is successful.

[0321] In some embodiments, the second network element can obtain the location range of the area and the location of each PRU, and then determine whether there is a PRU in the area by combining the location range of the area and the location of each PRU.

[0322] In some embodiments, the location range of the area may be pre-stored in the second network element, or it may be indicated to the second network element by the first network element (e.g., the location of the area may be included in the first request), or other possible methods, which are not limited in this disclosure. In some embodiments, the location range of the area may be represented by one or more cell IDs or TAI (Tracking Area Identity), or other possible methods, which are not limited in this disclosure.

[0323] In some embodiments, for any given PRU, the second network element can obtain the location of the PRU from the serving network element of that PRU. For example, during the PRU association process and the PRU association update process, the serving network element of the PRU can obtain the location of the PRU and send it to the second network element. In some embodiments, the PRU association process can be described with reference to the flowchart shown in FIG1b.

[0324] For example, if there are no PRUs in the region at time t1, and a PRU enters the region from outside at time t2, then the second network element can determine that the event occurred at time t2.

[0325] 1.2. PRU does not exist in this region.

[0326] Events related to PRUs in a region include: if no PRU exists in the region, then the event can be determined to have occurred. If the first network element subscribes to the event from the second network element via a first request, then if the subscription to the event is successful, the second network element can determine whether the event has occurred.

[0327] In some embodiments, the second network element can obtain the location range of the area and the location of each PRU, and then determine whether a PRU exists in the area by combining the location range of the area and the location of each PRU. The implementation method of the second network element obtaining the location range of the area and the location of each PRU can be found in the relevant description in step 1.1 of S2101, and will not be repeated here.

[0328] For example, if PRU1 and PRU2 are included in the region at time t1, and both PRU1 and PRU2 leave the region at time t2, and no PRUs remain in the region after time t2, then the second network element can determine that the event occurred at time t2.

[0329] 1.3 PRU enters the area.

[0330] Events for PRUs within a region include: if a PRU enters the region, then the event can be determined to have occurred if one or more PRUs enter the region from outside. If a first network element requests subscription to the event from a second network element via a first request, then the second network element can determine whether the event has occurred if the subscription is successful.

[0331] In some embodiments, the second network element can obtain the location range of the area and the location of each PRU, and then determine whether any PRU has entered the area by combining the location range of the area and the location of each PRU. The implementation method of the second network element obtaining the location range of the area and the location of each PRU can be found in the relevant description in step 1.1 of S2101, and will not be repeated here.

[0332] For example, if PRU1 is in the region at time t1 and PRU2 is outside the region, and PRU2 enters the region at time t2, then the second network element can determine that the event occurred at time t2.

[0333] 1.4. PRU leaves the area.

[0334] Events for PRUs within a region include: PRUs leaving the region; if one or more PRUs leave the region, the event can be determined to have occurred. If a first network element subscribes to the event from a second network element via a first request, and the subscription is successful, the second network element can determine whether the event has occurred.

[0335] In some embodiments, the second network element can obtain the location range of the area and the location of each PRU, and then determine whether any PRU has left the area by combining the location range of the area and the location of each PRU. The implementation method of the second network element obtaining the location range of the area and the location of each PRU can be found in the relevant description in step 1.1 of S2101, and will not be repeated here.

[0336] For example, if PRU1 and PRU2 are included in the region at time t1, and PRU2 leaves the region at time t2, then the second network element can determine that the event occurred at time t2.

[0337] 1.5 The PRU information in this area has changed.

[0338] The information of PRUs in the region changes, meaning that the information of PRUs in the region is updated. For example, the number of PRUs in the region changes (this could be due to PRUs leaving the region or PRUs entering the region), the service AMF of the PRUs in the region changes, the PRU subscription information in the region changes, the location, type, and other information of the PRUs in the region changes, and so on.

[0339] In some embodiments, the PRU information includes at least one of the following 2.1 to 2.4:

[0340] 2.1 Types of PRUs.

[0341] In some embodiments, PRUs can be categorized into fixed PRUs and mobile PRUs based on their deployment method.

[0342] A fixed PRU refers to a PRU whose installation location is fixed and remains unchanged over a long period. A mobile PRU refers to a PRU whose installation location is not fixed and can change dynamically; a mobile PRU can also be called a non-fixed PRU.

[0343] 2.2 The location of PRU.

[0344] 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-defined and identified by different IDs). In some embodiments, the PRU's location can also be characterized by its relative position to a reference point, such as a terminal device, a base station, a fixed building, etc.

[0345] 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.

[0346] 2.3 First indication information, used to indicate whether a PRU exists in the area.

[0347] The first indication information, also known as the PRU indication, is used to indicate whether a PRU exists in the area. The process for determining whether a PRU exists in the area can be found in the relevant descriptions in steps 1.1 or 1.2 of S2101, and will not be repeated here.

[0348] 2.4 Information of PRU stored in the second network element.

[0349] The PRU information stored in the second network element can be information on all PRUs stored in the second network element, or information on some PRUs stored in the second network element.

[0350] For any PRU, its information can be sent from the serving network element to the second network element, and the second network element can store the information upon receiving it. For example, during the initial association process or association update process of the PRU, the PRU successfully establishes an association with the serving network element, and then the serving network element can send the PRU's information to the second network element, which then stores the PRU's information.

[0351] For any PRU, the information stored in the second network element may include one or more of the following: the type of the PRU, the location of the PRU, the ON / OFF status of the PRU, the serving network element of the PRU, etc.

[0352] In the above embodiments, the events and information of PRUs in the region are described. The first request is used to subscribe to the events of PRUs in the region. The contents included in the first request will be described below.

[0353] In some embodiments, the first request includes at least one of the following 3.1 to 3.4:

[0354] 3.1 The second instruction information is used to instruct the first network element to request information about the PRU in the area.

[0355] If the first request includes the second instruction information, the second network element can obtain the second instruction information upon receiving the first request, and based on the second instruction information, know that the first network element is requesting information about the PRUs in that area. The second network element can respond to the first network element's request and send the information about the PRUs in that area to the first network element.

[0356] 3.2 The third instruction information is used to instruct the first network element to request information from the third network element.

[0357] The third 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 third network element by initiating an initial PRU association process or by initiating a PRU association update process.

[0358] The information of the third network element refers to information related to the third network element, such as information used to instruct the third network element. If the first request includes third instruction information, the second network element can obtain the third instruction information upon receiving the first request and, based on the third instruction information, know that the first network element requested the information of the third network element. The second network element can respond to the request of the first network element and send the information of the third network element to the first network element. The information of the third network element can be found in the relevant description in 3.4 below.

[0359] 3.3 Association Relationship Identifier, used to identify the association relationship between the third network element and the PRU.

[0360] In some embodiments, the association identifier can be used to identify a third network element, and / or the association relationship between the third network element and the PRU. The third network element is the network element associated with the PRU. A description of the third network element can be found in the relevant content of 3.2 in step S2101, and will not be repeated here.

[0361] In some embodiments, the correlation identifier can be a session or service identifier used to identify a session or service. The correlation identifier can be a correlation ID or an analytics ID, and can be used to identify sessions used for AI, sessions used for location, sessions used for perception, etc. For example, an analytics ID is used to identify sessions used for AI; a correlation ID is used to identify sessions used for location and / or perception.

[0362] 3.4 Information about the third network element.

[0363] A third network element is a network element associated with a PRU, or a network element that has established an association with a PRU. Information about a third network element refers to information related to that third network element, such as information used to indicate the third network element.

[0364] In some embodiments, the first request may include information about a third network element. After receiving the first request, the second network element can obtain the information about the third network element and determine the third network element based on the information about the third network element.

[0365] In some embodiments, the information of the third network element includes at least one of the following:

[0366] a. Types of third network elements.

[0367] The type of the third network element can be, for example, the NF type of the third network element. For example, the type of the third network element can be the LMF network element type, or the sensing network element type, etc.

[0368] b. Identification of the third network element.

[0369] The identifier of a third network element can be, for example, the NF instance ID of the third network element, or any other information that can be used to identify the third network element.

[0370] In some embodiments, if the area includes multiple PRUs, and each PRU can have an associated third network element, the identifiers of the third network elements associated with each of the multiple PRUs can be represented in the form of an identifier list. For example, the identifiers of the third network elements can include an ID list, which includes the IDs of the third network elements associated with each of the multiple PRUs.

[0371] c. The identifier of the network element set, used to indicate the network element set to which the third network element belongs.

[0372] The identifier of a network element set can be, for example, the ID of an NF set, or any other information that can be used to indicate the network element set to which a third network element belongs. For different PRUs, the third network elements associated with different PRUs can belong to the same network element set or to different network element sets.

[0373] 3.5. Information about the event.

[0374] This event is a subscription event of the first network element. For a description of the event, please refer to the relevant content in steps 1.1 to 1.5 of S2101, which will not be repeated here.

[0375] Event information refers to information related to the event. In some embodiments, event information includes at least one of the following data types:

[0376] d. Event identifier.

[0377] An event identifier is used to indicate the event; different events have different identifiers, and the event identifier can also be called the event ID. If the first request includes an event identifier, the second network element can obtain the event identifier after receiving the first request, and can identify the event based on the event identifier.

[0378] e. The conditions that trigger the event.

[0379] The triggering conditions of an event are certain conditions that trigger the event. Based on the triggering conditions, it can be determined whether the event has occurred. If the first request includes the event triggering conditions, the second network element can obtain the event triggering conditions after receiving the first request, and determine whether the event has occurred based on the event triggering conditions.

[0380] For example, if the event is that a PRU enters the area, the triggering condition for the event could be that the distance between the PRU and a reference point in the area is less than or equal to a preset distance threshold. If the distance between a PRU and a reference point in the area is less than or equal to the preset distance threshold, then the PRU is considered to have entered the area, and the event has occurred.

[0381] f. The object of the event.

[0382] The object of an event can also be called the target of the event, the event reporting target, etc. The object of an event refers to the object that can trigger the event, such as a PRU that can trigger the event.

[0383] For example, if the object of the event is "any PRU", it means that any PRU may trigger the event; if the object of the event is "mobile PRU", it means that a mobile PRU can trigger the event, and so on.

[0384] 3.6. Information about the region.

[0385] The information about the region can be, for example, information indicating the region's location. This information can be characterized by various parameters, such as one or more cell IDs, TAIs, or the region's shape and coordinate range. If the first request includes the region's location, the second network element can obtain the region's location upon receiving the first request.

[0386] In some embodiments, the location of the area obtained by the second network element helps it determine whether a PRU exists in the area, whether the information of the PRU in the area has changed, whether a PRU has entered / left the area, and so on. Furthermore, obtaining the location of the area helps the second network element determine whether the event has occurred.

[0387] In step S2102, the second network element determines that it will accept the first request sent by the first network element.

[0388] After receiving the first request from the first network element, the second network element determines whether to accept the first request. Upon receiving the first request, the second network element is aware that the first network element has subscribed to the event. The second network element may accept or reject the subscription request from the first network element.

[0389] In step S2103, the second network element sends a first response to the first network element. The first response is used to indicate the result of the first network element's subscription event; the result of the first network element's subscription event is that the subscription was successful.

[0390] If the result of the first network element's subscription event is a successful subscription, the second network element sends a first response to the first network element. The first response is used to instruct the first network element to subscribe to the result of the event.

[0391] For example, if the second network element determines that it accepts the first request sent by the first network element (i.e., the second network element accepts the subscription requested by the first network element), the second network element sends a first response to the first network element. The first response indicates that the first network element has successfully subscribed to the event. Optionally, the first response includes a first event report, for example, information about the PRU stored by the second network element. Accordingly, the first network element receives the first response sent by the second network element, and can know from the first response that the first network element has successfully subscribed to the event.

[0392] In some embodiments, if the first network element successfully subscribes to the event, the first response includes at least one of the following 4.1 to 4.4:

[0393] 4.1 Subscription identifier.

[0394] The subscription identifier, also known as subscription ID, subscription identifier, subscription event identifier, etc., is used to uniquely identify the subscription requested by the first network element. If the first network element successfully subscribes to the event, the second network element can generate the subscription identifier and send it to the first network element, which can then manage the subscription based on this identifier.

[0395] For example, if a first network element wishes to unsubscribe from an event, it can send a request to a second network element to request unsubscribing from that event. This request can include an identifier of the subscription. Upon receiving the request, the second network element can obtain the subscription identifier and thus determine that the first network element requested to unsubscribe from that event.

[0396] For example, if a first network element wants to update the validity period of its subscription to an event, it can send a request to a second network element to request the update. This request may include the subscription identifier and the updated validity period. Upon receiving the request, the second network element can obtain the subscription identifier and the updated validity period, thus knowing that the first network element requested an update to the validity period of the event.

[0397] 4.2 Time information, used to indicate the valid period of the first network element's subscription to the event.

[0398] If the first network element successfully subscribes to the event, the second network element can instruct the first network element to subscribe to the valid period of the event. That is, the first network element's subscription to the event is valid within the valid period. If the event occurs within the valid period, the second network element will send relevant information to the first network element; if the event occurs outside the valid period, the second network element may not send relevant information to the first network element because the first network element's subscription to the event may expire.

[0399] Time information is used to indicate the valid period of subscription to the event. For example, time information may include at least one of the following: the start time of the valid period, the end time of the valid period, the duration of the valid period, etc.

[0400] 4.3 Identification of the third network element: The third network element is the network element that establishes an association with the PRU.

[0401] The identifier of the third network element can be found in section 3.4b of step S2101, and will not be repeated here. If the first network element successfully subscribes to the event, the second network element can send a first response to the first network element, which includes the identifier of the third network element. Upon receiving the first response, the first network element can obtain the identifier of the third network element and determine the third network element associated with the PRU based on this identifier.

[0402] 4.4 Information of PRU stored in the second network element.

[0403] The information about the PRUs stored in the second network element can be found in step 2.4 of S2101, and will not be repeated here. If the first network element successfully subscribes to the event, the second network element can send a first response to the first network element. The first response includes a first event report, for example, information about the PRUs stored in the second network element. Upon receiving the first response, the first network element can obtain the information about the PRUs stored in the second network element.

[0404] In some embodiments, the first response may also be referred to as a subscription response message, subscription response, etc., for example, it may be the Nnrf_NFManagement_NFStatusSubscriberesponse message.

[0405] For the service network element and RPU to perform the association / deassociation process, after the PRU association / deassociation process, the service network element calls Nnrf_NFManagement_NFUpdate to the NRF network element to request service operation, including an indication of the existence of the PRU associated with the TAI.

[0406] In step S2104, if an event of subscription by the first network element is detected, the second network element sends a notification message to the first network element to notify that the event has occurred.

[0407] If the first network element successfully subscribes to the event, the second network element can detect whether the event subscribed to by the first network element has occurred. If the second network element detects that the event subscribed to by the first network element has occurred, the second network element sends a notification message to the first network element to notify that the event has occurred; correspondingly, the first network element receives the notification message sent by the second network element and can know that the event has occurred based on the notification message.

[0408] In some embodiments, the notification message may also be called a status notification message, such as the Nnrf_NFManagement_NFStatusNotify message.

[0409] In some embodiments, the notification message includes at least one of the following 5.1 to 5.5:

[0410] 5.1. Types of changes in PRU information.

[0411] In the event of this incident, the PRU information may change. If the second network element detects this event, it can send a notification message to the first network element, including the type of change in the PRU information.

[0412] In some embodiments, the change type of PRU information includes at least one of the following gi:

[0413] g. Add PRU information.

[0414] Adding PRU information refers to adding additional PRU information to the existing PRU information. This can be due to the addition of new PRUs to the region, and the added PRU information can fall under the category of "adding PRU information." For example, adding PRU information could be due to the addition of new PRU information to the region.

[0415] For example, the area originally included PRU1 and PRU2. PRU1's information included its type, and PRU2's information included its location and type. For PRU1, if the serving network element of PRU1 reported its location to the second network element, then PRU1's location is newly added information; this case falls under the category of adding PRU information. Similarly, if PRU3 enters the area, then PRU3's information is newly added information; this case also falls under the category of adding PRU information.

[0416] h. Update PRU information.

[0417] Updating PRU information refers to updating certain information based on the existing PRU information.

[0418] For example, this area includes PRU1, and the information of PRU1 includes its location. For PRU1, if the serving network element of PRU1 locates PRU1, obtains the updated location of PRU1, and reports the updated location of PRU1 to the second network element, then the updated location of PRU1 is updated information, and this situation belongs to the case where the change type is updated PRU information.

[0419] i. Delete PRU information.

[0420] Deleting PRU information refers to deleting some existing PRU information.

[0421] For example, this area originally included PRU1, and the information for PRU1 included its type and location. If the type of PRU1 is deleted, then the type of PRU1 becomes the deleted information, which is a case where the change type is the deletion of PRU1 information.

[0422] 5.2 Identification of the third network element: The third network element is the network element that establishes an association with the PRU.

[0423] The identification of the third network element can be found in the relevant content of item b in step S2101, 3.4, which will not be repeated here.

[0424] When the second network element detects the occurrence of this event, it can send a notification message to the first network element, which includes the identifier of the third network element. Upon receiving the notification message, the first network element can obtain the identifier of the third network element and determine the third network element associated with the PRU based on the identifier.

[0425] 5.3 PRU Information.

[0426] The PRU information refers to the information of the PRU before the change. For example, if the area originally included PRU1 and PRU2, and the information of PRU1 included the type of PRU1, and the information of PRU2 included the location and type of PRU2, then the PRU information includes: the type of PRU1, the location of PRU2, and the type of PRU2.

[0427] If the second network element detects the occurrence of this event, it can send a notification message to the first network element, which includes the PRU information. Upon receiving the notification message, the first network element can obtain the PRU information.

[0428] 5.4 Information after the PRU changes.

[0429] The information after a change in PRU refers to the information about the PRU obtained after the information about the PRU has changed.

[0430] For example, if the area originally included PRU1 and PRU2, and PRU1's information included its type, while PRU2's information included its location and type, then the PRU information would include: PRU1's type, PRU2's location, and PRU2's type. If the serving network element of PRU1 reports PRU1's location to the second network element, then PRU1's location is newly added information. Therefore, the PRU information after the change would include: PRU1's type, PRU1's location, PRU2's location, and PRU2's type.

[0431] If the second network element detects the occurrence of this event, it can send a notification message to the first network element, which includes information about the changed PRU. Upon receiving this notification message, the first network element can obtain the changed PRU information.

[0432] 5.5 The fifth instruction information is used to indicate that the information of the PRU has changed.

[0433] Upon detecting the event, the second network element can send a notification message to the first network element, which includes the fifth indication information. Upon receiving this notification message, the first network element can obtain the fifth indication information and, based on it, determine that the PRU information has changed.

[0434] In some embodiments, if the first network element determines that it needs to collect PRU information, for example, to collect PRU information for training an AI / ML model, and if the first network element knows the SUPI of these PRUs, the first network element identifies the serving network element of the PRU, which is associated with the PRUs in the TAI list (or AoI) received and stored from the NRF network element in step S2103 or step S2104.

[0435] In step S2105, the first network element sends a second request to the second network element, the second request being used to request unsubscribe from the event.

[0436] In some cases, if the first network element does not need to obtain the PRU information in the area, the first network element can send a second request to the second network element to request the second network element to unsubscribe from the PRU events in the area; correspondingly, the second network element receives the second request sent by the first network element and can learn from the second request that the first network element has requested to unsubscribe from the PRU events in the area.

[0437] In some embodiments, the second request includes a subscription identifier, which is used to indicate the event subscribed to by the first network element. The second network element can determine, based on the subscription identifier, that the first network element is requesting to unsubscribe from the event.

[0438] In some embodiments, the second request may also be referred to as an unsubscribe message, an unsubscribe request message, etc., for example, it may be an Nnrf_NFManagement_NFStatusUnsubscriberequest message.

[0439] In step S2106, the second network element sends a second response to the first network element. The second response is used to instruct the first network element to unsubscribe from the event. The result of the first network element unsubscribing from the event is either successful unsubscription or unsubscription failure.

[0440] After receiving the second request from the first network element, the second network element is aware that the first network element is requesting to unsubscribe from the event. The second network element may accept or reject the first network element's request to unsubscribe. Then, the second network element sends a second response to the first network element, which indicates the result of the first network element's unsubscription of the event.

[0441] In some embodiments, the second response may also be called an unsubscribe response message, such as the Nnrf_NFManagement_NFStatusUnsubscriberesponse message.

[0442] The subscription method involved in the embodiments of this disclosure may include at least one of steps S2101 to S2106. For example, step S2101 may be implemented as a standalone embodiment, step S2101+S2102+S2103 may be implemented as a standalone embodiment, step S2101+S2102+S2103+S2104 may be implemented as a standalone embodiment, step S2101+S2102+S2103+S2104+S2105 may be implemented as a standalone embodiment, and step S2101+S2102+S2103+S2104+S2105+S2106 may be implemented as a standalone embodiment, but is not limited thereto.

[0443] In some embodiments, steps S2103 and S2104 may be performed in an alternate order or simultaneously, and steps S2104 and S2105 may be performed in an alternate order or simultaneously. Steps S2102, S2103, S2104, S2105, and S2106 are optional, and one or more of these steps may be omitted or substituted in different embodiments.

[0444] 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.

[0445] Figure 2b is an exemplary interactive schematic diagram of a subscription method provided in an embodiment of this disclosure. Referring to Figure 2b, the method includes:

[0446] Step S2201: The first network element sends a first request to the second network element. The first request is used to subscribe to the events of the PRU in the area.

[0447] The implementation method of step S2201 can be found in the relevant introduction of step S2101 in Figure 2a, which will not be repeated here.

[0448] In step S2202, the second network element determines to reject the first request sent by the first network element.

[0449] After receiving the first request from the first network element, the second network element can know that the first network element has subscribed to the event. The second network element may accept or reject the subscription request from the first network element.

[0450] In step S2203, the second network element sends a first response to the first network element. The first response is used to indicate the result of the first network element's subscription event; the result of the first network element's subscription event is that the subscription failed.

[0451] If the result of the first network element's subscription event is that the subscription fails, the second network element sends a first response to the first network element. The first response is used to instruct the first network element to subscribe to the result of the event.

[0452] For example, if the second network element determines that it rejects the first request sent by the first network element (i.e., the second network element rejects the subscription requested by the first network element), the second network element sends a first response to the first network element. The first response indicates that the first network element's subscription to the event has failed. Accordingly, the first network element receives the first response sent by the second network element, and can know from the first response that the first network element's subscription to the event has failed.

[0453] In some embodiments, if the first network element fails to subscribe to the event, the first response includes at least one of the following 6.1 to 6.2:

[0454] 6.1 The fourth instruction message is used to indicate that the first network element failed to subscribe to the event.

[0455] If the first network element fails to subscribe to the event, the second network element can send a first response to the first network element, which includes a fourth indication message. Upon receiving the first response, the first network element can obtain the fourth indication message and determine from it that the first network element's subscription to the event has failed.

[0456] 6.2 The reason why FirstNetElement failed to subscribe to this event.

[0457] The reason why the first network element failed to subscribe to the event can also be called the reason for failure, the reason for rejection, etc. If the first network element fails to subscribe to the event, the second network element can send a first response to the first network element, which includes the reason why the first network element failed to subscribe to the event. Upon receiving the first response, the first network element will know the reason why it failed to subscribe to the event.

[0458] The subscription method involved in the embodiments of this disclosure may include at least one of steps S2201 to S2203. For example, step S2201 may be implemented as a standalone embodiment, and step S2201 + step S2202 + step S2203 may be implemented as a standalone embodiment, but is not limited thereto.

[0459] In some embodiments, steps S2202 and S2203 are optional, and one or more of these steps may be omitted or substituted in different embodiments.

[0460] 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.

[0461] Figure 2c is an exemplary interactive schematic diagram of a subscription method provided in an embodiment of this disclosure. Referring to Figure 2c, the method includes:

[0462] Step S2301: The first network element sends a first request to the second network element. The first request is used to subscribe to PRU information in the region.

[0463] In some embodiments, the first network element can be a second LMF network element or a sensing function network element; the second network element can be, for example, an NRF network element.

[0464] The first network element sends a first request to the second network element, and subscribes to the PRU information in the area through the first request; correspondingly, the second network element receives the first request sent by the first network element, and can learn the PRU information in the area subscribed by the first network element through the first request.

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

[0466] For information about the PRU, please refer to steps 2.1 to 2.4 in step S2101 of Figure 2a. For information about the first request, please refer to steps 3.1 to 3.4 in step S2101 of Figure 2a. These details will not be repeated here.

[0467] In step S2302, the second network element determines that it will accept the first request sent by the first network element.

[0468] After receiving the first request from the first network element, the second network element can obtain the PRU information in the first network element's subscription area. The second network element may accept or reject the subscription request from the first network element.

[0469] In step S2303, the second network element sends a first response to the first network element. The first response is used to indicate the result of the first network element subscribing to the PRU information; the result of the first network element's subscription event is that the subscription is successful.

[0470] After receiving the first request from the first network element, the second network element can learn about the first network element's subscription to PRU information. The second network element may accept or reject the subscription request from the first network element. Then, the second network element sends a first response to the first network element, which indicates the result of the first network element's subscription to PRU information.

[0471] For example, if the second network element determines that it accepts the first request sent by the first network element (i.e., the second network element accepts the subscription requested by the first network element), the second network element sends a first response to the first network element. The first response indicates that the first network element has successfully subscribed to the PRU information. Accordingly, the first network element receives the first response sent by the second network element, and can know from the first response that the first network element has successfully subscribed to the PRU information.

[0472] In some embodiments, when the first network element successfully subscribes to the PRU information, the first response includes at least one of the following 7.1 to 7.4:

[0473] 7.1 Subscription identifier.

[0474] The subscription identifier, also known as subscription ID, subscription identifier, subscription event identifier, etc., is used to uniquely identify the subscription requested by the first network element. If the first network element successfully subscribes to the PRU information in the region, the second network element can generate the subscription identifier and send it to the first network element, which can then manage the subscription based on this identifier.

[0475] For example, if a first network element wishes to unsubscribe from PRU information in a region, it can send a request to a second network element to unsubscribe from the PRU information in the region. This request may include a subscription identifier. Upon receiving the request, the second network element can obtain the subscription identifier and thus know that the first network element requested to unsubscribe from the PRU information in the region.

[0476] For example, if a first network element wants to update the validity period of PRU information in a subscription area, it can send a request to a second network element to request the update of the validity period. This request may include the subscription identifier and the updated validity period. Upon receiving the request, the second network element can obtain the subscription identifier and the updated validity period, thus knowing that the first network element requested an update of the validity period of PRU information in the subscription area.

[0477] 7.2 Time information, used to indicate the valid period of time for the first network element to subscribe to PRU information.

[0478] If the first network element successfully subscribes to the PRU information in the region, the second network element can indicate the validity period of the PRU information in the region to the first network element. That is, the PRU information subscribed to by the first network element is valid within the validity period. If the PRU information in the region changes during the validity period, the second network element will send relevant information to the first network element; if the PRU information changes outside the validity period, the second network element may not send relevant information to the first network element because the PRU information in the region subscribed to by the first network element may become invalid.

[0479] Time information is used to indicate the valid period of information of PRU in the subscription area. For example, time information may include at least one of the following: the start time of the valid period, the end time of the valid period, the duration of the valid period, etc.

[0480] 7.3 Identification of the third network element: The third network element is the network element that establishes an association with the PRU.

[0481] The identifier of the third network element can be found in section 3.4b of step S2101, and will not be repeated here. If the first network element successfully subscribes to the PRU information in the region, the second network element can send a first response to the first network element, which includes the identifier of the third network element. Upon receiving the first response, the first network element can obtain the identifier of the third network element and determine the third network element associated with the PRU based on this identifier.

[0482] 7.4 Information about the PRU stored in the second network element.

[0483] The PRU information stored in the second network element can be found in step 2.4 of S2101, and will not be repeated here. If the first network element successfully subscribes to the PRU information in the region, the second network element can send a first response to the first network element, which includes the PRU information stored in the second network element. Upon receiving the first response, the first network element can obtain the PRU information stored in the second network element.

[0484] In step S2304, if an event is detected in which the information of the PRU in the area changes, the second network element sends a notification message to the first network element. The notification message is used to notify that the information of the PRU in the area has changed.

[0485] If the first network element successfully subscribes to the PRU information in the area, the second network element can detect whether the PRU information in the area has changed. If the second network element detects a change in the PRU information in the area, the second network element sends a notification message to the first network element to notify that the PRU information in the area has changed; correspondingly, the first network element receives the notification message sent by the second network element and can know from the notification message that the PRU information in the area has changed.

[0486] For details on the notification message, please refer to steps 5.1 to 5.5 in step S2103 of Figure 2a, which will not be repeated here.

[0487] In step S2305, the first network element sends a second request to the second network element. The second request is used to request the unsubscription of PRU information in the region.

[0488] In some cases, if the first network element does not need to obtain the PRU information in the area, the first network element can send a second request to the second network element to request the second network element to unsubscribe from the PRU information in the area; correspondingly, the second network element receives the second request sent by the first network element and can learn from the second request that the first network element requested to unsubscribe from the PRU information in the area.

[0489] In some embodiments, the second request includes a subscription identifier, which is used to indicate the PRU information in the region subscribed by the first network element. The second network element can determine from the subscription identifier that the first network element requests to unsubscribe from the PRU information in the region.

[0490] In step S2306, the second network element sends a second response to the first network element. The second response is used to indicate the result of the first network element unsubscribing from the PRU information in the region. The result of the first network element unsubscribing from the PRU information in the region is either successful unsubscription or unsubscription failure.

[0491] After receiving the second request from the first network element, the second network element is able to learn that the first network element requested to unsubscribe from the PRU information in the region. The second network element may accept or reject the first network element's request to unsubscribe. Then, the second network element sends a second response to the first network element, which indicates the result of the first network element's unsubscription of the PRU information in the region.

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

[0493] In some embodiments, steps S2303 and S2304 may be performed in a different order or simultaneously, and steps S2304 and S2305 may be performed in a different order or simultaneously. Steps S2302, S2303, S2304, S2305, and S2306 are optional, and one or more of these steps may be omitted or substituted in different embodiments.

[0494] 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.

[0495] Figure 2d is an exemplary interactive schematic diagram of a subscription method provided in this disclosure. Referring to Figure 2d, the method includes:

[0496] Step S2401: The first network element sends a first request to the second network element. The first request is used to subscribe to PRU information in the area.

[0497] The implementation method of step S2401 can be found in the relevant introduction of step S2301 in Figure 2c, and will not be repeated here.

[0498] In step S2402, the second network element determines to reject the first request sent by the first network element.

[0499] After receiving the first request from the first network element, the second network element can obtain the PRU information in the first network element's subscription area. The second network element may accept or reject the subscription request from the first network element.

[0500] In step S2403, the second network element sends a first response to the first network element. The first response is used to indicate the result of the first network element subscribing to the PRU information in the region. The result of the first network element subscribing to the PRU information in the region is that the subscription failed.

[0501] If the first network element fails to subscribe to the PRU information in the region, the second network element sends a first response to the first network element. The first response is used to indicate the result of the first network element's subscription to the PRU information in the region.

[0502] For example, if the second network element determines that it rejects the first request sent by the first network element (i.e., the second network element rejects the subscription requested by the first network element), the second network element sends a first response to the first network element. The first response indicates that the first network element's subscription to the PRU information has failed. Accordingly, the first network element receives the first response sent by the second network element and can know from the first response that the first network element's subscription to the PRU information has failed.

[0503] In some embodiments, if the first network element fails to subscribe to PRU information, the first response includes at least one of the following 8.1 to 8.2:

[0504] 8.1 The fourth instruction message is used to indicate that the first network element failed to subscribe to the PRU information.

[0505] If the first network element fails to subscribe to PRU information in the subscription area, the second network element can send a first response to the first network element, which includes a fourth indication. Upon receiving the first response, the first network element can obtain the fourth indication, and based on the fourth indication, it can determine that the first network element's subscription to PRU information in the subscription area has failed.

[0506] 8.2 Reasons for the failure of the first network element to subscribe to PRU information.

[0507] The reason why the first network element failed to subscribe to the PRU information in the subscription area can also be called the failure reason, rejection reason, etc. In the event that the first network element's subscription to the PRU information in the subscription area fails, the second network element can send a first response to the first network element, which includes the reason for the failure. Upon receiving the first response, the first network element will know the reason for the failure.

[0508] The subscription method involved in the embodiments of this disclosure may include at least one of steps S2401 to S2403. For example, step S2401 may be implemented as a standalone embodiment, and step S2401 + step S2402 + step S2403 may be implemented as a standalone embodiment, but is not limited thereto.

[0509] In some embodiments, steps S2402 and S2403 are optional, and one or more of these steps may be omitted or substituted in different embodiments.

[0510] 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.

[0511] Referring to Figure 3, which is an exemplary interactive schematic diagram of the subscription method provided in this embodiment of the disclosure. As shown in Figure 3, the subscription method includes the following steps:

[0512] Step S301: The first network element sends a first request to the second network element. The first request is used to subscribe to events of PRUs in the area and / or to subscribe to information of PRUs in the area.

[0513] In some embodiments, the first network element can be a second LMF network element or a sensing function network element; the second network element can be, for example, an NRF network element.

[0514] The first network element sends a first request to the second network element, subscribing to events of PRUs in the region and / or information of PRUs in the region through the first request; correspondingly, the second network element receives the first request sent by the first network element, and can learn about the events of PRUs in the region subscribed by the first network element and / or information of PRUs in the region through the first request.

[0515] If the first network element subscribes to events of the PRU in the area, the second network element can detect whether the event has occurred. If the event occurs, the second network element can send relevant information to the first network element. For example, events of the PRU in the area may include: the presence of a PRU in the area, the absence of a PRU in the area, a PRU entering the area, a PRU leaving the area, changes in the information of the PRU in the area, etc. For a description of events of the PRU in the area, please refer to steps 1.1 to 1.5 in step S2101 of Figure 2a, which will not be repeated here.

[0516] If the first network element subscribes to PRU information in the area, the second network element can detect whether the PRU information in the area has changed. If the PRU information in the area changes, the second network element can send relevant information to the first network element. For example, the PRU information in the area may include: the type of the PRU, the location of the PRU, third indication information indicating whether a PRU exists in the area, information about the PRU stored by the second network element, etc. For a description of the PRU information, please refer to steps 2.1 to 2.4 in step S2101 of Figure 2a.

[0517] For an introduction to the first request, please refer to the relevant content in steps 3.1 to 3.4 of S2101 in Figure 2a, which will not be repeated here.

[0518] In some embodiments, optional implementations of step S301 can refer to optional implementations of step S2101 in FIG2a, and other related parts in the embodiments involved in FIG2a; optional implementations of step S301 can also refer to optional implementations of step S2201 in FIG2b, and other related parts in the embodiments involved in FIG2b, which will not be repeated here.

[0519] 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.

[0520] 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.

[0521] 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.

[0522] 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. Furthermore, it can also be a hardware circuit designed for artificial intelligence, which can be understood as an ASIC, such as a Neural Network Processing Unit (NPU), a Tensor Processing Unit (TPU), or a Deep Learning Processing Unit (DPU).

[0523] Figure 4a is a schematic diagram of the structure of a subscription device according to an embodiment of this disclosure. The subscription device 4100 is used to perform any of the above methods. In some embodiments, as shown in Figure 4a, the subscription device 4100 may include:

[0524] The transceiver module 4101 is used to send a first request to the second network element. The first request is used to subscribe to events of PRUs in the area and / or to subscribe to information of PRUs in the area.

[0525] In some embodiments, the event includes at least one of the following:

[0526] PRUs exist in the region;

[0527] PRU is not present in the region;

[0528] PRU enters the area;

[0529] PRU leaves the area;

[0530] The information of PRU in the region has changed.

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

[0532] Types of PRUs;

[0533] Location of PRU;

[0534] The first indication information is used to indicate whether a PRU exists in the area;

[0535] The second network element stores PRU information.

[0536] In some embodiments, the first request includes at least one of the following:

[0537] The second instruction information is used to instruct the first network element to request information about the PRU in the region;

[0538] The third instruction information is used to instruct the first network element to request information from the third network element;

[0539] Association relationship identifier, used to identify the association relationship between the third network element and the PRU;

[0540] Information about the third network element;

[0541] Information about the event;

[0542] Information about the region;

[0543] The third network element is the network element associated with the PRU.

[0544] In some embodiments, the information of the third network element includes at least one of the following:

[0545] Types of third network elements;

[0546] The identifier of the third network element;

[0547] The identifier of a network element set is used to indicate the network element set to which the third network element belongs.

[0548] In some embodiments, the information of an event includes at least one of the following:

[0549] Event identifier;

[0550] The conditions for triggering the event;

[0551] The object of the event.

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

[0553] Receive a first response sent by the second network element, the first response being used to indicate the result of the first network element subscribing to the event and / or PRU information;

[0554] The result of the first network element subscription event and / or PRU information is that the subscription was successful; or the result of the first network element subscription event and / or PRU information is that the subscription failed.

[0555] In some embodiments, the first response is used to indicate that the first network element subscription event and / or PRU information was successful, and the first response includes at least one of the following:

[0556] The identifier of the subscription;

[0557] Time information is used to indicate the valid period of information for the first network element's subscription events and / or PRUs;

[0558] The identifier of the third network element; the third network element is the network element that establishes an association with the PRU.

[0559] The second network element stores PRU information.

[0560] In some embodiments, the first response is used to indicate that the information of the first network element subscription event and / or PRU has failed, and the first response includes:

[0561] The fourth instruction information is used to indicate that the first network element subscription event and / or PRU information failed; and / or,

[0562] The reason for the failure of the first network element subscription event and / or PRU information.

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

[0564] Receive notification messages sent by the second network element, which are used to notify of an event; and / or, the information of the PRU in the area has changed.

[0565] In some embodiments, the notification message includes at least one of the following:

[0566] The types of changes in PRU information;

[0567] The identifier of the third network element; the third network element is the network element that establishes an association with the PRU.

[0568] Information about PRU;

[0569] Information after the PRU changes;

[0570] The fifth instruction is used to indicate that the information of the PRU has changed.

[0571] In some embodiments, the type of change includes at least one of the following:

[0572] Add PRU information;

[0573] Update PRU information;

[0574] Delete PRU information.

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

[0576] Send a second request to the second network element. The second request is used to request information on the unsubscribe event and / or PRU.

[0577] In some embodiments, the second request includes a subscription identifier, which is used to indicate information about events and / or PRUs subscribed to by the first network element.

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

[0579] Receive a second response sent by the second network element, the second response being used to instruct the first network element on the result of unsubscribing from the event and / or PRU information;

[0580] The result of the first network element's unsubscription event and / or PRU information is that the unsubscription was successful; or the result of the first network element's unsubscription event and / or PRU information is that the unsubscription failed.

[0581] Optionally, the transceiver module is used to perform at least one of the communication steps such as sending and / or receiving performed by the subscription device 4100 in any of the above methods (e.g., steps S2101, S2103, S2104, S2105, S2106, S2201, S2203, S2301, S2303, S2304, S2305, S2306, S2401, S2403, S301, but not limited thereto), which will not be elaborated here.

[0582] Figure 4b is a schematic diagram of the structure of a subscription device according to an embodiment of this disclosure. The subscription device 4200 is used to perform any of the above methods. In some embodiments, as shown in Figure 4b, the subscription device 4200 may include:

[0583] The transceiver module 4201 is used to receive a first request sent by a first network element. The first request is used to subscribe to events of PRUs in the area and / or to subscribe to information of PRUs in the area.

[0584] In some embodiments, the event includes at least one of the following:

[0585] PRUs exist in the region;

[0586] PRU is not present in the region;

[0587] PRU enters the area;

[0588] PRU leaves the area;

[0589] The information of PRU in the region has changed.

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

[0591] Types of PRUs;

[0592] Location of PRU;

[0593] The first indication information is used to indicate whether a PRU exists in the area;

[0594] The second network element stores PRU information.

[0595] In some embodiments, the first request includes at least one of the following:

[0596] The second instruction information is used to instruct the first network element to request information about the PRU in the region;

[0597] The third instruction information is used to instruct the first network element to request information from the third network element;

[0598] Association relationship identifier, used to identify the association relationship between the third network element and the PRU;

[0599] Information about the third network element;

[0600] Information about the event;

[0601] Information about the region;

[0602] The third network element is the network element associated with the PRU.

[0603] In some embodiments, the information of the third network element includes at least one of the following:

[0604] Types of third network elements;

[0605] The identifier of the third network element;

[0606] The identifier of a network element set is used to indicate the network element set to which the third network element belongs.

[0607] In some embodiments, the information of an event includes at least one of the following:

[0608] Event identifier;

[0609] The conditions for triggering the event;

[0610] The object of the event.

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

[0612] Send a first response to the first network element. The first response is used to indicate the result of the first network element subscribing to the event and / or PRU information.

[0613] The result of the first network element subscription event and / or PRU information is that the subscription was successful; or the result of the first network element subscription event and / or PRU information is that the subscription failed.

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

[0615] If the first request sent by the first network element is accepted, a first response is sent to the first network element. The first response is used to indicate that the first network element has successfully subscribed to the event and / or PRU information.

[0616] The first response includes at least one of the following:

[0617] The identifier of the subscription;

[0618] Time information is used to indicate the valid period of information for the first network element's subscription events and / or PRUs;

[0619] The identifier of the third network element; the third network element is the network element that establishes an association with the PRU.

[0620] The second network element stores PRU information.

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

[0622] If it is determined that the first request sent by the first network element is rejected, a first response is sent to the first network element. The first response is used to indicate that the first network element has failed to subscribe to the event and / or PRU information.

[0623] The first response includes:

[0624] The fourth instruction information is used to indicate that the first network element subscription event and / or PRU information failed; and / or,

[0625] The reason for the failure of the first network element subscription event and / or PRU information.

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

[0627] Send a notification message to the first network element, the notification message being used to notify that an event has occurred; and / or, the notification message being used to notify that the information of the PRU in the area has changed.

[0628] In some embodiments, the notification message includes at least one of the following:

[0629] The types of changes in PRU information;

[0630] The identifier of the third network element; the third network element is the network element that establishes an association with the PRU.

[0631] Information about PRU;

[0632] Information after the PRU changes;

[0633] The fifth instruction is used to indicate that the information of the PRU has changed.

[0634] In some embodiments, the type of change includes at least one of the following:

[0635] Add PRU information;

[0636] Update PRU information;

[0637] Delete PRU information.

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

[0639] Receive a second request sent by the first network element. The second request is used to request information on the unsubscribe event and / or PRU.

[0640] In some embodiments, the second request includes a subscription identifier, which is used to indicate information about events and / or PRUs subscribed to by the first network element.

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

[0642] Send a second response to the first network element, the second response being used to instruct the first network element to unsubscribe from the event and / or the result of the PRU information;

[0643] The result of the first network element's unsubscription event and / or PRU information is that the unsubscription was successful; or the result of the first network element's unsubscription event and / or PRU information is that the unsubscription failed.

[0644] In some embodiments, the transceiver module may include a transmitting module and / or a receiving module, which may be separate or integrated. Optionally, the transceiver module may be interchangeable with a transceiver.

[0645] In some embodiments, the processing module may be a single module or may include multiple sub-modules. Optionally, the multiple sub-modules may each perform all or part of the steps required by the processing module.

[0646] In some embodiments, the processing module can be replaced by the processor, and the transceiver module can be replaced by the transceiver.

[0647] 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 subscription device 4200 in any of the above methods (e.g., steps S2101, S2103, S2104, S2105, S2106, S2201, S2203, S2301, S2303, S2304, S2305, S2306, S2401, S2403, S301, but not limited thereto), which will not be elaborated here.

[0648] Figure 5a is a schematic diagram of the structure of the communication device 5100 proposed in an embodiment of this disclosure. The communication device 5100 can be a network device (e.g., access network device, core network device, etc.), a terminal device (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 device 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.

[0649] As shown in Figure 5a, 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, terminal devices, terminal device 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.

[0650] 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 transceiver 5102 performs at least one of the communication steps such as sending and / or receiving in the above-described method (e.g., steps S2101, S2103, S2104, S2105, S2106, S2201, S2203, S2301, S2303, S2304, S2305, S2306, S2401, S2403, S301, but not limited thereto), and the processor 5101 performs at least one of other steps (e.g., steps S2102, S2202, S2302, S2402, 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.

[0651] 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.

[0652] 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 not be limited by FIG. 5a. The communication device may be a standalone device or may be 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, the IC collection may also include 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 device, smart terminal device, cellular phone, wireless device, handheld device, mobile unit, vehicle device, network device, cloud device, artificial intelligence device, etc.; (6) others, etc.

[0653] Figure 5b is a schematic diagram of the structure of the chip 5200 proposed in an embodiment of this disclosure. For cases where the communication device 5100 can be a chip or a chip system, the schematic diagram of the chip 5200 shown in Figure 5b can be referenced, but the invention is not limited thereto.

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

[0655] 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.

[0656] 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, S2103, S2104, S2105, S2106, S2201, S2203, S2301, S2303, S2304, S2305, S2306, S2401, S2403, S301, 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, the chip 5200, the memory 5203, or the transceiver device. In some embodiments, the processor 5201 performs at least one of other steps (e.g., steps S2102, S2202, S2302, S2402, but not limited thereto).

[0657] 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.

[0658] 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.

[0659] 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.

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

[0661] 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.

[0662] 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.

[0663] 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 subscription method, characterized in that, The method, executed by the first network element, includes: Send a first request to the second network element, the first request being used to subscribe to events of the localization reference unit (PRU) in the region, and / or to subscribe to information of the PRU in the region.

2. The method according to claim 1, characterized in that, The event includes at least one of the following: PRUs exist in the region; PRUs are not present in the region. PRU enters the area; PRU leaves the area; The PRU information changes in the region.

3. The method according to claim 1 or 2, characterized in that, The information of the PRU includes at least one of the following: Types of PRUs; Location of PRU; The first indication information is used to indicate whether a PRU exists in the area; The second network element stores the PRU information.

4. The method according to any one of claims 1-3, characterized in that, The first request includes at least one of the following: The second instruction information is used to instruct the first network element to request information about the PRU in the region; The third instruction information is used to instruct the first network element to request information from the third network element; Association relationship identifier, used to identify the association relationship between the third network element and the PRU; Information about the third network element; Information about the event; Information about the area; The third network element is a network element associated with the PRU.

5. The method according to claim 4, characterized in that, The information of the third network element includes at least one of the following: The type of the third network element; The identifier of the third network element; The identifier of the network element set is used to indicate the network element set to which the third network element belongs.

6. The method according to claim 4, characterized in that, The information about the event includes at least one of the following: The identifier of the event; The triggering conditions of the event; The object of the event.

7. The method according to any one of claims 1-6, characterized in that, The method further includes: Receive a first response sent by the second network element, the first response being used to indicate the result of the first network element subscribing to the event and / or the PRU information; Wherein, the result of the first network element subscribing to the event and / or the PRU information is a successful subscription; or, the result of the first network element subscribing to the event and / or the PRU information is a failed subscription.

8. The method according to claim 7, characterized in that, The first response is used to indicate that the first network element has successfully subscribed to the event and / or the PRU information, and the first response message includes at least one of the following: The identifier of the subscription; Time information is used to indicate the valid period during which the first network element subscribes to the event and / or the PRU information; The identifier of the third network element, which is a network element that has established an association with the PRU; The second network element stores the PRU information.

9. The method according to claim 7, characterized in that, The first response is used to indicate that the first network element failed to subscribe to the event and / or the PRU information, and the first response includes: The fourth indication information is used to indicate that the first network element failed to subscribe to the event and / or the PRU information; and / or, The reason why the first network element failed to subscribe to the event and / or the PRU information.

10. The method according to any one of claims 1-9, characterized in that, The method further includes: The system receives a notification message sent by the second network element, the notification message being used to notify that the event has occurred; and / or, the information of the PRU in the region has changed.

11. The method according to claim 10, characterized in that, The notification message includes at least one of the following: The types of changes in PRU information; The identifier of the third network element, which is a network element that has established an association with the PRU; Information about PRU; Information after the PRU changes; The fifth indication information is used to indicate that the information of the PRU has changed.

12. The method according to claim 11, characterized in that, The type of change includes at least one of the following: Add PRU information; Update PRU information; Delete PRU information.

13. The method according to any one of claims 1-12, characterized in that, The method further includes: Send a second request to the second network element, the second request being used to request unsubscribe from the event and / or the PRU information.

14. The method according to claim 13, characterized in that, The second request includes a subscription identifier, which is used to indicate the information of the event and / or the PRU subscribed by the first network element.

15. The method according to claim 13 or 14, characterized in that, The method further includes: Receive a second response sent by the second network element, the second response being used to instruct the first network element to unsubscribe from the event and / or the PRU information; Wherein, the result of the first network element unsubscribing from the event and / or the PRU information is a successful unsubscription; or, the result of the first network element unsubscribing from the event and / or the PRU information is a failed unsubscription.

16. A subscription method, characterized in that, The method, executed by the second network element, includes: Receive a first request sent by a first network element, the first request being used to subscribe to events of PRUs in the region, and / or to subscribe to information of PRUs in the region.

17. The method according to claim 16, characterized in that, The event includes at least one of the following: PRUs exist in the region; PRUs are not present in the region. PRU enters the area; PRU leaves the area; The PRU information changes in the region.

18. The method according to claim 16 or 17, characterized in that, The information of the PRU includes at least one of the following: Types of PRUs; Location of PRU; The first indication information is used to indicate whether a PRU exists in the area; The second network element stores the PRU information.

19. The method according to any one of claims 16-18, characterized in that, The first request includes at least one of the following: The second instruction information is used to instruct the first network element to request information about the PRU in the region; The third instruction information is used to instruct the first network element to request information from the third network element; Association relationship identifier, used to identify the association relationship between the third network element and the PRU; Information about the third network element; Information about the event; Information about the area; The third network element is a network element associated with the PRU.

20. The method according to claim 19, characterized in that, The information of the third network element includes at least one of the following: The type of the third network element; The identifier of the third network element; The identifier of the network element set is used to indicate the network element set to which the third network element belongs.

21. The method according to claim 19, characterized in that, The information about the event includes at least one of the following: The identifier of the event; The triggering conditions of the event; The object of the event.

22. The method according to any one of claims 16-21, characterized in that, The method further includes: Send a first response to the first network element, the first response being used to indicate the result of the first network element subscribing to the event and / or the PRU information; Wherein, the result of the first network element subscribing to the event and / or the PRU information is a successful subscription; or, the result of the first network element subscribing to the event and / or the PRU information is a failed subscription.

23. The method according to claim 22, characterized in that, Sending the first response to the first network element includes: If the first request sent by the first network element is accepted, the first response is sent to the first network element, wherein the first response is used to indicate that the first network element has successfully subscribed to the event and / or the PRU information; The first response includes at least one of the following: The identifier of the subscription; Time information is used to indicate the valid period during which the first network element subscribes to the event and / or the PRU information; The identifier of the third network element, which is a network element that has established an association with the PRU; The second network element stores the PRU information.

24. The method according to claim 22, characterized in that, Sending the first response to the first network element includes: If it is determined that the first request sent by the first network element is rejected, the first response is sent to the first network element, the first response being used to indicate that the first network element has failed to subscribe to the event and / or the PRU information; The first response includes: The fourth indication information is used to indicate that the first network element failed to subscribe to the event and / or the PRU information; and / or, The reason why the first network element failed to subscribe to the event and / or the PRU information.

25. The method according to any one of claims 16-24, characterized in that, The method further includes: Send a notification message to the first network element, the notification message being used to notify that the event has occurred; and / or, the notification message being used to notify that the information of the PRU in the area has changed.

26. The method according to claim 25, characterized in that, The notification message includes at least one of the following: The types of changes in PRU information; The identifier of the third network element, which is a network element that has established an association with the PRU; Information about PRU; Information after the PRU changes; The fifth indication information is used to indicate that the information of the PRU has changed.

27. The method according to claim 26, characterized in that, The type of change includes at least one of the following: Add PRU information; Update PRU information; Delete PRU information.

28. The method according to any one of claims 16-27, characterized in that, The method further includes: The system receives a second request sent by the first network element, the second request being used to request unsubscribing from the event and / or the PRU information.

29. The method according to claim 28, characterized in that, The second request includes a subscription identifier, which is used to indicate the information of the event and / or the PRU subscribed by the first network element.

30. The method according to claim 28 or 29, characterized in that, The method further includes: Send a second response to the first network element, the second response being used to instruct the first network element to unsubscribe from the event and / or the result of the PRU information; Wherein, the result of the first network element unsubscribing from the event and / or the PRU information is a successful unsubscription; or, the result of the first network element unsubscribing from the event and / or the PRU information is a failed unsubscription.

31. A subscription device, characterized in that, include: The transceiver module is used to send a first request to the second network element, wherein the first request is used to subscribe to events of PRUs in the area, and / or information of PRUs in the area.

32. A subscription device, characterized in that, include: The transceiver module is used to receive a first request sent by a first network element, wherein the first request is used to subscribe to events of PRUs in the area, and / or information of PRUs in the area.

33. A first network element, characterized in that, include: One or more processors; The first network element is used to execute the subscription method according to any one of claims 1-15.

34. A second network element, characterized in that, include: One or more processors; The second network element is used to execute the subscription method according to any one of claims 16-30.

35. A subscription system, characterized in that, include: First network element and second network element; The first network element is configured to implement the subscription method according to any one of claims 1-15; The second network element is configured to implement the subscription method as described in any one of claims 16-30.

36. A storage medium storing instructions, characterized in that, When the instruction is executed on a communication device, the communication device performs the subscription method as described in any one of claims 1-15 or 16-30.

37. 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 subscription method as described in any one of claims 1-15 or 16-30 is implemented.

Images