CN118075761A

CN118075761A - Communication method and communication device

Info

Publication number: CN118075761A
Application number: CN202211471394.XA
Authority: CN
Inventors: 于游洋
Original assignee: Huawei Technologies Co Ltd
Current assignee: Huawei Technologies Co Ltd
Priority date: 2022-11-23
Filing date: 2022-11-23
Publication date: 2024-05-24

Abstract

A method of communication, the method comprising: the core network function may determine whether to process the message of the terminal by the core network function based on a set of index values of terminals served by the core network function and index values of terminals transmitting the message. In this way, the core network function can perform the routing operation for the message from the terminal, and the nodes outside the core network function pool can not sense the online or offline of the core network function in the pool, which is helpful for reducing the signaling overhead and reducing the influence on the user service.

Description

Communication method and communication device

Technical Field

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

Background

Core network functions in the core network are typically deployed using pool (pool) mechanisms. I.e. a location area is served by a plurality of functionally identical core network functions, which form a pool, each core network function in the pool being connected to one or more access network devices. When a core network function in the pool fails, services can be continued to be provided by other core network functions in the pool.

Currently, when a core network function is on-line or off-line in a pool, nodes (such as an access network device, a routing device between the access network device and the core network function, a terminal, and the like) outside the core network function pool need to sense the on-line or off-line of the core network function in the pool, that is, complex parameter configuration needs to be performed on the nodes outside the core network function pool so as to adapt to the change of a connection relationship caused by the on-line or off-line of the core network function, signaling overhead is high, and user services may be affected.

Disclosure of Invention

The application provides a communication method and a communication device, which can be used for executing routing operation for messages from a terminal by a core network function, and nodes outside a core network function pool can not sense the online or offline of the core network function in the pool, thereby being beneficial to reducing signaling overhead and reducing the influence on user services.

In a first aspect, a communication method is provided, which may be performed by a first core network function, or may be performed by a module or a unit in the first core network function, hereinafter collectively referred to as the first core network function for convenience of description.

The method comprises the following steps: the first core network function receives a first message of a first terminal; the first core network function determines whether the first message is processed by the first core network function according to a first index value range corresponding to the first core network function and an index value of the first terminal, wherein the first index value range is a set of index values of terminals of the first core network function supporting service.

Alternatively, the first core network function receiving the first message of the first terminal may refer to: the first core network function receives a first message from a first terminal of the other core network function or the service framework function.

"Determining whether or not to process the first message by the first core network function" may also be replaced by: it is determined whether the first terminal is served by the first core network function or whether the first core network function serves the first terminal or whether the first core network function is responsible for the first terminal or whether the first terminal is under the first core network function.

Optionally, the first index value range is a range between an index value of the first core network function and an index value of the fourth core network function. The index value of the fourth core network function is adjacent to the index value of the first core network function, and the index value of the fourth core network function is smaller than the index value of the first core network function; or when the first core network function is the core network function with the minimum index value in the core network function group, the index value of the fourth core network function is adjacent to the index value of the first core network function, and the fourth core network function is the core network function with the maximum index value in the core network function group. In other words, the fourth core network function is a preamble node of the first core network function, which is responsible for the space between the first core network function and its preamble node.

In the above method, the first core network function corresponds to the first index value range and may serve a terminal whose index value falls within the first index value range, so that when the first core network function receives the first message of the first terminal, it may be determined whether the first message of the first terminal is processed by the first core network function according to whether the index value of the first terminal is within the first index value range, so as to perform a subsequent operation according to a determination result, for example, to process the first message when the index value of the first terminal is within the first index value range, or to transmit the first message to the core network function serving the first terminal when the index value of the first terminal is not within the first index value range, and so on. In other words, the routing operation for the message from the terminal performed by the core network function can be implemented based on the above method. Since the routing operation for the message from the terminal can be performed by the core network function, nodes outside the pool of core network functions can not perceive the online or offline of the core network function in the pool, which helps to reduce signaling overhead and reduce the impact on user traffic.

With reference to the first aspect, in some implementations of the first aspect, the first core network function belongs to a core network function group, where the core network function group includes a plurality of core network functions with the same service function, the first core network function is any one of the plurality of core network functions, and there is no intersection between index value ranges corresponding to the plurality of core network functions.

With reference to the first aspect or any implementation manner thereof, in other implementation manners of the first aspect, the method further includes: and when the index value of the first terminal does not belong to the first index value range, the first core network device sends the first message to a second core network function according to the index value of the first terminal, wherein the second core network function is a core network function in the core network function group for providing service for the first terminal.

I.e. when the first core network function does not serve the first terminal, the first core network function forwards the first message to the second core network function serving the first terminal. In this way, the first message may eventually be sent to the second core network function, which may process the first message, based on the forwarding of the message by the core network function for the terminal.

With reference to the first aspect or any implementation manner thereof, in other implementation manners of the first aspect, the method further includes: when the index value of the first terminal does not belong to the first index value range, the first core network device acquires information of a second core network function according to the index value of the first terminal, wherein the second core network function is a core network function in the core network function group for providing service for the first terminal; the first core network function sends information of the second core network function to a service framework function.

That is, when the first core network function does not provide services for the first terminal, the first core network function may acquire information of the second core network function providing services for the first terminal, and feed back the information of the second core network function to the service framework function, and the service framework function may send the first message to the second core network function again, and finally may send the first message to the second core network function that may process the first message.

With reference to the first aspect or any implementation manner thereof, in other implementation manners of the first aspect, the method further includes: when the first core network function joins the core network function group, the first core network function determines a third core network function according to the index value of the first core network function; the first core network function obtains a first context from the third core network function, and an index value of a terminal corresponding to the first context belongs to the first index value range.

Wherein the index value of the third core network function is adjacent to the index value of the first core network function, and the index value of the third core network function is greater than the index value of the first core network function; or the index value of the third core network function is adjacent to the index value of the first core network function, the third core network function is the core network function with the minimum index value in the core network function group, and the first core network function is the core network function with the maximum index value in the core network function group. In other words, the third core network function is a successor node of the first core network function in the core network function group.

Based on the method, when the first core network function joins the core network function group, the first core network function can acquire the context of the terminal served by the first core network function from the own subsequent node, thereby realizing the automatic migration of the context of the terminal, being beneficial to avoiding the influence of the first core network function on network elements outside the core network function group and being beneficial to ensuring the service continuity.

With reference to the first aspect or any implementation manner thereof, in other implementation manners of the first aspect, the method further includes: the first core network function sends a second message to a service framework function, the second message being used to instruct the first context to migrate to the first core network function.

Based on the method, the service framework function can update the corresponding relation between the terminal and the core network function providing service for the terminal in time, so that the service framework function can inquire the first core network function serving for the terminal when receiving the message sent by the corresponding terminal.

With reference to the first aspect or any implementation manner thereof, in other implementation manners of the first aspect, the second message includes information of a terminal corresponding to the first context and information of the first core network function; the information of the terminal corresponding to the first context comprises at least one of the following information: terminal identification, index value of terminal, or communication address of terminal; and/or the information of the first core network function comprises at least one of the following: an identification of the first core network function, an index value of the first core network function, or a communication address of the first core network function.

With reference to the first aspect or any implementation manner thereof, in other implementation manners of the first aspect, the acquiring, by the first core network function, a first context from the third core network function includes: the first core network function sends a third message to the third core network function, wherein the third message is used for requesting the context of the terminal; the first core network function receives a fourth message from a third core network function, the fourth message including the first context.

In the above method, the third core network function may determine a first index value range, obtain the first context according to the first index value range, and send the first context to the first core network function.

With reference to the first aspect or any implementation manner thereof, in other implementation manners of the first aspect, the third message includes the first index value range.

In the above method, the first index value range is provided by the first core network function to the third core network function, so that the operation of the third core network function can be simplified.

With reference to the first aspect or any implementation manner thereof, in other implementation manners of the first aspect, the first context includes: terminal identification and/or index value of the terminal.

With reference to the first aspect or any implementation manner thereof, in other implementation manners of the first aspect, the first context further includes at least one of the following information: a uniform resource identifier (uniform resource identifier, URI) of the terminal, an identification of a service framework function corresponding to the terminal, a communication address of the service framework function, location information of the terminal, or access information of the terminal.

With reference to the first aspect or any implementation manner thereof, in other implementation manners of the first aspect, the method further includes: when the first core network function is offline, the first core network function backs up a second context to a third core network function, and an index value of a terminal corresponding to the second context belongs to the first index value range; wherein the index value of the third core network function is adjacent to the index value of the first core network function, and the index value of the third core network function is greater than the index value of the first core network function; or the index value of the third core network function is adjacent to the index value of the first core network function, the third core network function is the core network function with the minimum index value in the core network function group, and the first core network function is the core network function with the maximum index value in the core network function group.

The context backup mode based on the method is suitable for a scenario of planned arrangement of core network function offline, for example, when the number of users is small, some core network functions can be offline so as to reduce energy consumption. In other words, when the first core network function is scheduled to be down-line, the first core network function may backup the context of the terminal for which it is responsible to its subsequent nodes in advance, so that even if the first core network function is down-line, the third core network function may serve the terminals.

With reference to the first aspect or any implementation manner thereof, in other implementation manners of the first aspect, the method further includes: the first core network function sends a fifth message to a service framework function, the fifth message being used to instruct the second context to migrate to the third core network function.

In this way, the service framework function may update that the terminal corresponding to the second context corresponds to the third core network function, so that when receiving the message sent by the corresponding terminal, the third core network function serving the corresponding terminal may be queried.

With reference to the first aspect or any implementation manner thereof, in other implementation manners of the first aspect, the fifth message includes information of a terminal corresponding to the second context and information of the third core network function; wherein the information of the terminal corresponding to the second context includes at least one of the following information: terminal identification, index value of terminal, or communication address of terminal; and/or, the information of the third core network function includes at least one of the following: an identification of the third core network function, an index value of the third core network function, or a communication address of the third core network function.

With reference to the first aspect or any implementation manner thereof, in other implementation manners of the first aspect, the method further includes: when the first core network function stores the context of the second terminal, the first core network function backs up the context of the second terminal to a third core network function; wherein the index value of the third core network function is adjacent to the index value of the first core network function, and the index value of the third core network function is greater than the index value of the first core network function; or the index value of the third core network function is adjacent to the index value of the first core network function, the third core network function is the core network function with the minimum index value in the core network function group, and the first core network function is the core network function with the maximum index value in the core network function group.

Based on the above method, the first core network function backs up the context of the terminal registered to the first core network function to the third core network function at any time, so that even if the first core network function is accidentally disconnected (for example, disconnected due to a fault), the third core network function can provide services for the terminals. The context backup mode is suitable for not only the scene of planning and arranging the core network function to be offline, but also the scene of unexpected core network function to be offline.

With reference to the first aspect or any implementation manner thereof, in other implementation manners of the first aspect, the method further includes: when the context of the second terminal is deleted from the first core network function, the first core network function sends a sixth message to the third core network function, where the sixth message is used to indicate that the context of the second terminal is deleted.

The above method helps to reduce the occupation of the storage space of the third core network function.

With reference to the first aspect or any implementation manner thereof, in other implementation manners of the first aspect, the context of the second terminal includes: the identity of the second terminal and/or the index value of the second terminal.

With reference to the first aspect or any implementation manner thereof, in other implementation manners of the first aspect, the context of the second terminal further includes at least one of the following information: the URI of the second terminal, the identifier of the service frame function corresponding to the second terminal, the communication address of the service frame function, the location information of the second terminal, or the access information of the second terminal.

With reference to the first aspect or any implementation manner thereof, in other implementation manners of the first aspect, the method further includes: the service framework function receives a first message from the first terminal; the service framework function searches a core network function corresponding to the first terminal; when the first core network function corresponding to the first terminal is found, the service framework function sends the first message to the first core network function; when the core network function corresponding to the first terminal is not found or the first core network function corresponding to the first terminal is found but the first core network function fails, the service framework function sends the first message to an entry core network function, where the entry core network function is any core network function except for the first core network function in a core network function group, and the core network function group includes a plurality of core network functions with the same service function. For a detailed description of the operations or steps performed by the service framework function reference may be made to the second aspect below or to implementations thereof.

With reference to the first aspect or any implementation manner thereof, in other implementation manners of the first aspect, the method further includes: when the first core network function joins a core network function group, a third core network function obtains a first context, and an index value of a terminal corresponding to the first context belongs to the first index value range; the third core network function sends the first context to the first core network function; wherein the index value of the third core network function is adjacent to the index value of the first core network function, and the index value of the third core network function is greater than the index value of the first core network function; or the index value of the third core network function is adjacent to the index value of the first core network function, the third core network function is the core network function with the minimum index value in the core network function group, and the first core network function is the core network function with the maximum index value in the core network function group. For a detailed description of the operations or steps performed by the third core network function reference may be made to the third aspect or implementation manner below.

In a second aspect, a communication method is provided, which may be performed by a service framework function, or by a module or unit in the service framework function, hereinafter collectively referred to as the service framework function for convenience of description.

Technical effects of the method according to the second aspect and possible implementation manners thereof may refer to the first aspect and possible implementation manners thereof, and are not described in detail.

The method comprises the following steps: the service framework function receives a first message from a first terminal; the service framework function searches a core network function corresponding to the first terminal; when a first core network function corresponding to the first terminal is found, the service framework function sends the first message to the first core network function; when the core network function corresponding to the first terminal is not found or the first core network function corresponding to the first terminal is found but the first core network function fails, the service framework function sends the first message to an entry core network function, wherein the entry core network function is any core network function except for the first core network function in a core network function group, and the core network function group comprises a plurality of core network functions with the same service function.

With reference to the second aspect, in some implementations of the second aspect, the method further includes: the service framework function receives information of a second core network function from the first core network function or the entry core network function, and the second core network function is a core network function in the core network function group for providing service for the first terminal; the service framework function sends the first message to the second core network function.

With reference to the second aspect or any implementation manner thereof, in other implementation manners of the second aspect, the method further includes: when the first core network function joins the core network function group, the service framework function receives a second message from the first core network function, where the second message is used to instruct a first context to migrate to the first core network function, and an index value of a terminal corresponding to the first context belongs to a first index value range, where the first index value range is a set of index values of terminals supporting services by the first core network function; and the service framework function stores the corresponding relation between the terminal corresponding to the first context and the first core network function.

With reference to the second aspect or any implementation manner thereof, in other implementation manners of the second aspect, the second message includes information of a terminal corresponding to the first context and information of the first core network function; the information of the terminal corresponding to the first context comprises at least one of the following information: terminal identification, index value of terminal, or communication address of terminal; and/or the information of the first core network function comprises at least one of the following: an identification of the first core network function, an index value of the first core network function, or a communication address of the first core network function.

With reference to the second aspect or any implementation manner thereof, in other implementation manners of the second aspect, the method further includes: when the first core network function is offline, the service framework function receives a fifth message from the first core network function and sends the fifth message, wherein the fifth message is used for indicating the migration of the second context to the third core network function; the service framework function stores the corresponding relation between the terminal corresponding to the second context and the third core network function; the index value of the terminal corresponding to the second context belongs to a first index value range, and the first index value range is a set of index values of terminals of the first core network function support service; the index value of the third core network function is adjacent to the index value of the first core network function, and the index value of the third core network function is greater than the index value of the first core network function; or the index value of the third core network function is adjacent to the index value of the first core network function, the third core network function is the core network function with the minimum index value in the core network function group, and the first core network function is the core network function with the maximum index value in the core network function group.

With reference to the second aspect or any implementation manner thereof, in other implementation manners of the second aspect, the fifth message includes information of a terminal corresponding to the second context and information of the third core network function; wherein the information of the terminal corresponding to the second context includes at least one of the following information: terminal identification, index value of terminal, or communication address of terminal; and/or, the information of the third core network function includes at least one of the following: an identification of the third core network function, an index value of the third core network function, or a communication address of the third core network function.

With reference to the second aspect or any implementation manner of the second aspect, in other implementation manners of the second aspect, when a first core network function corresponding to the first terminal is found, the method further includes: when a response message for the first message from the first core network function is not received within a preset time after the first message is sent, the service framework function determines that the first core network function fails; the service framework function sends the first message to the ingress core network function.

With reference to the second aspect or any implementation manner thereof, in other implementation manners of the second aspect, for a case where the first core network function fails, the method further includes: the service framework function sends a seventh message to the first core network function; when a response message for the seventh message from the first core network function is not received within a preset time, the service framework function determines that the first core network function fails; and/or when the connection between the first core network function and the service framework function is in a disconnected state, the service framework function determines that the first core network function fails.

With reference to the second aspect or any implementation manner thereof, in other implementation manners of the second aspect, the first index value range is a range between an index value of the first core network function and an index value of a fourth core network function; wherein the index value of the fourth core network function is adjacent to the index value of the first core network function, and the index value of the fourth core network function is smaller than the index value of the first core network function; or the index value of the fourth core network function is adjacent to the index value of the first core network function, the fourth core network function is the core network function with the largest index value in the core network function group, and the first core network function is the core network function with the smallest index value in the core network function group.

In a third aspect, a communication method is provided, which may be performed by a third core network function, or may be performed by a module or a unit in the third core network function, hereinafter collectively referred to as the third core network function for convenience of description.

Technical effects of the method shown in the third aspect and possible implementation manners thereof may refer to the first aspect and possible implementation manners thereof, and are not repeated.

The method comprises the following steps: when a first core network function joins a core network function group, a third core network function acquires a first context, wherein an index value of a terminal corresponding to the first context belongs to a first index value range, and the first index value range is a set of index values of terminals of a first core network function support service; the third core network function sends the first context to the first core network function; wherein the index value of the third core network function is adjacent to the index value of the first core network function, and the index value of the third core network function is greater than the index value of the first core network function; or the index value of the third core network function is adjacent to the index value of the first core network function, the third core network function is the core network function with the minimum index value in the core network function group, and the first core network function is the core network function with the maximum index value in the core network function group.

With reference to the third aspect, in some implementations of the third aspect, the method further includes: the third core network function receives a third message from the first core network function, wherein the third message is used for requesting a terminal context; the third core network function obtains a first context, including: the third core network function determines the first index value range according to the index value of the first core network function, and the third core network function obtains the first context according to the first index value range.

With reference to the third aspect or any implementation manner thereof, in other implementation manners of the third aspect, the method further includes: the third core network function receives a third message from the first core network function, the third message being for requesting a terminal context, the third message comprising the first index value range; the third core network function obtains a first context, including: and the third core network function acquires the first context according to the first index value range.

With reference to the third aspect or any implementation manner thereof, in other implementation manners of the third aspect, the first context includes: terminal identification and/or index value of the terminal.

With reference to the third aspect or any implementation manner thereof, in other implementation manners of the third aspect, the first context further includes at least one of the following information: the method comprises the steps of a URI of a terminal, an identification of a service framework function corresponding to the terminal, a communication address of the service framework function, position information of the terminal or access information of the terminal.

With reference to the third aspect or any implementation manner thereof, in other implementation manners of the third aspect, the method further includes: when the first core network function is offline, the third core network function receives a second context from the first core network function, and an index value of a terminal corresponding to the second context belongs to the first index value range.

With reference to the third aspect or any implementation manner thereof, in other implementation manners of the third aspect, the method further includes: the third core network function receives a context from the second terminal of the first core network function.

With reference to the third aspect or any implementation manner thereof, in other implementation manners of the third aspect, the method further includes: when the context of the second terminal is deleted from the first core network function, the third core network function receives a sixth message from the first core network function, wherein the sixth message is used for indicating that the context of the second terminal is deleted; and the third core network function deletes the context of the second terminal according to the sixth message.

With reference to the third aspect or any implementation manner thereof, in other implementation manners of the third aspect, the context of the second terminal includes: the identity of the second terminal and/or the index value of the second terminal.

With reference to the third aspect or any implementation manner thereof, in other implementation manners of the third aspect, the context of the second terminal further includes at least one of the following information: the URI corresponding to the second terminal, the identifier of the service framework function corresponding to the second terminal, the communication address of the service framework function, the location information of the second terminal, or the access information of the second terminal.

With reference to the third aspect or any implementation manner thereof, in other implementation manners of the third aspect, the first index value range is a range between an index value of the first core network function and an index value of a fourth core network function; wherein the index value of the fourth core network function is adjacent to the index value of the first core network function, and the index value of the fourth core network function is smaller than the index value of the first core network function; or the index value of the fourth core network function is adjacent to the index value of the first core network function, the fourth core network function is the core network function with the largest index value in the core network function group, and the first core network function is the core network function with the smallest index value in the core network function group.

In a fourth aspect, a communications device is provided for performing the method provided by any one of the aspects or implementations thereof. In particular, the apparatus may comprise means and/or modules, such as a processing unit and/or a communication unit, for performing the method provided in any of the above aspects or implementations thereof.

In one implementation, the apparatus is a first core network function, a service framework function, or a third core network function. When the apparatus is a first core network function, a service framework function or a third core network function, the communication unit may be a transceiver, or an input/output interface, or a communication interface; the processing unit may be at least one processor. Optionally, the transceiver is a transceiver circuit. Optionally, the input/output interface is an input/output circuit.

In another implementation, the apparatus is a chip, a system of chips or a circuit for use in a first core network function, a service framework function or a third core network function. When the apparatus is a chip, a system-on-chip or a circuit for use in a first core network function, a service framework function or a third core network function, the communication unit may be an input/output interface, an interface circuit, an output circuit, an input circuit, pins or related circuits on the chip, the system-on-chip or the circuit, etc.; the processing unit may be at least one processor, processing circuit or logic circuit, etc.

In a fifth aspect, there is provided a communication apparatus comprising: a memory for storing a program; at least one processor configured to execute a computer program or instructions stored in a memory to perform the method provided by any one of the aspects or implementations thereof.

In one implementation, the apparatus is a first core network function, a service framework function, or a third core network function.

In another implementation, the apparatus is a chip, a system of chips or a circuit for use in a first core network function, a service framework function or a third core network function.

In a sixth aspect, there is provided a communication apparatus comprising: at least one processor and a communication interface through which the at least one processor obtains computer programs or instructions stored in a memory to perform the methods provided by any one of the above aspects or implementations thereof. The communication interface may be implemented in hardware or software.

In one implementation, the apparatus further includes the memory.

In a seventh aspect, a processor is provided for performing the method provided in the above aspects.

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

In an eighth aspect, there is provided a computer readable storage medium storing program code for execution by a device, the program code comprising instructions for performing the method provided by any one of the aspects or implementations thereof.

In a ninth aspect, there is provided a computer program product comprising instructions which, when run on a computer, cause the computer to perform the method provided by any one of the aspects or implementations thereof.

In a tenth aspect, a chip is provided, the chip including a processor and a communication interface, the processor reading instructions stored on a memory through the communication interface, and performing the method provided by any one of the above aspects or implementation manner. The communication interface may be implemented in hardware or software.

Optionally, as an implementation manner, the chip further includes a memory, where a computer program or an instruction is stored in the memory, and the processor is configured to execute the computer program or the instruction stored in the memory, where the processor is configured to execute the method provided in any one of the above aspects or implementation manner.

When the method provided by the application is executed by the chips, the application is not limited to the number of the chips for realizing the method of the application, and the method can be executed by one chip or can be executed by 2 or more chips. When the number of chips for implementing the method of the application is 2 or more, the chip manufacturer is not limited, and the chips can be the same manufacturer or different manufacturers.

In an eleventh aspect, a communication system is provided comprising the at least one of the above first core network function, service framework function or third core network function.

Drawings

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

Fig. 2 is a schematic diagram of another network architecture suitable for use with the present application.

Fig. 3 is a schematic diagram of deployment of core network functions using a pool mechanism.

Fig. 4 is a schematic diagram of a distributed hash table (distributed hash table, DHT) ring.

Fig. 5 is an example of a Network Function (NF) group based on DHT technology.

Fig. 6 is a system framework provided by the present application and suitable for use in the communication method of the present application.

Fig. 7 is a schematic flow chart of a communication method 700 provided by the present application.

Fig. 8 is a schematic flow chart of a communication method 800 provided by the present application.

Fig. 9 is a schematic flow chart of a communication method 900 provided by the present application.

Fig. 10 is a schematic flow chart of a communication method 1000 provided by the present application.

Fig. 11 is a schematic structural view of a device according to an embodiment of the present application.

Fig. 12 is a schematic view of another structure of the device according to the embodiment of the present application.

Detailed Description

In order to facilitate understanding of the embodiments of the present application, the following description is made before describing the embodiments of the present application.

In the present application, "for indicating" or "indicating" may include for direct indication and for indirect indication, or "for indicating" or "indicating" may be explicitly and/or implicitly indicated. For example, when describing certain information for indicating information I, the information may be included to indicate I directly or indirectly, and not to represent that I must be carried in the information. As another example, the implicit indication may be based on a location and/or a resource used for the transmission; the explicit indication may be based on one or more parameters, and/or one or more indices, and/or one or more bit patterns it represents.

The definitions of many of the features of the present application are set forth only to illustrate the function of the features by way of example and reference is made to the prior art for details.

In the embodiments shown below, the first, second, third, fourth, and various numerical numbers are merely for convenience of description and are not intended to limit the scope of the embodiments of the present application. For example, different fields, different information, etc. are distinguished.

The "pre-defining" may be implemented by pre-storing corresponding codes, tables, or other means for indicating relevant information in the device, and the present application is not limited to the specific implementation manner. Where "save" may refer to saving in one or more memories. The type of memory may be any form of storage medium, and the application is not limited in this regard.

The "protocol" referred to in the embodiments of the present application may refer to a standard protocol in the field of communications, and may include, for example, a long term evolution (long term evolution, LTE) protocol, a New Radio (NR) protocol, and related protocols applied in future communication systems, which are not limited in this respect.

The present application will present various aspects, embodiments, or features about a system comprising a plurality of devices, components, modules, etc. It is to be understood and appreciated that the various systems may include additional devices, components, modules, etc. and/or may not include all of the devices, components, modules etc. discussed in connection with the figures. Furthermore, combinations of these schemes may also be used.

In the embodiments of the present application, words such as "exemplary," "for example," "illustratively," "as (another) one example," and the like are used to mean serving as an example, instance, or illustration. Any embodiment or design described herein as "exemplary" is not necessarily to be construed as preferred or advantageous over other embodiments or designs. Rather, the term use of an example is intended to present concepts in a concrete fashion.

The terms "comprising," "including," "having," and variations thereof mean "including but not limited to," unless expressly specified otherwise.

"At least one" means one or more, and "a plurality" means two or more. "and/or", describes an association relationship of an association object, and indicates that there may be three relationships, for example, a and/or B, and may indicate: a alone, a and B together, and B alone, wherein a, B may be singular or plural. The character "/" generally indicates that the context-dependent object is an "or" relationship. "at least one of" or the like means any combination of these items, including any combination of single item(s) or plural items(s). For example, at least one (one) of a, b, and c may represent: a, or b, or c, or a and b, or a and c, or b and c, or a, b and c. Wherein a, b and c can be single or multiple respectively.

The descriptions of "when … …", "in the case of … …", "if" and "if" etc. all refer to the corresponding processing that the device will perform under some objective condition, are not intended to limit the time, nor do the device require any judgment in the implementation, nor are other limitations meant to be implied.

In the embodiment of the application, the description related to the network element a sending a message, information or data to the network element B and the network element B receiving the message, information or data from the network element a is intended to illustrate to which network element the message, information or data is sent, but not to limit whether the message, information or data is sent directly or indirectly via other network elements.

In embodiments of the present application, various aspects, embodiments, or features will be presented in terms of systems that include a number of devices, components, modules, and the like. It should be understood that each system may include all devices, components, modules, or only portions thereof, as referred to in the schematic diagram of the network architecture, and is not limited thereto.

The technical scheme of the application is described below.

The embodiments provided by the present application can be applied to various communication systems. For example, fifth generation (5 ^th generation, 5G) or New Radio (NR) systems, long term evolution (long term evolution, LTE) systems, LTE frequency division duplex (frequency division duplex, FDD) systems, LTE time division duplex (time division duplex, TDD) systems, and the like. The embodiments provided by the application can also be applied to non-terrestrial communication network (non-TERRESTRIAL NETWORK, NTN) communication systems such as satellite communication systems. Embodiments provided herein may also be applied to device-to-device (D2D) communications, vehicle-to-everything (V2X) communications, machine-to-machine (machine to machine, M2M) communications, machine-type communications (MACHINE TYPE communications, MTC), and internet of things (internet of things, ioT) communications systems or other communications systems. The embodiments provided by the application can also be applied to future communication systems, such as sixth generation mobile communication systems. In addition, the method can be extended to similar wireless communication systems, such as wireless-fidelity (WiFi), worldwide interoperability for microwave access (worldwide interoperability for microwave access, WIMAX), and third generation partnership project (3rd generation partnership project,3GPP) related communication systems, without limitation.

Illustratively, fig. 1 shows a schematic diagram of a network architecture.

As shown in fig. 1, the communication system is exemplified by a 5G system (the 5th generation system,5GS). The network architecture may include three parts, namely a User Equipment (UE) part, a Data Network (DN) part, and an operator network part. Wherein the operator network may comprise one or more of the following network elements: a (radio) access network (R) AN device, a user plane function (user plane function, UPF) network element, AN authentication server function (authentication server function, AUSF) network element, AN access and mobility management function (ACCESS AND mobility management function, AMF) network element, a session management function (session management function, SMF) network element, a network slice selection function (network slice selection function, NSSF) network element, a network opening function (network exposure function, NEF) network element, a network function library function (network repository function, NRF) network element, a policy control function (policy control function, PCF) network element, a unified data management (unified DATA MANAGEMENT, UDM) network element, and AN application function (application function, AF) network element. In the above-described operator network, the portion other than the RAN portion may be referred to as a core network portion.

Wherein:

A UE may also be referred to as a terminal, user, access terminal, subscriber unit, subscriber station, mobile station, remote terminal, mobile device, user terminal, terminal device, wireless communication device, user agent, or user equipment, etc., hereinafter collectively referred to as a terminal for ease of description. A terminal is a device that can access a wireless communication network. The terminal and the (R) AN may communicate using AN air interface technology (e.g., NR or LTE). Air interface technology (such as NR or LTE) can also be used for communication between terminals. Specifically, the terminal may be a mobile phone (mobile phone), a tablet computer (pad), a computer with a wireless transceiving function, a Virtual Reality (VR) terminal, an augmented reality (augmented reality, AR) terminal, a terminal in satellite communication, a terminal in an access backhaul (INTEGRATED ACCESS AND backhaul, IAB) system, a terminal in a WiFi communication system, a terminal in industrial control (industrial control), a terminal in unmanned (SELF DRIVING), a terminal in remote medical (remote medical), a terminal in a smart grid (SMART GRID), a terminal in transportation security (transportation safety), a terminal in a smart city (SMART CITY), a terminal in a smart home (smart home), and the like. The embodiment of the application does not limit the specific technology and the specific equipment form adopted by the terminal.

The (R) AN may be a device for communicating with a terminal or a device for accessing a terminal to a wireless communication network. The (R) AN may be a node in a radio access network. For example, a base station (base station), an evolved NodeB (eNodeB), a transmission and reception point (transmission reception point, TRP), a home base station (e.g., home evolved NodeB, or home Node B, HNB), a Wi-Fi Access Point (AP), a mobile switching center, a next generation NodeB (gNB) in a 5G mobile communication system, a next generation base station in a sixth generation (6th generation,6G) mobile communication system, an access network device or a module of an access network device in an open RAN (ora) system, or a base station in a future mobile communication system, etc. The (R) AN may also be a module or unit that performs a function of a base station part, for example, a Centralized Unit (CU), a Distributed Unit (DU), a remote radio unit (remote radio unit, RRU), or a baseband unit (BBU), etc. The (R) AN may also be a device in the D2D communication system, the V2X communication system, the M2M communication system, the IoT communication system that assumes the functionality of a base station, etc. The (R) AN may also be a network device in the NTN, i.e. the (R) AN may be deployed on AN aerial platform or satellite. The (R) AN may be a macro base station, a micro base station, AN indoor station, a relay node, a donor node, or the like. The embodiment of the present application does not limit the specific technology, device configuration and name used for the (R) AN.

The UPF is mainly responsible for forwarding and receiving user data in the terminal. For example, the UPF may receive user plane data from the DN and send the user plane data to the terminal through the access network device. The UPF may also receive user plane data from the terminal through the access network device and forward to the DN. The transmission resources and scheduling functions in the UPF network element that serve the terminal are controlled by the SMF management.

DN is mainly used for an operator network providing data services for terminals. Such as the Internet (Internet), a third party's service network, or an IP multimedia service (IP multimedia-MEDIA SERVICE, IMS) network, etc.

AUSF support access authentication for 3GPP and non-3 GPP.

The AMF is mainly responsible for the signaling processing part, for example: access control, mobility management, attach and detach, gateway selection, etc. In the case of providing services for a session in a terminal, the AMF may provide a storage resource of a control plane for the session to store a session identity, an SMF network element identity associated with the session identity, etc.

The SMF is mainly responsible for user plane element selection, user plane element redirection, internet protocol (internet protocol, IP) address allocation, bearer establishment, modification and release, quality of service (quality of service, qoS) control, etc.

NSSF is mainly responsible for network slice selection, and determines network slice examples which the terminal is allowed to access according to slice selection auxiliary information, subscription information and the like of the terminal.

NEF mainly supports the interaction of 3GPP networks and third party application security.

NRF is mainly used for storing network function entities, description information of services provided by the network function entities, and the like.

The PCF is mainly responsible for policy control decisions, policy rules providing control plane functions, traffic based charging control functions, etc.

The UDM is mainly responsible for subscription data management of the terminal, including storage and management of terminal identification, access authorization of the terminal, and the like.

AF mainly supports interactions with the 3GPP core network to provide services, such as influencing data routing decisions, policy control functions, or providing services to third parties to the network. The AF can be an AF deployed by an operator network, or can be a third party AF.

It should be understood that the functions or network elements AMF, SMF, UPF, PCF, UDM, AUSF, NSSF, NEF, NRF, AF shown in fig. 1, etc., may be understood as network elements for implementing different functions, for example, may be combined into network slices as needed. The network elements may be independent devices, may be integrated in the same device to implement different functions, or may be network elements in hardware devices, or may be software functions running on dedicated hardware, or may be virtualized functions instantiated on a platform (for example, a cloud platform), where the specific form of the network elements is not limited by the present application.

The 5GS architecture supports not only the wireless technology defined by the 3GPP standards group to access the core network, but also non-3GPP (non-3 GPP) access technologies to access the core network through non-3GPP interworking functions (non-3GPP interworking function,N3IWF) or next generation packet data gateways (next generation PACKET DATA GATEWAY, ngPDG). When the 5G core network supports non-trusted non-3GPP (which may be abbreviated as N3G) access, trusted non-3GPP access and/or wired network access. The non-trusted non-3GPP access network can be a non-trusted wireless local area network (wireless local area network, WLAN) access network, the trusted non-3GPP access network comprises a trusted WALN network and the like, and the wired access network comprises a fixed home network access and the like.

When the 5G core network supports untrusted non-3GPP (N3G for short) access, the network architecture may be as shown in fig. 2. The N3IWF in fig. 2 is an untrusted non-3GPP access gateway.

When the 5G core network supports trusted non-3GPP access and/or wired network access, the network architecture is similar to the untrusted non-3GPP access network architecture, and the untrusted non-3GPP access gateway (e.g., N3IWF in FIG. 2) may be replaced with a trusted WLAN access gateway (e.g., trusted non-3GPP gateway function (trusted non-3GPP gateway function,TNGF)), or with a wired network access gateway (e.g., wired access gateway function (WIRELINE ACCESS GATEWAY function, W-AGF)). The access network devices between the UE and the access gateway include WLAN access points (WLAN ACCESS points, WLAN APs), wired network access network devices (e.g., fixed access networks (fixed Access network, FAN)), switches, routers, and the like.

In the network architecture shown in fig. 1 and 2, the network elements may communicate with each other via interfaces. The interfaces between the network elements can be point-to-point interfaces or service interfaces, and the application is not limited.

It should be understood that the network architectures shown in fig. 1 and fig. 2 are merely exemplary, and the network architectures to which the embodiments of the present application are applied are not limited, and any network architecture capable of implementing the functions of the respective network elements described above is applicable to the embodiments of the present application.

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

Core network functions, such as AMFs, in the above network architecture are typically deployed in the existing network using a pool mechanism. I.e. a location area is served by a plurality of functionally identical core network functions, which form a pool, each core network function in the pool being connected to one or more access network devices. When a core network function in the pool fails, services can be continued to be provided by other core network functions in the pool.

Fig. 3 is a schematic diagram of deployment of core network functions using a pool mechanism. As shown in fig. 3, each AMF in the AMF pool (e.g., AMFs 1-4 in fig. 3) is connected to a base station presence device.

Because each AMF in the AMF pool is connected with the base station by the device, when the AMF is on-line or off-line in the AMF pool, nodes (such as the base station, the routing device between the base station and the AMF, and the terminal) outside the AMF pool need to sense the on-line or off-line of the network function in the pool, i.e. the nodes outside the AMF pool need to perform complex parameter configuration on the nodes outside the AMF to adapt to the change of the connection relationship caused by the on-line or off-line of the network function, which is specifically as follows.

For the AMF to be on-line, when the new AMF is on-line in the AMF pool, a connection between the new AMF and the base station needs to be configured, for example, a communication address of the new AMF is notified to each base station, then a connection establishment procedure between the new AMFs is initiated by the base station, for example, a communication address of each base station is configured to the new AMF, and a connection establishment path to each base station is initiated by the AMF. In this process, in order to make the base station establish a connection with the new AMF, it is necessary to ensure that the communication address of the new AMF has full network reachability, so the routing device between the base station and the new AMF also needs to perform corresponding routing update. It can be seen that when an AMF is newly added in the AMF pool, a plurality of network elements are affected, and complex parameter configuration is required.

For AMF offline, when a certain AMF in the AMF pool is offline, similar to AMF offline, the base station needs to perceive this as well. In particular, when a certain AMF goes offline due to a fault, the user traffic of the fault AMF node service is also affected. Specifically, when an AMF fails, the base station needs to perceive that the AMF fails and select other AMFs for the terminal. In this process, if the reselected AMF cannot acquire the user context, the terminal needs to be re-registered to the network side, which seriously affects the user experience, or even if the reselected AMF can acquire the user context, the reselected AMF needs to reassign the temporary identifier to the terminal and update the temporary identifier to the terminal side, so that the terminal is affected, and signaling waste exists.

Here, only the AMF pool is taken as an example.

Based on the above, the nodes or network elements affected by the uplink and downlink flows of the nodes in the AMF pool are more and more information needs to be configured. Therefore, the uplink and downlink flows of the nodes in the AMF pool are complex and have great signaling overhead, and flexible uplink and downlink of the nodes cannot be realized. Moreover, when a certain AMF is disconnected from the terminal due to a fault, the terminal may be affected, which may cause damage to the user service.

In addition, because the uplink and downlink flows of the nodes in the AMF pool are complex, when the total number of users served by the AMF pool changes, for example, the number of users is significantly different between day and night, it is difficult for the network side to flexibly adjust the use of network resources (for example, some AMFs can be offline when the number of users is small, and some AMFs can be online when the number of users is large), which results in network resource waste.

In view of the above problems, the present application provides a communication method and a communication device, which can implement that a core network function performs a routing operation for a message from a terminal, so that a node outside a core network function pool may not perceive the online or offline of the core network function in the pool, which is helpful for reducing signaling overhead and reducing the influence on user services.

To facilitate an understanding of the aspects of the present application, a distributed hash table (distributed hash table, DHT) technique is first described.

Fig. 4 is a schematic diagram of a DHT ring.

Fig. 4 shows a DHT ring formed based on DHT technology, which ring is a spatial domain of 0 to N, N being an integer value and being to the power N of 2. Each device may correspond to a particular value in the spatial domain referred to as the index value, i.e., key, for that device. Files stored in the device may also correspond to a specific value in the 0-N spatial domain, referred to as the index value of the file, which may also be represented by a key.

After the device is mapped to the DHT ring, a precursor and successor relationship may be formed based on the index value of the device. As shown in fig. 4, N0, N9, N15, N22, N33, N42, N52, etc. are index values of devices, and taking the N22 node as an example, a predecessor node of the N22 node is the N15 node, and a successor node of the N22 node is the N33 node.

Each device is responsible for storing space that is the space behind its predecessor node. For example, the space that the N33 node is responsible for is N22-N33, i.e. when the index value of a file falls into the space, the file is responsible for storage by the N33 node. For example, when the index value of the file x=11, the file X is stored by the N15 node.

Each node maintains a routing table, and the specific storage node of the file with a certain index value can be found based on the routing table maintained by the node. One possible form of routing table is illustrated in fig. 4 with the routing table of the N9 node.

One possible way is to modulo the identity of the device or file by a function f (x) operation, and obtain the corresponding index value. For example, when the identity of a device is its IP address, the index value of this device=f (IP address of the device) mod N. For another example, when the identification of a file is a file name, the index value of this file=f (file name) mod N,

Alternatively, the function f (x) may be a Hash (Hash) function. The application is not limited to the specific expression form of the hash function, i.e. the hash function can be any hash function.

It should be noted that the operation of modulo operation of the function F (x) described above may be collectively referred to as a function operation F (x), and F (x) mod N will be hereinafter denoted by F (x).

Of course, F (x) may be another function operation manner that may be used to calculate an index value of a device or a file, and the present application is not limited to the specific expression form of F (x). The function operation F (x) may also be simply referred to as function operation F.

The DHT ring realizes self-organization based on an algorithm and can support dynamic online and offline of nodes. Common node up-down algorithms include: each node periodically performs stabilization a stability algorithm, asking if its successor node's predecessor node is itself to update its successor node and entries in the routing table.

Specifically, the algorithm may comprise the steps of:

0) Add (n 0) (join (n 0)): n joins a DHT ring, of which one node n0 is known;

1) Stabilizing (stabilize) n queries the predecessor node P of the successor node to determine if P should be a successor node to n, i.e., when P is not n itself, it is said that P is newly added, at which point the successor node to n is set to P;

2) Notification (n 0) (notify (n 0)): n0 informs n of its existence, and if n has no preamble node or n0 is closer to n than n existing preamble nodes at this time, n sets n0 as the preamble node;

3) Fix_fingers: the routing table is modified.

For a more detailed description of DHT technology reference is made to the prior art and will not be described in detail here.

In the present application, a Network Function (NF) group may be constructed based on DHT technology.

Fig. 5 is an example of NF groups based on DHT technology.

The NF group consisting of the NF comprises the NF with the same logic function, the NF in the NF group provides service for a certain position area, and when a certain NF in the NF group fails, other NF in the NF group can continue to provide service. The present application is not limited to a specific service function of the NF, and for example, the NF may support an authentication service, a subscription data storage service, a registration service, a session service, or a plurality of services among the above-mentioned plurality of services. NF groups may also be referred to as NF pools. NF may be a core network function.

As shown in fig. 5, the area a is served by a group of NFs, each NF may correspond to at least one logical node on the DHT ring, for example NF1 corresponds to logical node N200 on the DHT ring, device NF2 corresponds to logical nodes N350 and N100 (being newly added nodes) on the DHT ring, and device NF3 corresponds to logical node N150 on the DHT ring.

When the NFs provide services for the terminals, the terminals are files processed by the NFs, each NF can maintain a routing table, and NFs providing services for the terminals can be determined based on the routing table and index values of the terminals. For example, when the index value of the terminal=300, the terminal is served by the N350 node closest to 300, i.e., the terminal is served by NF 2.

The system framework mainly includes NF group and Service Framework (SFW) functions. Wherein, a ring topology structure is formed between the NFs in the NF group, the application is not limited to the technology used for forming the NF group, for example, the NFs form a ring based on DHT technology, and the specific description may refer to fig. 5. There is a connection between the SFW and NF groups. In addition, there is a connection between the SFW and the access device or other NF functions outside the NF group, where a cellular radio access technology, such as LTE, 5G NR, or 6G radio air interface technology, may be used between the access device and the terminal, or a non-3GPP access technology, such as wifi technology, wired technology, or ultra-wideband (UWB) technology, etc., may be used between the access device and the terminal.

The communication method provided by the application is described below.

The NF is referred to as a core network function in the method 700, which may also be referred to as a core network node, a core network device, etc. The core network function group in the method 700 includes a plurality of core network functions having the same service function, and the manner in which the plurality of core network functions (the first core network function, the second core network function, the third core network function, and the third core network function referred to below) form the core network function group may refer to fig. 4 to 6. The core network function in the present application may be physical devices, logical devices or virtual devices, and is not limited.

Method 700 includes at least some of the following.

In step 701, the first terminal sends a first message to the SFW, or the SFW receives the first message from the first terminal.

The first message is a message sent to the core network function by the first terminal, and the specific type and function of the first message are not limited by the application.

In step 702, the sfw searches for a core network function corresponding to the first terminal.

One possible implementation manner is that the corresponding relation between the terminal and the core network function is stored in the SFW, and the SFW may search the core network function corresponding to the first terminal according to the corresponding relation.

The results of the SFW lookup include the following:

Case 1: the SFW searches for a first core network function corresponding to the first terminal. In this case, the SFW may perform step 703a, step 703a being specifically as follows.

At step 703a, the SFW sends a first message to the first core network function, or the first core network function receives the first message from the SFW.

Optionally, for case 1, if the SFW does not receive a response message for the first message from the first core network function, such as an Acknowledgement (ACK) message, within a preset time, the SFW may determine that the first core network function is offline or fails, the SFW may send the first message to the ingress core network function, and the ingress core network function may be any core network function in the core network function group, where the ingress core network function may be any core network function in the core network function group other than the first core network function.

Case 2: the SFW does not find the first core network function corresponding to the first terminal. In this case, the SFW may perform step 703b, step 703b being specifically as follows.

Step 703b, the SFW sends a first message to the ingress core network function, or the ingress core network function receives the first message from the SFW.

The ingress core network function may be any core network function in the core network function group.

Case 3: the SFW finds the first core network function corresponding to the first terminal, but the SFW already knows that the first core network function has been down-line or has failed. In this case, the SFW may also perform step 703b.

Optionally, for case 3, prior to step 702, method 700 may further include: the SFW determines that the first core network function has been down or failed.

One possible implementation, before step 702, the SFW sends a seventh message to the first core network function; if the SFW does not receive a response message, such as an ACK message, from the first core network function for the seventh message within a preset time, the SFW may determine that the first core network function is offline or fails.

In another possible implementation, the SFW determines that the first core network function is down or fails when the connection between the first core network function and the SFW is in a disconnected state.

Alternatively, an alternative to step 702 is to: the SFW may send the first message directly to the ingress core network function without looking up the core network function corresponding to the first terminal.

The operations performed by the core network function are described below, and the operations performed by the first core network function are the same as those performed by the ingress core network function, and hereinafter, the operations of the ingress core network function are exemplified by the operations of the first core network function, and the operations of the ingress core network function may refer to the operations of the first core network function and will not be described in detail.

After receiving the first message, the first core network function may perform step 704, step 704 being specifically as follows.

In step 704, the first core network function determines whether the first message is processed by the first core network function according to the first index value range corresponding to the first core network function and the index value of the first terminal.

Wherein "determining whether the first message is processed by the first core network function" may be understood as: it is determined whether the first terminal is served by the first core network function or whether the first core network function serves the first terminal or whether the first core network function is responsible for the first terminal or whether the first terminal is under the first core network function. The first message is processed by the first core network function when the first terminal is served by the first core network function, e.g. when the first message is a registration request message, the context of the first terminal is generated by the first core network function from the first message. When the first core network function does not serve the first terminal, the first message is not processed by the first core network function, e.g. when the first message is a registration request message, the context of the first terminal is not generated by the first core network function from the first message.

The first index value range is a set of index values of the terminal that the first core network function supports services, in other words, the terminal is served by the first core network function when the index value of the terminal falls within the first index value range, and the terminal is not served by the first core network function when the index value of the terminal does not fall within the first index value range. It should be noted that the method 700 only uses the first core network function as an example to describe the solution of the present application, where each core network function in the core network function group to which the first core network function belongs corresponds to one index value range, and there is no intersection between each index value range.

One possible implementation, the first index value range is a range between the index value of the first core network function and the index value of the fourth core network function. The index value of the fourth core network function is adjacent to the index value of the first core network function, and the index value of the fourth core network function is smaller than the index value of the first core network function; or when the first core network function is the core network function with the minimum index value in the core network function group, the index value of the fourth core network function is adjacent to the index value of the first core network function, and the fourth core network function is the core network function with the maximum index value in the core network function group. In other words, the fourth core network function is a preamble node of the first core network function, which is responsible for the space between the first core network function and its preamble node.

In the present application, the index value of the first core network function may be obtained by performing the function operation F on the identification of the first core network function, where the index value of the first core network function=f (identification of the first core network function). The identification of the first core network function may be any information that can uniquely determine the first core network function. Optionally, the identification of the first core network function includes at least one of the following information: a full domain name (fully qualified domain name, FQDN) of the first core network function, or a communication address of the first core network function.

In the present application, the index value of the first terminal may be obtained by performing the function operation F on the identification of the first terminal, where the index value of the first terminal=f (identification of the first terminal). The identifier of the first terminal may be any information capable of uniquely determining the first terminal. Optionally, the identification of the first terminal includes at least one of the following information: a subscriber permanent identity (subscription PERMANENT IDENTIFIER, SUPI), a subscriber hidden identifier (subscription concealed identifier, SUCI), a general public subscriber identity (generic public subscription identifier, GPSI), a permanent equipment identifier (PERMANENT EQUIPMENT IDENTIFIER, PEI), or a mobile subscriber international ISDN/PSTN number (mobile subscriber international ISDN/PSTN number, MSISDN), where ISDN is an abbreviation for integrated services digital network (INTEGRATED SERVICE DIGITAL network), PSTN is a public switched telephone network (public switched telephone network), etc. The MSISDN may be understood as an identity that the UE may disclose externally, such as a phone number of the UE, etc.

It is noted that the function operation for calculating the index value of the first core network function is the same as the function operation for calculating the index value of the first terminal. F (x) may be any functional operation method that may be used to calculate an index value of a core network function or a terminal, and is not limited.

Optionally, step 704 specifically includes: when the index value of the first terminal belongs to the first index value range, the first access network device can determine that the first core network function provides service for the first terminal, namely, the first core network function processes the first message; when the index value of the first terminal does not belong to the first index value range, the first access network device may determine that the first terminal is not served by the first core network function, i.e. the first core network function does not process the first message.

When the index value of the first terminal does not belong to the first index value range, the subsequent operation of the first core network function may take many forms, which is specifically as follows.

Mode a: step 705a is performed as follows.

Step 705a, the first core network function sends a first message to a second core network function according to the index value of the first terminal, where the second core network function is a core network function in the core network function group that provides services for the first terminal.

I.e. when the first core network function does not serve the first terminal, the first core network function forwards the first message to the second core network function serving the first terminal.

The implementation manner of the first core network function sending the first message to the second core network function according to the index value of the first terminal is similar to the manner of searching for the file storage node according to the index value of the file in the DHT technology, and will not be described in detail.

It should be noted that the first core network function may or may not pass through other core network functions in the core network function group in the process of sending the first message to the second core network function, i.e. the first message may reach the second core network function after one or more hops, which is not limited by the present application.

Mode B: steps 705a-1 to 705b-2 are performed as follows.

Step 705b-1, the first core network device obtains information of the second core network function according to the index value of the first terminal.

The second core network function is a core network function in the core network function group for providing services for the first terminal.

Optionally, the information of the second core network function includes at least one of the following information: an identification of the second core network function, an index value of the second core network function, or a communication address of the second core network function.

The implementation manner of the first core network function to acquire the information of the second core network function according to the index value of the first terminal is similar to the manner of searching for the file storage node according to the index value of the file in the DHT technology, and will not be described in detail.

It should be noted that, in the process of the first core network function acquiring the information of the second core network function, the first core network function may or may not acquire the information of the second core network function through other core network functions in the core network function group, that is, after one or more hops, the application is not limited.

Step 705b-2, the first core network function sends information of the second core network function to the SFW, or the SFW receives information of the second core network function from the first core network function.

After receiving the information of the second core network function, the SFW may perform step 705b-3, as follows.

Step 705b-3, the sfw sends the first message to the second core network function according to the information of the second core network function.

For mode B, that is, when the first core network function does not provide services for the first terminal, the first core network function obtains information of the second core network function that provides services for the first terminal, and feeds back the information of the second core network function to the SFW, so that the SFW may send the first message to the second core network function.

In fig. 7, the first core network function receives the first message from the SFW as an example. In other scenarios, the first core network function may also receive the first message of the first terminal from other core network functions in the group of core network functions, e.g. when the first core network function is the second and subsequent core network functions in the first message transmission procedure, the first core network function receives the first message from the other core network functions. In other words, each core network function in the core network function group may determine whether to process the first message by itself according to its corresponding index value range and the index value of the first terminal after receiving the first message.

Taking the first core network function as an example, the description is given below of the on-line or off-line of the core network function in the core network function group.

In another scenario of the above-described embodiment of the present application, the method 700 further comprises: when the first core network function is added into the core network function group, or called when the first core network function is on line, the first core network function determines a third core network function according to the index value of the first core network function; the third core network function acquires a first context, and an index value of a terminal corresponding to the first context belongs to a first index value range; the third core network function sends the first context to the first core network function, or the first core network function obtains the first context from the third core network function. Wherein the index value of the third core network function is adjacent to the index value of the first core network function, and the index value of the third core network function is greater than the index value of the first core network function; or the index value of the third core network function is adjacent to the index value of the first core network function, the third core network function is the core network function with the smallest index value in the core network function group, the first core network function is the core network function with the largest index value in the core network function group, in other words, the third core network function is the subsequent node of the first core network function in the core network function group.

I.e. when the first core network function joins the core network function group, the first core network function obtains the context of the terminal served by itself from its successor node.

The first core network function determines a third core network function according to the index value of the first core network function, which may be referred to as: the first core network function searches for the third core network function in the core network function group according to the index value of the first core network function, and a specific searching manner is similar to that of the device searching for its own subsequent node in the DHT technology, which is not described in detail herein.

The information of the subsequent node of the first core network function may be preconfigured in the first core network function through the network management system when the first core network function is on line, which is not limited.

It should be further noted that the first context may include a context of one or more terminals, where index values of the one or more terminals fall within a first range of index values.

Optionally, the first context includes: terminal identification and/or index value of the terminal.

Optionally, the first context may further include at least one of the following information: the URI of the terminal, the identification of the SFW corresponding to the terminal, the communication address of the SFW corresponding to the terminal, the location information of the terminal, or the access information of the terminal.

Optionally, in the case of storing the correspondence between the core network functions and the terminals served by them in the SFW, the method 700 further includes: the first core network function sends a second message to the SFW, or the SFW receives the second message from the first core network function, wherein the second message is used for indicating the first context to migrate to the first core network function; the SFW stores the corresponding relation between the terminal corresponding to the first context and the first core network function. In this way, the SFW may update the terminal corresponding to the first context to correspond to the first core network function, so that when receiving the message sent by the corresponding terminal, the SFW may query the first core network function serving the corresponding terminal.

Optionally, the second message includes information of the terminal corresponding to the first context and information of the first core network function; the information of the terminal corresponding to the first context comprises at least one of the following information: terminal identification, index value of terminal, or communication address of terminal; and/or the information of the first core network function comprises at least one of: an identification of the first core network function, an index value of the first core network function, or a communication address of the first core network function.

In the present application, there are many implementation manners, but not limited, for the first core network function to acquire the first context from the third core network function.

One possible implementation manner, the first core network function sends a third message to the third core network function, where the third message is used to request the context of the terminal; after receiving the third message from the first core network function, the third core network function determines a first index value range according to the index value of the first core network function, and acquires a first context according to the first index value range; the third core network function sends a fourth message to the first core network function, the fourth message including the first context. I.e. the third core network function determines the first range of index values and obtains the first context from the first range of index values.

In another possible implementation, the first core network function sends a third message to the third core network function, the third message being for requesting a terminal context, and the third message including the first index value range; after receiving a third message from the first core network function, the third core network function obtains a first context according to a first index value range in the third message; the third core network function sends a fourth message to the first core network function, the fourth message including the first context. I.e. the first range of index values is provided by the first core network function to the third core network function.

In another scenario of the above-described embodiment of the present application, the method 700 further comprises: when the first core network function is offline, the first core network function backs up the second context to the third core network function, the index value of the terminal corresponding to the second context belongs to the first index value range, and the description of the third core network function can refer to the above and will not be repeated. The context backup mode is suitable for a scenario of planned offline of core network functions, for example, when the number of users is small, some core network functions can be offline so as to reduce energy consumption. In other words, when the first core network function is scheduled to be down-line, the first core network function may backup the context of the terminal for which it is responsible to its subsequent nodes in advance, so that even if the first core network function is down-line, the third core network function may serve the terminals.

Wherein the second context may comprise a context of one or more terminals having index values falling within the first range of index values. The second context may be the same as or different from the first context, for example, after the first core network function is brought online, if a new terminal (a terminal other than the terminal corresponding to the first context) is registered in the first core network function and/or a terminal in the terminal corresponding to the first context leaves the first core network function, the second context is different from the first context.

Optionally, the second context includes: terminal identification and/or index value of the terminal.

Optionally, the second context may further include at least one of the following information: the URI of the terminal, the identification of the SFW corresponding to the terminal, the communication address of the SFW corresponding to the terminal, the location information of the terminal, or the access information of the terminal.

Optionally, in the case of storing the correspondence between the core network functions and the terminals served by them in the SFW, the method 700 further includes: the first core network function sends a fifth message to the SFW, or the SFW receives the fifth message from the first core network function, wherein the fifth message is used for indicating the second context to migrate to the third core network function; the SFW stores the corresponding relation between the terminal corresponding to the second context and the third core network function. In this way, the SFW may update that the terminal corresponding to the second context corresponds to the third core network function, so that when receiving the message sent by the corresponding terminal, the SFW may query the third core network function serving the corresponding terminal.

Optionally, the fifth message includes information of the terminal corresponding to the second context and information of the third core network function; wherein the information of the terminal corresponding to the second context includes at least one of the following information: terminal identification, index value of terminal, or communication address of terminal; and/or the information of the third core network function comprises at least one of: an identification of the third core network function, an index value of the third core network function, or a communication address of the third core network function.

In another scenario of the above-described embodiment of the present application, the method 700 further comprises: when the first core network function stores the context of the second terminal, the first core network function backs up the context of the second terminal to the third core network function. The term "the first core network function stores the context of the second terminal" as used herein is understood to be: the second terminal registers with the first core network function and the context of the second terminal is stable. In other words, the first core network function backs up the context of the terminals registered to the first core network function to the third core network function at any time, so that the third core network function can provide services for the terminals even if the first core network function is accidentally disconnected (e.g., disconnected due to a fault). The context backup mode is suitable for not only the scene of planning and arranging the core network function to be offline, but also the scene of unexpected core network function to be offline.

Alternatively, when the context of the subsequent second terminal is deleted from the first core network function, i.e. the second terminal leaves the first core network function, the first core network function may send a sixth message to the third core network function, or the third core network function receives a sixth message from the first core network function, where the sixth message is used to indicate that the context of the second terminal is deleted.

Optionally, the context of the second terminal includes: the identity of the second terminal and/or the index value of the second terminal.

Optionally, the context of the second terminal further comprises at least one of the following information: the URI corresponding to the second terminal, the identifier of the SFW corresponding to the second terminal, the communication address of the SFW corresponding to the second terminal, the location information of the second terminal, or the access information of the second terminal.

The communication method provided by the present application is described in detail below with reference to specific examples.

In the following examples, NF may correspond to the above core network function, NF key may correspond to an index value of the core network function, UEkey may correspond to an index value of the terminal.

The NFs in this embodiment form a distributed NF group based on DHT technology, and the functional services of each NF in the NF group are the same and are used to provide services for the same location area. Each NF and each NF-serviced UE may be mapped onto one DHT ring. Each NF may correspond to a value on the DHT ring, which may be referred to as NF key, i.e., an index value of NF. Based on the NF key, each NF in the NF group may form a precursor to successor relationship. Similarly, a UE served by the NF may also correspond to a value on the DHT ring, which may be referred to as UEkey, i.e., the index value of the UE. The UE served by each NF is a UE whose UE key follows the index value of the precursor node of each NF, or UE whose UE key is between the NF key of each NF and the NF key of the precursor node of each NF.

The service function of NF is not particularly limited in this embodiment. For example, the NF may be an NF that supports or is responsible for UE authentication, such as AUSF; or the NF may be an NF that supports or is responsible for UE subscription data storage, such as UDM; or the NF may be an NF that supports or is responsible for accessing registration services, such as AMF; or the NF may be an NF that supports or is responsible for session services, such as SMF; or the NF may be an NF that supports or is responsible for multiple ones of the services described above (e.g., all of the services described above) simultaneously.

The NF automatic on-line scheme provided by the present application is described below with reference to fig. 8.

In step 801, the ue establishes a connection with the NF.

In other words, the UE establishes a connection with the network side, or the UE is connected to NF, or the UE is registered with the network side. NF provides service for the UE. For ease of distinction, NF herein will be referred to as old NF hereinafter.

The manner in which the UE establishes a connection with the old NF may refer to the prior art and will not be described in detail herein.

For UEs establishing a connection with old NF, each UE has a corresponding UE key. The UE key may be a UE index value obtained after performing a function operation F on the UE identity, i.e., UE key=f (UE identity). The application is not limited to the device that calculates UEkey, and may be, for example, a UE, SFW, or old NF.

The UE identifier may be a permanent identifier of the UE or a temporary identifier of the UE. For example, the identity of the UE may be SUPI, SUCI, GPSI, PEI, MSISDN of the UE, or the like.

The function operation F (or called function F) may be any function operation for a key corresponding to a computing device or a file, and the specific expression form of the function operation F is not limited in the present application. For example, the function operation F is a HASH function, and of course, the function operation F may be any HASH function.

Optionally, through a process of establishing connection between the UE and the old NF, the SFW may obtain and store a correspondence between the UE identifier and the old NF, or obtain and store a correspondence between the UE key and the old NF.

Wherein the information of old NF includes at least one of the following information: old NF identifies, old NF key, or a communication address of old NF. The old NF key may be an old NF index value obtained by performing a function operation F on the old NF identifier, that is, old NFkey =f (old NF identifier). The function operation for calculating old NF key is the same as the function operation for calculating UE key.

The process of NF up is described below as shown in steps 802-808.

NF up, also referred to as NF, joins the NF group. For ease of distinction, the NF of the upper line will be referred to hereinafter as new NF.

In step 802, the dht route is updated (DHT routing update).

The process of DHT route update includes the following steps 1) to 3).

1) The new NF obtains the communication address and new NF identification of the entrance NF of the NF group, or obtains the communication address and new NF key corresponding to the new NF in the NF group.

The NF group entry NF may be any node in the NF group, or may be a fixed node in the NF group, or may be a successor node of new NF.

The communication address of the ingress NF may be any address that can reach the ingress NF, for example, an IP address of the ingress NF, etc.

The new NF identifier is any identifier that can uniquely identify newNF in the NF group, for example, a full domain name (fully qualified domain name, FQDN) of the new NF, and the like.

The new NF key may be a new NF index value obtained after performing the function operation F on the new NF identifier, that is, new NFkey =f (new NF identifier). The function operation for calculating new NF key is the same as the function operation for calculating UE key.

The embodiment of the application does not specifically limit the manner of acquiring the communication address, the new NF identifier or the new NF key of the NF group by the new NF.

One possible implementation may use a static configuration to configure new NF with at least one of the following information: the communication address, new NF identification, or new NF key of the ingress NF of the NF group.

Another possible implementation manner may be to configure at least one of the following information for new NF in a network management system configuration manner: the communication address, new NF identification, or new NF key of the ingress NF of the NF group.

Optionally, new NF may also obtain an identification (hereinafter referred to as an entry NF identification) and an index value (hereinafter referred to as an entry NF key) of the entry NF of the NF group.

The identity of the inlet NF is any identity which can uniquely identify the inlet NF in the NF group, such as the FQDN of the inlet NF, etc.

The entry NF key may be an entry NF index value obtained after performing the function operation F on the entry NF identifier, i.e., entry NFkey =f (entry NF identifier). The function operation for calculating the ingress NF key is the same as the function operation for calculating the UE key.

2) The new NF acquires the communication address of the subsequent node of the new NF and establishes connection with the subsequent node of the new NF.

The communication address of the successor node NF may be any address that can reach the successor node NF, for example, an IP address of the successor node NF, etc.

In case 1, when the successor node of new NF is the ingress NF, new NF has acquired the communication address of the successor node of new NF through step 1).

In case 2, when the successor node of new NF is not the ingress NF, the new NF interacts with the ingress NF, and obtains the communication address of the successor node of new NF. Specifically, the portal NF may acquire the communication address of the successor node of the new NF based on the request of the new NF, and send the acquired communication address to the new NF. For example, the new NF may send a request message #1 to the ingress NF, where the request message #1 carries a new NF identifier or a new NF key, and the ingress NF may search a routing table of the ingress NF for a communication address of a successor node of the new NF, and if the routing table of the ingress NF does not find a communication address of a successor node of the new NF, the ingress node may request the communication addresses of successor nodes of the new NF to other NFs in the NF group.

3) New NF obtains the routing table.

The routing table includes a correspondence between a UE identity and information of NF serving the UE, or includes a correspondence between a stored UE key and information of NF serving the UE. Thus, based on the routing table, new NF can search NF corresponding to a UE identifier or UE key, i.e. NF storing the context of the UE.

The manner in which the new NF obtains the routing table may refer to the manner in which the node on the existing DHT ring obtains the routing table, which is not described herein.

In step 803, new NF interacts with the successor node of new NF to obtain the communication address of SFW and optionally the SFW identifier.

In fig. 8, it is assumed that the successor node of new NF is old NF.

Specifically, new NF sends a request message #2 to old NF requesting the communication address of the SFW, old NF sends a response message #2 to new NF, the response message #2 including the communication address of the SFW. The SFW communication address may be an SFW IP address, or other address that may establish a connection with the SFW.

It should be noted that, the process of acquiring the communication address of the SFW and the optional SFW identifier by the new NF may also be described as a process of configuring the communication address of the SFW and the optional SFW identifier for the new NF.

Optionally, in the process of interaction between new NF and old NF, old NF may obtain new NF key and/or new NF identification of new NF.

It should be noted that new NF may interact with any NF in NF group to obtain the communication address of SFW and possibly SWF identification, and new NF is only taken as an example in fig. 8 from the successor node of new NE.

At step 804, new NF establishes a connection with SFW.

Specifically, the new NF sends a connection establishment request message to the SFW through the communication address of the SFW obtained in step 803; the SFW stores at least one of a new NF identifier, a new NF key or a new NF communication address, and sends a connection establishment completion message to the new NF.

Step 804 is an optional step.

In step 805, old NF determines the migrated UE context based on new NF identity or new NFkey.

When the old NF obtains the new NF mark, the old NF carries out function operation F on the new NF mark to obtain new NF key.

When the UE key is less than or equal to the new NF key, the UE is the migrated UE, i.e., the UE context for which the UE key is less than or equal to the new NF key is the migrated UE context.

The new NF flag or new NFkey here may be obtained in step 803.

Step 805 is an optional step.

In step 806, the new NF sends a request message #3 (e.g. context request) to the old NF for requesting to migrate the UE context.

Accordingly, old NF receives the request message #3 from new NF.

Optionally, the request message #3 may include a UE key data segment (UE key range) corresponding to the UE context requesting migration. The UE key data segment may be determined by new NF according to the new NF key, where the UE key data segment is a data segment less than or equal to the new NF key. For example, assuming new NF key=100, the UE key data segment is a UE key less than or equal to 100. For another example, assuming new NF key=100, and NF key=50 for the precursor node of new NF, the UE key data segment is 50-100.

When the request message #3 does not include the UE key data section, the UE key data section corresponding to the migrated UE context may be determined by old NF.

Step 806 is an optional step.

In step 807, old NF sends the migrated UE context to new NF.

Accordingly, new NF receives UE context from old NF.

The UE context may include a UE identity or a UE key, among other things.

Optionally, the UE context may further include at least one of the following information: URI, SFW identification, communication address of SFW, UE location information, or UE access information (e.g., access technology employed, etc.).

The URI is identification information of the UE context in a data storage space (DB), and is used for searching the UE context stored in the data storage space, for example, when the UE context is stored in other NF, the UE context can be searched based on the URI. The SFW identifier or the communication address of the SFW is the SFW identifier or the communication address of the SFW to which the UE is connected, i.e. the SFW identifier or the communication address of the SFW serving the UE.

In one possible implementation, the old NF may send the migrated UE context to the new NF based on the request message #3 of the new NF, such as by a context transfer message (context transfer). In this implementation, there are two cases as follows.

Case 1: the new NF request message #3 contains the UE key data segment corresponding to the migrated UE context. In this case, the old NF may send UE context to the new NF according to the UE key data section provided by the new NF, where the UE context is UE context that the UE key falls within the range of the UE key data section.

Case 2: the new NF request message #3 does not contain the UE key data segment corresponding to the migrated UE context. In this case, if step 805 has been performed before step 807, the old NF may send the UE context to the new NF based on the migrated UE context determined in step 805. If step 805 is not performed before step 807, the old NF determines the migrated UE context based on the new NF identifier or the new NF key, and sends the UE context to the new NF, wherein the manner in which the old NF determines the migrated UE context may refer to step 805, which is not described in detail.

In another possible implementation, the old NF may actively send the migrated UE context to the new NF, such as by a context transfer message (context transfer). As an example, when the old NF receives the request message #2 of the new NF to request the communication address of the SFW, the old NF may determine the migrated UE context based on the new NF identifier or the new NF key, and send the UE context to the new NF, where the manner of determining the migrated UE context by the old NF may refer to step 805, which will not be described herein.

It should be noted that, the communication address of the migrated UE context and the SFW may be sent in the same message, or may be sent in a different message, which is not limited.

In step 808, new NF sends a notification message to SFW.

Accordingly, the SFW receives the notification message from new NF. The notification message includes UE identities or UE keys of UEs responsible for the new NF, so as to notify the SFW that the contexts of the UEs have migrated to the new NF and the new NF provides services for the UEs.

The UE identity in the notification message may be a single UE identity or may be multiple UE identities, such as a list of UE identities. Similarly, the UE key in the notification message may be a single UE key or may be multiple UE keys, such as a UE key list. For example, when UE contexts of multiple UEs migrate to new NF and the multiple UEs correspond to the same SFW, the new NF may send a notification message carrying multiple UE identities or multiple UE keys.

After receiving the notification message of new NF, the SFW may store the correspondence between the UE identifier and the information of new NF, or obtain and store the correspondence between the UE key and the information of new NF. Wherein the information of new NF includes at least one of the following information: new NF identification, new NF key, or new NF communication address.

Optionally, the SFW may delete the correspondence between the UE identity and the old NF information in the notification message, or delete the correspondence between the UE key and the old NF information in the notification message.

It should be noted that if step 804 is not performed before step 808, the new NF may first establish a connection with the SFW, and the specific implementation may refer to step 804, which is not described herein.

Step 808 is an optional step.

After new NF is online, the transmission mode of the message between UE and NF is shown in steps 809-815.

In step 809, the ue sends a NAS message to the SWF.

Accordingly, the SFW receives the NAS message from the middle UE. Wherein the NSA message includes a UE identity or UE key.

The present embodiment does not limit the function of the NAS message. For example, the NAS message may be a NAS message in the access registration procedure, a NAS message in the session management procedure, or the like. Wherein the session management procedure comprises at least one of the following procedures: session establishment procedures, session update procedures, or session deletion or release procedures.

After receiving the NAS message of the UE, the SFW may search for a new NF corresponding to the UE based on the UE identity or UE key. Specifically, the operations performed by the SFW include case a and case B, as follows.

Case A

The SFW stores the corresponding relation between the UE identification and the new NF information or stores the corresponding relation between the UE key and the new NF information.

In case a, steps 810 and 811 may be continued, with steps 810 and 811 as follows.

Step 810, the sfw determines new NF information according to the UE identity or the UE key, and sends a request message #4 to the new NF according to the determined new NF information.

Accordingly, new NF receives request message #4. The request message #4 includes the received NAS message. The request message #4 may also include a UE identity or UE key.

This allows the NAS message to be handled by the new NF.

In step 811, the ue completes various procedures, such as access registration, session management, etc., through SFW and new NF.

Specifically, similar to the NAS messages in step 810, the other NAS messages of the UE are forwarded by the SFW to the new NF, and the new NF processes the NAS messages, so as to complete the access registration, session management, and other processes of the UE.

Case B

The corresponding relation between the UE identification and the new NF information and the corresponding relation between the UE key and the new NF information are not stored in the SFW. In case B, the operations to be performed subsequently may again include case 1 and case 2, as follows.

Case 1

The SFW stores the corresponding relation between the UE identification and the old NF information or stores the corresponding relation between the UE key and the old NF information. For example, in step 801, the correspondence between the UE identity stored in the SFW and the old NF information, or the correspondence between the UE key and the old NF information is passed.

In case 1, step 812 may continue to be performed, step 812 being as follows.

In step 812, the sfw finds the information of old NF according to the UE identity or UE key, and sends a request message #5 to old NF.

Accordingly, old NF receives the request message #5 from SFW. Wherein the request message #5 includes the received NAS message. The request message #5 also includes a UE identity or UE key.

Upon receiving the request message #5 from the SMF, the old NF determines that the UE is not under the old NF based on the UE identity or UE key (i.e., is not served by oldNF or is not within the UE key range served by the old NF). Specifically, when the old NF obtains the UE identity in step 812, the old NF performs a function operation F on the UE identity to obtain a UE key, and further determines that the UE is not under the old NF according to the UE key. When the old NF obtains the UE key in step 812, the old NF determines that the UE is not under the old NF according to the UE key.

In this case, old NF looks up NF serving the UE based on the routing table, which may include mode 1 and mode 2, as follows.

Mode 1

In step 813, old NF forwards the request message #5 from SFW to next hop NF.

If the next hop NF of the old NF is still not the NF that provides the service for the UE, the next hop NF repeats the old NF operation, and continues to forward the request message #5 until the new NF that provides the service for the UE receives the request message #5.

Note that, the message forwarding process between old NF and new NF is not shown in fig. 8.

Mode 2

In step 814, old NF looks up the information of new NF serving the UE in the routing table based on the UE identity or UE key, and sends response message #5 of request message #5 to SFW.

Accordingly, the SMF receives a response message #5 from old NF. The response message #5 includes information of NF serving the UE, that is, new NF.

Wherein the information of new NF includes at least one of the following information: new NF identifies, new NF key, or a communication address of new NF.

It should be noted that, when the old NF does not find information of the NF serving the UE in the local routing table based on the UE identifier or the UE key, the old NF may send a request message to other NFs in the NF group for finding information of the NF serving the UE, and the other NFs may repeat the operation of the old NF until the information of the NF serving the UE is found.

Based on mode 2, step 815 may be performed subsequently, as follows.

In step 815, the sfw sends a request message #4 to the new NF according to the information of the new NF returned by the old NF.

Processing of the NAS message by new NF can be achieved by way 1 and 2 described above.

Case 2

The corresponding relation between the UE identification and the information of old NF and the corresponding relation between the UE key and the information of old NF are not stored in the SFW.

In case 2, step 816 may continue, as follows.

In step 816, the sfw arbitrarily selects NF send request message #6 in the NF group.

Accordingly, the NF receives the request message #6 from the SFW. Wherein the request message #6 includes a UE identity or UE key. Optionally, the request message #6 further includes a NAS message received by the SMF.

For convenience of description, NF arbitrarily selected by SFW is hereinafter described as an inlet NF.

Depending on whether the SFW sent request message #6 includes a NAS message, the subsequent operations may include mode 1 and mode 2, as follows.

Mode 1

In step 817, when the request message #6 sent by the SFW includes a NAS message, the ingress NF forwards the request message #6 from the SFW to the next hop NF.

If the next hop NF of the ingress NF is still not the NF that serves the UE, the next hop NF repeats the ingress NF operation and continues forwarding the request message #6 until the new NF that serves the UE receives the request message #6.

Note that, in fig. 8, a message forwarding process between the gateway NF and the new NF is not shown.

Mode 2

In step 818, when the request message #6 sent by the SFW does not include the NAS message, the ingress NF searches the routing table for information of new NF serving the UE based on the UE identity or the UE key, and sends a response message #6 of the request message #6 to the SFW.

Accordingly, the SMF receives a response message #6 from the ingress NF. The response message #6 includes information of NF serving the UE, that is, new NF.

It should be noted that, when the ingress NF does not find information of the NF serving the UE in the local routing table based on the UE identifier or the UE key, the ingress NF may send a request message to other NFs in the NF group for finding information of the NF serving the UE, and the other NFs may repeat the operation of the ingress NF until the information of the NF serving the UE is found.

Based on mode 2, step 819 may be performed subsequently.

In step 819, the sfw sends a request message #4 to the new NF according to the information of the new NF returned by the ingress NF.

In step 820, the ue completes various procedures, such as access registration, session management, etc., through SFW and new NF.

Specifically, similar to the NAS message in step 809, the other NAS messages of the UE are all forwarded to the new NF by the SFW, and the new NF processes the NAS messages, so as to complete the access registration, session management, and other processes of the UE.

Thus, in the method 800, NF groups may be formed based on DHT technology, where the NF groups are connected to the UE through SFW, and may complete route update of NF uplink and automatic migration of UE context based on an algorithm, which helps to avoid the influence of NF uplink on network elements outside the NF groups and helps to ensure service continuity.

The NF automatic offline scheme provided by the present application is described below with reference to fig. 9. The NF automatic offline scheme shown in fig. 9 is applicable to a scenario in which NF offline is planned. NF1 is NF that is scheduled to be taken offline in fig. 9, and NF2 is the successor node of NF 1. Based on the user context migration rule in the NF group, when NF1 goes offline, the UE responsible for NF1 will migrate to the successor node NF2 of NF1, i.e. the context of the UE responsible for NF1 will migrate to NF2.

In step 901, the ue establishes a connection with NF 1.

The detailed description of step 901 may refer to step 801, and will not be repeated here.

In step 902, before NF1 goes offline, NF1 sends the migrated UE context to NF 2.

This migrated UE context may be the context of the UE for which NF1 is responsible.

The UE context may include a UE identity or a UE key, among other things.

One possible implementation, NF1 sends the migrated UE context to NF2 via a context transfer message (context transfer).

At step 903, nf2 sends a notification message to the SFW.

Accordingly, the SFW receives the notification message from NF 2. The notification message includes UE identities or UE keys of UEs responsible for NF1 to notify SFW that the contexts of the UEs have migrated to NF2 and the NF2 serves the UEs.

The UE identity in the notification message may be a single UE identity or may be multiple UE identities, such as a list of UE identities. Similarly, the UE key in the notification message may be a single UE key or may be multiple UE keys, such as a UE key list. For example, when UE contexts of multiple UEs migrate to NF2 and the multiple UEs correspond to the same SFW, NF2 may send a notification message carrying multiple UE identities or multiple UE keys.

After receiving the NF2 notification message, the SFW may update the correspondence between the UE identifier and the NF2 information, or update the correspondence between the UE key and the NF2 information.

Step 903 is an optional step.

After NF1 is offline, the transmission manner of the message between the UE and NF is shown in steps 904 to 910.

In step 904, the ue sends a NAS message to the SWF.

After receiving the NAS message of the UE, the SFW may search NF2 corresponding to the UE based on the UE identity or UE key. Specifically, the operations performed by the SFW include case a and case B, as follows.

Case A

The SFW stores the corresponding relation between the UE identification and the NF2 information or stores the corresponding relation between the UE key and the NF2 information.

In case a, steps 904 and 906 may continue to be performed, with steps 905 and 906 being as follows.

In step 905, the sfw determines NF2 information according to the UE identity or UE key, and sends a request message #4 to NF2 according to the determined NF2 information.

Accordingly, NF2 receives request message #4. The request message #4 includes the received NAS message. The request message #4 may also include a UE identity or UE key.

This allows for processing of the NAS message by NF 2.

In step 906, the ue completes various procedures, such as access registration, session management, etc., through SFW and NF 2.

Specifically, similar to the NAS messages in step 905, the other NAS messages of the UE are forwarded to NF2 by the SFW, and the NF2 processes the NAS messages, so as to complete the procedures of access registration, session management, and the like of the UE.

Case B

The corresponding relation between the UE identification and the NF2 information and the corresponding relation between the UE key and the NF2 information are not stored in the SFW. In case B, steps 907-911 may be continued subsequently, as follows.

In step 907, the sfw arbitrarily selects NF as the ingress NF in the NF group, and sends a request message #6 to the ingress NF.

Accordingly, the ingress NF receives the request message #6 from the SFW. Wherein the request message #6 includes a UE identity or UE key. Optionally, the request message #6 further includes a NAS message received by the SMF.

Mode 1

In step 908, when the request message #6 sent by the SFW includes a NAS message, the ingress NF forwards the request message #6 from the SFW to the next hop NF.

If the next hop NF of the ingress NF is still not the NF that serves the UE, the next hop NF repeats the ingress NF operation and continues forwarding the request message #6 until the NF2 that serves the UE receives the request message #6.

Note that, in fig. 9, a message forwarding process between the ports NF and NF2 is not shown.

Mode 2

In step 909, when the request message #6 sent by the SFW does not include the NAS message, the ingress NF looks up the information of NF2 serving the UE in the routing table based on the UE identity or the UE key, and sends the response message #6 of the request message #6 to the SFW.

Accordingly, the SMF receives a response message #6 from the ingress NF. Wherein the response message #6 includes information of NF serving the UE, i.e., information of NF 2.

Wherein the NF2 information includes at least one of the following information: NF2 identification, NF2 key, or a communication address of NF 2.

Based on mode 2, step 910 may be performed subsequently.

In step 910, the sfw sends a request message #4 to NF2 according to the NF2 information returned by the ingress NF.

Processing of the NAS message by NF2 can be achieved by way 1 and 2 described above.

In step 911, the ue completes various procedures, such as access registration, session management, etc., through SFW and NF 2.

Specifically, similar to the NAS messages in step 904, the other NAS messages of the UE are all forwarded to NF2 by the SFW, and the NF2 processes the NAS messages, so as to complete the procedures of access registration, session management, and the like of the UE.

Thus, in the method 900, NF groups may be formed based on DHT technology, where the NF groups are connected to the UE through SFW, and may complete route update of NF offline and automatic migration of UE context based on an algorithm, which is helpful for avoiding the NF offline from affecting network elements outside the NF groups, and for ensuring service continuity.

Another NF automatic offline scheme provided by the present application is described below in conjunction with fig. 10. The NF automatic offline scheme shown in fig. 10 is applicable to the scenario in which NF is accidentally offline due to a fault. Assume in fig. 10 that NF1 is an NF that was down unexpectedly due to a fault, NF2 is a backup node for backing up the UE context of NF1, e.g., NF2 is a successor node of NF 1.

In step 1001, the ue establishes a connection with NF 1.

A detailed description of step 1001 may refer to step 801, which is not described herein.

In step 1002, NF1 determines a backup node when the UE context is stable.

The backup node may be a successor node of NF1, i.e., NF2.

For example, NF1 processes the NAS message from the UE, and when the flow process is finished, the UE context is considered to be stable, NF1 determines the backup node, and subsequently initiates the UE context backup request to the backup node NF.

Step 1003, nf1 backs up the UE context to NF2.

Specifically, NF1 sends a request message #7 (e.g., a backup request message) to NF2, and accordingly NF2 receives the request message #7 from NF1, wherein the request message #7 includes the UE identity and the UE context.

Wherein the UE context includes at least one of the following information: UE key, URI, SFW identification, communication address of SFW, UE location information, or UE access information (e.g., access technology employed, etc.).

In step 1004, when the UE context on NF1 is deleted, for example, due to UE movement, NF1 notifies NF2 to delete the relevant UE context when NF serving it changes.

One possible implementation manner, NF1 sends a request message #8 to NF2, and accordingly, NF2 receives a request message #8 from NF1, where the request message #8 includes a UE identity to indicate a backup UE context that needs to be deleted; NF2 deletes the UE context corresponding to the UE identifier according to the UE identifier in the request message # 8.

Optionally, the request message #8 further includes deletion indication information, where the deletion indication information is used to indicate deletion of the user context corresponding to the UE identity.

In another possible implementation, NF1 sends a request message #9 (e.g., a backup request message) to NF2, where the request message #9 includes the updated UE identity list; after receiving the updated request message #9, NF2 compares the updated UE identity list with the locally backed up UE identity list, and deletes the UE context corresponding to the UE identity that is not in the updated UE identity list.

In step 1005, the ue sends a NAS message to the SWF.

Assuming NF1 is accidentally taken off line due to a fault, the subsequent operations include case a and case B, as follows.

Case A

SFW has perceived NF1 to fail.

The application does not limit the scheme of SFW sensing NF1 failure. As one example, when the connection between the SFW and NF1 is broken, the SFW determines that NF1 is malfunctioning. As another example, when the SFW sends a message to NF1 but does not receive a reply from NF1, the SFW determines that the NF is malfunctioning.

One possible implementation manner, the SFW stores the received NAS message, searches the UE context based on the UE identifier or the UE key, and determines NF that provides service for the UE, i.e., NF1, based on NF information stored in the UE context; SWF determined NF1 failed.

In case a, step 1006 may continue, as follows.

In step 1006, the sfw selects any NF node except NF1 in the NF group as the ingress NF, and sends a request message #6 to the ingress NF.

Mode 1

In step 1007, when the request message #6 sent by the SFW includes a NAS message, the ingress NF forwards the request message #6 from the SFW to the next hop NF.

Note that, in fig. 10, a message forwarding process between the ports NF and NF2 is not shown.

Mode 2

In step 1008, when the request message #6 sent by the SFW does not include the NAS message, the ingress NF searches the routing table for information of NF2 serving the UE based on the UE identity or the UE key, and sends a response message #6 of the request message #6 to the SFW.

Based on mode 2, step 1009 may be performed subsequently.

In step 1009, the sfw sends a request message #4 to NF2 according to the NF2 information returned by the ingress NF.

In step 1010, the ue completes various procedures, such as access registration, session management, etc., through SFW and NF 2.

Specifically, similar to the NAS messages in step 1005, the other NAS messages of the UE are forwarded to NF2 by the SFW, and the NF2 processes the NAS messages, so as to complete the procedures of access registration, session management, and the like of the UE.

Case B

The SFW did not perceive NF1 failure.

In case B, steps 1011 to 1012 may be continued as follows.

In step 1011, the sfw searches the UE context based on the UE identity or UE key and determines NF, i.e., NF1, that serves the UE based on the NF location information stored in the UE context.

In step 1012, the sfw sends a request message #4 to NF1 and buffers the NAS message, starting a timer.

The request message #4 includes the received NAS message. The request message #4 may also include a UE identity or UE key.

If the SFW does not receive the response message of NF1 when the timer is overtime, the SFW determines that NF1 fails.

Subsequent steps 1013 to 1017 may refer to steps 1006 to 1010, which will not be described in detail.

In this way, in the method 1000, NF groups may be formed based on DHT technology, where the NF groups are connected to the UE through the SFW, and may support recovery of NF under the unexpected offline condition due to failure, which helps to avoid service damage and improve user experience.

The method provided by the present application is described in detail above with reference to fig. 5 to 10, and the device embodiment of the present application will be described in detail below with reference to fig. 11 to 12.

It will be appreciated that, in order to implement the functions of the above embodiments, the apparatus in fig. 11 or fig. 12 includes corresponding hardware structures and/or software modules for performing the respective functions. Those of skill in the art will readily appreciate that the various illustrative elements and method steps described in connection with the embodiments disclosed herein may be implemented as hardware or combinations of hardware and computer software.

Fig. 11 and 12 are schematic structural views of possible devices according to embodiments of the present application. These devices may be used to implement the functions of the transmitting end or the receiving end in the above method embodiments, so that the beneficial effects of the above method embodiments may also be implemented.

As shown in fig. 11, the apparatus 10 includes a transceiving unit 11 and a processing unit 12.

When the apparatus 10 is configured to implement the first core network function in the above-described method embodiment, the transceiver unit 11 is configured to: receiving a first message of a first terminal; the processing unit 12 is configured to: and determining whether the first message is processed by the first core network function according to a first index value range corresponding to the first core network function and the index value of the first terminal, wherein the first index value range is a set of index values of the terminal supporting service by the first core network function.

Optionally, the first core network function belongs to a core network function group, the core network function group includes a plurality of core network functions with the same service function, the first core network function is any one of the plurality of core network functions, and index value ranges corresponding to the plurality of core network functions have no intersection.

Optionally, the transceiver unit 11 is further configured to: and when the index value of the first terminal does not belong to the first index value range, sending the first message to a second core network function according to the index value of the first terminal, wherein the second core network function is a core network function in the core network function group for providing service for the first terminal.

Optionally, the transceiver unit 11 is further configured to: when the index value of the first terminal does not belong to the first index value range, acquiring information of a second core network function according to the index value of the first terminal, wherein the second core network function is a core network function in the core network function group for providing service for the first terminal; and sending the information of the second core network function to a service framework function.

Optionally, the processing unit 12 is further configured to: and when the first core network function joins the core network function group, determining a third core network function according to the index value of the first core network function. The transceiver unit 11 is further configured to: and acquiring a first context from the third core network function, wherein an index value of a terminal corresponding to the first context belongs to the first index value range. Wherein the index value of the third core network function is adjacent to the index value of the first core network function, and the index value of the third core network function is greater than the index value of the first core network function; or the index value of the third core network function is adjacent to the index value of the first core network function, the third core network function is the core network function with the minimum index value in the core network function group, and the first core network function is the core network function with the maximum index value in the core network function group.

Optionally, the transceiver unit 11 is further configured to: and sending a second message to a service framework function, wherein the second message is used for indicating the first context to migrate to the first core network function.

Optionally, the transceiver unit 11 is specifically configured to: sending a third message to the third core network function, wherein the third message is used for requesting a terminal context; a fourth message is received from a third core network function, the fourth message including the first context.

Optionally, the third message includes the first index value range.

Optionally, the first index value range is a range between an index value of the first core network function and an index value of a fourth core network function; wherein the index value of the fourth core network function is adjacent to the index value of the first core network function, and the index value of the fourth core network function is smaller than the index value of the first core network function; or the index value of the fourth core network function is adjacent to the index value of the first core network function, the fourth core network function is the core network function with the largest index value in the core network function group, and the first core network function is the core network function with the smallest index value in the core network function group.

Optionally, the transceiver unit 11 is further configured to: when the first core network function is offline, backing up a second context to a third core network function, wherein an index value of a terminal corresponding to the second context belongs to the first index value range; wherein the index value of the third core network function is adjacent to the index value of the first core network function, and the index value of the third core network function is greater than the index value of the first core network function; or the index value of the third core network function is adjacent to the index value of the first core network function, the third core network function is the core network function with the minimum index value in the core network function group, and the first core network function is the core network function with the maximum index value in the core network function group.

Optionally, the transceiver unit 11 is further configured to: and sending a fifth message to a service framework function, wherein the fifth message is used for indicating the second context to migrate to the third core network function.

Optionally, the transceiver unit 11 is further configured to: when the first core network function stores the context of the second terminal, the context of the second terminal is backed up to a third core network function; wherein the index value of the third core network function is adjacent to the index value of the first core network function, and the index value of the third core network function is greater than the index value of the first core network function; or the index value of the third core network function is adjacent to the index value of the first core network function, the third core network function is the core network function with the minimum index value in the core network function group, and the first core network function is the core network function with the maximum index value in the core network function group.

Optionally, the transceiver unit 11 is further configured to: and when the context of the second terminal is deleted from the first core network function, sending a sixth message to the third core network function, wherein the sixth message is used for indicating that the context of the second terminal is deleted.

When the apparatus 10 is used to implement the service framework functions in the above-described method embodiment, the transceiver unit 11 is configured to: receiving a first message from a first terminal; the processing unit 12 is configured to: searching a core network function corresponding to the first terminal; the transceiver unit 11 is further configured to: when a first core network function corresponding to the first terminal is found, sending the first message to the first core network function; and when the core network function corresponding to the first terminal is not found or the first core network function corresponding to the first terminal is found but the first core network function fails, sending the first message to an entry core network function, wherein the entry core network function is any core network function except for the first core network function in a core network function group, and the core network function group comprises a plurality of core network functions with the same service function.

Optionally, the transceiver unit 11 is further configured to: receiving information of a second core network function from the first core network function or the entry core network function, wherein the second core network function is a core network function in the core network function group for providing service for the first terminal; and sending the first message to the second core network function.

Optionally, the transceiver unit 11 is further configured to: when the first core network function joins the core network function group, receiving a second message from the first core network function, where the second message is used to instruct a first context to migrate to the first core network function, and an index value of a terminal corresponding to the first context belongs to a first index value range, where the first index value range is a set of index values of terminals that support services by the first core network function; the processing unit 12 is also configured to: and storing the corresponding relation between the terminal corresponding to the first context and the first core network function.

Optionally, the transceiver unit 11 is further configured to: when the first core network function is offline, receiving a fifth message sent by the first core network function, wherein the fifth message is used for indicating the migration of the second context to the third core network function; the processing unit 12 is also configured to: storing the corresponding relation between the terminal corresponding to the second context and the third core network function; the index value of the terminal corresponding to the second context belongs to a first index value range, and the first index value range is a set of index values of terminals of the first core network function support service; the index value of the third core network function is adjacent to the index value of the first core network function, and the index value of the third core network function is greater than the index value of the first core network function; or the index value of the third core network function is adjacent to the index value of the first core network function, the third core network function is the core network function with the minimum index value in the core network function group, and the first core network function is the core network function with the maximum index value in the core network function group.

Optionally, when the first core network function corresponding to the first terminal is found, the processing unit 12 is further configured to: when a response message for the first message from the first core network function is not received within a preset time after the first message is sent, determining that the first core network function fails; the transceiver unit 11 is further configured to: and sending the first message to the entrance core network function.

Optionally, for the case that the first core network function fails, the transceiver unit 11 is further configured to: sending a seventh message to the first core network function; the processing unit 12 is also configured to: and when the response message for the seventh message from the first core network function is not received within a preset time, determining that the first core network function fails. And/or the processing unit 12 is further configured to: and determining that the first core network function fails when the connection between the first core network function and the service framework function is in a disconnected state.

When the apparatus 10 is configured to implement the third core network function in the above-described method embodiment, the processing unit 12 is configured to: when a first core network function joins a core network function group, acquiring a first context, wherein an index value of a terminal corresponding to the first context belongs to a first index value range, and the first index value range is a set of index values of terminals of the first core network function support service; the transceiver unit 11 is configured to: transmitting the first context to the first core network function; wherein the index value of the third core network function is adjacent to the index value of the first core network function, and the index value of the third core network function is greater than the index value of the first core network function; or the index value of the third core network function is adjacent to the index value of the first core network function, the third core network function is the core network function with the minimum index value in the core network function group, and the first core network function is the core network function with the maximum index value in the core network function group.

Optionally, the transceiver unit 11 is further configured to: receiving a third message from the first core network function, wherein the third message is used for requesting a terminal context; the processing unit 12 is specifically configured to: and determining the first index value range according to the index value of the first core network function, and acquiring the first context according to the first index value range.

Optionally, the transceiver unit 11 is further configured to: receiving a third message from the first core network function, the third message being for requesting a terminal context, the third message comprising the first index value range; the processing unit 12 is specifically configured to: and acquiring the first context according to the first index value range.

Optionally, the transceiver unit 11 is further configured to: a context is received from a second terminal of the first core network function.

Optionally, when the context of the second terminal is deleted from the first core network function, the transceiver unit 11 is further configured to: receiving a sixth message sent by the first core network function, wherein the sixth message is used for indicating to delete the context of the second terminal; the processing unit 12 is also configured to: and deleting the context of the second terminal according to the sixth message.

For a more detailed description of the transceiver unit 11 and the processing unit 12, reference is made to the relevant description of the method embodiments described above, which is not explained here.

As shown in fig. 12, the apparatus 20 includes a processor 21. Processor 21 is coupled to memory 23, memory 23 for storing instructions. When the apparatus 20 is used to implement the method described above, the processor 21 is configured to execute instructions in the memory 23 to implement the functions of the processing unit 12 described above.

Optionally, the apparatus 20 further comprises a memory 23.

Optionally, the apparatus 20 further comprises an interface circuit 22. The processor 21 and the interface circuit 22 are coupled to each other. It is understood that the interface circuit 22 may be a transceiver or an input-output interface. When the apparatus 20 is used to implement the method described above, the processor 21 is configured to execute instructions to implement the functions of the processing unit 12, and the interface circuit 22 is configured to implement the functions of the transceiver unit 11.

Illustratively, when the apparatus 20 is a chip applied to the transmitting end or the receiving end, the chip implements the functions of the transmitting end or the receiving end in the above-described method embodiment. The chip receives information from other modules (such as a radio frequency module or an antenna) in the transmitting end or the receiving end, and the information is transmitted to the transmitting end or the receiving end by other devices; or the chip sends information to other modules (such as a radio frequency module or an antenna) in the transmitting end or the receiving end, and the information is sent to other devices by the transmitting end or the receiving end.

The present application also provides a communication device comprising a processor coupled to a memory for storing computer programs or instructions and/or data, the processor being for executing the computer programs or instructions stored in the memory or for reading the data stored in the memory for performing the methods of the above method embodiments. Optionally, the processor is one or more. Optionally, the communication device comprises a memory. Optionally, the memory is one or more. Alternatively, the memory may be integrated with the processor or provided separately.

The present application also provides a computer readable storage medium having stored thereon computer instructions for implementing the methods performed by the transmitting end or the receiving end in the above-described method embodiments.

The present application also provides a computer program product containing instructions that, when executed by a computer, implement the methods performed by the transmitting end or the receiving end in the above method embodiments.

The present application also provides a communication system including at least one of the transmitting end or the receiving end in the above embodiments.

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

It is to be appreciated that the processor in embodiments of the application may be a central processing unit (central processing unit, CPU), but may also be other general purpose processors, digital signal processors (DIGITAL SIGNAL processors, DSPs), application Specific Integrated Circuits (ASICs), field programmable gate arrays (field programmable GATE ARRAY, FPGAs), 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 method steps in the embodiments of the present application may be implemented by hardware, or may be implemented by executing software instructions by a processor. The software instructions may be comprised of corresponding software modules that may be stored in random access memory, flash memory, read-only memory, programmable read-only memory, erasable programmable read-only memory, electrically erasable programmable read-only memory, registers, hard disk, removable disk, compact disk-read-only memory (compact disc read-only memory), 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 be located in the transmitting end or the receiving end. It is also possible that the processor and the storage medium reside as discrete components in a transmitting or receiving end.

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

In various embodiments of the application, where no special description or logic conflict exists, 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 based on their inherent logic.

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.

Unless defined otherwise, all technical and scientific terms used in the embodiments of the application have the same meaning as commonly understood by one of ordinary skill in the art to which this application belongs. The terminology used in the present application is for the purpose of describing particular embodiments only and is not intended to limit the scope of the present application. It should be appreciated that the above examples are for illustrative purposes only to assist those skilled in the art in understanding the embodiments of the present application and are not intended to limit the application embodiments to the particular values or particular scenarios illustrated. Various equivalent modifications and changes will be apparent to those skilled in the art from the foregoing examples, and it is intended that such modifications and changes fall within the scope of the embodiments of the present application.

The foregoing is merely illustrative of the present application, and the present application is not limited thereto, and any person skilled in the art will readily recognize that variations or substitutions are within the scope of the present application. Therefore, the protection scope of the present application shall be subject to the protection scope of the claims.

Claims

1. A method of communication, the method comprising:

the first core network function receives a first message of a first terminal;

The first core network function determines whether the first message is processed by the first core network function according to a first index value range corresponding to the first core network function and an index value of the first terminal, wherein the first index value range is a set of index values of terminals of the first core network function supporting service.

2. The method of claim 1, wherein the step of determining the position of the substrate comprises,

The first core network function belongs to a core network function group, the core network function group comprises a plurality of core network functions with the same service function, the first core network function is any one of the plurality of core network functions, and index value ranges corresponding to the plurality of core network functions have no intersection.

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

and when the index value of the first terminal does not belong to the first index value range, the first core network device sends the first message to a second core network function according to the index value of the first terminal, wherein the second core network function is a core network function in the core network function group for providing service for the first terminal.

4. The method according to claim 2, wherein the method further comprises:

When the index value of the first terminal does not belong to the first index value range, the first core network device acquires information of a second core network function according to the index value of the first terminal, wherein the second core network function is a core network function in the core network function group for providing service for the first terminal;

the first core network function sends information of the second core network function to a service framework function.

5. The method according to any one of claims 2 to 4, further comprising:

when the first core network function joins the core network function group, the first core network function determines a third core network function according to the index value of the first core network function;

the first core network function acquires a first context from the third core network function, and an index value of a terminal corresponding to the first context belongs to the first index value range;

Wherein the index value of the third core network function is adjacent to the index value of the first core network function, and the index value of the third core network function is greater than the index value of the first core network function; or the index value of the third core network function is adjacent to the index value of the first core network function, the third core network function is the core network function with the minimum index value in the core network function group, and the first core network function is the core network function with the maximum index value in the core network function group.

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

the first core network function sends a second message to a service framework function, the second message being used to instruct the first context to migrate to the first core network function.

7. The method according to claim 5 or 6, wherein the first core network function obtains a first context from the third core network function, comprising:

the first core network function sends a third message to the third core network function, wherein the third message is used for requesting the context of the terminal;

The first core network function receives a fourth message from a third core network function, the fourth message including the first context.

8. The method of claim 7, wherein the step of determining the position of the probe is performed,

The third message includes the first index value range.

9. The method according to any one of claims 1 to 8, wherein,

The first index value range is a range between the index value of the first core network function and the index value of the fourth core network function;

Wherein the index value of the fourth core network function is adjacent to the index value of the first core network function, and the index value of the fourth core network function is smaller than the index value of the first core network function; or the index value of the fourth core network function is adjacent to the index value of the first core network function, the fourth core network function is the core network function with the largest index value in the core network function group, and the first core network function is the core network function with the smallest index value in the core network function group.

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

When the first core network function is offline, the first core network function backs up a second context to a third core network function, and an index value of a terminal corresponding to the second context belongs to the first index value range;

11. The method according to claim 10, wherein the method further comprises:

The first core network function sends a fifth message to a service framework function, the fifth message being used to instruct the second context to migrate to the third core network function.

12. The method according to any one of claims 1 to 9, further comprising:

When the first core network function stores the context of the second terminal, the first core network function backs up the context of the second terminal to a third core network function;

13. The method according to claim 12, wherein the method further comprises:

When the context of the second terminal is deleted from the first core network function, the first core network function sends a sixth message to the third core network function, where the sixth message is used to indicate that the context of the second terminal is deleted.

14. The method according to any one of claims 1 to 13, further comprising:

The service framework function receives a first message from the first terminal;

The service framework function searches a core network function corresponding to the first terminal;

When the first core network function corresponding to the first terminal is found, the service framework function sends the first message to the first core network function;

When the core network function corresponding to the first terminal is not found or the first core network function corresponding to the first terminal is found but the first core network function fails, the service framework function sends the first message to an entry core network function, where the entry core network function is any core network function except for the first core network function in a core network function group, and the core network function group includes a plurality of core network functions with the same service function.

15. The method according to any one of claims 1 to 14, further comprising:

When the first core network function joins a core network function group, a third core network function obtains a first context, and an index value of a terminal corresponding to the first context belongs to the first index value range;

the third core network function sends the first context to the first core network function;

16. A method of communication, the method comprising:

The service framework function receives a first message from a first terminal;

When a first core network function corresponding to the first terminal is found, the service framework function sends the first message to the first core network function;

When the core network function corresponding to the first terminal is not found or the first core network function corresponding to the first terminal is found but the first core network function fails, the service framework function sends the first message to an entry core network function, wherein the entry core network function is any core network function except for the first core network function in a core network function group, and the core network function group comprises a plurality of core network functions with the same service function.

17. The method of claim 16, wherein the method further comprises:

The service framework function receives information of a second core network function from the first core network function or the entry core network function, and the second core network function is a core network function in the core network function group for providing service for the first terminal;

The service framework function sends the first message to the second core network function.

18. The method according to claim 16 or 17, characterized in that the method further comprises:

When the first core network function joins the core network function group, the service framework function receives a second message from the first core network function, where the second message is used to instruct a first context to migrate to the first core network function, and an index value of a terminal corresponding to the first context belongs to a first index value range, where the first index value range is a set of index values of terminals supporting services by the first core network function;

And the service framework function stores the corresponding relation between the terminal corresponding to the first context and the first core network function.

19. The method of claim 18, wherein the method further comprises:

When the first core network function is offline, the service framework function receives a fifth message from the first core network function and sends the fifth message, wherein the fifth message is used for indicating the migration of the second context to the third core network function;

The service framework function stores the corresponding relation between the terminal corresponding to the second context and the third core network function;

The index value of the terminal corresponding to the second context belongs to a first index value range, and the first index value range is a set of index values of terminals of the first core network function support service; the index value of the third core network function is adjacent to the index value of the first core network function, and the index value of the third core network function is greater than the index value of the first core network function; or the index value of the third core network function is adjacent to the index value of the first core network function, the third core network function is the core network function with the minimum index value in the core network function group, and the first core network function is the core network function with the maximum index value in the core network function group.

20. The method according to any one of claims 16 to 19, wherein when a first core network function corresponding to the first terminal is found, the method further comprises:

When a response message for the first message from the first core network function is not received within a preset time after the first message is sent, the service framework function determines that the first core network function fails;

the service framework function sends the first message to the ingress core network function.

21. The method according to any of claims 16 to 19, wherein for the case of a failure of the first core network function, the method further comprises:

The service framework function sends a seventh message to the first core network function; when a response message for the seventh message from the first core network function is not received within a preset time, the service framework function determines that the first core network function fails; and/or the number of the groups of groups,

When the connection between the first core network function and the service framework function is in a disconnected state, the service framework function determines that the first core network function fails.

22. A communication device, comprising

The receiving and transmitting unit is used for receiving a first message of the first terminal;

And the processing unit is used for determining whether the first message is processed by the first core network function according to a first index value range corresponding to the first core network function and the index value of the first terminal, wherein the first index value range is a set of index values of the terminal of the first core network function supporting service.

23. A communication device, comprising

A transceiver unit for receiving a first message from a first terminal;

The processing unit is used for searching the core network function corresponding to the first terminal;

The sending unit is further configured to send the first message to a first core network function corresponding to the first terminal when the first core network function is found; and when the core network function corresponding to the first terminal is not found or the first core network function corresponding to the first terminal is found but the first core network function fails, sending the first message to an entry core network function, wherein the entry core network function is any core network function except for the first core network function in a core network function group, and the core network function group comprises a plurality of core network functions with the same service function.

24. 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 15 or to perform the method of any one of claims 16 to 21.

25. The apparatus of claim 24, further comprising the memory.

26. The device of claim 24 or 25, wherein the device is a chip.

27. 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 according to any of claims 1 to 15 or to perform the method according to any of claims 16 to 21.

28. A computer program product, characterized in that it comprises instructions for performing the method of any one of claims 1 to 15 or instructions for performing the method of any one of claims 16 to 21.

29. A communication system, comprising: a first core network function for performing the method of any of claims 1 to 15 and/or a service framework function for performing the method of any of claims 16 to 21.