WO2018045521A1

WO2018045521A1 - Method and device for transmitting signaling in wireless network

Info

Publication number: WO2018045521A1
Application number: PCT/CN2016/098373
Authority: WO
Inventors: 程竹林
Original assignee: 华为技术有限公司
Priority date: 2016-09-08
Filing date: 2016-09-08
Publication date: 2018-03-15
Also published as: CN109661854A

Abstract

Provided in the embodiments of the present invention are a method and a device for transmitting signaling in a wireless network, which can eliminate the dependence of some private properties on a baseband chip. The method comprises: a transmission terminal transmitting a first IP packet to a reception terminal, the first IP packet comprising first signaling, at least some of fields in the IP header of the first IP packet and/or in the transport layer protocol header of the first IP packet being used for the transmission terminal to recognize the reception terminal, so as to facilitate the reception terminal to parse the first signaling; the transmission terminal receiving a second IP packet in response to the first IP packet, transmitted by the reception terminal, the second IP packet comprising second signaling; according to at least some of the fields in the IP header of the second IP packet and/or in the transport layer protocol header of the second IP packet, the transmission terminal recognizing the reception terminal, and parsing the second signaling.

Description

Method and device for transmitting signaling in a wireless network

Technical field

The present invention relates to the field of wireless communications, and more particularly to a method and apparatus for transmitting signaling in a wireless network.

Background technique

With the development of Internet services, people's bandwidth requirements for wireless networks are getting higher and higher. Many manufacturers in the industry are working on various optimization schemes to improve the air interface bandwidth of the wireless network or improve the user experience. Among these optimization schemes, some optimization schemes require the cooperation of the network and the terminal chip. However, due to the inability of the standard to land, or the late arrival time, these solutions could not provide timely services to customers. If these optimization schemes are to be commercialized in time, they need to consider a non-standard, privatization method, which involves the cooperation of the wireless network and the terminal, that is, the end-pipe coordination.

The network side and the terminal perform private end-pipe collaborative processing on the wireless air interface, and exchange private signaling. The main methods are as follows:

1. Add private signaling through the reserved field or extension field of the existing signaling in the air interface;

2. The private signaling is newly added in the signaling layer of the air interface, such as the Radio Resource Control (RRC) layer of the Long Term Evolution (LTE) or the Network Attached Storage (NAS) layer;

3. In the MAC header of the Media Access Control (MAC) packet of the air interface, the reserved field or the reserved value of some fields is used for marking, and then the private signaling is encapsulated in the MAC packet of the marked air interface. .

However, when the above-mentioned technical solution is used for the end-pipe coordination, the baseband chip of the terminal needs to be modified, so it is necessary to rely on the cooperation of the baseband chip manufacturers, thereby increasing the difficulty of landing the private characteristics of the terminal and the wireless network.

Summary of the invention

Embodiments of the present invention provide a method and apparatus for transmitting signaling in a wireless network, which can get rid of the dependence of part of the private characteristics on the baseband chip of the terminal device.

The first aspect provides a method for transmitting signaling in a wireless network, where: the sending end sends a first Internet Protocol (IP) packet to the receiving end, where the first IP packet includes the first The signaling, the identifier field of the first IP packet is used by the receiving end to identify the sending end, so that the receiving end parses the first signaling, and the identifier field of the first IP packet includes the IP header of the first IP packet and/or Or at least part of the first layer of the transport layer protocol of the first IP packet; the sender receives the second IP packet that is sent by the receiver and responds to the first IP packet, and the second IP packet includes the second signaling; Identifying the receiving end according to the identifier field of the second IP packet, and parsing the second signaling, where the identifier field of the second IP packet includes an IP header of the second IP packet and/or a transport layer of the second IP packet At least some of the fields in the header of the protocol.

In the method for transmitting signaling in a wireless network according to an embodiment of the present invention, a transmitting end (for example, a network device) and a receiving end (for example, a terminal device) may pass at least part of a transport layer protocol header of an IP header and/or an IP packet. The fields identify each other, and the signaling in the IP packet (for example, the first signaling or the second signaling) can be parsed. Since the IP packets sent and received by the terminal device are only processed by the CPU module of the terminal device, instead of being processed by the baseband chip responsible for wireless air interface processing. Therefore, the method for transmitting signaling in the embodiment of the present invention only needs to modify the system software of the terminal device when applying the private signaling interaction between the network device and the terminal device, without modifying the baseband chip of the terminal device. Therefore, it is possible to get rid of the dependence of the partial proprietary features on the baseband chip of the terminal device, and provide a basis for the landing of the partially proprietary end-pipe collaboration feature.

In a possible implementation manner, the value of some or all of the fields in the identification field is different from the value of some or all of the fields in the identification field specified by the RFC specification.

The RFC specification related to the IP header involved in the present invention may be an RFC specification such as RFC1340, RFC1883 or RFC2460, and the RFC specification related to the transport layer protocol header may be an RFC specification such as RFC793, RFC768 or the like.

In this implementation, specifically, the value of some or all of the at least part of the fields in the IP header may be different from the value of some or all of the at least part of the fields specified in the RFC specification. In addition, the value of some or all of the fields in at least part of the fields in the transport layer protocol header may be different from the value of at least part of the fields specified in the RFC specification.

It should be understood that the value of some or all of the fields in the identification field is different from the value of some or all of the fields in the identification field specified by the RFC specification, and refers to the value of some or all of the fields in the identification field. Some or all of the fields in the identification field that are in one-to-one correspondence with some or all of the fields in the identification field specified by the RFC specification are different.

In this implementation, the sender (or the receiver) may set the value of some or all of the fields in the identifier field to some or all of the fields in the identifier field specified by the RFC specification. Different values are used to mark IP packets (for example, the first IP packet and the second IP packet) that encapsulate signaling (for example, the first signaling or the second signaling). In this way, the receiving end (or the transmitting end) can identify and encode some or all of the fields in the identifier field, identify the IP packet encapsulated with signaling, and further parse the signaling in the IP packet, and the sending end. (or the receiving end) for private interaction. The method for transmitting signaling in the wireless network in the embodiment of the present invention does not need to modify the baseband chip of the terminal device, so that the IP packet sent and received by the terminal device is processed by the CPU module of the terminal device. Get rid of the dependence of some proprietary features on the baseband chip of the terminal device.

On the other hand, since the IP headers and/or transport layer protocol headers of these IP packets (for example, the first IP packet and the second IP packet) that encapsulate signaling do not satisfy the definition of the relevant RFC, private The processed network device or terminal device discards these IP packets as invalid packets. Therefore, the method for transmitting signaling in the embodiment of the present invention does not interfere with normal communication of the user when applied to the private signaling interaction between the network device and the terminal device.

In a possible implementation manner, the value of some or all of the fields in the identification field is a reserved value of some or all of the fields in the identification field specified by the RFC specification.

In this implementation, specifically, the value of some or all of the at least part of the fields in the IP header may be a reserved value of some or all of the at least part of the fields specified by the RFC specification. In addition, the value of some or all of the fields in at least part of the fields in the transport layer protocol header may be reserved values of at least part of the fields specified by the RFC specification.

It should be understood that the value of some or all of the fields in at least part of the IP header or transport layer protocol header herein is a reserved value of some or all of the fields in at least part of the fields specified in the RFC specification, and refers to the IP header or The value of some or all of the at least part of the fields in the transport layer protocol header is reserved by the RFC specification for some or all of the at least part of the fields corresponding to some or all of the at least some of the fields. value.

In this implementation, the transmitting end (or the receiving end) marks the encapsulation signaling by marking the IP header of the IP packet or some of the fields in the transport layer protocol header by using the reserved value specified by the RFC specification (for example, the first letter) The IP packet (for example, the first IP packet and the second IP packet) of the command or the second signaling may enable the receiving end (or the transmitting end) to identify and encapsulate the signaling by parsing and determining the fields. The IP packet is used to parse the signaling in the IP packet. In this way, the sender and the receiver can perform private signaling interaction without modifying the baseband chip of the terminal device.

In a possible implementation manner, the transport layer protocol may include a Transmission Control Protocol (TCP) and a User Datagram Protocol (UDP).

In a possible implementation manner, the value of the header checksum field in the IP header is a value calculated according to a preset rule, which is different from the rule specified in the RFC specification.

Optionally, the preset rule is different from the rule specified in RFC791.

In a possible implementation manner, the value of the source port number and the destination port number field of the transport layer protocol header is a preset port number.

In a possible implementation manner, the value of the checksum field in the transport layer protocol header is a value calculated according to a preset rule, which is different from the rule specified in the RFC specification.

Specifically, the preset rule is different from the rules specified in RFC1071, RFC 1141, and RFC1624.

In a possible implementation, the time-to-live or hop limit field in the IP header has a value of zero.

In a possible implementation, before the sending end sends the first Internet Protocol IP packet to the receiving end, the method further includes: receiving, by the sending end, configuration information sent by an operation support system (OSS), and configuring the information. And instructing the sending end to perform signaling interaction with the receiving end based on the identifier field.

The OSS can configure whether the sender supports the identification function of the sender and receiver of the IP packet. In the embodiment of the present invention, the OSS may configure, by using the configuration information, the sending end to perform signaling interaction with the receiving end based on the identifier field. That is, after receiving the configuration information, the transmitting end can identify the IP packet encapsulated by the identifier field, and can parse the signaling encapsulated in the IP packet.

The second aspect provides a method for transmitting signaling in a wireless network, where: the receiving end receives the first Internet Protocol IP packet sent by the sending end, where the first IP packet includes the first signaling, and the receiving end is configured according to the first The identifier field of an IP packet identifies the sender and parses the first signaling. The identifier field of the first IP packet includes an IP header of the first IP packet and/or a transport layer association of the first IP packet. At least part of the field in the header; the receiving end sends a second IP packet in response to the first IP packet to the sending end, the second IP packet includes the second signaling, and the identifier field of the second IP packet is used in the sending end Identifying the receiving end, so that the sending end parses the second signaling, where the identifier field of the second IP packet includes at least part of the IP header of the second IP packet and/or the transport layer protocol header of the second IP packet Field.

In a possible implementation, the transport layer protocol includes a transport control protocol TCP and a user data packet protocol UDP.

Optionally, the preset rule is different from the rule specified in RFC791.

In a possible implementation manner, before the receiving end identifies the sending end according to the identifier field of the first IP packet, the method further includes: receiving, by the receiving end, configuration information sent by the OSS of the operation support system, where the configuration information is used to indicate receiving The terminal performs signaling interaction with the sender based on the identifier field.

The OSS can configure whether the receiving end supports the identification function of the sender and receiver of the IP packet. In the embodiment of the present invention, the OSS may configure the receiving end to perform signaling interaction with the sending end based on the identifier field by using the configuration information. That is, after receiving the configuration information, the receiving end can identify the IP packet encapsulated by the identifier field, and can parse the signaling encapsulated in the IP packet.

In the method for transmitting signaling in a wireless network according to an embodiment of the present invention, a sending end (or a receiving end) may set a value of some fields in an IP header and/or a transport layer protocol header in an IP packet to be an RFC specification. Specify the values of these fields to be different values; or by setting the values of some fields to the reserved values of these fields specified by the RFC specification; or by setting the values of some fields to those of the RFC specification. Values with different values, and the values of other fields are set to the reserved values of these fields specified by the RFC specification, so that the receiving end (or the transmitting end) can identify the transmitting end (or receiving end) as a device for private processing, and further It can parse the signaling in the IP packet and perform private interaction with the sender (or receiver). The method for transmitting signaling in the wireless network in the embodiment of the present invention does not need to modify the baseband chip of the terminal device, so that the IP packet sent and received by the terminal device is processed by the CPU module of the terminal device. Get rid of the dependence of some proprietary features on the baseband chip of the terminal device.

In a third aspect, an apparatus for transmitting signaling in a wireless network is provided for performing the method of the first aspect or any possible implementation of the first aspect. In particular, the apparatus comprises means for performing the method of the first aspect or any of the possible implementations of the first aspect.

In a fourth aspect, an apparatus for transmitting signaling in a wireless network is provided for performing the method of any of the second aspect or the second aspect. In particular, the apparatus comprises means for performing the method of any of the second aspect or any of the possible implementations of the second aspect.

In a fifth aspect, an apparatus for transmitting signaling in a wireless network is provided, the apparatus comprising a receiver, a transmitter, a processor, a memory, and a bus system. The receiver, the transmitter, the processor and the memory are connected by a bus system, the memory is used for storing instructions, and the processor is configured to execute instructions stored in the memory to control the receiver to receive signals and control the transmitter to send signals. And when the processor executes the instructions stored in the memory, performing any possibility that causes the processor to perform the first aspect or the first aspect The method in the implementation.

In a sixth aspect, the present application provides an apparatus for transmitting signaling in a wireless network, the apparatus comprising a receiver, a transmitter, a processor, a memory, and a bus system. The receiver, the transmitter, the processor and the memory are connected by a bus system, the memory is used for storing instructions, and the processor is configured to execute instructions stored in the memory to control the receiver to receive signals and control the transmitter to send signals. And when the processor executes the instructions stored in the memory, the method of causing the processor to perform the second aspect or any of the possible implementations of the second aspect is performed.

In a seventh aspect, the application provides a computer readable medium for storing a computer program, the computer program comprising instructions for performing the method of the first aspect or any of the possible implementations of the first aspect.

In an eighth aspect, the present application provides a computer readable medium for storing a computer program, the computer program comprising instructions for performing the method of any of the second aspect or any of the possible implementations of the second aspect.

DRAWINGS

In order to more clearly illustrate the technical solutions of the embodiments of the present invention, the drawings used in the embodiments or the prior art description will be briefly described below. Obviously, the drawings in the following description are only some of the present invention. For the embodiments, those skilled in the art can obtain other drawings according to the drawings without any creative work.

1 is a schematic diagram of a system architecture of an embodiment of the present invention.

2 is a schematic flowchart of a method for transmitting signaling in a wireless network according to an embodiment of the present invention.

FIG. 3 is a schematic diagram of an IP packet encapsulated by an IP header format of IPV4.

Figure 4 is a schematic diagram of an IP header format based on IPV4.

Figure 5 is a schematic diagram of an IP header format based on IPV6.

Figure 6 is a schematic diagram of the TCP header format.

Figure 7 is a schematic diagram of the UDP header format.

FIG. 8 is a schematic diagram of an IP packet encapsulating signaling by using an IP header format and a UDP header format.

FIG. 9 is a schematic block diagram of an apparatus for transmitting signaling in a wireless network according to an embodiment of the present invention.

FIG. 10 is a schematic block diagram of an apparatus for transmitting signaling in a wireless network according to another embodiment of the present invention.

FIG. 11 is a schematic structural diagram of an apparatus for transmitting signaling in a wireless network according to an embodiment of the present invention.

FIG. 12 is a schematic structural diagram of an apparatus for transmitting signaling in a wireless network according to another embodiment of the present invention; Figure.

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 obvious that the described embodiments are a part of the embodiments of the present invention, but not all embodiments. All other embodiments obtained by those skilled in the art based on the embodiments of the present invention without creative efforts are within the scope of the present invention.

The technical solution of the present invention can be applied to various communication systems, such as: Global System of Mobile Communication (GSM), Code Division Multiple Access (CDMA), Wideband Code Division Multiple Access ( WCDMA (Wideband Code Division Multiple Access Wireless), General Packet Radio Service (GPRS), Long Term Evolution (LTE), etc.

1 is a schematic diagram of a system architecture in accordance with an embodiment of the present invention. As shown in FIG. 1, a network device 101, a terminal device 102, a terminal device 103, and a terminal device 104 are included.

The terminal device 102, the terminal device 103, and the terminal device 104 may also be referred to as a mobile terminal (Mobile Terminal), a mobile user device, etc., and may communicate with the network device 101. The terminal device may be a mobile terminal, such as a mobile phone (or "cellular" phone) and a computer with a mobile terminal, for example, a portable, portable, handheld, computer built-in or in-vehicle mobile device, and a network Device 101 exchanges languages and/or data. The terminal device includes a baseband chip and a central processing unit (CPU). The baseband chip is responsible for the transmission, modulation, demodulation and processing of air interface signaling and air interface data. The CPU is responsible for upper layer service processing, such as related processing of the IP protocol stack.

The network device 103 may be a base station (BTS, Base Transceiver Station) in GSM or CDMA, or may be a base station (NodeB) in WCDMA, or may be an evolved base station in LTE (eNB or e-NodeB, evolutional Node B) The invention is not limited.

In the prior art, the terminal device and the network device perform private end-pipe collaborative processing on the air interface protocol, and when the network device and the terminal device identify and perform signaling interaction, the baseband chip of the terminal device needs to be modified, and therefore needs to rely on the baseband. The cooperation of chip manufacturers has increased the difficulty of landing the proprietary features of the terminal equipment and network equipment. In order to solve the above problem, an embodiment of the present invention provides a method for transmitting signaling in a wireless network, in which a packet carrying signaling can be processed by a CPU without requiring a baseband chip (or called) of the terminal device. Tuning demodulator Modem chip) to modify.

2 is a schematic flowchart of a method 200 of transmitting signaling in a wireless network according to an embodiment of the present invention. The method 200 can be applied to non-standardized private processing between a sender and a receiver. It should be understood that, in the method shown in FIG. 2, the transmitting end may be the terminal device shown in FIG. 1, and the receiving end may be the network device shown in FIG. 1. Alternatively, the transmitting end may be the network device shown in FIG. 1, and the transmitting end may be the terminal device shown in FIG. 1. The method 200 for transmitting signaling in the wireless network according to the embodiment of the present invention is described below by taking the transmitting end as a network device and the receiving end as a terminal device as an example.

S210. The sending end sends the first IP packet to the receiving end.

After the network device is connected to the network, the network device can send a special IP packet to the terminal device, which is called the first IP packet. The sender sets at least part of the IP header of the first IP packet and/or the header of the transport layer protocol as an identifier field, and then encapsulates the first signaling in the first IP packet. After receiving the first IP packet sent by the network device, the terminal device parses and determines the identifier field of the first IP packet, that is, the first IP packet IP header and/or the first IP packet transport layer protocol. The at least part of the fields in the header may determine that the network device is a network device that supports private processing. Furthermore, the terminal device can parse the first signaling in the first IP packet.

The transport layer protocol herein may include the transport control protocol TCP and the user datagram protocol UDP, but the embodiment of the present invention does not limit this.

S220. The receiving end parses the first signaling in the first IP packet according to the first IP packet sent by the sending end.

After receiving the first IP packet, the terminal device can determine that the network device supports the private device by parsing and determining the IP header of the first IP packet and/or at least part of the first layer of the transport layer protocol header of the first IP packet. The network device being processed. Afterwards, the terminal device can parse the first signaling in the first IP packet.

S230. The sending end receives the second IP packet that is sent by the receiving end and responds to the first IP packet.

After the terminal device obtains the first signaling, the terminal device may send a second IP packet to the network device, where the packet is used to respond to the first IP packet. The terminal device also sets at least part of the IP header and/or the transport layer protocol header of the second IP packet as an identifier field, and then encapsulates the second signaling in the first IP packet. After the network device receives the second IP packet, it parses and determines the IP header of the second IP packet and/or the identifier field of the second IP packet, that is, the transport layer protocol header of the second IP packet. At least part of the field, it can be determined that the terminal device is a terminal device that supports private processing. Furthermore, the network device can parse the second signaling in the second IP packet.

S240. The sending end parses the second signaling included in the second IP packet according to the second IP packet sent by the receiving end.

The network device receives the second IP packet, and determines that the terminal device is a terminal that supports private processing by parsing and determining at least part of the IP header of the second IP packet and/or the transport layer protocol header of the first IP packet. device. Then, the network device can parse the second signaling in the second IP packet. That is, after the network device extracts the second IP packet, and determines that the second IP packet satisfies the rules agreed by the two parties, it can be known that the terminal supports private processing, so that the network device and the terminal device can establish private collaborative processing. Channel, the interaction of private signaling.

Therefore, in the method for transmitting signaling in a wireless network according to an embodiment of the present invention, a transmitting end (for example, a network device) and a receiving end (for example, a terminal device) may pass through an IP header and/or an IP packet in a transport layer protocol header. At least some of the fields are identified by each other, and the signaling in the IP packet (for example, the first signaling or the second signaling) can be parsed. Since the IP packets sent and received by the terminal device are only processed by the CPU module of the terminal device, instead of being processed by the baseband chip responsible for wireless air interface processing. Therefore, the method for transmitting signaling in the embodiment of the present invention only needs to modify the system software of the terminal device when applying the private signaling interaction between the network device and the terminal device, without modifying the baseband chip of the terminal device. Therefore, it is possible to get rid of the dependence of the partial proprietary features on the baseband chip of the terminal device, and provide a basis for the landing of the partially proprietary end-pipe collaboration feature.

Before performing non-standardized private processing between the sender and the receiver, the OSS may send configuration information to the sender and the receiver respectively, and configure the sender to support the signaling interaction between the identifier and the receiver. The receiving end is configured to support a function of signaling interaction with the transmitting end based on the identification field. Specifically, for the network device part, if the related function is enabled, the IP packet encapsulated by the identifier field is used to perform signaling interaction with the terminal. For the terminal device, the software of the terminal device is required to perform signaling interaction with the network device by using the IP packet encapsulated in the identifier field.

In the embodiment of the present invention, the identifier field is used to mark the IP packet of the encapsulated signaling. The flag field can be all or part of the field in the IP header. The identification field can also be all or part of a field in the transport layer protocol header. Alternatively, the identifier field may include some or all of the fields in the IP header and some or all of the fields in the transport layer protocol header, which are not limited in this embodiment of the present invention.

The RFC specification related to the IP header involved in the present invention may be an RFC specification such as RFC1340, RFC1883 or RFC2460, and the RFC specification related to the transport layer protocol header may be RFC 793, RFC 768 and other RFC specifications, but the embodiment of the present invention does not limit this.

When the identification field includes all or part of the fields in the IP header, optionally, the value of some or all of the fields in the IP header is different from the value of the part or all of the fields specified in the RFC specification.

Specifically, when the sender and the receiver perform signaling interaction, the value of one or more fields in the IP header that carries the signaling, such as the IP header in the first IP packet and the second IP packet, may be The value of the one or more fields specified by the RFC specification is different. That is, the sender (or the receiver) can set the value of one or more fields in the IP header of the IP packet to a value different from the value of one or more fields specified by the RFC specification. The IP packets encapsulating the signaling (for example, the first IP packet and the second IP packet) are marked. For example, the value of the one or more fields may be a legal value of the one or more fields that are not in compliance with the RFC specification, such as RFC1340, RFC1883, or RFC2460.

For example, the identification field can be a field, which can be a version field. The value field of the version field specified by the RFC specification is 4 or 6. In the embodiment of the present invention, the version field in the IP header of the first IP packet and the second IP packet may be any value other than 4 and not 6. For example, 3, 5, 7, etc. When the version field in the first IP packet and the second IP packet is 5, the network device and the terminal device resolve the IP header, and the value of the version field is determined to be 5, so that the IP packet is determined to be a network device and a terminal. The signaling IP packets are transmitted between the devices, and the signaling in the IP packets can be parsed.

When the identifier field includes all or part of the fields in the IP header, optionally, the value of some or all of the fields in the IP header may be a reserved value of the part or all of the fields specified by the RFC specification.

Specifically, the value of one or more fields in the IP header of the first IP packet and the second IP packet may take a reserved value of the one or more fields specified by the RFC specification. That is, the sender (or the receiver) can mark the reserved value of some fields in the IP header of the IP packet, and then mark the IP packet (for example, the first IP packet and the second packet). Encapsulation signaling in IP packets). Therefore, the receiving end (or the transmitting end) can identify and parse the IP addresses in the IP header by parsing and judging the fields in the IP header, and then parsing the signaling in the IP packet.

For example, the identification field can be a protocol field. The reserved value in the protocol field specified by the RFC specification is 239, indicating the unassigned protocol type. In the embodiment of the present invention, the value of the protocol field may be 239. The network device and the terminal device resolve the IP header, and the value of the protocol field is 239, and the IP packet is determined to be an IP packet for signaling between the network device and the terminal device. In turn, the signaling in the IP packet can be parsed.

The method for transmitting signaling in a wireless network according to an embodiment of the present invention is described in detail below with reference to specific embodiments.

When the network device and the terminal device perform the signaling interaction, the network device and the terminal device may adopt one of the following methods, or combine the following methods to construct an IP packet for encapsulating signaling (for example, the first IP packet and the first Two IP packets).

Mode 1, the sender (or the receiver) adopts IPV4, or adopts IPV6, or encapsulates the packet carrying the signaling by using the same IP protocol version as the data plane of the receiving end (or the transmitting end) according to the result of the negotiation of the wireless air interface. However, the values of the Destination Address and the Source Address field in the IP header use the reserved IP address specified in the RFC specification.

Mode 2: Use IPv4 or IPv6 packet format, but the protocol version number in the IP header is not IPV4 or IPV6, but the value not used in this field in the RFC specification. That is, the Version field in the IP header uses values that are not used in this field in the RFC specification.

Mode 3: The calculation rule for the IP header check is calculated by using a preset rule, and the preset rule is different from the operation rule for the IP header check specified by the RFC specification. For example, the preset rule is different from the one specified in RFC791. That is to say, the value of the Header Checksum field in the IP header may be a value calculated according to a preset rule.

Mode 4, the protocol field of the IP header uses the reserved value specified by the RFC specification.

Mode 5: The time to live (TTL) (for IPv4) or Hop Limit (for IPv6) field of the IP header takes a value of 0.

For the values of other fields in the IP header, refer to the prior art, and details are not described herein again.

In an embodiment provided by the present invention, the IP header format of the IPV4 may be used to encapsulate the signaling, and the signaling may directly serve as the payload of the IP packet, and the format thereof is as shown in FIG. 3 . The IP header format of an IP packet based on IPV4 is shown in Figure 4.

As shown in FIG. 4, for IPV4, the 4-bit version field takes a value of 4. In an embodiment of the invention, the version field may be any integer value other than 4, such as 1, 3, 7, and the like.

Time to live field: The source host sets a lifetime for the packet. For example, 64, the value is decremented by 1 for each router. If it is reduced to 0, it indicates that the route is too long and the destination host's network cannot be found. Discard the package. In the embodiment of the present invention, the value of the time-to-live field may be fixed to 0, but the comparison of the embodiments of the present invention is not limited.

In the existing IPV4 format, the protocol field indicates that the upper layer protocol is TCP, UDP, and Internet control. Internet Control Message Protocol (ICMP) or Internet Group Management Protocol (IGMP). In the embodiment of the present invention, the value of the field may be any value that does not represent the foregoing protocols such as TCP, UDP, ICMP, or IGMP. For example, an unassigned protocol type specified by the RFC specification may be adopted.

Header Checksum Field: This is obtained by examining the IP header using the algorithm for IP header verification as specified by the RFC specification. In the embodiment of the present invention, when the IP header check is performed, a preset rule different from the operation rule specified by the RFC specification may be adopted. For example, a header offset can be obtained by adding a fixed offset value to the result obtained by the checksum calculation method defined by RFC791. As another example, the first offset can be obtained by subtracting the fixed offset value from the result obtained by the checksum calculation method defined by RFC791. Here, this fixed offset value can be any number that is not equal to 0, such as 1, 2, and the like.

In the embodiment of the present invention, the destination address and the source address field may adopt a reserved IP address specified by the RFC specification, such as an IP address that does not appear in normal network communication, such as 0.0.0.0 or 169.254.x.x.

For the Header Length, Type of Service, Total Length, Identifier, Flags, Fragmented Offset shown in FIG. 4, which is not described above. The definitions and values of the fields such as the options and the extensions can be referred to the prior art. For brevity, details are not described herein again.

For example, the corresponding field in the IP header of the embodiment of the present invention, and/or the corresponding field in the IP header of the second IP packet and the value corresponding to the corresponding field may be as shown in Table 1.

Table 1

字段 Field	取值Value

版本version	00
生存时间 Survival time	00
协议protocol	239239
首部检验和First inspection and	(Checksum1+α)％65535(Checksum1+α)%65535
选项Option	无no
扩充expansion	无no

In Table 1, Checksum1 is the checksum obtained by calculating the IP header according to RFC791, and α is any integer not equal to 0. In addition, the value of the option field and the extension field is none, indicating the IP header. There are no option fields and extension fields in the section. Other fields that do not appear in Table 1 may be valued according to RFC specifications or values according to methods of embodiments of the present invention.

In the embodiment of the present invention, the transmitting end (for example, the network device) constructs an IP packet (first IP packet) that encapsulates the first signaling according to the rules shown in Table 1, and the receiving end (for example, the terminal device) parses the version. If the field satisfies the IP packet of the version field shown in Table 1, and further checks the IP packet whose lifetime, protocol, and header checksum fields meet the rules shown in Table 1, the packet is intercepted (here, The first IP packet) and identifies the first signaling therein. Then, the receiving device can also construct a second IP packet according to the rules shown in Table 1, and feedback the first IP packet. Similarly, the sender parses the version field to satisfy the IP packet of the version field shown in Table 1, and further checks the IP packet whose lifetime, protocol, and header checksum fields meet the rules shown in Table 1, and intercepts the IP packet. The message (here, the second IP message) and the signaling therein, that is, the second signaling. It should be noted that the receiving end device may also construct the second IP packet according to the rules shown in Table 1. The second IP packet may be configured by using any one of the foregoing methods 1 to 5 or any of the methods 1 to 5, which is not limited by the embodiment of the present invention.

For example, the corresponding fields in the IP header of the embodiment and/or the IP header of the second IP packet and the corresponding values corresponding to the corresponding fields may be as shown in Table 2.

Table 2

字段Field	取值Value
版本version	44
源地址source address	0.0.0.00.0.0.0
目的地址Destination address	0.0.0.00.0.0.0

Other fields that do not appear in Table 2 may be valued according to the RFC specification or values according to methods of embodiments of the present invention.

In the embodiment of the present invention, the transmitting end (for example, the network device) constructs an IP packet (first IP packet) that encapsulates the first signaling according to the rules shown in Table 1, and the receiving end (for example, the terminal device) parses the version. If the source address and the destination address field satisfy the IP packet of the rule shown in Table 2, the packet is intercepted (here, the first IP packet), and the first signaling is identified. Then, the receiving device can also construct a second IP packet according to the rules shown in Table 2, and feedback the first IP packet. If the sender resolves the IP packet whose version, source address, and destination address field meet the rules shown in Table 2, the packet is intercepted (here, the second IP packet), and the signaling is identified. Two Signaling. It should be noted that the receiving end device may also construct the second IP packet according to the rules shown in Table 2. The second IP packet may be configured by using any one of the foregoing methods 1 to 5 or any of the methods 1 to 5, which is not limited by the embodiment of the present invention.

In another embodiment provided by the present invention, the IPV6 IP header format may be used to encapsulate signaling. The signaling can be directly used as the payload of the IP packet. The format is shown in Figure 3. The IP header format of an IP packet based on IPV6 is shown in Figure 5.

As shown in FIG. 5, for IPV6, the 4-bit version field has a value of 6. In an embodiment of the invention, the version field may be any integer value other than 6, such as 1, 3, 7, and the like. The value of other fields in the IP header may be a legal value specified by the RFC specification, or may be obtained according to other embodiments of the present invention.

Skip Limit Field: Similar to the Time to Live field in IPV4 above. The source host sets a lifetime for the packet. For example, 64, the value is decremented by 1 for each router. If it is reduced to 0, the route is already too long. If the network of the destination host is still not found, the packet is discarded. In the embodiment of the present invention, the value of the hop limit field may be fixed to 0, but the comparison in the embodiment of the present invention is not limited.

In the embodiment of the present invention, the destination address and the source address field may adopt a reserved IP address specified by the RFC specification. For example, the source and destination addresses may be 0:0:0:0:0:0:0:0. The value of other fields in the IP header may be a legal value specified by the RFC specification, or may be obtained in accordance with other embodiments of the present invention.

For the definition and value of the flow class (Traffic Class), flow label (Flow Type, Payload Length, Next Header) and the like shown in FIG. 5, which are not described above, reference may be made to the prior art. For the sake of brevity, we will not repeat them here.

For example, the corresponding fields in the IP header of the embodiment of the present invention and/or the IP header of the second IP packet and the corresponding values corresponding to the corresponding fields may be as shown in Table 3.

table 3

字段Field	取值Value
版本version	55
跳限制 Jump limit	00

For other fields not appearing in Table 3, values may be taken according to the RFC specification or values according to the method of the embodiment of the present invention.

In the embodiment of the present invention, the sending end (for example, the network device) follows the rules shown in Table 3. The IP packet (the first IP packet) of the first signaling is encapsulated, and the receiving end (for example, the terminal device) parses the IP packet of the version field in the version field shown in Table 3, and further checks that the hop limit field is also satisfied. The rule IP packet shown in Table 3 intercepts the packet (here, the first IP packet) and identifies the first signaling therein. Then, the receiving device can also construct a second IP packet according to the rules shown in Table 3, and feedback the first IP packet. Similarly, the sender parses the version field to satisfy the IP packet of the version field shown in Table 1, and further checks the IP packet whose hop limit field also satisfies the rule shown in Table 3, and intercepts the packet (here, The second IP packet), and identifies the signaling therein, that is, the second signaling. It should be noted that the receiving end device may also construct the second IP packet according to the rules shown in Table 3. The second IP packet may also meet only one of the conditions in Table 3, but the embodiment of the present invention does not limit this.

Therefore, in the method for transmitting signaling in the wireless network according to the embodiment of the present invention, the transmitting end (or the receiving end) may set the value of at least part of the field in the IP header in the IP packet to at least part of the RFC specification. The value of the field is different, or the value of the at least part of the field is set to a reserved value of at least part of the field specified by the RFC specification to mark the encapsulated IP packet, so that the receiving end (or the transmitting end) can Identifying the sender (or receiver) as a device for private processing, and thus being able to parse the signaling and perform private interaction with the sender (or receiver). The method for transmitting signaling in the wireless network in the embodiment of the present invention does not need to modify the baseband chip of the terminal device, so that the IP packet sent and received by the terminal device is processed by the CPU module of the terminal device. Get rid of the dependence of some proprietary features on the baseband chip of the terminal device.

On the other hand, because the IP headers of the IP packets (for example, the first IP packet and the second IP packet) that encapsulate the signaling do not meet the definition of the relevant RFC, the network device or the terminal device that does not support private processing is not supported. These IP packets are discarded as invalid packets. Therefore, the method for transmitting signaling in the embodiment of the present invention does not interfere with normal communication of the user when applied to the private signaling interaction between the network device and the terminal device.

When the identification field includes all or part of the fields in the transport layer protocol header, optionally, the value of all or part of the fields in the transport layer protocol header is different from the value of the all or part of the field specified by the RFC specification.

Specifically, when the sender and the receiver perform signaling interaction, the IP packet carrying the signaling (for example, the first signaling or the second signaling), for example, the transmission in the first IP packet and the second IP packet All or part of the fields in the layer protocol header may be different from the values of all or part of the fields specified in the RFC specification. That is to say, the transmitting end (or receiving end) can pass the transport layer protocol of the IP packet. The value of all or part of the fields in the header is set to a value different from the value of all or part of the fields specified in the RFC specification, and the IP packet encapsulated by the signaling (for example, the first IP packet and the second IP packet) Mark). For example, the value of the all or part of the field may be a legal value that does not comply with the RFC specification, such as RFC793, RFC768, etc., all or part of the field. At the same time, when all or part of the fields in the header of the transport layer protocol are different from the values of all or part of the fields specified in the RFC specification, the values of all or part of the fields in the IP header are the same as those specified in the RFC specification. The value of the partial field may be the same or different, which is not limited by the embodiment of the present invention.

When the identification field includes all or part of the fields in the transport layer protocol header, optionally, the value of at least part of the fields in the transport layer protocol header may be a reserved value of the at least part of the field specified by the RFC specification.

Specifically, the values of all or part of the fields in the transport layer protocol header of the first IP packet and the second IP packet may take the reserved value of the all or part of the field specified by the RFC specification. That is, the sender (or receiver) can mark the reserved values of certain fields in the transport layer protocol header of the IP packet, and then mark the IP packets (for example, the first IP packet and Signaling in the second IP packet). Therefore, the receiving end (or the transmitting end) can identify the IP packets encapsulated with signaling by parsing and judging these fields in the header of the transport layer protocol, and then parsing the signaling in the IP packet.

For example, the all or part of the field may be a source port number and a destination port number field. The network device and the terminal device resolve the IP header. When the value of the source port number and the destination port number field is determined as a reserved value pre-agreed by the network device and the terminal device, the IP packet can be determined to be between the network device and the terminal device. The signaling IP packet is transmitted, and then the signaling can be parsed.

As an embodiment, the network device and the terminal device may adopt one of the mode 6 and the mode 7, or adopt a combination of the mode 6 and the mode 7 to construct an IP packet encapsulating the signaling packet (for example, the first IP packet and the first packet) Two IP packets):

Manner 6, the operation rule for the first layer check of the transport layer protocol is calculated by using a preset rule, which is different from the operation rule for the IP header check specified by the RFC specification. For example, the preset rule is different from the one specified in RFC791. That is to say, the value of the checksum field in the header of the transport layer protocol may be a value calculated according to a preset rule.

In the mode 7, the source port number and the destination port number in the header of the transport layer protocol adopt a port number pre-agreed by the sender and the receiver.

For the values of other fields in the transport layer protocol header, refer to the prior art, and details are not described herein again.

It should be noted that, in the embodiment of the present invention, the value of the checksum, the source port number, and the destination port number field of the first IP packet and the second IP packet may be the same or different, and the embodiment of the present invention is different. This is not limited.

Hereinafter, a method for transmitting signaling in a wireless network according to an embodiment of the present invention will be described by taking a transport layer protocol as TCP and UDP as an example.

The TCP header format is shown in Figure 4.

As shown in Figure 4, the existing RFC specification specifies that the source port number and the destination port number are used to identify the port number of the remote end and the local port, that is, the port numbers of the sender and the receiver. In the embodiment of the present invention, the value of the source port number and the destination port number field may be a port number pre-agreed by the sender and the receiver. For example, the source port number and destination port number fields all have a value of 65530. The values of other fields in the TCP header may be obtained in accordance with the RFC specification, or may be obtained in accordance with other embodiments of the present invention.

Checksum field: In the embodiment of the present invention, when the TCP header check is performed, a custom rule different from the operation rule specified by the protocol may be adopted. For example, a fixed offset value can be added to the result obtained by the checksum calculation method defined by the RFC specification to obtain a checksum. As another example, the first offset can be obtained by subtracting the fixed offset value from the result obtained by the checksum calculation method defined by the RFC specification. Here, this fixed offset value can be any number that is not equal to 0, such as 1, 2, and the like. The values of other fields in the TCP header may be obtained in accordance with the RFC specification, or may be obtained in accordance with other embodiments of the present invention.

For the sequence number, Acknowledge Number, Header Length, Reserved, Urgent, URG, Acknowledge, ACK shown in Figure 6 not described above. ), push bit (Push, PSH), reset bit (Reset, RST), sync bit (Sync, SYN), stop bit (, Final, FIN), window size (Window), Urgent Pointer (Urgent Pointer), option ( The definitions and values of fields such as Options and Padding can be referred to the prior art, and are not described here for brevity.

The UDP header format is shown in Figure 7.

As shown in Figure 7, the existing RFC specification specifies that the source port number and the destination port number are used to identify the remote and local port numbers, that is, the port numbers of the sender and the receiver. In the embodiment of the present invention, The value of the source port number and the destination port number field may be a port number pre-agreed by the sender and the receiver. For example, the source port number and destination port number fields all have a value of 65530. The values of other fields in the TCP header may be obtained in accordance with the RFC specification, or may be obtained in accordance with other embodiments of the present invention.

Checksum field: is set to ensure high reliability. In the embodiment of the present invention, when performing the UDP header check, a custom rule different from the operation rule specified by the RFC specification may be adopted. For example, a fixed offset value can be added to the result obtained by the checksum calculation method defined by the RFC specification to obtain a checksum. As another example, the first offset can be obtained by subtracting the fixed offset value from the result obtained by the checksum calculation method defined by the RFC specification. Here, this fixed offset value can be any number that is not equal to 0, such as 4, 6, and so on.

For the definition and value of the UDP length field shown in FIG. 7 which is not described above, reference may be made to the prior art, and for brevity, no further details are provided herein.

In the method for transmitting signaling in the wireless network according to the embodiment of the present invention, the first relevant field of the transport layer protocol of the IP packet adopts a legal value that does not comply with the RFC specification or uses a reserved value specified by the RFC specification, so that the receiver can be normal. The data communication message intercepts the packet carrying the signaling, so that the terminal device and the network device can identify and interact based on the IP packet. Since the IP packets sent and received by the terminal device are only processed by the CPU module of the terminal device, instead of being processed by the baseband chip responsible for wireless air interface processing. Therefore, the method for transmitting signaling in the embodiment of the present invention only needs to modify the system software of the terminal device, and does not need to modify the baseband chip of the terminal device, so as to get rid of the dependence of the partial private feature on the baseband chip of the terminal device. Provide the basis for the landing of some of the proprietary end-pipe collaboration features.

On the other hand, because the transport layer protocol header of these IP packets (for example, the first IP packet and the second IP packet) that encapsulate signaling does not satisfy the definition of the relevant RFC, the network device that does not support private processing or The terminal device discards these IP packets as invalid packets. Therefore, the method for transmitting signaling in the embodiment of the present invention does not interfere with normal communication of the user when applied to the private signaling interaction between the network device and the terminal device.

In another embodiment provided by the present invention, the IP header format and the UDP header format may be used to encapsulate signaling, and the signaling may directly serve as a payload of the IP packet, and its format is as shown in FIG. 8. For example, the corresponding fields in the IP header and the UDP header of the IP packet of the embodiment of the present invention and the corresponding values corresponding to the corresponding fields may be respectively shown in Table 4 and Table 5.

Table 4

字段Field	取值Value
版本version	44
协议protocol	1717
源地址source address	0.0.0.00.0.0.0
目的地址Destination address	0.0.0.00.0.0.0
选项Option	无no
扩充expansion	无no

table 5

字段Field	取值Value
源端口号Source port number	6553065530
目的端口号Destination port number	6553065530
校验和Checksum	(Checksum2+β)％65535(Checksum2+β)%65535

In Table 3, the value of the option field and the augmentation field is none, indicating that there are no option fields and extension fields in the IP header. In Table 5, Checksum2 may be a result obtained by verifying the UDP header according to RFC1071, RFC1141, or RFC1624, and β is any integer not equal to 0.

The values of the fields that are not present in Tables 4 and 5 can be obtained according to the RFC specification, or obtained according to the method of the embodiment of the present invention.

In the embodiment of the present invention, the transmitting end (for example, the network device) constructs an IP packet (first IP packet) for encapsulating signaling (first signaling) according to the rules shown in Table 4 and Table 5, and the receiving end ( For example, the terminal device parses the version, the protocol, the source address, and the destination address field to satisfy the value of the corresponding field shown in Table 4, and further parses the UDP header in the IP packet. If the source port number, the destination port number, and the checksum field of the UDP header meet the values of the corresponding fields in Table 5, the packet is intercepted (here, the first IP packet), and the identifier is identified. First signaling. Then, the receiving device can also construct a second IP packet according to the rules shown in Table 4 and Table 5, and feedback the first IP packet. Similarly, the sender parses the IP packet whose version field satisfies the value of the corresponding field shown in 4, and further parses the UDP header in the IP packet. If the source port number, the destination port number, and the checksum field of the UDP header meet the values of the corresponding fields in Table 5, the packet is intercepted (here, the second IP packet), and the identifier is identified. Signaling, that is, second signaling. It should be noted that the receiving end device may also construct the second IP packet according to the rules shown in Table 4 and Table 5. However, the embodiment of the present invention does not limit this.

The method for transmitting signaling in the wireless network according to the embodiment of the present invention, the IP packet for encapsulating signaling may satisfy any one of the manners 1 to 7 described in the foregoing manner, or the manners of the manners 1 to 7 are simultaneously adopted. Combine in any number of ways. The method for transmitting signaling in the wireless network according to the embodiment of the present invention can implement private identification of the network device and the terminal device on the basis of the baseband chip that does not depend on the terminal device, thereby providing a basis for private enhanced feature processing.

Hereinabove, a method of transmitting signaling in a wireless network according to an embodiment of the present invention is described in conjunction with FIGS. 1 through 8. Hereinafter, an apparatus for transmitting signaling in a wireless network according to an embodiment of the present invention will be described with reference to FIGS. 9 through 12.

FIG. 9 shows a schematic block diagram of an apparatus 900 for transmitting signaling in a wireless network in accordance with an embodiment of the present invention. As shown in FIG. 9, the apparatus 900 includes a transmitting unit 910, a receiving unit 920, and a processing unit 930.

The sending unit 910 is configured to send the first Internet Protocol IP packet to the receiving end, where the first IP packet includes the first signaling, and the identifier field of the first IP packet is used by the receiving end to identify the device 900, so as to be received. The end parses the first signaling, where the identifier field of the first IP packet includes an IP header of the first IP packet and/or at least a part of a transport layer protocol header of the first IP packet.

The receiving unit 920 is configured to receive a second IP packet sent by the receiving end and sent by the sending unit 910, where the second IP packet includes the second signaling.

The processing unit 930 is configured to identify the receiving end according to the identifier field of the second IP packet received by the receiving unit 920, and parse the second signaling, where the identifier field of the second IP packet includes the IP header of the second IP packet. And/or at least a portion of the fields in the transport layer protocol header of the second IP message.

The units of the apparatus 900 for transmitting signaling in the wireless network according to the embodiment of the present invention and the other operations or functions described above are respectively implemented by the transmitting end to implement the above method. For the sake of brevity, it will not be repeated here.

Therefore, the apparatus for transmitting signaling in the wireless network according to the embodiment of the present invention may set the value of at least part of the IP header in the IP packet and/or the header of the transport layer protocol to at least the value specified in the RFC specification. The value of the partial field is different, or the value of the at least part of the field is set to a reserved value of at least part of the field specified by the RFC specification, so that the receiving end can identify the device as a device for private processing, and thus can parse the IP. Signaling in the message, private interaction with the device. When the device is a terminal device or the receiving end is a terminal device, since the IP packet sent and received by the terminal device is only processed by the CPU module of the terminal device, the device for transmitting signaling in the wireless network according to the embodiment of the present invention No need to modify the baseband chip, or The receiver can be modified so that the baseband chip does not need to be modified, so that the dependence of the partial proprietary chip on the baseband chip can be eliminated.

FIG. 10 shows a schematic block diagram of an apparatus 1000 for transmitting signaling in a wireless network in accordance with an embodiment of the present invention. As shown in FIG. 10, the apparatus 1000 includes a receiving unit 1010, a processing unit 1020, and a transmitting unit 1030.

The receiving unit 1010 is configured to receive a first Internet Protocol IP packet sent by the sending end, where the first IP packet includes the first signaling.

The processing unit 1020 is configured to identify the sending end according to the identifier field of the first IP packet received by the receiving unit 1010, and parse the second signaling, where the identifier field of the first IP packet includes an IP header of the first IP packet. And/or at least part of a field in the transport layer protocol header of the first IP message.

The sending unit 1030 is configured to send, to the sending end, the second IP packet of the first IP packet that is received by the receiving unit 1010, where the second IP packet includes the second signaling, and the identifier field of the second IP packet is used to send The device identifies the device 1000, so that the sending end parses the second signaling, where the identifier field of the second IP packet includes at least an IP header of the second IP packet and/or a transport layer protocol header of the second IP packet. Part of the field.

The units of the apparatus 1000 for transmitting signaling in the wireless network according to the embodiment of the present invention and the other operations or functions described above are respectively performed by the receiving end to implement the above-described method. For the sake of brevity, it will not be repeated here.

Therefore, the apparatus for transmitting signaling in the wireless network according to the embodiment of the present invention may set the value of at least part of the IP header in the IP packet and/or the header of the transport layer protocol to at least the value specified in the RFC specification. The value of the partial field is different, or the value of the at least part of the field is set to a reserved value of at least part of the field specified by the RFC specification, so that the transmitting end can identify the device as a device for private processing, and thus can parse the IP. Signaling in the message, private interaction with the device. When the device is a terminal device or the transmitting device is a terminal device, the device that transmits the signaling in the wireless network according to the embodiment of the present invention is only required to process the IP packet sent and received by the terminal device only by the CPU module of the terminal device. There is no need to modify the baseband chip, or the sender may not need to modify the baseband chip, so as to get rid of the dependence of the partial proprietary features on the baseband chip.

FIG. 11 is a schematic structural diagram of an apparatus 1100 for transmitting signaling in a wireless network according to an embodiment of the present invention. As shown in FIG. 11, the apparatus 1100 includes a receiver 1110, a transmitter 1120, a processor 1130, a memory 1140, and a bus system 1150. Wherein, the receiver 1110, the transmitter 1120, The processor 1130 and the memory 1140 are connected by a bus system 1150 for storing instructions for executing instructions stored by the memory 1140 to control the receiver 1110 to receive signals and controlling the transmitter 1120 to transmit signals.

The sender 1120 is configured to send the first Internet Protocol IP packet to the receiving end, where the first IP packet includes the first signaling, and the identifier field of the first IP packet is used by the receiving end to identify the device 1100. The first signaling is parsed by the receiving end, and the identifier field of the first IP packet includes an IP header of the first IP packet and/or at least a part of a transport layer protocol header of the first IP packet.

The receiver 1110 is configured to receive a second IP packet sent by the receiving end in response to the first IP packet sent by the sender 1120, where the second IP packet includes the second signaling.

The processor 1130 is configured to identify the receiving end according to the identifier field of the second IP packet received by the receiver 1110, and parse the second signaling, where the identifier field of the second IP packet includes the IP header of the second IP packet. And/or at least a portion of the fields in the transport layer protocol header of the second IP message.

It should be understood that, in the embodiment of the present invention, the processor 1130 may be a central processing unit ("CPU"), and the processor 1130 may also be other general-purpose processors, digital signal processors (DSPs). , an application specific integrated circuit (ASIC), an off-the-shelf programmable gate array (FPGA) or other programmable logic device, discrete gate or transistor logic device, discrete hardware component, and the like. The general purpose processor may be a microprocessor or the processor or any conventional processor or the like.

The memory 1140 can include read only memory and random access memory and provides instructions and data to the processor 1130. A portion of the memory 1140 can also include a non-volatile random access memory. For example, the memory 1140 can also store information of the device type.

The bus system 1150 may include a power bus, a control bus, a status signal bus, and the like in addition to the data bus. However, for clarity of description, various buses are labeled as bus system 1150 in the figure.

In the implementation process, each step of the foregoing method may be completed by an integrated logic circuit of hardware in the processor 1130 or an instruction in a form of software. The steps of the method for transmitting signaling in the wireless network in combination with the embodiment of the present invention may be directly implemented by the hardware processor, or may be performed by a combination of hardware and software modules in the processor. The software module can be located in a conventional storage medium such as random access memory, flash memory, read only memory, programmable read only memory or electrically erasable programmable memory, registers, and the like. The storage medium is located in the memory 1140, and the processor 1130 reads the information in the memory 1140 and completes the steps of the above method in combination with its hardware. To avoid repetition, it will not be described in detail here.

The units of the apparatus for transmitting signaling in the wireless network according to the embodiment of the present invention and the other operations or functions described above are respectively implemented by the transmitting end to implement the above method. For the sake of brevity, it will not be repeated here.

Therefore, the apparatus for transmitting signaling in the wireless network according to the embodiment of the present invention may set the value of at least part of the IP header in the IP packet and/or the header of the transport layer protocol to at least the value specified in the RFC specification. The value of the partial field is different, or the value of the at least part of the field is set to a reserved value of at least part of the field specified by the RFC specification, so that the receiving end can identify the device as a device for private processing, and thus can parse the IP. Signaling in the message, private interaction with the device. When the device is a terminal device or the receiving end is a terminal device, since the IP packet sent and received by the terminal device is only processed by the CPU module of the terminal device, the device for transmitting signaling in the wireless network according to the embodiment of the present invention There is no need to modify the baseband chip, or the receiving end does not need to modify the baseband chip, so that the dependence of the partial proprietary characteristics on the baseband chip can be eliminated.

FIG. 12 is a schematic structural diagram of an apparatus 1200 for transmitting signaling in a wireless network according to an embodiment of the present invention. As shown in FIG. 12, the apparatus 1200 includes a receiver 1210, a transmitter 1220, a processor 1230, a memory 1240, and a bus system 1250. The receiver 1210, the transmitter 1220, the processor 1230, and the memory 1240 are connected by a bus system 1250 for storing instructions for executing the instructions stored by the memory 1240 to control the receiver 1210 to receive. Signal, and control transmitter 1220 to send a signal.

The receiver 1210 is configured to receive a first Internet Protocol IP packet sent by the sending end, where the first IP packet includes the first signaling.

The processor 1230 is configured to identify the sending end according to the identifier field of the first IP packet received by the receiver 1210, and parse the first signaling, where the identifier field of the first IP packet includes an IP header of the first IP packet. And/or at least part of a field in the transport layer protocol header of the first IP message.

The transmitter 1220 is configured to send, to the sending end, a second IP packet that is sent to the first IP packet that is received by the receiver 1210, where the second IP packet includes the second signaling, and the identifier field of the second IP packet is used to send The device 1200 is configured to identify the second signaling, where the identifier field of the second IP packet includes at least one of an IP header of the second IP packet and/or a transport layer protocol header of the second IP packet. Part of the field.

It should be understood that, in the embodiment of the present invention, the processor 1230 may be a central processing unit ("CPU"), and the processor 1230 may also be another general-purpose processor. Digital signal processor (DSP), application specific integrated circuit (ASIC), off-the-shelf programmable gate array (FPGA) or other programmable logic device, discrete gate or transistor logic device, discrete hardware component, etc. The general purpose processor may be a microprocessor or the processor or any conventional processor or the like.

The memory 1240 can include read only memory and random access memory and provides instructions and data to the processor 1230. A portion of the memory 1240 may also include a non-volatile random access memory. For example, the memory 1240 can also store information of the device type.

The bus system 1250 may include a power bus, a control bus, a status signal bus, and the like in addition to the data bus. However, for clarity of description, various buses are labeled as bus system 1250 in the figure.

In the implementation process, each step of the above method may be completed by an integrated logic circuit of hardware in the processor 1230 or an instruction in a form of software. The steps of the method for transmitting signaling in the wireless network in combination with the embodiment of the present invention may be directly implemented by the hardware processor, or may be performed by a combination of hardware and software modules in the processor. The software module can be located in a conventional storage medium such as random access memory, flash memory, read only memory, programmable read only memory or electrically erasable programmable memory, registers, and the like. The storage medium is located in the memory 1240, and the processor 1230 reads the information in the memory 1240 and, in conjunction with its hardware, performs the steps of the above method. To avoid repetition, it will not be described in detail here.

The units of the apparatus for transmitting signaling in the wireless network according to the embodiment of the present invention and the other operations or functions described above are respectively performed by the receiving end to implement the above-described method. For the sake of brevity, it will not be repeated here.

It should be understood that the term "and/or" herein is merely an association describing the associated object. It is indicated that there may be three kinds of relationships, for example, A and/or B, which may indicate that there are three cases where A exists separately, A and B exist at the same time, and B exists separately. In addition, the character "/" in this article generally indicates that the contextual object is an "or" relationship.

It should be understood that, in various embodiments of the present invention, the size of the sequence numbers of the above processes does not mean the order of execution, and the order of execution of each process should be determined by its function and internal logic, and should not be taken to the embodiments of the present invention. The implementation process constitutes any limitation.

Those of ordinary skill in the art will appreciate that the elements and algorithm steps of the various examples described in connection with the embodiments disclosed herein can be implemented in electronic hardware or a combination of computer software and electronic hardware. Whether these functions are performed in hardware or software depends on the specific application and design constraints of the solution. A person skilled in the art can use different methods for implementing the described functions for each particular application, but such implementation should not be considered to be beyond the scope of the present invention.

A person skilled in the art can clearly understand that for the convenience and brevity of the description, the specific working process of the system, the device and the unit described above can refer to the corresponding process in the foregoing method embodiment, and details are not described herein again.

In the several embodiments provided by the present application, it should be understood that the disclosed systems, devices, and methods may be implemented in other manners. For example, the device embodiments described above are merely illustrative. For example, the division of the unit is only a logical function division. In actual implementation, there may be another division manner, for example, multiple units or components may be combined or Can be integrated into another system, or some features can be ignored or not executed. In addition, the mutual coupling or direct coupling or communication connection shown or discussed may be an indirect coupling or communication connection through some interface, device or unit, and may be in an electrical, mechanical or other form.

The units described as separate components may or may not be physically separated, and the components displayed as units may or may not be physical units, that is, may be located in one place, or may be distributed to multiple network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution of the embodiment.

In addition, each functional unit in each embodiment of the present invention may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit.

The functions may be stored in a computer readable storage medium if implemented in the form of a software functional unit and sold or used as a standalone product. Based on such understanding, the technical solution of the present invention is essentially or a part contributing to the prior art or a part of the technical solution. The points may be embodied in the form of a software product stored in a storage medium, including instructions for causing a computer device (which may be a personal computer, server, or network device, etc.) to perform various embodiments of the present invention All or part of the steps of the method. The foregoing storage medium includes: a U disk, a mobile hard disk, a read-only memory (ROM), a random access memory (RAM), a magnetic disk, or an optical disk, and the like. .

The above is only a specific embodiment of the present invention, but the scope of the present invention is not limited thereto, and any person skilled in the art can easily think of changes or substitutions within the technical scope of the present invention. It should be covered by the scope of the present invention. Therefore, the scope of the invention should be determined by the scope of the appended claims.

Claims

A method for transmitting signaling in a wireless network, comprising:

The sending end sends the first Internet Protocol IP packet to the receiving end, where the first IP packet includes the first signaling, and the identifier field of the first IP packet is used by the receiving end to identify the sending end In order to facilitate the parsing of the first signaling by the receiving end, the identifier field of the first IP packet includes an IP header of the first IP packet and/or a transport layer protocol of the first IP packet. At least part of the field in the header;

Receiving, by the sending end, the second IP packet that is sent by the receiving end and responding to the first IP packet, where the second IP packet includes the second signaling;

The sending end identifies the receiving end according to the identifier field of the second IP packet, and parses the second signaling, where the identifier field of the second IP packet includes the second IP packet At least part of the IP header and/or the transport layer protocol header of the second IP message.
The method according to claim 1, wherein the value of some or all of the fields in the identification field is different from the value of some or all of the fields in the identification field specified by the RFC specification.
The method according to claim 1 or 2, wherein the value of some or all of the fields in the identification field is a reserved value of some or all of the fields in the identification field specified by the RFC specification.
The method according to any one of claims 1 to 3, wherein the transport layer protocol comprises a transport control protocol TCP and a user data packet protocol UDP.
The method according to any one of claims 1 to 4, wherein the value of the header checksum field in the IP header is a value calculated according to a preset rule, the preset rule and the RFC. The rules laid down in the specification are different.
The method according to any one of claims 1 to 5, wherein the value of the source port number and the destination port number field of the header of the transport layer protocol is a preset port number.
The method according to any one of claims 1 to 6, wherein the value of the checksum field included in the header of the transport layer protocol is a value calculated according to a preset rule, and the preset rule Different from the rules stipulated in the RFC specification.
The method according to any one of claims 1 to 7, wherein the time-to-live or hop limit field in the IP header has a value of zero.
The method according to any one of claims 1 to 8, wherein before the sending end sends the first internet protocol IP packet to the receiving end, the method further includes:

The sending end receives the configuration information sent by the OSS of the operation support system, where the configuration information is used to indicate that the sending end performs signaling interaction with the receiving end based on the identifier field.
A method for transmitting signaling in a wireless network, comprising:

Receiving, by the receiving end, the first Internet Protocol IP packet sent by the sending end, where the first IP packet includes the first signaling;

The receiving end identifies the sending end according to the identifier field of the first IP packet, and parses the first signaling, where the identifier field of the first IP packet includes the first IP packet At least part of the IP header and/or the transport layer protocol header of the first IP message;

The receiving end sends a second IP packet in response to the first IP packet to the sending end, where the second IP packet includes a second signaling, and an identifier field of the second IP packet is used. The sending end identifies the receiving end, so that the sending end parses the second signaling, and the identifier field of the second IP packet includes an IP header of the second IP packet and/or At least part of a field in a transport layer protocol header of the second IP packet.
The method according to claim 10, wherein the value of some or all of the fields in the identification field is different from the value of some or all of the fields in the identification field specified by the RFC specification.
The method according to claim 10 or 11, wherein the value of some or all of the fields in the identification field is a reserved value of some or all of the fields in the identification field specified by the RFC specification.
The method according to any one of claims 10 to 12, wherein the transport layer protocol comprises a transport control protocol TCP and a user data packet protocol UDP.
The method according to any one of claims 10 to 13, wherein the value of the header checksum field in the IP header is a value calculated according to a preset rule, the preset rule and the RFC. The rules laid down in the specification are different.
The method according to any one of claims 10 to 14, wherein the value of the source port number and the destination port number field of the header of the transport layer protocol is a preset port number.
The method according to any one of claims 10 to 15, wherein the value of the checksum field included in the header of the transport layer protocol is a value calculated according to a preset rule, and the preset rule Different from the rules stipulated in the RFC specification.
The method according to any one of claims 10 to 16, wherein the time-to-live or hop limit field in the IP header has a value of zero.
The method according to any one of claims 10 to 17, wherein before the receiving end identifies the transmitting end according to the identifier field of the first IP packet, the method further includes:

The receiving end receives the configuration information sent by the OSS of the operation support system, where the configuration information is used to indicate that the receiving end performs signaling interaction with the sending end based on the identifier field.
An apparatus for transmitting signaling in a wireless network, comprising:

a sending unit, configured to send a first Internet Protocol IP packet to the receiving end, where the first IP packet includes a first signaling, and an identifier field of the first IP packet is used by the receiving end to the device Identifying, so that the receiving end parses the first signaling, and the identifier field of the first IP packet includes an IP header of the first IP packet and/or a transmission of the first IP packet At least part of the fields in the layer protocol header;

a receiving unit, configured to receive a second IP packet that is sent by the receiving end and that is sent by the sending unit, where the second IP packet includes a second signaling;

a processing unit, configured to identify the receiving end according to the identifier field of the second IP packet received by the receiving unit, and parse the second signaling, where the identifier field of the second IP packet includes At least part of the IP header of the second IP packet and/or the transport layer protocol header of the second IP packet.
The apparatus according to claim 19, wherein the value of some or all of the fields in the identification field is different from the value of some or all of the fields in the identification field specified by the RFC specification.
The apparatus according to claim 19 or 20, wherein the value of some or all of the fields in the identification field is a reserved value of some or all of the fields in the identification field specified by the RFC specification.
The apparatus according to any one of claims 19 to 21, wherein the transport layer protocol comprises a transport control protocol TCP and a user data packet protocol UDP.
The device according to any one of claims 19 to 22, wherein the value of the header checksum field in the IP header is a value calculated according to a preset rule, the preset rule and the RFC. The rules laid down in the specification are different.
Apparatus according to any one of claims 19 to 23, wherein said transmission The value of the source port number and destination port number field in the layer protocol header is the default port number.
The device according to any one of claims 19 to 24, wherein the value of the checksum field included in the header of the transport layer protocol is a value calculated according to a preset rule, and the preset rule Different from the rules stipulated in the RFC specification.
The apparatus according to any one of claims 19 to 24, wherein the time-to-live or hop limit field in the IP header has a value of zero.
The device according to any one of claims 19 to 25, wherein the receiving unit is further configured to:

Receiving configuration information sent by the OSS of the operation support system, where the configuration information is used to instruct the device to perform signaling interaction with the receiving end based on the identifier field.
An apparatus for transmitting signaling in a wireless network, comprising:

a receiving unit, configured to receive a first Internet Protocol IP packet sent by the sending end, where the first IP packet includes a first signaling;

a processing unit, configured to identify the sending end according to the identifier field of the first IP packet received by the receiving unit, and parse the first signaling, where the identifier field of the first IP packet includes At least part of the IP header of the first IP packet and/or the transport layer protocol header of the first IP packet;

a sending unit, configured to send, to the sending end, a second IP packet that is in response to the first IP packet received by the receiving unit, where the second IP packet includes a second signaling, the second IP The identifier field of the packet is used by the sending end to identify the device, so that the sending end parses the second signaling, and the identifier field of the second IP packet includes the second IP packet At least part of the IP header and/or the transport layer protocol header of the second IP message.
The apparatus according to claim 28, wherein the value of some or all of the fields in the identification field is different from the value of some or all of the fields in the identification field specified by the RFC specification.
The apparatus according to claim 28 or 29, wherein the value of some or all of the fields in the identification field is a reserved value of some or all of the fields in the identification field specified by the RFC specification.
The apparatus according to any one of claims 28 to 30, wherein the transport layer protocol comprises a transport control protocol TCP and a user data packet protocol UDP.
Apparatus according to any one of claims 28 to 31, wherein said IP The value of the header checksum field in the header is a value calculated according to a preset rule, which is different from the rule specified by the RFC specification.
The device according to any one of claims 28 to 32, wherein the value of the source port number and the destination port number field of the transport layer protocol header is a preset port number.
The device according to any one of claims 28 to 33, wherein the value of the checksum field included in the header of the transport layer protocol is a value calculated according to a preset rule, and the preset rule Different from the rules stipulated in the RFC specification.
The apparatus according to any one of claims 28 to 34, wherein the time-to-live or hop limit field in the IP header has a value of zero.
The apparatus according to any one of claims 28 to 35, wherein the receiving unit is further configured to:

And receiving, by the operation support system, the configuration information sent by the OSS, where the configuration information is used to indicate that the device performs signaling interaction with the sending end according to the identifier field.