Apparatus, method and computer program for optimizing shared data retrieval

Abstract

And measures for shared data retrieval optimization are provided. Such measures exemplarily comprise sending a request for first data, the request comprising at least one available shared data set identifier corresponding to at least one available shared data set; and receiving a data response including compiled data including general data in an explicit form, at least one unavailable shared data set in an explicit form, and at least one unavailable shared data set identifier corresponding to the at least one unavailable shared data set.

Description

Cross-reference to related applications

[0001] This application claims the benefit of priority to Indian Provisional Patent Application No. 202341033726, filed on May 12, 2024, which is incorporated herein by reference as if reproduced in its entirety. Technical Field

[0002] Various example embodiments relate to the optimization of shared data retrieval in communication systems (commonly referred to as shared data retrieval optimization). More specifically, various example embodiments exemplarily relate to methods, apparatus, and computer program products for optimizing shared data retrieval in communication systems. Summary of the Invention

[0003] The appended claims set forth various aspects of the exemplary embodiments.

[0004] According to one exemplary aspect, a method is provided, the method comprising: sending a request for a shared dataset that matches a shared dataset identifier-independent matching criterion, the request including the shared dataset identifier-independent matching criterion; and receiving a response including at least one shared dataset that matches the shared dataset identifier-independent matching criterion and at least one shared dataset identifier corresponding to the at least one shared dataset.

[0005] According to one exemplary aspect, a method is provided, the method comprising: receiving a request for a shared dataset that matches a shared dataset identifier-independent matching criterion, the request including the shared dataset identifier-independent matching criterion; retrieving from a data storage device storing the shared dataset at least one shared dataset that matches the shared dataset identifier-independent matching criterion; and sending a response including the at least one shared dataset that matches the shared dataset identifier-independent matching criterion and at least one shared dataset identifier corresponding to the at least one shared dataset.

[0006] According to one exemplary aspect, a method is provided, the method comprising: sending a subscription request for a shared dataset that matches a shared dataset identifier-independent matching criterion, the subscription request including the shared dataset identifier-independent matching criterion; and receiving a subscription confirmation.

[0007] According to one exemplary aspect, a method is provided, the method comprising: receiving a subscription request for a shared dataset that matches a shared dataset identifier-independent matching criterion, the subscription request including the shared dataset identifier-independent matching criterion; retrieving from a data storage device storing the shared dataset at least one shared dataset that matches the shared dataset identifier-independent matching criterion; establishing a subscription for the at least one shared dataset that matches the shared dataset identifier-independent matching criterion; and sending a subscription confirmation.

[0008] According to one exemplary aspect, a method is provided, the method comprising: sending a request for first data, the request including at least one available shared dataset identifier corresponding to at least one available shared dataset; and receiving a data response including compiled data, the compiled data including general data in explicit form, at least one unavailable shared dataset in explicit form, and at least one unavailable shared dataset identifier corresponding to the at least one unavailable shared dataset.

[0009] According to one exemplary aspect, a method is provided, the method comprising: receiving a request for first data, the request including at least one available shared dataset identifier corresponding to at least one available shared dataset; retrieving the first data from a data storage as retrieved data; compiling data based on the retrieved data into compiled data, the compiled data including general data in explicit form, at least one unavailable shared dataset in explicit form, and at least one unavailable shared dataset identifier corresponding to the at least one unavailable shared dataset; and sending a data response including the compiled data.

[0010] According to one exemplary aspect, a method is provided, the method comprising: sending a subscription request for first data, the subscription request including at least one available shared dataset identifier corresponding to at least one available shared dataset; and receiving a message based on the subscription request, the message including information about at least one unavailable shared dataset associated with the first data.

[0011] According to one exemplary aspect, a method is provided, the method comprising: receiving a subscription request for first data, the subscription request including at least one available shared dataset identifier corresponding to at least one available shared dataset; retrieving the first data from a data storage as retrieved data; and sending a message based on the subscription request, the message including information about at least one unavailable shared dataset associated with the first data.

[0012] According to one exemplary aspect, a method is provided, the method comprising: sending a request for first data; and receiving a data response, the data response including compiled data, said compiled data including general data in an explicit form, at least one unavailable shared dataset in an explicit form associated with said first data, and at least one unavailable shared dataset identifier corresponding to said at least one unavailable shared dataset.

[0013] According to one exemplary aspect, a method is provided, the method comprising: receiving a request for first data; retrieving the first data from a data storage as retrieved data; compiling data based on the retrieved data into compiled data, the compiled data including general data in an explicit form, at least one unavailable shared dataset in an explicit form associated with the first data, and at least one unavailable shared dataset identifier corresponding to the at least one unavailable shared dataset; and sending a data response including the compiled data.

[0014] According to one exemplary aspect, a method is provided, the method comprising: sending a subscription request for first data; and receiving a message based on the subscription request, the message including information about at least one unavailable shared dataset related to the first data.

[0015] According to one exemplary aspect, a method is provided, the method comprising: receiving a subscription request for first data; retrieving the first data from a data storage as retrieved data; and sending a message based on the subscription request, the message including information about at least one unavailable shared dataset associated with the first data.

[0016] According to one exemplary aspect, an apparatus is provided, comprising: a transmitting circuit system and a receiving circuit system, the transmitting circuit system being configured to transmit a request for a shared dataset that matches a shared dataset identifier-independent matching criterion, the request including the shared dataset identifier-independent matching criterion, and the receiving circuit system being configured to receive a response including at least one shared dataset that matches the shared dataset identifier-independent matching criterion and at least one shared dataset identifier corresponding to the at least one shared dataset.

[0017] According to one exemplary aspect, an apparatus is provided, comprising: a receiving circuit system, an acquiring circuit system, and a transmitting circuit system, the receiving circuit system being configured to receive a request for a shared dataset that matches a shared dataset identifier-independent matching criterion, the request including the shared dataset identifier-independent matching criterion; the acquiring circuit system being configured to acquire at least one shared dataset that matches the shared dataset identifier-independent matching criterion from a data storage device storing the shared dataset; and the transmitting circuit system being configured to transmit a response including the at least one shared dataset that matches the shared dataset identifier-independent matching criterion and at least one shared dataset identifier corresponding to the at least one shared dataset.

[0018] According to one exemplary aspect, an apparatus is provided, comprising: a transmitting circuit system and a receiving circuit system, the transmitting circuit system being configured to transmit a subscription request for a shared dataset that matches a shared dataset identifier-independent matching criterion, the subscription request including the shared dataset identifier-independent matching criterion, and the receiving circuit system being configured to receive a subscription confirmation.

[0019] According to one exemplary aspect, an apparatus is provided, comprising: a receiving circuit system, an acquiring circuit system, an establishing circuit system, and a transmitting circuit system, wherein the receiving circuit system is configured to receive a subscription request for a shared dataset that matches a shared dataset identifier-independent matching criterion, the subscription request including the shared dataset identifier-independent matching criterion; the acquiring circuit system is configured to acquire at least one shared dataset that matches the shared dataset identifier-independent matching criterion from a data storage device storing the shared dataset; the establishing circuit system is configured to establish a subscription for the at least one shared dataset that matches the shared dataset identifier-independent matching criterion; and the transmitting circuit system is configured to send a subscription confirmation.

[0020] According to one exemplary aspect, an apparatus is provided, comprising: a transmitting circuit system and a receiving circuit system, the transmitting circuit system being configured to transmit a request for first data, the request including at least one available shared dataset identifier corresponding to at least one available shared dataset, and the receiving circuit system being configured to receive a data response including compiled data, the compiled data including general data in explicit form, at least one unavailable shared dataset in explicit form, and at least one unavailable shared dataset identifier corresponding to the at least one unavailable shared dataset.

[0021] According to one exemplary aspect, an apparatus is provided, comprising: a receiving circuit system, an acquiring circuit system, a compiling circuit system, and a transmitting circuit system. The receiving circuit system is configured to receive a request for first data, the request including at least one available shared dataset identifier corresponding to at least one available shared dataset. The acquiring circuit system is configured to acquire the first data from a data storage as acquired data. The compiling circuit system is configured to compile data based on the acquired data into compiled data, the compiled data including general data in explicit form, at least one unavailable shared dataset in explicit form, and at least one unavailable shared dataset identifier corresponding to the at least one unavailable shared dataset. The transmitting circuit system is configured to transmit a data response including the compiled data.

[0022] According to one exemplary aspect, an apparatus is provided comprising: a transmitting circuit system and a receiving circuit system, the transmitting circuit system being configured to transmit a subscription request for first data, the subscription request including at least one available shared dataset identifier corresponding to at least one available shared dataset, and the receiving circuit system being configured to receive a message based on the subscription request, the message including information about at least one unavailable shared dataset associated with the first data.

[0023] According to one exemplary aspect, an apparatus is provided, comprising: a receiving circuit system, an acquiring circuit system, and a transmitting circuit system, wherein the receiving circuit system is configured to receive a subscription request for first data, the subscription request including at least one available shared dataset identifier corresponding to at least one available shared dataset; the acquiring circuit system is configured to acquire the first data from a data storage as acquired data; and the transmitting circuit system is configured to transmit a message based on the subscription request, the message including information about at least one unavailable shared dataset associated with the first data.

[0024] According to one exemplary aspect, an apparatus is provided comprising: a transmitting circuit system and a receiving circuit system, the transmitting circuit system being configured to transmit a request for first data, and the receiving circuit system being configured to receive a data response, the data response including compiled data, the compiled data including general data in explicit form, at least one unavailable shared dataset in explicit form associated with the first data, and at least one unavailable shared dataset identifier corresponding to the at least one unavailable shared dataset.

[0025] According to one exemplary aspect, an apparatus is provided, comprising: a receiving circuit system, an acquiring circuit system, a compiling circuit system, and a transmitting circuit system. The receiving circuit system is configured to receive a request for first data. The acquiring circuit system is configured to acquire the first data from a data storage as acquired data. The compiling circuit system is configured to compile data based on the acquired data into compiled data, the compiled data including general data in an explicit form, at least one unavailable shared dataset in an explicit form associated with the first data, and at least one unavailable shared dataset identifier corresponding to the at least one unavailable shared dataset. The transmitting circuit system is configured to transmit a data response including the compiled data.

[0026] According to one exemplary aspect, an apparatus is provided comprising: a transmitting circuit system and a receiving circuit system, the transmitting circuit system being configured to transmit a subscription request for first data, and the receiving circuit system being configured to receive a message based on the subscription request, the message including information about at least one unavailable shared dataset related to the first data.

[0027] According to one exemplary aspect, an apparatus is provided comprising: a receiving circuit system, an acquiring circuit system, and a transmitting circuit system, wherein the receiving circuit system is configured to receive a subscription request for first data, the acquiring circuit system is configured to acquire the first data from a data storage device as acquired data, and the transmitting circuit system is configured to transmit a message based on the subscription request, the message including information about at least one unavailable shared dataset associated with the first data.

[0028] According to one exemplary aspect, an apparatus is provided, the apparatus comprising: at least one processor, at least one memory including computer program code, and at least one interface configured to communicate with at least another apparatus, the at least one processor, the at least one memory, and the computer program code being configured to cause the apparatus to perform: sending a request for a shared dataset that matches a shared dataset identifier-independent matching criterion, the request including the shared dataset identifier-independent matching criterion; and receiving a response including at least one shared dataset that matches the shared dataset identifier-independent matching criterion and at least one shared dataset identifier corresponding to the at least one shared dataset.

[0029] According to one exemplary aspect, an apparatus is provided, comprising: at least one processor, at least one memory including computer program code, and at least one interface configured to communicate with at least another apparatus, the at least one processor, the at least one memory, and the computer program code being configured to cause the apparatus to perform: receiving a request for a shared dataset that matches a shared dataset identifier-independent matching criterion, the request including the shared dataset identifier-independent matching criterion; retrieving from a data memory storing the shared dataset at least one shared dataset that matches the shared dataset identifier-independent matching criterion; and sending a response including the at least one shared dataset that matches the shared dataset identifier-independent matching criterion and at least one shared dataset identifier corresponding to the at least one shared dataset.

[0030] According to one exemplary aspect, an apparatus is provided, the apparatus comprising: at least one processor, at least one memory including computer program code, and at least one interface configured to communicate with at least another apparatus, the at least one processor, the at least one memory, and the computer program code being configured to cause the apparatus to perform: sending a subscription request for a shared dataset that matches a shared dataset identifier-independent matching criterion, the subscription request including the shared dataset identifier-independent matching criterion; and receiving a subscription confirmation.

[0031] According to one exemplary aspect, an apparatus is provided, comprising: at least one processor, at least one memory including computer program code, and at least one interface configured to communicate with at least another apparatus, the at least one processor, the at least one memory, and the computer program code being configured to cause the apparatus to perform: receiving a subscription request for a shared dataset that matches a shared dataset identifier-independent matching criterion, the subscription request including the shared dataset identifier-independent matching criterion; retrieving from a data memory storing the shared dataset at least one shared dataset that matches the shared dataset identifier-independent matching criterion; establishing a subscription for the at least one shared dataset that matches the shared dataset identifier-independent matching criterion; and sending a subscription confirmation.

[0032] According to one exemplary aspect, an apparatus is provided, the apparatus comprising: at least one processor, at least one memory including computer program code, and at least one interface configured to communicate with at least another apparatus, the at least one processor, the at least one memory, and the computer program code being configured to cause the apparatus to perform: sending a request for first data, the request including at least one available shared dataset identifier corresponding to at least one available shared dataset; and receiving a data response, the data response including compiled data, the compiled data including general data in explicit form, at least one unavailable shared dataset in explicit form, and at least one unavailable shared dataset identifier corresponding to the at least one unavailable shared dataset.

[0033] According to one exemplary aspect, an apparatus is provided, comprising: at least one processor, at least one memory including computer program code, and at least one interface configured to communicate with at least another apparatus, the at least one processor, the at least one memory, and the computer program code being configured to cause the apparatus to perform: receiving a request for first data, the request including at least one available shared dataset identifier corresponding to at least one available shared dataset; retrieving the first data from a data memory as retrieved data; compiling data based on the retrieved data into compiled data, the compiled data including general data in explicit form, at least one unavailable shared dataset in explicit form, and at least one unavailable shared dataset identifier corresponding to the at least one unavailable shared dataset; and sending a data response including the compiled data.

[0034] According to one exemplary aspect, an apparatus is provided, the apparatus comprising: at least one processor, at least one memory including computer program code, and at least one interface configured to communicate with at least another apparatus, the at least one processor, the at least one memory, and the computer program code being configured to cause the apparatus to perform: sending a subscription request for first data, the subscription request including at least one available shared dataset identifier corresponding to at least one available shared dataset; and receiving a message based on the subscription request, the message including information about at least one unavailable shared dataset associated with the first data.

[0035] According to one exemplary aspect, an apparatus is provided, comprising: at least one processor, at least one memory including computer program code, and at least one interface configured to communicate with at least another apparatus, the at least one processor, the at least one memory, and the computer program code being configured to cause the apparatus to perform: receiving a subscription request for first data, the subscription request including at least one available shared dataset identifier corresponding to at least one available shared dataset; retrieving the first data from a data memory as retrieved data; and sending a message based on the subscription request, the message including information about at least one unavailable shared dataset associated with the first data.

[0036] According to one exemplary aspect, an apparatus is provided, the apparatus comprising: at least one processor, at least one memory including computer program code, and at least one interface configured to communicate with at least another apparatus, the at least one processor, the at least one memory, and the computer program code being configured to cause the apparatus to perform: sending a request for first data; and receiving a data response, the data response including compiled data, the compiled data including general data in explicit form, at least one unavailable shared dataset in explicit form associated with the first data, and at least one unavailable shared dataset identifier corresponding to the at least one unavailable shared dataset.

[0037] According to one exemplary aspect, an apparatus is provided, comprising: at least one processor, at least one memory including computer program code, and at least one interface configured to communicate with at least another apparatus, the at least one processor, the at least one memory, and the computer program code being configured to cause the apparatus to perform: receiving a request for first data; retrieving the first data from a data memory as retrieved data; compiling data based on the retrieved data into compiled data, the compiled data including general data in an explicit form, at least one unavailable shared dataset in an explicit form associated with the first data, and at least one unavailable shared dataset identifier corresponding to the at least one unavailable shared dataset; and sending a data response including the compiled data.

[0038] According to one exemplary aspect, an apparatus is provided, the apparatus comprising: at least one processor, at least one memory including computer program code, and at least one interface configured to communicate with at least another apparatus, the at least one processor, the at least one memory, and the computer program code being configured to cause the apparatus to perform: sending a subscription request for first data; and receiving a message based on the subscription request, the message including information about at least one unavailable shared dataset associated with the first data.

[0039] According to one exemplary aspect, an apparatus is provided, the apparatus comprising: at least one processor, at least one memory including computer program code, and at least one interface configured to communicate with at least another apparatus, the at least one processor, the at least one memory, and the computer program code being configured to cause the apparatus to perform: receiving a subscription request for first data; retrieving the first data from a data storage device as retrieved data; and sending a message based on the subscription request, the message including information about at least one unavailable shared dataset associated with the first data.

[0040] According to one exemplary aspect, a computer program product is provided, the computer program product including computer-executable computer program code, which, when the program is run on a computer (e.g., a computer of an apparatus according to any of the above-described apparatus-related exemplary aspects of the present disclosure), is configured to cause the computer to perform a method according to any of the above-described method-related exemplary aspects of the present disclosure.

[0041] Such computer program products may include (or be embodied in) a (tangible) computer-readable (storage) medium on which computer-executable computer program code is stored, and / or the program may be directly loaded into the internal memory of a computer or its processor.

[0042] Any of the above aspects can efficiently reduce communication and signaling load, thereby addressing at least some of the problems and drawbacks associated with the prior art.

[0043] As an example embodiment, optimization for shared data retrieval is provided. More specifically, as an example embodiment, measures and mechanisms for implementing optimization for shared data retrieval are provided.

[0044] Therefore, improvements are achieved by enabling / implementing methods, apparatuses, and computer program products that optimize shared data retrieval. Attached Figure Description

[0045] The present disclosure will be described in more detail below by way of non-limiting example with reference to the accompanying drawings, in which:

[0046] Figure 1 This is a block diagram illustrating an apparatus according to an exemplary embodiment;

[0047] Figure 2 This is a block diagram illustrating an apparatus according to an exemplary embodiment;

[0048] Figure 3 This is a block diagram illustrating an apparatus according to an exemplary embodiment;

[0049] Figure 4 This is a block diagram illustrating an apparatus according to an exemplary embodiment;

[0050] Figure 5 This is a block diagram illustrating an apparatus according to an exemplary embodiment.

[0051] Figure 6 This is a block diagram illustrating an apparatus according to an exemplary embodiment.

[0052] Figure 7 This is a block diagram illustrating an apparatus according to an exemplary embodiment.

[0053] Figure 8 This is a block diagram illustrating an apparatus according to an exemplary embodiment;

[0054] Figure 9 This is a block diagram illustrating an apparatus according to an exemplary embodiment;

[0055] Figure 10 This is a block diagram illustrating an apparatus according to an exemplary embodiment;

[0056] Figure 11 This is a block diagram illustrating an apparatus according to an exemplary embodiment;

[0057] Figure 12 This is a block diagram illustrating an apparatus according to an exemplary embodiment;

[0058] Figure 13 This is a block diagram illustrating an apparatus according to an exemplary embodiment;

[0059] Figure 14 This is a block diagram illustrating an apparatus according to an exemplary embodiment;

[0060] Figure 15 This is a block diagram illustrating an apparatus according to an exemplary embodiment;

[0061] Figure 16 This is a block diagram illustrating an apparatus according to an exemplary embodiment;

[0062] Figure 17 This is a block diagram illustrating an apparatus according to an exemplary embodiment;

[0063] Figure 18 This is a block diagram illustrating an apparatus according to an exemplary embodiment;

[0064] Figure 19 This is a block diagram illustrating an apparatus according to an exemplary embodiment;

[0065] Figure 20 This is a block diagram illustrating an apparatus according to an exemplary embodiment;

[0066] Figure 21 This is a block diagram illustrating an apparatus according to an exemplary embodiment.

[0067] Figure 22This is a block diagram illustrating an apparatus according to an exemplary embodiment;

[0068] Figure 23 This is a schematic diagram of a process according to an example embodiment;

[0069] Figure 24 This is a schematic diagram of a process according to an example embodiment;

[0070] Figure 25 This is a schematic diagram of a process according to an example embodiment;

[0071] Figure 26 This is a schematic diagram of a process according to an example embodiment;

[0072] Figure 27 This is a schematic diagram of a process according to an example embodiment;

[0073] Figure 28 This is a schematic diagram of a process according to an example embodiment;

[0074] Figure 29 This is a schematic diagram of a process according to an example embodiment;

[0075] Figure 30 This is a schematic diagram of a process according to an example embodiment;

[0076] Figure 31 This is a schematic diagram of a process according to an example embodiment;

[0077] Figure 32 This is a schematic diagram of a process according to an example embodiment;

[0078] Figure 33 This is a schematic diagram of a process according to an example embodiment;

[0079] Figure 34 This is a schematic diagram of a process according to an example embodiment;

[0080] Figure 35 A schematic diagram of a signaling sequence according to an example embodiment is shown;

[0081] Figure 36 A schematic diagram of a signaling sequence according to an example embodiment is shown;

[0082] Figure 37 A schematic diagram of a signaling sequence according to an example embodiment is shown;

[0083] Figure 38 A schematic diagram of a signaling sequence according to an example embodiment is shown;

[0084] Figure 39 A schematic diagram of a signaling sequence according to an example embodiment is shown;

[0085] Figure 40 A schematic diagram of a signaling sequence according to an example embodiment is shown;

[0086] Figure 41 A schematic diagram of a signaling sequence according to an example embodiment is shown;

[0087] Figure 42 A schematic diagram of a signaling sequence according to an example embodiment is shown;

[0088] Figure 43 A schematic diagram of a signaling sequence according to an example embodiment is shown;

[0089] Figure 44 A schematic diagram of a signaling sequence according to an example embodiment is shown;

[0090] Figure 45 A schematic diagram of a signaling sequence according to an example embodiment is shown;

[0091] Figure 46 A schematic diagram of a signaling sequence according to an example embodiment is shown;

[0092] Figure 47 A schematic diagram of a signaling sequence according to an example embodiment is shown; and

[0093] Figure 48 This is a block diagram of an apparatus according to an example embodiment, which is an alternative map. Detailed Implementation

[0094] This disclosure is described herein with reference to specific, non-limiting examples and embodiments that are now considered possible. Those skilled in the art will understand that this disclosure is by no means limited to these examples and can be applied more broadly.

[0095] It should be noted that the following description of this disclosure and its embodiments primarily relates to specifications used as non-limiting examples of certain exemplary network configurations and deployments. That is, this disclosure and its embodiments are primarily described in conjunction with 3GPP specifications used as non-limiting examples of certain exemplary network configurations and deployments. Therefore, the description of the exemplary embodiments given herein specifically refers to terms directly related to them. Such terms are used only in the context of the presented non-limiting examples and naturally do not limit this disclosure in any way. Rather, any other communication or communication-related system deployments, etc., may be utilized, provided they conform to the features described herein.

[0096] In the following, various embodiments and implementations of this disclosure, as well as aspects or embodiments thereof, are described using several variations and / or alternatives. It should generally be noted that, depending on certain needs and constraints, all described variations and / or alternatives may be provided individually or in any possible combination (including combinations of individual features of the various variations and / or alternatives).

[0097] As used herein, “at least one of the following:” and “at least one of…” and similar wording (where a list of two or more elements is connected by “and” or “or”) means at least any one of these elements, or at least any two or more of these elements, or at least all of these elements.

[0098] According to example embodiments, measures and mechanisms are generally provided for (enabling / implementing) optimization of shared data retrieval in communication systems.

[0099] This specification generally relates to methods or procedures for retrieving shared data from network entities of a communication system, such as the Unified Data Management (UDM) / Unified Data Repository (UDR) of a fifth-generation communication system (5GS). In addition to normal (unique) data, shared data can also be stored in the UDM / UDR. For example, some data may be part of the user equipment (UE) context of an exemplary user equipment (UE1) or the UE context of another exemplary user equipment (UE2). This data can then be stored as shared data. In the network entity (e.g., the UDM / UDR) of the communication data, the shared data is assigned a shared data identifier (ID). In the example above, the UE contexts of UE1 and UE2 will each contain some (unique) data for UE1 or UE2, as well as a shared data ID (only the ID of the shared data) that identifies the shared data (this is part of the UE contexts of both UE1 and UE2, but the shared data is stored in another data repository located elsewhere). Therefore, currently, when a network function (NF) wants to retrieve the UE context of, for example, UE1, stored at a network entity (e.g., the UDM / UDR of the communication system), the NF will request the UE context of UE1, and it will receive UE1's unique data plus a shared data ID. Then, in a second step, the NF needs to use the shared data ID to retrieve the shared data that is part of UE1's UE context from another data repository.

[0100] Any NF in the communication system can retrieve shared subscription data from the UDM / UDR of the communication system (e.g., 5GS) using the Nudm and Nudr interfaces of the communication system.

[0101] Retrieval of shared subscription data (when needed, i.e., before it is stored in the data repository) is based on the identifier of the shared data (often referred to as the shared data ID in this article). In other words, so far, shared data can only be retrieved based on the shared data ID.

[0102] The NF can retrieve individual UE-specific data from the UDM / UDR using Nudm and Nudr. Upon receiving the individual UE-specific data, the NF can detect that the retrieved individual UE-specific data includes a shared data ID indicating that the retrieved individual UE-specific data is incomplete and must be expanded / merged with some shared data. If the shared data pointed to by this ID is not already cached, the NF retrieves the shared data identified by the shared data ID, as described above.

[0103] An NF that has retrieved shared subscription data (e.g., shared access and mobility (AM) data identified by exemplary shared data ID-17 for a UE1-specific context) can store the shared AM data for later use (e.g., in a UE2-specific context, when UE1 and UE2 share the retrieved AM data identified by shared data ID-17).

[0104] NF can use Nudm's "data change notification subscription" mechanism, and when shared data (e.g., identified by shared data ID-17) is modified, UDM / UDR will notify the Nudr interface.

[0105] Shared data identified by a shared data identifier is only available in the UE-specific context in which the shared data is referenced via a shared data ID. For example, if UE3 shares AM data identified by shared data ID-25 (e.g., a shared data ID with a value of 25) with another UE (e.g., UE4) but does not share AM data with UE1 and UE2, then NF cannot use shared data ID-17 (e.g., a shared data ID with a value of 17) in the UE3-specific context.

[0106] Shared data can have one of a variety of predefined data types (e.g., shared data types).

[0107] In other words, in the above implementation, shared data is retrieved one by one based on shared data ID, and whenever shared data is retrieved based on shared data ID, NF must use the "data change notification subscription" mechanism to subscribe to notifications of changes to the shared data identified by the shared data ID.

[0108] Therefore, the following problem arises: this method results in additional / increased signaling in communication systems (e.g., 5GS).

[0109] Therefore, there is a need to provide apparatus, methods, and computer programs for optimizing shared data retrieval, as well as measures and mechanisms for optimizing shared data retrieval.

[0110] In short, to address the problem that shared data can only be retrieved based on shared data ID to date, according to the example embodiment, it is possible to retrieve or subscribe to notifications about changes to shared data based on shared data type (in addition to retrieval or subscription based on shared data ID).

[0111] Accordingly, an NF (e.g., AMF or UDM) of a communication system (e.g., 5GS) can be an NF service consumer and can provide one or more shared data types in a request to retrieve data and / or subscribe to notifications about data changes to the UDM or UDR. The terms "NF service consumer" and "NF consumer" are used interchangeably herein. An "NF service consumer" is any NF of a communication system (e.g., 5GS) that consumes services exposed by another NF of the communication system (e.g., 5GS), as described in the 3GPP NR standard.

[0112] Then, in response to a request to retrieve this data, the UDM or UDR provides the shared data for all (or some) shared data IDs that match the indication type, or stores a subscription to notifications of changes to all (or some) shared data IDs that match the indication type, and subsequently provides notifications when these shared data change.

[0113] According to an example embodiment, the NF consumer can indicate a set of conditions that the shared data should meet in order to be retrieved (or subscribed to), such as the presence of certain attributes or attribute value pairs in the shared data type, rather than indicating the shared data type that the NF consumer wants to retrieve (or subscribe to).

[0114] Furthermore, to address the identified problem that, so far, the data retrieval mechanism for the Nudm and Nudr interfaces can be implemented through only two consecutive retrieval steps, according to an example embodiment, the NF consumer (e.g., AMF or UDM) can include a list of shared data IDs identifying shared data that the consumer has already stored locally in its requests to retrieve data and / or subscribe to notifications about data changes to the UDM or UDR.

[0115] If the UDM or UDR determines that the NF consumer does not reference some shared data in the request or subscription data, the UDM or UDR will also include both the shared data ID and the actual shared data for that shared data ID in its response to the request to retrieve that data, or store a subscription for notifications of changes to that shared data, and subsequently provide notifications including both the shared data ID and the actual changed shared data whenever any shared data changes.

[0116] According to an example embodiment, subscriptions can be combined with instant reporting requests, which enable the combination of retrieval and subscription as described above.

[0117] Furthermore, to further address the identified issue that the data retrieval mechanism of the Nudm and Nudr interfaces can currently be implemented through only two consecutive retrieval steps, according to an example embodiment, the NF consumer (e.g., the AMF or UDM of a 5GS) sends a request to the UDM or UDR to retrieve data and / or subscribe to notifications regarding data changes. Based on the (established) subscription to the shared data ID of that NF consumer, the UDM or UDR determines whether the NF consumer does not reference some shared data in the requested or subscribed data. In order to be able to determine which shared data the NF consumer has based on existing subscriptions, the UDM / UDR may need to know, for example, that the NF consumer preferably uses a subscription to retrieve such data based on the configuration of both parties.

[0118] If the NF consumer does not reference some shared data in the requested or subscribed data (if the UDM or UDR determines that the NF consumer does not reference some shared data in the requested or subscribed data), then the UDM or UDR additionally includes both the shared data ID and the actual shared data for that shared data ID in its response to a request to retrieve that data, or stores a subscription for notifications of changes to that shared data, and subsequently provides notifications including both the shared data ID and the actual changed shared data whenever any of those shared data changes. According to an example embodiment, a subscription can be combined with a request for immediate notification to achieve the combination of retrieval and subscription as described above.

[0119] The example implementation is described in more detail below.

[0120] Figure 1 This is a block diagram illustrating an apparatus according to an example embodiment. The apparatus may be a network entity 10, such as an Access and Mobility Functions entity or a Unified Data Management entity, which includes a transmitting circuit system 11 and a receiving circuit system 12. The transmitting circuit system 11 sends a request for a shared dataset that matches a shared dataset identifier-independent matching criterion, the request including the shared dataset identifier-independent matching criterion. The receiving circuit system 12 receives a response including at least one shared dataset that matches the shared dataset identifier-independent matching criterion and at least one shared dataset identifier corresponding to the at least one shared dataset. Figure 23 This is a schematic diagram of a process according to an example embodiment. According to Figure 1 The device can perform Figure 23 This method, but not limited to this method. Figure 23 The method can be derived from Figure 1 The device performs the action, but is not limited to the device performing the action.

[0121] like Figure 23As shown, the process according to the example embodiment includes the following operations: sending (S231) a request for a shared dataset that matches a shared dataset identifier-independent matching criterion, the request including the shared dataset identifier-independent matching criterion; and receiving (S232) a response including at least one shared dataset that matches the shared dataset identifier-independent matching criterion and at least one shared dataset identifier corresponding to the at least one shared dataset.

[0122] Figure 2 This is a block diagram illustrating an apparatus according to an exemplary embodiment. Specifically, Figure 2 The diagram shows Figure 1 A variant of the device shown. Therefore, according to Figure 2 The device may also include a storage circuit system 21.

[0123] In one embodiment, Figure 1 (or Figure 2 At least some of the functions of the apparatus shown can be shared between two physically independent devices that form an operational entity. Therefore, the apparatus can be considered as an operational entity that describes one or more physically independent devices for performing at least some of the described processes.

[0124] According to another example embodiment, the above-mentioned shared dataset identifier-independent matching criteria include Shared data types, or The characteristics of shared data content elements of the above shared data types.

[0125] According to another example embodiment, the above-mentioned shared dataset identifier-independent matching criteria include filtering information for filtering candidate information elements of the shared dataset.

[0126] according to Figure 23 The variations of the process shown provide exemplary additional operations, which are independent of each other. According to such variations, the exemplary method of the example embodiment may include the operation of storing at least one of the aforementioned shared datasets together with the corresponding shared dataset identifiers.

[0127] according to Figure 23 Variations of the illustrated process provide exemplary additional operations, which are themselves independent of each other. According to this variation, the response includes at least two shared datasets that match the aforementioned shared dataset identifier-independent matching criteria and at least two shared dataset identifiers corresponding to the aforementioned at least two shared datasets. Furthermore, the exemplary method according to the example embodiment may include sending a subscription request for notification of changes to the aforementioned at least two shared datasets, wherein the subscription request includes the aforementioned at least two shared dataset identifiers.

[0128] Figure 3 This is a block diagram illustrating an apparatus according to an example embodiment. The apparatus may be a network entity 30, such as a unified data management entity or a unified data repository entity, which includes a receiving circuitry 31, an acquiring circuitry 32, and a transmitting circuitry 33. The receiving circuitry 31 receives a request for a shared dataset that matches a shared dataset identifier-independent matching criterion, the request including the shared dataset identifier-independent matching criterion. The acquiring circuitry 32 acquires at least one shared dataset that matches the shared dataset identifier-independent matching criterion from a data storage device storing the shared datasets. The transmitting circuitry 33 transmits a response including the at least one shared dataset that matches the shared dataset identifier-independent matching criterion and at least one shared dataset identifier corresponding to the at least one shared dataset. Figure 24 This is a schematic diagram of a process according to an example embodiment. According to Figure 3 The device can perform Figure 24 This method, but not limited to this method. Figure 24 The method can be derived from Figure 3 The device performs the action, but is not limited to the device performing the action.

[0129] like Figure 24 As shown, the process according to the example embodiment includes the following operations: receiving (S241) a request for a shared dataset that matches a shared dataset identifier-independent matching criterion, the request including the shared dataset identifier-independent matching criterion; obtaining (S242) at least one shared dataset that matches the shared dataset identifier-independent matching criterion from a data storage device storing the shared dataset; and sending (S243) a response including the at least one shared dataset that matches the shared dataset identifier-independent matching criterion and at least one shared dataset identifier corresponding to the at least one shared dataset.

[0130] Figure 4 This is a block diagram illustrating an apparatus according to an exemplary embodiment. Specifically, Figure 4 The diagram shows Figure 3 A variant of the device shown. Therefore, according to Figure 4 The device may also include a filter circuit system 41 and / or a consideration circuit system 42.

[0131] In one embodiment, Figure 3 (or Figure 4 At least some of the functions of the apparatus shown can be shared between two physically independent devices that form an operational entity. Therefore, the apparatus can be considered as an operational entity that describes one or more physically independent devices for performing at least some of the described processes.

[0132] According to another example embodiment, the above-mentioned shared dataset identifier-independent matching criteria include: Shared data types; or The characteristics of shared data content elements of the above shared data types.

[0133] according to Figure 24 The illustrated variation provides exemplary additional operations and details of the sending operation, which are independent of each other. According to this variation, the shared dataset identifier-independent matching criterion includes filtering information for filtering candidate information elements of the shared dataset, and the exemplary method according to the example embodiment may include the operation of filtering information elements of at least one shared dataset obtained above. Furthermore, this exemplary sending operation according to the example embodiment may include operations that take into account the results of the above filtering.

[0134] according to Figure 24 Variations of the illustrated process provide exemplary additional operations, which are themselves independent of each other. According to this variation, the response includes at least two shared datasets that match the aforementioned shared dataset identifier-independent matching criteria and at least two shared dataset identifiers corresponding to the aforementioned at least two shared datasets. Furthermore, the exemplary method according to the example embodiment may include receiving a subscription request for notification of changes to the aforementioned at least two shared datasets, wherein the subscription request includes the aforementioned at least two shared dataset identifiers.

[0135] Figure 5 This is a block diagram illustrating an apparatus according to an example embodiment. The apparatus may be a network entity 50, such as an Access and Mobility Functions entity or a Unified Data Management entity, which includes a transmitting circuit system 51 and a receiving circuit system 52. The transmitting circuit system 51 transmits a subscription request for a shared dataset that matches a shared dataset identifier-independent matching criterion, the subscription request including the shared dataset identifier-independent matching criterion. The receiving circuit system 52 receives a subscription confirmation. Figure 25 This is a schematic diagram of a process according to an example embodiment. According to Figure 5 The device can perform Figure 25 This method, but not limited to this method. Figure 25 The method can be derived from Figure 5 The device performs the action, but is not limited to the device performing the action.

[0136] like Figure 25As shown, the process according to the example embodiment includes the following operations: sending (S251) a subscription request for a shared dataset that matches a shared dataset identifier-independent matching criterion, the subscription request including the shared dataset identifier-independent matching criterion; and receiving (S252) a subscription confirmation.

[0137] Figure 6 This is a block diagram illustrating an apparatus according to an exemplary embodiment. Specifically, Figure 6 The diagram shows Figure 5 A variant of the device shown. Therefore, according to Figure 6 The device may also include a storage circuit system 61.

[0138] In one embodiment, Figure 5 (or Figure 6 At least some of the functions of the apparatus shown can be shared between two physically independent devices that form an operational entity. Therefore, the apparatus can be considered as an operational entity that describes one or more physically independent devices for performing at least some of the described processes.

[0139] According to another example embodiment, the above-mentioned shared dataset identifier-independent matching criteria include: Shared data types; or The characteristics of shared data content elements of the above shared data types.

[0140] According to another example embodiment, the above-mentioned shared dataset identifier-independent matching criteria include filtering information for filtering candidate information elements of the shared dataset.

[0141] According to another example embodiment, the subscription request indicates an immediate reporting requirement, and the subscription confirmation includes at least one shared dataset that matches the matching criteria unrelated to the shared dataset identifier and at least one shared dataset identifier corresponding to the at least one shared dataset.

[0142] according to Figure 25 The variations of the process shown provide exemplary additional operations, which are independent of each other. According to such variations, the exemplary method of the example embodiment may include the operation of storing at least one of the aforementioned shared datasets together with the corresponding shared dataset identifiers.

[0143] Figure 7This is a block diagram illustrating an apparatus according to an example embodiment. The apparatus may be a network entity 70, such as a unified data management entity or a unified data repository entity, which includes a receiving circuitry 71, an acquiring circuitry 72, an establishing circuitry 73, and a transmitting circuitry 74. The receiving circuitry 71 receives a subscription request for a shared dataset that matches a shared dataset identifier-independent matching criterion, the subscription request including the shared dataset identifier-independent matching criterion. The acquiring circuitry 72 acquires at least one shared dataset that matches the shared dataset identifier-independent matching criterion from a data storage device storing the shared datasets. The establishing circuitry 73 establishes a subscription for the at least one shared dataset that matches the shared dataset identifier-independent matching criterion. The transmitting circuitry 74 sends a subscription confirmation. Figure 26 This is a schematic diagram of a process according to an example embodiment. According to Figure 7 The device can perform Figure 26 This method, but not limited to this method. Figure 26 The method can be derived from Figure 7 The device performs the action, but is not limited to the device performing the action.

[0144] like Figure 26 As shown, the process according to the example embodiment includes the following operations: receiving (S261) a subscription request for a shared dataset that matches a shared dataset identifier-independent matching criterion, the subscription request including the shared dataset identifier-independent matching criterion; obtaining (S262) at least one shared dataset that matches the shared dataset identifier-independent matching criterion from a data storage device storing the shared dataset; establishing (S263) a subscription for the at least one shared dataset that matches the shared dataset identifier-independent matching criterion; and sending (S264) a subscription confirmation.

[0145] Figure 8 This is a block diagram illustrating an apparatus according to an exemplary embodiment. Specifically, Figure 8 The diagram shows Figure 7 A variant of the device shown. Therefore, according to Figure 8 The device may also include a filter circuit system 81 and / or a consideration circuit system 82.

[0146] In one embodiment, Figure 7 (or Figure 8 At least some of the functions of the apparatus shown can be shared between two physically independent devices that form an operational entity. Therefore, the apparatus can be considered as an operational entity that describes one or more physically independent devices for performing at least some of the described processes.

[0147] According to another example embodiment, the above-mentioned shared dataset identifier-independent matching criteria include: Shared data types; or The characteristics of shared data content elements of the above shared data types.

[0148] according to Figure 26 The illustrated variation provides details of exemplary additional operations and exemplary establishment operations, which are independent of each other. According to this variation, the shared dataset identifier-independent matching criterion includes filtering information for filtering candidate information elements of the shared dataset, and the exemplary method according to the example embodiment may include the operation of filtering information elements of at least one shared dataset obtained above. Furthermore, this exemplary establishment operation according to the example embodiment may include operations that take into account the results of the above filtering.

[0149] According to another example embodiment, the subscription request indicates an immediate reporting requirement, and the subscription confirmation includes at least one shared dataset that matches the matching criteria unrelated to the shared dataset identifier and at least one shared dataset identifier corresponding to the at least one shared dataset.

[0150] Figure 9 This is a block diagram illustrating an apparatus according to an example embodiment. The apparatus may be a network entity 90, such as an Access and Mobility Functions entity or a Unified Data Management entity, which includes a transmitting circuit system 91 and a receiving circuit system 92. The transmitting circuit system 91 transmits a request for first data, the request including at least one available shared dataset identifier corresponding to at least one available shared dataset. The receiving circuit system 92 receives a data response including compiled data, the compiled data including general data in explicit form, at least one unavailable shared dataset in explicit form, and at least one unavailable shared dataset identifier corresponding to the at least one unavailable shared dataset. Figure 27 This is a schematic diagram of a process according to an example embodiment. According to Figure 9 The device can perform Figure 27 This method, but not limited to this method. Figure 27 The method can be derived from Figure 9 The device performs the action, but is not limited to the device performing the action.

[0151] like Figure 27As shown, the process according to the example embodiment includes the following operations: sending (S271) a request for first data, the request including at least one available shared dataset identifier corresponding to at least one available shared dataset; and receiving (S272) a data response, the data response including compiled data, the compiled data including general data in explicit form, at least one unavailable shared dataset in explicit form, and at least one unavailable shared dataset identifier corresponding to the at least one unavailable shared dataset.

[0152] In one embodiment, Figure 9 At least some of the functions of the illustrated apparatus can be shared between two physically independent devices forming an operational entity. Therefore, the apparatus can be considered as depicting an operational entity comprising one or more physically independent devices for performing at least some of the described processes.

[0153] According to another example embodiment, the compiled data includes at least one of the at least one available shared dataset identifiers, which corresponds to at least one available shared dataset in reference form among the at least one available shared dataset.

[0154] Figure 10 This is a block diagram illustrating an apparatus according to an example embodiment. The apparatus may be a network entity 100, such as a unified data management entity or a unified data repository entity, which includes a receiving circuitry 101, an acquisition circuitry 102, a compilation circuitry 103, and a transmitting circuitry 104. The receiving circuitry 101 receives a request for first data, the request including at least one available shared dataset identifier corresponding to at least one available shared dataset. The acquisition circuitry 102 acquires the first data from a data storage as acquisition data. The compilation circuitry 103 compiles data based on the acquired data into compiled data, the compiled data including general data in explicit form, at least one unavailable shared dataset in explicit form, and at least one unavailable shared dataset identifier corresponding to the at least one unavailable shared dataset. The transmitting circuitry 104 transmits a data response including the compiled data. Figure 28 This is a schematic diagram of a process according to an example embodiment. According to Figure 10 The device can perform Figure 28 This method, but not limited to this method. Figure 28 The method can be derived from Figure 10 The device performs the action, but is not limited to the device performing the action.

[0155] like Figure 28As shown, the process according to the example embodiment includes the following operations: receiving (S281) a request for first data, the request including at least one available shared dataset identifier corresponding to at least one available shared dataset; retrieving (S282) the first data from a data storage as retrieved data; compiling (S283) data based on the retrieved data into compiled data, the compiled data including general data in explicit form, at least one unavailable shared dataset in explicit form, and at least one unavailable shared dataset identifier corresponding to the at least one unavailable shared dataset; and sending (S284) a data response including the compiled data.

[0156] Figure 11 This is a block diagram illustrating an apparatus according to an exemplary embodiment. Specifically, Figure 11 The diagram shows Figure 10 A variant of the device shown. Therefore, according to Figure 11 The device may also include an analysis circuit system 111 and / or a forwarding circuit system 112.

[0157] In one embodiment, Figure 10 (or Figure 11 At least some of the functions of the apparatus shown can be shared between two physically independent devices that form an operational entity. Therefore, the apparatus can be considered as an operational entity that describes one or more physically independent devices for performing at least some of the described processes.

[0158] According to another example embodiment, the compiled data includes at least one of the at least one available shared dataset identifiers, which corresponds to at least one available shared dataset in reference form among the at least one available shared dataset.

[0159] according to Figure 28 Variations of the illustrated process provide exemplary additional operations, which are independent of each other. According to such a variation, an exemplary method based on an example embodiment may include: analyzing the acquired data to determine whether the acquired data includes at least one unavailable shared dataset identifier; and retrieving from the data storage the at least one unavailable shared dataset corresponding to the at least one unavailable shared dataset identifier.

[0160] according to Figure 28The variations of the illustrated process provide exemplary details of the acquisition operation, which are independent of each other. Such an exemplary acquisition operation according to an exemplary embodiment may include: forwarding the at least one available shared dataset identifier to the data storage; and receiving the acquired data from the data storage, the acquired data including the at least one unavailable shared dataset in explicit form and the at least one unavailable shared dataset identifier corresponding to the at least one unavailable shared dataset.

[0161] Figure 12 This is a block diagram illustrating an apparatus according to an example embodiment. The apparatus may be a network entity 120, such as an Access and Mobility Functions entity or a Unified Data Management entity, which includes a transmitting circuitry system 121 and a receiving circuitry system 122. The transmitting circuitry system 121 transmits a subscription request for first data, the subscription request including at least one available shared dataset identifier corresponding to at least one available shared dataset. The receiving circuitry system 122 receives a message based on the subscription request, the message including information about at least one unavailable shared dataset associated with the first data. Figure 29 This is a schematic diagram of a process according to an example embodiment. According to Figure 12 The device can perform Figure 29 This method, but not limited to this method. Figure 29 The method can be derived from Figure 12 The device performs the action, but is not limited to the device performing the action.

[0162] like Figure 29 As shown, the process according to the example embodiment includes the following operations: sending (S291) a subscription request for first data, the subscription request including at least one available shared dataset identifier corresponding to at least one available shared dataset; and receiving a message (S292) based on the subscription request, the message including information about at least one unavailable shared dataset related to the first data.

[0163] Figure 13 This is a block diagram illustrating an apparatus according to an exemplary embodiment. Specifically, Figure 13 The diagram shows Figure 12 A variant of the device shown. Therefore, according to Figure 13 The device may also include a storage circuit system 131.

[0164] In one embodiment, Figure 12 (or Figure 13 At least some of the functions of the apparatus shown can be shared between two physically independent devices that form an operational entity. Therefore, the apparatus can be considered as an operational entity that describes one or more physically independent devices for performing at least some of the described processes.

[0165] According to another example embodiment, the subscription request indicates an immediate reporting requirement, and the message is a subscription confirmation that includes the at least one unavailable shared dataset and at least one unavailable shared dataset identifier corresponding to the at least one unavailable shared dataset.

[0166] According to another example embodiment, the above message is a notification that includes information about changes to the at least one unavailable shared dataset and at least one unavailable shared dataset identifier corresponding to the at least one unavailable shared dataset.

[0167] according to Figure 29 The variations of the process shown provide exemplary additional operations, which are independent of each other. According to such variations, the exemplary method of the example embodiment may include the operation of storing at least one unavailable shared dataset along with the corresponding unavailable shared dataset identifier.

[0168] Figure 14 This is a block diagram illustrating an apparatus according to an example embodiment. The apparatus may be a network entity 140, such as a unified data management entity or a unified data repository entity, which includes a receiving circuitry 141, an acquiring circuitry 142, and a sending circuitry 144. The receiving circuitry 141 receives a subscription request for first data, the subscription request including at least one available shared dataset identifier corresponding to at least one available shared dataset. The acquiring circuitry 142 acquires the first data from a data storage device as acquired data. The sending circuitry 144 sends a message based on the subscription request, the message including information about at least one unavailable shared dataset associated with the first data. Figure 30 This is a schematic diagram of a process according to an example embodiment. According to Figure 14 The device can perform Figure 30 This method, but not limited to this method. Figure 30 The method can be derived from Figure 14 The device performs the action, but is not limited to the device performing the action.

[0169] like Figure 30 As shown, the process according to the example embodiment includes the following operations: receiving (S301) a subscription request for first data, the subscription request including at least one available shared dataset identifier corresponding to at least one available shared dataset; retrieving (S302) the first data from a data storage as retrieved data; and sending (S303) a message based on the subscription request, the message including information about at least one unavailable shared dataset related to the first data.

[0170] Figure 15 This is a block diagram illustrating an apparatus according to an exemplary embodiment. Specifically, Figure 15 The diagram shows Figure 14 A variant of the device shown. Therefore, according to Figure 14 The device may also include an analysis circuit system 151, a forwarding circuit system 152 and / or an establishment circuit system 153.

[0171] In one embodiment, Figure 14 (or Figure 15 At least some of the functions of the apparatus shown can be shared between two physically independent devices that form an operational entity. Therefore, the apparatus can be considered as an operational entity that describes one or more physically independent devices for performing at least some of the described processes.

[0172] according to Figure 30 Variations of the illustrated process provide exemplary additional operations, which are independent of each other. According to such a variation, an exemplary method based on an example embodiment may include analyzing the acquired data to determine whether the acquired data includes at least one unavailable shared dataset identifier.

[0173] According to another example embodiment, the subscription request indicates an immediate reporting requirement, and the message is a subscription confirmation that includes the at least one unavailable shared dataset and at least one unavailable shared dataset identifier corresponding to the at least one unavailable shared dataset. In some embodiments, the shared dataset is provided only as part of the immediate reporting, and no subscription is established for subsequent notifications regarding changes to the shared dataset.

[0174] According to other example embodiments, subscriptions to subsequent notifications regarding changes to the shared dataset are established. Notifications are provided when one or more shared datasets change. In some example embodiments, if the same consumer has already established several subscriptions to the same shared dataset, and the shared dataset changes, only one notification is provided related to one of the established subscriptions.

[0175] according to Figure 30 Variations of the process shown provide exemplary additional operations, which are independent of each other. According to such a variation, an exemplary method according to an example embodiment may include the following operations: establishing a subscription for an unavailable shared dataset related to the first data, based on the data acquired above, the unavailable shared dataset including at least one of the aforementioned unavailable shared datasets, wherein the message is a notification including information about changes to the at least one unavailable shared dataset and at least one unavailable shared dataset identifier corresponding to the at least one unavailable shared dataset.

[0176] according to Figure 30 The variations of the process shown provide exemplary additional operations, which are independent of each other. According to such variations, an exemplary method based on an example embodiment may include retrieving at least one of the aforementioned unavailable shared datasets from the aforementioned data storage.

[0177] according to Figure 30 The variations of the illustrated process provide exemplary details of the acquisition operation, which are independent of each other. Such an exemplary acquisition operation according to an exemplary embodiment may include: forwarding the at least one available shared dataset identifier to the data storage; and receiving the acquired data from the data storage, the acquired data including the at least one unavailable shared dataset in explicit form.

[0178] Figure 16 This is a block diagram illustrating an apparatus according to an example embodiment. The apparatus may be a network entity 160, such as an Access and Mobility Functions entity or a Unified Data Management entity, which includes a transmitting circuit system 161 and a receiving circuit system 162. The transmitting circuit system 161 transmits a request for first data. The receiving circuit system 162 receives a data response, which includes compiled data, said compiled data including general data in explicit form, at least one unavailable shared dataset in explicit form associated with said first data, and at least one unavailable shared dataset identifier corresponding to said at least one unavailable shared dataset. Figure 31 This is a schematic diagram of a process according to an example embodiment. According to Figure 16 The device can perform Figure 31 This method, but not limited to this method. Figure 31 The method can be derived from Figure 16 The device performs the action, but is not limited to the device performing the action.

[0179] like Figure 31 As shown, the process according to the example embodiment includes the following operations: sending (S311) a request for first data; and receiving (S312) a data response, the data response including compiled data, the compiled data including general data in explicit form, at least one unavailable shared dataset in explicit form associated with the first data, and at least one unavailable shared dataset identifier corresponding to the at least one unavailable shared dataset.

[0180] In one embodiment, Figure 16 At least some of the functions of the illustrated apparatus can be shared between two physically independent devices forming an operational entity. Therefore, the apparatus can be considered as depicting an operational entity comprising one or more physically independent devices for performing at least some of the described processes.

[0181] According to another example embodiment, the above request for the first data indicates whether the request for the first data is also related to an unavailable shared dataset, and if the above request for the first data does not indicate that the request for the first data is also related to an unavailable shared dataset, then the above compiled data does not include the above at least one unavailable shared dataset in explicit form.

[0182] According to another example embodiment, the compiled data described above includes at least one available shared dataset identifier as a reference to at least one available shared dataset.

[0183] Figure 17 This is a block diagram illustrating an apparatus according to an example embodiment. The apparatus may be a network entity 170, such as a unified data management entity or a unified data repository entity, which includes a receiving circuitry 171, an acquisition circuitry 172, a compilation circuitry 173, and a transmitting circuitry 174. The receiving circuitry 171 receives a request for first data. The acquisition circuitry 172 acquires the first data from a data storage as acquisition data. The compilation circuitry 173 compiles data based on the acquired data into compiled data, which includes general data in explicit form, at least one unavailable shared dataset in explicit form associated with the first data, and at least one unavailable shared dataset identifier corresponding to the at least one unavailable shared dataset. The transmitting circuitry 174 transmits a data response including the compiled data. Figure 32 This is a schematic diagram of a process according to an example embodiment. According to Figure 17 The device can perform Figure 32 This method, but not limited to this method. Figure 32 The method can be derived from Figure 17 The device performs the action, but is not limited to the device performing the action.

[0184] like Figure 32 As shown, the process according to the example embodiment includes the following operations: receiving (S321) a request for first data; retrieving (S322) the first data from the data storage as acquired data; compiling (S323) data based on the acquired data into compiled data, the compiled data including general data in explicit form, at least one unavailable shared dataset in explicit form associated with the first data, and at least one unavailable shared dataset identifier corresponding to the at least one unavailable shared dataset; and sending (S324) a data response including the compiled data.

[0185] Figure 18 This is a block diagram illustrating an apparatus according to an exemplary embodiment. Specifically, Figure 18 The diagram shows Figure 17A variant of the device shown. Therefore, according to Figure 18 The apparatus may also include a driving circuit system 181 and / or an analysis circuit system 182.

[0186] In one embodiment, Figure 17 (or Figure 18 At least some of the functions of the apparatus shown can be shared between two physically independent devices that form an operational entity. Therefore, the apparatus can be considered as an operational entity that describes one or more physically independent devices for performing at least some of the described processes.

[0187] According to another example embodiment, the above request for the first data indicates whether the request for the first data is also related to an unavailable shared dataset, and if the above request for the first data does not indicate that the request for the first data is also related to an unavailable shared dataset, then the above compiled data does not include the above at least one unavailable shared dataset in explicit form.

[0188] according to Figure 32 Variations of the illustrated process provide exemplary additional operations, which are independent of each other. According to such variations, an exemplary method based on an example embodiment may include operations that derive information about the available shared datasets at the requester of the first data based on subscription information associated with the requester of the first data described above.

[0189] according to Figure 32 Variations of the illustrated process provide exemplary additional operations, which are independent of each other. According to such a variation, an exemplary method based on an example embodiment may include: analyzing, based on the aforementioned information regarding the available shared dataset, whether the acquired data includes at least one unavailable shared dataset identifier; and retrieving from the aforementioned data storage the at least one unavailable shared dataset corresponding to the at least one unavailable shared dataset identifier.

[0190] according to Figure 32 The variations of the process shown provide exemplary details of the acquisition operation, which are independent of each other. Such an exemplary acquisition operation according to an example embodiment may include receiving the acquired data from the data storage described above, the acquired data including, in explicit form, the at least one unavailable shared dataset and an identifier corresponding to the at least one unavailable shared dataset.

[0191] According to another example embodiment, the compiled data described above includes at least one available shared dataset identifier corresponding to at least one available shared dataset in the form of a reference.

[0192] Figure 19 This is a block diagram illustrating an apparatus according to an example embodiment. The apparatus may be a network entity 190, such as an Access and Mobility Functions entity or a Unified Data Management entity, which includes a transmitting circuit system 191 and a receiving circuit system 192. The transmitting circuit system 191 transmits a subscription request for first data. The receiving circuit system 192 receives a message based on the subscription request, the message including information about at least one unavailable shared dataset related to the first data. Figure 33 This is a schematic diagram of a process according to an example embodiment. According to Figure 19 The device can perform Figure 33 This method, but not limited to this method. Figure 33 The method can be derived from Figure 19 The device performs the action, but is not limited to the device performing the action.

[0193] like Figure 33 As shown, the process according to the example embodiment includes the following operations: sending (S331) a subscription request for first data; and receiving (S332) a message based on the subscription request, the message including information about at least one unavailable shared dataset related to the first data.

[0194] Figure 20 This is a block diagram illustrating an apparatus according to an exemplary embodiment. Specifically, Figure 20 The diagram shows Figure 19 A variant of the device shown. Therefore, according to Figure 20 The device may also include a storage circuit system 201.

[0195] In one embodiment, Figure 19 (or Figure 20 At least some of the functions of the apparatus shown can be shared between two physically independent devices that form an operational entity. Therefore, the apparatus can be considered as an operational entity that describes one or more physically independent devices for performing at least some of the described processes.

[0196] According to another example embodiment, the subscription request for the first data indicates whether the subscription request for the first data is also related to an unavailable shared dataset, and if the subscription request for the first data does not indicate that the subscription request for the first data is also related to an unavailable shared dataset, then the message does not include the above information about the at least one unavailable shared dataset.

[0197] According to another example embodiment, the subscription request indicates an immediate reporting requirement, and the message is a subscription confirmation that includes the at least one unavailable shared dataset and at least one unavailable shared dataset identifier corresponding to the at least one unavailable shared dataset.

[0198] According to another example embodiment, the above message is a notification that includes information about changes to the at least one unavailable shared dataset and at least one unavailable shared dataset identifier corresponding to the at least one unavailable shared dataset.

[0199] according to Figure 33 The variations of the process shown provide exemplary additional operations, which are independent of each other. According to such variations, the exemplary method of the example embodiment may include the operation of storing at least one unavailable shared dataset along with the corresponding unavailable shared dataset identifier.

[0200] Figure 21 This is a block diagram illustrating an apparatus according to an example embodiment. The apparatus may be a network entity 210, such as a unified data management entity or a unified data repository entity, which includes a receiving circuitry 211, an acquiring circuitry 212, and a sending circuitry 214. The receiving circuitry 211 receives a subscription request for first data. The acquiring circuitry 212 acquires the first data from a data storage device as acquired data. The sending circuitry 214 sends a message based on the subscription request, the message including information about at least one unavailable shared dataset associated with the first data. Figure 34 This is a schematic diagram of a process according to an example embodiment. According to Figure 21 The device can perform Figure 34 This method, but not limited to this method. Figure 34 The method can be derived from Figure 21 The device performs the action, but is not limited to the device performing the action.

[0201] like Figure 34 As shown, the process according to the example embodiment includes the following operations: receiving (S341) a subscription request for first data; retrieving (S342) the first data from the data storage as retrieved data; and sending (S343) a message based on the subscription request, the message including information about at least one unavailable shared dataset related to the first data.

[0202] Figure 22 This is a block diagram illustrating an apparatus according to an exemplary embodiment. Specifically, Figure 22 The diagram shows Figure 21 A variant of the device shown. Therefore, according to Figure 22The device may also include a driving circuit system 221, an analysis circuit system 222, a forwarding circuit system 223 and / or an establishment circuit system 224.

[0203] In one embodiment, Figure 21 (or Figure 22 At least some of the functions of the apparatus shown can be shared between two physically independent devices that form an operational entity. Therefore, the apparatus can be considered as an operational entity that describes one or more physically independent devices for performing at least some of the described processes.

[0204] According to another example embodiment, the subscription request for the first data indicates whether the subscription request for the first data is also related to an unavailable shared dataset, and if the subscription request for the first data does not indicate that the subscription request for the first data is also related to an unavailable shared dataset, then the message does not include the above information about the at least one unavailable shared dataset.

[0205] according to Figure 34 Variations of the illustrated process provide exemplary additional operations, which are independent of each other. According to such variations, an exemplary method based on an example embodiment may include operations that derive information about the available shared datasets at the requester of the first data based on subscription information associated with the requester of the first data described above.

[0206] according to Figure 34 The variations of the illustrated process provide exemplary additional operations, which are independent of each other. According to such variations, the exemplary method of the example embodiment may include an operation based on the aforementioned information about the available shared dataset to analyze whether the acquired data includes at least one unavailable shared dataset identifier.

[0207] According to another example embodiment, the subscription request indicates an immediate reporting requirement, and the message is a subscription confirmation that includes the at least one unavailable shared dataset and at least one unavailable shared dataset identifier corresponding to the at least one unavailable shared dataset. In some embodiments, the shared dataset is provided only as part of the immediate reporting, and no subscription is established for subsequent notifications regarding changes to the shared dataset.

[0208] According to other example embodiments, subscriptions are established for subsequent notifications regarding changes to a shared dataset related to the acquisition of data. Notifications are provided when one or more shared datasets change. In some example embodiments, if several subscriptions to the same shared dataset have already been established for the same requester, and the shared dataset changes, only one notification is provided related to one of the established subscriptions. In some embodiments, if a subscription to a shared dataset related to a requester terminates, but the aforementioned subscription request for data related to the requester remains valid, the process includes checking whether the shared dataset with the terminated subscription is related to the acquisition of data, and if so, establishing a new subscription to the shared dataset by terminating the subscription.

[0209] according to Figure 34 Variations of the illustrated process provide exemplary additional operations, which are independent of each other. According to such a variation, an exemplary method according to an example embodiment may include the following operations: establishing a subscription to an unavailable shared dataset related to the first data, the unavailable shared dataset including at least one of the aforementioned unavailable shared datasets, based on the acquired data described above; wherein the message is a notification including information about changes to the at least one unavailable shared dataset; and at least one unavailable shared dataset identifier corresponding to the at least one unavailable shared dataset.

[0210] according to Figure 34 The variations of the process shown provide exemplary additional operations, which are independent of each other. According to such variations, the exemplary method of the example embodiment may include the operation of retrieving at least one of the aforementioned unavailable shared datasets from the aforementioned data storage.

[0211] according to Figure 34 The variations of the illustrated process provide exemplary details of the acquisition operation, which are independent of each other. Such an exemplary acquisition operation according to an exemplary embodiment may include: forwarding the at least one available shared dataset identifier to the data storage; and receiving the acquired data from the data storage, the acquired data including the at least one unavailable shared dataset in explicit form.

[0212] The above overview and specified example embodiments are explained below using more specific terminology.

[0213] Specifically, to address the current limitation that shared data can only be retrieved based on shared data ID, according to the example embodiment, if supported, the NF consumer of the Nudm_SDM service can retrieve shared data from the UDM based on the type of shared data. Some portions of the retrieved shared data can be used immediately by the NF consumer and can be stored for later use, while other portions may not be used immediately but can be stored for later use, thus avoiding the need to retrieve data later. Avoiding the need for subsequent data retrieval helps reduce signaling load and system stability.

[0214] Figure 35 A schematic diagram of a signaling sequence according to an example embodiment is shown.

[0215] like Figure 35 As shown in the example flow, according to the example embodiment, the AMF sends a GET request to the UDM to retrieve all shared data of type AM-Data (not just the shared data with ID 17). This request may include the query parameter shared-data-ID=17 to indicate the current requirement ( Figure 35 (not shown in the image), but in addition, the query parameter type=AM-Data can be included to indicate the desire / ability to receive additional shared AM-Data for later use.

[0216] Similarly, according to the example embodiment, a GET request is sent from the UDM to the UDR.

[0217] Therefore, according to the example embodiment, the 200 OK response message not only contains the shared data of ID 17 (which is needed immediately at the AMF), but also other shared AM data and its ID (which can be used later at the AMF).

[0218] According to the example embodiment, the UDM / UDR includes shared data with ID=17 in the response, and may also include all shared data or a subset of all shared data of type AM-Data.

[0219] After the AMF receives the shared data, according to the example embodiment, the AMF uses all received IDs to subscribe to shared data change notifications.

[0220] According to another example embodiment, if supported, the NF consumer of the Nudm_SDM service can retrieve shared data from the UDM based on different filter information stored in the shared data. For example, each shared data object contains metadata information elements (IEs), such as... • Slices are allowed: Slice 1, Slice 2, ... • Allowed PLMNs: PLMn1, PLMN2, ... • Allowed NF consumers: AMF, SMF, ...

[0221] According to the example embodiment, based on the metadata stored in the shared data object, the shared data object can be isolated by slice, PLMN or the requested consumer NF type.

[0222] According to the example implementation, a supporting feature is defined for the above behavior, and if the UDM or UDR supports the feature, the NF consumer will only use the query parameter "type".

[0223] Figure 36 A schematic diagram of a signaling sequence according to an example embodiment is shown.

[0224] like Figure 36 As shown in the example embodiment, the NF service consumer accordingly requests shared data and more filtering elements, such as Slice=Slice1 and type=SMData. UDM / UDR provides shared data with type=SMData and AllowedSlice=Slice1. This advantageously leads to more filters that allow shared data to be saved at different granularities; that is, if SMF supports slice1, it can download smData that is only applicable to slice1.

[0225] Figure 37 A schematic diagram of a signaling sequence according to an example embodiment is shown.

[0226] like Figure 37 As shown, according to an example embodiment, an NF service consumer (e.g., AMF or UDM) may provide one or more shared data types in a request to subscribe to notifications about changes to UDM or UDR data.

[0227] Then, the UDM or UDR stores a subscription to notifications for changes to all shared data IDs that match the specified type, and provides notifications when these shared data changes.

[0228] According to the example implementation, a supporting feature can be defined for the above behavior, and if the UDM or UDR supports the feature, the NF consumer will subscribe to notifications of changes in the shared data type.

[0229] Figure 38 A schematic diagram of a signaling sequence according to an example embodiment is shown.

[0230] like Figure 38 As shown, according to the example embodiment, subscriptions can be combined with instant reporting requests to achieve the combination of retrieval and subscription as described above.

[0231] According to the example embodiment, Figure 38The process can be modified because the NF service consumer provides a structure as input that indicates the conditions of the data to be subscribed to, rather than indicating "subscribe data = shared data type X".

[0232] According to the example embodiment, the structure can be defined as follows:

[0233] Based on the above inputs / filters, NF service consumers can subscribe to, for example, all shared data entries containing the attribute "sharedVnGroupDatas", i.e., all shared database entries containing virtual network data, or any other possible combination.

[0234] The aforementioned method for resolving the identified problem, which so far only allows retrieval of shared data based on shared data ID, requires downloading all shared data of a specific type (e.g., AM data) to the AMF, regardless of whether the AMF will provide services to UEs that require that data.

[0235] According to the example embodiment, in order to address this problem and the fact that the data retrieval mechanism of the Nudm and Nudr interfaces can only be implemented through two consecutive retrieval steps, the following optimizations are provided.

[0236] Figure 39 A schematic diagram of a signaling sequence according to an example embodiment is shown.

[0237] like Figure 39 As shown, according to an example embodiment, an NF service consumer (e.g., AMF or UDM) may include a list of shared data IDs in a request to retrieve data from a UDM or UDR. These shared data IDs are used to identify shared data stored locally (e.g., as a "query" parameter in an HTTP request).

[0238] If the UDM or UDR determines that the NF service consumer does not reference some shared data in the requested data, then, according to an example embodiment, the UDM or UDR may also include both the shared data ID and the actual shared data for that shared data ID in its response to the request to retrieve the data.

[0239] Figure 40 A schematic diagram of a signaling sequence according to an example embodiment is shown.

[0240] like Figure 40As shown, according to an example embodiment, an NF service consumer (e.g., AMF or UDM) may include a list of shared data IDs in a request to subscribe to notifications about data changes to some indication of subscribed data to the UDM or UDR. These shared data IDs are used to identify the shared data stored locally (e.g., as a "query" parameter in an HTTP request).

[0241] If the UDM or UDR determines that the NF service consumer does not reference some shared data in its subscription data, then, according to an example embodiment, the UDM or UDR stores subscriptions for notifications of changes to this shared data and subsequently provides notifications including both the shared data ID and the actual changed shared data whenever any shared data changes.

[0242] In response to a subscription request, the UDM / UDR preferably includes information about the subscription for each of these shared data IDs, as well as a separate subscription ID for each of these subscriptions. These subscription IDs can be used by the NF service consumer for subsequent requests to modify or terminate the relevant subscription.

[0243] Figure 41 A schematic diagram of a signaling sequence according to an example embodiment is shown.

[0244] like Figure 41 As shown, according to the example embodiment, subscriptions can be combined with instant reporting requests to achieve the combination of retrieval and subscription as described above.

[0245] According to the example implementation, a supporting feature can be defined for the above behavior, and the NF consumer will only use the query parameter "Available Shared Data" if the UDM or UDR supports the feature.

[0246] Figure 42 A schematic diagram of a signaling sequence according to an example embodiment is shown.

[0247] like Figure 42 As shown in the example embodiment, when the AMF sends a first GET request to the UDM, it can indicate to the AMF a list of shared data IDs available / stored for that specific data type (e.g., AM data).

[0248] According to the example embodiment, if the UDM determines that the AMF already has a shared data ID associated with the UE, the UDM will send the shared data ID to the AMF in response.

[0249] If the UDM determines that the AMF does not have shared data associated with the UE, then according to the example embodiment, the UDM first retrieves the shared data from the UDR, including both the shared data ID associated with the UE subscription and the actual shared data corresponding to that shared data ID.

[0250] In this way, AMF does not require a second query to retrieve shared data with a shared data ID or shared data type. A single query is sufficient to provide the necessary data. Furthermore, AMF does not need to store some shared data that may not all be used.

[0251] The UDM still needs to perform two queries. First, it retrieves the AM data. Then, if the AM data has a shared data ID, and the shared data ID is not in the list provided by the AMF, the UDM further queries the UDR to retrieve the shared data, and includes both the shared data ID and the shared data in the response.

[0252] AMF requires a subscription operation to be performed once for each shared data ID in order to subscribe to notifications of changes to the shared data.

[0253] Therefore, in addition to the aforementioned optimizations to the interface between the consumer (e.g., AMF) and the UDM, according to the example embodiment, similar optimizations are also provided for the interface between the UDM and the UDR: accordingly, the first GET message sent from the UDM to the UDR (see...) Figure 42 The UDR expands the list with available shared AM data. Then, it checks if the AM data requested by the UDM contains a shared data ID pointing to shared data that is not yet available on the UDM. If so, the UDR not only sends the requested AM data to the UDM but also does not send the shared data in a 200 OK response message. By doing so, a second GET message (and a 200 OK response message) is avoided.

[0254] After the data is retrieved, the consumer may want to subscribe to data change notifications by sending a POST request message to the UDM / UDR, requesting the UDM / UDR to send a notification message to the consumer when the data at the UDM / UDR is modified (e.g., due to data configuration operations at the UDM / UDR). This is to ensure data consistency between the consumer (such as the AMF) and the UDM / UDR. The two-step method above (i.e., retrieval (GET), followed by subscription to change notifications (POST)) has been optimized to allow a single-step process by omitting the GET request and extending the POST request with an immediate data reporting indication. The UDM / UDR not only monitors the data to detect changes so that it can send notifications to the consumer when the data changes, but also includes the current value of the monitored data in the POST response message confirming the subscription request.

[0255] In this situation, the following may occur.

[0256] Consumers (e.g., AMF) send a POST request message to UDM, which includes an immediate reporting instruction to subscribe to AM data change notifications and retrieve AM data (similar to UDM to UDR).

[0257] However, the AM data sent back in the POST response may contain a shared data ID to indicate that the AM data is incomplete and needs to be expanded / merged with some shared data. Therefore, the AMF (if it is not already caching shared data or subscribing to shared data change notifications) needs to retrieve and subscribe to the shared data.

[0258] Therefore, in addition to the aforementioned optimizations to the interface between consumers, according to the example embodiment, additional signaling (retrieval and subscription of shared data) is avoided by including a list of shared data IDs in the subscription request message (POST) with an immediate response indicator. These shared data IDs identify shared data that is already available (and for which data change notifications have been subscribed) at the consumer (e.g., AMF).

[0259] Then, the UDM checks whether the AM data to be sent in the POST response contains a shared data ID pointing to shared data that is not yet available and has not been subscribed to by the AMF. If so, according to the example embodiment, not only the requested AM data is sent to the AMF, but also the shared data in the POST response is sent to the AMF. Furthermore, the UDM monitors not only the AM data but also the shared data so that it can send notifications to the consumer (e.g., the AMF) not only when the AM data changes but also when the shared data changes.

[0260] To further address the identified issues, based on the example implementation, the data retrieval mechanism for the Nudm and Nudr interfaces, which can currently be implemented through only two consecutive retrieval steps, provides the following optimizations.

[0261] Figure 43 A schematic diagram of a signaling sequence according to an example embodiment is shown.

[0262] like Figure 43 As shown, according to an example embodiment, an NF service consumer (e.g., an AMF or UDM) sends a request to the UDM or UDR for retrieved data. In some embodiments, the NF service consumer provides query parameters or indicates supporting features to request the UDM or UDR to include shared data in the response. Based on the NF consumer's subscription to shared data IDs, the UDM or UDR determines whether the NF service consumer does not have some shared data referenced in the requested data. That is, the principle behind these example embodiments is that the UDM or UDR assumes the NF consumer already has the shared data IDs it previously subscribed to.

[0263] If the NF service consumer does not reference some shared data in the requested data, according to the example embodiment, the UDM or UDR also includes both the shared data ID and the actual shared data of that shared data ID in its response to the request to retrieve the data.

[0264] Figure 44 A schematic diagram of a signaling sequence according to an example embodiment is shown.

[0265] like Figure 44 As shown, according to an example embodiment, an NF service consumer (e.g., an AMF or a UDM) can request a subscription from a UDM or UDR for notifications of data changes to some specified subscription data. In some embodiments, the NF service consumer provides query parameters or indication support features to request the UDM or UDR to include shared data in the subscription.

[0266] Based on the existing subscriptions to the shared data IDs of the NF consumer, the UDM or UDR determines whether the NF service consumer does not have a subscription to some shared data IDs referenced in the subscription data.

[0267] If the UDM or UDR determines that the NF service consumer does not have a subscription for some shared data referenced in the subscription data, then according to the example embodiment, the UDM or UDR stores subscriptions for notifications of changes to these shared data and provides notifications including both the shared data ID and the actual changed shared data when any shared data changes.

[0268] In response to a subscription request, the UDM / UDR preferably includes information about the subscription for each of these shared data IDs, as well as a separate subscription ID for each of these subscriptions. These subscription IDs can be used by the NF service consumer for subsequent requests to modify or terminate the relevant subscription.

[0269] Figure 45 A schematic diagram of a signaling sequence according to an example embodiment is shown.

[0270] like Figure 45 As shown, according to the example embodiment, subscriptions can be combined with instant reporting requests to achieve the combination of retrieval and subscription as described above.

[0271] According to the example implementation, a supporting feature can be defined for the above behavior. If the UDM or UDR supports the feature, the NF consumer will only use the query parameter "includeShared data".

[0272] As described above, the method for solving the identified problem that the data retrieval mechanism of the Nudm and Nudr interfaces can only be implemented through two consecutive retrieval steps, and the method for further solving the problem that the data retrieval mechanism of the Nudm and Nudr interfaces can only be implemented through two consecutive retrieval steps, can be combined with the method for solving the identified problem that the shared data can only be retrieved based on the shared data ID, as described above.

[0273] In particular, as mentioned above, the method for solving the problem that, to date, shared data can only be retrieved based on shared data IDs can be used to constrain the shared data that UDM / UDR will return, in order to solve the problem that, to date, the data retrieval mechanism of the Nudm and Nudr interfaces can only be implemented through two consecutive retrieval steps, as discussed above, and to further solve the problem that, to date, the data query mechanism of the Nudm and Nudr interfaces can be implemented through two adjacent retrieval steps.

[0274] For example, if an NF service consumer provides (or UDM / UDR determines) information about ID1 and ID4 in its request, but is only interested in specific types of shared data or shared data that meets certain conditions, and the UDM determines to return ID17 and ID21, but ID17 does not meet the conditions indicated in the consumer's request, then only ID21 will be returned.

[0275] The basic principles of the example implementation can be specified / standardized as follows.

[0276] Access and mobility subscription data retrieval can be defined as follows.

[0277] Figure 46 (“Request for UE Access and Mobility Subscription Data”) illustrates a schematic diagram of a signaling sequence according to an example embodiment, and in particular illustrates a scenario in which an NF serving consumer (such as an AMF) sends a request to a UDM to receive UE access and mobility subscription data (see also 3GPP TS 23.502[3]). Figure 4 2.2.2.2-1 Step 14). The request includes the UE's identity ( / {supi}), the type of requested information ( / am data), and query parameters (supported features, plmn id, shared data id).

[0278] At point 1, the NF service consumer (e.g., AMF) sends a GET request to a resource representing the UE's access and mobility subscription data, where query parameters indicate supporting features and / or plmn id and / or shared data id.

[0279] NF service consumers can include an optional query parameter, shared data id, to indicate to the UDM that the shared AccessAndMobilitySubscriptionData identified by the shared data id is available at the NF service consumer.

[0280] At 2a, upon success, the UDM responds with a "200 OK" message body containing the UE's access and mobility subscription data associated with the requesting NF service consumer. If the UE's access and mobility subscription data contains the attribute sharedAmDataID that identifies shared AccessAndMobilitySubscriptionData, and these IDs are not yet available at the NF consumer (i.e., the shared data ID is not included in the shared data ID query parameter in the GET request message), the UE's access and mobility subscription data sent in the 200 OK message body may also include a list of shared access and mobility subscription data associated with the UE but not yet available at the NF service consumer.

[0281] Note 1: If the UDM initiates a request to obtain SoR information from the SoR-AF, the UDM will start an operator-configurable timer, and before the timer expires, the UDM shall wait for a response from the SoR-AF to retrieve the SoR information. Before the timer expires, the UDM responds to the NF service consumer's access and mobility subscription data retrieval service operation. If the SOR-AF does not provide a response with SOR information before the timer expires, the UDM shall operate in accordance with Clause C.2 of 3GPP TS 23.122

[20] (step 3d). As described in Clause C.2 of 3GPP TS 23.122

[20] (step 4), if the UDM supports SOR-CMCI, the UDM instructs the transmission of an acknowledgment in its response to the NF service consumer (i.e., AMF), which will include "ME support for SOR-CMCI". If the UE is performing initial or emergency registration, the UDM will also remove “ME support for SOR-CMCI” to update the AuthenticationSoR of the Nudr_DataRepository service as specified in Clause 5.2.25 of 3GPP TS 29.505

[10] . The UDM will determine whether to provide SOR-CMCI based on the “usimSupportOfSorCmci” retrieved by the AuthenticationSoR of the Nudr_DataRepository service as specified in Clause 5.2.25 of 3GPP TS 29.505

[10] .

[0282] At 2b, if the UE has not successfully subscribed to data, the HTTP status code “404 Not Found” should be returned, which includes other error information in the response body (in the “ProblemDetails” element).

[0283] Note 2: Upon receiving any Nudm_EventExposure or Nudm_PP operation, or when the validity of the event subscription or configuration parameters and their associated maximum latency, maximum response time, or DL ​​buffer suggested packet count value expires, the UDM may need to adjust the values ​​of the active time and / or periodically registered timers and / or DL ​​buffer suggested packet count. If the value is updated, the UDM shall notify the AMF and / or SMF (see Sections 4.15.3.2.3b and 4.15.6.3a of 3GPP TS 23.502[3].

[0284] Note 3: If UPU data has been configured previously but has not yet been confirmed by the UE, for example, because the AMF was not registered during configuration, the UDM needs to transmit the UPU data (after AMF protection) to the AMF within 200 OK AccessAndMobilitySubscriptionData.

[0285] In the event of failure, an appropriate HTTP status code indicating the error should be returned, and appropriate additional error information should be returned in the body of the GET response.

[0286] The definition of data change notification subscription is as follows.

[0287] Figure 47 (“NF Service Consumer Subscription Notification”) illustrates a schematic diagram of a signaling sequence according to an example embodiment, and in particular illustrates a scenario in which an NF service consumer sends a request to the UDM for a notification of changes to subscription data (see also 3GPP TS 23.502[3]). Figure 4 Step 14 (2.2.2.2-1). This request includes the callback URI and the URI of the monitored resource.

[0288] At point 1, the NF service consumer sends a POST request to the parent resource (subscription set) (... / {ueId} / sdm subscription) to create the subscription that exists in the message body. The payload body of the POST request should contain a representation of the individual subscription resource to be created. NF consumers supporting the “LimitedSubscriptions” feature should create a unique subscription for each UE (identified by the ueId in the URI) without attaching any filtering criteria, or using specific filtering criteria (e.g., dnn and / or singleNssai), and set the “uniqueSubscription” IE to the value “true” in the request body.

[0289] At point 2a, upon success, UDM responds with a "201 Created" response, where the message body contains an indication that the subscription has been created. The location HTTP header should include the URI for creating the subscription.

[0290] If the SdmSubscription received in the POST request contains an immediateReport instruction, the SdmSubscription in the "201Created" response may also contain a report attribute, which has a current representation of the subscription data.

[0291] Furthermore, if the received POST request includes an optional query parameter, Shared Data ID, to identify shared data available (and subscribed) at the NF service consumer, and the current representation of the subscribed data includes shared data IDs identifying shared data not yet available (and not subscribed) at the NF service consumer, then the current representation of the subscribed data sent in the "201 Created" response should also include shared data not yet available to the NF service consumer. Additionally, the UDM can add the resource URIs of unsubscribed shared data to the list of monitored resource URIs received in the request and monitor this shared data.

[0292] If partially successful, the "201 Created" result should only contain the Uris monitoring resource supported by UDM.

[0293] In 2b, if the UE does not have valid subscription data, the HTTP status code "404 Not Found" should be returned, which includes other error information in the response body (in the "ProblemDetails" element).

[0294] At 2c, if the UE subscription data exists but the requested data change notification subscription cannot be created (e.g., due to an invalid / unsupported data reference to be monitored contained in the SdmSubscription parameter), the HTTP status code "501 Not Implemented" should be returned, including other error information in the response body (in the "ProblemDetails" element).

[0295] The "501 NotImplemented" error will only be returned if UDM does not support all montitoredResourceUris.

[0296] In the event of failure, the appropriate HTTP status code indicating the error should be returned, and appropriate additional error information should be returned in the body of the POST response.

[0297] POST can be defined as follows.

[0298] This method should support the URI lookup parameters specified in the following table ("URI lookup variables supported by the POST method on this resource").

[0299] This method should support the request data structures specified in the following table ("Data structures supported by the POST request body on this resource").

[0300] This method should support the response data structures and response codes specified in the following table ("Data structures supported by the POST response body on this resource").

[0301] Note: In the case of a stateless UDM deployment, it is assumed that the stateless UDMs are organized into several UDM groups, and an FQDN can be assigned to each UDM group.

[0302] The following table defines the headers supported by the 201 response code pair for this resource.

[0303] GET can be defined as follows.

[0304] This method should support the URI query parameters specified in the following table ("URI query parameters supported by the GET method on this resource").

[0305] If “plmn-id” is included, the UDM should return the access and mobility data of the SUPI associated with the plmn or SNPN identified by “plmn-id”.

[0306] If “plmn-id” is not included, the UDM should return the access and mobility data of the SUPI associated with the HPLMN.

[0307] This method should support the request data structures specified in the following table ("Data structures supported by the GET request body on this resource").

[0308] This method should support the response data structures and response codes specified in the following table ("Data structures supported by the GET response body on this resource").

[0309] The following table defines the headers supported by the GET method on this resource.

[0310] The following table defines the headers supported by the 200 response code for this resource.

[0311] The type AccessAndMobilitySubscriptionData can be defined as follows:

[0312] The definition of the AccessAndMobilitySubscriptionData type is shown in the table below. The Nudm_SDM API can be defined as follows: OpenAPI: 3.0.0 For clarity, the text is not shown. / {supi} / am-data: get: Summary: Retrieve UE access and mobility subscription data. operationId: GetAmData tags: Access and mobility subscription data retrieval security: - {} - oAuth2ClientCredentials: - nudm-sdm - oAuth2ClientCredentials: - nudm-sdm - nudm-sdm:am-data:read parameters: - name: supi in: path Description: UE identifier required: true schema: $ref: 'TS29571_CommonData.yaml# / components / schemas / Supi' - name: supported-features in: query Description: Supported features schema: $ref: 'TS29571_CommonData.yaml# / components / schemas / SupportedFeatures' - name: plmn-id in: query Description: Service PLMN ID or SNPN ID content: application / json: schema: $ref: 'TS29571_CommonData.yaml# / components / schemas / PlmnIdNid' - name: adjacent-plmns in: query Description: List of PLMNs adjacent to the UE's serving PLMN schema: type: array items: $ref: 'TS29571_CommonData.yaml# / components / schemas / PlmnId' minItems: 1 style: form explode: false - name: disaster-roaming-ind in: query Description: Instructions on whether to apply disaster roaming services. required: false schema: type: boolean default: false - name: shared-data-ids in: query Description: A list of IDs identifying shared access and mobility subscription data that are already available at the NF service consumer. schema: type: array items: $ref: '# / components / schemas / SharedDataId' style: form explode: false - name: If-None-Match in: header Description: A validator for conditional requests, as described in RFC 7232, 3.2. schema: type: string - name: If-Modified-Since in: header Description: A validator for conditional requests, as described in RFC 7232, 3.3. schema: type: string responses: '200': Description: Expected response to a valid request. content: application / json: schema: $ref: '# / components / schemas / AccessAndMobilitySubscriptionData' headers: Cache-Control: Description: Includes cache control with maximum age, as described in RFC 7234, 5.2. schema: type: string ETag: Description: Entity tag containing a strong validator, as described in RFC 7232, 2.3. schema: type: string Last-Modified: Description: The timestamp of the resource's last modification, as described in RFC 7232, 2.2. schema: type: string '400': $ref: 'TS29571_CommonData.yaml# / components / responses / 400' '401': $ref: 'TS29571_CommonData.yaml# / components / responses / 401' '403': $ref: 'TS29571_CommonData.yaml# / components / responses / 403' '404': $ref: 'TS29571_CommonData.yaml# / components / responses / 404' '406': $ref: 'TS29571_CommonData.yaml# / components / responses / 406' '429': $ref: 'TS29571_CommonData.yaml# / components / responses / 429' '500': $ref: 'TS29571_CommonData.yaml# / components / responses / 500' '502': $ref: 'TS29571_CommonData.yaml# / components / responses / 502' '503': $ref: 'TS29571_CommonData.yaml# / components / responses / 503' default: description: Unexpected error The text is not shown for clarity / {ueId} / sdm-subscriptions: post: summary: Subscription to notifications operationId: Subscribe tags: - Subscription Creation security: - {} - oAuth2ClientCredentials: - nudm-sdm - oAuth2ClientCredentials: - nudm-sdm - nudm-sdm:sdm-subscriptions:create parameters: - name: ueId in: path Description: User's identity required: true schema: $ref: 'TS29571_CommonData.yaml# / components / schemas / VarUeId' - name: shared-data-ids in: query Description: A list of IDs that identify the shared data that NF service consumers have subscribed to. schema: type: array items: $ref: '# / components / schemas / SharedDataId' style: form explode: false requestBody: content: application / json: schema: $ref: '# / components / schemas / SdmSubscription' required: true responses: '201': Description: Expected response to a valid request. content: application / json: schema: $ref: '# / components / schemas / SdmSubscription' headers: Location: Description: 'Based on the structure, contains the URI of the newly created resource: {apiRoot} / nudm-sdm / ' <apiversion> / {ueId} / sdm-subscriptions / {subscriptionId}' required: true schema: type: string '400': $ref: 'TS29571_CommonData.yaml# / components / responses / 400' '401': $ref: 'TS29571_CommonData.yaml# / components / responses / 401' '403': $ref: 'TS29571_CommonData.yaml# / components / responses / 403' '404': $ref: 'TS29571_CommonData.yaml# / components / responses / 404' '411': $ref: 'TS29571_CommonData.yaml# / components / responses / 411' '413': $ref: 'TS29571_CommonData.yaml# / components / responses / 413' '415': $ref: 'TS29571_CommonData.yaml# / components / responses / 415' '429': $ref: 'TS29571_CommonData.yaml# / components / responses / 429' '500': $ref: 'TS29571_CommonData.yaml# / components / responses / 500' '501': $ref: 'TS29571_CommonData.yaml# / components / responses / 501' '502': $ref: 'TS29571_CommonData.yaml# / components / responses / 502' '503': $ref: 'TS29571_CommonData.yaml# / components / responses / 503' default: description: Unexpected error callbacks: datachangeNotification: '{request.body# / callbackReference}': post: requestBody: required: true content: application / json: schema: $ref: '# / components / schemas / ModificationNotification' responses: '204': description: Successful notification response '307': $ref: 'TS29571_CommonData.yaml# / components / responses / 307' '308': $ref: 'TS29571_CommonData.yaml# / components / responses / 308' '400': $ref: 'TS29571_CommonData.yaml# / components / responses / 400' '401': $ref: 'TS29571_CommonData.yaml# / components / responses / 401' '403': $ref: 'TS29571_CommonData.yaml# / components / responses / 403' '404': $ref: 'TS29571_CommonData.yaml# / components / responses / 404' '411': $ref: 'TS29571_CommonData.yaml# / components / responses / 411' '413': $ref: 'TS29571_CommonData.yaml# / components / responses / 413' '415': $ref: 'TS29571_CommonData.yaml# / components / responses / 415' '429': $ref: 'TS29571_CommonData.yaml# / components / responses / 429' '500': $ref: 'TS29571_CommonData.yaml# / components / responses / 500' '502': $ref: 'TS29571_CommonData.yaml# / components / responses / 502' '503': $ref: 'TS29571_CommonData.yaml# / components / responses / 503' default: description: Unexpected error dataRestorationNotification: '{request.body# / dataRestorationCallbackUri}': post: requestBody: required: true content: application / json: schema: $ref: 'TS29503_Nudm_UECM.yaml# / components / schemas / DataRestorationNotification' responses: '204': description: Successful notification response '307': $ref: 'TS29571_CommonData.yaml# / components / responses / 307' '308': $ref: 'TS29571_CommonData.yaml# / components / responses / 308' '400': $ref: 'TS29571_CommonData.yaml# / components / responses / 400' '404': $ref: 'TS29571_CommonData.yaml# / components / responses / 404' '409': $ref: 'TS29571_CommonData.yaml# / components / responses / 409' '500': $ref: 'TS29571_CommonData.yaml# / components / responses / 500' '503': $ref: 'TS29571_CommonData.yaml# / components / responses / 503' default: Description: Unexpected error For clarity, the text is not shown. AccessAndMobilitySubscriptionData: type: object properties: supportedFeatures: $ref: 'TS29571_CommonData.yaml# / components / schemas / SupportedFeatures' gpsis: type: array items: $ref: 'TS29571_CommonData.yaml# / components / schemas / Gpsi' hssGroupId: $ref: 'TS29571_CommonData.yaml# / components / schemas / NfGroupId' internalGroupIds: type: array items: $ref: 'TS29571_CommonData.yaml# / components / schemas / GroupId' minItems: 1 sharedVnGroupDataIds: Description: Mapping (list of key-value pairs), where GroupId is the key of SharedDataId. type: object Additional Properties: $ref: '# / components / schemas / SharedDataId' minProperties: 1 subscribedUeAmbr: $ref: 'TS29571_CommonData.yaml# / components / schemas / AmbrRm' nssai: $ref: '# / components / schemas / Nssai' ratRestrictions: type: array items: $ref: 'TS29571_CommonData.yaml# / components / schemas / RatType' uniqueItems: true forbiddenAreas: type: array items: $ref: 'TS29571_CommonData.yaml# / components / schemas / Area' serviceAreaRestriction: $ref: 'TS29571_CommonData.yaml# / components / schemas / ServiceAreaRestriction' coreNetworkTypeRestrictions: type: array items: $ref: 'TS29571_CommonData.yaml# / components / schemas / CoreNetworkType' accessTypeRestrictions: type: array items: $ref: 'TS29571_CommonData.yaml# / components / schemas / AccessType' maxItems: 2 rfspIndex: $ref: 'TS29571_CommonData.yaml# / components / schemas / RfspIndexRm' subsRegTimer: $ref: 'TS29571_CommonData.yaml# / components / schemas / DurationSecRm' ueUsageType: $ref: '# / components / schemas / UeUsageType' mpsPriority: $ref: '# / components / schemas / MpsPriorityIndicator' mcsPriority: $ref: '# / components / schemas / McsPriorityIndicator' activeTime: $ref: 'TS29571_CommonData.yaml# / components / schemas / DurationSecRm' sorInfo: $ref: '# / components / schemas / SorInfo' sorInfoExpectInd: type: boolean sorafRetrieval: type: boolean default: false sorUpdateIndicatorList: type: array items: $ref: '# / components / schemas / SorUpdateIndicator' minItems: 1 upuInfo: $ref: '# / components / schemas / UpuInfo' routingIndicator: type: string pattern: '^[0-9]{1,4}$' micoAllowed: $ref: '# / components / schemas / MicoAllowed' sharedAmDataIds: type: array items: $ref: '# / components / schemas / SharedDataId' minItems: 1 odbPacketServices: $ref: 'TS29571_CommonData.yaml# / components / schemas / OdbPacketServices' subscribedDnnList: type: array items: anyOf: - $ref: 'TS29571_CommonData.yaml# / components / schemas / Dnn' - $ref: 'TS29571_CommonData.yaml# / components / schemas / WildcardDnn' serviceGapTime: $ref: 'TS29571_CommonData.yaml# / components / schemas / DurationSec' mdtUserConsent: $ref: '# / components / schemas / MdtUserConsent' mdtConfiguration: $ref: 'TS29571_CommonData.yaml# / components / schemas / MdtConfiguration' traceData: $ref: 'TS29571_CommonData.yaml# / components / schemas / TraceData' cagData: $ref: '# / components / schemas / CagData' stnSr: $ref: 'TS29571_CommonData.yaml# / components / schemas / StnSr' cMsisdn: $ref: 'TS29571_CommonData.yaml# / components / schemas / CMsisdn' nbIoTUePriority: $ref: '# / components / schemas / NbIoTUePriority' nssaiInclusionAllowed: type: boolean default: false rgWirelineCharacteristics: $ref: 'TS29571_CommonData.yaml# / components / schemas / RgWirelineCharacteristics' ecRestrictionDataWb: $ref: '# / components / schemas / EcRestrictionDataWb' ecRestrictionDataNb: type: boolean default: false expectedUeBehaviourList: $ref: '# / components / schemas / ExpectedUeBehaviourData' primaryRatRestrictions: type: array items: $ref: 'TS29571_CommonData.yaml# / components / schemas / RatType' uniqueItems: true secondaryRatRestrictions: type: array items: $ref: 'TS29571_CommonData.yaml# / components / schemas / RatType' uniqueItems: true edrxParametersList: type: array items: $ref: '# / components / schemas / EdrxParameters' minItems: 1 ptwParametersList: type: array items: $ref: '# / components / schemas / PtwParameters' minItems: 1 iabOperationAllowed: type: boolean default: false adjacentPlmnRestrictions: description: Mapping of PlmnRestriction (list of key-value pairs where PlmnId is the key) type: object additionalProperties: $ref: '# / components / schemas / PlmnRestriction' minProperties: 1 wirelineForbiddenAreas: type: array items: $ref: 'TS29571_CommonData.yaml# / components / schemas / WirelineArea' wirelineServiceAreaRestriction: $ref: 'TS29571_CommonData.yaml# / components / schemas / WirelineServiceAreaRestriction' pcfSelectionAssistanceInfos: type: array items: $ref: '# / components / schemas / PcfSelectionAssistanceInfo' minItems: 1 aerialUeSubInfo: $ref: '# / components / schemas / AerialUeSubscriptionInfo' roamingRestrictions: $ref: 'TS29571_CommonData.yaml# / components / schemas / RoamingRestrictions' remoteProvInd: type: boolean default: false 3gppChargingCharacteristics: $ref: '# / components / schemas / 3GppChargingCharacteristics' timeSyncData: $ref: '# / components / schemas / TimeSyncData' sharedDataList: type: array items: $ref: '# / components / schemas / SharedData' minItems: 1 For clarity, the text is not shown.

[0313] The above processes and functions can be implemented by the various functional components, processors, etc., as described below.

[0314] In the exemplary description of the network entities described above, only functional blocks are used to describe units relevant to understanding the principles of this disclosure. A network entity may include other units required for its corresponding operation. However, descriptions of these units are omitted in this specification. The arrangement of functional blocks in the device should not be construed as limiting this disclosure; functionality may be performed by a single block or further subdivided into sub-blocks.

[0315] When the above description indicates that the device, i.e., the network entity (or some other component), is configured to perform certain functions, this should be interpreted as equivalent to the following description: that is, at least one processor or corresponding circuit system, potentially cooperating with computer program code stored in the memory of the corresponding device, is configured to cause the device to perform at least the aforementioned functions. Furthermore, such functions should be interpreted as being equivalently implemented by specially configured circuit systems or components for performing the corresponding functions (i.e., the expression "a unit configured as..." is interpreted as equivalent to expressions such as "a component for...").

[0316] exist Figure 48 Alternate illustrations of a device according to an example embodiment are depicted. Figure 48 As shown, according to an example embodiment, device (network node) 10' (corresponding to network node 10) includes a processor 481, a memory 482, and an interface 483, which are connected via a bus 484, etc. Furthermore, according to an example embodiment, device (network node) 30' (corresponding to network node 30) includes a processor 481, a memory 482, and an interface 483, which are connected via a bus 484, etc. Furthermore, according to an example embodiment, device (network node) 50' (corresponding to network node 50) includes a processor 481, a memory 482, and an interface 483, which are connected via a bus 484, etc. Furthermore, according to an example embodiment, device (network node) 70' (corresponding to network node 70) includes a processor 481, a memory 482, and an interface 483, which are connected via a bus 484, etc. Furthermore, according to an example embodiment, device (network node) 90' (corresponding to network node 90) includes a processor 481, a memory 482, and an interface 483, which are connected via a bus 484, etc. Furthermore, according to an example embodiment, device (network node) 100' (corresponding to network node 100) includes a processor 481, a memory 482, and an interface 483, which are connected via a bus 484, etc. Furthermore, according to an example embodiment, device (network node) 120' (corresponding to network node 120) includes a processor 481, a memory 482, and an interface 483, which are connected via a bus 484, etc. Furthermore, according to an example embodiment, device (network node) 140' (corresponding to network node 140) includes a processor 481, a memory 482, and an interface 483, which are connected via a bus 484, etc. Furthermore, according to an example embodiment, device (network node) 160' (corresponding to network node 160) includes a processor 481, a memory 482, and an interface 483, which are connected via a bus 484, etc. Furthermore, according to an example embodiment, device (network node) 170' (corresponding to network node 170) includes a processor 481, a memory 482, and an interface 483, which are connected via a bus 484, etc. Furthermore, according to the example embodiment, device (network node) 190' (corresponding to network node 190) includes a processor 481, a memory 482, and an interface 483, which are connected via a bus 484, etc. Furthermore, according to the example embodiment, device (network node) 210' (corresponding to network node 210) includes a processor 481, a memory 482, and an interface 483, which are connected via a bus 484, etc. Devices (10', 30', 50', 70', 90', 100', 120', 140', 160', 170', 190', 210') can be connected to other devices, such as corresponding other devices among devices (10', 30', 50', 70', 90', 100', 120', 140', 160', 170', 190', 210'), via links 485.

[0317] Processor 481 and / or interface 483 may also include modems, etc., to facilitate communication over (hardwired or wireless) links, respectively. Interface 483 may include suitable transceivers coupled to one or more antennas or communication components for (hardwired or wireless) communication with (multiple) linked or connected devices, respectively. Interface 483 is typically configured to communicate with at least one other device (i.e., its interface).

[0318] Memory 482 may store a corresponding program, which is assumed to include program instructions or computer program code, which, when executed by a corresponding processor, enables the corresponding electronic device or apparatus to operate according to the example embodiment (particularly according to the reference). Figures 23 to 34 (any of the methods of interpretation).

[0319] Generally, the corresponding device / apparatus (and / or part thereof) can refer to a component used to perform the corresponding operation and / or demonstrate the corresponding function (especially with reference to...). Figures 23 to 34 Any of the methods of interpretation), and / or the corresponding device (and / or a part thereof) may have the function of performing the corresponding operation and / or displaying the corresponding function.

[0320] When a statement declares that a processor (or some other component) is configured to perform a certain function, this should be interpreted as equivalent to the description that at least one processor, potentially cooperating with computer program code stored in the memory of the corresponding device, is configured to cause the device to perform at least the aforementioned function. Furthermore, such function should be interpreted as being equivalently achievable by a specially configured component for performing the corresponding function (i.e., the expression "processor configured to [cause the device] to perform xxxing" is interpreted as equivalent to expressions such as "component for xxxing").

[0321] For more details regarding the operability / functionality of individual devices, please refer to the above combinations. Figures 1 to 47 Description of any one of them.

[0322] For the purposes of this disclosure as stated above, it should be noted that - Method steps that may be implemented as part of software code and run using a processor at a network server or network entity (as an example of a device, apparatus and / or its modules, or as an example of an entity that therefore includes an apparatus and / or modules) are independent of the software code and can be specified using any known or future-developed programming language, as long as the functionality defined by the method steps is preserved. - Generally, any method steps are suitable for implementation as software or by hardware without changing the idea of ​​the embodiment and its modifications in terms of the functions implemented; - Method steps and / or devices, units or components (e.g., devices performing the functions of the devices according to the above embodiments) that may be implemented as hardware components in the apparatus(s) or any of the modules thereof as defined above are hardware-independent and may be implemented using any known or future-developed hardware technology or any combination of such technologies, such as MOS (Metal-Oxide-Semiconductor), CMOS (Complementary MOS), BiMOS (Bipolar MOS), BiCMOS (Bipolar CMOS), ECL (Transmitter Coupled Logic), TTL (Transistor Transistor Logic), etc., using, for example, ASIC (Application-Specific Integrated Circuit) components, FPGA (Field-Programmable Gate Array) components, CPLD (Complex Programmable Logic Device) components or DSP (Digital Signal Processor) components; - Devices, units, or components (e.g., any of the network entities or network registers defined above, or their respective units / components) may be implemented as individual devices, units, or components, but this does not preclude them from being implemented in a distributed manner throughout the system, as long as the functionality of the devices, units, or components is preserved; Devices such as user equipment and network entities / network registers can be represented by semiconductor chips, chipsets, or (hardware) modules including such chips or chipsets; however, this does not preclude the possibility that the functionality of a device or module (rather than hardware implementation) can be implemented as software using (software) modules, such as computer programs or computer program products including executable software code portions for execution / running on a processor. - For example, a device can be considered as a unit or a component of more than one unit, whether they are functionally complementary or functionally independent but housed within the same device housing.

[0323] Generally, it should be noted that if a corresponding functional block or element according to the foregoing aspects is only suitable for performing the functions described above for the corresponding part, it can be implemented in hardware and / or software in any known manner. The above method steps can be implemented in individual functional blocks or by individual devices, or one or more of the method steps can be implemented in a single functional block or by a single device.

[0324] Generally, any method steps are suitable for implementation as software or in hardware without altering the spirit of this disclosure. Devices and components may be implemented as individual devices, but this does not preclude their implementation in a distributed manner throughout the system, provided that the functionality of the devices is preserved. These and similar principles are considered to be known to those skilled in the art.

[0325] Software in the sense of this specification includes software code, which itself includes code components or portions or computer programs or computer program products for performing corresponding functions; and software (or computer programs or computer program products) embodied on a tangible medium such as a computer-readable (storage) medium on which corresponding data structures or code components / portions are stored, or embodied in a signal or chip, potentially during its processing.

[0326] This disclosure also covers any possible combination of the above-described method steps and operations, as well as any possible combination of the above-described nodes, devices, modules or elements, provided that the concepts of the above-described method and structural arrangement are applicable.

[0327] In view of the above, measures for optimizing shared data retrieval are provided. Such measures exemplarily include sending a request for first data, the request including at least one available shared dataset identifier corresponding to at least one available shared dataset; and receiving a data response including compiled data, the compiled data including general data in explicit form, at least one unavailable shared dataset in explicit form, and at least one unavailable shared dataset identifier corresponding to the at least one unavailable shared dataset.

[0328] Although the present disclosure has been described above with reference to the accompanying drawings, it should be understood that the disclosure is not limited thereto. Rather, it will be apparent to those skilled in the art that the disclosure can be modified in various ways without departing from the scope of the inventive concept disclosed herein.

[0329] List of acronyms and abbreviations 3GPP: Third Generation Partnership Project UDM: Unified Data Management UDR: Unified Data Repository UE: User Equipment ID: Identifier NF: Network Functions AM: Access and Mobility IE: Information Elements AMF: Access and Mobility Management Functions< / apiversion>

Claims

1. A method for a network function service consumer, the method comprising: Send a request for data, the request including at least one shared dataset identifier corresponding to at least one shared dataset available to the network function service consumer; as well as Receive a response to the request for data, the response including compiled data, the compiled data including general data in explicit form, at least shared datasets in explicit form that are not available to the network function service consumer, and at least shared dataset identifiers corresponding to the at least one shared dataset that is not available to the network function service consumer.

2. The method according to claim 1, wherein the compiled data includes: At least one of the at least one shared dataset identifiers, the at least one shared dataset identifier corresponding to at least one shared dataset in the form of a reference that can be used by the consumer of the network function service.

3. An apparatus including a network function service consumer, configured to perform: Sending a request for data, the request including at least one shared dataset identifier corresponding to at least one shared dataset available to the network function service consumer; and Receive a response to the request for data, the response including compiled data, the compiled data including general data in explicit form, at least shared datasets in explicit form that are not available to the network function service consumer, and at least shared dataset identifiers corresponding to the at least one shared dataset that is not available to the network function service consumer.

4. The apparatus of claim 3, wherein the compilation data includes: At least one of the at least one shared dataset identifiers, the at least one shared dataset identifier corresponding to at least one shared dataset in the form of a reference that can be used by the consumer of the network function service.

5. An apparatus comprising: At least one processor; as well as At least one memory stores instructions for a network function service consumer, wherein the instructions, when executed by the at least one processor, cause the apparatus to perform the method according to claim 1 or 2.

6. A non-transient computer-readable medium comprising instructions for a network function service consumer, wherein the instructions, when executed by at least one processor of the device, cause the device to perform the method according to claim 1 or 2.

7. A computer program comprising instructions for a network function service consumer, wherein when the program is executed by a device, the instructions cause the device to perform the method according to claim 1 or 2.

8. A method for network entities, the method comprising: Receives a request for data from a network function service consumer, the request including at least one shared dataset identifier corresponding to at least one shared dataset available to the network function service consumer; The data is retrieved from the data storage as the retrieved data; The data based on the acquired data is compiled into compiled data, which includes general data in explicit form, at least one shared dataset in explicit form that is unavailable to the network function service consumer, and at least one shared dataset identifier corresponding to the at least one shared dataset that is unavailable to the network function service consumer; and Send a response to the request for the data, the response including the compiled data.

9. The method of claim 8, wherein the compiled data comprises: At least one of the at least one shared dataset identifiers, the at least one shared dataset identifier corresponding to at least one shared dataset in the form of a reference that can be used by the consumer of the network function service.

10. The method according to claim 8 or 9, further comprising: The acquired data is analyzed to determine whether the acquired data includes at least one shared dataset identifier corresponding to at least one shared dataset among at least one shared dataset that is not available to the network function service consumer; as well as Retrieve from the data storage at least one shared dataset corresponding to at least one shared dataset identifier that is unavailable to the network function service consumer.

11. The method of claim 9 or 9, wherein the acquisition further comprises: Forward the at least one shared dataset identifier corresponding to the at least one shared dataset in the at least one shared dataset that is unavailable to the network function service consumer to the data storage; as well as The data to be acquired is received from the data storage, the data including at least one shared dataset in an explicit form that is unavailable to the network function service consumer, and at least one shared dataset identifier corresponding to the at least one shared dataset that is unavailable to the network function service consumer.

12. An apparatus comprising a network entity configured to perform the method according to any one of claims 8 to 11.

13. An apparatus comprising: At least one processor; as well as At least one memory stores instructions for a network function service consumer, wherein the instructions, when executed by the at least one processor, cause the apparatus to perform the method according to any one of claims 8 to 11.

14. A non-transient computer-readable medium comprising instructions for a network function service consumer, wherein the instructions, when executed by at least one processor of the apparatus, cause the apparatus to perform the method according to any one of claims 8 to 11.

15. A computer program comprising instructions for a network function service consumer, wherein when the program is executed by a device, the instructions cause the device to perform the method according to any one of claims 8 to 11.

16. A method for a network function service consumer, comprising: Send a subscription request for data, the subscription request including at least one shared dataset identifier corresponding to at least one shared dataset available to the network function service consumer; as well as Messages are received based on the subscription request, the messages including information about at least one shared dataset related to the data and that the network function service consumer is unavailable.

17. The method of claim 16, wherein... The subscription request indicates an immediate reporting requirement, and The message is a subscription confirmation, which includes at least one shared dataset that is unavailable to the network function service consumer and at least one shared dataset identifier corresponding to the at least one shared dataset that is unavailable to the network function service consumer.

18. The method according to claim 16 or 17, further comprising: A subscription is established based on the acquired data for a shared dataset that is unavailable to the network function service consumer and is associated with the data, wherein the shared dataset that is unavailable to the network function service consumer includes at least one shared dataset that is unavailable to the network function service consumer, and wherein the message is a notification that includes information about changes to the at least one shared dataset that is unavailable to the network function service consumer, and at least one shared dataset identifier corresponding to the at least one shared dataset that is unavailable to the network function service consumer.

19. An apparatus comprising a network function service consumer configured to perform the method according to any one of claims 16 to 18.

20. An apparatus comprising: At least one processor; as well as At least one memory stores instructions for a network function service consumer, wherein the instructions, when executed by the at least one processor, cause the apparatus to perform the method according to any one of claims 16 to 18.

21. A non-transient computer-readable medium comprising instructions for a network function service consumer, wherein the instructions, when executed by at least one processor of the apparatus, cause the apparatus to perform the method according to any one of claims 16 to 18.

22. A computer program comprising instructions for a network function service consumer, wherein when the program is executed by a device, the instructions cause the device to perform the method according to any one of claims 16 to 18.

23. A method for network entities, comprising: A subscription request for data is received from a network function service consumer, the subscription request including at least one shared dataset identifier corresponding to at least one shared dataset available to the network function service consumer. The data is retrieved from the data storage as the retrieved data, and A message is sent based on the subscription request, the message including information about at least one shared dataset related to the data and that the network function service consumer is unavailable.

24. The method of claim 23, further comprising: The acquired data is analyzed to determine whether the acquired data includes at least one shared dataset identifier corresponding to at least one shared dataset that is not available to the network function service consumer.

25. The method according to claim 23 or 24, wherein The subscription request indicates an immediate reporting requirement, and The message is a subscription confirmation, which includes at least one shared dataset that is unavailable to the network function service consumer and at least one shared dataset identifier corresponding to the at least one shared dataset that is unavailable to the network function service consumer.

26. The method according to any one of claims 23 to 25, further comprising: Based on the acquired data, a subscription is established for a shared dataset that is unavailable to the network function service consumer and is related to the data. The shared dataset that is unavailable to the network function service consumer includes at least one other shared dataset that is unavailable to the network function service consumer. The message is a notification that includes information about changes to the at least one shared dataset that is unavailable to the network function service consumer, and at least one shared dataset identifier corresponding to the at least one shared dataset that is unavailable to the network function service consumer.

27. A network entity comprising components for performing the method according to any one of claims 23 to 26.

28. A network entity, comprising: At least one processor; as well as At least one memory stores instructions that, when executed by the at least one processor, cause the network entity to perform the method according to any one of claims 23 to 26.

29. A non-transient computer-readable medium comprising instructions that, when executed by at least one processor of a network entity, cause the network entity to perform the method according to any one of claims 23 to 26.

30. A computer program comprising instructions that, when executed by a network entity, cause the network entity to perform the method according to any one of claims 23 to 26.

Images