WO2024027299A1 - 消息路由方法和装置 - Google Patents

消息路由方法和装置 Download PDF

Info

Publication number
WO2024027299A1
WO2024027299A1 PCT/CN2023/096497 CN2023096497W WO2024027299A1 WO 2024027299 A1 WO2024027299 A1 WO 2024027299A1 CN 2023096497 W CN2023096497 W CN 2023096497W WO 2024027299 A1 WO2024027299 A1 WO 2024027299A1
Authority
WO
WIPO (PCT)
Prior art keywords
message
network element
seid
function network
session
Prior art date
Application number
PCT/CN2023/096497
Other languages
English (en)
French (fr)
Inventor
姚琦
宗在峰
张继东
Original Assignee
华为技术有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 华为技术有限公司 filed Critical 华为技术有限公司
Publication of WO2024027299A1 publication Critical patent/WO2024027299A1/zh

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W40/00—Communication routing or communication path finding
    • H04W40/24—Connectivity information management, e.g. connectivity discovery or connectivity update
    • H04W40/246—Connectivity information discovery
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/12—Discovery or management of network topologies
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W40/00—Communication routing or communication path finding
    • H04W40/24—Connectivity information management, e.g. connectivity discovery or connectivity update
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W40/00—Communication routing or communication path finding
    • H04W40/24—Connectivity information management, e.g. connectivity discovery or connectivity update
    • H04W40/248—Connectivity information update
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/10—Connection setup
    • H04W76/11—Allocation or use of connection identifiers

Definitions

  • the embodiments of the present application relate to the field of communications, and more specifically, to a message routing method and device.
  • the 3rd generation partnership project (3Gpp) has proposed a network service-oriented architecture in order to improve the reliability and flexibility of the network.
  • the session management function not only needs to support service-oriented interfaces (for example, SMF and access and mobility management function network elements) Management function (AMF), policy control function (PCF), etc. are service-oriented interfaces).
  • SMF also needs to support non-service-oriented interfaces (for example, SMF and user plane function , the N4 interface between UPF) is a non-service interface).
  • SMF needs to preserve the context information of the user or the context information associated with the transport layer.
  • UPF may need to re-establish a session with the new SMF, transmit context information, etc.
  • the service-oriented function of SMF is not complete, resulting in a coupling relationship with UPF during SMF failure recovery or SMF expansion/reduction, which is not flexible enough and cannot give full play to the advantages of the service-oriented architecture.
  • LLOF can use a service-oriented interface to transmit messages with SMF, and LLOF can use a non-service-oriented interface with UPF. This enables SMF to be completely service-oriented, and communication between SMF and UPF through LLOF can also be realized.
  • the first aspect provides a communication method, which can be executed by the link load orchestration function network element, or can also be executed by the component (such as a chip or circuit) of the link load orchestration function network element, and no further modifications are made to this. limited.
  • the method includes: the link load orchestration function network element receives a first message from the session management function network element, the first message carries the user plane function network element information and the session message, and the first message is used to request forwarding the session message, wherein , the first message is transmitted through the service-oriented interface of the link load orchestration function network element; the link load orchestration function network element responds to the user plane The information of the functional network element determines the target user plane functional network element; the link load orchestration functional network element sends session messages to the target user plane functional network element through the non-service interface.
  • the session message may be a Packet Forwarding Control Protocol PFCP session message.
  • the session message includes an information element IE
  • the IE includes a control plane fully qualified session endpoint identifier CP F-SEID corresponding to the session management function network element.
  • the method before the link load orchestration function network element receives the first message from the session management function network element, the method further includes: the link load orchestration function network element receives the second message from the session management function network element. message, the second message is used to request to obtain the CP F-SEID corresponding to the session management function network element; the link load orchestration function network element allocates the corresponding CP F-SEID to the session management function network element according to the second message; the link The path load orchestration function network element sends the CP F-SEID to the session management function network element.
  • SMF when LLOF supports parsing session message headers but does not support parsing IE of session messages, SMF can obtain the corresponding session endpoint identifier CP F-SEID from LLOF in advance, and encapsulate it in the session message. Sent to LLOF in IE so that LLOF can forward the session message to the target UPF.
  • the CP F-SEID may be assigned by the session management function network element.
  • SMF can also allocate CP F-SEID by itself, thereby making it compatible with existing technology, that is, making small changes to the existing protocol, making it easier to implement and reduce costs.
  • SMF does not need to request CP F-SEID from LLOF, which can reduce the complexity of the process.
  • the link load orchestration function network element allocates the corresponding control plane fully qualified session endpoint identifier CP F-SEID to the session management function network element according to the first message.
  • the link load orchestration function network element The CP F-SEID is encapsulated in the information element IE of the session message.
  • LLOF provides the service of allocating CP F-SEID.
  • the binding relationship between CP F-SEID and SMF can be dynamically updated, that is, if the SMF fails, LLOF can reselect a new SMF. , there is no need to re-allocate the CP F-SEID, just bind the CP F-SEID to the new SMF, which can reduce communication delay and ensure user business experience.
  • the method also includes: the link load orchestration function network element saves the mapping relationship between the session management function network element and the CP F-SEID.
  • LLOF can save the mapping relationship, so that subsequent LLOF can route messages from UPF based on the mapping relationship, and communication between SMF and UPF can be realized.
  • the method also includes: the link load orchestration function network element encapsulates the session message, and the link load orchestration function network element sends the session message to the target user plane function network element, including: the link load orchestration function network element The network element sends the encapsulated session message to the target user plane function network element.
  • the link load orchestration function network element can encapsulate session messages according to the format of the N4 interface protocol stack.
  • LLOF can encapsulate session messages, so that LLOF and UPF follow the N4 interface protocol without making any changes to UPF, which facilitates implementation and reduces costs.
  • the method further includes: the link load orchestration function network element receives a third message from the target user plane function network element, where the third message carries the session endpoint identifier SEID, the user plane fully qualified session endpoint Identifier UP F-SEID.
  • the third message also carries indication information, where the indication information is used to respond to the session message.
  • the link load orchestration function network element determines the CP F-SEID based on the SEID; the link load orchestration function network element determines the CP F-SEID based on the CP F-SEID and the session
  • the mapping relationship of the management function network element is sent to the session management function network element, and the fourth message carries UP F-SEID and the indication information.
  • the header of the third message includes SEID, and the IE of the third message includes UP F-SEID.
  • the link load orchestration function network element receives the third message from the target user plane function network element.
  • the IE of the third message includes UP F-SEID and CP F-SEID.
  • the third message also carries Instruction information, where the instruction information is used to respond to the session message.
  • the link load orchestration function network element sends a fourth message to the session management function network element according to the mapping relationship between the CP F-SEID and the session management function network element.
  • the fourth message carries The UP F-SEID and indication information.
  • the link load orchestration function network element receives a third message from the target user plane function network element, the header of the third message includes CP F-SEID, and the third message carries indication information, where the indication The information is used to respond to the session message.
  • the link load orchestration function network element sends a fourth message to the session management function network element according to the mapping relationship between the CP F-SEID and the session management function network element.
  • the fourth message carries the UP F-SEID. and instructions.
  • LLOF can route messages from UPF through mapping relationships, that is, determine the target SMF, thereby realizing communication between SMF and UPF and avoiding signaling caused by LLOF sending messages to the wrong SMF. consumption.
  • a second aspect provides a message routing device, which is configured to perform the method in any possible implementation manner of the first aspect.
  • the device may include units and/or modules for performing the method in any possible implementation of the first aspect, such as a transceiver unit and/or a processing unit.
  • the device is a link load orchestration function network element.
  • the communication unit may be a transceiver, or an input/output interface; the processing unit may be at least one processor.
  • the transceiver may be a transceiver circuit.
  • the input/output interface may be an input/output circuit.
  • the device is a chip, chip system or circuit for a link load orchestration function network element.
  • the communication unit may be an input/output interface, interface circuit, output circuit, input circuit, pin or related circuit on the chip, chip system or circuit, etc.
  • the processing unit may be at least one processor, processing circuit or logic circuit, etc.
  • a message routing device in a third aspect, includes: at least one processor for executing computer programs or instructions stored in a memory to execute any of the possible implementations of any of the above-mentioned first aspects. Methods.
  • the device further includes a memory for storing computer programs or instructions.
  • the device further includes a communication interface, through which the processor reads the computer program or instructions stored in the memory.
  • the device is a link load orchestration function network element.
  • the device is a chip, chip system or circuit for a link load orchestration function network element.
  • this application provides a processor, including: an input circuit, an output circuit and a processing circuit.
  • the processing circuit is configured to receive a signal through the input circuit and transmit a signal through the output circuit, so that the processor executes the method in any possible implementation manner of any aspect in the first aspect.
  • the above-mentioned processor can be one or more chips
  • the input circuit can be an input pin
  • the output circuit can be an output pin
  • the processing circuit can be a transistor, a gate circuit, a flip-flop and various logic circuits, etc.
  • the input signal received by the input circuit may be received and input by, for example, but not limited to, a transceiver.
  • the signal output by the output circuit may be, for example, but not limited to, output to a transmitter and transmitted by the transmitter, and the input circuit and the output A circuit may be the same circuit that functions as an input circuit and an output circuit at different times.
  • the embodiments of this application do not limit the specific implementation methods of the processor and various circuits.
  • processor output, reception, input and other operations can be understood as processor output, reception, input and other operations.
  • transmitting and receiving operations performed by the radio frequency circuit and the antenna, which is not limited in this application.
  • a processing device including a processor and a memory.
  • the processor is used to read instructions stored in the memory, and can receive signals through the transceiver and transmit signals through the transmitter to execute the method in any possible implementation manner of any aspect in the first aspect.
  • processors there are one or more processors and one or more memories.
  • the memory may be integrated with the processor, or the memory may be provided separately from the processor.
  • the memory can be a non-transitory memory, such as a read-only memory (ROM), which can be integrated on the same chip as the processor, or can be set in different On the chip, the embodiment of the present application does not limit the type of memory and the arrangement of the memory and the processor.
  • ROM read-only memory
  • sending instruction information may be a process of outputting instruction information from the processor
  • receiving capability information may be a process of the processor receiving input capability information.
  • the data output by the processor can be output to the transmitter, and the input data received by the processor can be from the transceiver.
  • the transmitter and the transceiver can be collectively referred to as the transceiver.
  • the processing device in the above fifth aspect may be one or more chips.
  • the processor in the processing device can be implemented by hardware or software.
  • the processor can be a logic circuit, an integrated circuit, etc.;
  • the processor can be a general processor, which is implemented by reading software codes stored in a memory, and the memory can Integrated in the processor, it can be located outside the processor and exist independently.
  • a sixth aspect provides a computer-readable storage medium that stores program code for device execution, where the program code includes a method for executing any of the possible implementation methods of the first aspect.
  • a seventh aspect provides a computer program product containing instructions, which when the computer program product is run on a computer, causes the computer to execute the method in any of the possible implementations of the first aspect.
  • An eighth aspect provides a chip system, including a processor for calling and running a computer program from a memory, so that a device installed with the chip system executes the method in each implementation of any of the above-mentioned first aspects.
  • a communication system which includes a link load orchestration function network element.
  • the link load orchestration function network element is used to perform any possible implementation method in any of the above first aspects.
  • the communication system also includes a session management functional network element and a user plane functional network element.
  • Figure 1 is a schematic diagram of the 5G network service architecture.
  • Figure 2 is a schematic diagram of a 5G network service architecture proposed by this application.
  • Figure 3 is a schematic diagram of the protocol stack of the N4 interface.
  • Figure 4 is a schematic diagram of the format of a PFCP session message.
  • Figure 5 is a schematic diagram of the format of a PFCP session message header.
  • Figure 6 is a schematic diagram of a format of PFCP session message information elements.
  • Figure 7 is a schematic flow chart of a message routing method 700 provided by this application.
  • Figure 8 is a schematic flow chart of another message routing method 800 provided by this application.
  • Figure 9 is a schematic block diagram of a message routing device 100 provided by this application.
  • Figure 10 is a schematic block diagram of another message routing device 200 provided by this application.
  • the wireless communication systems mentioned in this application include but are not limited to: global system of mobile communication (GSM) system, long term evolution (long term evolution, LTE) frequency division duplex (FDD) system, LTE Time division duplex (TDD), LTE system, advanced long-term evolution (LTE-Advanced, LTE-A) system, next-generation communication system (for example, 6G communication system), convergence system of multiple access systems, or evolving systems.
  • GSM global system of mobile communication
  • LTE long term evolution
  • FDD frequency division duplex
  • TDD LTE Time division duplex
  • LTE system LTE system
  • LTE-Advanced LTE-Advanced
  • LTE-A advanced long-term evolution
  • next-generation communication system for example, 6G communication system
  • convergence system of multiple access systems or evolving systems.
  • the technical solution provided by this application can also be applied to machine type communication (MTC), long term evolution-machine (LTE-M), and device to device (D2D) networks.
  • M2M machine to machine
  • IoT Internet of things
  • the IoT network may include, for example, the Internet of Vehicles.
  • the communication methods in the Internet of Vehicles system are collectively called vehicle to other devices (vehicle to X, V2X, X can represent anything).
  • the V2X can include: vehicle to vehicle (vehicle to vehicle, V2V) communication.
  • FIG. 1 shows a schematic diagram of a 5G system (the 5th generation system, 5GS) network service architecture.
  • the network architecture may specifically include the following network elements:
  • User equipment can be called terminal equipment, access terminal, user unit, user station, mobile station, mobile station, remote station, remote terminal, mobile device, user terminal, terminal, wireless communication equipment , user agent or user device.
  • the terminal device may be a device that provides voice/data to users, for example, a handheld device with wireless connection function, a vehicle-mounted device, etc.
  • some examples of terminals are: mobile phones, tablets, laptops, PDAs, mobile internet devices (MID), virtual reality (VR) devices, augmented reality, AR) equipment, wireless terminals in industrial control, wireless terminals in self-driving, wireless terminals in remote medical surgery, wireless terminals in smart grid, Wireless terminals in transportation safety, wireless terminals in smart city, wireless terminals in smart home, cellular phones, cordless phones, session initiation protocol (SIP) phones , wireless local loop (WLL) station, personal digital assistant (PDA), handheld device with wireless communication capabilities, computing device or other processing device connected to a wireless modem, terminal in 5G network Equipment or terminal equipment in a future evolved public land mobile communication network (public land mobile network, PLMN), etc., the embodiments of the present application are not limited to this.
  • the terminal device may also be a wearable device.
  • Wearable devices can also be called wearable smart devices. It is a general term for applying wearable technology to intelligently design daily wear and develop wearable devices, such as glasses, gloves, watches, clothing and shoes, etc.
  • a wearable device is a portable device that is worn directly on the body or integrated into the user's clothing or accessories. Wearable devices are not just hardware devices; Powerful functions are achieved through software support, data interaction, and cloud interaction.
  • wearable smart devices include full-featured, large-sized devices that can achieve complete or partial functions without relying on smartphones, such as smart watches or smart glasses, and those that only focus on a certain type of application function and need to cooperate with other devices such as smartphones.
  • the terminal device may also be a terminal device in the IoT system.
  • IoT is an important part of the future development of information technology. Its main technical feature is to connect objects to the network through communication technology, thereby realizing human-machine Interconnection, the intelligent network of interconnection of things.
  • terminal equipment and access network equipment can communicate with each other using certain air interface technology (such as NR or LTE technology, etc.).
  • Terminal devices can also communicate with each other using some air interface technology (such as NR or LTE technology, etc.).
  • the device used to implement the functions of the terminal device may be a terminal device, or may be a device capable of supporting the terminal device to implement the function, such as a chip system or a chip, and the device may be installed in the terminal device.
  • the chip system may be composed of chips, or may include chips and other discrete devices.
  • Radio access network (R)AN) equipment It can provide authorized users in a specific area with the function of accessing the communication network. Specifically, it can include the 3rd generation partnership program (3rd generation partnership) Wireless network devices in project, 3GPP) networks may also include access points in non-3GPP (non-3GPP) networks.
  • 3rd generation partnership program 3rd generation partnership
  • 3GPP access technologies for example, wireless access technologies used in third generation (3G), fourth generation (4G) or 5G systems
  • non-3GPP non- 3GPP (non-3GPP) access technology
  • 3GPP access technology refers to access technology that complies with 3GPP standard specifications.
  • the access network equipment in the 5G system is called next generation Node Base station (gNB) or RAN equipment.
  • Non-3GPP access technologies can include air interface technology represented by access point (AP) in wireless fidelity (WiFi), global interoperability for microwave access (WiMAX), code Code division multiple access (CDMA), etc.
  • AP access point
  • WiFi wireless fidelity
  • WiMAX global interoperability for microwave access
  • CDMA code Code division multiple access
  • AN equipment can allow interconnection and interworking between terminal equipment and the 3GPP core network using non-3GPP technologies.
  • RAN equipment can be responsible for functions such as wireless resource management, quality of service (QoS) management, data compression and encryption on the air interface side.
  • AN equipment provides access services to terminal equipment, thereby completing the forwarding of control signals and user data between the terminal equipment and the core network.
  • RAN equipment may include, for example, but is not limited to: macro base station, micro base station (also called small station), radio network controller (RNC), Node B (Node B, NB), base station controller (base station controller) , BSC), base transceiver station (BTS), home base station (for example, home evolved NodeB, or home Node B, HNB), baseband unit (baseband unit, BBU), AP in WiFi system, wireless relay Node, wireless backhaul node, transmission point (TP) or transmission and reception point (TRP), etc., can also be a gNB or transmission point (TRP or TP) in the 5G (such as NR) system , one or a group (including multiple antenna panels) antenna panels of a base station in a 5G system, or it can also be a network node that constitutes a gNB or transmission point, such as a distributed unit (DU), or next-generation communications Base stations in 6G systems, etc.
  • RNC radio network controller
  • Node B Node B
  • User plane function network element (user plane function, UPF): It can be used for packet routing and forwarding, or quality of service (QoS) processing of user plane (UP) data, etc. User data can be accessed to the data network (DN) through this network element. In the embodiment of this application, it can be used to implement the functions of user plane network elements.
  • UPF user plane function
  • Data network used to provide a network for transmitting data.
  • DN Data network
  • the operator's business network Internet network
  • third-party business network etc.
  • Authentication and authorization function network element selected by network slice (network slice-specific authentication and authorization function, NSSAAF): supports the use of authentication, authorization and accounting (AAA) servers for specified network slices
  • AAA authentication, authorization and accounting
  • Authentication server function supports authenticating UE for the requestor network element, providing key material to the requestor network element, and protecting the "guidance information list" of the requester network element.
  • Access and mobility management function Mainly used for mobility management and access management, etc., and can be used to implement mobility management entity (MME) functions in addition to Other functions besides session management, such as terminal mobility management, terminal registration and de-registration, terminal session access, terminal allowed slice access selection, legal interception or access authorization (or authentication) and other functions. In the embodiment of this application, it can be used to implement the functions of access and mobility management network elements.
  • MME mobility management entity
  • Session management function network element (session management function, SMF): mainly used for session management, IP address allocation and management of terminal equipment, selection and management of user plane functions, policy control, termination points of charging function interfaces or downlink data notifications wait. In the embodiment of this application, it can be used to implement the function of the session management network element.
  • SMF session management function
  • Service communication proxy responsible for message routing of service interfaces between control plane (CP) network elements.
  • control plane network elements include AMF, SMF, AUSF, PCF and other networks. Yuan.
  • Network slice admission control function It can support monitoring and controlling the number of registered users of each network slice, and support monitoring and controlling the protocol data unit (protocol data) established by each network slice. unit, PDU) session number, supports event-based network slice status notification and reports to other network elements.
  • protocol data unit protocol data
  • PDU protocol data unit
  • NSSF Network slice selection function
  • Network capability exposure function used to securely open to the outside the business and capability information (such as terminal location, network congestion status) provided by the 3GPP network function network element.
  • Network repository function This new function is used to provide registration and discovery functions, allowing each network element to discover each other and communicate through the application programming interface (API) interface. .
  • PCF Policy control function
  • Unified data management used to process user identification, access authentication rights, registration, or mobility management, etc.
  • Application function network element used to provide services, or perform application-influenced data routing, access network open function network elements, or interact with PCF network elements for business data for policy control, etc.
  • EASDF Edge application server discovery function
  • EASDF Assists the new network element EASDF discovered by the edge application server (EAS). Its main function is to process the domain name system (domain name) according to the instructions of the SMF. system, DNS) messages. For example, report DNS messages to SMF and add DNS extended mechanisms (extended mechanisms for DNS, EDNS) client subnet option (client subnet option) in DNS query (query) (DNS extended mechanism client subnet option, which can also be referred to as " ECS option”), forward DNS query to DNS server, forward DNS response (response) to UE, etc.
  • DNS domain name system
  • AMF and SMF support both service-oriented interfaces and non-service-oriented interfaces.
  • the "service-oriented interface” can be understood as: the externally exposed interface of the functional body implemented through the service registration and service discovery of the service-oriented architecture. This interface is only for a single functional body, and the related functional bodies are exposed to the outside through the service-oriented interface. It interacts with other functional bodies, and other functional bodies interact with this functional body through the interface exposed by this functional body. In other words, this mechanism provides a "many-to-one" access mechanism, and due to the use of service registration and service discovery, each other can access each other without knowing each other's address.
  • non-service interface can be understood as a traditional interface based on a reference point, that is, an interface for mutual access between two network elements with different functions. On non-serviced interfaces, there is a binding relationship between the user context and the physical interface.
  • the SMF needs to send the SMF set identification (ID) and/or the backup SMF information corresponding to the UE to other surrounding networks that have relationships with it. yuan (e.g., sent to UPF).
  • ID SMF set identification
  • yuan e.g., sent to UPF.
  • the network element can reselect an SMF from the SMF set based on the SMF set ID to continue to provide services to the UE, or the network element can also reselect the backup SMF based on the backup SMF information. In order to continue to provide services to the UE.
  • the context information may not be passed to the newly selected SMF due to the failure of the old SMF.
  • UPF may need to re-establish a session with the new SMF and transmit context information, which increases the communication delay, affects the user's business experience, etc.
  • the N26 interface is the interface between the 4G core network (i.e., mobility management entity (MME)) and the 5G core network (i.e., AMF), and is used for handover or redirection operations between 4G and 5G. . If the AMF in the 5G core network supports the N26 interface, the RAN can fall back through handover or redirection to use voice services.
  • MME mobility management entity
  • AMF 5G core network
  • this application improves the 5G network service architecture in Figure 1 and obtains a new service architecture as shown in Figure 2.
  • a new functional network element is added in Figure 2.
  • the newly added functional network element may be called a "link load orchestration function (LLOF)".
  • LLOF link load orchestration function
  • the N4 interface is between UPF and the service interface between SMF and LLOF. Therefore, in this application, the non-serverized N4 interface between SMF and UPF can be shielded, so that the service-oriented function of SMF can be completely realized.
  • there is an N2 interface between LLOF and RAN so that the non-service N2 interface between AMF and RAN can be shielded.
  • there is an N26 interface between LLOF and MME so that the non-service N26 interface between AMF and MME can be shielded.
  • shielding in this application can also be understood as, for example, there may still be an N4 interface between SMF and UPF, but SMF may not use the N4 interface to communicate with UPF.
  • N2 interface still exists between the AMF and the RAN, but the AMF does not need to use the N2 interface to communicate with the RAN.
  • N26 interface still exists between the AMF and the MME, but the AMF does not need to use the N26 interface to communicate with the MME.
  • this application proposes a new service-oriented architecture, which adds LLOF.
  • the LLOF can terminate the non-service-oriented interface, for example, it can terminate N2 interface, N4 interface and N26 interface.
  • the interfaces between UPF, RAN, MME and LLOF are still based on existing non-service-oriented interfaces.
  • Service-oriented interfaces can be used between LLOF and control plane network elements (for example, AMF, SMF, etc.), so that AMF and SMF no longer need to support non-service-oriented interfaces, which is conducive to decoupling between AMF, SMF and other network elements. It can be more easily expanded and reduced, and the implementation of AMF and SMF is simplified.
  • LLOF can provide one or more of the following services:
  • LLOF provides a service interface Nllof, through which control plane network elements (for example, AMF, SMF, etc.) can request LLOF to provide services.
  • control plane network elements for example, AMF, SMF, etc.
  • SMF can send a hypertext transfer protocol (HTTP) request message to LLOF, requesting to call a certain service of the LLOF.
  • HTTP hypertext transfer protocol
  • LLOF is responsible for the processing of network element-level NG interface application protocol (NGAP) messages of the N2 interface.
  • NGAP network element-level NG interface application protocol
  • the network element-level NGAP message is a message for network element configuration
  • the NG interface is the interface between the RAN and the core network.
  • NG interface messages for example, can be NG setup, RAN configuration update, AMF configuration update, etc.
  • LLOF terminates the processing of packet forwarding control protocol (PFCP) node-level messages (for example, node-level messages include PFCP association-related messages) on the N4 interface, and is responsible for the reliable retransmission of PFCP session messages, Responsible for the encapsulation or decapsulation of the Internet protocol (IP) and user datagram protocol (UDP) headers of PFCP session messages.
  • PFCP packet forwarding control protocol
  • IP Internet protocol
  • UDP user datagram protocol
  • LLOF is responsible for the reliable retransmission of GPRS tunneling protocol-control plane (GTP-C) messages and the encapsulation and decapsulation of the IP and UDP headers of GTP-C messages.
  • GTP-C GPRS tunneling protocol-control plane
  • LLOF is responsible for the routing of user-level N2, N4, and GTP-C messages.
  • LLOF is responsible for message routing of service interfaces (for example, the interface between SMF and AMF, the interface between AMF and UDM).
  • LLOF is responsible for allocating routing identifiers.
  • the routing identifier is used to determine the control plane network element that processes the message.
  • the routing identifier can be the NGAP UE ID of the N2 interface or the session endpoint identifier of the N26 interface. , SEID), tunneling endpoint identifier (tunnelingendpoint identifier, TEID), SEID of the N4 interface, etc.
  • LLOF is responsible for maintaining the binding relationship, where the binding relationship can refer to the corresponding relationship between the UE context and the NF instance.
  • LLOF is responsible for the health status detection and disaster recovery processing of network elements (such as AMF, SMF, etc.).
  • LLOF is responsible for the expansion and contraction of network elements (for example, AMF, SMF, etc.).
  • LLOF is responsible for load sharing and overload control of network elements (such as AMF, SMF, etc.).
  • the newly added functional network element supports one or more of the above-mentioned services, but its specific name does not need to be limited. In the following description, only the name of the network element is used. Take LLOF as an example to describe.
  • FIG 2 is only an example of the network architecture that can be applied to the embodiments of the present application.
  • the network architecture applicable to the embodiments of the present application is not limited to this. Any network architecture that can realize the functions of each of the above network elements All network architectures are applicable to the embodiments of this application.
  • the N1 interface is the reference point between the terminal device and the AMF
  • the N2 interface is the interface between the RAN and the AMF network element and is used for wireless parameters and non-access stratum signaling (non-accessstratum, NAS).
  • the N3 interface is the interface between the RAN and UPF network elements, used to transmit user plane data, etc.
  • the N4 interface is the interface between the SMF network element and the UPF network element, used to transmit business policies, N3 connection tunnel identification information, data cache indication information, and downlink data notification messages and other information.
  • the N4 interface is the reference point between SMF and UPF and is used to transmit information such as tunnel identification information of the N3 connection, data cache indication information, and downlink data notification messages;
  • the N6 interface is the reference point between UPF and DN and is used to transmit Transmit user plane data, etc.;
  • the N9 interface is the reference point of UPF.
  • functions or network elements such as AMF, SMF, and LLOF shown in Figures 1 and 2 can be understood as network elements used to implement different functions.
  • network slices can be combined on demand.
  • These network elements can be independent devices, or they can be integrated into the same device to implement different functions, or they can be network elements in hardware devices, software functions running on dedicated hardware, or platforms (for example, cloud The virtualization function instantiated on the platform), this application does not limit the specific form of the above network elements.
  • the 5G network still uses non-service-oriented interfaces on some interfaces.
  • the N4 interface that needs to transmit a large amount of business and policy information between SMF and UPF has relatively complex logic and is usually used Non-service-oriented interface of PFCP protocol.
  • the N4 interface is the interface between SMF and UPF.
  • the control plane is used to transmit node-level messages and session-level messages, using the PFCP protocol; the user plane is used to transmit messages that SMF needs to receive or send through UPF, using the user-level GPRS tunnel. Protocol (GPRS tunneling protocol for the user plane, GTP-U).
  • Figure 3 shows the protocol stack of the N4 interface. As shown in Figure 3, from top to bottom, there are PFCP layer, UDP layer, IP layer, L2 layer (ie, data link layer), and L1 layer (physical layer).
  • PFCP layer As shown in Figure 3, from top to bottom, there are PFCP layer, UDP layer, IP layer, L2 layer (ie, data link layer), and L1 layer (physical layer).
  • Figure 4 shows the format of the PFCP session message.
  • the PFCP session message can have n (an integer greater than 0) bytes, and each byte has 8 bits.
  • bytes #1 to byte #m are PFCP session message header (PFCP message header) (in this application, "PFCP session message header” is also called “PFCP session message header")
  • byte #(m+1 ) to byte #n are zero or more information elements (IE).
  • IE information elements
  • Figure 5 specifically shows a format of the PFCP session message header.
  • the PFCP session message header can have 16 bytes (n is an integer greater than 0), and each byte also has 8 bits.
  • bit #1 in the first byte is the "S" flag, which indicates whether the session endpoint identifier (SEID) field exists in the PFCP session message header. If the "S" flag is set to "0", the SEID field shall not appear in the PFCP header. If the "S” flag is set to "1", the SEID field should immediately follow the length field, in units of byte #5 to byte #12 (8 bytes in total). The value of the "S” flag shall be set to "1" in all PFCP session messages except node-related messages.
  • SEID session endpoint identifier
  • Bit #2 represents the "message priority (MP)" flag. If MP is set to “1”, bits 5 to 8 of byte #16 can be used to indicate the priority of the message.
  • Bit #3 represents the "follow open (FO)” flag. If the "FO” flag is set to "1”, another PFCP session message will be followed in the UDP or IP data packet (see TS.26.244 Sections 6.5 and 7.2.1A for details).
  • Bits #4 to #5 are spare bits. If the sending entity sets it to "0”, the receiving entity SHOULD ignore it. Bits 6 to 8 represent the PFCP version, and the current version is all 1. Should be set to decimal 1 ("001").
  • Byte #2 represents the message type
  • Byte #3 ⁇ Byte #4 is the two-byte message length
  • Byte #5 ⁇ Byte #12 is the optional SEID field, which can occupy 8 bytes
  • Bytes #13 to #15 are sequence numbers
  • the last byte #16 is a spare byte (for example, bits 5 to 8 can indicate the priority of the message).
  • Figure 6 shows one of the formats of the IE of the PFCP session message.
  • the first two bytes indicate the message type.
  • the IE type value range defined by 3GPP is 0 ⁇ 32767
  • the IE type value range specified by the supplier is: 32768 ⁇ 65535.
  • Byte #3 ⁇ Byte #4 indicate the message length.
  • the enterprise ID is an optional field.
  • it also includes: specific data of the IE group or the content field of the IE.
  • IE includes a control plane fully qualified session endpoint identifier (F-SEID).
  • F-SEID contains SEID and IP address.
  • IP address can be understood as the IP address of the network element to which the SEID is allocated.
  • the IP address can be understood as the IP address of the SMF.
  • the IP address here can be understood as the IP address of the LLOF.
  • LLOF can also get the F-SEID based on the SEID and its own IP address.
  • F-SEID can also be consistent with SEID, which is not limited in this application.
  • IE also includes creating packet detection rules (PDR), updating data detection rules, creating forwarding action rules (FAR), creating usage reporting rules (URR), and creating Qos QoS enforcement rules (QER), forwarding parameters, duplicating parameters, etc.
  • PDR packet detection rules
  • FAR forwarding action rules
  • URR usage reporting rules
  • QER Qos QoS enforcement rules
  • Figure 7 is a schematic flow chart of a message routing method 700 proposed in this application. Each step shown in Figure 7 will be described below. It should be noted that the steps indicated by dotted lines in Figure 7 are optional and will not be described again in the following text.
  • the method includes:
  • Step 701 LLOF receives a first message from SMF.
  • the first message carries UPF information and session messages.
  • the first message is used to request forwarding of the session message.
  • the first message is transmitted through the service interface of LLOF.
  • the session message may be a PFCP session message;
  • the UPF information may be UPF address information, for example, IP address or fully qualified domain name (fully qualified domain name, FQDN), etc.; or the UPF information may also be UPF Parameter information, such as data network name (DNN) and/or slice information, etc.; or, UPF information can be, for example, UP F-SEID.
  • the session message includes an information element IE, and the IE includes the CP F-SEID corresponding to the SMF.
  • the CP F-SEID may be allocated by the SMF.
  • the CP F-SEID may be obtained from LLOF by SMF.
  • the CP F-SEID can be allocated by LLOF.
  • the SMF may send a second message to the LLOF, and the second message is used to request to obtain the CP F-SEID corresponding to the SMF. After receiving the second message, LLOF assigns the CP F-SEID to the SMF and sends it to the SMF.
  • the session message does not contain the CP F-SEID corresponding to the SMF.
  • LLOF can allocate the corresponding CP F-SEID to the SMF and encapsulate the CP F-SEID in the information element IE of the session message.
  • LLOF can also save the mapping relationship between SMF and CP F-SEID.
  • mapping relationship in this article can also be expressed as “association relationship” or “correspondence relationship”.
  • a corresponds to B in this application can be understood as “there is an association between A and B”, “there is a correspondence between A and B”, and “there is a mapping relationship between A and B” .
  • “A corresponds to B” means that A can be determined based on B, but it should also be understood that determining A based on B does not mean that A is determined only based on B. A can also be determined based on B and/or other information.
  • Step 702 LLOF determines the target UPF based on the UPF information.
  • LLOF can determine the target UPF based on the address information of the UPF. In one implementation, LLOF queries the corresponding UPF based on the FQDN information of the UPF. For another example, LLOF can select the target UPF based on the parameter information of the UPF. In one implementation, LLOF selects the corresponding UPF based on the DNN and slice selection auxiliary information, thereby determining the IP address of the UPF, and so on.
  • Step 703 LLOF sends a session message to the target UPF through a non-service interface.
  • UPF receives session messages from LLOF.
  • LLOF can encapsulate the session message and send the encapsulated session message to the target UPF.
  • step 704 is also included, where the LLOF receives the third message from the UPF.
  • the third message header includes SEID
  • the IE of the third message includes UP F-SEID
  • the third message also carries indication information.
  • the third message may be a session message, for example, a PFCP session message.
  • the UP F-SEID may be assigned by the UPF based on the received session message. For example, UPF can assign corresponding UP F-SEID according to the name of the session message, and so on.
  • This indication information is used to respond to the session message. For example, if UPF accepts the IE in the session message, UPF can store the CP F-SEID and N4rule contained in the session message, and send a third message to LLOF. The third message contains "Success" message. If UPF only accepts part of N4rule, Alternatively, if the UPF does not accept all N4rules, the third message sent by the UPF to LLOF contains "error cause" (which can also be understood as "cause value”) indication information.
  • LLOF can obtain the CP F-SEID based on the SEID and its own IP address (the CP F-SEID is the CP F-SEID corresponding to the SMF in step 701); or, the SEID itself is equal to the F-SEID, and this application does not Make limitations.
  • the IE of the third message includes the UP F-SEID and CP F-SEID, and the third message also carries indication information.
  • the header of the third message includes the CP F-SEID, and the third message also carries indication information.
  • the third message may be transmitted through a non-serviced interface.
  • step 705 is also included.
  • the LLOF sends a fourth message to the SMF according to the mapping relationship between the SMF and the CP F-SEID.
  • the fourth message carries the UP F-SEID and indication information.
  • LLOF After LLOF receives the third message sent by UPF, it can determine the CP F-SEID. As mentioned above, the CP F-SEID can be included in the IE or header, and LLOF obtains the CP F-SEID by parsing the IE or header; or, LLOF determines the CP F-SEID based on the SEID, which is not limited in this application.
  • LLOF can determine the target SMF based on the mapping relationship and forward it to the target SMF. Instructions and UP F-SEID.
  • the fourth message may be transmitted through a service-based interface, for example.
  • this application proposes a new network service-oriented architecture including LLOF.
  • LLOF can use a service-oriented interface to transmit messages with SMF, and LLOF can use a non-service-oriented interface with UPF, so that SMF can be completely realized.
  • SMF Service-oriented interface
  • UPF non-service-oriented interface with UPF
  • Figure 8 is a schematic flow chart of another message routing method 800 proposed in this application.
  • the session message is a PFCP message as an example for description.
  • SMF is SMF#1 as an example for description
  • UPF is UPF#1 as an example for description.
  • LLOF supports parsing and encapsulating PFCP session message headers, but does not support IE that parses and encapsulates PFCP session messages; in another possible implementation, LLOF not only supports LLOF support Parses and encapsulates PFCP session message headers, and also supports IE that parses and encapsulates PFCP session messages. The technical solution of this application is described below for this situation.
  • steps 801 to 803 can be performed.
  • step 801 SMF#1 sends request message #1 to LLOF.
  • the request message #1 is used to request to obtain the corresponding CP F-SEID.
  • LLOF receives request message #1 from SMF
  • request message #1 can be transmitted through the service interface of LLOF.
  • the request message #1 may be a request message encapsulated in HTTP format.
  • LLOF provides the service of allocating CPF-SEID to SMF.
  • the service can be defined as Nllof_Fseid_allocation. It can also be understood that in this application, LLOF has the ability to allocate CPF-SEID to SMF, or LLOF supports allocating CP F-SEID to SMF.
  • SMF#1 can call LLOF to allocate CPF-SEID services and request LLOF to allocate corresponding CP F-SEID.
  • SMF#1 can send request message #1 to LLOF, and request message #1 is used to request LLOF to obtain the CP F-SEID corresponding to SMF#1.
  • SMF#1 can first determine the target LLOF before requesting the LLOF to allocate the corresponding CPF-SEID. In other words, SMF can determine to which LLOF to send request message #1. In one possible implementation, SMF can determine the target LLOF based on configuration information or domain name system (DNS) query. In another possible implementation, the SMF can first select the UPF, and the SMF determines the target LLOF based on the selected UPF. For example, SMF determines the UPF based on information such as data network name (DNN) and/or network slice (e.g., single network slice selection assistance information (S-NSSAI)).
  • DNN data network name
  • S-NSSAI single network slice selection assistance information
  • SMF can determine the target LLOF based on the IP version supported by the selected UPF. , making the selected LLOF compatible with the IP version supported by UPF.
  • step 802 LLOF allocates CP F-SEID#1 and binds it to SMF#1.
  • LLOF after LLOF receives request message #1, it can trigger LLOF to allocate the service of the corresponding CP F-SEID.
  • the correspondence between the SMF and the CP F-SEID can be saved.
  • the correspondence between SMF and CP F-SEID can be saved in advance on LLOF.
  • the corresponding relationship can be configured on the LLOF at the factory.
  • the corresponding relationship may be obtained by LLOF from other network elements, etc., without limitation.
  • LLOF can store the corresponding relationship between one or more SMFs and CP F-SEID.
  • the corresponding relationship can be in the form of a table, as shown in Table 1 below.
  • SMF#1 corresponds to F-SEID#1
  • SMF#2 corresponds to F-SEID#2
  • SMF#3 corresponds to F-SEID#3.
  • LLOF not only provides the service of allocating CPF-SEID
  • LLOF also supports the function of modifying the corresponding relationship between SMF and CP F-SEID. For example, assuming SMF#1 fails, LLOF can modify the correspondence between SMF#1 and CP F-SEID#1. For example, CP F-SEID#1 can be bound to SMF#2.
  • SMF session context information can also be stored on the LLOF. Therefore, if an SMF fails, LLOF can select another SMF and send session context information to the newly selected SMF so that the SMF can continue session-related operations. For example, assume that SMF#2 is bound to CPF-SEID#2. If SMF#2 fails, LLOF can select SMF#3 to continue session-related operations. At this time, LLOF can modify SMF#2 and CPF in Table 1. -The corresponding relationship of SEID#2 is changed to the correspondence between SMF#3 and CPF-SEID#2.
  • SMF can allocate CPF-SEID. If an SMF fails, a new SMF is required to re-allocate CPF-SEID to the session, and the failed SMF cannot transmit the session context information to the newly selected SMF. As a result, the newly selected SMF restarts the operations related to establishing the session, resulting in a long communication delay and seriously affecting the user's business experience.
  • the new network service architecture of LLOF proposed in this application can select a new SMF when the SMF fails to provide services for the session, reduce communication delay, and ensure user services. experience.
  • step 803 LLOF sends response message #1 to SMF#1, and the response message #1 carries CPF-SEID#1.
  • the response message #1 may be transmitted through the service-oriented interface between SMF#1 and LLOF.
  • the response message #1 can be encapsulated in HTTP format for transmission.
  • steps 801 to 803 are technical solutions for requesting LLOF to allocate CPF-SEID for SMF#1.
  • SMF can also allocate CPF-SEID itself. In this case, steps 801 to 803 may not be performed.
  • Step 804 SMF#1 sends request message #2 to LLOF.
  • Request message #2 carries UPF information and PFCP session message.
  • Request message #2 is used to request forwarding of the PFCP session message.
  • LLOF receives request message #2 from SMF#1.
  • the IE includes CP F-SEID#1 corresponding to the session management function network element.
  • different PFCP request messages can define different service names. For example, define Nllof_PFCP message_transfer for transmitting PFCP session messages (i.e., transmitting N4 messages between SMF and UPF). For another example, LLOF defines the Nllof_NGAP message_transfer service for transmitting NGAP messages (ie, N2 messages between NG-RAN and AMF), etc. For another example, define Nllof_GTP-C message_transfer to transmit GTP-C messages (ie, N26 messages between AMF and MME).
  • LLOF has the ability to forward messages for SMF, or that LLOF supports forwarding messages for SMF.
  • LLOF can forward request message #4 for SMF via Nllof_PFCP message_transfer.
  • LLOF can still define the same service name to unify various PFCP request messages.
  • LLOF uses the same service name Nllof_message_transfer to provide message forwarding services.
  • LLOF needs to further define the service parameters in the message, so that different interface message types can be distinguished through the service parameters.
  • Nllof_message_transfer 30 service parameters need to be defined.
  • parameters #1 to service parameters #10 may indicate that the service is used to transmit N4 messages between SMF and UPF.
  • parameters #11 to service parameters #20 may indicate that the service is used to transmit N2 messages between NG-RAN and AMF.
  • parameters #21 to service parameters #30 may indicate that the service is used to transmit N26 messages between the AMF and the MME.
  • request message #2 can be transmitted through the service-oriented interface of LLOF.
  • request message #2 may be a message encapsulated in HHTP format.
  • the UPF information can be used to select the target UPF.
  • the UPF information may be UPF address information and/or UPF parameter information.
  • the address information of the UPF may be, for example, the IP address information of the UPF, or information such as a fully qualified domain name (fully qualified domain name, FQDN).
  • the parameter information of UPF may be, for example, data network name (DNN) and network slice selection assistance information (NSSAI).
  • LLOF can select the target UPF based on the parameter information of the UPF and determine the IP address of the UPF.
  • the UPF information can be understood as the UP F-SEID allocated by the UPF for the session. It should be understood that in this application, the CP F-SEID and the UP F-SEID can identify a session. It can also be understood that a pair of user plane F-SEID and control plane F-SEID can identify a session.
  • the PFCP session message includes a PFCP header and one or more IEs.
  • IE can include CP F-SEID#1.
  • IE can also create one or more of packet inspection rules, Qos implementation rules, and Qos implementation rules.
  • the PFCP session message may be a PFCP session establishment message (ie, PFCP session establishment message).
  • the PFCP session message may be a PFCP session modification message (ie, PFCP sessionmodification).
  • the PFCP session message may be a PFCP session deletion request message (ie, PFCP session deletion request message), and so on.
  • the specific name of the PFCP session message is not limited. For details, please refer to Chapter 7.3 in TS29.244.
  • LLOF can provide a message forwarding service.
  • the service can be defined as Nllof_message_transfer.
  • LLOF can also provide different message forwarding services for different types of non-service messages. For example, define Nllof_PFCP message_transfer for transmitting PFCP session messages (i.e., transmitting N4 messages between SMF and UPF).
  • Nllof_NGAP message_transfer service for transmitting NGAP messages (ie, N2 messages between NG-RAN and AMF), etc.
  • Nllof_GTP-C message_transfer to transmit GTP-C messages (ie, N26 messages between AMF and MME).
  • LLOF has the ability to forward messages for SMF, or that LLOF supports forwarding messages for SMF.
  • LLOF can forward request message #2 for SMF via Nllof_PFCP message_transfer.
  • LLOF can define different services for each different type of non-serviced message (for example, LLOF defines Nllof_PFCP message_transfer service, Nllof_NGAP message_transfer service, Nllof_GTP-C message_transfer service), then SMF#1 requests LLOF to send non-serviced messages.
  • LLOF can determine the type of non-servicing message based on the name of the request message #2. For example, if the message name of request message #2 is Nllof_PFCP message_transfer, LLOF can be determined to be the N4 interface message type.
  • LLOF can be determined to be the N2 interface message type.
  • LLOF can be determined to be the N26 interface message type.
  • LLOF uses the Nllof_message_transfer service to forward request message #2 for SMF.
  • the request message #2 may carry indication information #1, and the indication information #1 is used to indicate the type of unserviced message.
  • indication information #1 is a message type field.
  • the indication information #1 may indicate that the unserviced message is an N2 interface message type.
  • the indication information #1 may indicate that the unserviced message is an N4 interface message type.
  • the indication information #1 may indicate that the unserviced message is an N26 interface message type.
  • Step 805 LLOF parses the request message #2 and encapsulates the PFCP session message.
  • sequential PFCP session messages may be encapsulated according to the protocol stack shown in FIG. 3 . That is, UDP header encapsulation and IP header encapsulation are performed on the PFCP session message in sequence.
  • LLOF encapsulates the PFCP header for the IE to obtain the PFCP session message.
  • the UDP layer can then continue to encapsulate the PFCP session message using the UDP header,
  • the UDP source port can be a UDP port number assigned by LLOF, for example, UDP port number #1; the UDP destination port is port number #8805.
  • the IP layer can then use an IP header to encapsulate the UDP layer message.
  • the source IP address of the IP header is the IP address of LLOF
  • the destination IP address is the IP address of UPF#1.
  • Step 806 LLOF sends the encapsulated PFCP session message to UPF#1.
  • UPF#1 receives the encapsulated PFCP session message.
  • LLOF may determine that the target UPF is UPF#1 based on UPF information (for example, UPF address information, and/or UPF parameter information), and send an encapsulated PFCP session message to UPF#1.
  • UPF information for example, UPF address information, and/or UPF parameter information
  • the destination address in the session message is the IP address of UPF#1.
  • Step 807 UPF#1 parses the encapsulated PFCP session message and allocates UP F-SEID.
  • UPF#1 can parse the IP header first, then the UDP header, and finally the PFCP header and IE. Also, UPF#1 can assign UP F-SEID#8 based on the name of the PFCP session message.
  • UPF#1 can store the CP F-SEID#1 and N4rule contained in the PFCP session message, And send a response message to LLOF, the response message contains "success” indication information.
  • the response message sent by UPF#1 to LLOF contains "error cause" (can also be understood as "cause value”) indication information.
  • the response message sent by UPF#1 to LLOF contains indication information #2, which is a response to the PFCP session message.
  • the indication information may be rejection "reason value” indication information, or "success” indication information.
  • the response message may be first encapsulated into a PFCP session message, and the PFCP session message includes a PFCP session message header and one or more IEs.
  • the PFCP message header may include SEID#1; in another possible implementation, the PFCP session message header may include CP F-SEID#1, PFCP The session message IE includes the UP F-SEID.
  • UPF#1 can encapsulate UP F-SEID#8 and CP F-SEID#2 in IE; in another possible implementation, PFCP message The header may include SEID#2, and the IE of the PFCP session message may include UP F-SEID#8; in another possible implementation, the PFCP session message header may include CP F-SEID#2, and the PFCP session message IE can include UP F-SEID#8.
  • the UDP header is used to encapsulate the PFCP session message.
  • the source port number of the UDP header is port number #8805
  • the port number of the UDP destination port is port number #1.
  • use an IP header for encapsulation For example, the source IP address of the IP header is the IP address of the UPF, and the destination IP address of the IP header is the IP address of the LLOF.
  • Step 808 UPF#1 sends the encapsulated response message #2 to LLOF.
  • the corresponding LLOF receives response message #2.
  • Step 809 LLOF parses response message #2, obtains CP F-SEID#1, and determines the corresponding SMF based on the correspondence between the saved SMF and CP F-SEID.
  • LLOF can parse IP headers, UDP headers, and PFCP headers in sequence.
  • SEID#1 is obtained after successfully parsing the PFCP session message header.
  • LLOF can obtain CP F-SEID#1 based on SEID#1 and its own IP address. As described in step 801, since the correspondence between SMF and CP F-SEID is stored on LLOF, at this time, LLOF can determine that the target SMF is SMF#1 based on the correspondence.
  • Step 810 LLOF sends response message #3 to SMF#1.
  • LLOF can provide message forwarding service.
  • LLOF can be based on Nllof_ Message_Notify service, sends response message #3 to SMF#1.
  • the response message #3 carries indication information #2 and UP F-SEID #8.
  • the response message #3 can be a message in HTTP format, or it can also be understood that the response message #3 can be transmitted using a service-oriented interface protocol.
  • steps 801 to 810 are understood as the N4 session establishment process, that is, the PFCP session message is a PFCP session establishment message
  • steps 811 to 815 can be understood as the N4 session modification process or the N4 session release process.
  • step 811 SMF sends N4 session modification request message #1 to LLOF.
  • LLOF receives session modification request message #1 from SMF.
  • the N4 session modification request message #1 can be a PFCP session modification message.
  • the PFCP session modification message header contains UP F-SEID#8.
  • the IE of the PFCP session modification message may include some update rules of the N4 session message, and so on.
  • the N4 session modification request message #1 can be transmitted through the service interface.
  • the N4 session modification request message #1 may be encapsulated into a message in HHTP format.
  • step 812 LLOF determines the target UPF based on the N4 session modification request message #1.
  • LLOF can determine that the target UPF is UPF#1 based on the fact that the PFCP session modification message header contains UP F-SEID#8.
  • step 813 LLOF sends N4 session modification request message #2 to UPF#1.
  • UPF#1 receives session modification request message #2 from LLOF.
  • the session modification request message #2 is a PFCP session modification message.
  • the IE of the PFCP session modification message may include some update rules of the N4 session message, and so on.
  • the PFCP session modification message header may contain CP F-SEID#1.
  • LLOF can send an N4 session modification request message to UPF#1 through the N4 interface.
  • UPF#1 sends session modification response message #1 to LLOF.
  • the corresponding LLOF receives session modification response message #1.
  • UPF#1 can send a response message to LLOF.
  • the response message contains indication information #3.
  • the indication information #3 can be "success” indication information.
  • the response message sent by UPF#1 to LLOF contains an "error cause" (can also be understood as "reason value”) indication. information.
  • the session modification response message contains a PFCP session modification message header and one or more IEs.
  • the PFCP message header may include SEID#1 assigned by LLOF to the SMF.
  • the PFCP message header may include the CP F-SEID#1 assigned by LLOF to the SMF. The information carried in the response message here is consistent with the response message for session establishment, and the processing after LLOF is received is also consistent.
  • step 815 LLOF parses the session modification response message #1, obtains CP F-SEID #1, and determines the corresponding SMF based on the correspondence between the saved SMF and CP F-SEID.
  • LLOF can parse IP headers, UDP headers, and PFCP headers in sequence.
  • SEID#1 is obtained after successfully parsing the PFCP session modification message header.
  • LLOF can obtain CP F-SEID#1 based on SEID#1 and its own IP address.
  • step 801 since the correspondence between SMF and CP F-SEID is stored on LLOF, At this time, LLOF can determine that the target SMF is SMF#1 based on the corresponding relationship.
  • step 816 LLOF sends a session modification response message to SMF#1.
  • LLOF can provide a message forwarding service.
  • LLOF can send a session modification response message to SMF#1 based on the Nllof_Message_Notify service.
  • this application proposes a new network service-oriented architecture including LLOF.
  • the service-oriented interface can be used to transmit messages between LLOF and SMF, so that SMF can be completely service-oriented.
  • LLOF can provide services such as allocating CP F-SEID and forwarding messages to ensure communication between SMF and UPF.
  • the session context information is saved on LLOF, when the SMF fails, LLOF can quickly select a new SMF, transmit the session context to the newly selected SMF, provide services for the session, reduce communication delay, and ensure user safety. Business experience.
  • pre-definition in this application can be understood as definition, pre-definition, storage, pre-storage, pre-negotiation, pre-configuration, solidification, or pre-firing.
  • each node such as the link load orchestration function network element, the session management function network element, and the user plane function network element, in order to realize the above functions, includes hardware structures and/or software modules corresponding to each function.
  • the present application can be implemented in the form of hardware or a combination of hardware and computer software with the units and algorithm steps of each example described in conjunction with the embodiments disclosed herein. Whether a function is performed by hardware or computer software driving the hardware depends on the specific application and design constraints of the technical solution. Skilled artisans may implement the described functionality using different methods for each specific application, but such implementations should not be considered beyond the scope of this application.
  • the link load orchestration function network element includes corresponding hardware structures and/or software modules for executing each function.
  • the units and method steps of each example described in conjunction with the embodiments disclosed in this application can be implemented in the form of hardware or a combination of hardware and computer software. Whether a certain function is executed by hardware or computer software driving the hardware depends on the specific application scenarios and design constraints of the technical solution.
  • FIGS 9 and 10 are schematic structural diagrams of possible message routing devices provided by embodiments of the present application. These message routing devices can be used to implement the functions of the link load orchestration functional network elements in the above method embodiments, and therefore can also achieve the beneficial effects of the above method embodiments.
  • the message routing device 100 includes a processing unit 110 and a transceiver unit 120 .
  • the message routing device 100 is used to implement the functions of the link load orchestration functional network element in the method embodiment shown in FIG. 8 .
  • the transceiver unit 120 is used to receive the first message from the session management function network element, and the first message carries the user The first message is used to request the forwarding of session messages, where the first message is transmitted through the service interface of the device, and the processing unit 110 is used to determine the target according to the information of the user plane functional network element.
  • the transceiver unit 120 is also configured to send session messages to the target user plane functional network element through the non-service interface.
  • the transceiver unit 120 is used to receive a second message from the session management function network element, and the second message is used to request to obtain the CP F-SEID corresponding to the session management function network element; the processing The unit 110 is configured to allocate the corresponding CP F-SEID to the session management function network element according to the second message; the transceiver unit 120 is used to send the CP F-SEID to the session management function network element.
  • the processing unit 110 is configured to allocate a corresponding control plane fully qualified session endpoint identifier CP F-SEID to the session management function network element according to the first message.
  • the processing Unit 110 is configured to encapsulate the CP F-SEID in the information element IE of the session message.
  • the processing unit 110 is configured to save the mapping relationship between the session management function network element and the CP F-SEID.
  • the processing unit 110 is configured to encapsulate the session message; the transceiver unit 120 sends the session message to the target user plane functional network element, including: the transceiver unit 120 uses To send the encapsulated session message to the target user plane functional network element.
  • the transceiver unit 120 is configured to receive a third message from the target user plane functional network element, where the third message carries the session endpoint identifier SEID and the user plane fully qualified session endpoint identifier UP F- SEID and indication information, wherein the indication information is used to respond to the session message; the processing unit 110 is used to determine the CP F-SEID according to the SEID; the processing unit 110 determines the CP F-SEID according to the CP F- The mapping relationship between the SEID and the session management function network element controls the transceiver unit 120 to send a fourth message to the session management function network element, where the fourth message carries the UP F-SEID and the indication information.
  • processing unit 110 and transceiver unit 120 can be obtained directly by referring to the relevant descriptions in the method embodiment shown in FIG. 8 , and will not be described again here.
  • the message routing device 200 includes a processor 210 and an interface circuit 220 .
  • the processor 210 and the interface circuit 220 are coupled to each other.
  • the interface circuit 220 may be a transceiver or an input-output interface.
  • the message routing device 200 may also include a memory 230 for storing instructions executed by the processor 210 or input data required for the processor 210 to run the instructions or data generated after the processor 210 executes the instructions.
  • the processor 210 is used to implement the functions of the above-mentioned processing unit 110
  • the interface circuit 220 is used to implement the functions of the above-mentioned transceiver unit 120 .
  • processor shown in FIG. 10 may include at least one processor, and the interface circuit may also include multiple interface circuits.
  • the processor in the embodiment of the present application can be a central processing unit (Central Processing Unit, CPU), or other general-purpose processor, digital signal processor (Digital Signal Processor, DSP), or application specific integrated circuit. (Application Specific Integrated Circuit, ASIC), Field Programmable Gate Array (FPGA) or other programmable logic devices, transistor logic devices, hardware components or any combination thereof.
  • a general-purpose processor can be a microprocessor or any conventional processor.
  • the present application also provides a computer program product.
  • the computer program product stores computer program code.
  • the computer program code When the computer program code is run on the computer, the computer is caused to execute method 700 and method 800.
  • the method is executed by the link load orchestration function network element in the embodiment.
  • the present application also provides a computer-readable medium.
  • the computer-readable medium stores program code.
  • the program code When the program code is run on a computer, it causes the computer to execute the method 700 of the above embodiment.
  • method 800 the method is executed by the link load orchestration function network element.
  • this application also provides a communication system, which includes a terminal and a network device.
  • the terminal is used to perform steps corresponding to the link load orchestration function network element in the above method 700 and method 800.
  • the communication system may also include a user plane functional network element and a session management functional network element.
  • the method steps in the embodiments of the present application can be implemented in hardware or in software instructions that can be executed by a processor.
  • Software instructions can be composed of corresponding software modules, and the software modules can be stored in random access memory, flash memory, read-only memory, programmable read-only memory, erasable programmable read-only memory, electrically erasable programmable read-only memory In memory, register, hard disk, mobile hard disk, CD-ROM or any other form of storage medium well known in the art.
  • An exemplary storage medium is coupled to the processor such that the processor can read information from the storage medium and write information to the storage medium.
  • the storage medium may also be an integral part of the processor.
  • the processor and storage media may be located in an ASIC.
  • the ASIC can be located in the link load orchestration function network element.
  • the processor and storage media may also exist as discrete components in the link load orchestration function network element.
  • the computer program product includes one or more computer programs or instructions.
  • the computer may be a general purpose computer, a special purpose computer, a computer network, a network device, a user equipment, or other programmable device.
  • the computer program or instructions may be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another.
  • the computer program or instructions may be transmitted from a website, computer, A server or data center transmits via wired or wireless means to another website site, computer, server, or data center.
  • the computer-readable storage medium may be any available medium that can be accessed by a computer or a data storage device such as a server or data center that integrates one or more available media.
  • the available media may be magnetic media, such as floppy disks, hard disks, and magnetic tapes; they may also be optical media, such as digital video optical disks; they may also be semiconductor media, such as solid-state media. harddisk.
  • the computer-readable storage medium may be volatile or nonvolatile storage media, or may include both volatile and nonvolatile types of storage media.

Landscapes

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

Abstract

本申请实施例提供一种消息路由方法和装置，提出了一种包含LLOF的新的网络服务化架构，LLOF可以与SMF之间采用服务化接口传输消息，LLOF可以与UPF之间采用非服务化接口，使得SMF彻底实现服务化，并且，还可以实现SMF通过LLOF与UPF之间的通信。

Description

消息路由方法和装置
本申请要求于2022年7月30日提交中国专利局、申请号为202210912571.7、申请名称为“消息路由方法和装置”的中国专利申请的优先权，其全部内容通过引用结合在本申请中。
技术领域
本申请实施例涉及通信领域，并且更具体的，涉及一种消息路由方法和装置。
背景技术
目前，第三代合作伙伴计划(3rd generation partnership project，3Gpp)为了提高网络的可靠性和弹性，已经提出了网络服务化架构。例如，图1所示的5G网络服务化架构中，会话管理功能网元(session management function，SMF)不仅需要支持服务化接口(例如，SMF与接入与移动性管理功能网元(access and mobility management function，AMF)、策略控制管理功能网元(policy control function，PCF)等之间为服务化接口)，SMF还需要支持非服务化接口(例如，SMF与用户面功能网元(user plane function，UPF)之间的N4接口为非服务化接口)。
由于，在非服务化接口上，用户上下文与物理接口之间存在绑定关系。例如，SMF需要保留用户的上下文信息或传输层关联的上下文信息。此时，如果SMF发生故障时，也会影响UPF的性能，例如，UPF可能需要重新和新的SMF建立会话，传输上下文信息，等等。换句话说，目前的5G网络服务化架构中，SMF的服务化功能不彻底，导致SMF故障恢复或者SMF的扩/缩容时与UPF存在耦合关系，不够灵活，不能充分发挥服务化架构的优势。
有鉴于此，如何使得SMF可以彻底实现服务化并且实现与UPF的通信，成为目前需要解决的技术问题。
发明内容
本申请实施例提供一种消息路由方法，提出了一种包含LLOF的新的网络服务化架构，LLOF可以与SMF之间采用服务化接口传输消息，LLOF可以与UPF之间采用非服务化接口，使得SMF彻底实现服务化，并且，还可以实现SMF通过LLOF与UPF之间的通信。
第一方面，提供了一种通信方法，该方法可以由链路负载编排功能网元执行，或者，也可以由链路负载编排功能网元的组成部件(例如芯片或者电路)执行，对此不作限定。
该方法包括：链路负载编排功能网元接收来自会话管理功能网元的第一消息，该第一消息携带用户面功能网元的信息和会话消息，第一消息用于请求转发会话消息，其中，第一消息通过链路负载编排功能网元的服务化接口传输；链路负载编排功能网元根据用户面 功能网元的信息，确定目标用户面功能网元；链路负载编排功能网元通过非服务化接口向该目标用户面功能网元发送会话消息。
本申请中，例如会话消息可以为数据包转发控制协议PFCP会话消息。
在一种可能的实现方式中，该会话消息包括信息元素IE，IE包括与会话管理功能网元对应的控制面全限定会话终点标识符CP F-SEID。
在一种可能的实现方式中，链路负载编排功能网元接收来自会话管理功能网元的第一消息之前，方法还包括：链路负载编排功能网元接收来自会话管理功能网元的第二消息，第二消息用于请求获取会话管理功能网元对应的CP F-SEID；链路负载编排功能网元根据所述第二消息，为会话管理功能网元分配对应的CP F-SEID；链路负载编排功能网元向会话管理功能网元发送CP F-SEID。
基于上述技术方案，本申请中，在LLOF支持解析会话消息头但不支持解析会话消息的IE时，SMF可以提前先从LLOF获取对应的会话终点标识符CP F-SEID，并且封装在会话消息的IE中发送给LLOF，从而便于LLOF可以将会话消息转发给目标UPF。
在一种可能的实现方式中，CP F-SEID可以是由会话管理功能网元分配的。
基于上述技术方案，本申请中，SMF也可以自己分配CP F-SEID，从而与现有技术进行兼容，即对现有的协议改动较小，便于实现，减少成本。此外，SMF无需向LLOF请求获取CP F-SEID，可以减少流程的复杂度。
在一种可能的实现方式中，链路负载编排功能网元根据第一消息，为会话管理功能网元分配对应的控制面全限定会话终点标识符CP F-SEID，链路负载编排功能网元将CP F-SEID封装在会话消息的信息元素IE中。
基于上述技术方案，本申请中，LLOF提供分配CP F-SEID的服务，CP F-SEID与SMF之间的绑定关系可以动态更新，即如果SMF发生故障，则LLOF可以重新选择一个新的SMF，无需重新分配CP F-SEID，只需将CP F-SEID与新的SMF绑定，可以减小通信时延，保障用户业务体验。
在一种可能的实现方式中，该方法还包括：链路负载编排功能网元保存会话管理功能网元与CP F-SEID之间的映射关系。
基于上述技术方案，本申请中，LLOF可以保存映射关系，以便后续LLOF可以基于该映射关系对来自UPF的消息进行路由，可以实现SMF和UPF之间的通信。
在一种可能的实现方式中，该方法还包括：链路负载编排功能网元封装会话消息，链路负载编排功能网元向目标用户面功能网元发送会话消息，包括：链路负载编排功能网元向目标用户面功能网元发送封装后的会话消息。
例如，链路负载编排功能网元可以按照N4接口协议栈的格式对会话消息进行封装。
基于上述技术方案，本申请中，LLOF可以封装会话消息，从而使得LLOF与UPF之间遵循N4接口协议，无需对UPF做任何改动，便于实现，减少成本。
在一种可能的实现方式中，该方法还包括：链路负载编排功能网元接收来自目标用户面功能网元的第三消息，第三消息携带会话终点标识符SEID、用户面全限定会话终点标识符UP F-SEID。第三消息还携带指示信息，其中，指示信息用于响应所述会话消息，链路负载编排功能网元根据SEID，确定CP F-SEID；链路负载编排功能网元根据CP F-SEID与会话管理功能网元的映射关系，向会话管理功能网元发送第四消息，第四消息携带UP  F-SEID和所述指示信息。
在一种可能的实现方式中，第三消息的报头包括SEID，第三消息的IE包括UP F-SEID。
在一种可能的实现方式中，链路负载编排功能网元接收来自目标用户面功能网元的第三消息，第三消息的IE包括UP F-SEID、CP F-SEID，第三消息还携带指示信息，其中，指示信息用于响应会话消息，链路负载编排功能网元根据CP F-SEID与会话管理功能网元的映射关系，向会话管理功能网元发送第四消息，第四消息携带所述UP F-SEID和指示信息。
在一种可能的实现方式中，链路负载编排功能网元接收来自目标用户面功能网元的第三消息，第三消息的报头包括CP F-SEID，第三消息携带指示信息，其中，指示信息用于响应会话消息，链路负载编排功能网元根据CP F-SEID与会话管理功能网元的映射关系，向会话管理功能网元发送第四消息，第四消息携带所述UP F-SEID和指示信息。
基于上述技术方案，本申请中，LLOF可以通过映射关系对来自UPF的消息进行路由，即确定目标SMF，从而实现SMF与UPF之间的通信，避免LLOF将消息发送给错误的SMF引发的信令消耗。
第二方面，提供了一种消息路由装置，该装置用于执行上述第一方面中任一种可能实现方式中的方法。具体地，该装置可以包括用于执行第一方面中任何一种可能实现方式中的方法的单元和/或模块，如收发单元和/或处理单元。
在一种实现方式中，该装置为链路负载编排功能网元。当该装置为通信设备时，通信单元可以是收发器，或，输入/输出接口；处理单元可以是至少一个处理器。可选地，收发器可以为收发电路。可选地，输入/输出接口可以为输入/输出电路。
在另一种实现方式中，该装置为用于链路负载编排功能网元的芯片、芯片系统或电路。当该装置为用于通信设备的芯片、芯片系统或电路时，通信单元可以是该芯片、芯片系统或电路上的输入/输出接口、接口电路、输出电路、输入电路、管脚或相关电路等；处理单元可以是至少一个处理器、处理电路或逻辑电路等。
第三方面，提供了一种消息路由装置，该装置包括：至少一个处理器，用于执行存储器存储的计算机程序或指令，以执行上述第一方面中任一方面中任一种可能实现方式中的方法。可选地，该装置还包括存储器，用于存储的计算机程序或指令。可选地，该装置还包括通信接口，处理器通过通信接口读取存储器存储的计算机程序或指令。
在一种实现方式中，该装置为链路负载编排功能网元。
在另一种实现方式中，该装置为用于链路负载编排功能网元的芯片、芯片系统或电路。
第四方面，本申请提供一种处理器，包括：输入电路、输出电路和处理电路。所述处理电路用于通过所述输入电路接收信号，并通过所述输出电路发射信号，使得所述处理器执行第一方面中任一方面中任一种可能实现方式中的方法。
在具体实现过程中，上述处理器可以为一个或多个芯片，输入电路可以为输入管脚，输出电路可以为输出管脚，处理电路可以为晶体管、门电路、触发器和各种逻辑电路等。输入电路所接收的输入的信号可以是由例如但不限于收发器接收并输入的，输出电路所输出的信号可以是例如但不限于输出给发射器并由发射器发射的，且输入电路和输出电路可以是同一电路，该电路在不同的时刻分别用作输入电路和输出电路。本申请实施例对处理器及各种电路的具体实现方式不做限定。
对于处理器所涉及的发送和获取/接收等操作，如果没有特殊说明，或者，如果未与其在相关描述中的实际作用或者内在逻辑相抵触，则可以理解为处理器输出和接收、输入等操作，也可以理解为由射频电路和天线所进行的发送和接收操作，本申请对此不做限定。
第五方面，提供了一种处理设备，包括处理器和存储器。该处理器用于读取存储器中存储的指令，并可通过收发器接收信号，通过发射器发射信号，以执行第一方面中任一方面中任一种可能实现方式中的方法。
可选地，所述处理器为一个或多个，所述存储器为一个或多个。
可选地，所述存储器可以与所述处理器集成在一起，或者所述存储器与处理器分离设置。
在具体实现过程中，存储器可以为非瞬时性(non-transitory)存储器，例如只读存储器(read only memory，ROM)，其可以与处理器集成在同一块芯片上，也可以分别设置在不同的芯片上，本申请实施例对存储器的类型以及存储器与处理器的设置方式不做限定。
应理解，相关的数据交互过程例如发送指示信息可以为从处理器输出指示信息的过程，接收能力信息可以为处理器接收输入能力信息的过程。具体地，处理器输出的数据可以输出给发射器，处理器接收的输入数据可以来自收发器。其中，发射器和收发器可以统称为收发器。
上述第五方面中的处理设备可以是一个或多个芯片。该处理设备中的处理器可以通过硬件来实现也可以通过软件来实现。当通过硬件实现时，该处理器可以是逻辑电路、集成电路等；当通过软件来实现时，该处理器可以是一个通用处理器，通过读取存储器中存储的软件代码来实现，该存储器可以集成在处理器中，可以位于该处理器之外，独立存在。
第六方面，提供一种计算机可读存储介质，该计算机可读介质存储用于设备执行的程序代码，该程序代码包括用于执行上述第一方面中任一种可能实现方式中的方法。
第七方面，提供一种包含指令的计算机程序产品，当该计算机程序产品在计算机上运行时，使得计算机执行上述第一方面中任一种可能实现方式中的方法。
第八方面，提供一种芯片系统，包括处理器，用于从存储器中调用并运行计算机程序，使得安装有该芯片系统的设备执行上述第一方面中任一方面中各实现方式中的方法。
第九方面，提供一种通信系统，该通信系统包括链路负载编排功能网元。所述链路负载编排功能网元用于执行上述第一方面中任一方面中的任一种可能实现方法。
在一种可能的实现方式中，该通信系统还包括会话管理功能网元和用户面功能网元。
附图说明
图1是5G网络服务化架构的示意图。
图2是本申请提出的一种5G网络服务化架构的示意图。
图3是N4接口的协议栈的示意图。
图4是PFCP会话消息的格式的示意图。
图5是PFCP会话消息头的格式的示意图。
图6是PFCP会话消息信息元素的一种格式的示意图。
图7是本申请提供的一种消息路由方法700的示意性流程图。
图8是本申请提供的另一种消息路由方法800的示意性流程图。
图9是本申请提供的一种消息路由装置100的示意性框图。
图10是本申请提供的另一种消息路由装置200的示意性框图。
具体实施方式
下面将结合附图，对本申请实施例中的技术方案进行描述。
本申请提及的无线通信系统包括但不限于：全球移动通信(global system of mobile communication，GSM)系统、长期演进(long term evolution，LTE)频分双工(frequency division duplex，FDD)系统、LTE时分双工(time division duplex，TDD)、LTE系统、先进的长期演进(LTE-Advanced，LTE-A)系统、下一代通信系统(例如，6G通信系统)、多种接入系统的融合系统，或演进系统。
本申请提供的技术方案还可以应用于机器类通信(machine type communication，MTC)、机器间通信长期演进技术(long term evolution-machine，LTE-M)、设备到设备(device to device，D2D)网络、机器到机器(machine to machine，M2M)网络、物联网(internet of things，IoT)网络或者其他网络。其中，IoT网络例如可以包括车联网。其中，车联网系统中的通信方式统称为车到其他设备(vehicle to X，V2X，X可以代表任何事物)，例如，该V2X可以包括：车辆到车辆(vehicle to vehicle，V2V)通信，车辆与基础设施(vehicle to infrastructure，V2I)通信、车辆与行人之间的通信(vehicle to pedestrian，V2P)或车辆与网络(vehicle to network，V2N)通信等。
图1示出了一种5G系统(the 5th generation system，5GS)网络服务化架构的示意图，该网络架构具体可以包括下列网元：
1、用户设备(user equipment，UE)：可以称为终端设备、接入终端、用户单元、用户站、移动站、移动台、远方站、远程终端、移动设备、用户终端、终端、无线通信设备、用户代理或用户装置。
终端设备可以是一种向用户提供语音/数据的设备，例如，具有无线连接功能的手持式设备、车载设备等。目前，一些终端的举例为：手机(mobile phone)、平板电脑、笔记本电脑、掌上电脑、移动互联网设备(mobile internet device，MID)，虚拟现实(virtual reality，VR)设备、增强现实(augmented reality，AR)设备、工业控制(industrial control)中的无线终端、无人驾驶(self driving)中的无线终端、远程手术(remote medical surgery)中的无线终端、智能电网(smart grid)中的无线终端、运输安全(transportation safety)中的无线终端、智慧城市(smart city)中的无线终端、智慧家庭(smart home)中的无线终端、蜂窝电话、无绳电话、会话启动协议(session initiation protocol，SIP)电话、无线本地环路(wireless local loop，WLL)站、个人数字助理(personal digital assistant，PDA)、具有无线通信功能的手持设备、计算设备或连接到无线调制解调器的其它处理设备，5G网络中的终端设备或者未来演进的公用陆地移动通信网络(public land mobile network，PLMN)中的终端设备等，本申请实施例对此并不限定。
作为示例而非限定，在本申请实施例中，该终端设备还可以是可穿戴设备。可穿戴设备也可以称为穿戴式智能设备，是应用穿戴式技术对日常穿戴进行智能化设计、开发出可以穿戴的设备的总称，如眼镜、手套、手表、服饰及鞋等。可穿戴设备即直接穿在身上，或是整合到用户的衣服或配件的一种便携式设备。可穿戴设备不仅仅是一种硬件设备，更 是通过软件支持以及数据交互、云端交互来实现强大的功能。广义穿戴式智能设备包括功能全、尺寸大、可不依赖智能手机实现完整或者部分的功能，例如：智能手表或智能眼镜等，以及只专注于某一类应用功能，需要和其它设备如智能手机配合使用，如各类进行体征监测的智能手环、智能首饰等。
此外，在本申请实施例中，终端设备还可以是IoT系统中的终端设备，IoT是未来信息技术发展的重要组成部分，其主要技术特点是将物品通过通信技术与网络连接，从而实现人机互连，物互连的智能化网络。
需要指出的是，终端设备与接入网设备之间可以采用某种空口技术(如NR或LTE技术等)相互通信。终端设备与终端设备之间也可以采用某种空口技术(如NR或LTE技术等)相互通信。
本申请实施例中，用于实现终端设备的功能的装置可以是终端设备，也可以是能够支持终端设备实现该功能的装置，例如芯片系统或芯片，该装置可以被安装在终端设备中。本申请实施例中，芯片系统可以由芯片构成，也可以包括芯片和其他分立器件。
2、(无线)接入网((radio)access network，(R)AN)设备：可以为特定区域的授权用户提供接入通信网络的功能，具体可以包括第三代合作伙伴计划(3rd generation partnership project，3GPP)网络中无线网络设备也可以包括非3GPP(non-3GPP)网络中的接入点。
RAN设备可以为采用不同的无线接入技术。目前的无线接入技术有两种类型：3GPP接入技术(例如，第三代(3rd generation，3G)、第四代(4th generation，4G)或5G系统中采用的无线接入技术)和非3GPP(non-3GPP)接入技术。3GPP接入技术是指符合3GPP标准规范的接入技术，例如，5G系统中的接入网设备称为下一代基站节点(next generation Node Base station，gNB)或者RAN设备。非3GPP接入技术可以包括以无线保真(wireless fidelity，WiFi)中的接入点(access point，AP)为代表的空口技术、全球互联微波接入(worldwide interoperability for microwave access，WiMAX)、码分多址(code division multiple access，CDMA)等。AN设备可以允许终端设备和3GPP核心网之间采用非3GPP技术互连互通。
RAN设备能够负责空口侧的无线资源管理、服务质量(quality of service，QoS)管理、数据压缩和加密等功能。AN设备为终端设备提供接入服务，进而完成控制信号和用户数据在终端设备和核心网之间的转发。
RAN设备例如可以包括但不限于：宏基站、微基站(也称为小站)、无线网络控制器(radio network controller，RNC)、节点B(Node B，NB)、基站控制器(base station controller，BSC)、基站收发台(base transceiver station，BTS)、家庭基站(例如，home evolved NodeB，或home Node B，HNB)、基带单元(baseband unit，BBU)，WiFi系统中的AP、无线中继节点、无线回传节点、传输点(transmission point，TP)或者发送接收点(transmission and reception point，TRP)等，还可以为5G(如，NR)系统中的gNB或传输点(TRP或TP)，5G系统中的基站的一个或一组(包括多个天线面板)天线面板，或者，还可以为构成gNB或传输点的网络节点，如分布式单元(distributed unit，DU)，或者下一代通信6G系统中的基站等。本申请实施例对AN设备所采用的具体技术和具体设备形态不做限定。
3、用户面功能网元(user plane function，UPF)：可用于分组路由和转发、或用户面(user plane，UP)数据的服务质量(quality of service，QoS)处理等。用户数据可通过该网元接入到数据网络(data network，DN)。在本申请实施例中，可用于实现用户面网元的功能。
4、数据网络(digital network，DN)：用于提供传输数据的网络。例如，运营商业务的网络、因特(Internet)网、第三方的业务网络等。
5、网络切片选择的认证和授权功能网元：(network slice-specific authentication and authorization function，NSSAAF)：支持使用鉴权、授权和记账(authentication,authorization and accounting，AAA)服务器对指定的网络切片特定身份验证和授权，如果AAA服务器属于第三方，NSSAAF可以通过AAA代理联系AAA服务器。支持使用AAA服务器的凭据访问SNPN，如果凭据持有者属于第三方，NSSAAF可以通过AAA代理联系AAA服务器。
6、鉴权服务功能网元(authentication server function，AUSF)：支持为请求者网元验证UE、向请求者网元提供密钥材料、保护请求者网元的“指导信息列表”。
7、接入和移动管理功能网元(access and mobility management function，AMF)：主要用于移动性管理和接入管理等，可以用于实现移动性管理实体(mobility management entity，MME)功能中除会话管理之外的其它功能，例如，终端移动性管理、终端注册与去注册、终端会话接入、终端的允许的切片接入选择、合法监听或接入授权(或鉴权)等功能。在本申请实施例中，可用于实现接入和移动管理网元的功能。
8、会话管理功能网元(session management function，SMF)：主要用于会话管理、终端设备的IP地址分配和管理、选择和管理用户平面功能、策略控制、收费功能接口的终结点或下行数据通知等。在本申请实施例中，可用于实现会话管理网元的功能。
9、服务通信代理(service communication proxy，SCP)：负责控制面(control plane，CP)网元间的服务化接口的消息路由，例如，，控制面网元包括AMF、SMF、AUSF、PCF等网元。
10、网络切片准入控制功能网元(network slice admission control function，NSACF)：可以支持监控和控制每个网络切片的注册用户数、支持监控和控制每个网络切片建立的协议数据单元(protocol data unit，PDU)会话数、支持基于事件的网络切片状态通知并向其他网元报告。
11、网络切片选择功能(network slice selection function，NSSF)：用于进行网络切片的选择。
12、网络能力开放功能网元(network exposure function，NEF)：用于安全地向外部开放由3GPP网络功能网元提供的业务和能力信息(如终端位置、网络拥塞状况)等。
13、网络仓库功能网元(network repository function，NRF)：该用于提供注册和发现功能的新功能，可以使各个网元相互发现并通过应用程序编程接口(application programming interface，API)接口进行通信。
14、策略控制网元(policy control function，PCF)：用于指导网络行为的统一策略框架，为控制平面功能网元(例如AMF，SMF网元等)提供业务策略、计费策略信息等。
15、统一数据管理(unified data management，UDM)：用于处理用户标识、接入鉴 权、注册、或移动性管理等。
16、应用功能网元(application function，AF)：用于提供业务，或者进行应用影响的数据路由，接入网络开放功能网元，或，与PCF网元交互业务数据进行策略控制等。
17、边缘应用服务器发现网元(edge application server discovery function，EASDF)：辅助边缘应用服务器(edge application server，EAS)发现的新网元EASDF，其主要作用为根据SMF的指示处理域名系统(domain name system，DNS)消息。例如，将DNS消息上报SMF、在DNS询问(query)中添加DNS扩展机制(extended mechanisms for DNS，EDNS)客户端子网选项(client subnet option)(DNS扩展机制客户端子网选项，也可简称为“ECS option”)、将DNS query转发到DNS服务器、将DNS响应(response)转发到UE等。
图1所示的架构中，例如，AMF、SMF既支持服务化接口，也支持非服务化接口。其中，“服务化接口”可以理解为是：通过服务化架构的服务注册和服务发现来实现的功能体对外暴露的接口，这种接口只针对于单个功能体，相关功能体通过服务化接口向外与其他的功能体进行交互，而其他的功能体通过该功能体暴露的接口与此功能体进行交互。换句话说，这种机制提供了一种“多对一”访问的机制，并且由于采用服务注册和服务发现，相互之间无需相互知道对方地址即可访问。这种机制使得各个网元之间的通信变得像服务吻合功能而不是串行链接，有助于减少每个接口之间的依赖性，并有助于每个网元的独立扩展。因此，服务化网络架构的服务的灵活性得到了提高。而“非服务化接口”可以理解为是，基于参考点的传统接口，即，两个不同功能网元之间相互约定的互访问的接口。在非服务化接口上，用户上下文与物理接口之间存在绑定关系。
例如，为了支持SMF的故障处理，每个注册到该SMF的UE，SMF需要将SMF集合(set)标识(ID)和/或该UE对应的备份SMF的信息发送给周边与其存在关系的其他网元(例如，发送给UPF)。当其他网元检测到SMF故障时，该网元可以根据SMF set ID从SMF set中重新选择一个SMF以便继续为该UE提供服务，或者，该网元也可以根据备份SMF的信息重新选择备份SMF以便继续该UE提供服务。又例如，即使SMF已经提供了备份机制，如果为UE服务的SMF出现故障时，即便可以重新选择新的SMF为UE提供服务，但由于旧的SMF出现故障，上下文信息可能无法传递给新选择的SMF，此时，UPF可能需要和新的SMF重新建立会话，传输上下文信息，增加了通信时延，影响用户的业务体验，等等。
再例如，N26接口是4G核心网(即，移动管理实体(mobility management entity，MME))和5G核心网(即，AMF)之间的接口，用于4G和5G的之间切换或重定向操作。如果5G核心网中的AMF支持N26接口，则RAN可通过切换或重定向进行回落，使用语音服务。
换句话说，目前的5G网络服务化架构中，SMF(或者AMF)的服务化功能不彻底，导致SMF(或AMF)故障恢复或者SMF的扩/缩容时与其它网元之间存在耦合关系，不够灵活，不能充分发挥服务化架构的优势。
有鉴于此，本申请对图1的5G网络服务化架构进行了改进，得到了如图2所示的新的服务化架构。与图1相比，图2中新增了一个功能网元。例如，该新增的功能网元可以称为“链路负载编排功能网元(link load orchestration function，LLOF)”。例如，LLOF 与UPF之间为N4接口，SMF与LLOF之间为服务化接口。因此，可以本申请中可以将SMF和UPF之间的非服务化N4接口屏蔽，从而可以彻底实现SMF的服务化功能。可选的，LLOF和RAN之间为N2接口，从而可以将AMF和RAN之间的非服务化N2接口屏蔽。可选的，LLOF和MME之间为N26接口，从而可以将AMF和MME之间的非服务化N26接口屏蔽。
本申请中的“屏蔽”也可以理解为，例如，SMF和UPF之间仍然可以存在N4接口，但是SMF可以不使用该N4接口与UPF通信。或者，也可以理解为，AMF和RAN之间仍然存在N2接口，但是AMF可以不使用该N2接口与RAN通信。又或者，还可以理解为，AMF和MME之间仍然存在N26接口，但是AMF可以不使用该N26接口与MME通信。
换句话说，与现有图1中的服务化架构相比，本申请提出了一种新的服务化架构，该架构中增加了LLOF，该LLOF可以终结非服务化接口，例如，可以终结N2接口、N4接口和N26接口。为了和现有的服务化架构兼容，UPF、RAN、MME与LLOF间的接口仍然基于现有的非服务化接口。LLOF与控制面网元(例如，AMF、SMF等)之间可以采用服务化接口，这样AMF、SMF不再需要支持非服务化接口，有利于AMF、SMF与其它网元之间进行解耦，可以更方便对其进行扩缩容，且简化了AMF、SMF的实现。
本申请中，LLOF可以提供如下服务中的一种或多种：
(1)LLOF提供服务化接口Nllof，控制面网元(例如，AMF、SMF等)可以通过该服务化接口请求LLOF提供服务。例如，SMF可以向LLOF发送超文本传输协议(hyper text transfer protocol，HTTP)请求消息，请求调用该LLOF的某种服务。
(2)LLOF终结N2接口的流控制传输协议(stream control transmission protocol，SCTP)链路。
(3)LLOF负责N2接口的网元级NG接口应用协议(NG application protocol，NGAP)消息的处理。其中，网元级NGAP消息是进行网元配置的消息；NG接口为RAN与核心网之间的接口。NG接口的消息，例如可以是，NG setup、RAN configuration update、AMF configuration update，等等。
(4)LLOF终结N4接口上的数据包转发控制协议(packet forwarding control protocol，PFCP)节点级消息(例如，节点级消息包括PFCP association相关的消息)的处理、负责PFCP会话消息的可靠重传、负责PFCP会话消息的互联网协议(Internet protocol，IP)、用户数据报协议(user datagram protocol，UDP)头的封装或解封装。
(5)LLOF负责GPRS控制面隧道协议(GPRS tunneling protocol-control plane，GTP-C)消息的可靠重传和GTP-C消息的IP、UDP头的封装和解封装。
(6)LLOF负责用户级N2、N4、GTP-C消息的路由。
(7)LLOF负责服务化接口(例如，SMF与AMF间接口、AMF与UDM间接口)的消息路由。
(8)LLOF负责路由标识的分配，其中，路由标识用于确定处理消息的控制面网元，例如，路由标识可以是N2接口的NGAP UE ID、或者N26接口的会话端点标识符(session endpoint identifier，SEID)、隧道端点标识符(tunnelingendpoint identifier，TEID)、N4接口的SEID等。
(9)LLOF负责绑定关系的维护，其中，绑定关系可以指UE的上下文与NF实例的对应关系。
(10)LLOF负责网元(例如，AMF、SMF等)的健康状态检测与容灾处理。
(11)LLOF负责网元(例如，AMF、SMF等)的扩缩容。
(12)LLOF负责网元(例如，AMF、SMF等)的负载分担与过载控制。
需要说明的是，本申请中，新增的功能网元的支持提供上述一种或多种服务，但是其具体的名称可以不予限定，在下面的描述中，仅仅是以该网元的名称为LLOF为例进行描述。
本申请中，由于提出了LLOF与SMF之间通过服务化接口进行通信，LLOF与UPF之间通过N4接口进行通信的新的服务化架构，并且，SMF和UPF之间的N4接口可以被屏蔽。此时，SMF和UPF之间如何通信，成为需要解决的技术问题。
应理解，上述图2示出的架构仅仅是可以应用于本申请实施例的网络架构的一种示例，适用本申请实施例的网络架构并不局限于此，任何能够实现上述各个网元的功能的网络架构都适用于本申请实施例。
在图1、图2所示的网络架构中，各网元之间可以通过图中所示的接口通信。例如，如图1所示，N1接口为终端设备与AMF之间的参考点；N2接口为RAN和AMF网元的接口，用于无线参数、非接入层信令(non-accessstratum，NAS)信令的发送等；N3接口为RAN和UPF网元之间的接口，用于传输用户面的数据等；N4接口为SMF网元和UPF网元之间的接口，用于传输例如业务策略、N3连接的隧道标识信息，数据缓存指示信息，以及下行数据通知消息等信息。N4接口为SMF和UPF之间的参考点，用于传输例如N3连接的隧道标识信息，数据缓存指示信息，以及下行数据通知消息等信息；N6接口为UPF和DN之间的参考点，用于传输用户面的数据等；N9接口为UPF的参考点。
应理解，图1、图2中的各个网元之间的接口名称只是一个示例，具体实现中接口的名称可能为其他的名称，本申请对此不作具体限定。此外，上述各个网元之间的所传输的消息(或信令)的名称也仅仅是一个示例，对消息本身的功能不构成任何限定。
还应理解，图1、图2中所示的AMF、SMF、LLOF等功能或者网元，可以理解为用于实现不同功能的网元。例如，可以按需组合成网络切片。这些网元可以各自独立的设备，也可以集成于同一设备中实现不同的功能，或者可以是硬件设备中的网络元件，也可以是在专用硬件上运行的软件功能，或者是平台(例如，云平台)上实例化的虚拟化功能，本申请对于上述网元的具体形态不作限定。
还应理解，上述命名仅为便于区分不同的功能而定义，不应对本申请构成任何限定。本申请并不排除在6G网络以及未来其它的网络中采用其他命名的可能。例如，在6G网络中，上述各个网元中的部分或全部可以沿用5G中的术语，也可能采用其他名称等。
如图1中的服务化架构中，5G网络在部分接口上仍然保持使用非服务化接口，例如，SMF和UPF之间需要传输大量的业务和策略信息的N4接口，其逻辑相对复杂，通常使用PFCP协议的非服务化接口。N4接口是SMF和UPF之间的接口，控制面用于传输节点级消息和会话级消息，采用PFCP协议；用户面用于传输SMF需要通过UPF接收或发送的报文，采用用户层面的GPRS隧道协议(GPRS tunnelling protocol for the user plane，GTP-U)。
图3示出了N4接口的协议栈，如图3所示，从上向下依次为PFCP层、UDP层、IP层、L2层(即，数据链路层)、L1层(物理层)。
图4示出了PFCP会话消息的格式，如图4所示，PFCP会话消息可以有n(为大于0的整数)个字节，每个字节分别有8位(bit)。其中，字节#1到字节#m为PFCP会话消息头(PFCP message header)(本申请中，“PFCP会话消息头”也称为“PFCP会话消息报头”)，字节#(m+1)到字节#n为零个或者多个信息元素(information element，IE)。具体的描述，可以参见技术规范(technical specification，TS)29.244中第7.2.1章。
图5具体示出了PFCP会话消息头的一种格式，如图5所示，PFCP会话消息头可以有16个字节(n为大于0的整数)，每个字节也是分别有8位。其中，第一个字节中的位#1为“S”标志，该标志指示会话端点标识符(session endpoint identifier，SEID)字段是否存在于PFCP会话消息头中。如果“S”标志设置为“0”，则SEID字段不得出现在PFCP头中。如果“S”标志设置为“1”，则SEID字段应紧随长度字段之后，以字节#5至字节#12为单位(共8个字节)。除了与节点有关的消息外，在所有PFCP会话消息中，“S”标志的值应为设置为“1”。当S＝1时，该字段可以明确标识接收分组转发控制实体中的会话端点。位#2代表“消息优先级(message priority，MP)”标志，如果MP设置为“1”，字节#16的第5位～第8位可以用于指示消息的优先级。位#3表示“跟随打开(follow open，FO)”标志。如果将“FO”标志设置为“1”，则在UDP或IP的数据包中将跟随另一个PFCP会话消息(具体可以参见TS.26.244第6.5和7.2.1A节)。位#4～位#5是备用位(spare)。如果发送实体将其设置为“0”，则接收实体应将其忽略。位6～位8代表PFCP版本(version)，当前版本都是1。应设置为十进制1(“001”)。字节#2代表消息类型(message type)；字节#3～字节#4是两字节的消息长度；字节#5～字节#12是可选项SEID字段，可以占8字节；字节#13～字节#15为序列号；最后一个字节#16为备用字节(例如，第5位～第8位可以指示消息的优先级)。具体的，有关PFCP会话消息头的描述，可以参见TS29.244中第7.2.2章。
图6示出了PFCP会话消息的IE的其中一种格式，如图6所示，前两个字节指示消息类型。例如，3GPP定义的IE类型值范围为0～32767，而供应商指定的IE的范围为：32768～65535。字节#3～字节#4指示消息长度。其中，企业(enterprise)ID为可选的字段。最后还包括：IE组的特定数据或IE的内容字段。
例如，IE包括控制面全限定的会话端点标识符(fully qualified session endpoint identifier，F-SEID)。需要说明的是，IE中包含的F-SEID和Header中的SEID不完全相同，F-SEID由SEID和IP地址构成，“IP地址”可以理解为，分配SEID的网元的IP地址。例如，现有技术中，该IP地址可以理解为SMF的IP地址，本申请中，这里的IP地址可以理解为LLOF的IP地址。换句话说，LLOF也可以基于SEID和自身的IP地址得到F-SEID。可选的，F-SEID也可以与SEID一致，本申请不做限定。
又例如，IE还包括创建数据包检测规则(packet detection rule，PDR)、更新数据检测规则、创建转发行为规则(forwarding action rules，FAR)、创建使用报告规则(usage reporting rules，URR)、创建Qos实施规则(QoS enforcement rules，QER)、转发参数(forwarding parameters)、复制参数(duplicating parameters)，等等。关于IE的格式和具体的说明可以参见TS.29.244的7.5章。
图7是本申请提出的一种消息路由方法700的示意性流程图，下面对图7所示的各步骤进行说明。需要说明的是，图7中用虚线表示的步骤是可选的，在后文中不多赘述。该方法包括：
步骤701，LLOF接收来自SMF的第一消息，第一消息携带UPF的信息和会话消息，第一消息用于请求转发该会话消息，该第一消息通过LLOF的服务化接口传输。
本申请中，该会话消息可以是PFCP会话消息；UPF的信息可以是UPF的地址信息，例如，IP地址或全限定域名(fully qualified domain name，FQDN)等；或者，UPF的信息也可以是UPF的参数信息，例如数据网络名称(data network name，DNN)和/或切片信息等；或者，UPF的信息例如可以是UP F-SEID。
可选的，该会话消息包括信息元素IE，IE包括与SMF对应的CP F-SEID。具体的，在一种可能的实现方式中，该CP F-SEID可以是由SMF分配的。在另一种可能的实现方式中，该CP F-SEID可以是由SMF从LLOF获取的。或者，也可以理解为，该CP F-SEID可以是由LLOF分配的。具体的，在步骤701之前，SMF可以向LLOF发送第二消息，该第二消息用于请求获取SMF对应的CP F-SEID。LLOF接收到第二消息后，为该SMF分配CP F-SEID，并发送给SMF。
可选的，该会话消息不包含SMF对应的CP F-SEID。此时，LLOF接收到第一消息后，可以为SMF分配对应的CP F-SEID，并将该CP F-SEID封装在该会话消息的信息元素IE中。
本申请中，LLOF还可以保存SMF与CP F-SEID之间的映射关系。
可替换地，本文中的“映射关系”也可以表述为“关联关系”、“对应关系”。
需要说明的是，本申请中的“A对应的B”可以理解为“A与B之间有关联关系”、“A与B之间有对应关系”、“A与B之间有映射关系”。本申请中“A对应的B”，表示根据B可以确定A，但还应理解，根据B确定A并不意味着仅仅根据B确定A，还可以根据B和/或其它信息确定A。
步骤702，LLOF根据UPF的信息，确定目标UPF。
例如，LLOF可以根据UPF的地址信息确定目标UPF，在一种实现中，LLOF根据UPF的FQDN信息查询对应的UPF。又例如，LLOF可以根据UPF的参数信息选择目标UPF，在一种实现中，LLOF根据DNN和切片选择辅助信息选择对应的UPF，从而确定UPF的IP地址，等等。
步骤703，LLOF通过非服务化接口向该目标UPF发送会话消息。对应的，UPF接收来自LLOF的会话消息。
例如，LLOF可以封装该会话消息，并将封装后的会话消息发送给目标UPF。
可选的，还包括步骤704，LLOF接收来自UPF的第三消息。
在一种可能的实现方式中，该第三消息报头包括SEID，第三消息的IE包括UP F-SEID，第三消息还携带指示信息。第三消息可以是会话消息，例如，PFCP会话消息。
其中，UP F-SEID可以是UPF基于接收到的会话消息分配的。例如，UPF可以根据会话消息的名称分配对应的UP F-SEID，等等。该指示信息用于响应该会话消息，例如，UPF接受会话消息中的IE，则UPF可以存储会话消息中包含的CP F-SEID以及N4rule，并向LLOF发送第三消息，第三消息中包含“成功”指示信息。若UPF只接受部分N4rule， 或者，若UPF全部不接受N4rule，则UPF向LLOF发送的第三消息中包含“错误原因”(也可以理解为“原因值”)指示信息。值得注意的是LLOF可以根据SEID和自身的IP地址获得CP F-SEID(该CP F-SEID为步骤701中SMF对应的CP F-SEID)；或者，SEID本身就等于F-SEID，本申请不做限定。
在另一种可能的实现方式中，该第三消息的IE包括该UP F-SEID、CP F-SEID，该第三消息还携带指示信息。
在又一种可能的实现方式中，该第三消息的报头包括该CP F-SEID，该第三消息还携带指示信息。
本申请中，例如，第三消息可以通过非服务化接口传输。
可选的，还包括步骤705，LLOF根据SMF与CP F-SEID的映射关系，向该SMF发送第四消息，第四消息携带UP F-SEID和指示信息。
LLOF接收到UPF发送的第三消息后，可以确定CP F-SEID。如前所述，CP F-SEID可以包含于IE或报头中，LLOF通过解析IE或报头获取CP F-SEID；又或者，LLOF根据SEID确定CP F-SEID，本申请不做限定。
如前所述，本申请中，由于LLOF上保存了SMF与CP F-SEID的映射关系，因此，LLOF确定CP F-SEID后，LLOF可以根据所述映射关系确定目标SMF，并向目标SMF转发指示信息和UP F-SEID。
本申请中，第四消息例如可以通过服务化接口传输。
基于上述技术方案，本申请提出了一种包含LLOF的新的网络服务化架构，LLOF可以与SMF之间采用服务化接口传输消息，LLOF可以与UPF之间采用非服务化接口，使得SMF彻底实现服务化，并且，还可以实现SMF通过LLOF与UPF之间的通信。
图8是本申请提出的另一种消息路由方法800的示意性流程图，本实施例中，以会话消息为PFCP消息为例进行描述。本实施例中以SMF为SMF#1为例进行描述，以UPF为UPF#1为例进行描述。
本申请中，在一种可能的实现方式中，LLOF支持解析和封装PFCP会话消息头，但不支持解析和封装PFCP会话消息的IE；在另一种可能的实现方式中，LLOF不仅支持LLOF支持解析和封装PFCP会话消息头，还支持解析和封装PFCP会话消息的IE。下面针对这情况描述本申请的技术方案。
情况(1)
假设LLOF支持解析和封装PFCP会话消息头，但不支持解析和封装PFCP会话消息的IE，则可以执行步骤801～步骤803。
可选的，步骤801，SMF#1向LLOF发送请求消息#1，请求消息#1用于请求获取对应的CP F-SEID。对应的，LLOF接收来自SMF的请求消息#1
本申请中，请求消息#1可以通过LLOF的服务化接口进行传输。例如，该请求消息#1可以是封装为HTTP格式的请求消息。
本申请中，LLOF提供为SMF分配CPF-SEID的服务。例如，该服务可以定义为Nllof_Fseid_allocation。也可以理解为，本申请中，LLOF具备为SMF分配CPF-SEID的能力，或者，LLOF支持为SMF分配CP F-SEID。
示例性的，SMF#1可以调用LLOF分配CPF-SEID的服务，请求LLOF为其分配对应 的CP F-SEID。例如，SMF#1可以向LLOF发送请求消息#1，请求消息#1用于向LLOF请求获取该SMF#1对应的CP F-SEID。
可选的，SMF#1在请求LLOF为其分配对应的CPF-SEID之前，可以先确定目标LLOF。换句话说，SMF可以确定向哪个LLOF发送请求消息#1。在一种可能的实现方式中，SMF可以根据配置信息或域名系统(domain name system，DNS)查询等方式确定目标LLOF。在另一种可能的实现方式中，SMF可以先选择UPF，SMF根据选择的UPF确定目标LLOF。例如，SMF根据数据网络名称(data network name，DNN)和/或网络切片(例如，单个网络切片选择协助信息(single network slice selection assistance information，S-NSSAI))等信息确定UPF。由于一些UPF仅支持互联网协议版本4(IPv4(version 4))，有的UPF仅支持IPv6，不同的LLOF对应于不同的IP版本，因此，SMF可以根据选择的UPF所支持的IP version确定目标LLOF，使得选择的LLOF能兼容UPF支持的IP版本。
可选的，步骤802，LLOF分配CP F-SEID#1，并与SMF#1绑定。
例如，LLOF接收到请求消息#1后，便可以触发LLOF分配对应的CP F-SEID的服务。
在一种可能的实现方式中，LLOF分配完CP F-SEID后，可以保存该SMF与该CP F-SEID之间的对应关系。
在另一种可能的实现方式中，LLOF上可以预先保存SMF与CP F-SEID的对应关系。例如，该对应关系可以在出厂时便配置在LLOF上。又例如，该对应关系可以是LLOF从其它网元获取的，等等，不予限定。
具体而言，例如，LLOF上可以保存一个或者多个SMF与CP F-SEID的对应关系。例如，该对应关系可以是表格的表现形式，如下表格1所示。表格1中，SMF#1对应于F-SEID#1，SMF#2对应于F-SEID#2，SMF#3对应于F-SEID#3。
表格1
本申请中，LLOF不仅提供分配CPF-SEID的服务，LLOF还支持修改SMF与CP F-SEID对应关系的功能。例如，假设SMF#1故障，则LLOF可以修改SMF#1与CP F-SEID#1之间的对应关系。例如，可以将CP F-SEID#1与SMF#2绑定。
本申请中，LLOF上还可以保存有SMF会话上下文的信息。因此，如果某个SMF发生故障，LLOF可以选择其它的SMF，并将会话上下文信息发送给新选择的SMF，使得该SMF可以继续会话相关的操作。例如，假设SMF#2与CPF-SEID#2绑定，若SMF#2发生故障，此时LLOF可以选择SMF#3继续会话相关的操作，此时，LLOF可以修改表格1中SMF#2与CPF-SEID#2的对应关系，即改为SMF#3与CPF-SEID#2对应。
现有技术中，SMF可以分配CPF-SEID，如果某个SMF发生故障，则需要新的SMF重新再为该会话分配CPF-SEID，并且故障SMF也无法将会话上下文信息传输给新选择的SMF，从而，使得新选择的SMF重新开始建立会话相关的操作，通信时延很长，严重影响用户的业务体验。
因此，与现有技术相比，本申请提出的LLOF的新的网络服务化架构，在SMF发生故障时，LLOF可以选择新的SMF，为会话提供服务，减小通信时延，保障用户的业务体验。
可选的，步骤803，LLOF向SMF#1发送响应消息#1，该响应消息#1携带CPF-SEID#1。
例如，该响应消息#1可以通过SMF#1与LLOF之间的服务化接口传输。具体的，该响应消息#1可以封装为HTTP的格式进行传输。
应理解，步骤801～步骤803，为SMF#1请求LLOF分配CPF-SEID的技术方案，本申请中，SMF也可以自己分配CPF-SEID，此时，也可以不执行步骤801～步骤803。
情况(2)
假设LLOF不仅支持LLOF支持解析和封装PFCP会话消息头，还支持解析和封装PFCP会话消息的IE，则可以不用执行步骤801～步骤803，直接执行步骤804。
步骤804，SMF#1向LLOF发送请求消息#2，请求消息#2携带UPF的信息和PFCP会话消息，请求消息#2用于请求转发该PFCP会话消息。对应的，LLOF接收来自SMF#1的请求消息#2。
针对情况(1)，由于PFCP会话消息携带IE，IE包括与所述会话管理功能网元对应的CP F-SEID#1。
针对情况(2)，由于PFCP会话消息头中不包含对应的CP F-SEID，后续LLOF收到请求消息#2后，解析出IE，发现IE中没有包含SMF#1对应的CP F-SEID，则可以为SMF#1分配对应的CP F-SEID#1，并且将该CP F-SEID#1封装在IE中。
并且，针对情况(2)，由于LLOF支持解析和封装IE，因此，在一种可能的实现方式中，不同的PFCP请求消息可以定义不同的服务名称。例如，定义Nllof_PFCP message_transfer用于传输PFCP会话消息(即，传输SMF和UPF之间的N4消息)。又例如，LLOF定义Nllof_NGAP message_transfer服务用于传输NGAP消息(即，NG-RAN和AMF之间的N2消息)等。再例如，定义Nllof_GTP-C message_transfer用于传输GTP-C消息(即，AMF和MME之间的N26消息)。也可以理解为，LLOF具备为SMF转发消息的能力，或者，LLOF支持为SMF转发消息。例如，LLOF可以通过Nllof_PFCP message_transfer为SMF转发请求消息#4。在另一种可能的实现方式中，LLOF仍然可以定义一个相同的服务名称，统一各种不同的PFCP请求消息，例如，LLOF使用相同的服务名称Nllof_message_transfer提供消息转发服务。此时，LLOF需要进一步定义该消息中的服务参数，从而使得可以通过该服务参数区分不同的接口消息类型。假设，如果LLOF使用相同的服务名称Nllof_message_transfer，则需要定义30个服务参数。例如，参数#1～服务参数#10可以指示出服务用于传输SMF和UPF之间的N4消息。又例如，参数#11～服务参数#20可以指示出服务用于传输NG-RAN和AMF之间的N2消息。又例如，参数#21～服务参数#30可以指示出服务用于传输AMF和MME之间的N26消息。
本申请中，请求消息#2可以通过LLOF的服务化接口传输。例如，请求消息#2可以是封装为HHTP格式的消息。
在一种可能的实现方式中，UPF的信息可以用于选择目标UPF。例如，UPF的信息可以是UPF的地址信息，和/或，UPF的参数信息。其中，UPF的地址信息例如可以是UPF的IP地址信息，或者，全限定域名(fully qualified domain name，FQDN)等信息。 UPF的参数信息例如可以是数据网络名称(data network name，DNN)、网络切片选择辅助信息(network slice selection assistance information，NSSAI)。例如，LLOF可以根据UPF的参数信息选择目标UPF，并且确定UPF的IP地址。在另一种可能的实现方式中，UPF的信息可以理解为，UPF为会话分配的UP F-SEID。应理解，本申请中，CP F-SEID和UP F-SEID可以标识一个会话，也可以理解为，一对用户面F-SEID和控制面F-SEID可以标识一个会话。
本申请中，PFCP会话消息包括PFCP头和一个或者多个IE。其中，IE中可以包括CP F-SEID#1。IE还可以是创建数据包检测规则、创建Qos实施规则、创建Qos实施规则中的一个或者多个。例如，PFCP会话消息可以为PFCP会话建立消息(即，PFCP session establishment消息)。又例如，PFCP会话消息可以为PFCP会话修改消息(即，PFCP sessionmodification)。再例如，PFCP会话消息可以为PFCP会话删除请求消息(即，PFCP session deletion request消息)，等等。本申请中，对PFCP会话消息的具体名称，不予限定，具体的可以参见TS29.244中7.3章。
本申请中，LLOF可以提供转发消息的服务，例如，该服务可以定义为Nllof_message_transfer。具体的，LLOF还可以为不同类型的非服务化消息提供不同的消息转发服务。例如，定义Nllof_PFCP message_transfer用于传输PFCP会话消息(即，传输SMF和UPF之间的N4消息)。又例如，LLOF定义Nllof_NGAP message_transfer服务用于传输NGAP消息(即，NG-RAN和AMF之间的N2消息)等。再例如，定义Nllof_GTP-C message_transfer用于传输GTP-C消息(即，AMF和MME之间的N26消息)。也可以理解为，LLOF具备为SMF转发消息的能力，或者，LLOF支持为SMF转发消息。例如，LLOF可以通过Nllof_PFCP message_transfer为SMF转发请求消息#2。
可选的，如果LLOF可以为每个不同类型的非服务化消息定义不同的服务(例如，LLOF定义Nllof_PFCP message_transfer服务、Nllof_NGAP message_transfer服务、Nllof_GTP-C message_transfer服务)，则SMF#1在请求LLOF发送非服务化消息时，LLOF可以根据该请求消息#2的名称确定非服务化消息的类型。例如，如果请求消息#2的消息名称为Nllof_PFCP message_transfer，LLOF可以确定为N4接口消息类型。又例如，如果请求消息#2的消息名称为Nllof_NGAP message_transfer，LLOF可以确定为N2接口消息类型。再例如，如果请求消息#2的消息名称为Nllof_GTP-C message_transfer，LLOF可以确定为N26接口消息类型。
可选的，如果LLOF没有为每个不同类型的非服务化消息定义不同的服务，例如，LLOF使用Nllof_message_transfer服务为SMF转发请求消息#2。此时，请求消息#2中可以携带指示信息#1，该指示信息#1用于指示非服务化消息的类型。例如，指示信息#1为消息类型字段。例如，指示信息#1可以指示该非服务化消息为N2接口消息类型。又例如，指示信息#1可以指示该非服务化消息为N4接口消息类型。再例如，指示信息#1可以指示该非服务化消息为N26接口消息类型。
步骤805，LLOF解析请求消息#2，并对PFCP会话消息进行封装。
例如，可以按照图3示出的协议栈的对依次PFCP会话消息进行封装。即依次对PFCP会话消息进行UDP报头封装以及IP报头封装。示例性的，LLOF为IE封装上PFCP报头，得到PFCP会话消息。然后，UDP层可以继续对PFCP会话消息采用UDP报头进行封装， UDP的源端口可以是LLOF分配的一个UDP端口号，例如，为UDP端口号#1；UDP目的端口为端口号#8805。接着IP层可以采用IP报头对UDP层的消息进行封装，IP报头的源IP地址为LLOF的IP地址，目的IP地址为UPF#1的IP地址。
步骤806，LLOF向UPF#1发送封装后的PFCP会话消息。对应的，UPF#1接收该封装后的PFCP会话消息。
例如，LLOF可以根据UPF的信息(例如，UPF的地址信息，和/或，UPF的参数信息)确定目标UPF为UPF#1，并向UPF#1发送封装后的PFCP会话消息，封装后的PFCP会话消息中目的地址为UPF#1的IP地址。
步骤807，UPF#1解析封装后的PFCP会话消息，并且分配UP F-SEID。
例如，UPF#1可以先解析IP报头，然后解析UDP报头，最后解析PFCP报头和IE。并且，UPF#1可以基于PFCP会话消息的名称分配UP F-SEID#8。
假设，UPF#1接受PFCP会话消息中的IE(即，PFCP会话消息中的各种N4规则(N4rule))，则UPF#1可以存储PFCP会话消息中包含的CP F-SEID#1以及N4rule，并向LLOF发送响应消息，响应消息中包含“成功”指示信息。若UPF#1只接受部分N4rule，或者，若UPF#1全部不接受N4rule，则UPF#1向LLOF发送的响应消息中包含“错误原因”(也可以理解为“原因值”)指示信息。换句话说，UPF#1向LLOF发送的响应消息中包含指示信息#2，该指示信息是对PFCP会话消息的响应。例如，该指示信息可以为拒绝“原因值”指示信息，或者，“成功”指示信息。
示例性的，该响应消息也可以是先封装为PFCP会话消息，PFCP会话消息包含PFCP会话消息头和一个或多个IE。
针对情况(1)，在一种可能的实现方式中，PFCP消息头中可以包括SEID#1；在另一种可能的实现方式中，PFCP会话消息头中可以包括CP F-SEID#1，PFCP会话消息IE中包括UP F-SEID。
针对情况(2)，在一种可能的实现方式中，UPF#1可以将UP F-SEID#8和CP F-SEID#2封装在IE中；在另一种可能的实现方式中，PFCP消息头中可以包括SEID#2，PFCP会话消息的IE中可以包括UP F-SEID#8；在又一种可能的实现方式中，PFCP会话消息头中可以包括CP F-SEID#2，PFCP会话消息的IE中可以包括UP F-SEID#8。
然后，再使用UDP报头对PFCP会话消息进行封装，例如，UDP报头的源端口的端口号为端口号#8805，UDP目的端口的端口号为端口号#1。接着使用IP报头进行封装，例如，IP报头的源IP地址为UPF的IP地址，IP报头的目的IP地址为LLOF的IP地址。
步骤808，UPF#1向LLOF发送封装后的响应消息#2。对应的LLOF接收响应消息#2。
步骤809，LLOF解析响应消息#2，获得CP F-SEID#1，并且根据保存SMF与CP F-SEID之间的对应关系确定对应的SMF。
例如，LLOF可以依次解析IP报头、UDP报头、PFCP报头。在一种可能的实现方式中，在成功解析PFCP会话消息报头后获得SEID#1，如前所述，LLOF可以基于SEID#1和自身的IP地址获得CP F-SEID#1。如步骤801中的描述，由于LLOF上保存了SMF与CP F-SEID的对应关系，此时，LLOF可以根据该对应关系确定目标SMF为SMF#1。
步骤810，LLOF向SMF#1发送响应消息#3。
由于，本申请中LLOF可以提供消息转发服务，例如，LLOF可以基于Nllof_ Message_Notify服务，向SMF#1发送响应消息#3。该响应消息#3中携带指示信息#2和UP F-SEID#8。
示例性的，该响应消息#3可以是HTTP格式的消息，或者，也可以理解为，可以采用服务化接口协议传输响应消息#3。
假设，将上述步骤801～步骤810中理解为N4会话建立过程，即，PFCP会话消息为PFCP session establishment消息，则下述步骤811～815可以理解为N4会话修改过程或N4会话释放过程。
可选的，步骤811，SMF向LLOF发送N4会话修改请求消息#1。对应的，LLOF接收来自SMF的会话修改请求消息#1。
例如，该N4会话修改请求消息#1可以为PFCP session modification消息。该PFCP会话修改消息头中包含UP F-SEID#8。例如，该PFCP会话修改消息的IE中可以是N4会话消息的一些更新规则，等等。
例如，该N4会话修改请求消息#1可以通过服务化接口传输。具体的，该N4会话修改请求消息#1可以封装为HHTP格式的消息。
可选的，步骤812，LLOF根据N4会话修改请求消息#1，确定目标UPF。
例如，LLOF可以根据该PFCP会话修改消息头中包含UP F-SEID#8，确定目标UPF为UPF#1。
可选的，步骤813，LLOF向UPF#1发送N4会话修改请求消息#2。对应的，UPF#1接收来自LLOF的会话修改请求消息#2。
例如，该会话修改请求消息#2为PFCP会话修改消息。例如，该PFCP会话修改消息的IE中可以是N4会话消息的一些更新规则，等等。可选的，该PFCP会话修改消息头中可以包含CP F-SEID#1。
例如，LLOF可以通过N4接口向UPF#1发送N4会话修改请求消息。
可选的，步骤814，UPF#1向LLOF发送会话修改响应消息#1。对应的LLOF接收会话修改响应消息#1。
假设，UPF#1接受会话修改请求消息中的IE(即，PFCP会话修改消息中的各种N4规则(N4rule))，则UPF#1可以向LLOF发送响应消息。该响应消息中包含指示信息#3，例如，UPF接收IE中的全部N4rule，则该指示信息#3可以为“成功”指示信息。又例如，若UPF#1只接受部分N4rule，或者，若UPF#1全部不接受N4rule，则UPF#1向LLOF发送的响应消息中包含“错误原因”(也可以理解为“原因值”)指示信息。
例如，会话修改响应消息包含PFCP会话修改消息头和一个或多个IE。在一种可能的实现方式中，PFCP消息头中可以包括LLOF为SMF分配的SEID#1。在另一种可能的实现方式中，PFCP消息头中可以包括LLOF为SMF分配的CP F-SEID#1。这里响应消息与会话建立的响应消息携带信息是一致的以及LLOF收到后的处理也是一致的。
可选的，步骤815，LLOF解析会话修改响应消息#1，获得CP F-SEID#1，并且根据保存的SMF与CP F-SEID之间的对应关系确定对应的SMF。
例如，LLOF可以依次解析IP报头、UDP报头、PFCP报头。在成功解析PFCP会话修改消息报头后获得SEID#1，如前所述，LLOF可以基于SEID#1和自身的IP地址获得CP F-SEID#1。如步骤801中的描述，由于LLOF上保存了SMF与CP F-SEID的对应关系， 此时，LLOF可以根据该对应关系确定目标SMF为SMF#1。
可选的，步骤816，LLOF向SMF#1发送会话修改响应消息。
由于，本申请中LLOF可以提供消息转发服务，例如，LLOF可以基于Nllof_Message_Notify服务，向SMF#1发送会话修改响应消息。
需要说明的是，本申请中，类似Nllof_message_transfer、Nllof_Fseid_allocation等消息均为消息名称的一种示例，不予限定。
基于上述技术方案，本申请提出了一种包含LLOF的新的网络服务化架构，LLOF与SMF之间可以采用服务化接口传输消息，使得SMF彻底实现服务化。并且，LLOF可以提供分配CP F-SEID、转发消息等服务，保障SMF与UPF之间的通信。另外，由于LLOF上保存了会话上下文信息，还可以使得SMF发生故障时，LLOF可以快速选择新的SMF，向新选择的SMF传输会话上下文，为会话提供服务，减小通信时延，保障用户的业务体验。
可以理解，本申请实施例中的方法700、方法800中的例子仅仅是为了便于本领域技术人员理解本申请实施例，并非要将本申请实施例限于例示的具体场景。本领域技术人员根据方法700、方法800中的例子，显然可以进行各种等价的修改或变化，这样的修改或变化也落入本申请实施例的范围内。
还可以理解，本申请的各实施例中的一些可选的特征，在某些场景下，可以不依赖于其他特征，也可以在某些场景下，与其他特征进行结合，不作限定。
还可以理解，本申请中描述的各个实施例可以为独立的方案，也可以根据内在逻辑进行组合，这些方案都落入本申请的保护范围中。并且实施例中出现的各个术语的解释或说明可以在各个实施例中互相参考或解释，对此不作限定。
应该理解，本申请中的预定义可以理解为定义、预先定义、存储、预存储、预协商、预配置、固化、或预烧制。
可以理解，在本申请中，“在…情况下”、“若”以及“如果”均指在某种客观情况下装置会做出相应的处理，并非是限定时间，且也不要求装置实现时一定要有判断的动作，也不意味着存在其它限定。
可以理解，本文中术语“和/或”，描述关联对象的关联关系，表示可以存在三种关系，例如，A和/或B，可以表示：单独存在A，同时存在A和B，单独存在B的情况，其中A,B可以是单数或者复数。在本申请的文字描述中，字符“/”，一般表示前后关联对象是一种“或”的关系；在本申请的公式中，字符“/”，表示前后关联对象是一种“相除”的关系。
上述主要从各个节点之间交互的角度对本申请实施例提供的方案进行了介绍。可以理解的是，各个节点，例如链路负载编排功能网元、会话管理功能网元、用户面功能网元，为了实现上述功能，其包含了执行各个功能相应的硬件结构和/或软件模块。本领域技术人员应该可以意识到，结合本文中所公开的实施例描述的各示例的单元及算法步骤，本申请能够以硬件或硬件和计算机软件的结合形式来实现。某个功能究竟以硬件还是计算机软件驱动硬件的方式来执行，取决于技术方案的特定应用和设计约束条件。专业技术人员可以对每个特定的应用来使用不同方法来实现所描述的功能，但是这种实现不应认为超出本申请的范围。
可以理解的是，为了实现上述实施例中功能，链路负载编排功能网元包括了执行各个功能相应的硬件结构和/或软件模块。本领域技术人员应该很容易意识到，结合本申请中所公开的实施例描述的各示例的单元及方法步骤，本申请能够以硬件或硬件和计算机软件相结合的形式来实现。某个功能究竟以硬件还是计算机软件驱动硬件的方式来执行，取决于技术方案的特定应用场景和设计约束条件。
图9和图10为本申请的实施例提供的可能的消息路由装置的结构示意图。这些消息路由装置可以用于实现上述方法实施例中链路负载编排功能网元的功能，因此也能实现上述方法实施例所具备的有益效果。
如图9所示，消息路由装置100包括处理单元110和收发单元120。消息路由装置100用于实现上述图8中所示的方法实施例中链路负载编排功能网元的功能。
当消息路由装置100用于实现图8所示的方法实施例中链路负载编排功能网元的功能时，收发单元120用于接收来自会话管理功能网元的第一消息，第一消息携带用户面功能网元的信息和会话消息，第一消息用于请求转发会话消息，其中，第一消息通过该装置的服务化接口传输，处理单元110用于根据用户面功能网元的信息，确定目标用户面功能网元，收发单元120还用于通过非服务化接口向目标用户面功能网元发送会话消息。
在一种可能的实现方式中，所述收发单元120用于接收来自会话管理功能网元的第二消息，第二消息用于请求获取会话管理功能网元对应的CP F-SEID；所述处理单元110用于根据第二消息，为会话管理功能网元分配对应的CP F-SEID；所述收发单元120用于向会话管理功能网元发送所述CP F-SEID。
在一种可能的实现方式中，所述处理单元110用于根据所述第一消息，为所述会话管理功能网元分配对应的控制面全限定会话终点标识符CP F-SEID，所述处理单元110用于将所述CP F-SEID封装在会话消息的信息元素IE中。
在一种可能的实现方式中，所述处理单元110用于保存所述会话管理功能网元与所述CP F-SEID之间的映射关系。
在一种可能的实现方式中，所述处理单元110用于封装所述会话消息；所述收发单元120向所述目标用户面功能网元发送所述会话消息，包括：所述收发单元120用于向目标用户面功能网元发送封装后的会话消息。
在一种可能的实现方式中，所述收发单元120用于接收来自目标用户面功能网元的第三消息，第三消息携带会话终点标识符SEID、用户面全限定会话终点标识符UP F-SEID和指示信息，其中，所述指示信息用于响应所述会话消息；所述处理单元110用于根据所述SEID，确定所述CP F-SEID；所述处理单元110根据所述CP F-SEID与所述会话管理功能网元的映射关系，控制所述收发单元120向所述会话管理功能网元发送第四消息，第四消息携带所述UP F-SEID和所述指示信息。
有关上述处理单元110和收发单元120更详细的描述可以直接参考图8所示的方法实施例中相关描述直接得到，这里不加赘述。
如图10所示，消息路由装置200包括处理器210和接口电路220。处理器210和接口电路220之间相互耦合。可以理解的是，接口电路220可以为收发器或输入输出接口。可选的，消息路由装置200还可以包括存储器230，用于存储处理器210执行的指令或存储处理器210运行指令所需要的输入数据或存储处理器210运行指令后产生的数据。
当消息路由装置200用于实现图8所示的方法时，处理器210用于实现上述处理单元110的功能，接口电路220用于实现上述收发单元120的功能。
应理解，图10示出的处理器可以包含至少一个处理器，接口电路也可以包括多个接口电路。
上述提供的任一种装置中相关内容的解释及有益效果均可参考上文提供的对应的方法实施例，此处不再赘述。
可以理解的是，本申请的实施例中的处理器可以是中央处理单元(Central Processing Unit，CPU)，还可以是其它通用处理器、数字信号处理器(Digital Signal Processor，DSP)、专用集成电路(Application Specific Integrated Circuit，ASIC)、现场可编程门阵列(Field Programmable Gate Array，FPGA)或者其它可编程逻辑器件、晶体管逻辑器件，硬件部件或者其任意组合。通用处理器可以是微处理器，也可以是任何常规的处理器。
根据本申请实施例提供的方法，本申请还提供一种计算机程序产品，该计算机程序产品上存储有计算机程序代码，当该计算机程序代码在计算机上运行时，使得该计算机执行方法700、方法800实施例中由链路负载编排功能网元执行的方法。
根据本申请实施例提供的方法，本申请还提供一种计算机可读介质，该计算机可读介质存储有程序代码，当该程序代码在计算机上运行时，使得该计算机执行上述实施例方法700、方法800中由链路负载编排功能网元执行的方法。
根据本申请实施例提供的方法，本申请还提供一种通信系统，该通信系统包括终端和网络设备。该终端用于执行上述方法700、方法800中链路负载编排功能网元对应的步骤。
可选的，该通信系统中还可以包括用户面功能网元和会话管理功能网元。
本申请的实施例中的方法步骤可以在硬件中实现，也可以在可由处理器执行的软件指令中实现。软件指令可以由相应的软件模块组成，软件模块可以被存放于随机存取存储器、闪存、只读存储器、可编程只读存储器、可擦除可编程只读存储器、电可擦除可编程只读存储器、寄存器、硬盘、移动硬盘、CD-ROM或者本领域熟知的任何其它形式的存储介质中。一种示例性的存储介质耦合至处理器，从而使处理器能够从该存储介质读取信息，且可向该存储介质写入信息。存储介质也可以是处理器的组成部分。处理器和存储介质可以位于ASIC中。另外，该ASIC可以位于链路负载编排功能网元中。处理器和存储介质也可以作为分立组件存在于链路负载编排功能网元中。
在上述实施例中，可以全部或部分地通过软件、硬件、固件或者其任意组合来实现。当使用软件实现时，可以全部或部分地以计算机程序产品的形式实现。所述计算机程序产品包括一个或多个计算机程序或指令。在计算机上加载和执行所述计算机程序或指令时，全部或部分地执行本申请实施例所述的流程或功能。所述计算机可以是通用计算机、专用计算机、计算机网络、网络设备、用户设备或者其它可编程装置。所述计算机程序或指令可以存储在计算机可读存储介质中，或者从一个计算机可读存储介质向另一个计算机可读存储介质传输，例如，所述计算机程序或指令可以从一个网站站点、计算机、服务器或数据中心通过有线或无线方式向另一个网站站点、计算机、服务器或数据中心进行传输。所述计算机可读存储介质可以是计算机能够存取的任何可用介质或者是集成一个或多个可用介质的服务器、数据中心等数据存储设备。所述可用介质可以是磁性介质，例如，软盘、硬盘、磁带；也可以是光介质，例如，数字视频光盘；还可以是半导体介质，例如，固态 硬盘。该计算机可读存储介质可以是易失性或非易失性存储介质，或可包括易失性和非易失性两种类型的存储介质。
在本申请的各个实施例中，如果没有特殊说明以及逻辑冲突，不同的实施例之间的术语和/或描述具有一致性、且可以相互引用，不同的实施例中的技术特征根据其内在的逻辑关系可以组合形成新的实施例。
可以理解的是，在本申请的实施例中涉及的各种数字编号仅为描述方便进行的区分，并不用来限制本申请的实施例的范围。上述各过程的序号的大小并不意味着执行顺序的先后，各过程的执行顺序应以其功能和内在逻辑确定。

Claims (18)

  1. 一种消息路由方法，其特征在于，包括：
    链路负载编排功能网元接收来自会话管理功能网元的第一消息，所述第一消息携带用户面功能网元的信息和会话消息，所述第一消息用于请求转发所述会话消息，其中，所述第一消息通过所述链路负载编排功能网元的服务化接口传输；
    所述链路负载编排功能网元根据所述用户面功能网元的信息，确定目标用户面功能网元；
    所述链路负载编排功能网元通过非服务化接口向所述目标用户面功能网元发送所述会话消息。
  2. 根据权利要求1所述的方法，其特征在于，所述会话消息为数据包转发控制协议PFCP会话消息。
  3. 根据权利要求1或2所述的方法，其特征在于，所述会话消息包括信息元素IE，所述IE包括与所述会话管理功能网元对应的控制面全限定会话终点标识符CP F-SEID。
  4. 根据权利要求3所述的方法，其特征在于，在所述链路负载编排功能网元接收来自会话管理功能网元的第一消息之前，所述方法还包括：
    所述链路负载编排功能网元接收来自会话管理功能网元的第二消息，所述第二消息用于请求获取所述会话管理功能网元对应的CP F-SEID；
    所述链路负载编排功能网元根据所述第二消息，为所述会话管理功能网元分配对应的CP F-SEID；
    所述链路负载编排功能网元向所述会话管理功能网元发送所述CP F-SEID。
  5. 根据权利要求3所述方法，其特征在于，所述CP F-SEID为所述会话管理功能网元分配的。
  6. 根据权利要求1或2所述的方法，其特征在于，所述方法还包括：
    所述链路负载编排功能网元根据所述第一消息，为所述会话管理功能网元分配对应的控制面全限定会话终点标识符CP F-SEID；
    所述链路负载编排功能网元将所述CP F-SEID封装在所述会话消息的信息元素IE中。
  7. 根据权利要求3至6中任一项所述的方法，其特征在于，所述方法还包括：
    所述链路负载编排功能网元保存所述会话管理功能网元与所述CP F-SEID之间的映射关系。
  8. 根据权利要求7中所述的方法，其特征在于，所述方法还包括：
    所述链路负载编排功能网元封装所述会话消息；
    所述链路负载编排功能网元向所述目标用户面功能网元发送所述会话消息，包括：
    所述链路负载编排功能网元向所述目标用户面功能网元发送封装后的所述会话消息。
  9. 根据权利要求8所述的方法，其特征在于，所述方法还包括：
    所述链路负载编排功能网元接收来自所述目标用户面功能网元的第三消息，所述第三消息携带会话终点标识符SEID、用户面全限定会话终点标识符UP F-SEID和指示信息，其中，所述指示信息用于响应所述会话消息；
    所述链路负载编排功能网元根据所述SEID，确定所述CP F-SEID；
    所述链路负载编排功能网元根据所述CP F-SEID与所述会话管理功能网元的映射关系，向所述会话管理功能网元发送第四消息，所述第四消息携带所述UP F-SEID和所述指示信息。
  10. 根据权利要求9所述的方法，其特征在于，
    所述第三消息的报头包括所述SEID，所述第三消息的IE包括所述UP F-SEID。
  11. 根据权利要求7所述的方法，其特征在于，所述方法还包括：
    所述链路负载编排功能网元接收来自所述目标用户面功能网元的第三消息，所述第三消息的IE包括所述UP F-SEID、所述CP F-SEID和指示信息，其中，所述指示信息用于响应所述会话消息；
    所述链路负载编排功能网元根据所述CP F-SEID与所述会话管理功能网元的映射关系，向所述会话管理功能网元发送第四消息，所述第四消息携带所述UP F-SEID和所述指示信息。
  12. 一种消息路由装置，包括用于执行如权利要求1至11中的任一项所述方法的模块。
  13. 一种消息路由装置，其特征在于，包括处理器和接口电路，所述接口电路用于接收来自所述装置之外的其它通信装置的信号并传输至所述处理器或将来自所述处理器的信号发送给所述装置之外的其它通信装置，所述处理器通过逻辑电路或执行代码指令用于实现如权利要求1至11中任一项所述的方法。
  14. 一种消息路由装置，其特征在于，包括：处理器，所述处理器与存储器耦合，所述存储器用于存储指令，当所述指令被所述处理器执行时，使得所述装置执行如权利要求1至11中任一项所述的方法。
  15. 一种计算机可读存储介质，其特征在于，所述存储介质中存储有指令，当所述指令被通信装置执行时，实现如权利要求1至11中任一项所述的方法。
  16. 一种计算机程序产品，其特征在于，当其在计算机上运行时，使得计算机执行如权利要求1至11中任一项所述的方法。
  17. 一种通信系统，其特征在于，包括至少一个用于执行如权利要求1至11中的任一项所述的装置。
  18. 根据权利要求17所述的通信系统，其特征在于，所述通信系统还包括会话管理功能网元和用户面功能网元。
PCT/CN2023/096497 2022-07-30 2023-05-26 消息路由方法和装置 WO2024027299A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN202210912571.7 2022-07-30
CN202210912571.7A CN117528706A (zh) 2022-07-30 2022-07-30 消息路由方法和装置

Publications (1)

Publication Number Publication Date
WO2024027299A1 true WO2024027299A1 (zh) 2024-02-08

Family

ID=89748297

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2023/096497 WO2024027299A1 (zh) 2022-07-30 2023-05-26 消息路由方法和装置

Country Status (2)

Country Link
CN (1) CN117528706A (zh)
WO (1) WO2024027299A1 (zh)

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2020173137A1 (zh) * 2019-02-28 2020-09-03 华为技术有限公司 一种数据传输方法、相关设备、程序产品以及存储介质
CN112671567A (zh) * 2020-12-16 2021-04-16 中盈优创资讯科技有限公司 一种基于服务化接口的5g核心网拓扑发现方法及装置
WO2021248275A1 (en) * 2020-06-08 2021-12-16 Telefonaktiebolaget Lm Ericsson (Publ) Method and apparatus for network interworking

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2020173137A1 (zh) * 2019-02-28 2020-09-03 华为技术有限公司 一种数据传输方法、相关设备、程序产品以及存储介质
WO2021248275A1 (en) * 2020-06-08 2021-12-16 Telefonaktiebolaget Lm Ericsson (Publ) Method and apparatus for network interworking
CN112671567A (zh) * 2020-12-16 2021-04-16 中盈优创资讯科技有限公司 一种基于服务化接口的5g核心网拓扑发现方法及装置

Also Published As

Publication number Publication date
CN117528706A (zh) 2024-02-06

Similar Documents

Publication Publication Date Title
US20230093339A1 (en) Session Management Method, Apparatus, and System
US11871273B2 (en) Systems and methods for user plane handling
KR102469973B1 (ko) 통신 방법 및 장치
WO2020224618A1 (zh) 一种寻址方法、通信装置及系统
EP4106480A1 (en) Communication method and apparatus
US20200280892A1 (en) Session context handling method, network element, and terminal device
US20230254922A1 (en) Multipath transmission method and communication apparatus
WO2021212939A1 (zh) 通信方法、装置及系统
WO2022171051A1 (zh) 一种通信方法和通信装置
US20230156833A1 (en) Packet Forwarding Method, Apparatus, and System
WO2022199451A1 (zh) 会话切换的方法和装置
CN111491370B (zh) 一种通信方法、网元、系统及存储介质
WO2023024931A1 (zh) 用于设备间通信的方法和装置
US20220225463A1 (en) Communications method, apparatus, and system
KR20240060670A (ko) 통신 방법 및 장치
WO2024027299A1 (zh) 消息路由方法和装置
WO2023207637A1 (zh) 通信方法及装置
WO2023197737A1 (zh) 报文发送方法、pin管理方法、通信装置及通信系统
WO2023143212A1 (zh) 一种通信方法及装置
WO2023116556A1 (zh) 会话切换的方法和装置
WO2023066207A1 (zh) 一种通信方法及装置
WO2022170798A1 (zh) 确定策略的方法和通信装置
WO2022068336A1 (zh) 路由信息更新方法、通信装置及存储介质
US20240155325A1 (en) Information obtaining method and apparatus, and system
WO2023061207A1 (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: 23849009

Country of ref document: EP

Kind code of ref document: A1