WO2022252964A1

WO2022252964A1 - Service transfer method and apparatus

Info

Publication number: WO2022252964A1
Application number: PCT/CN2022/092740
Authority: WO
Inventors: 彭文杰
Original assignee: 华为技术有限公司
Priority date: 2021-05-31
Filing date: 2022-05-13
Publication date: 2022-12-08
Also published as: CN115484565A

Abstract

The present application relates to the technical field of wireless communications, and provides a service transfer method and apparatus, in order to improve the universality of service transfer methods. In the method, a first device can send a service transfer request to a core network device. The service transfer request may comprise information of a second device. The service transfer request can be used for requesting to transfer a service to be transferred from a source device to a target device. The first device can receive a first message from the core network device. The first message may comprise information of the service to be transferred.

Description

Method and device for service transfer

Cross References to Related Applications

This application claims the priority of a Chinese patent application filed with the Intellectual Property Office of the People's Republic of China on May 31, 2021, with application number 202110599761.3, and application name "A Method and Device for Business Transfer", the entire contents of which are incorporated by reference In this application.

technical field

The present application relates to the technical field of wireless communication, and in particular to a service transfer method and device.

Background technique

In related technologies, some application software can support the switching of user services from one device to another device, for example, a video on a mobile phone can be projected to a TV.

However, this method requires software to support the above functions, so it is not universal. Not only that, the above-mentioned functional network is not aware, so business continuity cannot be guaranteed.

Contents of the invention

The present application provides a service transfer method and device, in order to improve the universality of the service transfer method.

In the first aspect, a service transfer method is improved. The method may be executed by the first device provided in the embodiment of the present application, or by a chip having a function similar to that of the first device. Wherein, the first device may be a device capable of communicating with a network. In this method, the first device may send a service transfer request to the core network device. Wherein, the service transfer request may include the information of the second device. The aforementioned service transfer request may be used to request to transfer the service to be transferred from the source device to the target device. The first device may receive the first message from the core network device. Wherein, the first message may include service information to be transferred.

Based on the above solution, the first device can initiate a service transfer process to the core network device, enabling the user's service to be transferred between different devices, which is universal. Moreover, the network can perceive the service transfer process, which can improve service continuity.

In a possible implementation manner, the first device may receive service information to be transferred from the second device. Wherein, when the second device is the source device, the first device is the target device.

Based on the above solution, the target device can initiate a service transfer process to the core network device, enabling the user's service to be transferred from the source device to the target device.

In a possible implementation manner, the first device may receive the information of the second device from the second device.

Based on the above solution, the source device can trigger the target device to initiate the service transfer process, and send the source device information to the target device, enabling the target device to carry the source device information when initiating the service transfer process to the core network device.

In a possible implementation manner, the service transfer request may also include service information to be transferred.

In a possible implementation manner, the first message may be a service establishment request.

Based on the above solution, the core network device can establish a service with the target device through a service establishment request, and transmit service data with the target device, thereby improving service continuity.

In a possible implementation manner, when the first device is a source device, the second device is a target device. The first message may release the message for the service.

Based on the above solution, the source device can initiate a service transfer process to the core network device, enabling the user's service to be transferred from the source device to the target device.

In a possible implementation manner, the first device may receive service data from the second device; the service data may be cached data of a service to be transferred. Alternatively, the first device may send the service data to the second device, and the service data may be cached data of the service to be transferred.

Based on the above solution, the source device can send the cached data of the service to the target device, so as to improve the continuity of the service.

In a possible implementation manner, when the second device is a source device, the third device is a target device. The third device may be a personal IoT network (personal IoT network, PIN) device managed by the first device.

Based on the above solution, if the target device does not have the ability to communicate with the network, it can communicate with the network through the PIN management device, enabling the user's business to be transferred from the source device to the target device.

In a possible implementation manner, the first device may receive the service information to be transferred, the information of the third device, and the information of the second device from the second device.

Based on the above solution, the source device may trigger the first device to initiate a service transfer process, so that the first device acquires information of the target device and information of the source device.

In a possible implementation manner, the first device may receive the service information to be transferred from the third device and the information of the second device.

In a possible implementation manner, the information of the second device may include at least one of the following: an identifier of the second device, a device identifier for managing the second device, a PIN identifier of the second device, a PIN device identifier of the second device , temporary mobile subscriber identity (serving-tmeporary mobile subscriber identity, S-TMSI), globally unique temporary identity (globally unique temporary UE identity, GUTI), user permanent identifier (subscription permanent identifier, SUPI) SUPI or user hidden identifier ( subscription concealed identifier, SUCI).

In a possible implementation manner, the service information to be transferred may include at least one of protocol data unit (protocol data unit, PDU) session information and quality of service (quality of service, QoS) flow information.

In a possible implementation manner, the first device may receive service data from the second device, where the service data is cached data of a service to be transferred. The first device may forward the service data to the third device.

In the second aspect, a service transfer method is provided. The method can be executed by a core network device, or by a chip with a function similar to that of the core network device. In this method, the core network device may receive the service transfer request from the first device. Wherein, the service transfer request may include the information of the second device, and the service transfer request may be used to request transfer of the service to be transferred from the source device to the target device. The core network device may send a first message to the first device, where the first message includes service information to be transferred.

In a possible implementation manner, when the second device is the source device and the first device is the target device, the first message may be a service establishment request.

In a possible implementation manner, when the first device is the source device and the second device is the target device, the first message may be a service release message.

In a possible implementation manner, when the second device is a source device, the third device is a target device. Wherein, the third device may be a PIN device managed by the first device.

In a possible implementation manner, the first message may further include information about the third device.

Based on the above solution, the first message may carry the information of the third device, so that the first device can determine the target device in the PIN.

In a possible implementation manner, the information of the second device may include at least one of the following: an identifier of the second device, a device identifier for managing the second device, a PIN identifier of the second device, a PIN device identifier of the second device , S-TMSI, GUTI, SUPI, or SUCI.

In a possible implementation manner, the service information to be transferred may include at least one of PDU session information and quality of service (QoS) flow information.

In the third aspect, a service transfer method is provided. The method can be executed by a core network device, or by a chip with a function similar to that of the core network device. In this method, the core network device may receive the service transfer request from the first device. Wherein, the service transfer request is used to request to transfer the service to be transferred to the target device. The core network device may send the first request message to the access network device. Wherein, the first request message is used to instruct the access network device to establish a target PDU session for the target device.

Based on the above solution, the core network device may send a first request message to the access network device, requesting the core network device to establish a PDU session for the target device.

In a possible implementation manner, the first request message may include target device information, target PDU session information, and indication information. Wherein, the indication information may be used to indicate that the target PDU session of the target device uses the source PDU session of the first device. The information of the target PDU session may include at least one piece of QoS flow information, and the at least one piece of QoS flow information is the QoS flow information for the first device to execute the service to be transferred.

Based on the above solution, the core network device may indicate to the access network device through indication information that the information of the target PDU session is the information of the source PDU session, or that the target device uses the source PDU session.

In a possible implementation manner, the indication information may include at least one of the following: an identifier of the first device or information about the first GTP tunnel of the first device.

In a possible implementation manner, the core network device may receive the first response message from the access network device. Wherein, the first response message may include the identifier of the target PDU session and the information of the first GTP tunnel. The first GTP tunnel is the GTP tunnel of the source PDU session of the first device.

Based on the above solution, the access network device can establish a target PDU session for the target device, and the GTP tunnel of the target PDU session is the same as the GTP tunnel of the source PDU session. In other words, the GTP tunnel of the target PDU session uses the GTP tunnel of the source PDU session to avoid frequent changes of the GTP tunnel.

In a possible implementation manner, the core network device may send the second request message to the access network device. Wherein, the second request message may be used to request the access network device to release the source PDU session of the first device. The second request message may contain an identification of the source PDU session.

Based on the above solution, the source PDU session of the first device can be released, but the GTP tunnel of the source PDU session is reserved for the target PDU session.

In a possible implementation manner, the core network device may receive the second response message from the access network device. Wherein, the second response message is used to inform the core network device that the PDU session of the first device has been released.

In the fourth aspect, a service transfer method is provided. The method can be executed by an access network device, or by a chip similar to the function of the access network device. In this method, the access network device may receive the first request message from the core network device. Wherein, the first request message may be used to instruct the access network device to establish a target PDU session for the target device. Wherein, the first request message includes indication information. The indication information may be used to indicate that the target PDU session of the target device uses the source PDU session of the first device.

Based on the above solution, the core network device may send a first request message to the access network device, requesting the core network device to establish a PDU session for the target device. Moreover, the core network device may indicate to the access network device through indication information that the information of the target PDU session is the information of the source PDU session, or that the target device uses the source PDU session.

In a possible implementation manner, the access network device sends the first response message to the core network device. Wherein, the first response message may include the identifier of the target PDU session and the information of the first GTP tunnel. The first GTP tunnel is the GTP tunnel of the source PDU session.

In a possible implementation manner, the first request message may further include target device information and target PDU session information. Wherein, the information of the target PDU session includes at least one piece of QoS flow information, and the at least one piece of QoS flow information may be the QoS flow information for the first device to execute the service to be transferred.

In a possible implementation manner, the indication information may include at least one of the following: an identifier of the first device or first GTP tunnel information of the first device.

In a possible implementation manner, the access network device may receive the second request message from the core network device. Wherein, the second request message is used to request the access network device to release the source PDU session of the first device; the second request message may include the source PDU session identifier.

In a possible implementation manner, the access network device may send the second response message to the core network device. Wherein, the second response message is used to inform the core network device that the PDU session of the first device has been released.

In a fifth aspect, a communication device is provided, including a transceiver module and a processing module. Wherein, the processing module is used to generate a service transfer request. The service transfer request includes the information of the second device, and the service transfer request is used to request to transfer the service to be transferred from the source device to the target device. The transceiver module is used to send a service transfer request to the core network equipment. The transceiver module is also used to receive the first message from the core network equipment; the first message includes the service information to be transferred.

In one design, before sending the service transfer request to the core network device, the transceiver module is further configured to: receive service information to be transferred from the second device; the second device is the source device, and the first device is the target device.

In one design, the transceiving module is further configured to receive information from the second device of the second device.

In one design, the service transfer request also includes service information to be transferred.

In one design, the first message is a service setup request.

In one design, the first device is a source device, and the second device is a target device; the first message is a service release message.

In one design, the second device is a source device, and the third device is a target device; the third device is a PIN device managed by the first device.

In one design, before sending the service transfer request to the core network device, the transceiver module is further configured to: receive service information to be transferred from the second device and information from the third device.

In one design, before sending the service transfer request to the core network device, the transceiver module is further configured to: receive service information to be transferred from the third device and information of the second device.

In one design, the information of the second device includes at least one of the following: an identifier of the second device, a device identifier for managing the second device, a PIN identifier of the second device, a PIN device identifier of the second device, an S-TMSI , GUTI, SUPI or SUCI.

In one design, the service information to be transferred includes at least one of PDU session information and QoS flow information.

According to a sixth aspect, a communication device is provided, including a transceiver module and a processing module. Wherein, the transceiver module is used to receive a service transfer request from the first device; the service transfer request includes the information of the second device, and the service transfer request is used to request transfer of the service to be transferred from the source device to the target device. A processing module, configured to generate a first message. The transceiver module is further configured to send a first message to the first device; the first message includes service information to be transferred.

In one design, the second device is a source device, and the first device is a target device; the first message is a service establishment request.

In one design, the first message also includes information about the third device.

In a seventh aspect, a communication device is provided, including a transceiver module and a processing module. Wherein, the transceiver module is configured to receive a service transfer request from the first device; the service transfer request is used to request transfer of the service to be transferred to the target device. A processing module, configured to generate a first request message. The first request message is used to instruct the access network device to establish a target PDU session for the target device. The transceiver module is further configured to send the first request message to the access network device.

In one design, the first request message includes target device information, target PDU session information, and indication information; the indication information is used to indicate that the target PDU session of the target device uses the source PDU session of the first device; the target PDU session information It includes at least one piece of QoS flow information; the at least one piece of QoS flow information is the QoS flow information for the first device to execute the service to be transferred.

In one design, the indication information includes at least one of the following: an identifier of the first device or information of a first GTP tunnel of the source PDU session.

In one design, the transceiver module is also used to receive a first response message from the access network device; the first response message includes the identifier of the target PDU session and the information of the first GTP tunnel; the first GTP tunnel is the source PDU session GTP tunnel.

In one design, the transceiver module is further configured to send a second request message to the access network device; the second request message is used to request the access network device to release the source PDU session; the second request message includes the identifier of the source PDU session.

In an eighth aspect, a communication device is provided, including a transceiver module and a processing module. Wherein, the transceiver module is configured to receive a first request message from the core network device; the first request message is used to instruct the access network device to establish a target PDU session for the target device. Wherein, the first request message includes indication information; the indication information is used to indicate that the target PDU session of the target device uses the source PDU session of the first device.

In one design, a processing module is configured to generate a first response message. The first response message includes the identifier of the target PDU session and information of the first GTP tunnel; the first GTP tunnel is the GTP tunnel of the source PDU session. The transceiver module is further configured to send the first response message to the core network equipment.

In one design, the first request message also includes the information of the target device and the information of the target PDU session; the information of the target PDU session includes at least one QoS flow information; at least one QoS flow information is the QoS of the first device executing the service to be transferred stream information.

In one design, the access network device receives a second request message from the core network device; the second request message is used to request the access network device to release the source PDU session; the second request message includes the identifier of the source PDU session.

In the ninth aspect, the present application provides a communication device, including a processor, the processor is coupled to a memory, the memory is used to store computer programs or instructions, and the processor is used to execute the computer programs or instructions to implement the first aspect or the second aspect above Or the implementation methods of the third aspect or the fourth aspect. The memory may be located within the device or external to the device. The number of the processors is one or more.

In a tenth aspect, the present application provides a communication device, including: a processor and an interface circuit, the interface circuit is used to communicate with other devices, and the processor is used in each of the first aspect or the second aspect or the third aspect or the fourth aspect. Implementation.

In an eleventh aspect, a communication device is provided. The device includes a logic circuit and an input and output interface.

In one design, logic circuitry is used to generate traffic transfer requests. The service transfer request includes the information of the second device, and the service transfer request is used to request to transfer the service to be transferred from the source device to the target device. The input and output interfaces are used to output service transfer requests. The input and output interface is also used for inputting the first message. The first message includes service information to be transferred.

In one design, an input-output interface is used to input traffic transfer requests. The service transfer request includes the information of the second device, and the service transfer request is used to request to transfer the service to be transferred from the source device to the target device. A logic circuit for generating a first message. Wherein, the first message includes service information to be transferred. The input and output interface is used to output the first message.

In one design, an input-output interface is used to input traffic transfer requests. The service transfer request includes the information of the second device, and the service transfer request is used to request to transfer the service to be transferred from the source device to the target device. A logic circuit, configured to generate a first request message. The first request message is used to instruct the access network device to establish a target PDU session for the target device. The input and output interface is used to output the first request message.

In one design, the input-output interface is used to receive the first request message. The first request message is used to instruct the access network device to establish a target PDU session for the target device. Wherein, the first request message includes indication information; the indication information is used to indicate that the target PDU session of the target device uses the source PDU session of the first device. Optionally, a logic circuit is used to generate the first response message. The first response message includes the identifier of the target PDU session and the information of the first GTP tunnel; the first GTP tunnel is the GTP tunnel of the source PDU session. The input and output interface is used to output the first response message.

In a twelfth aspect, the present application provides a communication system, including at least: a first device configured to execute the implementation methods of the first aspect above, and a core network device configured to execute the implementation methods of the second aspect above.

In a thirteenth aspect, the present application provides a communication system, including at least: a core network device configured to execute the implementation methods of the third aspect above, and an access network device configured to execute the implementation methods of the fourth aspect above.

In a fourteenth aspect, the present application further provides a chip system, including: a processor, configured to execute each implementation method of the above-mentioned first aspect or the second aspect or the third aspect or the fourth aspect.

In the fifteenth aspect, the present application also provides a computer program product, including computer-executable instructions, when the computer-executable instructions are run on the computer, each of the above-mentioned first aspect or the second aspect or the third aspect or the fourth aspect can be realized method is executed.

In the sixteenth aspect, the present application also provides a computer-readable storage medium, in which computer programs or instructions are stored, and when the instructions are run on the computer, the above-mentioned first aspect or the second aspect or the third aspect can be realized. Each implementation method of the aspect or the fourth aspect.

In addition, for the beneficial effects of the fifth aspect to the sixteenth aspect, reference may be made to the beneficial effects of the first aspect to the fourth aspect, which will not be repeated here.

Description of drawings

FIG. 1A is one of the schematic diagrams of the communication system provided by the embodiment of the present application;

FIG. 1B is one of the schematic diagrams of the communication system provided by the embodiment of the present application;

FIG. 2A is one of the schematic diagrams of application scenarios provided by the embodiment of the present application;

FIG. 2B is one of the schematic diagrams of application scenarios provided by the embodiment of the present application;

FIG. 3 is one of the exemplary flowcharts of the service transfer method provided by the embodiment of the present application;

FIG. 4 is one of the exemplary flowcharts of the service transfer method provided by the embodiment of the present application;

FIG. 5 is one of the exemplary flowcharts of the service transfer method provided by the embodiment of the present application;

FIG. 6 is one of the exemplary flowcharts of the service transfer method provided by the embodiment of the present application;

FIG. 7 is one of the exemplary flowcharts of the service transfer method provided by the embodiment of the present application;

FIG. 8 is one of the exemplary flowcharts of the service transfer method provided by the embodiment of the present application;

FIG. 9 is one of the exemplary flowcharts of the service transfer method provided by the embodiment of the present application;

FIG. 10 is one of the exemplary flowcharts of the service transfer method provided by the embodiment of the present application;

FIG. 11 is one of the exemplary flowcharts of the service transfer method provided by the embodiment of the present application;

FIG. 12A is one of the GTP tunnel schematic diagrams of the first device and the second device provided by the embodiment of the present application;

FIG. 12B is one of the GTP tunnel schematic diagrams of the first device and the second device provided by the embodiment of the present application;

FIG. 13 is one of the exemplary flowcharts of the service transfer method provided by the embodiment of the present application;

FIG. 14 is one of the schematic diagrams of the communication device provided by the embodiment of the present application;

FIG. 15 is one of the schematic diagrams of the communication device provided by the embodiment of the present application;

FIG. 16 is one of the schematic diagrams of the communication device provided by the embodiment of the present application;

FIG. 17 is one of the schematic diagrams of the communication device provided by the embodiment of the present application.

Detailed ways

In the following, technical terms involved in the embodiments of the present application are explained and illustrated.

1) Personal IoT network (PIN), which can be understood as a network formed by different devices of the same user. For example, a user's mobile phone and watch can form a PIN, and both the mobile phone and the watch can be considered as PIN elements or PIN devices. Within this PIN, the user's voice service can be transferred between the phone and the watch.

Optionally, the user's device can add different devices to the PIN through a PIN element with a management function, and the PIN element with a management function can be called a management device or a PIN management device. For example, although TVs or stereos do not have the ability to directly communicate with base stations, they can also access the network through management devices.

2) Service transfer can be understood as transferring any service of a user from one device to another. For example, the user's voice service can be transferred from the mobile phone to the watch. Wherein, the mobile phone may be referred to as a source device, and the watch may be referred to as a target device.

Hereinafter, the service transfer method provided by the embodiment of the present application will be explained and described in conjunction with the accompanying drawings.

As the user equipment (user equipment, UE) continues to become more intelligent, the demand for user services is also constantly enriched, and there are more and more demands for user services to be transferred between different devices. In the PIN, there may be some devices that do not have the ability to directly communicate with the base station. Such devices need to rely on the management device to work. It can be understood that the device is sending and receiving data with the management device. However, some devices themselves can communicate with the base station. At this time, the management device may not participate in the communication between the device and the base station, or the management device may also act as a relay between the device and the base station, such as relaying UE (UE- to-Network relay). The device can establish a connection with the network and create services through the management device, and the management device only acts as a pipeline in the middle.

In related technologies, a user's business can be transferred from one device to another. For example, you can cast a video playing on your phone to your TV. However, this service transfer method requires software support, is not universal, and the network cannot perceive the service transfer, so service continuity cannot be guaranteed.

An embodiment of the present application provides a service transfer method. The service transfer method provided in the embodiment of the present application may be applied to a communication system 100 as shown in FIG. 1A , where the communication system 100 includes an access network device 120 , a terminal 130 and a terminal 140 . As shown in FIG. 1A, terminal 130 and terminal 140 may form a PIN. Wherein, the terminal 130 and the terminal 140 can communicate with the access network device 120 respectively.

Optionally, referring to FIG. 1B , the communication system 100 may further include a terminal 150 and a terminal 160 . In FIG. 1B, terminal 130, terminal 150, and terminal 160 may form a PIN. Among them, the terminal 130 and the terminal 150 can directly communicate with the access network device 120, but the terminal 160 cannot directly communicate with the access network device 120, and the terminal 160 can communicate with the access network device 120 through the terminal 150, and the terminal 150 is a terminal 160 management equipment.

[Corrected 13.06.2022 under Rule 91]
Optionally, as shown in FIG. 1A and FIG. 1B , the communication system 100 further includes a core network device 110 . Wherein, the core network device 110 can perceive all devices in the PIN, and is used for registering the PIN device.

It should be understood that the communication system 100 may further include more terminals, and the terminals in FIG. 1A and FIG. 1B are exemplary, and the number of terminals is not limited.

A terminal, also called user equipment (UE), mobile station (MS), mobile terminal (MT), etc., is a device that provides voice and/or data connectivity to users . For example, a terminal may include a handheld device with a wireless connection function, a vehicle-mounted device, and the like. The terminal can be: mobile phone, tablet computer, notebook computer, handheld computer, mobile internet device (mobile internet device, MID), wearable device, virtual reality (virtual reality, VR) device, augmented reality (augmented reality, AR) equipment, wireless terminals in industrial control, wireless terminals in self-driving, wireless terminals in remote medical surgery, wireless terminals in smart grid , wireless terminals in transportation safety, wireless terminals in smart city, or wireless terminals in smart home, smart home appliances, hot air balloons, satellites or drones, etc. limit.

An access network device, which may also be called a network device or an access network device (access network, AN), provides wireless access services to the terminal. The access network device is a device in the communication system that connects the terminal device to a wireless network. The access network device is a node in the radio access network, and may also be called a base station, and may also be called a radio access network (radio access network, RAN) node (or device). At present, some examples of access network equipment are: gNB, transmission reception point (transmission reception point, TRP), transmission point (transmission point, TP), evolved node B (evolved Node B, eNB), radio network controller ( radio network controller (RNC), Node B (Node B, NB), base station controller (base station controller, BSC), base transceiver station (base transceiver station, BTS), home base station (for example, home evolved NodeB, or home Node B, HNB), base band unit (base band unit, BBU), or wireless fidelity (wireless fidelity, Wifi) access point (access point, AP), satellite, hot air balloon or drone, etc.

In the following, application scenarios of the embodiments of the present application will be introduced with reference to FIG. 2A and FIG. 2B .

Referring to FIG. 2A , the user's business can be transferred between the terminal 130 and the terminal 140 . Wherein, the terminal 130 and the terminal 140 respectively communicate with the access network device 120 through the Uu interface.

Referring to FIG. 2B , the user's business can be transferred between the terminal 130 and the terminal 160 . Wherein, the terminal 130 can communicate with the access network device 120 through the Uu interface. However, the terminal 160 does not have the capability of communicating with the access network device 120 based on the Uu interface, but accesses the network through the terminal 150 . The terminal 150 can communicate with the access network device 110 through the Uu interface. The communication interface between the terminal 150 and the terminal 160 may be WiFi, Bluetooth or other non-3rd generation partnership project ( ^3rd generation partnership project, 3GPP) access technology, and may also be a PC5 interface. In Fig. 2B, the PC5 interface is taken as an example.

Referring to FIG. 3 , it is an exemplary flow chart of the service transfer method provided in the embodiment of the present application, which may include the following operations.

S301: The first device sends a service transfer request to a core network device, and the corresponding core network device receives the service transfer request.

Wherein, the service transfer request may be used to request to switch the service to be transferred from the source device to the target device. The service transfer request may include the information of the second device. It should be noted that the device information involved in this embodiment of the present application may be the identifier of the second device, the device identifier for managing the second device, the PIN identifier of the second device, and the PIN device identifier (PIN device ID) of the second device at least one of the Wherein, the identifier of the second device may be an identifier uniquely identified by a core network device. For example, it may be S-TMSI, GUTI, SUPI, SUCI or other identifiers, which will not be repeated below. The PIN ID (PIN ID) is used to identify a PIN. The PIN ID can uniquely identify a PIN globally, or uniquely identify a PIN within a public land mobile network (PLMN). The PIN device identifier can identify a device, uniquely identify a PIN device globally, or uniquely identify a PIN device within a PLMN, or uniquely identify a PIN device within a PIN. Wherein, the PIN identifier and the PIN device identifier may be allocated by the core network equipment. For example, it can be assigned by the core network device when the device registers to the network, and the detailed description will be shown in the registration process later.

S302: The core network device sends a first message to the first device, and the corresponding first device receives the first message.

Wherein, the first message may be used to inform the first message that the service transfer has been completed. The first message may include service information to be transferred. For example, it may be at least one of PDU session information and QoS flow information of the service to be transferred. Optionally, the first message may be one of a service release message and a service setup message.

In the embodiment of the present application, the data transmission between the device and the core network device can be realized through the access network device. For example, the device may send data to the access network device, and the access network device sends the data to the core network device.

Based on the above solution, the first device can initiate the service transfer process to the core network device, enabling the user's service to be transferred between different devices, which is universal, and because the service transfer is realized through the core network device, the network can perceive the service Transfer, which can reduce the possibility of business interruption.

It should be noted that due to the difference between the source device and the target device and the roles of the above-mentioned first device and the second device, the service transfer method shown in FIG. 3 of the embodiment of the present application has different situations. In the following, detailed descriptions will be given for various situations.

Case 1. The first device is a source device, and the second device is a target device.

Referring to FIG. 4 , it is an exemplary flow chart of the service transfer method in the embodiment of the present application, which may include the following operations.

S401: The source device sends a service transfer request to the core network device.

Wherein, the service transfer request may include the information of the target device. Optionally, the service transfer request may also include service information to be transferred, that is, the service information requested to be transferred to the target device, and reference may be made to the foregoing related description.

S402: The core network device sends a service release message to the source device.

Optionally, the service release message may include service information to be transferred.

The core network device can perform non-access stratum (non-access stratum, NAS) layer signaling interaction with the target device to establish a service. For example, the core network device may perform a service request (service request) process with the target device. Optionally, the following operation S403 may be performed.

S403: The core network device sends a service establishment request to the target device.

Wherein, the service establishment request may include the service information to be transferred. Optionally, the service establishment request may also include information of the source device.

It should be noted that S403 may be performed after S402, or S403 may also be performed before S402, or S403 and S402 may be performed simultaneously.

Optionally, after the core network device receives the service transfer request in S401, the core network device may confirm whether the source device is allowed to trigger service transfer, or may confirm whether the source device is allowed to transfer the service to the target device. If confirmed, execute S402 and S403; if confirmed not, execute S402 and S403. Optionally, if the confirmation is not possible, the core network device may feed back a rejection message to the source device.

For example, the core network device can confirm whether the source device is allowed to trigger service transfer according to the information of the source device. Alternatively, the core network device can confirm whether the source device is allowed to transfer services to the target device according to the PIN IDs of the source device and the target device. For example, are the PIN IDs of the source and destination devices the same. It should be understood that the foregoing confirmation conditions are exemplary only, and do not constitute a limitation on the confirmation conditions of the core network device in this embodiment of the present application.

In case 2, the first device is the target device, and the second device is the source device.

Referring to FIG. 5 , it is an exemplary flow chart of the service transfer method in the embodiment of the present application, which may include the following operations.

S501: The source device sends service information to be transferred to the target device.

Wherein, for the service information to be transferred, reference may be made to the foregoing related descriptions, which will not be repeated here.

Optionally, the source device may also send its own information, that is, the information of the source device, to the target device. For reference, reference may be made to the aforementioned related descriptions, which will not be repeated here.

Optionally, after the target device receives the service information to be transferred in S501, the target device can confirm whether the source device can transfer the service to the target device. For example, the destination device can confirm whether the source device belongs to the same PIN network as itself. If the target device confirms that the source device can transfer the service to the target device, the following S502 may be performed. If the target device confirms that it is not possible, the following S502 may not be executed. Optionally, if the target device confirms that it is not possible, a rejection message may be fed back to the source device. It should be understood that the target device may also confirm whether the source device can transfer the service to the target device based on other conditions, which is not specifically limited in this application. For example, the target device can also confirm whether the source device can transfer services to the target device according to its own load. For example, when its own load is greater than or equal to a certain threshold, it can be considered that the source device cannot transfer services to the target device.

S502: The target device sends a service transfer request to the core network device.

Wherein, the service transfer request may include the information of the source device. Optionally, the service transfer request may also include service information to be transferred.

The core network device can exchange NAS layer signaling with the target device to establish services. For example, the core network device may perform a service request (service request) process with the target device. Optionally, the following operation S503 may be performed.

S503: The core network device sends a service establishment request to the target device.

S504: The core network device sends a service release message to the source device.

It should be noted that S504 may be performed after S503, or S504 may be performed before S503, or S504 and S503 may be performed simultaneously.

Optionally, after the core network device receives the service transfer request in S502, the core network device can confirm whether the source device is allowed to trigger the service transfer, or can confirm whether the source device is allowed to transfer the service to the target device, as shown in the preceding figure Related descriptions in the embodiment shown in 4.

Optionally, if the source device and the target device have not established a connection, the source device and the target device may also perform the following operation S500 before the foregoing S501.

S500: Establish a connection between the source device and the target device.

It should be noted that the purpose of establishing a connection between the source device and the target device is that the source device and the target device can transmit data safely. Exemplarily, the source device may send a connection request to the target device. Optionally, the connection request may include source device information. For example, at least one of source device identification, PIN ID, and PIN device identification may be included. After receiving the connection request, the target device can reply a response message to the source device. Optionally, if the information of the source device in the connection request is information that the target device is interested in, a response message may be returned to the source device. For example, if the PIN ID is the same as the PIN ID of the target device, or the PIN device ID or the source device ID is the device ID in the PIN where it is located, then it can be considered that the information of the source device is the information that the target device is interested in. Optionally, the source device and the target device can also negotiate an encryption algorithm and a secret key during data transmission.

In this embodiment of the present application, the device identifier may be the only identifier capable of identifying a device in the core network, for example, it may be G-S-TMSI, GUTI, SUPI, SUCI or other identifiers, which will not be described in detail below.

Through the above cases 1 and 2, the service to be transferred can be transferred from the source device to the target device. The target device can transmit service data with the core network device after establishing a service with the core network device, so as to execute the service to be transferred.

In a possible implementation, when the first device and the second device form a PIN, they can perform a registration process, the purpose of which is to complete the registration of devices in the PIN, so as to ensure that service transfer occurs between registered devices without It will be transferred to other personal devices to ensure the security of user business data. It should be understood that the purpose of the registration process is to establish a PIN and complete registration and authentication with the core network device. The registration process only needs to receive at least one of the PIN ID and PIN device ID assigned by the core network device. The following describes the registration process. It should be noted that the following registration process is only exemplary, and does not constitute a limitation to the registration process of the PIN device in the embodiment of the present application.

Referring to FIG. 6 , the registration process of the PIN device in the embodiment of the present application is described, which may include the following operations.

S601: The first device broadcasts a PIN creation message.

Optionally, the PIN creation message may include at least one of service identifier and device information.

After receiving the PIN creation message, the second device may determine to establish a connection with the second device based on the PIN creation message. For example, the second device may confirm whether the service identifier is an identifier that it is interested in, or whether the information of the device is information that it is interested in. If the second device is interested, it can communicate with the first device. Optionally, the second device may perform the following operation S602.

S602: The second device establishes a connection with the first device.

Optionally, when the second device establishes a connection with the first device, it may be considered that the second device can communicate with the first device. The second device may send an acknowledgment message to the first device in response to the PIN creation message.

S603: The first device sends its own device identifier to the second device.

S604: The second device sends its own device identifier to the first device.

It should be noted that, in the foregoing operations S603 and S604, any one operation or all operations may be executed.

S605: The first device sends the device identifier of the second device to the core network device.

S606: The second device sends the device identifier of the first device to the core network.

S607: The core network device sends a PIN registration confirmation message to the first device.

S608: The core network device sends a PIN registration confirmation message to the second device.

Wherein, the PIN registration confirmation message is used to respond to the report of the first device or the second device, and can be understood as indicating to the first device or the second device that the core network device has completed registration. Optionally, the PIN registration confirmation message may also include at least one of the PIN ID and the PIN device identifier.

It should be noted that, if the operation S603 is performed but S604 is not performed, it is sufficient to perform S606 in S605 and S606, and it is sufficient to perform S608 in S607 and S608. If the operation S604 is performed without performing S603, it only needs to perform S605 in S605 and S606, and it only needs to perform S607 in S607 and S608. If S603 and S604 are executed, then S605 and S606 and S607 and S608 are executed.

Based on the above solution, the first device and the second device can complete PIN registration, and the user's business can be transferred between the first device and the second device. Optionally, the service transfer process may be triggered by an application server (application server, AS), or may also be triggered by an upper layer of the first device or the second device. Wherein, the upper layer may include an application layer and an operating system layer. For example, the operating system layer can obtain user input instructions, thereby triggering service transfer. AS triggering may include event triggering, where an event may be indicated to the AS by an access network device or a core network device. For example, the AS may trigger service transfer when the transmission quality of service data is less than or equal to a specified threshold.

Optionally, after the AS triggers or the upper layer triggers the service transfer process, a PIN device discovery operation may be performed. For example, the first device may send a discovery signal, and the second device may acquire the information of the first device from the discovery signal, and determine that the first device may perform service transfer. Alternatively, the first device may send a discovery request message, and the second device may respond to the discovery request message, so as to enable the second device to discover the first device and determine that the first device can perform service transfer. The information of the first device obtained during the PIN device discovery process may be as described above, and will not be repeated here.

It should be noted that the above PIN device discovery operation may not be performed, but the upper layer indicates the associated device. For example, instructions may be entered by a user to associate a source device with a target device. The associated device can be understood as the business of the first device needs to be transferred to the target device.

It should be clarified that in the service transfer request sent by the first device to the core network device, the information of the second device may be obtained in S501, or may also be obtained through the above registration process or PIN device discovery process. Applications are not specifically limited.

Based on the above solution, the target device or the source device can initiate a service transfer process to the core network device, so that the user's service can be transferred between different devices.

In the above case 1 and case 2, the source device and the target device can communicate with the network, so both the source device and the target device can initiate a service transfer process to the core network device. If either of the source device and the target device cannot communicate with the network, the management device can communicate with the network.

It should be noted that if any one of the source device and the target device cannot communicate with the network device, the management device may serve as an intermediate device to support any one of the source device and the target device to communicate with the network. Among them, the intermediate device can work between the device and the network, and is responsible for receiving data from the network and forwarding it to the device. The forwarded data may be data received from the network, or may be data obtained by performing some processing on the received data. Exemplarily, the intermediate device may be a relay device, for example, may perform relay based on layer 2 (L2), or may perform relay based on layer 3 (L3). The intermediate devices of the source device and the target device may be the same device or different devices.

Assuming that the source device cannot communicate with the network device, the source device in case 1 and case 2 is equivalent to the management device of the source device at this time. That is to say, the management device of the source device may send a service transfer request to the core network device. Optionally, the management device of the source device may receive a request sent by the source device, requesting to transfer the service to be transferred to the target device.

Assuming that the target device cannot communicate with the network device, the target device in case 1 and case 2 is equivalent to the management device of the target device at this time. That is to say, the management device of the target device may send a service transfer request to the core network device. Optionally, the management device of the target device may receive a request sent by the source device, the management device of the source device, or the target device, requesting that the service to be transferred be transferred to the target device.

In the following, cases 3 and 4 show cases where the target device cannot communicate with the network. It should be understood that the cases 3 and 4 are only exemplary descriptions of the service transfer method when the target device cannot communicate with the network, and do not constitute a limitation to the service transfer method provided in this application.

In case 3, the first device is a source device, the second device is a target device, and the third device is a management device of the target device.

Referring to FIG. 7 , it is an exemplary flow chart of the service transfer method in the embodiment of the present application, which may include the following operations.

S701: The source device sends a service transfer request to the core network device.

Wherein, the service transfer request may include service information to be transferred. Optionally, the service transfer request may also include information of the target device and information of the third device.

S702: The core network device sends a service release message to the source device.

The core network device can exchange NAS layer signaling with the third device to establish a service. For example, the core network device may perform a service request (service request) process with the target device. Optionally, the following operation S703 may be performed.

S703: The core network device sends a service establishment request to the third device.

Wherein, the service establishment request may include service information to be transferred and target device information. The information of the target device can be used by the third device to identify the target device, so that the service to be transferred is transferred to the target device in the PIN.

It should be noted that S703 may be executed after S702, or S703 may be executed before S702, or S703 and S702 may be executed simultaneously.

Optionally, after the core network device receives the service transfer request in S701, the core network device can confirm whether the source device is allowed to trigger service transfer, or can confirm whether the source device is allowed to transfer the service to the target device, as shown in Figure 4 Relevant descriptions in the illustrated embodiment will not be repeated here.

Through the above operations, the service to be transferred can be transferred from the source device to the target device. Since the target device cannot communicate with the access network device, the target device can transmit service data with the access network device through the third device, so as to execute the service to be transferred.

Situation 4. The first device is the management device of the target device, the second device is the source device, and the third device is the target device.

Referring to FIG. 8 , it is an exemplary flow chart of the service transfer method in the embodiment of the present application, which may include the following operations. Fig. 8 shows a method in which the source device triggers the first device to execute the service transfer process and a target device triggers the first device to execute the service transfer process. In the following, they will be introduced respectively.

Wherein, the method for triggering the first device to execute the service transfer process by the source device may include the following operations.

S801: The source device sends service information to be transferred to the first device.

Optionally, the source device may also send the information of the target device to the first device, so that the first device can know the target device expected by the source device.

S802: The first device sends a service transfer request to the core network device.

Wherein, the service transfer request may include the information of the target device. Optionally, the service transfer request may also include service information to be transferred.

S803: The core network device sends a service release message to the source device.

Wherein, the service release message may include service information to be transferred.

The core network device can exchange NAS layer signaling with the target device to establish services. Since the target device cannot communicate with the core network device, the core network device can perform a service request (service request) process with the management device of the target device, that is, the first device. Optionally, the following operation S804 may be performed.

S804: The core network device sends a service establishment request to the first device.

Wherein, the service establishment request may include service information to be transferred. If the source device sends the information of the target device to the first device, the first device may determine that the service establishment request is a request to transfer the service to be transferred to the target device. If the source device does not send the information of the target device to the first device, the first device may determine a device capable of carrying the service to be transferred in the PIN. Optionally, the first device may transfer the service to be transferred to a device that can carry the found device. Or, the first device may send the information of the found device to the source device, and the source device confirms which device to transfer the tape transfer service to. Optionally, the source device may send a confirmation message to the first device, and the confirmation message may carry device information, and the first device may transfer the service to be transferred to the desired device of the source device according to the confirmation message.

It should be noted that S804 may be performed after S803, or S804 may be performed before S803, or S804 and S803 may be performed simultaneously.

Optionally, after the core network device receives the service transfer request in S802, the core network device can confirm whether the source device is allowed to trigger service transfer, or can confirm whether the source device is allowed to transfer the service to the target device, as shown in Figure 4 Relevant descriptions in the illustrated embodiment will not be repeated here.

The method for triggering the first device to execute the service transfer process by the target device may include the following operations.

S805: The source device sends a first request to the target device.

The first request may be used to request to transfer the service to be transferred to the target device. Optionally, the first request may include at least one of information about the service to be transferred and information about the source device.

Optionally, after receiving the first request in S805, the target device may confirm whether the source device can transfer the service to the target device. For details, please refer to the relevant description in the embodiment shown in FIG. 5 , which will not be repeated here.

S806: The target device sends a second request to the first device.

Wherein, since the target device does not have the ability to communicate with the network, it means that the target device cannot generate NAS messages. Therefore, the target device notifies the first device of the received first request or the content of the first request. That is, the second request may be the same request as the first request or the content of the second request may be the same as that of the first request.

S807: The first device sends a service transfer request to the core network device.

Wherein, the first device may serve as an intermediate device between the target device and the core network device, and may generate a NAS message according to the second request and send it to the core network device.

S808: The core network device sends a service release request to the source device.

The core network device can exchange NAS layer signaling with the target device to establish services. Since the target device cannot communicate with the core network device, the core network device can perform a service request (service request) process with the management device of the target device, that is, the first device. Optionally, the following operation S809 may be performed.

S809: The core network device sends a service establishment request to the first device.

It should be understood that since the target device does not have the capability of communicating with the network, the service may be established between the core network device and the first device. The first device receives the service data and sends the service data to the target device, so as to transfer the service to the target device. Optionally, the first device may send a confirmation message to the target device after S809, where the confirmation message is used to respond to the second request in S802.

It should be noted that S809 may be performed after S808, or S809 may be performed before S808, or S809 and S808 may be performed simultaneously.

Optionally, after the core network device receives the service transfer request in S807, the core network device can confirm whether the source device is allowed to trigger service transfer, or can confirm whether the source device is allowed to transfer the service to the target device, as shown in Figure 4 Relevant descriptions in the illustrated embodiment will not be repeated here.

Through the foregoing cases 3 and 4, the source device can transfer the service to be transferred to the target device. Since the target device cannot communicate with the access network device, the target device can transmit service data with the access network device through the third device, so as to execute the service to be transferred.

In a possible implementation manner, since the third device cannot directly communicate with the network, the registration process of the third device is different from the registration processes of the aforementioned first device and the second device. The third device can register with the core network device through the second device, and obtain at least one of the PIN ID and the PIN device allocated by the core network device. The following describes the registration process. It should be noted that the following registration process is only exemplary, and does not constitute a limitation to the registration process of the third device in the embodiment of the present application.

Referring to FIG. 9 , it is a schematic diagram of a registration process of a third device, which may include the following operations.

S901: Device discovery.

In S901, the second device and the third device may discover each other, and since the third device cannot communicate with the network, the third device may communicate with the second device and the network. Optionally, the second device and the third device may be associated, the third device may store the information of the second device, and the second device may also store the information of the third device.

S902: The second device requests registration for the third device.

The second device may send the device identifier of the third device to the core network to help the third device complete registration.

S903: The core network device sends a PIN registration confirmation message to the second device.

Wherein, the PIN registration confirmation message may include at least one of the PIN ID of the third device and the PIN device identifier.

S904: The second device sends the PIN ID and the PIN device identification of the third device to the third device.

Optionally, the second device may also send the PIN device identifier of the second device to the third device.

It should be noted that the above S901-S904 is a registration process for the third device that accesses the network through the second device, and its purpose is to complete the registration of the third device. Optionally, the third device can initiate registration with the core network device through the second device itself, and at this time, the interaction process between the third device and the core network device can be the same as that of the first device or the second device shown in FIG. 6 . At this time, the second device serves as an intermediate device between the third device and the network, helping the third device communicate with the network.

Next, FIG. 10 shows a situation where the source device cannot communicate with the network. The source device can communicate with the network through the management device to realize the service transfer process. Referring to FIG. 10 , description is made by taking the management device in which the first device is the source device as an example. It should be understood that FIG. 10 is only an exemplary description of the service transfer method when the source device cannot communicate with the network, and does not constitute a limitation to the service transfer method provided in this application.

Wherein, the method for the target device to initiate the service transfer process may include the following operations.

S1001: The target device sends a service transfer request to the core network device.

Wherein, the service transfer request may include service information to be transferred. Optionally, the service transfer request may further include at least one of information about the source device and information about the first device.

S1002: The core network device sends a service release message to the first device.

Wherein, the service release message may include the service information to be transferred. Optionally, the information of the source device is also included in the service release message.

Since the core network device can perceive all devices in the PIN, if the service transfer request contains the information of the source device, the core network device can determine the information of the first device that manages the source device according to the information of the source device, and send the request to the second A device sends a service release message. Optionally, the information of the source device may be included in the service release message. The information of the first device may determine the source device executing the relevant service according to the information of the source device or the service information to be transferred, and forward the service release message to the source device.

If the service transfer request includes the information of the first device, the core network device may send a service release message to the first device. It can be seen from the embodiment shown in FIG. 8 that the service is established between the management device and the core network device, so the first device can release the service according to the service release message. The first device may also release services with the source device.

S1003: The core network device sends a service establishment request to the target device.

It should be noted that S1003 may be performed before S1002, or S1003 may be performed after S1002, or S1003 and S1002 may be performed simultaneously.

Optionally, after the core network device receives the service transfer request in S1001, the core network device can confirm whether the source device is allowed to trigger service transfer, or can confirm whether the source device is allowed to transfer the service to the target device, as shown in Figure 4 Relevant descriptions in the illustrated embodiment will not be repeated here.

Optionally, the following S1000 may also be executed before the above S1001.

S1000: The source device sends a first request to the target device.

The first request may be used to request to transfer the service to be transferred to the target device. The first request may include service information to be transferred. Optionally, the first request may further include at least one of information about the source device and information about the first device.

Optionally, after receiving the first request in S1000, the target device may confirm whether the source device can transfer the service to the target device. For details, please refer to the relevant description in the embodiment shown in FIG. 5 , which will not be repeated here.

Based on the above S1000, the source device may trigger the target device to initiate a service transfer process.

The method for the source device to trigger the first device to initiate a service transfer process may include the following operations.

S1004: The source device sends a third request to the first device.

Wherein, the third request may be used to request to transfer the service to be transferred to the target device. The third request may include the information of the target device and the service information to be transferred.

S1005: The first device sends a service transfer request to the core network device.

Since the source device does not have the capability of communicating with the network, the communication with the network may be implemented through the first device, the intermediate device. The first device may generate a service transfer request according to the fourth request and send it to the core network device.

S1006: The core network device may send a service release message to the first device.

Wherein, the service release message may include the service information to be transferred. Optionally, the information of the source device may also be included in the service release message. The first device may release the service according to the service release message, and release the service with the source device.

[Corrected 13.06.2022 under Rule 91]
The core network device can exchange NAS layer signaling with the target device to establish services. For example, the core network device may perform a service request (service request) process with the target device. Optionally, the following operation S1007 may be performed.

S1007: The core network device sends a service establishment request to the target device.

It should be noted that S1007 may be performed after S1006, or S1007 may be performed before S1006, or S1007 and S1006 may be performed simultaneously.

Optionally, after the core network device receives the service transfer request in S1005, the core network device can confirm whether the source device is allowed to trigger service transfer, or can confirm whether the source device is allowed to transfer the service to the target device, as shown in Figure 4 Relevant descriptions in the illustrated embodiment will not be repeated here.

In a possible implementation manner, for the method for the source device to perform PIN registration, refer to the related description of the aforementioned third device performing PIN registration, which will not be repeated here. Optionally, the method for triggering the service forwarding process may be described above, and will not be repeated here. Optionally, the source device and the target device may also perform a PIN device discovery operation or an upper layer may instruct an associated device, and reference may be made to the foregoing related description, which will not be repeated here.

In the following, FIG. 11 shows the situation that neither the source device nor the target device can communicate with the network device. The source device can communicate with the network through the management device of the source device, and the target device can communicate with the network through the management device of the target device to realize the service transfer process. Referring to FIG. 11 , description is made by taking the first device as the management device of the source device and the second device as the management device of the target device as an example. It should be understood that FIG. 11 is only an exemplary description of the service transfer method when the source device and the target device cannot communicate with the network, and does not constitute a limitation to the service transfer method provided in this application.

Wherein, the method for the source device to trigger the first device to execute the service transfer process may include the following operations.

S1101: The source device sends a third request to the first device.

The third request may be used to request that traffic be transferred to the target device. Wherein, the third request may include the information of the target device and the service information to be transferred. Optionally, the third request may also include information about the source device.

S1102: The first device sends a service transfer request to the core network device.

The first device may serve as an intermediate device between the core network device and the source device.

S1103: The core network device sends a service release request to the first device.

The service release request may include service information to be transferred. Optionally, the service release message may also include information of the source device. For the related description of releasing the service by the first device, refer to the related description in the embodiment shown in FIG. 10 , which will not be repeated here.

The core network device can exchange NAS layer signaling with the target device to establish services. Since the target device does not have the ability to communicate with the network, the core network device can execute a service request (service request) process with the management device of the target device, that is, the second device. Optionally, the following operation S1105 may be performed.

S1104: The core network device sends a service establishment request to the second device.

Optionally, the service establishment request may include service information to be transferred. The service transfer request may also include the information of the source device.

Wherein, the core network device may determine the information of the second device according to the information of the target device in the service transfer request, and send the service establishment request to the second device. The service establishment request may include the information of the target device, so that the second device can determine the target device in the PIN. For the description of establishing a service by the second device, reference may be made to the relevant description in the embodiment shown in FIG. 8 , and details are not repeated here.

It should be noted that S1104 may be performed after S1103, or S1104 may also be performed before S1103, or S1104 and S1103 may be performed simultaneously.

[Corrected 13.06.2022 under Rule 91]
Optionally, after the core network device receives the service transfer request in S1102, the core network device can confirm whether the source device is allowed to trigger service transfer, or can confirm whether the source device is allowed to transfer the service to the target device, as shown in Figure 4. Relevant descriptions in the illustrated embodiment are not repeated here.

The method for the source device to trigger the target device to execute the service transfer process may include the following operations.

S1105: The source device sends a first request to the target device.

Wherein, the first request may be used to request to transfer the service to be transferred to the target device. Optionally, the first request may include at least one of information about the service to be transferred and information about the source device.

Optionally, after receiving the first request in S1105, the target device may confirm whether the source device can transfer the service to the target device. For details, please refer to the relevant description in the embodiment shown in FIG. 5 , which will not be repeated here.

S1106: The target device sends a second request to the second device.

The second request may include service information to be transferred. Optionally, the second request may include at least one of information about the source device and information about the first device.

S1107: The second device sends a service transfer request to the core network device.

Wherein, the second device supports communication between the target device and the core network device as an intermediate device.

The core network device can exchange NAS layer signaling with the target device to establish services. For example, the core network device may execute a service request (service request) process with the management device of the target device, that is, the second device. Optionally, the following operation S1108 may be performed.

S1108: The core network device sends a service establishment request to the second device.

Wherein, the service establishment request may include the service information to be transferred. Optionally, the service establishment request may also include information of the source device. For the description of the establishment of the service by the second device, refer to the relevant description in the embodiment shown in FIG. 8 , and details are not repeated here.

S1109: The core network device sends a service release message to the first device.

Wherein, the service release message may include the service information to be transferred. Optionally, the service release message may also include information of the source device. For the related description of releasing the service by the first device, refer to the related description in the embodiment shown in FIG. 10 , which will not be repeated here.

It should be noted that S1109 may be performed after S1108, or S1109 may also be performed before S1108, or S1109 and S1108 may be performed simultaneously.

Optionally, after the core network device receives the service transfer request in S1107, the core network device can confirm whether the source device is allowed to trigger service transfer, or can confirm whether the source device is allowed to transfer the service to the target device, as shown in Figure 4. Relevant descriptions in the illustrated embodiment are not repeated here.

In a possible implementation manner, for a method for performing PIN registration by the source device and the target device, reference may be made to the relevant description of the aforementioned PIN registration performed by the third device, which will not be repeated here. Optionally, the method for triggering the service transfer process may be described above, and will not be repeated here. Optionally, the source device and the target device may also perform a PIN device discovery operation or an upper layer may instruct an associated device, and reference may be made to the foregoing related description, which will not be repeated here.

It should be noted that the above embodiments shown in FIG. 4 to FIG. 11 can be combined arbitrarily to implement the service transfer method provided in this application. Those skilled in the art can select part or all of the operations to form a complete embodiment.

In another possible implementation manner, the source device may also send the cached data of the service to be transferred to the target device. For example, the source device can send cached data to the target device, or the source device can send cached data to the management device of the target device, or the source device can send cached data to the target device through the management device of the source device, or the source device can send cached data to the target device through the source device The management device of the target device sends the cached data to the management device of the target device.

For example, for the video download service, the source device needs to transfer the previously cached video to the target device, so as to ensure that the video does not freeze. Optionally, when data is forwarded, each packet needs to carry at least one of the corresponding PDU session ID and QoS flow ID. Optionally, uplink data and downlink data also need to be distinguished, for example, by carrying an indication in the packet, or by establishing different bearers.

In a possible implementation, before the service to be transferred is transferred between the two devices, the data connection is established between the source device and the core network, and after the service to be transferred is transferred between the two devices, the data connection is established between the two devices. Between the target device and the core network. As an intermediate node, the access network device does not perceive this process. Therefore, data tunnels are established for the source device and the target device between the access network device and the core network device. Referring to FIG. 12A , when a service is carried by UE1, the access network device may establish a data tunnel 1 for UE1. The data tunnel 1 may be a data tunnel between the core network device and UE1. Since the access network device is not aware of the service transfer process as an intermediate node, the access network device will establish a data tunnel 2 for UE2, and the data tunnel 2 may be a data tunnel between the core network device and UE2.

In an example, before and after the service to be transferred is transferred between the two devices, the data tunnel between the enabled core network and the access network device remains unchanged. Referring to FIG. 12B , when a service is carried by UE1, the access network device may establish a data tunnel 1 for UE1. When the service is transferred to UE2, the access network device may enable the data tunnel of UE2 to still use data tunnel 1.

In FIG. 12A and FIG. 12B , one PDU session is taken as an example to illustrate that the target device uses the data tunnel of the source device. For multiple PDU sessions, the target device can also use the data tunnel of the source device, which will not be repeated here.

Referring to FIG. 13 , it is an exemplary flow chart of the service transfer method in the embodiment of the present application, which may include the following operations.

Assuming that the service to be transferred is borne by the source device, the access network device may establish a source PDU session and a first GTP tunnel for the source device. Wherein, the first GTP tunnel corresponds to the source PDU session. Wherein, the process of the access network device establishing the source PDU session for the source device may include the core network device sending a PDU session establishment request to the access network device. The PDU session establishment request includes information of the first GTP tunnel allocated by the core network device for the source PDU session. The access network device sends a PDU session establishment response to the core network device, and the PDU session establishment response includes information about the first GTP tunnel allocated by the access network device for the source PDU session. Wherein, the information of the GTP tunnel may include the GTP tunnel endpoint identifier and the endpoint IP address. The aforementioned core network equipment may be an access mobile management function (AMF).

S1301: The core network device receives a service transfer request from the first device.

Wherein, for the service transfer request, reference may be made to the foregoing related descriptions, which will not be repeated here.

S1302: The core network device sends a first request message to the access network device, and the corresponding access network device receives the first request message.

Wherein, the first request message may instruct the access network device to establish a target PDU session for the target device. Optionally, the first request message may include target device information, target PDU session information, and indication information. Wherein, the indication information may be used to indicate that the target PDU session uses the source PDU session. The above information of the target PDU session may include at least one QoS flow information. Wherein, the QoS flow information may be the QoS flow information when the first device executes the service to be transferred.

Optionally, the indication information may be at least one of an identifier of the first device or information of the first GTP tunnel. Wherein, the identifier of the first device may be an identifier of an interface assigned to the first device by the core network device or the access network device.

In an example, the first request message may be an initial context setup request (initial context setup request) message or a PDU session resource setup request (PDU session resource setup request) message.

Based on the above solution, the access network device can perceive the association relationship between the first device and the target device, so as to reuse the source PDU session of the first device to the target device.

Optionally, perform the following operations.

S1303: The access network device sends a first response message to the core network device, and the corresponding core network device receives the first response message.

Wherein, the first response message may include the identifier of the target PDU session and the information of the first GTP tunnel. The first GTP tunnel may correspond to a target PDU session. Optionally, the first response message may be an initial context setup response (initial context setup response) message or a PDU session resource setup response (PDU session resource setup response) message.

S1304: The core network device sends a second request message to the access network device, and the corresponding access network device receives the second request message.

Wherein, the second request message is used to request the access network device to release the source PDU session. The second request message may include the identifier of the source PDU session. Optionally, the second request message may be a PDU session resource release request (PDU session resource release request) message or a UE context release request (UE context release request) message.

S1305: The access network sends a second response message to the core network device, and the corresponding core network device receives the second response message.

Wherein, the second response message may be used to inform the core network to release the released source PDU session. Optionally, the second response message may be a PDU session resource release response (PDU session resource release response) message or a UE context release response (UE context release response) message.

Based on the above scheme, the source PDU session of the source device can be released, but the GTP tunnel corresponding to the source PDU session will not be released, and the target PDU session associated with the target device can enable the access network device to reuse the GTP tunnel before and after service transfer, avoiding GTP Tunnels change frequently.

Based on the same idea, referring to FIG. 14 , an embodiment of the present application provides a communication device 1400 , where the device 1400 includes a processing module 1401 and a transceiver module 1402 . The apparatus 1400 may be the first device, or may be an apparatus applied to the first device, capable of supporting the first device to execute the above method, or, the apparatus 1400 may be a core network device, or may be applied to a core network device, capable of A device supporting core network equipment to execute the above method.

Wherein, the transceiver module may also be referred to as a transceiver module, a transceiver, a transceiver, a transceiver device, and the like. A processing module may also be called a processor, a processing board, a processing module, a processing device, and the like. Optionally, the device used to implement the receiving function in the transceiver module can be regarded as a receiving unit. It should be understood that the transceiver module is used to perform the sending and receiving operations on the first device side or the core network device side in the above method embodiments, The device used to implement the sending function in the transceiver module is regarded as a sending unit, that is, the transceiver module includes a receiving unit and a sending unit. When the apparatus 1400 is applied to the first device, the receiving unit included in the transceiver module 1402 is configured to perform a receiving operation on the first device side, such as receiving a first message, specifically receiving first information from a core network device; The sending unit included in the transceiver module 1402 is configured to perform a sending operation on the first device side, such as sending a service transfer request, specifically, sending a service transfer request to a core network device. When the apparatus 1400 is applied to a core network device, the sending unit included in the transceiver module 1402 is configured to perform a sending operation on the core network device side, such as sending the first message, specifically, sending the first message to the first device. The receiving unit included in the transceiver module 1402 is configured to perform a sending operation on the core network device side, such as receiving a service transfer request, specifically, receiving a service transfer request from the first device. In addition, it should be noted that if the device is implemented by a chip/chip circuit, the transceiver module can be an input and output circuit and/or a communication interface, and performs input operations (corresponding to the aforementioned receiving operations) and output operations (corresponding to the aforementioned sending operations); the processing module An integrated processor or microprocessor or integrated circuit.

The implementation manner in which the apparatus 1400 is applied to the first device or the core network device will be described in detail below.

Exemplarily, the apparatus 1400 is applied to the first device, and the operations performed by each module thereof are described in detail.

The processing module 1401 is configured to generate a service transfer request. The service transfer request includes the information of the second device, and the service transfer request is used to request to transfer the service to be transferred from the source device to the target device. The transceiver module 1402 is configured to send a service transfer request to the core network equipment. The transceiver module 1402 is further configured to receive a first message from a core network device; the first message includes service information to be transferred. For the relevant descriptions of the source device, the target device, the first device, the second device, the service transfer request and the first message, please refer to the relevant descriptions in the method embodiments shown in Figure 3-Figure 11, and will not be repeated here. .

Exemplarily, the application of the apparatus 1400 to a core network device and the operations performed by each module thereof will be described in detail.

The transceiver module 1402 is configured to receive a service transfer request from the first device; the service transfer request includes information of the second device, and the service transfer request is used to request to transfer the service to be transferred from the source device to the target device. A processing module 1401, configured to generate a first message. The transceiver module 1402 is further configured to send a first message to the first device; the first message includes service information to be transferred. For the relevant descriptions of the source device, the target device, the first device, the second device, the service transfer request and the first message, please refer to the relevant descriptions in the method embodiments shown in Figure 3-Figure 11, and will not be repeated here. .

Based on the same idea, referring to FIG. 15 , an embodiment of the present application provides a communication device 1500 , where the device 1500 includes a processing module 1501 and a transceiver module 1502 . The device 1500 may be an access network device, or it may be a device applied to an access network device that can support the access network device to perform the above method, or the device 1500 may be a core network device, or it may be a device applied to a core network The device is an apparatus capable of supporting the core network device to execute the foregoing method.

Wherein, the transceiver module may also be referred to as a transceiver module, a transceiver, a transceiver, a transceiver device, and the like. A processing module may also be called a processor, a processing board, a processing module, a processing device, and the like. Optionally, the device used to implement the receiving function in the transceiver module can be regarded as a receiving unit. It should be understood that the transceiver module is used to perform the sending and receiving operations on the core network device side and the access network device side in the above method embodiments , the device used to implement the sending function in the transceiver module is regarded as a sending unit, that is, the transceiver module includes a receiving unit and a sending unit. When the apparatus 1500 is applied to a core network device, the receiving unit included in the transceiver module 1502 is used to perform a receiving operation on the core network device side, such as receiving a service transfer request, specifically receiving a service transfer request from a first device; The sending unit included in the transceiver module 1502 is configured to perform a sending operation on the core network device side, such as sending a first request message, specifically, sending the first request message to an access network device. When the apparatus 1500 is applied to an access network device, the sending unit included in the transceiver module 1502 is used to perform a sending operation on the access network device side, such as sending a first response message, specifically, sending a first response to a core network device information. The receiving unit included in the transceiver module 1502 is configured to perform a sending operation on the access network device side, such as receiving a first request message, specifically, receiving a first request message from a core network device. In addition, it should be noted that if the device is realized by a chip/chip circuit, the transceiver module can be an input and output circuit and/or a communication interface, and performs an input operation (corresponding to the aforementioned receiving operation) and an output operation (corresponding to the aforementioned sending operation); the processing module An integrated processor or microprocessor or integrated circuit.

The implementation of applying the apparatus 1500 to core network equipment or access network equipment will be described in detail below.

Exemplarily, the application of the apparatus 1500 to a core network device, and the operations performed by each module thereof will be described in detail.

The transceiver module 1502 is configured to receive a service transfer request from the first device; the service transfer request is used to request to transfer the service to be transferred to the target device. The processing module 1501 is configured to generate a first request message. The first request message is used to instruct the access network device to establish a target PDU session for the target device. The transceiver module 1502 is further configured to send the first request message to the access network device. Wherein, the service transfer request, the first request message, the target PDU session, etc. can refer to the relevant descriptions in the method embodiments shown in FIGS. 3-13 , and will not be repeated here.

Exemplarily, the application of the apparatus 1500 to an access network device, and the operations performed by each module thereof will be described in detail.

The transceiver module 1502 is configured to receive a first request message from a core network device; the first request message is used to instruct the access network device to establish a target PDU session for the target device. Wherein, the first request message includes indication information; the indication information is used to indicate that the target PDU session of the target device uses the source PDU session of the first device.

Optionally, the processing module 1501 is configured to generate a first response message. The first response message includes the identifier of the target PDU session and information of the first GTP tunnel; the first GTP tunnel is the GTP tunnel of the source PDU session. The transceiver module 1502 is further configured to send the first response message to the core network device. For the first request message, indication information, first response message, source PDU session, and target PDU session, reference may be made to relevant descriptions in the method embodiment shown in FIG. 13 , and details are not repeated here.

Based on the same idea, as shown in FIG. 16 , an embodiment of the present application provides a communication device 1600 , where the communication device 1600 may be a chip or a chip system. Optionally, in the embodiment of the present application, the system-on-a-chip may be composed of chips, or may include chips and other discrete devices.

The communication device 1600 may include at least one processor 1610, and the processor 1610 is coupled with a memory. Optionally, the memory may be located inside the device or outside the device. For example, the communication device 1600 may further include at least one memory 1620 . The memory 1620 stores necessary computer programs, configuration information, computer programs or instructions and/or data for implementing any of the above embodiments; the processor 1610 may execute the computer programs stored in the memory 1620 to complete the methods in any of the above embodiments.

The coupling in the embodiments of the present application is an indirect coupling or a communication connection between devices, units or modules, which may be in electrical, mechanical or other forms, and is used for information exchange between devices, units or modules. The processor 1610 may operate in cooperation with the memory 1620 .

The communication apparatus 1600 may further include a transceiver 1630, and the communication apparatus 1600 may perform information exchange with other devices through the transceiver 1630. The transceiver 1630 may be a circuit, a bus, a transceiver or any other device that can be used for information exchange, or is called a signal transceiving module. As shown in FIG. 16 , the transceiver 1630 includes a transmitter 1631 , a receiver 1632 and an antenna 1633 . In addition, when the communication device 1600 is a chip-like device or circuit, the transceiver in the communication device 1600 can also be an input and output circuit and/or a communication interface, which can input data (or receive data) and output data ( or referred to as sending data), the processor is an integrated processor or a microprocessor or an integrated circuit, and the processor can determine output data according to input data.

The embodiment of the present application does not limit the specific connection medium among the transceiver 1630, the processor 1610, and the memory 1620.

In a possible implementation manner, the communication apparatus 1600 may be applied to the first device, and the specific communication apparatus 1600 may be the first device, or may be capable of supporting the first device, so as to realize the first The means by which the device functions. The memory 1620 stores necessary computer programs, computer programs or instructions and/or data to realize the functions of the first device in any of the above-mentioned embodiments. The processor 1610 may execute the computer program stored in the memory 1620 to complete the method performed by the first device in any of the foregoing embodiments. Applied to the first device, the transmitter 1631 in the communication apparatus 1600 may be used to send transmission control configuration information to the network through the antenna 1633 , and the receiver 1632 may be used to receive the transmission information sent by the network through the antenna 1633 .

In another possible implementation manner, the communication device 1600 can be applied to core network equipment, and the specific communication device 1600 can be a core network device, or can support a core network device, to implement the core A device that functions as a network device. The memory 1620 stores necessary computer programs, computer programs or instructions and/or data for realizing the functions of the core network device in any of the foregoing embodiments. The processor 1610 may execute the computer program stored in the memory 1620 to complete the method performed by the core network device in any of the foregoing embodiments.

In a possible implementation, the communication device 1600 can be applied to access network equipment, and the specific communication device 1600 can be an access network device, or can support an access network device, to implement any of the above-mentioned embodiments A device that accesses the functions of network equipment. The memory 1620 stores necessary computer programs, computer programs or instructions and/or data for realizing the functions of the access network device in any of the foregoing embodiments. The processor 1610 may execute the computer program stored in the memory 1620 to complete the method performed by the access network device in any of the foregoing embodiments. Applied to access network devices, the transmitter 1631 in the communication apparatus 1600 may be used to send transmission information to the first device through the antenna 1633 , and the receiver 1632 may be used to receive the transmission control configuration information sent by the first device through the antenna 1633 .

[Corrected 13.06.2022 under Rule 91]
Because the communication apparatus 1600 provided in this embodiment can be applied to the first device to complete the method performed by the above-mentioned first device, or applied to the core network device to complete the method performed by the core network device. Or, it is applied to an access network device to complete the method performed by the access network device. Therefore, the technical effects that can be obtained can refer to the above-mentioned method embodiments, and will not be repeated here.

In this embodiment of the application, the processor may be a general-purpose processor, a digital signal processor, an application-specific integrated circuit, a field programmable gate array or other programmable logic device, a discrete gate or transistor logic device, or a discrete hardware component, and may implement or Execute the methods, steps and logic block diagrams disclosed in the embodiments of the present application. A general purpose processor may be a microprocessor or any conventional processor or the like. The steps of the methods disclosed in connection with the embodiments of the present application may be directly implemented by a hardware processor, or implemented by a combination of hardware and software modules in the processor.

In the embodiment of the present application, the memory may be a non-volatile memory, such as a hard disk (hard disk drive, HDD) or a solid-state drive (solid-state drive, SSD), etc., and may also be a volatile memory (volatile memory), such as Random-access memory (RAM). The memory may also be, but is not limited to, 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 in the embodiment of the present application may also be a circuit or any other device capable of implementing a storage function, for storing computer programs, computer programs or instructions and/or data.

Based on the above embodiments, referring to FIG. 17, the embodiment of the present application also provides another communication device 1700, including: an input and output interface 1710 and a logic circuit 1720; the input and output interface 1710 is used to receive code instructions and transmit them to the logic circuit 1720; The logic circuit 1720 is configured to run code instructions to execute the method executed by the first device or the method executed by the core network device or the method executed by the access network device in any one of the above embodiments.

Hereinafter, operations performed by applying the communication apparatus to the first device or the core network device or the access network device will be described in detail.

In an optional implementation manner, the communication apparatus 1700 may be applied to a first device to execute the above method executed by the first device, specifically, for example, the method executed by the first device in the preceding cases 1-4. Logic circuit 1720, configured to generate a service transfer request. The service transfer request includes the information of the second device, and the service transfer request is used to request to transfer the service to be transferred from the source device to the target device. The input and output interface 1710 is used to output service transfer requests. The input and output interface 1710 is also used to input the first message. The first message includes service information to be transferred.

In another optional implementation manner, the communication apparatus 1700 may be applied to a core network device to execute the above method performed by the core network device, specifically, for example, the methods performed by the core network device in the preceding cases 1-4. The input and output interface 1710 is used for inputting a service transfer request. The service transfer request includes the information of the second device, and the service transfer request is used to request to transfer the service to be transferred from the source device to the target device. Logic circuit 1720, configured to generate a first message. Wherein, the first message includes service information to be transferred. The input and output interface 1710 is configured to output the first message.

In an optional implementation manner, the communication device may be applied to a core network device to perform the method performed by the above core network device, specifically, for example, the method performed by the core network device in the method embodiment shown in FIG. 13 . The input and output interface 1710 is used for inputting a service transfer request. The service transfer request includes the information of the second device, and the service transfer request is used to request to transfer the service to be transferred from the source device to the target device. Logic circuit 1720, configured to generate a first request message. The first request message is used to instruct the access network device to establish a target PDU session for the target device. The input and output interface 1710 is configured to output the first request message.

In another optional implementation manner, the communication device 1700 can be applied to an access network device to execute the above-mentioned method performed by the access network device, specifically, for example, the access network device in the method embodiment shown in FIG. 13 The method executed. The input and output interface 1710 is configured to receive the first request message. The first request message is used to instruct the access network device to establish a target PDU session for the target device. Wherein, the first request message includes indication information; the indication information is used to indicate that the target PDU session of the target device uses the source PDU session of the first device. Optionally, the logic circuit 1720 is configured to generate a first response message. The first response message includes the identifier of the target PDU session and the information of the first GTP tunnel; the first GTP tunnel is the GTP tunnel of the source PDU session. The input and output interface 1710 is configured to output the first response message.

Because the communication apparatus 1700 provided in this embodiment can be applied to the first device to execute the method executed by the above-mentioned first device, or applied to the core network device to execute the method executed by the core network device. Or, it is applied to an access network device to execute the method performed by the access network device. Therefore, the technical effects that can be obtained can refer to the above-mentioned method embodiments, and will not be repeated here.

Based on the above embodiments, an embodiment of the present application further provides a communication system, where the communication system includes at least one communication device applied to a first device and at least one communication device applied to a core network device. For the technical effects that can be obtained, reference can be made to the foregoing method embodiments, and details are not repeated here.

Based on the above embodiments, an embodiment of the present application further provides a communication system, where the communication system includes at least one communication device applied to core network equipment and at least one communication device applied to access network equipment. For available technical details, reference may be made to the above-mentioned method embodiments, and details are not repeated here.

Based on the above embodiments, embodiments of the present application further provide a computer-readable storage medium, which stores computer programs or instructions, and when the instructions are executed, the first device in any of the above-mentioned embodiments executes the The method is implemented or the method executed by the core network equipment is implemented or the method executed by the access network equipment is implemented. The computer-readable storage medium may include: a U disk, a mobile hard disk, a read-only memory, a random access memory, a magnetic disk or an optical disk, and other media capable of storing program codes.

In order to realize the functions of the above-mentioned communication devices in Figures 14 to 17, the embodiment of the present application further provides a chip, including a processor, used to support the communication device to implement the first device or core network device or access The functions involved in the network equipment. In a possible design, the chip is connected to a memory or the chip includes a memory for storing necessary computer programs or instructions and data of the communication device.

Those skilled in the art should understand that the embodiments of the present application may be provided as methods, systems, or computer program products. Accordingly, the present application may take the form of an entirely hardware embodiment, an entirely software embodiment, or an embodiment combining software and hardware aspects. Furthermore, the present application may take the form of a computer program product embodied on one or more computer-usable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) having computer-usable program code embodied therein.

The present application is described with reference to flowcharts and/or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of the present application. It should be understood that each procedure and/or block in the flowchart and/or block diagram, and a combination of procedures and/or blocks in the flowchart and/or block diagram can be realized by computer programs or instructions. These computer programs or instructions may be provided to a general purpose computer, special purpose computer, embedded processor, or processor of other programmable data processing equipment to produce a machine such that instructions executed by the processor of the computer or other programmable data processing equipment produce Means for realizing the functions specified in one or more procedures of the flowchart and/or one or more blocks of the block diagram.

These computer programs or instructions may also be stored in a computer-readable memory capable of directing a computer or other programmable data processing apparatus to operate in a specific manner, such that the instructions stored in the computer-readable memory produce an article of manufacture comprising instruction means, the The instruction means implements the functions specified in one or more procedures of the flowchart and/or one or more blocks of the block diagram.

These computer programs or instructions may also be loaded onto a computer or other programmable data processing device, causing a series of operational steps to be performed on the computer or other programmable device to produce a computer-implemented process for execution on the computer or other programmable device The instructions provide steps for implementing the functions specified in the procedure or procedures of the flowchart and/or the block or blocks of the block diagram.

Apparently, those skilled in the art can make various changes and modifications to the embodiments of the present application without departing from the scope of the embodiments of the present application. In this way, if the modifications and variations of the embodiments of the present application fall within the scope of the claims of the present application and equivalent technologies, the present application also intends to include these modifications and variations.

Claims

A business transfer method, characterized by comprising:

The first device sends a service transfer request to the core network device; the service transfer request includes information of the second device, and the service transfer request is used to request transfer of the service to be transferred from the source device to the target device;

The first device receives a first message from the core network device; the first message includes service information to be transferred.
The method according to claim 1, wherein before the first device sends the service transfer request to the core network device, it further includes:

The first device receives the service information to be transferred from the second device; the second device is the source device, and the first device is the target device.
The method according to claim 2, further comprising:

The first device receives the second device information from the second device.
The method according to any one of claims 1 to 3, wherein the service transfer request further includes the service information to be transferred.
The method according to claim 2 or 3, wherein the first message is a service establishment request.
The method according to claim 1, wherein the first device is the source device, the second device is the target device; and the first message is a service release message.
The method according to claim 1, wherein the first device receives service data from the second device, and the service data is cached data of the service to be transferred; or, the first device Send the service data to the second device.
The method according to claim 1, wherein the second device is the source device, and the third device is the target device; the third device is a personal Internet of Things network managed by the first device PIN device.
The method according to claim 8, wherein, before the first device sends the service transfer request to the core network device, further comprising:

The first device receives the service information to be transferred and the information of the third device from the second device.
The method according to claim 8, wherein before the first device sends the service transfer request to the core network device, it further includes:

The first device receives the service information to be transferred and the information of the second device from the third device.
The method according to any one of claims 1-10, wherein the information of the second device includes at least one of the following:

The identifier of the second device, the device identifier for managing the second device, the PIN identifier of the second device, the PIN device identifier of the second device, the shortened global unique temporary identifier S-TMSI, the globally unique temporary identifier GUTI, user unique permanent identity SUPI or user unique permanent identity SUCI.
The method according to any one of claims 1 to 11, wherein the service information to be transferred includes at least one of protocol data unit (PDU) session information and quality of service (QoS) flow information.
A business transfer method, characterized by comprising:

The core network device receives a service transfer request from the first device; the service transfer request includes information of the second device, and the service transfer request is used to request to transfer the service to be transferred from the source device to the target device;

The core network device sends a first message to the first device; the first message includes service information to be transferred.
The method according to claim 13, wherein the second device is the source device, the first device is the target device; and the first message is a service establishment request.
The method according to claim 13 or 14, wherein the service transfer request further includes the service information to be transferred.
The method according to claim 13, wherein the first device is the source device, the second device is the target device; and the first message is a service release message.
The method according to claim 13, wherein the second device is the source device, and the third device is the target device; the third device is a personal Internet of Things network managed by the first device PIN device.
The method according to claim 17, wherein the first message further includes information of the third device.
The method according to any one of claims 13-18, wherein the information of the second device includes at least one of the following:

The identifier of the second device, the device identifier for managing the second device, the PIN identifier of the second device, the PIN device identifier of the second device, the shortened global unique temporary identifier S-TMSI, the globally unique temporary identifier GUTI, user unique permanent identity SUPI or user unique permanent identity SUCI.
The method according to any one of claims 13-19, wherein the service information to be transferred includes at least one of protocol data unit (PDU) session information and quality of service (QoS) flow information.
A business transfer method, characterized by comprising:

The core network device receives a service transfer request from the first device; the service transfer request is used to request to transfer the service to be transferred to the target device;

The core network device sends a first request message to the access network device; the first request message is used to instruct the access network device to establish a target protocol data unit PDU session for the target device.
The method according to claim 21, wherein the first request message includes the information of the target device, the information of the target PDU session and indication information; the indication information is used to indicate the The target PDU session uses the source PDU session of the first device; the information of the target PDU session includes at least one quality of service QoS flow information; the at least one QoS flow information is the first device executing the service to be transferred QoS flow information.
The method according to claim 22, wherein the indication information includes at least one of the following: an identifier of the first device or information of a first GTP tunnel of the source PDU session.
The method according to any one of claims 21-23, further comprising:

The core network device receives a first response message from the access network device; the first response message includes the identifier of the target PDU session and information about the first GTP tunnel; the first GTP tunnel is the GTP tunnel for the source PDU session.
The method according to any one of claims 21-24, further comprising:

The core network device sends a second request message to the access network device; the second request message is used to request the access network device to release the source PDU session; the second request message includes the source PDU session The identifier of the PDU session.
The method according to any one of claims 21-25, further comprising: the core network device receiving a second response message from the access network device; the second response message is used to notify the The core network device has released the source PDU session.
A business transfer method, characterized by comprising:

The access network device receives a first request message from the core network device; the first request message is used to instruct the access network device to establish a target protocol data unit PDU session for the target device;

Wherein, the first request message includes indication information; the indication information is used to indicate that the target PDU session of the target device uses the source PDU session of the first device.
The method according to claim 27, further comprising:

The access network device sends a first response message to the core network device; the first response message includes the identifier of the target PDU session and the information of the first GTP tunnel; the first GTP tunnel is the source GTP tunnel for PDU sessions.
The method according to claim 27 or 28, wherein the first request message further includes the information of the target device and the information of the target PDU session; the information of the target PDU session includes at least one quality of service QoS flow information: the at least one piece of QoS flow information is the QoS flow information for the first device to execute the service to be transferred.
The method according to any one of claims 27-29, wherein the indication information includes at least one of the following: an identifier of the first device or information of a first GTP tunnel of the source PDU session.
The method according to any one of claims 27-30, further comprising:

The access network device receives a second request message from the core network device; the second request message is used to request the access network device to release the source PDU session; the second request message includes the Identifier of the source PDU session.
The method according to any one of claims 27-31, further comprising:

The access network device sends a second response message to the core network device; the second response message is used to inform the core network device that the source PDU session has been released.
A communication device, characterized by comprising a module for performing the method according to any one of claims 1 to 12, or comprising a module for performing the method according to any one of claims 13 to 20 A module, or a module of the method according to any one of claims 21 to 26, or a module of the method according to any one of claims 27 to 32.
A communication device, characterized by comprising: a processor and a memory;

said memory for storing computer programs or instructions;

The processor is configured to execute a computer program or an instruction in a memory, so that the device performs the method according to any one of claims 1 to 12 or makes the device perform any one of claims 13 to 20 The method described in item 1 or causing the device to perform the method described in any one of claims 21 to 26 or causing the device to perform the method described in any one of claims 27 to 32.
A computer-readable storage medium, characterized in that the computer-readable storage medium stores computer-executable instructions, and when the computer-executable instructions are invoked by a computer, the or the method described in any one of claims 13 to 20 is carried out; or the method described in any one of claims 21 to 26 is carried out; or carried out as claimed in any one of claims 27 to 32 The method described in any one is carried out.
A computer program product, characterized in that it contains computer-executable instructions, and when the instructions are run on a computer, the method according to any one of claims 1 to 12 is executed; or as claimed in claims 13 to 12 The method according to any one of claims 20 is carried out; or the method according to any one of claims 21 to 26 is carried out; or the method according to any one of claims 27 to 32 is carried out.