Patent Description:
The core network of the future <NUM> communication system will adopt a service-oriented architecture. Under the service-oriented architecture, network function entities interact with each other through service-oriented interfaces, and the service-oriented interfaces have been explicitly defined to call data using the HTTP/<NUM>+TCP protocol.

The servicing interface in the related technology transmits data at a granularity of resources, and a service request initiated by the service consumer to the service provider through the servicing interface can only read one resource. Different from communication systems in related art, <NUM> communication systems will have diversified service requests, and each service request requires a different combination of data. If the service consumer requests multiple data at the same time, there are three data acquisition solutions based on the service interface in related art:.

<NUM>) The service provider defines all data in a resource. After the service consumer initiates a service request, the service provider sends the entire resource to the service consumer. The disadvantage of this solution is that the service provider can only send the full amount of data of the resource to the service consumer. If the service consumer only expects to acquire a part of the data in the resource, it will also obtain some useless data at the same time, so the utilization ratio of the transmission resource is low.

<NUM>) The service provider defines a resource for each data combination, and the service provider only needs to provide the service consumer with the resource corresponding to the desired data. The disadvantage of this solution is that it requires a lot of resources to support the combination of different data, the same data will be stored by multiple resources at the same time, and the utilization ratio of the storage resource of service provider is not high.

<NUM>) The service provider defines a resource for each data, and the service consumer provides the resource corresponding to the desired data. The disadvantage of this solution is that when the service consumer wants to acquire multiple data, it needs to initiate multiple service requests to the service provider, so the acquisition efficiency is low and the overhead is large, the association relationship of the storage space or data and resources is more complicated.

It can be seen that the data acquisition method of the service-oriented interface in the related art cannot be flexibly applied to different service requests, so it needs to be re-standardized. Document "<CIT>" discussed a method includes storing a user attribute, a resource attribute of a resource of a web service, one or more scope conditions for applying one of attributes in generating a decision of whether to permit an action, and a script comprising an access control policy comprising one or more policy conditions to be satisfied in order to permit an action. Document "<CIT>" discussed a resource acquisition method and relevant equipment, and aims to effectively reduce transmission of redundant data between a registrar common service entity and a hosting common service entity. The method in the embodiment of the invention comprises the following steps that: the registrar common service entity receives a first request for acquiring a target attribute included in resources sent by a terminal, wherein the first request carries a uniform resource identifier (URI) of the target attribute; the registrar common service entity determines that the resources to which the target attribute belongs are stored in the registrar common service entity according to the URI, wherein the target attribute is a part of content included in the resources; and the registrar common service entity transmits a valid target attribute indicated by the URI to the terminal.

The scope of the present invention is determined only by the scope of the appended claims. More precisely, in a first aspect, the present invention provides a data acquisition method according to claim <NUM> and further detailed in the dependent claims referring back to this claim. A corresponding service provider network function entity is provided in claim <NUM>.

In a second aspect, the present invention provides a data acquisition method according to claim <NUM> and further detailed in the dependent claims referring back to this claim. A corresponding service consumer network function entity is provided in claim <NUM>.

In order to make the technical issues to be solved, technical solutions and features clearer, the present disclosure will be described in detail with reference to the drawings and embodiments. In the following description, specific details such as specific configurations and components are provided only to help a comprehensive understanding of the embodiments of the present disclosure. Therefore, it should be clear to those skilled in the art that various changes and modifications can be made to the embodiments described herein without departing from the scope of the present disclosure. In addition, for clarity and conciseness, descriptions of known functions and configurations are omitted.

It should be understood that "one embodiment" or "an embodiment" mentioned throughout the specification means that a specific feature, structure, or characteristic related to the embodiment is included in at least one embodiment of the present disclosure. Therefore, "in one embodiment" or "in an embodiment" in various places throughout the specification do not necessarily refer to the same embodiment. In addition, these specific features, structures or characteristics can be combined in one or more embodiments in any suitable manner.

In the various embodiments of the present disclosure, it should be understood that the size of the sequence number of the following processes does not mean the order of execution. The execution order of each process should be determined by its function and internal logic, and should not be implemented in the present disclosure. The implementation process of the example constitutes any limitation.

The objective of the present disclosure is to solve the technical issues in the related art that the data acquisition method of the service-oriented interface in the related art cannot be flexibly applied to different service requests, the data acquisition method of the service-oriented interface is re-standardized.

On the one hand, data acquisition method is provided in an embodiment of the present disclosure, which is applied to a service provider (the service provider may be the network function entity hereinabove). As shown in <FIG>, the data acquisition method includes:.

Step <NUM>: receiving a service request message initiated by a service consumer for acquiring a resource attribute of a resource, where the service request message carries query information configured to indicate the resource attribute.

Specifically, the above-mentioned resource attribute may include one or more resource attributes, may be a part of the parameters in the resource, or may be all the parameters in the resource.

Step <NUM>: sending data of the resource attribute to the service consumer through a service response message.

Specifically, in this step, the service provider may determine the resource attributes that the service consumer expects to acquire from the above resources, according to the query information carried in the service request message, instead of determining, through the service request message, the resource that the service consumer expects to acquire as in the related art.

It can be seen that, a mapping for the data in the resource is configured according to the resource attribute. The service consumer specifies the specific data to be acquired to the service provider through improved query information, so that the service provider effectively provides the corresponding data instead of the full data of the entire resource, so the service interface realizes a more flexible data interaction.

Based on the embodiment of the present disclosure, for the service provider, resources can be defined for different service requests. Therefore, compared with the technical solution in related art, it has the following characteristics:.

The data acquisition method in the embodiment of the present disclosure will be described in detail below.

Exemplarily, in this embodiment, the data of the resource may be configured with a corresponding code according to the resource attribute, and the above query information may be the code of the resource attribute.

The resource attribute code of all data in the resource may be a sequential code, or a combination of characters without sequence, or a code generated by a code technique in any related art.

When the service consumer requests to acquire at least two resource attributes, the service request message carries a set of codes of resource attributes.

For example, there are four resource attributes requested by the service consumer, and the corresponding codes are <NUM>, <NUM>, <NUM>, and <NUM>, and the set of codes carried in the service request message is (<NUM>, <NUM>, <NUM>, <NUM>).

Optionally, if the resource attribute requested by the service consumer corresponds to a continuous code, the continuous code can also be expressed by a range in the set.

For example, when the resource attributes requested by the service consumer are four, and the corresponding codes are <NUM>, <NUM>, <NUM>, and <NUM>, then the service request message carries the code set as (<NUM>, <NUM>-<NUM>), and the <NUM>-<NUM> in the set represents resource attributes <NUM>, <NUM>, <NUM>.

Of course, when the resource attribute codes in the above resources are represented by letters, the set of codes carried in the service request message is (A, D-F), then D-F represents resource attributes D, E, and F.

When the resource attribute code in the above resource is represented by any code, the set of codes carried in the service request message is (code <NUM>, code <NUM>, code <NUM>). Regarding the data in the structured resource, this embodiment may use multi-level code to represent the resource attributes of the sub-resources contained in the resource. That is, the code of the resource attribute of the sub-resource of the resource is composed of at least a first-level subcode and a second-level subcode.

For example, the code of the resource attribute of the data in the structured resource may be <NUM>, <NUM>, <NUM>, and so on, where one digit before the decimal point and one digit after the decimal point are the first-level subcode and the second-level subcode respectively.

The code of the resource attribute of the data in the structured resource can also be expressed in the same general form, for example, the Mth resource attribute (sub-resource) code of the resource/the Nth resource attribute (sub-resource) code of the resource /. / the Fth resource attribute (sub-resource) code of the resource.

For example, the data of the <NUM> communication system in the related technology may be divided into different resources such as subscription data, service data, policy data, consumer context data, identification data, and code number data.

Based on the multi-level code, different types of data such as subscription data, service data, and policy data may be defined in a consumer's network data resources. The subscription data, service data, and policy data are taken as sub-resource data. The resource attributes of different data of the subscription data sub-resource is represented by <NUM>. X, the resource attributes of different data of the service data sub-resource is represented by <NUM>. X, and the resource attributes of different data of the policy data sub-resource is represented by <NUM>. X, and the representation form of the resource attributes of different data of sub-resources in other resources (such as user context data, identification data, number data) can be done in the same manner.

Alternatively, the resource attributes of different data of the subscription data sub-resource is represented by subscription data sub-resource code/resource attribute code, the resource attributes of different data of the service data sub-resource is represented by service data sub-resource code/resource attribute code, and the resource attributes of different data of the policy data sub-resource is represented by policy data sub-resource code/resource attribute code, and the rest can be done in the same manner.

" or "/" in the multi-level code represent a connector between different levels of in the code, and any connector can be used.

Obviously based on the above-mentioned multi-level code, the service provider may define all data in the same resource for service requests, and each data may be accurately represented through the multi-level code.

In addition, in practical applications, the service response message fed back to the service consumer in this embodiment further carries a code associated with data of the resource attribute.

For example, it is assumed that the data in a resource acquired by the service consumer includes resource attribute <NUM>, resource attribute <NUM>, and resource attribute <NUM>, and the corresponding codes are code <NUM>, code <NUM>, and code <NUM>.

According to code <NUM>, code <NUM>, and code <NUM>, the service provider determines from the resource that the data of resource attribute <NUM>, resource attribute <NUM>, and resource attribute <NUM> are Data1, Data1, and Data3.

After that, the service response message fed back by the service provider to the service consumer may include: Data1-encode1, Data2-encode2, and Data3-encode3.

After receiving the service response message, the service consumer may identify each data in the resource according to the code. For example, according to the code <NUM> in Data1-code <NUM>, it can be identified that Data1 corresponds to the data of resource attribute <NUM>; according to the code <NUM> in Data2-code <NUM>, it can be recognized that Data2 corresponds to the data of resource attribute <NUM>.

Specifically, the service request message in the embodiment of the present disclosure may be sent according to a GET sending mode in a Hypertext Transfer Protocol, and the code or the set of codes of the resource attribute is represented by a content of a query parameter in the GET mode.

For example: query_parameter1 is used to represent the query parameter, and the value of the query parameter query_parameter1 in the GET method is used to specify the code of the resource attribute to be obtained. Assuming that there are three resource attributes to be obtained, the corresponding codes are code <NUM>, code <NUM>, and code <NUM>, the service request message may carry query parameters as: query_parameter1=(code <NUM>, code <NUM>, code <NUM>). Assuming that there are three resource attributes to be obtained, the corresponding codes are code <NUM>, code <NUM>, and code <NUM>, the service request message may carry query parameters as follows: query_parameter1= (code <NUM>, code <NUM>, code <NUM>) or query_parameter1= (code <NUM> -<NUM>).

In the above embodiment, query_parameter1 is used to represent the query parameter, and the query parameter may also be represented by other characters (for example, English, numbers, and/or symbols, etc.).

The service provider may determine the resource attribute data that the service consumer expects to acquire through the value of query_parameter1 in the service request message.

Of course, the foregoing encode as query information is only a feasible solution in the specific embodiment of the present disclosure. As other solutions, the specific embodiment of the present disclosure may also use other methods to represent the parameters in the resource.

On the other hand, data acquisition method applied to a service consumer is further provided in another embodiment of the present disclosure. As shown in <FIG>, the data acquisition method includes:.

According to method of in the embodiment, a mapping for the data in the resource is configured according to the resource attribute. The service consumer specifies the data to be obtained to the service provider, through the query information in the service request message, so that the service provider may effectively provide corresponding data. Obviously, such data acquisition method is more flexible.

Based on the method in the embodiment of the present disclosure, when the service consumer expects to acquire the data of a certain resource attribute in a certain resource, the query information of the resource attribute will be carried in the service request message of the resource to inform the service provider. According to the query information in the service request message, the service provider may directly feedback the data of the corresponding parameter in the resource to the service consumer. It can be seen that, according to the data acquisition method in the embodiment, the service consumer may directly acquire the data in the desired resource, so this data acquisition method is more flexible.

The data acquisition method of the embodiment of the present disclosure will be described in detail below.

For example, the data of the resource in the embodiment is configured with a corresponding code according to the resource attribute, and the above query information may be the code of the resource attribute.

When there are at least two resource attributes, the service consumer may carry a set of codes of resource attributes in the service request message.

For example: there are four resource attributes, and the corresponding codes are <NUM>, <NUM>, <NUM>, <NUM>, and the service consumer can carry the set of codes (<NUM>, <NUM>, <NUM>, <NUM>) in the service request message to inform the service provider.

Optionally, if the resource attribute corresponds to a continuous code, the continuous code may also be represented by a range in the set.

For example, when the code of the resource attribute is <NUM>, <NUM>, <NUM>, <NUM>, then the set of codes carried in the service request message is (<NUM>, <NUM>-<NUM>), the <NUM>-<NUM> in this set represent resource attributes <NUM>, <NUM>, and <NUM>.

In addition, in practical applications, the service response message fed back to the service consumer in this embodiment also carries: a code associated with data of the resource attribute.

For example, it is assumed that the resource attributes in a resource obtained by the service consumer include resource attribute <NUM>, resource attribute <NUM>, and resource attribute <NUM>, and the corresponding codes are code <NUM>, code <NUM>, and code <NUM>.

According to code <NUM>, code <NUM>, and code <NUM>, the service provider determines from the resource that the data of resource attribute <NUM>, resource attribute <NUM>, and resource attribute <NUM> are Data1, Data1, and Data3. After that, the service provider feeds back a service response message to the service consumer, and the service response message may include: Data1-Code1, Data2-Code2, and Data3-Code2.

After receiving the service response message, the service consumer may identify each data according to the code. For example, according to the code <NUM> in Data1-Code <NUM>, it can be recognized that Data1 is the data of resource attribute <NUM>; according to the code <NUM> in Data2-Code <NUM>, it can be recognized that Data2 is the data of resource attribute <NUM>.

Specifically, when step <NUM> is performed, the service request message for the resource may be sent to the service provider the service request message is sent according to a GET sending mode in a Hypertext Transfer Protocol, and the code or the set of codes of the resource attribute is represented by a content of a query parameter in the GET mode.

For example: query_parameter1 is used to represent the query parameter, and the value of the query parameter query_parameter1 in the GET method is used to specify the code of the resource attribute to be obtained. Assuming that there are three resource attributes to be obtained, the corresponding codes are code <NUM>, code <NUM>, and code <NUM>, the service request message may carry query parameters as: query_parameter1=(code <NUM>, code <NUM>, code <NUM>). Assuming that there are three resource attributes to be obtained, the corresponding codes are code <NUM>, code <NUM>, and code <NUM>, the service request message may carry query parameters as: query_parameter1= (code <NUM>, code <NUM>, code <NUM>) or query_parameter1= (code <NUM> -<NUM>).

For example, when the data in the resources of this embodiment is divided into resource attributes with multiple structures, this embodiment may use multi-level code to represent the resource attributes of the sub-resources contained in the resources. That is, the code of the resource attribute of the sub-resource of the resource is composed of at least a first-level subcode and a second-level subcode.

For example, the code of the resource attribute of the data in the structured resource may be <NUM>, <NUM>, <NUM>, and so on.

One digit before the decimal point and one digit after the decimal point are the first-level subcode and the second-level subcode respectively. The multi-code manner may further divide the data in the resource according to the resource attribute.

Based on the multi-level code, different types of data such as subscription data, service data, and policy data may be defined in a consumer's network data resources. The subscription data, service data, and policy data are taken as sub-resource data. The resource attributes of different data of the subscription data sub-resource is represented by <NUM>. X, the resource attributes of different data of the service data sub-resource is represented by <NUM>. X, and the resource attributes of different data of the policy data sub-resource is represented by <NUM>. X, and the representation form of the resource attributes of different data of sub-resources in other resources (such as consumer context data, identification data, code number data) can be done in the same manner.

" or "/" in the multi-level code represent a connector between different levels of in the code, and any connector can be used.

Further, the subscription data may be further divided into: the first type of service subscription data, the second type of service subscription data,. , and the Nth type of service subscription data.

Correspondingly, in this embodiment, the code of the first type of service subscription data is <NUM> whish is used to represent the data in the first type of service subscription data; similarly, the code of the Nth type of service subscription is <NUM>. N which is used to represent data in the Nth type of service subscription data.

Obviously, based on the above-mentioned multi-level code, the service provider may define all data in the same resource for service requests, and each data may be accurately expressed through multi-level code. It should be noted that, for more levels of code representation, since the principle is the same, that will not be repeated with examples.

In the following, the data acquisition method of the present disclosure will be introduced in detail in different embodiments in conjunction with the service provider and the service consumer.

As the <NUM> communication system has clarify that the service-oriented interface uses the HTTP/<NUM>+TCP protocol to call data, in this embodiment, the service consumer requests acquiring the data in the resource from the service provider, through the GET sending mode in the HTTP protocol.

For example, the model structure of the resources at the service provider side is shown in <FIG>.

Resource represents a resource, and it can be seen from <FIG> that the data in the resource is divided into n resource attributes, and each resource attribute is configured with a code (<NUM>, <NUM>,.

Take the resource attribute with code <NUM> as an example, its data is Attr#<NUM>=value#<NUM>, and similarly the data of the resource attribute with code <NUM> is Attr#<NUM>=value#<NUM>,. , the data of the resource attribute with code n is Attr#n=value#n.

Assuming that the service consumer is to acquire the parameters of the resource with the resource attribute code=<NUM>, <NUM>, <NUM>, the corresponding process is shown in <FIG>.

The service consumer may expand the representation of the query parameter in the GET (acquisition) method in the service request message, specify the resource by query_parameter1 (query_parameter1) = value (value), and request the service provider for the resource attributes <NUM>, <NUM>, and <NUM> of the resource by carrying the resource attribute code set. The service provider, through the 200OK message in the service response message, provides the service consumer with the value of the resource attributes <NUM>, <NUM>, and <NUM> in the resource (<NUM>: value, <NUM>: value, <NUM>: value).

Alternatively, as shown in <FIG>, the service consumer may expand the representation of the GET method in the service request message and introduce the parameter range. The resource is specified through query_parameter1=value, and the resource attribute <NUM>, <NUM>, and <NUM> of the resource is requested from the service provider by carrying the resource attribute code range. The service provider, through the 200OK message in the service response message, provides the service consumer with the value of the resource attributes <NUM>, <NUM>, and <NUM> in the resource (<NUM>: value, <NUM>: value, <NUM>: value).

The above is an introduction to the data acquisition method of the present disclosure. It should be noted that the foregoing implementation manners are only used as examples, and cannot limit the protection scope of the present disclosure. Reasonable changes can be made without departing from the principles of the present disclosure. For example, there may be multiple resource attributes in the above practical application, and the query information may also be replaced by other methods, for example, the name of the resource attribute is directly used as the query information.

In addition, a service provider is further provided in another embodiment of the present disclosure, as shown in <FIG>, the service provider includes:.

Obviously, the service provider of the embodiment of the present disclosure is the executive body of the data acquisition method applied to the service provider in the present disclosure. Therefore, the technical effect that the data acquisition method can achieve can also be achieved by the service provider of this embodiment.

Optionally, the data of the resource is configured with a corresponding code according to the resource attribute, and the query information is a code of the resource attribute.

Optionally, the service response message further carries a code associated with the data of the resource attribute.

Optionally, in the case that there are at least two resource attributes, the service request message carries a set of codes of the resource attributes.

Optionally, in the case that there are a plurality of resource attributes and the resource attributes correspond to continuous codes, the continuous codes are represented by a range in the set.

Optionally, the service request message is sent according to a GET sending mode in a Hypertext Transfer Protocol, and the code or the set of codes of the resource attribute is represented by a content of a query parameter in the GET mode.

Optionally, the code of the resource attribute is a one-level code or a multi-level code, and the multi-level code includes at least a first-level subcode and a second-level subcode.

In addition, a service consumer is further provided in another embodiment of the present disclosure, as shown in <FIG>, the service consumer includes:.

Obviously, the service consumer of the embodiment of the present disclosure is the executive body of the data acquisition method applied to the service consumer in the present disclosure. Therefore, the technical effect that the data acquisition method can achieve can also be achieved by the service consumer of this embodiment.

In addition, as shown in <FIG>, a network function entity <NUM> is further provided in another embodiment of the present disclosure, including:
an antenna <NUM>, a radio frequency device <NUM>, a baseband device <NUM>, a processor <NUM>, a memory <NUM>, a user interface <NUM>, and a bus interface.

In the embodiment of the present disclosure, the network side device (i.e., the network function entity) <NUM> may serve as a service consumer or a service provider.

The network side device <NUM> also includes: a computer program stored in the memory <NUM> and executable on the processor <NUM>.

When the network side device <NUM> serves as a service provider, the processor executes the computer program to:.

When the network side device <NUM> serves as a service consumer, the processor executes the computer program to:.

The bus interface may include any number of interconnected buses and bridges. Specifically, one or more processors represented by the processors and various circuits of the memory represented by the memory <NUM> are linked together. The bus architecture can also link various other circuits such as peripherals, voltage regulators, power management circuits, etc., which are all known in the art, and therefore, no further description will be given herein. The bus interface provides the interface. The antenna <NUM>, the radio frequency device <NUM>, and the baseband device <NUM> together form a transmitter and a receiver, and provide a unit for communicating with various other devices on the transmission medium. For different consumer equipment, the consumer interface <NUM> may also be an interface capable of connecting externally and internally with the required equipment. The connected equipment includes but not limited to a keypad, a display, a speaker, a microphone, a joystick, etc..

The processor <NUM> is responsible for managing the bus interface and general processing, and the memory <NUM> can store data used by the processor <NUM> when performing operations.

Optionally, when the network side device <NUM> serves as a service consumer, the processor <NUM> executes the computer program to:
send the service request message to the service provider according to a GET sending mode in a Hypertext Transfer Protocol, where the code or the set of codes of the resource attribute is represented by a content of a query parameter in the GET mode.

In addition, a computer-readable storage medium is further provide din another embodiment of the present disclosure, where a computer program is stored therein, and a processor executes the computer program to:.

Claim 1:
A data acquisition method, performed by a service provider network function entity, comprising:
receiving (<NUM>) a service request message initiated by a service consumer for acquiring a resource attribute of a resource, wherein the service request message carries query information configured to indicate the resource attribute; and
sending (<NUM>) data of the resource attribute to the service consumer through a service response message;
wherein the data of the resource is configured with a corresponding code according to the resource attribute, and the query information is a code of the resource attribute;
characterized in that in the case that there are at least two resource attributes, the service request message carries a set of codes of the resource attributes;
a multi-level code of the resource attribute comprises at least a first-level subcode and a second-level subcode, wherein the multi-level code is configured to represent the resource attribute of a sub-resource contained in the resource, and the first-level subcode identifies a resource data type of the sub-resource and the second-level subcode indicates the resource attribute of the sub-resource identified by the first-level subcode.