EP3986027A1 - Procédé et appareil de communication, entité et support d'informations - Google Patents

Procédé et appareil de communication, entité et support d'informations Download PDF

Info

Publication number
EP3986027A1
EP3986027A1 EP20825559.6A EP20825559A EP3986027A1 EP 3986027 A1 EP3986027 A1 EP 3986027A1 EP 20825559 A EP20825559 A EP 20825559A EP 3986027 A1 EP3986027 A1 EP 3986027A1
Authority
EP
European Patent Office
Prior art keywords
function entity
scp
network
network function
network element
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Pending
Application number
EP20825559.6A
Other languages
German (de)
English (en)
Other versions
EP3986027A4 (fr
Inventor
Tao Wang
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Tencent Technology Shenzhen Co Ltd
Original Assignee
Tencent Technology Shenzhen Co Ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Tencent Technology Shenzhen Co Ltd filed Critical Tencent Technology Shenzhen Co Ltd
Publication of EP3986027A1 publication Critical patent/EP3986027A1/fr
Publication of EP3986027A4 publication Critical patent/EP3986027A4/fr
Pending legal-status Critical Current

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W24/00—Supervisory, monitoring or testing arrangements
    • H04W24/04—Arrangements for maintaining operational condition
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/06—Management of faults, events, alarms or notifications
    • H04L41/0654—Management of faults, events, alarms or notifications using network fault recovery
    • H04L41/0659—Management of faults, events, alarms or notifications using network fault recovery by isolating or reconfiguring faulty entities
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/06—Management of faults, events, alarms or notifications
    • H04L41/0654—Management of faults, events, alarms or notifications using network fault recovery
    • H04L41/0668—Management of faults, events, alarms or notifications using network fault recovery by dynamic selection of recovery network elements, e.g. replacement by the most appropriate element after failure
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/40—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks using virtualisation of network functions or resources, e.g. SDN or NFV entities
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L45/00—Routing or path finding of packets in data switching networks
    • H04L45/22—Alternate routing
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/50—Network services
    • H04L67/56—Provisioning of proxy services
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W28/00—Network traffic management; Network resource management
    • H04W28/02—Traffic management, e.g. flow control or congestion control
    • H04W28/08—Load balancing or load distribution
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/34—Reselection control
    • H04W36/38—Reselection control by fixed network equipment
    • H04W36/385—Reselection control by fixed network equipment of the core network
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W88/00—Devices specially adapted for wireless communication networks, e.g. terminals, base stations or access point devices
    • H04W88/18—Service support devices; Network management devices
    • H04W88/182—Network node acting on behalf of an other network entity, e.g. proxy
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W28/00—Network traffic management; Network resource management
    • H04W28/02—Traffic management, e.g. flow control or congestion control
    • H04W28/08—Load balancing or load distribution
    • H04W28/0827—Triggering entity
    • H04W28/0831—Core entity
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W28/00—Network traffic management; Network resource management
    • H04W28/02—Traffic management, e.g. flow control or congestion control
    • H04W28/08—Load balancing or load distribution
    • H04W28/088—Load balancing or load distribution among core entities

Definitions

  • This application relates to the technical field of communications, and in particular, to a communication technology between network function entities.
  • NF network function
  • NF service network function service
  • an NF network element/NF service module serving as a consumer directly communicates with an NF network element/NF service module serving as a producer. There is a relative relationship between the producer and the consumer. If a party A provides a service to a party B, the party A is a producer, and the party B is a consumer.
  • An indirect communication technology is introduced in R16. That is, the NF network element/NF service module serving as the consumer needs to communicate with the NF network element/NF service module serving as the producer via a service communication proxy (SCP) network element.
  • SCP service communication proxy
  • an SCP network element used by the NF network element/NF service module serving as the consumer is statically configured. If the statically configured SCP network element is invalid, indirect communication of the NF network element/NF service module serving as the consumer is invalid.
  • a communication method is provided according to embodiments of this application, to ensure that a first network function entity and a second network function entity can continually perform service communication in a case that an SCP network element used by the first network function entity to communicate with the second network function entity is invalid, thereby ensuring the service continuity and the reliability and availability of a system.
  • An apparatus, an entity, and a storage medium are further provided accordingly according to the embodiments of this application.
  • a communication method including:
  • a communication apparatus including: a communication module, a detection module, a returning module, and a switching module.
  • the communication module is configured to indirectly communicate with a second network function entity by using a first service communication proxy (SCP) network element.
  • the detection module is configured to detect a second SCP network element in a case that it is determined that the first SCP network element is invalid.
  • the returning module is configured to return to directly communicate with the second network function entity in a case that it is determined that the first SCP network element is invalid.
  • the switching module is configured to switch from the first SCP network element to the second SCP network element in a case that the detection module detects that the second SCP network element is valid.
  • the communication module is further configured to indirectly communicate with the second network function entity via the second SCP network element that is switched to by the switching module.
  • the returning module is further configured to return to directly communicate with the second network function entity in a case that the detection module detects that the second SCP network element is invalid.
  • the communication apparatus further includes a first selection module.
  • the first selection module is configured to select a third SCP network element, and select, in a case that the third SCP network element is invalid during selecting the second network function entity for the first network function entity, the first SCP network element to establish a communication connection between the first network function entity and the second network function entity.
  • the detection module may be further configured to: select N valid SCP network elements from configured M valid SCP network elements as the second SCP network elements, where M is an integer greater than 0, and N is an integer greater than 0 and less than or equal to M.
  • the detection module may include: a first transmission unit, and a first reception unit.
  • the first transmission unit is configured to transmit a first query request to a control function entity.
  • the first reception unit is configured to receive a first query response transmitted by the control function entity, the first query response includes information about M valid SCP network elements, M is an integer greater than 0.
  • the first selection module is further configured to select N valid SCP network elements from the M valid SCP network elements as the second SCP network elements, N is an integer greater than 0 and less than or equal to M.
  • the detection module may include: a second transmission unit and a second reception unit.
  • the second transmission unit is configured to transmit a second query request to a control function entity.
  • the second reception unit is configured to receive a second query response transmitted by the control function entity, the second query response is used for indicating absence of a valid SCP network element, the absence of a valid SCP network element represents that the second SCP network element is invalid.
  • the communication apparatus further includes a service allocation module.
  • the service allocation module is configured to perform service allocation among the N second SCP network elements according to load capacity information of each of the N second SCP network elements.
  • the service allocation module is further configured to adjust, in a case that Q second SCP network elements in the N second SCP network elements are invalid, the service allocation according to load capacity information of each of (N-Q) second SCP network elements, Q is an integer greater than 0 and less than N.
  • the first selection module is configured to select a second SCP network element from the N second SCP network elements to provide a service for a connected terminal.
  • the communication apparatus further includes: a transmission module.
  • the transmission module is configured to transmit, to the control function entity or a third network function entity, a first notification message indicating that the first SCP network element or the second SCP network element is invalid.
  • the communication apparatus further includes: a first reception module.
  • the first reception module is configured to receive, in a case that the first network function entity returns to directly communicate with the second network entity, a second notification message indicating that the first SCP network element is restored to be valid or the second SCP network element is restored to be valid.
  • the switching module is further configured to switch, in response to the second notification message, to indirectly communicate with the second network function entity via the first SCP network element or the second SCP network element.
  • the communication apparatus further includes: a second reception module and an addition module.
  • the second reception module is configured to receive, in a case that the first network function entity communicates with the second network function entity via the second SCP network element, a third notification message indicating that the first SCP network element is restored to be valid.
  • the addition module is configured to add the first SCP network element to a resource pool of candidate valid SCP network elements according to the third notification message.
  • a network function entity including: a communication interface, a processor, and a memory.
  • the memory is configured to store computer executable instructions.
  • the communication interface is configured to, when the network function entity operates, perform operations performed by the communication module according to the second aspect or any possible implementation of the second aspect.
  • the processor is configured to execute the computer executable instructions stored on the memory, to perform operations performed by the switching module according to the second aspect or any possible implementation of the second aspect.
  • a computer-readable storage medium which stores instructions.
  • the instructions when run on a computer, cause the computer to perform the method according to the first aspect.
  • a computer program product including instructions is provided.
  • the instructions when run on a computer, cause the computer to perform the method according to the first aspect.
  • the SCP network element used by the first network function entity to communicate with the second network function entity is invalid
  • another available SCP network element may be used for indirect communication or the first network function entity may return to directly communicate with the second network function entity. In this way, it can be ensured that the first network function entity can continually perform service communication with the second network function entity, thereby ensuring the service continuity and the reliability and availability of a system.
  • a communication method is provided according to embodiments of this application, to ensure that a first network function entity and a second network function entity can continually perform service communication in a case that an SCP network element used by the first network function entity to communicate with the second network function entity is invalid, thereby ensuring the service continuity and the reliability and availability of a system.
  • An apparatus, an entity, and a storage medium are further provided accordingly according to the embodiments of this application. Detailed descriptions are provided below.
  • FIG. 1 is a schematic diagram of a network architecture of a communication system according to an embodiment of this application.
  • the communication system provided in this embodiment of this application includes a first network function entity, a service communication proxy (SCP) network element, and a second network function entity.
  • the SCP network element may be a first SCP network element. That is, the first network function entity indirectly communicates with the second network function entity via the first SCP network element.
  • the first network function entity and the second network function entity may be network elements or modules that perform particular functions in an operator network, or may be NF network elements, or may be NF service modules.
  • the first network function entity or the second network function entity may include an access and mobility management function (AMF) network element, a session management function (SMF) network element, a user plane function (UPF) network element, a policy control function (PCF) network element, a unified data management (UDM) network element, a unified data repository (UDR) network element, an authentication server function (AUSF) network element, a network slice selection function (NSSF) network element, a network data analytics function (NWDAF) network element, or a network repository function (NRF) network element.
  • AMF access and mobility management function
  • SMF session management function
  • UPF user plane function
  • PCF policy control function
  • UDM unified data management
  • UDR unified data repository
  • AUSF authentication server function
  • NSSF network slice selection function
  • NWDAAF network data analytics function
  • NWDAF network data analytics function
  • the first network function entity or the second network function entity may be a function module providing services to the foregoing network elements, for example, an AMF service module, an SMF service module, a UPF service module, a PCF service module, a UDM service module, a UDR service module, an AUSF service module, an NSSF service module, an NWDAF service module, or an NRF service module.
  • an AMF service module for example, an AMF service module, an SMF service module, a UPF service module, a PCF service module, a UDM service module, a UDR service module, an AUSF service module, an NSSF service module, an NWDAF service module, or an NRF service module.
  • the SCP network element may be a device that acts as proxy to implement functions of the foregoing NF network element or NF service module.
  • first network function entities there may be one or more first network function entities, and there may also be one or more second network function entities.
  • the first network function entity may indirectly communicate with the second network function entity via multiple SCP network elements.
  • One of the first network function entity and the second network function entity may serve as a producer, and the other one may serve as a consumer.
  • the first network function entity serves as a consumer
  • the second network function entity serve as a producer.
  • an SMF network element may serve as the first network function entity. If a UPF network element serves as the second network function entity, an SMF network element may serve as the first network function entity. If a PCF network element serves as the second network function entity, an AMF network element may serve as the first network function entity, or an SMF network element may serve as the first network function entity. Further, a producer-consumer relationship between entities is not limited to the types listed herein. As long as two entities can communicate with each other, a producer-consumer relationship between the first network function entity and the second network function entity may be established.
  • an AMF network element may include one or more AMF service modules, which may be marked as AMF service 1/2/3/...
  • an SMF network element may include one or more SMF service modules, which may be marked as SMF service 1/2/3/.... If the SMF service 1/2/3/... serves as the second network function entity, the AMF service 1 may serve as the first network function entity. Further, the AMF service 2 may also serve as the first network function entity.
  • the foregoing producer-consumer relationship is relative and is not fixed, and may be determined according to different use scenarios. This is not limited in this embodiment of this application.
  • the communication system may further include a control function entity.
  • the control function entity is configured to provide information about valid SCP network elements for the first network function entity in a case that the first SCP network element used by the first network function entity to indirectly communicate with the second network function entity is invalid.
  • the first network function entity may select a second SCP network element from the valid SCP network elements based on the information about the valid SCP network elements, and further indirectly communicate with the second network function entity via the second SCP network element.
  • the control function entity may be a network element for recording whether an SCP network element is valid, for example, an NRF network element or a domain name system (DNS) network element.
  • the control function entity may alternatively be a service module for recording whether an SCP network element is valid, for example, an NRF service module or a DNS service module.
  • FIG. 3 is a schematic diagram of a network architecture of a communication system according to another embodiment of this application.
  • the communication system may not detect, by using a control function entity, whether another valid SCP network element exists. Instead, the first network function entity directly communicates with the second network function entity.
  • FIG. 4 is a schematic diagram of a network architecture of a communication system according to another embodiment of this application, in a case that the first SCP network element is invalid, if the first network function entity does not find a valid SCP network element by using a control function entity, the first network function entity may directly communicate with the second network function entity.
  • both searching for another valid SCP network element to establish indirect communication between the first network function entity and the second network function entity by using the valid second SCP network element and establishing, by the first network function entity, direct communication with the second network function entity can ensure that the first network function entity and the second network function entity can continually perform service communication in a case that the SCP network element used by the first network function entity to communicate with the second network function entity is invalid, thereby ensuring the service continuity and the reliability and availability of a system.
  • an embodiment of the communication method provided by the embodiments of this application may include the following steps 101 to 105.
  • a first network function entity indirectly communicates with a second network function entity via a first SCP network element.
  • the first network function entity detects a second SCP network element in a case that the first network function entity determines that the first SCP network element is invalid.
  • the first network function entity may determine that the first SCP network element is invalid in a way that if the first network function entity does not receive a response from the first SCP network element after requesting the first SCP network element to select a second network function entity for the first network function entity, the first network function entity determines that the first SCP network element is invalid.
  • a process of detecting the second SCP network element by the first network function entity may include two processes, namely, a finding process and a selection process.
  • the finding process may include that the first network function entity finds the second SCP network element by using a control function entity, for example, the control function entity feeds back a information list about valid SCP network elements including a second SCP network element to the first network function entity.
  • the selection process may include that the first network function entity selects the second SCP network element from the information list about valid SCP network elements fed back by the control function entity.
  • step 103 the first network function entity returns to directly communicate with the second network function entity.
  • Step 102 and step 103 are not performed at a same process, that is, if step 102 is performed, step 103 is not performed; if step 103 is performed, step 102 is not performed. That is, in a case that the first SCP network element is invalid, the first network function entity may detect another SCP network element (for example, the second SCP network element) to ensure that the first network function entity can continually perform service communication with the second network function entity. Alternatively, the first network function entity may return to directly communicate with the second network function entity to ensure that the first network function entity can continually perform service communication with the second network function entity.
  • another SCP network element for example, the second SCP network element
  • the first network function entity detects another SCP network element to ensure that the first network function entity can continually perform service communication with the second network function entity, because the detected another SCP network element may be valid or invalid, different communication manners may be determined depending on whether the second SCP network element is valid. Therefore, whether the second SCP network element is valid needs to be determined.
  • a determining manner is the same as the foregoing manner of determining whether the first SCP network element is valid. Details are not described herein again.
  • step 104 the first network function entity switches from the first SCP network element to the second SCP network element in a case that the second SCP network element is valid, and indirectly communicates with the second network function entity via the second SCP network element.
  • the first network function entity returns to directly communicate with the second network function entity in a case that the second SCP network element is invalid.
  • the SCP network element used by the first network function entity for communication with the second network function entity is invalid
  • another available SCP network element may be switched to or the first network function entity may return to directly communicate with the second network function entity. In this way, it can be ensured that the first network function entity can continually perform service communication with the second network function entity, thereby ensuring the service continuity and the reliability and availability of a system.
  • the first SCP network element may be not the first SCP network element selected by the first network function entity, and may be switched to from another SCP network element. Therefore, before step 101, the first network function entity may select a third SCP network element. In a case that the third SCP network element is invalid during selecting the second network function entity for the first network function entity, the first network function entity selects the first SCP network element to establish a communication connection between the first network function entity and the second network function entity.
  • the first network function entity may determine that the third SCP network element is invalid during selecting the second network function entity. In this case, the first network function entity may select the first SCP network element from valid SCP network elements and select the second network function entity for the first network function entity by using the first SCP network element.
  • the first network function entity selects N valid SCP network elements from configured M valid SCP network elements as the second SCP network elements, M is an integer and is greater than 0, and N is an integer and N is greater than 0 and less than or equal to M.
  • the detection is implemented through a statical configuration.
  • Multiple valid SCP network elements are configured for the first network function entity during initial configuration.
  • a second SCP network element may be selected from the remaining valid SCP network elements.
  • the M valid SCP network elements may be understood as the remaining valid SCP network elements.
  • the first network function entity transmits a first query request to the control function entity.
  • the control function entity may transmit a first query response to the first network function entity in response to the first query request.
  • the first query response includes information about the M valid SCP network elements
  • the first network function entity may select the N valid SCP network elements from the M valid SCP network elements as the second SCP network elements.
  • M is an integer and is greater than 0, and N is an integer and N is greater than 0 and less than or equal to M.
  • the first network function entity transmits a second query request to the control function entity.
  • the control function entity may transmit a second query response to the first network function entity in response to the second query request.
  • the second query response indicates absence of a valid SCP network element, it indicates that the second SCP network element is invalid.
  • the first query request and the second query request have the same function for querying the control function entity for whether a valid second SCP network element exists.
  • the communication method may include the following steps 201 to 203.
  • the first network function entity selects N valid SCP network elements from the M valid SCP network elements as the second SCP network elements, where N is an integer greater than 0 and less than or equal to M.
  • the first network function entity may select one second SCP network element, or may select two or more second SCP network elements. If two or more second SCP network elements are selected, service allocation may be performed in step 202 according to different service capabilities of the second SCP network elements.
  • step 202 the first network function entity performs service allocation among the N second SCP network elements according to load capacity information of each of the N second SCP network elements.
  • service may be allocated according to load capacity information of the second SCP network elements in a load balance manner.
  • the load capacity information may be represented by a weight factor. That is, service may be allocated based on weight factors of the second SCP network elements.
  • service may be allocated based on a proportion of the weight factor of each second SCP network element in a sum of the weight factors of all the second SCP network elements.
  • service allocation may also be performed on one of the following five bases.
  • the first network function entity may use different SCP network elements for different messages of a user equipment (UE), for example, use the SCP-1 for a message A of the UE and use the SCP-2 for a message B of the UE.
  • UE user equipment
  • the UE may establish different packet data unit (PDU) sessions, and different SCP network elements may use different PDU sessions.
  • PDU packet data unit
  • SCP-1 is used for a PDU session 1
  • SCP-2 is used for a PDU session 2.
  • Different SCP network elements may be used for different types of Internet Protocol (IP) addresses used by the UE.
  • IP Internet Protocol
  • the SCP-1 is used when a type of an IP address used by the UE is IPv4
  • the SCP-2 is used when a type of an IP address used by the UE is IPv6.
  • Different SCP network elements are used based on different service types of the UE.
  • the SCP-1 is used for short messages
  • the SCP-2 is used for security authentication
  • the SCP-3 is used for mobility management.
  • DNNs data network names
  • S-NSSAI single network slice selection assistance information
  • the first network function entity selects a second SCP network element from the N second SCP network elements to provide a service for a connected terminal. For example, all service requests for UE1 are allocated to the SCP-1, all service requests for UE2 are allocated to the SCP-2, and all service requests for UE3 are allocated to the SCP-3.
  • the UE may be referred to as a terminal and is a device with a wireless transceiver function.
  • the device may be deployed on the land, including an indoor or outdoor device, a handheld device, or an in-vehicle device; or may be deployed on the water (for example, on a steamship); or may be deployed in the air (for example, on an airplane, a balloon, or a satellite).
  • the terminal may be a mobile phone, a tablet computer (Pad), a computer with a wireless transceiver function, a virtual reality (VR) terminal, an augmented reality (AR) terminal, a wireless terminal for industrial control, a wireless terminal for remote medical, a wireless terminal in a smart grid, a wireless terminal for transportation safety, a wireless terminal in a smart city, a wireless terminal in a smart home, or the like.
  • a virtual reality (VR) terminal an augmented reality (AR) terminal
  • a wireless terminal for industrial control a wireless terminal for remote medical
  • a wireless terminal in a smart grid a wireless terminal for transportation safety
  • a wireless terminal in a smart city a wireless terminal in a smart home, or the like.
  • the first network function entity adjusts, in a case that Q second SCP network elements in the N second SCP network elements are invalid, the service allocation according to load capacity information of each of (N-Q) second SCP network elements, where Q is an integer greater than 0 and less than N.
  • the SCP-1 may be a second SCP network element (1) in FIG. 6
  • the SCP-2 may be a second SCP network element (2) in FIG. 6
  • ... the SCP-n may be a second SCP network element (n) in FIG. 6 .
  • load balance may be performed according to load capacities of the second SCP network elements, thereby improving the service processing capability.
  • the first network function entity may further notify the control function entity or the third network function entity of which SCP network elements are invalid. For example, the first network function entity transmits, to the control function entity or the third network function entity, a first notification message indicating that the first SCP network element or the second SCP network element is invalid, so that the control function entity timely updates, in response to the first notification message, information about whether recorded SCP network elements are invalid, to provide an accurate list of valid SCP network elements. In addition, a case that the third network function entity selects an invalid SCP network element is avoided.
  • the third network function entity may be a network function entity other than the first network function entity and the second network function entity.
  • An invalid SCP network element may be further restored to be valid again.
  • the communication method provided in the embodiments of this application may further include the following steps 301 to 303.
  • step 301 the first network function entity has returned to directly communicate with the second network function entity.
  • the first network function entity receives a second notification message indicating that the first SCP network element is restored to be valid or the second SCP network element is restored to be valid.
  • step 303 the first network function entity switches, in response to the second notification message, to indirectly communicate with the second network function entity via the first SCP network element or the second SCP network element.
  • the first network function entity switches to indirectly communicate with the second network function entity via the first SCP network element.
  • the second notification message indicates that the second SCP network element is restored to be valid
  • the first network function entity switches to indirectly communicate with the second network function entity via the second SCP network element.
  • the first network function entity may switch from direct communication to indirect communication, thereby further ensuring the reliability of a system while ensuring the service continuity.
  • An invalid first SCP network element may be further restored to be valid again.
  • the communication method provided in the embodiments of this application may further include the following steps 401 to 403.
  • step 401 the first network function entity indirectly communicates with the second network function entity via the second SCP network element.
  • the first network function entity receives a third notification message indicating that the first SCP network element is restored to be valid.
  • the first network function entity adds the first SCP network element to a resource pool of candidate valid SCP network elements in response to the third notification message.
  • the first SCP network element when the first SCP network element will be selected as a proxy between the first network function entity and the second network function entity again, reference may be made to the foregoing described solution. For example, when the first SCP network element and the second SCP network element perform load balance for service requests or when the second SCP network element is invalid and an SCP network element is to be selected from the resource pool of the valid SCP network elements, the first SCP network element may be selected again to provide an indirect communication service for the first network function entity and the second network function entity.
  • a communication apparatus 50 may include: a communication module 501, a detection module 502, a returning module 503, and a switching module 504.
  • the communication module 501 is configured to indirectly communicate with a second network function entity via a first SCP network element.
  • the detection module 502 is configured to detect a second SCP network element in a case that it is determined that the first SCP network element is invalid.
  • the return module 503 is configured to return to directly communicate with the second network function entity in a case that it is determined that the first SCP network element is invalid.
  • the switching module 504 is configured to switch from the first SCP network element to the second SCP network element in a case that the detection module detects that the second SCP network element is valid.
  • the communication module 501 is further configured to indirectly communicate with the second network function entity via the second SCP network element that is switched to by the switching module.
  • the return module 503 is further configured to return to directly communicate with the second network function entity in a case that the detection module detects that the second SCP network element is invalid.
  • the SCP network element used by the first network function entity to communicate with the second network function entity is invalid, another available SCP network element may be switched to or the first network function entity may return to directly communicate with the second network function entity. In this way, it can be ensured that the first network function entity can continually perform service communication with the second network function entity, thereby ensuring the service continuity and the reliability and availability of a system.
  • the communication apparatus 50 may further include a first selection module 505.
  • the first selection module 505 is configured to select a third SCP network element, and select, in a case that the third SCP network element is invalid during selecting the second network function entity for the first network function entity, the first SCP network element to establish a communication connection between the first network function entity and the second network function entity.
  • the detection module 502 is further configured to select N valid SCP network elements from configured M valid SCP network elements as the second SCP network elements, where M is an integer greater than 0, and N is an integer greater than 0 and less than or equal to M.
  • the detection module 502 may include: a first transmission unit and a first reception unit.
  • the first transmission unit is configured to transmit a first query request to a control function entity.
  • the first reception unit is configured to receive a first query response transmitted by the control function entity, the first query response includes information about M valid SCP network elements, M is an integer greater than 0.
  • the first selection module is further configured to select N valid SCP network elements from the M valid SCP network elements as the second SCP network elements, N is an integer greater than 0 and less than or equal to M.
  • the detection module 502 may include: a second transmission unit and a second reception unit.
  • the second transmission unit is configured to transmit a second query request to a control function entity.
  • the second reception unit is configured to receive a second query response transmitted by the control function entity, the second query response is used for indicating absence of a valid SCP network element, the absence of a valid SCP network element represents that the second SCP network element is invalid.
  • first transmission unit, the second transmission unit, the third transmission unit, the first reception unit, and the second reception unit are substantially the same, and each is a transmission unit or a reception unit.
  • the communication apparatus 50 further includes a service allocation module 506.
  • the service allocation module 506 is configured to perform service allocation among the N second SCP network elements according to load capacity information of each of the N second SCP network elements.
  • the service allocation module 506 is further configured to adjust, in a case that Q second SCP network elements in the N second SCP network elements are invalid, the service allocation according to load capacity information of each of (N-Q) second SCP network elements, Q is an integer greater than 0 and less than N.
  • the communication apparatus further includes: a transmission module 507.
  • the transmission module 507 is configured to transmit, to the control function entity or a third network function entity, a first notification message indicating that the first SCP network element or the second SCP network element is invalid.
  • the communication apparatus further includes a first reception module 508.
  • the first reception module 508 is configured to receive, in a case that the first network function entity has returned to directly communicate with the second network entity, a second notification message indicating that the first SCP network element is restored to be valid or the second SCP network element is restored to be valid.
  • the switching module 504 is further configured to switch, in response to the second notification message, to indirectly communicate with the second network function entity via the first SCP network element or the second SCP network element.
  • the communication apparatus further includes a second reception module 509 and an addition module 510.
  • the second reception module 509 is configured to receive, in a case that the first network function entity communicates with the second network function entity via the second SCP network element, a third notification message indicating that the first SCP network element is restored to be valid.
  • the addition module 510 is configured to add the first SCP network element to a resource pool of candidate valid SCP network elements in response to the third notification message.
  • the foregoing first network function entity includes corresponding hardware structures and/or software modules for performing the functions.
  • this application can be implemented by hardware or a combination of hardware and computer software. Whether a function is performed by hardware or computer software driving hardware depends on particular applications and design constraints of the technical solutions. Those skilled in the art may use different methods to implement the described functions for each particular application, but such implementation is not to be considered beyond the scope of this application.
  • the first network function entity may be implemented by using one physical apparatus, or may be jointly implemented by using multiple physical apparatuses, or may be a logical function unit in a physical apparatus. This is not specifically limited in this embodiment of this application.
  • the first network function entity may be implemented by the communication device in FIG. 11.
  • FIG. 11 is a schematic structural diagram of hardware of a communication device according to an embodiment of this application.
  • the communication device includes at least one processor 801, a memory 802, and a communication line 803.
  • the communication device may further include at least one of a transceiver 804 and a communication interface 806.
  • the processor 801 may be a general-purpose central processing unit (CPU), a microprocessor, an application-specific integrated circuit (ASIC), or one or more integrated circuits configured to control execution of a program in implementing the solutions of this application.
  • CPU central processing unit
  • ASIC application-specific integrated circuit
  • the communication line 803 may include a route, to transmit information between the foregoing components.
  • the transceiver 804 is configured to communicate, by using any transceiving apparatus, with another device or a communication network such as the Ethernet, a radio access network (RAN), or a wireless local area network (WLAN).
  • the transceiver 804 may alternatively be a transceiver circuit or a transceiver machine.
  • the communication device is the first network function entity, the communication device may include the transceiver.
  • the communication device may further include the communication interface 806.
  • the memory 802 may be a read-only memory (ROM) or another type of static storage device capable of storing static information and instructions, a random access memory (RAM) or another type of dynamic storage device capable of storing information and instructions, or may be an electrically erasable programmable read-only memory (EEPROM), a compact disc read-only memory (CD-ROM), or other compact disc storage or optical disc storage (including a compressed optical disc, a laser disc, an optical disc, a digital universal optical disc, a blue-ray optical disc, and the like), a magnetic disk storage medium or another magnetic storage device, or any other medium capable of carrying or storing expected program code in a form of instructions or data structures and capable of being accessed by a computer, but is not limited thereto.
  • the memory may exist independently, and is connected to the processor 801 by using the communication line 803.
  • the memory 802 may alternatively be integrated with the processor 801.
  • the memory 802 is configured to store computer executable instructions for executing the solutions of this application, and the processor 801 controls the execution.
  • the processor 801 is configured to execute the computer executable instructions stored in the memory 802, to implement the communication method provided by the method embodiments of this application.
  • the computer executable instructions in this embodiment of this application may also be referred to as application codes. This is not specifically limited in this embodiment of this application.
  • the processor 801 may include one or more CPUs, for example, a CPU 0 and a CPU 1 in FIG. 11 .
  • the communication device may include multiple processors, for example, a processor 801 and a processor 805 in FIG. 11 .
  • processors may be a single-core (single-CPU) processor, or may be a multi-core (multi-CPU) processor.
  • the processor herein may be one or more devices or circuits, and/or a processing core configured to process data (for example, computer executable instructions).
  • this application may perform function unit division for the control function entity and the first network function entity according to the foregoing method embodiments.
  • various function units may be obtained through division according to the corresponding functions, or two or more functions may be integrated into one function unit.
  • the integrated function unit may be implemented in the form of hardware, or may be implemented in the form of a software function unit.
  • the first reception module 509, the second reception module 510, the transmission module 508, and the communication module 501 all may be implemented by using the transceiver 804. Further, the communication module 501 may be implemented by using the communication interface 806. The detection module 502 may also be implemented by using the transceiver 804.
  • the switching module 504, the returning module 503, the addition module 511, the first selection module 505, and the service allocation module 506 may be all implemented by using the processor 801 or the processor 805.
  • All or some of the foregoing embodiments may be implemented by using software, hardware, firmware, or any combination thereof.
  • implementation may be entirely or partially performed 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, all or some of the processes or functions according to the embodiments of this application are produced.
  • the computer may be a general-purpose computer, a dedicated computer, a computer network, or other programmable apparatuses.
  • the computer instructions may be stored in a computer-readable storage medium or may be transmitted from a computer-readable storage medium to another computer-readable storage medium.
  • the computer instructions may be transmitted from a website, a computer, server, or a data center to another website, computer, server, or data center in a wired (for example, a coaxial cable, an optical fiber, or a digital subscriber line (DSL)) or wireless (for example, infrared, radio, or microwave) manner.
  • the computer-readable storage medium may be any usable medium that can be stored by the computer, or a data storage device, such as a server or a data center in which one or more usable mediums are integrated.
  • the usable medium may be a magnetic medium (for example, a soft disk, a hard disk, or a magnetic tape), an optical medium (for example, a DVD), a semiconductor medium (for example, a solid state disk (SSD)), or the like.
  • a person of ordinary skill in the art may understand that all or some of the steps of the methods in the embodiments may be implemented by a program instructing relevant hardware.
  • the program may be stored in a computer-readable storage medium.
  • the storage medium may include: a ROM, a RAM, a magnetic disk, or an optical disc.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Mobile Radio Communication Systems (AREA)
EP20825559.6A 2019-06-17 2020-06-03 Procédé et appareil de communication, entité et support d'informations Pending EP3986027A4 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201910523153.7A CN110234140B (zh) 2019-06-17 2019-06-17 一种通信方法、装置、实体及存储介质
PCT/CN2020/094140 WO2020253531A1 (fr) 2019-06-17 2020-06-03 Procédé et appareil de communication, entité et support d'informations

Publications (2)

Publication Number Publication Date
EP3986027A1 true EP3986027A1 (fr) 2022-04-20
EP3986027A4 EP3986027A4 (fr) 2022-07-27

Family

ID=67859951

Family Applications (1)

Application Number Title Priority Date Filing Date
EP20825559.6A Pending EP3986027A4 (fr) 2019-06-17 2020-06-03 Procédé et appareil de communication, entité et support d'informations

Country Status (6)

Country Link
US (1) US12022304B2 (fr)
EP (1) EP3986027A4 (fr)
JP (1) JP7237195B2 (fr)
KR (1) KR102705525B1 (fr)
CN (1) CN110234140B (fr)
WO (1) WO2020253531A1 (fr)

Families Citing this family (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN110234140B (zh) * 2019-06-17 2022-07-08 腾讯科技（深圳）有限公司 一种通信方法、装置、实体及存储介质
US11102138B2 (en) * 2019-10-14 2021-08-24 Oracle International Corporation Methods, systems, and computer readable media for providing guaranteed traffic bandwidth for services at intermediate proxy nodes
CN112822678B (zh) * 2019-10-31 2022-05-06 华为技术有限公司 一种服务化架构授权的方法
US11765618B2 (en) * 2020-03-20 2023-09-19 Nokia Technologies Oy Wireless communication system
US11102058B1 (en) * 2020-08-13 2021-08-24 Verizon Patent And Licensing Inc. Method and system for network function recovery notification

Family Cites Families (10)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP2013051509A (ja) 2011-08-30 2013-03-14 Sanyo Electric Co Ltd 仲介用通信端末装置および通信システム
EP2587774B1 (fr) * 2011-10-24 2015-03-04 Alcatel Lucent Procédé pour basculement proxy SIP
CN103096393B (zh) * 2011-10-27 2015-08-19 普天信息技术研究院有限公司 一种移动中继的切换方法
CN104144521B (zh) * 2013-05-08 2018-09-11 华为技术有限公司 中继通信方法、装置及系统
CN103873131B (zh) * 2014-04-09 2017-08-25 成都千嘉科技有限公司 一种无线抄表通信中继方法
CN105790995B (zh) * 2014-12-26 2020-04-14 中国移动通信集团辽宁有限公司 一种业务自动切换方法和装置
CN107623589A (zh) * 2017-08-17 2018-01-23 深圳市盛路物联通讯技术有限公司 路由切换方法及装置
US11271846B2 (en) * 2018-10-22 2022-03-08 Oracle International Corporation Methods, systems, and computer readable media for locality-based selection and routing of traffic to producer network functions (NFs)
US11864092B2 (en) * 2019-06-12 2024-01-02 Apple Inc. Performance measurements related to application triggering and SMS over NAS
CN110234140B (zh) * 2019-06-17 2022-07-08 腾讯科技（深圳）有限公司 一种通信方法、装置、实体及存储介质

Also Published As

Publication number Publication date
JP7237195B2 (ja) 2023-03-10
US20210392522A1 (en) 2021-12-16
JP2022527363A (ja) 2022-06-01
KR102705525B1 (ko) 2024-09-11
EP3986027A4 (fr) 2022-07-27
CN110234140B (zh) 2022-07-08
CN110234140A (zh) 2019-09-13
US12022304B2 (en) 2024-06-25
KR20210126739A (ko) 2021-10-20
WO2020253531A1 (fr) 2020-12-24

Similar Documents

Publication Publication Date Title
EP3986027A1 (fr) Procédé et appareil de communication, entité et support d'informations
EP3993347A1 (fr) Procédé et dispositif de migration d'application
EP3700252B1 (fr) Procédé et dispositif de communication
EP4075867A1 (fr) Procédé, dispositif et système de détermination d'instance d'application
EP3512118B1 (fr) Procédé et dispositif de transmission de message de réponse
KR102513998B1 (ko) 통신 방법 및 장치, 엔티티 및 컴퓨터 판독가능 저장 매체
US20120179737A1 (en) System and method for searching for mobile devices, and for establishing connections and data exchange between the mobile devices
CN109088799B (zh) 一种客户端接入方法、装置、终端以及存储介质
KR20140116900A (ko) 무선 네트워크에서 디바이스들 간의 터널 다이렉트 링크 설정(tdls) 세션을 확립하는 방법들 및 장치들
CN113543165B (zh) 通信方法、装置及系统
US11082893B2 (en) Session migration method and device applied to a UE tracking area update
CN114080056B (zh) 一种会话更新方法、终端和网络侧设备
US20210259047A1 (en) Apparatus and method of performing a group communication
US20220330373A1 (en) Subscription change processing method, device, and system
CN112583880B (zh) 一种服务器发现方法及相关设备
CN104426816B (zh) 一种虚拟机通信方法及装置
US11706301B2 (en) Server node selection method and terminal device
WO2017045454A1 (fr) Procédé, dispositif et système destinés à réaliser un accès à un terminal
WO2015085573A1 (fr) Procédé et dispositif de communication utilisant un spectre blanc
KR102100529B1 (ko) 디바이스간 무선 데이터 통신을 위한 연결 정보
EP4311280A1 (fr) Procédé et dispositif de communication
WO2024022163A1 (fr) Procédé de positionnement, terminal et dispositif réseau
US20240283771A1 (en) Method for Sending DNS Message, Terminal, and Network-Side Device
WO2022207399A1 (fr) Appareil, procédés et programmes informatiques
CN117998344A (zh) 信息确定方法、装置、通信设备以及可读存储介质

Legal Events

Date Code Title Description
STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: THE INTERNATIONAL PUBLICATION HAS BEEN MADE

PUAI Public reference made under article 153(3) epc to a published international application that has entered the european phase

Free format text: ORIGINAL CODE: 0009012

STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: REQUEST FOR EXAMINATION WAS MADE

17P Request for examination filed

Effective date: 20210713

AK Designated contracting states

Kind code of ref document: A1

Designated state(s): AL AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HR HU IE IS IT LI LT LU LV MC MK MT NL NO PL PT RO RS SE SI SK SM TR

RAP3 Party data changed (applicant data changed or rights of an application transferred)

Owner name: TENCENT TECHNOLOGY (SHENZHEN) COMPANY LIMITED

A4 Supplementary search report drawn up and despatched

Effective date: 20220629

RIC1 Information provided on ipc code assigned before grant

Ipc: H04W 28/08 20090101ALN20220623BHEP

Ipc: H04L 45/00 20220101ALI20220623BHEP

Ipc: H04L 41/40 20220101ALI20220623BHEP

Ipc: H04L 41/0668 20220101ALI20220623BHEP

Ipc: H04W 24/04 20090101AFI20220623BHEP

DAV Request for validation of the european patent (deleted)
DAX Request for extension of the european patent (deleted)
REG Reference to a national code

Ref country code: DE

Ref legal event code: R079

Free format text: PREVIOUS MAIN CLASS: H04W0036000000

Ipc: H04W0024040000

RIC1 Information provided on ipc code assigned before grant

Ipc: H04W 28/08 20090101ALN20240816BHEP

Ipc: H04L 41/0668 20220101ALI20240816BHEP

Ipc: H04L 45/00 20220101ALI20240816BHEP

Ipc: H04L 41/40 20220101ALI20240816BHEP

Ipc: H04L 41/0659 20220101ALI20240816BHEP

Ipc: H04W 24/04 20090101AFI20240816BHEP

GRAP Despatch of communication of intention to grant a patent

Free format text: ORIGINAL CODE: EPIDOSNIGR1

STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: GRANT OF PATENT IS INTENDED

RIC1 Information provided on ipc code assigned before grant

Ipc: H04W 28/08 20090101ALN20240910BHEP

Ipc: H04L 41/0668 20220101ALI20240910BHEP

Ipc: H04L 45/00 20220101ALI20240910BHEP

Ipc: H04L 41/40 20220101ALI20240910BHEP

Ipc: H04L 41/0659 20220101ALI20240910BHEP

Ipc: H04W 24/04 20090101AFI20240910BHEP