Communication method and device

Abstract

The invention provides a communication method and device, belongs to the technical field of communication, and aims to avoid communication failure between an EAS and an AS. The method comprises the following steps: a first user plane network element receives a first message and first indication information, and configures a route between the first user plane network element and one or more edge application servers according to the first message. The first indication information is used for indicating a first user plane network element and a second user plane network element to establish a tunnel, and the second user plane network element and the first user plane network element correspond to different data network access ranges; the one or more edge application servers and the first user plane network element correspond to the same data network access range.

Description

Technical Field

[0001] This application relates to the field of communications, and more particularly to a communication method and apparatus. Background Technology

[0002] A data network (DN) can include a local data network (L-DN) and a central data network (central-DN). A DN can include one or more servers (such as edge application servers (EAS), application servers (EAS), etc.). For example, EAS is in L-DN and AS is in central-DN.

[0003] Communication between L-DN and central-DN can be achieved through tunneling. For example, a user plane function (UPF) element, denoted as L-UPF, is selected in the data network access identifier (DNAI) of the EAS. A tunnel is established between this L-UPF and a central UPF. The EAS can communicate with the AS through this tunnel, such as the data packet sending path: EAS->L-UPF->central-UPF->AS, and vice versa.

[0004] However, practical applications have shown that even though tunnels have been established, communication failures still occur between EAS and AS. Therefore, ensuring the stability and reliability of communication between EAS and AS is currently a hot research topic. Summary of the Invention

[0005] This application provides a communication method and apparatus to avoid communication failures between EAS and AS.

[0006] To achieve the above objectives, this application adopts the following technical solution:

[0007] In a first aspect, a communication method is provided, applied to a first user plane network element. The method includes: the first user plane network element receiving a first message and first indication information; and configuring routing between the first user plane network element and one or more edge application servers according to the first message. The first indication information is used to instruct the first user plane network element to establish a tunnel with a second user plane network element, wherein the second user plane network element and the first user plane network element correspond to different data network access ranges; and the one or more edge application servers and the first user plane network element correspond to the same data network access range.

[0008] Therefore, when the first user plane network element establishes a tunnel (or node tunnel) with the second user plane network element, the first user plane network element also establishes a route between itself and one or more edge application servers to ensure that data can be correctly routed from one or more edge application servers to the first user plane network element, and finally routed to the application server through the tunnel, so as to ensure the stability and reliability of communication between the edge application server and the application server and avoid communication failure.

[0009] It is understandable that the tunnel between the first user plane network element and the second user plane network element can be applied to communication between two nodes (or node devices). That is, the communication between the first user plane network element and the second user plane network element is unrelated to the data or service type transmitted in the tunnel, or in other words, it is not limited by the data or service type transmitted.

[0010] It can also be understood that the second user plane network element can be interpreted as not a specific one or more user plane network elements, but rather as a network element that is different from the first user plane network element, or can be replaced by other user plane network elements. Alternatively, the second user plane network element can also be a specific one or more user plane network elements.

[0011] In one possible design, the first message includes first instruction information. The first user plane network element configures the routing between itself and one or more edge application servers according to the first message. This includes: the first user plane network element configures the routing between itself and one or more edge application servers according to the first instruction information in the first message. That is, the routing is established by reusing existing information, without additional signaling overhead. The implementation difficulty and complexity are relatively low, and it is also more friendly to the standard.

[0012] Optionally, the first user plane network element configures the routing between itself and one or more edge application servers according to the first indication information in the first message. This includes: the first user plane network element broadcasting default routing information via the user plane according to the first indication information in the first message. One or more edge application servers are within the range where the default routing information is broadcast. This default routing information indicates that if a data packet does not match the routing table, the data packet needs to be routed to the first user plane network element; it can also be understood as a default route, or a default route to the first user plane network element. In this way, even if multiple user plane network elements can communicate with the edge application server, the data packet will only be sent to the first user plane network element, thus ensuring communication between the edge application server and the first user plane network element and preventing communication failure between the edge application server and the application server.

[0013] It should be understood that the default routing information is an exemplary name, or it can be replaced with any possible name, such as the default routing information.

[0014] In one possible design, the first message includes second instruction information, which instructs the first user plane network element to configure routing between itself and one or more edge application servers. The first user plane network element configures the routing between itself and one or more edge application servers according to the first message, including: the first user plane network element configures the routing between itself and one or more edge application servers according to the second instruction information in the first message, that is, establishing routing through a newly defined information element (the second instruction information), decoupling it from existing information elements, and enabling greater flexibility.

[0015] Optionally, the first user plane network element configures the routing between itself and one or more edge application servers according to the second indication information in the first message. This includes: the first user plane network element broadcasting default routing information through the user plane according to the second indication information in the first message. One or more edge application servers are within the range where the default routing information is broadcast. The default routing information is used to indicate that if a data packet does not match the routing table, the data packet needs to be routed to the first user plane network element. For details, please refer to the relevant introduction above, which will not be repeated here.

[0016] In one possible design, the first message includes third indication information, which indicates the address of at least one edge application server or a range of addresses for edge application servers, wherein the address range includes the addresses of at least one edge application server. The first user plane network element configures routing between itself and one or more edge application servers according to the first message, including: the first user plane network element configuring routing between itself and at least one edge application server via the user plane according to the third indication information in the first message. The at least one edge application server belongs to one or more edge application servers, specifically it may be some or all of the edge application servers in the one or more edge application servers.

[0017] In other words, among the edge application servers that can establish routes with the first user plane network element, some or all of the edge application servers can be selected to establish routes with the first user plane network element. The specific selection can be made according to the actual situation, such as the load of the edge application server and the communication latency, so as to ensure that the routing between the two can meet the actual communication needs.

[0018] Optionally, the first message may also include first indication information, meaning that the second indication information (or third indication information) and the first indication information can be transmitted through the same message, resulting in lower communication overhead. Alternatively, if the second message contains the second or third indication information, the first user plane network element receiving the first message and the first indication information includes: the first user plane network element receiving the first message and the second message, where the second message includes the first indication information. That is, the second indication information (or third indication information) and the first indication information can be transmitted through different messages, allowing for more flexible information transmission.

[0019] In one possible design, one or more edge application servers correspond to the same data network access range (such as the first data network access range) as the first user plane network element, or it can also be expressed as one or more edge application servers correspond to the same data network (such as the first data network) as the first user plane network element, such as including: one or more edge application servers correspond to the same data network access identifier DNAI (such as the first DNAI) as the first user plane network element, that is, the data network access range can be the data network or the DNAI.

[0020] It is understood that the aforementioned third indication information may also indicate DNAI (such as DNAI corresponding to one or more edge application servers) or service identifier (such as application ID / full address domain name FQDN, etc.). The first user plane can determine the address of at least one edge application server or the address range of the edge application server corresponding to the DNAI or service identifier.

[0021] In one possible design, the second user plane network element corresponds to a different data network access range than the first user plane network element (e.g., the second user plane network element corresponds to a second data network access range), or it can be described as the second user plane network element corresponding to a different data network than the first user plane network element (e.g., the second user plane network element corresponds to a second data network), such as: the second user plane network element and the first user plane network element each correspond to a different DNAI (e.g., the second user plane network element corresponds to a second DNAI).

[0022] Secondly, a communication method is applied to a session management network element. The method includes: the session management network element receiving edge application service information from an application function network element; and the session management network element sending at least one of a second indication message or a third indication message to a first user plane network element. The edge application service information is used to indicate a communication requirement (or connection / tunneling) between two data network access areas (or two data networks / DNAIs). The second indication message is used to instruct the first user plane network element to configure routing between itself and one or more edge application servers, wherein the first or more edge application servers correspond to the same data network access area in the two data network access areas as the first user plane network element. The third indication message is used to indicate the address of at least one edge application server or a range of addresses for edge application servers, wherein at least one edge application server belongs to one or more edge application servers, and the address range includes the address of at least one edge application server.

[0023] It is understandable that edge application service information can be existing information, such as edge application server deployment information (EDI), or it can be information that will be newly defined in the future, and there are no restrictions on the specific naming.

[0024] In one possible design, the session management network element sends at least one of a second or a third instruction to the first user plane network element, including: the session management network element sending a first message to the first user plane network element based on edge application service information. The first message includes the first instruction and at least one of the aforementioned information. The first instruction is used to instruct the first user plane network element to establish a tunnel with the second user plane network element, where the second user plane network element and the first user plane network element correspond to two different data network access ranges. In other words, the establishment of the tunnel between the first user plane network element and the second user plane network element, and the configuration of the route between the first user plane network element and the edge application server, can occur simultaneously, avoiding communication failures due to tunnel establishment without route configuration, or vice versa.

[0025] Optionally, the two data network access ranges corresponding to the second user plane network element and the first user plane network element respectively include: the two data network access identifiers (DNAI) corresponding to the second user plane network element and the first user plane network element respectively.

[0026] In one possible design, the session management network element sends at least one of a second or a third instruction to the first user plane network element. This includes: the session management network element determining the terminal's session requirements and, based on these requirements, sending the aforementioned at least one piece of information to the first user plane network element. The session requirements include the terminal's session needing routing between two data network access ranges. That is, when data actually needs to be transmitted between two data network access ranges, the session management network element can instruct the first user plane network element to configure its own routing with the edge application server, thus avoiding redundancy caused by pre-configuring routes.

[0027] Optionally, the session management network element determines the terminal's session requirements, including: the session management network element obtaining the edge application server deployment information associated with the data network and / or slice corresponding to the session; the edge application server deployment information includes information indicating communication requirements between the two data network access ranges. In this case, the session management network element determines that the session has a routing requirement between the two data network access ranges based on the information indicating communication requirements between the two data network access ranges.

[0028] Alternatively, the session management network element determines the terminal's session requirements, including: the session management network element instructing the network element serving the session to detect whether the session's data is associated with two data network access ranges; if the session's data is associated with two data network access ranges, then the session management network element determines that the session has a need for routing between the two data network access ranges. For example, edge application service information also indicates the services corresponding to the two data network access ranges; the session management network element instructing the network element serving the session to detect whether the session's data is associated with two data network access ranges includes: the session management network element instructing the network element serving the session to detect whether the data in the session contains services corresponding to the two data network access ranges; if the data in the session contains services corresponding to the two data network access ranges, then it indicates that the session's data is associated with the two data network access ranges; otherwise, the session's data is not associated with the two data network access ranges.

[0029] In other words, the session management network element can determine whether a terminal's session needs to be routed between two data network access ranges through either the control plane or the user plane. The specific choice can be made flexibly according to the actual situation, and no restrictions are imposed here.

[0030] In one possible design, one or more edge application servers and the first user plane network element correspond to the same data network access range, including: one or more edge application servers and the first user plane network element correspond to the same DNAI.

[0031] It is understandable that the technical effects of the method described in the second aspect can also refer to the relevant introduction of the method described in the first aspect above, and will not be repeated here.

[0032] Thirdly, a communication method is provided, applied to a session management network element. The method includes: the session management network element receiving edge application service information from an application function network element; and the session management network element sending address information of a first user plane network element to the application function network element. The edge application service information indicates a communication requirement between two data network access ranges. Routing needs to be configured between the first user plane network element and the edge application server. The first user plane network element is used for communication between the edge application server and a server in the second data network access range of the two data network access ranges. The edge application server and the first user plane network element correspond to the first data network access range of the two data network access ranges.

[0033] Therefore, when there is a communication requirement between the first data network access range and the second data network access range, the session management network element can expose the address information of the first user plane network element corresponding to the same data network access range as the edge application server, i.e., the first data network access range, to the application function network element. This allows the application function network element to instruct the edge application server to configure routing with the first user plane network element, ensuring that data can be correctly routed from the edge application server to the first user plane network element and finally routed to the application server through the tunnel. This ensures the stability and reliability of communication between the edge application server and the application server and avoids communication failures.

[0034] In one possible design, the address information of the first user plane network element is the N6 address of the first user plane network element, or the address of the first user plane network element on the N6 interface. The N6 interface is the interface between the first user plane network element and the data network, which can ensure that the edge application server and the first user plane network element are configured with routing.

[0035] Optionally, the method described in the third aspect may further include: the session management network element obtaining the address information of the first user plane network element from any of the following: the session management network element itself, the first user plane network element, or the data storage network element. For example, obtaining the address information of the first user plane network element from the data storage network element includes: the session management network element sending the N4 address of the first user plane network element to the data storage network element, and receiving the N6 address of the first user plane network element returned by the data storage network element based on the N4 address of the first user plane network element.

[0036] In one possible design, the session management network element sends the address information of the first user plane network element to the application function network element. This includes: the session management network element sending the address information of the first user plane network element to the application function network element according to the identifier of the application function network element. This ensures that the address information of the first user plane network element can be correctly accessed by the application function network element.

[0037] Optionally, the method described in the first aspect may further include: the session management network element receiving the identifier of the application function network element from the application function network element, that is, provided by the application function network element itself, or the session management network element may obtain it through other means, without any specific limitation.

[0038] In one possible design, the first user plane network element corresponds to the first data network access range including the first data network access identifier (DNAI) corresponding to the first user plane network element. The method described in the third aspect may further include: the session management network element sending the first DNAI to the application function network element, so that the application function network element can select the edge application server corresponding to the same DNAI as the first user plane network element, ensuring that subsequent routing can be configured successfully.

[0039] In one possible design, the method described in the third aspect may further include: the session management network element sending information to the application function network element to indicate the establishment of a tunnel between user plane network elements. This information may be combined with the address information of the first user plane network element to indicate that the first user plane network element is the user plane network element for establishing the tunnel between user plane network elements, so that the application function network element can know that it needs to configure routing for the first user plane network element.

[0040] Optionally, the second user plane network element corresponds to the second data network access range including: the second user plane network element corresponds to the second DNAI.

[0041] In one possible design, the session management network element sends the address information of the first user plane network element to the application function network element. This includes: the session management network element receiving a subscription request from the application function network element; the subscription request is used to subscribe to user plane events, where the user plane event is a terminal accessing a service requiring communication between two data network access ranges; the session management network element instructs the network element serving the terminal's session to detect the user plane event; if the network element serving the terminal's session detects the user plane event, the session management network element sends a subscription response to the application function network element; the subscription response contains the address information of the first user plane network element. In other words, the session management network element only provides the address information of the first user plane network element to the application function network element when data actually needs to be transmitted between the two data network access ranges, in order to configure the routing between the first user plane network element and the edge application server, thus avoiding redundancy caused by pre-configuration.

[0042] Optionally, the subscription request also indicates the services corresponding to the two data network access ranges; the session management network element instructs the network element serving the terminal's session to detect user plane events, including: the session management network element instructs the network element serving the terminal's session to detect whether the data in the session contains services corresponding to the two data network access ranges; if the data in the session contains services corresponding to the two data network access ranges, it indicates that a user plane event has been detected; otherwise, no user plane event has been detected. Thus, using information provided by the application function network element for detection can ensure the accuracy of the detection. Correspondingly, in the case of a detected user plane event, the method described in the third aspect further includes: the session management network element determining a first user plane network element for establishing a tunnel based on at least one of the following: the terminal's location, edge application service information, and information related to services corresponding to the two data network access ranges in the data packets in the session; the first user plane network element establishes a tunnel with a second user plane network element; the second user plane network element corresponds to the second data network access range, to avoid routing configuration failure due to providing incorrect address information.

[0043] Optionally, the second user plane network element corresponds to the second data network access range including the second user plane network element corresponds to the second DNAI.

[0044] Fourthly, a communication method is provided, applied to an application function network element. The method includes: the application function network element sending edge application service information to a session management network element and receiving address information of a first user plane network element returned by the session management network element; thereby, based on the address information of the first user plane network element, instructing at least one edge application server to configure routing between itself and the first user plane network element. The edge application service information is used to indicate a communication requirement between two data network access ranges; the first user plane network element is used for communication between the edge application server and a server in the second data network access range of the two data network access ranges, and the first user plane network element and at least one edge application server correspond to the first data network access range of the two data network access ranges.

[0045] It is understandable that the way the application function network element instructs at least one edge application server to configure the routing between the first user plane network element can be referred to the above description, such as broadcasting missing routing information or configuring routing based on address information, which will not be repeated here.

[0046] In one possible design, the address information of the first user plane network element is the N6 address of the first user plane network element.

[0047] In one possible design, the method described in the fourth aspect may further include: the application function network element determining, from the two data network access ranges, at least one edge application server corresponding to the same data network access range as the first user plane network element.

[0048] In one possible design, the method described in the fourth aspect may further include: the application function network element receiving a first data network access identifier (DNAI) corresponding to a first user plane network element from the session management network element; the first data network access range corresponding to the first user plane network element includes the first DNAI corresponding to the first user plane network element.

[0049] In one possible design, the method described in the fourth aspect may further include: the application function network element receiving information from the session management network element instructing the establishment of a tunnel between user plane network elements.

[0050] In one possible design, the application function network element receives address information from the first user plane network element of the session management network element, including: the application function network element sending a subscription request to the session management network element; the subscription request is used to subscribe to user plane events, where the user plane events are services that require communication between two data network access ranges; the application function network element receives a subscription response returned by the session management network element in response to the subscription request; the subscription response contains the address information of the first user plane network element.

[0051] It is understandable that the technical effects of the method described in the fourth aspect can also refer to the relevant introduction of the method described in the third aspect above, and will not be repeated here.

[0052] Fifthly, a communication method is provided, applied to a session management network element. The method includes: the session management network element receiving edge application service information from an application function network element; the edge application service information indicating a communication requirement between two data network access ranges, and address information of a first user plane network element; wherein the first user plane network element and the edge application server are configured with a route, and the edge application server and the first user plane network element correspond to the same data network access range among the two data network access ranges; if no tunnel has been established between user plane network elements in the data network access range corresponding to the first user plane network element, the session management network element instructs the first user plane network element to establish a tunnel with a second user plane network element; the second user plane network element and the first user plane network element each correspond to two data network access ranges.

[0053] Therefore, it can be seen that the application function network element actively configures the routing between the first user plane network element and the edge application server corresponding to the same data network access range, and provides the address information of the first user plane network element to the session management network element. Then, the session management network element can establish a tunnel between the first user plane network element and the second user plane network element based on the address information of the first user plane network element, so as to realize communication between the two data network access ranges.

[0054] It is understandable that the method of configuring routing between the edge application server and the first user plane network element for application function network elements can refer to the above introduction, such as broadcasting missing routing information or configuring routing based on address information, which will not be elaborated here.

[0055] In one possible design scheme, the tunnel between user plane network elements refers to the tunnel between user plane network elements corresponding to two data network access ranges respectively. For details, please refer to the relevant introduction above, which will not be repeated here.

[0056] In one possible design, the method described in the fifth aspect may further include: if a tunnel between user plane network elements has been established within the data network access range corresponding to the first user plane network element, the session management network element instructs the third user plane network element to release the established tunnel between user plane network elements to avoid redundancy. Furthermore, the first user plane network element and the third user plane network element correspond to the same data network access range.

[0057] In one possible design, the method described in the fifth aspect may further include: when a tunnel between user plane network elements has been established within the data network access range corresponding to the first user plane network element, the session management network element sends an indication message to the application function network element. The indication message is used to indicate that routing between the third user plane network element and the edge application server needs to be configured to ensure normal communication between the two data network access ranges. The second user plane network element has already established a tunnel between user plane network elements, and the first user plane network element and the second user plane network element correspond to the same data network access range. Thus,

[0058] In one possible design, the session management network element instructs the first user plane network element to establish a tunnel with the second user plane network element, including: the session management network element instructs the first user plane network element to establish a tunnel with the second user plane network element based on the address information of the first user plane network element, so as to avoid tunnel establishment failure due to address errors.

[0059] Optionally, the address information of the first user plane network element is its N6 address. The session management network element, based on the address information of the first user plane network element, instructs the first user plane network element to establish a tunnel with the second user plane network element. This includes: the session management network element determining the N4 address of the first user plane network element based on its N6 address, and instructing the first user plane network element to establish a tunnel with the second user plane network element based on its N4 address. It can be understood that the N6 address of the first user plane network element is the address of the first user plane network element on its N6 interface, which is the interface between the first user plane network element and the data network. The N4 address of the first user plane network element is the address of the first user plane network element on its N4 interface, which is the interface between user plane network elements. Therefore, directly using the address on the N6 interface cannot establish a tunnel with the second user plane. The session management network element must convert the N6 address to the N4 address to successfully establish a tunnel between user plane network elements.

[0060] Optionally, the session management network element determines the N4 address of the first user plane network element based on the N6 address. This includes: the session management network element sending the N6 address to the data storage network element and receiving the N4 address returned by the data storage network element based on the N6 address. Alternatively, it can be obtained through other means, the principle of which is similar to obtaining the N6 address based on the N4 address as described above. Please refer to the above understanding, and it will not be repeated here.

[0061] A sixth aspect provides a communication method applied to a first user plane network element, the method comprising: the first user plane network element receiving a first data packet from a second user plane network element through a tunnel between the first user plane network element and a second user plane network element; the first user plane network element and the second user plane network element respectively corresponding to different data network access ranges; the first user plane network element converting a first address of the first data packet to a second address to obtain a second data packet; the second address being a unique address in the data network; and the first user plane network element sending the second data packet to the data network.

[0062] Therefore, when a tunnel is established between the first user plane network element and the second user plane network element, the first user plane network element can perform address translation of data packets in the tunnel, such as converting the first address of the first data packet into a unique second address in the data network, in order to avoid data transmission errors due to address conflicts.

[0063] In one possible design, the method described in the sixth aspect may further include: the first user plane network element determining the second address based on the first address and the identifier of the aforementioned tunnel. In this case, if data in different tunnels reuses the same address, the first user plane network element can also convert to different addresses based on the tunnel identifier, thus avoiding address conflicts.

[0064] A seventh aspect provides a communication device comprising a module for performing the method described in any one of the first to sixth aspects.

[0065] In one possible design, the communication device described in the seventh aspect may further include a transceiver. This transceiver may be a transceiver circuit or an interface circuit. The transceiver can be used for communication between the communication device described in the seventh aspect and other communication devices.

[0066] In one possible design, the communication device described in the seventh aspect may further include a memory. This memory may be integrated with the processor or disposed separately. The memory may be used to store instructions relating to the methods described in any of the first to sixth aspects.

[0067] In the embodiments of this application, the communication device described in the seventh aspect may be a network device, or a chip (system) or other component or assembly disposed in the network device, or a device containing the network device.

[0068] It is understood that the technical effects of the device described in the seventh aspect can also be referred to the relevant descriptions of the methods in any of the first to sixth aspects mentioned above, and will not be repeated here.

[0069] Eighthly, a communication device is provided. The communication device includes a processor coupled to a memory, the processor being configured to execute instructions stored in the memory such that the communication device performs the method described in any one of the first to sixth aspects.

[0070] In one possible design, the communication device described in the eighth aspect may further include a transceiver. This transceiver may be a transceiver circuit or an interface circuit. The transceiver can be used for communication between the communication device described in the eighth aspect and other communication devices.

[0071] In the embodiments of this application, the communication device described in the eighth aspect may be a network device described in any one of the first to sixth aspects, or a chip (system) or other component or assembly disposed in the network device, or a device containing the network device.

[0072] Furthermore, the technical effects of the communication device described in the eighth aspect can be referred to the technical effects of the method described in any one of the first to sixth aspects, and will not be repeated here.

[0073] A ninth aspect provides a communication device, comprising: a processor and a memory; the memory being used to store instructions that, when executed by the processor, cause the communication device to perform the method as described in any one of the first to sixth aspects.

[0074] In one possible design, the communication device described in the ninth aspect may further include a transceiver. This transceiver may be a transceiver circuit or an interface circuit. The transceiver can be used by the communication device described in the sixth aspect to communicate with other communication devices.

[0075] In the embodiments of this application, the communication device described in the ninth aspect may be a network device described in any one of the first to sixth aspects, or a chip (system) or other component or assembly disposed in the network device, or a device containing the network device.

[0076] Furthermore, the technical effects of the communication device described in the ninth aspect can be referred to the technical effects of the method described in any one of the first to sixth aspects, and will not be repeated here.

[0077] In a tenth aspect, a chip is provided, the chip comprising: a controller and an interface circuit, wherein the controller is configured to interact with other devices via the interface circuit to perform the method as described in any one of the first to sixth aspects.

[0078] Eleventhly, a communication system is provided. The communication system includes a data management network element for performing the method described in the first aspect and a terminal for performing the method described in the fourth aspect. Alternatively, the communication system includes a terminal for performing the method described in the fifth aspect and a policy control network element for performing the method described in the sixth aspect.

[0079] In a twelfth aspect, a computer-readable storage medium is provided, the computer-readable storage medium including storage of a computer program or instructions that, when executed, cause the method described in any one of the first to sixth aspects to be performed.

[0080] In a thirteenth aspect, a computer program product is provided, comprising a computer program or instructions that, when run, cause the method described in any one of the first to sixth aspects to be performed. Attached Figure Description

[0081] Figure 1 This is a schematic diagram of the 5GC architecture;

[0082] Figure 2 This is a schematic diagram illustrating a scenario of communication between EAS and AS.

[0083] Figure 3 This is a schematic diagram of the architecture of the communication system provided in the embodiments of this application;

[0084] Figure 4 Flowchart of the communication method provided in the embodiments of this application Figure 1 ;

[0085] Figure 5 Flowchart of the communication method provided in the embodiments of this application Figure 2 ;

[0086] Figure 6 Flowchart of the communication method provided in the embodiments of this application Figure 3 ;

[0087] Figure 7 Flowchart of the communication method provided in the embodiments of this application Figure 4 ;

[0088] Figure 8 Flowchart of the communication method provided in the embodiments of this application Figure 5 ;

[0089] Figure 9 Flowchart of the communication method provided in the embodiments of this application Figure 6 ;

[0090] Figure 10 Flowchart of the communication method provided in the embodiments of this applicationFigure 7 ;

[0091] Figure 11 Flowchart of the communication method provided in the embodiments of this application Figure 8 ;

[0092] Figure 12 Flowchart of the communication method provided in the embodiments of this application Figure 9 ;

[0093] Figure 13 Schematic diagram of the communication device provided in the embodiments of this application Figure 1 ;

[0094] Figure 14 Schematic diagram of the communication device provided in the embodiments of this application Figure 2 . Detailed Implementation

[0095] The technical solutions of this application embodiment can be applied to various communication systems, such as Wi-Fi wireless network systems, vehicle-to-everything (V2X) communication systems, device-to-device (D2D) communication systems, vehicle-to-everything (V2X) communication systems, fourth-generation (4G) mobile communication systems, such as long-term evolution (LTE) systems, worldwide interoperability for microwave access (WiMAX) communication systems, fifth-generation (5G) mobile communication systems, such as new radio (NR) systems, and future communication systems, such as 5.5G and sixth-generation (6G) mobile communication systems.

[0096] For ease of understanding, the technical terms used in this application will be introduced below.

[0097] 1. Fifth generation (5G) mobile communication system (5G system, 5GS):

[0098] Figure 1 This is a schematic diagram of the non-roaming architecture of 5GS. (Example:) Figure 1 As shown, 5GS includes: access network (AN) and core network (CN), and may also include: terminals.

[0099] The aforementioned terminal can be a terminal with transceiver capabilities, or a chip or chip system that can be installed on the terminal. This terminal can also be referred to as user equipment (UE), access terminal, user unit, user station, mobile station (MS), mobile station, remote station, remote terminal, mobile device, user terminal, terminal, wireless communication equipment, user agent, or user equipment. The terminals in the embodiments of this application may be mobile phones, cellular phones, smartphones, tablets, wireless data cards, personal digital assistants (PDAs), wireless modems, handsets, laptop computers, machine-type communication (MTC) terminals, computers with wireless transceiver capabilities, virtual reality (VR) terminals, augmented reality (AR) terminals, wireless terminals in industrial control, wireless terminals in self-driving, wireless terminals in remote medical care, wireless terminals in smart grids, wireless terminals in transportation safety, wireless terminals in smart cities, wireless terminals in smart homes, vehicle-mounted terminals, roadside units (RSUs) with terminal functions, etc. The terminal of this application may also be an on-board module, on-board unit, on-board component, on-board chip or on-board unit that is built into a vehicle as one or more components or units.

[0100] The aforementioned AN (Access Network Adapter) is used to implement access-related functions. It can provide network access functionality for authorized users in a specific area and determine transmission links of different quality based on user level and service requirements to transmit user data. The AN forwards control signals and user data between the terminal and the CN (Radio Access Network). The AN may include access network equipment, also known as radio access network (RAN) equipment. The CN is primarily responsible for maintaining the mobile network's subscription data and providing terminals with functions such as session management, mobility management, policy management, and security authentication. The CN mainly includes the following network elements: User Plane Function (UPF) network element, Authentication Server Function (AUSF) network element, Access and Mobility Management Function (AMF) network element, Session Management Function (SMF) network element, Network Slice Selection Function (NSSF) network element, Network Exposure Function (NEF) network element, Network Function Repository Function (NRF) network element, Policy Control Function (PCF) network element, Unified Data Management (UDM) network element, Unified Data Repository (UDR) network element, and Application Function (AF).

[0101] like Figure 1 As shown, the UE accesses the 5G network through the RAN device. The UE communicates with the AMF network element through the N1 interface (N1 for short); the RAN network element communicates with the AMF network element through the N2 interface (N2 for short); the RAN network element communicates with the UPF network element through the N3 interface (N3 for short); the SMF communicates with the UPF network element through the N4 interface (N4 for short), and the UPF network element accesses the data network (DN) through the N6 interface (N6 for short). Furthermore, Figure 2The control plane functions of the AUSF, AMF, SMF, NSSF, NEF, NRF, PCF, UDM, UDR, or AF network elements shown above interact using service-oriented interfaces. For example, the service-oriented interface provided by the AUSF network element is Nausf; that of the AMF network element is Namf; that of the SMF network element is Nsmf; that of the NSSF network element is Nnssf; that of the NEF network element is Nnef; that of the NRF network element is Nnrf; that of the PCF network element is Npcf; that of the UDM network element is Nudm; that of the UDR network element is Nudr; and that of the AF network element is Naf.

[0102] RAN equipment can be a device that provides access to terminals. For example, RAN equipment may include: next-generation mobile communication system, such as 6G access network equipment, such as 6G base station, or in next-generation mobile communication system, the network equipment may also have other naming methods, all of which are covered within the protection scope of the embodiments of this application, and this application does not limit them in any way. Alternatively, RAN equipment may also include 5G, such as gNB in ​​a new radio (NR) system, or one or a group of antenna panels (including multiple antenna panels) of a 5G base station, or it may be a network node constituting a gNB, transmission and reception point (TRP or transmission point (TP)) or transmission measurement function (TMF), such as a building base band unit (BBU), or a centralized unit (CU) or distributed unit (DU), an RSU with base station function, or a wired access gateway, or a 5G core network element. Alternatively, RAN equipment may also include access points (APs) in wireless fidelity (WiFi) systems, wireless relay nodes, wireless backhaul nodes, various forms of macro base stations, micro base stations (also known as small stations), relay stations, access points, wearable devices, vehicle-mounted equipment, and so on.

[0103] UPF network elements are primarily responsible for user data processing (forwarding, receiving, billing, etc.). For example, a UPF network element can receive user data from a data network (DN) and forward that data to the terminal through access network equipment. A UPF network element can also receive user data from the terminal through access network equipment and forward that data to the DN. A DN network element refers to the operator's network that provides data transmission services to users. Examples include Internet Protocol (IP), IP Multimedia Service (IMS), and the Internet. A DN can be an external network of the operator or a network controlled by the operator, used to provide services to terminal devices.

[0104] The AUSF network element is mainly used to perform security authentication for terminals.

[0105] AMF network elements are primarily used for mobility management in mobile networks. Examples include user location updates, user network registration, and user handover.

[0106] SMF network elements are primarily used for session management in mobile networks. This includes tasks such as session establishment, modification, and release. Specific functions include assigning Internet Protocol (IP) addresses to users and selecting UPF network elements that provide packet forwarding capabilities.

[0107] The PCF network element primarily supports providing a unified policy framework to control network behavior, providing policy rules to the control layer network functions, and is also responsible for acquiring user subscription information related to policy decisions. The PCF network element can provide policies to the AMF and SMF network elements, such as Quality of Service (QoS) policies and slice selection policies.

[0108] NSSF network elements are mainly used to select network slices for terminals.

[0109] NEF network elements are primarily used to support the opening of capabilities and events.

[0110] UDM network elements are mainly used to store user data, such as subscription data and authentication / authorization data.

[0111] UDR network elements are mainly used to store structured data, including contract data, policy data, externally exposed structured data, and application-related data.

[0112] AF primarily supports interaction with CN to provide services, such as influencing data routing decisions, policy control functions, or providing third-party services to the network side.

[0113] 2. EAS Deployment Information:

[0114] 3GPP TS23.548 defines Edge Application Server (EAS) deployment information (EDI). EAS deployment information reflects the network deployment at the edge, including information such as the EAS address, DNS server information, and Full Qualified Domain Name (FQDN). It also includes identifiers for these edge services provided by the 5GC, such as the Data Network Access Identifier (DNAI), the Data Network Name (DNN) corresponding to the EAS, and Single Network Slice Selection Assistance Information (S-NSSAI). The DNAI is a concept related to service deployment and geographical location, and its function is to identify a network access point. A DNAI can include one or more UPFs and EASs. For example, if an edge data center is deployed in area A, containing two EASs, and the 5GC has two UPFs directly connected to this data center (e.g., fiber optic connections), these two EASs and two UPFs belong to the same DNAI, such as the DNAI for area A.

[0115] EAS deployment information reflects the correspondence between these information. For example, it includes one or more of the following: the FQDN range, the EAS IP address range, and the DNS server identifier for each DNAI. If a service's FQDN or EAS IP falls within the above range, it indicates that the service is deployed at the local edge.

[0116] EAS deployment information is stored in the UDR network element, and the SMF network element can obtain EAS deployment information from the UDR network element. For example, the SMF provides a DNN and / or S-NSSAI to the UDR network element, thereby obtaining EAS deployment information related to this DNN and / or S-NSSAI.

[0117] 3. Packet routing:

[0118] A DN can include a local data network (L-DN) and a central data network (central-DN). A DN can include one or more servers (such as EAS, AS, etc.). For example, EAS is in an L-DN and AS is in a central-DN.

[0119] Key issue #3 of 3GPP TR23700-49 discusses packet routing between L-DN and central-DN. This problem assumes that the EAS in the L-DN and the AS in the central DN need to communicate, but the L-DN and central-DN are not interoperable (i.e., the EAS cannot directly send packets to the AS in the DN and receive them via IP routing). 3GPP aims to propose a solution that uses the CN (Network Connector) to facilitate connection establishment between the L-DN and central-DN, thereby enabling communication between the EAS and AS.

[0120] like Figure 3 As shown, in the discussion, one proposed solution is to establish a node-level tunnel (i.e., independent of the UE's PDU session) connecting the L-DN and central-DN, thereby enabling communication between the EAS and AS. Specifically, an L-UPF (capable of connecting / communicating with the EAS) is selected in the data network access identifier (DNAI) of the EAS. A node-level tunnel is then established between this L-UPF and a central UPF (a UPF capable of connecting / communicating with the central-DN). In this solution, the AF indicates to the 5GC that a tunnel needs to be established, including the DNAI for which the tunnel needs to be established. After receiving the indication, the SMF network element selects an L-UPF within that DNAI and instructs this L-UPF to establish a node-level tunnel with a central UPF, or in other words, a tunnel from the L-UPF to the central UPF. Thus, after the node-level tunnel is established, the EAS can communicate with the AS through this tunnel. At this time, the data packet transmission path is: EAS->L-UPF->central-UPF->AS (and vice versa).

[0121] Although a node-level tunnel connecting the L-DN and the central DN has been established, it is still necessary to ensure that packets sent from the EAS to the AS can be correctly routed to the L-UPF, and then sent through the tunnel to the central DN, and subsequently to the AS. For example, among the UPF network elements connected to the L-DN (such as UPF 1 and UPF 2), only UPF 1 has established a node-level tunnel to the central DN, while UPF 2 cannot connect to the central DN. In this case, if a data packet sent from the EAS to the AS is routed to UPF 2, this data packet cannot be routed to the AS, resulting in transmission failure. Therefore, ensuring that packets sent from the EAS to the AS are routed to the L-UPF with the established tunnel is a problem that needs to be solved.

[0122] To address the aforementioned technical problems, the embodiments of this application propose the following technical solutions.

[0123] The technical solutions in this application will now be described with reference to the accompanying drawings.

[0124] In the embodiments of this application, "instruction" can include direct and indirect instructions, as well as explicit and implicit instructions. The information indicated by a certain piece of information is called the information to be instructed. In the specific implementation process, there are many ways to instruct the information to be instructed, such as, but not limited to, directly instructing the information to be instructed, such as the information to be instructed itself or its index. It can also indirectly instruct the information to be instructed by instructing other information, where there is a relationship between the other information and the information to be instructed. It can also instruct only a part of the information to be instructed, while the other parts are known or pre-agreed upon. For example, the instruction of specific information can be achieved by using a pre-agreed (e.g., protocol-defined) arrangement of various pieces of information, thereby reducing instruction overhead to some extent. At the same time, common parts of various pieces of information can be identified and uniformly indicated to reduce the instruction overhead caused by individually indicating the same information.

[0125] Furthermore, the specific indication method can also be any existing indication method, such as, but not limited to, the above-mentioned indication methods and their various combinations. Specific details of various indication methods can be found in existing technologies, and will not be repeated here. As described above, for example, when multiple pieces of information of the same type need to be indicated, the indication methods for different pieces of information may differ. In the specific implementation process, the required indication method can be selected according to specific needs. This application embodiment does not limit the selected indication method; therefore, the indication methods involved in this application embodiment should be understood to cover various methods that enable the party to be indicated to obtain the information to be indicated.

[0126] It should be understood that the information to be indicated can be sent as a whole or divided into multiple sub-information messages sent separately, and the sending period and / or timing of these sub-information messages can be the same or different. The specific sending method is not limited in this application embodiment. The sending period and / or timing of these sub-information messages can be predefined, for example, according to a protocol, or configured by the sending device by sending configuration information to the receiving device.

[0127] In this application, "sending information" can be understood as one device sending information to another device, or it can also be understood as one logical module within a device sending information to another logical module. For example, "network device sending information" can be understood as a network device sending information to another device (such as a terminal or other network device), or it can be understood as logical module 1 in the network device sending information to logical module 2 in the network device.

[0128] In this application, "receiving information" can be understood as one device receiving information from another device, or it can also be understood as a logical module within a device receiving information from another logical module. For example, "network device receiving information" can be understood as a network device receiving information from another device (such as a terminal or other network device), or it can be understood as logical module 1 in the network device receiving information from logical module 2 in the network device.

[0129] In this application, phrases such as "sending information to... (e.g., a terminal)" or related illustrations in the accompanying drawings can be understood as indicating that the destination of the information is a terminal. This can include sending information directly or indirectly to a terminal. Similarly, phrases such as "receiving information from... (e.g., a terminal)," "receiving information from... (e.g., a terminal)," or "receiving information sent by (e.g., a terminal)," or related illustrations in the accompanying drawings, can be understood as indicating that the source of the information is a terminal. This can include receiving information directly or indirectly from a terminal. Information may undergo necessary processing between the source and destination, such as format changes, but the destination can understand the valid information from the source. Similar expressions in this application can be interpreted similarly and will not be elaborated further here.

[0130] "Predefined" or "pre-configured" can be achieved by pre-saving corresponding codes, tables, or other means that can be used to indicate relevant information in the device. This application does not limit the specific implementation method. "Saving" can refer to saving in one or more memories. These memories can be separate installations or integrated into the encoder, decoder, processor, or communication device. Alternatively, some memories can be separately installed, while others are integrated into the decoder, processor, or communication device. The type of memory can be any form of storage medium, and this application does not limit this.

[0131] The “protocol” mentioned in the embodiments of this application may refer to a protocol family in the field of communication, a standard protocol with a similar protocol family frame structure, or a related protocol applied to future communication systems. The embodiments of this application do not specifically limit this.

[0132] In the embodiments of this application, descriptions such as "when," "under the circumstances," "if," and "if" all refer to the device making corresponding processing under certain objective circumstances, and are not limited to a specific time. They do not require the device to make a judgment action during implementation, nor do they imply any other limitations.

[0133] In the description of the embodiments of this application, unless otherwise stated, " / " indicates that the objects before and after are in an "or" relationship. For example, A / B can represent A or B. "And / or" in the embodiments of this application is merely a description of the relationship between related objects, indicating that three relationships can exist. For example, A and / or B can represent: A alone, A and B simultaneously, and B alone, where A and B can be singular or plural. Furthermore, in the description of the embodiments of this application, unless otherwise stated, "multiple" refers to two or more. "At least one of the following" or similar expressions refer to any combination of these items, including any combination of single or plural items. For example, at least one of a, b, or c can represent: a, b, c, ab, ac, bc, or abc, where a, b, and c can be single or multiple. Additionally, to facilitate a clear description of the technical solutions of the embodiments of this application, the terms "first" and "second" are used in the embodiments of this application to distinguish identical or similar items with essentially the same function and effect. Those skilled in the art will understand that the terms "first," "second," etc., do not limit the quantity or order of execution, and that "first," "second," etc., are not necessarily different. Furthermore, in the embodiments of this application, words such as "exemplary" or "for example" are used to indicate that something is being used as an example, illustration, or description. Any embodiment or design scheme described as "exemplary" or "for example" in the embodiments of this application should not be construed as being more preferred or advantageous than other embodiments or design schemes. Specifically, the use of words such as "exemplary" or "for example" is intended to present the relevant concepts in a concrete manner for ease of understanding.

[0134] The network architecture and business scenarios described in the embodiments of this application are for the purpose of more clearly illustrating the technical solutions of the embodiments of this application, and do not constitute a limitation on the technical solutions provided in the embodiments of this application. As those skilled in the art will know, with the evolution of network architecture and the emergence of new business scenarios, the technical solutions provided in the embodiments of this application are also applicable to similar technical problems.

[0135] To facilitate understanding of the embodiments of this application, a communication system will be used as an example to describe in detail the communication system applicable to the embodiments of this application.

[0136] Figure 4 This is a schematic diagram of the architecture of a communication system, which mainly includes at least one of the following: user plane network element, session management network element, or application function network element.

[0137] User plane network elements can be the UPF network elements mentioned above, or in future communication systems, user plane network elements can be replaced with any other possible names. Session management network elements can be the SMF network elements mentioned above, or in future communication systems, session management network elements can be replaced with any other possible names. Application function network elements can be the AF network elements mentioned above, or in future communication systems, application function network elements can be replaced with any other possible names.

[0138] In one possible scenario, tunnels can be established between different user plane network elements, such as the first user plane network element and the second user plane network element. In this case, the session management network element can instruct the first user plane network element to establish a route between itself and the edge application server, ensuring that data can be correctly routed from the edge application server to the first user plane network element, and finally routed to the application server through the tunnel. This ensures the stability and reliability of communication between the edge application server and the application server, and avoids communication failures.

[0139] In another possible scenario, when the first user plane network element and the second user plane network element establish a tunnel, the session management network element can expose the address information of the first user plane network element, which is in the same data network access range as the edge application server, to the application function network element. This allows the application function network element to instruct the edge application server to configure routing with the first user plane network element, ensuring that data can be correctly routed from the edge application server to the first user plane network element and finally routed to the application server through the tunnel. This guarantees the stability and reliability of communication between the edge application server and the application server, and avoids communication failures.

[0140] In another possible scenario, the application function network element can proactively configure the routing between the first user plane network element and the edge application server corresponding to the same data network access range, and provide the address information of the first user plane network element to the session management network element. Then, the session management network element can establish a tunnel between the first user plane network element and the second user plane network element based on the address information of the first user plane network element, so as to realize communication between the two data network access ranges.

[0141] In another possible scenario, when a tunnel is established between the first user plane network element and the second user plane network element, the first user plane network element can translate the address of the data packets in the tunnel, such as converting the first address of the first data packet to a unique second address in the data network, in order to avoid data transmission errors due to address conflicts.

[0142] The communication method and apparatus of the present application embodiments will be further described below with reference to the accompanying drawings. It is understood that the present application uses network devices and terminals as examples of the execution subjects in the interaction illustration, but the present application does not limit the execution subjects of the interaction illustration. For example, the method executed by the network device in the present application can also be executed by a module applied to the network device (e.g., a chip, chip system, or processor), or by a logical node, logical module, or software capable of implementing all or part of the network device's functions; similarly, the method executed by the terminal in the present application can also be executed by a module applied to the terminal (e.g., a chip, chip system, or processor), or by a logical node, logical module, or software capable of implementing all or part of the terminal's functions.

[0143] The interaction process between various network elements / devices in the above-described communication system will be specifically described below through method embodiments. The communication method provided in this application embodiment can be applied to the above-described communication system and specifically applied to various scenarios mentioned in the above-described communication system, which will be described in detail below.

[0144] Figure 1 Flowchart of the communication method provided in the embodiments of this application Figure 4 This communication method is applicable to the aforementioned communication system and mainly involves the interaction between the first user plane network element and the session management network element.

[0145] like Figure 4 As shown, the specific process is as follows:

[0146] S401, the session management network element receives edge application service information from the application function network element.

[0147] Edge application service information (EIA) indicates a communication need (or connection / tunneling) between two data network access ranges. A data network access range can also be understood as (or alternatively, as) a data network or DNAI; therefore, two data network access ranges can be understood as two data networks or two DNAIs. For example, the two data network access ranges are a first data network access range and a second data network access range. The first data network access range can be replaced with the first data network, such as an L-DN, or with the first DNAI, such as a local DNAI. The second data network access range can be replaced with the second data network, such as a central DN / DN, or with the second DNAI, such as a central DNAI. Based on this, EIA can also be considered as indicating a communication need / connection / tunneling between two data networks / two DNAIs.

[0148] For example, edge application service information may include at least one of the following: indication cells, edge application server information.

[0149] Indication elements can be used to indicate the establishment of a tunnel (or node-level tunnel). This tunnel can be applicable to communication between two nodes (or node devices), regardless of the type of data or service transmitted or the terminal / session corresponding to the data. Communication between two data network access areas can be achieved through tunneling. For example, if a user plane network element corresponding to the first data network access area establishes a tunnel with a user plane network element corresponding to the second data network access area, then indicating the establishment of a tunnel can also indicate a communication requirement / tunnel between the two data network access areas. Alternatively, indication elements can be used to indicate traffic routing between a local DN and a central DN.

[0150] Information about edge application servers can be used to represent the characteristics / location of edge application servers.

[0151] For example, the information of the edge application server can be the address or FQDN of the edge application server, such as an IP address, or it can be other addresses, such as a medium access control (MAC) address, so as to represent the characteristics of the edge application server through the address of the edge application server.

[0152] For example, the information of the edge application server can be a first DNAI, which indicates the location of the edge application server, that is, the edge application server is located within the first data network access range. This is also referred to as the edge application server corresponding to the first DNAI, and it also indicates that a tunnel needs to be established for this first DNAI. Optionally, the edge application service information can also include information indicating whether the DNAI contained in the edge application service information is a local DNAI or a central DNAI. In this case, the DNAI contained in the edge application service information is the first DNAI, that is, the information indicates that it is a local DNAI. Optionally, if one application function network element corresponds to one DNAI, the information of the edge application server may not include the first DNAI. The session management network element can determine the first DNAI corresponding to the edge application server based on the application function network element that sent the edge application service information.

[0153] Of course, the information above is only a few examples. The information of the edge application server can also be any other information that can represent the location / characteristics of the edge application server. There are no restrictions on the specific implementation.

[0154] Optionally, when the edge application service information includes an indication cell and information about the edge application server, the indication cell and the information about the edge application server correspond. For example, the edge application server information includes a first DNAI, and the indication cell indicates that a tunnel needs to be established between the first DNAI and the second DNAI. As another example, the edge application server information includes a first DNAI and a second DNAI, and the indication cell indicates that a tunnel needs to be established between the first DNAI and the second DNAI.

[0155] Optionally, the edge application service information may also indicate the services corresponding to the two data network access ranges mentioned above, such as information corresponding to these two data network access ranges: service identifiers, such as fully qualified domain name (FQDN) and / or application identifiers (APP ID), edge application server addresses (such as IP addresses), or edge application server address ranges (EAS IP ranges), etc. If the service data contains this information, it indicates that the service is a service corresponding to these two data network access ranges.

[0156] It is understandable that edge application service information can be existing information, such as EDI. This EDI can also contain other information. For specific implementation, please refer to the relevant introduction in "3. EAS Deployment Information" above, which will not be repeated here. Alternatively, edge application service information can also be newly defined information in the future, and there are no restrictions on the specific naming.

[0157] It can also be understood that the statement that the session management network element receives edge application service information from the application function network element is only an exemplary description. The network open network element (such as the NEF network element) obtains edge application service information from the application function network element or the data storage network element (such as the UDR network element), and the session management network element then obtains edge application service information from the network open network element. Therefore, it can also be said that the session management network element obtains edge application service information from the network open network element, the application function network element, or the data storage network element.

[0158] It should be noted that S401 is an optional step, and the solution in this application embodiment can also start from S402.

[0159] S402, the session management network element sends a first message and a first instruction information to the first user plane network element. The first user plane network element receives the first message and the first instruction information.

[0160] The first instruction information is used to instruct the first user plane network element to establish a tunnel with the second user plane network element, such as the tunnel mentioned above. That is, the tunnel is used for communication between the first user plane network element and the second user plane network element, or for data packet routing between edge application servers and application servers / cloud application servers / central application servers / remote application servers. It can also be called for data packet routing between L-DN and central DN.

[0161] For example, the first user plane network element corresponds to the first data network access range, or it can be expressed as the first user plane network element corresponding to the first data network / first DNAI. The first DNAI can be a local DNAI, meaning the first user plane network element can be an L-UPF network element. The session management network element can determine the first user plane network element based on edge application service information, such as the deployment information of the edge application server. If existing technologies are reused, please refer to 3GPP TS23.548 for details, which will not be elaborated here. The second user plane network element corresponds to a different data network access range than the first user plane network element, such as the second user plane network element and the first user plane network element each corresponding to a different data network / DNAI. For example, the second user plane network element corresponds to the second data network access range, or it can be expressed as the second user plane network element corresponding to the second data network / second DNAI. The second DNAI is a central DNAI, meaning the second user plane network element can be a central UPF network element.

[0162] Optionally, a user plane network element corresponds to a DNAI, or it can be said that the user plane network element belongs to a DNAI. A user plane network element corresponds to a DN (local DN / central DN), or it can be said that the user plane network element belongs to / corresponds to a DNAI, which is the same as one or more EAS / AS in the DN belonging to / corresponding to a DNAI.

[0163] The first indication information may contain a cell / field / string. For example, a field may be denoted as field #1, where field #1 is a bit with a value of 1, indicating that a tunnel needs to be established. If the value of this bit is 0, it indicates that field #1 is empty. In this case, the second user plane network element can be understood as not a specific user plane network element, but rather as a network element different from the first user plane network element. It can be replaced by other user plane network elements. The specific user plane network element with which to establish a tunnel can be determined by the first user plane network element itself, and this application embodiment does not impose any restrictions. Alternatively, the first indication information may also contain information about the second user plane network element, such as the identifier / address / tunnel information of the second user plane network element. That is, the second user plane network element can be a specific user plane network element, used to indicate that the first user plane network element needs to establish a tunnel with that specific user plane network element, or to indicate the rules for the first user plane network element to forward data packets to that specific user plane network element. For example, the first indication information is PDR and / or FAR, indicating that the first user plane network element needs to forward data packets received from the N6 interface to the tunnel and / or address corresponding to the second user plane network element. Optionally, the data packets received from the N6 interface are data packets received from the N6 interface whose source / destination addresses include an edge application server or an application server address.

[0164] Optionally, the first indication information may also include information about the first user plane network element, such as the identifier / address / context identifier of the first user plane network element, so as to jointly indicate that the first user plane network element needs to establish a tunnel with the second user plane network element by using the information of the first user plane network element, together with the aforementioned field #1 and / or the information of the second user plane network element. Alternatively, the first indication information may not include information about the first user plane network element. In this case, the transmission relationship of the information elements can be used to implicitly indicate which network element / device needs to establish a tunnel. For example, if the first user plane network element receives the first indication information, it means that the first user plane network element needs to establish a tunnel with the second user plane network element.

[0165] The first message can be an existing message, such as an N4 message, like a message used to configure node-level N4 rules (such as establishing a tunnel or configuring a route in the embodiments of this application), or it can be a newly defined message in the future; there are no specific limitations. The first message may contain first indication information.

[0166] The first message can also contain a second or third instruction. That is, the second (or third) instruction and the first instruction can be transmitted through the same message, with relatively low communication overhead. Alternatively, the second (or third) instruction and the first instruction can be transmitted through different messages, which allows for more flexible message transmission. This will be discussed below.

[0167] The second indication information can be used to indicate (display indication) the routing configuration (or routing via user plane configuration) of the first user plane network element, such as the routing (or packet routing) between the first user plane network element and one or more edge application servers. These one or more edge application servers correspond to the same data network access range / data network / DNAI as the first user plane network element, such as the first data network access range / first data network / first DNAI. For example, the second indication information can be an information element / field / string with indication capabilities. For instance, let's say a field, denoted as field #2. Field #2 is a bit with a value of 1, used to indicate that the user plane network element needs to configure its routing with one or more edge application servers. If the value of this bit is 0, it means that field #2 is empty. In this case, "one or more edge application servers" can be a general term for edge application servers, that is, it does not limit which specific edge application servers are being configured, but rather the edge application servers corresponding to the first data network access range / first data network / first DNAI.

[0168] Optionally, the second indication information may also include information about the first user plane network element to indicate that the first user plane network element itself needs to configure routing. Alternatively, the second indication information may not include information about the first user plane network element, such as if the first indication information already includes information about the first user plane network element, or it may implicitly indicate which network element / device needs to configure routing through the transmission relationship of information elements. For example, if the first user plane network element receives the second indication information, it means that the first user plane network element itself needs to configure routing.

[0169] The third indication information can be used to indicate the identifier or address (such as IP address) of at least one edge application server or the address range (EAS IP range) of the edge application server, so as to implicitly indicate the first user plane network element to configure routing, such as the routing between the first user plane network element and the at least one edge application server, or the routing (or packet routing) between edge application servers with addresses in the address range.

[0170] For example, at least one edge application server belongs to one or more of the aforementioned edge application servers, such as at least some of these edge application servers, or at least some of the edge application servers corresponding to the first DNA. That is, among the edge application servers capable of establishing routes with the first user plane network element, the session management network element can select some or all of the edge application servers to establish routes with the first user plane network element. The specific selection can be based on actual conditions, such as the load of the edge application servers and communication latency, to ensure that the routing between them meets actual communication needs. The address of at least one edge application server can be a continuous address or a non-contiguous address; there is no specific restriction. The address of at least one edge application server can be represented by an address table, such as an edge application server address table (EAS IP List), or by any other possible method; there is no specific implementation restriction. The address range of the edge application server can be an address range composed of the addresses of various edge application servers (such as the addresses of at least some of the aforementioned edge application servers). The address range of an edge application server can be a continuous address range, such as IP x1 to IP x2, or it can be multiple non-contiguous address ranges, such as IP x1 to IP x2 and IP y1 to IP y2, where IP x2 and IP y1 are not contiguous. The address range of an edge application server may include the addresses of at least one of the aforementioned edge application servers, or it may not include them; there is no specific restriction.

[0171] The third indication information can be used to display the address or address range of at least one edge application server, such as including the address or address range of at least one edge application server. Alternatively, the third indication information can also be used to implicitly indicate the address or address range of at least one edge application server, such as including information like the first DNAI, or the identifier of the service (such as FQDN and / or the identifier of the application), which corresponds to the address or address range of at least one edge application server. This application embodiment does not limit the way the session management network element obtains this information; it can obtain it from edge application service information or indication information, or from information pre-configured locally on the session management network element, or from any other possible network element. Optionally, the first user plane network element can determine the address or address range of the corresponding at least one edge application server based on the third indication information and the stored correspondence. The first user plane network element can configure this correspondence locally or obtain it from other network elements.

[0172] Optionally, the third indication information may also include information about the first user plane network element. Alternatively, the third indication information may not include information about the first user plane network element, such as when the first indication information / second indication information already includes information about the first user plane network element, or when the transmission relationship of information elements implicitly indicates which network element / device needs to configure routing. For example, if the first user plane network element receives the third indication information, it means that the first user plane network element itself needs to configure routing.

[0173] It is understood that the second and third instruction information can also be implemented in combination. For example, the first message may contain the second and third instruction information to jointly instruct the first user plane network element to configure its routing with at least one edge application server (or an edge application server whose address is within the above address range).

[0174] In this embodiment, the session management network element can send the first message and the first instruction information to the first user plane network element at different times, which will be described below.

[0175] In the first possible scenario, the session management network element can send a first message to the first user plane network element based on the edge application service information. Correspondingly, the first user plane network element can receive the first message. In this case, the first message may contain first indication information, and at least one of second and third indication information. That is, the establishment of a tunnel between the first user plane network element and the second user plane network element, and the configuration of the route between the first user plane network element and the edge application server, can occur simultaneously. This avoids communication failures caused by either a tunnel being established but the route not being configured, or vice versa.

[0176] In the second possible scenario, the session management network element can send a first message to the first user plane network element based on edge application service information. The first user plane network element can then receive the first message. In this case, the first message may contain first indication information but not either the second or third indication information, used by the first user plane network element to establish a tunnel. Optionally, the session management network element can also determine the terminal's session requirements (or session characteristics) and send at least one of the aforementioned information to the first user plane network element based on these requirements. For example, the session management network element can send a second message to the first user plane network element based on the session requirements, and the user plane network element can then receive the second message. The second message can be different from the first message. For instance, the second message can be an existing message, such as an N4 message used to configure node-level N4 rules, or it can be a newly defined message in the future; there are no specific limitations. The second message can contain at least one of the aforementioned information to instruct it to configure routing.

[0177] Session requirements may include the need for a terminal's session (such as a protocol data unit (PDU) session) to be routed between two data network access ranges. In other words, when data actually needs to be transmitted between two data network access ranges, the session management network element can instruct the first user plane network element to configure the route between itself and the edge application server, so as to avoid redundancy caused by pre-configuring routes.

[0178] For example, the session management network element can obtain EDI. This EDI can be associated with the data network and / or slice corresponding to the terminal's session. The specific implementation of this EDI can be found in the relevant introduction in "3. EAS Deployment Information" above, and will not be repeated here.

[0179] Specifically, for a terminal session, the session management network element can obtain the data network and / or slice corresponding to the session, such as the data network name (DNN) and / or single network slice selection assistance information (S-NSSAI), or any other possible information. The session management network element can obtain the EDI corresponding to the data network and / or slice for the session from the terminal's subscription data stored by the data management network element (such as the UDM network element). If the EDI includes information indicating a communication requirement between two data network access ranges, such as an indication from the application function network element to establish a tunnel and / or a first DNAI, the session management network element determines, based on this information, that the terminal's session has a routing requirement between the two data network access ranges and sends a second message to the first user plane network element to instruct it to configure routing.

[0180] For example, the session management network element instructs the network element serving the session of the aforementioned terminal to detect whether the data of the session is associated with two data network access ranges; if the data of the session is associated with two data network access ranges, the session management network element determines that the session has a need for routing between the two data network access ranges; otherwise, the session does not have a need for routing between the two data network access ranges.

[0181] Specifically, the network element serving the aforementioned terminal's session can be the user plane network element or the edge application server discovery network element corresponding to the session, such as the edge application server discovery function (EASDF). The session management network element can instruct the network element serving the session to detect whether the data in the session contains services corresponding to the two data network access ranges. For example, the session management network element configures detection rules for the network element serving the session, and these detection rules include services corresponding to the two data network access ranges. The specific implementation of the services corresponding to the two data network access ranges can be found in the relevant description in S401 above, and will not be repeated here. The services corresponding to the two data network access ranges can be obtained by the session management network element from the edge application service information, or pre-configured locally on the session management network element; there are no specific restrictions. In this case, if the data in the session contains services corresponding to the two data network access ranges, it means that the data in the session is associated with the two data network access ranges; otherwise, the data in the session is not associated with the two data network access ranges. For example, if a network element serving a session detects, according to the detection rule, that the data of the session contains services corresponding to two data network access ranges, then the network element serving the session reports the detected information, i.e., the services corresponding to the two data network access ranges, to the session management network element; otherwise, no report is made. The session management network element can determine the association between the data of the session and the two data network access ranges based on the information reported by the network element serving the session. Based on this, the session management network element can determine the DNAI corresponding to one or more of the information reported by the network element serving the session, EDI, or the location of the terminal, such as the first DNAI. The location of the terminal can be obtained by the session management network element through subscription to the access and mobility management network element (such as the AMF network element) serving the terminal. Thus, the session management network element can send a second message to the user plane network element (i.e., the first user plane network element) corresponding to the first DNAI and already instructed to establish a tunnel, to instruct it to configure routing.

[0182] As can be seen in the two examples above, the session management network element can determine whether the terminal's session requires routing between the two data network access ranges through either the control plane or the user plane. The specific method used can be flexibly chosen based on the actual situation and is not restricted here. Alternatively, the session management network element can also achieve this through other methods. For example, the session management network element can directly determine the DNAI indicated in the aforementioned edge application service information, or in other words, the DNAI for which a tunnel needs to be established (such as the first DNAI), including the DNAI corresponding to the terminal's location, based on the terminal's location, and then send a second message to the first user plane network element to instruct it to configure routing.

[0183] S403, the first user plane network element configures the routing between the first user plane network element and one or more edge application servers according to the first message.

[0184] The first user plane network element can also establish a tunnel between the first user plane network element and the second user plane network element according to the first instruction information. This can be achieved by reusing existing technologies. For example, the process of establishing a tunnel between UPFs in the session establishment process can be referred to 3GPP TS23.502, which will not be elaborated here.

[0185] One possible design scheme is that the first message may include first instruction information. The first user plane network element can configure the route between the first user plane network element and one or more edge application servers according to the first instruction information in the first message. That is, the route is established by reusing existing information, without additional signaling overhead. The implementation difficulty and complexity are relatively low, and the support for standards is also more friendly.

[0186] For example, the first user plane network element broadcasts default route information via the user plane according to the first instruction information in the first message. Within the scope of the broadcast default route information, one or more edge application servers are involved. This default route information indicates that if a data packet does not match the routing table, the data packet needs to be routed to the first user plane network element; that is, a default route, which can also be replaced by a default route / router, or simply a default route to the first user plane network element. For example, the default route can be a special route used only when no matching entry in the routing table is found. For instance, if the destination address of a data packet (or message) cannot match any entry in the routing table, the edge application server selects a default route for the data packet. Thus, even if multiple user plane network elements can communicate with the edge application server, the data packet will only be sent to the first user plane network element, ensuring communication between the edge application server and the first user plane network element and preventing communication failure between the edge application server and the application server.

[0187] It should be understood that the default routing information is an exemplary name and can be replaced with any possible name, such as default route or default routing information. Alternatively, the first user plane network element can also broadcast other information on the user plane, such as indicating through user plane route broadcasts that it can connect to the central DN. In this way, the edge application server can route data packets destined for the central DN to the first user plane network element.

[0188] Another possible design scheme is that the first message may include second indication information. The first user plane network element can configure routing between itself and one or more edge application servers based on the second indication information in the first message. This establishes routing through a newly defined information element (the second indication information), decoupling it from existing information elements and allowing for greater flexibility. For example, the first user plane network element can broadcast default routing information via the user plane based on the second indication information in the first message. The one or more edge application servers mentioned above are within the range of this broadcast default routing information. For specific implementation details, please refer to the relevant description in the above possible design scheme; further elaboration will not be repeated here.

[0189] Another possible design scheme is that the first message may include third indication information. For example, if the third indication information indicates the address of at least one edge application server, the first user plane network element can configure routing between itself and at least one edge application server via the user plane based on the third indication information in the first message. As another example, if the third indication information indicates a range of edge application server addresses, the first user plane network element can configure routing between itself and at least some of the edge application servers within that address range via the user plane based on the third indication information in the first message. The routing configuration between the first user plane network element and at least one edge application server or at least some of the edge application servers in the address range can be as follows: the first user plane network element establishes a tunnel with each edge application server, such as an IP over IP tunnel, a generic route encapsulation (GRE) tunnel, a GPRS tunneling protocol for the user plane (GTP-U) tunnel, or other methods, as long as it can ensure that the data packets sent by the edge application server to the application server can be routed to the first user plane network element. There are no restrictions on the specific protocols or actions used by the first user plane network element.

[0190] Therefore, data packets from at least one or more edge application servers can be correctly routed to the first user plane network element, which then sends them to the second user plane network element through a tunnel, and finally the second user plane network element sends them to the data network.

[0191] Optionally, in S402, the session management network element can also provide additional information for user plane configuration to the first user plane network element. For example, this information can be used to instruct the first user plane network element to configure user plane behavior, such as the protocol type used by the first user plane network element to configure the tunnel between the first user plane network element and the edge application server, and the settings of the default route broadcast, such as the scope of influence and the routing path. The embodiments of this application do not limit the content and form of this information.

[0192] In summary, when the first user plane network element establishes a tunnel (or node tunnel) with the second user plane network element, the first user plane network element also establishes a route between itself and one or more edge application servers. This ensures that data can be correctly routed from one or more edge application servers to the first user plane network element, and finally routed to the application server through the tunnel. This guarantees the stability and reliability of communication between the edge application servers and the application server, and avoids communication failures.

[0193] The above combination Figure 5-6 The overall process of the communication method provided in the embodiments of this application in the first scenario is described in detail below, in conjunction with... Figure 5 This section describes the specific process of this communication method in this scenario.

[0194] Figure 2 Flowchart of the communication method provided in the embodiments of this application Figure 5 This communication method is applicable to the aforementioned communication system and mainly involves the interaction between L-UPF network elements (such as the first user plane network element), SMF network elements (such as the session management network element), EAS, and AF (such as the application function network element).

[0195] Specifically, such as Figure 6 As shown, the flow of this communication method is as follows:

[0196] S501, AF sends EDI to SMF network element.

[0197] EDI may include the DNAI where the EAS is located, such as the first DNAI. Optionally, it may also include an indicator cell (used to explicitly indicate the establishment of a tunnel) and information indicating whether the DNAI is an L-DNAI or a central DNAI. For specific implementation details, please refer to the relevant introduction in "Edge Application Service Information" above, which will not be repeated here. AF can send EDI to SMF network elements through NEF. For details, please refer to the relevant introduction in S401 above, which will not be repeated here.

[0198] S502, the SMF network element determines the L-UPF network element to establish / reuse the tunnel according to the AF instruction.

[0199] The SMF network element can determine the L-UPF network element based on the information in the EDI, and determine whether it needs to establish / reuse a tunnel, i.e., execute the following S503.

[0200] S503, the SMF network element sends node-level N4 rules to the L-UPF network element, and the L-UPF network element receives the node-level N4 rules from the SMF network element.

[0201] The node-level N4 rule may include first indication information, and optionally, it may also include second and / or third indication information. For details, please refer to the relevant description in S402 above, which will not be repeated here.

[0202] S504, the L-UPF network element configures the routing between the L-UPF network element and EAS through the user plane according to the instructions.

[0203] The L-UPF network element can configure a missing route through the user plane according to the first indication information / second indication information, or the L-UPF network element can configure a route between the L-UPF network element and EAS through the user plane according to the third indication information. For the specific implementation principle, please refer to the relevant introduction in S403 above, which will not be repeated here.

[0204] S505, EAS sends data packets to L-UPF network elements through the routing between L-UPF network elements and EAS.

[0205] Figure 3 Flowchart of the communication method provided in the embodiments of this application Figure 6 This communication method is applicable to the aforementioned communication system and mainly involves the interaction between L-UPF network elements (such as the first user plane network element), SMF network elements (such as the session management network element), EASDF / UPF network elements, EAS, and AF (such as the application function network element).

[0206] Specifically, such as Figure 7 As shown, the flow of this communication method is as follows:

[0207] S601, AF sends EDI to SMF network element.

[0208] EDI may include the DNAI where the EAS is located, such as the first DNAI. Optionally, it may also include an indicator cell (used to explicitly indicate the establishment of a tunnel) and information indicating whether the DNAI is an L-DNAI or a central DNAI. For specific implementation details, please refer to the relevant introduction in "Edge Application Service Information" above, which will not be repeated here. AF can send EDI to SMF network elements through NEF. For details, please refer to the relevant introduction in S401 above, which will not be repeated here.

[0209] S602, the SMF network element determines the L-UPF network element to establish / reuse the tunnel according to the AF instruction.

[0210] The SMF network element can determine the L-UPF network element based on the information in the EDI, and determine whether it needs to establish / reuse a tunnel, i.e., execute the following S603.

[0211] S603, the SMF network element sends node-level N4 rules to the L-UPF network element, and the L-UPF network element receives node-level N4 rules from the SMF network element.

[0212] The node-level N4 rule may include the first indication information, which can be referred to in the relevant introduction in S402 above, and will not be repeated here.

[0213] S604, PDU session establishment process.

[0214] SMF network elements can execute PDU session establishment procedures to establish a PDU session for the UE.

[0215] S605, the SMF network element configures the detection rules to the EASDF / UPF network element.

[0216] The EASDF / UPF network element is the network element that serves the PDU session. The detection rules can be used to detect the services accessed by the UE, such as whether the PDU data contains the specified FQDN, APP ID, EAS IP range, etc. For details, please refer to the relevant introductions in S401-S402 above, which will not be repeated here.

[0217] S606, the UE sends data packets through the PDU session.

[0218] S607, EASDF / UPF network elements report detection results to SMF network elements.

[0219] If the data packet contains the above characteristics, such as FQDN, APP ID, IP address within the EAS IP range, etc., the EASDF / UPF network element can report it in the detection result.

[0220] S608, the SMF network element determines the service accessed by the UE, and the DNAI corresponding to that service.

[0221] SMF network elements can determine the corresponding DNAI, such as the first DNAI, based on the reported results, EDI, and UE location. For details, please refer to the relevant description in S402 above; it will not be repeated here. Furthermore, S605-S608 are optional; SMF network elements can also determine the DNAI through the DNN and S-NSSAI of the PDU session. Again, please refer to the relevant description in S402 above; it will not be repeated here.

[0222] S609, the SMF network element sends the N4 rule to the L-UPF network element, and the L-UPF network element receives the N4 rule from the SMF network element.

[0223] The N4 rule may include second and / or third instruction information, as detailed in the relevant description in S402 above, and will not be repeated here.

[0224] S610, the L-UPF network element configures the routing between the L-UPF network element and EAS through the user plane according to the instructions.

[0225] The L-UPF network element can configure the missing route through the user plane according to the second indication information, or the L-UPF network element can configure the route between the L-UPF network element and EAS through the user plane according to the third indication information. For the specific implementation principle, please refer to the relevant introduction in S403 above, which will not be repeated here.

[0226] S611, EAS sends data packets to L-UPF network elements through the routing between L-UPF network elements and EAS.

[0227] Figure 4 Flowchart of the communication method provided in the embodiments of this application Figure 7 This communication method is applicable to the aforementioned communication system and mainly involves the interaction between session management network elements and application function network elements.

[0228] like Figure 7 As shown, the specific process is as follows:

[0229] S701, the application function network element sends edge application service information to the session management network element, and the session management network element receives the edge application service information from the application function network element.

[0230] Edge application service information can be used to indicate communication needs between two data network access ranges. For specific implementation details, please refer to the relevant description in S401 above, which will not be repeated here. After receiving the edge application service information, the session management network element can send first indication information to the first user plane network element to instruct the first user plane network element to establish a tunnel with the second user plane network element. For specific implementation details, please refer to the relevant descriptions in S402-S403 above, which will not be repeated here. However, the difference between S701 and S402-S403 is that the first user plane network element may not configure its own routing with the edge application server based on the first indication information.

[0231] S702, the session management network element sends the address information of the first user plane network element to the application function network element. The application function network element receives the address information of the first user plane network element returned by the session management network element.

[0232] The first user plane network element is used for communication between the edge application server and the server in the second data network access range of the two data network access ranges. The edge application server and the first user plane network element correspond to the first data network access range of the two data network access ranges. Optionally, routing needs to be configured between the first user plane network element and the edge application server. The address information of the first user plane network element may include the N6 address of the first user plane network element, or the address of the first user plane network element on the N6 interface, such as an IP address or any other possible form of address. The N6 interface of the first user plane network element is the interface between the first user plane network element and the data network (i.e., the network where the edge application server is located), to ensure that routing between the edge application server and the first user plane network element can be successfully configured subsequently.

[0233] The session management network element can decide to send the address information of the first user plane network element to the application function network element on its own, or it can send the address information of the first user plane network element to the application function network element based on the application function network element's subscription. These will be described separately below.

[0234] Scenario 1:

[0235] The session management network element can automatically obtain and open the address information of the first user plane network element at any possible time.

[0236] For example, a session management network element can establish a tunnel based on an instruction to a first user plane network element and obtain the address information of the first user plane network element from a data storage network element. Specifically, the session management network element can send the identifier / N4 address of the first user plane network element to the data storage network element (such as a UDR network element or an NRF network element). The identifier of the first user plane network element can be its network element identifier, IP address, FQDN, API interface, etc., without specific restrictions. Optionally, if the session management network element sends the identifier of the first user plane network element to the data storage network element, it may need to explicitly / implicitly indicate the request for the N6 address through the name of the message containing the identifier of the first user plane network element or the information element in that message, for example, through an NF discovery request (Nnrf_NFDiscovery_Request) message. The data storage network element is usually configured with a mapping between the identifier / N4 address of the first user plane network element and the N6 address. In this way, the data storage network element can return the N6 address of the first user plane network element to the session management network element based on the identifier / N4 address of the first user plane network element. Correspondingly, the session management network element can receive the N6 address of the first user plane network element returned by the data storage network element based on the N4 address of the first user plane network element. For example, the N6 address can be the notification target address of the first user plane network element.

[0237] For example, the session management network element can multiplex the instruction to the first user plane network element to establish a tunnel and obtain the address information of the first user plane network element. Specifically, the session management network element can instruct the first user plane network element to establish a tunnel between user planes, such as by sending a first instruction message, as detailed in the relevant description in S402 above. For the first user plane network element, if it receives the instruction message for establishing a tunnel sent by the session management network element, the first user plane network element can return its own N6 address to the session management network element. That is, in response to receiving the first instruction message, the first user plane network element returns its own N6 address to the session management network element, and correspondingly, the session management network element receives the N6 address from the first user plane network element.

[0238] It should be understood that if the N4 address and N6 address of the first user plane network element are the same, or if the session management network element has configured the N6 address of the first user plane network element locally, then the session management network element does not need to obtain the N6 address of the first user plane network element separately.

[0239] Having obtained the address information (N6 address) of the first user plane network element, the session management network element can send the address information of the first user plane network element to the application function network element based on the identifier of the application function network element. The identifier of the application function network element can be the network element identifier, IP address, FQDN, API interface, or FQDN+DNAI, etc., which can uniquely identify the application function network element and ensure that the address information of the first user plane network element can be correctly opened to the application function network element.

[0240] The session management network element can obtain the identifier of the application function network element in advance from the application function network element. For example, if the session management network element receives the identifier of the application function network element from the application function network element, it is provided by the application function network element itself. In this case, the identifier of the application function network element can be carried in the aforementioned edge application service information to improve communication efficiency, or it can be decoupled from the edge application service information through other information transmission, making information transmission more flexible. Alternatively, the application function network element may not provide its identifier, and the network open network element (such as the NEF network element) can send the identifier of the application function network element to the session management network element. For example, when the network open network element receives the edge application service information sent by the application function network element, it can, by default or based on the indication of communication needs between the two data network access ranges (or an indication to establish a tunnel), add the identifier of the application function network element to the edge application service information, and then send the edge application service information to the session management network element.

[0241] It should be understood that in the existing technical process, application function network elements provide session-independent information (such as EDI) to the 5GC's network open network elements. The session management network element obtains this information by subscribing to the network open network elements. The session management network element is unaware of the application function network elements and does not need to reply to them. If the existing technical process is reused, the session management network element needs to be aware of the application function network elements, such as obtaining the identifier of the application function network elements, in order to send the N6 address to them.

[0242] It should also be understood that the interfaces of a UPF network element on the user plane include at least: N3 interface (UPF network element to RAN equipment), N9 interface (UPF network element to UPF network element), or N6 (interface UPF network element to DN). The interfaces of a UPF network element on the control plane include at least: N4 interface (UPF network element to SMF network element). These interfaces may use different IP addresses / APIs / FQDNs, etc. When configuring a UPF network element, the SMF network element uses the address of the UPF network element on the N4 interface, i.e., the N4 address of the UPF network element. The SMF network element may not know the N6 address of the UPF network element. However, the edge application server in the DN communicates with the UPF network element using the N6 interface. Therefore, the SMF network element needs to send the N6 address of the UPF network element to the application function network element, i.e., the address information of the first user plane network element, to ensure that the edge application server can find the UPF network element.

[0243] Scenario 2:

[0244] The session management network element obtains and opens the address information of the first user plane network element based on the subscription of the application function network element.

[0245] Application function network elements can send subscription requests to session management network elements, and correspondingly, session management network elements can receive subscription requests from application function network elements. This subscription request can be used to subscribe to user plane events. For example, the subscription request can include the identifier of the application function network element and information indicating the user plane event, specifically the identifier of the user plane event. This user plane event can be a terminal accessing a service that requires communication between two data network access ranges. Optionally, the subscription request can also indicate the services corresponding to the two data network access ranges, such as including information corresponding to these two data network access ranges. For details, please refer to the relevant description in S401 above, which will not be repeated here. Alternatively, when the edge application service information indicates services corresponding to two data network access ranges, the subscription request may not indicate the services corresponding to these two data network access ranges to avoid information redundancy.

[0246] The session management network element instructs the network element serving the terminal's session (such as the user plane network element or edge application server discovery network element corresponding to the session) to detect user plane events. For example, the session management network element can instruct the network element serving the terminal's session to detect whether the data in the session contains services corresponding to two data network access ranges, to ensure the accuracy of the detection. If the data in the session contains services corresponding to two data network access ranges, it means that a user plane event has been detected; otherwise, no user plane event has been detected. For specific implementation details, please refer to the relevant description in S402 above, which will not be repeated here.

[0247] When a network element serving a terminal session detects a user plane event, the session management network element can send a subscription response to the application function network element. This subscription response may contain the address information of the first user plane network element.

[0248] Specifically, the session management network element can first determine which user plane network element's address information needs to be sent to avoid routing configuration failure due to providing incorrect address information. For example, the session management network element can determine the first user plane network element to establish a tunnel based on at least one of the following: the terminal's location, the aforementioned edge application service information, and information related to the services corresponding to the two data network access ranges in the session's data packets (such as FQDN / EAS IP), such as the first user plane network element establishing a tunnel with the second user plane network element. In one possible approach, the session management network element can first determine the first data network access range corresponding to the terminal's location based on at least one of the above, such as the aforementioned first DNAI, and then determine the user plane network element that establishes a tunnel with the second user plane network element corresponding to the second data network access range (such as the aforementioned second DNAI) among the user plane network elements corresponding to the first DNAI, such as the first user plane network element. Specific implementation details can be found in the relevant description in S402 above and will not be repeated here. In this way, the session management network element can encapsulate the address information of the first user plane network element into a subscription response and then send the subscription response to the application function network element. Correspondingly, the application function network element receives the subscription response returned by the session management network element based on the subscription request.

[0249] It can be seen that when data needs to be transmitted between two data network access ranges, the session management network element provides the application function network element with the address information of the first user plane network element, so that the application function network element can configure the routing between the first user plane network element and the edge application server, in order to avoid redundancy caused by pre-configuration.

[0250] It is understandable that in Case 2, the specific implementation of the session management network element obtaining the address information of the first user plane network element is similar to that in Case 1, and can be referred to for understanding, so it will not be repeated here.

[0251] Optionally, the session management network element can send a first DNAI to the application function network element, allowing the application function network element to select an edge application server that corresponds to the same DNAI as the first user plane network element. The first DNAI can be carried in the same message as the address information of the first user plane network element to reduce communication overhead, or they can be carried independently in their respective messages to achieve decoupling and more flexible information transmission. It can be understood that sending the first DNAI to the application function network element is optional. If the session management network element can determine that the application function network element corresponds to a single DNAI, such as the first DNAI, based on its identifier, then the session management network element may not send the first DNAI to the application function network element. Otherwise, if the application function network element corresponds to multiple DNAIs, then the session management network element may send the first DNAI to the application function network element.

[0252] Optionally, the session management network element can send information to the application function network element to instruct the establishment of a tunnel between user plane network elements, denoted as tunnel information, or any other possible name. This tunnel information can be combined with the address information of the first user plane network element to instruct the first user plane network element to establish the tunnel between user plane network elements, enabling the application function network element to know that it needs to configure routing for the first user plane network element. Furthermore, the tunnel information can be carried in the same message as the address information of the first user plane network element to reduce communication overhead, or they can be carried independently in their respective corresponding messages to achieve decoupling and more flexible information transmission. It can be understood that sending tunnel information to the application function network element by the session management network element is an optional action; for example, the application function network element can also know that it needs to configure routing for the first user plane network element based solely on the address information of the first user plane network element.

[0253] It should be understood that the above is based on the N6 address as an example and is not limited. For example, the session management network element can also provide the application function network element with any possible address corresponding to the N6 address, so that the application function network element can convert it to the N6 address according to the correspondence. Alternatively, it can be the identifier of the first user plane network element, such as the device / network element ID or any other possible identifier, so that the application function network element can configure the routing of the first user plane network element.

[0254] S703, the application function network element instructs at least one edge application server to configure routing between itself and the first user plane network element based on the address information of the first user plane network element.

[0255] At least one edge application server corresponds to the first data network access range, or the first DNAI.

[0256] The application function network element determines at least one edge application server from the two data network access ranges that corresponds to the same data network access range as the first user plane network element. For example, the application function network element can determine the route that needs to be configured between the edge application server and the first user plane network element based on the address information and tunnel information (optionally) of the first user plane network element. Based on this, the application function network element can determine the first data network access range, i.e., the first DNAI, from the two data network access ranges based on the first DNAI provided by the session management network element, or the first DNAI uniquely corresponding to the application function network element itself. This allows it to select at least a portion of the edge application servers (i.e., at least one edge application server) from one or more edge application servers corresponding to the first DNAI that need to be configured with a route to the first user plane network element.

[0257] It is understood that the embodiments of this application do not limit the strategy of the application function network element to select at least one edge application server, such as selecting based on information such as load, latency, or location.

[0258] The application function network element can configure a route between at least one edge application server and the first user plane network element based on the address information of the first user plane network element. For example, the application function network element can instruct at least one edge application server to configure a missing route, or in other words, instruct at least one edge application server to configure the first user plane network element as a missing route. That is, when a data packet does not match the routing table, at least one edge application server needs to route the data packet to the first user plane network element based on its address information. The specific implementation is similar to S403 above and can be understood by referring to it, so it will not be repeated here. Alternatively, the application function network element can also instruct at least one edge application server to establish a tunnel with the first user plane network element based on its address information. The specific implementation is similar to S403 above and can be understood by referring to it, so it will not be repeated here.

[0259] Application function network elements and edge application servers can be the same entity or different entities. When the application function network element and the edge application server are the same entity, the routing between the entity and the first user plane network element can be determined locally or according to internal logic. For example, the same server may have both application function network element and edge application server functions. Another example is two virtual machines or instances on the same server, each with the functions of an application function network element and an edge application server, respectively. In this case, instruction information can be passed between the two virtual machines or instances.

[0260] In summary, when there is a communication requirement between the first data network access range and the second data network access range, the session management network element can expose the address information of the first user plane network element corresponding to the same data network access range as the edge application server, i.e., the first data network access range, to the application function network element. This allows the application function network element to instruct the edge application server to configure routing with the first user plane network element, ensuring that data can be correctly routed from the edge application server to the first user plane network element and finally routed to the application server through a tunnel. This guarantees the stability and reliability of communication between the edge application server and the application server, and avoids communication failures.

[0261] The above combination Figure 8-9 The overall process of the communication method provided in the embodiments of this application in the second scenario is described in detail below. Figure 8 This section describes the specific process of this communication method in this scenario.

[0262] Figure 5 Flowchart of the communication method provided in the embodiments of this application Figure 8 This communication method is applicable to the aforementioned communication system and mainly involves the interaction between L-UPF network elements (such as the first user plane network element), SMF network elements (such as the session management network element), EAS, NEF (such as the network open network element), NRF network elements (such as the data storage network element), and AF (such as the application function network element).

[0263] Specifically, such as Figure 9 As shown, the flow of this communication method is as follows:

[0264] S801, AF sends EDI to SMF network element.

[0265] EDI may include the DNAI where the EAS is located, such as the first DNAI. Optionally, it may also include an indicator cell (used to explicitly indicate the establishment of a tunnel) and information indicating whether the DNAI is an L-DNAI or a central DNAI. For specific implementation details, please refer to the relevant introduction in "Edge Application Service Information" above, which will not be repeated here. AF can send EDI to SMF network elements through NEF. For details, please refer to the relevant introduction in S401 above, which will not be repeated here.

[0266] S802, NEF network elements add AF ID in EDI.

[0267] NEF network elements can add AF IDs to the EDI based on the indicator information element contained therein. For details, please refer to the relevant introduction in S702, which will not be repeated here. S602 is optional; for example, the EDI provided by the AF can also directly contain the AF ID.

[0268] S803, the NEF network element sends EDI to the SMF network element.

[0269] S804, the SMF network element determines the L-UPF network element to establish / reuse the tunnel according to the AF instruction.

[0270] The SMF network element can determine the L-UPF network element based on the information in the EDI, and determine whether it needs to establish / reuse a tunnel, i.e., execute the following S805.

[0271] S805, the SMF network element sends node-level N4 rules to the L-UPF network element, and the L-UPF network element receives the node-level N4 rules from the SMF network element.

[0272] Node-level N4 rules may include first indication information, which can be found in the relevant description in S402 above, and will not be repeated here.

[0273] S806a, the L-UPF network element returns the N6 address of the L-UPF network element to the SMF network element.

[0274] S806b, the SMF network element sends the N4 address of the L-UPF network element to the NRF network element.

[0275] In S806c, the NRF network element sends the N6 address of the L-UPF network element to the SMF network element.

[0276] S806a and S806b-S806c are optional. For example, the L-UPF network element can establish / reuse a tunnel according to the SMF network element's instruction and return the N6 address of the L-UPF network element to the SMF network element, or the SMF network element can obtain the N6 address of the L-UPF network element from the NRF network element. For details, please refer to the relevant introduction in S702 above, which will not be repeated here.

[0277] S807, SMF network element determines AF ID.

[0278] After configuring the tunnel, the SMF network element can determine the AF ID, such as by obtaining the AF ID from the EDI mentioned above.

[0279] S808, SMF network element determines the DNAI corresponding to AF ID.

[0280] The DNAI corresponding to the AF ID can be the first DNAI. S808 is optional; when AF uniquely corresponds to a single DNAI, S808 may not be executed.

[0281] S809, the SMF network element sends the N6 address of the L-UPF network element to the AF.

[0282] Optionally, in S809, the SMF network element can also send the DNAI corresponding to the AF ID to the AF (i.e., sent when S808 is executed), as well as information for instructing the establishment of a tunnel between user plane network elements.

[0283] S810, AF instructs EAS to configure routing between L-UPF network elements and EAS.

[0284] Furthermore, the specific implementations of S807-S810 can be found in the relevant descriptions in S702-S703 above, and will not be repeated here.

[0285] S811, EAS sends data packets to L-UPF network elements through the routing between L-UPF network elements and EAS.

[0286] Figure 6 Flowchart of the communication method provided in the embodiments of this application Figure 9 This communication method is applicable to the aforementioned communication system and mainly involves the interaction between L-UPF network elements (such as the first user plane network element), SMF network elements (such as the session management network element), EASDF / UPF network elements, EAS, and AF (such as the application function network element).

[0287] Specifically, such as Figure 10 As shown, the flow of this communication method is as follows:

[0288] S901, AF sends EDI to SMF network element.

[0289] EDI may include the DNAI where the EAS is located, such as the first DNAI. Optionally, it may also include an indicator cell (used to explicitly indicate the establishment of a tunnel) and information indicating whether the DNAI is an L-DNAI or a central DNAI. For specific implementation details, please refer to the relevant introduction in "Edge Application Service Information" above, which will not be repeated here. AF can send EDI to SMF network elements through NEF. For details, please refer to the relevant introduction in S401 above, which will not be repeated here.

[0290] S902, the SMF network element determines the L-UPF network element to establish / reuse the tunnel according to the AF instruction.

[0291] The SMF network element can determine the L-UPF network element based on the information in the EDI, and determine whether it needs to establish / reuse a tunnel, i.e., execute the following S603.

[0292] S903, the SMF network element sends node-level N4 rules to the L-UPF network element, and the L-UPF network element receives the node-level N4 rules from the SMF network element.

[0293] The node-level N4 rule may include the first indication information, which can be referred to in the relevant introduction in S402 above, and will not be repeated here.

[0294] S904, PDU session establishment process.

[0295] SMF network elements can execute PDU session establishment procedures to establish a PDU session for the UE.

[0296] S905, AF sends subscription messages to SMF network elements.

[0297] Subscription messages are used to subscribe to user plane events for services that require EAS and AS communication from the UE. The relevant descriptions in S702 above will not be repeated here.

[0298] S906, the SMF network element configures the detection rules to the EASDF / UPF network element.

[0299] The EASDF / UPF network element is the network element that serves the PDU session. The detection rules can be used to detect the services accessed by the UE, such as whether the PDU data contains the specified FQDN, APP ID, and EAS IP range. If it does, it means that the UE has services that require communication between EAS and AS. For details, please refer to the relevant introduction in S702 above, which will not be repeated here.

[0300] S907, the UE sends data packets through the PDU session.

[0301] S908, EASDF / UPF network elements report detection results to SMF network elements.

[0302] If the data packet contains the above characteristics, such as FQDN, APP ID, IP address within the EAS IP range, etc., the EASDF / UPF network element can report it in the detection result.

[0303] In S909, the SMF network element determines the service accessed by the UE and the DNAI corresponding to that service.

[0304] SMF network elements can determine the corresponding DNAI based on the reported results, EDI, and UE location, such as the first DNAI. For details, please refer to the relevant introduction in S402 above, which will not be repeated here.

[0305] S910, the SMF network element sends a subscription response to the AF.

[0306] The subscription response may include the N6 address of the L-UPF network element, and optionally, may also include the first DNAI.

[0307] S911, AF instructs EAS to configure routing between L-UPF network elements and EAS.

[0308] Furthermore, the specific implementations of S907-S911 can be found in the relevant descriptions in S702-S703 above, and will not be repeated here.

[0309] In S912, EAS sends data packets to L-UPF network elements via routing between L-UPF network elements and EAS.

[0310] Figure 7 Flowchart of the communication method provided in the embodiments of this application Figure 10 This communication method is applicable to the aforementioned communication system and mainly involves the interaction between session management network elements and application function network elements.

[0311] like Figure 8-10 As shown, the specific process is as follows:

[0312] S1001, the session management network element receives edge application service information from the application function network element.

[0313] Edge application service information can be used to indicate communication needs between two data network access ranges. For specific implementation details, please refer to the relevant introduction in S401 above, which will not be repeated here.

[0314] Edge application service information can also be used to indicate the address information of the first user plane network element, such as including that address information.

[0315] The first user plane network element and the edge application server correspond to the same data network access range in two data network access ranges, such as the first DNAI mentioned above. For details, please refer to the relevant description in S401 above, which will not be repeated here. The first user plane network element and the edge application server have configured routes. Specifically, the edge application server can configure the first user plane network element as the default router / default route address through the user plane. Existing technologies can be reused, such as fixed networks, protocols defined by the Internet Engineering Task Force (IETF), or routing table configurations, etc. There are no specific restrictions, or you can refer to the relevant description in S403 above for further understanding. The address information of the first user plane network element can be the N6 address of the first user plane network element. For details, please refer to the relevant description of the N6 address above, which will not be repeated here. During / after the route configuration process, the edge application server can obtain the address information of the first user plane network element and send it to the application function network element. The application function network element then sends the address information of the first user plane network element to the session management network element through the edge application service information.

[0316] In this embodiment of the application, for Figure 10-12The address information of the first user plane network element involved in the relevant content can be understood by default as the N4 address of the first user plane network element. Figure 8 The address information of the first user plane network element involved in the relevant content can be understood by default as the address of the first user plane network element N6.

[0317] S1002, if no tunnel has been established between user plane network elements within the data network access range corresponding to the first user plane network element, the session management network element instructs the first user plane network element to establish a tunnel with the second user plane network element.

[0318] The tunnel between user plane network elements refers to the tunnel between user plane network elements that correspond to two data network access ranges respectively. For details, please refer to the relevant introduction in S401 above, which will not be repeated here.

[0319] The second user plane network element and the first user plane network element each correspond to two data network access ranges. For example, the first user plane network element corresponds to the first DNAI / first data network, and the second user plane network element corresponds to the second DNAI / second data network. For details, please refer to the relevant introduction in S401 above, which will not be repeated here.

[0320] The session management network element can determine whether a tunnel between user plane network elements has been established within the data network access range corresponding to the first user plane network element, i.e., whether the first DNAI has established a tunnel between user plane network elements. For example, the session management network element can determine whether it has instructed the user plane network element corresponding to the first DNAI to establish a tunnel between user plane network elements.

[0321] If the session management network element does not instruct the user plane network element corresponding to the first DNAI to establish a tunnel between user plane network elements, it means that the first DNAI has not established a tunnel between user plane network elements. In this case, the session management network element can instruct the first user plane network element to establish a tunnel with the second user plane network element based on the address information of the first user plane network element, to avoid tunnel establishment failure due to address errors. Specifically, the session management network element can determine the N4 address or identifier of the first user plane network element based on its N6 address, such as a device / network element ID or any other possible identifier, to enable communication between the session management network element and the first user plane network element. For example, the session management network element can send the N6 address of the first user plane network element to the data storage network element and receive the N4 address or identifier returned by the data storage network element based on the N6 address of the first user plane network element. Alternatively, it can obtain the N6 address through other methods, the principle of which is similar to the above understanding of the session management network element obtaining the N6 address based on the N4 address or identifier, and will not be elaborated further here. The session management network element can instruct the first user plane network element to establish a tunnel with the second user plane network element based on the N4 address or identifier of the first user plane network element. For specific implementation details, please refer to the relevant description in S402 above, which will not be repeated here.

[0322] It can be understood that the N6 address of the first user plane network element is its address on the N6 interface, which is the interface between the first user plane network element and the data network. The N4 address of the first user plane network element is its address on the N4 interface, which is the interface between user plane network elements. Therefore, directly using the address on the N6 interface cannot establish a tunnel with the second user plane. The session management network element can only successfully establish a tunnel between user plane network elements by converting the N6 address to the N4 address.

[0323] If the session management network element has instructed the user plane network element corresponding to the first DNAI to establish a tunnel between user plane network elements, it indicates that the first DNAI has already established a tunnel between user plane network elements. The session management network element can then determine whether the user plane network element that established the tunnel is the first user plane network element. This determination can be made by the session management network element obtaining the N4 address / identifier corresponding to the N6 address of the first user plane network element, and based on the identifier / address of the user plane network element that has established a tunnel between the local DN and central DN within the first DNAI, either stored locally or obtained from other network elements. If so, the session management network element may not need to perform any processing, and may not need to instruct the first user plane network element to establish a tunnel with the second user plane network element again. If the user plane network element that established the tunnel is not the first user plane network element, such as the third user plane network element, the session management network element can instruct the third user plane network element to release the established tunnel between user plane network elements. The specific instruction method is not limited to avoid redundancy. Furthermore, the session management network element can also instruct the first user plane network element to establish a tunnel with the second user plane network element. Alternatively, if the user plane network element establishing the tunnel between user plane network elements is a third user plane network element, the session management network element can also send indication information to the application function network element, denoted as the fourth indication information. The fourth indication information can be used to indicate that routing between the third user plane network element and the edge application server needs to be configured to ensure normal communication between the two data network access ranges.

[0324] The session management network element can determine whether it has instructed the user plane network element corresponding to the first DNAI to establish a tunnel between user plane network elements in the following ways: the session management network element stores locally or obtains from other network elements (UDR / NRF, etc.) the identifier / address (N4 address) of the user plane network element that has established a tunnel between the local DN and the central DN in the first DNAI.

[0325] Specifically, the fourth indication information may include at least one of the following: the address information of the third user plane network element, an indication element, or the first DNAI. The address information of the third user plane network element may be the N6 address of the third user plane network element. The method by which the session management network element obtains the N6 address of the third user plane network element is similar to that described above for obtaining the N6 address of the first user plane network element; this can be understood by referring to the example and will not be repeated here. The indication element can be used to indicate that the routing between the user plane network element and the edge application server needs to be reconfigured. The indication element is optional; for example, it can also implicitly indicate that the routing between the user plane network element and the edge application server needs to be reconfigured through the address information of the third user plane network element or the name of the message containing the fourth indication information. The first DNAI is also optional. For example, if the application function network element carries the first DNAI when making an indication (such as sending edge application service information), then if the session management network element sending the fourth indication information to the application function network element is a response to the application function network element's indication, the fourth indication information does not need to carry the first DNAI; otherwise, the fourth indication information needs to carry the first DNAI.

[0326] It is understandable that when the session management network element sends the fourth instruction information to the application function network element, it can specifically send the fourth instruction information to the application function network element based on the identifier of the application function network element. Furthermore, regarding the scenario where the session management network element instructs the first user plane network element to establish a tunnel with the second user plane network element, after the tunnel establishment is completed (or the tunnel configuration is completed), the session management network element can also notify the application function network element of the tunnel establishment completion based on the identifier of the application function network element. In this case, the method by which the session management network element obtains the identifier of the application function network element can refer to the above. Figure 10 The relevant information will not be repeated here.

[0327] In summary, the application function network element actively configures the routing between the first user plane network element and the edge application server corresponding to the same data network access range, and provides the address information of the first user plane network element to the session management network element. Then, the session management network element can establish a tunnel between the first user plane network element and the second user plane network element based on the address information of the first user plane network element, so as to realize communication between the two data network access ranges.

[0328] The above combination Figure 11 The overall process of the communication method provided in the embodiments of this application in the third scenario is described in detail below. Figure 11 This section describes the specific process of this communication method in this scenario.

[0329] Figure 8 Flowchart of the communication method provided in the embodiments of this application Figure 11This communication method is applicable to the aforementioned communication system and mainly involves the interaction between L-UPF1 network elements (such as the first user plane network element), L-UPF2 network elements (such as the third user plane network element), SMF network elements (such as the session management network element), EAS, NRF network elements (such as the data storage network element), and AF (such as the application function network element).

[0330] Specifically, such as Figure 12 As shown, the flow of this communication method is as follows:

[0331] S1100, EAS is configured with L-UPF1 network element as a missing route.

[0332] Configuring L-UPF1 as a missing route in EAS can be understood as configuring the route between L-UPF1 and EAS. During this process, EAS can inform AF of the N6 address of L-UPF1.

[0333] S1101, AF sends EDI to SMF network element.

[0334] EDI may include the DNAI where EAS resides, such as the first DNAI. Optionally, it may also include an indicator cell (used to explicitly indicate the establishment of a tunnel) and information indicating whether the DNAI is an L-DNAI or a central DNAI. For specific implementation details, please refer to the relevant description in "Edge Application Service Information" above, which will not be repeated here. EDI may also include the N6 address of the L-UPF1 network element. For specific implementation details, please refer to the relevant description in S1001 above, which will not be repeated here. Furthermore, AF can send EDI to SMF network elements through NEF. For details, please refer to the relevant description in S401 above, which will not be repeated here.

[0335] S1102, the SMF network element sends the N6 address of the L-UPF1 network element to the NRF network element.

[0336] S1103, the NRF network element sends the N4 address of the L-UPF1 network element to the SMF network element.

[0337] For the specific implementation of S1102-S1103, please refer to the relevant introduction of S1002 above, which will not be repeated here.

[0338] Then, execution can proceed in three scenarios: S1104-S1105, S1106-S1108.

[0339] S1104, the SMF network element determines that the L-UPF1 network element establishes a tunnel according to the AF instruction.

[0340] S1105, the SMF network element sends node-level N4 rules to the L-UPF1 network element.

[0341] In S1104-S1105, the node-level N4 rule may include first indication information, which can be referred to in the relevant description in S402 above, and will not be repeated here. The SMF network element can determine from the information in EDI that the DNAI corresponding to the L-UPF1 network element has not established a tunnel, and thus determine that the L-UPF1 network element needs to establish a tunnel, that is, execute S1105, which can be referred to in the relevant description in S1002 above, and will not be repeated here.

[0342] S1106, the SMF network element determines, according to the AF instruction, that the L-UPF2 network element establishes a tunnel.

[0343] S1107, SMF network element instructs L-UPF2 network element to release tunnel.

[0344] S1108, the SMF network element sends node-level N4 rules to the L-UPF1 network element.

[0345] In S1106-S1108, if the DNAI corresponding to the L-UPF1 network element already has a tunnel established by the L-UPF2 network element, the SMF network element instructs the L-UPF2 network element to release its established tunnel and instructs the L-UPF1 network element to establish a tunnel. For details, please refer to the relevant introduction in S1002 above, which will not be repeated here.

[0346] S1109, EAS sends data packets to L-UPF1 network element through the routing between L-UPF1 network element and EAS.

[0347] After S1104-S1108, S1109 can be executed.

[0348] S1110, the SMF network element determines, according to the AF instruction, that the L-UPF2 network element establishes a tunnel.

[0349] S1111, the SMF network element instructs the AF to reconfigure the route.

[0350] S1112, AF instructs EAS to configure L-UPF2 network element as a missing route.

[0351] S1113, EAS sends data packets to L-UPF2 network elements through the routing between L-UPF2 network elements and EAS.

[0352] In S1110-S1113, if the DNAI corresponding to the L-UPF1 network element already has a tunnel established with the L-UPF2 network element, the SMF network element can trigger AF to configure the routing between the L-UPF2 network element and the EAS. For details, please refer to the relevant introduction in S1002 above, which will not be repeated here.

[0353] Figure 9Flowchart of the communication method provided in the embodiments of this application Figure 12 This communication method is applicable to the aforementioned communication system and mainly involves the interaction between user plane network elements.

[0354] like Figure 12 As shown, the specific process is as follows:

[0355] S1201, the first user plane network element receives the first data packet from the second user plane network element through the tunnel between the first user plane network element and the second user plane network element.

[0356] The first user plane network element and the second user plane network element correspond to different data network access ranges, and a tunnel can be established between the first user plane network element and the second user plane network element. For details, please refer to the relevant introduction above. However, the difference lies in... Figure 4-12 The first user plane network element can be a central UPF network element, and the second user plane network element can be an L-UPF network element, which will not be elaborated here.

[0357] S1202, the first user plane network element converts the first address of the first data packet to the second address to obtain the second data packet.

[0358] The first address of the first data packet can be an IP address or any other possible address. This first address can be an address applicable to the L-DN, therefore address conflicts may occur in data networks such as central DNs. The second address can be an address applicable to the central DN, such as a unique address within the central DN, specifically an IP address or any other possible address.

[0359] The first user plane network element can pre-configure a mapping between addresses applicable to L-DN and addresses applicable to Central DN. The first user plane network element can then traverse this mapping based on the first address of the first data packet to convert the first address of the first data packet to the second address, thus obtaining the second data packet. Alternatively, the first user plane network element can pre-configure a mapping between addresses applicable to L-DN and tunnel identifiers. In this case, the first user plane network element can determine the second address based on the first address of the first data packet and the aforementioned tunnel identifier, thereby converting the first address of the first data packet to the second address, thus obtaining the second data packet. In this scenario, if data in different tunnels reuses the same address, the first user plane network element can also convert it to different addresses based on the tunnel identifier, avoiding address conflicts.

[0360] S1203, the first user plane network element sends the second data packet to the data network.

[0361] In summary, when a tunnel is established between the first user plane network element and the second user plane network element, the first user plane network element can perform address translation of data packets in the tunnel, such as converting the first address of the first data packet into a unique second address in the data network, in order to avoid data transmission errors due to address conflicts.

[0362] The above combination Figure 13-14 The communication method provided in the embodiments of this application is described in detail below. Figure 13 This document describes in detail the communication apparatus used to perform the communication method provided in the embodiments of this application.

[0363] Figure 1 This is a schematic diagram of the structure of the communication device provided in the embodiments of this application. Figure 13 For example, such as Figure 13 As shown, the communication device 1300 includes a transceiver module 1301 and a processing module 1302. For ease of explanation, Figure 13 Only the main components of the communication device are shown.

[0364] The communication device 1300 can be applied to the above-described communication method to achieve the corresponding functions. For example, the transceiver module 1301 can be used to implement the transceiver function in the above-described communication method, and the processing module 1302 can be used to implement other functions in the above-described communication method besides the transceiver function.

[0365] Optionally, the transceiver module 1301 may include a transmitting module. Figure 13 (not shown in the image) and receiving module ( Figure 13 (Not shown in the image). The transmitting module is used to implement the transmitting function of the communication device 1300, and the receiving module is used to implement the receiving function of the communication device 1300.

[0366] Optionally, the communication device 1300 may also include a storage module. Figure 4-12 (Not shown in the image), the storage module stores programs or instructions. When the processing module 1302 executes the program or instructions, the communication device 1300 can perform the aforementioned operations. Figure 14 The functions in the method shown.

[0367] It is understood that the communication device 1300 may be a network device, or a chip (system) or other component or assembly that can be set in the network device, or a device that includes the network device. This application does not limit this.

[0368] Furthermore, the technical effects of the communication device 1300 can be referenced from the technical effects of the communication method described above, and will not be repeated here.

[0369] Figure 2 Schematic diagram of the communication device provided in the embodiments of this application Figure 14For example, the communication device can be a terminal, or a chip (system) or other component or assembly that can be set in the terminal. Figure 14 As shown, the communication device 1400 may include a processor 1401. Optionally, the communication device 1400 may also include a memory 1402 and / or a transceiver 1403. The processor 1401 is coupled to the memory 1402 and the transceiver 1403, for example, they may be connected via a communication bus.

[0370] The following is combined Figure 4-12 A detailed description of each component of the communication device 1400 is provided below:

[0371] The processor 1401 is the control center of the communication device 1400. It can be a single processor or a collective term for multiple processing elements. For example, the processor 1401 can be one or more central processing units (CPUs), application-specific integrated circuits (ASICs), or one or more integrated circuits configured to implement the embodiments of this application, such as one or more digital signal processors (DSPs), or one or more field-programmable gate arrays (FPGAs).

[0372] Optionally, the processor 1401 can perform various functions of the communication device 1400, such as the functions described above, by running or executing software programs stored in the memory 1402 and calling data stored in the memory 1402. Figure 14 The communication method shown.

[0373] In a specific implementation, as one example, the processor 1401 may include one or more CPUs, for example... Figure 14 CPU0 and CPU1 are shown in the diagram.

[0374] In a specific implementation, as one example, the communication device 1400 may also include multiple processors, for example... Figure 14 The processors 1401 and 1404 are shown. Each of these processors can be a single-core processor or a multi-core processor. A processor here can refer to one or more devices, circuits, and / or processing cores used to process data (e.g., computer program instructions).

[0375] The memory 1402 is used to store the software program that executes the solution of this application, and is controlled by the processor 1401 to execute it. The specific implementation method can be referred to the above method embodiment, and will not be repeated here.

[0376] Optionally, the memory 1402 may be a read-only memory (ROM) or other type of static storage device capable of storing static information and instructions, random access memory (RAM) or other type of dynamic storage device capable of storing information and instructions, or electrically erasable programmable read-only memory (EEPROM), compact disc read-only memory (CD-ROM) or other optical disc storage, optical disc storage (including compressed optical discs, laser discs, optical discs, digital universal optical discs, Blu-ray discs, etc.), magnetic disk storage media or other magnetic storage devices, or any other medium capable of carrying or storing desired program code in the form of instructions or data structures and accessible by a computer, but not limited thereto. The memory 1402 may be integrated with the processor 1401 or may exist independently, and may be connected via the interface circuit of the communication device 1400. Figure 14 (Not shown in the image) is coupled to processor 1401, and this embodiment of the application does not specifically limit this.

[0377] Transceiver 1403 is used for communication with other communication devices. For example, if communication device 1400 is a terminal, transceiver 1403 can be used to communicate with a network device or with another terminal device. As another example, if communication device 1400 is a network device, transceiver 1403 can be used to communicate with a terminal or with another network device.

[0378] Alternatively, transceiver 1403 may include a receiver and a transmitter. Figure 14 (Not shown separately). The receiver is used to implement the receiving function, and the transmitter is used to implement the sending function.

[0379] Alternatively, the transceiver 1403 can be integrated with the processor 1401, or it can exist independently and be connected via the interface circuit of the communication device 1400. Figure 14 (Not shown in the image) is coupled to processor 1401, and this embodiment of the application does not specifically limit this.

[0380] Understandable, ​The structure of the communication device 1400 shown does not constitute a limitation on the communication device. Actual communication devices may include more or fewer components than shown, or combine certain components, or have different component arrangements.

[0381] Furthermore, the technical effects of the communication device 1400 can be referred to the technical effects of the method described in the above method embodiments, and will not be repeated here.

[0382] It should be understood that the processor in the embodiments of this application can be a central processing unit (CPU), or it can be other general-purpose processors, digital signal processors (DSPs), application-specific integrated circuits (ASICs), field-programmable gate arrays (FPGAs), or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc. The general-purpose processor can be a microprocessor or any conventional processor.

[0383] It should also be understood that the memory in the embodiments of this application can be volatile memory or non-volatile memory, or may include both volatile and non-volatile memory. The non-volatile memory can be read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), or flash memory. The volatile memory can be random access memory (RAM), which is used as an external cache. By way of example, but not limitation, many forms of random access memory (RAM) are available, such as static RAM (SRAM), dynamic RAM (DRAM), synchronous DRAM (SDRAM), double data rate synchronous DRAM (DDR SDRAM), enhanced synchronous DRAM (ESDRAM), synchronous linked DRAM (SLDRAM), and direct rambus RAM (DR RAM).

[0384] The above embodiments can be implemented, in whole or in part, by software, hardware (such as circuits), firmware, or any other combination thereof. When implemented using software, the above embodiments can be implemented, in whole or in part, in the form of a computer program product. The computer program product includes one or more computer instructions or computer programs. When the computer instructions or computer programs are loaded or executed on a computer, all or part of the processes or functions described in the embodiments of this application are generated. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device. The computer instructions can be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another. For example, the computer instructions can be transmitted from one website, computer, server, or data center to another website, computer, server, or data center via wired (e.g., infrared, wireless, microwave, etc.) means. The computer-readable storage medium can be any available medium that a computer can access or a data storage device such as a server or data center that includes one or more sets of available media. The available medium can be a magnetic medium (e.g., floppy disk, hard disk, magnetic tape), an optical medium (e.g., DVD), or a semiconductor medium. A semiconductor medium can be a solid-state drive.

[0385] It should be understood that the term "and / or" in this article is merely a description of the relationship between related objects, indicating that three relationships can exist. For example, A and / or B can represent: A existing alone, A and B existing simultaneously, or B existing alone. A and B can be singular or plural. Additionally, the character " / " in this article generally indicates an "or" relationship between the preceding and following related objects, but it can also represent an "and / or" relationship. Please refer to the context for a more accurate understanding.

[0386] In this application, "at least one" means one or more, and "more than one" means two or more. "At least one of the following" or similar expressions refer to any combination of these items, including any combination of single or multiple items. For example, at least one of a, b, or c can mean: a, b, c, ab, ac, bc, or abc, where a, b, and c can be single or multiple.

[0387] It should be understood that in the various embodiments of this application, the order of the above-mentioned processes does not imply the order of execution. The execution order of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiments of this application.

[0388] Those skilled in the art will recognize that the units and algorithm steps of the various examples described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are implemented in hardware or software depends on the specific application and design constraints of the technical solution. Those skilled in the art can use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of this application.

[0389] Those skilled in the art will understand that, for the sake of convenience and brevity, the specific working processes of the systems, devices, and units described above can be referred to the corresponding processes in the foregoing method embodiments, and will not be repeated here.

[0390] In the several embodiments provided in this application, it should be understood that the disclosed systems, apparatuses, and methods can be implemented in other ways. For example, the apparatus embodiments described above are merely illustrative; for instance, the division of units is only a logical functional division, and in actual implementation, there may be other division methods. For example, multiple units or components may be combined or integrated into another system, or some features may be ignored or not executed. Furthermore, the coupling or direct coupling or communication connection shown or discussed may be through some interfaces; the indirect coupling or communication connection between apparatuses or units may be electrical, mechanical, or other forms.

[0391] The units described as separate components may or may not be physically separate. The components shown as units may or may not be physical units; that is, they may be located in one place or distributed across multiple network units. Some or all of the units can be selected to achieve the purpose of this embodiment according to actual needs.

[0392] In addition, the functional units in the various embodiments of this application can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit.

[0393] If the aforementioned functions are implemented as software functional units and sold or used as independent products, they can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of this application, in essence, or the part that contributes to the prior art, or a portion of the technical solution, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) to execute all or part of the steps of the methods described in the various embodiments of this application. The aforementioned storage medium includes various media capable of storing program code, such as USB flash drives, portable hard drives, read-only memory (ROM), random access memory (RAM), magnetic disks, or optical disks.

[0394] The above description is merely a specific embodiment of this application, but the scope of protection of this application is not limited thereto. Any variations or substitutions that can be easily conceived by those skilled in the art within the technical scope disclosed in this application should be included within the scope of protection of this application. Therefore, the scope of protection of this application should be determined by the scope of the claims.

Claims

1. A communication method, characterized in that, Applied to a first user plane network element, the method includes: The first user plane network element receives a first message and a first indication information. The first indication information is used to instruct the first user plane network element to establish a tunnel with the second user plane network element. The second user plane network element and the first user plane network element correspond to different data network access ranges. The first user plane network element configures the routing between itself and one or more edge application servers according to the first message; the one or more edge application servers correspond to the same data network access range as the first user plane network element.

2. The method according to claim 1, characterized in that, The first message includes the first indication information. Based on the first message, the first user plane network element configures routing between itself and one or more edge application servers, including: The first user plane network element configures the routing between the first user plane network element and the one or more edge application servers according to the first indication information in the first message.

3. The method according to claim 2, characterized in that, The first user plane network element configures routing between itself and one or more edge application servers according to the first indication information in the first message, including: The first user plane network element broadcasts default routing information through the user plane according to the first indication information in the first message, and the one or more edge application servers are within the range where the default routing information is broadcast.

4. The method according to claim 1, characterized in that, The first message includes second indication information, which instructs the first user plane network element to configure routing between the first user plane network element and the one or more edge application servers. The first user plane network element configures the routing between itself and the one or more edge application servers according to the first message, including: The first user plane network element configures the routing between the first user plane network element and the one or more edge application servers according to the second instruction information in the first message.

5. The method according to claim 4, characterized in that, The first user plane network element configures the routing between itself and the one or more edge application servers according to the second indication information in the first message, including: The first user plane network element broadcasts default routing information through the user plane according to the second indication information in the first message, and the one or more edge application servers are within the range where the default routing information is broadcast.

6. The method according to claim 3 or 5, characterized in that, The default routing information is used to indicate that if a data packet does not match the routing table, the data packet needs to be routed to the first user plane network element.

7. The method according to claim 1, characterized in that, The first message includes third indication information, which indicates the address of at least one edge application server or a range of addresses for edge application servers, the address range including the addresses of the at least one edge application server. Based on the first message, the first user plane network element configures routing between itself and one or more edge application servers, including: The first user plane network element configures the routing between the first user plane network element and the at least one edge application server through the user plane according to the third indication information in the first message, wherein the at least one edge application server belongs to the one or more edge application servers.

8. The method according to claim 5 or 7, characterized in that, The first message further includes the first indication information, or, the first user plane network element receives the first message and the first indication information, including: The first user plane network element receives the first message and the second message, wherein the second message includes the first indication information.

9. A communication method, characterized in that, Applied to a session management network element, the method includes: The session management network element receives edge application service information from the application function network element; the edge application service information is used to indicate that there is a communication requirement between two data network access ranges. The session management network element sends at least one of the second or third instruction information to the first user plane network element; The second indication information is used to instruct the first user plane network element to configure its routing with one or more edge application servers. The first or more edge application servers correspond to the same data network access range in the two data network access ranges as the first user plane network element. The third indication information is used to indicate the address of at least one edge application server or the address range of an edge application server. The at least one edge application server belongs to the one or more edge application servers, and the address range includes the address of the at least one edge application server.

10. The method according to claim 9, characterized in that, The session management network element sends at least one of the second or third indication information to the first user plane network element, including: The session management network element sends a first message to the first user plane network element according to the edge application service information; the first message includes first indication information and at least one of the above information, the first indication information is used to instruct the first user plane network element to establish a tunnel with the second user plane network element, the second user plane network element and the first user plane network element respectively correspond to the two data network access ranges.

11. The method according to claim 10, characterized in that: The second user plane network element and the first user plane network element respectively correspond to the two data network access ranges including: the second user plane network element and the first user plane network element respectively correspond to two data network access identifiers (DNAI).

12. The method according to claim 9, characterized in that, The session management network element sends at least one of the second or third indication information to the first user plane network element, including: The session management network element determines the terminal's session requirements; the session requirements include the terminal's session needing to be routed between the two data network access ranges. The session management network element sends at least one piece of information to the first user plane network element according to the session requirements.

13. The method according to claim 12, characterized in that, The session management network element determines the terminal's session requirements, including: The session management network element obtains the edge application server deployment information associated with the data network and / or slice corresponding to the session; the edge application server deployment information includes information indicating that there is a communication requirement between the two data network access ranges. The session management network element determines that the session has a routing requirement between the two data network access ranges based on the information indicating that there is a communication requirement between the two data network access ranges.

14. The method according to claim 12, characterized in that, The session management network element determines the terminal's session requirements, including: The session management network element instructs the network element serving the session to detect whether the data of the session is associated with the two data network access ranges; If the data of the session is associated with the two data network access ranges, the session management network element determines that the session has a routing requirement between the two data network access ranges.

15. The method according to claim 14, characterized in that, The edge application service information also indicates the services corresponding to the two data network access ranges; the session management network element instructs the network element serving the session to detect whether the data of the session is associated with the two data network access ranges, including: The session management network element instructs the network element serving the session to detect whether the data in the session contains services corresponding to the two data network access ranges; if the data in the session contains services corresponding to the two data network access ranges, it indicates that the data in the session is associated with the two data network access ranges; otherwise, the data in the session is not associated with the two data network access ranges.

16. A communication method, characterized in that, Applied to a session management network element, the method includes: The session management network element receives edge application service information from the application function network element; the edge application service information is used to indicate that there is a communication requirement between two data network access ranges. The session management network element sends the address information of the first user plane network element to the application function network element; the first user plane network element and the edge application server need to be configured with routing. The first user plane network element is used for the edge application server to communicate with the server in the second data network access range of the two data network access ranges. The edge application server and the first user plane network element correspond to the first data network access range of the two data network access ranges.

17. The method according to claim 16, characterized in that: The address information of the first user plane network element is the N6 address of the first user plane network element.

18. The method according to claim 17, characterized in that, The method further includes: The session management network element obtains the address information of the first user plane network element from any of the following: the session management network element itself, the first user plane network element, or the data storage network element.

19. The method according to claim 18, characterized in that, The session management network element obtains the address information of the first user plane network element from the data storage network element, including: The session management network element sends the N4 address of the first user plane network element to the data storage network element; The session management network element receives the N6 address of the first user plane network element returned by the data storage network element based on the N4 address of the first user plane network element.

20. The method according to any one of claims 16-19, characterized in that, The first user plane network element corresponds to the first data network access range including the first data network access identifier (DNAI) corresponding to the first user plane network element, and the method further includes: The session management network element sends the first DNAI to the application function network element.

21. The method according to any one of claims 16-20, characterized in that, The method further includes: The session management network element sends information to the application function network element to instruct the establishment of a tunnel between user plane network elements.

22. The method according to claim 21, characterized in that: The second user plane network element corresponds to the second data network access range, including: the second user plane network element corresponds to the second DNAI.

23. The method according to any one of claims 16-19, characterized in that, The session management network element sends the address information of the first user plane network element to the application function network element, including: The session management network element receives a subscription request from the application function network element; the subscription request is used to subscribe to user plane events, which are services that require communication between the two data network access ranges. The session management network element instructs the network element serving the session of the terminal to detect the user plane event; When a network element serving the terminal's session detects the user plane event, the session management network element sends a subscription response to the application function network element; the subscription response includes the address information of the first user plane network element.

24. The method according to claim 23, characterized in that, The subscription request also indicates the services corresponding to the two data network access ranges; the session management network element instructs the network element serving the session of the terminal to detect the user plane event, including: The session management network element instructs the network element serving the terminal's session to detect whether the data in the session contains services corresponding to the two data network access ranges; if the data in the session contains services corresponding to the two data network access ranges, it indicates that the user plane event has been detected; otherwise, the user plane event has not been detected. Accordingly, upon detecting the user plane event, the method further includes: The session management network element determines the first user plane network element to establish a tunnel based on at least one of the following: the location of the terminal, edge application service information, and information related to the services corresponding to the two data network access ranges in the data packets of the session. The first user plane network element establishes a tunnel with the second user plane network element, and the second user plane network element corresponds to the second data network access range.

25. A communication device, characterized in that, The apparatus includes a module for performing the method as described in any one of claims 1-24.

26. A communication device, characterized in that, The communication device includes a processor and a memory; the memory is used to store computer instructions, which, when executed by the processor, cause the communication device to perform the method as described in any one of claims 1-24.

27. A communication system, characterized in that, The system includes at least one of the following: one or more network elements for performing the method described in any one of 1-24.

28. A computer-readable storage medium, characterized in that, The computer-readable storage medium includes a computer program or instructions that, when executed on a computer, cause the computer to perform the method as described in any one of claims 1-24.

29. A computer program product, characterized in that, The computer program product includes a computer program or instructions that, when run on a computer, cause the computer to perform the method as described in any one of claims 1-24.

Images