WO2012159291A1 - Method for identifying type of terminal and wireless access network device - Google Patents

Abstract

A method for identifying type of terminal and a wireless access network device are provided by the present invention. The method includes that a wireless access network device receives a message sent from a terminal (11); the wireless access network device analyzes the message and obtains keywords indicating the type of the terminal (12); the wireless access network device determines the type of the terminal according to the keywords (13). The present invention can identify type of terminal on the wireless access network side.

Description

 Method for identifying terminal type and wireless access network device

 The present invention relates to mobile communication technologies, and in particular, to a method for identifying a terminal type and a wireless access network device. Background technique

 With the development of communication technologies, different types of terminals have emerged, such as ordinary mobile phones, smart phones, data cards, and the like. Operators expect to differentiate these different types of terminals on the radio access network side to implement different differentiated services for different types of terminals. However, there is a lack of corresponding solutions in the prior art. Summary of the invention

 The embodiments of the present invention provide a method for identifying a terminal type and a radio access network device, which implements identification of a terminal type on a radio access network side.

 An embodiment of the present invention provides a method for identifying a terminal type, including:

 The radio access network device receives the packet sent by the terminal;

 The radio access network device parses the packet to obtain a keyword indicating a terminal type; the radio access network device determines the type of the terminal according to the keyword.

 An embodiment of the present invention provides a radio access network device, including:

 a receiver, configured to receive a message sent by the terminal;

 a first processor, configured to parse a packet received by the receiver to obtain a keyword indicating a terminal type;

And a second processor, configured to determine a terminal type according to the keyword obtained by the first processor. According to the foregoing technical solution, the embodiment of the present invention identifies the packet sent by the terminal by using the radio access network device, and determines the terminal type according to the identification result, so that the radio access network can be identified. Do not leave the terminal type, and then you can differentiate the terminal. DRAWINGS

 In order to more clearly illustrate the technical solutions in the embodiments of the present invention, a brief description of the drawings to be used in the description of the embodiments will be briefly made. It is obvious that the drawings in the following description are some embodiments of the present invention. It will be apparent to those skilled in the art that other drawings may be obtained from these drawings without the inventive labor.

 1 is a schematic flow chart of a method according to a first embodiment of the present invention;

 2 is a schematic flow chart of a method according to a second embodiment of the present invention;

 FIG. 3 is a schematic structural diagram of a radio access network device according to a third embodiment of the present invention. detailed description

 The technical solutions in the embodiments of the present invention are clearly and completely described in the following with reference to the accompanying drawings in the embodiments of the present invention. It is a partial embodiment of the invention, and not all of the embodiments. All other embodiments obtained by a person of ordinary skill in the art based on the embodiments of the present invention without creative efforts are within the scope of the present invention.

 FIG. 1 is a schematic flowchart of a method according to a first embodiment of the present invention, including:

 Step 11: The radio access network device receives the packet sent by the terminal.

 For example, the packet sent by the terminal is an end-to-end protocol (Peer-Peer Protocol). The protocol stack corresponding to the PPP packet may include: PPP, Internet Protocol (IP), and Transmission Control Protocol (Transmission Control Protocol). TCP) and HyperText Transfer Protocol (HTTP), hereinafter abbreviated as PPP/IP/TCP/HTTP.

 Step 12: The radio access network device parses the packet to obtain a keyword indicating the type of the terminal.

For example, it may specifically include: The radio access network device parses the packet to obtain a hypertext transfer protocol request

(HTTP GET) section;

 The radio access network device parses the HTTP GET part to obtain a user agent (UserAgent) field, and the UserAgent field includes a keyword indicating a terminal type.

 Specifically, when the PPP packet sent by the terminal adopts the HTTP request (GET) method, the PPP packet includes an HTTP GET part. The GET method is a method in which a terminal requests a resource from a server in HTTP. The format is usually "GET" followed by the requested content.

 The HTTP GET part may include a UserAgent field, and the UserAgent field includes a keyword indicating a terminal type.

 At this point, the IP, TCP, and HTTP headers can be parsed in turn to obtain the UserAgent domain. Step 13: The radio access network device determines the type of the terminal according to the keyword.

 The keyword in the UserAgent field can be matched with the pre-configured terminal type field in a matching manner, and the type represented by the successfully matched terminal type field is used as the type of the terminal.

 Specifically, it may include:

 If the keyword is the Microsoft terminal operating system Windows CE, it is determined that the terminal is a mobile version of the Microsoft Windows Mobile terminal; or

 If the keyword is the Google operating system Andriod, it is determined that the terminal is a Google operating system Andriod terminal; or

 If the keyword is an Apple iPhone, determining that the terminal is an Apple iPhone terminal; or

 If the keyword is the Microsoft network terminal operating system Windows NT, determining that the terminal is a data card terminal; or

 If the keyword is a vendor model, it is determined that the terminal is a normal mobile phone.

Among them, the Windows CE operating system is the foundation of Microsoft's embedded and mobile computing platform. It is an open, scalable 32-bit embedded operating system based on handheld computers. Child device operating system. When the terminal adopts the Windows CE operating system, the corresponding keyword is Windows CE. The Android operating system is the name of the open source mobile operating system based on the Linux platform announced by Google. The platform consists of the operating system, middleware, user interface and application software. When the terminal adopts the Android operating system, the corresponding keyword is Android. The iPhone is a handheld device that combines a camera phone, a personal digital assistant, a media player, and a wireless communication device. It was announced by Apple Inc. When the terminal is an iPhone, the corresponding keyword is the iPhone. The Windows NT operating system is a network operating system introduced by Microsoft for workstations, network servers, and mainframe computers. When the terminal adopts the Windows NT operating system, the corresponding keyword is Windows NT.

 In this embodiment, the radio access network device identifies the packet sent by the terminal, and determines the terminal type according to the identification result, so that the terminal type can be identified on the radio access network side, and the terminal can be differentiated. Moreover, further, the embodiment of the present invention does not require special customization, and the scope of application can be expanded with respect to the prior art.

 FIG. 2 is a schematic flowchart of a method according to a second embodiment of the present invention. In this embodiment, a radio access network device is used as a base station controller as an example. Referring to FIG. 2, this embodiment includes:

 Step 201: The base station controller receives the PPP packet sent by the terminal.

 In the prior art, the base station controller transparently transmits the received PPP (the corresponding protocol stack is a PPP/IP/TCP/HTTP) message, and in the embodiment of the present invention, in order to implement terminal identification in the radio access network, The base station controller performs deep packet inspection (DPI) on the received PPP packet. details as follows:

 Step 202: Parse the PPP packet layer by layer according to the IP, TCP, and HTTP headers to obtain the "HTTP Request (GET)" part.

When the terminal uses the HTTP GET method, it can carry a keyword indicating the terminal type in the "UserAgent" field of the "HTTP GET" section. For example, for a Windows Mobile terminal, its "UserAgent" field will contain the keyword "Windows CE"; for an Android terminal, its "UserAgent" field will contain the keyword "Andriod"; for iPhone terminals, its "UserAgent" field will contain the key The word "iPhone"; for a data card terminal, its "UserAgent" field will contain The key word "Windows NT"; for a normal mobile phone, its "UserAgent" field will contain the keyword "vendor model", for example "HW-C7300".

 Step 203: Determine whether the HTTP GET part can be obtained. If yes, execute step 204, no, and go to step 209.

 Through parsing, it can be determined whether the HTTP GET part can be obtained. For example, by parsing the PPP message, it is determined whether there is a "GET" string to determine whether the HTTP GET part can be obtained.

 Step 204: Determine whether the HTTP GET part includes a UserAgent (UserAgent) field. If yes, go to Step 205. Otherwise, go to Step 208.

 By parsing the HTTP GET part, it can be determined whether the UserAgent field can be obtained. For example, by analyzing whether the "UserAgent" string exists, it is determined whether the GET request part contains the UserAgent field.

 Step 205: Perform string matching and judge whether it is successful. If successful, perform step 206. Otherwise, perform step 207.

 For example, the keyword in the UserAgent field is matched with the pre-configured terminal type field. If it matches a certain field, the matching is successful. If the matching with all the pre-configured fields fails, the matching fails.

 Step 206: The identification is successful, and the terminal type is determined.

 Specifically, the terminal type field that successfully matches is used as the type field of the terminal. For example, if the keyword in the UserAgent domain matches "Microsoft Terminal Operating System Windows CE", it indicates that the terminal is a "Windows CE" terminal, that is, a mobile version of Microsoft Terminal (Windows Mobile Terminal).

 Step 207: The identification is completed and it is determined that it is unrecognizable.

 Step 208: Complete the identification and determine that there is no client information.

 Step 209: End the parsing of the PPP packet and continue to parse the next PPP packet.

UserAgent in the HTTP GET request section when the terminal is using the HTTP GET method The type information of the terminal is carried in the domain. In this embodiment, the terminal type can be identified by the radio access network side by identifying it in the base station controller, and the terminal type identification can be completed without special configuration.

 3 is a schematic structural diagram of a radio access network device according to a third embodiment of the present invention. The device may be a base station controller, where the device includes a receiver 31, a first processor 32, and a second processor 33. Receiving a message sent by the terminal; the first processor 32 is configured to parse the message received by the receiver 31 to obtain a keyword indicating a terminal type; the second processor 33 is configured to be used according to the first processor 32. The resulting keyword determines the terminal type.

 Alternatively, the functions of the first processor 32 and the second processor 33 described above may be integrated in one processor.

 The first processor 32 may include: a third processor, configured to parse the message received by the receiver to obtain a hypertext transfer control protocol request HTTP GET part; and a fourth processor, the HTTP GET part A user agent UserAgent field is obtained by parsing, and the UserAgent field includes a keyword indicating the type of the terminal.

 Specifically, the third processor may be specifically configured to sequentially parse the IP, TCP, and HTTP protocols in the file, to obtain the HTTP GET request part.

 In addition, the second processor 33 may be specifically configured to sequentially match the keyword in the UserAgent field with the pre-configured terminal type field, and use the type represented by the successfully matched terminal type field as the type of the terminal.

Specifically, the second processor 33 is specifically configured to: if the keyword is a soft terminal operating system Windows CE, determine that the terminal is a mobile version of a Microsoft Windows Mobile terminal; or if the keyword is a Google operation System Andriod, determining that the terminal is a Google operating system Andriod terminal; or, if the keyword is an Apple iPhone, determining that the terminal is an Apple iPhone terminal; or, if the keyword is a Microsoft network terminal operating system Windows NT, determining that the terminal is a data card terminal; or, if the keyword is a vendor model, determining that the terminal is a normal mobile phone. In this embodiment, the radio access network device identifies the packet sent by the terminal, and determines the terminal type according to the identification result, so that the terminal type can be identified on the radio access network side, and the terminal can be differentiated. Moreover, further, the embodiment of the present invention does not require special customization, and the scope of application can be expanded with respect to the prior art.

 It can be understood that related features in the above methods and devices can be referred to each other. In addition, "first", "second", and the like in the above embodiments are used to distinguish the embodiments, and do not represent the advantages and disadvantages of the embodiments.

 A person skilled in the art can understand that all or part of the steps of implementing the above method embodiments may be completed by using hardware related to program instructions. The foregoing program may be stored in a computer readable storage medium, and when executed, the program includes The foregoing steps of the method embodiment; and the foregoing storage medium includes: a medium that can store program codes, such as a ROM, a RAM, a magnetic disk, or an optical disk.

 It should be noted that the above embodiments are only for explaining the technical solutions of the present invention, and are not intended to be limiting; although the present invention has been described in detail with reference to the foregoing embodiments, it will be understood by those skilled in the art that: The technical solutions described in the foregoing embodiments are modified, or some of the technical features are equivalently replaced. The modifications and substitutions do not depart from the spirit and scope of the technical solutions of the embodiments of the present invention.

Claims

Rights request  A method for identifying a terminal type, comprising:  The radio access network device receives the packet sent by the terminal;  The radio access network device parses the packet to obtain a keyword indicating a terminal type; the radio access network device determines the type of the terminal according to the keyword.  2. The method according to claim 1, wherein the message is a peer-to-peer protocol PPP.  The method according to claim 1 or 2, wherein the radio access network device parses the packet to obtain a keyword indicating that the terminal type includes:  The radio access network device parses the message to obtain a hypertext transfer protocol request HTTP GET part;  The radio access network device parses the HTTP GET part to obtain a user agent UserAgent field, where the UserAgent field includes a keyword indicating a terminal type.  The method according to claim 3, wherein the radio access network device parses the message to obtain an HTTP GET part, including:  The Internet Protocol IP, the Transmission Control Protocol TCP, and the Hypertext Transmission in the message are sequentially parsed. The HTTP GET header is obtained, and the HTTP GET part is obtained.  The method according to claim 3 or 4, wherein the determining the type of the terminal according to the keyword comprises:  The keywords in the UserAgent field are matched with the pre-configured terminal type field in sequence, and the type represented by the successfully matched terminal type field is used as the type of the terminal.  The method according to any one of claims 1-5, wherein the determining the type of the terminal according to the keyword comprises:  If the keyword is the Microsoft mobile operating system Windows CE, it is determined that the terminal is a mobile version of the Microsoft Windows Mobile terminal; or If the keyword is the Google operating system Andriod, it is determined that the terminal is a Google operating system Andriod terminal; or,  If the keyword is an Apple iPhone, determining that the terminal is an Apple iPhone terminal; or  If the keyword is the Microsoft terminal operating system Windows NT, determining that the terminal is a data card terminal; or  If the keyword is a vendor model, it is determined that the terminal is a normal mobile phone.  A radio access network device, comprising:  a receiver, configured to receive a message sent by the terminal;  a first processor, configured to parse a packet received by the receiver to obtain a keyword indicating a terminal type;  And a second processor, configured to determine a terminal type according to the keyword obtained by the first processor.  The device according to claim 7, wherein the first processor comprises: a third processor, configured to parse a message received by the receiver to obtain a hypertext transfer protocol request HTTP GET part ;  The fourth processor parses the HTTP GET part to obtain a user agent UserAgent field, where the UserAgent field includes a keyword indicating a terminal type.  The device according to claim 8, wherein the third processor is specifically configured to sequentially parse the Internet Protocol IP, the Transmission Control Protocol (TCP), and the Hypertext Transfer Protocol (HTTP) in the message. , get the HTTP GET part.  The device according to any one of claims 7-9, wherein the second processor is specifically configured to sequentially match the keyword with a pre-configured terminal type field, and successfully match the terminal type. The type represented by the field is the type of the terminal.  The device according to any one of claims 7 to 10, wherein the second processor is specifically configured to: If the keyword is the Microsoft mobile operating system Windows CE, determining that the terminal is a mobile version of the Microsoft Windows Mobile terminal; or If the keyword is the Google operating system Andriod, determining that the terminal is a Google operating system Andriod terminal; or  If the keyword is an Apple iPhone, determining that the terminal is an Apple iPhone terminal; or  If the keyword is the Microsoft network terminal operating system Windows NT, determining that the terminal is a data card terminal; or  If the keyword is a vendor model, it is determined that the terminal is a normal mobile phone.