Communication method, and device, system and storage medium

Abstract

The embodiments of the present disclosure relate to the technical field of communications. Disclosed are a communication method and apparatus, and a computer-readable storage medium. The communication method comprises: receiving data packets; on the basis of first information, determining first address information corresponding to a first data packet among the data packets, and using the first address information to process a second data packet, wherein the first address information is used for identifying source address information of the first data packet, and the second data packet is a data packet associated with the first data packet. By means of configured first information, first address information corresponding to a first data packet among received data packets can be determined, and the first address is used to process a second data packet associated with the first data packet, and the first address information identifies source address information of the first data packet, such that session management of a terminal that accesses a network by means of an MWAB can be supported.

Description

Communication method, device, system and storage medium TECHNICAL FIELD

[0001] The present disclosure relates to the technical field of communication, and in particular, the present disclosure relates to a communication method, device, system and storage medium. BACKGROUND

[0002] Mobile gNB with wireless access backhaul (MWAB) refers to a mobile base station acting as a next generation base station (gNB) for other terminals and providing access to a network (such as a 5th generation mobile communication system (5G) network), i.e., the MWAB provides a 5G new radio (NR) access link for the terminal and uses an NR wireless connection to a 5G core (5GC) through an Internet Protocol (IP) connection (i.e., a backhaul path) provided by a protocol data unit (PDU) session. The protocol data unit session for establishing the backhaul path can be referred to as a backhaul protocol data unit (BH PDU) session. The BH PDU session is established through an NG-RAN cell in which the mobile base station can reside. The BH PDU session can be provided by a terrestrial network or a non-terrestrial network. Such a mobile base station can be installed on a moving vehicle and provide services for users inside or outside (or entering / leaving the vehicle).

[0003] SUMMARY

[0004] The present disclosure provides a communication method, device, system and storage medium.

[0005] In a first aspect, a communication method is provided, the method is performed by a first network function, and the method comprises:

[0006] receiving a data packet;

[0007] determining first address information corresponding to a first data packet in the data packet according to first information, and using the first address information for processing of a second data packet;

[0008] The first address information is used to identify source address information of the first data packet, and the second data packet is a data packet associated with the first data packet.

[0009] In a second aspect, a communication method is provided. The method is performed by a second network function, and the method comprises:

[0010] sending first information to a first network function;

[0011] wherein the first information is used to determine first address information corresponding to a first data packet in data packets received by the first network function, and to determine that the first address information is used for processing of a second data packet;

[0012] wherein the first address information is used to identify source address information of the first data packet; and the second data packet is a data packet associated with the first data packet.

[0013] In a third aspect, a first network function is provided. The first network function comprises:

[0014] a first transceiver configured to receive data packets;

[0015] a first processing module configured to determine first address information corresponding to a first data packet in the data packets according to first information, and to use the first address information for processing of a second data packet;

[0016] wherein the first address information is used to identify source address information of the first data packet; and the second data packet is a data packet associated with the first data packet.

[0017] In a fourth aspect, a second network function is provided. The second network function comprises:

[0018] a second transceiver configured to send first information to a first network function;

[0019] wherein the first information is used to determine first address information corresponding to a first data packet in data packets received by the first network function, and to determine that the first address information is used for processing of a second data packet;

[0020] wherein the first address information is used to identify source address information of the first data packet; and the second data packet is a data packet associated with the first data packet.

[0021] In a fifth aspect, a communication apparatus is provided. The apparatus comprises:

[0022] one or more processors;

[0023] wherein the processor is configured to perform the optional implementation of the first aspect.

[0024] In a sixth aspect, a communication apparatus is provided. The apparatus comprises:

[0025] one or more processors;

[0026] The processor is configured to execute the optional implementation of the second aspect.

[0027] According to a seventh aspect of the embodiments of the present disclosure, a communication system is provided, comprising a first network function and a second network function, wherein the first network function is configured to implement the method described in the first aspect, and the second network function is configured to implement the method described in the second aspect.

[0028] The first network function receives a data packet and first information sent by the second network function.

[0029] The first network function determines first address information corresponding to a first data packet in the data packet according to the first information, and uses the first address information for processing of a second data packet.

[0030] The first address information is used to identify source address information of the first data packet, and the second data packet is a data packet associated with the first data packet.

[0031] According to an eighth aspect of the embodiments of the present disclosure, a communication system is provided, comprising a first network function and a second network function, wherein the first network function is configured to implement the method described in the optional implementation of the first aspect, and the second network function is configured to implement the method described in the optional implementation of the second aspect.

[0032] According to a ninth aspect of the embodiments of the present disclosure, a computer readable storage medium is provided, which stores executable instructions. The executable instructions are loaded and executed by the processor to implement the method described in the optional implementation of the first aspect or the second aspect or the third aspect.

[0033] It should be understood that the above general description and the following detailed description are only exemplary and explanatory, and cannot limit the present disclosure. BRIEF DESCRIPTION OF DRAWINGS

[0034] The accompanying drawings, which are incorporated into the specification and constitute part of the specification, illustrate embodiments consistent with the present disclosure and, together with the specification, serve to explain the principles of the present disclosure.

[0035] FIG. 1a is a schematic diagram of a structure of a wireless communication system according to an exemplary embodiment;

[0036] FIG. 1b is a schematic diagram of a structure of a wireless communication system according to an exemplary embodiment;

[0037] FIG. 1c is a flow diagram of a session management according to an exemplary embodiment;

[0038] FIG. 2 is a flow diagram of a communication method according to an exemplary embodiment;

[0039] FIG. 3a is a flow diagram illustrating a communication method according to an example embodiment of the present disclosure;

[0040] FIG. 3b is a flow diagram illustrating a communication method according to an example embodiment of the present disclosure;

[0041] FIG. 4 is a flow diagram illustrating a communication method according to an example embodiment of the present disclosure;

[0042] FIG. 5 is a flow diagram illustrating a communication method according to an example embodiment of the present disclosure;

[0043] FIG. 6a is a schematic diagram illustrating a structure of a first network function according to an example embodiment of the present disclosure;

[0044] FIG. 6b is a schematic diagram illustrating a structure of a second network function according to an example embodiment of the present disclosure;

[0045] FIG. 7 is a flow diagram illustrating a communication method according to an example embodiment of the present disclosure;

[0046] FIG. 8a is a schematic diagram illustrating a structure of a communication device according to an example embodiment of the present disclosure;

[0047] FIG. 8b is a schematic diagram illustrating a structure of a chip according to an example embodiment of the present disclosure. DETAILED DESCRIPTION

[0048] The present disclosure provides a communication method, a communication device, a communication system, and a storage medium.

[0049] In a first aspect, the present disclosure provides a communication method, which is performed by a first network function, and the method comprises:

[0050] receiving a data packet;

[0051] determining first address information corresponding to a first data packet in the data packet according to first information, and using the first address information for processing of a second data packet;

[0052] The first address information is used to identify source address information of the first data packet, and the second data packet is a data packet associated with the first data packet.

[0053] In the above embodiment, the first address information corresponding to a first data packet in the received data packet can be determined according to the first information, and the first address information is used for processing of a second data packet associated with the first data packet. The first address information identifies the source address information of the first data packet, thereby supporting session management of a terminal accessing a network via a MWAB.

[0054] In some embodiments combined with the first aspect, in some embodiments, the using the first address information for processing of the second data packet comprises encapsulating the second data packet using the first address information.

[0055] In the above embodiments, the processing rule of the data packet of the session of the terminal accessing the network via the MWAB configured by the second network function, so that the correct transmission of the data packet of the session of the terminal accessing the network via the MWAB can be realized.

[0056] In some embodiments combined with the first aspect, in some embodiments, the first data packet is an uplink user plane data packet transmitted to the first network function via a backhaul path, and the second data packet is a downlink user plane data packet belonging to a same packet data unit (PDU) session as the first data packet.

[0057] In some embodiments combined with the first aspect, in some embodiments, the PDU session is a PDU session of a first terminal accessing the first network function via a first node, and the PDU session is a first session.

[0058] The backhaul path is a user plane path of a second session, and the second session is a PDU session providing a backhaul path for a terminal part included by the first node.

[0059] In the above embodiments, the first data packet of the session transmitted via the backhaul path, the second data packet associated with the first data packet is determined, and the address of the first data packet is used for transmission of the second data packet, so that the correct transmission of the data packet of the session of the terminal accessing the network via the MWAB can be realized.

[0060] In some embodiments combined with the first aspect, in some embodiments, the address information comprises an IP address and / or a port number.

[0061] In some embodiments combined with the first aspect, in some embodiments, the first address information comprises one of the following:

[0062] Source address information of the initial first data packet;

[0063] Source address information of the first data packet after the address information of the terminal part providing the backhaul path is changed.

[0064] In some embodiments combined with the first aspect, in some embodiments, the first address information corresponding to the packet;

[0065] The second data packet associated with the first data packet;

[0066] Whether the first address information is used for processing of the second data packet;

[0067] process the second data packet using the first address information.

[0068] In the above embodiment, by configuring the detection condition and processing condition of the received data packet, the source address information of the first data packet meeting the detection condition can be accurately obtained, and the source address information is used for processing the second data packet.

[0069] In some embodiments of the first aspect, the determining whether the received data packet is the first data packet comprises:

[0070] determining whether the received data packet is the first data packet based on the first tunnel information; or

[0071] determining whether the received data packet is the first data packet based on second information configured or negotiated between the first node and the second network function.

[0072] In the above embodiment, by taking the tunnel information or the information negotiated between the first node and the second network function as the detection condition, the first data packet meeting the detection condition can be accurately obtained.

[0073] In some embodiments of the first aspect, the first tunnel information comprises user plane tunnel information associated with the first network function corresponding to the first session.

[0074] In the above embodiment, by taking the user plane tunnel information associated with the first network function of the PDU session of the first terminal accessing the network through the first node as the detection condition, the first data packet meeting the detection condition can be accurately obtained.

[0075] In some embodiments of the first aspect, the second information comprises at least one of:

[0076] a connection identifier of a user plane connection of the first session;

[0077] an identifier of a first terminal of the first session;

[0078] specific indication information for indicating a user plane connection between the first node and the first network function of the first session;

[0079] specific identification information for identifying a user plane connection between the first node and the first network function of the first session.

[0080] In some embodiments of the first aspect, the first data packet comprises at least one of:

[0081] a user data packet of a first terminal accessing the network through the first node;

[0082] a specific data packet, the specific data packet being generated by the first node.

[0083] In the above embodiment, the first data packet can be a user data packet of a first terminal accessing the network via the first node, or, in the case where no user data packet of the first terminal is received, a specific data packet generated by the first node, so that the process of the first terminal accessing the network via the first node can be triggered flexibly.

[0084] In combination with some embodiments of the first aspect, in some embodiments, the specific data packet comprises at least one of:

[0085] a user plane signaling message of a specific tunneling protocol;

[0086] an empty user plane message of a tunneling protocol.

[0087] In combination with some embodiments of the first aspect, in some embodiments, the method further comprises:

[0088] obtaining, by the first node, the first information sent by the second network function through a first request message, the first request message being used for managing a user plane path of a packet data unit (PDU) session of a first terminal accessing a network via the first node.

[0089] In the above embodiment, the first information is sent to the first network function through the request message used for managing the user plane path of the PDU session of the first terminal accessing the network via the first node, so that the deployment mode of the network system can be better adapted.

[0090] In combination with some embodiments of the first aspect, in some embodiments, the method further comprises:

[0091] determining the first data packet and the second data packet based on the first information.

[0092] In the above embodiment, after obtaining the processing rule for the first data packet and the second data packet associated with the first data packet, the first data packet and the second data packet that meet the processing rule can be determined from the received data packets, so as to obtain the first address information of the first data packet, and the first address information is used for processing of the second data packet, thereby realizing transmission of the data packets of the PDU session of the first terminal.

[0093] In combination with some embodiments of the first aspect, in some embodiments, the first node is a mobile base station with wireless backhaul, the first node comprises a base station part of the mobile base station with wireless backhaul, and / or a terminal part of the mobile base station with wireless backhaul.

[0094] In a second aspect, the embodiments of the present disclosure provide a communication method, the method being performed by a second network function, the method comprising:

[0095] sending first information to a first network function;

[0096] wherein the first information is used to determine first address information corresponding to a first data packet in data packets received by the first network function, and to determine that the first address information is used for processing of a second data packet;

[0097] wherein the first address information is used to identify source address information of the first data packet; and the second data packet is a data packet associated with the first data packet.

[0098] In some embodiments of the second aspect, in some embodiments, the second data packet is encapsulated using the first address information.

[0099] In some embodiments of the second aspect, in some embodiments, the first data packet is an uplink user plane data packet transmitted to the first network function via a backhaul path;

[0100] the second data packet is a downlink user plane data packet belonging to a same packet data unit (PDU) session as the first data packet.

[0101] In some embodiments of the second aspect, in some embodiments, the PDU session is a PDU session of a first terminal accessing the first network function via a first node, and the PDU session is a first session.

[0102] the backhaul path is a user plane path of a second session, and the second session is a PDU session providing a backhaul path for a terminal part included in the first node.

[0103] In some embodiments of the second aspect, in some embodiments, the address information includes an IP address and / or a port number.

[0104] In some embodiments of the second aspect, in some embodiments, the first address information includes one of:

[0105] source address information of the first data packet;

[0106] source address information of the first data packet after address information of the terminal part providing the backhaul path is changed.

[0107] In some embodiments of the second aspect, in some embodiments, the first information is used to determine at least one of:

[0108] whether the received data packet is the first data packet;

[0109] compliance with the first address information corresponding to the first data packet;

[0110] the second data packet associated with the first data packet;

[0111] whether the first address information is used for processing of the second data packet;

[0112] processing the second data packet using the first address information.

[0113] In some embodiments of the second aspect, the determining whether the received data packet is the first data packet comprises:

[0114] determining whether the received data packet is the first data packet based on first tunnel information; or

[0115] determining whether the received data packet is the first data packet based on second information configured or negotiated between the first node and the second network function.

[0116] In some embodiments of the second aspect, the first tunnel information comprises user plane tunnel information associated with the first network function corresponding to the first session.

[0117] In some embodiments of the second aspect, the second information comprises at least one of:

[0118] a connection identifier of a user plane connection of the first session;

[0119] an identifier of a first terminal of the first session;

[0120] specific indication information indicating a user plane connection between the first node and the first network function of the first session;

[0121] specific identification information identifying a user plane connection between the first node and the first network function of the first session.

[0122] In some embodiments of the second aspect, the first data packet comprises at least one of:

[0123] a user data packet of a first terminal accessing the network via the first node;

[0124] a specific data packet generated by the first node.

[0125] In some embodiments of the second aspect, the specific data packet comprises at least one of:

[0126] a user plane signaling message of a specific tunnel protocol;

[0127] a user plane message of an empty tunnel protocol.

[0128] In some embodiments of the second aspect, the first information sent to the first network function comprises:

[0129] The first information is sent to the first network function through a first request message, and the first request message is used to manage a user plane path of the first session.

[0130] In some embodiments of the second aspect, the first node is a mobile base station with wireless backhaul, the first node comprises a base station part of the mobile base station with wireless backhaul, and / or the first node comprises a terminal part with wireless backhaul.

[0131] In a third aspect, the embodiments of the present disclosure provide a first network function, comprising:

[0132] A first transceiver module, configured to receive a data packet;

[0133] A first processing module, configured to determine first address information corresponding to a first data packet in the data packet according to first information, and use the first address information for processing of a second data packet;

[0134] The first address information is used to identify source address information of the first data packet; and the second data packet is a data packet associated with the first data packet.

[0135] In a fourth aspect, the embodiments of the present disclosure provide a second network function, comprising:

[0136] A second transceiver module, configured to send first information to a first network function;

[0137] The first information is used to determine first address information corresponding to a first data packet in a data packet received by the first network function, and to determine that the first address information is used for processing of a second data packet.

[0138] The first address information is used to identify source address information of the first data packet; and the second data packet is a data packet associated with the first data packet.

[0139] In a fifth aspect, the embodiments of the present disclosure provide a communication apparatus, comprising:

[0140] One or more processors;

[0141] The processor is configured to execute the optional implementation of the first aspect.

[0142] In a sixth aspect, the embodiments of the present disclosure provide a communication apparatus, comprising:

[0143] One or more processors;

[0144] The processor is configured to perform the optional implementation of the second aspect.

[0145] In a seventh aspect, the embodiments of the present disclosure provide a communication system, comprising a first network function and a second network function, wherein,

[0146] The first network function receives a data packet and first information sent by the second network function;

[0147] The first network function determines first address information corresponding to a first data packet in the data packet according to the first information, and uses the first address information for processing of a second data packet;

[0148] The first address information is used to identify source address information of the first data packet; and the second data packet is a data packet associated with the first data packet.

[0149] In combination with some embodiments of the seventh aspect, in some embodiments, the first network function encapsulates the second data packet using the first address information.

[0150] In an eighth aspect, the embodiments of the present disclosure provide a communication system, comprising a first network function and a second network function, wherein the first network function is configured to implement the method described in the optional implementation of the first aspect, and the second network function is configured to implement the method described in the optional implementation of the second aspect.

[0151] In a ninth aspect, the embodiments of the present disclosure provide a computer readable storage medium, wherein the computer readable storage medium stores executable instructions, and the executable instructions are loaded and executed by a processor to implement the method described in the optional implementation of the first aspect or the second aspect.

[0152] In a tenth aspect, the embodiments of the present disclosure provide a program product, which, when executed by a communication device, causes the communication device to perform the method described in the optional implementation of the first aspect or the second aspect.

[0153] In an eleventh aspect, the embodiments of the present disclosure provide a computer program, which, when executed on a computer, causes the computer to perform the method described in the optional implementation of the first aspect or the second aspect.

[0154] In a twelfth aspect, the embodiments of the present disclosure provide a chip or chip system, which comprises processing circuitry configured to perform the method described in the optional implementation of the first aspect or the second aspect.

[0155] It can be understood that the apparatus for random access, the communication device, the communication system, the storage medium, the program product, and the computer program described above are used to execute the method proposed in the embodiments of the present disclosure. Therefore, the beneficial effects achieved by the above apparatuses can refer to the beneficial effects of the corresponding method, which will not be described here. The communication device can be a terminal or a network device.

[0156] The embodiments of the present disclosure propose a communication method, an apparatus, a communication device, a communication system, and a storage medium.

[0157] In some embodiments, the communication method and the information processing method can be replaced with each other, the apparatus for random access and the information processing apparatus can be replaced with each other, and the information processing system and the communication system can be replaced with each other.

[0158] The embodiments of the present disclosure are not exhaustive, but only illustrate some embodiments, and are not specific limitations on the protection scope of the embodiments of the present disclosure. In the case of no contradiction, each step in an embodiment can be implemented as an independent embodiment, and the steps can be combined arbitrarily, for example, the scheme after removing some steps in an embodiment can also be implemented as an independent embodiment, and the order of the steps in an embodiment can be exchanged arbitrarily, in addition, the optional implementation manners in an embodiment can be combined arbitrarily; in addition, the embodiments can be combined arbitrarily, for example, the steps of different embodiments or part of the steps of different embodiments can be combined arbitrarily, an embodiment can be combined with the optional implementation manners of other embodiments.

[0159] In the embodiments of the present disclosure, the terms and / or descriptions between the embodiments are consistent and can be referred to each other if there is no special description and logical conflict, and the technical features in different embodiments can be combined to form new embodiments according to their inherent logical relationship.

[0160] The terms used in the embodiments of the present disclosure are only for the purpose of describing specific embodiments, and not as a limitation on the embodiments of the present disclosure.

[0161] In the embodiments of the present disclosure, unless otherwise specified, the elements expressed in singular form, such as “one”, “a”, “the”, “above”, “said”, “preceding”, “this” and the like, can represent “one and only one”, or “one or more”, “at least one” and the like. For example, in the case of using articles such as “a”, “an”, “the” and the like in English, the noun after the article can be understood as singular expression, or as plural expression.

[0162] In the embodiments of the present disclosure, “a plurality of” means two or more.

[0163] In some embodiments, the terms “at least one of,” “at least one of,” “at least one of,” “one or more,” “a plurality of,” “multiple,” and the like can be replaced with each other.

[0164] In the description of the embodiments of the present disclosure, the description modes such as “at least one of A, B, and C”, “A and / or B and / or C”, and the like include any one of A, B, and C existing alone, and also include any combination of any number of A, B, and C, and each case can exist alone; for example, “at least one of A, B, and C” includes a case of A alone, a case of B alone, a case of C alone, a case of a combination of A and B, a case of a combination of A and C, a case of a combination of B and C, and a case of a combination of A and B and C; for example, A and / or B includes a case of A alone, a case of B alone, and a case of a combination of A and B.

[0165] In some embodiments, the description modes such as “A in a case, B in another case”, “in response to a case A, in response to another case B”, and the like can include the following technical solutions according to the cases: A is executed regardless of B, that is, A in some embodiments; B is executed regardless of A, that is, B in some embodiments; A and B are selectively executed, that is, A and B are selected from A and B to be executed in some embodiments; A and B are both executed, that is, A and B in some embodiments. When there are more branches of A, B, C, and the like, it is similar to the above.

[0166] The prefix words of "first", "second" and the like in the embodiments of the present disclosure are merely used to distinguish different description objects, and do not constitute limitation on the position, order, priority, quantity or content of the description objects. The description objects are described in the claims or embodiments, and should not be construed as redundant limitation because of the use of the prefix words. For example, the description object is "field", and the ordinal words before "field" in "first field" and "second field" do not limit the position or order between "fields", and "first" and "second" do not limit whether the "fields" modified thereby are in the same message or not, nor limit the order of "first field" and "second field". For another example, the description object is "level", and the ordinal words before "level" in "first level" and "second level" do not limit the priority between "levels". For another example, the quantity of the description object is not limited by the ordinal words, and can be one or more. For example, "first device", wherein the quantity of "device" can be one or more. In addition, the objects modified by different prefix words can be the same or different, for example, the description object is "device", and "first device" and "second device" can be the same device or different devices, and the types thereof can be the same or different. For another example, the description object is "information", and "first configuration" and "second configuration" can be the same information or different information, and the contents thereof can be the same or different.

[0167] In some embodiments, "including A", "containing A", "for indicating A", "carrying A" can be interpreted as directly carrying A, or indirectly indicating A.

[0168] In some embodiments, the terms of "in response to", "in response to determining", "in the case of", "when", "when", "if", "if" and the like can be replaced with each other.

[0169] In some embodiments, the terms of "greater than", "greater than or equal to", "not less than", "more than", "more than or equal to", "not less than", "higher than", "higher than or equal to", "not lower than", "above" and the like can be replaced with each other, and the terms of "less than", "less than or equal to", "not greater than", "less than", "less than or equal to", "not more than", "lower than", "lower than or equal to", "not higher than", "below" and the like can be replaced with each other.

[0170] In some embodiments, an apparatus or the like can be interpreted as an entity, and can also be interpreted as virtual, and the name thereof is not limited to the name described in the embodiments, and the terms "apparatus", "equipment", "device", "circuit", "network element", "node", "function", "unit", "section", "system", "network", "chip", "chip system", "entity", "subject" and the like can be replaced with each other.

[0171] In some embodiments, the terms "access network device (AN device)", "radio access network device (RAN device)", "base station (BS)", "radio base station", "fixed station", "node", "access point", "transmission point (TP)", "reception point (RP)", "transmission / reception point (TRP)", "panel", "antenna panel", "antenna array", "cell", "macro cell", "small cell", "femto cell", "pico cell", "sector", "cell group", "carrier", "component carrier", "bandwidth part (BWP)" and the like can be replaced with each other.

[0172] In some embodiments, the terms "terminal", "terminal device", "user equipment (UE)", "user terminal", "mobile station (MS)", "mobile terminal (MT)", "subscriber station", "mobile unit", "subscriber unit", "wireless unit", "remote unit", "mobile device", "wireless device", "wireless communication device", "remote device", "mobile subscriber station", "access terminal", "mobile terminal", "wireless terminal", "remote terminal", "handset", "user agent", "mobile client", "client", and the like can be replaced with each other.

[0173] In some embodiments, the access network device, the core network device, or the network device can be replaced with a terminal. For example, for a structure in which communication between the access network device, the core network device, or the network device and the terminal is replaced with communication between a plurality of terminals (for example, also referred to as device-to-device (D2D), vehicle-to-everything (V2X), and the like), the embodiments of the present disclosure can also be applied. In this case, it can also be configured as a structure in which the terminal has all or part of the functions of the access network device. In addition, the language of "uplink", "downlink", and the like can also be replaced with language corresponding to the inter-terminal communication (for example, "side").

[0174] For example, the uplink channel, the downlink channel, and the like can be replaced with a sidelink channel, and the uplink, the downlink, and the like can be replaced with a sidelink.

[0175] In some embodiments, the terms "uplink", "uplink", "physical uplink", and the like can be replaced with each other, the terms "downlink", "downlink", "physical downlink", and the like can be replaced with each other, and the terms "side", "sidelink", "sidelink communication", "sidelink communication", "direct connection", "direct connection link", "direct connection communication", "direct connection link communication", and the like can be replaced with each other.

[0176] In some embodiments, the terms "downlink control information (DCI)", "downlink (DL) assignment", "DL DCI", "uplink (UL) grant", "UL DCI", and the like can be replaced with each other.

[0177] In some embodiments, the terms "physical downlink shared channel (PDSCH)", "DL data", and the like can be replaced with each other, and the terms "physical uplink shared channel (PUSCH)", "UL data", and the like can be replaced with each other.

[0178] In some embodiments, determination or judgment can be made by a value represented by 1 bit (0 or 1), or by a true or false value (Boolean value) represented by true or false, or by comparison of numerical values (for example, comparison with a predetermined value), but is not limited thereto.

[0179] In some embodiments, "network" can be interpreted as devices (for example, access network devices, core network devices, and the like) contained in the network.

[0180] In some embodiments, obtaining data, information, and the like can comply with the laws and regulations of the country where the location is located.

[0181] In some embodiments, data, information, and the like can be obtained after obtaining the consent of the user.

[0182] FIG. 1a is a schematic diagram of the architecture of a communication system according to an embodiment of the present disclosure.

[0183] As shown in FIG. 1a, the communication system 100 includes a terminal (terminal) 101 and a network device 102.

[0184] In some embodiments, the terminal 101 includes at least one of a mobile phone, a wearable device, an Internet of Things device, a communication-capable automobile, a smart automobile, a tablet (Pad), a wireless transceiver-equipped computer, a virtual reality (VR) terminal device, an augmented reality (AR) terminal device, a wireless terminal device in industrial control, a wireless terminal device in self-driving, a wireless terminal device in remote medical surgery, a wireless terminal device in a smart grid, a wireless terminal device in transportation safety, a wireless terminal device in a smart city, a wireless terminal device in a smart home, and the like, but is not limited thereto.

[0185] In some embodiments, the network device 102 can include at least one of an access network device and a core network device.

[0186] In some embodiments, the access network device is at least one of a node or a device that accesses a terminal to a wireless network, for example, an evolved NodeB (eNB) in a 5G communication system, a next generation eNB (ng-eNB), a next generation NodeB (gNB), a node B (NB), a home node B (HNB), a home evolved node B (HeNB), a wireless backhaul device, a radio network controller (RNC), a base station controller (BSC), a base transceiver station (BTS), a base band unit (BBU), a mobile switching center, a base station in a 6G communication system, an Open RAN, a Cloud RAN, a base station in other communication systems, an access node in a wireless fidelity (WiFi) system, and the like, but is not limited thereto.

[0187] In some embodiments, the technical solutions of the embodiments of the present disclosure can be applicable to an Open RAN architecture, at this time, the interfaces between or within the network devices involved in the embodiments of the present disclosure can become internal interfaces of the Open RAN, and the processes and information interactions between the internal interfaces can be implemented through software or programs.

[0188] In some embodiments, the access network device can be composed of a central unit (CU) and a distributed unit (DU), wherein the CU can also be referred to as a control unit. The CU-DU structure can split the protocol layers of the network device, and the functions of part of the protocol layers are controlled by the CU, and the functions of the remaining part or all of the protocol layers are distributed in the DU and controlled by the CU. However, the present disclosure is not limited thereto.

[0189] In some embodiments, the access network device can be one device, or a plurality of devices or device groups, and respectively includes all or part of the first network element, the second network element, and the like. The network element can be virtual or physical. The network device includes at least one of an evolved packet core (EPC), a 5G core network (5GCN), and a next generation core (NGC).

[0190] In some embodiments, the core network device can be one device including one or more network elements, or a plurality of devices or device groups, and respectively includes all or part of the one or more network elements. The network element can be virtual or physical. The core network includes at least one of an evolved packet core (EPC), a 5G core network (5GCN), and a next generation core (NGC).

[0191] In some embodiments, the terminal 101 accesses the core network through a (radio) access network (RAN), and the core network includes a user plane network element and a control plane network element. The user plane network element of the core network includes a user plane function (UPF), and the control plane network element of the core network includes at least one of an authentication server function (AUSF), an AMF, an SMF, a network slice selection function (NSSF), a network exposure function (NEF), a network function repository function (NRF), a unified data management (UDM), a PCF, and an AF.

[0192] The user plane network element (for example, the UPF) is mainly responsible for packet data forwarding, quality of service (QoS) control, charging information statistics, and the like. The control plane network element is mainly responsible for service process interaction, issuing packet forwarding policies and QoS control policies to the user plane, and the like.

[0193] In some embodiments, the control plane of the core network can adopt a service-oriented architecture, that is, the interaction between the control plane network elements adopts a service call manner to replace the point-to-point communication manner in the traditional architecture. In the service-oriented architecture, one control plane network element opens services to other control plane network elements for calling by other control plane network elements; in the point-to-point communication, a specific set of messages exists for the communication interface between the control plane network elements, and can only be used by the control plane network elements at both ends of the interface when communicating.

[0194] The functions of the network elements in the 5G core network involved in the embodiments of the present disclosure are introduced as follows:

[0195] The UPF performs user data packet forwarding according to the routing rules of the SMF, such as sending uplink data to a data network (DN) or other UPFs, and forwarding downlink data to other UPFs or RANs.

[0196] The AUSF performs security authentication of the UE.

[0197] AMF (Access and Mobility Management Function, access and mobility management function), responsible for UE state maintenance, UE reachability management, non-mobility management (mobility management, MM) forwarding of non-access layer (non-access-stratum, NAS) messages, forwarding of session management (session management, SM) N2 messages.

[0198] SMF (Session Management Function, session management function), allocates resources for the session of the UE, and releases the resources. The resources include session quality of service (quality of service, QoS), session path, forwarding rule, etc.

[0199] NSSF, selects a network slice for the UE.

[0200] NEF, exposes network function to third parties in the form of northbound application programming interface (application programming interface, API).

[0201] NRF, provides a storage function and selection function of network function entity information for other network elements.

[0202] UDM, used for user subscription context management.

[0203] PCF (Policy Control Function, policy control function), used for generating and managing user, session, and QoS flow processing policies.

[0204] AF, application management, a functional network element that provides various service services, can interact with the core network through NEF, and can interact with the policy management framework for policy management.

[0205] The related interfaces between the functions of the 5G network elements involved in the embodiments of the present disclosure include:

[0206] N1: interface between UE and core network control plane.

[0207] N2: communication interface between access network (access network, AN) network element and core network control plane.

[0208] N3: communication interface between access network network element and UPF, used for transmitting user data.

[0209] N4: communication interface between SMF and UPF, used for policy configuration of UPF, etc.

[0210] N6: Communication port between the UPF and a data network (DN).

[0211] Embodiments of the present disclosure also relate to a mobile gNB with wireless access backhaul (MWAB), as shown in Figure 1b, which acts as a gNB for other UEs and provides access to the 5G network, i.e. provides NR access link to UEs and wireless connection to 5GC (using NR) through IP connectivity provided by a PDU session established via an NG-RAN cell in which the mobile gNB can camp. The PDU session is provided by a terrestrial network or a non-terrestrial network. Such mobile gNB can be installed on a moving vehicle and provide service to UEs located inside or outside (or entering / leaving the vehicle).

[0212] In some embodiments, the MWAB has the following assumed characteristics:

[0213] - the MWAB is composed of a gNB component (MWAB-gNB) and a UE component (MWAB-UE);

[0214] - the MWAB gNB has gNB functionalities as specified by existing protocols;

[0215] - the N2 / N3 interfaces of the MWAB-gNB access OAM (Operation Administration and Maintenance) through IP connectivity provided by a PDU session of the MWAB-UE;

[0216] - the interface between the MWAB-UE and the MWAB-gNB is not in the scope of SA WG2 if standardization is needed;

[0217] - the MWAB-UE connects to the NG-RAN through a single NR Uu hop (e.g. the terminal functionality accesses the gNB via an NR Uu interface which can use terrestrial network TN or non-terrestrial network NTN technology);

[0218] - the MWAB can serve UEs located inside or outside the vehicle in which the MWAB relay functionality is installed;

[0219] - NR Uu is used for the wireless link between the MWAB gNB and the served UEs. The NR Uu radio link between the MWAB gNB and the served UEs does not use NTN technology;

[0220] - the existing LCS framework is used to provide positioning services to the served UEs;

[0221] - The MWAB can be connected to an NG-RAN of a PLMN (Public Land Mobile Network) or a SNPN (Stand-alone Non-Public Network);

[0222] - The MWAB-gNB can broadcast a PLMN-ID different from the PLMN-ID of the PLMN to which the MWAB-UE is connected;

[0223] - The serving PLMN of the UE is the PLMN broadcasted by the MWAB-gNB to which it is camping / connected, the serving PLMN of the UE can be a PLMN-ID different from the PLMN-ID of the PLMN serving the MWAB-UE.

[0224] In some embodiments, when the UE is served via the MWAB-gNB, the N3 access is made over the IP connection provided by the PDU session of the MWAB-UE, therefore, the user data exchanged between the MWAB-gNB and the UE UPF serving the UE access should be encapsulated as user plane data over the IP connection provided by the PDU session of the MWAB-UE, therefore, the address information of the MWAB node (MWAB-gNB and / or MWAB-UE) should be configured at the serving UPF of the UE. In addition, the UPF can use network address translation (NAT) between the UE and the data network, which can result in that the (private) UE IP address allocated by the 5GC can not be visible on the N6 reference point, i.e.: the serving UPF of the UE can not have access to the (private) UE IP address allocated by the 5GC, therefore, the (private) UE IP address of the MWAB-UE allocated for the BH PDU session is different from the IP address of the IP connection seen by the UE UPF.

[0225] In some embodiments, the existing management procedure for the backhaul Packet Data Unit (BH PDU) session for N3 access is provided as shown in FIG. 1c. As shown in FIG. 1c, the process of UE PDU session establishment or modification can include the following steps:

[0226] Step 1. Establish or modify the PDU session for the UE based on the provisions of the existing protocol, which can make the MWAB-gNB receive a new SM context for the PDU session from the SMF, the new SM context at least includes QoS flow.

[0227] Step 2. For each QoS flow, the MWAB-gNB determines the required 5G network quality of service identity / allocation and retention priority (5G QoS Identifier / Allocation and Retention Priority, 5QI / ARP) and other QoS parameters in the BH PDU session and transport network layer (TNL) information for signaling the QoS rules related to the downlink (DL) service data flow (SDF) to the BH SMF. For uplink (UL), the QoS rules are also determined by the MWAB, and the TNL information determined by the MWAB-gNB is used for classifying the UL data.

[0228] Step 3. The MWAB-UE modifies the BH PDU session according to the indication.

[0229] Step 4. The UPF of the BH PDU session correctly handles the DL traffic from the UE UPF.

[0230] Step 5. The MWAB-UE confirms the correct modification of the BH PDU session.

[0231] Step 6. The MWAB-gNB completes the establishment of the PDU session.

[0232] Step 7. Data for the UE PDU session can be sent / received using the correct QoS.

[0233] In the above scheme, the QoS flows of the PDU session of the UE served by the MWAB-gNB are mapped into the BH PDU session, and the UPF configuration of the BH PDU session is determined by the BH PDU session modification to support handling different data flows from the UE; however, how to configure the address information of the MWAB-UE to the UE UPF to support the N3 access of the UE served by the MWAB-gNB is not provided; nor is the case of using a NAT UPF between the MWAB-UE and the data network (UE UPF) considered.

[0234] It should be noted that the PDU involved in the embodiments of the present disclosure can be described as a (Packet Data Unit, PDU) or a (Protocol Data Unit, PDU), which is not limited.

[0235] Based on the above wireless communication system, the various embodiments of the communication method proposed by the present disclosure are described in detail below.

[0236] FIG. 2 is an interaction diagram of a communication method according to an embodiment of the present disclosure. As shown in FIG. 2, the communication method is used in the communication system 100, and the method comprises:

[0237] S201. The second network function sends the first information to the first network function.

[0238] In some embodiments, the network function can also be referred to as a network element, a network node, a network function entity, etc. The network function can also be a specific logical function entity or a flexible deployed logical function, but is not limited thereto.

[0239] In some embodiments, the second network function can be a network function for session management serving the first terminal. Optionally, the second network function can be denoted as UE SMF.

[0240] In some embodiments, the first network function can be a user plane function serving the first terminal. Optionally, the first network function can be denoted as UE UPF.

[0241] In some embodiments, the first network function can receive the first information sent by the second network function.

[0242] In some embodiments, the sending can be understood as direct sending or forwarding via other network elements, etc.

[0243] In some embodiments, the second network function can configure the first information to the first network function. Optionally, the configuration can be understood as sending.

[0244] In some embodiments, the first information is used to indicate a processing rule of the first data packet and a second data packet associated with the first data packet.

[0245] In some embodiments, the first data packet is an uplink user plane data packet transmitted to the first network function via a backhaul path.

[0246] In some embodiments, the second data packet can be a downlink user plane data packet belonging to the same packet data unit (PDU) session as the first data packet.

[0247] In some embodiments, the PDU session is a PDU session of the first terminal accessing the first network function via the first node, and the PDU session is a first session.

[0248] In some embodiments, the backhaul path is a user plane path of a second session, and the second session is a PDU session providing a backhaul path for a terminal part included in the first node.

[0249] In some embodiments, the first node is a mobile gNB with wireless access backhaul (MWAB). Optionally, the first node comprises a base station part of the mobile gNB with wireless access backhaul (e.g., denoted as MWAB-gNB) and / or the first node comprises a terminal part of the mobile gNB with wireless access backhaul (e.g., denoted as MWAB-UE). Optionally, the terminal part of the mobile gNB with wireless access backhaul can be described as a second terminal.

[0250] Optionally, the terminal accessing the network via the base station part of the mobile gNB with wireless access backhaul is a first terminal.

[0251] In some embodiments, the first data packet and the second data packet are both data packets received by the first network function, and the association relationship therebetween can comprise:

[0252] The first data packet is an uplink user data packet of a first session transmitted to the first network function via the backhaul path, and the second data packet is a downlink user data packet of the first session transmitted to the first network function and needs to be transmitted to the first terminal or the first node via the backhaul path.

[0253] In some embodiments, the destination address of the first data packet is address information of the first network function, and the first data packet can further comprise address information of the first session, for example, address information of the first terminal related to the first session as an inner source address encapsulated in the first data packet, and / or can further comprise a destination address of a service data packet of the first session, for example, a server address of the service data packet of the first session as an inner destination address encapsulated in the first data packet. Based on this, the association relationship between the first data packet and the second data packet can comprise:

[0254] The source address information of the first session included in the first data packet is the same as the destination address information of the second data packet; or,

[0255] The destination address of the first session included in the first data packet is the same as the source address information of the second data packet.

[0256] Optionally, the address information in the embodiments of the present disclosure can comprise an IP address and / or a port number.

[0257] In some embodiments, if the source IP address of the first session included in the first data packet is the same as the destination IP address of the second data packet, it can be determined that the first data packet and the second data packet are associated data packets.

[0258] In some embodiments, if the destination IP address of the first session of the first data packet is the same as the source IP address of the second data packet, it can be determined that the first data packet and the second data packet are associated data packets.

[0259] In some embodiments, the first data packet does not include the address information of the first session, and optionally, the first data packet does not include the first session data packet, and the address information of the corresponding first session can be added in the first network function.

[0260] In some embodiments, if the destination IP address of the first session of the first data packet is the same as the source IP address of the second data packet, it can be determined that the first data packet and the second data packet are associated data packets.

[0261] In some embodiments, the first address information includes one of the following:

[0262] The source address information of the initial first data packet;

[0263] The source address information of the first data packet after the address information of the backhaul path of the second terminal is changed.

[0264] In some embodiments, the first address information is used to identify the source address information of the first data packet, and the first data packet can be the initial first data packet, or the first data packet after the address information of the backhaul path is changed.

[0265] In some embodiments, if the first data packet is the first data packet after the address information of the backhaul path is changed, the corresponding first address information is changed compared with the address information of the initial first data packet.

[0266] In some embodiments, the initial first data packet is the first data packet when the address information of the backhaul path has not been changed.

[0267] In some embodiments, the first information is used to determine at least one of the following:

[0268] Whether the received data packet is the first data packet;

[0269] Whether the received data packet meets the first address information corresponding to the first data packet;

[0270] Whether the second data packet associated with the first data packet;

[0271] Whether the first address information is used for processing of the second data packet;

[0272] Processing the second data packet using the first address information.

[0273] In some embodiments, the first information can include: a first rule, a second rule, and a third rule, wherein the first rule is used to determine whether the received data packet is the first data packet; the second rule is used to determine the first address information corresponding to the first data packet that meets the first rule; and the third rule is used to determine whether the first address information is used for the second data packet and to process the second data packet using the first address information.

[0274] In some embodiments, the first rule used to detect the first data packet and the second rule used to determine the first address can be combined into one rule.

[0275] In some embodiments, the rule used to detect the second data packet and the rule used to process the second data packet using the first address information can be described separately as different rules.

[0276] In some embodiments, the above-mentioned data packet can be an uplink data packet sent via the first node.

[0277] Optionally, the first processing rule includes a detection / inspection rule of the data packet and a recording rule of the data packet, wherein the detection rule is used to determine whether the received data packet is a data packet sent from the MWAB-gNB to the UPF in the PDU session, i.e., an N3 interface uplink data packet of the PDU session (e.g., denoted as: the first session) of the first terminal sent through the backhaul path PDU session (e.g., denoted as: the second session) provided by the second terminal, and the corresponding data packet can be referred to as the first data packet; and the action rule is used to determine the recording time and the recording content of the first data packet that meets the detection rule. In some embodiments, the first address information corresponding to the first data packet that meets the first rule can be determined according to the reception of the first first data packet.

[0278] Optionally, the recording time can be the time when the first first data packet is received, and the recording content can include the first address information corresponding to the first data packet that meets the detection rule.

[0279] In some embodiments, the first network function determines whether the received data packet meets the first rule according to the first rule, and records the first address information corresponding to the first data packet that meets the first rule according to the second rule.

[0280] In some embodiments, the detection rule is also used to determine the second data packet associated with the first data packet, i.e., whether there is a downlink user plane data packet belonging to the same PDU session (i.e., the above-mentioned first session) as the first data packet, and to determine whether the first address information corresponding to the first data packet is used for processing the second data packet and to process the second data packet using the first address information.

[0281] In some embodiments, in the case that the address information of the first session is included in the first data packet, the second data packet can be determined through the association between the address information of the first data packet and the address information of the second data packet.

[0282] Optionally, the downlink user plane data packet with the same source address of the first session included in the first data packet as the destination address can be determined as the second data packet.

[0283] Optionally, the downlink user plane data packet with the same source address of the first session included in the first data packet as the destination address can be determined as the second data packet.

[0284] In some embodiments, processing the second data packet using the first address information can be understood as encapsulating the second data packet using the first address information. Optionally, the second data packet is encapsulated with the first address as the destination address.

[0285] In some embodiments, the first rule can include determining whether the received data packet is the first data packet based on the first tunnel information.

[0286] Optionally, if the tunnel information of the received data packet is the first tunnel information, it is determined that the data packet is the first data packet conforming to the first rule.

[0287] Optionally, the first tunnel information includes user plane address information associated with the first network function corresponding to the first session. The first session is a packet data unit (PDU) session of a first terminal accessing the network through the first node. The first tunnel information can be allocated by the first network function in the first session establishment process and sent to the second network function in the response of the N4 session establishment request, or updated by the first network function in the first session update process and sent to the second network function in the response of the N4 session update request.

[0288] Optionally, the user plane tunnel information associated with the first network function can be core node (CN) tunnel information associated with the first network function, such as GPRS tunneling protocol (GTP) tunnel information. GPRS is the abbreviation of General Packet Radio Service.

[0289] In some embodiments, when an uplink user plane data packet is received based on the user plane channel established based on the first session, it can be determined whether the received data packet is the first data packet based on the GTP tunnel information of the first session. That is, it can be checked whether the received data packet is the first data packet according to the GTP tunnel information of the first session.

[0290] In some embodiments, the first rule can comprise: determining whether the received data packet is the first data packet based on second information configured or negotiated between the first node and the second network function.

[0291] In some embodiments, the first information for determining whether the received data packet is the first data packet can be configured based on second information configured or negotiated between the first node and the second network function.

[0292] In some embodiments, the second information can be information for identifying the data packet sent by the first session other than the first tunnel information.

[0293] Optionally, the second information can comprise at least one of:

[0294] a connection identifier of a user plane connection of the first session;

[0295] an identifier of a first terminal of the first session;

[0296] specific indication information for indicating a user plane connection between the first node and the first network function of the first session;

[0297] specific identification for identifying a user plane connection between the first node and the first network function of the first session.

[0298] In some embodiments, if the second information is available, the determination of whether the received data packet is the first data packet can be based on the second information.

[0299] Optionally, the connection identifier of the user plane connection of the first session can be a connection identifier of an N3 connection of the first session.

[0300] Optionally, the identifier of the first terminal of the first session can be a universal public user identifier of the first terminal of the first session, but is not limited thereto.

[0301] Optionally, the second information can also be specific indication or identification for indicating or identifying the N3 connection between the first node and the UE UPF.

[0302] In some embodiments, the second information can be pre-configured or acquired through protocol interaction between the first node and the second network function, and the embodiments of the present application are not limited thereto.

[0303] In some embodiments, whether the first data packet comprises address information of the first session is not limited, in the case that the first data packet does not comprise the address information of the first session, for the uplink data packet received by the first network function, the first data packet received by the first network function can be determined as the first data packet based on the first tunnel information or the second information as above, i.e. the data packet is the uplink data packet of the first session; for the downlink user plane data packet received by the first network function, whether the downlink user plane data packet received by the first network function is the second data packet can be determined based on the rule information configured by the second network function and comprising the address of the first terminal of the first session. Optionally, when the destination address of the downlink user plane data packet is the address of the first terminal of the first session, it can be determined that the downlink user plane data packet received by the first network function is the second data packet, i.e. the data packet is the downlink user plane data packet of the first session, and it is determined that the second data packet is associated with the first data.

[0304] In some embodiments, the first data packet can comprise at least one of the following:

[0305] a user data packet of the first terminal;

[0306] a specific data packet generated by the first node.

[0307] Optionally, the first data packet can be an uplink user data packet received through an N3 interface.

[0308] Optionally, the first data packet can be a user data packet from the first terminal or a specific data packet generated by the first node.

[0309] In some embodiments, the specific data packet can comprise at least one of the following:

[0310] a user plane signaling message of a specific tunnel protocol;

[0311] an empty user plane message of a tunnel protocol.

[0312] In some embodiments, the user plane signaling message of the specific tunnel protocol can comprise a GTP-U and a GTP-U signaling message.

[0313] Optionally, the GTP-U signaling message can comprise a tunnel state, an error indication or a new GTP-U signaling message, but is not limited thereto.

[0314] Optionally, the empty user plane message of the tunnel protocol can be a pseudo g-PDU message.

[0315] In some embodiments, the step S201 can specifically include: sending the first information to the first network function through a first request message, the first request message being used for managing a user plane path of a packet data unit (PDU) session of a first terminal accessing a network via the first node.

[0316] In some embodiments, the first request message can include an N4 session modification request or an N4 session establishment request.

[0317] Optionally, the UE SMF can send the first information to the UE UPF through an N4 session establishment / modification request.

[0318] In some embodiments, the UE SMF can send the first information to the UE UPF through an N4 session establishment request before the sending of the N4 session establishment request, if the second information is available; or send the first information to the UE UPF through an N4 session modification request based on the first tunnel information after obtaining the first tunnel information in a response message of the N4 session establishment request.

[0319] S202, the first network function determines first address information corresponding to a first data packet in the received data packets based on the first information, and uses the first address information for processing of a second data packet.

[0320] In some embodiments, the first network function can determine whether the received data packet is the first data packet based on rule information in the first information. Optionally, if the received data packet is an uplink user plane data packet transmitted to the first network function through a backhaul path, it is determined that the data packet is the first data packet, and then it is determined that source address information of the first data packet is the corresponding first address information.

[0321] In some embodiments, using the first address information for processing of the second data packet includes: encapsulating the second data packet using the first address information.

[0322] Optionally, the second data packet is an associated data packet of the first data packet.

[0323] Optionally, the first address information can be recorded in the first network function, and the first address information is used for processing of the second data packet when the second data packet is received.

[0324] In some embodiments, if the first address information is source address information of an initial first data packet, the source address information of the initial first data packet can be used to encapsulate a second data packet associated with the initial first data packet.

[0325] In some embodiments, if the first address information is the source address information of the first data packet after the address information of the backhaul path is changed, the second data packet associated with the first data packet after the address information of the backhaul path is changed can be encapsulated using the source address information of the first data packet after the address information of the backhaul path is changed.

[0326] It should be noted that after the source address of the first data packet is changed, the first information used to process the second data packet associated with the first data packet does not need to be changed. The changed first address can be recorded according to the first information, and then the changed first address is used for processing of the second data packet.

[0327] Optionally, the second data packet can be encapsulated with the address corresponding to the first address information as the destination address.

[0328] In some embodiments, the processing rule indicated (or included) by the first information is related to a first session of a PDU session of a first terminal accessing a network through the first node, that is, the user plane path of the PDU session is accessed by the first node through the user plane data interaction interface, and the interaction with the second network function through the backhaul path is implemented.

[0329] Optionally, the specific content of the processing rule can be referred to the related description of the first information in the foregoing, which will not be described here.

[0330] In some embodiments, the first address information can be the address information of the backhaul path provided by the second terminal.

[0331] In some embodiments, one end of the backhaul path involved in the embodiments of the present disclosure can be connected to the MWAB (such as MWAB-UE), and the other end can be connected to the data network. The MWAB can transmit user plane data packets to the first network function in the data network through the user plane communication of the backhaul path.

[0332] In some embodiments, the address information of the backhaul path involved in the embodiments of the present disclosure refers to the address of the MWAB at one end of the backhaul path between the MWAB and the second network function, which can include at least one of the IP address, the IP prefix, and the port address of the MWAB at one end of the backhaul path.

[0333] It should be noted that in other parts of the embodiments of the present disclosure, the address information of the backhaul path can also be described as the IP address of the BH session, the IP prefix of the BH session, the port address of the BH session, the IP address of the backhaul path, the IP prefix of the backhaul path, and the port address of the backhaul path. These information are all used to indicate the address of the MWAB at one end of the backhaul path.

[0334] It should be noted that in some networks, the operator will use a NAT (Network Address Translation) function before the UPF sends data to the data network. For example: in the present embodiment, the data packet sent from the MWAB-gNB to the UE UPF (which can correspond to the first network function in the above) is forwarded by the UPF of the backhaul path, and the UPF will use the NAT function to remap the source address of the data packet when sending the data to the first network function, so that the source address of the user plane data packet sent by the MWAB and the source address of the user plane data packet received by the first network function can be different, but both of them are address information indicating the same backhaul path.

[0335] For example, assuming that the source address of the first data packet sent by the MWAB is address information #1, after the first data packet is sent to the UPF of the backhaul path, the UPF of the backhaul path will remap the source address from address information #1 to address information #2 before sending it to the first network function. At this time, the source address of the user plane data packet received by the first network function is address information #2, wherein address information #1 and address information #2 are address information indicating the same backhaul path, and address information #1 and address information #2 can be the same or different. Wherein, address information #1 can be the information used by the MWAB to indicate the address information of the backhaul path, and address information #2 can be the information used by the first network function to indicate the address information of the backhaul path.

[0336] Optionally, the data packet sent from the UE UPF to the MWAB is forwarded by the UPF of the backhaul path, and the UPF of the backhaul path will use the NAT function to remap the destination address of the data packet when receiving the data packet sent by the UE UPF. For example: in the above example, the destination address information of the data packet when it is sent from the UE UPF is address information #2, and the UPF of the backhaul path maps address information #2 to address information #1 and transmits it to the MWAB-UE through the backhaul path.

[0337] It should be understood that the UE UPF can be the same as the UPF of the backhaul path (for example: different parts of the same UPF provide services for different terminals respectively), or different, which is not limited. Similarly, the UE AMF can be the same as or different from the AMF of the backhaul path, and the UE SMF can be the same as or different from the SMF of the backhaul path, which is not limited.

[0338] In some embodiments, before step S202, the above method can further include:

[0339] S203, the first network function receives the data packet.

[0340] In some embodiments, the first network function receives the uplink user plane data packet sent by the first terminal.

[0341] In S204, the first network function determines the first data packet and the second data packet based on the acquired first information.

[0342] In some embodiments, the first network function determines whether the received data packet is the first data packet according to a first rule in the first information; determines the first address information corresponding to the first data packet meeting the first rule when the first first data packet is received, and updates the recorded first address information when the first data packet after the backhaul path change is received according to a second rule in the first information; and determines the second data packet associated with the first data packet based on a third rule in the first information, and processes the second data packet using the recorded first address information.

[0343] In some embodiments, the first rule for detecting the first data packet and the second rule for recording the first address can be combined into the same rule.

[0344] In some embodiments, the rule for detecting the second data packet and the rule for processing the second data packet using the first address information can be described separately as different rules.

[0345] In some embodiments, the above rule information can be implemented by updating the processing rule of the uplink and downlink user plane data packet of the existing first session.

[0346] In some embodiments, the names of information, etc. are not limited to the names described in the embodiments, and the terms of "information", "message", "signal", "signaling", "report", "configuration", "indication", "instruction", "command", "channel", "parameter", "domain", "field", "symbol", "data", etc. can be replaced with each other.

[0347] In some embodiments, the terms of "sending", "transmitting", "reporting", "issuing", "transmitting", "bidirectional transmitting", "sending and / or receiving", etc. can be replaced with each other.

[0348] In some embodiments, the terms "certain", "preset", "pre-set", "set", "indicated", "any", "first", and the like can be replaced with each other, and "certain A", "preset A", "pre-set A", "set A", "indicated A", "any A", "first A" can be interpreted as A predetermined in a protocol or the like, or A obtained by setting, configuration, or indication, or a specific A, any A, or first A, but are not limited thereto.

[0349] In some embodiments, the terms "in the case of", "when", "if", and the like can be replaced with each other.

[0350] The method related to the embodiments of the present disclosure can include at least one of steps S201-S203. For example, steps S201 and S202 can be implemented as independent embodiments, but are not limited thereto.

[0351] In some embodiments, step S203 is optional, and one or more of the steps can be omitted or replaced in different embodiments.

[0352] FIG. 3a is a flow diagram of a communication method according to an embodiment of the present disclosure. As shown in FIG. 3a, the communication method can be performed by a first network function, and the method includes:

[0353] S301, receiving first information sent by a second network function.

[0354] The optional implementation of step S301 can refer to the optional implementation of step S201 of FIG. 2 and other associated parts in the embodiments related to FIG. 2, which will not be repeated here.

[0355] In some embodiments, the first information is used to indicate a processing rule of the first data packet and a second data packet managed by the first data packet.

[0356] In some embodiments, the first information includes a processing rule of the first data packet and a second data packet managed by the first data packet.

[0357] In some embodiments, the first network function can be a UPF serving the first terminal.

[0358] In some embodiments, the second network function can be an SMF serving the first terminal.

[0359] In some embodiments, the first data packet is an uplink user plane data packet transmitted to the first network function via a backhaul path.

[0360] In some embodiments, the second data packet can be a downlink user plane data packet belonging to a same packet data unit, PDU, session as the first data packet. Optionally, the PDU session is a PDU session of a first terminal accessing a first network function through the first node, and the PDU session is a first session. Optionally, the first terminal is a terminal accessing the network through the first node.

[0361] In some embodiments, the backhaul path is a user plane path of a second session, and the second session is a PDU session providing the backhaul path for a terminal part included by the first node.

[0362] In some embodiments, the first node can be a multi-wavelength access base station, MWAB, and optionally, the MWAB can include a MWAB-gNB and / or a MWAB-UE. Optionally, the first terminal is a terminal accessing the network through the MWAB-gNB. Optionally, the MWAB-UE is the second terminal.

[0363] S302, determining, based on the first information, a first data packet and a second data packet in the received data packet that meet the first information.

[0364] Optional implementation manners of step S302 can refer to optional implementation manners of step S203 of FIG. 2 and other associated parts in the embodiments involved in FIG. 2, which will not be described herein.

[0365] In some embodiments, the received data packet can be an uplink data packet sent via the first node. In some embodiments, the first information includes a first rule for determining whether the received data packet is the first data packet; can further include a second rule for determining first address information corresponding to the first data packet that meets the first rule; and can further include a third rule for determining and processing the second data packet.

[0366] In some embodiments, the first network function can determine, based on a processing rule included in the first information, whether the received data packet is the first data packet and / or the second data packet.

[0367] S303, determining, based on the first information, first address information corresponding to the first data packet, and using the first address information for processing of the second data packet.

[0368] Optional implementation manners of step S303 can refer to optional implementation manners of step S202 of FIG. 2 and other associated parts in the embodiments involved in FIG. 2, which will not be described herein.

[0369] In some embodiments, the first address information is used to identify source address information of the first data packet.

[0370] In some embodiments, the first address information includes one of the following:

[0371] source address information of the initial first data packet;

[0372] source address information of the changed first data packet of the second terminal providing the backhaul path.

[0373] The method related to the embodiments of the present disclosure can include at least one of steps S301-S303. For example, steps S301 and S303 can be implemented as independent embodiments, but are not limited thereto.

[0374] In some embodiments, step S302 is optional, and one or more of these steps can be omitted or replaced in different embodiments.

[0375] FIG. 3b is a flow diagram of a communication method according to an embodiment of the present disclosure. As shown in FIG. 3b, the communication method can be performed by a first network function, and the method includes:

[0376] S311, obtaining first information.

[0377] Optional implementation of step S311 can refer to optional implementation of step S201 of FIG. 2, step S301 of FIG. 3a, and other associated parts in the embodiments related to FIG. 2 and FIG. 3a, which will not be described here.

[0378] In some embodiments, the first network function receives the first information sent by the second network function.

[0379] In some embodiments, the first information is used to indicate processing rules of the first data packet and a second data packet managed by the first data packet.

[0380] In some embodiments, the first information includes processing rules of the first data packet and a second data packet managed by the first data packet.

[0381] In some embodiments, the first network function can be a UPF serving the first terminal.

[0382] In some embodiments, the second network function can be an SMF serving the first terminal.

[0383] In some embodiments, the first data packet is an uplink user plane data packet transmitted to the first network function through a backhaul path.

[0384] In some embodiments, the second data packet can be a downlink user plane data packet belonging to the same packet data unit (PDU) session as the first data packet. Optionally, the PDU session is a PDU session of the first terminal accessing the first network function through the first node, and the PDU session is a first session. Optionally, the first terminal is a terminal accessing the network through the first node.

[0385] In some embodiments, the backhaul path is a user plane path of a second session, the second session being a PDU session providing the backhaul path for a terminal part comprised by the first node.

[0386] In some embodiments, the first data packet comprises source address information of the first session which is same as destination address information of the second data packet; or, the first data packet comprises destination address information which is same as source address information of the second data packet.

[0387] Optionally, the address information comprises an IP address and / or a port number.

[0388] In some embodiments, the first information is used to determine at least one of:

[0389] whether the received data packet is the first data packet;

[0390] whether the first address information corresponding to the first data packet is matched;

[0391] whether the second data packet is associated with the first data packet;

[0392] whether the first address information is used for processing of the second data packet;

[0393] processing the second data packet using the first address information.

[0394] In some embodiments, determining whether the received data packet is the first data packet comprises:

[0395] determining, based on the first tunnel information, whether the received data packet is the first data packet; or

[0396] determining, based on second information configured or negotiated between the first node and the second network function, whether the received data packet is the first data packet.

[0397] In some embodiments, the first tunnel information is user plane tunnel information of the first session associated with the first network function.

[0398] In some embodiments, the second information comprises at least one of:

[0399] a connection identifier of a user plane connection of the first session;

[0400] an identifier of a first terminal of the first session;

[0401] specific indication information indicating the user plane connection between the first node and the first network function of the first session;

[0402] specific identifier identifying the user plane connection between the first node and the first network function of the first session.

[0403] In some embodiments, the first data packet comprises at least one of:

[0404] a user data packet of the first terminal accessing the network via the first node;

[0405] a specific data packet, the specific data packet being generated by the first node.

[0406] In some embodiments, the specific data packet comprises at least one of:

[0407] a user plane signaling message of a specific tunneling protocol;

[0408] a user plane message of an empty tunneling protocol.

[0409] In some embodiments, the step 311 can specifically comprise: obtaining, by the first request message, the first information sent by the second network function.

[0410] In some embodiments, the first request message is used for managing a user plane path of the first session.

[0411] In some embodiments, the first node can be a MWAB, and optionally, the MWAB can comprise a MWAB-gNB and / or a MWAB-UE. Optionally, the first terminal is a terminal accessing the network via the MWAB-gNB. Optionally, the MWAB-UE is the second terminal.

[0412] S312, determining, based on the first information, first address information corresponding to the first data packet in the received data packet, and using the first address information for processing of the second data packet.

[0413] Optional implementation manners of the step S312 can refer to the optional implementation manners of the step S202 in FIG. 2, the step S303 in FIG. 3a, and other associated parts in the embodiments involved in FIG. 2 and FIG. 3a, which will not be described herein again.

[0414] In some embodiments, the first address information is used for identifying source address information of the first data packet.

[0415] In some embodiments, the first address information comprises one of:

[0416] initial source address information of the first data packet;

[0417] changed source address information of the first data packet of the second terminal providing the backhaul path.

[0418] In some embodiments, using the first address information for processing of the second data packet comprises: encapsulating the second data packet using the first address information.

[0419] In some embodiments, the second data packet is encapsulated with the first address information. Optionally, the second data packet can be encapsulated with an address corresponding to the first address information as a destination address.

[0420] In some embodiments, before step S302, the method can further include: determining, based on the first information, the first data packet and the second data packet in the received data packet that meet the first information.

[0421] The optional implementation manners of the above can refer to the optional implementation manners of step S204 of FIG. 2, step S302 of FIG. 3a, and other associated parts in the embodiments related to FIG. 2 and FIG. 3a, which will not be repeated here.

[0422] In some embodiments, the received data packet can be an uplink data packet sent via the first node. In some embodiments, the first information includes a first rule for determining whether the received data packet is the first data packet; can further include a second rule for determining the first address information corresponding to the first data packet that meets the first rule; and can further include a third rule for determining and processing the second data packet.

[0423] In some embodiments, the first network function can determine, based on the processing rule included in the first information, whether the received data packet is the first data packet and / or the second data packet.

[0424] FIG. 3c is a flow diagram of a communication method according to an embodiment of the present disclosure. As shown in FIG. 3c, the communication method can be performed by a first network function, and the method includes:

[0425] S321, receiving a data packet.

[0426] The optional implementation manner of step S321 can refer to the optional implementation manner of step S203 of FIG. 2 and other associated parts in the embodiments related to FIG. 2, which will not be repeated here.

[0427] S322, determining, based on the first information, the first address information corresponding to the first data packet in the data packet, and using the first address information for processing of the second data packet.

[0428] The optional implementation manner of step S322 can refer to the optional implementation manner of step S202 of FIG. 2, step S303 of FIG. 3a, step S312 of FIG. 3b, and other associated parts in the embodiments related to FIG. 2, FIG. 3a, and FIG. 3b, which will not be repeated here.

[0429] FIG. 4 is a flow diagram of a communication method according to an embodiment of the present disclosure. As shown in FIG. 4, the communication method can be performed by a second network function, and the method includes:

[0430] S401, sending first information.

[0431] The optional implementation of step S401 can refer to the optional implementation of step S201 in FIG. 2 and other associated parts in the embodiments related to FIG. 2, which will not be repeated here.

[0432] In some embodiments, the first network function sends the first information to the first network function.

[0433] In some embodiments, the first information is used to indicate a processing rule of the first data packet and a second data packet managed by the first data packet.

[0434] In some embodiments, the first information is used to determine first address information corresponding to the first data packet, and to determine that the first address information is used for processing of the second data packet.

[0435] In some embodiments, the first address information is used to identify source address information of the first data packet.

[0436] In some embodiments, the first network function can be a UPF serving the first terminal.

[0437] In some embodiments, the second network function can be an SMF serving the first terminal.

[0438] In some embodiments, the second data packet is encapsulated using the first address information.

[0439] In some embodiments, the first data packet is an uplink user plane data packet transmitted to the first network function via a backhaul path.

[0440] In some embodiments, the second data packet is a downlink user plane data packet belonging to the same packet data unit (PDU) session as the first data packet.

[0441] In some embodiments, the PDU session is a PDU session of a first terminal accessing the first network function via the first node, and the PDU session of the first terminal is a first session.

[0442] In some embodiments, the backhaul path is a user plane path of a second session, and the second session is a PDU session providing a backhaul path for a terminal part included in the first node.

[0443] In some embodiments, the first data packet includes source address information of the first session that is the same as destination address information of the second data packet, or the first data packet includes destination address information that is the same as source address information of the second data packet.

[0444] Optionally, the address information includes an IP address and / or a port number.

[0445] In some embodiments, the first address information includes one of the following:

[0446] source address information of the first data packet;

[0447] source address information of the first data packet after the address information of the terminal part of the backhaul path is changed.

[0448] In some embodiments, the first information is used to determine at least one of:

[0449] whether the received data packet is the first data packet;

[0450] whether the first data packet corresponds to the first address information;

[0451] the second data packet associated with the first data packet;

[0452] whether the first address information is used for processing of the second data packet;

[0453] processing the second data packet using the first address information.

[0454] In some embodiments, determining whether the received data packet is the first data packet comprises:

[0455] determining whether the received data packet is the first data packet based on first tunnel information; or

[0456] determining whether the received data packet is the first data packet based on second information configured or negotiated between the first node and the first network function.

[0457] In some embodiments, the first tunnel information is user plane tunnel information associated with the first network function for the first session.

[0458] In some embodiments, the second information comprises at least one of:

[0459] a connection identifier of a user plane connection for the first session;

[0460] an identifier of the first terminal for the first session;

[0461] specific indication information indicating a user plane connection between the first node and the first network function for the first session;

[0462] specific identifier identifying a user plane connection between the first node and the first network function for the first session.

[0463] In some embodiments, the first data packet comprises at least one of:

[0464] a user data packet of the first terminal accessing the network via the first node;

[0465] a particular data packet, the particular data packet being generated by the first node.

[0466] In some embodiments, the particular data packet comprises at least one of:

[0467] a user plane signaling message of a particular tunneling protocol.

[0468] an empty user plane message of a tunneling protocol.

[0469] In some embodiments, the step 401 can comprise: sending the first information to the first network function through a first request message, the first request message being used for managing a user plane path of the first session.

[0470] In some embodiments, the first node is a mobile base station with wireless backhaul, the first node comprises a base station part of the mobile base station with wireless backhaul, and / or the first node comprises a terminal part of the mobile base station with wireless backhaul, the terminal part of the mobile base station with wireless backhaul being the second terminal.

[0471] FIG. 5 is a flow diagram of a communication method according to an embodiment of the present disclosure. As shown in FIG. 5, the communication method can be performed by a communication system, and the method comprises:

[0472] S501, the second network node sends the first information to the first network node.

[0473] The optional implementation of the step S501 can refer to the optional implementation of the step S201 in FIG. 2, the step S301 in FIG. 3a, the step S311 in FIG. 3b, the step S401 in FIG. 4, and other associated parts in the embodiments related to FIG. 2, FIG. 3a-3b, and FIG. 4, which will not be repeated here.

[0474] In some embodiments, the first information is used to indicate a processing rule of the first data packet and a second data packet associated with the first data packet.

[0475] S502, the first network node determines first address information corresponding to the first data packet in the received data packet based on the received first information, and uses the first address information for processing of the second data packet.

[0476] The optional implementation of the step S502 can refer to the step S204 in FIG. 2, the step S303 in FIG. 3a, the step S312 in FIG. 3b, and other associated parts in the embodiments related to FIG. 2 and FIG. 3a-3b, which will not be repeated here.

[0477] The embodiments of the present disclosure further provide a device for implementing any of the above methods, for example, a device comprising units or modules for implementing the steps performed by the terminal in any of the above methods. For another example, another device is provided, comprising units or modules for implementing the steps performed by the network element (such as an access network device, a core network function node, a core network device, etc.) in any of the above methods.

[0478] It should be understood that the division of each unit or module in the above device is only a logical function division, and all or part of the units or modules can be integrated into one physical entity or physically separated in actual implementation. In addition, the units or modules in the device can be implemented in the form of processor invoking software: for example, the device comprises a processor connected with a memory, the memory stores instructions, and the processor invokes the instructions stored in the memory to implement any of the above methods or to implement the functions of each unit or module of the device, wherein the processor is a general processor such as a central processing unit (CPU) or a microprocessor, and the memory is a memory in the device or a memory outside the device. Alternatively, the units or modules in the device can be implemented in the form of hardware circuit, and the functions of part or all of the units or modules can be implemented by the design of the hardware circuit. The above hardware circuit can be understood as one or more processors; for example, in one implementation, the above hardware circuit is an application-specific integrated circuit (ASIC), and the functions of part or all of the units or modules are implemented by the design of the logical relationship between the elements in the circuit; for another example, in another implementation, the above hardware circuit is a programmable logic device (PLD), and a field programmable gate array (FPGA) is taken as an example, which can include a large number of logic gate circuits, and the connection relationship between the logic gate circuits is configured by a configuration file, so as to implement the functions of part or all of the units or modules.

[0479] All units or modules of the above apparatus can be implemented in the form of processor invoking software, or in the form of hardware circuit, or partially in the form of processor invoking software and partially in the form of hardware circuit. In the embodiments of the present disclosure, the processor is a circuit with signal processing capability, and in one implementation, the processor can be a circuit with instruction reading and running capability, such as a central processing unit (CPU), a microprocessor, a graphics processing unit (GPU) (which can be understood as a microprocessor), a digital signal processor (DSP), etc.; in another implementation, the processor can implement certain functions through a logical relationship of hardware circuit, and the logical relationship of the above hardware circuit is fixed or reconfigurable, such as an application-specific integrated circuit (ASIC) or a programmable logic device (PLD) implemented hardware circuit, such as an FPGA. In the reconfigurable hardware circuit, the processor loads a configuration document to implement the configuration of the hardware circuit, and the process can be understood as the process of the processor loading instructions to implement the functions of part or all of the units or modules. In addition, it can also be a hardware circuit designed for artificial intelligence, which can be understood as an ASIC, such as a neural network processing unit (NPU), a tensor processing unit (TPU), a deep learning processing unit (DPU), etc.

[0480] FIG. 6a is a structural schematic diagram of a first network function according to an embodiment of the present disclosure. As shown in FIG. 6a, the first network function can include at least one of a first transceiver module 611, a first processing module 612, etc.

[0481] In some embodiments, the first transceiver module is configured to receive a data packet; and the first processing module is configured to determine, according to first information, first address information corresponding to a first data packet in the data packet, and use the first address information for processing of a second data packet; wherein the first address information is used to identify source address information of the first data packet; and the second data packet is a data packet associated with the first data packet.

[0482] Optionally, the first processing module 612 is further configured to perform the steps related to processing information performed by the first network function in any of the above methods, for example, step S204 shown in FIG. 2, which will not be described herein again.

[0483] Optionally, the first transceiver module 611 is configured to perform the steps related to transceiving signaling performed by the first network function in any of the above methods, for example, step S201 shown in FIG. 2, which will not be described herein again.

[0484] Optionally, the first transceiver module 611 is further configured to perform the steps related to transceiving data performed by the first network function in any of the above methods, for example, step S203 shown in FIG. 2, which will not be described herein again.

[0485] FIG. 6b is a structural diagram of a second network function according to the embodiments of the present disclosure. As shown in FIG. 6b, the second network function includes at least one of a second transceiver module 621, a second processing module 622, and the like.

[0486] In some embodiments, the second transceiver module 621 is configured to send first information to the first network function;

[0487] The first information is used to determine first address information corresponding to a first data packet in a data packet received by the first network function, and to determine that the first address information is used for processing of a second data packet.

[0488] The first address information is used to identify source address information of the first data packet; and the second data packet is a data packet associated with the first data packet.

[0489] In some optional embodiments, a solution is provided for supporting a PDU session connection network established through a MWAB, whether or not a NAT is used between a MWAB-UE and a data network (UE UPF). The solution supports corresponding user data transmission through an IP connection network provided by a PDU session of the MWAB-UE, and supports establishment / modification / release of the corresponding PDU session.

[0490] In the following embodiments, the MWAB-UE is authorized, and the corresponding MWAB-gNB is configured with information that can connect to the AMF via the corresponding OAM server. A BH PDU session for the MWAB-gNB providing N2 access to the AMF is established based on the policy configuration to the MWAB-UE (e.g., by the URSP rule of the MWAB-UE), where the user route selection policy (URSP) is a policy for selecting different PDU sessions. A BH PDU session for the MWAB-gNB providing N3 access to the UPF serving the UE is established based on the policy configuration to the MWAB-UE (e.g., by the URRP rule of the MWAB-UE). Based on the policy configuration to the MWAB-UE, the BH PDU for the MWAB-gNB N3 access UPF and the BH PDU session for the MWAB-gNB N2 access AMF can be the same or different. The AMF serving the UE accessed by the MWAB-gNB is referred to as the UE AMF, and the N3 UPF / SMF serving the UE accessed by the MWAB-gNB is referred to as the UE UPF / UE SMF. The MWAB-gNB can share the address information of the BH PDU session for N2 / N3 access, or the address information of the MWAB-gNB can be different from the address information of the BH PDU session for N2 / N3. The AMF serving the UE accessed by the MWAB-gNB or the AMF serving the UE is referred to as the UE AMF, and the N3 UPF / SMF serving the UE accessed by the MWAB-gNB is referred to as the UE UPF / UE SMF. The MWAB-gNB can share the address information of the BH PDU session corresponding to the backhaul path for N2 / N3 access, or the address information of the MWAB-gNB can be different from the address information of the BH PDU session corresponding to the backhaul path for N2 / N3.

[0491] In some embodiments, the BH peer address (which can correspond to the first address information in the above) is the address information of the backhaul path for N3 access, which can refer to the address information of the MWAB-UE end of the backhaul path provided by the BH PDU session used by the UE SMF / UE UPF, which can be the same or different based on whether the NAT is the same as the address information of the MWAB-UE end of the backhaul path provided by the BH PDU session used by the WMAB, both of which indicate the same backhaul path address information.

[0492] In some embodiments, the configuration packet dynamic processing rule is to use the BH peer address in the received uplink data packet.

[0493] In some embodiments, the BH peer address is detected by the UE UPF via the received N3 uplink data packet and recorded.

[0494] In some embodiments, the data packet dynamic handling rule is that the BH peer address is recorded and used for downlink data packet transmission.

[0495] In some embodiments, the data packet dynamic handling rule is that the updated BH peer address (which can correspond to the updated first address information above) is detected by the UE UPF via the received N3 uplink data packet and used for downlink data packet transmission.

[0496] In some embodiments, as shown in FIG. 7, a solution to support PDU session access through MWAB is provided, which can include the following steps:

[0497] S1. A MWAB-UE (which can correspond to the second terminal above) is registered and provided with a MWAB authorization.

[0498] Optionally, the MWAB-gNB is configured with information acting as wireless access, and the MWAB-gNB is serving the UE.

[0499] S2. The UE (which can correspond to the first terminal above) sends a PDU session establishment request to the MWAB-gNB.

[0500] S3. Trigger a BH PDU session modification / establishment for accessing a serving AMF (UE AMF) of the UE for exchanging signaling for session management procedures.

[0501] S4. Send the PDU session establishment request included in the N2 message from the MWAB-gNB to the UE AMF through the BH PDU session.

[0502] S5. Optionally, the UE AMF determines that the sender of the N2 message including the PDU session establishment request is the MWAB-gNB, i.e., the UE is currently accessing the network via the WMAB-gNB, based on information included in the message received from step S4 or local information related to the access RAN node.

[0503] In some embodiments, the information included in the message received from step S4 or local information related to the access RAN node can be information indicating that the UE accesses the network via the MWAB-gNB, which can include at least one of an explicit MWAB indication, location configuration, access type information, location information, etc.

[0504] S6. The UE AMF invokes the Nsmf_PDUSession_CreateSMContext Request service to send a PDU session context setup request to the UE SMF (may correspond to the second network function in the above).

[0505] In some embodiments, if it is determined in step S5 that the sender of the N2 message including the PDU session establishment request is the MWAB-gNB, the information indicating that the PDU session is established for the UE accessing the network via the MWAB can be included in the PDU session context setup request sent to the UE SMF.

[0506] In some embodiments, if it is not determined in step S5 that the sender of the N2 message including the PDU session establishment request is the MWAB-gNB, the information included in the message received from step S5 can be the information indicating that the UE accesses the network via the MWAB-gNB, such as: displayed MWAB indication, location configuration, access type information and / or location information. Alternatively, the UE AMF can determine that the sender of the N2 message including the PDU session establishment request is the MWAB-gNB based on the information included in the message received from step S5 or local information for accessing the RAN node, and then the information indicating that the PDU session is established for the UE accessing the network via the MWAB can be included in the PDU session context setup request sent to the UE SMF.

[0507] S7. Optionally, the UE SMF determines to establish the PDU session via the MWAB-gNB based on the information included in the message received from step S6 or local information related to the access RAN node.

[0508] In some embodiments, if it is determined in step S5 that the sender of the N2 message including the PDU session establishment request is the MWAB-gNB, the information included in the message received from step S6 can be the information indicating that the PDU session is established for the UE accessing the network via the MWAB.

[0509] In some embodiments, if it is not determined in step S5 that the sender of the N2 message including the PDU session establishment request is the MWAB-gNB, but it is determined in step S6, the information included in the message received from step S6 can be the information indicating that the PDU session is established for the UE accessing the network via the MWAB.

[0510] In some embodiments, if it is determined in steps S5 and S6 that the sender of the N2 message including the PDU session establishment request is not the MWAB-gNB, the information included in the message received from step S6 can be information indicating that the UE accesses the network via the MWAB-gNB, for example: explicit MWAB indication, location configuration, access type information, and / or location information.

[0511] S8. Establish / modify N4 session to establish user plane connection for serving a PDU session of the UE (UE PDU session).

[0512] In this procedure, the acquired CN tunnel information is GTP tunnel information about the UE UPF. The CN tunnel information is used for the transmission of user data of the UE PDU session between the MWAB-gNB and the UE UPF based on the backhaul path, and the CN tunnel information is sent to the UE SMF.

[0513] In some embodiments, if information other than the CN tunnel information can be used to identify the data packets transmitted by the UE PDU session between the MWAB-gNB and the UE UPF based on the backhaul path, the information (which can correspond to the second information in the foregoing) can be configured or negotiated between the MWAB-gNB and the UE SMF. Optionally, the information can include but is not limited to the following information: using the connection identifier of the N3 connection identifying the PDU session, or using the UE ID (e.g., the UE GPSI (Generic Public Subscription Identifier) of the PDU session), or using any other specific indication or identifier.

[0514] In some embodiments, if the above information is available before step S8, the processing rule for reporting the BH peer address or forwarding the data packet with the BH peer address can be set as described in step S9 in this step S8. Optionally, the detection information for the data packet can be information other than the CN tunnel information. It should be understood that the N4 session establishment / modification request in step S8 or the N4 session modification request in S9 can correspond to the first information in the foregoing.

[0515] S9. Modify the N4 session to indicate detecting the BH peer address.

[0516] In some embodiments, the BH peer address is address information of the MWAB-UE of a BH PDU session (may correspond to the second session above) providing IP connectivity for N3 access. In this embodiment, the address information is address information of the MWAB-UE at the end of the backhaul path provided by the BH PDU session that the UE UPF can obtain and use (i.e., can be obtained by the UE UPF), regardless of whether NAT is used between the MWAB-UE and the UE UPF.

[0517] In some embodiments, the detection information for the data packet can be destination GTP tunnel information of the UE UPF for uplink user data transmission between the MWAB-gNB and the UE UPF for the UE PDU session (may correspond to the first session above).

[0518] Optionally, the detection condition for the BH peer address is to determine, based on the GTP tunnel information or information other than the CN tunnel information described above, whether the data packet sent by the UE PDU session is user data between the MWAB-gNB and the UE UPF for the UE PDU session via the MWAB-gNB.

[0519] In some embodiments, the recorded BH peer address can be applied to processing of associated data packets.

[0520] Optionally, the associated data packet can include a downlink user plane data packet having the same PDU session as the received uplink user plane data packet (e.g., including the matching GTP tunnel information), or if the received uplink data packet (e.g., including the matching GTP tunnel information) includes a UE IP address of the UE PDU session, the associated data packet is a downlink user plane data packet having the corresponding UE IP address as the destination address.

[0521] In some embodiments, the recording condition for the BH peer address includes a recording opportunity and recording content. Optionally, the recording opportunity can include receiving a first uplink data through the N3 interface, or the source IP address has changed compared to the latest recorded IP address. Optionally, the recording content can include the source IP address of the received uplink data packet having the matching GTP tunnel information.

[0522] In some embodiments, the first uplink data received through the N3 interface can be uplink user data from the UE or uplink data generated by the MWAB-gNB.

[0523] In some embodiments, the uplink data received through the N3 interface can be uplink user data from the UE or uplink data generated by the MWAB-gNB. Optionally, the uplink data generated by the MWAB-gNB can be a specific GTP-U signaling message (e.g., tunnel status, error indication, or new GTP-U signaling message) or a pseudo g-PDU message (e.g., empty GTP-U message).

[0524] S10-S11. The SMF sends a PDU session establishment accept to the UE via the AMF through the MWAB-gNB, and sends an N2 message to the MWAB-gNB, which carries an N2 PDU session request (N2 PDU Session Request) with CN tunnel information.

[0525] Optionally, the messages between the AMF and the MWAB-gNB are transmitted through the BH PDU session.

[0526] Optionally, the indication information can be included to indicate that the specific uplink data generated via the MWAB-gNB includes a specific GTP-U signaling message (e.g., tunnel status, error indication, or new GTP-U signaling message) or a pseudo g-PDU message.

[0527] S12. MWAB gNB to UE: The (R)AN can send AN specific signaling exchange to the UE including the relevant information received from the SMF.

[0528] S13. Optionally, for N3 access implemented through the backhaul path to exchange user plane data for the PDU session through the backhaul path triggers the BH PDU session modification / establishment to access the serving UE UPF.

[0529] S14. The N2 PDU session response is sent from the MWAB-gNB to the UE AMF. Optionally, the response can include AN tunnel information (AN Tunnel Info) for MWAB access. Optionally, the response can be an N2 PDU Session Response.

[0530] S15. The first uplink user data from the UE is sent to the UE UPF using the CN tunnel information received in step S11, or if there is no user data from the UE, uplink data can be generated by the MWAB-gNB, wherein the uplink data can be a specific GTP-U signaling message (e.g., tunnel status, error indication, or new GTP-U signaling message) or a pseudo g-PDU message.

[0531] In some embodiments, the information indicating the data packet whose BH peer address information is detected by the UE UPF from the WMAB-gNB can comprise the information used to identify the data packet whose PDU session is sent as described in step S8.

[0532] Optionally, the CN tunnel information can be replaced by the information used to identify the data packet other than the CN tunnel information described in step 8.

[0533] S16. The UE UPF (which can correspond to the first network function in the foregoing) detects the uplink data received through the N3 interface in step S15, and records the source address information of the received data packet with matching GTP tunnel information.

[0534] S17. The UE AMF invokes the Nsmf_PDUSession_UpdateSMContext Request service to send the AN tunnel information received in step S14 to the UE SMF.

[0535] S18. The UE SMF initiates the N4 session modification procedure with the UE UPF.

[0536] Optionally, the UE SMF provides the AN tunnel information received in step S17 to the UE UPF.

[0537] The information related to the processing of the associated downlink user data packet using dynamic BH peer address information as described in step S9 can also be included in this step.

[0538] In some embodiments, the dynamic BH peer address information comprises information of the associated data packet processing rule for the detection of the BH peer address, for indicating the use of the corresponding BH peer address for encapsulating the downlink user data.

[0539] Optionally, the data packet processing rule comprises: the downlink user plane data packet on the N3 interface is encapsulated with the BH peer address, wherein the BH peer address information is the address information of the BH peer address associated with the indicated data packet processing rule.

[0540] Optionally, the AN tunnel information can comprise the address information of the MWAB-gNB and / or the MWAB-UE, and the BH peer address is used for the encapsulation of the downlink user plane data packet.

[0541] Optionally, the address information of the MWAB-gNB and the MWAB-UE can be the same or different.

[0542] S19. The UE AMF is sent an Nsmf_PDUSession_UpdateSMContext response.

[0543] S20. Uplink and downlink data for the PDU session is transmitted via the BH PDU session for N3 access, which uses the updated BH peer address for packet transfer over N3.

[0544] S21. An IP address change / removal / insertion of the MWAB-UE for the BH session accessing the UE UPF is triggered.

[0545] S22. After the IP address change of the MWAB-UE for the BH session accessing the UE UPF, uplink data as described in step S15 is sent to the UE UPF over N3.

[0546] S23. The UE UPF detects the IP address change of the MWAB-UE for the BH session accessing the UE UPF based on the N3 uplink data received in step S22, then records the updated source address information of the received packets including the matching GTP tunnel information, and updates the associated downlink user plane packet processing rules with the updated BH peer address.

[0547] S24. Uplink and downlink data for the PDU session is transmitted via the BH PDU session for N3 access, which uses the updated BH peer address for packet transfer over N3.

[0548] In some embodiments, if the NG-RAN node (e.g., MWAB above) supports a Service-Based Interface (SBI) interface with the AMF, the above solution can also be applied.

[0549] In some embodiments, if the first terminal has an existing session that is switched from accessing the first node to accessing a non-first node, or is switched between different first nodes, the above corresponding method occurs in the session modification procedure.

[0550] In some embodiments, if the first terminal has an existing session that is switched from accessing the first node to accessing a non-first node, the processing rule of the packet configured in the above corresponding method can be cancelled or no packet meeting the rule can be received.

[0551] FIG. 8a is a structural schematic diagram of a communication device 7100 according to an embodiment of the present disclosure. The communication device 7100 can be a network device (for example, an access network device, a core network device, etc.), a terminal (for example, a user equipment, etc.), a chip, a chip system, or a processor supporting the network device to implement any of the above methods, or a chip, a chip system, or a processor supporting the terminal to implement any of the above methods. The communication device 7100 can be used to implement the methods described in the above method embodiments, and details can be referred to the descriptions in the above method embodiments.

[0552] As shown in FIG. 8a, the communication device 7100 includes one or more processors 7101. The processor 7101 can be a general purpose processor or a special purpose processor, for example, a baseband processor or a central processing unit. The baseband processor can be used to process communication protocols and communication data, and the central processing unit can be used to control the communication device (for example, a base station, a baseband chip, a terminal device, a terminal device chip, a DU or a CU, etc.), execute programs, and process data of the programs. The processor 7101 is used to invoke instructions to enable the communication device 7100 to perform any of the above methods.

[0553] In some embodiments, the communication device 7100 further includes one or more transceivers 7103. When the communication device 7100 includes one or more transceivers 7103, the transceiver 7103 performs at least one of the communication steps (for example, at least one of steps S201 and S203 shown in FIG. 2, but not limited to this) in the above method, and the processor 7101 performs at least one of the other steps (for example, at least one of steps S202 and S204 shown in FIG. 2, but not limited to this). In alternative embodiments, the transceiver can include a receiver and / or a transmitter, which can be separate or integrated together. Alternatively, the terms of transceiver, transceiving unit, transceiver, transceiving circuit, interface circuit, interface, etc. can be replaced with each other, and the terms of transmitter, transmitting unit, transmitter, transmitting circuit, etc. can be replaced with each other, and the terms of receiver, receiving unit, receiver, receiving circuit, etc. can be replaced with each other.

[0554] In some embodiments, the communication device 7100 further includes one or more memories 7102 for storing instructions. Alternatively, all or part of the memory 7102 can also be outside the communication device 7100.

[0555] In some embodiments, the transceiver can include a receiver and a transmitter, which can be separate or integrated together. Optionally, the terms transceiver, transceiving unit, transceiver, transceiving circuit, etc. can be replaced by each other, the terms transmitter, transmitting unit, transmitter, transmitting circuit, etc. can be replaced by each other, and the terms receiver, receiving unit, receiver, receiving circuit, etc. can be replaced by each other.

[0556] Optionally, the communication device 7100 further includes one or more interface circuits 7104 connected with the memory 7102, which can be used to receive signals from the memory 7102 or other devices, and can be used to send signals to the memory 7102 or other devices. For example, the interface circuit 7104 can read the instructions stored in the memory 7102 and send the instructions to the processor 7101.

[0557] The communication device 7100 described in the above embodiments can be a network device or a terminal, but the scope of the communication device 7100 described in the embodiments of the present disclosure is not limited to this. The structure of the communication device 7100 can not be limited by Figure 8a. The communication device can be an independent device or a part of a larger device. For example, the communication device can be: 1) an independent integrated circuit (IC), or a chip, or a chip system or subsystem; (2) a set of one or more ICs, which can optionally include storage components for storing data and programs; (3) an ASIC, such as a modem; (4) a module that can be embedded in other devices; (5) a receiver, terminal device, intelligent terminal device, cellular phone, wireless device, handset, mobile unit, vehicle-mounted device, network device, cloud device, artificial intelligence device, etc.; (6) other devices, etc.

[0558] Figure 8b is a structural schematic diagram of a chip 7200 according to an embodiment of the present disclosure. For the case where the communication device 7100 is a chip or a chip system, the structural schematic diagram of the chip 7200 shown in Figure 8b can be referred to, but is not limited thereto.

[0559] The chip 7200 includes one or more processors 7201. The chip 7200 is configured to execute any of the above methods.

[0560] In some embodiments, the chip 7200 further includes one or more interface circuits 7202. Optionally, the terms interface circuit, interface, transceiver pin, etc. can be replaced by each other. In some embodiments, the chip 7200 further includes one or more memories 7203 for storing data. Optionally, all or part of the memory 7203 can be outside the chip 7200. Optionally, the interface circuit 7202 is connected with the memory 7203, the interface circuit 7202 can be used to receive data from the memory 7203 or other devices, the interface circuit 7202 can be used to send data to the memory 7203 or other devices. For example, the interface circuit 7202 can read the data stored in the memory 7203 and send the data to the processor 7201.

[0561] In some embodiments, the interface circuit 7202 performs at least one of the communication steps (for example, at least one of steps S201, S203 shown in FIG. 2, but not limited to this) of transmitting and / or receiving in the above method. The interface circuit 7202 performing at least one of the communication steps of transmitting and / or receiving in the above method refers to, for example, the interface circuit 7202 performing data interaction between the processor 7201, the chip 7200, the memory 7203 or the transceiver device. In some embodiments, the processor 7201 performs at least one of other steps (for example, at least one of steps S202, S204 shown in FIG. 2, but not limited to this).

[0562] The disclosure also proposes a program product, which, when executed by the communication device 7100, causes the communication device 7100 to perform any of the above methods. Optionally, the above program product is a computer program product.

[0563] The disclosure also proposes a computer program, which, when running on a computer, causes the computer to perform any of the above methods.

[0564] The technical solutions described in the embodiments of the disclosure can be combined arbitrarily without conflict.

[0565] Other embodiments of the application will be apparent to those skilled in the art from consideration of the specification and practice of the application disclosed herein. The disclosure is intended to cover any variations, uses or adaptations of the application following, in general, the principles of the application and including such steps that are apparent to those skilled in the art to which the application pertains. The specification and examples are to be regarded as exemplary only, and the true scope and spirit of the application are indicated by the following claims.

[0566] It should be understood that the application is not limited to the precise construction that has been described above and shown in the accompanying drawings, and that various modifications and changes can be made by those skilled in the art without departing from the scope of the application. The scope of the application is indicated only by the appended claims.

Claims

1. A communication method characterized by comprising: The method is performed by a first network function, and the method comprises: receiving a data packet; determining first address information corresponding to a first data packet in the data packet according to first information, and using the first address information for processing of a second data packet; wherein the first address information is used to identify source address information of the first data packet; and the second data packet is a data packet associated with the first data packet.

2. The method of claim 1, wherein, The use of the first address information for processing of the second data packet comprises: encapsulating the second data packet using the first address information.

3. The method according to claim 1 or 2, characterized in that, The first data packet is an uplink user plane data packet transmitted to the first network function via a backhaul path, and the second data packet is a downlink user plane data packet belonging to a same packet data unit (PDU) session as the first data packet.

4. The method of claim 3, wherein, The PDU session is a PDU session of a first terminal accessing the first network function via a first node, and the PDU session is a first session; The backhaul path is a user plane path of a second session, and the second session is a PDU session providing a backhaul path for a terminal part included by the first node.

5. The method of claim 4, wherein, The first address information comprises one of: source address information of the first data packet before an address information of the terminal part providing the backhaul path is changed; and source address information of the first data packet after the address information of the terminal part providing the backhaul path is changed.

6. The method according to any one of claims 1-5, characterized in that, The first information is used to determine at least one of: whether the received data packet is the first data packet; whether the first address information corresponding to the first data packet is met; whether the second data packet associated with the first data packet is met; whether the first address information is used for processing of the second data packet; and whether the second data packet is processed using the first address information.

7. The method of claim 6, wherein, The determination of whether the received data packet is the first data packet comprises: determining, based on first tunnel information, whether the received data packet is the first data packet; or determining, based on second information configured or negotiated between the first node and the second network function, whether the received data packet is the first data packet.

8. The method of claim 7, wherein, The first tunnel information comprises user plane address information associated with the first network function corresponding to the first session.

9. The method of claim 7, wherein, The second information comprises at least one of: a connection identifier of a user plane connection of the first session; an identifier of the first terminal of the first session; specific indication information used to indicate a user plane connection between the first node and the first network function of the first session; and a specific identifier used to identify a user plane connection between the first node and the first network function of the first session.

10. The method according to any one of claims 1-9, characterized in that, The first data packet comprises at least one of: a user data packet of the first terminal accessing the network via the first node; and a specific data packet generated by the first node.

11. The method of claim 10, wherein, The specific data packet comprises at least one of: a user plane signaling message of a specific tunnel protocol; and an empty user plane message of a tunnel protocol.

12. The method according to any one of claims 1-11, characterized in that, The method further comprises: obtaining the first information sent by the second network function through a first request message, the first request message being used to manage a user plane path of the first session.

13. The method according to any one of claims 1-12, characterized in that, The method further comprises: determine the first data packet and the second data packet based on the first information.

14. The method according to any one of claims 4-13, characterized in that, The first node is a mobile base station with wireless backhaul, the first node includes a base station part of the mobile base station with wireless backhaul, and / or the first node includes a terminal part with wireless backhaul.

15. A method of communication, comprising: The method is performed by a second network function, and the method comprises: sending first information to a first network function; wherein the first information is used to determine first address information corresponding to a first data packet in a data packet received by the first network function, and to determine that the first address information is used for processing of a second data packet; wherein the first address information is used to identify source address information of the first data packet; and the second data packet is a data packet associated with the first data packet.

16. The method of claim 15, wherein, The second data packet is encapsulated using the first address information.

17. The method of claim 15 or 16, wherein, the first data packet is an uplink user plane data packet transmitted to the first network function via a backhaul path; the second data packet is a downlink user plane data packet belonging to a same packet data unit (PDU) session as the first data packet.

18. The method of claim 17, wherein, The PDU session is a PDU session of a first terminal accessing the first network function via a first node, and the PDU session of the first terminal is a first session; The backhaul path is a user plane path of a second session, and the second session is a PDU session for which a terminal part included in the first node provides a backhaul path.

19. The method of claim 18, wherein, The first address information includes one of: source address information of the first data packet before an address of the terminal part providing the backhaul path is changed; source address information of the first data packet after the address of the terminal part providing the backhaul path is changed.

20. The method of any one of claims 15-19, wherein, The first information is used to determine at least one of: whether the received data packet is the first data packet; compliance with the first address information corresponding to the first data packet; the second data packet associated with the first data packet; whether the first address information is used for processing of the second data packet; processing the second data packet using the first address information.

21. The method of claim 20, wherein, The determination of whether the received data packet is the first data packet comprises: determining, based on first tunnel information, whether the received data packet is the first data packet; or determining, based on second information configured or negotiated between the first node and the second network function, whether the received data packet is the first data packet.

22. The method of claim 21, wherein, The first tunnel information includes user plane address information associated with the first network function corresponding to the first session.

23. The method of claim 21, wherein, The second information includes at least one of: a connection identifier of a user plane connection of the first session; an identifier of the first terminal of the first session; specific indication information indicating a user plane connection between the first node and the first network function of the first session; a specific identifier identifying a user plane connection between the first node and the first network function of the first session.

24. The method of any one of claims 15-23, wherein, The first data packet includes at least one of: a user data packet of a first terminal accessing a network via a first node; a specific data packet generated by the first node.

25. The method of claim 24, wherein, The specific data packet comprises at least one of: a user plane signaling message of a specific tunnel protocol; an empty user plane message of a tunnel protocol.

26. The method of any one of claims 15-25, wherein, The sending of the first information to the first network function comprises: sending the first information to the first network function through a first request message, the first request message being used for managing a user plane path of the first session.

27. The method of any one of claims 18-26, wherein, The first node is a mobile base station with wireless backhaul, the first node comprises a base station part of the mobile base station with wireless backhaul, and / or the first node comprises a terminal part with wireless backhaul.

28. A communication system, characterized by Comprise: a first network function and a second network function, wherein the first network function receives a data packet and the second network function sends first information; the first network function determines first address information corresponding to a first data packet in the data packet according to the first information, and uses the first address information for processing of a second data packet; wherein the first address information is used for identifying source address information of the first data packet; the second data packet is a data packet associated with the first data packet.

29. The system of claim 28, wherein, The first network function encapsulates the second data packet using the first address information.

30. A first network function, the first network function comprising: Comprise: a first transceiver module, configured to receive a data packet; a first processing module, configured to determine first address information corresponding to a first data packet in the data packet according to first information, and use the first address information for processing of a second data packet; wherein the first address information is used for identifying source address information of the first data packet; the second data packet is a data packet associated with the first data packet.

31. A second network function, characterized in that, Comprise: a second transceiver module, configured to send first information to a first network function; wherein the first information is used for determining first address information corresponding to a first data packet in a data packet received by the first network function, and determining that the first address information is used for processing of a second data packet; wherein the first address information is used for identifying source address information of the first data packet; the second data packet is a data packet associated with the first data packet.

32. A communications device, characterized by Comprise: one or more processors; wherein the processor is configured to perform the communication method of any one of claims 1 to 14.

33. A communications device, characterized by Comprise: one or more processors; wherein the processor is configured to perform the communication method of any one of claims 15 to 27.

34. A computer-readable storage medium, characterized in that, The computer readable storage medium stores executable instructions, the executable instructions are loaded and executed by the processor to implement the method of any one of claims 1 to 14, or 15 to 27.

Images