Call service processing method, system, and apparatus, and computer readable storage medium

Abstract

The present application provides a call service processing method, comprising: when receiving service packets initiated by a user equipment (UE), a central user plane function network element center UPF identifies a service packet satisfying a preset condition to obtain a target service packet; the central UPF reports the target service packet to a session management network element SMF; and the SMF receives the target service packet reported by the central UPF, and selects a local UPF to process the target service packet. The present application further provides a call service processing system and apparatus, and a computer readable storage medium.

Description

Call service processing method, system, device and computer-readable storage medium

[0001] Related applications

[0002] This application claims priority to Chinese patent application No. 202310762235.3 filed on June 26, 2023, the entire contents of which are incorporated by reference into this application. Technical Field

[0003] The present application relates to the field of communication technology, and in particular to a call service processing method, system, device and computer-readable storage medium. Background Art

[0004] With the large-scale deployment of 5G networks and the commercialization of VoNR services, the large bandwidth and low latency characteristics of 5G and 5G-Advanced provide a solid network foundation for upgrading high-definition audio and video communications to interactive and immersive audio and video communications. Under the 5G-Advanced architecture, VoNR networks will evolve into VoNR+ networks. VoNR+ (Voice over New Radio) refers to the superposition of new data channels and pan-voice capabilities accompanying audio and video on the 5G VoNR network. It supports multiple types of data transmission and provides the foundational capability foundation for the VoNR+ service ecosystem.

[0005] Because VoNR+ supports more application scenarios, a large number of messages will be sent from the calling user to the called user. These messages will pass through the calling user plane function (UPF), the IP multimedia subsystem (IMS), and the called user's UPF (a long message transmission path). This large number of messages will increase the load on the IMS and large network UPFs, affecting service data transmission and reducing call quality.

[0006] Summary of the Invention

[0007] In response to the above technical problems, the present application provides a call service processing method, system, device and computer-readable storage medium, aiming to reduce the load of IMS and large network UPF and improve the VoNR+ new call effect.

[0008] In the first aspect, the present application provides a call service processing method, including: when the central user plane function network element center UPF receives a service message initiated by the user equipment UE, it identifies the service message that meets the preset conditions and obtains the target service message; the central UPF reports the target service message to the session management network element SMF; the SMF receives the target service message reported by the central UPF, and selects a local UPF to process the target service message.

[0009] On the other hand, the present application also provides a call service processing method, including: the session management network element SMF receives the target service message reported by the central user plane function network element center UPF; and selects a local UPF to process the target service message.

[0010] On the other hand, the present application also provides a call service processing method, including: when the central user plane function network element center UPF receives a service message initiated by the user equipment UE, it identifies the service message that meets the preset conditions and obtains the target service message; and reports the target service message to the session management network element SMF.

[0011] On the other hand, an embodiment of the present application also provides a call service processing system, including: a processor; a storage device on which a program is stored, and when the program is executed by the processor, the processor implements the steps of the call service processing method described in any one of the above.

[0012] On the other hand, an embodiment of the present application also provides a call service processing device, including: one or more processors; a storage device on which one or more programs are stored, and when the one or more programs are executed by the one or more processors, the one or more processors implement the above-mentioned call service processing method.

[0013] On the other hand, an embodiment of the present application further provides a computer storage medium storing a computer processing program, wherein the computer processing program is called by a processor to execute the call service processing method described in any of the above embodiments. BRIEF DESCRIPTION OF THE DRAWINGS

[0014] The accompanying drawings herein are incorporated into and constitute a part of the specification, illustrate embodiments consistent with the present application, and together with the specification, are used to explain the principles of the present application. In order to more clearly illustrate the technical solutions of the embodiments of the present application, the following is a brief introduction to the drawings required for describing the embodiments. Obviously, for those skilled in the art, other drawings can be obtained based on these drawings without inventive work.

[0015] FIG1 is a schematic diagram of a 5G architecture for implementing the present call service processing method;

[0016] FIG2 is a schematic diagram of another 5G architecture for implementing the present call service processing method;

[0017] FIG3 is a flow chart of a first embodiment of a method for processing a call service application;

[0018] FIG4 is a flow chart of a second embodiment of a method for processing a call service application;

[0019] 5 is a schematic diagram of data optimization in the second embodiment of the call service processing method of the present application;

[0020] FIG6 is a flow chart of a third embodiment of a method for processing a call service application;

[0021] 7 is a flowchart of a fourth embodiment of the present application call service processing method;

[0022] FIG8 is a schematic diagram of data optimization in the fourth embodiment of the call service processing method of the present application.

[0023] The purpose of this application, its features, and advantages will be further described in conjunction with the embodiments and with reference to the accompanying drawings. The accompanying drawings illustrate specific embodiments of this application, which will be described in more detail below. These drawings and the accompanying text are not intended to limit the scope of the present application in any way, but rather to illustrate the concepts of this application to those skilled in the art by reference to specific embodiments. DETAILED DESCRIPTION

[0024] Exemplary embodiments will be described in detail herein, with examples illustrated in the accompanying drawings. In the following description, when referring to the drawings, identical numerals in different figures represent identical or similar elements, unless otherwise indicated. The embodiments described in the following exemplary embodiments are not intended to represent all embodiments consistent with the present application. Rather, they are merely examples of apparatus and methods consistent with certain aspects of the present application, as detailed in the appended claims.

[0025] As used herein, the terms "comprises," "includes," or any other variations thereof are intended to encompass non-exclusive inclusion, such that a process, method, article, or apparatus comprising a series of elements includes not only those elements but also other elements not explicitly listed, or includes elements inherent to such process, method, article, or apparatus. In the absence of further limitations, an element defined by the phrase "comprising a ..." does not exclude the presence of other identical elements in the process, method, article, or apparatus comprising the element. In addition, components, features, and elements with the same name in different embodiments of the present application may have the same meaning or different meanings, and their specific meanings shall be determined by their interpretation in the specific embodiment or further in conjunction with the context of the specific embodiment.

[0026] Although terms such as first, second, and third may be used herein to describe various information, such information should not be limited to these terms. These terms are merely used to distinguish information of the same type from one another. For example, without departing from the scope of this document, first information may also be referred to as second information, and similarly, second information may also be referred to as first information. Depending on the context, the term "if" as used herein may be interpreted as meaning "at the time of," "when," or "in response to a determination." Furthermore, as used herein, the singular forms "a," "an," and "the" are intended to include the plural forms as well, unless the context indicates otherwise. It should be further understood that the terms "comprising" and "including" indicate the presence of the described features, steps, operations, elements, components, items, types, and / or groups, but do not exclude the presence, occurrence, or addition of one or more other features, steps, operations, elements, components, items, types, and / or groups. The terms "or," "and / or," "including at least one of the following," etc., used herein, may be interpreted as inclusive, meaning any one or any combination. For example, “comprising at least one of the following: A, B, C” means “any of the following: A; B; C; A and B; A and C; B and C; A and B and C”; and for another example, “A, B or C” or “A, B and / or C” means “any of the following: A; B; C; A and B; A and C; B and C; A and B and C”. An exception to this definition will occur only when a combination of elements, functions, steps or operations are inherently mutually exclusive in some manner.

[0027] Although the various steps in the flowchart in the embodiment of the present application are shown in sequence according to the indication of the arrows, these steps are not necessarily performed in sequence in the order indicated by the arrows. Unless clearly stated herein, the execution of these steps is not strictly limited in order and can be performed in other orders. Moreover, at least a portion of the steps in the figure may include multiple sub-steps or multiple stages, and these sub-steps or stages are not necessarily performed at the same time, but can be performed at different times, and their execution order is not necessarily performed in sequence, but can be performed in turn or alternately with at least a portion of other steps or sub-steps or stages of other steps.

[0028] As used herein, the words "if" and "if" may be interpreted as "at the time of" or "when" or "in response to determining" or "in response to detecting," depending on the context. Similarly, the phrases "if it is determined" or "if (stated condition or event) is detected" may be interpreted as "when it is determined" or "in response to the determination" or "when detecting (stated condition or event)" or "in response to detecting (stated condition or event)," depending on the context.

[0029] It should be noted that in this article, step codes such as S10 and S20 are used for the purpose of expressing the corresponding content more clearly and concisely, and do not constitute a substantial limitation on the order. When implementing the step, those skilled in the art may execute S20 first and then S10, etc., but these should all be within the scope of protection of this application.

[0030] The specific embodiments described herein are merely used to explain the present application and are not intended to limit the present application.

[0031] In the subsequent description, the use of suffixes such as "module", "component" or "unit" to represent elements is only for the purpose of facilitating the description of the present application and has no specific meaning. Therefore, "module", "component" or "unit" can be used interchangeably.

[0032] VoNR+ (Voice over New Radio) new calls support more application scenarios. Therefore, when a call is established, in addition to establishing traditional dedicated voice and video bearers, other new data channels will be established according to new business needs to transmit all business data. With the increase in application scenarios, a large amount of new business data will inevitably be added. These business data need to pass through the calling user UPF (User Plane Function), IMS (IP Multimedia Subsystem), and the called user UPF (long message transmission path) from the calling user to the called user. The addition of a large number of messages will increase the load on the IMS and the large network UPF, which will not only affect the transmission of the original VoNR voice service, but also affect the transmission of new business data, reducing the call quality.

[0033] To address this issue, a new approach has been proposed to improve VoNR+ call quality. This approach categorizes new VoNR+ services, offloading some services locally to reduce the amount of data transmitted to the user, thereby lowering the load on the IMS and large-scale network UPFs. Alternatively, by optimizing the transmission format of service data and reducing the transmission load, the load on the IMS and large-scale network UPFs can be reduced, improving service data transmission efficiency and ultimately improving VoNR+ call quality.

[0034] Please refer to Figures 1 and 2. Figure 1 shows a 5G system architecture (non-roaming scenario) involved in the call service processing method of this application, and Figure 2 shows another 5G system architecture (roaming scenario) involved in the call service processing method of this application.

[0035] In non-roaming scenarios, the 5G system architecture: ULCL (UpLink Classifier) ​​and PSA1 (PDU Session Anchor 1) are jointly set up, which includes: UE (User Equipment), (R)AN ((Radio)Access Network, (Radio)Access Network), AMF (Access and Mobility Management Function), SMF (Session Management Function), ULCL (UpLink Classifier), PSA (PDU Session Anchor).

[0036] In the roaming scenario, the 5G system architecture: ULCL (UpLink Classifier) ​​and PSA1 (PDU Session Anchor 1) are jointly set up, which includes: UE (User Equipment), (R)AN ((Radio)Access Network, (Radio)Access Network), AMF (Access and Mobility Management Function), I-SMF (Intermediate Session Management Function), A-SMF, ULCL (UpLink Classifier), PSA (PDU Session Anchor).

[0037] Based on the above system architecture, the present application call service processing method implements the operation of the following embodiments.

[0038] Referring to Figure 3, which is a flowchart illustrating an embodiment of a call service processing method of the present application, this embodiment illustrates a method for processing a new service message in a call service, such as offloading the new service message to a local server for processing, thereby reducing the transmission of service messages during a call, thereby reducing the load on the IMS and the large network UPF, and improving call quality.

[0039] In this embodiment, the call service processing method includes:

[0040] Step S301: The UE has completed going online and is in an online state.

[0041] The user terminal has completed going online and is in an online state. At this time, the user terminal can initiate a call request, or the user terminal can receive a call request.

[0042] Step S302: A local UPF capable of processing VoNR+ services registers with the UM.

[0043] VoNR+ services include the existing VoNR voice services and new services compared to the existing VoNR voice services. Because VoNR+ new calls support more application scenarios, when a VoNR+ call is established, in addition to the existing VoNR voice services, services for other application scenarios are also available.

[0044] In one embodiment, the 5G communication architecture includes both local UPFs and large-network UPFs. The local UPFs have the ability to process certain services (i.e., enforce service message rules), such as translation and intelligent customer service Q&A, without requiring processing by the large-network UPF. Therefore, after a user terminal goes online, the local UPF registers with the UM, indicating its processing capabilities. For example, a field "Capability: Local service processing" is added to the N4 PFCP Association Setup Req message. This allows the UM to record the service processing capabilities of each local UPF.

[0045] In one embodiment, different local UPFs have different service processing capabilities, and the corresponding service processing capabilities are marked according to the service types to be processed. In this way, the local UPF can be selected based on the service type that matches the processing capability reported by the local UPF.

[0046] Step S303: The user terminal initiates a VoNR+ call request, and the IMS initiates the entire VoNR+ service process.

[0047] When the user terminal initiates a VoNR+ call request, the VoNR+ service process is started. Before any service message is transmitted, the rules for identifying service messages are established, that is, the detection rules for service messages are established to establish a processing environment for the local UPF to process service messages.

[0048] Step S304: PCF issues the policy to SMF;

[0049] Because the call request is a VoNR+ call request, which includes the existing VoNR voice service and services in other application scenarios, the policy issued by the PFC includes policies related to accessing the VoNR voice service and policies related to accessing the newly added VoNR+ services.

[0050] After the user terminal initiates a call request, the PCF (Policy Control Function Network Element) issues a policy for the call request, and further determines a processing rule for the call request.

[0051] Step S305: The SMF responds to the policy issued by the PCF.

[0052] In this embodiment, the SMF responds to the policy issued by the PCF and identifies the IMS (IP Multimedia Subsystem) session to determine whether the IMS session includes a request for a new service.

[0053] If the IMS session includes a request for a new service, the data network interface identifier (Dnai) in the policy rule is used to identify whether the call involves the new service. In this embodiment, new services that are not related to the peer user are configured as target service messages, and new services that are not related to the peer user are configured as service messages that can be processed by the local server.

[0054] In this embodiment, SMF determines whether the rules of the target business message are involved by identifying the rules of the call request. If so, it determines that some business messages in the call can be diverted to the local server and processed by the local server.

[0055] In one embodiment, when it is determined that there is a target service message, the SMF first combines the processing capabilities of the local UPF reported when the local UPF registers with the UM, such as the ability to execute target service message rules, to determine the local UPF that can locally process the target service message, and selects the local UPF to process the newly added target service message in the call.

[0056] If the pre-stored local UPF has the ability to execute the diversion business rules of the target business message, the diversion business rules are cached so that when there are subsequent business messages, the diversion business rules are used to locally process the business messages.

[0057] In this embodiment, if the UPF with processing capabilities reported by the local UPF does not include the processing capabilities to process the target business message, that is, the pre-stored local UPF does not have the ability to execute the diversion business rules of the target business message, then this embodiment can also create a local UPF that can process the target business message according to the requirements of the target business message.

[0058] Alternatively, for uplink triggered services, you can consider establishing ULCL after it is triggered when the user has an uplink message, that is, inserting the local UPF on demand. That is, the uplink message is relatively random and diverse, so you can create a local UPF that can process the message according to the needs of the target service message.

[0059] When the SMF determines that the system has a local UPF that can process the target service message, it caches the diversion rules of the target service message (in this embodiment, the diversion service rule refers to the rule for processing the service message, which is defined as a diversion service rule because it can be diverted from other voice message services).

[0060] In one embodiment, the SMF also constructs a detection rule for the diversion service rule, which is used to identify the type of service message transmitted during the call, and then triggers the selection of local UPF processing or transmission to the large network UPF (central UPF) for processing.

[0061] Step S306: SMF initiates a user plane update request and notifies the central UPF to install the detection rules.

[0062] After the SMF constructs the detection rule for the offload service rule, it sends a user plane update message to the central UPF, so that the central UPF can update the user plane function of the central UPF. The update request carries the detection rule constructed in step S305. The central UPF installs the detection rule and responds to the SMF with the installation result and allocated resource information.

[0063] Step S307: The UE initiates a service (such as intelligent translation, intelligent customer service, etc.).

[0064] The user terminal initiates a service and generates a service message.

[0065] In this embodiment, VoNR+ calls include a variety of call scenarios, and therefore a variety of service message types. These scenarios include intelligent translation, intelligent customer service, fun calls, screen sharing, and home terminals. The corresponding message types are different from those of existing VoNR voice and video call scenarios.

[0066] Step S308: The message arrives at the central UPF through the base station, and the central UPF identifies the service message that meets the preset conditions and obtains the target service message.

[0067] When the central UPF receives a service message initiated by the UE, it identifies the type of the service message and determines whether it is a target service message. The target service message refers to the service message newly added to the VoNR+ call in this embodiment, and the service message meets the following conditions: a service message that is not related to the opposite user.

[0068] If the service message is a target service message, the central UPF reports the service message to the SMF, and the SMF selects a local UPF to process the service message.

[0069] If the service message is not the target service message, the central UPF processes the target service message and then transmits it to the central UPF of the opposite user through the IMS. It does not use the local UPF for processing and does not report to the SMF.

[0070] In this embodiment, the method of identifying the service message that meets the preset conditions and obtaining the target service message includes: identifying whether the target packet data network address of the service message matches the packet data network address in the detection rule PDR; if they match, determining that the service message is the target service message.

[0071] The detection rules of the central UPF are sent by the SMF and are specially constructed for newly added messages that can be processed by the local UPF to identify this type of business message.

[0072] The PDN (Packet Data Network) address in the detection rule PDR indicates the service type. Different service types correspond to different PDN (Packet Data Network) addresses. This embodiment matches the PDN in the detection rule PDR with the PDN address in the service message. If the match is successful, it is determined that the service message is a new service message that can be processed by the local UPF (a service message that is not related to the opposite user).

[0073] If there is no match, it means that the service message is not a new one and can be processed by the local UPF. In this case, it will not be reported to the SMF and will be transmitted to the central UPF of the other end user through the ISM. Or if it is other types, other methods will be used for processing.

[0074] Step S309: The central UPF reports the target service message to the SMF.

[0075] In one embodiment, when the central UPF determines that the message is a service that is not related to the peer user, it indicates to the SMF that there is a service request that does not require interaction with the peer, and notifies the SMF to execute the local diversion strategy.

[0076] Step S310: The SMF receives the target service message reported by the central UPF and selects a local UPF to process the target service message.

[0077] This embodiment needs to reselect the local UPF based on the diversion service rules corresponding to the previously cached target service message, and decide whether to insert the PSA for the current target service message of VoNR+.

[0078] In this embodiment, the SMF selects a matching local UPF according to the pre-stored diversion service rules and the data network interface identifier Dnai of the processing rule to be installed.

[0079] Step S311: SMF initiates a user plane update request and notifies the central UPF to apply for an N9 tunnel.

[0080] The central UPF establishes an N9 tunnel between the central UPF and the selected local UPF according to the user plane update request to achieve communication. After the central UPF establishes the N9 tunnel, it notifies the SMF.

[0081] Step S312: SMF initiates a user plane establishment request, notifies the local UPF to allocate relevant resources, and installs target service message processing rules.

[0082] The SMF initiates a user plane establishment request to the selected local UPF. The local UPF allocates the resources required for the target service message based on the user plane establishment request, and then installs rules related to the VoNR+ service (target service message) in the local UPF. In this way, the local UPF can directly process the target service based on the installed service message processing rules without transferring it to the IMS, optimizing the message transmission path, reducing the data messages transferred to the IMS, and reducing the load on the IMS.

[0083] After the local UPF installs the target business message processing rules, it feeds back the installation completion information to the SMF.

[0084] Step S313: The SMF initiates a user plane update request to the central UPF, and the central UPF updates the downlink address to point to the ULCL.

[0085] Based on the local UPF installation completion information, the SMF initiates a user plane update request to the central UPF. The central UPF updates the downlink address to point to the forward ULCL. In this way, in this call request, the original VoNR voice and video packets are transferred to the IMS and transmitted to the peer user. However, the target service packets unrelated to the peer user are diverted to the local UPF for processing. After processing by the local UPF, they are directly output to the user terminal through the ULCL without passing through the IMS and the peer user.

[0086] Step S314: Notify the UE to install the diversion rule.

[0087] After the diversion rules are installed, all subsequent transmissions of target business messages in this call can be directly diverted without going through the ISM and large network UPF.

[0088] In one embodiment, the above steps are the process of establishing diversion rules when the target service message is received for the first time during this call. When the target service message is identified in the subsequent service message, it is directly processed by the local UPF and then sent to the user terminal by ULCL.

[0089] In this embodiment, SMF can apply for local UPF resources in real time according to the actual needs of VoNR+, and optimize the user's data transmission path to improve the call quality.

[0090] In this embodiment, some business scenarios bypass the IMS and large network UPF to provide faster call response and improve the user's VoNR+ service experience.

[0091] Referring to Figure 4, which is a flow chart of another embodiment of the call service processing method of the present application, this embodiment illustrates a method for processing another type of service message newly added to the call service, such as diverting the newly added service message to the local server for formatting, and then transmitting it to the peer user through the IMS and the large network UPF. The service message with optimized format can reduce the amount of data transmitted in the IMS and the large network UPF, reduce IMS load, avoid the impact of the newly added VoNR+ data channel service on the original voice and video service, and improve the call quality.

[0092] In this embodiment, the call service processing method includes:

[0093] Step S401: The UE has completed going online and is in an online state.

[0094] The user terminal has completed going online and is in an online state. At this time, the user terminal can initiate a call request, or the user terminal can receive a call request.

[0095] Step S402: A local UPF capable of processing VoNR+ services registers with the UM.

[0096] VoNR+ services include the existing VoNR voice services and new services compared to the existing VoNR voice services. Because VoNR+ new calls support more application scenarios, when a VoNR+ call is established, in addition to the existing VoNR voice services, services for other application scenarios are also available.

[0097] In one embodiment, the 5G communication architecture includes both local UPFs and large-network UPFs. The local UPFs have the ability to process certain services (i.e., enforce service message rules), such as translation and intelligent customer service Q&A, without requiring processing by the large-network UPF. Therefore, after a user terminal goes online, the local UPF registers with the UM, indicating its processing capabilities. For example, a field "Capability: Local service processing" is added to the N4 PFCP Association Setup Req message. This allows the UM to record the service processing capabilities of each local UPF.

[0098] In one embodiment, different local UPFs have different service processing capabilities, and the corresponding service processing capabilities are marked according to the service types to be processed. In this way, the local UPF can be selected based on the service type that matches the processing capability reported by the local UPF.

[0099] Step S403: The user terminal initiates a VoNR+ call request, and the IMS initiates the entire VoNR+ service process.

[0100] When the user terminal initiates a VoNR+ call request, the VoNR+ service process is started. Before any service message is transmitted, the rules for identifying service messages are established, that is, the detection rules for service messages are established to establish a processing environment for the local UPF to process service messages.

[0101] Step S404: PCF issues the policy to SMF;

[0102] Because the call request is a VoNR+ call request, which includes the existing VoNR voice service and services in other application scenarios, the policy issued by the PFC includes policies related to accessing the VoNR voice service and policies related to accessing the newly added VoNR+ services.

[0103] After the user terminal initiates a call request, the PCF (Policy Control Function Network Element) issues a policy for the call request, and further determines a processing rule for the call request.

[0104] Step S405: The SMF responds to the policy issued by the PCF.

[0105] In this embodiment, the SMF responds to the policy issued by the PCF and identifies the IMS (IP Multimedia Subsystem) session to determine whether the IMS session includes a request for a new service.

[0106] If the IMS session includes a request for a new service, the data network interface identifier (Dnai) in the policy rule is used to identify whether the call involves the new service. In this embodiment, a new service message having model characteristics (characteristic model) and capable of being extracted for compression and decompression is configured as a target service message. This service message is configured as a service message that can be processed by a local server, wherein the processing method is to format the service message. For example, if the service message is an uplink message, the service message is compressed; if the service message is a downlink message, the service message is decompressed.

[0107] In this embodiment, SMF determines whether the rules of the target business message are involved by identifying the rules of the call request. If so, it determines that some business messages in the call can be diverted to the local server and processed by the local server.

[0108] In one embodiment, when it is determined that there is a target service message, the SMF first combines the processing capabilities of the local UPF reported when the local UPF registers with the UM, such as the ability to execute target service message rules, to determine the local UPF that can locally process the target service message, and selects the local UPF to process the newly added target service message in the call.

[0109] If the pre-stored local UPF has the ability to execute the diversion business rules of the target business message, the diversion business rules are cached so that when there are subsequent business messages, the diversion business rules are used to locally process the business messages.

[0110] In this embodiment, if the UPF with processing capabilities reported by the local UPF does not include the processing capabilities to process the target business message, that is, the pre-stored local UPF does not have the ability to execute the diversion business rules of the target business message, then this embodiment can also create a local UPF that can process the target business message according to the requirements of the target business message.

[0111] Alternatively, for uplink triggered services, you can consider establishing ULCL after it is triggered when the user has an uplink message, that is, inserting the local UPF on demand. That is, the uplink message is relatively random and diverse, so you can create a local UPF that can process the message according to the needs of the target service message.

[0112] When the SMF determines that the system has a local UPF that can process the target service message, it caches the diversion rules of the target service message (in this embodiment, the diversion service rule refers to the rule for processing the service message, which is defined as a diversion rule because it can be diverted from other voice message services).

[0113] In one embodiment, the SMF also constructs a detection rule for the diversion service rule, which is used to identify the type of service message transmitted during the call, and then triggers the selection of local UPF processing or transmission to the large network UPF (central UPF) for processing.

[0114] Step S406: SMF initiates a user plane update request and notifies the central UPF to install the detection rules.

[0115] After the SMF constructs the detection rule for the offload service rule, it sends a user plane update message to the central UPF, so that the central UPF can update the user plane function of the central UPF. The update request carries the detection rule constructed in step S405. The central UPF installs the detection rule and responds to the SMF with the installation result and allocated resource information.

[0116] Step S407: The UE initiates a service (such as intelligent translation, intelligent customer service, etc.).

[0117] The user terminal initiates a service and generates a service message.

[0118] In this embodiment, VoNR+ calls include a variety of call scenarios, so there are also many types of service messages. For example, scenarios such as intelligent translation and intelligent customer service correspond to different message types than the original VoNR voice and video call scenarios.

[0119] Step S408: The message arrives at the central UPF through the base station, and the central UPF identifies the service message that meets the preset conditions and obtains the target service message.

[0120] When the central UPF receives a service message initiated by the UE, it identifies the type of the service message and determines whether it is a target service message. The target service message refers to the service message newly added to the VoNR+ call in this embodiment, and the service message meets the following conditions: it is a service message with preset model characteristics. In other words, when the central UPF detects that the service message belongs to a message that can be format converted according to the standard, it satisfies the preset conditions and is a service message with model characteristics.

[0121] If the service message is the target service message, the central UPF will report the service message to the SMF, and the SMF will select the local UPF to process the service message. After processing the target service message, it will be transferred to the IMS.

[0122] If the service message is not the target service message, the central UPF processes the target service message and then transmits it to the central UPF of the opposite user through the IMS. It does not use the local UPF for processing and does not report to the SMF.

[0123] In this embodiment, the method of identifying the service message that meets the preset conditions and obtaining the target service message includes: identifying whether the target packet data network address of the service message matches the packet data network address in the detection rule PDR; if they match, determining that the service message is the target service message.

[0124] The detection rules of the central UPF are sent by the SMF and are specially constructed for newly added messages that can be processed by the local UPF to identify this type of business message.

[0125] The PDN (Packet Data Network) address in the detection rule PDR indicates the service type. Different service types correspond to different PDN (Packet Data Network) addresses. This embodiment matches the PDN in the detection rule PDR with the PDN address in the service message. If the match is successful, it is determined that the service message is a new service message (a service message with preset model characteristics) that can be processed by the local UPF.

[0126] If there is no match, it means that the service message is not a new one and can be processed by the local UPF. In this case, it will not be reported to the SMF and will be transmitted to the central UPF of the other end user through the ISM. Or if it is other types, other methods will be used for processing.

[0127] Step S409: The central UPF reports the target service message to the SMF.

[0128] In one embodiment, when the central UPF determines that the message is a message with preset model characteristics, it indicates to the SMF that the message needs to be decompressed by the local UPF and notifies the SMF to execute the local diversion strategy.

[0129] Step S410: The SMF receives the target service message reported by the central UPF and selects a local UPF to process the target service message.

[0130] In one embodiment, this embodiment needs to reselect the local UPF based on the diversion service rules corresponding to the target service message previously cached, and decide whether to insert the PSA for the current target service message of VoNR+.

[0131] In this embodiment, the SMF selects a matching local UPF according to the pre-stored diversion service rules and the data network interface identifier Dnai of the processing rule to be installed.

[0132] Step S411: SMF initiates a user plane update request and notifies the central UPF to apply for an N9 tunnel.

[0133] The central UPF establishes an N9 tunnel between the central UPF and the selected local UPF according to the user plane update request to achieve communication. After the central UPF establishes the N9 tunnel, it notifies the SMF.

[0134] Step S412: SMF initiates a user plane establishment request, notifies the local UPF to allocate relevant resources, and installs target service message processing rules.

[0135] SMF initiates a user plane establishment request to the selected local UPF. The local UPF allocates the resources required for the target service message based on the user plane establishment request, and then installs the rules related to the VoNR+ service (target service message) in the local UPF for specific message diversion processing. In this way, the local UPF can directly process the target service based on the installed service message processing rules, and then transfer the processed message to the IMS. The local UPF is used to optimize the transmission data format, reduce the amount of data transmitted by the message in the IMS and the large network UPF, reduce the load on the IMS, and avoid the impact of the new VoNR+ data channel service on the existing voice and video services.

[0136] In this embodiment, the local UPF processes the target service message through compression and decompression. If the target service message is an uplink message (the local end is the sender), the local UPF compresses the target service message, which is then transferred to the IMS and transmitted to the peer user. If the target service message is a downlink message (the peer user is the initiator), the local UPF decompresses the target service message and then transmits it to the local user terminal via ULCL.

[0137] After the local UPF installs the target business message processing rules, it feeds back the installation completion information to the SMF.

[0138] Step S413: The SMF initiates a user plane update request to the central UPF, and the central UPF updates the downlink address to point to the forward ULCL.

[0139] Based on the local UPF installation completion information, the SMF initiates a user plane update request to the central UPF. The central UPF updates the downlink address to point to the forward ULCL. In this way, in this call request, the original VoNR voice and video packets are transferred to the IMS and transmitted to the peer user. However, the target service packets unrelated to the peer user are diverted to the local UPF for processing. After processing by the local UPF, they are directly output to the user terminal through the ULCL without passing through the IMS and the peer user.

[0140] Step S414: Notify the UE to install the diversion rule.

[0141] After the diversion rules are installed, all subsequent target business message transmissions during this call can be directly diverted and compressed or decompressed locally. The compressed message data occupies less data volume, which optimizes the data transmission during the call and improves the call quality.

[0142] In this embodiment, message data compression methods include, but are not limited to, redundancy compression and model-based (content-based and semantic-based) methods. In one embodiment, the model-based method defines the mapping between the source document set and the code subset before message transmission, so that a given message is always represented by the same codeword at any time within the document set. This embodiment is not limited to the compression methods listed above; other data compression and decompression technologies may also be used.

[0143] Please refer to Figure 5, which illustrates the transmission process of a data message after local compression in this embodiment. In this embodiment, during the data transmission process, the local UPF is first used to compress the data, and then the compressed data is transmitted along the data transmission path. Compared with the exemplary technology, the transmission of compressed message data in this embodiment can reduce the data volume, thereby reducing the data transmission load and improving transmission efficiency.

[0144] The application scenarios of all the above embodiments can be applied simultaneously in a single terminal or in different terminals. That is, a terminal can reduce the data transmission load by formatting and optimizing newly added service messages, or reduce the amount of data transmitted by locally processing service messages, thereby reducing the data transmission load. A terminal can also simultaneously perform formatting and optimization on service messages and locally process service messages.

[0145] Based on this, when the central user plane function (UPF) receives a service message initiated by a user equipment (UE), it identifies the service message that meets the preset conditions and obtains the target service message. If the target service message is not related to the peer user, the service message is optimized using the embodiment shown in Figure 3. If the target service message has the characteristics of the preset model, the service message is optimized using the embodiment shown in Figure 4.

[0146] The above-mentioned embodiments optimize the data path for new VoNR+ calls in 5G networks. When performing services that do not rely on the other terminal, the SMF identifies the service and selects a local UPF capable of handling it. This allows the data to be processed locally without passing through the IMS and large-network UPFs. This shortens the data transmission path, reducing the IMS load and improving the user experience. When the user's service data has certain model characteristics, the SMF determines and identifies the local UPF capable of performing data compression and decompression. This reduces the amount of data transmitted on the IMS, reducing the IMS load and minimizing the impact of new call services on basic voice and video calls.

[0147] Referring to Figure 6, which is a flow chart illustrating another embodiment of a call service processing method of the present application, this embodiment illustrates another method for processing a new service message in a call service, such as offloading new service messages in a roaming call scenario to local processing, thereby reducing the transmission of service messages during the call, thereby reducing the load on the IMS and the large network UPF, and improving call quality.

[0148] In this embodiment, the call service processing method includes:

[0149] Step S601: The UE initiates a request for an online process in a roaming scenario.

[0150] The user terminal has completed going online and is in an online state. At this time, the user terminal can initiate a call request, or the user terminal can receive a call request.

[0151] In one embodiment, in a roaming scenario, in a 5G architecture, an intermediate session management network element I-SMF is added to the anchor session management network element A-SMF, and roaming calls are implemented through the I-SMF.

[0152] Step S602: A local UPF capable of processing VoNR+ services registers with the UM.

[0153] VoNR+ services include the existing VoNR voice services and new services compared to the existing VoNR voice services. Because VoNR+ new calls support more application scenarios, when a VoNR+ call is established, in addition to the existing VoNR voice services, services for other application scenarios are also available.

[0154] In one embodiment, the 5G communication architecture includes both local UPFs and large-network UPFs. The local UPFs have the ability to process certain services (i.e., enforce service message rules), such as translation and intelligent customer service Q&A, without requiring processing by the large-network UPF. Therefore, after a user terminal goes online, the local UPF registers with the UM, indicating its processing capabilities. For example, a field "Capability: Local service processing" is added to the N4 PFCP Association Setup Req message. This allows the UM to record the service processing capabilities of each local UPF.

[0155] In one embodiment, different local UPFs have different service processing capabilities, and the corresponding service processing capabilities are marked according to the service types to be processed. In this way, the local UPF can be selected based on the service type that matches the processing capability reported by the local UPF.

[0156] Step S603: The user terminal initiates a VoNR+ call request, and the IMS initiates the entire VoNR+ service process.

[0157] When the user terminal initiates a VoNR+ call request, the VoNR+ service process is started. Before any service message is transmitted, the rules for identifying service messages are established, that is, the detection rules for service messages are established to establish a processing environment for the local UPF to process service messages.

[0158] Step S604: PCF sends the policy to SMF.

[0159] Because the call request is a VoNR+ call request, which includes the existing VoNR voice service and services in other application scenarios, the policy issued by the PFC includes policies related to accessing the VoNR voice service and policies related to accessing the newly added VoNR+ services.

[0160] After the user terminal initiates a call request, the PCF (Policy Control Function Network Element) issues a policy for the call request, and further determines a processing rule for the call request.

[0161] Step S605: The A-SMF receives the policy issued by the PCF, and notifies the I-SMF of the policy rules.

[0162] Step S606: The I-SMF responds to the policy issued by the A-SMF.

[0163] In this embodiment, the I-SMF responds to the policy issued by the PCF and identifies the IMS (IP Multimedia Subsystem) session to determine whether the IMS session includes a request for a new service.

[0164] If the IMS session includes a request for a new service, the data network interface identifier (Dnai) in the policy rule is used to identify whether the call involves the new service. In this embodiment, new services that are not related to the peer user are configured as target service messages, and new services that are not related to the peer user are configured as service messages that can be processed by the local server.

[0165] In this embodiment, the I-SMF determines whether the rules of the target business message are involved by identifying the call request. If so, it determines that some business messages in the call can be diverted to the local server and processed by the local server.

[0166] In one embodiment, when it is determined that there is a target service message, the I-SMF first combines the processing capabilities of the local UPF reported when the local UPF registers with the UM, such as the ability to execute target service message rules, to determine the local UPF that can locally process the target service message, and selects the local UPF to process the newly added target service message in the call.

[0167] If the pre-stored local UPF has the ability to execute the diversion business rules of the target business message, the diversion business rules are cached so that when there are subsequent business messages, the diversion business rules are used to locally process the business messages.

[0168] In this embodiment, if the UPF with processing capabilities reported by the local UPF does not include the processing capabilities to process the target business message, that is, the pre-stored local UPF does not have the ability to execute the diversion business rules of the target business message, then this embodiment can also create a local UPF that can process the target business message according to the requirements of the target business message.

[0169] Alternatively, for uplink triggered services, you can consider establishing ULCL after it is triggered when the user has an uplink message, that is, inserting the local UPF on demand. That is, the uplink message is relatively random and diverse, so you can create a local UPF that can process the message according to the needs of the target service message.

[0170] When the I-SMF determines that the system has a local UPF that can process the target service message, it caches the diversion rules of the target service message (in this embodiment, the diversion service rule refers to the rule for processing the service message, which is defined as a diversion rule because it can be diverted from other voice message services).

[0171] In one embodiment, the I-SMF also constructs a detection rule for the diversion service rule, which is used to identify the type of service message transmitted during the call, and then triggers the selection of local UPF processing or transmission to the large network UPF (central UPF) for processing.

[0172] Step S607: The I-SMF initiates a user plane update request and notifies the central UPF to install the detection rules.

[0173] After constructing the detection rules for the offload service rules, the I-SMF sends user plane update information to the central UPF for the central UPF to update the user plane function of the central UPF. The update request carries the detection rules constructed in step S606. The central UPF installs the detection rules and responds to the I-SMF with the installation results and allocated resource information.

[0174] Step S608: The UE initiates a service (such as intelligent translation, intelligent customer service, etc.).

[0175] The user terminal initiates a service and generates a service message.

[0176] In this embodiment, VoNR+ calls include a variety of call scenarios, so there are also many types of service messages. For example, scenarios such as intelligent translation and intelligent customer service correspond to different message types than the original VoNR voice and video call scenarios.

[0177] Step S609: The message arrives at the central UPF through the base station. The central UPF identifies the service message that meets the preset conditions and obtains the target service message.

[0178] When the central UPF receives a service message initiated by the UE, it identifies the type of the service message and determines whether it is a target service message. The target service message refers to the service message newly added to the VoNR+ call in this embodiment, and the service message meets the following conditions: a service message that is not related to the opposite user.

[0179] If the service message is a target service message, the central UPF reports the service message to the I-SMF, and the I-SMF selects a local UPF to process the service message.

[0180] If the service message is not the target service message, the central UPF processes the target service message and then transmits it to the central UPF of the peer user through the IMS. It does not use the local UPF for processing and does not report to the I-SMF.

[0181] In this embodiment, the method of identifying the service message that meets the preset conditions and obtaining the target service message includes: identifying whether the target packet data network address of the service message matches the packet data network address in the detection rule PDR; if they match, determining that the service message is the target service message.

[0182] The detection rules of the central UPF are sent by the I-SMF and are specially constructed for newly added messages that can be processed by the local UPF. They are used to identify this type of business message.

[0183] The PDN (Packet Data Network) address in the detection rule PDR indicates the service type. Different service types correspond to different PDN (Packet Data Network) addresses. This embodiment matches the PDN in the detection rule PDR with the PDN address in the service message. If the match is successful, it is determined that the service message is a new service message that can be processed by the local UPF (a service message that is not related to the opposite user).

[0184] If there is no match, it means that the service message is not a new one and can be processed by the local UPF. In this case, it will not be reported to the SMF and will be transmitted to the central UPF of the other end user through the ISM. Or if it is other types, other methods will be used for processing.

[0185] Step S610: The central UPF reports the target service message to the I-SMF.

[0186] In one embodiment, when the central UPF determines that the message is a service unrelated to the peer user, it indicates to the I-SMF that there is a service request that does not require interaction with the peer, and notifies the SMF to execute the local diversion strategy.

[0187] Step S611: The I-SMF receives the target service message reported by the central UPF and selects a local UPF to process the target service message.

[0188] This embodiment needs to reselect the local UPF based on the diversion service rules corresponding to the previously cached target service message, and decide whether to insert the PSA for the current target service message of VoNR+.

[0189] In this embodiment, the I-SMF selects a matching local UPF according to the pre-stored offload service rules and the data network interface identifier Dnai of the processing rule to be installed.

[0190] Step S612: I-SMF initiates a user plane update request and sets up a private network UPF.

[0191] The central UPF establishes an N9 tunnel between the central UPF and the selected local UPF based on the user plane update request to achieve communication. After the central UPF establishes the N9 tunnel, it notifies the I-SMF.

[0192] Step S613: The I-SMF initiates a user plane update request, and the central UPF updates the downlink address to point to the forward ULCL.

[0193] Based on the local UPF installation completion information, the I-SMF initiates a user plane update request to the central UPF. The central UPF updates the downlink address to point to the forward ULCL. In this way, in this call request, the original VoNR voice and video packets are transferred to the IMS and transmitted to the peer user. However, the target service packets unrelated to the peer user are diverted to the local UPF for processing. After processing by the local UPF, they are directly output to the user terminal through the ULCL without passing through the IMS and the peer user.

[0194] Step S614: Notify the UE to install the diversion rule.

[0195] After the diversion rules are installed, all subsequent transmissions of target business messages in this call can be directly diverted without going through the ISM and large network UPF.

[0196] The above steps are the process of establishing diversion rules when the target service message is received for the first time during this call. When the target service message is identified in the subsequent service message, it is directly processed by the local UPF and then sent to the user terminal by ULCL.

[0197] In this embodiment, I-SMF can apply for local UPF resources in real time according to the actual needs of VoNR+, and optimize the user's data transmission path to improve the call quality.

[0198] In this embodiment, some business scenarios bypass the IMS and large network UPF to provide faster call response and improve the user's VoNR+ service experience.

[0199] Referring to Figure 7, which is a flow chart of another embodiment of the call service processing method of the present application, this embodiment illustrates another method for processing another type of service message newly added to the call service. For example, the newly added service message in the roaming call scenario is diverted to the local server for formatting processing, and then transmitted to the peer user through the IMS and the large network UPF. The service message with optimized format can reduce the amount of data transmitted in the IMS and the large network UPF, reduce IMS load, avoid the impact of the newly added VoNR+ data channel service on the original voice and video service, and improve the call quality.

[0200] In this embodiment, the call service processing method includes:

[0201] Step S701: The user initiates a request for an online process of a roaming scenario.

[0202] The user terminal has completed going online and is in an online state. At this time, the user terminal can initiate a call request, or the user terminal can receive a call request.

[0203] In one embodiment, in a roaming scenario, in a 5G architecture, an intermediate session management network element I-SMF is added to the anchor session management network element A-SMF, and roaming calls are implemented through the I-SMF.

[0204] Step S702: A local UPF capable of processing VoNR+ services registers with the UM.

[0205] VoNR+ services include the existing VoNR voice services and new services compared to the existing VoNR voice services. Because VoNR+ new calls support more application scenarios, when a VoNR+ call is established, in addition to the existing VoNR voice services, services for other application scenarios are also available.

[0206] In one embodiment, the 5G communication architecture includes both local UPFs and large-network UPFs. The local UPFs have the ability to process certain services (i.e., enforce service message rules), such as translation and intelligent customer service Q&A, without requiring processing by the large-network UPF. Therefore, after a user terminal goes online, the local UPF registers with the UM, indicating its processing capabilities. For example, a field "Capability: Local service processing" is added to the N4 PFCP Association Setup Req message. This allows the UM to record the service processing capabilities of each local UPF.

[0207] In one embodiment, different local UPFs have different service processing capabilities, and the corresponding service processing capabilities are marked according to the service types to be processed. In this way, the local UPF can be selected based on the service type that matches the processing capability reported by the local UPF.

[0208] For example, a UPF capable of processing VoNR+ service data compression and data decompression registers with the UM and indicates that the local UPF has the data compression and data decompression capabilities.

[0209] Step S703: The user terminal initiates a VoNR+ call request, and the IMS initiates the entire VoNR+ service process.

[0210] When the user terminal initiates a VoNR+ call request, the VoNR+ service process is started. Before any service message is transmitted, the rules for identifying service messages are established, that is, the detection rules for service messages are established to establish a processing environment for the local UPF to process service messages.

[0211] Step S704: PCF issues the policy to SMF;

[0212] Because the call request is a VoNR+ call request, which includes the existing VoNR voice service and services in other application scenarios, the policy issued by the PFC includes policies related to accessing the VoNR voice service and policies related to accessing the newly added VoNR+ services.

[0213] Step S705: The A-SMF receives the policy issued by the PCF, and notifies the I-SMF of the policy rules.

[0214] Step S706: The I-SMF responds to the policy issued by the A-SMF.

[0215] In this embodiment, the I-SMF responds to the policy issued by the PCF and identifies the IMS (IP Multimedia Subsystem) session to determine whether the IMS session includes a request for a new service.

[0216] If the IMS session includes a request for a new service, the data network interface identifier (Dnai) in the policy rule is used to identify whether the call involves the new service. In this embodiment, a new service message having model characteristics (characteristic model) and capable of being extracted for compression and decompression is configured as a target service message. This service message is configured as a service message that can be processed by a local server, wherein the processing method is to format the service message. For example, if the service message is an uplink message, the service message is compressed; if the service message is a downlink message, the service message is decompressed.

[0217] In this embodiment, the I-SMF determines whether the rules of the target business message are involved by identifying the call request. If so, it determines that some business messages in the call can be diverted to the local server and processed by the local server.

[0218] In one embodiment, when it is determined that there is a target service message, the I-SMF first combines the processing capabilities of the local UPF reported when the local UPF registers with the UM, such as the ability to execute target service message rules, to determine the local UPF that can locally process the target service message, and selects the local UPF to process the newly added target service message in the call.

[0219] If the pre-stored local UPF has the ability to execute the diversion business rules of the target business message, the diversion business rules are cached so that when there are subsequent business messages, the diversion business rules are used to locally process the business messages.

[0220] In this embodiment, if the UPF with processing capabilities reported by the local UPF does not include the processing capabilities to process the target business message, that is, the pre-stored local UPF does not have the ability to execute the diversion business rules of the target business message, then this embodiment can also create a local UPF that can process the target business message according to the requirements of the target business message.

[0221] Alternatively, for uplink triggered services, you can consider establishing ULCL after it is triggered when the user has an uplink message, that is, inserting the local UPF on demand. That is, the uplink message is relatively random and diverse, so you can create a local UPF that can process the message according to the needs of the target service message.

[0222] When the I-SMF determines that the system has a local UPF that can process the target service message, it caches the diversion rules of the target service message (in this embodiment, the diversion service rule refers to the rule for processing the service message, which is defined as a diversion rule because it can be diverted from other voice message services).

[0223] In one embodiment, the I-SMF also constructs a detection rule for the diversion service rule, which is used to identify the type of service message transmitted during the call, and then triggers the selection of local UPF processing or transmission to the large network UPF (central UPF) for processing.

[0224] Step S707: The I-SMF initiates a user plane update request and notifies the central UPF to install the detection rules.

[0225] After constructing the detection rules for the offload service rules, the I-SMF sends user plane update information to the central UPF for the central UPF to update the user plane function of the central UPF. The update request carries the detection rules constructed in step S706. The central UPF installs the detection rules and responds to the I-SMF with the installation results and allocated resource information.

[0226] Step S708: The UE initiates a service (such as intelligent translation, intelligent customer service, etc.).

[0227] The user terminal initiates a service and generates a service message.

[0228] In this embodiment, VoNR+ calls include a variety of call scenarios, so there are also many types of service messages. For example, scenarios such as intelligent translation and intelligent customer service correspond to different message types than the original VoNR voice and video call scenarios.

[0229] Step S709: The message arrives at the central UPF through the base station. The central UPF identifies the service message that meets the preset conditions and obtains the target service message.

[0230] When the central UPF receives a service message initiated by the UE, it identifies the type of the service message and determines whether it is a target service message. The target service message refers to the service message newly added to the VoNR+ call in this embodiment, and the service message meets the following conditions: it is a service message with preset model characteristics. In other words, when the central UPF detects that the service message belongs to a message that can be format converted according to the standard, it satisfies the preset conditions and is a service message with model characteristics.

[0231] If the service message is the target service message, the central UPF will report the service message to the I-SMF, and the I-SMF will select the local UPF to process the service message. After processing the target service message, it will be transferred to the IMS.

[0232] If the service message is not the target service message, the central UPF processes the target service message and then transmits it to the central UPF of the peer user through the IMS. It does not use the local UPF for processing and does not report to the I-SMF.

[0233] In this embodiment, the method of identifying the service message that meets the preset conditions and obtaining the target service message includes: identifying whether the target packet data network address of the service message matches the packet data network address in the detection rule PDR; if they match, determining that the service message is the target service message.

[0234] The detection rules of the central UPF are sent by the I-SMF and are specially constructed for newly added messages that can be processed by the local UPF. They are used to identify this type of business message.

[0235] The PDN (Packet Data Network) address in the detection rule PDR indicates the service type. Different service types correspond to different PDN (Packet Data Network) addresses. This embodiment matches the PDN in the detection rule PDR with the PDN address in the service message. If the match is successful, it is determined that the service message is a new service message (a service message with preset model characteristics) that can be processed by the local UPF.

[0236] If there is no match, it means that the service message is not a new one and can be processed by the local UPF. In this case, it will not be reported to the I-SMF and will be transmitted to the central UPF of the other end user through the ISM. Or if it is of other types, other methods will be used for processing.

[0237] Step S710: The central UPF reports the target service message to the I-SMF.

[0238] In one embodiment, when the central UPF determines that the message is a message with preset model characteristics, it indicates to the I-SMF that there is a message that needs to be decompressed by the local UPF and notifies the I-SMF to execute the local diversion strategy.

[0239] Step S711: The I-SMF receives the target service message reported by the central UPF and selects a local UPF to process the target service message.

[0240] In one embodiment, this embodiment needs to reselect the local UPF based on the diversion service rules corresponding to the target service message previously cached, and decide whether to insert the PSA for the current target service message of VoNR+.

[0241] In this embodiment, the I-SMF selects a matching local UPF according to the pre-stored offload service rules and the data network interface identifier Dnai of the processing rule to be installed.

[0242] Step S712: The I-SMF initiates a user plane update request (IUPF and ULCL are the same UPF).

[0243] In one embodiment, the user plane update request requests the local UPF to install diversion rules for compressing or decompressing data.

[0244] I-SMF initiates a user plane establishment request to the selected local UPF. The local UPF allocates the resources required for the target service message based on the user plane establishment request, and then installs rules related to the VoNR+ service (target service message) in the local UPF for specific message diversion processing. In this way, the local UPF can directly process the target service based on the installed service message processing rules, and then transfer the processed message to the IMS. The local UPF is used to optimize the transmission data format, reduce the amount of data transmitted by the message in the IMS and the large network UPF, reduce the load on the IMS, and avoid the impact of the new VoNR+ data channel service on the existing voice and video services.

[0245] In this embodiment, the local UPF processes the target service message through compression and decompression. If the target service message is an uplink message (the local end is the sender), the local UPF compresses the target service message, which is then transferred to the IMS and transmitted to the peer user. If the target service message is a downlink message (the peer user is the initiator), the local UPF decompresses the target service message and then transmits it to the local user terminal via ULCL.

[0246] After the local UPF installs the target business message processing rules, it feeds back the installation completion information to the SMF.

[0247] Step S713: SMF initiates a user plane establishment request (IUP and ULCL are not the same UPF).

[0248] SMF initiates a user plane establishment request and recommends I-UPF. The I-SMF subsequent timer deletes the IUPF.

[0249] Based on the local UPF installation completion information, the SMF initiates a user plane update request to the central UPF. The central UPF updates the downlink address to point to the forward ULCL. In this way, in this call request, the original VoNR voice and video packets are transferred to the IMS and transmitted to the peer user. However, the target service packets unrelated to the peer user are diverted to the local UPF for processing. After processing by the local UPF, they are directly output to the user terminal through the ULCL without passing through the IMS and the peer user.

[0250] Step S714: Notify the UE to install the diversion rules and complete the subsequent process.

[0251] After the diversion rules are installed, all subsequent target business message transmissions during this call can be directly diverted and compressed or decompressed locally. The compressed message data occupies less data volume, which optimizes the data transmission during the call and improves the call quality.

[0252] At this point, the I-SMF can identify the user's service characteristics based on the user's VoNR+ service needs, and use the local UPF in real time to optimize the transmitted data format, reducing the amount of data transmitted between the home UPF, IMS, and large network UPF. This application can reduce the IMS load, avoid the impact of the new VoNR+ data channel service on the existing voice and video services, and also improve the user experience;

[0253] Please refer to Figure 8, which illustrates the transmission process of a data message after local compression in this embodiment. In this embodiment, during the data transmission process, the local UPF is first used to compress the data, and then the compressed data is transmitted along the data transmission path. Compared with the exemplary technology, the transmission of compressed message data in this embodiment can reduce the data volume, thereby reducing the data transmission load and improving transmission efficiency.

[0254] The above examples are only for reference. In order to avoid redundancy, they will not be listed one by one here. In actual development or application, they can be flexibly combined according to actual needs, but any combination belongs to the technical solution of this application and is covered within the scope of protection of this application.

[0255] The present application also provides a call service processing system, including:

[0256] processor;

[0257] A storage device stores a program thereon, and when the program is executed by the processor, the processor implements the method for processing the call service described in any one of the above embodiments.

[0258] The present application also provides a call service processing device, including:

[0259] one or more processors;

[0260] A storage device stores one or more programs thereon, and when the one or more programs are executed by the one or more processors, the one or more processors implement the method for processing the call service described in any of the above embodiments.

[0261] The present application also provides a computer-readable storage medium, on which a processing program is stored. When the processing program is executed by a processor, the steps of the processing method in any of the above embodiments are implemented.

[0262] In the embodiments of the communication device and computer-readable storage medium provided in this application, all technical features of any of the above-mentioned processing method embodiments may be included. The expanded and explained contents of the specification are basically the same as those of the embodiments of the above-mentioned methods and will not be repeated here.

[0263] An embodiment of the present application further provides a computer program product, which includes computer program code. When the computer program code runs on a computer, the computer is enabled to execute the methods in the above various possible implementation modes.

[0264] The above scenarios are merely examples and do not limit the application scenarios of the technical solutions provided in the embodiments of this application. The technical solutions of this application can also be applied to other scenarios. For example, those skilled in the art will appreciate that, with the evolution of system architecture and the emergence of new business scenarios, the technical solutions provided in the embodiments of this application are equally applicable to similar technical problems.

[0265] The serial numbers of the above embodiments of the present application are for description only and do not represent the advantages or disadvantages of the embodiments.

[0266] The steps in the method of the embodiment of the present application can be adjusted in order, combined and deleted according to actual needs.

[0267] The units in the device of the embodiment of the present application can be merged, divided and deleted according to actual needs.

[0268] In this application, the same or similar terminology, technical solutions and / or application scenario descriptions are generally only described in detail the first time they appear. When they appear again later, they are generally not repeated for the sake of brevity. When understanding the technical solutions and other contents of this application, for the same or similar terminology, technical solutions and / or application scenario descriptions that are not described in detail later, you can refer to the previous relevant detailed descriptions.

[0269] In this application, the description of each embodiment has its own focus. For parts that are not described or recorded in detail in a certain embodiment, please refer to the relevant description of other embodiments.

[0270] The various technical features of the technical solution of this application can be combined arbitrarily. In order to make the description concise, not all possible combinations of the various technical features in the above embodiments are described. However, as long as there is no contradiction in the combination of these technical features, they should be considered to be within the scope of this application.

[0271] Through the description of the above implementation methods, those skilled in the art can clearly understand that the above-mentioned embodiment methods can be implemented by means of software plus the necessary general hardware platform, and of course can also be implemented by hardware, but in many cases the former is a better implementation method. Based on this understanding, the technical solution of the present application is essentially or the part that contributes to the prior art can be embodied in the form of a software product, which is stored in a storage medium (such as ROM / RAM, magnetic disk, optical disk) as mentioned above, and includes a number of instructions for enabling a terminal device (which can be a mobile phone, computer, server, controlled terminal, or network device, etc.) to execute the method of each embodiment of the present application.

[0272] In the above embodiments, it can be implemented in whole or in part by software, hardware, firmware or any combination thereof. When software is used for implementation, it can be implemented in whole or in part in the form of a computer program product. The computer program product includes one or more computer instructions. When the computer program instructions are loaded and executed on a computer, the process or function according to the embodiment of the present application is generated in whole or in part. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device. The computer instructions can be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another computer-readable storage medium. For example, the computer instructions can be transmitted from one website, computer, server or data center to another website, computer, server or data center via a wired (e.g., coaxial cable, optical fiber, digital subscriber line) or wireless (e.g., infrared, wireless, microwave, etc.) method. The computer-readable storage medium can be any available medium that a computer can access or a data storage device such as a server or data center that includes one or more available media integrations. The available medium can be a magnetic medium (e.g., a floppy disk, a storage disk, a tape), an optical medium (e.g., a DVD), or a semiconductor medium (e.g., a solid-state storage disk Solid State Disk (SSD)).

[0273] The above are merely optional embodiments of the present application and do not limit the patent scope of the present application. Any equivalent structure or equivalent process transformation made using the contents of the present application specification and drawings, or directly or indirectly applied in other related technical fields, are also included in the patent protection scope of the present application.

Claims

1. A method for processing a call service, wherein: The method comprises: When the central user plane function network element center UPF receives a service message initiated by the user equipment UE, it identifies the service message that meets the preset conditions and obtains the target service message; The central UPF reports the target service message to the session management network element SMF; The SMF receives the target service message reported by the central UPF and selects a local UPF to process the target service message.

2. The method for processing call service according to claim 1, wherein: The service messages that meet the preset conditions include at least one of the following: Business messages that are not related to the peer user; Business messages with preset model characteristics.

3. The method for processing call service according to claim 1, wherein: The step of identifying a service message that meets a preset condition and obtaining a target service message comprises: Identify whether the target packet data network address of the service message matches the packet data network address in the detection rule PDR; If there is a match, it is determined that the service message is the target service message.

4. The method for processing call service according to claim 1, wherein: When the target service message reported by the SMF receiving center UPF is a service message unrelated to the opposite user, the step of selecting a local UPF to process the target service message includes: The SMF selects a local UPF to allocate resources based on pre-stored diversion business rules and installs target business message processing rules.

5. The method for processing call service as claimed in claim 4, wherein: The SMF selects a local UPF to allocate resources according to the pre-stored diversion service rules, and installs the target service message processing rules, including: The SMF selects a matching local UPF according to the pre-stored diversion service rules and the data network interface identifier Dnai of the processing rules to be installed; The local UPF allocates the required resources of the target service message and installs the processing rules of the target service message.

6. The method for processing call service according to claim 1, wherein: When the target service message reported by the SMF receiving center UPF is a service message having a preset model feature, the step of selecting a local UPF to process the target service message includes: The SMF selects a local UPF to format the target service message according to the pre-stored diversion service rules.

7. The method for processing call service as claimed in claim 6, wherein: The step of the SMF selecting a local UPF to format the target service message according to the pre-stored diversion service rule includes: The SMF selects a matching local UPF according to the pre-stored diversion service rules; The local UPF compresses or decompresses the target service message.

8. The method for processing call services according to any one of claims 1 to 7, wherein: When the central user plane function network element center UPF receives a service message initiated by the user equipment UE, before identifying the service message that meets the preset conditions and obtaining the target service message, it also includes: When the SMF receives a call establishment request, it constructs a detection rule; Initiate a user plane update request to the central UPF based on the detection rule; The central UPF installs the detection rule carried in the update request according to the update request, so that when the central UPF receives a service message sent by the user equipment UE, it detects whether the service message is a target service message based on the detection rule.

9. The method for processing call service as claimed in claim 8, wherein: When the SMF receives a call establishment request, the step of constructing a detection rule includes: When receiving a call establishment request, according to the policy corresponding to the call establishment request sent by the policy control function network element PCF to SMF, identify the diversion service rules in the policy, wherein when the call establishment request has a newly added service message irrelevant to the opposite user or a service message with a preset model feature, the policy includes the diversion service rules of the newly added service message; Determine whether the pre-stored local UPF has the ability to execute the diversion service rules, wherein the local UPF indicates the execution capability when registering with the SMF; When the pre-stored local UPF has the ability to execute the diversion service rule, the diversion service rule is cached and a detection rule for the diversion service rule is constructed.

10. The method for processing call service according to claim 9, wherein: Before the step of caching the diversion business rules, the method further includes: When the pre-stored local UPF does not have the ability to execute the diversion service rule, a local UPF is inserted according to the processing requirements of the diversion service rule.

11. The method for processing call service according to claim 9, wherein: When the call establishment request is received, the step of identifying the diversion service rule in the policy according to the policy corresponding to the call establishment request sent by the policy control function network element PCF to the SMF comprises: When the PCF receives the call establishment request, it sends the policy corresponding to the call establishment request to the anchor session management network element A-SMF; The A-SMF receives the policy and notifies the intermediate session management network element I-SMF of the policy; The I-SMF identifies the diversion service rules in the policy.

12. The method for processing call service according to claim 1, wherein: The SMF includes an intermediate session management network element I-SMF, and the step of reporting the target service message to the session management network element SMF includes: The central UPF reports the target service message to the I-SMF, so that the I-SMF selects a local I-UPF to process the target service message.

13. A method for processing a call service, wherein: The method comprises: The session management network element SMF receives the target service message reported by the central user plane function network element center UPF; Select a local UPF to process the target service message.

14. The method for processing call service according to claim 13, wherein: When the target service message reported by the SMF receiving center UPF is a service message unrelated to the opposite user, the step of selecting a local UPF to process the target service message includes: The SMF selects a matching local UPF according to the pre-stored diversion service rules and the data network interface identifier Dnai of the processing rules to be installed, and installs the target service message processing rules.

15. The method for processing call service according to claim 13, wherein: When the target service message reported by the SMF receiving center UPF is a service message having a preset model feature, the step of selecting a local UPF to process the target service message includes: The SMF selects a matching local UPF according to the pre-stored diversion service rules to format the target service message.

16. The method for processing call service according to claim 13, wherein: Before the step of the session management network element SMF receiving the target service message reported by the central user plane function network element center UPF, the step also includes: When the SMF receives a call establishment request, it constructs a detection rule; A user plane update request is initiated to the central UPF based on the detection rule.

17. The method for processing call service according to claim 16, wherein: When the SMF receives a call establishment request, the step of constructing a detection rule includes: When receiving a call establishment request and receiving a policy corresponding to the call establishment request issued by a policy control function network element PCF, identifying a diversion service rule in the policy, wherein when the call establishment request adds a service message irrelevant to the opposite end user or a service message with a preset model feature, the policy includes a diversion service rule for the newly added service message; Determine whether the pre-stored local UPF has the ability to execute the diversion service rules, wherein the local UPF indicates the execution capability when registering with the SMF; When the pre-stored local UPF has the ability to execute the diversion service rule, the diversion service rule is cached and a detection rule for the diversion service rule is constructed.

18. The method for processing call service according to claim 17, wherein: Before the step of caching the diversion business rules, the method further includes: When the pre-stored local UPF does not have the ability to execute the diversion service rule, a local UPF is inserted according to the processing requirements of the diversion service rule.

19. A method for processing a call service, wherein: The method comprises: When the central user plane function network element center UPF receives a service message initiated by the user equipment UE, it identifies the service message that meets the preset conditions and obtains the target service message; Report the target service message to the session management network element SMF.

20. The method for processing call service as claimed in claim 19, wherein: The service messages that meet the preset conditions include at least one of the following: Business messages that are not related to the peer user; Business messages with preset model characteristics.

21. The method for processing call service as claimed in claim 19, wherein: The step of identifying a service message that meets a preset condition and obtaining a target service message comprises: The central UPF identifies whether the target packet data network address of the service message matches the packet data network address in the detection rule PDR; If there is a match, it is determined that the service message is the target service message.

22. The method for processing call service as claimed in claim 19, wherein: When the central user plane function network element center UPF receives a service message initiated by the user equipment UE, before identifying the service message that meets the preset conditions and obtaining the target service message, it also includes: The central UPF receives the user plane update request initiated by the SMF, where the update request carries a detection rule; The central UPF installs the detection rules.

23. A call service processing system, wherein: The system comprises: processor; A storage device having a program stored thereon, when the program is executed by the processor, the processor implements the method for processing call services as described in any one of claims 1-12.

24. A call service processing device, wherein: The device comprises: one or more processors; A storage device having one or more programs stored thereon, wherein when the one or more programs are executed by the one or more processors, the one or more processors implement the method for processing call services as described in any one of claims 13-18, and / or 19-22.

25. A computer-readable storage medium, wherein: A computer processing program is stored, and the computer processing program is called by a processor to execute the method for processing call services according to any one of claims 1 to 22.

Images