Apparatuses, methods, and computer programs for optimizing retrieval of shared data
By enabling data retrieval and subscription based on shared data types and conditions, the inefficiencies in current data retrieval mechanisms are addressed, reducing signaling loads and improving system stability in communication systems.
Patent Information
- Application Number
- PCT/IB2024/054610
- Authority / Receiving Office
- WO · WO
- Patent Type
- Applications
- Current Assignee / Owner
- Priority Date
- 2023-05-12
- Filing Date
- 2024-05-13
- Publication Date
- 2024-11-21
AI Technical Summary
Current data retrieval mechanisms in communication systems, such as 5G networks, are inefficient as they can only retrieve shared data based on shared data IDs, leading to increased signaling and extra steps in data retrieval processes.
Implementing methods and apparatuses that allow retrieval and subscription to shared data based on shared data types and conditions, such as attribute-value pairs, enabling simultaneous retrieval and notification of data changes, and optimizing data retrieval by including available shared data in responses to reduce the need for subsequent queries.
This approach reduces communication and signaling loads by allowing data retrieval and subscription based on types and conditions, minimizing the number of queries and improving system stability by providing immediate data availability and change notifications.
Smart Images

Figure IB2024054610_21112024_PF_FP_ABST
Abstract
Description
APPARATUSES, METHODS, AND COMPUTER PROGRAMS FOR OPTIMIZING RETRIEVAL OF SHARED DATARelated Applications
[0001] This application claims the benefit of priority of Indian Provisional Patent Application No. 202341033726 filed May 12, 2024, which is hereby incorporated by reference as if reproduced in its entirety.Field
[0002] Various example embodiments relate to optimization of retrieval of shared data (generally referred to as shared data retrieval optimization) in a communication system. More specifically, various example embodiments exemplarily relate to methods, apparatuses, and computer program products for optimized retrieval of shared data in a communication system.Summary
[0003] Various aspects of example embodiments are set out in the appended claims.
[0004] According to an exemplary aspect, there is provided a method comprising transmitting a request for shared-data sets which match shared-data set identifier independent matching criteria, said request including said shared-data set identifier independent matching criteria, and receiving a response including at least one shared-data set which matches said shared-data set identifier independent matching criteria and at least one shared-data set identifier corresponding to said at least one shared-data set.
[0005] According to an exemplary aspect, there is provided a method comprising receiving a request for shared-data sets which match shared-data set identifier independent matching criteria, said request including said shared-data set identifier independent matching criteria, obtaining, from a data store storing shared-data sets, at least one shared-data set which matches said shared-data set identifier independent matching criteria, and transmitting a response including said at least one shared-data set which matches said shared-data set identifier independent matching criteria and at least one shared-data set identifier corresponding to said at least one shared-data set.
[0006] According to an exemplary aspect, there is provided a method comprising transmitting a subscription request for shared-data sets which match shared-data setidentifier independent matching criteria, said subscription request including said shared- data set identifier independent matching criteria, and receiving a subscription acknowledgment.
[0007] According to an exemplary aspect, there is provided a method comprising receiving a subscription request for shared-data sets which match shared-data set identifier independent matching criteria, said subscription request including said shared- data set identifier independent matching criteria, obtaining, from a data store storing shared-data sets, at least one shared-data set which matches said shared-data set identifier independent matching criteria, establishing a subscription for said at least one shared-data set which matches said shared-data set identifier independent matching criteria, and transmitting a subscription acknowledgment.
[0008] According to an exemplary aspect, there is provided a method comprising transmitting a request for first data, said request including 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, said compiled data including general data in explicit form, at least one not-available shared-data set in explicit form, and at least one not-available shared-data set identifier corresponding to said at least one not-available shared-data set.
[0009] According to an exemplary aspect, there is provided a method comprising receiving a request for first data, said request including at least one available shared-data set identifier corresponding to at least one available shared-data set, obtaining, as obtained data, said first data from a data store, compiling, as compiled data, data based on said obtained data, said compiled data including general data in explicit form, at least one not- available shared-data set in explicit form, and at least one not-available shared-data set identifier corresponding to said at least one not-available shared-data set, and transmitting a data response including said compiled data.
[0010] According to an exemplary aspect, there is provided a method comprising transmitting a subscription request for first data, said subscription request including at least one available shared-data set identifier corresponding to at least one available shared-data set, and receiving a message based on said subscription request, said messageincluding information on at least one not-available shared-data set relating to said first data.
[0011] According to an exemplary aspect, there is provided a method comprising receiving a subscription request for first data, said subscription request including at least one available shared-data set identifier corresponding to at least one available shared-data set, obtaining, as obtained data, said first data from a data store, and transmitting a message based on said subscription request, said message including information on at least one not-available shared-data set relating to said first data.
[0012] According to an exemplary aspect, there is provided a method comprising transmitting a request for first data, and receiving a data response including compiled data, said compiled data including general data in explicit form, at least one not-available shared-data set relating to said first data in explicit form, and at least one not-available shared-data set identifier corresponding to said at least one not-available shared-data set.
[0013] According to an exemplary aspect, there is provided a method comprising receiving a request for first data, obtaining, as obtained data, said first data from a data store, compiling, as compiled data, data based on said obtained data, said compiled data including general data in explicit form, at least one not-available shared-data set relating to said first data in explicit form, and at least one not-available shared-data set identifier corresponding to said at least one not-available shared-data set, and transmitting a data response including said compiled data.
[0014] According to an exemplary aspect, there is provided a method comprising transmitting a subscription request for first data, and receiving a message based on said subscription request, said message including information on at least one not-available shared-data set relating to said first data.
[0015] According to an exemplary aspect, there is provided a method comprising receiving a subscription request for first data, obtaining, as obtained data, said first data from a data store, and transmitting a message based on said subscription request, said message including information on at least one not-available shared-data set relating to said first data.
[0016] According to an exemplary aspect, there is provided an apparatus comprising transmitting circuitry configured to transmit a request for shared-data sets which matchshared-data set identifier independent matching criteria, said request including said shared-data set identifier independent matching criteria, and receiving circuitry configured to receive a response including at least one shared-data set which matches said shared-data set identifier independent matching criteria and at least one shared-data set identifier corresponding to said at least one shared-data set.
[0017] According to an exemplary aspect, there is provided an apparatus comprising receiving circuitry configured to receive a request for shared-data sets which match shared-data set identifier independent matching criteria, said request including said shared-data set identifier independent matching criteria, obtaining circuitry configured to obtain, from a data store storing shared-data sets, at least one shared-data set which matches said shared-data set identifier independent matching criteria, and transmitting circuitry configured to transmit a response including said at least one shared-data set which matches said shared-data set identifier independent matching criteria and at least one shared-data set identifier corresponding to said at least one shared-data set.
[0018] According to an exemplary aspect, there is provided an apparatus comprising transmitting circuitry configured to transmit a subscription request for shared-data sets which match shared-data set identifier independent matching criteria, said subscription request including said shared-data set identifier independent matching criteria, and receiving circuitry configured to receive a subscription acknowledgment.
[0019] According to an exemplary aspect, there is provided an apparatus comprising receiving circuitry configured to receive a subscription request for shared-data sets which match shared-data set identifier independent matching criteria, said subscription request including said shared-data set identifier independent matching criteria, obtaining circuitry configured to obtain, from a data store storing shared-data sets, at least one shared-data set which matches said shared-data set identifier independent matching criteria, establishing circuitry configured to establish a subscription for said at least one shared- data set which matches said shared-data set identifier independent matching criteria, and transmitting circuitry configured to transmit a subscription acknowledgment.
[0020] According to an exemplary aspect, there is provided an apparatus comprising transmitting circuitry configured to transmit a request for first data, said request including at least one available shared-data set identifier corresponding to at least one availableshared-data set, and receiving circuitry configured to receive a data response including compiled data, said compiled data including general data in explicit form, at least one not-available shared-data set in explicit form, and at least one not-available shared-data set identifier corresponding to said at least one not-available shared-data set.
[0021] According to an exemplary aspect, there is provided an apparatus comprising receiving circuitry configured to receive a request for first data, said request including at least one available shared-data set identifier corresponding to at least one available shared-data set, obtaining circuitry configured to obtain, as obtained data, said first data from a data store, compiling circuitry configured to compile, as compiled data, data based on said obtained data, said compiled data including general data in explicit form, at least one not-available shared-data set in explicit form, and at least one not-available shared- data set identifier corresponding to said at least one not-available shared-data set, and transmitting circuitry configured to transmit a data response including said compiled data.
[0022] According to an exemplary aspect, there is provided an apparatus comprising transmitting circuitry configured to transmit a subscription request for first data, said subscription request including at least one available shared-data set identifier corresponding to at least one available shared-data set, and receiving circuitry configured to receive a message based on said subscription request, said message including information on at least one not-available shared-data set relating to said first data.
[0023] According to an exemplary aspect, there is provided an apparatus comprising receiving circuitry configured to receive a subscription request for first data, said subscription request including at least one available shared-data set identifier corresponding to at least one available shared-data set, obtaining circuitry configured to obtain, as obtained data, said first data from a data store, and transmitting circuitry configured to transmit a message based on said subscription request, said message including information on at least one not-available shared-data set relating to said first data.
[0024] According to an exemplary aspect, there is provided an apparatus comprising transmitting circuitry configured to transmit a request for first data, and receiving circuitry configured to receive a data response including compiled data, said compiled data including general data in explicit form, at least one not-available shared-data set relatingto said first data in explicit form, and at least one not-available shared-data set identifier corresponding to said at least one not-available shared-data set.
[0025] According to an exemplary aspect, there is provided an apparatus comprising receiving circuitry configured to receive a request for first data, obtaining circuitry configured to obtain, as obtained data, said first data from a data store, compiling circuitry configured to compile, as compiled data, data based on said obtained data, said compiled data including general data in explicit form, at least one not-available shared-data set relating to said first data in explicit form, and at least one not-available shared-data set identifier corresponding to said at least one not-available shared-data set, and transmitting circuitry configured to transmit a data response including said compiled data.
[0026] According to an exemplary aspect, there is provided an apparatus comprising transmitting circuitry configured to transmit a subscription request for first data, and receiving circuitry configured to receive a message based on said subscription request, said message including information on at least one not-available shared-data set relating to said first data.
[0027] According to an exemplary aspect, there is provided an apparatus comprising receiving circuitry configured to receive a subscription request for first data, obtaining circuitry configured to obtain, as obtained data, said first data from a data store, and transmitting circuitry configured to transmit a message based on said subscription request, said message including information on at least one not-available shared-data set relating to said first data.
[0028] According to an exemplary aspect, there is provided an apparatus comprising at least one processor, at least one memory including computer program code, and at least one interface configured for communication with at least another apparatus, the at least one processor, with the at least one memory and the computer program code, being configured to cause the apparatus to perform transmitting a request for shared-data sets which match shared-data set identifier independent matching criteria, said request including said shared-data set identifier independent matching criteria, and receiving a response including at least one shared-data set which matches said shared-data set identifier independent matching criteria and at least one shared-data set identifier corresponding to said at least one shared-data set.
[0029] According to an exemplary aspect, there is provided an apparatus comprising at least one processor, at least one memory including computer program code, and at least one interface configured for communication with at least another apparatus, the at least one processor, with the at least one memory and the computer program code, being configured to cause the apparatus to perform receiving a request for shared-data sets which match shared-data set identifier independent matching criteria, said request including said shared-data set identifier independent matching criteria, obtaining, from a data store storing shared-data sets, at least one shared-data set which matches said shared- data set identifier independent matching criteria, and transmitting a response including said at least one shared-data set which matches said shared-data set identifier independent matching criteria and at least one shared-data set identifier corresponding to said at least one shared-data set.
[0030] According to an exemplary aspect, there is provided an apparatus comprising at least one processor, at least one memory including computer program code, and at least one interface configured for communication with at least another apparatus, the at least one processor, with the at least one memory and the computer program code, being configured to cause the apparatus to perform transmitting a subscription request for shared-data sets which match shared-data set identifier independent matching criteria, said subscription request including said shared-data set identifier independent matching criteria, and receiving a subscription acknowledgment.
[0031] According to an exemplary aspect, there is provided an apparatus comprising at least one processor, at least one memory including computer program code, and at least one interface configured for communication with at least another apparatus, the at least one processor, with the at least one memory and the computer program code, being configured to cause the apparatus to perform receiving a subscription request for shared- data sets which match shared-data set identifier independent matching criteria, said subscription request including said shared-data set identifier independent matching criteria, obtaining, from a data store storing shared-data sets, at least one shared-data set which matches said shared-data set identifier independent matching criteria, establishing a subscription for said at least one shared-data set which matches said shared-data set identifier independent matching criteria, and transmitting a subscription acknowledgment.
[0032] According to an exemplary aspect, there is provided an apparatus comprising at least one processor, at least one memory including computer program code, and at least one interface configured for communication with at least another apparatus, the at least one processor, with the at least one memory and the computer program code, being configured to cause the apparatus to perform transmitting a request for first data, said request including 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, said compiled data including general data in explicit form, at least one not-available shared- data set in explicit form, and at least one not-available shared-data set identifier corresponding to said at least one not-available shared-data set.
[0033] According to an exemplary aspect, there is provided an apparatus comprising at least one processor, at least one memory including computer program code, and at least one interface configured for communication with at least another apparatus, the at least one processor, with the at least one memory and the computer program code, being configured to cause the apparatus to perform receiving a request for first data, said request including at least one available shared-data set identifier corresponding to at least one available shared-data set, obtaining, as obtained data, said first data from a data store, compiling, as compiled data, data based on said obtained data, said compiled data including general data in explicit form, at least one not-available shared-data set in explicit form, and at least one not-available shared-data set identifier corresponding to said at least one not-available shared-data set, and transmitting a data response including said compiled data.
[0034] According to an exemplary aspect, there is provided an apparatus comprising at least one processor, at least one memory including computer program code, and at least one interface configured for communication with at least another apparatus, the at least one processor, with the at least one memory and the computer program code, being configured to cause the apparatus to perform transmitting a subscription request for first data, said subscription request including at least one available shared-data set identifier corresponding to at least one available shared-data set, and receiving a message based on said subscription request, said message including information on at least one not-available shared-data set relating to said first data.
[0035] According to an exemplary aspect, there is provided an apparatus comprising at least one processor, at least one memory including computer program code, and at least one interface configured for communication with at least another apparatus, the at least one processor, with 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, said subscription request including at least one available shared-data set identifier corresponding to at least one available shared-data set, obtaining, as obtained data, said first data from a data store, and transmitting a message based on said subscription request, said message including information on at least one not-available shared-data set relating to said first data.
[0036] According to an exemplary aspect, there is provided an apparatus comprising at least one processor, at least one memory including computer program code, and at least one interface configured for communication with at least another apparatus, the at least one processor, with the at least one memory and the computer program code, being configured to cause the apparatus to perform transmitting a request for first data, and receiving a data response including compiled data, said compiled data including general data in explicit form, at least one not-available shared-data set relating to said first data in explicit form, and at least one not-available shared-data set identifier corresponding to said at least one not-available shared-data set.
[0037] According to an exemplary aspect, there is provided an apparatus comprising at least one processor, at least one memory including computer program code, and at least one interface configured for communication with at least another apparatus, the at least one processor, with the at least one memory and the computer program code, being configured to cause the apparatus to perform receiving a request for first data, obtaining, as obtained data, said first data from a data store, compiling, as compiled data, data based on said obtained data, said compiled data including general data in explicit form, at least one not-available shared-data set relating to said first data in explicit form, and at least one not-available shared-data set identifier corresponding to said at least one not- available shared-data set, and transmitting a data response including said compiled data.
[0038] According to an exemplary aspect, there is provided an apparatus comprising at least one processor, at least one memory including computer program code, and at leastone interface configured for communication with at least another apparatus, the at least one processor, with the at least one memory and the computer program code, being configured to cause the apparatus to perform transmitting a subscription request for first data, and receiving a message based on said subscription request, said message including information on at least one not-available shared-data set relating to said first data.
[0039] According to an exemplary aspect, there is provided an apparatus comprising at least one processor, at least one memory including computer program code, and at least one interface configured for communication with at least another apparatus, the at least one processor, with 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, obtaining, as obtained data, said first data from a data store, and transmitting a message based on said subscription request, said message including information on at least one not-available shared-data set relating to said first data.
[0040] According to an exemplary aspect, there is provided a computer program product comprising computer-executable computer program code which, when the program is run on a computer (e.g., a computer of an apparatus according to any one of the aforementioned apparatus-related exemplary aspects of the present disclosure), is configured to cause the computer to carry out the method according to any one of the aforementioned method-related exemplary aspects of the present disclosure.
[0041] Such computer program product may comprise (or be embodied) a (tangible) computer-readable (storage) medium or the like on which the computer-executable computer program code is stored, and / or the program may be directly loadable into an internal memory of the computer or a processor thereof.
[0042] Any one of the above aspects enables an efficient reduction of communication and signaling load to thereby solve at least part of the problems and drawbacks identified in relation to the prior art.
[0043] By way of example embodiments, there is provided shared data retrieval optimization. More specifically, by way of example embodiments, there are provided measures and mechanisms for realizing shared data retrieval optimization.
[0044] Thus, improvement is achieved by methods, apparatuses and computer program products enabling / realizing shared data retrieval optimization.Brief description of the drawings
[0045] In the following, the present disclosure will be described in greater detail by way of non-limiting examples with reference to the accompanying drawings, in which:
[0046] Figure 1 is a block diagram illustrating an apparatus according to example embodiments;
[0047] Figure 2 is a block diagram illustrating an apparatus according to example embodiments;
[0048] Figure 3 is a block diagram illustrating an apparatus according to example embodiments;
[0049] Figure 4 is a block diagram illustrating an apparatus according to example embodiments;
[0050] Figure 5 is a block diagram illustrating an apparatus according to example embodiments,
[0051] Figure 6 is a block diagram illustrating an apparatus according to example embodiments,
[0052] Figure 7 is a block diagram illustrating an apparatus according to example embodiments,
[0053] Figure 8 is a block diagram illustrating an apparatus according to example embodiments;
[0054] Figure 9 is a block diagram illustrating an apparatus according to example embodiments;
[0055] Figure 10 is a block diagram illustrating an apparatus according to example embodiments;
[0056] Figure 11 is a block diagram illustrating an apparatus according to example embodiments;
[0057] Figure 12 is a block diagram illustrating an apparatus according to example embodiments;
[0058] Figure 13 is a block diagram illustrating an apparatus according to example embodiments;
[0059] Figure 14 is a block diagram illustrating an apparatus according to example embodiments;
[0060] Figure 15 is a block diagram illustrating an apparatus according to example embodiments;
[0061] Figure 16 is a block diagram illustrating an apparatus according to example embodiments;
[0062] Figure 17 is a block diagram illustrating an apparatus according to example embodiments;
[0063] Figure 18 is a block diagram illustrating an apparatus according to example embodiments;
[0064] Figure 19 is a block diagram illustrating an apparatus according to example embodiments;
[0065] Figure 20 is a block diagram illustrating an apparatus according to example embodiments;
[0066] Figure 21 is a block diagram illustrating an apparatus according to example embodiments,
[0067] Figure 22 is a block diagram illustrating an apparatus according to example embodiments;
[0068] Figure 23 is a schematic diagram of a procedure according to example embodiments;
[0069] Figure 24 is a schematic diagram of a procedure according to example embodiments;
[0070] Figure 25 is a schematic diagram of a procedure according to example embodiments;
[0071] Figure 26 is a schematic diagram of a procedure according to example embodiments;
[0072] Figure 27 is a schematic diagram of a procedure according to example embodiments;
[0073] Figure 28 is a schematic diagram of a procedure according to example embodiments;
[0074] Figure 29 is a schematic diagram of a procedure according to example embodiments;
[0075] Figure 30 is a schematic diagram of a procedure according to example embodiments;
[0076] Figure 31 is a schematic diagram of a procedure according to example embodiments;
[0077] Figure 32 is a schematic diagram of a procedure according to example embodiments;
[0078] Figure 33 is a schematic diagram of a procedure according to example embodiments;
[0079] Figure 34 is a schematic diagram of a procedure according to example embodiments;
[0080] Figure 35 shows a schematic diagram of signaling sequences according to example embodiments;
[0081] Figure 36 shows a schematic diagram of signaling sequences according to example embodiments;
[0082] Figure 37 shows a schematic diagram of signaling sequences according to example embodiments;
[0083] Figure 38 shows a schematic diagram of signaling sequences according to example embodiments;
[0084] Figure 39 shows a schematic diagram of signaling sequences according to example embodiments;
[0085] Figure 40 shows a schematic diagram of signaling sequences according to example embodiments;
[0086] Figure 41 shows a schematic diagram of signaling sequences according to example embodiments;
[0087] Figure 42 shows a schematic diagram of signaling sequences according to example embodiments;
[0088] Figure 43 shows a schematic diagram of signaling sequences according to example embodiments;
[0089] Figure 44 shows a schematic diagram of signaling sequences according to example embodiments;
[0090] Figure 45 shows a schematic diagram of signaling sequences according to example embodiments;
[0091] Figure 46 shows a schematic diagram of signaling sequences according to example embodiments;
[0092] Figure 47 shows a schematic diagram of signaling sequences according to example embodiments; and
[0093] Figure 48 is a block diagram alternatively illustrating apparatuses according to example embodiments.Detailed description
[0094] The present disclosure is described herein with reference to particular non- limiting examples and to what are presently considered to be conceivable embodiments. A person skilled in the art will appreciate that the disclosure is by no means limited to these examples, and may be more broadly applied.
[0095] It is to be noted that the following description of the present disclosure and its embodiments mainly refers to specifications being used as non-limiting examples for certain exemplary network configurations and deployments. Namely, the present disclosure and its embodiments are mainly described in relation to 3GPP specifications being used as non-limiting examples for certain exemplary network configurations and deployments. As such, the description of example embodiments given herein specifically refers to terminology which is directly related thereto. Such terminology is only used in the context of the presented non-limiting examples, and does naturally not limit the disclosure in any way. Rather, any other communication or communication related system deployment, etc. may also be utilized as long as compliant with the features described herein.
[0096] Hereinafter, various embodiments and implementations of the present disclosure and its aspects or embodiments are described using several variants and / or alternatives. It is generally noted that, according to certain needs and constraints, all of the described variants and / or alternatives may be provided alone or in any conceivable combination (also including combinations of individual features of the various variants and / or alternatives).
[0097] As used herein, "at least one of the following:" and "at least one of" and similar wording, where the list of two or more elements are joined by "and" or "or", mean at least any one of the elements, or at least any two or more of the elements, or at least all the elements.
[0098] According to example embodiments, in general terms, there are provided measures and mechanisms for (enabling / realizing) shared data retrieval optimization in a communication system.
[0099] The present specification generally relates to a method or process of retrieving shared data from a network entity of a communication system, e.g., unified data management (UDM) / unified data repository (UDR) of a fifth-generation communication system (5GS). In addition to normal (unique) data, shared data can be stored in the UDM / UDR. For example, some data may be part of the user equipment (UE) context for an exemplary user equipment (UE1), and also part of the UE context of another exemplary user equipment (UE2). This data may then be stored as shared data. In the network entity of the communication data (e.g., the UDM / UDR), shared data is assigned shared data identifier (ID). In the above example, the UE contexts for UE1 and UE2 would then contain some (unique) data for UE1 or UE2, respectively, plus the shared data ID (only the ID of the shared data) that identifies the shared data (that is part of the UE contexts of both UE1 and UE2, but the shared data is stored is another data repository located somewhere else). Thus, currently, when a network function (NF) wants to retrieve the UE context for e.g., UE1 stored at the network entity of the communication system (e.g., UDM / UDR of the communication system), the NF will request the UE context for UE1, and it will receive the unique data for UE1 plus the shared data ID. Then, in a second step, the NF needs to retrieve the shared data that is part of the UE context for UE1 using the shared data ID from another data repository.
[0100] Shared subscription data may be retrieved from UDM / UDR of a communication system by any NF of the communication system using Nudm and Nudr interfaces of the communication system (e.g., 5GS).
[0101] Retrieval of shared subscription data (when needed, i.e., when not already stored in a data repository) is based on identifiers of shared data (generally referred to herein as shared data IDs). In other words, so far, shared data can be retrieved only based on shared data IDs.
[0102] A NF may retrieve individual UE specific data from a UDM / UDR using the Nudm and Nudr. Having received the individual UE specific data, the NF may detect that the retrieved individual UE specific data contains a shared data ID indicating that the retrieved individual UE specific data is incomplete and must be extended / merged withsome shared data. If the shared data to which this ID points to has not been cached already, the NF retrieves the shared data identified by the shared data ID as mentioned above.
[0103] NF that has retrieved shared subscription data (e.g., shared access and mobility (AM) -data identified by an exemplary shared data ID-17 for use in a UEl-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] A NF can use a "subscribe to data change notification" mechanism of the Nudm and Nudr interfaces be notified by the UDM / UDR when shared data (e.g., identified by shared data ID- 17) is modified.
[0105] The retrieved, stored and subscribed shared data identified by a shared data identifier only apply to the UE specific contexts where the shared data are referenced via the shared data ID. For instance, shared data ID- 17 (e.g., the shared data ID having the value 17) cannot be used by a NF in a UE3-specific context, if UE3 shares AM-data identified by shared data ID-25 )e.g., the shared data ID having the value 25) with another UE e.g., UE4 (but does not share AM-data with UE1 and UE2).
[0106] Shared data may have one of a number of predefined data types (e.g., shared data types).
[0107] That is, with an implementation as outlined above, shared data are retrieved one by one based on shared data ID and a NF must use the "subscribe to data change notification" mechanism whenever shared data is retrieved based on shared data ID to subscribe to notifications of changes to the shared data identified by shared data ID.
[0108] Hence, the problem arises that such approach leads to extra / increased signaling in a communication system (e.g., a 5GS).
[0109] Hence, there is a need to provide for apparatuses, methods, and computer programs for optimizing retrieval of shared data and measures and mechanisms for shared data retrieval optimization.
[0110] In brief, to address the identified issue that, so far, shared data can be retrieved only based on shared data IDs, according to example embodiments, a retrieval or subscription to notifications about changes of shared data is allowed to be based on a shared data type (in addition to the retrieval or subscription based on shared data ID).
[0111] According thereto, a NF (e.g., AMF or UDM) of a communication system (e.g., a 5GS) may be a NF service consumer and may provide one or several shared data type(s)in a request to retrieve data and / or to subscribe to notifications about data changes towards a UDM or UDR. The terms “NF service consumer” and “NF consumer” are used interchangeably herein. A “NF service consumer” is any NF of a communication system (e.g., a 5GS) which consumes services exposed by another NF of the communication system (e.g., 5GS) as described in the 3GPP standard for NR.
[0112] The UDM or UDR then provides the shared data for all (or some) shared data IDs matching the indicated types in a response to the request for the retrieval of those data or stores a subscription for notifications of changes for all (or some) shared data IDs matching the indicated types and subsequently provides notifications when those shared data change.
[0113] Instead of indicating a type of shared data that a NF consumer wants to retrieve (or subscribe to), according to example embodiments, the NF consumer can indicate a set of conditions that this shared data shall fulfil in order to be retrieved (or subscribed to), e.g., existence of certain attributes or attribute-value pairs within the shared data type.
[0114] Further, to address the identified issue that, so far, data retrieval mechanisms of Nudm and Nudr interfaces may be implemented only with two consecutive steps of retrievals, according to example embodiments, a NF consumer, (e.g., AMF or UDM) may include in a request to retrieve data and / or to subscribe to notifications about data changes towards a UDM or UDR a list of shared data IDs identifying shared data that the consumer has already stored locally.
[0115] If the UDM or UDR determines that the NF consumer does not have some of the shared data referenced within 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 a response to the request for the retrieval of those data or stores a subscription for notifications about changes of those shared data and subsequently provides notifications including both shared data ID and actual changed shared data when any of those shared data change.
[0116] According to example embodiments, the subscription can be combined with a request of immediate reporting that enables a combination of retrieval and subscription as described above.
[0117] Still further, to further address the identified issue that, so far, data retrieval mechanisms of Nudm and Nudr interfaces may be implemented only with twoconsecutive steps of retrievals, according to example embodiments, a NF consumer (e.g., AMF or UDM of a 5GS) sends a request to retrieve data and / or to subscribe to notifications about data changes towards a UDM or UDR. Based on (already established) subscriptions to shared data IDs of that NF consumer, the UDM or UDR determines whether the NF consumer does not have some of the shared data referenced within the requested or subscribed data. In order to be able to determine based on existing subscriptions which shared data an NF consumer has, the UDM / UDR may need to know, e.g., based on configuration on both sides, that the NF consumer preferably uses subscriptions in order to retrieve such data.
[0118] If the NF consumer does not have some of the shared data referenced within the requested or subscribed data (if the UDM or UDR determines that the NF consumer does not have some of the shared data referenced within the requested or subscribed data), the UDM or UDR additionally includes both the shared data ID and the actual shared data for that shared data ID in a response to the request for the retrieval of those data or stores a subscription for notifications about changes of those shared data and subsequently provides notifications including both shared data ID and actual changed shared data when any of those shared data change. According to example embodiments, the subscription can be combined with a request of immediate notifications that enables a combination of retrieval and subscription as described above.
[0119] Example embodiments are specified below in more detail.
[0120] Figure 1 is a block diagram illustrating an apparatus according to example embodiments. The apparatus may be a network entity 10, such as an access and mobility function entity or a unified data management entity, comprising a transmitting circuitry 11 and a receiving circuitry 12. The transmitting circuitry 11 transmits a request for shared-data sets which match shared-data set identifier independent matching criteria, said request including said shared-data set identifier independent matching criteria. The receiving circuitry 12 receives a response including at least one shared-data set which matches said shared-data set identifier independent matching criteria and at least one shared-data set identifier corresponding to said at least one shared-data set. Figure 23 is a schematic diagram of a procedure according to example embodiments. The apparatus according to Figure 1 may perform the method of Figure 23 but is not limited to thismethod. The method of Figure 23 may be performed by the apparatus of Figure 1 but is not limited to being performed by this apparatus.
[0121] As shown in Figure 23, a procedure according to example embodiments comprises an operation of transmitting (S231) a request for shared-data sets which match shared-data set identifier independent matching criteria, said request including said shared-data set identifier independent matching criteria, and an operation of receiving (S232) a response including at least one shared-data set which matches said shared-data set identifier independent matching criteria and at least one shared-data set identifier corresponding to said at least one shared-data set.
[0122] Figure 2 is a block diagram illustrating an apparatus according to example embodiments. In particular, Figure 2 illustrates a variation of the apparatus shown in Figure 1. The apparatus according to Figure 2 may thus further comprise a storing circuitry 21.
[0123] In an embodiment at least some of the functionalities of the apparatus shown in Figure 1 (or 2) may be shared between two physically separate devices forming one operational entity. Therefore, the apparatus may be seen to depict the operational entity comprising one or more physically separate devices for executing at least some of the described processes.
[0124] According to further example embodiments, said shared-data set identifier independent matching criteria include a shared-data type, or shared-data content elements characteristic for said shared-data type.
[0125] According to further example embodiments, said shared-data set identifier independent matching criteria include filter information for filtering information elements of shared-data set candidates.
[0126] According to a variation of the procedure shown in Figure 23, exemplary additional operations are given, which are inherently independent from each other as such. According to such variation, an exemplary method according to example embodiments may comprise an operation of storing said at least one shared-data set together with said corresponding shared-data set identifier.
[0127] According to a variation of the procedure shown in Figure 23, exemplary additional operations are given, which are inherently independent from each other as such. According to such variation, said response includes at least two shared-data sets which match said shared-data set identifier independent matching criteria and at least two shared-data set identifiers corresponding to said at least two shared-data sets, and an exemplary method according to example embodiments may comprise an operation of transmitting a subscription request for subscribing for change notifications with respect to said at least two shared-data sets, wherein said subscription request includes said at least two shared-data set identifiers.
[0128] Figure 3 is a block diagram illustrating an apparatus according to example embodiments. The apparatus may be a network entity 30, such as a unified data management entity or a unified data repository entity, comprising a receiving circuitry 31, an obtaining circuitry 32, and a transmitting circuitry 33. The receiving circuitry 31 receives a request for shared-data sets which match shared-data set identifier independent matching criteria, said request including said shared-data set identifier independent matching criteria. The obtaining circuitry 32 obtains, from a data store storing shared- data sets, at least one shared-data set which matches said shared-data set identifier independent matching criteria. The transmitting circuitry 33 transmits a response including said at least one shared-data set which matches said shared-data set identifier independent matching criteria and at least one shared-data set identifier corresponding to said at least one shared-data set. Figure 24 is a schematic diagram of a procedure according to example embodiments. The apparatus according to Figure 3 may perform the method of Figure 24 but is not limited to this method. The method of Figure 24 may be performed by the apparatus of Figure 3 but is not limited to being performed by this apparatus.
[0129] As shown in Figure 24, a procedure according to example embodiments comprises an operation of receiving (S241) a request for shared-data sets which match shared-data set identifier independent matching criteria, said request including said shared-data set identifier independent matching criteria, an operation of obtaining (S242), from a data store storing shared-data sets, at least one shared-data set which matches said shared-data set identifier independent matching criteria, and an operation of transmitting (S243) a response including said at least one shared-data set which matches said shared-data set identifier independent matching criteria and at least one shared-data set identifier corresponding to said at least one shared-data set.
[0130] Figure 4 is a block diagram illustrating an apparatus according to example embodiments. In particular, Figure 4 illustrates a variation of the apparatus shown in Figure 3. The apparatus according to Figure 4 may thus further comprise a filtering circuitry 41 and / or a considering circuitry 42.
[0131] In an embodiment at least some of the functionalities of the apparatus shown in Figure 3 (or 4) may be shared between two physically separate devices forming one operational entity. Therefore, the apparatus may be seen to depict the operational entity comprising one or more physically separate devices for executing at least some of the described processes.
[0132] According to further example embodiments, said shared-data set identifier independent matching criteria include: a shared-data type; or shared-data content elements characteristic for said shared-data type.
[0133] According to a variation of the procedure shown in Figure 24, exemplary additional operations and exemplary details of the transmitting operation are given, which are inherently independent from each other as such. According to such variation, said shared-data set identifier independent matching criteria include filter information for filtering information elements of shared-data set candidates, and an exemplary method according to example embodiments may comprise an operation of filtering information elements of said obtained at least one shared-data set. Further, such exemplary transmitting operation according to example embodiments may comprise an operation of considering a result of said filtering.
[0134] According to a variation of the procedure shown in Figure 24, exemplary additional operations are given, which are inherently independent from each other as such. According to such variation, said response includes at least two shared-data sets which match said shared-data set identifier independent matching criteria and at least two shared-data set identifiers corresponding to said at least two shared-data sets, and an exemplary method according to example embodiments may comprise an operation of receiving a subscription request for subscribing for change notifications with respect tosaid at least two shared-data sets, wherein said subscription request includes said at least two shared-data set identifiers.
[0135] Figure 5 is a block diagram illustrating an apparatus according to example embodiments. The apparatus may be a network entity 50, such as an access and mobility function entity or a unified data management entity, comprising a transmitting circuitry 51 and a receiving circuitry 52. The transmitting circuitry 51 transmits a subscription request for shared-data sets which match shared-data set identifier independent matching criteria, said subscription request including said shared-data set identifier independent matching criteria. The receiving circuitry 52 receives a subscription acknowledgment. Figure 25 is a schematic diagram of a procedure according to example embodiments. The apparatus according to Figure 5 may perform the method of Figure 25 but is not limited to this method. The method of Figure 25 may be performed by the apparatus of Figure 5 but is not limited to being performed by this apparatus.
[0136] As shown in Figure 25, a procedure according to example embodiments comprises an operation of transmitting (S251) a subscription request for shared-data sets which match shared-data set identifier independent matching criteria, said subscription request including said shared-data set identifier independent matching criteria, and an operation of receiving (S252) a subscription acknowledgment.
[0137] Figure 6 is a block diagram illustrating an apparatus according to example embodiments. In particular, Figure 6 illustrates a variation of the apparatus shown in Figure 5. The apparatus according to Figure 6 may thus further comprise a storing circuitry 61.
[0138] In an embodiment at least some of the functionalities of the apparatus shown in Figure 5 (or 6) may be shared between two physically separate devices forming one operational entity. Therefore, the apparatus may be seen to depict the operational entity comprising one or more physically separate devices for executing at least some of the described processes.
[0139] According to further example embodiments, said shared-data set identifier independent matching criteria include: a shared-data type; or shared-data content elements characteristic for said shared-data type.
[0140] According to further example embodiments, said shared-data set identifier independent matching criteria include filter information for filtering information elements of shared-data set candidates.
[0141] According to further example embodiments, said subscription request is indicative of an immediate reporting demand, and said subscription acknowledgement includes at least one shared-data set which matches said shared-data set identifier independent matching criteria and at least one shared-data set identifier corresponding to said at least one shared-data set.
[0142] According to a variation of the procedure shown in Figure 25, exemplary additional operations are given, which are inherently independent from each other as such. According to such variation, an exemplary method according to example embodiments may comprise an operation of storing said at least one shared-data set together with said corresponding shared-data set identifier.
[0143] Figure 7 is a block diagram illustrating an apparatus according to example embodiments. The apparatus may be a network entity 70, such as a unified data management entity or a unified data repository entity, comprising a receiving circuitry 71, an obtaining circuitry 72, an establishing circuitry 73, and a transmitting circuitry 74. The receiving circuitry 71 receives a subscription request for shared-data sets which match shared-data set identifier independent matching criteria, said subscription request including said shared-data set identifier independent matching criteria. The obtaining circuitry 72 obtains, from a data store storing shared-data sets, at least one shared-data set which matches said shared-data set identifier independent matching criteria. The establishing circuitry 73 establishes a subscription for said at least one shared-data set which matches said shared-data set identifier independent matching criteria. The transmitting circuitry 74 transmits a subscription acknowledgment. Figure 26 is a schematic diagram of a procedure according to example embodiments. The apparatus according to Figure 7 may perform the method of Figure 26 but is not limited to this method. The method of Figure 26 may be performed by the apparatus of Figure 7 but is not limited to being performed by this apparatus.
[0144] As shown in Figure 26, a procedure according to example embodiments comprises an operation of receiving (S261) a subscription request for shared-data sets which match shared-data set identifier independent matching criteria, said subscriptionrequest including said shared-data set identifier independent matching criteria, an operation of obtaining (S262), from a data store storing shared-data sets, at least one shared-data set which matches said shared-data set identifier independent matching criteria, an operation of establishing (S263) a subscription for said at least one shared- data set which matches said shared-data set identifier independent matching criteria, and an operation of transmitting (S264) a subscription acknowledgment.
[0145] Figure 8 is a block diagram illustrating an apparatus according to example embodiments. In particular, Figure 8 illustrates a variation of the apparatus shown in Figure 7. The apparatus according to Figure 8 may thus further comprise a filtering circuitry 81 and / or a considering circuitry 82.
[0146] In an embodiment at least some of the functionalities of the apparatus shown in Figure 7 (or 8) may be shared between two physically separate devices forming one operational entity. Therefore, the apparatus may be seen to depict the operational entity comprising one or more physically separate devices for executing at least some of the described processes.
[0147] According to further example embodiments, said shared-data set identifier independent matching criteria include: a shared-data type; or shared-data content elements characteristic for said shared-data type.
[0148] According to a variation of the procedure shown in Figure 26, exemplary additional operations and exemplary details of the establishing operation are given, which are inherently independent from each other as such. According to such variation, said shared-data set identifier independent matching criteria include filter information for filtering information elements of shared-data set candidates, and an exemplary method according to example embodiments may comprise an operation of filtering information elements of said obtained at least one shared-data set. Further, such exemplary establishing operation according to example embodiments may comprise an operation of considering a result of said filtering.
[0149] According to further example embodiments, said subscription request is indicative of an immediate reporting demand, and said subscription acknowledgement includes said at least one shared-data set which matches said shared-data set identifierindependent matching criteria and at least one shared-data set identifier corresponding to said at least one shared-data set.
[0150] Figure 9 is a block diagram illustrating an apparatus according to example embodiments. The apparatus may be a network entity 90, such as an access and mobility function entity or a unified data management entity, comprising a transmitting circuitry 91 and a receiving circuitry 92. The transmitting circuitry 91 transmits a request for first data, said request including at least one available shared-data set identifier corresponding to at least one available shared-data set. The receiving circuitry 92 receives a data response including compiled data, said compiled data including general data in explicit form, at least one not- available shared-data set in explicit form, and at least one not- available shared-data set identifier corresponding to said at least one not-available shared- data set. Figure 27 is a schematic diagram of a procedure according to example embodiments. The apparatus according to Figure 9 may perform the method of Figure 27 but is not limited to this method. The method of Figure 27 may be performed by the apparatus of Figure 9 but is not limited to being performed by this apparatus.
[0151] As shown in Figure 27, a procedure according to example embodiments comprises an operation of transmitting (S271) a request for first data, said request including at least one available shared-data set identifier corresponding to at least one available shared-data set, and an operation of receiving (S272) a data response including compiled data, said compiled data including general data in explicit form, at least one not-available shared-data set in explicit form, and at least one not-available shared-data set identifier corresponding to said at least one not-available shared-data set.
[0152] In an embodiment at least some of the functionalities of the apparatus shown in Figure 9 may be shared between two physically separate devices forming one operational entity. Therefore, the apparatus may be seen to depict the operational entity comprising one or more physically separate devices for executing at least some of the described processes.
[0153] According to further example embodiments, said compiled data includes at least one of said at least one available shared-data set identifier corresponding to at least one of said at least one available shared-data set as a shared-data set in referenced form.
[0154] Figure 10 is a block diagram illustrating an apparatus according to example embodiments. The apparatus may be a network entity 100, such as a unified datamanagement entity or a unified data repository entity, comprising a receiving circuitry 101, an obtaining circuitry 102, a compiling circuitry 103, and a transmitting circuitry 104. The receiving circuitry 101 receives a request for first data, said request including at least one available shared-data set identifier corresponding to at least one available shared-data set. The obtaining circuitry 102 obtains, as obtained data, said first data from a data store. The compiling circuitry 103 compiles, as compiled data, data based on said obtained data, said compiled data including general data in explicit form, at least one not- available shared-data set in explicit form, and at least one not- available shared-data set identifier corresponding to said at least one not-available shared-data set. The transmitting circuitry 104 transmits a data response including said compiled data. Figure 28 is a schematic diagram of a procedure according to example embodiments. The apparatus according to Figure 10 may perform the method of Figure 28 but is not limited to this method. The method of Figure 28 may be performed by the apparatus of Figure 10 but is not limited to being performed by this apparatus.
[0155] As shown in Figure 28, a procedure according to example embodiments comprises an operation of receiving (S281) a request for first data, said request including at least one available shared-data set identifier corresponding to at least one available shared-data set, an operation of obtaining (S282), as obtained data, said first data from a data store, an operation of compiling (S283), as compiled data, data based on said obtained data, said compiled data including general data in explicit form, at least one not- available shared-data set in explicit form, and at least one not-available shared-data set identifier corresponding to said at least one not-available shared-data set, and an operation of transmitting (S284) a data response including said compiled data.
[0156] Figure 11 is a block diagram illustrating an apparatus according to example embodiments. In particular, Figure 11 illustrates a variation of the apparatus shown in Figure 10. The apparatus according to Figure 11 may thus further comprise an analyzing circuitry 111 and / or a forwarding circuitry 112.
[0157] In an embodiment at least some of the functionalities of the apparatus shown in Figure 10 (or 11) may be shared between two physically separate devices forming one operational entity. Therefore, the apparatus may be seen to depict the operational entity comprising one or more physically separate devices for executing at least some of the described processes.
[0158] According to further example embodiments, said compiled data includes at least one of said at least one available shared-data set identifier corresponding to at least one of said at least one available shared-data set as a shared-data set in referenced form.
[0159] According to a variation of the procedure shown in Figure 28, exemplary additional operations are given, which are inherently independent from each other as such. According to such variation, an exemplary method according to example embodiments may comprise an operation of analyzing said obtained data for whether said obtained data includes at least one not-available shared-data set identifier, and an operation of obtaining, from said data store, said at least one not-available shared-data set corresponding to said at least one not-available shared-data set identifier.
[0160] According to a variation of the procedure shown in Figure 28, exemplary details of the obtaining operation are given, which are inherently independent from each other as such. Such exemplary obtaining operation according to example embodiments may comprise an operation of forwarding said at least one available shared-data set identifier to said data store, and an operation of receiving, from said data store, said obtained data including said at least one not-available shared-data set in explicit form and said at least one not-available shared-data set identifier corresponding to said at least one not- available shared-data set.
[0161] Figure 12 is a block diagram illustrating an apparatus according to example embodiments. The apparatus may be a network entity 120, such as an access and mobility function entity or a unified data management entity, comprising a transmitting circuitry 121 and a receiving circuitry 122. The transmitting circuitry 121 transmits a subscription request for first data, said subscription request including at least one available shared-data set identifier corresponding to at least one available shared-data set. The receiving circuitry 122 receives a message based on said subscription request, said message including information on at least one not-available shared-data set relating to said first data. Figure 29 is a schematic diagram of a procedure according to example embodiments. The apparatus according to Figure 12 may perform the method of Figure 29 but is not limited to this method. The method of Figure 29 may be performed by the apparatus of Figure 12 but is not limited to being performed by this apparatus.
[0162] As shown in Figure 29, a procedure according to example embodiments comprises an operation of transmitting (S291) a subscription request for first data, saidsubscription request including at least one available shared-data set identifier corresponding to at least one available shared-data set, and an operation of receiving (S292) a message based on said subscription request, said message including information on at least one not-available shared-data set relating to said first data.
[0163] Figure 13 is a block diagram illustrating an apparatus according to example embodiments. In particular, Figure 13 illustrates a variation of the apparatus shown in Figure 12. The apparatus according to Figure 13 may thus further comprise a storing circuitry 131.
[0164] In an embodiment at least some of the functionalities of the apparatus shown in Figure 12 (or 13) may be shared between two physically separate devices forming one operational entity. Therefore, the apparatus may be seen to depict the operational entity comprising one or more physically separate devices for executing at least some of the described processes.
[0165] According to further example embodiments, said subscription request is indicative of an immediate reporting demand, and said message is a subscription acknowledgement including said at least one not-available shared-data set and at least one not-available shared-data set identifier corresponding to said at least one not- available shared-data set.
[0166] According to further example embodiments, said message is a notification including information on changes of said at least one not-available shared-data set, and at least one not-available shared-data set identifier corresponding to said at least one not- available shared-data set.
[0167] According to a variation of the procedure shown in Figure 29, exemplary additional operations are given, which are inherently independent from each other as such. According to such variation, an exemplary method according to example embodiments may comprise an operation of storing said at least one not-available shared- data set together with said corresponding not-available shared-data set identifier.
[0168] Figure 14 is a block diagram illustrating an apparatus according to example embodiments. The apparatus may be a network entity 140, such as a unified data management entity or a unified data repository entity, comprising a receiving circuitry 141, an obtaining circuitry 142, and a transmitting circuitry 144. The receiving circuitry 141 receives a subscription request for first data, said subscription request including atleast one available shared-data set identifier corresponding to at least one available shared-data set. The obtaining circuitry 142 obtains, as obtained data, said first data from a data store. The transmitting circuitry 144 transmits a message based on said subscription request, said message including information on at least one not-available shared-data set relating to said first data. Figure 30 is a schematic diagram of a procedure according to example embodiments. The apparatus according to Figure 14 may perform the method of Figure 30 but is not limited to this method. The method of Figure 30 may be performed by the apparatus of Figure 14 but is not limited to being performed by this apparatus.
[0169] As shown in Figure 30, a procedure according to example embodiments comprises an operation of receiving (S301) a subscription request for first data, said subscription request including at least one available shared-data set identifier corresponding to at least one available shared-data set, an operation of obtaining (S302), as obtained data, said first data from a data store, and an operation of transmitting (S303) a message based on said subscription request, said message including information on at least one not-available shared-data set relating to said first data.
[0170] Figure 15 is a block diagram illustrating an apparatus according to example embodiments. In particular, Figure 15 illustrates a variation of the apparatus shown in Figure 14. The apparatus according to Figure 14 may thus further comprise an analyzing circuitry 151, a forwarding circuitry 152, and / or an establishing circuitry 153.
[0171] In an embodiment at least some of the functionalities of the apparatus shown in Figure 14 (or 15) may be shared between two physically separate devices forming one operational entity. Therefore, the apparatus may be seen to depict the operational entity comprising one or more physically separate devices for executing at least some of the described processes.
[0172] According to a variation of the procedure shown in Figure 30, exemplary additional operations are given, which are inherently independent from each other as such. According to such variation, an exemplary method according to example embodiments may comprise an operation of analyzing said obtained data for whether said obtained data includes at least one not-available shared-data set identifier.
[0173] According to further example embodiments, said subscription request is indicative of an immediate reporting demand, and said message is a subscription acknowledgement including said at least one not-available shared-data set and at leastone not-available shared-data set identifier corresponding to said at least one not- available shared-data set. In some embodiments, the shared data sets are only provided as part of the immediate reporting and no subscription for subsequent notifications about changes of shared data sets is established.
[0174] According to other example embodiments, a subscription for subsequent notifications about changes of shared data sets is established. When one or several of the shared data sets are changed, a notification is provided. In some example embodiments, if several subscriptions for the same shared data set have been established by the same consumer, and that shared data set changes, only one notification relating to one of the established subscriptions is provided.
[0175] According to a variation of the procedure shown in Figure 30, exemplary additional operations are given, which are inherently independent from each other as such. According to such variation, an exemplary method according to example embodiments may comprise an operation of establishing, based on said obtained data, a subscription for not-available shared-data sets relating to said first data, said not-available shared-data sets including said at least one not-available shared-data set, wherein said message is a notification including information on changes of said at least one not- available shared-data set, and at least one not-available shared-data set identifier corresponding to said at least one not-available shared-data set.
[0176] According to a variation of the procedure shown in Figure 30, exemplary additional operations are given, which are inherently independent from each other as such. According to such variation, an exemplary method according to example embodiments may comprise an obtaining, from said data store, said at least one not- available shared-data set.
[0177] According to a variation of the procedure shown in Figure 30, exemplary details of the obtaining operation are given, which are inherently independent from each other as such. Such exemplary obtaining operation according to example embodiments may comprise an operation of forwarding said at least one available shared-data set identifier to said data store, and an operation of receiving, from said data store, said obtained data including said at least one not-available shared-data set in explicit form.
[0178] Figure 16 is a block diagram illustrating an apparatus according to example embodiments. The apparatus may be a network entity 160, such as an access and mobilityfunction entity or a unified data management entity, comprising a transmitting circuitry 161 and a receiving circuitry 162. The transmitting circuitry 161 transmits a request for first data. The receiving circuitry 162 receives a data response including compiled data, said compiled data including general data in explicit form, at least one not-available shared-data set relating to said first data in explicit form, and at least one not-available shared-data set identifier corresponding to said at least one not-available shared-data set. Figure 31 is a schematic diagram of a procedure according to example embodiments. The apparatus according to Figure 16 may perform the method of Figure 31 but is not limited to this method. The method of Figure 31 may be performed by the apparatus of Figure 16 but is not limited to being performed by this apparatus.
[0179] As shown in Figure 31, a procedure according to example embodiments comprises an operation of transmitting (S311) a request for first data, and an operation of receiving (S312) a data response including compiled data, said compiled data including general data in explicit form, at least one not-available shared-data set relating to said first data in explicit form, and at least one not-available shared-data set identifier corresponding to said at least one not-available shared-data set.
[0180] In an embodiment at least some of the functionalities of the apparatus shown in Figure 16 may be shared between two physically separate devices forming one operational entity. Therefore, the apparatus may be seen to depict the operational entity comprising one or more physically separate devices for executing at least some of the described processes.
[0181] According to further example embodiments, said request for first data is indicative of whether said request for first data also relates to not-available shared-data sets, and, if said request for first data is not indicative of that said request for first data also relates to not-available shared-data sets, said compiled data does not include said at least one not-available shared-data set in explicit form.
[0182] According to further example embodiments, said compiled data includes at least one available shared-data set identifier corresponding to at least one available shared-data set as a shared-data set in referenced form.
[0183] Figure 17 is a block diagram illustrating an apparatus according to example embodiments. The apparatus may be a network entity 170, such as a unified data management entity or a unified data repository entity, comprising a receiving circuitry171, an obtaining circuitry 172, a compiling circuitry 173, and a transmitting circuitry 174. The receiving circuitry 171 receives a request for first data. The obtaining circuitry172 obtains, as obtained data, said first data from a data store. The compiling circuitry173 compiles, as compiled data, data based on said obtained data, said compiled data including general data in explicit form, at least one not-available shared-data set relating to said first data in explicit form, and at least one not-available shared-data set identifier corresponding to said at least one not-available shared-data set. The transmitting circuitry174 transmits a data response including said compiled data. Figure 32 is a schematic diagram of a procedure according to example embodiments. The apparatus according to Figure 17 may perform the method of Figure 32 but is not limited to this method. The method of Figure 32 may be performed by the apparatus of Figure 17 but is not limited to being performed by this apparatus.
[0184] As shown in Figure 32, a procedure according to example embodiments comprises an operation of receiving (S321) a request for first data, an operation of obtaining (S322), as obtained data, said first data from a data store, an operation of compiling (S323), as compiled data, data based on said obtained data, said compiled data including general data in explicit form, at least one not-available shared-data set relating to said first data in explicit form, and at least one not-available shared-data set identifier corresponding to said at least one not-available shared-data set, and an operation of transmitting (S324) a data response including said compiled data.
[0185] Figure 18 is a block diagram illustrating an apparatus according to example embodiments. In particular, Figure 18 illustrates a variation of the apparatus shown in Figure 17. The apparatus according to Figure 18 may thus further comprise a deducing circuitry 181 and / or an analyzing circuitry 182.
[0186] In an embodiment at least some of the functionalities of the apparatus shown in Figure 17 (or 18) may be shared between two physically separate devices forming one operational entity. Therefore, the apparatus may be seen to depict the operational entity comprising one or more physically separate devices for executing at least some of the described processes.
[0187] According to further example embodiments, said request for first data is indicative of whether said request for first data also relates to not-available shared-data sets, and, if said request for first data is not indicative of that said request for first dataalso relates to not-available shared-data sets, said compiled data does not include said at least one not-available shared-data set in explicit form.
[0188] According to a variation of the procedure shown in Figure 32, exemplary additional operations are given, which are inherently independent from each other as such. According to such variation, an exemplary method according to example embodiments may comprise an operation of deducing, based on subscription information in relation to a requestor of said first data, information on available shared-data sets available at said requestor of said first data.
[0189] According to a variation of the procedure shown in Figure 32, exemplary additional operations are given, which are inherently independent from each other as such. According to such variation, an exemplary method according to example embodiments may comprise an operation of analyzing, based on said information on available shared-data sets, said obtained data for whether said obtained data includes at least one not-available shared-data set identifier, and an operation of obtaining, from said data store, said at least one not-available shared-data set corresponding to said at least one not-available shared-data set identifier.
[0190] According to a variation of the procedure shown in Figure 32, exemplary details of the obtaining operation are given, which are inherently independent from each other as such. Such exemplary obtaining operation according to example embodiments may comprise an operation of receiving, from said data store, said obtained data including said at least one not-available shared-data set in explicit form and said at least one not- available shared-data set identifier corresponding to said at least one not-available shared- data set.
[0191] According to further example embodiments, said compiled data includes at least one available shared-data set identifier corresponding to at least one available shared-data set as a shared-data set in referenced form.
[0192] Figure 19 is a block diagram illustrating an apparatus according to example embodiments. The apparatus may be a network entity 190, such as an access and mobility function entity or a unified data management entity, comprising a transmitting circuitry 191 and a receiving circuitry 192. The transmitting circuitry 191 transmits a subscription request for first data. The receiving circuitry 192 receives a message based on said subscription request, said message including information on at least one not-availableshared-data set relating to said first data. Figure 33 is a schematic diagram of a procedure according to example embodiments. The apparatus according to Figure 19 may perform the method of Figure 33 but is not limited to this method. The method of Figure 33 may be performed by the apparatus of Figure 19 but is not limited to being performed by this apparatus.
[0193] As shown in Figure 33, a procedure according to example embodiments comprises an operation of transmitting (S331) a subscription request for first data, and an operation of receiving (S332) a message based on said subscription request, said message including information on at least one not-available shared-data set relating to said first data.
[0194] Figure 20 is a block diagram illustrating an apparatus according to example embodiments. In particular, Figure 20 illustrates a variation of the apparatus shown in Figure 19. The apparatus according to Figure 20 may thus further comprise a storing circuitry 201.
[0195] In an embodiment at least some of the functionalities of the apparatus shown in Figure 19 (or 20) may be shared between two physically separate devices forming one operational entity. Therefore, the apparatus may be seen to depict the operational entity comprising one or more physically separate devices for executing at least some of the described processes.
[0196] According to further example embodiments, said subscription request for first data is indicative of whether said subscription request for first data also relates to not- available shared-data sets, and, if said subscription request for first data is not indicative of that said subscription request for first data also relates to not-available shared-data sets, said message does not include said information on said at least one not-available shared- data set.
[0197] According to further example embodiments, said subscription request is indicative of an immediate reporting demand, and said message is a subscription acknowledgement including said at least one not-available shared-data set and at least one not-available shared-data set identifier corresponding to said at least one not- available shared-data set.
[0198] According to further example embodiments, said message is a notification including information on changes of said at least one not-available shared-data set, and atleast one not-available shared-data set identifier corresponding to said at least one not- available shared-data set.
[0199] According to a variation of the procedure shown in Figure 33, exemplary additional operations are given, which are inherently independent from each other as such. According to such variation, an exemplary method according to example embodiments may comprise an operation of storing said at least one not-available shared- data set together with said corresponding not-available shared-data set identifier.
[0200] Figure 21 is a block diagram illustrating an apparatus according to example embodiments. The apparatus may be a network entity 210, such as a unified data management entity or a unified data repository entity, comprising a receiving circuitry 211, an obtaining circuitry 212, and a transmitting circuitry 214. The receiving circuitry 211 receives a subscription request for first data. The obtaining circuitry 212 obtains, as obtained data, said first data from a data store. The transmitting circuitry 214 transmits a message based on said subscription request, said message including information on at least one not-available shared-data set relating to said first data. Figure 34 is a schematic diagram of a procedure according to example embodiments. The apparatus according to Figure 21 may perform the method of Figure 34 but is not limited to this method. The method of Figure 34 may be performed by the apparatus of Figure 21 but is not limited to being performed by this apparatus.
[0201] As shown in Figure 34, a procedure according to example embodiments comprises an operation of receiving (S341) a subscription request for first data, an operation of obtaining (S342), as obtained data, said first data from a data store, and an operation of transmitting (S343) a message based on said subscription request, said message including information on at least one not-available shared-data set relating to said first data.
[0202] Figure 22 is a block diagram illustrating an apparatus according to example embodiments. In particular, Figure 22 illustrates a variation of the apparatus shown in Figure 21. The apparatus according to Figure 22 may thus further comprise a deducing circuitry 221, an analyzing circuitry 222, a forwarding circuitry 223, and / or an establishing circuitry 224.
[0203] In an embodiment at least some of the functionalities of the apparatus shown in Figure 21 (or 22) may be shared between two physically separate devices forming oneoperational entity. Therefore, the apparatus may be seen to depict the operational entity comprising one or more physically separate devices for executing at least some of the described processes.
[0204] According to further example embodiments, said subscription request for first data is indicative of whether said subscription request for first data also relates to not- available shared-data sets, and, if said subscription request for first data is not indicative of that said subscription request for first data also relates to not-available shared-data sets, said message does not include said information on said at least one not-available shared- data set.
[0205] According to a variation of the procedure shown in Figure 34, exemplary additional operations are given, which are inherently independent from each other as such. According to such variation, an exemplary method according to example embodiments may comprise an operation of deducing, based on subscription information in relation to a requestor of said first data, information on available shared-data sets available at said requestor of said first data.
[0206] According to a variation of the procedure shown in Figure 34, exemplary additional operations are given, which are inherently independent from each other as such. According to such variation, an exemplary method according to example embodiments may comprise an operation of analyzing, based on said information on available shared-data sets, said obtained data for whether said obtained data includes at least one not-available shared-data set identifier.
[0207] According to further example embodiments, said subscription request is indicative of an immediate reporting demand, and said message is a subscription acknowledgement including said at least one not-available shared-data set and at least one not-available shared-data set identifier corresponding to said at least one not- available shared-data set. In some embodiments, the shared data sets are only provided as part of the immediate reporting and no subscription for subsequent notifications about changes of shared data sets is established.
[0208] According to other example embodiments, a subscription for subsequent notifications about changes of shared data sets that relate to the obtained data is established. When one or several of the shared data sets are changed, a notification is provided. In some example embodiments, if several subscriptions for the same shareddata set have been established in relation to the same requestor, and that shared data set changes, only one notification relating to one of the established subscriptions is provided. In some embodiments, if a subscription for a shared data set in relation to the requestor is terminated, but said subscription request for data in relation to the requestor is still active, the procedure includes checking whether the shared data set with terminated subscription relates to the obtained data, and if so establishing a new subscription the shared data set with terminated subscription.
[0209] According to a variation of the procedure shown in Figure 34, exemplary additional operations are given, which are inherently independent from each other as such. According to such variation, an exemplary method according to example embodiments may comprise an operation of establishing, based on said obtained data, a subscription for not-available shared-data sets relating to said first data, said not-available shared-data sets including said at least one not-available shared-data set, wherein said message is a notification including information on changes of said at least one not- available shared-data set, and at least one not-available shared-data set identifier corresponding to said at least one not-available shared-data set.
[0210] According to a variation of the procedure shown in Figure 34, exemplary additional operations are given, which are inherently independent from each other as such. According to such variation, an exemplary method according to example embodiments may comprise an operation of obtaining, from said data store, said at least one not-available shared-data set.
[0211] According to a variation of the procedure shown in Figure 34, exemplary details of the obtaining operation are given, which are inherently independent from each other as such. Such exemplary obtaining operation according to example embodiments may comprise an operation of forwarding said at least one available shared-data set identifier to said data store, and an operation of receiving, from said data store, said obtained data including said at least one not-available shared-data set in explicit form.
[0212] Example embodiments outlined and specified above are explained below in more specific terms.
[0213] In particular, to address the identified issue that, so far, shared data can be retrieved only based on shared data IDs, according to example embodiments, if supported, the NF consumer of the Nudm_SDM service may retrieve shared data from the UDMbased on the type of shared data. Some parts of the retrieved shared data may be for immediate use at the NF consumer and may be stored for later use, other parts may not be used immediately but may be stored for potential later use and so avoid data retrieval at later use. Avoiding the need for subsequent data retrieval contributes to signaling load reduction and system stability.
[0214] Figure 35 shows a schematic diagram of signaling sequences according to example embodiments.
[0215] As illustrated in the example flow in Figure 35, according to example embodiments, the AMF sends a GET request to the UDM to retrieve all shared data of type AM-Data (rather than just the shared data of ID 17). The request may contain the query parameter shared-data-ID=17 to indicate the current need (not shown in Figure 35), but in addition may also contain the query parameter type=AM-Data indicating the desire / ability to receive additional shared AM-Data for later use.
[0216] Similarly, according to example embodiments, the GET request sent from UDM to UDR.
[0217] As a consequence, according to example embodiments, the 200 OK response message contains not only the shared data of ID 17 (which are needed for immediate use at the AMF) but also other shared AM data and their IDs (for potential later use at the AMF).
[0218] According to example embodiments, the UDM / UDR includes in the response the shared data of ID=17 and in addition may include all or a subset of all shared data of type AM-Data.
[0219] Once the AMF has received the shared data, according to example embodiments, the AMF subscribes to shared data change notifications using all the received IDs.
[0220] According to further example embodiments, if supported, the NF consumer of the Nudm_SDM service may 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 information element (IE), like• Allowed Slice: Slicel, Slice2, ...• Allowed PLMN: PLMnl , PLMN2, . . .Allowed NF consumer: AMF, SMF, . . .
[0221] Based on this metadata stored in the sharedData object, according to example embodiments, the sharedData object can be segregated per slice, per PLMN, or per requested Consumer NF Type.
[0222] According to example embodiments, a supported feature is defined for the above-described behavior, and the NF consumer will only use the query parameter “type” if the UDM or UDR supports this feature.
[0223] Figure 36 shows a schematic diagram of signaling sequences according to example embodiments.
[0224] As illustrated in Figure 36, according to example embodiments, an NF service consumer requests the sharedData along with more filter elements like Slice= Slice 1, type= SMData, accordingly. The UDM / UDR provides the sharedData having type= SMData and AllowedSlice= Slice 1.This advantageously leads to that more filters allows to keep shared data at different granularity, i.e., if SMF supporting a slicel, then it can download the smData applicable to slicel only.
[0225] Figure 37 shows a schematic diagram of signaling sequences according to example embodiments.
[0226] As illustrated in Figure 37, according to example embodiments, a NF service consumer (e.g. AMF or UDM) may provide one or several shared data type(s) in a request to subscribe to notifications about data changes towards a UDM or UDR.
[0227] The UDM or UDR then stores a subscription for notifications of changes for all shared data IDs matching the indicated types, and subsequently provides notifications when those shared data change.
[0228] According to example embodiments, a supported feature can be defined for the above-described behavior, and the NF consumer will subscribe to notifications of shared data type changes, if the UDM or UDR supports this feature.
[0229] Figure 38 shows a schematic diagram of signaling sequences according to example embodiments.
[0230] As illustrated in Figure 38, according to example embodiments, the subscription can be combined with a request of immediate reporting that enables a combination of retrieval and subscription as described above.
[0231] According to example embodiments, the procedure of Figure 38 may be modified in that instead of the indication "subscribed data=shared data type X", the NF service consumer provides as input a structure that indicates the conditions for the data to be subscribed.
[0232] According to example embodiments, this structure could be defined as follows:
[0233] Based on the above input / filter, an NF service consumer can subscribe e.g. to all Shared Data enties that contain e.g. the attribute "sharedVnGroupDatas", i.e. all shared data entries that contain Virtual Network data, or any other possible combination.
[0234] The above discussed approach to address the identified issue that, so far, shared data can be retrieved only based on shared data IDs, entails that all the shared data of a specific type (e.g. AM Data) is downloaded to the AMF, irrespective of whether the AMF is going to serve a UE that requires that data.
[0235] To address this and the identified issue that, so far, data retrieval mechanisms of Nudm and Nudr interfaces may be implemented only with two consecutive steps of retrievals, according to example embodiments, the following optimization is provided.
[0236] Figure 39 shows a schematic diagram of signaling sequences according to example embodiments.
[0237] As illustrated in Figure 39, according to example embodiments, an NF service consumer (e.g. AMF or UDM) may include in a request to retrieve data towards a UDM or UDR a list of shared data IDs identifying shared data (e.g. as “query” parameter in the HTTP request) that it has stored locally.
[0238] If the UDM or UDR determines that the NF service consumer does not have some of the shared data referenced within the requested data, then, according to example embodiments, the UDM or UDR additionally includes both the shared data ID and the actual shared data for that shared data ID in a response to the request for the retrieval of those data.
[0239] Figure 40 shows a schematic diagram of signaling sequences according to example embodiments.
[0240] As illustrated in Figure 40, according to example embodiments, an NF service consumer (e.g., AMF or UDM) may include in a request to subscribe to notifications about data changes for some indicated subscribed data towards a UDM or UDR a list of shared data IDs identifying shared data that it has stored locally (e.g., as “query” parameter in the HTTP request).
[0241] If the UDM or UDR determines that the NF service consumer does not have some of the shared data referenced within the subscribed data, then, according to example embodiments, the UDM or UDR stores a subscription for notifications about changes ofthose shared data and subsequently provides notifications including both shared data ID and actual changed shared data when any of those shared data change.
[0242] In the response to the subscription request, the UDM / UDR preferably includes information about the subscription for each of those shared data IDs and a separate subscription ID for each of those subscriptions. Those subscription IDs can be used in subsequent requests of the NF service consumer to modify or terminate the related subscriptions.
[0243] Figure 41 shows a schematic diagram of signaling sequences according to example embodiments.
[0244] As illustrated in Figure 41, according to example embodiments, the subscription can be combined with a request of immediate reporting that enables a combination of retrieval and subscription as described above.
[0245] According to example embodiments, a supported feature can be defined for the above-discussed behavior, and the NF consumer will use the query parameter “Available Shared data” only if the UDM or UDR supports this feature.
[0246] Figure 42 shows a schematic diagram of signaling sequences according to example embodiments.
[0247] As illustrated in Figure 42, according to example embodiments, when the AMF sends the first GET request to the UDM, it may indicate the list of shared data IDs that are available / stored at the AMF for that specific data type (e.g. AM Data).
[0248] If the UDM determines that the AMF already has the shared data ID that is associated with the UE, according to example embodiments, the UDM then only sends the shared data ID to the AMF in response.
[0249] If the UDM determines that the AMF does not have the shared data associated with the UE, then, according to example embodiments, the UDM first retrieves the shared data from UDR and includes both the shared data ID associated with the UE subscription and the actual shared data corresponding to that shared data ID.
[0250] With this approach, the AMF does not need to make the second query to retrieve the shared data with the shared data ID or shared data type. Only a single query is sufficient to provide the necessary data. Additionally, the AMF does not need to store some shared data that it may not use all.
[0251] The UDM would still need to do two queries. First to get the AM data. After that, if the AM data has a shared data ID, and the shared data ID is not in the list provided by the AMF, then UDM further queries UDR to get the shared data and include both shared data ID and the shared data in the response.
[0252] AMF would need to perform one subscribe operation for each shared data ID to subscribe to notification on change of the shared data.
[0253] Hence, in addition to the above-discussed optimization on the interface between consumer (e.g. AMF) and UDM, according to example embodiments, a similar optimization is provided for the interface between UDM and UDR: According thereto, the first GET message sent from UDM to UDR (see Figure 42) is extended with the list of available shared AM-data. The UDR then checks whether the AM-Data requested by the UDM contains a shared data ID pointing to shared data not yet available at the UDM. If so, the UDR sends not only the requested AM-data but also the shared data in the 200 OK response message to the UDM. By doing so, sending the second GET message (and 200 OK response message) can be avoided.
[0254] Once data are retrieved, the consumer may want to subscribe to data change notifications, i.e., sends a POST request message to the UDM / UDR asking the UDM / UDR to send a notification message to the consumer when the data at the UDM / UDR are modified (e.g. due to data provisioning actions at the UDM / UDR). This is to ensure data consistency between consumer (e.g. AMF) and UDM / UDR. The two- step approach (i.e. retrieval (GET) followed by subscription to change notification (POST)) has already been optimized above, allowing a single step procedure by omitting the GET request and extending the POST request with an indication of immediate data reporting. The UDM / UDR then not only monitors the data to detect changes in order to being able of sending notifications to the consumer when data are changed, but also includes the current value of the monitored data in the POST response message acknowledging the subscribe request.
[0255] The following may occur in such case.
[0256] The consumer (e.g. AMF) sends a POST request message to the UDM including the immediate report indication in order to subscribe to AM-data change notifications and to retrieve AM-data (similarly UDM to UDR).
[0257] The AM-data sent back in the POST response, however, may contain a shared data ID indicating that the AM-data are incomplete and need to be extended / merged with some shared data. As a consequence, the AMF (if it not already has cached the shared data and not already has subscribed to shared data change notifications) needs to retrieve and subscribe to the shared data.
[0258] Hence, in addition to the above-discussed optimization on the interface between consumer, according to example embodiments, the extra signaling (retrieve and subscribe to shared data) is avoided by including a list of shared data IDs identifying shared data already available (and already subscribed for data change notifications) at the consumer (e.g. AMF) in the subscribe with immediate response indicator request message (POST).
[0259] The UDM then checks whether the AM-data to be sent in the POST response contains a shared data ID pointing to shared data that are not already available and not already subscribed by the AMF, and if so, according to example embodiments, sends not only the requested AM-data but also the shared data in the POST response to the AMF, and monitors not only the AM-data but also the shared data in order to being able of sending notifications to the consumer (e.g. AMF) not only when the AM-data are changed but also when the shared data are changed.
[0260] To further address the identified issue that, so far, data retrieval mechanisms of Nudm and Nudr interfaces may be implemented only with two consecutive steps of retrievals, according to example embodiments, the following optimization is provided.
[0261] Figure 43 shows a schematic diagram of signaling sequences according to example embodiments.
[0262] As illustrated in Figure 43, according to example embodiments, an NF service consumer (e.g. AMF or UDM) sends a request to retrieve data towards a UDM or UDR. In some embodiments, the NF service consumer provides a query parameter or indicates a supported feature to request that the UDM or UDR includes shared data in the response. Based on subscriptions to shared data IDs of that NF consumer, the UDM or UDR determines whether the NF service consumer does not have some of the shared data referenced within the requested data. Namely, a principle behind these example embodiments is that the UDM or UDR assumes that the NF consumer already has shared data IDs for which it has previously subscribed.
[0263] If the NF service consumer does not have some of the shared data referenced within the requested data, according to example embodiments, the UDM or UDR additionally includes both the shared data ID and the actual shared data for that shared data ID in the response to the request for the retrieval of those data.
[0264] Figure 44 shows a schematic diagram of signaling sequences according to example embodiments.
[0265] As illustrated in Figure 44, according to example embodiments, an NF service consumer (e.g. AMF or UDM) may request to subscribe to notifications about data changes for some indicated subscribed data towards a UDM or UDR. In some embodiments, the NF service consumer provides a query parameter or indicates a supported feature to request that the UDM or UDR includes shared data in the subscription.
[0266] Based on already existing subscriptions to shared data IDs of that NF consumer, the UDM or UDR determines whether the NF service consumer does not have subscriptions for some of the shared data IDs referenced within the subscribed data.
[0267] If the UDM or UDR determines that the NF service consumer does not have subscriptions for some of the shared data referenced within the subscribed data, then, according to example embodiments, the UDM or UDR stores a subscription for notifications about changes of those shared data, and subsequently provides notifications including both shared data ID and actual changed shared data when any of those shared data change.
[0268] In the response to the subscription request, the UDM / UDR preferably includes information about the subscription for each of those shared data IDs and a separate subscription ID for each of those subscriptions. Those subscription IDs can be used in subsequent request of the NF service consumer to modify or terminate the related subscriptions.
[0269] Figure 45 shows a schematic diagram of signaling sequences according to example embodiments.
[0270] As illustrated in Figure 45, according to example embodiments, the subscription can be combined with a request of immediate reporting that enables a combination of retrieval and subscription as described above.
[0271] According to example embodiments, a supported feature can be defined for the above-explained behavior, and the NF consumer will only use the query parameter “includeShared data”, if the UDM or UDR supports this feature.
[0272] The approaches to address the identified issue that, so far, data retrieval mechanisms of Nudm and Nudr interfaces may be implemented only with two consecutive steps of retrievals, as discussed above, and the approaches to further address the identified issue that, so far, data retrieval mechanisms of Nudm and Nudr interfaces may be implemented only with two consecutive steps of retrievals, as discussed above, can be combined with the approaches to address the identified issue that, so far, shared data can be retrieved only based on shared data IDs, as discussed above.
[0273] In particular, the approaches to address the identified issue that, so far, shared data can be retrieved only based on shared data IDs, as discussed above, can be used to constrain the shared data that will be returned by the UDM / UDR in the approaches to address the identified issue that, so far, data retrieval mechanisms of Nudm and Nudr interfaces may be implemented only with two consecutive steps of retrievals, as discussed above, and the approaches to further address the identified issue that, so far, data retrieval mechanisms of Nudm and Nudr interfaces may be implemented only with two consecutive steps of retrievals, as discussed above.
[0274] For example, if the NF service consumer provides in the request (or the UDM / UDR determines by itself) the information that it has ID1 and ID4, but is only interested in Shared Data of a specific type or shared data which fulfil certain conditions, and the UDM determines to return ID 17 and ID21, but ID 17 does not fulfil a condition indicated in the consumer request, then only ID21 will be returned.
[0275] The principles underlying example embodiments may be specified / standardized as follows.
[0276] Access and Mobility Subscription Data Retrieval may be defined as below.
[0277] Figure 46 ("Requesting a UE's Access and Mobility Subscription Data") shows a schematic diagram of signaling sequences according to example embodiments, and in particular shows a scenario where the NF service consumer (e.g. AMF) sends a request to the UDM to receive the UE's Access and Mobility Subscription data (see also 3GPP TS 23.502 [3] figure 4.2.2.2.2-1 step 14). The request contains the UE's identity ( / { supi } ),the type of the requested information ( / am-data) and query parameters (supported- features, plmn-id, shared-data-ids).
[0278] At 1, the NF service consumer (e.g. AMF) sends a GET request to the resource representing the UE's Access and Mobility Subscription Data, with query parameters indicating the supported-features and / or plmn-id and / or shared-data-ids.
[0279] The optional query parameter shared-data-ids may be included by the NF service consumer to indicate to the UDM that shared AccessAndMobilitySubscriptionData identified by the shared-data-ids are already available at the NF service consumer.
[0280] At 2a, on success, the UDM responds with "200 OK" with the message body containing the UE's Access and Mobility Subscription Data as relevant for the requesting NF service consumer. If the UE's Access and Mobility Subscription Data contains the attribute sharedAmDatalDs identifying shared AccessAndMobilitySubscriptionData, and those are not already available at the NF consumer (i.e. the shared data IDs are not included in the shared-data-ids query parameter in the GET request message), the UE's Access and Mobility Subscription Data sent in the 200 OK message body may also contain a list of shared Access And Mobility Subscription data relevant to the UE but not yet available at the NF service consumer.
[0281] NOTE 1 : If the UDM initiated a request to obtain SoR information from the SOR-AF, the UDM starts an operator configurable timer up to which the UDM shall wait for a response from the SOR-AF for retrieving the SoR information. The UDM responds back to the NF service consumer for Access and Mobility Subscription Data Retrieval service operation before the timer expires. If the SOR-AF has not provided a response with the SoR information before the timer expires, the UDM shall behave as specified in clause C.2 of 3GPP°TS°23.122
[0020] (step 3d). As described in clause C.2 of 3GPP°TS°23.122
[0020] (step 4), if UDM supports SOR-CMCI, then UDM indicates in the response to NF service consumer (i.e. AMF) to send acknowledgement that will include the "ME support of SOR-CMCI". UDM will also delete the "ME support of SOR-CMCI" updating AuthenticationSoR of Nudr_DataRepository service as specified in 3GPP TS 29.505
[0010] clause 5.2.25, if the UE is performing initial registration or emergency registration. UDM will decide whether to provide SOR-CMCI based on "usimSupportOfSorCmci" retrieved via AuthenticationSoR of Nudr_DataRepository service as specified in 3GPP TS 29.505
[0010] clause 5.2.25.
[0282] At 2b, if there is no valid subscription data for the UE, HTTP status code "404 Not Found" shall be returned including additional error information in the response body (in the "ProblemDetails" element).
[0283] NOTE 2: Upon reception of any Nudm_EventExposure operation or Nudm_PP operation, or when the validity of an event subscription or provisioned parameter with its associated maximum latency, maximum response time or DL Buffering Suggested Packet Count value expires, UDM may need to adjust the values of active time and / or periodic registration timer and / or DL Buffering Suggested Packet Count. The UDM shall notify AMF and / or SMF if the values are updated (see clause 4.15.3.2.3b and 4.15.6.3a of 3GPP TS 23.502 [3]).
[0284] NOTE 3: If UPU data have previously been provisioned, but have not yet been acknowledged by the UE, e.g. because no AMF was registered at provisioning time, the UDM needs to convey the UPU data (after AUSF protection) within 200 OK AccessAndMobilitySubscriptionDatato to the AMF.
[0285] On failure, the appropriate HTTP status code indicating the error shall be returned and appropriate additional error information should be returned in the GET response body.
[0286] Subscription to notifications of data change may be defined as below.
[0287] Figure 47 ("NF service consumer subscribes to notifications") shows a schematic diagram of signaling sequences according to example embodiments, and in particular shows a scenario where the NF service consumer sends a request to the UDM to subscribe to notifications of data change (see also 3GPP TS 23.502 [3] figure 4.2.2.2.2-1 step 14). The request contains a callback URI and the URI of the monitored resource.
[0288] At 1, the NF service consumer sends a POST request to the parent resource (collection of subscriptions) (... / {ueld} / sdm-subscriptions), to create a subscription as present in message body. The payload body of the POST request shall contain a representation of the individual subscription resource to be created. An NF consumer supporting the "Limitedsubscriptions" feature shall create only one unique subscription per UE (identified by the ueld in URI) without additional filter criteria, or with a specific filter criteria (e.g. dnn and / or singleNssai), and set the "uniqueSubscription" IE with the value "true" in request body.
[0289] At 2a, on success, the UDM responds with "201 Created" with the message body containing a representation of the created subscription. The Location HTTP header shall contain the URI of the created subscription.
[0290] If the SdmSubscription received in the POST request contains the immediateReport indication, the SdmSubscription in the "201 Created" response may also contain a report attribute with the current representation of the subscribed data.
[0291] In addition, if the received POST request contains the optional query parameter shared-data-ids identifying shared data available (and subscribed) at the NF service consumer, and the current representation of the subscribed data contains shared data IDs identifying shared data not yet available (and not yet subscribed) at the NF service consumer, the current representation of the subscribed data sent in the "201 Created" response shall also contain shared data that are not yet available at the NF service consumer. In addition, the UDM may add the resource URI of the not yet subscribed shared data to the list of monitored resource URIs as received in the request, and monitor also these shared data.
[0292] In case of partial success, "201 Created" should contain only the monitores resource Uris that are supported by the UDM.
[0293] At 2b, if there is no valid subscription data for the UE, HTTP status code "404 Not Found" shall be returned including additional error information in the response body (in the "ProblemDetails" element).
[0294] At 2c, if the UE subscription data exist, but the requested subscription to data change notification cannot be created (e.g. due to an invalid / unsupported data reference to be monitored, contained in the SdmSubscription parameter), HTTP status code "501 Not Implemented" shall be returned including additional error information in the response body (in the "ProblemDetails" element).
[0295] " 501 Not Implemented" shall be returned only when none of the montitoredResourceUris are supported by the UDM.
[0296] On failure, the appropriate HTTP status code indicating the error shall be returned and appropriate additional error information should be returned in the POST response body.
[0297] POST may be defined as below.
[0298] This method shall support the URI query parameters specified in table ("URI query parameters supported by the POST method on this resource") below.
[0299] This method shall support the request data structures specified in table ("Data structures supported by the POST Request Body on this resource") below.
[0300] This method shall support the response data structures and response codes specified in table ("Data structures supported by the POST Response Body on this resource") below.
[0301] NOTE: In the scenario of stateless UDM deployment, it is assumed that stateless UDMs are organized into several UDM groups, and for each UDM group an FQDN can be allocated.
[0302] Headers supported by the 201 Response Code on this resource are defined in the table below.
[0303] GET may be defined as below.
[0304] This method shall support the URI query parameters specified in table ("URI query parameters supported by the GET method on this resource") below.
[0305] If "plmn-id" is included, UDM shall return the Access and Mobility Data for the SUPI associated to the PLMN or SNPN identified by "plmn-id".
[0306] If "plmn-id" is not included, UDM shall return the Access and Mobility Data for the SUPI associated to the HPLMN.
[0307] This method shall support the request data structures specified in table ("Data structures supported by the GET Request Body on this resource") below.
[0308] This method shall support the response data structures and response codes specified in table ("Data structures supported by the GET Response Body on this resource") below.
[0309] Headers supported by the GET method on this resource are defined in the table below.
[0310] Headers supported by the 200 Response Code on this resource are defined in the table below.
[0311] Type AccessAndMobilitySubscriptionData may be defined as below:
[0312] Definition of type AccessAndMobilitySubscriptionData is defined in the table below.Nudm_SDM API may be defined as below: openapi: 3.0.0 / {supi} / am-data: get: summary: retrieve a UE's Access and Mobility Subscription Data operationld: 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: Identifier of the UE required: true schema:$ref: 'TS2957 l_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: Serving 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' minltems: 1 style: form explode: false- name: disaster-roaming-ind in: query description: Indication whether Disaster Roaming service is applied or not required: falseschema: type: boolean default: false- name: shared-data-ids in: query description: List of IDs identifying shared Access and Mobility Subscription Data already available at the NF service consumer schema: type: array items:$ref : '# / components / schemas / SharedD atald' style: form explode: false- name: If-None-Match in: header description: Validator for conditional requests, as described in RFC 7232, 3.2 schema: type: string- name: If-Modified-Since in: header description: Validator for conditional requests, as described in RFC7232, 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: Cache-Control containing max-age, as described in RFC 7234, 5.2 schema: type: stringETag: description: Entity Tag, containing a strong validator, as described in RFC 7232, 2.3 schema: type: stringLast-Modified: description: Timestamp for last modification of the resource, as described in RFC 7232, 2.2 schema: type: string'400':$ref: 'TS2957 l_CommonData.yaml# / components / responses / 400'$ref: 'TS29571_CommonData.yaml# / components / responses / 40r '403':$ref: 'TS2957 l_CommonData.yaml# / components / responses / 403''404':$ref: 'TS2957 l_CommonData.yaml# / components / responses / 404' '406':$ref: 'TS2957 l_CommonData.yaml# / components / responses / 406' '429':$ref: 'TS2957 l_CommonData.yaml# / components / responses / 429''500':$ref: 'TS2957 l_CommonData.yaml# / components / responses / 500' '502':$ref: 'TS2957 l_CommonData.yaml# / components / responses / 502' '503':$ref: 'TS2957 l_CommonData.yaml# / components / responses / 503' default: description: Unexpected error / {ueld} / sdm-subscriptions: post: summary: subscribe to notifications operationld: Subscribe tags:- Subscription Creation security:- { }- oAuth2ClientCredentials:- nudm-sdm- oAuth2ClientCredentials:- nudm-sdm- nudm-sdm:sdm-subscriptions:create parameters:- name: ueld in: path description: Identity of the user required: true schema:$ref:'TS29571 _Common Data.yaml# / componcnts / schcmas / V arUeld'- name: shared-data-ids in: query description: List of IDs identifying shared Data already available at and subscribed by the NF service consumer schema: type: array items:$ref : '# / components / schemas / SharedD atald' 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: 'Contains the URI of the newly created resource, according to the structure: {apiRoot} / nudm-sdm / <apiVersion> / {ueId} / sdm- subscriptions / { subscription^} ' required: true schema: type: string'400':$ref: 'TS2957 l_CommonData.yaml# / components / responses / 400''401':$ref: 'TS29571_CommonData.yaml# / components / responses / 40r'403':$ref: 'TS2957 l_CommonData.yaml# / components / responses / 403''404':$ref: 'TS2957 l_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: 'TS2957 l_CommonData.yaml# / components / responses / 429''500':$ref: 'TS2957 l_CommonData.yaml# / components / responses / 500''501':$ref: 'TS29571_CommonData.yaml# / components / responses / 50r '502':$ref: 'TS2957 l_CommonData.yaml# / components / responses / 502' '503':$ref: 'TS2957 l_CommonData.yaml# / components / responses / 503' default: description: Unexpected error callbacks: datachangeNotification:' {request. body# / callbackReference } ' : post: requestBody: required: truecontent: 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:'TS2957 l_CommonData.yaml# / components / responses / 40r'403':$ref:'TS29571_CommonData.yaml# / components / responses / 403''404':$ref:'TS29571_CommonData.yaml# / components / responses / 404'’411’:$ref:'TS2957 l_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: truecontent: application / json: schema:$ref:'TS29503_Nudm_UECM.yaml# / components / schemas / DataRestorationNotificati on' 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 errorAccessAndMobilitySubscriptionData: type: object properties: supportedFeatures :$ref:'TS29571_CommonData.yaml# / components / schemas / SupportedFeatures' gpsis: type: array items:$ref: 'TS2957 l_CommonData.yaml# / components / schemas / Gpsi' hssGroupId:$ref:'TS29571_CommonData.yaml# / components / schemas / NfGroupId' internalGroupIds : type: array items:$ref:'TS29571_CommonData.yaml# / components / schemas / GroupId' minltems: 1 sharedV nGroupDatalds :description: A map(list of key- value pairs) where Groupld serves as key of SharedDatald type: object additionalProperties :$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: 'TS2957 l_CommonData.yaml# / components / schemas / Area' serviceAreaRestriction :$ref:'TS29571_CommonData.yaml# / components / schemas / ServiceAreaRestriction' coreNetworkTypeRestrictions: type: arrayitems:$ref:'TS29571_CommonData.yaml# / components / schemas / CoreNetworkType' accessTypeRestrictions: type: array items:$ref:'TS29571_CommonData.yaml# / components / schemas / AccessType' maxitems: 2 rfsplndex:$ref:'TS29571_CommonData.yaml# / components / schemas / RfspIndexRm' subsRegTimer:$ref:'TS29571_CommonData.yaml# / components / schemas / DurationSecRm' ueUsageType:$ref : '# / components / schemas / UeUs ageT ype' mpsPriority:$ref : '# / components / schemas / MpsPriority Indicator' mcsPriority:$ref: '# / components / schemas / McsPriorityIndicator' activeTime:$ref:'TS29571_CommonData.yaml# / components / schemas / DurationSecRm' sorlnfo:$ref : '# / components / schemas / SorInfo'sorlnfoExpectlnd: type: boolean sorafRetrieval: type: boolean default: false sorUpdatelndicatorList: type: array items:$ref: '# / components / schemas / SorUpdateIndicator' minltems: 1 upulnfo:$ref : '# / components / schemas / UpuInfo' routingindicator: type: string pattern: 'A[0-9]{ 1,4}$' mico Allowed:$ref : '# / components / schemas / Mico Allowed' sharedAmDatalds : type: array items:$ref: '# / components / schemas / SharedDataId' minltems: 1 odbPacketServices:$ref:'TS29571_CommonData.yaml# / components / schemas / OdbPacketServices'subscribedDnnList: type: array items: any Of:$ref:'TS29571_CommonData.yaml# / components / schemas / Dnn'$ref:'TS29571_CommonData.yaml# / components / schemasAVildcardDnn' serviceGapTime:$ref:'TS29571_CommonData.yaml# / components / schemas / DurationSec' mdtUserConsent:$ref : '# / components / schemas / MdtU serConsent' mdtConfiguration :$ref:'TS29571_CommonData.yaml# / components / schemas / MdtConfiguration' traceData:$ref:'TS29571_CommonData.yaml# / components / schemas / TraceData' cagData:$ref: '# / components / schemas / CagData' stnSr:$ref: 'TS2957 l_CommonData.yaml# / components / schemas / StnSr' cMsisdn:$ref:'TS29571_CommonData.yaml# / components / schemas / CMsisdn'nbloTUePriority:$ref: '# / components / schemas / NbIoTUePriority' nssailnclusionAllowed: type: boolean default: false rgWirelineCharacteristics :$ref:'TS29571_CommonData.yaml# / components / schemas / RgWirelineCharacteristics ecRe s trictionD ata Wb :$ref: '# / components / schemas / EcRestrictionDataWb' ecRestrictionDataNb: type: boolean default: false expectedU eB ehaviourList :$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 edrxParameter sList : type: array items:$ref: '# / components / schemas / EdrxParameters' minltems: 1 ptwParametersList : type: array items:$ref: '# / components / schemas / PtwParameters' minltems: 1 iabOperationAllowed: type: boolean default: false adj acentPlmnRestrictions : description: A map (list of key-value pairs where Plmnld serves as key) of PlmnRestriction type: object additionalProperties :$ref: '# / components / schemas / PlmnRestriction' minProperties: 1 wirelineForbidden Areas : type: array items:$ref:'TS29571_CommonData.yaml# / components / schemasAVirelineArea' wirelineServiceAreaRestriction:$ref:'TS29571_CommonData.yaml# / components / schemasAVirelineServiceAreaRestr iction' pcfSelectionAssistancelnfos : type: array items:$ref: '# / components / schemas / PcfSelectionAssistanceInfo' minltems: 1 aerialUeSublnfo:$ref: '# / components / schemas / AerialUeSubscriptionInfo' roamingRestrictions :$ref:'TS29571_CommonData.yaml# / components / schemas / RoamingRestrictions' remoteProvInd: type: boolean default: false3gppChargingCharacteristics :$ref: '# / components / schemas / 3GppChargingCharacteristics' timeSyncData:$ref: '# / components / schemas / TimeSyncData' sharedDataList: type: array items:$ref: '# / components / schemas / SharedData' minltems: 1
[0313] The above-described procedures and functions may be implemented by respective functional elements, processors, or the like, as described below.
[0314] In the foregoing exemplary description of the network entity, only the units that are relevant for understanding the principles of the disclosure have been described using functional blocks. The network entity may comprise further units that are necessary for its respective operation. However, a description of these units is omitted in this specification. The arrangement of the functional blocks of the devices is not construed to limit the disclosure, and the functions may be performed by one block or further split into sub-blocks.
[0315] When in the foregoing description it is stated that the apparatus, i.e. network entity (or some other means) is configured to perform some function, this is to be construed to be equivalent to a description stating that a (i.e. at least one) processor or corresponding circuitry, potentially in cooperation with computer program code stored in the memory of the respective apparatus, is configured to cause the apparatus to perform at least the thus mentioned function. Also, such function is to be construed to be equivalently implementable by specifically configured circuitry or means for performing the respective function (i.e., the expression “unit configured to" is construed to be equivalent to an expression such as “means for”).
[0316] In Figure 48, an alternative illustration of apparatuses according to example embodiments is depicted. As indicated in Figure 48, according to example embodiments, the apparatus (network node) 10’ (corresponding to the network node 10) comprises a processor 481, a memory 482 and an interface 483, which are connected by a bus 484 or the like. Further, according to example embodiments, the apparatus (network node) 30’ (corresponding to the network node 30) comprises a processor 481, a memory 482 and an interface 483, which are connected by a bus 484 or the like. Further, according to example embodiments, the apparatus (network node) 50’ (corresponding to the network node 50) comprises a processor 481, a memory 482 and an interface 483, which are connected by a bus 484 or the like. Further, according to example embodiments, the apparatus (networknode) 70’ (corresponding to the network node 70) comprises a processor 481, a memory482 and an interface 483, which are connected by a bus 484 or the like. Further, according to example embodiments, the apparatus (network node) 90’ (corresponding to the network node 90) comprises a processor 481, a memory 482 and an interface 483, which are connected by a bus 484 or the like. Further, according to example embodiments, the apparatus (network node) 100’ (corresponding to the network node 100) comprises a processor 481, a memory 482 and an interface 483, which are connected by a bus 484 or the like. Further, according to example embodiments, the apparatus (network node) 120’ (corresponding to the network node 120) comprises a processor 481, a memory 482 and an interface 483, which are connected by a bus 484 or the like. Further, according to example embodiments, the apparatus (network node) 140’ (corresponding to the network node 140) comprises a processor 481, a memory 482 and an interface 483, which are connected by a bus 484 or the like. Further, according to example embodiments, the apparatus (network node) 160’ (corresponding to the network node 160) comprises a processor 481, a memory 482 and an interface 483, which are connected by a bus 484 or the like. Further, according to example embodiments, the apparatus (network node) 170’ (corresponding to the network node 170) comprises a processor 481, a memory 482 and an interface 483, which are connected by a bus 484 or the like. Further, according to example embodiments, the apparatus (network node) 190’ (corresponding to the network node 190) comprises a processor 481, a memory 482 and an interface 483, which are connected by a bus 484 or the like. Further, according to example embodiments, the apparatus (network node) 210’ (corresponding to the network node 210) comprises a processor 481, a memory 482 and an interface 483, which are connected by a bus 484 or the like. The apparatuses (10’, 30’, 50’, 70’, 90’, 100’, 120’, 140’, 160’, 170’, 190’, 210’) may be connected to other apparatuses, e.g. respective others of the apparatuses (10’, 30’, 50’, 70’, 90’, 100’, 120’, 140’, 160’, 170’, 190’, 210’), via link 485, respectively.
[0317] The processor 481 and / or the interface 483 may also include a modem or the like to facilitate communication over a (hardwire or wireless) link, respectively. The interface483 may include a suitable transceiver coupled to one or more antennas or communication means for (hardwire or wireless) communications with the linked or connected device(s), respectively. The interface 483 is generally configured to communicate with at least one other apparatus, i.e. the interface thereof.
[0318] The memory 482 may store respective programs assumed to include program instructions or computer program code that, when executed by the respective processor, enables the respective electronic device or apparatus to operate in accordance with the example embodiments (in particular in accordance with the methods explained with reference to any of Figures 23 to 34).
[0319] In general terms, the respective devices / apparatuses (and / or parts thereof) may represent means for performing respective operations and / or exhibiting respective functionalities (in particular the methods explained with reference to any of Figures 23 to 34), and / or the respective devices (and / or parts thereof) may have functions for performing respective operations and / or exhibiting respective functionalities.
[0320] When it is stated that the processor (or some other means) is configured to perform some function, this is to be construed to be equivalent to a description stating that at least one processor, potentially in cooperation with computer program code stored in the memory of the respective apparatus, is configured to cause the apparatus to perform at least the thus mentioned function. Also, such function is to be construed to be equivalently implementable by specifically configured means for performing the respective function (i.e. the expression “processor configured to [cause the apparatus to] perform xxx-ing” is construed to be equivalent to an expression such as “means for xxx- ing”).
[0321] For further details regarding the operability / functionality of the individual apparatuses, reference is made to the above description in connection with any one of Figures 1 to 47, respectively.
[0322] For the purpose of the present disclosure as described herein above, it should be noted that- method steps likely to be implemented as software code portions and being run using a processor at a network server or network entity (as examples of devices, apparatuses and / or modules thereof, or as examples of entities including apparatuses and / or modules therefore), are software code independent 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 step is suitable to be implemented as software or by hardware without changing the idea of the embodiments and its modification in terms of the functionality implemented;- method steps and / or devices, units or means likely to be implemented as hardware components at the above-defined apparatuses, or any module(s) thereof, (e.g., devices carrying out the functions of the apparatuses according to the embodiments as described above) are hardware independent and can be implemented using any known or future developed hardware technology or any hybrids of these, such as MOS (Metal Oxide Semiconductor), CMOS (Complementary MOS), BiMOS (Bipolar MOS), BiCMOS (Bipolar CMOS), ECL (Emitter Coupled Logic), TTL (Transistor-Transistor Logic), etc., using for example ASIC (Application Specific IC (Integrated Circuit)) components, FPGA (Field-programmable Gate Arrays) components, CPLD (Complex Programmable Logic Device) components or DSP (Digital Signal Processor) components;- devices, units or means (e.g. the above-defined network entity or network register, or any one of their respective units / means) can be implemented as individual devices, units or means, but this does not exclude that they are implemented in a distributed fashion throughout the system, as long as the functionality of the device, unit or means is preserved;- an apparatus like the user equipment and the network entity / network register may be represented by a semiconductor chip, a chipset, or a (hardware) module comprising such chip or chipset; this, however, does not exclude the possibility that a functionality of an apparatus or module, instead of being hardware implemented, be implemented as software in a (software) module such as a computer program or a computer program product comprising executable software code portions for execution / being run on a processor;- a device may be regarded as an apparatus or as an assembly of more than one apparatus, whether functionally in cooperation with each other or functionally independently of each other but in a same device housing, for example.
[0323] In general, it is to be noted that respective functional blocks or elements according to above-described aspects can be implemented by any known means, either in hardware and / or software, respectively, if it is only adapted to perform the describedfunctions of the respective parts. The mentioned method steps can be realized in individual functional blocks or by individual devices, or one or more of the method steps can be realized in a single functional block or by a single device.
[0324] Generally, any method step is suitable to be implemented as software or by hardware without changing the idea of the present disclosure. Devices and means can be implemented as individual devices, but this does not exclude that they are implemented in a distributed fashion throughout the system, as long as the functionality of the device is preserved. Such and similar principles are to be considered as known to a skilled person.
[0325] Software in the sense of the present description comprises software code as such comprising code means or portions or a computer program or a computer program product for performing the respective functions, as well as software (or a computer program or a computer program product) embodied on a tangible medium such as a computer-readable (storage) medium having stored thereon a respective data structure or code means / portions or embodied in a signal or in a chip, potentially during processing thereof.
[0326] The present disclosure also covers any conceivable combination of method steps and operations described above, and any conceivable combination of nodes, apparatuses, modules or elements described above, as long as the above-described concepts of methodology and structural arrangement are applicable.
[0327] In view of the above, there are provided measures for shared data retrieval optimization. Such measures exemplarily comprise transmitting a request for first data, said request including 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, said compiled data including general data in explicit form, at least one not-available shared-data set in explicit form, and at least one not-available shared-data set identifier corresponding to said at least one not-available shared-data set.
[0328] Even though the disclosure is described above with reference to the examples according to the accompanying drawings, it is to be understood that the disclosure is not restricted thereto. Rather, it is apparent to those skilled in the art that the present disclosure can be modified in many ways without departing from the scope of the inventive idea as disclosed herein.
[0329] List of acronyms and abbreviations3GPP Third Generation Partnership ProjectUDM unified data managementUDR unified data repositoryUE user equipmentID identifierNF network functionAM access and mobilityIE information elementAMF access and mobility management function
Claims
Claims1. A method for a network function service consumer, the method comprising transmitting a request for data, said request including at least one shared-data set identifier corresponding to at least one shared-data set that is available to the network function service consumer; and receiving a response to the request for data, the response including compiled data, said compiled data including general data in explicit form, at least shared-data set that is not available to the network function service consumer in explicit form, and at least shared-data set identifier corresponding to said at least one shared-data set that is not available to the network function service consumer.
2. The method according to claim 1, wherein said compiled data includes at least one of said at least one shared-data set identifier corresponding to at least one of said at least one shared-data set available to the network function service consumer as a shared-data set in referenced form.
3. An apparatus comprising network function service consumer configured to perform: transmitting a request for data, said request including at least one shared-data set identifier corresponding to at least one shared-data set that is available to the network function service consumer; and receiving a response to the request for data, the response including compiled data, said compiled data including general data in explicit form, at least shared-data set that is not available to the network function service consumer in explicit form, and at least shared-data set identifier corresponding to said at least one shared-data set that is not available to the network function service consumer.
4. The apparatus of claim 3, wherein said compiled data includes at least one of said at least one shared-data set identifier corresponding to at least one of said at least one shared- data set available to the network function service consumer as a shared-data set in referenced form.
5. An apparatus comprising: at least one processor; and at least one memory storing instructions of a network function service consumer, wherein the instructions when executed by the at least one processor, cause the apparatus to perform the method of claim 1 or 2.
6. A non-transitory computer-readable medium comprising instructions of a network function service consumer, wherein the instructions, when executed by the at least one processor of an apparatus, cause the apparatus to perform the method of claim 1 or 2.
7. A computer program comprising instructions of a network function service consumer, wherein when the program is executed by an apparatus, cause the apparatus to carry out the method of claim 1 or 2.
8. A method for a network entity, the method comprising: receiving, from a network function service consumer, a request for data, said request including at least one shared-data set identifier corresponding to at least one shared-data set available to the network function service consumer; obtaining, as obtained data, said data from a data store; compiling, as compiled data, data based on said obtained data, said compiled data including general data in explicit form, at least one shared-data set not available to the network function service consumer in explicit form, and at least one shared-data set identifier corresponding to said at least one shared-data set not available to the network function service consumer; and transmitting a response to said request for data, said response including said compiled data.
9. The method according to claim 8, wherein said compiled data includes at least one of said at least one shared-data set identifier corresponding to at least one of said at least one shared-data set available to the network function service consumer as a shared-data set in referenced form.
10. The method according to claim 8 or 9, further comprising: analyzing said obtained data for whether said obtained data includes at least one shared-data set identifier corresponding to at least one of said at least one shared-data set not available to the network function service consumer; and obtaining, from said data store, said at least one shared-data set corresponding to said at least one shared-data set identifier not available to the network function service consumer.
11. The method according to claim 9 or 9, wherein the obtaining further comprises: forwarding said at least one shared-data set identifier corresponding to the at least one of said at least one shared-data set not available to the network function service consumer to said data store; and receiving, from said data store, said obtained data including said at least one shared-data set not available to the network function service consumer in explicit form and said at least one shared-data set identifier corresponding to said at least one shared-data set not available to the network function service consumer.
12. An apparatus comprising a network entity configured to perform the method of any of claims 8 to 11.
13. An apparatus comprising: at least one processor; and at least one memory storing instructions of a network function service consumer, wherein the instructions when executed by the at least one processor, cause the apparatus to perform the method of any of claims 8 to 11.
14. A non-transitory computer-readable medium comprising instructions of a network function service consumer, wherein the instructions, when executed by the at least one processor of an apparatus, cause the apparatus to perform the method of any of claims 8 to 11.
15. A computer program comprising instructions of a network function service consumer, wherein when the program is executed by an apparatus, cause the apparatus to carry out the method of any of claims 8 to 11.
16. A method for a network function service consumer comprising: transmitting a subscription request for data, said subscription request including at least one shared-data set identifier corresponding to at least one shared-data set that is available to the network function service consumer, and receiving a message based on said subscription request, said message including information on at least one shared-data set that is not available to the network function service consumer and relating to said data.
17. The method according to claim 16, wherein said subscription request is indicative of an immediate reporting demand, and said message is a subscription acknowledgement including said at least one shared-data set not available to the network function service consumer and at least one shared-data set identifier corresponding to said at least one shared-data set that is not available to the network function service consumer.
18. The method according to claim 16 or 17, further comprising: establishing, based on said obtained data, a subscription for shared-data sets not available to the network function service consumer and relating to said data, said shared- data sets not available to the network function service consumer including said at least one shared-data set not available to the network function service consumer, and wherein said message is a notification including information on changes of said at least one shared-data set not available to the network function service consumer, and at least one shared-data set identifier corresponding to said at least one shared-data set that is not available to the network function service consumer.
19. An apparatus comprising network function service consumer configured to perform the method of any of claims 16 to 18.
20. An apparatus comprising: at least one processor; and at least one memory storing instructions of a network function service consumer, wherein the instructions when executed by the at least one processor, cause the apparatus to perform the method of any of claims 16 to 18.
21. A non-transitory computer-readable medium comprising instructions of a network function service consumer, wherein the instructions, when executed by the at least one processor of an apparatus, cause the apparatus to perform the method of any of claims 16 to 18.
22. A computer program comprising instructions of a network function service consumer, wherein when the program is executed by an apparatus, cause the apparatus to carry out the method of any of claims 16 to 18.
23. A method for a network entity comprising: receiving, from a network function service consumer, a subscription request for data, said subscription request including at least one shared-data set identifier corresponding to at least one shared-data set available to the network function service consumer, obtaining, as obtained data, said data from a data store, and transmitting a message based on said subscription request, said message including information on at least one shared-data set not available to the network function service consumer and relating to said data.
24. The method according to claim 23, further comprising analyzing said obtained data for whether said obtained data includes at least one shared-data set identifier corresponding to at least one shared-data set not available to the network function service consumer.
25. The method according to claim 23 or 24, wherein said subscription request is indicative of an immediate reporting demand, andsaid message is a subscription acknowledgement including said at least one shared-data set not available to the network function service consumer and at least one shared-data set identifier corresponding to said at least one shared-data set not available to the network function service consumer.
26. The method according to any of claims 23 to 25, further comprising establishing, based on said obtained data, a subscription for shared-data sets not available to the network function service consumer and relating to said data, said shared- data sets not available to the network function service consumer including said at least one shared-data set not available to the network function service consumer, wherein said message is a notification including information on changes of said at least one shared-data set not available to the network function service consumer, and at least one shared-data set identifier corresponding to said at least one shared-data set not available to the network function service consumer.
27. A network entity comprising means for performing the method of any of claims 23 to 26.
28. A network entity comprising: at least one processor; and at least one memory storing instructions which, when executed by the at least one processor, cause the network entity to perform the method of any of claims 23 to 26.
29. A non-transitory computer-readable medium comprising instructions which, when executed by the at least one processor of a network entity, cause the network entity to perform the method of any of claims 23 to 26.
30. A computer program comprising instructions which when the program is executed by a network entity, cause the network entity to carry out the method of any of claims 23 to
