CN114501490A

CN114501490A - Service transfer method, terminal and network side equipment

Info

Publication number: CN114501490A
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: 2022-05-13
Anticipated expiration: 2040-11-13
Also published as: WO2022100544A1; CN114501490B

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: 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.

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 demand of users for service transfer between terminals is more and more obvious. A typical traffic shifting application requirement includes: when the mobile phone receives an IMS call request, the user wants to not ring the incoming call in response, but request the intelligent watch to divide the user plane of the telephone service into the intelligent watch and then ring the user plane to answer. However, the related art does not provide a related scheme for service transfer, and cannot meet the increasing demand for service transfer.

Disclosure of Invention

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

In a first aspect, a method for service transfer is provided, where the method is performed by a second terminal, and the method includes: and 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 the first terminal user.

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

In a third aspect, a method for service transfer is provided, where the method is performed by a first terminal, and the method includes: sending service information to be transferred to a second terminal; and the service information to be transferred is used for the second terminal to send NAS information to a core network, wherein 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 method for service transfer 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 relationship; wherein the transfer relationship comprises at least one of: the method comprises the steps of service data tunnel identification of a transfer service, service data quality of service flow identification QFI of the transfer service, service data tunnel identification and transfer indication, service data tunnel identification and identification of a second terminal user, service data tunnel identification and identification of a second terminal, service data quality of service flow identification QFI and transfer indication, service data quality of service flow identification QFI and identification of the second terminal user, service data quality of service flow identification QFI and identification of the second terminal, service data tunnel identification and identification of a first terminal user, service data tunnel identification and identification of a first terminal, service data quality of service flow identification QFI and identification of the first terminal user, and service data quality of service flow identification QFI and identification of the first terminal.

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

In a sixth aspect, there is provided a second terminal comprising: a sending module, 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 terminal user.

A seventh aspect provides a first core network function, 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 a PDU session of a first terminal user; and the sending module is used for sending the transfer information to the second core network function.

In an eighth aspect, there is provided a first terminal comprising: the sending module is used for sending the service information to be transferred to the second terminal; and the service information to be transferred is used for the second terminal to send NAS information to a core network, wherein the NAS information is used for requesting to establish, modify or activate the PDU session of the first terminal user.

In a ninth aspect, an access network side device is provided, which includes: a receiving module, configured to receive a transfer relationship from a core network; a sending module, 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 service data tunnel identification of a transfer service, service data quality of service flow identification QFI of the transfer service, service data tunnel identification and transfer indication, service data tunnel identification and identification of a second terminal user, service data tunnel identification and identification of a second terminal, service data quality of service flow identification QFI and transfer indication, service data quality of service flow identification QFI and identification of the second terminal user, service data quality of service flow identification QFI and identification of the second terminal, service data tunnel identification and identification of a first terminal user, service data tunnel identification and identification of a first terminal, service data quality of service flow identification QFI and identification of the first terminal user, and service data quality of service flow identification QFI and identification of the first terminal.

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

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

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

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

In a fourteenth aspect, a computer program product is provided, which comprises a processor, a memory, and a program or instructions stored on the memory and executable on the processor, which when executed by the processor, implements the method according to any one of the first to fifth aspects.

In a fifteenth aspect, a chip is provided, the chip comprising a processor and a communication interface, the communication interface being coupled to the processor, the processor being configured to execute a program or instructions to implement the method according to any one 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 with 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 traffic shifting method according to one embodiment of the present application;

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

FIG. 4 is a schematic flow chart diagram of a traffic shifting method in accordance with a specific embodiment of the present application;

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

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

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

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

FIG. 9 is a schematic diagram of a second terminal according to one 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 diagram of a first terminal according to one 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 block diagram of a communication device according to one embodiment of the present application;

FIG. 15 is a block diagram of a terminal according to one 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

The technical solutions in the embodiments of the present application will be described clearly below with reference to the drawings in the embodiments of the present application, and it is obvious that the described embodiments are some, but not all, embodiments of the present application. All other embodiments that can be derived from the embodiments given herein by a person of ordinary skill in the art are intended to be within the scope of the present disclosure.

The terms first, second and the like in the description and in the claims of the present application are used for distinguishing between similar elements and not necessarily for describing a particular sequential or chronological order. It should be understood that the data so used are interchangeable under appropriate circumstances such that embodiments of the application can be practiced in sequences other than those illustrated or described herein, and the terms "first" and "second" used herein generally do not denote any order, nor do they denote any order, for example, the first object may be one or more. In addition, "and/or" in the specification and the claims means at least one of connected objects, and a character "/" generally means that a preceding and succeeding related objects are in an "or" relationship.

It is noted that the techniques described in the embodiments of the present application are not limited to Long Term Evolution (LTE)/LTE Evolution (LTE-Advanced) systems, but may also be used in other wireless communication systems, such as Code Division Multiple Access (CDMA), Time Division Multiple Access (TDMA), Frequency Division Multiple Access (FDMA), Orthogonal Frequency Division Multiple Access (OFDMA), Single-carrier Frequency-Division Multiple Access (SC-FDMA), and other systems. The term "system" in the embodiments of the present application "And "network" are often used interchangeably, the described techniques are applicable to both the above-mentioned systems and radio technologies, as well as to other systems and radio technologies. The following description describes a New Radio (NR) system for purposes of example, and NR terminology is used in much of the description below, but the techniques may also be applied to applications other than NR system applications, such as generation 6 (6)^thGeneration, 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-side device 12. Wherein, the terminal 11 may also be called as a terminal Device or a User Equipment (UE), the terminal 11 may be a Mobile phone, a Tablet Personal Computer (Tablet Personal Computer), a Laptop Computer (Laptop Computer) or a notebook Computer, a Personal Digital Assistant (PDA), a palmtop Computer, a netbook, a super-Mobile Personal Computer (UMPC), a Mobile Internet Device (MID), a Wearable Device (Wearable Device) or a vehicle-mounted Device (VUE), a pedestrian terminal (PUE), and other terminal side devices, the Wearable Device includes: bracelets, earphones, glasses and the like. It should be noted that the embodiment of the present application does not limit the specific type of the terminal 11. The network-side device 12 may be a Base Station or a core network, wherein the Base Station may be referred to as a node B, an evolved node B, an access Point, a Base Transceiver Station (BTS), a radio Base Station, a radio Transceiver, a Basic Service Set (BSS), an 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 (hbo), a WLAN access Point, a WiFi node, a Transmission Receiving Point (TRP), or some other suitable terminology in the field, as long as the same technical effect is achieved, 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, an embodiment of the present application provides a service transfer method 200, which may be performed by the second terminal, in other words, the method may be performed by software or hardware installed in the second terminal, and the method includes the following steps.

S202: sending a Non-Access Stratum (NAS) message to a core network, the NAS message requesting establishment, modification or activation of a Protocol Data Unit (PDU) session of a first end user.

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

The NAS message in this embodiment may be from the first terminal, and thus, before S202, the second terminal may further receive the NAS message from the first terminal. For example, the first terminal and the second terminal interact through a near field communication manner, for example, using a Sidelink (Sidelink) or a 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, a first terminal and a 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. Similarly, the above explanation also applies to the second terminal and the second terminal user.

Optionally, the NAS message includes at least one of: the identifier of the first terminal user, the identifier of the first terminal, the PDU session Identifier (ID), the 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 is equivalent to request 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 (e.g., an access network side device such as a base station) can distinguish the target of service data transmission according to the PDU session ID and the like.

In one example, as shown in fig. 3, the PDU session of the first end-user (i.e., the PDU session established, modified, or activated in S202) has QFI groups nested therein, each of which may include one or more QFIs. In fig. 3, the base station (gNB) may directly transmit the traffic data corresponding to the QFI group 1 to the first terminal (UE1), transfer the traffic data corresponding to the QFI group 2 to the second terminal (UE2), or simultaneously transmit the traffic data to 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 requested to be established, modified or activated by the first end user itself, and the second PDU session is a PDU session requested to be established, modified or activated by the second end user in S202, so that the base station (gNB) may send the traffic data corresponding to the first PDU session directly to the first terminal (UE1), transfer the traffic data corresponding to the second PDU session to the second terminal (UE2), or send the traffic data 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 the 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, the first key, the cell information and the service information to be transferred.

The first key is used for the first terminal or the second terminal to generate a new key, so AS to protect the signaling of the access stratum AS related process or the signaling of the 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) and the second terminal protects the signaling of the related process of the Access Stratum (AS) 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. The signaling of the AS-related procedure includes, for example, an RRC Connection Establishment (RRC Connection Establishment) message and the like.

2) And the second terminal protects the signaling of the NAS related process 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.

The cell information is used for the second terminal to select an access network side device, which may be an access network side device providing 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 bearer service, QFI of the bearer service, message filter information of the service data, an identifier of the first terminal user, and an identifier of the first terminal.

Optionally, 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 correspond to a PDU session identifier, QFI, or packet filter information in the NAS message, and indicate that service data corresponding to the PDU session identifier, QFI, or packet filter information is for transfer and needs to be transferred to the second terminal.

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

Optionally, the foregoing embodiments may further include the steps of: the second terminal sends at least one of the following information to the access network side equipment: an identity of the first end user, an identity of the first terminal, an identity of a core network function serving the first end user (e.g., AMF1), a handover indication, an identity of the second end user, and an identity of the second terminal. And the core network function identifier serving the first terminal user is used for the access network side equipment to route NAS information to the core network function serving the first terminal user.

To describe the service transfer method provided in this embodiment in detail, a specific embodiment is described below, and as shown in fig. 4, this embodiment includes the following steps.

Step 1: a first terminal (UE1) registers in the network and through a registration procedure, transfer allowed terminal identification (allowed UE ID) information is obtained, possibly through a core network (e.g., AMF1), indicating which UEs can transfer the session of the UE 1.

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

Step 2: the UE1 and the second terminal (UE2) interact through close range communication, such as using the Sidelink or Wifi technology, and the UE1 sends the service information to be transferred to the UE 2.

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

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

And 3, step 3: optionally, the UE1 sends at least one of the following information to the 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 the UE2 together.

The NAS message is a message requesting 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 identity of the first end user (e.g., UE1 ID), an identity of the first terminal, an identity of the second end user (e.g., UE2 ID), a PDU session identity ID, a quality of service flow identity QFI, message filter information, and a transfer indication (IuT indication). The transfer indication indicates that a switchover operation needs to be performed.

The key 1 is derived based on 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 UE2ID or an ID corresponding to the UE2ID at the same time (i.e., derived based on the key shared by the UE1 and the core network and the UE2ID at the same time), and the UE2 may further derive a second key (key 2) used for the AS-related procedure and a third key (key 3) used for the NAS-related procedure, respectively, based on the key 1, for example, further derive based on the key 1 and the UE2 ID. If the UE1 has passed the key 1 to the UE2, it does not need to pass it, and if the UE2 has the key 2 or the key 3 (e.g., the UE1 sends to the UE2), the UE2 does not regenerate these keys.

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

And 4, step 4: the UE2 and the gNB interactively activate an air interface Connection, for example, the UE2 executes a random access process (e.g., two-step random access messages 1-2) and an RRC Connection Establishment (i.e., messages 3-5) process. In the air interface connection activation process, the UE2 sends at least one of the following information to the gNB: the identifier of the first terminal user (UE1 ID), the identifier of the first terminal, the core network function identifier (AMF1) serving the first terminal user, the transfer indication (IuT indication), the identifier of the second terminal user, and the identifier of the second terminal.

Step 5 can be divided into two cases:

in case 1, the UE2 transmits a NAS message to the AMF 1. Case 1 may be performed if UE2 sends UE1 ID to the gNB.

In case 2, the UE2 forwards the NAS message to the AMF1 through the AMF 2. Case 2 may be performed if the UE2 sends the AMF1 to the gNB.

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

In step 5, the UE2 requests from the core network (AMF1) to establish, modify or activate a PDU Session for the UE1, such as sending a NAS message like a Service Request (Service Request) or a PDU Session Establishment (PDU Session Establishment).

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

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

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

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

2) And a PDU session type corresponding to the PDU session ID, for example, whether the PDU session type is a transfer type.

3) Subscription information for the UE1, such as whether the UE1 allows the UE2 to transfer the session, or whether the UE2 is allowed to transfer the specified data stream.

4) The AMF1 may also request subscription information of the UE2 from the AMF2 or AUSF2 to which the UE2 belongs, and determine whether the UE2 can transfer the session of the UE1 or allow the UE2 to transfer a specified data flow of the UE1 according to the subscription information of the UE 2.

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

And 7: the AMF1 sends transition information to the SMF1, the transition information including at least one of:

the identifier (UE1 ID) of the first terminal user, the core network function identifier (AMF1) accessed by the first terminal user, the transfer indication, PDU Session ID, QFI, packet filter.

And 8: optionally, SMF1 interacts with User Port Function (UPF) 1 to indicate the QFI corresponding to the data stream corresponding to the packet filter. Specifically, reference may be made to the description of the first core network function side in the following embodiments.

And step 9: the SMF1 sends flow information to the gNB through the AMF1, where the flow information includes QFIs and the like, and may further include an IuT indicator for indicating which QFIs are for transfer purposes, that is, which QFIs to be transferred to the UE2, and which are not to be transferred and are directly sent to the UE 1.

Step 10: AMF1 receives information sent by SMF1 to the gNB, and forwards the information to the gNB, wherein the information comprises QFIs, and an IuT indicator for indicating that the QFIs are for transfer purpose.

AMF1 may also generate key 1 or key 2 using the same rule in step 3 and send key 1 or key 2 to the gNB. The AMF1 may also assign a new UE ID for UE2 and send 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 may be protected based on the key 1 or the key 2.

The gNB identifies from the QFI whether the data from the network is destined for the UE1 or is to be transferred to the UE 2.

The service transfer method according to the embodiment of the present application is described in detail above with reference to fig. 2 to 4. In the following, a service transfer method according to several other embodiments of the present application will be described in detail with reference to fig. 5 to 8. It is to be understood that the description of fig. 5 to 8 is the same as or corresponds to the partial description of the method shown in fig. 2 to 4, and the related description is appropriately omitted to avoid redundancy.

Fig. 5 is a schematic flow chart of an implementation of the service forwarding method according to the embodiment of the present application, which may be applied to a first core network function (e.g., 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 sending the transfer information to the second core network function.

The NAS message may be sent by the second terminal 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 with 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 identifier to the second terminal, wherein the identifier is used for identifying the second terminal or the second terminal user. The identifier in this embodiment may be an identifier newly allocated by the first core network function to the second terminal or the 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 identity of the second end user and a key shared with the first end user; or, the first key is generated based on the identifier 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 a newly allocated identifier or may be an original identifier of the second end user.

The transfer instruction in this embodiment may correspond to a PDU session identifier, QFI, or packet filter information in the NAS message, and indicate that service data corresponding to the PDU session identifier, QFI, or packet filter information is for transfer 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 (e.g., an 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: sending 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 where the first terminal is located;

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 from a core network function (e.g., AMF2) serving the second end user. The second core network function may determine, according to the 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 specified 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 identification of the first terminal user, the identification of the first terminal, the PDU session identification ID, the QFI and the message filter information.

1) the PDU session type corresponding to the PDU session identification ID; such as whether it is a branch type.

2) Subscription information of the first end 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 identification ID, QoS flow identification QFI, message filter information and transfer indication.

Fig. 6 is a schematic flow chart of an implementation 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 a PDU session of a first terminal user.

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

In the embodiment of the application, the first terminal sends the service information to be transferred to the second terminal, and the second terminal user requests the first core network function to establish, modify or activate the PDU session of the first terminal user by using 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: sending at least one of the following to the second terminal: a 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 identifier 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 an implementation of a service transfer method according to an embodiment of the present application, which may be applied to an access network side device (e.g., 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 or the second terminal and the first terminal according to the transfer relationship, namely, forwarding the service data to the second terminal while sending 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 use and needs to be transferred to the second terminal, and certainly, the service data tunnel identifier may also be sent to the first terminal at the same time.

2) The service data qos flow identifier QFI of the transfer service, that is, the service data corresponding to the QFI is for transfer use, and needs to be transferred to the second terminal, or certainly, may be sent to the first terminal at the same time.

3) The service data tunnel identifier and the transfer indication, that is, the service data in the service data tunnel is for transfer, and needs to be transferred to the second terminal, or certainly, may be sent to the first terminal at the same time.

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, or certainly, may be sent to the first terminal at the same time.

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 transfer, and needs to be transferred to the second terminal, or certainly, may be sent to the first terminal at the same time.

6) The service data qos flow identifier QFI and the forwarding indication, that is, the service data corresponding to the QFI is for forwarding use and needs to be forwarded to the second terminal, or certainly, may be sent to the first terminal at the same time.

7) The service data qos flow identifier QFI and the identifier of the second terminal user, that is, the service data corresponding to the QFI is for transfer, and needs to be transferred to the second terminal, or certainly, may be sent to the first terminal at the same time.

8) The service data qos flow identifier QFI and the identifier of the second terminal, that is, the service data corresponding to the QFI is for transfer, needs to be transferred to the second terminal, and certainly can also be sent to the first terminal at the same time.

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 quality of service flow identifier QFI and the identifier of the first terminal user, for example, the service data corresponding to the QFI is directly sent to the first terminal without transferring.

12) The service data quality of service flow identifier QFI and the identifier of the first terminal, for example, the service data corresponding to the QFI is directly sent to the first terminal without transferring.

In the embodiment of the application, the access network side device receives the transfer relationship 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 relationship. The embodiment of the application provides an effective solution for service transfer, and is convenient for meeting increasing service transfer requirements.

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

Optionally, as an embodiment, the forwarding, according to the transfer relationship, the service data to the second terminal, or the second terminal and the first terminal 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: signaling an interaction process with the second terminal; service data from or to the second terminal.

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

s802: transfer information from the first core network function is received.

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

In this embodiment, the second core network function receives the transfer information from the first core network function, and sends the transfer relationship 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 relationship. The embodiment of the application provides an effective solution for service transfer, and is convenient for meeting increasing service transfer requirements.

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

Optionally, as an embodiment, the method further includes: sending transfer indication information to a third core network Function, such as a User Port Function (UPF), where the transfer indication information is used to indicate that the transfer service data is sent in at least one of the following manners:

a service data tunnel for transferring a service;

transferring service data service quality flow of the service;

a traffic data tunnel associated with the transition indication;

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

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

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

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

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

a service data tunnel unrelated to the identity of the first end user;

a service data quality of service flow unrelated to the identity of the first end user;

a service data tunnel unrelated to the identity of the first terminal;

a traffic data quality of service flow independent of the identity 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 includes a receiving module, which may be configured to receive at least one of the following from the first terminal: the NAS message, the first key, the cell information and the service information to be transferred.

Optionally, as an embodiment, the second terminal 900 further includes a processing module, and may be configured to at least one of the following: protecting signaling of an Access Stratum (AS) related process based on the first key or a second key generated based on the first key; securing signaling of a NAS related procedure 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: sending a transfer indication to the core network; and sending the identifier of the second terminal user or the identifier of the second terminal to the core network.

Optionally, as an embodiment, the sending module 902 may be further configured to send, to the access network-side device, at least one of the following: the identifier of the first terminal user, the identifier of the first terminal, the core network function identifier serving the first terminal user, the transfer indication, the identifier of the second terminal user, and the identifier of the second terminal.

Optionally, as an embodiment, the core network function identifier serving the first end user is used by the access network side device to route the NAS message to the core network function serving the first end user.

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

The second terminal 900 according to the embodiment of the present application may refer to the flow corresponding to the method 200 of the embodiment of the present application, and each unit/module and the other operations and/or functions in the second terminal 900 are respectively for implementing the corresponding flow in the method 200 and can achieve the same or equivalent technical effects, and for brevity, no further description is provided here.

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 an NAS message sent by a second terminal, where the NAS message is used to request to establish, modify, or activate a PDU session of a first terminal user;

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

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

Optionally, as an embodiment, the receiving module 1002 may further be 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 identity of the second end user and a key shared with the first end user; or, the first key is generated based on the identifier 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 a newly allocated identifier or may be an 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 the access network side device, where the first key or the second key is used to protect a signaling of an AS-related procedure of an access stratum; wherein the second key is generated based on the first key.

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

2) subscription information of a second end user;

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

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

2) subscription information of the first end user.

The first core network function 1000 according to the embodiment of the present application may refer to the flow corresponding to the method 500 of the embodiment of the present application, and each unit/module and the other operations and/or functions in the first core network function 1000 are respectively for implementing the corresponding flow in the method 500 and can achieve the same or equivalent technical effects, and for brevity, no further description is provided herein.

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;

and the service information to be transferred is used for the second terminal to send NAS information to a core network, wherein 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, to the second terminal, at least one of the following: a first key, cell information, the NAS message.

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

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

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 identifier of the second terminal and a key shared by the first terminal and the core network; or

And generating the first key based on the identification 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:

the Application information of the service, the current cookie information of the service, the PDU session ID of the bearer service, the QFI of the bearer service, the message filter information of the service data, the identifier of the first terminal user, and the identifier of the first terminal.

The first terminal 1100 according to the embodiment of the present application may refer to the flow corresponding to the method 600 of the embodiment of the present application, and each unit/module and the other operations and/or functions in the first terminal 1100 are respectively for implementing the corresponding flow in the method 600 and achieving the same or equivalent technical effects, and for brevity, no further description is provided here.

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 service data tunnel identification of a transfer service, service data quality of service flow identification QFI of the transfer service, service data tunnel identification and transfer indication, service data tunnel identification and identification of a second terminal user, service data tunnel identification and identification of a second terminal, service data quality of service flow identification QFI and transfer indication, service data quality of service flow identification QFI and identification of the second terminal user, service data quality of service flow identification QFI and identification of the second terminal, service data tunnel identification and identification of a first terminal user, service data tunnel identification and identification of a first terminal, service data quality of service flow identification QFI and identification of the first terminal user, and service data quality of service flow identification QFI and identification of the 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 comprises at least one of: the identifier of the first terminal user, the identifier of the first terminal, the core network function identifier serving the first terminal user, the transfer instruction, the identifier of the second terminal user, and the identifier of 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: signaling an interaction process with the second terminal; service 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 corresponding to the method 700 according to the embodiment of the present application, and each unit/module and the other operations and/or functions in the access network-side device 1200 are respectively for implementing the corresponding flow in the method 700 and achieving the same or equivalent technical effects, and for brevity, no further description is provided here.

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 a transfer relationship to an access network side device through the first core network function, where the transfer relationship is used for the access network device to forward 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, to a third core network Function, such as a User Port Function (UPF), forwarding indication information, where the forwarding indication information is used to indicate that forwarding service data is sent by at least one of the following manners:

a service data tunnel for transferring a service;

transferring service data service quality flow of the service;

a traffic data tunnel associated with the transition indication;

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

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

a service data tunnel unrelated to the identity of the first end user;

a service data tunnel unrelated to the identity of the first terminal;

The second core network function 1300 according to the embodiment of the present application may refer to the process corresponding to the method 800 of the embodiment of the present application, and each unit/module and the other operations and/or functions in the second core network function 1300 are respectively for implementing the corresponding process in the method 800, and can achieve the same or equivalent technical effects, and for brevity, no further description is provided herein.

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 can be a mobile terminal or a non-mobile terminal. By way of example, the mobile terminal may include, but is not limited to, the above-listed type of terminal 11, and the non-mobile terminal may be a server, a Network Attached Storage (NAS), a Personal Computer (PC), a Television (TV), a teller machine, a kiosk, or the like, and the embodiments of the present application are not limited in particular.

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

The terminal provided in the embodiment of the present application can implement each process implemented by the method embodiments of fig. 2 to fig. 4 or fig. 6, and achieve the same technical effect, and is not described here again to avoid repetition.

Optionally, as shown in fig. 14, an embodiment of the present application further provides a communication device 1400, which includes a processor 1401, a memory 1402, and a program or an instruction stored in the memory 1402 and executable on the processor 1401, for example, when the communication device 1400 is a terminal (e.g., a first terminal or a second terminal), the program or the instruction is executed by the processor 1401 to implement the processes of the foregoing service migration method embodiment, and the same technical effect can be achieved. When the communication device 1400 is a network-side device (e.g., an access network-side device, a first core network function, a second core network function, etc.), when the program or the instruction is executed by the processor 1401, the processes of the service transfer method embodiment are implemented, and the same technical effect can be achieved.

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

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

Those skilled in the art will appreciate that the terminal 1500 may also include a power supply (e.g., a battery) for powering the various components, which may be logically coupled to the processor 1510 via a power management system to manage charging, discharging, and power consumption management functions 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 those shown, or combine some components, or have a different arrangement of components, and thus will not be described again.

It should be understood that in the embodiment of the present application, the input Unit 1504 may include a Graphics Processing Unit (GPU) 15041 and a microphone 15042, and the Graphics processor 15041 processes image data of still pictures or videos obtained by an image capturing device (such as 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. A touch panel 15071, also referred to as a touch screen. The touch panel 15071 may include two parts of 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, and a joystick, which are not described in detail herein.

In this embodiment, the radio frequency unit 1501 receives downlink data from a network side device and then processes the downlink data in the processor 1510; in addition, the uplink data is sent to the network side equipment. In general, 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 as well as various data. The memory 1509 may mainly include a stored program or instruction area and a stored data area, wherein the stored program or instruction area 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 further include a nonvolatile Memory, wherein the nonvolatile Memory may be a Read-Only Memory (ROM), a Programmable Read-Only Memory (PROM), an Erasable Programmable Read-Only Memory (EPROM), an Electrically Erasable Programmable Read-Only Memory (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.

Processor 1510 may include one or more processing units; optionally, the processor 1510 may integrate an application processor, which primarily handles operating system, user interface, and applications or instructions, etc., and a modem processor, which primarily handles 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 to-be-transferred service information to the second terminal; and the service information to be transferred is used for the second terminal to send NAS information to a core network, wherein 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 effect, and for avoiding repetition, details are not described here again.

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

The band processing means may be located in the baseband means 163, and the method performed by the network side device in the above embodiment may be implemented in the baseband means 163, where the baseband means 163 includes a processor 164 and a memory 165.

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

The baseband device 163 may further include a network interface 166, such as a Common Public Radio Interface (CPRI), for exchanging information with the radio frequency device 162.

Specifically, the network side device of the embodiment of the present invention further includes: the instructions or programs stored in the memory 165 and executable on the processor 164, and the processor 164 calls the instructions or programs in the memory 165 to execute the method executed by the modules shown in fig. 10, fig. 12 and fig. 13 to achieve the same technical effects, which are not described herein for avoiding repetition.

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 implements each process of the foregoing service transfer method embodiment, and can achieve the same technical effect, and in order to avoid repetition, details are not repeated here.

The processor may be the 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 (RAM), a magnetic disk or an optical disk, and so on.

The embodiment of the present application further provides a chip, where the chip includes a processor and a communication interface, the communication interface is coupled to the processor, and the processor is configured to execute a program or an instruction to implement each process of the foregoing service transfer method embodiment, and can achieve the same technical effect, and in order to avoid repetition, the details are not repeated here.

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

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 an … …" does not exclude the presence of other like elements in a process, method, article, or apparatus that comprises the element. Further, it should be noted that the scope of the methods and apparatuses in the embodiments of the present application is not limited to performing the functions in the order illustrated or discussed, but may include performing the functions in a substantially simultaneous manner or in a reverse order based on the functions recited, e.g., the described methods may be performed in an order different from that described, and various steps may be added, omitted, or combined. In addition, features described with reference to certain examples may be combined in other examples.

Through the above description of the embodiments, those skilled in the art will clearly understand that the method of the above embodiments can be implemented by software plus a necessary general hardware platform, and certainly can also be implemented by hardware, but in many cases, the former is a better implementation manner. Based on such understanding, the technical solutions of the present application may be embodied in the form of a software product, which is stored in a storage medium (such as ROM/RAM, magnetic disk, optical disk) and includes instructions for enabling a terminal (such as a mobile phone, a computer, a server, an air conditioner, or a network device) to execute the method according to the embodiments of the present application.

While the present embodiments have been described with reference to the accompanying drawings, it is to be understood that the invention is not limited to the precise embodiments described above, which are meant to be illustrative and not restrictive, and that various changes may be made therein by those skilled in the art without departing from the spirit and scope of the invention as defined by the appended claims.

Claims

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

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.

2. The method of claim 1, wherein prior to sending the NAS message to a core network, the method further comprises:

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

3. The method of claim 2, wherein the cell information is used for the second terminal to select an access network side device.

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

protecting signaling of an Access Stratum (AS) related process based on the first key or a second key generated based on the first key;

securing signaling of a NAS related procedure 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:

sending a transfer indication to the core network;

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

6. The method of claim 1, wherein the NAS message comprises at least one of:

the identification of the first terminal user, the identification of the first terminal, the PDU session identification ID, the QFI and the message filter information.

7. The method of claim 1, further comprising: sending at least one of the following to the access network side equipment:

the identifier of the first terminal user, the identifier of the first terminal, the core network function identifier serving the first terminal user, the transfer indication, the identifier of the second terminal user, and the identifier of the second terminal.

8. The method of claim 7, wherein the core network function identity serving the first end user is used for the access network-side device to route the NAS message to the core network function serving the first end user.

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

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

10. A method of traffic forwarding, the method being performed by a first core network function, the method comprising:

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

and sending the transfer information to the second core network function.

11. The method of claim 10, further comprising:

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

12. The method of claim 10, further comprising:

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 identity of the second end user and a key shared with the first end user; or, the first key is generated based on the identifier of the second terminal and a key shared with the first terminal user;

the third key is generated based on the first key.

13. The method of claim 12, further comprising:

sending the first key or the second key to access network side equipment for protecting a signaling of an Access Stratum (AS) related process;

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

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

sending 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 where the first terminal is located;

subscription information of a second end user;

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

15. The method of claim 10, wherein the NAS message comprises at least one of:

16. The method of claim 15, wherein 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 end user.

17. The method of claim 10, wherein the transfer information comprises at least one of:

PDU session identification ID, QoS flow identification QFI, message filter information and transfer indication.

18. A method of traffic forwarding, the method being performed by a first terminal, the method comprising:

sending the information of the service to be transferred to a second terminal;

19. The method of claim 18, further comprising:

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

20. The method of claim 19, wherein the cell information is used for the second terminal to select an access network side device.

21. The method of claim 19, further comprising:

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

23. A service transfer method is characterized in that the method is executed by an access network side device, and the method comprises the following steps:

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 relationship;

wherein the transition relationship comprises at least one of:

the method comprises the steps of service data tunnel identification of a transfer service, service data quality of service flow identification QFI of the transfer service, service data tunnel identification and transfer indication, service data tunnel identification and identification of a second terminal user, service data tunnel identification and identification of a second terminal, service data quality of service flow identification QFI and transfer indication, service data quality of service flow identification QFI and identification of the second terminal user, service data quality of service flow identification QFI and identification of the second terminal, service data tunnel identification and identification of a first terminal user, service data tunnel identification and identification of a first terminal, service data quality of service flow identification QFI and identification of the first terminal user, and service data quality of service flow identification QFI and identification of the first terminal.

24. The method of claim 23, further comprising:

receiving transfer information from the second terminal;

wherein the transfer information comprises at least one of:

the identifier of the first terminal user, the identifier of the first terminal, the core network function identifier serving the first terminal user, the transfer instruction, the identifier of the second terminal user, and the identifier of the second terminal.

25. The method of claim 24, wherein forwarding the service data to the second terminal, or the second terminal and the first terminal according to the forwarding relationship comprises:

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.

26. The method of claim 24, further comprising:

receiving a transfer key from the core network;

securing at least one of:

signaling an interaction process with the second terminal;

service data from or to the second terminal.

27. A method of traffic forwarding, 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 relationship to the access network side equipment through the first core network function, wherein the transfer relationship is used for the access network side equipment to forward the service data to the second terminal, or the second terminal and the first terminal.

28. The method of claim 27,

the transfer information includes at least one of: an identifier of a first terminal user, an identifier of a first terminal, an identifier of a core network function serving the first terminal user, a transfer indication, an identifier of the second terminal user, and an identifier of the second terminal; and/or

The transfer relationship comprises at least one of: the method comprises the steps of service data tunnel identification of a transfer service, service data quality of service flow identification QFI of the transfer service, service data tunnel identification and transfer indication, service data tunnel identification and identification of a second terminal user, service data tunnel identification and identification of a second terminal, service data quality of service flow identification QFI and transfer indication, service data quality of service flow identification QFI and identification of the second terminal user, service data quality of service flow identification QFI and identification of the second terminal, service data tunnel identification and identification of a first terminal user, service data tunnel identification and identification of a first terminal, service data quality of service flow identification QFI and identification of the first terminal user, and service data quality of service flow identification QFI and identification of the first terminal.

29. The method of claim 27, further comprising:

sending transfer indication information to a third core network function, wherein the transfer indication information is used for indicating that the transfer service data is sent in at least one of the following modes:

a service data tunnel for transferring a service;

transferring service data service quality flow of the service;

a traffic data tunnel associated with the transition indication;

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

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

a service data tunnel unrelated to the identity of the first end user;

a service data tunnel unrelated to the identity of the first terminal;

30. A second terminal, comprising:

a sending module, 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 terminal user.

31. 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 a PDU session of a first terminal user;

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

32. A first terminal, comprising:

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

33. An access network-side device, comprising:

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

a sending module, 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:

34. A second core network function, comprising:

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

and the sending module is used for sending a transfer relationship to the access network side equipment through the first core network function, wherein the transfer relationship is used for the access network equipment to forward the service data to the second terminal, or the second terminal and the first terminal.

35. A terminal comprising a processor, a memory and a program or instructions stored on the memory and executable on the processor, the program or instructions when executed by the processor implementing a traffic transfer method as claimed in any one of claims 1 to 9 or implementing a traffic transfer method as claimed in any one of claims 18 to 22.

36. A network-side device comprising a processor, a memory, and a program or instructions stored on the memory and executable on the processor, wherein the program or instructions, when executed by the processor, implement the traffic transfer method according to any one of claims 10 to 17, or implement the traffic transfer method according to any one of claims 23 to 29.

37. A readable storage medium, on which a program or instructions are stored, which program or instructions, when executed by the processor, implement the traffic transfer method according to any of claims 1 to 29.