CN114501490B

CN114501490B - Service transfer method, terminal and network side equipment

Info

Publication number: CN114501490B
Application number: CN202011273311.7A
Authority: CN
Inventors: 谢振华; 柯小婉; 杨晓东
Original assignee: Vivo Mobile Communication Co Ltd
Current assignee: Vivo Mobile Communication Co Ltd
Priority date: 2020-11-13
Filing date: 2020-11-13
Publication date: 2024-04-02
Anticipated expiration: 2040-11-13
Also published as: CN114501490A; WO2022100544A1

Abstract

The embodiment of the application discloses a service transfer method, a terminal and network side equipment, which can solve the problem that service transfer cannot be realized in the related technology. The method may be performed by a second terminal, comprising: and sending a non-access stratum (NAS) message to the core network, wherein the NAS message is used for requesting to establish, modify or activate the Protocol Data Unit (PDU) session of the first terminal user.

Description

Service transfer method, terminal and network side equipment

Technical Field

The application belongs to the technical field of communication, and particularly relates to a service transfer method, a terminal and network side equipment.

Background

With the development of terminal technology, the requirements of users for service transfer between terminals are also becoming more and more obvious. A typical business transfer application requirement includes: the mobile phone is playing online or offline video, the user does not want to be interrupted by unimportant incoming call, when the mobile phone receives an IMS call request, the user wants not to ring the responding incoming call, but requests the intelligent watch to divide the user plane of the telephone service on the intelligent watch and then ring to answer. However, the related art does not provide a related scheme for service transfer, and cannot meet the increasing service transfer requirements.

Disclosure of Invention

The embodiment of the application provides a service transfer method, a terminal and network side equipment, which can solve the problem that service transfer cannot be realized in the related technology.

In a first aspect, a service transfer method is provided, the method being performed by a second terminal, the method comprising: and sending a non-access stratum (NAS) message to the core network, wherein the NAS message is used for requesting to establish, modify or activate the Protocol Data Unit (PDU) session of the first terminal user.

In a second aspect, a service transfer method is provided, the method being performed by a first core network function, the method comprising: receiving NAS information sent by a second terminal, wherein the NAS information is used for requesting to establish, modify or activate a PDU session of a first terminal user; and transmitting transfer information to the second core network function.

In a third aspect, a service transfer method is provided, the method being performed by a first terminal, the method comprising: transmitting service information to be transferred to a second terminal; the service information to be transferred is used for the second terminal to send NAS information to the core network, and the NAS information is used for requesting to establish, modify or activate the PDU session of the first terminal user.

In a fourth aspect, a service transfer method is provided, where the method is performed by an access network side device, and the method includes: receiving a transfer relationship from a core network; forwarding the service data to the second terminal or the second terminal and the first terminal according to the transfer relation; wherein the transfer relationship comprises at least one of: the method comprises the steps of transferring a service data tunnel identifier QFI of the service, transferring a service data service quality stream identifier QFI of the service, transferring a service data tunnel identifier and a transfer instruction, identifying a service data tunnel identifier and a second terminal, identifying a service data service quality stream identifier QFI and a transfer instruction, identifying a service data service quality stream identifier QFI and a second terminal, identifying a service data tunnel identifier and a first terminal user, identifying a service data tunnel identifier and a first terminal, identifying a service data service quality stream identifier QFI and a first terminal user, and identifying a service data service quality stream identifier QFI and a first terminal.

In a fifth aspect, a service transfer method is provided, the method being performed by a second core network function, the method comprising: receiving transfer information from a first core network function; and sending a transfer relation to access network side equipment through the first core network function, wherein the transfer relation is used for forwarding service data to a second terminal or the second terminal and the first terminal by the access network equipment.

In a sixth aspect, there is provided a second terminal comprising: and the sending module is used for sending a non-access stratum (NAS) message to the core network, wherein the NAS message is used for requesting to establish, modify or activate the Protocol Data Unit (PDU) session of the first terminal user.

In a seventh aspect, a first core network function is provided, including: the receiving module is used for receiving an NAS message sent by the second terminal, wherein the NAS message is used for requesting to establish, modify or activate the PDU session of the first terminal user; and the sending module is used for sending the transfer information to the second core network function.

An eighth aspect provides a first terminal, including: the sending module is used for sending the service information to be transferred to the second terminal; the service information to be transferred is used for the second terminal to send NAS information to the core network, and the NAS information is used for requesting to establish, modify or activate the PDU session of the first terminal user.

A ninth aspect provides an access network side device, including: the receiving module is used for receiving the transfer relation from the core network; the sending module is used for forwarding the service data to the second terminal or the second terminal and the first terminal according to the transfer relation; wherein the transfer relationship comprises at least one of: the method comprises the steps of transferring a service data tunnel identifier QFI of the service, transferring a service data service quality stream identifier QFI of the service, transferring a service data tunnel identifier and a transfer instruction, identifying a service data tunnel identifier and a second terminal, identifying a service data service quality stream identifier QFI and a transfer instruction, identifying a service data service quality stream identifier QFI and a second terminal, identifying a service data tunnel identifier and a first terminal user, identifying a service data tunnel identifier and a first terminal, identifying a service data service quality stream identifier QFI and a first terminal user, and identifying a service data service quality stream identifier QFI and a first terminal.

In a tenth aspect, there is provided a second core network function, comprising: the receiving module is used for receiving transfer information from the first core network function; and the sending module is used for sending a transfer relation to the access network side equipment through the first core network function, wherein the transfer relation is used for forwarding the service data to the second terminal or the second terminal and the first terminal by the access network equipment.

In an eleventh aspect, there is provided a terminal comprising a processor, a memory and a program or instruction stored on the memory and executable on the processor, the program or instruction when executed by the processor implementing the method according to the first or third aspect.

In a twelfth aspect, there is provided a network side device comprising a processor, a memory and a program or instruction stored on the memory and executable on the processor, the program or instruction implementing the method according to any one of the second aspect, the fourth aspect and the fifth aspect when executed by the processor.

In a thirteenth aspect, there is provided a readable storage medium having stored thereon a program or instructions which, when executed by a processor, implement the method according to any of the first to fifth aspects.

In a fourteenth aspect, there is provided a computer program product comprising a processor, a memory and a program or instruction stored on the memory and executable on the processor, the program or instruction when executed by the processor implementing the method according to any one of the first to fifth aspects.

In a fifteenth aspect, there is provided a chip comprising a processor and a communications interface, the communications interface and the processor being coupled, the processor being for running a program or instructions to implement the method of any of the first to fifth aspects.

In the embodiment of the application, the second terminal user requests the core network to establish, modify or activate the PDU session of the first terminal user by the identity of the first terminal user, so that the subsequent network side can transfer the service data to the second terminal based on the PDU session.

Drawings

Fig. 1 is a block diagram of a wireless communication system according to one embodiment of the present application;

FIG. 2 is a schematic flow chart diagram of a method of traffic transfer according to one embodiment of the present application;

FIG. 3 is a schematic diagram of a specific application of a service diversion method according to an embodiment of the present application;

FIG. 4 is a schematic flow chart diagram of a method of traffic transfer according to one particular embodiment of the present application;

FIG. 5 is a schematic flow chart diagram of a method of traffic transfer according to one embodiment of the present application;

FIG. 6 is a schematic flow chart diagram of a method of traffic transfer according to one embodiment of the present application;

FIG. 7 is a schematic flow chart diagram of a method of traffic transfer in accordance with one embodiment of the present application;

FIG. 8 is a schematic flow chart diagram of a method of traffic transfer according to one embodiment of the present application;

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

fig. 10 is a schematic structural diagram of a first core network function according to an embodiment of the present application;

fig. 11 is a schematic structural view of a first terminal according to an embodiment of the present application;

fig. 12 is a schematic structural diagram of an access network side device according to an embodiment of the present application;

fig. 13 is a schematic structural diagram of a second core network function according to an embodiment of the present application;

fig. 14 is a schematic structural view of a communication device according to an embodiment of the present application;

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

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

Detailed Description

Technical solutions in the embodiments of the present application will be clearly described below with reference to the drawings in the embodiments of the present application, and it is apparent that the described embodiments are some embodiments of the present application, but not all embodiments. All other embodiments obtained by a person of ordinary skill in the art based on the embodiments in the present application are within the scope of the protection of the present application.

The terms first, second and the like in the description and in the claims, are used for distinguishing between similar objects and not necessarily for describing a particular sequential or chronological order. It is to be understood that the data so used may be interchanged where appropriate, such that embodiments of the present application may be implemented in sequences other than those illustrated or described herein, and that the "first" and "second" distinguished objects generally are of the type and do not limit the number of objects, e.g., the first object may be one or more. Furthermore, in the description and claims, "and/or" means at least one of the connected objects, and the character "/" generally means a relationship in which the associated object is an "or" before and after.

It is noted that the techniques described in embodiments of the present application are not limited to long term evolution (Long Term Evolution, LTE)/LTE evolution (LTE-Advanced, LTE-a) systems, but may also be used in other wireless communication systems, such as code division multiple access (Code Division Multiple Access, CDMA), time division multiple access (Time Division Multiple Access, TDMA), frequency division multiple access (Frequency Division Multiple Access, FDMA), orthogonal frequency division multiple access (Orthogonal Frequency Division Multiple Access, OFDMA), single-carrier frequency division multiple access (Single-carrier Frequency-Division Multiple Access, SC-FDMA), and other systems. The terms "system" and "network" in embodiments of the present application are often used interchangeably, and the techniques described may be used for both the above-mentioned systems and radio technologies, as well as other systems and radio technologies. The following description describes a New air interface (NR) system for purposes of illustration, and NR terminology is used in much of the following description, but these techniques are also applicable to applications other than NR system applications, such as generation 6 (6 ^th Generation, 6G) communication system.

Fig. 1 shows a block diagram of a wireless communication system to which embodiments of the present application are applicable. The wireless communication system includes a terminal 11 and a network device 12. The terminal 11 may also be called a terminal Device or a User Equipment (UE), and the terminal 11 may be a terminal-side Device such as a mobile phone, a tablet Computer (Tablet Personal Computer), a Laptop (Laptop Computer) or a notebook (Personal Digital Assistant, PDA), a palm Computer, a netbook, an ultra-mobile personal Computer (ultra-mobile personal Computer, UMPC), a mobile internet Device (Mobile Internet Device, MID), a Wearable Device (or a vehicle-mounted Device (VUE), a pedestrian terminal (PUE), and the Wearable Device includes: a bracelet, earphone, glasses, etc. Note that, the specific type of the terminal 11 is not limited in the embodiment of the present application. The network side device 12 may be a base station or a core network, wherein the base station may be called a node B, an evolved node B, an access point, a base transceiver station (Base Transceiver Station, BTS), a radio base station, a radio transceiver, a basic service set (Basic Service Set, BSS), an extended service set (Extended Service Set, ESS), a node B, an evolved node B (eNB), a next generation node B (gNB), a home node B, a home evolved node B, a WLAN access point, a WiFi node, a transmission and reception point (Transmitting Receiving Point, TRP), or some other suitable terminology in the field, and the base station is not limited to a specific technical vocabulary, and it should be noted that, in the embodiment of the present application, only the base station in the NR system is taken as an example, but the specific type of the base station is not limited.

The service transfer method, the terminal and the network side device provided in the embodiments of the present application are described in detail below with reference to the accompanying drawings through specific embodiments and application scenarios thereof.

As shown in fig. 2, one embodiment of the present application provides a service transfer method 200, which may be performed by a second terminal, in other words, by software or hardware installed at the second terminal, the method including the following steps.

S202: a Non-Access Stratum (NAS) message is sent to the core network requesting to establish, modify or activate a protocol data unit (Protocol Data Unit, PDU) session of the first end user.

The core network (or core network function) in this embodiment may be an access and mobility management function (Access and Mobility Management Function, AMF) serving the first end user.

The NAS message in this embodiment may be from the first terminal, so that the second terminal may also receive the above NAS message from the first terminal before S202. For example, the first terminal and the second terminal interact through a short-range communication manner, for example, using a Sidelink (sidlink) or wireless network (Wifi) technology, and the first terminal sends the NAS message to the second terminal.

It should be noted that, in the embodiments of the present specification, the first terminal and the first terminal user are mentioned, and the first terminal user may be an identity of a SIM card installed in the first terminal, and in some cases, the first terminal and the first terminal user may also be understood as equivalent concepts. The same applies to the second terminal and the second terminal user.

Optionally, the NAS message includes at least one of: the identity of the first terminal user, the identity of the first terminal, the PDU session Identity (ID), the quality of service flow identity (Qos Flow Identity, QFI) of the service to be transferred, and the packet filter information (packet filter) of the service to be transferred.

In this embodiment, the second end user requests the core network to establish, modify or activate the PDU session of the first end user with the identity of the first end user, so that in the subsequent process, the network side (such as the access network side equipment of the base station) can distinguish the targets of sending service data according to the PDU session ID and the like.

In one example, as shown in fig. 3, a first end user' S PDU session (i.e., the PDU session established, modified, or activated in S202) is nested with QFI sets, each of which may include one or more QFI. In fig. 3, the base station (gNB) may directly transmit the service data corresponding to the QFI set 1 to the first terminal (UE 1), transfer the service data corresponding to the QFI set 2 to the second terminal (UE 2), or transmit the service data to both the first terminal and the second terminal.

In another example, the first end user may even correspond to multiple PDU sessions, such as a first PDU session and a second PDU session, where the first PDU session is a PDU session that the first end user itself requests to establish, modify or activate, and the second PDU session is a PDU session that the second end user requests to establish, modify or activate in S202, so that the base station (gNB) may send the service data corresponding to the first PDU session directly to the first terminal (UE 1), transfer the service data corresponding to the second PDU session to the second terminal (UE 2), or send the service data corresponding to the second PDU session to both the first terminal and the second terminal.

According to the service transfer method provided by the embodiment of the application, the second terminal user requests the core network to establish, modify or activate the PDU session of the first terminal user by the identity of the first terminal user, so that the subsequent network side can transfer service data to the second terminal based on the PDU session.

Optionally, before the second terminal sends the NAS message to the core network in S200, the method further includes the following steps: the second terminal receives at least one of the following from the first terminal: the NAS message, a first key, cell information and service information to be transferred.

The first key is used for generating a new key by the first terminal or the second terminal, so AS to protect signaling of an access stratum AS related process or signaling of a NAS related process. In one example, after the second terminal receives the first key from the first terminal, the method further comprises at least one of:

1) The second terminal protects Access Stratum (AS) related procedure signaling based on the first key or a second key generated based on the first key. The second key may be generated by the second terminal, or may be generated by the first terminal and transmitted to the second terminal. Signaling of the AS related procedure includes, for example, RRC connection setup (RRC Connection Establishment) messages, etc.

2) The second terminal protects signaling of NAS related procedures based on the first key or a third key generated based on the first key. The third key may be generated by the second terminal, or may be generated by the first terminal and transmitted to the second terminal. The signaling of the NAS related procedure includes, for example, a Service Request (Service Request) message or a PDU session establishment (PDU Session Establishment) message, etc.

The cell information is used for the second terminal to select an access network side device, and the access network side device may be an access network side device that provides a service for the first terminal.

The service information to be transferred includes at least one of the following: application (Application) information of the service, current cookie information of the service, PDU session ID of the bearing service, QFI of the bearing service, message filter information of service data, identification of the first terminal user, and identification of the first terminal.

Optionally, each of the foregoing embodiments may further include at least one of:

1) And the second terminal sends a transfer instruction to the core network. The transfer instruction may be corresponding to PDU session identifier, QFI, or message filter information in the NAS message, and indicates that the service data corresponding to the PDU session identifier, QFI, or message filter information is a transfer application, and needs to be transferred to the second terminal.

2) And the second terminal sends the identification of the second terminal user to the core network or sends the identification of the second terminal.

Optionally, the foregoing embodiments may further include the steps of: the second terminal sends at least one of the following to the access network side equipment: the first terminal user identifier, the first terminal identifier, the core network function identifier (such as AMF 1) serving the first terminal user, the transfer instruction, the second terminal user identifier, and the second terminal identifier. The core network function identifier serving the first end user is used for the access network side device to route NAS messages to the core network function serving the first end user.

In order to describe the service transfer method provided in the embodiment of the present application in detail, a specific embodiment will be described below, and as shown in fig. 4, this embodiment includes the following steps.

Step 1: a first terminal (UE 1) registers in the network, and through the registration procedure, it is possible to obtain transfer-allowed terminal identification (allowed UE ID) information, which is used to indicate which UEs can transfer the session of the UE1, through a core network (such as AMF 1).

In one example, AMF1 carries zero or more allowed UE ID information in a registration accept message, where zero indicates that any UE can transfer the session for UE 1. The following embodiments mainly take as an example a session in which the second terminal (UE 2) can transfer UE 1.

Step 2: the UE1 and the second terminal (UE 2) interact through a short-range communication manner, for example, using a sidlink or Wifi technology, and the UE1 sends service information to be transferred to the UE 2.

Optionally, the service information to be transferred includes at least one of the following: application (Application) information of the service, current cookie information of the service, PDU session ID of the bearing service, QFI of the bearing service, message filter information of service data, identification of a first terminal user and identification of the first terminal.

The service information to be transferred may be carried in a message that UE1 requests UE2 to transfer, or may be carried in a message returned to UE2 by UE1 after UE2 requests UE 1.

Step 3: optionally, UE1 sends at least one of the following information to UE 2:

NAS message, first key (i.e. key 1), cell information.

In practical applications, step 3 and step 2 may be performed in combination, that is, the information in step 3 and the information in step 2 may be sent to UE2 together.

The NAS message is a message requesting to the core network to establish, modify or activate a PDU session for the first end user. Optionally, the NAS message includes at least one of: an identification of a first end user (e.g., UE1 ID), an identification of a first terminal, an identification of a second end user (e.g., UE2 ID), a PDU session identification ID, a quality of service flow identification QFI, message filter information, and a transition indication (IuT indication). The transfer indication is used to indicate that a transfer operation needs to be performed.

The key 1 is derived from a key shared by the UE1 and the core network, and may be multiple keys, the key 1 may also be derived based on the UE2 ID or an ID corresponding to the UE2 ID (i.e. derived based on a key shared by the UE1 and the core network and the UE2 ID), and the UE2 may derive a second key (key 2) for the AS related procedure and a third key (key 3) for the NAS related procedure based on the key 1 and the UE2 ID, respectively, such AS derived based on the key 1 and the UE2 ID. If UE1 has passed key 1 to UE2 then no further passes are necessary, and if UE2 has either key 2 or key 3 (e.g., UE1 sent to UE 2), then UE2 does not regenerate these keys.

The above cell information is used for UE2 to select an access network side device, and UE2 may select a gNB based on the received cell information, where the gNB may be a gNB that provides services for UE 1.

Step 4: UE2 interactively activates the air interface connection with the gNB, e.g., UE2 performs a random access procedure (e.g., two-step random access messages 1-2) and an RRC connection setup (RRC Connection Establishment) (i.e., messages 3-5) procedure. In the air interface connection activation process, UE2 sends at least one of the following information to the gNB: the identity of the first terminal user (UE 1 ID), the identity of the first terminal, the core network function identity (AMF 1) serving the first terminal user, the transition indication (IuT indication), the identity of the second terminal user, and the identity of the second terminal.

Step 5 can be divided into two cases:

case 1, ue2 sends a NAS message to AMF1. Case 1 may be performed in case UE2 sends UE1 ID to the gNB.

Case 2, ue2 forwards the NAS message to AMF1 via AMF 2. Case 2 may be performed in case UE2 sends AMF1 to the gNB.

Step 5 and step 4 may be performed in combination, i.e. UE2 carries the NAS message in the AS message.

In step 5, UE2 requests to the core network (AMF 1) to establish, modify or activate a PDU session of UE1, such as sending a Service Request (Service Request) or a NAS message for PDU session establishment (PDU Session Establishment).

For a detailed description of this NAS message, reference may be made to the description in step 3, and this NAS message may be received by UE2 in step 3, and thus may be protected by UE1 using a key shared by UE1 and the core network, or may be transmitted by UE2, and thus may be protected by UE2 using key 1 or key 3.

Optionally, after step 5, AMF1 may also generate key 1 or key 3 using the same rule in step 3 based on the transfer indication (IuT indication) or the UE2ID, and process the received NAS message based on key 1 or key 3 (without reproduction if key 1 or key 3 is already present).

Step 6: optionally, the AMF1 performs a determination according to at least one of the following, and if the determination result is yes, step 7 is performed.

1) In step 5, whether the radio access network (Radio Access Network, RAN) node information (such as cell ID, gNB ID, etc.) from which the message comes is the same as the RAN node information where the UE1 is located.

2) The PDU session type corresponding to the PDU session ID, such as whether it is a transfer type.

3) Subscription information of UE1, such as whether UE1 allows UE2 to transfer a session or whether UE2 is allowed to transfer a specified data flow.

4) The AMF1 may also request the AMF2 or AUSF2 to which the UE2 belongs for subscription information of the UE2, and determine whether the UE2 can transfer the session of the UE1 according to the subscription information of the UE2, or whether the UE2 is allowed to transfer the designated data stream of the UE 1.

5) The AMF1 may also request the AMF2 or AUSF2 to determine according to the subscription information of the UE2 and return a determination result, where the determination result may be whether the UE2 can transfer the session of the UE1 or whether the UE2 is allowed to transfer the designated data stream of the UE1.

Step 7: AMF1 sends transfer information to SMF1, the transfer information including at least one of:

the first terminal user identifier (UE 1 ID), the first terminal user access core network function identifier (AMF 1), a transfer instruction, a PDU Session ID, QFI, and a packet filter.

Step 8: optionally, SMF1 interacts with a user port function (User Port Function, UPF) 1 to indicate a QFI corresponding to a data flow corresponding to a packet filter. Reference may be made in particular to the description of the functional side of the first core network in the embodiments described hereinafter.

Step 9: the SMF1 sends flow information to the gNB through the AMF1, where the flow information includes QFI and the like, and may also include an IuT indicator, which is used to indicate which QFI is used for transfer, that is, which QFI is transferred to the UE2, and which is not required to be transferred, and directly sent to the UE1.

Step 10: AMF1 receives information sent by SMF1 to gNB, and forwards the information to gNB, wherein the information comprises QFI (quad Flat information), and also can comprise IuT indicator for indicating that the QFI is used for transferring.

AMF1 may also generate key 1 or key 2 using the same rules in step 3 and send key 1 or key 2 to the gNB. AMF1 may also assign a new UE ID to UE2 and send it to UE2 via the base station (e.g., via NAS message).

Step 11: the UE2 and the gNB complete air interface interaction to establish a wireless transmission channel, and the interaction process and the user data transmitted between the UE2 and the gNB can be protected based on the key 1 or the key 2.

The gNB identifies whether to issue data to UE1 or transfer data to UE2 based on QFI.

The service transfer method according to the embodiment of the present application is described in detail above in connection with fig. 2 to 4. The service transfer method according to further several embodiments of the present application will be described in detail below with reference to fig. 5 to 8. It will be appreciated that the descriptions of fig. 5 to 8 are identical to or correspond to the partial descriptions of the methods shown in fig. 2 to 4, and the relevant descriptions are omitted as appropriate to avoid repetition.

Fig. 5 is a schematic flow chart of a service transfer method according to an embodiment of the present application, which may be applied to a first core network function (such as AMF 1). As shown in fig. 5, the method 500 includes:

s502: and receiving a NAS message sent by the second terminal, wherein the NAS message is used for requesting to establish, modify or activate the PDU session of the first terminal user.

S504: and transmitting transfer information to the second core network function.

The NAS message may be that the second terminal sends the NAS message to the access network side device, and the access network side device forwards the NAS message to the first core network function.

In the embodiment of the application, the second terminal user requests the first core network function to establish, modify or activate the PDU session of the first terminal user by the identity of the first terminal user, so that the subsequent network side can transfer the service data to the second terminal based on the PDU session.

Optionally, as an embodiment, the method further includes: and sending an identification to the second terminal, wherein the identification is used for identifying the second terminal or the second terminal user. The identity in this embodiment may be an identity newly allocated by the first core network function for said second terminal or said second terminal user.

Optionally, as an embodiment, the method further includes: receiving a transfer instruction sent by the second terminal, and processing the NAS message based on a first key or a third key; wherein the first key is generated based on a key shared with the first end user; or, the first key is generated based on the identification of the second end user and a key shared with the first end user; or, the first key is generated based on the identification of the second terminal and a key shared with the first terminal user; the third key is generated based on the first key. The identifier of the second end user in this embodiment may be the newly allocated identifier or the original identifier of the second end user.

The transfer instruction in this embodiment may correspond to the PDU session identifier, QFI, or message filter information in the NAS message, and indicates that the service data corresponding to the PDU session identifier, QFI, or message filter information is a transfer application, and needs to be transferred to the second terminal.

Optionally, as an embodiment, the method further includes: sending the first key or the second key to an access network side device (for example, the access network side device from which the NAS message comes), where the first key or the second key is used to protect signaling of an access stratum AS related procedure; wherein the second key is generated based on the first key.

Optionally, as an embodiment, the sending the transfer information to the second core network function includes: transmitting transfer information to the second core network function according to at least one of:

1) The access network side equipment from which the NAS message comes is the same as the access network side equipment in which the first terminal is positioned;

2) Subscription information of the second end user. The first core network function may determine, according to the subscription information, whether the second end user may transfer the session of the first end user or whether the second end user is allowed to transfer the specified data stream of the first end user.

3) An indication of a core network function (e.g., AMF 2) from a serving second end user. The second core network function may determine, according to subscription information of the second end user, whether the second end user may transfer the session of the first end user, or whether the second end user is allowed to transfer the designated data stream of the first end user, and indicate the determination result to the first core network function.

Optionally, as an embodiment, the NAS message includes at least one of: the first terminal user identifier, the first terminal identifier, the PDU session identifier ID, the QFI service quality stream identifier and the message filter information.

1) The PDU session type corresponding to the PDU session identification ID; such as whether it is of the transfer type.

2) Subscription information of the first terminal user. Such as whether the first end user allows the second end user to transfer the session or whether the second end user is allowed to transfer the specified data stream.

Optionally, as an embodiment, the transfer information includes at least one of: PDU session identity ID, quality of service flow identity QFI, message filter information, transfer indication.

Fig. 6 is a schematic flow chart of a service transfer method according to an embodiment of the present application, which may be applied to a first terminal (UE 1). As shown in fig. 6, the method 600 includes:

s602: and sending service information to be transferred to a second terminal, wherein the service information to be transferred is used for sending NAS information to a core network by the second terminal, and the NAS information is used for requesting to establish, modify or activate PDU session of the first terminal user.

Optionally, the service information to be transferred includes at least one of: application information of the service, current cookie information of the service, PDU session ID of the bearing service, QFI of the bearing service, message filter information of service data, identification of the first terminal user and identification of the first terminal.

In the embodiment of the application, the first terminal sends the service information to be transferred to the second terminal, the second terminal user requests the first core network function to establish, modify or activate the PDU session of the first terminal user by the identity of the first terminal user, so that the subsequent network side can transfer the service data to the second terminal based on the PDU session.

Optionally, as an embodiment, the method further includes: transmitting to the second terminal at least one of: the first key, cell information, the NAS message.

Optionally, as an embodiment, the cell information is used for the second terminal to select an access network side device.

Optionally, as an embodiment, the method further includes: generating the first key based on a key shared by the first terminal and the core network; or generating the first key based on the identification of the second terminal and a key shared by the first terminal and the core network; or generating the first key based on the identity of the second terminal user and a key shared by the first terminal and the core network.

Fig. 7 is a schematic flow chart of a service transfer method in the embodiment of the present application, which may be applied to an access network side device (such as a gNB). As shown in fig. 7, the method 700 includes:

s702: a transfer relationship is received from a core network.

S704: and forwarding the service data to the second terminal according to the transfer relation, or forwarding the service data to the second terminal while the second terminal and the first terminal send the service data to the first terminal.

Wherein the transfer relationship comprises at least one of:

1) The service data tunnel identifier of the transfer service, that is, the service data in the service data tunnel is for transfer, needs to be transferred to the second terminal, and can of course also be simultaneously sent to the first terminal.

2) The service data quality of service flow identifier QFI of the transfer service, that is, the service data corresponding to the QFI is the transfer application, and needs to be transferred to the second terminal, and of course, can also be simultaneously sent to the first terminal.

3) The service data tunnel identifier and the transfer instruction, that is, the service data in the service data tunnel is for transfer, need to be transferred to the second terminal, and of course, can also be simultaneously sent to the first terminal.

4) The service data tunnel identifier and the identifier of the second terminal, that is, the service data in the service data tunnel is for transfer, and needs to be transferred to the second terminal, and of course, can also be simultaneously sent to the first terminal.

5) The service data tunnel identifier and the identifier of the second terminal user, that is, the service data in the service data tunnel is for transferring, and needs to be transferred to the second terminal, and of course, can also be simultaneously sent to the first terminal.

6) The service data quality of service flow identifier QFI and the transfer instruction, that is, the service data corresponding to the QFI is the transfer application, and needs to be transferred to the second terminal, and of course, can also be simultaneously sent to the first terminal.

7) The service data quality of service flow identifier QFI and the identifier of the second terminal user, that is, the service data corresponding to the QFI is the transfer application, and needs to be transferred to the second terminal, and of course, can also be simultaneously sent to the first terminal.

8) The service data service quality flow identifier QFI and the identifier of the second terminal, that is, the service data corresponding to the QFI is a transfer application and needs to be transferred to the second terminal, and of course, the service data service quality flow identifier QFI and the identifier of the second terminal can also be simultaneously sent to the first terminal.

9) The service data tunnel identifier and the identifier of the first terminal user, for example, the service data in the service data tunnel is directly sent to the first terminal without transferring.

10 The service data tunnel identifier and the identifier of the first terminal, for example, the service data in the service data tunnel is directly sent to the first terminal without transferring.

11 The service data corresponding to the QFI is directly transmitted to the first terminal without transferring, for example.

12 The service data corresponding to the QFI is directly transmitted to the first terminal without transferring, for example.

In the embodiment of the application, the access network side equipment receives the transfer relation from the core network and forwards the service data to the second terminal or the second terminal and the first terminal according to the transfer relation. The embodiment of the application provides an effective solution for service transfer, and is convenient for meeting the increasing service transfer demands.

Optionally, as an embodiment, the method further includes: receiving transfer information from the second terminal; wherein the transfer information includes at least one of: the method comprises the steps of identifying a first terminal user, identifying the first terminal, serving a core network function identifier of the first terminal user, transferring an instruction, identifying a second terminal user and identifying the second terminal.

Optionally, as an embodiment, forwarding the service data to the second terminal or the second terminal and the first terminal according to the transfer relationship includes: and forwarding service data to the second terminal or the second terminal and the first terminal according to the transfer relation and the transfer information.

Optionally, as an embodiment, the method further includes: receiving a transfer key from the core network; protecting at least one of the following based on the transfer key: interactive process signaling with the second terminal; traffic data from or to the second terminal.

Fig. 8 is a schematic flow chart of a service transfer method according to an embodiment of the present application, which may be applied to a second core network function (such as SMF). As shown in fig. 8, the method 800 includes:

S802: transfer information from a first core network function is received.

S804: and sending a transfer relation to access network side equipment through the first core network function, wherein the transfer relation is used for forwarding service data to a second terminal or the second terminal and the first terminal by the access network equipment.

In the embodiment of the application, the second core network function receives the transfer information from the first core network function, and sends the transfer relation to the access network side device through the first core network function, so that the access network side device can forward the service data to the second terminal or the second terminal and the first terminal according to the transfer information and the transfer relation. The embodiment of the application provides an effective solution for service transfer, and is convenient for meeting the increasing service transfer demands.

Optionally, as an embodiment, the transfer information includes at least one of: the method comprises the steps of identifying a first terminal user, identifying a first terminal, serving a core network function identifier of the first terminal user, transferring an instruction, identifying a second terminal user and identifying the second terminal; and/or; the transfer relationship comprises at least one of: the method comprises the steps of transferring a service data tunnel identifier QFI of the service, transferring a service data service quality stream identifier QFI of the service, transferring a service data tunnel identifier and a transfer instruction, identifying a service data tunnel identifier and a second terminal, identifying a service data service quality stream identifier QFI and a transfer instruction, identifying a service data service quality stream identifier QFI and a second terminal, identifying a service data tunnel identifier and a first terminal user, identifying a service data tunnel identifier and a first terminal, identifying a service data service quality stream identifier QFI and a first terminal user, and identifying a service data service quality stream identifier QFI and a first terminal.

Optionally, as an embodiment, the method further includes: transmitting transfer indication information to a third core network function, such as a subscriber port function (User Port Function, UPF), the transfer indication information being used to indicate transfer traffic data to be transmitted by at least one of:

a service data tunnel for transferring the service;

transferring the service data service quality flow of the service;

a traffic data tunnel associated with the transfer indication;

a traffic data quality of service flow associated with the transfer indication;

a traffic data tunnel associated with the identity of the second end user;

a quality of service stream of business data associated with the identity of the second end user;

a traffic data tunnel associated with the identity of the second terminal;

a traffic data quality of service stream associated with the identity of the second terminal;

a traffic data tunnel independent of the identity of the first end user;

a quality of service stream of traffic data independent of the identity of the first end user;

a traffic data tunnel independent of the identity of the first terminal;

and the service data service quality stream is irrelevant to the identification of the first terminal.

Fig. 9 is a schematic structural diagram of a second terminal 900 according to an embodiment of the present application, and as shown in fig. 9, the second terminal 900 includes:

A sending module 902, configured to send a non-access stratum NAS message to a core network, where the NAS message is used to request to establish, modify, or activate a protocol data unit PDU session of a first end user.

Optionally, as an embodiment, the second terminal 900 further comprises a receiving module, which may be used for receiving at least one of the following from the first terminal: the NAS message, a first key, cell information and service information to be transferred.

Optionally, as an embodiment, the second terminal 900 further includes a processing module, which may be used for at least one of: signaling of access stratum, AS, related processes is protected based on the first key or a second key generated based on the first key; signaling of NAS related procedures is protected based on the first key or a third key generated based on the first key.

Optionally, as an embodiment, the sending module 902 may be further configured to at least one of: transmitting a transfer instruction to the core network; and sending the identification of the second terminal user or the identification of the second terminal to the core network.

Optionally, as an embodiment, the sending module 902 may be further configured to send at least one of the following to an access network device: the method comprises the steps of identifying a first terminal user, identifying a first terminal, serving a core network function identifier of the first terminal user, transferring an instruction, identifying a second terminal user and identifying the second terminal.

Optionally, as an embodiment, the core network function serving the first end user identifies a core network function for the access network side device to route the NAS message to serve the first end user.

Optionally, as an embodiment, the service information to be transferred includes at least one of the following: application information of the service, current cookie information of the service, PDU session ID of the bearing service, QFI of the bearing service, message filter information of service data, identification of the first terminal user and identification of the first terminal.

The second terminal 900 according to the embodiment of the present application may refer to the flow of the method 200 corresponding to the embodiment of the present application, and each unit/module in the second terminal 900 and the other operations and/or functions described above are respectively for implementing the corresponding flow in the method 200, and may achieve the same or equivalent technical effects, which are not described herein for brevity.

Fig. 10 is a schematic structural diagram of a first core network function 1000 according to an embodiment of the present application, and as shown in fig. 10, the first core network function 1000 includes:

a receiving module 1002, configured to receive a NAS message sent by a second terminal, where the NAS message is used to request establishment, modification, or activation of a PDU session of a first end user;

a sending module 1004, configured to send transfer information to the second core network function.

Optionally, as an embodiment, the sending module 1004 may be further configured to: and sending an identification to the second terminal, wherein the identification is used for identifying the second terminal or the second terminal user. The identity in this embodiment may be a newly allocated identity for the second terminal or the second terminal user.

Optionally, as an embodiment, the receiving module 1002 may be further configured to: receiving a transfer instruction sent by the second terminal, and processing the NAS message based on a first key or a third key; wherein the first key is generated based on a key shared with the first end user; or, the first key is generated based on the identification of the second end user and a key shared with the first end user; or, the first key is generated based on the identification of the second terminal and a key shared with the first terminal user; the third key is generated based on the first key. The identifier of the second end user in this embodiment may be the newly allocated identifier or the original identifier of the second end user.

Optionally, AS an embodiment, the sending module 1004 may be further configured to send the first key or the second key to an access network side device, where the signaling is used to protect an access stratum AS related process; wherein the second key is generated based on the first key.

Optionally, as an embodiment, the sending module 1004 is configured to send transfer information to the second core network function according to at least one of:

2) Subscription information of the second terminal user;

3) An indication of the core network function from the serving second end user.

1) The PDU session type corresponding to the PDU session identification ID;

2) Subscription information of the first terminal user.

The first core network function 1000 according to the embodiments of the present application may refer to the flow of the method 500 corresponding to the embodiments of the present application, and each unit/module in the first core network function 1000 and the other operations and/or functions described above are respectively for implementing the corresponding flow in the method 500, and can achieve the same or equivalent technical effects, which are not described herein for brevity.

Fig. 11 is a schematic structural diagram of a first terminal 1100 according to an embodiment of the present application, and as shown in fig. 11, the first terminal 1100 includes:

a sending module 1102, configured to send service information to be transferred to a second terminal;

the service information to be transferred is used for the second terminal to send NAS information to the core network, and the NAS information is used for requesting to establish, modify or activate the PDU session of the first terminal user.

Optionally, as an embodiment, the sending module 1102 may be further configured to send at least one of the following to the second terminal: the first key, cell information, the NAS message.

Optionally, as an embodiment, the first terminal 1100 further includes a key generating module, configured to:

generating the first key based on a key shared by the first terminal and the core network; or (b)

Generating the first key based on the identification of the second terminal and a key shared by the first terminal and the core network; or (b)

The first key is generated based on the identity of the second terminal user and a key shared by the first terminal and the core network.

Optionally, as an embodiment, the service information to be transferred includes at least one of the following:

application information of the service, current cookie information of the service, PDU session ID of the bearing service, QFI of the bearing service, message filter information of service data, identification of the first terminal user, and identification of the first terminal.

The first terminal 1100 according to the embodiment of the present application may refer to the flow of the method 600 corresponding to the embodiment of the present application, and each unit/module in the first terminal 1100 and the other operations and/or functions described above are respectively for implementing the corresponding flow in the method 600, and may achieve the same or equivalent technical effects, which are not described herein for brevity.

Fig. 12 is a schematic structural diagram of an access network side device 1200 according to an embodiment of the present application, and as shown in fig. 12, the access network side device 1200 includes:

a receiving module 1202, configured to receive a transfer relationship from a core network;

a sending module 1204, configured to forward the service data to the second terminal, or the second terminal and the first terminal, according to the transfer relationship;

wherein the transfer relationship comprises at least one of: the method comprises the steps of transferring a service data tunnel identifier QFI of the service, transferring a service data service quality stream identifier QFI of the service, transferring a service data tunnel identifier and a transfer instruction, identifying a service data tunnel identifier and a second terminal, identifying a service data service quality stream identifier QFI and a transfer instruction, identifying a service data service quality stream identifier QFI and a second terminal, identifying a service data tunnel identifier and a first terminal user, identifying a service data tunnel identifier and a first terminal, identifying a service data service quality stream identifier QFI and a first terminal user, and identifying a service data service quality stream identifier QFI and a first terminal.

Optionally, as an embodiment, the receiving module 1202 may be further configured to receive transfer information from the second terminal; wherein the transfer information includes at least one of: the method comprises the steps of identifying a first terminal user, identifying the first terminal, serving a core network function identifier of the first terminal user, transferring an instruction, identifying a second terminal user and identifying the second terminal.

Optionally, as an embodiment, the sending module 1204 may be configured to forward service data to the second terminal, or the second terminal and the first terminal, according to the transfer relationship and the transfer information.

Optionally, as an embodiment, the receiving module 1202 may be further configured to receive a transfer key from the core network; protecting at least one of the following based on the transfer key: interactive process signaling with the second terminal; traffic data from or to the second terminal.

The access network side device 1200 according to the embodiment of the present application may refer to the flow of the method 700 corresponding to the embodiment of the present application, and each unit/module in the access network side device 1200 and the other operations and/or functions described above are respectively for implementing the corresponding flow in the method 700, and may achieve the same or equivalent technical effects, which are not described herein for brevity.

Fig. 13 is a schematic structural diagram of a second core network function 1300 according to an embodiment of the present application, and as shown in fig. 13, the second core network function 1300 includes:

a receiving module 1302, configured to receive transfer information from a first core network function;

a sending module 1304, configured to send, by using the first core network function, a transfer relationship to an access network side device, where the transfer relationship is used for forwarding, by using the access network device, service data to a second terminal, or the second terminal and the first terminal.

Optionally, as an embodiment, the sending module 1304 may be further configured to send transfer instruction information to a third core network function, such as a user port function (User Port Function, UPF), where the transfer instruction information is used to instruct transfer service data to be sent by at least one of the following manners:

A service data tunnel for transferring the service;

transferring the service data service quality flow of the service;

a traffic data tunnel associated with the transfer indication;

a traffic data quality of service flow associated with the transfer indication;

a traffic data tunnel associated with the identity of the second end user;

a traffic data tunnel associated with the identity of the second terminal;

a traffic data tunnel independent of the identity of the first end user;

a traffic data tunnel independent of the identity of the first terminal;

The second core network function 1300 according to the embodiment of the present application may refer to the flow of the method 800 corresponding to the embodiment of the present application, and each unit/module in the second core network function 1300 and the other operations and/or functions described above are respectively for implementing the corresponding flow in the method 800, and can achieve the same or equivalent technical effects, which are not described herein for brevity.

The terminal (e.g., the first terminal or the second terminal) in the embodiments of the present application may be a device, or may be a component, an integrated circuit, or a chip in the terminal. The device may be a mobile terminal or a non-mobile terminal. By way of example, mobile terminals may include, but are not limited to, the types of terminals 11 listed above, and non-mobile terminals may be servers, network attached storage (Network Attached Storage, NAS), personal computers (personal computer, PCs), televisions (TVs), teller machines, self-service machines, etc., and embodiments of the present application are not limited in detail.

The terminal in the embodiment of the application may be a device with an operating system. The operating system may be an Android operating system, an ios operating system, or other possible operating systems, which are not specifically limited in the embodiments of the present application.

The terminal provided in this embodiment of the present application can implement each process implemented in the embodiments of the methods of fig. 2 to fig. 4, or fig. 6, and achieve the same technical effects, so that repetition is avoided, and no further description is given here.

Optionally, as shown in fig. 14, the embodiment of the present application further provides a communication device 1400, including a processor 1401, a memory 1402, and a program or an instruction stored in the memory 1402 and capable of being executed on the processor 1401, where, for example, the communication device 1400 is a terminal (e.g., a first terminal or a second terminal), the program or the instruction implements each process of the foregoing service transfer method embodiment when executed by the processor 1401, and can achieve the same technical effect. When the communication device 1400 is a network side device (such as an access network side device, a first core network function, a second core network function, etc.), the program or the instruction when executed by the processor 1401 implements each process of the above-mentioned service transfer method embodiment, and the same technical effects can be achieved, so that repetition is avoided, and no description is repeated here.

Fig. 15 is a schematic hardware structure of a terminal for implementing an embodiment of the present application.

The terminal 1500 includes, but is not limited to: radio frequency unit 1501, network module 1502, audio output unit 1503, input unit 1504, sensor 1505, display unit 1506, user input unit 1507, interface unit 1508, memory 1509, and processor 1510.

Those skilled in the art will appreciate that the terminal 1500 may further include a power source (e.g., a battery) for powering the various components, and the power source may be logically connected to the processor 1510 via a power management system so as to perform functions such as managing charging, discharging, and power consumption via the power management system. The terminal structure shown in fig. 15 does not constitute a limitation of the terminal, and the terminal may include more or less components than shown, or may combine some components, or may be arranged in different components, which will not be described in detail herein.

It should be appreciated that in embodiments of the present application, the input unit 1504 may include a graphics processor (Graphics Processing Unit, GPU) 15041 and a microphone 15042, the graphics processor 15041 processing image data of still pictures or video obtained by an image capturing device (e.g., a camera) in a video capturing mode or an image capturing mode. The display unit 1506 may include a display panel 15061, and the display panel 15061 may be configured in the form of a liquid crystal display, an organic light emitting diode, or the like. The user input unit 1507 includes a touch panel 15071 and other input devices 15072. The touch panel 15071 is also referred to as a touch screen. The touch panel 15071 may include two parts, a touch detection device and a touch controller. Other input devices 15072 may include, but are not limited to, a physical keyboard, function keys (e.g., volume control keys, switch keys, etc.), a trackball, a mouse, a joystick, and so forth, which are not described in detail herein.

In this embodiment, after receiving downlink data from a network side device, the radio frequency unit 1501 processes the downlink data with the processor 1510; in addition, the uplink data is sent to the network side equipment. Typically, the radio frequency unit 1501 includes, but is not limited to, an antenna, at least one amplifier, a transceiver, a coupler, a low noise amplifier, a duplexer, and the like.

The memory 1509 may be used to store software programs or instructions and various data. The memory 1509 may mainly include a storage program or instruction region and a storage data region, wherein the storage program or instruction region may store an operating system, an application program or instruction (such as a sound playing function, an image playing function, etc.) required for at least one function, and the like. In addition, the Memory 1509 may include a high-speed random access Memory, and may also include a nonvolatile Memory, wherein the nonvolatile Memory may be a Read-Only Memory (ROM), a Programmable ROM (PROM), an Erasable PROM (EPROM), an Electrically Erasable EPROM (EEPROM), or a flash Memory. Such as at least one magnetic disk storage device, flash memory device, or other non-volatile solid-state storage device.

The processor 1510 may include one or more processing units; alternatively, the processor 1510 may integrate an application processor that primarily processes operating systems, user interfaces, and applications or instructions, etc., with a modem processor that primarily processes wireless communications, such as a baseband processor. It will be appreciated that the modem processor described above may not be integrated into the processor 1510.

Wherein, when the terminal 1500 is the second terminal in the foregoing embodiment, the radio frequency unit 1501 is configured to send a non-access stratum NAS message to the core network, where the NAS message is used to request to establish, modify or activate a protocol data unit PDU session of the first terminal user.

When the terminal 1500 is the first terminal in the foregoing embodiment, the radio frequency unit 1501 is configured to send service information to be transferred to the second terminal; the service information to be transferred is used for the second terminal to send NAS information to the core network, and the NAS information is used for requesting to establish, modify or activate the PDU session of the first terminal user.

The terminal 1500 provided in this embodiment of the present application may further implement each process of the foregoing service transfer method embodiment, and may achieve the same technical effects, so that repetition is avoided and no further description is given here.

Specifically, the embodiment of the application also provides network side equipment. The network side device may be an access network side device, a first core network function, a second core network function, or the like in the foregoing embodiment. As shown in fig. 16, the network device 1600 includes: an antenna 161, a radio frequency device 162, a baseband device 163. The antenna 161 is connected to a radio frequency device 162. In the uplink direction, the radio frequency device 162 receives information via the antenna 161, and transmits the received information to the baseband device 163 for processing. In the downstream direction, the baseband device 163 processes the information to be transmitted, and transmits the processed information to the radio frequency device 162, and the radio frequency device 162 processes the received information and transmits the processed information through the antenna 161.

The above-described band processing means may be located in the baseband apparatus 163, and the method performed by the network-side device in the above embodiment may be implemented in the baseband apparatus 163, the baseband apparatus 163 including the processor 164 and the memory 165.

The baseband apparatus 163 may, for example, comprise at least one baseband board on which a plurality of chips are disposed, as shown in fig. 16, where one chip, for example, a processor 164, is connected to the memory 165 to invoke a program in the memory 165 to perform the network device operations shown in the above method embodiment.

The baseband device 163 may also include a network interface 166, such as a common public radio interface (common public radio interface, CPRI for short), for interacting with the radio frequency device 162.

Specifically, the network side device of the embodiment of the present invention further includes: instructions or programs stored in the memory 165 and executable on the processor 164, the processor 164 invokes the instructions or programs in the memory 165 to perform the method performed by the modules shown in fig. 10 and fig. 13 of fig. 12, and achieve the same technical effects, and are not repeated here.

The embodiment of the present application further provides a readable storage medium, where a program or an instruction is stored on the readable storage medium, and when the program or the instruction is executed by a processor, the program or the instruction realizes each process of the above embodiment of the service transfer method, and the same technical effects can be achieved, so that repetition is avoided, and no description is repeated here.

The processor may be a processor in the terminal described in the above embodiment. The readable storage medium includes a computer readable storage medium such as a Read-Only Memory (ROM), a random access Memory (Random Access Memory, RAM), a magnetic disk or an optical disk, and the like.

The embodiment of the application further provides a chip, the chip includes a processor and a communication interface, the communication interface is coupled with the processor, and the processor is used for running a program or an instruction, so as to implement each process of the above service transfer method embodiment, and achieve the same technical effect, so that repetition is avoided, and no redundant description is provided here.

It should be understood that the chips referred to in the embodiments of the present application may also be referred to as system-on-chip chips, or the like.

It should be noted that, in this document, the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising one … …" does not exclude the presence of other like elements in a process, method, article, or apparatus that comprises the element. Furthermore, it should be noted that the scope of the methods and apparatus in the embodiments of the present application is not limited to performing the functions in the order shown or discussed, but may also include performing the functions in a substantially simultaneous manner or in an opposite order depending on the functions involved, e.g., the described methods may be performed in an order different from that described, and various steps may also be added, omitted, or combined. Additionally, features described with reference to certain examples may be combined in other examples.

From the above description of the embodiments, it will be clear to those skilled in the art that the above-described embodiment method may be implemented by means of software plus a necessary general hardware platform, but of course may also be implemented by means of hardware, but in many cases the former is a preferred embodiment. Based on such understanding, the technical solution of the present application may be embodied essentially or in a part contributing to the prior art in the form of a software product stored in a storage medium (such as ROM/RAM, magnetic disk, optical disk), including several instructions for causing a terminal (which may be a mobile phone, a computer, a server, an air conditioner, or a network device, etc.) to perform the method described in the embodiments of the present application.

The embodiments of the present application have been described above with reference to the accompanying drawings, but the present application is not limited to the above-described embodiments, which are merely illustrative and not restrictive, and many forms may be made by those of ordinary skill in the art without departing from the spirit of the present application and the scope of the claims, which are also within the protection of the present application.

Claims

1. A method of traffic transfer, the method being performed by a second terminal, the method comprising:

at least one of the following is received: NAS message, first secret key, cell information and service information to be transferred;

sending a non-access stratum (NAS) message to a core network, wherein the NAS message is used for requesting to establish, modify or activate a Protocol Data Unit (PDU) session of a first terminal user;

wherein the NAS message includes at least one of:

the first terminal user identifier, the first terminal identifier, the PDU session identifier ID, the QFI service quality stream identifier and the message filter information.

2. The method of claim 1, wherein the receiving at least one of: NAS message, first secret key, cell information, service information to be transferred, comprising:

receiving at least one of the following from the first terminal: the NAS message, a first key, cell information and service information to be transferred.

3. The method according to claim 2, characterized in that the cell information is used for the second terminal to select an access network side device.

4. The method of claim 2, wherein after the receiving the first key from the first terminal, the method further comprises at least one of:

Signaling of access stratum, AS, related processes is protected based on the first key or a second key generated based on the first key;

signaling of NAS related procedures is protected based on the first key or a third key generated based on the first key.

5. The method of claim 1, further comprising at least one of:

transmitting a transfer instruction to the core network;

and sending the identification of the second terminal user or the identification of the second terminal to the core network.

6. The method according to claim 1, wherein the method further comprises: transmitting at least one of the following to the access network side device:

the method comprises the steps of identifying a first terminal user, identifying a first terminal, serving a core network function identifier of the first terminal user, transferring an instruction, identifying a second terminal user and identifying the second terminal.

7. The method of claim 6, wherein the core network function serving the first end user identifies a core network function for the access network side device to route the NAS message to serve the first end user.

8. The method of claim 2, wherein the traffic information to be transferred comprises at least one of:

The method comprises the steps of service application information, service current cookie information, PDU session ID bearing service, QFI bearing service, message filter information of service data, identification of a first terminal user and identification of a first terminal.

9. A method of traffic transfer, the method performed by a first core network function, the method comprising:

receiving NAS information sent by a second terminal, wherein the NAS information is used for requesting to establish, modify or activate a PDU session of a first terminal user;

transmitting transfer information to a second core network function;

the NAS message includes at least one of:

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

and sending an identification to the second terminal, wherein the identification is used for identifying the second terminal or the second terminal user.

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

receiving a transfer instruction sent by the second terminal, and processing the NAS message based on a first key or a third key;

Wherein the first key is generated based on a key shared with the first end user; or, the first key is generated based on the identification of the second end user and a key shared with the first end user; or, the first key is generated based on the identification of the second terminal and a key shared with the first terminal user;

the third key is generated based on the first key.

12. The method of claim 11, wherein the method further comprises:

the first key or the second key is sent to the access network side equipment and used for protecting the signaling of the AS related process of the access layer;

wherein the second key is generated based on the first key.

13. The method of claim 9, wherein the sending the transfer information to the second core network function comprises:

transmitting transfer information to the second core network function according to at least one of:

the access network side equipment from which the NAS message comes is the same as the access network side equipment in which the first terminal is positioned;

subscription information of the second terminal user;

an indication of the core network function from the serving second end user.

14. The method of claim 13, wherein the sending the transfer information to the second core network function comprises:

the PDU session type corresponding to the PDU session identification ID;

subscription information of the first terminal user.

15. The method of claim 9, wherein the transfer information comprises at least one of:

PDU session identity ID, quality of service flow identity QFI, message filter information, transfer indication.

16. A method of traffic transfer, the method being performed by a first terminal, the method comprising:

transmitting service information to be transferred to a second terminal;

the service information to be transferred is used for the second terminal to send NAS information to a core network, and the NAS information is used for requesting to establish, modify or activate PDU session of the first terminal user;

the NAS message includes at least one of:

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

Transmitting to the second terminal at least one of: the first key, cell information, the NAS message.

18. The method according to claim 17, wherein the cell information is used for the second terminal to select an access network side device.

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

20. The method of claim 16, wherein the traffic information to be transferred comprises at least one of:

the method comprises the steps of service application information, service current cookie information, PDU session ID bearing service, QFI bearing service, message filter information of service data, identification of a first terminal user and identification of the first terminal.

21. A second terminal, comprising:

A transmitting module, configured to receive at least one of: NAS information, a first key, cell information and service information to be transferred, wherein the NAS information is used for requesting to establish, modify or activate a protocol data unit PDU session of a first terminal user;

wherein the NAS message includes at least one of:

22. A first core network function, comprising:

the receiving module is used for receiving an NAS message sent by the second terminal, wherein the NAS message is used for requesting to establish, modify or activate the PDU session of the first terminal user;

the sending module is used for sending transfer information to the second core network function;

wherein the NAS message includes at least one of:

23. A first terminal, comprising:

the sending module is used for sending the service information to be transferred to the second terminal;

The NAS message includes at least one of:

24. A terminal comprising a processor, a memory and a program or instruction stored on the memory and executable on the processor, which when executed by the processor implements the traffic diversion method of any one of claims 1 to 8 or implements the traffic diversion method of any one of claims 16 to 20.

25. A network side device comprising a processor, a memory and a program or instruction stored on the memory and executable on the processor, which when executed by the processor implements the traffic transfer method according to any of claims 9 to 15.

26. A readable storage medium, characterized in that the readable storage medium has stored thereon a program or instructions which, when executed by a processor, implements the service transfer method according to any of claims 1 to 20.