WO2022186566A1 - Electronic device and method using media conditions for ims supplementary service - Google Patents

Abstract

An electronic device according to one embodiment may comprise: a communication module; a memory; and a processor which transmits a GET request according to XML configuration access protocol (XCAP) to a server in response to detecting a user's PUT attempt according to XCAP, transmits a first PUT request according to XCAP to the server in response to receiving a reply to the GET request, and transmits a second PUT request having a second media condition different from a first media condition of the first PUT request to the server in response to failure of a PUT operation corresponding to the first PUT request.

Description

Electronic device and method using media conditions for IMS supplementary service

The following disclosure relates to an electronic device and method for using a media condition for an IMS supplementary service.

IMS is a network framework devised by 3GPP to provide multimedia services in the Internet Protocol (hereinafter 'IP') network. IMS uses a packet-switched-based non-fixed path based on the Internet protocol to increase transmission efficiency and ensure stability. The electronic device may support various supplementary service functions, and representatively, a function for call forwarding and a function for call barring exist.

Unlike legacy networks where media conditions are enforced, in IMS, it is at the discretion of the operator operating the XCAP server to classify rules according to media. The rules according to the media of the XCAP server may be different for each call forwarding (CF) function and call blocking (CB) function. Accordingly, when the electronic device transmits a PUT request to a server to change a setting for an additional service function, success or failure of the PUT operation is often divided according to media conditions. Even when it appears that media is not used on the XML document transmitted by the server to the electronic device, when the electronic device transmits a PUT request having a media condition including media to the server, the PUT operation may be successful. Even if the operator has set rules according to the media for the XCAP server, since the supplementary service information is managed for each subscriber, there are cases where the rules according to the media required for each SIM are different depending on mergers and acquisitions of telecommunication companies, MVNO, rate plan, device change, etc. .

In response to detecting a PUT attempt according to the communication module, the memory, and the user's XML Configuration Access Protocol (XCAP), the electronic device according to an embodiment transmits a GET request according to the XCAP to the server, and responds to the GET request. In response to receiving a reply to and a processor for sending a second PUT request having a second media condition different from a media condition to the server.

The communication module may receive a rule set including a rule for at least one function from the server receiving the GET request.

The processor may determine whether a successful PUT operation exists for the function selected by the user among the at least one function from the successful PUT operation history associated with the server.

When the successful PUT operation exists, the processor determines whether a previous PUT request includes a media type designation, and generates a third PUT request using the media type designation of the previous PUT request. can be transmitted

When the successful PUT operation does not exist, the processor may generate and transmit the first PUT request based on a rule for the selected function.

The processor may determine whether the extracted rule includes a media type designation, and may generate and transmit a first PUT request using the media type designation of the extracted rule.

The processor sends, to the server, a second PUT request having a second media condition in which the media type specification is excluded, when the first media condition includes the media type specification, and the first media condition specifies the media type If not included, a second PUT request having a second media condition including media type designation may be transmitted to the server.

The processor extracts a rule corresponding to the function selected by the user from among the rules for the at least one function, and adds a media condition including a media type for which the electronic device requests a setting change to the extracted rule The second PUT request may be generated.

In response to the success of the PUT operation corresponding to the first PUT request, the processor determines whether the first media condition of the first PUT request includes a media type specification and requests a configuration change in the first PUT request. The function may be stored as a history of successful PUT operations for the server.

The processor receives a response status code from the server in response when a PUT operation corresponding to the first PUT request fails, and when the received response status code is a first code, sends the second PUT request can be transmitted to the server.

A method implemented by a processor according to an embodiment includes an operation of transmitting a GET request according to the XCAP to a server in response to detecting a PUT attempt according to the XML Configuration Access Protocol (XCAP) of the user, and a reply to the GET request In response to receiving the first media of the first PUT request, in response to an operation of transmitting a first PUT request according to XCAP to the server and a PUT operation corresponding to the first PUT request fail and transmitting a second PUT request having a second media condition different from the media condition to the server.

The electronic device according to an embodiment may transmit a first PUT request according to XCAP to the server, and when the PUT operation according to the first PUT request fails, may transmit a second PUT request having a different media condition to the server. Even if the PUT operation fails, the electronic device according to an embodiment may transmit a second PUT request having a different media condition to increase the success probability of the PUT operation.

When the PUT operation corresponding to the PUT request is successful, the electronic device according to an embodiment determines whether the media condition of the PUT request includes specifying a media type and a function of requesting a setting change in the PUT request to the server, a successful PUT operation history can be saved as The electronic device according to an embodiment may reduce the number of requests and/or responses between the electronic device and the server by using the successful PUT operation history at the next PUT attempt.

1 is a block diagram illustrating a configuration of an electronic device in a network environment according to example embodiments.

2 is a flowchart illustrating an operation of an electronic device according to an exemplary embodiment.

3 illustrates a screen provided by an electronic device to a user to change a function setting according to an exemplary embodiment.

4 illustrates an Extensible Markup Language (XML)-based document that an electronic device transmits and receives a GET request to a server according to an exemplary embodiment.

5 illustrates an XML-based document for a PUT request transmitted from an electronic device to a server according to an embodiment.

6 illustrates a process in which an electronic device generates a PUT request using a successful PUT operation history according to an embodiment.

7 illustrates an operation for generating and transmitting a first PUT request of an electronic device to a server according to an embodiment.

8 illustrates an operation for a case in which a PUT operation corresponding to a first PUT request of an electronic device fails, according to an embodiment.

1 is a block diagram of an electronic device 101 in a network environment 100, according to various embodiments. Referring to FIG. 1 , in a network environment 100 , the electronic device 101 communicates with the electronic device 102 through a first network 198 (eg, a short-range wireless communication network) or a second network 199 . It may communicate with at least one of the electronic device 104 and the server 108 through (eg, a long-distance wireless communication network). According to an 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 , a sound output module 155 , a display module 160 , an audio module 170 , and 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 an antenna module 197 . In some embodiments, at least one of these components (eg, the connection terminal 178 ) may be omitted or one or more other components may be added to the electronic device 101 . In some embodiments, some of these components (eg, sensor module 176 , camera module 180 , or antenna module 197 ) are integrated into one component (eg, display module 160 ). can be

The processor 120, for example, executes software (eg, a program 140) to execute at least one other component (eg, a hardware or software component) of the electronic device 101 connected to the processor 120. It can control and perform various data processing or operations. According to one embodiment, as at least part of data processing or operation, the processor 120 converts commands or data received from other components (eg, the sensor module 176 or the communication module 190 ) to the volatile memory 132 . may be stored in , process commands or data stored in the volatile memory 132 , and store the result data in the non-volatile memory 134 . According to an embodiment, the processor 120 is the 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 (eg, a graphic processing unit, a neural network processing unit) a neural processing unit (NPU), an image signal processor, a sensor hub processor, or a communication processor). For example, when the electronic device 101 includes the main processor 121 and the sub-processor 123 , the sub-processor 123 uses less power than the main processor 121 or is set to be specialized for a specified function. can The auxiliary processor 123 may be implemented separately from or as a part of the main processor 121 .

The secondary processor 123 may, for example, act on behalf of the main processor 121 while the main processor 121 is in an inactive (eg, sleep) state, or when the main processor 121 is active (eg, executing an application). ), 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 an embodiment, the coprocessor 123 (eg, an image signal processor or a communication processor) may be implemented as part of another functionally related component (eg, the camera module 180 or the communication module 190 ). have. 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. Artificial intelligence models can be created through machine learning. Such learning may be performed, for example, in the electronic device 101 itself on which the artificial intelligence model 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 above, but is not limited to the above example. The artificial intelligence model may include, in addition to, or alternatively, a software structure in addition to the hardware structure.

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, the program 140 ) and instructions related thereto. The memory 130 may include a volatile memory 132 or a 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 (eg, a user) of the electronic device 101 . 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 a sound signal 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. The receiver can be used to receive incoming calls. According to one embodiment, the receiver may be implemented separately from or as part of the speaker.

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

The audio module 170 may convert a sound into an electric signal or, conversely, convert an electric signal into a sound. According to an embodiment, the audio module 170 acquires a sound through the input module 150 , or an external electronic device (eg, a sound output module 155 ) connected directly or wirelessly with the electronic device 101 . The electronic device 102) (eg, a speaker or headphones) may output a sound.

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 sensed state. can do. According to an embodiment, the sensor module 176 may include, for example, a gesture sensor, a gyro sensor, a barometric pressure sensor, a magnetic sensor, an acceleration sensor, a grip sensor, a proximity sensor, a color sensor, an IR (infrared) sensor, a biometric sensor, It may include a temperature sensor, a humidity sensor, or an illuminance sensor.

The interface 177 may support one or more specified protocols that may be used by the electronic device 101 to directly or wirelessly connect with an external electronic device (eg, the electronic device 102 ). According to an 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 can be physically connected to an external electronic device (eg, the electronic device 102 ). According to an 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 an electrical signal into a mechanical stimulus (eg, vibration or movement) or an electrical stimulus that the user can perceive through tactile or kinesthetic sense. According to an 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 an 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 an embodiment, the power management module 188 may be implemented as, for example, at least a part of a power management integrated circuit (PMIC).

The battery 189 may supply power to at least one component of the electronic device 101 . According to one embodiment, 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). It can support establishment and communication performance through the established communication channel. 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 communication module, or a global navigation satellite system (GNSS) communication module) or a wired communication module 194 (eg, : It may include a local area network (LAN) communication module, or a power line communication module). A corresponding communication module among these communication modules 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 computer network (eg, a telecommunication network such as a LAN or a WAN). These various types of communication modules may be integrated into one component (eg, a single chip) or may be implemented as a plurality of components (eg, multiple chips) separate from each other. 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, a new radio access technology (NR). NR access technology includes high-speed transmission of high-capacity data (eMBB (enhanced mobile broadband)), minimization of terminal power and access to multiple terminals (mMTC (massive machine type communications)), or high reliability and low latency (URLLC (ultra-reliable and low-latency) -latency communications)). 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 techniques for securing performance in a high-frequency band, for example, beamforming, massive multiple-input and multiple-output (MIMO), all-dimensional multiplexing. It may support technologies such as full dimensional MIMO (FD-MIMO), an array antenna, analog beam-forming, or a large scale antenna. The wireless communication module 192 may support various requirements defined in the electronic device 101 , an external electronic device (eg, the electronic device 104 ), or a network system (eg, the second network 199 ). According to an embodiment, the wireless communication module 192 may include a peak data rate (eg, 20 Gbps or more) for realizing eMBB, loss coverage (eg, 164 dB or less) for realizing mMTC, or U-plane latency for realizing URLLC ( Example: Downlink (DL) and uplink (UL) each 0.5 ms or less, or round trip 1 ms or less) can be supported.

The antenna module 197 may transmit or receive a signal or power to the outside (eg, an external electronic device). According to an embodiment, the antenna module 197 may include an antenna including a conductor formed on a substrate (eg, a PCB) or a radiator formed of a conductive pattern. According to an 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 connected from the plurality of antennas by, for example, the communication module 190 . can be selected. 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)) other than the radiator may be additionally formed as a part of the antenna module 197 .

According to various embodiments, the antenna module 197 may form a mmWave antenna module. According to one embodiment, the mmWave antenna module comprises a printed circuit board, an RFIC disposed on or adjacent to a first side (eg, bottom side) of the printed circuit board and capable of supporting a designated high frequency band (eg, mmWave band); and a plurality of antennas (eg, an array antenna) disposed on or adjacent to a second side (eg, top or side) 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 a signal ( e.g. commands or data) can be exchanged with each other.

According to an embodiment, the command 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 a part of operations executed in the electronic device 101 may be executed in one or more external electronic devices 102 , 104 , or 108 . For example, when the electronic device 101 needs to perform a function or service automatically or in response to a request from a user or other device, the electronic device 101 may perform the function or service itself instead of executing the function or service itself. Alternatively or additionally, one or more external electronic devices may be requested to perform at least a part of the function or the service. One or more external electronic devices that have received 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 transmit a result of the execution to the electronic device 101 . The electronic device 101 may process the result as it is or additionally and provide it as at least a part of a response to the request. For this purpose, 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. The server 108 may be an intelligent server using machine learning and/or neural networks. According to an embodiment, the external electronic device 104 or the server 108 may be included in the second network 199 . The electronic device 101 may be applied to an intelligent service (eg, smart home, smart city, smart car, or health care) based on 5G communication technology and IoT-related technology.

The electronic device according to various embodiments disclosed in this document may have various types of devices. 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 device. The electronic device according to the embodiment of the present document is not limited to the above-described devices.

The 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 it should be understood to include various modifications, equivalents, or substitutions of the embodiments. In connection with the description of the drawings, like reference numerals may be used for similar or related components. The singular form of the noun corresponding to the item may include one or more of the item, unless the relevant context clearly dictates otherwise. As used herein, "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 , B, or C," each of which may include any one of the items listed together in the corresponding one of the phrases, or all possible combinations thereof. Terms such as "first", "second", or "first" or "second" may simply be used to distinguish an element from other elements in question, and may refer elements to other aspects (e.g., importance or order) is not limited. It is said that one (eg, first) component is “coupled” or “connected” to another (eg, second) component, with or without the terms “functionally” or “communicatively”. When referenced, it means that one component can 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, logic block, component, or circuit. can be used as A module may be an integrally formed part or a minimum unit or a part of the part that performs one or more functions. For example, according to an embodiment, the module may be implemented in the form of an application-specific integrated circuit (ASIC).

Various embodiments of the present document include 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). may be implemented as software (eg, the program 140) including For example, the processor (eg, the processor 120 ) of the device (eg, the electronic device 101 ) may call at least one of the one or more instructions stored from the storage medium and execute it. This makes it possible for the device to be operated to perform at least one function according to the called at least one command. 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-transitory' only means that the storage medium is a tangible device and does not contain a signal (eg, electromagnetic wave), and this term is used in cases where data is semi-permanently stored in the storage medium and It does not distinguish between temporary storage cases.

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

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

2 is a flowchart illustrating an operation of an electronic device according to an exemplary embodiment.

In operation 210 , when the processor (eg, the processor 120 of FIG. 1 ) of the electronic device (eg, the electronic device 101 of FIG. 1 ) detects a PUT attempt according to the XML Configuration Access Protocol (XCAP) of the user In response, a GET request according to XCAP may be sent to the server.

The electronic device is an Internet Protocol Multimedia Subsystem ('IMS') terminal, and may be a terminal using an IMS session for voice or video call. Table 1 below shows the support functions of call forwarding (Call Forwarding, hereinafter 'CF') and call blocking (Call Barring, hereinafter 'CB') of the IMS terminal required by GSMA PRD IR.92.

The electronic device may change the setting values for the additional service functions of [Table 1] by using the XCAP protocol.

The electronic device may support a plurality of functions related to call forwarding (CF) and a plurality of functions related to call barring (CB). Referring to Table 1, the electronic device includes a plurality of functions related to call forwarding (CF), such as Communication Forwarding Unconditional (CFU), Communication Forwarding on not Logged in (CFNL), Communication Forwarding on Busy (CFB), and Communication Forwarding on not Reachable. (CFNRc) and Communication Forwarding on No Reply (CFNRy) functions may be supported. The Communication Forwarding Unconditional (CFU) function indicates the function of unconditionally forwarding calls based on the destination address. The Communication Forwarding on not Logged in (CFNL) function indicates a function of forwarding calls when the terminal is not connected to the network. The Communication Forwarding on Busy (CFB) function indicates a function of forwarding a call when the terminal is in a call. The Communication Forwarding on not Reachable (CFNRc) function indicates a function of forwarding calls when the terminal is not accessible. The Communication Forwarding on No Reply (CFNRy) function indicates a function of forwarding a call when the terminal does not respond.

Electronic devices have multiple functions associated with call blocking (CB): Barring of All Incoming Calls (BAIC), Barring of All Outgoing Calls (BAOC), Barring of Outgoing International Calls (BOIC), Barring of Outgoing International Calls - ex Home Country (BOIC ExHC), Barring of Outgoing International Calls - When Roaming (BOICRoam), and Barring of Incoming Calls - When Roaming (BICRoam) can be supported. The Barring of All Incoming Calls (BAIC) function refers to the function to block all incoming calls. Barring of All Outgoing Calls (BAOC) refers to the ability to block all outgoing calls. The Barring of Outgoing International Calls (BOIC) function refers to the ability to block international outgoing calls. Barring of Outgoing International Calls - ex Home Country (BOIC ExHC) function refers to the function to block international outgoing calls to countries other than the user's own country. Barring of Outgoing International Calls - When Roaming (BOICRoam) function indicates the function to block international outgoing calls when the roaming function is running. Barring of Incoming Calls - When Roaming (BICRoam) function indicates the ability to block incoming calls when the roaming function is running.

The electronic device may detect a PUT attempt according to the user's XCAP for changing the setting of the additional service function from the user. The PUT attempt is a signal generated by a user and may indicate a signal for attempting to change a setting for at least one function among functions supported by the electronic device. In response to detecting a PUT attempt according to XCAP from the user, the electronic device may transmit a GET request according to XCAP to the server. The server may be an XCAP server.

The electronic device may transmit a GET request to the server in order to receive a list of functions supported by the XCAP server and a rule corresponding to the functions supported by the XCAP server. Functions supported by each server may be different. For example, the first XCAP server may support the Call Forwarding Unconditional (hereinafter, 'CFU') function, but may not support the Call Forwarding on Busy (hereinafter, 'CFB') function. The second XCAP server may not support the CFU function, but may support the CFB function. The electronic device may receive a rule for a function supported by the server, which will be described in more detail with reference to FIG. 4 .

In operation 220 , in response to receiving a reply to the GET request, the electronic device may transmit the first PUT request according to the XCAP to the server. The electronic device may receive a list of functions supported by the server and respective rules for supported functions according to the GET request. In response to receiving a reply to the GET request, the electronic device may transmit a first PUT request for changing a setting for a function selected by the user to the server.

The GET request may indicate a signal requesting delivery of at least one function supported by the server and a rule for at least one function. The server may transmit at least one supported function and a message configured as an XML document for at least one function rule to the terminal that has transmitted the GET request.

The PUT request may be a signal for requesting a configuration change for at least one function supported by the server. The PUT request may be a message composed of an XML document, and the user terminal may transmit the PUT request to the server.

In operation 230 , in response to the failure of the PUT operation corresponding to the first PUT request, the electronic device requests a second PUT having a second media condition different from a first media condition of the first PUT request. can be sent to the server.

There are four media conditions according to the media type. The media condition may include a media condition including audio, a media condition including video, a media condition including both audio and video, and a media condition not including media. The electronic device may transmit a PUT request having a media condition including audio to the server, and may transmit a PUT request having a media condition including video to the server. Also, the electronic device may transmit a PUT request having a media condition including audio to the server and then transmit a PUT request having a media condition including video to the server. The electronic device may transmit a PUT request having a media condition that does not include media to the server. Hereinafter, it will be described that media type designation is included for a media condition including at least one media type, and media type designation is excluded for a media condition that does not include a media.

The electronic device according to an embodiment transmits a first PUT request to a server, and in response to a failure of a PUT operation corresponding to the first PUT request, a second media condition different from the first media condition of the first PUT request A second PUT request having a may be transmitted to the server. Even if the PUT operation corresponding to the first PUT request fails, the electronic device according to an embodiment may increase the success probability of the PUT operation by transmitting the second PUT request to the server.

When the first media condition of the first PUT request includes the designation of the media type, the electronic device according to an embodiment may transmit the second PUT request having the second media condition in which the designation of the media type is excluded to the server. When the first media condition does not include the media type designation, the electronic device may transmit a second PUT request having the second media condition including the media type designation to the server.

3 illustrates a screen provided by an electronic device to a user to change a function setting according to an exemplary embodiment.

The electronic device (eg, the electronic device 101 of FIG. 1 ) according to an embodiment may provide a screen 310 for an additional service. The electronic device may receive an interaction signal for the object 311 corresponding to call forwarding or the object 312 corresponding to call barring within the screen 310 from the user. . The electronic device according to an embodiment detects an interaction signal from the user for the object 311 corresponding to call forwarding (CF) or the object 312 corresponding to call blocking (CB) as a PUT attempt according to the user's XCAP. can

Since media is classified in a legacy network, the electronic device may generally provide a screen 320 for receiving a selection of a media type from a user. In the media type, there are an audio requesting to change the setting of a function for a voice and a video for requesting a setting change of a function for a video. The electronic device may receive an interaction signal for one of an object (voice call) 321 corresponding to audio or an object (video call) 322 corresponding to video media from a user in the screen 320 . When receiving an interaction signal for the object 321 corresponding to audio from the user, the electronic device may transmit a PUT request having a media condition including audio to the server. Similarly, when receiving an interaction signal for an object 322 corresponding to a video from a user, the electronic device may transmit a PUT request having a media condition including video to the server.

Furthermore, the electronic device may request a function setting change from the server without distinction of media types. The electronic device may determine the input signal for the MMI code from the dialer received from the user as a setting change request signal for the additional service function. In this case, the electronic device may include all media types in the media conditions and transmit them to the server. After transmitting the PUT request having the media condition including audio to the server, the electronic device may transmit the PUT request having the media condition including video to the server.

After receiving an interaction signal for a media type from the user on the screen 320 , the electronic device may present a screen 330 in which a plurality of supported functions are divided and displayed. 3 as an example, when the electronic device receives an interaction signal for the object 311 corresponding to the call forwarding (CF) from the user on the screen 310 , the electronic device receives the call forwarding (CF) in the screen 330 . ) and related functions can be presented. For example, the electronic device may include an object 331 corresponding to a Communication Forwarding Unconditional (CFU) function, an object 332 corresponding to a Communication Forwarding on Busy (CFB) function, and a Communication Forwarding on No Reply (CFNRy) function corresponding to the object corresponding to the function. An object 333 and an object 334 corresponding to a Communication Forwarding on Not Reachable (CFNRc) function may be presented. Similarly, when the electronic device receives an interaction signal for the object 312 corresponding to the call blocking (CB) from the user on the screen 310 , the plurality of call blocking (CB) associated with the screen 330 is displayed. functions can be presented.

4 illustrates an Extensible Markup Language (XML)-based document that an electronic device transmits and receives a GET request to a server according to an exemplary embodiment.

The communication module (eg, the communication module 190 of FIG. 1 ) of the electronic device (eg, the electronic device 101 of FIG. 1 ) according to an embodiment may transmit a GET request to the server, and the GET request A rule set including a rule for at least one function may be received from the server receiving the . The electronic device may omit the GET request when a rule set previously transmitted to the server already exists.

The electronic device may transmit a GET request to the server, and in response to the GET request, at least one function supported by the server and information about a rule for at least one function may be received as the XML document 400 . have. The XML document 400 received from the server may include a rule set 420 including rules for functions supported by the server along with a 200 OK response 410 .

The XML document 400 may include an object 411 capable of distinguishing the type of the rule set 420 . The electronic device uses the object 411 in the XML document 400 to determine whether the rule set 420 includes rules for functions related to call forwarding (CF) and rules for functions related to call blocking (CB). can determine whether For example, referring to FIG. 4 , the object 411 in the XML document 400 is “communication-diversion”, and the electronic device determines that the rule set 420 includes a rule related to call forwarding (CF). can do.

The rule set 420 may include a first rule 421 , a second rule 422 , and a third rule 423 . In FIG. 4 , the rule set 420 of the XML document 400 is illustrated as including three rules 421 , 422 , and 423 , but the number of rules is not limited thereto. A function supported by the XCAP server for the additional service may correspond to rules 421 , 422 , and 423 in the XML document 400 , respectively. The electronic device may determine a function corresponding to the rule based on conditions 431 , 432 , and 433 of the rules 421 , 422 , and 423 . For example, when the condition 431 of the first rule 421 does not contain any conditions, the electronic device determines that the first rule 421 performs Communication Forwarding Unconditional (CFU) among functions related to call forwarding (CF). It can be judged that it corresponds to the function. As another example, when the condition 432 of the second rule 422 includes a <busy> condition, the second rule 432 includes a Communication Forwarding on Busy (CFB) function among functions related to call forwarding (CF). It can be judged that it corresponds to As another example, when the third rule 433 includes a <no answer> condition as a condition, it may be determined that the third rule corresponds to a Communication Forwarding on No Reply (CFNRy) function. The electronic device may determine that the server supports the CFU function, the CFB function, and the CFNRy function based on the rule set 420 of the XML document 400 received from the server.

Conditions 431 , 432 , and 433 of each rule in the XML document 400 received from the server may include media conditions. For example, the first rule 421 and the third rule 423 may have a media condition excluding media type designation, and the second rule 422 may have a media condition including media type designation. . Referring to FIG. 4 , the second rule 422 may include a media condition 452 including audio.

Furthermore, in the XML document 400 received from the server, the conditions 431 , 432 , and 433 of each rule may include an inactive condition according to whether a function corresponding to the rule is currently activated. For example, when the CFB function corresponding to the second rule 422 is not currently activated in the electronic device, a deactivation condition (<rule-deactivated/>, 462 ) may be included. Similarly, when the CFNRy function corresponding to the third rule 423 is currently deactivated in the electronic device, the deactivation condition 463 may be included. On the other hand, when the CFU function corresponding to the first rule 421 is currently activated in the electronic device, the first rule 421 does not include a deactivation condition.

Table 2 below shows conditions for distinguishing additional service functions related to call forwarding and call blocking.

According to GSMA IR 92. Section 2.3.2, in the electronic device, among the conditions included in one rule, the remaining conditions except for the inactive condition (eg, <rule-deactivated>) and the media condition are additional services. In the case of strictly matching the condition corresponding to the function, the corresponding rule may be determined to correspond to the corresponding additional service function. For example, referring to FIG. 4 , among the conditions included in the second rule 422 , the remaining conditions excluding the inactive condition (<rule-deactivated/>) and the media condition (audio) may be a <busy> condition. . In the electronic device, since the remaining conditions of the second rule 422 match the condition (<busy>) corresponding to the function of the CFB, the second rule 422 corresponds to the function of the CFB. As another example, among the conditions included in the third rule 423 , the remaining conditions excluding the inactive condition may be a <no-answer> condition. Since the remaining conditions of the third rule 423 match the condition (<no-answer>) corresponding to the function of CFNRy, the electronic device may determine that the third rule 423 corresponds to the function of CFNRy.

The electronic device may acquire a set value of a function corresponding to the rule based on the action 441 , 442 , and 443 of the rule. For example, if the first target address 471 is included in the action 441 of the first rule, the electronic device determines that the CFU function corresponding to the first rule 421 performs the first target address ( 471) can be determined.

5 illustrates an XML-based document for a PUT request transmitted from an electronic device to a server according to an embodiment.

The electronic device (eg, the electronic device 101 of FIG. 1 ) according to an embodiment may transmit a PUT request to the server in order to change the function setting. The electronic device may transmit the XML document 500 to the server as a PUT request.

The XML document 500 may include a rule set 520 including a rule for a function requesting a setting change. The XML document 500 may include an object 511 capable of distinguishing the type of the rule set 520 . The electronic device displays the object 511 in the XML document 500 to distinguish whether the rule set 520 is a rule for a function related to call forwarding (CF) or a rule for a function related to call blocking (CB). can

The rule set 520 may include a fourth rule 521 corresponding to a function requesting a setting change. The electronic device may include a condition corresponding to the function requesting a setting change in the condition 531 of the fourth rule. Referring to FIG. 4 , when the electronic device requests the server to change the setting for the CFB function, a condition (<busy/>) indicating the type of function may be included in the condition 531 of the fourth rule. The electronic device may also include the media condition 532 in the condition 531 of the fourth rule. The electronic device may include the second target address 542 as a setting value for requesting a change to the CFB function in the action 541 of the fourth rule.

The XCAP server may receive the XML document 500 according to the PUT request from the electronic device. If there is no grammatical error in the received XML document 500 and the media condition 532 included in the rule matches the media condition of the server, the server performs a function corresponding to the fourth rule 521 (eg, CFB). function) may be changed to the second target address 542 .

6 illustrates a process in which an electronic device generates a PUT request using a successful PUT operation history according to an embodiment.

In operation 621 , the electronic device (eg, the electronic device 101 of FIG. 1 ) determines whether there is a successful PUT operation for the function selected by the user among at least one function supported by the server from the successful PUT operation history related to the server. can determine whether

In operation 622, when there is a successful PUT operation for a function selected from the successful PUT operation history, the electronic device determines whether a previous PUT request includes a media type specification, and the media of the previous PUT request. A third PUT request may be generated and transmitted using the type designation. When the previous PUT request includes the media type designation, the electronic device may generate and transmit a third PUT request having a media condition including the media type designation to the server. When the media type specification is excluded from the previous PUT request, the electronic device may generate a third PUT request having a media condition in which the media type specification is excluded and transmit it to the server. For example, a case in which the electronic device receives a selection signal for audio among media types from a user will be described. When a previous PUT request corresponding to a successful PUT operation includes a media type designation, the electronic device may generate and transmit a third PUT request having a media condition including audio to the server. When the previous PUT request does not include the media type specification, the electronic device may generate a third PUT request having a media condition in which the media type specification is excluded and transmit it to the server. After generating and transmitting the third PUT request to the server, the electronic device may terminate communication with the server.

In operation 623, when there is no successful PUT operation for the function selected by the user from the successful PUT operation history, the electronic device extracts a rule corresponding to the function selected by the user from among the rules for at least one function, A first PUT request may be generated based on the extracted rule and transmitted to the server. The electronic device may receive a rule set including rules for functions supported by the server in response to the GET request from the server. The electronic device may generate the first PUT request by extracting a rule corresponding to a function selected by the user from among the rules included in the rule set. Hereinafter, a process in which the electronic device generates the first PUT request using the extracted rule will be described.

The electronic device may generate the first PUT request using the rule set transmitted from the server. The rule set may include a rule for at least one function supported by the server. The electronic device may extract a rule corresponding to the function selected by the user from among the rules for at least one function transmitted from the server. The electronic device may extract a rule in which the remaining conditions excluding the inactivity condition and the media condition among at least one rule received from the server strictly match a condition corresponding to a function selected by the user. The electronic device may determine whether the extracted rule includes the media type designation, and may generate and transmit the first PUT request using the media type designation of the extracted rule. When the extracted rule includes the media type designation, the electronic device may generate a first PUT request having a media condition including the media type designation and transmit it to the server. When the extracted rule does not include the media type designation, the electronic device may generate and transmit a first PUT request having a media condition in which the media type designation is excluded to the server. For example, referring to FIG. 4 , the electronic device may transmit a GET request to the server to change the setting for the Communication Forwarding on Busy (CFB) function, and transmit the XML document 400 as a reply to the GET request from the server. can be sent The electronic device may extract a rule 422 corresponding to the CFB function from among the rules 421 , 422 , and 423 for at least one function received from the server. Since the extracted rule 422 includes a media condition including audio, the electronic device may determine that the rule 422 includes media type designation. The electronic device may generate a first PUT request having a media condition including media type designation and transmit it to the server. When the electronic device receives a selection signal for audio among media types from the user, it may generate a first PUT request having a media condition including audio and transmit it to the server. When the electronic device receives a selection signal for video among media types from the user, it may generate and transmit a first PUT request having a media condition including video to the server.

As another example, the electronic device may transmit a GET request to the server to change the settings for the Communication Forwarding Unconditional (CFU) function, and rules 421, 422, 423), it is possible to extract the first rule 421 corresponding to the CFU function. Since the extracted first rule 421 includes a media condition that does not include media, the electronic device may determine that the media type designation is excluded from the first rule 421 . Accordingly, the electronic device may generate and transmit the first PUT request having a media condition in which the designation of the media type is excluded to the server. The electronic device may generate and transmit a first PUT request having a media condition that does not include media to the server.

7 illustrates an operation for generating and transmitting a first PUT request of an electronic device to a server according to an embodiment.

In operation 731 , the electronic device (eg, the electronic device 101 of FIG. 1 ) may determine whether the PUT operation corresponding to the first PUT request is successful. When the electronic device transmits the first PUT request to the server, the server determines whether there is a grammatical error in the XML document indicating the first PUT request, whether a setting change for a function not supported is requested, and the media condition of the XML document A response to the PUT request may be provided to the electronic device by determining whether it meets the media condition of the server. If there is no error in the first PUT request transmitted from the electronic device, the server may change the setting value of the function requested to be changed. The server may transmit a 200 OK response to the electronic device in response to the first PUT request. When receiving the 200 OK response from the server, the electronic device may determine that the server has changed a setting value for the function requested to be changed, and may determine that the PUT operation corresponding to the first PUT request is successful.

In operation 732 , the electronic device changes whether the first media condition of the first PUT request includes a media type specification and a setting in the first PUT request in response to the success of the PUT operation corresponding to the first PUT request. The requested function can be saved as a history of successful PUT operation for the corresponding XCAP server. The electronic device may generate a PUT request using a successful PUT operation history when a user requests a change in the setting of the same function for the corresponding server thereafter.

In operation 733 , the electronic device transmits, to the server, a second PUT request having a second media condition different from the first media condition of the first PUT request to the server in response to the failure of the PUT operation corresponding to the first PUT request. can The operation 733 will be described in more detail with reference to FIG. 8 .

8 illustrates an operation for a case in which a PUT operation corresponding to a first PUT request of an electronic device fails, according to an embodiment.

In operation 831 , the electronic device may receive a response status code from the server in response to the failure of the PUT operation corresponding to the first PUT request. The electronic device may determine whether the response status code received from the server is the first code.

In operation 832 , when the response status code received from the server is the first code, the electronic device may transmit the second PUT request to the server. The electronic device may transmit the second PUT request to the server only when the response status code received from the server is the first code. Here, the first code may be a 409 Conflict code. 409 Conflict indicates that the current state of the server and the PUT request of the electronic device collide. 409 Conflict occurs when the XML document received by the server from the electronic device contains grammatical errors, rules for functions not supported by the server are included in the XML document, or the XML document contains a condition that does not exist in the server. This is the error code for When the electronic device according to an embodiment receives an error code for 409 Conflict when the PUT operation corresponding to the first PUT request fails, the server receives a media condition in the XML document transmitted from the electronic device. ), it is determined that there is an error, and the second PUT request can be transmitted to the server.

When the response status code received from the server is the second code, the electronic device may terminate communication with the server. The second code may be one of the remaining codes except for the first code (eg, 409 Conflict code) among error codes. HTTP response status codes can be divided into 5 classes. The first digit of the response status code may define the class of the response. A response status code with the first digit of '4' indicates a code regarding a client error, and a response status code with a first digit of '5' indicates a code regarding a server error. The error code indicates a response status code in which the first digit of the HTTP response status codes is '4' or '5'. After terminating communication with the server, the electronic device may attempt to change a setting for a call forwarding (CF)/call blocking (CB) function according to an existing method. For example, the electronic device may attempt to change the setting for the additional service function in a circuit switch fallback method, which is a method using the existing 3G network.

The electronic device may transmit a second PUT request having a second media condition different from the first media condition of the first PUT request to the server. Whether the media type designation for the first media condition is included and whether the media type designation for the second media condition is included may be opposite to each other.

When the first media condition includes the media type specification, the second media condition may exclude the media type specification. When transmitting a first PUT request having a media condition including audio, the electronic device according to an embodiment may transmit a second PUT request having a media condition not including media to the server. When the electronic device transmits the first PUT request having the media condition including video, the electronic device may transmit the second PUT request having the media condition not including the media to the server. When the electronic device transmits the first PUT request having the media condition including both audio and video to the server, the electronic device may transmit the second PUT request having the media condition including no media to the server. In other words, when the electronic device transmits a first PUT request having a media condition including audio and a first PUT request having a media condition including video, the second PUT request having a media condition including no media A PUT request can be sent to the server.

If the first media condition does not include the media type specification, the second media condition may include the media type specification. When transmitting the first PUT request having the media condition including the media type designation, the electronic device according to an embodiment may transmit the second PUT request having the media condition including the media type designation. The electronic device may receive a selection input for a media type from the user and request a change in settings for a function with respect to the media type. When the electronic device receives a signal requesting a change of settings for a function from a user regardless of media type, the electronic device may request a change of settings for a function from the server for both audio and video. When the media type for requesting a configuration change from the server is audio, the electronic device may transmit the second PUT request as a media condition including audio. When the media type for requesting a setting change from the server is video, the electronic device may transmit the second PUT request as a media condition including video. When the electronic device requests the server to change the function setting without discriminating the media type, the electronic device transmits a second PUT request having a media condition including audio to the server, and then transmits a second PUT request having a media condition including video to the server. A PUT request can be sent to the server.

When the electronic device transmits a second PUT request having a media condition including media type designation to the server, the second PUT using a rule corresponding to a function requesting a setting change among at least one rule received from the server You can create a request. The electronic device extracts a rule corresponding to the function selected by the user from among the rules for at least one function received from the server, and adds a media condition including a media type for which the electronic device requests a setting change to the extracted rule. A second PUT request may be generated. The electronic device cannot generate a PUT request including a new rule other than the rule for at least one function received from the server. Accordingly, the electronic device may first extract a rule in which the remaining conditions excluding the media condition and the inactivity condition from among the at least one rule received from the server strictly match the condition corresponding to the function selected by the user. The electronic device may add a media condition including a media type requesting a setting change to the extracted rule condition, and transmit a rule having a condition to which the media condition is added to the server to change the setting of a function corresponding to the rule can request

In operation 833 , the electronic device may determine whether a PUT operation corresponding to the second PUT request is successful.

In operation 834 , the electronic device changes whether a second media condition of the second PUT request includes a media type specification and a setting in the second PUT request in response to the success of the PUT operation corresponding to the second PUT request. The requested function can be saved as a successful PUT operation history for the server. The electronic device may generate a PUT request by using the stored successful PUT operation history when a user requests to change the setting of the same function for the corresponding server thereafter. In response to the failure of the PUT operation corresponding to the second PUT request, the electronic device may terminate communication with the server. After terminating communication with the server, the electronic device may attempt to change a setting for a call forwarding (CF)/call blocking (CB) function according to an existing method. For example, the electronic device may attempt to change the setting for the additional service function in a circuit switch fallback method, which is a method using the existing 3G network.

Claims (15)

1. In an electronic device,

   communication module;

   Memory; and

   In response to detecting the user's PUT attempt according to the XML Configuration Access Protocol (XCAP), a GET request according to the XCAP is transmitted to the server, and in response to receiving a reply to the GET request, the system according to the XCAP 1 PUT request is sent to the server, and in response to a failure of a PUT operation corresponding to the first PUT request, having a second media condition different from the first media condition of the first PUT request A processor that sends a second PUT request to the server

   An electronic device comprising a.
2. According to claim 1,

   The communication module is

   Receiving a rule set including rules for at least one function from the server receiving the GET request

   electronic device.
3. 3. The method of claim 2,

   The processor is

   Determining whether there is a successful PUT operation for the function selected by the user among the at least one function from the successful PUT operation history related to the server

   electronic device.
4. 4. The method of claim 3,

   The processor is

   When the successful PUT operation exists, it is determined whether a previous PUT request includes a media type designation, and a third PUT request is generated and transmitted using the media type designation of the previous PUT request.

   electronic device.
5. 4. The method of claim 3,

   The processor is

   If the successful PUT operation does not exist, generating and transmitting the first PUT request based on a rule for the selected function

   electronic device.
6. 6. The method of claim 5,

   The processor is

   It is determined whether the extracted rule includes a media type designation, and a first PUT request is generated and transmitted using the media type designation of the extracted rule.

   electronic device.
7. 3. The method of claim 2,

   The processor is

   When the first media condition includes a media type designation, a second PUT request with a second media condition in which the media type designation is excluded is sent to the server, and the first media condition does not include the media type designation In this case, sending a second PUT request having a second media condition including media type designation to the server

   electronic device.
8. 8. The method of claim 7,

   The processor is

   extracting a rule corresponding to the function selected by the user from among the rules for the at least one function, and adding a media condition including a media type for which the electronic device requests a setting change to the extracted rule to add the second to generate a PUT request

   electronic device.
9. According to claim 1,

   The processor is

   In response to the success of the PUT operation corresponding to the first PUT request, whether the first media condition of the first PUT request includes a media type designation and the function of requesting a setting change in the first PUT request. It is saved as a history of successful PUT operation for the server.

   electronic device.
10. According to claim 1,

    The processor is

    In response to the failure of the PUT operation corresponding to the first PUT request, a response status code is received from the server, and when the received response status code is the first code, the second PUT request is sent to the server. to transmit

    electronic device.
11. A method implemented by a processor, comprising:

    transmitting a GET request according to the XCAP to the server in response to detecting a PUT attempt according to the XML Configuration Access Protocol (XCAP) of the user;

    transmitting a first PUT request according to XCAP to the server in response to receiving a reply to the GET request; and

    In response to the failure of the PUT operation corresponding to the first PUT request, transmitting a second PUT request having a second media condition different from a first media condition of the first PUT request to the server movement

    How to include.
12. 12. The method of claim 11,

    The operation of sending the GET request to the server is,

    Receiving a rule set including a rule for at least one function from the server receiving the GET request

    How to include.
13. 13. The method of claim 12,

    The operation of transmitting the first PUT request to the server comprises:

    determining whether there is a successful PUT operation for the function selected by the user among the at least one function from the successful PUT operation history associated with the server;

    When the successful PUT operation exists, determining whether a previous PUT request includes a media type designation, and generating and transmitting a third PUT request using the media type designation of the previous PUT request ; and

    When the successful PUT operation does not exist, extracting a rule corresponding to the selected function from among the rules for the at least one function, and generating and transmitting the first PUT request based on the extracted rule

    How to include.
14. 14. The method of claim 13,

    The operation of transmitting the first PUT request to the server comprises:

    Determining whether the extracted rule includes a media type designation, and generating and transmitting a first PUT request using the media type designation of the extracted rule

    How to include.
15. 12. The method of claim 11,

    Transmitting a second PUT request having the second media condition to the server includes:

    transmitting, to the server, a second PUT request having a second media condition in which the media type specification is excluded when the first media condition includes a media type specification; and

    When the first media condition does not include the media type designation, transmitting a second PUT request having a second media condition including the media type designation to the server

    How to include.

Images