CN111372322B

CN111372322B - Communication method and device

Info

Publication number: CN111372322B
Application number: CN201811588219.2A
Authority: CN
Inventors: 华哲辰; 程国秀
Original assignee: Huawei Technologies Co Ltd
Current assignee: Huawei Technologies Co Ltd
Priority date: 2018-12-25
Filing date: 2018-12-25
Publication date: 2022-04-12
Anticipated expiration: 2038-12-25
Also published as: CN111372322A; WO2020135440A1

Abstract

A communication method and a communication device are used for solving the problem that in the prior art, the system function is limited due to the fact that corresponding actions executed by a core network user plane network element according to rules are limited. And when the core network control plane network element determines that the core network user plane network element needs to be triggered to carry out bearer connection, sending a bearer connection request message to the core network user plane network element, and creating at least one first EAR by the core network user plane network element according to at least one piece of first EAR creation information included in the bearer connection request message, and correspondingly storing the created at least one first EAR and the identifier of the first EAR. By the method, the core network user plane network element can execute the relevant actions corresponding to the execution rules except for FAR, URR and QER, thereby achieving the purpose of expanding the action rules and further improving the integrity of the system function.

Description

Communication method and device

Technical Field

The present application relates to the field of communications technologies, and in particular, to a communication method and apparatus.

Background

The release of the 3GPP standard 29244100 describes that an Sx interface is used to define an interface between a control plane network element and a user plane network element of a 4G core network (EPC), and a next generation control plane (NG-CP) network element issues various rules and policy information related to a user plane (NG-UP) network element of a 5G core network through the interface when the user is on line or updated.

Wherein, when the core network control plane network element sends the bearing establishment request message to the core network user plane network element, the bearer establishment request message carries a Packet Detection Rule (PDR), a Forwarding Action Rule (FAR), a Usage Reporting Rule (URR), and a quality of service (QoS) enforcement rule (QER), the PDR includes a PDR Identifier (ID), a priority (precedence), Packet Detection Information (PDI), a FAR ID, a URR ID, and a QER ID., and the subsequent core network user plane network elements respectively match the FAR, URR, and QER carried in the bearer establishment request message through the FAR ID, URR ID, and QER ID included in the PDR, and then according to FAR, URR and QER, executing corresponding forwarding action and usage amount report, and executing corresponding QoS.

At present, service policies required by a core network user plane element all need to be configured in a bearer establishment request message, but the bearer establishment request message only includes three types of rules of FAR, URR, and QER, and a PDR only supports three types of identifiers including FAR ID, URR ID, and QER ID, so that the core network user plane element can only execute relevant actions specified by the three types of rules, resulting in limited system functions.

Disclosure of Invention

The application provides a communication method and a communication device, which are used for solving the problem that in the prior art, the system function is limited due to the fact that corresponding actions executed by a core network user plane network element are limited according to rules.

In a first aspect, the present application provides a communication method, when a core network control plane network element determines that a core network user plane network element needs to be triggered to perform bearer connection, a bearer connection request message is sent to the core network user plane network element, where the bearer connection request message includes at least one first created Extended Action Rule (EAR) information, the at least one first created EAR information is used to indicate to create at least one first EAR, and the at least one first EAR is an execution rule except a forwarding action rule FAR, a usage reporting rule URR, and a quality of service execution rule QER; then, the core network user plane network element creates the at least one first EAR according to the at least one first created EAR information, and correspondingly stores the created at least one first EAR and the identifier of the first EAR; wherein, any one of the first created EAR information includes an identifier of the first EAR that the any one of the first created EAR information indicates is created.

By the method, the core network user plane network element can execute the relevant actions corresponding to the execution rules except for FAR, URR and QER, so that the aim of expanding the action rules can be fulfilled, and the integrity of the system function can be improved.

In a possible design, the bearer connection request message further includes a first PDR, where the first PDR includes identifiers corresponding to the at least one first EAR, respectively; furthermore, after receiving the first user data message matched with the first PDR, the core network user plane network element searches for the stored at least one first EAR according to the identifier corresponding to the at least one first EAR included in the first PDR, and performs a corresponding action on the first user data message according to the at least one found first EAR.

Through the method, the core network control plane network element realizes the execution of the relevant actions corresponding to the execution rules except for FAR, URR and QER, thereby achieving the purpose of extending the action rules.

In a possible design, when determining that it is necessary to trigger the core network user plane element to update the bearer connection, the core network control plane element sends a bearer connection modification request message to the core network user plane element, where the bearer connection modification request message includes at least one second created EAR information, and the at least one second created EAR information is used to indicate that at least one second EAR is created; any second created EAR information comprises an identifier of a second EAR which is indicated to be created by the any second created EAR information; and the core network user plane network element creates the at least one second EAR according to the at least one second created EAR information, and correspondingly stores the created at least one second EAR and the identifier of the second EAR.

By the method, when the core network user plane network element needs to execute the relevant action corresponding to the second EAR, the second EAR to be executed can be directly searched in the at least one second EAR.

In a possible design, the bearer connection modification request message may further include a second PDR, where the second PDR includes an identifier of at least one third EAR, and the at least one third EAR is part or all of the following EARs: the at least one first EAR and/or the at least one second EAR; after receiving the second user data message matched with the second PDR, the core network user plane network element may search for at least one third EAR in the at least one stored first EAR and/or the at least one stored second EAR according to the identifier of the at least one third EAR, and perform a corresponding action on the second user data message according to the at least one searched third EAR.

By the method, the core network user plane network element can execute the corresponding action of the rule needing to be expanded according to the requirement, thereby improving the integrity of the system function.

In a possible design, when determining that it is necessary to trigger the core network user plane element to update the bearer connection, the core network control plane element sends a bearer connection modification request message to the core network user plane element, where the bearer connection modification request message includes delete EAR information and/or update EAR information, the delete EAR information includes an identifier of an EAR that needs to be deleted, and the update EAR information includes an identifier of an EAR that needs to be updated; the EAR deletion information is used for indicating to delete the EAR corresponding to the EAR identifier needing to be deleted, and the EAR updating information is used for indicating to update the EAR corresponding to the EAR identifier needing to be updated.

By the method, the core network user plane network element can delete and/or update the EAR which is stored currently according to the requirement.

In a possible design, when the bearer connection modification request message includes the EAR deletion information, the core network user plane network element may search, according to the identifier of the EAR to be deleted, for the EAR to be deleted in the stored EAR, and delete the EAR to be deleted. Thus, the core network user plane network element can delete the saved EAR according to the requirement.

In a possible design, when the bearer connection modification request message includes the updated EAR information, the core network user plane network element searches for the EAR to be updated in the saved EAR according to the identifier of the EAR to be updated, and updates the EAR to be updated. Thus, the user plane network element of the core network can update the saved EAR according to the requirement.

In one possible design, the core network user plane element may be saved in a database when the at least one first EAR or the at least one second EAR.

In a second aspect, the present application further provides a communication device, where the communication device has a function of implementing the core network control plane network element or the core network user plane network element in the method in the first aspect. The functions can be realized by hardware, and the functions can also be realized by executing corresponding software by hardware. The hardware or software includes one or more units corresponding to the above functions.

In a possible design, the structure of the communication device includes a transceiver unit and a processing unit, and these units may perform corresponding functions in the above method example, see the detailed description in the method example of the first aspect, which is not described herein again.

In a possible design, the communication apparatus includes a transceiver and a processor, and optionally may further include a memory, where the transceiver is configured to receive and transmit information and perform communication interaction with other devices in the communication system, and the processor is configured to support the communication apparatus to perform functions corresponding to the core network control plane network element or the core network user plane network element in the method according to the first aspect. The memory is coupled to the processor and retains program instructions and data necessary for the communication device.

In a third aspect, the present application further provides a communication system, where the communication system at least includes the core network control plane network element and the core network user plane network element mentioned in the above design.

In a fourth aspect, the present application also provides a computer storage medium having stored thereon computer-executable instructions for causing the computer, when invoked by the computer, to perform any of the methods mentioned above.

In a fifth aspect, the present application also provides a computer program product containing instructions which, when run on a computer, cause the computer to perform any of the methods mentioned above.

In a sixth aspect, the present application further provides a chip, coupled to a memory, for reading and executing program instructions stored in the memory to implement any of the above-mentioned methods.

Drawings

Fig. 1 is a schematic architecture diagram of a communication system provided in the present application;

fig. 2 is a flow chart of a communication method provided herein;

FIG. 3 is a schematic diagram of a PDR provided herein;

fig. 4 is a schematic structural diagram of a communication device provided in the present application;

fig. 5 is a structural diagram of a communication device according to the present application.

Detailed Description

The present application will be described in further detail below with reference to the accompanying drawings.

The embodiment of the application provides a communication method and a communication device, which are used for solving the problem that in the prior art, the system function is limited due to the fact that corresponding actions executed by a core network user plane network element are limited according to rules. The method and the device are based on the same inventive concept, and because the principles of solving the problems of the method and the device are similar, the implementation of the device and the method can be mutually referred, and repeated parts are not repeated.

Hereinafter, some terms in the present application are explained to facilitate understanding by those skilled in the art.

1) And the core network control plane network element is a network element responsible for mobility management and/or forwarding path management in the mobile network. The core network control plane network element may be a 4G core network control plane network element, or may be a 5G core network control plane network element (NG-CP). For example, it may be a mobility management entity (mobility management entity, serving gateway (S-GW), or a packet data network gateway (P-GW) in the core network, or may be an S-GW control plane or a P-GW control plane, or may be any network element of the MME, the S-GW, and the P-GW that are merged to form a control plane network element, or may be an S-GW control plane and a P-GW control plane that are merged to form a control plane network element, or may be an NG-CP network element (session management function, SMF), a network open function (NEF), a Policy Control Function (PCF) network element, or a packet gateway control plane function (PGW-C), a serving gateway function entity (serving gateway control plane function, SGW-C), a traffic detection function control plane function entity (TDF-C), an evolved packet data gateway control plane network element (ePDG-C), a Centralized Gateway (CGW), and other network elements having an Evolved Packet Core (EPC) control plane function.

2) The core network user plane network element is also called a core network forwarding plane network element and is a network element responsible for providing service message forwarding for terminal equipment, and the main functions are data packet routing and forwarding, mobility anchor points and uplink classifiers for supporting routing service flows to a data network and branch points for supporting multi-homing Packet Data Unit (PDU) sessions and the like. The core network User Plane network element may be a 4G core network User Plane network element, or may be a 5G core network User Plane network element (NG-UP). For example, the forwarding plane may be a physical forwarding plane device such as an S-GW, a P-GW, a router, a switch, and an SDN switch, or may be a virtual forwarding plane network element such as an S-GW forwarding plane or a P-GW forwarding plane. For example, the NG-UP may also be a network element having an EPC user plane function, such as a packet data network user plane function (PGW-U), a serving Gateway user plane function (SGW-U), a traffic detection function (TDF-U), an evolved packet data Gateway user plane network element (ePDG-U), a Distributed Gateway (DGW), and a Remote Gateway (RGW).

3) The terms "first," "second," and the like in the description of the present application are used for descriptive purposes only and are not intended to indicate or imply relative importance nor order to be construed.

4) And "at least one" means one or more.

In order to more clearly describe the technical solutions of the embodiments of the present application, the following describes in detail a communication method and apparatus provided by the embodiments of the present application with reference to the accompanying drawings.

Fig. 1 illustrates a possible architecture of a communication system, that is, an Evolved Packet System (EPS) architecture, to which the communication method provided in the embodiment of the present application is applicable, where the EPS architecture is divided into an access network and a core network, that is, an EPC. Wherein:

the access network can be an evolved E-UTRAN and realizes the functions related to wireless access for the terminal equipment;

the EPC mainly includes the following key logical network elements: MME, S-GW, P-GW, Home Subscriber Server (HSS) and Policy and Charging Rule Function (PCRF), which are described in detail below:

the MME mainly completes the processing of signaling plane functions, such as authentication and switching of users, mobility management of idle state terminals, user context, bearer management and the like;

the HSS is used for storing subscription information of a user;

the S-GW is used for routing and forwarding of a data network and providing related functions of lawful interception;

the P-GW is a gateway connected to an external data network, is a user plane anchor point between a 3rd Generation Partnership Project (3 GPP) access network and a non-3 GPP access network, and is responsible for functions such as user address allocation, policy control, execution of charging rules, and lawful interception, where the S-GW and the P-GW may be deployed in the same entity device or may be deployed in different entity devices, which is not limited in this embodiment of the present application;

and the PCRF provides policy and charging rules.

When establishing bearer connection, a terminal device may connect to the P-GW through an access network, and create a Protocol Data Unit (PDU) connection to access an external data network through the P-GW.

In the architecture of the communication system shown in fig. 1, the terminal device, the access network, and the network element in the EPC interact with the DN through corresponding interfaces.

It should be noted that, the foregoing only lists the 4G communication system to which the communication method provided in the embodiment of the present application is applied, and the communication method provided in the embodiment of the present application may also be applied to a 5G communication system, where functions of a core network control plane network element and a core network user plane network element in the 5G communication system are similar to those in the 4G communication system, and are not listed here.

The communication method provided by the embodiment of the application is suitable for the communication system shown in fig. 1. Referring to fig. 2, a specific process of the method may include:

step 201, the core network control plane network element determines that the core network user plane network element needs to be triggered to perform bearer connection.

In an alternative embodiment, when a terminal device (also referred to as a user equipment) is activated on the network line, the core network control plane network element determines that it needs to trigger the core network user plane network element to perform bearer connection, so as to execute step 202.

In an optional implementation manner, the determining, by the core network control plane network element, that the core network user plane network element needs to be triggered to perform bearer connection specifically may be: the core network control plane network element needs to trigger a new Packet Data Network (PDN) connection or a Traffic Detection Function (TDF) connection established by the core network user plane.

Step 202, the core network control plane network element sends a bearer connection request message to the core network user plane network element, where the bearer connection request message includes at least one piece of first created EAR information, where the at least one piece of first created EAR information is used to indicate that at least one first EAR is created, and the at least one first EAR is an execution rule except FAR, URR, and QER; the identity of the any one first created EAR information indicating a created first EAR is included in the any one first created EAR information.

In an alternative embodiment, based on the mentioned in step 201, the bearer connection request message may be used to trigger the core network user plane network element to establish a new PDN connection or TDF connection.

For example, the core network control plane network element may send the bearer Establishment Request message to the core network user plane network element by calling Sx Session Establishment Request service.

In practice, the bearer connection request message only contains one or more types of rules in three types of rules, FAR, URR, and QER, so that the core network user plane element can only execute the relevant actions specified by the three types of rules, resulting in limited functions. Therefore, when the core network user plane network element needs to execute the relevant actions corresponding to the rules other than the above three types of rules, in step 202 in this embodiment of the present application, the core network control plane network element may create a first created EAR message in the bearer connection request message, where each first created EAR message indicates to create a corresponding first EAR, so as to achieve the purpose of extending the action rules, so that the core network user plane network element may subsequently execute the relevant actions of the rules other than the existing rules, and thus may extend the system functions.

For example, the first EAR may be, but is not limited to, a Transmission Control Protocol (TCP) optimization rule, a video optimization rule, a local traffic splitting rule, a Toolbar (Toolbar) rule, and the like, which are not listed herein. It should be noted that the at least one first creation EAR information may indicate that different types of rules are created, for example, at least one of the above listed rules may be created.

In an alternative embodiment, the specific information element contained in the bearer connection request message may be embodied by table 1 below. It can be seen that, in table 1, the bearer connection message is added with create EAR information (in bold slant format in table 1), which is referred to as first create EAR information herein.

Table 1 information element for bearer setup messages

The specific content included in any one of the first created EAR information in the bearer connection request message may be embodied as following table 2:

table 2 creating EAR information

As can be seen from table 2, the first created EAR information includes an identifier of the first EAR that needs to be created, which is indicated by the first created EAR information, that is, the EAR ID in table 2, and this identifier uniquely identifies the first EAR.

Note that, any of the first created EAR information may include other contents shown in table 2 in addition to the identifier of the corresponding first EAR, but is not limited to only the contents shown in table 2, and may include contents other than the contents shown in table 2, and the present application does not limit this.

In an optional implementation manner, when the core network user plane network element needs to perform an action corresponding to a rule other than FAR, URR, and QER subsequently, the bearer connection request message may further include a first PDR, where the first PDR includes an identifier corresponding to each of the at least one first EAR. Thus, when the user plane network element of the core network receives the bearer connection request message, the corresponding first EAR can be searched through the identifier of the at least one first EAR, and then corresponding actions are executed.

Illustratively, when the first PDR includes an identifier of a FAR, an identifier of a URR, an identifier of a QER, and an identifier corresponding to the at least one first EAR, respectively, the first PDR may be represented as a PDR diagram shown in fig. 3.

Illustratively, the first PDR, when included in the bearer connection request message, may be embodied as an information element of Create PDR information (Create PDR) as shown in table 1. Specifically, the specific content included in the first PDR may be shown by the following table 3:

TABLE 3 first PDR

As can be seen from table 3, the EAR ID is included in the first PDR (in the bold oblique format in table 3), and in the embodiment of the present application, at least one EAR represented by the EAR ID corresponds to the ID.

In the process after bearer connection establishment, when the core network control plane network element determines that it needs to trigger the core network user plane network element to update bearer connection, the core network control plane network element may send a bearer connection modification request message to the core network user plane network element, for example, content included in the bearer connection modification request message may be as shown in table 4 referred to below. Specifically, according to different requirements, the content included in the bearer connection modification request message sent by the core network control plane network element to the core network user plane network element is different, and the following 23 cases may be exemplarily classified:

example case 1: the bearer connection modification request message comprises at least one piece of second created EAR information, and the at least one piece of second created EAR information is used for indicating the creation of at least one second EAR; the identity of the any second created EAR indicated by the any second created EAR information is included in the any second created EAR information.

In this example case 1, the specific contents shown in table 4 include Create EAR information (i.e., Create EAR in bold slant format in table 4), referred to herein as second Create EAR information. In an optional implementation manner, specific contents included in any one of the second created EAR information may also be referred to in table 2, and details are not repeated here.

Example case 2: the bearer connection modification request message includes a second PDR, where the second PDR includes an identifier of a part or all of the at least one first EAR.

In this example case 2, the second PDR may be an updated PDR with respect to the first PDR, and in particular, the content included in the second PDR may be the content of the updated PDR as shown in table 5 referred to below. At this time, the EAR ID (in bold slant format in table 5) included in table 5 is an identifier of a part or all of the at least one first EAR.

Example case 3: the bearer connection modification request message includes the at least one second created EAR information and a third PDR, where the third PDR includes an identifier of a part or all of the at least one second EAR.

In this example case 3, the third PDR may be an updated PDR with respect to the first PDR, and the content included in the third PDR may also refer to the content of the updated PDR shown in table 5 referred to below. At this time, the EAR ID included in table 5 is an identifier of a part or all of the at least one second EAR.

Example case 4: example case 1 and example case 2 are combined.

Example case 5: example case 2 is combined with example case 3.

It should be noted that, in this example case 5, the second PDR and the third PDR may be regarded as the same PDR. That is, in this example case 5, the updated PDR may include both a part or all of the identifier of the at least one first EAR and a part or all of the identifier of the at least one second EAR.

Example case 6: the bearer connection modification request message includes EAR deletion information, the EAR deletion information includes an EAR identifier that needs to be deleted, and the EAR deletion information is used for indicating deletion of the EAR corresponding to the EAR identifier that needs to be deleted.

In this example case 6, the delete EAR information is embodied as delete EAR information in table 4 (i.e., Remove EAR in bold slant format in table 4). In an alternative embodiment, the content included in the deleted EAR information may be as shown in table 6. In this case, the EAR ID included in the deleted EAR information is an identifier of an existing EAR at present, for example, when only the at least one first EAR is created at present, the EAR ID may be a part or all of the identifier of the at least one first EAR, so that the core network user plane element deletes the created EAR that needs to be deleted.

Example case 7: the bearer connection modification request message includes updated EAR information, the updated EAR information includes an identifier of an EAR that needs to be updated, and the updated EAR information is used for indicating to update an EAR corresponding to the identifier of the EAR that needs to be updated.

In this example case 7, the updated EAR information is embodied as the updated EAR information in table 4 (i.e., Update EAR in bold tilt format in table 4). In an alternative embodiment, the content included in the updated EAR information may be as shown in table 7. In this case, the EAR ID included in the updated EAR information is an identifier of an existing EAR at present, for example, when only the at least one first EAR is created at present, the EAR ID may be part or all of the identifier of the at least one first EAR, so that the core network user plane element updates the created EAR that needs to be deleted.

It should be noted that the updated EAR information may include other contents shown in table 7 in addition to the identifier of the corresponding EAR, but is not limited to only the contents shown in table 7, and may include contents other than the contents shown in table 7, and the present application does not limit this.

Example case 8: the bearer connection modification request message includes the delete EAR information and the update EAR information, that is, a combination of example case 6 and example case 7.

Example case 9: example case 1 and example case 6 are combined.

In this example case 9, the case where both at least one first EAR and at least one second EAR are created is the case, and at this time, the EAR ID included in the delete EAR information may be part or all of the identification of the at least one first EAR and part or all of the identification of the at least one second EAR.

Example case 10: example case 1 and example case 7 are combined.

In this example case 9, the case where both at least one first EAR and at least one second EAR are created is the case, and at this time, the EAR ID included in the updated EAR information may be part or all of the identification of the at least one first EAR and part or all of the identification of the at least one second EAR.

Example case 11: example case 1 and example case 8 are combined. This case can also be regarded as a combination of the example case 9 and the example case 10, and reference can be made to the above description, which is not described herein again.

Example case 12: example case 2 and example case 6 are combined. In this case, the currently created EAR is only the at least one first EAR, so the EAR ID included in the delete EAR information at this time may be part or all of the identification of the at least one first EAR.

Example case 13: example case 2 is combined with example case 7. In this case, the currently created EAR is only the at least one first EAR, so the EAR ID included in the updated EAR information may be part or all of the identification of the at least one first EAR at this time.

Example case 14: example case 2 is combined with example case 8. This case can also be considered as a combination of example 12 and example case 13, and reference can be made specifically to the above description, which is not described in detail here.

Example case 15: example case 3 is combined with example case 6.

In this example case 15, the at least one first EAR and the at least one second EAR are both created, and in this case, the EAR ID included in the deleted EAR information may be part or all of the identification of the at least one first EAR and part or all of the identification of the at least one second EAR.

Example case 16: example case 3 is combined with example case 7.

In this example case 16, the case where both at least one first EAR and at least one second EAR are created is the case, and at this time, the EAR ID included in the updated EAR information may be part or all of the identification of the at least one first EAR and part or all of the identification of the at least one second EAR.

Example case 17: example case 3 is combined with example case 8. This case can also be regarded as a combination of example 15 and example case 16, and reference can be made specifically to the above description, which is not described in detail here.

Example case 18: example case 4 and example case 6 are combined.

Example case 19: example case 4 is combined with example case 7.

Example case 20: example case 4 is combined with example case 8.

Example case 21: example case 5 and example case 6 are combined.

Example case 22: example case 5 and example case 7 are combined.

Example case 23: example case 5 and example case 8 are combined.

The example cases 18 to 23 can all refer to the related descriptions in the corresponding example cases, and the application is not described in detail.

Table 4 bearer connection modification request message

TABLE 5 updated PDR

TABLE 6 delete EAR information

Table 7 update EAR information

For example, the core network control plane network element may send the bearer connection Modification Request message to the core network user plane network element by calling an Sx Session Modification Request service.

Step 203, the core network user plane network element creates the at least one first EAR according to the at least one first created EAR information, and correspondingly stores the created at least one first EAR and the identifier of the first EAR.

In an optional implementation manner, the core network user plane element may store the at least one first EAR and an identifier of the first EAR in a database, where the database may be local to the core network user plane element or may exist independently of the core network user plane element, and this is not specifically limited in this application. Of course, the core network user plane network element may store the at least one first EAR in other places than the database, which is not listed in this application.

In an optional implementation manner, the core network user plane network element may store the at least one first EAR and the identifier of the first EAR in a table form, and may also store the identifier in other forms, which is not limited in this application.

Specifically, when the core network user plane element stores the at least one first EAR, the core network user plane element also stores the identifier corresponding to each of the at least one first EAR, so as to identify the corresponding first EAR, thereby facilitating subsequent searching for the corresponding first EAR.

In an optional implementation manner, after the core network user plane network element performs step 203, the core network user plane network element replies a bearer connection response message to the core network control plane network element, and then the core network control plane network element performs a subsequent communication procedure, for example, the core network control plane network element may perform interactive communication with a network element that initiates a PDN or TDF session.

For example, the core network user plane network element may send the bearer connection Response message to the core network control plane network element by calling Sx Session Establishment Response service.

In an optional implementation manner, when the bearer connection request message further includes the first PDR involved in step 202, after receiving a first user data packet matching the first PDR, the core network user plane network element searches the stored at least one first EAR according to the identifier corresponding to each of the at least one first EAR included in the first PDR, and performs a corresponding action on the first user data packet according to the at least one first EAR found. Thus, the core network user plane element can execute the execution rules except FAR, URR and QER.

In an optional implementation manner, when the content included in the bearer connection modification request message received by the core network user plane network element from the core network control plane network element is different, the operation performed by the core network user plane network element is also different, and with reference to example case 1-example case 23 related to step 202, the operation performed by the core network user plane network element may be divided into the following 23 operations:

operation 1: when the bearer connection modification request message is the case in example case 1, the core network user plane network element may create the at least one second EAR according to the at least one second created EAR information, and correspondingly store the created at least one second EAR and an identifier of the second EAR.

Operation 2: when the bearer connection modification request message is the case in example case 2, after receiving a second user data message matched with the second PDR, the core network user plane network element searches, according to an identifier of an EAR included in the second PDR, for a first EAR corresponding to the identifier of the EAR included in the second PDR in the at least one stored first EAR, and performs a corresponding action on the second user data message according to the searched first EAR.

Operation 3: when the bearer connection modification request message is the case in example case 3, the core network user plane network element performs operation 1, and meanwhile, after receiving a third user data message matched with the third PDR, according to an identifier of an EAR included in the third PDR, searches for a second EAR corresponding to the identifier of the EAR included in the third PDR in the stored at least one second EAR, and performs a corresponding action on the third user data message according to the searched second EAR.

And operation 4: when the bearer connection modification request message is the case of the above-described example case 4, the core network user plane network element performs operations 1 and 2.

Operation 5: when the bearer connection modification request message is the case in the above-described example case 5, the core network user plane network element performs operations 2 and 3.

Operation 6: when the bearer connection modification request message is the case in example case 6, the core network user plane network element searches the EAR to be deleted in the saved EAR according to the identifier of the EAR to be deleted, and deletes the EAR to be deleted. For example, in a case that only the at least one first EAR is currently saved, the EAR that the core network user plane network element needs to delete is part or all of the saved at least one first EAR.

Operation 7: when the bearer connection modification request message is the case in example case 7, the core network user plane network element searches for the EAR to be updated in the saved EAR according to the identifier of the EAR to be updated, and deletes the EAR to be updated. For example, in a case that only the at least one first EAR is currently saved, the EAR that the core network user plane network element needs to update is part or all of the saved at least one first EAR.

Operation 8: when the bearer connection modification request message is the case in the above-described example case 8, the core network user plane network element performs operations 6 and 7.

Operation 9: when the bearer connection modification request message is the case in the above-described example case 9, the core network user plane network element performs operations 1 and 6. At this time, when the core network user plane network element performs operation 6, the EAR deleted by the core network is part or all of the stored at least one first EAR and part or all of the at least one second EAR.

Operation 10: when the bearer connection modification request message is the case in the above-described example case 10, the core network user plane network element performs operations 1 and 7. At this time, when the core network user plane network element performs operation 7, the EAR updated by the core network is part or all of the saved at least one first EAR and part or all of the at least one second EAR.

Operation 11: when the bearer connection modification request message is the case in the above example case 11, the operations performed by the core network user plane network element may refer to operations 9 and 10.

Operation 12: when the bearer connection modification request message is the case in the above-described exemplary case 12, the core network user plane network element performs operations 2 and 6.

Operation 13: when the bearer connection modification request message is the case in the above-described example case 13, the core network user plane network element performs operations 2 and 7.

Operation 14: when the bearer connection modification request message is the case in the above-mentioned example case 14, the operations performed by the core network user plane network element may refer to operation 12 and operation 13.

Operation 15: when the bearer connection modification request message is the case in the above-described example case 15, the core network user plane network element performs operations 3 and 6. Specifically, when the core network user plane network element performs operation 6, refer to the detailed description in operation 9, and details are not repeated here.

Operation 16: when the bearer connection modification request message is the case in the above-described example case 16, the core network user plane network element performs operations 3 and 7. Specifically, when the core network user plane network element performs operation 7, refer to the detailed description in operation 10, and details are not repeated here.

Operation 17: when the bearer connection modification request message is the case in the above-mentioned exemplary case 17, the operations performed by the core network user plane network element may refer to operation 15 and operation 16.

Operation 18: when the bearer connection modification request message is the case in the above-described example case 18, the core network user plane network element performs operation 1, operation 2, and operation 6. Specifically, when the core network user plane network element performs operation 6, refer to the detailed description in operation 9, and details are not repeated here.

Operation 19: when the bearer connection modification request message is the case in the above-described example case 19, the core network user plane network element performs operation 1, operation 2, and operation 7. Specifically, when the core network user plane network element performs operation 7, refer to the detailed description in operation 10, and details are not repeated here.

Operation 20: when the bearer connection modification request message is the case in the above exemplary case 20, the operations performed by the core network user plane network element may refer to operations 18 and 19.

Operation 21: when the bearer connection modification request message is the case in the above example case 21, the operations performed by the core network user plane network element may refer to operations 3 and 9.

Operation 22: when the bearer connection modification request message is the case in the above-mentioned example case 22, the operations performed by the core network user plane network element may refer to operations 3 and 7.

Operation 23: when the bearer connection modification request message is the case in the above-mentioned exemplary case 23, the operations performed by the core network user plane network element may refer to operation 21 and operation 22.

In an optional implementation manner, the core network user plane network element further sends a bearer connection modification response message to the core network control plane network element, so that the core network control plane network element performs a subsequent communication procedure, for example, the core network control plane network element may perform interactive communication with a network element that initiates a PDN or TDF session.

For example, the core network user plane network element may send the bearer connection Modification Response message to the core network control plane network element by calling an Sx Session Modification Response service.

By using the communication method provided in the embodiment of the present application, when a core network control plane network element determines that a core network user plane network element needs to be triggered to perform bearer connection, a bearer connection request message is sent to the core network user plane network element, and the core network user plane network element creates at least one first EAR according to at least one first created EAR information included in the bearer connection request message, and correspondingly stores the created at least one first EAR and an identifier of the first EAR. By the method, the core network user plane network element can execute the relevant actions corresponding to the execution rules except for FAR, URR and QER, thereby achieving the purpose of expanding the action rules and further improving the integrity of the system function.

In the embodiments provided in the foregoing application, the solutions of the communication methods provided in the embodiments of the present application are introduced from the perspective of each network element or device itself and from the perspective of interaction between each network element or device. It is to be understood that each network element and device, for example, the core network control plane network element and the core network user plane network element, in order to implement the above functions, includes a corresponding hardware structure and/or software unit for performing each function. Those of skill in the art would readily appreciate that the various illustrative elements and algorithm steps described in connection with the embodiments disclosed herein may be implemented as hardware or combinations of hardware and computer software. Whether a function is performed as hardware or computer software drives hardware depends upon the particular application and design constraints imposed on the solution. Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present application.

For example, when the network element or the device described above implements the corresponding functions through a software unit, as shown in fig. 4, a communication apparatus (a communication apparatus for performing a communication method) provided in an embodiment of the present application may include a processing unit 401 and a transceiver unit 402.

In an embodiment, the communication apparatus shown in fig. 4 may be configured to perform the operations of the core network control plane network element in the embodiment shown in fig. 2. For example:

the processing unit 401 is configured to determine that a core network user plane network element needs to be triggered to perform bearer connection; the transceiver unit 402 is configured to send a bearer connection request message to the core network user plane network element, where the bearer connection request message includes at least one piece of first created extended action rule EAR information, where the at least one piece of first created EAR information is used to indicate that at least one first EAR is created, and the at least one first EAR is an execution rule except for a forwarding action rule FAR, a usage reporting rule URR, and a quality of service execution rule QER; the identity of the any one first created EAR information indicating a created first EAR is included in the any one first created EAR information.

Therefore, based on the above communication apparatus, the core network user plane network element may create at least one first EAR according to at least one first created EAR information included in the bearer connection request message, and store the at least one first EAR. Therefore, the core network user plane network element can subsequently execute the relevant actions corresponding to the execution rules except for FAR, URR and QER, thereby achieving the purpose of expanding the action rules and further improving the integrity of the system function.

In an optional implementation manner, the bearer connection request message further includes a first PDR, where the first PDR includes identifiers corresponding to the at least one first EAR, respectively.

In an optional implementation manner, the processing unit 401 is further configured to determine that it is required to trigger the core network user plane network element to update a bearer connection; furthermore, the transceiver unit 402 is further configured to send a bearer connection modification request message to the core network user plane network element, where the bearer connection modification request message includes at least one second created EAR information, and the at least one second created EAR information is used to indicate that at least one second EAR is created; the identity of the any second created EAR indicated by the any second created EAR information is included in the any second created EAR information.

In an optional implementation manner, the bearer connection modification request message further includes a second PDR, where the second PDR includes an identifier of at least one third EAR, and the at least one third EAR is part or all of the following EARs: the at least one first EAR and/or the at least one second EAR.

In an optional implementation manner, the processing unit 401 is further configured to determine that it is required to trigger the core network user plane network element to update a bearer connection; furthermore, the transceiver unit 402 is further configured to send a bearer connection modification request message to the core network user plane network element, where the bearer connection modification request message includes EAR deletion information and/or EAR update information, where the EAR deletion information includes an identifier of an EAR that needs to be deleted, and the EAR update information includes an identifier of an EAR that needs to be updated; the EAR deletion information is used for indicating to delete the EAR corresponding to the EAR identifier needing to be deleted, and the EAR updating information is used for indicating to update the EAR corresponding to the EAR identifier needing to be updated.

In another embodiment, the communication apparatus shown in fig. 4 may be further configured to perform the operation of the user plane network element of the core network in the embodiment shown in fig. 2. For example:

the transceiver unit 402 is configured to receive a bearer connection request message from a core network control plane network element, where the bearer connection request message includes at least one first create extended action rule EAR information, where the at least one first create EAR information is used to indicate that at least one first EAR is created, and the at least one first EAR is an execution rule except for a forwarding action rule FAR, a usage reporting rule URR, and a quality of service execution rule QER; any one of the first created EAR information comprises an identifier of the first created EAR indicated by the any one of the first created EAR information; the processing unit 401 is configured to create the at least one first EAR according to the at least one first created EAR information, and store and correspondingly store the created at least one first EAR and an identifier of the first EAR.

Therefore, based on the communication device, the core network user plane network element can subsequently execute the relevant actions corresponding to the execution rules except for FAR, URR and QER, thereby achieving the purpose of extending the action rules and further improving the integrity of the system function.

In an optional implementation manner, the bearer connection request message further includes a first PDR, where the first PDR includes identifiers corresponding to the at least one first EAR; correspondingly, the transceiver unit 402 is further configured to receive a first user data packet; furthermore, the processing unit 401 is further configured to, after the transceiving unit 402 receives the first user data packet matching the first PDR, search the stored at least one first EAR according to the identifier corresponding to the at least one first EAR included in the first PDR, and perform a corresponding action on the first user data packet according to the searched at least one first EAR.

In an optional implementation manner, the transceiver unit 402 is further configured to receive a bearer connection modification request message from the core network control plane network element, where the bearer connection modification request message includes at least one second created EAR information, and the at least one second created EAR information is used to indicate that at least one second EAR is created; any second created EAR information comprises an identifier of a second EAR which is indicated to be created by the any second created EAR information; the corresponding processing unit 401 is further configured to create the at least one second EAR according to the at least one second created EAR information, and correspondingly store the created at least one second EAR and an identifier of the second EAR.

In an optional implementation manner, the bearer connection modification request message further includes a second PDR, where the second PDR includes an identifier of at least one third EAR, and the at least one third EAR is part or all of the following EARs: the at least one first EAR and/or the at least one second EAR; the corresponding transceiving unit 402 is further configured to receive a second user data packet; furthermore, the processing unit 401 is further configured to, after the transceiver unit receives a second user data packet matching the second PDR, search the at least one third EAR in the at least one stored first EAR and/or the at least one stored second EAR according to the identifier of the at least one third EAR, and perform a corresponding action on the second user data packet according to the at least one searched third EAR.

In another optional implementation, the transceiver unit 402 is further configured to receive a bearer connection modification request message from the core network control plane network element, where the bearer connection modification request message includes delete EAR information and/or update EAR information, where the delete EAR information includes an identifier of an EAR that needs to be deleted, and the update EAR information includes an identifier of an EAR that needs to be updated; the EAR deletion information is used for indicating to delete the EAR corresponding to the EAR identifier needing to be deleted, and the EAR updating information is used for indicating to update the EAR corresponding to the EAR identifier needing to be updated.

In an implementation manner, when the bearer connection modification request message includes the information for deleting the EAR, the processing unit 401 is further configured to search the EAR to be deleted from the saved EARs according to the identifier of the EAR to be deleted, and delete the EAR to be deleted.

In another implementation manner, when the bearer connection modification request message includes the updated EAR information, the processing unit 401 is further configured to search, according to the identifier of the EAR to be updated, for the EAR to be updated in the saved EAR, and update the EAR to be updated.

It should be noted that the division of the unit in the embodiment of the present application is schematic, and is only a logic function division, and there may be another division manner in actual implementation. The functional units in the embodiments of the present application may be integrated into one processing unit, or each unit may exist alone physically, or two or more units are integrated into one unit. The integrated unit can be realized in a form of hardware, and can also be realized in a form of a software functional unit.

The integrated unit, if implemented in the form of a software functional unit and sold or used as a stand-alone product, may be stored in a computer readable storage medium. Based on such understanding, the technical solution of the present application may be substantially implemented or contributed by the prior art, or all or part of the technical solution may be embodied in a software product, which is stored in a storage medium and includes instructions for causing a computer device (which may be a personal computer, a server, a network device, or the like) or a processor (processor) to execute all or part of the steps of the method according to the embodiments of the present application. And the aforementioned storage medium includes: various media capable of storing program codes, such as a usb disk, a removable hard disk, a read-only memory (ROM), a Random Access Memory (RAM), a magnetic disk, or an optical disk.

For another example, when the network element or the device implements corresponding functions through hardware, a communication apparatus (a communication apparatus for performing a communication method) provided in this application may include a transceiver 501 and a processor 502, and optionally may further include a memory 503, and refer to the structure diagram shown in fig. 5.

For example, the processor 502 may be a Central Processing Unit (CPU), a Network Processor (NP), or a combination of a CPU and an NP. The processor 502 may further include a hardware chip. The hardware chip may be an application-specific integrated circuit (ASIC), a Programmable Logic Device (PLD), or a combination thereof. The PLD may be a Complex Programmable Logic Device (CPLD), a field-programmable gate array (FPGA), a General Array Logic (GAL), or any combination thereof. When the processor 502 implements the above functions, it may be implemented by hardware, or may be implemented by hardware executing corresponding software.

The transceiver 501 and the processor 502 are connected to each other. Optionally, the transceiver 501 and the processor 502 are connected to each other through a bus 504; the bus 504 may be a Peripheral Component Interconnect (PCI) bus, an Extended Industry Standard Architecture (EISA) bus, or the like. The bus may be divided into an address bus, a data bus, a control bus, etc. For ease of illustration, only one thick line is shown in FIG. 5, but this is not intended to represent only one bus or type of bus.

The memory 503 is coupled to the processor 502 for storing programs necessary for the communication device. For example, the program may include program code including computer operating instructions. The memory 503 may include RAM, and may also include a non-volatile memory (non-volatile memory), such as at least one disk memory. The processor 502 executes the application program stored in the memory 503 to implement the functions of the communication apparatus.

In one embodiment, the communication apparatus shown in fig. 5 may be configured to perform the operations of the core network control plane network element in the embodiment shown in fig. 2. For example: the transceiver 501 is configured to implement communication interaction with other devices or network elements connected to the core network control plane network element, that is, to receive and send data; the processor 502 is configured to perform other operations or functions of the core network control plane network element.

In another embodiment, the communication apparatus shown in fig. 5 may be further configured to perform the operations of the core network user plane network element in the embodiment shown in fig. 2. For example: the transceiver 501 is configured to implement communication interaction with other devices or network elements connected to the user plane network element of the core network, that is, to receive and send data; the processor 502 is configured to perform other operations or functions of the core network user plane network element.

In an optional implementation manner, the memory 403 may be further configured to store the EAR created by the core network user plane network element (e.g., the at least one first EAR and/or the at least one second EAR referred to in the foregoing embodiment).

In summary, embodiments of the present application provide a communication method and apparatus, when a core network control plane network element determines that a core network user plane network element needs to be triggered to perform bearer connection, a bearer connection request message is sent to the core network user plane network element, and the core network user plane network element creates at least one first EAR according to at least one first created EAR information included in the bearer connection request message, and stores the at least one first EAR. By the method, the core network user plane network element can execute the relevant actions corresponding to the execution rules except for FAR, URR and QER, thereby achieving the purpose of expanding the action rules and further improving the integrity of the system function.

As will be appreciated by one skilled in the art, embodiments of the present application may be provided as a method, system, or computer program product. Accordingly, the present application may take the form of an entirely hardware embodiment, an entirely software embodiment or an embodiment combining software and hardware aspects. Furthermore, the present application may take the form of a computer program product embodied on one or more computer-usable storage media (including, but not limited to, disk storage, CD-ROM, optical storage, and the like) having computer-usable program code embodied therein.

The present application is described with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of the application. It will be understood that each flow and/or block of the flow diagrams and/or block diagrams, and combinations of flows and/or blocks in the flow diagrams and/or block diagrams, can be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general purpose computer, special purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.

These computer program instructions may also be stored in a computer-readable memory that can direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer-readable memory produce an article of manufacture including instruction means which implement the function specified in the flowchart flow or flows and/or block diagram block or blocks.

These computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide steps for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.

It will be apparent to those skilled in the art that various changes and modifications may be made in the embodiments of the present application without departing from the scope of the embodiments of the present application. Thus, if such modifications and variations of the embodiments of the present application fall within the scope of the claims of the present application and their equivalents, the present application is also intended to encompass such modifications and variations.

Claims

1. A method of communication, comprising:

the core network control plane network element determines that the core network user plane network element needs to be triggered to carry out bearing connection;

the core network control plane network element sends a bearer connection request message to the core network user plane network element, where the bearer connection request message includes at least one piece of first created extended action rule EAR information, where the at least one piece of first created EAR information is used to indicate that at least one first EAR is created, and the at least one first EAR is an execution rule except for a forwarding action rule FAR, a usage reporting rule URR, and a quality of service execution rule QER; the identity of the any one first created EAR information indicating a created first EAR is included in the any one first created EAR information.

2. The method according to claim 1, wherein the bearer connection request message further includes a first packet detection rule PDR, and the first PDR includes identifiers corresponding to the at least one first EAR, respectively.

3. The method of claim 1 or 2, wherein the method further comprises:

the core network control plane network element determines that the core network user plane network element needs to be triggered to update the bearer connection;

the core network control plane network element sends a bearer connection modification request message to the core network user plane network element, where the bearer connection modification request message includes at least one second created EAR information, and the at least one second created EAR information is used to indicate that at least one second EAR is created; the identity of the any second created EAR indicated by the any second created EAR information is included in the any second created EAR information.

4. The method of claim 3, wherein the bearer connection modification request message further includes a second PDR, the second PDR including an identification of at least one third EAR, the at least one third EAR being some or all of the following EARs: the at least one first EAR and/or the at least one second EAR.

5. The method of claim 1 or 2, wherein the method further comprises:

the core network control plane network element sends a bearer connection modification request message to the core network user plane network element, wherein the bearer connection modification request message includes EAR deletion information and/or EAR update information, the EAR deletion information includes an identifier of EAR to be deleted, and the EAR update information includes an identifier of EAR to be updated;

the EAR deletion information is used for indicating to delete the EAR corresponding to the EAR identifier needing to be deleted, and the EAR updating information is used for indicating to update the EAR corresponding to the EAR identifier needing to be updated.

6. A method of communication, comprising:

a core network user plane network element receives a bearer connection request message from a core network control plane network element, wherein the bearer connection request message includes at least one piece of first created Extended Action Rule (EAR) information, the at least one piece of first created EAR information is used for indicating the creation of at least one first EAR, and the at least one first EAR is an execution rule except a Forwarding Action Rule (FAR), a Usage Reporting Rule (URR) and a service Quality Execution Rule (QER); any one of the first created EAR information comprises an identifier of the first created EAR indicated by the any one of the first created EAR information;

and the core network user plane network element creates the at least one first EAR according to the at least one first created EAR information, and correspondingly stores the created at least one first EAR and the identifier of the first EAR.

7. The method according to claim 6, wherein the bearer connection request message further includes a first packet detection rule PDR, and the first PDR includes identifiers corresponding to the at least one first EAR; the method further comprises the following steps:

after receiving the first user data message matched with the first PDR, the core network user plane network element searches for the stored at least one first EAR according to the identifier corresponding to the at least one first EAR included in the first PDR, and performs a corresponding action on the first user data message according to the searched at least one first EAR.

8. The method of claim 6 or 7, wherein the method further comprises:

the core network user plane network element receives a bearer connection modification request message from the core network control plane network element, where the bearer connection modification request message includes at least one second created EAR information, and the at least one second created EAR information is used to indicate that at least one second EAR is created; any second created EAR information comprises an identifier of a second EAR which is indicated to be created by the any second created EAR information;

and the core network user plane network element creates the at least one second EAR according to the at least one second created EAR information, and correspondingly stores the created at least one second EAR and the identifier of the second EAR.

9. The method of claim 8, wherein the bearer connection modification request message further includes a second PDR, the second PDR including an identification of at least one third EAR, the at least one third EAR being some or all of: the at least one first EAR and/or the at least one second EAR;

the method further comprises the following steps:

and after receiving a second user data message matched with the second PDR, the core network user plane network element searches for at least one third EAR in the at least one stored first EAR and/or at least one stored second EAR according to the identifier of the at least one third EAR, and executes corresponding action on the second user data message according to the at least one searched third EAR.

10. The method of claim 6 or 7, wherein the method further comprises:

the core network user plane network element receives a bearer connection modification request message from the core network control plane network element, wherein the bearer connection modification request message includes EAR deletion information and/or EAR update information, the EAR deletion information includes an identifier of EAR to be deleted, and the EAR update information includes an identifier of EAR to be updated;

the EAR deletion information is used for indicating to delete the EAR corresponding to the EAR identifier needing to be deleted, and the EAR updating information is used for indicating to update the EAR corresponding to the EAR identifier needing to be updated;

when the bearer connection modification request message includes the EAR deletion information, the core network user plane network element searches the EAR to be deleted in the saved EAR according to the identifier of the EAR to be deleted, and deletes the EAR to be deleted;

and when the bearer connection modification request message includes the updated EAR information, the core network user plane network element searches the EAR needing to be updated in the saved EAR according to the identifier of the EAR needing to be updated, and updates the EAR needing to be updated.

11. A communication apparatus, applied to a core network control plane network element, comprising:

the processing unit is used for determining that the user plane network element of the core network needs to be triggered to carry out bearing connection;

a receiving and sending unit, configured to send a bearer connection request message to the core network user plane network element, where the bearer connection request message includes at least one piece of first created extended action rule EAR information, where the at least one piece of first created EAR information is used to indicate that at least one first EAR is created, and the at least one first EAR is an execution rule except for a forwarding action rule FAR, a usage reporting rule URR, and a quality of service execution rule QER; the identity of the any one first created EAR information indicating a created first EAR is included in the any one first created EAR information.

12. The apparatus of claim 11, wherein the bearer connection request message further includes a first packet detection rule PDR, and the first PDR includes identifiers corresponding to the at least one first EAR, respectively.

13. The apparatus of claim 11 or 12,

the processing unit is further configured to determine that the update bearer connection of the core network user plane network element needs to be triggered;

the transceiver unit is further configured to send a bearer connection modification request message to the core network user plane network element, where the bearer connection modification request message includes at least one second created EAR information, and the at least one second created EAR information is used to indicate that at least one second EAR is created; the identity of the any second created EAR indicated by the any second created EAR information is included in the any second created EAR information.

14. The apparatus of claim 13, wherein the bearer connection modification request message further includes a second PDR, the second PDR including an identification of at least one third EAR, the at least one third EAR being some or all of: the at least one first EAR and/or the at least one second EAR.

15. The apparatus of claim 11 or 12,

the receiving and sending unit is further configured to send a bearer connection modification request message to the core network user plane network element, where the bearer connection modification request message includes EAR deletion information and/or EAR update information, the EAR deletion information includes an identifier of an EAR that needs to be deleted, and the EAR update information includes an identifier of an EAR that needs to be updated;

16. A communication apparatus, applied to a core network user plane network element, comprising:

a receiving and sending unit, configured to receive a bearer connection request message from a core network control plane network element, where the bearer connection request message includes at least one piece of first created extended action rule EAR information, where the at least one piece of first created EAR information is used to indicate that at least one first EAR is created, and the at least one first EAR is an execution rule except for a forwarding action rule FAR, a usage reporting rule URR, and a quality of service execution rule QER; any one of the first created EAR information comprises an identifier of the first created EAR indicated by the any one of the first created EAR information;

and the processing unit is used for creating the at least one first EAR according to the at least one first EAR creating information and correspondingly storing the at least one created first EAR and the identifier of the first EAR.

17. The apparatus according to claim 16, wherein the bearer connection request message further includes a first packet detection rule PDR, and the first PDR includes identifiers corresponding to the at least one first EAR, respectively;

the receiving and sending unit is also used for receiving a user data message;

the processing unit is further configured to, after the receiving and sending unit receives the first user data packet matching the first PDR, search the stored at least one first EAR according to the identifier corresponding to each of the at least one first EAR included in the first PDR, and perform a corresponding action on the first user data packet according to the searched at least one first EAR.

18. The apparatus of claim 16 or 17,

the transceiver unit is further configured to receive a bearer connection modification request message from the core network control plane network element, where the bearer connection modification request message includes at least one second created EAR information, and the at least one second created EAR information is used to indicate that at least one second EAR is created; any second created EAR information comprises an identifier of a second EAR which is indicated to be created by the any second created EAR information;

the processing unit is further configured to create the at least one second EAR according to the at least one second created EAR information, and correspondingly store the created at least one second EAR and an identifier of the second EAR.

19. The apparatus of claim 18, wherein the bearer connection modification request message further includes a second PDR, the second PDR including an identification of at least one third EAR, the at least one third EAR being some or all of: the at least one first EAR and/or the at least one second EAR;

the receiving and sending unit is also used for receiving a user data message;

the processing unit is further configured to, after the transceiver unit receives a second user data packet matching the second PDR, search for at least one third EAR in the at least one stored first EAR and/or the at least one stored second EAR according to the identifier of the at least one third EAR, and perform a corresponding action on the second user data packet according to the at least one searched third EAR.

20. The apparatus of claim 16 or 17, wherein the transceiver unit is further configured to:

receiving a bearer connection modification request message from the core network control plane network element, where the bearer connection modification request message includes EAR deletion information and/or EAR update information, the EAR deletion information includes an identifier of an EAR that needs to be deleted, and the EAR update information includes an identifier of an EAR that needs to be updated;

when the bearer connection modification request message includes the delete EAR information, the processing unit is further configured to:

according to the identifier of the EAR needing to be deleted, searching the EAR needing to be deleted in the stored EAR, and deleting the EAR needing to be deleted;

when the bearer connection modification request message includes the updated EAR information, the processing unit is further configured to:

and searching the EAR needing to be updated in the saved EAR according to the identifier of the EAR needing to be updated, and updating the EAR needing to be updated.