Communication method and communication apparatus
By generating routing rules, ensure that the services accessed by the terminal device in the VPLMN are authorized by HPLMN, the problem that HPLMN cannot control local shunt services is solved, and effective control of service access is achieved.
Patent Information
- Application Number
- PCT/CN2024/091594
- Authority / Receiving Office
- WO · WO
- Patent Type
- Applications
- Current Assignee / Owner
- Priority Date
- 2023-05-19
- Filing Date
- 2024-05-08
- Publication Date
- 2024-11-28
AI Technical Summary
In the home routing roaming scenario, HPLMN cannot control the services accessed by the terminal device through the VPLMN, resulting in the inability to effectively control the local shunt services.
By generating routing rules, indicating whether the traffic accessed by the terminal device in the VPLMN is authorized by the HPLMN, ensuring that the terminal device uses the appropriate source address to achieve HPLMN control of local shunt services. This routing rule is generated based on the information provided by HPLMN and the source address used by the terminal device in the VPLMN, ensuring the accuracy and legality of service shunts.
It realizes HPLMN's control over the service access of terminal devices in VPLMN, ensures the accuracy and legality of service shunts, and solves the problem that HPLMN cannot control local shunts services.
Smart Images

Figure CN2024091594_28112024_PF_FP_ABST
Abstract
Description
Communication method and communication device
[0001] This application claims priority to the Chinese patent application filed with the State Intellectual Property Office of China on May 19, 2023, with application number 202310576706.1 and application name “Communication Method and Communication Device”, the entire contents of which are incorporated by reference into this application. Technical Field
[0002] The present application relates to the field of communications, and in particular to a communication method and a communication device. Background Art
[0003] In the home routed (HR) roaming scenario, a new edge computing scenario exists: the home routed with session breakout (HR-SBO) roaming scenario. In this HR-SBO scenario, a session of a terminal device can access services through the home public land mobile network (HPLMN) while accessing the edge hosting environment (EHE) through local offload to the visited public land mobile network (VPLMN). To maintain the HPLMN's control over the locally offloaded services, the HPLMN needs to control the services accessed by the terminal device in the VPLMN.
[0004] However, the HPLMN cannot control the services that the terminal device accesses through the VPLMN, resulting in the HPLMN being unable to control the local offload services.
[0005] Summary of the Invention
[0006] The present application provides a communication method and a communication device, which are beneficial for the HPLMN to control the services accessed by terminal devices in the VPLMN.
[0007] In a first aspect, a communication method is provided, which is applied to a first network element, the method comprising: generating a routing rule based on first information and second information, the first information being used to indicate a service allowed to be routed to a local data network in a VPLMN, the second information comprising a source address used by a terminal device, the routing rule being used by the terminal device to select the source address according to the routing rule; and sending the routing rule.
[0008] The first information is used to indicate the services that are allowed to be routed to the local data network in the VPLMN. It can also be understood that the first information is used to indicate the services that the HPLMN authorizes the terminal device to access in the VPLMN, or in other words, the first information is used to indicate that the HPLMN allows the terminal device to be routed to the services of the local data network in the VPLMN. The services that are allowed to be routed to the local data network in the VPLMN can also be referred to as the services that the HPLMN authorizes the terminal device's session to access in the VPLMN, or the services that the HPLMN authorizes the terminal device's session to access via the VPLMN and routed to the local data network, or the services that the HPLMN authorizes the terminal device's session to access via the VPLMN and routed to the local data network in the VPLMN. In other words, the services that the terminal device accesses are services authorized by the HPLMN. When accessing the services, the terminal device can access the server through the VPLMN, or the traffic reaches the server through the VPLMN. It should be noted that the server does not necessarily belong to the VPLMN.
[0009] In one example, the first information is used to instruct the HPLMN to allow the HR-SBO session of the terminal device to be routed to the service of the local data network in the VPLMN. The first information can be referred to as a VPLMN-specific offload policy, a VPLMN-specific offload policy, VPLMN-specific offload information, or VPLMN-specific offload information.
[0010] In another example, the first information may also be referred to as HPLMN authorization information, which is not limited in this application.
[0011] The number of services allowed to be routed to the local data network in the VPLMN may be zero, one, or multiple, which is not limited in this application.
[0012] This application is applicable to multi-homing sessions, which may be Internet Protocol version 6 (IPv6) multi-homing sessions, but this application is not limited to this. A terminal device may use a source address in a multi-homing session. The source address used by a terminal device in a multi-homing session can be understood as the source address selected in the multi-homing session. The source address may be an IPv6 prefix, but this application is not limited to this.
[0013] A multi-homed routing session can be used to access services in a VPLMN or a HPLMN. If a terminal device accesses a service in a VPLMN through a multi-homed routing session, it can also be referred to as the terminal device accessing a service through the VPLMN, or it can be referred to as the terminal device accessing a service in the VPLMN. Correspondingly, if a terminal device accesses a service in the HPLMN through a multi-homed routing session, it can also be referred to as the terminal device accessing a service through the HPLMN, or it can be referred to as the terminal device accessing a service in the HPLMN. A terminal device accessing a service in the HPLMN or VPLMN through a multi-homed routing session can be understood as the terminal device's uplink service message reaching a server (e.g., an edge application server or application server) through the core network and data network of the HPLMN or VPLMN; it can also be understood as the terminal device accessing the data network in the HPLMN through a session, or accessing the edge application server in the VPLMN through a session; it can also be understood as the terminal device's traffic being routed to the application server in the HPLMN, or the traffic being locally routed to the edge application server in the VPLMN. Traffic being locally routed to the edge application server in the VPLMN can also be referred to as traffic being locally routed to the edge application server through the VPLMN.
[0014] A terminal device needs to use a source address when accessing services via a VPLMN or HPLMN. The second information includes the source address used by the terminal device. In one example, the source address used by the terminal device in a multi-homed session. The second information includes the source address used by the terminal device. This can be understood as including the source address used by the terminal device when accessing services via a VPLMN and / or the source address used by the terminal device when accessing services via an HPLMN.
[0015] The services accessed by the terminal device through the VPLMN or HPLMN may include video services, chat services, browser services, etc., which are not limited in this application.
[0016] The first information and / or the second information may be local to the first network element or may be information obtained from other network elements, which is not limited in this application. If the first information and / or the second information is local to the first network element, this helps save information exchange between different network elements. If the first information and / or the second information is obtained from other network elements, generating routing rules after receiving the information helps save local storage space or save computing power for generating the information.
[0017] The first network element generates a routing rule based on the first information and the second information. That is, the routing rule takes into account the services that the HPLMN authorizes the terminal device to access in the VPLMN and the source address used by the terminal device when accessing the service. The routing rule can be used by the terminal device to determine the source address used when accessing the service, or in other words, the routing rule is used by the terminal device to select the source address according to the routing rule.
[0018] In the communication method provided by the present application, the first information is used to indicate the services allowed to be routed to the local data network in the VPLMN, and the second information includes the source address used by the terminal device. The routing rules generated based on the first information and the second information can guide the terminal device to select a suitable source address to access the service in the VPLMN, which is conducive to the control of local diversion services.
[0019] In combination with the first aspect, in certain implementations of the first aspect, the first information includes a fully qualified domain name (FQDN) or a first address segment, the FQDN includes a service allowed to be routed to a local data network in the VPLMN, and the first address segment includes an address of a server allowed to be routed to a local data network in the VPLMN.
[0020] The FQDN includes services that are allowed to be routed to the local data network in the VPLMN. In one example, the FQDN can be the domain name of the service. The address in the first address segment can be an Internet Protocol (IP) address, a Media Access Control (MAC) address segment, an IPv6 prefix, or an Internet Protocol version 4 (IPv4) address, which is not limited in this application. The first information includes the FQDN or the first address segment. The number of FQDNs can be one or more, which is not limited in this application.
[0021] In combination with the first aspect, in certain implementations of the first aspect, the source address included in the second information is a source address used when the terminal device routes services to a local data network in the VPLMN.
[0022] The source address is the source address used by the terminal device when routing to services on the local data network in the VPLMN. It can also be understood that the source address is the address used to access services through the VPLMN. In a multi-homed session, the source address can be the source address used by the terminal device when routing to services on the local data network in the VPLMN in the multi-homed session. The first network element generates a routing rule based on the source address included in the first information and the second information, so that the terminal device can use the source address included in the second information when accessing services on the local data network in the VPLMN.
[0023] In combination with the first aspect, in certain implementations of the first aspect, the second information also includes a data network access identifier DNAI corresponding to the source address and / or a second address segment, wherein the second address segment may include the address of a service that can be accessed using the source address, and the DNAI may include the DNAI where the service that can be accessed using the source address is located.
[0024] There can be one or more DNAIs. The address in the second address segment can be an IP address, a MAC address segment, an IPv6 prefix, or an IPv4 address, which is not limited in this application. The second address segment can be a continuous address or a discontinuous address, which is not limited in this embodiment of the present application. The second address segment can be the address segment corresponding to the DNAI, that is, the address segment of a server (such as an edge application server (EAS)) in the VPLMN (for example, the address of the optimal EAS server when accessing the DN through this DNAI). There is a mapping relationship between the DNAI and the second address segment. If the second information includes the DNAI corresponding to the first address, the first network element can determine the second address segment based on the DNAI. If the second information includes the DNAI corresponding to the first address and the second address segment, that is, the second information includes the mapping relationship between the DNAI and the second address segment. If the second address segment is a second IP segment, the DNAI or second IP segment where the service accessible by the first address involved in this application is located can be: the DNAI / IP segment includes the DNAI or IP segment supported by the anchor user plane function (UPF) that allocates the first address.
[0025] Optionally, the DNAI and / or the second address segment corresponding to the above-mentioned source address, wherein corresponding can also be understood as related. One possible way of "corresponding or related" is that the terminal device is routed to the service of the local data network in the VPLMN through the network element that allocates the source address in the multi-homed session. Optionally, the above-mentioned second address segment can be obtained by the session management function network element in the VPLMN through the DNAI and the server in the VPLMN of the VPLMN, such as EAS deployment information (for example, the session management function network element in the VPLMN obtains the DNAI from the L-PSA of the VPLMN, and the session management function network element in the VPLMN obtains the EAS deployment information through local configuration or from the unified data management function (which can be obtained through NEF in the middle), and there is a correspondence between DNAI and IP segment in the deployment information, thereby obtaining the second address segment corresponding to the DNAI).
[0026] The source address included in the second information may be the IPV6 prefix newly allocated by the UPF, and the UPF may be an anchor point UPF (packet data unit session anchor (PSA)), a local anchor point UPF (local packet data unit session anchor (L-PSA)) or a local anchor point UPF in the VPLMN (i.e., L-PSA in the VPLMN).
[0027] In combination with the first aspect, in certain implementations of the first aspect, the above method is applied to a home routing session group HR-SBO roaming scenario.
[0028] In combination with the first aspect, in some implementations of the first aspect, the method further includes: receiving second information from the second network element during the process of establishing or modifying a home routing session group HR-SBO session.
[0029] If the first network element has pre-set first information or can generate the first information based on local information, during the HR-SBO session establishment or modification process, the first network element receives second information from the second network element and can generate routing rules based on the first and second information. In this implementation, the first network element only needs to receive the second information to generate routing rules, as it already has the first information, which helps save signaling interaction.
[0030] If the first network element does not have the first information preset, during the HR-SBO session establishment or modification process, the first network element receives the second information from the second network element and may also receive the first information from other network elements. The other network element refers to a network element other than the first network element, and may or may not be the second network element, which is not limited in this application. In this implementation, the first network element does not need to preset or generate the first and second information, which helps save the storage capacity or computing power of the first network element.
[0031] Optionally, the second network element obtains the second information from the L-PSA, wherein the second network element and the L-PSA are in the same PLMN. In other words, the second information sent by the second network element to the first network element may not be generated or preset by the second network element, but may be sent by the L-PSA in the same PLMN as the second network element.
[0032] With reference to the first aspect, in some implementations of the first aspect, the first network element is a session management function network element in the HPLMN, and the second network element is a session management function network element in the VPLMN.
[0033] The session management function network element is used to represent a network element with session management function, such as session management function (SMF). The session management function network element in the HPLMN and the session management function network element in the VPLMN provide services for the same session.
[0034] In combination with the first aspect, in some implementations of the first aspect, when the first network element is a session management function network element in the HPLMN, the method further includes: receiving first information from a policy control function network element in the HPLMN.
[0035] If the first network element has the second information pre-set or can generate the second information based on local information, during the HR-SBO session establishment or modification process, the first network element receives the first information from the policy control function network element in the HPLMN and can generate routing rules based on the first and second information. In this implementation, the first network element includes the second information and only needs to receive the first information to generate the routing rules, which helps save signaling interaction.
[0036] If the first network element does not have the second information preset, during the HR-SBO session establishment or modification process, the first network element receives the first information from the policy control function network element in the HPLMN and may also receive the second information from other network elements. The other network elements are network elements other than the first network element, and may or may not be policy control function network elements in the HPLMN. This is not limited in this application. In this implementation, the first network element does not need to preset or generate the first and second information, which helps save the first network element's storage capacity or computing power for generating information.
[0037] In combination with the first aspect, in certain implementations of the first aspect, the above method also includes: sending an FQDN to a session management function network element in the VPLMN, where the FQDN includes services allowed to be routed to a local data network in the VPLMN; and receiving a third address segment corresponding to the FQDN from the session management function network element in the VPLMN, where the first information includes the third address segment.
[0038] The session management function network element in the VPLMN can determine the third address segment corresponding to the FQDN based on the FQDN. The third address segment corresponding to the FQDN means that the session management function network element in the VPLMN obtains the address segment corresponding to the FQDN based on the EAS deployment information of the VPLMN. The third address segment has the same function as the first address segment mentioned above. The FQDN in the EAS deployment information refers to the supported FQDN of the application deployed in the local part of the DN. The address segment in the EAS deployment information refers to the IP address / address segment of one or more EAS in the local data network. The third address segment can be understood as the address segment of the service allowed to be routed to the local data network in the VPLMN.
[0039] The FQDN corresponds to the third address segment, which can also be understood as the third address segment being generated based on the FQDN, or the third address segment being obtained based on the FQDN, or the session management function network element in the VPLMN obtaining the third address segment based on the FQDN. This application does not limit this. The first network element can generate a routing rule based on the third address segment and the second information.
[0040] In this implementation, the session management function network element in the VPLMN obtains the third address segment corresponding to the FQDN based on the FQDN and sends the third address segment to the first network element. The first network element does not need to generate the third address segment, which is beneficial to saving the ability of the first network element to generate the third address segment.
[0041] In combination with the first aspect, in certain implementations of the first aspect, the first network element is a session management function network element in the VPLMN. When the first information includes the FQDN, a routing rule is generated based on the first information and the second information, including: generating a routing rule based on the third address segment corresponding to the FQDN and the second information, where the FQDN includes services allowed to be routed to the local data network in the VPLMN.
[0042] In this implementation mode, the session management function network element in the VPLMN determines the third address segment based on the FQDN and uses the third address segment to generate routing rules, which has high initiative.
[0043] In combination with the first aspect, in some implementations of the first aspect, sending the routing rule includes: sending the routing rule to the terminal device.
[0044] The first network element may send routing rules to the terminal device for use by the terminal device when accessing a service. The terminal device may determine the source address based on the routing rules when accessing the service. The first network element may send the information directly to the terminal device or through one or more network elements, which is not limited in this application.
[0045] In combination with the first aspect, in certain implementations of the first aspect, when the first network element is a session management function network element in the HPLMN, sending routing rules includes: sending routing rules to the UPF or protocol data unit session anchor PSA in the HPLMN, and the UPF or PSA is used to send the routing rules to the terminal device.
[0046] This implementation method forwards the routing rules to the terminal device through the UPF or PSA in the HPLMN, which is conducive to maintaining the control capability of the session management function network element in the HPLMN over the terminal device.
[0047] In combination with the first aspect, in certain implementations of the first aspect, when the first network element is a session management function network element in a VPLMN or a policy control function network element in an HPLMN, sending routing rules includes: sending routing rules to a session management function network element in the HPLMN, where the session management function network element is used to send the routing rules to a terminal device.
[0048] In this implementation, the session management function network element in the VPLMN or the policy control function network element in the HPLMN forwards the routing rules to the terminal device through the session management function network element in the HPLMN, which is conducive to maintaining the control capability of the session management function network element in the HPLMN over the terminal device.
[0049] In combination with the first aspect, in certain implementations of the first aspect, when the first network element is a session management function network element in a VPLMN, sending routing rules includes: sending routing rules to a local protocol data unit session anchor (local packet data unit session anchor, L-PSA) in the VPLMN, and the L-PSA is used to send the routing rules to the terminal device.
[0050] In this implementation, the session management function network element in the VPLMN forwards the routing rules to the terminal device through the network element in the VPLMN. Compared with sending the routing rules to the network element in the HPLMN and forwarding them to the terminal device by the network element in the HPLMN, it is beneficial to shorten the transmission path.
[0051] In combination with the first aspect, in certain implementations of the first aspect, the first information includes a first address segment, the second information includes a source address and a second address segment corresponding to the source address, and the routing rules used by the terminal device to access the service based on the first information and the second information include: using the intersection of the first address segment and the second address segment as the target address segment; generating routing rules based on the source address and the target address segment, and the routing rules are used to indicate that the source address is used as the source address when accessing the service in the VPLMN when accessing the server in the target address segment.
[0052] The second information includes a source address and a second address segment corresponding to the source address, where the number of source addresses can be one or more. If there are multiple source addresses, then there are also multiple second address segments corresponding to the source addresses, i.e., there is a one-to-one correspondence between the source addresses and the second address segments. If there are multiple second address segments, the first network element can take the intersection of these multiple second address segments and the first address segment as the target address segment, and the number of target address segments will be multiple.
[0053] The routing rule is used to indicate that when accessing a server in the target address segment, the source address is used to access the service in the VPLMN, so that the terminal device can access the service in the server. If the address of the server is in the target address segment, the terminal device can use the source address to access the service in the VPLMN.
[0054] If the first information includes FQDN and the second information includes DNAI, the first network element first determines the third address segment corresponding to the FQDN based on the FQDN in the first information, and determines the second address segment based on the DNAI in the second information, and then uses the intersection of the third address segment and the second address segment as the target address segment, and generates routing rules based on the source address and target address segments.
[0055] It is understandable that if the first information includes an FQDN and the second information includes a second address segment, the first network element first determines the third address segment corresponding to the FQDN based on the FQDN in the first information, then uses the intersection of the third address segment and the second address segment as the target address segment, and generates routing rules based on the source address and target address segments. If the first information includes a first address segment and the second information includes a DNAI, the first network element first determines the second address segment based on the DNAI in the second information, then uses the intersection of the first address segment and the second address segment as the target address segment, and generates routing rules based on the source address and target address segments.
[0056] In combination with the first aspect, in certain implementations of the first aspect, generating routing rules based on the first information and the second information includes: generating routing rules based on the first information, the second information, the third information and the fourth information, the third information is used to indicate services allowed to be routed to the data network in the HPLMN, the fourth information includes the source address used by the terminal device, and the fourth information is different from the second information.
[0057] The source address included in the fourth information may be obtained by the first network element from the PSA of the HPLMN. The second information may be obtained by the first network element from the L-PSA of the VPLMN. The fourth information is different from the second information.
[0058] The first network element generates routing rules used by the terminal device to access services based on the first information, the second information, the third information and the fourth information. The terminal device can access services authorized by the HPLMN in the VPLMN and access services authorized by the HPLMN in the HPLMN, which is conducive to the HPLMN's control over the terminal device's access to services.
[0059] In a second aspect, a communication method is provided, which is applied to a terminal device, and the method includes: receiving a routing rule for selecting a source address; and sending information for accessing a service, wherein the information for accessing the service includes a source address selected according to the routing rule.
[0060] When the terminal device uses the source address, it can select a suitable source address based on the routing rules, and send information for accessing the service based on the source address. In the multi-homing session scenario, the use of routing rules: When the terminal device has an IPv6 multi-homing protocol data unit (PDU) session, the terminal device selects the source IPv6 prefix according to the routing rules. This routing rule can be sent to the terminal device by the network (such as the 5G core network). In another example, the routing rules can also be configured locally on the terminal device. The content of the routing rules in the multi-homing session can be the correspondence between the source address and the address segment, where the source address is the source address used by the terminal device in the multi-homing session, and the address segment corresponding to the source address is the address segment of the server, that is, the destination address segment corresponding to the source address in the multi-homing session. The routing rules in the multi-homing session generally include multiple such correspondences.
[0061] When accessing a service, a terminal device can select a source address based on routing rules and, based on the source address, send information for accessing the service to a diversion device, such as a UPF with a branching point (BP) function. The source address can be an IP address or a MAC address, which is not limited in this application. A UPF supporting the BP function can divert the service to a VPLMN or HPLMN based on the source address in the service access information.
[0062] In conjunction with the second aspect, in certain implementations of the second aspect, the source address is a source address of a service routed to the VPLMN local data network.
[0063] The source address is used as the source address for services routed to the VPLMN local data network, and can also be understood as the source address used to access services authorized by the home public land mobile network HPLMN in the VPLMN.
[0064] If the terminal device is within the coverage of the VPLMN and the service accessed by the terminal device is accessible in the VPLMN after being authorized by the HPLMN, the terminal device can access the service in the VPLMN based on the source address determined by the routing rule.
[0065] In combination with the second aspect, in some implementations of the second aspect, the source address is determined based on the destination address and routing rules; the method further includes: receiving the destination address.
[0066] The destination address is the address of the server accessed by the terminal device. If the routing rule includes the same address as the destination address, the terminal device can use its corresponding source address to access the service.
[0067] This implementation method determines the source address based on the destination address and routing rules, which helps to improve the accuracy of determining the source address and thus access services through the appropriate PLMN.
[0068] In conjunction with the second aspect, in certain implementations of the second aspect, the information used to access the service further includes a destination address, and the destination address is used to route to an address of a server in a local data network in the VPLMN.
[0069] This implementation method is conducive to the diversion point to divert services based on the source address, thereby improving the accuracy of service diversion.
[0070] In combination with the second aspect, in certain implementations of the second aspect, receiving the routing rules used when accessing the service includes: receiving routing rules from a session management function network element in a visited public land mobile network VPLMN or a session management function network element in a home public land mobile network HPLMN.
[0071] In combination with the second aspect, in some implementations of the second aspect, the routing rules are generated based on first information and second information, the first information is used to indicate services allowed to be routed to the local data network in the VPLMN, and the second information includes a source address used by the terminal device.
[0072] In combination with the second aspect, in certain implementations of the second aspect, the first information includes a fully qualified domain name FQDN or a first address segment, the FQDN includes a service allowed to be routed to a local data network in the VPLMN, and the first address segment includes an address of a server allowed to be routed to a local data network in the VPLMN.
[0073] In conjunction with the second aspect, in certain implementations of the second aspect, the source address included in the second information is a source address used when routing services to a local data network in the VPLMN.
[0074] In combination with the second aspect, in some implementations of the second aspect, the second information further includes a data network access identifier DNAI corresponding to the source address and / or a second address segment.
[0075] According to a third aspect, a communication device is provided, comprising: a processing unit and a transceiver unit. The processing unit is configured to generate a routing rule based on first information and second information, wherein the first information indicates a service permitted to be routed to a local data network in a VPLMN, the second information includes a source address used by a terminal device, and the routing rule instructs the terminal device to select the source address according to the routing rule; and the transceiver is configured to transmit the routing rule.
[0076] In combination with the third aspect, in certain implementations of the third aspect, the first information includes a fully qualified domain name FQDN or a first address segment, the FQDN includes a service allowed to be routed to a local data network in the VPLMN, and the first address segment includes the address of a server allowed to be routed to a local data network in the VPLMN.
[0077] In combination with the third aspect, in certain implementations of the third aspect, the source address included in the second information is a source address used when the terminal device routes services to a local data network in the VPLMN.
[0078] In combination with the third aspect, in certain implementations of the third aspect, the second information further includes a data network access identifier DNAI corresponding to the source address and / or a second address segment.
[0079] In combination with the third aspect, in certain implementations of the third aspect, it is applied to a home routing session group HR-SBO roaming scenario.
[0080] In combination with the third aspect, in certain implementations of the third aspect, the transceiver unit is further configured to: receive second information from the second network element during establishment or modification of a home routing session group HR-SBO session.
[0081] In combination with the third aspect, in certain implementations of the third aspect, the above-mentioned device is a session management function network element in the HPLMN, and the second network element is a session management function network element in the VPLMN.
[0082] In combination with the third aspect, in certain implementations of the third aspect, when the above-mentioned device is a session management function network element in the HPLMN, the transceiver unit is further used to: receive first information from a policy control function network element in the HPLMN.
[0083] In combination with the third aspect, in certain implementations of the third aspect, the above-mentioned transceiver unit is also used to: send an FQDN to a session management function network element in the VPLMN, where the FQDN includes services allowed to be routed to a local data network in the VPLMN; and receive a third address segment corresponding to the FQDN from the session management function network element in the VPLMN, where the first information includes the third address segment corresponding to the FQDN.
[0084] In combination with the third aspect, in certain implementations of the third aspect, the first network element is a session management function network element in the VPLMN, and when the first information includes the FQDN, the above-mentioned processing unit is also used to: generate routing rules based on the third address segment corresponding to the FQDN and the second information, and the FQDN includes services allowed to be routed to the local data network in the VPLMN.
[0085] In combination with the third aspect, in some implementations of the third aspect, the transceiver unit is further used to: send routing rules to the terminal device.
[0086] In combination with the third aspect, in certain implementations of the third aspect, when the above-mentioned device is a session management function network element in the HPLMN, the transceiver unit is also used to: send routing rules to the user plane function UPF or protocol data unit session anchor PSA in the HPLMN, and the UPF or PSA is used to send the routing rules to the terminal device.
[0087] In combination with the third aspect, in certain implementations of the third aspect, when the above-mentioned device is a session management function network element in a VPLMN or a policy control function network element in an HPLMN, the transceiver unit is also used to: send routing rules to the session management function network element in the HPLMN, and the session management function network element is used to send the routing rules to the terminal device.
[0088] In combination with the third aspect, in certain implementations of the third aspect, when the above-mentioned device is a session management function network element in a VPLMN, the transceiver unit is also used to: send routing rules to the local protocol data unit session anchor L-PSA in the VPLMN, and the L-PSA is used to send the routing rules to the terminal device.
[0089] In combination with the third aspect, in certain implementations of the third aspect, the first information includes a first address segment, the second information includes a source address and a second address segment corresponding to the source address, and the above-mentioned processing unit is also used to: use the intersection of the first address segment and the second address segment as the target address segment; generate routing rules based on the source address and the target address segment, and the routing rules are used to indicate that the source address is used to access the service in the VPLMN when accessing the server in the target address segment.
[0090] In combination with the third aspect, in certain implementations of the third aspect, the processing unit is further used to: generate routing rules based on the first information, the second information, the third information and the fourth information, the third information is used to indicate services allowed to be routed to the data network in the HPLMN, the fourth information includes the source address used by the terminal device, and the fourth information is different from the second information.
[0091] In a fourth aspect, a communication device is provided, comprising: a transceiver unit configured to: receive a routing rule used when selecting a source address; and send information for accessing a service, the information for accessing the service including a source address selected according to the routing rule.
[0092] In conjunction with the fourth aspect, in certain implementations of the fourth aspect, the source address is a source address of a service routed to the VPLMN local data network.
[0093] In combination with the fourth aspect, in certain implementations of the fourth aspect, the source address is determined based on the destination address and routing rules; and the transceiver unit is further used to: receive the destination address.
[0094] In conjunction with the fourth aspect, in certain implementations of the fourth aspect, the information used to access the service further includes a destination address, and the destination address is used to route to an address of a server in a local data network in the VPLMN.
[0095] In combination with the fourth aspect, in some implementations of the fourth aspect, the transceiver unit is further configured to: receive routing rules from a session management function network element in a visited public land mobile network VPLMN or a session management function network element in a home public land mobile network HPLMN.
[0096] In combination with the fourth aspect, in certain implementations of the fourth aspect, routing rules are generated based on first information and second information, the first information is used to indicate services allowed to be routed to the local data network in the VPLMN, and the second information includes a source address used by the terminal device.
[0097] In combination with the fourth aspect, in certain implementations of the fourth aspect, the first information includes a fully qualified domain name FQDN or a first address segment, the FQDN includes a service allowed to be routed to a local data network in the VPLMN, and the first address segment includes the address of a server allowed to be routed to a local data network in the VPLMN.
[0098] In combination with the fourth aspect, in certain implementations of the fourth aspect, the source address included in the second information is a source address used when routing services to a local data network in the VPLMN.
[0099] In combination with the fourth aspect, in certain implementations of the fourth aspect, the second information further includes a data network access identifier DNAI corresponding to the source address and / or a second address segment.
[0100] In a fifth aspect, a communication device is provided, comprising: a processor, wherein the processor is configured to execute the method described in any aspect and any possible implementation of any aspect.
[0101] The communication device may further include a memory for storing instructions and data. The memory is coupled to the processor, and when the processor executes the instructions stored in the memory, the methods described in the above aspects may be implemented. The communication device may further include a communication interface for communicating with other devices. Exemplarily, the communication interface may be a transceiver, circuit, bus, module, or other type of communication interface.
[0102] In a sixth aspect, a communication system is provided, comprising the communication device of the third aspect and the communication device of the fourth aspect.
[0103] In a seventh aspect, a communication device is provided, comprising: a processor, the processor being coupled to a memory, the memory being used to store instructions, and when the processor calls the instruction, the communication device executes a method in any possible implementation of any of the above aspects.
[0104] In an eighth aspect, a chip system is provided, comprising: a processor for calling and executing instructions from a memory, so that the chip system executes a method in any possible implementation of any of the above aspects.
[0105] In the ninth aspect, a computer-readable storage medium is provided, which stores a computer program (also referred to as code, or instructions) which, when run on a computer, enables the computer to execute a method in any possible implementation of any of the above aspects.
[0106] In the tenth aspect, a computer program product is provided, which includes: a computer program (also referred to as code, or instructions), which, when executed, enables a computer to execute a method in any possible implementation of any of the above aspects. BRIEF DESCRIPTION OF THE DRAWINGS
[0107] Figure 1 is a schematic block diagram of a non-roaming 5G edge computing offload architecture;
[0108] FIG2 is a schematic block diagram of an HR-SBO roaming offload architecture applicable to an embodiment of the present application;
[0109] FIG3 is a schematic flow chart of a communication method provided in an embodiment of the present application;
[0110] FIG4 is a schematic flow chart of a method for processing routing rules provided in an embodiment of the present application;
[0111] FIG5 is a schematic flowchart of another method for processing routing rules provided in an embodiment of the present application;
[0112] FIG6 is a schematic flowchart of another method for processing routing rules provided in an embodiment of the present application;
[0113] FIG7 is a schematic flowchart of another method for processing routing rules provided in an embodiment of the present application;
[0114] FIG8 is a schematic flowchart of another method for processing routing rules provided in an embodiment of the present application;
[0115] FIG9 is a schematic flowchart of another method for processing routing rules provided in an embodiment of the present application;
[0116] FIG10 is a schematic flowchart of another method for processing routing rules provided in an embodiment of the present application;
[0117] FIG11 is a schematic flowchart of another method for processing routing rules provided in an embodiment of the present application;
[0118] FIG12 is a schematic block diagram of a communication device provided in an embodiment of the present application;
[0119] FIG13 is a schematic block diagram of another communication device provided in an embodiment of the present application. DETAILED DESCRIPTION
[0120] The technical solution in this application will be described below with reference to the accompanying drawings.
[0121] In order to better understand the embodiments of the present application, the scenarios involved in the embodiments of the present application are first introduced.
[0122] 1. Edge computing (EC)
[0123] In the fourth-generation (4G) mobile communication technology and previous traditional mobile network architectures and deployments, user-plane equipment generally follows a tree topology. Uplink user packets pass through base stations and backhaul networks before ultimately accessing the data network through centrally deployed anchor gateways. These anchor gateways are typically located higher in the network, such as in regional central equipment rooms. This relatively simple topology facilitates centralized service control and packet processing at the anchor points.
[0124] However, with the explosive growth of mobile service traffic, this deployment model is increasingly unable to support this rapidly increasing mobile service traffic model. On the one hand, in a network with centralized anchor gateway deployment, the increasing traffic ultimately concentrates at the gateways and core equipment rooms, placing increasingly stringent requirements on backhaul network bandwidth, equipment room throughput, and gateway specifications. On the other hand, the long backhaul network distance from access points (i.e., base stations) to anchor gateways and the complex transmission environment also lead to significant latency and jitter in user message transmission.
[0125] Against this backdrop, the industry has proposed the concept of edge computing (EC). Building on this deployment, the UPF and service processing capabilities are moved down to the network edge, enabling local processing of distributed service traffic and avoiding excessive traffic concentration. This significantly reduces the specification requirements for core equipment rooms and centralized gateways, while also shortening the distance of the backhaul network and reducing the end-to-end (E2E) latency and jitter of user packets, making the deployment of ultra-low-latency services possible.
[0126] 2. Multi-homed PDU session
[0127] When accessing a service, the terminal device can establish a PDU session and access the service through the PDU session. If a PDU session can be associated with multiple IPv6 prefixes, the PDU session is called a multi-homed PDU Session. A multi-homed PDU session supports access to the data network through multiple PDU session anchors. Different user plane paths leading to different PDU session anchors can be diverted at the UPF that supports the branching point (BP) function. In other words, the UPF that supports the BP function can divert the service in the session according to the IP address used by the terminal device when accessing the service, that is, when a certain IP address is used to access the service, it will be diverted to the PDU session anchor assigned to the IP address. The UPF that supports the BP function provides uplink traffic diversion to different PDU session anchors and downlink traffic merging to the UE, that is, it merges the downlink traffic from different PDU session anchors into the link to the terminal device.
[0128] When a terminal device has the function of establishing an IPv6 multi-homed PDU session, the terminal device can select a source IPv6 prefix based on an IPv6 multi-homed routing rule pre-configured in the terminal device or received from the network, and establish an IPv6 multi-homed PDU session using the source IPv6 prefix. The IPv6 multi-homed routing rule received from the network has a higher priority than the IPv6 multi-homed routing rule pre-configured by the terminal device. For ease of description, the IPv6 multi-homed routing rule will be referred to as the routing rule in the following text.
[0129] The session management function (SMF) can generate routing rules for terminal devices based on local configuration or dynamic policy control and charging (PCC) rules received from the policy control function (PCF). If dynamic PCC rules are deployed, the SMF can generate routing rules for the source IPv6 prefix based on the service data flow template of the PCC rule for the source IPv6 prefix. These rules contain the DNAI corresponding to the newly assigned IPv6 prefix. The SMF can send routing rules to the terminal device at any time during the life cycle of the IPv6 multi-homed PDU session by sending a router advertisement (RA) message through the UPF.
[0130] 3. Roaming
[0131] In a certain country or region, a certain type of cellular mobile communication network of a certain operator is called a public land mobile network (PLMN). The PLMN to which a terminal device subscribes is called an HPLMN, which represents the home operator of the subscribed user. When a terminal device leaves the coverage of the HPLMN due to movement or other reasons, if there is a PLMN that meets the following conditions: (1) it can cover the current location of the terminal device; (2) its operator has signed a roaming agreement with the operator of the HPLMN of the terminal device (a commercial agreement between operators, the content of which may include but is not limited to the services and billing methods provided to the subscribed users of the other operator's network), then the terminal device can access this PLMN, which is called a VPLMN (Visited PLMN). The terminal device accessing the VPLMN is called roaming.
[0132] Depending on whether the user plane of a terminal device terminates in a VPLMN or an HPLMN, roaming scenarios can be categorized as local breakout (LBO) roaming and home routed (HR) roaming. In LBO roaming, the HPLMN does not restrict the services a terminal device can access in the VPLMN. In HR roaming, the HPLMN does restrict the services a terminal device can access in the VPLMN.
[0133] Edge computing can be introduced in both roaming and non-roaming scenarios. In non-roaming scenarios, terminal devices can access services on different data networks. In HR roaming scenarios, there is a new edge computing scenario, namely the HR-SBO roaming scenario. In this HR-SBO scenario, a session of a terminal device can access services through the HPLMN while accessing EHE through local diversion to the VPLMN. This application takes the non-roaming 5G edge computing diversion architecture and the HR-SBO roaming diversion architecture as examples to introduce in detail the process of terminal devices accessing services.
[0134] For example, Figure 1 shows a schematic block diagram of a non-roaming 5G edge computing offload architecture 100. As shown in Figure 1, the architecture 100 includes a terminal device, an access node (AN), a UPF supporting BP function, a UPF supporting central packet data unit session anchor (C-PSA) function, an application server (AS), a UPF supporting L-PSA function, an EAS, a network repository function (NRF), a PCF, an application server (AF), a unified data management (UDM), an access and mobility management function (AMF), an SMF, a network exposure function (NEF), and an edge application server discovery network element (EASDF). Among them, the UPF supporting BP function can also be called BP, the UPF supporting C-PSA function can also be called C-PSA, and the UPF supporting L-PSA function can also be called L-PSA, which is not limited in this embodiment of the present application. AN can be a base station, but the embodiment of the present application is not limited to this. AS can be part of the (remote or central) DN, and EAS can be part of the local DN. In this architecture 100, the embodiments of the present application focus on devices other than NRF, AF, UDM, AMF, NEF and EASDF. AMF communicates with the terminal device through the N1 interface, AMF communicates with the AN through the N2 interface, AN communicates with the BP through the N3 interface, L-PSA communicates with the local DN through the N6 interface, SMF communicates with the L-PSA, BP or C-PSA through the N4 interface, BP communicates with the C-PSA through the N9 interface, and C-PSA communicates with the (remote or central) DN through the N6 interface.PCF, AF, UDM, AMF, SMF, NEF and EASDF can call Nnrf to send messages to NRF, NRF, AF, UDM, AMF, SMF, NEF and EASDF can call Npcf to send messages to PCF, NRF, PCF, UDM, AMF, SMF, NEF and EASDF can call Naf to send messages to AF, NRF, PCF, AF, AMF, SMF, NEF and EASDF can call Nudm to send messages to UDM, NRF, PCF, AF, UDM, SMF, NEF and EASDF can call Namf to send messages to AMF. NRF, PCF, AF, UDM, AMF, NEF and EASDF can call Nsmf to send messages to SMF. NRF, PCF, AF, UDM, AMF, SMF and EASDF can call Nnef to send messages to NEF. NRF, PCF, AF, UDM, AMF, SMF and NEF can call Neasdf to send messages to EASDF.
[0135] The terminal device can access the AS (application server) in the (remote / central) DN or the EAS (edge application server) in the local DN to access the service. For example, the SMF can generate routing rules for the terminal device based on the local configuration or the PCC rules received from the PCF. These rules contain the IPv6 prefix assigned by the L-PSA and its corresponding DNAI. The SMF can send the routing rules to the terminal device by sending an RA message on the user plane at any time during the life cycle of the IPv6 multi-homed PDU session. When the terminal device accesses the service through the IPv6 multi-homed PDU session, it can select multiple source IPv6 prefixes according to the routing rules received from the SMF, and access the AS in the (remote / central) DN or the EAS in the local DN through multiple source IPv6 prefixes.
[0136] For example, the terminal device sends a message for accessing the service to the BP through the AN in the IPv6 multi-homing PDU session. The BP receives the uplink message and can divert the service messages in the IPv6 multi-homing PDU session according to the multiple source IPv6 prefixes in the IPv6 multi-homing PDU session, that is, the service messages corresponding to these multiple source IPv6 prefixes are diverted to the C-PSA or L-PSA respectively to access the AS in the (remote / central) DN or the EAS in the local DN.
[0137] Figure 2 shows a schematic block diagram of an HR-SBO roaming offload architecture 200. As shown in Figure 2, the architecture 200 includes a terminal device, an AN, an HPLMN, and a VPLMN. The HPLMN includes a UPF, an AS, a PCF, an SMF, and an UDM. The AS can be part of the DN, the SMF communicates with the UPF via the N4 interface, and the UPF communicates with the DN via the N6 interface. The PCF and SMF can call Nudm to send messages to the UDM, the PCF and UDM can call Nsmf to send messages to the SMF, and the SMF and UDM can call Npcf to send messages to the PCF. The SMF can also be called a home SMF, i.e., an H-SMF. The UPF is the PDU session anchor point in the HPLMN.
[0138] The VPLMN includes the UPF (Uniform Functionality Provider) supporting the L-PSA function, the EAS, the UPF (Uniform Functionality Provider) supporting the Business Plan (BP), the NRF, the PCF, the AF, the AMF, the SMF, the NEF, and the EASDF. The EAS can be part of the local DN. The L-PSA is the PDU session anchor point in the VPLMN. The L-PSA communicates with the local DN over the N6 interface, and the SMF communicates with the L-PSA or BP over the N4 interface. PCF, AF, AMF, SMF, NEF and EASDF can call Nnrf to send messages to NRF. NRF, AF, AMF, SMF, NEF and EASDF can call Npcf to send messages to PCF. NRF, PCF, AMF, SMF, NEF and EASDF can call Naf to send messages to AF. NRF, PCF, AF, SMF, NEF and EASDF can call Namf to send messages to AMF. NRF, PCF, AF, AMF, NEF and EASDF can call Nsmf to send messages to SMF. NRF, PCF, AF, AMF, SMF and EASDF can call Nnef to send messages to NEF. NRF, PCF, AF, AMF, SMF and NEF can call Neasdf to send messages to EASDF.
[0139] Terminal devices can access services in the AS in the HPLMN or the EAS in the VPLMN. At the same time, services accessed by terminal devices in the EAS of the VPLMN need to be authorized by the HPLMN.
[0140] In the HR-SBO roaming offload architecture, the HPLMN needs to control the services accessed by terminal devices in the VPLMN to achieve control over local offload services. However, currently the HPLMN cannot control the services accessed by terminal devices in the VPLMN, resulting in the HPLMN being unable to control local offload services.
[0141] The applicant conducted research on this and found that the routing rules used by terminal devices to determine the source IP address did not take into account the services authorized by the HPLMN for the terminal devices to access in the VPLMN. BP could only divert services based on the source IP address used by the terminal device and would not screen whether the accessed services were authorized. Therefore, BP would divert unauthorized services to the VPLMN, causing the terminal device to access services in the VPLMN that were not authorized by the HPLMN, resulting in the HPLMN being unable to control the locally diverted services.
[0142] In view of this, an embodiment of the present application provides a communication method and a communication device, and the information for generating routing rules may include the services that the HPLMN authorizes the terminal device to access in the VPLMN. When the terminal device accesses the service, the source IP address determined based on the routing rule can access the service authorized by the HPLMN in the VPLMN.
[0143] The VPLMN and HPLMN in the methods provided in the embodiments of this application are not limited to PLMNs. They can also be two different areas, where one area authorizes a terminal device to access services in another area. In this scenario, all implementation methods provided in this application are applicable, except that the "VPLMN" and "HPLMN" are changed to two different areas.
[0144] To facilitate understanding of the method provided in the embodiments of the present application, the following points are first explained:
[0145] First, to clearly describe the technical solutions of the embodiments of this application, terms such as "first" and "second" are used in the embodiments of this application to distinguish between identical or similar items with substantially identical functions and effects. For example, the terms "first network element" and "second network element" are simply used to distinguish different network elements. Those skilled in the art will understand that terms such as "first" and "second" do not limit the number or order, and do not necessarily imply differences.
[0146] Second, "at least one" means one or more, and "more" means two or more. "And / or" describes the association relationship of associated objects, indicating that three relationships may exist. For example, A and / or B can mean: A exists alone, A and B exist at the same time, and B exists alone, where A and B can be singular or plural. The character " / " generally indicates that the previous and next associated objects are in an "or" relationship. "At least one of the following items" or similar expressions refers to any combination of these items, including any combination of single or plural items. For example, at least one of a, b and c can mean: a, or b, or c, or a and b, or a and c, or b and c, or a, b and c, where a, b, c can be single or multiple.
[0147] Third, in the embodiments of the present application, descriptions such as "when...", "in the case of...", "if" and "if" all mean that under certain objective circumstances, the device (such as the terminal device or access network device described below) will make corresponding processing, which is not a time limit, and does not require the device (such as the terminal device or access network device described below) to have a judgment action when implementing it, nor does it mean that there are other limitations.
[0148] The communication method provided in this application will be described in detail below with reference to the accompanying drawings.
[0149] It can be understood that the interaction process diagram of this application uses the first network element and the terminal device as examples of the execution subjects of the interaction diagram to illustrate the method provided by this application, but this application does not limit the execution subjects of the interaction diagram.
[0150] For example, the first network element may be a chip, a chip system, or a processor applied to the first network element, or a logical node, a logical module, or software that can implement all or part of the functions of the first network element. For another example, the terminal device may be a chip, a chip system, or a processor applied to the terminal device, or a logical node, a logical module, or software that can implement all or part of the functions of the terminal device.
[0151] FIG3 shows a schematic flow chart of a communication method 300 provided in an embodiment of the present application. The method 300 can be applied to the scenario shown in FIG2 above, but the embodiment of the present application is not limited thereto. As shown in FIG3 , the method 300 may include the following steps:
[0152] S301. The first network element generates a routing rule based on first information and second information, where the first information is used to indicate services that are allowed to be routed to the local data network in the VPLMN, and the second information includes a source address used by a terminal device. The routing rule is used by the terminal device to select the source address according to the routing rule.
[0153] The first information indicates services permitted to be routed to the local data network in the VPLMN. The services can be either FQDNs or address segments. Specifically, the first information indicates the FQDNs permitted to be routed to the local data network in the VPLMN, or the address segments permitted to be routed to the local data network in the VPLMN. Alternatively, the first information indicates the services authorized by the HPLMN for the terminal device to access in the VPLMN, or in other words, indicates that the HPLMN allows the terminal device to be routed to the local data network in the VPLMN. Services permitted to be routed to the local data network in the VPLMN can also be referred to as services authorized by the HPLMN for the terminal device's session to access in the VPLMN, services authorized by the HPLMN for the terminal device's session to access via the VPLMN, or services authorized by the HPLMN for the terminal device's session to be routed to the local data network in the VPLMN. Services authorized by the HPLMN for the terminal device's session to access via the VPLMN to the local data network, that is, services accessed by the terminal device are services authorized by the HPLMN. When accessing these services, the terminal device can access the server through the VPLMN, or traffic reaches the server through the VPLMN. It should be noted that the server does not necessarily belong to the VPLMN.
[0154] In one example, the first information is used to instruct the HPLMN to allow the HR-SBO session of the terminal device to be routed to the service of the local data network in the VPLMN. The first information can be referred to as a VPLMN-specific offload policy, a VPLMN-specific offload policy, VPLMN-specific offload information, or VPLMN-specific offload information.
[0155] In another example, the first information may also be referred to as HPLMN authorization information, which is not limited in the embodiments of the present application.
[0156] The number of services allowed to be routed to the local data network in the VPLMN may be zero, one, or multiple, and this is not limited in the embodiments of the present application. A multi-homed routing session may be used to access services in the VPLMN or services in the HPLMN. If a terminal device accesses a service in the VPLMN through a multi-homed routing session, it may also be referred to as the terminal device accessing the service through the VPLMN, or it may be referred to as the terminal device accessing the service in the VPLMN. Correspondingly, the terminal device accessing the service in the HPLMN may also be referred to as the terminal device accessing the service through the HPLMN, or it may be referred to as the terminal device accessing the service in the HPLMN. The terminal device accessing services in the HPLMN or VPLMN may be understood as the terminal device's uplink service message entering the data network through the anchor point UPF (PSA) of the core network of the HPLMN or VPLMN and reaching the server (e.g., edge application server or application server); it may also be understood as the terminal device accessing the data network in the HPLMN through a session, or accessing the edge application server in the VPLMN through a session; it may also be understood as the terminal device's traffic being routed to the application server in the HPLMN, or the traffic being locally routed to the edge application server in the VPLMN. The traffic being locally routed to the edge application server in the VPLMN may also be referred to as the traffic being locally routed to the edge application server through the VPLMN.
[0157] A terminal device must use a source address when accessing services via either a VPLMN or an HPLMN. The second information includes the source address used by the terminal device. In one example, the second information includes the source address used by the terminal device in a multi-homed session. The second information includes the source address used by the terminal device, which can be understood as including the source address used by the terminal device when accessing services via the VPLMN and / or the source address used by the terminal device when accessing services via the HPLMN. The second information includes the source address used by the terminal device, which can also be understood as including the source address used by the terminal device when accessing services. The second information can also be referred to as indicating the ability to access services. In other words, the second information indicates the ability to access services via the VPLMN and / or the ability to access services via the HPLMN. If the second information indicates the ability to access services via the VPLMN, the second information indicates the services that the terminal device can access in the VPLMN. Services accessible by the terminal device may include video services, chat services, or browser services, etc., which are not limited in this embodiment of the present application. If the second information indicates the ability to access services via the HPLMN, the second information indicates the services that the terminal device can access in the HPLMN. If the second information is used to indicate the capability of accessing services through the VPLMN and the capability of accessing services through the HPLMN, the second information is used to indicate the services that the terminal device can access in the VPLMN and the services that it can access in the HPLMN.
[0158] The first information and / or the second information may be local to the first network element or may be information obtained from other network elements, which is not limited in this embodiment of the present application. If the first information and / or the second information is local to the first network element, this helps save information exchange between different network elements. If the first information and / or the second information is obtained from other network elements, generating routing rules after receiving the information helps save local storage space or save computing power for generating information.
[0159] For example, in the scenario shown in FIG2 above, the first network element may be an SMF in the HPLMN, a PCF in the HPLMN, or an SMF in the VPLMN. If the first network element is an SMF in the HPLMN, the SMF in the HPLMN may locally store, generate, or receive first information from other network elements (such as the PCF in the HPLMN), and may receive second information from other network elements, such as the SMF in the VPLMN. If the first network element is a PCF in the HPLMN, the PCF in the HPLMN may receive first information and second information sent by other network elements. For example, the PCF in the HPLMN receives first information from the SMF in the HPLMN and second information from the SMF in the VPLMN, and the SMF in the VPLMN may send the second information to the PCF in the HPLMN via the SMF in the HPLMN. It is understandable that the network element that sends the first information to the PCF in the HPLMN and the network element that sends the second information may be the same network element or different network elements. If the first network element is an SMF in a VPLMN, the SMF in the VPLMN may locally store, generate, or receive the second information from another network element (such as the L-PSA of the VPLMN), and may receive the first information from another network element, such as the SMF in the HPLMN. For example, after the SMF in the VPLMN is inserted into the BP (such as in the scenario shown in FIG. 2 above), the second information may be obtained from the L-PSA. Alternatively, the first information may be received from the SMF in the HPLMN during the establishment or modification of the HR-SBO session.
[0160] Optionally, the first information includes a fully qualified domain name FQDN or a first address segment, the FQDN includes a service allowed to be routed to a local data network in the VPLMN for access, and the first address segment includes an address of a server allowed to be routed to a local data network in the VPLMN for access.
[0161] The FQDN includes services that are allowed to be routed to the local data network in the VPLMN. This can also be understood as the FQDN including services that the HPLMN authorizes the terminal device's session to access via the VPLMN and route to the local data network. This can be referred to as services that the HPLMN authorizes the terminal device's session to access in the VPLMN and can also be referred to as services that the HPLMN authorizes the terminal device's session to access via the VPLMN and route to the local data network in the VPLMN. In other words, the service accessed by the terminal device is a service authorized by the HPLMN. When accessing this service, the terminal device can access the server through the VPLMN, or the traffic reaches the server through the VPLMN. It should be noted that the server does not necessarily belong to the VPLMN.
[0162] The address in the first address segment can be an IP address, a MAC address, an IPv6 prefix, or an IPv4 address, which is not limited in this embodiment of the present application. The first information includes a fully qualified domain name (FQDN) or the first address segment. The number of FQDNs can be one or more, which is not limited in this application.
[0163] In one possible implementation, the first information includes an FQDN, i.e., a service that the HPLMN authorizes the terminal device session to access in the VPLMN. Generally, one FQDN corresponds to one service. However, when the HPLMN authorizes the terminal device session to access multiple services in the VPLMN, the first information may include multiple FQDNs. This embodiment of the present application also does not exclude the possibility that one FQDN corresponds to multiple services, or that multiple FQDNs correspond to one service.
[0164] For example, one FQDN corresponds to one service, and the FQDN corresponding to the Baidu service may be www.baidu.com. If the first information includes the FQDN corresponding to the Baidu service, it can be indicated that the HPLMN authorizes the session of the terminal device to access the Baidu service in the VPLMN.
[0165] In another possible implementation, the first information includes a first address segment, where the first address segment includes an address of a server that is allowed to be routed to a local data network in the VPLMN for access.
[0166] The first address segment includes the address of the server that is allowed to be routed to the local data network in the VPLMN. It can also be understood that the first address segment includes the address of the server that the HPLMN authorizes the session of the terminal device to access in the VPLMN.
[0167] The first address segment can be a continuous address or a discontinuous address, which is not limited in the embodiments of the present application. Each address included in the first address segment is the address of a server, which can also be called a destination address. The server is a device that provides services to the terminal device. In the scenario shown in Figure 2 above, the server can be an AS or an EAS. When the terminal device accesses a service on the server, if the address of the server is within the first address segment, the terminal device's session can access the service in the VPLMN.
[0168] In one example, after the SMF in the VPLMN inserts the BP, the second information may be sent by the SMF in the VPLMN to the SMF in the HPLMN, and the SMF in the HPLMN generates a routing rule based on the first information and the second information. Optionally, the SMF in the VPLMN may also send indication information to the SMF in the HPLMN to indicate that the SMF in the VPLMN has inserted the BP.
[0169] Optionally, the second information may include a source address as the source address used by the terminal device to access the service through the VPLMN. It can also be understood that the source address included in the second information is the source address used by the terminal device when routing to the service of the local data network in the VPLMN in a multi-home session, or it can be understood that the source address included in the second information is the source address used by the terminal device when routing to the service of the local data network in the VPLMN.
[0170] The number of source addresses may be one or more, and the number of second address segments may be one or more, which is not limited in the embodiments of the present application. The source address and the second address segment may correspond one to one. The second information may include the source address used when the terminal device routes services to the local data network in the VPLMN. The first information is used to indicate services that are allowed to be routed to the local data network in the VPLMN. Based on the first information and the second information, the first network element may generate a routing rule, which may be used by the terminal device to select a source address according to the routing rule.
[0171] In one example, the second information also includes a DNAI and / or a second address segment corresponding to the source address, the source address is the address used by the terminal device to access the service in the VPLMN, the second address segment includes the address of the service that can be accessed using the source address, and the DNAI includes the DNAI where the service that can be accessed using the source address is located.
[0172] The source address may be an IPV6 prefix newly allocated by the UPF, and the UPF may be an anchor UPF (PSA), a local anchor UPF (local packet data unit session anchor (L-PSA)), or a local anchor UPF in a VPLMN (ie, L-PSA in a VPLMN).
[0173] The source address can be used by the terminal device to use this address as the source address in the IPv6 multi-homed PDU session to route to the local data network to access the service through the VPLMN. In the IPv6 multi-homed PDU session, the terminal device selects the source address it uses according to the routing rules. The DNAI and / or second address (e.g., IP) segment corresponding to the source address can be a DNAI / IP segment supported by the L-PSA, that is, through this L-PSA (L-PSA that allocates the source address), it can be routed to the edge server (EAS) in these DNAI / IP segments to access the service. More specifically, the DNAI and / or second IP segment corresponding to the source address can be obtained by the V-SMF from the L-PSA.
[0174] DNAI can be one or more, which is not limited in the embodiments of the present application. The second address segment can be a continuous address or a discontinuous address, which is not limited in the embodiments of the present application. The address in the second address segment can be an IP address, a MAC address segment, an IPv6 prefix or an IPv4 address, which is not limited in the embodiments of the present application. Each address included in the second address segment can use the source address to access the service in the VPLMN. The source address can also be called a new address (new IPv6 prefix / newly assigned IPv6 prefix), which is not limited in the embodiments of the present application. There is a mapping relationship between DNAI and the second address segment. If the second information includes the DNAI corresponding to the first address, the first network element can determine the second address segment based on the DNAI. One way is that when the first network element is the session management network element of the VPLMN, the first network element determines the second address segment corresponding to the DNAI based on the DNAI and the EAS deployment information of the VPLMN. If the second information includes the second address segment, the terminal device can use the source address to access the second address segment. One way is that when the first network element is the session management network element of the HPLMN, the session management network element of the VPLMN determines the second address segment corresponding to the DNAI based on the DNAI and the EAS deployment information of the VPLMN, or the session management network element of the VPLMN obtains the second address segment from the L-PSA of the VPLMN, and the session management network element of the VPLMN sends the second information to the first network element, and the second information includes the second address segment. If the second information includes the DNAI and the second address segment corresponding to the source address, that is, the second information includes the mapping relationship between the DNAI and the second address segment. The DNAI or second IP segment where the service that can be accessed by the source address involved in the embodiment of the present application is located can be: the DNAI / IP segment includes the DNAI or IP segment supported by the anchor point UPF that allocates the source address.
[0175] Optionally, if the first information includes the first address segment or the third address segment, and the second information includes the second address segment, the first network element generating a routing rule based on the first information and the second information may include: the first network element using the intersection of the first address segment and the second address segment or the intersection of the third address segment and the second address segment as the target address segment; and generating a routing rule based on the source address and the target address segment, the routing rule being used to indicate that the source address is used when the terminal device accesses a server in the target address segment. When there are multiple source addresses and second address segments, the target address segment of each source address is the intersection of its corresponding second address segment and the first address segment or the third address segment.
[0176] When a terminal device accesses a service (it has obtained the address of the server corresponding to the service (through local configuration or DNS query)), the terminal device compares the address of the server with the address segment in the routing rule. If the address of the server is within the target address segment, the terminal device can access the service (the server) using the source address (which can be routed to the local data network via the VPLMN). Otherwise (if the address of the server is not within the target address segment), the terminal device uses the source address assigned by the HPLMN when the session is established to access the server.
[0177] If the first information includes FQDN and the second information includes DNAI, the first network element first determines the third address segment corresponding to the FQDN based on the FQDN in the first information, and determines the second address segment based on the DNAI in the second information, and then uses the intersection of the third address segment and the second address segment as the target address segment, and generates routing rules based on the source address and target address segments.
[0178] It is understandable that if the first information includes an FQDN and the second information includes a second address segment, the first network element first determines the third address segment corresponding to the FQDN based on the FQDN in the first information, then uses the intersection of the third address segment and the second address segment as the target address segment, and generates routing rules based on the source address and target address segments. If the first information includes a first address segment and the second information includes a DNAI, the first network element first determines the second address segment based on the DNAI in the second information, then uses the intersection of the first address segment and the second address segment as the target address segment, and generates routing rules based on the source address and target address segments.
[0179] The first network element generating a routing rule based on the first information and the second information may also include the first network element considering the first information and the second information according to internal logic and generating the routing rule. The target address segment of this routing rule is not necessarily the intersection of the first address segment and the second address segment or the intersection of the third address segment and the second address segment, but the routing rule is characterized in that the target address segment must be within the range of the first address segment or the third address segment, or in other words, when a terminal device uses the source address included in the second information to access a service according to this routing rule, the destination address must be within the range of the first address segment or the third address segment.
[0180] S302. The first network element sends a routing rule to the terminal device. Correspondingly, the terminal device receives the routing rule. The routing rule can be used to select a source address according to the routing rule.
[0181] The first network element can send routing rules to the terminal device to facilitate, for example, selecting a source address in a multi-homing session. The terminal device can select a source address based on the routing rules when accessing a service. The first network element can be sent directly to the terminal device, or it can be sent to the terminal device through one or more network elements, which is not limited in this embodiment of the present application. The message carrying the routing rules can be an RA message, which is transmitted on the user plane. It can also be control plane signaling, which is transmitted on the control plane. It is also possible to use control plane signaling in one section of the transmission process and use user plane messages in another section, which is not limited in this embodiment of the present application.
[0182] Routing rules can be used by terminal devices to select source addresses based on the routing rules. In other words, when a terminal device accesses a service, the source address used by the terminal device to access the service is determined based on the routing rules. The source address can be an IP address or a MAC address. If the source address is an IP address, the IP address can be an IPv6 prefix. The source address in the embodiments of the present application is used to provide the source of the route for the traffic, and its specific form is not limited.
[0183] In the HR-SBO roaming scenario, the first network element may execute S301 and S302 throughout the entire lifecycle of the HR-SBO session.
[0184] S303: When there is a multi-homed session, the terminal device sends information for accessing the service based on the routing rule. The information for accessing the service includes a source address selected according to the routing rule.
[0185] When a terminal device uses a source address, it can select an appropriate source address based on routing rules and send information for accessing services based on the source address. In a multi-homed session scenario, routing rules are used: When a terminal device has an IPv6 multi-homed PDU session, the terminal device selects a source IPv6 prefix based on routing rules. This routing rule can be sent to the terminal device by the network (e.g., the 5G core network). In another example, routing rules can also be configured locally on the terminal device.
[0186] When accessing a service, a terminal device can select a source address based on routing rules and send service access information to the service provider based on the source address. The source address can be an IP address or a MAC address, which is not limited in this embodiment of the present application. The source address is used to route services to the VPLMN local data network. The service can be an IP address or an EQDN. The service provider can divert the service to the VPLMN or HPLMN based on the source address in the service access information.
[0187] For example, in the example shown in Figure 2 above, the terminal device can select the source IP address based on the routing rules, and establish a multi-homed PDU session based on the source IP address, and send the multi-homed PDU session to the BP through the AN. The BP can divert the service to the VPLMN or HPLMN based on the source address in the multi-homed PDU session.
[0188] Optionally, the source address is used to access services authorized by the HPLMN in the VPLMN. If the terminal device is within the coverage of the VPLMN and the service accessed by the terminal device is accessible in the VPLMN with the HPLMN authorization, the BP receives the information sent by the terminal device regarding the accessed service determined based on the routing rule and can divert the corresponding service to the VPLMN.
[0189] Optionally, before executing S303 above, the terminal device may also receive a destination address from a DNS resolver or the EASDF or UPF of the VPLMN. The terminal device may determine the source address based on the destination address and the routing rules. The destination address is the address of the server accessed by the terminal device. If the routing rules include an address that is the same as the destination address, the terminal device may use its corresponding source address to access the service. The destination address in the embodiments of the present application is used to provide a routing destination for traffic, and its specific form is not limited.
[0190] For example, the terminal device may request the destination address from the EASDF of the VPLMN on the user plane, and the terminal device may receive the destination address from the EASDF of the VPLMN on the user plane via the L-SPA and the UPF (BP) of the VPLMN. It should be noted that the UPF of the VPLMN may be a BP or a UPF used by the VPLMN for other functions, and this embodiment of the present application is not limited thereto.
[0191] This implementation method determines the source address based on the destination address and routing rules, which helps to improve the accuracy of determining the source address and thus access services through the appropriate PLMN.
[0192] Optionally, the information sent by the terminal device for accessing the service may further include a destination address, and the destination address is within the HPLMN authorized range.
[0193] This implementation method is conducive to subsequent BP to divert services based on source addresses, thereby improving the accuracy of service diversion.
[0194] In the communication method provided by an embodiment of the present application, the first information is used to indicate the services that are allowed to be routed to the local data network in the VPLMN, and the second information includes the source address used by the terminal device. The routing rules generated based on the first information and the second information can guide the terminal device to select a suitable source address to access the service in the VPLMN, which is conducive to controlling the local diversion service.
[0195] As an optional embodiment, the above method 300 further includes: during the process of establishing or modifying the HR-SBO session, the second network element sends second information to the first network element, and correspondingly, the first network element can receive the second information.
[0196] If the first network element has pre-set first information or can generate the first information based on local information, during the HR-SBO session establishment or modification process, the first network element receives second information from the second network element and can generate routing rules based on the first and second information. In this implementation, the first network element only needs to receive the second information to generate routing rules, as it already has the first information, which helps save signaling interaction.
[0197] If the first network element does not have the first information preset, during the HR-SBO session establishment or modification process, the first network element receives the second information from the second network element and may also receive the first information from other network elements. The other network element is a network element other than the first network element, and may or may not be the second network element, which is not limited in this embodiment of the present application. In this implementation, the first network element does not need to preset or generate the first and second information, which helps save the storage capacity or computing power of the first network element.
[0198] Optionally, the second network element obtains the second information from the L-PSA, wherein the second network element and the L-PSA are in the same PLMN. In other words, the second information sent by the second network element to the first network element may not be generated or preset by the second network element, but may be sent by the L-PSA in the same PLMN as the second network element.
[0199] The L-PSA sends the second information to the second network element. In other words, the L-PSA allocates the second information and transmits it through the second network element, which is beneficial for the terminal device to access the PLMN based on the second information.
[0200] Optionally, the second network element may also send information about the server affecting VPLMN routing while sending the second information to the first network element, which is beneficial for subsequent terminal devices to smoothly access the server and access services in the VPLMN.
[0201] Optionally, the first network element may be a session management function network element in the HPLMN, and the second network element may be a session management function network element in the VPLMN. The session management function network element is used to represent a network element having a session management function, such as an SMF. The session management function network element in the HPLMN and the session management function network element in the VPLMN provide services for the same session.
[0202] If the session management function network element is an SMF, the first network element may be the SMF in the HPLMN, and the second network element may be the SMF in the VPLMN. During the HR-SBO session establishment or modification process, the SMF in the HPLMN may receive the second information from the SMF in the VPLMN. For ease of description, the SMF in the HPLMN is referred to as the H-SMF, and the SMF in the VPLMN is referred to as the V-SMF.
[0203] For example, FIG4 shows a schematic flow chart of a method 400 for processing routing rules. The method 700 is applied to the HR-SBO scenario. As shown in FIG4 , the method 400 may include the following steps:
[0204] S401. During the HR-SBO session modification process, the V-SMF sends second information to the H-SMF, and correspondingly, the H-SMF receives the second information.
[0205] The session modification process may refer to a network element or terminal device such as V-SMF or H-SMF triggering a session modification process, and executing this step in the session modification process. It may also refer to V-SMF calling H-SMF for a session-related service interface and sending information through this interface. The embodiment of the present application is not limited to this.
[0206] The second information may include the source address, and may also include the DNAI and / or the second address segment corresponding to the source address. For the V-SMF, the second information may be obtained from the L-PSA in the same PLMN as the V-SMF.
[0207] S402: The H-SMF generates a routing rule based on the second information and the first information.
[0208] The H-SMF may be preset with the first information, may generate the first information, or may receive the first information from the PCF in the HPLMN, which is not limited in this embodiment of the present application.
[0209] S403. The H-SMF sends the routing rules to the terminal device.
[0210] For example, in the scenario shown in FIG2 above, the H-SMF may send routing rules to the terminal device through the UPF in the HPLMN, the BP in the VPLMN, and the AN, or the H-SMF may send routing rules to the terminal device through the SMF in the VPLMN, the BP in the VPLMN, and the AN.
[0211] This method of processing routing rules is that during the HR-SBO session establishment process, the H-SMF receives the second information sent by the V-SMF, and generates routing rules based on the first information and the second information, which is conducive to including the first information in the information for generating the routing rules, that is, taking into account the services authorized by the HPLMN in the VPLMN, making it easier for subsequent terminal devices to access the services authorized by the HPLMN in the VPLMN, thereby realizing the control of the HPLMN over the services.
[0212] In the above method 400, one possible approach is that before the H-SMF generates the routing rule, the H-SMF may receive a trigger condition for generating the routing rule, such as a policy and charging control (PCC) rule. In other words, after the H-SMF obtains the first information and the second information, it receives the trigger condition for generating the routing rule and then generates the routing rule based on the first information and the second information.
[0213] For example, FIG5 shows a schematic flow chart of a method 500 for processing routing rules. As shown in FIG5 , the method 500 may include the following steps:
[0214] S501. During the HR-SBO session modification process, the V-SMF sends second information to the H-SMF, and correspondingly, the H-SMF receives the second information.
[0215] This step is the same as the above-mentioned S401 and will not be repeated here.
[0216] S502: The H-SMF sends second information to the PCF in the HPLMN (hereinafter referred to as H-PCF). Correspondingly, the H-PCF receives the second information.
[0217] S503, H-PCF sends PCC rules and second information to H-SMF, and correspondingly, H-SMF receives PCC rules and second information, wherein PCC rules can be generated based on the second information, that is, part or all of the content of the second information can be included in the PCC rules; or PCC rules can be unrelated to the second information, that is, PCC rules are used for other functions, but have the function of triggering S505. The correlation between PCC rules and second information is not limited in the embodiment of the present application. Regardless of whether the second information and PCC rules are related, both can be sent to H-SMF as the same (the second information is included in the PCC rules) or different messages, and can be sent simultaneously or at different times when sent as different messages. This is not limited in the embodiment of the present application.
[0218] Optionally, the H-PCF may further send the first information to the H-SMF. The first information, the second information, and the PCC rule may be sent simultaneously or at different times. This is not limited in the embodiment of the present application.
[0219] The H-SMF can execute S504 only after receiving the PCC rule.
[0220] S504: The H-SMF generates a routing rule based on the second information and the first information.
[0221] The H-SMF may be preset with the first information, may generate the first information, or may receive the first information from the H-PCF, which is not limited in this embodiment of the present application.
[0222] S505. The H-SMF sends the routing rules to the terminal device.
[0223] S505 is the same as the above S403 and will not be described again here.
[0224] In this implementation, H-SMF generates routing rules only after receiving the PPC rule, i.e., the triggering condition for generating routing rules, which is beneficial for controlling the timing of generating routing rules.
[0225] The above method 400 and method 500 both introduce methods for generating routing rules within the life cycle of a session.
[0226] As an optional embodiment, if the H-SMF receives the second information from the V-SMF during the HR-SBO session establishment process, the H-SMF can generate a routing rule for domain name system (DNS) query based on the second information, and generate a routing rule based on the first information and the second information during the session modification process.
[0227] The routing rules for DNS queries are used to indicate that the source address used to access services can be determined through the domain name system.
[0228] In this implementation, during the session establishment process, routing rules for DNS queries are first generated based on the received second information. When there is subsequent business access, routing rules are generated based on the first information and the second information, which is conducive to the rational use of computing resources.
[0229] As an optional embodiment, the above method 300 may further include: during the process of establishing or modifying the HR-SBO session, the third network element sends the first information to the first network element, and correspondingly, the first network element may receive the first information.
[0230] If the first network element has the second information pre-set or can generate the second information based on local information, during the HR-SBO session establishment or modification process, the first network element receives the first information from the third network element and can generate routing rules based on the first and second information. In this implementation, the first network element only needs to receive the first information to generate routing rules, as it includes the second information, which helps save signaling interaction.
[0231] If the first network element does not have the second information preset, during the HR-SBO session establishment or modification process, the first network element receives the first information from the third network element and may also receive the second information from other network elements. The other network element refers to a network element other than the first network element, which may or may not be a third network element, and this embodiment of the present application is not limited to this. In this implementation, the first network element does not need to preset or generate the first and second information, which helps save the first network element's storage capacity or computing power for generating information.
[0232] It should be noted that the embodiment of the present application is not limited to the case where the first network element receives the first information from the third network element only during the process of establishing or modifying the HR-SBO session. The method can also be applied in other roaming scenarios.
[0233] Optionally, the first network element may be a session management function network element in the HPLMN, and the third network element may be a policy control function network element in the HPLMN. The session management function network element is used to represent a network element with a session management function, such as an SMF. The policy control function network element is used to represent a network element with a policy control function, such as a PCF.
[0234] If the first network element is the SMF in the HPLMN, and the third network element is the PCF in the HPLMN, namely H-PCF, during the establishment or modification of the HR-SBO session, the third network element can send the first information to the first network element, and the second network element can send the second message to the first network element, and the first network element can generate routing rules based on the first information and the second information.
[0235] For example, FIG6 shows a schematic flow chart of a method 600 for processing routing rules. As shown in FIG6 , the method 600 may include the following steps:
[0236] S601. During the HR-SBO session modification process, the V-SMF sends second information to the H-SMF, and correspondingly, the H-SMF receives the second information.
[0237] This step is the same as the above-mentioned S401 and will not be repeated here.
[0238] S602. The H-PCF sends first information to the H-SMF. Correspondingly, the H-SMF receives the first information.
[0239] The first information may be locally preset by the H-PCF, for example, determined based on factors such as the service level agreement between operators and the user's contract information, or generated by it, which is not limited in this embodiment of the present application.
[0240] S603: The H-SMF generates a routing rule based on the second information and the first information.
[0241] S604. The H-SMF sends the routing rules to the terminal device.
[0242] S603 is the same as the above S301, and S604 is the same as the above S302, which will not be repeated here.
[0243] In this implementation mode, the H-SMF can obtain the second information from the V-SMF and the first information from the H-PCF, without the need to preset or generate the first information and the second information, which is beneficial to saving the storage space of the H-SMF or the ability to generate information.
[0244] Optionally, in the above method 600, before the H-SMF executes S603, it may receive a trigger condition for generating routing rules from the H-PCF, such as a PCC rule. The trigger condition for generating routing rules may be carried in the same message as the first message, or may be carried in a different message from the first message, which is not limited in this embodiment of the present application.
[0245] In a possible implementation, the triggering condition for generating the routing rule and the first information are carried in the same piece of information. In other words, the first information in S602 can also be used to trigger the H-SMF to generate the routing rule.
[0246] In this implementation, the triggering condition for generating the routing rule and the first information are carried in the same piece of information, which can reduce the sending of one piece of information and save information interaction.
[0247] In another possible implementation, the triggering condition for generating the routing rule and the first information are carried in different information. In other words, before the above S603, the H-SMF may also receive the triggering condition for generating the routing rule from the H-PCF.
[0248] This implementation method is helpful in controlling the timing of generating routing rules.
[0249] Optionally, the third network element sends first information to the first network element, where the first information may include a third address segment corresponding to the FQDN. The first network element may be a session management function network element in the HPLMN, and the third network element may be a session management function network element in the VPLMN. For example, the session management function network element in the HPLMN may send the FQDN to the session management function network element in the VPLMN, and the session management function network element in the VPLMN may send the third address segment corresponding to the FQDN to the session management function network element in the HPLMN. The FQDN includes services allowed to be routed to the local data network in the VPLMN.
[0250] The session management function network element in the VPLMN can determine the third address segment corresponding to the FQDN based on the FQDN. The third address segment corresponding to the FQDN means that the session management function network element in the VPLMN obtains the address segment corresponding to the FQDN based on the EAS deployment information of the VPLMN. The third address segment has the same function as the first address segment mentioned above. The FQDN in the EAS deployment information refers to the supported FQDN of the application deployed in the local part of the DN. The address segment in the EAS deployment information refers to the IP address / address segment of one or more EAS in the local data network. The third address segment can be understood as the address segment of the service allowed to be routed to the local data network in the VPLMN.
[0251] The FQDN corresponds to the third address segment, which can also be understood as the third address segment being generated based on the FQDN, or the third address segment being obtained based on the FQDN, or the session management function network element in the VPLMN obtaining the third address segment based on the FQDN. This embodiment of the present application does not limit this.
[0252] For example, the session management function network element in the HPLMN may be an H-SMF, and the session management function network element in the VPLMN may be a V-SMF. FIG7 shows a schematic flow chart of a method 700 for processing routing rules. As shown in FIG7 , the method 700 may include the following steps:
[0253] S701. The PCF in the HPLMN (hereinafter referred to as H-PCF) sends an FQDN to the H-SMF. Correspondingly, the H-SMF receives the FQDN.
[0254] The FQDN includes services that are allowed to be routed to the local data network in the VPLMN, and the services may be domain names.
[0255] S702. H-SMF sends FQDN to V-SMF, and correspondingly, V-SMF receives FQDN.
[0256] S703. The V-SMF determines the third address segment corresponding to the FQDN based on the FQDN.
[0257] S704. The V-SMF sends first information to the H-SMF, where the first information is the third address segment.
[0258] S705. The H-SMF generates a routing rule based on the first information and the second information.
[0259] The H-SMF may be preset with the second information, or may generate the second information based on local information, or may receive the second information from other network elements (eg, V-SMF, H-PCF), which is not limited in this embodiment of the present application.
[0260] S706. The H-SMF sends the routing rules to the terminal device.
[0261] In this implementation method, V-SMF determines the third address segment corresponding to the FQDN based on the FQDN and sends the third address segment to the H-SMF. The H-SMF does not need to generate the third address segment, which is beneficial to saving the H-SMF's ability to generate the third address segment.
[0262] As an optional embodiment, the above-mentioned first network element is a session management function network element in the VPLMN. When the first information includes the FQDN, a routing rule is generated based on the first information and the second information, including: generating a routing rule based on the third address segment corresponding to the FQDN and the second information, and the FQDN includes services allowed to be routed to the local data network in the VPLMN.
[0263] The first network element is a session management function network element in the VPLMN, which may be a V-SMF. The V-SMF may generate a routing rule based on the third address segment corresponding to the FQDN and the second information.
[0264] For example, the V-SMF may determine a third address segment corresponding to the FQDN based on the FQDN, and generate a routing rule based on the third address segment and the second information. The FQDN may be obtained by the V-SMF from another network element. The V-SMF may obtain the third address segment corresponding to the FQDN based on edge server (EAS) deployment information.
[0265] In this implementation method, V-SMF determines the third address segment corresponding to the FQDN based on the FQDN, and uses the third address segment to generate routing rules, which has high initiative.
[0266] In the above-mentioned method, the first network element uses the intersection of the first address segment and the second address segment as the target address segment; generates a routing rule based on the source address and the target address segment, wherein the routing rule is used to indicate that when a terminal device accesses a server in the target address segment, it uses the first address to access services in the VPLMN. This is only one possible implementation. In another possible implementation, the first network element may receive the target address segment and source address from another network element and generate a routing rule based on the source address and the target address segment.
[0267] For example, the first network element may be an H-SMF, and the other network elements may be V-SMFs. FIG8 shows a schematic flow chart of a method 800 for processing routing rules. The method 800 is applied to the HR-SBO scenario. As shown in FIG8 , the method 800 may include the following steps:
[0268] S801. During the HR-SBO session establishment process, the H-SMF sends the first information to the V-SMF, and correspondingly, the V-SMF receives the first information.
[0269] The H-SMF stores the first information, which may be preset, locally generated, or received from other network elements, which is not limited in this embodiment of the present application. The H-SMF may transmit the first information to the V-SMF.
[0270] S802. The V-SMF determines a target address segment based on the first information and the second information.
[0271] The V-SMF stores second information, which can be preset, locally generated, or received from other network elements. This embodiment of the present application does not limit this. The V-SMF can determine the target address segment based on the first information and the second information. Alternatively, the V-SMF can determine the DNAI based on the first information and the second information, and then determine the target address segment based on the DNAI.
[0272] S803. During the HR-SBO session modification process, the V-SMF sends the source address and target address segments to the H-SMF. Correspondingly, the H-SMF receives the source address and target address segments.
[0273] The second information includes the source address. During the HR-SBO session modification process, the V-SMF can transmit the source address and target address segments to the H-SMF.
[0274] S804. H-SMF generates routing rules based on the source address and destination address segments.
[0275] A routing rule is generated based on the source address and the target address segment. The routing rule is used to indicate that when a terminal device accesses a server in the target address segment, it uses the source address to access services in the VPLMN.
[0276] S805. The H-SMF sends the routing rules to the terminal device.
[0277] This step is the same as the above-mentioned S403 and will not be repeated here.
[0278] In this implementation, the H-SMF does not need to determine the target address segment based on the first information and the second information, which helps to reduce computing power.
[0279] Optionally, in the above method 800, before the H-SMF executes S804, the H-PCF may send a trigger condition for generating routing rules, such as a PCC rule, to the H-SMF. After receiving the trigger condition for generating routing rules, the H-SMF executes S804.
[0280] For example, FIG9 shows a schematic flow chart of a method 900 for processing routing rules. The method 900 is applied to the HR-SBO scenario. As shown in FIG9 , the method 900 may include the following steps:
[0281] S901. During the HR-SBO session establishment process, the H-SMF sends the first information to the V-SMF, and correspondingly, the V-SMF receives the first information.
[0282] S902. The V-SMF determines a target address segment based on the first information and the second information.
[0283] S903. During the HR-SBO session modification process, the V-SMF sends the source address and target address segments to the H-SMF. Correspondingly, the H-SMF receives the source address and target address segments.
[0284] S901 to S903 are respectively the same as S801 to S803 in the above method 800 and are not described again here.
[0285] S904. The H-SMF sends the source address to the H-PCF. Correspondingly, the H-PCF receives the source address.
[0286] Optionally, the source address may also be sent to the H-PCF by a network element other than the H-SMF, which is not limited in the embodiment of the present application.
[0287] Optionally, the H-SMF may also send a target address segment to the H-PCF.
[0288] S905 . The H-PCF sends the PCC rule and source address to the H-SMF. Correspondingly, the H-SMF receives the PCC rule and source address.
[0289] The PCC rule can be generated based on the source address, that is, the source address can be included in the PCC rule; or the PCC rule can be unrelated to the source address, that is, the PCC rule is used for other functions, but has the effect of triggering S906. The correlation between the PCC rule and the source address is not limited in the embodiment of the present application. Regardless of whether the source address and the PCC rule are related, both can be sent to the H-SMF as the same (the source address is included in the PCC rule) or different messages, and can be sent simultaneously or at different times when sent as different messages. This is not limited in the embodiment of the present application.
[0290] The H-SMF can execute S906 only after receiving the PCC rule.
[0291] S906. The H-SMF generates routing rules based on the source address and destination address segments.
[0292] S907. The H-SMF sends the routing rules to the terminal device.
[0293] This step is the same as the above-mentioned S403 and will not be repeated here.
[0294] In this implementation, the H-SMF generates routing rules only after receiving the PCC rules, which helps the HPLMN control the timing of generating routing rules.
[0295] As an optional embodiment, the first network element in the above method 300 may be a session management function network element in a VPLMN, such as an SMF. For the convenience of description, the SMF in the VPLMN may be referred to as V-SMF in the following.
[0296] The V-SMF may generate routing rules based on the first information and the second information. The second information may be obtained by the V-SMF from the L-PSA, where the L-PSA and the V-SMF are in the same PLMN. The first information may be sent to the V-SMF by a session management function network element in the HPLMN. The first information may be preset or generated by a session management function network element in the HPLMN, or may be sent by another network element, and this is not limited in this embodiment of the present application.
[0297] For example, the session management function network element in the HPLMN may be an SMF in the HPLMN, i.e., an H-SMF. The first information may be sent by a policy control function network element in the HPLMN to the H-SMF, wherein the policy control function network element in the HPLMN may be a PCF in the HPLMN, i.e., an H-PCF. FIG10 shows a schematic flow chart of a method 1000 for processing routing rules. As shown in FIG10 , the method 1000 may include the following steps:
[0298] S1001. The H-PCF sends first information to the H-SMF. Correspondingly, the H-SMF receives the first information.
[0299] S1002. H-SMF sends first information to V-SMF. Correspondingly, V-SMF receives the first information.
[0300] S1003. The V-SMF generates a routing rule based on the first information and the second information obtained from the L-PSA.
[0301] S1004. V-SMF sends routing rules to the terminal device.
[0302] The V-SMF may send routing rules to the terminal device through L-PSA, UPF (BP), and AN, or through H-SMF, UPF of HPLMN, UPF (BP) of VPLMN, and AN. In the process of V-SMF sending H-SMF, the message carrying the routing rules is the signaling of the control plane. In the rest of the process, the message carrying the routing rules is the RA message, which is transmitted on the user plane.
[0303] In this implementation, the V-SMF does not need to send the first information to the H-SMF, and can directly generate routing rules based on the obtained first information and second information, which is conducive to reducing information interaction.
[0304] If the first information is sent by the policy control function element in the HPLMN to the session management function element in the HPLMN, the policy control function element in the HPLMN may also send a routing rule triggering condition to the session management function element in the HPLMN. After receiving the routing rule triggering condition, the session management function element in the HPLMN may first generate a portion of the routing rule based on the first information, then send the portion of the routing rule to the session management function element in the VPLMN, and finally the session management function element in the VPLMN generates the routing rule.
[0305] For example, the session management function network element in the HPLMN may be an H-SMF, the policy control function network element in the HPLMN may be an H-PCF, and the triggering condition for generating routing rules may be a PCC rule. FIG11 shows a schematic flow chart of a method 1100 for processing routing rules. As shown in FIG11 , the method 1100 may include the following steps:
[0306] S1101. The H-PCF generates PCC rules.
[0307] The embodiments of the present application do not limit the specific implementation method of the H-PCF generating PCC rules. The H-PCF can generate PCC rules based on the first information, or can generate routing rules based on information other than the first information, and the embodiments of the present application do not limit this. The PCC rules may include the first information or may not include the first information, and the embodiments of the present application do not limit this. If the PCC rules include the first information, in S1102, the H-PCF can send the PCC rules to the H-SMF. If the PCC rules do not include the first information, the H-PCF can send the first information and the PCC rules to the H-SMF.
[0308] S1102. The H-PCF sends first information and PCC rules to the H-SMF. Correspondingly, the H-SMF receives the first information and PCC rules.
[0309] When the PCC rule does not include the first information, the H-PCF may send the first information and the PCC rule to the H-SMF.
[0310] S1103. The H-SMF generates some routing rules based on the first information.
[0311] The H-SMF receives the PCC rule and may first generate a partial routing rule based on the first information, where the first information includes the FQDN or the first address segment. The partial routing rule is used to indicate that access to the server in the first address segment can be accessed in the VPLMN.
[0312] S1104. H-SMF sends some routing rules to V-SMF.
[0313] S1105. The V-SMF generates routing rules based on the second information and part of the routing rules.
[0314] The V-SMF may update part of the routing rules based on the second information and generate routing rules, which are used by the terminal device to select a source address according to the routing rules.
[0315] S1106. V-SMF sends routing rules to the terminal device.
[0316] In this implementation mode, H-SMF first generates some routing rules based on the trigger conditions, and V-SMF can generate routing rules by updating some routing rules based on the second information, which is beneficial to reducing some computing power.
[0317] In the above-mentioned method, the first network element may send the routing rules directly to the terminal device. In another possible implementation, the first network element may forward the routing rules to the terminal device through an intermediate network element.
[0318] In a first implementation, when the first network element is a session management function network element in the HPLMN, the first network element sends the routing rules to the UPF or PSA in the HPLMN. The UPF or PSA then sends the routing rules to the terminal device. In other words, the UPF or PSA in the HPLMN acts as an intermediate network element, forwarding the routing rules from the first network element to the terminal device.
[0319] The first network element can send the routing rule to the terminal device through the user plane. There may or may not be other network elements between the UPF or PSA and the terminal device, and this embodiment of the application does not limit this.
[0320] For example, in the scenario shown in Figure 2 above, the first network element can be the SMF in the HPLMN, namely H-SMF, and the H-SMF sends routing rules to the UPF in the HPLMN, namely H-UPF. The H-UPF can forward the routing rules to the UPF (BP) of the VPLMN, and the UPF (BP) can forward the routing rules to the AN, and the AN can forward the routing rules to the terminal device.
[0321] This implementation method forwards the routing rules to the terminal device through the UPF or PSA in the HPLMN, which is conducive to maintaining the control capability of the session management function network element in the HPLMN over the terminal device.
[0322] In the second implementation method, when the first network element is a session management function network element in a VPLMN or a policy control function network element in a HPLMN, the first network element sends routing rules to the session management function network element in the HPLMN, and the session management function network element is used to send the routing rules to the terminal device.
[0323] There may or may not be other network elements between the session management function network element in the HPLMN and the terminal device, and this embodiment of the present application does not limit this.
[0324] For example, in the scenario shown in Figure 2 above, the first network element can be the SMF in the VPLMN or the PCF in the HPLMN, namely the H-UPF. The SMF or H-UPF in the VPLMN can send routing rules to the SMF in the HPLMN, namely the H-SMF. The H-SMF can forward the routing rules to the H-UPF. The H-UPF can forward the routing rules to the BP. The BP can forward the routing rules to the AN. The AN can forward the routing rules to the terminal device.
[0325] In this implementation, the session management function network element in the VPLMN or the policy control function network element in the HPLMN forwards the routing rules to the terminal device through the session management function network element in the HPLMN, which is conducive to maintaining the control capability of the session management function network element in the HPLMN over the terminal device.
[0326] In a third implementation method, when the first network element is a session management function network element in a VPLMN, the first network element may send routing rules to a local protocol data unit session anchor L-PSA in the VPLMN, and the L-PSA is used to send the routing rules to the terminal device.
[0327] There may or may not be other network elements between the L-PSA and the terminal device, and this embodiment of the present application does not limit this.
[0328] For example, in the scenario shown in Figure 2 above, the first network element can be the SMF in the VPLMN, the SMF in the VPLMN can send routing rules to the L-PSA, the L-PSA can forward the routing rules to the BP, the BP can forward the routing rules to the AN, and the AN can forward the routing rules to the terminal device.
[0329] In this implementation, the session management function network element in the VPLMN forwards the routing rules to the terminal device through the network element in the VPLMN. Compared with sending the routing rules to the network element in the HPLMN and forwarding them to the terminal device by the network element in the HPLMN, it is beneficial to shorten the transmission path.
[0330] The above-mentioned routing rules include the source address in the first information, which is the address used by the session of the terminal device to access the service in the VPLMN. If the source address used by the session of the terminal device received by BP is the source address in the first information, BP can divert the service in the session to the VPLMN. If the source address of the session of the terminal device received by BP does not use the source address in the first information, BP can divert the service in the session to the HPLMN. The embodiment of the present application also provides a method. If the source address used by the session of the terminal device received by BP is the first address (i.e., the source address in the first information), BP can divert the service in the session to the VPLMN. If the source address used by the session of the terminal device received by BP is the second address (the source address in other information), BP can divert the service in the session to the HPLMN. In this case, the information used to generate the routing rules can also include the second address used to access the service in the HPLMN.
[0331] In the above method 300, S301 generates routing rules used by the terminal device to access the service based on the first information and the second information, including: generating routing rules based on the first information, the second information, the third information and the fourth information, the third information is used to indicate the service allowed to be routed to the data network in the HPLMN, the fourth information is used to indicate the source address used by the terminal device (which can be called the second address), and the fourth information is different from the above second information.
[0332] The terminal device generates a routing rule based on the first information, the second information, the third information and the fourth information, wherein the routing rule is used to indicate that the address used by the session of the terminal device to access the service in the VPLMN is the first address and the address used to access the service in the HPLMN is the second address.
[0333] This implementation method clarifies the address used to access services in the HPLMN.
[0334] The order of execution of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiment of the present application.
[0335] The method of the embodiment of the present application is described in detail above with reference to Figures 1 to 11 , and the device of the embodiment of the present application will be described in detail below with reference to Figures 12 and 13 .
[0336] FIG12 shows a schematic block diagram of a communication device 1200 according to an embodiment of the present application. As shown in FIG12 , the communication device 1200 may include: a processing unit 1210 and a transceiver unit 1220 .
[0337] In a possible implementation, the communication device 1200 may execute the steps performed by the first network element in the above method 300.
[0338] Among them, the processing unit 1210 is used to: generate routing rules based on the first information and the second information, the first information is used to indicate the services allowed to be routed to the local data network in the visited public land mobile network VPLMN, the second information includes the source address used by the terminal device, and the routing rules are used by the terminal device to select the source address according to the routing rules; the transceiver unit 1220 is used to: send the routing rules.
[0339] In another possible implementation, the communication device 1200 may execute the steps executed by the terminal device in the above method 300.
[0340] Among them, the transceiver unit 1220 is used to: receive the routing rules used when selecting the source address; when there are multiple home sessions, determine the information used to access the service through the processing unit 1210, and send the information used to access the service, and the information used to access the service includes the source address selected according to the routing rules.
[0341] It should be understood that the communication device 1200 here is embodied in the form of a functional unit. The term "unit" here may refer to an application specific integrated circuit (ASIC), an electronic circuit, a processor (such as a shared processor, a dedicated processor or a group processor, etc.) and a memory for executing one or more software or firmware programs, a merged logic circuit and / or other suitable components that support the described functions. In an optional example, those skilled in the art will understand that the communication device 1200 may be specifically the first network element or terminal device in the above-mentioned embodiment, and the communication device 1200 may be used to execute the various processes and / or steps corresponding to the first network element or terminal device in the above-mentioned method embodiment. To avoid repetition, they will not be described here.
[0342] The communication device 1200 of each of the above solutions has the function of implementing the corresponding steps performed by the first network element or terminal device in the above method; the above functions can be implemented by hardware, or by hardware executing corresponding software. The hardware or software includes one or more modules corresponding to the above functions.
[0343] In an embodiment of the present application, the communication device 1200 in FIG12 may also be a chip or a chip system, such as a system on chip (SoC).
[0344] Figure 13 shows a schematic block diagram of another communication device 1300 provided in an embodiment of the present application. As shown in Figure 13, the communication device 1300 includes a processor 1310, a communication interface 1320, and a memory 1330. The processor 1310, the communication interface 1320, and the memory 1330 communicate with each other through an internal connection path. The memory 1330 is used to store instructions. The communication interface 1320 has input and output or transceiver functions and is used to communicate with other devices through a transmission medium, so that the communication device 1300 can communicate with other devices. The processor 1310 is used to execute the instructions stored in the memory 1330 to control the communication interface 1320 to send and / or receive signals.
[0345] It should be understood that the communication device 1300 can be specifically the first network element or terminal device in the above-mentioned embodiment, and can be used to execute the various steps and / or processes corresponding to the first network element or terminal device in the above-mentioned method embodiment. Optionally, the memory 1330 may include read-only memory and random access memory, and provide instructions and data to the processor. A portion of the memory may also include non-volatile random access memory. For example, the memory may also store device type information. The processor 1310 can be used to execute instructions stored in the memory, and when the processor 1310 executes the instructions stored in the memory, the processor 1310 is used to execute the various steps and / or processes of the above-mentioned method embodiment corresponding to the first network element or terminal device. The communication interface 1320 may include a transmitter and a receiver. The transmitter can be used to implement the various steps and / or processes corresponding to the communication interface 1320 for performing the sending action, and the receiver can be used to implement the various steps and / or processes corresponding to the communication interface 1320 for performing the receiving action.
[0346] It should be understood that in the embodiments of the present application, the processor of the above-mentioned device may be a central processing unit (CPU), and the processor may also 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 may be a microprocessor or any conventional processor, etc.
[0347] During implementation, each step of the above method can be completed by hardware integrated logic circuits in the processor or by instructions in the form of software. The steps of the method disclosed in conjunction with the embodiments of the present application can be directly embodied as being executed by a hardware processor, or can be executed by a combination of hardware and software units in the processor. The software unit can be located in a storage medium mature in the art, such as random access memory, flash memory, read-only memory, programmable read-only memory, or electrically erasable programmable memory, registers, etc. The storage medium is located in the memory, and the processor executes the instructions in the memory, combining with its hardware to complete the steps of the above method. To avoid repetition, it will not be described in detail here.
[0348] An embodiment of the present application also provides a communication system, which may include the first network element and terminal device in the above embodiment.
[0349] An embodiment of the present application provides a computer-readable storage medium, which is used to store a computer program, and the computer program is used to implement the method corresponding to the first network element shown in various possible implementations in the above embodiments.
[0350] An embodiment of the present application provides another computer-readable storage medium, which is used to store a computer program, and the computer program is used to implement the method corresponding to the terminal device shown in various possible implementation methods in the above embodiments.
[0351] An embodiment of the present application provides a computer program product, which includes a computer program (also referred to as code or instructions). When the computer program runs on a computer, the computer can execute the method corresponding to the first network element shown in the above embodiment.
[0352] An embodiment of the present application provides another computer program product, which includes a computer program (also referred to as code, or instructions). When the computer program runs on a computer, the computer can execute the methods corresponding to the terminal device shown in the various possible implementations of the above embodiments.
[0353] An embodiment of the present application provides a chip system, which is used to support the above-mentioned first network element to implement the functions shown in the embodiment of the present application.
[0354] An embodiment of the present application provides another chip system, which is used to support the above-mentioned terminal device to implement the functions shown in the embodiment of the present application.
[0355] Those skilled in the art will appreciate that the units and algorithm steps of each example 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 performed in hardware or software depends on the specific application and design constraints of the technical solution. Professional and technical personnel 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.
[0356] Those skilled in the art will clearly understand that, for the convenience and brevity of description, the specific working processes of the systems, devices and units described above can refer to the corresponding processes in the aforementioned method embodiments and will not be repeated here.
[0357] In the several embodiments provided in this application, it should be understood that the disclosed systems, devices and methods can be implemented in other ways. For example, the device embodiments described above are merely schematic. For example, the division of units is only a logical function division. In actual implementation, there may be other division methods, such as multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be through some interfaces, indirect coupling or communication connection of devices or units, which can be electrical, mechanical or other forms.
[0358] Units described as separate components may or may not be physically separate, and 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 these units may be selected to achieve the purpose of this embodiment according to actual needs.
[0359] In addition, each functional unit in each embodiment of the present application may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit.
[0360] If the function is implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present application, or the part that contributes to the prior art, or the part of the technical solution, can be embodied in the form of a software product. The computer software product is stored in a storage medium and includes several instructions for enabling a computer device (which can be a personal computer, a server, or a receiving end, etc.) to execute all or part of the steps of the various embodiments of the present application. The aforementioned storage medium includes various media that can store program codes, such as a USB flash drive, a mobile hard disk, a read-only memory (ROM), a random access memory (RAM), a magnetic disk or an optical disk.
[0361] The above are only specific embodiments of the present application, but the scope of protection of this application is not limited thereto. Any changes or substitutions that can be easily conceived by a person skilled in the art within the technical scope disclosed in this application should be included in the scope of protection of this application. Therefore, the scope of protection of this application should be based on the scope of protection of the claims.
Claims
1. A communication method, It is characterized in that Applied to the first network element, including: generating a routing rule based on first information and second information, the first information being used to indicate a service that is allowed to be routed to a local data network in a visited public land mobile network VPLMN, the second information comprising a source address used by a terminal device, and the routing rule being used by the terminal device to select a source address according to the routing rule; The routing rule is sent.
2. The method according to claim 1, It is characterized in that The first information includes a fully qualified domain name FQDN or a first address segment, the FQDN includes a service allowed to be routed to a local data network in the VPLMN, and the first address segment includes an address of a server allowed to be routed to a local data network in the VPLMN.
3. The method according to claim 1 or 2, It is characterized in that The source address included in the second information is the source address used by the terminal device when routing to the service of the local data network in the VPLMN.
4. The method according to claim 3, It is characterized in that The second information also includes a data network access identifier DNAI and / or a second address segment corresponding to the source address.
5. The method according to any one of claims 1 to 4, It is characterized in that The method is applied to the home routing session group HR-SBO roaming scenario.
6. The method according to any one of claims 1 to 5, It is characterized in that The method further comprises: During the process of establishing or modifying a home routing session group HR-SBO session, the second information is received from the second network element.
7. The method according to claim 6, It is characterized in that The first network element is a session management function network element in a home public land mobile network HPLMN, and the second network element is a session management function network element in the VPLMN.
8. The method according to any one of claims 1 to 7, It is characterized in that When the first network element is a session management function network element in the HPLMN, the method further includes: The first information is received from a policy control function network element in the HPLMN.
9. The method according to claim 1, It is characterized in that The method further comprises: Sending an FQDN to a session management function network element in the VPLMN, the FQDN including services allowed to be routed to a local data network in the VPLMN; A third address segment corresponding to the FQDN is received from a session management function network element in the VPLMN, wherein the first information includes the third address segment.
10. The method according to any one of claims 1 to 6, It is characterized in that The first network element is a session management function network element in the VPLMN, and when the first information includes the FQDN, generating a routing rule based on the first information and the second information includes: A routing rule is generated based on a third address segment corresponding to the FQDN and the second information, wherein the FQDN includes services that are allowed to be routed to a local data network in the VPLMN.
11. The method according to any one of claims 1 to 10, It is characterized in that The sending of the routing rule comprises: The routing rule is sent to the terminal device.
12. The method according to any one of claims 1 to 10, It is characterized in that When the first network element is a session management function network element in the HPLMN, the sending the routing rule includes: The routing rule is sent to a user plane function UPF or a protocol data unit session anchor PSA in the HPLMN, and the UPF or the PSA is used to send the routing rule to the terminal device.
13. The method according to any one of claims 1 to 5, It is characterized in that When the first network element is a session management function network element in the VPLMN or a policy control function network element in the HPLMN, the sending routing rule includes: The routing rule is sent to a session management function network element in the HPLMN, and the session management function network element is used to send the routing rule to the terminal device.
14. The method according to any one of claims 1 to 4, It is characterized in that When the first network element is a session management function network element in the VPLMN, the sending routing rule includes: The routing rule is sent to a local protocol data unit session anchor L-PSA in the VPLMN, and the L-PSA is used to send the routing rule to a terminal device.
15. The method according to any one of claims 1 to 14, It is characterized in that The generating of routing rules based on the first information and the second information includes: The routing rule is generated based on the first information, the second information, the third information and the fourth information, the third information is used to indicate the services allowed to be routed to the data network in the HPLMN, the fourth information includes the source address used by the terminal device, and the fourth information is different from the second information.
16. A communication method, It is characterized in that Applied to terminal equipment, including: Receive the routing rules used when selecting the source address; Information for accessing the service is sent, wherein the information for accessing the service includes a source address selected according to the routing rule.
17. The method according to claim 16, It is characterized in that The source address is used as the source address of the traffic routed to the visited public land mobile network VPLMN local data network.
18. The method according to claim 16 or 17, It is characterized in that The source address is determined based on the destination address and the routing rule; The method further comprises: The destination address is received.
19. The method according to any one of claims 16 to 18, It is characterized in that The information for accessing the service also includes a destination address, and the destination address is used to route to an address of a server in a local data network in the VPLMN.
20. The method according to any one of claims 16 to 18, It is characterized in that The routing rules used when receiving and selecting a source address include: The routing rule is received from a session management function network element in a visited public land mobile network VPLMN or a session management function network element in a home public land mobile network HPLMN.
21. The method according to any one of claims 16 to 20, It is characterized in that The routing rule is generated based on first information and second information, the first information is used to indicate the services allowed to be routed to the local data network in the VPLMN, and the second information includes a source address used by the terminal device.
22. The method according to claim 21, It is characterized in that The first information includes a fully qualified domain name FQDN or a first address segment, the FQDN includes a service allowed to be routed to a local data network in the VPLMN, and the first address segment includes an address of a server allowed to be routed to a local data network in the VPLMN.
23. The method according to claim 21 or 22, It is characterized in that The source address included in the second information is the source address used by the terminal device when routing to the service of the local data network in the VPLMN.
24. The method according to claim 23, It is characterized in that The second information also includes a data network access identifier DNAI and / or a second address segment corresponding to the source address.
25. A communication device, It is characterized in that include: A processing unit and a transceiver unit, wherein the processing unit is used to perform the operation of generating routing rules in the communication method described in any one of claims 1 to 15, and the transceiver unit is used to perform the operation of receiving or sending in the communication method described in any one of claims 1 to 15.
26. A communication device, It is characterized in that include: A processing unit and a transceiver unit, wherein the processing unit is used to perform the operation of determining the source address in the communication method described in any one of claims 16 to 24, and the transceiver unit is used to perform the operation of receiving or sending in the communication method described in any one of claims 16 to 24.
27. A communication device, It is characterized in that include: A processor, the processor is coupled to a memory, the memory is used to store instructions, when the processor calls the instructions, the method of any one of claims 1 to 15 is executed or the method of any one of claims 16 to 24 is executed.
28. A communication system, It is characterized in that include: A first network element and a terminal device, wherein the first network element is used to execute the method described in any one of claims 1 to 15, and the terminal device is used to execute the method described in any one of claims 16 to 24.
29. A computer-readable storage medium, It is characterized in that The computer-readable storage medium stores a computer program, and when the computer program is run on a computer, the method according to any one of claims 1 to 15 is executed or the method according to any one of claims 16 to 24 is executed.
30. A communication method, It is characterized in that include: The first network element generates a routing rule based on first information and second information, the first information being used to indicate a service that is allowed to be routed to a local data network in a visited public land mobile network VPLMN, and the second information including a source address used by a terminal device, The routing rule is used by the terminal device to select a source address according to the routing rule; The first network element sends the routing rule; The terminal device receives the routing rule; The terminal device sends information for accessing a service, where the information for accessing a service includes a source address selected according to the routing rule.
Citation Information
Patent Citations
Method and apparatus for providing local data network information to terminal in wireless communication system
CN115699877A
Communication method and device
CN115915091A
Method and Function for Handling Traffic for an Application
US20210099943A1
