CN107302441B - Information processing method and device and server - Google Patents

Abstract

Embodiments of the present invention disclose an information processing method, device, and server. The method applied to a first entity includes: receiving a first message sent by a server; wherein the first message includes a message type, service characteristics and a first rule corresponding to the service feature; the service feature is used to indicate the first service applied by the user equipment UE; according to the message type, determine whether the first message is a rule configuration message; when the first When the message is a rule configuration message, the first message is sent to the second entity; wherein the first message is used to trigger the second entity to install or update the first message corresponding to the service feature based on the first rule. Two rules.

Description

Information processing method, device and server

technical field

The present invention relates to the field of communications, and in particular, to an information processing method, device and server.

Background technique

The Policy Control and Charging Rules Function (PCRF) entity is used to decide what to execute according to the user's access network restrictions, operator policies, user subscription data, and the user's current business information, etc. The Policy and Charging Enforcement Function (PCEF) entity executes these charging policies. The PCEF entity is used to implement the detection and measurement of service data flow, the detection and measurement of service data flow, the QoS guarantee of service data flow, the traffic processing of the user plane, and the triggering of the session of the control plane by executing the policy issued by the PCRF. management, etc. This functional entity is implemented based on the gateway. A user subscription database (Subscription Profile Repository, SPR) is used to provide user subscription data to a Policy And Charging Rules Function (PCRF).

The current charging party switching process is that after the user equipment (User Equipment, UE) goes online, the application server (Application Server, AS) triggers the capability open platform to configure charging rules or QoS rules. Practice has proved that the configuration of such rules There are many methods that can only be performed after the UE goes online, and the triggering method of the rule configuration is single and so on.

SUMMARY OF THE INVENTION

In view of this, embodiments of the present invention are expected to provide an information processing method, apparatus, and server, which at least partially solve the above problems.

In order to achieve the above object, the technical scheme of the present invention is achieved in this way:

A first aspect of an embodiment of the present invention provides an information processing method applied to a first entity, the method comprising:

receiving a first message sent by a server; wherein the first message includes a message type, a service feature and a first rule corresponding to the service feature; the service feature is used to indicate the first service applied by the user equipment UE;

According to the message type, determine whether the first message is a rule configuration message;

When the first message is a rule configuration message, send the first message to a second entity; wherein the first message is used to trigger the second entity to install or update the The second rule corresponding to the service feature.

Based on the above scheme, the method further includes:

According to the message type, determine whether the first message is a rule setting message;

When the first message is a rule setting message, the first message is sent to a third entity; wherein the first message is used to trigger the third entity to install or update the The third rule corresponding to the business feature.

Based on the above solution, the first entity is a capability openness SCEF entity; the second entity is a user subscription database SPR; and the third entity is a policy control and charging rule function PCRF entity.

Based on the above solution, when the first message further includes the UE identifier of the user equipment, if the message type is a rule configuration message, it means that the UE applying the first service at the first moment is not connected to the server; the message The type is a rule setting message, indicating that the UE applying the first service is connected to the server at the first moment; the first moment is the moment when the server forms the first message.

Based on the above solution, the service feature includes at least one of a service identifier, a service uniform resource address, a service network protocol IP address, a service sponsor identity identifier, and a service provider identity identifier.

Based on the above solution, the first rule includes a service policy rule; the service feature rule includes at least one of a service charging rule and a quality of service QoS rule.

A second aspect of the embodiments of the present invention provides an information processing method, which is applied to the first entity, and the method includes:

receiving a first message sent by a server; wherein the first message includes a message type, a service feature and a first rule corresponding to the service feature; the service feature is used to indicate the first service applied by the user equipment UE;

According to the message type, determine whether the first message is a rule setting message;

When the first message is a rule setting message, the first message is sent to a third entity; wherein the first message is used to trigger the third entity to install or update the The third rule corresponding to the business feature.

A third aspect of the embodiments of the present invention provides an information processing method, which is applied to a second entity, including:

Receive the first message sent by the first entity; wherein, the first message includes a message type, a service feature and a first rule corresponding to the service feature; the service feature is used to indicate the first message applied by the user equipment UE. a business;

Based on the first rule, install or update the second rule of the first service corresponding to the service feature;

sending the second rule to a third entity according to the message type;

Wherein, the second rule is used for the third entity to install or update the third rule corresponding to the first rule.

Based on the above solution, the first message further includes a user equipment UE identifier; the UE identifier is the identifier of the first UE;

The sending the second rule to a third entity according to the message type includes:

According to the message type, determine whether the first message is a rule configuration message;

When the first message is the rule configuration message, determining whether the first UE applying the first service is currently connected to the network;

When the first UE is connected to the network at the current moment, the second rule is sent to the third entity.

Based on the above scheme, the method further includes:

When the first UE is not connected to the network at the current moment, the second rule is stored.

Based on the above solution, the sending the second rule to the third entity according to the message type includes:

According to the message type, determine whether the first message is a rule configuration message;

When the first message is the rule configuration message, query the third entity involved in the first service;

sending the second rule and the service feature to a third entity involved in the first service; wherein the second rule and the service feature are jointly used for the third entity to evaluate the first Configure billing policies for services.

Based on the above solution, the first entity is a capability openness SCEF entity; the second entity is a user subscription database SPR; and the third entity is a policy control and charging rule function PCRF entity.

A fourth aspect of the embodiments of the present invention provides an information processing method, which is applied in a server, and the method includes:

forming a first message, wherein the first message includes a message type, a service feature and a first rule corresponding to the service feature; the service feature is used to indicate the first service applied by the user equipment UE;

sending the first message to a first entity; wherein the message type is used by the first entity to determine to send the first message to a second entity or a third entity; the first rule is used for providing The second entity forms the second rule or for the third entity to form the third rule.

Based on the above scheme, the method further includes:

at the first moment, judging whether the user equipment UE applying the first service is connected to the server;

If at the first moment, the UE applying the first service is not connected to the server, determining that the message type of the first message is a rule configuration message;

If at the first moment, a first UE applying the first service has been connected to the server, determining that the message type of the first message is a rule setting message;

The first message further includes the UE identity of the first UE.

A fifth aspect of the embodiments of the present invention provides an information processing apparatus, which is applied to a first entity, where the first entity includes:

a first receiving unit, configured to receive a first message sent by a server; wherein the first message includes a message type, a service feature and a first rule corresponding to the service feature; the service feature is used to indicate the user equipment UE The first business of the application;

a first judging unit, configured to judge whether the first message is a rule configuration message according to the message type;

a first sending unit, configured to send the first message to a second entity when the first message is a rule configuration message; wherein the first message is used to trigger the second entity based on the first message A rule installs or updates the second rule corresponding to the service feature.

Based on the above solution, the first judgment unit is further configured to judge whether the first message is a rule setting message according to the message type;

The first sending unit is further configured to send the first message to a third entity when the first message is a rule setting message; wherein the first message is used to trigger the third entity to base on the The first rule installs or updates the third rule corresponding to the service feature.

Based on the above solution, the first entity is a capability openness SCEF entity; the second entity is a user subscription database SPR; and the third entity is a policy control and charging rule function PCRF entity.

Based on the above solution, when the first message further includes the UE identifier of the user equipment, if the message type is a rule configuration message, it means that the UE applying the first service at the first moment is not connected to the server; the message The type is a rule setting message, indicating that the UE applying the first service is connected to the server at the first moment; the first moment is the moment when the server forms the first message.

Based on the above solution, the service feature includes at least one of a service identifier, a service uniform resource address, a service network protocol IP address, a service sponsor identity identifier, and a service provider identity identifier.

Based on the above solution, the first rule includes a service policy rule; the service feature rule includes at least one of a service charging rule and a quality of service QoS rule.

A sixth aspect of the embodiments of the present invention provides an information processing apparatus, which is applied to a first entity, where the first entity includes:

The second receiving unit is configured to receive the first message sent by the server; wherein, the first message includes a message type, a service feature and a first rule corresponding to the service feature; the service feature is used to indicate the user equipment UE The first business of the application;

a second judging unit, configured to judge whether the first message is a rule setting message according to the message type;

a second sending unit, configured to send the first message to a third entity when the first message is a rule setting message; wherein the first message is used to trigger the third entity to A rule installs or updates the third rule corresponding to the service feature.

A seventh aspect of the embodiments of the present invention provides an information processing apparatus, applied to a second entity, including:

a third receiving unit, configured to receive the first message sent by the first entity; wherein the first message includes a message type, a service feature and a first rule corresponding to the service feature; the service feature is used for indicating the first service applied by the user equipment UE;

a processing unit, configured to install or update the second rule of the first service corresponding to the service feature based on the first rule;

a third sending unit, configured to send the second rule to a third entity according to the message type;

Wherein, the second rule is used for the third entity to install or update the third rule corresponding to the first rule.

Based on the above solution, the first message further includes a user equipment UE identifier; the UE identifier is the identifier of the first UE;

The third sending unit is specifically configured to determine whether the first message is a rule configuration message according to the message type; when the first message is the rule configuration message, determine whether to apply the first service. Whether the first UE is connected to the network at the current moment; when the first UE is connected to the network at the current moment, the second rule is sent to the third entity.

Based on the above solution, the second entity further includes:

The storage unit is further configured to store the second rule when the first UE is not connected to the network at the current moment.

Based on the above solution, the third sending unit is further specifically configured to determine whether the first message is a rule configuration message according to the message type; when the first message is the rule configuration message, query the A third entity involved in the first business; sending the second rule and the business feature to a third entity involved in the first business; wherein the second rule and the business feature are jointly used for all The third entity configures a charging policy for the first service.

Based on the above solution, the first entity is a capability openness SCEF entity; the second entity is a user subscription database SPR; and the third entity is a policy control and charging rule function PCRF entity.

An eighth aspect of an embodiment of the present invention provides a server, where the server includes:

a forming unit, configured to form a first message, wherein the first message includes a message type, a service feature and a first rule corresponding to the service feature; the service feature is used to indicate the first service applied by the user equipment UE ;

a fifth sending unit, configured to send the first message to a first entity; wherein, the message type is used by the first entity to determine to send the first message to a second entity or a third entity; The first rule is used for the second entity to form a second rule or for the third entity to form a third rule.

Based on the above solution, the server includes:

a second judging unit, configured to judge at the first moment whether the user equipment UE applying the first service is connected to the server; if at the first moment, the UE applying the first service is not connected to the server If at the first moment, a first UE applying the first service has been connected to the server, determine that the first message is a rule configuration message. The message type of the message is a rule setting message; the first message further includes the UE identifier of the first UE.

In the information processing method, the first entity, the second entity, and the server provided by the embodiments of the present invention, the first message received by the first entity includes a message type, and the first entity will determine whether the first message is a rule configuration message, and if so The rule configuration message is then sent to the second entity, which is convenient for the second entity to configure the second rule according to the first rule in the first message. In this way, it is not necessary to wait for the UE to establish a connection with the server before the rule configuration can be performed. , adding the way of rule configuration, avoiding the problem of single rule configuration. The first message may be a UE granularity message or a service granularity message; when the first message is a service granularity message, the first entity only needs to receive one piece of the first message from the server, and then pass The forwarding of the first message can perform the installation and update of the second rule and/or the third rule for the entire first service corresponding to the service feature, without the need for UE-granularity messages, which need to be sent for each UE. The message that triggers the installation and update of the second rule and/or the third rule can reduce the number of messages exchanged between the first entity and the server, thereby reducing the amount of data exchanged.

Description of drawings

1A is a schematic flowchart of a first information processing method provided by an embodiment of the present invention;

1B is a schematic flowchart of a second information processing method provided by an embodiment of the present invention;

2 is a schematic flowchart of a third information processing method provided by an embodiment of the present invention;

3 is a schematic flowchart of a fourth information processing method provided by an embodiment of the present invention;

4 is a schematic flowchart of a fifth information processing method provided by an embodiment of the present invention;

5 is a schematic structural diagram of an information processing apparatus according to an embodiment of the present invention;

6 is a schematic structural diagram of another information processing apparatus provided by an embodiment of the present invention;

7 is a schematic structural diagram of an information processing apparatus according to an embodiment of the present invention;

FIG. 8 is a schematic structural diagram of a server according to an embodiment of the present invention;

9 is a schematic flowchart of a fourth information processing method provided by an embodiment of the present invention;

10 is a schematic flowchart of a fifth information processing method provided by an embodiment of the present invention;

FIG. 11 is a schematic flowchart of a sixth information processing method according to an embodiment of the present invention.

Detailed ways

The technical solutions of the present invention will be further elaborated below with reference to the accompanying drawings and specific embodiments of the description.

Example 1:

As shown in FIG. 1A, an information processing method, applied to a first entity, includes:

Step S110: Receive a first message sent by a server; wherein, the first message includes a message type, a service feature and a first rule corresponding to the service feature; the service feature is used to indicate the first application of the user equipment UE. business;

Step S121: According to the message type, determine whether the first message is a rule configuration message;

Step S131: When the first message is a rule configuration message, send the first message to a second entity; wherein, the first message is used to trigger the second entity to install or install based on the first rule. The second rule corresponding to the service feature is updated.

The first entity may be a capability exposure (Service Capability Exposure Function, SCEF) entity. The server may be an application server; the second entity may be a user subscription database (SubscriptionProfile Repository, SPR).

In this embodiment, the first message is provided by the server, and the first message carries at least a message type, a service feature, and a first rule. The service feature includes at least one of a service identifier, a service uniform resource address (Uniform Resource Location, URL), a service Internet Protocol (Internet Protocol, IP) address, a service sponsor ID, and a service provider ID. The service identifier here may be various identification information of the first service, such as identification information such as a service code serial number of the first service identifier. The service IP address may be the IP address of the server providing the service. The server may be the server in step S110, which may be referred to as an application server. The service sponsor ID and service provider ID may be an IP address, a media access control (Media Access Control, MAC) address, a domain name address, or a server name, and the like. Of course, the service feature may also include other identifiers that can indicate the first service provider.

The first rule may include a service policy rule; the service feature rule may include at least one of a service charging rule and a quality of service (QoS) rule. The service charging rule can be used to indicate the service fee payment scheme, payment method, unit price and other related information about root charging. The quality of service rule is used to indicate the quality of service of the first service, for example, parameters such as required delay. The service charging rule instructs to switch the payer. For example, the configuration instruction is used to instruct the payer to switch the charging, for example, another example is to instruct the payer, to indicate the payment time period of a certain payer or the payment ratio of each payer and other information related to charging.

When the first message further includes the UE identifier of the user equipment, if the message type is a rule configuration message, it means that the UE applying the first service at the first moment is not connected to the server; the message type is rule setting message, indicating that the UE applying the first service is connected to the server at the first moment; the first moment is the moment when the server forms the first message. In this embodiment, the UE identifier may be an International Mobile Equipment Identity (International Mobile Equipment Identity, IMEI) of the user equipment, or may be a communication identifier of the UE. The communication identifier here may be an identifier such as a mobile phone number. In this case, the UE identifier is the identifier of the UE applying the first service.

The server can determine whether the UE applying the first service is connected to the server according to when it forms the first message, and then determine the message type according to the connection status with the UE, which is convenient for all users. The first entity determines whether to send the first message to the second entity or the third entity according to the message type.

As a further improvement of this embodiment,

As shown in Figure 1B, the method further includes:

Step S122: According to the message type, determine whether the first message is a rule setting message;

Step S123: when the first message is a rule setting message, send the first message to a third entity; wherein, the first message is used to trigger the third entity to install or install based on the first rule. The third rule corresponding to the service feature is updated.

If it is determined that the first message is a rule setting message, the first entity directly sends the first message to a third entity, where the third entity may be a PCRF entity. The third rule is a rule corresponding to the first service.

In this embodiment, the second rule and the third rule are both rules corresponding to the first service rule. For example, the first rule includes a QoS rule, then both the second rule and the third rule may include a QoS rule. In this embodiment, the second rule is a rule stored in the second entity, the third rule is a rule stored in a third entity, and the second rule can be used as a One of the basis for generation. In a specific implementation process, the third rule may be directly used to perform operations such as quality control and charging processing for the UE accessing the first service.

In this embodiment, the first message may be a UE granularity message or a service granularity message; correspondingly, the first service rule may be a UE granularity rule or a service granularity rule. The second rule may also be a UE granularity rule or a service granularity rule. The third rule is usually a UE granularity rule.

When the first rule is a rule of service granularity, the first entity only needs to receive one first message, and the second entity or the third entity will respond to the service feature carried in the first message by the second entity or the third entity. The corresponding first service performs rule installation or update of the entire service. In this way, the server only needs to send the first message to the first entity, so that the second rule and the third rule corresponding to all UEs applying the first service can be configured. At this time, usually the first message does not include the UE identifier of the UE applying the first service.

Embodiment 2:

As shown in FIG. 2, this embodiment provides an information processing method, which is applied to the first entity, and the method includes:

Step S210: Receive a first message sent by the server; wherein, the first message includes a message type, a service feature and a first rule corresponding to the service feature; the service feature is used to indicate the first application of the user equipment UE. business;

Step S220: According to the message type, determine whether the first message is a rule setting message;

When the first message is a rule setting message, the first message is sent to a third entity; wherein the first message is used to trigger the third entity to install or update the The third rule corresponding to the business feature.

This embodiment is an information processing method applied to the first entity. In this embodiment, the first entity, the third entity, the first message, the first rule, and the third rule can all refer to Embodiment 1 will not be repeated here. In a word, the information processing method described in this embodiment can simply determine whether the first message is a rule setting message according to the message type included in the first message, so as to determine whether it needs to be sent to a third entity.

Embodiment three:

As shown in FIG. 3 , this embodiment provides an information processing method, which is applied to the second entity, including:

Step S310: Receive the first message sent by the first entity; wherein the first message includes a message type, a service feature and a first rule corresponding to the service feature; the service feature is used to indicate the user equipment UE The first business of the application;

Step S320: Based on the first rule, install or update the second rule of the first service corresponding to the service feature;

Step S330: according to the message type, send the second rule to a third entity;

Wherein, the second rule is used for the third entity to install or update the third rule corresponding to the first rule.

The information processing method provided in this embodiment is a method applied to a second entity, where the second entity may be the aforementioned user subscription database SPR, and the first entity may be the SCEF entity. The third entity may be a PCRF entity.

In this embodiment, the second entity receives the first message sent by the first entity, where the first message may be the first message provided by a server such as an application server AS forwarded by the first entity. For the formation and information content of the first message here, reference may be made to Embodiment 1, which will not be repeated here.

The step S320 is to install or update the second rule of the first service corresponding to the service feature according to the first rule. The second rule here is a rule stored in the second entity. Generally, the content included in the second rule is consistent with the content included in the first rule. The second rule is generated according to the first rule. Here, the first rule may be a service granularity rule or a UE granularity rule. The second rule may also be a service granularity or UE granularity rule.

In a word, the second entity in this embodiment configures the second rule and sends the third rule according to the first message sent by the first entity.

There are many ways to implement the step S330, and the following provides several optional ways:

Option 1:

The first message further includes the user equipment UE identifier; the UE identifier is the identifier of the first UE. The step S330 may include: according to the message type, judging whether the first message is a rule configuration message; when the first message is the rule configuration message, determining a first UE that applies the first service Whether it is currently connected to the network; when the first UE is currently connected to the network, the second rule is sent to the third entity. According to the method described in the first embodiment, the first message may be formed at the first moment, and the current moment at the moment when the step S330 is performed in this embodiment may be the second moment. Usually, the second moment is the same as the second moment. The current moment is a different moment. In this embodiment, the second entity will determine whether the first UE applying the first service at the current moment is connected to the network, where the connection to the network may be whether the UE is connected to the network through the communication interface of the UE, and the first UE is connected to the network through the communication interface of the UE. The three entities can conduct a session with the UE through the network. For example, the UE may not be connected to the network if the UE is powered off or the battery is pulled out; if the UE is powered on and currently attached to the network, the UE is considered to be connected to the network.

Here, it is determined whether the first UE is connected to the network, the second entity itself maintains a database representing whether the UE is connected to the network at the current moment, and the second entity can easily know the first UE by querying the database maintained by itself. Whether a UE is online at the current moment. Specifically, if the second entity is an SPR, the SPR maintains data on whether each subscribed UE is connected to the network at the current moment.

Of course, the first message is the first moment. If the time difference between the first moment and the current moment is less than the preset time threshold, it may be directly considered that the first UE is currently connected to the network. If the time difference between the first moment and the second moment is greater than the time threshold, the second entity may determine whether the first UE is currently connected to the network by querying a database maintained by itself.

In step S330, when sending the second rule to the third entity, it may include: sending the UE identity of the first UE connected to the network at the current moment to the third entity, so as to facilitate the third entity. The entity conducts a session with the UE according to the UE identifier, and performs the setting of the foregoing third rule.

As a further improvement of this embodiment, the method further includes:

The second rule is stored when the first UE is not currently connected to the network. The storage here requires the rule to wait for the first UE to connect to the network again before sending the third entity, and the third entity can install and configure the third rule through the connection with the UE.

Option 2:

The step S330 may include:

According to the message type, determine whether the first message is a rule configuration message;

When the first message is the rule configuration message, query the third entity involved in the first service;

sending the second rule and the service feature to a third entity involved in the first service; wherein the second rule and the service feature are jointly used for the third entity to evaluate the first Configure billing policies for services.

In this embodiment, the second entity will not judge whether the UE is connected to the network at the current moment. In this embodiment, it will query the third entity involved in the first service according to the service characteristics. After the third entity of the first service is sent, the second rule and the service feature are sent to the corresponding third entity. The third entity here may be a PCRF entity, so the entity involved in the third service will install or update the third rule according to the service granularity according to the service feature rule.

It is worth noting that the rules are installed and updated according to the business granularity, which may include the configuration of the business granularity of the second rule and the installation and update of the business granularity of the third rule. For example, if there are M UEs applying the first service, in step S330, when configuring the second rule, according to the service feature, find out all the second rules of the first service that match the service feature, The second rule is updated uniformly according to the first rule. If the second rule of the first service is not currently stored in the second entity, the service feature is directly used as an identifier to configure the second rule of the first service to form a second rule, and later No matter which UE or which UE uses the first service, the second rule is used for processing. Usually the second rule may not store the identity of the UE. The configuration of the above rules is also applicable to the configuration of the third rule at business granularity.

Embodiment 4:

As shown in Figure 4, an information processing method, applied in a server, includes:

Step S410: forming a first message, wherein the first message includes a message type, a service feature and a first rule corresponding to the service feature; the service feature is used to indicate the first service applied by the user equipment UE;

Step S420: Send the first message to a first entity; wherein, the message type is used by the first entity to determine to send the first message to a second entity or a third entity; the first rule For the second entity to form the second rule or for the third entity to form the third rule.

In this embodiment, the server will form a first message, and the first message includes a message type. In this embodiment, the type may include a rule configuration message and a rule setting message.

For detailed definitions of the service features and the first rule, please refer to the corresponding parts in Embodiment 1, and will not be repeated here.

In this embodiment, step S420 will send the first message to a first entity, where the first entity may be a SCEF entity as described in Embodiment 1, and the message type is used for the first entity Whether the entity sends the first message to the second entity or sends the first message to the second entity.

The first message may be a service-granular rule installation or update message, or a UE-granular rule installation or update message. Usually, a service-granularity rule can be sent to the second entity by sending a piece of the first message. and updating the second rule and the third rule corresponding to the UE applying the first service with the third entity. Of course, the first message may also be a UE-granular rule installation or update message. In this case, the first message may contain a service granularity for at least partially applying the first service. In this embodiment, the server may be a server such as an application server AS that provides the first business service. For the detailed content of the service feature, please refer to Embodiment 1. In a word, the message type is added to the first message in this embodiment, which facilitates the first entity to determine the recipient who receives the first message, and has the characteristics of simple implementation.

Further, the method includes:

At the first moment, determine whether the user equipment UE applying the first service is connected to the server; if at the first moment, the UE applying the first service is not connected to the server, determine the The message type of the first message is a rule configuration message; if at the first moment, a first UE applying the first service has been connected to the server, it is determined that the message type of the first message is a rule setting message; the first message further includes the UE identity of the first UE. In this embodiment, the first moment is the moment when the first message is formed, and the server may select the first UE by detecting its currently established connection, and assign the UE identifier of the first UE to the server. carried in the first message. Usually at this time, the first message is a UE-granular rule installation or update message.

Embodiment 5:

As shown in FIG. 5 , this embodiment provides an information processing apparatus, which is applied to a first entity, where the first entity includes:

The first receiving unit 110 is configured to receive a first message sent by a server; wherein the first message includes a message type, a service feature and a first rule corresponding to the service feature; the service feature is used to indicate the user equipment The first service applied by the UE;

a first judging unit 120, configured to judge whether the first message is a rule configuration message according to the message type;

A first sending unit 130, configured to send the first message to a second entity when the first message is a rule configuration message; wherein the first message is used to trigger the second entity to The first rule installs or updates the second rule corresponding to the service feature.

The first entity may be a SCEF entity, but is not limited to a SCEF entity. The second entity is the user subscription database SPR; the third entity is the policy control and charging rule function PCRF entity. For example, the SCEF entity may be a functional entity applied to various electronic devices, such as a server or a service platform. The first receiving unit 110 and the first transmitting unit 130 may correspond to various types of communication interfaces. The communication interface here may include a wired interface or a wireless interface, and the wired interface may include a cable interface or an optical fiber interface. The wireless interface may include a transceiver antenna and the like.

The first judgment unit 120 may include a processor or a processing circuit, and the processor may include a central processing unit, a microprocessor, a digital signal processor, an application processor, a programmable array, or the like. The processing circuit may comprise an application specific integrated circuit. The processor may complete the second regular formation through the execution of the specified code. The ASIC may complete the formation of the second rule through the transmission of electrical signals.

The first determining unit 120 is further configured to determine whether the first message is a rule setting message according to the message type; the first sending unit 130 is further configured to determine whether the first message is a rule setting message when the first message is a rule setting message When the first message is sent to a third entity, the first message is used to trigger the third entity to install or update the third rule corresponding to the service feature based on the first rule.

When the first message further includes the UE identifier of the user equipment, if the message type is a rule configuration message, it means that the UE applying the first service at the first moment is not connected to the server; the message type is rule setting message, indicating that the UE applying the first service is connected to the server at the first moment; the first moment is the moment when the server forms the first message.

Further, the service feature includes at least one of a service identifier, a service uniform resource address, a service network protocol IP address, a service sponsor identity identifier and a service provider identity identifier. The first rule includes a service policy rule; the service feature rule includes at least one of a service charging rule and a quality of service QoS rule.

Embodiment 6:

As shown in FIG. 6, this embodiment provides a first entity, and the first entity includes:

The second receiving unit 210 is configured to receive a first message sent by the server; wherein the first message includes a message type, a service feature and a first rule corresponding to the service feature; the service feature is used to indicate the user equipment The first service applied by the UE;

a second judging unit 220, configured to judge whether the first message is a rule setting message according to the message type;

The second sending unit 230 is configured to send the first message to a third entity when the first message is a rule setting message; wherein, the first message is used to trigger the third entity based on the The first rule installs or updates the third rule corresponding to the service feature.

The first entity in this embodiment may have the same physical structure as the first entity in the fifth embodiment. The second receiving unit 210 may correspond to the first receiving unit 110 in the foregoing embodiments, the second transmitting unit 230 may correspond to the first transmitting unit 130 in the foregoing embodiments; the second determining unit 220 may correspond to The second judging unit in the foregoing embodiment. For details of the first service and the first message, reference may be made to the foregoing embodiments. In a word, this embodiment provides a first entity, which can determine whether to send the first message to the third entity according to the message type.

Embodiment 7:

As shown in FIG. 7 , this embodiment provides an information processing apparatus, which is applied to a second entity, including:

The third receiving unit 310 is configured to receive the first message sent by the first entity; wherein the first message includes a message type, a service feature, and a first rule corresponding to the service feature; the service feature uses for indicating the first service applied by the user equipment UE;

a processing unit 320, configured to install or update the second rule of the first service corresponding to the service feature based on the first rule;

a third sending unit 330, configured to send the second rule to a third entity according to the message type;

Wherein, the second rule is used for the third entity to install or update the third rule corresponding to the first rule.

The second entity may be an SPR. The second entity can be applied to various electronic devices, such as a server or a functional entity on a service platform. The third receiving unit 310 and the third transmitting unit 330 may correspond to various types of communication interfaces. The communication interface here may include a wired interface or a wireless interface, and the wired interface may include a cable interface or an optical fiber interface. The wireless interface may include a transceiver antenna and the like.

The processing unit 320 may include a processor or processing circuit, and the processor may include a central processing unit, a microprocessor, a digital signal processor, an application processor, a programmable array, or the like. The processing circuit may comprise an application specific integrated circuit. The processor may complete the second regular formation through the execution of the specified code. The ASIC may complete the formation of the second rule through the transmission of electrical signals.

Specifically, as described in this embodiment, the third receiving unit 310 may be configured to receive the first message forwarded by the SCEF entity and formed by the AS in the first state, where the first message does not include the UE of the UE applying the first service logo. For the detailed description of the first state, the first message, the service feature, and the configuration instruction in this embodiment, reference may be made to the first implementation, which will not be repeated here.

There are various structures of the second entity, and several optional structures are provided below:

Optional structure one:

The first message further includes a user equipment UE identity; the UE identity is the identity of the first UE;

The third sending unit 330 is specifically configured to determine whether the first message is a rule configuration message according to the message type; when the first message is the rule configuration message, determine to apply the first service whether the first UE is connected to the network at the current moment; when the first UE is connected to the network at the current moment, the second rule is sent to the third entity.

The second entity also includes:

The storage unit is further configured to store the second rule when the first UE is not connected to the network at the current moment. The storage unit described in this embodiment may include various types of storage media, for example, random storage media RAM, read-only storage media ROM, or flash memory Flash, optionally non-transitory storage media. The stored second rule may be sent to the third entity after the corresponding UE is connected to the network. Usually in optional structure 1, the third sending unit 330 also sends the UE identifier of the UE currently connected to the network and applying the first service to the third entity, so as to facilitate the third entity to install the third rule or update.

Optional structure two:

The third sending unit 330 is further specifically configured to determine whether the first message is a rule configuration message according to the message type; when the first message is the rule configuration message, query the first service The third entity involved; sending the second rule and the business feature to a third entity involved in the first business; wherein the second rule and the business feature are jointly used for the third entity The entity configures a charging policy for the first service. In this embodiment, the second rule configuration and the third rule configuration of the service granularity are performed, so that the third sending unit 330 does not need to determine which UEs currently applying the first service are connected to the network.

Further, the first entity is a capability openness SCEF entity; the second entity is a user subscription database SPR; and the third entity is a policy control and charging rule function PCRF entity.

In conclusion, this embodiment provides a second entity that can easily and quickly generate a second rule and send the second rule to a third entity.

Embodiment 8:

As shown in FIG. 8 , this embodiment provides a server, and the server includes:

The forming unit 410 is configured to form a first message, wherein the first message includes a message type, a service feature and a first rule corresponding to the service feature; the service feature is used to indicate the first application of the user equipment UE. business;

a fifth sending unit 420, configured to send the first message to a first entity; wherein, the message type is used by the first entity to determine to send the first message to a second entity or a third entity; The first rule is used for the second entity to form a second rule or for the third entity to form a third rule.

The server in this embodiment may be an application server, which may be a server providing the first service, a server in a communication platform of a current communication operator, or a third-party server outside the current communication platform.

The forming unit 410 may correspond to a processor or a processing circuit in the server, the structure of the processor or the processing circuit, the first message, the specific structure corresponding to the first entity to the third entity, the first rule For the similarities and differences to the third rule, reference can be made to the foregoing embodiments, and will not be repeated here.

Further, the server includes:

a second judging unit, configured to judge at the first moment whether the user equipment UE applying the first service is connected to the server; if at the first moment, the UE applying the first service is not connected to the server If at the first moment, a first UE applying the first service has been connected to the server, determine that the first message is a rule configuration message. The message type of the message is a rule setting message; the first message further includes the UE identifier of the first UE.

In this embodiment, the second determining unit may determine the first UE by querying the local storage medium of the server or other electronic devices. The local storage medium can be various types of storage medium, and has the characteristics of simple structure and easy implementation.

Several specific examples are provided below in conjunction with any of the above-mentioned embodiments:

Example one:

As shown in Figure 9, this example provides an information processing method, including:

Step S1: transmission of the first message; the AS sends a first message to the SCEF entity, where the first message includes the service feature and the first rule installed or updated by the second rule of a certain service. The service feature may include information such as the IP address of the AS or the URL of the service. The first rule may be used to indicate a payer for switching billing.

Step S2: Authentication; the SCEF entity authenticates whether the AS has the right to update or install the second rule for the service.

Step S3: Determine whether there is a UE applying the first service connected to the network, if yes, go to Step S4, if not, go to Step S6. Step S3 is executed after the authentication is passed. The service corresponding to the service feature of the first service.

Step S4: The first UE that applies the first service is connected to the network, and the UE identifier of the first UE is extracted.

Step S5: Transmission of the first message and the first UE identity. The SCEF entity sends the first message and the first UE identity to the SPR.

Step S6: The UE that does not apply the first service is connected to the network, and the first message is stored.

Step S7: Install or update the second rule of the first service according to the first message.

Step S8: Transmission of the second rule and the identity of the first UE. Here, the SPR sends the second rule and the first UE to the PCRF entity.

Step S9: transmission of the response message. The response message here indicates that at least the second rule is configured according to the first message. The transmission of the response message includes two parts: the first part: the SPR sends the response message to the SCEF entity; the second part: the SCEF entity sends the response message to the AS. In specific implementation, the transmission of the response message may be that after the SCEF entity sends the first message to the SPR, the response message is sent to the AS.

Example two:

As shown in Figure 10, this example provides an information processing method, including:

Step S11: transmission of the first message; the AS sends a first message to the SCEF entity, where the first message includes the service feature and the first rule installed or updated by the second rule of a certain service. The service feature may include information such as the IP address of the AS or the URL of the service. The first rule may be used to indicate a payer for switching billing.

Step S12: Authentication; the SCEF entity authenticates whether the AS has the right to update or install the second rule for the service.

Step S13: The transmission of the first message specifically includes: the SCEF entity sends the first message to the SPR. Step S13 is executed after the authentication is passed. The service corresponding to the service feature of the first service.

Step S14: Install or update the second rule for the first service.

Step S15: Determine the second UE identifier of the second UE that applies the first service and is currently connected to the network;

Step S16: Transmission of the second rule and the second UE identity.

Step S17: Install and update the third rule on the second UE according to the second rule.

Step S18: Store the second rule of the third UE that applies the first service and is not currently connected to the network.

Step S19: Transmission of the response message. The transmission of the response message includes two parts: the first part: the SPR sends the response message to the SCEF entity; the second part: the SCEF entity sends the response message to the AS. In specific implementation, the transmission of the response message may be that after the SCEF entity sends the first message to the SPR, the response message is sent to the AS.

Example three:

As shown in Figure 11, this example provides an information processing method, including:

Step S21: transmission of the first message; the AS sends a first message to the SCEF entity, where the first message includes the service feature and the first rule installed or updated by the second rule of a certain service. The service feature may include information such as the IP address of the AS or the URL of the service. The first rule may be used to indicate a payer for switching billing.

Step S22: Authentication; the SCEF entity authenticates whether the AS has the right to update or install the second rule for the service.

Step S23: The transmission of the first message specifically includes: the SCEF entity sends the first message to the SPR. Step S23 is executed after the authentication is passed. The service corresponding to the service feature of the first service.

Step S24: Install and update the second rule for the first service.

Step S25: Determine the PCRF entity involved in the first service.

Step S26: Transmission of the second rule and service feature. The SPR here sends the second rule and service characteristics to the PCRF entity.

Step S27: Transmission of the response message. The first part: the SPR sends a response message to the SCEF entity; the second part: the SCEF entity sends a response message to the AS. In specific implementation, the transmission of the response message may be that after the SCEF entity sends the first message to the SPR, the response message is sent to the AS.

It is worth noting that in this application, the AS may also be called SCS, the SPR may also be called UCD, the SCS is an abbreviation of Services Capability Server, and the corresponding Chinese is Business Capability Server. The UCD is an abbreviation of UserData Convergence, which is also a user database in Chinese.

In the several embodiments provided in this application, it should be understood that the disclosed apparatus and method may be implemented in other manners. The device embodiments described above are only illustrative. For example, the division of the units is only a logical function division. In actual implementation, there may be other division methods. For example, multiple units or components may be combined, or Can be integrated into another system, or some features can be ignored, or not implemented. In addition, the coupling, or direct coupling, or communication connection between the components shown or discussed may be through some interfaces, and the indirect coupling or communication connection of devices or units may be electrical, mechanical or other forms. of.

The unit described above as a separate component may or may not be physically separated, and the component displayed as a unit may or may not be a physical unit, that is, it may be located in one place or distributed to multiple network units; Some or all of the units may be selected according to actual needs to achieve the purpose of the solution in this embodiment.

In addition, each functional unit in each embodiment of the present invention may all be integrated into one processing module, or each unit may be separately used as a unit, or two or more units may be integrated into one unit; the above-mentioned integration The unit can be implemented either in the form of hardware or in the form of hardware plus software functional units.

Those of ordinary skill in the art can understand that all or part of the steps of implementing the above method embodiments can be completed by program instructions related to hardware, the aforementioned program can be stored in a computer-readable storage medium, and when the program is executed, execute Including the steps of the above-mentioned method embodiment; and the aforementioned storage medium includes: a mobile storage device, a read-only memory (ROM, Read-Only Memory), a random access memory (RAM, Random Access Memory), a magnetic disk or an optical disk and other various A medium on which program code can be stored.

The above are only specific embodiments of the present invention, but the protection scope of the present invention is not limited thereto. Any person skilled in the art can easily think of changes or substitutions within the technical scope disclosed by the present invention. should be included within the protection scope of the present invention. Therefore, the protection scope of the present invention should be based on the protection scope of the claims.

Claims (24)

1. An information processing method applied to a first entity, the method comprising:

receiving a first message sent by a server; the first message comprises a message type, a service characteristic and a first rule corresponding to the service characteristic; the service characteristic is used for indicating a first service applied by User Equipment (UE); the first entity is a capability open SCEF entity;

judging whether the first message is a rule configuration message or not according to the message type;

when the first message is a rule configuration message, sending the first message to a second entity; the first message is used for triggering the second entity to install or update a second rule corresponding to the service feature based on the first rule; the second entity is a user subscription database SPR;

when the first message further comprises a User Equipment (UE) identity, if the message type is a rule configuration message, indicating that the UE applying the first service at the first moment is not connected to the server; the first time is the time when the server forms the first message.

2. The method of claim 1,

the method further comprises the following steps:

judging whether the first message is a rule setting message or not according to the message type;

when the first message is a rule setting message, sending the first message to a third entity; the first message is used for triggering the third entity to install or update a third rule corresponding to the business feature based on the first rule; and the third entity is a policy control and charging rule function (PCRF) entity.

3. The method of claim 2,

and if the message type is a rule setting message, indicating that the UE applying the first service at the first moment is connected to the server.

4. The method of claim 1,

the service characteristics comprise at least one of service identification, service uniform resource address, service network protocol IP address, service sponsor identification and service provider identification.

5. The method of claim 1,

the first rule comprises a business policy rule; the service characteristic rule comprises at least one of a service charging rule and a service quality QoS rule.

6. An information processing method applied to a first entity, the method comprising:

receiving a first message sent by a server; the first message comprises a message type, a service characteristic and a first rule corresponding to the service characteristic; the service characteristic is used for indicating a first service applied by User Equipment (UE); the first entity is a capability open SCEF entity;

judging whether the first message is a rule setting message or not according to the message type;

when the first message is a rule setting message, sending the first message to a third entity; the first message is used for triggering the third entity to install or update a third rule corresponding to the business feature based on the first rule; the third entity is a policy control and charging rule function (PCRF) entity;

when the first message further comprises a User Equipment (UE) identifier, if the message type is a rule setting message, indicating that the UE applying the first service at a first moment is connected to the server; the first time is the time when the server forms the first message.

7. An information processing method applied to a second entity, comprising:

receiving a first message sent by a first entity; the first message comprises a message type, a service characteristic and a first rule corresponding to the service characteristic; the service characteristic is used for indicating a first service applied by User Equipment (UE); the first message further comprises a User Equipment (UE) identity; the first entity is a capability open SCEF entity; the second entity is a user subscription database SPR;

installing or updating a second rule of the first service corresponding to the service characteristic based on the first rule;

sending the second rule to a third entity according to the message type; the third entity is a policy control and charging rule function (PCRF) entity;

the sending the second rule to a third entity according to the message type includes:

judging whether the first message is a rule configuration message or not according to the message type;

when the first message is the rule configuration message, determining whether a first UE applying the first service is connected to a network at the current moment;

sending the second rule to the third entity when the first UE is connected to a network at the current moment;

wherein the second rule is used for the third entity to install or update a third rule corresponding to the first rule.

8. The method of claim 7,

the UE identity is the identity of the first UE.

9. The method of claim 8,

the method further comprises the following steps:

storing the second rule when the first UE is not connected to a network at a current time.

10. The method of claim 7,

the sending the second rule to a third entity according to the message type includes:

judging whether the first message is a rule configuration message or not according to the message type;

when the first message is the rule configuration message, inquiring a third entity involved in the first service;

sending the second rule and the service characteristic to a third entity related to the first service; wherein the second rule and the service feature are jointly used for the third entity to perform charging policy configuration on the first service.

11. An information processing method, applied to a server, the method comprising:

forming a first message, wherein the first message comprises a message type, a service characteristic and a first rule corresponding to the service characteristic; the service characteristic is used for indicating a first service applied by User Equipment (UE);

sending the first message to a first entity; wherein the message type is used for the first entity to determine to send the first message to a second entity or a third entity; the first rule is used for the second entity to form a second rule or for the third entity to form a third rule; the first entity is a capability open SCEF entity; the second entity is a user subscription database SPR; the third entity is a policy control and charging rule function (PCRF) entity;

at a first moment, judging whether User Equipment (UE) applying the first service is connected to the server;

if the UE applying the first service is not connected to the server at the first moment, determining that the message type of the first message is a rule configuration message;

and if a first UE applying the first service is connected to the server at the first moment, determining that the message type of the first message is a rule setting message.

12. The method of claim 11,

the first message further includes a UE identity of the first UE.

13. An information processing apparatus applied to a first entity, the apparatus comprising:

the first receiving unit is used for receiving a first message sent by the server; the first message comprises a message type, a service characteristic and a first rule corresponding to the service characteristic; the service characteristic is used for indicating a first service applied by User Equipment (UE); the first entity is a capability open SCEF entity;

the first judging unit is used for judging whether the first message is a rule configuration message or not according to the message type;

a first sending unit, configured to send the first message to a second entity when the first message is a rule configuration message; the first message is used for triggering the second entity to install or update a second rule corresponding to the service feature based on the first rule; the second entity is a user subscription database SPR;

when the first message further comprises a User Equipment (UE) identity, if the message type is a rule configuration message, indicating that the UE applying the first service at the first moment is not connected to the server; the first time is the time when the server forms the first message.

14. The apparatus of claim 13,

the first judging unit is further configured to judge whether the first message is a rule setting message according to the message type;

the first sending unit is further configured to send the first message to a third entity when the first message is a rule setting message; the first message is used for triggering the third entity to install or update a third rule corresponding to the business feature based on the first rule; and the third entity is a policy control and charging rule function (PCRF) entity.

15. The apparatus of claim 14,

the message type is a rule setting message, and indicates that the UE applying the first service at the first moment is connected to the server.

16. The apparatus of claim 13,

the service characteristics comprise at least one of service identification, service uniform resource address, service network protocol IP address, service sponsor identification and service provider identification.

17. The apparatus of claim 13,

the first rule comprises a business policy rule; the service characteristic rule comprises at least one of a service charging rule and a service quality QoS rule.

18. An information processing apparatus applied to a first entity, the apparatus comprising:

the second receiving unit is used for receiving the first message sent by the server; the first message comprises a message type, a service characteristic and a first rule corresponding to the service characteristic; the service characteristic is used for indicating a first service applied by User Equipment (UE); the first entity is a capability open SCEF entity;

a second judging unit, configured to judge whether the first message is a rule setting message according to the message type;

a second sending unit, configured to send the first message to a third entity when the first message is a rule setting message; the first message is used for triggering the third entity to install or update a third rule corresponding to the business feature based on the first rule; the third entity is a policy control and charging rule function (PCRF) entity;

when the first message further comprises a User Equipment (UE) identifier, the message type is a rule setting message, and the message indicates that the UE applying the first service at the first moment is connected to the server; the first time is the time when the server forms the first message.

19. An information processing apparatus applied to a second entity, comprising:

a third receiving unit, configured to receive a first message sent by a first entity; the first message comprises a message type, a service characteristic and a first rule corresponding to the service characteristic; the service characteristic is used for indicating a first service applied by User Equipment (UE); the first message further comprises a User Equipment (UE) identity; the first entity is a capability open SCEF entity; the second entity is a user subscription database SPR;

the processing unit is used for installing or updating a second rule of the first service corresponding to the service characteristic based on the first rule;

a third sending unit, configured to send the second rule to a third entity according to the message type; the third entity is a policy control and charging rule function (PCRF) entity;

the third sending unit is specifically configured to determine, according to the message type, whether the first message is a rule configuration message; when the first message is the rule configuration message, determining whether a first UE applying the first service is connected to a network at the current moment; sending the second rule to the third entity when the first UE is connected to a network at the current moment;

wherein the second rule is used for the third entity to install or update a third rule corresponding to the first rule.

20. The apparatus of claim 19,

the UE identity is the identity of the first UE.

21. The apparatus of claim 20,

the second entity further comprises:

a storage unit, further configured to store the second rule when the first UE is not connected to a network at the current time.

22. The apparatus of claim 21,

the third sending unit is further specifically configured to determine whether the first message is a rule configuration message according to the message type; when the first message is the rule configuration message, inquiring a third entity involved in the first service; sending the second rule and the service characteristic to a third entity related to the first service; wherein the second rule and the service feature are jointly used for the third entity to perform charging policy configuration on the first service.

23. A server, the server comprising:

the system comprises a forming unit, a processing unit and a processing unit, wherein the forming unit is used for forming a first message, and the first message comprises a message type, a service characteristic and a first rule corresponding to the service characteristic; the service characteristic is used for indicating a first service applied by User Equipment (UE);

a fifth sending unit, configured to send the first message to a first entity; wherein the message type is used for the first entity to determine to send the first message to a second entity or a third entity; the first rule is used for the second entity to form a second rule or for the third entity to form a third rule; the first entity is a capability open SCEF entity; the second entity is a user subscription database SPR; the third entity is a policy control and charging rule function (PCRF) entity;

a second determining unit, configured to determine, at a first time, whether a UE applying the first service is connected to the server; if the UE applying the first service is not connected to the server at the first moment, determining that the message type of the first message is a rule configuration message; and if a first UE applying the first service is connected to the server at the first moment, determining that the message type of the first message is a rule setting message.

24. The server according to claim 23,

the first message further includes a UE identity of the first UE.

Images