KR20230075205A - Electronic device using network slice and method for operating thereof - Google Patents

Abstract

According to various embodiments, an electronic device includes at least one processor. The at least one processor may be configured to obtain a URSP rule including at least one traffic descriptor and at least one path selection descriptor, confirm that the time identified by the electronic device and/or the location identified by the electronic device corresponds to first time information and/or first place information included in a first path selection descriptor among the at least one path selection descriptor, provide a notification to a first application identified by a first traffic descriptor among the at least one traffic descriptor corresponding to the first path selection descriptor, and perform at least one operation for establishing a PDU session based on the first path selection descriptor corresponding to the first application based on the confirmation of a network connection request from the first application that has received the notification. Various other embodiments are possible. Accordingly, the establishment of a specific PDU session may be possible.

Description

Electronic device and operation method using network slice {ELECTRONIC DEVICE USING NETWORK SLICE AND METHOD FOR OPERATING THEREOF}

Various embodiments relate to an electronic device and operating method using a network slice.

Efforts have been made to develop an improved 5G communication system or 6G communication system in order to meet the growing demand for wireless data traffic after the commercialization of the 4G communication system. For this reason, the 5G communication system or the 6G communication system is called a Beyond 4G Network communication system or a Post LTE system. In order to achieve high data transmission rates, 5G communication systems are being implemented and serviced in mmWave bands (eg, 60 gigabytes (60 GHz) bands) and sub-6 GHz bands. In 5G communication, in order to mitigate the path loss of radio waves and increase the transmission distance of radio waves with a higher frequency than conventional LTE, beamforming, massive MIMO, and full-dimensional multiple input/output Dimensional MIMO (FD-MIMO), array antenna, analog beam-forming, and large scale antenna technologies are being discussed.

Among the new structural features of the 5G network, the most prominent is the introduction of network slicing technology for the Radio Access Network (RAN) and Core Network (CN) structures. It bundles network resources and network functions into one independent network slice according to individual services, thereby providing isolation, customization, independent management and orchestration of network system functions and resources. It is intended to apply the same property to the mobile communication network structure. Using this network slicing technology, it is possible to provide independent and flexible 5G services by selecting and combining network functions of the 5G system according to service, user, and business model criteria.

In the 3rd generation partnership project (3GPP), UE route selection policy (URSP) rules are defined. A user equipment (UE) may receive a URSP rule from a policy control function (PCF) and establish a data session with a network slice. A URSP rule may include a traffic descriptor and a route selection descriptor.

According to TS (technical specification) 24.526 of 3GPP, the path selection descriptor may include time information (eg, time window) and/or location information (eg, location criteria) in which a PDU session can be effectively established. can For example, the time window may mean a time window in which matched traffic is allowed. For example, the location criteria may indicate a location of a user device where matched traffic is permitted. If the time information and/or the location information checked based on the network connection request (eg, requestNetwork) from the application corresponds to the time information and/or location information included in the path selection descriptor, the user device An operation for establishing a PDU session based on the path selection descriptor may be performed. However, the path selection descriptor of the URSP rule is not provided to the application. Accordingly, in order to establish the corresponding PDU session, the application must provide a network connection request in response to the time information and/or location information accidentally included in the path selection descriptor, and thus the availability of the corresponding PDU session is reduced. It can be.

According to various embodiments, the electronic device and its operating method provide a notification to an application when the checked time information and/or the checked place information corresponds to the time information and/or place information included in the path selection descriptor, , at least one operation for establishing a PDU session may be performed based on confirmation of a network connection request in response to the notification.

According to various embodiments, an electronic device includes at least one processor, and the at least one processor obtains a URSP rule including at least one traffic descriptor and at least one path selection descriptor, and in the electronic device confirming that the time identified by and/or the place identified by the electronic device corresponds to first time information and/or first place information included in a first route selection descriptor among the at least one route selection descriptor; A notification is provided to a first application identified by a first traffic descriptor among the at least one traffic descriptor corresponding to the first path selection descriptor, and a network connection request is made from the first application receiving the notification. Based on this confirmation, it may be configured to perform at least one operation for establishing a PDU session based on the first path selection descriptor corresponding to the first application.

According to various embodiments, an operating method of an electronic device may include obtaining a URSP rule including at least one traffic descriptor and at least one path selection descriptor, a time identified by the electronic device, and/or the electronic device An operation of confirming that the place identified by the above corresponds to first time information and/or first place information included in a first route selection descriptor among the at least one route selection descriptor, and a second route corresponding to the first route selection descriptor. 1 An operation of providing a notification to a first application identified by a traffic descriptor, and based on confirmation of a network connection request from the first application that has received the notification, the first application corresponding to the first application. 1 It may include an operation of performing at least one operation for establishing a PDU session based on the path selection descriptor.

According to various embodiments, an electronic device includes at least one processor, and the at least one processor obtains a URSP rule including at least one traffic descriptor and at least one path selection descriptor, and from a first application Obtaining a network connection request for an event of, and selecting a first path among the at least one path selection descriptor corresponding to a first traffic descriptor among the at least one traffic descriptor identified based on information included in the network connection request Based on the first path selection descriptor, based on the first time information and/or first place information included in the descriptor corresponding to the time and/or the place confirmed by the electronic device It can be configured to perform at least one operation for establishing a PDU session.

According to various embodiments, an electronic device includes at least one processor, and the at least one processor obtains a URSP rule including at least one traffic descriptor and at least one path selection descriptor, and from a first application First time information included in a first path selection descriptor of the at least one path selection descriptor corresponding to a first traffic descriptor among the at least one traffic descriptor that confirms the inquiry and is identified based on the information included in the inquiry and/or providing a response corresponding to the inquiry to the first application based on the correspondence of the first location information to the time and/or the location confirmed by the electronic device; Based on confirmation of a network connection request from the first application receiving a response, at least one operation for establishing a PDU session based on the first path selection descriptor corresponding to the first application may be set to be performed. there is.

According to various embodiments, a network that provides a notification to an application and responds to the notification when the checked time information and/or the checked place information corresponds to the time information and/or place information included in the path selection descriptor. An electronic device capable of performing at least one operation for establishment of a PDU session based on confirmation of a connection request and an operating method thereof may be provided. Accordingly, since the application can check whether the conditions for establishing a specific PDU session are satisfied, it is possible to establish a specific PDU session. Since the application can check whether a condition for establishing a specific PDU session connectable at a specific time and/or location is satisfied, a specific PDU session to be connected by the application can be established.

1 is a block diagram of an electronic device in a network environment, according to various embodiments.
2A is a block diagram of an electronic device for supporting legacy network communication and 5G network communication according to various embodiments.
2B is a block diagram of an electronic device for supporting legacy network communication and 5G network communication according to various embodiments.
Figure 3a shows a 5G system architecture.
3b shows a 5G network slice structure.
4A is a diagram illustrating a traffic allowance period according to various embodiments.
4B is a diagram illustrating a PDU session between an electronic device and a network according to various embodiments.
4C is a diagram illustrating PDU session establishment according to a location of an electronic device according to various embodiments.
5 is a flowchart illustrating an operating method of an electronic device according to various embodiments.
6 is a diagram illustrating a configuration of an event table according to various embodiments.
7 is a diagram for describing entities executed in an electronic device according to various embodiments.
8 is a diagram for describing an operation of an entity executed in an electronic device according to various embodiments.
9A is a flowchart illustrating a method of operating an electronic device according to various embodiments.
9B is a diagram for describing a UI provided by an electronic device according to various embodiments.
9C is a flowchart illustrating a method of operating an electronic device according to various embodiments.
10 is a flowchart illustrating a method of operating an electronic device according to various embodiments.
11 is a flowchart illustrating a method of operating an electronic device according to various embodiments.
12 is a flowchart illustrating a method of operating an electronic device according to various embodiments.
13 is a flowchart illustrating a method of operating an electronic device according to various embodiments.
14 is a flowchart illustrating a method of operating an electronic device according to various embodiments.
15 is a flowchart illustrating a method of operating an electronic device according to various embodiments.
16 is a flowchart illustrating a PDU session established by an electronic device according to various embodiments.
17 is a diagram for describing an operation of an entity executed in an electronic device according to various embodiments.
18 is a diagram for describing an operation of an entity executed in an electronic device according to various embodiments.
19A is a diagram for describing an operation of an entity executed in an electronic device according to various embodiments.
19B is a diagram for explaining notifications according to various embodiments.
20 is a diagram for describing operations of entities executed in an electronic device according to various embodiments.
21A is a flowchart illustrating a method of operating an electronic device according to various embodiments.
21B is a flowchart illustrating a method of operating an electronic device according to various embodiments.

1 is a block diagram of an electronic device 101 within a network environment 100, according to various embodiments. Referring to FIG. 1 , in a network environment 100, an electronic device 101 communicates with an electronic device 102 through a first network 198 (eg, a short-range wireless communication network) or through a second network 199. It is possible to communicate with the electronic device 104 or the server 108 through (eg, a long-distance wireless communication network). According to one embodiment, the electronic device 101 may communicate with the electronic device 104 through the server 108 . According to an embodiment, the electronic device 101 includes 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), interface 177, connection terminal 178, haptic module 179, camera module 180, power management module 188, battery 189, communication module 190, subscriber identification module 196 , or the antenna module 197 may be included. In some embodiments, in the electronic device 101, at least one of these components (eg, the connection terminal 178) may be omitted or one or more other components may be added. In some embodiments, some of these components (eg, sensor module 176, camera module 180, or antenna module 197) are integrated into a single component (eg, display module 160). It can be.

The processor 120, for example, executes software (eg, the program 140) to cause at least one other component (eg, hardware or software component) of the electronic device 101 connected to the processor 120. It can control and perform various data processing or calculations. According to one embodiment, as at least part of data processing or operation, the processor 120 transfers instructions or data received from other components (e.g., sensor module 176 or communication module 190) to volatile memory 132. , processing commands or data stored in the volatile memory 132 , and storing resultant data in the non-volatile memory 134 . According to one embodiment, the processor 120 may include a main processor 121 (eg, a central processing unit or an application processor) or a secondary processor 123 (eg, a graphic processing unit, a neural network processing unit ( NPU: neural processing unit (NPU), image signal processor, sensor hub processor, or communication processor). For example, when the electronic device 101 includes the main processor 121 and the auxiliary processor 123, the auxiliary processor 123 may use less power than the main processor 121 or be set to be specialized for a designated function. can The secondary processor 123 may be implemented separately from or as part of the main processor 121 .

The secondary processor 123 may, for example, take the place of the main processor 121 while the main processor 121 is in an inactive (eg, sleep) state, or the main processor 121 is active (eg, running an application). ) state, together with the main processor 121, at least one of the components of the electronic device 101 (eg, the display module 160, the sensor module 176, or the communication module 190) It is possible to control at least some of the related functions or states. According to one embodiment, the auxiliary processor 123 (eg, image signal processor or communication processor) may be implemented as part of other functionally related components (eg, camera module 180 or communication module 190). there is. According to an embodiment, the auxiliary processor 123 (eg, a neural network processing device) may include a hardware structure specialized for processing an artificial intelligence model. AI models can be created through machine learning. Such learning may be performed, for example, in the electronic device 101 itself where artificial intelligence is performed, or may be performed through a separate server (eg, the server 108). The learning algorithm may include, for example, supervised learning, unsupervised learning, semi-supervised learning or reinforcement learning, but in the above example Not limited. The artificial intelligence model may include a plurality of artificial neural network layers. Artificial neural networks include deep neural networks (DNNs), convolutional neural networks (CNNs), recurrent neural networks (RNNs), restricted boltzmann machines (RBMs), deep belief networks (DBNs), bidirectional recurrent deep neural networks (BRDNNs), It may be one of deep Q-networks or a combination of two or more of the foregoing, but is not limited to the foregoing examples. The artificial intelligence model may include, in addition or alternatively, software structures in addition to hardware structures.

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

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

The input module 150 may receive a command or data to be used by a component (eg, the processor 120) of the electronic device 101 from the outside of the electronic device 101 (eg, a user). The input module 150 may include, for example, a microphone, a mouse, a keyboard, a key (eg, a button), or a digital pen (eg, a stylus pen).

The sound output module 155 may output sound signals to the outside of the electronic device 101 . The sound output module 155 may include, for example, a speaker or a receiver. The speaker can be used for general purposes such as multimedia playback or recording playback. A receiver may be used to receive an incoming call. According to one embodiment, the receiver may be implemented separately from the speaker or as part of it.

The display module 160 may visually provide information to the outside of the electronic device 101 (eg, a user). The display module 160 may include, for example, a display, a hologram device, or a projector and a control circuit for controlling the device. According to one embodiment, the display module 160 may include a touch sensor set to detect a touch or a pressure sensor set to measure the intensity of force generated by the touch.

The audio module 170 may convert sound into an electrical signal or vice versa. According to one embodiment, the audio module 170 acquires sound through the input module 150, the sound output module 155, or an external electronic device connected directly or wirelessly to the electronic device 101 (eg: Sound may be output through the electronic device 102 (eg, a speaker or a headphone).

The sensor module 176 detects an operating state (eg, power or temperature) of the electronic device 101 or an external environmental state (eg, a user state), and generates an electrical signal or data value corresponding to the detected state. can do. According to one embodiment, the sensor module 176 may include, for example, a gesture sensor, a gyro sensor, an air pressure sensor, a magnetic sensor, an acceleration sensor, a grip sensor, a proximity sensor, a color sensor, an IR (infrared) sensor, a bio sensor, It may include a temperature sensor, humidity sensor, or light sensor.

The interface 177 may support one or more designated protocols that may be used to directly or wirelessly connect the electronic device 101 to an external electronic device (eg, the electronic device 102). According to 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.

The connection terminal 178 may include a connector through which the electronic device 101 may be physically connected to an external electronic device (eg, the 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 (eg, a headphone connector).

The haptic module 179 may convert electrical signals into mechanical stimuli (eg, vibration or motion) or electrical stimuli that a user may perceive through tactile or kinesthetic senses. According to one embodiment, the haptic module 179 may include, for example, a motor, a piezoelectric element, or an electrical stimulation device.

The camera module 180 may capture still images and moving images. According to one embodiment, the camera module 180 may include one or more lenses, image sensors, image signal processors, or flashes.

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

The battery 189 may supply power to at least one component of the electronic device 101 . According to one embodiment, the battery 189 may include, for example, a non-rechargeable primary cell, a rechargeable secondary cell, or a fuel cell.

The communication module 190 is a direct (eg, wired) communication channel or a wireless communication channel between the electronic device 101 and an external electronic device (eg, the electronic device 102, the electronic device 104, or the server 108). Establishment and communication through the established communication channel may be supported. The communication module 190 may include one or more communication processors that operate independently of the processor 120 (eg, an application processor) and support direct (eg, wired) communication or wireless communication. According to one embodiment, the communication module 190 is a wireless communication module 192 (eg, 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 (eg, : a local area network (LAN) communication module or a power line communication module). Among these communication modules, a corresponding communication module is a first network 198 (eg, a short-range communication network such as Bluetooth, wireless fidelity (WiFi) direct, or infrared data association (IrDA)) or a second network 199 (eg, legacy It may communicate with the external electronic device 104 through a cellular network, a 5G network, a next-generation communication network, the Internet, or a telecommunications network such as a computer network (eg, a LAN or a WAN). These various types of communication modules may be integrated as one component (eg, a single chip) or implemented as a plurality of separate components (eg, multiple chips). The wireless communication module 192 uses subscriber information (eg, International Mobile Subscriber Identifier (IMSI)) stored in the subscriber identification module 196 within a communication network such as the first network 198 or the second network 199. The electronic device 101 may be identified or authenticated.

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

The antenna module 197 may transmit or receive signals or power to the outside (eg, 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 (eg, PCB). According to one embodiment, the antenna module 197 may include a plurality of antennas (eg, 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 is selected from the plurality of antennas by the communication module 190, for example. can be chosen A signal or power may be transmitted or received between the communication module 190 and an external electronic device through the selected at least one antenna. According to some embodiments, other components (eg, a radio frequency integrated circuit (RFIC)) may be additionally created as a part of the antenna module 197 in addition to the radiator.

According to various embodiments, the antenna module 197 may generate a mmWave antenna module. According to one embodiment, the mmWave antenna module includes a printed circuit board, an RFIC disposed on or adjacent to a first surface (eg, a lower surface) of the printed circuit board and capable of supporting a designated high frequency band (eg, mmWave band); and a plurality of antennas (eg, array antennas) disposed on or adjacent to a second surface (eg, a top surface or a side surface) of the printed circuit board and capable of transmitting or receiving signals of the designated high frequency band. can do.

At least some of the components are connected to each other through a communication method between peripheral devices (eg, a bus, general purpose input and output (GPIO), serial peripheral interface (SPI), or mobile industry processor interface (MIPI)) and signal ( e.g. commands or data) can be exchanged with each other.

According to an embodiment, commands or data may be transmitted or received between the electronic device 101 and the external electronic device 104 through the server 108 connected to the second network 199 . Each of the external electronic devices 102 or 104 may be the same as or different from the electronic device 101 . According to an embodiment, all or part of operations executed in the electronic device 101 may be executed in one or more external electronic devices among the external electronic devices 102 , 104 , or 108 . For example, when the electronic device 101 needs to perform a certain function or service automatically or in response to a request from a user or another device, the electronic device 101 instead of executing the function or service by itself. Alternatively or additionally, one or more external electronic devices may be requested to perform the function or at least part of the service. One or more external electronic devices receiving the request may execute at least a part of the requested function or service or an additional function or service related to the request, and deliver the execution result to the electronic device 101 . The electronic device 101 may provide the result as at least part of a response to the request as it is or additionally processed. To this end, for example, cloud computing, distributed computing, mobile edge computing (MEC), or client-server computing technology may be used. The electronic device 101 may provide an ultra-low latency service using, for example, distributed computing or mobile edge computing. In another embodiment, the external electronic device 104 may include an internet of things (IoT) device. Server 108 may be an intelligent server using machine learning and/or neural networks. According to one embodiment, the external electronic device 104 or server 108 may be included in the second network 199 . The electronic device 101 may be applied to intelligent services (eg, smart home, smart city, smart car, or health care) based on 5G communication technology and IoT-related technology.

2A is a block diagram 200 of an electronic device 101 for supporting legacy network communication and 5G network communication, according to various embodiments. Referring to FIG. 2A, the electronic device 101 includes a first communication processor 212, a second communication processor 214, a first radio frequency integrated circuit (RFIC) 222, a second RFIC 224, and a third RFIC 226, fourth RFIC 228, first radio frequency front end (RFFE) 232, second RFFE 234, first antenna module 242, second antenna module 244, third An antenna module 246 and antennas 248 may be included. The electronic device 101 may further include a processor 120 and a memory 130 . The second network 199 may include a first cellular network 292 and a second cellular network 294 . According to another embodiment, the electronic device 101 may further include at least one of the components illustrated in FIG. 1 , and the second network 199 may further include at least one other network. According to one embodiment, a first communication processor 212, a second communication processor 214, a first RFIC 222, a second RFIC 224, a fourth RFIC 228, a first RFFE 232, and the second RFFE 234 may form at least a portion of the wireless communication module 192 . According to another embodiment, the fourth RFIC 228 may be omitted or included as part of the third RFIC 226 .

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

The first communication processor 212 may transmit and receive data with the second communication processor 214 . For example, data classified as being transmitted through the second cellular network 294 may be changed to be transmitted through the first cellular network 292 . In this case, the first communication processor 212 may receive transmission data from the second communication processor 214 . For example, the first communication processor 212 may transmit and receive data through the second communication processor 214 and the inter-processor interface 213 . The processor-to-processor interface 213 may be implemented as, for example, a universal asynchronous receiver/transmitter (UART) (eg, HS-high speed-UART (HS-UART) or a peripheral component interconnect bus express (PCIe) interface), but the 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 communication processor 212 may transmit and receive various types of information such as sensing information, information on output strength, and resource block (RB) allocation information with the second communication processor 214 .

Depending on the implementation, the first communications processor 212 may not be directly coupled to the second communications processor 214 . In this case, the first communication processor 212 may transmit and receive data through the second communication processor 214 and the processor 120 (eg, 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 (eg, application processor) through an HS-UART interface or a PCIe interface, but the interface There are no restrictions on types. 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 (eg, an application processor). .

According to one embodiment, the first communication processor 212 and the second communication processor 214 may be implemented on a single chip or in a single package. According to various embodiments, the first communication processor 212 or the second communication processor 214 may be formed in a single chip or single package with the processor 120, coprocessor 123, or communication module 190. there is. For example, as shown in FIG. 2B , the communication processor 440 may support functions for communication with both the first cellular network 292 and the second cellular network 294 .

The first RFIC 222, when transmitted, transmits a baseband signal generated by the first communication processor 212 to about 700 MHz to about 700 MHz used in the first cellular network 292 (eg, a legacy network). It can be converted into a radio frequency (RF) signal at 3 GHz. In reception, an RF signal is obtained from a first network 292 (eg, a legacy network) via an antenna (eg, first antenna module 242), and via an RFFE (eg, first RFFE 232). It can be preprocessed. The first RFIC 222 may convert the preprocessed RF signal into a baseband signal to be processed by the first communication processor 212 .

The second RFIC 224 uses the baseband signal generated by the first communication processor 212 or the second communication processor 214 to the second cellular network 294 (eg, a 5G network) during transmission. It can be converted into an RF signal (hereinafter referred to as a 5G Sub6 RF signal) of a Sub6 band (eg, about 6 GHz or less). At reception, a 5G Sub6 RF signal is obtained from a second cellular network 294 (eg, a 5G network) through an antenna (eg, the second antenna module 244), and an RFFE (eg, the second RFFE 234) ) can be pretreated through. The second RFIC 224 may convert the preprocessed 5G Sub6 RF signal into a baseband signal to be processed by a corresponding communication processor among the first communication processor 212 and the second communication processor 214 .

The third RFIC 226 transmits the baseband signal generated by the second communication processor 214 to the 5G Above6 band (eg, about 6 GHz to about 60 GHz) to be used in the second cellular network 294 (eg, a 5G network). It can be converted into an RF signal (hereinafter referred to as 5G Above6 RF signal). Upon reception, the 5G Above6 RF signal may be obtained from the second cellular network 294 (eg, 5G network) via an antenna (eg, antenna 248) and preprocessed via a third RFFE 236. The third RFIC 226 may convert the preprocessed 5G Above6 RF signal into a baseband signal to be processed by the second communication processor 214 . According to one embodiment, the third RFFE 236 may be formed as part of the third RFIC 226 .

The electronic device 101, according to one embodiment, may include a fourth RFIC 228 separately from or at least as part of the third RFIC 226. In this case, the fourth RFIC 228 converts the 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 (eg, about 9 GHz to about 11 GHz). After conversion, the IF signal may be transmitted to the third RFIC 226. The third RFIC 226 may convert the IF signal into a 5G Above6 RF signal. Upon reception, a 5G Above6 RF signal may be received from a second cellular network 294 (eg, a 5G network) via an antenna (eg, antenna 248) and converted to an IF signal by a third RFIC 226. there is. The fourth RFIC 228 may convert the IF signal into a baseband signal so that the second communication processor 214 can process it.

According to one embodiment, the first RFIC 222 and the second RFIC 224 may be implemented as a single chip or at least part of a single package. According to various embodiments, when the first RFIC 222 and the second RFIC 224 in FIG. 2A or 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 is connected to the first RFFE 232 and the second RFFE 234 to convert the baseband signal into a signal of a band supported by the first RFFE 232 and/or the second RFFE 234, , The converted signal may be transmitted 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 a single chip or at least part of a single package. According to one embodiment, at least one antenna module 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 a plurality of corresponding bands.

According to one embodiment, third RFIC 226 and antenna 248 may be disposed on the same substrate to form third antenna module 246 . For example, the wireless communication module 192 or processor 120 may be disposed on a first substrate (eg, main PCB). In this case, the third RFIC 226 is provided on a part (eg, lower surface) of the second substrate (eg, sub PCB) separate from the first substrate, and the antenna 248 is placed on another part (eg, upper surface). is disposed, the third antenna module 246 may be formed. By arranging 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, for example, can reduce loss (eg, attenuation) of a signal of a high frequency band (eg, about 6 GHz to about 60 GHz) used in 5G network communication by a transmission line. As a result, the electronic device 101 can improve the quality or speed of communication with the second network 294 (eg, 5G network).

According to an example, antenna 248 may be formed as an antenna array comprising a plurality of antenna elements that may be used for beamforming. In this case, the third RFIC 226 may include, for example, a plurality of phase shifters 238 corresponding to a plurality of antenna elements as part of the third RFFE 236 . During transmission, each of the plurality of phase shifters 238 may convert the phase of a 5G Above6 RF signal to be transmitted to the outside of the electronic device 101 (eg, a base station of a 5G network) through a corresponding antenna element. . Upon reception, each of the plurality of phase shifters 238 may convert the phase of the 5G Above6 RF signal received from the outside through the corresponding antenna element into the same or substantially the same phase. This enables transmission or reception through beamforming between the electronic device 101 and the outside.

The second cellular network 294 (eg, 5G network) may be operated independently (eg, SA (Stand-Alone)) or connected to the first cellular network 292 (eg, a legacy network). Example: Non-Stand Alone (NSA). For example, a 5G network may include only an access network (eg, a 5G radio access network (RAN) or a next generation RAN (NG RAN)) and no core network (eg, a next generation core (NGC)). In this case, after accessing the access network of the 5G network, the electronic device 101 may access an external network (eg, the Internet) under the control of a core network (eg, evolved packed core (EPC)) of the legacy network. Protocol information for communication with the legacy network (eg LTE protocol information) or protocol information for communication with the 5G network (eg New Radio (NR) protocol information) is stored in the memory 230, and other parts (eg processor 120 , the first communications processor 212 , or the second communications processor 214 .

Meanwhile, the processor 120, the communication processor (eg, at least one of the first communication processor 212, the second communication processor 214, or the integrated communication processor 260) is an integrated circuit. It may be implemented, in which case it may include at least one storage circuit for storing at least one instruction causing execution of an operation by various embodiments and at least one processing circuit for executing the at least one instruction.

Figure 3a shows a 5G system architecture. 3b shows a 5G network slice structure. Hereinafter, an overall 5G system will be described with reference to FIGS. 3A and 3B, and a network slice will be described.

As shown in FIG. 3A, the 5G system structure includes an electronic device 101 (e.g., a user equipment (UE)) as network elements, a (R) AN (Radio Access Network) 302, and a data network (Data Network, DN). ) 345 and a plurality of network functions (Network Functions, NFs) inside the Core Network (CN).

In the 5G system structure, functions, connection points, and protocols can be defined for each of a plurality of NFs, and a reference point representing a service-based interface corresponding to the NFs and a reference point representing interactions between NFs ( A 5G system structure may be shown using a reference point).

A plurality of network functions (NF) include an Authentication Server Function (AUSF) (309), an Access and Mobility Management Function (AMF) (303), and a Network Exposure Function (Network Exposure Function). , NEF) (347), Network Function Repository Function (NRF) (305), Policy Control Function (PCF) (307), Session Management Function (SMF) (341), Unified Data Management (UDM) (306), User Plane Function (UPF) (342) and Application Function (AF) (346), Network Slice Selection Function , NSSF) (304).

In various embodiments of the present disclosure, AMF, SMF, PCF, and UPF are key to Protocol Data Unit (PDU) (“UE-requested PDU”) session establishment and traffic management between the UE and the DN requested by the user device. can play a negative role.

A reference point between the electronic device 101 and the AMF 303 is defined as N1.

(R)AN 302 may represent a base station using Radio Access Technology (RAT). For example, AN 302 can be a base station that includes a 3GPP access technology or a base station that includes a non-3GPP access technology such as Wi-Fi. A reference point between the AN 302 and the AMF 303 is defined as N2, and a reference point between the AN and the UPF 342 is defined as N3.

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

The AMF 303 may provide an access technology-independent, eg, electronic device 101 unit access and mobility management function. The reference point between the AMF 303 and the electronic device 101 is defined as N1, the reference point between the AMF 303 and the (R) AN 302 is defined as N2, and the AMF 303 and the UDM 306 are defined as N2. The reference point is defined as N8, the reference point between the AMF 303 and the AUSF 309 is defined as N12, and the reference point between the AMF 303 and the SMF 341 is defined as N11.

The SMF 341 may provide a session management function for managing each session by assigning a different SMF to each session when one electronic device 101 has multiple sessions. N4 reference points are defined so that the UPF 342 can be set using the control signal information generated by the SMF 341 and the UPF 342 can report its status to the SMF 341. The reference point between SMF (341) and AMF (303) is defined as N11, the reference point between SMF (341) and UDM (306) is defined as N10, and the reference point between SMF (341) and PCF (305) is defined as N7 , and the reference point between the SMF 341 and the AMF 303 is defined as N11.

For example, while each electronic device 101 can be connected to one AMF 303, in the case of the SMF 341, since one electronic device 101 can establish multiple sessions, a different SMF for each session (311, 321, 331).

The AF 346 may provide information on a packet flow to the PCF 307 in charge of policy control in order to guarantee Quality of Service (QoS).

The PCF 307 determines policies such as session management and mobility management based on information on packet flow to ensure QoS, and transfers them to the AMF 303 and SMF 341 to provide appropriate mobility management, session management, and QoS. At least one of the management can be performed. A reference point between AF 346 and PCF 307 is defined as N5.

The AUSF 309 may store data for authentication of the electronic device 101 .

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

The CP functions include various functions to control the network and the terminal, and include the electronic device 101, (R)AN 302, UPF 342, and AMF in charge of mobility management function, which are two representative functions. 303, AF 346, DN 345 and SMF 341 in charge of session management functions can be included in CP functions as two independent functions.

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

A mobile communication service provider may allocate network resources suitable for a corresponding service for each slice or for each set of specific slices. The network resource may mean at least one of a network function (NF), a logical resource provided by the network function (NF), or radio resource allocation.

Network slicing is the property of at least one of network isolation, customization, and independent management and orchestration by bundling network resources and network functions into one independent slice according to service. It is a technology that can be applied to the mobile communication core network structure.

Network slicing is a new concept in the 5G core network. The network slicing is a technique of providing network resources and network functions necessary for a service requested by a mobile terminal in one independent slice.

Through network slicing, network operators can independently allocate network resources specific to each service and user, and resource virtualization based on software defined networking (SDN) and network function virtualization (NFV) technologies. By securing the flexibility of the network through, it is possible to secure the scalability and reliability of service and network resource management.

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

The electronic device 101 may access a network and simultaneously or sequentially receive a service from at least one of a plurality of slice instances.

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

Referring to FIGS. 3A and 3B , the SMF 321 of the slice instance 2 320 may be connected to the PCF 307 of the PLMN level and the PCF 323 of the slice level. The PLMN level PCF 307 may manage and provide the PLMN level policy information to the SMF 321 . The slice level PCF 323 belonging to slice instance 2 may manage a policy required to provide the corresponding slice and provide corresponding information to the SMF 321 .

Each slice may be identified by a slice ID. For example, the slice ID may be Single-Network Slice Selection Assistance Information (S-NSSAI) defined in 3GPP. According to various embodiments, the electronic device 101 may store information about Configured Network Slice Selection Assistance Information (Configured NSSAI) and Network Slice Selection Policy (NSSP). . The configured network slice selection assistance information (Configured NSSAI) may be configured as a list of S-NSSAIs of network slices to which the electronic device 101 has joined the Home PLMN (HPLMN). The list of S-NASSAI may include at least one S-NSSAI #id. For example, the S-NASSAI list may include S-NASSAI #a, S-NASSAI #b, S-NASSAI #c, and S-NASSAI #d. Since the Configured NSSAI is determined based on the subscription information of the electronic device 101, the S-NSSAI constituting the Configured NSSAI may be different for each electronic device 101. In addition, since the Configured NSSAI is determined based on the subscription information of the electronic device 101, if the subscription information of the electronic device 101 is changed, the Configured NSSAI stored in the electronic device 101 may also be changed. The S-NSSAI list to which the electronic device 101 constituting the Configured NSSAI is subscribed may be stored in the unified UDM 306 that stores subscription information of the electronic device 101 . The S-NSSAI stored in the UDM 306 and subscribed to by the electronic device 101 may be referred to as 'Subscribed S-NSSAI'. The network slice selection policy (NSSP) indicates mapping information between an S-NSSAI (S-NSSAI #id) to which the electronic device 101 has subscribed and an application that the corresponding S-NSSAI can support. One S-NSSAI #id may be mapped to at least one application. For example, S-NASSAI #a maps to App #1 and App #2, S-NASSAI #b maps to App #1, S-NASSAI #c maps to App #3, and S-NASSAI #b maps to App #3. # can be mapped to all supported applications. The NSSP may be stored in a policy control function (PCF) that stores policy information related to the electronic device 101 and the network. Alternatively, the NSSP is stored in the User Data Repository (UDR), and the PCF may obtain the NSSP information from the UDR by requesting NSSP information from the UDR as needed. When there is a change in subscription information of the electronic device 101, a change may occur in information about subscribed S-NSSAIs of the electronic device 101 stored in the UDM 306. When the subscription information of the electronic device 101 is changed, NSSP information stored in the PCF or UDR may be changed. When a change occurs in at least one of subscribed S-NSSAIs and NSSP, related configuration information stored in the electronic device 101 may also need to be updated.

4A is a diagram illustrating a traffic allowance period according to various embodiments. The embodiment of FIG. 4A will be described with reference to FIG. 4B. 4B is a diagram illustrating a PDU session between an electronic device and a network according to various embodiments.

According to various embodiments, the electronic device 101 (eg, at least a portion of the processor 120, the first communication processor 212, the second communication processor 214, or the integrated communication processor 260), A URSP rule shown in Table 1 may be obtained from a network (eg, PCF), for example.

rule number rule precedence traffic descriptor path selection descriptor One One App Descriptor = AppID1 Precedence = 1 S-NSSAI = 101
SSC Mode = 2 2 2 App Descriptor = AppID1 [RSD(route selection descriptor) I]
Precedence = 1
S-NSSAI = 102, SSC Mode = 2
Time Window = TimeVal_a1 ~ TimeVal_a2
Location Criteria = Location_a [RSD 2]
Precedence = 2
S-NSSAI = 103, DNN = internet.mno.com
SSC Mode = 1
Time Window = TimeVal_b1 ~ TimeVal_b2
Location Criteria = Location_b 3 3 * (match all) Precedence = 1
S-NSSAI = 1
DNN = internet.mno2.com

Referring to Table 1, in rule number "1" of the URSP rules, the traffic descriptor may include information that the application descriptor is AppID1, and in the path selection descriptor, precedence is 1, S-NSSAI is 101, , information indicating that the SSC mode is 2 may be included. For example, when a network connection request (eg, requestNetwork) is confirmed from an application of AppID1, the electronic device 101 uses at least the path selection descriptor of the URSP rule of rule number “1” to establish a PDU session. One action can be performed. In rule number "2" of the URSP rules, information indicating that the application descriptor is AppID2 may be included in the traffic descriptor. In rule number "3" of the URSP rules, the application descriptor is unlimited in the traffic descriptor (for example, match all), and in the route selection descriptor, precedence is 1, S-NSSAI is 1, and DNN is internet.mno2 It may include information such as .com. For example, if a network connection request is confirmed from an application that does not correspond to the traffic descriptor of rule number “1” and rule number “2”, the electronic device 101 selects the path selection descriptor of the URSP rule of rule number “3” At least one operation for establishing a PDU session may be performed using

Meanwhile, a plurality of (eg, two) path selection descriptors (eg, RSD1 and RSD2) may be set corresponding to one traffic descriptor. In one path selection descriptor (eg, RSD1), precedence is 1, S-NSSAI is 102, and SSC mode is 2, along with time information (eg, Time Window) at the first point in time ( For example, TimeVal_a1) to the second time point (eg, TimeVal_a2), and the place information (eg, Location Criteria) may include the first point (eg, Location_a). In another path selection descriptor (eg RSD2), time information (eg, precedence is 2, S-NSSAI is 103, DNN is internet.mno.com, SSC mode is 1) Time Window) is the third point (eg, TimeVal_b1) to the fourth point (eg, TimeVal_b2), and the location information (eg, Location Criteria) includes the second point (eg, Location_b). can Time information (eg, Time Window) in the example may be expressed in a 64-bit NTP timestamp format, but the expression format is not limited. Location information (eg, Location Criteria) in the example may be expressed as TA (tacking area) and/or cell information, but the expression format is not limited. For example, if time information and/or location information are included in one route selection descriptor (eg, RSD1), time information and/or location information may also be included in another route selection descriptor (eg, RSD2). may be requested. The electronic device 101 checks the current time information and/or current place information, and when the checked time information and/or the checked place information corresponds to the time information and/or place information included in the route selection descriptor. , it can be confirmed that the corresponding URSP rule is valid. If the checked time information and/or checked place information does not correspond to the time information and/or place information included in the path selection descriptor, the electronic device 101 determines that the corresponding URSP rule is invalid. You can check.

For example, referring to FIGS. 4A and 4B , time points t2 to t4 may be time information (eg, Time Window) 431 included in the path selection descriptor of the URSP rule. In addition, the location of location A may be location information (eg, location criteria) 432 included in the path selection descriptor of the URSP rule. For example, the corresponding PDU session 412 (or network slice) is for a specific event (eg, AAA live concert) according to an agreement between a mobile network operator (MNO) and a service provider. can be set. An entity (eg, PCF) of a network corresponding to the MNO may share a URSP rule according to the agreement with user devices. At time t2, the MNO is required to perform network slice provisioning, the service provider is required to prepare a service, and the user may be required to connect to the network slice and connect to the service. The electronic device 101 can confirm that the corresponding URSP rule is valid during times t2 to t4, and can confirm that the corresponding URSP rule is not valid during a period other than times t2 to t4. On the other hand, those skilled in the art will understand that this assumes that conditions associated with place information are satisfied. At time t4, the MNO is requested to destroy the network slice, the service provider is requested to terminate the service, and the user is required to terminate the connection to the network slice and terminate the use of the service. there is.

For example, when the application provides a network connection request at time t3 including time t2 to time t4, the electronic device 101 determines that the URSP rule is valid at the time of checking the network connection request, and determines that the URSP rule is valid. A PDU session 412 may be established based on the path selection descriptor of the rule. Accordingly, the electronic device 101 may transmit and/or receive the traffic 422 with the second server 424 using the PDU session 412 specially established in response to the corresponding event. Meanwhile, when the application provides a network connection request at time t1, which is included in a period other than time t2 to time t4, the electronic device 101 can confirm that the URSP rule is invalid at the time of checking the network connection request. there is. In this case, the electronic device 101 establishes the PDU session 411 based on the path selection descriptor of another valid URSP rule, and uses the PDU session 411 to transfer the traffic 421 to and from the first server 423. transmit and/or receive. For example, a first server 423 corresponding to the PDU session 411 and a second server 424 corresponding to the PDU session 412 may be established for one application 401 . Meanwhile, in FIG. 4B, the first server 423 and the second server 424 are represented as different entities, but this is exemplary, and the first server 423 and the second server 424 are physically separate entities. may be, or may be logically divided servers within one physical entity, or may be implemented as one server according to circumstances. Accordingly, the electronic device 101 may not be able to use the PDU session 412 specially set in response to the corresponding event. If information that the URSP rule is valid or information related to the validity of the URSP rule (eg, time information and / or location information of the path selection descriptor) is not previously transmitted to the application, the application It cannot be guaranteed to provide network connection requests during this period. The electronic device 101 according to various embodiments may provide a notification to an application based on the satisfaction of a condition associated with time information and/or location information included in a URSP rule, and in response thereto When a network connection request is confirmed from an application, a PDU session may be established.

4C is a diagram illustrating PDU session establishment according to a location of an electronic device according to various embodiments.

According to various embodiments, the electronic device 101 (eg, at least a portion of the processor 120, the first communication processor 212, the second communication processor 214, or the integrated communication processor 260), It can be located within the coverage 481a of the first cell 481 and can access the first cell 481 . The electronic device 101 may establish a first PDU session 491 with the network 400 in a state of being connected to the first cell 481 . Meanwhile, for convenience of description, the first cell 481 (eg, RU) is shown as not part of the network 400, but this is only for description, and the first cell 481 is also a network It will be understood by those skilled in the art that it may constitute at least part of 400 . The electronic device 101 may establish a first PDU session 491 based on a URSP rule having the highest priority among at least one effective URSP rule in a state of accessing the first cell 481 . The electronic device 101 may transmit and/or receive traffic with the first server 423 through the first PDU session 491 . Meanwhile, the electronic device 101 may move within the coverage 482a of the second cell 482 . The electronic device 101 may perform at least one procedure for handover from the first cell 481 to the second cell 482, and thus access the second cell 482. The electronic device 101 can confirm that the location information associated with the second cell 482 corresponds to the location information of the path selection descriptor of the URSP rule. The electronic device 101 may provide a notification to an application corresponding to a path selection descriptor of corresponding place information. Meanwhile, those skilled in the art will understand that when time information is further included in the path selection descriptor of the URSP rule in addition to place information, it is assumed that the condition associated with the time information is also satisfied. The electronic device 101 may establish a second PDU session 492 based on a corresponding URSP rule based on confirmation of the network connection request corresponding to the notification. The electronic device 101 may transmit and/or receive traffic with the second server 424 through the second PDU session 492 . Accordingly, the electronic device 101 transmits and/or receives traffic using the second PDU session 492 specially configured in a specific place (eg, accessing a specific cell and/or located in a specific TA). can be done The electronic device 101 may perform establishment of a PDU session based on a request for network connection as a response to providing a notification for an application and a response to the notification, so that establishment of a second PDU session at a specific place may be missed (missing). ) can reduce the likelihood of

5 is a flowchart illustrating an operating method of an electronic device according to various embodiments.

According to various embodiments, the electronic device 101 (eg, at least a portion of the processor 120, the first communication processor 212, the second communication processor 214, or the integrated communication processor 260), In operation 501, a URSP rule including at least one traffic descriptor and at least one path selection descriptor may be obtained. In operation 503, the electronic device 101 corresponds to first time information and/or first place information included in a first route selection descriptor among at least one route selection descriptor, in operation 503 . can confirm that it is. For example, when the first time information included in the first path selection descriptor is time t1 to time t2 and the time identified as the current time is time t3, the electronic device as time t3 is included in time t1 to time t2 (101) can confirm that the checked time corresponds to the first time information included in the first path selection descriptor. If time t3 is not included in time t1 to time t2, the electronic device 101 may confirm that the checked time does not correspond to the first time information included in the first path selection descriptor. For example, when the first place information included in the first path selection descriptor is first cell identification information, the electronic device 101 is the first cell identification information as the identification information of the cell currently accessed by the electronic device 101 ( 101) may confirm that the checked place corresponds to the first place information included in the first path selection descriptor. If the identification information of the cell currently accessed by the electronic device 101 is not the first cell identification information, the electronic device 101 corresponds to the first place information included in the first path selection descriptor. You can confirm that it doesn't. For example, if the first place information included in the first path selection descriptor is the first TA, the electronic device 101 is the confirmed place because the current TA including the electronic device 101 is the first TA. It can be confirmed that it corresponds to the first place information included in the first path selection descriptor. If the current TA including the electronic device 101 is not the first TA, the electronic device 101 may confirm that the checked place does not correspond to the first place information included in the first route selection descriptor. .

According to various embodiments, in operation 505, the electronic device 101 may provide a notification to the first application identified by the first traffic descriptor corresponding to the first path selection descriptor. For example, AppID may be included in the first traffic descriptor, and the electronic device 101 may identify the first application using the AppID. The notification includes, for example, information included in the first traffic descriptor (eg, application descriptor, internet protocol (IP) descriptor, IP descriptor, domain descriptor (eg, At least some of a fully qualified domain name (FQDN), a non-IP descriptor, a data network name (DNN), and connection capabilities) may be included, but is not limited thereto. A method of providing notification to the first application may be, for example, an IPC-based method, a callback-based method, a socket-based method, an intent-based method, or a message-based method, but those skilled in the art are not limited to the type. will understand In operation 507, the electronic device 101 may perform at least one operation for establishing a PDU session based on the first path selection descriptor based on confirmation of the network connection request from the first application. In one example, an application may be configured to provide a network connection request in response to receiving a notification. In this case, the application may not require an additional event other than the notification reception to provide the network connection request. In another example, the application may be configured to provide a UI for user input in response to receiving a notification or to request UI provision from another entity (eg, a notification manager). When input from the user based on the UI is confirmed, the application may provide a network connection request. For example, the network connection request may include at least a part of information included in the notification. In the above example, since at least some of the information included in the first traffic descriptor may be included in the notification, at least some of the information included in the first traffic descriptor may be included in the network connection request. At least one operation for establishing a PDU session, which will be described later, may include, for example, at least transmission of a PDU session establishment request message and reception of a PDU session establishment acknowledgment message.

6 is a diagram illustrating a configuration of an event table according to various embodiments.

According to various embodiments, the electronic device 101 (eg, at least a portion of the processor 120, the first communication processor 212, the second communication processor 214, or the integrated communication processor 260), The URSP rules 600 may be obtained, for example, from the network. The URSP rule 600 may include a rule precedence 601, a traffic descriptor 610, and a path selection descriptor list 620. The traffic descriptor 610 includes an application descriptor (eg, AppID) 611, an IP descriptor or a non-IP descriptor 612, an FQDN(s) 613, A DNN 614 and connection capabilities 615 may be included. AppID is an ID for distinguishing between an OS and an App from a business operator, and may be set based on OS information and/or App package information, but is not limited thereto. The path selection descriptor list 620 may include a plurality of path selection descriptors 621 , 622 , 623 , and 624 . For example, in one path selection descriptor 622, Precedence 622a of "Priority", "SCC mode", "NS selection", components 622b of DNN, Time Window and Location Criteria validity Validation criteria 622c may be included.

According to various embodiments, the electronic device 101 may configure the event table 640 based on the URSP rule 600 . The event table 640 may include an event identifier (Event ID) 650 . The event identifier 650 may include, for example, an application descriptor (eg, AppID) and metadata. Here, the metadata may include at least some of information other than the application descriptor among the traffic descriptors. For example, in one of the traffic descriptors, AppID1 and other information may be stored in correspondence with each other, and the electronic device 101 associates AppID1 651a and Meta1 652a based on the corresponding traffic descriptor to generate the first event ID can be configured. Meta1 652a may include at least some of the remaining information of the traffic descriptor. For example, in one of the other traffic descriptors, AppID2 and other information may be stored in correspondence with each other, and the electronic device 101 associates AppID2 651b and Meta1 652b based on the other traffic descriptor to obtain a second traffic descriptor. The event ID is configurable. Meta1 652b may include at least some of the remaining information of the other traffic descriptor, and in the example of FIG. 6, the metadata of the first event ID and the metadata of the second event ID have been described as identical, but this is an example. may differ from one another.

According to various embodiments, the electronic device 101 may configure the priority 660 of the event table 640 based on the priority from the path selection descriptor. Values 661a, 661b, and 661c of the priority 660 of the event table 640 may be values corresponding to each traffic descriptor. Meanwhile, in the example of FIG. 6 , in the URSP rule 660, two path selection descriptors may correspond to traffic descriptors including AppID2. Accordingly, two priorities 661b and 661c may correspond to the second event ID corresponding to AppId2 651b. The electronic device 101 may configure time information 670 of the event table 640 based on time information (eg, time window) from the path selection descriptor. Each of the values 671a, 671b, and 671c of the time information 670 may be a value corresponding to each traffic descriptor. The electronic device 101 may configure location information 680 of the event table 640 based on location information (eg, location criteria) from the path selection descriptor. Each of the values 681a, 681b, and 681c of the location information 680 may be a value corresponding to each traffic descriptor.

According to various embodiments, the electronic device 101 may check whether to provide a notification to an application based on the event table 640 . For example, when the checked current time and/or current location correspond to the time information 670 and/or location information 680 of the event table 640, the electronic device 101 corresponds to the corresponding event ID. Notifications can be provided by applications that do. Meanwhile, the configuration of the event table 640 is merely illustrative, and the electronic device 101 may use the URSP rule 600 to determine whether to provide a notification to the application. The electronic device 101, when the checked current time and/or current location corresponds to the time information and/or location information of the route selection descriptor included in the URSP rule 600, the electronic device 101 generates a corresponding event Notification can be provided with an application corresponding to the ID.

7 is a diagram for describing entities executed in an electronic device according to various embodiments.

According to various embodiments, the network 400 may obtain event information (eg, URI, time information, and/or location information) from the application server 425 in operation 711 . In various embodiments, network 400 may obtain information for an event (eg, URI, time information, and/or location information) from entities other than application server 425 . The network 400 (eg, PCF) may construct a URSP rule based on the information for the event obtained. The electronic device 101 (eg, the processor 120) may execute the URSP manager 708. The URSP manager 708, in operation 721, may obtain URSP rules from the network 400 (eg, PCF). The URSP manager 708 may store and/or manage acquired URSP rules. The URSP manager 708 may transmit and/or receive at least a portion of the connection manager 707 and the URSP rules 728, for example, a mobile data manager (not shown) on behalf of the connection manager 707. city) may transmit and/or receive at least some of the URSP rules 728 with the URSP manager 708 . The URSP event manager 703 may obtain time information and/or location information 725 from the information providing manager 705 . The information providing manager 705 may obtain current time information and/or location information 725 and provide the obtained information to the URSP event manager 703 . The URSP event manager 703 may check an event corresponding to the time information and/or the location information 725 in the stored event table 704 (eg, the event table 640 of FIG. 6 ). The URSP event manager 703 may provide a notification 726 to the application 701a corresponding to the confirmed event. The application 701a may provide a network connection request 727 to the connection manager 728 in response to receiving the notification 726 or in response to a user input confirmed after the notification 726. can At least a part of the traffic descriptor may be included in the network connection request 727 . The connection manager 707 (or mobile data manager) may request a path selection descriptor based on at least a portion of the traffic descriptor from the URSP manager 723, and the URSP manager 723 may, in response, request at least one of the traffic descriptors A path selection descriptor corresponding to a part may be provided to the connection manager 707 (or mobile data manager). The connection manager 707 (or mobile data manager) may request establishment of a PDU session to the communication processor 709 . The communication processor 709 may establish a PDU session 729. For example, the applications 701a, 701b, and 701c, the URSP event manager 703, the information provision manager 705, the connection manager 707, and the URSP manager 708 may be executed by an application processor. Meanwhile, at least one of the applications 701a, 701b, and 701c, the URSP event manager 703, the information provision manager 705, the connection manager 707, and the URSP manager 708 is executed by the communication processor 709. and the rest may be executed by the application processor.

8 is a diagram for describing an operation of an entity executed in an electronic device according to various embodiments.

According to various embodiments, network 400 may provide a URSP rule to communication processor 444 in operation 801 . In operation 803 , the communication processor 444 may provide the URSP rule to the URSP manager 443 . The URSP manager 443 may store and/or manage URSP rules. The URSP manager 443 may provide a path selection descriptor in response to a request for a path selection descriptor based on a network connection request of a specific application later. The URSP manager 443 may provide the URSP rules to the URSP event manager 445 in operation 805 . The URSP event manager 445 may configure an event table (eg, the event table 640) using the provided URSP rules. On the other hand, this is an example, and the URSP event manager 445 may determine whether notification is provided using a URSP rule without configuring an event table. Or, in another example, the URSP manager 443 may use a URSP rule to determine whether notification is provided, and in this case, the URSP event manager 445 may be executed or not defined.

According to various embodiments, the URSP event manager 445, in operation 807, the checked time and/or checked place corresponds to first time information and/or first place information included in the first path selection descriptor. can confirm that it is. Corresponds to the URSP event manager 445 and the first route selection descriptor based on the correspondence of the confirmed time and/or confirmed place to the first time information and/or first place information included in the first route selection descriptor It is possible to identify the application 401 using the first traffic descriptor. For example, the URSP event manager 445 may identify the application 401 based on the AppID included in the first traffic descriptor. Alternatively, the URSP event manager 445 may identify the application 401 based on the AppID included in the event ID corresponding to the first path selection descriptor of the event table (eg, the event table 640). The URSP event manager 445 may provide a notification to the identified application 401 in operation 809 . The notification may include, for example, meta data (eg, at least a part of a traffic descriptor). In response to the notification, the application 401 may provide a network connection request (eg, requestNewtork) to the connection manager 441 in operation 811 . A network connection request may include, for example, metadata. In one example, application 401 may provide a network connection request based on additional confirmation from the user. Alternatively, the application 401 may provide a network connection request in response to receiving the notification. The connection manager 441 may provide a network connection request to the mobile data manager 442 in operation 813 . Based on the reception of the network connection request, the mobile data manager 442 may provide a route selection descriptor request (eg, selectURSPRoute) to the URSP manager 443 in operation 815 . The path selection descriptor request may include, for example, AppID and/or metadata, such as at least part of a traffic descriptor. The URSP manager 443 may check a path selection descriptor corresponding to the path selection descriptor request based on the reception of the path selection descriptor request. For example, the URSP manager 443 may check a path selection descriptor corresponding to AppID and/or metadata included in the path selection descriptor request by using a URSP rule. In operation 817, the USRP manager 443 may provide information (eg, URSPRouteInformation) associated with the path selection descriptor to the mobile data manager 442. Information related to the path selection descriptor may include at least a part of the path selection descriptor. Mobile data manager 442 , in operation 819 , may provide a setup data call request to communications processor 444 . At least a part of the path selection descriptor may be included in the setup data call request. The communication processor 444 may transmit a PDU session establishment request message to the network 400 based on reception of the setup data call request in operation 821 . Based on the reception of the PDU session establishment request message, the network 400 may perform at least one operation for establishing a PDU session. The network 400 may perform at least one operation for establishment of a PDU session and transmit a PDU session establishment accept message to the communication processor 444 in operation 823 . In operation 825 , the communications processor 444 may provide a setup data call response to the mobile data manager 442 . In operation 827 , the mobile data manager 442 may provide a network notification (notifyNewtork) to the connection manager 441 . The connection manager 441 may provide a network notification (notifyNewtork) to the application 401 in operation 829 . The application 401 may transmit and/or receive traffic 833 through the PDU session 831 established thereafter. The application 401 may transmit and/or receive the traffic 833 based on a socket corresponding to the PDU session 831, for example, and transmit the traffic 833 through the PDU session 831. and/or reception. As described above, when conditions associated with time information and/or location information are satisfied, a corresponding PDU session may be established automatically or based on additional confirmation by the user.

9A is a flowchart illustrating a method of operating an electronic device according to various embodiments. The embodiment of FIG. 9A will be described with reference to FIG. 9B. 9B is a diagram for describing a UI provided by an electronic device according to various embodiments.

According to various embodiments, the electronic device 101 (eg, at least a portion of the processor 120, the first communication processor 212, the second communication processor 214, or the integrated communication processor 260), In operation 901, it can be confirmed that the checked time and/or checked place correspond to first time information and/or first place information included in the first path selection descriptor. In operation 903, the electronic device 101 may provide a UI corresponding to the first traffic descriptor and/or the first path selection descriptor. For example, the electronic device 101 may display the UI 925 as shown in FIG. 9B. The UI 925 may include, for example, a notification 927 inquiring whether or not a PDU session is established, and the notification 927 may include text that is easy for a user to understand (eg, "high quality Live The concert starts now. Would you like to access?) For example, the event manager 445 may include the first time information included in the first route selection descriptor for the confirmed time and/or the confirmed place. and/or correspond to the first location information The event manager 445 may provide the notification 921 to the application 401 corresponding to the first traffic descriptor and/or the first route. The application 401 may provide information 923 for constructing the UI 925 including the notification 927 based on the notification 921. In one example, the application 401 may provide information 923 to a notification manager (not shown), and the notification manager (not shown) may provide a UI 925 based on the information 923. Meanwhile, in another embodiment, the electronic device 101 receives additional information (eg, an image file) associated with an event from an application server and configures the UI 925 by using the additional information together. For example, based on reception of the notification, the application 401 may request additional information from the application server. The application 401 may request meta information included in the notification (for example, For example, FQDN) may be used to request additional information from the application server, in response to the request, the application server may provide additional information related to the event to the electronic device 101 (eg, the application 401). The electronic device 101 (eg, the application 401) may use the additional information to configure the UI 925. Again, referring to FIG. 9A, the electronic device 101, In operation 905, it may be checked whether the PDU session establishment command is confirmed through the UI. For example, the electronic device 101, based on the input to the notification 927 of FIG. 9B or an additional input after the input to the notification 927, receives a PDU session establishment command (or application execution command) is acquired. Meanwhile, in FIG. 9B, although the visual UI 925 has been described, this is exemplary, and the UI 925 can be provided in various ways such as an auditory method in addition to the visual method, and the user according to various methods. It can be determined whether the input is also acquired in a corresponding way. If the PDU session establishment command is obtained (905 - Yes), the electronic device 101, in operation 907, may perform at least one operation for establishing a PDU session. If the PDU session establishment command is not obtained (905 - No), the electronic device 101 may refrain from establishing a new PDU session in operation 909. As described above, the user can check whether the PDU session can be established based on the UI 925 provided, and can input a corresponding PDU session establishment command to the electronic device 101 .

9C is a flowchart illustrating a method of operating an electronic device according to various embodiments.

According to various embodiments, the URSP event manager 445 determines that the checked time and/or place in operation 931 corresponds to the first time information and/or first place information included in the first path selection descriptor. You can check. The URSP event manager 445 may check the application 400 corresponding to the first path selection descriptor and/or the first traffic descriptor. The URSP event manager 445 may provide a notification to the checked application 400 in operation 933 . In operation 935, the application 400 may provide a network connection request (eg, requestNetwork) in response to receiving the notification. Based on the network connection request, a PDU session may be established. The application 400 may provide a network connection request in response to receiving a notification without requiring any user confirmation. Accordingly, for example, even when a user cannot check the electronic device 101 at a specific time and/or in a specific place, a PDU session may be automatically established.

10 is a flowchart illustrating a method of operating an electronic device according to various embodiments.

According to various embodiments, the electronic device 101 (eg, at least a portion of the processor 120, the first communication processor 212, the second communication processor 214, or the integrated communication processor 260), In operation 1001, a traffic descriptor and a path selection descriptor included in the URSP rule may be checked. For example, the electronic device 101 may obtain a URSP rule from a network (or another entity), and check a traffic descriptor and a path selection descriptor included in the URSP rule at an acquisition time point (or another time point). there is. In operation 1003, the electronic device 101 may check whether the AppID is included in the traffic descriptor. For example, the electronic device 101 may obtain the URSP rules shown in Table 2.

rule number rule precedence traffic descriptor path selection descriptor One One App Descriptor = AppID2
FQDN = FQDN_1 Precedence = 1
S-NSSAI = 105, DNN = internet.mno4.com
Time Window = TimeVal_d1 ~ TimeVal_d2
Location Criteria = Location_d 2 2 * Precedence = 1
S-NSSAI = 1, DNN = internet.mno2.com

The electronic device 101 may confirm that "AppID2" is included in the traffic descriptor for rule "1". Meanwhile, the electronic device 101 may confirm that "AppID2" is not included in the traffic descriptor for rule "2". In operation 1005, when AppID is included in the traffic descriptor (1003-Yes), the electronic device 101 may configure an event corresponding to the traffic descriptor and the path selection descriptor. When the traffic descriptor does not include the AppID (1003-No), the electronic device 101 may refrain from configuring an event corresponding to the traffic descriptor and the path selection descriptor in operation 1007. For example, the electronic device 101 may configure an event for rule number “1”. Accordingly, the electronic device 101 may provide a notification to the application corresponding to AppID2 when the checked time satisfies the conditions of TimeVal_d1 to TimeVal_d2 and the checked location satisfies “Location_d”. If a network connection request is confirmed from the application corresponding to AppID2, the electronic device 101 may perform at least one operation for establishing a PDU session based on the path selection descriptor of rule "1". Meanwhile, the electronic device 101 may not configure an event for rule number 2. For example, since an application to provide a notification when an event is satisfied is not defined, the electronic device 101 may not configure an event for rule number 2. For example, when a plurality of rules are included in the URSP rule, the electronic device 101 may configure an event for some rules and not configure an event for other rules.

11 is a flowchart illustrating a method of operating an electronic device according to various embodiments.

According to various embodiments, the electronic device 101 (eg, at least a portion of the processor 120, the first communication processor 212, the second communication processor 214, or the integrated communication processor 260), In operation 1101, a first traffic descriptor and a first path selection descriptor may be checked. In operation 1103, the electronic device 101 may confirm that AppID is not included in the first traffic descriptor. For example, the electronic device 101 includes a traffic descriptor of “DNN=internet” and a corresponding traffic descriptor of “Precedence = 1, S-NSSAI = 102, SSC Mode = 2, Time Window = TimeVal_a1 to TimeVal_a2, Location Criteria = Location_a You can check the path selection descriptor of ". Even if AppID is not included in the traffic descriptor, the electronic device 101 may configure events corresponding to the first traffic descriptor and the first path selection descriptor in operation 1105 . In operation 1107, the electronic device 101 may confirm that conditions related to time information and/or place information included in the first path selection descriptor are satisfied. For example, the electronic device 101 may confirm that the checked time is included in TimeVal_a1 to TimeVal_a2 and/or that the checked place is Location_a. In operation 1109, the electronic device 101 may provide a notification to at least one application. In one example, the electronic device 101 may provide notifications for all installed applications or all running applications. In another example, the electronic device 101 may provide a notification to at least one pre-designated application. There are no restrictions on applications for providing notifications.

12 is a flowchart illustrating a method of operating an electronic device according to various embodiments.

According to various embodiments, the electronic device 101 (eg, at least a portion of the processor 120, the first communication processor 212, the second communication processor 214, or the integrated communication processor 260), In operation 1201, a traffic descriptor and a path selection descriptor may be checked. In operation 1203, the electronic device 101 may check whether security information is included in the traffic descriptor. For example, the security information may be an IP address, but the type is not limited. For example, the electronic device 101 may acquire URSP rules as shown in Table 3.

rule number rule precedence traffic descriptor path selection descriptor One One App Descriptor = AppID2
FQDN=FQDN_1 Precedence = 1
S-NSSAI = 102, SSC Mode = 2
Time Window = TimeVal_a1 ~ TimeVal_a2
Location Criteria = Location_a 2 2 App Descriptor = AppID3
IP=10.10.10.1,
port=10040,
protocol = TCP Precedence = 1
S-NSSAI = 104, DNN = internet.mno3.com
SSC Mode = 1
Time Window = TimeVal_c1 ~ TimeVal_c2
Location Criteria = Location_c

The electronic device 101 may confirm that security information (eg, an IP address) is not included in the traffic descriptor for rule “1”. Meanwhile, the electronic device 101 may confirm that security information (eg, an IP address) is included in the traffic descriptor for rule “2”. When security information is not included in the traffic descriptor (1203-No), the electronic device 101 may configure an event corresponding to the traffic descriptor and the path selection descriptor in operation 1205. When security information is included in the traffic descriptor (1203-No), the electronic device 101 may refrain from configuring events corresponding to the traffic descriptor and the path selection descriptor in operation 1207. For example, the electronic device 101 may configure an event for rule number “1”. Accordingly, the electronic device 101 may provide a notification to the application corresponding to AppID2 when the checked time satisfies the conditions of TimeVal_d1 to TimeVal_d2 and the checked location satisfies “Location_d”. If a network connection request is confirmed from the application corresponding to AppID2, the electronic device 101 may perform at least one operation for establishing a PDU session based on the path selection descriptor of rule "1". Meanwhile, the electronic device 101 may not configure an event for rule number 2. For example, when a plurality of rules are included in the URSP rule, the electronic device 101 may configure an event for some rules and not configure an event for other rules.

13 is a flowchart illustrating a method of operating an electronic device according to various embodiments.

According to various embodiments, the electronic device 101 (eg, at least a portion of the processor 120, the first communication processor 212, the second communication processor 214, or the integrated communication processor 260), In operation 1301, a traffic descriptor and a path selection descriptor may be checked. In operation 1303, the electronic device 101 may check whether time information and/or place information included in the path selection descriptor satisfy specified conditions. For example, the designated condition may include that time information included in the route selection descriptor is not “every time” and/or that location information is not “everywhere”. Here, time information of “every time” may mean that the corresponding rule is valid at any time, and location information of “everywhere” may mean that the corresponding rule is valid anywhere. For example, the electronic device 101 may acquire URSP rules as shown in Table 4.

rule number rule precedence traffic descriptor path selection descriptor One One App Descriptor = AppID1
FQDN=FQDN_1 [RSD1]
Precedence = 1
S-NSSAI = 102, SSC Mode = 2
Time Window = TimeVal_a1 ~ TimeVal_a2
Location Criteria = Location_a 2 2 App Descriptor = AppID2
FQDN=FQDN_1 [RSD2]
Precedence = 2
Time Window = every time, Location Criteria = every where

For rule “1”, the electronic device 101 determines that time information and/or place information satisfy designated conditions, for example, time information is not “every time” and/or place information is I can confirm that it is not "everywhere". For rule “2”, the electronic device 101 determines that time information and/or place information do not satisfy designated conditions, for example, that time information is “every time” and/or place information is “every time”. You can see that it is "everywhere". The electronic device 101 may configure an event corresponding to the traffic descriptor and the path selection descriptor in operation 1305 when the time information and/or the location information satisfy the designated conditions (1303-Yes). The electronic device 101 may refrain from configuring events corresponding to the traffic descriptor and the path selection descriptor in operation 1307 when the time information and/or the location information do not satisfy the designated condition (1303 - No). For example, the electronic device 101 may configure an event for rule number “1”. Accordingly, the electronic device 101 may provide a notification to the application corresponding to AppID2 when the checked time satisfies the conditions of TimeVal_d1 to TimeVal_d2 and the checked location satisfies “Location_d”. If a network connection request is confirmed from the application corresponding to AppID2, the electronic device 101 may perform at least one operation for establishing a PDU session based on the path selection descriptor of rule "1". Meanwhile, the electronic device 101 may not configure an event for rule number 2. For example, when a plurality of rules are included in the URSP rule, the electronic device 101 may configure an event for some rules and not configure an event for other rules.

14 is a flowchart illustrating a method of operating an electronic device according to various embodiments.

According to various embodiments, the electronic device 101 (eg, at least a portion of the processor 120, the first communication processor 212, the second communication processor 214, or the integrated communication processor 260), In operation 1401, it can be confirmed that the condition corresponding to the first event is satisfied. In operation 1403, the electronic device 101 may check whether another event having the traffic descriptor of the first event exists. For example, in the electronic device 101, one path selection descriptor may be set for one traffic descriptor, or a plurality of path selection descriptors may be set. If a plurality of path selection descriptors are set for one traffic descriptor, the electronic device 101 may set another event having the traffic descriptor of the first event. If there is another event having the traffic descriptor of the first event (1403 - Yes), the electronic device 101 may check, in operation 1405, whether a condition corresponding to the other event is satisfied. If the condition corresponding to the second event, which is another event, is satisfied (1405-Yes), in operation 1407, the electronic device 101 determines whether the priority of the first event is higher than that of the second event. You can check. If the priority of the first event is lower than or equal to the priority of the second event (1407 - No), the electronic device 101, in operation 1409, provides a notification to the application corresponding to the first event. can refrain from Accordingly, the PDU session corresponding to the second event may be established prior to the PDU session corresponding to the first event. If the priority of the first event is higher than that of the second event (1407-Yes), the electronic device 101, in operation 1411, may provide a notification to an application corresponding to the first event. . Even if another event having the traffic descriptor of the first event does not exist (1403 - No) or if a condition corresponding to the other event is not satisfied (1405 - No), the electronic device 101 performs operation 1411 In , a notification to an application corresponding to the first event may be provided. Accordingly, if conditions associated with time information and/or location information of a plurality of path selection descriptors for one traffic descriptor are satisfied at least simultaneously, the electronic device 101 corresponds to an event having a relatively high priority. Notifications can be provided as applications.

15 is a flowchart illustrating a method of operating an electronic device according to various embodiments.

According to various embodiments, the electronic device 101 (eg, at least a portion of the processor 120, the first communication processor 212, the second communication processor 214, or the integrated communication processor 260), In operation 1501, a URSP rule including at least one traffic descriptor and at least one path selection descriptor may be obtained. In operation 1503, the electronic device 101 may check whether a plurality of path selection descriptors correspond to the first traffic descriptor. If a plurality of path selection descriptors correspond to the first traffic descriptor (1503 - Yes), in operation 1505, the electronic device 101 may check whether path selection descriptors having overlapping event times exist. If there are path selection descriptors with overlapping event times (1505 - Yes), the electronic device 101 may configure the event by adjusting based on priority in operation 1507. For example, as shown in Table 5, the electronic device 101 may obtain a URSP rule in which a plurality of path selection descriptors correspond to one traffic descriptor.

rule number rule precedence traffic descriptor path selection descriptor One One App Descriptor = AppID1 [RSD(route selection descriptor) I]
Precedence = 1
S-NSSAI = 102, SSC Mode = 2
Time Window = TimeVal_a1 ~ TimeVal_a3
Location Criteria = Location_a [RSD 2]
Precedence = 2
S-NSSAI = 103, DNN = internet.mno.com
SSC Mode = 1
Time Window = TimeVal_a2 ~ TimeVal_a4
Location Criteria = Location_b

Referring to Table 5, the time information (time window) included in the first path selection descriptor may have values of a1 to a3, and the time information (time window) included in the second path selection descriptor may have values from a2 to a3. It can have a value of a4. For example, a1, a2, a3, and a4 may respectively mean points of time, and it is assumed that a1, a2, a3, and a4 have a time sequence. The electronic device 101 may check that the event times of the first path selection descriptor and the second path selection descriptor overlap at time points a2 to a3. In this case, the electronic device 101 may configure an event using the first path selection descriptor having a higher priority during the corresponding time. Accordingly, the electronic device 101 may configure an event table as shown in Table 6.

Event ID Time Window Location Criteria AppID1 a1 to a3 Location_a a3 to a4 Location_b

As shown in Table 6, the electronic device 101 may configure location information (eg, Location_a) included in a path selection descriptor with a higher priority as an event for overlapping times a2 to a3. there is. On the other hand, when a plurality of path selection descriptors do not correspond to the first traffic descriptor (1503-No), or when there are no path selection descriptors with overlapping event times (1505-No), the electronic device 101 operates in 1509 In operation, an event may be configured based on the at least one traffic descriptor and the at least one path selection descriptor.

16 is a flowchart illustrating a PDU session established by an electronic device according to various embodiments.

According to various embodiments, the electronic device 101 (eg, at least a portion of the processor 120, the first communication processor 212, the second communication processor 214, or the integrated communication processor 260), For example, the URSP rules shown in Table 4 can be obtained. As described with reference to Table 4, at time points a2 to a3, the event times of the first path selection descriptor and the second path selection descriptor may overlap. The electronic device 101 may provide a notification to the application 401 at times a1 to a3. When a network connection request is confirmed from the application 401, the electronic device 101 may establish a first PDU session 1601. Meanwhile, at points a2 to a4, the electronic device 101 may provide a notification to the application 401. When a network connection request is confirmed from the application 401, the electronic device 101 establishes a second PDU session. 1602. For example, the first PDU session 1601 and the second PDU session 1602 may be established at least simultaneously.

17 is a diagram for describing an operation of an entity executed in an electronic device according to various embodiments.

According to various embodiments, the network 400 may provide the URSP rules to the communications processor 444 in operation 1701 . 17, the URSP manager 443 may be included (or executed) in the communication processor 444. Accordingly, the URSP manager 443 may store and/or manage URSP rules. Communications processor 444 (or URSP manager 443 ) may provide URSP rules to URSP event manager 445 , in operation 1703 . The URSP event manager 445 may configure an event table (eg, the event table 640) using the provided URSP rules.

According to various embodiments, the URSP event manager 445, in operation 1705, the checked time and/or checked place corresponds to first time information and/or first place information included in the first route selection descriptor. can confirm that it is. Corresponds to the URSP event manager 445 and the first route selection descriptor based on the correspondence of the confirmed time and/or confirmed place to the first time information and/or first place information included in the first route selection descriptor It is possible to identify the application 401 using the first traffic descriptor. The URSP event manager 445 may provide a notification to the identified application 401 in operation 1707 . The notification may include, for example, meta data (eg, at least a part of a traffic descriptor). In response to the notification, the application 401 may provide a network connection request (eg, requestNewtork) to the connection manager 441 in operation 1709 . A network connection request may include, for example, metadata. The connection manager 441 may provide a network connection request to the mobile data manager 442 in operation 1711 . Based on receipt of the network connection request, mobile data manager 442 may provide a setup data call request to communication processor 444 in operation 1713 . At least a part of the path selection descriptor may be included in the setup data call request. The communication processor 444 may check a corresponding path selection descriptor based on the setup data call request. The communication processor 444 may transmit a PDU session establishment request message to the network 400 based on reception of the setup data call request in operation 1715 . Based on the reception of the PDU session establishment request message, the network 400 may perform at least one operation for establishing a PDU session. The network 400 may perform at least one operation for establishment of a PDU session and transmit a PDU session establishment accept message to the communication processor 444 in operation 1717 . In operation 1719 , the communications processor 444 may provide a setup data call response to the mobile data manager 442 . In operation 1721 , the mobile data manager 442 may provide a network notification (notifyNewtork) to the connection manager 441 . The connection manager 441 may provide a network notification (notifyNewtork) to the application 401 in operation 1723 . The application 401 may transmit and/or receive traffic 1727 through the PDU session 1725 established thereafter.

18 is a diagram for describing an operation of an entity executed in an electronic device according to various embodiments.

According to various embodiments, the network 400 may provide the URSP rules to the communications processor 444 in operation 1801 . In operation 1803, the communication processor 444 may provide the URSP rule to the URSP manager 443. The URSP manager 443 may store and/or manage URSP rules. The URSP manager 443 may provide the URSP rules to the URSP event manager 445 in operation 1805 . The URSP event manager 445 may configure an event table (eg, the event table 640) using the provided URSP rules.

According to various embodiments, in operation 1807, the application 401 may provide a network connection request for an event (requestNetworkForEvent) to the connection manager 441. For example, the application 401 sends a network connection request (requestNetworkForEvent) for an event to request a PDU session when the electronic device 101 satisfies the event without receiving a notification from the inside, and the connection manager (441). For example, the application 401 may provide a network connection request (requestNetworkForEvent) for an event to the connection manager 441 when receiving a connection request for an event from a server to be connected. In one example, the application 401 may receive event time information (eg, 2:00 pm) from a connected server. The application 401 may provide a network connection request for an event (requestNetworkForEvent) to the connection manager 441 at a time specified in the corresponding time information or earlier. In this case, the network connection request for the event (requestNetworkForEvent) may include time information (eg, 2:00 pm). For example, the application 401 may provide a network connection request (requestNetworkForEvent) for an event to the connection manager 441 based on an external input (eg, a user input). For example, the application 401 may provide a network connection request for an event (requestNetworkForEvent) to the connection manager 441 when at least one of sensing information, GPS information, or time information satisfies a specified condition. , there are no restrictions on the specified conditions and their judgment parameters. The connection manager 441 may provide a network connection request for an event (requestNetworkForEvent) to the mobile data manager 442 in operation 1809 . The mobile data manager 442 may provide a network connection request for an event (requestNetworkForEvent) to the URSP event manager 445 in operation 1811 .

According to various embodiments, the URSP event manager 445 may monitor whether a condition for an event is satisfied based on receiving a network connection request for an event (requestNetworkForEvent). The URSP event manager 445 may identify an event to be monitored based on information (eg, metadata) included in a network connection request (requestNetworkForEvent) for an event. If the condition for the event is not satisfied (1820), the URSP event manager 445, in operation 1821, provides a NotifyNewtwork including “fail” information to the mobile data manager 442. can For example, if confirmation of a corresponding event fails, the URSP event manager 445 may provide a NotifyNewtwork including “fail” information. The mobile data manager 442 may provide a NotifyNewtwork including “fail” information to the connection manager 441 in operation 1823 . The connection manager 441 may provide a NotifyNewtwork including “fail” information to the application 401 in operation 1825 .

If the condition for the event is satisfied (1830), the URSP event manager 445 may provide a network connection request (requestNetwork) to the mobile data manager 442. For example, when a corresponding event exists, the URSP event manager 445 may monitor whether a condition is satisfied, and may provide a network connection request (requestNetwork) when the condition for the event is satisfied. The network connection request (requestNetwork) may include, for example, AppID and/or metadata. Based on the reception of the network connection request, the mobile data manager 442 may provide a path selection descriptor request (eg, selectURSPRoute) to the URSP manager 443 in operation 1833 . The path selection descriptor request may include, for example, AppID and/or metadata, such as at least part of a traffic descriptor. The URSP manager 443 may check a path selection descriptor corresponding to the path selection descriptor request based on the reception of the path selection descriptor request. For example, the URSP manager 443 may check a path selection descriptor corresponding to AppID and/or metadata included in the path selection descriptor request by using a URSP rule. In operation 1835, the USRP manager 443 may provide information (eg, URSPRouteInformation) associated with the path selection descriptor to the mobile data manager 442. Information related to the path selection descriptor may include at least a part of the path selection descriptor. Mobile data manager 442 , in operation 1837 , may provide a setup data call request to communications processor 444 . At least a part of the path selection descriptor may be included in the setup data call request. The communication processor 444 may transmit a PDU session establishment request message to the network 400 based on reception of the setup data call request in operation 1839 . Based on the reception of the PDU session establishment request message, the network 400 may perform at least one operation for establishing a PDU session. The network 400 may perform at least one operation for establishment of a PDU session and transmit a PDU session establishment accept message to the communication processor 444 in operation 1841. In operation 1843, the communications processor 444 may provide a setup data call response to the mobile data manager 442. In operation 1847, the mobile data manager 442 may provide a network notification (notifyNewtork) including “success” information to the connection manager 441. The connection manager 441 may provide a network notification (notifyNewtork) including information of “success” to the application 401 in operation 1849 . The application 401 may provide a UI indicating the PDU session based on establishment. For example, the UI may include text indicating establishment of a PDU session, such as “a high-quality connection has been established”, but the implementation is not limited. The application 401 may transmit and/or receive traffic 1853 through the PDU session 1851 established thereafter. The application 401 may transmit and/or receive the traffic 833 based on a socket corresponding to the PDU session 831, for example, and transmit the traffic 833 through the PDU session 831. and/or reception. As described above, when conditions associated with time information and/or location information are satisfied, a corresponding PDU session may be established automatically or based on additional confirmation by the user.

19A is a diagram for describing an operation of an entity executed in an electronic device according to various embodiments. The embodiment of FIG. 19A will be described with reference to FIG. 19B. 19B is a diagram for explaining notifications according to various embodiments.

According to various embodiments, the network 400 may provide the URSP rules to the communications processor 444 in operation 1911 . In operation 1913, the communication processor 444 may provide the URSP rule to the URSP manager 443. The URSP manager 443 may store and/or manage URSP rules. The URSP manager 443 may provide the URSP rules to the URSP event manager 445 in operation 1915 . The URSP event manager 445 may configure an event table (eg, the event table 640) using the provided URSP rules. The URSP event manager 445 may provide a push notification to the notification manager 1900 in operation 1917 . The push notification may include URL information for installing an application. For example, when the URSP event manager 445 confirms that the checked time and/or checked place correspond to the first time information and/or first place information included in the first route selection descriptor, notification A push notification may be provided to the manager 1900 . Alternatively, for example, the URSP event manager 445 sends a push notification to the notification manager 1900 when the checked time has a difference of less than or equal to a threshold and the first time information included in the first path selection descriptor. application can be provided. The notification manager 1900 may output a notification based on the push notification in operation 1919 . For example, referring to FIG. 19B , the electronic device 101 may output a UI 1925. The UI 1925 may include, for example, a notification 1927 inquiring whether an application is downloaded, and the notification 1927 may include text that is easy for the user to understand (eg, "high quality Live Concert"). is starting now. Would you like to download an App that allows you to watch high-quality live concerts?"). The electronic device 101 sends a PDU session establishment command (or application download command) based on the input to the notification 1927 of FIG. 19B or additional input after the input to the notification 1927. You can check whether it is obtained or not. Meanwhile, in FIG. 19B, although the visual UI 1925 has been described, this is exemplary, and the UI 1925 may be provided in various ways such as an auditory method in addition to the visual method, and the user according to various methods It can be determined whether the input is also acquired in a corresponding way. If the application download command is obtained, the electronic device 101 may perform at least one operation for downloading the application using the URL. After the application is downloaded, the URSP event manager 445 determines that the checked time and/or place correspond to the first time information and/or first place information included in the first path selection descriptor, A notification can be provided as a downloaded application. Since the process for establishment of the subsequent PDU session has been described with reference to FIG. 8, a description thereof will be omitted.

19C is a diagram for explaining an operating method of an electronic device according to various embodiments.

According to various embodiments, the electronic device 101 (eg, at least a portion of the processor 120, the first communication processor 212, the second communication processor 214, or the integrated communication processor 260), In operation 1951, a URSP rule including at least one traffic descriptor and at least one path selection descriptor may be obtained. In operation 1953, the electronic device 101 may confirm that the checked time and/or checked place correspond to first time information and/or first place information included in the first path selection descriptor. In operation 1955, the electronic device 101 may check whether the first application corresponding to the first path selection descriptor is installed. If it is confirmed that the first application is installed (1955-Yes), in operation 1957, the electronic device 101 sends a notification to the first application identified by the first traffic descriptor corresponding to the first path selection descriptor. can provide Then, when the network connection request is confirmed from the first application, the electronic device 101 may perform at least one operation for establishing a PDU session. If it is not confirmed that the first application is installed (1955 - No), in operation 1959, the electronic device 101 may output a UI inquiring whether or not the first application is installed. If the application download command is confirmed through the UI, the electronic device 101 may perform at least one operation for downloading and/or installing the application. The electronic device 101 may provide a notification as an installed application. Then, when the network connection request is confirmed from the first application, the electronic device 101 may perform at least one operation for establishing a PDU session.

20 is a diagram for describing operations of entities executed in an electronic device according to various embodiments.

According to various embodiments, the network 400, in operation 2001, may provide the URSP rules to the communications processor 444. In operation 2003, the communications processor 444 may provide the URSP rules to the URSP manager 443. The URSP manager 443 may store and/or manage URSP rules. URSP manager 443 may provide URSP rules to URSP event manager 445 in operation 2005 . The URSP event manager 445 may configure an event table (eg, the event table 640) using the provided URSP rules.

According to various embodiments, the application 401 may provide an event network slice availability inquiry (requestEventNSAvailability) to the URSP event manager 445 in operation 2007 . The URSP event manager 445 may check whether the checked time and/or checked place correspond to time information and/or place information of an event corresponding to the application 401 . If the confirmed time and/or confirmed location corresponds to the time information and/or location information of the event corresponding to the application 401, in operation 2009, the URSP event manager 445 provides the application 401 with A response containing "available" information may be provided. If the confirmed time and/or confirmed location does not correspond to the time information and/or location information of the event corresponding to the application 401, in operation 2009, the URSP event manager 445 sends the application 401 A response including “not” information may be provided. If a response including “available” information is provided, the application 401 may provide a network connection request (eg, requestNewtork) to the connection manager 441 in operation 2011. there is. A network connection request may include, for example, metadata. The connection manager 441 may provide a network connection request to the mobile data manager 442 in operation 2013 . Based on the reception of the network connection request, the mobile data manager 442 may provide a path selection descriptor request (eg, selectURSPRoute) to the URSP manager 443 in operation 2015 . The path selection descriptor request may include, for example, AppID and/or metadata, such as at least part of a traffic descriptor. The URSP manager 443 may check a path selection descriptor corresponding to the path selection descriptor request based on the reception of the path selection descriptor request. For example, the URSP manager 443 may check a path selection descriptor corresponding to AppID and/or metadata included in the path selection descriptor request by using a URSP rule. In operation 2017, the USRP manager 443 may provide the mobile data manager 442 with information associated with the path selection descriptor (eg, URSPRouteInformation). Information related to the path selection descriptor may include at least a part of the path selection descriptor. Mobile data manager 442 , in operation 2019 , may provide a setup data call request to communications processor 444 . At least a part of the path selection descriptor may be included in the setup data call request. The communication processor 444 may transmit a PDU session establishment request message to the network 400 based on reception of the setup data call request in operation 2021 . Based on the reception of the PDU session establishment request message, the network 400 may perform at least one operation for establishing a PDU session. The network 400 may perform at least one operation for establishment of a PDU session and transmit a PDU session establishment accept message to the communication processor 444 in operation 2023. In operation 2025, the communications processor 444 may provide a setup data call response to the mobile data manager 442. In operation 2027, the mobile data manager 442 may provide a network notification (notifyNewtork) to the connection manager 441. The connection manager 441 may provide a network notification (notifyNewtork) to the application 401 in operation 2029 . The application 401 may transmit and/or receive traffic 2033 through the PDU session 2031 established thereafter.

21A is a flowchart illustrating a method of operating an electronic device according to various embodiments.

According to various embodiments, the electronic device 101 (eg, at least a portion of the processor 120, the first communication processor 212, the second communication processor 214, or the integrated communication processor 260), In operation 2101, a URSP rule including at least one traffic descriptor and at least one path selection descriptor may be obtained. In operation 2103, the electronic device 101 receives a notification based on confirming that the checked time and/or checked place correspond to the first time information and/or first place information included in the first path selection descriptor. You can decide when to provide the application. For example, the electronic device 101 may determine a time to provide a notification based on an output value of a random function. For example, the electronic device 101 sends a notification based on a result of processing (eg, hashing) at least one of IMEI, IMSI, phone number, MAC address, IP address, or time information. It is possible to determine when to provide the notification, but there is no limit to a method for determining when to provide the notification. In operation 2105, the electronic device 101 may provide a notification to the first application identified by the first traffic descriptor corresponding to the first path selection descriptor at the determined time point. In operation 2107, the electronic device 101 may perform at least one operation for establishing a PDU session based on the confirmation of the network connection request from the first application. Accordingly, the timing at which a plurality of electronic devices transmit PDU session establishment request messages to the network may be distributed. In one example, when the time point at which a specific URSP rule is useful is the first time point, there is a possibility that a plurality of electronic devices substantially simultaneously request PDU session establishment request messages to the network. According to various embodiments, the electronic device 101 may randomly set (or have a plurality of electronic devices have different values) a time point for providing a notification to an application, so that a relatively large number of notifications are temporarily provided to the network. Requesting a PDU session of can be mitigated.

21B is a flowchart illustrating a method of operating an electronic device according to various embodiments.

According to various embodiments, the electronic device 101 (eg, at least a portion of the processor 120, the first communication processor 212, the second communication processor 214, or the integrated communication processor 260), In operation 2111, a URSP rule including at least one traffic descriptor and at least one path selection descriptor may be obtained. In operation 2113, the electronic device 101 may confirm that the checked time and/or checked place correspond to first time information and/or first place information included in the first path selection descriptor. In operation 2115, the electronic device 101 may provide a notification to the first application identified by the first traffic descriptor corresponding to the first path selection descriptor. In operation 2117, the electronic device 101 may determine a PDU session establishment request time point based on the confirmation of the network connection request from the first application. For example, the electronic device 101 may determine the PDU session establishment request time point based on the output value of the random function. For example, the electronic device 101 requests PDU session establishment based on a result of processing (eg, hashing) at least one of IMEI, IMSI, phone number, MAC address, IP address, or time information. The timing may be determined, but there is no limitation on the method for determining the timing of the PDU session establishment request. The electronic device 101, in operation 2119, may perform at least one operation for establishing a PDU session at the determined time point. According to various embodiments, the electronic device 101 may randomly set a PDU session establishment request time point (or have a plurality of electronic devices have different values), so that a relatively large number of PDU sessions are temporarily established in the network. What is requested can be relaxed.

According to various embodiments, an electronic device (eg, the electronic device 101) includes at least one processor (eg, the processor 120, the first communication processor 212, and the second communication processor 214). , or the unified communication processor 260), wherein the at least one processor obtains a URSP rule including at least one traffic descriptor and at least one path selection descriptor, and confirmed by the electronic device It is confirmed that the selected time and/or the place confirmed by the electronic device corresponds to first time information and/or first place information included in a first route selection descriptor among the at least one route selection descriptor, and A notification is provided to a first application identified by a first traffic descriptor among the at least one traffic descriptor corresponding to 1 path selection descriptor, and a network connection request is confirmed from the first application receiving the notification. Based on this, it may be configured to perform at least one operation for establishing a PDU session based on the first path selection descriptor corresponding to the first application.

According to various embodiments, the at least one processor determines, based on the first path selection descriptor corresponding to the first application, based on confirmation of the network connection request from the first application that has received the notification. As at least part of the operation of performing the at least one operation for establishing a PDU session, a UI corresponding to the notification is provided, and the PDU session establishment command through the UI is confirmed. Provided in response to Based on the confirmation of the network connection request from the first application, the at least one operation for establishing a PDU session may be performed based on the first path selection descriptor corresponding to the first application.

According to various embodiments, as at least part of an operation of providing the UI corresponding to the notification, the at least one processor requests additional information from an application server corresponding to the first application and responds to the request. Therefore, the UI may be configured using the additional information received from the application server.

According to various embodiments, the at least one processor determines, based on the first path selection descriptor corresponding to the first application, based on confirmation of the network connection request from the first application that has received the notification. As at least part of the operation of performing the at least one operation for establishing a PDU session, the network connection request from the first application provided in response to receiving the notification is confirmed. Based on the confirmation, the first It may be set to perform the at least one operation for establishing a PDU session based on the first path selection descriptor corresponding to an application.

According to various embodiments, the at least one processor uses at least a part of the at least one traffic descriptor and the at least one path selection descriptor of the URSP rule, and each of the at least part of the traffic descriptor and the path selection descriptor of the path selection descriptor It is further configured to configure at least one event including at least a part, time information and/or place information, wherein the at least one processor includes the time and/or location identified by the electronic device. As at least part of the operation of confirming that the first time information and/or first place information included in the first path selection descriptor among the at least one path selection descriptor corresponds to the time and/or It may be configured to check whether the place confirmed by the electronic device corresponds to time information and/or place information of each of the at least one event.

According to various embodiments, the at least one processor corresponds to at least one second traffic descriptor including an AppID among the at least one traffic descriptor of the URSP rule, as at least part of the operation of configuring the at least one event configures at least some of the at least one event, and refrain from configuring an event corresponding to at least one third traffic descriptor not including the AppID among the at least one traffic descriptor of the URSP rule. .

According to various embodiments, the at least one processor, as at least part of the operation of configuring the at least one event, at least one second traffic descriptor that does not include security information among the at least one traffic descriptor of the URSP rule Configure at least some of the at least one event corresponding to, and refrain from configuring an event corresponding to at least one third traffic descriptor including the security information among the at least one traffic descriptor of the URSP rule. can

According to various embodiments, the at least one processor may, as at least part of the operation of configuring the at least one event, time information and/or location information that satisfies a specified condition among the at least one path selection descriptor of the URSP rule. Time information that configures at least some of the at least one event corresponding to at least one second path selection descriptor that includes, and does not satisfy the specified condition among the at least one path selection descriptor of the URSP rule, and/or It may be configured to refrain from configuring an event corresponding to at least one third path selection descriptor including place information.

According to various embodiments, the at least one processor selects the first path as at least part of an operation of providing a notification to a first application identified by a first traffic descriptor corresponding to the first path selection descriptor. Based on the fact that the first priority corresponding to the descriptor is higher than the second priority corresponding to the fourth path selection descriptor corresponding to the time identified by the electronic device and/or the place identified by the electronic device, The notification may be provided to the first application identified by the first traffic descriptor.

According to various embodiments, the at least one processor, as at least part of an operation of providing a notification to a first application identified by a first traffic descriptor corresponding to the first path selection descriptor, uses the first traffic descriptor Based on this, the first application may be downloaded, installed in the electronic device, and configured to provide the notification to the first application.

According to various embodiments, the at least one processor, as at least part of an operation of downloading the first application based on the first traffic descriptor and installing the first application in the electronic device, inquires whether the first application is downloaded. A UI may be provided, and based on confirmation of a command to download the first application through the UI, the first application may be set to be downloaded based on the first traffic descriptor.

According to various embodiments, the at least one processor, as at least part of an operation of providing the notification to the first application identified by the first traffic descriptor corresponding to the first path selection descriptor, the node It may be configured to check a time point for providing a notification, and provide the notification to the first application at the checked time point.

According to various embodiments, the at least one processor, as at least part of an operation of performing at least one operation for establishing a PDU session based on the first path selection descriptor corresponding to the first application, the first It may be set to check the time to transmit the PDU session establishment request message based on the path selection descriptor, and to transmit the PDU session establishment request message at the confirmed time point.

According to various embodiments, an operating method of an electronic device may include obtaining a URSP rule including at least one traffic descriptor and at least one path selection descriptor, a time identified by the electronic device, and/or the electronic device An operation of confirming that the place identified by the above corresponds to first time information and/or first place information included in a first route selection descriptor among the at least one route selection descriptor, and a second route corresponding to the first route selection descriptor. 1 An operation of providing a notification to a first application identified by a traffic descriptor, and based on confirmation of a network connection request from the first application that has received the notification, the first application corresponding to the first application. 1 It may include an operation of performing at least one operation for establishing a PDU session based on the path selection descriptor.

According to various embodiments, based on confirming the network connection request from the first application receiving the notification, establishing a PDU session based on the first path selection descriptor corresponding to the first application The operation of performing the at least one operation may include an operation of providing a UI corresponding to the notification, and the operation of providing the network from the first application provided in response to confirming the establishment command of the PDU session through the UI. Based on the confirmation of the connection request, an operation of performing the at least one operation for establishing a PDU session based on the first path selection descriptor corresponding to the first application.

According to various embodiments, the providing of the UI corresponding to the notification may include requesting additional information from an application server corresponding to the first application, and receiving additional information from the application server in response to the request. An operation of configuring the UI using the additional information may be included.

According to various embodiments, based on confirming the network connection request from the first application receiving the notification, establishing a PDU session based on the first path selection descriptor corresponding to the first application The operation of performing the at least one operation may include selecting the first path corresponding to the first application based on confirming the network connection request from the first application provided in response to receiving the notification. The at least one operation for establishing a PDU session may be performed based on the descriptor.

According to various embodiments, the operation of providing a notification to the first application identified by the first traffic descriptor corresponding to the first path selection descriptor has a first priority corresponding to the first path selection descriptor. , Based on a higher priority than the second priority corresponding to the second path selection descriptor corresponding to the time identified by the electronic device and/or the place identified by the electronic device, identified by the first traffic descriptor The notification may be provided to the first application.

According to various embodiments, providing a notification to a first application identified by a first traffic descriptor corresponding to the first path selection descriptor includes downloading the first application based on the first traffic descriptor. and installing the notification on the electronic device, and providing the notification to the first application.

According to various embodiments, an electronic device includes at least one processor, and the at least one processor obtains a URSP rule including at least one traffic descriptor and at least one path selection descriptor, and from a first application Obtaining a network connection request for an event of, and selecting a first path among the at least one path selection descriptor corresponding to a first traffic descriptor among the at least one traffic descriptor identified based on information included in the network connection request Based on the first path selection descriptor, based on the first time information and/or first place information included in the descriptor corresponding to the time and/or the place confirmed by the electronic device It can be configured to perform at least one operation for establishing a PDU session.

According to various embodiments, an electronic device includes at least one processor, and the at least one processor obtains a URSP rule including at least one traffic descriptor and at least one path selection descriptor, and from a first application First time information included in a first path selection descriptor of the at least one path selection descriptor corresponding to a first traffic descriptor among the at least one traffic descriptor that confirms the inquiry and is identified based on the information included in the inquiry and/or providing a response corresponding to the inquiry to the first application based on the correspondence of the first location information to the time and/or the location confirmed by the electronic device; Based on confirmation of a network connection request from the first application receiving a response, at least one operation for establishing a PDU session based on the first path selection descriptor corresponding to the first application may be set to be performed. there is.

Electronic devices according to various embodiments disclosed in this document may be devices of various types. The electronic device may include, for example, a portable communication device (eg, a smart phone), a computer device, a portable multimedia device, a portable medical device, a camera, a wearable device, or a home appliance. An electronic device according to an embodiment of the present document is not limited to the aforementioned devices.

Various embodiments of this document and terms used therein are not intended to limit the technical features described in this document to specific embodiments, but should be understood to include various modifications, equivalents, or substitutes of the embodiments. In connection with the description of the drawings, like reference numbers may be used for like or related elements. The singular form of a noun corresponding to an item may include one item or a plurality of items, unless the relevant context clearly dictates otherwise. In this document, "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 "A Each of the phrases such as "at least one of , B, or C" may include any one of the items listed together in that phrase, or all possible combinations thereof. Terms such as "first", "second", or "first" or "secondary" may simply be used to distinguish a given component from other corresponding components, and may be used to refer to a given component in another aspect (eg, importance or order) is not limited. A (e.g., first) component is said to be "coupled" or "connected" to another (e.g., second) component, with or without the terms "functionally" or "communicatively." When mentioned, it means that the certain component may be connected to the other component directly (eg by wire), wirelessly, or through a third component.

The term "module" used in various embodiments of this document may include a unit implemented in hardware, software, or firmware, and is interchangeable with terms such as, for example, logic, logical blocks, parts, or circuits. can be used as A module may be an integrally constructed component or a minimal unit of components or a portion thereof that performs one or more functions. For example, according to one embodiment, the module may be implemented in the form of an application-specific integrated circuit (ASIC).

Various embodiments of this document provide one or more instructions stored in a storage medium (eg, internal memory 136 or external memory 138) readable by a machine (eg, electronic device 101). It may be implemented as software (eg, the program 140) including them. For example, a processor (eg, the processor 120 ) of a device (eg, the electronic device 101 ) may call at least one command among one or more instructions stored from a storage medium and execute it. This enables the device to be operated to perform at least one function according to the at least one command invoked. The one or more instructions may include code generated by a compiler or code executable by an interpreter. The device-readable storage medium may be provided in the form of a non-transitory storage medium. Here, 'non-temporary' only means that the storage medium is a tangible device and does not contain a signal (e.g. electromagnetic wave), and this term refers to the case where data is stored semi-permanently in the storage medium. It does not discriminate when it is temporarily stored.

According to one embodiment, the method according to various embodiments disclosed in this document may be included and provided in a computer program product. Computer program products may be traded between sellers and buyers as commodities. A computer program product is distributed in the form of a device-readable storage medium (e.g. compact disc read only memory (CD-ROM)), or through an application store (e.g. Play Store™) or on two user devices (e.g. It can be distributed (eg downloaded or uploaded) online, directly between smart phones. In the case of online distribution, at least part of the computer program product may be temporarily stored or temporarily created in a device-readable storage medium such as a manufacturer's server, an application store server, or a relay server's memory.

According to various embodiments, each component (eg, module or program) of the above-described components may include a single object or a plurality of entities, and some of the plurality of entities may be separately disposed in other components. there is. According to various embodiments, one or more components or operations among the aforementioned corresponding components may be omitted, or one or more other components or operations may be added. Alternatively or additionally, a plurality of components (eg modules or programs) may be integrated into a single component. In this case, the integrated component may perform one or more functions of each of the plurality of components identically or similarly to those performed by a corresponding component of the plurality of components prior to the integration. . According to various embodiments, the actions performed by a module, program, or other component are executed sequentially, in parallel, iteratively, or heuristically, or one or more of the actions are executed in a different order, or omitted. or one or more other actions may be added.

Claims (20)

In electronic devices,
comprising at least one processor, wherein the at least one processor:
obtain a URSP rule including at least one traffic descriptor and at least one path selection descriptor;
The time identified by the electronic device and/or the place identified by the electronic device correspond to first time information and/or first place information included in a first route selection descriptor among the at least one route selection descriptor. confirm that it is
Providing a notification to a first application identified by a first traffic descriptor among the at least one traffic descriptor corresponding to the first path selection descriptor;
To perform at least one operation for establishing a PDU session based on the first path selection descriptor corresponding to the first application based on confirmation of a network connection request from the first application receiving the notification set electronics. According to claim 1,
The at least one processor is configured to establish a PDU session based on the first path selection descriptor corresponding to the first application based on confirmation of the network connection request from the first application receiving the notification. As at least part of the operation of performing the at least one operation for
Provide a UI corresponding to the notification,
PDU based on the first path selection descriptor corresponding to the first application based on confirmation of the network connection request from the first application provided in response to confirmation of the PDU session establishment command through the UI An electronic device configured to perform the at least one operation for establishing a session. According to claim 2,
The at least one processor, as at least part of an operation of providing the UI corresponding to the notification,
Requesting additional information from an application server corresponding to the first application;
An electronic device configured to configure the UI by using the additional information received from the application server in response to the request. According to claim 1,
The at least one processor is configured to establish a PDU session based on the first path selection descriptor corresponding to the first application based on confirmation of the network connection request from the first application receiving the notification. As at least part of the operation of performing the at least one operation for
The method for establishing a PDU session based on the first path selection descriptor corresponding to the first application based on confirming the network connection request from the first application provided in response to receiving the notification. An electronic device configured to perform at least one action. According to claim 1,
The at least one processor may use at least a portion of the at least one traffic descriptor and the at least one path selection descriptor of the URSP rule, respectively, at least a portion of a traffic descriptor, at least a portion of a path selection descriptor, time information, and / or further configured to configure at least one event including place information,
The at least one processor may determine the first time information and/or the first time information and/or the location identified by the electronic device in a first route selection descriptor among the at least one route selection descriptor. Or, as at least part of an operation of confirming that the first place information corresponds to, the time information and/or location information of each of the at least one event is determined by the time and/or the place confirmed by the electronic device. An electronic device set to check whether or not it corresponds to According to claim 5,
The at least one processor, as at least part of the operation constituting the at least one event,
Configuring at least a part of the at least one event corresponding to at least one second traffic descriptor including an AppID among the at least one traffic descriptor of the URSP rule;
The electronic device configured to refrain from configuring an event corresponding to at least one third traffic descriptor not including the AppID among the at least one traffic descriptor of the URSP rule. According to claim 5,
The at least one processor, as at least part of the operation constituting the at least one event,
Configuring at least a part of the at least one event corresponding to at least one second traffic descriptor not including security information among the at least one traffic descriptor of the URSP rule;
An electronic device configured to refrain from configuring an event corresponding to at least one third traffic descriptor including the security information among the at least one traffic descriptor of the URSP rule. According to claim 5,
The at least one processor, as at least part of the operation constituting the at least one event,
Constructing at least a part of the at least one event corresponding to at least one second path selection descriptor including time information and/or place information satisfying a specified condition among the at least one path selection descriptor of the URSP rule;
An electronic device configured to refrain from configuring an event corresponding to at least one third route selection descriptor including time information and/or place information that does not satisfy the specified condition among the at least one route selection descriptor of the URSP rule. According to claim 1,
The at least one processor, as at least part of an operation of providing a notification to a first application identified by a first traffic descriptor corresponding to the first path selection descriptor,
A first priority corresponding to the first route selection descriptor is greater than a second priority corresponding to a fourth route selection descriptor corresponding to the time and/or location confirmed by the electronic device. An electronic device configured to provide the notification to the first application identified by the first traffic descriptor based on high. According to claim 1,
The at least one processor, as at least part of an operation of providing a notification to a first application identified by a first traffic descriptor corresponding to the first path selection descriptor,
Downloading the first application based on the first traffic descriptor and installing the first application in the electronic device;
An electronic device configured to provide the notification to the first application. According to claim 10,
The at least one processor, as at least part of an operation of downloading and installing the first application in the electronic device based on the first traffic descriptor,
Provide a UI for inquiring whether or not to download the first application;
The electronic device configured to download the first application based on the first traffic descriptor based on confirmation of a download command of the first application through the UI. According to claim 1,
The at least one processor, as at least part of an operation of providing the notification to the first application identified by the first traffic descriptor corresponding to the first path selection descriptor,
Check the timing of providing the notification,
An electronic device configured to provide the notification to the first application at the confirmed time point. According to claim 1,
The at least one processor, as at least part of an operation of performing at least one operation for establishing a PDU session based on the first path selection descriptor corresponding to the first application,
Checking a time to transmit a PDU session establishment request message based on the first path selection descriptor;
An electronic device configured to transmit the PDU session establishment request message at the confirmed time point. In the operating method of the electronic device,
obtaining a URSP rule including at least one traffic descriptor and at least one path selection descriptor;
The time identified by the electronic device and/or the place identified by the electronic device correspond to first time information and/or first place information included in a first route selection descriptor among the at least one route selection descriptor. operation to confirm that it is;
providing a notification to a first application identified by a first traffic descriptor corresponding to the first path selection descriptor; and
Performing at least one operation for establishing a PDU session based on the first path selection descriptor corresponding to the first application based on confirmation of a network connection request from the first application receiving the notification movement
A method of operating an electronic device comprising a. 15. The method of claim 14,
The at least one operation for establishing a PDU session based on the first path selection descriptor corresponding to the first application based on confirmation of the network connection request from the first application receiving the notification action to perform,
An operation of providing a UI corresponding to the notification, and
PDU based on the first path selection descriptor corresponding to the first application based on confirmation of the network connection request from the first application provided in response to confirmation of the PDU session establishment command through the UI An operation of performing the at least one operation for establishing a session.
A method of operating an electronic device comprising a. According to claim 15,
The operation of providing the UI corresponding to the notification,
requesting additional information to an application server corresponding to the first application; and
Configuring the UI using the additional information received from the application server in response to the request
A method of operating an electronic device comprising a. 15. The method of claim 14,
The at least one operation for establishing a PDU session based on the first path selection descriptor corresponding to the first application based on confirmation of the network connection request from the first application receiving the notification action to perform,
The method for establishing a PDU session based on the first path selection descriptor corresponding to the first application based on confirming the network connection request from the first application provided in response to receiving the notification. A method of operating an electronic device that performs at least one operation. 15. The method of claim 14,
In the operation of providing a notification to the first application identified by the first traffic descriptor corresponding to the first path selection descriptor, the first priority corresponding to the first path selection descriptor is determined by the electronic device. Based on a higher priority than the second priority corresponding to the identified time and/or the second path selection descriptor corresponding to the location identified by the electronic device, the first application identified by the first traffic descriptor A method of operating an electronic device providing notification. In electronic devices,
comprising at least one processor, wherein the at least one processor:
obtain a URSP rule including at least one traffic descriptor and at least one path selection descriptor;
Obtaining a network connection request for an event from a first application;
First time information included in a first path selection descriptor of the at least one path selection descriptor corresponding to a first traffic descriptor of the at least one traffic descriptor identified based on the information included in the network connection request, and/or At least one operation for establishing a PDU session based on the first path selection descriptor based on the first location information corresponding to the time and/or location confirmed by the electronic device An electronic device set up to perform In electronic devices,
comprising at least one processor, wherein the at least one processor:
obtain a URSP rule including at least one traffic descriptor and at least one path selection descriptor;
Confirm the inquiry from the first application,
First time information and/or first time information included in a first path selection descriptor among the at least one path selection descriptor corresponding to a first traffic descriptor among the at least one traffic descriptor identified based on the information included in the inquiry; Providing a response corresponding to the inquiry to the first application based on location information corresponding to a time and/or a location confirmed by the electronic device;
An electronic device configured to perform at least one operation for establishing a PDU session based on the first path selection descriptor corresponding to the first application, based on confirmation of a network connection request from the first application receiving the response. Device.

Images