CN117528460A

CN117528460A - Reliable message transmission method and device

Info

Publication number: CN117528460A
Application number: CN202210912588.2A
Authority: CN
Inventors: 姚琦; 宗在峰
Original assignee: Huawei Technologies Co Ltd
Current assignee: Huawei Technologies Co Ltd
Priority date: 2022-07-30
Filing date: 2022-07-30
Publication date: 2024-02-06

Abstract

The application provides a method and a device for reliably transmitting a message, and provides a new network servitization architecture containing LLOF, wherein a servitization interface is adopted between LLOF and a first network element to transmit a non-servitization message, so that the first network element thoroughly realizes servitization. And LLOF can confirm that the non-service message is transmitted reliably through the non-service interface, so that the reliable transmission of the non-service message is ensured, and the communication performance is ensured.

Description

Reliable message transmission method and device

Technical Field

The embodiment of the application relates to the field of communication, and more particularly, to a reliable message transmission method and device.

Background

Currently, the third generation partnership project (3rd generation partnership project,3Gpp) has proposed a network servitization architecture in order to improve the reliability and flexibility of the network. For example, in the 5G network servitization architecture shown in fig. 1, the session management function network element (session management function, SMF) needs to support not only a servitization interface (for example, a servitization interface between the SMF and the access and mobility management function network element (access and mobility management function, AMF), the policy control management function network element (policy control function, PCF), etc.), but also a non-servitization interface (for example, a non-servitization interface is an N4 interface between the SMF and the user plane function network element (user plane function, UPF)), and similar problems exist in the AMF.

Since, on the non-serviced interface, there is a binding relationship between the user context and the physical interface. For example, SMF needs to retain context information of a user or context information associated with a transport layer. At this time, if the SMF fails, the performance of the UPF may also be affected, e.g., the UPF may need to reestablish a session with a new SMF, transmit context information, etc. In other words, in the current 5G network service architecture, the service function of the SMF is not thorough, so that the SMF fault recovery or the coupling relationship between the SMF and the UPF exists during the expansion/contraction of the SMF, which is not flexible enough, and the advantages of the service architecture cannot be fully exerted.

In view of this, how to achieve the SMF and AMF thoroughly and achieve reliable information transmission is a technical problem that needs to be solved at present.

Disclosure of Invention

The embodiment of the application provides a reliable message transmission method, and provides a new network servitization architecture containing LLOF, wherein a servitization interface is adopted between LLOF and a first network element to transmit a non-servitization message, so that the first network element thoroughly realizes servitization. And LLOF can confirm that the non-service message is transmitted reliably through the non-service interface, so that the reliable transmission of the non-service message is ensured, and the communication performance is ensured.

In a first aspect, a communication method is provided, which may be performed by a link load orchestration function network element, or may also be performed by a component part (e.g. a chip or a circuit) of the link load orchestration function network element, which is not limited.

The method comprises the following steps: the method comprises the steps that a network element with a link load arranging function receives a first message from a first network element, wherein the first message carries a non-service message, and the first message is used for requesting forwarding of the non-service message, and the first message is transmitted through a service interface; the network element of the link load arranging function determines that the non-service message is reliably transmitted through a non-service interface; the link load orchestration function network element sends the non-serviced message to the second network element over the non-serviced interface.

In one possible implementation, the link load orchestration function network element determines that the non-serviced message is reliably transmitted over a non-serviced interface, including: the network element of the link load arranging function determines that the non-service message is reliably transmitted through an N2 interface; or the network element of the link load arranging function determines that the non-service message is reliably transmitted through the N4 interface; alternatively, the link load orchestration function network element determines that the non-serviced message is reliably transmitted over the N26 interface.

It is also understood that in this application, messages transmitted on some non-serviced interfaces may need to be reliably transmitted, and messages transmitted on other non-serviced interfaces may not need to be reliably transmitted. In other words, not all messages transmitted over the non-serviced interface are required to be reliably transmitted in this application. For example, in one possible implementation, a portion of the message transmitted over the N2, N4, or N26 interface requires a reliability transmission, and a portion of the message does not require a reliability transmission. In another possible implementation, the messages transmitted over the N4 interface need to be reliably transmitted, and the messages transmitted over the N2 interface need not be reliably transmitted.

In one possible implementation manner, the first message carries first indication information, where the first indication information is used to indicate reliable transmission of the non-service message, and the link load arrangement function network element determines that the non-service message is reliably transmitted through the non-service interface, and includes: and the link load arranging function network element determines to reliably transmit the non-service message through the non-service interface according to the first indication information.

In one possible implementation, the link load orchestration function network element determines that a further non-serviced message is reliably transmitted over a non-serviced interface, including: the link load arrangement function network element determines to reliably transmit the non-serviced message through the non-serviced interface according to the name of the first message.

In one possible implementation manner, the first message carries second indication information, where the second indication information is used to indicate the type of the non-service message, and the link load arranging function network element determines that the non-service message is reliably transmitted through the non-service interface, and includes: the link load orchestration function network element determines to reliably transmit the non-serviced message through the non-serviced interface according to the second indication information.

In one possible implementation, the non-servitized message type is one or more of the following types: n2 interface message type, N4 interface message type, N26 interface message type.

Based on the above technical scheme, in the application, the LLOF can determine whether to perform reliable transmission on the non-service message in various ways, so that the network resources are saved for the message which does not need to ensure reliable transmission, and the reliable transmission of the message is ensured and the user experience is ensured for the message which needs to ensure reliable transmission. .

In one possible implementation manner, the first network element is a session management function network element, the second network element is a user plane function network element, and the non-service interface is an N4 interface; or the first network element is an access and mobility management network element, the second network element is a mobility management entity, and the non-service interface is an N26 interface; the first network element is an access and mobility management network element, the second network element is a wireless access network, and the non-service interface is an N2 interface.

Based on the above technical scheme, in the application, the messages transmitted on the interfaces can be reliably transmitted, so that the communication quality is ensured, and the N4 interface between the SMF and the UPF, the N2 interface between the AMF and the RAN and the N26 interface between the AMF and the MME are provided.

In one possible implementation, the link load orchestration function network element determines that the non-serviced message is reliably transmitted, including: the network element of the link load arranging function allocates a first serial number for the non-service message; the network element of the link load arranging function encapsulates the non-service message, wherein the encapsulated non-service message comprises a first serial number; the link load orchestration function network element sends a non-servitization message to the second network element, comprising: the link load arrangement functional network element sends the encapsulated non-servitized message to a second network element.

In one possible implementation, the method further includes: the link load arranging function network element receives a second message from a second network element, wherein the second message carries a second serial number; if the second sequence number is the same as the first sequence number, the link load arranging function network element determines that the non-service message is successfully sent; or if the second sequence number is different from the first sequence number, the link load arrangement function network element determines that the non-service message transmission fails.

In this application, "successful sending of the non-served message" may also be understood as the LLOF determines that retransmission of the non-served message is not required; in this application, "non-serviced message transmission failure" is also understood to mean that LLOF determines that retransmission of the non-serviced message is required.

Based on the above technical solution, in the present application, LLOF may determine whether the sending of the non-service message is successful by allocating a sequence number and determining whether the sequence number carried in the response message from the second network element is consistent with the sequence number allocated for the first time.

In one possible implementation, the method further includes: the network element of the link load arranging function starts a timer, and the duration of the timer is a first duration; if the link load arranging function network element receives the second message from the second network element before the timer is overtime, the link load arranging function network element determines that the non-service message is successfully transmitted; or if the timer is overtime, the link load arrangement functional network element does not receive the second message from the second network element, and the link load arrangement functional network element determines that the sending of the non-service message fails.

For example, LLOF may start a timer after the first message is sent.

In this application, the first duration may be predefined, or preconfigured, without limitation. In this application, the "first time period" may be understood as a period of time, for example; for another example, the "first time length" may be a time unit. For example, a "time unit" may be one or more radio frames, one or more subframes, one or more slots, one or more minislots, one or more symbols, and the like. Wherein the symbol may be an orthogonal frequency division multiplexing (orthogonal frequency division multiplexing, OFDM) symbol, a discrete fourier transform spread orthogonal frequency division multiplexing (discrete fourier transform spread spectrum orthogonal frequency division multiplexing, DFT-S-OFDM) symbol, or the like. For example, the first time may also be 1 second(s) or more seconds, 1 millisecond (ms) or more milliseconds, or the like.

Based on the above technical solution, in the present application, the LLOF may determine whether the sending of the non-service message is successful by starting a timer and determining whether a response message from the second network element is received within a timing duration. For example, if LLOF receives a response message from the second network element after the timer expires, LLOF determines that the non-serviced message transmission failed; for another example, if the LLOF still does not receive a response message from the second network element after the timer expires, the LLOF determines that the non-serviced message transmission failed.

In one possible implementation, the method further includes: if the retransmission times do not reach N when the link load arranging function network element receives the second message from the second network element, the link load arranging function network element determines that the non-service message is successfully transmitted; or if the retransmission times reach N, the link load arrangement function network element does not receive the second message from the second network element, and the link load arrangement function network element determines that the transmission of the non-service message fails.

Based on the above technical solution, in the present application, the LLOF may determine that the sending of the non-service message is successful by maintaining the number of retransmissions N, that is, if the number of retransmissions of the LLOF that receives the response message from the second network element does not reach N; if the LLOF does not reach N in the number of retransmissions of the response message received from the second network element, determining that the non-serviced message transmission fails.

In a second aspect, a message reliable transmission device is provided for performing the method in any of the possible implementations of the first aspect. In particular, the apparatus may comprise means and/or modules, such as a transceiver unit and/or a processing unit, for performing the method in any one of the possible implementations of the first aspect.

In one implementation, the apparatus orchestrates functional network elements for link loads. When the apparatus is a communication device, the communication unit may be a transceiver, or an input/output interface; the processing unit may be at least one processor. Alternatively, the transceiver may be a transceiver circuit. Alternatively, the input/output interface may be an input/output circuit.

In another implementation, the apparatus is a chip, a system-on-chip or a circuit for a link load orchestration functional network element. When the apparatus is a chip, a system-on-chip or a circuit for a communication device, the communication unit may be an input/output interface, an interface circuit, an output circuit, an input circuit, a pin, or a related circuit, etc. on the chip, the system-on-chip or the circuit; the processing unit may be at least one processor, processing circuit or logic circuit, etc.

In a third aspect, there is provided a message reliable transmission apparatus, the apparatus comprising: at least one processor configured to execute a computer program or instructions stored in a memory to perform a method according to any one of the possible implementations of the first aspect. Optionally, the apparatus further comprises a memory for storing a computer program or instructions. Optionally, the apparatus further comprises a communication interface through which the processor reads the computer program or instructions stored in the memory.

In one implementation, the apparatus orchestrates functional network elements for link loads.

In another implementation, the apparatus is a chip, a system-on-chip or a circuit for a link load orchestration functional network element.

In a fourth aspect, the present application provides a processor comprising: input circuit, output circuit and processing circuit. The processing circuit is configured to receive signals via the input circuit and to transmit signals via the output circuit, such that the processor performs the method of any one of the possible implementations of the first aspect.

In a specific implementation process, the processor may be one or more chips, the input circuit may be an input pin, the output circuit may be an output pin, and the processing circuit may be a transistor, a gate circuit, a flip-flop, various logic circuits, and the like. The input signal received by the input circuit may be received and input by, for example and without limitation, a transceiver, the output signal output by the output circuit may be output to and transmitted by, for example and without limitation, a transmitter, and the input circuit and the output circuit may be the same circuit, which functions as the input circuit and the output circuit, respectively, at different times. The embodiments of the present application do not limit the specific implementation manner of the processor and the various circuits.

The operations such as transmitting and acquiring/receiving, etc. related to the processor may be understood as operations such as outputting and receiving, inputting, etc. by the processor, or may be understood as operations such as transmitting and receiving by the radio frequency circuit and the antenna, if not specifically stated, or if not contradicted by actual function or inherent logic in the related description, which is not limited in this application.

In a fifth aspect, a processing device is provided that includes a processor and a memory. The processor is configured to read instructions stored in the memory and is configured to receive signals via the transceiver and to transmit signals via the transmitter to perform the method of any one of the possible implementations of the first aspect.

Optionally, the processor is one or more, and the memory is one or more.

Alternatively, the memory may be integrated with the processor or the memory may be separate from the processor.

In a specific implementation process, the memory may be a non-transient (non-transitory) memory, for example, a Read Only Memory (ROM), which may be integrated on the same chip as the processor, or may be separately disposed on different chips.

It should be appreciated that the related data interaction process, for example, transmitting the indication information, may be a process of outputting the indication information from the processor, and the receiving the capability information may be a process of receiving the input capability information by the processor. Specifically, the data output by the processor may be output to the transmitter, and the input data received by the processor may be from the transceiver. Wherein the transmitter and transceiver may be collectively referred to as a transceiver.

The processing device in the fifth aspect described above may be one or more chips. The processor in the processing device may be implemented in hardware or in software. When implemented in hardware, the processor may be a logic circuit, an integrated circuit, or the like; when implemented in software, the processor may be a general-purpose processor, implemented by reading software code stored in a memory, which may be integrated in the processor, or may reside outside the processor, and exist separately.

In a sixth aspect, a computer readable storage medium is provided, the computer readable medium storing program code for device execution, the program code comprising instructions for performing the method of any one of the possible implementations of the first aspect.

In a seventh aspect, there is provided a computer program product comprising instructions which, when run on a computer, cause the computer to perform the method of any one of the possible implementations of the first aspect.

In an eighth aspect, a chip system is provided, comprising a processor for calling and running a computer program from a memory, so that a device on which the chip system is installed performs the method in each implementation of the first aspect.

A ninth aspect provides a communication system comprising a link load orchestration function network element for performing any one of the possible implementations of the method of the first aspect.

In one possible implementation, the communication system further includes a first network element and a second network element.

Drawings

Fig. 1 is a schematic diagram of a 5G web-servitization architecture.

Fig. 2 is a schematic diagram of a 5G network server architecture according to the present application.

Fig. 3 is a schematic diagram of a format of a PFCP message.

Fig. 4 is a schematic diagram of a format of a PFCP message header.

Fig. 5 is a schematic flow chart diagram of a message reliable transmission method 500 provided herein.

Fig. 6 is a schematic block diagram of a message reliable transmission apparatus 100 provided herein.

Fig. 7 is a schematic block diagram of a message reliable transmission apparatus 200 provided herein.

Detailed Description

The technical solutions in the embodiments of the present application will be described below with reference to the accompanying drawings.

The wireless communication systems mentioned in this application include, but are not limited to: global system for mobile communications (global system of mobile communication, GSM), long term evolution (long term evolution, LTE) frequency division duplex (frequency division duplex, FDD) system, LTE time division duplex (time division duplex, TDD), LTE system, long term evolution-Advanced (LTE-a) system, next generation communication system (e.g., 6G communication system), a converged system of multiple access systems, or evolved system.

The technical solutions provided herein may also be applied to machine-type communication (machine type communication, MTC), inter-machine communication long term evolution technology (long term evolution-machine, LTE-M), device-to-device (D2D) networks, machine-to-machine (machine to machine, M2M) networks, internet of things (internet of things, ioT) networks, or other networks. The IoT network may include, for example, an internet of vehicles. The communication modes in the internet of vehicles system are generally called as vehicle to other devices (V2X, X may represent anything), for example, the V2X may include: vehicle-to-vehicle (vehicle to vehicle, V2V) communication, vehicle-to-infrastructure (vehicle to infrastructure, V2I) communication, vehicle-to-pedestrian communication (vehicle to pedestrian, V2P) or vehicle-to-network (vehicle to network, V2N) communication, etc.

Fig. 1 shows a schematic diagram of a 5G system (the 5th generation system,5GS) network server architecture, which may include the following network elements:

1. user Equipment (UE): may be referred to as a terminal device, access terminal, subscriber unit, subscriber station, mobile station, remote terminal, mobile device, user terminal, wireless communication device, user agent, or user equipment.

The terminal device may be a device that provides voice/data to a user, e.g., a handheld device with wireless connection, an in-vehicle device, etc. Currently, some examples of terminals are: examples of mobile phones, tablet computers, notebook computers, palm computers, mobile internet devices (mobile internet device, MID), virtual Reality (VR) devices, augmented reality (augmented reality, AR) devices, wireless terminals in industrial control (industrial control), wireless terminals in unmanned (self driving), wireless terminals in teleoperation (remote medical surgery), wireless terminals in smart grid (smart grid), wireless terminals in transportation security (transportation safety), wireless terminals in smart city (smart city), wireless terminals in smart home (smart home), cellular phones, cordless phones, session initiation protocol (session initiation protocol, SIP) phones, wireless local loop (wireless local loop, WLL) stations, personal digital assistants (personal digital assistant, PDAs), handheld devices with wireless communication functions, computing devices or other processing devices connected to wireless modems, terminal devices in 5G networks or terminals in future evolved public land mobile networks (public land mobile network, PLMN), and the like are not limited in this application.

By way of example, and not limitation, in embodiments of the present application, the terminal device may also be a wearable device. The wearable device can also be called as a wearable intelligent device, and is a generic name for intelligently designing daily wear by applying wearable technology and developing wearable devices, such as glasses, gloves, watches, clothes, shoes and the like. The wearable device is a portable device that is worn directly on the body or integrated into the clothing or accessories of the user. The wearable device is not only a hardware device, but also can realize a powerful function through software support, data interaction and cloud interaction. The generalized wearable intelligent device includes full functionality, large size, and may not rely on the smart phone to implement complete or partial functionality, such as: smart watches or smart glasses, etc., and focus on only certain types of application functions, and need to be used in combination with other devices, such as smart phones, for example, various smart bracelets, smart jewelry, etc. for physical sign monitoring.

In addition, in the embodiment of the application, the terminal device may also be a terminal device in an IoT system, where IoT is an important component of future information technology development, and the main technical feature is to connect the article with a network through a communication technology, so as to implement man-machine interconnection and an intelligent network for interconnection of the articles.

It should be noted that, some air interface technology (such as NR or LTE technology) may be used to communicate between the terminal device and the access network device. The terminal equipment and the terminal equipment can also communicate with each other by adopting a certain air interface technology (such as NR or LTE technology).

In the embodiment of the present application, the device for implementing the function of the terminal device may be the terminal device, or may be a device capable of supporting the terminal device to implement the function, for example, a chip system or a chip, and the device may be installed in the terminal device. In the embodiment of the application, the chip system may be formed by a chip, and may also include a chip and other discrete devices.

2. (radio) access network (R) AN) device: the authorized users of the specific area may be provided with the functionality to access the communication network, which may specifically include wireless network devices in a third generation partnership project (3rd generation partnership project,3GPP) network or may include access points in a non-3GPP (non-3 GPP) network.

The RAN equipment may be adapted to employ different radio access technologies. There are two types of current radio access technologies: 3GPP access technologies (e.g., third generation (3rd generation,3G), fourth generation (4th generation,4G), or wireless access technologies employed in 5G systems) and non-3GPP (non-3 GPP) access technologies. The 3GPP access technology refers to an access technology conforming to the 3GPP standard specification, for example, access network devices in a 5G system are referred to as next generation base station nodes (next generation Node Base station, gNB) or RAN devices. Non-3GPP access technologies can include air interface technologies typified by an Access Point (AP) in Wireless Fidelity (wireless fidelity, wiFi), worldwide interoperability for microwave Access (worldwide interoperability for microwave access, wiMAX), code division multiple Access (code division multiple access, CDMA), and so forth. The AN device may allow interworking between the terminal device and the 3GPP core network using non-3GPP technology.

The RAN device can be responsible for radio resource management, quality of service (quality of service, qoS) management, data compression, encryption, etc. functions on the air interface side. The AN equipment provides access service for the terminal equipment, and further, the forwarding of control signals and user data between the terminal equipment and the core network is completed.

RAN devices may include, for example, but are not limited to: macro base stations, micro base stations (also called small stations), radio network controllers (radio network controller, RNC), node bs (Node bs, NB), base station controllers (base station controller, BSC), base transceiver stations (base transceiver station, BTS), home base stations (e.g., home evolved NodeB, or home Node bs, HNB), base Band Units (BBU), APs in WiFi systems, wireless relay nodes, wireless backhaul nodes, transmission points (transmission point, TP), or transmission reception points (transmission and reception point, TRP), etc., as well as a gNB or transmission points (TRP or TP) in 5G (e.g., NR) systems, an antenna panel of one or a group (including multiple antenna panels) of base stations in 5G systems, or as well as network nodes constituting a gNB or transmission point, such as a Distributed Unit (DU), or a base station in next generation communication 6G systems, etc. The embodiment of the application does not limit the specific technology and the specific equipment form adopted by the AN equipment.

3. User plane function network element (user plane function, UPF): quality of service (quality of service, qoS) handling, etc. for packet routing and forwarding, or user plane data. User data may be accessed to a Data Network (DN) through the network element. In the embodiment of the application, the method and the device can be used for realizing the functions of the user plane network element.

4. Data Network (DN): for providing a network for transmitting data. Such as a network of operator services, internet network, third party service network, etc.

5. Authentication and authorization function network element of network slice selection: (network slice-specific authentication and authorization function, NSSAAF): the use of an authentication, authorization and accounting (authorization and accounting, AAA) server is supported for specific authentication and authorization of a specified network slice, and if the AAA server belongs to a third party, the nsaaf may contact the AAA server through an AAA proxy. The NSSAAF may contact the AAA server through the AAA proxy if the credential holder belongs to a third party, supporting access to SNPN using the credential of the AAA server.

6. -authentication service function network element (authentication server function, AUSF): support for authentication of UE for the requester network element, providing key material to the requester network element, protecting "guidance information list" of the requester network element.

7. Access and mobility management function network element (access and mobility management function, AMF): the method is mainly used for mobility management, access management and the like, and can be used for realizing other functions besides session management in the functions of a mobility management entity (mobility management entity, MME), such as functions of terminal mobility management, terminal registration and deregistration, terminal session access, allowed slice access selection of a terminal, legal interception or access authorization (or authentication) and the like. In the embodiment of the application, the method and the device can be used for realizing the functions of the access and mobile management network elements.

8. Session management function network element (session management function, SMF): the method is mainly used for session management, IP address allocation and management of terminal equipment, user plane function selection and management, policy control, terminal node or downlink data notification of charging function interfaces and the like. In the embodiment of the application, the method and the device can be used for realizing the function of the session management network element.

9. Service communication proxy (service communication proxy, SCP): message routing in charge of the servitization interface between the control plane network elements, for example, the control plane network elements include network elements such as AMF, SMF, AUSF, PCF.

10. Network slice admission control function network element (network slice admission control function, nsafc): the number of registered users per network slice may be supported for monitoring and controlling, the number of protocol data unit (protocol data unit, PDU) sessions established per network slice is supported for monitoring and controlling, event based network slice status notification is supported and reported to other network elements.

11. Network slice selection function (network slice selection function, NSSF): for making a selection of network slices.

12. Network capability open function network element (network exposure function, NEF): for securely opening to the outside the traffic and capability information (e.g., terminal location, network congestion status) provided by the 3GPP network function network element, etc.

13. Network warehouse function network element (network repository function, NRF): the new functionality for providing registration and discovery functions enables individual network elements to discover each other and communicate via an application programming interface (application programming interface, API) interface.

14. Policy control network element (policy control function, PCF): a unified policy framework for guiding network behavior, and provides service policies, charging policy information, etc. for control plane function network elements (such as AMF, SMF network elements, etc.).

15. Unified data management (unified data management, UDM): for handling user identification, access authentication, registration, or mobility management, etc.

16. -application function network element (application function, AF): the method is used for providing service, or carrying out data routing influenced by application, accessing an open function network element of a network, or carrying out strategy control and the like by interacting service data with a PCF network element.

17. The edge application server discovers the network element (edge application server discovery function, EASDF): a new network element EASDF discovered by the secondary edge application server (edge application server, EAS) primarily functions to process domain name system (domain name system, DNS) messages according to the SMF indication. For example, reporting DNS messages to SMF, adding DNS extension mechanism (extended mechanisms for DNS, EDNS) client subnet options (client subnet option) in DNS query (query) (DNS extension mechanism client subnet options, also may be simply referred to as "ECS option"), forwarding DNS query to DNS server, forwarding DNS response (response) to UE, etc.

In the architecture shown in fig. 1, for example, AMFs, SMFs support both serviced interfaces and non-serviced interfaces. Wherein "servitization interface" can be understood as: the interface exposed to the outside of the functional body is realized through the service registration and the service discovery of the service architecture, the interface is only aimed at a single functional body, the related functional body interacts with other functional bodies outwards through the service interface, and the other functional bodies interact with the functional body through the interface exposed by the functional body. In other words, this mechanism provides a "many-to-one" access mechanism and is accessible without mutual knowledge of each other's address due to the use of service registration and service discovery. This mechanism allows communication between the individual network elements to become service-like rather than serial links, helping to reduce dependencies between each interface and helping to extend independently for each network element. Thus, flexibility of service of the service network architecture is improved. By "non-servitized interface" is understood a conventional interface based on reference points, i.e. an interface of mutually agreed mutual access between two different functional network elements. On the non-serviced interface, there is a binding relationship between the user context and the physical interface.

For example, to support failure handling of an SMF, each UE registered with the SMF needs to send an SMF set (set) Identification (ID) and/or information of a backup SMF corresponding to the UE to other network elements (e.g., to a UPF) whose surroundings have a relationship with it. When other network elements detect an SMF failure, the network element may reselect an SMF from the SMF set according to the SMF set ID to continue to provide service to the UE, or may reselect a backup SMF according to the information of the backup SMF to continue to provide service to the UE. For another example, even if the SMF has provided a backup mechanism, if the SMF serving the UE fails, even if a new SMF may be reselected to serve the UE, context information may not be transferred to the newly selected SMF due to the failure of the old SMF, at which time the UPF may need to reestablish a session with the new SMF, transmit context information, increase communication latency, affect the user's business experience, and so on.

As another example, the N26 interface is an interface between a 4G core network (i.e., mobility management entity (mobility management entity, MME)) and a 5G core network (i.e., AMF) for handover or redirection operations between 4G and 5G. If the AMF in the 5G core network supports the N26 interface, the RAN may fall back through handover or redirection, using voice services.

In other words, in the current 5G network service architecture, the service function of the SMF (or AMF) is not complete, so that there is a coupling relationship between the SMF (or AMF) and other network elements when the SMF (or AMF) fails to recover or the SMF expands/contracts, which is not flexible enough, and the advantages of the service architecture cannot be fully exerted.

In view of this, the present application improves on the 5G network servitization architecture of fig. 1, resulting in a new servitization architecture as shown in fig. 2. Compared with fig. 1, a functional network element is added in fig. 2. For example, the newly added functional network element may be referred to as a "link load orchestration functional network element (link load orchestration function, LLOF)". For example, an N4 interface is between LLOF and UPF, and a servitized interface is between SMF and LLOF. Therefore, the non-service N4 interface between the SMF and the UPF can be shielded in the application, so that the service function of the SMF can be thoroughly realized. Optionally, an N2 interface is between the LLOF and the RAN, so that the non-served N2 interface between the AMF and the RAN can be shielded. Optionally, an N26 interface is between the LLOF and the MME, so that the non-serving N26 interface between the AMF and the MME can be masked.

"masking" in this application is also understood, for example, that there may still be an N4 interface between the SMF and the UPF, but the SMF may not use this N4 interface to communicate with the UPF. Alternatively, it is also understood that there is still an N2 interface between the AMF and the RAN, but the AMF may not use this N2 interface to communicate with the RAN. Still alternatively, it is also understood that there is still an N26 interface between the AMF and the MME, but the AMF may not use this N26 interface to communicate with the MME.

In other words, compared to the existing servitization architecture in fig. 1, the present application proposes a new servitization architecture, in which LLOF is added, and the LLOF can terminate a non-servitization interface, for example, can terminate an N2 interface, an N4 interface, and an N26 interface. The interface between UPF, RAN, MME and LLOF is still based on an existing non-serviced interface in order to be compatible with existing serviced architecture. The LLOF and the control surface network elements (such as AMF, SMF and the like) can adopt a service interface, so that the AMF and the SMF do not need to support a non-service interface, decoupling between the AMF and the SMF and other network elements is facilitated, capacity expansion and contraction can be more conveniently carried out, and the realization of the AMF and the SMF is simplified.

In this application, LLOF may provide one or more of the following services:

(1) LLOF provides a serviceization interface Nllof through which a control plane network element (e.g., AMF, SMF, etc.) can request LLOF to provide a service. For example, the SMF may send a hypertext transfer protocol (hyper text transfer protocol, HTTP) request message to LLOF requesting to invoke a certain service of the LLOF.

(2) The LLOF terminates the flow control transmission protocol (stream control transmission protocol, SCTP) link of the N2 interface.

(3) The LLOF is responsible for the processing of network element level NG interface application protocol (NG application protocol, NGAP) messages of the N2 interface. Wherein, the network element grade NGAP message is a message for configuring network elements; the NG interface is the interface between the RAN and the core network. The message of the NG interface may be, for example, NG setup, RAN configuration update, AMF configuration update, etc.

(4) The processing of packet forwarding control protocol (packet forwarding control protocol, PFCP) node-level messages (e.g., node-level messages include PFCP association-related messages) over the LLOF terminating N4 interface, responsible for reliable retransmission of PFCP messages, responsible for encapsulation or decapsulation of internet protocol (Internet protocol, IP) user datagram protocol (user datagram protocol, UDP) headers of PFCP messages.

(5) The LLOF is responsible for reliable retransmission of GPRS control plane tunneling protocol (GTP-C) messages and encapsulation and decapsulation of IP, UDP headers of GTP-C messages.

(6) LLOF is responsible for the routing of user-level N2, N4, GTP-C messages.

(7) LLOF is responsible for message routing for servitized interfaces (e.g., interface between SMF and AMF, interface between AMF and UDM).

(8) LLOF is responsible for the assignment of a routing identity for determining the control plane network element handling the message, e.g. the routing identity may be NGAP UE ID of the N2 interface or session endpoint identifier (session endpoint identifier, SEID) of the N26 interface, tunnel endpoint identifier (tunnelingendpoint identifier, TEID), SEID of the N4 interface, etc.

(9) The LLOF is responsible for maintenance of a binding relationship, where the binding relationship may refer to a correspondence between a context of the UE and an NF instance.

(10) LLOF is responsible for health detection and disaster recovery processing of network elements (e.g., AMFs, SMFs, etc.).

(11) LLOF is responsible for the scaling of network elements (e.g., AMF, SMF, etc.).

(12) LLOF is responsible for load sharing and overload control of network elements (e.g., AMFs, SMFs, etc.).

In this application, the support of the newly added functional network element provides one or more services, but the specific name thereof is not limited, and in the following description, only the name of the network element is taken as an example to describe.

In this application, since a new service architecture is proposed for the N4 interface between LLOF and UPF, at this time, the N4 interface between SMF and UPF can be masked. SMF can communicate with UPF through LLOF. However, how to reliably transfer information from SMF to UPF is a technical problem to be solved. Similar problems exist between the AMF and the RAN. Since the LLOF and the RAN are an N2 interface, the non-servitized N2 interface of the AMF and the RAN is shielded. At this time, the AMF may send information to be sent to the RAN (or MME) to the LLOF through the server interface, and the LLOF may send the information to the RAN (or MME).

Therefore, the present application further considers the problem of information transmission reliability between the SMF and the UPF and the problem of information transmission reliability between the AMF and the RAN (or MME) on the basis of proposing the new 5G network servitization architecture of fig. 2.

It should be understood that the architecture shown in fig. 2 is only one example of a network architecture that may be applied to the embodiments of the present application, and the network architecture to which the embodiments of the present application are applicable is not limited to this, and any network architecture that can implement the functions of the respective network elements described above is applicable to the embodiments of the present application.

In the network architecture shown in fig. 1 and 2, the network elements may communicate through interfaces shown in the figures. For example, as shown in fig. 1, the N1 interface is a reference point between the terminal device and the AMF; the N2 interface is an interface of RAN and AMF network element, and is used for sending radio parameters, non-access stratum (NAS) signaling, etc.; the N3 interface is an interface between the RAN and the UPF network element and is used for transmitting data of a user plane and the like; the N4 interface is an interface between the SMF network element and the UPF network element, and is used for transmitting information such as a service policy, tunnel identification information of the N3 connection, data buffer indication information, and a downlink data notification message. The N4 interface is a reference point between the SMF and the UPF, and is used for transmitting information such as tunnel identification information, data buffer indication information, downlink data notification message, and the like of the N3 connection; the N6 interface is a reference point between UPF and DN and is used for transmitting data of a user plane and the like; the N9 interface is the reference point for UPF.

It should be understood that the names of interfaces between the network elements in fig. 1 and fig. 2 are only an example, and the names of interfaces in the specific implementation may be other names, which are not specifically limited in this application. Furthermore, the names of the transmitted messages (or signaling) between the various network elements described above are also merely an example, and do not constitute any limitation on the function of the message itself.

It should also be understood that the functions or network elements shown in fig. 1, AMF, SMF, LLOF, etc. in fig. 2 may be understood as network elements for implementing different functions. For example, network slices may be combined as desired. The network elements may be independent devices, may be integrated in the same device to implement different functions, or may be network elements in hardware devices, or may be software functions running on dedicated hardware, or be virtualized functions instantiated on a platform (for example, a cloud platform), which is not limited to the specific form of the network elements.

It should also be understood that the above designations are merely defined to facilitate distinguishing between different functions and should not be construed as limiting the present application in any way. The present application does not exclude the possibility of using other designations in 6G networks as well as other networks in the future. For example, in a 6G network, some or all of the individual network elements may follow the terminology in 5G, possibly by other names, etc.

As in the servitization architecture of fig. 1, the 5G network still maintains on part of the interfaces the use of non-servitized interfaces, e.g., the N4 interface between SMF and UPF, which requires the transmission of large amounts of traffic and policy information, the logic of which is relatively complex, typically the non-servitized interface using PFCP protocol. The N4 interface is an interface between SMF and UPF, the control plane is used for transmitting node-level information and session-level information, and PFCP protocol is adopted; the user plane is used for transmitting the message that the SMF needs to receive or send through the UPF, and the GPRS tunneling protocol (GPRS tunnelling protocol for the user plane, GTP-U) of the user plane is adopted.

Fig. 3 illustrates the format of a PFCP message, which may have n (an integer greater than 0) bytes each having 8 bits (bits), as shown in fig. 4. Where bytes #1 through #m are PFCP message header (PFCP message header), bytes # and (m+1) through #n are zero or more information elements (information element, IE). For a specific description, see chapter 7.2.1 of technical specification (technical specification, TS) 29.244.

Fig. 4 shows a format of a PFCP message header, which may have 16 bytes (n is an integer greater than 0) and 8 bits each, as shown in fig. 5. Wherein bit #1 in the first byte is an "S" flag indicating whether a session endpoint identifier (session endpoint identifier, SEID) field is present in the PFCP message header. If the "S" flag is set to "0", the SEID field does 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 bytes #5 through #12 (8 bytes total). In all PFCP messages, the value of the "S" flag should be set to "1" except for the node-related messages. When s=1, this field may explicitly identify the session endpoint in the receiving packet forwarding control entity. Bit #2 represents a "Message Priority (MP)" flag, and if MP is set to "1", bits 5 to 8 of byte #16 may be used to indicate the priority of a message. Bit #3 represents a "Follow Open (FO)" flag. If the "FO" flag is set to "1" then another PFCP message will follow in the UDP or IP packet (see in particular ts.26.244 sections 6.5 and 7.2.1A). Bits #4 to #5 are spare bits (spare). If the sending entity sets it to "0", the receiving entity should ignore it. Bits 6-8 represent PFCP versions (versions), the current versions being all 1. Should be set to decimal 1 ("001"). Byte #2 represents a message type (message type); bytes #3 to #4 are two bytes of message length; bytes #5 to #12 are optional SEID fields, which may occupy 8 bytes; bytes #13 to #15 are sequence numbers; the last byte #16 is a spare byte (e.g., bits 5-8 may indicate the priority of the message). For a description of the PFCP header, see chapter 7.2.2 in TS 29.244.

Fig. 5 is a schematic flow chart of a message reliable transmission method 500 proposed in the present application, and the steps shown in fig. 7 are explained below. It should be noted that the steps shown by the dashed lines in fig. 7 are optional, and will not be described in detail later. The method comprises the following steps:

in step 501, the first network element sends a request message #1 to the LLOF, where the request message #1 carries a non-service message, and the request message #1 is used to request forwarding of the non-service message. Correspondingly, LLOF receives a request message #1 from the first network element.

In this application, the first network element may be, for example, SMF and AMF. The request message #1 may be transmitted over a servitized interface between the first network element and the LLOF. For example, request message #1 may be encapsulated for transmission in HTTP format.

For example, the non-serviced message may be a PFCP message, an NGAP message, a GTP-C message.

The PFCP message may be, for example, a PFCP session establishment message. As another example, the PFCP message is PFCP sessionmodification. As another example, the PFCP message may be a PFCP session deletion request message, or the like. Alternatively, the PFCP message includes a PFCP message header, and a value in a Sequence Number (SN) field in the PFCP message header may be 0. That is, the SMF may not fill the SN, which is subsequently allocated and filled by LLOF. Alternatively, the PFCP message does not contain a PFCP message header, and the SN field may be allocated and filled when the PFCP message header is encapsulated by a subsequent LLOF. Alternatively, the IE of the PFCP message may be one or more of creating a packet detection rule, creating a Qos enforcement rule. In particular, see chapter 7.3 of TS 29.244.

In the present application, LLOF may provide a service for forwarding a message, or it may be understood that LLOF has a capability of forwarding a message for a first network element, or LLOF supports forwarding a message for a first network element. For example, the service may be defined as nlof_message_transfer.

In one possible implementation, LLOF may also provide different message forwarding services for different types of non-serviced messages. For example, nlof_pfcp message_transfer is defined for transmitting PFCP messages (i.e., transmitting N4 messages between SMF and UPF). As another example, LLOF defines an nlof_ngap message_transfer service for transmitting NGAP messages (i.e., N2 messages between NG-RAN and AMF), and the like. For another example, nllof_GTP-Cmessage_transfer is defined for transmitting GTP-C messages (i.e., N26 messages between AMF and MME). In the application, LLOF can determine to reliably transmit the non-serviced message according to the name of the serviced message.

In a possible implementation manner, the request message #1 may further carry indication information #1, where the indication information #1 is used to indicate that the non-service message is reliably transmitted.

In another possible implementation, the request message #1 carries indication information #2, where the indication information #2 is used to indicate a type of the non-service message. For example, indication information #2 may indicate that the type of the non-serviced message is an N4 interface message type (i.e., a non-serviced message between SMF and UPF). For another example, indication information #2 may indicate that the type of the non-serviced message is an N2 interface message type (i.e., a non-serviced message between the AMF and the RAN). For another example, indication information #2 may indicate that the type of the non-serviced message is an N26 interface message type (i.e., a non-serviced message between the AMF and the MME). The subsequent LLOF may determine to reliably transmit the non-serviced message based on the indication information # 2.

At step 502, llof determines to reliably transfer the non-serviced message in request message #1 over the non-serviced interface.

It should be understood that in this application, messages transmitted on some non-serviced interfaces need to be reliably transmitted, and messages transmitted on other non-serviced interfaces may not need to be reliably transmitted. In other words, not all messages transmitted over the non-serviced interface are required to be reliably transmitted in this application.

For example, LLOF determines reliable transmission of non-serviced messages over the N2 interface; for another example, LLOF determines reliable transmission of non-serviced messages over the N4 interface; the LLOF determines reliable transmission of the non-serviced message over the N26 interface.

In one possible implementation, LLOF may determine to reliably transmit the non-serviced message in the request message #1 based on the name of the serviced message. For example, LLOF may determine reliable transmission of PFCP messages from the nlof_pfcp message_transfer message name. For another example, LLOF may determine reliable transmission of NGAP messages based on the nlof_ngap message_transfer message name. For another example, LLOF may determine reliable transmission to GTP-C based on the nlof_gtp-cmessage_transfer message name.

In another possible implementation, if the request message #1 carries the indication information #1, the indication information #1 may be a displayed IE, for example reliable transmission indication. The LLOF can determine to reliably transmit the non-serviced message carried in the request message #1.

In yet another possible implementation, if the request message #1 carries indication information #2, LLOF determines the type of the non-serviced message according to the indication information # 2. For example, LLOF determines that the non-serviced message is an N4 interface message type, LLOF determines that reliable transmission is to be made for the N4 interface message. For another example, if LLOF determines that the non-serviced message is an N2 interface message type, LLOF determines that reliable transmission is to be made for the N2 interface message. For another example, if LLOF determines that the non-serviced message is an N26 interface message type, LLOF determines that reliable transmission of the N2 interface message is to be performed.

In this step, the LLOF may parse the header of the non-service message after receiving the request message #1, and assign a sequence number to the header of the non-service message, and fill it. Besides, the LLOF may further encapsulate the non-service message, where the encapsulated non-service message includes the sequence number. Taking the non-service message as a PFCP message as an example, assume that LLOF assigns a sequence number of sequence #1 to the PFCP message. LLOF may encapsulate the PFCP in turn UDP, IP, etc.

At step 503 llof sends a non-serviced message to the second network element over the non-serviced interface. Correspondingly, the second network element receives the non-servitized message from the first network element.

In this application, for example, the second network element may be a UPF, for example, the second network element may be a RAN, or, for example, the second network element may be an MME.

Specifically, in one possible implementation manner, the first network element is an SMF, the second network element is a UPF, and the type of the corresponding non-service message is an N4 interface message type; in another possible implementation manner, the first network element is an AMF, the second network element is a RAN, and the corresponding non-service message type is an N2 interface message type; in yet another possible implementation, the first network element is an AMF, the second network element is an MME, and the corresponding non-servitized message type is an N26 interface message type.

Optionally, in step 504, the second network element sends a response message #1 to LLOF.

In one possible implementation, the second network element accepts the IE of the request message #1 (i.e., the various N4 rules (N4 rule) in the PFCP message), then the second network element may send a response message #1 to LLOF. For example, the second network access receives all N4 rule in the IE, the indication information #3 may be a "success" indication information. For another example, if the second network element only accepts part of the N4 rule, or if the second network element does not accept all of the N4 rule, the response message sent by the second network element to the LLOF includes "error cause" (also referred to as "cause value") indication information.

Optionally, at step 505, llof determines whether the non-serviced message was sent successfully.

In one possible implementation, LLOF determines that the non-serviced message was sent successfully if the sequence number carried in response message #1 (an example of a second sequence number) is the same as the LLOF assigned sequence number (an example of a first sequence number). In this application, "successful sending of the non-served message" may also be understood as the LLOF determines that retransmission of the non-served message is not required; if the sequence number carried in response message #1 is different from the sequence number assigned by LLOF, LLOF determines that the non-serviced message transmission failed. In this application, "non-serviced message transmission failure" is also understood to mean that LLOF determines that retransmission of the non-serviced message is required.

Optionally, the LLOF may further determine whether the non-service message is successfully sent by determining whether the source address and the destination address of the IP layer, the source port and the destination port of the UDP layer in the response message #1 completely correspond to the source address and the destination address of the IP layer, and the source port and the destination port of the UDP layer when the request message #1 is encapsulated. For example, if LLOF determines that the SN, IP address, UDP port in response message #1 corresponds exactly to the SN, IP address, UDP port at the time of encapsulation of request message #1, LLOF determines that the non-service message transmission was successful; if the LLOF determines that the SN, IP address, UDP port in the response message #1 does not fully correspond to the SN, IP address, UDP port at the time of encapsulating the request message #1, the LLOF determines that the non-service message transmission failed.

In another possible implementation, the LLOF may start a timer when sending a non-servitized message to the second network element, assuming that the timing duration of the timer is the first duration. If the LLOF receives the response message #1 from the second network element before the timer times out, the LLOF determines that the sending of the non-service message is successful; if the LLOF does not receive the response message #1 from the second network element when the timer expires, the LLOF determines that the non-serviced message transmission fails. For example, if LLOF receives a response message #1 from the second network element after the timer expires, LLOF determines that the non-serviced message transmission failed; for another example, if LLOF still does not receive response message #1 from the second network element after the timer expires, LLOF determines that the non-serviced message transmission failed.

In yet another possible implementation, LLOF may maintain a number of retransmissions N, N being an integer greater than 0. For example, N may be understood as the maximum number of retransmissions. If the number of retransmissions does not reach N when the LLOF receives the response message #1 from the second network element, the LLOF determines that the non-service message transmission is successful. For example, before the number of retransmissions N is exceeded, LLOF receives a response message #1 from the second network element, and LLOF determines that the non-service message transmission was successful; if the number of retransmissions reaches N, LLOF does not receive the response message #1 from the second network element, LLOF determines that the non-service message transmission failed. For example, LLOF determines that the non-served message transmission failed if LLOF receives a response message #1 from the second network element after the number of retransmissions N has been exceeded, or LLOF determines that the non-served message transmission failed if LLOF still does not receive a response message #1 from the second network element after the number of retransmissions N has been exceeded.

In one possible implementation, if the LLOF determines that the non-serviced message was sent successfully, steps 506-507 are performed; in another possible implementation, if LLOF determines that the non-serviced message transmission failed, steps 508-509 are performed.

Optionally, at step 506, llof sends a response message #2 to the first network element.

For example, the response message #2 may carry indication information #3, where indication information #3 is "success" indication information.

Optionally, in step 507, the first network element performs message processing.

For example, if the first network element is an SMF and the second network element is a UPF, when the request message #1 is an N4 session establishment request message, in a possible implementation manner, the SMF determines that the N4 session establishment is successful according to the indication information #3, and may initiate a session modification request procedure subsequently.

For another example, if the first network element is an AMF, the second network element is an MME, and the request message #1 is a forward relocation request, in a possible implementation manner, the AMF determines that the MME is ready for a relocation procedure according to the indication information #3.

Optionally, at step 508, llof sends a response message #3 to the first network element.

For example, the response message #3 may carry indication information #3, where the indication information #3 is "cause value" indication information.

Optionally, in step 509, the first network element performs a processing operation that the message transmission fails.

For example, if the first network element is an SMF, the second network element is a UPF, and the request message #1 is an N4 session establishment request message, in one possible implementation, the SMF determines that the session establishment fails, and may subsequently reinitiate the session suggestion request procedure.

For another example, if the first network element is an AMF, the second network element is an MME, and the request message #1 is a forward relocation request, in one possible implementation manner, the AMF determines that the MME cannot perform the relocation procedure, and may subsequently reinitiate the relocation request procedure.

Based on the above technical solution, in the present application, a new network server architecture including LLOF is provided, and a server interface is adopted between LLOF and a first network element to transmit a non-server message, so that the first network element thoroughly realizes server. And LLOF can confirm that the non-service message is transmitted reliably through the non-service interface, so that the reliable transmission of the non-service message is ensured, and the communication performance is ensured.

It will be appreciated that the examples in the method 500 in the embodiments of the present application are merely for the convenience of those skilled in the art to understand the embodiments of the present application and are not intended to limit the embodiments of the present application to the specific scenarios illustrated. It will be apparent to those skilled in the art from this disclosure that various equivalent modifications or variations can be made, and such modifications or variations are intended to be within the scope of the embodiments of the present application.

It will also be appreciated that some optional features of the various embodiments of the application may, in some circumstances, be independent of other features, or may, in some circumstances, be combined with other features, without limitation.

It is also understood that the various embodiments described in this application may be independent schemes or may be combined according to internal logic, which are all within the scope of this application. And the explanation or explanation of the respective terms appearing in the embodiments may be referred to or explained with each other in the respective embodiments, without limitation.

It should be understood that predefining in this application may be understood as defining, predefining, storing, pre-negotiating, pre-configuring, curing, or pre-firing.

It is to be understood that in this application, the terms "in …," "if," and "if" are used to indicate that the device is doing so under some objective condition, and are not intended to limit the time and require that the device must perform certain acts, nor are other limitations intended.

It will be appreciated that the term "and/or" herein describes an association relationship of associated objects, meaning that there may be three relationships, e.g., a and/or B, which may represent: a alone, a and B together, and B alone, wherein a, B may be singular or plural. In the text description of the present application, the character "/", generally indicates that the associated object is an or relationship; in the formulas of the present application, the character "/" indicates that the front and rear associated objects are a "division" relationship.

The above description has been presented mainly from the point of interaction between the nodes. It will be appreciated that the various nodes, e.g. link load orchestration function network elements, session management function network elements, user plane function network elements, comprise corresponding hardware structures and/or software modules performing the various functions in order to achieve the above described functions. Those of skill in the art will appreciate that the various illustrative elements and algorithm steps described in connection with the embodiments disclosed herein may be implemented as hardware or combinations of hardware and computer software. Whether a function is implemented as hardware or computer software driven hardware depends upon the particular application and design constraints imposed on the solution. Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present application.

It will be appreciated that in order to implement the functions of the above embodiments, the link load orchestration function network element comprises corresponding hardware structures and/or software modules that perform the respective functions. Those of skill in the art will readily appreciate that the elements and method steps of the examples described in connection with the embodiments disclosed herein may be implemented as hardware or a combination of hardware and computer software. Whether a function is implemented as hardware or computer software driven hardware depends upon the particular application scenario and design constraints imposed on the solution.

Fig. 6 and fig. 7 are schematic structural diagrams of a possible reliable message transmission device according to an embodiment of the present application. The reliable message transmission device can be used for realizing the functions of the link load arranging function network element in the method embodiment, so that the beneficial effects of the method embodiment can be realized.

As shown in fig. 7, the message reliable transmission apparatus 100 includes a processing unit 110 and a transceiving unit 120. The message reliable transport apparatus 100 is arranged to implement the functions of the link load orchestration function network element described above in the method embodiment shown in fig. 5.

When the reliable message transmission device 100 is configured to implement the function of the link load arranging function network element in the method embodiment shown in fig. 5, the transceiver unit 120 is configured to receive a first message from a first network element, where the first message carries a non-service message, and the first message is configured to request forwarding of the non-service message, where the first message is transmitted through a service interface; the processing unit 110 is configured to determine that the non-serviced message is reliably transmitted through the non-serviced interface; the transceiving unit 110 transmits the non-serviced message through the non-serviced interface.

In one possible implementation manner, the first message carries first indication information, where the first indication information is used to indicate reliable transmission of the non-service message, and the processing unit 110 is configured to determine that the non-service message is reliably transmitted through the non-service interface, and includes: the processing unit 110 is configured to determine, according to the first indication information, to reliably transmit the non-service message through a non-service interface.

In one possible implementation, the processing unit 110 is configured to determine that the non-service message is reliably transmitted through a non-service interface, including: the processing unit 110 is configured to determine, according to the name of the first message, that the non-service message is reliably transmitted through the non-service interface.

In one possible implementation manner, the first message carries second indication information, where the second indication information is used to indicate the type of the non-service message, and the processing unit 110 is configured to determine that the non-service message is reliably transmitted through the non-service interface, and includes: the processing unit 110 is configured to determine, according to the second indication information, to reliably transmit the non-service message through the non-service interface.

In a possible implementation manner, the processing unit 110 is configured to determine reliable transmission of the non-service message, including: the processing unit 110 is configured to assign a first sequence number to the non-service message; the processing unit is used for packaging the non-service message, wherein the packaged non-service message contains the first serial number; the transceiver unit 120 is configured to send the non-service message, including: the transceiver unit 120 is configured to send the encapsulated non-service message.

In one possible implementation, the transceiver unit 120 is configured to receive a second message, where the second message carries a second sequence number; if the second sequence number is the same as the first sequence number, the processing unit 110 is configured to determine that the sending of the non-service message is successful; alternatively, if the second sequence number is different from the first sequence number, the processing unit 110 is configured to determine that the sending of the non-service message fails.

In one possible implementation, the processing unit 110 is configured to start a timer, where the duration of the timer is a first duration; if the transceiver unit 120 receives the second message before the timer expires, the processing unit 110 is configured to determine that the sending of the non-service message is successful; alternatively, if the timer expires, the transceiver unit 120 does not receive the second message, and the processing unit 110 is configured to determine that the sending of the non-service message fails.

In one possible implementation, the processing unit 110 is configured to maintain a retransmission number N, where N is an integer greater than 0; if the number of retransmissions does not reach N when the transceiver unit 120 receives the second message, the processing unit 110 determines that the sending of the non-service message is successful; alternatively, if the number of retransmissions reaches N, the transceiver unit 120 does not receive the second message, and the processing unit 110 determines that the sending of the non-service message fails.

The above-mentioned more detailed descriptions of the processing unit 110 and the transceiver unit 120 may be directly obtained by referring to the related descriptions in the method embodiment shown in fig. 5, which are not repeated herein.

As shown in fig. 7, the message reliable transmission apparatus 200 includes a processor 210 and an interface circuit 220. The processor 210 and the interface circuit 220 are coupled to each other. It is understood that the interface circuit 220 may be a transceiver or an input-output interface. Optionally, the apparatus 200 may further include a memory 230 for storing instructions executed by the processor 210 or for storing input data required by the processor 210 to execute instructions or for storing data generated after the processor 210 executes instructions.

When the message reliable transmission device 200 is used to implement the method shown in fig. 5, the processor 210 is used to implement the functions of the processing unit 110, and the interface circuit 220 is used to implement the functions of the transceiver unit 120.

It should be appreciated that the processor illustrated in fig. 7 may comprise at least one processor, and that the interface circuit may also include a plurality of interface circuits.

The explanation and beneficial effects of the related content in any of the above-mentioned devices can refer to the corresponding method embodiments provided above, and are not repeated here.

It is to be appreciated that the processor in embodiments of the present application may be a central processing unit (Central Processing Unit, CPU), but may also be other general purpose processors, digital signal processors (Digital Signal Processor, DSP), application specific integrated circuits (Application Specific Integrated Circuit, ASIC), field programmable gate arrays (Field Programmable Gate Array, FPGA) or other programmable logic devices, transistor logic devices, hardware components, or any combination thereof. The general purpose processor may be a microprocessor, but in the alternative, it may be any conventional processor.

According to the method provided in the embodiments of the present application, there is further provided a computer program product having a computer program code stored thereon, which when run on a computer causes the computer to perform the method performed by the link load orchestration function network element in the embodiments of method 500.

According to the method provided in the embodiment of the present application, the present application further provides a computer readable medium storing a program code, which when run on a computer, causes the computer to perform the method performed by the link load orchestration function network element in the method 500 of the embodiment described above.

According to the method provided by the embodiment of the application, the application also provides a communication system which comprises a terminal and network equipment. The terminal is configured to perform the steps corresponding to the link load arranging function network element in the method 500.

Optionally, the communication system may further include a first network element and a second network element.

The method steps in the embodiments of the present application may be implemented in hardware, or in software instructions executable by a processor. The software instructions may be comprised of corresponding software modules that may 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, registers, hard disk, removable disk, CD-ROM, or any other form of storage medium known in the art. An exemplary storage medium is coupled to the processor such the processor can read information from, and write information to, the storage medium. The storage medium may be integral to the processor. The processor and the storage medium may reside in an ASIC. In addition, the ASIC may reside in a link load orchestration function network element. The processor and the storage medium may reside as discrete components in a link load orchestration function network element.

In the above embodiments, it may be implemented in whole or in part by software, hardware, firmware, or any combination thereof. When implemented in software, may be implemented in whole or in part in the form of a computer program product. The computer program product includes one or more computer programs or instructions. When the computer program or instructions are loaded and executed on a computer, the processes or functions described in the embodiments of the present application are performed in whole or in part. The computer may be a general purpose computer, a special purpose computer, a computer network, a network device, a user device, or other programmable apparatus. The computer program or instructions may be stored in a computer readable storage medium or transmitted from one computer readable storage medium to another computer readable storage medium, for example, the computer program or instructions may be transmitted from one website site, computer, server, or data center to another website site, computer, server, or data center by wired or wireless means. 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, data center, etc. that integrates one or more available media. The usable medium may be a magnetic medium, e.g., floppy disk, hard disk, tape; but also optical media such as digital video discs; but also semiconductor media such as solid state disks. The computer readable storage medium may be volatile or nonvolatile storage medium, or may include both volatile and nonvolatile types of storage medium.

In the various embodiments of the application, if there is no specific description or logical conflict, terms and/or descriptions between the various embodiments are consistent and may reference each other, and features of the various embodiments may be combined to form new embodiments according to their inherent logical relationships.

It will be appreciated that the various numerical numbers referred to in the embodiments of the present application are merely for ease of description and are not intended to limit the scope of the embodiments of the present application. The sequence number of each process does not mean the sequence of the execution sequence, and the execution sequence of each process should be determined according to the function and the internal logic.

Claims

1. A method for reliable transmission of messages, comprising:

the method comprises the steps that a link load arranging function network element receives a first message from a first network element, wherein the first message carries a non-service message, and the first message is used for requesting forwarding of the non-service message, and the first message is transmitted through a service interface;

the link load arranging function network element determines that the non-service message is reliably transmitted through a non-service interface;

the link load orchestration function network element sends the non-serviced message to the second network element through a non-serviced interface.

2. The method according to claim 1, wherein the link load orchestration function network element determining that the non-serviced message is reliably transmitted over a non-serviced interface, comprising:

the link load arranging function network element determines that the non-service message is reliably transmitted through an N2 interface; or,

the link load arranging function network element determines that the non-service message is reliably transmitted through an N4 interface; or,

the link load orchestration function network element determines that the non-serviced message is reliably transmitted over the N26 interface.

3. The method according to claim 1 or 2, wherein the first message carries first indication information for indicating a reliable transmission of the non-servitized message,

the link load orchestration function network element determining that the non-serviced message is reliably transmitted over a non-serviced interface, comprising:

and the link load arranging function network element determines to reliably transmit the non-service message through a non-service interface according to the first indication information.

4. The method according to claim 1 or 2, wherein the link load orchestration function network element determining a reliable transmission of the non-serviced message over a non-serviced interface, comprising:

And the link load arranging function network element determines to reliably transmit the non-service message through a non-service interface according to the name of the first message.

5. The method according to claim 1 or 2, wherein the first message carries second indication information indicating the non-serviced message type,

and the link load arranging function network element determines to reliably transmit the non-service message through a non-service interface according to the second indication information.

6. The method of claim 5, wherein the non-serviced message type is one or more of the following types: n2 interface message type, N4 interface message type, N26 interface message type.

7. The method according to any one of claim 1 to 6, wherein,

the first network element is a session management function network element, the second network element is a user plane function network element, and the non-service interface is an N4 interface; or,

the first network element is an access and mobility management network element, the second network element is a mobility management entity, and the non-service interface is an N26 interface;

The first network element is an access and mobility management network element, the second network element is a wireless access network, and the non-service interface is an N2 interface.

8. The method according to any of claims 1 to 7, wherein the link load orchestration function network element determines a reliable transmission of the non-serviced message, comprising:

the link load arranging function network element distributes a first serial number for the non-service message;

the link load arranging function network element encapsulates the non-service message, wherein the encapsulated non-service message contains the first sequence number;

the link load orchestration function network element sending the non-servitized message to the second network element, comprising:

and the link load arranging function network element sends the encapsulated non-service message to the second network element.

9. The method of claim 8, wherein the method further comprises:

the link load arranging function network element receives a second message from the second network element, wherein the second message carries a second serial number;

if the second sequence number is the same as the first sequence number, the link load arrangement function network element determines that the non-service message is successfully sent; or,

And if the second sequence number is different from the first sequence number, the link load arrangement function network element determines that the non-service message transmission fails.

10. The method according to any one of claims 1 to 7, further comprising:

the network element of the link load arranging function starts a timer, and the duration of the timer is a first duration;

if the link load arranging function network element receives a second message from the second network element before the timer is overtime, the link load arranging function network element determines that the non-service message is successfully transmitted; or,

and if the timer is overtime, the link load arranging function network element does not receive the second message from the second network element, and the link load arranging function network element determines that the non-service message transmission fails.

11. The method according to any one of claims 1 to 7, further comprising:

the network element of the link load arranging function maintains retransmission times N, wherein N is an integer greater than 0;

if the retransmission times do not reach N when the link load arranging functional network element receives the second message from the second network element, the link load arranging functional network element determines that the non-service message is successfully transmitted; or,

And if the retransmission times reach N, the link load arrangement function network element does not receive the second message from the second network element, and the link load arrangement function network element determines that the non-service message transmission fails.

12. A message reliable transmission apparatus comprising means for performing the method of any one of claims 1 to 11.

13. A message reliable transmission device comprising a processor and interface circuitry for receiving signals from other communication devices than the device and transmitting to the processor or sending signals from the processor to other communication devices than the device, the processor being operable to implement the method of any one of claims 1 to 11 by logic circuitry or executing code instructions.

14. A reliable message transmission apparatus, comprising: a processor coupled with a memory for storing instructions that, when executed by the processor, cause the apparatus to perform the method of any one of claims 1 to 11.

15. A computer readable storage medium having stored therein instructions which, when executed by a communication device, implement the method of any of claims 1 to 11.

16. A computer program product, characterized in that it, when run on a computer, causes the computer to perform the method according to any one of claims 1 to 11.

17. A communication system comprising at least one apparatus for performing any of claims 1 to 11.

18. The communication system of claim 17, further comprising a first network element and a second network element.