CN110708727B

CN110708727B - Relocation management method and device

Info

Publication number: CN110708727B
Application number: CN201810752205.3A
Authority: CN
Inventors: 陆伟; 周铮; 刘睿智
Original assignee: Huawei Technologies Co Ltd
Current assignee: Huawei Technologies Co Ltd
Priority date: 2018-07-10
Filing date: 2018-07-10
Publication date: 2021-05-11
Anticipated expiration: 2038-07-10
Also published as: WO2020011173A1; CN110708727A

Abstract

The application provides a relocation management method and a relocation management device, relates to the technical field of communication, and particularly provides a scheme that a terminal processes application support/does not support application relocation. The method comprises the following steps: the method comprises the steps that a terminal receives relocation attribute information sent by network equipment, wherein the relocation attribute information is used for indicating relocation attributes of one or more applications, the relocation attributes comprise application relocation support or application relocation unsupported, and the one or more applications comprise first applications; if the relocation attribute of the first application is that the application relocation is not supported, the terminal transmits the data stream of the first application through a first route; and if the relocation attribute of the first application is application relocation support, the terminal transmits the data stream of the first application through the second route. The method and the device are suitable for the transmission process of the data stream of the application.

Description

Relocation management method and device

Technical Field

The present application relates to the field of communications technologies, and in particular, to a relocation management method and device.

Background

Currently, in the process of terminal movement, a network device reselects a User Plane Function (UPF) network element for a terminal according to information such as the position of the terminal, and triggers the terminal to establish a route with the reselected UPF network element. And finally, the terminal migrates the applied data stream from the route between the terminal and the UPF network element before reselection to the route between the terminal and the UPF network element after reselection so as to acquire better data transmission service.

However, in some cases, for example, due to the deployment of the third-party application server, or the reason that the third-party application server does Not support context transfer, and the like, during the movement of the terminal, the position of the connected third-party application server remains unchanged when the third-party application server requests the terminal to perform the service of the third-party application, and the third-party application having such a feature may be considered as Not supporting application relocation (Not). In a scenario that the application relocation is not supported by the third-party application, compared with the UPF network element before reselection, the UPF network element after reselection may be far away from the third-party application server, so that, in order to improve user experience, the terminal should transmit an application data packet to the third-party application server by using the UPF network element before reselection, instead of transmitting an application data stream by using the UPF network element after reselection. However, this is contradictory to the current routing after terminal reselection. At present, for the problem caused by that the third party application does not support application relocation, the prior art does not provide a corresponding solution.

Disclosure of Invention

The application provides a relocation management method and a relocation management device, and particularly provides a scheme that a terminal processes application support/does not support application relocation.

In order to achieve the purpose, the technical scheme is as follows:

in a first aspect, a relocation management method is provided, including: the method comprises the steps that a terminal receives relocation attribute information, wherein the relocation attribute information is used for indicating relocation attributes of one or more applications, the relocation attributes comprise Application relocation supporting (Application relocation capable) or Application relocation not supporting, and the one or more applications comprise first applications; if the relocation attribute of the first application is that the application relocation is not supported, the terminal transmits the data stream of the first application through a first route; and if the relocation attribute of the first application is application relocation support, the terminal transmits the data stream of the first application through a second route. In this way, a scheme that the terminal processes application migration support/non-support is provided, so that the problem that the route (namely, the second route) of the data stream actually used for transmitting the application by the terminal is inconsistent with the route (namely, the first route) of the data stream expected to be used for transmitting the application by the third-party application server in the scenario that the application migration is not supported by the terminal is solved.

In one possible design, the method includes: and before the terminal receives the relocation attribute information, the terminal transmits the data stream of the first application through the first route. That is, for the first application, the first route is a route used by the terminal to transmit a data stream of the first application before receiving the relocation attribute information.

Optionally, the relocation attribute information is used to indicate relocation attributes of one or more applications, and at least includes one of the following situations: (1) the relocation attribute information includes information of an application that does not support application relocation; (2) the relocation attribute information includes information of an application supporting the relocation of the application; (3) the relocation attribute information includes first indication information and application information, where the first indication information is used to indicate that the application information included in the relocation attribute information is information of an application supporting relocation of the application, or the first indication information is used to indicate that the application supports relocation of the application; (4) the relocation attribute information includes second indication information and application information, where the second indication information is used to indicate that the application information included in the relocation attribute information is information of an application that does not support application relocation, or the second indication information is used to indicate that the application does not support application relocation; (5) the relocation attribute information comprises one or more application timer configuration information, and the application timer configuration information is used for indicating the configuration of an application timer; before the application timer is overtime, the application moving attribute corresponding to the application timer is application moving support; or before the application timer is overtime, the application moving attribute corresponding to the application timer is that the application moving is not supported.

Optionally, the information of the application includes at least one of the following situations: an identification of the application; a data flow identification of the application; triplet information, the triplet information comprising: address, port and transport layer protocols; quintuple information, which includes a destination address, a source address, a destination port, a source port, and a transport layer protocol.

In one possible design, the method further includes: the terminal receives the route timer information and configures the route timer according to the reason timer information. Further, the terminal releases the route corresponding to the route timer according to the route timer information. Optionally, the route timer information is used to instruct the terminal to configure a route timer for the corresponding route, and/or the route timer is used to instruct a time when the route corresponding to the route timer is released. Therefore, the terminal can configure the routing timer according to the routing timer information, so that the corresponding route is released after the routing timer is overtime, and network resources are saved.

In a second aspect, a relocation management method is provided, including: the network equipment determines relocation attribute information, wherein the relocation attribute information is used for indicating relocation attributes of one or more applications, and the relocation attributes comprise application relocation support or application relocation unsupported; and the network equipment sends the relocation attribute information to the terminal. According to the relocation management method, the network equipment sends the relocation attribute information to the terminal, so that the terminal can acquire the relocation attribute of one or more applications. Therefore, the terminal can select a proper route to transmit the data stream of the application according to the application migration attribute, so that the problem that the route (namely, the second route) of the data stream actually used for transmitting the application by the terminal is contradictory to the route (namely, the first route) of the data stream expected to be used for transmitting the application by the third-party application server under the situation that the application does not support the application migration is solved.

Optionally, the relocation attribute information is used to indicate relocation attributes of one or more applications, and at least includes one of the following situations: (1) the relocation attribute information includes information of an application that does not support application relocation; (2) the relocation attribute information includes information of an application supporting the relocation of the application; (3) the relocation attribute information includes first indication information and application information, the first indication information is used for indicating that the application information included in the relocation attribute information is information of an application supporting relocation of the application, or the first indication information is used for indicating that the application supports relocation of the application; (4) the relocation attribute information includes second indication information and application information, the second indication information is used for indicating that the application information included in the relocation attribute information is information of an application which does not support application relocation, or the second indication information is used for indicating that the application does not support application relocation; (5) the relocation attribute information comprises one or more application timer configuration information, and the application timer configuration information is used for indicating the configuration of an application timer; before the application timer is overtime, the application moving attribute corresponding to the application timer is application moving support; or before the application timer is overtime, the application moving attribute corresponding to the application timer is that the application moving is not supported.

In one possible design, the method further includes: the network device sends routing timer information to the terminal device, wherein the routing timer information is used for indicating the configuration information of the route corresponding to the routing timer, and/or the routing timer is used for indicating the time for releasing the route corresponding to the routing timer. Therefore, the network equipment indicates the terminal to configure the route timer through the route timer information, so that the terminal releases the specified route at the specified time, and the network resource is saved.

In one possible design, the method further includes: and the network equipment determines the routing timer information according to the application timer configuration information. For example, the application timer configuration information includes an application timer timing length, the routing timer information includes a routing timer timing length, and the network device may determine a maximum value of the timing length of the application timer from the plurality of application timer configuration information and set the maximum value of the timing length of the application timer as the timing length of the routing timer.

In one possible design, a network device is a policy function control network element, and the network device sends relocation attribute information to a terminal, including: the policy function control network element sends user equipment routing policy (URSP) information to the terminal, wherein the URSP information comprises relocation attribute information. The design provides a specific implementation mode for the network equipment to send the relocation attribute information to the terminal.

In a third aspect, a terminal is provided, where the terminal has a function of implementing the method of any one of the first aspect. The function can be realized by hardware, and can also be realized by executing corresponding software by hardware. The hardware or software includes one or more modules corresponding to the functions described above.

In a fourth aspect, a terminal is provided, including: a processor, a memory, a bus, and a communication interface; the memory is configured to store a computer execution instruction, the processor is connected to the memory through the bus, and when the terminal runs, the processor executes the computer execution instruction stored in the memory, so that the terminal executes the relocation management method according to any one of the first aspect.

In a fifth aspect, a terminal is provided, including: a processor; the processor is configured to be coupled to the memory, and after reading an instruction in the memory, execute the relocation management method according to any one of the first aspect.

A sixth aspect provides a computer-readable storage medium having stored therein instructions, which, when run on a computer, enable the computer to execute the relocation management method according to any one of the first aspects.

In a seventh aspect, a computer program product containing instructions is provided, which when run on a computer, enables the computer to perform the relocation management method according to any one of the first aspect.

In an eighth aspect, a chip system is provided, which includes a processor for enabling a terminal to implement the functions recited in the first aspect. In one possible design, the system-on-chip further includes a memory for storing program instructions and data necessary for the terminal. The chip system may be constituted by a chip, or may include a chip and other discrete devices.

For technical effects brought by any one of the design manners in the third aspect to the eighth aspect, reference may be made to technical effects brought by different design manners in the first aspect, and details are not described here.

A ninth aspect provides a network device having a function of implementing the relocation management method according to any one of the second aspects. The function can be realized by hardware, and can also be realized by executing corresponding software by hardware. The hardware or software includes one or more modules corresponding to the functions described above.

In a tenth aspect, there is provided a network device comprising: a processor, a memory, a bus, and a communication interface; the memory is configured to store a computer execution instruction, the processor is connected to the memory through the bus, and when the network device runs, the processor executes the computer execution instruction stored in the memory, so that the network device executes the relocation management method according to any one of the second aspects.

In an eleventh aspect, a network device is provided, which includes: a processor; the processor is configured to be coupled to the memory, and after reading the instruction in the memory, execute the relocation management method according to any one of the second aspects.

In a twelfth aspect, a computer-readable storage medium is provided, in which instructions are stored, and when the computer-readable storage medium runs on a computer, the computer can execute the relocation management method according to any one of the second aspects.

In a thirteenth aspect, there is provided a computer program product containing instructions which, when run on a computer, enable the computer to perform the relocation management method of any one of the second aspects.

In a fourteenth aspect, a chip system is provided, which includes a processor for supporting a network device to implement the functions recited in the second aspect. In one possible design, the system-on-chip further includes a memory for storing program instructions and data necessary for the network device. The chip system may be constituted by a chip, or may include a chip and other discrete devices.

The technical effects brought by any one of the design manners in the ninth aspect to the fourteenth aspect can be referred to the technical effects brought by different design manners in the second aspect, and are not described herein again.

Drawings

Fig. 1 is a schematic architecture diagram of a communication system according to an embodiment of the present application;

fig. 2 is a schematic view of a scenario in which a terminal establishes a route according to an embodiment of the present application;

fig. 3 is a schematic view of another scenario in which a terminal establishes a route according to an embodiment of the present application;

fig. 4 is a schematic diagram of a communication system according to an embodiment of the present application;

fig. 5 is a schematic hardware structure diagram of a communication device according to an embodiment of the present application;

fig. 6 is a flowchart of a relocation management method according to an embodiment of the present application;

fig. 7 is a flowchart of another relocation management method according to an embodiment of the present application;

fig. 8 is a flowchart of another relocation management method according to an embodiment of the present application;

fig. 9 is a schematic structural diagram of a terminal according to an embodiment of the present application;

fig. 10 is a schematic structural diagram of a network device according to an embodiment of the present application.

Detailed Description

The terms "first", "second", and the like in the present application are only for distinguishing different objects, and do not limit the order thereof. For example, the first route and the second route are only for distinguishing different routes, and the precedence order thereof is not limited.

The term "and/or" in this application is only one kind of association relationship describing the associated object, and means that there may be three kinds of relationships, for example, a and/or B, which may mean: a exists alone, A and B exist simultaneously, and B exists alone. In addition, the character "/" in this application generally indicates that the former and latter related objects are in an "or" relationship.

It is noted that, in the present application, words such as "exemplary" or "for example" are used to mean exemplary, illustrative, or descriptive. Any embodiment or design described herein as "exemplary" or "e.g.," is not necessarily to be construed as preferred or advantageous over other embodiments or designs. Rather, use of the word "exemplary" or "such as" is intended to present concepts related in a concrete fashion.

In addition, the network architecture and the service scenario described in the embodiment of the present application are for more clearly illustrating the technical solution of the embodiment of the present application, and do not constitute a limitation to the technical solution provided in the embodiment of the present application, and it can be known by a person skilled in the art that the technical solution provided in the embodiment of the present application is also applicable to similar technical problems along with the evolution of the network architecture and the appearance of a new service scenario.

The technical solution provided in the embodiment of the present application may be applied to a wireless communication system, which may be a 5G system, or other future communication systems, and certainly may also be a Long Term Evolution (LTE) system, an LTE-Advanced (LTE-a) system, and the like.

Taking the wireless communication system as a 5G system as an example, as shown in fig. 1, it is a schematic structural diagram of a communication system to which the technical solution provided by the embodiment of the present application is applied. In fig. 1, a communication system may include: a terminal 10, a Radio Access Network (RAN) or AN Access Network (AN) 20 (hereinafter referred to as (R) AN20), a core network 30, and a Data Network (DN) 40. The core network element (or referred to as a network function network element) in the core network 30 may include: an access and mobility management function (AMF) network element, a Session Management Function (SMF) network element, a Policy Control Function (PCF) network element, a UPF network element, and the like.

The AMF network element communicates with the SMF network element through a Next generation network (N) 11 interface, the AMF network element communicates with the PCF network element through an N15 interface, the SMF network element communicates with the PCT network element through an N7 interface, the SMF network element communicates with the UPF network element through an N4 interface, and the UPF network element communicates with the DN through an N6 interface. It should be noted that the interface name between each network element in fig. 1 is only an example, and the interface name may be other names in specific implementation, which is not limited in this embodiment of the present application.

The terminal 10 may comprise various handheld devices having wireless communication capabilities, in-vehicle devices, wearable devices, computing devices, or other processing devices connected to a wireless modem; a subscriber unit (subscriber unit), a cellular phone (cellular phone), a smart phone (smart phone), a wireless data card, a Personal Digital Assistant (PDA) computer, a tablet computer, a wireless modem (modem), a handheld device (dhhand), a laptop computer (laptop computer), a cordless phone (cordless phone) or a Wireless Local Loop (WLL) station, a Machine Type Communication (MTC) terminal, a User Equipment (UE), a Mobile Station (MS), a terminal equipment (terminal device) or a relay user equipment, etc. may also be included. The relay user equipment may be, for example, a 5G home gateway (RG). For convenience of description, these devices are collectively referred to as a terminal (terminal) in this application.

The (R) AN20 may be used to provide a wireless connection between the terminal 10 and the core network 30. The network elements in the (R) AN20 may include, for example and without limitation, a base station, AN evolved node base (eNB), a next generation base station (gNB), a new radio base station (new radio eNB), a macro base station, a micro base station, a high frequency base station or a Transmission and Reception Point (TRP), a non-3GPP access network (e.g., Wi-Fi), and/or a non-3GPP interworking function (N3 IWF), and other devices. It should be noted that, hereinafter, the (R) AN20 may be understood as a network element in the (R) AN, and is described herein in a unified manner, and will not be described in detail below.

The AMF network element may be used for connection management, mobility management, registration management, access authentication and authorization, reachability management, security context management, selection of SMF network elements, and the like. The SMF network element may be used for session management such as establishment, modification, and release of a session, selection and control of a UPF network element, selection of a service and session continuity (service and session continuity) mode, and roaming service, etc. The PCF network element may be configured to provide a policy control service and obtain subscription information related to policy decision. The UPF network element may be configured to process events related to a user plane, such as transmitting or routing a data packet, detecting a data packet, reporting a traffic volume, processing quality of service (QoS), lawful interception, storing a downlink data packet, and the like.

DN40 may be, for example, an operator service, internet access or third party service, etc.

It is understood that, although not shown, the 5G network may further include other network elements, such as an authentication service function (AUSF) network element, an Application Function (AF) network element, and a network open function (NEF) network element, and the present application is not limited in this respect.

It should be noted that, in fig. 1, each network element, such as the terminal 10, (R) AN20, AMF network element, SMF network element, PCF network element, and UPF network element, etc., is only a name, and the name does not limit the device itself. In the 5G network and other networks in the future, these network elements may also be given other names, which is not specifically limited in this embodiment of the present application. For example, the AMF network element may also be replaced by an AMF or an AMF entity, etc., which are described herein in a unified manner and will not be described in detail below.

At present, in the process of terminal movement, in order to reduce data transmission delay, a network device reselects a UPF network element for a terminal according to information such as the position of the terminal, and triggers the terminal to establish a route with the reselected UPF network element. In connection with the architecture of the communication system shown in fig. 1, there are specifically the following situations:

(1) the terminal can establish connection with different UPF network elements through different PDU sessions, that is, only one route is included in one PDU session. As shown in fig. 2, the terminal first establishes a first PDU session with the UPF network element 1, and the terminal transmits the data stream of the application through the route (i.e. the first route) of the first PDU session. During the movement of the terminal, or due to other factors, such as the rerouting of requests for certain application data flows, the terminal chooses to establish a second PDU session with the UPF network element 2 (i.e. the reselected UPF network element). In this way, the terminal may migrate the data flow of the application, which is originally transmitted on the first route, to a route (i.e., a second route) of the second PDU session, and transmit the data flow of the application by the second route.

(2) The terminal can establish connection with different UPF network elements through the same PDU session, namely one PDU session comprises a plurality of routes. As shown in fig. 3, the terminal first establishes a first route with a PDU session anchor point (UPF network element 4 in fig. 3), and the terminal transmits the data stream of the application through the first route. During the movement of the terminal or due to other factors, such as the request of rerouting of some application data streams, the mobile communication network selects to establish a second route with another PDU session anchor point (UPF network element 5 in fig. 3) through the shunting point (UPF network element 3 in fig. 3). In this way, the terminal may migrate the data stream of the application originally transmitted on the first route to the second route, and transmit the data stream of the application by the second route.

Under the condition that the application does not support application relocation, currently, the route (i.e. the second route) of the data stream actually used for transmitting the application by the terminal is contradictory to the route (i.e. the first route) of the data stream which the third-party application server wishes to transmit the application. The prior art does not provide a corresponding solution to this problem.

In order to solve the above problem, as shown in fig. 4, a schematic diagram of a communication system according to an embodiment of the present application is provided. As shown in fig. 4, the communication system includes: a terminal 10 and a network device 50. The network device 50 may be a third-party application server, a PCF network element, an SMF network element, and the like, which is not limited in this embodiment of the present application.

The network device 50 is configured to send relocation attribute information to a terminal, where the relocation attribute information includes relocation attributes of one or more applications, where the one or more applications include a first application, and the relocation attributes include that application relocation is supported or application relocation is not supported.

The terminal 10 is configured to receive the relocation attribute information; and selecting a proper route to transmit the data stream of the application according to the transfer attribute of the application.

For example, before the terminal 10 receives the relocation attribute information, the terminal transmits the data stream of the first application through the first route. If the migration attribute of the first application is that the application migration is not supported, continuing to transmit the data stream of the first application through the first route, and if the migration attribute of the first application is that the application migration is supported, switching the first route to a second route, and transmitting the data stream of the first application through the second route.

In this way, for an application that does not support application relocation, the terminal can ensure that the data stream of the application continues to be transmitted on the original route (i.e., the first route).

Alternatively, the terminal 10 or the network device 50 in fig. 4 may be implemented by one device, or may be implemented by multiple devices together, or may be a functional module in one device, which is not specifically limited in this embodiment of the present application. It is understood that the above functions may be either network elements in a hardware device, software functions running on dedicated hardware, or virtualized functions instantiated on a platform (e.g., a cloud platform).

For example, the terminal 10 or the network device 50 in fig. 4 can be implemented by the communication device in fig. 5. Fig. 5 is a schematic diagram illustrating a hardware structure of a communication device according to an embodiment of the present application. The communication device 500 includes at least one processor 501, communication lines 502, memory 503, and at least one communication interface 504.

The processor 501 may be a general-purpose Central Processing Unit (CPU), a microprocessor, an application-specific integrated circuit (ASIC), or one or more ics for controlling the execution of programs in accordance with the present disclosure.

The communication link 502 may include a path for transmitting information between the aforementioned components.

Communication interface 504, using any transceiver or the like, is used for communicating with other devices or communication networks, such as ethernet, RAN, Wireless Local Area Networks (WLAN), etc.

The memory 503 may be, but is not limited to, a read-only memory (ROM) or other type of static storage device that may store static information and instructions, a Random Access Memory (RAM) or other type of dynamic storage device that may store information and instructions, an electrically erasable programmable read-only memory (EEPROM), a compact disc read-only memory (CD-ROM) or other optical disk storage, optical disk storage (including compact disc, laser disc, optical disc, digital versatile disc, blu-ray disc, etc.), magnetic disk storage media or other magnetic storage devices, or any other medium that can be used to carry or store desired program code in the form of instructions or data structures and that can be accessed by a computer. The memory may be separate and coupled to the processor via a communication line 502. The memory may also be integral to the processor.

The memory 503 is used for storing computer-executable instructions for executing the present application, and is controlled by the processor 501 to execute. The processor 501 is configured to execute computer-executable instructions stored in the memory 503 to implement the methods provided by the embodiments of the present application described below.

Optionally, the computer-executable instructions in the embodiments of the present application may also be referred to as application program codes, which are not specifically limited in the embodiments of the present application.

In particular implementations, processor 501 may include one or more CPUs such as CPU0 and CPU1 in fig. 5 as an example.

In particular implementations, communication device 500 may include multiple processors, such as processor 501 and processor 507 in fig. 5, for example, as an embodiment. Each of these processors may be a single-core (single-CPU) processor or a multi-core (multi-CPU) processor. A processor herein may refer to one or more devices, circuits, and/or processing cores for processing data (e.g., computer program instructions).

In particular implementations, communication device 500 may also include an output device 505 and an input device 506, as one embodiment. An output device 505, which is in communication with the processor 501, may display information in a variety of ways. For example, the output device 505 may be a Liquid Crystal Display (LCD), a Light Emitting Diode (LED) display device, a Cathode Ray Tube (CRT) display device, a projector (projector), or the like. The input device 506 is in communication with the processor 501 and may receive user input in a variety of ways. For example, the input device 506 may be a mouse, a keyboard, a touch screen device, or a sensing device, among others.

The communication device 500 may be a general purpose device or a special purpose device. In a specific implementation, the communication device 500 may be a desktop, a laptop, a web server, a Personal Digital Assistant (PDA), a mobile phone, a tablet, a wireless terminal device, an embedded device, or a device with a similar structure as in fig. 5. The embodiment of the present application does not limit the type of the communication device 500.

As shown in fig. 6, a flowchart of a relocation management method provided in an embodiment of the present application is shown, where the method includes the following steps:

s101, the network equipment determines the relocation attribute information.

Wherein the relocation attribute information is used to indicate relocation attributes of one or more applications. Optionally, the relocation attribute information is used to indicate that multiple applications have the same relocation attribute; or, for a plurality of applications, the migration attribute information indicates the migration attribute of the application for each application.

In the embodiment of the present application, the migration attribute includes that application migration is supported or application migration is not supported. Supporting application relocation refers to allowing the application's data flow to migrate from the original route (i.e., the first route) to another route (e.g., the second route). The fact that application relocation is not supported means that migration of data streams of an application from an original route to another route is not allowed.

Optionally, the network device may determine the migration attribute of the one or more applications according to the following manner:

in a first mode, the network device stores relocation attributes of one or more applications in advance.

Illustratively, the network device may store the migration attribute of the application in the form of table one.

Watch 1

Information of applications	Relocation Attribute
		Information of application A	Supporting application relocation
Information of application B	Supporting application relocation
		Information of application C	Not supporting application relocation
Information of application D	Supporting application relocation

It is worth mentioning that the information of the above applications includes but is not limited to: an identification of an application, an identification of a data stream of an application, triplet information, or quintet information.

It should be noted that the triplet information includes a transport layer protocol, an address, and a port. Wherein the address is a source address or a destination address. The port is a destination port or a source port. For example, the triplet information may be a transport layer protocol, a source address, and a source port; alternatively, the triplet information may be a transport layer protocol, a destination address, and a destination port.

Wherein the source address is an address of a device that sends the data stream of the application. The destination address is the address of the device receiving the data stream of the application. The source port is the port of the device that sends the data stream of the application. The destination port is a port of a device that receives a data stream of an application. In the embodiment of the application, the device for receiving/sending the data stream of the application is a terminal or a third-party application server. In particular, the method comprises the following steps of,

illustratively, the transport layer Protocol is Internet Protocol (IP).

It should be noted that the quintuple information includes: destination address, source address, destination port, source port, and transport layer protocol. The explanation of the content contained in the above five-tuple information is described above with reference to the triplet information.

Optionally, in addition to the text description manner shown in table one, the migration attribute of the application may also be described in other manners. For example, a binary number "1" may be used to indicate that the migration attribute of the application is application migration support, and a binary number "0" may be used to indicate that the migration attribute of the application is application migration support. Based on the example shown in table one, in the case of describing the migration attribute of the application by using binary number, the network device may store the migration attribute of the application in the form of table two.

Watch two

Information of applications	Relocation Attribute
		Information of application A	1
Information of application B	1
		Information of application C	0
Information of application D	1

Optionally, the relocation attributes of the application may be valid based on time and/or location. That is, if the terminal runs an application at a specific time and/or at a specific location, the relocation attribute of the application stored in the network device is valid. Thus, for the terminal, the migration attribute of the application is the migration attribute stored in the network device.

For example, for an application, the network device stores a migration attribute that does not support application migration. And if the terminal runs the application at a specific time and/or at a specific position, the moving attribute of the application is that the application moving is not supported for the terminal. On the contrary, if the terminal does not run the application at a specific time and/or the terminal is not at a specific location, the application is supported to be migrated according to the migration attribute of the application for the terminal.

For another example, for an application, the network device stores a migration attribute to support application migration. And if the terminal runs the application at a specific time and/or at a specific position, the moving attribute of the application is the application moving support for the terminal. On the contrary, if the terminal does not run the application at the specific time and/or the terminal is not at the specific position, the application is not supported to be moved by the moving attribute of the application for the terminal.

Therefore, when storing the migration attribute of the application, the network device also stores the valid location and/or the valid time period corresponding to the application. The valid location is used to indicate where the relocation attribute of the application is in effect. The valid period is used to indicate a period of time for which the relocation attribute of the application is valid.

Illustratively, based on the example shown in table two, the network device may store the migration attribute of the application in the form of table three, table four, or table five.

Watch III

Information of applications	Relocation Attribute	Effective site
			Information of application A	1	Beijing
Information of application B	1	Beijing, Shanghai
			Information of application C	0	Shanghai province
Information of application D	1	Shanghai province

Watch four

Information of applications	Relocation Attribute	Effective time period
			Information of application A	1	8:00-12:00
Information of application B	1	12:00-13:00
			Information of application C	0	11:00-18:00
Information of application D	1	6:00-18:30

Watch five

Information of applications	Relocation Attribute	Effective site	Effective time period
				Information of application A	1	Beijing	8:00-12:00
Information of application B	1	Beijing, Shanghai	12:00-13:00
				Information of application C	0	Shanghai province	11:00-18:00
Information of application D	1	Shanghai province	6:00-18:30

For example, based on table three, if the terminal runs the application D in beijing, for the terminal, the migration attribute of the application D is the support application migration. If the terminal runs the application D in the Shanghai, the migration attribute of the application D is that the application migration is not supported for the terminal.

For example, based on table four, if the terminal runs application a at 8:01, the migration attribute of application a is to support application migration for the terminal. If the terminal runs the application A at 7:00, for the terminal, the migration attribute of the application A is that the application migration is not supported.

Illustratively, based on table five, if the terminal is in beijing and runs application a at 8:01, the migration attribute of application a is to support application migration for the terminal. If the terminal is in the Shanghai and runs the application A at 8:01, the relocation attribute of the application A is that the application relocation is not supported for the terminal.

It is to be understood that the above tables one to five are examples of specific implementations of the migration attribute of the network device storage application, and do not constitute a limitation to the specific implementations of the migration attribute of the network device storage application.

Optionally, the network device stores in advance a relocation attribute of all or part of the applications. Thus, for a certain application, the network device can query the migration attribute of the application from the data stored in the network device according to the information of the application.

And secondly, the network equipment acquires the relocation attribute of the application from other equipment which can communicate with the network equipment.

For example, assuming that the network device is a PCF network element, for a certain application, the PCF network element obtains the relocation attribute of the application from an application server corresponding to the application. For example, the application server of the application actively sends notification information to the PCF network element, where the notification information carries the relocation attribute of the application. Or the PCF sends an inquiry request to the application server corresponding to the application, where the inquiry request is used to inquire about the relocation attribute of the application. The application server replies response information to the PCF network element, wherein the response information comprises the relocation attribute of the application.

For another example, assuming that the network device is an SMF network element, for a certain application, the SMF network element obtains the relocation attribute of the application from the PCF network element. For example, the PCF network element sends notification information to the SMF network element, where the notification information carries the relocation attribute of the application. Or, the SMF network element may actively query the PCF network element for the relocation attribute of the application.

Optionally, after the network device obtains the migration attribute of the application from another device, the network device may store the migration attribute of the application according to a form shown in any one of tables one to five.

It should be noted that the migration attribute of the application is not fixed, in other words, the migration attribute of the application may change according to the change of the actual situation. For example, the location of the third-party application server is not changed, and under the condition that the UPF network element for transmitting the data stream of the application is closer to the third-party application server when the third-party application server wants the current UE to perform the service of the application, if the reselected UPF network element is farther from the third-party application server than the UPF network element before reselection, the relocation attribute of the application corresponding to the third-party application server at this time is that the application relocation is not supported; on the contrary, if the reselected UPF network element is closer to the third-party application server than the UPF network element before reselection, the application relocation attribute corresponding to the third-party application server is the application relocation support attribute.

For the change of the application relocation attribute, the third-party application server sends update indication information to the network equipment so as to inform the network equipment of updating the application relocation attribute. For example, for an application, the migration attribute of the application stored by the network device is that the application migration is not supported, and after the network device receives the update indication information corresponding to the application, the network device changes the migration attribute of the application to support the application migration.

After determining the migration attributes of the applications based on the above manner, the network device generates migration attribute information according to the migration attributes of the one or more applications.

Optionally, the relocation attribute information at least includes one of the following situations:

in case one, the relocation attribute information includes information of an application that does not support application relocation.

Optionally, in the case of the first scenario, for the terminal, if information of an application is in the relocation attribute information, the terminal may determine that the relocation attribute of the application is that the application relocation is not supported. Further, if the information of an application is not in the migration attribute information, the terminal can determine that the migration attribute of the application is application migration support, or the terminal defaults the migration attribute of the application as application migration support according to a preset or agreed rule.

Illustratively, in connection with the example shown in table one, the relocation attribute information generated by the network device includes: information of application C. For the terminal, after receiving the relocation attribute information, the terminal can determine that the relocation attribute of the application C is not supported by the application relocation according to the relocation attribute information. Optionally, the terminal may further determine that the migration attribute of the application other than the application C is application migration support. That is, the terminal can determine that the migration attributes of the application a, the application B, and the application D all support application migration.

And in the second situation, the relocation attribute information comprises information of the application supporting the relocation of the application.

Optionally, in the case of the second case, for the terminal, if the information of one application is in the migration attribute information, the terminal may determine that the migration attribute of the application is application migration support. Further, if the information of an application is not in the relocation attribute information, the terminal can determine that the relocation attribute of the application is not support for application relocation, or, according to a preset or agreed rule, the terminal defaults that the relocation attribute of the application is not support for application relocation.

Illustratively, based on the example shown in table one, the relocation attribute information generated by the network device includes: information of application a, information of application B, and information of application D. For the terminal, after receiving the migration attribute information, the terminal can determine that the migration attributes of the application a, the application B and the application D all support application migration according to the migration attribute information. Optionally, the terminal may further determine that the migration attribute of the application other than the application a, the application B, and the application D does not support application migration. That is, the terminal can determine that the migration attribute of the application C does not support application migration.

And thirdly, the relocation attribute information comprises first indication information and application information. The first indication information is used for indicating that the information of the application included in the relocation attribute information is information of the application which does not support application relocation. In other words, the first indication information is used to indicate that the application does not support application relocation.

Optionally, in the case of the third scenario, for the terminal, if information of an application is in the relocation attribute information, the terminal may determine that the relocation attribute of the application is that the application relocation is not supported. Further, if the information of an application is not in the migration attribute information, the terminal can determine that the migration attribute of the application is application migration support, or the terminal defaults the migration attribute of the application as application migration support according to a preset or agreed rule.

And fourthly, the relocation attribute information comprises second indication information and application information. The second indication information is used for indicating that the information of the application included in the relocation attribute information is information of the application supporting the relocation of the application. In other words, the second indication information is used to indicate that the application supports application migration.

Optionally, in the case of the fourth application, if information of an application is in the migration attribute information, the terminal may determine that the migration attribute of the application is application migration support. Further, if the information of an application is not in the relocation attribute information, the terminal can determine that the relocation attribute of the application is not support for the relocation of the application, or the terminal defaults the relocation attribute of the application as support for the relocation of the application according to a preset or agreed rule.

And in case five, the relocation attribute information comprises one or more pieces of application timer configuration information. The application timer configuration information includes configuration information of an application timer, and the application timer corresponds to an application. Further, the application timer configuration information is used to instruct the terminal to configure an application timer for the corresponding application. Optionally, before the application timer times out, the application relocation attribute corresponding to the application timer is to support application relocation. Or before the application timer is overtime, the application moving attribute corresponding to the application timer is that the application moving is not supported.

Optionally, the application timer configuration information includes: information of the application and a timing duration of the application timer. It should be noted that the timing durations of the application timers corresponding to different applications may be the same or different. Alternatively, the timing duration of the application timer may be determined according to the type of application. For example, the timing duration of the application timer corresponding to the video application is uniformly set to 5 minutes, and the timing duration of the application timer corresponding to the game application is uniformly set to 3 minutes.

In the embodiment of the present application, the trigger condition of the application timer may be predefined or indicated by the application timer configuration information. That is, the application timer configuration information may further include a trigger condition of the application timer. The trigger condition of the application timer is a condition for starting the application timer by the terminal to start timing. Illustratively, the trigger condition of the application timer is: the terminal receives the application timer configuration information.

Illustratively, the relocation attribute information includes an application timer configuration information. The application timer configuration information includes the following: the information of the application A, the timing duration of the application timer is 5 minutes. Therefore, after the terminal receives the relocation attribute information, an application timer is set for the application a, and when the application timer does not count for more than 5 minutes, the terminal can determine that the relocation attribute of the application a is application relocation support (or application relocation is not supported); after the application timer counts for more than 5 minutes, the terminal determines that the migration attribute of the application A is not support for application migration (or support for application migration).

Alternatively, the type of application timer may be predefined or indicated by application timer configuration information. It should be noted that the type of the application timer is used to indicate the relocation attribute of the application corresponding to the application timer before the application timer is not timed out. For example, when the type of the application timer is 1, before the application timer is not timed out, the migration attribute of the application corresponding to the application timer is to support application migration. When the type of the application timer is 2, before the application timer is not overtime, the application relocation attribute corresponding to the application timer is that the application relocation is not supported.

The above-mentioned cases one to five are merely examples of the migration attribute information, and do not limit the specific implementation manner of the migration attribute information.

In this embodiment of the present application, the relocation attribute information specifically adopts any one of the first to fifth cases, and is mainly determined by negotiation between the network device and a terminal, or based on factory settings of the network device, which is not limited in this embodiment of the present application.

S102, the network equipment sends the relocation attribute information to the terminal, and the terminal receives the relocation attribute information.

It should be noted that, in the embodiment of the present application, the condition under which the network device executes step S102 is not limited. For example, the network device may send the relocation attribute information to the terminal after receiving a query message (e.g., information querying for the relocation attribute of one or more applications) of the terminal. For another example, in a process of a new Protocol Data Unit (PDU) session or a route of a terminal, the network device sends relocation attribute information to the terminal.

Illustratively, if the network device is an SMF network element, the SMF network element sends the relocation attribute information to the terminal through the AMF network element.

Illustratively, if the network device is a PCF network element, the PCF network element sends the URSP information of the user equipment to the terminal, where the URSP information includes relocation attribute information.

And after receiving the relocation attribute, the terminal determines the relocation attribute of the one or more applications according to the relocation attribute information. In this way, for the first application (the first application may be any one of the one or more applications), the terminal detects whether the migration attribute of the first application does not support application migration or supports application migration. If the relocation attribute of the first application is that the application relocation is not supported, the terminal executes the following step S103; if the migration attribute of the first application is application migration support, the terminal performs the following step S104.

It should be noted that, before the terminal receives the relocation attribute information, the terminal transmits a data stream of a first application through a first route. That is, for the first application, the first route is a route used by the terminal to transmit the data stream of the first application before receiving the relocation attribute information, and the second route is a route other than the first route. In combination with an actual scenario, the first route is a route between the terminal and the UPF network element before reselection, and the second route is a route between the terminal and the UPF network element after reselection.

S103, if the relocation attribute of the first application is that the application relocation is not supported, the terminal transmits the data stream of the first application through a first route.

And S104, if the relocation attribute of the first application is application relocation support, the terminal transmits the data stream of the first application through a second route.

Optionally, as shown in fig. 6, the relocation management method provided in the embodiment of the present application further includes the following steps S105 and S106:

s105, the network equipment sends the routing timer information to the terminal, and the terminal receives the routing timer information.

And the routing timer information is used for indicating the terminal to configure a routing timer. The routing timer is used for indicating the time when the route corresponding to the routing timer is released.

Optionally, the routing timer information is used to indicate configuration information of a route corresponding to the routing timer. The configuration information of the route may be an identifier of the route, a name of the route, and the like.

Further, the routing timer information includes a timing duration of the routing timer.

In an embodiment of the present application, the trigger condition of the routing timer is predefined or indicated by the routing timer information. That is, the routing timer information may further include a trigger condition. It should be noted that the trigger condition of the routing timer is used to instruct the terminal to start the routing timer to start timing. For example, the triggering condition of the routing timer may be that the terminal receives routing timer information.

In an alternative implementation, the network device may determine the routing timer information according to the application timer configuration information. For example, the network device determines a maximum value of a timing duration of an application timer according to at least one application timer configuration information; and setting the maximum value of the timing duration of the application timer as the timing duration of the routing timer. For example, if the timing duration of the application timer 1 is 5 minutes, the timing duration of the application timer 2 is 6 minutes, and the timing duration of the application timer 3 is 8 minutes, the network device sets the timing duration of the routing timer to 8 minutes.

S106, the terminal configures the route timer according to the route timer information.

In an optional implementation manner, a terminal configures a route timer for a specified route according to route timer information; and after the route timer is overtime, the terminal releases the designated route so as to save network resources.

The actions of the terminal or the network device in steps S101 to S106 may be executed by the processor 501 in the communication device shown in fig. 5 calling the application program code stored in the memory 503, which is not limited in this embodiment of the present application.

The method shown in fig. 6 will be described with reference to an actual application scenario and the network architecture shown in fig. 1.

Based on the scenario shown in fig. 2, as shown in fig. 7, a flowchart of a relocation management method provided in another embodiment of the present application is provided, where the method includes the following steps:

s201, the SMF network element 1 reselects the SMF network element and/or the UPF network element.

In an optional implementation manner, the SMF network element 2 reselects the SMF network element and/or the UPF network element based on information such as the location of the terminal.

It should be noted that, in fig. 7, the reselected SMF network element is denoted by an SMF network element 2, and the reselected UPF network element is denoted by an UPF network element 2.

It should be noted that before the SMF network element 1 reselects the SMF network element and/or the UPF network element, the terminal has already established a first PDU session with the UPF network element 1 through the SMF network element 1, and the terminal transmits the data stream of the application through the route (i.e., the first route) of the first PDU session.

S202, the SMF network element 1 sends the relocation attribute information to the terminal through the AMF network element.

Optionally, the relocation attribute information may be included in the Nmaf _ communication _ N1N2MessageTransfer message. It should be noted that, here, only one example of the message name is given, and the message for sending the relocation attribute information is not limited.

Optionally, if the SMF network element determines that the application does not support application relocation in the first PDU session, the SMF network element does not issue the routing timer information to the terminal. That is, the SMF network element does not force the terminal to release the first route.

Alternatively, step S202 may be replaced with step S202 b.

S202b, the PCF network element sends URSP information to the terminal using Non-access stratum (NAS) signaling, where the URSP information includes relocation attribute information.

It should be noted that, in the embodiment of the present application, the execution time of step S202 (or step S202b) is not limited. For example, the following steps S203-S204 may be performed first, and then step S202 (or step S202b) may be performed. Alternatively, step S202 (or step S202b) and step S203 may be performed simultaneously.

S203, the AMF network element sends session establishment indication information to the terminal by using NAS signaling. The session establishment indication information is used for indicating the terminal to establish a second PDU session with the SMF network element 2/UPF network element 2.

S204, the terminal initiates a second PDU session establishment flow.

S205, the terminal transmits the data flow of the application supporting the application relocation through the route (namely, the second route) of the second PDU session. Specifically, the terminal may switch the data stream of the application supporting the application relocation to the second route for transmission.

S206, the terminal transmits the data stream of the application that does not support the application relocation through the route (i.e. the first route) of the first PUD session. In particular, the terminal may keep the data stream of the application that does not support the application relocation transmitted on the first route.

S207, after the data flow in the first PDU session is finished, the terminal initiates a signaling flow for releasing the first PDU session.

In an optional implementation manner, after the data flow in the first PDU session is finished, that is, after the first route has transmitted all the data flows of the applications that do not support application migration, the terminal may initiate a release procedure of the first PDU session. Specifically, the terminal sends a release request of a first PDU session to the AMF network element; the AMF network element sends the release request to the SMF network element 1; the SMF network element 1 releases the first PDU session according to the release request and returns a response message to the AMF network element to inform the AMF network element that the first PDU session is successfully released; and the AMF network element sends the response message to the terminal.

Of course, if the terminal migrates all the application data streams to the second route for transmission, the terminal may also directly initiate a signaling procedure for releasing the first PDU session.

It should be noted that the flow of the terminal newly establishing the PDU session shown in fig. 7 only illustrates some steps related to the technical solution shown in fig. 6, so as to illustrate an application scenario of the technical solution shown in fig. 6. In actual implementation, the process of newly creating a PDU session may further include other steps, which have been described in detail in the prior art, and are not described in detail in this embodiment of the present application.

Based on the scenario shown in fig. 3, as shown in fig. 8, a flowchart of a relocation management method provided in another embodiment of the present application is provided, where the method includes the following steps:

s301, the terminal establishes a PDU session, and a first PDU session anchor point of the PDU session is a UPF network element 4. That is, a first route exists between the terminal and the UPF network element 1, and the terminal transmits the data stream of the application through the first route.

S302, the SMF network element selects a second PDU session anchor point (i.e. the UPF network element 5 in fig. 8).

In an optional implementation manner, the SMF network element selects the second PDU session anchor based on information such as the location of the terminal.

S303, the SMF network element selects a shunting point (i.e. the UPF network element 3 in fig. 8).

The shunting point is used for shunting data streams which belong to the same PDU session but belong to different routes.

S304, the SMF network element notifies the UPF network element 4 of the information of the forking point, so as to update the first route.

S305, the SMF network element establishes a second route between the terminal and the UPF network element 5.

S306, similar to step S202, the related description of step S306 can refer to the embodiment shown in fig. 7, and is not repeated herein.

In addition, the execution time of step S306 is not limited in the embodiment of the present application. For example, step S306 may be performed first, followed by steps S301-S305. Alternatively, step S301 is executed first, then step S306 is executed, and then steps S302-S305 are executed. Still alternatively, step S301 and step S306 may be executed in parallel.

S307-S309, similar to steps S205-S207, differ in that: in step S207, the terminal releases the first PDU session; and in step S309, the terminal releases only the first route in the PDU session. The related descriptions of steps S307-S309 can refer to the embodiment shown in fig. 7, and are not repeated herein.

It should be noted that the flow of the terminal establishing a new route for the PDU session shown in fig. 8 only illustrates some steps related to the technical solution shown in fig. 6, so as to illustrate an application scenario of the technical solution shown in fig. 6. In actual implementation, the flow of creating a new route may include other steps, which have been described in detail in the prior art, and are not described in detail in this embodiment of the present application.

The above description mainly introduces the scheme provided in the embodiments of the present application from the perspective of a terminal and a network device. It is to be understood that the terminal and the network device include hardware structures or software modules for performing the respective functions in order to realize the functions. Those of skill in the art would readily appreciate that the various illustrative elements and algorithm steps described in connection with the embodiments disclosed herein may be implemented as hardware or combinations of hardware and computer software. Whether a function is performed as hardware or computer software drives hardware depends upon the particular application and design constraints imposed on the solution. Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present application.

For example, in the case of dividing each functional module by corresponding functions, fig. 9 shows a schematic structural diagram of a terminal. As shown in fig. 9, the terminal includes a communication module 901. Optionally, the terminal further includes a processing module 902.

A communication module 901, configured to receive relocation attribute information, where the relocation attribute information is used to indicate relocation attributes of one or more applications, where the relocation attributes include that application relocation is supported or that application relocation is not supported, and the one or more applications include a first application.

The communication module 901 is further configured to transmit a data stream of the first application through a first route when the migration attribute of the first application is that application migration is not supported; and when the migration attribute of the first application is application migration support, transmitting the data stream of the first application through a second route.

Further, the processing module 902 is configured to determine a migration attribute of the first application, where the migration attribute of the first application is that application migration is not supported or application migration is supported.

In a possible design, the communication module 901 is configured to transmit a data stream of the first application through the first route before receiving the relocation attribute information.

Optionally, the relocation attribute information is used to indicate relocation attributes of one or more applications, and at least includes one of the following situations: (1) the relocation attribute information includes information of an application that does not support application relocation; (2) the relocation attribute information comprises information of an application supporting relocation of the application; (3) the relocation attribute information comprises first indication information and application information, wherein the first indication information is used for indicating that the application information included in the relocation attribute information is the application information supporting application relocation; (4) the relocation attribute information comprises second indication information and application information, wherein the second indication information is used for indicating that the application information included in the relocation attribute information is the application information which does not support application relocation; (5) the relocation attribute information comprises one or more application timer configuration information, and the application timer configuration information is used for indicating the configuration of an application timer; before the application timer is overtime, the application moving attribute corresponding to the application timer is application moving support; or before the application timer is overtime, the application moving attribute corresponding to the application timer is that the application moving is not supported.

Optionally, the information of the application at least includes one of the following situations: an identification of the application; a data flow identification of the application; triplet information, the triplet information comprising: address and port and transport layer protocols; quintuple information including a destination address, a source address, a destination port, a source port, and a transport layer protocol.

In one possible design, the communication module 901 is further configured to receive routing timer information. The processing module 902 is configured to configure a routing timer according to the routing timer.

In the embodiment of the present application, the terminal is presented in a form of dividing each functional module corresponding to each function, or the terminal is presented in a form of dividing each functional module in an integrated manner. A "module" herein may include an Application-Specific Integrated Circuit (ASIC), an electronic Circuit, a processor and memory that execute one or more software or firmware programs, an Integrated logic Circuit, or other devices that provide the described functionality. For example, the communication module 901 shown in fig. 9 may be implemented by the communication interface 503 shown in fig. 5, and the processing module shown in fig. 9 may be implemented by the processor 501 or the processor 507 shown in fig. 5, which is not limited in this embodiment of the present application.

An embodiment of the present application further provides a computer-readable storage medium, in which instructions are stored; when the computer-readable storage medium runs on the terminal shown in fig. 5, the terminal is caused to execute the relocation management method shown in fig. 6 to 8 in the embodiment of the present application.

Optionally, an embodiment of the present application provides a chip system, where the chip system includes a processor, and is used to support a terminal to implement the relocation management method shown in fig. 6 to 8. In one possible design, the system-on-chip further includes a memory. The memory is used for storing program instructions and data necessary for the receiver. Of course, the memory may not be in the system-on-chip. The chip system may be formed by a chip, and may also include a chip and other discrete devices, which is not specifically limited in this embodiment of the present application.

For example, in the case of dividing each functional module by corresponding functions, fig. 10 shows a schematic structural diagram of a network device. As shown in fig. 10, the network device includes a processing module 1001 and a sending module 1002.

The processing module 1001 is configured to determine relocation attribute information, where the relocation attribute information is used to indicate relocation attributes of one or more applications, and the relocation attributes include that application relocation is supported or application relocation is not supported.

A sending module 1002, configured to send the relocation attribute information to a terminal.

Optionally, the information of the application at least includes one of the following situations: an identification of the application; a data flow identification of the application; triplet information, the triplet information comprising: address, port and transport layer protocols; quintuple information including a destination address, a source address, a destination port, a source port, and a transport layer protocol.

In a possible design, the sending module 1002 is further configured to send routing timer information to the terminal device, where the routing timer information is used to indicate configuration information of a route corresponding to the routing timer.

In one possible design, the processing module 1002 is further configured to determine routing timer information according to the application timer configuration information.

In a possible design, the sending module 1002 is configured to send, to the terminal, URSP information when the network device is a policy function control network element, where the URSP information includes the relocation attribute information.

In the embodiment of the present application, the network device is presented in a form of dividing each functional module corresponding to each function, or the network device is presented in a form of dividing each functional module in an integrated manner. A "module" herein may include an application specific integrated circuit, a processor and memory that execute one or more software or firmware programs, an integrated logic circuit, or other devices that may provide the described functionality. For example, the processing module 1001 shown in fig. 10 may be implemented by the processor 501 or the processor 507 shown in fig. 5, and the sending module 1002 shown in fig. 10 may be implemented by the communication interface 503 shown in fig. 5, which is not limited in this embodiment of the present application.

An embodiment of the present application further provides a computer-readable storage medium, in which instructions are stored; when the computer-readable storage medium runs on the network device shown in fig. 5, the network device is caused to execute the relocation management method shown in fig. 6 to 8 in the embodiment of the present application.

Optionally, an embodiment of the present application provides a chip system, where the chip system includes a processor, and is used to support a network device to implement the relocation management method shown in fig. 6 to 8. In one possible design, the system-on-chip further includes a memory. The memory is used for storing program instructions and data necessary for the receiver. Of course, the memory may not be in the system-on-chip. The chip system may be formed by a chip, and may also include a chip and other discrete devices, which is not specifically limited in this embodiment of the present application.

In the above embodiments, the implementation may be wholly or partially realized by software, hardware, firmware, or any combination thereof. When implemented using a software program, 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 instructions. The procedures or functions described in accordance with the embodiments of the present application are all or partially generated upon loading and execution of computer program instructions on a computer. The computer may be a general purpose computer, a special purpose computer, a network of computers, or other programmable device. The computer instructions may be stored on a computer readable storage medium or transmitted from one computer readable storage medium to another, for example, from one website, computer, server, or data center to another website, computer, server, or data center via wire (e.g., coaxial cable, fiber optic, Digital Subscriber Line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.). The computer-readable storage medium can be any available medium that can be accessed by a computer or can comprise one or more data storage devices, such as a server, a data center, etc., that can be integrated with the medium. The usable medium may be a magnetic medium (e.g., floppy disk, hard disk, magnetic tape), an optical medium (e.g., DVD), or a semiconductor medium (e.g., Solid State Disk (SSD)), among others.

Although the present application has been described in conjunction with specific features and embodiments thereof, it will be evident that various modifications and combinations can be made thereto without departing from the spirit and scope of the application. Accordingly, the specification and figures are merely exemplary of the present application as defined in the appended claims and are intended to cover any and all modifications, variations, combinations, or equivalents within the scope of the present application. It will be apparent to those skilled in the art that various changes and modifications may be made in the present application without departing from the spirit and scope of the application. Thus, if such modifications and variations of the present application fall within the scope of the claims of the present application and their equivalents, the present application is intended to include such modifications and variations as well.

Claims

1. A relocation management method, characterized in that the method comprises:

the method comprises the steps that a terminal receives relocation attribute information, wherein the relocation attribute information is used for indicating relocation attributes of one or more applications, the relocation attributes comprise application relocation support or application relocation unsupported, and the one or more applications comprise first applications;

if the relocation attribute of the first application is that the application relocation is not supported, the terminal transmits the data stream of the first application through a first route;

if the relocation attribute of the first application is application relocation support, the terminal transmits the data stream of the first application through a second route;

the relocation attribute information comprises one or more application timer configuration information, and the application timer configuration information is used for indicating the configuration of an application timer; before the application timer is overtime, the application moving attribute corresponding to the application timer is application moving support; or before the application timer is overtime, the application moving attribute corresponding to the application timer is that the application moving is not supported.

2. The relocation management method according to claim 1, further comprising:

and before the terminal receives the relocation attribute information, the terminal transmits the data stream of the first application through the first route.

3. The relocation management method according to claim 2, wherein the relocation attribute information is used to indicate relocation attributes of one or more applications, and includes at least one of:

the relocation attribute information includes information of an application that does not support application relocation;

the relocation attribute information comprises information of an application supporting relocation of the application;

the relocation attribute information comprises first indication information and application information, wherein the first indication information is used for indicating that the application information included in the relocation attribute information is the application information supporting application relocation;

the relocation attribute information includes second indication information and application information, and the second indication information is used for indicating that the application information included in the relocation attribute information is information of an application that does not support application relocation.

4. The relocation management method according to claim 3, wherein the information of the application includes at least one of:

an identification of the application;

a data flow identification of the application;

triplet information, the triplet information comprising: address, port and transport layer protocols;

quintuple information including a destination address, a source address, a destination port, a source port, and a transport layer protocol.

5. The relocation management method according to any one of claims 1 to 4, further comprising:

the terminal receives routing timer information;

and the terminal configures a routing timer according to the routing timer information.

6. A relocation management method, characterized in that the method comprises:

the network equipment determines relocation attribute information, wherein the relocation attribute information is used for indicating relocation attributes of one or more applications, and the relocation attributes comprise application relocation support or application relocation unsupported;

the network equipment sends the relocation attribute information to a terminal;

7. The relocation management method according to claim 6, wherein the relocation attribute information is used to indicate relocation attributes of one or more applications, and includes at least one of:

8. The relocation management method according to claim 7, wherein the information of the application includes at least one of:

an identification of the application;

a data flow identification of the application;

9. The relocation management method according to claim 8, further comprising:

and the network equipment sends routing timer information to the terminal equipment, wherein the routing timer information is used for indicating the configuration information of the route corresponding to the routing timer.

10. The relocation management method according to claim 9, further comprising:

and the network equipment determines the routing timer information according to the application timer configuration information.

11. The relocation management method according to any one of claims 6 to 10, wherein the network device is a policy function control network element,

wherein, the sending, by the network device, the relocation attribute information to the terminal includes:

and the policy function control network element sends URSP information of a user equipment routing policy to the terminal, wherein the URSP information comprises the relocation attribute information.

12. A terminal, comprising:

the communication module is used for receiving relocation attribute information, the relocation attribute information is used for indicating relocation attributes of one or more applications, the relocation attributes comprise that application relocation is supported or application relocation is not supported, and the one or more applications comprise first applications;

the communication module is further configured to transmit a data stream of the first application through a first route when the migration attribute of the first application is that application migration is not supported; when the relocation attribute of the first application is application relocation support, transmitting the data stream of the first application through a second route;

13. The terminal according to claim 12, wherein the communication module is configured to transmit a data flow of the first application through the first route before receiving the relocation attribute information.

14. The terminal according to claim 13, wherein the relocation attribute information is used to indicate relocation attributes of one or more applications, and includes at least one of:

15. The terminal according to claim 14, wherein the information of the application comprises at least one of the following situations:

an identification of the application;

a data flow identification of the application;

16. The terminal according to any of claims 12 to 15, characterized in that the terminal further comprises: a processing module;

the communication module is further used for receiving routing timer information;

and the processing module is used for configuring a routing timer according to the routing timer information.

17. A network device, comprising:

the system comprises a processing module, a storage module and a processing module, wherein the processing module is used for determining relocation attribute information, the relocation attribute information is used for indicating relocation attributes of one or more applications, and the relocation attributes comprise application relocation support or application relocation unsupported;

the sending module is used for sending the relocation attribute information to a terminal;

18. The network device of claim 17, wherein the relocation attribute information is used to indicate relocation attributes of one or more applications, and includes at least one of:

19. The network device of claim 18, wherein the information of the application comprises at least one of:

an identification of the application;

a data flow identification of the application;

20. The network device according to claim 19, wherein the sending module is further configured to send routing timer information to the terminal device, where the routing timer information is used to indicate configuration information of a route corresponding to a routing timer.

21. The network device of claim 20, wherein the processing module is further configured to determine the routing timer information according to application timer configuration information.

22. The network device according to any one of claims 17 to 21, wherein the sending module is configured to send, to the terminal, URSP information of a user equipment routing policy when the network device is a policy function control network element, where the URSP information includes the relocation attribute information.

23. A terminal comprising a processor that, when executing a computer program stored on a memory, causes the terminal to perform the relocation management method according to any one of claims 1 to 5.

24. A computer-readable storage medium, having stored thereon a computer program which, when run on a computer, causes the computer to execute the relocation management method according to any one of claims 1 to 5.

25. A network device comprising a processor that, when executing a computer program stored on a memory, causes the network device to perform the relocation management method of any of claims 6 to 11.

26. A computer-readable storage medium, having stored thereon a computer program which, when run on a computer, causes the computer to execute the relocation management method according to any one of claims 6 to 11.