CN101035367A - Method for the mobile communication back transfer interface to realize information source integrated access interaction - Google Patents

Abstract

A method for realizing unified access and interaction of information sources through a mobile communication backhaul interface relates to the field of mobile communication, in particular to a mobile communication communication interface. The method comprises the following steps: the client sends a session request message, and the server sends a success message if the processing is successful. After confirming that the session is established, the client and the server exchange session data, and the communication is completed, and the session is closed; if the session is rejected or fails, the server The client returns a session error message, and the client resends a session request message; the client and the server adopt a message-based interface protocol. The invention enables different types of mobile communication clients to perform information interaction in mobile communication according to the invention.

Description

Method for realizing unified access and interaction of information sources through mobile communication backhaul interface

technical field

The invention relates to the field of mobile communication, in particular to a communication interface for mobile communication.

Background technique

With the vigorous development of the mobile communication field, GSM, CDMA, and GPRS have been used unprecedentedly. The recent introduction of the 3G standard has even applied multimedia services to the mobile communication network. With the development of mobile communications, more and more services such as SMS, MMS, and various value-added services have been applied. In the process, each operator and various services use their own independent interface protocols to run, which limits The communication and interaction between various services and many operators limits the wider application of mobile communication.

With the rapid development of mobile communication technology, it is more and more important to use mobile communication network and mobile communication terminal for information interaction, processing and transmission. However, how to realize the common communication interface between terminal and server in mobile communication network has not yet found a feasible method. .

Contents of the invention

The purpose of the present invention is to provide a mobile communication return interface suitable for different types of mobile communication clients to realize unified access and interaction of information sources.

The purpose of the present invention can be achieved in this way, a method for designing a mobile communication return interface to realize the unified access and interaction of information sources, comprising the following steps:

The client sends a session request message, and the server sends a success message if the processing is successful. After confirming that the session is established, the client and the server exchange session data. After the communication is completed, the session is closed; if it refuses or fails, the server returns a session error message , the client resends the session request message;

The client and the server adopt a message-based interface protocol.

The invention enables different types of mobile communication clients to perform information interaction in mobile communication according to the invention.

Detailed ways

Below in conjunction with embodiment the present invention is further described.

A method for realizing unified access and interaction of information sources through a mobile communication return interface, comprising the following steps:

The client sends a session request message, and the server sends a success message if the processing is successful. After confirming that the session is established, the client and the server exchange session data. After the communication is completed, the session is closed; if it refuses or fails, the server returns a session error message , the client resends the session request message;

The client and the server adopt a message-based interface protocol. The communication between the server and the client adopts the message method. For the interface, the front-end system is the server, and the user terminal is the client. Each user terminal can only establish one connection with the front-end system at the same time.

The steps also include that after the server returns a success message, the client sends a test message to check the integrity of the session.

The message includes version information, manufacturer identification information, message type identification, message structure format, message length, parameter type, parameter length, parameter value, and CRC checksum of message data. The version information occupies 1 byte, the identification manufacturer information occupies 2 bytes, the identification message type occupies 2 bytes, the message structure format occupies 2 bytes, the message length occupies 2 bytes, and the parameter type occupies 2 bytes Byte, the parameter length occupies 2 bytes, the parameter value occupies 1 byte, and the CRC checksum of the message data occupies 4 bytes.

The message includes safety data and safety data length. The security data length occupies 1 byte, and the security data occupies 1 byte.

The message structure format includes attribute tags and attribute dependencies. The attribute label occupies 4 characters, and the attribute dependency occupies 12 characters.

The message structure of the return interface protocol is as follows: Generic_message

{

Protocol_version 1byte

Manufacture_id 2byte

Message_type 2byte

Message_attribution() 2byte

Message_length 2byte

For(I=0;I<n;I++) n is the number of parameters

{

Parameter_type 2byte

Parameter_length 2byte

For(I=0;I<m;I++) m is the parameter length

{

Parameter_value_data 1 byte

}

}

Security_data_length 1byte

For(I=0;I<m;I++) m is the safe data length

{

Security_data 1byte

}

CRC32 4byte}

Protocol_version: An 8-bit field identifying the protocol version number, currently 0x01.

Manufacturer_id: ID number identifying the manufacturer. When the value is 0, it means that there is no manufacturer ID number definition.

Message_type: Identifies the message type value.

The Message_attribution structure format is as follows:

Message_attribution

{

Attr_tag 4bit

Attr_dependence 12bit

}

Attr_tag: attribute tag, its definition is shown in the table below: value meaning 0 attribute not applied 1 Apply the encryption property, i.e. the current content is encrypted 2-15 undefined, reserved for future use

Attr_dependence: Attribute dependency. This field definition is related to Attr_tag.

When Attr_tag is 0, this field has no meaning and should be set to all "1".

When Attr_tag is 1, this field indicates the key index value used to encrypt the current content.

When Attr_tag is other values, this field is undefined.

Message_length: message length, which identifies the length of the message data that follows it.

Parameter_type: parameter type. The receiver will ignore the unrecognized parameter type, skip the subsequent length and value fields, and continue to analyze the next parameter value.

Parameter_length: The length of the parameter. Identifies the byte length of the Parameter_value field immediately following it.

Parameter_value_data: parameter value. Its length is specified by Parameter_length.

Security_data_length: Security data length.

Secutity_data: Security data.

Security data is used to ensure the integrity of the data and the authenticity of the message, and its function is equivalent to the digital signature of the message. The use of safety data is optional.

CRC32: CRC checksum of message data.

For all mobile communication environments, this kind of backhaul interface protocol structure can be used to communicate through messages, and can be freely expanded according to the general message structure.

The client communicates and controls according to the server-side interface adaptation message provided by the standard interface. Its main functions include basic communication functions, device control functions, and security control functions, such as transmitting various information such as user management, authorization, tariffs, and personalized services. .

Different types of mobile communication clients can perform information interaction in mobile communication according to the present invention.

The parameter type includes session ID number, user ID number, resource identification number, maximum delay time of message response, and maximum message length.

Refer to the table below for parameter types, parameter type values and parameter lengths: parameter type value Parameter Type Parameter length (byte) 0x0000 reserve 0x0001 Session_id 4 0x0002 User_id 10 0x0010 Resource_id 20 0x0020 Max_time_out 4 0x0020 Max_message_size 4 0x1000 Private_data variable 0x2000 Error_status 2 0x2001 Error_Information variable other undefined reserve

illustrate:

Session_id: ID number identifying the session.

User_id: ID number to identify the user.

Resource_id: resource identification number.

Max_time_out: The maximum delay time for message response, in milliseconds. If the duration is exceeded, the communicating party will consider the session timed out, and the session identified by Session_id will end.

Max_message_size: The maximum message length that the session can allow.

The message types include session establishment message, session test message, session state message, session close message, session close corresponding message, session error message, and data exchange message.

The message type and message type value are as follows: message type value message type 0x0000 reserve 0x0001 Session_setup 0x0002 Session_test 0x0003 Session_status 0x0004 Session_close_request 0x0005 Session_close_response 0x0006 Session_error 0x0007 Session_data_provision 0x0008-0xffff reserve

The session establishment message (Session_setup) includes a User_id parameter, which is used to indicate to the server the object requesting connection; the number of User_id parameters is 1.

For a physical connection, only one session is established at the same time. When the session is established, the client sends a session establishment message (Session_setup) message to the server. If successful, the server returns a session status message (Session_status). If rejected or failed, the server returns a session error message (Session_error), which means that the session has not been opened and needs to be re-established.

A session test message (Session_test) includes a Session_id parameter to detect the current session state. The number of parameters is 1.

A session status message (Session_status) is a response to a session establishment message or a session test message. Contains Session_id, User_id, Max_time_out, Max_message_size parameters, the number of each parameter is 1.

At any time, the server and the client can send a session test message (Session_test) to check the integrity of the session. In reply to this message, the receiving component sends a session status message (Session_status) or a session error message (Session_error).

Session close message (Session_close_request), sent by the client, requests to close the specified session. It contains the Session_id parameter, and Session_id specifies the ID of the session to be closed; the number of parameters is 1.

Session close response message (Session_close_response). It contains the Session_id parameter, and the Session_id identifies the closed session; the number of parameters is 1.

Session closing is always initiated by the client. It is implemented by sending a session close message (Session_close_request) message from the client, and a session close response message (Session_close_response) indicates that the session has been closed.

Session error message (Session_error). The error message sent when the service segment communicates with the client. Sent during a session by any party to the session if the session generates an error. It includes Session_id, Error_status, and Error_information parameters, where the number of Session_id parameters is 1, the number of Error_status parameters is 1~n, and the number of Error_information parameters is 0~m.

Data exchange message (Session_data_provision). Contains Session_id, Private_data parameters. Session_id identifies the session to which the current data exchange belongs, and the number of parameters is 1; Private_data is used to transmit private data during the session, and the number of parameters is 1~n.

After the session is established, the server and the client exchange data through data exchange messages (Session_data_provision). Data exchange messages can be sent by either party of the conversation. Considering that the initial initiator of the session is usually the client, the first data exchange message (Session_data_provision) is usually initiated by the client.

Handling of communication errors. Both the server and the client can handle communication error issues. Either party suspecting a possible loss of communication can send a test message to check the state of the session and expect to receive a status message. If a status message is not received within a given time, the session will be re-established.

If the data received by one party of the session is inconsistency, a Session_error message will be sent to the other party, and both parties of the session will close the session. The client being the initiator of the session will restart the session.

User-defined data, unknown parameter types, or message types shall not be considered inconsistent.

The error states that may occur during a session are listed in the following table. Its value is represented in the parameter Error_status. error status value Parameter Type 0x0000 reserve 0x0001 illegal information 0x0002 Unsupported protocol version 0x0003 unknown message type 0x0004 message too long 0x0005 Unknown User_id value 0x0006 invalid session_id 0x0007 unknown parameter type 0x0008 Invalid parameter value 0x0009 wrong parameter length 0x000A Session timeout 0x000B～0xFFFE reserve 0xFFFF unknown mistake

The invention defines an open mobile communication return interface protocol to realize unified access and interaction of information sources in mobile communication. According to the defined unified and extensible open interface, the client communicates and controls according to the server-side interface adaptation message provided by the standard interface. Its main functions include basic communication functions, device control functions, and security control functions, such as transmitting user management , authorization, tariffs, personalized services and other information. The invention integrates the communication of various mobile communication terminals and server terminals.

Claims (10)

1. A method for realizing unified access and interaction of information sources through a mobile communication return interface, characterized in that it comprises the following steps: The client sends a session request message, and the server sends a success message if the processing is successful. After confirming that the session is established, the client and the server exchange session data. After the communication is completed, the session is closed; if it refuses or fails, the server returns a session error message , the client resends the session request message; The client and the server adopt a message-based interface protocol. 2. The method for realizing unified access and interaction of information sources through the mobile communication backhaul interface according to claim 1, characterized in that: after the server returns a success message, the client sends a test message to check the integrity of the session. 3. The method for realizing unified access and interaction of information sources according to the mobile communication backhaul interface according to claim 1, characterized in that: said message includes version information, manufacturer information, message type, message structure format, message length, parameter type , parameter length, parameter value, CRC checksum of message data. 4. The method for realizing unified access and interaction of information sources through the mobile communication backhaul interface according to claim 1, characterized in that: said message includes security data and security data length. 5. The method for realizing unified access and interaction of information sources through the mobile communication backhaul interface according to claim 3, characterized in that: the message structure format includes attribute labels and attribute dependencies. 6. The method for realizing unified access and interaction of information sources according to the mobile communication backhaul interface according to claim 3, characterized in that: the version information occupies 1 byte, the manufacturer information occupies 2 bytes, and the message type occupies 2 bytes. bytes, message structure format occupies 2 bytes, message length occupies 2 bytes, parameter type occupies 2 bytes, parameter length occupies 2 bytes, parameter value occupies 1 byte, message data CRC check The checksum occupies 4 bytes. 7. The method for realizing unified access and interaction of information sources through the mobile communication backhaul interface according to claim 4, characterized in that: the length of the security data occupies 1 byte, and the security data occupies 1 byte. 8. The method for realizing unified access and interaction of information sources through the mobile communication backhaul interface according to claim 5, characterized in that: the attribute label occupies 4 characters, and the attribute dependency occupies 12 characters. 9. The method for realizing unified access and interaction of information sources through the mobile communication backhaul interface according to claim 3, characterized in that: the parameter type includes session ID number, user ID number, resource identification number, message response Maximum delay time, maximum message length. 10. The method for realizing unified access and interaction of information sources through the mobile communication backhaul interface according to claim 3, characterized in that: the message types include session establishment messages, session test messages, session status messages, session close messages, session Close corresponding messages, session error messages, data exchange messages.