EP2624518B1 - Method and device for processing multimode controller incoming messages and multimode controller - Google Patents
Method and device for processing multimode controller incoming messages and multimode controller Download PDFInfo
- Publication number
- EP2624518B1 EP2624518B1 EP11841339.2A EP11841339A EP2624518B1 EP 2624518 B1 EP2624518 B1 EP 2624518B1 EP 11841339 A EP11841339 A EP 11841339A EP 2624518 B1 EP2624518 B1 EP 2624518B1
- Authority
- EP
- European Patent Office
- Prior art keywords
- standard
- message
- protocol
- primitive
- incoming message
- 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 55
- 230000011664 signaling Effects 0.000 claims description 88
- 238000010586 diagram Methods 0.000 description 7
- 238000004891 communication Methods 0.000 description 6
- 230000005540 biological transmission Effects 0.000 description 4
- 230000009977 dual effect Effects 0.000 description 3
- 238000010295 mobile communication Methods 0.000 description 2
- 238000005516 engineering process Methods 0.000 description 1
- 238000003032 molecular docking Methods 0.000 description 1
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W88/00—Devices specially adapted for wireless communication networks, e.g. terminals, base stations or access point devices
- H04W88/02—Terminal devices
- H04W88/06—Terminal devices adapted for operation in multiple networks or having at least two operational modes, e.g. multi-mode terminals
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04Q—SELECTING
- H04Q3/00—Selecting arrangements
- H04Q3/0016—Arrangements providing connection between exchanges
- H04Q3/0025—Provisions for signalling
Definitions
- the disclosure proposes a method for processing an incoming message of a multimode controller, which includes: receiving, by a multimode controller, an incoming message from an abutting network element, and parsing the incoming message to construct an N-primitive message; obtaining a service standard type of the incoming message according to the N-primitive message; and processing the N-primitive message according to the service standard type.
- the standard attribute table may include: local end signalling points and thereof standard attribute fields, and/or opposite end signalling points and thereof standard attribute fields; or the standard attribute table may include: local end signalling point code, opposite end signalling point code, and corresponding network interface type fields; or the standard attribute table may include: local end signalling point code, opposite end signalling point code, corresponding network interface type fields, and standard attribute fields of local or opposite ends.
- the disclosure proposes a method and device for processing an incoming message of a multimode controller, and a multimode controller, and by adding a protocol enhancement module between a standard SCCP protocol module and standard RNSAP protocol modules to process the N-primitive message received by the multimode controller, obtains a service standard type of the incoming message and realizes to send an N-primitive message to a RNSAP protocol module with a corresponding standard on a wireless control plane to process.
- the disclosure mainly describes processing procedures above an SCCP protocol layer based on current lur-g and lur standard protocol interface protocol stacks, and does not change other transmission-related protocol processing processes under the SCCP protocol layer in a standard protocol stack.
- the standard attribute table includes: local end signalling points and thereof standard attribute fields, and/or opposite end signalling points and thereof standard attribute fields; or the standard attribute table includes: local end signalling point code, opposite end signalling point code, and corresponding network interface type fields; or the standard attribute table includes: local end signalling point code, opposite end signalling point code, corresponding network interface type fields, and standard attribute fields of local or opposite ends.
- the signalling points in the transport layer information correspond to local end network element signalling points and opposite end network element signalling points respectively.
- the standard attribute table includes local end signalling points and thereof standard attribute fields.
- a multimode controller is configured with two signalling points such as a signalling point 1 and a signalling point 2, wherein the signalling point 1 is of a 2G standard attribute and the signalling point 2 is of a 3G standard attribute.
- the DPC of a message which is received by the local end is the signalling point 2
- the standard attribute table can further include local end network element signalling point fields, opposite end network element signalling point fields, corresponding network interface type fields and other fields.
- RNSAP protocol modules of 2G and 3G standards that is, a GSM RNSAP protocol module and a WCDMA RNSAP protocol module
- the whole implementing flow of the embodiment is described in detail as follows.
- Example two taking a dual-mode controller being configured to a single 3G controller as an example, the dual-mode controller receives a UDT message from an abutting RNC, an SCCP protocol module parses the UDT message to construct an N-primitive message, and sends the N-primitive message to a protocol enhancement module in a wireless network control layer, and the protocol enhancement module pre-decodes an RNSAP message in the N-primitive message, wherein the RNSAP message is a paging message, in which an ID of a cell which is of a 3G standard is included, therefore the incoming message is a 3G standard service, and the protocol enhancement module sends the N-primitive message to the WCDMA RNSAP protocol module to continue to process.
- the RNSAP message is a paging message, in which an ID of a cell which is of a 3G standard is included, therefore the incoming message is a 3G standard service
- the protocol enhancement module sends the N-primitive message to the WCDMA
- the protocol enhancement module 602 includes: a parsing unit 6021 and a standard type obtaining unit 6022, wherein:
- the standard attribute table includes: local end signalling points and thereof standard attribute fields, and/or opposite end signalling points and thereof standard attribute fields; or the standard attribute table includes: Origination Point Code (OPC), Destination Point Code (DPC), and corresponding network interface type fields; or the standard attribute table includes: OPC, DPC, corresponding network interface type fields, and standard attribute fields of the OPC.
- OPC Origination Point Code
- DPC Destination Point Code
- OPC Origination Point Code
- DPC Destination Point Code
- standard attribute table includes: OPC, DPC, corresponding network interface type fields, and standard attribute fields of the OPC.
- the disclosure assists the SCCP protocol module and the RNSAP protocol modules in correctly and quickly establishing a corresponding relationship, saves software maintenance cost, makes up shortages of current SCCP and RNSAP protocols when supporting the multimode controller, and realizes to a function of processing signalling according to standards. Furthermore, when being only configured as a single mode or presenting in the manner of multimode, the multimode controller needs not to be modified functionally, and can accurately forward a signalling to a corresponding standard of wireless network control service layer to process.
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Mobile Radio Communication Systems (AREA)
Description
- The disclosure relates to the field of mobile communication technologies, particular to a method and device for processing an incoming message of a multimode controller which interacts with a Base Station Controller (BSC), a Radio Network Controller (RNC), other multimode controllers and the like, and a multimode controller.
- At present, more and more telecommunication equipment manufacturers release multimode controllers in which 2G and 3G are common mode, and the multimode controller enables 2G and 3G services to be integrated, so that an operator only needs to buy a set of equipment to be able to support both 2G services and 3G services, and when the equipment is used as a 2G single mode controller in an early stage and the 3G service needs to be provided in a later stage, to also be able to directly use as a multimode controller, so as to greatly decrease equipment cost of the operator; therefore, the multimode controllers are attracted more and more extensive attention.
- The multimode controller generally needs to support characteristics of all interfaces in 2G or 3G single mode, such as Abis interfaces, lub interfaces, lur-g interfaces, lur interfaces, A interfaces, luCS interfaces, luPS interfaces, Gb interfaces, and the like. For example, network interfaces of a multimode controller embody an lur-g attribute when interacting with a 2G BSC, and the network interfaces of the multimode controller embody an lur attribute when interacting with a 3G RNC.
- In the single mode, an lur interface protocol stack is shown in
Fig. 1 , an lur-g interface protocol stack is shown inFig. 2 , and wireless control planes of the lur and lur-g interfaces both use a Signalling Connection Control Part (SCCP) protocol to bear wireless signalling. The multimode controller can realize that 2G and 3G are common mode, in terms of realization probability and cost saving, a software platform and a hardware platform should be shared as soon as possible, so in an incoming signalling procedure, a multimode controller based on sharing an SCCP protocol module should be relatively reasonable implementation. - However, in the prior art, Sub-System Numbers (SSNs) of upper users corresponding to the SCCP all are Radio Network Subsystem Application Part (RNSAP) on the lur and lur-g interfaces, for an SCCP protocol module, it cannot distinguish under a multimode only by the SSN whether a message received by the SCCP protocol module is an lur service or an lur-g service, which results in that incoming messages cannot build a correct corresponding relationship with target service users in an initial stage, increases a time delay for processing messages, and thus reduces use reliability of the multimode controller.
-
US 2008/207230 A1 discloses a multi-mode communication system that the multi-mode communication system uses a first mode among a plurality communication modes for accessing a first mobility control entity (MCE) among a plurality ofMCEs, and communicates data with the first MCE. The multi -mode communication system receives a paging request that has been transmitted from a multi-mode control entity (MMCE) for accessing a second MCE from the first MCE and analyzes the paging request, and puts the first mode into a sleep mode and a second mode for accessing the second MCE into an awake mode based on the analysis. Subsequently, multi-mode UE accesses the second MCE by using the second mode in the awake mode. -
US 2010/3061336 A1 discloses a method for acquiring/updating information in the case of a handover between heterogeneous networks that includes: a) requesting first control information, associated with a new access point detected by a link scanning, from a network entity for providing information associated with a specific network; b) acquiring the requested first control information and second control information supplied from the new access point; and c) performing a connection to the new access point according to the first control information and the second control information. - In view of the problem above, the main purpose of the disclosure is to provide a method and device for processing an incoming message of a multimode controller, and a multimode controller, which are intended to realize a function of processing various standard services quickly and accurately by the multimode controller, and to enhance use reliability of the multimode controller.
- In order to achieve the purpose above, the disclosure proposes a method for processing an incoming message of a multimode controller, which includes: receiving, by a multimode controller, an incoming message from an abutting network element, and parsing the incoming message to construct an N-primitive message; obtaining a service standard type of the incoming message according to the N-primitive message; and processing the N-primitive message according to the service standard type.
- Preferably, the step of obtaining a service standard type of the incoming message according to the N-primitive message may include: pre-decoding a Radio Network Subsystem Application Part, RNSAP message in the N-primitive message; and obtaining the service standard type of the incoming message according to a pre-decoded result.
- Preferably, the step of obtaining a service standard type of the incoming message according to the N-primitive message may include: obtaining transport layer information by parsing the N-primitive message; and obtaining the service standard type of the incoming message according to the transport layer information and a standard attribute table.
- Preferably, the standard attribute table may include: local end signalling points and thereof standard attribute fields, and/or opposite end signalling points and thereof standard attribute fields; or the standard attribute table may include: local end signalling point code, opposite end signalling point code, and corresponding network interface type fields; or the standard attribute table may include: local end signalling point code, opposite end signalling point code, corresponding network interface type fields, and standard attribute fields of local or opposite ends.
- Preferably, the transport layer information may include Origination Point Code, OPC and/or Destination Point Code, DPC.
- The disclosure further proposes a device for processing an incoming message of a multimode controller, which includes: a Signalling Connection Control Part, SCCP protocol module configured to receive an incoming message from an abutting network element, and parse the incoming message to construct an N-primitive message; a protocol enhancement module configured to obtain a service standard type of the incoming message according to the N-primitive message, and send the N-primitive message to a corresponding standard of Radio Network Subsystem Application Part, RNSAP protocol module; and multiple standards of RNSAP protocol modules configured to process a corresponding standard of N-primitive message, wherein the device is inside a multimode controller.
- Preferably, the protocol enhancement module may include: a parsing unit configured to pre-decode an RNSAP message in the N-primitive message; a standard type obtaining unit configured to obtain the service standard type of the incoming message according to a pre-decoded result; and a forwarding unit configured to send the N-primitive message according to the service standard type of the incoming message to a RNSAP protocol module with a corresponding standard on a wireless control plane.
- Preferably, the parsing unit may be further configured to obtain transport layer information by parsing the N-primitive message; and the standard type obtaining unit may be further configured to obtain the service standard type of the incoming message according to the transport layer information and a standard attribute table.
- Preferably, the standard attribute table may include: local end signalling points and thereof standard attribute fields, and/or opposite end signalling points and thereof standard attribute fields; or the standard attribute table may include: local end signalling point code, opposite end signalling point code, and corresponding network interface type fields; or the standard attribute table may include: local end signalling point code, opposite end signalling point code, corresponding network interface type fields, and standard attribute fields of local or opposite ends.
- The disclosure further proposes a multimode controller including the device as described above.
- The disclosure proposes a method and device for processing an incoming message of a multimode controller, and a multimode controller, and by adding a protocol enhancement module between a standard SCCP protocol module and standard RNSAP protocol modules to process the N-primitive message received by the multimode controller, obtains a service standard type of the incoming message and realizes to send an N-primitive message to a RNSAP protocol module with a corresponding standard on a wireless control plane to process. Wherein, both the protocol enhancement module and the SCCP protocol module are multiplexed by the multimode controller, which not only saves software maintenance cost of the multimode controller, but also makes up shortages of current SCCP and RNSAP protocols when supporting the multimode controller, and assists the SCCP protocol module and various standards of RNSAP protocol modules in quickly establishing a corresponding relationship. Furthermore, when being only configured as a single mode or presenting in the manner of multimode, the multimode controller needs not to be modified functionally, and can accurately forward a signalling to a corresponding standard of wireless network control service layer to process.
-
-
Fig. 1 shows a basic structure diagram of an lur interface protocol stack; -
Fig. 2 shows a basic structure diagram of an lur-g interface protocol stack; -
Fig. 3 shows a flowchart of one embodiment of a method for processing an incoming message of a multimode controller according to the disclosure; -
Fig. 3a shows a service architecture diagram of obtaining a service standard type of an incoming message according to an N-primitive message in one embodiment of the method for processing an incoming message of a multimode controller according to the disclosure; -
Fig. 3b shows another service architecture diagram of obtaining a service standard type of an incoming message according to an N-primitive message in one embodiment of the method for processing an incoming message of a multimode controller according to the disclosure; -
Fig. 4 shows an implementation flowchart of obtaining a service standard type of an incoming message according to an N-primitive message in one embodiment of the method for processing an incoming message of a multimode controller according to the disclosure; -
Fig. 5 shows another implementation flowchart of obtaining a service standard type of an incoming message according to an N-primitive message in one embodiment of the method for processing an incoming message of a multimode controller according to the disclosure; -
Fig. 6 shows a structure diagram of one embodiment of a device for processing an incoming message of a multimode controller according to the disclosure; -
Fig. 7 shows a structure diagram of a protocol enhancement module in one embodiment of a device for processing an incoming message of a multimode controller according to the disclosure; and -
Fig. 8 shows a structure diagram of one embodiment of a multimode controller according to the disclosure. - The solution of embodiments of the disclosure is to add a protocol enhancement module between an SCCP protocol module and RNSAP protocol modules, to process an incoming message received by a multimode controller, to obtain a service standard type of the incoming message, and to send the incoming message to a RNSAP protocol module with a corresponding standard on a wireless control plane to process.
- The disclosure mainly describes processing procedures above an SCCP protocol layer based on current lur-g and lur standard protocol interface protocol stacks, and does not change other transmission-related protocol processing processes under the SCCP protocol layer in a standard protocol stack.
- In following embodiments, the solution of the disclosure is illustrated by dual mode of Wideband Code Division Multiple Access (WCDMA)/Global System for Mobile Communications (GSM), and dual mode or multimode of other standards, for example, a combination of any two or more standards of existing wireless communication standards, such as GSM, Code Division Multiple Access (CDMA), WCDMA, Time Division-Synchronous Code Division Multiple Access (TD-SCDMA) and the like, or other subsequent evolved wireless communication standards, such as TD-SCDMA/GSM dual mode, WCDMA/CDMA/GSM multimode or the like, wherein at least two standards need to utilize an SCCP protocol incoming processing process, may refer to description of the disclosure.
- As shown in
Fig. 3 , one embodiment of the disclosure proposes a method for processing an incoming message of a multimode controller, and the method includes: - Step S101: a multimode controller receives an incoming message from an abutting network element, and parses the incoming message to construct an N-primitive message.
At first, the multimode controller receives the incoming message from the abutting network element, and an SCCP protocol module of the multimode controller parses the incoming message to construct the N-primitive message, wherein the N-primitive message includes transport layer information such as SSN, OPC (Origination Point Code, that is, an abutting network element signalling point sending the message), DPC (Destination Point Code, that is, a local end signalling point) and other information associated with a transport layer, if the SSN is an RNSAP, then the SCCP protocol module sends the N-primitive message to a protocol enhancement module. - Step S102: a service standard type of the incoming message is obtained according to the N-primitive message.
- In the step, the service standard type of the incoming message is obtained by the protocol enhancement module according to the N-primitive message, wherein obtaining the service standard type of the incoming message according to the N-primitive message can be completed in a transport network layer (first implementation), and also can be completed in a wireless network layer (second implementation), that is, the protocol enhancement module can belong to a transmission network user plane of the transport network layer together with the SCCP protocol module, as shown in
Fig. 3a , and also can belong to a control plane of the wireless network layer together with RNSAP protocol modules, as shown inFig. 3b . For the first implementation, the protocol enhancement module and the SCCP protocol module belong to the transport network layer, and the protocol enhancement module can obtain the related transport layer information from the N-primitive message, wherein the transport layer information includes SSN, OPC, DPC and other information, a network element corresponding to a signalling point in the transport layer information is of a standard attribute, which can be obtained by a local end when docks with an abutting network element, for example, whether the abutting network element is a 2G BSC or a 3G RNC, so the corresponding standard type can be obtained according to the standard attribute of the network element corresponding to an origination signalling point and/or a destination signalling point in the transport layer information. - For the second implementation, after the SCCP protocol module receives the incoming message, if the SSN is the RNSAP, then the SCCP protocol module sends the N-primitive message to a wireless network control layer according to the standard N-primitive message between the SCCP and the RNSAP, and the protocol enhancement module in the wireless network control layer obtains an RNSAP message from the N-primitive message sent from the SCCP to the RNSAP, and pre-decodes the RNSAP message. Information such as a cell number, an information type, a target RNC ID and the like can be obtained by decoding the RNSAP message, for example, the cell number is unique, whether the RNSAP message being of the 2G standard or the 3G standard is certain, therefore that the target RNSAP message is which standard service can be determined according to the de-coded result. After obtaining the service standard type of the incoming message, the incoming message is sent by the protocol enhancement module to the RNSAP protocol module with a corresponding standard to process. Each standard service has its own protocol module, there are multiple RNSAP protocol modules according to different standard types, and each RNSAP protocol module with the corresponding standard processes an N-primitive message corresponding to the standard.
- Step S103: corresponding processing is performed on the N-primitive message according to the service standard type.
- Corresponding standards of the N-primitive messages are performed by different standards of RNSAP protocol modules.
- As shown in
Fig. 4 , corresponding to the above-mentioned first implementation of obtaining the service standard type, Step S102 includes: - Step S1021: transport layer information is obtained by parsing the N-primitive message.
The transport layer information includes: SSN and OPC and/or DPC. - Step S1022: the service standard type of the incoming message is obtained according to the transport layer information and a standard attribute table.
- The standard attribute table includes: local end signalling points and thereof standard attribute fields, and/or opposite end signalling points and thereof standard attribute fields; or the standard attribute table includes: local end signalling point code, opposite end signalling point code, and corresponding network interface type fields; or the standard attribute table includes: local end signalling point code, opposite end signalling point code, corresponding network interface type fields, and standard attribute fields of local or opposite ends.
- The signalling points in the transport layer information correspond to local end network element signalling points and opposite end network element signalling points respectively. The standard attribute table includes local end signalling points and thereof standard attribute fields. For example, a multimode controller is configured with two signalling points such as a signalling point 1 and a signalling point 2, wherein the signalling point 1 is of a 2G standard attribute and the signalling point 2 is of a 3G standard attribute. When the DPC of a message which is received by the local end is the signalling point 2, it can be obtained from inquiring the standard attribute table that the signalling received is a 3G service; and the standard attribute table can further include local end network element signalling point fields, opposite end network element signalling point fields, corresponding network interface type fields and other fields. For example, the lur interface is determined according to the OPC and DPC in the transport layer information, and the signalling received is determined as a 3G standard service directly; and the standard attribute table can further include local end network element signalling point fields, opposite end network element signalling point fields, corresponding network interface type fields, opposite end network element signalling point standard attribute fields and other fields, for example, by determining that the network interface is the lur-g interface as well as then based on that the standard type corresponding to the OPC (source signalling point sending the message) is of a 3G standard, it can be determined that the signalling received is a 2G standard service.
- As shown in
Fig. 5 , corresponding to the above-mentioned second implementation of obtaining the service standard type, in the embodiment, Step S102 may include: - Step S1023: an RNSAP message in the N-primitive message is pre-decoded.
- Step S1024: the service standard type of the incoming message is obtained according to a pre-decoded result.
- The whole implementing flow of the embodiment is described below for two implementation of obtaining the service standard type corresponding to
Fig. 4 andFig. 5 respectively. - Taking RNSAP protocol modules of 2G and 3G standards (that is, a GSM RNSAP protocol module and a WCDMA RNSAP protocol module) as an example, the whole implementing flow of the embodiment is described in detail as follows.
- Example one: taking a dual-mode controller receiving a CR message from an abutting RNC as an example, an SCCP protocol module parses the CR message to construct an N-primitive message. If the CR message does not include a Calling address field, then one Calling address field can be filled in after obtaining OPC information by a layer 3 signalling link protocol layer (such as an MTP3B layer, or an M3UA layer or the like) which receives the CR message. A Called address field in the N-primitive message includes transport layer information such as DPC, SSN and the like, and the Calling address field includes transport layer information such as OPC and the like. The SCCP protocol module can also add the OPC and DPC information obtained from a transmission signalling layer into the standard N-primitive message directly. When finding that the SSN is an RNSAP, the SCCP protocol module sends the SSN to a protocol enhancement module. The protocol enhancement module can obtain, by inquiring the standard attribute table according to the transport layer information OPC and DPC in the N-primitive message, that the OPC (opposite end network element signalling point) corresponds to a network element of 3G attribute and the DPC (local end signalling point) corresponds to a network element of 2G attribute, therefore the CR message is a 2G standard service; and the protocol enhancement module can further directly determine, directly according to that the DPC (local end signalling point) corresponds to a network element of 2G attribute, that the CR message is a 2G standard service. The protocol enhancement module sends the N-primitive message to the GSM RNSAP protocol module to continue to process.
- After an SCCP connection is established, the SCCP protocol module has established a correct corresponding relationship of logic entities with the GSM RNSAP protocol module, at this moment, the SCCP protocol module can participle in processing flows no longer, and an incoming message associated with the SCCP connection can be sent to the GSM RNSAP protocol module at the SCCP protocol module.
- Example two: taking a dual-mode controller being configured to a single 3G controller as an example, the dual-mode controller receives a UDT message from an abutting RNC, an SCCP protocol module parses the UDT message to construct an N-primitive message. SSN and DPC information can be obtained from a Called address in the UDT message, and OPC information can be obtained from a Calling address in the UDT message directly. A protocol enhancement module can obtain, according to the transport layer information OPC and DPC in the N-primitive message, that the OPC (opposite end network element signalling point) corresponds to a network element of 3G attribute and the DPC (local end signalling point) corresponds to a network element of 3G attribute, therefore the UDT message is a 3G standard service, and the protocol enhancement module sends the standard N-primitive message to the WCDMA RNSAP protocol module to continue to process.
- Taking RNSAP protocol modules of 2G and 3G standards (that is, a GSM RNSAP protocol module and a WCDMA RNSAP protocol module) as an example, the whole implementing flow of the embodiment is described in detail as follows.
- Example one: taking a dual-mode controller receiving a CR message from an abutting RNC as an example, an SCCP protocol module parses the CR message to construct an N-primitive message, and sends the N-primitive message to a protocol enhancement module in a wireless network control layer, and the protocol enhancement module pre-decodes an RNSAP message in the N-primitive message, wherein the RNSAP message is a wireless link establishment request message of the lur interface, in which has an ID of a cell which is of a 2G standard, therefore the incoming message is a 2G standard service, and the protocol enhancement module sends the N-primitive message to the GSM RNSAP protocol module to continue to process.
- Example two: taking a dual-mode controller being configured to a single 3G controller as an example, the dual-mode controller receives a UDT message from an abutting RNC, an SCCP protocol module parses the UDT message to construct an N-primitive message, and sends the N-primitive message to a protocol enhancement module in a wireless network control layer, and the protocol enhancement module pre-decodes an RNSAP message in the N-primitive message, wherein the RNSAP message is a paging message, in which an ID of a cell which is of a 3G standard is included, therefore the incoming message is a 3G standard service, and the protocol enhancement module sends the N-primitive message to the WCDMA RNSAP protocol module to continue to process.
- In addition, the protocol enhancement module is an independent module listed individually for functionally distinguishing an original standard protocol module, in a specific implementing process, the protocol enhancement module can also be implemented by integrating functions of the protocol enhancement module into an SCCP protocol module, and it needs to modify a part of incoming processing procedure of the SCCP protocol at this moment; the protocol enhancement module can further be implemented by integrating functions of the protocol enhancement module into an RNSAP protocol module, specifically, the SCCP sends all incoming messages to a RNSAP protocol module with a certain standard, the RNSAP protocol module with certain standard forwards, after determining all standard types of all incoming messages, the incoming messages to corresponding standards of RNSAP protocol modules to process. Distinguishing standards and forwarding functions of the protocol enhancement module in the embodiment of the disclosure can further be implemented outside the standard protocol modules or by modifying the standard protocol modules.
- In the embodiment, by adding the protocol enhancement module between the SCCP protocol module and the RNSAP protocol modules to process the N-primitive message received by the multimode controller, the service standard type of the incoming message is obtained, and it is realized that the N-primitive message is sent to the RNSAP protocol module with the corresponding standard on the wireless control plane to process. Wherein, both the protocol enhancement module and the SCCP protocol module are multiplexed by the multimode controller, which not only saves software maintenance cost of the multimode controller, but also makes up shortages of current SCCP and RNSAP protocols when supporting the multimode controller, and realizes a function of distributing signalling according to standards. Furthermore, when being only configured as a single mode or presenting in the manner of multimode, the multimode controller needs not to be modified functionally, and can accurately forward a signalling to a corresponding standard of wireless network control service layer to process.
- As shown in
Fig. 6 , the disclosure proposes a device for processing an incoming message of a multimode controller, which includes: anSCCP protocol module 601, aprotocol enhancement module 602, and multiple different standards ofRNSAP protocol modules 603, wherein: - the
SCCP protocol module 601 is configured to receive an incoming message from an abutting network element, and parse the incoming message to construct an N-primitive message; - the multimode controller receives the incoming message from the abutting network element, and the
SCCP protocol module 601 parses the incoming message to construct the N-primitive message, which includes transport layer information such as SSN, OPC (abutting network element signalling point sending the message), DPC (local end signalling point) and other information associated with a transport layer, if the SSN is an RNSAP, then theSCCP protocol module 601 sends the N-primitive message to theprotocol enhancement module 602; - the
protocol enhancement module 602 is configured to obtain a service standard type of the incoming message according to the N-primitive message, and send the N-primitive message to aRNSAP protocol module 603 with a corresponding standard on a wireless control plane to process; and - the multiple standards of
RNSAP protocol modules 603 are configured to process a corresponding standard of N-primitive message. Each standard service has its own protocol module, there are multiple RNSAP protocol modules according to different standard types, and each RNSAP protocol module with a corresponding standard processes an N-primitive message corresponding to the standard. - In the embodiment, the service standard type of the incoming message is obtained by the
protocol enhancement module 602 according to the N-primitive message, wherein obtaining the service standard type of the incoming message according to the N-primitive message can be completed in a transport network layer (first implementation), and also can be completed in a wireless network layer (second implementation), that is, theprotocol enhancement module 602 can belong to a transmission network user plane of the transport network layer together with theSCCP protocol module 601, and also can belong to a control plane of the wireless network layer together with theRNSAP protocol modules 603. - For the first implementation, the
protocol enhancement module 602 and theSCCP protocol module 601 belong to the transport network layer, and theprotocol enhancement module 602 can obtain the related transport layer information from the N-primitive message, wherein the transport layer information at least includes SSN, OPC, and/or DPC and the like, and can obtain the service standard type of the incoming message according to the transport layer information and the standard attribute table. - The standard attribute table includes: local end signalling points and thereof standard attribute fields, and/or opposite end signalling points and thereof standard attribute fields; or the standard attribute table includes: Origination Point Code (OPC), Destination Point Code (DPC), and corresponding network interface type fields; or the standard attribute table includes: OPC, DPC, corresponding network interface type fields, and standard attribute fields of the OPC.
- For the second implementation, after the
SCCP protocol module 601 receives the incoming message, if the SSN is the RNSAP, then the SCCP protocol module 601sends the N-primitive message to a wireless network layer, and theprotocol enhancement module 602 in the wireless network layer obtains the RNSAP message from the N-primitive message sent by theSCCP protocol module 601, and pre-decodes the RNSAP message, accordingly, that the RNSAP message is which standard service can be determined according to the de-coded result, that is, the service standard type of the above incoming message can be obtained. - After obtaining the service standard type of the incoming message, the incoming message is sent by the
protocol enhancement module 602 to theRNSAP protocol module 603 with the corresponding standard to be processed by theRNSAP protocol module 603 with the corresponding standard. Each standard service has its own protocol module, there are multiple RNSAP protocol modules according to different standard types, and each RNSAP protocol module with corresponding standard processes an N-primitive message corresponding to the standard. - As shown in
Fig. 7 , theprotocol enhancement module 602 includes: aparsing unit 6021 and a standardtype obtaining unit 6022, wherein: - the
parsing unit 6021 is configured to obtain transport layer information by parsing the N-primitive message; and - the standard
type obtaining unit 6022 is configured to obtain the service standard type of the incoming message according to the transport layer information and a standard attribute table. - As mentioned above, the standard attribute table includes: local end signalling points and thereof standard attribute fields, and/or opposite end signalling points and thereof standard attribute fields; or the standard attribute table includes: Origination Point Code (OPC), Destination Point Code (DPC), and corresponding network interface type fields; or the standard attribute table includes: OPC, DPC, corresponding network interface type fields, and standard attribute fields of the OPC.
- The signalling points in the transport layer information correspond to local end network elements and opposite end network elements respectively, the network elements corresponding to the signalling points are of standard attributes, the local end can obtain the standard attribute when docking with an abutting network element, for example, if the abutting network element is a BSC of 2G, then the network element standard attribute of the BSC is 2G. Therefore, a corresponding standard type can be obtained according to the network element standard attributes corresponding to source signalling points and/or target signalling points in the transport layer information; which network interface can also be determined according to a corresponding table between pre-configured signalling points and network interface types, and a corresponding standard type can be obtained according to the network interface directly, for example, an lur interface can be determined according to the OPC and DPC in the transport layer information, and then a 3G standard service can be determined directly; when the standard type cannot determined directly according to the corresponding table between the pre-configured signalling points and the network interface types, the corresponding standard type can be obtained further according to a network element standard attribute corresponding to a source signalling point and/or a target signalling point in the transport layer information, for example, by determining that the network interface is the lur-g interface and in accordance with that the standard type corresponding to the OPC (source signalling point sending the message) is of a 3G standard, then a 2G standard service can be determined.
- A
forwarding unit 6023 is configured to send the N-primitive message according to a standard of the N-primitive message to a RNSAP protocol module with a corresponding standard on a wireless control plane. - Further, the
parsing unit 6021 is further configured to pre-decode the RNSAP message in the N-primitive message; and
the standardtype obtaining unit 6022 is further configured to obtain the service standard type of the incoming message according to a pre-decoded result. - It needs to be illustrated that the
protocol enhancement module 602 is an independent module listed individually for functionally distinguishing an original standard protocol module, in a specific implementing process, theprotocol enhancement module 602 can also be implemented by integrating functions of the protocol enhancement module into anSCCP protocol module 601, and it needs to modify a part of incoming processing procedure of the SCCP protocol at this moment; the protocol enhancement module can further be implemented by integrating functions of the protocol enhancement module into anRNSAP protocol module 603, specifically, the SCCP sends all incoming messages to aRNSAP protocol module 603 with the certain standard, theRNSAP protocol module 603 with certain standard forwards, after determining all standard types of all incoming messages, the incoming messages to corresponding standards of RNSAP protocol modules to process. Distinguishing standards and forwarding functions of theprotocol enhancement module 602 in the embodiment of the disclosure can further be implemented outside the standard protocol modules or by modifying the standard protocol modules. - As shown in
Fig. 8 , one embodiment of the disclosure proposes a multimode controller, which is configured to receive the incoming message from an abutting network element, and parse the incoming message to construct an N-primitive message; and obtain a service standard type of the incoming message according to the N-primitive message; and process the N-primitive message according to the service standard type. - In the embodiment, the multimode controller includes the
device 801 mentioned in the above embodiments. - In the embodiment, by adding the protocol enhancement module between the SCCP protocol module and the RNSAP protocol modules to process the N-primitive message received by the multimode controller, the service standard type of the incoming message is obtained, and it is realized that the N-primitive message is sent to the RNSAP protocol module with the corresponding_standard on the wireless control plane to process. Wherein, both the protocol enhancement module and the SCCP protocol module are multiplexed by the multimode controller, which not only saves software maintenance cost of the multimode controller, but also makes up shortages of current SCCP and RNSAP protocols when supporting the multimode controller, and realizes a function of distributing signalling according to standards. Furthermore, when being only configured as a single mode or presenting in the manner of multimode, the multimode controller needs not to be modified functionally, and can accurately forward a signalling to a corresponding standard of wireless network control service layer to process.
- The above are only preferable embodiments of the present disclosure, and are not used for limiting to the scope of protection of the present disclosure. Any equivalent structures or procedure alternations made by using the description and the drawings of the present disclosure, or direct or indirect applications in other related technical fields thereof shall fall within the scope of protection of the present disclosure.
- By adding a protocol enhancement module, which obtains a service standard type of a message, between an SCCP protocol module and RNSAP protocol modules, the disclosure assists the SCCP protocol module and the RNSAP protocol modules in correctly and quickly establishing a corresponding relationship, saves software maintenance cost, makes up shortages of current SCCP and RNSAP protocols when supporting the multimode controller, and realizes to a function of processing signalling according to standards. Furthermore, when being only configured as a single mode or presenting in the manner of multimode, the multimode controller needs not to be modified functionally, and can accurately forward a signalling to a corresponding standard of wireless network control service layer to process.
Claims (10)
- A method for processing an incoming message of a multimode controller, characterized in that the method comprises:receiving, by a multimode controller, an incoming message from an abutting network element, and parsing the incoming message to construct an N-primitive message (S101);obtaining a service standard type of the incoming message according to the N-primitive message (S102); andprocessing the N-primitive message according to the service standard type (S103).
- The method according to claim 1, wherein the step of obtaining a service standard type of the incoming message according to the N-primitive message comprises:pre-decoding a Radio Network Subsystem Application Part, RNSAP message in the N-primitive message (S1023); andobtaining the service standard type of the incoming message according to a pre-decoded result (S1024).
- The method according to claim 1, wherein the step of obtaining a service standard type of the incoming message according to the N-primitive message comprises:obtaining transport layer information by parsing the N-primitive message (S1021); andobtaining the service standard type of the incoming message according to the transport layer information and a standard attribute table (S1022).
- The method according to claim 3, wherein the standard attribute table comprises:
local end signalling points and thereof standard attribute fields, and/or opposite end signalling points and thereof standard attribute fields;
or the standard attribute table comprises: local end signalling point code, opposite end signalling point code, and corresponding network interface type fields;
or the standard attribute table comprises: local end signalling point code, opposite end signalling point code, corresponding network interface type fields, and standard attribute fields of local or opposite ends. - The method according to claim 3 or 4, wherein the transport layer information comprises Origination Point Code, OPC and/or Destination Point Code, DPC.
- A device for processing an incoming message of a multimode controller, characterized in that the device comprises:a Signalling Connection Control Part, SCCP protocol module (601) configured to receive an incoming message from an abutting network element, and parse the incoming message to construct an N-primitive message;a protocol enhancement module (602) configured to obtain a service standard type of the incoming message according to the N-primitive message, and send the N-primitive message to a corresponding standard of Radio Network Subsystem Application Part, RNSAP protocol module; andRNSAP protocol modules (603) with a corresponding standard configured to process a corresponding standard of N-primitive message,wherein the device is inside a multimode controller.
- The device according to claim 6, wherein the protocol enhancement module (602) comprises:a parsing unit (6021) configured to pre-decode an RNSAP message in the N-primitive message;a standard type obtaining unit (6022) configured to obtain the service standard type of the incoming message according to a pre-decoded result; anda forwarding unit (6023) configured to send the N-primitive message according to the service standard type of the incoming message to the RNSAP protocol module (603) with the corresponding standard on a wireless control plane.
- The device according to claim 7, wherein
the parsing unit (6021) is further configured to obtain transport layer information by parsing the N-primitive message; and
the standard type obtaining unit (6022) is further configured to obtain the service standard type of the incoming message according to the transport layer information and a standard attribute table. - The device according to claim 8, wherein the standard attribute table comprises: local end signalling points and thereof standard attribute fields, and/or opposite end signalling points and thereof standard attribute fields;
or the standard attribute table comprises: local end signalling point code, opposite end signalling point code, and corresponding network interface type fields;
or the standard attribute table comprises: local end signalling point code, opposite end signalling point code, corresponding network interface type fields, and standard attribute fields of local or opposite ends. - A multimode controller, comprising the device according to any one of claims 6 to 9.
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
CN201010546075.1A CN102469622B (en) | 2010-11-16 | 2010-11-16 | Method and device for processing incoming message of multimode controller and multimode controller |
PCT/CN2011/076227 WO2012065442A1 (en) | 2010-11-16 | 2011-06-23 | Method and device for processing multimode controller incoming messages and multimode controller |
Publications (3)
Publication Number | Publication Date |
---|---|
EP2624518A1 EP2624518A1 (en) | 2013-08-07 |
EP2624518A4 EP2624518A4 (en) | 2014-08-06 |
EP2624518B1 true EP2624518B1 (en) | 2018-08-08 |
Family
ID=46072594
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
EP11841339.2A Active EP2624518B1 (en) | 2010-11-16 | 2011-06-23 | Method and device for processing multimode controller incoming messages and multimode controller |
Country Status (5)
Country | Link |
---|---|
US (1) | US9060379B2 (en) |
EP (1) | EP2624518B1 (en) |
JP (1) | JP5688157B2 (en) |
CN (1) | CN102469622B (en) |
WO (1) | WO2012065442A1 (en) |
Families Citing this family (2)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
EP3029999B1 (en) | 2013-08-30 | 2019-10-09 | Huawei Technologies Co., Ltd. | Non-access stratum message processing |
CN115277311B (en) * | 2022-07-15 | 2024-02-20 | 南京邮电大学 | Software definition system and communication control method of multimode gateway |
Family Cites Families (17)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
KR100359059B1 (en) | 1998-12-30 | 2003-01-08 | 엘지정보통신주식회사 | Signal message processing method using signaling network layer protocol in mobile communication network |
US6967964B1 (en) | 2000-10-03 | 2005-11-22 | Telefonaktiebolaget Lm Ericsson (Publ) | Context identification using header compression key at link layer |
EP1871074A1 (en) | 2002-06-07 | 2007-12-26 | Nokia Corporation | Method for sending connection-oriented of connectionless data |
US7400593B2 (en) | 2003-08-15 | 2008-07-15 | Samsung Electronics Co., Ltd | Method for distinguishing MBMS service request from other service requests |
CN1581785A (en) * | 2003-08-15 | 2005-02-16 | 北京三星通信技术研究有限公司 | Method for discriminating MBMS business request from other business requests |
KR101087694B1 (en) * | 2004-08-20 | 2011-11-30 | 에스케이 텔레콤주식회사 | Method and System for Searching Target Cell by Using Multimode-Multiband Terminal in Mobile Communication Environment |
KR100703274B1 (en) * | 2004-12-14 | 2007-04-03 | 삼성전자주식회사 | Apparatus and method for managing user database in mobile terminal |
CN100486217C (en) * | 2005-07-26 | 2009-05-06 | 中兴通讯股份有限公司 | Connection-oriented establishment and message transmitting method on signalling gateway |
KR100678522B1 (en) * | 2005-09-23 | 2007-02-02 | 한국전자통신연구원 | Multi-mode communication system and method thereof |
EP1943862B1 (en) | 2005-11-01 | 2013-06-12 | Intellectual Ventures I LLC | Ps handover support indication |
US20070135121A1 (en) * | 2005-12-08 | 2007-06-14 | Electronics And Telecommunications Research Institute | User and service mobility support system and method in ubiquitous environment |
KR101377948B1 (en) | 2006-04-28 | 2014-03-25 | 엘지전자 주식회사 | Method of transmitting and receiving control information of Multimode mobile terminal |
CN101193351B (en) * | 2006-11-20 | 2011-02-16 | 华为技术有限公司 | Multi-system base station and its information processing method and wireless communication system |
CN101202974B (en) * | 2006-12-15 | 2011-09-28 | 华为技术有限公司 | System, base station and method for multi-standard base station intercommunication |
US20080239987A1 (en) | 2007-03-30 | 2008-10-02 | Tektronix, Inc. | System and Method for Real-Time Iub and Iur Link Detection and AAL5 Channel Detection in UTRAN |
CN101350836A (en) * | 2008-09-16 | 2009-01-21 | 华为技术有限公司 | Ganged method and apparatus for information transmission of CDMA system |
US8204029B2 (en) * | 2008-11-10 | 2012-06-19 | Cisco Technology, Inc. | Mobile intelligent roaming using multi-modal access point devices |
-
2010
- 2010-11-16 CN CN201010546075.1A patent/CN102469622B/en active Active
-
2011
- 2011-06-23 WO PCT/CN2011/076227 patent/WO2012065442A1/en active Application Filing
- 2011-06-23 EP EP11841339.2A patent/EP2624518B1/en active Active
- 2011-06-23 JP JP2013538040A patent/JP5688157B2/en active Active
- 2011-06-23 US US13/881,036 patent/US9060379B2/en active Active
Non-Patent Citations (1)
Title |
---|
None * |
Also Published As
Publication number | Publication date |
---|---|
US9060379B2 (en) | 2015-06-16 |
WO2012065442A1 (en) | 2012-05-24 |
CN102469622A (en) | 2012-05-23 |
EP2624518A1 (en) | 2013-08-07 |
EP2624518A4 (en) | 2014-08-06 |
JP5688157B2 (en) | 2015-03-25 |
JP2014501073A (en) | 2014-01-16 |
CN102469622B (en) | 2014-12-03 |
US20130217438A1 (en) | 2013-08-22 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
EP2169973B1 (en) | Method and device for realizing paging in pool of mobile switching centers | |
CN110300408B (en) | Non-access stratum communication method and equipment in mobile telecommunication system | |
RU2418386C2 (en) | Method, system and media-gateway to implement consolidation of mobile communication switching centres | |
US20200120470A1 (en) | Methods, Core Network Node and RAN Node for Enabling Emergency Services | |
CN101378596B (en) | Method, system and equipment for tracking single user | |
KR102024030B1 (en) | A method and system for handling voice and non-voice calls in a csfb scenario | |
EP2760240B1 (en) | Method, network node and system for determining a capability of a user equipment to support network sharing | |
CN101060652A (en) | A system, equipment and method for solving the mobile exchanging node fault | |
EP2861019B1 (en) | Method for returning to long term evolution network, mobile switching centre and system | |
CN102014365A (en) | Method and system for selecting core network operator from radio network sharing | |
JP2007134841A (en) | Mobile communication system, radio network controller, and method of attaining caller positional information report function used therefor | |
CN103313292A (en) | Inter-system measuring method based on single-baseband chip and double-connection framework | |
US10595353B2 (en) | Improving communication efficiency | |
EP2624518B1 (en) | Method and device for processing multimode controller incoming messages and multimode controller | |
US11622403B2 (en) | Data sending method, apparatus, and system | |
US20180227977A1 (en) | Method for accessing local network, and related device | |
CN101902723B (en) | Method and network for realizing mobile switching centre (MSC) pool network function | |
US9001739B2 (en) | Evolved universal mobile telecommunication radio access network system and task tracking method thereof | |
WO2008100184A1 (en) | Network pooling improvemen |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
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: 20130430 |
|
AK | Designated contracting states |
Kind code of ref document: A1 Designated state(s): AL AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HR HU IE IS IT LI LT LU LV MC MK MT NL NO PL PT RO RS SE SI SK SM TR |
|
DAX | Request for extension of the european patent (deleted) | ||
REG | Reference to a national code |
Ref country code: DE Ref legal event code: R079 Ref document number: 602011050933 Country of ref document: DE Free format text: PREVIOUS MAIN CLASS: H04L0029060000 Ipc: H04Q0003000000 |
|
A4 | Supplementary search report drawn up and despatched |
Effective date: 20140704 |
|
RIC1 | Information provided on ipc code assigned before grant |
Ipc: H04W 88/06 20090101ALI20140630BHEP Ipc: H04Q 3/00 20060101AFI20140630BHEP |
|
GRAP | Despatch of communication of intention to grant a patent |
Free format text: ORIGINAL CODE: EPIDOSNIGR1 |
|
STAA | Information on the status of an ep patent application or granted ep patent |
Free format text: STATUS: GRANT OF PATENT IS INTENDED |
|
INTG | Intention to grant announced |
Effective date: 20180215 |
|
GRAS | Grant fee paid |
Free format text: ORIGINAL CODE: EPIDOSNIGR3 |
|
GRAA | (expected) grant |
Free format text: ORIGINAL CODE: 0009210 |
|
STAA | Information on the status of an ep patent application or granted ep patent |
Free format text: STATUS: THE PATENT HAS BEEN GRANTED |
|
AK | Designated contracting states |
Kind code of ref document: B1 Designated state(s): AL AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HR HU IE IS IT LI LT LU LV MC MK MT NL NO PL PT RO RS SE SI SK SM 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 Ref country code: AT Ref legal event code: REF Ref document number: 1028434 Country of ref document: AT Kind code of ref document: T Effective date: 20180815 |
|
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: 602011050933 Country of ref document: DE |
|
REG | Reference to a national code |
Ref country code: NL Ref legal event code: MP Effective date: 20180808 |
|
REG | Reference to a national code |
Ref country code: LT Ref legal event code: MG4D |
|
REG | Reference to a national code |
Ref country code: AT Ref legal event code: MK05 Ref document number: 1028434 Country of ref document: AT Kind code of ref document: T Effective date: 20180808 |
|
PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
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: 20180808 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: 20181109 Ref country code: RS 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: 20180808 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: 20181208 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: 20181108 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: 20180808 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: 20180808 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: 20180808 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: 20181108 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: 20180808 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: 20180808 |
|
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: 20180808 Ref country code: AL 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: 20180808 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: 20180808 |
|
PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
Ref country code: ES 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: 20180808 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: 20180808 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: 20180808 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: 20180808 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: 20180808 |
|
REG | Reference to a national code |
Ref country code: DE Ref legal event code: R097 Ref document number: 602011050933 Country of ref document: DE |
|
PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
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: 20180808 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: 20180808 Ref country code: SM 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: 20180808 |
|
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 |
|
26N | No opposition filed |
Effective date: 20190509 |
|
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: 20180808 |
|
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: 20180808 |
|
REG | Reference to a national code |
Ref country code: CH Ref legal event code: PL |
|
REG | Reference to a national code |
Ref country code: BE Ref legal event code: MM Effective date: 20190630 |
|
PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
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: 20180808 |
|
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: 20190623 |
|
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 NON-PAYMENT OF DUE FEES Effective date: 20190630 Ref country code: CH Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES Effective date: 20190630 Ref country code: LI Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES Effective date: 20190630 Ref country code: LU Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES Effective date: 20190623 |
|
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: 20181208 |
|
PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
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: 20180808 |
|
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: 20110623 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: 20180808 |
|
PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
Ref country code: MK 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: 20180808 |
|
PGFP | Annual fee paid to national office [announced via postgrant information from national office to epo] |
Ref country code: FR Payment date: 20230510 Year of fee payment: 13 |
|
PGFP | Annual fee paid to national office [announced via postgrant information from national office to epo] |
Ref country code: GB Payment date: 20240402 Year of fee payment: 14 |
|
PGFP | Annual fee paid to national office [announced via postgrant information from national office to epo] |
Ref country code: DE Payment date: 20240328 Year of fee payment: 14 |