Patent Description:
Examples of mobile or wireless telecommunication systems may include the Universal Mobile Telecommunications System (UMTS) Terrestrial Radio Access Network (UTRAN), Long Term Evolution (LTE) Evolved UTRAN (E-UTRAN), LTE-Advanced (LTE-A), MulteFire, LTE-A Pro, and/or fifth generation (<NUM>) radio access technology or new radio (NR) access technology. <NUM> wireless systems refer to the next generation (NG) of radio systems and network architecture. A <NUM> system is mostly built on a <NUM> new radio (NR), but a <NUM> (or NG) network can also build on the E-UTRA radio. It is estimated that NR provides bitrates on the order of <NUM>-<NUM> Gbit/s or higher, and can support at least service categories such as enhanced mobile broadband (eMBB) and ultra-reliable low-latency-communication (URLLC) as well as massive machine type communication (mMTC). NR is expected to deliver extreme broadband and ultra-robust, low latency connectivity and massive networking to support the Internet of Things (IoT). With IoT and machine-to-machine (M2M) communication becoming more widespread, there will be a growing need for networks that meet the needs of lower power, low data rate, and long battery life. The next generation radio access network (NG-RAN) represents the RAN for <NUM>, which can provide both NR and LTE (and LTE-Advanced) radio accesses. It is noted that, in <NUM>, the nodes that can provide radio access functionality to a user equipment (i.e., similar to the Node B, NB, in UTRAN or the evolved NB, eNB, in LTE) may be named next-generation NB (gNB) when built on NR radio and may be named next-generation eNB (NG-eNB) when built on E-UTRA radio. 3GPP C4-<NUM> describes a technique involving applying multiple instances of shared resources to an individual resources according to a defined sequence.

It will be readily understood that the components of certain example embodiments, as generally described and illustrated in the figures herein, may be arranged and designed in a wide variety of different configurations. Thus, the following detailed description of some example embodiments of systems, methods, apparatuses, and computer program products for enhancing shared data in a communications system, is not intended to limit the scope of certain embodiments but is representative of selected example embodiments.

Additionally, if desired, the different functions or procedures discussed below may be performed in a different order and/or concurrently with each other. Furthermore, if desired, one or more of the described functions or procedures may be optional or may be combined. As such, the following description should be considered as illustrative of the principles and teachings of certain example embodiments, and not in limitation thereof.

In <NUM>, unified data management (UDM) manages network user data in a centralized element. UDM can be paired with a user data repository (UDR) that can store user information, such as customer subscription information, customer authentication information, and/or security credentials.

The shared data feature allows optimized handling of subscription data shared by multiple UEs. For example, the shared data feature may help to reduce subscriber profile size that is stored in the UDR by separating common data attributes from the individual subscriber profiles and store them in the shared profiles. <FIG> illustrates an example signaling flow diagram of subscription data management between a NF service consumer <NUM>, such as an access and mobility function (AMF) or session management function (SMF), and a NF service producer <NUM>, such as a UDM/UDR. In the example of <FIG>, the NF service consumer <NUM> may send a request for an individual subscriber resource towards the NF service producer <NUM>, and may receive the requested subscriber resource from the NF service producer <NUM>. The received individual subscriber resource may contain an indication indicating that, in addition to the individual subscriber resource, also a shared resource is applicable. If so, as also illustrated in the example of <FIG>, the NF service consumer <NUM> may also send a request for shared resource towards the NF service producer <NUM>, which stores the shared subscription data. The NF service consumer <NUM> may then receive the requested shared subscription data from the NF service producer <NUM>.

Currently, when shared data clash with individual data, it has been specified that individual data should take preference. For example, if both an individual subscriber data attribute and shared data attributes are configured in a resource, then precedence is given to the individual subscriber data. However, this predefined preference for individual data limits the flexibility that could be achieved by the shared data concept. There is no current mechanism available where a certain attribute from shared data can be selected even if the individual subscriber attribute is configured. To do so, the operator must delete the individual subscriber profile, which is a heavy provisioning operation. If, later, these values are required for individual subscriber profile, then those values would need to be provisioned again.

Another issue is that, if both the 'individual subscriber attribute in the resource' and the 'sharedData and corresponding attribute' are configured for a resource, then there is no framework available where, based on comparing the value of the both attributes, a final value can be selected. As one example, there is currently no mechanism for allowing the maximum value between the individual profile attribute and shared data attribute may be used, or the minimum value between the individual profile attribute and shared data attribute may be used. More generally, there is currently no method available to select the attribute from individual profile or shared profile dynamically without updating individual subscriber profiles. Example embodiments described herein provide solutions for at least these problems, as well as others.

As discussed below, example embodiments may be directed to extending the shared data feature by adding treatment instructions to the shared data indicating how the shared data attributes should be treated. The treatment instruction may, for example, indicate that individual data take precedence (e.g., as default) or that shared data take precedence. Therefore, certain embodioments, provide a method to enhance the shared profile/data with the additional capability to select an attribute from the individual profile or shared data, based on certain conditions defined in the shared data.

In general, the subscriber attribute may be configured in an individual profile, in a shared profile, or in both. However, there is currently no attribute level control in a shared profile to select which attribute is applicable. Therefore, certain example embodiments provide enhancements to the existing shared data to provide attribute level control in a shared profile in order to be able to select which attribute is applicable.

According to one example embodiment, an attribute that defines a treatment for one or more shared data attributes can be included in shared data. In certain example embodiments, when a subscriber profile attribute should be suppressed or precedence given to shared profile attribute, the treatment can be added in the shared profile for that attribute.

Additionally or alternatively, in an example embodiment, rather than having a new attribute specified for each attribute already defined, a single attribute (e.g., type map) can be added to a shared data record data structures that is a map of attribute as key and treatment value pairs.

<FIG> illustrates an example structure of a treatment attribute, according to one example embodiment. As illustrated in the example of <FIG>, a treatment indicating OVERWRITE" specifies to aggregate individual profile data with shared data so that the attribute of the individual profile is not used and so that the attribute of the shared data if present is used, "USE_IF_NO_CLASH" specifies to aggregate individual profile data with shared data so that the attribute of the individual data if present takes precedence, "MAX" specifies that the maximum value between the individual profile attribute and the shared data attribute is to be used, and "MIN" specifies that the minimum value between the individual profile attribute and the shared data attribute is to be used.

<FIG> illustrates one example applying an embodiment to an Access And Mobility Subscription Data resource and UE Ambr attribute. As illustrated in the example of <FIG>, the individual subscriber data <NUM> includes the AccessAndMobilitySubscriptionData resource with UeAmbr attribute indicating uplink of 20Mbps and downlink of 50Mbps. As also illustrated in the example of <FIG>, the shared data <NUM> includes UeAmbr attribute indicating uplink of 50Mbps and downlink of 100Mbps. However, the shared data <NUM> also includes an uplink treatment attribute indicating "OVERWRITE" and downlink treatment attribute indicating "OVERWRITE. " Hence, the treatment attributes in the shared data <NUM> indicate to update the individual subscriber data with the shared data attribute. In other words, in the example of <FIG>, the shared data attributes overwrite the corresponding data attributes in the individual subscriber data <NUM>. The example of <FIG> further illustrates the resulting aggregated data or final profile <NUM> showing that the UEAmbr attribute uses the uplink and downlink from the shared data <NUM>. It is noted that <FIG> depicts just one possible example for purposes of illustration, as example embodiments are not limited to this example.

<FIG> illustrates an example signaling flow diagram of subscription data management between a NF service consumer <NUM> and a NF service producer <NUM>, according to certain example embodiments. As mentioned above, the NF service consumer <NUM> may include an access and mobility function (AMF) and/or session management function (SMF), and the NF service producer <NUM> may include a UDM and/or UDR. In the example of <FIG>, the NF service consumer <NUM> may send a request for individual subscriber data (Get Subscriber Resource) towards the NF service producer <NUM>, and may receive the requested individual subscriber data from the NF service producer <NUM>. As also illustrated in the example of <FIG>, the NF service consumer <NUM> may also send a request for shared resource (Get Shared Resource) towards the NF service producer <NUM>, which stores the shared subscription data. The NF service producer <NUM> may then provide the requested shared subscription data to the NF service consumer <NUM>.

In an embodiment, the shared subscription data may include one or more treatment attributes that define or indicate whether a shared data attribute takes precendence over a subscriber resource attribute. According to one example embodiment, the service consumer <NUM> may then use the treatment attribute(s) to determine whether to apply the value provided in the shared data attribute or the value provided in the subscriber resource attribute. Therefore, as a result of the inclusion of the treatment attribute(s), the service consumer <NUM> knows how to consume the final aggregated data, without modifying individual subscriber data.

According to a further embodiment, the treatment attribute can also be the part of the individual subscriber data attribute level.

A treatment attribute can be included in the shared data and in the individual subscriber data. Such an embodiment may offer some additional flexibility, so that per-subscriber treatment can be used in conjunction with per shared data record treatment. When both are used, the precedence of or interactions between the treatments when there is a conflict between the treatment in subscriber data and shared data records can be defined. For example, it may be defined that the individual subscriber treatment takes precedence over the shared data treatment or vice versa.

<FIG> illustrates an example flow diagram of a method of subscription data management by enhancing shared data, according to one example embodiment. In certain example embodiments, the flow diagram of <FIG> may be performed by a network entity or network node in a communications system, such as LTE or <NUM> NR. In some example embodiments, the network entity performing the method of <FIG> may include a service consumer, such as an AMF or SMF, or the like. For instance, in one example embodiment, the method of <FIG> may be performed by an AMF or SMF, such as the AMF/SMF depicted in the example diagrams of <FIG> or <FIG>.

In an example embodiment, as illustrated in the example of <FIG>, a method may optionally include, at <NUM>, requesting individual subscriber data from a service producer and, at <NUM>, receiving or retrieving the individual subscriber data from the service producer. For example, in some embodiments, the service producer may include a UDM and/or UDR. According to certain example embodiments, the method may also include, at <NUM>, requesting shared data from the service producer and, at <NUM>, receiving or retrieving the shared data from the service producer. The shared data includes one or more treatment attributes configured to define or indicate a treatment of one or more attributes in the shared data with respect to one or more attributes in the individual subscriber data. As an example, the treatment attribute may be configured to indicate whether one or more attributes in the shared data should be applied or utilized over one or more attributes in the individual subscriber data. According to a further example embodiment, the individual subscriber data may additionally or alternatively include one or more treatment attributes configured to define or indicate a treatment of an attribute in the shared data over an attribute in the individual subscriber data. The treatment attribute(s) in the shared data and/or in the individual data indicates how a potential conflict between individual data and shared data should be treated, e.g. the treatment attribute may indicate the treatment of a potential conflict between individual data and shared data. The treatment attribute(s) may indicate whether a value provided by a shared data attribute takes precedence over a value provided by a corresponding individual subscriber data attribute that may conflict with the shared data attribute. According to an example embodiment, the method of <FIG> may include, at <NUM>, applying, based on the treatment attribute(s), a value provided in the shared data attribute or a value provided in the individual subscriber data attribute. This may be done in certain example embodiments by determining, using the treatment attribute, whether to apply a value provided in the shared data attribute or a value provided in the individual subscriber data attribute. In certain example embodiments, the method may also include aggregating data according to the determination of whether to apply the value provided in the shared data attribute or the value provided in the individual subscriber data attribute.

<FIG> illustrates an example flow diagram of a method of subscription data management by enhancing shared data, according to one example embodiment. In certain example embodiments, the flow diagram of <FIG> may be performed by a network entity or network node in a communications system, such as LTE or <NUM> NR. In some example embodiments, the network entity performing the method of <FIG> may include a service producer, such as an UDM or UDR, or the like. For instance, in one example embodiment, the method of <FIG> may be performed by a UDM or UDR, such as the UDM/UDR depicted in the example diagrams of <FIG> or <FIG>.

In an example embodiment, as illustrated in the example of <FIG>, a method may optionally include, at <NUM>, receiving a request for individual subscriber data from a service consumer and, at <NUM>, providing or transmitting the individual subscriber data to the service consumer. For example, in some embodiments, the service consumer may include an AMF and/or SMF. According to certain example embodiments, the method may also include, at <NUM>, receiving a request for shared data from the service consumer and, at <NUM>, providing or transmitting the shared data to the service consumer. The shared data includes one or more treatment attributes configured to define or indicate a treatment of one or more attributes in the shared data with respect to one or more attributes in the individual subscriber data. The individual subscriber data may additionally include one or more treatment attributes configured to define or indicate a treatment of an attribute in the shared data over an attribute in the individual subscriber data. The treatment attribute(s) may indicate whether a value provided by a shared data attribute takes precedence over a value provided by a corresponding individual subscriber data attribute that may conflict with the shared data attribute. The service consumer may then apply, based on the treatment attribute(s), a value provided in the shared data attribute or a value provided in the individual subscriber data attribute.

In some example embodiments, the shared data may include a treatment attribute provided for each attribute in the shared data. In a further example embodiment, the shared data may include a single treatment attribute as a map that includes, for example, key and treatment value pairs.

According to some example embodiments, the treatment attribute(s) may indicate to suppress the at least one individual subscriber data attribute in favor of the at least one shared data attribute, to overwrite the at least one individual subscriber data attribute with the at least one shared data attribute, to update the at least one individual subscriber data attribute with the at least one shared data attribute, to select a maximum value between the at least one individual subscriber data attribute and the at least one shared data attribute, and/or to select a minimum value between the at least one individual subscriber data attribute and the at least one shared data attribute.

In one example embodiment, when a plurality of shared data is configured, the treatment attribute(s) may be configured to be applied to all of the plurality of shared data. According to an example embodiment, a conflicting attribute in the individual subscriber data takes precedence over the attribute in the shared data unless the treatment attribute(s) indicate otherwise.

<FIG> illustrates an example of an apparatus <NUM> according to an example embodiment. In an example embodiment, apparatus <NUM> may be a node, host, or server in a communications network or serving such a network. For example, apparatus <NUM> may be a satellite, base station, a Node B, an evolved Node B (eNB), <NUM> Node B or access point, next generation Node B (NG-NB or gNB), and/or WLAN access point, associated with a radio access network, such as a LTE network, <NUM> or NR. In example embodiments, apparatus <NUM> may be NG-RAN node, an eNB in LTE, transmission/reception point (TRP) or gNB in <NUM>. According to some example embodiments, apparatus <NUM> may represent a service consumer, AMF, SMF, or the like.

While a single processor <NUM> is shown in <FIG>, multiple processors may be utilized according to other example embodiments. For example, it should be understood that, in certain example embodiments, apparatus <NUM> may include two or more processors that may form a multiprocessor system (e.g., in this case processor <NUM> may represent a multiprocessor) that may support multiprocessing. In certain example embodiments, the multiprocessor system may be tightly coupled or loosely coupled (e.g., to form a computer cluster).

In certain examples, processor <NUM> may be configured as a processing means or controlling means for executing any of the procedures described herein.

In certain example embodiments, memory <NUM> may be configured as a storing means for storing any information or instructions for execution as discussed elsewhere herein.

In an example embodiment, apparatus <NUM> may further include or be coupled to (internal or external) a drive or port that is configured to accept and read an external computer readable storage medium, such as an optical disc, USB drive, flash drive, or any other storage medium.

In some example embodiments, apparatus <NUM> may also include or be coupled to one or more antennas <NUM> for transmitting and receiving signals and/or data to and from apparatus <NUM>. Apparatus <NUM> may further include or be coupled to a transceiver <NUM> configured to transmit and receive information. The transceiver <NUM> may include, for example, a plurality of radio interfaces that may be coupled to the antenna(s) <NUM>. The radio interfaces may correspond to a plurality of radio access technologies including one or more of GSM, NB-IoT, LTE, <NUM>, WLAN, Bluetooth, BT-LE, NFC, radio frequency identifier (RFID), ultrawideband (UWB), MulteFire, and the like. The radio interface may include components, such as filters, converters (for example, digital-to-analog converters and the like), mappers, a Fast Fourier Transform (FFT) module, and the like, to generate symbols for a transmission via one or more downlinks and to receive symbols (for example, via an uplink).

In other example embodiments, transceiver <NUM> may be capable of transmitting and receiving signals or data directly. In certain example embodiments, transceiver <NUM> may be configured as a transceiving means for transmitting or receiving information as discussed elsewhere herein. Additionally or alternatively, in some example embodiments, apparatus <NUM> may include an input and/or output device (I/O device) or means.

In an example embodiment, memory <NUM> may store software modules that provide functionality when executed by processor <NUM>.

According to some example embodiments, processor <NUM> and memory <NUM> may be included in or may form a part of processing circuitry or control circuitry. In addition, in some example embodiments, transceiver <NUM> may be included in or may form a part of transceiver circuitry.

As introduced above, in certain example embodiments, apparatus <NUM> may be a network node or RAN node, such as service consumer, AMF, SMF, or the like. For example, in some example embodiments, apparatus <NUM> may be configured to perform one or more of the processes depicted in any of the flow charts or signaling diagrams described herein. For instance, apparatus <NUM> may be configured to perform any of the procedures executed by the AMF/SMF illustrated in <FIG> or <FIG>. Further, apparatus <NUM> may be configured to perform the process illustrated in the example flow diagram of <FIG>. In some example embodiments, as discussed herein, apparatus <NUM> may be configured to perform a procedure relating to subscription data management by enhancing shared data, for instance.

<FIG> illustrates an example of an apparatus <NUM> according to another example embodiment. In an example embodiment, apparatus <NUM> may be a satellite, base station, a Node B, an evolved Node B (eNB), <NUM> Node B or access point, next generation Node B (NG-NB or gNB), and/or WLAN access point, associated with a radio access network, such as a LTE network, <NUM> or NR. In example embodiments, apparatus <NUM> may be NG-RAN node, an eNB in LTE, or TRP or gNB in <NUM>. According to some further example embodiments, apparatus <NUM> may represent a service producer, UDM or UDR, or the like.

In some example embodiments, apparatus <NUM> may be configured to operate using one or more radio access technologies, such as GSM, LTE, LTE-A, NR, <NUM>, WLAN, WiFi, NB-IoT, Bluetooth, NFC, MulteFire, and/or any other radio access technologies.

While a single processor <NUM> is shown in <FIG>, multiple processors may be utilized according to other example embodiments. For example, it should be understood that, in certain example embodiments, apparatus <NUM> may include two or more processors that may form a multiprocessor system (e.g., in this case processor <NUM> may represent a multiprocessor) that may support multiprocessing. In certain example embodiments, the multiprocessor system may be tightly coupled or loosely coupled (e.g., to form a computer cluster).

In some example embodiments, apparatus <NUM> may also include or be coupled to one or more antennas <NUM> for receiving a downlink signal and for transmitting via an uplink from apparatus <NUM>.

In other example embodiments, transceiver <NUM> may be capable of transmitting and receiving signals or data directly. Additionally or alternatively, in some example embodiments, apparatus <NUM> may include an input and/or output device (I/O device). In certain example embodiments, apparatus <NUM> may further include a user interface, such as a graphical user interface or touchscreen.

In an example embodiment, memory <NUM> stores software modules that provide functionality when executed by processor <NUM>. According to an example embodiment, apparatus <NUM> may optionally be configured to communicate with apparatus <NUM> via a wireless or wired communications link or interface <NUM> according to any radio access technology, such as NR.

According to some example embodiments, processor <NUM> and memory <NUM> may be included in or may form a part of processing circuitry/means or control circuitry/means. In addition, in some embodiments, transceiver <NUM> may be included in or may form a part of transceiving circuitry or transceiving means.

As discussed above, according to some example embodiments, apparatus <NUM> may be network node, a service producer, UDM or UDR, or the like, for example. According to certain example embodiments, apparatus <NUM> may be controlled by memory <NUM> and processor <NUM> to perform the functions associated with example embodiments described herein. For example, in some example embodiments, apparatus <NUM> may be configured to perform one or more of the processes depicted in any of the flow charts or signaling diagrams described herein, such as those illustrated in <FIG>, <FIG> or <FIG>. For instance, in one example embodiment, apparatus <NUM> may represent the UDM/UDR illustrated in the examples of <FIG> or <FIG>. According to an example embodiment, apparatus <NUM> may be configured to perform a procedure relating to subscription data management by enhancing shared data, for instance.

Furthermore, it should be noted that an apparatus, according to certain example embodiments, may include means or functions for performing any of the procedures described herein.

Therefore, certain example embodiments provide several technological improvements, enhancements, and/or advantages over existing technological processes and constitute an improvement at least to the technological field of wireless network control and management. For example, as discussed in detail in the foregoing, certain example embodiments provide a process to select the attribute from an individual profile or shared profile dynamically, without the need to update individual subscriber profiles. Example embodiments therefore avoid the need to delete the individual subscriber profile, which is a substantial provisioning operation. Accordingly, the use of certain example embodiments results in improved functioning of communications networks and their nodes, such as base stations, eNBs, gNBs, and/or IoT devices, UEs or mobile stations.

In some example embodiments, the functionality of any of the methods, processes, signaling diagrams, algorithms or flow charts described herein may be implemented by software and/or computer program code or portions of code stored in memory or other computer readable or tangible media, and may be executed by a processor.

In some example embodiments, an apparatus may include or be associated with at least one software application, module, unit or entity configured as arithmetic operation(s), or as a program or portions of programs (including an added or updated software routine), which may be executed by at least one operation processor or controller. Programs, also called program products or computer programs, including software routines, applets and macros, may be stored in any apparatus-readable data storage medium and may include program instructions to perform particular tasks.

A computer program product may include one or more computer-executable components which, when the program is run, are configured to carry out some example embodiments. The one or more computer-executable components may be at least one software code or portions of code. Modifications and configurations required for implementing the functionality of an example embodiment may be performed as routine(s), which may be implemented as added or updated software routine(s). In one example, software routine(s) may be downloaded into the apparatus.

As an example, software or computer program code or portions of code may be in source code form, object code form, or in some intermediate form, and may be stored in some sort of carrier, distribution medium, or computer readable medium, which may be any entity or device capable of carrying the program. Such carriers may include a record medium, computer memory, read-only memory, photoelectrical and/or electrical carrier signal, telecommunications signal, and/or software distribution package, for example. The computer readable medium or computer readable storage medium may be a non-transitory medium.

In other example embodiments, the functionality of example embodiments may be performed by hardware or circuitry included in an apparatus, for example through the use of an application specific integrated circuit (ASIC), a programmable gate array (PGA), a field programmable gate array (FPGA), or any other combination of hardware and software. In yet another example embodiment, the functionality of example embodiments may be implemented as a signal, such as a non-tangible means, that can be carried by an electromagnetic signal downloaded from the Internet or other network.

Claim 1:
A method, comprising:
receiving or retrieving, at a service consumer (<NUM>, <NUM>), from a service producer (<NUM>, <NUM>) shared data (<NUM>) comprising at least one treatment attribute indicating how a potential conflict between individual subscriber data (<NUM>) and the shared data will be treated;
aggregating the shared data and the individual subscriber data according to a determination of whether to apply a value provided in the shared data or a value provided in the individual subscriber data based on the at least one treatment attribute.