Electronic device using network slice, and operating method

Abstract

According to one embodiment of the present disclosure, an electronic device (101) comprises: a communication circuit (190); one or more processors (120, 212, 214, 260, 410) including processing circuitry; and a memory (130) for storing instructions, wherein, when executed individually or collectively by the one or more processors, the instructions cause the electronic device to: acquire a first user equipment route selection policy (URSP) rule and a second URSP rule; establish, through the communication circuit, a first protocol data unit (PDU) session with a network (420) on the basis of the first URSP rule used for a PDU session with respect to a network slice common to a plurality of applications; and establish, through the communication circuit, a second PDU session with the network on the basis of the second URSP rule used to establish, on the basis of confirming that a set condition is satisfied, a PDU session with respect to a network slice dedicated to the application. Other embodiments are possible.

Description

Electronic devices and methods of operation using network slices

[0001] Various embodiments of the present disclosure relate to electronic devices and operating methods using network slices.

[0002] 4th generation (4 th To meet the increasing demand for wireless data traffic since the commercialization of 4G communication systems, the improved 5th generation (5 th generation: 5G) communication system or 6th generation (6 th Efforts are being made to develop 5G (6th generation) communication systems. For this reason, 5G communication systems or 6G communication systems are also called beyond 4G network communication systems or post-LTE (long term evolution) systems. To achieve high data rates, 5G communication systems are being implemented and serviced in ultra-high frequency (mmWave) bands (such as the 60 GHz band) and sub-6 GHz bands. In 5G communication, beamforming, massive multi-input multi-output (MIMO), full-dimensional MIMO (FD-MIMO), array antenna, analog beamforming, and large-scale antenna technologies are being discussed to mitigate radio wave path loss and increase radio transmission distance at higher frequencies than existing LTE.

[0003] Among the new architectural features of 5G networks, the most prominent is the introduction of network slicing technology into the radio access network (RAN) and core network (CN) architecture. Network slicing technology provides network resources and network functions through a single, independent network slice, tailored to individual services, thereby enabling isolation, customization, and / or independent management and orchestration of network system functions and resources. When this network slicing technology is used, the network functions of a 5G system can be selected and combined based on service, user, and business model criteria, enabling the provision of independent and flexible 5G services.

[0004] The 3rd Generation Partnership Project (3GPP) technical specification (TS) 24.526 defines user equipment route selection policy (URSP) rules. User equipment (UE) can receive URSP rules from the policy control function (PCF) to establish network slices and data sessions. URSP rules can include traffic descriptors and route selection descriptors.

[0005] A traffic descriptor may include an application descriptor. The application descriptor includes an OSId and an OSAppId, where the OSId indicates a universally unique identifier (UUID) as specified in Internet Engineering Task Force (IETF) request for comment (RFC) 4122, and the OSAppId may indicate an application identifier (App ID) running on an operating system (OS) installed on an electronic device (e.g., UE or smartphone). The application descriptor may be used to provide differentiated network services compared to other applications or services by providing a network slice for a specific application or service.

[0006] A route selection descriptor may include time information (e.g., a time window) and / or location information (e.g., location criteria) within which a protocol data unit (PDU) session can be validly established. For example, a time window may indicate a time window within which matching traffic is permitted. For example, location criteria may indicate the location of a UE within which matching traffic is permitted.

[0007] An operating system (OS) installed in an electronic device can provide a category-based network slice by default. The OS can provide a category-based network slice by setting the value of OSAppId to a specific value (e.g., "PRITORIZE_LATENCY" or "PRORITIZE_BANDWIDTH"). A service provider providing an application can send a URSP rule in which the value of OSAppId is set to a specific value supported by the OS to the electronic device in order to comply with the specifications supported by the OS. In this way, when a URSP rule in which the value of OSAppId is set only to a specific value supported by the OS is used, only a category-based network slice can be provided, so differentiated network services for applications or services can be provided, which can be a limitation in providing services based on network slicing.

[0008] According to one embodiment of the present disclosure, an electronic device (101) may include a communication circuit (190), one or more processors (120; 212; 214; 260; 410) including processing circuitry, and a memory (130) for storing instructions.

[0009] According to one embodiment of the present disclosure, the instructions, when individually or collectively executed by the one or more processors, may cause the electronic device to obtain a first user equipment route selection policy (URSP) rule and a second URSP rule.

[0010] According to one embodiment of the present disclosure, the instructions, when individually or collectively executed by the one or more processors, may cause the electronic device to establish a first protocol data unit (PDU) session with the network (420) based on the first URSP rule used for a network slice common to a plurality of applications via the communication circuitry.

[0011] According to one embodiment of the present disclosure, the instructions, when individually or collectively executed by the one or more processors, may cause the electronic device to establish a second PDU session with the network based on the second URSP rule used to establish a PDU session for a network slice dedicated to the application, through the communication circuitry, based on determining that a set condition is satisfied.

[0012] According to one embodiment of the present disclosure, the method of the electronic device (101) may include an operation of obtaining a first URSP rule and a second URSP rule.

[0013] According to one embodiment of the present disclosure, the method may include establishing a first PDU session with a network (420) based on the first URSP rule used for a PDU session for a network slice common to a plurality of applications.

[0014] According to one embodiment of the present disclosure, the method may include establishing a second PDU session with the network based on the second URSP rule used to establish a PDU session for a network slice dedicated to the application, based on verifying that a setup condition is satisfied.

[0015] According to one embodiment of the present disclosure, a storage medium may be provided that stores at least one computer-readable instruction, wherein the at least one instruction, when executed individually or collectively by one or more processors (120; 212; 214; 260; 410) of an electronic device (101), causes the electronic device (101) to perform at least one operation.

[0016] In one embodiment, the at least one operation comprises obtaining a first URSP rule and a second URSP rule.

[0017] In one embodiment, the at least one operation may include establishing a first PDU session with the network (420) based on the first URSP rule used for a PDU session for a network slice common to multiple applications.

[0018] In one embodiment, the at least one operation may include establishing a second PDU session with the network based on the second URSP rule used to establish a PDU session for a network slice dedicated to the application, based on verifying that a setup condition is satisfied.

[0019] FIG. 1 is a block diagram schematically illustrating an electronic device within a network environment according to one embodiment.

[0020] Figure 2a illustrates a legacy network communication and a fifth generation (5) network communication according to an embodiment. th This is a block diagram showing an electronic device for supporting 5G (5G) network communication.

[0021] FIG. 2b is a block diagram illustrating an electronic device for supporting legacy network communication and 5G network communication according to one embodiment.

[0022] Figure 3a is a diagram illustrating a 5G system structure.

[0023] Figure 3b is a diagram illustrating the structure of a 5G network slice.

[0024] FIG. 4 is a block diagram illustrating an electronic device according to one embodiment.

[0025] FIG. 5 is a signal flow diagram illustrating a general PDU session establishment procedure for comparison with a PDU session establishment procedure according to an embodiment.

[0026] Figure 6 is a diagram for explaining the configuration of a user equipment route selection policy (URSP) rule.

[0027] FIG. 7 is a flowchart illustrating a method of operating an electronic device according to one embodiment.

[0028] FIG. 8 is a signal flow diagram illustrating a PDU session establishment procedure according to one embodiment.

[0029] FIG. 9 is a signal flow diagram illustrating a PDU session establishment procedure according to one embodiment.

[0030] FIG. 10 is a diagram illustrating a UI for requesting consent to establish a second PDU session for an application according to one embodiment.

[0031] FIG. 11 is a signal flow diagram illustrating a PDU session establishment procedure according to one embodiment.

[0032] FIG. 12 is a diagram illustrating a UI pop-up for setting a third condition and / or a fourth condition used to establish a second PDU session according to one embodiment.

[0033] FIG. 13a is a signal flow diagram illustrating a PDU session release procedure according to one embodiment.

[0034] FIG. 13b is a signal flow diagram illustrating a PDU session release procedure according to one embodiment.

[0035] FIG. 14 is a diagram illustrating a UI pop-up for releasing a fifth condition used to establish a second PDU session according to one embodiment.

[0036] FIG. 15 is a signal flow diagram illustrating a PDU session establishment procedure according to one embodiment.

[0037] FIG. 16 is a flowchart schematically illustrating a PDU session selection operation according to one embodiment.

[0038] FIG. 17 is a signal flow diagram illustrating a PDU session establishment procedure according to one embodiment.

[0039] FIG. 18 is a diagram illustrating a UI notification indicating that an application is communicating via a second PDU session according to one embodiment.

[0040] Hereinafter, an embodiment of the present disclosure will be described in detail with reference to the attached drawings. In describing an embodiment of the present disclosure, if a detailed description of a related known function or configuration is determined to unnecessarily obscure the gist of an embodiment of the present disclosure, such detailed description will be omitted. The terms described below are defined in consideration of the functions of an embodiment of the present disclosure, and may vary depending on the intent or custom of the user or operator. Therefore, their definitions should be based on the contents throughout this specification.

[0041] It should be noted that the technical terms used in this specification are merely used to describe specific embodiments and are not intended to limit the embodiments of the present disclosure. Alternatively, unless specifically defined otherwise herein, the technical terms used in this specification should be interpreted as having a meaning generally understood by a person skilled in the art to which the present disclosure pertains, and should not be interpreted in an excessively broad or narrow sense. Alternatively, if a technical term used in this specification is an incorrect technical term that does not accurately express the spirit of the present disclosure, it should be replaced with a technical term that can be correctly understood by a person skilled in the art. Alternatively, general terms used in the embodiments of the present disclosure should be interpreted as defined in the dictionary or according to the context, and should not be interpreted in an excessively narrow sense.

[0042] Alternatively, the singular expressions used herein include plural expressions unless the context clearly dictates otherwise. In this application, terms such as "consisting of" or "comprising" should not be construed to necessarily include all of the various components or various operations described in the specification, and should be construed to mean that some of the components or some of the operations may not be included, or that additional components or operations may be included.

[0043] Alternatively, terms including ordinal numbers, such as "first" and "second," used herein may be used to describe various components, but the components should not be limited by these terms. These terms are used solely to distinguish one component from another. For example, without departing from the scope of the present disclosure, a first component could be referred to as a second component, and similarly, a second component could also be referred to as a first component.

[0044] When a component is referred to as being "connected" or "connected" to another component, it may be directly connected or connected to that other component, but there may also be other components intervening. Conversely, when a component is referred to as being "directly connected" or "connected" to another component, it should be understood that there are no other components intervening.

[0045] Hereinafter, an embodiment of the present disclosure will be described in detail with reference to the attached drawings. Regardless of the drawing numbers, identical or similar components will be given the same reference numbers and redundant descriptions thereof will be omitted. Alternatively, when describing an embodiment of the present disclosure, if a detailed description of a related known technology is determined to obscure the gist of the present disclosure, the detailed description thereof will be omitted. Alternatively, it should be noted that the attached drawings are only intended to facilitate easy understanding of the spirit of the present disclosure and should not be construed as limiting the spirit of the present disclosure by the attached drawings. The spirit of the present disclosure should be construed to extend to all modifications, equivalents, and substitutes other than the attached drawings.

[0046] Hereinafter, an embodiment of the present disclosure will be described using an electronic device as an example, but the electronic device may also be referred to as a terminal, a mobile station, mobile equipment (ME), user equipment (UE), user terminal (UT), subscriber station (SS), wireless device, handheld device, or access terminal (AT). Alternatively, in an embodiment of the present disclosure, the electronic device may be a device having a communication function, such as a mobile phone, a personal digital assistant (PDA), a smart phone, a wireless MODEM, or a laptop.

[0047] FIG. 1 is a block diagram schematically illustrating an electronic device (101) within a network environment (100) according to one embodiment.

[0048] Referring to FIG. 1, in a network environment (100), an electronic device (101) may communicate with an electronic device (102) via a first network (198) (e.g., a short-range wireless communication network), or may communicate with an electronic device (104) or a server (108) via a second network (199) (e.g., a long-range wireless communication network). According to one 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)).

[0049] The processor (120) may control at least one other component (e.g., a hardware or software component) of the electronic device (101) connected to the processor (120) by executing, for example, software (e.g., a program (140)), and may perform various data processing or calculations. According to one embodiment, as at least a part of the data processing or calculation, the processor (120) may store a command or data received from another component (e.g., a sensor module (176) or a communication module (190)) in a volatile memory (132), process the command or data stored in the volatile memory (132), and store the resulting 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 a secondary 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 therewith. For example, if the electronic device (101) includes a main processor (121) and a secondary processor (123), the secondary processor (123) may be configured to use less power than the main processor (121) or to be specialized for a specified function. The secondary processor (123) may be implemented separately from the main processor (121) or as a part thereof.

[0050] The auxiliary processor (123) may control at least a part 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 device) may include a hardware structure specialized for processing an artificial intelligence model. The artificial intelligence model 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.

[0051] 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).

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

[0053] 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).

[0054] 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. According to one embodiment, the receiver can be implemented separately from the speaker or as part of the speaker.

[0055] 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. In 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.

[0056] 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).

[0057] 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.

[0058] 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., electronic device (102)) (tablet and / or smartwatch). 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.

[0059] 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).

[0060] A 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.

[0061] 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.

[0062] 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).

[0063] 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.

[0064] The communication module (190) may also be referred to as a “communication circuit,” and thus, it should be noted that the communication module (190) and the communication circuit (190) may be used interchangeably as needed. 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). Any of these communication modules may communicate with an external electronic device (104) via a first network (198) (e.g., a short-range communication network such as Bluetooth, Wi-Fi (wireless fidelity) direct, or IrDA (infrared data association)) 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 may be integrated into a single component (e.g., a single chip) or implemented as multiple separate components (e.g., multiple chips).The wireless communication module (192) can verify or authenticate an electronic device (101) within a communication network, such as a first network (198) or a second network (199), using subscriber information (e.g., international mobile subscriber identity (IMSI)) stored in the subscriber identification module (196).

[0065] 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.

[0066] The antenna module (197) can transmit or receive signals or power to or from an external device (e.g., an external electronic device). According to 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). According to 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 selected at least one antenna. According to 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).

[0067] 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.

[0068] 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)).

[0069] 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 one 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.

[0070] 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.

[0071] The embodiments of this document and the terms used herein are not intended to limit the technical features described in this document to a specific embodiment, but should be understood to include various modifications, equivalents, or substitutes of the embodiment. 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 item, 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.

[0072] 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).

[0073] 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.

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

[0075] 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.

[0076] Figure 2a illustrates a legacy network communication and a fifth generation (5) network communication according to an embodiment. th This is a block diagram (200) of an electronic device (101) for supporting 5G network communication.

[0077] Referring to FIG. 2A, an electronic device (101) (e.g., the electronic device (101) of FIG. 1) 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 one 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 one embodiment, the fourth RFIC (228) may be omitted or may be included as a part of the third RFIC (226).

[0078] The first communication processor (212) can support the establishment of a communication channel in a band to be used for wireless communication with the first cellular network (292) and legacy network communication through the established communication channel. According to one embodiment, the first cellular network is a second generation (2 nd generation: 2G) network, 3rd generation (3 rdgeneration: 3G) network, 4th generation (4 th The second communication processor (214) may be a legacy network including a 4G (4 generation) network, or a 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 the 3rd generation partnership project (3GPP). Additionally, according to one embodiment, the first communication processor (212) or the second communication processor (214) may establish 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 may support 5G network communication through the established communication channel.

[0079] 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 strength, and resource block (RB) allocation information, with the second communication processor (214).

[0080] According to one embodiment, 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., an application processor). For example, the first communication processor (212) and the second communication processor (214) may transmit and receive data with the processor (120) 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 using a shared memory with the processor (120).

[0081] In one embodiment, the first communication processor (212) and the second communication processor (214) may be implemented in a single chip or a single package. In 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 in FIG. 2B, the integrated communication processor (260) may support both a function for communication with the first cellular network (292) and a function for communication with the second cellular network (294).

[0082] The first RFIC (222) may, upon transmission, convert a baseband signal generated by the first communication processor (212) into a radio frequency (RF) signal of about 700 MHz to about 3 GHz used in the first cellular network (292) (e.g., a legacy network). Upon reception, the RF signal may be acquired from the first cellular network (292) 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 baseband signal so that it may be processed by the first communication processor (212).

[0083] The second RFIC (224) may, upon transmission, convert a baseband 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 a 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) 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 baseband signal so that the preprocessed 5G Sub6 RF signal may be processed by a corresponding communication processor among the first communication processor (212) or the second communication processor (214).

[0084] The third RFIC (226) can convert the baseband signal generated by the second communication processor (214) into an RF signal (hereinafter, 5G Above6 RF signal) of the 5G Above6 band (e.g., about 6 GHz to about 60 GHz) used in the second cellular network (294). Upon reception, the 5G Above6 RF signal can be acquired from the second cellular network (294) via an antenna (e.g., antenna (248)) and preprocessed via the third RFFE (236). The third RFIC (226) can convert the preprocessed 5G Above6 RF signal into a baseband signal so that it 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).

[0085] According to one embodiment, the electronic device (101) may 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 baseband 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) 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 baseband signal so that the second communication processor (214) can process it.

[0086] 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 baseband 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 one embodiment, at least one of the first antenna module (242) or the second antenna module (244) may be omitted or combined with another antenna module to process RF signals of corresponding multiple bands.

[0087] 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., main PCB). In this case, the third RFIC (226) may be disposed on a portion (e.g., bottom surface) of a second substrate (e.g., sub PCB) separate from the first substrate, and the antenna (248) may be disposed on another portion (e.g., 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 communication due to 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).

[0088] According to one 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.

[0089] The second cellular network (294) may operate independently of the first cellular network (292) (e.g., stand-alone (SA)) or may be connected to the first cellular network (292) and operate (e.g., non-stand-alone (NSA)). For example, a 5G network may only have an access network (e.g., a 5G radio access network (RAN) or a next generation RAN (NG RAN)) and may not have a core network (e.g., a next generation core (NGC)). In this case, the electronic device (101) may access an external network (e.g., the Internet) under the control of a core network (e.g., an evolved packet core (EPC)) of a 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)).

[0090] FIG. 2b is a block diagram (250) of an electronic device for supporting legacy network communication and 5G network communication according to one embodiment.

[0091] Referring to FIG. 2B, the electronic device (101) (e.g., the electronic device (101) of FIG. 1A, FIG. 1B, or FIG. 1C) may include an integrated communication processor (260) (e.g., the communication processor (510) of FIG. 1C), a first RFIC (222), a second RFIC (224), a third RFIC (226), a fourth RFIC (228), a first RFFE (232), a second RFFE (234), a first antenna module (242), a second antenna module (244), a third antenna module (246), and / or 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).

[0092] The block diagram (250) of the electronic device (101) illustrated in FIG. 2b is different from the block diagram (200) of the electronic device (101) illustrated in FIG. 2a only in that the first communication processor (212) and the second communication processor (214) are implemented as an integrated communication processor (260), and the remaining components included in the block diagram (250) of the electronic device (101) can be implemented similarly or substantially identically to the components included in the block diagram (200) of the electronic device (101) illustrated in FIG. 2a, and thus a detailed description thereof will be omitted.

[0093] Figure 3a is a diagram illustrating a 5G system structure.

[0094] Figure 3b is a diagram illustrating the structure of a 5G network slice.

[0095] Below, the overall 5G system and network slices will be described with reference to FIGS. 3a and 3b.

[0096] Referring to FIG. 3A, a 5G system may include an electronic device (101) as a network element (e.g., user equipment (UE)), a radio access network ((R)AN) (302), a data network (DN) (345), and multiple network functions (NFs) within a core network (CN).

[0097] The 5G system can define functions, connection points, and protocols for each NF, and the structure of the 5G system can be illustrated using reference points that represent service-based interfaces corresponding to NFs and reference points that represent interactions that exist between NFs.

[0098] The plurality of 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 / or a network slice selection function (NSSF) (304).

[0099] In one embodiment of the present disclosure, the AMF (303), the SMF (341), the PCF (307), and the UPF (342) may perform operations related to establishing a protocol data unit (PDU) (“UE-requested PDU”) session requested by the electronic device (101) (e.g., UE) and managing traffic between the electronic device (101) and the DN (345).

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

[0101] (R)AN (302) may represent a base station using a radio access technology (RAT). For example, (R)AN (302) may be a base station including a 3GPP access technology or a base station including a 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.

[0102] DN (345) can transmit a PDU to be transmitted via downlink to UPF (342), or can receive a PDU transmitted by an electronic device (101) via UPF (342). The reference point between DN (345) and UPF (342) is defined as N6.

[0103] AMF (303) can provide access and mobility management functions independent of access technology, for example, for each electronic device (101). The reference point between AMF (303) and electronic device (101) is defined as N1, the existing 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 existing point between AMF (303) and SMF (341) is defined as N11.

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

[0105] For example, an electronic device (101) may be connected to one AMF (303), whereas for SMF (341), the electronic device (101) may establish multiple sessions, and thus may have different SMFs (e.g., SMF (311), SMF (321), SMF (331)) for each session.

[0106] AF (346) can provide information about packet flow to PCF (307) in charge of policy control to ensure quality of service (QoS).

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

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

[0109] The UDM (306) can store at least a portion of the user's subscription data and / or 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.

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

[0111] When describing an embodiment of the present disclosure, it should be noted that slice, service, network slice, network service, application slice, or application service may be used interchangeably.

[0112] A mobile operator can allocate network resources appropriate for a service on a slice-by-slice basis or on a set of specific slices. Network resources may represent at least one of the NF or logical resources or radio resources provided by the NF.

[0113] Network slicing may be a technology that can apply at least one of network isolation, customization, or independent management and orchestration to the structure of a mobile communication core network by providing network resources and network functions through an independent network slice according to service.

[0114] Network slicing may be a newly proposed concept for 5G core networks. Network slicing is a technology that provides network resources and network functions required for services requested by electronic devices (101) through a single, independent network slice.

[0115] 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.

[0116] A public land mobile network (PLMN) may provide multiple network slices, and each network slice may be provided to an electronic device (101) 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).

[0117] An electronic device (101) can access a network and receive services from at least one of a plurality of slice instances simultaneously or sequentially.

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

[0119] Referring to FIGS. 3A and 3B, the SMF (321) of slice instance 2 (320) can be connected to the PCF (307) at the PLMN level and the PCF (323) at the network slice level. The PCF (307) at the PLMN level can manage policy information at the PLMN level and provide the policy information at the PLMN level to the SMF (321). The PCF (323) at the network slice level included in slice instance 2 can manage policies required to provide network slices and provide the policies required to provide network slices to the SMF (321).

[0120] Each network slice can be distinguished by a slice identifier (ID). For example, the slice ID can be single-network slice selection assistance information (S-NSSAI) defined by 3GPP. According to one embodiment, the electronic device (101) can store information about configured network slice selection assistance information (Configured NSSAI) and network slice selection policy (NSSP).

[0121] The Configured NSSAI may include 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 may include at least one S-NSSAI #id. For example, the list of S-NASSAIs may include S-NASSAI #a, S-NASSAI #b, S-NASSAI #c, or S-NASSAI #d. The Configured NSSAI may be determined based on subscription information of the electronic device (101). The S-NSSAI included in the Configured NSSAI may be unique to the electronic device (101), and the S-NSSAI of another electronic device (e.g., the electronic device (102) or the electronic device (104) of FIG. 1) may be different from the S-NSSAI of the electronic device (101).

[0122] 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) changes, the Configured NSSAI stored in the electronic device (101) may also change. The S-NSSA of the electronic device (101), which is included in the Configured NSSAI, may be stored in the UDM (306) that stores the subscription information of the electronic device (101). The S-NSSAI of the electronic device (101) stored in the UDM (306) may also be referred to as a 'subscribed S-NSSAI'.

[0123] NSSP represents mapping information between S-NSSAI (S-NSSAI #id) subscribed by the electronic device (101) and applications that can be supported by the S-NSSAI subscribed by the electronic device (101). One S-NSSAI #id can be mapped to at least one application. For example, S-NASSAI #a is mapped to application #1 (App #1) and application #2 (App #2), S-NASSAI #b is mapped to App #1, S-NASSAI #c is mapped to application #3 (App #3), and S-NASSAI #c can be mapped to all applications that can be supported. The NSSP can be stored in the PCF (307) that stores policy information related to the electronic device (101) and network. The NSSP is stored in a user data repository (UDR), and the PCF (307) can request the NSSP from the UDR and obtain the NSSP from the UDR as needed.

[0124] When the subscription information of the electronic device (101) changes, the Subscribed S-NSSAI of the electronic device (101) stored in the UDM (306) may change. When the subscription information of the electronic device (101) changes, the NSSP stored in the PCF (307) or UDR may change. When at least one of the Subscribed S-NSSAI or NSSP changes, the related configuration information stored in the electronic device (101) may also need to be updated.

[0125] FIG. 4 is a block diagram illustrating an electronic device according to one embodiment.

[0126] Referring to FIG. 4, an electronic device (101) (e.g., the electronic device (101) of FIG. 1, FIG. 2a, FIG. 2b, FIG. 3a, or FIG. 3b) (e.g., a smartphone or UE) may include a memory (130) (e.g., the memory (130) of FIG. 1), an application processor (400) (e.g., the main processor (121) of FIG. 1, or the processor (120) of FIG. 2a or FIG. 2b), and / or a communication processor (410) (e.g., the auxiliary processor (123) of FIG. 1, the first communication processor (212) or the second communication processor (214) of FIG. 2a, or the integrated communication processor (260) of FIG. 2b).

[0127] According to one embodiment, the application processor (400) may include a connectivity manager (415), a telephony manager (417), a slice manager (419), and / or a routing manager (421). The connectivity manager (415), the telephony manager (417), the slice manager (419), and / or the routing manager (421) may be implemented in software or hardware. At least some of the connectivity manager (415), the telephony manager (417), the slice manager (419), and / or the routing manager (421) may be included in the communication processor (410).

[0128] In one embodiment, the connection manager (415) may provide an application programming interface (API) for a network connection request of an application (e.g., a first application (App1) (411) and / or a second application (App2) (413)). If a network slice of a category corresponding to the network connection request of the application is connected to the electronic device (101), the connection manager (415) may notify the application that the network slice is connected. The connection manager (415) may forward the network connection request of the application to the telephony manager (417). The connection manager (415) may receive a result (e.g., success or failure) of the network slice connection request of the application from the telephony manager (417) and notify the application of the received result.

[0129] In one embodiment, the telephony manager (417) may store information related to a network connection request received from the connection manager (415) and transmit information of an application that requested a network connection (e.g., OSAppID such as com.x.game) to the slice manager (419). The OSAppId may indicate an application identifier (App ID) running in an operating system (OS) installed in the electronic device (101). If a network slice of a category corresponding to the network connection request of the application is not connected to the electronic device (101), the telephony manager (417) may transmit the network connection request of the application to the communication processor (410). If a network slice of the category is connected to the electronic device (101), the telephony manager (417) may not transmit the network connection request of the application to the communication processor (410).

[0130] In one embodiment, when the slice manager (419) receives a network connection request of an application from the telephony manager (417), the slice manager (419) may or may not forward a second PDU session establishment request to the communication processor (410) based on a user equipment route selection policy (URSP) rule and a condition for establishing a second PDU session. The first PDU session may be a PDU session for a category-based network slice and may be a PDU session established between the electronic device (101) and the network (420). In one embodiment, the second PDU session may be additionally established after the first PDU session is established. The second PDU session may be a PDU session for an application-specific network slice, different from the category-based network slice, and may be a PDU session established between the electronic device (101) and the network (420). In one embodiment, when the first PDU session is released, the second PDU session may also be released.

[0131] The slice manager (419) can store URSP rules. The URSP rules are specified in the technical specification (TS) 24.526 of the 3rd generation partnership project (3GPP). The URSP rules can be provided from the network (420) (e.g., the PCF (307) of FIG. 3A or 3B), and a PDU session between the electronic device (101) and the network slice can be established based on the URSP rules. The URSP rules will be described in more detail below with reference to FIG. 6, and thus a detailed description thereof will be omitted herein. In the present disclosure, as an example, a case where at least some of the URSP rules are stored in the slice manager (419), and the remaining some of the URSP rules are stored in the communication processor (410) will be described. Alternatively, the URSP rules can be stored in either the slice manager (419) or the communication processor (410). If the URSP rule is stored in the communication processor (410), the slice manager (419) may perform a separate lookup operation to check whether the URSP rule containing the OSAppId of the application is stored in the communication processor (410).

[0132] The slice manager (419) can determine whether the application will use the first PDU session or the second PDU session according to the set policy, and based on the decision, can update the routing table of the electronic device (101) through the routing manager (421).

[0133] The routing manager (421) can manage the routing table of the electronic device (101).

[0134] FIG. 5 is a signal flow diagram illustrating a general PDU session establishment procedure for comparison with a PDU session establishment procedure according to an embodiment.

[0135] Referring to FIG. 5, a communication processor (410) (e.g., the auxiliary processor (123) of FIG. 1, the first communication processor (212) or the second communication processor (214) of FIG. 2A, the integrated communication processor (260) of FIG. 2B, or the communication processor (410) of FIG. 4) may receive URSP rules for a first application (App1) (411) (e.g., the first application (411) of FIG. 4) from a network (420) (e.g., the network (420) of FIG. 4) in operation 511 (URSP Rule Provisioning). The URSP rules for the first application (411) may be as shown in Table A below.

[0136] Table A

[0137]

[0138] In Table A, the URSP Rule may be a URSP rule used to establish a PDU session for a network slice common to multiple applications including the first application (411).

[0139] As shown in Table A, PRIORITIZE_LATENCY may be the type of network slice to which the first application (411) wishes to connect. PRIORITIZE_LATENCY may indicate a network slice type for an application category that is relatively sensitive to latency. A network slice corresponding to the PRIORITIZE_LATENCY category may be a common network slice that can be used by multiple applications. The remaining information shown in Table A will be described below with reference to FIG. 6, and therefore, a detailed description thereof will be omitted here.

[0140] Thereafter, the first application (411) may transmit a message (hereinafter referred to as a “requestNetwork message”) requesting a network slice connection to the connection manager (415) (e.g., the connection manager (415) of FIG. 4) in operation 513. The requestNetwork message may include a SliceType indicating a network slice to which a connection is desired. In the requestNetwork message transmitted in operation 513, the SliceType may be set to PRIORITIZE_LATENCY. In one embodiment, the SliceType may be set to PRIORITIZE_LATENCY in accordance with the URSP rule for the first application (411) received in operation 511.

[0141] The connection manager (415) that receives the requestNetwork message from the first application (411) can transmit the requestNetwork message to the telephony manager (417) (e.g., the telephony manager (417) of FIG. 4) in operation 515.

[0142] The telephony manager (417), which has received the requestNetwork message from the connection manager (415), may transmit a data call setup request (hereinafter referred to as “SETUP_DATA_CALL_REQ”) message requesting the communication processor (210) to set up a data call in accordance with the inter-process communication (IPC) format agreed upon between the telephony manager (417) and the communication processor (410) in operation 517. The telephony manager (417) may set the SliceType included in the requestNetwork message received from the connection manager (415) to the OSAppId included in the SETUP_DATA_CALL_REQ message.

[0143] The communication processor (410) that receives the SETUP_DATA_CALL_REQ message from the telephony manager (417) can transmit a PDU Session Establishment Request message requesting the network (420) to establish a PDU session based on the URSP rule stored in operation 519.

[0144] In response to the PDU Session Establishment Request message, the communication processor (410) may receive a PDU Session Establishment Accept message from the network (420) indicating that the request for PDU session establishment is accepted at operation 521.

[0145] The communication processor (410) that receives the PDU Session Establishment Accept message can confirm that a PDU session for the first application (411) is established, and can transmit a data call setup response (hereinafter referred to as “SETUP_DATA_CALL_RESP”) message indicating that a request for data call setup has been successfully performed to the telephony manager (417) in operation 523. The PDU session may be a PDU session common to a plurality of applications including the first application (411), and may be a PDU session established between a network slice corresponding to a category supported by the OS and the electronic device (101).

[0146] The telephony manager (417), which has received the SETUP_DATA_CALL_RESP message from the communication processor (410), may transmit a message (hereinafter referred to as an “onNetworkConnected message”) indicating that a network slice is connected to the connection manager (415) in operation 525. The onNetworkConnected message transmitted in operation 525 may include information indicating that a request for network connection has been successfully performed.

[0147] The connection manager (415), which has received the onNetworkConnected message from the telephony manager (417), can transmit the onNetworkConnected message to the first application (411) in operation 527. The onNetworkConnected message transmitted in operation 527 can include information indicating that the request for network connection has been successfully performed. The first application (411), which has received the onNetworkConnected message from the connection manager (415), can confirm that a PDU session for the first application (411) has been established. In one embodiment, after the PDU session is established, the first application (411) can transmit and receive data through the PDU session.

[0148] When a PDU session is established as described in FIG. 5, the established PDU session may be a PDU session common to multiple applications including the first application (411), and may be a PDU session established between a network slice corresponding to a category supported by the OS and the electronic device (101), and therefore, a dedicated PDU session suitable for the first application (411) may not be established. Accordingly, it may be difficult (or impossible) to provide differentiated network services for the first application (411).

[0149] Figure 6 is a diagram for explaining the configuration of the URSP rule.

[0150] Referring to FIG. 6, an electronic device (101) (e.g., the electronic device (101) of FIG. 1, FIG. 2a, FIG. 2b, FIG. 3a, FIG. 3b, or FIG. 4) (e.g., a smartphone or UE) can obtain at least one URSP rule (600) from a network (e.g., the network (420) of FIG. 4).

[0151] In FIG. 6, a URSP rule (600) may include a rule precedence (601), a traffic descriptor (610), and a route selection descriptor list (620). The traffic descriptor (610) may include an application descriptor (e.g., an application identifier (AppID) (611), an internet protocol (IP) descriptor, or a non-IP descriptor (612), a fully qualified domain name (FQDN)(613), a DNN (614), and connection capabilities (615). The AppID is an ID for distinguishing the App in the OS and the operator, and may be set based on the OS information and / or the package information of the application, but may not be limited. The route selection descriptor list (620) may include a plurality of route selection descriptors (621, 622, 623, 624). For example, one route selection descriptor (622) may include a Precedence (622a) of "Priority", "SCC mode", "NS selection", and DNN. It may include validation criteria (622c) of components (622b), time window and location criteria.

[0152] The URSP rules (600) are specified in 3GPP TS 24.503 as shown in Table 1 below.

[0153] Table 1

[0154]

[0155] The route selection descriptor is specified in 3GPP TS 24.503 as shown in Table 2 below.

[0156] Table 2

[0157]

[0158] According to one embodiment of the present disclosure, an electronic device (101) may include a communication circuit (190), one or more processors (120; 212; 214; 260; 410) including processing circuitry; and a memory (130) for storing instructions.

[0159] According to one embodiment of the present disclosure, the instructions, when individually or collectively executed by the one or more processors, may cause the electronic device to acquire a first URSP rule and a second URSP rule.

[0160] According to one embodiment of the present disclosure, the instructions, when individually or collectively executed by the one or more processors, may cause the electronic device to establish a first PDU session with the network (420) through the communication circuitry based on the first URSP rule used for the PDU session for a network slice common to a plurality of applications.

[0161] According to one embodiment of the present disclosure, the instructions, when individually or collectively executed by the one or more processors, may cause the electronic device to establish a second PDU session with the network based on the second URSP rule used to establish a PDU session for a network slice dedicated to an application, through the communication circuitry, based on determining that a set condition is satisfied.

[0162] According to one embodiment of the present disclosure, the set condition may be identified as being satisfied when a first condition is satisfied that the first PDU session is established, a second condition is satisfied that the first PDU session is established and a user input indicating consent to establish the second PDU session is confirmed, and a third condition is satisfied that the first PDU session is established and a time corresponding to the set time information at which the second PDU session is established exists.

[0163] According to one embodiment of the present disclosure, the set condition may be identified as being satisfied when a first condition is satisfied that the first PDU session is established, a second condition is satisfied that the first PDU session is established and a user input indicating consent to establishing the second PDU session is confirmed, and a fourth condition is satisfied that the location of the electronic device at the time the first PDU session is established and the second PDU session is established is at a location corresponding to the set location information.

[0164] According to one embodiment of the present disclosure, the set time information may include at least one of time information corresponding to a time window included in a route selection descriptor included in the second URSP rule, or time information based on a user setting.

[0165] According to one embodiment of the present disclosure, the set location information may include at least one of location information included in a route selection descriptor included in the second USRP rule, or location information based on a user setting.

[0166] According to one embodiment of the present disclosure, the instructions, when individually or collectively executed by the one or more processors, may cause the electronic device to transmit and receive data of the application through the communication circuitry through the second PDU session after the second PDU session is established.

[0167] According to one embodiment of the present disclosure, the instructions, when individually or collectively executed by the one or more processors, may cause the electronic device to determine whether a traffic status of the second PDU session satisfies a set criterion while transmitting and receiving data of the application through the second PDU session.

[0168] According to one embodiment of the present disclosure, the instructions, when individually or collectively executed by the one or more processors, may cause the electronic device to transmit and receive data of the application through the communication circuitry through the first PDU session based on determining that a traffic status of the second PDU session does not satisfy a set criterion.

[0169] According to one embodiment of the present disclosure, the setting criteria may include a criterion that a TCP packet loss rate of the second PDU session exceeds a first threshold, or a criterion that a domain name server DNS query / response error rate of the second PDU session exceeds a second threshold.

[0170] According to one embodiment of the present disclosure, the instructions, when individually or collectively executed by the one or more processors, may cause the electronic device to release the second PDU session with the network through the communication circuitry based on determining that another set condition is satisfied.

[0171] According to one embodiment of the present disclosure, the other set condition may include at least one of a condition in which the first PDU session is released, a condition in which a user input indicating rejection of establishing the second PDU session is confirmed, a condition in which the time point in time when the second PDU session is established does not exist within a time corresponding to the set time information, a condition in which the location of the electronic device at the time point in time when the second PDU session is established does not exist at a location corresponding to the set location information, or a condition in which the setting of at least one of the third condition or the fourth condition is released.

[0172] According to one embodiment of the present disclosure, the set time information may include at least one of time information corresponding to a time window included in a route selection descriptor included in the second URSP rule, or time information based on a user setting, or the set location information may include at least one of location information included in a route selection descriptor included in the second USRP rule, or location information based on a user setting.

[0173] FIG. 7 is a flowchart illustrating a method of operating an electronic device according to one embodiment.

[0174] Referring to FIG. 7, an electronic device (e.g., an electronic device (101) of FIG. 1, FIG. 2A, FIG. 2B, FIG. 3A, FIG. 3B, or FIG. 4) (e.g., a smartphone or UE) (e.g., one or more processors including processing circuitry) (e.g., a processor (120) of FIG. 1, FIG. 2A, or FIG. 2B, a first communication processor (212) or a second communication processor (214) of FIG. 2A, or an integrated communication processor (260) of FIG. 2B, or a communication processor (410) of FIG. 4) may acquire a first URSP rule and a second URSP rule for an application (e.g., a first application (411) or a second application (413) of FIG. 4) in operation 711. In one embodiment, the electronic device may obtain the first URSP rule and the second URSP rule by receiving the first URSP rule and the second URSP rule from a network (e.g., the network (420) of FIG. 4) via a communication circuit (e.g., the communication module (190) of FIG. 1). In one embodiment, the electronic device may obtain the first URSP rule and the second URSP rule that are preset in the electronic device (e.g., preset based on a UE Local Configuration that may be implemented in the form of a code and / or a table).

[0175] In one embodiment, the first URSP rule may be a URSP rule used to establish a PDU session for a network slice common to multiple applications including the application. In one embodiment, the second URSP rule may be a rule used to establish a PDU session for a network slice dedicated to the application.

[0176] An electronic device that has acquired the first URSP rule and the second URSP rule for an application may establish a first PDU session with a network based on the first URSP rule through a communication circuit in operation 713. In one embodiment, the first PDU session may be a PDU session for a category-based network slice, and may be a PDU session established between the electronic device and the network.

[0177] An electronic device that has established a first PDU session with a network may, at step 715, establish a second PDU session with the network based on a second URSP rule through a communication circuit, based on confirmation that a set condition is satisfied. In one embodiment, the second PDU session may be a PDU session established between the electronic device and the network for an application-specific network slice, different from a category-based network slice. In one embodiment, the second PDU session may be additionally established after the first PDU session is established. In one embodiment, if the first PDU session is not established, establishment of the second PDU session may not be attempted. In one embodiment, if the first PDU session is released, the second PDU session may also be released. In one embodiment, the setup condition may include at least one of a first condition that a first PDU session is established, a second condition that the first PDU session is established and a user input indicating consent to establishing a second PDU session is confirmed, a third condition that the first PDU session is established and a time corresponding to the set time information exists at a time corresponding to the set time information, or a fourth condition that the first PDU session is established and a location of the electronic device at the time the second PDU session is established exists at a location corresponding to the set location information.

[0178] FIG. 8 is a signal flow diagram illustrating a PDU session establishment procedure according to one embodiment.

[0179] Referring to FIG. 8, a communication processor (410) (e.g., the auxiliary processor (123) of FIG. 1, the first communication processor (212) or the second communication processor (214) of FIG. 2A, the integrated communication processor (260) of FIG. 2B, or the communication processor (410) of FIG. 4) may receive URSP rules for a first application (App1) (411) (e.g., the first application (411) of FIG. 4) from a network (420) (e.g., the network (420) of FIG. 4) in operation 811 (URSP Rule Provisioning). The URSP rules for the first application (411) may be as shown in Table 3 below.

[0180] Table 3

[0181]

[0182] In Table 3, URSP Rule #1 may be a first URSP rule used to establish a PDU session (e.g., a first PDU session) for a network slice common to multiple applications including the first application (411). In Table 3, URSP Rule #2 may be a URSP rule used to establish a PDU session (e.g., a second PDU session) for a network slice dedicated to the first application (411).

[0183] As shown in Table 3, com.x.game may be the OSAppId of the first application (411), and PRIORITIZE_LATENCY may be the type of network slice that the first application (411) wants to connect to. In Table 3, URSP Rule #1 may be a URSP Rule for connecting a network slice corresponding to the PRIORITIZE_LATENCY category, and URSP Rule #2 may be a URSP rule for connecting a network slice dedicated to the first application (411). PRIORITIZE_LATENCY may indicate a network slice type for an application category that is relatively sensitive to latency. The network slice corresponding to the PRIORITIZE_LATENCY category may be a public network slice that can be used by multiple applications. The remaining information shown in Table 3 may be implemented similarly or substantially identically to that described in FIG. 6.

[0184] Thereafter, the first application (411) may transmit a message requesting a network slice connection (hereinafter referred to as a “requestNetwork message”) to the connection manager (415) (e.g., the connection manager (415) of FIG. 4) in operation 813. The requestNetwork message may include a SliceType indicating a network slice to be connected to and a RequestingApp indicating information indicating an application requesting the network slice connection. In the requestNetwork message transmitted in operation 813, the SliceType may be set to PRIORITIZE_LATENCY, and the RequestingApp may be set to com.x.game, which is the OSAppId of the first application (411).

[0185] The connection manager (415) that received the requestNetwork message from the first application (411) can transmit the requestNetwork message to the telephony manager (417) (e.g., the telephony manager (417) of FIG. 4) in operation 815.

[0186] The telephony manager (417), which has received the requestNetwork message from the connection manager (415), may transmit a data call setup request (hereinafter referred to as “SETUP_DATA_CALL_REQ”) message requesting the communication processor (410) to set up a data call in accordance with the inter-process communication (IPC) format agreed upon between the telephony manager (417) and the communication processor (410) in operation 817. The telephony manager (417) may set the SliceType included in the requestNetwork message received from the connection manager (415) to the OSAppId included in the SETUP_DATA_CALL_REQ message.

[0187] The communication processor (410) that receives the SETUP_DATA_CALL_REQ message from the telephony manager (417) may transmit a PDU Session Establishment Request message requesting the network (420) to establish a PDU session based on the URSP rule stored in operation 819. In the PDU Session Establishment Request message transmitted in operation 819, the DNN may be set to eMBBPremium as shown in Table 3 (DNN = eMBBPremium).

[0188] In response to the PDU Session Establishment Request message, the communication processor (410) may receive a PDU Session Establishment Accept message from the network (420) indicating that the request for PDU session establishment is accepted at operation 821.

[0189] The communication processor (410) that receives the PDU Session Establishment Accept message can confirm that the first PDU session for the first application (411) is established, and can transmit a data call setup response (hereinafter referred to as “SETUP_DATA_CALL_RESP”) message indicating that the request for data call setup has been successfully performed to the telephony manager (417) in operation 823. The first PDU session is a PDU session for a category-based network slice, and may be a PDU session established between the electronic device (101) and the network (420).

[0190] The telephony manager (417), which has received the SETUP_DATA_CALL_RESP message from the communication processor (410), may transmit a message (hereinafter referred to as an “onNetworkConnected message”) indicating that a network slice is connected to the connection manager (415) in operation 825. The onNetworkConnected message transmitted in operation 825 may include information indicating that a request for network connection has been successfully performed.

[0191] The connection manager (415), which has received the onNetworkConnected message from the telephony manager (417), may transmit the onNetworkConnected message to the first application (411) in operation 827. The onNetworkConnected message transmitted in operation 827 may include information indicating that the request for network connection has been successfully performed. The first application (411), which has received the onNetworkConnected message from the connection manager (415), may confirm that the first PDU session for the first application (411) has been established. In one embodiment, the first application (411) may transmit and receive data through the first PDU session until the second PDU session is established after the first PDU session is established.

[0192] The telephony manager (417), which has confirmed that the first PDU session for the first application (411) is established, may transmit a message requesting an additional network slice connection (hereinafter referred to as a "requestAdditionalNetwork message") to the slice manager (419) in operation 829. The requestAdditionalNetwork message may include RequestingApp, which is information indicating the application requesting the network slice connection. In the requestAdditionalNetwork message, RequestingApp may be set to "com.x.game", which is the OSAppId of the first application (411).

[0193] The slice manager (419), which receives the requestAdditionalNetwork message from the telephony manager (417), may determine whether to establish a second PDU session for the first application (411) based on the URSP rules and the conditions for establishing the second PDU session. In one embodiment, the conditions for establishing the second PDU session may include at least one of the following first condition, second condition, third condition, or fourth condition.

[0194] (1) Condition 1

[0195] The first condition may include a condition under which the first PDU session is established.

[0196] (2) Second condition

[0197] A first PDU session may be established, and a condition may be included that confirms user input indicating consent to establish a second PDU session.

[0198] (3) Third condition

[0199] The third condition may include a condition that the time at which the first PDU session is established and the time at which the second PDU session is established exist within a time corresponding to the time information.

[0200] In one embodiment, the time information may include a time window included in a route selection descriptor included in a URSP rule. For example, the time window may indicate a time window within which matching traffic is permitted.

[0201] In one embodiment, the time information may include time information set by a user, a service provider, or an application developer.

[0202] For example, the slice manager (419) may decide to establish the second PDU session if the time at which the second PDU session is to be established is within a time corresponding to the time information (e.g., 7:00 PM to 8:00 PM). For example, if there is an event such as a concert and / or a sporting event during a specific time, and the first application (411) is an application related to the event, the slice manager (419) may establish the second PDU session if the time at which the second PDU session is to be established is within the time during which the event is in progress.

[0203] (4) Condition 4

[0204] The fourth condition may include a condition that the location of the electronic device at the time when the first PDU session is established and the second PDU session is established exists at a location corresponding to the location information.

[0205] In one embodiment, the location information may include location criteria included in a route selection descriptor included in the URSP. For example, the location criteria may indicate the location of an electronic device for which matching traffic is permitted.

[0206] In one embodiment, the location information may include location information set by a user, a service provider, or an application developer.

[0207] For example, the slice manager (419) may decide to establish the second PDU session if the location of the electronic device at the time of establishing the second PDU session corresponds to a location (e.g., a stadium) corresponding to the location information. For example, if there is an event such as a concert and / or a sports game at a specific location and the first application (411) is an application related to the event, the slice manager (419) may establish the second PDU session if the location of the electronic device at the time of establishing the second PDU session corresponds to the location where the event is taking place.

[0208] According to one embodiment, a separate UI popup may be implemented to set the third condition and / or the fourth condition, which will be described below with reference to FIG. 12, and thus a detailed description thereof will be omitted here.

[0209] In Fig. 8, a case in which the slice manager (419) decides to establish a second PDU session for the first application (411) based on the first condition will be described as an example. The case in which the slice manager (419) decides to establish a second PDU session for the first application (411) based on the second condition will be described below with reference to Fig. 9, and therefore a detailed description thereof will be omitted here.

[0210] The slice manager (419), which has decided to establish a second PDU session for the first application (411), may transmit a SETUP_DATA_CALL_REQ message requesting the communication processor (410) to set up a data call in operation 831. In the SETUP_DATA_CALL_REQ message transmitted in operation 831, the OSId may be set to "97a498e3-fc92-5c94-8986-033d06e4e47", which is the OSId of the OS running on the electronic device (101), and the OsAppId may be set to "com.x.game", which is the OSAppId of the first application (411).

[0211] The communication processor (410) that receives the SETUP_DATA_CALL_REQ message from the slice manager (419) may transmit a PDU Session Establishment Request message requesting to establish a PDU session to the network (420) based on the URSP rule stored in operation 833. In the PDU Session Establishment Request message transmitted in operation 833, the DNN may be set to eMBBPremiumGame as shown in Table 3 (DNN = eMBBPremiumGame).

[0212] In response to the PDU Session Establishment Request message, the communication processor (410) may receive a PDU Session Establishment Accept message from the network (420) indicating that the request for PDU session establishment is accepted at operation 835.

[0213] The communication processor (410) that receives the PDU Session Establishment Accept message can confirm that a second PDU session for the first application (411) is established, and can transmit a SETUP_DATA_CALL_RESP message indicating that a request for data call setup has been successfully performed to the slice manager (419) in operation 837. The first PDU session is a PDU session for a category-based network slice, and may be a PDU session established between the network (420) and the electronic device (101). The second PDU session is a PDU session for a network slice exclusive to an application, different from the category-based network slice, and may be a PDU session established between the electronic device (101) and the network (420). In one embodiment, the second PDU session may be additionally established after the first PDU session is established. In one embodiment, if the first PDU session is not established, establishment of the second PDU session may not be attempted. In one embodiment, when the first PDU session is released, the second PDU session may also be released.

[0214] In this way, when two PDU sessions (e.g., a first PDU session and a second PDU session) are established for a first application (411), the slice manager (419) can determine whether the first application (411) will use the first PDU session or the second PDU session based on the established policy, and can update the routing table of the electronic device through the routing manager (e.g., the routing manager (421) of FIG. 4) based on the determination. The policy used to determine which of the two PDU sessions for one application to use will be described in detail below, and therefore, a detailed description thereof will be omitted here.

[0215] FIG. 9 is a signal flow diagram illustrating a PDU session establishment procedure according to one embodiment.

[0216] Referring to FIG. 9, operations 911 to 929 can be implemented similarly or substantially identically to operations 811 to 829 of FIG. 8, and therefore, a detailed description thereof is omitted here.

[0217] In operation 929, the slice manager (419) (e.g., the slice manager (419) of FIG. 4 or FIG. 8), which has received a requestAdditionalNetwork message from the telephony manager (417) (e.g., the telephony manager (417) of FIG. 4 or FIG. 8), may determine whether to establish a second PDU session for the first application (App1) (411) (e.g., the first application (411) of FIG. 4 or FIG. 8) based on the URSP rule and the condition for establishing the second PDU session. In one embodiment, the condition for establishing the second PDU session may include at least one of the first condition, the second condition, the third condition, or the fourth condition, and the first condition, the second condition, the third condition, and the fourth condition may be implemented similarly or substantially identically to the first condition, the second condition, the third condition, and the fourth condition described in FIG. 8, and thus, a detailed description thereof will be omitted herein. In FIG. 9, a case in which the slice manager (419) decides to establish a second PDU session for the first application (411) based on the second condition will be described as an example. The case in which the slice manager (419) decides to establish a second PDU session for the first application (411) based on the first condition has been described above with reference to FIG. 8, and therefore a detailed description thereof will be omitted here.

[0218] Since the slice manager (419) determines whether to establish a second PDU session based on the second condition, a message may be output on the display (e.g., the display module (160) of FIG. 1) in operation 931 to inquire whether the user agrees to establish a second PDU session for the first application (411). For example, the message inquiring whether the user agrees to establish a second PDU session may be implemented as a separate UI pop-up, and a detailed description thereof will be omitted here since the UI pop-up inquiring whether the user agrees to establish a second PDU session will be described below with reference to FIG. 10.

[0219] The slice manager (419), which outputs a message asking whether the user agrees to establish a second PDU session for the first application (411) on the display, can confirm a user input indicating agreement to establish the second PDU session in operation 933. FIG. 9 illustrates an example where a user input indicating agreement to establish the second PDU session is confirmed, but if a user input indicating rejection of establishing the second PDU session is confirmed, no further operations may be performed, and thus, the second PDU session for the first application (411) may not be established.

[0220] The slice manager (419), having confirmed the user input indicating consent to establish a second PDU session, may transmit a SETUP_DATA_CALL_REQ message to the communication processor (410) requesting to set up a data call in operation 935. Operations 935 to 941 may be implemented similarly or substantially identically to operations 831 to 837 of FIG. 8, and thus, a detailed description thereof will be omitted herein.

[0221] FIG. 10 is a diagram illustrating a UI for requesting consent to establish a second PDU session for an application according to one embodiment.

[0222] Referring to FIG. 10, a slice manager (e.g., a slice manager (419) of FIG. 4, FIG. 8, or FIG. 9) that determines whether to establish a second PDU session for an application (e.g., the first application of FIG. 4, FIG. 8, or FIG. 9) based on a second condition as described in FIG. 9 may output a message on a display (e.g., a display module (160) of FIG. 1) requesting consent to establish a second PDU session for the application. In this case, the message requesting consent to establish a second PDU session for the application may be provided in the form of a UI pop-up, and may be provided as a screen (1000) as illustrated in FIG. 10. As an example, the message requesting consent to establish a second PDU session may be expressed as "App (com.x.game) requests a dedicated network slice connection. Do you want to allow the connection?"

[0223] For example, when a “yes” icon (1010) on the screen (1000) is input, the slice manager can confirm user input indicating consent to establish a second PDU session, and thus perform an action (e.g., action 935 of FIG. 9) to establish a second PDU session for the application.

[0224] For example, if a “No” icon (1020) on the screen (1000) is entered, the slice manager can confirm user input indicating a refusal to establish a second PDU session and thus not establish a second PDU session for the application.

[0225] FIG. 11 is a signal flow diagram illustrating a PDU session establishment procedure according to one embodiment.

[0226] Referring to FIG. 11, operations 1111 to 1123 can be implemented similarly or substantially identically to operations 811 to 823 of FIG. 8, and therefore, a detailed description thereof is omitted here.

[0227] The telephony manager (417) (e.g., the telephony manager (417) of FIG. 4, FIG. 8, or FIG. 9) that has received a SETUP_DATA_CALL_RESP message from the communication processor (410) (e.g., the auxiliary processor (123) of FIG. 1, the first communication processor (212) or the second communication processor (214) of FIG. 2A, the integrated communication processor (260) of FIG. 2B, or the communication processor (410) of FIG. 4, FIG. 8, or FIG. 9) may transmit a requestAdditionalNetwork message to the slice manager (419) (e.g., the slice manager (419) of FIG. 4, FIG. 8, or FIG. 9) in operation 1125. The requestAdditionalNetwork message may include RequestingApp, which is information indicating an application requesting a network slice connection. In the requestAdditionalNetwork message, RequestingApp may be set to "com.x.game", which is the OSAppId of the first application (411) (e.g., the first application (411) of FIG. 4, FIG. 8, or FIG. 9).

[0228] Actions 1127 to 1133 can be implemented similarly or substantially identically to actions 831 to 837 of FIG. 8, and therefore, their detailed descriptions are omitted here.

[0229] At operation 1133, the slice manager (419) (e.g., the slice manager (419) of FIG. 4, FIG. 8, or FIG. 9) that has received the SETUP_DATA_CALL_RESP message from the communication processor (410) may transmit a message indicating that an additional network slice is connected to the telephony manager (417) at operation 1135 (hereinafter referred to as an “onAdditionalNetworkConnected message”).

[0230] The telephony manager (417), which has received the onAdditionalNetworkConnected message from the slice manager (419), may transmit onNetworkConnected, indicating that the network slice is connected, to the connection manager (415) in operation 1137. The onNetworkConnected message transmitted in operation 1137 may include information indicating that the request for network connection was successfully performed.

[0231] The connection manager (415), which has received the onNetworkConnected message from the telephony manager (417), may transmit the onNetworkConnected message to the first application (411) in operation 1139. The onNetworkConnected message transmitted in operation 1139 may include information indicating that the request for network connection has been successfully performed. The first application (411), which has received the onNetworkConnected message from the connection manager (415), may confirm that the first PDU session and the second PDU session for the first application (411) have been established. In one embodiment, the first application (411) may transmit and receive data through the second PDU session dedicated to the first application (411) without using the first PDU session.

[0232] As described in FIG. 11, when a first PDU session and a second PDU session are established for a first application (411), the first application (411) can transmit and receive data through a second PDU session, which is a PDU session for an application-specific network slice different from a category-based network slice, without using the first PDU session, which is a PDU session for a category-based network slice.

[0233] FIG. 12 is a diagram illustrating a UI pop-up for setting a third condition and / or a fourth condition used to establish a second PDU session according to one embodiment.

[0234] Referring to FIG. 12, the conditions for establishing a second PDU session may include at least one of the first condition, the second condition, the third condition, or the fourth condition. The first condition, the second condition, the third condition, and the fourth condition may be implemented similarly or substantially identically to those described in FIG. 8, and thus, a detailed description thereof will be omitted herein.

[0235] The UI pop-up provided to set the third condition, which is a condition that the time when the second PDU session is established exists within a time corresponding to the time information, and / or the fourth condition, which is a condition that the location of the electronic device at the time when the second PDU session is established exists at a location corresponding to the location information, may be implemented as shown in screen (1200). Screen (1200) may be a screen for setting the third condition and / or the fourth condition for at least one of a plurality of applications, and in FIG. 12, it is assumed that an icon (1201) corresponding to the first application App1 is selected, in which case a screen (1210) for setting the third condition and / or the fourth condition for the first application may be output. Screen (1210) may be a screen for setting the third condition and the fourth condition for the first application. In screen (1210), the time information corresponding to the third condition may be set to "7:00 PM to 8:00 PM," and the location information corresponding to the fourth condition may be set to "sports complex."

[0236] Although not illustrated separately in FIG. 12, the UI pop-up for setting the third condition and / or the fourth condition used to establish the second PDU session illustrated in FIG. 12 may be a UI pop-up for setting the third condition and / or the fourth condition used to establish the second PDU session after the user consents to establishing the second PDU session by providing a message in the form of a UI pop-up for asking for consent to establish the second PDU session as described in FIG. 10.

[0237] FIG. 13a is a signal flow diagram illustrating a PDU session release procedure according to one embodiment.

[0238] Referring to FIG. 13A, a communication processor (410) (e.g., the auxiliary processor (123) of FIG. 1, the first communication processor (212) or the second communication processor (214) of FIG. 2A, the integrated communication processor (260) of FIG. 2B, or the communication processor (410) of FIG. 4, FIG. 8, FIG. 9, or FIG. 11) may receive a URSP rule for a first application (411) (e.g., the first application (411) of FIG. 4, FIG. 8, FIG. 9, or FIG. 11) from a network (420) (e.g., the network (420) of FIG. 4, FIG. 8, FIG. 9, or FIG. 11) in operation 1311 (URSP Rule Provisioning). The URSP rule for the first application (411) may be implemented similar to or substantially identical to Table 3, and thus, a detailed description thereof will be omitted herein.

[0239] Thereafter, the first application (411) may transmit a message (hereinafter referred to as a “releaseNetwork message”) requesting the release of a network slice connection to the connection manager (415) (e.g., the connection manager (415) of FIG. 4, FIG. 8, FIG. 9, or FIG. 11) in operation 1313. The releaseNetwork message may include a SliceType indicating a network slice to be released and a RequestingApp indicating information indicating an application requesting the release of the network slice connection. In the releaseNetwork message transmitted in operation 1313, the SliceType may be set to PRIORITIZE_LATENCY, and the RequestingApp may be set to com.x.game, which is the OSAppId of the first application (411).

[0240] The connection manager (415) that received the releaseNetwork message from the first application (411)

[0241] In operation 1315, a releaseNetwork message may be transmitted to the telephony manager (417) (e.g., the telephony manager (417) of FIG. 4, FIG. 8, FIG. 9, or FIG. 11).

[0242] The telephony manager (417), which has received a releaseNetwork message from the connection manager (415), may transmit a data call deactivation request (hereinafter referred to as “DEACTIVATE_DATA_CALL_REQ”) message requesting deactivation of a data call to the communication processor (210) in accordance with the IPC format agreed upon between the telephony manager (417) and the communication processor (410) in operation 1317. The telephony manager (417) may set the SliceType included in the releaseNetwork message received from the connection manager (415) to the OSAppId included in the DEACTIVATE_DATA_CALL_REQ message.

[0243] The communication processor (410) that receives the DEACTIVATE_DATA_CALL_REQ message from the telephony manager (417) may transmit a PDU Session Release Request message requesting the network (420) to release the PDU session in operation 1319.

[0244] In response to the PDU Session Release Request message, the communication processor (410) may receive a PDU Session Release Accept message from the network (420) indicating that the request for PDU session release is accepted at operation 1321.

[0245] The communication processor (410) that receives the PDU Session Release Accept message can confirm that the first PDU session for the first application (411) is released, and can transmit a data call setup response (hereinafter referred to as “DEACTIVATE_DATA_CALL_RESP”) message indicating that the request for data call deactivation has been successfully performed to the telephony manager (417) in operation 1323. The first PDU session is a PDU session for a category-based network slice, and may be a PDU session established between the network (420) and the electronic device (101).

[0246] The telephony manager (417), which has received the DEACTIVATE_DATA_CALL_RESP message from the communication processor (410), may transmit a message (hereinafter referred to as an “onNetworkDisconnected message”) indicating that the network slice is disconnected to the connection manager (415) in operation 1325. The onNetworkDisconnected message transmitted in operation 1325 may include information indicating that the request for disconnection of the network connection has been successfully performed.

[0247] The connection manager (415) that receives the onNetworkDisconnected message from the telephony manager (417) can transmit the onNetworkDisconnected message to the first application (411) in operation 1327. The onNetworkDisconnected message transmitted in operation 1327 can include information indicating that the request for releasing the network connection has been successfully performed. The first application (411) that receives the onNetworkDisconnected message from the connection manager (415) can confirm that the first PDU session for the first application (411) has been released. The telephony manager (417) that confirms that the first PDU session for the first application (411) has been released can transmit a message (hereinafter referred to as a “releaseAdditionalNetwork message”) requesting the release of an additional network slice connection to the slice manager (419) (e.g., the slice manager (419) of FIG. 4, FIG. 8, FIG. 9, or FIG. 11) in operation 1329. The releaseAdditionalNetwork message may include RequestingApp, which is information indicating the application requesting the release of the network slice connection. In the releaseAdditionalNetwork message, RequestingApp may be set to "com.x.game," which is the OSAppId of the first application (411).

[0248] The slice manager (419), which has received the releaseAdditionalNetwork message from the telephony manager (417), may determine whether to release the second PDU session for the first application (411) based on the condition for releasing the second PDU session in operation 1331. In one embodiment, the condition for releasing the second PDU session may include at least one of the following first condition, second condition, third condition, or fourth condition.

[0249] (1) Condition 1

[0250] The first condition may include a condition under which the first PDU session is released.

[0251] (2) Second condition

[0252] A condition may be included that verifies user input indicating a refusal to establish a second PDU session.

[0253] (3) Third condition

[0254] The third condition may include a condition where the point in time at which the second PDU session is established does not exist within a time corresponding to the time information. The time information may be implemented similarly or substantially identically to that described in FIG. 8, and therefore, a detailed description thereof is omitted here.

[0255] (4) Condition 4

[0256] The fourth condition may include a condition in which the electronic device's location at the time the second PDU session is established is not at a location corresponding to the location information. The location information may be implemented similarly or substantially identically to that described in FIG. 8, and therefore, a detailed description thereof is omitted herein.

[0257] (5) Condition 5

[0258] The fifth condition may include a condition for releasing the third condition for establishing the second PDU session and / or the fourth condition. For example, if the third condition for establishing the second PDU session and / or the fourth condition are set and the third condition for establishing the second PDU session and / or the fourth condition are released, the slice manager (419) may decide to release the second PDU session. The fifth condition may further include a condition for releasing only the second PDU session while the first PDU session is established. According to one embodiment, a separate UI pop-up may be implemented to release the third condition and / or the fourth condition, which will be described below with reference to FIG. 14, and thus a detailed description thereof will be omitted herein.

[0259] The slice manager (419) may transmit a DEACTIVATE_DATA_CALL_REQ message requesting the communication processor (410) to deactivate a data call. In the DEACTIVATE_DATA_CALL_REQ message transmitted in operation 1331, the OSId may be set to "97a498e3-fc92-5c94-8986-033d06e4e47", which is the OSId of the OS running on the electronic device (101), and the OsAppId may be set to "com.x.game", which is the OSAppId of the first application (411).

[0260] The communication processor (410) that receives the DEACTIVATE_DATA_CALL_REQ message from the slice manager (419) can transmit a PDU Session Release Request message requesting to release the PDU session to the network (420) in operation 1333.

[0261] In response to the DEACTIVATE_DATA_CALL_REQ message, the communication processor (410) may receive a PDU Session Release Accept message from the network (420) indicating that the request for PDU session release is accepted at operation 1335.

[0262] The communication processor (410) that receives the PDU Session Release Accept message can confirm that the second PDU session for the first application (411) is released, and can transmit a DEACTIVATE_DATA_CALL_RESP message to the slice manager (419) indicating that the request for data call deactivation has been successfully performed in operation 1337.

[0263] FIG. 13b is a signal flow diagram illustrating a PDU session release procedure according to one embodiment.

[0264] Referring to FIG. 13b, the first application (411) may transmit a requestNetwork message requesting a network slice connection to a connection manager (415) (e.g., the connection manager (415) of FIG. 4, FIG. 8, FIG. 9, FIG. 11, or FIG. 13a) in operation 1351. In the requestNetwork message transmitted in operation 1351, SliceType may be set to PRIORITIZE_LATENCY, and RequestingApp may be set to com.x.game, which is the OSAppId of the first application (411). As the requestNetwork message is transmitted from the first application (411), in operation 1353, the connection manager (415), the telephony manager (417) (e.g., the telephony manager (417) of FIG. 4, FIG. 8, FIG. 9, FIG. 11, or FIG. 13a), the communication processor (410) (e.g., the auxiliary processor (123) of FIG. 1, the first communication processor (212) or the second communication processor (214) of FIG. 2a, the integrated communication processor (260) of FIG. 2b, or the communication processor (410) of FIG. 4, FIG. 8, FIG. 9, FIG. 11, or FIG. 13a), the slice manager (419) (e.g., the slice manager (419) of FIG. 4, FIG. 8, FIG. 9, FIG. 11, or FIG. 13a), the network (420) (e.g., the slice manager (419) of FIG. 4, FIG. 8, FIG. 9, FIG. 11, or FIG. 13a) A procedure for establishing a first PDU session for a first application (411) between networks (420) may be performed. The first PDU session may be a PDU session for a category-based network slice, and may be a PDU session established between the network (420) and the electronic device (101). The operation for establishing the first PDU session may be implemented similarly or substantially identically to that described in FIG. 4, FIG. 8, FIG. 9, FIG. 11, or FIG. 13A, and thus a detailed description thereof will be omitted herein.

[0265] As operation 1353 is performed, a first PDU session may be established, and the connection manager (415) may forward an onNetworkConnected message to the first application (411) in operation 1355. After forwarding the onNetworkConnected message to the first application (411), a procedure for establishing a second PDU session for the first application (411) among the connection manager (415), the telephony manager (417), the communication processor (410), the slice manager (419), and the network (420) may be performed in operation 1357. In one embodiment, the second PDU session may be a PDU session for an application-specific network slice, different from a category-based network slice, and may be a PDU session established between the network (420) and the electronic device (101). The operation of establishing a second PDU session can be implemented similarly or substantially identically to that described in FIG. 4, FIG. 8, FIG. 9, FIG. 11, or FIG. 13a, and therefore, a detailed description thereof is omitted here.

[0266] When a user input indicating that the second PDU session for the first application (411) is not to be used is confirmed through the UI (1350) in operation 1359 while the first PDU session and the second PDU session for the first application (411) are established, an App1 slice disconnection request message requesting the telephony manager (417) to release the second PDU session may be transmitted through the UI (1350) in operation 1361.

[0267] The telephony manager (417), which has received an App1 slice disconnection request message from the UI (1350), may transmit a releaseAdditionalNetwork message requesting the release of an additional network slice connection to the slice manager (419) in operation 1363. Operation 1363 may be implemented similarly or substantially identically to operation 1329 of FIG. 13A, and thus a detailed description thereof will be omitted here.

[0268] The slice manager (419), which has received the releaseAdditionalNetwork message from the telephony manager (417), may transmit a DEACTIVATE_DATA_CALL_REQ message requesting the communication processor (410) to deactivate the data call in operation 1365. In the DEACTIVATE_DATA_CALL_REQ message transmitted in operation 1331, the OSId may be set to "97a498e3-fc92-5c94-8986-033d06e4e47", which is the OSId of the OS running on the electronic device, and the OsAppId may be set to "com.x.game", which is the OSAppId of the first application (411).

[0269] The communication processor (410) that receives the DEACTIVATE_DATA_CALL_REQ message from the slice manager (419) may transmit a PDU Session Release Request message requesting the network (420) to release the PDU session in operation 1367.

[0270] In response to the DEACTIVATE_DATA_CALL_REQ message, the communication processor (410) may receive a PDU Session Release Accept message from the network (420) at operation 1369 indicating that the request for PDU session release is accepted.

[0271] The communication processor (410) that receives the PDU Session Release Accept message can confirm that the second PDU session for the first application (411) is released, and can transmit a DEACTIVATE_DATA_CALL_RESP message to the slice manager (419) indicating that the request for data call deactivation has been successfully performed in operation 1371.

[0272] FIG. 14 is a diagram illustrating a UI pop-up for releasing a fifth condition used to establish a second PDU session according to one embodiment.

[0273] Referring to FIG. 14, the condition for establishing the second PDU session is similar to or can be implemented substantially identically to the fifth condition described in FIG. 13a, and therefore, a detailed description thereof is omitted here.

[0274] The UI pop-up provided to release the third condition, which is a condition that the time when the second PDU session is established exists within a time corresponding to the time information, and / or the fourth condition, which is a condition that the location of the electronic device at the time when the second PDU session is established exists at a location corresponding to the location information, may be implemented as shown in screen (1400). Screen (1400) may be a screen for releasing the third condition and / or the fourth condition for at least one of a plurality of applications, and in FIG. 14, it is assumed that an icon (1401) corresponding to the first application App1 is selected, in which case a screen (1410) indicating that the third condition and / or the fourth condition for the first application is released may be output. Unlike screen (1400), screen (1410) may indicate that an icon (1402) corresponding to the first application App1 releases the third condition and / or the fourth condition.

[0275] FIG. 15 is a signal flow diagram illustrating a PDU session establishment procedure according to one embodiment.

[0276] Referring to FIG. 15, operations 1511 to 1537 may be implemented similarly to, or substantially identically to, operations 811 to 837 of FIG. 8, and therefore, a detailed description thereof will be omitted herein.

[0277] However, after the first PDU session is established, a network interface generated by an OS running on an electronic device (e.g., the electronic device (101) of FIG. 1, FIG. 2a, FIG. 2b, FIG. 3a, FIG. 3b, or FIG. 4) (e.g., a smartphone or UE) is additionally illustrated. For example, after the first PDU session is established, a network interface rmnet0 may be generated, and a first routing rule as shown in Table 4 below may be generated. The first routing rule may be based on policy-based routing, and may be generated by a slice manager (419) (e.g., the slice manager (419) of FIG. 4, FIG. 8, FIG. 9, FIG. 11, or FIG. 13a).

[0278] Table 4

[0279]

[0280] As shown in Table 4, the first routing rule may be a routing rule that specifies that all packets using netid 100 with a priority of 10000 are referred to the routing table corresponding to the rmnet0 network interface. For example, a higher priority value may indicate a higher priority.

[0281] For example, after the second PDU session is established, the rmnet1 network interface may be created, and a second routing rule as shown in Table 5 below may be created. The second routing rule may be based on policy-based routing and may be created by the slice manager (419).

[0282] Table 5

[0283]

[0284] As shown in Table 5, the second routing rule can be created to refer to a specific routing rule for a specific application (e.g., the first application (411) of FIG. 4, FIG. 8, FIG. 9, FIG. 11, or FIG. 13a). In the second routing rule of Table 5, the priority for the first application with the OSAppId "com.x.game" is set to 9000, which is lower than the priority of the first routing rule with 10000, so that the data of the first application can be transmitted and received via the network interface rmnet0. If the priority for the first application in the second routing rule is set to a value greater than the priority of the first routing rule with 10000, the data of the first application can be transmitted and received via the network interface rmnet1. In Table 5, "from com.x.game lookup rmnet1" may indicate that data from com.x.game needs to lookup rmnet1. The second routing rule in Table 5 may indicate that data targeting the destination IP address 0.0.0.0 in the rmnet1 routing table needs to be sent through rmnet1 to the gateway with the IP address 192.168.1.2, and data targeting the destination IP address 192.168.1.0 needs to be sent through rmnet1 to the gateway with the IP address 0.0.0.0.

[0285] FIG. 16 is a flowchart schematically illustrating a PDU session selection operation according to one embodiment.

[0286] Referring to FIG. 16, when a first PDU session and a second PDU session are established for a first application (e.g., the first application (411) of FIG. 4, FIG. 8, FIG. 9, FIG. 11, FIG. 13a, or FIG. 15), an electronic device (e.g., the electronic device (101) of FIG. 1, FIG. 2a, FIG. 2b, FIG. 3a, FIG. 3b, or FIG. 4) (e.g., a smartphone or UE) (e.g., the processor (120) of FIG. 1, FIG. 2a, or FIG. 2b, the first communication processor (212) or the second communication processor (214) of FIG. 2a, or the integrated communication processor (260) of FIG. 2b, or the communication processor (410) of FIG. 4, FIG. 8, FIG. 9, FIG. 11, FIG. 13a, or FIG. 15) can transmit and receive data of the first application through the second PDU session. In one embodiment, the first PDU session may be a PDU session for a category-based network slice, and may be a PDU session established between the network and the electronic device. In one embodiment, the second PDU session may be additionally established after the first PDU session is established. The second PDU session may be a PDU session for an application-specific network slice, different from the category-based network slice, and may be a PDU session established between the network (420) and the electronic device (101).

[0287] While transmitting and receiving data of the first application through the second PDU session, the electronic device may collect traffic status information of the first application transmitting and receiving data through the second PDU session in operation 1611. In one embodiment, the traffic status information may include, but is not limited to, information related to a transmission control protocol (TCP) packet loss rate and / or a domain name server (DNS) query / response error rate. In one embodiment, the time for collecting the traffic status information may be adaptively determined as needed.

[0288] An electronic device that has collected traffic status information of a first application may, in operation 1613, determine whether a TCP packet loss rate of a second PDU session exceeds a first threshold or a DNS query / response error rate of the second PDU session exceeds a second threshold. The operation of determining whether the TCP packet loss rate of the second PDU session exceeds the first threshold or the DNS query / response error rate of the second PDU session exceeds the second threshold may be an operation of determining whether a traffic status of the second PDU session satisfies a reference condition. The reference condition may include a condition under which traffic transmission and reception through the second PDU session can be stably performed, and the reference condition may be adaptively set as needed. For example, if the TCP packet loss rate of the second PDU session exceeds the first threshold or the DNS query / response error rate of the second PDU session exceeds the second threshold, the electronic device may determine that the traffic status of the second PDU session does not satisfy the reference condition. For example, the electronic device can determine that the traffic status of the second PDU session satisfies the reference condition if the TCP packet loss rate of the second PDU session is less than or equal to a first threshold value and the DNS query / response error rate of the second PDU session is less than or equal to a second threshold value. If the TCP packet loss rate of the second PDU session exceeds the first threshold value or the DNS query / response error rate of the second PDU session exceeds the second threshold value (operation 1613-Yes), the electronic device can determine that the traffic status of the second PDU session is not good, and therefore, in operation 1615, can set a routing rule so that the first application can transmit and receive data through the first PDU session.

[0289] While the first application transmits and receives data through the first PDU session based on the routing rules, the electronic device may perform a ping operation to check the traffic status of the second PDU session at operation 1617. In FIG. 16, a case where the ping operation is performed to check the traffic status of the second PDU session is described as an example, but may not be limited thereto.

[0290] The electronic device that performed the ping operation to check the traffic status of the second PDU session can check whether the ping loss rate of the second PDU session is less than the third threshold value in operation 1619. If the ping loss rate of the second PDU session is less than the third threshold value (operation 1619 - Yes), the electronic device can check that the traffic status of the second PDU session is good, and therefore, in operation 1621, can set a routing rule so that the first application can transmit and receive data through the second PDU session.

[0291] As described in FIG. 16, when a first PDU session and a second PDU session are established for a first application, the first application can transmit and receive data through the second PDU session by default, and thereafter, based on the traffic status of the second PDU session, can transmit and receive data through the first PDU session or the second PDU session.

[0292] FIG. 17 is a signal flow diagram illustrating a PDU session establishment procedure according to one embodiment.

[0293] Referring to FIG. 17, a processor (410) (e.g., processor (120) of FIG. 1, FIG. 2A, or FIG. 2B, first communication processor (212) or second communication processor (214) of FIG. 2A, or integrated communication processor (260) of FIG. 2B, or communication processor (410) of FIG. 4, FIG. 8, FIG. 9, FIG. 11, FIG. 13A, or FIG. 15) may receive URSP rules for a first application (411) (e.g., first application (411) of FIG. 4, FIG. 8, FIG. 9, FIG. 11, FIG. 13A, or FIG. 15) and a second application (413) (e.g., second application (413) of FIG. 4)) in operation 1711 (URSP Rule Provisioning). The URSP rules for the first application (411) and the second application (413) may be as shown in Table 6 below.

[0294] Table 6

[0295]

[0296] As shown in Table 6, com.x.game is the OSAppId of the first application (411), com.y.game is the OSAppId of the second application (413), and PRIORITIZE_LATENCY may be the type of network slice that the first application (411) and the second application (413) want to connect to. In Table 6, URSP Rule #1 may be a URSP rule for a network slice connection corresponding to the PRIORITIZE_LATENCY category, and URSP Rule #2 may be a URSP rule for a network slice connection dedicated to the first application (411). In Table 6, URSP Rule #3 may be a URSP rule for a network slice connection dedicated to the second application (413). PRIORITIZE_LATENCY may indicate a network slice type for an application category that is relatively sensitive to latency. A network slice corresponding to the PRIORITIZE_LATENCY category may be a public network slice that can be used by multiple applications. The remaining information shown in Table 6 may be implemented similarly or substantially identically to that described in FIG. 6.

[0297] After receiving the URSP rules for the first application (411) and the second application (413), the first application (411) may transmit a requestNetwork message requesting a network slice connection to the connection manager (415) (e.g., the connection manager (415) of FIG. 4, FIG. 8, FIG. 9, FIG. 11, FIG. 13a, or FIG. 15) in operation 1713. Operations 1713 to 1737 may be implemented similarly or substantially identically to operations 813 to 837 of FIG. 8, and thus, a detailed description thereof will be omitted herein.

[0298] Thereafter, the second application (413) may transmit a requestNetwork message requesting a network slice connection to the connection manager (415) in operation 1751. The requestNetwork message may include a SliceType indicating a network slice to be connected to and a RequestingApp information indicating an application requesting the network slice connection. In the requestNetwork message transmitted in operation 1751, the SliceType may be set to PRIORITIZE_LATENCY, and the RequestingApp may be set to com.y.game, which is the OSAppId of the second application (413).

[0299] The connection manager (415), which has received the requestNetwork message from the second application (413), can confirm that there is no need to establish the first PDU session because the first PDU session, which is a PDU session corresponding to the SliceType, has already been established. In operation 1753, the connection manager (415) can transmit the requestNetwork message to the telephony manager (417) (e.g., the telephony manager (417) of FIG. 4, FIG. 8, FIG. 9, FIG. 11, FIG. 13a, or FIG. 15).

[0300] Since the first PDU session, which is a PDU session corresponding to the SliceType, has already been established, the connection manager (415) can transmit an onNetworkConnected message indicating that the network slice is connected in operation 1755. The onNetworkConnected message transmitted in operation 1755 can include information indicating that the request for network connection was successfully performed.

[0301] The telephony manager (417), which has confirmed that the first PDU session is established, may transmit a requestAdditionalNetwork message requesting an additional network slice connection to the communication processor (210) in accordance with the IPC format agreed upon between the telephony manager (417) and the communication processor (410) in operation 1757. The requestAdditionalNetwork message may include RequestingApp, which is information indicating an application requesting a network slice connection. In the requestAdditionalNetwork message, the RequestingApp may be set to "com.y.game", which is the OSAppId of the second application (413).

[0302] The slice manager (419), which receives the requestAdditionalNetwork message from the telephony manager (417), can determine whether to establish a second PDU session for the second application (413) based on the URSP rule and the condition for establishing the second PDU session. The condition for establishing the second PDU session for the second application (413) can include at least one of the first condition, the second condition, the third condition, or the fourth condition, and the first condition, the second condition, the third condition, and the fourth condition can be implemented similarly or substantially identically to those described in FIG. 8, and therefore, a detailed description thereof will be omitted herein.

[0303] In Fig. 17, an example will be described in which a slice manager (419) decides to establish a second PDU session for a second application (413) based on a first condition. The slice manager (419) that decides to establish a second PDU session for a second application (413) can transmit a SETUP_DATA_CALL_REQ message requesting the communication processor (410) to set up a data call in operation 1759. In the SETUP_DATA_CALL_REQ message transmitted at operation 1759, the OSId may be set to "97a498e3-fc92-5c94-8986-033d06e4e47", which is the OSId of the OS running on the electronic device (e.g., the electronic device (101) of FIG. 1, FIG. 2a, FIG. 2b, FIG. 3a, FIG. 3b, or FIG. 4) (e.g., a smartphone or UE), and the OsAppId may be set to "com.y.game", which is the OSAppId of the second application (413).

[0304] The communication processor (410) that receives the SETUP_DATA_CALL_REQ message from the slice manager (419) can transmit a PDU Session Establishment Request message requesting to establish a PDU session to the network (420) based on the URSP rule stored in operation 1761.

[0305] In response to the PDU Session Establishment Request message, the communication processor (410) may receive a PDU Session Establishment Accept message from the network (420) indicating that the request for PDU session establishment is accepted at operation 1763.

[0306] The communication processor (410) that receives the PDU Session Establishment Accept message can confirm that a second PDU session for the second application (413) is established, and can transmit a SETUP_DATA_CALL_RESP message indicating that a request for data call setup has been successfully performed to the slice manager (419) in operation 1765. The first PDU session is a PDU session for a category-based network slice, and may be a PDU session established between the network (420) and the electronic device (101). The second PDU session of the first application (411) and the second PDU session of the second application (413) are PDU sessions for an application-specific network slice that is different from the category-based network slice, and may be PDU sessions established between the network (420) and the electronic device (101). In one embodiment, the second PDU session of the first application (411) and the second PDU session of the second application (413) may be additionally established after the first PDU session is established. In one embodiment, if the first PDU session is not established, establishment of the second PDU session of the first application (411) and the second PDU session of the second application (413) may not be attempted. In one embodiment, if the first PDU session is released, the second PDU session of the first application (411) and the second PDU session of the second application (413) may also be released.

[0307] In this way, when two PDU sessions (e.g., a first PDU session and a second PDU session) are established for the first application (411), the slice manager (419) can determine whether the first application (411) will use the first PDU session or the second PDU session based on the set policy, and can update the routing table of the electronic device through the routing manager (e.g., the routing manager (421) of FIG. 4) based on the decision. When two PDU sessions (e.g., a first PDU session and a second PDU session) are established for the second application (413), the slice manager (419) can determine whether the second application (413) will use the first PDU session or the second PDU session based on the set policy, and can update the routing table of the electronic device through the routing manager (e.g., the routing manager (421) of FIG. 4) based on the decision. The policy used to determine which of the two PDU sessions to use for an application has been described above, and therefore its detailed description is omitted here.

[0308] FIG. 18 is a diagram illustrating a UI notification indicating that an application is communicating via a second PDU session according to one embodiment.

[0309] Referring to FIG. 18, when an application in the foreground is communicating via a second PDU session, a screen (1800) corresponding to the application may be displayed while the communication via the second PDU session may be provided in the form of a bar (1810).

[0310] According to one embodiment of the present disclosure, the method of the electronic device (101) may include an operation of obtaining a first URSP rule and a second URSP rule.

[0311] According to one embodiment of the present disclosure, the method may include establishing a first PDU session with a network (420) based on the first URSP rule used for a PDU session for a network slice common to a plurality of applications.

[0312] According to one embodiment of the present disclosure, the method may include establishing a second PDU session with the network based on the second URSP rule used to establish a PDU session for a network slice dedicated to the application, based on verifying that a setup condition is satisfied.

[0313] According to one embodiment of the present disclosure, the set condition may be identified as being satisfied when a first condition is satisfied that the first PDU session is established, a second condition is satisfied that the first PDU session is established and a user input indicating consent to establish the second PDU session is confirmed, and a third condition is satisfied that the first PDU session is established and a time corresponding to the set time information at which the second PDU session is established exists.

[0314] According to one embodiment of the present disclosure, the set condition may be identified as being satisfied when a first condition is satisfied that the first PDU session is established, a second condition is satisfied that the first PDU session is established and a user input indicating consent to establishing the second PDU session is confirmed, and a fourth condition is satisfied that the location of the electronic device at the time the first PDU session is established and the second PDU session is established is at a location corresponding to the set location information.

[0315] According to one embodiment of the present disclosure, the set time information may include at least one of time information corresponding to a time window included in a route selection descriptor included in the second URSP rule, or time information based on a user setting.

[0316] According to one embodiment of the present disclosure, the set location information may include at least one of location information included in a route selection descriptor included in the second USRP rule, or location information based on a user setting.

[0317] According to one embodiment of the present disclosure, the method may include an operation of transmitting and receiving data of the application through the second PDU session after the second PDU session is established.

[0318] According to one embodiment of the present disclosure, the method may include an operation of checking whether a traffic status of the second PDU session satisfies a set criterion while transmitting and receiving data of the application through the second PDU session.

[0319] According to one embodiment of the present disclosure, the method may include an operation of transmitting and receiving data of the application through the first PDU session based on determining that the traffic status of the second PDU session does not satisfy a set criterion.

[0320] According to one embodiment of the present disclosure, the setting criteria may include a criterion that a TCP packet loss rate of the second PDU session exceeds a first threshold, or a criterion that a DNS query / response error rate of the second PDU session exceeds a second threshold.

[0321] According to one embodiment of the present disclosure, a storage medium storing at least one computer-readable instruction may be provided.

[0322] According to one embodiment of the present disclosure, the at least one instruction, when executed individually or collectively by one or more processors (120; 212; 214; 260; 410) of the electronic device (101), may cause the electronic device (101) to perform at least one operation.

[0323] In one embodiment, the at least one operation may include obtaining a first URSP rule and a second URSP rule.

[0324] In one embodiment, the at least one operation may include establishing a first PDU session with the network (420) based on the first URSP rule used for a PDU session for a network slice common to multiple applications.

[0325] In one embodiment, the at least one operation may include establishing a second PDU session with the network based on the second URSP rule used to establish a PDU session for a network slice dedicated to the application, based on verifying that a setup condition is satisfied.

Claims

1. In an electronic device (101), Communication circuit (190); One or more processors (120; 212; 214; 260; 410) comprising processing circuitry; and A memory (130) for storing instructions, wherein the instructions, when individually or collectively executed by one or more processors, cause the electronic device to: Obtain the first user equipment route selection policy (URSP) rule and the second URSP rule, Through the above communication circuit, a first PDU session is established with the network (420) based on the first URSP rule used for a protocol data unit (PDU) session for a network slice common to multiple applications, and An electronic device that causes the network to establish a second PDU session based on the second URSP rule used to establish a PDU session for a network slice dedicated to an application, through the communication circuit, based on verification that the setup condition is satisfied.

2. In paragraph 1, The first condition for establishing the above first PDU session, A second condition wherein the first PDU session is established and user input indicating consent to establishing the second PDU session is confirmed, and The electronic device, wherein the first PDU session is established and the third condition that exists within a time corresponding to the time information set at which the second PDU session is established is satisfied, is identified as the set condition being satisfied.

3. In paragraph 1, The first condition for establishing the above first PDU session, A second condition wherein the first PDU session is established and user input indicating consent to establishing the second PDU session is confirmed, and An electronic device, wherein the electronic device is identified as having satisfied the set condition when a fourth condition is satisfied that the location of the electronic device at the time the first PDU session is established and the second PDU session is established is at a location corresponding to the set location information.

4. In paragraph 2, The electronic device wherein the set time information includes at least one of time information corresponding to a time window included in a route selection descriptor included in the second URSP rule, or time information based on a user setting.

5. In paragraph 3, The electronic device wherein the set location information includes at least one of location information included in a route selection descriptor included in the second USRP rule or location information based on a user setting.

6. In paragraph 1, The above instructions, when individually or collectively executed by one or more processors, cause the electronic device to: An electronic device that causes data of the application to be transmitted and received through the second PDU session via the communication circuit after the second PDU session is established.

7. In paragraph 6, The above instructions, when individually or collectively executed by one or more processors, cause the electronic device to: While transmitting and receiving data of the application through the second PDU session, it is checked whether the traffic status of the second PDU session satisfies the set criteria, and An electronic device that causes data of the application to be transmitted and received through the first PDU session through the communication circuit based on determining that the traffic status of the second PDU session does not satisfy the set criteria.

8. In paragraph 7, The electronic device wherein the above setting criteria include a criterion that a transmission control protocol (TCP) packet loss rate of the second PDU session exceeds a first threshold, or a criterion that a domain name server (DNS) query / response error rate of the second PDU session exceeds a second threshold.

9. In any one of paragraphs 1 to 8, The above instructions, when individually or collectively executed by one or more processors, cause the electronic device to: An electronic device that causes the network to release the second PDU session through the communication circuit based on verification that other setup conditions are satisfied.

10. In paragraph 9, The other setting conditions above are: Conditions under which the above first PDU session is released, A condition in which user input indicating a refusal to establish the above second PDU session is confirmed; A condition where the point in time at which the above second PDU session is established does not exist within the time corresponding to the set time information; A condition where the location of the electronic device at the time the second PDU session is established is not in a location corresponding to the set location information, or The electronic device including at least one of the conditions for releasing the setting of at least one of the third condition or the fourth condition.

11. In paragraph 10, The above set time information includes at least one of time information corresponding to a time window included in a route selection descriptor included in the second URSP rule, or time information based on a user setting, or The electronic device wherein the set location information includes at least one of location information included in a route selection descriptor included in the second USRP rule or location information based on a user setting.

12. In the method of electronic device (101), An operation of obtaining a first user equipment route selection policy (URSP) rule and a second URSP rule; An operation of establishing a first PDU session with the network (420) based on the first URSP rule used for a protocol data unit (PDU) session for a network slice common to multiple applications; and A method comprising: establishing a second PDU session with the network based on the second URSP rule used to establish a PDU session for a network slice dedicated to the application, based on verifying that the setup condition is satisfied.

13. In paragraph 12, The first condition for establishing the above first PDU session, A second condition wherein the first PDU session is established and user input indicating consent to establishing the second PDU session is confirmed, and The method, wherein the set condition is identified as being satisfied when a third condition is satisfied that exists within a time corresponding to the time information set when the first PDU session is established and the second PDU session is established.

14. In paragraph 12, The first condition for establishing the above first PDU session, A second condition wherein the first PDU session is established and user input indicating consent to establishing the second PDU session is confirmed, and The method, wherein the set condition is identified as being satisfied when a fourth condition is satisfied in which the location of the electronic device at the time the first PDU session is established and the second PDU session is established is at a location corresponding to the set location information.

15. In a storage medium storing at least one computer-readable instruction, The at least one instruction, when executed individually or collectively by one or more processors (120; 212; 214; 260; 410) of the electronic device (101), causes the electronic device (101) to perform at least one operation, At least one of the above actions: An operation for obtaining a first user equipment route selection policy (URSP) rule and a second URSP rule; An operation of establishing a first PDU session with a network (420) based on the first URSP rule used for a protocol data unit (PDU) session for a network slice common to multiple applications, and The storage medium including an operation of establishing a second PDU session with the network based on the second URSP rule used to establish a PDU session for a network slice dedicated to the application, based on verifying that the setup condition is satisfied.

Images