Communication method and related apparatus

Abstract

The present application provides a communication method and a related apparatus. The method comprises: acquiring a rule related to a tunnel, wherein the rule comprises address information of a first application server and address information of a second application server; configuring a first user plane function network element and / or a second user plane function network element on the basis the rule to obtain the tunnel, wherein the tunnel is used for communication between the first application server and the second application server; and sending a response to an application network element, the response being used to indicate that the tunnel has been configured. The above technical solution allows for configuration of the tunnel between the first user plane function network element and the second user plane function network element. In this way, the first application server can process a data packet by means of the function of the second application server. For a user, a network side can provide richer functions, thereby improving user experience.

Description

Communication method and related device

[0001] This application claims priority to the Chinese patent application filed with the China Patent Office on February 8, 2024, with application number 202410179397.9 and titled “Communication Methods and Related Devices,” the entire contents of which are incorporated by reference into this application. Technical Field

[0002] The present application relates to the field of communication technology, and more specifically, to a communication method and related devices. Background Art

[0003] With the development of communications and the improvement of smart terminal capabilities, terminal devices support an increasing number of applications. Users are accessing applications stored in application servers with increasing frequency, resulting in higher and higher user expectations for the service experience when accessing applications. Therefore, how to improve the functionality of application servers is an urgent problem to be solved. Summary of the Invention

[0004] The present application provides a communication method and related devices, which can enable an application server to provide richer services.

[0005] In a first aspect, an embodiment of the present application provides a communication method, the method comprising: obtaining rules related to a tunnel, the rules comprising address information of a first application server and address information of a second application server; configuring a first user plane function network element and / or a second user plane function network element according to the rules to obtain the tunnel, wherein the first user plane function network element is a network element capable of accessing the first application server, the second user plane function network element is a network element capable of accessing the second application server, and the tunnel is used for communication between the first application server and the second application server; sending a response to the application network element, the response being used to indicate that the tunnel has been configured.

[0006] The above technical solution can configure a tunnel between the first user plane function network element and the second user plane function network element. In this way, the first application server can send data packets to the second application server through the tunnel. For example, the first application server can use the functions of the second application server to process data packets. For example, some processing tasks can be shared with the first application server, or the first application server can be assisted in processing some data that cannot be processed by the first application server. For another example, some services require the first application server and the second application server to cooperate with each other to provide services. In this way, for users, the network side can provide richer functions, thereby improving the user experience.

[0007] In combination with the first aspect, in some possible implementations of the first aspect, the first user plane function network element and the second user plane function network element are network elements in a first network, and the first application server and the second application server do not belong to the first network.

[0008] In combination with the first aspect, in some possible implementations of the first aspect, before the first user plane function network element and / or the second user plane function network element are configured to obtain the tunnel, the method also includes: selecting the first user plane function network element and the second user plane function network element for the terminal, the first user plane function network element and the second user plane function network element are used to transmit data of the terminal's session, the first application server and the second application server provide the terminal with application services related to the session, and the communication between the first application server and the second application server is related to the application service.

[0009] The above technical solution can bind the tunnel to the terminal, so that a dedicated tunnel can be allocated for the service of the terminal. In this way, the first application server and the second application server can use this dedicated tunnel to provide services to the terminal, thereby improving the user experience of the terminal user.

[0010] In combination with the first aspect, in some possible implementations of the first aspect, the first user plane function network element is selected based on the address information of the first application server; the second user plane function network element is selected based on the address information of the second application server.

[0011] In combination with the first aspect, in some possible implementations of the first aspect, the rule also includes: a data network access identifier DNAI, the first user plane function network element is selected based on the DNAI; the second user plane function network element is selected based on the address information of the second application server.

[0012] In combination with the first aspect, in some possible implementations of the first aspect, the first user plane function network element and / or the second user plane function network element are configured according to the rule to obtain the tunnel, including: configuring the first user plane function network element by sending a first packet detection rule to the first user plane function network element to obtain the tunnel, the first packet detection rule including: at least one of the address information of the first application server or the address information of the second application server; and / or, configuring the second user plane function network element by sending a second packet detection rule to the second user plane function network element to obtain the tunnel, the second packet detection rule including: at least one of the address information of the first application server or the address information of the second application server.

[0013] In combination with the first aspect, in some possible implementations of the first aspect, the method also includes: sending a third packet detection rule to a third user plane functional network element, the third user plane functional network element being used to forward and / or divert data of the session, the third packet detection rule being used to detect data packets from the first application server and / or the second application server, the third packet detection rule including at least one of the address information of the first application server or the address information of the second application server.

[0014] In combination with the first aspect, in some possible implementations of the first aspect, the first user plane function network element and / or the second user plane function network element are configured according to the rule to obtain the tunnel, and also includes: sending a fourth packet detection rule to the second user plane function network element, the fourth packet detection rule being used to detect data packets from the second application server, the fourth packet detection rule including a first address, and the first address being allocated by the second user plane function network element to the terminal.

[0015] Based on the above technical solution, the second application server can use the first address to send data to the first application server. In this way, the second application server does not need to allocate a fixed port number to the terminal.

[0016] In combination with the first aspect, in some possible implementations of the first aspect, it also includes: sending a first indication message to the second user plane function network element, the first indication message being used to instruct the second user plane function network element to allocate an address; obtaining the first address, which is allocated by the second user plane function network element to the terminal based on the first indication message.

[0017] Based on the allocated first address, the allocated tunnel can be bound to the terminal. In this way, some information previously configured by the terminal, such as QoS rules, etc., can be reused, and control can be performed at the terminal level.

[0018] In combination with the first aspect, in some possible implementations of the first aspect, the configuration of the first user plane function network element and / or the second user plane function network element to obtain the tunnel also includes: configuring the first user plane function network element by sending second indication information to the first user plane function network element, the second indication information being used to indicate that the source address of the data packet from the first application server is replaced with the first address.

[0019] In combination with the first aspect, in some possible implementations of the first aspect, the method also includes: sending the fifth packet detection rule and the sixth packet detection rule to the fourth user plane functional network element, the fourth user plane functional network element is used to forward and / or divert data of the session, the fifth packet detection rule is used to detect data packets from the first application server, the fifth packet detection rule includes the first address, and the sixth packet detection rule is used to detect data packets from the second application server, and the sixth packet detection rule includes the first address; sending third indication information to the fourth user plane functional network element, the third indication information is used to instruct the fourth user plane functional network element to send a data packet with the source address being the first address to the second user plane functional network element, and to send a data packet with the destination address being the first address to the first user plane functional network element.

[0020] In combination with the first aspect, in some possible implementations of the first aspect, the configuration of the first user plane function network element and / or the second user plane function network element to obtain the tunnel also includes: configuring the second user plane function network element by sending fourth indication information to the second user plane function network element, and the fourth indication information is used to indicate that the source address of the data packet from the first application server is replaced with the first address.

[0021] In combination with the first aspect, in some possible implementations of the first aspect, the method also includes: sending a seventh packet detection rule and an eighth packet detection rule to the fifth user plane functional network element, the fifth user plane functional network element is used to forward and / or divert data of the session, the seventh packet detection rule is used to detect data packets from the first application server, the seventh packet detection rule includes at least one of the address information of the first application server or the address information of the second application server, the eighth packet detection rule is used to detect data packets from the second application server, and the eighth packet detection rule includes the first address; sending sixth indication information to the fifth user plane functional network element, the sixth indication information instructing the fifth user plane functional network element to send a data packet with the source address being the first address to the second user plane functional network element, and to send a data packet with the destination address being the first address to the first user plane functional network element.

[0022] In combination with the first aspect, in some possible implementations of the first aspect, the tunnel includes: a first tunnel, used for communication from the first application server to the second application server, a first port number is used to identify the unique port of the first application server for communication using the first tunnel, and a second port number is used to identify the unique port of the second application server for communication using the first tunnel; and / or, a second tunnel, used for communication from the second application server to the first application server, a third port number is used to identify the unique port of the first application server for communication using the second tunnel, and a fourth port number is used to identify the unique port of the second application server for communication using the second tunnel.

[0023] The above technical solution uses a unique port number to identify the port of the application server using tunnel communication, so that the determined tunnel can be bound to the port number, which facilitates the configuration of detection rules for detecting packets from the application server.

[0024] In combination with the first aspect, in some possible implementations of the first aspect, the address information of the first application server is used to indicate any one or more of the following: the Internet Protocol IP address of the first application server, the first port number, or the third port number; the address information of the second application server is used to indicate any one or more of the following: the IP address of the second application server, the second port number, or the fourth port number.

[0025] In a second aspect, an embodiment of the present application provides a communication method, comprising: sending a first request, the first request including address information of a first application server and address information of a second application server; receiving a response to the first request, the response being used to indicate that a tunnel between the first user plane function network element and the second user plane function network element has been configured, wherein the first user plane function network element is a network element capable of accessing the first application server, the second user plane function network element is a network element capable of accessing the second application server, and the tunnel is used for communication between the first application server and the second application server.

[0026] The above technical solution can configure a tunnel between the first user plane function network element and the second user plane function network element. In this way, the first application server can send data packets to the second application server through the tunnel. For example, the first application server can use the functions of the second application server to process data packets. For example, some processing tasks can be shared with the first application server, or the first application server can be assisted in processing some data that cannot be processed by the first application server. For another example, some services require the first application server and the second application server to cooperate with each other to provide services. In this way, for users, the network side can provide richer functions, thereby improving the user experience.

[0027] In combination with the second aspect, in some possible implementations of the second aspect, the first user plane function network element and the second user plane function network element are network elements in a first network, and the first application server and the second application server do not belong to the first network.

[0028] In combination with the second aspect, in some possible implementations of the second aspect, the tunnel includes: a first tunnel, used for communication from the first application server to the second application server, the first port number is used to identify the unique port of the first application server for communication using the first tunnel, and the second port number is used to identify the unique port of the second application server for communication using the first tunnel; and / or, a second tunnel, used for communication from the second application server to the first application server, the third port number is used to identify the unique port of the first application server for communication using the second tunnel, and the fourth port number is used to identify the unique port of the second application server for communication using the second tunnel.

[0029] The above technical solution uses a unique port number to identify the port of the application server using tunnel communication, so that the determined tunnel can be bound to the port number, which facilitates the configuration of detection rules for detecting packets from the application server.

[0030] In combination with the second aspect, in some possible implementations of the second aspect, the address information of the first application server is used to indicate any one or more of the following: the Internet Protocol IP address of the first application server, the first port number, or the third port number; the address information of the second application server is used to indicate any one or more of the following: the IP address of the second application server, the second port number, or the fourth port number.

[0031] In combination with the second aspect, in some possible implementations of the second aspect, the first request also includes: identity information of the terminal, the first application server and the second application server provide application services for the terminal, and the communication between the first application server and the second application server is related to the application service.

[0032] The above technical solution can bind the tunnel to the terminal, so that a dedicated tunnel can be allocated for the service of the terminal. In this way, the first application server and the second application server can use this dedicated tunnel to provide services to the terminal, thereby improving the user experience of the terminal user.

[0033] In combination with the second aspect, in some possible implementations of the second aspect, before sending the first request, the method also includes: determining a policy control network element corresponding to the terminal; and sending the first request includes: sending the first request to the policy control network element.

[0034] In combination with the second aspect, in some possible implementations of the second aspect, the first request further includes: a data network access identifier DNAI, where the DNAI is used to indicate a region where the first application server is located.

[0035] In combination with the second aspect, in some possible implementations of the second aspect, the first request is used to instruct establishment of the tunnel, or to reuse an existing tunnel as the tunnel.

[0036] In combination with the second aspect, in some possible implementations of the second aspect, the first request further includes first indication information, where the first indication information is used to indicate establishing the tunnel, or to reuse an existing tunnel as the tunnel.

[0037] In combination with the second aspect, in some possible implementations of the second aspect, the first request further indicates an address of an allocated terminal, and the address of the terminal is used for the first user plane function network element or the second user plane function network element to perform the communication.

[0038] Based on the assigned first address, the assigned tunnel can be bound to the terminal. The second application server can use the first address to send data to the first application server. This eliminates the need for the second application server to allocate a fixed port number for the terminal. Furthermore, previously configured information for the terminal, such as QoS rules, can be reused, enabling control at the terminal level.

[0039] In combination with the second aspect, in some possible implementations of the second aspect, the first request also includes second indication information, and the second indication information is used to indicate any one or more of the following: sending the address information of the first application server and the address information of the second application server to the policy control network element corresponding to the terminal; sending the identity information of the terminal to the policy control network element corresponding to the terminal; establishing or obtaining a mapping relationship between the identity information of the terminal and the address information of the first application server.

[0040] In a third aspect, an embodiment of the present application provides a communication method, which includes: obtaining a first packet detection rule; obtaining a first data packet; and processing the first data packet when the first data packet matches the first packet detection rule.

[0041] In combination with the third aspect, in some possible implementations of the third aspect, before processing the first data packet, the method also includes: receiving first indication information, the first indication being used to indicate that the source address of the data packet from the first application server is replaced with the first address; and when the first data packet matches the first packet detection rule, processing the first data packet, including: using the address to replace the source address of the first data packet to obtain a second data packet; and sending the second data packet to the destination network element.

[0042] In a fourth aspect, an embodiment of the present application provides a communication system, which includes: a first network element, used to obtain rules related to a tunnel, the rules including address information of a first application server and address information of a second application server; the first network element, further used to configure a first user plane function network element and / or a second user plane function network element according to the rules to obtain the tunnel, wherein the first user plane function network element is a network element capable of accessing the first application server, the second user plane function network element is a network element capable of accessing the second application server, and the tunnel is used for communication between the first application server and the second application server; the first network element, further used to send a response to the application network element, the response being used to indicate that the tunnel has been configured; the application network element, used to receive the response; the first user plane function network element and / or the second user plane function network element, configured according to the first network element, using the forwarding tunnel to send data packets.

[0043] In combination with the fourth aspect, in some possible implementations of the fourth aspect, the first user plane function network element and the second user plane function network element are network elements in a first network, and the first application server and the second application server do not belong to the first network.

[0044] In combination with the fourth aspect, in some possible implementations of the fourth aspect, the first network element is also used to select the first user plane function network element and the second user plane function network element for the terminal, the first user plane function network element and the second user plane function network element are used to transmit data of the terminal's session, the first application server and the second application server provide the terminal with application services related to the session, and the communication between the first application server and the second application server is related to the application service.

[0045] In combination with the fourth aspect, in some possible implementations of the fourth aspect, the first network element is further used to configure the first user plane function network element by sending a first packet detection rule to the first user plane function network element to obtain the tunnel, and the first packet detection rule includes: at least one of the address information of the first application server or the address information of the second application server; and / or, the first network element is further used to configure the second user plane function network element by sending a second packet detection rule to the second user plane function network element to obtain the tunnel, and the second packet detection rule includes: the address information of the first application server or the address information of the second application server. At least one of the address information; the first user plane functional network element is further used to match the first data packet based on the first packet detection rule, and when the first data packet matches the first detection rule, the first data packet is processed, and the first data packet is the data packet received by the first user plane functional network element, and / or the second user plane functional network element is further used to match the second data packet based on the second packet detection rule, and when the second data packet matches the second packet detection rule, the second data packet is processed, and the second data packet is the data packet received by the second user plane functional network element.

[0046] In combination with the fourth aspect, in some possible implementations of the fourth aspect, the first network element is also used to send a third packet detection rule to a third user plane functional network element, and the third user plane functional network element is used to forward and / or divert data of the session. The third packet detection rule is used to detect data packets from the first application server and / or the second application server, and the third packet detection rule includes at least one of the address information of the first application server or the address information of the second application server.

[0047] In combination with the fourth aspect, in some possible implementations of the fourth aspect, the first network element is further used to send a fourth packet detection rule to the second user plane function network element, and the fourth packet detection rule is used to detect the data packet from the second application server, and the fourth packet detection rule includes a first address, which is allocated by the second user plane function network element to the terminal; the first network element is also used to configure the first user plane function network element by sending second indication information to the first user plane function network element, or to configure the second user plane function network element by sending fourth indication information to the second user plane function network element, the second indication information is used to indicate that the source address of the data packet from the first application server is replaced with the first address, and the fourth indication information is used to indicate that the source address of the data packet from the first application server is replaced with the first address.

[0048] In combination with the fourth aspect, in some possible implementations of the fourth aspect, the first user plane functional network element is further used to match the first data packet based on the first packet detection rule, and when the first data packet matches the first detection rule, the source address of the first data packet is replaced by the first address, and the first data packet is the data packet received by the first user plane functional network element; or, the second user plane functional network element is further used to match the second data packet based on the second packet detection rule, and when the second data packet matches the second detection rule, the source address of the second data packet is replaced by the first address, and the second data packet is the data packet received by the second user plane functional network element; the second user plane functional network element is further used to match the third data packet based on the fourth packet detection rule, and when the third data packet matches the fourth packet detection rule, the third data packet is processed, and the third data packet is the data packet received by the second user plane network element from the second application server.

[0049] In combination with the fourth aspect, in some possible implementations of the fourth aspect, the application network element is further used to send a first request, where the first request includes address information of the first application server and address information of the second application server.

[0050] In combination with the fourth aspect, in some possible implementations of the fourth aspect, the tunnel includes: a first tunnel, used for communication from the first application server to the second application server, the first port number is used to identify the unique port of the first application server for communication using the first tunnel, and the second port number is used to identify the unique port of the second application server for communication using the first tunnel; and / or, a second tunnel, used for communication from the second application server to the first application server, the third port number is used to identify the unique port of the first application server for communication using the second tunnel, and the fourth port number is used to identify the unique port of the second application server for communication using the second tunnel.

[0051] In combination with the fourth aspect, in some possible implementations of the fourth aspect, the address information of the first application server is used to indicate any one or more of the following: the Internet Protocol IP address of the first application server, the first port number, or the third port number; the address information of the second application server is used to indicate any one or more of the following: the IP address of the second application server, the second port number, or the fourth port number.

[0052] In combination with the fourth aspect, in some possible implementations of the fourth aspect, the first request also includes: identity information of the terminal, the first application server and the second application server provide application services for the terminal, and the communication between the first application server and the second application server is related to the application service.

[0053] In combination with the fourth aspect, in some possible implementations of the fourth aspect, the application network element is further used to determine a policy control network element corresponding to the terminal; the application network element is further used to send the first request to the policy control network element.

[0054] In combination with the fourth aspect, in some possible implementations of the fourth aspect, the first request is also used to indicate any one or more of the following: establishing the tunnel, reusing the existing tunnel as the tunnel, allocating the address of the terminal, and the address of the terminal is used for the first user plane function network element or the second user plane function network element to perform the communication; sending the address information of the first application server and the address information of the second application server to the policy control network element corresponding to the terminal; sending the identity information of the terminal to the policy control network element corresponding to the terminal; or establishing or obtaining a mapping relationship between the identity information of the terminal and the address information of the first application server.

[0055] In a fifth aspect, an embodiment of the present application provides a communication method, which includes: receiving a first request, the first request including address information of a first application server and address information of a second application server; sending a second request to a control policy network element, the second request including address information of the first application server and address information of the second application server.

[0056] In combination with the fifth aspect, in some possible implementations of the fifth aspect, the method also includes: obtaining first identity information of the first terminal; determining second identity information of the terminal based on the first identity information of the terminal; and sending the second identity information of the terminal to the control policy network element.

[0057] In combination with the fifth aspect, in some possible implementations of the fifth aspect, the method further includes: establishing a mapping relationship between the first identity information of the terminal and the address information of the first application server.

[0058] In combination with the fifth aspect, in some possible implementations of the fifth aspect, the method also includes: obtaining first indication information, the first indication information being used to indicate establishing a mapping relationship between the identity information of the terminal and the address information of the first application server, the first indication information being also used to indicate sending the address information of the first application server, the address information of the second application server and the identity information of the terminal to the control policy network element.

[0059] In combination with the fifth aspect, in some possible implementations of the fifth aspect, obtaining the first identity information of the terminal includes: determining the first identity information of the terminal based on a mapping relationship between the first identity information of the terminal and the address information of the first application server, and the address information of the first application server.

[0060] In combination with the fifth aspect, in some possible implementations of the fifth aspect, the method also includes: obtaining second indication information, the second indication information being used to indicate obtaining a mapping relationship between the first identity information of the terminal and the address information of the first application server, and the third indication information being further used to indicate sending the address information of the first application server, the address information of the second application server and the identity information of the terminal to the control policy network element.

[0061] In combination with the fifth aspect, in some possible implementations of the fifth aspect, before sending the address information of the first application server and the address information of the second application server to the control policy network element, the method also includes: determining the control policy network element based on the first identity information or the second identity information of the terminal.

[0062] In combination with the fifth aspect, in some possible implementations of the fifth aspect, the second request is also used to instruct the establishment of the tunnel, or to reuse an existing tunnel as the tunnel.

[0063] In combination with the fifth aspect, in some possible implementations of the fifth aspect, the second request also includes first indication information, and the first indication information is used to indicate the establishment of the tunnel, or to reuse an existing tunnel as the tunnel.

[0064] With reference to the fifth aspect, in some possible implementations of the fifth aspect, the second request is further used to indicate an address of an allocated terminal, where the address of the terminal is used for the first user plane function network element or the second user plane function network element to perform the communication. Alternatively, the second request further includes a second indication, where the second indication is used to indicate an address of an allocated terminal, where the address of the terminal is used for the first user plane function network element or the second user plane function network element to perform the communication.

[0065] In a sixth aspect, an embodiment of the present application provides a communication method, which includes: receiving a second request, the second request including address information of a first application server and address information of a second application server; sending tunnel-related rules to a session management network element, the rules including address information of the first application server and address information of the second application server.

[0066] In combination with the sixth aspect, in some possible implementations of the sixth aspect, the method also includes: obtaining the second identity information of the terminal; determining the third identity information of the terminal based on the second identity information of the terminal; and sending the third identity information of the terminal to the session management network element.

[0067] In combination with the sixth aspect, in some possible implementations of the sixth aspect, before sending the address information of the first application server and the address information of the second application server to the session management network element, the method also includes: determining the session management network element based on the second identity information of the terminal.

[0068] In combination with the sixth aspect, in some possible implementations of the sixth aspect, before sending the address information of the first application server and the address information of the second application server to the session management network element, the method also includes: determining the session management network element based on the address information of the first application server.

[0069] In combination with the sixth aspect, in some possible implementations of the sixth aspect, the method further includes: sending first indication information to the session management network element, where the first indication information is used to indicate the establishment of the tunnel, or to reuse the existing tunnel as the tunnel.

[0070] In combination with the sixth aspect, in some possible implementations of the sixth aspect, the method also includes: sending second indication information to the second user plane function network element, the second indication information being used to indicate the address of the allocated terminal, and the address of the terminal being used for the first user plane function network element or the second user plane function network element to perform the communication.

[0071] Optionally, the first identity information of the terminal includes: any one or more of the terminal's IP address, GPSI, or SUPI. The second identity information of the terminal includes: the terminal's IP address and / or SUPI. The third identity information of the terminal includes: any one or more of the terminal's IP address, SUPI, or PDU session ID.

[0072] In a seventh aspect, a communication device is provided, which is configured to execute the methods provided in aspects 1 to 3 above. Specifically, the device may include units and / or modules, such as a processing unit and / or a communication unit, configured to execute the methods provided in any one of the implementations of aspects 1 to 3, the fifth aspect, and the sixth aspect.

[0073] In one implementation, the apparatus is a terminal device. When the apparatus is a terminal device, the communication unit may be a transceiver or an input / output interface; and the processing unit may be at least one processor. Optionally, the transceiver may be a transceiver circuit. Optionally, the input / output interface may be an input / output circuit.

[0074] In another implementation, the device is a chip, chip system, or circuit used in a terminal device. When the device is a chip, chip system, or circuit used in a terminal device, the communication unit may be an input / output interface, interface circuit, output circuit, input circuit, pin, or related circuit on the chip, chip system, or circuit; and the processing unit may be at least one processor, processing circuit, or logic circuit.

[0075] In an eighth aspect, a communication device is provided, comprising: a memory for storing programs; and at least one processor for executing computer programs or instructions stored in the memory to execute any one of the above-mentioned implementation methods of the first to third aspects, the fifth aspect, and the sixth aspect.

[0076] In one implementation, the apparatus is a terminal device.

[0077] In another implementation, the apparatus is a chip, a chip system, or a circuit used in a terminal device.

[0078] In a ninth aspect, the present application provides a processor for executing the methods provided in the above aspects.

[0079] For the operations such as sending and acquiring / receiving involved in the processor, unless otherwise specified, or if they do not conflict with their actual functions or internal logic in the relevant descriptions, they can be understood as processor output, reception, input and other operations, and can also be understood as sending and receiving operations performed by the radio frequency circuit and antenna. This application does not limit this.

[0080] In the tenth aspect, a computer-readable storage medium is provided, which stores program code for execution by a device, and the program code includes a method provided by any one of the above-mentioned implementation methods of the first to third aspects, the fifth aspect, and the sixth aspect.

[0081] In the eleventh aspect, a computer program product comprising instructions is provided. When the computer program product is run on a computer, the computer is enabled to execute the method provided by any one of the above-mentioned implementations of the first to third aspects, the fifth aspect, and the sixth aspect.

[0082] In the twelfth aspect, a chip is provided, which includes a processor and a communication interface. The processor reads instructions stored in the memory through the communication interface and executes the method provided by any one of the above-mentioned implementation methods of the first to third aspects, the fifth aspect, and the sixth aspect.

[0083] Optionally, as an implementation method, the chip also includes a memory, in which a computer program or instruction is stored, and the processor is used to execute the computer program or instruction stored on the memory. When the computer program or instruction is executed, the processor is used to execute the method provided in any one of the above-mentioned implementation methods of the first to third aspects.

[0084] In a thirteenth aspect, a communication system is provided, comprising a network element that implements the functions of the first to third, fifth and sixth aspects described above. BRIEF DESCRIPTION OF THE DRAWINGS

[0085] FIG1 is a schematic diagram of the network architecture provided by this application.

[0086] FIG2 is a schematic diagram of another network architecture provided in an embodiment of the present application.

[0087] FIG3 is a schematic diagram of another network architecture provided in an embodiment of the present application.

[0088] FIG4 is a schematic diagram of another network architecture provided in an embodiment of the present application.

[0089] FIG5 is a schematic diagram of another network architecture provided according to an embodiment of the present application.

[0090] FIG6 is a schematic flowchart of a communication method provided according to an embodiment of the present application.

[0091] FIG7 is a schematic flowchart of another communication method provided according to an embodiment of the present application.

[0092] FIG8 is a schematic flowchart of another communication method provided according to an embodiment of the present application.

[0093] FIG9 is a schematic flowchart of another communication method provided according to an embodiment of the present application.

[0094] FIG10 is a schematic flowchart of another communication method provided according to an embodiment of the present application.

[0095] FIG11 is a schematic flowchart of another communication method provided according to an embodiment of the present application.

[0096] FIG12 is a schematic flowchart of another communication method provided according to an embodiment of the present application.

[0097] FIG13 is a schematic flowchart of another communication method provided according to an embodiment of the present application.

[0098] FIG14 is a schematic block diagram of a communication device provided in an embodiment of the present application.

[0099] FIG15 is a schematic diagram of another communication device provided in an embodiment of the present application.

[0100] FIG16 is a schematic diagram of a chip system provided in an embodiment of the present application. DETAILED DESCRIPTION

[0101] The technical solution in this application will be described below with reference to the accompanying drawings.

[0102] The technical solutions provided in this application can be applied to various communication systems, such as new radio (NR) systems, long term evolution (LTE) systems, LTE frequency division duplex (FDD) systems, LTE time division duplex (TDD) systems, etc. The technical solutions provided in this application can also be applied to device-to-device (D2D) communication, vehicle-to-everything (V2X) communication, machine-to-machine (M2M) communication, machine type communication (MTC), and Internet of Things (IoT) communication systems or other communication systems.

[0103] In a communication system, the part operated by an operator may be referred to as a public land mobile network (PLMN), or an operator network, etc. A PLMN is a network established and operated by the government or an operator approved by it for the purpose of providing land mobile communication services to the public. It is primarily a public network where mobile network operators (MNOs) provide mobile broadband access services to users. The PLMN described in the embodiments of the present application may specifically be a network that complies with the requirements of the 3GPP standard, referred to as a 3GPP network. 3GPP networks generally include but are not limited to 5G networks, fourth-generation mobile communication (4G) networks, and other future communication systems.

[0104] For the convenience of description, the embodiments of the present application will be described using PLMN or 5G network as an example.

[0105] Figure 1 is a schematic diagram of a network architecture 100 provided in this application, taking the 5G network architecture based on the Service-Based Architecture (SBA) in a non-roaming scenario, as defined in the 3GPP standardization process, as an example. As shown in the figure, this network architecture can be comprised of three components: the terminal device component, the DN, and the operator network PLMN component. The following briefly describes the functions of the network elements in each component.

[0106] The terminal device part may include a terminal device 110, which may also be referred to as user equipment (UE). The terminal device 110 in this application is a device with wireless transceiver functions, which can communicate with one or more core network (CN) devices via an access network device (or also referred to as an access device) in a radio access network (RAN) 140. The terminal device 110 may also be referred to as an access terminal, terminal, user unit, user station, mobile station, mobile station, remote station, remote terminal, mobile device, user terminal, user agent or user device, etc. The terminal device 110 may be deployed on land, including indoors or outdoors, handheld or vehicle-mounted; it may also be deployed on water (such as ships, etc.); it may also be deployed in the air (such as airplanes, balloons and satellites, etc.). The terminal device 110 may be a cellular phone, a cordless phone, a Session Initiation Protocol (SIP) phone, a smart phone, a mobile phone, a wireless local loop (WLL) station, a personal digital assistant (PDA), etc. Alternatively, the terminal device 110 may be a handheld device with wireless communication capabilities, a computing device, or other device connected to a wireless modem, an in-vehicle device, a wearable device, an unmanned aerial vehicle (UAV), or a terminal in the Internet of Things (IoT), the Internet of Vehicles (IoV), any terminal in a 5G network or future networks, a relay user device, or a terminal in a future evolving communication network, etc. The relay user device may be, for example, a 5G residential gateway (RG). For example, the terminal device 110 can be a virtual reality (VR) terminal, an augmented reality (AR) terminal, a wireless terminal in industrial control, a wireless terminal in self-driving, a wireless terminal in remote medical, a wireless terminal in smart grid, a wireless terminal in transportation safety, a wireless terminal in smart city, a wireless terminal in smart home, etc. The terminal device here refers to a 3GPP terminal. The embodiments of the present application do not limit the type or category of the terminal device. For ease of explanation, this application will be described later using UE as an example to refer to the terminal device.

[0107] The operator network PLMN part may include but is not limited to the (radio) access network (R)AN) 120 and the core network (CN) part.

[0108] (R)AN 120 can be considered a subnetwork of the operator network, serving as the implementation system between service nodes in the operator network and terminal device 110. To access the operator network, terminal device 110 first passes through (R)AN 120, which then connects to service nodes in the operator network. The access network device (RAN device) in the embodiment of the present application is a device that provides wireless communication functions for the terminal device 110, and can also be called a network device. The RAN device includes but is not limited to: the next generation node base station (gNB) in the 5G system, the evolved node B (eNB) in the long term evolution (LTE), the radio network controller (RNC), the node B (NB), the base station controller (BSC), the base transceiver station (BTS), the home base station (for example, home evolved node B, or home node B, HNB), the base band unit (BBU), the transmission point (TRP), the transmitting point (TP), the small base station device (pico), the mobile switching center, or the network device in the future network. In systems using different wireless access technologies, the name of the device with the access network device function may be different. For the convenience of description, in all embodiments of the present application, the above-mentioned device that provides wireless communication functions for the terminal device 110 is collectively referred to as the access network device or simply referred to as RAN or AN. It should be understood that this document does not limit the specific type of access network equipment.

[0109] In some deployments, the (R)AN 120 may include a centralized unit (CU) and a distributed unit (DU). The CU implements some of the gNB's functions, while the DU implements some of the gNB's functions. For example, the CU is responsible for processing non-real-time protocols and services, and implementing the functions of the radio resource control (RRC) and packet data convergence protocol (PDCP) layers. The DU is responsible for processing physical layer protocols and real-time services, and implementing the functions of the radio link control (RLC), media access control (MAC), and physical (PHY) layers. It is understood that the (R)AN 120 may be a device including one or more of a CU node and a DU node. In addition, the CU may be classified as a network device in the radio access network (RAN) or a network device in the core network (CN), but this application does not limit this.

[0110] For example, the radio access network may also be an open radio access network (O-RAN) architecture. In the ORAN system, the CU may also be referred to as an O-CU (open CU), the DU may also be referred to as an O-DU, the CU-CP may also be referred to as an O-CU-CP, the CU-UP may also be referred to as an O-CU-UP, and the RU may also be referred to as an O-RU. Any of the CU (or CU-CP, CU-UP), DU, and RU in this application may be implemented by a software module, a hardware module, or a combination of a software module and a hardware module.

[0111] The CN part may include but is not limited to the following NFs: user plane function (UPF) 130, network exposure function (NEF) 131, network function repository function (NRF) 132, policy control function (PCF) 133, unified data management function (UDM) 134, unified data repository function (UDR) 135, network data analytics function (NWDAF) 136, authentication server function (AUSF) 137, access and mobility management function (AMF) 138, and session management function (SMF) 139.

[0112] The data network DN 140, which may also be referred to as a packet data network (PDN), is typically a network located outside the operator's network, such as a third-party network. Of course, in some implementations, the data network (DN) may also be deployed by the operator, that is, the DN is part of the PLMN. This application does not impose any restrictions on whether the DN belongs to the PLMN. The operator network PLMN can access multiple data networks DN 140, and a variety of services can be deployed on the data network DN 140, which can provide data and / or voice services to the terminal device 110. For example, the data network DN 140 may be a private network of a smart factory, and the sensors installed in the workshop of the smart factory may be the terminal devices 110. The control server of the sensors is deployed in the data network DN 140, and the control server can provide services for the sensors. The sensors can communicate with the control server, obtain instructions from the control server, and transmit the collected sensor data to the control server according to the instructions. For another example, data network DN 140 can be a company's internal office network. The company's employees' mobile phones or computers can be terminal devices 110, which can access information, data resources, and the like on the company's internal office network. Terminal device 110 can establish a connection with the carrier network via an interface (e.g., N1) provided by the carrier network and use data and / or voice services provided by the carrier network. Terminal device 110 can also access data network DN 140 through the carrier network and use carrier services deployed on data network DN 140 and / or services provided by third parties.

[0113] The following is a brief description of the NF functions included in the network architecture 100.

[0114] 1. UPF 130 is a gateway provided by the operator, serving as the gateway for communication between the operator network and the data network DN 140. UPF network function 130 includes user plane-related functions such as packet routing and transmission, packet inspection, service usage reporting, quality of service (QoS) processing, legal monitoring, uplink packet inspection, and downlink packet storage.

[0115] 2. NEF 131 is a control plane function provided by the operator. It mainly enables third parties to use the services provided by the network, supports the network to open its capabilities, event and data analysis, provides PLMN security configuration information from external applications, and converts interactive information inside and outside the PLMN. It provides an API interface open to the operator network and provides interaction between external servers and internal operator networks.

[0116] 3. NRF 132 is a control plane function provided by the operator. It is used to maintain real-time information about network functions and services in the network. For example, it supports network service discovery, maintains the services supported by the NF profile of the NF instance, supports service discovery of the service communication proxy (SCP), maintains the SCP profile of the SCP instance, sends notifications about newly registered, deregistered, and updated NFs and SCPs, and maintains the health status of NF and SCP operations.

[0117] In this application, NRF can provide the certificate management network element with the number of available network elements corresponding to different network element types in a certain area through network service discovery or network service subscription process. The functions of NRF will be explained with specific examples below, which will not be repeated here.

[0118] 4. PCF 133 is the control plane function provided by the operator. It supports a unified policy framework to govern network behavior, provide policy rules to other control functions, and provide contract information related to policy decisions.

[0119] 5. The UDM 134 is a control plane function provided by the operator, responsible for storing information such as the subscriber permanent identifier (SUPI), the generic public subscription identifier (GPSI), and credentials of subscribers in the operator network. The SUPI is first encrypted during transmission, and the encrypted SUPI is called a hidden subscriber subscription identifier (SUCI). The information stored by the UDM network function 134 can be used for authentication and authorization of the terminal device 110 to access the operator network. The subscribers of the above-mentioned operator network can specifically be users who use services provided by the operator network, such as users who use China Telecom's mobile phone SIM cards or users who use China Mobile's mobile phone SIM cards. The credentials of the above-mentioned subscribers can be a small file storing long-term keys stored in the mobile phone SIM card or information related to mobile phone SIM card encryption, which is used for authentication and / or authorization. It should be noted that permanent identifiers, credentials, security contexts, authentication data (cookies), and tokens are equivalent to verification / authentication and authorization-related information. In the embodiments of this application, no distinction or restriction is made for the sake of convenience of description.

[0120] 6. UDR 135 is a control plane function provided by the operator. It provides the UDM with the functions of storing and retrieving subscription data, the PCF with the functions of storing and retrieving policy data, and the user's NF group ID information.

[0121] 7. NWDAF 136 is a control plane function provided by the operator. Its main function is to collect data from NFs, external application functions (AFs), and OAM devices, and provide NWDAF service registration, data exposure, and data analysis to NFs and AFs.

[0122] 8. The AUSF 137 is a control plane function provided by the operator and is typically used for level 1 authentication, i.e., authentication between the terminal device 110 (subscriber) and the operator's network. After receiving an authentication request initiated by a subscriber, the AUSF network function 137 may authenticate and / or authorize the subscriber using the authentication information and / or authorization information stored in the UDM network function 134, or generate authentication and / or authorization information for the subscriber via the UDM network function 134. The AUSF network function 137 may also provide feedback on the authentication and / or authorization information to the subscriber.

[0123] 9. AMF 138 is a control plane network function provided by the operator network, responsible for access control and mobility management of the terminal device 110 accessing the operator network, such as mobility status management, allocation of user temporary identity, authentication and authorization of users, etc.

[0124] The AMF 138 is used to establish a NAS connection with the UE and has the same 5G NAS security context as the UE. The 5G NAS security context includes the KAMF, key identification information with the same NAS layer key, UE security capabilities, and uplink and downlink NAS COUNT values. NAS layer keys include NAS encryption keys and NAS integrity protection keys, which are used for confidentiality protection and integrity protection of NAS messages, respectively.

[0125] 10. SMF 139 is a control plane network function provided by the operator network and is responsible for managing PDU sessions for terminal device 110. A PDU session is a channel for transmitting PDUs, which terminal devices need to use to transfer PDUs to and from data network DN 140. SMF network function 139 is responsible for establishing, maintaining, and deleting PDU sessions. SMF network function 139 includes session management (e.g., session establishment, modification, and release, including tunnel maintenance between user plane function (UPF) 130 and (R)AN 120), selection and control of UPF network function 130, service and session continuity (SSC) mode selection, roaming, and other session-related functions. In some embodiments, SMF 139 may be responsible for allocating and managing Internet Protocol (IP) addresses assigned to terminal device 110. In some embodiments, terminal device 110 may also be responsible for selecting or reselecting a specific instance of UPF 130 or UPF 13 for traffic associated with a specific session of terminal device 110. The SMF 139 can configure packet processing rules (e.g., packet routing and forwarding rules, packet marking rules) in the UPF 130 to support local area network (LAN) type communications (e.g., 5G LAN communications).

[0126] 11. AF 141 is a control plane network function provided by the operator network. It provides application layer information and can interact with the policy framework through network open function elements or directly with the policy framework to make policy decision requests. AF 141 can be located within or outside the operator network. AF 141 can interact with the core network through NEF 131.

[0127] It is understood that the above network elements or functions can be physical entities in hardware devices, software instances running on dedicated hardware, or virtualized functions instantiated on a shared platform (e.g., a cloud platform). Simply put, an NF can be implemented by hardware or software.

[0128] In Figure 1, Nnef, Nnrf, Npcf, Nudm, Nudr, Nnwdaf, Nausf, Namf, Nsmf, N1, N2, N3, N4, and N6 are interface serial numbers. For example, the meaning of the above interface serial numbers can be found in the meaning defined in the 3GPP standard protocol, and this application does not limit the meaning of the above interface serial numbers. It should be noted that the interface name between the various network functions in the figure is only an example. In a specific implementation, the interface name of the system architecture may also be other names, which is not limited by this application. In addition, the name of the message (or signaling) transmitted between the above network elements is only an example and does not constitute any limitation on the function of the message itself.

[0129] For ease of explanation, in the embodiments of this application, network functions (such as NEF 131…SMF 139) are collectively referred to as NFs. That is, the NFs described later in the embodiments of this application can be replaced with any network function. Furthermore, FIG1 schematically illustrates only some network functions, and the NFs described later are not limited to those shown in FIG1.

[0130] It should be understood that the above-mentioned network architecture applied to the embodiment of the present application is only a network architecture described from the perspective of service-oriented architecture. The network architecture applicable to the embodiment of the present application is not limited to this. Any network architecture that can realize the functions of the above-mentioned network elements is applicable to the embodiment of the present application.

[0131] It should also be understood that the AMF, SMF, UPF, NEF, AUSF, NRF, PCF, and UDM shown in the figure can be understood as network elements for implementing different functions, for example, they can be combined into network slices as needed. These core network elements can be independent devices or integrated into the same device to implement different functions. This application does not limit the specific form of the above network elements.

[0132] The network element types involved in the following embodiments may be: network elements may be divided into different network element types according to functions, deployment locations, or home domains. For example, division by service function may include division into the aforementioned SMF, AMF, UPF, NEF, and other network element types; division by deployment location may include division into access network elements or non-access network elements; and division by home domain may include division into visited network elements or home network elements.

[0133] For example, network elements belonging to different network element types provide different services. For example, network elements belonging to AMF are responsible for access control and mobility management of terminal devices accessing the operator network; for example, network elements belonging to SMF are responsible for managing PDU sessions of terminal devices.

[0134] It should be understood that during the service certificate update process, a large number of certificates may be updated simultaneously, and the certificate update process may cause the corresponding network elements to be unavailable. In particular, if network elements providing the same service in the network update their certificates at the same time, the network will be unable to provide the corresponding service. For example, if all AMFs in the network perform service certificate updates, there will be no available AMFs in the network.

[0135] It should also be understood that the above naming is defined only to facilitate the distinction between different functions and should not constitute any limitation to this application. This application does not exclude the possibility of adopting other naming in 5G networks and other future networks. For example, in future communication networks, some or all of the above network elements may continue to use 5G terminology, or may adopt other names.

[0136] To facilitate understanding of the embodiments of the present application, some basic concepts involved in the present application are briefly described. It should be understood that the basic concepts introduced below are illustrated by taking the basic concepts specified in the NR protocol as an example, but the embodiments of the present application are not limited to being applicable only to NR systems. Therefore, the standard names that appear when describing the NR system as an example are all functional descriptions. The specific names are not limited and only indicate the functions of the device, which can be extended to other systems in the future.

[0137] The network function (e.g., SMF 139 in FIG1 ) may generate corresponding packet detection rules for different PDU sessions and send them to the corresponding UPF to implement forwarding of data packets in the 3GPP network.

[0138] Table 1 is a schematic diagram of a packet detection rule.

[0139] Table 1

[0140] As shown in Table 1, the packet detection rules include packet detection information, forwarding rule ID, QoS rule ID, etc. Specifically, the packet detection information is used to match the data packet received by the UPF. Once the data packet matches the relevant information of the packet detection information, the ID of the relevant rule contained in the packet detection rule is indexed to the specific relevant rule and operations such as packet forwarding and QoS control are performed.

[0141] In the packet detection information, the UE IP address is used to determine the relevant session, which is used to match the source IP address or destination IP in the five-tuple information of the data packet received by the UPF; the packet filter set is used to match the source and / or destination port number and / or source and / or destination IP address and other information received by the UPF. The IP address mentioned in the embodiments of the present application can be an IP address of the fourth version of the Internet Protocol (Internet Protocol version 4, IPv4) or a prefix of the sixth version of the Internet Protocol (Internet Protocol version 6, IPv6).

[0142] In addition, in order to facilitate understanding of the embodiments of the present application, the following explanations are made.

[0143] First, in this application, "used to indicate" can include being used for direct indication and being used for indirect indication. When describing that a certain indication information is used to indicate A, it can include that the indication information directly indicates A or indirectly indicates A, but it does not mean that the indication information must include A.

[0144] The information indicated by the indication information is referred to as the information to be indicated. During the specific implementation process, there are many ways to indicate the information to be indicated. The information to be indicated can be sent as a whole or divided into multiple sub-information and sent separately. The transmission period and / or transmission timing of these sub-information can be the same or different. The specific transmission method is not limited in this application. The transmission period and / or transmission timing of these sub-information can be predefined, for example, according to a protocol, or can be configured by the transmitting device through sending configuration information to the receiving device.

[0145] Second, "at least one" shown in the present application refers to one or more, and "a plurality of" refers to two or more. In addition, in the embodiments of the present application, "first", "second" and various digital numbers (for example, "#1", "#2", etc.) are only for the convenience of description and are not used to limit the scope of the embodiments of the present application. The size of the sequence number of each process below does not mean the order of execution. The execution order of each process should be determined by its function and inherent logic, and should not constitute any limitation to the implementation process of the embodiments of the present application. It should be understood that the objects described in this way can be interchanged where appropriate, so that the schemes other than the embodiments of the present application can be described. In addition, in the embodiments of the present application, words such as "301", "302" are only for the convenience of description and are not used to limit the order of execution of steps.

[0146] Third, in this application, words such as "exemplary" or "for example" are used to indicate examples, illustrations, or descriptions. Any embodiment or design described in this application as "exemplary" or "for example" should not be construed as being preferred or advantageous over other embodiments or designs. Rather, the use of words such as "exemplary" or "for example" is intended to present the relevant concepts in a concrete manner.

[0147] Fourth, the "protocol" involved in the embodiments of the present application may refer to a standard protocol in the field of communications, for example, it may include an LTE protocol, an NR protocol, and related protocols used in future communication systems, which is not limited in this application.

[0148] Fifth, in the embodiments of the present application, "under the circumstances", "when", and "if" can sometimes be used interchangeably. It should be pointed out that when the distinction between them is not emphasized, the meanings they intend to express are consistent.

[0149] Sixth, in the embodiments of this application, various terms and English abbreviations, such as radio resource control (RRC), are provided for ease of description and should not constitute any limitation on this application. This application does not exclude the possibility of defining other terms in existing or future protocols that can achieve the same or similar functions.

[0150] Seventh, the term "and / or" in this document simply describes an association between related objects, indicating that three possible relationships exist. For example, "A and / or B" can mean: A exists alone, A and B exist simultaneously, or B exists alone. Furthermore, the character " / " in this document generally indicates that the related objects are in an "or" relationship.

[0151] Figure 2 is a schematic diagram of a network architecture 200 provided in an embodiment of the present application. As shown in Figure 2, an application server (AS) 211 is deployed in a DN 210, and an application server 221 is deployed in a DN 220. A communication device 230 can access the application servers in the DN through the core network, and the application servers in the DN can also provide services to the communication device 230 through the core network.

[0152] The network architecture 200 shown in Figure 2 includes an uplink classifier (ULCL) 243, a packet data unit (PDU) session anchor (PSA) 241, and a PSA 242. The ULCL 243 is a network element that can provide data packet forwarding and data offload services. Therefore, the ULCL 243 can be considered a user plane functional network element. For example, in the network architecture shown in Figure 1, the UPF 130 may include the ULCL 243. The PSA is a network element in a mobile communication network (or the core network of a mobile communication network) that can access application servers. In other words, application servers can access the mobile communication network through the PSA. Therefore, the PSA can also be considered a user plane functional network element. For example, in the network architecture shown in Figure 1, the UPF 130 may include the PSA 241 and the PSA 242. As described above, the SMF can generate corresponding packet detection rules for different PDU sessions and send the packet detection rules to the UPF. Corresponding to the network architecture 200 shown in FIG2 , PSA 241 and PSA 242 are both managed by SMF 251. Therefore, SMF 251 can generate packet detection rules for PSA 241 and send the generated packet detection rules to PSA 241. Similarly, SMF 251 can also generate packet detection rules for PSA 242 and send the generated packet detection rules to PSA 242. In this way, PSA 241 and PSA 242 can detect and process received data packets according to the packet detection rules.

[0153] FIG3 is a schematic diagram of another network architecture 300 provided in an embodiment of the present application. The difference between the network architecture 300 shown in FIG3 and the network architecture 200 shown in FIG2 is that PSA 341 and PSA 342 are managed by different SMFs. Specifically, PSA 341 is managed by SMF 351, and PSA 352 is managed by SMF 352. SMF 351 can generate packet detection rules and send the generated packet detection rules to PSA 341; SMF 352 can generate packet detection rules and send the packet detection rules to PSA 342.

[0154] Figure 4 is a schematic diagram of another network architecture 400 provided in an embodiment of the present application. In the network architecture 400 shown in Figure 4 , PSA 441 can communicate directly with the RAN without going through the ULCL. Furthermore, PSA 442 can also communicate without having to communicate with the RAN. In the network architecture 400 shown in Figure 4 , PSA 441 and PSA 442 are managed by the same SMF, namely SMF 451 shown in Figure 4 . SMF 451 configures packet inspection rules for PSA 441 and PSA 442, respectively, and sends the configured packet inspection rules to PSA 441 and PSA 442, respectively.

[0155] Figure 5 is a schematic diagram of another network architecture 500 provided according to an embodiment of the present application. The difference between the network architecture 500 shown in Figure 5 and the network architecture 400 shown in Figure 4 is that the two PSAs in network architecture 500 are respectively managed by two different SMFs. Specifically, PSA 541 is managed by SMF 551, and PSA 552 is managed by SMF 552. SMF 551 can generate packet detection rules and send the generated packet detection rules to PSA 541; SMF 552 can generate packet detection rules and send the packet detection rules to PSA 542.

[0156] Those skilled in the art will understand that the network architectures shown in Figures 2 to 4 are merely schematic and non-limiting examples of network architectures to which the technical solution of the present application can be applied. The method for confirming a tunnel provided in the embodiments of the present application can also be applied to other network architectures. For example, in the network architectures shown in Figures 2 to 5, each application server accesses the mobile communication network through a PSA. In some embodiments, an application server may also correspond to two or more PSAs and access the network through the corresponding application servers. Taking Figure 2 as an example, in some embodiments, the network architecture 200 may further include PSA 261 and PSA 262 (not shown in the figure), AS211 may also access the mobile communication network through PSA 261, and AS221 may also access the mobile communication network through PSA 262. In this case, SMF 251 may also determine packet detection rules for PSA 261 and PSA 262 respectively, and send the determined packet detection rules to PSA 261 and PSA 262.

[0157] FIG6 is a schematic flowchart of a communication method provided according to an embodiment of the present application.

[0158] 601. A first network element sends a request #1 to a second network element. Accordingly, the second network element receives the request #1. The request #1 includes the address information of the application server #1, the address information of the application server #2, and the identity information #1 of the terminal #1.

[0159] The first network element may be a functional network element that provides various business services. Therefore, the first network element may also be referred to as a business network element, a first business network element, etc. For example, the first network element may be an AF in the network architecture shown in Figures 1 to 5.

[0160] The second network element may be a control plane function network element. The second network element may also be referred to as a control plane function network element or a control plane network element. For example, in some embodiments, the second network element may be an NEF in the network architecture shown in FIG1 to FIG5.

[0161] The application server #1 and the application server #2 may belong to different DNs. For example, in some embodiments, the first DN includes the application server #1, and the second DN includes the application server #2.

[0162] In some embodiments, depending on the deployment location, the first DN may also be referred to as a local DN, and the second DN may also be referred to as a remote DN. Accordingly, application server #1 may also be referred to as a local application server, and application server #2 may also be referred to as a remote application server.

[0163] In some embodiments, the local DN (or local application server) and the remote DN (or remote application server) can be determined by the delay from the DN or the application server in the DN to the terminal. For example, assuming that the delay from the terminal to the local application server is D1, and the delay from the terminal to the remote application server is D2, then D1 and D2 satisfy the following relationship: D1 <D2。

[0164] In some other embodiments, it is not necessary to distinguish between the remote DN and the local DN. Therefore, in some embodiments, D1 may be equal to D2.

[0165] In some embodiments, the address information of application server #1 may include the IP address and port number #1 of application server #1; and the address information of application server #2 may include the IP address and / or port number #2 of application server #2. In other words, the address information of application server #1 may include both the IP address and port number #1 of application server #1, while the address information of application server #2 may include either or both the IP address or port number #2 of application server #2.

[0166] In other embodiments, the address information of application server #1 may include the IP address and / or port number #1 of application server #1; and the address information of application server #2 may include the IP address and port number #2 of application server #2. In other words, the address information of application server #2 may include both the IP address and port number #2 of application server #2, while the address information of application server #1 may include either or both the IP address or port number #1 of application server #1.

[0167] In other embodiments, the address information of application server #1 may include the IP address and / or port number #1 of application server #1; and the address information of application server #2 may include the IP address and / or port number #2 of application server #2. In other words, in this case, the address information of application server #1 and application server #2 may include any one or both of their respective IP addresses or port numbers. Similarly, in other embodiments, the address information of application server #1 may include the IP address and port number #1 of application server #1, and the address information of application server #2 may include the IP address and port number #2 of application server #2.

[0168] In some embodiments, port number #1 is a fixed port number, and port number #2 is also a fixed port number. For example, in some embodiments, port number #1 and port number #2 may both be port numbers assigned by application server #1. In other embodiments, port number #1 and port number #2 may both be port numbers assigned by the first network element. In some embodiments, port number #1 and port number #2 may be terminal-related. For example, in some embodiments, application server #1 determines that it needs to send a data packet to application server #2 in response to a data packet from terminal #1. In this case, application server #1 may allocate two port numbers, namely, port number #1 and port number #2, to terminal #1. Alternatively, application server #1 may instruct the first network element to allocate two fixed transmission port numbers, namely, port number #1 and port number #2, to terminal #1. In other embodiments, application server #1 may determine that it needs to send a data packet to application server #2 while providing an application service to terminal #1. In this case, the application server #1 may allocate two fixed sending port numbers to the terminal #1, or the application server #1 may instruct the first network element to allocate two fixed sending port numbers to the terminal #1.

[0169] In other embodiments, port number #1 or port number #2 is a fixed port number. In other words, one of port number #1 and port number #2 is a fixed port number, while the other can be a random port number. Similarly, the fixed port number can be terminal-dependent. For example, application server #1 can assign a fixed port number (e.g., port number #1) to terminal #1 when confirming that a data packet needs to be sent to application server #2.

[0170] In other embodiments, the port number #1 and the port number #2 are both random port numbers.

[0171] In the embodiments of the present application, the event that triggers the first network element to send the address information of application server #1 and application server #2 to the second network element (hereinafter referred to as the "triggering event") is not limited. For example, in some embodiments, the triggering event may be the establishment of a PDU session for terminal #1. For example, when the PDU session for terminal #1 is established, application server #1 may instruct the first network element to send the address information of application server #1 and application server #2 to the second network element. At the same time, application server #1 may assign fixed port numbers (i.e., port numbers #1 and #2 mentioned above) to terminal #1. For another example, in some embodiments, the triggering event may be the receipt of a data packet sent by terminal #1. For example, application server #1 receives a data packet from terminal #1. In this case, application server #1 may assign fixed port numbers (i.e., port numbers #1 and #2 mentioned above) to terminal #1 and instruct the first network element to send request #1 to the second network element. For another example, in other embodiments, the triggering event may be determined independently by application server #1. For example, the application server #1 confirms that it needs the assistance of the application server #2 during the process of providing services to the terminal #1 (for example, the application server #1 is processing data from the terminal #1). In this case, the application server #1 can instruct the first network element to send the request #1 to the second network element. In the above embodiments, the application server #1 instructs the first network element to send the request #1 to the second network element. In other embodiments, the first network element may also determine on its own that it needs to send the request #1 to the second network element. For example, in some embodiments, the first network element sends the request #1 to the second network element when it determines that the PDU session of the terminal #1 has been established or the application server #1 has obtained the data packet from the terminal #1.

[0172] The identity information #1 of the communication device #1 may be any one or more of the IP address of the terminal #1, the subscription permanent identifier (SUPI) of the terminal #1, or the generic public subscription identifier (GPSI) of the terminal #1.

[0173] Optionally, in some embodiments, the first network element may further send indication information #1 to the second network element. Indication information #1 is used to instruct the establishment of a tunnel between user plane function network element #1 and user plane function network element #2. In other words, in some embodiments, the first network element may send a display indication information to the second network element, which is used to instruct the establishment of a tunnel between user plane function network element #1 and user plane function network element #2. User plane function network element #1 is a network element that can access application server #1, and user plane function network element #2 is a network element that can access application server #2. User plane function network element #1 and user plane function network element #2 may be network elements in a network, but application server #1 and application server #2 do not belong to the network. The network may be a mobile communication network or a core network within the mobile communication network. Taking Figure 2 as an example, if application server #1 is AS211, user plane function network element #1 is PAS241; if application server #2 is AS221, user plane function network element #2 is PAS242.

[0174] Optionally, in some embodiments, the first network element may send instruction information #2 to the second network element, wherein the instruction information #2 is used to instruct the second network element to send the address information of the application server #1, the address information of the application server #2, and the identity information of the terminal #1 to a third network element.

[0175] The third network element may be a control network element. For example, the third network element may be used to generate and manage users, sessions, QoS processing policies, etc. Therefore, the third network element may be referred to as a control network element, a control policy network element, or a control function network element. In some embodiments, the third network element may be a PCF as shown in Figures 1 to 5.

[0176] Optionally, in some embodiments, the indication information #2 may also be used to instruct the second network element to establish a mapping relationship, where the mapping relationship is a mapping relationship between the identity information of the terminal #1 and the address information of the application server #1.

[0177] In summary, the first network element can instruct the second network element to establish a mapping relationship between the identity information of the terminal #1 and the address information of the application server #1 by displaying instructions, and instruct the second network element to send the address information of the application server #1, the address information of the application server #2 and the identity information of the terminal #1 to the third network element.

[0178] In other embodiments, the first network element may indicate the content indicated by indication information #2 through two indication information. For example, in some embodiments, the first network element may send indication information #2.1 and indication information #2.2 to the second network element. Indication information #2.1 is used to instruct the second network element to establish a mapping relationship between the identity information of terminal #1 and the address information of application server #1; and indication information #2.2 is used to instruct the second network element to send the address information of application server #1, the address information of application server #2, and the identity information of terminal #1 to a third network element.

[0179] Optionally, in other embodiments, the first network element may send instruction information #3 to the second network element. Instruction information #3 has all the functions of instruction information #1 and instruction information #2. In other words, instruction information #3 may indicate the following: instructing the establishment of a tunnel between user plane function network element #1 and user plane function network element #2, instructing the second network element to establish a mapping relationship between the identity information of terminal #1 and the address information of application server #1, and instructing the second network element to send the address information of application server #1, the address information of application server #2, and the identity information of terminal #1 to a third network element.

[0180] Optionally, in some embodiments, the first network element may send any one of indication information #1, indication information #2, or indication information #3 to the second network element. In other embodiments, the first network element may send any multiple or all of indication information #1, indication information #2, or indication information #3 to the second network element.

[0181] Optionally, in some embodiments, all indication information sent by the first network element to the second network element may be carried by request #1. In other words, request #1 may also include any one or more of indication information #1, indication information #2, or indication information #3.

[0182] Optionally, in other embodiments, part or all of the indication information sent by the first network element to the second network element may also be carried by a single request. For example, indication information #1 may be carried by request #1, and indication information #2 may be carried by request #a.

[0183] Optionally, in some embodiments, the address information of application server #1, the address information of application server #2, and the identity information #1 of terminal #1 may be carried in different requests. For example, request #a includes the address information of application server #1, request #b includes the address information of application server #2, and request #c includes the identity information #1 of terminal #1.

[0184] 602. The second network element establishes a mapping relationship between the identity information of the terminal #1 and the address information of the application server #1.

[0185] Optionally, in some embodiments, the second network element may save the established mapping relationship locally.

[0186] Optionally, in other embodiments, the second network element may also store the established mapping relationship in another network element. For example, in some embodiments, the second network element may store the established mapping relationship in a network element with a storage function. For example, the network element with a storage function may be the UDR 135 in the system shown in FIG1 .

[0187] Optionally, in some embodiments, the second network element may establish a mapping relationship between the identity information of the terminal #1 and the address information of the application server #1 upon receiving the display indication. For example, the second network element may establish a mapping relationship between the identity information of the terminal #1 and the address information of the application server #1 upon receiving indication information #2 or indication information #3.

[0188] Optionally, in some embodiments, if the second network element does not receive an explicit indication (e.g., indication information #2 and indication information #3), then it can be considered that the first network element implicitly instructs the second network element to establish a mapping relationship between the identity information of the terminal #1 and the address information of the application server #1 through request #1. In other words, if the first network element sends the request #1 to the second network element, or the first network element sends any one or more of the identity information #1 of the terminal #1, the address information of the application server #1, and the address information of the application server #2 to the second network element, it can be considered that the first network element instructs the second network element to establish a mapping relationship between the identity information of the terminal #1 and the address information of the application server #1. In other words, if the second network element receives the request #1 or receives any one or more of the identity information #1 of the terminal #1, the address information of the application server #1, and the address information of the application server #2, then the second network element establishes a mapping relationship between the identity information of the terminal #1 and the address information of the application server #1.

[0189] Optionally, in some embodiments, the mapping relationship may store the identity information #1 of the terminal #1 and the address information of the application server #1.

[0190] Optionally, in other embodiments, the mapping relationship may store the identity information #2 of the terminal #1 and the address information of the application server #1. The identity information #2 of the terminal #1 includes the IP address of the terminal #1 and / or the SUPI of the terminal #1. The identity information #2 of the terminal #1 may be determined based on the identity information #1 of the terminal #1.

[0191] 603. The second network element determines a third network element according to the identity information #1 of the terminal #1.

[0192] 604. The second network element sends the address information of the application server #1 and the address information of the application server #2 to the third network element. Correspondingly, the third network element receives the address information of the application server #1 and the address information of the application server #2.

[0193] Optionally, in some embodiments, the second network element may directly send the received #Request 1 containing the address information of the application server #1 and the address information of the application server #2 to the third network element. In other words, in this case, it can be considered that the second network element transparently transmits the request #1.

[0194] Optionally, in other embodiments, the second network element may re-determine a new request (e.g., request #1-1) based on request #1, where request #1-1 includes relevant information to be sent to the third network element. For example, request #1-1 includes the address information of application server #1 and the address information of application server #2.

[0195] Optionally, in some embodiments, the second network element may determine the identity information #2 of terminal #1 based on the identity information #1 of terminal #1. In this case, the second network element may also send the identity information #2 of terminal #1 to the third network element. Accordingly, the third network element receives the identity information #2 of terminal #1.

[0196] Optionally, in some embodiments, the second network element may send the address information of the application server #1, the address information of the application server #2, and the identity information #2 of the terminal #1 to the third network element upon receiving the display indication. For example, the second network element may send the address information of the application server #1, the address information of the application server #2, and the identity information #2 of the terminal #1 to the third network element upon receiving indication information #2 or indication information #3.

[0197] Optionally, in other embodiments, if the second network element does not receive the display indication (e.g., indication information #2 and indication information #3), then it can be considered that the first network element implicitly instructs the second network element to send the address information of the application server #1, the address information of the application server #2, and the identity information #2 of the terminal #1 to the third network element. In other words, if the first network element sends the identity information #1 of the terminal #1, the address information of the application server #1, and the address information of the application server #2 to the second network element, it can be considered that the first network element instructs the second network element to send the address information of the application server #1, the address information of the application server #2, and the identity information #2 of the terminal #1 to the third network element. In other words, if the second network element receives the identity information #1 of the terminal #1, the address information of the application server #1, and the address information of the application server #2, then the second network element sends the address information of the application server #1, the address information of the application server #2, and the identity information #2 of the terminal #1 to the third network element.

[0198] As described above, the second network element's sending of the identity information #2 of terminal #1 to the third network element is optional. In some embodiments, the instruction information #2 and the instruction information #3 may also indicate that the address information of application server #1 and the address information of application server #2 are sent to the third network element. In other words, in this case, the instruction information #2 and the instruction information #3 may not necessarily indicate that the identity information #2 of terminal #1 is sent to the third network element. Of course, in other embodiments, even if the instruction information #2 or the instruction information #3 indicates that the identity information #2 of terminal #1 is sent to the third network element, the second network element may independently determine not to send the identity information #2 of terminal #1 to the third network element.

[0199] As described above, in some embodiments, the first network element may further send an indication message (e.g., indication message #1 and indication message #3) to the second network element indicating the establishment of a tunnel between user plane function network element #1 and user plane function network element #2. When the second network element receives the indication message, the second network element may send an indication message to the third network element, where the indication message is used to instruct the establishment of a tunnel between user plane function network element #1 and user plane function network element #2. For example, if the second network element receives indication message #1, the second network element may directly forward the indication message #1 to the third network element. Alternatively, it may be considered that the second network element transparently transmits the indication message #1 to the third network element. For another example, if the second network element receives indication message #3, the second network element may determine a new indication message (which may be referred to as indication message #3.1). Indication message #3.1 is used to instruct the establishment of a tunnel between user plane function network element #1 and user plane function network element #2.

[0200] Optionally, in some embodiments, if the second network element does not receive instruction information (e.g., instruction information #1 or instruction information #3) explicitly instructing the establishment of a tunnel between user plane function network element #1 and user plane function network element #2, then the first network element may be deemed to have implicitly instructed the establishment of a tunnel between user plane function network element #1 and user plane function network element #2. In other words, if the first network element sends request #1, or sends any one or more of the identity information #1 of terminal #1, the address information of application server #1, and the address information of application server #2 to the second network element, then the first network element may be deemed to have instructed the establishment of a tunnel between user plane function network element #1 and user plane function network element #2. In other words, if the second network element receives request #1, or receives any one or more of the identity information #1 of terminal #1, the address information of application server #1, and the address information of application server #2, then the second network element sends an instruction information to the third network element, wherein the instruction information instructs the establishment of a tunnel between user plane function network element #1 and user plane function network element #2.

[0201] 605. The third network element determines session management network element #1.

[0202] Optionally, in some embodiments, the third network element may determine the session management network element #1 based on the address information of the application server #1.

[0203] Optionally, in some other embodiments, the third network element may determine the session management network element #1 based on the identity information #2 of the terminal #1.

[0204] In some embodiments, if the third network element obtains the identity information of the terminal, the third network element can independently determine whether to determine the session management network element based on the identity information of the terminal. In other words, if the third network element obtains the identity information #2 of terminal #1, the third network element can determine the session management network element based on the address information of application server #1, or it can determine the session management network element based on the identity information 2 of terminal #1.

[0205] In other embodiments, if the third network element obtains the identity information of the terminal, the third network element determines the session management network element based on the identity information of the terminal. In other words, if the third network element obtains the identity information #2 of terminal #1, the third network element determines the session management network element based on the identity information #2 of terminal #1; if the third network element does not obtain the identity information #2 of terminal #1, the third network element may determine the session management network element based on the address information of application server #1.

[0206] 606. The third network element sends the address information of the application server #1 and the address information of the application server #2 to the session management network element #1.

[0207] Optionally, in some embodiments, the third network element determines a rule related to the tunnel, and then sends the rule to the session management network element #1.

[0208] Optionally, in some embodiments, the third network element may directly determine the rule based on the received information. In other words, the rule only includes the address information of the application server #1 and the address information of the application server #2 received by the third network element from the second network element.

[0209] Optionally, in other embodiments, the third network element may determine this rule based on the received information and other information. For example, in some embodiments, the third network element may receive identity information #2 of terminal #1. In this case, the third network element may also determine identity information #3 of terminal #1 based on identity information #2 of terminal #1, and then send identity information #3 of terminal #1 to session management network element #1. In this case, the rule includes the address information of application server #1, the address information of application server #2, and identity information #3 of terminal #1 determined by the third network element.

[0210] The identity information #3 of the terminal #1 may be any one or more of the IP address of the terminal #1, the SUPI of the terminal #1, or the PDU session ID.

[0211] A session management network element (e.g., session management network element #1) is a network element that has session management functions. For example, the session management network element can manage the creation and deletion of PDU sessions, maintain PDU session contexts, and user plane forwarding channel information. For example, the session management network element can be an SMF in the system shown in Figures 1 to 5.

[0212] As described above, in some embodiments, the third network element may also receive a display instruction for instructing the establishment of a tunnel between user plane function network element #1 and user plane function network element #2. In this case, the third network element may forward the display instruction to the session management network element #1. Similarly, if the third network element does not receive the display instruction, the third network element may independently determine a display instruction for instructing the establishment of a tunnel between user plane function network element #1 and user plane function network element #2, and send the display instruction to the session management network element #1.

[0213] 607. The session management network element #1 may configure a tunnel for the user plane function network element #1 and / or the user plane function network element #2 according to tunnel-related rules, wherein the rules include the address information of the application server #1 and the address information of the application server #2.

[0214] The session management network element #1 may determine or select the user plane function network element #1 based on the address information of the application server #1. The session management network element #1 may determine or select the user plane function network element #2 based on the address information of the application server #2.

[0215] In some embodiments, session management network element #1 can determine, based on the address of application server #1, that a user plane function network element controlled by session management network element #1 is a user plane function network element capable of accessing application server #1. In this case, session management network element #1 can determine that this user plane function network element is user plane function network element #1. Session management network element #1 can determine, based on the address of application server #2, that another user plane function network element controlled by session management network element #1 is a user plane function network element capable of accessing application server #2. In this case, session management network element #1 can determine that this user plane function network element is user plane function network element #2.

[0216] In other embodiments, session management network element #1 can determine, based on the address of application server #1, that a user plane function network element controlled by session management network element #1 is a user plane function network element that can access application server #1. In this case, session management network element #1 can determine that this user plane function network element is user plane function network element #1. Session management network element #1 can determine, based on the address of application server #1, that none of the user plane function network elements controlled by session management network element #1 can access application server #2. In this case, session management network element #1 can determine a session management network element (which can be referred to as session management network element #2) that can control the user plane function network element that can access application server #2, and send the address information of application server #1 and application server #2 to session management network element #2.

[0217] When both user plane function network element #1 and user plane function network element #2 are controlled by session management network element #1, session management network element #1 may interact with user plane function network element #1 and / or user plane function network element #2 to configure a tunnel for user plane function network element #1 and / or user plane function network element #2. For example, session management network element #1 configures user plane function network element #1 by sending packet detection rule #1 to user plane function network element #1 to obtain the tunnel. Session management network element #1 may determine packet detection rule #1 and send packet detection rule #1 to user plane function network element #1. Packet detection rule #1 may include at least one of the address information of application server #1 or the address information of application server #2. For example, in some embodiments, packet detection rule #1 may include packet detection information #1, which includes packet filter set #1 and / or address information #1. Packet filter set #1 includes at least one of the address information of application server #1 or the address information of application server #2. The address information #1 includes at least one of the IP address or port number #1 of the application server #1. Optionally, in some embodiments, session management network element #1 obtains the tunnel by sending packet detection rule #2 to user plane function network element #2 to configure user plane function network element #2. Session management network element #1 may determine packet detection rule #2 and send packet detection rule #2 to user plane function network element #2. The packet detection rule #2 may include at least one of the address information of application server #1 or the address information of application server #2. For example, in some embodiments, packet detection rule #2 may include packet detection information #2, which includes packet filter set #2 and / or address information #2. The packet filter set #2 includes at least one of the address information of application server #1 or the address information of application server #2. The address information #2 includes at least one of the IP address or port number #1 of application server #1.

[0218] When user plane function network element #1 is controlled by session management network element #1 and user plane function network element #2 is controlled by session management network element #2, session management network element #1 may interact with user plane function network element #1 and / or session management network element #2 to configure a tunnel for user plane function network element #1 and / or user plane function network element #2. For example, session management network element #1 configures user plane function network element #1 by sending packet detection rule #1 to user plane function network element #1 to obtain the tunnel. Session management network element #1 may determine packet detection rule #1 and send packet detection rule #1 to user plane function network element #1. Packet detection rule #1 may include at least one of the address information of application server #1 or the address information of application server #2. For example, in some embodiments, packet detection rule #1 may include packet detection information #1, which includes packet filter set #1 and / or address information #1. Packet filter set #1 includes at least one of the address information of application server #1 or the address information of application server #2. The address information #1 includes at least one of the IP address or port number #1 of the application server #1. Optionally, session management network element #1 configures user plane function network element #2 by sending packet detection rule #2 to user plane function network element #2 to obtain the tunnel. For example, in some embodiments, session management network element #1 may also instruct session management network element #2 to send packet detection rule #2 to user plane function network element #2. For example, in some embodiments, session management network element #1 may instruct session management network element #2 to determine packet detection rule #2 and then send the packet detection rule #2 to user plane function network element #2. In other words, in this case, packet detection rule #2 is determined by session management network element #2. In other embodiments, session management network element #1 may independently determine packet detection rule #2 and then send packet detection rule #2 to session management network element #2. Session management network element #2 then sends the obtained packet detection rule #2 to user plane function network element #2. Packet detection rule #2 may include at least one of the address information of application server #1 or the address information of application server #2. For example, in some embodiments, packet detection rule #2 may include packet detection information #2, which includes packet filter set #2 and / or address information #2. Packet filter set #2 includes at least one of the address information of application server #1 or the address information of application server #2. Address information #2 includes at least one of the IP address of application server #1 or port number #1.

[0219] Packet inspection rule #1 and packet inspection rule #2 can be used to inspect data packets from application server #1.

[0220] Corresponding to Table 1, packet filter set #1 and packet filter set #2 may be entries named “packet filter set” in Table 1, and address information #1 and address information #2 may be entries named “UE IP address” in Table 1.

[0221] If the network also includes a network element responsible for data packet forwarding and data offloading services (which may be referred to as a seventh network element), the session management network element #1 may determine packet detection information #5 and send the packet detection rule #5 to the seventh network element. For example, the seventh network element may be the ULCL in Figure 2 or Figure 3.

[0222] Packet detection rule #5 may include packet detection information #5, which is used to detect data packets from application server #1. Packet detection information #5 may include a packet filter set #5 and / or address information #5. Packet filter set #5 may include at least one of the address information of application server #1 or the address information of application server #2. Address information #5 includes at least one of the IP address or port number #1 of application server #1. Similarly, packet filter set #5 may be the entry named "Packet Filter Set" in Table 1, and address information #5 may be the entry named "UE IP Address" in Table 1.

[0223] 608. The session management network element #1 may send tunnel confirmation information to the first network element. The tunnel confirmation information is used to indicate that the tunnel between the user plane function network element #1 and the user plane function network element #2 has been configured.

[0224] For ease of description, in the following embodiments, the tunnel configured by the method shown in FIG. 6 may be referred to as tunnel #1.

[0225] When tunnel #1 is configured, application server #1 can send a data packet to application server #2 through tunnel #1. The source IP address of the data packet is application server #1's IP address, the source port number is port #1, the destination IP address is application server #2's IP address, and the destination port number is port #2.

[0226] After receiving the data packet from application server #1, user plane function network element #1 can match the data packet based on packet detection rule #1. If the data packet matches packet detection rule #1, it will perform the corresponding forwarding action and send the data packet to user plane function network element #2 or the seventh network element.

[0227] Similarly, if packet inspection rule #2 is configured for user plane function network element #2, user plane function network element #2 can match the received data packet based on packet inspection rule #2. If the data packet matches packet inspection rule #2, user plane function network element #2 performs the corresponding forwarding action and sends the data packet to application server #2. If packet inspection rule #2 is not configured for user plane function network element #2, user plane function network element #2 can send the data packet to application server #2 based on the outer header of the encapsulated data packet.

[0228] If the system includes a seventh network element and a packet detection rule (i.e., packet detection rule #5 mentioned above) is configured for the seventh network element, the seventh network element can receive a data packet from user plane function network element #1, match the received data packet based on packet detection rule #5, and if the data packet matches packet detection rule #5, perform the corresponding forwarding action and send the data packet to user plane function network element #2. Similarly, if no packet detection rule is configured for the seventh network element, the seventh network element can send the data packet to user plane function network element #2 based on the outer header.

[0229] Application server #2 can also start a similar process to build a tunnel to send data packets to application server #1. The following describes the tunnel determination process with reference to FIG7.

[0230] FIG7 is a schematic flowchart of another communication method provided according to an embodiment of the present application.

[0231] 701. The fourth network element sends a request #2 to the fifth network element. Correspondingly, the fifth network element receives the request #2. The request #2 includes the address information of the application server #1 and the address information of the application server #2.

[0232] The fourth network element can be a functional network element that provides various business services. Therefore, the fourth network element can also be called a service network element, a first service network element, etc. For example, the fourth network element can be the AF in the network architecture shown in Figures 1 to 5. The fourth network element and the first network element in the embodiment shown in Figure 6 can be the same network element or different network elements.

[0233] The fifth network element may be a control plane function network element. The fifth network element may also be referred to as a control plane function network element or a control plane network element. For example, in some embodiments, the fifth network element may be an NEF in the network architecture shown in Figures 1 to 5. The fifth network element may be the same network element as the second network element in the embodiment shown in Figure 6 or a different network element.

[0234] The application server #1 and the application server #2 may belong to different DNs. For example, in some embodiments, the first DN includes the application server #1, and the second DN includes the application server #2.

[0235] In some embodiments, depending on the deployment location, the first DN may also be referred to as a local DN, and the second DN may also be referred to as a remote DN. Accordingly, application server #1 may also be referred to as a local application server, and application server #2 may also be referred to as a remote application server.

[0236] In some embodiments, the local DN (or local application server) and the remote DN (or remote application server) can be determined by the delay from the DN or the application server in the DN to the terminal. For example, assuming that the delay from the terminal to the local application server is D1, and the delay from the terminal to the remote application server is D2, then D1 and D2 satisfy the following relationship: D1 <D2。

[0237] In some other embodiments, it is not necessary to distinguish between the remote DN and the local DN. Therefore, in some embodiments, D1 may be equal to D2.

[0238] In some embodiments, the address information of application server #1 may include the IP address and port number #3 of application server #1; and the address information of application server #2 may include the IP address and / or port number #4 of application server #2. In other words, the address information of application server #1 may include both the IP address and port number #3 of application server #1, while the address information of application server #2 may include either or both the IP address or port number #4 of application server #2.

[0239] In other embodiments, the address information of application server #1 may include the IP address and / or port number #3 of application server #1; and the address information of application server #2 may include the IP address and port number #4 of application server #2. In other words, the address information of application server #2 may include both the IP address and port number #4 of application server #2, while the address information of application server #1 may include either or both the IP address or port number #3 of application server #1.

[0240] In other embodiments, the address information of application server #1 may include the IP address and / or port number #3 of application server #1; and the address information of application server #2 may include the IP address and / or port number #4 of application server #2. In other words, in this case, the address information of both application server #1 and application server #2 may include any one or both of their respective IP addresses or port numbers. Similarly, in other embodiments, the address information of application server #1 may include the IP address and port number #3 of application server #1, and the address information of application server #2 may include the IP address and port number #4 of application server #2.

[0241] In some embodiments, port number #3 is a fixed port number, and port number #4 is also a fixed port number. For example, in some embodiments, port number #3 and port number #4 may both be port numbers assigned by application server #2. In other embodiments, port number #3 and port number #4 may both be port numbers assigned by the fourth network element. In some embodiments, port number #3 and port number #4 may be terminal-related. For example, in some embodiments, application server #2 determines that it needs to send a data packet to application server #1 in response to a data packet from application server #1. This data packet is related to a service at terminal #1. In this case, application server #1 may assign two port numbers to terminal #1, namely, port number #3 and port number #4. Alternatively, application server #2 may instruct the fourth network element to assign two fixed sending port numbers to terminal #1, namely, port number #3 and port number #4.

[0242] In other embodiments, port number #3 or port number #4 is a fixed port number. In other words, one of port number #3 and port number #4 is a fixed port number, while the other can be a random port number. Similarly, the fixed port number can be terminal-dependent. For example, application server #1 can assign a fixed port number (e.g., port number #3) to terminal #1 when confirming that it needs to send a data packet to application server #2.

[0243] In other embodiments, the port number #3 and the port number #4 are both random port numbers.

[0244] In the embodiments of the present application, the event that triggers the fourth network element to send the address information of application server #1 and application server #2 to the fifth network element (hereinafter referred to as the "triggering event") is not limited. For example, in some embodiments, the triggering event may be the receipt of a data packet sent by terminal #1. For example, application server #1 receives a data packet from terminal #1 and then sends the data packet to application server #2 via tunnel #1. In this case, application server #2 may assign fixed port numbers (i.e., port numbers #3 and #4 mentioned above) to terminal #1 and instruct the fourth network element to send request #2 to the fifth network element. In other embodiments, the triggering event may be determined independently by application server #2. For example, upon determining that tunnel #1 is configured, application server #2 may instruct the fourth network element to send request #2 to the fifth network element. In the above embodiments, application server #1 instructs the fourth network element to send request #2 to the fifth network element. In other embodiments, the fourth network element may also determine independently that request #2 needs to be sent to the fifth network element. For example, in some embodiments, the fourth network element sends the request #2 to the fifth network element when it determines that the application server #2 obtains the data packet from the terminal #1 or the data packet related to the terminal #1 (for example, the data packet from the terminal #1 processed by the application server #1).

[0245] In the method shown in Figure 6, the first network element can send the address information of application server #1 to the second network element. For ease of description, this address information of application server #1 sent to the second network element can be referred to as application server #1 address information #1. In other words, application server #1 address information #1 includes the IP address and / or port number #1 of application server #1. Application server #1 address information #2 includes the IP address and / or port number #3 of application server #1.

[0246] In some embodiments, port number #1 may be the same as port number #3. In other words, the address information #1 of application server #1 and the address information #2 of application server #1 are the same. In this case, the address information of application server #1 included in request #2 can be considered to be either the address information #1 of application server #1 or the address information #2 of application server #1.

[0247] In other embodiments, port number #1 and port number #3 may be different. In this case, the address information #1 of application server #1 is different from the address information #2 of application server #1. In this case, the address information of application server #1 in request #2 may include: the address information #1 of application server #1 and the address information #2 of application server #1. In other words, the address information of application server #1 in request #2 may include: the IP address and / or port number #1 of application server #1; the address information of application server #1 in request #2 may also include the IP address and / or port number #3 of application server #1. As described above, when application server #1 sends a data packet to application server #2 through tunnel #1, the source IP address of the data packet is the IP address of application server #1, and the source port number of the data packet is port number #1. Therefore, application server #2 and the first network element can obtain the address information #1 of application server #1 through the data packet.

[0248] Similarly, in some embodiments, port number #2 may be the same as port number #4. In other embodiments, port number #2 may be different from port number #4.

[0249] The identity information #1 of the terminal #1 may be any one or more of the IP address of the terminal #1, the subscription permanent identifier (SUPI) of the terminal #1, or the generic public subscription identifier (GPSI) of the terminal #1.

[0250] Optionally, in some embodiments, the fourth network element may further send instruction information #4 to the fifth network element. Instruction information #4 is used to instruct the establishment of a tunnel between user plane function network element #3 and user plane function network element #4. In other words, in some embodiments, the fourth network element may send a display instruction information to the fifth network element, which is used to instruct the establishment of a tunnel between user plane function network element #3 and user plane function network element #4. User plane function network element #3 is a network element that can access application server #1, and user plane function network element #4 is a network element that can access application server #2. User plane function network element #3 and user plane function network element #4 may be network elements in a network that application server #1 and application server #2 do not belong to. The network may be a mobile communication network or a core network within a mobile communication network. Taking Figure 2 as an example, if application server #1 is AS211, user plane function network element #3 is PAS241; if application server #2 is AS221, user plane function network element #4 is PAS 242. In some embodiments, user plane function network element #3 and user plane function network element #1 in the embodiment shown in Figure 6 may be the same user plane function network element, or different user plane function network elements. In some embodiments, user plane function network element #4 and user plane function network element 2 in the embodiment shown in Figure 6 may be the same user plane function network element, or different user plane function network elements.

[0251] Optionally, in some embodiments, the fourth network element may send instruction information #5 to the fifth network element. The instruction information #5 is used to instruct the fifth network element to send the address information of the application server #1, the address information of the application server #2, and the identity information of the terminal #1 to the sixth network element.

[0252] The sixth network element may be a control network element. For example, the sixth network element may be used to generate and manage users, sessions, QoS processing policies, etc. Therefore, the sixth network element may be referred to as a control network element, a control policy network element, or a control function network element. In some embodiments, the sixth network element may be a PCF as shown in Figures 1 to 5.

[0253] Optionally, in some embodiments, the indication information #5 may also be used to instruct the fifth network element to obtain a mapping relationship, where the mapping relationship is a mapping relationship between the identity information of the terminal #1 and the address information of the application server #1.

[0254] In summary, the fourth network element can instruct the fifth network element to obtain the mapping relationship between the identity information of the terminal #1 and the address information of the application server #1 by displaying instructions, and instruct the fifth network element to send the address information of the application server #1, the address information of the application server #2 and the identity information of the terminal #1 to the sixth network element.

[0255] In other embodiments, the fourth network element may indicate the content indicated by indication information #5 using two indication information. For example, in some embodiments, the fourth network element may send indication information #5.1 and indication information #5.2 to the fifth network element. Indication information #5.1 is used to instruct the fifth network element to obtain the mapping relationship between the identity information of terminal #1 and the address information of application server #1; and indication information #5.2 is used to instruct the fifth network element to send the address information of application server #1, the address information of application server #2, and the identity information of terminal #1 to the sixth network element.

[0256] Optionally, in some other embodiments, the fourth network element may send instruction information #6 to the fifth network element. Instruction information #6 has all the functions of instruction information #4 and instruction information #5. In other words, instruction information #6 may indicate the following: instructing the establishment of a tunnel between user plane function network element #3 and user plane function network element #4, instructing the fifth network element to obtain the mapping relationship between the identity information of terminal #1 and the address information of application server #1, and instructing the fifth network element to send the address information of application server #1, the address information of application server #2, and the identity information of terminal #1 to the sixth network element.

[0257] Optionally, in some embodiments, the fourth network element may send any one of indication information #4, indication information #5, or indication information #6 to the fifth network element. In other embodiments, the fourth network element may send any multiple or all of indication information #4, indication information #5, or indication information #6 to the fifth network element.

[0258] Optionally, in some embodiments, all indication information sent by the third network element to the fourth network element may be carried by request #2. In other words, request #2 may also include any one or more of indication information #3, indication information #4, or indication information #5.

[0259] Optionally, in other embodiments, part or all of the indication information sent by the third network element to the fourth network element may also be carried by a single request. For example, indication information #3 may be carried by request #2, and indication information #4 may be carried by request #a.

[0260] Optionally, in some embodiments, the address information of application server #1 and the address information of application server #2 may be carried in different requests. For example, request #a includes the address information of application server #1, and request #b includes the address information of application server #2.

[0261] 702. The fifth network element obtains a mapping relationship between the identity information of the terminal #1 and the address information of the application server #1.

[0262] As described above, in step 602 of Figure 6 , the fifth network element establishes a mapping relationship between the identity information of the terminal #1 and the address information of the application server #1. In this case, the fifth network element can obtain this mapping relationship.

[0263] Accordingly, in some embodiments, the fifth network element may obtain the mapping relationship locally. In other embodiments, the fifth network element may obtain the mapping relationship from a network element with a storage function (eg, UDR).

[0264] Optionally, in some embodiments, the fifth network element may obtain the mapping relationship between the identity information of the terminal #1 and the address information of the application server #1 upon receiving the display indication. For example, the fifth network element obtains the mapping relationship between the identity information of the terminal #1 and the address information of the application server #1 upon receiving indication information #5 or indication information #6.

[0265] Optionally, in some embodiments, if the fifth network element does not receive a display indication (e.g., indication information #5 and indication information #6), then it can be considered that the fourth network element implicitly instructs the fifth network element to obtain the mapping relationship between the identity information of the terminal #1 and the address information of the application server #1. In other words, if the fourth network element sends the identity information #1 of the terminal #1, the address information of the application server #1, and the address information of the application server #2 to the fifth network element, it can be considered that the fourth network element instructs the fifth network element to obtain the mapping relationship between the identity information of the terminal #1 and the address information of the application server #1. In other words, if the fifth network element receives the identity information #1 of the terminal #1, the address information of the application server #1, and the address information of the application server #2, then the fifth network element obtains the mapping relationship between the identity information of the terminal #1 and the address information of the application server #1.

[0266] 703 : The fifth network element determines the identity information #1 of the terminal #1 according to the acquired mapping relationship and the identity information of the application server #1.

[0267] Optionally, in some embodiments, the mapping relationship may store the identity information #1 of the terminal #1 and the address information of the application server #1. In this case, the fifth network element may directly determine the identity information #1 of the terminal #1 based on the mapping relationship.

[0268] Optionally, in other embodiments, the mapping relationship may store the identity information #2 of terminal #1 and the address information of application server #1. The identity information #2 of terminal #1 includes the IP address of terminal #1 and / or the SUPI of terminal #1. In this case, the fifth network element may first determine the identity information #2 of terminal #1 based on the mapping relationship and the address information of application server #1, and then determine the identity information #1 of terminal #1 based on the identity information #2 of terminal #1.

[0269] This mapping relationship is established in the method shown in Figure 6 , so the address information of application server #1 stored in this mapping relationship is the address information of application server #1 mentioned in step 601. In other words, the address information of application server #1 stored in this mapping relationship is the address information #1 of application server #1 mentioned above. If the address information #1 of application server #1 is the same as the address information #2 of application server #1, request #2 can carry only the address information #1 or the address information #2 of application server #1 (or both). If the address information #1 of application server #1 is different from the address information #2 of application server #1, request #2 needs to include both the address information #1 and the address information #2 of application server #1. In other words, request #2 always carries the address information of application server #1 stored in the mapping relationship (i.e., the address information #1 of application server #1). Therefore, the fifth network element can determine the identity information #2 or identity information #1 of terminal #1 based on this mapping relationship and the address information #1 of application server #1.

[0270] 704. The fifth network element determines a sixth network element according to the identity information #1 of the terminal #1.

[0271] 705. The fifth network element sends the address information of the application server #1 and the address information of the application server #2 to the sixth network element. Correspondingly, the sixth network element receives the address information of the application server #1 and the address information of the application server #2.

[0272] Optionally, in some embodiments, the fifth network element may directly send the received #Request 2 containing the address information of the application server #1 and the address information of the application server #2 to the sixth network element. In other words, in this case, it can be considered that the fifth network element transparently transmits the #Request 2.

[0273] Optionally, in other embodiments, the fifth network element may re-determine a new request (e.g., request #2-1) based on request #2, where request #2-1 includes relevant information to be sent to the sixth network element. For example, request #2-1 includes the address information of application server #1 and the address information of application server #2.

[0274] Optionally, in some embodiments, the fifth network element may determine the identity information #2 of terminal #1 based on the identity information #1 of terminal #1. In this case, the fifth network element may also send the identity information #2 of terminal #1 to the sixth network element. Correspondingly, the sixth network element receives the identity information #2 of terminal #1.

[0275] Optionally, in some embodiments, the fifth network element may send the address information of the application server #1, the address information of the application server #2, and the identity information #2 of the terminal #1 to the sixth network element upon receiving the display instruction. For example, the fifth network element may send the address information of the application server #1, the address information of the application server #2, and the identity information #2 of the terminal #1 to the sixth network element upon receiving instruction information #5 or instruction information #6.

[0276] Optionally, in other embodiments, if the fifth network element does not receive the display indication (e.g., indication information #5 and indication information #6), then it can be considered that the fourth network element implicitly instructs the fifth network element to send the address information of application server #1, the address information of application server #2, and the identity information #2 of terminal #1 to the sixth network element. In other words, if the fourth network element sends request #2 to the fifth network element, or sends the address information of application server #1 and / or the address information of application server #2, then it can be considered that the fourth network element instructs the fifth network element to send the address information of application server #1, the address information of application server #2, and the identity information #2 of terminal #1 to the sixth network element. In other words, if the fifth network element receives request #2, or receives the address information of application server #1 and / or the address information of application server #2, then the fifth network element sends the address information of application server #1, the address information of application server #2, and the identity information #2 of terminal #1 to the sixth network element.

[0277] As described above, the fifth network element's sending of the terminal #1's identity information #2 to the sixth network element is optional. In some embodiments, the instruction information #5 and the instruction information #6 may also indicate that the address information of the application server #1 and the address information of the application server #2 are sent to the sixth network element. In other words, in this case, the instruction information #5 and the instruction information #6 may not necessarily indicate that the terminal #1's identity information #2 is sent to the sixth network element. Of course, in other embodiments, even if the instruction information #5 or the instruction information #6 indicates that the terminal #1's identity information #2 is sent to the sixth network element, the fifth network element may independently determine not to send the terminal #1's identity information #2 to the sixth network element.

[0278] As described above, in some embodiments, the fourth network element may further send an indication message (e.g., indication message #4 and indication message #6) to the fifth network element indicating the establishment of a tunnel between user plane function network element #3 and user plane function network element #4. When the fifth network element receives the indication message, the fifth network element may send an indication message to the sixth network element, where the indication message is used to instruct the establishment of a tunnel between user plane function network element #3 and user plane function network element #4. For example, if the fifth network element receives indication message #4, the fifth network element may directly forward the indication message #4 to the sixth network element. Alternatively, it may be considered that the fifth network element transparently transmits the indication message #4 to the sixth network element. For another example, if the fifth network element receives indication message #6, the fifth network element may determine a new indication message (which may be referred to as indication message #6.1). Indication message #6.1 is used to instruct the establishment of a tunnel between user plane function network element #3 and user plane function network element #4.

[0279] Optionally, in some embodiments, if the fifth network element does not receive instruction information (e.g., instruction information #4 or instruction information #6) explicitly instructing the establishment of a tunnel between user plane function network element #3 and user plane function network element #4, then the fourth network element may be deemed to have implicitly instructed the establishment of a tunnel between user plane function network element #3 and user plane function network element #4. In other words, if the fourth network element sends request #2, or sends the address information of application server #1 and / or the address information of application server #2 to the fifth network element, then the fourth network element may be deemed to have instructed the establishment of a tunnel between user plane function network element #3 and user plane function network element #4. In other words, if the fifth network element receives request #2, or receives the address information of application server #1 and / or the address information of application server #2, then the fifth network element sends an instruction information to the sixth network element, wherein the instruction information instructs the establishment of a tunnel between user plane function network element #3 and user plane function network element #4.

[0280] 706. The sixth network element determines session management network element #1.

[0281] Optionally, in some embodiments, the sixth network element may determine the session management network element #1 based on the address information of the application server #2.

[0282] Optionally, in some other embodiments, the sixth network element may determine the session management network element #1 based on the identity information #2 of the terminal #1.

[0283] In some embodiments, if the sixth network element obtains the identity information of the terminal, the sixth network element can independently determine whether to determine the session management network element based on the identity information of the terminal. In other words, if the sixth network element obtains the identity information #2 of terminal #1, the sixth network element can determine the session management network element based on the address information of application server #1, or it can determine the session management network element based on the identity information 2 of terminal #1.

[0284] In other embodiments, if the sixth network element obtains the identity information of the terminal, the sixth network element determines the session management network element based on the identity information of the terminal. In other words, if the sixth network element obtains the identity information #2 of the terminal #1, the sixth network element determines the session management network element based on the identity information #2 of the terminal #1; if the sixth network element does not obtain the identity information #2 of the terminal #1, the sixth network element may determine the session management network element based on the address information of the application server #1.

[0285] 707 : The sixth network element sends the address information of the application server # 1 and the address information of the application server # 2 to the session management network element # 1 .

[0286] Optionally, in some embodiments, the sixth network element may determine a rule related to the tunnel, and then send the rule to the session management network element #1.

[0287] Optionally, in some embodiments, the sixth network element may directly determine the rule based on the received information. In other words, the rule only includes the address information of the application server #1 and the address information of the application server #2 received by the sixth network element from the fifth network element.

[0288] Optionally, in other embodiments, the sixth network element may determine this rule based on the received information and other information. For example, in some embodiments, the sixth network element may receive identity information #2 of terminal #1. In this case, the sixth network element may also determine identity information #3 of terminal #1 based on identity information #2 of terminal #1, and then send identity information #3 of terminal #1 to session management network element #1. In this case, the rule includes the address information of application server #1, the address information of application server #2, and identity information #3 of terminal #1 determined by the sixth network element.

[0289] The identity information #3 of the terminal #1 may be any one or more of the IP address of the terminal #1, the SUPI of the terminal #1, or the PDU session ID of the terminal #1.

[0290] A session management network element (e.g., session management network element #1) is a network element that has session management functions. For example, the session management network element can manage the creation and deletion of PDU sessions, maintain PDU session contexts, and user plane forwarding channel information. For example, the session management network element can be an SMF in the system shown in Figures 1 to 5.

[0291] As described above, in some embodiments, the sixth network element may also receive a display instruction for instructing the establishment of a tunnel between user plane function network element #3 and user plane function network element #4. In this case, the sixth network element may forward the display instruction to the session management network element #1. Similarly, if the sixth network element does not receive the display instruction, the sixth network element may independently determine a display instruction for instructing the establishment of a tunnel between user plane function network element #3 and user plane function network element #4, and send the display instruction to the session management network element #1.

[0292] 708. The session management network element #1 may configure the user plane function network element #3 and / or the user plane function network element #4 to obtain a tunnel according to tunnel-related rules, wherein the rules include the address information of the application server #1 and the address information of the application server #2.

[0293] The session management network element #1 may determine or select the user plane function network element #3 based on the address information of the application server #1. The session management network element #1 may determine or select the user plane function network element #4 based on the address information of the application server #2.

[0294] In some embodiments, session management network element #1 can determine, based on the address of application server #1, that a user plane function network element controlled by session management network element #1 is a user plane function network element capable of accessing application server #1. In this case, session management network element #1 can determine that this user plane function network element is user plane function network element #3. Session management network element #1 can determine, based on the address of application server #1, that another user plane function network element controlled by session management network element #1 is a user plane function network element capable of accessing application server #2. In this case, session management network element #1 can determine that this user plane function network element is user plane function network element #4.

[0295] In other embodiments, session management network element #1 can determine, based on the address of application server #1, that a user plane function network element controlled by session management network element #1 is a user plane function network element that can access application server #1. In this case, session management network element #1 can determine that this user plane function network element is user plane function network element #3. Session management network element #1 can determine, based on the address of application server #1, that none of the user plane function network elements controlled by session management network element #1 can access application server #2. In this case, session management network element #1 can determine a session management network element (referred to as session management network element #2) that can control the user plane function network element that can access application server #2 and send the address information of application server #1 and application server #2 to session management network element #2.

[0296] When both user plane function network element #3 and user plane function network element #4 are controlled by session management network element #1, session management network element #1 can interact with user plane function network element #3 and / or user plane function network element #4 to configure user plane function network element #3 and / or user plane function network element #4 to obtain a tunnel. For example, session management network element #1 configures user plane function network element #4 by sending packet detection rule #4 to user plane function network element #4 to obtain the tunnel. Session management network element #1 can determine packet detection rule #4 and send packet detection rule #4 to user plane function network element #4. Packet detection rule #4 can include at least one of the address information of application server #1 or the address information of application server #2. For example, in some embodiments, packet detection rule #4 can include packet detection information #4, which includes packet filter set #4 and / or address information #4. Packet filter set #4 includes at least one of the address information of application server #1 or the address information of application server #2. The address information #4 includes at least one of the IP address or port number #1 of application server #1. Alternatively, the address information #4 includes at least one of the IP address or port number #4 of application server #2. Optionally, in some embodiments, session management network element #1 obtains the tunnel by sending packet detection rule #3 to user plane function network element #3 to configure user plane function network element #3. Session management network element #1 may determine packet detection rule #3 and send packet detection rule #3 to user plane function network element #3. The packet detection rule #3 may include at least one of the address information of application server #1 or the address information of application server #2. For example, in some embodiments, packet detection rule #3 may include packet detection information #3, which includes packet filter set #3 and / or address information #3. The packet filter set #3 includes at least one of the address information of application server #1 or the address information of application server #2. The address information #3 includes at least one of the IP address or port number #1 of application server #1. Alternatively, the address information #3 includes at least one of the IP address or port number #4 of the application server #2.

[0297] When user plane function network element #3 is controlled by session management network element #1 and user plane function network element #4 is controlled by session management network element #2, session management network element #1 can interact with user plane function network element #3 and / or session management network element #4 to configure user plane function network element #3 and / or user plane function network element #4 to obtain a tunnel. For example, session management network element #1 configures user plane function network element #1 by sending packet detection rule #4 to user plane function network element #4. Session management network element #1 can instruct session management network element #2 to send packet detection rule #4 to user plane function network element #4. For example, in some embodiments, session management network element #1 can instruct session management network element #2 to determine packet detection rule #4 and then send packet detection rule #4 to user plane function network element #4. In other words, in this case, packet detection rule #4 is determined by session management network element #2. In other embodiments, session management network element #1 can independently determine packet detection rule #4 and then send packet detection rule #4 to session management network element #2. Session management network element #2 then sends the obtained packet detection rule #4 to user plane function network element #4. Packet detection rule #4 may include at least one of the address information of application server #1 or the address information of application server #2. For example, in some embodiments, packet detection rule #4 may include packet detection information #4, which includes packet filter set #4 and / or address information #4. Packet filter set #4 includes at least one of the address information of application server #1 or the address information of application server #2. Address information #4 includes at least one of the IP address or port number #1 of application server #1. Alternatively, address information #4 includes at least one of the IP address or port number #4 of application server #2. Optionally, session management network element #1 configures user plane function network element #3 by sending packet detection rule #3 to user plane function network element #3 to obtain the tunnel. For example, in some embodiments, session management network element #1 may determine packet detection rule #3 and send packet detection rule #3 to user plane function network element #3. Packet detection rule #3 may include at least one of the address information of application server #1 or the address information of application server #2. For example, in some embodiments, packet detection rule #3 may include packet detection information #3, which includes packet filter set #3 and / or address information #3. Packet filter set #3 includes at least one of the address information of application server #1 or the address information of application server #2. Address information #3 includes at least one of the IP address or port number #1 of application server #1. Alternatively, address information #3 includes at least one of the IP address or port number #4 of application server #2.

[0298] Packet inspection rule #3 and packet inspection rule #4 can be used to inspect data packets from application server #2.

[0299] Corresponding to Table 1, packet filter set #3 and packet filter set #4 may be entries named “packet filter set” in Table 1, and address information #3 and address information #4 may be entries named “UE IP address” in Table 1.

[0300] If the network also includes a network element responsible for data packet forwarding and data offloading services (which may be referred to as an eighth network element), the session management network element #1 may determine packet detection information #6 and send the packet detection rule #6 to the eighth network element. For example, the eighth network element may be the ULCL in Figure 2 or Figure 3. The eighth network element may be the same network element as the seventh network element in Figure 6.

[0301] Packet detection rule #6 may include packet detection information #6, which is used to detect data packets from application server #2. Packet detection information #6 may include a packet filter set #6 and / or address information #6. Packet filter set #6 may include at least one of the address information of application server #1 or the address information of application server #2. Address information #6 may include at least one of the IP address or port number #1 of application server #1. Alternatively, address information #6 may include at least one of the IP address or port number of application server #2.

[0302] 709 , the session management network element # 1 may send tunnel confirmation information to the fourth network element, where the tunnel confirmation information is used to indicate that the tunnel between the user plane function network element # 3 and the user plane function network element # 4 has been configured.

[0303] For ease of description, in the following embodiments, the tunnel configured by the method shown in FIG. 7 may be referred to as tunnel #2.

[0304] If tunnel #2 is configured, application server #2 can send a data packet to application server #1 through tunnel #2. The source IP address of the data packet is application server #2's IP address, the source port number is port #4, the destination IP address is application server #1's IP address, and the destination port number is port #3.

[0305] After receiving the data packet from application server #2, user plane function network element #4 can match the data packet based on packet detection rule #4. If the data packet matches packet detection rule #4, it will perform the corresponding forwarding action and send the data packet to user plane function network element #3 or the eighth network element.

[0306] Similarly, if packet inspection rule #3 is configured for user plane function network element #3, user plane function network element #3 can match the received data packet based on packet inspection rule #3. If the data packet matches packet inspection rule #3, it will perform the corresponding forwarding action and send the data packet to application server #1. If packet inspection rule #3 is not configured for user plane function network element #3, user plane function network element #3 can send the data packet to application server #1 based on the outer header of the encapsulated data packet.

[0307] If the system includes an eighth network element and a packet detection rule is configured for the eighth network element (i.e., the packet detection rule #6 mentioned above), the eighth network element can receive a data packet from the user plane function network element #4, match the received data packet based on the packet detection rule #6, and if the data packet matches the packet detection rule #6, perform the corresponding forwarding action and send the data packet to the user plane function network element #3. Similarly, if no packet detection rule is configured for the eighth network element, the eighth network element can send the data packet to the user plane function network element #3 based on the outer header.

[0308] FIG8 is a schematic flowchart of a communication method provided according to an embodiment of the present application.

[0309] 801. A first network element sends a request #1 to a second network element. Accordingly, the second network element receives the request #1. The request #1 includes the address information of the application server #1 and the address information of the application server #2.

[0310] In some embodiments, the address information of the application server #1 may include the IP address and / or port number #1 of the application server #1.

[0311] In some embodiments, the address information of the application server #2 may include the IP address and / or port number #2 of the application server #2.

[0312] In the embodiment of the present application, there is no limitation on the event that triggers the first network element to send the address information of application server #1 and the address information of application server #2 to the second network element (hereinafter referred to as "trigger event").

[0313] For a detailed introduction to the first network element, the second network element, application server #1, application server #2, the address information of application server #1, the address information of application server #2, and the triggering event, please refer to the method shown in Figure 6. For the sake of brevity, it will not be repeated here.

[0314] Optionally, in some embodiments, the first network element may further send indication information #1 to the second network element. The function of indication information #1 is the same as that of indication information #1 in the method shown in FIG6 , and will not be described here for the sake of brevity.

[0315] Optionally, in some embodiments, the first network element may send indication information #2 to the second network element, wherein the indication information #2 is used to instruct the second network element to send the address information of the application server #1 and the address information of the application server #2 to a third network element.

[0316] The third network element may be a control network element. For example, the third network element may be used to generate and manage users, sessions, QoS processing policies, etc. Therefore, the third network element may be referred to as a control network element, a control policy network element, or a control function network element. In some embodiments, the third network element may be a PCF as shown in Figures 1 to 5.

[0317] In summary, the first network element may instruct the second network element to send the address information of the application server #1 and the address information of the application server #2 to the third network element by displaying an instruction.

[0318] Optionally, in other embodiments, the first network element may send instruction information #3 to the second network element. Instruction information #3 has all the functions of instruction information #1 and instruction information #2. In other words, instruction information #3 may indicate the following: instructing to establish a tunnel between user plane function network element #1 and user plane function network element #2, and instructing the second network element to send the address information of application server #1 and the address information of application server #2 to a third network element.

[0319] Optionally, in some embodiments, the first network element may send any one of indication information #1, indication information #2, or indication information #3 to the second network element. In other embodiments, the first network element may send any multiple or all of indication information #1, indication information #2, or indication information #3 to the second network element.

[0320] Optionally, in some embodiments, all indication information sent by the first network element to the second network element may be carried by request #1. In other words, request #1 may also include any one or more of indication information #1, indication information #2, or indication information #3.

[0321] Optionally, in other embodiments, part or all of the indication information sent by the first network element to the second network element may also be carried by a single request. For example, indication information #1 may be carried by request #1, and indication information #2 may be carried by request #a.

[0322] Optionally, in some embodiments, the address information of application server #1, the address information of application server #2, and the identity information #1 of terminal #1 may also be carried in different requests. For example, request #a includes the address information of application server #1, and request #b includes the address information of application server #2.

[0323] 802. The second network element determines a third network element.

[0324] 803. The second network element sends the address information of the application server #1 and the address information of the application server #2 to the third network element. Correspondingly, the third network element receives the address information of the application server #1 and the address information of the application server #2.

[0325] Optionally, in some embodiments, the second network element may directly send the received #Request 1 containing the address information of the application server #1 and the address information of the application server #2 to the third network element. In other words, in this case, it can be considered that the second network element transparently transmits the request #1.

[0326] Optionally, in other embodiments, the second network element may re-determine a new request (e.g., request #1-1) based on request #1, where request #1-1 includes relevant information to be sent to the third network element. For example, request #1-1 includes the address information of application server #1 and the address information of application server #2.

[0327] Optionally, in some embodiments, the second network element may send the address information of the application server #1 and the address information of the application server #2 to the third network element upon receiving the display indication. For example, the second network element may send the address information of the application server #1 and the address information of the application server #2 to the third network element upon receiving indication information #2 or indication information #3.

[0328] Optionally, in some other embodiments, if the second network element does not receive the explicit indication (e.g., the indication information #2 and the indication information #3), then it can be considered that the first network element implicitly instructs the second network element to send the address information of the application server #1 and the address information #2 of the application server #2 to the third network element. In other words, if the first network element sends the address information of the application server #1 and the address information of the application server #2 to the second network element, it can be considered that the first network element instructs the second network element to send the address information of the application server #1 and the address information of the application server #2 to the third network element. In other words, if the second network element receives the address information of the application server #1 and the address information of the application server #2, then the second network element sends the address information of the application server #1 and the address information of the application server #2 to the third network element.

[0329] As described above, in some embodiments, the first network element may further send an indication message (e.g., indication message #1 and indication message #3) to the second network element indicating the establishment of a tunnel between user plane function network element #1 and user plane function network element #2. When the second network element receives the indication message, the second network element may send an indication message to the third network element, where the indication message is used to instruct the establishment of a tunnel between user plane function network element #1 and user plane function network element #2. For example, if the second network element receives indication message #1, the second network element may directly forward the indication message #1 to the third network element. Alternatively, it may be considered that the second network element transparently transmits the indication message #1 to the third network element. For another example, if the second network element receives indication message #3, the second network element may determine a new indication message (which may be referred to as indication message #3.1). Indication message #3.1 is used to instruct the establishment of a tunnel between user plane function network element #1 and user plane function network element #2.

[0330] Optionally, in some embodiments, if the second network element does not receive indication information (e.g., indication information #1 or indication information #3) that explicitly instructs the establishment of a tunnel between user plane function network element #1 and user plane function network element #2, then it can be considered that the first network element implicitly instructs the establishment of a tunnel between user plane function network element #1 and user plane function network element #2. In other words, if the first network element sends request #1 to the second network element, or sends the address information of application server #1 and / or the address information of application server #2, then it can be considered that the first network element instructs the establishment of a tunnel between user plane function network element #1 and user plane function network element #2. In other words, if the second network element receives request #1, or receives the address information of application server #1 and / or the address information of application server #2, then the second network element sends an indication information to the third network element, wherein the indication information instructs the establishment of a tunnel between user plane function network element #1 and user plane function network element #2.

[0331] 804. The third network element determines session management network element #1.

[0332] The third network element may determine the session management network element #1 according to the address information of the application server #1.

[0333] 805 , the third network element sends the address information of the application server #1 and the address information of the application server #2 to the session management network element #1.

[0334] Optionally, in some embodiments, the third network element determines a rule related to the tunnel, and then sends the rule to the session management network element #1.

[0335] Optionally, in some embodiments, the third network element may directly determine the rule based on the received information. In other words, the rule only includes the address information of the application server #1 and the address information of the application server #2 received by the third network element from the second network element.

[0336] Optionally, in other embodiments, the third network element may determine this rule based on the received information and other information. For example, in some embodiments, the third network element may receive identity information #2 of terminal #1. In this case, the third network element may also determine identity information #3 of terminal #1 based on identity information #2 of terminal #1, and then send identity information #3 of terminal #1 to session management network element #1. In this case, the rule includes the address information of application server #1, the address information of application server #2, and identity information #3 of terminal #1 determined by the third network element.

[0337] A session management network element (e.g., session management network element #1) is a network element that has session management functions. For example, the session management network element can manage the creation and deletion of PDU sessions, maintain PDU session contexts, and user plane forwarding channel information. For example, the session management network element can be an SMF in the system shown in Figures 1 to 5.

[0338] As described above, in some embodiments, the third network element may also receive a display instruction for instructing the establishment of a tunnel between user plane function network element #1 and user plane function network element #2. In this case, the third network element may forward the display instruction to the session management network element #1. Similarly, if the third network element does not receive the display instruction, the third network element may independently determine a display instruction for instructing the establishment of a tunnel between user plane function network element #1 and user plane function network element #2, and send the display instruction to the session management network element #1.

[0339] 806. The session management network element #1 may configure a tunnel for the user plane function network element #1 and / or the user plane function network element #2 according to tunnel-related rules, wherein the rules include the address information of the application server #1 and the address information of the application server #2.

[0340] The session management network element #1 can determine the user plane function network element #1 based on the address information of the application server #1. The session management network element #1 can determine the user plane function network element #2 based on the address information of the application server #2.

[0341] In some embodiments, session management network element #1 can determine, based on the address of application server #1, that a user plane function network element controlled by session management network element #1 is a user plane function network element capable of accessing application server #1. In this case, session management network element #1 can determine that this user plane function network element is user plane function network element #1. Session management network element #1 can determine, based on the address of application server #2, that another user plane function network element controlled by session management network element #1 is a user plane function network element capable of accessing application server #2. In this case, session management network element #1 can determine that this user plane function network element is user plane function network element #2.

[0342] In other embodiments, session management network element #1 can determine, based on the address of application server #1, that a user plane function network element controlled by session management network element #1 is a user plane function network element that can access application server #1. In this case, session management network element #1 can determine that this user plane function network element is user plane function network element #1. Session management network element #1 can determine, based on the address of application server #1, that none of the user plane function network elements controlled by session management network element #1 can access application server #2. In this case, session management network element #1 can determine a session management network element (which can be referred to as session management network element #2) that can control the user plane function network element that can access application server #2, and send the address information of application server #1 and application server #2 to session management network element #2.

[0343] When both user plane function network element #1 and user plane function network element #2 are controlled by session management network element #1, session management network element #1 may interact with user plane function network element #1 and / or user plane function network element #2 to configure a tunnel for user plane function network element #1 and / or user plane function network element #2. For example, session management network element #1 configures user plane function network element #1 by sending packet detection rule #1 to user plane function network element #1 to obtain the tunnel. Session management network element #1 may determine packet detection rule #1 and send packet detection rule #1 to user plane function network element #1. Packet detection rule #1 may include at least one of the address information of application server #1 or the address information of application server #2. For example, in some embodiments, packet detection rule #1 may include packet detection information #1, which includes packet filter set #1 and / or address information #1. Packet filter set #1 includes at least one of the address information of application server #1 or the address information of application server #2. The address information #1 includes at least one of the IP address or port number #1 of the application server #1. Optionally, in some embodiments, session management network element #1 obtains the tunnel by sending packet detection rule #2 to user plane function network element #2 to configure user plane function network element #2. Session management network element #1 may determine packet detection rule #2 and send packet detection rule #2 to user plane function network element #2. The packet detection rule #2 may include at least one of the address information of application server #1 or the address information of application server #2. For example, in some embodiments, packet detection rule #2 may include packet detection information #2, which includes packet filter set #2 and / or address information #2. The packet filter set #2 includes at least one of the address information of application server #1 or the address information of application server #2. The address information #2 includes at least one of the IP address or port number #1 of application server #1.

[0344] When user plane function network element #1 is controlled by session management network element #1 and user plane function network element #2 is controlled by session management network element #2, session management network element #1 may interact with user plane function network element #1 and / or session management network element #2 to configure a tunnel for user plane function network element #1 and / or user plane function network element #2. For example, session management network element #1 configures user plane function network element #1 by sending packet detection rule #1 to user plane function network element #1 to obtain the tunnel. Session management network element #1 may determine packet detection rule #1 and send packet detection rule #1 to user plane function network element #1. Packet detection rule #1 may include at least one of the address information of application server #1 or the address information of application server #2. For example, in some embodiments, packet detection rule #1 may include packet detection information #1, which includes packet filter set #1 and / or address information #1. Packet filter set #1 includes at least one of the address information of application server #1 or the address information of application server #2. The address information #1 includes at least one of the IP address or port number #1 of the application server #1. Optionally, session management network element #1 configures user plane function network element #2 by sending packet detection rule #2 to user plane function network element #2 to obtain the tunnel. For example, in some embodiments, session management network element #1 may also instruct session management network element #2 to send packet detection rule #2 to user plane function network element #2. For example, in some embodiments, session management network element #1 may instruct session management network element #2 to determine packet detection rule #2 and then send the packet detection rule #2 to user plane function network element #2. In other words, in this case, packet detection rule #2 is determined by session management network element #2. In other embodiments, session management network element #1 may independently determine packet detection rule #2 and then send packet detection rule #2 to session management network element #2. Session management network element #2 then sends the obtained packet detection rule #2 to user plane function network element #2. Packet detection rule #2 may include at least one of the address information of application server #1 or the address information of application server #2. For example, in some embodiments, packet detection rule #2 may include packet detection information #2, which includes packet filter set #2 and / or address information #2. Packet filter set #2 includes at least one of the address information of application server #1 or the address information of application server #2. Address information #2 includes at least one of the IP address of application server #1 or port number #1.

[0345] Packet inspection rule #1 and packet inspection rule #2 can be used to inspect data packets from application server #1.

[0346] Corresponding to Table 1, packet filter set #1 and packet filter set #2 may be entries named “packet filter set” in Table 1, and address information #1 and address information #2 may be entries named “UE IP address” in Table 1.

[0347] If the network also includes a network element responsible for data packet forwarding and data offloading services (which may be referred to as a seventh network element), the session management network element #1 may determine packet detection information #5 and send the packet detection rule #5 to the seventh network element. For example, the seventh network element may be the ULCL in Figure 2 or Figure 3.

[0348] Packet detection rule #5 may include packet detection information #5, which is used to detect data packets from application server #1. Packet detection information #5 may include a packet filter set #5 and / or address information #5. Packet filter set #5 may include at least one of the address information of application server #1 or the address information of application server #2. Address information #5 includes at least one of the IP address or port number #1 of application server #1. Similarly, packet filter set #5 may be the entry named "Packet Filter Set" in Table 1, and address information #5 may be the entry named "UE IP Address" in Table 1.

[0349] 807 , the session management network element #1 may send tunnel confirmation information to the first network element, where the tunnel confirmation information is used to indicate that the tunnel between the user plane function network element #1 and the user plane function network element #2 has been configured.

[0350] For ease of description, in the following embodiments, the tunnel configured by the method shown in FIG. 8 may be referred to as tunnel #3.

[0351] When tunnel #3 is configured, application server #1 can send a data packet to application server #2 through tunnel #3. The source IP address of the data packet is application server #1's IP address, the source port number is port #1, the destination IP address is application server #2's IP address, and the destination port number is port #2.

[0352] After receiving the data packet from application server #1, user plane function network element #1 can match the data packet based on packet detection rule #1. If the data packet matches packet detection rule #1, it will perform the corresponding forwarding action and send the data packet to user plane function network element #2 or the seventh network element.

[0353] Similarly, if packet inspection rule #2 is configured for user plane function network element #2, user plane function network element #2 can match the received data packet based on packet inspection rule #2. If the data packet matches packet inspection rule #2, user plane function network element #2 performs the corresponding forwarding action and sends the data packet to application server #2. If packet inspection rule #2 is not configured for user plane function network element #2, user plane function network element #2 can send the data packet to application server #2 based on the outer header of the encapsulated data packet.

[0354] If the system includes a seventh network element and a packet detection rule (i.e., packet detection rule #5 mentioned above) is configured for the seventh network element, the seventh network element can receive a data packet from user plane function network element #1, match the received data packet based on packet detection rule #5, and if the data packet matches packet detection rule #5, perform the corresponding forwarding action and send the data packet to user plane function network element #2. Similarly, if no packet detection rule is configured for the seventh network element, the seventh network element can send the data packet to user plane function network element #2 based on the outer header.

[0355] Application server #2 can also start a similar process to build a tunnel to send data packets to application server #1. The following describes the process of determining this tunnel with reference to FIG9.

[0356] FIG9 is a schematic flowchart of another communication method provided according to an embodiment of the present application.

[0357] 901. The fourth network element sends a request #2 to the fifth network element. Correspondingly, the fifth network element receives the request #2. The request #2 includes the address information of the application server #1 and the address information of the application server #2.

[0358] In some embodiments, the address information of the application server #1 may include the IP address and / or port number #3 of the application server #1.

[0359] In some embodiments, the address information of the application server #2 may include the IP address and / or port number #4 of the application server #2.

[0360] In the embodiment of the present application, there is no limitation on the event that triggers the fourth network element to send the address information of application server #1 and the address information of application server #2 to the fifth network element (hereinafter referred to as "trigger event").

[0361] For a detailed introduction to the fourth network element, the fifth network element, application server #1, application server #2, the address information of application server #1, the address information of application server #2, and the triggering event, please refer to the method shown in Figure 7. For the sake of brevity, it will not be repeated here.

[0362] Optionally, in some embodiments, the fourth network element may further send indication information #4 to the fifth network element. The indication information #4 has the same function as the indication information #4 in the method shown in FIG7 , and will not be described again for the sake of brevity.

[0363] Optionally, in some embodiments, the fourth network element may send instruction information #5 to the fifth network element. The instruction information #5 is used to instruct the fifth network element to send the address information of the application server #1 and the address information of the application server #2 to the sixth network element.

[0364] The sixth network element may be a control network element. For example, the sixth network element may be used to generate and manage users, sessions, QoS processing policies, etc. Therefore, the sixth network element may be referred to as a control network element, a control policy network element, or a control function network element. In some embodiments, the sixth network element may be a PCF as shown in Figures 1 to 5.

[0365] Optionally, in some other embodiments, the fourth network element may send instruction information #6 to the fifth network element. Instruction information #6 has all the functions of instruction information #4 and instruction information #5. In other words, instruction information #6 may indicate the following: instructing to establish a tunnel between user plane function network element #3 and user plane function network element #4, and instructing the fifth network element to send the address information of application server #1 and the address information of application server #2 to the sixth network element.

[0366] Optionally, in some embodiments, the fourth network element may send any one of indication information #4, indication information #5, or indication information #6 to the fifth network element. In other embodiments, the fourth network element may send any multiple or all of indication information #4, indication information #5, or indication information #6 to the fifth network element.

[0367] Optionally, in some embodiments, all indication information sent by the third network element to the fourth network element may be carried by request #2. In other words, request #2 may also include any one or more of indication information #3, indication information #4, or indication information #5.

[0368] Optionally, in other embodiments, part or all of the indication information sent by the third network element to the fourth network element may also be carried by a single request. For example, indication information #3 may be carried by request #2, and indication information #4 may be carried by request #a.

[0369] Optionally, in some embodiments, the address information of application server #1 and the address information of application server #2 may be carried in different requests. For example, request #a includes the address information of application server #1, and request #b includes the address information of application server #2.

[0370] 902. The fifth network element determines a sixth network element.

[0371] 903. The fifth network element sends the address information of the application server #1 and the address information of the application server #2 to the sixth network element. Correspondingly, the sixth network element receives the address information of the application server #1 and the address information of the application server #2.

[0372] Optionally, in some embodiments, the fifth network element may directly send the received #Request 2 containing the address information of the application server #1 and the address information of the application server #2 to the third network element. In other words, in this case, it can be considered that the fifth network element transparently transmits the #Request 2.

[0373] Optionally, in other embodiments, the fifth network element may re-determine a new request (e.g., request #2-1) based on request #2, where request #2-1 includes relevant information to be sent to the third network element. For example, request #2-1 includes the address information of application server #1 and the address information of application server #2.

[0374] Optionally, in some embodiments, the fifth network element may send the address information of application server #1 and the address information #2 of application server #2 to the sixth network element upon receiving the display indication. For example, the fifth network element may send the address information of application server #1 and the address information #2 of application server #2 to the sixth network element upon receiving indication information #5 or indication information #6.

[0375] Optionally, in some other embodiments, if the fifth network element does not receive the explicit indication (e.g., indication information #5 and indication information #6), then it can be considered that the fourth network element implicitly instructs the fifth network element to send the address information of application server #1 and the address information #2 of application server #2 to the sixth network element. In other words, if the fourth network element sends request #2 to the fifth network element, or sends the address information of application server #1 and / or the address information of application server #2, then it can be considered that the fourth network element instructs the fifth network element to send the address information of application server #1 and the address information #2 of application server #2 to the sixth network element. In other words, if the fifth network element receives request #2, or receives the address information of application server #1 and / or the address information of application server #2, then the fifth network element sends the address information of application server #1 and the address information #2 of application server #2 to the sixth network element.

[0376] As described above, in some embodiments, the fourth network element may further send an indication message (e.g., indication message #4 and indication message #6) to the fifth network element indicating the establishment of a tunnel between user plane function network element #3 and user plane function network element #4. When the fifth network element receives the indication message, the fifth network element may send an indication message to the sixth network element, where the indication message is used to instruct the establishment of a tunnel between user plane function network element #3 and user plane function network element #4. For example, if the fifth network element receives indication message #4, the fifth network element may directly forward the indication message #4 to the sixth network element. Alternatively, it may be considered that the fifth network element transparently transmits the indication message #4 to the sixth network element. For another example, if the fifth network element receives indication message #6, the fifth network element may determine a new indication message (which may be referred to as indication message #6.1). Indication message #6.1 is used to instruct the establishment of a tunnel between user plane function network element #3 and user plane function network element #4.

[0377] Optionally, in some embodiments, if the fifth network element does not receive instruction information (e.g., instruction information #4 or instruction information #6) explicitly instructing the establishment of a tunnel between user plane function network element #3 and user plane function network element #4, then the fourth network element may be deemed to have implicitly instructed the establishment of a tunnel between user plane function network element #3 and user plane function network element #4. In other words, if the fourth network element sends request #2 to the fifth network element, or sends the address information of application server #1 and / or the address information of application server #2, then the fourth network element may be deemed to have instructed the establishment of a tunnel between user plane function network element #3 and user plane function network element #4. In other words, if the fifth network element receives request #2, or receives the address information of application server #1 and / or the address information of application server #2, then the fifth network element sends an instruction information to the sixth network element, wherein the instruction information instructs the establishment of a tunnel between user plane function network element #3 and user plane function network element #4.

[0378] 904. The sixth network element determines session management network element #1.

[0379] Optionally, in some embodiments, the sixth network element may determine the session management network element #1 based on the address information of the application server #2.

[0380] 905 : The sixth network element sends the address information of the application server #1 and the address information of the application server #2 to the session management network element #1.

[0381] Optionally, in some embodiments, the sixth network element may determine a rule related to the tunnel, and then send the rule to the session management network element #1.

[0382] Optionally, in some embodiments, the sixth network element may directly determine the rule based on the received information. In other words, the rule only includes the address information of the application server #1 and the address information of the application server #2 received by the sixth network element from the fifth network element.

[0383] Optionally, in other embodiments, the sixth network element may determine this rule based on the received information and other information. For example, in some embodiments, the sixth network element may receive identity information #2 of terminal #1. In this case, the sixth network element may also determine identity information #3 of terminal #1 based on identity information #2 of terminal #1, and then send identity information #3 of terminal #1 to session management network element #1. In this case, the rule includes the address information of application server #1, the address information of application server #2, and identity information #3 of terminal #1 determined by the sixth network element.

[0384] A session management network element (e.g., session management network element #1) is a network element that has session management functions. For example, the session management network element can manage the creation and deletion of PDU sessions, maintain PDU session contexts, and user plane forwarding channel information. For example, the session management network element can be an SMF in the system shown in Figures 1 to 5.

[0385] As described above, in some embodiments, the sixth network element may also receive a display instruction for instructing the establishment of a tunnel between user plane function network element #3 and user plane function network element #4. In this case, the sixth network element may forward the display instruction to the session management network element #1. Similarly, if the sixth network element does not receive the display instruction, the sixth network element may independently determine a display instruction for instructing the establishment of a tunnel between user plane function network element #3 and user plane function network element #4, and send the display instruction to the session management network element #1.

[0386] 906. The session management network element #1 may configure the user plane function network element #3 and / or the user plane function network element #4 to obtain a tunnel according to tunnel-related rules, wherein the rules include the address information of the application server #1 and the address information of the application server #2.

[0387] The session management network element #1 may determine or select the user plane function network element #3 based on the address information of the application server #1. The session management network element #1 may determine or select the user plane function network element #4 based on the address information of the application server #2.

[0388] In some embodiments, session management network element #1 can determine, based on the address of application server #1, that a user plane function network element controlled by session management network element #1 is a user plane function network element capable of accessing application server #1. In this case, session management network element #1 can determine that this user plane function network element is user plane function network element #3. Session management network element #1 can determine, based on the address of application server #1, that another user plane function network element controlled by session management network element #1 is a user plane function network element capable of accessing application server #2. In this case, session management network element #1 can determine that this user plane function network element is user plane function network element #4.

[0389] In other embodiments, session management network element #1 can determine, based on the address of application server #1, that a user plane function network element controlled by session management network element #1 is a user plane function network element that can access application server #1. In this case, session management network element #1 can determine that this user plane function network element is user plane function network element #3. Session management network element #1 can determine, based on the address of application server #1, that none of the user plane function network elements controlled by session management network element #1 can access application server #2. In this case, session management network element #1 can determine a session management network element (referred to as session management network element #2) that can control the user plane function network element that can access application server #2 and send the address information of application server #1 and application server #2 to session management network element #2.

[0390] When both user plane function network element #3 and user plane function network element #4 are controlled by session management network element #1, session management network element #1 can interact with user plane function network element #3 and / or user plane function network element #4 to configure user plane function network element #3 and / or user plane function network element #4 to obtain a tunnel. For example, session management network element #1 configures user plane function network element #4 by sending packet detection rule #4 to user plane function network element #4 to obtain the tunnel. Session management network element #1 can determine packet detection rule #4 and send packet detection rule #4 to user plane function network element #4. Packet detection rule #4 can include at least one of the address information of application server #1 or the address information of application server #2. For example, in some embodiments, packet detection rule #4 can include packet detection information #4, which includes packet filter set #4 and / or address information #4. Packet filter set #4 includes at least one of the address information of application server #1 or the address information of application server #2. The address information #4 includes at least one of the IP address or port number #1 of application server #1. Alternatively, the address information #4 includes at least one of the IP address or port number #4 of application server #2. Optionally, in some embodiments, session management network element #1 obtains the tunnel by sending packet detection rule #3 to user plane function network element #3 to configure user plane function network element #3. Session management network element #1 may determine packet detection rule #3 and send packet detection rule #3 to user plane function network element #3. The packet detection rule #3 may include at least one of the address information of application server #1 or the address information of application server #2. For example, in some embodiments, packet detection rule #3 may include packet detection information #3, which includes packet filter set #3 and / or address information #3. The packet filter set #3 includes at least one of the address information of application server #1 or the address information of application server #2. The address information #3 includes at least one of the IP address or port number #1 of application server #1. Alternatively, the address information #3 includes at least one of the IP address or port number #4 of the application server #2.

[0391] When user plane function network element #3 is controlled by session management network element #1 and user plane function network element #4 is controlled by session management network element #2, session management network element #1 can interact with user plane function network element #3 and / or session management network element #4 to configure user plane function network element #3 and / or user plane function network element #4 to obtain a tunnel. For example, session management network element #1 configures user plane function network element #1 by sending packet detection rule #4 to user plane function network element #4. Session management network element #1 can instruct session management network element #2 to send packet detection rule #4 to user plane function network element #4. For example, in some embodiments, session management network element #1 can instruct session management network element #2 to determine packet detection rule #4 and then send packet detection rule #4 to user plane function network element #4. In other words, in this case, packet detection rule #4 is determined by session management network element #2. In other embodiments, session management network element #1 can independently determine packet detection rule #4 and then send packet detection rule #4 to session management network element #2. Session management network element #2 then sends the obtained packet detection rule #4 to user plane function network element #4. Packet detection rule #4 may include at least one of the address information of application server #1 or the address information of application server #2. For example, in some embodiments, packet detection rule #4 may include packet detection information #4, which includes packet filter set #4 and / or address information #4. Packet filter set #4 includes at least one of the address information of application server #1 or the address information of application server #2. Address information #4 includes at least one of the IP address or port number #1 of application server #1. Alternatively, address information #4 includes at least one of the IP address or port number #4 of application server #2. Optionally, session management network element #1 configures user plane function network element #3 by sending packet detection rule #3 to user plane function network element #3 to obtain the tunnel. For example, in some embodiments, session management network element #1 may determine packet detection rule #3 and send packet detection rule #3 to user plane function network element #3. Packet detection rule #3 may include at least one of the address information of application server #1 or the address information of application server #2. For example, in some embodiments, packet detection rule #3 may include packet detection information #3, which includes packet filter set #3 and / or address information #3. Packet filter set #3 includes at least one of the address information of application server #1 or the address information of application server #2. Address information #3 includes at least one of the IP address or port number #1 of application server #1. Alternatively, address information #3 includes at least one of the IP address or port number #4 of application server #2.

[0392] Packet inspection rule #3 and packet inspection rule #4 can be used to inspect data packets from application server #2.

[0393] Corresponding to Table 1, packet filter set #3 and packet filter set #4 may be entries named “packet filter set” in Table 1, and address information #3 and address information #4 may be entries named “UE IP address” in Table 1.

[0394] If the network also includes a network element responsible for data packet forwarding and data offloading services (which may be referred to as an eighth network element), the session management network element #1 may determine packet detection information #6 and send the packet detection rule #6 to the eighth network element. For example, the eighth network element may be the ULCL in Figure 2 or Figure 3. The eighth network element may be the same network element as the seventh network element in Figure 8.

[0395] Packet detection rule #6 may include packet detection information #6, which is used to detect data packets from application server #2. Packet detection information #6 may include a packet filter set #6 and / or address information #6. Packet filter set #6 may include at least one of the address information of application server #1 or the address information of application server #2. Address information #6 may include at least one of the IP address or port number #1 of application server #1. Alternatively, address information #6 may include at least one of the IP address or port number of application server #2.

[0396] 907 , the session management network element # 1 may send tunnel confirmation information to the fourth network element, where the tunnel confirmation information is used to indicate that the tunnel between the user plane function network element # 3 and the user plane function network element # 4 has been configured.

[0397] For ease of description, in the following embodiments, the tunnel configured by the method shown in FIG. 7 may be referred to as tunnel #4.

[0398] When tunnel #4 is configured, application server #2 can send a data packet to application server #1 through tunnel #4. The source IP address of the data packet is application server #2's IP address, the source port number is port #4, the destination IP address is application server #1's IP address, and the destination port number is port #3.

[0399] After receiving the data packet from application server #2, user plane function network element #4 can match the data packet based on packet detection rule #4. If the data packet matches packet detection rule #4, it will perform the corresponding forwarding action and send the data packet to user plane function network element #3 or the eighth network element.

[0400] Similarly, if packet inspection rule #3 is configured for user plane function network element #3, user plane function network element #3 can match the received data packet based on packet inspection rule #3. If the data packet matches packet inspection rule #3, it will perform the corresponding forwarding action and send the data packet to application server #1. If packet inspection rule #3 is not configured for user plane function network element #3, user plane function network element #3 can send the data packet to application server #1 based on the outer header of the encapsulated data packet.

[0401] If the system includes an eighth network element and a packet detection rule is configured for the eighth network element (i.e., the packet detection rule #6 mentioned above), the eighth network element can receive a data packet from the user plane function network element #4, match the received data packet based on the packet detection rule #6, and if the data packet matches the packet detection rule #6, perform the corresponding forwarding action and send the data packet to the user plane function network element #3. Similarly, if no packet detection rule is configured for the eighth network element, the eighth network element can send the data packet to the user plane function network element #3 based on the outer header.

[0402] FIG10 is a schematic flowchart of a communication method provided according to an embodiment of the present application.

[0403] 1001. A first network element sends a request #1 to a second network element. In response, the second network element receives the request #1. The request #1 includes the address information of application server #1, the address information of application server #2, and the identity information #1 of terminal #1.

[0404] In some embodiments, the address information of the application server #1 may include the IP address and / or port number #1 of the application server #1.

[0405] In some embodiments, the address information of the application server #2 may include the IP address and / or port number #2 of the application server #2.

[0406] In the embodiment of the present application, there is no limitation on the event that triggers the first network element to send the address information of application server #1 and the address information of application server #2 to the second network element (hereinafter referred to as "trigger event").

[0407] For a detailed introduction to the first network element, the second network element, application server #1, application server #2, the address information of application server #1, the address information of application server #2, the triggering event, and the identity information #1 of terminal #1, please refer to the method shown in Figure 6. For the sake of brevity, it will not be repeated here.

[0408] Optionally, in some embodiments, the first network element may further send indication information #1 to the second network element. This indication information #1 is used to instruct the reuse of an existing tunnel. In other words, in some embodiments, the first network element may send a display indication information to the second network element, which is used to instruct the reuse of an existing tunnel. This existing tunnel may be a tunnel for terminal #1. The tunnel for terminal #1 may include the tunnel between terminal #1 and user plane function network element #1. The tunnel for terminal #1 may also include the tunnel between terminal #1 and user plane function network element #2. In other words, the tunnel for terminal #1 may include: a tunnel from terminal #1 to user plane function network element #1, and a tunnel from user plane function network element #1 to terminal #1. The tunnel for terminal #1 may also include: a tunnel from terminal #1 to user plane function network element #2, and a tunnel from user plane function network element #2 to terminal #1. User plane function network element #1 is a network element that can access application server #1, and user plane function network element #2 is a network element that can access application server #2. User plane function network element #1 and user plane function network element #2 can be network elements in a network, but application server #1 and application server #2 do not belong to the network. The network can be a mobile communication network or a core network within a mobile communication network. Taking Figure 2 as an example, if application server #1 is AS211, user plane function network element #1 is PAS241; if application server #2 is AS221, user plane function network element #2 is PAS242.

[0409] Optionally, in some embodiments, the first network element may send indication information #2 to the second network element. The indication information #2 is similar to the indication information #2 in the method shown in FIG6 , and will not be described again for the sake of brevity.

[0410] Optionally, in other embodiments, the first network element may send instruction information #3 to the second network element. This instruction information #3 has all the functions of instruction information #1 and instruction information #2. In other words, this instruction information #3 may indicate the following: instructing the tunnel of terminal #1 to be multiplexed, instructing the second network element to establish a mapping relationship between the identity information of terminal #1 and the address information of application server #1, and instructing the second network element to send the address information of application server #1, the address information of application server #2, and the identity information of terminal #1 to a third network element.

[0411] Optionally, in some embodiments, the first network element may send any one of indication information #1, indication information #2, or indication information #3 to the second network element. In other embodiments, the first network element may send any multiple or all of indication information #1, indication information #2, or indication information #3 to the second network element.

[0412] Optionally, in some embodiments, all indication information sent by the first network element to the second network element may be carried by request #1. In other words, request #1 may also include any one or more of indication information #1, indication information #2, or indication information #3.

[0413] Optionally, in other embodiments, part or all of the indication information sent by the first network element to the second network element may also be carried by a single request. For example, indication information #1 may be carried by request #1, and indication information #2 may be carried by request #a.

[0414] Optionally, in some embodiments, the address information of application server #1, the address information of application server #2, and the identity information #1 of terminal #1 may be carried in different requests. For example, request #a includes the address information of application server #1, request #b includes the address information of application server #2, and request #c includes the identity information #1 of terminal #1.

[0415] 1002. The second network element establishes a mapping relationship between the identity information of the terminal #1 and the address information of the application server #1.

[0416] Step 1002 is similar to step 602 and will not be described again for the sake of brevity.

[0417] 1003. The second network element determines a third network element according to the identity information #1 of the terminal #1.

[0418] 1004. The second network element sends the address information of the application server #1 and the address information of the application server #2 to the third network element. Correspondingly, the third network element receives the address information of the application server #1 and the address information of the application server #2.

[0419] Optionally, in some embodiments, the second network element may directly send the received #Request 1 containing the address information of the application server #1 and the address information of the application server #2 to the third network element. In other words, in this case, it can be considered that the second network element transparently transmits the request #1.

[0420] Optionally, in other embodiments, the second network element may re-determine a new request (e.g., request #1-1) based on request #1, where request #1-1 includes relevant information to be sent to the third network element. For example, request #1-1 includes the address information of application server #1 and the address information of application server #2.

[0421] Optionally, in some embodiments, the second network element may determine the identity information #2 of terminal #1 based on the identity information #1 of terminal #1. In this case, the second network element may also send the identity information #2 of terminal #1 to the third network element. Accordingly, the third network element receives the identity information #2 of terminal #1.

[0422] Optionally, in some embodiments, the second network element may send the address information of the application server #1, the address information of the application server #2, and the identity information #2 of the terminal #1 to the third network element upon receiving the display indication. For example, the second network element may send the address information of the application server #1, the address information of the application server #2, and the identity information #2 of the terminal #1 to the third network element upon receiving indication information #2 or indication information #3.

[0423] Optionally, in some other embodiments, if the second network element does not receive the display indication (e.g., indication information #2 and indication information #3), then it can be considered that the first network element implicitly instructs the second network element to send the address information of the application server #1, the address information of the application server #2, and the identity information #2 of the terminal #1 to the third network element. In other words, if the first network element sends the request #1, or sends any one or more of the identity information #1 of the terminal #1, the address information of the application server #1, and the address information of the application server #2 to the second network element, it can be considered that the first network element instructs the second network element to send the address information of the application server #1, the address information of the application server #2, and the identity information #2 of the terminal #1 to the third network element. In other words, if the second network element receives the request #1, or receives any one or more of the identity information #1 of the terminal #1, the address information of the application server #1, and the address information of the application server #2, the second network element sends the address information of the application server #1, the address information of the application server #2, and the identity information #2 of the terminal #1 to the third network element.

[0424] As described above, the second network element's sending of the identity information #2 of terminal #1 to the third network element is optional. In some embodiments, the instruction information #2 and the instruction information #3 may also indicate that the address information of application server #1 and the address information of application server #2 are sent to the third network element. In other words, in this case, the instruction information #2 and the instruction information #3 may not necessarily indicate that the identity information #2 of terminal #1 is sent to the third network element. Of course, in other embodiments, even if the instruction information #2 or the instruction information #3 indicates that the identity information #2 of terminal #1 is sent to the third network element, the second network element may independently determine not to send the identity information #2 of terminal #1 to the third network element.

[0425] As described above, in some embodiments, the first network element may further send an indication message (e.g., indication message #1 and indication message #3) to the second network element, indicating the tunnel of multiplexing terminal #1. When the second network element receives the indication message, the second network element may send an indication message to the third network element, where the indication message is used to indicate the tunnel of multiplexing terminal #1. For example, if the second network element receives indication message #1, the second network element may directly forward the indication message #1 to the third network element. Alternatively, it may be considered that the second network element transparently transmits the indication message #1 to the third network element. For another example, if the second network element receives indication message #3, the second network element may determine a new indication message (which may be referred to as indication message #3.1). Indication message #3.1 is used to indicate the tunnel of multiplexing terminal #1.

[0426] Optionally, in some embodiments, if the second network element does not receive indication information (e.g., indication information #1 or indication information #3) that explicitly indicates the tunnel of multiplexing terminal #1, then the first network element may be considered to have implicitly indicated the tunnel of multiplexing terminal #1. In other words, if the first network element sends the request #1 to the second network element, or sends any one or more of the identity information #1 of the terminal #1, the address information of the application server #1, and the address information of the application server #2, then the first network element may be considered to have indicated the tunnel of multiplexing terminal #1. In other words, if the second network element receives the request #1, or receives any one or more of the identity information #1 of the terminal #1, the address information of the application server #1, and the address information of the application server #2, then the second network element sends an indication information to the third network element, where the indication information indicates the tunnel of multiplexing terminal #1.

[0427] 1005. The third network element determines session management network element #1.

[0428] Optionally, in some embodiments, the third network element may determine the session management network element #1 based on the address information of the application server #1.

[0429] Optionally, in some other embodiments, the third network element may determine the session management network element #1 based on the identity information #2 of the terminal #1.

[0430] In some embodiments, if the third network element obtains the identity information of the terminal, the third network element can independently determine whether to determine the session management network element based on the identity information of the terminal. In other words, if the third network element obtains the identity information #2 of terminal #1, the third network element can determine the session management network element based on the address information of application server #1, or it can determine the session management network element based on the identity information 2 of terminal #1.

[0431] In other embodiments, if the third network element obtains the identity information of the terminal, the third network element determines the session management network element based on the identity information of the terminal. In other words, if the third network element obtains the identity information #2 of terminal #1, the third network element determines the session management network element based on the identity information #2 of terminal #1; if the third network element does not obtain the identity information #2 of terminal #1, the third network element may determine the session management network element based on the address information of application server #1.

[0432] 1006. The third network element sends the address information of the application server #1 and the address information of the application server #2 to the session management network element #1.

[0433] Optionally, in some embodiments, the third network element determines a rule related to the tunnel, and then sends the rule to the session management network element #1.

[0434] Optionally, in some embodiments, the third network element may directly determine the rule based on the received information. In other words, the rule only includes the address information of the application server #1 and the address information of the application server #2 received by the third network element from the second network element.

[0435] Optionally, in other embodiments, the third network element may determine this rule based on the received information and other information. For example, in some embodiments, the third network element may receive identity information #2 of terminal #1. In this case, the third network element may also determine identity information #3 of terminal #1 based on identity information #2 of terminal #1, and then send identity information #3 of terminal #1 to session management network element #1. In this case, the rule includes the address information of application server #1, the address information of application server #2, and identity information #3 of terminal #1 determined by the third network element.

[0436] The identity information #3 of the terminal #1 may be any one or more of the IP address of the terminal #1, the SUPI of the terminal #1, or the PDU session ID.

[0437] A session management network element (e.g., session management network element #1) is a network element that has session management functions. For example, the session management network element can manage the creation and deletion of PDU sessions, maintain PDU session contexts, and user plane forwarding channel information. For example, the session management network element can be an SMF in the system shown in Figures 1 to 5.

[0438] As described above, in some embodiments, the third network element may also receive a display indication indicating the tunnel of multiplexing terminal #1. In this case, the third network element may forward the display indication to the session management network element #1. Similarly, if the third network element does not receive the display indication, the third network element may independently determine a display indication indicating the tunnel of multiplexing terminal #1 and send the display indication to the session management network element #1.

[0439] 1007. The session management network element #1 determines PDU session #1 and configures a tunnel for user plane function network element #1 and / or user plane function network element #2 according to tunnel-related rules. The rules include the address information of the application server #1 and the address information of the application server #2.

[0440] PDU session #1 is a PDU session of terminal #1. User plane function network element #1 and user plane function network element #2 are used to transmit data of the PDU session of terminal #1.

[0441] The session management network element #1 may determine or select the user plane function network element #1 based on the address information of the application server #1. The session management network element #1 may determine or select the user plane function network element #2 based on the address information of the application server #2.

[0442] In some embodiments, session management network element #1 can determine, based on the address of application server #1, that a user plane function network element controlled by session management network element #1 is a user plane function network element capable of accessing application server #1. In this case, session management network element #1 can determine that this user plane function network element is user plane function network element #1. Session management network element #1 can determine, based on the address of application server #1, that another user plane function network element controlled by session management network element #1 is a user plane function network element capable of accessing application server #2. In this case, session management network element #1 can determine that this user plane function network element is user plane function network element #2.

[0443] In other embodiments, session management network element #1 can determine, based on the address of application server #1, that a user plane function network element controlled by session management network element #1 is a user plane function network element that can access application server #1. In this case, session management network element #1 can determine that this user plane function network element is user plane function network element #1. Session management network element #1 can determine, based on the address of application server #1, that none of the user plane function network elements controlled by session management network element #1 can access application server #2. In this case, session management network element #1 can determine a session management network element (which can be referred to as session management network element #2) that can control the user plane function network element that can access application server #2, and send the address information of application server #1 and application server #2 to session management network element #2.

[0444] When both user plane function network element #1 and user plane function network element #2 are controlled by session management network element #1, session management network element #1 may interact with user plane function network element #1 and / or user plane function network element #2 to configure a tunnel for user plane function network element #1 and / or user plane function network element #2. For example, session management network element #1 configures user plane function network element #1 by sending packet detection rule #1 to user plane function network element #1 to obtain the tunnel. Session management network element #1 may determine packet detection rule #1 and send packet detection rule #1 to user plane function network element #1. Packet detection rule #1 may include at least one of the address information of application server #1 or the address information of application server #2. For example, in some embodiments, packet detection rule #1 may include packet detection information #1, which includes packet filter set #1 and / or address information #1. Packet filter set #1 includes at least one of the address information of application server #1 or the address information of application server #2. The address information #1 includes at least one of the IP address or port number #1 of the application server #1. Optionally, in some embodiments, session management network element #1 obtains the tunnel by sending packet detection rule #2 to user plane function network element #2 to configure user plane function network element #2. Session management network element #1 may determine packet detection rule #2 and send packet detection rule #2 to user plane function network element #2. The packet detection rule #2 may include at least one of the address information of application server #1 or the address information of application server #2. For example, in some embodiments, packet detection rule #2 may include packet detection information #2, which includes packet filter set #2 and / or address information #2. The packet filter set #2 includes at least one of the address information of application server #1 or the address information of application server #2. The address information #2 includes at least one of the IP address or port number #1 of application server #1.

[0445] When user plane function network element #1 is controlled by session management network element #1 and user plane function network element #2 is controlled by session management network element #2, session management network element #1 may interact with user plane function network element #1 and / or session management network element #2 to configure a tunnel for user plane function network element #1 and / or user plane function network element #2. For example, session management network element #1 configures user plane function network element #1 by sending packet detection rule #1 to user plane function network element #1 to obtain the tunnel. Session management network element #1 may determine packet detection rule #1 and send packet detection rule #1 to user plane function network element #1. Packet detection rule #1 may include at least one of the address information of application server #1 or the address information of application server #2. For example, in some embodiments, packet detection rule #1 may include packet detection information #1, which includes packet filter set #1 and / or address information #1. Packet filter set #1 includes at least one of the address information of application server #1 or the address information of application server #2. The address information #1 includes at least one of the IP address or port number #1 of the application server #1. Optionally, session management network element #1 configures user plane function network element #2 by sending packet detection rule #2 to user plane function network element #2 to obtain the tunnel. For example, in some embodiments, session management network element #1 may also instruct session management network element #2 to send packet detection rule #2 to user plane function network element #2. For example, in some embodiments, session management network element #1 may instruct session management network element #2 to determine packet detection rule #2 and then send the packet detection rule #2 to user plane function network element #2. In other words, in this case, packet detection rule #2 is determined by session management network element #2. In other embodiments, session management network element #1 may independently determine packet detection rule #2 and then send packet detection rule #2 to session management network element #2. Session management network element #2 then sends the obtained packet detection rule #2 to user plane function network element #2. Packet detection rule #2 may include at least one of the address information of application server #1 or the address information of application server #2. For example, in some embodiments, packet detection rule #2 may include packet detection information #2, which includes packet filter set #2 and / or address information #2. Packet filter set #2 includes at least one of the address information of application server #1 or the address information of application server #2. Address information #2 includes at least one of the IP address of application server #1 or port number #1.

[0446] Packet inspection rule #1 and packet inspection rule #2 can be used to inspect data packets from application server #1.

[0447] Corresponding to Table 1, packet filter set #1 and packet filter set #2 may be entries named “packet filter set” in Table 1, and address information #1 and address information #2 may be entries named “UE IP address” in Table 1.

[0448] In some embodiments, packet inspection rule #1 and packet inspection rule #2 can be modifications to the existing packet inspection rule in PDU session #1. In other words, session management network element #1 can update a packet inspection rule in PDU session #1 and then send the updated packet inspection rule (i.e., packet inspection rule #1) to user plane function network element #1. Similarly, session management network element #1 or session management network element #2 can update a packet inspection rule in PDU session #1 and then send the updated packet inspection rule (i.e., packet inspection rule #2) to user plane function network element #2.

[0449] In some embodiments, packet detection rule #1 and packet detection rule #2 may be two newly created packet detection rules.

[0450] If the network also includes a network element responsible for data packet forwarding and data offloading services (which may be referred to as a seventh network element), the session management network element #1 may determine packet detection information #5 and send the packet detection rule #5 to the seventh network element. For example, the seventh network element may be the ULCL in Figure 2 or Figure 3.

[0451] Packet detection rule #5 may include packet detection information #5, which is used to detect data packets from application server #1. Packet detection information #5 may include a packet filter set #5 and / or address information #5. Packet filter set #5 may include at least one of the address information of application server #1 or the address information of application server #2. Address information #5 includes at least one of the IP address or port number #1 of application server #1. Similarly, packet filter set #5 may be the entry named "Packet Filter Set" in Table 1, and address information #5 may be the entry named "UE IP Address" in Table 1.

[0452] 1008. The session management network element #1 may send tunnel confirmation information to the first network element. The tunnel confirmation information is used to indicate that the tunnel between the user plane function network element #1 and the user plane function network element #2 has been configured.

[0453] For ease of description, in the following embodiments, the tunnel configured by the method shown in FIG. 10 may be referred to as tunnel #5.

[0454] When tunnel #5 is configured, application server #1 can send a data packet to application server #2 through tunnel #5. The source IP address of the data packet is application server #1's IP address, the source port number is port #1, the destination IP address is application server #2's IP address, and the destination port number is port #2.

[0455] After receiving the data packet from application server #1, user plane function network element #1 can match the data packet based on packet detection rule #1. If the data packet matches packet detection rule #1, it will perform the corresponding forwarding action and send the data packet to user plane function network element #2 or the seventh network element.

[0456] Similarly, if packet inspection rule #2 is configured for user plane function network element #2, user plane function network element #2 can match the received data packet based on packet inspection rule #2. If the data packet matches packet inspection rule #2, user plane function network element #2 performs the corresponding forwarding action and sends the data packet to application server #2. If packet inspection rule #2 is not configured for user plane function network element #2, user plane function network element #2 can send the data packet to application server #2 based on the outer header of the encapsulated data packet.

[0457] If the system includes a seventh network element and a packet detection rule (i.e., packet detection rule #5 mentioned above) is configured for the seventh network element, the seventh network element can receive a data packet from user plane function network element #1, match the received data packet based on packet detection rule #5, and if the data packet matches packet detection rule #5, perform the corresponding forwarding action and send the data packet to user plane function network element #2. Similarly, if no packet detection rule is configured for the seventh network element, the seventh network element can send the data packet to user plane function network element #2 based on the outer header.

[0458] Application server #2 can also start a similar process to build a tunnel to send data packets to application server #1. The following describes the process of determining this tunnel with reference to FIG11.

[0459] FIG11 is a schematic flowchart of another communication method provided according to an embodiment of the present application.

[0460] 1101. The fourth network element sends a request #2 to the fifth network element. In response, the fifth network element receives the request #2. The request #2 includes the address information of the application server #1, the address information of the application server #2, and the identity information #1 of the terminal #1.

[0461] In some embodiments, the address information of the application server #1 may include the IP address and / or port number #3 of the application server #1.

[0462] In some embodiments, the address information of the application server #2 may include the IP address and / or port number #4 of the application server #2.

[0463] In the method shown in Figure 10, the first network element can send the address information of application server #1 to the second network element. For ease of description, this address information of application server #1 sent to the second network element can be referred to as application server #1 address information #1. In other words, application server #1 address information #1 includes the IP address and / or port number #1 of application server #1. Application server #1 address information #2 includes the IP address and / or port number #3 of application server #1.

[0464] In some embodiments, port number #1 may be the same as port number #3. In other words, the address information #1 of application server #1 and the address information #2 of application server #1 are the same. In this case, the address information of application server #1 included in request #2 can be considered to be either the address information #1 of application server #1 or the address information #2 of application server #1.

[0465] In other embodiments, port number #1 and port number #3 may be different. In this case, the address information #1 of application server #1 is different from the address information #2 of application server #1. In this case, the address information of application server #1 in request #2 may include: the address information #1 of application server #1 and the address information #2 of application server #1. In other words, the address information of application server #1 in request #2 may include: the IP address and / or port number #1 of application server #1; the address information of application server #1 in request #2 may also include the IP address and / or port number #3 of application server #1. As described above, when application server #1 sends a data packet to application server #2 through tunnel #1, the source IP address of the data packet is the IP address of application server #1, and the source port number of the data packet is port number #1. Therefore, application server #2 and the first network element can obtain the address information #1 of application server #1 through the data packet.

[0466] Similarly, in some embodiments, port number #2 may be the same as port number #4. In other embodiments, port number #2 may be different from port number #4.

[0467] In the embodiment of the present application, there is no limitation on the event that triggers the fourth network element to send the address information of application server #1 and the address information of application server #2 to the fifth network element (hereinafter referred to as "trigger event").

[0468] For a detailed introduction to the fourth network element, the fifth network element, application server #1, application server #2, the address information of application server #1, the address information of application server #2, the triggering event, and the identity information #1 of terminal #1, please refer to the method shown in Figure 7. For the sake of brevity, it will not be repeated here.

[0469] Optionally, in some embodiments, the fourth network element may further send indication information #4 to the fifth network element. Indication information #4 is used to instruct the reuse of an existing tunnel. In other words, in some embodiments, the first network element may send a display indication information to the second network element, which displays the indication information to instruct the reuse of an existing tunnel. This existing tunnel may be the tunnel of terminal #1. The tunnel of terminal #1 may include the tunnel between terminal #1 and user plane function network element #3. The tunnel of terminal #1 may also include the tunnel between terminal #1 and user plane function network element #4. In other words, the tunnel of terminal #1 may include: a tunnel from terminal #1 to user plane function network element #3, and a tunnel from user plane function network element #3 to terminal #1. The tunnel of terminal #1 may also include: a tunnel from terminal #1 to user plane function network element #4, and a tunnel from user plane function network element #4 to terminal #1. User plane function network element #3 is a network element that can access application server #1, and user plane function network element #4 is a network element that can access application server #2. User plane function network element #3 and user plane function network element #4 can be network elements in a network, and application server #1 and application server #2 do not belong to the network. The network can be a mobile communication network or a core network in a mobile communication network. Taking Figure 2 as an example, if application server #1 is AS211, user plane function network element #3 is PAS241; if application server #2 is AS221, user plane function network element #4 is PAS. 242. In some embodiments, user plane function network element #3 and user plane function network element #1 in the embodiment shown in Figure 10 can be the same user plane function network element, or different user plane function network elements. In some embodiments, user plane function network element #4 and user plane function network element #2 in the embodiment shown in Figure 10 can be the same user plane function network element, or different user plane function network elements.

[0470] Optionally, in some embodiments, the fourth network element may send instruction information #5 to the fifth network element. The instruction information #5 is used to instruct the fifth network element to send the address information of the application server #1, the address information of the application server #2, and the identity information of the terminal #1 to the sixth network element.

[0471] The sixth network element may be a control network element. For example, the sixth network element may be used to generate and manage users, sessions, QoS processing policies, etc. Therefore, the sixth network element may be referred to as a control network element, a control policy network element, or a control function network element. In some embodiments, the sixth network element may be a PCF as shown in Figures 1 to 5.

[0472] Optionally, in some embodiments, the indication information #5 may also be used to instruct the fifth network element to obtain a mapping relationship, where the mapping relationship is a mapping relationship between the identity information of the terminal #1 and the address information of the application server #1.

[0473] In summary, the fourth network element can instruct the fifth network element to obtain the mapping relationship between the identity information of the terminal #1 and the address information of the application server #1 by displaying instructions, and instruct the fifth network element to send the address information of the application server #1, the address information of the application server #2 and the identity information of the terminal #1 to the sixth network element.

[0474] In other embodiments, the fourth network element may indicate the content indicated by indication information #5 using two indication information. For example, in some embodiments, the fourth network element may send indication information #5.1 and indication information #5.2 to the fifth network element. Indication information #5.1 is used to instruct the fifth network element to obtain the mapping relationship between the identity information of terminal #1 and the address information of application server #1; and indication information #5.2 is used to instruct the fifth network element to send the address information of application server #1, the address information of application server #2, and the identity information of terminal #1 to the sixth network element.

[0475] Optionally, in other embodiments, the fourth network element may send instruction information #6 to the fifth network element. This instruction information #6 has all the functions of instruction information #4 and instruction information #5. In other words, this instruction information #6 may indicate the following: instructing the tunnel of terminal #1 to be multiplexed, instructing the fifth network element to obtain the mapping relationship between the identity information of terminal #1 and the address information of application server #1, and instructing the fifth network element to send the address information of application server #1, the address information of application server #2, and the identity information of terminal #1 to the sixth network element.

[0476] Optionally, in some embodiments, the fourth network element may send any one of indication information #4, indication information #5, or indication information #6 to the fifth network element. In other embodiments, the fourth network element may send any multiple or all of indication information #4, indication information #5, or indication information #6 to the fifth network element.

[0477] Optionally, in some embodiments, all indication information sent by the third network element to the fourth network element may be carried by request #2. In other words, request #2 may also include any one or more of indication information #3, indication information #4, or indication information #5.

[0478] Optionally, in other embodiments, part or all of the indication information sent by the third network element to the fourth network element may also be carried by a single request. For example, indication information #3 may be carried by request #2, and indication information #4 may be carried by request #a.

[0479] Optionally, in some embodiments, the address information of application server #1 and the address information of application server #2 may be carried in different requests. For example, request #a includes the address information of application server #1, and request #b includes the address information of application server #2.

[0480] 1102. The fifth network element obtains a mapping relationship between the identity information of the terminal #1 and the address information of the application server #1.

[0481] As described above, in step 1002 of Figure 10, the fifth network element establishes a mapping relationship between the identity information of the terminal #1 and the address information of the application server #1. In this case, the fifth network element can obtain this mapping relationship.

[0482] Accordingly, in some embodiments, the fifth network element may obtain the mapping relationship locally. In other embodiments, the fifth network element may obtain the mapping relationship from a network element with a storage function (eg, UDR).

[0483] Optionally, in some embodiments, the fifth network element may obtain the mapping relationship between the identity information of the terminal #1 and the address information of the application server #1 upon receiving the display indication. For example, the fifth network element obtains the mapping relationship between the identity information of the terminal #1 and the address information of the application server #1 upon receiving indication information #5 or indication information #6.

[0484] Optionally, in some embodiments, if the fifth network element does not receive a display indication (e.g., indication information #5 and indication information #6), then it can be considered that the fourth network element implicitly instructs the fifth network element to obtain the mapping relationship between the identity information of the terminal #1 and the address information of the application server #1. In other words, if the fourth network element sends the identity information #1 of the terminal #1, the address information of the application server #1, and the address information of the application server #2 to the fifth network element, it can be considered that the fourth network element instructs the fifth network element to obtain the mapping relationship between the identity information of the terminal #1 and the address information of the application server #1. In other words, if the fifth network element receives the identity information #1 of the terminal #1, the address information of the application server #1, and the address information of the application server #2, then the fifth network element obtains the mapping relationship between the identity information of the terminal #1 and the address information of the application server #1.

[0485] 1103 : The fifth network element determines the identity information #1 of the terminal #1 according to the acquired mapping relationship and the identity information of the application server #1.

[0486] Optionally, in some embodiments, the mapping relationship may store the identity information #1 of the terminal #1 and the address information of the application server #1. In this case, the fifth network element may directly determine the identity information #1 of the terminal #1 based on the mapping relationship.

[0487] Optionally, in other embodiments, the mapping relationship may store the identity information #2 of terminal #1 and the address information of application server #1. The identity information #2 of terminal #1 includes the IP address of terminal #1 and / or the SUPI of terminal #1. In this case, the fifth network element may first determine the identity information #2 of terminal #1 based on the mapping relationship and the address information of application server #1, and then determine the identity information #1 of terminal #1 based on the identity information #2 of terminal #1.

[0488] This mapping relationship is established in the method shown in Figure 10 , so the address information of application server #1 stored in this mapping relationship is the address information of application server #1 mentioned in step 1001. In other words, the address information of application server #1 stored in this mapping relationship is the address information #1 of application server #1 mentioned above. If the address information #1 of application server #1 is the same as the address information #2 of application server #1, request #2 can carry only the address information #1 or the address information #2 of application server #1 (or both). If the address information #1 of application server #1 is different from the address information #2 of application server #1, request #2 needs to include both the address information #1 and the address information #2 of application server #1. In other words, request #2 always carries the address information of application server #1 stored in the mapping relationship (i.e., the address information #1 of application server #1). Therefore, the fifth network element can determine the identity information #2 or identity information #1 of terminal #1 based on this mapping relationship and the address information #1 of application server #1.

[0489] 1104. The fifth network element determines a sixth network element according to the identity information #1 of the terminal #1.

[0490] 1105. The fifth network element sends the address information of the application server #1 and the address information of the application server #2 to the sixth network element. Correspondingly, the sixth network element receives the address information of the application server #1 and the address information of the application server #2.

[0491] Optionally, in some embodiments, the fifth network element may directly send the received #Request 2 containing the address information of the application server #1 and the address information of the application server #2 to the third network element. In other words, in this case, it can be considered that the fifth network element transparently transmits the #Request 2.

[0492] Optionally, in other embodiments, the fifth network element may re-determine a new request (e.g., request #2-1) based on request #2, where request #2-1 includes relevant information to be sent to the third network element. For example, request #2-1 includes the address information of application server #1 and the address information of application server #2.

[0493] Optionally, in some embodiments, the fifth network element may determine the identity information #2 of terminal #1 based on the identity information #1 of terminal #1. In this case, the fifth network element may also send the identity information #2 of terminal #1 to the sixth network element. Correspondingly, the sixth network element receives the identity information #2 of terminal #1.

[0494] Optionally, in some embodiments, the fifth network element may send the address information of the application server #1, the address information of the application server #2, and the identity information #2 of the terminal #1 to the sixth network element upon receiving the display instruction. For example, the fifth network element may send the address information of the application server #1, the address information of the application server #2, and the identity information #2 of the terminal #1 to the sixth network element upon receiving instruction information #5 or instruction information #6.

[0495] Optionally, in some other embodiments, if the fifth network element does not receive the display indication (e.g., indication information #5 and indication information #6), then it can be considered that the fourth network element implicitly instructs the fifth network element to send the address information of the application server #1, the address information of the application server #2, and the identity information #2 of the terminal #1 to the sixth network element. In other words, if the fourth network element sends the request #2, or sends any one or more of the identity information #1 of the terminal #1, the address information of the application server #1, and the address information of the application server #2 to the fifth network element, it can be considered that the fourth network element instructs the fifth network element to send the address information of the application server #1, the address information of the application server #2, and the identity information #2 of the terminal #1 to the sixth network element. In other words, if the fifth network element receives the request #2, or receives any one or more of the identity information #1 of the terminal #1, the address information of the application server #1, and the address information of the application server #2, the fifth network element sends the address information of the application server #1, the address information of the application server #2, and the identity information #2 of the terminal #1 to the sixth network element.

[0496] As described above, the fifth network element's sending of the terminal #1's identity information #2 to the sixth network element is optional. In some embodiments, the instruction information #5 and the instruction information #6 may also indicate that the address information of the application server #1 and the address information of the application server #2 are sent to the sixth network element. In other words, in this case, the instruction information #5 and the instruction information #6 may not necessarily indicate that the terminal #1's identity information #2 is sent to the sixth network element. Of course, in other embodiments, even if the instruction information #5 or the instruction information #6 indicates that the terminal #1's identity information #2 is sent to the sixth network element, the fifth network element may independently determine not to send the terminal #1's identity information #2 to the sixth network element.

[0497] As described above, in some embodiments, the fourth network element may further send an indication message (e.g., indication message #4 and indication message #6) to the fifth network element, indicating the tunnel of multiplexing terminal #1. When the fifth network element receives the indication message, the fifth network element may send an indication message to the sixth network element, where the indication message is used to indicate the tunnel of multiplexing terminal #1. For example, if the fifth network element receives indication message #4, the fifth network element may directly forward the indication message #4 to the sixth network element. Alternatively, it may be considered that the fifth network element transparently transmits the indication message #4 to the sixth network element. For another example, if the fifth network element receives indication message #6, the fifth network element may determine a new indication message (which may be referred to as indication message #6.1). Indication message #6.1 is used to indicate the tunnel of multiplexing terminal #1.

[0498] Optionally, in some embodiments, if the fifth network element does not receive indication information (e.g., indication information #4 or indication information #6) that explicitly indicates the tunnel of multiplexing terminal #1, then the fourth network element may be considered to have implicitly indicated the tunnel of multiplexing terminal #1. In other words, if the fourth network element sends the request #2 to the fifth network element, or sends any one or more of the identity information #1 of the terminal #1, the address information of the application server #1, and the address information of the application server #2, then the fourth network element may be considered to have indicated the tunnel of multiplexing terminal #1. In other words, if the fifth network element receives the request #2, or receives no one or more of the identity information #1 of the terminal #1, the address information of the application server #1, and the address information of the application server #2, then the fifth network element sends an indication information to the sixth network element, where the indication information indicates the tunnel of multiplexing terminal #1.

[0499] 1106. The sixth network element determines session management network element #1.

[0500] Optionally, in some embodiments, the sixth network element may determine the session management network element #1 based on the address information of the application server #2.

[0501] Optionally, in some other embodiments, the sixth network element may determine the session management network element #1 based on the identity information #2 of the terminal #1.

[0502] In some embodiments, if the sixth network element obtains the identity information of the terminal, the sixth network element can independently determine whether to determine the session management network element based on the identity information of the terminal. In other words, if the sixth network element obtains the identity information #2 of terminal #1, the sixth network element can determine the session management network element based on the address information of application server #1, or it can determine the session management network element based on the identity information 2 of terminal #1.

[0503] In other embodiments, if the sixth network element obtains the identity information of the terminal, the sixth network element determines the session management network element based on the identity information of the terminal. In other words, if the sixth network element obtains the identity information #2 of the terminal #1, the sixth network element determines the session management network element based on the identity information #2 of the terminal #1; if the sixth network element does not obtain the identity information #2 of the terminal #1, the sixth network element may determine the session management network element based on the address information of the application server #1.

[0504] 1107. The sixth network element sends the address information of the application server #1 and the address information of the application server #2 to the session management network element #1.

[0505] Optionally, in some embodiments, the sixth network element may determine a rule related to the tunnel, and then send the rule to the session management network element #1.

[0506] Optionally, in some embodiments, the sixth network element may directly determine the rule based on the received information. In other words, the rule only includes the address information of the application server #1 and the address information of the application server #2 received by the sixth network element from the fifth network element.

[0507] Optionally, in other embodiments, the sixth network element may determine this rule based on the received information and other information. For example, in some embodiments, the sixth network element may receive identity information #2 of terminal #1. In this case, the sixth network element may also determine identity information #3 of terminal #1 based on identity information #2 of terminal #1, and then send identity information #3 of terminal #1 to session management network element #1. In this case, the rule includes the address information of application server #1, the address information of application server #2, and identity information #3 of terminal #1 determined by the sixth network element.

[0508] The identity information #3 of the terminal #1 may be any one or more of the IP address of the terminal #1, the SUPI of the terminal #1, or the PDU session ID of the terminal #1.

[0509] A session management network element (e.g., session management network element #1) is a network element that has session management functions. For example, the session management network element can manage the creation and deletion of PDU sessions, maintain PDU session contexts, and user plane forwarding channel information. For example, the session management network element can be an SMF in the system shown in Figures 1 to 5.

[0510] As described above, in some embodiments, the sixth network element may also receive a display indication indicating the tunnel of multiplexing terminal #1. In this case, the sixth network element may forward the display indication to the session management network element #1. Similarly, if the sixth network element does not receive the display indication, the sixth network element may independently determine a display indication indicating the tunnel of multiplexing terminal #1 and send the display indication to the session management network element #1.

[0511] 1108. The session management network element #1 determines PDU session #2 and configures user plane function network element #3 and / or user plane function network element #4 to obtain a tunnel according to tunnel-related rules. The rules include the address information of the application server #1 and the address information of the application server #2.

[0512] PDU Session #2 is the PDU Session of Terminal #1. User plane function network element #1 and user plane function network element #2 are used to transmit data of the PDU Session of Terminal #1. PDU Session #2 and PDU Session #1 may or may not be the same.

[0513] The session management network element #1 may determine or select the user plane function network element #1 based on the address information of the application server #1. The session management network element #1 may determine or select the user plane function network element #2 based on the address information of the application server #2.

[0514] In some embodiments, session management network element #1 can determine, based on the address of application server #1, that a user plane function network element controlled by session management network element #1 is a user plane function network element capable of accessing application server #1. In this case, session management network element #1 can determine that this user plane function network element is user plane function network element #3. Session management network element #1 can determine, based on the address of application server #1, that another user plane function network element controlled by session management network element #1 is a user plane function network element capable of accessing application server #2. In this case, session management network element #1 can determine that this user plane function network element is user plane function network element #4.

[0515] In other embodiments, session management network element #1 can determine, based on the address of application server #1, that a user plane function network element controlled by session management network element #1 is a user plane function network element that can access application server #1. In this case, session management network element #1 can determine that this user plane function network element is user plane function network element #3. Session management network element #1 can determine, based on the address of application server #1, that none of the user plane function network elements controlled by session management network element #1 can access application server #2. In this case, session management network element #1 can determine a session management network element (referred to as session management network element #2) that can control the user plane function network element that can access application server #2 and send the address information of application server #1 and application server #2 to session management network element #2.

[0516] When both user plane function network element #3 and user plane function network element #4 are controlled by session management network element #1, session management network element #1 can interact with user plane function network element #3 and / or user plane function network element #4 to configure user plane function network element #3 and / or user plane function network element #4 to obtain a tunnel. For example, session management network element #1 configures user plane function network element #4 by sending packet detection rule #4 to user plane function network element #4 to obtain the tunnel. Session management network element #1 can determine packet detection rule #4 and send packet detection rule #4 to user plane function network element #4. Packet detection rule #4 can include at least one of the address information of application server #1 or the address information of application server #2. For example, in some embodiments, packet detection rule #4 can include packet detection information #4, which includes packet filter set #4 and / or address information #4. Packet filter set #4 includes at least one of the address information of application server #1 or the address information of application server #2. The address information #4 includes at least one of the IP address or port number #1 of application server #1. Alternatively, the address information #4 includes at least one of the IP address or port number #4 of application server #2. Optionally, in some embodiments, session management network element #1 obtains the tunnel by sending packet detection rule #3 to user plane function network element #3 to configure user plane function network element #3. Session management network element #1 may determine packet detection rule #3 and send packet detection rule #3 to user plane function network element #3. The packet detection rule #3 may include at least one of the address information of application server #1 or the address information of application server #2. For example, in some embodiments, packet detection rule #3 may include packet detection information #3, which includes packet filter set #3 and / or address information #3. The packet filter set #3 includes at least one of the address information of application server #1 or the address information of application server #2. The address information #3 includes at least one of the IP address or port number #1 of application server #1. Alternatively, the address information #3 includes at least one of the IP address or port number #4 of the application server #2.

[0517] When user plane function network element #3 is controlled by session management network element #1 and user plane function network element #4 is controlled by session management network element #2, session management network element #1 can interact with user plane function network element #3 and / or session management network element #4 to configure user plane function network element #3 and / or user plane function network element #4 to obtain a tunnel. For example, session management network element #1 configures user plane function network element #1 by sending packet detection rule #4 to user plane function network element #4. Session management network element #1 can instruct session management network element #2 to send packet detection rule #4 to user plane function network element #4. For example, in some embodiments, session management network element #1 can instruct session management network element #2 to determine packet detection rule #4 and then send packet detection rule #4 to user plane function network element #4. In other words, in this case, packet detection rule #4 is determined by session management network element #2. In other embodiments, session management network element #1 can independently determine packet detection rule #4 and then send packet detection rule #4 to session management network element #2. Session management network element #2 then sends the obtained packet detection rule #4 to user plane function network element #4. Packet detection rule #4 may include at least one of the address information of application server #1 or the address information of application server #2. For example, in some embodiments, packet detection rule #4 may include packet detection information #4, which includes packet filter set #4 and / or address information #4. Packet filter set #4 includes at least one of the address information of application server #1 or the address information of application server #2. Address information #4 includes at least one of the IP address or port number #1 of application server #1. Alternatively, address information #4 includes at least one of the IP address or port number #4 of application server #2. Optionally, session management network element #1 configures user plane function network element #3 by sending packet detection rule #3 to user plane function network element #3 to obtain the tunnel. For example, in some embodiments, session management network element #1 may determine packet detection rule #3 and send packet detection rule #3 to user plane function network element #3. Packet detection rule #3 may include at least one of the address information of application server #1 or the address information of application server #2. For example, in some embodiments, packet detection rule #3 may include packet detection information #3, which includes packet filter set #3 and / or address information #3. Packet filter set #3 includes at least one of the address information of application server #1 or the address information of application server #2. Address information #3 includes at least one of the IP address or port number #1 of application server #1. Alternatively, address information #3 includes at least one of the IP address or port number #4 of application server #2.

[0518] Packet inspection rule #3 and packet inspection rule #4 can be used to inspect data packets from application server #2.

[0519] Corresponding to Table 1, packet filter set #3 and packet filter set #4 may be entries named “packet filter set” in Table 1, and address information #3 and address information #4 may be entries named “UE IP address” in Table 1.

[0520] In some embodiments, packet inspection rule #3 and packet inspection rule #4 can be modifications to the existing packet inspection rule in PDU session #1. In other words, session management network element #1 can update a packet inspection rule in PDU session #1 and then send the updated packet inspection rule (i.e., packet inspection rule #3) to user plane function network element #3. Similarly, session management network element #1 or session management network element #2 can update a packet inspection rule in PDU session #1 and then send the updated packet inspection rule (i.e., packet inspection rule #4) to user plane function network element #4.

[0521] In some embodiments, packet detection rule #3 and packet detection rule #4 may be two newly created packet detection rules.

[0522] If the network also includes a network element responsible for data packet forwarding and data offloading services (which may be referred to as an eighth network element), the session management network element #1 may determine packet detection information #6 and send the packet detection rule #6 to the eighth network element. For example, the eighth network element may be the ULCL in Figure 2 or Figure 3. The eighth network element may be the same network element as the seventh network element in Figure 6.

[0523] Packet detection rule #6 may include packet detection information #6, which is used to detect data packets from application server #2. Packet detection information #6 may include a packet filter set #6 and / or address information #6. Packet filter set #6 may include at least one of the address information of application server #1 or the address information of application server #2. Address information #6 may include at least one of the IP address or port number #1 of application server #1. Alternatively, address information #6 may include at least one of the IP address or port number of application server #2.

[0524] 1109. The session management network element #1 may send tunnel confirmation information to the fourth network element. The tunnel confirmation information is used to indicate that the tunnel between the user plane function network element #3 and the user plane function network element #4 has been configured.

[0525] For ease of description, in the following embodiments, the tunnel established by the method shown in FIG. 11 may be referred to as tunnel #6.

[0526] With tunnel #6 established, application server #2 can send a data packet to application server #1 through tunnel #6. The source IP address of the data packet is application server #2's IP address, the source port number is port #4, the destination IP address is application server #1's IP address, and the destination port number is port #3.

[0527] After receiving the data packet from application server #2, user plane function network element #4 can match the data packet based on packet detection rule #4. If the data packet matches packet detection rule #4, it will perform the corresponding forwarding action and send the data packet to user plane function network element #3 or the eighth network element.

[0528] Similarly, if packet inspection rule #3 is configured for user plane function network element #3, user plane function network element #3 can match the received data packet based on packet inspection rule #3. If the data packet matches packet inspection rule #3, it will perform the corresponding forwarding action and send the data packet to application server #1. If packet inspection rule #3 is not configured for user plane function network element #3, user plane function network element #3 can send the data packet to application server #1 based on the outer header of the encapsulated data packet.

[0529] If the system includes an eighth network element and a packet detection rule is configured for the eighth network element (i.e., the packet detection rule #6 mentioned above), the eighth network element can receive a data packet from the user plane function network element #4, match the received data packet based on the packet detection rule #6, and if the data packet matches the packet detection rule #6, perform the corresponding forwarding action and send the data packet to the user plane function network element #3. Similarly, if no packet detection rule is configured for the eighth network element, the eighth network element can send the data packet to the user plane function network element #3 based on the outer header.

[0530] FIG12 is a schematic flowchart of a communication method provided according to an embodiment of the present application.

[0531] 1201. A first network element sends a request #1 to a second network element. Accordingly, the second network element receives the request #1. The request #1 includes the address information of application server #1, the address information of application server #2, and the identity information #1 of terminal #1.

[0532] In some embodiments, the address information of the application server #1 may include the IP address and / or port number #1 of the application server #1.

[0533] In some embodiments, the address information of the application server #2 may include the IP address and / or port number #2 of the application server #2.

[0534] In the embodiment of the present application, there is no limitation on the event that triggers the first network element to send the address information of application server #1 and the address information of application server #2 to the second network element (hereinafter referred to as "trigger event").

[0535] For a detailed introduction to the first network element, the second network element, application server #1, application server #2, the address information of application server #1, the address information of application server #2, the triggering event, and the identity information #1 of terminal #1, please refer to the method shown in Figure 6. For the sake of brevity, it will not be repeated here.

[0536] Optionally, in some embodiments, the first network element may further send indication information #1 to the second network element. This indication information #1 is used to instruct the reuse of an existing tunnel. In other words, in some embodiments, the first network element may send a display indication information to the second network element, which is used to instruct the reuse of an existing tunnel. This existing tunnel may be a tunnel for terminal #1. The tunnel for terminal #1 may include the tunnel between terminal #1 and user plane function network element #1. The tunnel for terminal #1 may also include the tunnel between terminal #1 and user plane function network element #2. In other words, the tunnel for terminal #1 may include: a tunnel from terminal #1 to user plane function network element #1, and a tunnel from user plane function network element #1 to terminal #1. The tunnel for terminal #1 may also include: a tunnel from terminal #1 to user plane function network element #2, and a tunnel from user plane function network element #2 to terminal #1. User plane function network element #1 is a network element that can access application server #1, and user plane function network element #2 is a network element that can access application server #2. User plane function network element #1 and user plane function network element #2 can be network elements in a network, but application server #1 and application server #2 do not belong to the network. The network can be a mobile communication network or a core network within a mobile communication network. Taking Figure 2 as an example, if application server #1 is AS211, user plane function network element #1 is PAS241; if application server #2 is AS221, user plane function network element #2 is PAS242.

[0537] Optionally, in some embodiments, the first network element may send instruction information #2 to the second network element, wherein the instruction information #2 is used to instruct the second network element to send the address information of the application server #1, the address information of the application server #2, and the identity information of the terminal #1 to a third network element.

[0538] The third network element may be a control network element. For example, the third network element may be used to generate and manage users, sessions, QoS processing policies, etc. Therefore, the third network element may be referred to as a control network element, a control policy network element, or a control function network element. In some embodiments, the third network element may be a PCF as shown in Figures 1 to 5.

[0539] Optionally, in some embodiments, the first network element may send indication information #3 to the second network element. Indication information #3 is used to instruct the user plane function network element #2 to allocate an address to the terminal #1. In other words, the first network element may instruct the user plane function network element #2 to allocate an address to the terminal #1 through a displayed indication. This address may be an IP address. For example, in some embodiments, the user plane function network element #2 may have already allocated an address to the terminal #1. In this case, indication information #3 instructs the user plane function network element #2 to allocate a new address. For another example, in other embodiments, the user plane function network element #2 may not have allocated an address to the terminal #1. In this case, the user plane function network element #2 may allocate an address to the terminal #1 in response to indication information #3. For ease of description, in the following embodiments, the address allocated to the terminal #1 by the user plane function network element #2 in response to indication information #3 is referred to as address #1, new address, or specific address. If the user plane function network element #2 has allocated an address to the terminal #1 before responding to the indication information #3, then this address can be called address #0 or old address or original address.

[0540] Optionally, in other embodiments, the first network element may send instruction information #4 to the second network element. This instruction information #4 has all the functions of instruction information #1, instruction information #2, and instruction information #3. In other words, this instruction information #4 may indicate the following: instructing the tunnel of terminal #1 to be multiplexed, instructing the user plane function network element #2 to allocate an address to terminal #1, and instructing the second network element to send the address information of application server #1, the address information of application server #2, and the identity information of terminal #1 to the third network element.

[0541] Optionally, in some embodiments, the first network element may send any one of indication information #1, indication information #2, indication information #3, or indication information #4 to the second network element. In other embodiments, the first network element may send any multiple or all of indication information #1, indication information #2, indication information #3, or indication information #4 to the second network element.

[0542] Optionally, in some embodiments, all indication information sent by the first network element to the second network element may be carried by request #1. In other words, request #1 may also include any one or more of indication information #1, indication information #2, indication information #3, or indication information #4.

[0543] Optionally, in other embodiments, part or all of the indication information sent by the first network element to the second network element may also be carried by a single request. For example, indication information #1 may be carried by request #1, and indication information #2 may be carried by request #a.

[0544] Optionally, in some embodiments, the address information of application server #1, the address information of application server #2, and the identity information #1 of terminal #1 may be carried in different requests. For example, request #a includes the address information of application server #1, request #b includes the address information of application server #2, and request #c includes the identity information #1 of terminal #1.

[0545] 1202. The second network element determines a third network element according to the identity information #1 of the terminal #1.

[0546] 1203. The second network element sends the address information of the application server #1 and the address information of the application server #2 to the third network element. Correspondingly, the third network element receives the address information of the application server #1 and the address information of the application server #2.

[0547] Optionally, in some embodiments, the second network element may directly send the received #Request 1 containing the address information of the application server #1 and the addres...

Claims

1. A communication method, characterized in that: The method comprises: Acquire a rule related to the tunnel, the rule including address information of the first application server and address information of the second application server; According to the rule, a first user plane function network element and / or a second user plane function network element is configured to obtain the tunnel, wherein the first user plane function network element is a network element that can access the first application server, the second user plane function network element is a network element that can access the second application server, and the tunnel is used for communication between the first application server and the second application server; A response is sent to the application network element, where the response is used to indicate that the tunnel has been configured.

2. The method according to claim 1, characterized in that The first user plane function network element and the second user plane function network element are network elements in a first network, and the first application server and the second application server do not belong to the first network.

3. The method according to claim 1 or 2, characterized in that Before configuring the first user plane function network element and / or the second user plane function network element to obtain the tunnel, the method further includes: The first user plane function network element and the second user plane function network element are selected for the terminal, the first user plane function network element and the second user plane function network element are used to transmit data of the session of the terminal, the first application server and the second application server provide application services related to the session for the terminal, and the communication between the first application server and the second application server is related to the application service.

4. The method according to claim 3, characterized in that The first user plane function network element is selected according to the address information of the first application server; The second user plane function network element is selected according to the address information of the second application server.

5. The method according to claim 3, characterized in that The rules also include: a data network access identifier DNAI, The first user plane function network element is selected according to the DNAI; The second user plane function network element is selected according to the address information of the second application server.

6. The method according to any one of claims 3 to 5, characterized in that Configuring the first user plane function network element and / or the second user plane function network element according to the rule to obtain the tunnel includes: The tunnel is obtained by configuring the first user plane function network element by sending a first packet detection rule to the first user plane function network element, where the first packet detection rule includes: at least one of the address information of the first application server or the address information of the second application server; and / or The tunnel is obtained by sending a second packet detection rule to the second user plane function network element to configure the second user plane function network element, where the second packet detection rule includes: at least one of the address information of the first application server or the address information of the second application server.

7. The method according to any one of claims 3 to 6, characterized in that The method further comprises: A third packet detection rule is sent to a third user plane functional network element, where the third user plane functional network element is used to forward and / or divert data of the session, and the third packet detection rule is used to detect data packets from the first application server and / or the second application server. The third packet detection rule includes at least one of the address information of the first application server or the address information of the second application server.

8. The method according to any one of claims 3 to 6, characterized in that The configuring the first user plane function network element and / or the second user plane function network element according to the rule to obtain the tunnel further includes: A fourth packet detection rule is sent to the second user plane function network element, where the fourth packet detection rule is used to detect data packets from the second application server, and the fourth packet detection rule includes a first address, which is allocated by the second user plane function network element to the terminal.

9. The method according to claim 8, characterized in that Said also includes: Sending first indication information to the second user plane function network element, where the first indication information is used to instruct the second user plane function network element to allocate an address; Obtain the first address, where the first address is allocated to the terminal by the second user plane function network element according to the first indication information.

10. The method according to claim 8 or 9, characterized in that The configuring the first user plane function network element and / or the second user plane function network element to obtain the tunnel further includes: The first user plane function network element is configured by sending second indication information to the first user plane function network element, where the second indication information is used to indicate that a source address of a data packet from the first application server is replaced with the first address.

11. The method according to any one of claims 8 to 10, characterized in that The method further comprises: Sending a fifth packet detection rule and a sixth packet detection rule to a fourth user plane function network element, where the fourth user plane function network element is used to forward and / or divert data of the session, the fifth packet detection rule is used to detect a data packet from the first application server, and the fifth packet detection rule includes the first address; and the sixth packet detection rule is used to detect a data packet from the second application server, and the sixth packet detection rule includes the first address; Send third indication information to the fourth user plane function network element, and the third indication information is used to instruct the fourth user plane function network element to send a data packet with the source address being the first address to the second user plane function network element, and to send a data packet with the destination address being the first address to the first user plane function network element.

12. The method according to claim 8 or 9, characterized in that The configuring the first user plane function network element and / or the second user plane function network element to obtain the tunnel further includes: The second user plane function network element is configured by sending fourth indication information to the second user plane function network element, where the fourth indication information is used to instruct to replace the source address of the data packet from the first application server with the first address.

13. The method according to claim 12, characterized in that The method further comprises: Sending a seventh packet detection rule and an eighth packet detection rule to a fifth user plane function network element, where the fifth user plane function network element is used to forward and / or divert data of the session, the seventh packet detection rule is used to detect a data packet from the first application server, the seventh packet detection rule includes at least one of the address information of the first application server or the address information of the second application server, and the eighth packet detection rule is used to detect a data packet from the second application server, and the eighth packet detection rule includes the first address; Send sixth indication information to the fifth user plane function network element, and the sixth indication information instructs the fifth user plane function network element to send a data packet with the source address being the first address to the second user plane function network element, and to send a data packet with the destination address being the first address to the first user plane function network element.

14. The method according to any one of claims 1 to 13, characterized in that The tunnel comprises: a first tunnel for communication from the first application server to the second application server, a first port number for identifying a unique port for the first application server to communicate using the first tunnel, and a second port number for identifying a unique port for the second application server to communicate using the first tunnel; and / or The second tunnel is used for communication from the second application server to the first application server, the third port number is used to identify the unique port of the first application server using the second tunnel for communication, and the fourth port number is used to identify the unique port of the second application server using the second tunnel for communication.

15. The method according to claim 14, characterized in that The address information of the first application server is used to indicate any one or more of the following: an Internet Protocol IP address of the first application server, the first port number, or the third port number; The address information of the second application server is used to indicate any one or more of the following: the IP address of the second application server, the second port number, or the fourth port number.

16. A communication method, characterized in that: include: Sending a first request, where the first request includes address information of the first application server and address information of the second application server; Receive a response to the first request, where the response is used to indicate that a tunnel between a first user plane function network element and a second user plane function network element has been configured, wherein the first user plane function network element is a network element capable of accessing the first application server, the second user plane function network element is a network element capable of accessing the second application server, and the tunnel is used for communication between the first application server and the second application server.

17. The method according to claim 16, characterized in that The first user plane function network element and the second user plane function network element are network elements in a first network, and the first application server and the second application server do not belong to the first network.

18. The method according to claim 16 or 17, characterized in that The tunnel comprises: a first tunnel for communication from the first application server to the second application server, a first port number for identifying a unique port for the first application server to communicate using the first tunnel, and a second port number for identifying a unique port for the second application server to communicate using the first tunnel; and / or The second tunnel is used for communication from the second application server to the first application server, the third port number is used to identify the unique port of the first application server using the second tunnel for communication, and the fourth port number is used to identify the unique port of the second application server using the second tunnel for communication.

19. The method according to claim 18, characterized in that The address information of the first application server is used to indicate any one or more of the following: an Internet Protocol IP address of the first application server, the first port number, or the third port number; The address information of the second application server is used to indicate any one or more of the following: the IP address of the second application server, the second port number, or the fourth port number.

20. The method according to any one of claims 16 to 19, characterized in that The first request further includes: identity information of the terminal, the first application server and the second application server provide application services for the terminal, and the communication between the first application server and the second application server is related to the application services.

21. The method according to claim 20, characterized in that Before sending the first request, the method further includes: Determining a policy control network element corresponding to the terminal; The sending of the first request includes: Sending the first request to the policy control network element.

22. The method according to any one of claims 16 to 21, characterized in that The first request further includes: a data network access identifier DNAI, where the DNAI is used to indicate the area where the first application server is located.

23. The method according to any one of claims 16 to 22, characterized in that The first request is used to instruct to establish the tunnel, or to multiplex an existing tunnel into the tunnel.

24. The method according to any one of claims 16 to 22, characterized in that The first request further includes first indication information, where the first indication information is used to instruct to establish the tunnel, or to multiplex an existing tunnel into the tunnel.

25. The method according to any one of claims 16 to 24, characterized in that The first request further indicates an address of an allocated terminal, where the address of the terminal is used by the first user plane function network element or the second user plane function network element for the communication.

26. The method according to any one of claims 16 to 25, characterized in that The first request further includes second indication information, where the second indication information is used to indicate any one or more of the following: Sending the address information of the first application server and the address information of the second application server to a policy control network element corresponding to the terminal; Sending the identity information of the terminal to the policy control network element corresponding to the terminal; Establish or obtain a mapping relationship between the identity information of the terminal and the address information of the first application server.

27. A communication method, characterized in that: The method comprises: Get the first packet detection rule; Obtaining a first data packet; When the first data packet matches the first packet detection rule, the first data packet is processed.

28. The method according to claim 27, characterized in that Before processing the first data packet, the method further includes: receiving first instruction information, where the first instruction is used to instruct to replace a source address of a data packet from a first application server with a first address; The step of processing the first data packet when the first data packet matches the first packet detection rule includes: Replacing the source address of the first data packet with the address to obtain a second data packet; Send the second data packet to the destination network element.

29. A communication system, characterized in that: The system comprises: a first network element, configured to obtain a rule related to the tunnel, the rule including address information of the first application server and address information of the second application server; The first network element is further configured to configure a first user plane function network element and / or a second user plane function network element according to the rule to obtain the tunnel, wherein the first user plane function network element is a network element that can access the first application server, the second user plane function network element is a network element that can access the second application server, and the tunnel is used for communication between the first application server and the second application server; The first network element is further configured to send a response to the application network element, where the response is used to indicate that the tunnel has been configured; An application network element, configured to receive the response; The first user plane function network element and / or the second user plane function network element is configured to send data packets using the tunnel according to the first network element configuration.

30. The system according to claim 29, wherein: The first user plane function network element and the second user plane function network element are network elements in a first network, and the first application server and the second application server do not belong to the first network.

31. The system according to claim 29 or 30, characterized in that The first network element is also used to select the first user plane function network element and the second user plane function network element for the terminal, the first user plane function network element and the second user plane function network element are used to transmit data of the session of the terminal, the first application server and the second application server provide application services related to the session for the terminal, and the communication between the first application server and the second application server is related to the application service.

32. The system according to claim 31, wherein: The first network element is further configured to configure the first user plane function network element to obtain the tunnel by sending a first packet detection rule to the first user plane function network element, where the first packet detection rule includes: at least one of the address information of the first application server or the address information of the second application server; and / or The first network element is further configured to configure the second user plane function network element to obtain the tunnel by sending a second packet detection rule to the second user plane function network element, where the second packet detection rule includes: at least one of the address information of the first application server or the address information of the second application server; The first user plane functional network element is further used to match a first data packet based on the first packet detection rule, and to process the first data packet when the first data packet matches the first packet detection rule. The first data packet is a data packet received by the first user plane functional network element, and / or the second user plane functional network element is further used to match a second data packet based on the second packet detection rule, and to process the second data packet when the second data packet matches the second packet detection rule. The second data packet is a data packet received by the second user plane functional network element.

33. The system according to claim 31 or 32, characterized in that The first network element is also used to send a third packet detection rule to a third user plane function network element, where the third user plane function network element is used to forward and / or divert data of the session, and the third packet detection rule is used to detect data packets from the first application server and / or the second application server, and the third packet detection rule includes at least one of the address information of the first application server or the address information of the second application server.

34. The system according to claim 31 or 32, characterized in that The first network element is further configured to send a fourth packet detection rule to the second user plane function network element, where the fourth packet detection rule is used to detect a data packet from the second application server, and the fourth packet detection rule includes a first address, where the first address is allocated by the second user plane function network element to the terminal; The first network element is further used to configure the first user plane function network element by sending second indication information to the first user plane function network element, or to configure the second user plane function network element by sending fourth indication information to the second user plane function network element, wherein the second indication information is used to indicate that the source address of the data packet from the first application server is replaced with the first address, and the fourth indication information is used to indicate that the source address of the data packet from the first application server is replaced with the first address.

35. The system according to claim 34, wherein: The first user plane function network element is further configured to match a first data packet based on a first packet detection rule, and replace a source address of the first data packet with the first address when the first data packet matches the first packet detection rule, where the first data packet is a data packet received by the first user plane function network element; or The second user plane function network element is further configured to match a second data packet based on a second packet detection rule, and when the second data packet matches the second packet detection rule, replace the source address of the second data packet with the first address, where the second data packet is a data packet received by the second user plane function network element; The second user plane functional network element is also used to match the third data packet based on the fourth packet detection rule, and process the third data packet when the third data packet matches the fourth packet detection rule. The third data packet is a data packet received by the second user plane network element from the second application server.

36. The system according to any one of claims 29 to 35, characterized in that The application network element is further configured to send a first request, where the first request includes address information of the first application server and address information of the second application server.

37. The system according to any one of claims 29 to 36, characterized in that The tunnel comprises: a first tunnel for communication from the first application server to the second application server, a first port number for identifying a unique port for the first application server to communicate using the first tunnel, and a second port number for identifying a unique port for the second application server to communicate using the first tunnel; and / or The second tunnel is used for communication from the second application server to the first application server, the third port number is used to identify the unique port of the first application server using the second tunnel for communication, and the fourth port number is used to identify the unique port of the second application server using the second tunnel for communication.

38. The system according to claim 37, wherein: The address information of the first application server is used to indicate any one or more of the following: an Internet Protocol IP address of the first application server, the first port number, or the third port number; The address information of the second application server is used to indicate any one or more of the following: the IP address of the second application server, the second port number, or the fourth port number.

39. The system according to any one of claims 36 to 38, characterized in that The first request further includes: identity information of the terminal, the first application server and the second application server provide application services for the terminal, and the communication between the first application server and the second application server is related to the application services.

40. The system according to claim 39, wherein: The application network element is further used to determine a policy control network element corresponding to the terminal; The application network element is further configured to send the first request to the policy control network element.

41. The system according to any one of claims 36 to 40, characterized in that The first request is further used to indicate any one or more of the following: establishing said tunnel, Reusing an existing tunnel as the tunnel, Allocating an address of a terminal, where the address of the terminal is used for the first user plane function network element or the second user plane function network element to perform the communication; Sending the address information of the first application server and the address information of the second application server to a policy control network element corresponding to the terminal; Sending the identity information of the terminal to a policy control network element corresponding to the terminal; or Establish or obtain a mapping relationship between the identity information of the terminal and the address information of the first application server.

42. A communication device, characterized in that The apparatus comprises: a module for executing the method according to any one of claims 1 to 15, or a module for executing the method according to any one of claims 16 to 26, or a module for executing the method according to claim 27 or 28.

43. A communication device, characterized in that include: A processor, configured to execute a computer program stored in a memory, so that the apparatus performs the method according to any one of claims 1 to 15, or the method according to any one of claims 16 to 26, or the method according to claim 27 or 28.

44. A computer program product, characterized in that The computer program product comprises instructions for performing the method of any one of claims 1 to 15, or instructions for performing the method of any one of claims 16 to 26, or instructions for performing the method of claim 27 or 28.

45. A computer-readable storage medium, characterized in that include: The computer-readable storage medium stores a computer program; when the computer program runs on a computer, the computer executes the method according to any one of claims 1 to 15, or the method according to any one of claims 16 to 26, or the method according to claim 27 or 28.

Images