CN107302441B

CN107302441B - Information processing method and device and server

Info

Publication number: CN107302441B
Application number: CN201610232639.1A
Authority: CN
Inventors: 蔡慧
Original assignee: China Mobile Communications Group Co Ltd; China Mobile Communications Ltd Research Institute
Current assignee: China Mobile Communications Group Co Ltd; China Mobile Communications Ltd Research Institute
Priority date: 2016-04-14
Filing date: 2016-04-14
Publication date: 2020-06-30
Anticipated expiration: 2036-04-14
Also published as: CN107302441A

Abstract

The embodiment of the invention discloses an information processing method, an information processing device and a server, wherein the method applied to a first entity comprises the following steps: 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); 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.

Description

Information processing method and device and server

Technical Field

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

Background

A Policy Control and Charging Rules Function (PCRF) entity, configured to determine a Policy to be executed according to a restriction on a network accessed by a user, an operator Policy, user subscription data, service information currently performed by the user, and the like, and issue the Policy to a Policy and Charging Enforcement Function entity, where the Policy and Charging Enforcement Function (PCEF) entity enforces the Charging policies. And the PCEF entity is configured to implement detection and measurement of a service data flow, QoS guarantee of a service data flow, traffic processing of a user plane, session management of a trigger control plane, and the like by executing a policy issued by the PCRF. The functional entity is implemented based on a gateway. A Subscription database (SPR) for providing subscriber Subscription data to a Policy And Charging Rules Function (PCRF).

The current charging party switching process is that after User Equipment (UE) is on-line, an Application Server (AS) triggers a capability opening platform to configure a charging rule or a service quality rule, and practice proves that many rule configuration modes need to be performed after the UE is on-line, and the rule configuration triggering mode is single.

Disclosure of Invention

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

In order to achieve the purpose, the technical scheme of the invention is realized as follows:

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

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);

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.

Based on the above scheme, the method further comprises:

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.

Based on the scheme, the first entity is an SCEF entity with opened capability; 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 scheme, when the first message further includes a UE identity, if the message type is a rule configuration message, it indicates that the UE applying the first service at the first time is not connected to the server; 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; the first time is the time when the server forms the first message.

Based on the scheme, the service characteristics comprise at least one of a service identifier, a service uniform resource address, a service network protocol (IP) address, a service sponsor identifier and a service provider identifier.

Based on the scheme, the first rule comprises a business strategy rule; the service characteristic rule comprises at least one of a service charging rule and a service quality QoS rule.

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

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

receiving the 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);

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;

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

Based on the above scheme, the first message further includes a UE identity; the UE identification is an identification of a first UE;

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

when the first message is the rule configuration message, determining whether the 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 time.

Based on the above scheme, the method further comprises:

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

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

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.

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

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.

Based on the above scheme, the method further comprises:

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;

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;

the first message further includes a 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:

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 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.

Based on the above scheme, the first determining unit is further configured to determine 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.

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

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);

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.

A seventh aspect 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; 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 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 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 the 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 time.

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

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

Based on the above scheme, 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.

An eighth aspect of the embodiments of the present invention provides a server, including:

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.

Based on the above scheme, the server includes:

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; 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; the first message further includes a UE identity of the first UE.

In the information processing method, the first entity, the second entity, and the server provided in the embodiments of the present invention, the first message received by the first entity includes a message type, and the first entity determines whether the first message is a rule configuration message, and if the first message is the rule configuration message, the first message is sent to the second entity, so that the second entity can conveniently configure the second rule according to the first rule in the first message. The first message may be a message of UE granularity or a message of service granularity; when the first message is a message of service granularity, the first entity only needs to receive one first message from the server, and then the first message is forwarded to install and update the second rule and/or the third rule on the whole first service corresponding to the service characteristics, so that messages of UE granularity are not needed, and a message triggering the installation and update of the second rule and/or the third rule needs to be sent for each UE, so that the number of message interactions between the first entity and the server can be reduced, and the amount of interactive data is further reduced.

Drawings

Fig. 1A is a schematic flowchart of a first information processing method according to an embodiment of the present invention;

fig. 1B is a schematic flowchart of a second information processing method according to an embodiment of the present invention;

FIG. 2 is a flowchart illustrating a third information processing method according to an embodiment of the present invention;

FIG. 3 is a flowchart illustrating a fourth information processing method according to an embodiment of the present invention;

fig. 4 is a flowchart illustrating a fifth information processing method according to an embodiment of the present invention;

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

FIG. 6 is a schematic structural diagram of another information processing apparatus according to an embodiment of the present invention;

FIG. 7 is a diagram illustrating 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;

FIG. 9 is a flowchart illustrating a fourth information processing method according to an embodiment of the present invention;

FIG. 10 is a flowchart illustrating a fifth information processing method according to an embodiment of the present invention;

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

Detailed Description

The technical solution of the present invention is further described in detail with reference to the drawings and the specific embodiments of the specification.

The first embodiment is as follows:

as shown in fig. 1A, an information processing method applied in a first entity includes:

step S110: 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);

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

step S131: 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 first entity may be an open Capability Exposure Function (SCEF) entity. The server may be an application server; the second entity may be a subscriber subscription database (SPR).

In this embodiment, the first message is provided by the server, and the first message at least carries a message type, a service feature, and a first rule. The service characteristics include at least one of a service identifier, a Uniform Resource Locator (URL), an Internet Protocol (IP) address, a service sponsor identifier, and a service provider identifier. The service identifier may be various kinds of identification information of the first service, for example, identification information such as a service code number of the first service identifier. The service IP address may be an IP address of a server providing the service. The server may be the server in step S110, and may be referred to as an application server. The service sponsor identifier and the service provider identifier may be an IP address, a Media Access Control (MAC) address, a domain name address, a server name, or the like. Of course, the service feature may also include other identifiers capable of indicating the first service provider.

The first rule may comprise a business policy rule; the service characteristic rule comprises at least one of a service charging rule and a service quality QoS rule. The service charging rule can be used for indicating service charge payment scheme, payment mode, unit price and other related charging information. The quality of service rule is used for indicating the quality of service of the first service, such as a parameter of required time-delay. The service charging rules indicate a handover payer. For example, the configuration instruction is used to instruct the payer to switch charging, such as instructing the payer, instructing a certain payer to pay time period or paying proportion of each payer, and other various charging related information.

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 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; the first time is the time when the server forms the first message. In this embodiment, the UE identifier may be an International Mobile Equipment Identity (IMEI) of the UE, or may be a communication identifier of the UE. The communication identifier may be a mobile phone number or the like. At this time, the UE identity is an identity of the UE applying the first service.

The server may determine whether the UE applying the first service is connected to the server according to the first message formed by the server, and then determine the message type according to a connection state with the UE, so that the first entity may determine whether to send the first message to the second entity or the third entity according to the message type.

As a further improvement of the present embodiment,

as shown in fig. 1B, the method further comprises:

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

step S123: 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 if the first message is judged to be a rule setting message, the first entity directly sends the first message to a third entity, wherein the third entity can 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 business rule. For example, if the first rule comprises a QoS rule, then both the second rule and the third rule may comprise 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 may be one of the generation bases of the third rule. In a specific implementation process, the third rule may be directly used to perform operations such as quality control and charging processing on the UE accessing the first service.

In this embodiment, the first message may be a message of UE granularity, or may be a message of service granularity; correspondingly, the first service rule may be a rule of UE granularity, or may be a rule of service granularity. The second rule may also be a rule of UE granularity or a rule of traffic granularity. The third rule is typically a UE-granular rule.

When the first rule is a rule of service granularity, the first entity only needs to receive one first message, and when the second entity or the third entity installs or updates the rule of the whole service for the first service corresponding to the service feature carried in the first message. In this way, the server can configure the second rule and the third rule corresponding to all UEs applying the first service by only sending one first message to the first entity. At this time, the first message typically does not include the UE identity of the UE to which the first service is applied.

Example two:

as shown in fig. 2, the present embodiment provides an information processing method applied in a first entity, where the method includes:

step S210: 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);

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

In this embodiment, the first entity, the third entity, the first message, the first rule, and the third rule may all refer to embodiment one, which is not repeated here. In short, the information processing method according to this embodiment can simply and conveniently 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 the first message needs to be sent to a third entity.

Example three:

as shown in fig. 3, the present embodiment provides an information processing method applied to a second entity, including:

step S310: receiving the 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);

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

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

The information processing method provided in this embodiment is a method applied to a second entity, where the second entity may be the aforementioned subscriber 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 a first message sent by a first entity, where the first message may be a first message provided by a server, such AS an application server AS, forwarded by the first entity. The first message may be formed, the information content, and the like, and is not repeated here.

In step S320, a second rule of the first service corresponding to the service feature is installed or updated according to the first rule. The second rule here is a rule stored in the second entity. Typically, the content included in the second rule is identical to the content included in the first rule. The second rule is generated according to the first rule. Here, the first rule may be a rule of traffic granularity or a rule of UE granularity. The second rule may also be a traffic-granularity or UE-granularity rule.

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

There are various implementation manners of the step S330, and specifically, several optional manners are provided as follows:

the first alternative is as follows:

the first message further comprises a User Equipment (UE) identity; the UE identity is the identity of the first UE. The step S330 may include: 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 currently connected to a network; sending the second rule to the third entity when the first UE is currently connected to a network. As the method in the first embodiment, the first message may be formed at a first time, and in this embodiment, the current time of the step S330 may be a second time, and the second time is different from the current time. In this embodiment, the second entity may determine whether a first UE applying the first service at the current time is connected to a network, where the connection to the network may be whether the UE is connected to the network through a communication interface of the UE, and the third entity may perform a session with the UE through the network, for example, the UE may not be connected to the network when the UE is powered off or a battery is unplugged; and if the UE is started and is 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 maintains a database indicating whether the UE is connected to the network at the current time, and the second entity can simply know whether the first UE is online at the current time by querying the database maintained by the second entity. Specifically, if the second entity is the SPR, the SPR maintains data indicating whether each UE subscribed to the network is connected to the network at the current time.

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

When sending the second rule to the third entity in step S330, the method may include: and the UE identifier of the first UE connected to the network at the current moment is sent to the third entity, so that the third entity can conveniently carry out conversation with the UE according to the UE identifier and set the third rule.

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

storing the second rule when the first UE is not currently connected to a network. The rules are stored such that the third entity is sent again when the first UE is waiting for a connection to the network again, and the third entity performs the installation and configuration of the third rules by a connection with the UE.

The second option is:

the step S330 may include:

In this embodiment, the second entity does not determine whether the UE is connected to the network at the current time, in this embodiment, a third entity related to the first service is queried according to the service feature, and after the third entity related to the first service is queried, the second rule and the service feature are sent to the corresponding third entity. The third entity may be a PCRF entity, and thus the entity involved in the third service installs or updates the third rule according to the service feature rule and the service granularity.

It is worth noting that: the installation and updating of the rules according to the service granularity can comprise the service granularity configuration of the second rule and the installation and updating of the service granularity of the third rule. For example, when the M UEs apply the first service, in step S330, when performing the second rule configuration, the second rules of all the first services matching the service features are found according to the service features, and the second rules are updated uniformly according to the first rules. And if the second rule of the first service is not stored in the second entity at present, directly taking the service characteristics as an identifier, configuring the second rule of the first service to form a second rule, and then processing the second rule by using the second rule no matter which UE or which UE uses the first service. Typically the second rule may not have an identity of the UE stored. The above-described configuration of rules also applies to the configuration of the third rule at traffic granularity.

Example four:

as shown in fig. 4, an information processing method applied in a server includes:

step S410: 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);

step S420: 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.

In this embodiment, the server forms a first message, where the first message includes a message type, and in this embodiment, the type may include a rule configuration message and a rule setting message.

For detailed definitions of the service characteristics and the first rule, please refer to the corresponding parts in embodiment one, which is not repeated here.

In this embodiment, the step S420 sends the first message to a first entity, where the first entity may be an SCEF entity as described in embodiment one, and the message type is used for whether the first entity sends the first message to a second entity or sends the first message to the second entity.

The first message may be a rule installation or update message of a service granularity, or may also be a rule installation or update message of a UE granularity, and a rule of a service granularity may be sent by one first message, so that the second entity and the third entity update the second rule and the third rule corresponding to the UE applying the first service. Of course, the first message may also be a rule installation or update message of UE granularity, and at this time, the first message may include a service granularity 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 service. The detailed content of the service features can be seen in embodiment one. In short, in this embodiment, the message type is added to the first message, so that the first entity can determine the receiver receiving the first message conveniently, and the method has the characteristic of simple and convenient implementation.

Further, the method comprises:

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; 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; the first message further includes a UE identity of the first UE. In this embodiment, the first time is a time when the first message is formed, and the server may select the first UE by detecting a currently established connection thereof, and load a UE identity of the first UE in the first message. Typically, the first message is a rule installation or update message of UE granularity.

Example five:

as shown in fig. 5, the present embodiment provides an information processing apparatus applied to a first entity, where the first entity includes:

a first receiving unit 110, configured to receive 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);

a first determining unit 120, configured to determine 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; 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 first entity may be, but is not limited to, an 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. 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 herein may include a wired interface, which may include a cable interface or a fiber optic cable interface, or a wireless interface. The wireless interface may include a transceiver antenna, or the like.

The first determining 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 rule formation by specifying execution of code. The application specific integrated circuit may complete the formation of the second rule by transmission of an electrical signal.

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 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.

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 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; the first time is the time when the server forms the first message.

Further, the service characteristics include at least one of a service identifier, a service uniform resource address, a service network protocol IP address, a service sponsor identifier, and a service provider identifier. 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.

Example six:

as shown in fig. 6, in the first entity provided in this embodiment, the first entity includes:

a second receiving unit 210, configured to receive 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);

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

a second sending unit 230, 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 first entity in this embodiment may have the same corresponding 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 embodiment, and the second sending unit 230 may correspond to the first sending unit 130 in the foregoing embodiment; the second determining unit 220 may correspond to the second determining unit in the foregoing embodiments. Details of the first service and the first message may be found in the foregoing embodiments. In summary, the present embodiment provides a first entity, which is capable of determining whether to send a first message to a third entity according to the message type.

Example seven:

as shown in fig. 7, the present embodiment provides an information processing apparatus applied to a second entity, including:

a third receiving unit 310, configured to receive the first message sent by the 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);

a processing unit 320, configured to install or update a 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;

The second entity may be SPR. The second entity may be applicable 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 herein may include a wired interface, which may include a cable interface or a fiber optic cable interface, or a wireless interface. The wireless interface may include a transceiver antenna, or the like.

The processing unit 320 may include a processor or processing circuitry, which 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 rule formation by specifying execution of code. The application specific integrated circuit may complete the formation of the second rule by transmission of an electrical signal.

Specifically, AS described in this embodiment, the third receiving unit 310 may be configured to receive a first message formed in a first state by an AS forwarded by an SCEF entity, where the first message does not include a UE identity of a UE to which the first service is applied. In this embodiment, the detailed descriptions of the first state, the first message, the service feature, the configuration instruction, and the like may be referred to as implementation one, and are not repeated here.

The structure of the second entity is varied, and several alternative structures are provided below:

an optional structure one:

the first message further comprises a User Equipment (UE) identity; the UE identification is an identification of a 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, determining whether the 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 time.

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. The storage unit in this embodiment may include various types of storage media, such as a Random Access Memory (RAM), a read-only memory (ROM), or a Flash memory (Flash), and optionally a non-transitory storage medium. The stored second rule may be sent to the third entity after the corresponding UE connects to the network. Generally, in the first alternative structure, the third sending unit 330 is further configured to send the UE identity 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 or update the third rule.

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, 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. 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 open 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 short, the embodiment provides a second entity, which can simply, conveniently and quickly generate a second rule and send the second rule to a third entity.

Example eight:

as shown in fig. 8, the present embodiment provides a server, including:

a forming unit 410, configured to form a first message, where the first message includes a message type, a service feature, and a first rule corresponding to the service feature; the service characteristic is used for indicating a first service applied by User Equipment (UE);

a fifth sending unit 420, configured to send the first message to the 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 server described 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, and the structure of the processor or the processing circuit, the first message, the specific structure corresponding to the first entity to the third entity, and the differences between the first rule and the third rule may all be referred to in the foregoing embodiments, which is not repeated here.

Further, the server includes:

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

Several specific examples are provided below in connection with any of the embodiments described above:

example one:

as shown in fig. 9, the present example provides an information processing method including:

step S1: transmission of a first message; the AS sends a first message to the SCEF entity, wherein the first message comprises service characteristics and a first rule of a certain service, which are installed or updated according to a second rule. The service characteristics may include information such AS an IP address of the AS or a URL of the service. The first rule may be used to indicate a payer for handover charging.

Step S2: authentication; the SCEF entity identifies whether the AS is entitled to update or install the second rule for the service.

Step S3: it is determined whether the UE applying the first service is connected to the network, and if so, the process proceeds to step S4, and the process does not proceed to step S6. Step S3 is performed after the authentication is passed. And the first service is a service corresponding to the service characteristic.

Step S4: a first UE applying a first service is connected to a network, and a UE identity 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: and the UE which does not apply the first service is connected to the network, and the first message is stored.

Step S7: and installing or updating the second rule of the first service according to the first message.

Step S8: a second rule and a transmission of the first UE identity. 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 comprises two parts: a first part: the SPR sends a response message to the SCEF entity; a second part: the SCEF entity sends a response message to the AS. In a specific implementation, the transmission of the response message may be that the response message is sent to the AS after the SCEF entity sends the first message to the SPR.

Example two:

as shown in fig. 10, the present example provides an information processing method including:

step S11: transmission of a first message; the AS sends a first message to the SCEF entity, wherein the first message comprises service characteristics and a first rule of a certain service, which are installed or updated according to a second rule. The service characteristics may include information such AS an IP address of the AS or a URL of the service. The first rule may be used to indicate a payer for handover charging.

Step S12: authentication; the SCEF entity identifies whether the AS is entitled 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 performed after the authentication is passed. And the first service is a service corresponding to the service characteristic.

Step S14: and installing or updating the second rule for the first service.

Step S15: determining a second UE identity of a second UE which applies the first service and is currently connected to the network;

step S16: a second rule and a transmission of a second UE identity.

Step S17: and installing and updating a third rule for the second UE according to the second rule.

Step S18: a second rule is stored for a third UE that applies the first traffic and is not currently connected to the network.

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

Example three:

as shown in fig. 11, the present example provides an information processing method including:

step S21: transmission of a first message; the AS sends a first message to the SCEF entity, wherein the first message comprises service characteristics and a first rule of a certain service, which are installed or updated according to a second rule. The service characteristics may include information such AS an IP address of the AS or a URL of the service. The first rule may be used to indicate a payer for handover charging.

Step S22: authentication; the SCEF entity identifies whether the AS is entitled 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 performed after the authentication is passed. And the first service is a service corresponding to the service characteristic.

Step S24: and installing and updating the second rule for the first service.

Step S25: and determining a PCRF entity related to the first service.

Step S26: second rules and transmission of traffic characteristics. The SPR here sends the second rules and traffic characteristics to the PCRF entity.

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

It should be noted that in this application, the AS may also be referred to AS SCS, which may also be referred to AS UCD, the SCS is an abbreviation of Services Capability Server, and the corresponding chinese is a service Capability Server. The UCD is an abbreviation of UserData conversion, and Chinese is also a user database.

In the several embodiments provided in the present application, it should be understood that the disclosed apparatus and method may be implemented in other ways. The above-described device embodiments are merely illustrative, for example, the division of the unit is only a logical functional division, and there may be other division ways in actual implementation, such as: multiple units or components may be combined, or may be integrated into another system, or some features may be omitted, or not implemented. In addition, the coupling, direct coupling or communication connection between the components shown or discussed may be through some interfaces, and the indirect coupling or communication connection between the devices or units may be electrical, mechanical or other forms.

The units described as separate parts may or may not be physically separate, and parts displayed as units may or may not be physical units, that is, may be located in one place, or may be distributed on a plurality of network units; some or all of the units can be selected according to actual needs to achieve the purpose of the solution of the embodiment.

In addition, all the functional units in the embodiments of the present invention may be integrated into one processing module, or each unit may be separately used as one unit, or two or more units may be integrated into one unit; the integrated unit can be realized in a form of hardware, or in a form of hardware plus a software functional unit.

Those of ordinary skill in the art will understand that: all or part of the steps for implementing the method embodiments may be implemented by hardware related to program instructions, and the program may be stored in a computer readable storage medium, and when executed, the program performs the steps including the method embodiments; and the aforementioned storage medium includes: a mobile storage device, a Read-Only Memory (ROM), a Random Access Memory (RAM), a magnetic disk or an optical disk, and other various media capable of storing program codes.

The above description is only for the specific embodiments of the present invention, but the scope of the present invention is not limited thereto, and any person skilled in the art can easily conceive of the changes or substitutions within the technical scope of the present invention, and all the changes or substitutions should be covered within the scope of the present invention. Therefore, the protection scope of the present invention shall be subject to the protection scope of the appended claims.

Claims

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;

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:

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:

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;

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;

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;

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:

10. The method of claim 7,

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

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;

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;

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;

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,

17. The apparatus of claim 13,

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 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;

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;

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:

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:

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.