Electronic device using network slice, method for operating same, and storage medium

Abstract

An electronic device according to an embodiment may: perform at least one operation for establishing a first protocol data unit (PDU) session on the basis of pre-stored information for establishing a PDU session; identify the occurrence of an event related to the application of a user equipment route selection policy (URSP); identify whether to maintain or release the first PDU session on the basis of the result of comparison between the URSP rule and pieces of information regarding the first PDU session, on the basis of identifying the occurrence of the event; perform at least one operation for releasing the first PDU session on the basis of identifying that the first PDU session is to be released; and perform at least one operation for establishing a second PDU session on the basis of at least a part of the URSP rule, on the basis of the release of the first PDU session.

Description

Electronic device utilizing network slice, method of operation thereof, and storage medium

[0001] The present disclosure relates to an electronic device, an operating method, and a storage medium utilizing a network slice.

[0002] To meet the increasing demand for wireless data traffic since the commercialization of 4G communication systems, efforts are being made to develop improved 5G communication systems, or pre-5G communication systems. 5G communication systems, or pre-5G communication systems, are also referred to as communication systems beyond the 4G network or systems after the LTE system (post-LTE). To achieve high data rates, 5G communication systems are being considered for implementation in ultra-high frequency (mmWave) bands (e.g., the 60 GHz band). To mitigate path loss and increase transmission range of radio waves in ultra-high frequency bands, beamforming, massive multi-input multiple-output (MIMO), full-dimensional MIMO (FD-MIMO), array antennas, analog beamforming, and large-scale antenna technologies are being discussed in 5G communication systems.

[0003] One of the most prominent new architectural features of 5G networks is the introduction of network slicing technology into the radio access network (RAN) and core network (CN) architecture. This technology aims to apply properties such as isolation, customization, independent management, and orchestration of network system functions and resources to the mobile communications network architecture by bundling network resources and network functions into independent network slices according to individual services. This network slicing technology enables the selection and combination of network functions of a 5G system based on service, user, and business model criteria, enabling the provision of independent and flexible 5G services.

[0004] In the 3rd generation partnership project (3GPP), URSP (UE route selection policy) rules are defined. User equipment (UE) can receive URSP rules from the policy control function (PCF) and establish network slices and data sessions. URSP rules can include traffic descriptors and route selection descriptors.

[0005] The above information may be provided as background art to aid in understanding the present disclosure. No claim or determination is made as to whether any of the above is applicable as prior art related to the present disclosure.

[0006] When a UE receives a URSP rule from the PCF, it can establish a protocol data unit (PDU) session according to the URSP rule. While the UE is communicating with the network according to the established PDU session, the network can send a new URSP rule using the Manage UE Policy command. In response, the UE will release the current PDU session by sending a PDU Session Release Request and receiving a PDU Session Release Acceptance. Then, the UE will establish a new PDU session with the network according to the new URSP rule.

[0007] Consequently, when the URSP rule is updated, the current PDU session is released and a new PDU session is established. However, this causes a service interruption, which may lead to service disconnection issues for the UE. For example, the UE may experience a temporary service interruption, and the user may experience issues such as delayed responses or icon flickering due to the service interruption.

[0008] The electronic device may include at least one processor.

[0009] An electronic device may include a memory that stores instructions.

[0010] The instructions, when individually or collectively executed by the at least one processor, may cause the electronic device to perform at least one operation for establishing a first protocol data unit (PDU) session based on information for establishing a PDU session pre-stored in the electronic device.

[0011] The above instructions, when individually or collectively executed by the at least one processor, may cause the electronic device to determine the occurrence of an event associated with the application of a URSP rule.

[0012] The instructions, when individually or collectively executed by the at least one processor, may cause the electronic device to determine whether to maintain or release the first PDU session based on a comparison result between the URSP rule and information about the first PDU session, based on confirmation of the occurrence of the event.

[0013] The instructions, when individually or collectively executed by the at least one processor, may cause the electronic device to perform at least one operation for releasing the first PDU session based on a determination that the first PDU session is to be released, and to perform at least one operation for establishing a second PDU session based on at least a portion of the URSP rule based on the release of the first PDU session.

[0014] A method of operating an electronic device may include performing at least one operation for establishing a first protocol data unit (PDU) session based on information for establishing a PDU session pre-stored in the electronic device.

[0015] The method of operating the electronic device may include an operation of determining the occurrence of an event related to the application of a URSP rule.

[0016] The method of operating the electronic device may include an operation of determining whether to maintain or release the first PDU session based on a comparison result between the URSP rule and information about the first PDU session, based on confirmation of occurrence of the event.

[0017] The method of operating the electronic device may include performing at least one operation for releasing the first PDU session based on determining that the first PDU session is to be released, and performing at least one operation for establishing a second PDU session based on at least a part of the URSP rule based on the release of the first PDU session.

[0018] A storage medium for storing computer-readable instructions may be provided.

[0019] The instructions, when individually or collectively executed by the at least one processor, may cause the electronic device to perform at least one operation for establishing a first protocol data unit (PDU) session based on information for establishing a PDU session pre-stored in the electronic device.

[0020] The above instructions, when individually or collectively executed by the at least one processor, may cause the electronic device to determine the occurrence of an event associated with the application of a URSP rule.

[0021] The instructions, when individually or collectively executed by the at least one processor, may cause the electronic device to determine whether to maintain or release the first PDU session based on a comparison result between the URSP rule and information about the first PDU session, based on confirmation of the occurrence of the event.

[0022] The instructions, when individually or collectively executed by the at least one processor, may cause the electronic device to perform at least one operation for releasing the first PDU session based on a determination that the first PDU session is to be released, and to perform at least one operation for establishing a second PDU session based on at least a portion of the URSP rule based on the release of the first PDU session.

[0023] The electronic device may include at least one processor.

[0024] An electronic device may include a memory that stores instructions.

[0025] The instructions, when individually or collectively executed by the at least one processor, may cause the electronic device to perform at least one operation for establishing a first protocol data unit (PDU) session based on information for establishing a PDU session pre-stored in the electronic device.

[0026] The above instructions, when individually or collectively executed by the at least one processor, may cause the electronic device to determine the occurrence of an event associated with the application of a URSP rule.

[0027] The instructions, when individually or collectively executed by the at least one processor, may cause the electronic device to determine whether adjustment of the first PDU session is required based on a comparison result between the URSP rule and information about the first PDU session, based on confirmation of occurrence of the event.

[0028] The instructions, when individually or collectively executed by the at least one processor, may cause the electronic device to perform at least one operation for moderating the first PDU session based on at least a portion of the URSP rules, based on determining that the first PDU session is to be moderated.

[0029] A method of operating an electronic device may include performing at least one operation for establishing a first protocol data unit (PDU) session based on information for establishing a PDU session pre-stored in the electronic device.

[0030] The method of operating the electronic device may include an operation of determining the occurrence of an event related to the application of a URSP rule.

[0031] The method of operating the electronic device may include an operation of determining whether to adjust the first PDU session based on a comparison result between the URSP rule and information about the first PDU session, based on confirmation of occurrence of the event.

[0032] The method of operating the electronic device may include performing at least one operation for coordination of the first PDU session based on at least a portion of the URSP rule, based on determining that the first PDU session is to be coordinated.

[0033] A storage medium for storing computer-readable instructions may be provided.

[0034] The instructions, when individually or collectively executed by the at least one processor, may cause the electronic device to perform at least one operation for establishing a first protocol data unit (PDU) session based on information for establishing a PDU session pre-stored in the electronic device.

[0035] The above instructions, when individually or collectively executed by the at least one processor, may cause the electronic device to determine the occurrence of an event associated with the application of a URSP rule.

[0036] The instructions, when individually or collectively executed by the at least one processor, may cause the electronic device to determine whether adjustment of the first PDU session is required based on a comparison result between the URSP rule and information about the first PDU session, based on confirmation of occurrence of the event.

[0037] The instructions, when individually or collectively executed by the at least one processor, may cause the electronic device to perform at least one operation for moderating the first PDU session based on at least a portion of the URSP rules, based on determining that the first PDU session is to be moderated.

[0038] FIG. 1 is a block diagram of an electronic device within a network environment according to various embodiments.

[0039] FIG. 2A is a block diagram of an electronic device for supporting legacy network communication and 5G network communication according to various embodiments.

[0040] FIG. 2b is a block diagram of an electronic device for supporting legacy network communication and 5G network communication according to various embodiments.

[0041] Figure 3a illustrates a 5G system architecture.

[0042] Figure 3b illustrates a 5G network slice structure.

[0043] FIG. 4 is a diagram for explaining an operation method of an electronic device and a network according to one embodiment.

[0044] FIG. 5 is a drawing for explaining an operation method of an electronic device and a network according to a comparative example for comparison with an embodiment.

[0045] FIG. 6A is a drawing for explaining an operation method of an electronic device according to one embodiment.

[0046] FIG. 6b is a drawing for explaining an operation method of an electronic device according to one embodiment.

[0047] FIG. 6c is a drawing for explaining an operation method of an electronic device according to one embodiment.

[0048] FIG. 7 is a diagram for explaining an operation method of an electronic device and a network according to one embodiment.

[0049] Figure 8 is a flowchart for explaining an operating method of an electronic device according to one embodiment.

[0050] FIG. 9 is a drawing for explaining an operating method of an electronic device according to one embodiment.

[0051] FIG. 10 is a drawing for explaining an operating method of an electronic device according to one embodiment.

[0052] FIG. 11A is a drawing for explaining an operation method of an electronic device according to one embodiment.

[0053] FIG. 11b is a diagram for explaining an operation method of an electronic device and a network according to one embodiment.

[0054] FIG. 12A is a drawing for explaining an operation method of an electronic device according to one embodiment.

[0055] FIG. 12b is a diagram for explaining an operation method of an electronic device and a network according to one embodiment.

[0056] FIG. 13 is a drawing for explaining an operating method of an electronic device according to one embodiment.

[0057] FIG. 1 is a block diagram of an electronic device (101) within a network environment (100) according to an embodiment. Referring to FIG. 1, in the network environment (100), the electronic device (101) may communicate with the electronic device (102) via a first network (198) (e.g., a short-range wireless communication network), or may communicate with the electronic device (104) or a server (108) via a second network (199) (e.g., a long-range wireless communication network). According to an embodiment, the electronic device (101) may communicate with the electronic device (104) via the server (108). According to one embodiment, the electronic device (101) may include a processor (120), a memory (130), an input module (150), an audio output module (155), a display module (160), an audio module (170), a sensor module (176), an interface (177), a connection terminal (178), a haptic module (179), a camera module (180), a power management module (188), a battery (189), a communication module (190), a subscriber identification module (196), or an antenna module (197). In some embodiments, the electronic device (101) may omit at least one of these components (e.g., the connection terminal (178)), or may have one or more other components added. In some embodiments, some of these components (e.g., the sensor module (176), the camera module (180), or the antenna module (197)) may be integrated into one component (e.g., the display module (160)).

[0058] The processor (120) may, for example, execute software (e.g., a program (140)) to control at least one other component (e.g., a hardware or software component) of the electronic device (101) connected to the processor (120) and perform various data processing or operations. According to one embodiment, as at least a part of the data processing or operations, the processor (120) may store commands or data received from other components (e.g., a sensor module (176) or a communication module (190)) in a volatile memory (132), process the commands or data stored in the volatile memory (132), and store result data in a non-volatile memory (134). According to one embodiment, the processor (120) may include a main processor (121) (e.g., a central processing unit or an application processor) or an auxiliary processor (123) (e.g., a graphics processing unit, a neural processing unit (NPU), an image signal processor, a sensor hub processor, or a communication processor) that can operate independently or together with the main processor (121). For example, when the electronic device (101) includes the main processor (121) and the auxiliary processor (123), the auxiliary processor (123) may be configured to use less power than the main processor (121) or to be specialized for a given function. The auxiliary processor (123) may be implemented separately from the main processor (121) or as a part thereof.

[0059] The auxiliary processor (123) may control at least a portion of functions or states associated with at least one component (e.g., a display module (160), a sensor module (176), or a communication module (190)) of the electronic device (101), for example, on behalf of the main processor (121) while the main processor (121) is in an inactive (e.g., sleep) state, or together with the main processor (121) while the main processor (121) is in an active (e.g., application execution) state. In one embodiment, the auxiliary processor (123) (e.g., an image signal processor or a communication processor) may be implemented as a part of another functionally related component (e.g., a camera module (180) or a communication module (190)). In one embodiment, the auxiliary processor (123) (e.g., a neural network processing unit) may include a hardware structure specialized for processing artificial intelligence models. The artificial intelligence models may be generated through machine learning. This learning can be performed, for example, in the electronic device (101) itself where artificial intelligence is performed, or can be performed through a separate server (e.g., server (108)). The learning algorithm can include, for example, supervised learning, unsupervised learning, semi-supervised learning, or reinforcement learning, but is not limited to the examples described above. The artificial intelligence model can include multiple artificial neural network layers.The artificial neural network may be one of a deep neural network (DNN), a convolutional neural network (CNN), a recurrent neural network (RNN), a restricted Boltzmann machine (RBM), a deep belief network (DBN), a bidirectional recurrent deep neural network (BRDNN), a deep Q-network, or a combination of two or more of the above, but is not limited to the examples described above. In addition to, or alternatively to, a hardware structure, an artificial intelligence model may include a software structure.

[0060] The memory (130) can store various data used by at least one component (e.g., processor (120) or sensor module (176)) of the electronic device (101). The data can include, for example, software (e.g., program (140)) and input data or output data for commands related thereto. The memory (130) can include volatile memory (132) or non-volatile memory (134).

[0061] The program (140) may be stored as software in the memory (130) and may include, for example, an operating system (142), middleware (144), or an application (146).

[0062] The input module (150) can receive commands or data to be used in a component of the electronic device (101) (e.g., a processor (120)) from an external source (e.g., a user) of the electronic device (101). The input module (150) can include, for example, a microphone, a mouse, a keyboard, a key (e.g., a button), or a digital pen (e.g., a stylus pen).

[0063] The audio output module (155) can output audio signals to the outside of the electronic device (101). The audio output module (155) can include, for example, a speaker or a receiver. The speaker can be used for general purposes, such as multimedia playback or recording playback. The receiver can be used to receive incoming calls. In one embodiment, the receiver can be implemented separately from the speaker or as part of the speaker.

[0064] The display module (160) can visually provide information to an external party (e.g., a user) of the electronic device (101). The display module (160) may include, for example, a display, a holographic device, or a projector and a control circuit for controlling the device. According to one embodiment, the display module (160) may include a touch sensor configured to detect a touch, or a pressure sensor configured to measure the intensity of a force generated by the touch.

[0065] The audio module (170) can convert sound into an electrical signal, or vice versa, convert an electrical signal into sound. According to one embodiment, the audio module (170) can acquire sound through the input module (150), output sound through the sound output module (155), or an external electronic device (e.g., electronic device (102)) (e.g., speaker or headphone) directly or wirelessly connected to the electronic device (101).

[0066] The sensor module (176) can detect the operating status (e.g., power or temperature) of the electronic device (101) or the external environmental status (e.g., user status) and generate an electrical signal or data value corresponding to the detected status. According to one embodiment, the sensor module (176) can include, for example, a gesture sensor, a gyro sensor, a barometric pressure sensor, a magnetic sensor, an acceleration sensor, a grip sensor, a proximity sensor, a color sensor, an IR (infrared) sensor, a biometric sensor, a temperature sensor, a humidity sensor, or an illuminance sensor.

[0067] The interface (177) may support one or more designated protocols that may be used to directly or wirelessly connect the electronic device (101) with an external electronic device (e.g., the electronic device (102)). In one embodiment, the interface (177) may include, for example, a high definition multimedia interface (HDMI), a universal serial bus (USB) interface, an SD card interface, or an audio interface.

[0068] The connection terminal (178) may include a connector through which the electronic device (101) may be physically connected to an external electronic device (e.g., electronic device (102)). According to one embodiment, the connection terminal (178) may include, for example, an HDMI connector, a USB connector, an SD card connector, or an audio connector (e.g., a headphone connector).

[0069] The haptic module (179) can convert electrical signals into mechanical stimuli (e.g., vibration or movement) or electrical stimuli that a user can perceive through tactile or kinesthetic sensations. According to one embodiment, the haptic module (179) can include, for example, a motor, a piezoelectric element, or an electrical stimulation device.

[0070] The camera module (180) can capture still images and videos. According to one embodiment, the camera module (180) may include one or more lenses, image sensors, image signal processors, or flashes.

[0071] The power management module (188) can manage power supplied to the electronic device (101). According to one embodiment, the power management module (188) can be implemented as, for example, at least a part of a power management integrated circuit (PMIC).

[0072] A battery (189) may power at least one component of the electronic device (101). In one embodiment, the battery (189) may include, for example, a non-rechargeable primary battery, a rechargeable secondary battery, or a fuel cell.

[0073] The communication module (190) may support the establishment of a direct (e.g., wired) communication channel or a wireless communication channel between the electronic device (101) and an external electronic device (e.g., electronic device (102), electronic device (104), or server (108)), and the performance of communication through the established communication channel. The communication module (190) may operate independently from the processor (120) (e.g., application processor) and may include one or more communication processors that support direct (e.g., wired) communication or wireless communication. According to one embodiment, the communication module (190) may include a wireless communication module (192) (e.g., a cellular communication module, a short-range wireless communication module, or a global navigation satellite system (GNSS) communication module) or a wired communication module (194) (e.g., a local area network (LAN) communication module, or a power line communication module). Among these communication modules, the corresponding communication module can communicate with an external electronic device (104) via a first network (198) (e.g., a short-range communication network such as Bluetooth, wireless fidelity (WiFi) direct, or infrared data association (IrDA)) or a second network (199) (e.g., a long-range communication network such as a legacy cellular network, a 5G network, a next-generation communication network, the Internet, or a computer network (e.g., a LAN or WAN)). These various types of communication modules can be integrated into a single component (e.g., a single chip) or implemented as a plurality of separate components (e.g., multiple chips). The wireless communication module (192) can verify or authenticate the electronic device (101) within a communication network such as the first network (198) or the second network (199) by using subscriber information (e.g., an international mobile subscriber identity (IMSI)) stored in the subscriber identification module (196).

[0074] The wireless communication module (192) can support 5G networks and next-generation communication technologies following the 4G network, such as NR access technology (new radio access technology). The NR access technology can support high-speed transmission of high-capacity data (eMBB (enhanced mobile broadband)), minimization of terminal power and connection of multiple terminals (mMTC (massive machine type communications)), or high reliability and low latency (URLLC (ultra-reliable and low-latency communications)). The wireless communication module (192) can support, for example, a high-frequency band (e.g., mmWave band) to achieve a high data transmission rate. The wireless communication module (192) can support various technologies for securing performance in a high-frequency band, such as beamforming, massive multiple-input and multiple-output (MIMO), full dimensional MIMO (FD-MIMO), array antenna, analog beam-forming, or large scale antenna. The wireless communication module (192) can support various requirements specified in the electronic device (101), an external electronic device (e.g., the electronic device (104)), or a network system (e.g., the second network (199)). According to one embodiment, the wireless communication module (192) can support a peak data rate (e.g., 20 Gbps or more) for eMBB realization, a loss coverage (e.g., 164 dB or less) for mMTC realization, or a U-plane latency (e.g., 0.5 ms or less for downlink (DL) and uplink (UL), or 1 ms or less for round trip) for URLLC realization.

[0075] The antenna module (197) can transmit or receive signals or power to or from an external device (e.g., an external electronic device). In one embodiment, the antenna module (197) may include an antenna including a radiator formed of a conductor or a conductive pattern formed on a substrate (e.g., a PCB). In one embodiment, the antenna module (197) may include a plurality of antennas (e.g., an array antenna). In this case, at least one antenna suitable for a communication method used in a communication network, such as the first network (198) or the second network (199), may be selected from the plurality of antennas, for example, by the communication module (190). A signal or power may be transmitted or received between the communication module (190) and an external electronic device via the at least one selected antenna. In some embodiments, in addition to the radiator, another component (e.g., a radio frequency integrated circuit (RFIC)) may be additionally formed as a part of the antenna module (197).

[0076] In one embodiment, the antenna module (197) may form a mmWave antenna module. In one embodiment, the mmWave antenna module may include a printed circuit board, an RFIC disposed on or adjacent a first side (e.g., a bottom side) of the printed circuit board and capable of supporting a designated high-frequency band (e.g., a mmWave band), and a plurality of antennas (e.g., an array antenna) disposed on or adjacent a second side (e.g., a top side or a side side) of the printed circuit board and capable of transmitting or receiving signals in the designated high-frequency band.

[0077] At least some of the above components can be interconnected and exchange signals (e.g., commands or data) with each other via a communication method between peripheral devices (e.g., a bus, GPIO (general purpose input and output), SPI (serial peripheral interface), or MIPI (mobile industry processor interface)).

[0078] According to one embodiment, commands or data may be transmitted or received between the electronic device (101) and an external electronic device (104) via a server (108) connected to a second network (199). Each of the external electronic devices (102 or 104) may be the same or a different type of device as the electronic device (101). According to one embodiment, all or part of the operations executed in the electronic device (101) may be executed in one or more of the external electronic devices (102, 104, or 108). For example, when the electronic device (101) is to perform a certain function or service automatically or in response to a request from a user or another device, the electronic device (101) may, instead of or in addition to executing the function or service itself, request one or more external electronic devices to perform the function or at least a part of the service. One or more external electronic devices that receive the request may execute at least a portion of the requested function or service, or an additional function or service related to the request, and transmit the result of the execution to the electronic device (101). The electronic device (101) may process the result as is or additionally and provide it as at least a portion of a response to the request. For this purpose, cloud computing, distributed computing, mobile edge computing (MEC), or client-server computing technology may be used, for example. The electronic device (101) may provide an ultra-low latency service by using distributed computing or mobile edge computing, for example. In another embodiment, the external electronic device (104) may include an Internet of Things (IoT) device. The server (108) may be an intelligent server utilizing machine learning and / or a neural network. According to one embodiment, the external electronic device (104) or the server (108) may be included in the second network (199).The electronic device (101) can be applied to intelligent services (e.g., smart home, smart city, smart car, or healthcare) based on 5G communication technology and IoT-related technology.

[0079] FIG. 2A is a block diagram (200) of an electronic device (101) for supporting legacy network communication and 5G network communication according to one embodiment. The electronic device (101) of FIG. 2A may be the electronic device (101) of FIG. 1 , and the electronic device (101) of FIG. 2B may be the electronic device (101) of FIG. 1 .

[0080] Referring to FIG. 2A, the electronic device (101) may include a first communication processor (212), a second communication processor (214), a first radio frequency integrated circuit (RFIC) (222), a second RFIC (224), a third RFIC (226), a fourth RFIC (228), a first radio frequency front end (RFFE) (232), a second RFFE (234), a first antenna module (242), a second antenna module (244), a third antenna module (246), and antennas (248). The electronic device (101) may further include a processor (120) and a memory (130). The second network (199) may include a first cellular network (292) and a second cellular network (294). According to another embodiment, the electronic device (101) may further include at least one of the components described in FIG. 1, and the second network (199) may further include at least one other network. According to one embodiment, the first communication processor (212), the second communication processor (214), the first RFIC (222), the second RFIC (224), the fourth RFIC (228), the first RFFE (232), and the second RFFE (234) may form at least a portion of the wireless communication module (192). According to another embodiment, the fourth RFIC (228) may be omitted or may be included as a part of the third RFIC (226).

[0081] The first communication processor (212) may establish a communication channel in a band to be used for wireless communication with the first cellular network (292), and may support legacy network communication through the established communication channel. According to one embodiment, the first cellular network may be a legacy network including a second generation (2G), 3G, 4G, or long term evolution (LTE) network. The second communication processor (214) may establish a communication channel corresponding to a designated band (e.g., about 6 GHz to about 60 GHz) among the bands to be used for wireless communication with the second cellular network (294), and may support 5G network communication through the established communication channel. According to one embodiment, the second cellular network (294) may be a 5G network defined by 3GPP. Additionally, according to one embodiment, the first communication processor (212) or the second communication processor (214) may support establishment of a communication channel corresponding to another designated band (e.g., about 6 GHz or less) among the bands to be used for wireless communication with the second cellular network (294), and 5G network communication through the established communication channel.

[0082] The first communication processor (212) can transmit and receive data with the second communication processor (214). For example, data classified to be transmitted via the second cellular network (294) may be changed to be transmitted via the first cellular network (292). In this case, the first communication processor (212) can receive the transmission data from the second communication processor (214). For example, the first communication processor (212) can transmit and receive data with the second communication processor (214) via the processor-to-processor interface (213). The above interprocessor interface (213) may be implemented as, for example, a universal asynchronous receiver / transmitter (UART) (e.g., HS-UART (high speed-UART) or PCIe (peripheral component interconnect bus express) interface), but there is no limitation on its type. Alternatively, the first communication processor (212) and the second communication processor (214) may exchange control information and packet data information using, for example, a shared memory. The first communication processor (212) may transmit and receive various information, such as sensing information, information on output intensity, and resource block (RB) allocation information, with the second communication processor (214).

[0083] Depending on the implementation, the first communication processor (212) may not be directly connected to the second communication processor (214). In this case, the first communication processor (212) may transmit and receive data with the second communication processor (214) through the processor (120) (e.g., application processor). For example, the first communication processor (212) and the second communication processor (214) may transmit and receive data with the processor (120) (e.g., application processor) through an HS-UART interface or a PCIe interface, but there is no limitation on the type of interface. Alternatively, the first communication processor (212) and the second communication processor (214) may exchange control information and packet data information with the processor (120) (e.g., application processor) using shared memory.

[0084] According to one embodiment, the first communication processor (212) and the second communication processor (214) may be implemented in a single chip or a single package. According to one embodiment, the first communication processor (212) or the second communication processor (214) may be formed in a single chip or a single package with the processor (120), the auxiliary processor (123), or the communication module (190). For example, as shown in FIG. 2B, the integrated communication processor (260) may support functions for communicating with both the first cellular network (292) and the second cellular network (294).

[0085] As described above, at least one of the processor (120), the first communication processor (212), the second communication processor (214), or the integrated communication processor (260) may be implemented as a single chip or a single package. In this case, the single chip or single package may include a memory (or storage means) that stores instructions that cause the performance of at least some of the operations performed according to an embodiment, and a processing circuit (or, the name thereof is not limited, such as an arithmetic circuit) for executing the instructions.

[0086] The first RFIC (222) may, upon transmission, convert a signal generated by the first communication processor (212) into a radio frequency (RF) signal of about 700 MHz to about 3 GHz used in a first cellular network (292) (e.g., a legacy network). Upon reception, the RF signal may be acquired from the first cellular network (292) (e.g., a legacy network) via an antenna (e.g., the first antenna module (242)) and preprocessed via an RFFE (e.g., the first RFFE (232)). The first RFIC (222) may convert the preprocessed RF signal into a signal that may be processed by the first communication processor (212).

[0087] The second RFIC (224) may, upon transmission, convert a signal generated by the first communication processor (212) or the second communication processor (214) into an RF signal (hereinafter, a 5G Sub6 RF signal) of a Sub6 band (e.g., about 6 GHz or less) used in the second cellular network (294) (e.g., a 5G network). Upon reception, the 5G Sub6 RF signal may be acquired from the second cellular network (294) (e.g., a 5G network) via an antenna (e.g., the second antenna module (244)) and preprocessed via an RFFE (e.g., the second RFFE (234)). The second RFIC (224) may convert the preprocessed 5G Sub6 RF signal into a signal that may be processed by a corresponding communication processor among the first communication processor (212) or the second communication processor (214).

[0088] The third RFIC (226) can convert a signal generated by the second communication processor (214) into an RF signal (hereinafter, 5G Above6 RF signal) of a 5G Above6 band (e.g., about 6 GHz to about 60 GHz) to be used in a second cellular network (294) (e.g., a 5G network). Upon reception, the 5G Above6 RF signal can be acquired from the second cellular network (294) (e.g., a 5G network) through an antenna (e.g., antenna (248)) and preprocessed through the third RFFE (236). The third RFIC (226) can convert the preprocessed 5G Above6 RF signal into a signal that can be processed by the second communication processor (214). According to one embodiment, the third RFFE (236) can be formed as a part of the third RFIC (226).

[0089] The electronic device (101) may, according to one embodiment, include a fourth RFIC (228) separately from or at least as a part of the third RFIC (226). In this case, the fourth RFIC (228) may convert a signal generated by the second communication processor (214) into an RF signal (hereinafter, referred to as an IF signal) of an intermediate frequency band (e.g., about 9 GHz to about 11 GHz) and then transmit the IF signal to the third RFIC (226). The third RFIC (226) may convert the IF signal into a 5G Above6 RF signal. Upon reception, the 5G Above6 RF signal may be received from the second cellular network (294) (e.g., a 5G network) via an antenna (e.g., antenna (248)) and converted into an IF signal by the third RFIC (226). The fourth RFIC (228) can convert the IF signal into a signal that can be processed by the second communication processor (214).

[0090] According to one embodiment, the first RFIC (222) and the second RFIC (224) may be implemented as a single chip or at least a portion of a single package. According to one embodiment, when the first RFIC (222) and the second RFIC (224) in FIG. 2A or FIG. 2B are implemented as a single chip or a single package, they may be implemented as an integrated RFIC. In this case, the integrated RFIC may be connected to the first RFFE (232) and the second RFFE (234) to convert a signal into a signal in a band supported by the first RFFE (232) and / or the second RFFE (234), and transmit the converted signal to one of the first RFFE (232) and the second RFFE (234). According to one embodiment, the first RFFE (232) and the second RFFE (234) may be implemented as at least a portion of a single chip or a single package. According to an example, at least one antenna module among the first antenna module (242) or the second antenna module (244) can be omitted or combined with another antenna module to process RF signals of corresponding multiple bands.

[0091] According to one embodiment, the third RFIC (226) and the antenna (248) may be disposed on the same substrate to form a third antenna module (246). For example, the wireless communication module (192) or the processor (120) may be disposed on the first substrate (e.g., the main PCB). In this case, the third RFIC (226) may be disposed on a portion (e.g., the bottom surface) of a second substrate (e.g., the sub PCB) separate from the first substrate, and the antenna (248) may be disposed on another portion (e.g., the top surface) to form the third antenna module (246). By disposing the third RFIC (226) and the antenna (248) on the same substrate, it is possible to reduce the length of the transmission line therebetween. This can reduce, for example, the loss (e.g., attenuation) of signals in a high-frequency band (e.g., about 6 GHz to about 60 GHz) used in 5G network communications by the transmission line. Due to this, the electronic device (101) can improve the quality or speed of communication with the second network (294) (e.g., 5G network).

[0092] According to an exemplary embodiment, the antenna (248) may be formed as an antenna array including a plurality of antenna elements that may be used for beamforming. In this case, the third RFIC (226) may include a plurality of phase shifters (238) corresponding to the plurality of antenna elements, for example, as part of the third RFFE (236). Upon transmission, each of the plurality of phase shifters (238) may shift the phase of a 5G Above6 RF signal to be transmitted to an external source (e.g., a base station of a 5G network) of the electronic device (101) via its corresponding antenna element. Upon reception, each of the plurality of phase shifters (238) may shift the phase of a 5G Above6 RF signal received from the external source via its corresponding antenna element to the same or substantially the same phase. This enables transmission or reception via beamforming between the electronic device (101) and the external source.

[0093] The second cellular network (294) (e.g., a 5G network) may operate independently (e.g., Stand-Alone (SA)) or in connection with (e.g., Non-Stand Alone (NSA)) the first cellular network (292) (e.g., a legacy network). For example, the 5G network may only have an access network (e.g., a 5G radio access network (RAN) or next generation RAN (NG RAN)) and no core network (e.g., next generation core (NGC)). In this case, the electronic device (101) may access an external network (e.g., the Internet) under the control of the core network (e.g., evolved packet core (EPC)) of the legacy network after accessing the access network of the 5G network. Protocol information for communication with a legacy network (e.g., LTE protocol information) or protocol information for communication with a 5G network (e.g., New Radio (NR) protocol information) may be stored in the memory (230) and accessed by other components (e.g., the processor (120), the first communication processor (212), or the second communication processor (214)).

[0094] Figure 3a illustrates a 5G system architecture.

[0095] Figure 3b illustrates a 5G network slice structure.

[0096] Below, the overall 5G system is described with reference to FIGS. 3a and 3b, and network slices are described.

[0097] As illustrated in FIG. 3a, the 5G system architecture may include a network element, an electronic device (101) (e.g., a user equipment (UE)), a radio access network (R) (302), a data network (DN) (345), and multiple network functions (NFs) within a core network (CN).

[0098] The 5G system architecture can be illustrated by defining functions, connection points, and protocols for each of multiple NFs, using reference points that represent service-based interfaces corresponding to NFs, and reference points that represent interactions existing between NFs.

[0099] The plurality of network functions (NFs) may include an authentication server function (AUSF) (309), an access and mobility management function (AMF) (303), a network exposure function (NEF) (347), a network function repository function (NRF) (305), a policy control function (PCF) (307), a session management function (SMF) (341), a unified data management (UDM) (306), a user plane function (UPF) (342), an application function (AF) (346), and a network slice selection function (NSSF) (304).

[0100] In various embodiments of the present disclosure, AMF, SMF, PCF, and UPF may play a key role in establishing a UE-requested protocol data unit (PDU) session and managing traffic between the UE and the DN.

[0101] The reference point between the electronic device (101) and the AMF (303) is defined as N1.

[0102] (R)AN (302) may represent a base station using radio access technology (RAT). For example, (R)AN (302) may be a base station including 3GPP access technology or a base station including non-3GPP access technology such as Wi-Fi. The reference point between (R)AN (302) and AMF (303) is defined as N2, and the reference point between (R)AN (302) and UPF (342) is defined as N3.

[0103] DN (345) can transmit a PDU to be transmitted in the downlink direction to UPF (342) or receive a PDU sent by an electronic device (101) through UPF (342). The reference point between DN (345) and UPF (342) is defined as N6.

[0104] AMF (303) can provide access and mobility management functions for each electronic device (101), for example, independent of access technology. The reference point between AMF (303) and electronic device (101) is defined as N1, the reference point between AMF (303) and (R)AN (302) is defined as N2, the reference point between AMF (303) and UDM (306) is defined as N8, the reference point between AMF (303) and AUSF (309) is defined as N12, and the reference point between AMF (303) and SMF (341) is defined as N11.

[0105] SMF (341) can provide a session management function in which, when one electronic device (101) has multiple sessions, a different SMF is allocated for each session and each session is managed. UPF (342) is set using control signal information generated in SMF (341), and N4 reference point is defined so that UPF (342) can report its status to SMF (341). The reference point between SMF (341) and AMF (303) is defined as N11, the reference point between SMF (341) and UDM (306) is defined as N10, the reference point between SMF (341) and PCF (307) is defined as N7, and the reference point between SMF (341) and AMF (303) is defined as N11.

[0106] For example, each electronic device (101) may be connected to one AMF (303), whereas in the case of SMF (341), one electronic device (101) may establish multiple sessions, and thus may have a different SMF (311, 321, 331) for each session.

[0107] AF (346) can provide information about packet flow to PCF (307), which is responsible for policy control, to ensure quality of service (QoS).

[0108] PCF (307) determines policies such as session management and mobility management based on information about packet flows to ensure QoS, and transmits the information to AMF (303) and SMF (341), thereby enabling at least one of appropriate mobility management, session management, and QoS management to be performed. The reference point between AF (346) and PCF (307) is defined as N5.

[0109] AUSF (309) can store data for authentication of an electronic device (101).

[0110] The UDM (306) can store at least a portion of the user's subscription data and policy data. The reference point between the AUSF (309) and the UDM (306) is defined as N13, the reference point between the AUSF (309) and the AMF (303) is defined as N12, the reference point between the UDM (306) and the AMF (303) is defined as N8, and the reference point between the UDM (306) and the SMF (341) is defined as N10.

[0111] CP functions include various functions for controlling networks and terminals, and two representative functions, an electronic device (101), (R)AN (302), UPF (342), AMF (303), AF (346), DN (345) responsible for mobility management functions, and an SMF (341) responsible for session management functions, can be included in CP functions as two independent functions.

[0112] In describing embodiments of the present disclosure, the terms slice, service, network slice, network service, application slice, and application service may be used interchangeably.

[0113] A mobile operator may allocate network resources appropriate for a given service on a slice-by-slice basis or on a set of specific slices. The network resources may refer to at least one of a network function (NF), logical resources provided by the network function (NF), or radio resource allocation.

[0114] Network slicing is a technology that can apply at least one of the properties of network isolation, customization, and independent management and orchestration to the mobile communication core network structure by bundling network resources and network functions into an independent slice according to service.

[0115] Network slicing is a new concept in 5G core networks. This technology bundles the network resources and functions required for a service requested by a mobile terminal into a single, independent slice.

[0116] Through network slicing, network operators can independently allocate network resources specific to each service and user, and secure network flexibility through resource virtualization based on software defined networking (SDN) and network function virtualization (NFV) technologies, thereby ensuring scalability and reliability of service and network resource operation.

[0117] A public land mobile network (PLMN) may provide multiple network slices, each of which may be provided to a terminal in the form of a slice instance. For example, the PLMN may include slice instance 1 (310), slice instance 2 (320), and slice instance 3 (330).

[0118] An electronic device (101) can connect to a network and receive services from at least one of multiple slice instances simultaneously or sequentially.

[0119] Each slice instance may be configured with the network resources required to provide the corresponding network slice. For example, slice instance 1 (310) may be configured with SMF (311) and UPF (312, 313), slice instance 2 (320) may be configured with SMF (321), UPF (322), and PCF (323), and slice instance 3 (330) may be configured with SMF (331), UPF (332), PCF (333), and NRF (334).

[0120] Referring to FIGS. 3A and 3B, the SMF (321) of slice instance 2 (320) can be connected to the PCF (307) of the PLMN level and the PCF (323) of the slice level. The PCF (307) of the PLMN level can manage policy information of the PLMN level and provide it to the SMF (321). The PCF (323) of the slice level belonging to slice instance 2 (320) can manage the policy required to provide the corresponding slice and provide the corresponding information to the SMF (321).

[0121] Each slice can be distinguished by a slice ID. For example, the slice ID can be single-network slice selection assistance information (S-NSSAI) defined in 3GPP. According to various embodiments, the electronic device (101) can store information about configured network slice selection assistance information (configured NSSAI) and a network slice selection policy (NSSP). The configured NSSAI can be configured as a list of S-NSSAIs of network slices to which the electronic device (101) subscribes in a home PLMN (HPLMN). The list of S-NASSAIs can include at least one S-NSSAI #id. For example, the list of S-NASSAIs can include S-NASSAI #a, S-NASSAI #b, S-NASSAI #c, and S-NASSAI #d. Since the Configured NSSAI is determined based on the subscription information of the electronic device (101), the S-NSSAI constituting the Configured NSSAI may be different for each electronic device (101). In addition, since the Configured NSSAI is determined based on the subscription information of the electronic device (101), if the subscription information of the electronic device (101) is changed, the Configured NSSAI stored in the electronic device (101) may also be changed. The list of S-NSSAIs subscribed to by the electronic device (101) constituting the Configured NSSAI may be stored in the integrated UDM (306) that stores the subscription information of the electronic device (101).The S-NSSAI subscribed by the electronic device (101) stored in the UDM (306) may be referred to as a 'Subscribed S-NSSAI'. The Network Slice Selection Policy (NSSP) indicates mapping information between the S-NSSAI (S-NSSAI #id) subscribed by the electronic device (101) and the applications that the corresponding S-NSSAI can support. One S-NSSAI #id can be mapped to at least one application. For example, S-NASSAI #a can be mapped to App #1 and App #2, S-NASSAI #b can be mapped to App #1, S-NASSAI #c can be mapped to App #3, and S-NASSAI #d can be mapped to all supportable applications. The NSSP may be stored in a policy control function (PCF) that stores the electronic device (101) and network-related policy information. Alternatively, the NSSP may be stored in a user data repository (UDR), and the PCF may request the NSSP information from the UDR as needed to obtain the NSSP information from the UDR. When there is a change in the subscription information of the electronic device (101), a change may occur in the subscribed S-NSSAIs information of the electronic device (101) stored in the UDM (306). When there is a change in the subscription information of the electronic device (101), a change may occur in the NSSP information stored in the PCF or UDR. If a change occurs in at least one of the subscribed S-NSSAIs or the NSSP, the related setting information stored in the electronic device (101) may also need to be updated.

[0122] FIG. 4 is a diagram for explaining an operation method of an electronic device and a network according to one embodiment.

[0123] According to one embodiment, the electronic device (101) (e.g., the processor (120), the first communication processor (212), the second communication processor (214), and / or the unified communication processor (260)) may, in operation 401, transmit a registration request message to the network (400) for system registration (e.g., an evolved packet system (EPS) and / or a 5th generation system (5GS)). The network (400) may, in operation 403, transmit a registration accept message to the electronic device (101). The electronic device (101) may, in operation 405, transmit a registration complete message to the network (400). The registration procedure based on the 401 action, the 403 action, and / or the 405 action may be performed based on, for example, but not limited to, the 3rd generation partnership project (3GPP) technical specification (TS) 23.501.

[0124] According to one embodiment, the electronic device (101), in operation 407, may transmit a first protocol data unit (PDU) session establishment request message of a first data network name (DNN) to the network (400) while being registered in the system. The network (400), in operation 409, may transmit a first PDU session establishment accept message corresponding to the first PDU session establishment request message to the electronic device (101). For example, the PDU session establishment accept message may include a PDU session ID, but there is no limitation. The electronic device (101), in operation 411, may transmit a second PDU session establishment request message of a second DNN to the network (400). The network (400) may, in operation 413, transmit a second PDU session establishment approval message corresponding to the second PDU session establishment request message to the electronic device (101).

[0125] For example, the electronic device (101) can identify the first DNN and the second DNN based on preset information. The electronic device (101) can pre-store the Internet protocol multimedia core network subsystem (IMS) for voice calls and the Internet for cellular data communication as the first DNN and the second DNN, but there is no limitation on the type and / or number of DNNs. Information that replaces the DNN and / or is additional (for example, but is not limited to, the slice service type (SST), the slice differentiator (SD), the Internet protocol (IP) type, the session and service continuity (SSC) mode, the proxy call session control function request (P_CSCF_REQ), and / or the protocol configuration options (PCO)) can also be stored in the electronic device (101) as preset information. For example, the electronic device (101) may transmit a first PDU session establishment request message to the network (400) to establish a first PDU session of the DNN of "internet". For example, the first PDU session establishment request message may include a PDU session ID (e.g., PSI=5) and information of the DNN of "internet". For example, the PDU session establishment request message may include S-NSSAI, but there is no limitation. For example, the electronic device (101) may transmit a second PDU session establishment request message to the network (400) to establish a second PDU session of the DNN of "IMS".For example, the second PDU session establishment request message may include a PDU session ID (e.g., PSI=6) and information on the DNN of "IMS". According to the above, the electronic device (101) may establish PDU sessions corresponding to the first DNN and the second DNN based on the preset information. For example, the electronic device (101) may perform PDU session establishment based on the preset information that has been stored in advance before receiving the URSP rule from the network (400) (e.g., PCF) and / or when the received URSP rule is inapplicable. The electronic device (101) may receive the URSP rule from the network (400) after establishing at least one PDU session and / or may confirm that the URSP rule that has been received in advance is applicable. In this case, the electronic device (101) may need to release the previously established PDU session and perform a procedure for establishing a PDU session based on the URSP rule, but this may result in service interruption, which will be described with reference to FIG. 5.

[0126] FIG. 5 is a drawing for explaining an operation method of an electronic device and a network according to a comparative example for comparison with an embodiment.

[0127] Those skilled in the art will appreciate that some of the operations described may also be performed by the electronic device (101) and / or the network (400) according to the embodiment, as performed by the electronic device (101) and / or the network (400) described in the comparative example.

[0128] The electronic device (101) may establish at least one PDU session based on preset information in operation 501. For example, as described with reference to FIG. 4, the electronic device (101) may establish a PDU session based on pre-stored preset information before receiving a URSP rule from the network (400) (e.g., PCF) and / or when the received URSP rule is inapplicable. In the example of FIG. 5, it is assumed that the electronic device (101) establishes at least one PDU session based on preset information based on not receiving a URSP rule from the network (400). For example, the electronic device (101) may perform an operation (e.g., transmitting a PDU session establishment request message, receiving a PDU session establishment approval message, and / or transmitting a PDU session establishment completion message) to establish a PDU session of the DNN of the "IMS" and a PDU session of the DNN of the "internet" using information indicating a DNN of the "IMS" and information indicating a DNN of the "internet", which are pre-stored information, as described in FIG. 4.

[0129] The network (400) may transmit a manage UE policy command message to the electronic device (101) at operation 503. The electronic device (101) may transmit a manage UE policy complete message to the network (400) at operation 505. The manage UE policy command may include, for example, a URSP rule, but is not limited thereto. The electronic device (101) may transmit, at operation 507, a first PDU session release request message for a first PDU session, which is a PDU session having preset information corresponding to the URSP rule, to the network (400). For example, if the URSP rule includes a URSP rule corresponding to a DNN of "internet," the electronic device (101) may confirm that establishment of a PDU session based on the URSP rule corresponding to the DNN included in the URSP rule is requested. Accordingly, the electronic device (101) may transmit a first PDU session release request message to the network (400). The network (400) may transmit a first PDU session release accept message corresponding to the first PDU session release request. Accordingly, the first PDU session may be released. Based on the release of the first PDU session, the electronic device (101) may transmit a first PDU session establishment request message based on the URSP rule to the network (400) in operation 511. For example, it is assumed that information on the previously established first PDU session and information included in the URSP rule are the same. The network (400) may transmit a first PDU session establishment accept message corresponding to the first PDU session establishment request message to the electronic device (101) in operation 513.In the comparative example, for example, even though the information included in the URSP rule and the information about the established PDU session are identical, and / or at least partially identical, the electronic device (101) must release the first PDU session and re-establish the first PDU session, which may result in a service interruption period. The electronic device (101) according to the embodiment may, if it is confirmed that the URSP rule is applicable, perform a procedure for maintaining the established PDU session or establishing a PDU session after release, based on the comparison result between the information about the established PDU session and the information in the URSP rule, which will be described with reference to FIG. 6.

[0130] FIG. 6A is a drawing for explaining an operation method of an electronic device according to one embodiment.

[0131] According to one embodiment, the electronic device (101) may perform at least one operation for establishing a first PDU session based on information for establishing a pre-stored PDU session in operation 601. For example, the information for establishing a pre-stored PDU session may include, but is not limited to, information about a DNN (or an access point name (APN)), information about a PDU type (e.g., information about an IP version, such as, but not limited to, information indicating whether it is IPv4 or IPv6), information about whether a P_CSCF_REQ is requested, information about a PCO (e.g., but not limited to, information indicating whether an extended protocol configuration options request is required), information about an S-NSSAI (e.g., SST and / or SD), and / or information about an ALAWAYS_ON_PDU. The first PDU session established by the electronic device (101) based on information for establishing a pre-stored PDU session may be named, for example, a default PDU session, and there is no limitation on the trigger for establishing the default PDU session.

[0132] After the first PDU session is established, the electronic device (101) can, in operation 603, identify the occurrence of an event related to the application of the URSP rule. For example, the electronic device (101) can identify the receipt of a URSP rule from the network (400) as an event related to the application of the URSP rule. For example, the electronic device (101) can receive a URSP rule from the network (400) after establishing a default PDU session, and in this case, the reception of the URSP rule from the network (400) can be identified as an event. For example, the electronic device (101) can identify the reception of a new URSP rule (or a changed or updated URSP rule) as an event. In this case, the electronic device (101) may confirm the reception of a new URSP rule as an event after establishing a PDU session (in this case, it may not be a default PDU session) based on an existing URSP rule. For example, the electronic device (101) may confirm the applicability of a previously inapplicable URSP rule as an event. For example, a URSP rule may not be applicable in an EPS (evolved packet system) but may be applicable in a 5GS (5th generation system). The electronic device (101) can manage that the URSP rule is not applicable when registered in the EPS (or EPC (evolved packet core)). The electronic device (101) can confirm the applicability of the URSP rule as an event based on subsequent registration in the 5GS (or 5GC (5th generation core)). Meanwhile, there is no limitation on the type and / or number of events related to the application of the URSP rule.

[0133] The electronic device (101) can, in operation 605, determine whether to maintain the first PDU session based on the comparison result between the URSP rule and the information on the first PDU session. If it is determined to maintain the first PDU session (operation 605 - Yes), the electronic device (101) can maintain the first PDU session in operation 607. Those skilled in the art will understand that the electronic device (101) may not perform additional operations to maintain the first PDU session. If it is determined not to maintain the first PDU session (operation 605 - No), the electronic device (101) can, in operation 609, perform at least one operation to release the first PDU session and, based on the release of the first PDU session, perform at least one operation to establish a second PDU session based on the URSP rule.

[0134] For example, the electronic device (101) can manage (store and / or update) information about the first PDU session based on the establishment of the first PDU session. Table 1 is an example of information about each of the PDU sessions, for example, when the electronic device (101) establishes a PDU session of the DNN of the internet and a PDU session of the DNN of the IMS.

[0135] Table 1

[0136]

[0137] The information in Table 1 may be verified based on, for example, information pre-stored (or pre-set) in the electronic device (101) and / or information provided by the network (400) (for example, information in a PDU session establishment approval message), but there is no limitation on the verification method. The electronic device (101) may compare, for example, information about a PDU session such as Table 1 with the URSP rules. Tables 2 and 3 are examples of URSP rules.

[0138] Table 2

[0139]

[0140] Table 3

[0141]

[0142] For example, the electronic device (101) can identify a comparison target URSP rule based on a first part of information about the first PDU session. In one embodiment, the comparison target URSP rule can be a URSP rule that can be compared. Here, the first part can be, for example, information about types defined in the TD (for example, but not limited to, application descriptor, IP descriptor, domain descriptor, non-IP descriptor, DNN, and / or connection capabilities). For example, the electronic device (101) can use a DNN, which is a type defined in the TD among the information about the PDU session as shown in Table 1, as the first part for identifying the comparison target URSP rule. Meanwhile, those skilled in the art will understand that information about a PDU session may include, in addition to the above-described DNN, an application descriptor, an IP descriptor, a domain descriptor, a non-IP descriptor, and / or connection capabilities, and that the information may be used to identify a URSP rule to be compared as a first part.

[0143] Referring back to Table 1, the URSP rule in Table 2, which has the same DNN as "IMS", the DNN of the PDU session with PSI "6", can be identified as the URSP rule to be compared with respect to the information for the PDU session with PSI "6".

[0144] For example, the electronic device (101) can determine whether the first PDU session is maintained by comparing the second part of the information about the first PDU session with the RSD of the URSP rule to be compared. For example, the second part of the information about the first PDU session can be information about types defined in the RSD (e.g., but not limited to, SSC mode, SST, SD, DNN, PDU session type, non-seamless offload indication, ProSe layer-3 UE-to-Network relay Offload indication, ProSe Multi-path preference, access type preference, PDU session pair ID, RSN, time window, and / or location criteria). Referring to Table 1, information about PDU session type, SSC mode, SST, and SD of a PDU session having PSI of "6" can be compared with the RSD of the URSP rule to be compared as the second part of the information about the PDU session. Referring to Table 2, the RSD of the URSP rule to be compared may be SST=1, IPType=IPv6. In addition, referring to Table 1, the RSD of the URSP rule to be compared may be SST=1, IPType=IPv6 of the PDU session with PSI of "6". The electronic device (101) can confirm that the second part of the information on the PDU session and the RSD of the URSP rule are the same, and thus can confirm to maintain the PDU session with PSI of "6". Various embodiments regarding the relationship between the comparison result and whether or not to maintain the PDU session will be described later.

[0145] For example, referring back to Table 1, the electronic device (101) can identify the URSP rule of Table 3 having the same DNN as "internet", which is the DNN of the PDU session having PSI "5", as a URSP rule to be compared with respect to information about the PDU session having PSI "5". Referring to Table 1, information about the PDU session type, SSC mode, SST, and SD of the PDU session having PSI "5" can be compared with the URSP rule to be compared, for example, the RSD of the URSP rule of Table 3, as a second part of the information about the PDU session. Referring to Table 3, the RSD of the URSP rule to be compared may be SST=1, SD=3000, DNN=internet, IPType=IPv6. In addition, referring to Table 1, the RSD of the URSP rule to be compared may be SST=1, IPType=IPv4 of the PDU session with PSI of "5". The electronic device (101) may determine that IPType=4, which is part of the second part of the information about the PDU session, is different from IPType=6, which is part of the RSD of the URSP rule of Table 3, which is the URSP rule to be compared, and thus may determine not to maintain the PDU session with PSI of "5". In this case, the electronic device (101) may perform at least one operation for releasing the PDU session with PSI of "5". The electronic device (101) may perform at least one operation for establishing a PDU session based on a URSP rule, for example, a URSP rule such as Table 3, based on the release of the PDU session with PSI of "5". For example, the electronic device (101) may transmit a PDU session establishment request message including at least a portion of the RSD of the URSP rule of Table 3 to the network (400). Accordingly, the PDU session of IPType=IPv4 may be released, and a PDU session of IPType=IPv6 following the URSP rule may be established.

[0146] For example, the electronic device (101) can determine that the TD of the URSP rule of Table 3 corresponds to a PDU session with a PSI of 5 and a PDU session with a PSI of 6 based on the fact that the TD of the URSP rule of Table 3 corresponds to "match all". In this case, the electronic device (101) can additionally determine whether at least some of the RSDs of the URSP rule of Table 3 correspond to at least some of the information about the PDU session. The electronic device (101) can determine that the DNN "internet" among the RSDs of the URSP rule of Table 3 corresponds to the PDU session with a PSI of 5, and accordingly, the electronic device can determine the URSP rule to be compared for the PDU session with a PSI of "internet" as the URSP rule of Table 3. For example, the DNN may also be included in the TD according to the 3GPP (3rd generation project partnership) standard. The electronic device (101) can use, for example, a DNN commonly reflected in TD among RSDs of URSP rules as a parameter for confirming the URSP rule to be compared, but there is no limitation.

[0147] For example, the electronic device (101) can determine that the TD of the URSP rule of Table 3 corresponds to a PDU session with a PSI of 5 and a PDU session with a PSI of 6 based on the fact that the TD of the URSP rule of Table 3 corresponds to "match all". In this case, the electronic device (101) can exclude the PDU session with a PSI of 6 based on the fact that the first part of the information for the PDU session with a PSI of 6 corresponds to a TD other than "match all" of the URSP rule of Table 2 (e.g., another URSP rule). Accordingly, the electronic device (101) can determine the URSP rule to be compared for the PDU session with a PSI of 5 as the URSP rule of Table 3.

[0148] Meanwhile, the release of the first PDU session and the establishment of the second PDU session in operation 609 are merely exemplary, and the electronic device (101) may perform at least one operation for PDU session modification based on the RSD of the URSP rule, instead of operation 609. Those skilled in the art will understand that the release of the first PDU session and the establishment of the second PDU session in the embodiments of the present disclosure as well as in the present embodiment may be replaced with PDU session modification.

[0149] According to the above, based on the applicability of the URSP rule, rather than releasing all existing PDU sessions as in the comparative example and then establishing a PDU session according to the URSP rule, PDU sessions that follow the URSP rule are maintained, but PDU sessions that do not follow the URSP rule can be selectively released and then established.

[0150] FIG. 6b is a drawing for explaining an operation method of an electronic device according to one embodiment.

[0151] According to one embodiment, the electronic device (101) may, in operation 621, identify a first URSP rule including a first TD corresponding to a first part of information about a first PDU session among the URSP rules. Here, the first part may be, for example, but is not limited to, information about types defined in the TD (for example, but not limited to, an application descriptor, an IP descriptor, a domain descriptor, a non-IP descriptor, a DNN, and / or connection capabilities). For convenience of explanation, the first part may also be referred to as a TD of the first PDU session.

[0152] For example, as described above, the electronic device (101) can identify a URSP rule such as Table 2 including a DNN of "IMS" as a URSP rule to be compared, and the DNN as part of the first part of the information on the PDU session with PSI 6 in Table 1 may be "IMS". For example, the electronic device (101) can identify a URSP rule including the same information as one or more pieces of information of the first part of the information on the PDU session as a URSP rule to be compared. If a part of the first part of the information on the PDU session is the same as a part of the information of the URSP rule, but another part may be different from the information of the URSP rule. In this case, the electronic device (101) can identify a URSP rule including different information from a part of the first part as a URSP rule to be compared. Alternatively, the electronic device (101) may determine that a URSP rule containing different information from a portion of the first part is not a URSP rule to be compared. The electronic device (101) may apply a specified rule to information that matches and / or information that does not match between the first part and the URSP rule, and may determine whether the URSP rule is a rule to be compared based on the result of the application. There is no limitation on the rules for determining whether the URSP rule is a rule to be compared.

[0153] The electronic device (101) can check, in operation 623, whether the second part of the information about the first PDU session corresponds to the RSD of the first URSP rule. The second part of the information about the PDU session may be information about types defined in the RSD (for example, but not limited to, SSC mode, SST, SD, DNN, PDU session type, non-seamless offload indication, ProSe layer-3 UE-to-Network relay Offload indication, ProSe Multi-path preference, access type preference, PDU session pair ID, RSN, time window, and / or location criteria). For convenience of explanation, the second part of the information about the PDU session may also be referred to as the RSD of the PDU session. For example, the electronic device (101) may determine that the second part of the information about the first PDU session corresponds to the RSD of the URSP rule based on the fact that the second part of the information about the PDU session and at least one of the information in the RSD of the URSP rule are identical. If a part of the second part of the information about the PDU session is identical to a part of the RSD of the URSP rule, another part may be different from another part of the RSD of the URSP rule. In this case, the electronic device (101) may determine that the URSP rule including information that is different from a part of the second part corresponds to the PDU session. Alternatively, the electronic device (101) may determine that the URSP rule including information that is different from a part of the second part does not correspond to the PDU session.The electronic device (101) may apply a specified rule for matching and / or mismatching information between the second part and the URSP rule, and may check whether there is a correspondence between the PDU session and the URSP rule based on the application result, and there is no limitation on the rule for determining whether it is a rule to be compared. If it is confirmed that the second part of the information about the first PDU session and the RSD of the URSP rule correspond (Operation 623 - Yes), the electronic device (101) may determine to maintain the first PDU session in operation 625. If it is confirmed that the second part of the information about the first PDU session and the RSD of the URSP rule do not correspond (Operation 623 - No), the electronic device (101) may determine not to maintain the first PDU session in operation 627. In this case, the electronic device (101) can perform at least one operation for releasing the first PDU session and at least one operation for establishing the second PDU session, as described above.

[0154] FIG. 6c is a drawing for explaining an operation method of an electronic device according to one embodiment.

[0155] According to one embodiment, the electronic device (101) may, in operation 641, identify a first URSP rule including a first RSD corresponding to a first part of information about a first PDU session among the URSP rules. In the example of FIG. 6C, the electronic device (101) may identify a URSP rule to be compared for the first PDU session based on a comparison result between the first part of information about the first PDU session (or the TD of the first PDU session) and the RSD of the URSP rule. For example, the DNN may be included in the TD or may be included in the RSD according to the 3GPP standard. For example, as in the example in Table 3, the DNN may be included in the RSD of the URSP rule, and the electronic device (101) may thus identify the first URSP rule including the first RSD corresponding to the first part of the information about the first PDU session. In operation 643, the electronic device (101) may identify whether the second part of the information about the first PDU session corresponds to the RSD of the first URSP rule. For example, in operation 641, the electronic device (101) may identify any one URSP rule as the first URSP rule to be compared based on the DNN that can be simultaneously included in the TD and the RSD. The electronic device (101) may compare the second part of the information about the first PDU session and the RSD of the first URSP rule to be compared, thereby identifying whether the first PDU session is maintained. If the second part of the information about the first PDU session corresponds to the RSD of the first URSP rule (operation 643 - yes), the electronic device (101) can confirm that the first PDU session will be maintained in operation 645.If the second part of the information for the first PDU session and the RSD of the first URSP rule do not correspond (action 643 - No), the electronic device (101) can determine, in operation 647, not to maintain the first PDU session.

[0156] FIG. 7 is a drawing for explaining an operation method of an electronic device and a network according to one embodiment.

[0157] According to one embodiment, the electronic device (101) may establish a first PDU session and a second PDU session based on preset information in operation 701. The preset information may include, but is not limited to, DNN, SST, SD, IP type, SSC mode, P_CSCF_REQ, and / or PCO. As described above, the first PDU session and the second PDU session may also be named a default PDU session, but is not limited to. The electronic device (101) may manage information about the PDU sessions in operation 703. For example, the electronic device (101) may manage information about the PDU sessions as described in Table 1, but is not limited to. The electronic device (101) may receive a management UE policy command message from the network (400) in operation 705. For example, the management UE policy command message may include a URSP rule. For example, the electronic device (101) may receive URSP rules as described in Tables 2 and 3 from the network (400), but without limitation. The electronic device (101) may, in operation 707, transmit a management UE policy completion message corresponding to the management UE policy command message to the network (400).

[0158] The electronic device (101) can, in operation 709, confirm that the first part of the information about the first PDU session corresponds to the TD and / or RSD of the first URSP rule. For example, the first part of the information about the PDU session may be information about types defined by the TD, but is not limited thereto. As described with reference to FIGS. 6B and 6C , the electronic device (101) can compare the first part of the information about the PDU session with the TD of the URSP rule and / or with the RSD of the URSP rule. Based on the comparison result, the electronic device (101) can confirm that the first part of the information about the first PDU session corresponds to the TD and / or RSD of the first URSP rule, and thus confirm the first URSP rule as a URSP rule to be compared with the first PDU session. The electronic device (101), in operation 711, can determine to maintain the first PDU session based on whether the second part of the information about the first PDU session corresponds to the RSD of the first URSP rule. For example, the second part of the information about the PDU session may be information about types defined by the RSD, but is not limited thereto. Based on the determination to maintain the first PDU session, the electronic device (101) can continuously perform communication through the first PDU session, thereby preventing communication disconnection due to unnecessary release and re-establishment of the first PDU session.

[0159] The electronic device (101), in operation 713, can confirm that the first part of the information about the second PDU session corresponds to the TD and / or RSD of the second URSP rule. Accordingly, the second URSP rule can be confirmed as a URSP rule to be compared for the second PDU session. The electronic device (101), in operation 715, can confirm that the second PDU session is to be released and a third PDU session is to be established based on the second part of the information about the second PDU session not corresponding to the RSD of the second URSP rule. The electronic device (101), in operation 717, can transmit a second PDU session release request message to the network (400). The electronic device (101), in operation 719, may receive a second PDU session release acknowledgement message corresponding to the second PDU session release request message from the network (400). The second PDU session may be released based on the transmission / reception of the second PDU session release request message and the second PDU session release acknowledgement message. The electronic device (101), based on the release of the second PDU session, may perform at least one operation for establishing a third PDU session, which is a PDU session based on the RSD of the second URSP rule. The electronic device (101), in operation 721, may transmit the third PDU session establishment request message based on the RSD of the second URSP rule to the network (400). The electronic device (101), in operation 725, may manage information about the PDU session. For example, the electronic device (101) may delete information about a released second PDU session and add information about a newly established third PUD session, but there is no limitation.

[0160] For example, based on the fact that the PDU session type "ipv4", which is part of the second part of the information about the PDU session with PSI "5" in Table 1, does not correspond to the IPType "ipv6" of the URSP rule of Table 3, which is the URSP rule to be compared, the electronic device (101) may perform at least one operation for releasing the PDU session with PSI "5". Based on the release of the PDU session with PSI "5", the electronic device (101) may perform at least one operation for establishing a PDU session based on the URSP rule of Table 3. The electronic device (101) may update the information about the PDU session as in Table 1 and manage the information about the PDU session as in Table 4.

[0161] Table 4

[0162]

[0163] For example, while information about a PDU session with a PSI of "5" in Table 1 may be excluded, information about a PDU session with a PSI of "7" may be included in the information in Table 4. In the example in Table 4, it is described that the PSI (e.g., 7) of a newly created PDU session is set differently from the PSI (e.g., 5) of a released PDU session, but this is exemplary, and the PSI of a released PDU session and the PSI of a newly created PDU session may be the same. As a PDU session is created based on the URSP rule in Table 3, it can be confirmed that the DNN of the information about the PDU session with a PSI of "7" is "internet", the PDU session type is "ipv6", the SST is "1", and the SST is "3000". In addition, in the RSD_ID field, it can be managed that each PDU session corresponds to an RSD of an identifier of 0x21 and an RSD of an identifier of 0x11. With respect to information about a PDU session whose PSI is "6", for example, the RSD_ID field can be changed from none (e.g., a value indicating that the PDU is not generated by RSD) to the identifier of the corresponding RSD (e.g., 0x11). As described above, when an event for applying the URSP rule occurs, the electronic device (101) can release all existing PDU sessions and not create a PDU session based on the URSP rule, while maintaining a PDU session corresponding to the URSP rule (e.g., the first PDU session) and releasing a PDU session (e.g., the second PDU session) that does not correspond to the URSP rule, and then establish a PDU session (e.g., the third PDU session) based on the URSP rule.

[0164] Figure 8 is a flowchart for explaining an operating method of an electronic device according to one embodiment.

[0165] According to one embodiment, the electronic device (101) may, in operation 801, confirm the occurrence of an event related to the application of the URSP rule. In operation 803, the electronic device (101) may confirm whether there is a PDU session corresponding to the URSP rule among at least one pre-established PDU session (or whether there is a URSP rule to be compared corresponding to at least one pre-established PDU session). For example, as described with reference to FIGS. 6b and 6c, the electronic device (101) may confirm whether there is a URSP rule corresponding to the first part associated with the types defined by the TD among the information about the URSP PDU session, but there is no limitation. If it is determined that there is no PDU session corresponding to the URSP rule among at least one established PDU session (Operation 803 - No), the electronic device (101) can maintain at least one established PDU session in operation 805. If it is determined that there is a PDU session corresponding to the URSP rule among at least one established PDU session (or, it is determined that there is a URSP rule to be compared corresponding to the PDU session), the electronic device (101) can check whether the information of the corresponding PDU session and the RSD of the URSP rule correspond in operation 807. For example, the electronic device (101) can check whether the second part of the information on the corresponding PDU session and the RSD of the URSP rule correspond, but there is no limitation. If it is confirmed that the information of the corresponding PDU session and the RSD of the URSP rule correspond (action 807 - yes), the electronic device (101) can maintain the corresponding PDU session in operation 809.If it is determined that the information of the corresponding PDU session and the RSD of the URSP rule do not correspond (Action 807 - No), the electronic device (101) may, in operation 811, perform at least one operation for releasing the established PDU session and at least one operation for establishing a PDU session based on the RSD of the URSP.

[0166] FIG. 9 is a drawing for explaining an operating method of an electronic device according to one embodiment.

[0167] According to one embodiment, the electronic device (101) may, in operation 901, identify a first part associated with a type defined in a TD among the information about a pre-established PDU session. For example, the electronic device (101) may identify a DNN among the information about a pre-established PDU session as part of the first part, but those skilled in the art will understand that information associated with a type defined in a TD and / or additional information may be used as the first part. The electronic device (101) may, in operation 903, identify a URSP rule corresponding to the first part among the URSP rules. For example, the electronic device (101) may identify a URSP rule including a TD and / or an RSD corresponding to the first part as a URSP to be compared with respect to the pre-established PDU session, as described with reference to FIGS. 6B and 6C . The electronic device (101), in operation 905, can determine whether the PDU session is maintained based on whether the entire second part associated with the types defined in the RSD among the information about the established PDU session corresponds to the RSD of the identified rule. For example, the electronic device (101) can determine the four pieces of information of the PDU session type, SSC mode, SST, and SD as the second part of the information about the established PDU session, as shown in Table 1, but there is no limitation. The electronic device (101) can determine whether the established PDU session is maintained based on whether the entire four pieces of information of the PDU session type, SSC mode, SST, and SD are identical to the URSP rule to be compared. For example, the electronic device (101) may determine to maintain the established PDU session by confirming that the established PDU session corresponds to the URSP rule when all four pieces of information, PDU session type, SSC mode, SST, and SD, are identical to the information of RSD of the URSP rule.If some of the four pieces of information, PDU session type, SSC mode, SST, and SD, are not included in the URSP rule to be compared, the electronic device (101) may determine whether to maintain the established PDU session based on whether all of the information not included in the URSP rule is identical to the information in the URSP rule. If any one piece of information is different from the information in the URSP rule, the electronic device (101) may determine that the established PDU session does not correspond to the URSP rule, release the established PDU session, and establish a PDU session based on the URSP rule.

[0168] FIG. 10 is a drawing for explaining an operating method of an electronic device according to one embodiment.

[0169] According to one embodiment, the electronic device (101) may, in operation 1001, identify a first part associated with a type defined in a TD among information about a pre-established PDU session. In operation 1003, the electronic device (101) may identify a URSP rule corresponding to the first part among URSP rules. In operation 1005, the electronic device (101) may identify whether the pre-established PDU session is maintained based on whether some of the second parts associated with types defined in an RSD among information about the pre-established PDU session correspond to the RSD of the identified rule. For example, the electronic device (101) may determine whether the pre-established PDU session is maintained based on whether some of four pieces of information, namely, PDU session type, SSC mode, SST, and SD, are identical to a URSP rule to be compared. For example, the electronic device (101) may determine that the established PDU session corresponds to the URSP rule even though the SSC mode does not match the URSP rule based on the fact that the designated information, among the four pieces of information of the PDU session type, SSC mode, SST, and SD, matches the URSP rule, but there is no limitation on the type and / or number of information that can be ignored. For example, the electronic device (101) may determine whether to maintain the established PDU session based on the number of pieces of information (or matching ratio) that match the URSP rule among the total number of pieces of information to be compared, and there is no limitation on the conditions for determining whether to maintain the established PDU session.

[0170] FIG. 11 a is a drawing for explaining an operating method of an electronic device according to one embodiment.

[0171] According to one embodiment, the electronic device (101) may, in operation 1101, confirm registration of a previously received URSP rule with an available network as an event (e.g., an event for applying a URSP rule). For example, whether some RSDs of the URSP rule are applicable may be determined on a network-by-network basis. Table 5 shows examples of RSDs defined in 3GPP TS 24.526.

[0172] Table 5

[0173]

[0174] For example, when the electronic device (101) is registered in the EPS (or EPC), the URSP rule including at least some of the parameters of Table 5 in the RSD may be determined to be inapplicable. Even if the electronic device (101) receives the URSP rule from the network (400), it may determine that the URSP rule is inapplicable in the state of being registered in the EPS and may not use it. The electronic device (101) may move (or may be referred to as handover) from the EPS to the 5GS. Based on the electronic device (101) being registered in the 5GS, it may be determined that the URSP rule including at least some of the parameters of Table 5 in the RSD is applicable. Accordingly, the electronic device (101) may determine registration in a network (e.g., 5GS) that can use the URSP rule as an event. The electronic device (101), in operation 1103, can check the URSP rule corresponding to the first part associated with the type defined in the TD among the information about the first PDU session that has already been established. In operation 1105, the electronic device (101), based on the result of comparing the second part associated with the type defined in the RSD among the information about the first PDU session that has already been established and the RSD of the identified URSP rule, can maintain the establishment of the first PDU session or perform at least one operation for establishing a second PDU session based on the RSD of the rule.

[0175] FIG. 11b is a diagram for explaining an operation method of an electronic device and a network according to one embodiment.

[0176] According to one embodiment, the electronic device (101) may manage the acquired URSP rule in operation 1111. For example, the electronic device (101) may manage the URSP rule as not applicable when the electronic device (101) is registered in another network (1150), for example, EPS. For example, based on the inclusion of at least some of the parameters of Table 5 described above in the RSD, the URSP rule may be managed as not applicable in another network (1150), for example, EPS. The electronic device (101) may transmit a PDN (packet data network) connection request message to the other network (1150) in operation 1113. The other network (1150) may transmit a PDN connection approval message corresponding to the PDN connection request message to the electronic device (101) in operation 1115. Accordingly, a PDN connection may be established. For example, the electronic device (101) can establish a PDN connection based on pre-stored information, but there is no limitation. The electronic device (101) can manage information about the PDN connection in operation 1117. The electronic device (101) can confirm that it will move to a network (400) that can use the URSP rule, for example, 5GS, in operation 1119. The electronic device (101) can perform at least one operation for registration in the network (400), for example, 5GS, in operation 1121. The electronic device (101) can manage information about the PDU session in operation 1123. For example, the electronic device (101) can change information about the PDN connection to information about the PDU session based on the movement from EPS to 5GS. For example, the EPS bearer identifier (EBI) of a PDN connection can be changed to PSI, but this is exemplary and there is no limitation on the type and / or number of information that is converted.

[0177] The electronic device (101), in operation 1125, can confirm that the first URSP rule corresponds to the first part of the information about the first PDU session. The electronic device (101) can confirm the first URSP rule as a URSP rule to be compared for the first PDU session. In operation 1127, the electronic device (101) can confirm that the first PDU session is maintained based on the correspondence between the second part of the information about the first PDU session and the RSD of the first URSP rule. In operation 1129, the electronic device (101) can confirm that the second URSP rule corresponds to the first part of the information about the second PDU session. The electronic device (101) can confirm the second URSP rule as a URSP rule to be compared for the second PDU session. The electronic device (101), in operation 1131, may determine to release the second PDU session and establish a third PDU session based on the fact that the second part of the information about the second PDU session and the RSD of the second URSP rule do not correspond. The electronic device (101), in operation 1133, may transmit a second PDU session release request message to the network (400). The network (400), in operation 1135, may transmit a second PDU session release approval message corresponding to the second PDU session release request message to the electronic device (101). Accordingly, the second PDU session may be released. Based on the release of the second PDU session, the electronic device (101), in operation 1137, may transmit a third PDU session establishment request message to the network (400). The network (400) may, in operation 1139, transmit a third PDU session establishment approval message corresponding to the third PDU session establishment request message to the electronic device (101). Accordingly, a third PDU session based on the second URSP rule may be established. The electronic device (101) may, in operation 1141, manage information about the PDU session.For example, information about the second PDU session may be deleted and information about the third PDU session may be added, but there are no restrictions on how this is managed.

[0178] FIG. 12 a is a drawing for explaining an operating method of an electronic device according to one embodiment.

[0179] According to one embodiment, the electronic device (101) may, in operation 1201, confirm the occurrence of an event related to the application of the URSP rule. In operation 1203, the electronic device (101) may confirm that the first URSP rule corresponds to the first part of the information about the first PDU session. The electronic device (101) may confirm the first URSP rule as a URSP rule to be compared with respect to the first PDU session. In operation 1205, the electronic device (101) may confirm that the first PDU session is to be released based on confirmation that the second part of the information about the first PDU session and the RSD of the first URSP rule do not correspond. In operation 1207, the electronic device (101) may confirm whether a service based on the first PDU session is being performed. In one example, the electronic device (101) can determine that a service based on the first PDU session is being performed if the RRC state corresponding to the first PDU session is an RRC_Connected state. If the RRC state corresponding to the first PDU session is an RRC_idle state or an RRC_inactive state, the electronic device (101) can determine that the service based on the first PDU session is not being performed. If it is determined that the service based on the first PDU session is being performed (operation 1207 - Yes), the electronic device (101) can postpone the release of the first PDU session in operation 1209. If the first PDU session is released while the service based on the first PDU session is being performed, it may cause the service to be interrupted, and therefore, the electronic device (101) can postpone the release of the PDU session until the service is terminated. Accordingly, the release of a PDU session may be delayed while a service based on the PDU session is being performed.If it is determined that the service based on the first PDU session is not being performed (action 1207 - No), the electronic device (101) may, in operation 1211, release the first PDU session and perform at least one operation for establishing a second PDU session based on the RSD of the first URSP rule.

[0180] FIG. 12b is a diagram for explaining an operation method of an electronic device and a network according to one embodiment.

[0181] According to one embodiment, the electronic device (101) may establish a first PDU session of the IMS based on preset information in operation 1231. The electronic device (101) may manage information about the PDU session in operation 1233. The electronic device (101) may connect a voice call using, for example, the first PDU session of the IMS in operation 1235. While the voice call is connected, the RRC state of the first PDU session of the IMS may be an RRC_CONNECTED state. The electronic device (101) may receive a management UE policy command message from the network (400) in operation 1237. For example, the electronic device (101) may check the URSP rule included in the management UE policy command message. The electronic device (101) may transmit a management UE policy completion message corresponding to the management UE policy command message to the network (400) in operation 1239. The electronic device (101) may confirm that the second part of the information about the first PDU session and the RSD of the first URSP rule do not correspond in operation 1241. The electronic device (101) may postpone the release of the first PDU session until the voice call is terminated in operation 1243. The electronic device (101) may confirm the termination of the voice call in operation 1245. For example, the electronic device (101) may confirm whether the RRC state corresponding to the first PDU session is changed from the RRC_CONNECTED state to another state as whether the voice call is terminated, but this is exemplary and there is no limitation on the method of confirming whether the voice call is terminated. The electronic device (101), in operation 1247, may transmit a first PDU session release request message to the network (400) based on confirmation of termination of the voice call. The network (400), in operation 1249, may transmit a first PDU session release approval message corresponding to the first PDU session release request message to the electronic device (101).Accordingly, the first PDU session may be released. Based on the release of the first PDU session, the electronic device (101) may transmit a second PDU session establishment request message to the network (400) in operation 1251. The network (400) may transmit a second PDU session establishment approval message corresponding to the second PDU session establishment request message to the electronic device (101) in operation 1253. Accordingly, the second PDU session based on the first URSP rule may be established. The electronic device (101) may manage information about the PDU session in operation 1255. For example, information about the first PDU session may be deleted and information about the second PDU session may be added, but there is no limitation on the management method.

[0182] FIG. 13 is a drawing for explaining an operating method of an electronic device according to one embodiment.

[0183] According to one embodiment, the electronic device (101) may, in operation 1301, confirm the occurrence of an event related to the application of the URSP rule. In operation 1303, the electronic device (101) may confirm that the first URSP rule corresponds to the first part of the information about the first PDU session. In operation 1305, the electronic device (101) may confirm that the second part of the information about the first PDU session and the RSD of the first URSP rule do not correspond. Accordingly, in operation 1307, the electronic device (101) may perform the release of the first PDU session and the establishment of a second PDU session based on the RSD of the first URSP rule. In operation 1309, the electronic device (101) may confirm the occurrence of an event related to the deactivation of the URSP rule. For example, the electronic device (101) can identify the reception of information about the deletion of a URSP rule (e.g., an empty rule) from the network (400) as an event related to the deactivation of the URSP rule. For example, the electronic device (101) can identify registration to another network (e.g., EPS) to which the URSP rule cannot be applied as an event related to the deactivation of the URSP rule, but there is no limitation. Based on the identification of the event related to the deactivation of the URSP rule, the electronic device (101) can, in operation 1311, identify whether the second part of the information about the second PDU session corresponds to pre-stored information (e.g., information for creating a default PDU session). If the second part of the information about the second PDU session corresponds to the pre-stored information (operation 1311 - Yes), the electronic device (101) can maintain the second PDU session in operation 1313. If the second part of the information about the second PDU session does not correspond to the pre-stored information (operation 1311 - No), the electronic device (101) may perform at least one operation for releasing the second PDU session in operation 1315.The electronic device (101) may, based on the release of the second PDU session, in operation 1317, perform at least one operation for establishing a PDU session based on pre-stored information (e.g., information for establishing a default PDU session). As described above, based on the inapplicability of the URSP rule, existing PDU sessions are not released all at once and then PDU sessions are established based on the pre-stored information for creating a default PDU session, but PDU sessions that follow the information for creating a default PDU session are maintained, while PDU sessions that do not follow the information for creating a default PDU session may be selectively released and then established. For example, the number of PDU sessions that follow the information for creating a default PDU session and / or PDU sessions that do not follow it may be one or more, and there is no limitation.

[0184] The electronic device (101) may include at least one processor (120, 212, 214, 260).

[0185] The electronic device (101) may include a memory (130) that stores instructions.

[0186] The above instructions, when individually or collectively executed by the at least one processor (120, 212, 214, 260), may cause the electronic device (101) to perform at least one operation for establishing a first protocol data unit (PDU) session based on information for establishing a PDU session pre-stored in the electronic device (101).

[0187] The above instructions, when individually or collectively executed by the at least one processor (120, 212, 214, 260), may cause the electronic device (101) to identify the occurrence of an event related to the application of a URSP rule.

[0188] The above instructions, when individually or collectively executed by the at least one processor (120, 212, 214, 260), may cause the electronic device (101) to determine whether to maintain or release the first PDU session based on a comparison result between the URSP rule and information about the first PDU session, based on confirmation of the occurrence of the event.

[0189] The above instructions, when individually or collectively executed by the at least one processor (120, 212, 214, 260), may cause the electronic device (101) to perform at least one operation for releasing the first PDU session based on determining that the first PDU session is to be released, and to perform at least one operation for establishing a second PDU session based on at least a part of the URSP rule based on the release of the first PDU session.

[0190] The above instructions, when individually or collectively executed by the at least one processor (120, 212, 214, 260), may cause the first TD (traffic descriptor) of the URSP rule to be verified to correspond to a first part of the information for the first PDU session.

[0191] The above instructions, when individually or collectively executed by the at least one processor (120, 212, 214, 260), may cause the first PDU session to be maintained or released based on whether a second part of the information about the first PDU session corresponds to a first RSD (route selection descriptor) of the URSP rule.

[0192] The first part of the information about the first PDU session may include information associated with at least one type defined by TD, and / or the second part of the information about the first PDU session may include information associated with at least one type defined by RSD.

[0193] The above instructions, when individually or collectively executed by the at least one processor (120, 212, 214, 260), may cause the electronic device (101) to determine whether to maintain or release the first PDU session based on whether at least one piece of information included in the second portion is identical to at least a portion of the first RSD.

[0194] The above instructions, when individually or collectively executed by the at least one processor (120, 212, 214, 260), may cause the electronic device (101) to determine whether to maintain or release the first PDU session based on whether at least a portion of the information included in the second portion is identical to at least a portion of the first RSD.

[0195] The above instructions, when individually or collectively executed by the at least one processor (120, 212, 214, 260), may cause the electronic device (101) to verify that the first TD of the URSP rule corresponds to a second part associated with at least one type defined in the RSD among the information for the first PDU session.

[0196] The above instructions, when individually or collectively executed by the at least one processor (120, 212, 214, 260), may cause the electronic device (101) to determine whether to maintain or release the first PDU session based on whether the second portion and the first RSD of the URSP rule correspond.

[0197] The above instructions, when individually or collectively executed by the at least one processor (120, 212, 214, 260), may cause the electronic device (101) to perform at least one operation for releasing the first PDU session and at least one operation for establishing the second PDU session based on determining that at least one operation based on the first PDU session is not performed.

[0198] The above instructions, when individually or collectively executed by the at least one processor (120, 212, 214, 260), may cause the electronic device (101) to postpone performing at least one operation for releasing the first PDU session and at least one operation for establishing the second PDU session until the at least one operation based on the first PDU session is completed, based on determining that at least one operation based on the first PDU session is being performed.

[0199] The above instructions, when individually or collectively executed by the at least one processor (120, 212, 214, 260), may cause the electronic device (101) to perform at least one operation for releasing the first PDU session and at least one operation for establishing the second PDU session based on confirmation that at least one operation based on the first PDU session has been completed.

[0200] The above instructions, when individually or collectively executed by the at least one processor (120, 212, 214, 260), may cause the electronic device (101) to identify registration of the electronic device (101) in a network to which the URSP rule acquired by the electronic device (101) is applicable as the occurrence of the event.

[0201] The above instructions, when individually or collectively executed by the at least one processor (120, 212, 214, 260), may cause the electronic device (101) to perform at least one operation for registration in a network to which the URSP rule is applicable, according to mobility of the electronic device (101) from another network to which the URSP rule is not applicable to the network to which the URSP rule is applicable.

[0202] While the electronic device (101) is registered in the other network, the URSP rule may not be applied.

[0203] The above instructions, when individually or collectively executed by the at least one processor (120, 212, 214, 260), may cause the electronic device (101) to acknowledge the receipt of the URSP rule from the network as the occurrence of the event.

[0204] The above instructions, when individually or collectively executed by the at least one processor (120, 212, 214, 260), may cause the electronic device (101) to perform at least one operation for releasing the second PDU session and at least one operation for establishing a PDU session based on information for establishing a PDU session pre-stored in the electronic device (101), based on detecting an occurrence of an event associated with deactivation of the URSP rule after establishing the second PDU session, and based on information associated with at least one type defined by RSD among information about the second PDU session not corresponding to information for establishing a PDU session pre-stored in the electronic device (101).

[0205] The above instructions, when individually or collectively executed by the at least one processor (120, 212, 214, 260), may cause the electronic device (101) to acknowledge receipt of a command from the network to delete the URSP rule as the occurrence of an event associated with the deactivation of the URSP rule.

[0206] The above instructions, when individually or collectively executed by the at least one processor (120, 212, 214, 260), may cause the electronic device (101) to identify registration with another network to which the URSP rule cannot be applied as an occurrence of an event associated with the deactivation of the URSP rule.

[0207] The above instructions, when individually or collectively executed by the at least one processor (120, 212, 214, 260), may cause the electronic device (101) to maintain the first PDU session based on determining that the first PDU session is to be maintained.

[0208] The method of operating an electronic device (101) may include performing at least one operation for establishing a first protocol data unit (PDU) session based on information for establishing a PDU session pre-stored in the electronic device (101).

[0209] The method of operating the electronic device (101) may include an operation of confirming the occurrence of an event related to the application of a URSP rule.

[0210] The operating method of the electronic device (101) may include an operation of confirming whether to maintain or release the first PDU session based on a comparison result between the URSP rule and information about the first PDU session, based on confirmation of the occurrence of the event.

[0211] The method of operating the electronic device (101) may include performing at least one operation for releasing the first PDU session based on determining that the first PDU session is to be released, and performing at least one operation for establishing a second PDU session based on at least a part of the URSP rule based on the release of the first PDU session.

[0212] The operating method of the electronic device (101) may include an operation of confirming that the first TD (traffic descriptor) of the URSP rule corresponds to a first part of the information for the first PDU session.

[0213] The operating method of the electronic device (101) may include an operation of determining whether to maintain or release the first PDU session based on whether a second part of the information on the first PDU session corresponds to a first RSD (route selection descriptor) of the URSP rule.

[0214] The first part of the information about the first PDU session may include information associated with at least one type defined by TD, and / or the second part of the information about the first PDU session may include information associated with at least one type defined by RSD.

[0215] The operating method of the electronic device (101) may include an operation of determining whether to maintain or release the first PDU session based on whether at least one piece of information included in the second portion is identical to at least a part of the first RSD.

[0216] The method of operating the electronic device (101) may include an operation of determining whether to maintain or release the first PDU session based on whether at least a portion of the information included in the second portion is identical to at least a portion of the first RSD.

[0217] The method of operating the electronic device (101) may include an operation of confirming that the first TD of the URSP rule corresponds to a second part associated with at least one type defined in the RSD among the information for the first PDU session.

[0218] The operating method of the electronic device (101) may include an operation of determining whether the first PDU session is maintained or released based on whether the second portion and the first RSD of the URSP rule correspond.

[0219] The operating method of the electronic device (101) may include performing at least one operation for releasing the first PDU session and at least one operation for establishing the second PDU session based on confirming that at least one operation based on the first PDU session is not performed.

[0220] The operating method of the electronic device (101) may include an operation of postponing the performance of at least one operation for releasing the first PDU session and at least one operation for establishing the second PDU session until the at least one operation based on the first PDU session is completed, based on confirming that at least one operation based on the first PDU session is being performed.

[0221] The operating method of the electronic device (101) may include an operation of performing at least one operation for releasing the first PDU session and at least one operation for establishing the second PDU session based on confirmation that at least one operation based on the first PDU session has been completed.

[0222] The operating method of the electronic device (101) may include an operation of confirming registration of the electronic device (101) in a network to which the URSP rule acquired by the electronic device (101) is applicable as the occurrence of the event.

[0223] The method of operating the electronic device (101) may include performing at least one operation for registration in a network to which the URSP rule can be applied, according to the mobility of the electronic device (101) from another network to which the URSP rule cannot be applied, to a network to which the URSP rule can be applied.

[0224] While the electronic device (101) is registered in the other network, the URSP rule may not be applied.

[0225] The operating method of the electronic device (101) may include an operation of confirming the reception of the URSP rule from the network as the occurrence of the event.

[0226] The operating method of the electronic device (101) may include an operation of detecting an occurrence of an event associated with deactivation of the URSP rule after establishing the second PDU session, and performing at least one operation for releasing the second PDU session and at least one operation for establishing a PDU session based on information associated with at least one type defined by RSD among information about the second PDU session not corresponding to information for establishing a PDU session pre-stored in the electronic device (101), based on which the information does not correspond to information for establishing a PDU session pre-stored in the electronic device (101).

[0227] The method of operating the electronic device (101) may include an operation of confirming receipt of a command for deletion of the URSP rule from a network as an occurrence of an event associated with deactivation of the URSP rule.

[0228] The operating method of the electronic device (101) may include an operation of confirming registration to another network to which the URSP rule cannot be applied as an occurrence of an event associated with the deactivation of the URSP rule.

[0229] The operating method of the electronic device (101) may include an operation of maintaining the first PDU session based on determining that the first PDU session is to be maintained.

[0230] A storage medium for storing computer-readable instructions may be provided.

[0231] The above instructions, when individually or collectively executed by the at least one processor (120, 212, 214, 260), may cause the electronic device (101) to perform at least one operation for establishing a first protocol data unit (PDU) session based on information for establishing a PDU session pre-stored in the electronic device (101).

[0232] The above instructions, when individually or collectively executed by the at least one processor (120, 212, 214, 260), may cause the electronic device (101) to identify the occurrence of an event related to the application of a URSP rule.

[0233] The above instructions, when individually or collectively executed by the at least one processor (120, 212, 214, 260), may cause the electronic device (101) to determine whether to maintain or release the first PDU session based on a comparison result between the URSP rule and information about the first PDU session, based on confirmation of the occurrence of the event.

[0234] The above instructions, when individually or collectively executed by the at least one processor (120, 212, 214, 260), may cause the electronic device (101) to perform at least one operation for releasing the first PDU session based on determining that the first PDU session is to be released, and to perform at least one operation for establishing a second PDU session based on at least a part of the URSP rule based on the release of the first PDU session.

[0235] The electronic device (101) may include at least one processor (120, 212, 214, 260).

[0236] The electronic device (101) may include a memory (130) that stores instructions.

[0237] The above instructions, when individually or collectively executed by the at least one processor (120, 212, 214, 260), may cause the electronic device (101) to perform at least one operation for establishing a first protocol data unit (PDU) session based on information for establishing a PDU session pre-stored in the electronic device (101).

[0238] The above instructions, when individually or collectively executed by the at least one processor (120, 212, 214, 260), may cause the electronic device (101) to identify the occurrence of an event related to the application of a URSP rule.

[0239] The above instructions, when individually or collectively executed by the at least one processor (120, 212, 214, 260), may cause the electronic device (101) to determine whether adjustment of the first PDU session is required based on a comparison result between the URSP rule and information about the first PDU session, based on confirmation of occurrence of the event.

[0240] The above instructions, when individually or collectively executed by the at least one processor (120, 212, 214, 260), may cause the electronic device (101) to perform at least one operation for moderating the first PDU session based on at least a portion of the URSP rule, based on determining that the first PDU session is to be moderated.

[0241] The method of operating an electronic device (101) may include performing at least one operation for establishing a first protocol data unit (PDU) session based on information for establishing a PDU session pre-stored in the electronic device (101).

[0242] The method of operating the electronic device (101) may include an operation of confirming the occurrence of an event related to the application of a URSP rule.

[0243] The operating method of the electronic device (101) may include an operation of determining whether the first PDU session is adjusted based on a comparison result between the URSP rule and information about the first PDU session, based on confirmation of occurrence of the event.

[0244] The method of operating the electronic device (101) may include performing at least one operation for coordination of the first PDU session based on at least a portion of the URSP rule, based on determining that the first PDU session is to be coordinated.

[0245] A storage medium for storing computer-readable instructions may be provided.

[0246] The above instructions, when individually or collectively executed by the at least one processor (120, 212, 214, 260), may cause the electronic device (101) to perform at least one operation for establishing a first protocol data unit (PDU) session based on information for establishing a PDU session pre-stored in the electronic device (101).

[0247] The above instructions, when individually or collectively executed by the at least one processor (120, 212, 214, 260), may cause the electronic device (101) to identify the occurrence of an event related to the application of a URSP rule.

[0248] The above instructions, when individually or collectively executed by the at least one processor (120, 212, 214, 260), may cause the electronic device (101) to determine whether adjustment of the first PDU session is required based on a comparison result between the URSP rule and information about the first PDU session, based on confirmation of occurrence of the event.

[0249] The above instructions, when individually or collectively executed by the at least one processor (120, 212, 214, 260), may cause the electronic device (101) to perform at least one operation for moderating the first PDU session based on at least a portion of the URSP rule, based on determining that the first PDU session is to be moderated.

[0250] An electronic device (101) may include at least one processor (120, 212, 214, 260) and a memory storing instructions. The instructions, when individually or collectively executed by the at least one processor (120, 212, 214, 260), cause the electronic device (101) to: perform at least one operation for establishing a first protocol data unit (PDU) session based on information for establishing a PDU session pre-stored in the electronic device (101); receive a command for changing a URSP rule associated with the PDU session from a network; compare the newly received URSP rule with at least one piece of information about the first PDU session; and maintain the PDU session if the at least one piece of information matches information according to the newly received URSP rule. And if the at least one piece of information does not match the information according to the newly received URSP rule, it causes the first PDU session to be released and a second PDU session to be established based at least in part on the newly received URSP rule. The command to change the URSP rule may be received from a network entity such as a PCF. The at least one piece of information may include a traffic descriptor and / or a route selection descriptor.

[0251] An electronic device (101) may include at least one processor (120, 212, 214, 260) and a memory storing instructions. The instructions, when individually or collectively executed by the at least one processor (120, 212, 214, 260), cause the electronic device (101) to: receive a first URSP rule; perform at least one operation for establishing a first protocol data unit (PDU) session based on information for establishing a PDU session received in the first URSP rule; receive a command for changing the first URSP rule to a second URSP rule; compare the second URSP rule with at least one piece of information about the first PDU session; and maintain the PDU session if the at least one piece of information matches information according to the second URSP rule; And if the at least one piece of information does not match the information according to the second URSP rule, causing the first PDU session to be released and a second PDU session to be established based at least in part on the second URSP rule. The first URSP rule may be received from a network entity such as a PCF. A command to change the first URSP rule to the second URSP rule may be received from a network entity such as a PCF. The at least one piece of information may include a traffic descriptor and / or a route selection descriptor.

[0252] An operating method of an electronic device may include: performing at least one operation for establishing a first protocol data unit (PDU) session based on information for establishing a PDU session pre-stored in the electronic device (101); receiving a command for changing a URSP rule associated with the PDU session from a network; comparing the newly received URSP rule with at least one piece of information about the first PDU session; maintaining the PDU session if the at least one piece of information matches information according to the newly received URSP rule; and releasing the first PDU session and establishing a second PDU session based at least partially on the newly received URSP rule if the at least one piece of information does not match information according to the newly received URSP rule. The command for changing the URSP rule may be received from a network entity such as a PCF. The at least one piece of information may include a traffic descriptor and / or a route selection descriptor.

[0253] A method of operating an electronic device may include: receiving a first URSP rule; performing at least one operation for establishing a first protocol data unit (PDU) session based on information for establishing a PDU session received in the first URSP rule; receiving a command for changing the first URSP rule to a second URSP rule; comparing the second URSP rule with at least one piece of information about the first PDU session; maintaining the PDU session if the at least one piece of information matches information according to the second URSP rule; and releasing the first PDU session and establishing a second PDU session based at least partially on the second URSP rule if the at least one piece of information does not match information according to the second URSP rule. The first URSP rule may be received from a network entity such as a PCF. A command to change the above first URSP rule to the above second URSP rule may be received from a network entity such as a PCF. The at least one piece of information may include a traffic descriptor and / or a route selection descriptor.

[0254] The storage medium may include computer-readable instructions that, when individually or collectively executed by at least one processor, cause the electronic device to: perform at least one operation for establishing a first protocol data unit (PDU) session based on information for establishing a PDU session pre-stored in the electronic device (101); receive a command for changing a URSP rule associated with the PDU session from a network; compare the newly received URSP rule with at least one piece of information about the first PDU session; if the at least one piece of information matches information according to the newly received URSP rule, maintain the PDU session; and if the at least one piece of information does not match information according to the newly received URSP rule, release the first PDU session and establish a second PDU session based at least in part on the newly received URSP rule. The command for changing the URSP rule may be received from a network entity, such as a PCF. The at least one piece of information may include a traffic descriptor and / or a route selection descriptor.

[0255] A storage medium may include computer-readable instructions that, when individually or collectively executed by at least one processor, cause an electronic device to: receive a first URSP rule; perform at least one operation for establishing a first protocol data unit (PDU) session based on information for establishing a PDU session received in the first URSP rule; receive a command for changing the first URSP rule to a second URSP rule; compare the second URSP rule with at least one piece of information about the first PDU session; maintain the PDU session if the at least one piece of information matches information according to the second URSP rule; and release the first PDU session and establish a second PDU session based at least in part on the second URSP rule if the at least one piece of information does not match information according to the second URSP rule. The first URSP rule may be received from a network entity, such as a PCF. A command to change the above first URSP rule to the above second URSP rule may be received from a network entity such as a PCF. The at least one piece of information may include a traffic descriptor and / or a route selection descriptor.

[0256] Electronic devices according to embodiments disclosed herein may take various forms. Electronic devices may include, for example, portable communication devices (e.g., smartphones), computer devices, portable multimedia devices, portable medical devices, cameras, wearable devices, or home appliances. Electronic devices according to embodiments disclosed herein are not limited to the aforementioned devices.

[0257] The embodiments of this document and the terminology used herein are not intended to limit the technical features described in this document to specific embodiments, but should be understood to include various modifications, equivalents, or substitutes of the embodiments. In connection with the description of the drawings, similar reference numerals may be used for similar or related components. The singular form of a noun corresponding to an item may include one or more of the items, unless the context clearly indicates otherwise. In this document, each of the phrases "A or B", "at least one of A and B", "at least one of A or B", "A, B, or C", "at least one of A, B, and C", and "at least one of A, B, or C" can include any one of the items listed together in the corresponding phrase among those phrases, or all possible combinations thereof. Terms such as "first," "second," or "first" or "second" may be used merely to distinguish one component from another, and do not limit the components in any other respect (e.g., importance or order). When a component (e.g., a first component) is referred to as "coupled" or "connected" to another (e.g., a second component), with or without the terms "functionally" or "communicatively," it means that the component can be connected to the other component directly (e.g., wired), wirelessly, or through a third component.

[0258] The term "module" used in one embodiment of this document may include a unit implemented in hardware, software, or firmware, and may be used interchangeably with terms such as logic, logic block, component, or circuit. A module may be an integral component, or a minimum unit or part of such a component that performs one or more functions. For example, according to one embodiment, a module may be implemented in the form of an application-specific integrated circuit (ASIC).

[0259] An embodiment of the present document may be implemented as software (e.g., a program (140)) including one or more instructions stored in a storage medium (e.g., an internal memory (136) or an external memory (138)) readable by a machine (e.g., an electronic device (101)). For example, a processor (e.g., a processor (120)) of the machine (e.g., an electronic device (101)) may call at least one instruction among the one or more instructions stored from the storage medium and execute it. This enables the machine to operate to perform at least one function according to the at least one called instruction. The one or more instructions may include code generated by a compiler or code executable by an interpreter. The machine-readable storage medium may be provided in the form of a non-transitory storage medium. Here, 'non-transitory' simply means that the storage medium is a tangible device and does not contain signals (e.g., electromagnetic waves), and the term does not distinguish between cases where data is stored semi-permanently or temporarily on the storage medium.

[0260] According to one embodiment, the method according to one embodiment disclosed in the present document may be provided as included in a computer program product. The computer program product may be traded as a product between a seller and a buyer. The computer program product may be distributed in the form of a machine-readable storage medium (e.g., compact disc read-only memory (CD-ROM)), or may be distributed online (e.g., downloaded or uploaded) via an application store (e.g., Play Store™) or directly between two user devices (e.g., smart phones). In the case of online distribution, at least a portion of the computer program product may be temporarily stored or temporarily generated in a machine-readable storage medium, such as the memory of a manufacturer's server, an application store's server, or an intermediary server.

[0261] According to one embodiment, each component (e.g., a module or a program) of the above-described components may include one or more entities, and some of the entities may be separated and placed in other components. According to one embodiment, one or more components or operations of the aforementioned components may be omitted, or one or more other components or operations may be added. Alternatively or additionally, a plurality of components (e.g., a module or a program) may be integrated into a single component. In such a case, the integrated component may perform one or more functions of each of the plurality of components identically or similarly to those performed by the corresponding component among the plurality of components prior to the integration. According to one embodiment, the operations performed by a module, program, or other component may be executed sequentially, in parallel, iteratively, or heuristically, or one or more of the operations may be executed in a different order, omitted, or one or more other operations may be added.

[0262] It will be appreciated that all of the embodiments and their technical features described above may be combined with each other in each and every combination, as long as there is no conflict between the two embodiments or features. That is, each and every combination of two or more embodiments described above is contemplated and encompassed by the present disclosure. One or more features of any embodiment may be incorporated into any other embodiment and may provide a corresponding advantage or advantages.

Claims

1. In an electronic device (101), At least one processor (120,212,214,260); and Includes a memory (130) for storing instructions, The above instructions, when individually or collectively executed by the at least one processor (120, 212, 214, 260), cause the electronic device (101) to: At least one operation for establishing a first PDU session is performed based on information for establishing a PDU (protocol data unit) session pre-stored in the electronic device (101), Check the occurrence of events related to the application of URSP (user equipment route selection policy) rules, Based on the confirmation of the occurrence of the above event, based on the comparison result between the URSP rule and the information about the first PDU session, it is confirmed whether the first PDU session is maintained or released, An electronic device (101) that performs at least one operation for releasing the first PDU session based on determining that the first PDU session is to be released, and causes at least one operation for establishing a second PDU session based on at least a part of the URSP rule based on the release of the first PDU session.

2. In paragraph 1, The instructions, when individually or collectively executed by the at least one processor (120, 212, 214, 260), cause the electronic device (101) to determine whether to maintain or release the first PDU session based on a comparison result between the URSP rule and information about the first PDU session, as at least part of the operation. Confirm that the first TD (traffic descriptor) of the above URSP rule corresponds to the first part of the information about the first PDU session, An electronic device (101) that causes a determination as to whether to maintain or release the first PDU session based on whether the second part of the information about the first PDU session corresponds to the first RSD (route selection descriptor) of the URSP rule.

3. In any one of paragraphs 1 and 2, An electronic device (101) wherein the first part of the information about the first PDU session includes information associated with at least one type defined by TD, and / or the second part of the information about the first PDU session includes information associated with at least one type defined by RSD.

4. In any one of paragraphs 1 to 3, The instructions, when individually or collectively executed by the at least one processor (120, 212, 214, 260), cause the electronic device (101) to determine whether to maintain or release the first PDU session based on whether the second part of the information about the first PDU session corresponds to the first RSD of the URSP rule, at least as a part of the operation of: An electronic device (101) that causes the first PDU session to be maintained or released based on whether at least one piece of information included in the second part is identical to at least a part of the first RSD.

5. In any one of paragraphs 1 to 4, The instructions, when individually or collectively executed by the at least one processor (120, 212, 214, 260), cause the electronic device (101) to determine whether to maintain or release the first PDU session based on whether the second part of the information about the first PDU session corresponds to the first RSD of the URSP rule, at least as a part of the operation of: An electronic device (101) that causes the first PDU session to be maintained or released based on whether at least a portion of the information included in the second portion is identical to at least a portion of the first RSD.

6. In any one of paragraphs 1 to 5, The instructions, when individually or collectively executed by the at least one processor (120, 212, 214, 260), cause the electronic device (101) to determine whether to maintain or release the first PDU session based on a comparison result between the URSP rule and information about the first PDU session, as at least part of the operation. Confirm that the first TD of the above URSP rule corresponds to a second part associated with at least one type defined in the RSD among the information for the first PDU session, An electronic device (101) that causes the first PDU session to be maintained or released based on whether the second part corresponds to the first RSD of the URSP rule.

7. In any one of paragraphs 1 to 6, The instructions, when individually or collectively executed by the at least one processor (120, 212, 214, 260), cause the electronic device (101) to perform at least one operation for releasing the first PDU session based on determining that the first PDU session is to be released, and to perform at least one operation for establishing the second PDU session based on at least a part of the URSP rule based on the release of the first PDU session, as at least part of the operation. An electronic device (101) that causes at least one operation for releasing the first PDU session and at least one operation for establishing the second PDU session to be performed based on determining that at least one operation based on the first PDU session is not being performed.

8. In any one of paragraphs 1 to 7, The instructions, when individually or collectively executed by the at least one processor (120, 212, 214, 260), cause the electronic device (101) to perform at least one operation for releasing the first PDU session based on determining that the first PDU session is to be released, and to perform at least one operation for establishing the second PDU session based on at least a part of the URSP rule based on the release of the first PDU session, as at least a part of the operation. Based on the determination that at least one action based on the above first PDU session is being performed: Delaying the performance of at least one operation for releasing the first PDU session and at least one operation for establishing the second PDU session until at least one operation based on the first PDU session is completed; An electronic device (101) that causes at least one operation for releasing the first PDU session and at least one operation for establishing the second PDU session to be performed based on confirmation that at least one operation based on the first PDU session has been completed.

9. In any one of paragraphs 1 to 8, The above instructions, when individually or collectively executed by the at least one processor (120, 212, 214, 260), cause the electronic device (101) to at least partly determine the occurrence of an event related to the application of the URSP rule. An electronic device (101) that causes the registration of the electronic device (101) to a network to which the URSP rule acquired by the electronic device (101) can be applied to be confirmed as the occurrence of the event.

10. In any one of paragraphs 1 to 9, The above instructions, when individually or collectively executed by the at least one processor (120, 212, 214, 260), cause the electronic device (101) to, at least as part of an operation of confirming registration of the electronic device (101) in a network to which the URSP rule acquired by the electronic device (101) is applicable, as an occurrence of the event. According to the mobility of the electronic device (101) from another network to which the URSP rule cannot be applied to a network to which the URSP rule can be applied, at least one operation for registration in the network to which the URSP rule can be applied is performed, An electronic device (101) to which the URSP rule is not applied while the electronic device (101) is registered in the other network.

11. In any one of paragraphs 1 to 10, The above instructions, when individually or collectively executed by the at least one processor (120, 212, 214, 260), cause the electronic device (101) to at least partly determine the occurrence of an event related to the application of the URSP rule. An electronic device (101) that causes the reception of the above URSP rule from the network to be confirmed as the occurrence of the above event.

12. In any one of paragraphs 1 to 11, The above instructions, when individually or collectively executed by the at least one processor (120, 212, 214, 260), cause the electronic device (101) to: Based on detecting the occurrence of an event associated with the deactivation of the URSP rule after establishing the above second PDU session: An electronic device (101) that causes at least one operation for releasing the second PDU session and at least one operation for establishing a PDU session based on information for establishing a PDU session pre-stored in the electronic device (101), based on information associated with at least one type defined by RSD among information for the second PDU session not corresponding to information for establishing a PDU session pre-stored in the electronic device (101).

13. In any one of paragraphs 1 to 12, The above instructions, when individually or collectively executed by the at least one processor (120, 212, 214, 260), cause the electronic device (101) to: An electronic device (101) that causes a command to be received from a network for deletion of said URSP rule to be identified as the occurrence of an event associated with the deactivation of said URSP rule.

14. In the operating method of the electronic device (101), An operation of performing at least one operation for establishing a first PDU session based on information for establishing a PDU (protocol data unit) session pre-stored in the electronic device (101); An action to confirm the occurrence of an event related to the application of a URSP (user equipment route selection policy) rule; An operation of determining whether to maintain or release the first PDU session based on a comparison result between the URSP rule and information about the first PDU session, based on confirmation of the occurrence of the above event; and An operation of performing at least one operation for releasing the first PDU session based on determining that the first PDU session is to be released, and performing at least one operation for establishing a second PDU session based on at least a part of the URSP rule based on the release of the first PDU session. A method of operating an electronic device (101) including:

15. In a storage medium storing computer-readable instructions, when the instructions are individually or collectively executed by at least one processor (120, 212, 214, 260) of an electronic device (101), the electronic device (101) causes: At least one operation for establishing a first PDU session is performed based on information for establishing a PDU (protocol data unit) session pre-stored in the electronic device (101), Check the occurrence of events related to the application of URSP (user equipment route selection policy) rules, Based on the confirmation of the occurrence of the above event, based on the comparison result between the URSP rule and the information about the first PDU session, it is confirmed whether the first PDU session is maintained or released, A storage medium that causes at least one operation to be performed for releasing the first PDU session based on determining that the first PDU session is to be released, and at least one operation to establish a second PDU session based on at least a part of the URSP rule based on the release of the first PDU session.

Images