Method for updating slice information

Abstract

A wireless communication method for use in an Access and Mobility Management Function (AMF) is proposed. The wireless communication method includes: receiving network slice information of a first request for a Protocol Data Unit (PDU) session from a wireless terminal; generating network slice information of a second request based on the network slice information of the first request for the PDU session and the network slice information supported by a Radio Access Network (RAN) node of the wireless terminal; and transmitting the network slice information of the second request to a Session Management Function (SMF).

Description

Technical Field

[0001] This document generally relates to wireless communication, particularly to New Radio (NR) communication, and more particularly to 5G communication. Background Art

[0002] First, several terms are described as follows:

[0003] Network slice: A logical network that provides specific network capabilities and network characteristics.

[0004] Network slice instance: A collection of network function instances and required resources (such as computing, storage, and network resources), which forms a deployed network slice.

[0005] Network Slice Selection Assistance Information (NSSAI): NSSAI includes a single NSSAI (S-NSSAI) or a list of S-NSSAIs. The S-NSSAI is configured to identify a network slice and includes:

[0006] Slice / Service Type (SST), which refers to one or more expected network slice behaviors in terms of characteristics and services; and

[0007] Slice Differentiator (SD), which is optional information that supplements one or more slice / service types to distinguish multiple network slices of the same slice / service type.

[0008] In addition, a single or multiple S-NSSAIs can be used to identify a single network slice instance.

[0009] Configured NSSAI: The NSSAI supplied in a User Equipment (UE) applicable to one or more Public Land Mobile Networks (PLMNs).

[0010] Requested NSSAI: The NSSAI provided by the UE to the serving PLMN, for example, during the registration process or the PDU session establishment process.

[0011] Allowed NSSAI: The NSSAI provided by the serving PLMN, for example, during the registration process, and is configured to indicate the S-NSSAI value that can be used by the UE in the serving PLMN for the UE's current registration area.

[0012] Generally, the S-NSSAI in the allowed NSSAI is assumed to be valid for all cells under the current registered registration area (e.g., tracking area list) of the UE. However, this assumption has many limitations for network slice deployment. Within a single tracking area, the network operator may need to deploy different network slices for different cells. Summary of the Invention

[0013] The present disclosure provides methods, systems, and devices for supporting different network slices under different cells with the same tracking area.

[0014] The present disclosure relates to a wireless communication method for use in an access and mobility management function (AMF). The wireless communication method includes:

[0015] Receiving, from a wireless terminal, network slice information of a first request for a protocol data unit (PDU) session,

[0016] Generating, based on the network slice information of the first request for the PDU session and the network slice information supported by a radio access network (RAN) node of the wireless terminal, network slice information of a second request, and

[0017] Transmitting the network slice information of the second request to a session management function (SMF).

[0018] Various embodiments may preferably implement the following features:

[0019] Preferably, the RAN node does not support the network slice information of the first request.

[0020] Preferably, the network slice information of the second request includes: the network slice information of the first request and the network slice information supported by the RAN node of the wireless terminal.

[0021] Preferably, the network slice information of the second request includes: the network slice information of the first request and the network slice information mapped in a home public land mobile network (HPLMN) of the network slice information supported by the RAN node of the wireless terminal.

[0022] Preferably, in response to one of a PDU session establishment request, a handover request, a path switch request, or a service request, the network slice information of the second request is generated.

[0023] Preferably, the wireless communication method further includes:

[0024] Receiving, from the SMF, a message including updated network slice information of a PDU session, where the updated network slice information of the PDU session is set as the second requested network slice information.

[0025] Preferably, the wireless communication method further includes: Transmitting the updated network slice information of the PDU session to a wireless terminal.

[0026] The present disclosure relates to a wireless communication method for use in a session management function (SMF). The wireless communication method includes:

[0027] Establishing a protocol data unit (PDU) session for the first requested network slice information,

[0028] Receiving, from an access and mobility management function (AMF), the second requested network slice information of the PDU session, and

[0029] Transmitting, via the AMF, a message including the second network slice information of the PDU session to a wireless terminal corresponding to the PDU session.

[0030] Various embodiments may preferably implement the following features:

[0031] Preferably, the message is configured to: Update the PDU session to the second network slice information.

[0032] Preferably, the second requested network slice information includes: The first requested network slice information and the network slice information supported by the RAN node of the wireless terminal.

[0033] Preferably, the second requested network slice information includes: The first requested network slice information and the network slice information mapped in a home public land mobile network (HPLMN) of the network slice information supported by the RAN node of the wireless terminal.

[0034] The present disclosure relates to a wireless communication method for use in a wireless terminal. The wireless communication method includes:

[0035] Transmitting, to an access and mobility management function (AMF), the first requested network slice information of a protocol data unit (PDU) session,

[0036] Receiving, from the AMF, the second requested network slice information of the PDU session, and

[0037] Updating the PDU session to the second requested network slice information.

[0038] Various embodiments may preferably implement the following features:

[0039] Preferably, the network slice information of the second request includes: the network slice information of the first request and the network slice information supported by the radio access network (RAN) node of the wireless terminal.

[0040] Preferably, the network slice information of the second request includes: the network slice information of the first request and the network slice information mapped in the home public land mobile network (HPLMN) of the network slice information supported by the radio access network (RAN) node of the wireless terminal.

[0041] Preferably, the network slice information of the second request is within one of the PDU session establishment acceptance or the PDU session modification command.

[0042] The present disclosure relates to a radio network node of an access and mobility management function (AMF). The radio network node includes:

[0043] A communication unit, configured to:

[0044] Receive the network slice information of the first request of a protocol data unit (PDU) session from a wireless terminal, and

[0045] Transmit the network slice information of the second request to a session management function (SMF), and

[0046] A processor, configured to: generate the network slice information of the second request based on the network slice information of the first request of the PDU session and the network slice information supported by the radio access network (RAN) node of the wireless terminal.

[0047] Various embodiments may preferably implement the following features:

[0048] Preferably, the processor is further configured to execute the wireless communication method according to any one of the foregoing methods.

[0049] The present disclosure relates to a radio network node of a session management function (SMF). The radio network node includes:

[0050] A processor, configured to establish a protocol data unit (PDU) session of the network slice information of the first request, and

[0051] A communication unit, configured to:

[0052] Receive the network slice information of the second request of the PDU session from an access and mobility management function (AMF), and

[0053] Transmit a message including the second network slice information of the PDU session to the wireless terminal corresponding to the PDU session via the AMF.

[0054] Various embodiments may preferably implement the following features:

[0055] Preferably, the processor is further configured to execute the wireless communication method according to any one of the foregoing methods.

[0056] The present disclosure relates to a wireless terminal. The wireless terminal includes:

[0057] A communication unit, configured to:

[0058] Transmit network slice information of a first request for a PDU session to an Access and Mobility Management Function (AMF), and

[0059] Receive network slice information of a second request for the PDU session from the AMF, and

[0060] A processor, configured to update the PDU session to the network slice information of the second request.

[0061] Various embodiments may preferably implement the following features:

[0062] Preferably, the processor is further configured to execute the wireless communication method according to any one of the foregoing methods.

[0063] The present disclosure relates to a computer program product, including computer-readable program media code stored thereon, which when executed by a processor causes the processor to implement the wireless communication method according to any one of the foregoing methods.

[0064] The exemplary embodiments disclosed herein are intended to provide features that will become apparent upon reference to the following description when taken in conjunction with the accompanying drawings. According to various embodiments, exemplary systems, methods, devices, and computer program products are disclosed herein. However, it should be understood that these embodiments are presented by way of example and not limitation, and it will be apparent to those of ordinary skill in the art who have read the present disclosure that various modifications can be made to the disclosed embodiments while remaining within the scope of the present disclosure.

[0065] Therefore, the present disclosure is not limited to the example embodiments and applications described and illustrated herein. Additionally, the particular order or hierarchy of steps in the methods disclosed herein is merely an example approach. Based on design preferences, the particular order or hierarchy of steps of the disclosed methods or processes can be rearranged while remaining within the scope of the present disclosure. Thus, those of ordinary skill in the art will understand that the methods and techniques disclosed herein present various steps or acts in a sample order, and unless otherwise expressly stated, the present disclosure is not limited to the particular order or hierarchy presented.

[0066] The above and other aspects and their implementations are described in more detail in the drawings, description, and claims. Description of the Drawings

[0067] Figure 1 Shows a schematic diagram of a network architecture according to an embodiment of the present disclosure.

[0068] Figure 2 Shows an example of a schematic diagram of a wireless terminal according to an embodiment of the present disclosure.

[0069] Figure 3 Shows an example of a schematic diagram of a wireless network node according to an embodiment of the present disclosure.

[0070] Figure 4 Shows a flowchart of a registration process according to an embodiment of the present disclosure.

[0071] Figure 5A and Figure 5B Shows a flowchart of a PDU session establishment process according to an embodiment of the present disclosure.

[0072] Figure 6A and Figure 6B Shows a flowchart of an N2 handover process according to an embodiment of the present disclosure.

[0073] Figure 7A and Figure 7B Shows a flowchart of an Xn handover process according to an embodiment of the present disclosure.

[0074] Figure 8A and Figure 8B Shows a flowchart of a service request process according to an embodiment of the present disclosure. Detailed implementation

[0075] In the present disclosure, a network slice may be equal to an S-NSSAI, and vice versa, because each S-NSSAI identifies a single network slice.

[0076] Figure 1 Shows a schematic diagram of a network architecture, which includes: a user equipment (UE), radio access network (RAN) nodes RAN1 and RAN2, an access and mobility management function (AMF), a session management function (SMF), and a user plane function (UPF).

[0077] The AMF includes the following functions: registration management, connection management, reachability management, and mobility management. In addition, the AMF may also perform other functions, such as access authentication and access authorization. The AMF is a non-access stratum (NAS) security terminal and relays session management (SM) NAS between the UE and the SMF.

[0078] The SMF includes the following functions: session establishment, modification and release, UE Internet Protocol (IP) address allocation and management (including optional authorization functions), selection and control of the user plane (UP) functions, downlink data notification, etc.

[0079] The UPF includes the following functions: acting as an anchor point for mobility within / between radio access technologies (RATs), packet routing and forwarding, traffic usage reporting, quality of service (QoS) handling for the user plane, downlink packet buffering, and triggering of downlink data notification, etc.

[0080] In Figure 1 there are two cells (i.e., RAN nodes RAN1 and RAN2) under the same tracking area. In the embodiment, RAN node RAN1 supports network slice S#1, and RAN node RAN2 supports network slice S#2. In the embodiment, network slice S#1 can be configured for enhanced mobile broadband (eMBB), while network slice S#2 can be configured for ultra reliable low latency communication (URLLC). In the embodiment, RAN node RAN1 does not support network slice S#2. In the embodiment, RAN node RAN2 does not support network slice S#1.

[0081] In the embodiment, the UE is in the tracking areas of RAN nodes RAN1 and RAN2.

[0082] In addition, Figure 1 interfaces N2, N3, N4, and Xn between the SMF, AMF, UPF, and RAN nodes RAN1 and RAN2 are shown, and these interfaces are configured to allow the SMF, AMF, UPF, and RAN nodes RAN1 and RAN2 to communicate with each other. In the embodiment, there is an interface N1 between the AMF and the UE ( Figure 1 not shown in

[0083] Figure 2Schematic diagram of a wireless terminal 20 according to an embodiment of the present disclosure. The wireless terminal 20 may be a UE, a mobile phone, a laptop computer, a tablet computer, an e-book, or a portable computer system, and is not limited thereto. The wireless terminal 20 may include a processor 200 (such as a microprocessor or an application specific integrated circuit (ASIC)), a storage unit 210, and a communication unit 220. The storage unit 210 may be any data storage device that stores program code 212 accessed and executed by the processor 200. Embodiments of the storage unit 210 include, but are not limited to: a subscriber identity module (SIM), a read only memory (ROM), a flash memory, a random access memory (RAM), a hard disk, and an optical data storage device. The communication unit 220 may be a transceiver and is used to transmit and receive signals (such as messages or packets) according to the processing result of the processor 200. In an embodiment, the communication unit 220 transmits and receives signals via Figure 2 at least one antenna 222 shown.

[0084] In an embodiment, the storage unit 210 and the program code 212 may be omitted, and the processor 200 may include a storage unit storing the program code.

[0085] The processor 200 may implement any step in the exemplary embodiments on the wireless terminal 20, for example, by executing the program code 212.

[0086] The communication unit 220 may be a transceiver. Alternatively or additionally, the communication unit 220 may combine a transmitting unit and a receiving unit, and the transmitting unit and the receiving unit are respectively configured to transmit signals to a wireless network node (such as a base station) and receive signals therefrom.

[0087] Figure 3 Schematic diagram of a wireless network node 30 according to an embodiment of the present disclosure. The wireless network node 30 may be a satellite, a base station (BS), a network entity, a mobility management entity (MME), a serving gateway (S-GW), a packet data network (PDN) gateway (P-GW), a radio access network (RAN), a next generation RAN (NG-RAN), a data network, a core network, or a radio network controller (RNC), and is not limited thereto. In addition, the wireless network node 30 may be configured to implement one or more network functions, such as Figure 1The AMF, UPF, and / or SMF as shown. The wireless network node 30 may include a processor 300 (such as, a microprocessor or an ASIC), a storage unit 310, and a communication unit 320. The storage unit 310 may be any data storage device that stores program code 312 accessed and executed by the processor 300. Examples of the storage unit 310 include, but are not limited to: SIM, ROM, flash memory, RAM, hard disk, and optical data storage devices. The communication unit 320 may be a transceiver and is used to transmit and receive signals (such as, messages or packets) according to the processing result of the processor 300. In an example, the communication unit 320 transmits and receives signals via Figure 3 at least one antenna 322 as shown.

[0088] In an embodiment, the storage unit 310 and the program code 312 may be omitted. The processor 300 may include a storage unit storing program code.

[0089] The processor 300 may implement any steps described in the exemplary embodiments on the wireless network node 30, for example, by executing the program code 312.

[0090] The communication unit 320 may be a transceiver. Alternatively or additionally, the communication unit 320 may combine a transmission unit and a reception unit, and the transmission unit and the reception unit are respectively configured to transmit signals to a wireless terminal (such as, a user equipment) and receive signals from it.

[0091] Figure 4 A flowchart of a registration process according to an embodiment of the present disclosure is shown. In Figure 4 , the UE, the RAN nodes RAN1 and RAN2, and the AMF may be Figure 1 those as shown. That is, the RAN node RAN1 supports the network slice S#1, and the RAN node RAN2 supports the network slice S#2. In an embodiment, the RAN node RAN1 does not support the network slice S#2. In an embodiment, the RAN node RAN2 does not support the network slice S#1. In Figure 4 , the RAN node RAN1 / RAN2 initiates and establishes a next-generation (NG) connection towards the AME for negotiating the capabilities of the RAN node RAN1 / RAN2. Next, the UE performs registration towards the AMF via the RAN node RAN1.

[0092] More specifically, in step 401, the RAN node RAN1 initiates the registration process by sending (such as transmitting) an NG establishment request message to the AMF. In an embodiment, the NG establishment request message includes: the identifier RANID1 of the RAN node RAN1, the tracking area, and the supported network slice S#1.

[0093] In step 402, the AMF responds to the RAN node RAN1 with an NG establishment response message including the AMF identifier.

[0094] In step 403, the RAN node RAN2 initiates the registration process by sending an NG establishment request message to the AMF. In the embodiment, the NG establishment request message includes: the identifier RANID2 of the RAN node RAN2, the tracking area, and the supported network slice S#2.

[0095] In step 404, the AMF responds to the RAN node RAN2 with an NG establishment response message including the AMF identifier.

[0096] After steps 401 to 404, the AMF confirms that the identifier RANID1 (i.e., the RAN node RAN1) supports the network slice S#1, the identifier RANID2 (i.e., the RAN node RAN2) supports the network slice S#2, and both the network slices S#1 and S#2 are supported under the same tracking area. In the embodiment, the AMF may also, for example, in steps 402 and 404 respectively, notify both the RAN node RAN1 and the RAN node RAN2 that the network slice S#1 can be replaced by the network slice S#2 (i.e., replacement of the network slice S#1 by the network slice S#2 is supported). That is to say, it is possible to support the handover from the network slice S#1 to the network slice S#2.

[0097] In step 405, the UE can be powered on and perform cell selection. The UE initiates the registration request process by transmitting a registration request message to the AMF via the RAN node RAN1. In the embodiment, the requested NSSAI in the registration request message includes the network slices S#1 and S#2.

[0098] In step 406, the RAN node RAN1 performs AMF selection and forwards the registration request message from the UE to the AMF, where the forwarded registration request message includes the current tracking area of the RAN node RAN1.

[0099] In step 407, the AMF determines the allowed NSSAI based on the received registration request (e.g., UE subscription and requested NSSAI) and one or more supported network slices in the current tracking area obtained in steps 401 to 404. In this embodiment, the AMF accepts the UE registration and assigns a temporary identity to the UE. The AMF includes the allowed NSSAI including both the network slices S#1 and S#2, the registration area, and the temporary identity in the registration acceptance message and sends the message to the UE.

[0100] In step 408, the UE stores the temporary identity, the registration area, and the allowed NSSAI, and returns a registration completion message to the AMF.

[0101] After the registration process is completed, the core network (not shown) may send a UE route selection policy (URSP) rule to the UE. When the UE needs to establish a PDU session for its application traffic, the UE can determine parameters including the S-NSSAI of the PDU session and the data network name (DNN). In an embodiment, the URSP rule is sent by the home public land mobile network (HPLMN) of the UE. Therefore, in a non-roaming scenario, the S-NSSAI in the URSP rule is valid for the UE's current PLMN, while in a roaming scenario, the S-NSSAI in the URSP rule is valid for the HPLMN.

[0102] Embodiment 1: PDU session establishment for network slice S#2

[0103] Figure 5A and Figure 5B shows a flowchart of a PDU session establishment process according to an embodiment of the present invention, where Figure 5A and Figure 5B the UE, RAN node RAN1, AMF, SMF, and UPF shown may be Figure 1 those shown. In Figure 5A and Figure 5B , the UE determines to establish a PDU session for its application traffic in network slice S#2 based on the URSP rule, where the UE establishes the PDU session via RAN node RAN1. Note that RAN node RAN1 supports network slice S#1, and RAN node RAN2 supports network slice S#2. In this embodiment, the AMF determines to modify the requested S-NSSAI (i.e., network slice S#2) to the S-NSSAI supported by the current RAN node (i.e., network slice S#1 supported by RAN node RAN1). More details of the process shown in Figure 5A and Figure 5B are discussed below:

[0104] In step 501, the UE initiates a UE-requested PDU session establishment process by transmitting a NAS message containing (e.g., including) a PDU session establishment request within an N1 session management (SM) container. In an embodiment, the PDU session establishment request includes information about the PDU session, such as the PDU session ID, the requested PDU session type, the requested S-NSSAI indicating network slice S#2, the requested data network name (DNN), etc.

[0105] In an embodiment of the non-roaming scenario, the requested S-NSSAI (i.e., network slice S#2) is derived from the URSP rule and should be within the allowed NSSAI valid for the UE's current PLMN. In an embodiment of the roaming scenario, the requested S-NSSAI includes two parts: one part is the S-NSSAI of the PDU session valid within the current PLMN (e.g., corresponding to network slice S#2), and the other part is the S-NSSAI mapped by the UE in the HPLMN derived from the URSP rule (e.g., corresponding to network slice S#3).

[0106] In this embodiment, the NAS message is sent to the network (e.g., AMF / SMF) via the RAN node RAN1.

[0107] In step 502, the RAN node RAN1 forwards the PDU session establishment request including the requested NSSAI to the AMF.

[0108] In step 503, in response to the PDU session establishment request from the UE, the AMF generates a newly requested NSSAI. In an embodiment, the AMF generates the newly requested NSSAI based on the requested NSSAI received from the UE (via the RAN node RAN1) and the allowed NSSAI supported by the UE's current RAN node RAN1. More specifically, the AMF may check (e.g., determine) that the UE's current RAN node 1 does not support the requested S-NSSAI (i.e., network slice S#2), and that network slice S#2 can be replaced by another network slice supported by the current RAN node RAN1 (i.e., network slice S#1). In this case, the AMF generates a newly requested NSSAI for performing S-NSSAI replacement. In an embodiment, the information indicating that the replacement of network slice S#1 by network slice S#2 is supported is pre-configured in the AMF. In an embodiment of the roaming scenario, both network slices S#1 and S#2 are mapped to the same S-NSSAI (e.g., network slice S#3) in the UE's HPLMN. That is, network slice S#3 corresponds to the mapped S-NSSAI that is valid in the HPLMN and to which network slices S#1 and S#2 are mapped.

[0109] In an embodiment of the non-roaming scenario, the AMF generates a newly requested NSSAI, including two parts: one part is the S-NSSAI valid (e.g., supported) in the UE's current RAN node RAN1 (i.e., network slice S#1), and the other part is the requested S-NSSAI received from the UE but not supported by the UE's current RAN node RAN1 (i.e., network slice S#2).

[0110] In an embodiment of the roaming scenario, the AMF generates a newly requested NSSAI, which includes two parts: one part is the S-NSSAI (i.e., network slice S#1) that is valid (e.g., supported) in the UE's current RAN node RAN1, and the other part is the S-NSSAI mapped in the UE's HPLMN (i.e., network slice S#3). In an embodiment, the mapped S-NSSAI is received from the UE.

[0111] In step 504, the AMF performs SMF selection and sends an Nsmf_PDU Session_CreateSMContext request (message) to the selected SMF. In an embodiment, this message includes: the UE's subscribed permanent identifier (SUPI), DNN, newly requested S-NSSAI, PDU session ID, AMF ID, request type, N1 SM container (i.e., PDU session establishment request), user location information, etc.

[0112] In step 505, the SMF selects a UPF for the PDU session. In addition, the SMF establishes an N4 association relationship with the selected UPF, where the N3 tunnel information is allocated by the UPF and provided to the SMF.

[0113] In step 506, the SMF returns an Nsmf_PDUSession_CreateSMContext response (message), which includes a cause value indicating whether the request is accepted. In an embodiment, this message also includes the SM context ID allocated by the SMF. In an embodiment, the AMF uses the SM context ID for subsequent messages towards the SMF.

[0114] In step 507, the SMF sends a Namf_Communication_N1N2MessageTransfer message to the AMF. In an embodiment, this message includes the following parameters, such as PDU session ID, N2 SM information (e.g., including PDU session ID, QoS flow ID (one or more QFIs), one or more QoS profiles, N3 tunnel information of the UPF, S-NSSAI of the PDU session, etc.), N1 SM container (e.g., including PDU session establishment acceptance (e.g., one or more QoS rules, accepted S-NSSAI, DNN, etc.)). In the N2 SM information, the S-NSSAI is set to network slice S#1 supported by the UE's current RAN node RAN1. In the N1SM container, the accepted S-NSSAI is set to the newly requested S-NSSAI generated in step 503. In response to this message, the AMF sends a response (message) to the SMF.

[0115] In step 508, the AMF sends an N2 PDU session request (message) to RAN node RAN1. In an embodiment, the message includes: the received N2 SM information, NAS messages (such as PDU session ID, N1 SM container (such as PDU session establishment acceptance)).

[0116] In step 509, RAN node RAN1 may initiate AN-specific signaling exchange with the UE, which is related to the information received from the SMF in step 508 (e.g., PDU session establishment acceptance). For example, radio resource control (RRC) connection reconfiguration with the UE may occur to establish the necessary Next Generation RAN (NG-RAN) resources related to the QoS rules of the PDU session request. In an embodiment, RAN node RAN1 also assigns N3 tunnel information to the PDU session.

[0117] In step 510, RAN node RAN1 sends an N2 PDU session response (message) to the AMF. The message includes parameters such as PDU session ID, cause, N2 SM information (e.g., PDU session ID, N3 tunnel information, accepted / rejected QFI list), etc.

[0118] In step 511, the AMF sends an Nsmf_PDUSession_UpdateSMContext request (message) to the SMF (including, for example, SMF SM context ID, N2 SM information).

[0119] In step 512, the SMF initiates an N4 session modification process with the UPF to provide the N3 tunnel information received from RAN node RAN1.

[0120] In step 513, the SMF sends an Nsmf_PDUSession_UpdateSMContext response (message) to the AMF.

[0121] After completing Figure 5A and Figure 5B the processes shown, a PDU session is established. The UE stores the accepted S-NSSAI for the PDU session. In an embodiment of the non-roaming scenario, the accepted S-NSSAI has two parts: one part is network slice S#1 supported by the UE's current RAN node RAN1, and the other part is network slice S#2 derived from the URSP rule.

[0122] In an embodiment of the roaming scenario, the accepted S-NSSAI has two parts: one part is the network slice S#1 supported by the UE's current RAN node RAN1, and the other part is the network slice S#3 derived from the URSP rule and valid in the HPLMN (i.e., the mapped network slice information).

[0123] Figure 6A and Figure 6B shows a flowchart of the N2 handover process according to an embodiment of the present disclosure, where Figure 6A and Figure 6B the UE, RAN nodes RAN1 and RAN2, AMF, SMF, and UPF shown may be Figure 1 those shown. In Figure 6A and 6B , the UE needs to hand over to the target RAN node RAN2 via the N2 interface. The AMF modifies the network slice of the PDU session and notifies the network of the modification. The network updates the PDU session context and updates the new network slice of the PDU session to the UE.

[0124] More specifically, in step 601, the UE establishes a PDU session with the network slice S#1 via the RAN node RAN1, for example, via Figure 5A and Figure 5B the PDU session establishment process shown.

[0125] In step 602, the RAN node RAN1 performs UE measurements and determines that a handover to the RAN node RAN2 is required. The RAN node RAN1 (or RAN2) sends a handover request (message) to the AMF via the N2 interface (including, for example, the target ID (RAN node RAN2), source-to-target transparent container, SM N2 information list, PDU session ID).

[0126] In step 603, in response to a handover request (message), the AMF generates a new S-NSSAI. In an embodiment, the AMF generates a new S-NSSAI based on the current S-NSSAI of the PDU session (i.e., network slice S#1) and the S-NSSAI supported by the target RAN node RAN2 of the UE (i.e., network slice S#2). More specifically, the AMF checks (e.g., determines) that the target RAN node RAN2 identified by the target ID of the handover request does not support the current S-NSSAI of the PDU session (i.e., network slice S#1), the target RAN node RAN2 supports network slice S#2, and network slice S#1 can be replaced by S#2. In this case, the AMF performs an S-NSSAI replacement process. In an embodiment, information indicating that network slice S#1 can be replaced by network slice S#2 (e.g., replacement of network slice S#1 by network slice S#2 is supported) is preconfigured in the AMF. In an embodiment of the roaming scenario, both network slices S#1 and S#2 are mapped to the same S-NSSAI (e.g., network slice S#3) in the UE's HPLMN.

[0127] In an embodiment of the non-roaming scenario, the AMF generates a new S-NSSAI, which includes two parts: one part is the requested S-NSSAI (i.e., network slice S#2) that is valid in the target RAN2 node, and the other part is the S-NSSAI of the original network slice of the PDU session (i.e., network slice S#1 supported by the current RAN node RAN1 of the PDU session).

[0128] In an embodiment of the roaming scenario, the AMF generates a new S-NSSAI, which includes two parts: one part is the requested S-NSSAI (i.e., network slice S#2) that is valid in the target RAN node RAN2, and the other part is the S-NSSAI mapped in the HPLMN received from the UE (i.e., network slice S#3).

[0129] In an embodiment of AMF-to-AMF mobility, the S-NSSAI replacement process is performed by the target AMF corresponding to the requested S-NSSAI (i.e., network slice S#2).

[0130] In step 604, the AMF sends an Nsmf_PDUSession_UpdateSMContext request (message) to the SMF (including, for example, the PDU session ID, the new S-NSSAI, and N2 SM information). The SMF checks (determines) whether it can accept the N2 handover with the new S-NSSAI. When accepting the N2 handover, the SMF replaces the network slice of the PDU session with the new S-NSSAI received from the AMF.

[0131] In step 605, the SMF sends an Nsmf_PDUSession_UpdateSMContext response (message) to the AMF, including, for example, the PDU session ID and N2 SM information. In an embodiment, the N2 SM information includes the S-NSSAI supported by the target RAN node RAN2 (i.e., network slice S#2).

[0132] In step 606, the AMF sends a handover request (message) to the RAN node RAN2, including, for example, a source-to-target transparent container, N2 MM information, and a list of N2 SM information. In an embodiment, the AMF determines the target RAN (i.e., RAN node RAN2) based on the target ID. In an embodiment, the source-to-target transparent container is forwarded as the transparent container received from the source RAN (i.e., RAN node RAN1).

[0133] In step 607, the RAN node RAN2 sends a handover request acknowledgment (message) to the AMF, including, for example, a target-to-source transparent container and a list of PDU sessions switched with the N2 SM information. In an embodiment, the target-to-source transparent container includes a UE container having an access stratum part and a NAS part. In an embodiment, the N2 SM information includes the N3 tunnel information of the PDU session in the RAN node RAN2.

[0134] In step 608, the AMF sends an Nsmf_PDUSession_UpdateSMContext request message to the SMF, including, for example, the PDU session ID and the N2 SM information received from the RAN node RAN2.

[0135] In step 609, the SMF performs an N4 session modification procedure with the UPF to update the N3 tunnel information of the PDU session in the RAN node RAN2.

[0136] In step 610, the SMF sends an Nsmf_PDUSession_UpdateSMContext response (message) to the AMF, including, for example, the PDU session ID and the N2 SM information.

[0137] In step 611, the AMF sends a handover command to the RAN node RAN1, including, for example, a target-to-source transparent container and a list of PDU sessions to be switched with the N2 SM information.

[0138] In step 612, the RAN node RAN1 sends a handover command to the UE (including, for example, a UE container), where the UE container is the UE part of the target-to-source transparent container, which is transparently sent from the RAN node RAN2 to the RAN node RAN1 via the AMF and provided to the UE by the RAN node RAN1.

[0139] In step 613, after the UE successfully synchronizes to the target cell, the UE sends a handover confirmation (message) to the RAN node RAN2. In an embodiment, the handover is considered successful by the UE based on the handover confirmation (message).

[0140] In step 614, the RAN node RAN2 sends a handover notification (message) to the AMF, where the handover is based on the message considered successful in the RAN node RAN2.

[0141] In step 615, the AMF sends an Nsmf_PDUSession_UpdateSMContext request (message) to the SMF (including, for example, the PDU session ID, N2 SM information).

[0142] In step 616, the SMF initiates an N4 session modification procedure with the UPF to allow the UPF to send downlink (DL) data towards the RAN node RAN2 via the N2 tunnel.

[0143] In step 617, the SMF sends an Nsmf_PDUSession_UpdateSMContext response (message) to the AMF.

[0144] In step 618, when the SMF determines that the current network slice of the PDU session is modified in step 604, the SMF initiates the modification (e.g., update) of the network slice information of the PDU session in, for example, the AMF and / or the UE. In this embodiment, the SMF sends a Namf_Communication_N1N2Message Transfer message to the AMF. The message includes the following parameters, such as the PDU session ID, the new S-NSSAI, the N1 SM container (including, for example, the PDU session modification command (new S-NSSAI)). Note that the new S-NSSAI in the N1 SM container is set to the new S-NSSAI received from the AMF. The AMF sends a response to the SMF.

[0145] In an embodiment of the roaming scenario, the update of the PDU session slice information in the UE is initiated by the visited SMF (V-SMF).

[0146] In step 619, the AMF updates the PDU session context with the new S-NSSAI. The AMF sends a PDU session modification command (message) (including the new S-NSSAI) to the UE to modify the slice information of the PDU session.

[0147] In step 620, the UE updates the PDU session context with the new S-NSSAI, and the UE sends a PDU session modification command confirmation (message) to the AMF.

[0148] In step 621, after step 611, the UE may initiate a UE registration procedure to receive a new permitted NSSAI and a new registration area via the RAN node RAN2.

[0149] Figure 7A and Figure 7B shows a flowchart of an Xn handover procedure according to an embodiment of the present disclosure, where the UE, the RAN nodes RAN1 and RAN2, the AMF, the SMF, and the UPF may be Figure 1 those shown. In Figure 7A and Figure 7B the UE needs to hand over to the target RAN node RAN2 via the Xn interface. The RAN node RAN1 or RAN2 modifies the network slice of the PDU session and notifies the network. The network updates the PDU session context and updates the UE with the updated network slice of the PDU session.

[0150] More specifically, in step 701, the RAN node RAN1 sends an Xn establishment request (message) to the RAN node RAN2, where the Xn establishment request (message) includes the supported S-NSSAI of the RAN node RAN1 (i.e., network slice S#1).

[0151] In step 702, the RAN node RAN2 sends an Xn establishment response (message) to the RAN node RAN1, where the Xn establishment response (message) may include the supported S-NSSAI of the RAN node RAN2 (i.e., network slice S#2).

[0152] In an embodiment, after steps 701 and 702, the RAN nodes RAN1 and RAN2 exchange the supported network slices with each other. During the NG establishment procedure, the AMF may notify the RAN nodes RAN1 and RAN2 that the network slice S#1 can be replaced by S#2. The information indicating that the network slice S#1 can be replaced by the network slice S#2 may be pre-configured in the AMF. In an embodiment of the roaming scenario, both the network slices S#1 and S#2 are mapped to the same S-NSSAI in the HPLMN (e.g., network slice S#3).

[0153] In step 703, the UE establishes a PDU session with the network slice S#1 via the RAN node RAN1, for example, by performing Figure 5A and Figure 5B the PDU session establishment procedure shown.

[0154] In step 704, the RAN node RAN1 performs UE measurements and determines that a handover to the RAN node RAN2 is required. Note that the RAN node RAN1 is aware that the RAN node RAN2 does not support the network slice S#1, the RAN node RAN2 supports the network slice S#2, and the network slice S#1 can be replaced by the network slice S#2. Therefore, the RAN node RAN1 sends an Xn handover request (message) to the RAN node RAN2. In addition, the RAN node RAN1 may modify the S-NSSAI of the PDU session to the network slice S#2.

[0155] In step 705, the RAN node RAN2 determines that the network slice S#1 can be replaced by the network slice S#2 and determines to accept the handover request. The RAN node RAN2 sets the S-NSSAI of the PDU session to the network slice S#2 and sends an Xn handover response (message) to the RAN node RAN1. In an embodiment, the Xn handover response (message) includes an RRC container of the RAN node RAN2 (e.g., RAN2 RRC container).

[0156] In step 706, the RAN node RAN1 sends a handover command to the UE, where the handover command includes an RRC container of the RAN node RAN2.

[0157] In step 707, after successfully synchronizing to the target cell, the UE sends a handover confirmation (message) to the RAN node RAN2.

[0158] In step 708, the RAN node RAN2 sends a path handover request to the AMF. In an embodiment, the path handover request includes the network slice S#2 as the S-NSSAI of the PDU session, and the N2 SM information includes the N3 tunnel information of the RAN node RAN2.

[0159] In step 709, in response to the path handover request, the AMF generates a new S-NSSAI for the PDU session. In an embodiment, the AMF generates a new S-NSSAI for the PDU session based on the S-NSSAI received from the RAN node RAN2 (i.e., the network slice S#2 supported by the target RAN node RAN2) and the current S-NSSAI of the PDU session, and sends an Nsmf_PDUSession_UpdateSMContext request (message) to the SMF (including, for example, the PDU session ID, the new S-NSSAI, the N2 SM information).

[0160] In an embodiment of the non-roaming scenario, the new NSSAI includes two parts: one part is the S-NSSAI (i.e., network slice S#2) that is valid in the target RAN node, the RAN2 node, and the other part is the current S-NSSAI of the original network slice S#1 of the PDU session.

[0161] In an embodiment of the roaming scenario, the new NSSAI includes two parts: one part is the S-NSSAI (i.e., network slice S#2) that is valid in the target RAN2 node, and the other part is the S-NSSAI (e.g., network slice S#3) mapped in the HPLMN that can be received from the UE.

[0162] In step 710, the SMF initiates an N4 session modification procedure with the UPF to provide the N3 tunnel information received from the RAN node RAN2.

[0163] In step 711, the SMF sends an Nsmf_PDUSession_UpdateSMContext response (message) to the AMF.

[0164] In step 712, the AMF sends a path switch response (message) to the RAN node RAN2.

[0165] In step 713, the SMF determines that the network slice information of the PDU session was modified in step 709 and initiates a modification (e.g., update) of the network slice information of the PDU session in the UE. The SMF sends a Namf_Communication_N1N2MessageTransfer message to the AMF, where the message includes the following parameters, such as the PDU session ID, the new S-NSSAI, and the N1 SM container (including, for example, the PDU session modification command (new S-NSSAI)). The AMF sends a response to the SMF. Note that the new S-NSSAI in this message is set to the new NSSAI received from the AMF.

[0166] In an embodiment of the roaming scenario, the update of the network slice information of the PDU session in the UE is initiated by the V-SMF.

[0167] In step 714, the AMF updates the PDU session context with the new S-NSSAI and sends a PDU session modification command (including the new S-NSSAI) to the UE to modify the network slice of the PDU session.

[0168] In step 715, the UE updates the PDU session context with the new S-NSSAI and sends a PDU session modification command confirmation to the AMF.

[0169] In step 716, after step 707, the UE may initiate a UE registration procedure to receive a new permitted NSSAI.

[0170] Figure 8A and Figure 8B shows a flowchart of a service request procedure according to an embodiment of the present disclosure, where Figure 8A and Figure 8B the UE, RAN node RAN1, AMF, SMF, and UPF shown may be Figure 1 those shown. In Figure 8A and Figure 8B when the UE initiates a service request procedure to activate a PDU session for network slice S#2, the AMF determines that the UE's current RAN node RAN1 cannot support the original S-NSSAI of the PDU session (i.e., network slice S#2). In this case, the AMF determines to modify the network slice information of the PDU session from the original S-NSSAI (i.e., network slice S#2) to an S-NSSAI supported by the UE's current RAN node RAN1 (i.e., network slice S#1).

[0171] More specifically, in step 801, the UE initiates a service request procedure via RAN node RAN1 to activate a PDU session by transmitting a service request to RAN node RAN1. Note that the PDU session is established using the S-NSSAI corresponding to network slice S#2.

[0172] In step 802, RAN node RAN1 forwards the service request to the AMF.

[0173] In step 803, in response to the service request, the AMF generates a new S-NSSAI for the PDU session. In an embodiment, the AMF generates the new S-NSSAI based on the current S-NSSAI (i.e., network slice S#2 of the PDU session) and the S-NSSAI supported by the UE's current RAN node RAN1. Specifically, the AMF checks (determines) that the UE's current RAN node RAN1 does not support the original S-NSSAI of the PDU session (i.e., network slice S#2), and that network slice S#2 can be replaced by network slice S#1 of RAN node RAN1. Therefore, the AMF performs S-NSSAI replacement. In an embodiment, information indicating that network slice S#2 can be replaced by network slice S#1 is pre-configured in the AMF. In an embodiment of a roaming scenario, both network slices S#1 and S#2 are mapped to the same S-NSSAI in the HPLMN (e.g., network slice S#3). That is, network slice S#3 corresponds to the valid, mapped S-NSSAI in the HPLMN.

[0174] In an embodiment of the non-roaming scenario, the AMF generates a newly requested NSSAI, which includes two parts: one part is the S-NSSAI (i.e., network slice S#1) that is valid (e.g., supported) in the UE's current RAN node RAN1, and the other part is the requested S-NSSAI (i.e., network slice S#2) received from the UE but not supported by the UE's current RAN node RAN1.

[0175] In the case of roaming, the AMF generates a newly requested NSSAI, which includes two parts: one part is the S-NSSAI (i.e., network slice S#1) that is valid (e.g., supported) in the UE's current RAN node RAN1, and the other part is the S-NSSAI mapped for the UE's HPLMN (i.e., network slice S#3). In an embodiment, the mapped S-NSSAI is received from the UE.

[0176] In step 804, the AMF sends an Nsmf_PDUSession_UpdateSMContext request (message) to the SMF, where the message includes SUPI, DNN, new S-NSSAI, PDU session ID, AMF ID, user location information, etc.

[0177] In step 805, the SMF can let the UPF modify the N3 tunnel information in the UPF via the N4 session modification process. In an embodiment, the N3 tunnel information is allocated by the UPF and provided to the SMF.

[0178] In step 806, the SMF returns an Nsmf_PDUSession_UpdateSMContext response (message). The message includes N2 SM information (including, for example, PDU session ID, QFI, QoS profile, N3 tunnel information of the UPF, S-NSSAI, etc.). Note that the S-NSSAI in the N2 SM information is set to the network slice S#1 supported by the UE's current RAN node RAN1.

[0179] In step 807, the AMF sends an N2 PDU session request (message) to the RAN node RAN1. In an embodiment, the message includes N2 SM information and NAS messages (e.g., service acceptance message).

[0180] In step 808, the RAN node RAN1 can initiate a specific signaling exchange with the UE, which is related to the N2SM information received from the SMF. For example, an RRC connection reconfiguration with the UE can occur to establish the necessary NG-RAN resources related to the QoS rules for the PDU session request. The RAN node allocates the N3 tunnel information to the PDU session. The RAN node RAN1 also returns a service acceptance (message) to the UE.

[0181] In step 809, the RAN node RAN1 sends an N2 PDU session response (message) to the AMF. In an embodiment, the message includes the following parameters, such as the PDU session ID, cause, N2 SM information (PDU session ID, N3 tunnel information, list of accepted / rejected QFIs), etc.

[0182] In step 810, the AMF sends an Nsmf_PDUSession_UpdateSMContext request (message) to the SMF (including, for example, the SMF SM context ID and N2 SM information).

[0183] In step 811, the SMF initiates an N4 session modification procedure with the UPF to provide the N3 tunnel information received from the RAN node RAN1.

[0184] In step 812, the SMF sends an Nsmf_PDUSession_UpdateSMContext response (message) to the AMF.

[0185] In step 813, the SMF sends a Namf_Communication_N1N2Message Transfer message to the AMF to update the network slice information of the PDU session in the UE. In an embodiment, the message includes the following parameters, such as the PDU session ID, new S-NSSAI, N1 SM container (PDU session modification command (new S-NSSAI)). The AMF sends a response to the SMF. Note that the new S-NSSAI is received from the AMF.

[0186] In an embodiment of the roaming scenario, the update of the network slice information of the PDU session in the UE is initiated by the V-SMF.

[0187] In step 814, the AMF updates the PDU session context with the new S-NSSAI and sends a PDU session modification command (including the new S-NSSAI) to the UE to modify the network slice of the PDU session.

[0188] In step 815, the UE updates the PDU session context with the new S-NSSAI and sends a PDU session modification command confirmation to the AMF.

[0189] Although various embodiments of the present disclosure have been described above, it should be understood that they are presented by way of example and not limitation. Similarly, the various figures may depict example architectures or configurations provided to enable those of ordinary skill in the art to understand the exemplary features and functions of the present disclosure. However, those skilled in the art will understand that the present disclosure is not limited to the illustrated example architectures or configurations, but may be implemented using a variety of alternative architectures and configurations. Additionally, as will be understood by those of ordinary skill in the art, one or more features of one embodiment may be combined with one or more features of another embodiment described herein. Accordingly, the breadth and scope of the present disclosure should not be limited by any of the exemplary embodiments described above.

[0190] It should also be understood that any reference in this document to elements by names such as "first," "second," etc. generally does not limit the number or order of those elements. Instead, these names may be used herein as a convenient means of distinguishing between two or more elements or instances of elements. Thus, a reference to first and second elements does not mean that only two elements are employed, or that the first element must precede the second element in some manner.

[0191] Additionally, those of ordinary skill in the art will understand that information and signals can be represented using any of a variety of different technologies and processes. For example, data, instructions, commands, information, signals, bits, and symbols, such as those referred to in the description above, may be represented by voltages, currents, electromagnetic waves, magnetic fields or magnetic particles, optical fields or optical particles, or any combination thereof.

[0192] Those of ordinary skill in the art will also understand that any of the various illustrative logical blocks, modules, processors, devices, circuits, methods, and functions described in connection with the aspects disclosed herein may be implemented by electronic hardware (e.g., digital implementation, analog implementation, or a combination of both), firmware, various forms of program or design code in conjunction with instructions (which may be referred to herein, for convenience, as "software" or "software modules"), or any combination of these technologies.

[0193] To clearly illustrate this interchangeability of hardware, firmware, and software, various illustrative components, blocks, modules, circuits, and steps have been described above generally in terms of their functionality. Whether this functionality is implemented as hardware, firmware, software, or a combination of these techniques depends upon the particular application and design constraints imposed on the overall system. Skilled artisans may implement the described functionality in various ways for each particular application, but such implementation decisions do not depart from the scope of the present disclosure. In accordance with various embodiments, a processor, device, component, circuit, structure, machine, unit, etc. may be configured to perform one or more of the functions described herein. As used herein, the term "configured to" or "configured for" with respect to a particular operation or function refers to a processor, device, component, circuit, structure, machine, unit, etc. that is physically constructed, programmed, and / or arranged to perform the particular operation or function.

[0194] In addition, those skilled in the art will understand that the various illustrative logical blocks, modules, devices, components, and circuits described herein may be implemented within or performed by an integrated circuit (IC) that includes a general purpose processor, a digital signal processor (DSP), an application specific integrated circuit (ASIC), a field programmable gate array (FPGA) or other programmable logic device, or any combination thereof. The logical blocks, modules, and circuits may also include antennas and / or transceivers for communicating with various components within a network or within a device. A general purpose processor may be a microprocessor, but in the alternative, the processor may be any conventional processor, controller, or state machine. The processor may also be implemented as a combination of computing devices for performing the functions described herein, e.g., a combination of a DSP and a microprocessor, a combination of multiple microprocessors, a combination of one or more microprocessors in conjunction with a DSP core, or any other suitable configuration. If implemented in software, the functions may be stored as one or more instructions or code on a computer-readable medium. Accordingly, the steps of the methods or algorithms disclosed herein may be implemented as software stored on a computer-readable medium.

[0195] Computer-readable media includes both computer storage media and communication media, where communication media includes any medium that enables transfer of a computer program or code from one place to another. The storage media may be any available media that can be accessed by a computer. By way of example, and not limitation, such computer-readable media may include: RAM, ROM, EEPROM, CD-ROM or other optical disk storage, magnetic disk storage or other magnetic storage devices, or any other medium that can be used to store the desired program code in the form of instructions or data structures and that can be accessed by a computer.

[0196] In this document, the term "unit" as used herein refers to software, firmware, hardware, and any combination of these elements for performing the associated functions described herein. Additionally, for purposes of discussion, the various units are described as discrete units; however, it will be apparent to those of ordinary skill in the art that two or more units may be combined to form a single unit that performs the associated functions in accordance with embodiments of the present disclosure.

[0197] Additionally, in embodiments of the present disclosure, a memory or other storage device and communication components may be employed. It will be understood that, for clarity, the above description has described embodiments of the present disclosure with reference to different functional units and processors. However, it will be apparent that any suitable functional distribution between different functional units, processing logic elements, or domains may be used without departing from the present disclosure. For example, functionality described as being performed by separate processing logic elements or controllers may be performed by the same processing logic element or controller. Thus, the reference to specific functional units is merely a reference to the appropriate means for providing the recited functionality, rather than an indication of a strict logical or physical structure or organization.

[0198] Various modifications to the described embodiments of the present disclosure will be apparent to those skilled in the art, and the general principles defined herein may be applied to other embodiments without departing from the scope of the present disclosure. Accordingly, the present disclosure is not intended to be limited to the embodiments shown herein, but should be accorded the widest scope consistent with the novel features and principles disclosed herein, as set forth in the following claims.

Claims

1. A wireless communication method for use in an Access and Mobility Management Function (AMF), the wireless communication method comprising: Receiving, from a wireless terminal, network slice information of a first request for a Protocol Data Unit (PDU) session; Generating, based on the network slice information of the first request for the PDU session and the network slice information supported by a Radio Access Network (RAN) node of the wireless terminal, network slice information of a second request; and Transmitting the network slice information of the second request to a Session Management Function (SMF); wherein the network slice information of the second request includes: the network slice information of the first request and the network slice information supported by the RAN node of the wireless terminal.

2. The wireless communication method according to claim 1, wherein, The RAN node does not support the network slice information of the first request.

3. The wireless communication method according to claim 1 or 2, wherein The network slice information of the second request includes: the network slice information of the first request and the network slice information mapped in a Home Public Land Mobile Network (HPLMN) of the network slice information supported by the RAN node of the wireless terminal.

4. The wireless communication method according to claim 1 or 2, wherein The network slice information of the second request is generated in response to one of a PDU session establishment request, a handover request, a path switch request, or a service request.

5. The wireless communication method according to claim 1 or 2, further comprising: Receiving, from the SMF, a message including updated network slice information of the PDU session; wherein the updated network slice information of the PDU session is set to the network slice information of the second request.

6. The wireless communication method according to claim 5, further comprising: Transmitting the updated network slice information of the PDU session to the wireless terminal.

7. A wireless communication method for use in a Session Management Function (SMF), the wireless communication method comprising: Establishing a Protocol Data Unit (PDU) session for network slice information of a first request; Receiving, from an Access and Mobility Management Function (AMF), the network slice information of a second request for the PDU session; and Transmitting, via the AMF, to a wireless terminal corresponding to the PDU session, a message including the network slice information of the second request for the PDU session; wherein the network slice information of the second request includes: the network slice information of the first request and the network slice information supported by a Radio Access Network (RAN) node of the wireless terminal.

8. The wireless communication method according to claim 7, wherein, The message is configured to update the PDU session to the network slice information of the second request.

9. The wireless communication method according to claim 7 or 8, wherein, The network slice information of the second request includes: the network slice information of the first request and the network slice information mapped in a Home Public Land Mobile Network (HPLMN) of the network slice information supported by the RAN node of the wireless terminal.

10. A wireless communication method for use in a wireless terminal, the wireless communication method comprising: Transmitting, to an Access and Mobility Management Function (AMF), network slice information of a first request for a Protocol Data Unit (PDU) session; Receiving, from the AMF, the network slice information of a second request for the PDU session; and Updating the PDU session to the network slice information of the second request. Among them, the network slice information of the second request includes: the network slice information of the first request and the network slice information supported by the radio access network (RAN) node of the wireless terminal.

11. The wireless communication method according to claim 10, wherein, The network slice information of the second request includes: the network slice information of the first request and the network slice information mapped in the home public land mobile network (HPLMN) of the network slice information supported by the RAN node of the wireless terminal.

12. The wireless communication method according to claim 10 or 11, wherein, The network slice information of the second request is within one of the PDU session establishment acceptance or the PDU session modification command.

13. A radio network node of an access and mobility management function (AMF), the radio network node comprising: A communication unit, configured to: Receive the network slice information of the first request of a protocol data unit (PDU) session from a wireless terminal, and Transmit the network slice information of the second request to a session management function (SMF), and A processor, configured to: generate the network slice information of the second request based on the network slice information of the first request of the PDU session and the network slice information supported by the RAN node of the wireless terminal, Among them, the network slice information of the second request includes: the network slice information of the first request and the network slice information supported by the RAN node of the wireless terminal.

14. The wireless network node according to claim 13, wherein, The processor is further configured to execute the wireless communication method according to any one of claims 2 to 6.

15. A radio network node of a session management function (SMF), the radio network node comprising: A processor, configured to: establish a PDU session of the network slice information of the first request, and A communication unit, configured to: Receive the network slice information of the second request of the PDU session from the access and mobility management function (AMF), and Transmit a message including the network slice information of the second request of the PDU session to the wireless terminal corresponding to the PDU session via the AMF, Among them, the network slice information of the second request includes: the network slice information of the first request and the network slice information supported by the RAN node of the wireless terminal.

16. The wireless network node according to claim 15, wherein, The processor is further configured to execute the wireless communication method according to claim 8 or 9.

17. A wireless terminal, comprising: A communication unit, configured to: Transmit the network slice information of the first request of a PDU session to an access and mobility management function (AMF), and Receive the network slice information of the second request of the PDU session from the AMF, and a processor, configured to update the PDU session to the network slice information of the second request, where the network slice information of the second request includes: the network slice information of the first request and the network slice information supported by the RAN node of the wireless terminal.

18. The wireless terminal according to claim 17, wherein, The processor is further configured to execute the wireless communication method according to claim 11 or 12.

19. A computer program product, comprising computer-readable program media code stored thereon, which when executed by a processor causes the processor to implement the method according to any one of claims 1 to 12.

Images