WO2012122710A1

WO2012122710A1 - Bearer network and data transmission method thereof

Info

Publication number: WO2012122710A1
Application number: PCT/CN2011/071871
Authority: WO
Inventors: 晏祥彪; 王标; 黄兵
Original assignee: 中兴通讯股份有限公司
Priority date: 2011-03-16
Filing date: 2011-03-16
Publication date: 2012-09-20

Abstract

The present invention discloses a bearer network including multiple bearer network planes and terminal devices, wherein said bearer network planes are Internet Protocol (IP) bearer networks. Said bearer network planes are set to implement routing and forwarding of data messages between the terminal devices. Each of said bearer network planes is configured with a unique number, and performs routing and addressing by using an independent routing address space. Said terminal device is set to use a User Identification (UID) as an addressing identifier, said UID including a low segment (UID_L) which uses an IP address space and a high segment (UID_H) which is used to increase the bit number of said UID for extending the address space. The present invention also discloses a data transmission method. The present invention can be compatible with the present data bearer network and Internet, thereby achieving smooth transition during the next generation network construction.

Description

Bearer network and data transmission method

TECHNICAL FIELD The present invention relates to the field of data communications and Internet technologies, and in particular, to a bearer network and a terminal communication method.

BACKGROUND OF THE INVENTION Research on the next generation information network architecture is one of the current hot research topics. The basic direction of the research topic is a telecommunication network represented by voice services, a television network represented by video services, and a data service. The purpose of the seamless integration of the Internet is to characterize the network carrying IP. Typical examples are: Voice over IP (VOIP) networks that provide voice services, and IP Television (IPTV) networks that provide TV services, and third-generation mobile communications (the 3rd generation, which are carried over IP core networks). 3G) network and a large number of research projects for super 3G or 4th generation (4G) networks. The goal of 4G is to provide an IP bearer-based network solution for voice, data and streaming services, enabling users to get a higher-speed communication environment "anytime, anywhere, any business". The Next Generation Network (NGN) is a next-generation network based on the telecommunications network, aiming to establish a unified IP-based packet-switched transport layer. The development of various applications at a unified transport level can be extended independently of the specific transmission technology, extending the application range of the application. Since the current IP packet bearer network is developed on the basis of IPv4, IP technology was first developed in the United States, so developed countries such as the United States have a large number of IPv4 addresses. Conversely, IP addresses allocated to a large number of developing countries are few. The development of IP packet bearer networks and various communication networks in developing countries is constrained by the lack of IP addresses. For example, the number of Internet users in China has exceeded the number of IPv4 addresses owned by China, and the number of Internet users in China is still increasing rapidly. Other technologies and equipment may not be used to increase the reuse of IP addresses. Therefore, the problem of insufficient IP address space seriously plagues the development of China's future IP bearer networks and communication networks. Solve this problem most The ideal method is to use IP V6. However, this kind of down-to-earth network architecture technology needs to rebuild IPv6 bearer network, and it will cost huge construction costs and need to replace hundreds of millions of terminals, which is costly. The plan is not suitable for the current situation. It can be seen that the research focus and direction selection of the next generation network architecture are very different due to differences in technology foundation and interest background, but the problems and difficulties are the same.

3G and 4G are the core of research on next-generation networks in the field of wireless communications. They aim to improve the quality of wireless mobile communications based on the all-IP packet core network. NGN and Next Generation Internet (NGI) are the telecommunications network and the Internet. Research on next-generation network convergence; China's Next Generation Internet (CNGI) aims to build a next-generation Internet based on IPv6; "Transportation of Integrated Trusted Network and Universal Service System" proposed by Northern Jiaotong University Can build a unified new packet network. Although there are great differences in various studies, the widely accepted viewpoints of various studies are: The future network is a unified bearer network for packets. Therefore, research on the next generation network architecture will use the Internet as the main reference. The Internet has been developing rapidly since its birth. It has become the most successful and most vital communication network. Its flexible and scalable, efficient packet switching, and powerful functions of the terminal are in line with the design needs of the new generation network. The Internet will be the main reference blueprint for next-generation network design. However, the structure of the Internet is far from optimal, and there are many major design issues. In addition to the above IP address space can not meet the application needs, but also mainly in the following aspects: Internet invention in the 1970s, it is difficult to predict that there will be a large number of mobile terminals and multiple township terminals in the world today, therefore, the Internet at the time The protocol stack is primarily designed for terminals that are connected in a "fixed" manner. In the current network environment, since the terminal basically does not move from one location to another location, the IP address with the dual attribute of identity and location can work very well, and the identity attribute and the location attribute of the IP address are not generated. Any conflicts. The IP address also represents the identity and location that exactly met the network needs of the time. From the perspective of the network environment at the time, this design scheme is simple and effective, simplifying the hierarchy of the protocol stack. But there is no doubt that there is an internal contradiction between the identity attribute of the IP address and the location attribute. The identity attribute of an IP address requires that any two IP addresses be equal. Although the IP address can be assigned according to the organization, there is no necessary relationship between consecutively encoded IP addresses, or at least in the topological position. Relationship; the location attribute of an IP address requires that the IP address be based on the network topology (not the organization) For the row assignment, the IP addresses in the same subnet should be in a contiguous IP address block, so that the IP address prefixes in the network topology can be aggregated, thereby reducing the routing table entries of the router device and ensuring the routing system. Scalability. Along with the development of network scale and technology, some technologies for dynamically assigning IP addresses gradually emerged, such as the Dynamic Host Configuration Protocol (DHCP), which begins to break the IP address to uniquely represent a terminal assumption. The use of private IP address space and the birth of Network Address Translator (NAT) technology have continued to deteriorate. In this case, an IP address with both an identity attribute and a location attribute will be difficult to continue to perform its role. The dual attribute problem of IP addresses has been highlighted. In addition to the significant changes in technical requirements, the user status of the Internet has also undergone tremendous changes. In the early years after the birth of the Internet, the Internet was basically used by people who were in a common group and trusted by each other. The traditional Internet protocol stack was also designed based on this assumption; while the current Internet users are mixed, people can hardly continue trusting each other. In this case, the Internet, which lacks embedded security mechanisms, needs to change. In general, the inherent contradiction between the dual attributes of IP addresses will lead to the following main problems:

1. Routing Scalable Issues There is a basic assumption about the scalability of Internet routing systems:

"The address is assigned according to the topology, or the topology is deployed according to the address, and the two must choose one."

The identity attribute of an IP address requires that the IP address be assigned based on the organization to which the terminal belongs (rather than the network topology), and this allocation must be stable and cannot be changed frequently; the location attribute of the IP address requires the IP address to be based on the network. The topology is allocated to ensure the scalability of the routing system. In this way, the two attributes of the IP address create conflicts, which eventually leads to the scalability problem of the Internet routing system.

2. Mobility problem, the identity attribute of the IP address requires that the IP address should not change with the change of the terminal location, so as to ensure that the communication bound to the identity is not interrupted, and it can also ensure that after the terminal moves, other terminals still The identity of the IP address can be used to establish communication with it; the location attribute of the IP address requires the IP address to change as the location of the terminal changes, so that the IP address can be aggregated in the new network topology, otherwise the network must be mobile The terminal retains a separate routing letter Interest, resulting in a sharp increase in routing table entries.

3, a number of township problems, a number of townships usually refers to the terminal or network through the network of multiple Internet Service Providers (ISPs) to access the Internet. The advantages of multiple township technologies include increasing network reliability, supporting traffic load balancing across multiple ISPs, and increasing overall available bandwidth. However, the inherent contradiction between the dual attributes of IP addresses makes it difficult to implement multiple township technologies. The identity attribute of an IP address requires that a plurality of home terminals always display the same identity to other terminals, regardless of whether the multiple township terminals access the Internet through several ISPs; and the location attribute of the IP address requires that multiple township terminals are different. The ISP network uses different IP addresses to communicate, so that the IP address of the terminal can be aggregated in the topology of the ISP network. 4. Security and location privacy issues. Since the IP address contains both the identity information and the location information of the terminal, both the communication peer and the malicious eavesdropper can simultaneously obtain the identity information and topology location information of the terminal according to the IP address of one terminal. In general, since the establishment of the traditional Internet architecture, the technical environment and user groups of the Internet have undergone earth-shaking changes, and the Internet needs to be innovated. The dual attribute problem of IP address is one of the fundamental reasons that plague the Internet to continue to develop. Separating the identity attribute and location attribute of an IP address is a good way to solve the problems faced by the Internet. In order to solve the problem of identity and location, the industry has carried out a lot of research and exploration. The basic idea of all identity and location separation schemes is to separate the identity and location dual attributes originally bound to the IP address. Among them, some schemes use the application layer's Uniform Resource Locator (URL, which is an identification method for completely describing the address of web pages and other resources on the Internet) or a qualified domain name (Fuy Qualified Domain Name, FQDN). As the identity of the terminal, such as IPNL (IP Next Layer), TRIAD (A Scalable Deployable NAT-based Internet Architecture), etc.; some solutions introduce a new namespace as an identity, such as Host Identity Protocol (HIP) Adding a host identifier to the network layer with the IP address as the identifier; some schemes classify the IP address, some IPs are used as identity identifiers, and some IPs are used as location identifiers, such as Locator/ID Separation Protocol (LISP) ) Wait. The Chinese patent application CN200610001825 proposes a solution to use the IP address as the location identifier of the host and introduce the end host identifier as the identity identifier to solve the problem of identity and location separation. In the above solution, the host-based solution needs to modify the host protocol stack, and the network-based solution needs to improve the router at a specific location. Moreover, as a network-based solution, routers that perform identity and location mapping functions are located in different locations on the network. Some schemes clearly define that the router that performs the mapping function is located at the boundary of the user network, that is, the mapping function router belongs to the user network; some (LISP, TIDR, and Ivip) do not limit the location of the router in which the mapping function is completed in the network; The routing information that solves the problem of routing scalability and the identity and location is only known to the network administrator. The router that completes the mapping function is strictly defined as the core network access router, that is, the mapping function router belongs to the core network. In the solution where the identity and location identifiers are located at the same time in the network layer, such as LISP, there is a design difference between whether the identity and the location are completely separated according to the network topology. The current version of LISP requires that the network must use the Endpoint Identifier (EID) to route the first packet to the peer before the mapping resolution service is provided, so that the tunnel routers of the two communicating parties can learn the routing location identifier (Routing Locators). , RLOC) and terminal identification EID mapping information, which makes the network at least some routing nodes retain routing entries based on routing location identifier RLOC and terminal identifier EID, thus affecting LISP's ability to solve routing scalability problems. The original intentions of various identity and location separation schemes are not the same, so the functions that are finally implemented are also different. IPNL is designed to give IPv4 networks a longer life and avoid the challenge of replacing the IPv4 protocol with the replacement of the IPv4 protocol. TRIAD is designed to address the various issues that NAT brings to the Internet, while providing some support for mobility and policy routing. HIP was originally proposed to solve security problems, and then did a lot of work on mobility support, and conducted a number of township-supported research. SHIM6 (Level 3 Shim for IPv6) is mainly proposed to solve the problem that IPv6 networks can support multiple township problems. LIN6 (Location Independent Networking for IPv6) is designed to provide an alternative mobility and multiple township solution for the IPv6 protocol. ILNP is designed to provide an IPv6 extension mechanism that addresses mobility and multiple home issues. GSE attempts to change the structure of IPv6 addresses, thereby controlling the growth of global routing table entries and more flexible support for multiple home technologies. TIDR is designed to enhance the routing and forwarding capabilities of the existing Internet, and to address global routing table bloat, inter-domain routing security, and multiple township issues. LISP is primarily designed for routing scalability issues. In summary, the main problems in the prior art are: insufficient IP address space and imperfect IP address identity and location solutions.

SUMMARY OF THE INVENTION The technical problem to be solved by the present invention is to provide a bearer network and a data transmission method, which solves the problem of insufficient IP address resources in an existing network. In order to solve the above technical problem, a bearer network of the present invention includes: a plurality of bearer network planes and terminal devices, where the bearer network plane is an Internet Protocol (IP) bearer network, and the bearer network plane is set to The routing and forwarding of data packets between the terminal devices are implemented. Each bearer network plane of the multiple bearer network planes is configured with a unique number, and the routing address is used for routing and addressing. The setting is: using an identity (UID) as an addressing identifier, the UID includes a low segment (UID_L) and a high segment (UID_H), the low segment uses an IP address space, and the high segment uses To increase the number of bits of the UID, expand the address space. The network further includes: an access switching router (ASR), wherein the ASR is respectively connected to the multiple bearer network planes, and the ASR is configured to: obtain a corresponding route identifier (RID) and a bearer network according to the UID of the terminal device. The number of the plane. The network further includes: an access network, the access network is located between the terminal device and the ASR, and the access network is configured to: access the terminal device of the network to the ASR. The UID is a unique identifier of the terminal device, and is used between the terminal device and the ASR, and remains unchanged when the terminal device moves; the RID is a location identifier of the terminal device, and is used at the core layer. The lower part of the UID is carried by the IP address part of the IP packet header; the high part of the UID is transmitted by using the version bit of the IP packet. The lower part of the UID uses a 32-bit address of the IPv4 address space. Wherein, the UID uses a mobile phone number. When the mobile phone number is used as the UID, the mobile phone number is converted into a hexadecimal number, and the upper four bits are used as UID-H, and the lower three bits are used as UID-L. After converting the mobile phone number into a hexadecimal number, if the value of the upper four bits is greater than the number of the bearer network plane, the high four bits are compressed and converted to meet the number of the bearer network plane. When the mobile phone number is used as the UID, the last ten digits of the mobile phone number are converted into a hexadecimal number as UID-L. Wherein, when using the mobile phone number as the UID, the first two digits of the mobile phone number are converted into a single digit, and the converted one digit and the last nine digits of the mobile phone number are converted into hexadecimal digits. , as UID-L. The ASR is further configured to: perform mapping information of terminal device registration, access control, security authentication, maintenance UID, RID, and number of bearer network planes, and message rewriting and forwarding. The data packet between the ASR and the bearer network plane adopts an IP packet format, and the RID is used to implement route addressing in the bearer network plane. The RID uses an IP address. The bearer network plane adopts an IPv4 data bearer network, is planned and constructed according to an IP network protocol and principle, and is composed of an IPv4 routing protocol and a router device interconnection. The network further includes: a mapping server, the mapping server is connected to the bearer network plane, and the mapping server is configured to: be responsible for registering, saving, and updating mapping information of the UID, the RID, and the number of the bearer network plane; the ASR is also set to : According to the UID of the terminal device, obtain the corresponding RID and bearer network plane number from the mapping server or from the ASR query. The mapping server uses the RID as the identifier, and the terminal device is deployed in the bearer network plane; or uses the UID as the identifier to access the bearer network plane through the ASR. The mapping server is further configured to: after updating the mapping information of the UID, the RID, and the number of the bearer network plane, send the update message to update the UID, the RID, and the bearer network plane. The numbered mapping information is sent to the ASR. The high segment of the UID is the number of the bearer network plane to which the corresponding terminal device belongs. The terminal device that is addressed by the RID is connected to the bearer network plane 0 in the multiple bearer network planes. In order to solve the above technical problem, the present invention further provides a data transmission method, which is applied to the foregoing bearer network, the method comprising: receiving, by a first access switching router (ASR), a first terminal device to send to a second terminal device a message, where the first message uses the identity identifier (UID) of the first terminal device and the second terminal device as the source address and the destination address of the first text respectively; after receiving the first packet, the first ASR is configured according to The UIDs of the first terminal device and the second terminal device respectively query the routing identifier (RID) of the first terminal device and the second terminal device, and the number of the bearer network plane, and modify the source address and the destination address of the first packet to The RID of the first terminal device and the RID of the second terminal device generate a second packet; and the first ASR sends the second packet to the first packet according to the number of the bearer network plane to which the second terminal device belongs. Two ASR. The method further includes: after the second packet received by the second ASR, querying, according to the RID of the first terminal device and the second terminal device, and the number of the bearer network plane, the first terminal device and the second device are obtained. The UID of the terminal device restores the second packet to the first packet, and sends the first packet to the second terminal device. The first packet uses the version information part of the IPV4 packet to carry the high-order UID (UID H ) of the first terminal device and the second terminal device, and uses the source address information part of the IPV4 packet to carry the first terminal device. The UID (UID L ) and the destination address information part of the IPV4 message carry the second terminal device low-end UID (UID L ). When the first ASR generates the second packet, the UID-H of the first packet is restored to the version of the packet. This information. The first ASR is configured to query, according to the UIDs of the first terminal device and the second terminal device, the RIDs of the first terminal device and the second terminal device, and the number of the bearer network plane, where the first ASR is from the mapping server or The mapping information of the RID, the UID, and the number of the bearer network plane is obtained by the ASR, and the RID of the first terminal device and the second terminal device and the number of the bearer network plane are obtained. In order to solve the above technical problem, the present invention further provides a data transmission method, which is applied to the foregoing bearer network, the method comprising: receiving, by a first access switching router (ASR), a first terminal device to send to a third terminal device The third packet, the third packet uses the user identifier (UID) of the first terminal device as the source address of the third packet, and uses the routing identifier (RID) of the third terminal device as the destination address of the third packet. The number of the bearer network plane of the third terminal device is 0, and the third packet carries the number 0 of the bearer network plane of the third terminal device. After receiving the third packet, the first ASR is configured according to the first terminal device. The UID query obtains the RID of the first terminal device and the number of the bearer network plane, and modifies the source address of the third packet to the RID of the first terminal device to generate a fourth packet; and the first ASR according to the third terminal device belongs to The number of the network plane is carried, and the fourth packet is sent to the third ASR by the bearer network plane 0. The method further includes: after the fourth packet received by the third ASR, querying, according to the RID of the first terminal device and the number of the bearer network plane, the UID of the first terminal device, and the fourth packet The third packet is restored to the third terminal, and the third packet is sent to the third terminal device. among them,

The first terminal device uses the version information part of the IPV4 packet to carry the high-order UID (UID H ) of the first terminal device, and uses the source address information part of the IPV4 packet to carry the low-order UID (UID L ) of the first terminal device. . among them, When the first ASR generates the fourth packet, the UID-H of the third packet is restored to the version information of the packet. The first ASR obtains the RID of the first terminal device and the number of the bearer network plane according to the UID of the first terminal device, where the first ASR queries the RID, the UID, and the bearer network plane from the mapping server or locally. The numbered mapping information obtains the RID of the third terminal device and the number of the bearer network plane.

In summary, the present invention provides a multi-plane bearer network architecture, which can be compatible with existing data bearer networks and the Internet, and realizes smooth transition and distributed implementation in next-generation network construction, and in particular, can satisfy the next-generation mobile communication network ( 4G) network construction needs to solve the problem of insufficient IP address through the multi-plane bearer network architecture and the identity of the terminal device with more than 32 bits. At the same time, the multi-plane structure also realizes the separation of terminal identity and location. The solution is to effectively solve the above two problems. The invention can effectively solve the problems of security, mobility, multi-hole, route extension and network aggregation. The network capacity of the multi-plane bearer network architecture of the present invention is increased by the capacity of multiple bearer network planes, that is, equal to the number of bearer network planes multiplied by the capacity of a single bearer network plane, or the network of the entire architecture is extended by the number of bearer network planes. Capacity, thereby breaking the capacity of the traditional network (equivalent to the capacity of a bearer network plane of the present invention), and solving the scale bottleneck of the existing network. The multi-plane bearer network architecture of the present invention utilizes the identity of the terminal device to implement mapping processing between the switch and the route identifier, and solves the problems associated with the identity and location in the traditional network. The packet format used by the multi-plane bearer network architecture of the present invention is completely compatible with the traditional IP packet format, and can smoothly upgrade the existing network, build on demand, and effectively control the pace of investment and construction, thereby ensuring network operation. Healthy and stable development.

BRIEF DESCRIPTION OF THE DRAWINGS FIG. 1 is a structural diagram of a bearer network of the present invention; 2 is a flow chart of mutual access between terminal devices of the present invention; and FIG. 3 is a flow chart of accessing a legacy terminal by a terminal device according to the present invention.

Preferred embodiment of the invention

Embodiments of the present invention will be described in detail below with reference to the accompanying drawings. It should be noted that, in the case of no conflict, the features in the embodiments and the embodiments in the present application may be arbitrarily combined with each other. As shown in FIG. 1, the bearer network architecture of the embodiment of the present invention includes: a terminal device, an access switch router, a mapping server, and multiple bearer network planes, where: the terminal device uses an identity (UID) as a registration and communication. The addressing identifier is a unique identifier of the identity of the terminal device. It is used at the access layer. This is a fixed allocation. It remains unchanged when the device moves. The UID of the terminal device is expressed in binary, and the length is greater than 32 bits, that is, the identity. The UID space is greater than 2 to the 32th power; the packets sent and received by the terminal device are compatible with the traditional IP packet format. Specifically, the identity identifier UID of the terminal device is divided into two parts, the low segment UID-L and the high segment UID-H, and the lower 32 bits (binary) are low segments, and the packet format of the terminal device is compatible with the traditional IP packet. In the text format, the lower 32-bit segment uses the IP address part of the IP packet header to carry the transmission; the high segment uses other parts of the IP packet header that are not actually applied or fixed to carry the transmission. The low-end representation is compatible with the 32-bit address of the IPV4 address space, thus ensuring compatibility between the terminal device application software and the protocol software. The part higher than 32 bits (binary) is the high part, and the high part part is used to expand the address space, which can be flexibly set according to the construction needs. For example, one or two bits are set, and the same can be used to ensure the compatibility of the terminal software. The version bit in the IPV4 message carries the transmission. Setting the 1-2 bit high segment in the UID can expand the IPV4 address space by 2-4 times, which means that 2-4 IPV4 data bearer networks can be added. The terminal device is compatible with the upper layer applications such as the IP routing protocol and the application protocol interface, ensuring minor changes to the terminal, and replacing the traditional 32-bit IPV4 address with the 32-bit low segment in the identity identifier, thereby ensuring the format of the IP packet. Traditional message compatibility. For the high-end part of the terminal identity, the user can set it according to the network condition or automatically configure it by the network communication protocol. The identity of the terminal device is only used for identity identification and communication between the terminal and the terminal, in the bearer network of the present invention. In the network architecture, the identity of the terminal device is used between the terminal device and the access switching device, including: registration of the terminal device, and sending and receiving of data packets. The identity can also be referred to as an Access Identity (AID). The access switch router (ASR) connects to the terminal device through the access network, and is responsible for the registration, access control, and security authentication of the terminal device, and obtains the corresponding route identifier (RID) and 7-bit according to the UID query of the terminal device. The number of the network plane, the maintenance UID, the RID, and the mapping information of the number that carries the network plane, as well as packet rewriting and forwarding. The Routing Identity (RID) is the location identifier of the terminal device and the mapping used at the core layer. The access switch router and the multiple bearer network planes are connected. The data packets between the access switch router and the bearer network plane use the traditional IP packet format and related protocols, and the route identifier RID is used in the connected bearer network plane. Route addressing is implemented; the routing ID RID uses traditional IP addresses and is planned and deployed in accordance with the protocols and rules of traditional IP networks. The access switching router can maintain the correspondence between the identity identifier and the route identifier locally, and can also update the corresponding relationship. The access switching router can also complete the registration of the terminal device and the query and update of the terminal device routing identifier by communicating with the mapping server. The access switching router also forwards data packets to and from the bearer network plane. The basic packet processing procedure of the access switch router is: when receiving the packet of the terminal, searching according to the identity identifier of the terminal device of the present invention in the packet header. The 32-bit route identifier RID and the bearer network plane number are mapped and sent to the bearer network; or the bearer network data packet is received, and the demapping function is completed and sent back to the terminal device. The mapping server can actively send an update message to inform the access switch router of the new identity, the route identifier, and the mapping information of the number of the bearer network plane. When the access switch router maps the user identity and the route identifier, it performs operations such as query and update.

The traditional terminal device uses IPV4 address addressing, and can directly access the bearer network plane 0 without special processing in the mapping server. The users in the bearer network plane can directly communicate with each other across the bearer network plane. Communication cannot be performed directly, and communication can be indirectly through a proxy device or an address translation device. Multiple bearer network planes are used to implement routing and forwarding of data packets between terminal devices. The bearer network plane has the number of the network plane. Different bearer network planes have different numbers. Different numbered bearer network planes connect to different ports of the access switch router. Each bearer network plane uses an independent 32-bit routing address space. The routing addressing is the same as the traditional IPv4 data bearer network. It is planned and constructed according to the traditional IP network protocols and principles, and is composed of traditional IPv4 routing protocols and router device interconnection. The bearer network plane uses the route identifier RID to search for routes in the network plane. The RID uses a 32-bit binary address. The bearer network plane can be connected to the access switch router, or can be connected to a traditional terminal device that uses IP address addressing. The packet format uses the existing IP packet format to ensure compatibility between the bearer network plane and the existing core network.

The 32-bit address space of the bearer network plane is used to meet the address topology allocation principle of the traditional bearer network, and cannot overlap. In addition to the traditional terminal device, the present invention uses a part of the address as the routing address of the ASR connection port of the access switch router. The ASR is mapped to the terminal of the present invention for routing, so the terminal of the present invention can communicate with the legacy terminal device. For example, the terminal of the present invention can access various servers in a traditional network, and enjoy and use the services of the existing legacy network. Since the conventional terminal device cannot recognize the high segment UID-H in the identity of the terminal of the present invention, it cannot communicate directly. As an implementation manner, the number of the network plane and the address space formed by the RID may be associated with the identity of the terminal of the present invention, that is, the mapping information of the user identity and the route identifier of the terminal of the present invention may be The number of the bearer network plane is related. For example, the traditional terminal uniformly accesses the bearer network plane 0 and becomes the user with the high segment equal to 0. Different algorithms or rules can be used to complete the conversion between the identity identifier and the route identifier and the bearer network plane number according to the network construction requirements. It is also possible to use a relatively simple process. For example, the terminal high segment UID — H=0 indicates the terminal. The device corresponds to the transition to the bearer network plane 0; the high segment UID of the terminal - H = l indicates that the terminal device corresponds to the transition to the bearer network plane 1; the high segment of the terminal UID - H = 2 indicates that the terminal device corresponds to the switch Entering the bearer network plane 2; the high segment UID of the terminal - H=3 indicates that the terminal device correspondingly switches to the bearer network plane 3. The mapping server is used to register, store, and update the mapping information of the user identity UID and the route identifier RID and the bearer network plane number, so that the access switch router performs the operations of querying and updating when mapping the user identity and the route identifier. The mapping server can use RID As an identifier, the IP address is deployed in the bearer network plane as a traditional terminal device. It can also be identified by using the user identity UID and accessed through the access switch router. The mapping processing of the user identity identifier UID and the route identifier RID by the access switching router includes: querying the mapping server or the local, and maintaining the mapping information of the identity identifier UID, the route identifier RID, and the bearer network plane number, and receiving the packet of the terminal device. After the mapping between the user identifier UID and the route identifier RID is completed, the packet is sent to the bearer network plane corresponding to the bearer network plane number; the packet sent by the bearer network plane is received, and the route identifier RID and the user identity are completed according to the number of the bearer network plane. After the reverse mapping process of the UID, the packet is sent to the terminal device. The terminal of the traditional IPV4 network uses the IP address as the identity and route identifier, and connects to the bearer network plane numbered 0. After the device moves, the IP address changes, as shown in Figure 1120. The implementation of the technical solution will be further described in detail below with reference to the accompanying drawings.

The invention adopts a multi-plane bearer network architecture, each bearer network plane is compatible with an existing bearer network, and has all IP address spaces (32-bit address space, about 4 billion address space), and each bearer network plane has different numbers. In this way, the different bearer network planes can be distinguished, and the IP address space in the plane can be the same. When the multi-plane bearer network architecture has only one bearer network plane, which is equivalent to the existing bearer network, the multi-plane bearer network architecture of the present invention is It is composed of multiple bearer network planes, including two or more planes. Usually, the plane numbered 0 is the existing bearer network plane, and then other bearer network planes are added, so that it can be compatible with the existing bearer network, and It can be smoothly upgraded to the multi-bearer network plane of the present invention. For example, a network architecture with two bearer network planes can double the address space of the existing bearer network, and can have more than 8 billion address spaces. If four bearer network planes are constructed, as shown in Figure 1, 300 is The network planes 0, 310 are the network planes 1 and 320 are the network planes 2, 330 are the network planes 3, and the four network planes can generate a total of 16 billion address spaces, which can not only solve the next generation mobile The current IP address of the communication network is insufficient, and it can meet the development needs of mobile operators. It is equivalent to providing more than 10 digits of telephone number allocation space. For example, the current effective space of China Mobile's telephone number is less than 10 digits (for example, 13X). Xxxx xxxx ) , using the four bearer network planes of the present invention to provide sufficient address space, each mobile user can be assigned a unique address space for data communication without address reuse. If the multi-plane bearer network of the present invention is implemented, the user can use the currently used mobile phone number (13X XXXX XXXX) as the identity UID for any service access, surfing the Internet, VoIP, network video, and file downloading, etc. You can use such a unique number directly, without having to dynamically assign an IP address as you would now using an address translation device. The access switch router and each bearer network plane have a connection interface. The address space of the bearer network plane used by the interface can be determined according to the plan. For example, in Figure 1, ASR1 and four bearer network planes are connected through four interfaces. ASR2 is also connected to four bearer network planes. The route identifier address space used is the same as the traditional IP address space. The planning principle is the same. The example of the planned address space is as follows:

The processing procedure of the terminal communication of the multi-plane bearer network in the embodiment of the present invention is as follows: The terminal device of the present invention uses the identity identifier to communicate, and the terminal devices can communicate with each other; the terminal device of the present invention can pass the IP address of the traditional terminal and its The number of the bearer network plane that is accessed is used to form an identity of the terminal of the present invention for the legacy terminal, thereby identifying the legacy terminal for communication, and conversely, since the legacy terminal cannot completely identify the identity of the terminal device of the present invention, Therefore, it is not possible to directly communicate with the terminal device of the present invention. A traditional terminal device directly accesses the bearer network plane and can only communicate with users in the bearer network plane. The terminal of the present invention needs to access the bearer network plane by accessing the switching router ASR. In the present invention, the terminal that needs to access the bearer network plane can be selected according to the network plan, and can be automatically selected or manually selected, and the access switch router completes the mapping process of the bearer network plane number and the route identifier RID of the terminal.

The working process of the access switching router ASR in the embodiment of the present invention is as follows: The ASR completes the mapping processing of the terminal device identity to the bearer network plane and the number of the routing identifier RID and the bearer network plane, and may use packet encapsulation or identification. In other words, the RID address on the bearer network plane can be aggregated to implement route scalability.

The ASR completes the registration of the terminal device of the present invention in the mapping server, and registers the identity of the network user of the present invention and the number of the bearer network plane where the RID and the RID are located. During the movement of the terminal device, the identity identifier is unchanged, and the route identifier has changed, so it is necessary to re-register with the mapping server, the mapping server sends an update message to the access switching router, and the access switching router re-updates the local identity and routing identifier and The relationship between the bearer plane number and the number of the bearer network plane where the RID and RID of the network user are maintained.

The ASR is responsible for querying the mapping server according to the identity of the communication peer to the routing server. The RID and the number of the bearer network plane where the RID is located.

The ASR is responsible for transmitting the packet that completes the mapping to the bearer network plane of the corresponding number, and is responsible for receiving the packet sent from the bearer network plane, and performing reverse mapping to be sent to the terminal device of the present invention.

The ASR is also responsible for completing the access control and security authentication functions of the terminal device of the present invention.

The workflow of the bearer network plane in the embodiment of the present invention: The bearer network plane is planned and deployed according to a traditional IP network, using existing router equipment and associated routing protocols. The routing ID is performed by using the routing identifier RID of the present invention, and may also be referred to as an IP address in the bearer network plane. The port connecting the router device that carries the network plane and the access switching router of the present invention uses the IP address as the identity identifier and the location identifier. It is completely the same as the existing bearer network, so it can also access traditional terminal devices that are addressed using IP addresses.

The workflow of the mapping server in the embodiment of the present invention: the mapping server is configured to register, save, and update the correspondence between the identity identifier and the routing identifier of the terminal, and communicate with the access switching router, and may query the corresponding relationship, or update the corresponding relationship. . The mapping server can actively send an update message to inform the access switch router of the correspondence between the new identity and the route identifier.

The method of the present invention is described below by taking the first terminal device 100 of the present invention as an example of the second terminal device 110 of the present invention. It is assumed that the identity of the first terminal device is UID1 and the identity of the second terminal device is UID2. The switching router addresses using the identity of the user of the present invention and completes the mapping of the identity and routing identifiers. As shown in Figure 2, the communication process between terminal devices includes:

201: The first terminal device sends the first packet that accesses the second terminal device; the packet format is compatible with the packet format of the IPV4, and UID1—H and UID1—L are used as the source address, where the UID1—H uses the IPV4 packet. The version information part is carried, UID1—L is carried by the IP source address information part of the IPV4 message; UID2 H and UID2—L are used as the addressed destination address, where UID2 H is carried by the version information part of the IPV4 message, UID2—L The IP destination address information part of the IPV4 packet is carried. There are two differences between the >3⁄4 text of the embodiment of the present invention and the traditional IPV4^艮文, first, the traditional

The version information of the IPV4 packet is used to carry the high segment of the UID of the embodiment of the present invention. Second, the IP address portion of the conventional IPV4 packet is used to carry the low segment of the UID of the embodiment of the present invention, and other portions are not. It is changed to maintain compatibility with the IPV4 message format, and the terminal routing protocol and application software are also compatible. The application software of the terminal device does not need to be changed.

202: After receiving the first packet sent by the first terminal device, the first access switching router queries the corresponding routing identifier and the number of the bearer network plane according to the identity identifiers of the first and second terminal devices locally or to the mapping server. UID1 corresponds to RID1, UID2 corresponds to RID2, and a corresponding table of identity or route identifier is created or maintained;

203: The first access switching router rewrites the first packet, restores the version information of the packet to the version information of the traditional IPV4 packet, and uses the route identifier to replace the lower part of the identity identifier, that is, uses RID1 as the IP source address. And RID2 is used as the IP destination address to generate the second packet; 204: the first access switching router sends the second packet to the bearer network plane according to the number of the bearer network plane; for example, the second terminal device of the present invention belongs to The bearer network plane 3 sends the second packet to the network plane 3.

205: After receiving the second packet, the bearer network plane forwards according to the route identifier. For example, if the route identifier of the packet points to the interface of the second access switch router that carries the network plane 3, the bearer network plane passes the interface. Forward the message to the second access switching router.

206: The second access switching router restores the second packet to the first packet after receiving the second packet; and the second access switching router performs the process of rewriting the packet opposite to the first access switching router. The process includes: searching for the identity of the terminal in the local or mapping server according to the route identifier and the receiving port in the packet (the number of the bearer network plane is 3), and using UID1—H and UID1—L as the source of the packet. Address, where UID1—H is carried by the version information of the IPV4 message, UID1—L is carried by the IP source address part of the IPV4 message; UID2—H and UID2—L are used as the destination address for addressing, where UID2—H uses IP The version information of the V4 message is carried, and the UID2—L uses the IP destination address part of the IPV4.

207: The second access switching router sends the first packet to the second terminal device, and the second terminal device receives the packet according to the identity identifier, and provides the packet to the upper layer software interface, thereby completing the communication process. The process in which the terminal UID2 of the present invention accesses the terminal UID1 of the present invention is similar to the above process.

The following describes the method for accessing a conventional terminal device by the terminal device of the present invention. As shown in FIG. 3, the identity of the first terminal device of the present invention is UID1, and the third terminal device is a legacy terminal device, and its IP address is RID3. The RID3 and the routing identifier of the present invention are uniformly planned, which is equivalent to the routing identifier of the present invention. The traditional terminal device directly accesses the home bearer network plane 0 because its identity and location identifier are not separated. The traditional terminal is located on the bearer network plane 0. Therefore, when the terminal of the present invention initiates the access, the IP address of the legacy terminal is equated with the lower part of the identity identifier of the present invention, and the high segment of the identity identifier RID3 of the legacy terminal is equal to 0, which is equivalent. An identity terminal UID3 of the present invention is assigned to a legacy terminal, thereby unifying the processing flow to the terminal of the present invention to access the terminal of the present invention. In this embodiment, the terminal of the present invention accesses the process of the legacy terminal that carries the network plane 0:

301: The first terminal device sends a third packet that accesses the third terminal device; the packet format is compatible with the packet format of the IPV4, and UID1—H and UID1—L are used as source addresses, where UID1—H uses IPV4 packets. The version information part is carried, UID1—L is carried by the IP source address information part of the IPV4 message; UID3_H (for 0) and UID3 L (for RID3) are used as the destination address for addressing, where UID3—H uses the version of the IPV4 message The information bearer, UID3—L is carried by the IP destination address information part of the IPV4 packet. There are two differences between the >3⁄4 text of the embodiment of the present invention and the traditional IPV4^艮文, first, the traditional

The version information of the IPV4 packet is used to carry the high segment of the UID in the embodiment of the present invention. Second, the IP address portion of the conventional IPV4 packet is used to carry the low segment of the UID in the embodiment of the present invention, and the other portions are unchanged. It is compatible with the IPV4 packet format and ensures compatibility between the terminal routing protocol and the application software. The application software of the terminal device does not need to be changed. 302: After receiving the third packet, the first access switching router ASR1 queries the corresponding routing identifier and the number of the bearer network plane according to the identity identifier of the first terminal device locally or to the mapping server, and newly creates or Maintain the correspondence table between identity and route identifier, UID1 Corresponding to RID1 and UID3, since the high segment of the identity identifier is 0, the mapping information of RID3 is directly established without mapping processing;

303: The first access switching router rewrites the packet, and restores the version information of the packet to the version information of the traditional IPV4 packet. The routing identifier is used instead of the lower segment of the identifier, that is, the RID1 is used as the IP source address. The RID3 is used as the IP destination address to generate the fourth packet. In this embodiment, the legacy terminal belongs to the bearer network plane 0. Therefore, the packet is sent to the bearer network plane 0.

304: The first access switching router sends the fourth packet to the bearer network plane according to the number of the bearer network plane. 305: After receiving the packet, the bearer network plane 0 forwards the packet according to the route identifier. Three terminal devices.

306: After receiving the fourth packet, the second access switching router restores the fourth packet to the third packet.

307: The second access switching router sends the third packet to the third terminal device, and the third terminal device receives the packet according to the identity identifier, and provides the packet to the upper layer software interface, thereby completing the communication process.

The following describes an example of the identity identification of the terminal device of the present invention. For example, the mobile phone number of the mobile communication network is used as the terminal device identity identifier of the present invention, as follows: Currently, the number used by the mobile communication mobile phone of China is 11 digits. The first two are 13, 15, and 18, and the last nine are not fully used. They use less than 1 billion of the number space. Even if there are two numbers in China in the future, there will be only 2 billion addresses. Even if there is a number for each person in the world, according to relevant predictions, the population of the world will not exceed 8 billion in the next 20 years. Therefore, the multi-plane bearer network architecture of the present invention can satisfy the number using two bearer network planes. Need, if the development exceeds expectations, the world's population is exploding, the use of four bearer planes can also meet the demand for numbers. In this example, if you build a network architecture with two bearer network planes, users directly use mobile phone numbers to communicate. On the terminal device, you need to convert the decimal mobile phone number to binary or Hexadecimal, thus compatible with the format of traditional IP addresses. Take a global user of China Mobile as an example, the mobile number is 139, 9999, 9999. Converted to hexadecimal is 3 42 77 OB FF, the identity of the GSM user in the present invention is 3 42 77 0B FF (hexadecimal), the high section of this identity is 3, the last 32 bits are low The segment, the high segment equals 3 to the number of the above two planes, and requires more precise compression conversion (the existing data compression method can be used). At present, the first digit of the mobile phone number is fixed, so we can narrow the address space and use the last 10 digits of the mobile phone number to uniquely identify the GSM user. We take 10 digits to convert, ie 39, 9999. 9999 (decimal) is converted to obtain the hexadecimal number EE 6B 27 FF as the identity of the GSM user in the multi-plane bearer network of the present invention, thereby being compatible with the format requirements of the terminal, and planning and determining at the initial stage of network construction, and For users

Of course, other conversion methods can also be used, for example, first converting the first 2 digits of the mobile phone number, then forming the 10-digit number with the last 9 digits, and then performing hexadecimal conversion. For example, the mobile phone number segment 13 is converted to 0, the mobile phone number segment 15 is converted to 1, the mobile phone number segment 18 is converted to 2, and the currently used mobile phone number is unified to a space smaller than 30, 0000, 0000, which can be converted to the terminal device identity of the present invention. In the 32-bit low-order (binary) of the identifier, the bearer network plane 1 is uniformly used, and the bearer network plane 0 is used by the conventional terminal device, so that the new user new identifier of the present invention can be implemented, and the legacy terminal uses the old IP address to implement The smooth evolution of network construction, gradual upgrading, and step-by-step construction can save costs and solve the bottleneck of future network development. Of course, in the process of gradual reduction of the network, the first step only uses the present invention to expand the address space to solve the problem of insufficient IP address. At this time, the address space is expanded by using a multi-plane manner, and identity and address separation are not required; The gradual upgrade of identity and address separation features. The types of access networks supported by the present invention are described below. The above example of the present invention uses the IP address field of the conventional IP packet to transmit the identity of the present invention, thus supporting access of all Layer 2 access networks, for example, a mobile broadband data access network and a telecom broadband access network. The problem of the Layer 3 routing is not involved, and the aggregation of the Layer 2 switching is completed. The multi-plane bearer network architecture of the present invention can be well supported. For access networks that may involve Layer 3 routing, it is relatively more complicated, for example, On the one hand, the network needs to meet the needs of internal communication of the enterprise, and on the other hand, it needs to meet the needs of users within the enterprise network to access the multi-plane bearer network architecture of the present invention, because one user cannot simultaneously use the IP address identifier inside the enterprise network and The identity identifier of the present invention requires the router of the enterprise network to support the routing of the original IP address at the same time, and also needs to support the route of the identity identifier of the present invention. Since the identity identifier of the present invention is allocated, there is no route aggregation requirement, or the terminal moves. As a result, it is difficult to aggregate, and the requirements for the enterprise network router are relatively high, thereby increasing the cost. Therefore, another method for the enterprise network user to access the multi-bearing network plane architecture of the present invention is recommended. The method includes:

1. Allocating the identity identifier of the present invention to the enterprise network user;

2. The virtual access network of the multi-plane bearer network of the present invention is opened in the enterprise network, and the convergence of the second layer is completed.

The following describes the communication between users in the same access domain in the present invention: In the technical solution of the present invention, the user terminal device accesses the access switching router through the access network, and accesses the ASR in the same access switching router. The communication between the two users under control can control the switching devices in the Layer 2 access network through the access switching router according to the network planning, so that the terminal devices of the two users directly communicate with each other through Layer 2 switching, or through access Switch routers forward to communicate with each other.

The embodiment also discloses an access switching router (ASR), which is configured to: when the ASR is an ASR to which the first terminal device belongs, receive the first packet sent by the first terminal device to the second terminal device. The first packet uses the identity identifier (UID) of the first terminal device and the second terminal device as the source address and the destination address of the first packet respectively; and queries according to the UIDs of the first terminal device and the second terminal device respectively. Obtaining a route identifier (RID) of the first terminal device and the second terminal device and a number of the bearer network plane, and modifying the source address and the destination address of the first packet to the RID of the first terminal device and the RID of the second terminal device respectively Generating a second "3⁄4 text"; and passing the corresponding bearer network plane according to the number of the bearer network plane to which the second terminal device belongs Sending the second packet to the ASR to which the second terminal device belongs. The ASR is further configured to: when the ASR is the ASR to which the second terminal device belongs, after receiving the second packet sent by the bearer network plane to which the second terminal device belongs, according to the first packet in the second packet The RID of the terminal device and the second terminal device and the number of the associated bearer network plane, the UID of the first terminal device and the second terminal device are obtained, and the second packet is restored to the first packet, and the first packet is sent. Send to the second terminal device. The first packet uses the version information part of the IPV4 packet to carry the high-order UID (UID H ) of the first terminal device and the second terminal device, and uses the source address information part of the IPV4 packet to carry the first terminal device. The UID (UID L ) and the destination address information part of the IPV4 message carry the second terminal device low-end UID (UID L ). When the ASR is the ASR to which the first terminal device belongs, the ASR generates the second message, and restores the UID-H of the first packet to the version information of the packet. The ASR is configured to query the RIDs of the first terminal device and the second terminal device according to the UIDs of the first terminal device and the second terminal device, respectively, when the ASR is the ASR to which the first terminal device belongs. Number of the bearer network plane: The ASR obtains the RID of the first terminal device and the second terminal device and the number of the bearer network plane from the mapping server or the mapping information of the RID, the UID and the number of the bearer network plane in the local ASR. The ASR is further configured to: when the ASR is the ASR to which the first terminal device belongs, the receiving the first terminal device sends a third packet to the third terminal device, where the third packet is the user of the first terminal device The identifier (UID) is used as the source address of the third packet, and the routing identifier (RID) of the third terminal device is used as the destination address of the third packet. By default, the number of the bearer network plane of the third terminal is 0, and is in the third. The packet carries the number 0 of the bearer network plane of the third terminal. The RID and the bearer network plane of the first terminal device are obtained according to the UID query of the first terminal device. The number of the third packet is changed to the RID of the first terminal device to generate a fourth packet; and the fourth packet is sent by the bearer network plane 0 according to the number of the bearer network plane to which the third terminal device belongs. Give the ASR to which the third terminal device belongs. The ASR is further configured to: when the ASR is an ASR to which the third terminal device belongs,

After the fourth packet received by the ASR, the UID of the first terminal device is obtained according to the RID of the first terminal device and the number of the bearer network plane in the fourth packet, and the fourth packet is restored to the third packet. And sending the third packet to the third terminal device. among them,

When the ASR generates the fourth packet, the UID-H of the third packet is restored to the version information of the packet. When the ASR is the ASR to which the first terminal device belongs, the ASR is configured to obtain the RID of the first terminal device and the number of the bearer network plane according to the UID query of the first terminal device as follows: the ASR slave mapping The server or the mapping information of the RID, the UID, and the number of the bearer network plane is obtained by the local ASR, and the RID of the third terminal device and the number of the bearer network plane are obtained.

Industrial Applicability The present invention proposes a multi-plane bearer network architecture, which can be compatible with existing data bearer networks and the Internet, and realizes smooth transition and distributed implementation in next-generation network construction, especially for the next generation mobile communication network (4G). The need for network construction, through the multi-plane bearer network architecture and the identification of terminal devices with more than 32 bits to solve the problem of insufficient IP addresses, and the multi-plane structure also realizes a solution for terminal identity and location separation. , thus effectively solving the above two problems. The invention can effectively solve the problems of security, mobility, multi-hole, routing extension and network aggregation. The network capacity of the multi-plane bearer network architecture of the present invention is increased by the capacity of multiple bearer network planes, that is, equal to the number of bearer network planes multiplied by the capacity of a single bearer network plane, or The number of network planes is extended to expand the network capacity of the entire architecture, thereby breaking the capacity of the traditional network (equivalent to the capacity of a bearer network plane of the present invention), and solving the scale bottleneck of the existing network. The multi-plane bearer network architecture of the present invention utilizes the identity identifier of the terminal device to implement mapping processing between the route and the route identifier through the access switch router, and solves related problems caused by the identity and location in the traditional network. The packet format used by the multi-plane bearer network architecture of the present invention is completely compatible with the traditional IP packet format, and can smoothly upgrade the existing network, build on demand, and effectively control the pace of investment and construction, thereby ensuring network operation. Healthy and stable development.

Claims

Claim

A bearer network, the network comprising: a plurality of bearer network planes and terminal devices, wherein the bearer network plane is an Internet Protocol (IP) bearer network, and the bearer network plane is set to: implement datagrams between terminal devices And routing and forwarding, each bearer network plane in the multiple bearer network planes is configured with a unique number, and uses a separate routing address space for routing and addressing;

The terminal device is configured to: use an identity (UID) as an addressing identifier, the UID includes a low segment (UID-L) and a high segment (UID-H), and the low segment uses an IP address space. The high segment is used to increase the number of bits of the UID and expand the address space.

2. The network of claim 1, the network further comprising: an access switching router (ASR), wherein the ASR is respectively connected to the plurality of bearer network planes, and the ASR is set to: query according to a UID of the terminal device Obtain the corresponding route identifier (RID) and the number of the bearer network plane.

3. The network of claim 2, the network further comprising: an access network, the access network being located between the terminal device and the ASR, the access network being configured to: implement a terminal device of the network Access to the ASR.

4. The network according to claim 2, wherein the UID is a unique identity of the terminal device, used between the terminal device and the ASR, and remains unchanged when the terminal device moves; the RID is a location of the terminal device. Logo, used at the core layer.

The network of claim 4, wherein the lower part of the UID is carried by the IP address part of the IP packet header; the high part of the UID is transmitted by using the version bit of the IP packet.

6. The network of claim 5, wherein the lower portion of the UID uses a 32-bit address of the IPv4 address space.

7. The network according to claim 5, wherein the UID uses a mobile phone number.

8. The network according to claim 7, wherein, when the mobile phone number is used as the UID, the mobile phone number is converted into a hexadecimal number, and the upper four bits are used as UID-H, and the lower three bits are used as UID-L. .

The network according to claim 8, wherein after converting the mobile phone number into a hexadecimal number, if the value of the upper four bits is greater than the number of the bearer network plane, the high four bits are compressed and converted. To meet the number of bearer network planes.

10. The network according to claim 7, wherein, when the mobile phone number is used as the UID, the last ten digits of the mobile phone number are converted into a hexadecimal number as UID_L.

11. The network according to claim 7, wherein, when the mobile phone number is used as the UID, the first two digits of the mobile phone number are converted into a single digit, and the converted one digit and the last nine digits of the mobile phone number are used. Ten digits, converted to hexadecimal digits, as UID-L.

The network of claim 2, wherein the ASR is further configured to: perform mapping information of registration, access control, security authentication, maintenance UID, RID, and number of the 7-layer network plane of the terminal device, And >3⁄4 text rewriting and forwarding.

The network according to claim 12, wherein the data packet between the ASR and the bearer network plane is in an IP packet format, and the RID is used to implement routing in the bearer network plane. Addressing.

14. The network of claim 13, wherein the RID uses an IP address.

15. The network according to claim 1, wherein the bearer network plane uses an IPv4 data bearer network, is planned and constructed according to an IP network protocol and principles, and is composed of an IPv4 routing protocol and router device interconnection.

16. The network of claim 2, the network further comprising: a mapping server, the mapping server being connected to a bearer network plane, the mapping server being configured to: be responsible for registering, saving, and updating UIDs, RIDs, and bearer network planes Numbered mapping information; The ASR is further configured to: obtain a corresponding RID and a bearer network plane number from the mapping server or from the local ASR query according to the UID of the terminal device.

The network according to claim 16, wherein the mapping server uses the RID as the identifier, and the terminal device is deployed in the bearer network plane; or uses the UID as the identifier to access the bearer network plane through the ASR.

18. The network according to claim 17, wherein the mapping server is further configured to: after updating the mapping information of the UID, the RID, and the number of the bearer network plane, send the update message to the updated UID, RID, and bearer network. The mapping information of the plane number is sent to the ASR.

The network of claim 1, wherein the high segment of the UID is a number of a bearer network plane to which the corresponding terminal device belongs.

20. The network of claim 1, wherein the terminal device addressed by the RID is connected to the bearer network plane 0 in the plurality of bearer network planes.

A data transmission method, applied to the bearer network according to any one of claims 1 to 20, the method comprising: receiving, by the first access switching router (ASR), the first terminal device to send to the second terminal device a first packet, where the first packet uses the identity identifier (UID) of the first terminal device and the second terminal device as the source address and the destination address of the first text respectively; after the first ASR receives the first packet, Querying the route identifier (RID) of the first terminal device and the second terminal device and the number of the bearer network plane according to the UIDs of the first terminal device and the second terminal device respectively, and modifying the source address and the destination address of the first packet respectively Generating a second packet to the RID of the first terminal device and the RID of the second terminal device, and sending, by the first ASR, the second packet to the corresponding bearer network plane according to the number of the bearer network plane to which the second terminal device belongs Second ASR.

22. The method of claim 21, the method further comprising: After the second packet received by the second ASR, the UID of the first terminal device and the second terminal device are obtained according to the RID of the first terminal device and the second terminal device and the number of the bearer network plane to which the second terminal device belongs. The second packet is restored to the first packet, and the first packet is sent to the second terminal device.

The method of claim 22, wherein the first packet uses the version information part of the IPV4 packet to carry the high-order UID (UID H ) of the first terminal device and the second terminal device, and uses the IPV4 packet. The source address information part carries the low-end UID (UID L ) of the first terminal device, and uses the destination address information part of the IPV4 message to carry the second terminal device low-end UID (UID L ).

The method according to claim 23, wherein, when the first ASR generates the second message, the UID_H of the first text is restored to the version information of the text.

The method of claim 22, wherein the first ASR queries the RID of the first terminal device and the second terminal device and the number of the bearer network plane according to the UIDs of the first terminal device and the second terminal device, respectively. The first ASR obtains the RID of the first terminal device and the second terminal device and the number of the bearer network plane from the mapping server or the mapping information of the RID, the UID, and the number of the bearer network plane in the local ASR.

The data transmission method is applied to the bearer network according to any one of claims 1 to 20, the method comprising: receiving, by the first access switching router (ASR), the first terminal device to send to the third terminal device The third packet, the third packet uses the user identifier (UID) of the first terminal device as the source address of the third packet, and uses the routing identifier (RID) of the third terminal device as the destination address of the third packet. The number of the bearer network plane of the third terminal device is 0, and the third packet carries the number 0 of the bearer network plane of the third terminal device. After receiving the third packet, the first ASR is configured according to the first terminal device. UID query gets first The RID of the terminal device and the number of the bearer network plane, the source address of the third packet is modified to the RID of the first terminal device, and the fourth packet is generated; and the first ASR is based on the number of the bearer network plane to which the third terminal device belongs. The fourth packet is sent to the third ASR by the bearer network plane 0.

The method of claim 26, the method further comprising: after the fourth packet received by the third ASR, according to the RID of the first terminal device and the number of the bearer network plane to which the first terminal device belongs, The UID of the terminal device restores the fourth packet to the third packet, and sends the third packet to the third terminal device.

The method of claim 27, wherein the first terminal device uses the version information part of the IPV4 packet to carry the high-order UID (UID H ) of the first terminal device, and uses the source address information part of the IPV4 packet. The low segment UID (UID L ) carrying the first terminal device.

The method according to claim 28, wherein, when the first ASR generates the fourth packet, the UID-H of the third packet is restored to the version information of the packet.

The method of claim 25, wherein the first ASR obtains the RID of the first terminal device and the number of the bearer network plane according to the UID of the first terminal device, where the first ASR is from the mapping server or The mapping information of the RID, the UID, and the number of the bearer network plane is queried locally, and the RID of the third terminal device and the number of the bearer network plane are obtained.