WO2022067736A1 - Procédé et appareil de communication - Google Patents

Procédé et appareil de communication Download PDF

Info

Publication number
WO2022067736A1
WO2022067736A1 PCT/CN2020/119592 CN2020119592W WO2022067736A1 WO 2022067736 A1 WO2022067736 A1 WO 2022067736A1 CN 2020119592 W CN2020119592 W CN 2020119592W WO 2022067736 A1 WO2022067736 A1 WO 2022067736A1
Authority
WO
WIPO (PCT)
Prior art keywords
information
api
network element
function network
service
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.)
Ceased
Application number
PCT/CN2020/119592
Other languages
English (en)
Chinese (zh)
Inventor
孙海洋
葛翠丽
李岩
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.)
Huawei Technologies Co Ltd
Original Assignee
Huawei Technologies 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 Huawei Technologies Co Ltd filed Critical Huawei Technologies Co Ltd
Priority to PCT/CN2020/119592 priority Critical patent/WO2022067736A1/fr
Publication of WO2022067736A1 publication Critical patent/WO2022067736A1/fr
Anticipated expiration legal-status Critical
Ceased legal-status Critical Current

Links

Images

Classifications

    • 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/51—Discovery or management thereof, e.g. service location protocol [SLP] or web services
    • 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/14—Session management

Definitions

  • the present application relates to the field of communication technologies, and in particular, to a communication method and device.
  • the network exposure function (NEF) can be applied to third parties in the form of an application programming interface (API) Open 5G network functions, correspondingly, third-party applications can obtain terminal related information by calling APIs in NEF.
  • API application programming interface
  • NEF can open the function of user plane function (UPF) to application function (AF), that is, NEF can send the information received from UPF to AF.
  • AF can call NEF's API to get information from UPF.
  • the UPF that provides the API must be the UPF that transmits the corresponding service, so that the AF can obtain the information of the service. How to make the AF determine the UPF for transmitting the corresponding service is a problem that needs to be solved.
  • the present application provides a communication method and apparatus, which can enable an API caller (eg, an AF) to discover a UPF that transmits a corresponding service.
  • an API caller eg, an AF
  • a first aspect provides a communication method
  • the communication method may include the following steps: an application programming interface publishing function APF obtains service application programming interface API information of a user plane function UPF, the API information includes the N6 information of the UPF and /or service description information, where the service description information is used to identify the first service, and the UPF is used to transmit the data of the first service of the terminal device.
  • the APF sends a service API release request to the general application programming interface framework core function CCF, and correspondingly, the general application programming interface framework core function CCF receives the service application programming interface API release request from the application programming interface publishing function APF, and the service
  • the API release request is used to request to release the API service of the UPF; the service API release request carries the API information.
  • the API information is carried in the service API publishing request.
  • the API information includes the N6 information of the UPF, or the API information includes the service description information, or the API information includes the N6 information and the service description information.
  • both the N6 information and the service description information can be associated with a certain
  • the API service of the UPF published by the service API request is the UPF corresponding to the API information, so that the API caller (eg, AF) can discover the specific UPF.
  • the API publishing process can be optimized.
  • the APF obtains the API information of the UPF, which may be implemented in the following manner: (1) The APF receives the API information from the UPF. (2) The APF receives the API information from the session management function SMF associated with the UPF.
  • the API information further includes the identifier of the UPF, and may also include address information of the terminal device.
  • the API information further includes an identifier of the UPF; the CCF stores a first correspondence between the UPF and the API information.
  • the AF receives an API discovery request from the application function AF to the CCF, where the API discovery request carries the N6 information and/or the service description information of the UPF; the CCF The first corresponding relationship is returned, and the identifier of the UPF is returned to the AF.
  • N6 information and service description information can determine the unique UPF, so that the AF can obtain the UPF of the transmission-related service and optimize the API publishing process.
  • the API information further includes an identifier of the SMF; the method further includes: the CCF stores a second correspondence between the SMF and the API information.
  • the API information further includes address information of the terminal device; the method further includes: the CCF receives an API discovery request from the AF, the API discovery request carries discovery information, and the discovery
  • the information includes any one or more of the following information: the address information of the terminal device, the N6 information of the UPF, or the service description information; the CCF determines according to the discovery information and the second correspondence A session management function SMF; the CCF requests the SMF for a UPF associated with the discovery information; the CCF sends the AF an identifier of the UPF.
  • the CCF determines the SMF corresponding to the address information of the terminal device according to the second correspondence; or the CCF determines the SMF corresponding to the address information of the terminal according to the second correspondence The SMF corresponding to the N6 information of the UPF; or, the CCF determines the SMF corresponding to the service description information according to the second correspondence.
  • the CCF sends a discovery request to the SMF, where the discovery request carries the N6 information and/or the service description information of the UPF included in the discovery information; the CCF receives information from The identification of the UPF of the SMF.
  • the discovery request carries the address information of the terminal device included in the discovery information.
  • the API information further includes address information of the terminal device; the CCF receives an API discovery request from the AF, the API discovery request carries discovery information, and the discovery information includes any one of the following or multiple pieces of information: the address information of the terminal device, the N6 information of the UPF, or the service description information; the CCF returns the information corresponding to the discovery information to the AF according to the second correspondence SMF's logo.
  • the AF can request the SMF for service-related information associated with the AF, such as QoS monitoring information, so that the AF can find a UPF that can provide the correct API.
  • the N6 information of the UPF includes: the tunnel information of the N6 of the UPF, and/or the network address translation NAT information of the UPF, wherein the NAT information includes the NAT translation of the UPF The address before and/or after the NAT translation of the UPF.
  • a communication method comprising the following steps: an application function AF sends an application programming interface (API) discovery request to a common application programming interface framework core function CCF, where the API discovery request carries any one or more of the following Information: address information of the terminal device, N6 information of the user plane function UPF, or service description information, the service description information is used to identify the first service, and the UPF is used to transmit the information of the first service of the terminal device.
  • API application programming interface
  • the AF receives the identifier of the session management function SMF from the CCF; the AF sends the N6 information of the UPF and/or the service description information to the SMF; the AF receives the SMF from the SMF
  • the identifier of the UPF where the identifier of the UPF is associated with the N6 information of the UPF and/or the service description information.
  • the AF can request the SMF to transmit the UPF of the service associated with the AF, so that the AF finds the UPF that provides the correct API, and further the UPF obtains the UPF associated with the AF.
  • Service-related information such as QoS monitoring information.
  • a communication device in a third aspect, can be a CCF, a device in a CCF (eg, a chip, or a chip system, or a circuit), or a device that can be used in combination with the CCF.
  • the communication device may include modules that perform one-to-one correspondence with the methods/operations/steps/actions performed by the CCF described in the first aspect, and the modules may be hardware circuits, software, or hardware.
  • the circuit is implemented in combination with software.
  • the communication device may include a processing module and a communication module.
  • the processing module is used to call the communication module to perform the function of receiving and/or sending.
  • the communication module may include a receiving module and a transmitting module. Exemplarily:
  • a receiving module configured to receive a service application programming interface API publishing request from the application programming interface publishing function APF, where the service API publishing request is used to request publishing the API service of the user plane function UPF; the service API publishing request carries API information , the API information includes N6 information and/or service description information of the UPF, where the service description information is used to identify the first service, and the UPF is used to transmit the data of the first service of the terminal device.
  • the API information further includes an identifier of the UPF
  • the processing module is configured to store the first correspondence between the UPF and the API information.
  • the receiving module is further configured to receive an API discovery request from the application function AF, where the API discovery request carries the N6 information and/or the service description information of the UPF.
  • a sending module configured to return the identifier of the UPF to the AF according to the first correspondence.
  • the API information further includes an identifier of the SMF; the processing module is configured to store the second correspondence between the SMF and the API information.
  • the API information further includes address information of the terminal device; the receiving module is further configured to receive an API discovery request from the AF, where the API discovery request carries discovery information, and the discovery information includes the following Any one or more pieces of information: the address information of the terminal device, the N6 information of the UPF, or the service description information.
  • the processing module is configured to determine a session management function SMF according to the discovery information and the second correspondence, and request the SMF for a UPF associated with the discovery information.
  • a sending module configured to send the identifier of the UPF to the AF.
  • the processing module when determining the SMF according to the discovery information and the second corresponding relationship, is configured to: determine the address information corresponding to the terminal device according to the second corresponding relationship or, according to the second correspondence, determine the SMF corresponding to the N6 information of the UPF; or, according to the second correspondence, determine the SMF corresponding to the service description information SMF.
  • the sending module when requesting the UPF associated with the discovery information to the SMF, is configured to send a discovery request to the SMF, where the discovery request carries the information included in the discovery information
  • the N6 information of the UPF and/or the service description information; the receiving module is used for the CCF to receive the identifier of the UPF from the SMF.
  • the discovery request carries the address information of the terminal device included in the discovery information.
  • the API information further includes address information of the terminal device; the receiving module is further configured to: receive an API discovery request from the AF, where the API discovery request carries discovery information, and the discovery information It includes any one or more of the following information: the address information of the terminal device, the N6 information of the UPF, or the service description information; the device further includes a sending module for, according to the second correspondence, Return to the AF the identification of the SMF corresponding to the discovery information.
  • the N6 information of the UPF includes: the tunnel information of the N6 of the UPF, and/or the network address translation NAT information of the UPF, wherein the NAT information includes the NAT translation of the UPF The address before and/or after the NAT translation of the UPF.
  • a communication device may be an APF, a device in an APF (eg, a chip, or a chip system, or a circuit), or a device that can be used in combination with the APF.
  • the communication device may include modules that perform one-to-one correspondence with the methods/operations/steps/actions performed by the APF described in the first aspect, and the modules may be hardware circuits, software, or hardware.
  • the circuit is implemented in combination with software.
  • the communication device may include a processing module and a communication module. The processing module is used to call the communication module to perform the function of receiving and/or sending. Exemplarily:
  • a processing module configured to obtain the service application programming interface API information of the user plane function UPF, the API information includes N6 information and/or service description information of the UPF, and the service description information is used to identify the first service, so The UPF is used to transmit the data of the first service of the terminal device;
  • a communication module configured to send a service API release request to the core function CCF of the general application programming interface framework, where the service API release request is used to request to release the API service of the UPF; the service API release request carries the API information.
  • the processing module when acquiring the API information of the UPF, is configured to receive, according to the communication module, the API information from the UPF; or, all the information from the session management function SMF associated with the UPF. the API information.
  • the API information further includes one or more of the following: the identifier of the UPF, or the address information of the terminal device.
  • the N6 information of the UPF includes: the tunnel information of the N6 of the UPF, and/or the network address translation NAT information of the UPF, wherein the NAT information includes the NAT translation of the UPF The address before and/or after the NAT translation of the UPF.
  • a fifth aspect provides a communication device, which can be an AF, a device in an AF (eg, a chip, or a chip system, or a circuit), or a device that can be used in combination with the AF.
  • the communication device may include modules that perform one-to-one correspondence with the methods/operations/steps/actions performed by the AF described in the second aspect, and the modules may be hardware circuits, software, or hardware.
  • the circuit is implemented in combination with software.
  • the communication device may include a processing module and a communication module.
  • the processing module is used to call the communication module to perform the function of receiving and/or sending.
  • the communication module may include a receiving module and a transmitting module. Exemplarily:
  • the sending module is used to send an application programming interface API discovery request to the general application programming interface framework core function CCF, where the API discovery request carries any one or more of the following information: address information of the terminal device, N6 of the user plane function UPF information, or service description information, the service description information is used to identify the first service, and the UPF is used to transmit the data of the first service of the terminal device;
  • a receiving module configured to receive the identifier of the session management function SMF from the CCF;
  • the sending module is further configured to send the N6 information of the UPF and/or the service description information to the SMF;
  • the receiving module is further configured to receive an identifier of the UPF from the SMF, where the identifier of the UPF is associated with the N6 information of the UPF and/or the service description information.
  • an embodiment of the present application provides a communication apparatus, the apparatus includes a communication interface and a processor, and the communication interface is used for the apparatus to communicate with other devices, such as data or signal transmission and reception.
  • the communication interface may be a transceiver, circuit, bus, module or other type of communication interface, and other devices may be network devices.
  • the processor is configured to invoke a set of programs, instructions or data to execute the above-mentioned first aspect or the method performed by the CCF described in each possible design of the first aspect.
  • the apparatus may also include a memory for storing programs, instructions or data invoked by the processor. The memory is coupled to the processor, and when the processor executes the instructions or data stored in the memory, the method for executing the CCF described in the first aspect or each possible design of the first aspect can be implemented.
  • an embodiment of the present application provides a communication apparatus, the apparatus includes a communication interface and a processor, and the communication interface is used for the apparatus to communicate with other devices, such as data or signal transmission and reception.
  • the communication interface may be a transceiver, circuit, bus, module or other type of communication interface, and other devices may be network devices.
  • the processor is configured to invoke a set of programs, instructions or data to execute the above-mentioned first aspect or the method described by each possible design of the first aspect to execute the APF.
  • the apparatus may also include a memory for storing programs, instructions or data invoked by the processor. The memory is coupled to the processor, and when the processor executes the instructions or data stored in the memory, the method for executing the APF described in the first aspect or each possible design of the first aspect can be implemented.
  • an embodiment of the present application provides a communication apparatus, the apparatus includes a communication interface and a processor, and the communication interface is used for the apparatus to communicate with other devices, such as data or signal transmission and reception.
  • the communication interface may be a transceiver, circuit, bus, module or other type of communication interface, and other devices may be terminal devices.
  • the processor is configured to invoke a set of programs, instructions or data to execute the method described in the second aspect or each possible design of the second aspect.
  • the apparatus may also include a memory for storing programs, instructions or data invoked by the processor. The memory is coupled to the processor, and when the processor executes the instructions or data stored in the memory, the method described in the second aspect or each possible design of the second aspect can be implemented.
  • the embodiments of the present application further provide a computer-readable storage medium, where computer-readable instructions are stored in the computer-readable storage medium, and when the computer-readable instructions are run on a computer, the computer-readable instructions can be A method as described in one aspect, the second aspect, each possible design of the first aspect or each possible design of the second aspect is performed.
  • an embodiment of the present application provides a chip system, where the chip system includes a processor and may also include a memory, for implementing the first aspect, the second aspect, each possible design of the first aspect, or the second aspect methods described in each possible design.
  • the chip system can be composed of chips, and can also include chips and other discrete devices.
  • an embodiment of the present application provides a communication system, where the system includes, for example, a CCF, an APF, and an AF, where the CCF is configured to execute the above-mentioned first aspect or the execution of the CCF in each possible design of the first aspect A method, the APF is configured to perform the method performed by the APF in the first aspect or each possible design of the first aspect, and the AF is configured to perform the method in the second aspect or each possible design of the second aspect.
  • a twelfth aspect provides a computer program product comprising instructions which, when run on a computer, enable the first aspect, the second aspect, each possible design of the first aspect or each possible design of the second aspect as described above The method described in is executed.
  • FIG. 1 is a schematic diagram of a system architecture in an embodiment of the present application.
  • FIG. 2 is a schematic diagram of another system architecture in an embodiment of the present application.
  • FIG. 3 is a schematic diagram of another system architecture in an embodiment of the present application.
  • FIG. 4a is a schematic diagram of a publishing process of a service in an embodiment of the present application.
  • FIG. 4b is one of the schematic diagrams of the discovery process of the service in the embodiment of the present application.
  • FIG. 4c is a schematic diagram of a calling process of a service in an embodiment of the present application.
  • FIG. 5 is one of the specific flow diagrams of the communication method in the embodiment of the application.
  • FIG. 6 is the second schematic diagram of the discovery process of the service in the embodiment of the present application.
  • FIG. 7 is the second schematic diagram of the specific flow of the communication method in the embodiment of the application.
  • FIG. 8 is a schematic diagram of a UL CL scenario in an embodiment of the application.
  • FIG. 9 is one of the schematic structural diagrams of the communication device in the embodiment of the application.
  • FIG. 10 is a second schematic structural diagram of a communication device according to an embodiment of the present application.
  • Embodiments of the present application provide a communication method and apparatus, wherein the method and apparatus are conceived based on the same or similar technical concepts. Since the principles of the method and apparatus for solving problems are similar, the implementation of the apparatus and the method can be referred to each other, and the repetition is not repeated. Repeat.
  • "and/or" describes the association relationship of the associated objects, indicating that there may be three kinds of relationships, for example, A and/or B may indicate that A exists alone, A and B exist simultaneously, and a single relationship exists. There are three cases of B.
  • the plural referred to in this application means two or more.
  • the methods provided in the embodiments of the present application can be applied to 5G communication systems, such as 5G new radio (NR), and can also be applied to various future communication systems, such as 6th generation (6G) communication systems.
  • 5G communication systems such as 5G new radio (NR)
  • 6G 6th generation
  • FIG. 1 shows the architecture of a communication system to which the communication method provided by the embodiment of the present application is applicable, and the communication system may include a UPF, a session management function (session management function, SMF) and an AF.
  • a UPF user plane protocol
  • a session management function session management function, SMF
  • an AF AF
  • the communication system may further include user equipment (user equipment, UE), access network (access network, AN) or radio access network (radio access network, RAN) nodes, data network (date network, DN) , unified data management (unified data management, UDM), access and mobility management function (access and mobility management function, AMF) or policy control function (policy control function, PCF) and other functional entities.
  • user equipment user equipment
  • access network access network, AN
  • radio access network radio access network
  • RAN radio access network
  • data network date network, DN
  • unified data management unified data management
  • UDM access and mobility management function
  • policy control function policy control function
  • a NEF may also be included in the communication system, not shown in FIG. 1 .
  • the functions of the NEF include: the services and capabilities provided by the secure open 3GPP network functions, which can be opened internally or to third parties.
  • the NEF may open the function of the UPF to the AF.
  • NEF can transform or translate information that interacts with AF, as well as information that interacts with internal network functions, such as AF service identification and internal 5G core network information, such as single network slice selection assistance information, S-NSSAI), data network name (DNN).
  • Each function may be connected through an interface, and the serial number of the interface or the name of the interface is not limited in this embodiment of the present application.
  • the interface defined in the 3GPP-related standard protocol of the 5G system can be used, or the interface in the future communication system can be used.
  • the interface names in Figure 1 are an illustrative example.
  • the UE communicates with the AMF through the next generation network (next generation, N) 1 interface (N1 for short)
  • the (R)AN communicates with the AMF through the N2 interface (N2 for short)
  • the (R)AN communicates with the AMF through the N3 interface (N3 for short).
  • the UPF communicates, and the UPF communicates with the DN through the N6 interface (N6 for short).
  • AMF communicates with SMF through N11 interface (N11 for short), AMF communicates with UDM through N8 interface (N8 for short), AMF communicates with PCF through N15 interface (N15 for short), SMF communicates with PCF through N7 interface (N7 for short), SMF communicates with PCF through N7 interface (N7 for short)
  • the N4 interface (N4 for short) communicates with the UPF
  • the PCF network element communicates with the AF network element through the N5 interface (N5 for short)
  • the SMF communicates with the UDM through the N10 interface (N10 for short).
  • each function or network element may also use a service interface for interaction.
  • the external service interface provided by AMF can be Namf
  • the external service interface provided by SMF can be Nsmf
  • the external service interface provided by UDM can be Nudm
  • the external service interface provided by PCF can be Npcf
  • the external service interface provided by AUSF can be Nausf
  • the service interface provided by AF externally can be Naf.
  • 5G system architecture 5G system architecture
  • each function in the embodiments of the present application may be implemented by one device, may be implemented jointly by multiple devices, or may be implemented by one or more functional modules in one device, which are not implemented in the embodiments of the present application. Specific restrictions. It can be understood that each function involved in the embodiments of the present application may be either a network element in a hardware device, or a software function running on dedicated hardware, or a combination of hardware and software, or a platform (for example, a cloud. Virtualization functions instantiated on the platform).
  • each function may also include other functional entities formed by the fusion of any of the above-mentioned functions.
  • session management and policy control there are two types of session management and policy control.
  • the communication system shown in FIG. 1 does not constitute a limitation of the communication system to which the embodiments of the present application can be applied.
  • the communication system architecture shown in FIG. 1 is a non-roaming 5G system architecture.
  • the method in the embodiment of the present application is also applicable to a roaming 5G system architecture and to various future communication networks.
  • the terminal device in this embodiment of the present application may be a device for implementing a wireless communication function, such as a terminal or a chip that can be used in the terminal, and the like.
  • the terminal may be a user equipment (UE), an access terminal, a terminal unit, a terminal station, a mobile station, a mobile station, a remote station, a remote terminal, a mobile device, a wireless communication device in a 5G network or a future evolved PLMN. equipment, terminal agent or terminal device, etc.
  • the access terminal may be a cellular phone, a cordless phone, a session initiation protocol (SIP) phone, a wireless local loop (WLL) station, a personal digital assistant (PDA), a wireless communication Functional handheld devices, computing devices or other processing devices connected to wireless modems, in-vehicle devices or wearable devices, virtual reality (VR) end devices, augmented reality (AR) end devices, industrial control (industrial) wireless terminal in control), wireless terminal in self-driving, wireless terminal in remote medical, wireless terminal in smart grid, wireless terminal in transportation safety Terminals, wireless terminals in smart cities, wireless terminals in smart homes, etc. Terminals can be mobile or stationary.
  • the terminal equipment is represented by UE.
  • the network device in this embodiment of the present application refers to a device that accesses the core network, and may be, for example, a base station, a broadband network gateway (BNG), an aggregation switch, or a non-third-generation partnership program ( 3rd generation partnership project, 3GPP) access equipment, etc.
  • the base station may include various forms of base stations, such as: a macro base station, a micro base station (also called a small station), a relay station, an access point, and the like.
  • the network equipment is represented by (R)AN.
  • Each function or device involved in the embodiment of the present application may also be referred to as a communication device, which may be a general-purpose device or a dedicated device, which is not specifically limited in the embodiment of the present application.
  • the function of the UPF may be opened to the AF, and the function opening may also be referred to as information opening. Opening the function of the UPF to the AF can be regarded as opening the information of the UPF to the AF.
  • the network element that realizes the function opening may be the NEF, or may be other function opening entities that evolve along with the system development. Assuming that the functions of UPF are opened to AF through NEF, the function opening specifically means that AF obtains the identifier of UPF through NEF, so that the API of UPF can be called, and AF can obtain information from UPF, for example, AF obtains service quality (quality of service) from UPF. service, QoS) information. UPF obtains QoS information from network devices.
  • the QoS information may be, for example, QoS Notification Control (QNC) information, indicating whether the bandwidth requirements of the service are met; or, for example, may be QoS monitoring (QoS monitoring) information, indicating the network delay.
  • QNC QoS Notification Control
  • QoS monitoring QoS monitoring
  • FIG. 2 exemplarily shows an API system architecture that may be used in an embodiment of the present application.
  • a common API framework (CAPIF) architecture is provided.
  • the CAPIF architecture includes API calling (API invoker) network elements, common application programming interface framework core function (CAPIF core function, CCF) network elements and application programming interface publishing function (API publishing function, APF) network elements, and can also include application programming interfaces.
  • Open function API exposing function, AEF
  • API management function application programming interface management function
  • AEF network elements, APF network elements and application programming interface management function network elements can be provided by capability open nodes (such as NEF in 5G network), and API calling network elements (such as third-party applications) can obtain 5G network by calling the API of CAPIF and/or terminal-related services in the EPS network.
  • capability open nodes such as NEF in 5G network
  • API calling network elements such as third-party applications
  • the API calling network element is the AF, and the AF can obtain the identifier of the UPF through the NEF, thereby calling the API service of the UPF.
  • CCF can also be provided by capability open nodes (eg NEF in 5G network).
  • Capability open nodes (such as NEF in 5G network) can simultaneously provide the functions of CCF, APF, AEF and application programming interface management functions.
  • CAPIF-1 is the reference point between the API calling network element and the CCF, and is used for the API calling network element in the public land mobile network (PLMN) trust domain to find the API, authenticate with the CCF, and obtain authorization .
  • PLMN public land mobile network
  • CAPIF-1 supports the following functions: Authenticate API calling network elements based on the identification and security credentials of API calling network elements; two-way authentication between API calling network elements and CCF; provide API calling network elements with authorization to access APIs; discover API information, etc.
  • CAPIF-1e is used for API calls outside the PLMN trust domain to call network elements to find APIs, to authenticate with CCF, and to obtain authorization.
  • CAPIF-1e supports the same functions as CAPIF-1.
  • CAPIF-2 is the reference point for API calling network elements and API opening network elements, and is used for API communication of API calling network elements within the PLMN trust domain.
  • CAPIF-2 supports the following functions: authentication of the API calling network element based on the identity and security credentials of the API calling network element; authorization verification when the API calling network element accesses the API; API calling, etc.
  • CAPIF-2e is used for API communication of API calling network elements within the PLMN trust domain.
  • CAPIF-2e supports the same functions as CAPIF-2.
  • CAPIF-3 is the reference point between the API open function network element and the CCF, and is used to perform access and policy-related control of API communication initiated by the API calling network element.
  • CAPIF-3 supports the following functions: Supporting API open function NEs authenticate API calling NEs based on the identity and security credentials of API calling NEs; supporting API opening function NEs provide authorization for API calling NEs before API calling NEs access the API ;Support the authorization verification of the API open function network element when the API calls the network element to access the API; support the API open function network element to control the API access based on the policy configured by the PLMN operator; support the API open function network element to record the API call log; Support API open function NEs to charge for API calls, etc.
  • CAPIF-4 is the reference point between the API publishing network element and the CCF for publishing API information.
  • CAPIF-4 supports the following API publishing functions to publish API functions.
  • CAPIF-5 is the reference point between the API management function network element and the CCF, and is used for the management of API and API calling network element information.
  • CAPIF-5 supports the following functions: support API management function NE access API call log; support API management function NE monitoring API call events; support API call NE configure API call NE information in CCF to support API call NE registration; support API management function NEs configure policies in the CCF, such as the upper limit of API calls, temporarily disable the API for a period of time; support API providers to monitor the status of APIs, etc.
  • the API calls network elements, which are generally third-party application functional entity software programs that have signed a service agreement with the PLMN operator. IoT) applications, vehicle to everything (V2X) applications, etc. These applications can run on terminal devices or network devices.
  • the API calling network element may also refer to an application function (application function, AF) network element.
  • the API calling network element may be in the same trust domain as the API provider (eg PLMN operator) that provides the API, or may belong to different trust domains.
  • API calling NEs support the following capabilities: support the authentication of API calling NEs, authenticate the identification and other information of API calling NEs; support mutual authentication with CAPIF; obtain authorization before accessing APIs; find and call APIs, etc.
  • the CCF network element supports the following functions: authenticate the API calling network element based on the identity and other information of the API calling network element; support mutual authentication with the API calling network element; provide authorization to the API calling network element before the API calling network element accesses the API ; Publish, store and support API search; be responsible for API access control based on PLMN operator's policies; store API call logs and provide them to authorized entities; perform billing based on API logs; detect API calls; API call network Meta registration; storage configuration policy; support for auditing of calls and logs, etc.
  • AEF network element provides API and is also the entry point for API calling network element to call API. It supports the following functions: Authenticate API calling network element based on the identification of API calling network element and other information provided by CCF network element; confirm the API calling network element provided by CCF network element. Authorization; synchronize API logs to CCF.
  • the APF network element provides the function of API publishing, so that the API calling network element can discover the API.
  • AMF network elements which provide management of APIs, support the following functions: auditing of API call logs provided from CCF network elements; monitoring events reported by CCF network elements; configuring API provider policies to APIs; detecting API status; registering API calls to network elements, etc.
  • the AEF network element can be deployed in the service capability exposure function (sevice capability exposure function, SCEF) network element; the CCF can be deployed in an independent network entity; or the CCF and API service providers (such as Entities within AEF, APF, AMF) can be deployed together in SCEF.
  • SCEF service capability exposure function
  • AEF network elements can be deployed in network exposure function (NEF) network elements or SCEF+NEF.
  • SCEF+NEF refers to the network equipment provided with SCEF function modules and NEF function modules.
  • CCF network elements can be implemented and deployed in an independent network entity; or CCF and network elements in API service providers (eg AEF, APF, AMF) can be deployed together in NEF or SCEF+NEF.
  • FIG. 3 exemplarily shows a schematic diagram of a network system architecture.
  • EPC evolved packet core
  • SCS services capability server
  • AS application server
  • third-party applications can obtain information about the terminal from the EPC through SCEF.
  • SCEF 5th generation core
  • the third-party application can be realized through the application function (AF); the third-party application can be obtained from the 5GC through NEF or NEF+SCEF Information about the terminal.
  • third-party applications can obtain services through T8 or Nnef through pre-configured capability exposure network elements, or through the CAPIF interface in the CAPIF architecture to obtain services from the 3rd Generation Partnership Project (3GPP) network.
  • 3GPP 3rd Generation Partnership Project
  • the SCS/AS or AF acts as an API invoker (API invoker), which can search for available services through the CCF network element, and then initiate the capability exposure node (supporting the AEF network element in the CAPIF architecture) according to the available services.
  • API invoker API invoker
  • FIGS. 4 a to 4 c the process of publishing, discovering, and invoking services is shown in FIGS. 4 a to 4 c .
  • FIG. 4a it is a schematic diagram of a service publishing process.
  • the CCF network element has been configured with the necessary information to authorize the APF network element, and the API invoker may have subscribed the API service to the CCF network element.
  • the service publishing process includes the following steps:
  • the APF network element sends a service API publish request (service API publish request) message to the CCF network element, and the service API publish request message carries API information.
  • the API information may include, but is not limited to, the API name [M], AEF profile (AEF Identification [M], version number [M], protocol used by API, data format (such as xml, JASON), interface description (IP address, port number, security method [M]) [M], API description information, API Supported features (features), etc. [M] means required.
  • Step 2 The CCF network element checks whether the APF network element is authorized to publish the API, and when the check passes, the CCF network element saves the received API information.
  • Step 3 The CCF network element returns a service API publish response (service API publish response) message to the APF network element, and the service API publish response message indicates success or failure of API publishing.
  • the CCF network element can also send a notification message to the API invoker that has subscribed to the service to notify the API invoker that there is a new API or an API that the API invoker is interested in.
  • FIG. 4b it is a schematic diagram of a service discovery process.
  • the API invoker has logged in and learned the API invoker ID, and the CCF network element has configured the service discovered by the API invoker.
  • the service discovery process includes the following steps:
  • Step 1 The API invoker sends a service API discovery request (service API discover request) message to the CCF network element, and the request message includes the API invoker's identifier and discovery filter conditions.
  • service API discover request service API discover request
  • Step 2 After the CCF network element receives the service API discovery request message, the CCF network element authenticates the identity of the API invoker, and the CCF network element retrieves the API information according to the discovery filter conditions and the policy information of the API invoker.
  • Step 3 The CCF network element returns a service API discovery response message to the API invoker, and the response message contains the API information that can be used by the API invoker to be changed if the conditions are met.
  • the API information may be one or more API information.
  • the purpose of the service discovery process is that the API invoker requests available services from the CCF network element, so the service discovery process can also be understood as a service request process or a service search process.
  • FIG. 4c it is a schematic diagram of a service invocation process. As shown in Figure 4c, the service invocation process includes the following steps:
  • Step 1 The API invoker sends a service API call request message to the AEF network element, and the message may include the API caller identity and the information of the service API.
  • Step 2 After receiving the service API call request message, the AEF network element authenticates the API invoker, and then executes the corresponding API logic.
  • Step 3 The AEF network element returns a service API call response message to the API invoker.
  • the API calling network element may be an AF, or may be another network element capable of implementing a third-party application function, and the AF is used as an example for description.
  • the AF calls the network element as an API, and obtains information from the UPF through the API function, which can be terminal-related information, such as QoS information, QoS status notification, etc.
  • UPF is an API provider.
  • the UPF that can provide the API must be the UPF that transmits the corresponding service, and the corresponding service refers to the service provided by the AF for the terminal device.
  • the service API published by the CCF has nothing to do with the UPF itself.
  • the UPF discovered by the AF is not necessarily the UPF that transmits the corresponding service.
  • the embodiment of the present application provides a communication method, which enables the AF to obtain the API of the correct UPF and the API of the UPF that transmits the corresponding service, thereby obtaining the correct terminal device information and ensuring the correct operation of the service.
  • the APF obtains the API information of the UPF.
  • the API information includes one or more of the following information: N6 information of the UPF, or service description information.
  • the service description information is used to identify the first service, and the UPF is used to transmit the data of the first service of the terminal device.
  • the APF sends a service API publishing request to the CCF, and the CCF receives the service API publishing request from the APF.
  • the service API release request is used to request to release the API service of the UPF, and the service API release request carries any one or more kinds of API information in S501.
  • the API information is carried in the service API publishing request.
  • the API information includes the N6 information of the UPF, or the API information includes the service description information, or the API information includes the N6 information and the service description information.
  • the API information can be associated with a specific UPF, and the API service of the UPF published by the service API request is the UPF corresponding to the API information, so that the API caller (eg AF) can discover the specific UPF.
  • the API publishing process can be optimized.
  • the API information may also include address information of the terminal device, where the address information of the terminal device may be an Internet Protocol (IP) address allocated by the network to the terminal device, such as an IPv4 address or an IPv6 prefix.
  • IP Internet Protocol
  • the address information of the terminal device may also be a media access control (medium access control, MAC) address of the terminal device.
  • the IP address allocated by the network to the terminal device may refer to the IP address allocated by the network for the current PDU session, and the MAC address of the terminal device may also be the MAC address allocated by the network for the current PDU session.
  • the address information of the terminal device may also be the IP address segment of the UPF.
  • the N6 information of the UPF included in the API information may be the tunnel information of the N6 of the UPF.
  • it may be the tunnel information of the tunnel established between the UPF and the corresponding service server, such as the tunnel endpoint identifier, or the network address translation of the UPF ( network address translation, NAT) information, or a combination of the N6 tunnel information of UPF and the NAT information of UPF.
  • the NAT information of the UPF may include the address after the NAT translation corresponding to the UPF, such as the UE IP address in the service delivered by the UPF.
  • the NAT information of the UPF may also include the address before the NAT translation corresponding to the UPF, such as the UE IP address in the service delivered by the UPF.
  • the UE address (generally an IPv4 address) is converted into a new address
  • the NAT-translated address corresponding to the UPF is the new address of the UE after address translation.
  • the service description information included in the API information is used to distinguish information of different services, and the service description information is used to identify the first service.
  • the service description information may be an IP quintuple or an application identifier.
  • the service description information may be any one or more of a packet filter, an application identifier, a service identifier, or a packet detection rule (packet detection rule, PDR).
  • the UPF can be uniquely determined through both the N6 information of the UPF and the service description information.
  • the APF obtains the API information of the UPF, which may be obtained from the UPF, or may be obtained from the SMF associated with the UPF, or the APF may pre-store the correspondence between the UPF and the API information in a pre-configured manner.
  • APF obtains this API information from UPF, the following procedure is included.
  • the UPF sends the API information to the APF, and the APF receives the API information from the UPF.
  • the API information may also include the identifier of the UPF.
  • the APF After receiving the API information, the APF stores the correspondence between the UPF and the API information, which may be the correspondence between the identifier of the UPF and the API information.
  • APF obtains this API information from SMF, the following procedure is included.
  • the SMF sends the API information to the APF, and the APF receives the API information from the SMF.
  • the SMF may preconfigure the correspondence between the UPF and the API information.
  • the API information sent by the SMF to the APF may include the identifier of the UPF.
  • the APF stores the corresponding relationship between the UPF and the API information.
  • the API information may also refer to information that does not include the identifier of the UPF.
  • the SMF needs to send the identifier of the UPF to the APF when sending the API information to the APF, and the UPF needs to also send the APF to the APF when sending the AIP information to the APF. Send the identity of this UPF.
  • S503 is also included.
  • the CCF After receiving the service API publishing request from the APF, the CCF stores the corresponding relationship between the UPF and the API information.
  • the API information carried in the service API release request includes the identifier of the UPF.
  • the CCF After receiving the service API release request from the APF, the CCF can know the identifier of the UPF according to the API information carried in the service API release request, and store the UPF and API information. corresponding relationship.
  • the service API release request carries the identifier of the UPF.
  • the CCF After receiving the service API release request from the APF, the CCF stores the corresponding relationship between the UPF and the API information according to the identifier of the UPF carried in the service API release request.
  • the CCF can also check whether the APF is authorized to publish the API, and when the check passes, the CCF stores the correspondence between the UPF and the API information.
  • S504 is also included.
  • the CCF returns a service API publish response (service API publish response) to the APF, and the APF receives the service API publish response from the CCF.
  • service API publish response service API publish response
  • the service API publish response can indicate success or failure of the API publish.
  • CCF can also send notification messages to API invokers that have subscribed to the service, notifying the API invokers that there are new APIs or APIs that API invokers are interested in. For example, for a notification service subscribed by an AF, the CCF can send a notification message to the AF, informing the AF that the UPF can provide an API.
  • FIG. 5 provides a process for publishing a service API
  • the embodiment of the present application also provides a process for discovering a service API.
  • the process for discovering a service API can be used alone as an embodiment to form the solution to be protected in this application, or it can be combined with FIG. 5
  • the embodiments are combined to form the solutions to be protected in the present application.
  • FIG. 6 takes the combination with the embodiment of FIG. 5 as an example for illustration. When combined with the embodiment of FIG. 5 , after S502 , S601 and S602 are executed.
  • the discovery process of the service API provided by the embodiment of the present application is as follows.
  • the AF sends an API discovery request to the CCF, and the CCF receives the API discovery request from the AF.
  • the API discovery request carries the N6 information of the UPF, or the API discovery request carries the service description information, or the API discovery request carries the N6 information and the service description information of the UPF.
  • the API discovery request may also carry address information of the terminal device.
  • the AF can obtain service description information in the following ways.
  • the AF (or the application server corresponding to the AF) obtains one or more of the source address, destination address or port number of the data from the acquired data packet.
  • AF can also obtain the address information of the terminal device from the acquired data packet.
  • the AF can obtain the N6 information of UPF in the following ways. For example, when a tunnel is established between the UPF and the AF (or the application server corresponding to the AF), the UPF needs to send its own tunnel endpoint identifier to the AF (or the application server corresponding to the AF), so that the AF obtains the tunnel endpoint identifier of the UPF.
  • AF or the application server corresponding to AF
  • obtains information such as the source address, destination address and port number of the NAT-translated data from the obtained data packet, and sends a request to the network based on the obtained information.
  • the network side can store the correspondence between the UPF and the source address of the NAT-translated data.
  • the AF simultaneously obtains information such as the source address, destination address, and port number of the data before and after the NAT translation, and sends a request to the network based on the obtained information. This requires AF to be NAT-aware.
  • the CCF returns the identifier of the UPF to the AF according to the first correspondence.
  • the AF receives the identification of this UPF from the CCF.
  • what the CCF returns to the AF may be other information used to indicate the UPF.
  • the first correspondence is the correspondence between the UPF and the API information, and the API information includes the information carried in the above-mentioned API discovery request.
  • the first correspondence may be the correspondence between the UPF and the API information saved by the CCF after receiving the service API publishing request from the APF in S502.
  • the AF acquires the UPF that requests the API service, and the UPF is related to the service associated with the AF, that is, the service transmitted by the UPF is the service between the AF and the terminal device. Only the UPF can open service-related information associated with the AF, such as QoS monitoring information, so that the AF can find a UPF that can provide the correct API.
  • an API calling process may also be included.
  • An optional API call process is as follows.
  • Step 1 The AF sends a service API call request to the UPF, and the service API call request includes the API caller identity and the information of the service API.
  • Step 2 After receiving the service API call request, the UPF authenticates the API caller. Then execute the corresponding API logic.
  • the UPF can obtain the corresponding security information from the CCF to authenticate the API caller.
  • Step 3 UPF returns the service API call response to the API caller.
  • an embodiment of the present application further provides a communication method, as shown in FIG. 7 , and the specific process of the method is as follows.
  • the SMF sends API information to the APF, and the APF receives the API information from the SMF.
  • the information included in the API information can be in the following situations:
  • the API information includes the N6 information of the UPF.
  • the API information includes service description information.
  • the API information includes the N6 information and service description information of the UPF.
  • the API information may also include address information of the terminal device.
  • the SMF can obtain the above-mentioned API information according to the pre-configured information, and can also report the API information to the SMF through the UPF.
  • the APF sends a service API publishing request to the CCF, and the CCF receives the service API publishing request from the APF.
  • the service API release request is used to request to release the API service of the UPF, and the service API release request carries the API information in S701.
  • the SMF may also send the identifier of the SMF to the APF, or the API information may further include the identifier of the SMF.
  • S703 is also included.
  • the CCF After receiving the service API publishing request from the APF, the CCF stores the corresponding relationship between the SMF and the API information.
  • the API information carried in the service API release request includes the identifier of the SMF.
  • the CCF After receiving the service API release request from the APF, the CCF can know the identifier of the SMF according to the API information included in the service API release request, and store the SMF and API information. corresponding relationship.
  • the service API release request carries the SMF identifier.
  • the CCF After receiving the service API release request from the APF, the CCF stores the correspondence between the SMF and the API information according to the SMF identifier carried in the service API release request.
  • the CCF can also check whether the APF is authorized to publish the API, and when the check passes, the CCF stores the correspondence between the SMF and the API information.
  • S704 is also included.
  • the CCF returns a service API publish response (service API publish response) to the APF, and the APF receives the service API publish response from the CCF.
  • service API publish response service API publish response
  • the service API publish response can indicate success or failure of the API publish.
  • CCF can also send notification messages to API invokers that have subscribed to the service, notifying the API invokers that there are new APIs or APIs that API invokers are interested in. For example, for a notification service subscribed by an AF, the CCF can send a notification message to the AF, informing the AF that the UPF can provide an API.
  • the above steps S702 to S704 are the publishing process of the service API.
  • the embodiment of FIG. 7 also includes the discovery process of the service API. Combined with the publishing process of the service API, the solution to be protected in this application is formed.
  • S702 to S709 are executed.
  • S705 is executed after S702, and there is no strict sequence with S703 and S704.
  • S702* to S709* are executed.
  • the AF sends an API discovery request to the CCF, and the CCF receives the API discovery request from the AF.
  • the API discovery request carries discovery information, and the discovery information may be UPF N6 information, or the discovery information may be service description information, or the discovery information may be UPF N6 information and service description information.
  • the API discovery request may also carry address information of the terminal device. What information is carried by the API information in S701, the API discovers what information can be carried in the request.
  • the CCF determines the SMF according to the corresponding relationship between the SMF and the API information, and according to the above-mentioned discovery information.
  • the discovery information is related to the API information. What kind of information is carried by the API information in S701, and what kind of discovery information can be carried in the API discovery request, so that the CCF can correspond to the corresponding relationship between the discovery information and the SMF according to the corresponding relationship between the SMF and the API information relationship to determine the SMF corresponding to the discovery information.
  • the discovery information is service description information
  • the CCF determines the SMF corresponding to the service description information according to the correspondence between the SMF and the service description information.
  • the CCF requests the SMF for the UPF associated with the discovery information.
  • the CCF may send a discovery request (discovery request) to the SMF, and the SMF receives the discovery request from the CCF, where the discovery request is used to request the UPF associated with the discovery information, and the discovery request carries the information contained in the discovery information.
  • discovery request discovery request
  • S708 The SMF returns the identifier of the UPF to the CCF, and the CCF receives the identifier of the UPF from the SMF.
  • the SMF determines the UPF corresponding to the information, that is, the UPF that transmits the first service, and returns the UPF identifier to the CCF.
  • the CCF sends the identifier of the UPF to the AF, and the AF receives the identifier of the UPF from the CCF.
  • what the CCF returns to the AF may be other information used to indicate the UPF.
  • S705 to S709 may be implemented in the case that the API information in S701 includes (1), (2) or (3).
  • the AF sends an API discovery request to the CCF, and the CCF receives the API discovery request from the AF.
  • the API discovery request carries discovery information, and the discovery information may be information corresponding to the API information in S701.
  • the discovery information may be N6 information of UPF, or the discovery information may be service description information, or the discovery information may be N6 information and service description information of UPF.
  • the discovery information may also be address information of the terminal device. What information is carried by the API information in S701, and what information can be carried in the API discovery request.
  • the API information in S701 may be the address information of the terminal device.
  • the API discovery request carries the address information of the terminal device.
  • the CCF determines the SMF according to the corresponding relationship between the SMF and the API information, and according to the above-mentioned discovery information.
  • the discovery information is the identifier of the terminal device
  • the CCF determines the SMF corresponding to the identifier of the terminal device according to the correspondence between the SMF and the identifier of the terminal device.
  • the CCF sends the identifier of the SMF to the AF, and the AF receives the identifier of the SMF from the CCF.
  • the CCF sends an API discovery response to the AF, and the AF receives the API discovery response from the CCF.
  • the API discovery response carries the identifier of the SMF.
  • the AF requests the UPF from the SMF.
  • the CCF can send a discovery request to the SMF, and the SMF receives the discovery request from the CCF.
  • the discovery request is used to request a UPF, and the information carried in the discovery request is related to API information.
  • the discovery request carries the UPF.
  • the N6 information can also carry service description information, and can also carry the identity of the terminal device.
  • the SMF returns the identifier of the UPF to the AF, and the AF receives the identifier of the UPF from the SMF.
  • the SMF determines the UPF corresponding to these information, that is, determines the UPF that transmits the first service, and returns the identifier of the UPF to the AF.
  • what the SMF returns to the AF may be other information used to indicate the UPF.
  • S705* to S709* may be implemented in the case that the API information in S701 includes (1), (2), (3) or (4).
  • an API call process may also be included, that is, the AF calls the API of the UPF.
  • the API call process reference may be made to the relevant description in the above-mentioned embodiment in FIG. 6 , which will not be repeated here.
  • the API information is carried in the service API publishing request.
  • the API information includes the N6 information of the UPF, or the API information includes the service description information, or the API information includes the N6 information and the service description information.
  • the API information can be associated with a specific UPF, and the API service of the UPF published by the service API request is the UPF corresponding to the API information, so that the API caller (eg AF) can discover the specific UPF.
  • the API publishing process can be optimized.
  • the CCF stores the correspondence between the SMF and the API information.
  • the CCF can determine the corresponding SMF according to the information carried in the API discovery request.
  • the CCF requests the SMF for the UPF corresponding to the information carried in the API discovery request, so as to return the UPF that transmits the first service to the AF; or the CCF returns the SMF identifier to the AF, the AF requests the UPF to the SMF, and the SMF returns to the AF to transmit the first service. UPF for business.
  • the publishing process, the discovery process, and the calling process of the service API provided by the embodiments of the present application may be implemented on the basis of FIG. 4 a , FIG. 4 b , and FIG. 4 c .
  • the SMF can control the data path of the PDU session, so that the PDU session can correspond to multiple N6 interfaces at the same time.
  • the UPF that terminates these N6 interfaces is called the UPF that supports the PDU Session Anchor Function (ie PSA UPF).
  • PSA UPF PDU Session Anchor Function
  • Each anchor point of a PDU session provides access to the same DN.
  • the first PDU session anchor point when the PDU session is established is associated with the service and session continuity (service and session continuity, SSC) mode of this PDU session.
  • Other anchor points of the PDU session such as selective traffic routing to the DN, are independent of the SSC mode of the PDU session.
  • Selective routing of traffic to the DN refers to such a deployment that, for example, certain traffic is selected to be forwarded on the N6 interface to the access network (AN) closer to serving the UE.
  • AN access network
  • an uplink classifier functionality (UL classifier functionality) is used, which is called an uplink classifier (UL classifier, ULCL) scenario.
  • UL CL is a function provided by UPF, which is designed to transfer (locally) certain services using the flow filters provided by SMF.
  • the SMF can decide to add (insert) or remove a UPF that supports UL CL, and the SMF controls it through the common N4 interface and UPF capabilities.
  • the SMF can insert a UPF supporting UL CL when the session is established or after the establishment is completed, and can also remove the UL CL after the session is established.
  • the SMF can insert multiple UPFs supporting the UL CL function on the data path of the PDU session.
  • the UE does not perceive the transfer of traffic brought by the UL CL, nor does it participate in the addition or deletion of the UL CL.
  • IPv4 IPv6 or IPv4v6 type PDU scenario
  • the UE associates the PDU session with a single IPv4 address or a single IPv6 prefix or both.
  • a PDU session When UL CL is inserted in the data path, a PDU session will have multiple PDU session anchors. These anchors provide different access to the same DN. Among them, only one anchor point is the anchor point of the IPv4 address and/or IPv6 prefix assigned to the UE by this PDU session.
  • the UL CL forwards the uplink traffic to different PDU session anchors and aggregates the downlink traffic destined for the UE, i.e. aggregates the traffic from different PDU session anchors into the downlink destined for the UE. These are based on the service detection and service forwarding rules provided by SMF.
  • the UL CL uses filtering rules (such as checking the destination IP address/prefix of upstream IP packets) and then decides how the packets should be routed.
  • filtering rules such as checking the destination IP address/prefix of upstream IP packets
  • the UPF that supports the UL CL function can also be configured by the SMF to support functions such as charging, rate control (session-AMBR level), and lawful interception.
  • More UL CLs (and correspondingly more PDU session anchors) can be inserted on the data path to create a new data path for the same PDU session.
  • the way to organize the data paths of each UL CL within a PDU session depends on the operator's configuration and SMF logic, and there can only be one and only one UPF (UPF supporting UL CL) connected to the (R)AN through the N3 interface.
  • UPF UPF supporting UL CL
  • a new PSA transmission corresponding service can be inserted into the PDU session without the UE being aware of it, without assigning a new IP address to the UE, so the address information of the UE (that is, the above address information of the terminal device) to identify the UPF corresponding to the service.
  • the UPF corresponding to the service can be identified through the N6 information or the service description information, so as to ensure that the AF can find the UPF of the related service.
  • the local AF located in the local DN needs to call the API of the local UPF, and only PSA2 can be opened to the local AF function, such as opening QoS information, but the UE address information of PSA1 and PSA2 is the same, through the N6 of UPF information or service description information, the local AF can find the UPF that transmits the AF-related service, so as to ensure the correctness of the service information.
  • the first network device and the AMF may include hardware structures and/or software modules, and implement the above-mentioned various functions in the form of hardware structures, software modules, or hardware structures plus software modules.
  • the above functions may be performed in the form of a hardware structure, a software module, or a hardware structure plus a software module depending on the specific application and design constraints of the technical solution.
  • an embodiment of the present application further provides a communication device 900 .
  • the communication device 900 may be a CCF, APF or AF, or a device in a CCF, APF or AF, or a A device that can be used with CCF, APF or AF.
  • the communication device 900 may include a module that performs the CCF, APF or AF in the above method embodiments, and performs a one-to-one correspondence with the method/operation/step/action.
  • the module may be a hardware circuit or a software. It can also be implemented by a hardware circuit combined with software.
  • the communication device 900 may include a communication module 901 and a processing module 902 . Further, the communication module 901 may further include a receiving module 901-1 and a sending module 901-2.
  • the processing module 902 is configured to call the communication module 901 to receive and/or send signals.
  • the processing module 902 is configured to call the receiving module 901-1 to receive the API release request from the APF, and the service API release request is used to request the release of the API service of the user plane function UPF; the service API release request carries the API information, and the API information includes the N6 of the UPF. Information and/or service description information, the service description information is used to identify the first service, and the UPF is used to transmit the data of the first service of the terminal device.
  • the processing module 902 is used to obtain the service application programming interface API information of the user plane function UPF, the API information includes the N6 information and/or service description information of the UPF, the service description information is used to identify the first service, and the UPF is used to transmit the terminal equipment the data of the first business;
  • the communication module 901 is configured to send a service API release request to the CCF, and the service API release request is used to request to release the API service of the UPF; the service API release request carries API information.
  • the sending module is used to send an application programming interface API discovery request to the core function CCF of the general application programming interface framework.
  • the API discovery request carries any one or more of the following information: address information of the terminal device, N6 information of the user plane function UPF, or service description information, the service description information is used to identify the first service, and the UPF is used to transmit the data of the first service of the terminal device;
  • a receiving module for receiving the identifier of the session management function SMF from the CCF;
  • the sending module is also used to send the N6 information and/or service description information of the UPF to the SMF;
  • the receiving module is further configured to receive the identifier of the UPF from the SMF, where the identifier of the UPF is associated with the N6 information and/or service description information of the UPF.
  • the communication module 901 and the processing module 902 are further configured to perform other operations performed by the CCF, APF or AF in the above method embodiments, which will not be repeated here.
  • the division of modules in the embodiments of the present application is schematic, and is only a logical function division. In actual implementation, there may be other division methods.
  • the functional modules in the various embodiments of the present application may be integrated into one processing unit. In the device, it can also exist physically alone, or two or more modules can be integrated into one module.
  • the above-mentioned integrated modules can be implemented in the form of hardware, and can also be implemented in the form of software function modules.
  • a communication apparatus 1000 provided by an embodiment of the present application is used to implement the functions of CCF, APF, or AF in the above method.
  • the device When the function of the CCF is implemented, the device may be the CCF, a device in the CCF, or a device that can be matched and used with the CCF.
  • the device When the function of the APF is implemented, the device may be the APF, a device in the APF, or a device that can be used in combination with the APF.
  • the device may be AF, a device in AF, or a device that can be used in conjunction with AF.
  • the device may be a chip system.
  • the chip system may be composed of chips, or may include chips and other discrete devices.
  • the communication apparatus 1000 includes at least one processor 1020, configured to implement the functions of the CCF, APF, or AF in the methods provided in the embodiments of the present application.
  • the apparatus 1000 may also include a communication interface 1010 .
  • the communication interface may be a transceiver, a circuit, a bus, a module, or other types of communication interfaces, which are used to communicate with other devices through a transmission medium.
  • the communication interface 1010 is used for the apparatus in the communication apparatus 1000 to communicate with other devices.
  • the processor 1020 uses the communication interface 1010 to send and receive data, and is used to implement the methods described in the above method embodiments.
  • the processor 1020 is configured to call the communication interface 1010 to perform the following operations:
  • the service API release request is used to request the release of the API service of the user plane function UPF;
  • the service API release request carries the API information, and the API information includes the N6 information and/or service description information of the UPF.
  • the UPF is used to transmit data of the first service of the terminal device.
  • the processor 1020 is configured to acquire the service application programming interface API information of the user plane function UPF, the API information includes the N6 information and/or service description information of the UPF, and the service description information is used to identify the first service,
  • the UPF is used to transmit data of the first service of the terminal device.
  • the processor 1020 calls the communication interface 1010 to send a service API release request to the CCF, and the service API release request is used to request release of the API service of the UPF; the service API release request carries API information.
  • the processor 1020 calls the communication interface 1010 to perform the following operations: send an application programming interface (API) discovery request to the common application programming interface framework core function CCF, and the API discovery request carries any one or more of the following information: Terminal The address information of the device, the N6 information of the user plane function UPF, or the service description information, the service description information is used to identify the first service, and the UPF is used to transmit the data of the first service of the terminal device; identification; sending the N6 information and/or service description information of the UPF to the SMF; receiving the identification of the UPF from the SMF, and the identification of the UPF is associated with the N6 information and/or service description information of the UPF.
  • API application programming interface
  • the processor 1020 and the communication interface 1010 may also be configured to perform other corresponding steps or operations performed by the CCF, APF, or AF in the above method embodiments, which will not be repeated here.
  • Communication apparatus 1000 may also include at least one memory 1030 for storing program instructions and/or data.
  • Memory 1030 is coupled to processor 1020 .
  • the coupling in the embodiments of the present application is an indirect coupling or communication connection between devices, units or modules, which may be in electrical, mechanical or other forms, and is used for information exchange between devices, units or modules.
  • the processor 1020 may cooperate with the memory 1030 .
  • Processor 1020 may execute program instructions stored in memory 1030 . At least one of the at least one memory may be integrated with the processor.
  • the memory 1030 may be a non-volatile memory, such as a hard disk drive (HDD) or a solid-state drive (SSD), etc., or a volatile memory (volatile memory), Such as random-access memory (random-access memory, RAM).
  • Memory is, but is not limited to, any other medium that can be used to carry or store desired program code in the form of instructions or data structures and that can be accessed by a computer.
  • the memory in this embodiment of the present application may also be a circuit or any other device capable of implementing a storage function, for storing program instructions and/or data.
  • the specific connection medium between the communication interface 1010 , the processor 1020 , and the memory 1030 is not limited in this embodiment of the present application.
  • the memory 1030, the processor 1020, and the communication interface 1010 are connected through a bus 1040 in FIG. 10.
  • the bus is represented by a thick line in FIG. 10, and the connection between other components is only for schematic illustration. , is not limited.
  • the bus can be divided into an address bus, a data bus, a control bus, and the like. For ease of presentation, only one thick line is used in FIG. 10, but it does not mean that there is only one bus or one type of bus.
  • the communication module 901 and the communication interface 1010 may output or receive baseband signals.
  • the output or reception of the communication module 901 and the communication interface 1010 may be radio frequency signals.
  • the processor may be a general-purpose processor, a digital signal processor, an application-specific integrated circuit, a field programmable gate array or other programmable logic device, a discrete gate or transistor logic device, or a discrete hardware component, which can implement or The methods, steps and logic block diagrams disclosed in the embodiments of this application are executed.
  • a general purpose processor may be a microprocessor or any conventional processor or the like. The steps of the method disclosed in conjunction with the embodiments of the present application may be directly embodied as executed by a hardware processor, or executed by a combination of hardware and software modules in the processor.
  • Some or all of the operations and functions performed by the CCF, APF, or AF described in the above method embodiments of this application, or some or all of the operations and functions performed by the CCF, APF, or AF, may be performed by a chip or an integrated circuit. Finish.
  • an embodiment of the present application further provides a chip, including a processor, for supporting the communication apparatus to implement the first network device or the AMF involved in the above method embodiment. function.
  • the chip is connected to a memory or the chip includes a memory for storing necessary program instructions and data of the communication device.
  • An embodiment of the present application provides a computer-readable storage medium storing a computer program, where the computer program includes instructions for executing the foregoing method embodiments.
  • the embodiments of the present application provide a computer program product containing instructions, which, when executed on a computer, cause the above method embodiments to be executed.
  • the embodiments of the present application may be provided as a method, a system, or a computer program product. Accordingly, the present application may take the form of an entirely hardware embodiment, an entirely software embodiment, or an embodiment combining software and hardware aspects. Furthermore, the present application may take the form of a computer program product embodied on one or more computer-usable storage media (including, but not limited to, disk storage, CD-ROM, optical storage, etc.) having computer-usable program code embodied therein.
  • computer-usable storage media including, but not limited to, disk storage, CD-ROM, optical storage, etc.
  • These computer program instructions may also be stored in a computer-readable memory capable of directing a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer-readable memory result in an article of manufacture comprising instruction means, the instructions
  • the apparatus implements the functions specified in the flow or flow of the flowcharts and/or the block or blocks of the block diagrams.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Computer And Data Communications (AREA)

Abstract

L'invention concerne un procédé et un appareil de communication. Le procédé comprend les étapes suivantes : une fonction de publication d'interface de programmation d'application (APF) acquiert des informations d'interface de programmation d'application (API) de service d'une fonction de plan utilisateur (UPF), les informations d'API comprenant des informations N6 et/ou des informations de description de service de l'UPF, les informations de description de service étant utilisées pour identifier un premier service, et l'UPF étant utilisée pour transmettre des données d'un premier service d'un dispositif de terminal ; et l'APF envoie une demande de publication d'API de service à une CCF, et la CCF reçoit la demande de publication d'API à partir de l'APF, la demande de publication d'API de service transportant les informations d'API. Au moyen du transport d'informations d'API dans une demande de publication d'API de service, des informations N6 et des informations de description de service peuvent toutes être associées à une certaine UPF spécifique, et un service d'API d'une UPF que la demande de publication d'API de service demande de publier se rapporte à une UPF correspondant aux informations d'API, de sorte qu'une AF puisse découvrir l'UPF spécifique.
PCT/CN2020/119592 2020-09-30 2020-09-30 Procédé et appareil de communication Ceased WO2022067736A1 (fr)

Priority Applications (1)

Application Number Priority Date Filing Date Title
PCT/CN2020/119592 WO2022067736A1 (fr) 2020-09-30 2020-09-30 Procédé et appareil de communication

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2020/119592 WO2022067736A1 (fr) 2020-09-30 2020-09-30 Procédé et appareil de communication

Publications (1)

Publication Number Publication Date
WO2022067736A1 true WO2022067736A1 (fr) 2022-04-07

Family

ID=80951086

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2020/119592 Ceased WO2022067736A1 (fr) 2020-09-30 2020-09-30 Procédé et appareil de communication

Country Status (1)

Country Link
WO (1) WO2022067736A1 (fr)

Cited By (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2024067313A1 (fr) * 2022-09-30 2024-04-04 华为技术有限公司 Procédé et appareil de communication
US12580993B2 (en) * 2023-05-19 2026-03-17 Samsung Electronics Co., Ltd. Method and apparatus for discovering user plane function UPF in wireless communication system
WO2026067417A1 (fr) * 2024-09-26 2026-04-02 华为技术有限公司 Procédé et appareil de découverte d'élément de réseau

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN110362412A (zh) * 2018-04-09 2019-10-22 华为技术有限公司 一种服务api调用方法和相关装置
WO2020001649A1 (fr) * 2018-06-30 2020-01-02 华为技术有限公司 Procédé et appareil de communication
CN111148076A (zh) * 2018-11-05 2020-05-12 华为技术有限公司 一种api发布方法及装置
CN111435924A (zh) * 2019-01-14 2020-07-21 华为技术有限公司 调用应用程序接口的方法和装置

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN110362412A (zh) * 2018-04-09 2019-10-22 华为技术有限公司 一种服务api调用方法和相关装置
WO2020001649A1 (fr) * 2018-06-30 2020-01-02 华为技术有限公司 Procédé et appareil de communication
CN111148076A (zh) * 2018-11-05 2020-05-12 华为技术有限公司 一种api发布方法及装置
CN111435924A (zh) * 2019-01-14 2020-07-21 华为技术有限公司 调用应用程序接口的方法和装置

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
SAMSUNG, KDDI: "Proposal for use of CAPIF for eSBA Framework", 3GPP DRAFT; S2-188949 PROPOSAL FOR USE OF CAPIF FOR ESBA FRAMEWORK (WAS 8816), 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. SA WG2, no. Sophia Antipolis, France; 20180820 - 20180824, 26 August 2018 (2018-08-26), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France , XP051537718 *

Cited By (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2024067313A1 (fr) * 2022-09-30 2024-04-04 华为技术有限公司 Procédé et appareil de communication
US12580993B2 (en) * 2023-05-19 2026-03-17 Samsung Electronics Co., Ltd. Method and apparatus for discovering user plane function UPF in wireless communication system
WO2026067417A1 (fr) * 2024-09-26 2026-04-02 华为技术有限公司 Procédé et appareil de découverte d'élément de réseau

Similar Documents

Publication Publication Date Title
US11917498B2 (en) Communication method and communications apparatus
US11844014B2 (en) Service authorization for indirect communication in a communication system
CN112449315B (zh) 一种网络切片的管理方法及相关装置
CN113973322B (zh) 一种通信方法及装置
WO2020200066A1 (fr) Procédé, système et appareil d'acquisition de paramètre de latence de paquet de données
CN113453292B (zh) 一种建立连接的方法和通信装置以及系统
WO2022222817A1 (fr) Procédé et appareil de sélection de serveur d'application d'extrémité
US12363583B2 (en) Parameter configuration method, apparatus and system, device and storage medium
WO2022222745A1 (fr) Procédé et appareil de communication
WO2021094349A1 (fr) Autorisation de services en plusieurs étapes pour la communication indirecte dans un système de communication
US20240380848A1 (en) Communication method and apparatus
WO2023051381A1 (fr) Procédé et appareil de détermination de serveur d'application
CN115708385A (zh) 一种通信方法及通信装置
WO2022237857A1 (fr) Procédé de détermination de mode d'activation de protection de sécurité, procédé de communication et appareil de communication
WO2022067736A1 (fr) Procédé et appareil de communication
WO2021204277A1 (fr) Procédé, appareil et système de communication
WO2022001972A1 (fr) Procédé de résolution de demande dns, appareil de communication et système de communication
US20220353340A1 (en) Communication Method and Communication Apparatus
CN120380786A (zh) 用于针对归属路由会话疏导向vplmn传达业务卸载策略的方法和装置
WO2024012230A1 (fr) Procédé et appareil de communication
WO2023116356A1 (fr) Procédé et appareil de configuration d'informations, dispositifs associés et support de stockage associé
CN116647832A (zh) 一种通信方法及装置
WO2022165787A1 (fr) Procédé et appareil de configuration de paramètres, dispositif, et support de stockage
WO2022056794A1 (fr) Procédé et appareil de communication
US20260040051A1 (en) Communication Method and Communication Apparatus

Legal Events

Date Code Title Description
NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 20955760

Country of ref document: EP

Kind code of ref document: A1