CN113225256B

CN113225256B - Routing method, device, equipment and storage medium

Info

Publication number: CN113225256B
Application number: CN202010080039.4A
Authority: CN
Inventors: 孙军帅; 易芝玲
Original assignee: China Mobile Communications Group Co Ltd; China Mobile Communications Ltd Research Institute
Current assignee: China Mobile Communications Group Co Ltd; China Mobile Communications Ltd Research Institute
Priority date: 2020-02-04
Filing date: 2020-02-04
Publication date: 2022-09-13
Anticipated expiration: 2040-02-04
Also published as: CN113225256A; WO2021155771A1

Abstract

The embodiment of the application discloses a routing method, a routing device, routing equipment and a storage medium, wherein the method is executed by a functional entity of a current layer and comprises the following steps: receiving an IP packet from an upper layer adjacent to the current layer through a first bearer; wherein the first bearer is a bearer between the upper layer and the current layer; performing packet construction according to the header information of the protocol data unit of the current layer and the IP packet to obtain the protocol data unit of the current layer; determining an identifier of a target second bearer corresponding to the first bearer; wherein the second bearer is a bearer between the current layer and a lower layer adjacent to the current layer; and sending the protocol data unit to the lower layer through the target second bearer according to the identifier of the target second bearer.

Description

Routing method, device, equipment and storage medium

Technical Field

The embodiments of the present application relate to, but not limited to, the field of communications, and in particular, to a routing method, apparatus, device, and storage medium.

Background

The functionality of the Packet Data Convergence Protocol (PDCP) is given in the 38.323 specification of the third Generation Partnership Project (3rd 3GPP), where Header Compression (Header Compression) and Header Decompression (Header Decompression) are one of the basic functions of the PDCP Protocol functionality. In the related art, for example, the fifth generation (5) ^th Generation, 5G) wireless network, since PDCP is for each PDCP Service Data Unit (Service Data Unit)SDU) performs header compression/decompression of an Internet Protocol (IP) packet, which increases load and power consumption of terminal processing and also increases delay of packet processing.

In view of the above problems in the related art, no solution has been proposed at present.

Disclosure of Invention

In view of this, embodiments of the present application provide a routing method, apparatus, device, and storage medium.

The technical scheme of the embodiment of the application is realized as follows:

in one aspect, an embodiment of the present application provides a routing method, where the method is executed by a functional entity in a current layer, and the method includes:

receiving an IP packet from an upper layer adjacent to the current layer through a first bearer; wherein the first bearer is a bearer between the upper layer and the current layer;

performing packet construction according to the header information of the protocol data unit of the current layer and the IP packet to obtain the protocol data unit of the current layer;

determining an identifier of a target second bearer corresponding to the first bearer; wherein the second bearer is a bearer between the current layer and a lower layer adjacent to the current layer;

and sending the protocol data unit to the lower layer through the target second bearer according to the identifier of the target second bearer.

In another aspect, an embodiment of the present application provides a routing method, where the method is executed by a functional entity in a current layer, and the method includes:

receiving a data packet from a lower layer adjacent to the current layer through a second bearer; wherein the second bearer is a bearer between the current layer and the lower layer;

determining an identifier of a target first bearer corresponding to the second bearer; the first bearer is a bearer between the current layer and an upper layer adjacent to the current layer;

determining a target IP address corresponding to the identification of the target first bearer;

building an IP packet according to the target IP address and the data packet to obtain a reconstructed IP packet;

and sending the reconstructed IP packet to the upper layer through the target first bearer according to the identifier of the target first bearer.

In another aspect, an embodiment of the present application provides a routing apparatus, including:

a first receiving module, configured to receive, through a first bearer, an IP packet from an upper layer adjacent to a current layer; wherein the first bearer is a bearer between the upper layer and the current layer;

the first packet group module is used for carrying out packet construction according to the protocol data unit header information of the current layer and the IP packet to obtain the protocol data unit of the current layer;

a first determining module, configured to determine an identifier of a target second bearer corresponding to the first bearer; the second bearer is a bearer between the current layer and a lower layer adjacent to the current layer;

and the first sending module is used for sending the protocol data unit to the lower layer through the target second bearer according to the identifier of the target second bearer.

a second receiving module, configured to receive, through a second bearer, a data packet from a lower layer adjacent to a current layer; wherein the second bearer is a bearer between the current layer and the lower layer;

a second determining module, configured to determine an identifier of a target first bearer corresponding to the second bearer; the first bearer is a bearer between the current layer and an upper layer adjacent to the current layer;

a third determining module, configured to determine a target IP address corresponding to the identifier of the target first bearer;

the second group of packet module is used for carrying out IP packet construction according to the target IP address and the data packet to obtain a reconstructed IP packet;

and a second sending module, configured to send the reconstructed IP packet to the upper layer through the target first bearer according to the identifier of the target first bearer.

In another aspect, an embodiment of the present application provides a routing device, which includes a memory and a processor, where the memory stores a computer program that is executable on the processor, and the processor implements the steps in the method when executing the program.

In yet another aspect, an embodiment of the present application provides a computer-readable storage medium, on which a computer program is stored, and the computer program, when executed by a processor, implements the steps in the method.

In the embodiment of the application, the IP packet routing of the current layer is completed through the corresponding relation between the first bearing and the second bearing, the PDU data packet of the current layer does not need to carry the header information of the IP packet any more, and the shorter PDU header information is adopted to realize the data processing and data routing without the IP packet header, so that the header overhead of the IP packet is reduced, and the low-overhead transmission of the IP packet in a wireless network is realized. In addition, because there is no data of the IP header in the PDU packet of the current layer, when the lower layer is the PDCP protocol layer, the header compression/decompression function of the PDCP layer can be cancelled, thereby avoiding the problems of increased processing load and power consumption of the terminal and increased processing delay of the packet due to header compression/decompression of the PDCP layer.

Drawings

FIG. 1A is a functional implementation diagram of a PDCP layer;

fig. 1B is a schematic flowchart illustrating an implementation flow of a routing method according to an embodiment of the present application;

fig. 2 is a schematic flow chart of an implementation of a routing method according to an embodiment of the present application;

fig. 3 is a schematic flow chart of an implementation of a routing method according to an embodiment of the present application;

fig. 4 is a schematic implementation flow chart of a routing method according to an embodiment of the present application;

fig. 5A is a schematic implementation flowchart of a routing method according to an embodiment of the present application;

fig. 5B is a schematic flow chart illustrating an implementation of a method for determining a third mapping relationship according to the embodiment of the present application;

fig. 6 is a schematic implementation flow chart of a routing method according to an embodiment of the present application;

fig. 7 is a schematic flowchart illustrating an implementation flow of a routing method according to an embodiment of the present application;

fig. 8 is a schematic flow chart of an implementation of a routing method according to an embodiment of the present application;

fig. 9A is a schematic diagram of data transmission in which a terminal is simultaneously connected to multiple base stations according to an embodiment of the present application;

FIG. 9B shows an embodiment UP of the present application _L3 Is a functional schematic diagram of a single functional entity;

FIG. 9C shows an embodiment UP of the present application _L3 A functional schematic diagram when the bifunctional entity is used;

fig. 9D is a schematic diagram of an end-to-end IP tunnel function provided in the embodiment of the present application;

fig. 9E is a low-overhead routing method of an IP packet at an AS layer according to an embodiment of the present application;

fig. 10 is a low-overhead routing method of an IP packet at an AS layer according to an embodiment of the present application;

fig. 11 is a schematic structural diagram of a routing device according to an embodiment of the present application;

fig. 12 is a schematic structural diagram of a routing device according to an embodiment of the present application;

fig. 13 is a schematic hardware entity diagram of a routing device in an embodiment of the present application.

Detailed Description

In order to make the purpose, technical solutions and advantages of the present application clearer, the technical solutions of the present application are further described in detail with reference to the drawings and the embodiments, the described embodiments should not be considered as limiting the present application, and all other embodiments obtained by a person of ordinary skill in the art without creative efforts belong to the protection scope of the present application.

In the following description, reference is made to "some embodiments" which describe a subset of all possible embodiments, but it is understood that "some embodiments" may be the same subset or different subsets of all possible embodiments, and may be combined with each other without conflict.

Where similar language of "first/second" appears in the specification, the following description is added, and where reference is made to the term "first \ second \ third" merely to distinguish between similar items and not to imply a particular ordering with respect to the items, it is to be understood that "first \ second \ third" may be interchanged with a particular sequence or order as permitted, to enable the embodiments of the application described herein to be performed in an order other than that illustrated or described herein.

Unless defined otherwise, all technical and scientific terms used herein have the same meaning as commonly understood by one of ordinary skill in the art to which this application belongs. The terminology used herein is for the purpose of describing embodiments of the present application only and is not intended to be limiting of the application.

In order to better understand the technical solution described in the embodiments of the present application, first, the header compression and header decompression functions of the PDCP in the related art will be explained.

In the related art, the IP packet includes an IP packet header and an IP packet body, where the data amount in the IP packet header is large and occupies most bandwidth resources. In order to utilize bandwidth resources more efficiently, it is necessary to compress the IP packet header during data transmission and decompress the IP packet header during data reception, thereby reducing the length of the IP packet header during transmission. Fig. 1A is a functional implementation diagram of a PDCP layer, and as shown in fig. 1A, when data transmission is performed, the PDCP layer performs header compression on each packet associated with a PDCP SDU and each packet not associated with the PDCP SDU, and when data reception is performed, the PDCP layer also needs to perform header decompression on each packet associated with the PDCP SDU and each packet not associated with the PDCP SDU. Thus, not only the load and power consumption of terminal processing are increased, but also the time delay of data packet processing is increased.

The embodiment of the present application provides a routing method, which can solve the problems of increased terminal processing load and power consumption and increased data packet processing delay caused by the header compression/decompression function of PDCP in the related art. The method is executed by a functional entity at a current layer of a routing device (i.e., a communication node), fig. 1B is a schematic diagram of an implementation flow of the method, and as shown in fig. 1B, the method includes the following steps:

step S101, receiving an IP packet from an upper layer adjacent to the current layer through a first bearer; wherein the first bearer is a bearer between the upper layer and the current layer;

here, the first bearer may include a bearer for carrying an IP packet when the upper layer transmits the IP packet to the current layer and a bearer for carrying the IP packet when the current layer transmits the IP packet to the upper layer. IP packets received over the same first bearer have the same source and destination addresses.

Step S102, performing packet construction according to Protocol Data Unit (PDU) header information of the current layer and the IP packet to obtain a Protocol Data Unit of the current layer;

here, the PDU header information of the current layer is information for identifying protocol data of the current layer, and the PDU header information has a shorter length compared to the header information of the IP packet, and in some embodiments, simple identification information may be used as the PDU header information. In implementation, those skilled in the art can define the PDU header information of the current layer according to actual needs.

When the packet is constructed, the content related to the IP address information in the IP packet can be removed to obtain the SDU of the current layer, and the PDU header information is added to the obtained SDU to obtain the protocol data unit of the current layer.

In some embodiments, the data packet may be constructed according to the header information of the protocol data unit of the current layer and the dead load of the IP packet, so as to obtain the protocol data unit of the current layer. Here, the payload of the IP packet is information other than the IP packet header in the IP packet. In implementation, the payload of the IP packet may be extracted by parsing the IP packet, and the PDU header information may be added to the obtained payload as an SDU of the current layer, so as to obtain a PDU header information of the current layer.

Step S103, determining the identifier of a target second bearer corresponding to the first bearer; the second bearer is a bearer between the current layer and a lower layer adjacent to the current layer;

here, the second bearer has a specific identity from which a unique second bearer can be determined. In some embodiments, a mapping relationship between the identifiers of the specific first bearer and the specific second bearer may be preconfigured, and in implementation, the identifier of the target second bearer corresponding to the first bearer is determined by querying the mapping relationship. In some embodiments, when data transmission is required, a suitable target second bearer may be configured for the first bearer according to a current use condition of the second bearer, and an identifier of the target second bearer may be obtained. In some embodiments, the second Bearer may be a Radio Bearer (RB).

Step S104, according to the mark of the target second bearing, the protocol data unit is sent to the lower layer through the target second bearing.

Here, the target second bearer may be determined according to the identifier of the target second bearer, and the protocol data unit is carried on the target second bearer and sent to the lower layer.

In some embodiments, the current Layer may be Layer 3 (L3) newly defined at an Access Stratum (AS), the upper Layer may be other protocol layers above the network Layer, and the lower Layer may be a protocol Layer in a data link Layer, such AS a PDCP protocol Layer.

According to the routing method, the routing of the IP packet of the current layer is completed through the corresponding relation between the first bearing and the second bearing, the PDU data packet of the current layer does not need to carry the header information of the IP packet any more, and the shorter PDU header information is adopted, so that the data processing and the data routing without the IP packet header are realized, the header cost of the IP packet is reduced, and the low-cost transmission of the IP packet in a wireless network is realized. In addition, because there is no data of the IP header in the PDU packet of the current layer, when the lower layer is the PDCP protocol layer, the header compression/decompression function of the PDCP layer can be cancelled, thereby avoiding the problems of increased processing load and power consumption of the terminal and increased processing delay of the packet due to header compression/decompression of the PDCP layer.

An embodiment of the present application provides a routing method, where the method is executed by a functional entity in a current layer, and as shown in fig. 2, the method includes:

step S201, receiving an IP packet from an upper layer adjacent to the current layer through a first bearer; wherein the first bearer is a bearer between the upper layer and the current layer;

here, the first bearer has a specific identity from which a unique first bearer can be determined.

Step S202, performing packet construction according to the header information of the protocol data unit of the current layer and the IP packet to obtain the protocol data unit of the current layer;

step S203, determining an identifier of a target second bearer corresponding to the first bearer; wherein the second bearer is a bearer between the current layer and a lower layer adjacent to the current layer;

step S204, according to the mark of the target second bearing, the protocol data unit is sent to the lower layer through the target second bearing.

Here, the above steps S201 to S204 may refer to the implementation of the above steps S101 to S104, and are not described herein again for brevity.

Step S205, establishing a first mapping relation between the identifier of the first bearer and the IP address carried in the IP packet;

here, the IP packet may be subjected to IP address resolution to obtain IP address information, where the IP address information includes a source IP address and a destination IP address. In implementation, the identifier of the first bearer and the IP address information may be correspondingly stored, where the storage form includes, but is not limited to, a form of a configuration file, a form of a key value pair, or a form of a mapping relationship table, and the stored location includes, but is not limited to, a local storage, an operating memory, or a database. In some embodiments, the first mapping may be saved to a particular first mapping table.

Step S206, synchronizing the first mapping relation to a communication opposite end.

Here, the correspondent node may be a data receiving end in the data communication process. There are many ways to synchronize the first mapping relationship to the communication peer, and the first mapping relationship may be synchronized to the communication peer in a signaling transmission manner after the first mapping relationship is established, or may be transmitted to the communication peer by adding the first mapping relationship to a PDU packet of a current layer. In implementation, a person skilled in the art may select a suitable synchronization manner according to actual situations, which is not limited in the embodiment of the present application.

In some embodiments, the first mapping relationship may be synchronized to the correspondent node through Radio Resource Control (RRC) signaling transmission. In implementation, the first mapping relationship may be transmitted to the correspondent node through a Signaling Radio Bearers (SRBs) established with the correspondent node, such as SRB 1.

Since the IP packets received through the same first bearer have the same source address and destination address, in some embodiments, the above steps S205 and S206 may be performed only when the IP packet is the first IP packet received from the first bearer, so as to reduce data processing load and data transmission overhead.

An embodiment of the present application provides a routing method, where the method is executed by a functional entity in a current layer, and as shown in fig. 3, the method includes:

step S301, receiving an IP packet from an upper layer adjacent to the current layer through a first bearer; wherein the first bearer is a bearer between the upper layer and the current layer, and the first bearer has a specific identifier;

step S302, performing packet construction according to the protocol data unit header information of the current layer and the IP packet to obtain the protocol data unit of the current layer;

step S303, inquiring a second mapping relation according to the identifier of the first bearer to obtain an identifier of a target second bearer corresponding to the first bearer; the second bearer is a bearer between the current layer and a lower layer adjacent to the current layer, and the second mapping relationship is used for representing a relationship between an identifier of the first bearer and an identifier of the second bearer;

here, the second mapping relationship may be a pre-configured correspondence relationship between specific first bearers and identifiers of second bearers, and in implementation, the identifier of the target second bearer corresponding to the first bearer is determined by querying the correspondence relationship.

Step S304, according to the identifier of the target second bearer, sending the protocol data unit to the lower layer through the target second bearer.

It should be noted that, in the implementation of the steps S301, S302, and S304, reference may be made to the implementation of the steps S101, S102, and S104, which is not described herein again.

In some embodiments, before the step S303, the method further comprises: selecting and configuring a corresponding target second bearer for the first bearer according to the IP address carried in the IP packet, wherein the target second bearer has a specific identifier; establishing a second mapping relation between the identifier of the first bearer and the identifier of the target second bearer; and synchronizing the second mapping relation to a communication opposite end.

Here, the IP address carried in the IP packet includes a source IP address and a destination IP address of the IP packet, and a corresponding second bearer may be selected and configured for the first bearer according to the source IP address and the destination IP address, including but not limited to configuring identity information of the second bearer, multiplexing (Multiplex) information of the first bearer on the second bearer, identity identification information of the first bearer on the second bearer, a format used when a packet on the first bearer is received and sent through the second bearer, or Quality of Service (QoS) information, and the like. In implementation, the second bearer that can be used may be automatically selected for the first bearer according to a current usage of the second bearer. In some embodiments, multiple first bearers may be mapped onto the same second bearer in a multiplexing manner.

After determining a second bearer corresponding to the first bearer, the identifier of the first bearer and the identifier of the second bearer may be correspondingly stored, where the storage form includes, but is not limited to, a form of a configuration file, a form of a key value pair, or a form of a mapping relationship table, and the stored location includes, but is not limited to, a local storage, an operating memory, or a database. In some embodiments, the second mapping may be saved to a particular second mapping table.

The communication opposite end can be a data sending end or a data receiving end in the data communication process. There are many ways to synchronize the second mapping relationship to the communication peer, and the second mapping relationship may be synchronized to the communication peer after the second mapping relationship is established in a signaling transmission manner, or may be transmitted to the communication peer by adding the second mapping relationship to a PDU packet of a current layer. In implementation, a person skilled in the art may select an appropriate synchronization mode according to actual situations, and the embodiment of the present application is not limited thereto. In some embodiments, the second mapping relationship may be synchronized to the correspondent node through RRC signaling transmission.

In some embodiments, the same second bearer is configured for the same first bearer, so that only when the IP packet is a first IP packet received from the first bearer, a corresponding target second bearer is selected and configured for the first bearer, a second mapping relationship between the identifier of the first bearer and the identifier of the target second bearer is established, and the second mapping relationship is synchronized to a correspondent node, so as to reduce data processing load and data transmission overhead.

In some embodiments, the functional entities of the current layer include a control plane entity and a user plane entity, and before the obtaining of the identifier of the target second bearer corresponding to the first bearer, the method further includes: the user plane entity sends the IP address carried in the IP packet and the identifier of the first bearer to the control plane entity; the control plane entity selects and configures a target second bearer corresponding to the first bearer according to the IP address and the identifier of the first bearer; wherein the target second bearer has a specific identity; the control plane entity establishes a second mapping relation between the identifier of the first bearer and the identifier of the target second bearer; and the control plane entity synchronizes the second mapping relation to a communication opposite end.

In implementation, the second mapping relationship may be configured by the control plane entity and the user plane entity of the sending end and then synchronized to the receiving end, or configured by the control plane entity and the user plane entity of the receiving end and then synchronized to the sending end.

An embodiment of the present application provides a routing method, where the method is executed by a functional entity in a current layer, and as shown in fig. 4, the method includes:

step S401, receiving an IP packet from an upper layer adjacent to the current layer through a first bearer; wherein the first bearer is a bearer between the upper layer and the current layer, and the first bearer has a specific identifier;

step S402, inquiring a second mapping relation according to the identifier of the first bearer to obtain the identifier of the second mapping relation; the second mapping relationship has a specific identifier, and is used for characterizing a relationship between the identifier of the first bearer and the identifier of a second bearer, where the second bearer is a bearer between the current layer and a lower layer adjacent to the current layer;

here, the second mapping relationship has a specific identifier, and a unique second mapping relationship that characterizes a correspondence relationship between the identifier of the first bearer and the identifier of the second bearer may be determined according to the identifier, so as to determine a correspondence relationship between the unique identifier of the first bearer and the identifier of the second bearer.

Step S403, performing packet construction according to the protocol data unit header information of the current layer and the IP packet to obtain the protocol data unit of the current layer; wherein the protocol data unit header information includes an identification of the second mapping relationship;

here, since multiple first bearers may be mapped to the same second bearer in a multiplexing manner, that is, the identifier of the first bearer and the identifier of the second bearer may not be in a one-to-one mapping relationship, the identifier of the second mapping relationship may be included in the header information of the protocol data unit, so that the correspondent node may determine the unique correspondence between the identifier of the first bearer and the identifier of the second bearer according to the identifier.

Step S404, inquiring a second mapping relation according to the identifier of the first bearer to obtain the identifier of a target second bearer corresponding to the first bearer;

step S405, sending the protocol data unit to the lower layer through the target second bearer according to the identifier of the target second bearer.

It should be noted that, in the implementation of the steps S401, S403 to S405, reference may be made to the implementation of the steps S301 to S304, which is not described herein again.

An embodiment of the present application provides a routing method, which is executed by a functional entity in a current layer, as shown in fig. 5A, the method includes the following steps:

step S501, in the process of service application, an IP packet channel with a specific identifier is established with a communication opposite end, and data transmitted on the IP packet channel has the same source IP address and destination IP address;

here, in the process of the terminal applying for the service to the network side, the terminal and the network side establish an IP packet channel with a specific identifier. In practice, the IP packet path may be an end-to-end IP tunnel established by IP tunneling, each IP tunnel having a specific identifier, and a unique IP tunnel may be determined according to the identifier. Since the IP tunneling technology is a technology widely studied in the field, a person skilled in the art can understand the technology with reference to related technologies, and details of the embodiments of the present application are not described herein.

In some embodiments, the same terminal may establish a plurality of IP packet channels with the network side, and different IP packet channels may correspond to different source IP addresses and destination IP addresses.

Step S502, obtaining a third mapping relation, wherein the third mapping relation is used for representing the corresponding relation between the identification of the IP packet channel and the identification of the second bearer;

here, the third mapping relationship may be obtained by the current communication end configuration, or may be synchronized to the current communication end after the communication peer is configured. In implementation, the third mapping relationship may be configured by the functional entity of the sending end and then synchronized to the receiving end, or configured by the functional entity of the receiving end and then synchronized to the sending end.

In some embodiments, the method for determining the third mapping relationship may be as shown in fig. 5B, and includes:

step S511, selecting and configuring a corresponding target second bearer for the IP packet channel, wherein the target second bearer has a specific identifier;

here, the corresponding second bearer may be selected and configured for the IP packet tunnel according to a source IP address and a destination IP address corresponding to the IP packet tunnel, which include, but are not limited to, configuring identity information of the second bearer, Multiplex (Multiplex) information of the first bearer on the second bearer, identity identification information of the first bearer in the second bearer, a format or Quality of Service (QoS) information used when a packet on the first bearer is received and sent through the second bearer, and the like. In implementation, the second bearer that can be used may be automatically selected for the IP packet tunnel according to the current usage of the second bearer. In some embodiments, multiple IP packet channels may be mapped to the same second bearer in a multiplexing manner. In some embodiments, the same IP packet channel may be mapped to a plurality of second bearers.

Step S512, establishing a third mapping relation between the identifier of the IP packet channel and the identifier of the target second bearer;

here, the identifier of the IP packet channel and the identifier of the second bearer may be correspondingly stored, where the storage form includes, but is not limited to, a form of a configuration file, a form of a key value pair, or a form of a mapping relationship table, and the stored location includes, but is not limited to, a local storage, an operating memory, or a database. In some embodiments, the third mapping may be saved to a particular third mapping table.

Step S513, synchronizing the third mapping relation to a communication opposite terminal;

here, the correspondent node may be a data transmitting end or a data receiving end in the data communication process. There are many ways to synchronize the third mapping relationship to the communication peer, and the third mapping relationship may be synchronized to the communication peer after the third mapping relationship is established in a signaling transmission manner, or the third mapping relationship may be added to a PDU packet of a current layer and transmitted to the communication peer. In implementation, a person skilled in the art may select an appropriate synchronization mode according to actual situations, and the embodiment of the present application is not limited thereto. In some embodiments, the third mapping relationship may be synchronized to the correspondent node through RRC signaling transmission.

In some embodiments, the third mapping relationship may also be obtained from the correspondent node by receiving signaling or a data packet.

In some embodiments, the third mapping relationship may be stored in a specific third mapping relationship table.

Step S503, receiving an IP packet from an upper layer adjacent to the current layer through a first bearer; wherein, the first bearer is an IP packet channel with a specific identifier, and is used for bearer between the upper layer and the current layer;

step S504, according to the protocol data unit header information of the current layer and the IP packet, performing packet construction to obtain the protocol data unit of the current layer;

step S505, inquiring the third mapping relation according to the identifier of the IP packet channel to obtain the identifier of a target second bearer corresponding to the IP packet channel; wherein the second bearer is a bearer between the current layer and a lower layer adjacent to the current layer;

step S506, according to the identifier of the target second bearer, sending the pdu to the lower layer through the target second bearer.

Here, the steps S503 to S506 may refer to the implementation of the steps S101 to S104, which is not described herein again.

An embodiment of the present application provides a routing method, which is executed by a functional entity in a current layer, as shown in fig. 6, and the method includes the following steps:

step S601, receiving a data packet from a lower layer adjacent to the current layer through a second bearer; wherein the second bearer is a bearer between the current layer and the lower layer;

here, the data packet may be a protocol data unit of a current layer, and the second bearer has a specific identifier, which may be used to determine a unique second bearer. In practice, the second bearer may be an RB.

Step S602, determining an identifier of a target first bearer corresponding to the second bearer; the first bearer is a bearer between the current layer and an upper layer adjacent to the current layer;

here, the first bearer has a specific identity from which a unique first bearer can be determined. In some embodiments, a mapping relationship between a specific second bearer and an identifier of the first bearer may be preconfigured, and in implementation, the identifier of the target first bearer corresponding to the second bearer is determined by querying the mapping relationship.

In some embodiments, a specific second mapping relationship table may be queried according to the identifier of the second bearer to obtain an identifier of a target first bearer corresponding to the second bearer; and the second mapping relation table is used for representing the mapping relation between the identifier of the first bearer and the identifier of the second bearer.

In some embodiments, before the determining of the identifier of the target first bearer corresponding to the second bearer, the second mapping relationship table may be obtained from the correspondent node in a manner of receiving a signaling. In some embodiments, a new or updated second mapping relationship may also be obtained from the correspondent node in a signaling receiving manner, and updated to the second mapping relationship table.

Step S603, determining a target IP address corresponding to the identifier of the target first bearer;

here, a mapping relationship between the identifier of the specific first bearer and the IP address may be configured in advance, and in implementation, the identifier of the target first bearer corresponding to the second bearer is determined by querying the mapping relationship.

In some embodiments, a specific first mapping relationship table may be queried according to the identifier of the target first bearer to obtain a target IP address corresponding to the identifier of the target first bearer, where the first mapping relationship table is used to characterize a mapping relationship between the identifier of the first bearer and the IP address.

In some embodiments, before the determining of the target IP address corresponding to the identifier of the target first bearer, a first mapping relationship table may be obtained from a correspondent node in a manner of receiving a signaling. In some embodiments, a newly added or updated first mapping relationship may also be obtained from the correspondent node in a manner of receiving signaling, and updated to the first mapping relationship table.

Step S604, IP packet construction is carried out according to the target IP address and the data packet to obtain a reconstructed IP packet;

here, the data packet includes a PDU header of a current layer and a payload of the current layer, and the data packet may be analyzed to obtain the payload of the current layer as the payload of the IP packet. The IP address includes a source IP address and a destination IP address, and an IP packet header corresponding to the data packet may be constructed according to the source IP address and the destination IP address and a format of a specific IP packet header. And obtaining a reconstructed IP packet according to a specific IP packet format by using the dead load of the IP packet and the IP packet header.

Step S605, according to the identifier of the target first bearer, sending the reconstructed IP packet to the upper layer through the target first bearer.

Here, the target first bearer may be determined according to the identifier of the target first bearer, and the reconstructed IP packet may be carried on the target first bearer and sent to an upper layer.

The embodiment of the present application provides a routing method, which is executed by a functional entity at a current layer, and as shown in fig. 7, the method includes the following steps:

step S701, receiving a data packet from a lower layer adjacent to the current layer through a second bearer; wherein the second bearer has a specific identity;

step S702, analyzing the data packet to obtain an identifier of a second mapping relation in protocol data unit header information of the data packet;

here, the header information of the data packet, that is, the pdu header information of the current layer, may be obtained by parsing the data packet. The header information of the pdu includes an identifier of the second mapping relationship, and the identifier of the second mapping relationship can be obtained by analyzing the header information of the pdu.

Step S703, querying a specific second mapping relationship table according to the identifier of the second mapping relationship, to obtain an identifier of a target first bearer corresponding to the second bearer; the second mapping relation table is used for representing a mapping relation between the identifier of the first bearer and the identifier of the second bearer, and each second mapping relation in the second mapping relation table has a specific identifier;

here, each of the second mapping relationships has a specific identifier, and a unique second mapping relationship that represents a correspondence between the identifier of the first bearer and the identifier of the second bearer may be determined from the second mapping relationship table according to the identifier, so as to determine a correspondence between the identifier of the unique first bearer and the identifier of the second bearer. In implementation, the Identifier of the second mapping relationship may be an index number of each record in the second mapping relationship table, or may be a Universal Unique Identifier (UUID), and a person skilled in the art may select an appropriate Identifier according to an actual situation, which is not limited in this embodiment of the present application.

In implementation, the second mapping relation table may be stored in the local storage or the database after being preset. In some embodiments, the second mapping relation table may be obtained from the correspondent node by receiving signaling. In some embodiments, a new or updated second mapping relationship may also be obtained from the correspondent node by receiving a signaling, and the new or updated second mapping relationship is updated to the second mapping relationship table.

Step S704, determining a target IP address corresponding to the identifier of the target first bearer;

step S705, IP packet construction is carried out according to the target IP address and the dead load of the data packet to obtain a reconstructed IP packet;

step S706, according to the identifier of the target first bearer, sending the reconstructed IP packet to an upper layer adjacent to the current layer through the target first bearer.

It should be noted that, in the implementation of the steps S701 and S704 to S706, reference may be made to the implementation of the steps S601 and S603 to S605, which is not described herein again.

An embodiment of the present application provides a routing method, which is executed by a functional entity in a current layer, as shown in fig. 8, and the method includes the following steps:

step S801, in the process of service application, an IP packet channel with a specific identifier is established with a communication opposite end, and data transmitted on the IP packet channel has the same source IP address and destination IP address;

step S802, a third mapping relation table is obtained; the third mapping relation table is used for representing the mapping relation between the identifier of the IP packet channel and the identifier of the second bearer;

here, the third mapping relationship table includes a mapping relationship between the identifier of the at least one IP packet channel and the identifier of the second bearer, that is, a third mapping relationship. In implementation, the third mapping relationship may be obtained by referring to the implementation manner of step S502, and the third mapping relationship is stored in the third mapping relationship table, which is not described herein again.

Step S803, receiving a data packet from a lower layer adjacent to the current layer through a second bearer;

step S804, inquiring the third mapping relation table according to the identifier of the second bearer to obtain the identifier of the target IP packet channel corresponding to the second bearer; the first bearer is an IP packet channel with a specific identifier, and is used for bearer between the current layer and an upper layer adjacent to the current layer;

here, the IP packet tunnel has a specific identifier, and a unique IP packet tunnel can be determined from the identifier. The identifier of the target IP packet channel corresponding to the second bearer may be determined by querying the third mapping relationship table.

Step S805, determining a target IP address corresponding to the identifier of the target first bearer;

step S806, building an IP packet according to the target IP address and the dead load of the data packet to obtain a reconstructed IP packet;

step S807, sending the reconstructed IP packet to the upper layer through the target first bearer according to the identifier of the target first bearer.

It should be noted that, in the implementation of step S801, the embodiment of step S502 may be referred to, and in the implementation of steps S803, S805 to S807, the embodiments of steps S601, S603 to S605 may be referred to, which is not described again here.

In order to reduce processing overhead and processing delay caused by header compression/decompression for each PDCP SDU, embodiments of the present application provide a low-overhead routing method for an IP packet in an AS layer, which provides an IP proxy scheme based on an edge-to-wireless Network in order to meet a design objective of a very simple Network (Lite Network) in next-generation mobile communications. Fig. 9A is a schematic diagram of data transmission when a terminal is simultaneously connected to multiple base stations according to an embodiment of the present application, and AS shown in fig. 9A, when aiming at a next generation very simple network, the embodiment of the present application proposes a User Plane (UP) function, denoted AS UP, of a new definition Layer 3(Layer 3, L3) in an AS Layer _L3 The main function is to process the data of the IP layer. After the UP is defined by L3, the UP of L3 and a Control Plane (CP) (e.g., RRC signaling, etc.) are combined with each other to implement data processing and data routing without an IP header for an IP packet.

In order to better understand the method for routing IP packets at the AS layer provided in the embodiments of the present application, a plurality of functional modules involved in the method, including UP, are described first _L3 Function module, CP function module and UP _L3 An interaction module with the CP, wherein:

UP _L3 the function module is a UP function of L3 newly defined at AS layer, mainly processes data at IP layer, and comprises the following functionsOne of them is:

1) an IP Address resolution and construction function (IP Address server/Constructor, IP _ AP/AC);

here, the function of the IP _ AP/AC includes at least one of the following functions:

(1) IP address resolution function: analyzing a source IP address and a destination IP address carried in an IP packet received from an IP data Flow (IP Flow), generating a low-layer link routing requirement aiming at the IP data Flow, and sending the routing requirement to a CP function entity of L3 to obtain a corresponding low-layer bearer configuration signaling, wherein the low-layer bearer configuration signaling comprises mapping information between the IP data Flow configured by the CP function entity and a low-layer bearer.

Here, UP will be _L3 When sending IP packet to upper layer, the load of load IP packet is recorded as UP IP data flow, and the upper layer is UP _L3 When sending IP packet, the bearer of the IP packet is marked as downlink IP data flow, and the uplink IP data flow and the downlink IP data flow are collectively called IP data flow. The source IP address and the destination IP address of the IP packet carried by the same IP data stream are determined to be invariable, each IP data stream corresponds to one piece of identification information, and the identification information of the IP data stream can be a short identifier. The identification information of the IP data stream occupies less transmission overhead than the source IP address and the destination IP address. During implementation, the corresponding relationship between the identification information of the IP data stream and the source IP address and the destination IP address can be preconfigured, and a configuration information synchronization signaling is sent to the opposite end in a signaling transmission manner, so that the correspondence between the IP data stream identification information configured by the sending end and the receiving end and the source IP address and the destination IP address is kept consistent.

The lower layer link routing requirements include source and destination IP addresses corresponding to the IP data flows.

In some embodiments, for the same IP data stream, only the first IP packet received from the IP data stream needs to be parsed.

(2) A group package function: remove the content related to IP address information of IP packet, take out the dead load (Payload) of IP packet, obtain UP _L3 SDU of (3), adding UP to dead load _L3 Protocol Data Unit (Protocol Data Uni)t, PDU) header information, resulting in UP _L3 PDU packets of (1).

Here, the dead load is information other than the IP header in the IP packet, UP _L3 Protocol data unit header information of (1) for identifying UP _L3 Information of protocol data. In practice, the definition can be self-defined by those skilled in the art according to actual needs. In some embodiments, UP _L3 The pdu header information of (2) may further include identification information corresponding to an IP data stream carrying the IP packet.

(3) IP address information storage function of IP data stream: and storing the IP address information obtained from the IP packet according to the modes of the source IP address and the destination IP address.

Here, the IP address information may be stored in a form of correspondence between identification information of the IP data stream and the source IP address and the destination IP address. In implementation, after the sending end or the receiving end stores the IP address information, the sending end or the receiving end may also send a data synchronization signaling to the opposite end in a signaling transmission manner, so as to ensure that the data of the receiving end and the sending end are consistent. In some embodiments, all the stored IP address information can be synchronized to the opposite end through one signaling transmission, thereby reducing transmission overhead.

(4) IP address reconstruction function: receiving UP from lower layer bearer _L3 After PDU, according to identification information carried by PDU lower layer, obtaining identification information of IP data flow corresponding to PDU data packet, according to identification information of IP data flow, obtaining source IP address and destination IP address of data packet from stored IP address information, using IP address information and UP _L3 The payloads of the PDUs together constitute an IP packet, which is transmitted to an upper layer on an IP data stream.

Here, the identification information carried by the lower layer and the identification information of the IP data stream are associated with each other by a specific mapping relationship. UP _L3 The deadweight of a PDU is UP _L3 The constructed IP packet includes IP address information and UP _L3 The SDU of (1).

(5) Unpacking function: for UP received from lower layer bearer _L3 PDU is analyzed to obtain UP _L3 SDU and UP of _L3 Is an IP address ofStructure function providing UP _L3 And PDU information.

2) Bearer Routing function (Routing).

Here, the bearer routing function is through the UP _L3 And the functional entity can map the IP data flow to the lower layer bearer. The bearer routing function comprises at least one of the following functions:

(1) UP based on configured lower layer link information _L3 The PDU bearer of (a) is sent to the lower layer on the designated lower layer bearer.

(2) And receiving the data packet from the lower layer, carrying the reconstructed IP packet on a correct IP data stream and sending the correct IP data stream to the upper layer.

In the above UP _L3 Among the functions, the protocol functions of the terminal side and the network side are peer-to-peer. UP on the terminal side _L3 UP of the transmitting end corresponding to the network side _L3 UP on the receiving, terminal side _L3 UP of receiving end corresponding to network side _L3 And (5) transmitting the data.

In practice, for UP of terminal side _L3 Can be divided into UP _L3 Or UP _L3 One functional entity has both sending and receiving functions. The functional entity definition of the network side corresponds to the functional entity definition of the terminal side, and when the terminal side is a functional entity, the network side also corresponds to the functional entity; when the terminal side is two functional entities, the network side corresponds to the two functional entities. FIG. 9B shows an embodiment UP of the present application _L3 As shown in fig. 9B, the terminal side is a functional entity, and the network side is a corresponding functional entity. FIG. 9C is a diagram of an embodiment UP of the present application _L3 As shown in fig. 9C, the terminal side is two functional entities, and the network side is also two functional entities correspondingly.

The CP function module of L3 includes a configuration signaling processing function of IP data flow, where CP may be an RRC protocol layer, and the configuration signaling processing function of IP data flow includes:

1) and (3) signaling generation: according to the source and destination IP address information of the IP data stream provided by the IP _ AP/AC function, mapping information with a lower layer bearer is selected and configured for the IP data stream, including identity information of the lower layer bearer, Multiplex (Multiplex) information of the IP data stream on the lower layer bearer, identity identification information of the IP data stream in the lower layer bearer, format or Quality of Service (QoS) guarantee information used when a packet on the IP data stream is received and transmitted on the lower layer bearer, and the like.

Here, the CP may automatically select a usable lower layer bearer for the IP data flow according to the current use condition of the lower layer bearer. On the lower layer bearer, multiple IP data streams may be mapped to the same bearer in a multiplexing manner.

2) And the synchronous configuration is carried out on the opposite terminal in a signaling transmission mode, so that the data transmission link information of the sending terminal and the receiving terminal is ensured to be consistent.

UP _L3 An interaction module with the CP, comprising at least one of the following methods:

1) when a user applies for a service, an IP packet channel is established between a terminal side and a network side, and data transmitted on the channel has the same source IP address and destination IP address.

Fig. 9D is a functional diagram of an end-to-end IP tunnel according to an embodiment of the present application, and as shown in fig. 9D, one IP tunnel corresponds to one IP data flow of the same source IP address and destination IP address.

In some embodiments, an IP tunnel may be carried over one or more lower layer bearers, such as a Radio Bearer (RB).

In some embodiments, multiple IP tunnels may be simultaneously carried on one lower layer bearer, such as one RB.

In some embodiments, a user may have multiple IP tunnels.

2) CP of L3 according to UP _L3 The analyzed IP address information dynamically establishes a mapping relationship between the IP data stream and the lower layer bearer, including establishing or reconfiguring the lower layer bearer, for example, establishing a mapping relationship between a new IP data stream and an RB carrying the IP data stream, or reconfiguring the RB carrying the IP data stream.

Based on the UP _L3 Function module, CP function module and UP _L3 An interaction module with a CP, an embodiment of the present application provides a method for routing an IP packet at an AS layer with low overhead, fig. 9E is a schematic diagram of an implementation flow of the method, and the method is used for data transmission and can be executed by a terminal side or a network side, AS shown in fig. 9E, the method includes the following steps:

step S901, at UP _L3 The layer receives an IP packet from an upper layer through an IP data stream;

step S902, performing UP on the IP packet _L3 Function processing, obtaining UP _L3 The PDU of (1);

here, the UP of the IP packet is described _L3 Function processing, obtaining UP _L3 The PDU of (1), comprising: obtaining identification information of the IP data stream; carrying out IP address resolution on the IP packet to obtain a source IP address and a destination IP address carried in the IP packet; the identification information of the IP data stream is corresponding to a source IP address and a destination IP address carried in the IP packet, and the corresponding relation is stored in a local memory; obtaining the dead load of the IP packet from the IP packet as UP _L3 The SDU of (1); at the UP _L3 Add UP to SDU of _L3 PDU header information of obtaining UP _L3 PDU packets of (1).

Step S903, when the IP packet is the first IP packet received by the IP data stream, through UP _L3 Function processing, mapping the corresponding relation between the IP data stream and the low-layer bearer;

here, the passing UP _L3 Function processing, mapping the corresponding relation between the IP data stream and the low-layer bearer, including: performing IP address resolution on the IP packet to obtain a routing requirement of the IP data stream, wherein the routing requirement comprises a source IP address and a destination IP address; and sending the routing requirement to a CP functional entity of L3 to obtain a corresponding low-layer bearer configuration signaling, where the low-layer bearer configuration signaling includes mapping information between an IP data stream configured by the CP functional entity and a low-layer bearer.

Step S904, determining a target low-layer bearer corresponding to the IP data stream according to the mapping relation between the IP data stream and the low-layer bearer;

step S905, UP _L3 The PDU data packet is loaded on the target lower layer load and sent to the lower layer.

It should be noted that, in implementation, the IP data flow may be a first bearer that is a bearer between a current layer and an upper layer adjacent to the current layer, and the lower layer bearer may be a second bearer that is a bearer between the current layer and a lower layer adjacent to the current layer.

The routing method provided by the embodiment of the application newly defines the UP function of the L3 at the AS layer, introduces the definition of the IP data stream, and completes the processing of the IP packet routing by establishing the mapping between the IP data stream and the low-layer bearer, so that the UP function and the IP data stream are processed at the same time _L3 The PDU data packet does not need to carry the header information of the IP packet any more, and the short PDU header information is adopted to realize data processing and data routing without an IP packet header, thereby reducing the header overhead of the IP packet and realizing the low-overhead transmission of the IP packet in a wireless network. In addition, due to UP _L3 The PDU data packet has no data of an IP packet head, so that the header compression/decompression function of the PDCP layer can be cancelled, thereby solving the problems of increased terminal processing load and power consumption caused by the header compression/decompression of the PDCP layer and increased time delay of data packet processing.

Based on the UP _L3 Function module, CP function module and UP _L3 An interaction module with a CP, an embodiment of the present application provides a method for routing an IP packet at an AS layer with low overhead, fig. 10 is a schematic implementation flow diagram of the method, the method is used for receiving data and can be executed by a terminal side or a network side, AS shown in fig. 10, the method includes the following steps:

step S1001 at UP _L3 The layer receives the data packet from the lower layer through the lower layer bearing;

step S1002, carrying out the de-bearing mapping processing on the data packet to obtain a reconstructed IP packet and determining the identification information of the corresponding IP data stream;

here, the de-bearer mapping process is performed on the data packet to obtain UP _L3 The SDU of (a), comprising: analyzing the data packet to obtain UP _L3 The SDU of (1); based on the identification information carried by the lower layer,determining identification information of an IP data stream corresponding to the data packet; according to the identification information of the IP data stream, obtaining the source IP address and the destination IP address of the data packet from the stored IP address information; using the source IP address, the destination IP address and UP _L3 And the SDU carries out IP packet construction to obtain a reconstructed IP packet.

In some embodiments, UP _L3 The PDU head includes the identification information of IP data flow, correspondingly, the data packet is processed by de-bearing mapping to obtain UP _L3 The SDU of (a), comprising: analyzing the data packet to obtain UP _L3 SDU and PDU headers of (1); determining the identification information of the IP data flow corresponding to the data packet according to the PDU header; according to the identification information of the IP data stream, obtaining the source IP address and the destination IP address of the data packet from the stored IP address information; using the source IP address, the destination IP address and UP _L3 And the SDU carries out IP packet construction to obtain a reconstructed IP packet.

Step S1003, determining a target IP data stream corresponding to the reconstructed IP packet according to the identification information of the IP data stream;

step S1004, the reconstructed IP packet is carried on the target IP data stream and sent to an upper layer.

Based on the foregoing embodiments, an embodiment of the present application provides a routing device, fig. 11 is a schematic structural diagram of the routing device in the embodiment of the present application, and as shown in fig. 11, the routing device 1100 includes a first receiving module 1101, a first packetization module 1102, a first determining module 1103, and a first sending module 1104, where:

the first receiving module 1101 is configured to receive an IP packet from an upper layer adjacent to a current layer through a first bearer; wherein the first bearer is a bearer between the upper layer and the current layer;

the first packet grouping module 1102 is configured to perform packet grouping according to header information of a protocol data unit of a current layer and the IP packet to obtain a protocol data unit of the current layer;

the first determining module 1103 is configured to determine an identifier of a target second bearer corresponding to the first bearer; wherein the second bearer is a bearer between the current layer and a lower layer adjacent to the current layer;

the first sending module 1104 is configured to send the protocol data unit to the lower layer through the target second bearer according to the identifier of the target second bearer.

In some embodiments, the first bearer has a specific identifier, and correspondingly, the routing apparatus further includes: a first mapping module, configured to establish a first mapping relationship between the identifier of the first bearer and the IP address carried in the IP packet; and the first synchronization module is used for synchronizing the first mapping relation to a communication opposite end.

In some embodiments, the first synchronization module is further configured to synchronize the first mapping relationship to a correspondent node through RRC signaling transmission.

In some embodiments, the first bearer has a specific identifier, and correspondingly, the first determining module is further configured to query a second mapping relationship according to the identifier of the first bearer to obtain an identifier of a target second bearer corresponding to the first bearer; wherein the second mapping relationship is used for characterizing a relationship between the identifier of the first bearer and the identifier of the second bearer.

In some embodiments, the first packet grouping module is further configured to perform packet grouping according to header information of a protocol data unit of a current layer and a dead load of the IP packet, so as to obtain the protocol data unit of the current layer.

In some embodiments, the routing device further comprises:

a first configuration module, configured to select and configure a corresponding target second bearer for the first bearer according to an IP address carried in the IP packet before the identifier of the target second bearer corresponding to the first bearer is determined, where the target second bearer has a specific identifier; a second mapping module, configured to establish a second mapping relationship between the identifier of the first bearer and the identifier of the target second bearer; and the second synchronization module is used for synchronizing the second mapping relation to the communication opposite end.

In some embodiments, the routing device comprises a user plane functional entity and a control plane entity, wherein:

the user plane functional entity is configured to send the IP address carried in the IP packet and the identifier of the first bearer to the control plane entity;

the control plane functional entity is configured to: selecting and configuring a target second bearer corresponding to the first bearer according to the IP address and the identifier of the first bearer; wherein the target second bearer has a specific identity; establishing a second mapping relation between the identifier of the first bearer and the identifier of the target second bearer; and synchronizing the second mapping relation to the communication opposite end.

In some embodiments, the second mapping relationship has a specific identification, and the protocol data unit header information includes the identification of the second mapping relationship.

In some embodiments, the first bearer is an IP packet tunnel with a specific identifier, and the routing apparatus further includes a first establishing module, a second configuring module, a third mapping module, and a third synchronizing module, where:

the first establishing module is used for establishing the IP packet channel with a communication opposite end in the service application process, and data transmitted on the IP packet channel has the same source IP address and destination IP address;

the second configuration module is configured to configure a corresponding target second bearer for the IP packet channel, where the target second bearer has a specific identifier;

the third mapping module is configured to establish a third mapping relationship between the identifier of the IP packet channel and the identifier of the target second bearer;

the third synchronization module is configured to synchronize the third mapping relationship to a correspondent node;

correspondingly, the first determining module is further configured to query the third mapping relationship according to the identifier of the IP packet channel, so as to obtain an identifier of a target second bearer corresponding to the first bearer.

An embodiment of the present application provides a routing apparatus, fig. 12 is a schematic structural diagram of a routing apparatus in the embodiment of the present application, and as shown in fig. 12, the routing apparatus 1200 includes a second receiving module 1201, a second determining module 1202, a third determining module 1203, a second packet grouping module 1204, and a second sending module 1205, where:

the second receiving module 1201 is configured to receive a data packet from a lower layer adjacent to a current layer through a second bearer; wherein the second bearer is a bearer between the current layer and the lower layer;

the second determining module 1202 is configured to determine an identifier of a target first bearer corresponding to the second bearer; the first bearer is a bearer between the current layer and an upper layer adjacent to the current layer;

the third determining module 1203 is configured to determine a target IP address corresponding to the identifier of the target first bearer;

the second packet group module 1204 is configured to perform IP packet construction according to the target IP address and the data packet to obtain a reconstructed IP packet;

the second sending module 1205 is configured to send the reconstructed IP packet to the upper layer through the target first bearer according to the identifier of the target first bearer.

In some embodiments, the third determining module is further configured to query a specific first mapping relationship table according to the identifier of the target first bearer to obtain a target IP address corresponding to the identifier of the target first bearer; the first mapping relation table is used for representing the mapping relation between the identifier of the first bearer and the IP address.

In some embodiments, the second bearer has a specific identifier, and correspondingly, the second determining module is further configured to query a specific second mapping relationship table according to the identifier of the second bearer to obtain an identifier of a target first bearer corresponding to the second bearer; and the second mapping relation table is used for representing the mapping relation between the identifier of the first bearer and the identifier of the second bearer.

In some embodiments, the second determination module is further configured to: analyzing the data packet to obtain an identifier of a second mapping relation in protocol data unit header information of the data packet; inquiring a specific second mapping relation table according to the identifier of the second mapping relation to obtain the identifier of the target first bearer corresponding to the second bearer; the second mapping relation table is used for representing a mapping relation between the identifier of the first bearer and the identifier of the second bearer, and each second mapping relation in the second mapping relation table has a specific identifier.

In some embodiments, the first bearer is an IP packet tunnel with a specific identifier, and the routing apparatus further includes a second establishing module and a third receiving module, where:

the second establishing module is used for establishing the IP packet channel with the opposite communication terminal in the service application process, and the data transmitted on the IP packet channel has the same source IP address and destination IP address;

the third receiving module is used for obtaining a third mapping relation table from the communication opposite end through signaling receiving; the third mapping relation table is used for representing the mapping relation between the identifier of the IP packet channel and the identifier of the second bearer;

correspondingly, the second determining module is further configured to query the third mapping relation table according to the identifier of the second bearer, so as to obtain the identifier of the target IP packet channel corresponding to the second bearer.

The above description of the embodiment of the routing device is similar to the description of the embodiment of the method, and has similar beneficial effects as the embodiment of the method. For technical details not disclosed in the embodiments of the routing device of the present application, refer to the description of the embodiments of the method of the present application for understanding.

It should be noted that, in the embodiment of the present application, if the routing method is implemented in the form of a software functional module and sold or used as a standalone product, the routing method may also be stored in a computer-readable storage medium. Based on such understanding, the technical solutions of the embodiments of the present application or portions thereof that contribute to the related art may be embodied in the form of a software product, where the computer software product is stored in a storage medium and includes several instructions for enabling a routing device to execute all or part of the methods described in the embodiments of the present application. And the aforementioned storage medium includes: various media capable of storing program codes, such as a usb disk, a removable hard disk, a Read Only Memory (ROM), a magnetic disk, or an optical disk. Thus, embodiments of the present application are not limited to any specific combination of hardware and software.

Correspondingly, the embodiment of the present application provides a computer-readable storage medium, on which a computer program is stored, and the computer program realizes the steps of the above method when being executed by a processor.

Correspondingly, an embodiment of the present application provides a routing device, which includes a memory and a processor, where the memory stores a computer program that can be run on the processor, and the processor implements the steps in the above method when executing the program.

Here, it should be noted that: the above description of the storage medium and device embodiments is similar to the description of the method embodiments above, with similar advantageous effects as the method embodiments. For technical details not disclosed in the embodiments of the storage medium and apparatus of the present application, reference is made to the description of the embodiments of the method of the present application for understanding.

It should be noted that fig. 13 is a schematic diagram of a hardware entity of a routing device in an embodiment of the present application, and as shown in fig. 13, the hardware entity of the device 1300 includes: a processor 1301, a communication interface 1302, and a memory 1303, wherein

The processor 1301 generally controls the overall operation of the device 1300.

The communication interface 1302 may enable the device to communicate with other terminals or servers over a network.

The Memory 1303 is configured to store instructions and applications executable by the processor 1301, and may also cache data to be processed or already processed by the processor 1301 and modules in the device 1300, and may be implemented by a FLASH Memory (FLASH) or a Random Access Memory (RAM).

It should be appreciated that reference throughout this specification to "one embodiment" or "an embodiment" means that a particular feature, structure or characteristic described in connection with the embodiment is included in at least one embodiment of the present application. Thus, the appearances of the phrases "in one embodiment" or "in an embodiment" in various places throughout this specification are not necessarily all referring to the same embodiment. Furthermore, the particular features, structures, or characteristics may be combined in any suitable manner in one or more embodiments. It should be understood that, in the various embodiments of the present application, the sequence numbers of the above-mentioned processes do not mean the execution sequence, and the execution sequence of each process should be determined by its function and inherent logic, and should not constitute any limitation to the implementation process of the embodiments of the present application. The above-mentioned serial numbers of the embodiments of the present application are merely for description and do not represent the merits of the embodiments.

It should be noted that, in this document, the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising an … …" does not exclude the presence of other like elements in a process, method, article, or apparatus that comprises the element.

In the several embodiments provided in the present application, it should be understood that the disclosed apparatus and method may be implemented in other ways. The above-described device embodiments are merely illustrative, for example, the division of the unit is only a logical functional division, and there may be other division ways in actual implementation, such as: multiple units or components may be combined, or may be integrated into another system, or some features may be omitted, or not implemented. In addition, the coupling, direct coupling or communication connection between the components shown or discussed may be through some interfaces, and the indirect coupling or communication connection between the devices or units may be electrical, mechanical or other forms.

The units described as separate parts may or may not be physically separate, and parts displayed as units may or may not be physical units; can be located in one place or distributed on a plurality of network units; some or all of the units can be selected according to actual needs to achieve the purpose of the solution of the embodiment.

In addition, all functional units in the embodiments of the present application may be integrated into one processing unit, or each unit may be separately regarded as one unit, or two or more units may be integrated into one unit; the integrated unit may be implemented in the form of hardware, or in the form of hardware plus a software functional unit.

Those of ordinary skill in the art will understand that: all or part of the steps for realizing the method embodiments can be completed by hardware related to program instructions, the program can be stored in a computer readable storage medium, and the program executes the steps comprising the method embodiments when executed; and the aforementioned storage medium includes: various media that can store program codes, such as a removable Memory device, a Read Only Memory (ROM), a magnetic disk, or an optical disk.

Alternatively, the integrated unit described above may be stored in a computer-readable storage medium if it is implemented in the form of a software functional module and sold or used as a separate product. Based on such understanding, the technical solutions of the embodiments of the present application may be essentially implemented or portions thereof contributing to the related art may be embodied in the form of a software product stored in a storage medium, and including several instructions for enabling a computer device (which may be a personal computer, a server, or a network device) to execute all or part of the methods described in the embodiments of the present application. And the aforementioned storage medium includes: a removable storage device, a ROM, a magnetic or optical disk, or other various media that can store program code.

The above description is only an embodiment of the present application, but the scope of the present application is not limited thereto, and any person skilled in the art can easily think of the changes or substitutions within the technical scope of the present application, and shall cover the scope of the present application. Therefore, the protection scope of the present application shall be subject to the protection scope of the claims.

Claims

1. A routing method, performed by a functional entity of a current layer, the current layer being a layer 3L3 newly defined at an access stratum AS, comprising:

receiving an IP packet from an upper layer adjacent to the current layer through a first bearer; the first bearer is a bearer between the upper layer and the current layer, the first bearer is an IP packet channel with a specific identifier, and data transmitted on the IP packet channel has the same source IP address and destination IP address;

sending the protocol data unit to the lower layer through the target second bearer according to the identifier of the target second bearer;

wherein the determining the identifier of the target second bearer corresponding to the first bearer comprises: inquiring a third mapping relation according to the identifier of the IP packet channel to obtain an identifier of a target second bearer corresponding to the first bearer; and the third mapping relation is used for representing the corresponding relation between the identifier of the IP packet channel and the identifier of the second bearer.

2. The method of claim 1, further comprising:

establishing a first mapping relation between the identifier of the first bearer and the IP address carried in the IP packet;

and synchronizing the first mapping relation to a communication opposite end.

3. The method of claim 2, wherein synchronizing the first mapping relationship to the correspondent node comprises:

and synchronizing the first mapping relation to a communication opposite end through RRC signaling transmission.

4. The method of claim 1, wherein the first bearer has a specific identity; correspondingly, the determining the identifier of the target second bearer corresponding to the first bearer includes:

inquiring a second mapping relation according to the identifier of the first bearer to obtain an identifier of a target second bearer corresponding to the first bearer; wherein the second mapping relationship is used for characterizing a relationship between the identifier of the first bearer and the identifier of the second bearer.

5. The method of claim 4, wherein prior to the determining the identity of the target second bearer to which the first bearer corresponds, the method further comprises:

selecting and configuring a corresponding target second bearer for the first bearer according to the IP address carried in the IP packet, wherein the target second bearer has a specific identifier;

establishing a second mapping relation between the identifier of the first bearer and the identifier of the target second bearer;

and synchronizing the second mapping relation to the communication opposite end.

6. The method of claim 4, wherein the functional entities of the current layer comprise a control plane entity and a user plane entity; correspondingly, before the determining the identifier of the target second bearer corresponding to the first bearer, the method further includes:

the user plane entity sends the IP address carried in the IP packet and the identifier of the first bearer to the control plane entity;

the control plane entity selects and configures a target second bearer corresponding to the first bearer according to the IP address and the identifier of the first bearer; wherein the target second bearer has a specific identity;

the control plane entity establishes a second mapping relation between the identifier of the first bearer and the identifier of the target second bearer;

and the control plane entity synchronizes the second mapping relation to a communication opposite end.

7. The method of claim 4, wherein the second mapping relationship has a specific identification, and wherein the protocol data unit header information comprises the identification of the second mapping relationship.

8. The method of claim 1, wherein prior to said receiving the IP packet from the upper layer over the first bearer, the method further comprises:

in the service application process, establishing the IP packet channel with a communication opposite terminal;

selecting and configuring a corresponding target second bearer for the IP packet channel, wherein the target second bearer has a specific identifier;

establishing a third mapping relation between the identifier of the IP packet channel and the identifier of the target second bearer;

and synchronizing the third mapping relation to a communication opposite end.

9. The method of claim 1, wherein the performing packet construction according to the header information of the current-layer protocol data unit and the IP packet to obtain the current-layer protocol data unit comprises:

and constructing a data packet according to the header information of the protocol data unit of the current layer and the dead load of the IP packet to obtain the protocol data unit of the current layer.

10. A routing method, performed by a functional entity of a current layer, the current layer being a layer 3L3 newly defined at an access stratum AS, comprising:

receiving a data packet from a lower layer adjacent to the current layer through a second bearer; the second bearer is a bearer between the current layer and the lower layer, the second bearer is an IP packet channel with a specific identifier, and data transmitted on the IP packet channel has the same source IP address and destination IP address;

determining a target IP address corresponding to the identifier of the target first bearer;

sending the reconstructed IP packet to the upper layer through the target first bearer according to the identifier of the target first bearer;

wherein the determining the identifier of the target first bearer corresponding to the second bearer comprises: inquiring a third mapping relation table according to the identifier of the second bearer to obtain the identifier of a target IP packet channel corresponding to the second bearer; and the third mapping relation is used for representing the corresponding relation between the identifier of the IP packet channel and the identifier of the second bearer.

11. The method of claim 10, wherein the determining the target IP address corresponding to the target first bearer identity comprises:

inquiring a specific first mapping relation table according to the identifier of the target first bearer to obtain a target IP address corresponding to the identifier of the target first bearer; the first mapping relation table is used for representing the mapping relation between the identifier of the first bearer and the IP address.

12. The method of claim 10, wherein the determining the identity of the target first bearer corresponding to the second bearer comprises:

inquiring a specific second mapping relation table according to the identifier of the second bearer to obtain the identifier of a target first bearer corresponding to the second bearer; the second mapping relation table is used for representing the mapping relation between the identifier of the first bearer and the identifier of the second bearer.

13. The method of claim 10,

the determining the identifier of the target first bearer corresponding to the second bearer includes:

analyzing the data packet to obtain an identifier of a second mapping relation in protocol data unit header information of the data packet;

inquiring a specific second mapping relation table according to the identifier of the second mapping relation to obtain the identifier of the target first bearer corresponding to the second bearer; the second mapping relation table is used for characterizing a mapping relation between the identifier of the first bearer and the identifier of the second bearer, and each second mapping relation in the second mapping relation table has a specific identifier.

14. The method of claim 10, wherein prior to the determining the identity of the target first bearer to which the second bearer corresponds, the method further comprises:

and obtaining a third mapping relation table from the communication opposite end through signaling receiving.

15. A routing device, comprising:

a first receiving module, configured to receive, through a first bearer, an IP packet from an upper layer adjacent to a current layer; the first bearer is a bearer between the upper layer and the current layer, the first bearer is an IP packet channel with a specific identifier, data transmitted on the IP packet channel has the same source IP address and destination IP address, and the current layer is layer 3L3 newly defined in an Access Stratum (AS);

a first sending module, configured to send the pdu to the lower layer through the target second bearer according to the identifier of the target second bearer;

the first determining module is further configured to query a third mapping relationship according to the identifier of the IP packet channel, so as to obtain an identifier of a target second bearer corresponding to the first bearer; and the third mapping relation is used for representing the corresponding relation between the identifier of the IP packet channel and the identifier of the second bearer.

16. A routing device, comprising:

a second receiving module, configured to receive, through a second bearer, a data packet from a lower layer adjacent to a current layer; the second bearer is a bearer between the current layer and the lower layer, the second bearer is an IP packet channel with a specific identifier, data transmitted on the IP packet channel has the same source IP address and destination IP address, and the current layer is layer 3L3 newly defined in an access stratum AS;

a second sending module, configured to send the reconstructed IP packet to the upper layer through the target first bearer according to the identifier of the target first bearer;

the second determining module is further configured to query a third mapping relation table according to the identifier of the second bearer, so as to obtain an identifier of a target IP packet channel corresponding to the second bearer; and the third mapping relation is used for representing the corresponding relation between the identifier of the IP packet channel and the identifier of the second bearer.

17. A routing device comprising a processor and a memory, said memory storing a computer program operable on the processor, wherein said processor when executing said program performs the steps of the method of any of claims 1 to 14.

18. A computer-readable storage medium, on which a computer program is stored which, when being executed by a processor, carries out the steps of the method of any one of claims 1 to 14.