RADIO ACCESS NETWORK NODE, RADIO TERMINAL, CORE NETWORK NODE, AND METHOD THEREFOR

• US 20190191348A1
• Filed: 05/15/2017
• Published: 06/20/2019
• Est. Priority Date: 08/10/2016
• Status: Active Grant

• Current Assignee: NEC Corporation
• Original Assignee: NEC Corporation
• Inventors: FUTAKI, Hisashi, HAYASHI, Sadafuku
• Granted Patent: US 11,910,258 B2
• Time in Patent Office: Days
• CPC Class Codes: H04W 36/0033 with transfer of context information
• CPC Class Codes: H04W 36/0038 of security context information
• CPC Class Codes: H04W 36/13 Cell handover without a predetermined boundary, e.g. virtual cells
• CPC Class Codes: H04W 36/1443 between licensed networks
• CPC Class Codes: H04W 92/20 between access points

Abstract

In response to receiving from a source RAN node (2), on a direct interface (101), a message requesting a handover of a radio terminal (1) from a first network to a second network, a target RAN node (3) receives at least one of slice information and flow information from a core network (5), and controls communication of the radio terminal (1) based on at least one of the slice information and the flow information. The slice information relates to a network slice in the second network. The flow information relates to at least one session to be established in the second network, serving as a bearer-less network, in order to transfer at least one packet flow of the radio terminal (1). It is thus possible, for example, to provide an Inter-RAT handover procedure involving transfer of handover signaling messages on a direct inter-base-station interface.

Claims

1. A target radio access network (RAN) node associated with a second network, comprising:

at least one memory; and

at least one processor coupled to the at least one memory and configured to;

receive a handover request message on a direct interface from a source RAN node in a first network, the handover request message requesting a handover of a radio terminal from the first network to the second network;

receive at least one of slice information and flow information from a core network in response to receiving the handover request message; and

control communication of the radio terminal based on at least one of the slice information and the flow information, wherein

the slice information relates to a network slice in the second network to which the radio terminal is to be connected, and

the flow information relates to at least one session to be established in the second network, serving as a bearer-less network, in order to transfer at least one packet flow of the radio terminal.

2. The target RAN node according to claim 1, wherein the slice information includes:

(a) identification information of the network slice selected for the radio terminal;

(b) type information of the network slice selected for the radio terminal;

or (c) identification information of a network node or a network function associated with the network slice selected for the radio terminal;

or any combination thereof.

3. The target RAN node according to claim 1, wherein the slice information includes at least one of a mobility class and a session class that are supported by the network slice selected for the radio terminal.

4. The target RAN node according to claim 1, wherein the flow information includes a flow identifier and a flow QoS parameter in respect of each packet flow of the radio terminal.

5. The target RAN node according to claim 1, wherein the at least one processor is configured to receive at least one of the slice information and the flow information from the core network in a handover completion phase after the radio terminal connects to the target RAN node.

6. The target RAN node according to claim 5, wherein

the handover request message includes a security parameter derived by the source RAN node, and

the at least one processor is configured to derive an Access Stratum (AS) security key from the security parameter.

7. The target RAN node according to claim 5, wherein

the at least one processor is configured to send a path switch request message to the core network in the handover completion phase, and

the path switch request message triggers the core network to select or create a network slice for the radio terminal.

8. The target RAN node according to claim 5, wherein

the at least one processor is configured to send a path switch request message to the core network in the handover completion phase, and

the path switch request message triggers the core network to create a bearer-less session for the radio terminal.

9. The target RAN node according to claim 5, wherein the at least one processor is configured to transmit at least one of the slice information and the flow information to the radio terminal.

10. The target RAN node according to claim 1, wherein the at least one processor is configured to receive at least one of the slice information and the flow information from the core network in a handover preparation phase before the source RAN node issues a handover instruction to the radio terminal.

11. The target RAN node according to claim 10, wherein the at least one processor is configured to determine, based on the slice information, whether to accept a bearer or flow of the radio terminal on a per-bearer or per-flow basis.

12. The target RAN node according to claim 10, wherein the at least one processor is configured to determine, based on the slice information, whether it is possible to accept each network slice.

13. The target RAN node according to claim 10, wherein the at least one processor is configured to further receive Non-Access Stratum (NAS) security configuration information and a security parameter from the core network in the handover preparation phase, the security parameter being used by the target RAN node to derive an Access Stratum (AS) security key.

14. The target RAN node according to claim 10, wherein

the at least one processor is configured to send to the source RAN node, on the direct interface, a handover request acknowledge message containing a transparent container, wherein

the transparent container contains at least one of:

a predetermined parameter included in at least one of the slice information and the flow information; and

radio resource configuration information generated based on at least one of the slice information and the flow information, and the transparent container is to be forwarded to the radio terminal by the source RAN node.

15. The target RAN node according to claim 10, wherein

the at least one processor is configured to send to the core network, in the handover preparation phase, a request message requesting a transmission of at least one of the slice information and the flow information, wherein

the request message triggers the core network to select or create a network slice for the radio terminal.

16. The target RAN node according to claim 10, wherein

the at least one processor is configured to send to the core network, in the handover preparation phase, a request message requesting a transmission of at least one of the slice information and the flow information, wherein

the request message triggers the core network to create a bearer-less session for the radio terminal.

17. A source radio access network (RAN) node associated with a first network, comprising:

at least one memory; and

at least one processor coupled to the at least one memory and configured to;

determine a handover of a radio terminal from the first network to a second network;

send a handover request message on a direct interface to a target RAN node in the second network in response to determination of the handover, the handover request message requesting the handover of the radio terminal to the second network;

receive from the target RAN node, on the direct interface, a handover request acknowledge message containing a transparent container; and

transmit, to the radio terminal, a mobility command message containing the transparent container and indicating the handover to the second network, wherein

the transparent container includes radio resource configuration information needed by the radio terminal to establish a radio connection associated with the second network, and

the radio resource configuration information includes at least one of;

(a) first radio resource configuration information generated based on slice information relating to a network slice in the second network to which the radio terminal is to be connected; and

(b) second radio resource information generated based on flow information relating to at least one session to be established in the second network, serving as a bearer-less network, in order to transfer at least one packet flow of the radio terminal.

18. The source radio access network (RAN) node according to claim 17, wherein

the at least one processor is configured to derive a second security parameter to be used in the second network from a first security parameter used in the first network, and incorporate the second security parameter into the handover request message, wherein

the second security parameter is used by the target RAN node to derive an Access Stratum (AS) security key for the second network.

19. A method in a target radio access network (RAN) node associated with a second network, the method comprising:

receiving a handover request message on a direct interface from a source RAN node in a first network, the handover request message requesting a handover of a radio terminal from the first network to the second network;

receiving at least one of slice information and flow information from a core network in response to receiving the handover request message; and

controlling communication of the radio terminal based on at least one of the slice information and the flow information, wherein

the slice information relates to a network slice in the second network to which the radio terminal is to be connected, and

the flow information relates to at least one session to be established in the second network, serving as a bearer-less network, in order to transfer at least one packet flow of the radio terminal.

20-29. -29. (canceled)