EP2456144B1 - Method, device and system for identifying a service - Google Patents
Method, device and system for identifying a service Download PDFInfo
- Publication number
- EP2456144B1 EP2456144B1 EP12155573.4A EP12155573A EP2456144B1 EP 2456144 B1 EP2456144 B1 EP 2456144B1 EP 12155573 A EP12155573 A EP 12155573A EP 2456144 B1 EP2456144 B1 EP 2456144B1
- Authority
- EP
- European Patent Office
- Prior art keywords
- service
- service request
- request
- type
- url address
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active
Links
- 238000000034 method Methods 0.000 title claims description 43
- 230000008569 process Effects 0.000 claims description 17
- 230000004044 response Effects 0.000 description 6
- 230000002411 adverse Effects 0.000 description 2
- 230000005540 biological transmission Effects 0.000 description 2
- 238000004891 communication Methods 0.000 description 2
- 238000010586 diagram Methods 0.000 description 2
- 238000005516 engineering process Methods 0.000 description 2
- 238000013507 mapping Methods 0.000 description 2
- 230000011664 signaling Effects 0.000 description 2
- 230000008859 change Effects 0.000 description 1
- 230000001419 dependent effect Effects 0.000 description 1
- 230000002708 enhancing effect Effects 0.000 description 1
- 230000000977 initiatory effect Effects 0.000 description 1
- 230000006855 networking Effects 0.000 description 1
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W80/00—Wireless network protocols or protocol adaptations to wireless operation
- H04W80/08—Upper layer protocols
- H04W80/12—Application layer protocols, e.g. WAP [Wireless Application Protocol]
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L61/00—Network arrangements, protocols or services for addressing or naming
- H04L61/30—Managing network names, e.g. use of aliases or nicknames
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/50—Network services
- H04L67/51—Discovery or management thereof, e.g. service location protocol [SLP] or web services
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L2101/00—Indexing scheme associated with group H04L61/00
- H04L2101/30—Types of network names
- H04L2101/375—Access point names [APN]
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L51/00—User-to-user messaging in packet-switching networks, transmitted according to store-and-forward or real-time protocols, e.g. e-mail
- H04L51/58—Message adaptation for wireless communication
Definitions
- the present invention relates to a communication technology field, and particularly to a method, device and system for identifying a service.
- a user needs to contact a service provider when initiating a service request.
- the service provider provides services in response to the service request.
- MMS multimedia messaging service
- the user may initiate a service request for a multimedia messaging service (MMS) via a terminal such as a cell phone.
- MMS multimedia messaging service
- WAP GW wireless application protocol gateway
- API access point name
- the address of a service gateway should also be configured correctly at the same time. When all these parameters are configured correctly, the object of the service request may be realized.
- Patent application EP 1677462 Al discloses a system that implements robust service discovery in dynamic networks. It defines a relevance field, for a given service type, over the nodes of the network, namely by attributing, to each node, a relevance value phi(n). The relevance field is defined such that it has local maxima, each of which corresponds to a node (j1, j2) offering the given service type.
- the present disclosure provides a method, device and system for identifying a service which enables a service request to be identified correctly and hence transmitting the multimedia messaging service correctly even when a terminal is configured wrongly.
- a first aspect of embodiment of the disclosure provides a method for processing a service request, comprising:
- An second aspect of the disclosure discloses an application protocol gateway, comprising:
- a service content type for indicating a service type of the service request is included in the service request.
- the service type of the service request may also be determined according to the service content type, thereby realizing service normally. For example, after receiving a service request, if the service gateway address is configured by the terminal wrongly, the service request is determined according to the service content type and corresponding service flow is carried out. For example, when it is the MMS service, the service request is processed according to the MMS service flow, therefore realizing MMS service and providing better insurance for realizing service successfully.
- the multimedia message is a message that includes text, picture, video and audio contents, which is an enhancement of a short message service. If a user wants to use the MMS, he/she needs to configure an IP address and a port of the WAP GW and the APN on the cell phone terminal, and meanwhile configuring the address of the service gateway correctly is needed. After all the three parameters are configured correctly, the multimedia message can be transmitted correctly.
- a typical service gateway is for example the MMSC. If an operator deploys a plurality of MMSCs, the MMSCs are interconnected. When a user transmits an MMS message, a home MMSC is typically used for providing service. In this time, the WAP GW is needed to forward the service request to the home MMSC of the user.
- the WAP GW In order to realize the forwarding by the WAP GW, it needs to inquire an electronic numbers to uniform resource identifier (URI) mapping (ENUM) server to acquire the home MMSC of the user according to the address of the MMSC reported by a terminal of the user.
- URI uniform resource identifier
- ENUM electronic number to uniform resource identifier mapping
- An example procedure may be described as follows: a user may be roamed from home province B to province A and transmits a service request for accessing an MMS from a visited (namely roamed)WAP GW ; the visited WAP GW may receive the service request for accessing an MMS transmitted by the user, and inquire the ENUM server to acquire the uniform resource locator (URL) address of the home MMSC of the user (hereinafter referred to as a URL address); the visited WAP GW may transmit directly the service request for accessing an MMS to the home MMSC of the user; and, the home MMSC of the user may return an MMS message transmission response.
- URL uniform resource locator
- a terminal 100 may transmit an M-Send.req request message to a WAP GW 500 by taking a WAP as a carrying protocol.
- the terminal 100 is referred to as a sender terminal that is configured with the address of an MMSC.
- the WAP GW 500 may receive the request message from the terminal 100 and resolves the URL address included in the service request. If the address is http://mmsc.monternet.com, it is regarded that the service request is a multimedia messaging service request, and the user identification of the sender is obtained from the service request and an inquiry that the address of the home MMSC of the sender is retrieved from the ENUM server 300 is initiated.
- the ENUM server 300 may return to the WAP GW 500 an inquiry result including the address of the home MMSC of the sender.
- the WAP GW 500 may forward the M-Send.Req request message to the home MMSC 400 of the sender, to request to transmit the multimedia message.
- the home MMSC 400 of the sender may respond to the request message of the WAP GW 500 and incorporate an M-Send.conf in the response to indicate that the request has been accepted.
- the WAP GW 500 may forward the M-Send.conf to the terminal 100.
- the processing procedure for a person information management (PIM) service is the same with the above embodiment of transmitting multimedia messages.
- the PIM service may be mainly for synchronization of data such as a telephone directory, a scheduling table and an album between a cell phone terminal and the PIM server. For example, with synchronization operation on the telephone directory, a user may synchronize phone numbers on the terminal of the user to the PIM server.
- the processing procedure for the PIM service is similar to that of the MMS service.
- the WAP GW may receive the request message from the terminal and resolve the URL address included in the service request. If it is determined that the service to be executed is the PIM service, the ENUM server is inquired to acquire the address of the home PIM server of the user and the service request is forwarded to the home PIM server of the user by the WAP GW. However, if the terminal is configured with a wrong URL address, the WAP GW will identify wrongly and fail to process the service request as the PIM service. Thus the purpose of the service request can not be realized, which brings poor experience to users and is adverse for the carrier to actively promote services.
- An embodiment of the present invention provides a technical solution in which the WAP GW may respond normally to a service request, identify a service correctly and implement service process according to the service request even when the terminal is configured with the wrong address of the service gateway.
- a service content type included in the service request may be also incorporated as one of identifying features for the WAP GW, so that the WAP GW may identify the service request not only according to the URL address of the service request but also according to the type of service contents included in the service request such as content information included in the Content-Type field of the service request.
- an embodiment of the present invention provides a method for identifying services, and the method may include the following steps.
- a service type of the service request is identified according to a service content type included in the service request, when the determination result indicates that the URL address matches no service flow.
- a visited application protocol gateway may receive the service request of a roaming user and determine whether the URL address included in the service request is the URL address of an MMSC. If the URL address included in the service request is the URL address of the MMSC, the process proceeds to the process procedure of prior art. If the URL address included in the service request is not the URL address of the MMSC, the service type of the service request is identified according to the service content type included in the service request.
- a request for inquiring the address of the service server corresponding to the identified service type is transmitted after the service type of the service request is identified. For example, when the identified service type is the service request for the multimedia message, a request for inquiring the address of the home MMSC of the sender of the service request is transmitted.
- the above-mentioned step that whether the URL address matches a service flow is determined may further include the following steps: whether the URL address is the URL address of the MMSC or the address of the home PIM server of the user is determined; If the URL address is the URL address of the MMSC, the process proceeds to the MMS service procedure; and If the URL address is the address of the home PIM server of the user, the process proceeds to the PIM service procedure.
- the type of service content included in the service request may be information included in a field of the service request and the field may be for example the Content-Type field.
- S201 The service request from the roaming user is received by the visited WAP GW .
- S204 Whether the service request is the MMS is identified continually according to the service content type included in the service request.
- the included service content type is for example the content in the Content-Type field. If the content is the service content type of the MMS, for example, the content is "Application/vnd.wap. mms-message", it is determined that the service request is an MMS request.
- a determination feature may be further added, and the following is an example.
- the MMS service request is a request for transmitting MMS service and the content information type of the Content-Type field is the MMS. For example, if a content of a method field in the service request is "m-send-req", it is determined that the service request is the MMS service request.
- a determination step may also be added in an embodiment of the present invention.
- the request for inquiring the address of the home MMSC of the user is transmitted to the ENUM server when the service route table is matched successfully according to multipurpose internet mail extensions (MIME).
- MIME multipurpose internet mail extensions
- An MIME message may include text, image, voice, video and data specific to other application programs.
- S206 The request for inquiring the address of the home MMSC of the user is transmitted to the ENUM server if the WAP GW determines that the service request satisfying the above-mentioned conditions is the MMS service request.
- the WAP GW can determine and identify correctly the service type by the service content type and carry out subsequent steps for implementing the MMS even when the address of the service gateway is configured wrongly in the terminal.
- the user's service request is correctly realized, the user's experience is satisfied well, which is equivalent to enhancing the fault tolerant processing capacity of the WAP GW and is advantageous for the operator's service promotion.
- the Content-type field in the service request may be extended to facilitate the WAP GW to correctly identify the service type corresponding to the service request.
- the PIM service is taken as an example below.
- the visited WAP GW may resolve the URL address included in the service request after receiving the service request from the roaming user.
- Whether the URL address is the URL address of the PIM service is determined. If it is determined that the URL address is not the URL address of the PIM service, whether the service request is the PIM service is identified according to the service content type included in the service request.
- the included service content type may be for example the content in the included Content-Type field. If the content is the content type of the PIM service, it is determined that the service request is the PIM service request. Subsequent processing steps are carried out according to the prior art PIM service procedure.
- An embodiment of the present invention may also provide a application protocol gateway such as a WAP GW.
- the WAP GW 500 includes a receiving unit 501, a determining unit 502, and a resolving unit 503.
- the receiving unit 501 is configured to receive a service request including a URL address.
- the determining unit 502 is configured to determine whether the URL address matches a service flow.
- the resolving unit 503 is configured to resolve the service content type included in the service request to identify the service type of the service request when the determination result of the determining unit 502 indicates that the URL address matches no service flow.
- the determining unit 502 may determine whether the URL address matches a service flow. Further, the determining unit 502 may determine whether the URL address included in the service request is the URL address of the MMSC or the address of the home PIM server of the user.
- the resolution result of the resolving unit 503 may include the service content type to which the service request belongs, for example the MMS service or the PIM service.
- the WAP GW 500 may further include a transmitting unit 504 configured to transmit a request for inquiring the address of the service server corresponding to the identified service type. For example, when the resolution result is the MMS service, the transmitting unit 504 may transmit to the ENUM server 300 a request for inquiring the address of the home MMSC of the user.
- the WAP GW 500 in the procedure of processing the service request may be described as follows.
- the WAP GW 500 may typically be the visited WAP GW .
- the resolving unit 503 may resolve the service content type included in the service request.
- the determining unit 502 may determine whether the URL address included in the service request is the URL address of the MMSC such as "http://mmsc.monternet.com". If it is determined that the URL address included in the service request is not the URL address of the MMSC, the resolving unit may resolve the service content type included in the service request, and the service type of the service request is identified according to the resolution result (namely the service content type).
- the service type of the service request is the MMS service
- the fault toleration capability of the WAP GW may be enhanced.
- the addition of determination feature may increase probability of identifying the service type correctly and better ensure normal operation of the service. And it is easier to implement with lower cost.
- An embodiment of the present invention may also provide a service processing system including a terminal, an application protocol gateway and an application server.
- the terminal is configured to transmit a service request including a field identifying the service content type of the service request.
- the application protocol gateway may be for example the WAP GW 500 shown in Fig. 5 and is configured to resolve the service request transmitted by the terminal, identify the service type of the service request according to the field of the service content type and process service procedure according to the identified service type.
- the application server may be for example the ENUM server 300 shown in Fig. 5 and is configured to receive the inquiry request from the application protocol gateway and inquire the address of the service server corresponding to the identified service type.
- the inquiring the address of the service server corresponding to the identified service type is further described as follows: Referring to Fig. 5 , for example, when the service type identified by the WAP GW 500 is the MMS service, the ENUM server 300 may receive from the WAP GW 500 the request for inquiring the address of the home MMSC of the user and return to the WAP GW 500 an inquiry result including the address of the home MMSC of the user.
- the server corresponding to the MMS service is the home MMSC of the user.
- the ENUM server 300 is inquired to acquire the address of the home PIM server of the user, and the WAP GW 500 may forward the service request to the home PIM server of the user.
- the service server corresponding to PIM service is the PIM server.
- the WAP GW 500 may further include a receiving unit 501, a determining unit 502 and a resolving unit 503.
- the receiving unit 501 is configured to receive a service request including a URL address.
- the determining unit 502 is configured to determine whether the URL address matches a service flow.
- the resolving unit 503 is configured to resolve the service content type included in the service request and identify the service type of the service request when the determination result of the determining unit 502 indicates that the URL address matches no service flow.
- the determining unit 502 may determine whether the URL address matches a service flow. Further, the determining unit 502 may determine whether the URL address included in the service request is the URL address of the MMSC or the address of the home PIM server of the user.
- the resolution result of the resolving unit 503 may include the service content type to which the service request belongs, for example the MMS service or the PIM service.
- the WAP GW 500 may further include a transmitting unit 504 configured to transmit a request for inquiring the address of the service server corresponding to the identified service type. For example, when the resolution result is the MMS service, the transmitting unit 504 may transmit to the ENUM server 300 a request for inquiring the address of the home MMSC of the user.
- service content type is identified correctly, which may enhance the fault toleration capability of application protocol gateway, improve the system's capability of processing service and realize user's service request. And they are easier to implement with lower cost and with little change for networking structure of the overall system.
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Mobile Radio Communication Systems (AREA)
- Data Exchanges In Wide-Area Networks (AREA)
- Telephonic Communication Services (AREA)
Description
- The present invention relates to a communication technology field, and particularly to a method, device and system for identifying a service.
- In the communication technology field, a user needs to contact a service provider when initiating a service request. When the service request meets conditions, the service provider provides services in response to the service request. For example, in data services, the user may initiate a service request for a multimedia messaging service (MMS) via a terminal such as a cell phone. In order to contact the service provider, an IP address and a port of a wireless application protocol gateway (WAP GW) as well as an access point name (APN) need to be configured in the cell phone. The address of a service gateway should also be configured correctly at the same time. When all these parameters are configured correctly, the object of the service request may be realized.
- The inventor of the present invention found in the process of studying and practicing the above prior art that the system may typically take the address and the port of the WAP GW as default and the APN may be identified automatically, but the service request can not be realized correctly when the address of the service gateway is configured wrongly. This means that the prior art has the following disadvantages: Correct configuration of the address of the service gateway becomes a prerequisite for transmitting multimedia messages correctly and the service of transmitting multimedia messages can not be achieved when the address of the service gateway is configured wrongly in the terminal.
Patent applicationEP 1677462 Al discloses a system that implements robust service discovery in dynamic networks. It defines a relevance field, for a given service type, over the nodes of the network, namely by attributing, to each node, a relevance value phi(n). The relevance field is defined such that it has local maxima, each of which corresponds to a node (j1, j2) offering the given service type. - The present disclosure provides a method, device and system for identifying a service which enables a service request to be identified correctly and hence transmitting the multimedia messaging service correctly even when a terminal is configured wrongly.
- A first aspect of embodiment of the disclosure provides a method for processing a service request, comprising:
- receiving, by a WAP gateway, a service request from a terminal including a URL address and a service content type of the service request, wherein the URL address is configured on the terminal; and
- when the URL address is correctly configured on the terminal, identifying, by the WAP gateway, a service type of the service request according to the URL address;
- when the URL address is wrongly configured on the terminal, identifying, by the WAP gateway, a service type of the service request according to the service content type included in the service request;
- executing a corresponding service process according to the identified service type of the service request
- An second aspect of the disclosure discloses an application protocol gateway, comprising:
- a receiving unit, configured to receive a service request from a terminal including a URL address and a service content type of the service request, wherein the URL address is configured on the terminal; and
- a determining unit configured to determine whether the URL address is correctly configured on the terminal;
- a resolving unit, configured to when the URL address is correctly configured on the terminal, to identify a service type of the service request according to the URL address; when the URL address is wrongly configured on the terminal, to identify a service type of the service request according to the service content type included in the service request;
- an executing unit, configured to execute a corresponding service process according to the identified service type of the service request.
- Other preferred embodiments are provided according to dependent claims 2-5, and 7-10.
- With the technical solutions described in embodiments of the present invention, a service content type for indicating a service type of the service request is included in the service request. When the service gateway is configured wrongly in the terminal, the service type of the service request may also be determined according to the service content type, thereby realizing service normally. For example, after receiving a service request, if the service gateway address is configured by the terminal wrongly, the service request is determined according to the service content type and corresponding service flow is carried out. For example, when it is the MMS service, the service request is processed according to the MMS service flow, therefore realizing MMS service and providing better insurance for realizing service successfully.
- In order to make the technical problems to be solved in the present invention, the adopted technical solution and advantages clearer, the present invention will be described further in detail with reference to accompanying drawings and in conjunction with embodiments. It should be appreciated that all the drawings are not necessarily drawn to scale and not intended to limit the present invention. In the drawings:
-
Fig. 1 is an architecture diagram of a service implementing system in prior art; -
Fig. 2 is a signaling flow chart of implementing multimedia messaging service in prior art on the basis ofFig. 1 ; -
Fig. 3 is a flow chart of the method for identifying a service according to an embodiment of the present invention; -
Fig. 4 is a flow chart of the method for identifying a service according to another embodiment of the present invention; and -
Fig. 5 is an architecture diagram of the service processing system including an application protocol gateway according to an embodiment of the present invention. - Technical solutions of the present invention will be described further with reference to embodiments below.
- For convenience of description, definitions and functions of messages involved in embodiments of the present invention is described briefly here. What described here are only general meanings and common standard specifications should be referred for improper description here. The description here is not intended to limit the invention.
- The following are definitions and functions of messages involved in embodiments of the present invention:
- M-Send.req, a message submitted to a multimedia message service center (MMSC) by a sender terminal via a WAP GW;
- M-Send.conf, a response message returned to the sender terminal by the MMSC after receiving the message submitted by the sender terminal;
- M-Notification.ind, a push notification message for notifying a receiver terminal to get a message from the MMSC, which is transmitted to the receiver terminal by the MMSC after receiving the multimedia message submitted by the sender terminal;
- M-NotifyResp.ind, a message for indicating whether the multimedia message is received successfully, which is sent to the MMSC by the receiver terminal;
- M_GET_REQ, transmitted by the receiver terminal to the MMSC, which instructs to retrieve the multimedia message;
- M-Retrieve.req, transmitted by the receiver terminal to the MMSC, which instructs to request to retrieve the multimedia message;
- M-Retrieve.conf, a response message returned by the MMSC after receiving the GET message from the receiver terminal; and
- M-Acknowledge.ind, a message for indicating reception status, which is transmitted to the WAP GW by the receiver terminal after completing reception of multimedia message.
- An embodiment of the present invention is described as follows.
- The multimedia message is a message that includes text, picture, video and audio contents, which is an enhancement of a short message service. If a user wants to use the MMS, he/she needs to configure an IP address and a port of the WAP GW and the APN on the cell phone terminal, and meanwhile configuring the address of the service gateway correctly is needed. After all the three parameters are configured correctly, the multimedia message can be transmitted correctly. A typical service gateway is for example the MMSC. If an operator deploys a plurality of MMSCs, the MMSCs are interconnected. When a user transmits an MMS message, a home MMSC is typically used for providing service. In this time, the WAP GW is needed to forward the service request to the home MMSC of the user. In order to realize the forwarding by the WAP GW, it needs to inquire an electronic numbers to uniform resource identifier (URI) mapping (ENUM) server to acquire the home MMSC of the user according to the address of the MMSC reported by a terminal of the user. For convenience of description, the electronic number to uniform resource identifier mapping server is referred to as an ENUM server. An example procedure may be described as follows: a user may be roamed from home province B to province A and transmits a service request for accessing an MMS from a visited (namely roamed)WAP GW ; the visited WAP GW may receive the service request for accessing an MMS transmitted by the user, and inquire the ENUM server to acquire the uniform resource locator (URL) address of the home MMSC of the user (hereinafter referred to as a URL address); the visited WAP GW may transmit directly the service request for accessing an MMS to the home MMSC of the user; and, the home MMSC of the user may return an MMS message transmission response.
- As shown in the system architecture of
Fig. 1 and the signaling flow chart based onFig. 1 ofFig. 2 , the embodiment is further described in detail below. - S1: A terminal 100 may transmit an M-Send.req request message to a
WAP GW 500 by taking a WAP as a carrying protocol. The terminal 100 is referred to as a sender terminal that is configured with the address of an MMSC. - S2: The
WAP GW 500 may receive the request message from the terminal 100 and resolves the URL address included in the service request. If the address is http://mmsc.monternet.com, it is regarded that the service request is a multimedia messaging service request, and the user identification of the sender is obtained from the service request and an inquiry that the address of the home MMSC of the sender is retrieved from theENUM server 300 is initiated. - S3: The
ENUM server 300 may return to theWAP GW 500 an inquiry result including the address of the home MMSC of the sender. - S4: According to the response message, the
WAP GW 500 may forward the M-Send.Req request message to thehome MMSC 400 of the sender, to request to transmit the multimedia message. - S5: The
home MMSC 400 of the sender may respond to the request message of theWAP GW 500 and incorporate an M-Send.conf in the response to indicate that the request has been accepted. - S6: The
WAP GW 500 may forward the M-Send.conf to the terminal 100. - In the above-mentioned embodiment, in order to transmit the multimedia message, it is needed to configure correctly the address "http://mmsc.monternet.com" of the MMSC in the terminal (referring to the step S2 in the above-mentioned embodiment). If the address is configured wrongly as for example "http://mms.monternet.com", the WAP GW will identify wrongly and fail to process the request as the MMS, hence leading failure of transmission of the multimedia message. This may bring poor experience for users and is adverse for the operator to actively promote services.
- The processing procedure for a person information management (PIM) service is the same with the above embodiment of transmitting multimedia messages. The PIM service may be mainly for synchronization of data such as a telephone directory, a scheduling table and an album between a cell phone terminal and the PIM server. For example, with synchronization operation on the telephone directory, a user may synchronize phone numbers on the terminal of the user to the PIM server.
- The processing procedure for the PIM service is similar to that of the MMS service. The WAP GW may receive the request message from the terminal and resolve the URL address included in the service request. If it is determined that the service to be executed is the PIM service, the ENUM server is inquired to acquire the address of the home PIM server of the user and the service request is forwarded to the home PIM server of the user by the WAP GW. However, if the terminal is configured with a wrong URL address, the WAP GW will identify wrongly and fail to process the service request as the PIM service. Thus the purpose of the service request can not be realized, which brings poor experience to users and is adverse for the carrier to actively promote services.
- An embodiment of the present invention provides a technical solution in which the WAP GW may respond normally to a service request, identify a service correctly and implement service process according to the service request even when the terminal is configured with the wrong address of the service gateway. For example, a service content type included in the service request may be also incorporated as one of identifying features for the WAP GW, so that the WAP GW may identify the service request not only according to the URL address of the service request but also according to the type of service contents included in the service request such as content information included in the Content-Type field of the service request.
- As shown in
Fig. 3 , an embodiment of the present invention provides a method for identifying services, and the method may include the following steps. - S11: A service request including a URL address is received;
- S22: Whether the URL address matches a service flow is determined.
- S33: A service type of the service request is identified according to a service content type included in the service request, when the determination result indicates that the URL address matches no service flow.
- For example, a visited application protocol gateway (typically a WAP GW) may receive the service request of a roaming user and determine whether the URL address included in the service request is the URL address of an MMSC. If the URL address included in the service request is the URL address of the MMSC, the process proceeds to the process procedure of prior art. If the URL address included in the service request is not the URL address of the MMSC, the service type of the service request is identified according to the service content type included in the service request.
- S44: A request for inquiring the address of the service server corresponding to the identified service type is transmitted after the service type of the service request is identified. For example, when the identified service type is the service request for the multimedia message, a request for inquiring the address of the home MMSC of the sender of the service request is transmitted.
- The above-mentioned step that whether the URL address matches a service flow is determined may further include the following steps: whether the URL address is the URL address of the MMSC or the address of the home PIM server of the user is determined; If the URL address is the URL address of the MMSC, the process proceeds to the MMS service procedure; and If the URL address is the address of the home PIM server of the user, the process proceeds to the PIM service procedure.
- In the above-mentioned embodiment, the type of service content included in the service request may be information included in a field of the service request and the field may be for example the Content-Type field.
- Referring to
Fig. 4 , the present embodiment may be described further as follows. - S201: The service request from the roaming user is received by the visited WAP GW .
- S202: The URL address included in the service request is resolved.
- S203: Whether the URL address is the URL address of the MMSC such as "http://mmsc.monternet.com" is determined.
- S204: Whether the service request is the MMS is identified continually according to the service content type included in the service request. The included service content type is for example the content in the Content-Type field. If the content is the service content type of the MMS, for example, the content is "Application/vnd.wap. mms-message", it is determined that the service request is an MMS request.
- In addition, a determination feature may be further added, and the following is an example.
- S205: It is needed that the MMS service request is a request for transmitting MMS service and the content information type of the Content-Type field is the MMS. For example, if a content of a method field in the service request is "m-send-req", it is determined that the service request is the MMS service request.
- A determination step may also be added in an embodiment of the present invention. For example, the request for inquiring the address of the home MMSC of the user is transmitted to the ENUM server when the service route table is matched successfully according to multipurpose internet mail extensions (MIME).An MIME message may include text, image, voice, video and data specific to other application programs.
- S206: The request for inquiring the address of the home MMSC of the user is transmitted to the ENUM server if the WAP GW determines that the service request satisfying the above-mentioned conditions is the MMS service request.
- With the technical solution described in the above-mentioned embodiments, it is realized that the WAP GW can determine and identify correctly the service type by the service content type and carry out subsequent steps for implementing the MMS even when the address of the service gateway is configured wrongly in the terminal. Thus the user's service request is correctly realized, the user's experience is satisfied well, which is equivalent to enhancing the fault tolerant processing capacity of the WAP GW and is advantageous for the operator's service promotion.
- Similarly, in the data services, particularly in the message services, the Content-type field in the service request may be extended to facilitate the WAP GW to correctly identify the service type corresponding to the service request. Again, the PIM service is taken as an example below.
- The visited WAP GW may resolve the URL address included in the service request after receiving the service request from the roaming user.
- Whether the URL address is the URL address of the PIM service is determined. If it is determined that the URL address is not the URL address of the PIM service, whether the service request is the PIM service is identified according to the service content type included in the service request. The included service content type may be for example the content in the included Content-Type field. If the content is the content type of the PIM service, it is determined that the service request is the PIM service request. Subsequent processing steps are carried out according to the prior art PIM service procedure.
- An embodiment of the present invention may also provide a application protocol gateway such as a WAP GW. Referring to
Fig. 5 , theWAP GW 500 includes a receivingunit 501, a determiningunit 502, and a resolvingunit 503. - The receiving
unit 501 is configured to receive a service request including a URL address. - The determining
unit 502 is configured to determine whether the URL address matches a service flow. - The resolving
unit 503 is configured to resolve the service content type included in the service request to identify the service type of the service request when the determination result of the determiningunit 502 indicates that the URL address matches no service flow. - The determining
unit 502 may determine whether the URL address matches a service flow. Further, the determiningunit 502 may determine whether the URL address included in the service request is the URL address of the MMSC or the address of the home PIM server of the user. - The resolution result of the resolving
unit 503 may include the service content type to which the service request belongs, for example the MMS service or the PIM service. - The
WAP GW 500 may further include a transmittingunit 504 configured to transmit a request for inquiring the address of the service server corresponding to the identified service type. For example, when the resolution result is the MMS service, the transmittingunit 504 may transmit to the ENUM server 300 a request for inquiring the address of the home MMSC of the user. - The
WAP GW 500 in the procedure of processing the service request may be described as follows. - The
WAP GW 500 may typically be the visited WAP GW . After thereceiving unit 501 receives from a roaming user a service request including generally a URL address, the resolvingunit 503 may resolve the service content type included in the service request. Before the resolving of the resolvingunit 503, the determiningunit 502 may determine whether the URL address included in the service request is the URL address of the MMSC such as "http://mmsc.monternet.com". If it is determined that the URL address included in the service request is not the URL address of the MMSC, the resolving unit may resolve the service content type included in the service request, and the service type of the service request is identified according to the resolution result (namely the service content type). If it is identified that the service type of the service request is the MMS service, it may also be further determined that the service request is a request for transmitting the MMS service. After that, a request for inquiring the address of the home MMSC of the user is transmitted to theENUM server 300. Subsequent steps proceed to the prior art procedure and are not described further here. - With the technical solution described in the above-mentioned embodiments, the fault toleration capability of the WAP GW may be enhanced. The addition of determination feature may increase probability of identifying the service type correctly and better ensure normal operation of the service. And it is easier to implement with lower cost.
- An embodiment of the present invention may also provide a service processing system including a terminal, an application protocol gateway and an application server.
- The terminal is configured to transmit a service request including a field identifying the service content type of the service request.
- The application protocol gateway may be for example the
WAP GW 500 shown inFig. 5 and is configured to resolve the service request transmitted by the terminal, identify the service type of the service request according to the field of the service content type and process service procedure according to the identified service type. - The application server may be for example the
ENUM server 300 shown inFig. 5 and is configured to receive the inquiry request from the application protocol gateway and inquire the address of the service server corresponding to the identified service type. The inquiring the address of the service server corresponding to the identified service type is further described as follows: Referring toFig. 5 , for example, when the service type identified by theWAP GW 500 is the MMS service, theENUM server 300 may receive from theWAP GW 500 the request for inquiring the address of the home MMSC of the user and return to theWAP GW 500 an inquiry result including the address of the home MMSC of the user. Here, the server corresponding to the MMS service is the home MMSC of the user. For example again, when the service type identified by theWAP GW 500 is the PIM service, theENUM server 300 is inquired to acquire the address of the home PIM server of the user, and theWAP GW 500 may forward the service request to the home PIM server of the user. Here, the service server corresponding to PIM service is the PIM server. - Referring to
Fig. 5 , theWAP GW 500 may further include a receivingunit 501, a determiningunit 502 and a resolvingunit 503. - The receiving
unit 501 is configured to receive a service request including a URL address. - The determining
unit 502 is configured to determine whether the URL address matches a service flow. - The resolving
unit 503 is configured to resolve the service content type included in the service request and identify the service type of the service request when the determination result of the determiningunit 502 indicates that the URL address matches no service flow. - The determining
unit 502 may determine whether the URL address matches a service flow. Further, the determiningunit 502 may determine whether the URL address included in the service request is the URL address of the MMSC or the address of the home PIM server of the user. - The resolution result of the resolving
unit 503 may include the service content type to which the service request belongs, for example the MMS service or the PIM service. - The
WAP GW 500 may further include a transmittingunit 504 configured to transmit a request for inquiring the address of the service server corresponding to the identified service type. For example, when the resolution result is the MMS service, the transmittingunit 504 may transmit to the ENUM server 300 a request for inquiring the address of the home MMSC of the user. - With the technical solution described in the above-mentioned embodiments, service content type is identified correctly, which may enhance the fault toleration capability of application protocol gateway, improve the system's capability of processing service and realize user's service request. And they are easier to implement with lower cost and with little change for networking structure of the overall system.
- The above description is only preferred embodiments of the present invention and is not for limiting the scope of the invention. The specification as a whole supports the protection scope of the present invention.
Claims (10)
- A method for processing a service request, comprising:receiving, (S11, S201) by a WAP gateway, a service request from a terminal including a URL address and a service content type of the service request, wherein the URL address is configured on the terminal; andwhen the URL address is correctly configured on the terminal, (S22, S202-203) identifying, by the WAP gateway, a service type of the service request according to the URL address;when the URL address is wrongly configured on the terminal, (S33, S204) identifying, by the WAP gateway, a service type of the service request according to the service content type included in the service request;executing (S44, S205-S206) a corresponding service process according to the identified service type of the service request.
- The method for identifying a service of claim 1, wherein the receiving the service request further comprises:receiving, (S201) by the visited wireless application protocol gateway, the service request from the terminal of a roaming user.
- The method for identifying a service of claim 1, wherein the executing a corresponding service process according to the identified service type of the service request comprises:transmitting (S44) a request for inquiring an address of a service server corresponding to the identified service type.
- The method for identifying a service of claim 1, wherein the executing a corresponding service process according to the identified service type of the service request comprises:when the identified service type of the service request is a multimedia messaging service, the process proceeds to the MMS service procedure; or,when the identified service type of the service request is a personal information management service, the process proceeds to the PIM service procedure.
- The method for identifying a service of one of claims 1 to 4, wherein the service request including a service content type of the service request is:the service request including a service type field, information carried in the service type field is the service content type of the service request.
- An application protocol gateway, comprising:a receiving unit, (501) configured to receive a service request from a terminal including a URL address and a service content type of the service request, wherein the URL address is configured on the terminal;a determining unit (502) configured to determine whether the URL address is correctly configured on the terminal;a resolving unit, (503) configured to when the URL address is correctly configured on the terminal , to identify a service type of the service request according to the URL address; when the URL address is wrongly configured on the terminal, to identify a service type of the service request according to the service content type included in the service request;an executing unit, configured to execute a corresponding service process according to the identified service type of the service request.
- The application protocol gateway of claim 6, wherein the executing unit is:a transmitting unit (504), configured to transmit a request for inquiring an address of a service server corresponding to the identified service type.
- The application protocol gateway of claim 6 or 7, wherein the service request including a service content type of the service request is:the service request including a service type field, information carried in the service type field is the service content type of the service request.
- The application protocol gateway of claim 6 or 7, wherein the identified service type of the service request is: a multimedia messaging service or a personal information management service.
- A service processing system, comprising:an application protocol gateway according to any of the claims 6 to 9, and the terminal configured to send the service request including a URL address and a service content type of the service request, wherein the URL address is configured on the terminal.
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
CN2007100765183A CN101370159B (en) | 2007-08-17 | 2007-08-17 | Method, device and system for recognizing service |
EP08783973A EP2136512B1 (en) | 2007-08-17 | 2008-08-14 | A method, device and system for identifying service |
Related Parent Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
EP08783973.4 Division | 2008-08-14 |
Publications (3)
Publication Number | Publication Date |
---|---|
EP2456144A2 EP2456144A2 (en) | 2012-05-23 |
EP2456144A3 EP2456144A3 (en) | 2012-06-20 |
EP2456144B1 true EP2456144B1 (en) | 2013-10-30 |
Family
ID=40377851
Family Applications (2)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
EP08783973A Active EP2136512B1 (en) | 2007-08-17 | 2008-08-14 | A method, device and system for identifying service |
EP12155573.4A Active EP2456144B1 (en) | 2007-08-17 | 2008-08-14 | Method, device and system for identifying a service |
Family Applications Before (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
EP08783973A Active EP2136512B1 (en) | 2007-08-17 | 2008-08-14 | A method, device and system for identifying service |
Country Status (7)
Country | Link |
---|---|
US (1) | US20100048189A1 (en) |
EP (2) | EP2136512B1 (en) |
CN (1) | CN101370159B (en) |
BR (1) | BRPI0812140B1 (en) |
ES (2) | ES2442840T3 (en) |
RU (2) | RU2438171C2 (en) |
WO (1) | WO2009024063A1 (en) |
Families Citing this family (8)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN101841764B (en) * | 2009-03-16 | 2013-03-20 | 华为软件技术有限公司 | Method and device for sending and acquiring position information of mobile terminal |
CN103139319B (en) * | 2011-11-29 | 2016-10-26 | 华为终端有限公司 | Obtain the method for resource address, terminal and server |
CN102739523B (en) * | 2012-06-05 | 2016-04-27 | 深圳市共进电子股份有限公司 | A kind of method of nuclear location CPE traffic flow types in linux |
CN103763343A (en) * | 2013-12-27 | 2014-04-30 | 乐视网信息技术(北京)股份有限公司 | Method and device for processing service access |
CN105574749A (en) * | 2015-03-24 | 2016-05-11 | 西安酷派软件科技有限公司 | Selection method, device and system for card applications in secure element SE |
CN110875961A (en) * | 2018-08-31 | 2020-03-10 | 阿里巴巴集团控股有限公司 | Data service processing method, device and system |
UA145907U (en) * | 2020-08-13 | 2021-01-06 | Олексій Олегович Пташний | METHOD OF IDENTIFYING THE SERVICE IN THE ENUM STRUCTURE |
JP7113129B1 (en) * | 2021-11-12 | 2022-08-04 | Kddi株式会社 | Message relay device, system and program |
Family Cites Families (30)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
SE9401319L (en) * | 1994-04-19 | 1995-10-20 | Ellemtel Utvecklings Ab | telecommunication systems |
US6742022B1 (en) * | 1995-12-11 | 2004-05-25 | Openwave Systems Inc. | Centralized service management system for two-way interactive communication devices in data networks |
US7062561B1 (en) * | 2000-05-23 | 2006-06-13 | Richard Reisman | Method and apparatus for utilizing the social usage learned from multi-user feedback to improve resource identity signifier mapping |
US8326352B1 (en) * | 2000-09-06 | 2012-12-04 | Kevin Reid Imes | Device, network, server, and methods for providing service requests for wireless communication devices |
WO2002029584A1 (en) * | 2000-10-04 | 2002-04-11 | Enic Corporation | Providing services and information based on a request that includes a unique identifier |
WO2003036857A1 (en) * | 2001-10-24 | 2003-05-01 | Nokia Corporation | Ciphering as a part of the multicast cencept |
JP2003296213A (en) * | 2002-04-03 | 2003-10-17 | Sony Corp | Method and system for information transmission and reception |
US20040019697A1 (en) * | 2002-07-03 | 2004-01-29 | Chris Rose | Method and system for correcting the spelling of incorrectly spelled uniform resource locators using closest alphabetical match technique |
EP1418743A1 (en) * | 2002-11-07 | 2004-05-12 | CMG IPR Telecommunications B.V. | System for billing rating and selection of accounts |
FI20031097A0 (en) * | 2003-07-22 | 2003-07-22 | Uniqminds Ltd | Procedure and router for routing of multimedia communications |
EP1517469A1 (en) * | 2003-09-18 | 2005-03-23 | Comptel Corporation | Method, system and computer program product for online charging in a communications network |
US7296072B2 (en) * | 2003-12-12 | 2007-11-13 | International Business Machines Corporation | Enhanced port type agnostic proxy support for web services intermediaries |
US7464142B2 (en) * | 2003-12-12 | 2008-12-09 | International Business Machines Corporation | Port type agnostic proxy support for web services intermediates |
EP1592217B1 (en) * | 2004-04-29 | 2013-10-16 | Hewlett-Packard Development Company, L.P. | Method and apparatus for providing a specialized resource function in a telephone network |
CN1277392C (en) * | 2004-05-21 | 2006-09-27 | 华为技术有限公司 | Processing method for implementing multimedia message service single-node access |
CN100396112C (en) * | 2004-09-29 | 2008-06-18 | 华为技术有限公司 | Method for realizing mobile data service unification route in communication system |
CN100370746C (en) * | 2004-10-10 | 2008-02-20 | 华为技术有限公司 | Scheduling method of mobile data service |
EP1677462A1 (en) * | 2004-12-28 | 2006-07-05 | Eidgenössische Technische Hochschule Zürich | Service discovery in ad hoc networks |
US20060149845A1 (en) * | 2004-12-30 | 2006-07-06 | Xinnia Technology, Llc | Managed quality of service for users and applications over shared networks |
KR100652958B1 (en) * | 2005-02-28 | 2006-12-01 | 삼성전자주식회사 | Method of transmitting data by improvement of translating network address in gateway and system thereof |
RU2387103C2 (en) * | 2005-06-03 | 2010-04-20 | Нокиа Корпорейшн | Method and system for establishing connection between network elements |
US8849800B2 (en) * | 2005-09-19 | 2014-09-30 | Tektronix, Inc. | System and method of forwarding end user correlated user and control plane or network states to OSS system |
EP1764972B1 (en) * | 2005-09-20 | 2017-07-19 | Accenture Global Services Limited | Authentication and authorization architecture for an access gateway |
ATE434333T1 (en) * | 2005-10-28 | 2009-07-15 | Accenture Global Services Gmbh | SERVICE BROKER INTEGRATION LAYER TO SUPPORT TELECOMMUNICATIONS CLIENTS SERVICE REQUIREMENTS |
US8694616B2 (en) * | 2005-10-28 | 2014-04-08 | Accenture Global Services Limited | Service broker integration layer for supporting telecommunication client service requests |
CN1866947A (en) * | 2005-11-02 | 2006-11-22 | 华为技术有限公司 | Realization method and system for recognizing special service in service building process |
US20070130151A1 (en) * | 2005-12-01 | 2007-06-07 | Microsoft Corporation | Using errors to perform a search |
CN100542123C (en) * | 2006-03-29 | 2009-09-16 | 华为技术有限公司 | IP territory network and method for routing thereof that a kind of wireless traffic is used |
US8107952B2 (en) * | 2007-05-24 | 2012-01-31 | International Business Machines Corporation | Mobile device with an obfuscated mobile device user identity |
US8627345B2 (en) * | 2007-06-13 | 2014-01-07 | International Business Machines Corporation | Apparatus, system, and method for soap access to data source procedures |
-
2007
- 2007-08-17 CN CN2007100765183A patent/CN101370159B/en not_active Expired - Fee Related
-
2008
- 2008-08-14 EP EP08783973A patent/EP2136512B1/en active Active
- 2008-08-14 ES ES12155573.4T patent/ES2442840T3/en active Active
- 2008-08-14 RU RU2009145110/08A patent/RU2438171C2/en active
- 2008-08-14 WO PCT/CN2008/071982 patent/WO2009024063A1/en active Application Filing
- 2008-08-14 BR BRPI0812140-0A patent/BRPI0812140B1/en not_active IP Right Cessation
- 2008-08-14 RU RU2011134200/08A patent/RU2483352C2/en active
- 2008-08-14 EP EP12155573.4A patent/EP2456144B1/en active Active
- 2008-08-14 ES ES08783973T patent/ES2388201T3/en active Active
-
2009
- 2009-10-26 US US12/605,468 patent/US20100048189A1/en not_active Abandoned
Also Published As
Publication number | Publication date |
---|---|
US20100048189A1 (en) | 2010-02-25 |
CN101370159B (en) | 2013-01-30 |
EP2136512B1 (en) | 2012-06-20 |
EP2136512A4 (en) | 2010-09-08 |
EP2456144A3 (en) | 2012-06-20 |
RU2009145110A (en) | 2011-09-27 |
ES2388201T3 (en) | 2012-10-10 |
RU2438171C2 (en) | 2011-12-27 |
BRPI0812140A2 (en) | 2014-11-18 |
EP2136512A1 (en) | 2009-12-23 |
EP2456144A2 (en) | 2012-05-23 |
CN101370159A (en) | 2009-02-18 |
ES2442840T3 (en) | 2014-02-13 |
BRPI0812140B1 (en) | 2020-09-15 |
RU2483352C2 (en) | 2013-05-27 |
WO2009024063A1 (en) | 2009-02-26 |
RU2011134200A (en) | 2013-03-10 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
EP2456144B1 (en) | Method, device and system for identifying a service | |
US8799373B2 (en) | Method, system and apparatus for message interworking | |
US7546117B2 (en) | Method and apparatus for blocking ID information associated with a sender of a short messaging service (SMS) message | |
EP2353274B1 (en) | Mobile station and application server for providing a service to the mobile station and operation methods for the same | |
US20030236769A1 (en) | Method and device for mobile communication | |
WO2008019558A1 (en) | Message conversion device, system and conversion method | |
WO2008040248A1 (en) | A method and system for transmitting email and a push mail server | |
KR20090087790A (en) | Interworking method in converged ip messaging service | |
EP2184932A1 (en) | method, device and system for interworking between instant message and short message | |
JP2007325190A (en) | Push gateway, in-service registration server, portable terminal, push system and push method | |
WO2007000091A1 (en) | A method for limiting the forwarding times of the multimedia message for the multimedia messaging service center mmsc and a system thereof | |
WO2009000212A1 (en) | A message processing apparatus and terminal, a system and method for transmiting messages | |
US20120178428A1 (en) | Method, device and system for identifying a service | |
EP1665720B1 (en) | Implementing a web server on a mobile station | |
WO2008052476A1 (en) | Method for managing conversation, universal message client and server | |
EP1493256A1 (en) | Message header for messaging service | |
US9900353B2 (en) | Method and apparatus for enabling communications between users | |
US8014757B1 (en) | System and method for anonymous exchange of multimedia content utilizing a wireless network | |
CN101483834B (en) | Method and system for multimedia message communication using short number | |
CN102572696A (en) | Method for processing service request, apparatus and system thereof | |
KR101504172B1 (en) | Method for treating a call of number portability using telephone number mapping and system thereof | |
US20100062797A1 (en) | Method for group communication between subscribers to different messaging services, communication terminal and computer program product | |
CN1937814A (en) | Mobile communication terminal and sever having user information processing function and its using method | |
KR20050046880A (en) | Method for providing multimedia messaging service in wcdma | |
JP2007013614A (en) | Communication control apparatus and communication control method |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
PUAL | Search report despatched |
Free format text: ORIGINAL CODE: 0009013 |
|
PUAI | Public reference made under article 153(3) epc to a published international application that has entered the european phase |
Free format text: ORIGINAL CODE: 0009012 |
|
17P | Request for examination filed |
Effective date: 20120215 |
|
AC | Divisional application: reference to earlier application |
Ref document number: 2136512 Country of ref document: EP Kind code of ref document: P |
|
AK | Designated contracting states |
Kind code of ref document: A2 Designated state(s): AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HR HU IE IS IT LI LT LU LV MC MT NL NO PL PT RO SE SI SK TR |
|
AK | Designated contracting states |
Kind code of ref document: A3 Designated state(s): AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HR HU IE IS IT LI LT LU LV MC MT NL NO PL PT RO SE SI SK TR |
|
RIC1 | Information provided on ipc code assigned before grant |
Ipc: H04L 12/56 20060101AFI20120514BHEP |
|
GRAP | Despatch of communication of intention to grant a patent |
Free format text: ORIGINAL CODE: EPIDOSNIGR1 |
|
REG | Reference to a national code |
Ref country code: DE Ref legal event code: R079 Ref document number: 602008028478 Country of ref document: DE Free format text: PREVIOUS MAIN CLASS: H04L0012560000 Ipc: H04L0012701000 |
|
GRAP | Despatch of communication of intention to grant a patent |
Free format text: ORIGINAL CODE: EPIDOSNIGR1 |
|
GRAS | Grant fee paid |
Free format text: ORIGINAL CODE: EPIDOSNIGR3 |
|
GRAA | (expected) grant |
Free format text: ORIGINAL CODE: 0009210 |
|
INTG | Intention to grant announced |
Effective date: 20130906 |
|
RIC1 | Information provided on ipc code assigned before grant |
Ipc: H04L 12/701 20130101AFI20130828BHEP |
|
RIN1 | Information on inventor provided before grant (corrected) |
Inventor name: LI, RONGGAO |
|
AC | Divisional application: reference to earlier application |
Ref document number: 2136512 Country of ref document: EP Kind code of ref document: P |
|
AK | Designated contracting states |
Kind code of ref document: B1 Designated state(s): AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HR HU IE IS IT LI LT LU LV MC MT NL NO PL PT RO SE SI SK TR |
|
REG | Reference to a national code |
Ref country code: GB Ref legal event code: FG4D |
|
REG | Reference to a national code |
Ref country code: CH Ref legal event code: EP |
|
REG | Reference to a national code |
Ref country code: AT Ref legal event code: REF Ref document number: 638751 Country of ref document: AT Kind code of ref document: T Effective date: 20131115 |
|
REG | Reference to a national code |
Ref country code: IE Ref legal event code: FG4D |
|
REG | Reference to a national code |
Ref country code: DE Ref legal event code: R096 Ref document number: 602008028478 Country of ref document: DE Effective date: 20131219 |
|
REG | Reference to a national code |
Ref country code: ES Ref legal event code: FG2A Ref document number: 2442840 Country of ref document: ES Kind code of ref document: T3 Effective date: 20140213 |
|
REG | Reference to a national code |
Ref country code: NL Ref legal event code: VDEP Effective date: 20131030 |
|
REG | Reference to a national code |
Ref country code: AT Ref legal event code: MK05 Ref document number: 638751 Country of ref document: AT Kind code of ref document: T Effective date: 20131030 |
|
REG | Reference to a national code |
Ref country code: LT Ref legal event code: MG4D |
|
PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
Ref country code: BE Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20131030 Ref country code: HR Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20131030 Ref country code: LT Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20131030 Ref country code: SE Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20131030 Ref country code: FI Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20131030 Ref country code: NO Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20140130 Ref country code: IS Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20140228 Ref country code: NL Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20131030 |
|
PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
Ref country code: LV Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20131030 Ref country code: CY Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20131030 Ref country code: AT Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20131030 |
|
PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
Ref country code: PT Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20140228 |
|
PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
Ref country code: EE Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20131030 |
|
REG | Reference to a national code |
Ref country code: DE Ref legal event code: R097 Ref document number: 602008028478 Country of ref document: DE |
|
PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
Ref country code: RO Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20131030 Ref country code: SK Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20131030 Ref country code: CZ Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20131030 Ref country code: IT Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20131030 Ref country code: PL Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20131030 |
|
PLBE | No opposition filed within time limit |
Free format text: ORIGINAL CODE: 0009261 |
|
STAA | Information on the status of an ep patent application or granted ep patent |
Free format text: STATUS: NO OPPOSITION FILED WITHIN TIME LIMIT |
|
PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
Ref country code: DK Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20131030 |
|
26N | No opposition filed |
Effective date: 20140731 |
|
REG | Reference to a national code |
Ref country code: DE Ref legal event code: R097 Ref document number: 602008028478 Country of ref document: DE Effective date: 20140731 |
|
PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
Ref country code: SI Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20131030 |
|
PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
Ref country code: MC Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20131030 Ref country code: LU Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20140814 |
|
REG | Reference to a national code |
Ref country code: CH Ref legal event code: PL |
|
PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
Ref country code: LI Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES Effective date: 20140831 Ref country code: CH Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES Effective date: 20140831 |
|
REG | Reference to a national code |
Ref country code: IE Ref legal event code: MM4A |
|
PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
Ref country code: IE Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES Effective date: 20140814 |
|
PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
Ref country code: BG Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20131030 |
|
PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
Ref country code: MT Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20131030 Ref country code: GR Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20140131 |
|
REG | Reference to a national code |
Ref country code: FR Ref legal event code: PLFP Year of fee payment: 9 |
|
PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
Ref country code: HU Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT; INVALID AB INITIO Effective date: 20080814 Ref country code: TR Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20131030 |
|
REG | Reference to a national code |
Ref country code: FR Ref legal event code: PLFP Year of fee payment: 10 |
|
REG | Reference to a national code |
Ref country code: FR Ref legal event code: PLFP Year of fee payment: 11 |
|
REG | Reference to a national code |
Ref country code: DE Ref legal event code: R079 Ref document number: 602008028478 Country of ref document: DE Free format text: PREVIOUS MAIN CLASS: H04L0012701000 Ipc: H04L0045000000 |
|
PGFP | Annual fee paid to national office [announced via postgrant information from national office to epo] |
Ref country code: GB Payment date: 20220630 Year of fee payment: 15 |
|
PGFP | Annual fee paid to national office [announced via postgrant information from national office to epo] |
Ref country code: ES Payment date: 20220902 Year of fee payment: 15 Ref country code: DE Payment date: 20220608 Year of fee payment: 15 |
|
PGFP | Annual fee paid to national office [announced via postgrant information from national office to epo] |
Ref country code: FR Payment date: 20220709 Year of fee payment: 15 |
|
P01 | Opt-out of the competence of the unified patent court (upc) registered |
Effective date: 20230524 |
|
REG | Reference to a national code |
Ref country code: DE Ref legal event code: R119 Ref document number: 602008028478 Country of ref document: DE |
|
GBPC | Gb: european patent ceased through non-payment of renewal fee |
Effective date: 20230814 |
|
PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
Ref country code: GB Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES Effective date: 20230814 |
|
PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
Ref country code: GB Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES Effective date: 20230814 Ref country code: FR Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES Effective date: 20230831 Ref country code: DE Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES Effective date: 20240301 |