Optimized conditional transactions with udr

By incorporating Etag values for sub-resources in UDR responses, the limitations of current conditional transactions are overcome, enhancing network efficiency and enabling efficient conditional transactions with UDR.

WO2024235751A1PCT designated stage expired Publication Date: 2024-11-21NOKIA TECHNOLOGIES OY
View PDF 2 Cites 0 Cited by

Patent Information

Application Number
PCT/EP2024/062593
Authority / Receiving Office
WO · WO
Patent Type
Applications
Current Assignee / Owner
Priority Date
2023-05-12
Filing Date
2024-05-07
Publication Date
2024-11-21

AI Technical Summary

Technical Problem

Current conditional transactions with Unified Data Repository (UDR) do not allow for the use of Etag values for subsequent conditional reads and updates of sub-resources, limiting network efficiency and requiring proprietary solutions.

Method used

Incorporating query parameters in requests to UDR to include Etag values for sub-resources in responses, enabling conditional reads and updates through headers like '3gpp-sbi-etags' or structured Etag headers, allowing efficient data retrieval and management.

Benefits of technology

Enhances network efficiency by enabling optimized conditional transactions with UDR, supporting efficient and flexible use of Etags for sub-resources, applicable across various service-based interfaces.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure EP2024062593_21112024_PF_FP_ABST
    Figure EP2024062593_21112024_PF_FP_ABST
Patent Text Reader

Abstract

Various examples of embodiments described herein relate to methods and apparatuses for optimized conditional transactions. One such example of an embodiment relates to a method that includes providing a request, the request including a query parameter indicating a sub-resource for which an entity-tag value is requested. The method also includes receiving a response based on the request, the response including an entity-tag value for the indicated sub-resource. The method further includes performing subsequent conditional read and / or update of the sub-resource based on the entity-tag value included in the response.
Need to check novelty before this filing date? Find Prior Art

Description

[0001] OPTIMIZED CONDITIONAL TRANSACTIONS WITH UDR

[0002] TECHNICAL FIELD

[0003] Various examples of embodiments described herein relate to a method and an apparatus for optimized conditional transactions (e.g., conditional transactions with improved efficiency) with a network entity or function (e.g., Unified Data Repository (UDR)).

[0004] BACKGROUND

[0005] Over time, an increasing extension of communication networks has taken place all over the world. Various organizations, such as the European Telecommunications Standards Institute (ETSI), the 3rdGeneration Partnership Project (3GPP), Telecoms & Internet converged Services & Protocols for Advanced Networks (TISPAN), the International Telecommunication Union (ITU), 3rdGeneration Partnership Project 2 (3GPP2), Internet Engineering Task Force (IETF), the IEEE (Institute of Electrical and Electronics Engineers), the WiMAX Forum and the like are working on standards or specifications for telecommunication networks and access environments.

[0006] By way of example, 3GPP defines 5G Core Network Function’s (NF’s) interfaces and relevant Application Programming Interfaces (APIs) for each NF to communicate between NFs.

[0007] SUMMARY

[0008] Various examples of embodiments described in the subject disclosure provide certain advantages, for example in the form of one or more improvements that are either explicitly described herein or otherwise apparent to a person skilled in the art from the subject disclosure. Hence, at least some examples of embodiments of the subject disclosure aim to provide (or otherwise contribute to) at least part of the aforementioned advantages and improvements. Various aspects of examples of embodiments of the subject disclosure are set forth in the claims and pertain to methods, apparatuses and computer program products in the context of conditional transactions with a network entity or function (e.g., UDR).

[0009] At least some of aforementioned advantages and improvements may be achieved through the methods, apparatuses and non-transitory storage media as specified in the claims. Further advantages and improvements may be achieved through the methods, apparatuses and non-transitory storage media set forth in respective dependent claims.

[0010] Insofar, according to various examples of embodiments, a method may comprise: providing a request, the request including a query parameter indicating a subresource for which an entity-tag value is requested; receiving a response based on the request, the response including an entity-tag value for the indicated sub-resource; and performing subsequent conditional read and / or update of the sub-resource based on the entity-tag value included in the response.

[0011] According to various examples of embodiments, the method may further comprise that the request may be an HTTP request and that the response may be an HTTP response.

[0012] According to various examples of embodiments, the method may further comprise that the request may be a GET request and that the response may be a GET response.

[0013] According to various examples of embodiments, the method may comprise that the providing may comprises including the query parameter in the request.

[0014] According to various examples of embodiments, the method may comprise that the providing may comprise providing the request for a resource, wherein the sub-resource for which the entity-tag value is requested is a sub-resource of the resource.

[0015] According to at least some examples of embodiments, a method may comprise: receiving a request, the request including a query parameter indicating a subresource for which an entity-tag value is requested; including an entity-tag value for the indicated sub-resource in a response; and providing the response. According to at least some examples of embodiments, the method may further comprise that the request may be an HTTP request and that the response may be an HTTP response.

[0016] According to at least some examples of embodiments, the method may further comprise that the request may be a GET request and that the response may be a GET response.

[0017] According to at least some examples of embodiments, the method may further comprise that the receiving may comprise receiving the request for a resource, wherein the subresource for which the entity-tag value is requested is a sub-resource of the resource.

[0018] According to at least some examples of embodiments, the method may further comprise that the including may comprise including a map in the response, where an identifier of a resource for which the request is received, the resource comprising the sub-resource, serves as key and where an entity-tag of the sub-resource serves as the entity-tag value.

[0019] According to at least some examples of embodiments, the method may further comprise that the including may comprise introducing and / or updating a header in the response to comprise the entity-tag value corresponding to the indicated sub-resource.

[0020] According to at least some examples of embodiments, the method may further comprise that the introduced and / or updated header may be in list form or in map form.

[0021] According to at least some examples of embodiments, the method may further comprise that the including may comprise including, in the response, an entity-tag value of each sub-resource in a corresponding resource for which the request is received.

[0022] According to at least some examples of embodiments, the method may further comprise that the providing may comprise providing a single entity-tag header with structured content comprising at least one member for each sub-resource in a corresponding resource for which the request is received. According to various examples of embodiments, an apparatus, comprising at least one processor; and at least one memory storing instructions that, when executed by the at least one processor, may cause the apparatus at least to: provide a request, the request including a query parameter indicating a subresource for which an entity-tag value is requested; receive a response based on the request, the response including an entity-tag value for the indicated sub-resource; and perform subsequent conditional read and / or update of the sub-resource based on the entity-tag value included in the response.

[0023] According to various examples of embodiments in relation to the apparatus, the request may be an HTTP request and the response may be an HTTP response.

[0024] According to various examples of embodiments in relation to the apparatus, the request may be a GET request, and the response may be a GET response.

[0025] According to various examples of embodiments, the apparatus may further be caused to provide the request may comprise to include the query parameter in the request.

[0026] According to various examples of embodiments, the apparatus may further be caused to provide the request may comprise to provide the request for a resource, wherein the subresource for which the entity-tag value is requested is a sub-resource of the resource.

[0027] According to at least some examples of embodiments, an apparatus, comprising at least one processor; and at least one memory storing instructions that, when executed by the at least one processor, may cause the apparatus at least to: receive a request, the request including a query parameter indicating a subresource for which an entity-tag value is requested; include an entity-tag value for the indicated sub-resource in a response; and provide the response.

[0028] According to at least some examples of embodiments in relation to the apparatus, the request may be an HTTP request and the response may be an HTTP response.

[0029] According to at least some examples of embodiments in relation to the apparatus, the request may be a GET request and the response may be a GET response. According to at least some examples of embodiments, the apparatus may further be caused to receive the request may comprise to receive the request for a resource, wherein the sub-resource for which the entity-tag value is requested is a sub-resource of the resource.

[0030] According to at least some examples of embodiments, the apparatus may further be caused to include the entity-tag value may comprise to include a map in the response, where an identifier of a resource for which the request is received, the resource comprising the sub-resource, serves as key and where an entity-tag of the sub-resource serves as the entity-tag value.

[0031] According to at least some examples of embodiments, the apparatus may further be caused to include the entity-tag value may comprise to introduce and / or update a header in the response to comprise the entity-tag value corresponding to the indicated subresource.

[0032] According to at least some examples of embodiments in relation to the apparatus, the introduced and / or updated header may be in list form or in map form.

[0033] According to at least some examples of embodiments, the apparatus may further be caused to include the entity-tag value may comprise to include, in the response, an entity-tag value of each sub-resource in a corresponding resource for which the request is received.

[0034] According to at least some examples of embodiments, the apparatus may further be caused to provide the entity-tag value may comprise to provide a single entity-tag header with structured content comprising at least one member for each sub-resource in a corresponding resource for which the request is received.

[0035] Any one of the aspects mentioned according to the claims facilitates conditional transactions with a network entity or function (e.g., UDR), thereby providing at least part of the aforementioned advantages and improvements. In more detail, the subject disclosure describes conditional transactions with a network entity or function (e.g., UDR), which may, according to some examples of embodiments, prove advantageous over a proprietary solution for at least the following reasons.

[0036] Examples of embodiments described in the subject disclosure may, for instance, realize an increased efficiency, and an extension of network efficiency, of the NLIDR interface in use cases where Etags for conditional reads and updates can be used. It is further noted that at least some of the solution options are also applicable (e.g., useable) with any other service-based interface that makes use of the Etag mechanism and conditional reads and updates.

[0037] Further advantages may become apparent to a person skilled in the art from the following detailed description.

[0038] BRIEF DESCRIPTION OF THE DRAWINGS

[0039] Some examples of embodiments of the subject disclosure are described below, by way of example only, with reference to the accompanying drawings, in which:

[0040] FIG. 1 shows a signaling diagram, illustrating limitations with certain Etag solutions;

[0041] FIG. 2 (including part 1 of 2 and part2 of 2) shows a signaling diagram, illustrating an example flow(s) according to various examples of embodiments of the subject disclosure;

[0042] FIG. 3 shows a flowchart illustrating steps corresponding to an example method according to various examples of embodiments of the subject disclosure;

[0043] FIG. 4 shows a flowchart illustrating steps corresponding to an example method according to various examples of embodiments of the subject disclosure; FIG. 5 shows a block diagram illustrating an example apparatus according to various examples of embodiments of the subject disclosure; and

[0044] FIG. 6 shows a block diagram illustrating an example apparatus according to various examples of embodiments of the subject disclosure.

[0045] DEATILED DESCRIPTION

[0046] In general, two or more end points involved in a communication therebetween may be implemented as a particular type of end point (e.g. a communication station or element or function, such as a terminal device, user equipment (UE), or other communication network element, a database, a server, host, etc.), or as one or more network elements or functions (e.g. virtualized network functions), such as communication network control elements or functions, for example access network elements like access points (APs), radio base stations (BSs), relay stations, eNBs, gNBs etc., and core network elements or functions, for example control nodes, support nodes, service nodes, gateways, user plane functions, access and mobility functions, etc.. These end points may belong to a single communication network system, different communication network systems, or a combination of at least one same communication network system and at least one different communication network system.

[0047] In the following, various examples of embodiments will be described using, as an example of a communication network to which examples of embodiments may be applied, a communication network architecture based on 3GPP standards for a communication network, such as a 5G / NR, without restricting the examples of embodiments to such an architecture. It, however, is obvious for a person skilled in the art that the examples of embodiments may also be applied to other kinds of communication networks like 4G and / or LTE (and even 6G and higher) where mobile communication principles are integrated, e.g. Wi-Fi, worldwide interoperability for microwave access (WiMAX), Bluetooth®, personal communications services (PCS), ZigBee®, wideband code division multiple access (WCDMA), systems using ultra- wideband (UWB) technology, mobile ad-hoc networks (MANETs), wired access, etc.. Furthermore, without loss of generality, the description of some examples of embodiments is related to a mobile communication network, but the subject disclosure can be extended and applied to any other type of communication network, such as a wired communication network or datacenter networking.

[0048] The following examples of embodiments are to be understood only as illustrative in nature. Although portions of the subject disclosure may refer to the expressions “an”, “one”, or “some” example(s) of embodiment(s) in several specific locations, this does not necessarily mean that each such reference is related to the same example(s) of embodiment(s), or that the described feature only applies to a single example of an embodiment. Individual features from different examples of embodiments may also be combined to provide other examples of embodiments. Furthermore, terms like “comprising” and “including” should be understood as not limiting the described examples of embodiments to consist of only those features that have been mentioned; such examples of embodiments can also contain features, structures, units, modules etc. that have not been specifically mentioned.

[0049] A simplified system architecture of a (tele)communication network including a mobile communication system, where some examples of embodiments, are applicable may include an architecture of one or more communication networks. The one or more communication networkes may include wireless access network subsystem(s) and core network(s). Such an architecture may include one or more communication network control elements or functions, access network elements, radio access network elements, access service network gateways or base transceiver stations, such as a base station (BS), an access point (AP), a NodeB (NB), an eNB or a gNB, a distributed ora centralized unit (CU), which controls a respective coverage area or cell(s) and with which one or more communication stations such as communication elements or functions, like user devices (e.g. customer devices), mobile devices, or terminal devices, like a UE, or another device having a similar function, such as a modem chipset, a chip, a module etc., which can also be part of a station, an element, a function or an application configured to conduct a communication, such as a UE, an element or function usable in a machine-to-machine communication architecture, or attached as a separate element to such an element, function or application capable of conducting a communication, or the like, are configured to communicate via one or more channels via one or more communication beams for transmitting several types of data in a plurality of access domains. Furthermore, (core) network elements or network functions ((core) network control elements or network functions, (core) network management elements or network functions), such as gateway network elements / functions, mobility management entities, a mobile switching center, servers, databases and the like may be included.

[0050] Functions and interconnections of the described elements and functions, which also depend on the actual network type, are apparent to those skilled in the art and may be described in corresponding specifications, so that a description thereof is omitted herein. However, it is to be noted that several additional network elements and signaling links may be employed for a communication to or from an element, function or application, like a communication endpoint, a communication network control element, such as a server, a gateway, a radio network controller, and other elements of the same or other communication networks besides those described in detail herein below.

[0051] It should be appreciated that according to some examples of embodiments, a so-called “liquid” or flexible network concept may be implemented where the operations and functionalities of a network element, a network function, or of another entity of the network, may be performed in different entities or functions, such as in a node, host or server, in a flexible manner. Thus, a “division of labor” between involved network elements, functions or entities may vary case by case.

[0052] The subject disclosure, in some examples of embodies, relates to optimized conditional transactions (e.g., conditional transactions with improved efficiency) over Network Unified Data Repository (NUDR) interface defined in TS 29.505. Although certain examples of embodiments described in the subject disclosure detail the NUDR service, the subject disclosure is generally applicabile to any or all service-based interfaces that make use of the entity-tag (Etag) mechanism and conditional reads and updates.

[0053] The Etag header in a GET response from Unified Data Repository (UDR) may be used to perform conditional read or update of the same resource using the If-None-Match or If-Match headers. However, with regard to the conditional read or update, there is room for improvement, where conditional transactions with UDR as disclosed herewith may provide such improvement. Therefore, various examples of embodiments described in the subject disclosure provide certain advantages, for example in the form of one or more improvements that are either explicitly described herein or those otherwise apparent to a person skilled in the art from the subject disclosure.

[0054] At least some example embodiments may pertain to an Etag header in a GET response from UDR as indicated above. In certain examples of embodiments, the Etag header may be used to perform conditional read or update of the same resource using the If- None-Match or If-Match headers.

[0055] UDR may be configured to support a GET of multiple sub-resources using a parent resource Uniform Resource Identifier (URI) for optimized data retrieval (e.g., efficient data retrieval). For example, GET context-data using context-dataset-names, GET all ee subscriptions, may be employed.

[0056] However, subsequent conditional reads or updates of sub-resources by NF consumers (NFC) is not possible as the Etag value returned in the GET response is not applicable to sub-resources.

[0057] In particular, with regard to FIG. 1 , in response to the NFC 110 providing, in S101 , a GET request, the UDR 120 provides, in S102, an Etag value to the NFC 110. As illustrated in FIG. 1 , such Etag value received by the NFC 110 may not be used in subsequent GET and / or modification requests for sub-resources.

[0058] Examples of embodiments described in the subject disclosure provide certain advantages, for example in the form of one or more improvements that are either explicitly described herein or otherwise apparent to a person skilled in the art from the subject disclosure, to address at least part of these drawbacks.

[0059] According to at least some examples of embodiments, NF consumers may optionally include a query parameter in the GET request indicating the sub-resources for which Etag values are requested, where the UDR may support including Etag values of sub- resources in the GET response to enable NF consumers to perform (e.g., requested) subsequent conditional read and / or update of sub-resources.

[0060] With continued reference to FIG. 2 (including part 1 of 2 and part 2 of 2; to be connected at A’ and A” as well as B’ and B”), FIG. 2 shows a signaling diagram according to various examples of embodiments of the subject disclosure. In particular, according to some examples of embodiments, several options are illustrated in FIG. 2, which may address at least part of the aforementioned drawbacks.

[0061] According to an example of an embodiment, herein referred to as Option 1 , the UDR 210, in its response to the NFC 220, is configured to include a map where the URI or other identifier of the resource serves as key and the Etag of the sub-resource serves as the value.

[0062] According to another example of an embodiment, herein referred to as Option 2, the UDR 210, in its response to the NFC 220, is configured to include a new header '3gpp- sbi-etags' that packs the requested sub-resources' Etag values.

[0063] According to a further example of an embodiment, herein referred to as Option 3, the UDR 210, in its response to the NFC 220, is configured to include an Etag value of each sub-resource in the corresponding resource’s object.

[0064] According to a yet further example of an embodiment, herein referred to as Option 4, the UDR 210, in its response to the NFC 220, is configured to provide a single Etag header with structured content, such as a JSON map with one member for each sub-resource. The structured content of the Etag in this particular option does not need to be understood by the consumer. A structured Etag can simply be used in an If-Match / lf- None-Match header in a subsequent conditional read / update request, because the server would understand the structure of the content and be able to extract the individual sub-resource’s Etag to compare to the current Etag.

[0065] A possible change to GET of context / provisioned data sets is highlighted in bold below within the following examples of embodiments. The specific changes to the responses section reflect changes for Option 1 as described above and implemented in the following example of an embodiment.

[0066] / subscription-data / {ueld} / {servingPlmnld} / provisioned-data: get: parameters:

[0067] - name: requested-etags: in: query description: List of sub-resources for which etag values are requested style: form explode: false required: false anyOf:

[0068] - type: string enum:

[0069] - NONE - ALL

[0070] - $ref: '# / components / schemas / ProvisionedDataSetName

[0071] - type: array items:

[0072] $ref:,TS29571_CommonData.yaml# / components / schemas / Uri' responses:

[0073] '200': description: Expected response to a valid request content: application / json: schema:

[0074] $ref: '# / components / schemas / ProvisionedDataSetsExt' default:

[0075] $ref: 'TS29571_CommonData.yaml# / components / responses / default'

[0076] / subscription-data / {ueld} / context-data: get: parameters:

[0077] - name: requested-etags: in: query description: List of sub-resources for which etag values are requested style: form explode: false anyOf:

[0078] - type: string enum:

[0079] - NONE - ALL

[0080] - $ref: '# / components / schemas / ContextDatasetNames' - type: array items:

[0081] $ref:,TS29571_CommonData.yaml# / components / schemas / Uri' responses:

[0082] '200': description: Expected response to a valid request content: application / json: schema:

[0083] $ref: '# / components / schemas / ContextDataSetsExt' default:

[0084] $ref: 'TS29571_CommonData.yaml# / components / responses / default'

[0085] ContextDataSetsExt: allOf:

[0086] - $ref: '# / components / schemas / ContextDataSets'

[0087] - $ref: '# / components / schemas / ResourcesEtag'

[0088] ProvisionedDataSetsExt: allOf:

[0089] - $ref: '# / components / schemas / ProvisionedDataSets'

[0090] - $ref: '# / components / schemas / ResourcesEtag'

[0091] Resources Etag: properties: etags: description: A map (list of key-value pairs where Uri or other identifier of the resource serves as key) of entity tags type: object additionalProperties: type: string minProperties: 1

[0092] For Option 2, as an alternate option, a new 3gpp header called '3gpp-sbi-etags' can be introduced that can be returned in the response, is reflected in the following example of an embodiment.

[0093] Simple list form (URI used as resource identifier, but resource name string could be used instead):

[0094] 3gpp-Sbi-Etags = "3gpp-Sbi-Etags" ":" OWS resourceEtag OWS resourceEtag) resourceEtag = resourcename "=" entity-tag resourcename = DQUOTE URI DQUOTE entity-tag as defined by RFC 7232 section 2.3 Map form (URI used as resource identifier, but resource name string could be used instead):

[0095] 3gpp-Sbi-Etags = "3gpp-Sbi-Etags" OWS etagJSONMap

[0096] The etagJSONMap shall be a JSON document containing a single map object complying to the following OpenAPI specification: etagJSONMap: description: A map (list of key-value pairs where Uri or other identifier of the resource serves as key) of entity tags type: object additionalProperties: type: string minProperties: 1

[0097] For Option 3, adding an Etag as an optional property to existing resources is reflected in the following example of an embodiment. For example:

[0098] Amf3GppAccessRegistration: type: object required:

[0099] - amflnstanceld

[0100] - deregCallbackllri

[0101] - guami

[0102] - ratType properties: amflnstanceld:

[0103] $ref: 'TS29571_CommonData.yaml# / components / schemas / Nflnstanceld' etag: type: string

[0104] For Option 4, the UDR 210 may be configured to provide a single Etag header with structured content, such as a JSON map with one member for each sub-resource, in the following example of an embodiment. The Etag header syntax remains the same (as defined by RFC 7232 section 2.3) and the Etagc part complies to the following OpenAPI specification: etagJSONMap: description: A map (list of key-value pairs where Uri or other identifier of the resource serves as key) of entity tags type: object additionalProperties: type: string minProperties: 1 In the following, further examples of embodiments are described in relation to the aforementioned methods and / or apparatuses.

[0105] Referring now to FIG. 3, there is shown a flowchart illustrating steps corresponding to an example method according to various examples of embodiments of the subject disclosure. Such method steps may correspond to at least part of such steps as outlined above with reference to Options 1 to 4 and FIG. 2.

[0106] In particular, according to FIG. 3, in S310, the method comprises providing a request (e.g., an HTTP request, a GET request, etc.), the request including a query parameter indicating a sub-resource for which an entity-tag value is requested.

[0107] Further, in S320, the method comprises receiving a response (e.g., an HTTP response, a GET response) based on the provided request, the response including an entity-tag value for the indicated sub-resource.

[0108] Additionally, in S330, the method comprises performing subsequent conditional read and / or update of the sub-resource based on the entity-tag value included in the received response.

[0109] It is noted that according to various examples of embodiments of the subject disclosure, the aforementioned method steps S310 to S330 may be applied at / via the NLIDR interface. Moreover, it is noted that the aforementioned method may be applied at a network entity or function, (e.g., NFC 220) as outlined-above with reference to Options 1 to 4 and FIG. 2. In addition, such network entity or function may provide the request to (and may receive the response from) another network entity or function, (e.g., UDR 210) as outlined-above with reference to Options 1 to 4 and FIG. 2.

[0110] Moreover, according to at least some examples of embodiments, the request may be an HTTP request and the response may be an HTTP response.

[0111] Furthermore, according to various examples of embodiments, the request may be a GET request and the response may be a GET response. Moreover, according to at least some examples of embodiments, the method may comprise that the providing comprises including the query parameter in the request.

[0112] Furthermore, according to various examples of embodiments, the method may comprise that the providing comprises providing the request for a resource, wherein the subresource for which the entity-tag value is requested is a sub-resource of the resource.

[0113] The aforementioned examples of embodiments may thus, for instance, realize an increased efficiency, by optimized (e.g. efficient) use of Etags for conditional reads and / or updates. Therefore, the aforementioned solution may provide certain advantages in that it enables for optimized (e.g., efficient and / or secure and / or robust and / or failure resistant and / or flexible) conditional transactions with a network entity or function (e.g., UDR).

[0114] Referring now to FIG. 4, FIG. 4 shows a flowchart illustrating steps corresponding to an example method according to various examples of embodiments of the subject disclosure. Such method steps may correspond to at least part of such steps as outlined above with reference to Options 1 to 4 and FIG. 2.

[0115] In particular, according to FIG. 4, in S410, the method comprises receiving a request (e.g., HTTP request, GET request, etc.), the request including a query parameter indicating a sub-resource for which an entity-tag value is requested.

[0116] Further, in S420, the method comprises including an entity-tag value for the indicated sub-resource in a response (e.g., HTTP response, GET response, etc.).

[0117] Additionally, in S430, the method comprises providing the response.

[0118] It is noted that according to various examples of embodiments of the subject disclosure, the aforementioned method steps S410 to S430 may be applied at / via the NLIDR interface. Moreover, it is noted that the aforementioned method may be applied at a network entity or function, (e.g., UDR 210) as outlined-above with reference to Options 1 to 4 and FIG. 2. In addition, such network entity or function may provide the response to (and may receive the request from) another network entity or function (e.g., NFC 220) as outlined-above with reference to Options 1 to 4 and FIG. 2.

[0119] Moreover, according to at least some examples of embodiments, the request may be an HTTP request and the response may be an HTTP response.

[0120] Furthermore, according to various examples of embodiments, the request may be a GET request and the response may be a GET response.

[0121] Moreover, according to at least some examples of embodiments, the method may further comprise that the receiving comprises receiving the request for a resource, wherein the sub-resource for which the entity-tag value is requested is a sub-resource of the resource.

[0122] Furthermore, according to various examples of embodiments, the method may further comprise that the including comprises including a map in the response, where an identifier of a resource for which the request is received, the resource comprising the sub-resource, serves as key and where an entity-tag of the sub-resource serves as the entity-tag value.

[0123] In addition, according to at least some examples of embodiments, the method may further comprise that the including comprises introducing and / or updating a header in the response to comprise the entity-tag value corresponding to the indicated subresource.

[0124] Optionally, according to various examples of embodiments, the method may further comprise that the introduced and / or updated header is in list form or in map form.

[0125] Further, according to at least some examples of embodiments, the method may further comprise that the including comprises including, in the response, an entity-tag value of each sub-resource in a corresponding resource for which the request is received.

[0126] Moreover, according to various examples of embodiments, the method may further comprise that the providing comprises providing a single entity-tag header with structured content comprising at least one member for each sub-resource in a corresponding resource for which the request is received.

[0127] The aforementioned examples of embodiments may thus, for instance, realize an increased efficiency, by optimized (e.g., efficient) use of Etags for conditional reads and / or updates. Therefore, the aforementioned solution may provide certain advantages in that it enables for optimized (e.g., efficient and / or secure and / or robust and / or failure resistant and / or flexible) conditional transactions with a network entity or function (e.g., UDR).

[0128] Referring now to FIG. 5, FIG. 5 shows a block diagram illustrating an example apparatus according to various examples of embodiments of the subject disclosure.

[0129] Specifically, FIG. 5 shows a block diagram illustrating an apparatus 500, which may represent a network entity or function, (e.g. NFC 220) as outlined above with reference to Options 1 to 4 and FIG. 2, according to various examples of embodiments, which may participate in conditional transactions with another network entity or function (e.g., UDR). Furthermore, even though reference is made to a network entity or function, the network entity or function may be also another device or function having a similar task, such as a chipset, a chip, a module, an application etc., which can also be part of a network element or attached as a separate element to a network element, or the like. It should be understood that each block and any combination thereof may be implemented by various means or their combinations, such as hardware, software, firmware, one or more processors and / or circuitry.

[0130] The apparatus 500 shown in FIG. 5 may include a processing circuitry, a processing function, a control unit or a processor 510, such as a CPU or the like, which is suitable to enable conditional transactions with a network entity or function (e.g., UDR). The processor 510 may include one or more processing portions or functions dedicated to specific processing as described below, or the processing may be run in a single processor or processing function. Portions for executing such specific processing may be also provided as discrete elements or within one or more further processors, processing functions or processing portions, such as in one physical processor like a CPU or in one or more physical or virtual entities, for example. Reference signs 531 and 532 denote input / output (I / O) units or functions (interfaces) connected to the processor or processing function 510. The I / O units 531 and 532 may be a combined unit including communication equipment towards several entities / elements, or may include a distributed structure with a plurality of different interfaces for different entities / elements. Reference sign 520 denotes a memory usable, for example, for storing data and programs to be executed by the processor or processing function 510 and / or as a working storage of the processor or processing function 510. It is to be noted that the memory 520 may be implemented by using one or more memory portions of the same or different type of memory, but may also represent an external memory, e.g. an external database provided on a cloud server.

[0131] The processor or processing function 510 is configured to execute processing related to the above described processing. In particular, the processor or processing circuitry or function 510 includes one or more of the following sub-portions. Sub-portion 511 is a providing portion, which is usable as a portion for providing a request (e.g., an HTTP request, a GET request, etc.). The portion 511 may be configured to perform processing according to S310 of FIG. 3. Further, sub-portion 512 is a receiving portion, which is usable as a portion for receiving a response (e.g., an HTTP response, a GET response, etc.). The portion 512 may be configured to perform processing according to S320 of FIG. 3. Moreover, sub-portion 513 is a performing portion, which is usable as a portion for performing subsequent conditional read and / or update of a sub-resource. The portion 513 may be configured to perform processing according to S330 of FIG. 3.

[0132] Referring now to FIG. 6, FIG. 6 shows a block diagram illustrating an example apparatus according to various examples of embodiments of the subject disclosure.

[0133] Specifically, FIG. 6 shows a block diagram illustrating an apparatus 600, which may represent a network entity or function, (e.g., UDR 210) as outlined above with reference to Options 1 to 4 and FIG. 2, according to various examples of embodiments, which may participate in conditional transactions with a network entity or function (e.g., UDR). Furthermore, even though reference is made to a network entity or function, the network entity or function may be also another device or function having a similar task, such as a chipset, a chip, a module, an application etc., which can also be part of a network element or attached as a separate element to a network element, or the like. It should be understood that each block and any combination thereof may be implemented by various means or their combinations, such as hardware, software, firmware, one or more processors and / or circuitry.

[0134] The apparatus 600 shown in FIG. 6 may include a processing circuitry, a processing function, a control unit or a processor 610, such as a CPU or the like, which is suitable to enable conditional transactions with a network entity or function (e.g., UDR). The processor 610 may include one or more processing portions or functions dedicated to specific processing as described below, or the processing may be run in a single processor or processing function. Portions for executing such specific processing may be also provided as discrete elements or within one or more further processors, processing functions or processing portions, such as in one physical processor like a CPU or in one or more physical or virtual entities, for example. Reference signs 631 and 632 denote input / output (I / O) units or functions (interfaces) connected to the processor or processing function 610. The I / O units 631 and 632 may be a combined unit including communication equipment towards several entities / elements, or may include a distributed structure with a plurality of different interfaces for different entities / elements. Reference sign 620 denotes a memory usable, for example, for storing data and programs to be executed by the processor or processing function 610 and / or as a working storage of the processor or processing function 610. It is to be noted that the memory 620 may be implemented by using one or more memory portions of the same or different type of memory, but may also represent an external memory, e.g. an external database provided on a cloud server.

[0135] The processor or processing function 610 is configured to execute processing related to the above described processing. In particular, the processor or processing circuitry or function 610 includes one or more of the following sub-portions. Sub-portion 611 is a receiving portion, which is usable as a portion for receiving a request (e.g., an HTTP request, a GET request, etc.). The portion 611 may be configured to perform processing according to S410 of FIG. 4. Further, sub-portion 612 is an including portion, which is usable as a portion for including an entity-tag, Etag, value in a response (e.g., an HTTP response, a GET response, etc.). The portion 612 may be configured to perform processing according to S420 of FIG. 4. Moreover, sub-portion 613 is a providing portion, which is usable as a portion for providing the response. The portion 613 may be configured to perform processing according to S430 of FIG. 4.

[0136] It shall be noted that the apparatuses 500 and 600 as outlined above with reference to FIGS. 5 and 6 may comprise further / additional sub-portions, which may allow the apparatuses 500 and 600 to perform such methods / method steps as outlined above with reference to FIGS. 2 to 4.

[0137] It should be appreciated that

[0138] - an access technology via which traffic is transferred to and from an entity in the communication network may be any suitable present or future technology, such as WLAN (Wireless Local Access Network), WiMAX (Worldwide Interoperability for Microwave Access), LTE, LTE-A, 5G, 6G, Bluetooth, Infrared, and the like may be used; additionally, examples of embodiments may also apply wired technologies, e.g. IP based access technologies like cable networks or fixed lines.

[0139] - examples of embodiments suitable to be implemented as software code or portions thereof and being run using a processor or processing function are software code independent and can be specified using any known or future developed programming language, such as a high-level programming language, such as objective-C, C, C++, C#, Java, Python, Javascript, other scripting languages etc., or a low-level programming language, such as a machine language, or an assembler.

[0140] - implementation of examples of embodiments is hardware independent and may be implemented using any known or future developed hardware technology or any hybrids of these, such as a microprocessor or CPU (Central Processing Unit), MOS (Metal Oxide Semiconductor), CMOS (Complementary MOS), BiMOS (Bipolar MOS), BiCMOS (Bipolar CMOS), ECL (Emitter Coupled Logic), and / or TTL (Transistor-Transistor Logic).

[0141] - examples of embodiments may be implemented as individual devices, apparatuses, units, means or functions, or in a distributed fashion, for example, one or more processors or processing functions may be used or shared in the processing, or one or more processing sections or processing portions may be used and shared in the processing, wherein one physical processor or more than one physical processor may be used for implementing one or more processing portions dedicated to specific processing as described, - an apparatus may be implemented by a semiconductor chip, a chipset, or a (hardware) module including such chip or chipset;

[0142] - examples of embodiments may also be implemented as any combination of hardware and software, such as ASIC (Application Specific IC (Integrated Circuit)) components, FPGA (Field-programmable Gate Arrays) or CPLD (Complex Programmable Logic Device) components or DSP (Digital Signal Processor) components.

[0143] - examples of embodiments may also be implemented as computer program products, including a computer usable medium having a computer readable program code embodied therein, the computer readable program code adapted to execute a process as described in embodiments, wherein the computer usable medium may be a non- transitory medium.

[0144] The term “circuitry” may refer to one or more or all of the following examples of embodiments:

[0145] (a) hardware-only circuit implementations (such as implementations in only analog and / or digital circuitry) and

[0146] (b) combinations of hardware circuits and software, such as (as applicable):

[0147] (i) a combination of analog and / or digital hardware circuit(s) with software / firmware and

[0148] (ii) any portions of hardware processor(s) with software (including digital signal processor(s)), software, and memory(ies) that work together to cause an apparatus, such as a mobile phone or server, to perform various functions) and hardware circuit(s) and or processor(s), such as a microprocessor(s) or a portion of a microprocessor(s), that requires software (e.g., firmware) for operation, but the software may not be present when it is not needed for operation.”

[0149] This definition of circuitry applies to all uses of this term herein, including in any claims. As a further example, as used herein, the term circuitry also covers an implementation of merely a hardware circuit or processor (or multiple processors) or portion of a hardware circuit or processor and its (or their) accompanying software and / or firmware. The term circuitry also covers, for example and if applicable to the particular claim element, a baseband integrated circuit or processor integrated circuit for a mobile device or a similar integrated circuit in server, a cellular network device, or other computing or network device. The term “non-transitory,” as used herein, is a limitation of the medium itself (e.g., tangible, not a signal ) as opposed to a limitation on data storage persistency (e.g., RAM vs. ROM).

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

[0151] Although the subject disclosure has been described herein before with reference to various examples of embodiments thereof, the subject disclosure is not limited thereto and it will be apparent to a person skilled in the art that various modifications can be made to the subject disclosure.

[0152] ABBREVIATIONS

[0153] The following meanings for the abbreviations used herein apply:

[0154] 3GPP 3rdGeneration Partnership Project

[0155] 3GGP2 3rdGeneration Partnership Project 2

[0156] 4G Fourth Generation

[0157] 5G Fifth Generation

[0158] 6G Sixth Generation

[0159] AP Access Point

[0160] API Application Programming Interface

[0161] BS Base Station

[0162] CDMA Code Division Multiple Access eNB Evolved Node B

[0163] Etag entity-tag

[0164] ETSI European Telecommunications Standards Institute gNB Next Generation Node B

[0165] IEEE Institute of Electrical and Electronics Engineers

[0166] ITU International Telecommunication Union

[0167] LTE Long Term Evolution LTE-A Long Term Evolution-Advanced

[0168] MANETs Mobile Ad-Hoc Networks

[0169] NB Node B

[0170] NF Network Function NFC Network Function Consumer

[0171] NLIDR Network Unified Data Repository

[0172] RAM Random Access Memory

[0173] RAN Radio Access Network

[0174] ROM Read Only Memory TISPAN Telecoms & Internet converged Services & Protocols for Advanced

[0175] Networks

[0176] UE User Equipment

[0177] UDM Unified Data Management Services

[0178] UDR Unified Data Repository UWB Ultra- Wideband

[0179] WCDMA Wideband Code Division Multiple Access

[0180] WiMAX Worldwide Interoperability for Microwave Access

[0181] WLAN Wireless Local Area Network

Claims

CLAIMS1. A method comprising, providing a request, the request including a query parameter indicating a subresource for which an entity-tag value is requested; receiving a response based on the request, the response including an entity-tag value for the indicated sub-resource; and performing subsequent conditional read and / or update of the sub-resource based on the entity-tag value included in the response.

2. The method according to claim 1 , wherein the request is an HTTP request and the response is an HTTP response.

3. The method according to claim 1 or 2, wherein the request is a GET request and the response is a GET response.

4. The method according to any of claims 1 to 3, wherein the providing comprises including the query parameter in the request.

5. The method according to any of claims 1 to 4, wherein the providing comprises providing the request for a resource, wherein the sub-resource for which the entity-tag value is requested is a sub-resource of the resource.

6. A method comprising, receiving a request, the request including a query parameter indicating a subresource for which an entity-tag value is requested; including an entity-tag value for the indicated sub-resource in a response; and providing the response.

7. The method according to claim 6, wherein the request is an HTTP request and the response is an HTTP response.

8. The method according to claim 6 or 7, wherein the request is a GET request and the response is a GET response.

9. The method according to any of claims 6 to 8, wherein the receiving comprises receiving the request for a resource, wherein the sub-resource for which the entity-tag value is requested is a sub-resource of the resource.

10. The method according to any of claims 6 to 9, wherein the including comprises including a map in the response, where an identifier of a resource for which the request is received, the resource comprising the sub-resource, serves as key and where an entity-tag of the sub-resource serves as the entity-tag value.11 . The method according to any of claims 6 to 9, wherein the including comprises introducing and / or updating a header in the response to comprise the entity-tag value corresponding to the indicated sub-resource.

12. The method according to claim 11 , wherein the introduced and / or updated header is in list form or in map form.

13. The method according to any of claims 6 to 9, wherein the including comprises including, in the response, an entity-tag value of each sub-resource in a corresponding resource for which the request is received.

14. The method according to any of claims 6 to 9, wherein the providing comprises providing a single entity-tag header with structured content comprising at least one member for each sub-resource in a corresponding resource for which the request is received.

15. An apparatus (500), comprising at least one processor; and at least one memory storing instructions that, when executed by the at least one processor, cause the apparatus at least to: provide a request, the request including a query parameter indicating a subresource for which an entity-tag value is requested;1 receive a response based on the request, the response including an entity-tag value for the indicated sub-resource; and perform subsequent conditional read and / or update of the sub-resource based on the entity-tag value included in the response.

16. The method according to claim 15, wherein the request is an HTTP request and the response is an HTTP response.

17. The apparatus according to claim 15 or 16, wherein the request is a GET request, and the response is a GET response.

18. The apparatus according to any of claims 15 to 17, wherein the apparatus is further caused to provide the request comprises to include the query parameter in the request.

19. The apparatus according to any of claims 15 to 18, wherein the apparatus is further caused to provide the request comprises to provide the request for a resource, wherein the sub-resource for which the entity-tag value is requested is a sub-resource of the resource.

20. An apparatus (600), comprising at least one processor; and at least one memory storing instructions that, when executed by the at least one processor, cause the apparatus at least to: receive a request, the request including a query parameter indicating a subresource for which an entity-tag value is requested; include an entity-tag value for the indicated sub-resource in a response; and provide the response.

21. The method according to claim 20, wherein the request is an HTTP request and the response is an HTTP response.

22. The apparatus according to claim 20 or 21 , wherein the request is a GET request and the response is a GET response.

23. The apparatus according to any of claims 20 to 22, wherein the apparatus is further caused to receive the request comprises to receive the request for a resource, wherein the sub-resource for which the entity-tag value is requested is a sub-resource of the resource.

24. The apparatus according to any of claims claim 20 to 23, wherein the apparatus is further caused to include the entity-tag value comprises to include a map in the response, where an identifier of a resource for which the request is received, the resource comprising the sub-resource, serves as key and where an entity-tag of the sub-resource serves as the entity-tag value.

25. The apparatus according to any of claims 20 to 23, wherein the apparatus is further caused to include the entity-tag value comprises to introduce and / or update a header in the response to comprise the entity-tag value corresponding to the indicated sub-resource.

26. The apparatus according to claim 25, wherein the introduced and / or updated header is in list form or in map form.

27. The apparatus according to any of claims 20 to 23, wherein the apparatus is further caused to include the entity-tag value comprises to include, in the response, an entity-tag value of each sub-resource in a corresponding resource for which the request is received.

28. The apparatus according to any of claims 20 to 23, wherein the apparatus is further caused to provide the entity-tag value comprises to provide a single entity-tag header with structured content comprising at least one member for each sub-resource in a corresponding resource for which the request is received.

29. A computer program product for a computer, including software code portions for performing the steps of any of claims 1 to 5, or any of claims 6 to 14, when said product is run on the computer.

30. The computer program product according to claim 29, wherein the computer program product includes a computer-readable medium on which said software code portions are stored, and / or the computer program product is directly loadable into the internal memory of the computer and / or transmittable via a network by means of at least one of upload, download and push procedures.

Citation Information

Patent Citations

  • Updating dynamic content in cached resources

    US20140280691A1

  • Web page displaying method, request processing method, apparatus and system

    WO2010081336A1