Session control method and apparatus in multi-access environments of wireless communication systems

Through the coordinated operation of AMF and UE, session control in multi-access environments in wireless communication systems is realized, solving the problem that existing technologies cannot meet the diverse service requirements of 5G communication systems in IoT networks, and improving the system's flexibility and efficiency.

CN123126018APending Publication Date: 2026-11-17SAMSUNG ELECTRONICS CO LTD
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202580026476.9
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Priority Date
2024-04-05
Filing Date
2025-04-04
Publication Date
2026-11-17

AI Technical Summary

Technical Problem

In multi-access environments of wireless communication systems, existing technologies lack effective session control methods and cannot meet the diverse service needs of 5G communication systems in IoT networks.

Method used

Through the coordinated operation of Access and Mobility Functions (AMF) and User Equipment (UE), dual bootstrapping (DS) functionality is achieved, including registration requests, Policy Control Function (PCF) selection, Session Management Function (SMF) interaction, and PDU session establishment and rejection mechanisms, to control sessions in a multi-access environment.

Benefits of technology

It enables effective session control in multi-access environments, supports various service requirements of 5G communication systems in IoT networks, and improves the system's flexibility and efficiency.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN123126018A_ABST
    Figure CN123126018A_ABST
Patent Text Reader

Abstract

A method for operating Access and Mobility Function (AMF) in a wireless communication system is disclosed. The method includes: receiving a PDU session establishment request message from a User Equipment (UE) supporting Dual Bootstrapping (DS) function through a registered 3GPP access network using a second SUPI; determining, based on the subscriber information of the UE, whether a PDU session with the same S-NSSAI and DNN as included in the PDU session establishment request message exists for another 3GPP access; and sending a PDU session rejection message to the UE if the PDU session with the same S-NSSAI and DNN as included in the PDU session establishment request message exists for another 3GPP access.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] This disclosure generally relates to wireless communication systems, and more specifically, to session control methods in multi-access environments of wireless communication systems. Background Technology

[0002] To meet the growing demand for wireless data services following the commercialization of fourth-generation (4G) communication systems, efforts have been made to develop fifth-generation (5G) or near-5G communication systems, referred to as beyond-4G network communication systems or post-LTE systems. To achieve high data rates, the implementation of 5G communication systems in ultra-high frequency (UHF) or millimeter-wave (mmWave) bands (e.g., the 60 GHz band) has been considered. To mitigate path loss of radio waves and increase the transmission range of radio waves in UHF bands, beamforming, massive MIMO, full-dimensional MIMO (FD-MIMO), array antennas, analog beamforming, and large antenna technologies have been discussed in 5G communication systems. To improve the system network of 5G communication systems, various technologies have been developed, such as evolved small cells, advanced small cells, cloud radio access networks (RAN), ultra-dense networks, device-to-device (D2D) communication, wireless backhaul, mobile networks, cooperative communication, coordinated multipoint (CoMP), and receive interference cancellation. In addition, advanced coding and modulation (ACM) methods such as hybrid frequency shift keying (FSK), quadrature amplitude modulation (QAM) (FQAM), and sliding window superposition coding (SWSC) have been developed in 5G systems, as well as advanced access technologies such as filter bank multicarrier (FBMC), non-orthogonal multiple access (NOMA), and sparse code multiple access (SCMA).

[0003] Furthermore, the internet has evolved from a human-based network of connections where people create and consume information to the Internet of Things (IoT), in which distributed elements such as objects exchange information to process it. The Internet of Everything (IoE) technology, which combines IoT with big data processing technologies such as connecting to cloud servers, has also emerged. Since realizing IoT requires technological elements such as sensing technology, wireless communication and network infrastructure, service interface technology, and security technology, technologies such as sensor networks for connecting objects, machine-to-machine (M2M) communication, and machine-type communication (MTC) have recently been researched. In the IoT environment, intelligent information technology (IT) services can be provided to collect and analyze data generated by connected objects, thereby creating new value in human life. As existing IT integrates with various industries, IoT can be applied to various fields such as smart homes, smart buildings, smart cities, smart cars or connected cars, smart grids, healthcare, smart home appliances, and advanced medical services.

[0004] Therefore, various attempts have been made to apply 5G communication systems to IoT networks. For example, technologies such as sensor networks, M2M communication, and MTC have been implemented using various schemes as 5G communication technologies, such as beamforming, MIMO, and array antennas. Applying cloud RAN to the aforementioned big data processing technologies can be an example of the integration of 5G and IoT technologies.

[0005] Efforts are also underway to develop a sixth-generation (6G) communication system with a maximum speed approximately five times that of 5G communication systems. Therefore, to achieve high data transmission rates, implementation in higher frequency bands than 5G communication systems has been considered.

[0006] Wireless communication systems have evolved from providing initial voice-centric services to providing broadband wireless communication systems that offer high-speed, high-quality packet data services. These broadband wireless communication systems include communication standards such as 3GPP High-Speed ​​Packet Access (HSPA), LTE or Evolved Universal Terrestrial Radio Access (E-UTRA), LTE-Advanced (LTE-A), LTE-Pro, 3GPP2 High-Rate Packet Data (HRPD), Ultra Mobile Broadband (UMB), and IEEE 802.16e.

[0007] As an example of a broadband wireless communication system, the LTE system can employ Orthogonal Frequency Division Multiplexing (OFDM) for the downlink (DL) and Single-Carrier Frequency Division Multiple Access (SC-FDMA) for the uplink (UL). UL can refer to the radio link through which a terminal (UE or MS) transmits data or control signals to a base station (eNode B or BS), and DL can refer to the radio link through which the base station transmits data or control signals to the terminal. This multiple access scheme identifies the data or control information of each user by allocating non-overlapping time-frequency resources for carrying data or control information to the corresponding users and ensuring that these time-frequency resources are orthogonal to each other.

[0008] As the future communication system following LTE, 5G communication systems should be able to freely reflect the various needs of users and service providers. Therefore, 5G communication systems should support services that meet various needs simultaneously, such as enhanced mobile broadband (eMBB), massive MTC (mMTC), and ultra-reliable low-latency communication (URLLC).

[0009] As the development of the aforementioned wireless communication systems can provide a variety of services, there is a need in the art for a solution to control sessions in a multi-access environment. Summary of the Invention

[0010] Technical issues

[0011] Therefore, one aspect of this disclosure is to provide a session control method and apparatus in a multi-access environment of a wireless communication system or a mobile communication system.

[0012] Technical solution

[0013] According to one aspect of this disclosure, a method for Access and Mobility Function (AMF) in a wireless communication system may include: receiving a registration request message including a Dual Bootstrapping (DS) function support indicator from a User Equipment (UE) via a RAN; determining whether to allow UE registration based on the UE's subscription information; sending a registration acceptance message to the UE via the RAN; selecting a Policy Control Function (PCF) and sending a request message for UE policy establishment to the PCF; receiving a response message to the UE policy establishment request from the PCF; receiving a request message for UE policy update from the PCF; and sending a message including new configuration information to the UE.

[0014] According to one aspect of this disclosure, a method for Access and Mobility Function (AMF) in a wireless communication system may include: receiving a PDU session establishment request message from a User Equipment (UE) supporting Dual Bootstrapping (DS) functionality via a registered 3GPP access network using a second SUPI; determining, based on the UE's subscriber information, whether a PDU session with the same S-NSSAI and DNN as included in the PDU session establishment request message exists for another 3GPP access; and, if a PDU session with the same S-NSSAI and DNN as included in the PDU session establishment request message exists for another 3GPP access, sending a PDU session rejection message to the UE.

[0015] According to one aspect of this disclosure, a method for a user equipment (UE) supporting dual bootstrapping (DS) functionality in a wireless communication system may include: sending a PDU session establishment request message to an Access and Mobility Function (AMF) via a registered 3GPP access network using a second SUPI; and receiving a PDU session establishment response message from a Session Management Function (SMF), wherein, in the case that a PDU session with the same S-NSSAI and DNN as those included in the PDU session establishment request message exists for another 3GPP access, the PDU session establishment response message includes a PDU session rejection message.

[0016] According to one aspect of this disclosure, the AMF in a wireless communication system may include a transceiver and at least one processor, the at least one processor being configured to: receive a PDU session establishment request message from a user equipment (UE) supporting dual bootstrapping (DS) functionality via a registered 3GPP access network using a second SUPI; determine, based on the UE's subscriber information, whether a PDU session with the same S-NSSAI and DNN as included in the PDU session establishment request message exists for another 3GPP access; and, if a PDU session with the same S-NSSAI and DNN as included in the PDU session establishment request message exists for another 3GPP access, send a PDU session rejection message to the UE.

[0017] According to one aspect of this disclosure, a UE supporting DS functionality in a wireless communication system may include a transceiver and at least one processor, the at least one processor being configured to: send a PDU session establishment request message to an Access and Mobility Function (AMF) via a registered 3GPP access network using a second SUPI; and receive a PDU session establishment response message from a Session Management Function (SMF), wherein, in the case that a PDU session with the same S-NSSAI and DNN as those included in the PDU session establishment request message exists for another 3GPP access, the PDU session establishment response message includes a PDU session rejection message. Attached Figure Description

[0018] The above and other aspects, features and advantages of some embodiments of this disclosure will become more apparent from the following description taken in conjunction with the accompanying drawings, in which:

[0019] Figure 1 A 5G system according to an embodiment is shown;

[0020] Figure 2 A method for sending dual bootstrapping (DS) policy and UE routing policy (URSP) rules to a UE according to an embodiment is shown;

[0021] Figure 3 A session control method in a multi-access environment of a wireless communication system according to an embodiment is illustrated;

[0022] Figure 4 A session control method in a multi-access environment of a wireless communication system according to an embodiment is shown; and

[0023] Figure 5 A network entity according to an embodiment is shown. Detailed Implementation

[0024] Embodiments of this disclosure will now be described in detail with reference to the accompanying drawings. It should be noted that in the drawings, the same or similar elements are preferably represented by the same or similar reference numerals. For clarity and brevity, detailed descriptions of known functions or configurations that might obscure the subject matter of this disclosure will be omitted.

[0025] The terminology used below is defined in consideration of the functionality in this disclosure and may vary depending on the intent or practice of the user and provider. Therefore, definitions should be based on the entire contents of this specification.

[0026] Some components in the accompanying drawings are exaggerated, omitted, or shown schematically. The dimensions of the components do not perfectly reflect their actual dimensions. In the various drawings, the same reference numerals are assigned to the same or corresponding components.

[0027] For ease of description, the terms and names defined in the 3GPP NR standard may be used. However, this disclosure is not limited to the terms and names mentioned above, and may similarly apply to systems based on other standards. In this document, in addition to mobile phones, "terminal" may also refer to other wireless communication devices, such as narrowband Internet of Things (NB-IoT) devices and sensors.

[0028] In the following description, a base station may be an entity that performs terminal resource allocation and may be at least one of a gNode B (gNB), eNodeB (eNB), Node B (NB), BS, radio access unit, base station controller, or node on a network. A terminal may include a UE, mobile station (MS), cellular phone, smartphone, computer, or multimedia system capable of performing communication functions. However, this disclosure is not limited thereto.

[0029] This disclosure can be applied to 3GPP NR (5G mobile communication standard). This disclosure can be applied to smart services based on 5G communication technology and IoT technology (e.g., smart homes, smart buildings, smart cities, smart cars or connected cars, healthcare, digital education, retail, security and safety services).

[0030] Although embodiments of this disclosure will be described below using LTE, LTE-A, LTE Pro, or 5G NR systems as examples, this disclosure can also be applied to other communication systems with similar technical backgrounds or channel types without substantially departing from the scope of this disclosure, and can be applied to other communication systems by those skilled in the art as appropriate with some modifications.

[0031] Figure 1 A 5G system according to an embodiment is shown.

[0032] Reference Figure 1A 5G mobile communication network may include a 5G UE (or terminal) 100, a 5G RAN (or base station, gNB (5G NodeB), eNB (evolved NodeB), etc.) 110, and a 5G core network. The 5G core network may include network functions (NFs), such as Access and Mobility Management Functions (AMF) 120 providing UE mobility management, Session Management Functions (SMF) 135 providing session management, User Plane Functions (UPF) 130 performing data transmission, Policy Control Functions (PCF) 140 providing policy control, Unified Data Management (UDM) 145 providing data management such as subscriber data and policy control data, and a Unified Data Repository (UDR) storing data from various NFs such as UDM 145. The 5G core network may also include NFs such as Network Slice Selection Function (NSSF) 160, Network Data Analysis Function (NWDAF) 151, Application Functions (AF) 170, Data Network (DN) 175, and Network Slice Admission Control Function (NSACF) 180.

[0033] In 3GPP systems, the conceptual link that connects network elements (NFs) to each other in 5G systems can be defined as a reference point. For example, a reference... Figure 1 The reference points included in the 5G system architecture can be as follows.

[0034] N1 is the reference point between UE 100 and AMF 120.

[0035] N2 is the reference point between (R)AN 110 and AMF 120.

[0036] N3 is the reference point between (R)AN 110 and UPF 130.

[0037] N4 is the reference point between SMF 135 and UPF 130.

[0038] N5 is the reference point between PCF 140 and AF 170.

[0039] N6 is the reference point between UPF 130 and DN 175.

[0040] N7 is the reference point between SMF 135 and PCF 140.

[0041] N8 is the reference point between UDM 145 and AMF 120.

[0042] N9 is the reference point between the two core UPF 130s.

[0043] N10 is the reference point between UDM 145 and SMF 135.

[0044] N11 is the reference point between AMF 120 and SMF 135.

[0045] N12 is the reference point between AMF 120 and the Authentication Server Function (AUSF).

[0046] N13 is the reference point between UDM 145 and AUSF.

[0047] N14 is the reference point between the two AMF 120s.

[0048] N15 is a reference point between PCF 140 and AMF 120 in non-roaming scenarios, or between PCF 140 and AMF 120 in the surveyed network in roaming scenarios.

[0049] In 5G systems, network slicing refers to the technology and architecture that enables multiple virtualized independent logical networks within a single physical network. To meet specific service / application requirements, network operators can configure virtual end-to-end networks, known as network slices, to provide services. In this context, network slices can be distinguished by an identifier (ID) called Single Network Slice Selection Auxiliary Information (S-NSSAI). During the terminal registration process (e.g., UE registration process), the network can send a set of allowed slices (e.g., allowed NSSAIs) to the terminal, and the terminal can send / receive application data through Protocol Data Unit (PDU) sessions generated via one of the S-NSSAIs (i.e., one network slice). In the following text, NF operations can be understood as Orchestration and Management (OAM) operations.

[0050] Figure 2 A method for sending DS policies and URSP rules to a UE according to an embodiment is shown.

[0051] Reference Figure 2 In step 200, the UE can use the second Subscription Permanent ID (SUPI) (SUPI2) to perform registration in the second AMF (AMF2) via the second RAN (RAN2).

[0052] In step 210, the UE can send a registration request message to the AMF via the first RAN (RAN1). The registration request message may include a DS function support indicator (DS capability) (e.g., an indicator indicating support for registration with two 3GPP accesses, an indicator indicating support for using two 3GPP accesses, etc.), or an indicator indicating that the DS function is available. The UE may include its UE ID based on the first SUPI (SUPI1) in the request message.

[0053] In step 220, when the AMF receives a registration request message from the UE, the AMF can determine whether to allow the UE to register based on the UE's subscription information. The AMF can send a registration response message (e.g., a registration acceptance message) to the UE through RAN1.

[0054] The AMF can perform PCF selection. Specifically, in step 231, when the message in step 210 includes DS capabilities, the AMF can send a discovery request message to the Network Repository Function (NRF) that includes at least one of the following information.

[0055] NF Capability: The AMF can include the capability of the NF to be searched in the NF Capability. When the message in step 210 includes the DS capability, the AMF can include the DS capability in the request message (discovery request).

[0056] Target NF type: Indicates the NF type of the PCF.

[0057] AMF instance ID: The NF instance ID of itself.

[0058] When the NRF receives the request message from the AMF in step 231, the NRF may include information about NF instances that meet the conditions included in the message in the response message (e.g., an NF profile containing the NF instance ID and NF instance address (Fully Qualified Domain Name (FQDN)). When the NF type in the message received from the AMF is PCF and the NF capability includes DS capability, the NRF may include one or more PCF instances that support DS capability in the response message (e.g., an NF with an NF profile including DS capability). In step 232, the NRF may send a discovery response message to the AMF.

[0059] AMF can choose one of the NF profiles (e.g., NF instances) included in the response message received from NRF in step 232.

[0060] In step 241, the AMF may send a creation request message for UE policy association establishment to the selected PCF. When the registration request message received from the UE in step 210 includes a DS function support indicator, the AMF may include the DS function support indicator in the creation request message sent to the PCF in step 241. The creation request message in step 241 may include the UE ID (e.g., SUPI1).

[0061] In step 242, the PCF may send a creation response message to the AMF, which includes the result (success or failure) of the UE policy association establishment request message received from the AMF.

[0062] In step 250, when the PCF accepts the UE policy association establishment in steps 241 and 242, the PCF can send the UE policy to the UE through the UE configuration update procedure. To generate the UE policy, the PCF can send a message to the UDR requesting policy control subscription information about the UE (e.g., a request). The UDR can send a response message to the PCF including the policy control subscription information. The policy control subscription information may include whether the UE is allowed to use the DS function, which can be provided for each S-NSSAI, Data Network Name (DNN), or Public Land Mobile Network (PLMN) ID. When a message received from the AMF includes an indicator indicating that the UE supports DS capabilities, or a message received from the UDR includes an indicator indicating that the UE is allowed to use DS capabilities, the PCF can determine to send the DS policy and the URSP rules reflecting the DS and used to select two 3GPP access points.

[0063] When the UE is a DS-enabled UE and is registered in two 3GPP accesses and receives service through different AMFs, the PCF can determine which of the two 3GPP accesses should be used for transmission (e.g., during transmission in steps 261 and 262, or during transmission in steps 271 and 272). For example, the PCF can prioritize the 3GPP access where the UE's connection to the network is active. When both 3GPP accesses are active (e.g., in the case of CM_CONNECTED), the PCF can prioritize the 3GPP access connected to a terrestrial radio access technology (RAT) by considering the RAT type (i.e., selecting the 3GPP access connected to a non-terrestrial RAT (e.g., NR (LEO), NR (MEO), or NR (GEO)) with the lowest priority).

[0064] In step 261, the PCF may send a request message to the AMF that manages the selected 3GPP access for updating the UE policy.

[0065] When the UE supports the DS function, the PCF can include the following information in the message sent to the AMF, within the transparent container (e.g., the UE policy container) to be sent to the UE.

[0066] DS Policy: The message may include whether two 3GPP accesses can be used simultaneously. This information can be provided for each PLMN. Furthermore, it may include whether the same service (e.g., S-NSSAI or DNN) is allowed to be transmitted through two 3GPP accesses. Even if the UE is allowed to use the DS function, the PCF may disallow the DS function based on service network conditions or policies. When the PCF needs to control the UE's energy usage, and the UE's remaining battery capacity is limited, the PCF may include information disallowing the UE from using two 3GPP accesses in the DS policy, or may not include information allowing the use of two 3GPP accesses in the message. Even if the UE and S-NSSAI / DNN are allowed to use the DS function (e.g., the ability to use two 3GPP accesses simultaneously), the PCF may disallow the DS function based on service network conditions or policies (e.g., when S-NSSAI / DNN is congested or its energy usage is too high).

[0067] UE Routing Policy (URSP) Rules: The message may include information about which PLMN and / or RAT type path should be prioritized for a specific service. In this case, the URSP rule may include a service descriptor (indicating information about the application service, which may include connectivity capabilities, server IP address / port number / protocol and / or server FQDN) and a routing descriptor (indicating information about the path used to send the application service, which may include access preferences, RAT preferences, PLMN preferences, S-NSSAI and / or DNN). Access preferences may include one or both of 3GPP access and non-3GPP access. RAT preferences may include RATs (e.g., they may be classified as 5G NR, 5G NR (LEO), etc., or classified as terrestrial network RATs and non-terrestrial network RATs). When multiple RATs are included, the RAT listed first may be prioritized. PLMN preferences may include PLMN IDs. When multiple PLMN IDs are included, the PLMN listed first may be prioritized.

[0068] In step 262, the AMF can receive the message from step 261, and if the message contains a transparent container to be sent to the UE, it can send the information to the UE via RAN1. When the message received from the AMF via RAN1 includes new configuration information, the UE can update the configuration information.

[0069] When the AMF receives the message in step 261 but the UE is unreachable, the AMF can send a response message to the PCF regarding step 261, the response message including information indicating failure. In this case, the PCF can execute the UE policy transmission to the UE through another 3GPP access in steps 271 and 272.

[0070] In step 280, when the UE configuration update command received from the AMF includes a DS policy or URSP rule, the UE can store the information. If pre-stored information exists, the pre-stored information can be deleted and the received information stored.

[0071] In step 290, when a connection request is generated from the upper layer, the UE can operate as follows.

[0072] When the DS policy allows the same service to be used in two 3GPP accesses, in the case of an upper-layer connection request, the UE can determine whether it has a PDU session matching the URSP rule in one of the 3GPP accesses that received the connection request. If no PDU session matching the URSP rule exists, the UE can send a PDU session establishment request to the AMF.

[0073] When the DS policy allows the same service to be used in two 3GPP accesses, in the case of upper-layer connection requests, the UE can send an establishment request to the AMF for a multi-access (MA) PDU session using two 3GPP accesses for the same S-NSSAI or DNN (e.g., a PDU session with two 3GPP access user planes).

[0074] When the DS policy does not allow the use of the same service in two 3GPP accesses, in the case of an upper-layer connection request, the UE can determine whether it has a PDU session matching the URSP rule in its two registered 3GPP accesses. If no PDU session matching the URSP rule exists, the UE can send a PDU session establishment request to the AMF. When a matching PDU session is found in the UE's two registered 3GPP accesses, the application service requested by the received upper layer can be sent through the PDU session.

[0075] When the DS policy does not allow the use of the same service in two 3GPP accesses, in the case of upper-layer connection requests, the UE can send the establishment request for the MA PDU session for the same S-NSSAI or DNN through only one 3GPP access (e.g., a PDU session with a 3GPP access user plane).

[0076] Figure 3 A session control method in a multi-access environment of a wireless communication system according to an embodiment is illustrated.

[0077] Reference Figure 3In step 310, the UE can use the first SUPI (SUPI1) to send a PDU session establishment request message through the registered 3GPP access network. The UE can send a non-access stratum (NAS) message including the PDU session establishment request message to the AMF through the first RAN (RAN1). The message may include the PDU session ID, S-NSSAI, DNN, and N1 session management (SM) container (PDU session establishment request).

[0078] When the AMF receives a PDU session establishment request message from the UE, the AMF can send an SM context creation request message to the SMF (e.g., the first SMF (SMF1)). The SM context creation request message may include the PDU session ID, S-NSSAI, DNN, and N1 SM container (PDU session establishment request).

[0079] When the SMF receives the above message from the AMF, the SMF can execute the PDU session establishment process.

[0080] In step 320, the SMF can send a NAS message including PDU session establishment acceptance to the UE through the AMF and RAN1.

[0081] In step 330, SMF1 may send a message to UDM indicating that SMF1 itself is the serving SMF of the PDU session. The message may include the following information.

[0082] SUPI (e.g., SUPI1), SMF ID, PDU session ID, access type, RAT type, and PLMN ID.

[0083] Upon receiving the aforementioned message, the UDM can store the information in the UDR. When a SUPI associated with SUPI1 exists, the UDM can also store information for a second SUPI (SUPI2).

[0084] UDM can send a response message to SMF1 that includes a result indicating successful registration.

[0085] In step 340, data transmission between the UE, RAN, and UPF via 3GPP access can be performed.

[0086] In step 351, the UE can use SUPI2 to send a PDU session establishment request message through a registered 3GPP access network. The UE can send a NAS message including the PDU session establishment request message to the AMF through the second RAN (RAN2). The message may include the PDU session ID, S-NSSAI, DNN, and N1 SM container (PDU session establishment request).

[0087] When the AMF receives a PDU session establishment request message from the UE, the AMF can determine whether to allow the PDU session establishment based on the UE's subscriber information. If no subscriber information exists, the AMF can send a subscriber information request message to the UDM.

[0088] UDM can include PDU session information (S-NSSAI, DNN, PDU session ID, SMF ID, access type, PLMN and / or similar information) about the associated SUPI (e.g., SUPI stored in the same subscription profile) in the response message sent to AMF.

[0089] AMF can determine from the message received from UDM whether there is a PDU session with the same S-NSSAI and DNN as the PDU session establishment request message received from the UE (or DS device) in step 351 for another 3GPP access (or another SUPI associated with the UE, other than the UE's SUPI).

[0090] When the PDU session exists, in step 352, the AMF may include the PDU session ID and an indicator indicating the use of the PDU session in the message sent to the UE (PDU session accept or reject message).

[0091] When the AMF receives a PDU session establishment request message from the UE in step 351, the AMF may send an SM context creation request message to the second SMF (SMF2). The message may include the PDU session ID, S-NSSAI, DNN, and N1 SM container (PDU session establishment request).

[0092] When SMF2 receives a PDU session establishment request message from AMF, SMF2 can execute the PDU session establishment process.

[0093] In step 353, SMF2 may send a subscription information request message to UDM. The request message may include SUPI2.

[0094] UDM can include PDU session information (S-NSSAI, DNN, PDU session ID, SMF ID, access type, PLMN and / or similar information) about the associated SUPI (e.g., SUPI stored in the same subscription profile) in the response message sent to SMF2.

[0095] SMF2 can determine in step 353 whether there is a PDU session in the message received from UDM that has the same S-NSSAI and DNN as those included in the message received from AMF in step 351.

[0096] When the PDU session exists, in step 361, SMF2 may include the PDU session ID and an indicator indicating the use of the PDU session in the message (PDU session accept or reject message) sent to the UE via AMF. SMF may send the aforementioned message to be sent to the UE to AMF.

[0097] In step 362, SMF2 can send a UE configuration information update request message to PCF to update the UE's configuration information. The UE configuration information update request message may include a DS policy update request indicator and the UE ID. When PCF receives the UE configuration information update message, PCF can... Figure 2 The configuration information is sent in steps 250, 261, and 262.

[0098] For example, step 361 can be performed before or after step 362.

[0099] When the SM PCF and UE PCF exist separately, if the SM PCF receives a UE configuration information update message from the SMF, the SM PCF can send a UE configuration information update request message including the UE ID and DS policy update request indicator to the UE PCF in step 363.

[0100] Figure 4 A session control method in a multi-access environment of a wireless communication system according to an embodiment is illustrated.

[0101] Reference Figure 4 In step 410, the UE can use SUPI1 to send a PDU session establishment request message through the registered 3GPP access network. The UE can send a NAS message including the PDU session establishment request message to the AMF through RAN1. The message may include the PDU session ID, S-NSSAI, DNN, and N1 session management (SM) container (PDU session establishment request).

[0102] When the AMF receives a PDU session establishment request message from the UE, the AMF can send an SM context creation request message to the SMF1. The SM context creation request message may include the PDU session ID, S-NSSAI, DNN, and N1 SM container (PDU session establishment request).

[0103] When the SMF receives the above message from the AMF, the SMF can execute the PDU session establishment process.

[0104] In step 420, the SMF can send a NAS message including PDU session establishment acceptance to the UE via the AMF and RAN (e.g., RAN1).

[0105] In step 430, SMF1 may send a message to UDM indicating that SMF1 itself is the serving SMF of the PDU session. The message may include the following information.

[0106] — SUPI (e.g., SUPI1), SMF ID, PDU session ID, access type, RAT type, and PLMN ID.

[0107] Upon receiving the aforementioned message, the UDM can store the information in the UDR. When a SUPI associated with SUPI1 exists, the UDM can also store information for a second SUPI (SUPI2).

[0108] UDM can send a response message to SMF1 that includes a result indicating successful registration.

[0109] In step 440, data transmission between the UE, RAN, and UPF via 3GPP access can be performed.

[0110] In step 451, the UE can use SUPI2 to send a PDU session establishment request message through a registered 3GPP access network. The UE can send a NAS message including the PDU session establishment request message to the AMF through the second RAN (RAN2). The message may include the PDU session ID, S-NSSAI, DNN, and N1 SM container (PDU session establishment request).

[0111] When the AMF receives a PDU session establishment request message from the UE, the AMF can send an SM context creation request message to the second SMF (SMF2). The message may include the PDU session ID, S-NSSAI, DNN, and N1 SM container (PDU session establishment request).

[0112] When SMF2 receives a PDU session establishment request message from AMF, SMF2 can execute the PDU session establishment process.

[0113] SMF2 can send a contract information request message to UDM. The request message may include SUPI2.

[0114] UDM can include PDU session information (S-NSSAI, DNN, PDU session ID, SMF ID, access type, PLMN and / or similar information) about the associated SUPI (e.g., SUPI stored in the same subscription profile) in the response message sent to SMF.

[0115] SMF2 can determine whether there is a PDU session among the messages received from UDM that has the same S-NSSAI and DNN as those included in the messages received from AMF in step 451.

[0116] When the PDU session exists, in step 461, SMF2 may include the PDU session ID and an indicator indicating the use of the PDU session in the message (PDU session accept or reject message) sent to the UE via AMF. SMF may send the aforementioned message to be sent to the UE to AMF.

[0117] In step 462, SMF2 can send a UE configuration information update request message to PCF to update the UE's configuration information. The UE configuration information update request message may include a DS policy update request indicator and the UE ID. When PCF receives the UE configuration information update message, PCF can use the above... Figure 2 Steps 250, 261, and 262 send the configuration information.

[0118] For example, step 461 can be performed before or after step 462.

[0119] When the SM PCF and UE PCF exist separately, if the SM PCF receives a UE configuration information update message from the SMF, the SM PCF can send a UE configuration information update request message including the UE ID and DS policy update request indicator to the UE PCF in step 463.

[0120] Figure 5 A network entity 500 according to an embodiment is shown. (Refer to...) Figure 5 Network entity 500 can correspond to Figure 1 , Figure 2 , Figure 3 or Figure 4 The NRF, UDR, NSSF, NWDAF, UDM, NSACF, AMF, SMF, PCF, AF, UE, RAN, AN, UPF, or DN shown.

[0121] Network entity 500 may include transceiver 510, processor 520, and memory 530. The transceiver 510, processor 520, and memory 530 of network entity 500 may operate according to the communication method of network entity 500 described above. However, the components of network entity 500 are not limited thereto. For example, network entity 500 may include more components than those described above. In one embodiment of this disclosure, transceiver 510, processor 520, and memory 530 may be implemented as a single chip. Processor 520 may include one or more processors.

[0122] Transceiver 510 can be collectively referred to as the receiver and transmitter of network entity 500, and can send signals to or receive signals from a terminal or base station. Signals sent to or received from a terminal or base station may include control information and data.

[0123] Transceiver 510 can perform the function of transmitting / receiving signals via a wireless channel. For example, transceiver 510 can receive signals via a wireless channel and output the signals to processor 520, and can also transmit signals output from processor 520 via a wireless channel.

[0124] Memory 530 can store programs and data required for the operation of network entity 500. Memory 530 can store control information or data included in signals received by network entity 500. Memory 530 may include storage media or combinations of storage media such as ROM, RAM, hard disk, CD-ROM, and DVD. Memory 530 may not be provided separately and may be included in processor 520. Memory 530 may include volatile memory, non-volatile memory, or a combination of volatile and non-volatile memory. Memory 530 can provide stored data upon request from processor 520.

[0125] Processor 520 can control a series of processes to enable network entity 500 to operate according to the embodiments of this disclosure described above. For example, processor 520 can receive and process control and data signals via transceiver 510. Processor 520 can transmit processed control and data signals via transceiver 510 and can write / read data to / from memory 530. Processor 520 can perform the functions of the protocol stack required by the communication standard. For this purpose, processor 520 may include at least one processor or microprocessor. Transceiver 510 or a portion of processor 520 may be referred to as a communication processor (CP).

[0126] Although this disclosure has been shown and described with reference to various embodiments thereof, those skilled in the art will understand that various changes in form and detail may be made without departing from the spirit and scope of this disclosure as defined by the appended claims and their equivalents.

Claims

1. A method for Access and Mobility Function (AMF) in a wireless communication system, the method comprising: Using the second SUPI, a PDU session establishment request message is received from a UE that supports dual bootstrapping (DS) function through a registered 3GPP access network; Based on the UE's subscriber information, determine whether there exists a PDU session for another 3GPP access that has the same S-NSSAI and DNN as those included in the PDU session establishment request message; as well as If a PDU session with the same S-NSSAI and DNN as the one included in the PDU session establishment request message exists for another 3GPP access, a PDU session rejection message is sent to the UE.

2. The method according to claim 1, wherein, The PDU session establishment request message is received by the second RAN in the non-access stratum (NAS) message.

3. The method according to claim 1, wherein, The PDU session establishment request message includes at least one of the following: PDU session ID, S-NSSAI, DNN, or N1 session management (SM) container.

4. The method according to claim 1, wherein, The subscriber information includes PDU session information about the first SUPI associated with the second SUPI.

5. The method according to claim 4, wherein, The first SUPI and the second SUPI are stored in the same contract configuration file.

6. The method according to claim 1, wherein, The PDU session rejection message includes the PDU session identifier (ID) of the PDU session having the same S-NSSAI and DNN, and an indicator indicating the use of the PDU session.

7. A method for a user equipment (UE) supporting dual-booting (DS) functionality in a wireless communication system, the method comprising: Using the second SUPI, a PDU session establishment request message is sent to the Access and Mobility Function (AMF) through the registered 3GPP access network; as well as Receive PDU session establishment response message from the Session Management Function (SMF). In the case where a PDU session with the same S-NSSAI and DNN as those included in the PDU session establishment request message exists for another 3GPP access, the PDU session establishment response message includes a PDU session rejection message.

8. The method according to claim 7, wherein, The second RAN sends the PDU session establishment request message to the AMF in a Non-Access Stratum (NAS) message.

9. The method according to claim 7, wherein, The PDU session establishment request message includes at least one of the following: PDU session ID, S-NSSAI, DNN, or N1 session management (SM) container.

10. The method according to claim 7, wherein, The PDU session establishment response message is received by the AMF and RAN.

11. The method according to claim 7, wherein, The PDU session rejection message includes the PDU session identifier (ID) of the PDU session having the same S-NSSAI and DNN, and an indicator indicating the use of the PDU session.

12. An Access and Mobility Function (AMF) in a wireless communication system, comprising: transceiver; as well as At least one processor, said at least one processor being configured to: Using the second SUPI, a PDU session establishment request message is received from a UE that supports dual bootstrapping (DS) function through a registered 3GPP access network; Based on the subscriber information of the UE, determine whether there is a PDU session with the same S-NSSAI and DNN as those included in the PDU session establishment request message for another 3GPP access. as well as If a PDU session with the same S-NSSAI and DNN as the one included in the PDU session establishment request message exists for another 3GPP access, a PDU session rejection message is sent to the UE.

13. The AMF according to claim 12, wherein, The PDU session establishment request message includes at least one of the following: PDU session ID, S-NSSAI, DNN, or N1 session management (SM) container.

14. A user equipment (UE) supporting dual-booting (DS) functionality in a wireless communication system, comprising: transceiver; as well as At least one processor, said at least one processor being configured to: Using the second SUPI, a PDU session establishment request message is sent to the Access and Mobility Function (AMF) through the registered 3GPP access network; and Receive PDU session establishment response message from the Session Management Function (SMF). In the case where a PDU session with the same S-NSSAI and DNN as those included in the PDU session establishment request message exists for another 3GPP access, the PDU session establishment response message includes a PDU session rejection message.

15. The UE according to claim 14, wherein, The PDU session establishment request message includes at least one of the following: PDU session ID, S-NSSAI, DNN, or N1 session management (SM) container.