CN117528830A

CN117528830A - Message routing method, communication device and communication system

Info

Publication number: CN117528830A
Application number: CN202210912602.9A
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 message routing method, a communication device and a communication system, wherein the method comprises the following steps: the first link load orchestration function receives a first request message from a first instance; the first link load arranging function allocates a first route identifier based on the first request message and sends the first route identifier to the second instance, wherein the first instance and the first route identifier have a binding relationship; the first link load orchestration function receives a first message from the second instance, the first message including a first route identification; the first link load arranging function sends the second message to the first instance based on the first message and the first binding relation, so that the coupling degree between the first instance and the second instance can be reduced, and the flexibility of message routing is improved.

Description

Message routing method, communication device and communication system

Technical Field

The present application relates to the field of communication technology, and more particularly, to a method of message routing, a communication apparatus, and a communication system.

Background

At present, a plurality of instances serving the same business can be mutually bound, so that the plurality of instances can interact messages based on binding relation in the process of subsequent service. For example, the access and mobility management function (access and mobility management function, AMF) instance performs message interaction with the session management function (session management function, SMF) instance, the AMF instance maintains a binding relationship of the SMF instance with a routing identifier of the SMF instance, such as the AMF instance stores a uniform resource identifier (uniform resource identifier, URI) of the SMF instance containing a hostname (hostname) of the SMF instance, the AMF instance sends a message to the SMF instance through the service communication proxy (service communication proxy, SCP) carrying the URI of the SMF instance, the SCP can route the message directly to the SMF instance based on the hostname of the SMF instance in the URI. This approach results in coupling between multiple instances, for example, if an SMF instance needs to be replaced during the service process, a routing identifier needs to be allocated to the replaced SMF instance again, and the AMF instance is notified of the routing identifier, which causes the service terminal to make the message routing mechanism between the instances inflexible.

Disclosure of Invention

The application provides a message routing method, a communication device and a communication system, which can improve the flexibility of message routing.

In a first aspect, a method of message routing is provided, the method being executable by a first link load orchestration function instance or a chip in the link load orchestration function instance, optionally the method further being executable by a second link load orchestration function instance or a chip in the link load orchestration function instance, the method comprising: the first link load orchestration function receives a first request message from a first instance; the first link load arranging function allocates a first route identifier based on the first request message and sends the first route identifier to the second instance, wherein the first instance and the first route identifier have a binding relationship; the first link load orchestration function receives a first message from the second instance, the first message including a first route identification; the first link load orchestration function sends a second message to the first instance based on the first message, the first binding.

It should be noted that, the link load arrangement function instance may also be referred to as a link load arrangement function LLOF instance, and in this application, the link load arrangement function instance and the LLOF instance may represent the same meaning, which is not described in detail below.

Optionally, after the first LLOF receives the first message, the first LLOF determines that the first instance is not available; the first LLOF selects a third instance, releases the first binding relationship between the first instance and the first routing identifier, establishes a third binding relationship between the third instance and the first routing identifier, and sends a third message to the third instance based on the first message.

Based on the technical scheme, when two different instances need to communicate with each other, communication can be performed based on the route identification allocated by the first LLOF instance, that is, the second instance wants to send a message to the first instance, the route identification can be carried in the message, the second instance does not need to maintain the binding relationship between the first instance and the first route identification, that is, the second instance does not need to perceive the address information of the first instance, so that the coupling degree between the first instance and the second instance can be reduced, and the flexibility of message routing is improved.

On the other hand, after the first LLOF receives the first message from the second instance, if the first instance having the binding relationship with the first routing identifier is unusable, the first LLOF may reselect a third instance to continue providing the service, and the first LLOF may release the binding relationship between the first instance and the first routing identifier, establish a third binding relationship between the third instance and the first routing identifier, and send the third message to the third instance based on the first message. That is, the first instance does not need to be replaced by the second instance, the second instance can still use the first routing identifier to continue the message interaction in the subsequent message interaction, the coupling degree between the first instance and the second instance is lower, and the flexibility of the message routing is improved.

With reference to the first aspect, in certain manners of the first aspect, the first request message is configured to request the first link load orchestration function to allocate a first route identifier based on the first request message, and the method further includes: the first link load orchestration function sending a first route identification to the first instance in response to the first request message; the first link load orchestration function receives a first initial request message from a first instance, the first initial request message being used to establish interactions with a second instance; the first link load orchestration function sends a first route identification to the second instance, comprising: the first link load orchestration function sends a second initial request message to the second instance based on the first initial request message, the second initial request message including the first route identification.

Based on the technical scheme, the first LLOF can distribute route identifiers based on the special request message of the route identifiers, and the distribution mechanism is flexible and reliable.

Optionally, the first LLOF establishes the first binding relationship based on the first request message.

With reference to the first aspect, in certain aspects of the first aspect, the method further includes: the first link load orchestration function receives an initial response message from the second instance in response to the second initial request message, the initial response message including the first route identification; the first link load orchestration function establishes a binding relationship based on the initial response message.

Based on the technical scheme, the first LLOF establishes the first binding relation not based on the first request message but based on the initial response message returned by the second instance, and because the initial response message is used for responding to the second initial request message, the second initial request message is generated based on the first initial request message used for establishing interaction between the first instance and the second instance, the first LLOF receives the initial response message, and can be considered that no problem exists in the interaction between the first instance and the second instance, and the first binding relation is established at the moment, so that the reliability of message routing can be improved.

With reference to the first aspect, in some manners of the first aspect, the first request message is used to establish interaction with a second instance, and the first link load orchestration function sends a first route identifier to the second instance, including: the first link load orchestration function sends a second request message to the second instance based on the first request message, the second request message including the first route identification.

Based on the technical scheme, the first LLOF can allocate the first route identification based on the request message for establishing the interaction of the first instance and the second instance, and further the first route identification is carried in the second request message generated based on the first request message, so that the number of signaling can be reduced, and transmission resources can be saved.

Optionally, the first LLOF pre-configures an initial request message assignment route identification that establishes interaction between the two instances based on the initial request. For example, if the first LLOF determines that the initial request message does not include a route identification, the route identification needs to be allocated by default based on the message.

With reference to the first aspect, in some manners of the first aspect, the first request message includes indication information, where the indication information is used to instruct the first link load orchestration function to allocate the first route identifier based on the first request message.

According to the technical scheme, the first request message for establishing interaction between the first instance and the second instance can carry the indication information for indicating the first LLOF to allocate the first route identifier, and further the first LLOF can know whether the first instance has the requirement of allocating the first route identifier or not according to the indication information, so that the reliability of message routing can be improved.

With reference to the first aspect, in certain aspects of the first aspect, the method further includes: the first link load orchestration function receives a response message from the second instance in response to the second request message, the response message comprising the first route identification; the first link load orchestration function establishes a binding relationship based on the response message.

According to the technical scheme, the first LLOF establishes the first binding relation when the first route identification is allocated, but establishes the first binding relation based on the response message returned by the second instance, and because the response message is used for responding to the second request message, the second request message is generated based on the first request message for establishing interaction between the first instance and the second instance, the first LLOF receives the response message, and can consider that no problem exists in establishing interaction between the first instance and the second instance, and the reliability of message routing can be improved by establishing the first binding relation.

Alternatively, the first LLOF may be preconfigured with the type of the first route identification.

With reference to the first aspect, in some manners of the first aspect, the first request message includes type information, where the type information indicates a type of the first route identifier.

Based on the technical scheme, the first LLOF can determine the type of the first route identifier according to the indication of the type information, and further, the first instance can indicate the type of the required first route identifier according to specific scene requirements, for example, the first instance can request the first LLOF to allocate the returned type URI (callback URI) when the first LLOF needs to receive the notification message sent by the second instance, so that the flexibility of message transmission of the system can be improved.

With reference to the first aspect, in certain aspects of the first aspect, the method further includes: the first link load orchestration function receives a first release request message from the first instance; the first link load orchestration function releases the first binding relationship based on the first release request message.

Based on the technical scheme, the first LLOF can release the first binding relation based on the special release request message, and is simple and reliable.

With reference to the first aspect, in certain aspects of the first aspect, the method further includes: the first link load orchestration function receives an association deletion request message from the first instance; the first link load arrangement function sends an association deletion request message to the second instance; the first link load orchestration function receives an association deletion response message from the second instance in response to the association deletion request message; the first link load orchestration function releases the binding based on the association deletion response message.

The association deletion request message may be used to end the interaction between the first instance and the second instance.

Based on the technical scheme, the first LLOF can release the binding relation based on the transmission of the association deletion response message of the second instance, and the association deletion response message is in response to the association deletion request message, so that the first LLOF can consider that the process of disassociating the first instance and the second instance has no problem, and the first LLOF can release the binding relation based on the association deletion response message, thereby improving the reliability of the message routing.

With reference to the first aspect, in certain manners of the first aspect, the first link load orchestration function sends the first route identification to the second instance, including: the first link load orchestration function sending an initial request message to the second instance through a second link load orchestration function, the initial request message comprising the first route identification, the initial request message being used to establish interactions with the second instance; the method further comprises the steps of: the second link load orchestration function receiving an allocation request message from the second instance; the second link load orchestration function assigns a second route identification based on the assignment request message and sends the second route identification to the first instance through the first link load orchestration function, the second instance and the second route identification having a second binding relationship.

Optionally, the first instance sends the third message to the second LLOF via the first LLOF, and the second LLOF sends the fourth message to the second instance based on the third message and the second binding relationship.

According to the technical scheme, the first instance and the second instance can be routed by two different LLOF, and then the second LLOF corresponding to the second instance can allocate the second routing identifier based on the allocation request message sent by the second instance and send the second routing identifier to the first instance, so that when the first instance wants to send the message to the second instance, the second routing identifier can be carried in the message, and then the second LLOF can send the message to the second instance according to the second routing identifier, namely, the first instance does not need to perceive the address information of the second instance, thereby reducing the coupling degree between the first instance and the second instance and improving the flexibility of the message routing.

With reference to the first aspect, in certain manners of the first aspect, the first link load orchestration function sends the first route identification to the second instance, including: sending an initial request message to the second instance through a second link load orchestration function, the initial request message comprising the first route identification, the initial request message being used to establish interactions with the second instance; the method further comprises the steps of: the second link load orchestration function assigns a second route identification based on the initial request message and sends the second route identification to the first instance through the first link load orchestration function, the second instance and the second route identification having a second binding relationship.

According to the technical scheme, the first instance and the second instance can be routed by two different LLOF, and then the second LLOF corresponding to the second instance can allocate the second routing identifier based on the request message for establishing interaction of the first instance and the second instance and send the second routing identifier to the first instance, so that when the first instance wants to send the message to the second instance, the second routing identifier can be carried in the message, and then the second LLOF can send the message to the second instance according to the second routing identifier, namely, the first instance does not need to perceive the address information of the second instance, thereby reducing the coupling degree between the first instance and the second instance and improving the flexibility of message routing.

With reference to the first aspect, in certain manners of the first aspect, the first route is identified as a uniform resource identifier.

With reference to the first aspect, in some aspects of the first aspect, the first instance and the second instance are both instances of the control plane.

In a second aspect, there is provided a method of message routing, the method being executable by a first link load orchestration function instance or a chip in the link load orchestration function instance, the first instance or a chip in the first instance, the second instance or a chip in the second instance, optionally also by a second link load orchestration function instance or a chip in the link load orchestration function instance, the method comprising: the first instance sending a first request message to a first link load orchestration function; the first link load arranging function allocates a first route identifier based on the first request message and sends the first route identifier to the second instance, wherein the first instance and the first route identifier have a first binding relationship; the second instance sending a first message to the first link load orchestration function, the first message comprising a first route identification; the first link load orchestration function sends a second message to the first instance based on the first message, the first binding.

With reference to the second aspect, in certain implementations of the second aspect, the first request message is configured to request the first link load orchestration function to allocate a first route identifier based on the first request message, and the method further includes: the first link load orchestration function sending a first route identification to the first instance in response to the first request message; the first instance sends a first initial request message to the first link load orchestration function, the first initial request message being used to establish interactions with the second instance; the first link load orchestration function sends a first route identification to the second instance, comprising: the first link load orchestration function sends a second initial request message to the second instance based on the first initial request message, the second initial request message including the first route identification.

With reference to the second aspect, in certain implementations of the second aspect, the first link load orchestration function sends a second initial request message to the second instance, including: the first link load orchestration function sending a second initial request message to the second instance through the second link load orchestration function; the method further comprises the steps of: the second instance sends an allocation request message to the second link load orchestration function, the allocation request message being for requesting the second link load orchestration function to allocate a second route identification based on the allocation request message; the second link load arranging function allocates a second route identifier based on the allocation request message and sends the second route identifier to the second instance, and the second instance and the second route identifier have a second binding relationship; the second instance sending a second initial response message to the second link load orchestration function in response to the second initial request message, the second initial response message comprising a second route identification; the second link load orchestration function sends a first initial response message to the first instance through the first link load orchestration function based on the second initial response message, the first initial response message including the second route identification.

With reference to the second aspect, in certain implementations of the second aspect, the method further includes: the second link load orchestration function establishes a second binding relationship based on a second initial response message; the first link load orchestration function establishes a first binding relationship based on the first initial response message.

With reference to the second aspect, in some implementations of the second aspect, the first request message is used to establish interaction with the second instance, and the first link load orchestration function sends the first route identification to the second instance, including: the first link load orchestration function sends a second request message to the second instance based on the first request message, the second request message including the first route identification.

With reference to the second aspect, in certain implementations of the second aspect, the first link load orchestration function sends a second request message to the second instance, including: the first link load orchestration function sending the first request message to a second link load orchestration function, the second link load orchestration function assigning a second route identification based on the first request message, the second link load orchestration function sending the second request message to the second instance based on the first request message, the second request message comprising the second route identification, the second instance and the second route identification having a second binding relationship; the second instance sending a second response message to the second link load orchestration function in response to the second request message, the second response message comprising the second route identification; the second link load orchestration function sends a first response message to the first instance through the first link load orchestration function based on the second response message, the first response message including the second route identification.

Various implementation manners of the second aspect are methods of a system corresponding to various implementation manners of the first aspect, and regarding advantageous technical effects of the various implementation manners of the second aspect, reference may be made to descriptions of related implementation manners of the first aspect, which are not repeated herein.

In a third aspect, a communication device for message routing is provided, the device comprising a transceiver module and a processing module, the transceiver module being configured to receive a first request message from a first instance; the processing module is used for distributing a first route identifier based on the first request message, and the receiving and transmitting module is used for transmitting the first route identifier to a second instance, wherein the first instance and the first route identifier have a first binding relationship; the transceiver module is further configured to receive a first message from the second instance, the first message including the first route identification; the transceiver module is further configured to send a second message to the first instance based on the first message and the first binding relationship.

With reference to the third aspect, in certain implementations of the third aspect, the first request message is configured to request the first link load orchestration function to allocate the first route identifier based on the first request message, and the transceiver module is further configured to send the first route identifier to the first instance in response to the first request message; the transceiver module is further configured to receive a first initial request message from the first instance, the first initial request message being used to establish interaction with the second instance; the transceiver module is further configured to send a second initial request message to the second instance based on the first initial request message, the second initial request message including the first route identification.

With reference to the third aspect, in certain implementations of the third aspect, the transceiver module is further configured to receive an initial response message from the second instance in response to the second initial request message, where the initial response message includes the first route identification; the processing module is used for establishing the first binding relation based on the initial response message.

With reference to the third aspect, in some implementations of the third aspect, the first request message is used to establish interaction with the second instance, and the transceiver module is used to send a second request message to the second instance based on the first request message, where the second request message includes the first route identifier.

With reference to the third aspect, in certain implementations of the third aspect, the first request message includes indication information, where the indication information is used to instruct the first link load orchestration function to allocate the first route identification based on the first request message.

With reference to the third aspect, in certain implementations of the third aspect, the transceiver module is further configured to receive a response message from the second instance in response to the second request message, the response message including the first route identification; the processing module is used for establishing the first binding relation based on the response message.

With reference to the third aspect, in certain implementations of the third aspect, the first request message includes type information, where the type information is used to indicate a type of the first route identifier.

With reference to the third aspect, in certain implementations of the third aspect, the transceiver module is further configured to receive a first release request message from the first instance; the processing module is further configured to release the first binding relationship based on the first release request message.

With reference to the third aspect, in some implementations of the third aspect, the transceiver module is further configured to receive an association deletion request message from the first instance; the transceiver module is further configured to send the association deletion request message to the second instance; the transceiver module is further configured to receive an association deletion response message from the second instance in response to the association deletion request message; and the processing module is used for releasing the first binding relation based on the association deletion response message.

With reference to the third aspect, in some implementations of the third aspect, the first route is identified as a uniform resource identifier.

With reference to the third aspect, in some implementations of the third aspect, the first instance and the second instance are both instances of a control plane.

Various implementation manners of the third aspect are communication apparatuses corresponding to those of the first aspect, and with respect to beneficial technical effects of the various implementation manners of the third aspect, reference may be made to descriptions of related implementation manners of the first aspect, which are not repeated herein.

In a fourth aspect, a communication device is provided having any one of the possible implementations of the first aspect or the first aspect. The functions may be implemented by hardware, or may be implemented by hardware executing corresponding software. The hardware or software includes one or more units corresponding to the above functions.

In a fifth aspect, a communication device is provided that includes a processor. Optionally, a transceiver and memory may also be included. Wherein the memory is for storing a computer program, and the processor is for invoking and running the computer program stored in the memory and controlling the transceiver to transceive signals to cause the communication device to perform the method as in the first aspect, or any of the possible implementations of any of the first aspects.

Illustratively, the communication device orchestrates function instances for the link loads.

In a sixth aspect, a communication device is provided that includes a processor and a memory. Optionally, a transceiver may also be included. Wherein the memory is for storing a computer program, and the processor is for invoking and running the computer program stored in the memory and controlling the transceiver to transceive signals to cause the communication device to perform the method as in the first aspect, or any of the possible implementations of any of the first aspects.

In a seventh aspect, a communication device is provided, comprising a processor and a communication interface for receiving and transmitting data and/or information received to the processor, the processor processing the data and/or information, and the communication interface further being for outputting the data and/or information after processing by the processor, such that the method as in the first aspect, or any of the possible implementations of the first aspect, is performed. Wherein the communication means may be a chip applied to the link load orchestration function instance.

In an eighth aspect, there is provided a computer readable storage medium having stored therein computer instructions which, when run on a computer, cause the method as in the first aspect, or any possible implementation of any of the first aspects, to be performed.

A ninth aspect provides a computer program product comprising computer program code which, when run on a computer, causes the method as in the first aspect, or any of the possible implementations of any of the first aspects, to be performed.

In a tenth aspect, there is provided a wireless communication system comprising a communication device according to the third aspect.

An eleventh aspect provides a wireless communication system comprising a communication device as claimed in any one or more of the third to tenth aspects, or in any possible implementation of any of these aspects.

Drawings

FIG. 1 is a schematic diagram of a network architecture suitable for use in embodiments of the present application;

FIG. 2 is a schematic diagram of an N2 and Nllof interface protocol stack according to an embodiment of the present application;

FIG. 3 is a schematic diagram of an N4 and Nllof interface protocol stack according to an embodiment of the present application;

FIG. 4 is a schematic diagram of an N26 and Nllof interface protocol stack according to an embodiment of the present application;

FIG. 5 is a schematic diagram of an example deployment system provided by an embodiment of the present application;

FIG. 6 is a schematic diagram of a communication system including two LLOF provided in an embodiment of the present application;

fig. 7 is a schematic diagram of a communication system including LLOF and SCP according to an embodiment of the present application;

FIG. 8 is a schematic flow chart diagram of a message routing provided by an embodiment of the present application;

FIG. 9 is a schematic flow chart diagram of an example message routing method provided by an embodiment of the present application;

FIG. 10 is a schematic flow chart diagram of another example message routing method provided by an embodiment of the present application;

FIG. 11 is a schematic flow chart diagram of a method for releasing binding according to an embodiment of the present application;

FIG. 12 is a schematic flow chart diagram of another method for releasing binding provided by embodiments of the present application;

fig. 13 and 14 are schematic block diagrams of possible communication devices provided in an embodiment of the present application.

Detailed Description

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

In order to facilitate understanding of the technical solutions of the present application, a description will first be given of a communication system to which the technical solutions of the present application can be applied.

The technical scheme provided by the application can be applied to various communication systems. For example, a wireless mobile cellular communication system comprising a fifth generation (5 ^th generation, 5G) or NR systems, LTE frequency division duplex (frequency division duplex, FDD) systems, LTE time division duplex (time division duplex, TDD) systems, etc. This application disclosesThe technical scheme provided by the method can also be applied to non-terrestrial communication network (non-terrestrial network, NTN) communication systems such as satellite communication systems and the like. The technical solutions provided herein may also be applied to a device-to-device (D2D) communication system, a vehicle-to-everything (V2X) communication system, a machine-to-machine (machine to machine, M2M) communication system, a machine type communication (machine type communication, MTC) system, and an internet of things (internet of things, ioT) communication system or other communication systems. The technical scheme provided by the application can also be applied to future communication systems, such as a sixth generation mobile communication system.

Fig. 1 is a schematic diagram of a network architecture suitable for use in embodiments of the present application.

The service architecture and the communication mode thereof are briefly introduced. Referring to fig. 1, a service-based network architecture 100 provided in an embodiment of the present application includes a plurality of Network Functions (NF):

1. network slice selection network element: mainly for providing slice selection. In 5G communications, the network slice selection network element may be a network slice selection function (network slice selection function, NSSF). The Nnssf is a service-based interface provided by the NSSF, through which the NSSF may communicate with other network functions.

2. Network opening network element: for securely opening to the outside the services and capabilities provided by the third generation partnership project (3rd generation partnership project,3GPP) network functions, etc. In 5G communications, the network opening network element may be a network opening function (network exposure function, NEF) network element. Where Nnef is a service-based interface provided by the NEF, which may communicate with other network functions through the Nnef.

3. Network storage network element: for storing the network function entity and the description information of the service provided by the network function entity, supporting service discovery, network element entity discovery, etc. In 5G communication, the network storage network element may be a network storage function (network repository function, NRF) network element. The nrrf is a service-based interface provided by the NRF, which can communicate with other network functions through the nrrf.

4. Policy control network element: a unified policy framework for guiding network behavior, providing policy rule information for control plane function network elements (e.g., AMFs, SMFs, etc.), and the like. In 5G communication, the policy control network element may be a policy control function (policy control function, PCF) network element. Where Npcf is a service-based interface provided by the PCF, the PCF may communicate with other network functions through the Npcf.

5. Data management network element: for handling user identification, access authentication, registration, or mobility management, etc. In 5G communication, the data management network element may be a unified data management (unified data management, UDM) network element. Where Nudm is a service-based interface provided by the UDM, which may communicate with other network functions through Nudm.

6. Application network element: for performing application-influenced data routing, accessing network open functions, or interacting with policy frameworks for policy control, etc. In 5G communication, the application network element may be an application function (application function, AF) network element. Naf is a service-based interface provided by the AF, which may communicate with other network functions through Naf.

7. The edge application server discovers the network elements: the method is mainly used for assisting in discovering the edge application server. In 5G communications, the edge application server discovery network element may be an edge application server discovery function (edge application server discovery function, EASDF). Where Neasdf is a service-based interface provided by an EASDF, which may communicate with other network functions through Neasdf.

8. Network slice authentication and authorization network elements: the method is mainly used for authenticating and authorizing the network slice and the like. In 5G communications, the network slice authentication and authorization network element may be a network slice authentication and authorization function (NSSAAF). The Nnssaaf is a NSSAAF service-based interface through which NSSAAF may communicate with other network functions.

9. Authentication service network element: the method is mainly used for user authentication and the like. In 5G communication, the authentication service network element may be an authentication service function (authentication server function, AUSF) network element. Nausf is a service-based interface provided by AUSF, which may communicate with other network functions through Nausf.

10. Access management network element: 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 legal interception, access authorization (or authentication) and the like. In 5G communication, the access management network element may be an access management function (access and mobility management function, AMF) network element. Namf is a service-based interface provided by AMFs, which may communicate with other network functions through the Namf.

11. Session management network element: the method is mainly used for session management, network interconnection protocol (internet protocol, IP) address allocation and management of terminal equipment, terminal node of selecting manageable user equipment plane function, strategy control or charging function interface, downlink data notification and the like. In 5G communication, the session management network element may be a session management function (session management function, SMF) network element. Nsmf is a service-based interface provided by the SMF, which may communicate with other network functions through Nsmf.

12. Network slice admission control network element: the method is mainly used for network slice control and the like. In 5G communications, the network slice admission control network element may be a network slice admission control function (network slice admission control function, nsafc). The nnssacf is a service-based interface provided by the nsaacf, which may communicate with other network functions through the nnssacf.

13. User Equipment (UE). May include various handheld devices, vehicle mount devices, wearable devices, computing devices, or other processing devices connected to a wireless modem, as well as various forms of terminals, mobile Stations (MSs), terminals, user Equipment (UEs), soft terminals, etc., such as water meters, electricity meters, sensors, etc.

14. (radio) access network (radio access network, (R) AN) network element: the system is used for providing network access functions for authorized user equipment in a specific area and can use transmission tunnels with different qualities according to the level of the user equipment, the service requirements and the like.

The RAN can manage radio resources, provide access services for the terminal device, and further complete forwarding of control signals and user equipment data between the terminal and the core network, and may also be understood as a base station in a conventional network.

15. User plane network element: quality of service (quality of service, qoS) handling for packet routing and forwarding, or user plane data, etc. In 5G communications, the user plane network element may be a user plane function (user plane function, UPF) network element.

16. Data Network (DN) element: for providing a network for transmitting data, such as the Internet network, etc. The DN network elements can be data network authentication, authorization and charging (data network authentication, authorization, accounting), an application server (application function), etc.

It should be noted that, the network architecture applicable to the embodiment of the present application may further include a link load arranging network element:

17. Link load orchestration network elements: for supporting both serviced and non-serviced interfaces. The link load orchestration network element may also be referred to as a link load orchestration function (link load orchestration function, LLOF). The method can simultaneously communicate with the non-service functions such as RAN, UPF, MME and communicate information with the control plane functions such as AMF and SMF, so that the control plane functions such as AMF and SMF can transmit the message required to be sent to the non-service functions to the LLOF through the service interface.

Of these, nlof is illustratively a service-based serviced interface provided by LLOF, which can communicate with other functions, such as AMF, SMF, etc., through the serviced interface nlof. The N2 interface is a reference point between LLOF and RAN, and N4 is a reference point between LLOF and UPF, and in addition, although not shown in the figure, the N26 interface is a reference point between LLOF and MME. Since the control plane functions AMF, SMF, AUSF, PCF and the like can communicate with the LLOF through the server interface nlof, the control plane message routing is performed by the LLOF, and the control plane functions AMF, SMF and the like can eliminate the need for non-server interfaces. For example, the AMF may not need to support the non-serviced interface N2 and the SMF may not need to support the non-serviced interface N4.

To further facilitate an understanding of the embodiments of the present application, the N2, N4, and N26 interfaces provided by LLOF are described below in connection with fig. 2-4, respectively.

Fig. 2 is a schematic diagram of an N2 and nlof interface protocol stack according to an embodiment of the present application.

Referring to fig. 2, message interactions between IP-based and stream control transmission protocols (stream control transmission protocol, SCTP) exist between the RAN and LLOF. Interaction of next generation application protocol (next generation application protocol, NGAP) messages can be performed between the RAN and the AMF through LLOF. NGAP messages may be classified into user-level NGAP and service-level NGAP, where the user-level NGAP messages may be related to a UE, providing UE-related signaling and connections, such as for transmitting uplink and downlink NAS messages, etc.; the service level NGAP message is a message related to a specific service, such as a multicast/broadcast related NGAP message, etc. The interaction of the NGAP message can be carried out between the RAN and the LLOF through a non-service interface N2, and the interaction of the NGAP message can be carried out between the LLOF and the AMF through a service interface Nllof.

Fig. 3 is a schematic diagram of an N4 and nlof interface protocol stack provided in an embodiment of the present application.

Referring to fig. 3, message interactions based on IP and user datagram protocol (user datagram protocol, UDP) exist between UPF and LLOF, and there may be no interactions based on messages between IP layer and UDP layer between SMF and LLOF. Interaction of session-level packet forwarding control protocol (packet forwarding control protocol, PFCP) messages between the UPF and the SMF may be performed by LLOF. The session-level PFCP message is used to control the user plane resources of the PDU session, for example, the PFCP session creation request is used to create the user plane resources corresponding to the PDU session. Interaction of session-level PFCP messages is carried out between UPF and LLOF through a non-service interface N4 interface, and interaction of PFCP messages can be carried out between LLOF and SMF through a service interface Nllof.

Fig. 4 is a schematic diagram of an N26 and Nllof interface protocol stack provided in an embodiment of the present application.

Referring to fig. 4, the interaction based on the messages between the IP layer and the UDP layer exists between the MME and the LLOF, and the interaction based on the messages between the IP layer and the UDP layer may not exist between the AMF and the LLOF. Interaction of user plane protocol (GTP-C) messages between MME and AMF may be performed by LLOF. GTP-C messages are used to manage the movement of UEs between 4G and 5G, e.g., forward Relocation Request is used to hand over the UE from 4G to 5G or from 5G to 4G. Interaction of the user-level GTP-C message is carried out between the MME and the LLOF through a non-service interface N26 interface, and interaction of the user-level GTP-C message is carried out between the LLOF and the AMF through a service interface Nllof.

It will be appreciated that the functions or network elements described above may be either network elements in a hardware device, software functions running on dedicated hardware, or virtualized functions instantiated on a platform (e.g., a cloud platform). The functions, network elements and interfaces may be referred to by the names mentioned above or by other names in future communication systems, which are not particularly limited in this application.

The network architecture including LLOF and the communication interface provided by LLOF are described above, and the functionality of LLOF is further described below in connection with fig. 5-7.

In providing services to a user equipment, a plurality of network elements or functions are required to interact with each other. Wherein, a network element or function may refer to a NF instance, or a network element or function may be divided into a plurality of service instances based on services. Illustratively, the AMF may be considered as one AMF instance, or the AMF may be partitioned into multiple AMF service instances. LLOF may be considered as one LLOF instance, or LLOF may be a plurality of LLOF instances. The communication interaction between LLOF and NF can be regarded as a communication interaction between LLOF instance (or LLOF service instance) and NF instance (or NF service instance), which will not be described in detail below.

It should be noted that, similar to the description of the functions or network elements above, LLOF instances support a serviced interface (e.g., nllof interface) to interact with a serviced instance (e.g., AMF instance, SMF instance, etc.), LLOF instances support a non-serviced interface (e.g., N2, N4, or N26 interface) to interact with a non-serviced instance (e.g., RAN instance, UPF instance). In the following description, interactions between examples are described, which will not be described in detail.

One or more instances may constitute a set of instances, and the instances in a set of instances may provide the same functionality. One LLOF may be responsible for message routing for one or more instance sets, and instances in different instance sets may provide the same functionality or different functionality.

FIG. 5 illustrates a schematic diagram of an example deployment system provided by embodiments of the present application.

Referring to fig. 5 (a), the system 500 includes LLOF 510, an instance set 520, and a data set 530, wherein the instance set 520 includes instances 521 through 526, and the instances in the instance set 520 may provide the same functionality, e.g., the instances 521 through 526 are AMF instances. Instances in the same set of instances may share a context, i.e., instances in the same set of instances may save the context to a shared data set, such as instances in set of instances 520 may save the context to shared data set 530. Wherein LLOF may serve multiple Data Centers (DCs), such as instance 521 through instance 523 in one DC and instance 524 through instance 526 in another DC.

It should be noted that, the present application does not make any limitation on the number of instance sets served by the LLOF, one LLOF may serve one or more instance sets, the instances in different instance sets may provide the same service, or may provide different services, for example, the instances in two instance sets may be both AMF instances, or the instances in two instance sets are respectively an SMF instance and an AMF instance, which is not particularly limited in the present application.

In one possible implementation, LLOF 510 may be understood as a collection of LLOF instances, see fig. 5 (b), including LLOF instances 511-LLOF instances 514, in which case LLOF instances 511-LLOF instances 514 may share a context, and exemplary, context information for LLOF instances may also be saved to data collection 530. It should be noted that context information of LLOF instances is different from the context of the instances in the instance set 520, and the context is not shared among them.

It should be noted that, the present application does not limit the number of LLOF sets included in a system, one or more LLOF sets may be included in a system, one or more LLOF instances may be included in a LLOF set, one LLOF instance may serve one or more instance sets, and one LLOF set may serve multiple DCs. Such as shown in fig. 5 (b), one LLOF aggregate serves 2 DCs, each of which is served by 2 LLOF instances. The LLOF instances in a LLOF collection may be interconnected through interfaces defined between LLOFs, such as through interfaces within the LLOF domain. Two LLOF instances in two LLOF sets, respectively, may be interconnected by an external interface.

In one possible implementation, two instances requiring message interaction correspond to different LLOFs, respectively, and then message interaction between the two instances may be achieved by two LLOFs.

Fig. 6 shows a schematic diagram of a communication system including two LLOFs according to an embodiment of the present application. Referring to fig. 6, the system includes LLOF 610 and LLOF 620 that can communicate with each other, LLOF 610 being responsible for message routing for instances 631 to 633 in instance set 630 and 641 to 643 in instance set 640. LLOF 610 is responsible for message routing for instances 651-653 in instance set 650. When an instance 631 in the instance set 630 interacts with an instance 651 in the instance set 650, messages can be routed through LLOF 610 and LLOF 620, such as instance 631 sending a message to LLOF 610, LLOF 610 sending the message to LLOF 620, and LLOF 620 sending the message to instance 651.LLOF 610 and LLOF 620 may form LLOF domains (LLOF domains) that are capable of communicating with each other.

It should be noted that in the communication system shown in fig. 6, the two instances interact with each other through different LLOFs, and the participation of the service communication agents (service communication proxy, SCP) may not be required. In one possible implementation, two instances corresponding to two different LLOFs may also be forwarded through the SCP upon message interaction.

Fig. 7 shows a schematic diagram of a communication system including LLOF and SCP according to an embodiment of the present application. Referring to fig. 7, unlike the system shown in fig. 6, LLOF 610 and LLOF 620 do not communicate directly, but rather via SCP 710 and SCP 720, respectively. For example, when an instance 631 in the instance set 630 interacts with an instance 651 in the instance set 650, the instance 631 sends a message to LLOF 610, LLOF 610 sends a message to SCP 710, SCP 710 sends a message to SCP 720, SCP 720 sends a message to LLOF 620, and LLOF 620 routes the message to the instance 651.

A communication system to which the embodiments of the present application are applied is described above with reference to fig. 1 to 7. It should be understood that the application scenario of the embodiment of the present application is not limited thereto, and any network architecture capable of implementing the above-mentioned respective network functions is applicable to the embodiment of the present application.

At present, multiple instances serving the same user equipment may be bound to each other, so that the multiple instances may be based on binding interaction messages in a subsequent process of serving the user equipment. For example, the AMF instance performs message interaction with the SMF instance, the AMF instance maintains a binding relationship between the SMF instance and a routing identifier of the SMF instance, such as the AMF instance stores a uniform resource identifier (uniform resource identifier, URI) of the SMF instance that includes a hostname (hostname) of the SMF instance, the AMF instance sends a message for serving the user equipment to the SMF instance through the SCP, the message carries the URI of the SMF instance, and the SCP can directly route the message to the SMF instance based on the hostname in the URI. This approach allows multiple instances to be coupled to each other for the user equipment, for example, if an SMF instance needs to be replaced during the process of serving the user equipment, a routing identifier needs to be reassigned to the replaced SMF instance, and the AMF instance is notified of the routing identifier, which makes the message routing mechanism between the instances inflexible.

The embodiment of the application provides a method and a device for message routing, which can improve the flexibility of message routing. The method of message routing is described below in connection with fig. 8-12.

Fig. 8 is a schematic flow chart of message routing provided in an embodiment of the present application.

S810, the first instance sends a first request message to the first LLOF, which correspondingly receives the first request message from the first instance.

Wherein the first example and the second example may be any two examples described in fig. 1 to 7. Illustratively, the first instance may be an SMF instance or an SMF service instance, and the second instance may be an AMF instance or an AMF service instance. The description of the first LLOF, which is the LLOF associated with the first instance, may be referred to as the description in fig. 1 to 7.

The first LLOF may assign the first route identification based on a first request message, which in one possible implementation is used to request the first LLOF to assign the first route identification based on the first request message. In another possible implementation, the first request message is used to establish interaction of the first instance and the second instance. The two ways of more detailed flow are described in the following fig. 9 and 10, and are not described here.

S820, the first LLOF allocates a first routing identifier based on the first request message, and sends the first routing identifier to the second instance, where the first instance and the first routing identifier have a binding relationship.

In one possible implementation, the first route identification may be a URI, illustratively a notification URI (notification URI), or a return URI (callback URI).

The first LLOF may carry the first route identifier in a message for establishing an interaction between the first instance and the second instance, and a more detailed implementation may be referred to in the following description of fig. 9 and fig. 10, which are not repeated herein.

S830, the second instance sends a first message to the first LLOF, which correspondingly receives the first LLOF from the second instance.

The first message includes a first route identification.

The first message may be a message for serving the user equipment. The first message may be a message in a session related procedure, or may be a message in a mobility related procedure, or the like, for example.

S840, the first LLOF sends a second message to the first instance, which correspondingly receives the second identification from the first LLOF.

It will be appreciated that the second message may be identical to the first message, in which case the first LLOF may forward the first message directly to the first instance as the second message according to the first route identification. Alternatively, the second message may be different from the first message, and after the first LLOF receives the first message, the first message may be modified, and the modified first message may be sent as the second message to the first instance. For example, the header of the first message is changed, the message body is kept unchanged, a second message is formed, and the second message is sent to the first instance, etc., which is not particularly limited in the embodiments of the present application. In this context, the messages forwarded via LLOF may be described with reference to this paragraph, and will not be described in detail.

The second instance may send the first message directly to the first LLOF. Alternatively, the second instance may send the first message to the first LLOF by other means.

Illustratively, where both the first instance and the second instance are the two instances of the two sets of instances for which the first LLOF is responsible for message routing, e.g., see the system shown in fig. 5, then the second instance may send the first message directly to the first LLOF.

Further exemplary, in case the first instance and the second instance are respectively responsible for message routing by two LLOFs, see for example the system shown in fig. 6, the first instance is associated with a first LLOF, the second instance is associated with a second LLOF, the second instance may send the first message to the first LLOF by means of the second LLOF. For another example, referring to the system shown in fig. 7, where two LLOFs communicate via an SCP, the second instance may send a first message to the second SCP via the second LLOF, the second SCP sending the first message to the first SCP, which in turn sends the first message to the first LLOF.

It will be appreciated that in the case where the second instance sends the first message to the first LLOF via an intermediate device, such as the second LLOF, or the second LLOF, the second SCP, and the first SCP, the intermediate device may modify the first message, such as the intermediate device may modify the header of the first message during transmission of the first message, and the message body is kept unchanged, which is not particularly limited in this application.

In this context, the transmission of the message between the instance and the LLOF may refer to the above description, and may be directly transmitted, or may be transmitted through another device, which will not be described in detail below.

After the first LLOF receives the first message from the second instance, if the first instance having the binding relationship with the first route identifier is unusable, the first LLOF may reselect a third instance to continue providing the service, and the first LLOF may release the binding relationship between the first instance and the first route identifier, establish a third binding relationship between the third instance and the first route identifier, and send the third message to the third instance based on the first message. That is, the first instance does not need to be replaced by the second instance, the second instance can still use the first routing identifier to continue the message interaction in the subsequent message interaction, the coupling degree between the first instance and the second instance is lower, and the flexibility of the message routing is improved.

It should be noted that, in the case that both the first instance and the second instance are responsible for message routing by the first LLOF, the first LLOF may further allocate a second routing identifier based on a request message of the second instance, and send the second routing identifier to the first instance, and when the first instance sends a message to the second instance, the first instance may carry the second routing identifier in the message, and the first LLOF may send the message to the second instance according to the second routing identifier. In the case where the first instance and the second instance are respectively responsible for message routing by two LLOFs, the second LLOF may allocate a second routing identifier based on a request message of the second instance, and send the second routing identifier to the first instance, and when the first instance sends a message to the second instance, the message may carry the second routing identifier in the message, and the second LLOF may send the message to the second instance according to the second routing identifier.

The above illustrates that two different examples can communicate based on the LLOF assigned identities, the following combinations are referred to above: the first LLOF may assign the first route identification based on a first request message, and fig. 9 will explain a manner in which the first request message is used to request the first LLOF to assign the first route identification based on the first request message. Fig. 10 will illustrate the interaction of the first request message for establishing the first instance and the second instance.

It should be noted that, in the following, the first instance and the second instance are respectively illustrated by two LLOF responsible message routes, and the manner in which the first instance and the second instance are respectively illustrated by one LLOF responsible message route may be regarded as that the two LLOFs are combined, the receiving port and the sending port are shared, and the implementation manner is similar, and will not be repeated herein.

Fig. 9 is a schematic flow chart of a method for message routing provided in an embodiment of the present application.

S901, the first instance sends a first allocation request message to the first LLOF, and correspondingly, the first LLOF receives the first allocation request message of the first instance.

The first allocation request message may be regarded as the first request message in fig. 8.

The first allocation request message is for requesting the first LLOF to allocate a first route identification for the first instance. The first allocation request message may be a URI allocation request message for requesting the first LLOF to allocate a URI for the first instance, for example.

In one possible implementation, the first allocation request message includes identification type information indicating a type of the first route identification. Illustratively, the identification type information may be used to indicate that the first route is identified as a notification URI, or a callback URI.

It will be appreciated that the first instance may determine that a message interaction with the second instance is required based on the type of traffic, and may request that the first LLOF assign a first route identification of the first instance prior to interaction with the second instance, which may be used for subsequent interactions of the first instance and the second instance, such as transmission of the first message shown in fig. 8.

S902, the first LLOF allocates a first route identification based on the first allocation request message.

Illustratively, the first LLOF may allocate a URI identification for the first instance based on the URI allocation request message. Further exemplary, the first LLOF may allocate a first route identification for the first instance based on the identification type information in the first allocation request message, such as allocating a first route identification of a callback URI type for the first instance based on the identification type information.

S903, the first LLOF sends the first route identification to the first instance, and correspondingly, the first instance receives the first route identification from the first LLOF.

The first LLOF may send a first allocation response message to the first instance in response to the first allocation request message, the first allocation response message carrying the first route identification therein.

It is appreciated that the first LLOF may synchronously store the binding of the first instance and the first routing identifier when the first instance is assigned the first routing identifier. Or the first LLOF may also establish the first binding relationship between the first instance and the first route identification based on a second initial response message (see description of S912 below) sent by the second instance.

S904, the first instance sends a first initial request message to the first LLOF, which receives the first initial request message from the first instance, correspondingly.

The first initial request message may be an interaction established between the first instance and the second instance.

In one possible implementation, the initial request message includes discovery information for discovering the second instance. For example, the first instance may carry discovery information in a header or body of the initial request message. Wherein the discovery information may include at least one of the following information: user identification information, DNN, S-NDDAI, and position information of UE.

S905, the first LLOF and the second LLOF determine a second instance, and transmit a second initial request message.

The first LLOF may determine the second instance itself based on the first initial request message, or other devices, such as the second LLOF, SCP, NRF, may determine the second instance. The manner of determining the second example is explained below.

Mode 1:

the first LLOF determines location information of the second instance based on the local configuration information, and a second LLOF corresponding to the second instance.

It is understood that if the first initial request message includes discovery information, the first LLOF may determine location information of the second instance and the second LLOF based on the local configuration information and the discovery information.

The first LLOF sends a second initial request message to the second LLOF based on the location information of the second instance, and the first initial request message.

Mode 2:

the first LLOF sends a query message to the NRF.

The query message is used to query for location information of the second instance. Illustratively, the query message includes at least one of the following information: information indicating the type of the second instance, discovery information.

The NRF transmits location information of the second instance to the first LLOF in response to the query message.

The first LLOF may determine the second LLOF based on the location information of the second instance, or the NRF may also send information of the second LLOF to the first LLOF in response to the query message.

Mode 3:

the first LLOF sends a second initial request message to the second LLOF based on the first initial request message.

The second LLOF determines the second instance based on the second initial request message.

Mode 4:

the first LLOF sends a first initial request message to the first SCP.

The first SCP determines a second SCP based on the first initial request message.

The first SCP sends a second initial request message to the second SCP based on the first initial request message.

The second SCP determines a second instance based on the second initial request message, and a second LLOF corresponding to the second instance.

The second LLOF sends a second initial request message to the second instance.

S906, the second LLOF sends a second initial request message to the second instance.

The second initial request message includes a first route identification of the first instance. The second instance may save the first route identification of the first instance for subsequent message interactions with the first instance.

S907, the second instance sends a second allocation request message to the second LLOF.

The second allocation request message is for requesting the second LLOF to allocate a second route identification based on the second allocation request message. The second allocation request message may be a URI allocation request message for requesting the second LLOF to allocate a URI for the second instance, for example.

In one possible implementation, the second allocation request message includes identification type information indicating a type of the second route identification. The identification type information may be used to indicate that the second route is identified as a notification URI, or a callback URI, for example.

It will be appreciated that the identification type information may be preconfigured in the second instance. Alternatively, the identifier type information is carried in the third initial request message, which is not particularly limited in the present application.

S908, the second LLOF assigns a second routing identification for the second instance.

The first LLOF may allocate the second route identification based on the second allocation request message.

Illustratively, the second LLOF may allocate a URI identification for the second instance based on the URI allocation request message. Further exemplary, the second LLOF may assign a second routing identification to the second instance based on the identification type information in the second allocation request message, such as assigning a second routing identification of a callback URI type to the second instance based on the identification type information.

S909, the second LLOF sends the second routing identification to the second instance.

The second LLOF may send a second allocation response message to the second instance in response to the second allocation request message, the second allocation response message carrying the second routing identification therein.

It is appreciated that the second LLOF may synchronously store the binding of the second instance and the second routing identifier when the second instance is assigned the second routing identifier. Or the second LLOF may also store the binding of the second instance and the second routing identity based on the triggering of a second initial response message (see description of S911 below) sent by the second instance.

S910, the second instance sends a second initial response message to the second LLOF.

The second instance may send a second initial response message to the second LLOF in response to the second initial request message, the second initial response message including the second route identification. Optionally, the second initial response message further includes a first route identification.

S911, the second instance establishes a second binding relationship between the second instance and the second routing identifier.

The second instance may establish second binding relationship information between the second instance and the second routing identity based on the third initial response message.

It will be appreciated that if the second LLOF synchronously stores the binding information of the second instance and the second routing identifier when the second instance is assigned the second routing identifier, the second LLOF may not need to establish the second binding between the second instance and the second routing identifier here.

S912, the second LLOF sends a second initial response message to the first LLOF.

The second initial response message includes a second route identification for the second instance.

S913, the first LLOF establishes a first binding relationship between the first instance and the first routing identity.

The first LLOF may establish binding relationship information between the first instance and the first route identification based on the second initial response message.

It will be appreciated that if the first LLOF establishes the first binding between the first instance and the first routing identifier simultaneously when the first instance is assigned the first routing identifier, the first LLOF may not need to establish the first binding between the first instance and the first routing identifier here.

S914, the first LLOF sends a first initial response message to the first instance.

The first LLOF may send the first initial response message to the first instance based on the second initial response message. The first initial response message includes a second route identification for the second instance.

And the second instance wants to send a message to the first instance, the first routing identifier can be carried in the message, the second instance does not need to maintain a first binding relationship between the first instance and the first routing identifier, namely the second instance does not need to perceive the address information of the first instance, the first LLOF can route based on the first binding relationship, similarly, the first instance wants to send the message to the second instance, the second routing identifier can be carried in the message, the first instance does not need to maintain a second binding relationship between the second instance and the second routing identifier, namely the first instance does not need to perceive the address information of the second instance, and the second LLOF can route based on the second binding relationship.

Based on the technical scheme, the coupling degree between the first instance and the second instance can be reduced, and the flexibility of message routing is improved.

Fig. 10 is a schematic flow chart diagram of another example message routing method provided by an embodiment of the present application.

S1001, the first instance sends a first initial request message to the first LLOF.

The first initial request message may be used to establish an interaction between the first instance and the second instance.

In one possible implementation, the first initial request message includes indication information indicating that the first LLOF assigns a first routing identification for the first instance.

In another possible implementation, the first initial request message further includes identification type information indicating a type of the first route identification.

S1002, the first LLOF assigns a first route identification based on the first initial request message.

It should be noted that, the first LLOF may be configured in advance to allocate a first route identifier to the first instance based on the first initial request message sent by the first instance. Or the first LLOF may also assign the first instance with the first routing identification based on the indication information and/or the identification type information in the first initial request message.

S1003, the first LLOF and the second LLOF determine the second instance, and transmit the first initial request message.

The manner in which the first LLOF and the second LLOF determine the second instance may refer to the description of step S905 in fig. 9, which is not described herein.

S1004, the second LLOF assigns a second route identification based on the second initial request message.

S1005, the second LLOF sends a second initial request message to the second instance.

The second LLOF may send a second initial request message to the second instance based on the second initial request message. The second initial request message includes a first route identification of the first instance and a second route identification of the second instance.

S1006, the second instance sends a second initial response message to the second LLOF.

The second instance may send a second initial response message to the second LLOF, the second initial response message including the first route identification of the first instance and the second route identification of the second instance.

S1007, the second LLOF establishes a second binding between the second instance and the second routing identity.

The second instance may establish a second binding relationship between the second instance and a second routing identity based on a second initial response message.

It will be appreciated that if the second LLOF synchronously establishes the second binding information between the second instance and the second routing identifier at the time of assigning the second routing identifier to the second instance, the second LLOF may not need to establish the second binding between the second instance and the second routing identifier again.

S1008, the second LLOF sends a second initial response message to the first LLOF.

The second LLOF sends a second initial response message to the first LLOF.

The second initial response message includes a first route identification of the first instance and a second route identification of the second instance.

S1009, the first LLOF establishes a first binding relationship between the first instance and the first routing identity.

The first LLOF may establish a first binding relationship between the first instance and the first route identification based on the second initial response message.

S1010, the first LLOF sends a first initial response message to the first instance.

Fig. 11 is a schematic flowchart of a method for releasing a binding relationship according to an embodiment of the present application.

S1101, the first instance sends a first release request message to the first LLOF.

The first release request message is for requesting the first LLOF to release a first binding relationship between the first instance and the first routing identifier.

S1102, the first LLOF releases the binding between the first instance and the first routing identity.

The first LLOF may release the first binding relationship between the first instance and the first route identification based on the first release request message.

S1103, the first LLOF sends a first release response message to the first instance.

The first LLOF may send a first release response message to the first instance in response to the first release request message, the first release response message being for informing the first LLOF that the first binding relationship between the first instance and the first routing identity is released.

S1104, the first instance sends an association release request message to the second instance.

The association deletion request message is for requesting an end of the interaction between the first instance and the second instance.

The first instance may send the association deletion request message to the second instance through the first LLOF and the second LLOF.

S1105, the second instance sends a second release request message to the second LLOF.

The second release request message is for requesting a second LLOF to release a second binding relationship between the second instance and the second routing identity.

The second instance may send a second release request message to the second LLOF based on the triggering of the association delete request message.

S1106, the second LLOF releases the second binding between the second instance and the second routing identity.

The second LLOF may release the second binding relationship between the second instance and the second routing identity based on the second release request message.

S1107, the second LLOF transmits a second release response message to the second instance.

The second LLOF may send a second release response message to the second instance in response to the second release request message.

S1108, the second instance sends an association deletion response message to the first instance.

The second instance may send the association deletion response message to the second instance through the second LLOF and the first LLOF.

Fig. 12 is a schematic flow chart of another method for releasing binding according to an embodiment of the present application.

S1201, the first instance sends an association deletion request message to the second instance.

The first instance may send an association delete request message to the second instance over the first LLOF and the second LLOF.

S1202, the second instance sends an association deletion response message to the second LLOF.

The second instance may send the association deletion response message to the second LLOF in response to the association deletion request message.

S1203, the second LLOF releases the second binding between the second instance and the second routing identity.

The second LLOF may release the second binding relationship between the second instance and the second routing identity based on the association deletion response message.

S1204, the second LLOF transmits an association deletion response message to the first LLOF.

S1205, the first LLOF releases the first binding between the first instance and the first routing identifier.

The first LLOF may release the first binding relationship information between the first instance and the first route identification based on the association deletion response message.

S1206, the first LLOF sends an association deletion response message to the first instance.

And then unbinding the first instance and the first route identifier, and unbinding the second instance and the second route identifier.

Having described method embodiments of the present application, corresponding apparatus embodiments are described below. It is to be understood that the description of the device embodiments corresponds to the description of the method embodiments, and that parts not described in detail can therefore be seen in the preceding method embodiments.

Fig. 13 and 14 are schematic structural diagrams of a possible communication device according to an embodiment of the present application. These communication means can be used to implement the functionality of the LLOF instance in the above-described method embodiments and thus also the advantages provided by the above-described method embodiments. In the embodiment of the application, the communication device may be an LLOF instance, and may also be a module (such as a chip) applied in the LLOF instance.

As shown in fig. 13, the communication device 1300 includes a processing module 1310 and a transceiver module 1320. The communications apparatus 1300 is configured to implement the functionality of the LLOF instance in the method embodiments illustrated in fig. 8-12 described above. Alternatively, the communications apparatus 1300 can include modules for implementing any of the functions or operations of the LLOF examples in the method embodiments illustrated in fig. 8-12 described above, which can be implemented in whole or in part by software, hardware, firmware, or any combination thereof.

When the communication apparatus 1300 is used to implement the functions of the LLOF instance in the method embodiments shown in fig. 8 to 12, the transceiver module 1320 is configured to receive a first request message from the first instance; the processing module 1310 is configured to allocate a first routing identifier based on the first request message, and the transceiver module 1320 is configured to send the first routing identifier to the second instance, where the first instance and the first routing identifier have a first binding relationship; transceiver module 1320 is also configured to receive a first message from the second instance, the first message including a first route identification; the transceiver module 1320 is further configured to send a second message to the first instance based on the first message and the first binding relationship.

The above-mentioned processing module 1310 and transceiver module 1320 may be directly described with reference to the related descriptions in the method embodiments shown in fig. 3 to 10, which are not repeated herein.

As shown in fig. 14, the communication device 1200 includes a processor 1410 and an interface circuit 1420. The processor 1410 and the interface circuit 1420 are coupled to each other. It is to be appreciated that the interface circuit 1420 may be a transceiver or an input-output interface. Optionally, the communication device 1200 may further comprise a memory 1430 for storing instructions to be executed by the processor 1410 or for storing input data required by the processor 1410 to execute instructions or for storing data generated after the processor 1410 executes instructions.

When the communication apparatus 1200 is used to implement the methods shown in fig. 8 to 12, the processor 1410 is used to implement the functions of the processing unit 1310, and the interface circuit 1420 is used to implement the functions of the transceiver unit 1320.

When the communication device is a chip applied to the LLOF instance, the production network element chip implements the function of the LLOF instance in the method embodiment. The LLOF instance chip receives information from other modules (e.g., radio frequency modules or antennas) in the LLOF instance that the other instances send to the LLOF instance; alternatively, the LLOF instance chip sends information to other modules (e.g., radio frequency modules or antennas) in the LLOF instance that the LLOF instance sends to the other instances.

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.

The Memory in embodiments of the present application may be in random access Memory (Random Access Memory, RAM), flash Memory, read-Only Memory (ROM), programmable ROM (PROM), erasable Programmable ROM (EPROM), electrically Erasable Programmable EPROM (EEPROM), registers, hard disk, a removable disk, a 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. In the alternative, 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 network device or terminal device. The processor and the storage medium may reside as discrete components in a network device or terminal device.

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 terminal device, or other programmable apparatus. The computer program or instructions may be stored in or transmitted across a computer-readable storage medium. 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 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 DVD; but also semiconductor media such as Solid State Disks (SSDs).

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 should be understood that, in the embodiments of the present application, the numbers "first" and "second" … are merely for distinguishing different objects, such as for distinguishing different network devices, and are not limited to the scope of the embodiments of the present application, but are not limited thereto.

It should also be understood that, in this application, "when …", "if" and "if" all refer to a corresponding process that the network element will make under some objective condition, are not limited in time, nor do it require that the network element be implemented with a judging action, nor are other limitations meant to be present.

It should also be understood that in various embodiments of the present application, "B corresponding to a" means that B is associated with a from which B may be determined. It should also be understood that determining B from a does not mean determining B from a alone, but may also determine B from a and/or other information.

It should also be understood that the term "and/or" is merely one association relationship describing the associated object, and means that three relationships may exist, for example, a and/or B may mean: a exists alone, A and B exist together, and B exists alone. In addition, the character "/" herein generally indicates that the front and rear associated objects are an "or" relationship.

Similar to the term "appearing in this application includes one or more of the following: the meaning of the expressions a, B, and C "generally means that the item may be any one of the following unless otherwise specified: a, A is as follows; b, a step of preparing a composite material; c, performing operation; a and B; a and C; b and C; a, B and C; a and A; a, A and A; a, A and B; a, a and C, a, B and B; a, C and C; b and B, B and C, C and C; c, C and C, and other combinations of a, B and C. The above is an optional entry for the item exemplified by 3 elements a, B and C, when expressed as "the item includes at least one of the following: a, B, … …, and X ", i.e. when there are more elements in the expression, then the entry to which the item is applicable can also be obtained according to the rules described above.

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 of message routing, the method comprising:

The first link load orchestration function receives a first request message from a first instance;

the first link load arranging function allocates a first route identifier based on the first request message and sends the first route identifier to a second instance, wherein the first instance and the first route identifier have a first binding relationship;

the first link load orchestration function receiving a first message from the second instance, the first message comprising the first route identification;

the first link load orchestration function sends a second message to the first instance based on the first message, the first binding.

2. The method of claim 1, wherein the first request message is to request the first link load orchestration function to assign the first route identification based on the first request message, the method further comprising:

the first link load orchestration function sending the first route identification to the first instance in response to the first request message;

the first link load orchestration function receiving a first initial request message from the first instance, the first initial request message being used to establish interactions with the second instance;

The first link load orchestration function sending the first route identification to the second instance, including:

the first link load orchestration function sends a second initial request message to the second instance based on the first initial request message, the second initial request message including the first route identification.

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

the first link load orchestration function receiving an initial response message from the second instance in response to the second initial request message, the initial response message comprising the first route identification;

the first link load orchestration function establishes the first binding relationship based on the initial response message.

4. The method of claim 1, wherein the first request message is used to establish interaction with the second instance,

the first link load orchestration function sends a second request message to the second instance based on the first request message, the second request message including the first route identification.

5. The method of claim 4, wherein the first request message includes indication information that instructs the first link load orchestration function to assign the first route identification based on the first request message.

6. The method of claim 4 or 5, wherein the method further comprises:

the first link load orchestration function receives a response message from the second instance in response to the second request message, the response message comprising the first route identification;

the first link load orchestration function establishes the first binding relationship based on the response message.

7. The method of any of claims 1 to 6, wherein the first request message comprises type information indicating a type of the first route identification.

8. The method of any one of claims 1 to 7, wherein the method further comprises:

the first link load orchestration function receiving a first release request message from the first instance;

the first link load orchestration function releases the first binding relationship based on the first release request message.

9. The method of any one of claims 1 to 7, wherein the method further comprises:

the first link load orchestration function receives an association delete request message from the first instance;

the first link load orchestration function sends the association deletion request message to the second instance;

the first link load orchestration function receives an association deletion response message from the second instance in response to the association deletion request message;

the first link load orchestration function releases the first binding relationship based on the association deletion response message.

10. The method of claim 1, wherein the first link load orchestration function sends the first route identification to a second instance, comprising:

the first link load arrangement function sends an initial request message to the second instance through a second link load arrangement function, wherein the initial request message comprises the first route identification, and the initial request message is used for establishing interaction with the second instance;

the method further comprises the steps of:

the second link load orchestration function receiving an allocation request message from the second instance;

The second link load arrangement function allocates a second route identifier based on the allocation request message, and sends the second route identifier to the first instance through the first link load arrangement function, wherein the second instance and the second route identifier have a second binding relationship.

11. The method of claim 1, wherein the first link load orchestration function sends the first route identification to a second instance, comprising:

sending an initial request message to the second instance through a second link load orchestration function, the initial request message comprising the first route identification, the initial request message being used to establish interactions with the second instance;

the method further comprises the steps of:

the second link load arrangement function allocates a second route identifier based on the initial request message, and sends the second route identifier to the first instance through the first link load arrangement function, wherein the second instance and the second route identifier have a second binding relationship.

12. The method of any of claims 1 to 11, wherein the first route is identified as a uniform resource identifier.

13. The method of any one of claims 1 to 12, wherein the first instance and the second instance are each instances of a control plane.

14. A method of message routing, the method comprising:

the first instance sending a first request message to a first link load orchestration function;

the second instance sending a first message to the first link load orchestration function, the first message comprising the first route identification;

15. The method of claim 14, wherein the first request message is for requesting the first link load orchestration function to assign the first route identification based on the first request message, the method further comprising:

The first instance sending a first initial request message to the first link load orchestration function, the first initial request message being used to establish interaction with the second instance;

16. The method of claim 15, wherein the first link load orchestration function sending a second initial request message to the second instance, comprising:

the first link load orchestration function sending a second initial request message to the second instance through a second link load orchestration function;

the method further comprises the steps of:

the second instance sending an allocation request message to a second link load orchestration function, the allocation request message being for requesting the second link load orchestration function to allocate a second route identification based on the allocation request message;

the second link load arranging function allocates the second route identifier based on the allocation request message and sends the second route identifier to the second instance, wherein the second instance and the second route identifier have a second binding relationship;

The second instance sending a second initial response message to the second link load orchestration function in response to the second initial request message, the second initial response message comprising the second route identification;

the second link load orchestration function sends the first initial response message to the first instance through the first link load orchestration function based on the second initial response message, the first initial response message including the second route identification.

17. The method of claim 14, wherein the first request message is used to establish interaction with the second instance,

18. The method of claim 17, wherein the first link load orchestration function sending a second request message to the second instance, comprising:

the first link load orchestration function sending the first request message to a second link load orchestration function, the second link load orchestration function assigning a second route identification based on the first request message, the second link load orchestration function sending the second request message to the second instance based on the first request message, the second request message including the second route identification, the second instance and the second route identification having a second binding relationship;

The second instance sending a second response message to the second link load orchestration function in response to a second request message, the second response message comprising the second route identification;

the second link load orchestration function sends a first response message to the first instance through the first link load orchestration function based on the second response message, the first response message including the second route identification.

19. A communication device comprising means for performing the method of any one of claims 1 to 13 or the method of any one of claims 14 to 18.

20. A communication device, comprising: a processor for executing a computer program stored in a memory to cause the apparatus to perform the method of any one of claims 1 to 13 or to cause the apparatus to perform the method of any one of claims 14 to 18.

21. The apparatus of claim 20, wherein the apparatus further comprises the memory.

22. A computer readable storage medium, characterized in that the computer readable storage medium has stored thereon a computer program which, when run on a computer, causes the computer to perform the method of any of claims 1 to 13 or causes the computer to perform the method of any of claims 14 to 18.