KR20210021837A - Method and apparatus for providing multiple subscriptions in a wireless communication system - Google Patents

Abstract

According to an embodiment of the present disclosure, a method for providing a multiple subscription service in a wireless communication system includes the steps of: transmitting a registration request message to a base station; and receiving a response to the registration request message. The present invention can effectively support a communication service when a single terminal uses a plurality of subscription information in the wireless communication system.

Description

Method and apparatus for providing multiple subscription services in a wireless communication system {METHOD AND APPARATUS FOR PROVIDING MULTIPLE SUBSCRIPTIONS IN A WIRELESS COMMUNICATION SYSTEM}

The present disclosure generally relates to a wireless communication system, and more particularly, to a method and apparatus for effectively supporting a communication service when one terminal uses multiple subscription information in a wireless communication system.

4G (4 ^th generation) to meet the traffic demand in the radio data communication system increases since the commercialization trend, efforts to develop improved 5G (5 ^th generation) communication system, or pre-5G communication system have been made. For this reason, the 5G communication system or the pre-5G communication system is called a Beyond 4G Network communication system or a Long Term Evolution (LTE) system (Post LTE) system.

In order to achieve a high data rate, 5G communication systems are being considered for implementation in an ultra-high frequency (mmWave) band (eg, such as a 60 gigabyte (60 GHz) band). In order to mitigate the path loss of radio waves in the ultra-high frequency band and increase the propagation distance of radio waves, in 5G communication systems, beamforming, massive MIMO, and Full Dimensional MIMO (FD-MIMO) ), array antenna, analog beam-forming, and large scale antenna technologies are being discussed.

In addition, in order to improve the network of the system, in 5G communication systems, an evolved small cell, an advanced small cell, a cloud radio access network (cloud RAN), and an ultra-dense network ), Device to Device communication (D2D), wireless backhaul, moving network, cooperative communication, CoMP (Coordinated Multi-Points), and interference cancellation ), and other technologies are being developed.

In addition, in the 5G system, the advanced coding modulation (Advanced Coding Modulation, ACM) method of FQAM (Hybrid Frequency Shift Keying and Quadrature Amplitude Modulation) and SWSC (Sliding Window Superposition Coding), and advanced access technology, FBMC (Filter Bank Multi Carrier). ), NOMA (Non Orthogonal Multiple Access), and SCMA (Sparse Code Multiple Access) are being developed.

Due to the development of various IT (information technology) technologies, network equipment has evolved into a virtualized network function (NF) by applying virtualization technology. It is implemented in software form and can be installed/operated in various types of cloud or data center (DC). In particular, the NF can be freely expanded or scaled, installed (initiation), or terminated according to service requirements, system capacity, and network load.

In order to support various services in these various network structures, network slicing technology was introduced. Network slicing is a technology that logically composes a network as a set of network elements (NF) to support a specific service and separates it from other slices. One terminal can access two or more slices when receiving various services.

An embodiment of the present disclosure may provide a method and an apparatus for effectively supporting a communication service when a single terminal uses a plurality of subscription information in a wireless communication system.

A method of providing a multiple subscription service of a terminal in a wireless communication system according to an embodiment of the present disclosure includes: transmitting a registration request message to a base station; And receiving a response to the registration request message.

According to an embodiment of the present disclosure, in a wireless communication system, when one terminal uses a plurality of subscription information, a communication service may be effectively supported.

1 illustrates a wireless communication system according to various embodiments of the present disclosure.
2 illustrates a registration procedure of a terminal using two SIMs according to an embodiment of the present disclosure.
3 shows a PDU session establishment procedure of a terminal according to an embodiment of the present disclosure.
4 illustrates a method of processing a session by a terminal according to an embodiment of the present disclosure.
5 illustrates an IMS call processing method based on UDM session information according to an embodiment of the present disclosure.
6 is a diagram illustrating a configuration of a terminal according to an embodiment of the present disclosure.
7 is a diagram illustrating a configuration of a network entity according to an embodiment of the present disclosure.

Terms used in the present disclosure are used only to describe a specific embodiment, and may not be intended to limit the scope of other embodiments. Singular expressions may include plural expressions unless the context clearly indicates otherwise. Terms used herein, including technical or scientific terms, may have the same meaning as commonly understood by a person of ordinary skill in the technical field described in the present disclosure. Among the terms used in the present disclosure, terms defined in a general dictionary may be interpreted as having the same or similar meanings as those in the context of the related technology, and unless explicitly defined in the present disclosure, an ideal or excessively formal meaning Is not interpreted as. In some cases, even terms defined in the present disclosure cannot be interpreted to exclude embodiments of the present disclosure.

In various embodiments of the present disclosure described below, a hardware approach is described as an example. However, since various embodiments of the present disclosure include technology using both hardware and software, various embodiments of the present disclosure do not exclude a software-based approach. For example, when one NF (Network Function) is implemented in a software form instead of hardware, a virtualization is performed, or even when operating in a cloud, the embodiments of the present disclosure may be applied.

Hereinafter, the present disclosure relates to a method and apparatus for supporting various services in a wireless communication system. Specifically, the present disclosure describes a technique for effectively supporting various services when a single terminal has a plurality of subscription information in a wireless communication system. One terminal having a plurality of subscription information can be implemented as one terminal having two or more SIMs (Subscription Identity Modules) storing subscription information, and each SIM is in the form of a physical card (e.g., UICC), implemented in software form, or a combination of the two. In the following description of the embodiments of the present disclosure, the subscription information and the SIM may be used in an equivalent meaning to each other, and the SIM and USIM may be used in an equivalent meaning to each other.

Hereinafter, a term for identifying an access node used in the description, a term for a network entity (NE) or a network function (NF), a term for messages, network objects or networks A term referring to an interface between functions, a term referring to various identification information, and the like are exemplified for convenience of description. Accordingly, the present disclosure is not limited to terms to be described later, and other terms referring to objects having an equivalent technical meaning may be used.

For convenience of description below, this disclosure uses terms and names defined in 3GPP 3rd generation partnership project long term evolution (LTE) and 5G standards. However, the present disclosure is not limited by these terms and names, and may be equally applied to systems conforming to other standards.

1 illustrates a wireless communication system according to various embodiments of the present disclosure.

Referring to Figure 1, the 5G core network (Core Network) is AMF (Access and Mobility Management Function), SMF Session Management Function), PCF (Policy and Charging Function), NEF (Network Exposure Function), UDM (Unified Data Management) , UPF (User Plane Function), and other network functions (NF, Network Function). A terminal (User Equipment, Terminal, UE) can access the 5G core network through a base station (RAN, Radio Access Network, basestation, BS).

AMF (Access and Mobility Management Function) is a network function that manages wireless network access and mobility for a terminal. SMF (Session Management Function) is a network function that manages the PDN (Packet Data Network) connection provided to the terminal. This connection is called a PDU (protocol data unit) Session. Session information includes QoS information, billing information, and packet processing information. PCF (Policy and Charging Function) is a network function that applies a service policy of a mobile communication service provider, a charging policy, and a policy for a PDU session to a terminal. UDM (Unified Data Management) is a network function that stores and manages subscriber information, that is, subscription information. Network Exposure Function (NEF) allows access to information on managing a terminal in a 5G network, so it is possible to subscribe to a mobility management event of the terminal, a subscription to a session management event of the terminal, and a session ( Session) related information, setting the charging information of the corresponding terminal, requesting to change the PDU session policy for the corresponding terminal, etc.It is connected to the 5G core network NF (Network Function) to provide the corresponding NFs to the terminal. It delivers information about the terminal or performs a role of reporting information about the terminal to the outside. AF (Application Function) can use the services and functions provided by the 5G network through NEF. 5G-RAN (Radio Access Network) refers to a base station that provides a wireless communication function to a terminal. The UPF (User Plane Function) serves as a gateway for transmitting packets transmitted and received by the terminal, and is controlled by the SMF. UPF is connected to a data network (DN) and plays a role of transmitting data packets generated in a 5G system to an external data network. For example, the UPF is connected to a data network connected to the Internet, and can route data packets sent from the terminal to the Internet. UDR (Unified Data Repository) is a network function that stores and manages data. For example, the UDR may store terminal subscription information and provide terminal subscription information to the UDM. The UDR may store business policy information and provide business policy information to the PCF. UDR can store information related to network service exposure and provide it to NEF.

Each NF has defined the services they provide, which can be called Npcf, Nsmf, Namf, Nnef services, etc. For example, when AMF delivers session-related messages to SMF, a service (or API) called Nsmf_PDUSession_CreateSMContext can be used.

The terminal accesses the AMF through the base station, and can exchange a control plane signaling message with the 5G core network. In addition, the terminal may access the UPF through the base station to exchange data with a data network and user plane data.

Referring to FIG. 1, the terminal 100 according to an embodiment of the present disclosure may use two or more subscription information. At this time, each subscription information may be linked with one SIM (or USIM) card. That is, the terminal 100 using the two subscription information can use and manage the two SIM cards 101 and 102. In order to provide a mobile communication service to such a terminal, the mobile communication system may treat the terminal as two different terminals each using one SIM card. Alternatively, the mobile communication system may treat such a terminal as a single terminal using two SIM cards. An embodiment of the present disclosure may support all cases in which one terminal uses two or more subscription information, but for clarity of disclosure, a case in which two subscription information is used will be mainly described.

Referring to FIG. 1, the terminal 100 subscribes to PLMN A, and terminal subscription information of PLMN A may be stored in the SIM card A 101. The subscription information of the PLMN A of the terminal 100 may be stored in the UDM 134 of the PLMN A. The terminal 100 subscribes to the PLMN B, and the terminal subscription information of the PLMN B may be stored in the SIM card B 102. The subscription information of the PLMN B of the terminal 100 may be stored in the UDM 114 of the PLMN B.

Referring to FIG. 1, PLMN A and PLMN B may enter into a Service Level Agreement (SLA) and perform an operation to support a service to the terminal 100. The UDM 134 of PLMN A may store not only PLMN A's subscription information stored in SIM A 101 but also PLMN B's subscription information stored in SIM B 102 based on the SLA. Alternatively, the UDM 114 of PLMN B may store not only the PLMN B subscription information stored in the SIM B 102 based on the SLA, but also the PLMN A subscription information of the terminal 100 stored in the SIM A 101. .

When the terminal 100 according to an embodiment of the present disclosure accesses the PLMN B, the terminal 100 uses the SIM card B 102 that stores the PLMN B's subscription information to the AMF through the base station 105. You can register at (106). In addition, the terminal 100 downloads PLMN B's mobile operator policy information (operator policy, UE policy, URSP, etc.) from the PLMN B's PCF 113, and passes through the SMF 111, UPF 112 You can use it after making In this case, the AMF 106 serves as a serving AMF of the local PLMN that provides the service provided by the PLMN B to the terminal 100. In addition, the terminal 100 registers with the AMF 106 via the base station 105 using the SIM card A 101 storing the PLMN A subscription information, and from the PCF 113 of the PLMN A Download PLMN A's mobile operator policy information (operator policy, UE policy, URSP, etc.), and download V-SMF (121), H-SMF (131), V-UPF (122), H-UPF (132) After that, you can establish and use a PDU session. In this case, the AMF 106 serves as a serving AMF of the VPLMN that provides the service provided by PLMN A to the terminal 100.

The terminal 100 may provide a setting menu so that the user can set the priority of the SIMs of the terminal 100. The user may set the priority of the SIM (for example, primary USIM, secondary USIM, etc.) in the terminal 100. The SIM of the terminal 100 may be detachable, install/uninstall, or download. The priority of SIM can be set in various ways as follows.

When there is one SIM in the terminal 100, the priority of the corresponding SIM may be set to primary. When a SIM is additionally inserted/installed/downloaded in the terminal 100, the priority of the second SIM may be set to secondary. Alternatively, priority may be determined between the two SIMs according to the user's settings.

When there are two SIMs in the terminal 100, the priority of each SIM may be set (eg, primary, secondary). When the primary SIM of the terminal 100 is detached/deleted, the priority of the secondary SIM of the terminal 100 may be changed to primary. Alternatively, the priority of the secondary SIM of the terminal 100 is not changed, and the primary SIM may not exist as it is.

When there are two SIMs in the terminal 100, the terminal 100 may perform the registration procedure twice to register each SIM. That is, the terminal 100 may perform one registration procedure per SIM. In the order of registration, a registration process for a primary SIM card may be performed first, and then a registration process for a secondary SIM card may be performed. Alternatively, the order of the registration procedure may be performed regardless of the priority of the SIM. That is, for example, a registration procedure for a secondary SIM may be performed first, and then a registration procedure for a primary SIM may be performed.

This disclosure describes a method of selecting the same AMF 106 while performing two registration procedures requested by the terminal 100. That is, the AMF 106 that has processed the first registration procedure of the terminal 100 must be selected for the second registration procedure as well to be able to process the second registration procedure.

2 shows a registration procedure of a terminal using two SIMs according to an embodiment of the present disclosure.

Referring to FIG. 2, the terminal 100 can perform a procedure for registering the SIM A 101 (steps 200 to 212) and a procedure for registering the SIM B 102 (steps 220 to 230). have. Regarding the terminal registration procedure, the registration procedure for SIM A may be performed first, and the registration procedure for SIM B may be performed later. Alternatively, a registration procedure for SIM B may be performed first, and a registration procedure for SIM A may be performed later.

There may be various methods of registering the terminal 100 using two or more SIMs in the mobile communication system. For example, the terminal 100 may provide information related to multiple SIM (MUSIM) while making a request for registration of a mobile communication system. Alternatively, the mobile communication system receiving the registration request from the terminal 100 may process the registration request based on the subscription information (UE subscription) in the 5G core network. Alternatively, a method of processing a registration request may vary depending on which mobile communication service provider (PLMN) the terminal 100 first performs the registration procedure with. The following describes how to select the same AMF in such various situations.

[Example 1]

Embodiment 1 describes an example in which the terminal 100 provides information related to multiple SIM (MUSIM) while requesting initial registration of a mobile communication system.

Referring to FIG. 2, the terminal 100 may perform a first registration procedure.

In step 200, the terminal 100 may perform a PLMN A registration procedure for the SIM A 101. The terminal 100 may transmit a Registration Request message to the base station 105. The Registration Request message may include a terminal ID (eg, SUPI (Subscription Permanent Identifier) A, 5G-GUTI (Globally Unique Temporary Identifier) A, etc.) linked to the SIM A 101. In addition, in the Registration Request message, the terminal ID (e.g., SUPI B, 5G-GUTI B, etc.) linked to the SIM B 102 and the PLMN ID (e.g., PLMN ID indicating B), etc. may be included.

In step 202, the base station 105 may transmit a Registration Request message to the AMF 106 based on the information received from the terminal 100.

In step 204, the AMF 106 transmits the terminal ID associated with the SIM A 101 to the UDM 134, and the UDM 134 can return the subscription information corresponding to the received terminal ID to the AMF 106. have. The AMF 106 is based on information received from the terminal 100 (for example, SIM B related information) and/or terminal subscription information received from the UDM 134, and the terminal 100 uses the MUSIM function. Can be judged. AMF 106 may create a UE context for the terminal 100. Or, if the UE context for the terminal 100 already exists, the UE context can be updated. The UE context includes the terminal ID (e.g., SUPI A, 5G-GUTI A, SUPI B, 5G-GUTI B, etc.), the PLMN ID associated with the terminal ID, and the terminal capability (e.g., MUSIM function support). I can.

In the first embodiment, steps 206 and 208 may be skipped.

In step 210, the AMF 106 may be connected to the PCF 133 through the V-PCF 123 to establish a policy association.

In step 212, the AMF 106 may transmit a Registration Accept message to the terminal 100. The Registration Accept message may include a terminal ID (eg, 5G-GUTI A) through which the terminal 100 is registered in PLMN A and can receive a service. The terminal 100 may store the received terminal ID and use it for a later procedure.

In step 220, the terminal 100 may perform a second registration procedure. That is, the terminal 100 may perform a PLMN B registration procedure for the SIM B 102. The terminal 100 may transmit a Registration Request message to the base station 105. The registration request message may include a terminal ID (eg, SUPI B, 5G-GUTI B, etc.) linked to the SIM B 102. In addition, in the Registration Request message, the terminal ID (e.g., SUPI A, 5G-GUTI A, etc.) associated with the SIM A 101, and the PLMN ID (e.g., PLMN ID indicating B), etc. may be included. In addition, the terminal 100 tells the base station 105 the terminal ID received in the first registration procedure, that is, the terminal ID received in step 208 (e.g., 5G GUTI A) to information indicating AMF among the terminal IDs (e.g. For example, you can send a GUAMI (Globally Unique AMF Identifier).

In step 222, the base station may select the AMF that performed the first registration procedure based on information received from the terminal (eg, GUAMI among 5G GUTI A to 5G GUTI A). The base station can transmit a Registration Request message to the selected AMF.

In step 224, the AMF 106 transmits the terminal ID associated with the SIM B 102 to the UDM 114, and the UDM 114 can return the subscription information corresponding to the received terminal ID to the AMF 106. have. The AMF 106 is based on the information received from the terminal 100 (eg, SIM A related information) and/or the terminal subscription information received from the UDM 114, and the terminal 100 uses the MUSIM function. Can be judged. AMF 106 may update the UE context for the terminal 100. The UE context includes the terminal ID (e.g., SUPI A, 5G-GUTI A, SUPI B, 5G-GUTI B, etc.), the PLMN ID associated with the terminal ID, and the terminal capability (e.g., MUSIM function support). I can.

In the first embodiment, step 226 may be skipped.

In step 228, the AMF 106 may be connected with the PCF 113 to establish a policy association.

In step 230, the AMF 106 may transmit a Registration Accept message to the terminal 100. The Registration Accept message may include a terminal ID (eg, 5G-GUTI B) through which the terminal 100 is registered with the PLMN B to receive a service. The terminal 100 may store the received terminal ID and use it for a later procedure.

According to the first embodiment, in step 212, the AMF 106 may allocate a terminal ID (5G-GUTI A) indicating the SIM A 101 of the terminal 100. In step 230, the AMF 106 may allocate a terminal ID (5G-GUTI B) indicating the SIM B 102 of the terminal 100. In this case, information indicating AMF among 5G-GUTI A (GUAMI) and information indicating AMF among 5G-GUTI B (GUAMI) may be the same. That is, after the initial registration procedure, for example, based on the terminal ID-related information (5G-GUTI A to 5G-GUTI B to GUAMI) provided by the terminal in step 222, the base station 105 is the same AMF ( 106), and a Non Access Stratum (NAS) message can be delivered to the AMF.

Through this procedure, the terminal 100 may receive the PLMN A service and the PLMN B service from the same AMF 106. The AMF 106 may store and manage information for the SIM A 101 and the information for the SIM B 102 in the UE context of the terminal 100. [Embodiment 2]

Embodiment 2 describes an example in which a mobile communication system receiving a request for initial registration of a mobile communication system of the terminal 100 processes a registration request based on UE subscription in a 5G core network. That is, the difference between Embodiment 2 and Embodiment 1 is that in Embodiment 1, the terminal processes the registration procedure by using multi-sim-related information included in the Registration Request message, whereas in the case of Embodiment 2, the terminal processes the registration request message. It does not include multi-sim related information.

The UDM 134 of the PLMN A according to an embodiment of the present disclosure may store not only subscription information linked to the SIM A 101 of the terminal 100 but also subscription information linked to the SIM B 102. For example, PLMN A may enter into an SLA with PLMN B, and may store SIM B 102 information of PLMN B in UDM 134. PLMN A according to an embodiment of the present disclosure may sell SIM B 102 of PLMN B to subscriber UE 100 of PLMN A. The SIM B 102 may be a SIM supporting a multi-sim function. The mobile communication system can manage a range of SUPIs that support multi-sim functions. The mobile communication system is based on the SUPI interlocked with the SIM B 102 (for example, if the SUPI is included in the SUPI range supporting the multi-sim function), whether the SIM B 102 is a SIM supporting the multi-sim function. You can check.

Referring to FIG. 2, the terminal 100 may perform a first registration procedure.

In step 200, the terminal 100 may perform a PLMN A registration procedure for the SIM A 101. The terminal 100 may transmit a Registration Request message to the base station 105. The Registration Request message may include a terminal ID (eg, SUPI A, 5G-GUTI A, etc.) linked with SIM A 101.

In step 202, the base station 105 may transmit a Registration Request message to the AMF 106 based on the information received from the terminal 100. For example, upon receiving SUPI A, the base station 105 may transmit a message by selecting AMF according to the local configuration of the base station.

In step 204, the AMF 106 tells the UDM 134 a terminal ID (e.g., SUPI A, 5G-GUTI A, etc.) linked to the SIM A 101, and the serving PLMN ID to which the terminal 100 is currently connected ( That is, for example, the PLMN ID of PLMN B) may be transmitted. The UDM 134 may find corresponding subscription information based on the received terminal ID, serving PLMN ID, and the like. For example, when the terminal 100 corresponding to SUPI A connects to PLMN B, the UDM 134 has the SIM B 102 that the terminal 100 can use in PLMN B, and SIM B 102 It can be seen that the terminal ID linked to is SUPI B. The UDM 134 tells the AMF 106 terminal subscription information, a MUSIM indicator that the terminal 100 can use the MUSIM function, a terminal ID (e.g., SUPI B) linked with the SIM B 102, etc. You can reply. Based on the information received from the UDM 134, the AMF 106 knows that the terminal 100 is a terminal using the MUSIM function, and may decide to perform step 206. AMF 106 may create a UE context for the terminal 100. Or, if the UE context for the terminal 100 already exists, the UE context can be updated. The UE context includes the terminal ID (e.g., SUPI A, 5G-GUTI A, SUPI B, 5G-GUTI B, etc.), the PLMN ID associated with the terminal ID, and the terminal capability (e.g., MUSIM function support). I can.

In step 206, the AMF 106 may register itself with the UDM 114 of PLMN B as the serving AMF of the terminal 100. To this end, the AMF 106 tells the UDM 114 a terminal ID linked to the SIM B 102 (for example, SUPI B obtained in step 204) and the AMF 106's own information (for example, AMF ID ) Can be transmitted. The UDM 114 may store the AMF 106 as a serving AMF of a terminal corresponding to SUPI B.

In the second embodiment, step 208 may be skipped.

In step 210, the AMF 106 may be connected to the PCF 133 through the V-PCF 123 to establish a policy association.

In step 212, the AMF 106 may transmit a Registration Accept message to the terminal 100. The Registration Accept message may include a terminal ID (eg, 5G-GUTI A) through which the terminal 100 is registered in PLMN A and can receive a service. The terminal 100 may store the received terminal ID and use it for a later procedure.

In step 220, the terminal 100 may perform a second registration procedure. That is, the terminal 100 may perform a PLMN B registration procedure for the SIM B 102. The terminal 100 may transmit a Registration Request message to the base station 105. The registration request message may include a terminal ID (eg, SUPI B, 5G-GUTI B, etc.) linked to the SIM B 102.

In step 222, the base station 105 may transmit a Registration Request message to the AMF 106 based on the information received from the terminal 100. For example, when SUPI B is received, the base station 105 may transmit a message by selecting an AMF according to the local configuration of the base station.

In step 224, the AMF 106 transmits the terminal ID associated with the SIM B 102 to the UDM 114, and the UDM 114 can return the subscription information corresponding to the received terminal ID to the AMF 106. have. The UDM 114 may return the serving AMF information of the terminal 100 stored in step 206 to the AMF 106. The AMF 106 indicates that the terminal 100 is a terminal using the MUSIM function based on the terminal ID (for example, when SUPI B is included in the SUPI range supporting the multi-sim function) or information received from the UDM 114. I can confirm.

In step 226, the AMF 106 determines the serving AMF for the terminal based on the serving AMF information received from the UDM 114, and if it is different from the AMF 106, the AMF reallocation procedure to the corresponding serving AMF You can do it. In describing the steps below, it is assumed that the AMF 106 is serving AMF.

AMF 106 may update the UE context for the terminal 100. The UE context includes the terminal ID (e.g., SUPI A, 5G-GUTI A, SUPI B, 5G-GUTI B, etc.), the PLMN ID associated with the terminal ID, and the terminal capability (e.g., MUSIM function support). I can.

In step 228, the AMF 106 may be connected with the PCF 113 to establish a policy association.

In step 230, the AMF 106 may transmit a Registration Accept message to the terminal 100. The Registration Accept message may include a terminal ID (eg, 5G-GUTI B) through which the terminal 100 is registered in PLMN B and can receive a service. The terminal 100 may store the received terminal ID and use it for a later procedure.

According to the second embodiment, in step 204, the AMF 106 may confirm that the terminal is a terminal using the MUSIM function based on the subscription information received from the UDM. Accordingly, in step 206, the AMF 106 processing the registration procedure of SIM A may store serving AMF information of the terminal in the UDM 114 of PLMN B. In step 224, the AMF 106 processing the registration procedure of SIM B may obtain the serving AMF information of the terminal (ie, AMF information processing the registration procedure of SIM A) from the UDM 114, and serve as the serving AMF. AMF reassignment procedure can be performed.

Through this procedure, the terminal 100 may receive the PLMN A service and the PLMN B service from the same AMF 106. The AMF 106 may store and manage information for the SIM A 101 and the information for the SIM B 102 in the UE context of the terminal 100.

[Example 3]

Embodiment 3 describes an example in which a mobile communication system receiving a request for initial registration of a mobile communication system of the terminal 100 processes a registration request based on UE subscription in a 5G core network. That is, the difference between Example 2 and Example 3 is that in Example 2, the terminal performs SIM A registration first and then SIM B registration later, whereas in Example 3, the terminal performs SIM B registration first. In this case, SIM A registration is performed later.

Referring to FIG. 2, the terminal 100 may perform a first registration procedure with SIM B.

In step 220, the terminal 100 may perform a PLMN B registration procedure for the SIM B 102. The terminal 100 may transmit a Registration Request message to the base station 105. The registration request message may include a terminal ID (eg, SUPI B, 5G-GUTI B, etc.) linked to the SIM B 102.

In step 222, the base station 105 may transmit a Registration Request message to the AMF 106 based on the information received from the terminal 100. For example, when SUPI B is received, the base station 105 may transmit a message by selecting an AMF according to the local configuration of the base station.

In step 224, the AMF 106 transmits the terminal ID associated with the SIM B 102 to the UDM 114, and the UDM 114 can return the subscription information corresponding to the received terminal ID to the AMF 106. have. The AMF 106 indicates that the terminal 100 is a terminal using the MUSIM function based on the terminal ID (eg, when SUPI B is included in the SUPI range supporting the multi-sim function) or information received from the UDM 114. I can confirm. AMF 106 may create a UE context for the terminal 100. Or, if the UE context for the terminal 100 already exists, the UE context can be updated. The UE context includes the terminal ID (e.g., SUPI A, 5G-GUTI A, SUPI B, 5G-GUTI B, etc.), the PLMN ID associated with the terminal ID, and the terminal capability (e.g., MUSIM function support). I can.

In the third embodiment, step 226 may be skipped.

In step 228, the AMF 106 may be connected with the PCF 113 to establish a policy association.

In step 230, the AMF 106 may transmit a Registration Accept message to the terminal 100. The Registration Accept message may include a terminal ID (eg, 5G-GUTI B) through which the terminal 100 is registered with the PLMN B to receive a service. The terminal 100 may store the received terminal ID and use it for a later procedure.

In step 200, the terminal 100 may perform a second registration procedure. That is, the terminal 100 may perform a PLMN A registration procedure for the SIM A 101. The terminal 100 may transmit a Registration Request message to the base station 105. The Registration Request message may include a terminal ID (eg, SUPI A, 5G-GUTI A, etc.) linked with SIM A 101.

In step 202, the base station 105 may transmit a Registration Request message to the AMF 106 based on the information received from the terminal 100. For example, upon receiving SUPI A, the base station 105 may transmit a message by selecting AMF according to the local configuration of the base station.

In step 204, the AMF 106 tells the UDM 134 a terminal ID (e.g., SUPI A, 5G-GUTI A, etc.) linked to the SIM A 101, and the serving PLMN ID to which the terminal 100 is currently connected ( That is, for example, the PLMN ID of PLMN B) may be transmitted. The UDM 134 may find corresponding subscription information based on the received terminal ID, serving PLMN ID, and the like. For example, when the terminal 100 corresponding to SUPI A connects to PLMN B, the UDM 134 has the SIM B 102 that the terminal 100 can use in PLMN B, and SIM B 102 It can be seen that the terminal ID linked to is SUPI B. The UDM 134 tells the AMF 106 terminal subscription information, a MUSIM indicator that the terminal 100 can use the MUSIM function, a terminal ID (e.g., SUPI B) linked with the SIM B 102, etc. You can reply. Based on the information received from the UDM 134, the AMF 106 knows that the terminal 100 is a terminal using the MUSIM function, and may decide to perform step 206.

In step 206, the AMF 106 may request serving AMF information of the terminal 100 from the UDM 114 of the PLMN B. To this end, the AMF 106 may transmit a terminal ID (eg, SUPI B obtained in step 204) linked with the SIM B 102 to the UDM 114. The UDM 114 may provide serving AMF information (eg, AMF ID) of the terminal 100 registered in step 224 to the AMF 106.

In step 208, based on the serving AMF information received from the UDM 114, the AMF 106 determines the serving AMF for the terminal, and if different from the AMF 106, the AMF reallocation procedure to the corresponding serving AMF You can do it. In describing the steps below, it is assumed that the AMF 106 is serving AMF.

AMF 106 may update the UE context for the terminal 100. The UE context includes the terminal ID (e.g., SUPI A, 5G-GUTI A, SUPI B, 5G-GUTI B, etc.), the PLMN ID associated with the terminal ID, and the terminal capability (e.g., MUSIM function support). I can.

In step 210, the AMF 106 may be connected to the PCF 133 through the V-PCF 123 to establish a policy association.

In step 212, the AMF 106 may transmit a Registration Accept message to the terminal 100. The Registration Accept message may include a terminal ID (eg, 5G-GUTI A) through which the terminal 100 is registered in PLMN A and can receive a service. The terminal 100 may store the received terminal ID and use it for a later procedure.

According to Example 3, in step 224, the AMF 106 may confirm that the terminal is a terminal using the MUSIM function based on terminal subscription information (for example, when SUPI B is included in the SUPI range supporting the multi-sim function). . In step 224, the AMF 106, which is processing the registration procedure of SIM B, may store serving AMF information of the terminal in the UDM 114 of PLMN B. In step 204, the AMF 106 may confirm that the terminal is a terminal using the MUSIM function based on the subscription information received from the UDM. Accordingly, the AMF 106 processing the SIM A registration procedure in step 206 can obtain the serving AMF information of the terminal from the UDM 114 and can perform the AMF reallocation procedure with the serving AMF.

Through this procedure, the terminal 100 may receive the PLMN A service and the PLMN B service from the same AMF 106. The AMF 106 may store and manage information for the SIM A 101 and the information for the SIM B 102 in the UE context of the terminal 100.

[Example 4]

Embodiment 4 may define an AMF set composed of AMFs supporting a terminal supporting the MUSIM function. The base station 105 to the AMF 106 according to an embodiment of the present disclosure may recognize that the terminal 100 is a terminal supporting the MUSIM function during the registration procedure. The base station 105 to the AMF 106 receiving the registration request message of the terminal may transmit the Registration Request message received in steps 202 to 208, and 222 to 226 to an AMF set supporting the MUSIM function.

Through this procedure, the terminal 100 may receive the PLMN A service and the PLMN B service from the same AMF 106. The AMF 106 may store and manage information for the SIM A 101 and the information for the SIM B 102 in the UE context of the terminal 100.

In Embodiment 1, Embodiment 2, Embodiment 3, and Embodiment 4 of the present disclosure, a method of selecting the same AMF among the registration procedures of terminals using two or more SIMs has been described.

According to an embodiment of the present disclosure, the base station 105 can know whether the terminal is a terminal supporting the MUSIM function based on information (eg, MUSIM indicator, etc.) transmitted by the terminal received in steps 200 to 220. have.

When receiving a Registration Request message from a terminal supporting the MUSIM function, the base station 105 according to an embodiment of the present disclosure may transmit the Registration Request message to an AMF belonging to an AMF set supporting MUSIM.

According to an embodiment of the present disclosure, the AMF 106 is based on information transmitted by the terminal received in steps 202 to 222 (for example, a MUSIM indicator, a PLMN-related terminal ID other than the current registration procedure, etc.). It is possible to know whether the terminal is a terminal supporting the MUSIM function. Alternatively, the AMF 106 determines whether the terminal ID (e.g., SUPI) received from the terminal falls within the terminal ID range (e.g., a range of SUPIs, etc.) of the terminal supporting the MUSIM function, and If the received terminal ID (eg, SUPI) falls within the range of the terminal ID of the terminal supporting the MUSIM function, the terminal may be determined as a terminal supporting the MUSIM function. Alternatively, the AMF 106 may know whether the terminal is a terminal supporting the MUSIM function based on the subscription information received from the UDM in steps 204 to 206 to 224.

According to an embodiment of the present disclosure, the AMF 106 may check the serving AMF of the terminal based on the subscription information received from the UDM in steps 204 to 206 to 224. If the serving AMF and the AMF of the terminal are different, the AMF reallocation procedure may be performed in steps 208 to 226. If the serving AMF of the terminal does not exist, the AMF can register itself as a serving AMF.

According to an embodiment of the present disclosure, the AMF 106 may obtain policy information for providing the MUSIM function from the PCF in steps 210 to 228. This MUSIM policy information includes whether the terminal can use the MUSIM function, the priority between the multiple subscription information of the terminal (for example, SIM A may have a higher priority than SIM B), and the same service that the terminal uses (for example, , Voice phone service, S-NSSAI, DNN, etc.) between subscription information (e.g., calls made to SIM A's phone number have higher priority than calls made to SIM B's phone numbers, eMBB S- In the case of NSSAI, SIM B has a higher priority than SIM A, in the case of IMS DNN, SIM A has a higher priority than SIM B, etc.) information may be included. The MUSIM policy information that the AMF 106 receives from the PCF may be used to process the session priority of the terminal described in FIGS. 3 to 4.

In Embodiments 5, 6, and 7 of the present disclosure, a session processing method of a terminal using two or more SIMs will be described. The terminal according to an embodiment of the present disclosure may register with PLMN A and PLMN B through the procedure shown in FIG. 2, and establish a PDU session through the procedure shown in FIG. 3 (PDU session establishment). For example, the terminal establishes a PDU session (hereinafter referred to as PDU Session A) through the 5G core network of PLMN A in order to make a voice call to a phone number linked to SIM A, and transmits and receives data to and from the DN 135. I can. In addition, the terminal may establish a PDU session (hereinafter referred to as PDU Session B) through the 5G core network of PLMN B in order to make a voice call to the phone number linked to the SIM B, and transmit and receive data with the DN 115. . Referring to FIG. 1, the PDU session established by the UE to PLMN A is managed by the base station 105 and the AMF 106, the H-SMF 131, and the data through the base station 105 and the UPF 132. Can be transmitted and received. In addition, the PDU session established by the terminal to the PLMN B is managed by the base station 105 and the AMF 106, the SMF 111, and data may be transmitted and received through the base station 105 and the UPF 112. That is, PDU sessions established by the UE in different PLMNs are managed by different SMFs 131 and 111, and data is transmitted and received through different UPFs 132 and 112. On the other hand, in this case, the PDU session may share the same AMF 106.

Such a terminal can simultaneously manage PDU session A and PDU session B. However, such a terminal may not be able to simultaneously transmit and receive data in PDU session A and PDU session B. For example, it is assumed that the terminal 100 establishes a PLMN A and a PDU session A, and the PDU session A is in an activation state (data transmission/reception). In addition, it is assumed that the terminal 100 has established the PLMN B and the PDU session B, but the PDU session B is in a deactivate state (no data transmission/reception). In this case, the mobile communication system may process the session of the terminal differently according to the priority between PLMNs or between PLMNs for a specific service. For example, assuming that PLMN A has a higher priority than PLMN B, when a service is being used with PDU session A established in PLMN A and downlink data occurs in PDU session B established in PLMN B, mobile communication The system may not transmit downlink data of PDU session B to the terminal based on the priority of PDU session A and PDU session B. Conversely, when the service is being used by PDU session B established by PLMN B, and data is generated by PDU session A established by PLMN A, the mobile communication system uses PDU session B based on the priority of PDU session A and PDU session B. The session can be stopped and data for PDU session A can be transmitted to the terminal. For such session processing, various embodiments (AMF-level session processing, SMF-level session processing, UDM-level session processing, and IMS-level session processing) described in the present disclosure may be applied. Embodiment 5 describes a method of managing and processing session information and priority of a terminal in AMF. In Embodiment 6, a method of managing and processing session information and priority of a terminal in an SMF based on an AMF notification message is described. Embodiment 7 describes a method of managing and processing session information and priority of a terminal in UDM based on an AMF notification message. In addition, in Embodiment 7, an IMS call processing method is described based on session information of UDM.

[Example 5]

Embodiment 5 describes a method of managing session information and priority of a terminal and processing multiple sessions in AMF when a terminal using two or more SIMs simultaneously establishes a PDU session using two or more SIMs.

3 shows a PDU session establishment procedure of a terminal according to an embodiment of the present disclosure.

3, in step 300, the terminal 100 may transmit a PDU Session establishment request message. The PDU Session establishment request message may include information such as a terminal ID (eg, 5G-GUTI, SUPI, etc.) linked with a SIM intended to be used by the terminal, a PDU Session ID, S-NSSAI, DNN, and the like.

In step 302, the base station 105 may transmit a PDU establishment request message to the AMF 106. The AMF 106 may determine the priority of the requested PDU session based on the information received from the terminal in step 300/302 or the MUSIM policy information received in steps 210 of FIG. 2 to 228 of FIG. 2. The AMF 106 may include PDU session information established by the UE in the UE context of the UE. The PDU session information may include a PDU session ID, an S-NSSAI and/or DNN to which the PDU session is linked, whether the PDU session is activated (activation/deactivation), the priority of the PDU session, and the PLMN ID to which the PDU session belongs.

From step 304 to step 310, a PDU session can be established. In step 312, the AMF 106 may inform the terminal 100 that the PDU session establishment has been completed.

Using this method, the terminal 100 may establish a PDU session through PLMN A and establish a PDU session through PLMN B. The AMF 106 may store and manage PDU session information established by the UE through PLMN A and PLMN B.

In the fifth embodiment, steps 314, 316, 330, and 340 may be omitted.

4 illustrates a method of processing a session by a terminal according to an embodiment of the present disclosure.

Referring to FIG. 4, in step 400, the terminal 100 may start a service linked to SIM A (for example, a voice call to a phone number linked to SIM A) using a PDU session A established with PLMN A. . The AMF 106 may detect that a change has occurred in the session established by the terminal in PLMN A. Accordingly, the AMF may determine that the PDU session A has been activated, and store information of the PDU session A of the UE context as activation.

In Example 5, step 402 may be omitted.

In step 404, downlink data for PDU session B targeting SIM B 102 may be generated. If the AN tunnel information for the PDU session B does not exist in the UPF 112, the UPF 112 may transmit a data notification message to the SMF 111 in step 406.

In step 408, the SMF 111 may transmit a Namf_Communication_N1N2MessageTransfer message to the AMF 106. Upon receiving the message, the AMF 106 may determine that the UE is currently using PDU session A in PLMN A, and that PLMN A has a higher priority than PLMN B based on the UE context. In this case, the AMF 106 may decide not to transmit downlink data directed to SIM B to the terminal in order to allow the terminal to continue to use the service being used by SIM A. Accordingly, the AMF may return a reject message to the SMF 410 in step 410. In step 412, the SMF 111 may transmit a failure indication message indicating that data transmission has failed to the UPF 112.

The failure indication message sent by the SMF to the UPF in step 412 may include a cause value indicating that paging is currently impossible due to the MUSIM function.

In step 408, if PLMN A has a lower priority than PLMN B, the AMF 106 may transmit a paging message to SIM B of the terminal to transmit downlink data targeting SIM B to the terminal.

[Example 6]

Embodiment 6 describes a method of managing session information and priority of a terminal in SMF and processing multiple sessions when a terminal using two or more SIMs simultaneously establishes a PDU session by using two or more SIMs.

Referring to FIG. 3, the AMF 106 that has processed the PDU session request message through steps 300 to 302 in the method described in the fifth embodiment may transmit a PDU session request message to the SMF in step 304. In this case, priority information of the PDU session may also be delivered to the SMF. When the PDU session uses the subscription information of SIM A (ie, 5G-GUTI A is set as the terminal ID), the SMF may be the H-SMF 131. That is, the AMF 106 may transmit a PDU establishment request message to the H-SMF 131 via the V-SMF 121. When the PDU session uses the subscription information of SIM B (ie, 5G-GUTI B is set as the terminal ID), the SMF may be the SMF 111.

In step 306, the SMF may obtain terminal subscription information from the UDM. When the PDU session uses the subscription information of SIM A (that is, 5G-GUTI A is set as the terminal ID), the UDM may be the UDM 134. When the PDU session uses the subscription information of the SIM B (that is, 5G-GUTI B is set as the terminal ID), the UDM may be the UDM 114.

In step 308, the SMF may obtain policy information from the PCF. This policy information may include MUSIM policy information. The SMF may check or determine the priority of the PDU session based on the priority information received from the AMF 106 in step 304 to the priority information received from the PCF in step 308. When the PDU session uses the subscription information of SIM A (ie, 5G-GUTI A is set as the terminal ID), the PCF may be the PCF 133. When the PDU session uses the subscription information of SIM B (ie, 5G-GUTI B is set as the terminal ID), the PCF may be the PCF 113.

In step 310, the SMF may return a PDU session establishment response message to the AMF 106. In this case, the SMF may include PDU session priority information confirmed or determined in step 308. The AMF 106 may check or determine the priority of the PDU session based on the information received in steps 210 of FIG. 2 to 228 of FIG. 2 to steps 302 to 310 of FIG. 3.

In step 312, the AMF 103 may transmit a PDU session establishment permission message to the terminal 100.

The SMF according to an embodiment of the present disclosure is based on the PDU session information received from the AMF in step 304, the terminal subscription information received from the UDM in step 306, to the policy information received from the PCF in step 308, during the PDU session establishment procedure. It can be determined that the corresponding terminal is a terminal supporting the MUSIM function. Accordingly, the SMF knows that the UE can establish a PDU session in a PLMN other than the PLMN to which the UE currently belongs, and makes an event subscription request to the AMF 106, an NF that can manage PDU session information established in another PLMN in step 314. I can. The event subscription request is for receiving notification when there is a change in a PDU session established by another PLMN. The event subscription request message may include a terminal ID, a PDU session ID, an S-NSSAI associated with a PDU session, a DNN, a target service type (eg, voice, data, etc.).

In step 316, the AMF 106 may process the event subscription request message and may return an event subscription response message to the SMF. Subsequently, when an event related to a PDU session occurs, the AMF 106 may transmit an event notification message to the SMF as in step 402 of FIG. 4.

If there is a PDU session previously established by the UE, and the SMF that manages the PDU session requests the AMF 106 to subscribe to the event, the AMF that establishes a new PDU session through steps 300 to 312 is step 330 In the AMF 106 may transmit an event notification message notifying that a new PDU session has been established to the SMF.

In the sixth embodiment, step 340 may be omitted.

Referring to FIG. 4, in step 400, the terminal 100 may start a service linked to SIM A (for example, a voice call to a phone number linked to SIM A) using a PDU session A established with PLMN A. . The PDU session A may be managed by the SMF 131 of PLMN A. The AMF 106 may detect that a change has occurred in the session established by the terminal in PLMN A. Accordingly, the AMF may determine that the PDU session A is activated, and store information of the PDU session A of the terminal context as activation. In addition, information included in the event subscription request message requested by the SMF 111 in step 314 (e.g., terminal ID, PDU session ID, S-NSSAI associated with PDU session, DNN, target service type (e.g., voice, data, etc.)) and PDU session A information can be compared to determine that an event has occurred.

As a method for the AMF 106 to determine an event, it must first be able to determine the terminal. For example, in the terminal context stored by the AMF 106, the terminal ID associated with SIM A (for example, 5G-GUTI A, SUPI A, etc.) of the terminal 100 and the terminal ID associated with SIM B ( For example, 5G-GUTI B, SUPI B, etc.) may be included. AMF is the terminal ID (e.g., 5G-GUTI A, SUPI A, etc.) linked to the PDU session A and the terminal ID received from the SMF 111 in step 314 (e.g., 5G-GUTI B, SUPI B, etc.). ), and knowing that the terminal ID is linked to one terminal context, it can be determined that an event targeting the terminal has occurred.

In addition, as a method for the AMF 106 to determine an event, it must be able to determine a service. For example, the AMF compares the S-NSSAI and/or DNN information linked to the PDU session A with the S-NSSAI and/or DNN information received from the SMF 111 in step 314, and if the information matches, the S -It can be determined that an event targeting NSSAI and/or DNN has occurred.

Alternatively, the AMF may know the service of the PDU session A based on the S-NSSAI and/or DNN information linked to the PDU session A based on the local configuration. Accordingly, the AMF may compare the service interlocked with the PDU session A with the target service received from the SMF 111 in step 314, and determine that an event has occurred if the information matches.

In addition, as a method for the AMF 106 to determine an event, it should be possible to determine the priority between PLMNs. For example, the AMF may determine the priority between PLMNs based on the MUSIM policy information obtained through the procedures shown in FIGS. 2 to 3. In the AMF, when the priority of PLMN A linked to PDU session A is higher than that of PLMN B received from SMF 111 or to which SMF 111 belongs in step 314, an event targeting PDU session A occurs. You can judge that you did.

The AMF 106 determining that the event has occurred through the method described above may transmit an event notification message to the SMF 111 in step 402. The event notification message includes the terminal ID, the PDU session ID of the PDU session B (i.e., the PDU session ID transmitted by the SMF 111 to the AMF 106 in step 314), and the target where the event was detected (e.g., S-NSSAI , DNN, target service, etc.). Upon receiving the notification message, the SMF 111 may know that the terminal is using the service in PLMN A.

In step 404, downlink data for PDU session B targeting SIM B 102 may be generated. If the AN tunnel information for the PDU session B does not exist in the UPF 112, the UPF 112 may transmit a data notification message to the SMF 111 in step 406.

There may be various methods for the SMF 111 to process the data notification message. In one embodiment, in step 408, the SMF 111 performs a PDU session A based on the notification message received in step 402. As it is in use, it may be determined not to transmit data for PDU session B. Accordingly, the SMF 111 may transmit a failure indication message indicating that data transmission has failed to the UPF in step 412.

In one embodiment, in step 408, the SMF 111 is based on the notification message received in step 402 and the MUSIM policy information acquired through the procedure of FIG. 3, the terminal is using the PDU session A, and the PDU session A is It is determined that the priority is higher than that of the PDU session B, and it may be determined not to transmit data for the PDU session B. Accordingly, the SMF 111 may transmit a failure indication message indicating that data transmission has failed to the UPF in step 412.

The failure indication message sent by the SMF to the UPF in step 412 may include a cause value indicating that paging is currently impossible due to the MUSIM function.

In step 408, if PLMN A has a lower priority than PLMN B, the SMF transmits a paging message to SIM B of the terminal through the AMF 106, thereby transmitting downlink data targeting SIM B to the terminal. have.

[Example 7]

Embodiment 7 describes a method of managing session information and priority of a terminal in UDM and processing multiple sessions when a terminal using two or more SIMs simultaneously establishes a PDU session by using two or more SIMs.

Referring to FIG. 3, the AMF 106 that processed the PDU session request message through steps 300 to 312 in the method described in Embodiment 5 is an event notification message including PDU session state information to UDM of another PLMN in step 340. Can be transmitted.

In more detail, for example, in step 302, the PDU session establishment is requested from the terminal through PLMN A (SIM A), and the PDU session establishment is completed in step 312. The UDM 114 may transmit PDU session information established by the UE in PLMN A. The PDU session information may include a PDU session ID, a PLMN ID to which the PDU session belongs, a terminal ID using a PDU session, and a PDU session state (activation/deactivation). The UDM 114 of PLMN B may store PDU session information established by the UE in PLMN A. The UDM 114 of PLMN B may provide the stored PDU session information of PLMN A to the NF of PLMN B. For example, PDU session information of PLMN A may be provided to the AMF 106 in step 224 of the terminal registration procedure. Alternatively, PDU session information of PLMN A may be provided to the SMF 111 in step 306 of the PDU session establishment procedure of the terminal.

In step 340, when the AMF transmits the event notification message to the UDM, the AMF may always transmit the event notification message to the UDM when a state change of the PDU session occurs.

Alternatively, when a state change of the PDU session occurs, the AMF may transmit an event notification message only for a PDU session having a low priority based on the priority of the PDU session. In more detail, when the terminal establishes a PDU session in PLMN A through the procedure shown in FIG. 3, the AMF provides the same service in the PLMN B as the terminal based on the UE context of the terminal (e.g., S-NSSAI , DNN, target service, etc.) may determine whether a PDU session has been established. When the UE establishes a PDU session for the same service in PLMN B as well, the AMF may compare the priority of the PDU session established in PLMN A and the PDU session established in PLMN B. When the priority of the PDU session concluded by PLMN A is higher, the AMF may transmit an event notification message to the UDM of PLMN B.

Alternatively, when a state change of the PDU session occurs, the AMF may transmit the event notification message only for the PDU session of the PLMN having a low priority based on the priority of the PLMN to which the PDU session belongs.

In the seventh embodiment, step 330 may be omitted.

5 illustrates an IMS call processing method based on UDM session information according to an embodiment of the present disclosure.

Referring to FIG. 5, an IMS call request message with the terminal 100 as a destination may be delivered to the I-CSCF through steps 500 and 502. The I-CSCF may transmit a location request message to the UDM/HSS in step 504 to find the location of the terminal. In step 506, the UDM/HSS may check the location information of the terminal (ie, S-CSCF information registered by the terminal). The UDM/HSS according to an embodiment of the present disclosure may determine that a UE is using a PDU session in another PLMN, and that a PDU session of another PLMN has a higher priority than a PDU session requested in step 504. Accordingly, the UDM/HSS may not return the stored S-CSCF information to the I-CSCF in step 508. The I-CSCF may determine that the location of the terminal 100 cannot be found, and may transmit a reply message to the S-CSCF in step 510.

The mobile communication system according to an embodiment of the present disclosure provides a guide message (eg, a busy tone, etc.) indicating that the terminal 100 is currently on a call to a calling terminal that has made an IMS call request to the terminal 100. I can.

The mobile communication system according to an embodiment of the present disclosure may provide a guide message (eg, an SMS message, etc.) notifying that an IMS call request has been received, but a call request message has not been transmitted to the terminal 100.

If in step 506, the UDM/HSS determines that the UE is using a PDU session in another PLMN, and the PDU session of another PLMN has a lower priority than the PDU session requested in step 504, the UDM/HSS is stored and The existing S-CSCF information can be returned to the I-CSCF in step 508.

As another method, the terminal may register (IMS registration) in the IMS of PLMN A with the terminal ID (eg, IMPU A) linked to SIM A. In addition, the terminal may register (IMS registration) in the IMS of the PLMN B with a terminal ID (eg, IMPU B) linked to the SIM B. The terminal according to an embodiment of the present disclosure may determine the priority of PLMN A and PLMN B. For the sake of explanation, it is assumed that PLMN A has a higher priority than PLMN B. The UE may establish a PDU session A with PLMN A and use the service. If the terminal does not want to receive downlink data for PDU session B of PLMN B during PDU session A, the terminal registers in IMS of PLMN B with the terminal ID (e.g., IMPU B) linked with SIM B. In order to cancel (IMS registration), you can do IMS deregistration in PLMN B's IMS. Thereafter, even if data destined for IMPU B of the terminal occurs, the IMS of PLMN B is unable to transmit downlink data to the terminal because the registration of IMPU B is cancelled.

6 is a diagram illustrating a configuration of a terminal according to an embodiment of the present disclosure.

As shown in FIG. 6, the terminal of the present disclosure may include a transceiver 610, a memory 620, a processor 630, a first SIM 631 and a second SIM 632. According to the above-described communication method of the terminal, the transceiver 610, the memory 620, the processor 630, the first SIM 631 and the second SIM 632 of the terminal may operate. However, the components of the terminal are not limited to the above-described example. For example, the terminal may include more or fewer components than the above-described components. For example, referring to FIG. 6, only the first SIM 631 and the second SIM 632 are disclosed, but the present invention is not limited thereto, and N SIMs (not shown) may be further included. In addition, the processor 630, the transceiver 610, and the memory 620 may be implemented in the form of a single chip.

The transceiving unit 610 refers to a receiving unit of a terminal and a transmitting unit of a terminal, and may transmit and receive signals with a base station. Signals transmitted and received with the base station may include control information and data. To this end, the transceiver 610 may include an RF transmitter that up-converts and amplifies a frequency of a transmitted signal, and an RF receiver that amplifies a received signal with low noise and down-converts a frequency. However, this is only an embodiment of the transceiver 610, and components of the transceiver 610 are not limited to the RF transmitter and the RF receiver.

In addition, the transmission/reception unit 610 may receive a signal through a wireless channel, output it to the processor 630, and transmit a signal output from the processor 630 through a wireless channel.

The memory 620 may store programs and data necessary for the operation of the terminal. In addition, the memory 620 may store control information or data included in a signal acquired from the terminal. The memory 620 may be composed of a storage medium such as a ROM, a RAM, a hard disk, a CD-ROM, a DVD, or a combination of storage media.

The processor 630 may control a series of processes so that the terminal can operate according to the embodiment of the present disclosure described above. The processor 630 may include at least one or more processors. For example, the processor 630 may include a communication processor (CP) that controls communication and an application processor (AP) that controls an upper layer such as an application program.

The first SIM 631 and the second SIM 632 may be access control modules for accessing a network of a mobile communication service provider. The processor 630 may perform a registration process with a predetermined network entity using the first SIM 6310. In addition, the processor 630 may perform a registration process with the network entity using the second SIM 632. FIG. 7 is a diagram illustrating a configuration of a network entity according to an embodiment of the present disclosure.

As shown in FIG. 7, the network entity of the present disclosure may include a transceiver 710, a memory 720, and a processor 730. According to the above-described communication method of the network entity, the processor 730, the transceiver 710, and the memory 720 of the network entity may operate. However, the constituent elements of the network entity are not limited to the above-described example. For example, the network entity may include more or fewer components than the above-described components. In addition, the processor 730, the transceiver 710, and the memory 720 may be implemented in the form of a single chip. Network entities, such as AMF (Access and Mobility Management Function), SMF Session Management Function), PCF (Policy and Charging Function), NEF (Network Exposure Function), UDM (Unified Data Management), UPF (User Plane Function), etc. It may include a network function (NF). It may also include a base station.

The transmission/reception unit 710 collectively refers to a reception unit of a network entity and a transmission unit of a network entity, and may transmit and receive signals with a terminal or other network entity. In this case, the transmitted/received signal may include control information and data. To this end, the transceiver 710 may include an RF transmitter that up-converts and amplifies a frequency of a transmitted signal, and an RF receiver that amplifies a received signal with low noise and down-converts a frequency. However, this is only an embodiment of the transmission/reception unit 710, and components of the transmission/reception unit 710 are not limited to the RF transmitter and the RF receiver. The transceiving unit 710 may include a wired/wireless transceiving unit, and may include various configurations for transmitting and receiving signals.

In addition, the transceiver 710 may receive a signal through a communication channel (eg, a wireless channel), output it to the processor 730, and transmit a signal output from the processor 730 through a communication channel.

The memory 720 may store programs and data necessary for the operation of the network entity. Also, the memory 720 may store control information or data included in a signal obtained from a network entity. The memory 720 may be composed of a storage medium such as a ROM, a RAM, a hard disk, a CD-ROM, and a DVD, or a combination of storage media.

The processor 730 may control a series of processes so that the network entity can operate according to the above-described embodiment of the present disclosure. The processor 730 may include at least one or more processors. The methods according to the embodiments described in the claims or the specification of the present disclosure may be implemented in the form of hardware, software, or a combination of hardware and software.

When implemented in software, a computer-readable storage medium storing one or more programs (software modules) may be provided. One or more programs stored in a computer-readable storage medium are configured to be executable by one or more processors in an electronic device (device). The one or more programs include instructions for causing the electronic device to execute methods according to embodiments described in the claims or specification of the present disclosure.

These programs (software modules, software) include random access memory, non-volatile memory including flash memory, read only memory (ROM), and electrically erasable programmable ROM. (electrically erasable programmable read only memory, EEPROM), magnetic disc storage device, compact disc-ROM (CD-ROM), digital versatile discs (DVDs) or other forms of It may be stored in an optical storage device or a magnetic cassette. Alternatively, it may be stored in a memory composed of a combination of some or all of them. In addition, a plurality of configuration memories may be included.

In addition, the program is a communication network such as the Internet (Internet), Intranet (Intranet), LAN (local area network), WAN (wide area network), or SAN (storage area network), or a communication network composed of a combination thereof. It may be stored in an accessible storage device. Such a storage device may access a device performing an embodiment of the present disclosure through an external port. In addition, a separate storage device on the communication network may access a device performing an embodiment of the present disclosure.

In the above-described specific embodiments of the present disclosure, components included in the disclosure are expressed in the singular or plural according to the presented specific embodiments. However, the singular or plural expression is selected appropriately for the situation presented for convenience of description, and the present disclosure is not limited to the singular or plural constituent elements, and even constituent elements expressed in plural are composed of the singular or in the singular. Even the expressed constituent elements may be composed of pluralities.

Meanwhile, although specific embodiments have been described in the detailed description of the present disclosure, various modifications may be made without departing from the scope of the present disclosure. Therefore, the scope of the present disclosure is limited to the described embodiments and should not be defined, and should be determined by the scope of the claims and equivalents as well as the scope of the claims to be described later.

Claims (1)

In a method of providing a multiple subscription service of a terminal in a wireless communication system,
Transmitting a registration request message to a base station; And
Receiving a response to the registration request message.

Images