WO2024259918A1 - 消息传输方法、装置、系统、设备和存储介质 - Google Patents

消息传输方法、装置、系统、设备和存储介质 Download PDF

Info

Publication number
WO2024259918A1
WO2024259918A1 PCT/CN2023/138762 CN2023138762W WO2024259918A1 WO 2024259918 A1 WO2024259918 A1 WO 2024259918A1 CN 2023138762 W CN2023138762 W CN 2023138762W WO 2024259918 A1 WO2024259918 A1 WO 2024259918A1
Authority
WO
WIPO (PCT)
Prior art keywords
interface
protocol message
function entity
initial
network element
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Ceased
Application number
PCT/CN2023/138762
Other languages
English (en)
French (fr)
Inventor
刘双月
丁海峰
王波
王庆扬
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
China Telecom Corp Ltd
Original Assignee
China Telecom Corp Ltd
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 China Telecom Corp Ltd filed Critical China Telecom Corp Ltd
Publication of WO2024259918A1 publication Critical patent/WO2024259918A1/zh
Anticipated expiration legal-status Critical
Ceased legal-status Critical Current

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/12—Messaging; Mailboxes; Announcements
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W28/00—Network traffic management; Network resource management
    • H04W28/02—Traffic management, e.g. flow control or congestion control
    • H04W28/06—Optimizing the usage of the radio link, e.g. header compression, information sizing, discarding information
    • H04W28/065—Optimizing the usage of the radio link, e.g. header compression, information sizing, discarding information using assembly or disassembly of packets
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/10—Connection setup

Definitions

  • the present application relates to the field of wireless communication technologies, and in particular to a message transmission method, apparatus, system, device and storage medium.
  • the Serving Gateway (SGW) entity and the Packet Data Network Gateway (PGW) entity in the 4G network are respectively integrated with the Session Management Function (SMF) and the User Plane Function (UPF) in the 5G network.
  • the integration logic includes two types, namely, the SGW and PGW logical separation and the SGW and PGW logical integration.
  • the present application provides a message transmission method, the method comprising:
  • the initial PFCP protocol message is reconstructed to obtain a target PFCP protocol message, including: determining a reconstruction forwarding rule according to a network element fusion mode of the session management function entity and a network element fusion mode of the user plane function entity; and reconstructing the initial PFCP protocol message according to the reconstruction forwarding rule to obtain a target PFCP protocol message.
  • a reconstructed forwarding rule is determined according to a network element integration mode of the session management function entity and a network element integration mode of the user plane function entity, including: when the network element integration mode of the session management function entity is to logically separate the function of the SGW and the function of the PGW, a first forwarding rule is used as the reconstructed forwarding rule, and the first forwarding rule includes outputting data from the first interface from the second interface.
  • the initial PFCP protocol message includes a first parameter group and a second parameter group, the first parameter group corresponds to one of the SGW and the PGW, and the second parameter group corresponds to the other of the SGW and the PGW; the initial PFCP protocol message is reconstructed according to the reconstructed forwarding rule to obtain a target PFCP protocol message, including: deleting the first PDR data and the first FAR data in the first parameter group; according to the first forwarding rule, identifying the second PDR data in the second parameter group using the interface name of the first interface; binding the identified second PDR data, the second FAR data in the second parameter group, and other parameters in the second parameter group to a newly created PFCP protocol message to obtain the target PFCP protocol message; wherein the second FAR data in the second parameter group includes the interface name identifier of the second interface.
  • the first interface is an S1-U interface and the second interface is an SGI interface; if the initial PFCP protocol message is downlink data, the first interface is an SGI interface and the second interface is an S1-U interface.
  • a reconstructed forwarding rule is determined according to a network element integration mode of the session management function entity and a network element integration mode of the user plane function entity, including: when the network element integration mode of the session management function entity is to logically integrate the function of the SGW and the function of the PGW, a second forwarding rule is used as the reconstructed forwarding rule, and the second forwarding rule includes forwarding data from the first interface to the intermediate interface, and outputting data from the intermediate interface from the second interface.
  • the initial PFCP protocol message includes a third parameter group, the third parameter group includes third PDR data and third FAR data; the initial PFCP protocol message is reconstructed according to the reconstruction forwarding rule to obtain a target PFCP protocol message, including: replacing the original FAR identifier included in the third PDR data with the FAR identifier of the newly added FAR data to obtain a modified third PDR data, and obtain a fourth parameter group according to the modified third PDR data and the newly added FAR data; wherein the modified third PDR data includes the interface name identifier of the first interface, and the newly added FAR data includes the interface name of the intermediate interface; the interface name of the intermediate interface is used to replace the interface name of the first interface included in the third PDR data to obtain the replaced third PDR data, and obtain a fifth parameter group according to the replaced third PDR data and the third FAR data; wherein the third FAR data includes the interface name of the second interface; and obtain the target PFCP protocol message according to the fourth parameter group and the fifth parameter group.
  • the first interface is an S1-U interface
  • the intermediate interface is an S5/S8 interface
  • the second interface is an SGI interface
  • the first interface is an SGI interface
  • the intermediate interface is an S5/S8 interface
  • the second interface is an S1-U interface
  • determining whether the initial PFCP protocol message is a target message type includes: determining whether the initial PFCP protocol message is the target message type based on multiple target interface fields in the PFCP protocol message; the multiple target interface fields include at least a source interface field, a destination interface field, and a 3GPP interface type field.
  • the target message type is a 4G session establishment message.
  • the method further includes: if the initial PFCP protocol message is not a message for establishing the 4G session, directly sending the initial PFCP protocol message to the user plane function entity.
  • the first FDR data and the first FAR data in the first parameter group are deleted, including deleting the FAR ID, QER ID and URR ID in the first PDR data, and deleting the interface name of the intermediate interface in the first FAR data.
  • determining whether the network element integration mode of the session management function entity matches the network element integration mode of the user plane function entity includes:
  • the present application provides a message transmission device, the device comprising:
  • a first determination module is used to receive an initial PFCP protocol message sent by a session management function entity, and identify the initial PFCP protocol message to determine whether the initial PFCP protocol message is a target message type;
  • a second determination module is used to determine whether the network element fusion mode of the session management function entity and the network element fusion mode of the user plane function entity match each other when the initial PFCP protocol message is of the target message type, and the network element fusion mode is used to indicate a mode of fusion of the network element functions of the SGW and the PGW;
  • the reconstruction module is used to reconstruct the initial PFCP protocol message in the case of mismatch, obtain the target PFCP protocol message, and send the target PFCP protocol message to the user plane function entity.
  • the reconstruction module is specifically used to: determine the reconstruction forwarding rule according to the network element fusion mode of the session management function entity and the network element fusion mode of the user plane function entity; reconstruct the initial PFCP protocol message according to the reconstruction forwarding rule to obtain the target PFCP protocol message.
  • the reconstruction module is specifically used to: when the network element fusion mode of the session management function entity is to logically separate the function of the SGW and the function of the PGW, use the first forwarding rule as the reconstructed forwarding rule, and the first forwarding rule includes outputting data from the first interface from the second interface.
  • the initial PFCP protocol message includes a first parameter group and a second parameter group, the first parameter group corresponds to one of the SGW and the PGW, and the second parameter group corresponds to the other of the SGW and the PGW; a reconstruction module is specifically used to: delete the first PDR data and the first FAR data in the first parameter group; identify the second PDR data in the second parameter group using the interface name of the first interface according to the first forwarding rule; bind the identified second PDR data, the second FAR data in the second parameter group, and other parameters in the second parameter group to a newly created PFCP protocol message to obtain a target PFCP protocol message; wherein the second FAR data in the second parameter group includes the interface name identifier of the second interface.
  • the first interface is the S1-U interface and the second interface is the SGI interface; if the initial PFCP protocol message is downlink data, the first interface is the SGI interface and the second interface is the S1-U interface.
  • the reconstruction module is specifically used to: when the network element fusion mode of the session management function entity is to logically combine the function of the SGW and the function of the PGW, use the second forwarding rule as the reconstructed forwarding rule, and the second forwarding rule includes forwarding data from the first interface to the intermediate interface, and outputting data from the intermediate interface from the second interface.
  • the initial PFCP protocol message includes a third parameter group, which includes third PDR data and third FAR data; a reconstruction module is specifically used to: replace the original FAR identifier included in the third PDR data with the FAR identifier of the newly added FAR data to obtain modified third PDR data, and obtain a fourth parameter group based on the modified third PDR data and the newly added FAR data; wherein the modified third PDR data includes an interface name identifier of the first interface, and the newly added FAR data includes an interface name of the intermediate interface; replace the interface name of the first interface included in the third PDR data with the interface name of the intermediate interface to obtain the replaced third PDR data, and obtain a fifth parameter group based on the replaced third PDR data and the third FAR data; wherein the third FAR data includes the interface name of the second interface; and obtain the target PFCP protocol message based on the fourth parameter group and the fifth parameter group.
  • the first interface is the S1-U interface
  • the intermediate interface is the S5/S8 interface
  • the second interface is the SGI interface
  • the first interface is the SGI interface
  • the intermediate interface is the S5/S8 interface
  • the second interface is the S1-U interface
  • the first determination module is used to determine whether the initial PFCP protocol message is the target message type based on multiple target interface fields in the PFCP protocol message; the multiple target interface fields include at least a source interface field, a destination interface field and a 3GPP interface type field.
  • the target message type is a 4G session establishment message.
  • the device further comprises:
  • the sending module is used for directly sending the initial PFCP protocol message to the user plane function entity if the initial PFCP protocol message is not a message for establishing the 4G session.
  • the present application provides a communication system, which includes a session management function entity, a user plane function entity, and a communication device for executing the method described in any one of the first aspects above.
  • the present application provides a communication device, comprising: a receiver, a transmitter, a processor and a memory, wherein the memory stores a computer program;
  • the receiver is used to receive an initial PFCP protocol message sent by a session management function entity
  • the processor executes the computer program to identify the initial PFCP protocol message to determine whether the initial PFCP protocol message is a target message type; if the initial PFCP protocol message is the target message type, determine whether the network element fusion mode of the session management function entity matches the network element fusion mode of the user plane function entity, the network element fusion mode is used to indicate a mode of fusion of network element functions of SGW and PGW; and if there is no match, reconstruct the initial PFCP protocol message to obtain a target PFCP protocol message;
  • the transmitter is used to send the target PFCP protocol message to the user plane function entity.
  • the present application further provides a computer-readable storage medium, wherein a computer program is stored on the computer-readable storage medium, and when the computer program is executed by a processor, the message transmission method described in any one of the first aspects is implemented.
  • the present application further provides a chip, which includes a programmable logic circuit and/or program instructions, and implements any message transmission method described in the first aspect when the chip is running.
  • the present application further provides a computer program product, including a computer program, which implements any message transmission method described in the first aspect when executed by a processor.
  • the present application further provides a chip, comprising a processor, wherein the processor is configured to call and run a computer program from a memory to execute any message transmission method described in the first aspect above.
  • FIG1 is an application environment diagram of a message transmission method in one embodiment
  • FIG2 is a schematic diagram of a flow chart of a message transmission method in one embodiment
  • FIG3 is a schematic diagram of an architecture in an embodiment
  • FIG4 is a schematic diagram of an architecture in another embodiment
  • FIG5 is a schematic diagram of an architecture in another embodiment
  • FIG6 is a schematic diagram of an architecture in another embodiment
  • FIG7 is a schematic diagram of a process for determining a target PFCP protocol message in one embodiment
  • FIG8 is a schematic diagram of a process for determining a target PFCP protocol message in another embodiment
  • FIG9 is a schematic diagram of a reconstruction process in one embodiment
  • FIG10 is a schematic diagram of a process for determining a target PFCP protocol message in another embodiment
  • FIG11 is a schematic diagram of a reconstruction process in another embodiment
  • FIG12 is a schematic diagram of an application environment of a method for implementing 4G network and 5G network integration by using C-IWF for heterogeneous SMF and UPF collaborative networking in one embodiment;
  • FIG13 is a structural block diagram of a message transmission device in one embodiment
  • FIG14 is a diagram showing the internal structure of a communication device in one embodiment
  • FIG. 15 is a diagram showing the internal structure of a chip in one embodiment.
  • PFCP Packet Forwarding Control Protocol
  • SMF session management function entity
  • UPF user plane function entity
  • a customized signaling intercommunication gateway can be set between the user plane function entity and the session management entity, and the type of the initial PFCP protocol message sent by the SMF can be identified.
  • the initial PFCP protocol message is the target message type, it is determined whether the network element fusion mode of the session management function entity matches the network element fusion mode of the user plane function entity. If there is no match, the initial PFCP protocol message is reconstructed, and the reconstructed target PFCP protocol message is sent to the UPF, ensuring the normal transmission of PFCP protocol messages in heterogeneous scenarios of SMF and UPF, and realizing the integrated deployment of 4G networks and 5G networks between heterogeneous SMFs and UPFs.
  • the message transmission method provided in the embodiment of the present application can be applied in the application environment shown in Figure 1.
  • the communication device 101 is connected to the session management function entity 102 and the user plane function entity 103 for communication.
  • the communication device 101 can receive the initial PFCP protocol message sent by the session management function entity 102, and send the target PFCP protocol message obtained by the reconstruction process to the user plane function entity 103.
  • the communication device 101 can be a gateway device, for example, it can be a C-IWF (Customized-InterWorking Function).
  • the session management function entity can be an SMF (Session Management Function) in a 5G network, and the SMF can integrate the network element functions of PGW-C (Packet Data Network Gateway Control Plane) and/or SGW-C (Serving Gateway Control Plane) in a 4G network.
  • the user plane function entity can be an UPF (User Plane Function) in a 5G network, and the UPF integrates the network element functions of PGW-U (Packet Gateway User Plane) and/or SGW-U (Serving Gateway User Plane) in a 4G network.
  • a message transmission method is provided, which is described by taking the method applied to the communication device 101 in FIG. 1 as an example, and includes the following steps:
  • Step 201 Receive an initial PFCP protocol message sent by a session management function entity, and identify the initial PFCP protocol message to determine whether the initial PFCP protocol message is a target message type.
  • the initial PFCP protocol message may be a PFCP protocol message that the session management function entity needs to send to the user plane function entity.
  • the session management function entity and the user plane function entity are connected through the PFCP protocol interface, wherein the PFCP protocol interface is mainly responsible for establishing and managing characteristic session items.
  • the communication device is arranged between the session management function entity and the user plane function entity.
  • the communication device is connected with the session management function entity and the user plane function entity through the PFCP protocol interface to obtain the initial PFCP protocol message through the PFCP protocol interface, and then determine whether the initial PFCP protocol message needs to be reconstructed, so as to ensure the smooth transmission of the PFCP protocol message between the session management function entity and the user plane function entity.
  • the communication device After the communication device obtains the initial PFCP protocol message, it identifies whether the initial PFCP protocol message is a target message type, where the target message type refers to a PFCP protocol message related to the SGW network element and the PGW network element, or in other words, the target message type is a PFCP protocol message related to the 4G session service.
  • the target message type refers to a PFCP protocol message related to the SGW network element and the PGW network element, or in other words, the target message type is a PFCP protocol message related to the 4G session service.
  • Step 202 When the initial PFCP protocol message is of the target message type, it is determined whether the network element integration mode of the session management function entity matches the network element integration mode of the user plane function entity.
  • the sending and receiving identification of the initial PFCP protocol message are related to the SGW and PGW, which involves whether the network element fusion mode of the session management function entity matches the network element fusion mode of the user plane function entity. That is, if the network element fusion mode of the session management function entity does not match the network element fusion mode of the user plane function entity, the user plane function entity cannot normally identify the initial PFCP protocol message, and the communication equipment needs to reconstruct the initial PFCP protocol message; if the network element fusion mode of the session management function entity matches the network element fusion mode of the user plane function entity, the user plane function entity can normally identify the initial PFCP protocol message, and the communication equipment does not need to process the initial PFCP protocol message.
  • the network element fusion mode is used to indicate the mode of integrating the network element functions of SGW and PGW.
  • the SGW network element function is divided into SGW-C and SGW-U
  • the PGW network element function is divided into PGW-C and PGW-U.
  • the fusion architecture of 4G network and 5G network is divided into two types, namely standard definition architecture and enterprise standard architecture. Please refer to Figure 3.
  • SGW is an independent network element
  • the SGW-C of the control plane is not combined with SMF
  • the SGW-U of the user plane is not combined with UPF
  • the PGW-C of the control plane is combined with SMF
  • the PGW-U of the user plane is combined with UPF.
  • the SGW-C and PGW-C of the control plane are combined with SMF
  • the SGW-U and PGW-U of the user plane are combined with UPF.
  • the current architecture implementation scheme includes the integration mode of SGW and PGW logically combined and the integration mode of SGW and PGW logically separated.
  • Figure 5 shows a schematic diagram of the architecture of the logical combination of SGW and PGW in SMF and UPF provided by an embodiment of the present application.
  • Figure 6 shows a schematic diagram of the architecture of the logical separation of SGW and PGW in SMF and UPF provided by an embodiment of the present application.
  • UPF can receive the PFCP protocol message sent by SMF, and the heterogeneous SMF and UPF cannot be connected, that is, when one of SMF and UPF is a network element integration mode in which SGW and PGW are logically combined, and the other is a network element integration mode in which SGW and PGW are logically separated, the two cannot be connected, resulting in the difficulty of decoupling the PFCP protocol interface.
  • the initial PFCP protocol message is the target message type
  • the communication device may pre-configure the session management function entity and the user plane function entity as being logically heterogeneous or logically isomorphic, wherein if the two are logically heterogeneous, the network element fusion modes of the two are different; if the two are logically isomorphic, the network element fusion modes of the two are the same.
  • the communication device may determine the network element fusion mode of the session management function entity based on the received initial PFCP protocol message, and determine the network element fusion mode of the user plane function entity based on the historical PFCP protocol messages received from the user plane function entity, thereby combining the network element fusion mode of the session management function entity with the network element fusion mode of the user plane function entity.
  • the methods are different, it is determined that the two do not match.
  • the communication device can determine the network element fusion mode of the session management function entity by identifying the initial PFCP protocol message, and when it is clear that the session management function entity and the user plane function entity are logically heterogeneous by reading the pre-configured content, it determines that the two do not match and reconstructs the target initial PFCP protocol message.
  • Step 203 When the network element integration mode of the session management function entity does not match the network element integration mode of the user plane function entity, the initial PFCP protocol message is reconstructed to obtain the target PFCP protocol message, and the target PFCP protocol message is sent to the user plane function entity.
  • the internal forwarding rules of the initial PFCP protocol message sent by the session management function entity correspond to the network element integration mode of the session management function entity
  • the internal forwarding rules of the PFCP protocol message that the user plane function entity can receive correspond to the network element integration mode of the user plane function entity
  • the communication device reconstructs the initial PFCP protocol message to obtain the target PFCP protocol message, and the internal forwarding rule of the target PFCP protocol message corresponds to the network element fusion mode of the user plane function entity. Then, the target PFCP protocol message is directly sent to the user plane function entity, and accordingly, the user plane function entity can normally identify the target PFCP protocol message to achieve the decoupling of the PFCP protocol interface. It can also be understood that the transmission data included in the initial PFCP protocol message and the target PFCP protocol message are consistent.
  • the communication device receives the initial PFCP protocol message sent by the session management function entity, and identifies the initial PFCP protocol message to determine whether the initial PFCP protocol message is the target message type; when the initial PFCP protocol message is the target message type, it is determined whether the network element fusion mode of the session management function entity matches the network element fusion mode of the user plane function entity, and the network element fusion mode is used to indicate the mode of integrating the network element functions of the SGW and PGW; when the network element fusion mode of the session management function entity does not match the network element fusion mode of the user plane function entity, the initial PFCP protocol message is reconstructed to obtain the target PFCP protocol message, and the target PFCP protocol message is sent to the user plane function entity.
  • the target PFCP protocol message after the reconstruction is sent to the user plane functional entity and can be normally received by the user plane functional entity.
  • the PFCP protocol interface between the session management functional entity and the user plane functional entity can be normally decoupled to ensure that the session management functional entity and the user plane functional entity can be normally connected, so as to help realize the integrated deployment of 4G networks and 5G networks between heterogeneous SMFs and UPFs.
  • the following describes how to determine whether the initial PFCP protocol message is of the target message type.
  • the target message type is a 4G session establishment message.
  • SGW and PGW are both 4G network elements. Therefore, when the initial PFCP protocol message is a 4G session establishment message, the initial PFCP protocol message is related to the network element fusion mode of SGW and PGW, and then it is necessary to determine whether the initial PFCP protocol message needs to be reconstructed.
  • determining whether the initial PFCP protocol message is a target message type includes: determining whether the initial PFCP protocol message is a target message type according to multiple target interface fields in the PFCP protocol message, wherein the multiple target interface fields include at least a source interface field, a destination interface field, and a 3GPP interface type field.
  • the initial PFCP protocol message includes PDR (Packet Detection Rule) data and FAR (Forwarding Action Rules) data.
  • the PDR data includes the Source Interface field and the 3GPP Interface Type field, and the communication device can identify whether the Source Interface field and the 3GPP Interface Type field are related to the 4G session.
  • the FAR data includes the Destination Interface field and the 3GPP Interface Type field, and the communication device can identify whether the Destination Interface field and the 3GPP Interface Type field are related to the 4G session.
  • the initial PFCP protocol message is a target message type, that is, the initial PFCP protocol message is a 4G session establishment message.
  • the 3GPP interface is determined to be a 4G interface such as an S1-U interface or an SGI interface
  • the initial PFCP protocol message is determined to be a 4G session establishment message.
  • the method further includes: if the initial PFCP protocol message is not a 4G session establishment message, directly sending the initial PFCP protocol message to the user plane function entity.
  • the initial PFCP protocol message is not a 4G session establishment message, for example, the initial PFCP protocol message is a 5G session establishment message, it means that the initial PFCP protocol message is sent by the 5G network element SMF itself, which has nothing to do with the network element integration mode of the 4G network element.
  • the received 5G network element UPF can directly identify the initial PFCP protocol message, so the communication device can directly send the initial PFCP protocol message to the user plane function entity. For example, if the 3GPP interface is determined to be a 5G interface such as an N3 interface or an N6 interface, a 5G session establishment message is established.
  • the communication device can also directly transmit the initial PFCP protocol message to the user plane functional entity.
  • the communication device can quickly determine whether the initial PFCP protocol message is a 4G session establishment message based on the source interface field, the destination interface field, and the 3GPP interface type field in the PFCP protocol message, thereby ensuring the accuracy and efficiency of identification.
  • the communication device directly sends the initial PFCP protocol message to the user plane function entity, avoiding the useless reconstruction process, and forwarding the initial PFCP protocol message according to the message type of the initial PFCP protocol message, thereby ensuring the transmission efficiency again.
  • the following describes the process of reconstructing the initial PFCP protocol message to obtain the target PFCP protocol message.
  • FIG7 a schematic diagram of a process for determining a target PFCP protocol message provided by an embodiment of the present application is shown.
  • the initial PFCP protocol message is reconstructed to obtain the target PFCP protocol message, including:
  • Step 701 Determine a reconstruction forwarding rule according to a network element integration mode of a session management function entity and a network element integration mode of a user plane function entity.
  • the initial PFCP protocol message is reconstructed according to the data forwarding rules of the SGW and PGW when the logical integration is performed.
  • the initial PFCP protocol message is reconstructed according to the data forwarding rules of the SGW and PGW when the logical separation is performed.
  • a reconstruction forwarding rule is determined according to a network element integration mode of a session management functional entity and a network element integration mode of a user plane functional entity, including: when the network element integration mode of the session management functional entity is to logically separate the functions of the SGW and the PGW, a first forwarding rule is used as a reconstruction forwarding rule, and the first forwarding rule includes outputting data from the first interface from the second interface.
  • the forwarding rules of the data in the sent PFCP protocol message are: forwarding from the S1-U interface to the S5/S8 interface, and then forwarding from the S5/S8 interface to the SGI interface, or forwarding from the SGI interface to the S5/S8 interface, and then forwarding from the S5/S8 interface to the S1-U interface.
  • the forwarding rules for the data in the sent PFCP protocol message are: forwarding from the S1-U interface to the SGI interface, or forwarding from the SGI interface to the S1-U interface.
  • the first forwarding rule when the function logic of the SGW and the function logic of the PGW are combined should be used as the reconstructed forwarding rule.
  • the first interface is one of the S1-U interface and the SGI interface
  • the second interface is the other of the S1-U interface and the SGI interface.
  • the first interface is the S1-U interface and the second interface is the SGI interface; if the initial PFCP protocol message is downlink data, the first interface is the SGI interface and the second interface is the S1-U interface.
  • the forwarding rules in the target PFCP protocol message that the user plane functional entity can recognize are forwarding from the S1-U interface to the SGI interface, or from the SGI interface to the S1-U interface.
  • the initial PFCP protocol message is data sent by the base station to the UPF
  • the initial PFCP protocol message is uplink data
  • the first interface is the S1-U interface
  • the second interface is the SGI interface.
  • the initial PFCP protocol message is data sent by the UPF to the base station
  • the initial PFCP protocol message is downlink data, and correspondingly, at this time, the first interface is the SGI interface and the second interface is the S1-U interface.
  • the S1-U interface is the interconnection interface between the eNodeB (Evolved Node B) and the SGW, and is used for data message transmission.
  • the SGI interface is the interface between the PGW and the packet data network.
  • determining the reconstruction forwarding rule including: when the network element fusion mode of the session management function entity is to logically integrate the function of the SGW and the function of the PGW, using the second forwarding rule as the reconstruction forwarding rule, the second forwarding rule includes forwarding the data from the first interface to the user plane function entity.
  • the data from the intermediate interface is sent to the intermediate interface, and the data from the intermediate interface is output from the second interface.
  • the second forwarding rule when the function of the SGW and the function logic of the PGW are separated should be used as a reconstructed forwarding rule.
  • the first interface is one of the S1-U interface and the SGI interface
  • the second interface is the other of the S1-U interface and the SGI interface.
  • the first interface is the S1-U interface
  • the intermediate interface is the S5/S8 interface
  • the second interface is the SGI interface
  • the first interface is the SGI interface
  • the intermediate interface is the S5/S8 interface
  • the second interface is the S1-U interface
  • the forwarding rule in the target PFCP protocol message that the user plane function entity can identify is forwarding from the S1-U interface to the S5/S8 interface, and then forwarding from the S5/S8 interface to the SGI interface; or, the forwarding rule is forwarding from the SGI interface to the S5/S8 interface, and then forwarding from the S5/S8 interface to the S1-U interface.
  • the S5 interface is the interface used when the local SGW is connected to the local PGW
  • the S8 interface is the interface used when the local SGW is connected to the foreign PGW.
  • Step 702 reconstruct the initial PFCP protocol message according to the reconstruction forwarding rule to obtain the target PFCP protocol message.
  • the following first describes a process of reconstructing an initial PFCP protocol message by using the first forwarding rule as a reconstructed forwarding rule.
  • FIG8 another flow chart of determining a target PFCP protocol message provided by an embodiment of the present application is shown.
  • the initial PFCP protocol message is reconstructed according to the reconstruction forwarding rule to obtain the target PFCP protocol message, including:
  • Step 801 Delete the first PDR data and the first FAR data in the first parameter group.
  • Step 802 According to the first forwarding rule, the second PDR data in the second parameter group is identified by using the interface name of the first interface.
  • the initial PFCP protocol message includes a first parameter group and a second parameter group, the first parameter group corresponds to one of the SGW and the PGW, and the second parameter group corresponds to the other of the SGW and the PGW.
  • the first parameter group includes the first PDR data and the first FAR data.
  • the first PDR data includes a group of data such as FAR ID, QER ID, URR ID and the interface name of the first interface;
  • the first FAR data includes the interface name of the intermediate interface.
  • the second parameter group includes the second PDR data and the second FAR data.
  • the second PDR data also includes another set of FAR ID, QER ID, URR ID and the interface name of the intermediate interface;
  • the second FAR data includes the interface name of the second interface.
  • ID means identification or name;
  • QER is the abbreviation of QoS Enforcement Rules, which refers to QoS implementation rules, where QoS is Quality of Service, indicating service quality;
  • URR is the abbreviation of Usage Reporting Rules, which refers to usage reporting rules.
  • the first forwarding rule is used as a reconstructed forwarding rule, and only the relevant data forwarded from the first interface to the second interface needs to be retained in the first forwarding rule, it is necessary to delete some data in the first parameter group and the second parameter group, and reconstruct each data to obtain the target PFCP protocol message.
  • the first PDR data and the first FAR data in the first parameter group may be deleted, wherein, for example, the FAR ID, QER ID and URR ID in the first PDR data may be deleted, and the interface name of the intermediate interface in the first FAR data may be deleted.
  • the interface name of the remaining first interface in the first PDR data is used to replace the interface name of the intermediate interface included in the second PDR data, which is equivalent to using the interface name of the first interface to identify the second PDR data in the second parameter group.
  • the identified second PDR data includes data such as the interface name of the first interface, FAR ID, QER ID and URR ID.
  • the second FAR data since the second FAR data includes the interface name of the second interface, the second FAR data is identified by the interface name of the second interface.
  • Step 803 Bind the identified second PDR data, the second FAR data in the second parameter group, and other parameters in the second parameter group to a newly created PFCP protocol message to obtain a target PFCP protocol message, wherein the second FAR data in the second parameter group includes the interface name identifier of the second interface.
  • the communication device can generate a new PFCP protocol message, and bind the identified second PDR data and the identified second FAR data to the new PFCP protocol message, and also synchronously bind other parameters in the second parameter group to the new PFCP protocol message to obtain a target PFCP protocol message. It can be understood that due to the deletion process, the obtained target PFCP protocol message only includes one set of PDR data and FAR data, and the interface names of the first interface and the second interface are used for identification respectively, so the target PFCP protocol message can be identified by the user plane functional entity.
  • the first parameter group corresponds to the SGW-U
  • the first PDR data includes the interface name of the S1-U interface, which is used to characterize the source interface of the data
  • the first PDR data also includes FAR ID1, QER ID1 and URR ID1.
  • the first FAR data bound to the first PDR data can be determined according to FAR ID1, and the first FAR data includes the interface name of the S5/S8 interface, which is used to characterize the destination interface of the data.
  • the second parameter group corresponds to PGW-U, and the second PDR data includes the interface name of the S5/S8 interface, which is used to characterize the source interface of the data; the second PDR data also includes FAR ID2, QER ID2 and URR ID2.
  • the second FAR data bound to the second PDR data can be determined according to FAR ID2, and the second FAR data includes the interface name of the SGI interface, which is used to characterize the destination interface of the data.
  • the first PDR data and the first FAR data are deleted, that is, the content in the dotted box in Figure 9 is deleted, and the interface name of the S1-U interface is added to the second PDR data, so as to obtain the target PFCP protocol message corresponding to the reconstructed forwarding rule.
  • the first parameter group corresponds to the PGW-U
  • the first PDR data includes the interface name of the SGI interface, which is used to characterize the source interface of the data;
  • the first PDR data also includes FAR ID3, QER ID3 and URR ID3.
  • the first FAR data bound to the first PDR data can be determined according to FAR ID3, and the first FAR data includes the interface name of the S5/S8 interface, which is used to characterize the destination interface of the data.
  • the second parameter group corresponds to SGW-U
  • the second PDR data includes the interface name of the S5/S8 interface, which is used to characterize the source interface of the data; the second PDR data also includes FAR ID4, QER ID4 and URR ID4.
  • the second FAR data bound to the second PDR data can be determined according to FAR ID4, and the second FAR data includes the interface name of the S1-U interface, which is used to characterize the destination interface of the data.
  • the first PDR data and the first FAR data are deleted, that is, the content in the dotted box of Figure 9 is deleted, and the second PDR data is identified by the interface name of the SGI interface, so as to obtain the target PFCP protocol message corresponding to the reconstructed forwarding rule.
  • FIG10 another flow chart of determining a target PFCP protocol message provided by an embodiment of the present application is shown.
  • the initial PFCP protocol message is reconstructed according to the reconstruction forwarding rule to obtain the target PFCP protocol message, including:
  • Step 1001 replace the original FAR identifier included in the third PDR data with the FAR identifier of the newly added FAR data to obtain the modified third PDR data, and obtain the fourth parameter group according to the modified third PDR data and the newly added FAR data.
  • the modified third PDR data includes the interface name identifier of the first interface
  • the newly added FAR data includes the interface name of the intermediate interface.
  • the initial PFCP protocol message includes a third parameter group, and the third parameter group includes third PDR data and third FAR data.
  • Step 1002 Replace the interface name of the first interface included in the third PDR data with the interface name of the intermediate interface to obtain the replaced third PDR data, and obtain a fifth parameter group according to the replaced third PDR data and the third FAR data, wherein the third FAR data includes the interface name of the second interface.
  • Step 1003 Obtain a target PFCP protocol message according to the fourth parameter group and the fifth parameter group.
  • the third parameter group includes third PDR data and third FAR data.
  • the third PDR data includes the interface name of the S1-U interface, which is used to characterize the source interface of the data; the third PDR data also includes FAR ID0, QER ID0 and URR ID0.
  • the third FAR data bound to the third PDR data can be determined according to FAR ID0, and the third FAR data includes the interface name of the SGI interface.
  • the third PDR data is bound to the newly added FAR data.
  • the FAR identifier FAR ID0' of the newly added FAR data is used to replace the original FAR identifier FAR ID0.
  • the modified third PDR data includes the interface name identifier of the first interface, that is, the third PDR data is identified by the interface name of the first interface; and the newly added FAR data is identified by the interface name of the intermediate interface, and the fourth parameter group is obtained according to the modified third PDR data and the newly added FAR data.
  • the modified third PDR data included in the fourth parameter group includes the interface name, FAR ID0', QER ID0 and URR ID0 of the S1-U interface; the identified third FAR data included in the fourth parameter group includes the interface name of the S5/S8 interface, which is used to characterize the destination interface of the data.
  • the fifth parameter group includes the replaced third PDR data, which is obtained by replacing the interface name of the first interface included in the third PDR data with the interface name of the intermediate interface, that is, the replaced third PDR data included in the fifth parameter group includes the interface name of the S5/S8 interface, FAR ID0, QER ID0 and URR ID0.
  • the fifth parameter group also includes the third FAR data identified by the interface name of the second interface bound to the replaced third PDR data, that is, the third FAR data included in the fifth parameter group includes the interface name of the SGI interface. It can be understood that the fourth parameter group corresponds to SGW-U, and the fifth parameter group corresponds to PGW-U.
  • the fourth parameter group and the fifth parameter group obtained and other data and parameters in the initial PFCP protocol message are migrated to the newly created PFCP protocol message to obtain the target PFCP protocol message.
  • the target PFCP protocol message can comply with the logically separated forwarding rules and can be recognized by the logically separated UPF to achieve PFCP protocol interface decoupling.
  • the third parameter group when the initial PFCP protocol message sent by the SMF to the UPF is downlink data, the third parameter group includes third PDR data and third FAR data.
  • the third PDR data includes the interface name of the SGI interface, which is used to characterize the source interface of the data; the third PDR data also includes FAR ID1, QER ID1, and URR ID1.
  • the third FAR data bound to the third PDR data can be determined according to FAR ID1, and the third FAR data includes the interface name of the S1-U interface.
  • the third PDR data is bound to the newly added FAR data.
  • the FAR identifier FAR ID1' of the newly added FAR data is used to replace the original FAR ID1.
  • the third PDR data is identified by the interface name of the first interface
  • the newly added FAR data is identified by the interface name of the intermediate interface to obtain the fourth parameter group. That is, the modified third PDR data included in the fourth parameter group includes the interface name of the SGI interface, FAR ID1', QER ID1 and URR ID1; the third FAR data included in the fourth parameter group includes the interface name of the S5/S8 interface, which is used to characterize the destination interface of the data.
  • a fifth parameter group is also generated.
  • the replaced third PDR data included in the fifth parameter group includes the interface name of the S5/S8 interface, FAR ID1, QER ID1 and URR ID1.
  • the fifth parameter group also includes the third FAR data identified by the interface name of the second interface bound to the replaced third PDR data, that is, the third FAR data included in the fifth parameter group includes the interface name of the S1-U interface. It can be understood that the fourth parameter group corresponds to PGW-C, and the fifth parameter group corresponds to SGW-C.
  • the fourth parameter group and the fifth parameter group obtained and other data and parameters in the initial PFCP protocol message are migrated to the newly created PFCP protocol message to obtain the target PFCP protocol message.
  • the target PFCP protocol message can comply with the logically separated forwarding rules and can be recognized by the logically separated UPF to achieve PFCP protocol interface decoupling.
  • the initial PFCP protocol message is reconstructed according to the reconstruction forwarding rule to obtain the target PFCP protocol message, thereby sending the target PFCP protocol message to the user plane function entity, thereby realizing the integrated deployment of the 4G network and the 5G network between the heterogeneous SMF and UPF.
  • the communication equipment C-IWF By adding the functions of the communication equipment C-IWF to identify, analyze, and reconstruct the PFCP protocol message, the problem that the heterogeneous SMF and UPF cannot be adapted is solved.
  • corresponding PFCP protocol message reconstruction schemes are proposed for the two heterogeneous situations. Based on this, the communication equipment reconstructs the PFCP protocol interface message.
  • the PFCP protocol interface decoupling can be achieved without complex transformation of the existing network, which improves the flexibility of customized network deployment and the diversity of equipment selection, thereby promoting the development of the overall ecology of the 5G ToB industry.
  • the method proposed in the embodiment of the present application is specifically described below with a specific communication scenario.
  • the embodiment of the present application provides a method for realizing the integration of 4G network and 5G network by using C-IWF to perform heterogeneous SMF and UPF collaborative networking.
  • the method can be applied to the application environment shown in Figure 12. It should be noted that Figure 12 is only an exemplary application environment schematic diagram, which also shows other network elements connected to SMF and UPF.
  • the method includes the following contents:
  • C-IWF When forwarding the initial PFCP protocol message, C-IWF identifies the initial PFCP protocol message, including: judging whether the initial PFCP protocol message sent by SMF is a 4G session establishment message based on the Source Interface, Network Instance, 3GPP Interface Type in PDR and the Destination Interface, 3GPP Interface Type in FAR. Also, identifying whether the initial PFCP protocol message sent by SMF corresponds to the logical combination or separation of SGW and PGW, that is, determining whether SMF and UPF are homogeneous or heterogeneous.
  • C-IWF directly transparently transmits the initial PFCP protocol message to UPF.
  • the initial PFCP protocol message sent by SMF is a message for establishing a 4G session and SMF and UPF are isomorphic
  • C-IWF directly transparently transmits the initial PFCP protocol message to UPF.
  • the initial PFCP protocol message sent by SMF is a message for establishing a 4G session and SMF and UPF are heterogeneous
  • C-IWF reconstructs the initial PFCP protocol message.
  • the reconstruction process is as follows:
  • the message sent by the logically separate SMF to the logically combined UPF contains the forwarding rules: S1-U—S5/S8, S5/S8—SGI.
  • the C-IWF When docking with the logically combined UPF, the C-IWF combines the rules in the message into S1-U—SGI, deletes the redundant FAR and PDR in the message, and rebinds the original QER and URR binding relationship of S5/S8—SGI (in the uplink data) or S5/S8—S1-U (in the downlink data) to the PDR data corresponding to the S1-U—SGI rule.
  • the message sent by the logically combined SMF to the logically separated UPF contains the forwarding rule S1-U—SGI.
  • the C-IWF disassembles the S1-U—SGI in the message into S1-U—S5/S8 and S5/S8—SGI.
  • the PFCP protocol message is forwarded between the heterogeneous SMF and UPF through the C-IWF, and during the forwarding process, the PFCP protocol message sent by the SMF is identified, the data flow and information are determined according to the PDR data and the FAR data, and the PFCP protocol message is reconstructed according to the judgment result and the implementation logic of the UPF receiver, so that the UPF can correctly identify and receive the reconstructed PFCP protocol message, thereby ensuring the decoupling of the PFCP protocol interface, and realizing the integration of 4G networks and 5G networks under heterogeneous SMFs and UPFs without complex modifications to the existing network.
  • steps in the flowcharts involved in the above-mentioned embodiments can include multiple steps or multiple stages, and these steps or stages are not necessarily executed at the same time, but can be executed at different times, and the execution order of these steps or stages is not necessarily to be carried out in sequence, but can be executed in turn or alternately with other steps or at least a part of the steps or stages in other steps.
  • the embodiment of the present application also provides a message transmission device for implementing the message transmission method involved above.
  • the implementation scheme for solving the problem provided by the device is similar to the implementation scheme recorded in the above method, so the specific limitations in one or more message transmission device embodiments provided below can refer to the limitations on the message transmission method above, and will not be repeated here.
  • a message transmission device includes: a first determination module 1301, a second determination module 1302, and a reconstruction module 1303, wherein:
  • the first determination module 1301 is used to receive an initial PFCP protocol message sent by a session management function entity, and identify the initial PFCP protocol message to determine whether the initial PFCP protocol message is a target message type;
  • the second determination module 1302 is used to determine whether the network element fusion mode of the session management function entity and the network element fusion mode of the user plane function entity match each other when the initial PFCP protocol message is of the target message type, and the network element fusion mode is used to indicate a mode of fusion of network element functions of SGW and PGW;
  • the reconstruction module 1303 is used to reconstruct the initial PFCP protocol message to obtain the target PFCP protocol message and send the target PFCP protocol message to the user plane functional entity when the network element integration mode of the session management functional entity does not match the network element integration mode of the user plane functional entity.
  • the reconstruction module 1303 is specifically used to: determine the reconstruction forwarding rule according to the network element fusion mode of the session management function entity and the network element fusion mode of the user plane function entity; reconstruct the initial PFCP protocol message according to the reconstruction forwarding rule to obtain the target PFCP protocol message.
  • the reconstruction module 1303 is specifically used to: when the network element fusion mode of the session management function entity is to logically separate the function of the SGW and the function of the PGW, use the first forwarding rule as the reconstructed forwarding rule, and the first forwarding rule includes outputting data from the first interface from the second interface.
  • the first interface is the S1-U interface and the second interface is the SGI Interface; if the initial PFCP protocol message is downlink data, the first interface is the SGI interface and the second interface is the S1-U interface.
  • the reconstruction module 1303 is specifically used to: when the network element fusion mode of the session management function entity is to logically combine the function of the SGW and the function of the PGW, use the second forwarding rule as the reconstructed forwarding rule, and the second forwarding rule includes forwarding data from the first interface to the intermediate interface, and outputting data from the intermediate interface from the second interface.
  • the initial PFCP protocol message includes a third parameter group, which includes third PDR data and third FAR data; the reconstruction module 1303 is specifically used to: replace the original FAR identifier included in the third PDR data with the FAR identifier of the newly added FAR data to obtain the modified third PDR data, and obtain the fourth parameter group based on the modified third PDR data and the newly added FAR data; wherein the modified third PDR data includes the interface name identifier of the first interface, and the newly added FAR data includes the interface name of the intermediate interface; replace the interface name of the first interface included in the third PDR data with the interface name of the intermediate interface to obtain the replaced third PDR data, and obtain the fifth parameter group based on the replaced third PDR data and the third FAR data; wherein the third FAR data includes the interface name of the second interface; and obtain the target PFCP protocol message based on the fourth parameter group and the fifth parameter group.
  • the first interface is the S1-U interface
  • the intermediate interface is the S5/S8 interface
  • the second interface is the SGI interface
  • the first interface is the SGI interface
  • the intermediate interface is the S5/S8 interface
  • the second interface is the S1-U interface
  • the target message type is a 4G session establishment message.
  • the apparatus further comprises:
  • Each module in the above message transmission device can be implemented in whole or in part by software, hardware, or a combination thereof.
  • Each module can be embedded in or independent of a processor in a computer device in the form of hardware, or can be stored in a memory in a computer device in the form of software, so that the processor can call and execute operations corresponding to each module.
  • the present application provides a communication system, which includes a session management function entity, a user plane function entity, and a communication device that executes the message transmission method in the above embodiment.
  • FIG14 is a schematic diagram of the structure of a communication device provided in an embodiment of the present application.
  • the communication device 1400 shown in FIG14 includes: at least one processor 1401, a memory 1402, and at least one network interface 1404.
  • the various components in the communication device 1400 are coupled together through a bus system 1405. It can be understood that the bus system 1405 is used to realize the connection and communication between these components.
  • the bus system 1405 also includes a power bus, a control bus, and a status signal bus. However, for the sake of clarity, various buses are labeled as bus systems 1405 in FIG14.
  • a transceiver 1406 is also included, and the transceiver can be a plurality of elements, that is, a transmitter and a receiver, providing a unit for communicating with various other devices on a transmission medium.
  • RAM static RAM
  • DRAM dynamic RAM
  • SDRAM synchronous DRAM
  • DDR SDRAM double data rate synchronous DRAM
  • ESDRAM enhanced SDRAM
  • SLDRAM synchronous link DRAM
  • DRRAM direct RAM bus DRAM
  • the memory 1402 stores the following elements, executable modules or data structures, or their subsets, or their extended sets: operating system 1421.
  • the operating system 1421 includes various system programs, such as a framework layer, a core library layer, a driver layer, etc., which are used to implement various basic services and process hardware-based tasks.
  • a receiver is used to receive an initial PFCP protocol message sent by a session management function entity; a processor is used to identify the initial PFCP protocol message to determine whether the initial PFCP protocol message is a target message type; when the initial PFCP protocol message is of the target message type, it is determined whether the network element fusion mode of the session management function entity matches the network element fusion mode of the user plane function entity, and the network element fusion mode is used to indicate a mode of integrating the network element functions of the SGW and the PGW; when the network element fusion mode of the session management function entity does not match the network element fusion mode of the user plane function entity, the initial PFCP protocol message is reconstructed to obtain a target PFCP protocol message; a transmitter is used to send the target PFCP protocol message to the user plane function entity.
  • the processor 1401 may be an integrated circuit chip with signal processing capabilities. In the implementation process, each step of the above method may be completed by an integrated logic circuit of hardware in the processor 1401 or by instructions in the form of software.
  • the above processor 1401 may be a general-purpose processor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field programmable gate array (FPGA) or other programmable logic devices, discrete gates or transistor logic devices, discrete hardware components.
  • DSP digital signal processor
  • ASIC application-specific integrated circuit
  • FPGA field programmable gate array
  • the methods, steps and logic block diagrams disclosed in the embodiments of the present invention may be implemented or executed.
  • the general-purpose processor may be a microprocessor or the processor may also be any conventional processor, etc.
  • the steps of the method disclosed in conjunction with the embodiments of the present invention may be directly embodied as being executed by a hardware decoding processor, or may be executed by a combination of hardware and software modules in a decoding processor.
  • the software module may be located in a storage medium mature in the art, such as a random access memory, a flash memory, a read-only memory, a programmable read-only memory, or an electrically erasable programmable memory, a register, etc.
  • the storage medium is located in the memory 1402, and the processor 1401 reads the information in the memory 1402 and completes the steps of the above method in combination with its hardware.
  • the embodiments described in the embodiments of the present invention may be implemented by hardware, software, firmware, middleware, microcode or a combination thereof.
  • the processing unit may be implemented in one or more application specific integrated circuits (ASICs), digital signal processors (DSPs), digital signal processing devices (DSP devices, DSPDs), programmable logic devices (PLDs), field programmable gate arrays (FPGAs), general purpose processors, controllers, microcontrollers, microprocessors, other electronic units for performing the functions described in the present application or a combination thereof.
  • ASICs application specific integrated circuits
  • DSPs digital signal processors
  • DSP devices digital signal processing devices
  • DSPDs programmable logic devices
  • FPGAs field programmable gate arrays
  • general purpose processors controllers, microcontrollers, microprocessors, other electronic units for performing the functions described in the present application or a combination thereof.
  • the technology described in the embodiments of the present invention can be implemented by a module (such as a process, function, etc.) that performs the functions described in the embodiments of the present invention.
  • the software code can be stored in a memory and executed by the processor 1401.
  • the memory can be implemented in the processor 1401 or outside the processor 1401.
  • the processor executes a computer program, which is specifically used to determine a reconstruction forwarding rule according to a network element fusion mode of the session management function entity and a network element fusion mode of the user plane function entity; and reconstruct the initial PFCP protocol message according to the reconstruction forwarding rule to obtain a target PFCP protocol message.
  • the processor executes a computer program, specifically for using the first forwarding rule as the reconstructed forwarding rule when the network element fusion mode of the session management function entity is to logically separate the function of the SGW and the function of the PGW.
  • the first forwarding rule includes outputting data from the first interface from the second interface.
  • the processor executes a computer program, which is specifically used to use the second forwarding rule as the reconstructed forwarding rule when the network element fusion mode of the session management function entity is to logically combine the function of the SGW and the function of the PGW.
  • the second forwarding rule includes forwarding data from the first interface to the intermediate interface, and outputting data from the intermediate interface from the second interface.
  • the processor executes a computer program, specifically configured to replace an original FAR identifier included in the third PDR data with a FAR identifier of the newly added FAR data to obtain modified third PDR data, and obtain a fourth parameter group according to the modified third PDR data and the newly added FAR data; wherein the modified third PDR data includes an interface name identifier of the first interface, and the newly added FAR data includes an interface name of the intermediate interface; and the interface name of the intermediate interface is used to replace the interface name of the first interface included in the third PDR data.
  • the replaced third PDR data is obtained, and a fifth parameter group is obtained according to the replaced third PDR data and the third FAR data; wherein the third FAR data includes the interface name of the second interface; and a target PFCP protocol message is obtained according to the fourth parameter group and the fifth parameter group.
  • the processor executes a computer program specifically for determining whether the initial PFCP protocol message is the target message type based on multiple target interface fields in the PFCP protocol message; the multiple target interface fields include at least a source interface field, a destination interface field, and a 3GPP interface type field.
  • the transmitter is used for directly sending the initial PFCP protocol message to the user plane function entity if the initial PFCP protocol message is not a message for establishing the 4G session.
  • FIG. 14 is merely a block diagram of a partial structure related to the scheme of the present application, and does not constitute a limitation on the communication device to which the scheme of the present application is applied.
  • the specific communication device may include more or fewer components than shown in the figure, or combine certain components, or have a different arrangement of components.
  • a chip is provided, and Fig. 15 is a schematic structural diagram of the chip in the embodiment of the present application.
  • the chip 1500 shown in Fig. 15 includes a processor 1510, and the processor 1510 can call and run a computer program from a memory to implement the method in the embodiment of the present application.
  • the chip 1500 may further include a memory 1520.
  • the processor 1510 may call and run a computer program from the memory 1520 to implement the method in the embodiment of the present application.
  • the memory 1520 may be a separate device independent of the processor 1510, or may be integrated in the processor 1510.
  • the chip 1500 may further include an input interface 1530.
  • the processor 1510 may control the input interface 1530 to communicate with other devices or chips, and specifically, may obtain information or data sent by other devices or chips.
  • the chip 1500 may further include an output interface 1540.
  • the processor 1510 may control the output interface 1540 to communicate with other devices or chips, and specifically, may output information or data to other devices or chips.
  • the chip 1500 can be applied to the communication device in the embodiments of the present application, and the chip 1500 can implement the corresponding processes implemented by the communication device in each method of the embodiments of the present application, which will not be described here for the sake of brevity.
  • the chip 1500 mentioned in the embodiment of the present application can also be called a system-level chip, a system chip, a chip system or a system-on-chip chip, etc.
  • the processor of the embodiment of the present application may be an integrated circuit chip with signal processing capabilities.
  • each step of the above method embodiment can be completed by an integrated logic circuit of hardware in the processor or an instruction in the form of software.
  • the above processor can be a general-purpose processor, a digital signal processor (Digital Signal Processor, DSP), an application-specific integrated circuit (Application Specific Integrated Circuit, ASIC), a field programmable gate array (Field Programmable Gate Array, FPGA) or other programmable logic devices, discrete gates or transistor logic devices, discrete hardware components.
  • the methods, steps and logic block diagrams disclosed in the embodiments of the present application can be implemented or executed.
  • the general-purpose processor can be a microprocessor or the processor can also be any conventional processor, etc.
  • the steps of the method disclosed in the embodiment of the present application can be directly embodied as a hardware decoding processor to be executed, or a combination of hardware and software modules in the decoding processor can be executed.
  • the software module can be located in a storage medium mature in the art such as a random access memory, a flash memory, a read-only memory, a programmable read-only memory, or an electrically erasable programmable memory, a register, etc.
  • the storage medium is located in the memory, and the processor reads the information in the memory and completes the steps of the above method in combination with its hardware.
  • the present application further provides a computer-readable storage medium, on which a computer program is stored, and when the computer program is executed by a processor, the steps in the above method embodiment are implemented.
  • the present application further provides a computer program product, which includes a computer program, and when the computer program is executed by a processor, the steps in the above method embodiment are implemented.
  • the communication device receives the initial PFCP protocol message sent by the session management function entity, and identifies the initial PFCP protocol message to determine whether the initial PFCP protocol message is of the target message type; when the initial PFCP protocol message is of the target message type, it is determined whether the network element fusion mode of the session management function entity matches the network element fusion mode of the user plane function entity, and the network element fusion mode is used to indicate the mode of integrating the network element functions of the SGW and PGW; when there is no match, the initial PFCP protocol message is reconstructed to obtain the target PFCP protocol message, and the target PFCP protocol message is sent to the user plane function entity.
  • the reconstructed target PFCP protocol message is sent to the user plane function entity and can be normally received by the user plane function entity, and the PFCP protocol interface between the session management function entity and the user plane function entity can be normally decoupled, ensuring that the session management function entity and the user plane function entity can Normal docking helps to achieve the integrated deployment of 4G networks and 5G networks between heterogeneous SMFs and UPFs.
  • any reference to the memory, database or other medium used in the embodiments provided in the present application can include at least one of non-volatile and volatile memory.
  • Non-volatile memory can include read-only memory (ROM), magnetic tape, floppy disk, flash memory, optical memory, high-density embedded non-volatile memory, resistive random access memory (ReRAM), magnetoresistive random access memory (MRAM), ferroelectric random access memory (FRAM), phase change memory (PCM), graphene memory, etc.
  • Volatile memory can include random access memory (RAM) or external cache memory, etc.
  • RAM can be in various forms, such as static random access memory (SRAM) or dynamic random access memory (DRAM).
  • SRAM static random access memory
  • DRAM dynamic random access memory
  • the database involved in each embodiment provided in this application may include at least one of a relational database and a non-relational database.
  • Non-relational databases may include distributed databases based on blockchains, etc., but are not limited to this.
  • the processor involved in each embodiment provided in this application may be a general-purpose processor, a central processing unit, a graphics processor, a digital signal processor, a programmable logic unit, a data processing logic unit based on quantum computing, etc., but are not limited to this.

Landscapes

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

Abstract

本申请涉及一种消息传输方法、装置、系统、设备和存储介质。所述方法包括：接收会话管理功能实体发送的初始PFCP协议消息，并对初始PFCP协议消息进行识别，以确定初始PFCP协议消息是否为目标消息类型；在初始PFCP协议消息为目标消息类型的情况下，确定会话管理功能实体的网元融合方式与用户面功能实体的网元融合方式是否相互匹配，网元融合方式用于指示融合SGW和PGW的网元功能的方式；在不匹配的情况下，对初始PFCP协议消息进行重构，得到目标PFCP协议消息，并将目标PFCP协议消息发送至用户面功能实体。

Description

消息传输方法、装置、系统、设备和存储介质
相关申请
本申请要求2023年6月20日申请的，申请号为2023107357362，名称为“消息传输方法、装置、系统、设备和存储介质”的中国专利申请的优先权，在此将其全文引入作为参考。
技术领域
本申请涉及无线通信技术领域，特别是涉及一种消息传输方法、装置、系统、设备和存储介质。
背景技术
在4G网络和5G网络融合的场景中，4G网络中的服务网关(Serving Gateway，SGW)实体和分组数据网络网关(Packet Data Network Gateway，PGW)实体分别与5G网络中的会话管理功能实体(SMF，Session Management Function)以及用户面功能实体(UPF，User Plane Function)进行了融合，该融合逻辑包括两种，分别为SGW与PGW逻辑分设和SGW与PGW逻辑合设。
发明内容
第一方面，本申请提供了一种消息传输方法，该方法包括：
接收会话管理功能实体发送的初始PFCP协议消息，并对初始PFCP协议消息进行识别，以确定初始PFCP协议消息是否为目标消息类型；在初始PFCP协议消息为目标消息类型的情况下，确定会话管理功能实体的网元融合方式与用户面功能实体的网元融合方式是否相互匹配，网元融合方式用于指示融合SGW和PGW的网元功能的方式；在不匹配的情况下，对初始PFCP协议消息进行重构，得到目标PFCP协议消息，并将目标PFCP协议消息发送至用户面功能实体。
在其中一个实施例中，对该初始PFCP协议消息进行重构，得到目标PFCP协议消息，包括：根据该会话管理功能实体的网元融合方式和该用户面功能实体的网元融合方式，确定重构转发规则；根据该重构转发规则对该初始PFCP协议消息进行重构，得到目标PFCP协议消息。
在其中一个实施例中，根据该会话管理功能实体的网元融合方式和该用户面功能实体的网元融合方式，确定重构转发规则，包括：在该会话管理功能实体的网元融合方式为将该SGW的功能和该PGW的功能逻辑分设的情况下，将第一转发规则作为该重构转发规则，该第一转发规则包括将来源于第一接口的数据从第二接口输出。
在其中一个实施例中，该初始PFCP协议消息包括第一参数组和第二参数组，该第一参数组与该SGW和该PGW中的一个对应，该第二参数组与该SGW和该PGW中的另一个对应；根据该重构转发规则对该初始PFCP协议消息进行重构，得到目标PFCP协议消息，包括：对第一参数组中的第一PDR数据和第一FAR数据进行删除处理；根据第一转发规则，利用第一接口的接口名称标识第二参数组中的第二PDR数据；将标识后的第二PDR数据、第二参数组中的第二FAR数据以及第二参数组中的其他参数绑定至新建PFCP协议消息中，得到目标PFCP协议消息；其中，第二参数组中的第二FAR数据包括第二接口的接口名称标识。
在其中一个实施例中，若所述初始PFCP协议消息为上行数据，则所述第一接口为S1-U接口，所述第二接口为SGI接口；若所述初始PFCP协议消息为下行数据，则所述第一接口为SGI接口，所述第二接口为S1-U接口。
在其中一个实施例中，根据该会话管理功能实体的网元融合方式和该用户面功能实体的网元融合方式，确定重构转发规则，包括：在该会话管理功能实体的网元融合方式为将该SGW的功能和该PGW的功能逻辑合设的情况下，将第二转发规则作为该重构转发规则，该第二转发规则包括将来源于第一接口的数据转发至中间接口，并将来源于该中间接口的数据从第二接口输出。
在其中一个实施例中，该初始PFCP协议消息包括第三参数组，该第三参数组包括第三PDR数据和第三FAR数据；根据该重构转发规则对该初始PFCP协议消息进行重构，得到目标PFCP协议消息，包括：采用新增FAR数据的FAR标识替换第三PDR数据中包括的原始FAR标识，得到修改后的第三 PDR数据，并根据修改后的第三PDR数据和新增FAR数据得到第四参数组；其中，修改后的第三PDR数据包括第一接口的接口名称标识，新增FAR数据包括中间接口的接口名称；采用中间接口的接口名称替换第三PDR数据中包括的第一接口的接口名称，得到替换后的第三PDR数据，并根据替换后的第三PDR数据和第三FAR数据得到第五参数组；其中，第三FAR数据包括第二接口的接口名称；根据第四参数组和第五参数组得到目标PFCP协议消息。
在其中一个实施例中，若所述初始PFCP协议消息为上行数据，则所述第一接口为S1-U接口，所述中间接口为S5/S8接口，所述第二接口为SGI接口；若所述初始PFCP协议消息为下行数据，则所述第一接口为SGI接口，所述中间接口为S5/S8接口，所述第二接口为S1-U接口。
在其中一个实施例中，确定该初始PFCP协议消息是否为目标消息类型，包括：根据该PFCP协议消息中的多个目标接口字段确定该初始PFCP协议消息是否为该目标消息类型；该多个目标接口字段至少包括源接口字段、目的接口字段以及3GPP接口类型字段。
在其中一个实施例中，该目标消息类型为4G会话建立消息。
在其中一个实施例中，该方法还包括：若该初始PFCP协议消息不为该4G会话建立消息，则直接将该初始PFCP协议消息发送至该用户面功能实体。
在其中一个实施例中，对所述第一参数组中的第一FDR数据和第一FAR数据进行删除处理，包括删除所述第一PDR数据中的FAR ID、QER ID和URR ID，及删除第一FAR数据中的中间接口的接口名称。
在其中一个实施例中，确定所述会话管理功能实体的网元融合方式与用户面功能实体的网元融合方式是否相匹配，包括：
基于预先配置确定所述会话管理功能实体和用户面功能实体为逻辑异构还是逻辑同构，并在确定所述会话管理功能实体和所述用户面功能实体为逻辑异构的情况下，确定所述会话管理功能实体的网元融合方式与所述用户面功能实体的网元融合方式不匹配；或者
根据接收到的初始PFCP协议消息确定会话管理功能实体的网元融合方式，根据历史接收到的用户面功能实体发送的历史PFCP协议消息确定用户面功能实体的网元融合方式，并在所述会话管理功能实体的网元融合方式与所述用户面功能实体的网元融合方式不相同时，确定所述会话管理功能实体的网元融合方式与所述用户面功能实体的网元融合方式不匹配。
第二方面，本申请提供了一种消息传输装置，该装置包括：
第一确定模块，用于接收会话管理功能实体发送的初始PFCP协议消息，并对初始PFCP协议消息进行识别，以确定初始PFCP协议消息是否为目标消息类型；
第二确定模块，用于在初始PFCP协议消息为目标消息类型的情况下，确定会话管理功能实体的网元融合方式与用户面功能实体的网元融合方式是否相互匹配，网元融合方式用于指示融合SGW和PGW的网元功能的方式；
重构模块，用于在不匹配的情况下，对初始PFCP协议消息进行重构，得到目标PFCP协议消息，并将目标PFCP协议消息发送至用户面功能实体。
在其中一个实施例中，重构模块，具体用于：根据该会话管理功能实体的网元融合方式和该用户面功能实体的网元融合方式，确定重构转发规则；根据该重构转发规则对该初始PFCP协议消息进行重构，得到目标PFCP协议消息。
在其中一个实施例中，重构模块，具体用于：在该会话管理功能实体的网元融合方式为将该SGW的功能和该PGW的功能逻辑分设的情况下，将第一转发规则作为该重构转发规则，该第一转发规则包括将来源于第一接口的数据从第二接口输出。
在其中一个实施例中，该初始PFCP协议消息包括第一参数组和第二参数组，该第一参数组与该SGW和该PGW中的一个对应，该第二参数组与该SGW和该PGW中的另一个对应；重构模块，具体用于：对第一参数组中的第一PDR数据和第一FAR数据进行删除处理；根据第一转发规则，利用第一接口的接口名称标识第二参数组中的第二PDR数据；将标识后的第二PDR数据、第二参数组中的第二FAR数据以及第二参数组中的其他参数绑定至新建PFCP协议消息中，得到目标PFCP协议消息；其中，第二参数组中的第二FAR数据包括第二接口的接口名称标识。
在其中一个实施例中，若初始PFCP协议消息为上行数据，则第一接口为S1-U接口，第二接口为SGI接口；若初始PFCP协议消息为下行数据，则第一接口为SGI接口，第二接口为S1-U接口。
在其中一个实施例中，重构模块，具体用于：在该会话管理功能实体的网元融合方式为将该SGW的功能和该PGW的功能逻辑合设的情况下，将第二转发规则作为该重构转发规则，该第二转发规则包括将来源于第一接口的数据转发至中间接口，并将来源于该中间接口的数据从第二接口输出。
在其中一个实施例中，该初始PFCP协议消息包括第三参数组，该第三参数组包括第三PDR数据和第三FAR数据；重构模块，具体用于：采用新增FAR数据的FAR标识替换第三PDR数据中包括的原始FAR标识，得到修改后的第三PDR数据，并根据修改后的第三PDR数据和新增FAR数据得到第四参数组；其中，修改后的第三PDR数据包括第一接口的接口名称标识，新增FAR数据包括中间接口的接口名称；采用中间接口的接口名称替换第三PDR数据中包括的第一接口的接口名称，得到替换后的第三PDR数据，并根据替换后的第三PDR数据和第三FAR数据得到第五参数组；其中，第三FAR数据包括第二接口的接口名称；根据第四参数组和第五参数组得到目标PFCP协议消息。
在其中一个实施例中，若初始PFCP协议消息为上行数据，则第一接口为S1-U接口，中间接口为S5/S8接口，第二接口为SGI接口；若初始PFCP协议消息为下行数据，则第一接口为SGI接口，中间接口为S5/S8接口，第二接口为S1-U接口。
在其中一个实施例中，第一确定模块，用于：根据该PFCP协议消息中的多个目标接口字段确定该初始PFCP协议消息是否为该目标消息类型；该多个目标接口字段至少包括源接口字段、目的接口字段以及3GPP接口类型字段。
在其中一个实施例中，该目标消息类型为4G会话建立消息。
在其中一个实施例中，该装置还包括：
发送模块，用于若该初始PFCP协议消息不为该4G会话建立消息，则直接将该初始PFCP协议消息发送至该用户面功能实体。
第三方面，本申请提供了一种通信系统，该通信系统包括会话管理功能实体、用户面功能实体以及执行如上述第一方面任一项所述的方法的通信设备。
第四方面，本申请提供了一种通信设备，包括：接收器、发送器、处理器和存储器，该存储器存储有计算机程序；
该接收器，用于接收会话管理功能实体发送的初始PFCP协议消息；
该处理器执行该计算机程序，用于对该初始PFCP协议消息进行识别，以确定该初始PFCP协议消息是否为目标消息类型；在该初始PFCP协议消息为该目标消息类型的情况下，确定该会话管理功能实体的网元融合方式与用户面功能实体的网元融合方式是否相互匹配，该网元融合方式用于指示融合SGW和PGW的网元功能的方式；并在不匹配的情况下，对该初始PFCP协议消息进行重构，得到目标PFCP协议消息；
该发送器，用于将该目标PFCP协议消息发送至该用户面功能实体。
第五方面，本申请还提供了一种计算机可读存储介质。计算机可读存储介质，其上存储有计算机程序，计算机程序被处理器执行时实现上述第一方面任一所述的消息传输方法。
第六方面，本申请还提供了一种芯片。该芯片包括可编程逻辑电路和/或程序指令，当芯片运行时实现上述第一方面任一所述的消息传输方法。
第七方面，本申请还提供了一种计算机程序产品。计算机程序产品，包括计算机程序，该计算机程序被处理器执行时实现上述第一方面任一所述的消息传输方法。
第八方面，本申请还提供了一种芯片，包括处理器，所述处理器被配置为从存储器中调用并运行计算机程序，以执行上述第一方面任一所述的消息传输方法。
本发明的一个或多个实施例的细节在下面的附图和描述中提出。本发明的其它特征、目的和优点将从说明书、附图以及权利要求书变得明显。
附图说明
为了更清楚地说明本申请实施例或传统技术中的技术方案，下面将对实施例或传统技术描述中所 需要使用的附图作简单地介绍，显而易见地，下面描述中的附图仅仅是本申请的实施例，对于本领域普通技术人员来讲，在不付出创造性劳动的前提下，还可以根据公开的附图获得其他的附图。
图1为一个实施例中消息传输方法的应用环境图；
图2为一个实施例中消息传输方法的流程示意图；
图3为一个实施例中的架构示意图；
图4为另一个实施例中的架构示意图；
图5为另一个实施例中架构示意图；
图6为另一个实施例中架构示意图；
图7为一个实施例中确定目标PFCP协议消息的流程示意图；
图8为另一个实施例中确定目标PFCP协议消息的流程示意图；
图9为一个实施例中重构过程的示意图；
图10为另一个实施例中确定目标PFCP协议消息的流程示意图；
图11为另一个实施例中重构过程的示意图；
图12为一个实施例中利用C-IWF进行异构SMF和UPF协同组网实现4G网络和5G网络融合的方法的应用环境示意图；
图13为一个实施例中消息传输装置的结构框图；
图14为一个实施例中通信设备的内部结构图；
图15为一个实施例中芯片的内部结构图。
具体实施方式
为了使本申请的目的、技术方案及优点更加清楚明白，以下结合附图及实施例，对本申请进行进一步详细说明。应当理解，此处描述的具体实施例仅仅用以解释本申请，并不用于限定本申请。
尽管会话管理功能实体(SMF)和用户面功能实体(UPF)之间的PFCP(Packet Forwarding Control Protocol，包转发控制协议)协议接口的PFCP协议已经在3GPP(3rd Generation Partnership Project，第三代合作伙伴计划)中标准化定义，但5G功能在融合4G网元(SGW和PGW)时，存在逻辑分设和合设两种架构，申请人发现，对4G网元的融合逻辑架构不同的SMF和UPF来说，二者之间无法对接，使得PFCP协议接口难以解耦，UPF与SMF之间的PFCP协议消息无法正常传输。
有鉴于此，本申请实施例中，可在用户面功能实体和会话管理实体之间设置定制化信令互通网关，可对SMF下发的初始PFCP协议消息的类型进行识别，并在初始PFCP协议消息为目标消息类型的情况下，确定会话管理功能实体的网元融合方式与用户面功能实体的网元融合方式是否相互匹配，在不匹配的情况下，对初始PFCP协议消息进行重构，并将重构得到的目标PFCP协议消息发送至UPF，确保SMF和UPF异构场景下的PFCP协议消息的正常传输，实现了异构SMF与UPF之间的4G网络和5G网络的融合部署。
本申请实施例提供的消息传输方法，可以应用于如图1所示的应用环境中。其中，通信设备101与会话管理功能实体102以及用户面功能实体103通信连接，通信设备101可以接收会话管理功能实体102发送的初始PFCP协议消息，并将重构处理得到的目标PFCP协议消息发送至用户面功能实体103。
其中，通信设备101可以为网关设备，例如可以为C-IWF(Customized-InterWorking Function，定制化信令互通网关)。会话管理功能实体可以为5G网络中的SMF(Session Management Function，会话管理功能)，且SMF可以融合有4G网络中的PGW-C(Packet Data Network Gateway Control Plane，分组数据网络网关控制平面)和/或SGW-C(Serving Gateway Control Plane，服务网关控制平面)的网元功能。用户面功能实体可以为5G网络中的UPF(User Plane Function，用户平面功能)，且UPF融合有4G网络中的PGW-U(Packet Gateway User Plane，分组数据网络网关用户平面)和/或SGW-U(Serving Gateway User Plane，服务网关用户平面)的网元功能。
需要说明的是，本申请实施例所带来的有益效果或者所解决的技术问题并不限定于这一个，还可以是其它隐含或者关联的问题，具体可以参见下述实施例的描述。
下面以具体地实施例对本申请的技术方案以及本申请的技术方案如何解决上述技术问题进行详细 说明。下面这几个具体的实施例可以相互结合，对于相同或相似的概念或过程可能在某些实施例中不再赘述。下面将结合附图，对本申请的实施例进行描述。
在一个实施例中，如图2所示，提供了一种消息传输方法，以该方法应用于图1中的通信设备101为例进行说明，包括以下步骤：
步骤201，接收会话管理功能实体发送的初始PFCP协议消息，并对初始PFCP协议消息进行识别，以确定初始PFCP协议消息是否为目标消息类型。
其中，初始PFCP协议消息可为会话管理功能实体需要发送至用户面功能实体的PFCP协议消息。相关技术中，会话管理功能实体和用户面功能实体通过PFCP协议接口对接，其中，PFCP协议接口主要负责建立和管理特点会话项目。本申请实施例中，通信设备设置于会话管理功能实体和用户面功能实体之间，例如，通信设备通过PFCP协议接口与会话管理功能实体和用户面功能实体对接，以通过PFCP协议接口获取初始PFCP协议消息，进而确定是否需要对初始PFCP协议消息进行重构，保证会话管理功能实体和用户面功能实体之间PFCP协议消息的顺利传输。
通信设备获取到初始PFCP协议消息后，识别初始PFCP协议消息是否为目标消息类型，其中，目标消息类型指与SGW网元和PGW网元相关的PFCP协议消息，或者说，目标消息类型为与4G会话业务相关的PFCP协议消息。
步骤202，在初始PFCP协议消息为目标消息类型的情况下，确定会话管理功能实体的网元融合方式与用户面功能实体的网元融合方式是否相互匹配。
若初始PFCP协议消息为目标消息类型，则初始PFCP协议消息的发送和接收识别均与SGW和PGW相关，则涉及到会话管理功能实体的网元融合方式与用户面功能实体的网元融合方式是否相互匹配，也即是，若会话管理功能实体的网元融合方式与用户面功能实体的网元融合方式不相互匹配，则用户面功能实体无法正常识别初始PFCP协议消息，则需要通信设备对该初始PFCP协议消息进行重构处理；若会话管理功能实体的网元融合方式与用户面功能实体的网元融合方式相互匹配，则用户面功能实体可以正常识别初始PFCP协议消息，通信设备无需对该初始PFCP协议消息进行处理。
具体的，网元融合方式用于指示融合SGW和PGW的网元功能的方式。其中，4G网络和5G网络融合的场景中，SGW网元功能被分为SGW-C和SGW-U，PGW网元功能被分为PGW-C和PGW-U。通常，4G网络和5G网络的融合架构分为两种，分别为标准定义架构和企业标准架构。请参考图3所示，在标准定义架构下，SGW为独立的网元，控制面的SGW-C并未与SMF合设，且用户面的SGW-U并未与UPF合设，而控制面的PGW-C则与SMF合设，且用户面的PGW-U与UPF合设。请参考图4所示，企业标准架构下，考虑到实际现网的应用情况，为了避免现网SGW大量扩容，将控制面的SGW-C和PGW-C均与SMF合设，且用户面的SGW-U和PGW-U均与UPF合设。
具体的，在现有的4G网络和5G网络融合的标准定义架构下，并没有规定4G功能与5G功能融合在一个网元上时网元内部的实现架构，当前的架构实现方案中，包括SGW与PGW逻辑合设的融合方式以及SGW与PGW逻辑分设的融合方式。请参考图5所示，示出了本申请实施例提供的一种SGW与PGW在SMF和UPF中逻辑合设的架构示意图。请参考图6所所示，示出了本申请实施例提供的一种SGW与PGW在SMF和UPF中逻辑分设的架构示意图。其中，只有SMF下发的信令的逻辑结构与UPF接收信令的逻辑结构相对应，UPF才可以接收SMF下发的PFCP协议消息，而异构的SMF与UPF则无法对接，也即是，当SMF和UPF中的一个为SGW与PGW逻辑合设的网元融合方式，而另一个为SGW与PGW逻辑分设的网元融合方式，则二者无法对接，从而导致PFCP协议接口难以解耦。
本申请实施例中，在初始PFCP协议消息为目标消息类型的情况下，确定会话管理功能实体的网元融合方式与用户面功能实体的网元融合方式是否相互匹配，以确定用户面功能实体是否可以直接接收初始PFCP协议消息，以保证会话管理功能实体和用户面功能实体可以正常对接。
一些实施例中，通信设备中可预先配置会话管理功能实体和用户面功能实体为逻辑异构还是逻辑同构，其中，若二者逻辑异构，则二者的网元融合方式不同；若二者逻辑同构，则二者的网元融合方式相同。或者，在另一些实施方式中，通信设备可根据接收到的初始PFCP协议消息确定会话管理功能实体的网元融合方式，并根据历史接收到的用户面功能实体发送的历史PFCP协议消息确定用户面功能实体的网元融合方式，从而在所述会话管理功能实体的网元融合方式与所述用户面功能实体的网元融合 方式不相同时，确定二者不匹配。
这样，通信设备可通过识别初始PFCP协议消息确定会话管理功能实体的网元融合方式，并在通过读取预先配置的内容明确会话管理功能实体和用户面功能实体为逻辑异构的情况下，确定二者不匹配，且对目标初始PFCP协议消息进行重构。
步骤203，在会话管理功能实体的网元融合方式与用户面功能实体的网元融合方式不匹配的情况下，对初始PFCP协议消息进行重构，得到目标PFCP协议消息，并将目标PFCP协议消息发送至用户面功能实体。
可以理解，会话管理功能实体下发的该初始PFCP协议消息的内部转发规则是与会话管理功能实体的网元融合方式相对应的，而用户面功能实体可以接收的PFCP协议消息的内部转发规则是与用户面功能实体的网元融合方式相对应的。
若确定会话管理功能实体的网元融合方式与用户面功能实体的网元融合方式不匹配，则通信设备对初始PFCP协议消息进行重构处理，以得到目标PFCP协议消息，而该目标PFCP协议消息的内部转发规则即与用户面功能实体的网元融合方式相对应。进而，直接将该目标PFCP协议消息发送至用户面功能实体，相应的，用户面功能实体可以正常识别目标PFCP协议消息，实现PFCP协议接口的解耦。另外可以理解的是，初始PFCP协议消息和目标PFCP协议消息中包括的传输数据是一致的。
上述消息传输方法中，通信设备接收会话管理功能实体发送的初始PFCP协议消息，并对初始PFCP协议消息进行识别，以确定初始PFCP协议消息是否为目标消息类型；在初始PFCP协议消息为目标消息类型的情况下，确定会话管理功能实体的网元融合方式与用户面功能实体的网元融合方式是否相互匹配，网元融合方式用于指示融合SGW和PGW的网元功能的方式；在会话管理功能实体的网元融合方式与用户面功能实体的网元融合方式不匹配的情况下，对初始PFCP协议消息进行重构，得到目标PFCP协议消息，并将目标PFCP协议消息发送至用户面功能实体。这样，由于在会话管理功能实体的网元融合方式与用户面功能实体的网元融合方式不相互匹配的情况下对初始PFCP协议消息进行了重构处理，因此，重构处理后的目标PFCP协议消息发送至用户面功能实体，可以被用户面功能实体正常接收，会话管理功能实体与用户面功能实体之间的PFCP协议接口可以正常解耦，确保会话管理功能实体和用户面功能实体可以正常对接，以助于实现异构SMF与UPF之间的4G网络和5G网络的融合部署。
下面对确定初始PFCP协议消息是否为目标消息类型进行说明。
在一个实施例中，目标消息类型为4G会话建立消息。
其中，SGW和PGW均为4G网元，因此，当初始PFCP协议消息为4G会话建立消息时，该初始PFCP协议消息才与SGW和PGW的网元融合方式相关，进而才需要确定是否需要对初始PFCP协议消息进行重构处理。
在一个实施例中，确定初始PFCP协议消息是否为目标消息类型，包括：根据PFCP协议消息中的多个目标接口字段确定初始PFCP协议消息是否为目标消息类型。其中，多个目标接口字段至少包括源接口字段、目的接口字段以及3GPP接口类型字段。
具体的，初始PFCP协议消息中包括PDR(Packet Detection Rule，包检测规则)数据和FAR(Forwarding Action Rules，转发行为规则)数据。PDR数据中包括源接口(Source Interface)字段以及3GPP接口类型(3GPP Interface Type)字段，通信设备可识别该源接口字段以及3GPP接口类型字段是否与4G会话相关。另外，FAR数据中包括目的接口(Destination Interface)字段和3GPP接口类型字段，通信设备可识别该目的接口字段和3GPP接口类型字段是否与4G会话相关。
若多个目标接口字段与4G会话相关，则初始PFCP协议消息为目标消息类型，也即是，初始PFCP协议消息为4G会话建立消息。例如，若确定3GPP接口为S1-U接口或者SGI接口等4G接口，则确定初始PFCP协议消息为4G会话建立消息。
在一个实施例中，该方法还包括：若初始PFCP协议消息不为4G会话建立消息，则直接将初始PFCP协议消息发送至用户面功能实体。
其中，若初始PFCP协议消息不为4G会话建立消息，例如初始PFCP协议消息为5G会话建立消息，则意味着该初始PFCP协议消息为5G网元SMF本身发送的，与4G网元的网元融合方式无关，接 收的5G网元UPF可直接识别该初始PFCP协议消息，因此，通信设备可直接将初始PFCP协议消息发送至用户面功能实体。例如，若确定3GPP接口为N3接口或者N6接口等5G接口，则为5G会话建立消息。
另外，本申请实施例中，若初始PFCP协议消息为4G会话建立消息，但是通信设备确定SMF与UPF逻辑同构，则相应的，通信设备也可直接将初始PFCP协议消息透传至用户面功能实体。
本申请实施例中，通信设备可根据PFCP协议消息中的源接口字段、目的接口字段以及3GPP接口类型字段快速确定初始PFCP协议消息是否为4G会话建立消息，确保了识别准确性和识别效率。并且，若初始PFCP协议消息不为4G会话建立消息，或者会话管理功能实体和用户面功能实体逻辑同构，通信设备则直接将初始PFCP协议消息发送至用户面功能实体，避免无用的重构过程，针对性的根据初始PFCP协议消息的消息类型对初始PFCP协议消息进行转发传输，再次确保传输效率。
下面对初始PFCP协议消息进行重构得到目标PFCP协议消息的过程进行说明。
在一个实施例中，如图7所示，示出了本申请实施例提供的一种确定目标PFCP协议消息的流程示意图。对初始PFCP协议消息进行重构，得到目标PFCP协议消息，包括：
步骤701，根据会话管理功能实体的网元融合方式和用户面功能实体的网元融合方式，确定重构转发规则。
其中，当会话管理功能实体的网元融合方式为逻辑分设而用户面功能实体的网元融合方式为逻辑合设，则根据逻辑合设时SGW和PGW的数据转发规则对初始PFCP协议消息进行重构处理。当会话管理功能实体的网元融合方式为逻辑合设而用户面功能实体的网元融合方式为逻辑分设，则根据逻辑分设时SGW和PGW的数据转发规则对初始PFCP协议消息进行重构处理。
在一个可选实施例中，根据会话管理功能实体的网元融合方式和用户面功能实体的网元融合方式，确定重构转发规则，包括：在会话管理功能实体的网元融合方式为将SGW的功能和PGW的功能逻辑分设的情况下，将第一转发规则作为重构转发规则，第一转发规则包括将来源于第一接口的数据从第二接口输出。
继续参考上文图5和图6所示，可见，当SMF的网元融合方式为将SGW的功能和PGW的功能逻辑分设的情况下，所下发的PFCP协议消息中的数据的转发规则为：从S1-U接口转发至S5/S8接口，并从S5/S8接口再转发至SGI接口，或者，从SGI接口转发至S5/S8接口，并从S5/S8接口再转发至S1-U接口。
而当SMF的网元融合方式为将SGW的功能和PGW的功能逻辑合设的情况下，所下发的PFCP协议消息中的数据的转发规则为：从S1-U接口转发至SGI接口，或者，从SGI接口转发至S1-U接口。
基于此，当会话管理功能实体的网元融合方式为将SGW的功能和PGW的功能逻辑分设时，对应的，应该将SGW的功能和PGW的功能逻辑合设时的第一转发规则作为重构转发规则。其中，第一接口为S1-U接口和SGI接口中的一个，而第二接口为S1-U接口和SGI接口中的另一个。
本申请实施例中，若初始PFCP协议消息为上行数据，则第一接口为S1-U接口，第二接口为SGI接口；若初始PFCP协议消息为下行数据，则第一接口为SGI接口，第二接口为S1-U接口。
也即是，若会话管理功能实体中对SGW的功能和PGW的功能逻辑分设，由于二者异构，则用户面功能实体所能识别的目标PFCP协议消息中的转发规则为从S1-U接口转发至SGI接口，或者，从SGI接口转发至S1-U接口。
具体的，若初始PFCP协议消息为基站发送给UPF的数据，则初始PFCP协议消息为上行数据，对应的，此时，第一接口为S1-U接口，第二接口为SGI接口。若初始PFCP协议消息为UPF发送给基站的数据，则初始PFCP协议消息为下行数据，对应的，此时，第一接口为SGI接口，第二接口为S1-U接口。
其中，S1-U接口为eNodeB(Evolved Node B，演进型基站)与SGW之间的互连接口，用于数据报文传输。SGI接口为PGW和分组数据网络之间的接口。
在另一个可选实施例中，根据会话管理功能实体的网元融合方式和用户面功能实体的网元融合方式，确定重构转发规则，包括：在会话管理功能实体的网元融合方式为将SGW的功能和PGW的功能逻辑合设的情况下，将第二转发规则作为重构转发规则，第二转发规则包括将来源于第一接口的数据转 发至中间接口，并将来源于中间接口的数据从第二接口输出。
继续参考上文图5和图6所示，基于上文的说明可见，当会话管理功能实体的网元融合方式为将SGW的功能和PGW的功能逻辑合设时，对应的，由于会话管理功能实体与用户面功能实体异构，因此，应该将SGW的功能和PGW的功能逻辑分设时的第二转发规则作为重构转发规则。其中，第一接口为S1-U接口和SGI接口中的一个，而第二接口为S1-U接口和SGI接口中的另一个。
继续参考图5和图6所示，本申请实施例中，若所述初始PFCP协议消息为上行数据，则所述第一接口为S1-U接口，所述中间接口为S5/S8接口，所述第二接口为SGI接口；若所述初始PFCP协议消息为下行数据，则所述第一接口为SGI接口，所述中间接口为S5/S8接口，所述第二接口为S1-U接口。
也即是，若会话管理功能实体中对SGW的功能和PGW的功能逻辑合设，由于二者异构，则用户面功能实体所能识别的目标PFCP协议消息中的转发规则为从S1-U接口转发至S5/S8接口，并从S5/S8接口再转发至SGI接口；或者，转发规则为从SGI接口转发至S5/S8接口，并从S5/S8接口再转发至S1-U接口。其中，S5接口是本地SGW连接到本地PGW时使用的接口，S8接口是本地SGW与外地PGW连接使用的接口。
步骤702，根据重构转发规则对初始PFCP协议消息进行重构，得到目标PFCP协议消息。
下面首先针对将第一转发规则作为重构转发规则，对初始PFCP协议消息进行重构的过程进行说明。
在一个实施例中，如图8所示，示出了本申请实施例提供的另一种确定目标PFCP协议消息的流程示意图。根据重构转发规则对初始PFCP协议消息进行重构，得到目标PFCP协议消息，包括：
步骤801，对第一参数组中的第一PDR数据和第一FAR数据进行删除处理。
步骤802，根据第一转发规则，利用第一接口的接口名称标识第二参数组中的第二PDR数据。
其中，初始PFCP协议消息包括第一参数组和第二参数组，第一参数组与SGW和PGW中的一个对应，第二参数组与SGW和PGW中的另一个对应。
第一参数组包括第一PDR数据和第一FAR数据。并且，第一PDR数据中包括一组FAR ID、QER ID、URR ID以及第一接口的接口名称等数据；第一FAR数据中包含中间接口的接口名称。
第二参数组包括第二PDR数据和第二FAR数据。并且，第二PDR数据中也包括另一组FAR ID、QER ID、URR ID以及中间接口的接口名称等数据；第二FAR数据中包含第二接口的接口名称。其中，ID意为标识或者名称；QER为QoS Enforcement Rules的简称，指QoS实施规则，其中QoS为Quality of Service，表示服务质量；URR是Usage Reporting Rules的简称，指使用报告规则。
由于将第一转发规则作为重构转发规则，而第一转发规则中仅需保留由第一接口转发至第二接口的相关数据，因此，需要对第一参数组和第二参数组中的一些数据进行删除处理，并重构各数据，得到目标PFCP协议消息。
具体的，可对第一参数组中的第一PDR数据和第一FAR数据进行删除处理，其中，例如，可删除第一PDR数据中的FAR ID、QER ID和URR ID，删除第一FAR数据中的中间接口的接口名称。
进而，采用第一PDR数据中剩余的第一接口的接口名称替换第二PDR数据中包括的中间接口的接口名称，相当于，采用第一接口的接口名称标识第二参数组中的第二PDR数据，这样，标识后的第二PDR数据中则包括第一接口的接口名称、FAR ID、QER ID以及URR ID等数据。
另外，由于第二FAR数据中包含第二接口的接口名称，因此，第二FAR数据被第二接口的接口名称标识。
步骤803，将标识后的第二PDR数据、第二参数组中的第二FAR数据以及第二参数组中的其他参数绑定至新建PFCP协议消息中，得到目标PFCP协议消息。其中，第二参数组中的第二FAR数据包括第二接口的接口名称标识。
通信设备可生成新建PFCP协议消息，并将标识后的第二PDR数据和标识后的第二FAR数据绑定至新建PFCP协议消息中，对于第二参数组中的其他参数，也同步绑定至新建PFCP协议消息中，得到目标PFCP协议消息。可以理解，由于进行删除处理，所得到的目标PFCP协议消息中仅包括一组PDR数据和FAR数据，且分别采用第一接口和第二接口的接口名称标识，因此，目标PFCP协议消息可以被用户面功能实体识别。
为便于理解，下面以图9所示出的会话管理功能实体为逻辑分设时的PFCP协议消息结构进一步对重构过程进行说明。
如图9所示，示出了对SMF下发的初始PFCP协议消息进行重构的过程示意图。其中，在SMF向UPF发送的初始PFCP协议消息为上行数据时，第一参数组与SGW-U对应，第一PDR数据包括S1-U接口的接口名称，用于表征数据的来源接口；第一PDR数据还包括FAR ID1、QER ID1和URR ID1。并且，根据FAR ID1可确定与第一PDR数据绑定的第一FAR数据，且第一FAR数据包括S5/S8接口的接口名称，用于表征数据的目的接口。
第二参数组与PGW-U对应，第二PDR数据包括S5/S8接口的接口名称，用于表征数据的来源接口；第二PDR数据还包括FAR ID2、QER ID2和URR ID2。并且，根据FAR ID2可确定与第二PDR数据绑定的第二FAR数据，且第二FAR数据包括SGI接口的接口名称，用于表征数据的目的接口。对第一PDR数据和第一FAR数据进行删除处理等操作，也即是，删除图9中虚线框中的内容，并且，将S1-U接口的接口名称加入第二PDR数据中，从而得到重构后的转发规则对应的目标PFCP协议消息。
继续参考图9所示，其中，在SMF向UPF发送初始PFCP协议消息为下行数据时，第一参数组与PGW-U对应，第一PDR数据包括SGI接口的接口名称，用于表征数据的来源接口；第一PDR数据还包括FAR ID3、QER ID3和URR ID3。并且，根据FAR ID3可确定与第一PDR数据绑定的第一FAR数据，且第一FAR数据包括S5/S8接口的接口名称，用于表征数据的目的接口。
第二参数组与SGW-U对应，第二PDR数据包括S5/S8接口的接口名称，用于表征数据的来源接口；第二PDR数据还包括FAR ID4、QER ID4和URR ID4。并且，根据FAR ID4可确定与第二PDR数据绑定的第二FAR数据，且第二FAR数据包括S1-U接口的接口名称，用于表征数据的目的接口。对第一PDR数据和第一FAR数据进行删除处理等操作，也即是，删除图9虚线框中的内容，并且，采用SGI接口的接口名称标识第二PDR数据，从而得到重构后的转发规则对应的目标PFCP协议消息。
下面继续针对将第二转发规则作为重构转发规则，对初始PFCP协议消息进行重构的过程进行说明。
在一个实施例中，如图10所示，示出了本申请实施例提供的另一种确定目标PFCP协议消息的流程示意图。根据重构转发规则对初始PFCP协议消息进行重构，得到目标PFCP协议消息，包括：
步骤1001，采用新增FAR数据的FAR标识替换第三PDR数据中包括的原始FAR标识，得到修改后的第三PDR数据，并根据修改后的第三PDR数据和新增FAR数据得到第四参数组。其中，修改后的第三PDR数据包括第一接口的接口名称标识，新增FAR数据包括中间接口的接口名称。
其中，初始PFCP协议消息包括第三参数组，第三参数组包括第三PDR数据和第三FAR数据。
步骤1002，采用中间接口的接口名称替换第三PDR数据中包括的第一接口的接口名称，得到替换后的第三PDR数据，并根据替换后的第三PDR数据和第三FAR数据得到第五参数组。其中，第三FAR数据包括第二接口的接口名称。
步骤1003，根据第四参数组和第五参数组得到目标PFCP协议消息。
为便于理解，下面以图11所示出的会话管理功能实体为逻辑合设时的PFCP协议消息结构进一步对重构过程进行说明。
如图11所示，示出了对SMF下发的初始PFCP协议消息进行重构的过程示意图。其中，在SMF向UPF发送的初始PFCP协议消息为上行数据时，第三参数组包括第三PDR数据和第三FAR数据。第三PDR数据包括S1-U接口的接口名称，用于表征数据的来源接口；第三PDR数据还包括FAR ID0、QER ID0和URR ID0。并且，根据FAR ID0可确定与第三PDR数据绑定的第三FAR数据，且第三FAR数据包括SGI接口的接口名称。
在重构过程中，将第三PDR数据与新增FAR数据绑定，在绑定过程中，采用新增FAR数据的FAR标识FAR ID0'替换原始FAR标识FAR ID0。另外，修改后的第三PDR数据包括所述第一接口的接口名称标识，也即是，采用第一接口的接口名称标识第三PDR数据；并采用中间接口的接口名称标识新增FAR数据，根据修改后的第三PDR数据和新增FAR数据得到第四参数组。也即是，第四参数组中包括的修改后的第三PDR数据中包含S1-U接口的接口名称、FAR ID0'、QER ID0和URR ID0；第四参数组中包括的标识后的第三FAR数据中包含S5/S8接口的接口名称，用于表征数据的目的接口。
另外，还生成第五参数组。第五参数组中包括替换后的第三PDR数据，替换后的第三PDR数据是通过采用中间接口的接口名称替换第三PDR数据中包括的第一接口的接口名称得到的，也即是，第五参数组中包括的替换后的第三PDR数据中包含S5/S8接口的接口名称、FAR ID0、QER ID0和URR ID0。第五参数组中还包括与替换后的第三PDR数据绑定的被第二接口的接口名称标识的第三FAR数据，也即是，第五参数组中包括的第三FAR数据中包括SGI接口的接口名称。可以理解的是，第四参数组与SGW-U对应，且第五参数组与PGW-U对应。
将所得到的第四参数组和第五参数组以及初始PFCP协议消息中的其他数据和参数迁移至新建的PFCP协议消息中，即可得到目标PFCP协议消息。这样，目标PFCP协议消息即可符合逻辑分设的转发规则，则可以被逻辑分设的UPF识别，实现PFCP协议接口解耦。
继续参考图11所示，其中，在SMF向UPF发送的初始PFCP协议消息为下行数据时，第三参数组包括第三PDR数据和第三FAR数据。第三PDR数据包括SGI接口的接口名称，用于表征数据的来源接口；第三PDR数据还包括FAR ID1、QER ID1和URR ID1。并且，根据FAR ID1可确定与第三PDR数据绑定的第三FAR数据，且第三FAR数据包括S1-U接口的接口名称。
在重构过程中，将第三PDR数据与新增FAR数据绑定，在绑定过程中，采用新增FAR数据的FAR标识FAR ID1'替换原始FAR ID1。另外，采用第一接口的接口名称标识第三PDR数据，采用中间接口的接口名称标识新增FAR数据，得到第四参数组。也即是，第四参数组中包括的修改后的第三PDR数据中包含SGI接口的接口名称、FAR ID1'、QER ID1和URR ID1；第四参数组中包括的第三FAR数据中包含S5/S8接口的接口名称，用于表征数据的目的接口。
另外，还生成第五参数组。第五参数组中包括的替换后的第三PDR数据中包含S5/S8接口的接口名称、FAR ID1、QER ID1和URR ID1。第五参数组中还包括与替换后的第三PDR数据绑定的被第二接口的接口名称标识的第三FAR数据，也即是，第五参数组中包括的第三FAR数据中包括S1-U接口的接口名称。可以理解的是，第四参数组与PGW-C对应，且第五参数组与SGW-C对应。
将所得到的第四参数组和第五参数组以及初始PFCP协议消息中的其他数据和参数迁移至新建的PFCP协议消息中，即可得到目标PFCP协议消息。这样，目标PFCP协议消息即可符合逻辑分设的转发规则，则可以被逻辑分设的UPF识别，实现PFCP协议接口解耦。
本申请实施例中，根据重构转发规则对初始PFCP协议消息进行重构，得到目标PFCP协议消息，从而将目标PFCP协议消息发送至用户面功能实体，由此实现了异构SMF与UPF之间的4G网络和5G网络的融合部署。通过增加通信设备C-IWF对PFCP协议消息进行识别、分析、重构的功能，进而解决了异构SMF与UPF无法适配的问题。并且，针对两种异构情况，分别提出了对应的PFCP协议消息重构方案，基于此，通信设备对PFCP协议接口消息进行重构，在存在异构SMF与UPF部署需求的场景中，无需对现网进行复杂的改造，即可实现PFCP协议接口解耦，提升了定制网络部署的灵活性以及设备选择的多样性，从而促进5G ToB行业总体生态的发展。
下面以一个具体的通信场景对本申请实施例提出的方法进行具体说明。本申请实施例提供了一种利用C-IWF进行异构SMF和UPF协同组网实现4G网络和5G网络融合的方法。该方法可应用于如图12所示的应用环境中。需要说明的是，图12仅为示例性的应用环境示意图，其中还示出了与SMF和UPF对接的其他网元。该方法包括以下内容：
C-IWF在转发初始PFCP协议消息时，对初始PFCP协议消息进行识别，识别内容包括：根据PDR中的Source Interface、Network Instance、3GPP Interface Type以及FAR中的Destination Interface、3GPP Interface Type等字段，判断SMF下发的初始PFCP协议消息是否为4G会话建立消息。以及，识别SMF下发的初始PFCP协议消息对应的是SGW与PGW逻辑合设还是逻辑分设，也即是，确定SMF与UPF是同构还是异构。
其中，当SMF下发的初始PFCP协议消息为5G会话建立的消息时，C-IWF直接透传该初始PFCP协议消息至UPF。当SMF下发的初始PFCP协议消息为4G会话建立的消息且SMF与UPF同构时，C-IWF直接透传该初始PFCP协议消息至UPF。当SMF下发的初始PFCP协议消息为4G会话建立的消息且SMF与UPF异构时，C-IWF则对该初始PFCP协议消息进行重构。重构过程如下：
(1)当SMF中SGW-C与PGW-C为逻辑分设，而UPF中SGW-U与PGW-U为逻辑合设时：
逻辑分设的SMF下发给逻辑合设的UPF的消息中包含转发规则：S1-U—S5/S8，S5/S8—SGI。对接逻辑合设的UPF时，C-IWF将消息中的规则合设为S1-U—SGI，并且，删除消息中多余的FAR和PDR，并将原始的S5/S8—SGI(上行数据中)或S5/S8—S1-U(下行数据中)的QER与URR的绑定关系重新绑定至与S1-U—SGI规则对应的PDR数据上。
(2)当SMF中SGW-C与PGW-C为逻辑合设，而UPF中SGW-U与PGW-U为逻辑分设时：
逻辑合设的SMF下发给逻辑分设的UPF的消息中包含转发规则S1-U—SGI。对接逻辑分设的UPF时，C-IWF将消息中的S1-U—SGI拆解为S1-U—S5/S8、S5/S8—SGI。创建新的FAR(S5/S8目的方向)和PDR(S5/S8来源方向)，并将原始S1-U—SGI规则对应的QER和URR的绑定关系重新绑定至与新的S1-U—S5/S8以及S5/S8—SGI规则对应的PDR数据上。
本申请实施例中，在异构的SMF与UPF之间，通过C-IWF对PFCP协议消息进行转发，并且转发过程中通过识别SMF发送的PFCP协议消息，依照PDR数据和FAR数据判断数据流向和信息，根据判断结果以及UPF接收方的实现逻辑对PFCP协议消息进行重构，使得UPF可以正确识别接收重构后得PFCP协议消息，保证PFCP协议接口得解耦，无需对现网进行复杂的改造即可实现异构SMF和UPF下的4G网络和5G网络的融合。
应该理解的是，虽然如上所述的各实施例所涉及的流程图中的各个步骤按照箭头的指示依次显示，但是这些步骤并不是必然按照箭头指示的顺序依次执行。除非本文中有明确的说明，这些步骤的执行并没有严格的顺序限制，这些步骤可以以其它的顺序执行。而且，如上所述的各实施例所涉及的流程图中的至少一部分步骤可以包括多个步骤或者多个阶段，这些步骤或者阶段并不必然是在同一时刻执行完成，而是可以在不同的时刻执行，这些步骤或者阶段的执行顺序也不必然是依次进行，而是可以与其它步骤或者其它步骤中的步骤或者阶段的至少一部分轮流或者交替地执行。
基于同样的发明构思，本申请实施例还提供了一种用于实现上述所涉及的消息传输方法的消息传输装置。该装置所提供的解决问题的实现方案与上述方法中所记载的实现方案相似，故下面所提供的一个或多个消息传输装置实施例中的具体限定可以参见上文中对于消息传输方法的限定，在此不再赘述。
在一个实施例中，如图13所示，提供了一种消息传输装置，该消息传输装置1300包括：第一确定模块1301、第二确定模块1302和重构模块1303，其中：
第一确定模块1301，用于接收会话管理功能实体发送的初始PFCP协议消息，并对该初始PFCP协议消息进行识别，以确定该初始PFCP协议消息是否为目标消息类型；
第二确定模块1302，用于在该初始PFCP协议消息为该目标消息类型的情况下，确定该会话管理功能实体的网元融合方式与用户面功能实体的网元融合方式是否相互匹配，该网元融合方式用于指示融合SGW和PGW的网元功能的方式；
重构模块1303，用于在该会话管理功能实体的网元融合方式与用户面功能实体的网元融合方式不匹配的情况下，对该初始PFCP协议消息进行重构，得到目标PFCP协议消息，并将该目标PFCP协议消息发送至该用户面功能实体。
在一个实施例中，重构模块1303，具体用于：根据该会话管理功能实体的网元融合方式和该用户面功能实体的网元融合方式，确定重构转发规则；根据该重构转发规则对该初始PFCP协议消息进行重构，得到目标PFCP协议消息。
在一个实施例中，重构模块1303，具体用于：在该会话管理功能实体的网元融合方式为将该SGW的功能和该PGW的功能逻辑分设的情况下，将第一转发规则作为该重构转发规则，该第一转发规则包括将来源于第一接口的数据从第二接口输出。
在一个实施例中，该初始PFCP协议消息包括第一参数组和第二参数组，该第一参数组与该SGW和该PGW中的一个对应，该第二参数组与该SGW和该PGW中的另一个对应；重构模块1303，具体用于：对第一参数组中的第一PDR数据和第一FAR数据进行删除处理；根据第一转发规则，利用第一接口的接口名称标识第二参数组中的第二PDR数据；将标识后的第二PDR数据、第二参数组中的第二FAR数据以及第二参数组中的其他参数绑定至新建PFCP协议消息中，得到目标PFCP协议消息；其中，第二参数组中的第二FAR数据包括第二接口的接口名称标识。
在一个实施例中，若初始PFCP协议消息为上行数据，则第一接口为S1-U接口，第二接口为SGI 接口；若初始PFCP协议消息为下行数据，则第一接口为SGI接口，第二接口为S1-U接口。
在一个实施例中，重构模块1303，具体用于：在该会话管理功能实体的网元融合方式为将该SGW的功能和该PGW的功能逻辑合设的情况下，将第二转发规则作为该重构转发规则，该第二转发规则包括将来源于第一接口的数据转发至中间接口，并将来源于该中间接口的数据从第二接口输出。
在一个实施例中，该初始PFCP协议消息包括第三参数组，该第三参数组包括第三PDR数据和第三FAR数据；重构模块1303，具体用于：采用新增FAR数据的FAR标识替换第三PDR数据中包括的原始FAR标识，得到修改后的第三PDR数据，并根据修改后的第三PDR数据和新增FAR数据得到第四参数组；其中，修改后的第三PDR数据包括第一接口的接口名称标识，新增FAR数据包括中间接口的接口名称；采用中间接口的接口名称替换第三PDR数据中包括的第一接口的接口名称，得到替换后的第三PDR数据，并根据替换后的第三PDR数据和第三FAR数据得到第五参数组；其中，第三FAR数据包括第二接口的接口名称；根据第四参数组和第五参数组得到目标PFCP协议消息。
在一个实施例中，若初始PFCP协议消息为上行数据，则第一接口为S1-U接口，中间接口为S5/S8接口，第二接口为SGI接口；若初始PFCP协议消息为下行数据，则第一接口为SGI接口，中间接口为S5/S8接口，第二接口为S1-U接口。
在一个实施例中，第一确定模块1301，用于：根据该PFCP协议消息中的多个目标接口字段确定该初始PFCP协议消息是否为该目标消息类型；该多个目标接口字段至少包括源接口字段、目的接口字段以及3GPP接口类型字段。
在一个实施例中，该目标消息类型为4G会话建立消息。
在一个实施例中，该装置还包括：
发送模块，用于若该初始PFCP协议消息不为该4G会话建立消息，则直接将该初始PFCP协议消息发送至该用户面功能实体。
上述消息传输装置中的各个模块可全部或部分通过软件、硬件及其组合来实现。上述各模块可以硬件形式内嵌于或独立于计算机设备中的处理器中，也可以以软件形式存储于计算机设备中的存储器中，以便于处理器调用执行以上各个模块对应的操作。
在一个实施例中，本申请提供了一种通信系统，该通信系统包括会话管理功能实体、用户面功能实体以及执行如上述实施例中的消息传输方法的通信设备。
图14是本申请实施例提供的通信设备的结构示意图。图14所示的通信设备1400包括：至少一个处理器1401、存储器1402、至少一个网络接口1404。通信设备1400中的各个组件通过总线系统1405耦合在一起。可理解，总线系统1405用于实现这些组件之间的连接通信。总线系统1405除包括数据总线之外，还包括电源总线、控制总线和状态信号总线。但是为了清楚说明起见，在图14中将各种总线都标为总线系统1405。另外，本申请实施例中，还包括收发器1406，收发器可以是多个元件，即包括发送器和接收器，提供用于在传输介质上与各种其他装置通信的单元。
可以理解，本发明实施例中的存储器1402可以是易失性存储器或非易失性存储器，或可包括易失性和非易失性存储器两者。其中，非易失性存储器可以是只读存储器(Read-OnlyMemory，ROM)、可编程只读存储器(ProgrammableROM，PROM)、可擦除可编程只读存储器(ErasablePROM，EPROM)、电可擦除可编程只读存储器(ElectricallyEPROM，EEPROM)或闪存。易失性存储器可以是随机存取存储器(RandomAccessMemory，RAM)，其用作外部高速缓存。通过示例性但不是限制性说明，许多形式的RAM可用，例如静态随机存取存储器(StaticRAM，SRAM)、动态随机存取存储器(DynamicRAM，DRAM)、同步动态随机存取存储器(SynchronousDRAM，SDRAM)、双倍数据速率同步动态随机存取存储器(DoubleDataRate SDRAM，DDRSDRAM)、增强型同步动态随机存取存储器(Enhanced SDRAM，ESDRAM)、同步连接动态随机存取存储器(SynchlinkDRAM，SLDRAM)和直接内存总线随机存取存储器(DirectRambusRAM，DRRAM)。本发明实施例描述的系统和方法的存储器1402旨在包括但不限于这些和任意其它适合类型的存储器。
在一些实施方式中，存储器1402存储了如下的元素，可执行模块或者数据结构，或者他们的子集，或者他们的扩展集：操作系统1421。其中，操作系统1421，包含各种系统程序，例如框架层、核心库层、驱动层等，用于实现各种基础业务以及处理基于硬件的任务。
在本申请实施例中，通过调用存储器1402存储的程序或指令，使得：接收器，用于接收会话管理功能实体发送的初始PFCP协议消息；处理器，用于对该初始PFCP协议消息进行识别，以确定该初始PFCP协议消息是否为目标消息类型；在该初始PFCP协议消息为该目标消息类型的情况下，确定该会话管理功能实体的网元融合方式与用户面功能实体的网元融合方式是否相互匹配，该网元融合方式用于指示融合SGW和PGW的网元功能的方式；在该会话管理功能实体的网元融合方式与用户面功能实体的网元融合方式不匹配的情况下，对该初始PFCP协议消息进行重构，得到目标PFCP协议消息；发送器，用于将该目标PFCP协议消息发送至该用户面功能实体。
上述本发明实施例揭示的部分或者全部方法还可以应用于处理器1401中，或者由处理器1401实现，或者由处理器1401与其他元件(例如收发机)配合实现。处理器1401可能是一种集成电路芯片，具有信号的处理能力。在实现过程中，上述方法的各步骤可以通过处理器1401中的硬件的集成逻辑电路或者软件形式的指令完成。上述的处理器1401可以是通用处理器、数字信号处理器(DigitalSignalProcessor，DSP)、专用集成电路(ApplicationSpecific IntegratedCircuit，ASIC)、现成可编程门阵列(FieldProgrammableGateArray，FPGA)或者其他可编程逻辑器件、分立门或者晶体管逻辑器件、分立硬件组件。可以实现或者执行本发明实施例中的公开的各方法、步骤及逻辑框图。通用处理器可以是微处理器或者该处理器也可以是任何常规的处理器等。结合本发明实施例所公开的方法的步骤可以直接体现为硬件译码处理器执行完成，或者用译码处理器中的硬件及软件模块组合执行完成。软件模块可以位于随机存储器，闪存、只读存储器，可编程只读存储器或者电可擦写可编程存储器、寄存器等本领域成熟的存储介质中。该存储介质位于存储器1402，处理器1401读取存储器1402中的信息，结合其硬件完成上述方法的步骤。
可以理解的是，本发明实施例描述的这些实施例可以用硬件、软件、固件、中间件、微码或其组合来实现。对于硬件实现，处理单元可以实现在一个或多个专用集成电路(ApplicationSpecificIntegratedCircuits，ASIC)、数字信号处理器(DigitalSignalProcessing，DSP)、数字信号处理设备(DSPDevice，DSPD)、可编程逻辑设备(ProgrammableLogicDevice，PLD)、现场可编程门阵列(Field-ProgrammableGateArray，FPGA)、通用处理器、控制器、微控制器、微处理器、用于执行本申请所述功能的其它电子单元或其组合中。
对于软件实现，可通过执行本发明实施例所述功能的模块(例如过程、函数等)来实现本发明实施例所述的技术。软件代码可存储在存储器中并通过处理器1401执行。存储器可以在处理器1401中或在处理器1401外部实现。
在一个实施例中，处理器执行计算机程序，具体用于根据该会话管理功能实体的网元融合方式和该用户面功能实体的网元融合方式，确定重构转发规则；根据该重构转发规则对该初始PFCP协议消息进行重构，得到目标PFCP协议消息。
在一个实施例中，处理器执行计算机程序，具体用于在该会话管理功能实体的网元融合方式为将该SGW的功能和该PGW的功能逻辑分设的情况下，将第一转发规则作为该重构转发规则，该第一转发规则包括将来源于第一接口的数据从第二接口输出。
在一个实施例中，处理器执行计算机程序，具体用于对第一参数组中的第一PDR数据和第一FAR数据进行删除处理；根据第一转发规则，利用第一接口的接口名称标识第二参数组中的第二PDR数据；将标识后的第二PDR数据、第二参数组中的第二FAR数据以及第二参数组中的其他参数绑定至新建PFCP协议消息中，得到目标PFCP协议消息；其中，第二参数组中的第二FAR数据包括第二接口的接口名称标识。
在一个实施例中，处理器执行计算机程序，具体用于在该会话管理功能实体的网元融合方式为将该SGW的功能和该PGW的功能逻辑合设的情况下，将第二转发规则作为该重构转发规则，该第二转发规则包括将来源于第一接口的数据转发至中间接口，并将来源于该中间接口的数据从第二接口输出。
在一个实施例中，处理器执行计算机程序，具体用于采用新增FAR数据的FAR标识替换第三PDR数据中包括的原始FAR标识，得到修改后的第三PDR数据，并根据修改后的第三PDR数据和新增FAR数据得到第四参数组；其中，修改后的第三PDR数据包括第一接口的接口名称标识，新增FAR数据包括中间接口的接口名称；采用中间接口的接口名称替换第三PDR数据中包括的第一接口的接口名称， 得到替换后的第三PDR数据，并根据替换后的第三PDR数据和第三FAR数据得到第五参数组；其中，第三FAR数据包括第二接口的接口名称；根据第四参数组和第五参数组得到目标PFCP协议消息。
在一个实施例中，处理器执行计算机程序，具体用于根据该PFCP协议消息中的多个目标接口字段确定该初始PFCP协议消息是否为该目标消息类型；该多个目标接口字段至少包括源接口字段、目的接口字段以及3GPP接口类型字段。
在一个实施例中，该发送器用于若该初始PFCP协议消息不为该4G会话建立消息，则直接将该初始PFCP协议消息发送至该用户面功能实体。
本领域技术人员可以理解，图14中示出的结构，仅仅是与本申请方案相关的部分结构的框图，并不构成对本申请方案所应用于其上的通信设备的限定，具体的通信设备可以包括比图中所示更多或更少的部件，或者组合某些部件，或者具有不同的部件布置。
在一个实施例中，提供了一种芯片，图15是本申请实施例的芯片的示意性结构图。图15所示的芯片1500包括处理器1510，处理器1510可以从存储器中调用并运行计算机程序，以实现本申请实施例中的方法。
一些实施例中，如图15所示，芯片1500还可以包括存储器1520。其中，处理器1510可以从存储器1520中调用并运行计算机程序，以实现本申请实施例中的方法。其中，存储器1520可以是独立于处理器1510的一个单独的器件，也可以集成在处理器1510中。
一些实施例中，该芯片1500还可以包括输入接口1530。其中，处理器1510可以控制该输入接口1530与其他设备或芯片进行通信，具体地，可以获取其他设备或芯片发送的信息或数据。一些实施例中，该芯片1500还可以包括输出接口1540。其中，处理器1510可以控制该输出接口1540与其他设备或芯片进行通信，具体地，可以向其他设备或芯片输出信息或数据。
一些实施例中，该芯片1500可应用于本申请实施例中通信设备，并且该芯片1500可以实现本申请实施例的各个方法中通信设备实现的相应流程，为了简洁，在此不再赘述。
应理解，本申请实施例提到的芯片1500还可以称为系统级芯片，系统芯片，芯片系统或片上系统芯片等。应理解，本申请实施例的处理器可能是一种集成电路芯片，具有信号的处理能力。在实现过程中，上述方法实施例的各步骤可以通过处理器中的硬件的集成逻辑电路或者软件形式的指令完成。上述的处理器可以是通用处理器、数字信号处理器(Digital Signal Processor，DSP)、专用集成电路(Application Specific Integrated Circuit，ASIC)、现成可编程门阵列(Field Programmable Gate Array，FPGA)或者其他可编程逻辑器件、分立门或者晶体管逻辑器件、分立硬件组件。可以实现或者执行本申请实施例中的公开的各方法、步骤及逻辑框图。通用处理器可以是微处理器或者该处理器也可以是任何常规的处理器等。结合本申请实施例所公开的方法的步骤可以直接体现为硬件译码处理器执行完成，或者用译码处理器中的硬件及软件模块组合执行完成。软件模块可以位于随机存储器，闪存、只读存储器，可编程只读存储器或者电可擦写可编程存储器、寄存器等本领域成熟的存储介质中。该存储介质位于存储器，处理器读取存储器中的信息，结合其硬件完成上述方法的步骤。
在一个实施例中，本申请还提供了一种计算机可读存储介质。该计算机可读存储介质，其上存储有计算机程序，计算机程序被处理器执行时实现上述方法实施例中的步骤。
在一个实施例中，本申请还提供了一种计算机程序产品。该计算机程序产品，包括计算机程序，该计算机程序被处理器执行时实现上述方法实施例中的步骤。
上述消息传输方法、装置、系统、设备、存储介质及计算机程序产品，通信设备接收会话管理功能实体发送的初始PFCP协议消息，并对初始PFCP协议消息进行识别，以确定初始PFCP协议消息是否为目标消息类型；在初始PFCP协议消息为目标消息类型的情况下，确定会话管理功能实体的网元融合方式与用户面功能实体的网元融合方式是否相互匹配，网元融合方式用于指示融合SGW和PGW的网元功能的方式；在不匹配的情况下，对初始PFCP协议消息进行重构，得到目标PFCP协议消息，并将目标PFCP协议消息发送至用户面功能实体。这样，由于在会话管理功能实体的网元融合方式与用户面功能实体的网元融合方式不相互匹配的情况下对初始PFCP协议消息进行了重构处理，因此，重构处理后的目标PFCP协议消息发送至用户面功能实体，可以被用户面功能实体正常接收，会话管理功能实体与用户面功能实体之间的PFCP协议接口可以正常解耦，确保会话管理功能实体和用户面功能实体可以 正常对接，以助于实现异构SMF与UPF之间的4G网络和5G网络的融合部署。
本领域普通技术人员可以理解实现上述实施例方法中的全部或部分流程，是可以通过计算机程序来指令相关的硬件来完成，所述的计算机程序可存储于一非易失性计算机可读取存储介质中，该计算机程序在执行时，可包括如上述各方法的实施例的流程。其中，本申请所提供的各实施例中所使用的对存储器、数据库或其它介质的任何引用，均可包括非易失性和易失性存储器中的至少一种。非易失性存储器可包括只读存储器(Read-Only Memory，ROM)、磁带、软盘、闪存、光存储器、高密度嵌入式非易失性存储器、阻变存储器(ReRAM)、磁变存储器(Magnetoresistive Random Access Memory，MRAM)、铁电存储器(Ferroelectric Random Access Memory，FRAM)、相变存储器(Phase Change Memory，PCM)、石墨烯存储器等。易失性存储器可包括随机存取存储器(Random Access Memory，RAM)或外部高速缓冲存储器等。作为说明而非局限，RAM可以是多种形式，比如静态随机存取存储器(Static Random Access Memory，SRAM)或动态随机存取存储器(Dynamic Random Access Memory，DRAM)等。本申请所提供的各实施例中所涉及的数据库可包括关系型数据库和非关系型数据库中至少一种。非关系型数据库可包括基于区块链的分布式数据库等，不限于此。本申请所提供的各实施例中所涉及的处理器可为通用处理器、中央处理器、图形处理器、数字信号处理器、可编程逻辑器、基于量子计算的数据处理逻辑器等，不限于此。
以上实施例的各技术特征可以进行任意的组合，为使描述简洁，未对上述实施例中的各个技术特征所有可能的组合都进行描述，然而，只要这些技术特征的组合不存在矛盾，都应当认为是本说明书记载的范围。
以上所述实施例仅表达了本申请的几种实施方式，其描述较为具体和详细，但并不能因此而理解为对本申请专利范围的限制。应当指出的是，对于本领域的普通技术人员来说，在不脱离本申请构思的前提下，还可以做出若干变形和改进，这些都属于本申请的保护范围。因此，本申请的保护范围应以所附权利要求为准。

Claims (19)

  1. 一种消息传输方法，所述方法包括：
    接收会话管理功能实体发送的初始PFCP协议消息，并对所述初始PFCP协议消息进行识别，以确定所述初始PFCP协议消息是否为目标消息类型；
    在所述初始PFCP协议消息为所述目标消息类型的情况下，确定所述会话管理功能实体的网元融合方式与用户面功能实体的网元融合方式是否相互匹配，所述网元融合方式用于指示融合SGW和PGW的网元功能的方式；以及
    在所述会话管理功能实体的网元融合方式与所述用户面功能实体的网元融合方式不匹配的情况下，对所述初始PFCP协议消息进行重构，得到目标PFCP协议消息，并将所述目标PFCP协议消息发送至所述用户面功能实体。
  2. 根据权利要求1所述的方法，其中，所述对所述初始PFCP协议消息进行重构，得到目标PFCP协议消息，包括：
    根据所述会话管理功能实体的网元融合方式和所述用户面功能实体的网元融合方式，确定重构转发规则；以及
    根据所述重构转发规则对所述初始PFCP协议消息进行重构，得到目标PFCP协议消息。
  3. 根据权利要求2所述的方法，其中，所述根据所述会话管理功能实体的网元融合方式和所述用户面功能实体的网元融合方式，确定重构转发规则，包括：
    在所述会话管理功能实体的网元融合方式为将所述SGW的功能和所述PGW的功能逻辑分设的情况下，将第一转发规则作为所述重构转发规则，所述第一转发规则包括将来源于第一接口的数据从第二接口输出。
  4. 根据权利要求3所述的方法，其中，所述初始PFCP协议消息包括第一参数组和第二参数组，所述第一参数组与所述SGW和所述PGW中的一个对应，所述第二参数组与所述SGW和所述PGW中的另一个对应；所述根据所述重构转发规则对所述初始PFCP协议消息进行重构，得到目标PFCP协议消息，包括：
    对所述第一参数组中的第一PDR数据和第一FAR数据进行删除处理；
    根据所述第一转发规则，利用所述第一接口的接口名称标识所述第二参数组中的第二PDR数据；以及
    将标识后的所述第二PDR数据、所述第二参数组中的第二FAR数据以及所述第二参数组中的其他参数绑定至新建PFCP协议消息中，得到所述目标PFCP协议消息；其中，所述第二参数组中的第二FAR数据包括所述第二接口的接口名称标识。
  5. 根据权利要求4所述的方法，其中，
    若所述初始PFCP协议消息为上行数据，则所述第一接口为S1-U接口，所述第二接口为SGI接口；
    若所述初始PFCP协议消息为下行数据，则所述第一接口为SGI接口，所述第二接口为S1-U接口。
  6. 根据权利要求2所述的方法，其中，所述根据所述会话管理功能实体的网元融合方式和所述用户面功能实体的网元融合方式，确定重构转发规则，包括：
    在所述会话管理功能实体的网元融合方式为将所述SGW的功能和所述PGW的功能逻辑合设的情况下，将第二转发规则作为所述重构转发规则，所述第二转发规则包括将来源于第一接口的数据转发至中间接口，并将来源于所述中间接口的数据从第二接口输出。
  7. 根据权利要求6所述的方法，其中，所述初始PFCP协议消息包括第三参数组，所述第三参数组包括第三PDR数据和第三FAR数据；所述根据所述重构转发规则对所述初始PFCP协议消息进行重构，得到目标PFCP协议消息，包括：
    采用新增FAR数据的FAR标识替换所述第三PDR数据中包括的原始FAR标识，得到修改后的第三PDR数据，并根据所述修改后的第三PDR数据和所述新增FAR数据得到第四参数组；其中，所述修改后的第三PDR数据包括所述第一接口的接口名称标识，所述新增FAR数据包括所述中间接口的接口名称；
    采用所述中间接口的接口名称替换所述第三PDR数据中包括的第一接口的接口名称，得到替换后的第三PDR数据，并根据所述替换后的第三PDR数据和所述第三FAR数据得到第五参数组；其中，所述第三FAR数据包括所述第二接口的接口名称；以及
    根据所述第四参数组和所述第五参数组得到所述目标PFCP协议消息。
  8. 根据权利要求7所述的方法，其中，
    若所述初始PFCP协议消息为上行数据，则所述第一接口为S1-U接口，所述中间接口为S5/S8接口，所述第二接口为SGI接口；
    若所述初始PFCP协议消息为下行数据，则所述第一接口为SGI接口，所述中间接口为S5/S8接口，所述第二接口为S1-U接口。
  9. 根据权利要求1至8任一所述的方法，其中，所述确定所述初始PFCP协议消息是否为目标消息类型，包括：
    根据所述PFCP协议消息中的多个目标接口字段确定所述初始PFCP协议消息是否为所述目标消息类型；所述多个目标接口字段至少包括源接口字段、目的接口字段以及3GPP接口类型字段。
  10. 根据权利要求1至8任一所述的方法，其中，所述目标消息类型为4G会话建立消息。
  11. 根据权利要求10所述的方法，其中，所述方法还包括：
    若所述初始PFCP协议消息不为所述4G会话建立消息，则直接将所述初始PFCP协议消息发送至所述用户面功能实体。
  12. 根据权利要求4所述的方法，其中，对所述第一参数组中的第一FDR数据和第一FAR数据进行删除处理，包括：
    删除所述第一PDR数据中的FAR ID、QER ID和URR ID，及删除第一FAR数据中的中间接口的接口名称。
  13. 根据权利要求1-12任一项所述的方法，其中，确定所述会话管理功能实体的网元融合方式与用户面功能实体的网元融合方式是否相匹配，包括：
    基于预先配置确定所述会话管理功能实体和用户面功能实体为逻辑异构还是逻辑同构，并在确定所述会话管理功能实体和所述用户面功能实体为逻辑异构的情况下，确定所述会话管理功能实体的网元融合方式与所述用户面功能实体的网元融合方式不匹配；或者
    根据接收到的初始PFCP协议消息确定会话管理功能实体的网元融合方式，根据历史接收到的用户面功能实体发送的历史PFCP协议消息确定用户面功能实体的网元融合方式，并在所述会话管理功能实体的网元融合方式与所述用户面功能实体的网元融合方式不相同时，确定所述会话管理功能实体的网元融合方式与所述用户面功能实体的网元融合方式不匹配。
  14. 一种消息传输装置，所述装置包括：
    第一确定模块，用于接收会话管理功能实体发送的初始PFCP协议消息，并对所述初始PFCP协议消息进行识别，以确定所述初始PFCP协议消息是否为目标消息类型；
    第二确定模块，用于在所述初始PFCP协议消息为所述目标消息类型的情况下，确定所述会话管理功能实体的网元融合方式与用户面功能实体的网元融合方式是否相互匹配，所述网元融合方式用于指示融合SGW和PGW的网元功能的方式；
    重构模块，用于在所述会话管理功能实体的网元融合方式与所述用户面功能实体的网元融合方式不匹配的情况下，对所述初始PFCP协议消息进行重构，得到目标PFCP协议消息，并将所述目标PFCP协议消息发送至所述用户面功能实体。
  15. 一种通信系统，所述系统包括会话管理功能实体、用户面功能实体以及执行如权利要求1至13任一项所述的方法的通信设备。
  16. 一种通信设备，包括：接收器、发送器、处理器和存储器，所述存储器存储有计算机程序；
    所述接收器，用于接收会话管理功能实体发送的初始PFCP协议消息；
    所述处理器执行所述计算机程序，用于对所述初始PFCP协议消息进行识别，以确定所述初始PFCP协议消息是否为目标消息类型；在所述初始PFCP协议消息为所述目标消息类型的情况下，确定所述会话管理功能实体的网元融合方式与用户面功能实体的网元融合方式是否相互匹配，所述网元融合方式 用于指示融合SGW和PGW的网元功能的方式；并在所述会话管理功能实体的网元融合方式与所述用户面功能实体的网元融合方式不匹配的情况下，对所述初始PFCP协议消息进行重构，得到目标PFCP协议消息；以及
    所述发送器，用于将所述目标PFCP协议消息发送至所述用户面功能实体。
  17. 一种计算机可读存储介质，其上存储有计算机程序，所述计算机程序被处理器执行时实现权利要求1至13中任一项所述的方法的步骤。
  18. 一种计算机程序产品，包括计算机程序，该计算机程序被处理器执行时实现权利要求1至13中任一项所述的方法的步骤。
  19. 一种芯片，所述芯片包括处理器，所述处理器被配置为从存储器中调用并运行计算机程序，以执行如权利要求1至13中任一项所述方法的步骤。
PCT/CN2023/138762 2023-06-20 2023-12-14 消息传输方法、装置、系统、设备和存储介质 Ceased WO2024259918A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN202310735736.2 2023-06-20
CN202310735736.2A CN116709217B (zh) 2023-06-20 2023-06-20 消息传输方法、装置、系统、设备和存储介质

Publications (1)

Publication Number Publication Date
WO2024259918A1 true WO2024259918A1 (zh) 2024-12-26

Family

ID=87835541

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2023/138762 Ceased WO2024259918A1 (zh) 2023-06-20 2023-12-14 消息传输方法、装置、系统、设备和存储介质

Country Status (2)

Country Link
CN (1) CN116709217B (zh)
WO (1) WO2024259918A1 (zh)

Families Citing this family (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN116709217B (zh) * 2023-06-20 2026-03-10 中国电信股份有限公司 消息传输方法、装置、系统、设备和存储介质

Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN109167670A (zh) * 2018-07-09 2019-01-08 中兴通讯股份有限公司 Pfcp连接处理方法、装置、网元、系统及存储介质
WO2020011384A1 (en) * 2018-07-12 2020-01-16 Telefonaktiebolaget Lm Ericsson (Publ) Enabling functionality at a user plane function, upf, by a session management function, smf, in a telecommunication network
CN111294839A (zh) * 2020-02-20 2020-06-16 广州爱浦路网络技术有限公司 一种pfcp会话处理方法及装置
CN115243396A (zh) * 2022-07-27 2022-10-25 联想(北京)有限公司 一种信息处理方法、会话管理功能网元和用户面功能网元
CN116112994A (zh) * 2021-11-11 2023-05-12 中国电信股份有限公司 用户面网元选择的方法、装置、系统和相关网元
CN116709217A (zh) * 2023-06-20 2023-09-05 中国电信股份有限公司 消息传输方法、装置、系统、设备和存储介质

Family Cites Families (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN114599065A (zh) * 2020-12-03 2022-06-07 中兴通讯股份有限公司 网络切换方法、融合网元、通信系统和存储介质
KR20230022058A (ko) * 2021-08-06 2023-02-14 삼성전자주식회사 SMF(session management function)를 변경하는 방법 및 장치
CN115529294B (zh) * 2022-04-27 2024-04-09 中国移动通信集团设计院有限公司 业务处理方法、装置、设备及存储介质
CN115529342B (zh) * 2022-04-27 2025-08-19 中国移动通信集团设计院有限公司 业务访问处理方法、装置、设备及存储介质

Patent Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN109167670A (zh) * 2018-07-09 2019-01-08 中兴通讯股份有限公司 Pfcp连接处理方法、装置、网元、系统及存储介质
WO2020011384A1 (en) * 2018-07-12 2020-01-16 Telefonaktiebolaget Lm Ericsson (Publ) Enabling functionality at a user plane function, upf, by a session management function, smf, in a telecommunication network
CN111294839A (zh) * 2020-02-20 2020-06-16 广州爱浦路网络技术有限公司 一种pfcp会话处理方法及装置
CN116112994A (zh) * 2021-11-11 2023-05-12 中国电信股份有限公司 用户面网元选择的方法、装置、系统和相关网元
CN115243396A (zh) * 2022-07-27 2022-10-25 联想(北京)有限公司 一种信息处理方法、会话管理功能网元和用户面功能网元
CN116709217A (zh) * 2023-06-20 2023-09-05 中国电信股份有限公司 消息传输方法、装置、系统、设备和存储介质

Also Published As

Publication number Publication date
CN116709217A (zh) 2023-09-05
CN116709217B (zh) 2026-03-10

Similar Documents

Publication Publication Date Title
WO2019080235A1 (zh) 基于以太坊的区块链系统和交易数据处理方法
CN114238703B (zh) 事件流程编排方法、装置及应用
WO2020019943A1 (zh) 发送数据的方法和装置，以及接收数据的方法和装置
CN118555252B (zh) 一种路由方法、系统和电子设备及存储介质
CN111382201A (zh) 异构数据库同步方法、装置、计算机设备及存储介质
US20230327965A1 (en) Computer network architecture mapping using metadata
CN111447143A (zh) 业务服务数据传输方法、装置、计算机设备和存储介质
CN112035216A (zh) 一种Kubernetes集群网络和OpenStack网络的打通方法
EP3637690B1 (en) Service configuration-driven flow table method and device
CN118921709A (zh) 数据传输方法、系统、装置、通信设备、存储介质和计算机程序产品
CN111651498A (zh) 一种区块链数据的高效检索方法及装置
WO2024259918A1 (zh) 消息传输方法、装置、系统、设备和存储介质
WO2025158261A1 (zh) 请求处理方法以及装置、任务执行方法以及装置
CN116506902B (zh) 信令处理方法、装置、信令互通网关和存储介质
CN116233241B (zh) 一种微服务应用的迁移方法及装置
WO2023040678A1 (zh) 信息传输方法、装置、电子设备、芯片、存储介质、程序及程序产品
CN110099068A (zh) 基于区块链的开放平台间交互的方法、装置及设备
CN116887202B (zh) 消息转发方法、装置、通信设备、介质和程序产品
CN118400315A (zh) 软件定义广域网分布式端到端策略选路方法、装置及设备
CN118331628A (zh) 数据生成方法、装置和计算机设备
CN120034426A (zh) 网络配置数据的分发方法、装置、计算机设备、存储介质
CN105992180B (zh) 一种短信发送方法和装置
WO2023071777A1 (zh) 一种网络集成控制方法及装置
CN115510112A (zh) 一种数据上报的方法、装置、存储介质及电子设备
WO2024045179A1 (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: 23942184

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE