Communication method, device, system and storage medium

Abstract

The embodiment of the invention discloses a communication method and device and a computer readable storage medium, and relates to the technical field of communication. The communication method comprises the following steps: receiving a data packet; first address information corresponding to a first data packet in the data packets is determined according to the first information, and the first address information is used for processing 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. Through configured first information, first address information corresponding to a first data packet in received data packets can be determined, a first address is used for processing a second data packet associated with the first data packet, and the first address information identifies source address information of the first data packet. Therefore, session management of the terminal accessing the network through the MWAB can be supported.

Description

Technical Field

[0001] This disclosure relates to the field of communication technology, and more specifically, to a communication method, device, system, and storage medium. Background Art

[0002] A Mobile gNB with wireless access backhaul (MWAB) refers to a mobile base station that acts as a next-generation NodeB (gNB) for other terminals, providing access to networks such as 5G networks. Specifically, the MWAB provides a 5G New Radio (NR) access link to the terminal and uses an Internet Protocol (IP) connection (i.e., the backhaul path) provided by a Protocol Data Unit (PDU) session to wirelessly connect to the 5G core network (5G core, 5GC). The PDU session that establishes the backhaul path is called a Backhaul Protocol Data Unit (BH PDU) session. The BH PDU session is established through an NG-RAN cell where the mobile base station can reside. The BH PDU session can be provided by either a terrestrial or non-terrestrial network. This type of mobile base station can be installed on moving vehicles and provide services to users located inside or outside the moving vehicle (or entering / leaving the vehicle). Summary of the Invention

[0003] This disclosure provides a communication method, device, system, and storage medium.

[0004] A first aspect of this disclosure provides a communication method, the method being executed by a first network function, the method comprising:

[0005] Receive data packets;

[0006] The first address information corresponding to the first data packet in the data packet is determined based on the first information, and the first address information is used for the processing of the second data packet;

[0007] Wherein, the first address information is used to identify the source address information of the first data packet; the second data packet is a data packet associated with the first data packet.

[0008] A second aspect of this disclosure provides a communication method, the method being executed by a second network function, the method comprising:

[0009] Send the first message to the first network function;

[0010] Wherein, the first information is used to determine the first address information corresponding to the first data packet in the data packet received by the first network function, and to determine to use the first address information for the processing of the second data packet;

[0011] Wherein, the first address information is used to identify the source address information of the first data packet; the second data packet is a data packet associated with the first data packet.

[0012] A third aspect of this disclosure provides a first network function, including:

[0013] The first transceiver module is used to receive data packets;

[0014] The first processing module is used to determine the first address information corresponding to the first data packet in the data packet according to the first information, and use the first address information for processing the second data packet;

[0015] Wherein, the first address information is used to identify the source address information of the first data packet; the second data packet is a data packet associated with the first data packet.

[0016] A fourth aspect of this disclosure provides a second network function, including:

[0017] The second transceiver module is used to send the first information to the first network function;

[0018] Wherein, the first information is used to determine the first address information corresponding to the first data packet in the data packet received by the first network function, and to determine to use the first address information for the processing of the second data packet;

[0019] Wherein, the first address information is used to identify the source address information of the first data packet; the second data packet is a data packet associated with the first data packet.

[0020] A fifth aspect of this disclosure provides a communication device, comprising:

[0021] one or more processors;

[0022] The processor is used to execute an optional implementation of the first aspect described above.

[0023] A sixth aspect of this disclosure provides a communication device, comprising:

[0024] one or more processors;

[0025] The processor is used to execute an optional implementation of the second aspect described above.

[0026] A seventh aspect of this disclosure provides a communication system, comprising: a first network function and a second network function, wherein...

[0027] The first network function receives data packets and the first information sent by the second network function;

[0028] The first network function determines the first address information corresponding to the first data packet in the data packet based on the first information, and uses the first address information for processing the second data packet;

[0029] Wherein, the first address information is used to identify the source address information of the first data packet; the second data packet is a data packet associated with the first data packet.

[0030] An eighth aspect of this disclosure provides a communication system including a first network function and a second network function, wherein the first network function is used to implement the method described in an optional embodiment of the first aspect, and the second network function is used to implement the method described in an optional embodiment of the second aspect.

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

[0032] It is to be understood that the foregoing general description and the following detailed description are exemplary and explanatory only and are not restrictive of the disclosure. Attached Figure Description

[0033] The accompanying drawings, which are incorporated in and form part of this specification, illustrate embodiments consistent with the invention and, together with the description, serve to explain the principles of the invention.

[0034] Figure 1a This is a schematic diagram illustrating the structure of a wireless communication system according to an exemplary embodiment;

[0035] Figure 1b This is a schematic diagram illustrating the structure of a wireless communication system according to an exemplary embodiment;

[0036] Figure 1c This is a schematic diagram illustrating a session management process according to an exemplary embodiment;

[0037] Figure 2 This is a flowchart illustrating a communication method according to an exemplary embodiment;

[0038] Figure 3a This is a schematic flowchart illustrating the communication method according to an embodiment of this disclosure;

[0039] Figure 3b This is a schematic flowchart illustrating the communication method according to an embodiment of this disclosure;

[0040] Figure 4 This is a schematic flowchart illustrating the communication method according to an embodiment of this disclosure;

[0041] Figure 5 This is a schematic flowchart illustrating the communication method according to an embodiment of this disclosure;

[0042] Figure 6a This is a schematic diagram of the structure of the first network function proposed in the embodiments of this disclosure;

[0043] Figure 6b This is a schematic diagram of the structure of the second network function proposed in the embodiments of this disclosure;

[0044] Figure 7 This is a flowchart illustrating a communication method according to an exemplary embodiment;

[0045] Figure 8a This is a schematic diagram of the structure of the communication device proposed in the embodiments of this disclosure;

[0046] Figure 8b This is a schematic diagram of the chip structure proposed in the embodiments of this disclosure. Detailed Implementation

[0047] This disclosure provides communication methods, devices, communication systems, and storage media.

[0048] In a first aspect, embodiments of this disclosure provide a communication method, the method being executed by a first network function, the method comprising:

[0049] Receive data packets;

[0050] The first address information corresponding to the first data packet in the data packet is determined based on the first information, and the first address information is used for the processing of the second data packet;

[0051] Wherein, the first address information is used to identify the source address information of the first data packet; the second data packet is a data packet associated with the first data packet.

[0052] In the above embodiments, the first address information corresponding to the first data packet in the received data packet can be determined through the first information, and the first address is used for processing the 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 terminals accessing the network via MWAB.

[0053] In conjunction with some embodiments of the first aspect, in some embodiments, using the first address information for processing the second data packet includes: encapsulating the second data packet using the first address information.

[0054] In the above embodiments, the data packet processing rules for the session of a terminal accessing the network via MWAB are configured through the second network function, thereby enabling the correct transmission of data packets for the session of a terminal accessing the network via MWAB.

[0055] In conjunction with some embodiments of 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 the same Packet Data Unit (PDU) session as the first data packet.

[0056] In conjunction with some embodiments of the first aspect, in some embodiments, the PDU session is a PDU session of a first terminal accessing the first network function through a first node, and the PDU session is a first session;

[0057] The backhaul path is the user plane path of the second session, which is a PDU session in which the backhaul path is provided by the terminal portion included in the first node.

[0058] In the above embodiments, the first data packet of the session transmitted through the backhaul path is used to determine the associated second data packet, and the address of the first data packet is used for the transmission of the second data packet, thereby enabling the correct transmission of data packets of the session of the terminal accessing the network via MWAB.

[0059] In conjunction with some embodiments of the first aspect, in some embodiments, the address information includes an IP address and / or a port number.

[0060] In conjunction with some embodiments of the first aspect, in some embodiments, the first address information includes one of the following:

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

[0062] Provides the source address information of the first data packet after the address information of the terminal portion of the backhaul path has been changed.

[0063] In conjunction with some embodiments of the first aspect, in some embodiments, the first address information corresponding to the packet;

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

[0065] Whether to use the first address information for processing the second data packet;

[0066] The second data packet is processed using the first address information.

[0067] In the above embodiments, by configuring the detection and processing conditions of the received data packets, the source address information of the first data packet that meets the detection conditions can be accurately obtained, and the source address information can be used for the processing of the second data packet.

[0068] In conjunction with some embodiments of the first aspect, in some embodiments, determining whether the received data packet is the first data packet includes:

[0069] Based on the first tunnel information, determine whether the received data packet is the first data packet; or

[0070] Based on the second information configured or negotiated between the first node and the second network function, it is determined whether the received data packet is the first data packet.

[0071] In the above embodiments, by using tunnel information or information negotiated between the first node and the second network function as detection conditions, the first data packet that meets the detection conditions can be accurately obtained.

[0072] In conjunction with some embodiments of the first aspect, in some embodiments, the first tunnel information includes user plane tunnel information associated with the first network function corresponding to the first session.

[0073] In the above embodiments, 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 is used as the detection condition, so that the first data packet that meets the detection condition can be accurately obtained.

[0074] In conjunction with some embodiments of the first aspect, in some embodiments, the second information includes at least one of the following:

[0075] The connection identifier of the user plane connection in the first session;

[0076] The identifier of the first terminal in the first session;

[0077] Specific indication information is used to indicate the user plane connection between the first node of the first session and the first network function;

[0078] A specific identifier is used to identify the user plane connection between the first node of the first session and the first network function.

[0079] In conjunction with some embodiments of the first aspect, in some embodiments, the first data packet includes at least one of the following:

[0080] User data packets from the first terminal that accesses the network through the first node;

[0081] A specific data packet, which is generated by the first node.

[0082] In the above embodiments, the first data packet can be a user data packet of the first terminal accessing the network via the first node, or, if the user data packet of the first terminal is not received, it can be a specific data packet generated by the first node, thereby flexibly triggering the process of the first terminal accessing the network via the first node.

[0083] In conjunction with some embodiments of the first aspect, in some embodiments, the specific data packet includes at least one of the following:

[0084] User plane signaling messages specific to the tunneling protocol;

[0085] Empty tunnel protocol user plane messages.

[0086] In conjunction with some embodiments of the first aspect, in some embodiments, the method further includes:

[0087] The first request message is used to obtain the first information sent by the second network function. The first request message is used to manage the user plane path of the packet data unit (PDU) session of the first terminal accessing the network via the first node.

[0088] In the above embodiments, by sending the first information to the first network function through the request message for managing the user plane path of the PDU session of the first terminal accessing the network via the first node, the deployment mode of the network system can be better adapted.

[0089] In conjunction with some embodiments of the first aspect, in some embodiments, the method further includes:

[0090] Based on the first information, the first data packet and the second data packet are determined.

[0091] In the above embodiments, after obtaining the processing rules 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 conform to the processing rules can be determined from the received data packets so as to obtain the first address information of the first data packet and use the first address information for the processing of the second data packet, thereby realizing the transmission of data packets of the PDU session of the first terminal.

[0092] In conjunction with some embodiments of the first aspect, in some embodiments, the first node is a mobile base station with wireless backhaul, the first node including a base station portion of the mobile base station with wireless backhaul, and / or a terminal portion with wireless backhaul.

[0093] Secondly, embodiments of this disclosure provide a communication method, which is executed by a second network function, the method comprising:

[0094] Send the first message to the first network function;

[0095] Wherein, the first information is used to determine the first address information corresponding to the first data packet in the data packet received by the first network function, and to determine to use the first address information for the processing of the second data packet;

[0096] Wherein, the first address information is used to identify the source address information of the first data packet; the second data packet is a data packet associated with the first data packet.

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

[0098] In conjunction with 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;

[0099] 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.

[0100] In conjunction with 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 through the first node, and the PDU session is a first session;

[0101] The backhaul path is the user plane path of the second session, which is a PDU session in which the backhaul path is provided by the terminal portion included in the first node.

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

[0103] In conjunction with some embodiments of the second aspect, in some embodiments, the first address information includes one of the following:

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

[0105] Provides the source address information of the first data packet after the address information of the terminal portion of the backhaul path has been changed.

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

[0107] Is the received data packet the first data packet?

[0108] It conforms to the first address information corresponding to the first data packet;

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

[0110] Whether to use the first address information for processing the second data packet;

[0111] The second data packet is processed using the first address information.

[0112] In conjunction with some embodiments of the second aspect, in some embodiments, determining whether the received data packet is the first data packet includes:

[0113] Based on the first tunnel information, determine whether the received data packet is the first data packet; or,

[0114] Based on the second information configured or negotiated between the first node and the second network function, it is determined whether the received data packet is the first data packet.

[0115] In conjunction with some embodiments of the second aspect, in some embodiments, the first tunnel information includes user plane tunnel information corresponding to the first session and associated with the first network function.

[0116] In conjunction with some embodiments of the second aspect, in some embodiments, the second information includes at least one of the following:

[0117] The connection identifier of the user plane connection in the first session;

[0118] The identifier of the first terminal in the first session;

[0119] Specific indication information is used to indicate the user plane connection between the first node of the first session and the first network function;

[0120] A specific identifier is used to identify the user plane connection between the first node of the first session and the first network function.

[0121] In conjunction with some embodiments of the second aspect, in some embodiments, the first data packet includes at least one of the following:

[0122] User data packets from the first terminal that accesses the network through the first node;

[0123] A specific data packet, which is generated by the first node.

[0124] In conjunction with some embodiments of the second aspect, in some embodiments, the specific data packet includes at least one of the following:

[0125] User plane signaling messages specific to the tunneling protocol;

[0126] Empty tunnel protocol user plane messages.

[0127] In conjunction with some embodiments of the second aspect, in some embodiments, the first information sent to the first network function includes:

[0128] The first request message is used to send first information to the first network function to manage the user plane path of the first session.

[0129] In conjunction with some embodiments of the second aspect, in some embodiments, the first node is a mobile base station with wireless backhaul, the first node includes a base station portion of the mobile base station with wireless backhaul, and / or, the first node includes a terminal portion with wireless backhaul.

[0130] Thirdly, embodiments of this disclosure propose a first network function, including:

[0131] The first transceiver module is used to receive data packets;

[0132] The first processing module is used to determine the first address information corresponding to the first data packet in the data packet according to the first information, and use the first address information for processing the second data packet;

[0133] Wherein, the first address information is used to identify the source address information of the first data packet; the second data packet is a data packet associated with the first data packet.

[0134] Fourthly, embodiments of this disclosure propose a second network function, including:

[0135] The second transceiver module is used to send the first information to the first network function;

[0136] Wherein, the first information is used to determine the first address information corresponding to the first data packet in the data packet received by the first network function, and to determine to use the first address information for the processing of the second data packet;

[0137] Wherein, the first address information is used to identify the source address information of the first data packet; the second data packet is a data packet associated with the first data packet.

[0138] Fifthly, embodiments of this disclosure provide a communication device, including:

[0139] one or more processors;

[0140] The processor is used to execute an optional implementation of the first aspect described above.

[0141] Sixthly, embodiments of this disclosure provide a communication device, including:

[0142] one or more processors;

[0143] The processor is used to execute an optional implementation of the second aspect described above.

[0144] In a seventh aspect, embodiments of this disclosure provide a communication system, including: a first network function and a second network function, wherein,

[0145] The first network function receives data packets and the first information sent by the second network function;

[0146] The first network function determines the first address information corresponding to the first data packet in the data packet based on the first information, and uses the first address information for processing the second data packet;

[0147] Wherein, the first address information is used to identify the source address information of the first data packet; the second data packet is a data packet associated with the first data packet.

[0148] In conjunction with some embodiments of the seventh aspect, in some embodiments, the first network function uses the first address information to encapsulate the second data packet.

[0149] Eighthly, embodiments of this disclosure provide a communication system including a first network function and a second network function, wherein the first network function is used to implement the method described in the optional embodiments of the first aspect, and the second network function is used to implement the method described in the optional embodiments of the second aspect.

[0150] In a ninth aspect, embodiments of this disclosure provide a computer-readable storage medium storing executable instructions that are loaded and executed by the processor to implement the methods described in the optional embodiments of the first or second aspect.

[0151] In a tenth aspect, embodiments of this disclosure provide a program product that, when executed by a communication device, causes the communication device to perform the method as described in an optional implementation of the first or second aspect.

[0152] In one aspect, embodiments of this disclosure provide a computer program that, when run on a computer, causes the computer to perform the methods described in an optional implementation of the first or second aspect.

[0153] In a twelfth aspect, embodiments of this disclosure provide a chip or chip system including processing circuitry for performing the method described in an optional implementation of the first or second aspect above.

[0154] Understandably, the aforementioned devices, communication equipment, communication systems, storage media, program products, and computer programs for random access are all used to execute the methods proposed in the embodiments of this disclosure. Therefore, the beneficial effects they can achieve can be referred to the beneficial effects in the corresponding methods, and will not be repeated here. The communication equipment can be a terminal or a network device.

[0155] This disclosure provides communication methods, apparatus, devices, systems, and storage media.

[0156] In some embodiments, the terms communication method and information processing method, and for random access can be used interchangeably; the terms device for random access and information processing device, communication device, etc., can be used interchangeably; and the terms information processing system, communication system, etc., can be used interchangeably.

[0157] This disclosure is not exhaustive, but merely illustrative of some embodiments, and is not intended to limit the scope of protection of the embodiments disclosed. Unless otherwise specified, each step in a particular embodiment can be implemented as an independent embodiment, and the steps can be arbitrarily combined. For example, a solution after removing some steps in a particular embodiment can also be implemented as an independent embodiment, and the order of the steps in a particular embodiment can be arbitrarily interchanged. Furthermore, the optional implementation methods in a particular embodiment can be arbitrarily combined; moreover, the embodiments can be arbitrarily combined, for example, some or all steps of different embodiments can be arbitrarily combined, and a particular embodiment can be arbitrarily combined with the optional implementation methods of other embodiments.

[0158] In each embodiment of the present disclosure, unless otherwise specified or provided for by logic, the terms and / or descriptions between the embodiments are consistent and can be referenced by each other. The technical features in different embodiments can be combined to form a new embodiment based on their inherent logical relationships.

[0159] The terminology used in the embodiments of this disclosure is for the purpose of describing particular embodiments only and is not intended to limit the embodiments of this disclosure.

[0160] In the embodiments of the present disclosure, unless otherwise specified, elements expressed in the singular, such as "a", "an", "the", "above", "said", "the", "the", etc., may mean "one and only one", or "one or more", "at least one", etc. For example, when using articles such as "a", "an", "the" in English in translation, the noun following the article may be understood as a singular expression or a plural expression.

[0161] In the embodiments of the present disclosure, “plurality” refers to two or more.

[0162] In some embodiments, the terms “at least one of”, “at least one of”, “at least one of”, “one or more”, “a plurality of”, “multiple”, etc., may be used interchangeably.

[0163] The descriptions in this disclosure, such as "at least one of A, B, C..." or "A and / or B and / or C...", include the case where any one of A, B, C... exists alone, as well as the case where any combination of any of A, B, C... exists alone. Each case can exist alone. For example, "at least one of A, B, C" includes the cases of A alone, B alone, C alone, A and B combination, A and C combination, B and C combination, and A and B and C combination. For example, A and / or B includes the cases of A alone, B alone, and A and B combination.

[0164] In some embodiments, the notation "in one case A, in another case B" or "in response to one case A, in response to another case B" may include the following technical solutions depending on the situation: A is executed regardless of B, i.e., A is executed in some embodiments; B is executed regardless of A, i.e., B is executed in some embodiments; A and B are selectively executed, i.e., A and B are selected for execution in some embodiments; A and B are both executed, i.e., A and B are executed in some embodiments. The same applies when there are more branches such as A, B, and C.

[0165] The prefixes such as "first" and "second" in the embodiments of the present disclosure are only used to distinguish different description objects and do not constitute any restriction on the position, order, priority, quantity or content of the description objects. For the statement of the description object, please refer to the description in the context of the claims or embodiments, and no unnecessary restriction should be constituted due to the use of prefixes. For example, if the description object is a "field", the ordinal number before the "field" in the "first field" and the "second field" does not limit the position or order between the "fields". "First" and "second" do not limit whether the "fields" they modify are in the same message, nor do they limit the order of the "first field" and the "second field". For another example, if the description object is a "level", the ordinal number before the "level" in the "first level" and the "second level" does not limit the priority between the "levels". For another example, the number of description objects is not limited by the ordinal number and can be one or more. Taking "first device" as an example, the number of "devices" can be one or more. Furthermore, the objects modified by different prefixes can be the same or different. For example, if the object being described is "device", then "first device" and "second device" can be the same device or different devices, and their types can be the same or different. As another example, if the object being described is "information", then "first configuration" and "second configuration" can be the same information or different information, and their content can be the same or different.

[0166] In some embodiments, “including A,” “comprising A,” “used to indicate A,” and “carrying A” can be interpreted as directly carrying A or indirectly indicating A.

[0167] In some embodiments, terms such as "in response to...", "in response to determining...", "in the case of...", "at the time of...", "when...", "if...", "if...", etc. can be used interchangeably.

[0168] In some embodiments, terms such as "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 less than", and "above" can be replaced with each other, and terms such as "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", and "below" can be replaced with each other.

[0169] In some embodiments, devices, etc., can be interpreted as physical or virtual, and their names are not limited to the names recorded in the embodiments. Terms such as “device”, “equipment”, “circuit”, “network element”, “node”, “function”, “unit”, “section”, “system”, “network”, “chip”, “chip system”, “entity”, and “subject” can be used interchangeably.

[0170] 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," and "bandwidth part (BWP)" can be used interchangeably.

[0171] 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 subscriberstation, access terminal, mobile terminal, wireless terminal, remote terminal, handset, user agent, mobile client, and client can be used interchangeably.

[0172] In some embodiments, the access network device, core network device, or network device can be replaced by a terminal. For example, various embodiments of this disclosure can also be applied to structures that replace communication between the access network device, core network device, or network device and the terminal with communication between multiple terminals (e.g., also referred to as device-to-device (D2D), vehicle-to-everything (V2X), etc.). In this case, the terminal can also be configured to have all or part of the functions of the access network device. Furthermore, terms such as "uplink" and "downlink" can be replaced with terms corresponding to communication between terminals (e.g., "side").

[0173] For example, uplink channels and downlink channels can be replaced with side channels, and uplink links and downlink links can be replaced with side links.

[0174] In some embodiments, the terms "uplink", "uplink", and "physical uplink" can be used interchangeably, as can the terms "downlink", "downlink", and "physical downlink", as well as the terms "sidelink", "sidelink", "sidelink communication", "sidelink communication", "direct connection", "direct link", "direct communication", and "direct link communication".

[0175] In some embodiments, the terms “downlink control information (DCI),” “downlink (DL) assignment,” “DL DCI,” “uplink (UL) grant,” and “UL DCI” can be used interchangeably.

[0176] In some embodiments, terms such as "physical downlink shared channel (PDSCH)" and "DL data" can be used interchangeably, as can terms such as "physical uplink shared channel (PUSCH)" and "UL data".

[0177] In some embodiments, the determination or judgment can be performed 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.

[0178] In some embodiments, "network" can be interpreted as devices included in a network (e.g., access network devices, core network devices, etc.).

[0179] In some embodiments, obtaining data, information, etc. may comply with the laws and regulations of the country where the data is obtained.

[0180] In some embodiments, data, information, etc. may be obtained with the user's consent.

[0181] Figure 1a It is a schematic diagram of the architecture of a communication system according to an embodiment of the present disclosure.

[0182] like Figure 1a As shown, the communication system 100 includes a terminal 101 and a network device 102 .

[0183] In some embodiments, the terminal 101 includes, for example, a mobile phone, a wearable device, an Internet of Things device, a car with communication function, a smart car, a tablet computer, a computer with wireless transceiver function, 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, and at least one of a wireless terminal device in a smart home, but is not limited thereto.

[0184] In some embodiments, network device 102 may include at least one of access network device and core network device.

[0185] In some embodiments, the access network device is, for example, a node or device that connects a terminal to a wireless network. The network device may include, but is not limited to, at least one of the following in a 5G communication system: evolved Node B (eNB), next-generation eNB (ng-eNB), next-generation Node B (gNB), node B (NB), home node B (HNB), home evolved node B (HeNB), wireless backhaul device, radio network controller (RNC), base station controller (BSC), base transceiver station (BTS), base band unit (BBU), mobile switching center, base station in a 6G communication system, open RAN, cloud RAN, base station in other communication systems, and access node in a wireless fidelity (WiFi) system.

[0186] In some embodiments, the technical solutions of this disclosure can be applied to the Open RAN architecture. In this case, the interfaces between or within network devices involved in the embodiments of this disclosure can be transformed into internal interfaces of Open RAN. The processes and information interactions between these internal interfaces can be implemented by software or programs.

[0187] In some embodiments, the access network device may be composed of a central unit (CU) and a distributed unit (DU). The CU may also be called a control unit. The CU-DU structure can separate the protocol layer of the network device. Some of the protocol layer functions are centrally controlled by the CU, while the remaining part or all of the protocol layer functions are distributed in the DU and centrally controlled by the CU. However, this is not the only possibility.

[0188] In some embodiments, the access network device may be a single device, multiple devices, or a group of devices, including all or part of a first network element, a second network element, etc. Network elements may be virtual or physical. Network devices may include, for example, at least one of an Evolved Packet Core (EPC), a 5G Core Network (5GCN), and a Next Generation Core (NGC).

[0189] In some embodiments, a core network device may be a single device comprising one or more network elements, or it may be multiple devices or a group of devices, each comprising all or part of the aforementioned one or more network elements. Network elements may be virtual or physical. The core network may include, for example, at least one of an Evolved Packet Core (EPC), a 5G Core Network (5GCN), or a Next Generation Core (NGC).

[0190] In some embodiments, terminal 101 accesses the core network via a radio access network ((R)AN), the core network including user plane network elements and control plane network elements. The user plane network elements of the core network include user plane functions (UPF); the control plane network elements of the core network include at least one of the following: authentication server function (AUSF), AMF, SMF, network slice selection function (NSSF), network exposure function (NEF), network function repository function (NRF), unified data management (UDM), PCF, and AF.

[0191] User plane network elements (such as UPF) are mainly responsible for packet forwarding, quality of service (QoS) control, and billing information statistics. Control plane network elements are mainly responsible for service process interaction, issuing packet forwarding policies and QoS control policies to the user plane, etc.

[0192] In some embodiments, the control plane of the core network can adopt a service-oriented architecture, that is, the interaction between control plane network elements adopts a service call approach to replace the point-to-point communication method in the traditional architecture. In a service-oriented architecture, a control plane network element exposes services to other control plane network elements for them to call; in point-to-point communication, the communication interface between control plane network elements has a specific set of messages that can only be used by the control plane network elements at both ends of the interface during communication.

[0193] The functions of the network elements in the 5G core network involved in this embodiment are described below:

[0194] UPF performs user packet forwarding according to the routing rules of SMF, such as sending uplink data to the data network (DN) or other UPF, and forwarding downlink data to other UPF or (R)AN.

[0195] AUSF performs security authentication for the UE.

[0196] The AMF (Access and Mobility Management Function) is responsible for maintaining the UE's state, managing the UE's reachability, forwarding non-access-stratum (NAS) messages (mobility management, MM), and forwarding N2 messages (session management, SM).

[0197] SMF (Session Management Function) allocates and releases resources for the UE's sessions. These resources include session quality of service (QoS), session paths, forwarding rules, etc.

[0198] NSSF selects a network slice for the UE.

[0199] NEF exposes its network functionality to third parties via a northbound application programming interface (API).

[0200] NRF provides other network elements with the functions of storing and selecting network function entity information.

[0201] UDM is used for user subscription context management.

[0202] PCF (Policy Control Function) is used to generate and manage user, session, and QoS stream processing policies.

[0203] Application Management (AF) is a functional network element that provides various service functions. It can interact with the core network through the NEF and with the policy management framework for policy management.

[0204] The interfaces between 5G network element functions involved in the embodiments of this disclosure include:

[0205] N1: The interface between the UE and the core network control plane.

[0206] N2: Communication interface between access network (AN) elements and core network control plane.

[0207] N3: Communication interface between access network elements and UPF, used for transmitting user data.

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

[0209] N6: Communication port between UPF and data network (DN).

[0210] This disclosure also relates to mobile gNBs with wireless access backhaul (MWABs), such as... Figure 1b As shown, the mobile base station acts as a gNB for other UEs and provides access to the 5G network, specifically by providing NR access links to the UEs and wirelessly connecting to the 5GC (using NR) via IP connections established through PDU sessions in NG-RAN cells where the mobile gNB can camp. The PDU sessions are provided by either terrestrial or non-terrestrial networks. Such mobile gNBs can be installed in mobile vehicles and provide services to UEs located inside or outside the vehicle (or entering / leaving the vehicle).

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

[0212] -MWAB consists of a gNB component (MWAB-gNB) and a UE component (MWAB-UE);

[0213] -MWAB gNB has the gNB functionality specified in the existing protocol;

[0214] The N2 / N3 interface of the MWAB-gNB accesses OAM (Operation Administration and Maintenance) via an IP connection provided by the PDU session of the MWAB-UE;

[0215] - If standardization is required, the interface between MWAB-UE and MWAB-gNB is not within the scope of SAWG2;

[0216] -MWAB-UE connects to NG-RAN via a single NR Uu hop (e.g., terminal functions access gNB via NRUu interface that can use terrestrial network TN or non-terrestrial network NTN technologies);

[0217] -MWAB can serve UEs located inside or outside a vehicle equipped with MWAB relay functionality;

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

[0219] - The existing LCS framework is used to provide location services to the UEs it serves;

[0220] -MWAB can connect to NG-RAN of PLMN (Public Land Mobile Network) or SNPN (Stand-alone Non-Public Network);

[0221] -MWAB-gNB can broadcast a PLMN-ID that is different from the PLMN-ID of the PLMN connected to the MWAB-UE;

[0222] - The PLMN serving a UE is the PLMN broadcast by the MWAB-gNB to which it resides / connects. The PLMN serving a UE may have a different PLMN-ID than the PLMN-ID of the PLMN serving the MWAB-UE.

[0223] In some embodiments, when providing services to the UE via the MWAB-gNB, N3 access occurs over an IP connection provided by the MWAB-UE's PDU session. Therefore, the user data exchanged between the MWAB-gNB and the UE UPF providing access to the UE should be encapsulated as user plane data over the IP connection provided by the MWAB-UE's PDU session. Consequently, the address information of the MWAB nodes (MWAB-gNB and / or MWAB-UE) should be configured at the UE's serving UPF. Furthermore, the UPF may use network address translation (NAT) between the UE and the data network. This could result in the (private) UE IP address assigned by the 5GC being unvisible at the N6 reference point. That is, the UE's serving UPF may not be able to obtain the (private) UE IP address assigned by the 5GC. Therefore, the (private) UE IP address of the MWAB-UE assigned for the BH PDU session differs from the IP address seen by the UE UPF over the IP connection.

[0224] In some embodiments, such as Figure 1c It provides existing management procedures for backhaul packet data unit (BH PDU) sessions used for N3 access. For example... Figure 1c As shown, the process of establishing or modifying a UE PDU session may include the following steps:

[0225] Step 1. Establish or modify a PDU session for the UE based on the provisions of the existing protocol. This allows the MWAB-gNB to receive a new SM context for the PDU session from the SMF. This new SM context includes at least the QoS flow.

[0226] Step 2. For each QoS flow, the MWAB-gNB determines the required 5G QoS Identifier / Allocation and Retention Priority (5QI / ARP) and other QoS parameters in the BH PDU session, as well as transport network layer (TNL) information, to send signaling notifications to the BH SMF regarding the QoS rules associated with the downlink (DL) Service Data Flow (SDF). For the uplink (UL), the QoS rules are also determined by the MWAB, and the TNL information determined by the MWAB-gNB is used to classify the UL data.

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

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

[0229] Step 5. MWAB-UE confirms the correct modification to the BH PDU session.

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

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

[0232] In the above scheme, the QoS flow of the PDU session of the UE served by MWAB-gNB is mapped to the BH PDU session, and the UPF configuration of the BH PDU session is determined by modifying the BH PDU session to support the processing of different data flows from the UE; however, it does not provide how to configure the address information of MWAB-UE to the UE UPF to support N3 access of UE served by MWAB-gNB; nor does it consider the case of using NAT UPF between MWAB-UE and data network (UE UPF).

[0233] It should be noted that the PDU involved in this disclosure embodiment can be described as (Packet Data Unit) or (Protocol Data Unit), and there is no limitation on this.

[0234] Based on the aforementioned wireless communication system, various embodiments of the communication method proposed in this disclosure will be described in detail below.

[0235] Figure 2This is an interactive schematic diagram illustrating a communication method according to an embodiment of this disclosure. For example... Figure 2 As shown, this communication method is used in a communication system 100, and the method includes:

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

[0237] In some embodiments, network functions can also be described as network elements, network nodes, network function entities, etc. The logical functions that network functions can be flexibly deployed can also be specific logical function entities, but are not limited to this.

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

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

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

[0241] In some embodiments, sending can be understood as sending directly or forwarding via other network elements.

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

[0243] In some embodiments, the first information is used to indicate the processing rules for a first data packet and a second data packet associated with the first data packet.

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

[0245] In some embodiments, the second data packet may be a downlink user plane data packet belonging to the same Packet Data Unit (PDU) session as the first data packet.

[0246] In some embodiments, the PDU session is a PDU session of a first terminal that accesses the first network function through the first node, and the PDU session is the first session.

[0247] In some embodiments, the aforementioned backhaul path is a user plane path of a second session, which is a PDU session in which the backhaul path is provided by the terminal portion included in the first node.

[0248] In some embodiments, the first node is a Mobile gNB with wireless access backhaul (MWAB). Optionally, the first node includes a base station portion of the Mobile gNB with wireless access backhaul (e.g., it may be denoted as MWAB-gNB) and / or, the first node includes a terminal portion of the Mobile gNB with wireless access backhaul (e.g., it may be denoted as MWAB-UE). Optionally, the terminal portion of the Mobile gNB with wireless access backhaul may be described as a second terminal.

[0249] Optionally, the terminal that accesses the network via the base station portion of a mobile base station with wireless backhaul is the first terminal.

[0250] In some embodiments, both the first data packet and the second data packet are data packets received by the first network function, and their association relationship may include:

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

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

[0253] 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,

[0254] 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.

[0255] Optionally, the address information in this embodiment may include an IP address and / or a port number.

[0256] 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, then the first data packet and the second data packet can be determined to be associated data packets.

[0257] 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, then the first data packet and the second data packet can be determined to be associated data packets.

[0258] In some embodiments, it is not limited whether the first data packet includes the address information of the first session. Optionally, the first data packet may not include the data packet of the first session, and the address information of the corresponding first session may be added in the first network function.

[0259] 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, then the first data packet and the second data packet can be determined to be associated data packets.

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

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

[0262] The source address information of the first data packet after the address information of the second terminal providing the return path has been changed.

[0263] In some embodiments, the first address information is used to identify the source address information of the first data packet. The first data packet may be the initial first data packet, or the first data packet after the address information of the return path has been changed.

[0264] In some embodiments, if the first data packet is a first data packet with changed address information of the return path, then its corresponding first address information has changed compared to the address information corresponding to the initial first data packet.

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

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

[0267] Is the received data packet the first data packet?

[0268] It conforms to the first address information corresponding to the first data packet;

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

[0270] Whether to use the first address information for processing the second data packet;

[0271] The second data packet is processed using the first address information.

[0272] In some embodiments, the first information may 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 a first data packet; the second rule is used to determine and record the first address information corresponding to the first data packet that conforms to the first rule; and the third rule is used to determine whether the first address information is used in the second data packet and to process the second data packet using the first address information.

[0273] In some embodiments, the first rule for detecting the first data packet and the second rule for determining the first address to be recorded can be combined into a single rule for description.

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

[0275] In some embodiments, the aforementioned data packet may be an uplink data packet sent via the first node.

[0276] Optionally, the first processing rule includes packet detection / inspection rules and packet recording rules. The detection rule determines whether the received packet is a packet sent from the MWAB-gNB to the UPF in a PDU session, specifically: an uplink packet from the N3 interface of the first terminal's PDU session (e.g., the first session) sent through the PDU session (BHPDU session, e.g., the second session) via the backhaul path provided by the second terminal. This packet can be referred to as the first packet. The action rule determines the timing and content for recording the first packet that conforms to the detection rule. In some embodiments, the recording of the first packet conforming to the first rule or its corresponding first address information can be determined based on the receipt of the first first packet.

[0277] Optionally, the recording timing can be the moment the first data packet is received, and the recording content can include the first address information corresponding to the first data packet that conforms to the detection rules.

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

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

[0280] In some embodiments, where the first data packet includes address information of the first session, the second data packet can be determined by the association between the address information of the first data packet and the second data packet.

[0281] Optionally, a downlink user plane packet whose destination address is the same as the source address of the first session included in the first packet can be identified as the second packet.

[0282] Optionally, a downlink user plane data packet with the same source address as the destination address of the first data packet can be identified as the second data packet.

[0283] 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 using the first address as the destination address.

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

[0285] Optionally, if the tunnel information of the received data packet is the first tunnel information, then the data packet is determined to be the first data packet that conforms to the first rule.

[0286] 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 during the establishment of the first session and sent to the second network function in the response to the N4 session establishment request; or it can be updated by the first network function during the update of the first session and sent to the second network function in the response to the N4 session update request.

[0287] 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 short for General Packet Radio Service.

[0288] In some embodiments, when an uplink user plane data packet is received on a user plane channel established based on a 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, the GTP tunnel information of the first session can be used to check whether the received data packet is the first data packet.

[0289] In some embodiments, the first rule may include: 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.

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

[0291] In some embodiments, the second information may be information other than the first tunnel information described above, used to identify data packets sent in the first session.

[0292] Optionally, the second information may include at least one of the following:

[0293] The connection identifier for the user plane connection in the first session;

[0294] The identifier of the first terminal in the first session;

[0295] Specific indication information is used to indicate the user plane connection between the first node of the first session and the first network function;

[0296] A specific identifier is used to identify the user plane connection between the first node of the first session and the first network function.

[0297] In some embodiments, if the second information described above is available, it can be determined whether the received data packet is the first data packet based on the second information.

[0298] Optionally, the connection identifier of the user plane connection in the first session can be the connection identifier of the N3 connection in the first session.

[0299] Optionally, the identifier of the first terminal in the first session can be a general public user identifier of the first terminal in the first session, but is not limited to this.

[0300] Optionally, the second information may also be a specific indication or identifier used to indicate or identify the N3 connection between the first node and the UEPPF.

[0301] In some embodiments, the second information may be pre-configured or obtained through protocol interaction between the first node and the second network function; this application embodiment does not limit this.

[0302] In some embodiments, it is not limited whether the first data packet includes the address information of the first session. If the first data packet does not include the address information of the first session, for uplink data packets received by the first network function, it can be determined that the uplink data packet received by the first network function is the first data packet, i.e., the data packet is the uplink data packet of the first session, based on the first tunnel information or the second information mentioned above. For downlink user plane data packets received by the first network function, it can be determined whether the downlink user plane data packet received by the first network function is the second data packet by matching the rule information containing the address of the first terminal of the first session configured by the second network function. Optionally, if the destination address of the downlink user plane data packet is the address of the first terminal of the first session, then 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 the second data packet is associated with the first data packet.

[0303] In some embodiments, the first data packet described above may include at least one of the following:

[0304] User data packets for the first terminal;

[0305] A specific data packet, generated by the first node.

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

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

[0308] In some embodiments, a particular data packet may include at least one of the following:

[0309] User plane signaling messages specific to the tunneling protocol;

[0310] Empty tunnel protocol user plane messages.

[0311] In some embodiments, the user plane signaling messages of a specific tunneling protocol may include GTP-U and GTP-U signaling messages.

[0312] Optionally, GTP-U signaling messages may include tunnel status, error indications, or new GTP-U signaling messages, but are not limited to these.

[0313] Optionally, the empty tunneling protocol user plane message can be a pseudo g-PDU message.

[0314] In some embodiments, step S201 may specifically include: sending first information to a first network function via a first request message, wherein the first request message is used to manage the user plane path of a packet data unit (PDU) session of a first terminal accessing the network via a first node.

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

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

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

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

[0319] In some embodiments, the first network function may determine whether the received data packet is the first data packet based on the 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 via the backhaul path, then the data packet is determined to be the first data packet, and the source address information of the first data packet is determined to be its corresponding first address information.

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

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

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

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

[0324] 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 has been changed, the source address information of the first data packet after the address information of the backhaul path has been changed can be used to encapsulate the second data packet associated with the first data packet after the address information of the backhaul path has been changed.

[0325] It should be noted that if the source address of the first data packet changes, the first information used to process the associated second data packet does not need to be changed. The modified first address can be recorded based on the first information, and then the modified first address can be used to process the second data packet.

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

[0327] In some embodiments, the processing rules of the first information indication (or included) are related to the first session, which is the PDU session of the first terminal accessing the network via the first node, that is: the interaction between the first node and the second network function in the user plane path of the PDU session is realized through the backhaul path.

[0328] Optionally, the specific details of the processing rules can be found in the relevant description of the first information above, and will not be repeated here.

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

[0330] In some embodiments, one end of the backhaul path involved in this disclosure can be connected to the MWAB (e.g., MWAB-UE), and the other end can be connected to the data network. The MWAB can use this backhaul path to communicate with a first network function in the data network to transmit user plane data packets.

[0331] In some embodiments, the "address information of the backhaul path" involved in this disclosure refers to the address of the MWAB end of the backhaul path between the MWAB and the second network function, which may include at least one of the following: IP address, IP prefix, and port address of the MWAB end of the backhaul path.

[0332] It should be noted that in other parts of the embodiments of this 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, the port address of the backhaul path, etc., and these information are all used to indicate the "address of the MWAB end of the backhaul path".

[0333] It should be noted that in some networks, operators use NAT (Network Address Translation) before the UPF is sent to the data network. For example, in this implementation, data packets sent from the MWAB-gNB to the UE UPF (which can correspond to the first network function mentioned above) are forwarded through the UPF on the backhaul path. When the UPF sends data to the first network function, it uses NAT to remap the source address of the data packet. This may result in the source address of the user plane data packet sent by the MWAB being different from the source address of the user plane data packet received by the first network function. However, both of them indicate the same backhaul path address information.

[0334] For example, assuming the source address of the first data packet sent by MWAB is address information #1, after the first data packet is sent to the UPF of the return path, the UPF of the return 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. Address information #1 and address information #2 are used to indicate the same return path address information, and address information #1 and address information #2 can be the same or different. Address information #1 can be the information used by MWAB to indicate the return path address information, and address information #2 can be the information used by the first network function to indicate the return path address information.

[0335] Optionally, data packets sent from the UE UPF to the MWAB are forwarded through the UPF of the backhaul path. When the UPF of the backhaul path receives the data packets sent by the UE UPF, it will use the NAT function to remap the destination address of the data packets. For example, following the example above, the destination address information of the data packet when it is sent from the UE UPF is address information #2. 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.

[0336] It should be understood that the UE UPF can be the same as the UPF of the backhaul path (e.g., different parts of the same UPF provide services to different terminals) or different, without limitation. 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, without limitation.

[0337] In some embodiments, prior to step S202, the method may further include:

[0338] S203, First network function receives data packets.

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

[0340] S204. The first network function determines the first data packet and the second data packet based on the acquired first information.

[0341] In some embodiments, the first network function determines whether the received data packet is a first data packet according to a first rule in the first information; determines and records the first address information corresponding to the first data packet that conforms to the first rule when the first first data packet is received according to a second rule in the first information; updates the recorded first address information when the first data packet after the backhaul path has changed is received; 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.

[0342] In some embodiments, the first rule for detecting the first data packet and the second rule for determining the first address to be recorded can be combined into the same rule for description.

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

[0344] In some embodiments, the rule information described above can be implemented by updating the processing rules for uplink and downlink user plane data packets of the existing first session.

[0345] In some embodiments, the names of information, etc., are not limited to those described in the embodiments. Terms such as "information", "message", "signal", "signaling", "report", "configuration", "indication", "instruction", "command", "channel", "parameter", "domain", "field", "symbol", and "data" can be used interchangeably.

[0346] In some embodiments, terms such as "send", "transmit", "report", "download", "transmit", "bidirectional transmission", "send and / or receive" can be used interchangeably.

[0347] In some embodiments, terms such as "certain", "preset", "preset", "setting", "indicated", "a certain", "any", and "first" can be interchangeable. "Specific A", "preset A", "preset A", "setting A", "indicated A", "a certain A", "any A", and "first A" can be interpreted as A pre-specified in a protocol, etc., or as A obtained through setting, configuration, or indication, etc., or as specific A, a certain A, any A, or first A, etc., but not limited to this.

[0348] In some embodiments, terms such as “in the case of,” “when,” “when,” “if,” “if,” etc., can be used interchangeably.

[0349] The methods involved in the embodiments of this disclosure may include at least one of steps S201 to S203. For example, steps S201 and S202 may be implemented as independent embodiments, but are not limited thereto.

[0350] In some embodiments, step S203 is optional, and one or more of these steps may be omitted or substituted in different embodiments.

[0351] Figure 3a This is a flowchart illustrating a communication method according to an embodiment of this disclosure. Figure 3a As shown, the communication method can be executed by a first network function, and the method includes:

[0352] S301, Receive the first information sent by the second network function.

[0353] For optional implementations of step S301, please refer to [link / reference]. Figure 2 Optional implementation methods of step S201, and Figure 2 Other related parts in the embodiments involved will not be described in detail here.

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

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

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

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

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

[0359] In some embodiments, the second data packet may 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 a first terminal accessing the first network function through the first node, and the PDU session is the first session. Optionally, the first terminal is a terminal accessing the network via the first node.

[0360] In some embodiments, the backhaul path is a user plane path of a second session, which is a PDU session in which the backhaul path is provided by the terminal portion included in the first node.

[0361] In some embodiments, the first node may be a MWAB, and optionally, the MWAB may include a MWAB-gNB and / or a MWAB-UE. Optionally, the first terminal is a terminal that accesses the network via a MWAB-gNB. Optionally, the MWAB-UE is a second terminal.

[0362] S302. Based on the first information, determine the first data packet and the second data packet that match the first information in the received data packets.

[0363] For optional implementations of step S302, please refer to [link / reference]. Figure 2 Optional implementation methods of step S203, and Figure 2 Other related parts in the embodiments involved will not be described in detail here.

[0364] In some embodiments, the received data packet may 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 a first data packet; it may also include a second rule for determining and recording the first address information corresponding to the first data packet that conforms to the first rule; and it may also include a third rule for determining and processing the second data packet.

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

[0366] S303. Determine the first address information corresponding to the first data packet based on the first information, and use the first address information for processing the second data packet.

[0367] For optional implementations of step S303, please refer to Figure 2 Optional implementation methods of step S202, and Figure 2 Other related parts in the embodiments involved will not be described in detail here.

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

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

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

[0371] The source address information of the modified first data packet from the second terminal providing the return path.

[0372] The method involved in the embodiments of this disclosure may include at least one of steps S301 to S303. For example, steps S301 and S303 may be implemented as independent embodiments, but are not limited thereto.

[0373] In some embodiments, step S302 is optional, and one or more of these steps may be omitted or substituted in different embodiments.

[0374] Figure 3b This is a flowchart illustrating a communication method according to an embodiment of this disclosure. Figure 3b As shown, the communication method can be executed by a first network function, and the method includes:

[0375] S311, Obtain first information.

[0376] For optional implementations of step S311, please refer to [link / reference]. Figure 2 Step S201 Figure 3a Optional implementation methods of step S301, and Figure 2 , Figure 3a Other related parts in the embodiments involved will not be described in detail here.

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

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

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

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

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

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

[0383] In some embodiments, the second data packet may 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 a first terminal accessing the first network function through the first node, and the PDU session is the first session. Optionally, the first terminal is a terminal accessing the network via the first node.

[0384] In some embodiments, the backhaul path is a user plane path of a second session, which is a PDU session in which the backhaul path is provided by the terminal portion included in the first node.

[0385] In some embodiments, 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, the destination address of the first data packet is the same as the source address information of the second data packet.

[0386] Optionally, the address information includes the IP address and / or port number.

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

[0388] Is the received data packet the first data packet?

[0389] It conforms to the first address information corresponding to the first data packet;

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

[0391] Whether to use the first address information for processing the second data packet;

[0392] The second data packet is processed using the first address information.

[0393] In some embodiments, determining whether the received data packet is the first data packet includes:

[0394] Based on the first tunnel information, determine whether the received data packet is the first data packet; or,

[0395] Based on the second information configured or negotiated between the first node and the second network function, it is determined whether the received data packet is the first data packet.

[0396] In some embodiments, the first tunnel information is user plane tunnel information associated with a first network function in a first session.

[0397] In some embodiments, the second information includes at least one of the following:

[0398] The connection identifier for the user plane connection in the first session;

[0399] The identifier of the first terminal in the first session;

[0400] Specific indication information is used to indicate the user plane connection between the first node of the first session and the first network function;

[0401] A specific identifier is used to identify the user plane connection between the first node of the first session and the first network function.

[0402] In some embodiments, the first data packet includes at least one of the following:

[0403] User data packets from the first terminal that accesses the network through the first node;

[0404] A specific data packet, generated by the first node.

[0405] In some embodiments, a particular data packet includes at least one of the following:

[0406] User plane signaling messages specific to the tunneling protocol;

[0407] Empty tunnel protocol user plane messages.

[0408] In some embodiments, step 311 may specifically include: obtaining a second network function and sending first information through a first request message.

[0409] In some embodiments, the first request message is used to manage the user plane path of the first session.

[0410] In some embodiments, the first node may be a MWAB, and optionally, the MWAB may include a MWAB-gNB and / or a MWAB-UE. Optionally, the first terminal is a terminal that accesses the network via a MWAB-gNB. Optionally, the MWAB-UE is a second terminal.

[0411] S312. Based on the first information, determine the first address information corresponding to the first data packet in the received data packet, and use the first address information for processing the second data packet.

[0412] For optional implementations of step S312, please refer to Figure 2 Step S202 Figure 3a Optional implementation methods of step S303, and Figure 2 , Figure 3a Other related parts in the embodiments involved will not be described in detail here.

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

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

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

[0416] Provide the source address information of the modified first data packet of the second terminal of the backhaul path.

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

[0418] In some embodiments, the second data packet encapsulates first address information. Optionally, the second data packet can be encapsulated using the address corresponding to the first address information as the destination address.

[0419] In some embodiments, before step S302, the method may further include: determining, based on first information, a first data packet and a second data packet that conform to the first information in the received data packets.

[0420] The above optional implementation methods can be found in [reference]. Figure 2 Step S204 Figure 3a Optional implementation methods of step S302, and Figure 2 , Figure 3a Other related parts in the embodiments involved will not be described in detail here.

[0421] In some embodiments, the received data packet may 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 a first data packet; it may also include a second rule for determining and recording the first address information corresponding to the first data packet that conforms to the first rule; and it may also include a third rule for determining and processing the second data packet.

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

[0423] Figure 3c is a flowchart illustrating a communication method according to an embodiment of the present disclosure. As shown in Figure 3c, the communication method can be executed by a first network function, and the method includes:

[0424] S321, Receive data packets.

[0425] For optional implementations of step S321, please refer to [link / reference]. Figure 2 Optional implementation methods of step S203, and Figure 2 Other related parts in the embodiments involved will not be described in detail here.

[0426] S322. Based on the first information, determine the first address information corresponding to the first data packet in the data packet, and use the first address information for processing the second data packet.

[0427] For optional implementations of step S322, please refer to [link / reference]. Figure 2 Step S202 Figure 3a Step S303 Figure 3b Optional implementation methods of step S312, and Figure 2 , Figure 3a , Figure 3b Other related parts in the embodiments involved will not be described in detail here.

[0428] Figure 4 This is a flowchart illustrating a communication method according to an embodiment of this disclosure. Figure 4 As shown, this communication method can be executed by a second network function, and the method includes:

[0429] S401, Send the first message.

[0430] For optional implementations of step S401, please refer to [link / reference]. Figure 2 Optional implementation methods of step S201, and Figure 2 Other related parts in the embodiments involved will not be described in detail here.

[0431] In some embodiments, a first network function sends first information to another first network function.

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

[0433] In some embodiments, the first information is used to determine the first address information corresponding to the first data packet, and to determine whether to use the first address information for processing the second data packet.

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

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

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

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

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

[0439] 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.

[0440] In some embodiments, a PDU session is a PDU session of a first terminal that accesses a first network function through a first node, and the PDU session of the first terminal is a first session.

[0441] In some embodiments, the backhaul path is the user plane path of a second session, where the second session is a PDU session in which the backhaul path is provided by the terminal portion included in the first node.

[0442] In some embodiments, 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, the destination address of the first data packet is the same as the source address information of the second data packet.

[0443] Optionally, the address information includes the IP address and / or port number.

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

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

[0446] Provides the source address information of the first data packet after the address information of the terminal portion of the backhaul path has been changed.

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

[0448] Is the received data packet the first data packet?

[0449] It conforms to the first address information corresponding to the first data packet;

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

[0451] Whether to use the first address information for processing the second data packet;

[0452] The second data packet is processed using the first address information.

[0453] In some embodiments, determining whether the received data packet is the first data packet includes:

[0454] Based on the first tunnel information, determine whether the received data packet is the first data packet; or,

[0455] Based on the second information configured or negotiated between the first node and the second network function, it is determined whether the received data packet is the first data packet.

[0456] In some embodiments, the first tunnel information is user plane tunnel information associated with a first network function in a first session.

[0457] In some embodiments, the second information includes at least one of the following:

[0458] The connection identifier for the user plane connection in the first session;

[0459] The identifier of the first terminal in the first session;

[0460] Specific indication information is used to indicate the user plane connection between the first node of the first session and the first network function;

[0461] A specific identifier is used to identify the user plane connection between the first node of the first session and the first network function.

[0462] In some embodiments, the first data packet includes at least one of the following:

[0463] User data packets from the first terminal that accesses the network through the first node;

[0464] A specific data packet, generated by the first node.

[0465] In some embodiments, a particular data packet includes at least one of the following:

[0466] User plane signaling messages specific to the tunneling protocol;

[0467] Empty tunnel protocol user plane messages.

[0468] In some embodiments, step 401 may include: sending first information to a first network function via a first request message, the first request message being used to manage the user plane path of a first session.

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

[0470] Figure 5 This is a flowchart illustrating a communication method according to an embodiment of this disclosure. Figure 5 As shown, this communication method can be executed by a communication system, and the method includes:

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

[0472] For optional implementations of step S501, please refer to [link / reference]. Figure 2 Optional implementation methods of step S201 Figure 3aStep S301 Figure 3b Step S311 Figure 4 Step S401, and Figure 2 , Figures 3a-3b , Figure 4 Other related parts in the embodiments involved will not be described in detail here.

[0473] In some embodiments, the first information is used to indicate the processing rules for a first data packet and a second data packet associated with the first data packet.

[0474] S502, the first network node determines the 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 the second data packet.

[0475] For optional implementations of step S502, please refer to [link / reference]. Figure 2 Step S204 Figure 3a Step S303 Figure 3b Step S312, and Figure 2 , Figures 3a-3b Other related parts in the embodiments involved will not be described in detail here.

[0476] This disclosure also proposes an apparatus for implementing any of the above methods. For example, an apparatus is proposed that includes units or modules for implementing the steps performed by the terminal in any of the above methods. Furthermore, another apparatus is proposed that includes units or modules for implementing the steps performed by network elements (e.g., access network equipment, core network functional nodes, core network equipment, etc.) in any of the above methods.

[0477] It should be understood that the division of units or modules in the above device is only a logical functional division. In actual implementation, they can be fully or partially integrated into a single physical entity, or they can be physically separated. Furthermore, the units or modules in the device can be implemented by a processor calling software: for example, the device includes a processor connected to a memory containing instructions. The processor calls the instructions stored in the memory to implement any of the above methods or to implement the functions of the units or modules in the above device. The processor can be, for example, a general-purpose processor, such as a Central Processing Unit (CPU) or a microprocessor, and the memory can be internal or external to the device. Alternatively, the units or modules in the device can be implemented in the form of hardware circuits. The functions of some or all of the units or modules can be achieved through the design of the hardware circuits. The aforementioned hardware circuits can be understood as one or more processors. For example, in one implementation, the aforementioned hardware circuit is an application-specific integrated circuit (ASIC). The functions of some or all of the aforementioned units or modules are achieved through the design of the logical relationships between the components within the circuit. As another example, in another implementation, the aforementioned hardware circuits can be implemented through programmable logic devices (PLDs). Taking a field-programmable gate array (FPGA) as an example, it can include a large number of logic gates. The connection relationships between the logic gates are configured through configuration files, thereby achieving the functions of some or all of the aforementioned units or modules.

[0478] All units or modules of the above devices can be implemented entirely through processor-invoked software, entirely through hardware circuits, or partially through processor-invoked software with the remainder implemented through hardware circuits. In this embodiment, the processor is a circuit with signal processing capabilities. In one implementation, the processor can be a circuit with instruction read and execute capabilities, such as a Central Processing Unit (CPU), a microprocessor, a graphics processing unit (GPU) (which can be understood as a microprocessor), or a digital signal processor (DSP). In another implementation, the processor can implement certain functions through the logical relationships of hardware circuits. These logical relationships are fixed or reconfigurable. For example, the processor may be a hardware circuit implemented using an application-specific integrated circuit (ASIC) or a programmable logic device (PLD), such as an FPGA. In a reconfigurable hardware circuit, the process of the processor loading a configuration document and configuring the hardware circuit can be understood as the processor loading instructions to implement the functions of some or all of the above units or modules. In addition, it can also be hardware circuits designed for artificial intelligence, which can be understood as ASICs, such as Neural Network Processing Unit (NPU), Tensor Processing Unit (TPU), Deep Learning Processing Unit (DPU), etc.

[0479] Figure 6a This is a schematic diagram of the structure of the first network function proposed in an embodiment of this disclosure. For example... Figure 6a As shown, the first network function may include at least one of the following: a first transceiver module 611, a first processing module 612, etc.

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

[0481] Optionally, the first processing module 612 is further configured to perform steps related to information processing performed by the first network function in any of the above methods, for example: Figure 2 Step S204 shown in the diagram will not be repeated here.

[0482] Optionally, the first transceiver module 611 described above is used to perform steps related to transmitting and receiving signaling in any of the above methods performed by the first network function, for example: Figure 2 Step S201 shown in the figure will not be repeated here.

[0483] Optionally, the first transceiver module 611 described above is further configured to perform steps related to sending and receiving data in any of the above methods performed by the first network function, for example: Figure 2 Step S203 shown in the diagram will not be repeated here.

[0484] Figure 6b This is a schematic diagram of the structure of the second network function proposed in an embodiment of this disclosure. For example... Figure 6b As shown, the second network function includes at least one of the following: a second transceiver module 621, a second processing module 622, etc.

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

[0486] Wherein, the first information is used to determine the first address information corresponding to the first data packet in the data packet received by the first network function, and to determine to use the first address information for the processing of the second data packet;

[0487] Wherein, the first address information is used to identify the source address information of the first data packet; the second data packet is a data packet associated with the first data packet.

[0488] In some alternative embodiments, a solution is provided that supports establishing PDU session connections to the network via MWAB, regardless of whether NAT is used between the MWAB-UE and the data network (UE UPF). This solution supports the corresponding user data transmission via the IP connection network provided by the PDU session of the MWAB-UE, and supports the establishment / modification / release of the corresponding PDU session.

[0489] In the following embodiments, the MWAB-UE is authorized, and the corresponding MWAB-gNB is configured with information allowing it to connect to the AMF via the corresponding OAM server. A BH PDU session for providing N2 access to the AMF for the MWAB-gNB is established based on the policy configuration of the MWAB-UE (e.g., by the MWAB-UE's URSP rules), where the UE route selection populace (URSP) is a policy used to select different PDU sessions. A BH PDU session for providing N3 access to the MWAB-gNB and the UPF serving the UE is established based on the policy configuration of the MWAB-UE (e.g., by the MWAB-UE's URRP rules). Based on the policy configuration of the MWAB-UE, the BH PDU session for MWAB-gNB N3 access to the UPF and the BH PDU session for MWAB-gNB N2 access to the AMF can be the same or different. An AMF serving the UE accessed via MWAB-gNB is called a UE AMF, and an N3 UPF / SMF serving the UE accessed via MWAB-gNB is called a UE UPF / UE SMF. The MWAB-gNB can share the address information of the BH PDU sessions used for N2 / N3 access, or the address information of the MWAB-gNB can be different from the address information of the BH PDU sessions used for N2 / N3. An AMF serving the UE accessed via MWAB-gNB, or an AMF serving the UE, is called a UEAMF, and an N3 UPF / SMF serving the UE accessed via MWAB-gNB is called a UE UPF / UE SMF. The MWAB-gNB can share the address information of the BH PDU sessions corresponding to the backhaul paths used for N2 / N3 access, or the address information of the MWAB-gNB can be different from the address information of the BH PDU sessions corresponding to the backhaul paths used for N2 / N3.

[0490] In some embodiments, the BH peer address (which may correspond to the first address information mentioned above) is the address information for the backhaul path used for N3 access. This address information may 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. This address information may be the same as or different from the address information of the MWAB-UE end of the backhaul path provided by the BH PDU session used by the WMAB, depending on whether NAT is used. Both of these indicate the same backhaul path address information.

[0491] In some embodiments, a dynamic packet processing rule is configured, which is to use the BH peer address in the received uplink packet.

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

[0493] In some embodiments, the dynamic processing rule for the data packets is: the BH peer address is recorded and used for downlink data packet transmission.

[0494] In some embodiments, the dynamic processing rule for the data packet is as follows: the updated BH peer address (which may correspond to the updated first address information mentioned above) is detected by the UE UPF via the received N3 uplink data packet and used for downlink data packet transmission.

[0495] In some embodiments, such as Figure 7 As shown, a solution is provided to support PDU session access via MWAB, which may include the following steps:

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

[0497] Optionally, the MWAB-gNB is configured to act as a radio access point, and the MWAB-gNB is serving the UE.

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

[0499] S3. For N2 access, trigger BH PDU session modification / establishment for the Serving AMF (UE AMF) used to access the UE, in order to exchange signaling for the session management process.

[0500] S4. Send the PDU session establishment request, which is included in the N2 message from MWAB-gNB, to the UE AMF via the BH PDU session.

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

[0502] In some embodiments, the information included in the message received from step S4 or the local information related to the access RAN node may be information used to indicate that the access UE accesses the network via MWAB-gNB, and the information may include at least one of the following: explicit MWAB indication, location configuration, access type information, location information, etc.

[0503] S6. The UE AMF calls the Nsmf_PDUSession_CreateSMContext Request service to send a PDU session context establishment request to the UE SMF (which can correspond to the second network function mentioned above).

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

[0505] In some embodiments, if the sender of the N2 message including the PDU session establishment request is not determined to be the MWAB-gNB in ​​step S5, the information included in the message received in step S5 may be information indicating that the accessing UE accesses the network via the MWAB-gNB, such as: displayed MWAB indication, location configuration, access type information, and / or location information. Optionally, the UE AMF may 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 in step S5 or local information used for accessing the RAN node. In this case, the PDU session establishment request sent to the UE SMF may include information indicating that a PDU session is being established for a UE accessing the network via the MWAB.

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

[0507] In some embodiments, if it is determined in step S5 that the sender of the N2 message including the PDU session establishment request is MWAB-gNB, then the information included in the message received in step S6 may be information indicating that a UE is establishing a PDU session via the MWAB access network.

[0508] In some embodiments, if the sender of the N2 message including the PDU session establishment request is not determined in step S5, but is determined in step S6, the information included in the message received from step S6 may be information indicating that a UE is establishing a PDU session via the MWAB access network.

[0509] In some embodiments, if it is not determined in steps S5 and S6 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 may be information indicating that the accessing UE accesses the network via the MWAB-gNB, such as: explicit MWAB indication, location configuration, access type information and / or location information.

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

[0511] During this process, the acquired CN tunnel information is GTP tunnel information about the UE UPF. This CN tunnel information is used for the transmission of user data in the UE PDU session based on the backhaul path between the MWAB gNB and the UE UPF, and this CN tunnel information is sent to the UE SMF.

[0512] In some embodiments, if information other than CN tunnel information can be used to identify data packets sent by the MWAB gNB and the UE UEPF based on the backhaul path of the UE PDU session, this information can be configured or negotiated between the MWAB gNB and the UE SMF (which may correspond to the second information mentioned above). Optionally, this information may include, but is not limited to, the following: using a connection identifier that identifies the N3 connection of 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.

[0513] In some embodiments, if the above information is available prior to step S8, the processing rules for reporting the BH peer address or forwarding packets with the BH peer address, as set in step S9 below, can be executed in step S8. Optionally, the detection information for packets can be information other than 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 mentioned above.

[0514] S9. Modify the N4 session to indicate the detection of the BH peer address.

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

[0516] In some embodiments, the detection information for data packets may be destination GTP tunnel information about the UE UPF, which is used for uplink user data transmission between the MWAB-gNB and the UEPPF for the UE PDU session (which may correspond to the first session mentioned above).

[0517] Optionally, the detection condition for the BH peer address is to determine 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, based on GTP tunnel information or information other than CN tunnel information.

[0518] In some embodiments, the detected BH peer address can be recorded, and / or the recorded BH peer address can be applied to the processing of associated data packets.

[0519] Optionally, the associated data packet may include: a downlink user plane data packet that has the same PDU session as the received uplink user plane data packet (e.g., including matching GTP tunnel information), or, if the received uplink data packet (e.g., including matching GTP tunnel information) includes the UE IP address of the UE PDU session, then the associated data packet is a downlink user plane data packet with the corresponding UE IP address as the destination address.

[0520] In some embodiments, the recording conditions for the BH peer address include: recording timing and recording content. Optionally, the recording timing may include: receiving the first uplink data through the N3 interface, or the source IP address changing compared to the most recently recorded IP address. Optionally, the recording content may include: the source IP address of the received uplink data packet that matches the GTP tunnel information.

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

[0522] In some embodiments, the uplink data received via the N3 interface may be uplink user data from the UE or uplink data generated by the MWAB-gNB. Optionally, the uplink data generated by the MWAB-gNB may 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., an empty GTP-U message).

[0523] In S10-S11, the SMF sends a PDU session establishment acceptance message to the UE via the AMF through the MWAB-gNB, and sends an N2 message to the MWAB-gNB. This N2 message carries an N2 PDU session request with CN tunnel information.

[0524] Optionally, messages between the AMF and MWAB-gNB are transmitted via a BH PDU session.

[0525] Optionally, indication information may be included to indicate specific uplink data generated via MWAB-gNB, including: specific GTP-U signaling messages (e.g., tunnel status, error indication, or new GTP-U signal transmission messages) or pseudo g-PDU messages.

[0526] S12.MWAB gNB to UE: (R)AN can send AN-specific signaling exchanges to the UE, including relevant information received from SMF.

[0527] S13. Optionally, for N3 access via the backhaul path to exchange user plane data for PDU sessions via the backhaul path, trigger BH PDU session modification / establishment to access the serving UE UPF.

[0528] S14. Send an N2 PDU session response from the MWAB-gNB to the UE AMF. Optionally, the response may include AN Tunnel Information for MWAB access. Optionally, the response may be an N2 PDU SessionResponse.

[0529] S15. The first uplink user data from the UE is sent to the UEUPF using the CN tunnel information received in step S11, or if there is no user data from the UE, the 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.

[0530] In some embodiments, the information in the data packet sent from the WMAB-gNB that instructs the UE UPF to detect the BH peer address information may include information for identifying the data packet sent by the PDU session as described in step S8.

[0531] Optionally, the CN tunnel information can be replaced with information identifying the data packet other than the CN tunnel information described in step 8.

[0532] S16. The UE UPF (which can correspond to the first network function mentioned above) 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.

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

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

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

[0536] The information related to processing associated downlink user data packets using dynamic BH peer address information, as described in step S9, can also be included in this step.

[0537] In some embodiments, the dynamic BH peer address information includes information for associating BH peer address detection with relevant packet processing rules, which are used to indicate the use of the corresponding BH peer address to encapsulate downlink user data.

[0538] Optionally, the packet processing rules include: downlink user plane packets on the N3 interface are encapsulated with BH peer addresses, wherein the BH peer address information is the address information of the BH peer address associated with the indicated packet processing rules.

[0539] Optionally, the AN tunnel information may include the address information of MWAB-gNB and / or MWAB-UE, while the BH peer address is used for downlink user plane packet encapsulation.

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

[0541] S19. Send an Nsmf_PDUSession_UpdateSMContext response to the UE AMF.

[0542] S20. Uplink and downlink data for the PDU session are transmitted via a BH PDU session for N3 access, which uses the BH peer address to transmit data packets through N3.

[0543] S21. Trigger MWAB-UE IP address change / removal / insertion for BH session used to access UE UPF.

[0544] S22. After the IP address of the MWAB-UE used for the BH session to access the UE UPF is changed, the uplink data as described in step S15 is sent to the UE UPF via N3.

[0545] S23. If the UE UPF detects a change in the IP address of the MWAB-UE used for the BH session accessing the UE UPF based on the N3 uplink data received in step S22, it records the updated source address information of the received data packets, including the GTP tunnel information, and uses the updated BH peer address to update the associated downlink user plane data packet processing rules.

[0546] S24. Uplink and downlink data for the PDU session are transmitted via a BH PDU session for N3 access, which uses the updated BH peer address to transmit data packets through N3.

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

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

[0549] In some embodiments, if a first terminal has an existing session that switches from accessing the first node to accessing a non-first node, the data packet processing rules configured in the corresponding method described above can be canceled or no data packets that meet the rules will be received.

[0550] Figure 8aThis is a schematic diagram of the structure of the communication device 7100 proposed in this embodiment. The communication device 7100 can be a network device (e.g., access network device, core network device, etc.), a terminal (e.g., user equipment, etc.), a chip, chip system, or processor that supports the network device in implementing any of the above methods, or a chip, chip system, or processor that supports the terminal in implementing any of the above methods. The communication device 7100 can be used to implement the methods described in the above method embodiments; for details, please refer to the descriptions in the above method embodiments.

[0551] like Figure 8a As shown, the communication device 7100 includes one or more processors 7101. The processor 7101 can be a general-purpose processor or a dedicated processor, such as a baseband processor or a central processing unit (CPU). The baseband processor can be used to process communication protocols and communication data, while the CPU can be used to control communication devices (e.g., base stations, baseband chips, terminal devices, terminal device chips, DUs or CUs, etc.), execute programs, and process program data. The processor 7101 is used to invoke instructions to cause the communication device 7100 to execute any of the above methods.

[0552] 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 transceivers 7103 perform communication steps such as sending and / or receiving in the above-described method (e.g., ...). Figure 2 At least one of steps S201 and S203 shown in the diagram (but not limited to these), processor 7101 performs other steps (e.g., Figure 2 At least one of steps S202 and S204 shown, but not limited to, is included. In optional embodiments, the transceiver may include a receiver and / or a transmitter, which may be separate or integrated. Optionally, the terms transceiver, transceiver unit, transceiver, transceiver circuit, interface circuit, interface, etc., can be used interchangeably; the terms transmitter, transmitting unit, transmitter, transmitting circuit, etc., can be used interchangeably; and the terms receiver, receiving unit, receiver, receiving circuit, etc., can be used interchangeably.

[0553] In some embodiments, the communication device 7100 further includes one or more memories 7102 for storing instructions. Optionally, all or part of the memories 7102 may also be located outside the communication device 7100.

[0554] In some embodiments, a transceiver may include a receiver and a transmitter, which may be separate or integrated. Optionally, the terms transceiver, transceiver unit, transceiver, transceiver circuit, etc., may be used interchangeably; the terms transmitter, transmitting unit, transmitter, transmitting circuit, etc., may be used interchangeably; and the terms receiver, receiving unit, receiver, receiving circuit, etc., may be used interchangeably.

[0555] Optionally, the communication device 7100 further includes one or more interface circuits 7104, which are connected to the memory 7102. The interface circuits 7104 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 circuits 7104 can read instructions stored in the memory 7102 and send the instructions to the processor 7101.

[0556] The communication device 7100 described in the above embodiments may be a network device or a terminal, but the scope of the communication device 7100 described in this disclosure is not limited thereto, and the structure of the communication device 7100 may vary. Figure 8a The limitations. Communication equipment can be a standalone device or part of a larger device. For example, the communication equipment can be: (1) a standalone integrated circuit IC, or chip, or chip system or subsystem; (2) a collection of one or more ICs, optionally including 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, smart terminal device, cellular phone, wireless device, handheld device, mobile unit, vehicle device, network device, cloud device, artificial intelligence device, etc.; (6) others, etc.

[0557] Figure 8b This is a schematic diagram of the structure of chip 7200 according to an embodiment of this disclosure. For cases where the communication device 7100 can be a chip or a chip system, please refer to... Figure 8b The diagram shown is a schematic representation of the structure of chip 7200, but it is not limited to this.

[0558] Chip 7200 includes one or more processors 7201. Chip 7200 is used to perform any of the above methods.

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

[0560] In some embodiments, the interface circuit 7202 performs communication steps such as sending and / or receiving in the above method (e.g., Figure 2 At least one of steps S201 and S203 shown, but not limited to them. The interface circuit 7202 performing the communication steps such as sending and / or receiving in the above method refers, for example, to the interface circuit 7202 performing data interaction between the processor 7201, chip 7200, memory 7203, or transceiver device. In some embodiments, the processor 7201 performs other steps (e.g., Figure 2 At least one of steps S202 and S204 shown in the diagram, but not limited to these steps.

[0561] This disclosure also provides a program product that, when executed by the communication device 7100, causes the communication device 7100 to perform any of the above methods. Optionally, the program product is a computer program product.

[0562] The present disclosure also proposes a computer program, which, when executed on a computer, causes the computer to perform any one of the above methods.

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

[0564] Other embodiments of the invention will readily occur to those skilled in the art upon consideration of the specification and practice of the invention disclosed herein. This disclosure is intended to cover any variations, uses, or adaptations of the invention that follow the general principles of the invention and include common knowledge or customary techniques in the art not disclosed herein. The specification and examples are to be considered exemplary only, and the true scope and spirit of the invention are indicated by the following claims.

[0565] It should be understood that the present invention is not limited to the precise structure described above and shown in the accompanying drawings, and various modifications and changes can be made without departing from its scope. The scope of the invention is limited only by the appended claims.

Claims

1. A communication method, characterized in that, The method is performed by a first network function, and the method includes: Receive data packets; The first address information corresponding to the first data packet in the data packet is determined based on the first information, and the first address information is used for the processing of the second data packet; Wherein, the first address information is used to identify the source address information of the first data packet; the second data packet is a data packet associated with the first data packet.

2. The method according to claim 1, characterized in that, The step of using the first address information for processing the second data packet includes: The second data packet is encapsulated 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 the backhaul path, and 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.

4. The method according to claim 3, characterized in that, The PDU session is a PDU session of a first terminal that accesses the first network function through the first node, and the PDU session is the first session; The backhaul path is the user plane path of the second session, which is a PDU session in which the backhaul path is provided by the terminal portion included in the first node.

5. The method according to claim 4, characterized in that, The first address information includes one of the following: The source address information of the initial first data packet; Provides the source address information of the first data packet after the address information of the terminal portion of the backhaul path has been 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 the following: Is the received data packet the first data packet? It conforms to the first address information corresponding to the first data packet; The second data packet associated with the first data packet; Whether to use the first address information for processing the second data packet; The second data packet is processed using the first address information.

7. The method according to claim 6, characterized in that, Determining whether the received data packet is the first data packet includes: Based on the first tunnel information, determine whether the received data packet is the first data packet; or, Based on the second information configured or negotiated between the first node and the second network function, it is determined whether the received data packet is the first data packet.

8. The method according to claim 7, characterized in that, The first tunnel information includes the user plane address information associated with the first network function corresponding to the first session.

9. The method according to claim 7, characterized in that, The second information includes at least one of the following: The connection identifier of the user plane connection in the first session; The identifier of the first terminal in the first session; Specific indication information is used to indicate the user plane connection between the first node of the first session and the first network function; A specific identifier is used to identify the user plane connection between the first node of the first session and the first network function.

10. The method according to any one of claims 1-9, characterized in that, The first data packet includes at least one of the following: User data packets from the first terminal that accesses the network through the first node; A specific data packet, which is generated by the first node.

11. The method according to claim 10, characterized in that, The specific data packet includes at least one of the following: User plane signaling messages specific to the tunneling protocol; Empty tunnel protocol user plane messages.

12. The method according to any one of claims 1-11, characterized in that, The method further includes: The first request message is used to obtain the first information sent by the second network function, and the first request message is used to manage the user plane path of the first session.

13. The method according to any one of claims 1-12, characterized in that, The method further includes: Based on the first information, the first data packet and the second data packet are determined.

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 portion of the mobile base station with wireless backhaul, and / or the first node includes a terminal portion with wireless backhaul.

15. A communication method, characterized in that, The method is executed by a second network function, and the method includes: Send the first message to the first network function; Wherein, the first information is used to determine the first address information corresponding to the first data packet in the data packet received by the first network function, and to determine to use the first address information for the processing of the second data packet; Wherein, the first address information is used to identify the source address information of the first data packet; the second data packet is a data packet associated with the first data packet.

16. The method according to claim 15, characterized in that, The second data packet is encapsulated using the first address information.

17. The method according to claim 15 or 16, characterized in that, The first data packet is an uplink user plane data packet transmitted to the first network function via the backhaul path; 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.

18. The method according to claim 17, characterized in that, The PDU session is the PDU session of the first terminal that accesses the first network function through the first node, and the PDU session of the first terminal is the first session; The backhaul path is the user plane path of the second session, which is a PDU session in which the backhaul path is provided by the terminal portion included in the first node.

19. The method according to claim 18, characterized in that, The first address information includes one of the following: The source address information of the initial first data packet; Provides the source address information of the first data packet after the address information of the terminal portion of the backhaul path has been changed.

20. The method according to any one of claims 15-19, characterized in that, The first information is used to determine at least one of the following: Is the received data packet the first data packet? It conforms to the first address information corresponding to the first data packet; The second data packet associated with the first data packet; Whether to use the first address information for processing the second data packet; The second data packet is processed using the first address information.

21. The method according to claim 20, characterized in that, Determining whether the received data packet is the first data packet includes: Based on the first tunnel information, determine whether the received data packet is the first data packet; or, Based on the second information configured or negotiated between the first node and the second network function, it is determined whether the received data packet is the first data packet.

22. The method according to claim 21, characterized in that, The first tunnel information includes the user plane address information associated with the first network function corresponding to the first session.

23. The method according to claim 21, characterized in that, The second information includes at least one of the following: The connection identifier of the user plane connection in the first session; The identifier of the first terminal in the first session; Specific indication information is used to indicate the user plane connection between the first node of the first session and the first network function; A specific identifier is used to identify the user plane connection between the first node of the first session and the first network function.

24. The method according to any one of claims 15-23, characterized in that, The first data packet includes at least one of the following: User data packets from the first terminal that accesses the network through the first node; A specific data packet, which is generated by the first node.

25. The method according to claim 24, characterized in that, The specific data packet includes at least one of the following: User plane signaling messages specific to the tunneling protocol; Empty tunnel protocol user plane messages.

26. The method according to any one of claims 15-25, characterized in that, Sending the first information to the first network function includes: The first information is sent to the first network function via a first request message, the first request message being used to manage the user plane path of the first session.

27. The method according to any one of claims 18-26, characterized in that, The first node is a mobile base station with wireless backhaul, the first node includes a base station portion of the mobile base station with wireless backhaul, and / or the first node includes a terminal portion with wireless backhaul.

28. A communication system, characterized in that, include: First network function and second network function, wherein... The first network function receives data packets and the first information sent by the second network function; The first network function determines the first address information corresponding to the first data packet in the data packet based on the first information, and uses the first address information for processing the second data packet; Wherein, the first address information is used to identify the 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 according to claim 28, characterized in that, The first network function uses the first address information to encapsulate the second data packet.

30. A first network function, characterized in that, include: The first transceiver module is used to receive data packets; The first processing module is used to determine the first address information corresponding to the first data packet in the data packet according to the first information, and use the first address information for processing the second data packet; Wherein, the first address information is used to identify the 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, include: The second transceiver module is used to send the first information to the first network function; Wherein, the first information is used to determine the first address information corresponding to the first data packet in the data packet received by the first network function, and to determine to use the first address information for the processing of the second data packet; Wherein, the first address information is used to identify the source address information of the first data packet; the second data packet is a data packet associated with the first data packet.

32. A communication device, characterized in that, include: One or more processors; The processor is used to execute the communication method according to any one of claims 1 to 14.

33. A communication device, characterized in that, include: One or more processors; The processor is used to execute the communication method according to any one of claims 15 to 27.

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

Images