CN101742463B - Method, transmitting equipment and receiving equipment for realizing function of white name list - Google Patents
Method, transmitting equipment and receiving equipment for realizing function of white name list Download PDFInfo
- Publication number
- CN101742463B CN101742463B CN2009102611297A CN200910261129A CN101742463B CN 101742463 B CN101742463 B CN 101742463B CN 2009102611297 A CN2009102611297 A CN 2009102611297A CN 200910261129 A CN200910261129 A CN 200910261129A CN 101742463 B CN101742463 B CN 101742463B
- Authority
- CN
- China
- Prior art keywords
- application layer
- layer information
- white list
- fui
- information
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Expired - Fee Related
Links
- 238000000034 method Methods 0.000 title claims abstract description 41
- 238000001914 filtration Methods 0.000 claims description 35
- 230000004913 activation Effects 0.000 claims description 31
- 230000003213 activating effect Effects 0.000 claims description 4
- 238000010586 diagram Methods 0.000 description 4
- 230000005540 biological transmission Effects 0.000 description 1
- 238000005516 engineering process Methods 0.000 description 1
- GVVPGTZRZFNKDS-JXMROGBWSA-N geranyl diphosphate Chemical compound CC(C)=CCC\C(C)=C\CO[P@](O)(=O)OP(O)(O)=O GVVPGTZRZFNKDS-JXMROGBWSA-N 0.000 description 1
- 238000012986 modification Methods 0.000 description 1
- 230000004048 modification Effects 0.000 description 1
- 230000003287 optical effect Effects 0.000 description 1
- 230000008569 process Effects 0.000 description 1
- 238000006467 substitution reaction Methods 0.000 description 1
Images
Landscapes
- Information Transfer Between Computers (AREA)
- Computer And Data Communications (AREA)
Abstract
The invention provides a method, transmitting equipment and receiving equipment for realizing the function of a white name list. The method comprises the following steps: receiving an FUI transmitted by an OCS; acquiring application layer information of a server which belongs to the white name list according to the FUI; performing DPI processing on a service message transmitted by user equipment to obtain the application layer information of the service message; and when the application layer information of the service message matches the application layer information of the server which belongs to the white name list, allowing the user equipment to access the server corresponding to the application layer information of the service message. The embodiment of the invention can solve the problem that the white list name may not be deployed effectively when the white name list is deployed according to an IP address, thereby realizing the effective deployment of the function of the white name list.
Description
Technical Field
The embodiment of the invention relates to an online charging technology, in particular to a method for realizing a white list function, a sending device and a receiving device.
Background
A Charging Trigger Function (CTF) entity is a logical entity defined by the third Generation Partnership Project (3 GPP), and assumes functions of detecting, collecting, recording and reporting Charging information in a Charging related network element. In the Online Charging application, the CTF entity may control user service access according to a quota issued by an Online Charging System (OCS). RFC4006 defines that when the OCS detects that the user has the last quota remaining, it sends a white list to the CTF entity through a Final Unit Indication (FUI) cell, which indicates that the CTF entity controls the user to normally access the servers in the white list and blocks access to other servers. The format of the FUI cell is as follows:
Final-Unit-Indication::＝<AVP Header：430>
{Final-Unit-Action}＝2(RESTRICT_ACCESS)
alternatively, { Final-Unit-Action } - [ 1 ] (REDECT)
*[Restriction-Filter-Rule]
*[Filter-Id]
[Redirect-Server]
When the Final-Unit-Action value is RESTRICT _ ACCESS or REDIRECT, it indicates that the OCS instructs the CTF entity to use the white list function. The white list can be dynamically issued by a "prompt-Filter-Rule" Attribute Value Pair (AVP) in the FUI, or can activate a Filter Rule (FilterRule) locally configured by the CTF entity by the Filter-Id. Whether "recovery-Filter-Rule" AVP or locally configured Filter Rule, the whitelist contains only layer 3/4 information of the server that allows user service access, such as source and destination IP addresses, Protocol numbers, source and destination port numbers, Transmission Control Protocol (TCP) identification, etc.
In the process of implementing the invention, the inventor finds that the prior art has at least the following problems: because the IP address of the server can be dynamically changed, and the operator cannot know the changed IP address of a certain server at the next moment, the operator cannot issue an effective white list when the IP address is dynamically changed, so that the white list function cannot be deployed.
Disclosure of Invention
The embodiment of the invention provides a method for realizing a white list function, a sending device and a receiving device, which can enable an operator to issue an effective white list and realize the deployment of the white list function.
In one aspect, an embodiment of the present invention provides a method for implementing a white list function, including:
receiving a final unit indication FUI sent by an Online Charging System (OCS), and acquiring application layer information of a server belonging to a white list according to the FUI;
deep message analysis DPI processing is carried out on a service message sent by user equipment, and application layer information of the service message is obtained;
and when the application layer information of the service message is matched with the application layer information of the server belonging to the white list, allowing the user equipment to access the server corresponding to the application layer information of the service message.
In another aspect, an embodiment of the present invention provides a method for implementing a white list function, including:
adding first information into a final unit indication FUI, wherein the first information is used for enabling a Charging Trigger Function (CTF) entity to acquire application layer information of a server belonging to a white list;
and sending the FUI to a CTF entity so that the CTF entity performs application layer information matching according to the FUI to realize a white list function.
In one aspect, an embodiment of the present invention provides a receiving device, including:
the system comprises an acquisition module, a processing module and a processing module, wherein the acquisition module is used for receiving a final unit indication FUI sent by an Online Charging System (OCS) and acquiring application layer information of a server belonging to a white list according to the FUI;
the processing module is used for carrying out deep message analysis DPI processing on a service message sent by user equipment to obtain application layer information of the service message;
and the matching module is used for allowing the user equipment to access the server corresponding to the application layer information of the service message when the application layer information of the service message is matched with the application layer information of the server belonging to the white list.
In another aspect, an embodiment of the present invention provides a sending apparatus, including:
an adding module, configured to add first information to the last unit indication FUI, where the first information is used to enable a charging trigger function CTF entity to obtain application layer information of a server belonging to a white list;
and the sending module is used for sending the FUI to a CTF entity so that the CTF entity performs application layer information matching according to the FUI to realize a white list function.
According to the technical scheme, the embodiment of the invention can avoid the problem that the effective white list cannot be deployed due to the dynamically changed IP address by acquiring the application layer information of the server belonging to the white list, and realize the deployment of the white list function.
Drawings
In order to more clearly illustrate the technical solutions in the embodiments of the present invention, the drawings needed to be used in the embodiments are briefly introduced below, and it is obvious that the drawings in the following description are some embodiments of the present invention, and it is obvious for those skilled in the art to obtain other drawings based on these drawings without inventive labor.
FIG. 1 is a schematic flow chart of a method according to a first embodiment of the present invention;
FIG. 2 is a schematic flow chart of a method according to a second embodiment of the present invention;
FIG. 3 is a schematic flow chart of a method according to a third embodiment of the present invention;
FIG. 4 is a schematic flow chart of a method according to a fourth embodiment of the present invention;
FIG. 5 is a schematic flow chart of a method according to a fifth embodiment of the present invention;
FIG. 6 is a schematic flow chart of a method according to a sixth embodiment of the present invention;
fig. 7 is a schematic structural diagram of a receiving apparatus according to a seventh embodiment of the present invention;
fig. 8 is a schematic structural diagram of a transmitting device according to an eighth embodiment of the present invention.
Detailed Description
In order to make the objects, technical solutions and advantages of the embodiments of the present invention clearer, the technical solutions in the embodiments of the present invention will be clearly and completely described below with reference to the drawings in the embodiments of the present invention, and it is obvious that the described embodiments are some, but not all, embodiments of the present invention. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present invention.
Fig. 1 is a schematic flow chart of a method according to a first embodiment of the present invention, which includes:
step 11: and the CTF entity receives the FUI sent by the OCS and acquires the application layer information of the server belonging to the white list according to the FUI.
The application layer information in the embodiment of the present invention may be an application layer Protocol, for example, but not limited to, a hypertext Transfer Protocol (HTTP) or a Real Time Streaming Protocol (RTSP), and may also be other application layer information, for example, but not limited to, a Uniform Resource Locator (URL), a user-agent field, or a method field.
Taking the URL as an example, the FUI may carry the URL of the server belonging to the white list, and at this time, the CTF entity may directly obtain the URL of the server belonging to the white list in the FUI; or, the FUI may also carry activation information, where the activation information is used to activate a filtering rule that is configured in advance in the CTF entity and includes a URL of a server belonging to a white list, and at this time, the CTF entity may obtain the URL of the server belonging to the white list from the filtering rule.
Since the URL of the server is fixed, rather than dynamically changing as with an IP address, an efficient white list can be derived from the URL.
Step 12: the CTF entity performs deep packet analysis (DPI) processing on a service packet sent by the user equipment to obtain application layer information of the service packet.
The DPI is a deep parsing protocol, and can obtain application layer information of the packet. Since the general message parsing can only obtain the five-tuple of the message: the source and destination IP addresses, source and destination port numbers and protocol numbers, DPI is required to obtain high-level information.
Step 13: and when the application layer information of the service message is matched with the acquired application layer information of the server belonging to the white list, the CTF entity allows the user equipment to access the server corresponding to the application layer information of the service message.
That is, when the application layer information of the service packet belongs to the application layer information obtained according to the FUI, the user is allowed to access the server belonging to the white list, thereby implementing the white list function.
In this embodiment, by acquiring the application layer information of the server belonging to the white list and by matching the application layer information of the packet with the application layer information of the server in the white list, the white list function can be effectively deployed.
The first embodiment is described from the CTF entity side, and correspondingly, from the OCS side, as follows:
fig. 2 is a schematic flow chart of a method according to a second embodiment of the present invention, which includes:
step 21: the OCS adds first information to the FUI, where the first information is used for enabling the CTF entity to acquire application layer information of the server belonging to the white list.
The first information may be information of an application layer including a server belonging to a white list; alternatively, the first information may be activation information for activating a filtering rule of an application layer of a server belonging to a white list, which is pre-configured in the CTF entity.
Step 22: and the OCS sends the FUI to the CTF entity so that the CTF entity performs application layer information matching according to the FUI to realize a white list function. The CTF entity can acquire application layer information of a server belonging to a white list according to the first information in the FUI, and further, the application layer information of the service message is matched with the acquired application layer information through the service message sent by the DPI user, so that the white list function is realized.
In this embodiment, the information of the application layer of the server that enables the CTF entity to obtain the white list is carried in the FUI, so that the CTF entity can perform corresponding matching according to the information of the application layer, thereby implementing effective deployment of the white list function.
During implementation, the FUI can directly carry application layer information of a server belonging to a white list; the FUI may also carry activation information, and the CTF entity pre-configures application layer information of the server belonging to the white list, so that the CTF entity obtains the pre-configured application layer information of the server belonging to the white list after receiving the activation information. Whether the preset rules are directly carried or activated, the preset rules can be added or expanded. The following are described separately:
fig. 3 is a schematic flow chart of a method according to a third embodiment of the present invention, and this embodiment takes as an example that the FUI carries application layer information of a server belonging to a white list, and the application layer information is carried by an extended AVP, such as "retrieval-Filter-Rule". Referring to fig. 3, the present embodiment includes:
step 31: the OCS carries the application layer information of the servers belonging to the white list in the extended AVP in the FUI, for example, in the extended recovery-Filter-Rule. The OCS then carries the AVP "recovery-Filter-Rule" described above in FUI. Further, an AVP "Final-Unit-Action" indicating that the CTF entity uses the white list function may also be carried in the FUI.
Specifically, the format of FUI is as follows:
Final-Unit-Indication::＝<AVP Header：430>
{Final-Unit-Action}＝2(RESTRICT_ACCESS)
alternatively, { Final-Unit-Action } - [ 1 ] (REDECT)
*[Restriction-Filter-Rule]
[Redirect-Server]
The result-Filter-Rule includes application layer information of a server belonging to the white list, and takes the application layer information as a URL as an example, for example, the result-Filter-Rule includes URL-1 and URL-2.
Step 32: and the OCS issues the FUI to the CTF entity.
Step 33: the CTF entity obtains the application layer information of the server belonging to the white list from the extended AVP of the FUI, for example, the retrieval-Filter-Rule. For example, URL-1 and URL-2 are obtained.
The CTF entity may first know that a white list function needs to be used according to the Final-Unit-Action in the FUI, and then perform a step of obtaining the URL of the server belonging to the white list from the recovery-Filter-Rule of the FUI.
Step 34: and the CTF entity receives the service message sent by the user equipment, and performs DPI on the received service message to obtain the application layer information of the service message.
Step 35: the CTF entity determines whether the application layer information of the received service packet matches the application layer information obtained from the FUI, if so, step 36 is executed, otherwise, step 37 is executed.
For example, when the application layer information of a service packet is URL-1, the determination result is obtained as a match. When the application layer information of a service message is URL-2, the judgment result is also matched; and when the application layer information of a service message is neither URL-1 nor UR1-2, the judgment result is obtained as mismatching.
Step 36: and allowing the service message to access the server by the CTF entity.
Step 37: and the CTF entity prevents the service message from accessing the server. Wherein, when the value of the Final-Unit-Action is REDECT, the redirection is needed to be further carried out.
In this embodiment, the application layer information of the server belonging to the white list is carried in the FUI by the AVP "retrieval-Filter-Rule" displayed by the extension. In this embodiment, the application layer information of the server belonging to the white list is carried in the FUI, so that the effective white list can be issued, and the white list can be deployed.
Fig. 4 is a flowchart illustrating a method according to a fourth embodiment of the present invention, in which the FUI carries application layer information of a server belonging to a white list, and the application layer information is carried by adding an AVP. Referring to FIG. 4, the present embodiment includes
Step 41: the OCS carries the URL of the server belonging to the white list in the newly added AVP in the FUI. Meanwhile, the OCS may also carry AVP "Final-Unit-Action" indicating that the CTF entity uses the white list function in the FUI.
Specifically, the format of FUI is as follows:
Final-Unit-Indication::＝<AVP Header：430>
{Final-Unit-Action}＝2(RESTRICT_ACCESS)
alternatively, { Final-Unit-Action } - [ 1 ] (REDECT)
*[Restriction-Filter-Rule]
*[Application-Information]
[Redirect-Server]
The Application-Information includes Application layer Information of the servers belonging to the white list, where the Application layer Information may be an Application layer protocol, such as but not limited to HTTP or RTSP, or may be other Application layer Information, such as but not limited to URL, user-agent field, or method field. For example, the Application-Information includes URL-1 and URL-2.
Step 42: and the OCS issues the FUI to the CTF entity.
Step 43: the CTF entity obtains Application layer Information of the servers belonging to the white list from the newly added AVP, e.g., "Application-Information", in the FUI. For example, URL-1 and URL-2 are obtained.
The CTF entity may first know that the white list function needs to be used according to the Final-Unit-Action in the FUI, and then perform the step of obtaining the application layer information of the server belonging to the white list from the FUI.
Step 44: and the CTF entity receives the service message sent by the user equipment, and performs DPI on the received service message to obtain the application layer information of the service message.
Step 45: the CTF entity determines whether the application layer information of the received service packet matches the application layer information obtained from the FUI, if so, step 46 is executed, otherwise, step 47 is executed.
For example, when the application layer information of a service packet is URL-1, the determination result is obtained as a match. When the application layer information of a service message is URL-2, the judgment result is also matched; and when the application layer information of a service message is neither URL-1 nor UR1-2, the judgment result is obtained as mismatching.
Step 46: and allowing the service message to access the server by the CTF entity.
Step 47: and the CTF entity prevents the service message from accessing the server. Wherein, when the value of the Final-Unit-Action is REDECT, the redirection is needed to be further carried out.
In this embodiment, the Application layer Information of the server belonging to the white list is carried in the FUI through the newly added AVP "Application-Information". In this embodiment, the application layer information of the server belonging to the white list is carried in the FUI, so that the effective white list can be issued, and the white list can be deployed.
Fig. 5 is a schematic flowchart of a method according to a fifth embodiment of the present invention, in which the activation information carried in the FUI is taken as an example of an AVP extended from an existing AVP. At this time, the filtering rule activated by the activation information is an extension of the existing filtering rule. Referring to fig. 5, the present embodiment includes:
step 51: the OCS carries activation information in the FUI. Meanwhile, the OCS may also carry AVP "Final-Unit-Action" indicating that the CTF entity uses the white list function in the FUI.
Specifically, the format of FUI is as follows:
Final-Unit-Indication::＝<AVP Header：430>
{Final-Unit-Action}＝2(RESTRICT_ACCESS)
alternatively, { Final-Unit-Action } - [ 1 ] (REDECT)
*[Filter-Id]
[Redirect-Server]
Wherein, the Filter-Id is activation information.
Step 52: and the OCS issues the FUI to the CTF entity.
Step 53: and the CTF entity acquires a pre-configured extended filtering rule according to the activation information carried in the FUI, wherein the filtering rule comprises application layer information of a server belonging to a white list. For example, the filter rules include URL-1 and URL-2.
The CTF entity may first know that the white list function needs to be used according to the Final-Unit-Action in the FUI, and then perform the above step of obtaining the filtering rule according to the activation information.
Step 54: the CTF entity gets the application layer information of the servers belonging to the white list from the extended filtering rules, e.g. URL-1 and URL-2.
Step 55-58: corresponding to steps 34-37.
In this embodiment, the preset filtering rule includes the application layer information of the server belonging to the white list by expanding the existing filtering rule. Therefore, when the Filter rule is activated by using the AVP "Filter-Id", the application layer information of the white-listed server can be obtained from the Filter rule. In this embodiment, the FUI carries activation information for triggering the CTF entity to acquire application layer information of a server belonging to a white list, which is configured in advance, so that an effective white list can be issued, and the white list can be deployed.
Fig. 6 is a flowchart illustrating a method according to a sixth embodiment of the present invention, in which the embodiment takes the activation information carried in the FUI as an example of an added AVP. At this time, the filter rule activated by the activation information is the newly added filter rule. Referring to fig. 6, the present embodiment includes:
step 61: the OCS carries the newly added activation information in the FUI. Meanwhile, the OCS may also carry AVP "Final-Unit-Action" indicating that the CTF entity uses the white list function in the FUI.
Specifically, the format of FUI is as follows:
Final-Unit-Indication::＝<AVP Header：430>
{Final-Unit-Action}＝2(RESTRICT_ACCESS)
alternatively, { Final-Unit-Action } - [ 1 ] (REDECT)
*[Filter-Id]
*[Rule-Id]
[Redirect-Server]
Wherein, Rule-Id is newly added activation information.
Step 62: and the OCS issues the FUI to the CTF entity.
And step 63: and the CTF entity acquires a pre-configured filtering rule according to the newly added activation information carried in the FUI, wherein the filtering rule comprises application layer information of the server belonging to the white list. For example, the filter rules include URL-1 and URL-2.
The CTF entity may first know that the white list function needs to be used according to the Final-Unit-Action in the FUI, and then perform the above step of obtaining the filtering rule according to the activation information.
Step 64: the CTF entity gets the application layer information of the servers belonging to the white list from the filter rules, e.g. URL-1 and URL-2.
Step 65-68: corresponding to steps 34-37.
In this embodiment, the filter Rule including the application layer information of the server belonging to the white list is activated by the newly added AVP "Rule-Id" to obtain the application layer information of the server belonging to the white list. In this embodiment, the FUI carries activation information for triggering the CTF entity to acquire application layer information of a server belonging to a white list, which is configured in advance, so that an effective white list can be issued, and the white list can be deployed.
Fig. 3 to 6 respectively show four implementation manners of an extended AVP, a newly added AVP, an extended filter rule, and a newly added filter rule, and it is understood that, in practical applications, the implementation manners may be combined with each other or with an existing implementation manner, and a server belonging to a white list may be accessed as long as one of the conditions is satisfied. For example, the FUI carries both the extended trigger-Filter-Rule and the extended Filter-Id, and when the application layer information in a certain service message is the same as the application layer information in the extended trigger-Filter-Rule, or the application layer information in the Filter Rule activated by the extended Filter-Id is the same as the application layer information in the extended Filter-Id, the service message may access the corresponding server. For another example, the FUI carries both the newly added Application-Information and the existing response-Filter-Rule, and when the Application layer Information in a certain service message is the same as the Application layer Information in the extended Application-Information, or the IP address in the service message is the same as the IP address in the existing response-Filter-Rule, the service message may access the corresponding server.
Fig. 7 is a schematic structural diagram of a receiving device according to a seventh embodiment of the present invention, which includes an obtaining module 71, a processing module 72, and a matching module 73; the obtaining module 71 is configured to receive the FUI sent by the OCS, and obtain application layer information of a server belonging to a white list according to the FUI; the processing module 72 is configured to perform DPI processing on a service packet sent by a user equipment to obtain application layer information of the service packet; the matching module 73 is configured to allow the user equipment to access the server corresponding to the application layer information of the service packet when the application layer information of the service packet matches with the application layer information of the server belonging to the white list.
The obtaining module 71 may include a first unit 711 or a second unit 712; the first unit 711 is configured to directly obtain application layer information of a server belonging to a white list from the FUI; the second unit 712 is configured to obtain application layer information of a server belonging to a white list from the preconfigured filter rule after receiving activation information, which is carried in the FUI and used for activating the preconfigured filter rule.
The preset filtering rule is a filtering rule expanded from the existing filtering rule or a newly added filtering rule.
The application layer information may be an application layer protocol, such as, but not limited to, HTTP or RTSP, or other application layer information, such as, but not limited to, URL, user-agent field, or method field.
The specific functions of the modules may refer to method embodiments, and are not described in detail.
In this embodiment, by acquiring the application layer information of the server belonging to the white list and by matching the application layer information of the packet with the application layer information of the server in the white list, the white list function can be effectively deployed.
Fig. 8 is a schematic structural diagram of a transmitting device according to an eighth embodiment of the present invention, which includes an adding module 81 and a transmitting module 82; the adding module 81 is configured to add first information in the FUI, where the first information is used to enable the CTF entity to obtain application layer information of a server belonging to a white list; the sending module 82 is configured to send the FUI to the CTF entity, so that the CTF entity performs application layer information matching according to the FUI to implement a white list function.
Wherein the adding module 81 comprises a third unit 811 or a fourth unit 812; the third unit 811 is configured to add AVP containing application layer information of servers belonging to the white list in the FUI; the fourth unit 812 is configured to add activation information to the FUI, where the activation information is used to enable the CTF entity to obtain a pre-configured filtering rule, and the filtering rule includes application layer information of servers belonging to the white list.
The AVP containing the application layer information of the server belonging to the white list is an AVP expanded from the existing AVP or a newly added AVP. Or, the activation information is an AVP extended from an existing AVP, or a newly added AVP.
The application layer information may be an application layer protocol, such as, but not limited to, HTTP or RTSP, or other application layer information, such as, but not limited to, URL, user-agent field, or method field.
The specific functions of the modules may refer to method embodiments, and are not described in detail.
In this embodiment, the information of the application layer of the server that enables the CTF entity to obtain the white list is carried in the FUI, so that the CTF entity can perform corresponding matching according to the information of the application layer, thereby implementing effective deployment of the white list function.
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: various media that can store program codes, such as ROM, RAM, magnetic or optical disks.
Finally, it should be noted that: the above examples are only intended to illustrate the technical solution of the present invention, but not to limit it; although the present invention has been described in detail with reference to the foregoing embodiments, it will be understood by those of ordinary skill in the art that: the technical solutions described in the foregoing embodiments may still be modified, or some technical features may be equivalently replaced; and such modifications or substitutions do not depart from the spirit and scope of the corresponding technical solutions of the embodiments of the present invention.
Claims (16)
1. A method for implementing a white list function, comprising:
receiving a final unit indication FUI sent by an Online Charging System (OCS), and acquiring application layer information of a server belonging to a white list according to the FUI;
deep message analysis DPI processing is carried out on a service message sent by user equipment, and application layer information of the service message is obtained;
and when the application layer information of the service message is matched with the application layer information of the server belonging to the white list, allowing the user equipment to access the server corresponding to the application layer information of the service message.
2. The method of claim 1, wherein the obtaining application layer information of the servers belonging to the white list comprises:
directly acquiring application layer information of a server belonging to a white list from the FUI;
or,
and after receiving activation information carried in the FUI and used for activating a pre-configured filtering rule, acquiring application layer information of a server belonging to a white list from the pre-configured filtering rule.
3. The method of claim 2, wherein the pre-configured filtering rule is an extended filtering rule from an existing filtering rule or a newly added filtering rule.
4. The method according to any of claims 1-3, wherein the application layer information comprises: the hypertext transfer protocol HTTP, the real-time streaming protocol RTSP, the uniform resource locator URL, the user-agent field, or the method field.
5. A method for implementing a white list function, comprising:
adding first information into a final unit indication FUI, wherein the first information is used for enabling a Charging Trigger Function (CTF) entity to acquire application layer information of a server belonging to a white list;
and sending the FUI to a CTF entity so that the CTF entity acquires the application layer information of the server belonging to the white list according to the FUI and matches the application layer information of the server belonging to the white list with the application layer information of the service message to realize the white list function.
6. The method of claim 5, wherein adding the first information in the FUI comprises:
adding an Attribute Value Pair (AVP) containing application layer information of a server belonging to a white list into the FUI;
or,
adding activation information in the FUI, wherein the activation information is used for enabling the CTF entity to acquire application layer information of a white list server from a pre-configured filtering rule.
7. The method of claim 6,
the AVP containing the application layer information of the server belonging to the white list is an AVP expanded from the existing AVP or a newly added AVP;
or,
the activation information is an AVP extended from the existing AVP or a newly added AVP.
8. The method according to any of claims 5-7, wherein the application layer information comprises: the hypertext transfer protocol HTTP, the real-time streaming protocol RTSP, the uniform resource locator URL, the user-agent field, or the method field.
9. A receiving device, comprising:
the system comprises an acquisition module, a processing module and a processing module, wherein the acquisition module is used for receiving a final unit indication FUI sent by an Online Charging System (OCS) and acquiring application layer information of a server belonging to a white list according to the FUI;
the processing module is used for carrying out deep message analysis DPI processing on a service message sent by user equipment to obtain application layer information of the service message;
and the matching module is used for allowing the user equipment to access the server corresponding to the application layer information of the service message when the application layer information of the service message is matched with the application layer information of the server belonging to the white list.
10. The apparatus of claim 9,
the acquisition module comprises a first unit or a second unit;
the first unit is used for directly acquiring application layer information of a server belonging to a white list from the FUI;
the second unit is configured to obtain application layer information of a server belonging to a white list from the preconfigured filtering rule after receiving activation information carried in the FUI and used for activating the preconfigured filtering rule.
11. The apparatus of claim 10, wherein the pre-configured filtering rule is an extended filtering rule from an existing filtering rule or a newly added filtering rule.
12. The apparatus according to any of claims 9-11, wherein the application layer information comprises: the hypertext transfer protocol HTTP, the real-time streaming protocol RTSP, the uniform resource locator URL, the user-agent field, or the method field.
13. A transmitting device, comprising:
an adding module, configured to add first information to the last unit indication FUI, where the first information is used to enable a charging trigger function CTF entity to obtain application layer information of a server belonging to a white list;
and the sending module is used for sending the FUI to a CTF entity so that the CTF entity obtains the application layer information of the server belonging to the white list according to the FUI and matches the application layer information of the server belonging to the white list with the application layer information of the service message to realize the white list function.
14. The apparatus of claim 13,
the adding module comprises a third unit or a fourth unit;
the third unit is used for adding an attribute value pair AVP containing application layer information of a server belonging to a white list into the FUI;
the fourth unit is configured to add activation information to the FUI, where the activation information is used to enable the CTF entity to obtain a pre-configured filtering rule, and the filtering rule includes application layer information of a server belonging to a white list.
15. The apparatus of claim 14,
the AVP containing the application layer information of the server belonging to the white list is an AVP expanded from the existing AVP or a newly added AVP; or,
the activation information is an AVP extended from the existing AVP or a newly added AVP.
16. The apparatus according to any of claims 13-15, wherein the application layer information comprises: the hypertext transfer protocol HTTP, the real-time streaming protocol RTSP, the uniform resource locator URL, the user-agent field, or the method field.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN2009102611297A CN101742463B (en) | 2009-12-28 | 2009-12-28 | Method, transmitting equipment and receiving equipment for realizing function of white name list |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN2009102611297A CN101742463B (en) | 2009-12-28 | 2009-12-28 | Method, transmitting equipment and receiving equipment for realizing function of white name list |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN101742463A CN101742463A (en) | 2010-06-16 |
| CN101742463B true CN101742463B (en) | 2012-11-21 |
Family
ID=42465194
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN2009102611297A Expired - Fee Related CN101742463B (en) | 2009-12-28 | 2009-12-28 | Method, transmitting equipment and receiving equipment for realizing function of white name list |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN101742463B (en) |
Citations (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101208943A (en) * | 2005-06-20 | 2008-06-25 | 诺基亚西门子网络公司 | Controlling provision of services in a communications network |
-
2009
- 2009-12-28 CN CN2009102611297A patent/CN101742463B/en not_active Expired - Fee Related
Patent Citations (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101208943A (en) * | 2005-06-20 | 2008-06-25 | 诺基亚西门子网络公司 | Controlling provision of services in a communications network |
Also Published As
| Publication number | Publication date |
|---|---|
| CN101742463A (en) | 2010-06-16 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN110580256B (en) | Method, device and system for identifying application identification | |
| WO2017066359A1 (en) | Determining direction of network sessions | |
| EP3005660A1 (en) | Data aggregation | |
| WO2011060377A1 (en) | Method and apparatus for real time identification and recording of artifacts | |
| WO2009047065A4 (en) | Methods, apparatuses, system, and related computer program product for policy control | |
| CN106850568B (en) | Session aging method and device of multi-channel protocol | |
| CN104518968B (en) | The method and Transparent proxy server of a kind of Message processing | |
| CN108200158A (en) | Ask Transmission system, method, apparatus and storage medium | |
| EP3668043A1 (en) | Method for identifying encrypted data stream, device, storage medium, and system | |
| US20140101040A1 (en) | Method and apparatus for charging in a communication network | |
| CN102739811A (en) | Method and device of domain name resolution | |
| CN101325553B (en) | Method for ISCSI data to traverse NAT and inner network memory system | |
| CN107070719B (en) | Equipment management method and device | |
| US8296425B2 (en) | Method and system for lawful interception of internet service | |
| CN109309907B (en) | Method and device for charging flow and related equipment | |
| CN104184565B (en) | A kind of method and device of processing retransmission information | |
| CN101742463B (en) | Method, transmitting equipment and receiving equipment for realizing function of white name list | |
| CN103916489A (en) | Method and system for resolving single-domain-name multi-IP domain name | |
| WO2012088997A1 (en) | Method and device for identification | |
| JP5054664B2 (en) | Receiving terminal that receives header compressed packets | |
| KR20130069009A (en) | Method for generating ccn information using snmp and ipfix, and method for monitoring ccn using that | |
| CN103181121B (en) | A kind of access processing method, equipment and system | |
| CN103348740A (en) | Access processing method, apparatus and system | |
| US20150006756A1 (en) | Transmission management device, system, and method | |
| KR100884722B1 (en) | System and Method for Creating Network Share in Wired/Wireless Network |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| C06 | Publication | ||
| PB01 | Publication | ||
| C10 | Entry into substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| C14 | Grant of patent or utility model | ||
| GR01 | Patent grant | ||
| CF01 | Termination of patent right due to non-payment of annual fee |
Granted publication date: 20121121 |
|
| CF01 | Termination of patent right due to non-payment of annual fee |