Roaming communication method, communication network device, system, and storage medium
Through the interactive communication between the roaming NEF and the home network element function in the terminal roaming state, the problem of high network capability call cost during roaming is solved, and a flexible roaming networking method is realized, reducing the need for deploying equipment and interactive interfaces is achieved. .
Patent Information
- Application Number
- PCT/CN2024/073475
- Authority / Receiving Office
- WO · WO
- Patent Type
- Applications
- Current Assignee / Owner
- Priority Date
- 2023-06-30
- Filing Date
- 2024-01-22
- Publication Date
- 2025-01-02
AI Technical Summary
When roaming at the terminal, due to the lack of interactive interfaces between the roaming network and the home network, the deployment device and additional interactive interfaces need to be added, resulting in a high cost of calling the network capability.
In the terminal roaming state, the roaming network open function NEF receives the capability call request initiated by the home application function AF. If it can be processed, it will communicate with the home network element function to complete the capability call; if it cannot be processed, it will be passed through the home. The interactive communication and communication of NEF with the home network element function completes the capability call, avoiding the need to deploy I-NEF between the roaming network and the home network.
It reduces the cost of terminals' ability to call networks when roaming and communication, and improves deployment flexibility, and is suitable for application scenarios within and outside the trusted domain.
Smart Images

Figure CN2024073475_02012025_PF_FP_ABST
Abstract
Description
Roaming communication method, communication network equipment, system and storage medium
[0001] CROSS-REFERENCE TO RELATED APPLICATIONS
[0002] This disclosure is based on Chinese patent application CN202310802645.6, filed on June 30, 2023, entitled “Roaming Communication Method, Communication Network Equipment, System and Storage Medium”, and claims the priority of the patent application, and all the contents disclosed therein are incorporated into this disclosure by reference. Technical Field
[0003] The present disclosure relates to the field of communication technology, and in particular to a roaming communication method, communication network equipment, system, and storage medium. Background Art
[0004] NEF (Network Exposure Function) is an important component of the 5G network architecture. It supports the opening of various network element functions in the 5G core network to AF (Application Function). These functions mainly include event monitoring, service provisioning, policy / billing, and analysis and reporting capabilities, thus achieving a friendly connection between network capabilities and business needs. However, after the terminal roams, since there is no interactive interface between the NEFs of the roaming network and the home network, it is necessary to set up a centralized I-NEF (Intermediate-NEF) between the roaming network and the home network. This requires the deployment of additional equipment and additional interactive interfaces, which is costly.
[0005] Therefore, how to reduce the cost of calling network capabilities when the terminal is roaming and communicating has become an urgent problem to be solved.
[0006] Summary of the Invention
[0007] The main purpose of the embodiments of the present disclosure is to provide a roaming communication method, communication network equipment, system and storage medium, aiming to reduce the cost of calling network capabilities when a terminal is roaming.
[0008] In a first aspect, an embodiment of the present disclosure provides a roaming communication method, the method comprising: when a terminal is in a roaming state, the roaming network open function NEF receives a capability call request initiated by the home application function AF; determining whether the capability call request can be processed; if so, the roaming NEF interacts with the home network element function to complete the capability call; wherein the home network element function includes at least one of a unified data management function UDM and a policy control function PCF; if not, the home network element function interacts with the home network element function through the home NEF to complete the capability call.
[0009] In a second aspect, an embodiment of the present disclosure provides a communication network device, which includes: a processor, a memory, a computer program stored in the memory and executable by the processor, and a data bus for realizing connection communication between the processor and the memory, wherein when the computer program is executed by the processor, the steps of the roaming communication method as described above are implemented.
[0010] In a third aspect, an embodiment of the present disclosure provides a mobile network system, which includes a home AF, a home NEF, a home network element function, and a roaming NEF, wherein the home network element function includes at least one of UDM and PCF; the home AF is used to initiate a capability call request to the roaming NEF; the roaming NEF is used to determine whether it can process the capability call request; if so, the roaming NEF interacts and communicates with the home network element function to complete the capability call; if not, the home NEF interacts and communicates with the home network element function to complete the capability call.
[0011] In a fourth aspect, an embodiment of the present disclosure provides a storage medium for computer-readable storage, wherein the storage medium stores one or more programs, and the one or more programs can be executed by one or more processors to implement the steps of the roaming communication method as described above. BRIEF DESCRIPTION OF THE DRAWINGS
[0012] In order to more clearly illustrate the technical solutions of the embodiments of the present disclosure, the following briefly introduces the drawings required for use in the description of the embodiments. Obviously, the drawings described below are some embodiments of the present disclosure. For ordinary technicians in this field, other drawings can be obtained based on these drawings without any creative work.
[0013] Figure 1 is a schematic diagram of the NEF framework;
[0014] FIG2 is a schematic diagram of a mobile network system provided by an embodiment of the present disclosure;
[0015] FIG3 is a schematic diagram of a flow chart of a roaming communication method provided by an embodiment of the present disclosure;
[0016] FIG4 is a schematic diagram of an interaction of a mobile network system provided by an embodiment of the present disclosure;
[0017] FIG5 is a schematic diagram of a roaming communication process in which a roaming V-NEF can provide capability invocation according to an embodiment of the present disclosure;
[0018] FIG6 is a schematic diagram of interaction of another mobile network system provided by an embodiment of the present disclosure;
[0019] FIG7 is a schematic diagram of a roaming communication process in which a V-NEF in a roaming location cannot provide capability invocation according to an embodiment of the present disclosure;
[0020] FIG8 is a schematic block diagram of the structure of a communication network device provided by an embodiment of the present disclosure. DETAILED DESCRIPTION
[0021] The following will clearly and completely describe the technical solutions in the embodiments of the present disclosure in conjunction with the accompanying drawings. Obviously, the described embodiments are only part of the embodiments of the present disclosure, not all of them. All other embodiments obtained by ordinary technicians in this field based on the embodiments of the present disclosure without making any creative efforts shall fall within the scope of protection of the present disclosure.
[0022] The flowcharts shown in the accompanying drawings are for illustrative purposes only and do not necessarily include all contents and operations / steps, nor must they be executed in the order described. For example, some operations / steps may be decomposed, combined, or partially merged, so the actual execution order may vary depending on the actual situation.
[0023] It should be understood that the terms used in this disclosure are only for the purpose of describing particular embodiments and are not intended to limit the disclosure. As used in this disclosure and the appended claims, the singular forms "a," "an," and "the" are intended to include the plural forms unless the context clearly indicates otherwise.
[0024] NEF is an important component of the 5G network architecture, supporting the opening of various network element functions in the 5G core network to AF. The network element functions in the 5G core network include but are not limited to PCF (Policy Control Function), UDM (Unified Data Management), UDR (Unified Data Repository), AMF (Access and Mobility Management Function), SMF (Session Management Function), etc.
[0025] As shown in Figure 1, the NEF interacts with the AF using an API (Application Programming Interface), for example, through the N33 interface. The NEF also interacts with the PCF, UDM, UDR, AMF, and SMF through corresponding interfaces. For example, the NEF interacts with the PCF through the N30 interface, the NEF interacts with the UDM through the N52 interface, the NEF interacts with the UDR through the N37 interface, the NEF interacts with the AMF through the N51 interface, and the NEF interacts with the SMF through the N29 interface. The AF refers to various application layer services, which can be internal carrier applications or third-party applications such as video servers and game servers. Internal carrier applications can interact directly with other applications if they are within the same trusted domain. However, some applications within the trusted domain require access to other network element functions through the NEF, such as office applications like employee clocking in. Third-party applications, however, are not within the trusted domain and must access other network element functions through the NEF to subscribe to services or user information.
[0026] NEF supports opening up various network element functions such as PCF, UDM, UDR, AMF, and SMF to AF, mainly including event monitoring capabilities, service provisioning capabilities, policy / billing capabilities, analysis and reporting capabilities, etc., to achieve a friendly connection between network capabilities and business needs. Among them:
[0027] Event monitoring capabilities enable AF to subscribe to and obtain contextual information such as terminal status reports via the network. This allows AF to perform appropriate actions based on the terminal's status to improve AF's service quality or user experience. Event monitoring capabilities include, but are not limited to, subscription and reporting of the following events: connection loss, terminal reachability, terminal location and location updates, device-card detachment, roaming status, communication failures, and the number of terminals in the area.
[0028] The service provisioning capability allows third-party applications to provide expected terminal behavior or service-specific information to various network element functions in the 5G core network through NEF, including authorization information, external information received and supplied via NEF, storage information, etc.
[0029] The policy / charging capability allows requesting session and charging policies, implementing QoS (Quality of Service) policies, and applying charging functions. It can be used to specify QoS for terminal sessions, service priority processing, and set appropriate billing rates for the billing party.
[0030] The analysis and reporting capability allows third-party application data to be collected through NEF and provided to NWDAF (Network Data Analytics Function) for data analysis, and the analysis results are securely provided to third-party applications through NEF.
[0031] When the terminal roams, since there is no interactive interface between the NEFs of the roaming network and the home network, a centralized I-NEF needs to be set up between the roaming network and the home network respectively. Correspondingly, additional equipment and additional interactive interfaces need to be deployed, which is costly.
[0032] In order to solve the above problems, the embodiments of the present disclosure provide a roaming communication method, a communication network device, a system and a storage medium, which aim to reduce the cost of calling network capabilities when a terminal is roaming.
[0033] The following embodiments of the present disclosure are described in detail with reference to the accompanying drawings. In the absence of conflict, the following embodiments and features therein may be combined with each other.
[0034] Please refer to Figure 2, which is a schematic diagram of a mobile network system provided by an embodiment of the present disclosure. As shown in Figure 2, the mobile network system includes a home AF (H-AF), a home NEF (H-NEF), a home network element function, a roaming NEF (V-NEF), and a roaming network element function. The home network element function includes but is not limited to the UDM and PCF, and the roaming network element function includes but is not limited to the AMF and SMF.
[0035] After a terminal roams, the home AF (H-AF) initiates a capability invocation request to the roaming NEF (V-NEF). For example, these requests may include event subscription and notification, network parameter activation / configuration, and requests for network-side QoS control policy adjustments. The V-NEF determines whether it can process the capability invocation request, that is, whether it can provide the requested capability.
[0036] A scenario corresponding to the judgment result is that the V-NEF determines that the capability can be provided. Then, the V-NEF communicates with the local network element functions such as the UDM and PCF to complete the capability call and perform related operations, including but not limited to:
[0037] Subscribe to event monitoring and notifications, including event notification addresses, event reports, and other related information.
[0038] Monitor user dynamic information such as terminal mobility information, accessed service information, user service experience information, as well as functional load information of each network element in the network, wireless network load information (such as cell congestion information), etc.
[0039] Convert the AF's communication parameter configuration request message into an API interface message and send it to the corresponding UDM, AMF,
[0040] SMF and other network element functions. Communication parameters include, but are not limited to, periodic communication flags, communication cycle duration, communication cycle interval duration, designated communication time, terminal type flag, battery type flag, and data transmission type. If a group of terminals exists, the NEF splits each terminal into individual processes to execute related operations.
[0041] Send a request message to PCF, carrying information such as terminal identification, bandwidth, priority, QoS event monitoring indication, etc., to apply for the network side to adjust the QoS service quality control policy, dynamically adjust user policies, etc.
[0042] Another scenario corresponding to the judgment result is that the V-NEF determines that it cannot provide the capability. In this case, the V-NEF feeds back a response failure message of the capability call request to the H-AF. The H-AF initiates a capability call request to the H-NEF. The H-NEF communicates with the home network element functions such as the UDM and PCF to complete the capability call and perform related operations, including but not limited to:
[0043] Subscribe to event monitoring and notifications, including event notification addresses, event reports, and other related information.
[0044] Monitor user dynamic information such as terminal mobility information, accessed service information, user service experience information, as well as functional load information of each network element in the network, wireless network load information (such as cell congestion information), etc.
[0045] The AF's communication parameter configuration request message is converted into an API interface message and sent to the corresponding UDM, AMF, SMF, and other network element functions. Communication parameters include, but are not limited to, periodic communication flags, communication cycle duration, communication cycle interval duration, specified communication time, terminal type flag, battery type flag, and data transmission type. If a group of terminals exists, the NEF splits the process into individual terminals and initiates the relevant operations for each terminal.
[0046] Send a request message to PCF, carrying information such as terminal identification, bandwidth, priority, QoS event monitoring indication, etc., to apply for the network side to adjust the QoS service quality control policy, dynamically adjust user policies, etc.
[0047] In the absence of an interface between the roaming V-NEF and the home H-NEF, the aforementioned mobile network system provides a flexible roaming networking solution. This solution can be applied not only to scenarios where a capability call request is initiated by an internal operator application in a trusted domain while the terminal is roaming, but also to scenarios where a capability call request is initiated by a third-party application within or outside the trusted domain. For capability calls initiated by third-party applications outside the trusted domain, the application must access other network element functions through the NEF in order to subscribe to services or user-related information.
[0048] It can be understood that the above-mentioned mobile network system is not only applicable to the 5G core network, but also to 4G and other future mobile communication networks.
[0049] The following will introduce the roaming communication method provided by the embodiment of the present disclosure in detail based on the mobile network system. It should be noted that the mobile network system in Figure 2 is only used to explain the roaming communication method provided by the embodiment of the present disclosure, but does not constitute a limitation on the application scenarios of the roaming communication method provided by the embodiment of the present disclosure.
[0050] Please refer to Figure 3, which is a flow chart of a roaming communication method provided by an embodiment of the present disclosure. The roaming communication method can be applied in a mobile network system to reduce the cost of invoking network capabilities when a terminal is roaming.
[0051] As shown in FIG3 , the roaming communication method includes steps S101 to S104 .
[0052] S101: When a terminal is in roaming state, a roaming network exposure function (NEF) receives a capability invocation request initiated by a home application function (AF).
[0053] After the terminal roams, the home H-AF initiates a capability call request to the roaming V-NEF. Exemplarily, the capability call request carries AF identification information, access authentication information, capability call information, etc. The access authentication information includes, but is not limited to, tokens and keys, and the capability call information includes, but is not limited to, event IDs, network parameters, collectable data, computing load, network bandwidth, and network service quality. After the H-AF initiates the capability call request to the roaming V-NEF, the V-NEF receives the capability call request initiated by the H-AF.
[0054] Exemplarily, before the H-AF initiates a capability invocation request to the V-NEF, the H-AF receives an interactive message from the User Plane Function (UPF) sent to the H-AF. The message contains encrypted terminal information, such as an encrypted terminal identifier, terminal location information, and / or country code. For example, the encrypted terminal information, such as the terminal identifier, terminal location information, and / or country code, is carried in the message header. The H-AF parses the message to obtain the encrypted terminal information, and decrypts the encrypted terminal information to obtain the terminal information, such as the terminal identifier, terminal location information, and / or country code. Based on the obtained terminal information, exemplarily based on the terminal identifier, terminal location information, and / or country code, the H-AF determines the V-NEF providing services to the user. The H-AF then initiates a capability invocation request to the V-NEF, and the V-NEF receives the capability invocation request initiated by the H-AF.
[0055] S102, determining whether the capability call request can be processed; if so, executing step S103; if not, executing step S104;
[0056] S103. The roaming NEF interacts and communicates with the home network element function to complete capability invocation; wherein the home network element function includes at least one of a unified data management function (UDM) and a policy control function (PCF);
[0057] S104: Interactive communication is performed with the home network element function through the home NEF to complete the capability call.
[0058] After receiving the capability call request initiated by the H-AF, the V-NEF needs to determine whether it can process the capability call request, that is, determine whether it can provide the capability call corresponding to the request.
[0059] In some embodiments, determining whether the capability call request can be processed includes:
[0060] Obtain verification information, where the verification information includes at least one of AF identification information, access authentication information, and capability call information, where the access authentication information includes a token or a key, and the capability call information includes at least one of network parameters, computing load, network bandwidth, and network service quality;
[0061] Verifying the verification information;
[0062] If the verification passes, it is determined that the capability call request can be processed.
[0063] Exemplarily, the V-NEF parses the capability call request received from the H-AF to obtain corresponding verification information, where the verification information includes but is not limited to AF identification information, access authentication information, capability call information, etc. The access authentication information includes a token or key, and the capability call information includes but is not limited to event ID, network parameters, collectable data, computing load, network bandwidth, network service quality, etc.
[0064] The V-NEF verifies the AF identification information, access authentication information, capability call information and other verification information. If the verification passes, it is determined that the capability call request can be processed, that is, the capability call corresponding to the request can be provided. Conversely, if the verification fails, it is determined that the capability call request cannot be processed, that is, the capability call corresponding to the request cannot be provided.
[0065] In some embodiments, verifying the verification information includes:
[0066] Verify whether the AF identification information is legal;
[0067] Verify whether the access authentication information is correct;
[0068] Verify whether the capability called in the capability calling information is in the subscription list of the terminal and whether it meets the subscription calling policy.
[0069] Exemplarily, V-NEF verifies whether the AF identification information is legal, whether the token or key is correct, and whether the capability corresponding to the capability call information is in the contract list of the terminal and satisfies the contract call policy. If the AF identification information is legal, the token or key is correct, and the capability corresponding to the capability call information is in the contract list of the terminal and satisfies the contract call policy, then it is determined that the verification is passed and the capability call request can be processed, that is, the capability call corresponding to the request can be provided. Otherwise, if the verification AF identification information is illegal, or the token or key is incorrect, or the capability corresponding to the capability call information is not in the contract list of the terminal or does not satisfy the contract call policy, then it is determined that the verification fails and the capability call request cannot be processed, that is, the capability call corresponding to the request cannot be provided.
[0070] In one scenario, if the V-NEF determines that the capability can be provided, the V-NEF will communicate with the local network element functions such as the UDM and PCF to complete the capability call and perform related operations, including but not limited to:
[0071] Subscribe to event monitoring and notifications, including event notification addresses, event reports, and other related information.
[0072] Monitor user dynamic information such as terminal mobility information, accessed service information, user service experience information, as well as functional load information of each network element in the network, wireless network load information (such as cell congestion information), etc.
[0073] The AF's communication parameter configuration request message is converted into an API interface message and sent to the corresponding UDM, AMF, SMF, and other network element functions. Communication parameters include, but are not limited to, periodic communication flags, communication cycle duration, communication cycle interval duration, specified communication time, terminal type flag, battery type flag, and data transmission type. If a group of terminals exists, the NEF splits the process into individual terminals and initiates the relevant operations for each terminal.
[0074] Send a request message to PCF, carrying information such as terminal identification, bandwidth, priority, QoS event monitoring indication, etc., to apply for the network side to adjust the QoS service quality control policy, dynamically adjust user policies, etc.
[0075] In some embodiments, the roaming NEF interacts and communicates with the home network element function to complete the capability call, including:
[0076] Sending a capability call instruction to the home UDM and / or PCF, so that the home UDM and / or PCF interacts and communicates with a roaming network element function, and the roaming network element function executes the capability call; wherein the roaming network element function includes at least one of an access and mobility management function (AMF) and a session management function (SMF);
[0077] Receive a capability execution result notification reported by the roaming network element function.
[0078] If the V-NEF determines that the capability call can be provided, the V-NEF sends a capability call instruction to the home UDM and / or PCF, as shown in Figure 4. After the home UDM and / or PCF receives the capability call instruction, the home UDM and / or PCF communicates with the roaming AMF and / or SMF, and the roaming AMF and / or SMF executes the capability call.
[0079] The roaming AMF and / or SMF reports the capability execution result notification to the V-NEF, and the V-NEF receives the capability execution result notification reported by the roaming AMF and / or SMF. The capability execution result notification includes but is not limited to event monitoring capability, reporting event notification, etc.
[0080] Exemplarily, after receiving the capability execution result reported by the roaming network element function, the method includes:
[0081] Generate capability call results;
[0082] Push the capability call result to the home AF.
[0083] After receiving the capability execution result notification, V-NEF analyzes and processes the capability execution result notification. Based on the network configuration, when the business-related judgment conditions are met, it generates the capability call result and pushes the capability call result to the home H-AF.
[0084] For example, as shown in Figure 5, the roaming communication process that V-NEF can provide for capability invocation is as follows:
[0085] Step 1: The home H-AF finds the roaming V-NEF based on the terminal identifier, terminal location information and / or country code. The H-AF initiates a capability call request to the V-NEF, including the AF identifier, access authentication information (token or key, etc.), and capability call information.
[0086] Step 2: V-NEF determines whether it can provide the corresponding capability call. NEF verifies the AF identifier, access authentication information, and capability call information, including whether the AF identifier is legal, whether the token or key is correct, whether the called capability is in the terminal's contract list, and whether it meets the contracted call policy. It then comprehensively determines whether it can process the corresponding capability call request.
[0087] Step 3: If it is determined that the corresponding capability call request can be processed, the V-NEF sends a capability call instruction to the home UDM and / or PCF. For example, it initiates a monitoring request for subscription events and obtains notifications, and / or converts the AF's network parameter configuration request message into a home UDM interface message for configuration update, and / or sends a request message to the home PCF, carrying the terminal identification, bandwidth, priority, QoS event monitoring indication, etc., to request the network side to adjust the QoS service quality control policy and dynamically adjust the user policy.
[0088] Step 4: The UDM and / or PCF in the home location interacts with the AMF and / or SMF in the roaming location.
[0089] Step 5: The roaming AMF and / or SMF executes the capability call. The roaming AMF and / or SMF reports the capability execution result notification to the V-NEF, such as event monitoring capability, reporting event notification, etc.
[0090] Step 6: V-NEF analyzes and processes the capability execution result notification, generates the capability call result, and pushes the capability call result to H-AF.
[0091] In another scenario, if the V-NEF determines that it cannot provide the capability, the V-NEF will feedback the capability call request failure response information to the H-AF. The H-AF will initiate the capability call request to the H-NEF. The H-NEF will interact with the home network element functions such as the UDM and PCF to complete the capability call and perform related operations, including but not limited to:
[0092] Subscribe to event monitoring and notifications, including event notification addresses, event reports, and other related information.
[0093] Monitor user dynamic information such as terminal mobility information, accessed service information, user service experience information, as well as functional load information of each network element in the network, wireless network load information (such as cell congestion information), etc.
[0094] The AF's communication parameter configuration request message is converted into an API interface message and sent to the corresponding UDM, AMF, SMF, and other network element functions. Communication parameters include, but are not limited to, periodic communication flags, communication cycle duration, communication cycle interval duration, specified communication time, terminal type flag, battery type flag, and data transmission type. If a group of terminals exists, the NEF splits the process into individual terminals and initiates the relevant operations for each terminal.
[0095] Send a request message to PCF, carrying information such as terminal identification, bandwidth, priority, QoS event monitoring indication, etc., to apply for the network side to adjust the QoS service quality control policy, dynamically adjust user policies, etc.
[0096] In some embodiments, the interactive communication with the home network element function through the home NEF to complete the capability call includes:
[0097] Sending a response failure message of the capability call request to the home AF, so that when the home AF receives the failure message, it initiates a capability call request to the home NEF, the home NEF sends a capability call instruction to the home UDM and / or PCF, the home UDM and / or PCF interacts and communicates with the roaming network element function, the roaming network element function executes the capability call, and reports a capability execution result notification to the home NEF.
[0098] If the V-NEF determines that it cannot provide the capability call, it sends a failure response to the capability call request to the home H-AF. Upon receiving this failure response, the H-AF initiates a capability call request to the H-NEF, which then sends a capability call instruction to the home UDM and / or PCF. For example, as shown in Figure 6, after receiving the capability call instruction, the home UDM and / or PCF communicates with the roaming AMF and / or SMF, and the roaming AMF and / or SMF executes the capability call.
[0099] The roaming AMF and / or SMF reports the capability execution result notification to the H-NEF, and the H-NEF receives the capability execution result notification reported by the roaming AMF and / or SMF. The capability execution result notification includes but is not limited to event monitoring capability, reporting event notification, etc.
[0100] After receiving the capability execution result notification, H-NEF analyzes and processes the capability execution result notification. Based on the network configuration, when the business-related judgment conditions are met, it generates the capability call result and pushes the capability call result to the home H-AF.
[0101] For example, as shown in Figure 7, the roaming communication process in which V-NEF cannot provide capability invocation is as follows:
[0102] Step 1: The home H-AF finds the roaming V-NEF based on the terminal identifier, terminal location information and / or country code. The H-AF initiates a capability call request to the V-NEF, including the AF identifier, access authentication information (token or key, etc.), and capability call information.
[0103] Step 2: V-NEF determines whether it can provide the corresponding capability call. NEF verifies the AF identifier, access authentication information, and capability call information, including whether the AF identifier is legal, whether the token or key is correct, whether the called capability is in the terminal's contract list, and whether it meets the contracted call policy. It then comprehensively determines whether it can process the corresponding capability call request.
[0104] Step 3: If it is determined that the corresponding capability call request cannot be processed, the V-NEF feeds back a failure message to the H-AF.
[0105] Step 4: H-AF initiates a capability call request to H-NEF.
[0106] Step 5: H-NEF sends a capability call instruction to the home UDM and / or PCF, for example, initiates a monitoring request for subscription events and obtains notifications, and / or converts the AF's network parameter configuration request message into a home UDM interface message for configuration update, and / or sends a request message to the home PCF, carrying user identification, bandwidth, priority, QoS event monitoring indication, etc., to apply for the network side to adjust the QoS service quality control policy, dynamically adjust the user policy, etc.
[0107] Step 6: The UDM and / or PCF in the home location interacts with the AMF and / or SMF in the roaming location.
[0108] Step 7: The roaming AMF and / or SMF executes the capability call. The roaming AMF and / or SMF reports the capability execution result notification to the H-NEF, such as event monitoring capability, reporting event notification, etc.
[0109] Step 8: H-NEF analyzes and processes the capability execution result notification, generates a capability call result, and pushes the capability call result to H-AF.
[0110] The above roaming method eliminates the need to deploy an I-NEF between the roaming and home networks, and accordingly eliminates the need for additional deployment equipment and additional interaction interfaces, reducing costs. Compared to applications within carriers that are only applicable to trusted domains, this disclosure also applies to scenarios where third-party applications initiate network capability exposure requests during terminal roaming, improving deployment flexibility.
[0111] In the above embodiment, when the terminal is in a roaming state, the home AF initiates a capability call request to the roaming NEF. The roaming NEF determines whether it can process the capability call request. If so, the roaming NEF interacts and communicates with the home network element function to complete the capability call. The home network element function includes at least one of a UDM and a PCF. If not, the home NEF interacts and communicates with the home network element function to complete the capability call. This enables the completion of network capability call when there is no interface communication between the roaming NEF and the home NEF, thereby reducing the cost of calling network capabilities.
[0112] An embodiment of the present disclosure further provides a communication network device. Please refer to FIG8 , which is a schematic block diagram of the communication network device provided by an embodiment of the present disclosure.
[0113] As shown in FIG8 , the communication network device 200 may include a processor 210 and a memory 220 , wherein the processor 210 and the memory 220 are connected via a bus, such as an I2C (Inter-integrated Circuit) bus.
[0114] Specifically, the processor 210 may be a micro-controller unit (MCU), a central processing unit (CPU), or a digital signal processor (DSP).
[0115] Specifically, the memory 220 may be a Flash chip, a read-only memory (ROM) disk, an optical disk, a USB flash drive, or a mobile hard disk, etc. The memory 220 stores various computer programs for execution by the processor 210 .
[0116] The processor 210 is configured to run a computer program stored in the memory and implement the following steps when executing the computer program:
[0117] When the terminal is in roaming state, the roaming network open function NEF receives the capability call request initiated by the home application function AF;
[0118] Determining whether the capability call request can be processed;
[0119] If so, the roaming NEF interacts and communicates with the home network element function to complete the capability call; wherein the home network element function includes at least one of the unified data management function UDM and the policy control function PCF;
[0120] If not, the home NEF interacts with the home network element function to complete the capability call.
[0121] In some embodiments, when implementing interactive communication between the roaming NEF and the home network element function to complete capability invocation, the processor 210 is configured to implement:
[0122] Sending a capability call instruction to the home UDM and / or PCF, so that the home UDM and / or PCF interacts and communicates with a roaming network element function, and the roaming network element function executes the capability call; wherein the roaming network element function includes at least one of an access and mobility management function (AMF) and a session management function (SMF);
[0123] Receive a capability execution result notification reported by the roaming network element function.
[0124] In some embodiments, after receiving the capability execution result reported by the roaming network element function, the processor 210 is configured to implement:
[0125] Generate capability call results;
[0126] Push the capability call result to the home AF.
[0127] In some embodiments, when implementing the interactive communication with the home network element function through the home NEF and completing the capability call, the processor 210 is configured to implement:
[0128] Sending a response failure message of the capability call request to the home AF, so that when the home AF receives the failure message, it initiates a capability call request to the home NEF, the home NEF sends a capability call instruction to the home UDM and / or PCF, the home UDM and / or PCF interacts and communicates with the roaming network element function, the roaming network element function executes the capability call, and reports a capability execution result notification to the home NEF.
[0129] In some embodiments, the roaming location NEF is determined by the home location AF based on terminal information, wherein the terminal information includes terminal identification, terminal location information and / or country code; when the home location AF receives the user plane network element function UPF message, it decrypts the encrypted terminal information carried in the message to obtain the terminal information.
[0130] In some embodiments, when implementing the determination of whether the capability call request can be processed, the processor 210 is configured to implement:
[0131] Obtain verification information, where the verification information includes at least one of AF identification information, access authentication information, and capability call information, where the access authentication information includes a token or a key, and the capability call information includes at least one of network parameters, computing load, network bandwidth, and network service quality;
[0132] Verifying the verification information;
[0133] If the verification passes, it is determined that the capability call request can be processed.
[0134] In some embodiments, when implementing the verification of the verification information, the processor 210 is configured to implement:
[0135] Verify whether the AF identification information is legal;
[0136] Verify whether the access authentication information is correct;
[0137] Verify whether the capability called in the capability calling information is in the subscription list of the terminal and whether it meets the subscription calling policy.
[0138] An embodiment of the present disclosure also provides a storage medium for computer-readable storage, wherein the storage medium stores one or more programs, and the one or more programs can be executed by one or more processors to implement the steps of any roaming communication method provided in the description of the embodiment of the present disclosure.
[0139] The storage medium may be an internal storage unit of the communication network device described in the preceding embodiments, such as a hard disk or memory of the communication network device. The storage medium may also be an external storage device of the communication network device, such as a plug-in hard disk, a smart media card (SMC), a secure digital (SD) card, a flash memory card, etc., provided on the communication network device.
[0140] It will be appreciated by those skilled in the art that all or some of the steps, systems, and functional modules / units in the methods disclosed above may be implemented as software, firmware, hardware, and appropriate combinations thereof. In a hardware embodiment, the division between the functional modules / units mentioned in the above description does not necessarily correspond to the division of physical components; for example, a physical component may have multiple functions, or a function or step may be performed by several physical components in cooperation. Some or all physical components may be implemented as software executed by a processor, such as a central processing unit, a digital signal processor, or a microprocessor, or implemented as hardware, or implemented as an integrated circuit, such as an application-specific integrated circuit. Such software may be distributed on a computer-readable medium, which may include a computer storage medium (or non-transitory medium) and a communication medium (or temporary medium). As is well known to those skilled in the art, the term computer storage medium includes volatile and non-volatile, removable, and non-removable media implemented in any method or technology for storing information (such as computer-readable instructions, data structures, program modules, or other data). Computer storage media include, but are not limited to, RAM, ROM, EEPROM, flash memory or other memory technology, CD-ROM, digital versatile disks (DVD) or other optical disk storage, magnetic cassettes, magnetic tape, magnetic disk storage or other magnetic storage devices, or any other medium that can be used to store the desired information and can be accessed by a computer. In addition, it is well known to those skilled in the art that communication media generally embodies computer-readable instructions, data structures, program modules, or other data in a modulated data signal such as a carrier wave or other transport mechanism, and may include any information delivery media.
[0141] It should be understood that the term "and / or" as used in this disclosure and the appended claims refers to any combination of one or more of the associated listed items and all possible combinations, including these combinations. It should be noted that, in this article, the terms "include", "comprise" or any other variations thereof are intended to cover non-exclusive inclusion, so that a process, method, article or system that includes a series of elements includes not only those elements, but also includes other elements that are not explicitly listed, or also includes elements that are inherent to such process, method, article or system. In the absence of further restrictions, an element defined by the sentence "including a..." does not exclude the presence of other identical elements in the process, method, article or system that includes the element.
[0142] The serial numbers of the embodiments of the present disclosure are for description only and do not represent the advantages or disadvantages of the embodiments. The above description is only a specific embodiment of the present disclosure, but the scope of protection of the present disclosure is not limited thereto. Any technician familiar with the technical field can easily think of various equivalent modifications or replacements within the technical scope disclosed in the present disclosure, and these modifications or replacements should be included in the scope of protection of the present disclosure. Therefore, the scope of protection of the present disclosure should be based on the scope of protection of the claims.
Claims
1. A roaming communication method, the method comprising: When the terminal is in roaming state, the roaming network open function NEF receives the capability call request initiated by the home application function AF; Determining whether the capability call request can be processed; If yes, the roaming NEF interacts with the home network element function to complete the capability call; wherein the home network element function includes at least one of a unified data management function UDM and a policy control function PCF; If not, the home NEF interacts with the home network element function to complete the capability call.
2. The method according to claim 1, wherein: The roaming NEF interacts and communicates with the home network element function to complete the capability call, including: Sending a capability call instruction to the home UDM and / or PCF, so that the home UDM and / or PCF interacts and communicates with the roaming network element function, and the roaming network element function executes the capability call; wherein the roaming network element function includes at least one of an access and mobility management function AMF and a session management function SMF; Receive a capability execution result notification reported by the roaming network element function.
3. The method according to claim 2, wherein: After receiving the capability execution result reported by the roaming network element function, the method further comprises: Generate capability call results; Push the capability calling result to the home AF.
4. The method according to claim 1, wherein: The interactive communication with the home network element function through the home NEF to complete the capability call includes: Send a response failure message of the capability call request to the home AF, so that when the home AF receives the failure message, it initiates a capability call request to the home NEF, the home NEF sends a capability call instruction to the home UDM and / or PCF, the home UDM and / or PCF interacts and communicates with the roaming network element function, the roaming network element function executes the capability call, and reports a capability execution result notification to the home NEF.
5. The method according to claim 1, wherein: The roaming location NEF is determined by the home location AF based on terminal information, wherein the terminal information includes terminal identification, terminal location information and / or country code; when the home location AF receives the user plane network element function UPF message, it decrypts the encrypted terminal information carried in the message to obtain the terminal information.
6. The method according to any one of claims 1 to 5, wherein: The determining whether the capability call request can be processed includes: Acquire verification information, where the verification information includes at least one of AF identification information, access authentication information, and capability call information, where the access authentication information includes a token or a key, and the capability call information includes at least one of network parameters, computing power load, network bandwidth, and network service quality; Verifying the verification information; If the verification passes, it is determined that the capability call request can be processed.
7. The method according to claim 6, wherein: The verifying the verification information includes: Verify whether the AF identification information is legal; Verifying whether the access authentication information is correct; Verify whether the capability corresponding to the capability call in the capability call information is in the subscription list of the terminal and whether it satisfies the subscription call policy.
8. A communication network device, wherein: The communication network equipment comprises: A processor, a memory, a computer program stored in the memory and executable by the processor, and a data bus for realizing connection communication between the processor and the memory, wherein when the computer program is executed by the processor, the steps of the roaming communication method according to any one of claims 1 to 7 are realized.
9. A mobile network system, wherein: The mobile network system includes a home AF, a home NEF, a home network element function, and a roaming NEF, wherein the home network element function includes at least one of a UDM and a PCF; the home AF is used to initiate a capability call request to the roaming NEF; The roaming NEF is used to determine whether the capability call request can be processed; If so, the roaming NEF interacts and communicates with the home network element function to complete the capability call; if not, the home NEF interacts and communicates with the home network element function to complete the capability call.
10. A storage medium for computer-readable storage, wherein: The storage medium stores one or more programs, and the one or more programs can be executed by one or more processors to implement the steps of the roaming communication method according to any one of claims 1 to 7.
Citation Information
Patent Citations
Data distribution method and device, equipment and storage medium
CN115776487A
Communication method and device
CN117014854A
AF influenced PDU session management and subscription procedures
US20180270778A1
Method for providing network function for roaming user equipment
US20230308998A1