WO2020135440A1 - 一种通信方法及装置 - Google Patents

一种通信方法及装置 Download PDF

Info

Publication number
WO2020135440A1
WO2020135440A1 PCT/CN2019/128021 CN2019128021W WO2020135440A1 WO 2020135440 A1 WO2020135440 A1 WO 2020135440A1 CN 2019128021 W CN2019128021 W CN 2019128021W WO 2020135440 A1 WO2020135440 A1 WO 2020135440A1
Authority
WO
WIPO (PCT)
Prior art keywords
ear
network element
information
core network
creation
Prior art date
Application number
PCT/CN2019/128021
Other languages
English (en)
French (fr)
Inventor
华哲辰
程国秀
Original Assignee
华为技术有限公司
Priority date (The priority date 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 date listed.)
Filing date
Publication date
Application filed by 华为技术有限公司 filed Critical 华为技术有限公司
Publication of WO2020135440A1 publication Critical patent/WO2020135440A1/zh

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/10—Connection setup
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L5/00—Arrangements affording multiple use of the transmission path
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L5/00—Arrangements affording multiple use of the transmission path
    • H04L5/003—Arrangements for allocating sub-channels of the transmission path
    • H04L5/0053—Allocation of signaling, i.e. of overhead other than pilot signals
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management

Definitions

  • This application relates to the field of communication technology, and in particular, to a communication method and device.
  • the 3GPP standard 29244 version 100 describes the Sx interface used to define the interface between the 4G core network (evolved packet core, EPC) control plane network element and the user plane network element, and the 5G core network control plane (next generation control plane, NG-CP)
  • EPC evolved packet core
  • NG-CP next generation control plane
  • the network element will deliver various user-related rules and policy information to the 5G core network user plane (NG-UP) network element through this interface.
  • NG-UP 5G core network user plane
  • the bearer establishment request message will carry a packet detection rule (packet detection, rule, PDR) and a forwarding action rule (forwarding action rule, FAR), usage reporting rules (usage reporting (URR) and quality of service (QoS) enforcement rules (QoS enforcement (rule, QER), the PDR contains PDR identification (ID, priority) (precedence), packet detection information (packet detection information (PDI), FAR ID, URR ID and QER ID.
  • packet detection rule packet detection, rule, PDR
  • FAR forwarding action rule
  • URR usage reporting
  • QoS enforcement rules QoS enforcement (rule, QER
  • PDR contains PDR identification (ID, priority) (precedence), packet detection information (packet detection information (PDI), FAR ID, URR ID and QER ID.
  • the business strategy required by the core network user plane network element needs to be configured in the bearer establishment request message, but the current bearer establishment request message only contains the above three types of FAR, URR, QER rules, and the PDR only supports the inclusion of FAR ID , URR ID, QER ID three types of identification, so that the core network user plane network element can only perform the relevant actions specified in the above three types of rules, resulting in limited system functions.
  • the present application provides a communication method and device to solve the problem that the corresponding actions performed by the core network user plane network element reference rules in the prior art are limited, resulting in a limitation of system function.
  • the present application provides a communication method.
  • a core network control plane network element determines that a core network user plane network element needs to be triggered to carry a bearer connection, it sends a bearer connection request message to the core network user plane network element.
  • the bearer connection request message includes at least one first creation extended action rule EAR information, and the at least one first creation EAR information is used to indicate creation of at least one first EAR, and the at least one first EAR is a forwarding action rule FAR, Usage reporting rules URR and service quality execution rules other than QER execution rules; after that, the core network user plane network element creates the at least one first EAR according to the at least one first creation EAR information, and saves the creation accordingly The at least one first EAR and the identifier of the first EAR; wherein, any first creation EAR information includes an identifier of the first EAR created by the first creation EAR information.
  • the core network user plane network element can execute relevant actions corresponding to the execution rules other than FAR, URR, and QER, so that the purpose of expanding the action rules can be achieved, and thus the integrity of the system function can be improved.
  • the bearer connection request message further includes a first PDR, and the first PDR includes identifiers respectively corresponding to the at least one first EAR; further, the core network user plane network element After receiving the first user data message matching the first PDR, search for the saved at least one first EAR according to the identifiers corresponding to the at least one first EAR contained in the first PDR respectively And perform corresponding actions on the first user data message according to the found at least one first EAR.
  • the core network control plane network element implements relevant actions corresponding to execution rules other than FAR, URR, and QER, so that the purpose of expanding action rules can be achieved.
  • the core network control plane network element when it determines that the core network user plane network element needs to be triggered to update the bearer connection, it sends a bearer connection modification request message to the core network user plane network element.
  • the bearer connection modification request message includes at least one second creation EAR information, and the at least one second creation EAR information is used to instruct creation of at least one second EAR; any second creation EAR information includes the any one second creation EAR information
  • the EAR information indicates the identifier of the created second EAR; further, 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 stores the created at least one second EAR correspondingly The logo of the second EAR and the second EAR.
  • the second EAR that needs to be executed can be directly searched in the stored at least one second EAR.
  • 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 in the following EAR Part or all: the at least one first EAR and/or the at least one second EAR; after the core network user plane network element receives the second user data message matching the second PDR, According to the identifier of the at least one third EAR, at least one third EAR may be searched among the stored at least one first EAR and/or the at least one second EAR, and according to the searched at least one third EAR The EAR performs corresponding actions on the second user data message.
  • the user plane network element of the core network can perform actions corresponding to rules that need to be expanded as needed, thereby improving the integrity of system functions.
  • the core network control plane network element when it determines that the core network user plane network element needs to be triggered to update the bearer connection, it sends a bearer connection modification request message to the core network user plane network element.
  • the bearer connection modification request message includes deletion EAR information and/or update EAR information, the deletion EAR information includes an identifier of the EAR that needs to be deleted, and the update EAR information includes an identifier of the EAR that needs to be updated; wherein, the deletion The EAR information is used to indicate that the EAR corresponding to the identifier of the EAR that needs to be deleted is deleted, and the update EAR information is used to indicate that the EAR corresponding to the identifier of the EAR that needs to be updated is updated.
  • the core network user plane network element can delete and/or update the currently saved EAR as needed.
  • the core network user plane network element may be included in the saved EAR according to the identifier of the EAR that needs to be deleted Find the EAR that needs to be deleted, and delete the EAR that needs to be deleted. In this way, the core network user plane network element can delete the saved EAR as needed.
  • the core network user plane network element searches in the saved EAR according to the identifier of the EAR that needs to be updated The EAR that needs to be updated, and the EAR that needs to be updated is updated. In this way, the core network user plane network element can update the saved EAR as needed.
  • the core network user plane network element may be saved in a database when the at least one first EAR or the at least one second EAR.
  • the present application also provides a communication device having a function of implementing a core network control plane network element or a core network user plane network element in the method of the first aspect described above.
  • the function can be realized by hardware, or can also be realized by hardware executing corresponding software.
  • the hardware or software includes one or more units corresponding to the above functions.
  • the structure of the communication device includes a transceiver unit and a processing unit, and these units can perform the corresponding functions in the above method examples. See the detailed description in the method examples of the first aspect, which is not repeated here.
  • the structure of the communication device includes a transceiver and a processor, and optionally may also include a memory.
  • the transceiver is used to send and receive information and communicate with other devices in the communication system.
  • the processor is configured to support the communication device to perform the corresponding function of the core network control plane network element or the core network user plane network element in the method of the first aspect.
  • the memory is coupled to the processor, and stores necessary program instructions and data of the communication device.
  • the present application also provides a communication system, the communication system includes at least the core network control plane network element and the core network user plane network element mentioned in the above design.
  • the present application also provides a computer storage medium that stores computer-executable instructions, which when used by the computer, causes the computer to execute the And either method.
  • the present application also provides a computer program product containing instructions that, when run on a computer, cause the computer to perform any of the above-mentioned methods.
  • 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.
  • FIG. 1 is a schematic structural diagram of a communication system provided by this application.
  • FIG. 3 is a schematic diagram of a PDR provided by this application.
  • FIG. 4 is a schematic structural diagram of a communication device provided by this application.
  • FIG. 5 is a structural diagram of a communication device provided by the present application.
  • Embodiments of the present application provide a communication method and device to solve the problem that the corresponding actions performed by the core network user plane network element reference rule in the prior art are limited, resulting in a system function limitation.
  • the method and the device described in this application are based on the same inventive concept. Since the principles of the method and the device to solve the problem are similar, the implementation of the device and the method can be referred to each other, and the repetition is not repeated.
  • the core network control plane network element is the 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 a 5G core network control plane network element (next generation control plane (NG-CP).
  • NG-CP next generation control plane
  • it may be a mobility management entity (mobility management entity, service gateway (S-GW), or packet data network gateway (P-GW) in the core network, or an S-GW control plane or P-GW).
  • the GW control plane may also be any network element in the MME, S-GW and P-GW merged to form a control plane network element, or the S-GW control plane and the P-GW control plane merged to form a control plane network element.
  • the NG-CP can also be a session management function network element (session management function, SMF), network open function (network exposure function, NEF), policy control function (policy control function, PCF) network element, or packet gateway control plane function Entity (packet data network gateway control plane function, PGW-C), service gateway control plane function entity (serving gateway control plane function, SGW-C), business detection function control plane function entity (traffic detection function function control plane function, TDF- C), evolved packet data gateway control plane network element (evolved packet data-gateway-control plan, ePDG-C), centralized gateway (centralized gateway (CGW), etc. with evolved packet core network (evolved packet core, EPC) control plane Functional NE.
  • SMF session management function network element
  • NEF network exposure function
  • policy control function policy control function
  • PCF policy control function
  • packet gateway control plane function Entity packet gateway control plane function Entity
  • PGW-C packet data network gateway control plane function
  • SGW-C service gateway control plane function entity
  • the core network user plane network element also known as the core network forwarding plane network element, is the network element responsible for providing service packet forwarding for terminal equipment. Its main functions are packet routing and forwarding, mobility anchors, and upstream classification
  • the router supports routing service flows to the data network and branch points to support multi-homed packet data unit (PDU) sessions.
  • the core network user plane network element may be a 4G core network user plane network element or a 5G core network user plane network element (Next Generation User Plane, NG-UP).
  • NG-UP Next Generation User Plane
  • it may be a physical forwarding plane device such as S-GW, P-GW, router, switch, and SDN switch, or a virtual forwarding plane network element such as an S-GW forwarding plane or a P-GW forwarding plane.
  • the NG-UP may also be a packet gateway user plane function entity (packet data, network gateway user, plane function, PGW-U), a service gateway user plane function entity (serving gateway, user plane function, SGW-U), service Detection function user plane functional entity (traffic detection function user plane function (TDF-U), evolved packet data gateway user plane network element (evolved packet data-gateway-user plan (ePDG-U), distributed gateway (distributed gateway (DGW) , Remote gateway (Remote Gateway, RGW) and other network elements with EPC user plane functions.
  • packet gateway user plane function entity packet data, network gateway user, plane function, PGW-U
  • a service gateway user plane function entity serving gateway, user plane function, SGW-U
  • service Detection function user plane functional entity traffic detection function user plane function (TDF-U)
  • EPDG-U evolved packet data gateway user plane network element
  • DGW distributed gateway
  • RGW Remote gateway
  • At least one refers to one or more.
  • FIG. 1 shows a possible communication system architecture applicable to the communication method provided by the embodiment of the present application, namely an evolved packet system (EPS) system architecture.
  • EPS evolved packet system
  • the core network is the EPC. among them:
  • the access network may be an evolved E-UTRAN, which implements wireless access related functions for terminal equipment;
  • EPC mainly includes the following key logical network elements: MME, S-GW, P-GW, home subscriber server (home subscriber service, HSS) and policy and charging rule function (policy and charging rule function (PCRF), the following The specific introduction of the above network elements:
  • the MME mainly completes the processing of signaling plane functions, such as user authentication, handover, idle state terminal mobility management, user context, and bearer management, etc.;
  • the HSS is used to store user's contract information
  • the S-GW is used for data network routing and forwarding, and provides functions related to lawful interception
  • the P-GW is a gateway that connects to an external data network, and is a user plane anchor between the 3rd Generation Partnership Project (3GPP) access network and non-3GPP access network, and is responsible for user addresses. Functions such as allocation, policy control and charging rule execution, legal interception, etc., where the S-GW and the P-GW can be deployed in the same physical device or separately in different physical devices, embodiments of the present application There are no restrictions on this;
  • the PCRF provides policies and charging rules.
  • the terminal device may connect to the P-GW through an access network, and create a protocol data unit (packet data unit, PDU) connection through the P-GW to access an external data network.
  • PDU packet data unit
  • the terminal device, the access network, the network element in the EPC and the DN communicate and interact through corresponding interfaces.
  • the communication method provided by the embodiments of the present application is applicable to the communication system shown in FIG. 1.
  • the specific flow 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 carry the bearer connection.
  • the core network control plane network element determines that the core network user plane network element needs to be triggered to carry the bearer connection. Thus step 202 is performed.
  • the core network control plane network element determines that the core network user plane network element needs to be triggered for bearer connection. Specifically, the core network control plane network element needs to trigger the core A new packet data network (PDN) connection or traffic detection function (TDF) connection established on the network user plane.
  • PDN packet data network
  • TDF traffic detection function
  • 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 first creation EAR information, and the at least one first creation EAR information
  • the information is used to instruct the creation of at least one first EAR, and the at least one first EAR is an execution rule other than FAR, URR, and QER; any one of the first creation EAR information includes the any one of the first creation EAR information indicating creation The first EAR logo.
  • 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.
  • the core network control plane network element may send the bearer establishment request message to the core network user plane network element by calling the SxSessionEstablishmentRequest service.
  • the bearer connection request message only contains one or more types of rules among the three types of rules of FAR, URR, and QER, so that the core network user plane network element can only execute the relevant rules specified in the three types of rules. Action, resulting in limited functionality. Therefore, when the core network user plane network element is required to perform related actions corresponding to rules other than the above three types of rules, in step 202 of the embodiment of the present application, the core network control plane network element may include a The first creation EAR information, each first creation EAR information indicates the creation of a corresponding first EAR, to achieve the purpose of extending the action rules, so that the core network user plane network element can subsequently perform actions related to rules other than the existing ones, So that the system function can be expanded.
  • the first EAR may be, but not limited to, transmission control protocol (transmission control protocol, TCP) optimization rules, video optimization rules, local service offload rules, Toolbar rules, etc., for this application No longer list them one by one.
  • transmission control protocol transmission control protocol, TCP
  • the at least one first creation EAR information may indicate creation of different types of rules, for example, it may indicate creation of at least one of the above-listed rules.
  • the specific information element included in the bearer connection request message may be reflected in Table 1 below. It can be seen that in Table 1, the EAR creation information is added to the bearer connection message (as in the bold and oblique format in Table 1), which is referred to herein as the first creation EAR information.
  • the first creation EAR information includes the identifier of the first EAR that needs to be created indicated by the first creation EAR information, that is, the EAR ID in Table 2, and this identifier uniquely identifies the first One EAR.
  • any one of the first creation EAR information may include other content as shown in Table 2 in addition to the corresponding first EAR identifier, but it is not limited to only the content shown in Table 2, but also There are contents other than those shown in Table 2, which are not limited in this application.
  • the bearer connection request message may further include the first PDR.
  • the first PDR includes identifiers corresponding to the at least one first EAR respectively.
  • the first PDR when the first PDR includes the FAR logo, the URR logo, the QER logo, and the logo corresponding to the at least one first EAR, the first PDR may be represented as shown in FIG. 3 The schematic diagram of PDR is shown.
  • the first PDR when included in the bearer connection request message, it 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 in Table 3 below:
  • the first PDR contains the EAR ID (as in bold and slanted format in Table 3).
  • the core network control plane network element may report to the core network user plane network
  • the unit sends a bearer connection modification request message.
  • the content included in the bearer connection modification request message may be as shown in Table 4 below.
  • 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 may be divided into the following 23 examples:
  • the bearer connection modification request message includes at least one second creation EAR information, and the at least one second creation EAR information is used to indicate the creation of at least one second EAR; any one of the second creation EAR information includes all Any one of the second creation EAR information indicates the identity of the created second EAR.
  • the specific content shown in Table 4 contains creation EAR information (that is, Create EAR in bold oblique format in Table 4), which is referred to herein as second creation EAR information.
  • creation EAR information that is, Create EAR in bold oblique format in Table 4
  • second creation EAR information the specific content included in any second creation EAR information may also refer to Table 2, and specific details will not be repeated here.
  • the bearer connection modification request message includes a second PDR, and the second PDR includes an identification of part or all of the first EAR in the at least one first EAR.
  • the second PDR may be a PDR updated with respect to the first PDR, and the specific content included in the second PDR may be the content of the updated PDR as shown in Table 5 referred to below.
  • the EAR ID included in Table 5 is the identification of some or all of the first EARs in the at least one first EAR.
  • the bearer connection modification request message includes the at least one second creation EAR information and a third PDR, and the third PDR includes a part or all of the second EAR of the at least one second EAR Logo.
  • the third PDR may be an updated PDR relative to the first PDR, and the specific content of the third PDR may also be referred to the updated PDR shown in Table 5 below. content.
  • the EAR ID included in Table 5 is the identification of part or all of the second EAR in the at least one second EAR.
  • Example Case 4 Example Case 1 and Example Case 2 are combined.
  • Example Case 5 Example Case 2 and Example Case 3 are combined.
  • 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 not only part or all of the identifier of the at least one first EAR, but also part or all of the identifier of the at least one second EAR.
  • the bearer connection modification request message includes deletion EAR information, and the deletion EAR information includes an identifier of the EAR that needs to be deleted, wherein the deletion EAR information is used to instruct to delete the identifier of the EAR that needs to be deleted Corresponding EAR.
  • the deletion EAR information is embodied as the deletion EAR information in Table 4 (that is, the bold skewed format Remove in Table 4).
  • the content included in the deletion EAR information may be as shown in Table 6.
  • the EAR ID included in the deleted EAR information is the identifier of the currently existing EAR. For example, when only the at least one first EAR is currently created, it may be the at least one Part or all of the identifier of the first EAR, so that the core network user plane network element deletes the created EAR that needs to be deleted.
  • Example case 7 The bearer connection modification request message includes update EAR information, and the update EAR information includes an identifier of the EAR that needs to be updated, and the update EAR information is used to indicate that the identifier of the EAR that needs to be updated is updated. EAR.
  • the updated EAR information is embodied as the updated EAR information in Table 4 (that is, the bold italicized Update in Table 4).
  • the content included in the update EAR information may be as shown in Table 7.
  • the EAR ID included in the update EAR information is the identifier of the currently existing EAR. For example, when only the at least one first EAR is currently created, it may be the at least one Part or all of the identifier of the first EAR, so that the core network user plane network element updates the created EAR that needs to be deleted.
  • the updated EAR information may also contain other contents as shown in Table 7, but it is not limited to only the contents shown in Table 7, and there may also be a table 7 Contents other than those shown are not limited in this application.
  • 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.
  • the EAR ID included in the deletion EAR information may be the at least one first EAR Part or all of the identification, 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.
  • the EAR ID included in the update EAR information may be the at least one first EAR Part or all of the identification, 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, which can be referred to the above description and will not be repeated here.
  • Example Case 12 Example Case 2 and Example Case 6 are combined.
  • the currently created EAR only has the at least one first EAR, so the EAR ID included in the deleted EAR information at this time may be part or all of the identifier of the at least one first EAR.
  • Example Case 13 Example Case 2 and Example Case 7 are combined.
  • the currently created EAR only has the at least one first EAR, so the EAR ID included in the updated EAR information at this time may be part or all of the identifier of the at least one first EAR.
  • Example Case 14 Example Case 2 and Example Case 8 are combined. This case can also be regarded as a combination of Example 12 and Example Case 13. For details, please refer to the above description, which will not be described in detail here.
  • Example Case 15 Example Case 3 and Example Case 6 are combined.
  • the EAR ID included in the deletion EAR information may be the at least one first EAR Part or all of the identification, and part or all of the identification of the at least one second EAR.
  • Example Case 16 Example Case 3 and Example Case 7 are combined.
  • the EAR ID included in the update EAR information may be the at least one first EAR Part or all of the identification, and part or all of the identification of the at least one second EAR.
  • Example Case 17 Example Case 3 and Example Case 8 are combined. This case can also be regarded as a combination of Example 15 and Example Case 16. For details, please refer to the above description, which will not be described in detail here.
  • Example Case 18 Example Case 4 and Example Case 6 are combined.
  • Example Case 19 Example Case 4 and Example Case 7 are combined.
  • Example Case 20 Example Case 4 and Example Case 8 are combined.
  • 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 core network control plane network element may send the bearer connection modification request message to the core network user plane network element by invoking the 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 creation EAR information, and correspondingly saves the created at least one first EAR and the identifier of the first EAR.
  • the core network user plane network element may store the at least one first EAR and the first EAR identification in a database, where the database may be in the core network user plane
  • the network element is local, and may exist independently of the core network user plane network element, which is not specifically limited in this application.
  • the core network user plane network element may store the at least one first EAR elsewhere, and this application will not list them one by one.
  • the core network user plane network element may save the at least one first EAR and the first EAR logo in a table format, or may save it in other formats, which is not limited in this application .
  • the core network user plane network element when saving the at least one first EAR, the core network user plane network element also saves the identifiers corresponding to the at least one first EAR respectively, and is used to identify the corresponding first EAR, so as to facilitate subsequent search The corresponding first EAR.
  • the core network user plane network element after the core network user plane network element performs step 203, the core network user plane network element will reply to the core network control plane network element with a bearer connection response message, and then, The core network control plane network element will perform a subsequent communication process.
  • the core network control plane network element may interact with the network element that initiated the PDN or TDF session.
  • the core network user plane network element may send the bearer connection response message to the core network control plane network element by invoking the SxSessionEstablishmentResponse service.
  • the core network user plane network element receives a match with the first PDR After the first user data message, according to the identifiers corresponding to the at least one first EAR contained in the first PDR respectively, search for the saved at least one first EAR, and search for the at least one The first EAR performs corresponding actions on the first user data message.
  • the core network user plane network element can execute execution rules other than FAR, URR, and QER.
  • the core network user plane network element when the core network user plane network element receives different content from the bearer connection modification request message received from the core network control plane network element, the core network user plane network
  • the operations performed by the element are also different.
  • the operations performed by the core network user plane network element can be divided into the following 23 operations:
  • the core network user plane network element may create the at least one second EAR according to the at least one second creation EAR information, And correspondingly save the created at least one second EAR and the identifier of the second EAR.
  • Operation 2 When the bearer connection modification request message is the case in the above example case 2, the core network user plane network element receives the second user data message matching the second PDR, and then Searching for the identifier of the EAR included in the second PDR, searching for the first EAR corresponding to the identifier of the EAR included in the second PDR in the stored at least one first EAR, and searching for the first EAR according to the found first EAR The second user data message performs the corresponding action.
  • Operation 3 When the bearer connection modification request message is the case in the above example case 3, the core network user plane network element performs operation 1 while receiving a third user datagram matching the third PDR Afterwards, according to the identifier of the EAR included in the third PDR, search for the second EAR corresponding to the identifier of the EAR included in the third PDR in the stored at least one second EAR, and follow the found The second EAR performs corresponding actions on the third user data message.
  • Operation 5 When the bearer connection modification request message is the case in the above example case 5, the core network user plane network element performs operation 2 and operation 3.
  • the core network user plane network element searches the saved EAR for the need to delete according to the identifier of the EAR that needs to be deleted EAR, and delete the EAR that needs to be deleted. For example, when 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 the above example case 7, the core network user plane network element searches the saved EAR for the required update according to the identifier of the EAR that needs to be updated EAR and delete the EAR that needs to be updated. For example, when 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 foregoing 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 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 saved 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 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 foregoing 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 situation in the above example case 12, the core network user plane network element performs operations 2 and 6.
  • Operation 14 When the bearer connection modification request message is the case in the foregoing example case 14, the operations performed by the core network user plane network element may refer to operations 12 and 13.
  • Operation 15 When the bearer connection modification request message is the case in the above example case 15, the core network user plane network element performs operations 3 and 6. Specifically, when performing the operation 6, the user plane network element of the core network may refer to the detailed description in operation 9, which will not be repeated here.
  • Operation 16 When the bearer connection modification request message is the case in the above-mentioned example case 16, the core network user plane network element performs operations 3 and 7. Specifically, when performing the operation 7, the core network user plane network element may 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 foregoing example case 17, the operations performed by the core network user plane network element may refer to operations 15 and 16.
  • Operation 18 When the bearer connection modification request message is the case in the foregoing example case 18, the core network user plane network element performs operation 1, operation 2, and operation 6. Specifically, when performing the operation 6, the user plane network element of the core network may refer to the detailed description in operation 9, which will not be repeated here.
  • Operation 19 When the bearer connection modification request message is the case in the foregoing example case 19, the core network user plane network element performs operation 1, operation 2, and operation 7. Specifically, when performing the operation 7, the core network user plane network element may 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 example 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 foregoing example case 21, for operations performed by the user plane network element of the core network, refer to operations 3 and 9.
  • Operation 22 When the bearer connection modification request message is the case in the foregoing example case 22, for operations performed by the core network user plane network element, refer to operations 3 and 7.
  • Operation 23 When the bearer connection modification request message is the case in the foregoing example case 23, for operations performed by the core network user plane network element, refer to operations 21 and 22.
  • the core network user plane network element will also send a bearer connection modification response message to the core network control plane network element, so that the core network control plane network element will follow up
  • the communication process for example, the core network control plane network element can interact with the network element that initiated the PDN or TDF session.
  • 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 the Sx Session Modification Response service.
  • the core network control plane network element determines that the core network user plane network element needs to be triggered to carry a bearer connection, it sends a bearer connection request message to the core network user plane network element, and the core network user
  • the surface network element creates at least one first EAR according to the at least one first creation EAR information included in the bearer connection request message, and correspondingly stores the created at least one first EAR and the identifier of the first EAR.
  • the core network user plane network element can execute relevant actions corresponding to the execution rules other than FAR, URR, and QER, so as to achieve the purpose of expanding the action rules, and thus can improve the integrity of the system function.
  • each network element and device such as the above-mentioned core network control plane network element and core network user plane network element, include hardware structures and/or software units corresponding to performing each function.
  • the present application can be implemented in the form of hardware or a combination of hardware and computer software. Whether a function is performed by hardware or computer software driven hardware depends on the specific application of the technical solution and design constraints. Professional technicians can use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of this application.
  • the communication device (a communication device for executing a communication method) provided by an embodiment of the present application may include a processing unit 401 and transceiver Unit 402.
  • the communication device shown in FIG. 4 may be used to perform the operations of the core network control plane network element in the embodiment shown in FIG. 2 described above.
  • the processing unit 401 is used to determine that a core network user plane network element needs to be triggered to carry a bearer connection; the transceiver unit 402 is used 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 first creation extended action rule EAR information, the at least one first creation EAR information is used to instruct creation of at least one first EAR, the at least one first EAR is a forwarding action rule FAR, a usage report rule URR and Execution rules other than the quality of service execution rule QER; any first creation EAR information includes an identifier of the first creation EAR information indicating the creation of the first EAR.
  • the core network user plane network element may create at least one first EAR according to at least one first creation EAR information included in the bearer connection request message, and save the at least one first EAR . Therefore, the core network user plane network element can subsequently perform related actions corresponding to the execution rules other than FAR, URR, and QER, thereby achieving the purpose of expanding the action rules, and thereby improving the integrity of the system function.
  • the bearer connection request message further includes a first PDR, and the first PDR includes identifiers respectively corresponding to the at least one first EAR.
  • the processing unit 401 is further configured to determine that the core network user plane network element needs to be triggered to update the bearer connection; further, the transceiver unit 402 is further configured to send the core network user plane The network element sends a bearer connection modification request message, where the bearer connection modification request message includes at least one second creation EAR information, and the at least one second creation EAR information is used to instruct to create at least one second EAR; any one second creation The EAR information includes an identifier of the second EAR created by any one of the second creation EAR information.
  • 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 in the following EAR Part or all of: the at least one first EAR and/or the at least one second EAR.
  • the processing unit 401 is further configured to determine that the core network user plane network element needs to be triggered to update the bearer connection; in turn, the transceiver unit 402 is further configured to send the core network user plane network The unit sends a bearer connection modification request message, where the bearer connection modification request message includes delete EAR information and/or update EAR information, the delete EAR information includes the identifier of the EAR that needs to be deleted, and the update EAR information includes the need to update The EAR identifier; wherein, the delete EAR information is used to indicate deletion of the EAR corresponding to the identifier of the EAR that needs to be deleted, and the update EAR information is used to indicate update of the EAR corresponding to the identifier of the EAR that needs to be updated.
  • the communication device shown in FIG. 4 may also be used to perform the operations of the core network user plane network element in the embodiment shown in FIG. 2 described above.
  • 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 creation extended action rule EAR information, and the at least one first creation EAR information is used to Instruct to create at least one first EAR, the at least one first EAR is an execution rule other than the forwarding action rule FAR, the usage reporting rule URR, and the quality of service execution rule QER; any first creation EAR information includes the task One first creation EAR information indicates the identifier of the created first EAR; the processing unit 401 is used to create the at least one first EAR according to the at least one first creation EAR information and save the corresponding saved creation At least one first EAR and the logo of the first EAR.
  • the core network user plane network element can subsequently execute related actions corresponding to the execution rules other than FAR, URR, and QER, thereby achieving the purpose of expanding the action rules, and thereby improving the integrity of system functions.
  • the bearer connection request message further includes a first PDR
  • the first PDR includes identifiers corresponding to the at least one first EAR respectively
  • the transceiver unit 402 It is also used to receive the first user data message; further, the processing unit 401 is further used to receive the first user data message matching the first PDR after the transceiver unit 402 receives, according to the first PDR
  • 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 creation EAR information ,
  • the at least one second creation EAR information is used to indicate the creation of at least one second EAR; any second creation EAR information includes an identifier of the second EAR indicated by the any second creation EAR information; the corresponding
  • the processing unit 401 is further configured to create the at least one second EAR according to the at least one second creation EAR information, and correspondingly save the created at least one second EAR and the identifier of the second EAR.
  • 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 in the following EAR Part or all of: the at least one first EAR and/or the at least one second EAR; the corresponding transceiving unit 402 is also used to receive a second user data message; and the processing unit 401 is also used to After the transceiver unit receives the second user data message matching the second PDR, according to the identifier of the at least one third EAR, the saved at least one first EAR and/or the at least one A second EAR searches for the at least one third EAR, and performs a corresponding action on the second user data message according to the found at least one third EAR.
  • the second PDR includes an identifier of at least one third EAR
  • the at least one third EAR is in the following EAR Part or all of: the at least one first EAR and/or the at least one second EAR
  • 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 deleting EAR information and/or Update EAR information, the delete EAR information includes the identifier of the EAR that needs to be deleted, and the update EAR information includes the identifier of the EAR that needs to be updated; wherein, the delete EAR information is used to indicate the deletion of the EAR that needs to be deleted Identify the corresponding EAR, and the update EAR information is used to instruct to update the EAR corresponding to the identifier of the EAR that needs to be updated.
  • the processing unit 401 is further configured to search for a location in the saved EAR according to the identifier of the EAR that needs to be deleted Describe the EAR that needs to be deleted, and delete the EAR that needs to be deleted.
  • the processing unit 401 is further configured to search in the saved EAR according to the identifier of the EAR that needs to be updated The EAR that needs to be updated, and the EAR that needs to be updated is updated.
  • the division of the units in the embodiments of the present application is schematic, and is only a division of logical functions, and there may be other division manners 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 may be integrated into one unit.
  • the above integrated unit can be implemented in the form of hardware or software function unit.
  • the integrated unit is implemented in the form of a software functional unit and sold or used as an independent product, it may be stored in a computer-readable storage medium.
  • the technical solution of the present application essentially or part of the contribution to the existing technology or all or part of the technical solution can be embodied in the form of a software product, and the computer software product is stored in a storage medium , Including several instructions to enable a computer device (which may be a personal computer, server, or network device, etc.) or processor to execute all or part of the steps of the methods described in the embodiments of the present application.
  • the aforementioned storage media include: U disk, mobile hard disk, read-only memory (ROM), random access memory (RAM), magnetic disk or optical disk and other media that can store program codes .
  • the communication device (communication device for executing a communication method) provided by the present application may include a transceiver 501 and a processor 502, and may optionally include For the memory 503, refer to the structural diagram shown in FIG. 5.
  • the processor 502 may be a central processing unit (CPU), a network processor (NP), or a combination of CPU and NP, and so on.
  • 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 (complex programmable logic device (CPLD), field programmable gate array (FPGA), general array logic (GAL) or any combination thereof.
  • CPLD complex programmable logic device
  • FPGA field programmable gate array
  • GAL general array logic
  • the transceiver 501 and the processor 502 are connected to each other.
  • the transceiver 501 and the processor 502 are connected to each other through a bus 504;
  • the bus 504 may be a peripheral component interconnection standard (Peripheral Component Interconnect, PCI) bus or an extended industry standard structure (Extended Industry Standard) Architecture, EISA) bus, etc.
  • PCI peripheral component interconnection standard
  • EISA Extended Industry Standard
  • the bus can be divided into address bus, data bus, control bus and so on. For ease of representation, only a thick line is used in FIG. 5, but it does not mean that there is only one bus or one type of bus.
  • the memory 503 is coupled to the processor 502 and is used to store programs necessary for the communication device.
  • the program may include program code, and the program code includes computer operation instructions.
  • the memory 503 may include RAM, or may also include a non-volatile memory (non-volatile memory), for example, at least one magnetic disk memory.
  • the processor 502 executes the application program stored in the memory 503 to realize the function of the communication device.
  • the communication device shown in FIG. 5 may be used to perform the operations of the core network control plane network element in the embodiment shown in FIG. 2 described above.
  • the transceiver 501 is used to implement communication and interaction with other devices or network elements connected to the core network control plane network element, that is, used to receive and send data;
  • the processor 502 is configured to execute the core Other operations or functions of network elements on the network control plane.
  • the communication device shown in FIG. 5 may also be used to perform the operations of the core network user plane network element in the embodiment shown in FIG. 2 described above.
  • the transceiver 501 is used to implement communication and interaction with other devices or network elements connected to the user plane network element of the core network, that is, used to receive and send data; the processor 502 is configured to execute the core Other operations or functions of network user plane network elements.
  • the memory 403 may also be used to store the EAR created by the core network user plane network element (such as at least one first EAR and/or at least one second involved in the foregoing embodiment) EAR).
  • the core network user plane network element such as at least one first EAR and/or at least one second involved in the foregoing embodiment
  • the embodiments of the present application provide a communication method and device.
  • the core network control plane network element determines that it needs to trigger the core network user plane network element to carry a bearer connection, it sends a bearer connection to the core network user plane network element.
  • a request message the core network user plane network element creates at least one first EAR according to at least one first creation EAR information included in the bearer connection request message, and saves the at least one first EAR.
  • the core network user plane network element can execute relevant actions corresponding to the execution rules other than FAR, URR, and QER, so as to achieve the purpose of expanding the action rules, and thus can improve the integrity of the system function.
  • the embodiments of the present application may be provided as methods, systems, or computer program products. Therefore, the present application may take the form of an entirely hardware embodiment, an entirely software embodiment, or an embodiment combining software and hardware. Moreover, the present application may take the form of a computer program product implemented on one or more computer usable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) containing computer usable program code.
  • computer usable storage media including but not limited to disk storage, CD-ROM, optical storage, etc.
  • These computer program instructions may also be stored in a computer readable memory that can guide a computer or other programmable data processing device to work in a specific manner, so that the instructions stored in the computer readable memory produce an article of manufacture including an instruction device, the instructions
  • the device implements the functions specified in one block or multiple blocks of the flowchart one flow or multiple flows and/or block diagrams.
  • These computer program instructions can also be loaded onto a computer or other programmable data processing device, so that a series of operating steps are performed on the computer or other programmable device to produce computer-implemented processing, which is executed on the computer or other programmable device
  • the instructions provide steps for implementing the functions specified in one block or multiple blocks of the flowchart one flow or multiple flows and/or block diagrams.

Landscapes

  • Engineering & Computer Science (AREA)
  • Signal Processing (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

一种通信方法及装置，用以解决现有技术中核心网用户面网元参照规则执行的相应动作有限，导致系统功能受限的问题。核心网控制面网元确定需要触发核心网用户面网元进行承载连接时，向所述核心网用户面网元发送承载连接请求消息，所述核心网用户面网元根据所述承载连接请求消息包括的至少一个第一创建EAR信息，创建至少一个第一EAR，并对应保存创建的所述至少一个第一EAR以及第一EAR的标识。通过上述方法，所述核心网用户面网元可以执行FAR、URR和QER以外的执行规则对应的相关动作，从而达到扩展动作规则的目的，进而可以提高系统功能的完整性。

Description

一种通信方法及装置
本申请要求在2018年12月25日提交中国专利局、申请号为201811588219.2、申请名称为“一种通信方法及装置”的中国专利申请的优先权，其全部内容通过引用结合在本申请中。
技术领域
本申请涉及通信技术领域，尤其涉及一种通信方法及装置。
背景技术
3GPP标准29244 100版本中描述了Sx接口用来定义4G核心网(evolved packet core，EPC)控制面网元与用户面网元的接口，5G核心网控制面(next generation control plane，NG-CP)网元在用户上线或更新时会通过该接口给5G核心网用户面(next generation user plane，NG-UP)网元下发用户相关的各种规则和策略信息。
其中，在核心网控制面网元向核心网用户面网元发送承载建立请求消息时，承载建立请求消息中会携带报文检测规则(packet detection rule，PDR)、转发动作规则(forwarding action rule，FAR)、使用量上报规则(usage reporting rule，URR)和服务质量(quality of service，QoS)执行规则(QoS enforcement rule，QER)，所述PDR中包含PDR标识((identification，ID)、优先级(precedence)、报文检测信息(packet detection information，PDI)、FAR ID、URR ID和QER ID。后续所述核心网用户面网元通过所述PDR中包含的FAR ID、URR ID、QER ID分别匹配所述承载建立请求消息中携带的FAR、URR、QER，进而按照FAR、URR、QER去执行相应的转发动作、使用量上报，并执行相应的QoS。
目前，核心网用户面网元所需的业务策略都需要配置到承载建立请求消息中，但是目前承载建立请求消息中只包含上述FAR、URR、QER三类规则，且PDR中仅支持包含FAR ID、URR ID、QER ID三类标识，使得核心网用户面网元只能执行上述三类规则规定的相关动作，导致系统功能受限。
发明内容
本申请提供一种通信方法及装置，用以解决现有技术中核心网用户面网元参照规则执行的相应动作有限，导致系统功能受限的问题。
第一方面，本申请提供了一种通信方法，核心网控制面网元确定需要触发核心网用户面网元进行承载连接时，向所述核心网用户面网元发送承载连接请求消息，所述承载连接请求消息中包括至少一个第一创建扩展动作规则EAR信息，所述至少一个第一创建EAR信息用于指示创建至少一个第一EAR，所述至少一个第一EAR为除转发动作规则FAR、使用量上报规则URR和服务质量执行规则QER以外的执行规则；之后，所述核心网用户面网元根据所述至少一个第一创建EAR信息，创建所述至少一个第一EAR，并对应保存创建的所述至少一个第一EAR以及第一EAR的标识；其中，任一个第一创建EAR信息中包括所述任一个第一创建EAR信息指示创建的第一EAR的标识。
通过上述方法，所述核心网用户面网元可以执行FAR、URR和QER以外的执行规则 对应的相关动作，从而可以达到扩展动作规则的目的，进而可以提高系统功能的完整性。
在一种可能的设计中，所述承载连接请求消息中还包括第一PDR，所述第一PDR中包括所述至少一个第一EAR分别对应的标识；进而，所述核心网用户面网元在接收到与所述第一PDR匹配的第一用户数据报文后，根据所述第一PDR中包含的所述至少一个第一EAR分别对应的标识，查找保存的所述至少一个第一EAR，并按照查找到的所述至少一个第一EAR对所述第一用户数据报文执行相应的动作。
通过上述方法，所述核心网控制面网元实现了执行除FAR、URR和QER以外的执行规则对应的相关动作，从而可以达到扩展动作规则的目的。
在一种可能的设计中，所述核心网控制面网元确定需要触发所述核心网用户面网元更新承载连接时，向所述核心网用户面网元发送承载连接修改请求消息，所述承载连接修改请求消息中包括至少一个第二创建EAR信息，所述至少一个第二创建EAR信息用于指示创建至少一个第二EAR；任一个第二创建EAR信息中包括所述任一个第二创建EAR信息指示创建的第二EAR的标识；进而所述核心网用户面网元根据所述至少一个第二创建EAR信息，创建所述至少一个第二EAR，并对应保存创建的所述至少一个第二EAR以及第二EAR的标识。
通过上述方法，可以使所述核心网用户面网元需要执行第二EAR对应的相关动作时，可以直接在保存的所述至少一个第二EAR中查找需要执行的第二EAR。
在一种可能的设计中，所述承载连接修改请求消息中还可以包括第二PDR，所述第二PDR中包括至少一个第三EAR的标识，所述至少一个第三EAR为以下EAR中的部分或全部：所述至少一个第一EAR和/或所述至少一个第二EAR；之后所述核心网用户面网元在接收到与所述第二PDR匹配的第二用户数据报文后，可以根据所述至少一个第三EAR的标识，在保存的所述至少一个第一EAR和/或所述至少一个第二EAR中查找至少一个第三EAR，并按照查找的所述至少一个第三EAR对所述第二用户数据报文执行相应的动作。
通过上述方法，所述核心网用户面网元可以根据需要执行需要扩展的规则相应的动作，从而可以提高系统功能的完整性。
在一种可能的设计中，所述核心网控制面网元确定需要触发所述核心网用户面网元更新承载连接时，向所述核心网用户面网元发送承载连接修改请求消息，所述承载连接修改请求消息中包括删除EAR信息和/或更新EAR信息，所述删除EAR信息中包括需要删除的EAR的标识，所述更新EAR信息中包括需要更新的EAR的标识；其中，所述删除EAR信息用于指示删除所述需要删除的EAR的标识对应的EAR，所述更新EAR信息用于指示更新所述需要更新的EAR的标识对应的EAR。
通过上述方法，所述核心网用户面网元可以根据需要删除和/或更新当前已保存的EAR。
在一种可能的设计中，当所述承载连接修改请求消息中包括所述删除EAR信息时，所述核心网用户面网元可以根据所述需要删除的EAR的标识，在已保存的EAR中查找所述需要删除的EAR，并删除所述需要删除的EAR。这样所述核心网用户面网元可以根据需要删除已保存的EAR。
在一种可能的设计中，当所述承载连接修改请求消息中包括所述更新EAR信息时，所述核心网用户面网元根据所述需要更新的EAR的标识，在已保存的EAR中查找所述需要更新的EAR，并更新所述需要更新的EAR。这样所述核心网用户面网元可以根据需要个更新已保存的EAR。
在一种可能的设计中，所述核心网用户面网元在所述至少一个第一EAR或者所述至少一个第二EAR时，可以保存至数据库中。
第二方面，本申请还提供了一种通信装置，该通信装置具有实现上述第一方面方法中核心网控制面网元或者核心网用户面网元的功能。所述功能可以通过硬件实现，也可以通过硬件执行相应的软件实现。所述硬件或软件包括一个或多个与上述功能相对应的单元。
在一个可能的设计中，所述通信装置的结构中包括收发单元和处理单元，这些单元可以执行上述方法示例中的相应功能，参见第一方面方法示例中的详细描述，此处不做赘述。
在一个可能的设计中，所述通信装置的结构中包括收发器和处理器，可选的还可以包括存储器，所述收发器用于收发信息，以及与通信系统中的其他设备进行通信交互，所述处理器被配置为支持所述通信装置执行上述第一方面方法中核心网控制面网元或者核心网用户面网元相应的功能。所述存储器与所述处理器耦合，其保存所述通信装置必要的程序指令和数据。
第三方面，本申请还提供了一种通信系统，所述通信系统至少包括上述设计中提及的核心网控制面网元和核心网用户面网元。
第四方面，本申请还提供了一种计算机存储介质，所述计算机存储介质中存储有计算机可执行指令，所述计算机可执行指令在被所述计算机调用时用于使所述计算机执行上述提及的任一种方法。
第五方面，本申请还提供了一种包含指令的计算机程序产品，当其在计算机上运行时，使得计算机执行上述提及的任一种方法。
第六方面，本申请还提供了一种芯片，所述芯片与存储器耦合，用于读取并执行所述存储器中存储的程序指令，以实现上述提及的任一种方法。
附图说明
图1为本申请提供的一种通信系统的架构示意图；
图2为本申请提供的一种通信方法的流程图；
图3为本申请提供的一种PDR的示意图；
图4为本申请提供的一种通信装置的结构示意图；
图5为本申请提供的一种通信装置的结构图。
具体实施方式
下面将结合附图对本申请作进一步地详细描述。
本申请实施例提供一种通信方法及装置，用以解决现有技术中核心网用户面网元参照规则执行的相应动作有限，导致系统功能受限的问题。其中，本申请所述方法和装置基于同一发明构思，由于方法及装置解决问题的原理相似，因此装置与方法的实施可以相互参见，重复之处不再赘述。
以下，对本申请中的部分用语进行解释说明，以便于本领域技术人员理解。
1)、核心网控制面网元，是负责移动网络中移动性管理和/或转发路径管理的网元。所述核心网控制面网元可以是4G核心网控制面网元，也可以是5G核心网控制面网元(next generation control plane，NG-CP)。例如，可以是核心网中移动管理实体(mobility management  entity，服务网关(serving gateway S-GW)，或分组数据网网关(packet data network gateway，P-GW)，也可以是S-GW控制面或P-GW控制面，还可以是MME、S-GW和P-GW中任意网元融合形成控制面网元，或S-GW控制面和P-GW控制面融合形成控制面网元。例如，所述NG-CP还可以是会话管理功能网元(session management function，SMF)、网络开放功能(network exposure function，NEF)、策略控制功能(policy control function，PCF)网元，或者分组网关控制面功能实体(packet data network gateway control plane function，PGW-C)、服务网关控制面功能实体(serving gateway control plane function，SGW-C)、业务检测功能控制面功能实体(traffic detection function control plane function，TDF-C)、演进分组数据网关控制面网元(evolved packet data gateway-control plan，ePDG-C)、集中式网关(centralized gateway，CGW)等具有演进的分组核心网(evolved packet core，EPC)控制面功能的网元。
2)、核心网用户面网元，又称为核心网转发面网元，是负责为终端设备提供业务报文转发的网元，主要功能是数据包路由和转发、移动性锚点、上行分类器来支持路由业务流到数据网络、分支点来支持多归属分组数据单元(packet data unit，PDU)会话等。所述核心网用户面网元可以是4G核心网用户面网元，也可以是5G核心网用户面网元(Next Generation User Plane，NG-UP)。例如，可以是S-GW、P-GW、路由器、交换机、SDN switch等物理转发面设备，还可以是S-GW转发面或P-GW转发面等虚拟的转发面网元。又例如，所述NG-UP还可以是分组网关用户面功能实体(packet data network gateway user plane function，PGW-U)、服务网关用户面功能实体(serving gateway user plane function，SGW-U)、业务检测功能用户面功能实体(traffic detection function user plane function，TDF-U)、演进分组数据网关用户面网元(evolved packet data gateway-user plan，ePDG-U)、分布式网关(distributed gateway，DGW)、远程网关(remote Gateway，RGW)等具有EPC用户面功能的网元。
3)、在本申请的描述中，“第一”、“第二”等词汇，仅用于区分描述的目的，而不能理解为指示或暗示相对重要性，也不能理解为指示或暗示顺序。
4)、“至少一个”指一个或者多个。
为了更加清晰地描述本申请实施例的技术方案，下面结合附图，对本申请实施例提供的通信方法及装置进行详细说明。
图1示出了本申请实施例提供的通信方法适用的一种可能的通信系统的架构，即演进分组系统(evolved packet system，EPS)系统架构，在所述EPS系统架构中，分为接入网和核心网两部分，核心网即EPC。其中：
接入网可以是演进的E-UTRAN，为终端设备实现无线接入有关的功能；
EPC主要包括以下几个关键逻辑网元：MME、S-GW、P-GW、归属用户服务器(home subscriber service，HSS)和策略和计费规则功能(policy and charging rule function，PCRF)，以下对上述网元进行具体介绍：
所述MME主要完成信令面功能的处理，如用户的鉴权、切换、空闲状态终端的移动性管理、用户上下文以及承载管理等；
所述HSS用于存储用户的签约信息；
所述S-GW，用于数据网络的路由和转发，并提供合法监听相关功能；
所述P-GW是连接外部数据网络的网关，是第三代合作伙伴计划(3rd Generation  Partnership Project,，3GPP)接入网和非3GPP接入网之间的用户面锚点，负责用户地址的分配、策略控制和计费规则的执行、合法监听等功能，其中，所述S-GW和所述P-GW可以部署于同一实体设备中，或者分别部署于不同的实体设备，本申请实施例对此不做限定；
所述PCRF，提供策略和计费规则。
终端设备在建立承载连接时，可以通过接入网连接到所述P-GW，并通过所述P-GW创建协议数据单元(packet data unit，PDU)连接来访问外部数据网络。
其中，图1所示的通信系统的架构中终端设备、接入网、EPC中的网元与DN之间通过相应的接口进行通信交互。
需要说明的是，上述只列举了本申请实施例提供的通信方法适用的4G通信系统，本申请实施例提供的通信方法还可以适用于5G通信系统，其中5G通信系统中的核心网控制面网元和核心网用户面网元的功能与4G通信系统中的功能类似，本申请此处不再一一列举。
本申请实施例提供的一种通信方法，适用于如图1所示的通信系统。参阅图2所示，该方法的具体流程可以包括：
步骤201、核心网控制面网元确定需要触发核心网用户面网元进行承载连接。
在一种可选的实施方式中，当终端设备(也称用户设备)在网络上线激活时，所述核心网控制面网元此时就确定了需要触发核心网用户面网元进行承载连接，从而执行步骤202。
在一种可选的实施方式中，所述核心网控制面网元确定需要触发所述核心网用户面网元进行承载连接具体可以表现为：所述核心网控制面网元需要触发所述核心网用户面建立的新的分组数据网络(packet data network，PDN)连接或者业务检测功能(traffic detection function，TDF)连接。
步骤202、所述核心网控制面网元向所述核心网用户面网元发送承载连接请求消息，所述承载连接请求消息中包括至少一个第一创建EAR信息，所述至少一个第一创建EAR信息用于指示创建至少一个第一EAR，所述至少一个第一EAR为除FAR、URR和QER以外的执行规则；任一个第一创建EAR信息中包括所述任一个第一创建EAR信息指示创建的第一EAR的标识。
在一种可选的实施方式中，基于步骤201中提到的，所述承载连接请求消息可以用于触发所述核心网用户面网元建立新的PDN连接或者TDF连接。
示例性的，所述核心网控制面网元可以通过调用Sx Session Establishment Request服务向所述核心网用户面网元发送所述承载建立请求消息。
在实际中，目前所述承载连接请求消息中只包含FAR、URR、QER三类规则中的一种或者多类规则，使得所述核心网用户面网元只能执行上述三类规则规定的相关动作，导致功能受限。因此，当需要核心网用户面网元执行上述三类规则以外的规则对应的相关动作时，在本申请实施例步骤202中，所述核心网控制面网元可以在所述承载连接请求消息一个第一创建EAR信息，每一个第一创建EAR信息指示创建一个相应的第一EAR，达到扩展动作规则的目的，以使核心网用户面网元后续可以执行除现有以外的规则的相关动作，从而可以扩展系统功能。
示例性的，第一EAR可以但不限于是传输控制协议(transmission control protocol，TCP) 优化规则、视频优化规则、本地业务分流规则、工具条(栏)(Toolbar)规则等等，对此本申请不再一一列举。其中，需要说明的是，所述至少一个第一创建EAR信息可以指示创建不同类型的规则，例如可以指示创建上述列举的规则中的至少一个。
在一种可选的实施方式中，承载连接请求消息中包含的具体信元可以通过以下表1体现。可以看出，在表1中，所述承载连接消息中添加了创建EAR信息(如表1中的加粗倾斜格式的)，本申请中这里称为第一创建EAR信息。
表1承载建立消息的信元
Figure PCTCN2019128021-appb-000001
Figure PCTCN2019128021-appb-000002
其中，所述承载连接请求消息中的任一个第一创建EAR信息中包括的具体内容可以如下表2具体体现：
表2创建EAR信息
Figure PCTCN2019128021-appb-000003
从表2中到的内容可以看出，第一创建EAR信息中包括了该第一创建EAR信息指示的需要创建的第一EAR的标识，即表2中的EAR ID，这个标识唯一标识该第一EAR。
需要说明的是，任一个第一创建EAR信息除了对应的第一EAR的标识以外，还可以包含如表2中所示的其他内容，但是也不限于只是如表2所示的内容，还可以有出表2示出的内容以外的内容，本申请对此不作限定。
在一种可选的实施方式中，当所述核心网用户面网元后续需要执行FAR、URR和QER以外的规则对应的动作时，所述承载连接请求消息中还可以包括第一PDR，所述第一PDR中包括所述至少一个第一EAR分别对应的标识。这样所述核心网用户面网元在收到所述承载连接请求消息时，就可以通过所述至少一个第一EAR的标识去查找对应的第一EAR，进而执行相应的动作。
示例性的，当所述第一PDR中包括FAR的标识、URR的标识、QER的标识和所述至少一个第一EAR分别对应的标识的时候，所述第一PDR可以表示为如图3所示的PDR示意图。
示例性的，所述第一PDR被包括在所述承载连接请求消息中时，可以体现为如表1中所示的创建PDR信息(Create PDR)这一信元。具体的，所述第一PDR中包括的具体内容可以通过如下表3示出：
表3第一PDR
Figure PCTCN2019128021-appb-000004
Figure PCTCN2019128021-appb-000005
从上述表3中可以看出，所述第一PDR中包含了EAR ID(如表3中的加粗倾斜格式的)，本申请实施例中，这里EAR ID代表的至少一个EAR分别对应的ID。
在承载连接建立之后的流程中，所述核心网控制面网元确定需要触发所述核心网用户面网元更新承载连接时，所述核心网控制面网元可以向所述核心网用户面网元发送承载连接修改请求消息，例如，所述承载连接修改请求消息包括的内容可以如下面涉及的表4所示。具体的，根据需求不同，所述核心网控制面网元向所述核心网用户面网元发送的承载连接修改请求消息中包括的内容不同，示例性的可以分为以下23种情况：
示例情况1：所述承载连接修改请求消息中包括至少一个第二创建EAR信息，所述至少一个第二创建EAR信息用于指示创建至少一个第二EAR；任一个第二创建EAR信息中包括所述任一个第二创建EAR信息指示创建的第二EAR的标识。
在此示例情况1中，表4所示的具体内容中包含创建EAR信息(即表4中的加粗倾斜格式的Create EAR)，在此处被称为第二创建EAR信息。其中，一种可选的实施方式，任一个第二创建EAR信息中包括的具体内容同样可以参见表2，具体的此处不再重复赘述。
示例情况2：所述承载连接修改请求消息中包括第二PDR，所述第二PDR中包括所述至少一个第一EAR中的部分或者全部的第一EAR的标识。
在此示例情况2中，所述第二PDR可以是相对于第一PDR更新的PDR，具体的所述第二PDR中包括的内容可以如下面涉及的表5示出的更新的PDR的内容。此时，表5中包括的EAR ID(表5中的加粗倾斜格式的)即为所述至少一个第一EAR中的部分或者全部的第一EAR的标识。
示例情况3：所述承载连接修改请求消息中包括所述至少一个第二创建EAR信息和第三PDR，所述第三PDR中包括所述至少一个第二EAR中的部分或者全部的第二EAR的标识。
在此示例情况3中，所述第三PDR可以是相对于第一PDR更新的PDR，具体的所述第三PDR种包括的内容同样可以参见下面涉及的表5中示出的更新的PDR的内容。此时，表5中包括的EAR ID即为所述至少一个第二EAR中的部分或者全部的第二EAR的标识。
示例情况4：示例情况1和示例情况2结合。
示例情况5：示例情况2和示例情况3结合。
需要说明的是，在此示例情况5中，所述第二PDR和所述第三PDR可以看成是同一个PDR。也就是说，在此示例情况5中，更新的PDR中既可以包含部分或全部的所述至少一个第一EAR的标识，同时还可以包含部分或者全部所述至少一个第二EAR的标识。
示例情况6：所述承载连接修改请求消息中包括删除EAR信息，所述删除EAR信息中包括需要删除的EAR的标识，其中，所述删除EAR信息用于指示删除所述需要删除的EAR的标识对应的EAR。
在此示例情况6中，所述删除EAR信息体现为表4中的删除EAR信息(即表4中的加粗倾斜格式的Remove EAR)。在一种可选的实施方式中，所述删除EAR信息中包括的内容可以如表6所示。其中，此种情况下，所述删除EAR信息中包含的EAR ID为当前已有的EAR的标识，例如，当目前只创建了所述至少一个第一EAR的情况下，可以为所述 至少一个第一EAR的标识中的部分或者全部，以使所述核心网用户面网元删除已创建的需要删除的EAR。
示例情况7：所述承载连接修改请求消息中包括更新EAR信息，所述更新EAR信息中包括需要更新的EAR的标识，所述更新EAR信息用于指示更新所述需要更新的EAR的标识对应的EAR。
在此示例情况7中，所述更新EAR信息体现为表4中的更新EAR信息(即表4中的加粗倾斜格式的Update EAR)。在一种可选的实施方式中，所述更新EAR信息中包括的内容可以如表7所示。其中，此种情况下，所述更新EAR信息中包含的EAR ID为当前已有的EAR的标识，例如，当目前只创建了所述至少一个第一EAR的情况下，可以为所述至少一个第一EAR的标识中的部分或者全部，以使所述核心网用户面网元更新已创建的需要删除的EAR。
需要说明的是，所述更新EAR信息除了对应的EAR的标识以外，还可以包含如表7中所示的其他内容，但是也不限于只是如表7所示的内容，还可以有出表7示出的内容以外的内容，本申请对此不作限定。
示例情况8：所述承载连接修改请求消息中包括所述删除EAR信息和所述更新EAR信息，也即示例情况6和示例情况7的结合。
示例情况9：示例情况1和示例情况6结合。
在此示例情况9中，是既创建了至少一个第一EAR又创建了至少一个第二EAR的情况，此时，所述删除EAR信息中包含的EAR ID可以是所述至少一个第一EAR的标识中的部分或者全部，以及所述至少一个第二EAR的标识中的部分或者全部。
示例情况10：示例情况1和示例情况7结合。
在此示例情况9中，是既创建了至少一个第一EAR又创建了至少一个第二EAR的情况，此时，所述更新EAR信息中包含的EAR ID可以是所述至少一个第一EAR的标识中的部分或者全部，以及所述至少一个第二EAR的标识中的部分或者全部。
示例情况11：示例情况1和示例情况8结合。此种情况也可以看作是示例情况9和示例情况10的结合，可以参见上述描述，此处不再赘述。
示例情况12：示例情况2和示例情况6结合。在此种情况中，当前已创建的EAR只有所述至少一个第一EAR，所以此时所述删除EAR信息中包含的EAR ID可以为所述至少一个第一EAR的标识中的部分或者全部。
示例情况13：示例情况2和示例情况7结合。在此种情况中，当前已创建的EAR只有所述至少一个第一EAR，所以此时所述更新EAR信息中包含的EAR ID可以为所述至少一个第一EAR的标识中的部分或者全部。
示例情况14：示例情况2和示例情况8结合。此情况也可以看作是示例12和示例情况13的结合，具体可以参见上述描述，此处不再详细描述。
示例情况15：示例情况3和示例情况6结合。
在此示例情况15中，是既创建了至少一个第一EAR又创建了至少一个第二EAR的情况，此时，所述删除EAR信息中包含的EAR ID可以是所述至少一个第一EAR的标识中的部分或者全部，以及所述至少一个第二EAR的标识中的部分或者全部。
示例情况16：示例情况3和示例情况7结合。
在此示例情况16中，是既创建了至少一个第一EAR又创建了至少一个第二EAR的 情况，此时，所述更新EAR信息中包含的EAR ID可以是所述至少一个第一EAR的标识中的部分或者全部，以及所述至少一个第二EAR的标识中的部分或者全部。
示例情况17：示例情况3和示例情况8结合。此情况也可以看作是示例15和示例情况16的结合，具体可以参见上述描述，此处不再详细描述。
示例情况18：示例情况4和示例情况6结合。
示例情况19：示例情况4和示例情况7结合。
示例情况20：示例情况4和示例情况8结合。
示例情况21：示例情况5和示例情况6结合。
示例情况22：示例情况5和示例情况7结合。
示例情况23：示例情况5和示例情况8结合。
示例情况18至示例情况23均可以参见上述相应示例情况中相关的介绍，本申请不再一一详细介绍。
表4承载连接修改请求消息
Figure PCTCN2019128021-appb-000006
Figure PCTCN2019128021-appb-000007
Figure PCTCN2019128021-appb-000008
Figure PCTCN2019128021-appb-000009
表5更新的PDR
Figure PCTCN2019128021-appb-000010
Figure PCTCN2019128021-appb-000011
表6删除EAR信息
Figure PCTCN2019128021-appb-000012
表7更新EAR信息
Figure PCTCN2019128021-appb-000013
示例性的，所述核心网控制面网元可以通过调用Sx Session Modification Request服务向所述核心网用户面网元发送所述承载连接修改请求消息。
步骤203、所述核心网用户面网元根据所述至少一个第一创建EAR信息，创建所述至少一个第一EAR，并对应保存创建的所述至少一个第一EAR以及第一EAR的标识。
在一种可选的实施方式中，所述核心网用户面网元可以将所述至少一个第一EAR以及第一EAR的标识保存至数据库中，其中所述数据库可以在所述核心网用户面网元本地，也可以独立于所述核心网用户面网元存在，本申请对此不作具体限定。当然，除了数据库，所述核心网用户面网元还可以将所述至少一个第一EAR保存在其它地方，本申请不再一一列举。
在一种可选的实施方式中，所述核心网用户面网元可以以表格形式保存所述至少一个第一EAR以及第一EAR的标识，也可以以其它形式保存，本申请对此不作限定。
具体的，所述核心网用户面网元在保存所述至少一个第一EAR时，同时保存所述至少一个第一EAR分别对应的标识，用来标识对应的第一EAR，以使后续方便查找相应的第一EAR。
在一种可选的实施方式中，所述核心网用户面网元执行了步骤203之后，所述核心网用户面网元会向所述核心网控制面网元回复承载连接响应消息，而后，所述核心网控制面网元就会进行后续通信流程，例如，所述核心网控制面网元可以与发起了PDN或者TDF会话的网元进行交互通信。
其中，示例性的，所述核心网用户面网元可以通过调用Sx Session Establishment Response服务向所述核心网控制面网元发送所述承载连接响应消息。
在一种可选的实施方式中，当所述承载连接请求消息中还包括步骤202中涉及的所述 第一PDR时，所述核心网用户面网元在接收到与所述第一PDR匹配的第一用户数据报文后，根据所述第一PDR中包含的所述至少一个第一EAR分别对应的标识，查找保存的所述至少一个第一EAR，并按照查找到的所述至少一个第一EAR对所述第一用户数据报文执行相应的动作。这样所述核心网用户面网元就可以执行FAR、URR和QER以外的执行规则了。
在一种可选的实施方式中，当所述核心网用户面网元从所述核心网控制面网元接收的所述承载连接修改请求消息中包括的内容不同，所述核心网用户面网元执行的操作也不同，结合步骤202涉及的示例情况1-示例情况23，所述核心网用户面网元执行的操作可以分为以下23种操作：
操作1：当所述承载连接修改请求消息为上述示例情况1中的情况时，所述核心网用户面网元可以根据所述至少一个第二创建EAR信息，创建所述至少一个第二EAR，并对应保存创建的所述至少一个第二EAR以及第二EAR的标识。
操作2：当所述承载连接修改请求消息为上述示例情况2中的情况时，所述核心网用户面网元在接收到与所述第二PDR匹配的第二用户数据报文后，根据所述第二PDR中包括的EAR的标识，在保存的所述至少一个第一EAR中查找所述第二PDR中包括的EAR的标识对应的第一EAR，并按照查找到的第一EAR对所述第二用户数据报文执行相应的动作。
操作3：当所述承载连接修改请求消息为上述示例情况3中的情况时，所述核心网用户面网元执行操作1，同时在接收到与所述第三PDR匹配的第三用户数据报文后，根据所述第三PDR中包括的EAR的标识，在保存的所述至少一个第二EAR中查找所述第三PDR中包括的EAR的标识对应的第二EAR，并按照查找到的第二EAR对第三用户数据报文执行相应的动作。
操作4：当所述承载连接修改请求消息为上述示例情况4中的情况时，所述核心网用户面网元执行操作1和操作2。
操作5：当所述承载连接修改请求消息为上述示例情况5中的情况时，所述核心网用户面网元执行操作2和操作3。
操作6：当所述承载连接修改请求消息为上述示例情况6中的情况时，所述核心网用户面网元根据所述需要删除的EAR的标识，在已保存的EAR中查找所述需要删除的EAR，并删除所述需要删除的EAR。例如，当目前只保存了所述至少一个第一EAR的情况下，所述核心网用户面网元需要删除的EAR为已保存的所述至少一个第一EAR中的部分或者全部。
操作7：当所述承载连接修改请求消息为上述示例情况7中的情况时，所述核心网用户面网元根据所述需要更新的EAR的标识，在已保存的EAR中查找所述需要更新的EAR，并删除所述需要更新的EAR。例如，当目前只保存了所述至少一个第一EAR的情况下，所述核心网用户面网元需要更新的EAR为已保存的所述至少一个第一EAR中的部分或者全部。
操作8：当所述承载连接修改请求消息为上述示例情况8中的情况时，所述核心网用户面网元执行操作6和操作7。
操作9：当所述承载连接修改请求消息为上述示例情况9中的情况时，所述核心网用户面网元执行操作1和操作6。此时，所述核心网用户面网元在执行操作6时，所述核心 网删除的EAR为已保存的部分或全部所述至少一个第一EAR，以及部分或全部所述至少一个第二EAR。
操作10：当所述承载连接修改请求消息为上述示例情况10中的情况时，所述核心网用户面网元执行操作1和操作7。此时，所述核心网用户面网元在执行操作7时，所述核心网更新的EAR为已保存的部分或全部所述至少一个第一EAR，以及部分或全部所述至少一个第二EAR。
操作11：当所述承载连接修改请求消息为上述示例情况11中的情况时，所述核心网用户面网元执行的操作可以参见操作9和操作10。
操作12：当所述承载连接修改请求消息为上述示例情况12中的情况时，所述核心网用户面网元执行操作2和操作6。
操作13：当所述承载连接修改请求消息为上述示例情况13中的情况时，所述核心网用户面网元执行操作2和操作7。
操作14：当所述承载连接修改请求消息为上述示例情况14中的情况时，所述核心网用户面网元执行的操作可以参见操作12和操作13。
操作15：当所述承载连接修改请求消息为上述示例情况15中的情况时，所述核心网用户面网元执行操作3和操作6。具体的，所述核心网用户面网元在执行操作6时可以参见操作9中的详细描述，此处不再重复赘述。
操作16：当所述承载连接修改请求消息为上述示例情况16中的情况时，所述核心网用户面网元执行操作3和操作7。具体的，所述核心网用户面网元在执行操作7时可以参见操作10中的详细描述，此处不再重复赘述。
操作17：当所述承载连接修改请求消息为上述示例情况17中的情况时，所述核心网用户面网元执行的操作可以参见操作15和操作16。
操作18：当所述承载连接修改请求消息为上述示例情况18中的情况时，所述核心网用户面网元执行操作1、操作2和操作6。具体的，所述核心网用户面网元在执行操作6时可以参见操作9中的详细描述，此处不再重复赘述。
操作19：当所述承载连接修改请求消息为上述示例情况19中的情况时，所述核心网用户面网元执行操作1、操作2和操作7。具体的，所述核心网用户面网元在执行操作7时可以参见操作10中的详细描述，此处不再重复赘述。
操作20：当所述承载连接修改请求消息为上述示例情况20中的情况时，所述核心网用户面网元执行的操作可以参见操作18和操作19。
操作21：当所述承载连接修改请求消息为上述示例情况21中的情况时，所述核心网用户面网元执行的操作可以参见操作3和操作9。
操作22：当所述承载连接修改请求消息为上述示例情况22中的情况时，所述核心网用户面网元执行的操作可以参见操作3和操作7。
操作23：当所述承载连接修改请求消息为上述示例情况23中的情况时，所述核心网用户面网元执行的操作可以参见操作21和操作22。
在一种可选的实施方式中，所述核心网用户面网元还会向所述核心网控制面网元发送承载连接修改响应消息，以使所述核心网控制面网元就会进行后续通信流程，例如，所述核心网控制面网元可以与发起了PDN或者TDF会话的网元进行交互通信。
其中，示例性的，所述核心网用户面网元可以通过调用Sx Session Modification  Response服务向所述核心网控制面网元发送所述承载连接修改响应消息。
采用本申请实施例提供的通信方法，核心网控制面网元确定需要触发核心网用户面网元进行承载连接时，向所述核心网用户面网元发送承载连接请求消息，所述核心网用户面网元根据所述承载连接请求消息包括的至少一个第一创建EAR信息，创建至少一个第一EAR，并对应保存创建的所述至少一个第一EAR以及第一EAR的标识。通过上述方法，所述核心网用户面网元可以执行FAR、URR和QER以外的执行规则对应的相关动作，从而达到扩展动作规则的目的，进而可以提高系统功能的完整性。
上述本申请提供的实施例中，分别从各个网元或设备本身、以及从各个网元或设备之间交互的角度对本申请实施例提供的通信方法的方案进行了介绍。可以理解的是，各个网元和设备，例如上述核心网控制面网元、核心网用户面网元为了实现上述功能，其包含了执行各个功能相应的硬件结构和/或软件单元。本领域技术人员应该很容易意识到，结合本申请中所公开的实施例描述的各示例的单元及算法步骤，本申请能够以硬件或硬件和计算机软件的结合形式来实现。某个功能究竟以硬件还是计算机软件驱动硬件的方式来执行，取决于技术方案的特定应用和设计约束条件。专业技术人员可以对每个特定的应用来使用不同方法来实现所描述的功能，但是这种实现不应认为超出本申请的范围。
例如，当上述网元或者设备通过软件单元来实现相应的功能时，可以参阅图4所示，本申请实施例提供的通信装置(用于执行通信方法的通信装置)可以包括处理单元401和收发单元402。
在一个实施例中，图4所示的通信装置可以用于执行上述图2所示的实施例中核心网控制面网元的操作。例如：
所述处理单元401用于确定需要触发核心网用户面网元进行承载连接；所述收发单元402用于向所述核心网用户面网元发送承载连接请求消息，所述承载连接请求消息中包括至少一个第一创建扩展动作规则EAR信息，所述至少一个第一创建EAR信息用于指示创建至少一个第一EAR，所述至少一个第一EAR为除转发动作规则FAR、使用量上报规则URR和服务质量执行规则QER以外的执行规则；任一个第一创建EAR信息中包括所述任一个第一创建EAR信息指示创建的第一EAR的标识。
因此，基于上述通信装置，可以使所述核心网用户面网元根据所述承载连接请求消息包括的至少一个第一创建EAR信息，创建至少一个第一EAR，并保存所述至少一个第一EAR。从而所述核心网用户面网元后续可以执行FAR、URR和QER以外的执行规则对应的相关动作，从而达到扩展动作规则的目的，进而可以提高系统功能的完整性。
在一种可选的实施方式中，所述承载连接请求消息中还包括第一PDR，所述第一PDR中包括所述至少一个第一EAR分别对应的标识。
在一种可选的实施方式中，所述处理单元401还用于确定需要触发所述核心网用户面网元更新承载连接；进而，所述收发单元402还用于向所述核心网用户面网元发送承载连接修改请求消息，所述承载连接修改请求消息中包括至少一个第二创建EAR信息，所述至少一个第二创建EAR信息用于指示创建至少一个第二EAR；任一个第二创建EAR信息中包括所述任一个第二创建EAR信息指示创建的第二EAR的标识。
在一种可选的实施方式中，所述承载连接修改请求消息中还包括第二PDR，所述第二PDR中包括至少一个第三EAR的标识，所述至少一个第三EAR为以下EAR中的部分或全部：所述至少一个第一EAR和/或所述至少一个第二EAR。
在一种可选的实施方式中，所述处理单元401还用于确定需要触发所述核心网用户面网元更新承载连接；进而所述收发单元402还用于向所述核心网用户面网元发送承载连接修改请求消息，所述承载连接修改请求消息中包括删除EAR信息和/或更新EAR信息，所述删除EAR信息中包括需要删除的EAR的标识，所述更新EAR信息中包括需要更新的EAR的标识；其中，所述删除EAR信息用于指示删除所述需要删除的EAR的标识对应的EAR，所述更新EAR信息用于指示更新所述需要更新的EAR的标识对应的EAR。
在另一个实施例中，图4所示的通信装置还可以用于执行上述图2所示的实施例中核心网用户面网元的操作。例如：
所述收发单元402用于从核心网控制面网元接收承载连接请求消息，所述承载连接请求消息中包括至少一个第一创建扩展动作规则EAR信息，所述至少一个第一创建EAR信息用于指示创建至少一个第一EAR，所述至少一个第一EAR为除转发动作规则FAR、使用量上报规则URR和服务质量执行规则QER以外的执行规则；任一个第一创建EAR信息中包括所述任一个第一创建EAR信息指示创建的第一EAR的标识；所述处理单元401用于根据所述至少一个第一创建EAR信息，创建所述至少一个第一EAR，并保存对应保存创建的所述至少一个第一EAR以及第一EAR的标识。
因此，基于上述通信装置，核心网用户面网元后续可以执行FAR、URR和QER以外的执行规则对应的相关动作，从而达到扩展动作规则的目的，进而可以提高系统功能的完整性。
在一种可选的实施方式中，所述承载连接请求消息中还包括第一PDR，所述第一PDR中包括所述至少一个第一EAR分别对应的标识；相应的，所述收发单元402还用于接收第一用户数据报文；进而所述处理单元401还用于在所收发单元402接收到与所述第一PDR匹配的第一用户数据报文后，根据所述第一PDR中包含的所述至少一个第一EAR分别对应的标识，查找保存的所述至少一个第一EAR，并按照查找到的所述至少一个第一EAR对所述第一用户数据报文执行相应的动作。
在一种可选的实施方式中，所述收发单元402还用于从所述核心网控制面网元接收承载连接修改请求消息，所述承载连接修改请求消息中包括至少一个第二创建EAR信息，所述至少一个第二创建EAR信息用于指示创建至少一个第二EAR；任一个第二创建EAR信息中包括所述任一个第二创建EAR信息指示创建的第二EAR的标识；相应的所述处理单元401还用于根据所述至少一个第二创建EAR信息，创建所述至少一个第二EAR，并对应保存创建的所述至少一个第二EAR以及第二EAR的标识。
在一种可选的实施方式中，所述承载连接修改请求消息中还包括第二PDR，所述第二PDR中包括至少一个第三EAR的标识，所述至少一个第三EAR为以下EAR中的部分或全部：所述至少一个第一EAR和/或所述至少一个第二EAR；相应的所述收发单元402还用于接收第二用户数据报文；进而所述处理单元401还用于在所述收发单元接收到与所述第二PDR匹配的第二用户数据报文后，根据所述至少一个第三EAR的标识，在保存的所述至少一个第一EAR和/或所述至少一个第二EAR中查找所述至少一个第三EAR，并按照查找到的所述至少一个第三EAR对所述第二用户数据报文执行相应的动作。
在另一种可选的实施方式中，所述收发单元402还用于从所述核心网控制面网元接收承载连接修改请求消息，所述承载连接修改请求消息中包括删除EAR信息和/或更新EAR信息，所述删除EAR信息中包括需要删除的EAR的标识，所述更新EAR信息中包括需 要更新的EAR的标识；其中，所述删除EAR信息用于指示删除所述需要删除的EAR的标识对应的EAR，所述更新EAR信息用于指示更新所述需要更新的EAR的标识对应的EAR。
在一种实现方式中，当所述承载连接修改请求消息中包括所述删除EAR信息时，所述处理单元401还用于根据所述需要删除的EAR的标识，在已保存的EAR中查找所述需要删除的EAR，并删除所述需要删除的EAR。
在另一种实现方式中，当所述承载连接修改请求消息中包括所述更新EAR信息时，所述处理单元401还用于根据所述需要更新的EAR的标识，在已保存的EAR中查找所述需要更新的EAR，并更新所述需要更新的EAR。
需要说明的是，本申请实施例中对单元的划分是示意性的，仅仅为一种逻辑功能划分，实际实现时可以有另外的划分方式。在本申请的实施例中的各功能单元可以集成在一个处理单元中，也可以是各个单元单独物理存在，也可以两个或两个以上单元集成在一个单元中。上述集成的单元既可以采用硬件的形式实现，也可以采用软件功能单元的形式实现。
所述集成的单元如果以软件功能单元的形式实现并作为独立的产品销售或使用时，可以存储在一个计算机可读取存储介质中。基于这样的理解，本申请的技术方案本质上或者说对现有技术做出贡献的部分或者该技术方案的全部或部分可以以软件产品的形式体现出来，该计算机软件产品存储在一个存储介质中，包括若干指令用以使得一台计算机设备(可以是个人计算机，服务器，或者网络设备等)或处理器(processor)执行本申请各个实施例所述方法的全部或部分步骤。而前述的存储介质包括：U盘、移动硬盘、只读存储器(read-only memory，ROM)、随机存取存储器(random access memory，RAM)、磁碟或者光盘等各种可以存储程序代码的介质。
又例如，当上述网元或者设备通过硬件来实现相应的功能时，本申请提供的通信装置(用于执行通信方法的通信装置)可以包括收发器501和处理器502，可选的还可以包括存储器503，可以参考如图5所示结构图。
例如，所述处理器502可以是中央处理器(central processing unit，CPU)，网络处理器(network processor，NP)或者CPU和NP的组合等等。所述处理器502还可以进一步包括硬件芯片。上述硬件芯片可以是专用集成电路(application-specific integrated circuit，ASIC)，可编程逻辑器件(programmable logic device，PLD)或其组合。上述PLD可以是复杂可编程逻辑器件(complex programmable logic device，CPLD)，现场可编程逻辑门阵列(field-programmable gate array，FPGA)，通用阵列逻辑(generic array logic，GAL)或其任意组合。所述处理器502在实现上述功能时，可以通过硬件实现，当然也可以通过硬件执行相应的软件实现。
所述收发器501和所述处理器502之间相互连接。可选的，所述收发器501和所述处理器502通过总线504相互连接；所述总线504可以是外设部件互连标准(Peripheral Component Interconnect，PCI)总线或扩展工业标准结构(Extended Industry Standard Architecture，EISA)总线等。总线可以分为地址总线、数据总线、控制总线等。为便于表示，图5中仅用一条粗线表示，但并不表示仅有一根总线或一种类型的总线。
所述存储器503，与所述处理器502耦合，用于存放通信装置必要的程序等。例如，程序可以包括程序代码，该程序代码包括计算机操作指令。所述存储器503可能包括RAM，也可能还包括非易失性存储器(non-volatile memory)，例如至少一个磁盘存储器。所述处 理器502执行所述存储器503所存放的应用程序，实现所述通信装置的功能。
在一个实施例中，图5所示的通信装置可用于执行上述图2所示的实施例中的核心网控制面网元的操作。例如：所述收发器501用于实现与所述核心网控制面网元相连的其他设备或网元进行通信交互，即用于接收和发送数据；所述处理器502被配置为执行所述核心网控制面网元的其他操作或功能。
在另一个实施例中，图5所示的通信装置还可用于执行上述图2所示的实施例中的核心网用户面网元的操作。例如：所述收发器501用于实现与所述核心网用户面网元相连的其他设备或网元进行通信交互，即用于接收和发送数据；所述处理器502被配置为执行所述核心网用户面网元的其他操作或功能。
在一种可选的实施方式中，所述存储器403还可以用于保存所述核心网用户面网元创建的EAR(例如上述实施例中涉及的至少一个第一EAR和/或至少一个第二EAR)。
综上所述，通过本申请实施例提供一种通信方法及装置，核心网控制面网元确定需要触发核心网用户面网元进行承载连接时，向所述核心网用户面网元发送承载连接请求消息，所述核心网用户面网元根据所述承载连接请求消息包括的至少一个第一创建EAR信息，创建至少一个第一EAR，并保存所述至少一个第一EAR。通过上述方法，所述核心网用户面网元可以执行FAR、URR和QER以外的执行规则对应的相关动作，从而达到扩展动作规则的目的，进而可以提高系统功能的完整性。
本领域内的技术人员应明白，本申请的实施例可提供为方法、系统、或计算机程序产品。因此，本申请可采用完全硬件实施例、完全软件实施例、或结合软件和硬件方面的实施例的形式。而且，本申请可采用在一个或多个其中包含有计算机可用程序代码的计算机可用存储介质(包括但不限于磁盘存储器、CD-ROM、光学存储器等)上实施的计算机程序产品的形式。
本申请是参照根据本申请实施例的方法、设备(系统)、和计算机程序产品的流程图和/或方框图来描述的。应理解可由计算机程序指令实现流程图和/或方框图中的每一流程和/或方框、以及流程图和/或方框图中的流程和/或方框的结合。可提供这些计算机程序指令到通用计算机、专用计算机、嵌入式处理机或其他可编程数据处理设备的处理器以产生一个机器，使得通过计算机或其他可编程数据处理设备的处理器执行的指令产生用于实现在流程图一个流程或多个流程和/或方框图一个方框或多个方框中指定的功能的装置。
这些计算机程序指令也可存储在能引导计算机或其他可编程数据处理设备以特定方式工作的计算机可读存储器中，使得存储在该计算机可读存储器中的指令产生包括指令装置的制造品，该指令装置实现在流程图一个流程或多个流程和/或方框图一个方框或多个方框中指定的功能。
这些计算机程序指令也可装载到计算机或其他可编程数据处理设备上，使得在计算机或其他可编程设备上执行一系列操作步骤以产生计算机实现的处理，从而在计算机或其他可编程设备上执行的指令提供用于实现在流程图一个流程或多个流程和/或方框图一个方框或多个方框中指定的功能的步骤。
显然，本领域的技术人员可以对本申请实施例进行各种改动和变型而不脱离本申请实施例的范围。这样，倘若本申请实施例的这些修改和变型属于本申请权利要求及其等同技术的范围之内，则本申请也意图包含这些改动和变型在内。

Claims (28)

  1. 一种通信方法，其特征在于，包括：
    核心网控制面网元确定需要触发核心网用户面网元进行承载连接；
    所述核心网控制面网元向所述核心网用户面网元发送承载连接请求消息，所述承载连接请求消息中包括至少一个第一创建扩展动作规则EAR信息，所述至少一个第一创建EAR信息用于指示创建至少一个第一EAR，所述至少一个第一EAR为除转发动作规则FAR、使用量上报规则URR和服务质量执行规则QER以外的执行规则；任一个第一创建EAR信息中包括所述任一个第一创建EAR信息指示创建的第一EAR的标识。
  2. 如权利要求1所述的方法，其特征在于，所述承载连接请求消息中还包括第一报文检测规则PDR，所述第一PDR中包括所述至少一个第一EAR分别对应的标识。
  3. 如权利要求1或2所述的方法，其特征在于，所述方法还包括：
    所述核心网控制面网元确定需要触发所述核心网用户面网元更新承载连接；
    所述核心网控制面网元向所述核心网用户面网元发送承载连接修改请求消息，所述承载连接修改请求消息中包括至少一个第二创建EAR信息，所述至少一个第二创建EAR信息用于指示创建至少一个第二EAR；任一个第二创建EAR信息中包括所述任一个第二创建EAR信息指示创建的第二EAR的标识。
  4. 如权利要求3所述的方法，其特征在于，所述承载连接修改请求消息中还包括第二PDR，所述第二PDR中包括至少一个第三EAR的标识，所述至少一个第三EAR为以下EAR中的部分或全部：所述至少一个第一EAR和/或所述至少一个第二EAR。
  5. 如权利要求1或2所述的方法，其特征在于，所述方法还包括：
    所述核心网控制面网元确定需要触发所述核心网用户面网元更新承载连接；
    所述核心网控制面网元向所述核心网用户面网元发送承载连接修改请求消息，所述承载连接修改请求消息中包括删除EAR信息和/或更新EAR信息，所述删除EAR信息中包括需要删除的EAR的标识，所述更新EAR信息中包括需要更新的EAR的标识；
    其中，所述删除EAR信息用于指示删除所述需要删除的EAR的标识对应的EAR，所述更新EAR信息用于指示更新所述需要更新的EAR的标识对应的EAR。
  6. 一种通信方法，其特征在于，包括：
    核心网用户面网元从核心网控制面网元接收承载连接请求消息，所述承载连接请求消息中包括至少一个第一创建扩展动作规则EAR信息，所述至少一个第一创建EAR信息用于指示创建至少一个第一EAR，所述至少一个第一EAR为除转发动作规则FAR、使用量上报规则URR和服务质量执行规则QER以外的执行规则；任一个第一创建EAR信息中包括所述任一个第一创建EAR信息指示创建的第一EAR的标识；
    所述核心网用户面网元根据所述至少一个第一创建EAR信息，创建所述至少一个第一EAR，并对应保存创建的所述至少一个第一EAR以及第一EAR的标识。
  7. 如权利要求6所述的方法，其特征在于，所述承载连接请求消息中还包括第一报文检测规则PDR，所述第一PDR中包括所述至少一个第一EAR分别对应的标识；所述方法还包括：
    所述核心网用户面网元在接收到与所述第一PDR匹配的第一用户数据报文后，根据所述第一PDR中包含的所述至少一个第一EAR分别对应的标识，查找保存的所述至少一个 第一EAR，并按照查找到的所述至少一个第一EAR对所述第一用户数据报文执行相应的动作。
  8. 如权利要求6或7所述的方法，其特征在于，所述方法还包括：
    所述核心网用户面网元从所述核心网控制面网元接收承载连接修改请求消息，所述承载连接修改请求消息中包括至少一个第二创建EAR信息，所述至少一个第二创建EAR信息用于指示创建至少一个第二EAR；任一个第二创建EAR信息中包括所述任一个第二创建EAR信息指示创建的第二EAR的标识；
    所述核心网用户面网元根据所述至少一个第二创建EAR信息，创建所述至少一个第二EAR，并对应保存创建的所述至少一个第二EAR以及第二EAR的标识。
  9. 如权利要求8所述的方法，其特征在于，所述承载连接修改请求消息中还包括第二PDR，所述第二PDR中包括至少一个第三EAR的标识，所述至少一个第三EAR为以下EAR中的部分或全部：所述至少一个第一EAR和/或所述至少一个第二EAR；
    所述方法还包括：
    所述核心网用户面网元在接收到与所述第二PDR匹配的第二用户数据报文后，根据所述至少一个第三EAR的标识，在保存的所述至少一个第一EAR和/或所述至少一个第二EAR中查找至少一个第三EAR，并按照查找的所述至少一个第三EAR对所述第二用户数据报文执行相应的动作。
  10. 如权利要求6或7所述的方法，其特征在于，所述方法还包括：
    所述核心网用户面网元从所述核心网控制面网元接收承载连接修改请求消息，所述承载连接修改请求消息中包括删除EAR信息和/或更新EAR信息，所述删除EAR信息中包括需要删除的EAR的标识，所述更新EAR信息中包括需要更新的EAR的标识；
    其中，所述删除EAR信息用于指示删除所述需要删除的EAR的标识对应的EAR，所述更新EAR信息用于指示更新所述需要更新的EAR的标识对应的EAR；
    当所述承载连接修改请求消息中包括所述删除EAR信息时，所述核心网用户面网元根据所述需要删除的EAR的标识，在已保存的EAR中查找所述需要删除的EAR，并删除所述需要删除的EAR；
    当所述承载连接修改请求消息中包括所述更新EAR信息时，所述核心网用户面网元根据所述需要更新的EAR的标识，在已保存的EAR中查找所述需要更新的EAR，并更新所述需要更新的EAR。
  11. 一种通信装置，应用于核心网控制面网元，其特征在于，包括：
    处理单元，用于确定需要触发核心网用户面网元进行承载连接；
    收发单元，用于向所述核心网用户面网元发送承载连接请求消息，所述承载连接请求消息中包括至少一个第一创建扩展动作规则EAR信息，所述至少一个第一创建EAR信息用于指示创建至少一个第一EAR，所述至少一个第一EAR为除转发动作规则FAR、使用量上报规则URR和服务质量执行规则QER以外的执行规则；任一个第一创建EAR信息中包括所述任一个第一创建EAR信息指示创建的第一EAR的标识。
  12. 如权利要求11所述的装置，其特征在于，所述承载连接请求消息中还包括第一报文检测规则PDR，所述第一PDR中包括所述至少一个第一EAR分别对应的标识。
  13. 如权利要求11或12所述的装置，其特征在于，
    所述处理单元，还用于确定需要触发所述核心网用户面网元更新承载连接；
    所述收发单元，还用于向所述核心网用户面网元发送承载连接修改请求消息，所述承载连接修改请求消息中包括至少一个第二创建EAR信息，所述至少一个第二创建EAR信息用于指示创建至少一个第二EAR；任一个第二创建EAR信息中包括所述任一个第二创建EAR信息指示创建的第二EAR的标识。
  14. 如权利要求13所述的装置，其特征在于，所述承载连接修改请求消息中还包括第二PDR，所述第二PDR中包括至少一个第三EAR的标识，所述至少一个第三EAR为以下EAR中的部分或全部：所述至少一个第一EAR和/或所述至少一个第二EAR。
  15. 如权利要求11或12所述的装置，其特征在于，
    所述处理单元，还用于确定需要触发所述核心网用户面网元更新承载连接；
    所述收发单元，还用于向所述核心网用户面网元发送承载连接修改请求消息，所述承载连接修改请求消息中包括删除EAR信息和/或更新EAR信息，所述删除EAR信息中包括需要删除的EAR的标识，所述更新EAR信息中包括需要更新的EAR的标识；
    其中，所述删除EAR信息用于指示删除所述需要删除的EAR的标识对应的EAR，所述更新EAR信息用于指示更新所述需要更新的EAR的标识对应的EAR。
  16. 一种通信装置，应用于核心网用户面网元，其特征在于，包括：
    收发单元，用于从核心网控制面网元接收承载连接请求消息，所述承载连接请求消息中包括至少一个第一创建扩展动作规则EAR信息，所述至少一个第一创建EAR信息用于指示创建至少一个第一EAR，所述至少一个第一EAR为除转发动作规则FAR、使用量上报规则URR和服务质量执行规则QER以外的执行规则；任一个第一创建EAR信息中包括所述任一个第一创建EAR信息指示创建的第一EAR的标识；
    处理单元，用于根据所述至少一个第一创建EAR信息，创建所述至少一个第一EAR，并对应保存创建的所述至少一个第一EAR以及第一EAR的标识。
  17. 如权利要求16所述的装置，其特征在于，所述承载连接请求消息中还包括第一报文检测规则PDR，所述第一PDR中包括所述至少一个第一EAR分别对应的标识；
    所述收发单元，还用于接收用户数据报文；
    所述处理单元，还用于在所收发单元接收到与所述第一PDR匹配的第一用户数据报文后，根据所述第一PDR中包含的所述至少一个第一EAR分别对应的标识，查找保存的所述至少一个第一EAR，并按照查找到的所述至少一个第一EAR对所述第一用户数据报文执行相应的动作。
  18. 如权利要求16或17所述的装置，其特征在于，
    所述收发单元，还用于从所述核心网控制面网元接收承载连接修改请求消息，所述承载连接修改请求消息中包括至少一个第二创建EAR信息，所述至少一个第二创建EAR信息用于指示创建至少一个第二EAR；任一个第二创建EAR信息中包括所述任一个第二创建EAR信息指示创建的第二EAR的标识；
    所述处理单元，还用于根据所述至少一个第二创建EAR信息，创建所述至少一个第二EAR，并对应保存创建的所述至少一个第二EAR以及第二EAR的标识。
  19. 如权利要求18所述的装置，其特征在于，所述承载连接修改请求消息中还包括第二PDR，所述第二PDR中包括至少一个第三EAR的标识，所述至少一个第三EAR为以下EAR中的部分或全部：所述至少一个第一EAR和/或所述至少一个第二EAR；
    所述收发单元，还用于接收用户数据报文；
    所述处理单元，还用于在所述收发单元接收到与所述第二PDR匹配的第二用户数据报文后，根据所述至少一个第三EAR的标识，在保存的所述至少一个第一EAR和/或所述至少一个第二EAR中查找至少一个第三EAR，并按照查找的所述至少一个第三EAR对所述第二用户数据报文执行相应的动作。
  20. 如权利要求16或17所述的装置，其特征在于，所述收发单元，还用于：
    从所述核心网控制面网元接收承载连接修改请求消息，所述承载连接修改请求消息中包括删除EAR信息和/或更新EAR信息，所述删除EAR信息中包括需要删除的EAR的标识，所述更新EAR信息中包括需要更新的EAR的标识；
    其中，所述删除EAR信息用于指示删除所述需要删除的EAR的标识对应的EAR，所述更新EAR信息用于指示更新所述需要更新的EAR的标识对应的EAR；
    当所述承载连接修改请求消息中包括所述删除EAR信息时，所述处理单元，还用于：
    根据所述需要删除的EAR的标识，在已保存的EAR中查找所述需要删除的EAR，并删除所述需要删除的EAR；
    当所述承载连接修改请求消息中包括所述更新EAR信息时，所述处理单元，还用于：
    根据所述需要更新的EAR的标识，在已保存的EAR中查找所述需要更新的EAR，并更新所述需要更新的EAR。
  21. 一种通信装置，应用于核心网控制面网元，其特征在于，包括：
    收发器，用于接收和发送数据；
    处理器，用于调用程序指令使得所述通信装置实现权利要求1-5任一项所述的方法。
  22. 一种通信装置，应用于核心网用户面网元，其特征在于，包括：
    收发器，用于接收和发送数据；
    处理器，用于调用程序指令使得所述通信装置实现权利要求6-10任一项所述的方法。
  23. 一种通信装置，其特征在于，用于执行权利要求1-5任一项所述的方法。
  24. 一种通信装置，其特征在于，用于执行权利要求6-10任一项所述的方法。
  25. 一种包含指令的计算机程序产品，其特征在于，当所述计算机程序产品在计算机上运行时，使得计算机执行如权利要求1-10任一项所述的方法。
  26. 一种计算机存储介质，其特征在于，所述计算机存储介质中存储有计算机程序，所述计算机程序被计算机执行时，使得所述计算机执行如权利要求1-10任一项所述的方法。
  27. 一种芯片，其特征在于，所述芯片与存储器耦合，用于读取并执行所述存储器中存储的程序指令，以实现如权利要求1-10任一项所述的方法。
  28. 一种通信系统，其特征在于，包括如权利要求11-15、21、23任一项所述的装置，和权利要求16-20、22、24任一项所述的装置。
PCT/CN2019/128021 2018-12-25 2019-12-24 一种通信方法及装置 WO2020135440A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201811588219.2 2018-12-25
CN201811588219.2A CN111372322B (zh) 2018-12-25 2018-12-25 一种通信方法及装置

Publications (1)

Publication Number Publication Date
WO2020135440A1 true WO2020135440A1 (zh) 2020-07-02

Family

ID=71126067

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2019/128021 WO2020135440A1 (zh) 2018-12-25 2019-12-24 一种通信方法及装置

Country Status (2)

Country Link
CN (1) CN111372322B (zh)
WO (1) WO2020135440A1 (zh)

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102474519A (zh) * 2009-08-10 2012-05-23 高通股份有限公司 用于处理策略和计费控制规则或服务质量规则修改失败的方法和装置
CN103444154A (zh) * 2011-03-23 2013-12-11 瑞典爱立信有限公司 用于控制通知服务中的动作的方法和布置
EP3076741A1 (en) * 2015-03-31 2016-10-05 Alcatel Lucent Method for managing routing in a content distribution network in a mobile network

Family Cites Families (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN110461012B (zh) * 2014-09-05 2022-09-02 华为技术有限公司 一种分流策略协商方法及装置
CN108282342B (zh) * 2017-01-05 2021-04-09 华为技术有限公司 计费管理方法、用户面功能实体以及控制面功能实体

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102474519A (zh) * 2009-08-10 2012-05-23 高通股份有限公司 用于处理策略和计费控制规则或服务质量规则修改失败的方法和装置
CN103444154A (zh) * 2011-03-23 2013-12-11 瑞典爱立信有限公司 用于控制通知服务中的动作的方法和布置
EP3076741A1 (en) * 2015-03-31 2016-10-05 Alcatel Lucent Method for managing routing in a content distribution network in a mobile network

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
3GPP TECHNICAL SPECIFICATION GROUP CORE NETWORK AND TERMINALS: "3rd Generation Partnership Project; Technical Specification Group Core Network and Terminals; Interface between the Control Plane and the User Plane Nodes; Stage 3 (Release 15)", 3GPP STANDARD; TECHNICAL SPECIFICATION; 3GPP TS 29.244, no. V15.4.0, 22 December 2018 (2018-12-22), pages 1 - 194, XP051591546 *

Also Published As

Publication number Publication date
CN111372322B (zh) 2022-04-12
CN111372322A (zh) 2020-07-03

Similar Documents

Publication Publication Date Title
CN111698725A (zh) 动态确定网络切片的方法及电子设备
WO2019223660A1 (zh) 会话管理方法、装置和系统
US11233694B2 (en) Method and device for processing communication path
US8270942B2 (en) Method for the interception of GTP-C messages
WO2017070958A1 (zh) 一种网关配置方法和网关设备
US10165618B2 (en) Service processing method and device
WO2018006306A1 (zh) 一种网络连接配置方法及装置
CN112152923B (zh) 用户面重路由方法及装置
WO2018018631A1 (zh) 一种锚点网关的切换方法、装置及系统
KR102246978B1 (ko) 라우팅 방법 및 장치
CN108353022A (zh) 一种数据报文的处理方法、装置及系统
US20230058366A1 (en) Managing Service Function Chains
WO2021134446A1 (zh) 一种信息处理方法和通信装置以及通信系统
WO2019096306A1 (zh) 一种处理请求的方法以及相应实体
WO2019137539A1 (zh) 软件升级方法及系统
CN113613234A (zh) 一种策略管理的方法及装置
CN112312481B (zh) 一种mec与多运营商核心网的通信方法及系统
CN104521201B (zh) 转发节点的处理方法、转发节点及控制节点
CN106162733A (zh) 一种异常流量抑制方法及装置
WO2020135440A1 (zh) 一种通信方法及装置
WO2022057724A1 (zh) 数据分流方法和装置
WO2021008402A1 (zh) 支持端口关联的方法、网关选择的方法及通信设备
WO2023208122A1 (zh) 接入切换方法、amf实体、通信系统和存储介质
EP2285177A2 (en) Method for operating packet data protocol context and apparatus therefor
WO2018228309A1 (zh) 缓存控制方法、网元及控制器

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 19902148

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 19902148

Country of ref document: EP

Kind code of ref document: A1