Http-uri error recovery method and user equipment therefor

Abstract

The present application provides a method for HTTP-URI error recovery. The HTTP-URI error recovery method can be applied to a user equipment (UE). The HTTP-URI error recovery method comprises the following steps. The UE sends a first HTTP request with a first URI encoding scheme to an application server via an interface. Then, the UE receives a specific error response corresponding to the first HTTP request from the application server. Then, the UE sends a second HTTP request with a second URI encoding scheme to the application server based on the specific error response.

Description

TECHNICAL FIELD

[0001] The present application relates to wireless communication technology, and more particularly, to Hyper Text Transfer Protocol (HTTP)-Uniform Resource Identifier (URI) transmission technology. BACKGROUND

[0002] In the Internet Protocol (IP) Multimedia Subsystem (IMS), one of the main parts of multimedia telephony communication services is the supplementary services (e.g., call forwarding, call waiting, etc.) for User Equipment (UE). The service configuration of the supplementary services is stored in the application server in Extensible Markup Language (XML) format.

[0003] If the UE wants to change the configuration of a particular supplementary service, the UE can need to communicate with the application server through the Ut interface. When the UE wants to inquire or modify the status of the supplementary service, the UE initiates an XML Configuration Access Protocol (XCAP) Hyper Text Transfer Protocol (HTTP) request to the application server to obtain the latest status of the supplementary service. XCAP (XML Configuration Access Protocol) can be used to map XML document subtrees and element attributes to HTTP Uniform Resource Identifiers (URIs). The XCAP HTTP request URI can be constructed in a specific format defined in Request for Comment (RFC) standards and 3rd Generation Partnership Project (3GPP) standards.

[0004] However, when the UE receives an error response from the application server, it is usually difficult for the UE to detect what error has occurred due to different configurations of the application server by different operators. Identifying and solving the above problems requires a lot of effort and time. In addition, the URI character encoding problem is one of the most common problems.

[0005] Therefore, how to quickly recover from URI character encoding errors is a topic worth discussing. SUMMARY

[0006] The present application aims to provide a Hyper Text Transfer Protocol Uniform Resource Identifier error recovery method and user equipment thereof to solve the above problems.

[0007] Embodiments of the present disclosure provide a method for HTTP-URI error recovery. The method for HTTP-URI error recovery can be applied to a user equipment (UE). The method for HTTP-URI error recovery comprises the following steps. The UE sends a first HTTP request with a first URI encoding scheme to an application server via an interface. Then, the UE receives a specific error response corresponding to the first HTTP request from the application server. Then, the UE sends a second HTTP request with a second URI encoding scheme to the application server based on the specific error response.

[0008] In embodiments, the interface is a Ut interface.

[0009] In embodiments, the specific error response is a Bad Request error response, a NotFound error response, or a Conflict error response.

[0010] In embodiments, the first HTTP request and the second HTTP request comprise one or more specific characters. In embodiments, the first URI encoding scheme encodes the one or more specific characters in the first HTTP request based on a percent-encoding scheme, and the second URI encoding scheme does not encode the one or more specific characters in the second HTTP request based on the percent-encoding scheme. In another embodiment, the first URI encoding scheme does not encode the one or more specific characters in the first HTTP request based on a percent-encoding scheme, and the second URI encoding scheme encodes the one or more specific characters in the second HTTP request based on the percent-encoding scheme. In embodiments, the one or more specific characters comprise unsafe characters and / or reserved characters.

[0011] In embodiments, in the method for HTTP-URI error recovery, the UE can further receive a response corresponding to the second HTTP request from the application server; and determine whether the response is an error response. For the response not being the error response, the UE can record the second URI encoding scheme; and display a latest service status based on the response. For the response being the error response, the UE displays an error notification based on the response.

[0012] Embodiments of the present disclosure provide a user equipment for Hyper Text Transfer Protocol-Uniform Resource Identifier (HTTP-URI) error recovery. The UE includes a processor, a transmitter and a receiver. The processor is coupled to the transmitter and the receiver. The transmitter sends a first HTTP request with a first URI encoding scheme to an application server via an interface. The receiver receives a specific error response corresponding to the first HTTP request from the application server. The transmitter further sends a second HTTP request with a second URI encoding scheme to the application server based on the specific error response.

[0013] The HTTP-URI error recovery method and the user equipment thereof provided by the present disclosure can assist in quickly recovering from URI encoding errors. BRIEF DESCRIPTION OF DRAWINGS

[0014] The present disclosure can be more fully understood with reference to the following detailed description when taken in conjunction with the accompanying drawings, in which:

[0015] Figure 1 is a block diagram of a wireless communication system according to an embodiment of the present disclosure.

[0016] Figure 2 A procedure for HTTP-URI error recovery is described according to an embodiment of the present disclosure.

[0017] Figure 3 A procedure for HTTP-URI error recovery is described according to another embodiment of the present disclosure.

[0018] Figures 4A-4B is a flowchart of a HTTP-URI error recovery method described according to an embodiment of the present disclosure.

[0019] Figures 5A-5B is a flowchart of a HTTP-URI error recovery method described according to another embodiment of the present disclosure. DETAILED DESCRIPTION

[0020] Certain terms are used throughout the present description and claims to refer to particular components. As one skilled in the art will appreciate, manufacturers can refer to a component by different names. This document does not intend to distinguish between components that differ in name but not in function. In the following description and in the claims, the terms "include" and "comprise" are used in an open-ended fashion, and thus should be interpreted to mean "including, but not limited to." Also, the term "couple" or "coupled" as used herein is intended to mean either an indirect or direct electrical connection. Thus, if a first device couples to a second device, that connection can be through a direct electrical connection, or through an indirect electrical connection via other devices and connections.

[0021] The following description is of the best- mode embodiment of the application presently contemplated. Such description is not intended to limit the application in any way.

[0022] Figure 1 is a block diagram of a wireless communication system 100 according to an embodiment of the application. As shown, the wireless communication system 100 can include a user equipment (UE) 110, a network node 120, an application server 130, an Internet Protocol (IP) Multimedia Subsystem (IMS) core network 140, and an interface 150. It should be noted that for the purpose of clarifying the concepts of the present application, a simplified block diagram is presented, in which only elements relevant to the present application are shown. However, the present application should not be limited to what is shown. Figure 1 Figure 1 A simplified block diagram is presented, in which only elements relevant to the present application are shown. However, the present application should not be limited to what is shown. Figure 1

[0023] In an embodiment, the network node 120 can be a base station, a gNodeB (gNB), a NodeB (NB), an eNodeB (eNB), an access point, an access terminal, but the present application is not limited thereto. In an embodiment, the UE 110 can communicate with the network node 120 through a fifth generation (5G) communication technology or a 5G New Radio (NR) communication technology, but the present application should not be limited thereto.

[0024] In an embodiment, the application server 130 can handle supplementary services (e.g., call forwarding service, call waiting service, etc.) provided to the UE 110 in the IMS core network 140. Data associated with the supplementary services can be stored in the application server 130 in an extensible markup language (XML) format. The application server 130 can provide configuration and data associated with the supplementary services to the UE 110. In addition, the application server 130 can communicate with the UE 110 through the interface 150. In one embodiment, the interface 150 can be a Ut interface.

[0025] As​​Figure 1 As shown, the UE 110 can include at least a baseband signal processing device 111, a radio frequency (RF) signal processing device 112, a processor 113, a storage device 114, functional modules and circuits 115, and a display device 116.

[0026] In embodiments of the present application, the UE 110 can be a smart phone, a personal data assistant (PDA), a pager, a laptop computer, a desktop computer, a wireless handset, or any computing device that includes a wireless communication interface.

[0027] The RF signal processing device 112 can include a plurality of antennas to receive or transmit RF signals. The RF signal processing device 112 can receive RF signals through the antennas and process the received RF signals to convert the received RF signals to baseband signals for the baseband signal processing device 111 to process, or receive baseband signals from the baseband signal processing device 211 and convert the received baseband signals to radio frequency signals for transmission to a peer communication device. The RF signal processing device 112 can include a plurality of hardware elements to perform radio frequency conversion. For example, the RF signal processing device 112 can include a power amplifier, a mixer, an analog-to-digital converter (ADC) / digital-to-analog converter (DAC), etc.

[0028] The baseband signal processing device 111 can further process the baseband signals to obtain information or data transmitted by a peer communication device. The baseband signal processing device 111 can also include a plurality of hardware elements to perform baseband signal processing.

[0029] The processor 113 can control the operations of the baseband signal processing device 111 and the RF signal processing device 112. According to embodiments of the present application, the processor 113 can also be arranged to execute program codes of the software modules corresponding to the baseband signal processing device 111 and / or the RF signal processing device 112. In execution, the program codes with specific data in the data structure can also be referred to as processor logic units or stack instances. Thus, the processor 113 can be regarded as composed of a plurality of processor logic units, each of which is used to perform one or more specific functions or tasks of the corresponding software module.

[0030] The storage device 114 can store software and firmware program codes, system data, user data, etc. of the UE 110. The storage device 114 can be a volatile memory, such as a random access memory (RAM); can be a non-volatile memory, such as a flash memory or a read-only memory (ROM); can be a hard disk or any combination thereof.

[0031] According to embodiments of the present application, the RF signal processing device 112 and the baseband signal processing device 111 can be collectively referred to as a radio module capable of communicating with a wireless network to provide wireless communication services in compliance with a predetermined radio access technology (RAT). Notably, in embodiments of the present application, the UE 110 can be further extended to include multiple antennas and / or multiple radio modules, and the present application should not be limited to Figure 1 the content shown.

[0032] The functional modules and circuits 115 can include an encoding module 1151 and a determining module 1152. The processor 113 can execute different modules or circuits in the functional modules and circuits 115 to perform embodiments of the present application. In embodiments of the present application, the encoding module 1151 can encode specific characters in a hypertext transfer protocol (HTTP) request based on a uniform resource identifier (URI) encoding scheme. The determining module 1152 can determine whether a response to the HTTP request from the application server 130 is an error response, and determine whether the error response is a specific (or predefined) error response.

[0033] The display device 116 can be a liquid crystal display (LCD), a light emitting diode (LED) display, an organic LED (OLED) display, or an electronic paper display (EPD), etc., for providing a display function. Alternatively, the display device 116 can also include one or more touch sensors for sensing a touch, contact, or proximity of an object such as a finger or a stylus.

[0034] According to embodiments of the present application, when the UE 110 wants to inquire or modify the status of a supplementary service (e.g., a call forwarding service), the UE 110 can initiate (or send) a first HTTP request 130 to the application server through the interface 150 (i.e., the Ut interface) to obtain the latest status of the supplementary service. Specifically, the UE 110 can construct a URI of the first HTTP request based on a specific encoding or format defined in the XML configuration access protocol (XCAP). In one embodiment, after the UE 110 constructs the URI of the first HTTP request, the UE 110 can also construct a header and data of the first HTTP request. After the UE 110 constructs the first HTTP request, the UE 110 can send the first HTTP request to the application server 130 through the interface 150 (i.e., the Ut interface).

[0035] The constructed URI of the first HTTP request can include one or more special characters (e.g., plus sign +, @, space sign, double quote "", left square bracket [, right square bracket ], etc.). In the constructed URI of the first HTTP request, the special characters can be encoded by the UE 110 based on a URI encoding scheme. In one embodiment, the URI encoding scheme can be to encode the special characters in the first HTTP request based on percent encoding (e.g., + is encoded as %2B based on percent encoding). In another embodiment, the URI encoding scheme can be to not encode the special characters in the first HTTP request based on percent encoding (e.g., + is not encoded as %2B based on percent encoding).

[0036] When the application server 130 receives the first HTTP request, the application server 130 can send a response to the first HTTP request to the UE 110. When the response is a specific (or predefined) error response, the UE 110 can send a second HTTP request to the application server 130 through the interface 150. In embodiments of the present application, the specific error response can be a Bad Request error response, a Not Found error response, or a Conflict error response, but the present application is not limited thereto. The type of the specific error response can be predefined for URI error recovery.

[0037] When the UE 110 receives the response to the second HTTP request from the application server 130, the UE 110 can determine whether the response is an error response (which can be the specific error response or not). When the response is not an error response (i.e., the second HTTP request is successful), the UE 110 can record the second encoding scheme. That is, the UE 110 can employ the second encoding scheme for future HTTP requests. Then, the UE 110 can display the latest service status based on the response through the display device 116, or perform a subsequent operation associated with the supplemental service. When the response is an error response (i.e., the second HTTP request is not successful), the UE 110 can display an error notification based on the response through the display device 116.

[0038] The UE 110 can also construct the URI of the second HTTP request based on a particular encoding or format defined in the XCAP protocol. The constructed URI of the second HTTP request can include one or more particular characters (e.g., plus sign +, @, space number, double quote "", left square bracket [, right square bracket ], etc.). Specifically, in the constructed URI of the second HTTP request, the particular characters can be encoded by the UE 110 based on another URI encoding scheme that is different from the URI encoding scheme used to encode the particular characters in the URI of the first HTTP request. That is, the UE 110 can encode the particular characters of the first HTTP request using the other URI encoding scheme to generate the second HTTP request. In one embodiment, the URI encoding scheme of the second HTTP request can be to encode the particular characters in the second HTTP request based on percent encoding (e.g., + is encoded as %2B according to percent encoding). In another embodiment, the URI encoding scheme of the second HTTP request can be to not encode the particular characters in the second HTTP request based on percent encoding (e.g., + is not encoded as %2B according to percent encoding).

[0039] In embodiments of the present application, the particular characters in the first and second HTTP requests can be unsafe characters and / or reserved characters defined in the RFC 1738 standard.

[0040] Figure 2 A procedure for HTTP-URI error recovery is described in accordance with embodiments of the present application. In step S210, the UE 210 sends a first HTTP request with a first URI encoding scheme to the application server 230. In this embodiment, the first URI encoding scheme is to encode particular characters in the first HTTP request based on percent encoding (e.g., + is encoded as %2B according to percent encoding).

[0041] In step S220, the UE 210 receives a particular error response (e.g., a Bad Request error response, a Not Found error response, or a Conflict error response) from the application server 230.

[0042] In step S230, the UE 210 sends a second HTTP request with a second URI encoding scheme to the application server 230. In this embodiment, the second URI encoding scheme is to not encode one or more particular characters in the second HTTP request according to percent encoding (e.g., + is not encoded as %2B according to percent encoding).

[0043] In step S240 , when the second HTTP request is successful, the application server 230 may send a confirmation response (eg, 200 OK) to the UE 210 .

[0044] Figure 3 According to another embodiment of the present invention, a process for HTTP-URI error recovery is described. In step S310, UE 310 sends a first HTTP request using a first URI encoding scheme to application server 230. In this embodiment, the first URI encoding scheme does not percent-encode certain characters in the first HTTP request (e.g., + is not percent-encoded as %2B).

[0045] In step S320 , UE 310 receives a specific error response (eg, a Bad Request error response, a Not Found error response, or a Conflict error response) from application server 330 .

[0046] In step S330, UE 310 sends a second HTTP request with a second URI encoding scheme to application server 330. In this embodiment, the second URI encoding scheme encodes one or more specific characters in the second HTTP request based on the percent encoding method (for example, encoding + as %2B according to the percent encoding method).

[0047] In step S340 , when the second HTTP request is successful, the application server 230 may send a confirmation response (eg, 200 OK) to the UE 210 .

[0048] Figures 4A-4B FIG. 1 is a flowchart of an HTTP-URI error recovery method according to an embodiment of the present invention. The HTTP-URI error recovery method can be applied to the communication system 100. Figures 4A-4B As shown, in step S401, UE 110 may construct the URI of the first HTTP request using a first URI encoding scheme. In this embodiment, the first URI encoding scheme encodes specific characters in the first HTTP request based on a percent encoding scheme (for example, + is encoded as %2B according to the percent encoding scheme). In this embodiment, after UE 110 constructs the URI of the first HTTP request, UE 110 may further construct the header and data of the first HTTP request.

[0049] In step S402 , UE 110 may send a first HTTP request having a first URI encoding scheme to application server 130 through interface 150 (ie, Ut interface).

[0050] In step S403, the UE 110 can receive, from the application server 130, a response corresponding to the first HTTP request.

[0051] In step S404, the UE 110 can determine whether the response is an error response.

[0052] If the response is not an error response, step S405 is performed. In step S405, the UE 110 can display the latest service status or perform a subsequent operation associated with the supplementary service.

[0053] If the response is an error response, step S406 is performed. In step S406, the UE 110 can determine whether the response is a specific error response (e.g., a Bad Request error response, a Not Found error response, or a Conflict error response).

[0054] If the error response is not the specific error response, step S407 is performed. In step S407, the UE 110 can display an error notification.

[0055] If the error response is the specific error response, step S408 is performed. In step S408, the UE 110 can construct a URI of a second HTTP request with a second URI encoding scheme. In the present embodiment, the second URI encoding scheme is not to percent-encode the specific character in the second HTTP request (e.g., not to encode + as %2B according to the percent-encoding manner).

[0056] In step S409, the UE 110 can send, to the application server 130 through the interface 150 (i.e., the Ut interface), the second HTTP request with the second URI encoding scheme.

[0057] In step S410, the UE 110 can receive, from the application server 130, a response corresponding to the second HTTP request.

[0058] In step S411, the UE 110 can determine whether the response is an error response.

[0059] If the response is not an error response, step S412 is performed. In step S412, the UE 110 can record the second URI encoding scheme. Then, in step S413, the UE 110 can display the latest service status or perform a subsequent operation associated with the supplementary service.

[0060] If the response is an error response, step S414 is performed. In step S414, the UE 110 can display an error notification.

[0061] Figures 5A-5Bis a flowchart illustrating an HTTP-URI error recovery method according to another embodiment of the present application. The HTTP-URI error recovery method can be applied to the communication system 100. As shown in Figures 5A-5B In step S501, the UE 110 can construct a URI of a first HTTP request using a first URI encoding scheme. In this embodiment, the first URI encoding scheme is not to percent-encode a specific character in the first HTTP request (e.g., not to encode + as %2B according to the percent-encoding scheme). In this embodiment, after the UE 110 constructs the URI of the first HTTP request, the UE 110 can further construct a header and data of the first HTTP request.

[0062] In step S502, the UE 110 can send the first HTTP request with the first URI encoding scheme to the application server 130 through the interface 150 (i.e., the Ut interface).

[0063] In step S503, the UE 110 can receive a response corresponding to the first HTTP request from the application server 130.

[0064] In step S504, the UE 110 can determine whether the response is an error response.

[0065] If the response is not an error response, step S505 is performed. In step S505, the UE 110 can display the latest service status or perform a subsequent operation associated with the supplementary service.

[0066] If the response is an error response, step S506 is performed. In step S506, the UE 110 can determine whether the response is a specific error response (e.g., a Bad Request error response, a Not Found error response, or a Conflict error response).

[0067] If the error response is not the specific error response, step S507 is performed. In step S507, the UE 110 can display an error notification.

[0068] If the error response is the specific error response, step S508 is performed. In step S508, the UE 110 can construct a URI of a second HTTP request using a second URI encoding scheme. In this embodiment, the second URI encoding scheme is not to encode a specific character in the second HTTP request according to the percent-encoding scheme (e.g., not to encode + as %2B according to the percent-encoding scheme).

[0069] In step S509, the UE 110 can send the second HTTP request with the second URI encoding scheme to the application server 130 through the interface 150 (i.e., the Ut interface).

[0070] In step S510, the UE 110 can receive a response corresponding to the second HTTP request from the application server 130.

[0071] In step S511, the UE 110 can determine whether the response is an error response.

[0072] If the response is not an error response, step S512 is performed. In step S512, the UE 110 can record the second encoding scheme. Then, in step S513, the UE 110 can display the latest service status or perform a subsequent operation associated with the supplementary service.

[0073] If the response is an error response, step S514 is performed. In step S514, the UE 110 can display an error notification.

[0074] In the HTTP-URI error recovery method provided by the present disclosure, when the UE receives a specific error response (e.g., a BadRequest error response, a NotFound error response, or a Conflict error response), an encoding error of a specific character in the HTTP request can be determined.

[0075] The method steps associated with the above disclosure can be implemented directly by hardware, software modules executed by a processor, or a combination of both. Software modules (e.g., containing executable instructions and related data) and other data can be stored in a data storage, such as a RAM memory, a flash memory, a ROM memory, an EPROM memory, an EEPROM memory, a register, a hard disk, a removable disk, a CD-ROM, or other computer-readable storage media known in the art. An example storage medium can be coupled to a machine, such as a computer / processor (for convenience, which can be referred to as a "processor"). The processor can read information (e.g., code) from the storage medium and write information to the storage medium. The example storage medium can be built into the processor. The processor and the storage medium can be located in an ASIC. The ASIC can be located in a user device. In an alternative design, the processor and the storage medium can be separate elements in the user device. Furthermore, in many aspects, any suitable computer program product can include a computer-readable medium containing code associated with one or more aspects of the present disclosure. In many aspects, a computer software product includes packaging materials.

[0076] In several embodiments provided by the present application, it should be understood that the disclosed system, device and method can be implemented by other methods. The above-mentioned device embodiments are only exemplary, for example, the division of units is only a logical function division, and there can be other divisions in actual implementation. For example, a plurality of units or elements can be combined or integrated into another system, or some features can be omitted or not implemented. In addition, the mutual coupling or direct coupling or communication connection shown or discussed can be indirect coupling or communication connection through some interfaces, devices or units, and can be electrical, mechanical or other forms.

[0077] Although the present application has been described in terms of preferred embodiments, it is to be understood that the application is not limited to those embodiments. Variations and modifications to those embodiments can be affected by persons skilled in the art without deviating from the scope and spirit of the application. Therefore, the scope of the application should be defined by the appended claims and their equivalents.

Claims

1. A method for HTTP URI error recovery, comprising: sending, by a user equipment, a first HTTP request with a first URI encoding scheme to an application server via an interface; receiving, by the user equipment, a specific error response corresponding to the first HTTP request from the application server; sending, by the user equipment, a second HTTP request with a second URI encoding scheme to the application server based on the specific error response, wherein the first URI encoding scheme and the second URI encoding scheme are different, the first HTTP request and the second HTTP request contain one or more specific characters; receiving, by the user equipment, a response corresponding to the second HTTP request from the application server; determining, by the user equipment, whether the response is an error response; and for the response not being the error response, recording, by the user equipment, the second URI encoding scheme; and displaying, by the user equipment, a latest service status based on the response.

2. The HTTP URI error recovery method of claim 1, wherein, The interface is a Ut interface.

3. The HTTP URI error recovery method of claim 1, wherein, The specific error response is a bad request error response, a not found error response or a conflict error response.

4. The HTTP URI error recovery method of claim 1, wherein, The first URI encoding scheme encodes the one or more specific characters in the first HTTP request based on a percent encoding scheme, and the second URI encoding scheme encodes the one or more specific characters in the second HTTP request not based on the percent encoding scheme.

5. The HTTP URI error recovery method of claim 1, wherein, The first URI encoding scheme encodes the one or more specific characters in the first HTTP request not based on a percent encoding scheme, and the second URI encoding scheme encodes the one or more specific characters in the second HTTP request based on the percent encoding scheme.

6. The HTTP URI error recovery method of claim 1, wherein, The one or more specific characters contain unsafe characters and / or reserved characters.

7. The HTTP URI error recovery method of claim 1, wherein, Further comprising: for the response being the error response, displaying, by the user equipment, an error notification based on the response. 8.A user equipment for HTTP URI error recovery, comprising: a transmitter configured to send a first HTTP request with a first URI encoding scheme to an application server via an interface; a receiver configured to receive a specific error response corresponding to the first HTTP request from the application server; and a processor coupled to the transmitter and the receiver; ​ wherein, based on the particular error response, the transmitter transmits a second hypertext transfer protocol request having a second uniform resource identifier encoding scheme to the application server, wherein the first uniform resource identifier encoding scheme and the second uniform resource identifier encoding scheme are different, the first hypertext transfer protocol request and the second hypertext transfer protocol request contain one or more particular characters, wherein, by the receiver, a response corresponding to the second hypertext transfer protocol request is received from the application server; by the processor, it is determined whether the response is an error response; and for the response not being the error response, by the processor and the memory, the second uniform resource identifier encoding scheme is recorded and a latest service status is displayed based on the response.

9. The user device for Hypertext Transfer Protocol Uniform Resource Identifier error recovery of claim 8, wherein, The interface is a Ut interface.

10. The user device for Hypertext Transfer Protocol Uniform Resource Identifier error recovery of claim 8, wherein, The particular error response is a bad request error response, a not found error response, or a conflict error response.

11. The user device for Hypertext Transfer Protocol Uniform Resource Identifier error recovery of claim 8, wherein, The first uniform resource identifier encoding scheme encodes the one or more particular characters in the first hypertext transfer protocol request based on a percent encoding scheme, and the second uniform resource identifier encoding scheme encodes the one or more particular characters in the second hypertext transfer protocol request not based on the percent encoding scheme.

12. The user device for Hypertext Transfer Protocol Uniform Resource Identifier error recovery of claim 8, wherein, The first uniform resource identifier encoding scheme encodes the one or more particular characters in the first hypertext transfer protocol request not based on a percent encoding scheme, and the second uniform resource identifier encoding scheme encodes the one or more particular characters in the second hypertext transfer protocol request based on the percent encoding scheme.

13. The user device for Hypertext Transfer Protocol Uniform Resource Identifier error recovery of claim 8, wherein, The one or more particular characters contain an unsafe character and / or a reserved character.

14. The user device for Hypertext Transfer Protocol Uniform Resource Identifier error recovery of claim 8, wherein, Further comprising: a display device, for the response being the error response, displaying an error notification based on the response.

Images