Communication method and apparatus and readable storage medium

Abstract

The present application relates to the technical field of communications, and in particular to a communication method and apparatus and a readable storage medium. The method comprises: without the need to establish an IPsec tunnel, a UE establishing a connection with a UPF for multi-path transmission, and a network instructing the UE and / or the UPF to use dual IP layers on a non-3GPP path to perform data transmission; or the network updating a rule to carry an IP address allocated to the UE by an access node of the non-3GPP path, and issuing the rule to the UE and / or the UPF, such that after the UE establishes a direct connection with the UPF, multi-path transmission of service data can be normally performed over a multi-path session under the guidance of the rule.

Description

A communication method, apparatus and readable storage medium

[0001] The present application claims priority from the Chinese patent application No. 202410405089.3 filed on April 3, 2024, and entitled "A communication method, apparatus and readable storage medium", the content of which is incorporated herein by reference in its entirety. TECHNICAL FIELD

[0002] The present application relates to the field of communication technology, and in particular to a communication method, apparatus and readable storage medium. BACKGROUND

[0003] Access traffic steering, switching, splitting (ATSSS) is an optional feature that can be supported by a terminal device (user equipment, UE) and a core network. The ATSSS feature supports the establishment of a multi-access session (MA Session) (e.g., MA PDU Session), which can simultaneously transmit traffic data through a 3rd generation partnership project (3GPP) access network (also understood as a 3GPP access path) and a non-3GPP access network (also understood as a non-3GPP access path) to improve transmission efficiency.

[0004] Currently, the main difference between a multi-access session and a single access PDU Session is that the user plane channel of the single access PDU Session only passes through one access network device. For example, the UE can send uplink data to a user plane function (UPF) entity through a radio access network (RAN) device; or the UPF can send downlink data to the UE through the RAN. The user plane channel of the multi-access session can include two access network devices (such as a 3GPP access network device and a non-3GPP access network device), which can be connected to the same UPF (or connected to the same UPF through another UPF). For example, the UE can send uplink data to the UPF through the RAN and / or a non-3GPP interworking function (N3IWF); or the UPF can send downlink data to the UE through the RAN and / or the N3IWF.

[0005] However, since the non-3GPP access network device (such as N3IWF or TNGF) has not been commercially used, in order to enable the commercial use of the ATSSS feature, it is necessary to consider proposing a new multi-access session type that can not require the UE to establish a non-3GPP path with the UPF through the non-3GPP access network device (such as N3IWF or TNGF), for example, removing the non-3GPP access network device (such as N3IWF or TNGF) and establishing a non-3GPP path in the architecture directly connected by the UE and the UPF.

[0006] At present, the implementation scheme of the new multi-access session type is still under exploration. SUMMARY

[0007] The embodiments of the present application provide a communication method, device and readable storage medium, which can enable the UE to establish a connection with the UPF for multi-path transmission without establishing an IPsec tunnel.

[0008] The present application will be described from different aspects below. It should be understood that the implementation and advantages of the different aspects below can be mutually referred to.

[0009] In a first aspect, the present application provides a communication method applied to a terminal device, the method comprising:

[0010] sending a first request message to a first network device; the first request message is used to request to establish a multi-path session, the multi-path session includes a non-3GPP path, and the terminal device does not support non-access layer (NAS) transmission under the non-3GPP path;

[0011] receiving first information from the first network device; the first information indicates that the terminal device uses a double-layer IP layer for data transmission under the non-3GPP path.

[0012] In the embodiments of the present application, the UE establishes a connection with the UPF for multi-path transmission without establishing an IPsec tunnel, the network can instruct the UE to use a double-layer IP layer for data transmission under the non-3GPP path, so that after the UE establishes a connection directly connected with the UPF, the UE can normally perform multi-path transmission of service data through the multi-path session under the guidance of the rules.

[0013] In a possible implementation, in combination with the first aspect, the method further comprises:

[0014] receiving third information from the first network device; the third information indicates that the terminal device sends or updates an IP address allocated by an access node of the non-3GPP path for the terminal device after establishing a connection with the second network device through the non-3GPP path;

[0015] sending or updating, to the first network device, an access node of the non-3GPP path, an IP address allocated by the access node for the terminal device.

[0016] In an embodiment of the present application, the network can instruct the UE to report an IP address allocated by an access node of the non-3GPP path for the UE, so that the network can subsequently instruct the UPF to perform packet transmission based on the IP address.

[0017] In a second aspect, the present application provides a communication method applied to a first network device, and the method comprises:

[0018] receiving a first request message from a terminal device, the first request message being used to request establishment of a multi-path session, the multi-path session comprising a non-3GPP path, and the terminal device not supporting NAS transmission in the non-3GPP path;

[0019] sending second information to a second network device, the second information instructing the second network device to perform data transmission using a double-layer IP layer in the non-3GPP path.

[0020] In an embodiment of the present application, the UE establishes a connection with the UPF for multi-path transmission without establishing an IPsec tunnel, and the network can instruct the UPF to perform data transmission using a double-layer IP layer in the non-3GPP path, so that the UE can normally perform multi-path transmission of service data through the multi-path session under the guidance of rules after the UE establishes a connection with the UPF.

[0021] In a possible implementation, in combination with the second aspect, the method further comprises:

[0022] sending first information to the terminal device, the first information instructing the terminal device to perform data transmission using a double-layer IP layer in the non-3GPP path.

[0023] In an embodiment of the present application, the UE establishes a connection with the UPF for multi-path transmission without establishing an IPsec tunnel, and the network can instruct the UE to perform data transmission using a double-layer IP layer in the non-3GPP path, so that the UE can normally perform multi-path transmission of service data through the multi-path session under the guidance of rules after the UE establishes a connection with the UPF.

[0024] In a possible implementation, in combination with the second aspect, the method further comprises:

[0025] sending a second request message to a third network device, the second request message being used to request establishment of a policy association for the multi-path session;

[0026] receiving a policy association establishment response message sent by the third network device; the policy association establishment response message comprises control information of the multi-path session;

[0027] determining first information and / or the second information based on the control information.

[0028] In a possible implementation, in combination with the second aspect, the method further includes:

[0029] sending third information to the terminal device; the third information indicates that the terminal device sends or updates an IP address allocated by an access node of the non-3GPP path for the terminal device after the terminal device establishes a connection with the second network device through the non-3GPP path; and / or,

[0030] sending fourth information to the second network device; the fourth information indicates that the second network device sends or updates an IP address allocated by an access node of the non-3GPP path for the terminal device after the second network device establishes a connection with the terminal device through the non-3GPP path.

[0031] In the embodiments of the application, the network can instruct the UE and / or the UPF to report an IP address allocated by an access node of the non-3GPP path for the UE, so that the network can subsequently instruct the UPF to perform packet transmission based on the IP address.

[0032] In a third aspect, the application provides a communication method applied to a second network device, and the method includes:

[0033] receiving second information sent by a first network device; the second information indicates that the second network device uses a double-layer IP layer to perform data transmission in a non-3GPP path.

[0034] In the embodiments of the application, the UE establishes a connection with the UPF to perform multi-path transmission without establishing an IPsec tunnel, and the network can instruct the UPF to use a double-layer IP layer to perform data transmission in a non-3GPP path, so that after the UE establishes a connection with the UPF directly, the UE can normally perform multi-path transmission of service data through the multi-path session under the guidance of rules.

[0035] In a possible implementation, in combination with the third aspect, the method further includes:

[0036] receiving fourth information from the first network device; the fourth information indicates that the second network device sends or updates an IP address allocated by an access node of the non-3GPP path for the terminal device after the second network device establishes a connection with the terminal device through the non-3GPP path;

[0037] The first network device is sent or the access node of the non-3GPP path is updated to allocate an IP address for a terminal device.

[0038] In the embodiments of the present application, the network can instruct the UPF to report an IP address allocated by the access node of the non-3GPP path for the UE, so that the network can instruct the UPF to transmit data packets based on the IP address.

[0039] In a possible implementation, in combination with the second aspect or the third aspect, the instruction that the second network device uses a double-layer IP layer for data transmission on the non-3GPP path comprises:

[0040] In a packet detection rule, the second network device is instructed to use any one of IP+UDP+IP, IP+IP+UDP or UDP+IP+IP for packet header removal on the non-3GPP path; and / or,

[0041] In a forwarding action rule, the second network device is instructed to use any one of IP+UDP+IP, IP+IP+UDP or UDP+IP+IP for packet header creation on the non-3GPP path.

[0042] In a possible implementation, in combination with the second aspect or the third aspect, the IP address in the double-layer IP layer comprises an IP address allocated by the access node of the non-3GPP path for a terminal device.

[0043] The fourth aspect provides a communication method applied to a terminal device, and the method comprises:

[0044] A first request message is sent to a first network device, and the first request message is used to request to establish a multi-path session, the multi-path session comprises a non-3GPP path, and the terminal device does not support non-access layer (NAS) transmission on the non-3GPP path.

[0045] A first rule from the first network device is received, and a source IP address in the first rule comprises a first IP address allocated by the access node of the non-3GPP path for the terminal device.

[0046] In the embodiments of the present application, the UE establishes a connection with the UPF for multi-path transmission without establishing an IPsec tunnel, the network can update a rule, carry an IP address allocated by the access node of the non-3GPP path for the UE in the rule, and issue the rule to the UE, so that the UE can perform data packet transmission according to the updated rule, and ensure that the UE can normally perform multi-path transmission of service data through the multi-path session under the guidance of the rule after the UE establishes a connection with the UPF.

[0047] In a possible implementation, in combination with the fourth aspect, the method further includes:

[0048] receiving third information from the first network device, the third information indicating that the terminal device sends or updates an IP address allocated to the terminal device by an access node of the non-3GPP path after the terminal device establishes a connection with the second network device through the non-3GPP path;

[0049] sending or updating, to the first network device, the IP address allocated to the terminal device by the access node of the non-3GPP path.

[0050] In an embodiment of the application, the network can instruct the UE to report an IP address allocated to the UE by an access node of the non-3GPP path, so that the network can subsequently update a rule based on the IP address.

[0051] In a possible implementation, in combination with the fourth aspect, the method further includes:

[0052] receiving second information from the first network device, the second information indicating that the terminal device sends or updates a second IP address allocated to the terminal device by an access node of the non-3GPP path, the first IP address being different from the second IP address.

[0053] In an embodiment of the application, when an IP address allocated to the UE by an access node of the non-3GPP path changes, the network can update a rule based on the updated IP address and send the updated rule to the UE.

[0054] In a fifth aspect, the application provides a communication method applied to a first network device, the method including:

[0055] receiving a first request message from a terminal device, the first request message being used to request establishment of a multi-path session, the multi-path session including a non-3GPP path, and the terminal device not supporting NAS transmission in the non-3GPP path;

[0056] sending a third rule to a second network device, the terminal device IP address in the third rule including a first IP address allocated to the terminal device by an access node of the non-3GPP path.

[0057] In the embodiments of the application, the UE establishes a connection with the UPF for multi-path transmission without establishing an IPsec tunnel, the network can update a rule, carry an IP address allocated by an access node of a non-3GPP path for the UE in the rule, and distribute the rule to the UPF, so that the UPF can perform packet detection according to the updated rule, and ensure that after the UE establishes a connection with the UPF directly, the UE can normally perform multi-path transmission of service data through the multi-path session under the guidance of the rule.

[0058] In a possible implementation, in combination with the fifth aspect, the method further includes:

[0059] sending, to the terminal device, a first rule, wherein a source IP address in the first rule includes a first IP address allocated by an access node of a non-3GPP path for the terminal device.

[0060] In the embodiments of the application, the UE establishes a connection with the UPF for multi-path transmission without establishing an IPsec tunnel, the network can update a rule, carry an IP address allocated by an access node of a non-3GPP path for the UE in the rule, and distribute the rule to the UPF, so that the UPF can perform packet detection according to the updated rule, and ensure that after the UE establishes a connection with the UPF directly, the UE can normally perform multi-path transmission of service data through the multi-path session under the guidance of the rule.

[0061] In a possible implementation, in combination with the fifth aspect, the method further includes:

[0062] sending, to the terminal device, third information; the third information indicates that after the terminal device establishes a connection with the second network device through the non-3GPP path, an IP address allocated by an access node of the non-3GPP path for the terminal device is sent or updated; and / or,

[0063] sending, to the second network device, fourth information; the fourth information indicates that after the second network device establishes a connection with the terminal device through the non-3GPP path, an IP address allocated by an access node of the non-3GPP path for the terminal device is sent or updated.

[0064] In the embodiments of the application, the network can instruct the UE / UPF to report an IP address allocated by an access node of a non-3GPP path for the UE, so that the network can perform rule updating based on the IP address subsequently.

[0065] In a possible implementation, in combination with the fifth aspect, the method further includes:

[0066] receiving the first IP address sent by the terminal device; and / or,

[0067] receiving the first IP address sent by the second network device.

[0068] In a possible implementation, in combination with the fifth aspect, the method further includes:

[0069] sending, to the terminal device, a second rule, wherein a source IP address in the second rule includes a second IP address allocated by the access node of the non-3GPP path to the terminal device, and the first IP address is different from the second IP address; and / or,

[0070] sending, to the second network device, a fourth rule, wherein a terminal device IP address in the fourth rule includes a second IP address allocated by the access node of the non-3GPP path to the terminal device, and the first IP address is different from the second IP address.

[0071] In the embodiments of the present application, when the IP address allocated by the access node of the non-3GPP path to the UE changes, the network can update the rules based on the updated IP address, and distribute the updated rules to the UE and / or the UPF.

[0072] In a possible implementation, in combination with the fifth aspect, the method further includes:

[0073] sending, to a third network device, a second request message, wherein the second request message is used to request establishment of policy association for the multi-path session;

[0074] receiving a policy association establishment response message sent by the third network device, wherein the policy association establishment response message includes control information of the multi-path session;

[0075] determining the third rule and / or the first rule based on the control information and the first IP address.

[0076] In a sixth aspect, the present application provides a communication method applied to a second network device, and the method includes:

[0077] receiving a third rule sent by a first network device, wherein a terminal device IP address in the third rule includes a first IP address allocated by the access node of the non-3GPP path to the terminal device.

[0078] In a possible implementation, in combination with the sixth aspect, the method further includes:

[0079] receiving fourth information from the first network device, wherein the fourth information indicates that the second network device sends or updates an IP address allocated by the access node of the non-3GPP path to the terminal device after the second network device establishes a connection with the terminal device through the non-3GPP path.

[0080] sending or updating, to the first network device, an IP address allocated to the terminal device by an access node of the non-3GPP access.

[0081] In a possible implementation, in combination with the sixth aspect, the method further includes:

[0082] receiving a fourth rule from the first network device, wherein a terminal device IP address in the fourth rule includes a second IP address allocated to the terminal device by an access node of the non-3GPP access, and the first IP address is different from the second IP address.

[0083] The seventh aspect provides a communication apparatus, and the apparatus includes:

[0084] a sending unit configured to send a first request message to a first network device, wherein the first request message is used to request to establish a multi-path session, the multi-path session includes a non-3GPP access, and the terminal device does not support non-access stratum (NAS) transmission in the non-3GPP access;

[0085] a receiving unit configured to receive first information from the first network device, wherein the first information indicates that the terminal device uses a double-layer IP layer to perform data transmission in the non-3GPP access.

[0086] In a possible implementation, in combination with the seventh aspect, the receiving unit is further configured to:

[0087] receive third information from the first network device, wherein the third information indicates that, after the terminal device establishes a connection with the second network device through the non-3GPP access, an IP address allocated to the terminal device by an access node of the non-3GPP access is sent or updated;

[0088] the sending unit is further configured to:

[0089] send or update, to the first network device, an IP address allocated to the terminal device by an access node of the non-3GPP access.

[0090] The eighth aspect provides a communication apparatus, and the apparatus includes:

[0091] a receiving unit configured to receive a first request message from a terminal device, wherein the first request message is used to request to establish a multi-path session, the multi-path session includes a non-3GPP access, and the terminal device does not support NAS transmission in the non-3GPP access;

[0092] The sending unit is configured to send second information to the second network device, where the second information indicates that the second network device uses a double-layer IP layer to perform data transmission in the non-3GPP path.

[0093] In a possible implementation, in combination with the eighth aspect, the sending unit is further configured to:

[0094] send first information to the terminal device, where the first information indicates that the terminal device uses a double-layer IP layer to perform data transmission in the non-3GPP path.

[0095] In a possible implementation, in combination with the eighth aspect, the sending unit is further configured to:

[0096] send a second request message to the third network device, where the second request message is used to request establishment of a policy association for the multi-path session;

[0097] The receiving unit is further configured to:

[0098] receive a policy association establishment response message sent by the third network device, where the policy association establishment response message includes control information of the multi-path session.

[0099] determine first information and / or the second information based on the control information.

[0100] In a possible implementation, in combination with the eighth aspect, the sending unit is further configured to:

[0101] send third information to the terminal device, where the third information indicates that, after the terminal device establishes a connection with the second network device through the non-3GPP path, an IP address allocated to the terminal device by an access node of the non-3GPP path is sent or updated; and / or,

[0102] send fourth information to the second network device, where the fourth information indicates that, after the second network device establishes a connection with the terminal device through the non-3GPP path, an IP address allocated to the terminal device by an access node of the non-3GPP path is sent or updated.

[0103] The ninth aspect provides a communication apparatus, which comprises:

[0104] The receiving unit is configured to receive second information sent by a first network device, where the second information indicates that the second network device uses a double-layer IP layer to perform data transmission in a non-3GPP path.

[0105] In a possible implementation, in combination with the ninth aspect, the receiving unit is further configured to:

[0106] receive fourth information from the first network device; the fourth information indicates that the second network device sends or updates an IP address allocated by an access node of the non-3GPP path to the terminal device after the second network device establishes a connection with the terminal device through the non-3GPP path;

[0107] The apparatus further includes a sending unit configured to send or update, to the first network device, an IP address allocated by an access node of the non-3GPP path to the terminal device.

[0108] In a possible implementation, in combination with the eighth aspect or the ninth aspect, the indication that the second network device uses a double-layer IP layer for data transmission in the non-3GPP path includes:

[0109] indication in the packet detection rule that the second network device uses any one of IP+UDP+IP, IP+IP+UDP, or UDP+IP+IP for packet header removal in the non-3GPP path; and / or,

[0110] indication in the forwarding action rule that the second network device uses any one of IP+UDP+IP, IP+IP+UDP, or UDP+IP+IP for packet header creation in the non-3GPP path.

[0111] In a possible implementation, in combination with the eighth aspect or the ninth aspect, the IP address in the double-layer IP layer includes an IP address allocated by an access node of the non-3GPP path to the terminal device.

[0112] The tenth aspect provides a communication apparatus, and the apparatus includes:

[0113] a sending unit configured to send a first request message to a first network device; the first request message is used to request establishment of a multi-path session, the multi-path session includes a non-3GPP path, and the terminal device does not support non-access layer (NAS) transmission in the non-3GPP path;

[0114] a receiving unit configured to receive first rules from the first network device, and a source IP address in the first rules includes a first IP address allocated by an access node of the non-3GPP path to the terminal device.

[0115] In a possible implementation, in combination with the tenth aspect, the receiving unit is further configured to:

[0116] receive third information from the first network device, the third information indicating that the terminal device sends or updates an IP address allocated to the terminal device by an access node of the non-3GPP path after the terminal device establishes a connection with the second network device through the non-3GPP path;

[0117] The sending unit is further configured to:

[0118] send or update, to the first network device, the IP address allocated to the terminal device by the access node of the non-3GPP path.

[0119] In a possible implementation, in combination with the tenth aspect, the receiving unit is further configured to: receive second rules from the first network device, a source IP address in the second rules including a second IP address allocated to the terminal device by the access node of the non-3GPP path, the first IP address being different from the second IP address.

[0120] The eleventh aspect provides a communication apparatus, which comprises:

[0121] a receiving unit configured to receive a first request message from a terminal device, the first request message being used to request establishment of a multi-path session, the multi-path session including a non-3GPP path, the terminal device not supporting NAS transmission in the non-3GPP path;

[0122] a sending unit configured to send third rules to a second network device, a terminal device IP address in the third rules including a first IP address allocated to the terminal device by an access node of the non-3GPP path.

[0123] In a possible implementation, in combination with the eleventh aspect, the sending unit is further configured to:

[0124] send first rules to the terminal device, a source IP address in the first rules including the first IP address allocated to the terminal device by the access node of the non-3GPP path.

[0125] In a possible implementation, in combination with the eleventh aspect, the sending unit is further configured to:

[0126] send third information to the terminal device, the third information indicating that the terminal device sends or updates an IP address allocated to the terminal device by the access node of the non-3GPP path after the terminal device establishes a connection with the second network device through the non-3GPP path; and / or,

[0127] send fourth information to the second network device; the fourth information indicates that the second network device sends or updates an IP address allocated by an access node of the non-3GPP path to the terminal device after the second network device establishes a connection with the terminal device through the non-3GPP path.

[0128] In a possible implementation, in combination with the eleventh aspect, the receiving unit is further configured to:

[0129] receive the first IP address sent by the terminal device; and / or,

[0130] receive the first IP address sent by the second network device.

[0131] In a possible implementation, in combination with the eleventh aspect, the sending unit is further configured to:

[0132] send a second rule to the terminal device, a source IP address in the second rule includes a second IP address allocated by an access node of the non-3GPP path to the terminal device, and the first IP address is different from the second IP address; and / or,

[0133] send a fourth rule to the second network device, a terminal device IP address in the fourth rule includes a second IP address allocated by an access node of the non-3GPP path to the terminal device, and the first IP address is different from the second IP address.

[0134] In a possible implementation, in combination with the eleventh aspect, the sending unit is further configured to:

[0135] send a second request message to a third network device; the second request message is used to request establishment of a policy association for the multi-path session;

[0136] The receiving unit is further configured to:

[0137] receive a policy association establishment response message sent by the third network device; the policy association establishment response message includes control information of the multi-path session.

[0138] determine the third rule and / or the first rule based on the control information and the first IP address.

[0139] The twelfth aspect provides a communication apparatus, and the apparatus includes:

[0140] a receiving unit configured to receive a third rule sent by a first network device; a terminal device IP address in the third rule includes a first IP address allocated by an access node of the non-3GPP path to the terminal device.

[0141] In a possible implementation form, in combination with the twelfth aspect, the receiving unit is further configured to:

[0142] receive fourth information from the first network device, the fourth information indicating that the second network device sends or updates an IP address allocated to the terminal device by the access node of the non-3GPP path after the second network device establishes a connection with the terminal device through the non-3GPP path;

[0143] the sending unit is further configured to:

[0144] send or update, to the first network device, the IP address allocated to the terminal device by the access node of the non-3GPP path.

[0145] In a possible implementation form, in combination with the twelfth aspect, the receiving unit is further configured to:

[0146] receive fourth rules from the first network device, a terminal device IP address in the fourth rules including a second IP address allocated to the terminal device by the access node of the non-3GPP path, the first IP address being different from the second IP address.

[0147] In a thirteenth aspect, the present application provides a communication apparatus, which can include a processor, a transceiver and a memory. The memory is configured to store a computer program, the transceiver is configured to transceive various messages, and the computer program includes program instructions, which, when executed by the processor, cause the communication apparatus to perform the method described in any one of the possible implementation forms of the first aspect to the sixth aspect. The transceiver can be a radio frequency module in the communication apparatus, or a combination of a radio frequency module and an antenna, or an input / output interface of a chip or circuit.

[0148] In a fourteenth aspect, the present application provides a computer readable storage medium, which stores program instructions, when executed on a computer, cause the computer to perform the method described in any one of the possible implementation forms of the first aspect to the sixth aspect.

[0149] In a fifteenth aspect, the present application provides a program product containing program instructions, when executed, cause the method described in any one of the possible implementation forms of the first aspect to the sixth aspect to be performed.

[0150] In a sixteenth aspect, the present application provides a communication apparatus, which can be in the form of a chip, a device or a component of a device, etc. The apparatus includes a processor. The processor is configured to read and execute a program stored in a memory, so as to execute the communication method provided in any possible implementation manner of the first aspect to the sixth aspect. Optionally, the communication apparatus further includes the memory, and the memory is connected to the processor through a circuit. Further optionally, the communication apparatus further includes a communication interface, and the processor is connected to the communication interface. The communication interface is configured to receive a data packet and / or information to be processed. The processor acquires the data packet and / or information from the communication interface, processes the data packet and / or information, and outputs a processing result through the communication interface. The communication interface can be an input / output interface.

[0151] In a seventeenth aspect, the present application provides a chip system, which includes a processor. The processor is configured to support a device to implement functions related to any possible implementation manner of the first aspect to the sixth aspect, for example, to generate or process information related to the communication method. In a possible design, the chip system further includes a memory. The memory is configured to store necessary program instructions and data of the device. The chip system can be composed of a chip, or can include a chip and other discrete devices.

[0152] Optionally, the processor and the memory can be physically independent units, or the memory can be integrated with the processor.

[0153] In an eighteenth aspect, the present application provides a communication system. The communication system includes a terminal device, a first network device and a second network device. The terminal device is configured to execute the method in any possible implementation manner of the first aspect or the fourth aspect. The first network device is configured to execute the method in any possible implementation manner of the second aspect or the fifth aspect. The second network device is configured to execute the method in any possible implementation manner of the third aspect or the sixth aspect.

[0154] The technical effects achieved by the above aspects can be mutually referred or referred to the beneficial effects of the method embodiments shown below, which will not be described herein. BRIEF DESCRIPTION OF DRAWINGS

[0155] In order to more clearly illustrate the technical solutions in the embodiments of the present application or the background art, the drawings needed to be used in the embodiments of the present application or the background art will be described below.

[0156] FIG. 1 is a schematic architecture diagram of a communication system provided by an embodiment of the present application;

[0157] FIG. 2 is a schematic architecture diagram of a network supporting ATSSS characteristics;

[0158] Figure 3 is a schematic diagram of a network architecture based on untrusted non-3GPP access;

[0159] Figure 4 is a schematic diagram of a network architecture based on trusted non-3GPP access;

[0160] Figure 5 is a schematic diagram of a user plane protocol stack based on MPQUIC function;

[0161] Figure 6 is a schematic diagram of a user plane protocol stack on the untrusted non-3GPP side;

[0162] Figure 7 is a schematic diagram of a communication method according to an embodiment of the present application;

[0163] Figure 8 is a schematic diagram of a communication method according to an embodiment of the present application;

[0164] Figure 9 is a schematic diagram of a communication apparatus according to an embodiment of the present application;

[0165] Figure 10 is a schematic diagram of another communication apparatus according to an embodiment of the present application;

[0166] Figure 11 is a schematic diagram of still another communication apparatus according to an embodiment of the present application. DETAILED DESCRIPTION

[0167] The technical solutions in the embodiments of the present application will be described clearly and completely below with reference to the accompanying drawings in the embodiments of the present application.

[0168] In the description of the present application, the terms "first", "second", etc. are only used to distinguish different objects, and do not limit the quantity and execution order, and the terms "first", "second", etc. also do not necessarily distinguish different objects. For example, the first request message and the second request message, the first information and the second information, etc. are only used to distinguish different information, and do not limit the order. In addition, the terms "include" and "have" and any variations thereof are intended to cover non-exclusive inclusion. For example, a process, method, system, product or device, etc. including a series of steps or units, is not limited to the listed steps or units, but optionally includes other steps or units not listed, etc. or optionally includes other steps or units inherent to the process, method, product or device, etc.

[0169] In the description of the present application, unless otherwise specified, " / " means "or", for example, A / B can mean A or B. "And / or" in this article is only a description of the relationship between the associated objects, which means that there can be three relationships, for example, A and / or B, which can mean: A exists alone, A and B exist together, B exists alone, and the like. In addition, "at least one item", "one or more items" or the like means any combination of these items, including any combination of single item or multiple items. For example, at least one of a, b, or c can mean: a, b, c; a and b; a and c; b and c; or a and b and c. Where a, b, and c can be single or multiple.

[0170] In the description of the present application, the words "exemplary", "exemplarily" or "for example" are used to mean an example, illustration or description. Any embodiment or design solution described in the present application as "exemplary", "for example" or "for example" should not be interpreted as more preferred or more advantageous than other embodiments or design solutions. Rather, the use of "exemplary", "for example" or "for example" is intended to present the relevant concept in a specific way.

[0171] It can be understood that in the description of the present application, "when", "if" and "if" all refer to the corresponding processing of the device under certain objective conditions, not limited to time, and do not require the device to have a judgment action when implemented, nor does it mean that there are other limitations.

[0172] In the present application, "at the same time" can be understood as at the same time point, also can be understood as in a period of time, also can be understood as in the same cycle, which can be understood in combination with the context.

[0173] In the present application, the element expressed by the singular is intended to represent "one or more", not "one and only one", unless otherwise specified.

[0174] It can be understood that in the embodiments of the present application, "A and B correspond" means that B is associated with A and can be determined according to A. However, it should also be understood that the determination of B according to A does not mean that B is determined only according to A, but B can also be determined according to A and / or other information.

[0175] It can be understood that, in the embodiments of the present application, "for indicating" and "indicating" can include direct indication and indirect indication, and can also include explicit indication and implicit indication. When "certain indication information is used for indicating A" or "indication information of A" is described, the indication information can directly indicate A or indirectly indicate A, and it does not mean that A must be carried in the indication information. The information indicated by certain information is referred to as to-be-indicated information, and there are many ways to indicate the to-be-indicated information in the specific implementation process, for example but not limited to, the to-be-indicated information can be directly indicated, such as the to-be-indicated information itself or an index of the to-be-indicated information. The to-be-indicated information can also be indirectly indicated by indicating other information, where the other information and the to-be-indicated information have an association relationship. The to-be-indicated information can also be only indicated in part, and the other part of the to-be-indicated information is known or agreed in advance. For example, the indication of specific information can also be achieved by means of the arrangement order of each information agreed in advance (for example, a protocol). Thus, the indication overhead is reduced to a certain extent. At the same time, the common part of each information can be identified and uniformly indicated, so as to reduce the indication overhead caused by separately indicating the same information. In addition, the specific indication manner can also be various existing indication manners, for example but not limited to, the above indication manners and various combinations thereof. The specific details of various indication manners can refer to the prior art, and will not be described herein. As described above, for example, when multiple information of the same type needs to be indicated, the indication manner of different information can not be the same. In the specific implementation process, the required indication manner can be selected according to the specific needs, and the selected indication manner is not limited in the embodiments of the present application. In this way, the indication manner involved in the embodiments of the present application should be understood as covering various methods that can enable the to-be-indicated party to know the to-be-indicated information. The to-be-indicated information can be sent as a whole, or can be divided into multiple sub-information and sent separately, and the sending period and / or sending time of the sub-information can be the same or different. The specific sending method is not limited in the present application.

[0176] The technical solutions of the embodiments of the present application can be applied to various communication systems, for example: a universal mobile telecommunications system (UMTS) or a third generation (3G) system, a long term evolution (LTE) system or a fourth generation (4G) system, a worldwide interoperability for microwave access (WiMAX) communication system, a fifth generation (5G) system such as a new radio (NR) system, a network integrating multiple systems, an Internet of Things system, a vehicle-to-vehicle communication system, and a future communication system such as a sixth generation (6G) system or a seventh generation (7G) system. The technical solutions of the embodiments of the present application can also be applied to an open RAN (O-RAN or ORAN), a cloud radio access network (CRAN), or a communication network including two or more of the above networks. The technical solutions of the embodiments of the present application can also be applied to a sidelink communication system or other communication systems working in an unlicensed band, for example, a wireless local area network (WLAN) system. It can be understood that the "communication system working in an unlicensed band" mentioned in the present application refers to the communication system working in an unlicensed band in some cases, and of course, the communication system can also work in a licensed band in some other cases.

[0177] It should be understood that the network architecture and service scenarios described in the embodiments of the present application are for more clearly illustrating the technical solutions of the embodiments of the present application, and do not constitute a limitation on the technical solutions provided by the embodiments of the present application. It can be known by those skilled in the art that, as the communication network architecture evolves and new service scenarios appear, the technical solutions provided by the embodiments of the present application are also applicable to similar technical problems.

[0178] In order to better understand the communication method, device and readable storage medium disclosed by the embodiments of the present application, the following will first exemplarily describe the scenario architecture to which the embodiments of the present application can be applied. Referring to FIG. 1, FIG. 1 is an architecture schematic diagram of a communication system provided by the embodiments of the present application. As shown in FIG. 1, the architecture can include a user equipment (UE), a 3GPP side access network device, a non-3GPP side access point (AP), a core network device and a data network (DN). Among them,

[0179] The DN can be an internet, an IP multi-media service (IMS) network, a regional network, i.e., a local network, such as a multi access edge computing (MEC) network, etc. The DN is a destination of a packet data network (PDN) session or a protocol data unit (PDU) session access of the UE. The DN can include or be deployed with an application server, which can perform data transmission with the UE and provide service to the UE.

[0180] The core network device can be a core network device of a 4G system (such as an LTE system), a core network device of a 5G system (such as an NR system), or a core network device in a future communication system, such as a 6G system, a 7G system, etc. Taking the 5G system as an example, the core network device can include a user plane function (UPF) network element, an access and mobility management function (AMF) network element, a session management function (SMF) network element, etc., and can also include other network elements for slicing, authentication, charging or policy management, such as a policy control function (PCF) network element, an application function (AF) network element, a unified data management (UDM) network element, an authentication server function (AUSF) network element and a network slice selection function (NSSF) network element, etc. Among them,

[0181] The UPF network element is mainly responsible for processing user messages, such as forwarding, charging, etc. The user message can be received from the DN and transmitted to the UE through the 3GPP path and / or the non-3GPP path; the user message can also be received from the UE through the 3GPP path and / or the non-3GPP path and forwarded to the DN. The transmission resource and scheduling function provided by the UPF network element for the UE can be managed and controlled by the SMF network element.

[0182] The AMF network element can access the non-access layer (NAS) signaling (including session management (SM) signaling) of the UE through the N1 interface and access the signaling of the RAN through the N2 interface, complete the registration process of the UE and the forwarding of the SM signaling, and perform mobility management.

[0183] The SMF network element is mainly responsible for session management in a mobile network, such as session establishment, modification, release, update, and related rule distribution processes. In the embodiments of the present application, the SMF can generate ATSSS rules according to policy control and charging (PCC) rules, and send the ATSSS rules to the UE through the AMF; and the SMF can send N4 rules to the UPF for controlling the functions of the UPF and for the UPF to report some event information to the SMF.

[0184] It should be noted that the scheme in the embodiments of the present application can also be applied to other wireless communication networks, such as a 4G system network, and the core network devices of the above-mentioned 5G system can correspondingly become core network devices of the 4G system. For example, the core network devices of the 4G system can include mobile management entities (MMEs), service gateways (SGWs), public data network gateways (PDN gateways, PGWs), and other network elements for authentication and charging, such as home subscriber servers (HSSs), policy and charging rule functions (PCRFs), online charging systems (OCSs), and offline charging systems (OFCSs). Among them,

[0185] The MME is mainly responsible for mobility management, session management, user authentication and key management, encryption and integrity protection of the non-access stratum (NAS) layer signaling, tracking area list (TA LIST) management, and PGW / SGW selection, etc.

[0186] The SGW is mainly responsible for packet routing and forwarding functions, internet protocol (IP) header compression, IDLE state terminal, downlink data buffering, inter-eNodeB handover anchor, route optimization, transmission of data services in handover, and the like.

[0187] The PGW is mainly responsible for allocation of the IP address of the UE, and provides IP routing and forwarding functions; performs different charging and different policies according to users and services; and provides gateway functions for accessing external PDNs.

[0188] It should be further noted that each network element in the above 4G system network and 5G system network can also be referred to as a functional entity, which can be a network element implemented on a dedicated hardware, a software instance running on a dedicated hardware, or an instance of a virtualized function on a suitable platform, for example, the virtualization platform can be a cloud platform. In addition, different network elements or devices can communicate with each other through interfaces, and the interface names shown in FIG. 1 are only an example for illustration, and the embodiments of the present application do not make specific limitations thereto. Understandably, FIG. 1 is only a schematic diagram, and the communication system can also include other devices, such as wireless relay devices and wireless backhaul devices, etc., which are not shown in FIG. 1. For the convenience of understanding, the core network device of the 5G system network will be taken as an example to exemplarily illustrate the technical solutions provided by the embodiments of the present application. It should be understood that the core network device in the present application can also be a core network device of other system networks (such as 4G, 6G, etc.), which is not specifically limited herein.

[0189] The 3GPP side access network device is an access device through which a terminal device accesses a communication system in a wireless manner. The 3GPP side access network device can be a base station, an evolved NodeB (eNodeB), a transmission reception point (TRP), a next generation NodeB (gNB) in a 5th generation (5G) mobile communication system, a next generation NodeB in a 6th generation (6G) mobile communication system, a base station in a future mobile communication system, or an access node in a WiFi system, etc. The 3GPP side access network device can also be a module or unit that completes part of the functions of a base station, for example, it can be a central unit (CU) or a distributed unit (DU). The CU completes the functions of the radio resource control protocol and the packet data convergence protocol (PDCP) of the base station, and can also complete the function of the service data adaptation protocol (SDAP). The DU completes the functions of the radio link control layer and the medium access control (MAC) layer of the base station, and can also complete part of the physical layer or the entire physical layer. For specific descriptions of the above-mentioned protocol layers, reference can be made to the relevant technical specifications of the 3rd generation partnership project (3GPP). The 3GPP side access network device can be a macro base station, a micro base station, or an indoor station, and can also be a relay node, a donor node, etc.

[0190] The non-3GPP side access node includes a non-trusted non-3GPP access node and a trusted non-3GPP access node. The non-trusted non-3GPP access node can be an access node deployed by a non-operator, for example, an access point (AP) in a wireless fidelity (WiFi) system deployed at a user's home or a merchant; the trusted non-3GPP access node can be an access node deployed by an operator, for example, a WiFi AP deployed by an operator in a public place. In addition to the above-mentioned WiFi access type access nodes, the non-3GPP side access node can also be a Bluetooth access type access node, or a ZigBee access type access node, or an access node based on other wireless communication technologies, such as StarFlash technology, ultra wideband (UWB) technology, etc., which are not limited here. In the communication system architecture to which the communication method embodiments of the present application can be applied, no non-3GPP access network device (such as a non-3GPP interworking function (N3IWF), a trusted non-3GPP gateway function (TNGF), etc.) can be deployed, and the UE can directly connect to the UPF through the non-3GPP side access node to establish a non-3GPP path of a multi-path session, and can perform data transmission of the multi-path session with the UPF through the non-3GPP path.

[0191] The terminal device is a device with wireless transceiving function, which can send signals to a base station or receive signals from the base station. The terminal device can also be referred to as a terminal, user equipment (UE), mobile station, mobile terminal, etc. The terminal device can be widely applied to various scenarios, such as device-to-device (D2D) communication, vehicle to everything (V2X) communication, machine-type communication (MTC), internet of things (IOT), virtual reality, augmented reality, industrial control, automatic driving, remote medical treatment, smart grid, smart furniture, smart office, smart wear, smart transportation, smart city, etc. The terminal can be a mobile phone, tablet computer, computer with wireless transceiving function, wearable device, vehicle, airplane, ship, robot, mechanical arm, smart home device, etc. The embodiments of the present application do not limit the specific technology and specific device form of the terminal.

[0192] In the embodiments of the present application, the device for implementing the function of the terminal can be a terminal, or a device capable of supporting the terminal to implement the function, such as a chip system, or a communication module, or a modem, etc., which can be installed in the terminal. In the embodiments of the present application, the chip system can be composed of a chip, or can include a chip and other discrete devices. In the technical solutions provided by the embodiments of the present application, the device for implementing the function of the terminal is a terminal, and taking the terminal as an example of UE, the technical solutions provided by the embodiments of the present application are described. The embodiments of the present application do not limit the specific technology and specific device form adopted by the terminal device.

[0193] In the embodiments of the present application, the term "wireless communication" can also be referred to as "communication", and the term "communication" can also be described as "data transmission", "information transmission" or "transmission".

[0194] For the convenience of understanding, the following briefly introduces several terms or nouns related to the present application, so as to facilitate those skilled in the art to better understand the technical solutions of the embodiments of the present application.

[0195] Firstly, the network architecture supporting the ATSSS feature in the current R16 and R17 versions is described. Referring to FIG. 2, FIG. 2 is a schematic diagram of a network architecture supporting the ATSSS feature. The UE and the UPF in FIG. 2 both support the ATSSS feature, for example, the UE and the UPF both have the multi-path transmission control protocol function (MPTCP functionality), the multi-path fast UDP Internet connection function (MPQUIC functionality), the ATSSS lower layer function (ATSSS-LL functionality) or the performance measurement function (PMF), etc., so that the UE and the UPF can simultaneously perform data transmission through the 3GPP access network (which can also be understood as a 3GPP access path) and the non-3GPP access network (which can also be understood as a non-3GPP access path) after establishing a multi-access session.

[0196] Among them, the 3GPP access network refers to the access type of the access network as a 3GPP access type. The 3GPP access type can include the following access technologies: LTE (corresponding to a 4G cellular network), NR (corresponding to a 5G cellular network), or a satellite access mode defined by 3GPP (including low-orbit satellite, medium-orbit satellite, and synchronous satellite).

[0197] The non-3GPP access network refers to an access type of an access network being a non-3GPP access type. The non-3GPP access type includes untrusted non-3GPP access technology (for example, accessing a core network through a wireless access node purchased by an individual), trusted non-3GPP access technology (for example, accessing a core network through a wireless access node deployed by an operator), and wireline access technology. The non-3GPP access type can be WiFi, Bluetooth, ZigBee, and the like.

[0198] The access network device is an access device through which a terminal device accesses a communication system in a wireless manner, and can include a 3GPP access network device and a non-3GPP access network device. Among them,

[0199] The 3GPP access network device can be a base station, an evolved NodeB (eNodeB), a transmission reception point (TRP), a next generation NodeB (gNB) in a 5th generation (5G) mobile communication system, a next generation NodeB in a 6th generation (6G) mobile communication system, a base station in a future mobile communication system, and the like, and will not be enumerated one by one here.

[0200] The non-3GPP access network device can be a non-3GPP interworking function (N3IWF), a trusted non-3GPP gateway function (TNGF), a trusted WLAN interworking function (TWIF), or a wireline access gateway function (W-AGF), which can also be referred to as an AGF. If the access technology is untrusted non-3GPP access technology, the corresponding non-3GPP access network device can be an N3IWF; if the access technology is trusted non-3GPP access technology, the corresponding non-3GPP access network device can be a TNGF. In the current network architecture supporting a multi-access session, the UE is generally connected to a non-3GPP access network device through a non-3GPP access node on a non-3GPP path, and then accesses the core network through the non-3GPP access network device. The communication method provided in the embodiments of the present application can be applied to a network architecture without deploying a non-3GPP access network device (such as an N3IWF or a TNGF), and can establish a non-3GPP path of a multi-path session by directly connecting the UE and the UPF, and enable the UE and the UPF to transmit data of the multi-path session through the non-3GPP path.

[0201] Referring to FIG. 3, FIG. 3 is a schematic diagram of a network architecture based on untrusted non-3GPP access. The untrusted non-3GPP access network can be an access node (such as an access point (AP) in a wireless fidelity (WiFi) system) deployed by a non-operator, such as an access node deployed in a user's home or a merchant. The UE can first establish a connection with the untrusted non-3GPP access node, obtain an IP address, and then obtain IP identification information (such as address information) of the N3IWF through a domain name server (DNS) according to the criteria for N3IWF discovery and selection, establish an internet protocol security (IPSec) tunnel with the N3IWF, and finally access the 5GC through the N3IWF.

[0202] Referring to FIG. 4, FIG. 4 is a schematic diagram of a network architecture based on trusted non-3GPP access. The trusted non-3GPP access network can be an access node (i.e., a trusted non-3GPP access point in transit, TNAP) deployed by an operator, such as a WiFi AP deployed by an operator in a public place, etc. A UE can first select a public land mobile network (PLMN), and then select a non-3GPP access network in the PLMN that provides trusted connectivity, and then select a connection type (such as 5G connectivity or S2a connectivity of 4G), and finally access the core network through a TNGF.

[0203] Next, the protocol stack of the UE is briefly introduced. For example, the UE establishes a multi-access session (or a multi-path session, such as a multi-access PDU session, MA PDU session) through 3GPP access technology and non-3GPP access technology respectively, and uses MPQUIC offloading function to enable multi-path transmission.

[0204] Referring to FIG. 5, FIG. 5 is a schematic diagram of a user plane protocol stack based on MPQUIC function. During the MA PDU session establishment process, the UE can obtain the following address information from the core network (such as SMF or UPF): 1) the IP address of the MA PDU session; 2) two link-specific IP addresses; and 3) the IP address of the MPQUIC proxy on the UPF side. In one way, the UE can use the IP address of the MA PDU session as the source IP address of the IP layer, and use the IP address of the MPQUIC proxy on the UPF side as the destination IP address of the IP layer; the UPF can distinguish the 3GPP path and the non-3GPP path through N3 tunnel port information; in another way, the UE can use the two link-specific IP addresses as the source IP addresses of the IP layer on the 3GPP access path and the non-3GPP access path respectively, and use the IP address of the MPQUIC proxy on the UPF side as the destination IP address of the IP layer.

[0205] Referring to FIG. 6, which is a schematic diagram of a user plane protocol stack of a non-trusted non-3GPP side, since the UE needs to establish an IPsec tunnel with the N3IWF, the UE side needs to have two layers of IP layers, which are an Inner IP layer and an IP layer. For the Inner IP layer, the source IP address is the session IP address of the UE, and the destination IP address is allocated by the N3IWF to the UE and used to identify the IP address of the user plane, which can be generally referred to as an UP_IP_ADDRESS. For the IP layer below, the source IP address is an IP address allocated by an access point (AP) of a wireless local area network (WLAN) (such as the untrusted non-3GPP access network in FIG. 5), and the destination IP address is an N3IWF address. Therefore, through the IP address of the layer below, the non-trusted non-3GPP access network in the middle can route the data packet to the N3IWF, and according to the destination IP address of the Inner IP, the N3IWF can route the data packet to the UPF. It can be understood that when the UE establishes a MA PDU session, the source IP address of the Inner IP layer can be an IP address of the MA PDU session or a link-specific IP address.

[0206] Next, the ATSSS rule is briefly introduced. The SMF can generate the ATSSS rule according to the PCC rule, and can send the ATSSS rule to the UE through the AMF. The ATSSS rule can include but is not limited to the following contents:

[0207] 1. Rule identifier, used to uniquely identify the ATSSS rule;

[0208] 2. Rule Precedence, used to determine the order of the ATSSS rule;

[0209] 3. Traffic Descriptor, used to define a traffic flow. It can include one or more of the following information: Application descriptor, including one or more application identifiers, used to identify the application that produces the traffic flow; IP descriptor, including one or more five-tuples, used to identify the destination of the IP traffic flow; non-IP descriptor, including one or more descriptors, used to identify the destination of the non-IP traffic flow (such as an Ethernet data packet).

[0210] 4. Access Selection Descriptor, used to define part of the access selection. It can include the following information: steering mode, steering mode indication, threshold, steering function.

[0211] Wherein, the ATSSS rule does not contain IP descriptor and non-IP descriptor at the same time.

[0212] The following is a brief introduction to N4 rules. N4 rules are sent by SMF to UPF, used to control the function of UPF and let UPF report some event information to SMF. N4 rules can include but not limited to the following rules:

[0213] 1. Packet Detection Rule (PDR): contains information for classifying data packets arriving at the UPF.

[0214] 2. Forwarding Action Rule (FAR): contains information on whether to forward, drop or buffer traffic identified by PDR.

[0215] 3. Multi-Access Rule (MAR): contains information on how to handle steering, switching or steering in a multi-access session (MA session). Generally, this MAR rule is used in MA session.

[0216] 4. Usage Reporting Rule (URR): contains information for defining how to count traffic identified by PDR and how to report measurements.

[0217] 5. QoS Enforcement Rule (QER): contains information related to the enforcement of QoS for traffic identified by PDR.

[0218] 6. Session Reporting Rule (SRR): contains information requesting user plane function to detect and report events that are not related to specific PDR in PDU session, nor related to usage measurement.

[0219] Wherein,

[0220] A packet detection rule (PDR rule) can include one or more of the following parameters: a terminal device IP address (UE IP address), a packet filter set (Packet Filter Set), or outer header removal (Outer header removal), etc. The packet filter set (IP packet filter set) can support any combination of the following packet filters:

[0221] - Source / destination IP address or IPv6 prefix.

[0222] - Source / destination port number.

[0223] - Protocol ID of the protocol above IP / Next header type.

[0224] - Type of Service (TOS) (IPv4) / Traffic class (IPv6) and Mask.

[0225] - Flow Label (IPv6).

[0226] - Security parameter index.

[0227] - Packet Filter direction.

[0228] A forwarding action rule (FAR) can be used to define how to buffer, discard, or forward a packet, including packet encapsulation / decapsulation and forwarding destination. The forwarding action rule (FAR) can include an outer header creation (Outer header creation) parameter and other parameters required for transmitting a packet (such as a transport level marking (Transport level marking), a forwarding policy (Forwarding policy), etc.).

[0229] Next, the technical problems to be solved by the present application are analyzed and proposed. Since non-3GPP access network devices (such as N3IWF or TNGF) have not been commercially used, in order to make the characteristics of ATSSS commercially available, a new multi-access session type is considered to be proposed, without the need for the UE to establish a non-3GPP path with the N3IWF or TNGF, for example, removing the N3IWF or TNGF, and the UE directly connecting to the UPF (such as the architecture shown in FIG. 1). Under this architecture, the UE can not need to establish an IPsec tunnel with the UPF, and compared with the architecture with N3IWF or TNGF, the protocol stack of the UE on the non-3GPP side is less than two layers of Inner IP and IPSec. Therefore, for the UE, the source IP address of the remaining IP layer is the IP address allocated by the WLAN AP, and the destination IP address is the IP address on the UPF side.

[0230] In the existing architecture with N3IWF or TNGF, the source IP address used by the UE side is the IP address allocated by the network side, for example, the MA PDU session IP address or the link-specific IP address. Therefore, the SMF can include the IP address information in the rules issued to the UPF and the UE, so that the UE and the UPF can detect the data packets according to the traffic flow and the rules issued by the SMF, and perform data transmission according to the corresponding policy rules, for example, determine the transmission path (MAR rule of the UPF), determine the forwarding action (FAR rule of the UPF), etc.

[0231] Therefore, there is an urgent need for a communication method to solve the problem of how to issue correct rules to ensure normal transmission of traffic flow under this type of multi-access session.

[0232] At present, the implementation scheme of this type of multi-access session is still under exploration.

[0233] Therefore, the present application proposes a communication method, device and readable storage medium, which can enable the UE to establish a connection with the UPF for multi-path transmission without establishing an IPsec tunnel. Specifically,

[0234] Manner one: the network side (e.g. PCF or SMF) can instruct the UE and UPF to use double IP layers for data transmission in the non-3GPP path. For example, in the non-3GPP side, the protocol stack of the UE and UPF can add an IP layer (similar to Inner IP layer), in which the source IP address can be the session IP address or a link-specific IP address, and the destination IP address is the IP address of the UPF. The advantage of this manner is that for the upper IP layer, the UE and UPF can perform packet detection or encapsulation according to the existing rules. Optionally, for the PDR rule used by the UPF, a new message header combination can be added in the outer header removal parameter, such as any one of UDP+IP+IP, IP+UDP+IP or IP+IP+UDP. In addition, for the FAR rule used by the UPF, a new message header combination can be added in the outer header creation parameter, such as any one of UDP+IP+IP, IP+UDP+IP or IP+IP+UDP. Thus, the UPF can know that an additional IP layer needs to be added in the non-3GPP path. In one possible implementation, the network (e.g. PCF or SMF) can instruct the UPF to record the source IP address of the lower IP layer of the UE's uplink packet for the traffic flow in the non-3GPP path, and use the source IP address as the destination IP address of the lower IP layer of the downlink packet when sending the downlink packet to the UE through the non-3GPP path. In another possible implementation, the network side (e.g. PCF or SMF) can instruct the UPF to report the source IP address of the lower IP layer of the UE's uplink packet in the non-3GPP path, and update the rule. The rule includes the source IP address, instructing the UPF to use the IP address as the destination IP address of the lower IP layer when sending the downlink packet to the UE.

[0235] In the case that the UE and the UPF only transmit data through one layer of IP layer on the non-3GPP side (i.e., the source IP address of the UE is the IP address allocated by the WLAN AP), the network side (e.g., the PCF or the SMF) can send a rule to enable the data packet detection to cover the data flow on the non-3GPP side. For example, the UE IP address in the packet detection rule (e.g., the Packet Detection Rule) is included or replaced by the IP address allocated by the WLAN AP (i.e., the address of the non-3GPP path); optionally, the UPF can be instructed to report the changed source IP address to the SMF when the source IP address from the non-3GPP path changes, and the SMF sends an updated rule to the UE and / or the UPF according to the changed IP address. Alternatively, the SMF can also instruct the UE to report the updated address of the non-3GPP path, and the SMF sends an updated rule to the UE and / or the UPF according to the updated IP address. Alternatively, the SMF can instruct the UPF to associate all the uplink data packets from the non-3GPP path to the IP address of the multi-path session, and the UPF can record the source IP address of the non-3GPP path and use the IP address as the destination IP address of the downlink data packet according to the association relationship when forwarding the downlink data packet through the non-3GPP path.

[0236] In order to better understand the communication method provided by the embodiments of the present application, the technical solutions of the communication method provided by the embodiments of the present application will be described below in combination with more drawings.

[0237] In order to clearly describe the technical solutions of the present application, the present application will be described through multiple embodiments. In the present application, the same or similar parts between different embodiments or implementation manners can be mutually referenced. In the present application, the terms and / or descriptions of different embodiments and different implementation manners / implementation methods / realization methods have consistency and can be mutually referenced if there is no special description and no logical conflict. The technical features of different embodiments and different implementation manners / implementation methods / realization methods can be combined to form new embodiments, implementation manners, implementation methods, or realization methods according to their inherent logical relationship. The implementation manners of the present application described below do not constitute a limitation on the protection scope of the present application.

[0238] Please refer to FIG. 7, which is a flowchart of a communication method provided by an embodiment of the present application. The method can be applied to a terminal device, a first network device and a second network device. The terminal device can be the terminal in FIG. 1 or a module applied to the terminal. The first network device and the second network device can be the core network device in FIG. 1. The first network device can be a device with a session management function (e.g., SMF), and the second network device can be a device with a user packet processing function (e.g., UPF). For ease of understanding, the communication method of the embodiment of the present application is exemplarily described below with the first network device as SMF and the second network device as UPF. Alternatively, the communication method can also involve other devices in FIG. 1, such as a device with an access and mobility management function (e.g., AMF) and a device with a charging and policy management function (e.g., PCF). That is, the terminal device, SMF and UPF in FIG. 1 can be used to support and execute the method flow shown in FIG. 7. The present application does not limit the split function or the multi-path transmission protocol used by the UE and the UPF. For example, the split function can be an MPQUIC split function, an MPTCP split function or an MPQUIC lower layer (MPQUIC LL) split function. For another example, the multi-path transmission protocol can be MPQUIC or MPTCP. The present application takes MPQUIC as an example for illustration. The method flow shown in FIG. 7 can include but is not limited to the following steps:

[0239] S701: The UE sends a session establishment request message to the AMF.

[0240] For example, the PDU session establishment request message (PDU Session Establishment Request).

[0241] Correspondingly, the AMF receives the session establishment request message sent by the UE.

[0242] The session establishment request message can be a NAS message, and can carry one or more of the following parameters: session identifier (e.g., PDU Session ID), request type (e.g., Request Type), data network name requested by the UE (e.g., UE Requested DNN), slice information (e.g., S-NSSAI), and the like. The request type (Request Type) is a new multi-path session request type, which can be referred to as ATSSS-Lite or ATSSS-Lite MAPDU, for example, for requesting to establish a multi-path session including a non-3GPP path, and the terminal device does not support non-access layer (NAS) transmission on the non-3GPP path. In other words, the Request Type can indicate that the UE does not register on the non-3GPP side in the multi-path session, and / or that the UE only needs to establish a transmission path with the UPF on the non-3GPP side.

[0243] S702: The AMF sends a create session context request message to the SMF.

[0244] For example, the create session context request message (e.g., Nsmf_PDUSession_CreateSMContext Request) of the PDU session.

[0245] Correspondingly, the SMF receives the create session context request message sent by the AMF.

[0246] The create session context request message can carry one or more of the following parameters: UE identifier (e.g., SUPI), DNN requested by the UE, PDU Session ID, Request Type, and the like.

[0247] The above steps S701-S702 can be understood as that the UE sends a PDU session establishment request message (corresponding to a first request message) to the SMF. The first request message is used to request to establish a multi-path session including a non-3GPP path, and the terminal device does not support non-access layer (NAS) transmission on the non-3GPP path. Correspondingly, the SMF receives the first request message from the terminal device. In this process, the AMF can simply process and forward the request message sent by the UE, such as sending a create session context request message to the SMF.

[0248] Optionally, the above communication method can further include step S703.

[0249] S703: The SMF obtains session management subscription data from a UDM (unified data management function).

[0250] The subscription data can include information on whether to allow establishment of a multi-access session (MA PDU session).

[0251] S704: The SMF feeds back a create session context response message to the AMF.

[0252] For example, the create session context response message (Nsmf_PDUSession_CreateSMContext Response) of the PDU session.

[0253] Correspondingly, the AMF receives the create session context response message sent by the SMF.

[0254] S705: Perform a session authentication or authorization procedure. (Optional)

[0255] S706: The SMF selects a PCF and establishes a session policy association with the PCF.

[0256] Specifically, if dynamic policy control and charging rules (such as PCC rules) are needed, the SMF sends a policy association establishment request message (such as SM Policy Association Establishment Request) to the PCF. In one possible way, the SMF sends second request information to the PCF, requesting to establish a policy association for a multi-path session, and indicating that the multi-path session is a new multi-path session request type, for example, called ATSSS-Lite or ATSSS-Lite MA PDU, for which the terminal device does not support non-access layer (NAS) transmission under a non-3GPP path. In other words, for this multi-path session, the UE does not register on the non-3GPP side, and / or the UE only needs to establish a transmission path with the UPF on the non-3GPP side.

[0257] S707: The PCF sends a policy association establishment response message to the SMF.

[0258] Among them, the policy association establishment response message (for example, SM Policy Association Establishment Response) can contain multi-access session control information (MA PDU session control information) or control information of a new multi-path session type session, for example, called ATSSS-Lite Session control information, or ATSSS-Lite MA PDU Session control information. The control information can include steering mode, steering functionality, and the like.

[0259] S708: The SMF selects a suitable UPF.

[0260] S709: The SMF establishes an N4 connection with the UPF.

[0261] Specifically, the SMF sends a rule to the UPF. The rule can include one or more of the following rules: a rule for performing data packet detection (referred to as a packet detection rule), a rule for performing a data packet forwarding action (referred to as a forwarding action rule), a rule for indicating multi-path transmission (referred to as a multi-access rule), and the like. For example, the rule can be an N4 rule, which can include a packet detection rule (PDR), a forwarding action rule (FAR), a multi-access rule (MAR), and the like. Among them, the MAR rule can include steering mode, steering functionality, forwarding action rule, and the like.

[0262] In a possible implementation, the SMF can send the second information to the UPF, for example, after the N4 connection is established. The second information can indicate that the UPF uses the double-layer IP layer for data transmission on the non-3GPP path of the multi-path session. Optionally, the manner in which the SMF indicates the UPF to use the double-layer IP layer for data transmission on the non-3GPP path of the multi-path session can be that the SMF indicates, in a packet detection rule (for example, a PDR), the UPF to perform packet header removal using any one of IP+UDP+IP, IP+IP+UDP or UDP+IP+IP on the non-3GPP path, for example, by indicating in a packet header removal (outer header removal) parameter; and / or, the SMF indicates, in a forwarding action rule (for example, a FAR), the UPF to perform packet header creation using any one of IP+UDP+IP, IP+IP+UDP or UDP+IP+IP on the non-3GPP path, for example, by indicating in a packet header creation (outer header creation) parameter. For example, the UPF can remove the packet header of the double-layer IP layer when receiving an uplink data packet from the UE through the non-3GPP path (or receiving an uplink data packet sent by the UE through the non-3GPP path) according to the second information. For example, the UPF can encapsulate the packet header of the double-layer IP layer when sending a downlink data packet to the UE through the non-3GPP path according to the second information. For example, the SMF can include the second information in the N4 rule sent to the UPF.

[0263] In another possible implementation, the SMF can instruct the UPF to report an IP address used by the UE on the non-3GPP path. The IP address can be an IP address allocated to the UE by a WLAN AP to which the UE is connected on the non-3GPP path. For example, the IP address can be an IP address after network address translation (NAT) performed by the WLAN AP.

[0264] It should be noted that the SMF instructs the UPF to use the double-layer IP layer for data transmission on the non-3GPP path of the multi-path session. This instruction can be given before the multi-path fast UDP Internet connection (MPQUIC) is established between the UE and the UPF, such as the instruction in step S709; or it can be given after the multi-path fast UDP Internet connection (MPQUIC) is established between the UE and the UPF, such as the instruction in step S719. The instruction before the establishment of MPQUIC can save signaling, i.e., the subsequent step S719 can not be executed; and the instruction after the establishment of MPQUIC can avoid logical disorder and reduce resource waste caused by the establishment of MPQUIC between the UE and the UPF after the instruction in step S709.

[0265] Correspondingly, after the SMF sends the N4 rule to the UPF, the UPF can send the CN tunnel information and the address information of the UPF to the SMF. The address information of the UPF can be used later for the UE to establish a QUIC connection (including a 3GPP path and a non-3GPP path) with the UPF.

[0266] S710: The SMF sends first information to the AMF.

[0267] In a possible implementation, the SMF can instruct the UE to use the double-layer IP address for transmission on the non-3GPP path. For example, the SMF can instruct the UE to use the double-layer IP address for transmission on the non-3GPP path when the UE establishes a transmission path with the UPF through the non-3GPP path. The SMF can send first information to the UE, and the first information instructs the terminal device to use the double-layer IP layer for data transmission on the non-3GPP path. In a possible implementation, the SMF can first send the first information to the AMF through an N1N2 message transmission message, and then send the first information to the UE by the AMF.

[0268] Optionally, the N1N2 message transfer message (e.g., Namf_Communication_N1N2MessageTransfer) can contain session identification, N2 SM information (N2 interface session management information), and N1 SM Container (N1 interface session management container) and the like. Among them, the N2 SM information can be sent by the SMF to the RAN through the AMF, and the information in the N1 SM Container can be sent by the SMF to the UE through the AMF (for example, the AMF can send the UE through the NAS message). Exemplarily, the N2 SM information can contain the tunnel endpoint identification of the UPF and the like, which is sent to the RAN to tell the RAN where the uplink data should be sent (which can be understood as the destination address of the uplink data); the N1 SM Container can contain the PDU session establishment acceptance message (PDU Session Establishment Accept) and the ATSSS rule and the like. Among them, the ATSSS rule can include shunt mode, shunt function, threshold value and the like. Optionally, in the N1N2 message sent by the SMF to the AMF, the SMF can also indicate the AMF which access type path the message is transmitted through (for example, through 3GPP access), so that the AMF can send the N1N2 message to the access network device corresponding to the access type path. Exemplarily, the SMF can indicate the AMF to send the message through the 3GPP access, so in the following step S711, the AMF sends the content included in the message to the RAN. Exemplarily, the SMF can first send the first information to the UE through the N1 SM container in the N1N2 message transfer message.

[0269] It should be noted that the SMF instructs the UE to use a double IP layer for data transmission in the non-3GPP path of the above multi-path session. It can be instructed before the multi-path fast UDP Internet connection (MPQUIC) is established between the UE and the UPF, such as the instruction in the above step S711; or it can be instructed after the multi-path fast UDP Internet connection (MPQUIC) is established between the UE and the UPF, such as the instructions in the following steps S720 and S721.

[0270] S711: The AMF sends the first information to the RAN.

[0271] In a possible implementation, the SMF can indicate that the UE needs to use a dual stack IP address when transmitting over the non-3GPP path. Optionally, the AMF can forward the first information from the SMF to the RAN, and the RAN can subsequently forward the first information to the UE, so that the SMF can indicate, through the first information, that the UE needs to use a dual stack IP address when transmitting over the non-3GPP path. For example, the AMF can carry the first information in an N2 PDU session request message, for example, the N2 PDU session request message can carry N2 SM information, and a NAS message that needs to be sent to the UE, and the NAS message can include a session identifier and an N1 SM container. The AMF can carry the first information in the N1 SM container parameter.

[0272] S712: The RAN establishes air interface resources with the UE, and sends the first information to the UE.

[0273] In a possible implementation, the SMF can indicate that the UE needs to use a dual stack IP address when transmitting over the non-3GPP path. Optionally, the RAN can forward a NAS message to the UE. The NAS message can include the first information from the SMF, so that the SMF can indicate, through the first information, that the UE needs to use a dual stack IP address when transmitting over the non-3GPP path. For example, the RAN can carry the first information in the NAS message. Optionally, the NAS message can also carry a PDU session establishment acceptance message and ATSSS rule and other parameter information related to the multi-path session. The ATSSS rule can include information such as a split mode, a split function, and a threshold value.

[0274] S713: The RAN sends a response message to the AMF.

[0275] The response message can be an N2 PDU session response message, which can carry a tunnel endpoint identifier on the RAN side (subsequently sent to the UPF through the AMF and the SMF), and the information is used to tell the UPF where the downlink data should be sent (which can be understood as the destination address of the downlink data through the 3GPP path).

[0276] S714: The AMF sends the message sent by the RAN to the SMF through an update session context request.

[0277] S715: The SMF sends the AN tunnel endpoint identifier information on the RAN side to the UPF through an N4 session modification procedure.

[0278] In a possible implementation, the SMF can instruct the UPF to report the IP address used by the UE in the non-3GPP path in step S715. The IP address can be an IP address allocated to the UE by a WLAN AP to which the UE is connected in the non-3GPP path. For example, the IP address can be an IP address after network address translation (NAT) performed by the WLAN AP.

[0279] S716: The SMF sends an update session context response message to the AMF.

[0280] S717: The UE establishes an MPQUIC connection with the UPF through the 3GPP path and the non-3GPP path respectively.

[0281] S718: The UPF reports the completion of the connection establishment to the SMF.

[0282] In a possible implementation, the UPF can send the IP address of the UE in the non-3GPP path to the SMF. The IP address can be an IP address allocated to the UE by a WLAN AP to which the UE is connected in the non-3GPP path. For example, the IP address can be an IP address after network address translation (NAT) performed by the WLAN AP. In another possible implementation, the UPF can send the IP address of the UE in the non-3GPP path to the SMF according to a configuration or an instruction from the SMF in step S709 or step S715.

[0283] Optionally, the communication method can further include steps S719-S721.

[0284] S719: The SMF sends second information to the UPF.

[0285] Specifically, the SMF can send second information to the UPF, which can indicate that the UPF uses a double IP layer for data transmission on the non-3GPP path of the multi-path session. Optionally, the manner in which the SMF indicates the UPF to use a double IP layer for data transmission on the non-3GPP path of the multi-path session can be to indicate in a packet detection rule (e.g., PDR) that the UPF uses any one of IP+UDP+IP, IP+IP+UDP, or UDP+IP+IP for packet header removal on the non-3GPP path, e.g., in an outer header removal parameter; and / or, to indicate in a forwarding action rule (e.g., FAR) that the UPF uses any one of IP+UDP+IP, IP+IP+UDP, or UDP+IP+IP for packet header creation on the non-3GPP path, e.g., in an outer header creation parameter. For example, the UPF can remove the packet header of the double IP layer when receiving an uplink data packet from the UE through the non-3GPP path (or receiving an uplink data packet sent by the UE through the non-3GPP path) according to the second information. And / or, the UPF can encapsulate the packet header of the double IP layer when sending a downlink data packet to the UE through the non-3GPP path according to the second information. For example, the SMF can include the second information in the N4 rule sent to the UPF.

[0286] S720: The SMF sends first information to the AMF.

[0287] In a possible implementation, the SMF can indicate that the UE needs to use a double IP address for transmission on the non-3GPP path. Optionally, the SMF can indicate through the first information that the UE needs to use a double IP address for transmission of a service flow on the non-3GPP path after the UE establishes a transmission path with the UPF through the non-3GPP path. That is, the SMF can send first information to the UE through the AMF, which indicates that the terminal device uses a double IP layer for data transmission on the non-3GPP path. For example, the SMF sends the first information to the UE through an N1 SM container. Optionally, for the case where the UE uses a double IP layer for data transmission on the non-3GPP path, in addition to the indication by the SMF sending information, the network side can also be pre-configured, and the pre-configuration can be sent to the UE when the UE accesses the network, so that the UE can know to use a double IP layer for data transmission on the non-3GPP path.

[0288] S721: The AMF sends the first information in step S720 to the UE through the RAN.

[0289] In a possible implementation, the SMF can indicate that the UE needs to transmit by dual-layer IP address when transmitting in the non-3GPP path. Optionally, the AMF and the RAN can forward the first information sent by the SMF to the UE, so that the SMF can indicate by the first information that the UE needs to transmit by dual-layer IP address when transmitting in the non-3GPP path.

[0290] Understandably, in the steps S709-S712, if the SMF does not indicate that the UE and the UPF need to use the dual-layer IP layer for data transmission in the non-3GPP path of the multi-path session, the indication in steps S719-S721 can be additionally performed, i.e., steps S719-S721 can be executed. If the SMF has indicated in the steps S709-S712 that the UE and the UPF use the dual-layer IP layer for data transmission in the non-3GPP path of the multi-path session, the indication in steps S719-S721 can not be additionally performed, i.e., steps S719-S721 can not be executed.

[0291] It should be noted that the IP address of the UE in the non-3GPP path is an IP address allocated to the UE by a non-3GPP access node (such as the WLAN AP in FIG. 7) or an IP address after the WLAN AP performs NAT on the uplink data packet of the UE. Alternatively, in the case where the SMF indicates that the data transmission in the non-3GPP path uses a double IP layer, the protocol stack of the UE can add an IP layer (similar to the Inner IP layer), and at this time, the protocol stack of the UE includes the original IP layer (which can be in the lower layer) and the added IP layer (which can be in the upper layer). Among them, when the UE sends an uplink data packet, in the added IP layer, the source IP address can be the session IP address or the link-specific IP address, and the destination IP address can be the IP address of the UPF (or the IP address of the MPQUIC proxy in the UPF); when the UE sends an uplink data packet, in the original IP layer, the source IP address can be the IP address allocated by the WLAN AP (or the IP address after NAT is performed), and the destination IP address can be the IP address of the UPF. Correspondingly, the protocol stack of the UPF also adds an IP layer (similar to the Inner IP layer), and at this time, the protocol stack of the UPF includes the original IP layer (which can be in the lower layer) and the added IP layer (which can be in the upper layer). Among them, when the UPF sends a downlink data packet, in the added IP layer, the source IP address can be the IP address of the UPF (or the IP address of the MPQUIC proxy in the UPF), and the destination IP address can be the session IP address or the link-specific IP address; when the UPF sends a downlink data packet, in the original IP layer, the source IP address can be the IP address of the UPF, and the destination IP address can be the IP address allocated by the WLAN AP. Among them, the IP address allocated by the WLAN AP to the UE can be an address obtained after the WLAN AP performs address translation (network address translation, NAT).

[0292] For example, when the UPF receives an uplink data packet from the UE through the non-3GPP path (or receives an uplink data packet sent by the UE through the non-3GPP path), the UPF removes the packet header of the two-layer IP layer. And / or, when the UPF sends a downlink data packet to the UE through the non-3GPP path, the UPF encapsulates the packet header of the two-layer IP layer. Correspondingly, when the UE receives a downlink data packet from the UPF through the non-3GPP path (or receives a downlink data packet sent by the UPF through the non-3GPP path), the UE removes the packet header of the two-layer IP layer. And / or, when the UE sends an uplink data packet to the UPF through the non-3GPP path, the UE encapsulates the packet header of the two-layer IP layer.

[0293] Since the IP address of the UE in the non-3GPP path is the IP address allocated to the UE by the non-3GPP access node (such as the WLAN AP in FIG. 7), the core network does not know the address information, and the address information can be dynamically changed (because the WLAN AP performs network address translation (NAT)), the UPF can need the SMF to instruct to include the IP address allocated to the UE by the WLAN AP in the lower-layer IP layer, so that the UPF knows how to transmit.

[0294] Optionally, when instructing the UPF to use the double-layer IP layer for data transmission in the non-3GPP path, the SMF can carry the IP address allocated to the UE by the WLAN AP and instruct the UPF to include the IP address in the lower-layer IP layer. For example, before instructing the UPF to include the IP address allocated to the UE by the WLAN AP in the lower-layer IP layer, the SMF can instruct the UE and / or the UPF to send or update the IP address allocated to the UE by the access node (such as the WLAN AP in FIG. 7) of the non-3GPP path after the UPF and the UE establish a connection through the non-3GPP path.

[0295] Optionally, when instructing the UPF to use the double-layer IP layer for data transmission in the non-3GPP path, the SMF can instruct the UPF to record the source IP address of the non-3GPP path when receiving an uplink data packet on the non-3GPP path, and use the IP address as the destination IP address of a downlink data packet when forwarding the downlink data packet on the non-3GPP path. In this way, resource waste caused by additional reporting of the IP address by the UE and / or the UPF can be reduced.

[0296] In summary, the scheme of the embodiment corresponding to FIG. 7 described above can enable the UE to establish a connection directly with the UPF without establishing an IPsec tunnel with the non-3GPP access network device (such as the N3IWF or the TNGF) and without deploying the non-3GPP access network device (such as the N3IWF or the TNGF), and by instructing the UE and / or the UPF to use the double-layer IP layer for data transmission in the non-3GPP path, the UE can normally perform multi-path transmission of service data through the multi-path session under the guidance of the rules after establishing a connection directly with the UPF.

[0297] In addition to the communication method of the UE and the UPF using the double-layer IP layer for data transmission in the non-3GPP path described above, the embodiment of the present application also provides a communication method of the UE and the UPF using a single-layer IP layer for data transmission in the non-3GPP path.

[0298] Please refer to FIG. 8, which is a flowchart of a communication method provided by an embodiment of the present application. The method can be applied to a terminal device, a first network device and a second network device. The terminal device can be the terminal in FIG. 1 or a module applied to the terminal. The first network device and the second network device can be the core network device in FIG. 1. The first network device can be a device with a session management function (such as SMF), and the second network device can be a device with a user packet processing function (such as UPF). For ease of understanding, the communication method of the embodiment of the present application is exemplarily described below with the first network device as SMF and the second network device as UPF. Optionally, the communication method can also involve other devices in FIG. 1, such as a device with an access and mobility management function (such as AMF) and a device with a charging and policy management function (such as PCF). That is, the terminal device, SMF and UPF in FIG. 1 can be used to support and execute the method flow shown in FIG. 8. The method flow shown in FIG. 8 can include but is not limited to the following steps:

[0299] S801: The UE sends a session establishment request message to the AMF.

[0300] For example, PDU session establishment request message (PDU Session Establishment Request).

[0301] Correspondingly, the AMF receives the session establishment request message sent by the UE.

[0302] The session establishment request message can be a NAS message, which can carry one or more of the following parameters: session identifier (such as PDU Session ID), request type (such as Request Type), data network name requested by the UE (such as UE Requested DNN), slice information (such as S-NSSAI) and the like. The request type (such as Request Type) is a new multi-path session request type, which can be referred to as ATSSS-Lite or ATSSS-Lite MAPDU, for example, for requesting to establish a multi-path session, the multi-path session including a non-3GPP path, and the terminal device not supporting non-access layer (NAS) transmission on the non-3GPP path. In other words, the Request Type can indicate that the UE is not registered on the non-3GPP side in the multi-path session, and / or that the UE only needs to establish a transmission path with the UPF on the non-3GPP side.

[0303] S802: The AMF sends a create session context request message to the SMF.

[0304] For example, a PDU session Create Session Context Request message (e.g., Nsmf_PDUSession_CreateSMContext Request).

[0305] In the Create Session Context Request message, one or more of the following parameters can be carried: UE identity (e.g., SUPI), DNN requested by the UE, PDU Session ID, Request Type, and the like.

[0306] The above steps S801-S802 can be understood as that the UE sends a PDU session establishment request message (corresponding to a first request message) to the SMF; the first request message is used to request to establish a multi-path session, the multi-path session includes a non-3GPP path, and the terminal device does not support non-access layer (NAS) transmission in the non-3GPP path. Correspondingly, the SMF receives the first request message from the terminal device. In this process, the AMF can perform simple processing and forwarding on the request message sent by the UE, such as that the AMF sends a Create Session Context Request message to the SMF.

[0307] Optionally, the above communication method can further include step S803.

[0308] S803: The SMF obtains session management subscription data from the UDM.

[0309] The subscription data can include information on whether to allow establishment of a multi-access session (e.g., MA PDU session).

[0310] S804: The SMF feeds back a Create Session Context Response message to the AMF.

[0311] For example, a PDU session Create Session Context Response message (Nsmf_PDUSession_CreateSMContext Response).

[0312] S805: Perform a session authentication or authorization process. (Optional)

[0313] S806: The SMF selects a PCF and establishes a session policy association with the PCF.

[0314] Specifically, if dynamic PCC rules are needed, the SMF sends a policy association establishment request message (e.g., SM Policy Association Establishment Request) to the PCF. In one possible way, the SMF sends second request information to the PCF for requesting to establish a policy association for a multi-path session, and indicates that the multi-path session is a new multi-path session request type, e.g., called ATSSS-Lite or ATSSS-Lite MAPDU, for which the terminal device does not support non-access stratum (NAS) transmission over the non-3GPP path. In other words, for the multi-path session, the UE is not registered on the non-3GPP side, and / or the UE only needs to establish a transmission path with the UPF on the non-3GPP side.

[0315] S807: The PCF sends a policy association establishment response message to the SMF.

[0316] The policy association establishment response message (e.g., SM Policy Association Establishment Response) can include multi-access session control information (MA PDU session control information) or control information for a new type of session, e.g., called ATSSS-Lite Session control information or ATSSS-Lite MAPDU Session control information. The control information can include steering mode, steering functionality, and the like.

[0317] S808: The SMF selects a suitable UPF.

[0318] S809: The SMF establishes an N4 connection with the UPF.

[0319] Specifically, the SMF sends rules to the UPF. The rules can include one or more of the following rules: a rule for performing packet detection (referred to as a packet detection rule), a rule for performing packet forwarding actions (referred to as a forwarding action rule), a rule for indicating multi-path transmission (referred to as a multi-access rule), and the like. For example, the rules can be N4 rules, which include a packet detection rule (PDR), a forwarding action rule (FAR), a multi-access rule (MAR), and the like. The MAR rule includes steering mode, steering functionality, forwarding action rule, and the like.

[0320] In a possible implementation, the SMF can instruct the UPF to send or update the IP address of the UE on the non-3GPP path. Optionally, after the N4 connection is established, the SMF can send fourth information to the UPF, which can instruct the UPF to send or update the IP address of the UE on the non-3GPP path after the connection between the terminal device and the UPF on the non-3GPP path is established. Alternatively, the fourth information instructs the UPF to send or update the IP address (or the IP address after NAT) allocated by the access node (such as the WLAN AP in FIG. 8) of the non-3GPP path for the terminal device after the connection between the UE and the UPF on the non-3GPP path is established. In other words, the SMF can instruct the UPF to report the source IP address and / or port information of the UE on the non-3GPP side, or instruct the UPF to report the source IP address and / or port information of the MPQUIC connection (or the QUIC connection) established through the address and port corresponding to the non-3GPP path.

[0321] Optionally, after the SMF sends the N4 rule to the UPF, the UPF can send CN tunnel information and address information of the UPF to the SMF. The address information of the UPF can be used later for the UE to establish a QUIC connection with the UPF (including the 3GPP path and the non-3GPP path).

[0322] S810: The SMF sends third information to the AMF.

[0323] In a possible implementation, the SMF can instruct the UE to send or update the IP address of the UE on the non-3GPP path. Optionally, the SMF can send third information to the AMF, and the AMF forwards the third information to the UE, so that the SMF can instruct the UE to send or update the IP address of the UE on the non-3GPP path after the connection between the UE and the UPF on the non-3GPP path is established, through the third information; or instruct the UE to send or update the IP address (or the IP address after NAT) allocated by the access node (such as the WLAN AP in FIG. 8) of the non-3GPP path for the terminal device after the connection between the UE and the UPF on the non-3GPP path is established, through the third information. In a possible implementation, the SMF can first send the first information to the AMF through the N1N2 message transmission message, and then send the first information to the UE by the AMF.

[0324] Optionally, the N1N2 message transfer message (e.g., Namf_Communication_N1N2MessageTransfer) can include session identification, N2 SM information (N2 interface session management information), and N1 SM Container (N1 interface session management container) and the like. Among them, the N2 SM information can be sent by the SMF to the RAN through the AMF, and the information in the N1 SM Container can be sent by the SMF to the UE (e.g., the subsequent AMF can send it to the UE through the NAS message). Optionally, the N2 SM information can include the tunnel endpoint identification of the UPF and the like, which is sent to the RAN to tell the RAN where the uplink data should be sent (which can be understood as the destination address of the uplink data); the N1 SM Container can include the PDU session establishment acceptance message (PDU Session Establishment Accept) and the ATSSS rule and the like. Among them, the ATSSS rule can include the split mode, the split function, the threshold value and the like. Optionally, in the N1N2 message sent by the SMF to the AMF, the SMF can also indicate the AMF which access type path the message is transmitted through (e.g., through 3GPP access), so that the AMF can send the N1N2 message to the access network device corresponding to the access type path. Exemplarily, the SMF can indicate the AMF to send the message through the 3GPP access, so in the following step S811, the AMF will send the content included in the message to the RAN.

[0325] Exemplarily, the SMF can send the third information to the UE through the N1 SM container in the N1N2 message transfer message, which can instruct the UE to send or update the IP address (or the IP address after NAT) allocated by the access node (e.g., the WLAN AP in FIG. 8) of the non-3GPP path for the UE after establishing a connection with the UPF through the non-3GPP path. Optionally, the SMF can instruct the UPF to report the IP address allocated by the WLAN AP for the UE through the above step S809, or instruct the UE to report the IP address allocated by the WLAN AP for the UE through the above step S810. That is, the SMF can instruct the UE and / or the UPF to report the IP address allocated by the WLAN AP for the UE, which is not limited here.

[0326] S811: The AMF sends the third information to the RAN.

[0327] In a possible implementation, the SMF can instruct the UE to send or update the IP address of the UE in the non-3GPP path. Optionally, the AMF can forward the third information from the SMF to the RAN, and the RAN can subsequently forward the third information to the UE, so that the SMF can instruct the UE to send or update the IP address of the UE in the non-3GPP path, or to send or update the IP address (or the IP address after NAT) allocated by the access node (such as the WLAN AP in FIG. 8) of the non-3GPP path for the terminal device.

[0328] For example, the AMF can carry the third information in the N2 PDU session request message, for example, the N2 PDU session request message can carry the N2 SM information, and the NAS message to be sent to the UE, and the session identifier and the N1 SM container can be included in the NAS message. Optionally, the SMF can carry the third information in the N1 SM container parameter. That is, the AMF can forward the third information sent by the SMF to the UE to the RAN, and the third information can instruct the UE to send or update the IP address allocated by the access node (such as the WLAN AP in FIG. 8) of the non-3GPP path for the UE after the UE establishes a connection with the UPF through the non-3GPP path.

[0329] S812: The RAN establishes air interface resources with the UE, and the RAN sends the third information to the UE.

[0330] In a possible implementation, the SMF can instruct the UE to send or update the IP address of the UE in the non-3GPP path. Optionally, the RAN can forward the third information from the SMF to the UE, so that the SMF can instruct the UE to send or update the IP address of the UE in the non-3GPP path, or to send or update the IP address (or the IP address after NAT) allocated by the access node (such as the WLAN AP in FIG. 8) of the non-3GPP path for the terminal device.

[0331] For example, the RAN can carry the third information by forwarding the NAS message. Optionally, the NAS message can also carry the PDU session establishment acceptance message and the ATSSS rule and other session-related parameter information. The ATSSS rule can include the offloading mode, the offloading function, the threshold value, and other information. In other words, the NAS message can carry the third information, and the third information can instruct the UE to send or update the IP address allocated by the access node (such as the WLAN AP in FIG. 8) of the non-3GPP path for the UE after the UE establishes a connection with the UPF through the non-3GPP path, that is, the RAN can forward the third information sent by the SMF to the UE.

[0332] S813: The RAN sends a response message to the AMF.

[0333] The response message can be an N2 PDU session response message, which can carry the tunnel endpoint identification on the RAN side (to be sent to the UPF via the AMF and the SMF later). The information is used to tell the UPF where the downlink data should be sent (which can be understood as the destination address of the downlink data via the 3GPP path).

[0334] S814: The AMF sends the message from the RAN to the SMF via an update session context request.

[0335] S815: The SMF sends the AN tunnel endpoint identification information on the RAN side to the UPF via an N4 session modification procedure.

[0336] In a possible implementation, the SMF can instruct the UPF to report the IP address used by the UE in the non-3GPP path in step S815. The IP address can be an IP address allocated by a WLAN AP connected by the UE in the non-3GPP path. For example, the IP address can be an IP address after network address translation (NAT) performed by the WLAN AP. That is, the SMF can send the fourth information to the UPF in the session modification procedure, and the fourth information can instruct the UPF to send or update the IP address of the UE in the non-3GPP path after the UPF establishes a connection with the terminal device via the non-3GPP path. Alternatively, the fourth information can instruct the UPF to send or update the IP address (or the IP address after NAT) allocated by an access node (for example, the WLAN AP in FIG. 8) of the non-3GPP path to the terminal device after the UPF establishes a connection with the UE via the non-3GPP path.

[0337] S816: The SMF sends an update session context response message to the AMF.

[0338] S817: The UE establishes an MPQUIC connection with the UPF via the 3GPP path and the non-3GPP path respectively.

[0339] S818: The UPF reports to the SMF that the connection is established.

[0340] Optionally, the UPF can report the IP address of the UE in the non-3GPP path (i.e., the IP address allocated by the WLAN AP to the UE) to the SMF according to the fourth information or configuration in step S810 or S815. For example, the IP address can be an IP address after NAT performed by the WLAN AP.

[0341] S819: The SMF sends a third rule to the UPF.

[0342] In the third rule sent by the SMF, the UE's IP address on the non-3GPP path can be included; or the UE's IP address in the third rule includes a first IP address allocated to the UE by an access node (such as the WLAN AP in FIG. 8) of the non-3GPP path. The third rule can instruct the UPF that the uplink packet comes from the UE when the source IP address of the uplink packet contains the IP address; or the third rule can instruct the UPF that the downlink packet is sent to the UE when the destination IP address of the downlink packet contains the IP address. Or the third rule can instruct the UPF that the destination IP address needs to contain the IP address when the downlink packet needs to be sent to the UE. For example, the third rule can include a packet detection rule, and the packet detection rule can include the IP address. In another possible implementation, the third rule can instruct the UPF to associate the packet from the non-3GPP path of the MP QUIC connection (or the packet from the QUIC connection corresponding to the non-3GPP path) with the IP address of the multi-path session, so that the UPF can record the source IP address of the non-3GPP path when receiving the uplink packet on the non-3GPP path in the future, and use the IP address as the destination IP address of the downlink packet when forwarding the downlink packet on the non-3GPP path.

[0343] In a possible implementation, the third rule can be an N4 rule, and the UE IP address parameter of the packet detection rule (such as PDR) in the N4 rule can contain the UE's IP address on the non-3GPP side, that is, the UE's IP address in the third rule includes a first IP address allocated to the UE by an access node (such as the WLAN AP in FIG. 8) of the non-3GPP path. Or, the SMF can instruct the UPF in the N4 rule to associate the packet from the non-3GPP path of the MP QUIC connection with the IP address of the multi-path session, so that the UPF can record the source IP address of the non-3GPP path when receiving the uplink packet on the non-3GPP path in the future, and use the IP address as the destination IP address of the downlink packet when forwarding the downlink packet on the non-3GPP path.

[0344] Optionally, the steering mode, steering functionality, and the like information can be included in the third rule, for example, the information can be included in the MAR rule. The steering mode, steering functionality, and the like information in the third rule can be determined based on the control information of the new multi-path session included in the policy association establishment response message in step S807, wherein the control information of the new multi-path session includes steering mode, steering functionality, and the like information. In other words, the third rule described above can be determined based on the control information sent by the PCF and the IP address of the UE at the non-3GPP side (i.e., the first IP address).

[0345] S820: The SMF sends the first rule to the AMF.

[0346] Optionally, the IP address of the UE at the non-3GPP path can be included in the first rule sent by the SMF; or the IP address of the terminal device in the first rule includes the first IP address allocated by the access node (such as the WLAN AP in FIG. 8) of the non-3GPP path to the terminal device. The first rule can indicate that when the UE sends an uplink data packet to the UPF on the non-3GPP path, the source IP address of the uplink data packet includes the IP address of the UE at the non-3GPP path, so that the UPF can know that the uplink data packet comes from the UE.

[0347] In one possible manner, the SMF can send the first rule to the AMF through the N1 SM container, and then the AMF sends the first rule to the UE. The source IP address in the first rule can include the IP address of the UE at the non-3GPP side, i.e., the source IP address in the first rule can include the first IP address allocated by the access node (such as the WLAN AP in FIG. 8) of the non-3GPP path to the terminal device. Optionally, the first rule can be an ATSSS rule, and exemplarily, the source IP address of the traffic descriptor parameter in the ATSSS rule can be the first IP address allocated by the WLAN AP to the terminal device; or the first rule can be a QoS rule, and exemplarily, the source IP address of the packet filter parameter in the QoS rule can be the first IP address allocated by the WLAN AP to the terminal device.

[0348] Optionally, the first rule can be an ATSSS rule, and the first rule can include information such as a steering mode, a steering functionality, a threshold value, and the like. The steering mode and the steering functionality in the first rule can be determined based on the control information of the new multi-path session included in the policy association establishment response message in step S807, wherein the control information of the new multi-path session includes information such as a steering mode and a steering functionality. In other words, the first rule described above can be determined based on the control information sent by the PCF and the IP address of the UE on the non-3GPP side (i.e., the first IP address).

[0349] S821: The AMF sends the first rule in step S820 to the UE through the RAN.

[0350] Specifically, the AMF and the RAN can forward the first rule sent by the SMF to the UE. The first rule can include the IP address of the UE on the non-3GPP path, or the terminal device IP address in the first rule includes the first IP address allocated to the terminal device by the access node (such as the WLAN AP in FIG. 8) of the non-3GPP path. The first rule can indicate that when the UE sends an uplink data packet to the UPF on the non-3GPP path, the source IP address of the uplink data packet includes the IP address of the UE on the non-3GPP path, so that the UPF can know that the uplink data packet comes from the UE. For example, the AMF and the RAN can carry the first rule described above in a NAS message and send the first rule to the UE.

[0351] It should be noted that since the IP address of the UE on the non-3GPP path is the IP address allocated to the UE by the non-3GPP access node (such as the WLAN AP in FIG. 8), this address information can change dynamically (because the WLAN AP performs address translation). Optionally, when the IP address allocated to the UE by the WLAN AP changes, for example, from the first IP address to the second IP address, the UE and / or the UPF can report the changed IP address (i.e., the second IP address) to the SMF, so that the SMF can update the third rule and the first rule described above according to the new IP address (i.e., the second IP address) (corresponding to the fourth rule and the second rule, respectively), and then distribute the updated fourth rule and the second rule to the UPF and the UE respectively, to ensure that when the IP address of the UE on the non-3GPP path changes, the UE and the UPF can still perform data transmission through the non-3GPP path. For example, the terminal device IP address in the fourth rule can include the changed second IP address, and the source IP address in the second rule can include the changed second IP address.

[0352] In summary, the scheme of the embodiment corresponding to FIG. 8 can enable the UE to establish a connection without establishing an IPsec tunnel with a non-3GPP access network device (such as an N3IWF or a TNGF) and without deploying a non-3GPP access network device (such as an N3IWF or a TNGF), by updating a rule (such as an N4 rule, an ATSSS rule, or a QoS rule) to contain the IP address of the UE on the non-3GPP path and respectively issuing the updated rule to a UPF (such as an N4 rule) and the UE (such as an ATSSS rule or a QoS rule), so that the UE and the UPF can perform packet detection according to the updated rule, thereby ensuring that the UE and the UPF can normally perform multi-path transmission of service data through the multi-path session under the guidance of the rule after the UE and the UPF establish a direct connection.

[0353] The above describes the method provided by the present application. In order to facilitate the implementation of the above scheme of the embodiments of the present application, the embodiments of the present application further provide corresponding devices or equipment.

[0354] The present application divides the functions of the device according to the method embodiments, for example, each function module can be divided, or two or more functions can be integrated into one processing module. The above integrated module can be realized in the form of hardware or software function module. It should be noted that the division of the module in the present application is illustrative, and is only a logical function division. In actual implementation, another division mode can be used. The device of the embodiments of the present application will be described below with reference to the drawings.

[0355] Please refer to FIG. 9, which is a structural schematic diagram of a communication device provided by an embodiment of the present application. The communication device 10 can be used to realize the functions of the first communication device involved in any of the above method embodiments, and thus can also realize the beneficial effects possessed by the above method embodiments.

[0356] As shown in FIG. 9, the communication device 10 can include a sending unit 100 and a receiving unit 101. Optionally, the communication device can further include a processing unit 102 (not shown in the figure), which can be used to generate various types of information sent by the sending unit 100 or process various types of information received by the receiving unit 101.

[0357] In a possible design, when the communication device 10 is used to realize the functions of the terminal device, the functions of each unit are as follows:

[0358] The sending unit 100 is configured to send a first request message to a first network device; the first request message is used to request to establish a multi-path session, the multi-path session includes a non-3GPP path, and the terminal device does not support non-access stratum (NAS) transmission on the non-3GPP path;

[0359] The receiving unit 101 is configured to receive first information from the first network device, wherein the first information indicates that the terminal device uses a double-layer IP layer for data transmission in the non-3GPP path.

[0360] In a possible implementation, the receiving unit 101 is further configured to:

[0361] receive third information from the first network device, wherein the third information indicates that, after the terminal device establishes a connection with the second network device through the non-3GPP path, an IP address allocated to the terminal device by an access node of the non-3GPP path is sent or updated;

[0362] The sending unit 100 is further configured to:

[0363] send or update, to the first network device, an IP address allocated to the terminal device by an access node of the non-3GPP path.

[0364] In a possible design, when the communication apparatus 10 is configured to implement the functions of the first network device, the functions of the units are as follows:

[0365] The receiving unit 101 is configured to receive a first request message from a terminal device, wherein the first request message is used to request establishment of a multi-path session, and the multi-path session includes a non-3GPP path, and the terminal device does not support NAS transmission in the non-3GPP path;

[0366] The sending unit 100 is configured to send second information to a second network device, wherein the second information indicates that the second network device uses a double-layer IP layer for data transmission in the non-3GPP path.

[0367] In a possible implementation, the sending unit 100 is further configured to:

[0368] send first information to the terminal device, wherein the first information indicates that the terminal device uses a double-layer IP layer for data transmission in the non-3GPP path.

[0369] In a possible implementation, the sending unit 100 is further configured to:

[0370] send a second request message to a third network device, wherein the second request message is used to request establishment of a policy association for the multi-path session;

[0371] The receiving unit 101 is further configured to:

[0372] receive a policy association establishment response message sent by the third network device; the policy association establishment response message comprises control information of the multi-path session;

[0373] determine first information and / or the second information based on the control information.

[0374] In a possible implementation, the sending unit 100 is further configured to:

[0375] send third information to the terminal device; the third information indicates that the terminal device sends or updates an IP address allocated by an access node of the non-3GPP path for the terminal device after the terminal device establishes a connection with the second network device through the non-3GPP path; and / or,

[0376] send fourth information to the second network device; the fourth information indicates that the second network device sends or updates an IP address allocated by an access node of the non-3GPP path for the terminal device after the second network device establishes a connection with the terminal device through the non-3GPP path.

[0377] In a possible design, when the communication apparatus 10 is configured to implement the function of the second network device, the functions of the units are as follows:

[0378] The receiving unit 101 is configured to receive second information sent by the first network device; the second information indicates that the second network device uses a double-layer IP layer for data transmission in the non-3GPP path.

[0379] In a possible implementation, the receiving unit 101 is further configured to:

[0380] receive fourth information from the first network device; the fourth information indicates that the second network device sends or updates an IP address allocated by an access node of the non-3GPP path for the terminal device after the second network device establishes a connection with the terminal device through the non-3GPP path.

[0381] The apparatus further comprises a sending unit 100 configured to send or update an IP address allocated by an access node of the non-3GPP path for the terminal device to the first network device.

[0382] In a possible implementation, the indication that the second network device uses a double-layer IP layer for data transmission in the non-3GPP path comprises:

[0383] indication in a packet detection rule (PDR) that the second network device uses any one of IP+UDP+IP, IP+IP+UDP or UDP+IP+IP in the non-3GPP path for packet header removal; and / or,

[0384] The second network device is instructed in the forwarding action rule (FAR) to create a packet header using any one of IP+UDP+IP, IP+IP+UDP or UDP+IP+IP in the non-3GPP path.

[0385] In a possible implementation, the IP address in the double-layer IP layer includes an IP address allocated by an access node of the non-3GPP path to the terminal device.

[0386] In a possible design, when the communication apparatus 10 is used to implement the functions of the terminal device, the functions of the units are as follows:

[0387] The sending unit 100 is configured to send a first request message to a first network device, where the first request message is used to request establishment of a multi-path session, and the multi-path session includes a non-3GPP path, and the terminal device does not support non-access stratum (NAS) transmission in the non-3GPP path.

[0388] The receiving unit 101 is configured to receive a first rule from the first network device, where a source IP address in the first rule includes a first IP address allocated by an access node of the non-3GPP path to the terminal device.

[0389] In a possible implementation, the receiving unit 101 is further configured to:

[0390] receive third information from the first network device, where the third information indicates that an IP address allocated by an access node of the non-3GPP path to the terminal device is sent or updated after the terminal device establishes a connection with the second network device through the non-3GPP path;

[0391] The sending unit 100 is further configured to:

[0392] send or update, to the first network device, the IP address allocated by the access node of the non-3GPP path to the terminal device.

[0393] In a possible implementation, the receiving unit 101 is further configured to receive a second rule from the first network device, where a source IP address in the second rule includes a second IP address allocated by the access node of the non-3GPP path to the terminal device, and the first IP address is different from the second IP address.

[0394] In a possible design, when the communication apparatus 10 is used to implement the functions of the first network device, the functions of the units are as follows:

[0395] The receiving unit 101 is configured to receive a first request message from a terminal device, the first request message being used to request establishment of a multi-path session, the multi-path session including a non-3GPP path, the terminal device not supporting NAS transmission over the non-3GPP path.

[0396] The sending unit 100 is configured to send a third rule to a second network device, the terminal device IP address in the third rule including a first IP address allocated to the terminal device by an access node of the non-3GPP path.

[0397] In a possible implementation, the sending unit 100 is further configured to:

[0398] send a first rule to the terminal device, the source IP address in the first rule including the first IP address allocated to the terminal device by the access node of the non-3GPP path.

[0399] In a possible implementation, the sending unit 100 is further configured to:

[0400] send third information to the terminal device, the third information indicating that the terminal device sends or updates the IP address allocated to the terminal device by the access node of the non-3GPP path after the terminal device establishes a connection with the second network device over the non-3GPP path; and / or,

[0401] send fourth information to the second network device, the fourth information indicating that the second network device sends or updates the IP address allocated to the terminal device by the access node of the non-3GPP path after the second network device establishes a connection with the terminal device over the non-3GPP path.

[0402] In a possible implementation, the receiving unit 101 is further configured to:

[0403] receive the first IP address sent by the terminal device; and / or,

[0404] receive the first IP address sent by the second network device.

[0405] In a possible implementation, the sending unit 100 is further configured to:

[0406] send a second rule to the terminal device, the source IP address in the second rule including a second IP address allocated to the terminal device by the access node of the non-3GPP path, the first IP address being different from the second IP address; and / or,

[0407] The fourth rule is sent to the second network device, and a terminal device IP address in the fourth rule includes a second IP address allocated to the terminal device by an access node of the non-3GPP path, and the first IP address is different from the second IP address.

[0408] In a possible implementation, the sending unit 100 is further configured to:

[0409] The second request message is sent to a third network device, and the second request message is used to request establishment of policy association for the multi-path session;

[0410] The receiving unit 101 is further configured to:

[0411] The policy association establishment response message is received, and the policy association establishment response message includes control information of the multi-path session.

[0412] The third rule and / or the first rule are determined based on the control information and the first IP address.

[0413] In a possible design, when the communication apparatus 10 is configured to implement the function of the second network device, the functions of the units are as follows:

[0414] The receiving unit 101 is configured to receive the third rule sent by the first network device, and a terminal device IP address in the third rule includes a first IP address allocated to the terminal device by an access node of the non-3GPP path.

[0415] In a possible implementation, the receiving unit 101 is further configured to:

[0416] The fourth information is received from the first network device, and the fourth information indicates that an IP address allocated to the terminal device by an access node of the non-3GPP path is sent or updated after the second network device establishes a connection with the terminal device through the non-3GPP path;

[0417] The sending unit 100 is further configured to:

[0418] The IP address allocated to the terminal device by the access node of the non-3GPP path is sent or updated to the first network device.

[0419] In a possible implementation, the receiving unit 101 is further configured to:

[0420] The fourth rule is received from the first network device, and a terminal device IP address in the fourth rule includes a second IP address allocated to the terminal device by an access node of the non-3GPP path, and the first IP address is different from the second IP address.

[0421] It should be noted that the functions of each functional unit / module in the communication apparatus described in the embodiments of the present application can be referred to the related description in the method embodiments, which will not be repeated here.

[0422] It can be understood that the specific description of the sending unit and the receiving unit shown in the above apparatus embodiments is only an example. For the specific functions or executed steps of the sending unit and the receiving unit, reference can be made to the description of any of the above method embodiments, which will not be described in detail here.

[0423] The communication apparatus of the embodiments of the present application is introduced above. The possible product forms of the communication apparatus are introduced below. It should be understood that any form of product with the functions of the communication apparatus described in the above FIG. 9 falls within the protection scope of the embodiments of the present application. It should also be understood that the following introduction is only an example, and the product form of the communication apparatus of the embodiments of the present application is not limited to this.

[0424] In a possible implementation, in the communication apparatus shown in the above FIG. 9, the processing unit 102 can be one or more processors; the sending unit 100 and the receiving unit 101 can be a transceiver; or the sending unit 100 can be a transmitter and the receiving unit 101 can be a receiver. In the embodiments of the present application, the processor and the transceiver can be coupled, and the connection manner of the processor and the transceiver is not limited in the embodiments of the present application. In the process of executing the above method, the process of sending information in the above method can be understood as the process of outputting the above information by the processor. When the above information is outputted, the processor outputs the above information to the transceiver so as to be transmitted by the transceiver. The above information can be further processed after being outputted by the processor, and then reaches the transceiver. Similarly, the process of receiving information in the above method can be understood as the process of receiving the inputted above information by the processor. When the processor receives the inputted information, the transceiver receives the above information and inputs it to the processor. Further, after the transceiver receives the above information, the above information can be further processed, and then inputted to the processor.

[0425] Referring to FIG. 10, FIG. 10 is a structural schematic diagram of another communication apparatus provided by the embodiments of the present application. The communication apparatus 20 can be the communication apparatus 10, or a chip therein. FIG. 10 only shows the main components of the communication apparatus 20. In addition to the processor 1001, the communication apparatus 20 can further include a transceiver 1002, a memory 1003, or an input / output device (not shown in the figure).

[0426] The processor 1001 is mainly used for processing communication protocol and communication data, and controlling the whole communication device, executing software program, and processing data of the software program. The memory 1003 is mainly used for storing software program and data. The transceiver 1002 can include control circuit and antenna, and the control circuit is mainly used for converting baseband signal and radio frequency signal, and processing radio frequency signal. The antenna is mainly used for receiving and transmitting radio frequency signal in the form of electromagnetic wave. Input and output device, such as touch screen, display screen, keyboard, etc. is mainly used for receiving user input data and outputting data to user.

[0427] When the communication device is powered on, the processor 1001 can read the software program in the memory 1003, interpret and execute the instructions of the software program, and process the data of the software program. When data needs to be transmitted wirelessly, the processor 1001 performs baseband processing on the data to be transmitted, and outputs the baseband signal to the radio frequency circuit. The radio frequency circuit converts the baseband signal into a radio frequency signal, and transmits the radio frequency signal in the form of electromagnetic wave through the antenna. When data is transmitted to the communication device, the radio frequency circuit receives the radio frequency signal through the antenna, converts the radio frequency signal into a baseband signal, and outputs the baseband signal to the processor 1001. The processor 1001 converts the baseband signal into data and processes the data.

[0428] In another implementation, the radio frequency circuit and the antenna can be arranged independently of the processor for baseband processing, such as in a distributed scenario, the radio frequency circuit and the antenna can be arranged remotely from the communication device.

[0429] The transceiver 1002 can include a receiver for performing the functions (or operations) of receiving, and a transmitter for performing the functions (or operations) of transmitting. And the transceiver is used for communicating with other devices / apparatuses through transmission medium.

[0430] Among them, the processor 1001, the transceiver 1002, and the memory 1003 can be connected through a communication bus.

[0431] For example, when the communication device 20 is used to execute the steps or methods or functions related to the terminal device described above, the transceiver 1002 can be used to send a first request message to a first network device; the first request message is used to request to establish a multi-path session, the multi-path session includes a non-3GPP path, and the terminal device does not support non-access layer (NAS) transmission under the non-3GPP path; receiving first information from the first network device; the first information indicates that the terminal device uses a double-layer IP layer for data transmission under the non-3GPP path. Optionally, the processor 1001 can be used to process the data received or transmitted by the transceiver 1002. Or,

[0432] The transceiver 1002 can be configured to send a first request message to a first network device, the first request message being used to request establishment of a multi-path session, the multi-path session including a non-3GPP path, the terminal device not supporting non-access stratum (NAS) transmission over the non-3GPP path. The processor 1001 can be configured to process data received or sent by the transceiver 1002.

[0433] For example, when the communication apparatus 20 is configured to perform the steps or methods or functions related to the first network device, the transceiver 1002 can be configured to receive a first request message from a terminal device, the first request message being used to request establishment of a multi-path session, the multi-path session including a non-3GPP path, the terminal device not supporting NAS transmission over the non-3GPP path, and send second information to a second network device, the second information indicating that the second network device uses a double IP layer for data transmission over the non-3GPP path. The processor 1001 can be configured to process data received or sent by the transceiver 1002. Alternatively,

[0434] The transceiver 1002 can be configured to receive a first request message from a terminal device, the first request message being used to request establishment of a multi-path session, the multi-path session including a non-3GPP path, the terminal device not supporting NAS transmission over the non-3GPP path, and send a third rule to a second network device, the terminal device IP address in the third rule including a first IP address allocated to the terminal device by an access node of the non-3GPP path. The processor 1001 can be configured to process data received or sent by the transceiver 1002.

[0435] For example, when the communication apparatus 20 is configured to perform the steps or methods or functions related to the second network device, the transceiver 1002 can be configured to receive second information sent by a first network device, the second information indicating that the second network device uses a double IP layer for data transmission over a non-3GPP path. The processor 1001 can be configured to process data received or sent by the transceiver 1002. Alternatively,

[0436] The transceiver 1002 can be configured to receive a third rule sent by a first network device, the terminal device IP address in the third rule including a first IP address allocated to the terminal device by an access node of the non-3GPP path. The processor 1001 can be configured to process data received or sent by the transceiver 1002.

[0437] It can be understood that the specific description of the processor and the transceiver can also refer to the description of the processing unit, the sending unit and the receiving unit in the apparatus embodiment related to FIG. 9, which will not be repeated here.

[0438] Optionally, the transceiver for implementing the receiving and sending functions can be included in the processor 1001. For example, the transceiver can be a transceiver circuit, or an interface, or an interface circuit. The transceiver circuit, the interface or the interface circuit for implementing the receiving and sending functions can be separate or integrated together. The transceiver circuit, the interface or the interface circuit described above can be used for reading and writing of code / data, or the transceiver circuit, the interface or the interface circuit described above can be used for transmission or transfer of signals.

[0439] Optionally, the processor 1001 can store instructions, which can be a computer program, running on the processor 1001, so as to enable the communication device 20 to perform the method described in the foregoing method embodiments. The computer program can be fixed in the processor 1001, in which case the processor 1001 can be implemented by hardware.

[0440] In an implementation manner, the communication device 20 can include a circuit, which can implement the functions of sending or receiving or communication in the foregoing method embodiments. The processor and the transceiver described in the present application can be implemented on an integrated circuit (IC), an analog IC, a radio frequency integrated circuit (RFIC), a mixed signal IC, an application specific integrated circuit (ASIC), a printed circuit board (PCB), an electronic device, etc. The processor and the transceiver can also be manufactured by various IC process technologies, such as complementary metal oxide semiconductor (CMOS), N-type metal oxide semiconductor (NMOS), P-type metal oxide semiconductor (PMOS), bipolar junction transistor (BJT), bipolar CMOS (BiCMOS), silicon germanium (SiGe), gallium arsenide (GaAs), etc.

[0441] Understandably, the communication apparatus shown in the embodiments of the present application can also have more components than those shown in FIG. 10, and the embodiments of the present application do not limit this. The method performed by the processor and the transceiver described above is only an example, and the specific steps performed by the processor and the transceiver can refer to the description of the method embodiments above.

[0442] In another possible implementation, in the communication apparatus related to FIG. 9, the processing unit 102 can be one or more logic circuits; the sending unit 100 and the receiving unit 101 can be input-output interfaces, also called communication interfaces, or interface circuits, or interfaces, etc. Alternatively, the sending unit can be an output interface, and the receiving unit can be an input interface. The sending unit and the receiving unit can be integrated into one unit, such as an input-output interface. Referring to FIG. 11, FIG. 11 is a structural schematic diagram of another communication apparatus provided by the embodiments of the present application. As shown in FIG. 11, the communication apparatus 30 includes a logic circuit 901 and an interface 902. That is, the above-mentioned processing unit 102 can be implemented by the logic circuit 901, and the sending unit 100 and the receiving unit 101 can be implemented by the interface 902. The logic circuit 901 can be a chip, a processing circuit, an integrated circuit, or a system on chip (SoC) chip, etc., and the interface 902 can be a communication interface, an input-output interface, a pin, etc. For example, FIG. 11 is a chip with the above-mentioned communication apparatus 30 as an example, which includes the logic circuit 901 and the interface 902.

[0443] In the embodiments of the present application, the logic circuit and the interface can also be coupled to each other. The specific connection mode of the logic circuit and the interface is not limited in the embodiments of the present application.

[0444] For example, when the communication apparatus 30 is used to perform the steps or methods or functions related to the terminal device described above, the interface 902 can be used to send a first request message to a first network device; the first request message is used to request to establish a multi-path session, the multi-path session includes a non-3GPP path, and the terminal device does not support non-access stratum (NAS) transmission under the non-3GPP path; receive first information from the first network device; the first information indicates that the terminal device uses a double IP layer for data transmission under the non-3GPP path. Optionally, the logic circuit 901 can be used to process the data received or sent by the interface 902. Alternatively,

[0445] The interface 902 can be configured to send a first request message to the first network device, the first request message being used to request to establish a multi-path session, the multi-path session including a non-3GPP path, the terminal device not supporting non-access stratum (NAS) transmission over the non-3GPP path. The interface 902 can be configured to receive a first rule from the first network device, the source IP address in the first rule including a first IP address allocated to the terminal device by an access node of the non-3GPP path. Optionally, the logic circuit 901 can be configured to process data received or sent by the interface 902.

[0446] For example, when the communication apparatus 30 is configured to perform the steps or methods or functions related to the first network device, the interface 902 can be configured to receive a first request message from the terminal device, the first request message being used to request to establish a multi-path session, the multi-path session including a non-3GPP path, the terminal device not supporting NAS transmission over the non-3GPP path, and send second information to the second network device, the second information indicating that the second network device uses a double IP layer for data transmission over the non-3GPP path. Optionally, the logic circuit 901 can be configured to process data received or sent by the interface 902. Alternatively,

[0447] The interface 902 can be configured to receive a first request message from the terminal device, the first request message being used to request to establish a multi-path session, the multi-path session including a non-3GPP path, the terminal device not supporting NAS transmission over the non-3GPP path, and send a third rule to the second network device, the terminal device IP address in the third rule including a first IP address allocated to the terminal device by an access node of the non-3GPP path. Optionally, the logic circuit 901 can be configured to process data received or sent by the interface 902.

[0448] For example, when the communication apparatus 30 is configured to perform the steps or methods or functions related to the second network device, the interface 902 can be configured to receive second information sent by the first network device, the second information indicating that the second network device uses a double IP layer for data transmission over the non-3GPP path. Optionally, the logic circuit 901 can be configured to process data received or sent by the interface 902. Alternatively,

[0449] The interface 902 can be configured to receive a third rule sent by the first network device, the terminal device IP address in the third rule including a first IP address allocated to the terminal device by an access node of the non-3GPP path. Optionally, the logic circuit 901 can be configured to process data received or sent by the interface 902.

[0450] It is to be understood that the specific description of the logic circuit 901 and the interface 902 can also refer to the description of the processing unit, the sending unit and the receiving unit involved in the device embodiments of FIG. 9, which will not be repeated here.

[0451] It is to be understood that the communication apparatuses shown in the embodiments of the present application can implement the methods provided by the embodiments of the present application in the form of hardware, or implement the methods provided by the embodiments of the present application in the form of software, etc., and the embodiments of the present application do not limit this.

[0452] For the specific implementation of each embodiment shown in FIG. 11, reference can also be made to the above description of each embodiment, which will not be repeated here.

[0453] In addition, the present application also provides a computer program for implementing the operations and / or processes performed by the communication apparatus 10, the communication apparatus 20 or the communication apparatus 30 in the methods provided by the present application.

[0454] The present application also provides a readable storage medium having computer code stored therein, when the computer code is run on a computer, the computer code causes the computer to perform the operations and / or processes performed by the communication apparatus 10, the communication apparatus 20 or the communication apparatus 30 in the methods provided by the present application.

[0455] The present application also provides a computer program product including computer code or a computer program, when the computer code or the computer program is run on a computer, the operations and / or processes performed by the communication apparatus 10, the communication apparatus 20 or the communication apparatus 30 in the methods provided by the present application are performed.

[0456] The embodiments of the present application also provide a chip system including a processor for supporting a device to implement the functions involved in any of the above embodiments, for example, generating or processing the information involved in the above communication methods. In a possible design, the chip system further includes a memory, and the memory is used to save necessary program instructions and data of the device. The chip system can be composed of a chip, or can include a chip and other discrete devices.

[0457] In the above embodiments, the description of each embodiment has its own focus, and the parts not described in detail in a certain embodiment can refer to the relevant description of other embodiments.

[0458] It should be noted that, for the method embodiments described above, the steps of the methods can be performed in an order different than the order described, and / or the steps of the methods can be performed concurrently, to facilitate achieving the desired result. For example, describing the steps as occurring in a certain order does not imply that they must be performed in that order, and / or that the steps have dependency relationships as described. All such permutations are within the scope of the application.

[0459] In several embodiments provided in the present application, the coupling or direct coupling or communication connection between the display or discussion can be through some interface, device or unit indirectly coupled or communication connection, which can also be electrical, mechanical or other form of connection.

[0460] The above descriptions are merely specific embodiments of the present application, but the protection scope of the present application is not limited thereto, and any person skilled in the art can easily think of changes or replacements within the technical scope disclosed in the present application, which should be covered within the protection scope of the present application. Therefore, the protection scope of the present application should be subject to the protection scope of the claims.

Claims

1. A communication method, characterized in that, Applied to a terminal device, the method includes: Send a first request message to a first network device; the first request message is used to request the establishment of a multipath session, the multipath session includes a non-3GPP path, and the terminal device does not support non-access stratum NAS transmission under the non-3GPP path. The terminal device receives first information from the first network device; the first information instructs the terminal device to use a dual IP layer for data transmission in the non-3GPP path.

2. The method as described in claim 1, characterized in that, The method further includes: Receive third information from the first network device; the third information instructs the terminal device to establish a connection with the second network device through the non-3GPP path, and then send or update the IP address allocated to the terminal device by the access node of the non-3GPP path. Send or update the IP address assigned to the terminal device by the access node of the non-3GPP path to the first network device.

3. A communication method, characterized in that, Applied to a first network device, the method includes: A first request message is received from a terminal device. The first request message is used to request the establishment of a multipath session. The multipath session includes a non-3GPP path. The terminal device does not support NAS transmission under the non-3GPP path. Send a second message to the second network device; the second message instructs the second network device to use a dual IP layer for data transmission in the non-3GPP path.

4. The method as described in claim 3, characterized in that, The method further includes: Send first information to the terminal device; the first information instructs the terminal device to use a dual IP layer for data transmission in the non-3GPP path.

5. The method as described in claim 3 or 4, characterized in that, The method further includes: Send a second request message to a third network device; the second request message is used to request the establishment of a policy association for the multipath session; Receive a policy association establishment response message sent by the third network device; the policy association establishment response message includes control information of the multipath session; The first information and / or the second information are determined based on the control information.

6. The method according to any one of claims 3-5, characterized in that, The method further includes: Send third information to the terminal device; the third information instructs the terminal device to send or update the IP address assigned to the terminal device by the access node of the non-3GPP path after establishing a connection with the second network device through the non-3GPP path; and / or, Send a fourth message to the second network device; the fourth message instructs the second network device to send or update the IP address assigned to the terminal device by the access node of the non-3GPP path after establishing a connection with the terminal device through the non-3GPP path.

7. A communication method, characterized in that, Applied to a second network device, the method includes: The second information is received from the first network device; the second information instructs the second network device to use a dual IP layer for data transmission in a non-3GPP path.

8. The method as described in claim 7, characterized in that, The method further includes: The system receives fourth information from the first network device; the fourth information instructs the second network device to send or update the IP address allocated to the terminal device by the access node of the non-3GPP path after establishing a connection with the terminal device through the non-3GPP path. Send or update the IP address assigned to the terminal device by the access node of the non-3GPP path to the first network device.

9. The method according to any one of claims 3-8, characterized in that, The instruction to the second network device to use a dual IP layer for data transmission in a non-3GPP path includes: The packet inspection rule instructs the second network device to remove the packet header using any one of the following header combinations: IP+UDP+IP, IP+IP+UDP, or UDP+IP+IP, in the non-3GPP path; and / or, The forwarding action rule instructs the second network device to create a packet header using any one of the following combinations: IP+UDP+IP, IP+IP+UDP, or UDP+IP+IP, in the non-3GPP path.

10. The method according to any one of claims 1-9, characterized in that, The IP addresses in the dual IP layer include the IP addresses assigned to the terminal devices by the access nodes of the non-3GPP paths.

11. A communication method, characterized in that, Applied to a terminal device, the method includes: Send a first request message to a first network device; the first request message is used to request the establishment of a multipath session, the multipath session includes a non-3GPP path, and the terminal device does not support non-access stratum NAS transmission under the non-3GPP path. The system receives a first rule from the first network device, wherein the source IP address in the first rule includes a first IP address assigned to the terminal device by the access node of the non-3GPP path.

12. The method as described in claim 11, characterized in that, The method further includes: Receive third information from the first network device; the third information instructs the terminal device to establish a connection with the second network device through the non-3GPP path, and then send or update the IP address allocated to the terminal device by the access node of the non-3GPP path. Send or update the IP address assigned to the terminal device by the access node of the non-3GPP path to the first network device.

13. The method as described in claim 11 or 12, characterized in that, The method further includes: The system receives a second rule from the first network device, wherein the source IP address in the second rule includes a second IP address assigned to the terminal device by the access node of the non-3GPP path, and the first IP address is different from the second IP address.

14. A communication method, characterized in that, Applied to a first network device, the method includes: A first request message is received from a terminal device. The first request message is used to request the establishment of a multipath session. The multipath session includes a non-3GPP path. The terminal device does not support NAS transmission under the non-3GPP path. A third rule is sent to the second network device, wherein the terminal device IP address in the third rule includes the first IP address assigned to the terminal device by the access node of the non-3GPP path.

15. The method as described in claim 14, characterized in that, The method further includes: A first rule is sent to the terminal device, wherein the source IP address in the first rule includes the first IP address assigned to the terminal device by the access node of the non-3GPP path.

16. The method as described in claim 14 or 15, characterized in that, The method further includes: Send third information to the terminal device; the third information instructs the terminal device to send or update the IP address assigned to the terminal device by the access node of the non-3GPP path after establishing a connection with the second network device through the non-3GPP path; and / or, Send a fourth message to the second network device; the fourth message instructs the second network device to send or update the IP address assigned to the terminal device by the access node of the non-3GPP path after establishing a connection with the terminal device through the non-3GPP path.

17. The method according to any one of claims 14-16, characterized in that, The method further includes: Receive the first IP address sent by the terminal device; and / or, Receive the first IP address sent by the second network device.

18. The method according to any one of claims 14-17, characterized in that, The method further includes: Send a second rule to the terminal device, wherein the source IP address in the second rule includes a second IP address assigned to the terminal device by the access node of the non-3GPP path, and the first IP address is different from the second IP address; and / or, A fourth rule is sent to the second network device, wherein the terminal device IP address in the fourth rule includes a second IP address assigned to the terminal device by the access node of the non-3GPP path, and the first IP address is different from the second IP address.

19. The method according to any one of claims 14-18, characterized in that, The method further includes: Send a second request message to a third network device; the second request message is used to request the establishment of a policy association for the multipath session; Receive a policy association establishment response message sent by the third network device; the policy association establishment response message includes control information of the multipath session; The third rule and / or the first rule are determined based on the control information and the first IP address.

20. A communication method, characterized in that, Applied to a second network device, the method includes: The system receives a third rule sent by a first network device; the terminal device IP address in the third rule includes the first IP address assigned to the terminal device by the access node of the non-3GPP path.

21. The method as described in claim 20, characterized in that, The method further includes: The system receives fourth information from the first network device; the fourth information instructs the second network device to send or update the IP address allocated to the terminal device by the access node of the non-3GPP path after establishing a connection with the terminal device through the non-3GPP path. Send or update the IP address assigned to the terminal device by the access node of the non-3GPP path to the first network device.

22. The method as described in claim 20 or 21, characterized in that, The method further includes: The system receives a fourth rule from the first network device, wherein the terminal device IP address in the fourth rule includes a second IP address assigned to the terminal device by the access node of the non-3GPP path, and the first IP address is different from the second IP address.

23. A communication device, characterized in that, Includes modules or units for performing the method as described in any one of claims 1-22.

24. A communication device, characterized in that, The device includes a processor and an interface circuit, wherein the interface circuit is used to receive signals from other communication devices and transmit them to the processor or to send signals from the processor to other communication devices, and the processor is used to implement the method as described in any one of claims 1-22 through logic circuits or executing code instructions.

25. A computer-readable storage medium, characterized in that, The storage medium stores a computer program or instructions, which, when executed by a communication device, implement the method as described in any one of claims 1-22.

26. A computer program, characterized in that, The computer program includes instructions that, when executed by a communication device, implement the method as described in any one of claims 1-22.

27. A communication system, characterized in that, The communication system includes a terminal device, a first network device, and a second network device. The terminal device is used to perform the method as described in any one of claims 1, 2, 10, or 11-13. The first network device is used to perform the method as described in any one of claims 3-6, 9-10, or 14-19. The second network device is used to perform the method as described in any one of claims 7-10 or 20-22.

Images