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

Procédé de communication et appareil de communication Download PDF

Info

Publication number
WO2023185561A1
WO2023185561A1 PCT/CN2023/082937 CN2023082937W WO2023185561A1 WO 2023185561 A1 WO2023185561 A1 WO 2023185561A1 CN 2023082937 W CN2023082937 W CN 2023082937W WO 2023185561 A1 WO2023185561 A1 WO 2023185561A1
Authority
WO
WIPO (PCT)
Prior art keywords
function entity
service discovery
discovery function
information
service
Prior art date
Application number
PCT/CN2023/082937
Other languages
English (en)
Chinese (zh)
Inventor
陈泽昊
李永翠
倪慧
Original Assignee
华为技术有限公司
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 华为技术有限公司 filed Critical 华为技术有限公司
Publication of WO2023185561A1 publication Critical patent/WO2023185561A1/fr

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/0005—Control or signalling for completing the hand-off
    • H04W36/0011—Control or signalling for completing the hand-off for data sessions of end-to-end connection
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/14—Reselecting a network or an air interface
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W48/00—Access restriction; Network selection; Access point selection
    • H04W48/16—Discovering, processing access restriction or access information
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W48/00—Access restriction; Network selection; Access point selection
    • H04W48/18—Selecting a network or a communication service
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/10—Connection setup
    • H04W76/11—Allocation or use of connection identifiers
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W8/00—Network data management
    • H04W8/26—Network addressing or numbering for mobility support

Definitions

  • the embodiments of the present application relate to the field of communication, and, more specifically, to communication methods and communication devices.
  • the terminal equipment In the home routed (HR) roaming scenario, the terminal equipment (user equipment, UE) may simultaneously perceive the mobile devices deployed in the home public land mobile network (HPLMN) and visited PLMN (visited PLMN, VPLMN).
  • HPLMN home public land mobile network
  • VPLMN visited PLMN
  • Business discovery functional entity since HPLMN and VPLMN may deploy a variety of services, the domain name system (domain name system, DNS) processing rules configured by the service discovery functional entities of different PLMNs may also be different.
  • domain name system domain name system, DNS
  • Embodiments of the present application provide a communication method and communication device, which can enable the UE to select an appropriate service discovery function entity and improve the user's experience of accessing the service.
  • a communication method is provided.
  • the method may be executed by the first session management network element, or may be executed by a component (such as a chip or circuit) of the first session management network element.
  • a component such as a chip or circuit
  • the method will be executed by the first session management network element below.
  • Network element execution is taken as an example for explanation.
  • the method may include: the first session management network element obtains service discovery function entity selection information, the service discovery function entity selection information includes information of the first service discovery function entity and information of the second service discovery function entity, the first service discovery function entity The entity is deployed in the visited public land mobile network, and the second service discovery function entity is deployed in the home public land mobile network; the first session management network element sends service discovery function entity selection information to the terminal device, and the service discovery function entity selection information is used to determine the target
  • the service discovery function entity is a target service discovery function entity used to discover services to be accessed for the terminal device.
  • the first session management network element obtains and sends the service discovery function entity selection information to the UE.
  • the service discovery function entity selection information includes the information of the first service discovery function entity deployed in the VPLMN and the second service discovery deployed in the HPLMN. Functional entity information, so that the service discovery function entity selection information can be used to determine the service discovery function entity among multiple service discovery function entities deployed in different PLMNs, which is conducive to reasonable service discovery, thereby improving the user experience of accessing services. .
  • the information of the first service discovery function entity includes one or more of the following information: the address of the first service discovery function entity, the first service identifier, the visited public land mobile network network identification, the priority of the information of the first service discovery function entity;
  • the information of the second service discovery function entity includes one or more of the following information: the address of the second service discovery function entity, the second service identifier, the home public land mobile The network identifier and the priority of the information of the second service discovery function entity.
  • the information of the first service discovery function entity and the information of the second service discovery function entity may be used to determine the service discovery function entity among multiple service discovery function entities deployed in different PLMNs.
  • the address of the first service discovery function entity and the address of the second service discovery function entity are used to send corresponding information to the corresponding service discovery function entity.
  • the first service identifier and the second service identifier are used to identify the service to be accessed. Matching is performed to determine the PLMN where the service to be accessed is deployed.
  • the visiting public land mobile network identifier and the home public land mobile network identifier are used to determine the deployed PLMN, the priority of the information of the first service discovery function entity and the second service discovery function.
  • the priority of the entity information is used to determine the service discovery function for the UE access service.
  • the first service discovery function entity corresponds to the session of the terminal device
  • the second service discovery function entity corresponds to the session of the terminal device
  • the information of the second service discovery function entity is the first information of the second service discovery function entity
  • the first session management network element obtains the service discovery function entity selection information
  • the method includes: the first session management network element determines the information of the first service discovery function entity; the first session management network element receives the second information of the second service discovery function entity from the second session management network element; the first session management network element
  • the service discovery function entity selection information is determined according to the information of the first service discovery function entity and the second information of the second service discovery function entity; wherein, the first session management network element is deployed in the visited public land mobile network, and the second session management network element Deployed on the home public land mobile network.
  • the first session management network element deployed in the VPLMN can determine the service discovery function entity selection information including VPLMN and HPLMN related information, which is used to perform service discovery function entities among multiple service discovery function entities deployed in different PLMNs.
  • the information of the first service discovery functional entity includes a first service identifier
  • the first information of the second service discovery function entity includes a second service identifier
  • the second service discovery The second information of the functional entity includes a third service identifier
  • both the third service identifier and the first service identifier include a common service identifier
  • the second service identifier does not include a common service identifier. That is, when determining the service discovery function entity selection information, the first session management network element deduplicates the common service identifier contained in both the information of the first service discovery function entity and the second information of the second service discovery function entity. , then the second information of the second service discovery function entity in the service discovery function entity selection information does not include the common service identifier.
  • the method before the first session management network element obtains the service discovery function entity selection information, the method further includes: the first session management network element receives the service discovery function entity selection information from the second session management network element.
  • the first indication information is used to indicate determining the service discovery function entity selection information.
  • the first SMF can determine the service discovery function entity selection information according to the first indication information, which increases the flexibility of the solution.
  • the method further includes: second session management The network element sends the information of the second service discovery function entity to the terminal device.
  • the second SMF deployed in the HPLMN can send the updated information of the second service discovery function entity to the UE for use in multiple PLMNs deployed in different PLMNs.
  • the business discovery functional entity is determined in the business discovery functional entity.
  • the visited public land mobile network is the first visited public land mobile network
  • the second session management network element learns that the terminal device switches from the first visited public land mobile network to When the public land mobile network is visited for the second time, the method further includes: the second session management network element sending information of the second service discovery function entity and information of the service discovery function entity of the second visited public land mobile network to the terminal device.
  • the second SMF deployed in the HPLMN can send the updated information of the second service discovery function entity and the information of the service discovery function entity deployed in the other VPLMN to the UE. , used to determine the service discovery function entity among multiple service discovery function entities deployed in different PLMNs.
  • the first session management network element obtains the service discovery function entity selection information, including: the first session management network element receives the first service from the second session management network element. Discovery function entity information; the first session management network element determines the information of the second service discovery function entity; the first session management network element determines the service discovery function based on the information of the first service discovery function entity and the information of the second service discovery function entity Entity selection information; wherein, the first session management network element is deployed in the home public land mobile network; the second session management network element is deployed in the visited public land mobile network.
  • the first session management network element deployed in HPLMN can determine the service discovery function entity selection information including VPLMN and HPLMN related information, which is used to perform service discovery function entity selection among multiple service discovery function entities deployed in different PLMNs.
  • the information of the second service discovery function entity and the information of the first service discovery function entity do not include a common service identifier.
  • the method before the first session management network element receives the information from the first service discovery function entity of the second session management network element, the method further includes: first session management The network element sends a request message to the second session management network element, where the request message is used to request to obtain the information of the first service discovery function entity.
  • the first SMF can obtain the information of the first service discovery function entity by sending a request message, which increases the flexibility of the solution.
  • the method further includes: first session management The network element sends the information of the second service discovery function entity to the terminal device.
  • the first SMF deployed in the HPLMN can send updated service discovery function entity selection information to the UE for performing services in multiple service discovery function entities deployed in different PLMNs. Discover the identification of functional entities.
  • the visited public land mobile network is the first visited public land mobile network
  • the method further includes: the first session management network element sending the information of the second service discovery function entity and the information of the service discovery function entity of the second visited public land mobile network to the terminal device.
  • the first SMF deployed in the HPLMN can send updated service discovery function entity selection information and service discovery function entity information deployed in another VPLMN to the UE for
  • the service discovery function entity is determined among multiple service discovery function entities deployed in different PLMNs.
  • the second aspect provides a communication method.
  • the method may be executed by the terminal device, or may be executed by a component (such as a chip or circuit) of the terminal device, which is not limited.
  • a component such as a chip or circuit
  • the method will be described below by taking execution by the terminal device as an example.
  • the method includes: the terminal device determines a target service discovery function entity according to the service discovery function entity selection information.
  • the target service discovery function entity is used to discover services to be accessed for the terminal device.
  • the service discovery function entity selection information includes the first service discovery function.
  • the information of the entity and the information of the second service discovery function entity, the first service discovery function entity is deployed in the visiting public land mobile network, and the second service discovery function entity is deployed in the home public land mobile network; the terminal device sends the information to the target service discovery function entity Domain name system query messages.
  • the UE can determine the service discovery function entity among multiple service discovery function entities deployed in different PLMNs based on the service discovery function entity selection information.
  • the service discovery function entity selection information includes the first service discovery deployed in the VPLMN.
  • the information of the functional entity and the information of the second service discovery functional entity deployed in the HPLMN are conducive to reasonable service discovery, thereby improving the user experience of accessing the service.
  • the method further includes: the terminal device receiving service discovery function entity selection information from the first session management network element.
  • the UE can obtain the service discovery function entity selection information through the first session management network element, which increases the flexibility of the solution for obtaining the service discovery function entity selection information.
  • the information of the first service discovery function entity includes one or more of the following information: the address of the first service discovery function entity, the first service identifier, the visited public land Mobile network identification, priority of the information of the first service discovery function entity;
  • information of the second service discovery function entity includes one or more of the following information: address of the second service discovery function entity, second service identification, home public land The mobile network identification and the priority of the information of the second service discovery function entity.
  • the information of the first service discovery function entity and the information of the second service discovery function entity may be used to determine the service discovery function entity among multiple service discovery function entities deployed in different PLMNs.
  • the terminal device determines the target service discovery function entity according to the service discovery function entity selection information, including: the terminal device selects the service discovery function entity according to the identifier of the service to be accessed and the service discovery function entity information to determine the target business discovery functional entity.
  • the UE can determine the address of the service discovery function entity of the access service according to the identifier of the service to be accessed, which increases the flexibility of the solution.
  • the visited public land mobile network is the first visited public land mobile network
  • the terminal device switches from the first visited public land mobile network to the second visited public land mobile network
  • the method further includes: the terminal device receiving information from a second service discovery function entity deployed in the session management network element of the home public land mobile network and information from the second service discovery function entity of the visiting public land mobile network.
  • the UE when the UE switches from one VPLMN to another VPLMN, the UE can receive the updated second service discovery function entity information from the second SMF deployed in the HPLMN and the service discovery function deployed in the other VPLMN. Entity information, thereby enabling the UE to determine the service discovery function entity among multiple service discovery function entities deployed in different PLMNs.
  • the terminal device determines the target service discovery function entity according to the service discovery function entity selection information, including: the terminal device determines the target service discovery function entity according to the accessed public land mobile network, the to-be-served Enter the service identification and service discovery function entity selection information to determine the target service discovery function entity.
  • the UE can determine the address of the service discovery function entity of the access service according to the accessed PLMN and the identity of the service to be accessed, which increases the flexibility of the solution.
  • the third aspect provides a communication method.
  • This method can be executed by the access management network element, or it can also be executed by the component (such as a chip or circuit) of the access management network element. There is no limitation on this. For the convenience of description, below it is assumed that it is executed by the access management network element. Take an example to illustrate.
  • the method may include: the access management network element obtains service discovery function entity selection information, the service discovery function entity selection information is used to determine a target service discovery function entity, and the target service discovery function entity is used to discover services to be accessed for the terminal device;
  • the access management network element sends service discovery function entity selection information to the terminal device; wherein the service discovery function entity selection information includes the public land mobile network identifier corresponding to at least one service discovery function entity and the address of at least one service discovery function entity.
  • the access management network element obtains and sends the service discovery function entity selection information to the UE.
  • the service discovery function entity selection information can be used to determine the service discovery function entity among multiple service discovery function entities deployed in different PLMNs. , which is conducive to reasonable service discovery, thereby improving the user experience of accessing services.
  • the service discovery function entity selection information also includes one or more of the following information of at least one service discovery function entity: the data network name corresponding to at least one service discovery function entity , single network slice selection auxiliary information corresponding to at least one service discovery function entity, and a common service identifier corresponding to at least one service discovery function entity.
  • the access management network element obtains the service discovery function entity selection information, including: the access management network element receives service discovery from the data management network element or the policy control network element Functional entity selection information.
  • AMF can obtain the service discovery function entity selection information through the data management network element or the policy control network element, which increases the flexibility of the solution.
  • the fourth aspect provides a communication method.
  • the method may be executed by the terminal device, or may be executed by a component (such as a chip or circuit) of the terminal device, which is not limited.
  • a component such as a chip or circuit
  • the method will be described below by taking execution by the terminal device as an example.
  • the method includes: the terminal device determines a target service discovery function entity according to the service discovery function entity selection information, the target service discovery function entity is used to discover services to be accessed for the terminal device, and the service discovery function entity selection information includes at least one The public land mobile network identifier corresponding to the service discovery function entity and the address of at least one service discovery function entity; the terminal device sends a domain name system query message to the target service discovery function entity.
  • the UE can determine the service discovery function entity among multiple service discovery function entities deployed in different PLMNs based on the service discovery function entity selection information. This is conducive to reasonable service discovery, thereby improving the user's access to the service. experience.
  • the terminal device receives service discovery function entity selection information from the access management network element.
  • the UE can obtain the service discovery function entity selection information by accessing the management network element, which increases the flexibility of the solution for obtaining the service discovery function entity selection information.
  • the terminal device determines the target service discovery function entity according to the service discovery function entity selection information, including: the terminal device determines the target service discovery function entity according to the accessed public land mobile network and service Discover the functional entity selection information and determine the target service discovery functional entity.
  • the UE can determine the address of the service discovery function entity of the accessed service according to the identifier of the accessed service, which increases the flexibility of the solution.
  • the service discovery function entity selection information also includes one or more of the following information about at least one service discovery function entity: the data network name corresponding to at least one service discovery function entity , single network slice selection auxiliary information corresponding to at least one service discovery function entity, and a common service identifier corresponding to at least one service discovery function entity.
  • the terminal device determines the target service discovery function entity according to the service discovery function entity selection information, including: the terminal device determines the target service discovery function entity according to the accessed public land mobile network and session corresponding data. At least one of the network name, the single network slice selection auxiliary information corresponding to the session, the identification of the service to be accessed, and the service discovery function entity selection information determines the target service discovery function entity.
  • the UE can determine the address of the service discovery function entity of the access service based on the identifier of the accessed service, the DNN corresponding to the session, the S-NSSAI corresponding to the session, etc., which increases the flexibility of the solution.
  • a communication device including one or more units for executing the method shown in the first aspect.
  • the communication device may be a first session management network element, or may be configured in The chip or circuit in the first session management network element is executed, and this application does not limit this.
  • the communication device includes:
  • a processing unit configured to obtain service discovery function entity selection information.
  • the service discovery function entity selection information includes information of a first service discovery function entity and information of a second service discovery function entity.
  • the first service discovery function entity is deployed on a visiting public land.
  • the second service discovery function entity is deployed in the home public land mobile network;
  • the transceiver unit is used to send service discovery function entity selection information to the terminal device, and the service discovery function entity selection information is used to determine the target service discovery function entity, and the target The service discovery function entity is used to discover services to be accessed for the terminal device.
  • the information of the first service discovery function entity includes one or more of the following information: the address of the first service discovery function entity, the first service identifier, the visited public land Mobile network identification, priority of the information of the first service discovery function entity;
  • information of the second service discovery function entity includes one or more of the following information: address of the second service discovery function entity, second service identification, home public land The mobile network identification and the priority of the information of the second service discovery function entity.
  • the first service discovery function entity corresponds to the session of the terminal device
  • the second service discovery function entity corresponds to the session of the terminal device
  • the processing unit is also used to determine the information of the first service discovery function entity; the transceiver unit is also used to receive the second service from the second session management network element.
  • the second information of the discovery function entity; the processing unit is also configured to determine the service discovery function entity selection information according to the information of the first service discovery function entity and the second information of the second service discovery function entity; wherein, the first session management network element Deployed in the visited public land mobile network, the second session management network element is deployed in the home public land mobile network.
  • the information of the first service discovery functional entity includes a first service identification
  • the first information of the second service discovery functional entity includes a second service identification
  • the second information of the functional entity includes a third service identifier
  • both the third service identifier and the first service identifier include a common service identifier
  • the second service identifier does not include a common service identifier.
  • the transceiver unit is also configured to receive messages from the second session First indication information of the management network element, the first indication information is used to indicate determining the service discovery function entity selection information.
  • the transceiver unit is also configured to send information about the second service discovery function entity to the terminal device.
  • the transceiver unit is further configured to send information about the second service discovery function entity and information about the second service discovery function entity visiting the public land mobile network to the terminal device.
  • the transceiver unit is also used to receive information from the first service discovery function entity of the second session management network element; the processing unit is also used to determine the second service Discovery function entity information; the processing unit is also configured to determine service discovery function entity selection information according to the information of the first service discovery function entity and the information of the second service discovery function entity; wherein the first session management network element is deployed in the belonging public Land mobile network; the second session management network element is deployed in the access public land mobile network.
  • the information of the second service discovery function entity and the information of the first service discovery function entity do not include a common service identifier.
  • the transceiver unit is further configured to send a request message to the second session management network element, where the request message is used to request acquisition of information of the first service discovery function entity.
  • the transceiver unit is also configured to send information about the second service discovery function entity to the terminal device.
  • the transceiver unit is further configured to send information about the second service discovery function entity and information about the second service discovery function entity visiting the public land mobile network to the terminal device.
  • a sixth aspect provides a communication device, including one or more units for executing the method shown in the second aspect.
  • the communication device may be a terminal device, or may also be a device provided in the terminal device. Chip or circuit execution, this application does not limit this.
  • the communication device includes:
  • a processing unit configured to determine a target service discovery function entity according to the service discovery function entity selection information.
  • the target service discovery function entity is used to discover services to be accessed for the terminal device.
  • the service discovery function entity selection information includes the first service discovery function entity. information and information of the second service discovery function entity, the first service discovery function entity is deployed in the visited public land mobile network, and the second service discovery function entity is deployed in the home public land mobile network; the transceiver unit is used to provide the target service discovery function
  • the entity sends a domain name system query message.
  • the transceiver unit is also configured to receive service discovery function entity selection information from the first session management network element.
  • the information of the first service discovery function entity includes one or more of the following information: the address of the first service discovery function entity, the first service identifier, the visited public land Mobile network identification, priority of the information of the first service discovery function entity;
  • information of the second service discovery function entity includes one or more of the following information: address of the second service discovery function entity, second service identification, home public land The mobile network identification and the priority of the information of the second service discovery function entity.
  • the processing unit is further configured to determine the target service discovery function entity based on the identifier of the service to be accessed and the service discovery function entity selection information.
  • the transceiver unit is also used to receive signals from the home deployment The information of the second service discovery function entity of the session management network element belonging to the public land mobile network and the information of the second service discovery function entity of the visiting public land mobile network.
  • the processing unit is also configured to determine the target service discovery function based on the accessed public land mobile network, the identifier of the service to be accessed, and the service discovery function entity selection information. entity.
  • a seventh aspect provides a communication device, including one or more units for executing the method shown in the third aspect.
  • the communication device may be an access management network element, or may be configured on an access management network element.
  • the chip or circuit implemented in the management network element is not limited in this application.
  • the communication device includes:
  • the processing unit is used to obtain the service discovery function entity selection information.
  • the service discovery function entity selection information is used to determine the target service discovery function entity.
  • the target service discovery function entity is used to discover services to be accessed for the terminal device;
  • the transceiver unit is used to Send service discovery function entity selection information to the terminal device; wherein the service discovery function entity selection information includes a public land mobile network identifier corresponding to at least one service discovery function entity and an address of at least one service discovery function entity.
  • the service discovery function entity selection information also includes one or more of the following information about at least one service discovery function entity: the data network name corresponding to at least one service discovery function entity , single network slice selection auxiliary information corresponding to at least one service discovery function entity, and a common service identifier corresponding to at least one service discovery function entity.
  • the transceiver unit is also configured to receive service discovery function entity selection information from the data management network element or the policy control network element.
  • a communication device including one or more units for executing the method shown in the fourth aspect.
  • the communication device may be a terminal device, or may be a device provided in the terminal device. Chip or circuit execution, this application does not limit this.
  • the communication device includes:
  • a processing unit configured to determine a target service discovery function entity according to the service discovery function entity selection information.
  • the target service discovery function entity is used to discover services to be accessed for the terminal device.
  • the service discovery function entity selection information includes at least one service.
  • the public land mobile network identifier corresponding to the discovery function entity and the address of at least one service discovery function entity; the sending and receiving unit is used to send a domain name system query message to the target service discovery function entity.
  • the transceiver unit is also configured to receive service discovery function entity selection information from the access management network element.
  • the processing unit is further configured to determine the target service discovery function entity based on the accessed public land mobile network and the service discovery function entity selection information.
  • the service discovery function entity selection information also includes one or more of the following information about at least one service discovery function entity: a data network name corresponding to at least one service discovery function entity , single network slice selection auxiliary information corresponding to at least one service discovery function entity, at least one service Discover the common business identifier corresponding to the functional entity.
  • the processing unit is also configured to select the auxiliary information, the to-be-received data network according to the accessed public land mobile network, the data network name corresponding to the session, and the single network slice corresponding to the session. Enter at least one of the identifiers of the service to determine the target service discovery functional entity.
  • a ninth aspect provides a communication device, which includes: a memory for storing a program; and at least one processor for executing the computer program or instructions stored in the memory to execute any one of the above first to fifth aspects. possible implementation methods.
  • the device is a first session management network element.
  • the device is a chip, chip system or circuit used in the first session management network element.
  • this application provides a processor for executing the methods provided in the above aspects.
  • processor output, reception, input and other operations can be understood as processor output, reception, input and other operations.
  • transmitting and receiving operations performed by the radio frequency circuit and the antenna, which is not limited in this application.
  • a computer-readable storage medium stores a program code for device execution.
  • the program code includes a possible implementation manner for executing any one of the above-mentioned first to fourth aspects. Methods.
  • a computer program product containing instructions is provided.
  • the computer program product When the computer program product is run on a computer, it causes the computer to execute the method of any one of the possible implementation methods of the first to fourth aspects.
  • a chip in a thirteenth aspect, includes a processor and a communication interface.
  • the processor reads instructions stored in the memory through the communication interface and executes any of the possible implementation methods of the first to fourth aspects.
  • the chip also includes a memory, in which computer programs or instructions are stored.
  • the processor is used to execute the computer programs or instructions stored in the memory.
  • the processor is used to execute Any possible implementation method of any of the above first to fourth aspects.
  • a fourteenth aspect provides a communication system, including one or more of the following devices for implementing the technical solution of the present application: a first session management network element, a second session management network element, a terminal device or a service discovery function entity.
  • a communication system including one or more of the following devices for implementing the technical solution of the present application: access management network element, terminal device, service discovery functional entity, data management network element, or policy control network Yuan.
  • Figure 1 shows a schematic diagram of a network architecture suitable for embodiments of the present application.
  • Figure 2 shows a schematic diagram of a communication method 200 provided by an embodiment of the present application.
  • Figure 3 shows a schematic flow chart of a communication method 300 provided by the embodiment of the present application.
  • Figure 4 shows a schematic flowchart of a communication method 400 when a PLMN handover occurs provided by the embodiment of the present application.
  • Figure 5 shows a schematic flow chart of a communication method 500 provided by the embodiment of the present application.
  • Figure 6 shows a schematic flow chart of a communication method 600 provided by the embodiment of the present application.
  • Figure 7 shows a schematic block diagram of a communication device 700 provided by an embodiment of the present application.
  • Figure 8 shows a schematic block diagram of another communication device 800 provided by an embodiment of the present application.
  • FIG. 9 shows a schematic diagram of a chip system 900 provided by an embodiment of the present application.
  • the technical solutions of the embodiments of this application can be applied to various communication systems, such as: fifth generation (5th generation, 5G) or new radio (new radio, NR) systems, satellite communications, long term evolution (long term evolution, LTE) systems , LTE frequency division duplex (FDD) system, LTE time division duplex (TDD), etc.
  • the technical solution provided by this application can also be applied to future communication systems, such as the sixth generation mobile communication system.
  • the technical solutions of the embodiments of this application can also be applied to device-to-device (D2D) communication, vehicle-to-everything (V2X) communication, machine-to-machine (M2M) communication, and machine-to-machine (M2M) communication.
  • Machine type communication (MTC) industrial control
  • intelligent transportation system (ITS) mobile broadband
  • FIG. 1 shows a schematic diagram of a network architecture suitable for embodiments of the present application.
  • the network architecture may include, for example, but is not limited to the following: (radio) access network (R)AN) equipment, access management network elements, application network elements, data management network elements, user plane network elements, session management network elements, policy control network elements, network slice selection network elements, authentication service network elements, user equipment, etc.
  • R radio access network
  • User equipment It can be called terminal equipment, access terminal, user unit, user station, mobile station, mobile station, remote station, remote terminal, mobile device, user terminal, terminal, wireless communication equipment, User agent or user device.
  • the terminal device may be a device that provides voice/data to users, for example, a handheld device with wireless connection function, a vehicle-mounted device, etc.
  • terminals are: mobile phones, tablets, laptops, PDAs, mobile internet devices (MID), wearable devices, virtual reality (VR) devices, augmented reality (augmented reality, AR) equipment, wireless terminals in industrial control, wireless terminals in self-driving, wireless terminals in remote medical surgery, and smart grids Wireless terminals, wireless terminals in transportation safety, wireless terminals in smart cities, wireless terminals in smart homes, cellular phones, cordless phones, session initiation protocols , SIP) telephone, wireless local loop (WLL) station, personal digital assistant (personal digital assistant, PDA), handheld device with wireless communication capabilities, computing device or other processing device connected to a wireless modem, which can Wearable devices, terminal devices in the 5G network or terminal devices in the future evolved public land mobile communication network (public land mobile network, PLMN), etc., are not limited in the embodiments of this application.
  • MID mobile internet devices
  • the terminal device may also be a wearable device.
  • Wearable devices can also be called wearable smart devices. It is a general term for applying wearable technology to intelligently design daily wear and develop wearable devices, such as glasses, gloves, watches, clothing and shoes, etc.
  • a wearable device is a portable device that is worn directly on the body or integrated into the user's clothing or accessories. Wearable devices are not just hardware devices; Powerful functions are achieved through software support, data interaction, and cloud interaction.
  • wearable smart devices include full-featured, large-sized devices that can achieve complete or partial functions without relying on smartphones, such as smart watches or smart glasses, and those that only focus on a certain type of application function and need to cooperate with other devices such as smartphones.
  • the terminal device may also be a terminal device in the IoT system.
  • IoT is an important part of the future development of information technology. Its main technical feature is to connect objects to the network through communication technology, thereby realizing human-machine Interconnection, an intelligent network that interconnects things.
  • terminal equipment and access network equipment can communicate with each other using certain air interface technology (such as NR or LTE technology, etc.).
  • Terminal devices can also communicate with each other using some air interface technology (such as NR or LTE technology, etc.).
  • the device used to implement the functions of the terminal device may be a terminal device, or may be a device capable of supporting the terminal device to implement the function, such as a chip system or a chip, and the device may be installed in the terminal device.
  • the chip system may be composed of chips, or may include chips and other discrete devices.
  • (R)AN equipment It can provide authorized users in a specific area with the function of accessing the communication network. Specifically, it can include wireless network equipment in the 3rd generation partnership project (3GPP) network and can also include non-3GPP (non-3GPP) access point in the network. The following uses AN equipment representation for convenience of description.
  • 3GPP 3rd generation partnership project
  • non-3GPP non-3GPP
  • AN equipment can use different wireless access technologies.
  • 3GPP access technologies for example, wireless access technologies used in third generation (3G), fourth generation (4G) or 5G systems
  • non-3GPP non- 3GPP (non-3GPP) access technology.
  • 3GPP access technology refers to access technology that complies with 3GPP standard specifications.
  • the access network equipment in the 5G system is called next generation Node Base station (gNB) or RAN equipment.
  • Non-3GPP access technologies can include air interface technology represented by access point (AP) in wireless fidelity (WiFi), global interoperability for microwave access (WiMAX), code Code division multiple access (CDMA), etc.
  • AP access point
  • WiFi wireless fidelity
  • WiMAX global interoperability for microwave access
  • CDMA code Code division multiple access
  • AN equipment can allow interconnection and interworking between terminal equipment and the 3GPP core network using non-3GPP technologies.
  • AN equipment can be responsible for wireless resource management, quality of service (QoS) management, data compression and encryption on the air interface side.
  • AN equipment provides access services to terminal equipment, thereby completing the forwarding of control signals and user data between the terminal equipment and the core network.
  • QoS quality of service
  • AN equipment may include, for example, but is not limited to: macro base station, micro base station (also known as small station), radio network controller (radio network controller, RNC), Node B (Node B, NB), base station controller (base station controller) , BSC), base transceiver station (BTS), home base station (for example, home evolved NodeB, or home Node B, HNB), baseband unit (baseband unit, BBU), AP in WiFi system, wireless relay Node, wireless backhaul node, transmission point (TP) or transmission and reception point (TRP), etc., can also be a gNB or transmission point (TRP or TP) in the 5G (such as NR) system , one or a group (including multiple antenna panels) antenna panels of a base station in a 5G system, or it can also be a network node that constitutes a gNB or transmission point, such as a distributed unit (DU), or next-generation communications Base stations in 6G systems, etc.
  • RNC radio network controller
  • Access management network element mainly used for access control, mobility management, attachment and detachment and other functions. access pipe
  • the management network element can also serve as the anchor for the connection between N1 signaling (i.e., the signaling of the N1 interface, for simplicity, abbreviated as N1 signaling) and N2 signaling (i.e., the signaling of the N2 interface, for simplicity, abbreviation as N2 signaling). point to provide routing of N1/N2 session management (SM) messages for session management network elements.
  • the access management network element can also maintain and manage the status information of the UE.
  • the access management network element can access and mobility management functions (access and mobility management function, AMF).
  • AMF access and mobility management function
  • the access management network element may still be an AMF, or may have other names, which are not limited in this application.
  • Application network element It is mainly used to provide services to the 3GPP network, such as interacting with policy control network elements for policy control.
  • the application network element may be an application function (AF).
  • AF application function
  • the application network element can still be AF, or it can also have other names, which is not limited in this application.
  • Data management network element Mainly used for UE subscription data management, including storage and management of UE identification, UE access authorization, etc.
  • the data management network element can also generate 3GPP authentication credentials for the UE.
  • the data management network element can also register and maintain the network element currently serving the UE (for example, the AMF represented by AMF ID1 is the current serving AMF (serving AMF) of the UE).
  • the data management network element can be a unified data management (UDM) network element and/or a unified data repository (UDR) network element.
  • UDM unified data management
  • UDR unified data repository
  • data management network elements can still be UDM and/or UDR, or they can also have other names, which are not limited in this application.
  • User plane network element mainly used to process user messages, such as forwarding, accounting statistics, etc.
  • the UPF that is directly connected to the data network (DN) through N6 in the session is called the PDU session anchor (PSA).
  • the user plane network element may be a user plane function (UPF).
  • user plane network elements may still be UPF, or may have other names, which are not limited in this application.
  • Session management network element Mainly used for session management in mobile networks, such as session establishment, modification, and release. Specific functions include assigning IP addresses to users, selecting UPFs that provide packet forwarding functions, etc.
  • the session management network element may be a session management function (SMF).
  • SMF session management function
  • the session management network element may still be SMF, or may have other names, which are not limited in this application.
  • the session management network element is divided into home SMF (home SMF, H-SMF) and visited SMF (visited SMF, V-SMF).
  • Policy control network element Mainly used to support unified policy management of network behavior; provide policy rules to the control plane function for execution; obtain contract-related information from UDR to make policy decisions.
  • the policy control network element may be a policy control function (PCF).
  • PCF policy control function
  • the policy control network element may still be PCF, or may have other names, which are not limited in this application.
  • the policy control network element is divided into home PCF (home PCF, H-PCF) and visited PCF (visited PCF, V-PCF).
  • Network slice selection network element Mainly used to select the network slice instance set to serve the UE, determine the allowed network slice selection assistance information (NSSAI), and determine the single NSSAI to be signed when needed.
  • the mapping of (single-NSSAI, S-NSSAI) is also used to determine the configured NSSAI and the mapping to the subscribed S-NSSAI when needed. It is also used to determine the AMF set that may be used to query the UE, or based on Configure the list of candidate AMFs.
  • the network slice selection network element may be the network slice selection function (NSSF).
  • NSSF network slice selection function
  • network slicing selection network elements can still be NSSF, or they can have other names, which are not limited in this application.
  • network slicing selection network elements are divided into home NSSF (home NSSF, H-NSSF) and visited NSSF (visited NSSF, V-NSSF).
  • Authentication service network element Mainly used to authenticate the UE for the requester's network function (NF), provide key material to the requester NF, and protect the "guidance information list" of the requester NF.
  • the authentication service network element may be an authentication server function (AUSF).
  • AUSF authentication server function
  • the authentication service network element may still be AUSF, or may have other names, which are not limited in this application.
  • H-SMF, H-PCF, and H-NSSF are deployed in the home PLMN (home PLMN, HPLMN), and V-SMF, V-PCF, and V-NSSF are deployed in the visited PLMN (VPLMN). .
  • network elements can communicate with each other through the interfaces shown in the figure, and some interfaces can be implemented in the form of service-oriented interfaces.
  • communication between UE and AMF can be carried out through the N1 interface.
  • RAN and AMF can communicate through the N2 interface.
  • the relationship between other interfaces and each network element is shown in Figure 1. For the sake of simplicity, they will not be described in detail here.
  • network architecture shown above is only an illustrative description, and the network architecture applicable to the embodiments of the present application is not limited thereto. Any network architecture that can realize the functions of each of the above network elements is applicable to the embodiments of the present application.
  • the access management network element, application network element, data management network element, user plane network element, session management network element, etc. shown in Figure 1 can be understood as network elements used to implement different functions. For example, they can be These network elements need to be combined into network slices. These network elements can be independent devices, or they can be integrated into the same device to implement different functions, or they can be network elements in hardware devices, or they can be software functions running on dedicated hardware, or It is a virtualization function instantiated on a platform (for example, a cloud platform). This application does not limit the specific form of the above network element.
  • the above network elements or functions can be divided into one or more services, and further, there may also be services that exist independently of network functions.
  • instances of the above functions, or instances of services included in the above functions, or service instances that exist independently of network functions can be called service instances.
  • network elements with different functions can be co-located.
  • the access and mobility management network element can be co-located with the session management network element; the session management network element can be co-located with the user plane network element.
  • the public land mobile network that the UE subscribes to is called the home PLMN, which represents the home operator of the subscribed user.
  • the home PLMN which represents the home operator of the subscribed user.
  • a PLMN that meets the following conditions: it can cover the current location of the UE; or its operator has signed a roaming agreement with the operator of the UE's HPLMN ( A certain commercial agreement between operators, which may include but is not limited to issues such as services and billing methods for contracted users of the other operator's network), then the UE can access this PLMN, which is called a visited PLMN. .
  • the UE accessing the VPLMN is called roaming.
  • roaming scenarios can be divided into local breakout (LBO) roaming and home routed (HR) roaming.
  • LBO local breakout
  • HR home routed
  • EC realizes local processing of distributed business traffic and avoids excessive concentration of traffic, thus greatly reducing the specification requirements for core computer rooms and centralized gateways. At the same time, it shortens the distance of the backhaul network and reduces the end-to-end delay and jitter of user messages, making it possible to deploy ultra-low-latency services.
  • EAS Edge Application Servers
  • EASDF Edge Application Server Discovery Function
  • This application provides a communication method that enables the UE to select an appropriate service discovery function entity and improve the success rate of service access.
  • the communication method provided by the embodiment of the present application will be introduced below with reference to Figures 2 to 7. It should be understood that terms and identical steps in various embodiments of this application can be referred to each other.
  • Figure 2 is a schematic diagram of a communication method 200 provided by an embodiment of the present application.
  • Method 200 may include the following steps.
  • the first SMF obtains service discovery function entity selection information.
  • the business discovery function entity can be an edge application server discovery function (EASDF), a DNS server, or other domain name resolution functions/entities, entities with business discovery functions, or auxiliary business discovery Functions/entities, such as edge configuration server (ECS) or edge enabler server (EES), etc., are not restricted.
  • EASDF edge application server discovery function
  • DNS server DNS server
  • EES edge enabler server
  • the service discovery function entity is used to discover or provide the address or platform information of the service for the UE.
  • the service discovery function entity selection information is used to determine the target service discovery function entity.
  • service discovery function entity selection information can also be replaced with other names, such as service discovery function entity setting information, service discovery function entity configuration information, service discovery function entity usage information, service discovery function address information, etc., if the role of the information is the same as If the content is the same as or equivalent to the service discovery function entity selection information, it falls within the scope of protection of this application and will not be restricted.
  • the target service discovery function entity is used to assist the terminal device in discovering the service to be accessed.
  • the terminal device needs to access the service, it needs to determine the target service discovery function entity corresponding to the service to be accessed.
  • the terminal device passes The target service discovery function entity assists in discovering services to be accessed.
  • the service discovery function entity selection information includes information of the first service discovery function entity and information of the second service discovery function entity.
  • the first service discovery function entity is deployed in VPLMN.
  • the first service discovery function entity corresponds to a session of the terminal device.
  • the session correspondence between the first service discovery function entity and the terminal device may be that the first service discovery function entity serves one or more sessions of the terminal device.
  • EASDF assists the terminal device in performing service query through session granularity.
  • the information of the first service discovery function entity includes one or more of the following information: the address of the first service discovery function entity, the first service identification, VPLMNID, the priority of the information of the first service discovery function entity, etc. be restricted.
  • the address of the first service discovery function entity may be the IP address of the first service discovery function entity, etc., and is used for the terminal device to initiate service discovery. For example, the terminal device may subsequently send a request to the third service discovery function entity based on the address of the first service discovery function entity.
  • a service discovery function entity sends a domain name system query message.
  • the first service identifier is used to indicate the identifier of the service corresponding to the first service discovery function entity.
  • the identification of the service corresponding to the first service discovery function entity can be understood as, if the first service discovery function entity can perform or assist in performing the discovery of a certain service, then the service can be understood as the identification corresponding to the first service discovery function entity. business identity.
  • the first service identifier may identify one or more services.
  • the first service identifier may be one or more fully qualified domain names (FQDN), or one or more application (application, App) IDs, etc., without limitation.
  • FQDN fully qualified domain names
  • application application, App
  • the first service identifier can be described in the form of FQDN group, FQDN list, FQDN set, FQDN range, App ID group, App ID list, App ID set, App ID range, etc., without limitation.
  • the VPLMNID is the identifier of the above-mentioned VPLMN, that is, the identifier of the PLMN deployed by the first service discovery function entity.
  • the first service identifier may specifically be an identifier of a service deployed in the VPLMN, for example, the first service identifier
  • the first service identifier is the identifier of the service corresponding to the first service discovery functional entity
  • the first service identifier is the identifier of the service deployed in the VPLMN.
  • the deployment situation of a certain service identification can be understood as the deployment situation of the service corresponding to the service identification. If a certain service is deployed in a certain PLMN, it can be understood that the location where the service is deployed is covered by the network of the PLMN, or it can be understood that the service is allowed to be accessed through the PLMN.
  • the first service identifier may be the identifier of the service to be accessed through VPLMN.
  • the first service identifier is the identifier of the service corresponding to the first service discovery function entity.
  • the first service identifier is the identifier of the service to be accessed through the VPLMN.
  • the priority of the information of the first service discovery function entity is used to indicate the order in which the terminal device determines that the service discovery function entity to be accessed is discovered by the terminal device. Specifically, it can be a selection weight, or it can be reflected in the order in the list. wait.
  • the second service discovery function entity is deployed on HPLMN.
  • the second service discovery function entity corresponds to the session of the terminal device.
  • the session correspondence between the second service discovery function entity and the terminal device may be that the second service discovery function entity serves one or more sessions of the terminal device.
  • EASDF assists the terminal device in performing service query through session granularity.
  • the information of the second service discovery function entity includes one or more of the following information: the address of the second service discovery function entity, the second service identification, the HPLMN ID, the priority of the information of the second service discovery function entity, etc., No restrictions.
  • the address of the second service discovery function entity may specifically be the IP address of the second service discovery function entity, etc., which is used by the terminal device to initiate service discovery. For example, the terminal device may subsequently send a request to the third service discovery function entity based on the address of the second service discovery function entity.
  • the second service discovery function entity sends a domain name system query message.
  • the second service identifier is used to indicate the identifier of the service corresponding to the second service discovery function entity.
  • the service identifier corresponding to the second service discovery function entity can be understood as, if the second service discovery function entity can perform or assist in performing the discovery of a certain service, then the service can be understood as the service identifier corresponding to the second service discovery function entity. Business identification.
  • the second service identifier may identify one or more services.
  • the second service identifier may be one or more FQDNs, or one or more application AppIDs, etc., without limitation.
  • the second service identifier can be described in the form of FQDN group, FQDN list, FQDN set, FQDN range, App ID group, App ID list, App ID set, App ID range, etc., without limitation.
  • HPLMNID is the identifier of the above HPLMN, that is, the identifier of the PLMN deployed by the second service discovery function entity.
  • the second service identifier may specifically be an identifier of a service deployed in the HPLMN.
  • the second service discovery function entity is deployed in the HPLMN
  • the second service identifier is an identifier of a service corresponding to the second service discovery function entity
  • the second service discovery function entity is deployed in the HPLMN.
  • the second service identifier is the identifier of the service deployed in HPLMN.
  • the deployment situation of a certain service identification can be understood as the deployment situation of the service corresponding to the service identification. If a certain service is deployed in a certain PLMN, it can be understood that the location where the service is deployed is covered by the network of the PLMN, or it can be understood that the service is allowed to be accessed through the PLMN.
  • the second service identifier may be the identifier of the service to be accessed through HPLMN.
  • the second service identifier is the identifier of the service corresponding to the second service discovery function entity.
  • the second service identifier is the identifier of the service to be accessed through HPLMN.
  • the priority of the information of the second service discovery function entity is used to indicate the order in which the terminal device determines that the service discovery function entity to be accessed is discovered by the terminal device. Specifically, it can be a selection weight, or it can be reflected in the order in the list. wait.
  • the first SMF obtains the service discovery function entity selection information, which can be implemented in the following multiple ways according to the different PLMNs deployed by the first SMF.
  • the first SMF can be deployed on VPLMN, and the first SMF can also be deployed on HPLMN.
  • the first SMF determines the service discovery function entity selection information.
  • the first SMF deployed in the VPLMN determines the information of the first service discovery function entity, and receives the information of the second service discovery function entity from the second SMF deployed in the HPLMN.
  • the first SMF determines the information of the first service discovery function entity according to the first service discovery function entity.
  • the information and the information of the second service discovery function entity determine the service discovery function entity selection information.
  • the first SMF determines whether the information of the first service discovery function entity and the second service discovery function entity contain the VPLMN ID and the HPLMN ID.
  • the information of the discovery functional entity determines whether the information of the discovery functional entity and the second service discovery function entity contain the VPLMN ID and the HPLMN ID.
  • the service discovery function determined by the first SMF may include all the information on the first service discovery function and the information on the second service discovery function entity. The specific contents are shown in Table 1.
  • FQDN 1, FQDN 2, FQDN 3, FQDN 4, FQDN 5, FQDN 6, and FQDN 7 in the information of the first service discovery function entity in Table 1 are service identifiers deployed in VPLMN, and the information of the second service discovery function entity FQDN 6, FQDN7, FQDN8, FQDN9, and FQDN 10 are service identifiers deployed on HPLMN
  • the first SMF transfers the first service discovery function entity to The same service identifier in the information of the second service discovery function entity is deduplicated to determine the service discovery function entity selection information.
  • the information of the second service discovery function entity in the above service discovery function entity selection information is called the first information of the second service discovery function entity, and the second SMF is determined and sent to the first SMF.
  • the information of the second service discovery function entity is called the second information of the second service discovery function entity, and the same service identifier is called a common service identifier.
  • the shared service identifier can also be replaced by other names, such as overlapping service identifiers, consistent service identifiers, or the same service identifier, etc. If the function and content of the identifier are the same or equivalent to the shared service identifier, they all fall within the protection scope of this application. , not restricted.
  • first information of the second service discovery functional entity is the same as the second information of the second service discovery functional entity, or they are different.
  • the first information of the second service discovery function entity and the second information of the second service discovery function entity do not include a common service identifier, there may be no deduplication operation, then the first information of the second service discovery function entity and the second information of the second service discovery function entity The second information of the two service discovery function entities is the same.
  • the second information of the second service discovery function entity in the service discovery function entity selection information is the first information of the second service discovery function entity.
  • the service discovery function entity selection The content in the information may include all the information of the first service discovery function entity and the second information of the second service discovery function entity. The specific contents are shown in Table 2.
  • the first service discovery function entity and the second information of the second service discovery function entity include a common service identifier
  • a deduplication operation can be performed, then the first information of the second service discovery function entity and the second information of the second service discovery function entity The second information of the service discovery function entity is different.
  • the first SMF deduplicates according to the common service identifier.
  • the second information of the second service discovery function entity in the service discovery function entity selection information does not include the common service identifier, that is, the second service
  • the second information of the discovery function entity includes other service identifiers except the common service identifier in the first information of the second service discovery function entity.
  • the specific content of the service discovery function entity selection information is as shown in Table 3.
  • the first service identifier in the information of the first service discovery function entity includes FQDN 1, FQDN 2,..., FQDN 7, and the third service in the second information of the second service discovery function entity
  • the identifier includes FQDN 6, FQDN 7,..., FQDN 10
  • the first SMF discovers the information of the first service functional entity and the second service After discovering the same service identifier in the information of the functional entity, that is, the common service identifiers include FQDN 6 and FQDN 7, after deduplication, at this time
  • the service discovery function entity selection information includes FQDN 1 and FQDN 2 in the information of the first service discovery function. ,..., FQDN 7 and FQDN 8, FQDN 9, and FQDN 10 in the first information of the second service discovery function entity.
  • the first SMF can also perform the deduplication operation of the above-mentioned method 2, which is not limited in this application.
  • Another possible implementation manner is that when the first SMF is deployed on the HPLMN, the first SMF determines the service discovery function entity selection information.
  • the first SMF deployed in the HPLMN determines the information of the second service discovery function entity, and receives the information from the first service discovery function entity of the second SMF deployed in the VPLMN.
  • the first SMF determines the information of the first service discovery function entity according to the information of the first service discovery function entity. and the information of the second service discovery function entity determines the service discovery function entity selection information.
  • the specific process of the first SMF deployed on the HPLMN determining the service discovery function entity selection information is similar to the first SMF deployed on the VPLMN determining the service discovery function entity selection information. The difference is that the first SMF is deployed on HPLMN, the second SMF is deployed in the VPLMN.
  • the specific process can be referred to the above-mentioned specific process of the first SMF deployed in the VPLMN determining the service discovery function entity selection information.
  • its detailed description is omitted.
  • the first SMF before the first SMF obtains the service discovery function entity selection information, the first SMF can also receive the first indication information from the second SMF.
  • the first indication information may be used to indicate determining the service discovery function entity selection information (specifically, to instruct the first SMF to determine the service discovery function entity selection information), and may also be used to indicate sending the service discovery function entity selection information (specifically, to the UE). To instruct the first SMF to send service discovery function entity selection information) to the UE, etc.
  • the first SMF sends service discovery function entity selection information to the UE.
  • the UE receives the service discovery function entity selection information from the first SMF.
  • the first SMF may send the service discovery function entity selection information to the AMF, and the AMF forwards the service discovery function entity selection information to the UE.
  • the first SMF when the first SMF is deployed in the VPLMN, the first SMF sends the service discovery function entity selection information to the AMF through the Namf_Communication_N1N2MessageTransfer message.
  • the first SMF when the first SMF is deployed in the HPLMN, the first SMF sends the service discovery function entity selection information to the second SMF deployed in the VPLMN, and the second SMF sends the service discovery function entity selection information to the AMF through the Namf_Communication_N1N2MessageTransfer message.
  • the AMF sends the service discovery function entity selection information to the UE through the NAS message.
  • S203 The UE determines the target service discovery function entity according to the service discovery function entity selection information.
  • the determination method can be implemented in the following multiple ways.
  • the UE determines the target service discovery function entity based on the identity of the service to be accessed and the service discovery function entity selection information.
  • the UE performs query matching with the service discovery function entity selection information according to the identifier of the service to be accessed to determine the target service discovery function entity.
  • the UE matches the identifier of the service to be accessed with the first service identifier and the second service identifier in the service discovery function entity selection information. If the identifier of the service to be accessed is included in the first service identifier or the second service identifier, logo, then The service discovery function entity corresponding to the identifier of the service to be accessed is determined to be the target service discovery function entity.
  • the UE determines the target service discovery function entity based on the accessed PLMN, the identity of the service to be accessed, and the service discovery function entity selection information.
  • the UE queries and matches the service discovery function entity selection information according to the accessed PLMN and the identifier of the service to be accessed to determine the target service discovery function entity.
  • the UE first matches the identifier of the service to be accessed with the first service identifier or the second service identifier in the service discovery function entity selection information, and then matches the accessed PLMN with the VPLMN identifier in the service discovery function entity selection information. Or HPLMN identification to match.
  • the UE first matches the accessed PLMN with the VPLMN identifier or HPLMN identifier in the service discovery function entity selection information, and then matches the identifier of the service to be accessed with the first service identifier or the second service identifier.
  • the UE determines the priority of the information of the first service discovery function entity according to the priority of the information of the first service discovery function entity. and the priority of the information of the second service discovery function entity to determine the target service discovery function entity.
  • the priority of the information of the first service discovery function entity may be obtained by the first service discovery function entity according to local configuration or based on UE subscription information, which is not limited by this application.
  • the priority of the information of the second service discovery function entity may be obtained by the second service discovery function entity based on local configuration or based on UE subscription information, which is not limited by this application.
  • the priority of the information of the first service discovery function entity is higher than the priority of the information of the first service discovery function entity.
  • the UE determines the target service discovery function entity according to the priority of the information of the first service discovery function entity and the priority of the information of the second service discovery function entity, which can be implemented in the following multiple ways.
  • the UE can directly determine the target service discovery function entity as the first service discovery function entity. .
  • the UE first determines that the priority of the information of the first service discovery function entity is higher than the priority of the information of the first service discovery function entity. Further, the UE combines the identifier of the service to be accessed with the first service discovery function entity. The service identifier is matched. If the first service identifier contains the identifier of the service to be accessed, the UE determines that the target service discovery function entity is the first service discovery function entity; the first service identifier does not contain the identifier of the service to be accessed, then the UE will The identifier of the service to be accessed is matched with the second service identifier.
  • the UE determines that the target service discovery function entity is the second service discovery function entity; if the second service identifier does not include When accessing the service identification, the UE selects the locally configured default service discovery function entity, or randomly selects a service discovery function entity as the target service discovery function entity. This application does not limit the method of random selection by the UE.
  • S204 The UE sends a DNS query message to the target service discovery function entity.
  • the UE sends a DNS query message to the target service discovery function entity according to the address of the target service discovery function entity.
  • the first SMF obtains and sends the service discovery function entity selection information to the UE.
  • the UE determines the target service discovery function entity for the UE to discover the service to be accessed, and sends the service discovery function entity to the UE.
  • the target service discovery function entity should send a DNS query message to perform DNS query.
  • the UE can perform multiple service discovery functions deployed in different PLMNs based on the service discovery function entity selection information. Among the entities, determine the service discovery function entity to be used to avoid the problem of unable to properly resolve the DNS of the service, which is conducive to reasonable service discovery, thereby improving the user experience of accessing the service.
  • the UE After the UE queries the DNS, if a PLMN handover occurs in the UE, the UE re-determines the target service discovery function entity.
  • the PLMN handover of the UE may be that the UE moves from the VPLMN to the HPLMN, or it may also be that the UE moves from the first VPLMN to the second VPLMN.
  • S205 the first SMF deployed in the HPLMN learns that a PLMN handover occurs in the UE.
  • the first SMF triggers a process of sending updated information about the second service discovery function entity to the UE, for example, triggering a PDU session modification.
  • the first SMF sends the updated information of the second service discovery function entity to the UE.
  • the first SMF may send the updated information of the second service discovery function entity to the UE in the following situations.
  • Scenario 1 UE moves from VPLMN to HPLMN.
  • One possible implementation is that when no deduplication operation is performed in S201, that is, when the information of the first service discovery function entity and the information of the second service discovery function entity in the service discovery function entity selection information do not contain a common service identifier, That is to say, the information of the second service discovery function entity does not change at this time, and the first SMF sends the information of the second service discovery function entity obtained by the first SMF in S201 to the UE again.
  • Another possible implementation manner is that when the deduplication operation is performed in S201, that is, when the information of the first service discovery function entity and the information of the second service discovery function entity in the service discovery function entity selection information include a common service identifier, An SMF sends the updated information of the second service discovery function entity to the UE.
  • the updated information of the second service discovery function entity includes the information of the second service discovery function entity and the shared service identifier after deduplication in S201. .
  • Scenario 2 The UE moves from the first VPLMN to the second VPLMN.
  • One possible implementation is that when no deduplication operation is performed in S201, that is, when the information of the first service discovery function entity and the information of the second service discovery function entity in the service discovery function entity selection information do not contain a common service identifier, That is to say, the information of the second service discovery function entity does not change at this time.
  • the first SMF sends the information of the second VPLMN service discovery function entity and the information of the second service discovery function entity obtained by the first SMF in S201 to the UE. information.
  • Another possible implementation manner is that when the deduplication operation is performed in S201, that is, when the information of the first service discovery function entity and the information of the second service discovery function entity in the service discovery function entity selection information include a common service identifier, then The first SMF sends the information of the service discovery function entity of the second VPLMN and the updated information of the second service discovery function entity to the UE.
  • the updated information of the second service discovery function entity includes the information after deduplication in S201.
  • the information and common service identifier of the second service discovery function entity is performed in S201, that is, when the information of the first service discovery function entity and the information of the second service discovery function entity in the service discovery function entity selection information include a common service identifier.
  • S207 the UE re-determines the target service discovery function entity.
  • the UE re-determines the target service discovery function entity according to the updated information of the second service discovery function entity received from the first SMF.
  • Scenario 1 UE moves from VPLMN to HPLMN.
  • the UE re-determines the target industry based on the updated information of the second service discovery function entity.
  • Service discovery functional entities
  • the first SMF does not send the information of the second service discovery function entity to the UE, and the UE re-determines the target service discovery function entity based on the information of the second service discovery function entity obtained in S203.
  • the information of the second service discovery function entity does not change.
  • the first SMF may not send the information of the second service discovery function entity obtained by the first SMF in S201 to the UE.
  • the UE will again use the second service discovery function entity obtained by the first SMF in S202.
  • the information on the discovery functional entity re-determines the target service discovery functional entity.
  • the first SMF may not send the information of the second service discovery function entity obtained by the first SMF in S201 to the UE, and the UE can obtain the information according to the information of the second service discovery function entity in S202.
  • the HPLMN ID in the information of the second service discovery function entity is used to re-determine the target service discovery function entity.
  • Scenario 2 The UE moves from the first VPLMN to the second VPLMN.
  • the UE re-determines the target service discovery function entity based on the information of the service discovery function entity of the second VPLMN and the updated information of the second service discovery function entity.
  • the first SMF does not send the information of the second service discovery function entity to the UE, but sends the information of the second VPLMN service discovery function entity to the UE, and the UE uses the information of the second VPLMN service discovery function entity to The target service discovery function entity is re-determined with the information of the second service discovery function entity obtained in S203.
  • the first SMF may not send the information of the second service discovery function entity obtained by the first SMF in S201 to the UE. At this time, the first SMF sends the second service discovery function entity to the UE.
  • the UE According to the information of the service discovery function entity of the VPLMN, the UE re-determines the target service discovery function entity according to the information of the service discovery function entity of the second VPLMN and the information of the second service discovery function entity obtained in S202.
  • the first SMF may not send the information of the second service discovery function entity obtained by the first SMF in S201 to the UE.
  • the first SMF sends the information to the UE.
  • the UE sends the information of the service discovery function entity of the second VPLMN, and the UE re-determines the target service discovery function entity based on the information of the service discovery function entity of the second VPLMN and the HPLMN ID in the information of the second service discovery function entity obtained in S202.
  • the first SMF can strategically update the information of the second service discovery function entity according to different situations of UE handover to PLMN. While increasing the flexibility of the solution, it can reduce the information of determining the target service discovery function entity to varying degrees. Order overhead.
  • the service discovery function entity in the following embodiments takes EASDF as an example. That is to say, EASDF in this application is only used as an example, and can also be replaced by a DNS server, or other domain name resolution function/entity. For example, ECS or EES are not restricted. For example, replacing V-EASDF with a DNS server deployed in VPLMN still falls within the scope of protection of this application.
  • the first service identifier in the following embodiments is called FQDN set1
  • the second service identifier is called FQDN set2.
  • Figure 3 is a schematic diagram of a communication method 300 provided by an embodiment of the present application, in which the first SMF is deployed on the VPLMN and the second SMF is deployed on the HPLMN.
  • the first SMF in Figure 2 is called V-SMF
  • the second SMF is called H-SMF
  • the first service discovery function entity is called V-EASDF
  • the second service discovery function entity is called H-EASDF.
  • Method 300 may include the following steps.
  • S300 The UE establishes a protocol data unit (PDU) session.
  • PDU protocol data unit
  • the UE requests to establish a PDU session.
  • the UE sends a request to establish a PDU session to the AMF, so that the AMF selects the SMF for the session.
  • the UE currently accesses the VPLMN, and the AMF is deployed in the VPLMN.
  • the method flow shown in Figure 3 also includes:
  • AMF selects SMF.
  • the AMF selects the V-SMF deployed in the VPLMN and the H-SMF deployed in the HPLMN.
  • AMF sends an Nsmf_PDUSession_CreateSMContext message to V-SMF, which contains the address of H-SMF.
  • V-SMF receives the Nsmf_PDUSession_CreateSMContext message from AMF.
  • V-SMF selects V-UPF.
  • the V-SMF can select a V-UPF based on information such as the load of the UPF, the location of the UPF, and the capabilities of the UPF, and send N4 rules to the V-UPF.
  • the N4 rules are used for user plane message processing.
  • V-SMF sends Nsmf_PDUSession_Create Request message to H-SMF.
  • H-SMF receives the Nsmf_PDUSession_Create Request message from V-SMF.
  • H-SMF selects H-PCF.
  • H-SMF can select H-PCF based on local operator policy, DNN and other information.
  • H-SMF obtains policy information.
  • the authorization policy is used to indicate that the VPLMN is allowed to perform offloading, or to indicate that the offloading point is allowed to be inserted into the VPLMN, or to indicate that the V-EASDF is allowed to be selected. It should be noted that the above authorization policy can also be expressed as other information elements, such as authorization information, instruction information, etc., as long as it can play the above role, there is no restriction.
  • H-SMF can send a request to obtain policy information to H-PCF, and H-PCF carries the authorization policy in the request feedback message and sends it to H-SMF. H-SMF can also obtain policy information through local configuration without restrictions.
  • H-SMF can carry the request to obtain policy information in the Npcf_SMPolicyControl_Update Request/Response message and send it to H-PCF without restriction.
  • H-SMF determines the information of H-EASDF.
  • H-SMF selects H-EASDF and determines the information of H-EASDF.
  • H-EASDF information includes one or more of the following information: H-EASDF address, FQDN set2, HPLMN ID, etc., which are not restricted.
  • the address of H-EASDF can be the IP address of H-EASDF, or it can also be other addresses, such as media access control (media access control, MAC) address, uniform resource locator (uniform resource locator, URL), etc. be restricted.
  • media access control media access control, MAC
  • uniform resource locator uniform resource locator, URL
  • FQDN set2 is used to indicate the set of FQDNs of services deployed on HPLMN, or is used to indicate the set of FQDNs of services that are allowed/hoped for UE to access through the application server (Application Service, AS) deployed on HPLMN, and is not restricted. .
  • AS Application Service
  • FQDN set2 refers to the second service identifier in Figure 2. Those skilled in the art can understand that FQDN set2 and the second service identifier in the embodiment of the present application can be replaced with each other.
  • the H-SMF can determine the address of the H-EASDF through local configuration, can also determine the H-EASDF by obtaining it from the NRF, or obtain the address of the H-EASDF through other methods, without limitation.
  • H-SMF can obtain FQDN set2 through local configuration or acquisition from AF, without restrictions.
  • H-SMF sends DNS processing rules to H-EASDF.
  • H-EASDF receives DNS processing rules from H-SMF.
  • DNS processing rules are used by EASDF to process DNS messages, such as caching, forwarding DNS messages, adding ECS options to DNS messages, etc., and are not restricted.
  • H-SMF sends H-EASDF information to V-SMF.
  • the V-SMF receives the information of the H-EASDF from the H-SMF.
  • the H-EASDF information may also include the association between the H-EASDF address and FQDN set2.
  • the H-SMF sends the first indication information to the V-SMF.
  • the first indication information may be used to indicate determining the service discovery function entity selection information (specifically, instructing the V-SMF to determine the service discovery function entity selection information), and may also be used to indicate sending the service discovery function entity selection information (specifically, to instruct the V-SMF to determine the service discovery function entity selection information) to the UE. To instruct V-SMF to send service discovery function entity selection information) to the UE, etc.
  • V-SMF determines the information of V-EASDF.
  • the V-SMF determines the V-EASDF information.
  • the V-EASDF information includes one or more of the following information: V-EASDF address, FQDN set1, VPLMN ID, etc.
  • the address of V-EASDF can be the IP address of V-EASDF, or other addresses, such as MAC address, URL, etc., without limitation.
  • FQDN set1 is used to indicate the set of FQDNs of the services deployed in the VPLMN, or to indicate the set of FQDNs of the services that are allowed/hoped for the UE to access through the AS deployed in the VPLMN, or to indicate the FQDNs that are allowed to be offloaded in the VPLMN.
  • the collection is not limited.
  • FQDN set1 refers to the first service identifier in Figure 2. Those skilled in the art can understand that FQDN set1 and the first service identifier in the embodiment of the present application can be replaced with each other.
  • V-SMF determines V-EASDF information according to the first indication information, specifically including determining V-EASDF according to the first indication information.
  • EASDF information FQDN set1, VPLMN, etc.
  • the V-SMF can determine the address of the V-EASDF through local configuration, can also determine the V-EASDF by obtaining it from the NRF, or obtain the address of the H-EASDF in other ways, without limitation.
  • V-SMF can obtain the FQDN set through local configuration or acquisition from AF, without restrictions.
  • the above S320 may occur before or after the H-EASDF information obtained in the above S312, and there is no timing limit for the V-SMF to determine the V-EASDF information.
  • V-SMF determines the service discovery function entity selection information.
  • the V-SMF determines the service discovery function entity selection information based on the V-EASDF information determined in the above S320 and the H-EASDF information obtained in the above S312.
  • the above-mentioned S310-S330 process is similar to the process in S201 when the first SMF is deployed on the VPLMN and the first SMF determines the service discovery function entity selection information.
  • the V-SMF determines the service discovery function entity selection information based on the V-EASDF determined in the above-mentioned S320.
  • Information and the H-EASDF information obtained in S310 above determine the service discovery function entity selection information, that is, in S201, the first SMF determines the information of the first service discovery function entity and receives the second service discovery function entity from the second SMF.
  • the first SMF determines the service discovery function entity selection information based on the information of the first service discovery function entity and the second information of the second service discovery function entity.
  • its detailed description is omitted.
  • the service discovery function entity selection information includes the address of V-EASDF, FQDN set1, the address of H-EASDF, and FQDN set2.
  • the service discovery function entity selection information can be in the form of the address of V-EASDF - FQDN set1, the address of H-EASDF - FQDN set2, or the association relationship between the address of V-EASDF and FQDN set1, the address of H-EASDF The form of the association between the address and FQDN set2.
  • the service discovery function entity selection information may also include VPLMN ID and HPLMN ID.
  • the service discovery function entity selection information can also be in the form of the address of V-EASDF-FQDN set1-VPLMN ID, the address of H-EASDF-FQDN set2-HPLMN ID, or the address of V-EASDF and FQDN set1 and The association relationship of VPLMN ID, the form of the association relationship between H-EASDF address and FQDN set2 and HPLMN ID.
  • FQDN set1 and FQDN set2 may have overlapping service identifiers. For example, if a certain service is deployed in both HPLMN and VPLMN, the FQDN corresponding to the service may be included in both FQDN set1 and FQDN set2.
  • S340, V-SMF sends DNS processing rules to V-EASDF.
  • V-EASDF receives DNS processing rules from V-SMF.
  • DNS processing rules are used by EASDF to process DNS messages, such as caching, forwarding DNS messages, adding ECS options to DNS messages, etc., and are not restricted.
  • execution order of the above-mentioned S340 and the above-mentioned S330 can be executed in any time sequence, and can also be executed at the same time without limitation.
  • V-SMF sends service discovery function entity selection information to AMF.
  • the AMF receives the service discovery function entity selection information from the V-SMF.
  • V-SMF can send the service discovery function entity selection information to the AMF through the Namf_Communication_N1N2MessageTransfer message, etc., without restriction.
  • the AMF sends service discovery function entity selection information to the UE.
  • the UE receives the service discovery function entity selection information from the AMF.
  • the AMF can send the service discovery function entity selection information to the UE through non-access stratum (NAS) messages or other methods without restrictions.
  • NAS non-access stratum
  • the UE determines the target service discovery function entity and sends a DNS query message to the target service discovery function entity.
  • the UE determines the target service discovery function entity according to the accessed PLMN, the identity of the service to be accessed, and the service discovery function entity selection information.
  • a possible implementation manner is that when the UE determines that the identifier of the service to be accessed is only included in FQDN set1, or the identifier of the service to be accessed is only included in FQDN set2, the UE determines that the target service discovery function entity is V-EASDF or H- EASDF.
  • the UE determines that the target service discovery function entity is V-EASDF.
  • the UE determines that the target service discovery function entity is H-EASDF.
  • the UE determines that the identifier of the service to be accessed is included in both FQDN set1 and FQDN set2, in other words, the identifier of the service to be accessed is the common service identifier of FQDN set1 and FQDN set2, Or when the service to be accessed is deployed in both VPLMN and HPLMN, the UE determines the target service discovery function entity according to the accessed PLMN.
  • the UE determines that the target service discovery function entity is V-EASDF.
  • the UE determines that the target service discovery function entity is H-EASDF.
  • the UE first determines that the accessed PLMN is VPLMN or HPLMN, and then matches the identifier of the service to be accessed.
  • the UE determines whether the identifier of the service to be accessed is included in FQDN set1. If the identifier of the service to be accessed is included in FQDN set1, the UE determines the target service discovery function entity. is V-EASDF; if the identifier of the service to be accessed is not included in FQDN set1, the UE then determines whether the identifier of the service to be accessed is included in FQDN set2. If the identifier of the service to be accessed is included in FQDN set2, the UE determines the target service The discovery function entity is H-EASDF. If the identity of the service to be accessed is not included in FQDN set2, the UE selects the locally configured default service discovery function entity, or randomly selects a service discovery function entity without restriction.
  • the UE determines whether the identifier of the service to be accessed is included in FQDN set2. If the identifier of the service to be accessed is included in FQDN set2, the UE determines the target service discovery function entity. is H-EASDF; if the identifier of the service to be accessed is not included in FQDN set2, the UE then determines whether the identifier of the service to be accessed is included in FQDN set1. If the identifier of the service to be accessed is included in FQDN set1, the UE determines the target service The discovery function entity is V-EASDF. If the identity of the service to be accessed is not included in FQDN set1, the UE selects the locally configured default service discovery function entity, or randomly selects a service discovery function entity without restriction.
  • V-SMF determines and sends service discovery function entity selection information to the UE, so that the UE can The service discovery function entity selects information, determines the target service discovery function entity, and sends a DNS query message to the target service discovery function entity for DNS query.
  • the V-SMF determines the service discovery function entity selection information, and the UE can determine the service to be accessed by the UE among multiple service discovery function entities deployed in different PLMNs based on the service discovery function entity selection information.
  • the target service discovery functional entity avoids the problem of inability to properly resolve the DNS of the service, which is conducive to reasonable service discovery, thereby improving the user experience of accessing the service.
  • the H-SMF can learn that the PLMN switch occurs in the UE, and determine to send the information of the second service discovery function entity to the UE.
  • the specific steps are shown in Figure 4, which will be introduced in detail below in conjunction with Figure 4.
  • the method 400 may include the following steps.
  • the PLMN handover of the UE may be that the UE moves from the VPLMN to the HPLMN, or it may also be that the UE moves from the first VPLMN to the second VPLMN.
  • S420 H-SMF learns that a PLMN handover occurs in the UE.
  • H-SMF senses that a PLMN handover occurs in the UE through a cross-PLMN handover (HO) process.
  • the H-SMF when the H-SMF learns that a PLMN handover has occurred in the UE, the H-SMF triggers a process of sending the information of the second service discovery function entity to the UE.
  • the H-SMF sends the updated information of the second service discovery function entity to the UE.
  • the UE receives information from the second service discovery function entity of H-SMF.
  • the H-SMF can send the updated information of the second service discovery function entity to the UE by initiating a PDU session modification process or other methods.
  • the H-SMF sends updated H-EASDF information to the UE in the following situations.
  • Scenario 1 UE moves from VPLMN to HPLMN.
  • V-EASDF information and the H-EASDF information are not deduplicated, that is, when the FQDN set1 and FQDN set2 in the service discovery function entity selection information do not contain the common service identifier, that is to say At this time, the information of the second service discovery function entity does not change, and H-SMF sends H-EASDF information to the UE again.
  • H-SMF H-SMF
  • the UE sends updated H-EASDF information, which includes deduplicated H-EASDF information and a common service identifier.
  • the FQDN set1 in the V-EASDF information includes FQDN 1, FQDN 2,..., FQDN 7, and the FQDN set2 in the H-EASDF information includes FQDN 6, FQDN 7, ..., FQDN 10, then the H-EASDF information in the service discovery function entity selection information after deduplication includes FQDN 8, FQDN 9, FQDN 10.
  • H-SMF is sent to the UE
  • the updated H-EASDF information includes the deduplicated H-EASDF information and the common service identifier. For example, H-SMF sends the H-EASDF information to the UE by initiating a PDU session modification process.
  • Scenario 2 The UE moves from the first VPLMN to the second VPLMN.
  • One possible implementation is when the V-EASDF information and the H-EASDF information are not deduplicated, that is, when the FQDN set1 and FQDN set2 in the service discovery function entity selection information do not contain the common service identifier, that is to say At this time, the information of the second service discovery function entity does not change, and the H-SMF sends the information of the service discovery function entity of the second VPLMN and the information of the H-EASDF to the UE.
  • the H-SMF when the V-EASDF information and the H-EASDF information are deduplicated, that is, when the FQDN set1 and FQDN set2 in the service discovery function entity selection information contain common service identifiers, the H-SMF The UE sends the information of the service discovery function entity of the second VPLMN and the updated H-EASDF information.
  • the updated H-EASDF information includes the deduplicated H-EASDF information and the common service identifier.
  • the updated H-EASDF information can refer to the description in Table 4 above.
  • S440 The UE re-determines the target service discovery function entity.
  • the UE re-determines the target service discovery function entity according to the updated H-EASDF information received from the H-SMF.
  • the UE when the UE moves from the first VPLMN to the second VPLMN, the UE re-determines the target service discovery based on the information of the service discovery function entity of the second VPLMN received from the H-SMF and the updated H-EASDF information. Functional entity.
  • H-SMF can learn that the UE has undergone a PLMN switch and determine to send the information of the second service discovery function entity to the UE, avoiding the problem of being unable to properly resolve the DNS of the service and conducive to reasonable services. Discovery, thereby improving user experience of accessing services.
  • the V-SMF determines and sends the service discovery function entity selection information to the UE.
  • the H-SMF determines and sends the service discovery function entity selection information to the UE. The following is combined with Figures 5 and 6 illustrate this in detail.
  • Figure 5 is a schematic diagram of a communication method 500 provided by an embodiment of the present application, in which the first SMF is deployed on the HPLMN and the second SMF is deployed on the VPLMN.
  • Figure 5 can refer to the description of Figure 2 above.
  • the first SMF in Figure 2 is called H-SMF
  • the second SMF is called V-SMF
  • the first service discovery function entity is called H-EASDF
  • the first SMF in Figure 2 is called H-SMF
  • the second service discovery function entity is called V-EASDF
  • the method 500 may include the following steps.
  • S500 The UE establishes a PDU session.
  • H-SMF determines the information of H-EASDF.
  • H-SMF sends DNS processing rules to H-EASDF.
  • H-SMF sends a request message to V-SMF.
  • V-SMF receives the request message from H-SMF.
  • H-SMF sends a request message to the V-SMF, and the request message is used to request to obtain V-EASDF information. Request the address of V-EASDF. It should be understood that H-SMF can send this request message through Nsmf_PDUSession_Update Request message and other methods without restrictions.
  • the H-SMF sends second indication information to the V-SMF, and the second indication information is used to request to obtain FQDN set1.
  • V-SMF determines the information of V-EASDF.
  • the V-SMF determines the information of the V-EASDF.
  • V-EASDF information has been described in the above-mentioned S311. Here, in order to avoid redundancy, its detailed description is omitted.
  • V-SMF determines FQDN set1 in the V-EASDF information based on the second indication information.
  • V-SMF sends V-EASDF information to H-SMF.
  • the H-SMF receives the information of the V-EASDF from the V-SMF.
  • V-SMF can send the V-EASDF information to H-SMF through Nsmf_PDUSession_Update Response message, etc., without restriction.
  • the V-EASDF information may also include the association between the V-EASDF address and FQDN set1.
  • V-SMF sends DNS processing rules to V-EASDF.
  • S532 can be executed after S530 and before the following S560, and there is no timing limit for S532.
  • H-SMF determines the service discovery function entity selection information.
  • the H-SMF determines the service discovery function entity selection information based on the V-EASDF information obtained in S531 and the H-EASDF information determined in S510.
  • the above-mentioned S530-S540 process is similar to the process in S201 when the first SMF is deployed on the HPLMN and the first SMF determines the service discovery function entity selection information.
  • the H-SMF obtains the V-EASDF information based on S531. and the H-EASDF information determined in S511 to determine the service discovery function entity selection information, that is, in S201, the first SMF determines the information of the second service discovery function entity and receives the first service discovery function entity from the second SMF.
  • the first SMF determines the service discovery function entity selection information based on the information of the first service discovery function and the information of the second service discovery function entity.
  • the service discovery function entity selection information includes the address of V-EASDF, FQDN set1, the address of H-EASDF, and FQDN set2.
  • the service discovery function entity selection information can be the address of V-EASDF - FQDN set1, H-EASDF
  • the address-FQDN set2 may also be in the form of the association between the V-EASDF address and FQDN set1, or the association between the H-EASDF address and FQDN set2.
  • the service discovery function entity selection information may also include VPLMN ID and HPLMN ID.
  • the service discovery function entity selection information can also be in the form of the address of V-EASDF-FQDN set1-VPLMN ID, the address of H-EASDF-FQDN set2-HPLMN ID, or the address of V-EASDF and FQDN set1 and The association relationship of VPLMN ID, the form of the association relationship between H-EASDF address and FQDN set2 and HPLMN ID.
  • FQDN set1 and FQDN set2 may have overlapping service identifiers. For example, if a certain service is deployed in both HPLMN and VPLMN, the FQDN corresponding to the service may be included in both FQDN set1 and FQDN set2.
  • the service discovery function entity selection information also includes DNN, S-NSSAI, etc., without limitation.
  • H-SMF sends service discovery function entity selection information to the UE.
  • the H-SMF sends the service discovery function entity selection information to the V-SMF, and the V-SMF forwards the service discovery function entity selection information to the UE.
  • H-SMF can send service discovery function entity selection information to V-SMF through PDU session establishment response messages, etc., without restriction.
  • S560 The UE determines the target service discovery function entity and sends a DNS query message to the target service discovery function entity.
  • the H-SMF can learn that the PLMN switch occurs in the UE and determine to send the information of the second service discovery function entity to the UE.
  • the specific steps are similar to the processes of S410-S440. Here, in order to avoid redundancy, the detailed description is omitted.
  • H-SMF determines and sends the service discovery function entity selection information to the UE, so that the UE determines the target service discovery function entity according to the service discovery function entity selection information, and sends the service discovery function entity of the target access service to the service discovery function entity.
  • the H-SMF determines the service discovery function entity selection information, and the UE can determine the service discovery function entity to be accessed by the UE according to the service discovery function entity selection information deployed in different PLMNs.
  • the target service discovery functional entity of the service avoids the problem of inability to properly resolve the DNS of the service, which is conducive to reasonable service discovery, thereby improving the user experience of accessing the service.
  • Figures 2 to 5 are UE session granularity, and Figure 6 can occur in any UE granularity (or non-PDU session granularity) process without limitation.
  • Figure 6 takes the registration process as an example to introduce it in detail.
  • Figure 6 is a schematic diagram of a communication method 600 provided by an embodiment of the present application.
  • Method 600 may include the following steps.
  • S610 AMF obtains service discovery function entity selection information.
  • the service discovery function entity selection information is used to determine the target service discovery function entity.
  • the target service discovery function entity is used to assist the terminal device in discovering the service to be accessed.
  • the terminal device needs to access the service, it needs to determine the target service discovery function entity corresponding to the service to be accessed.
  • the terminal device passes The target service discovery function entity assists in discovering services to be accessed.
  • the service discovery function entity selection information includes the public land mobile network identity corresponding to at least one service discovery function entity and the address of at least one service discovery function entity.
  • the public land mobile network identifier corresponding to at least one service discovery function entity may specifically be the identifier of the PLMN deployed by the service discovery function entity.
  • the address of at least one service discovery function entity may specifically be the IP address of at least one service discovery function entity, etc., which is used by the terminal device to initiate service discovery. For example, the terminal device may subsequently discover the service based on the address of one of the service discovery function entities.
  • Functional entities send domain name system query messages.
  • the service discovery function entity selection information also includes one or more pieces of information about at least one service discovery function entity: the data network name corresponding to at least one service discovery function entity, and the single network slice selection corresponding to at least one service discovery function entity. Auxiliary information, the service identifier corresponding to at least one service discovery function entity.
  • the data network name (DNN) corresponding to at least one business discovery functional entity may be a DNN served or supported by at least one business discovery functional entity.
  • the single network slice selection assistance information (S-NSSAI) corresponding to at least one service discovery function entity may specifically be the S-NSSAI served or supported by at least one service discovery function entity.
  • the DNN corresponding to any one of the at least one service discovery functional entities may be one or more, and the S-NSSAI corresponding to any one of the at least one service discovery functional entities may also be is one or more.
  • the service identifier corresponding to at least one service discovery function entity may be the service identifier of the PLMN deployed by at least one service discovery function entity. It can also be understood that if at least one service discovery function entity can perform or assist in the discovery of a certain service, Then the service can be understood as the service identifier corresponding to the at least one service discovery function entity.
  • the service identifier corresponding to at least one service discovery function entity can identify one or more services.
  • the service identifier corresponding to at least one service discovery function entity can be one or more FQDNs, or one or more App IDs, etc., without limitation.
  • service identifier corresponding to at least one service discovery function entity can be described in the form of FQDN group, FQDN list, FQDN set, FQDN range, App ID group, App ID list, App ID set, App ID range, etc., without limitation.
  • the method for AMF to obtain service discovery function entity selection information is as follows:
  • the data management network element or the policy control network element PCF obtains the service discovery function entity selection information.
  • S612 The data management network element or PCF sends the service discovery function entity selection information to the AMF.
  • the data management network element or PCF can send the service discovery function entity selection information to the AMF during the registration process of the UE, and can also carry the service discovery function entity selection information in other information and send it to the AMF. This application does not allow limit.
  • S611 The data management network element or the policy control function (PCF) obtains the service discovery function entity selection information.
  • PCF policy control function
  • the data management network element can be unified data management (unified data management, UDM) and/or unified data repository (unified data repository, UDR).
  • UDM unified data management
  • UDR unified data repository
  • the data management network element or PCF can obtain the service discovery function entity selection information through local configuration or acquisition.
  • the service discovery function entity selection information may be an association relationship, which may specifically be a (PLMN ID-DNN-S-NSSAI-FQDN set-EASDF address) list corresponding to at least one service discovery function entity. It contains the above information of all or part of the VPLMN that the UE is allowed to access, and may or may not contain the above information of the HPLMN. As an example, the above information could be in the form of:
  • the FQDN set refers to the service identification of the service discovery function entity
  • the EASDF address refers to the address of the service discovery function entity
  • the PLMN ID refers to the public land mobile network identification corresponding to the service discovery function entity.
  • the FQDN set and the service identifier of the service discovery function entity in the embodiment of this application can be replaced with each other
  • the EASDF address and the public land mobile network identifier corresponding to the service discovery function entity can be replaced with each other
  • the PLMN ID and the public land mobile network identifier corresponding to the service discovery function entity can be replaced with each other.
  • Mobile network identifiers are interchangeable.
  • each row in the above Table 5 corresponds to the information of a business discovery function entity, among which DNN, S-NSSAI or FQDN set are optional, that is, any row in the above Table 5 does not need to contain DNN.
  • DNN a business discovery function entity
  • S-NSSAI or FQDN set are optional, that is, any row in the above Table 5 does not need to contain DNN.
  • One or more items in S-NSSAI or FQDN set may not contain different items in DNN, S-NSSAI or FQDN.
  • one row does not contain DNN and S-NSSAI, and another row does not contain FQDN set. But each line must contain the PLMN ID and EASDF address.
  • the above Table 5 can reflect the mapping relationship between PLMN ID and EASDF address, that is, the EASDF address can be determined based on the PLMN ID.
  • the above table can also reflect the mapping relationship between PLMN ID, DNN, S-NSSAI, FQDN set and EASDF address, that is, the EASDF address can be determined based on PLMN ID, DNN, S-NSSAI, FQDN set.
  • EASDFs may be deployed, but different PLMNs cannot share the same EASDF. If a PLMN deploys more than one EASDF, these EASDFs may support different DNNs and S-NSSAI. In other words, a certain EASDF may only support sessions for several specific DNNs and S-NSSAI, so it is not necessarily possible to determine which EASDF to use based only on the PLMN ID.
  • the UE sends a registration request to the AMF.
  • the AMF receives the registration request from the UE.
  • S614 the AMF sends request information to the data management network element or PCF.
  • the data management network element or PCF receives the sending request information from the AMF.
  • the AMF sends request information to the data management network element, and the request information is used to obtain registration information, or the AMF sends request information to the PCF, and the request information is used to obtain policy information.
  • AMF sends a Nudm_SDM_Get Request message to the data management network element, and the Nudm_SDM_Get Request message carries the request information, or AMF sends an Npcf_UEPolicyControl_Create Request message to the PCF, and the Npcf_UEPolicyControl_Create Request message carries the request information, without limitation.
  • S612 The data management network element or PCF sends service discovery function entity selection information to the AMF.
  • the AMF receives the service discovery function entity selection information from UDM or PCF.
  • the data management network element can carry the service discovery function entity selection information in the registration information and send it to the AMF, or the PCF can carry the service discovery function entity selection information in the policy information and send it to the AMF, or the UDM or PCF can directly Sending service discovery function entity selection information to AMF is not restricted.
  • the AMF sends service discovery function entity selection information to the UE.
  • the UE receives the service discovery function entity selection information from the AMF.
  • the AMF can send the service discovery function entity selection information to the UE through a registration acceptance message or other means.
  • S621 the UE initiates a (non-roaming) PDU session establishment process in HPLMN.
  • S630 is executed.
  • S630 The UE determines the target service discovery function entity and sends a DNS query message to the target service discovery function entity.
  • the UE determines the target service discovery function entity according to the accessed PLMN and service discovery function entity selection information.
  • the UE matches the accessed PLMN with the PLMN identifier corresponding to at least one service discovery function entity in the service discovery function entity selection information. If the accessed PLMN is the PLMN identifier corresponding to one of the service discovery function entities, then determine the PLMN identifier corresponding to the service discovery function entity.
  • the service discovery functional entity is the target service discovery functional entity.
  • the UE can also determine the service discovery function entity of the access service based on one or more of the DNN corresponding to the session, the S-NSSAI corresponding to the session, the identifier of the service to be accessed, and the service discovery function entity selection information. .
  • the UE senses the currently accessed PLMN and matches the current PLMN ID with the service discovery function entity selection information. If only the address of one service discovery function entity is matched, the UE determines the target service discovery function entity. Discover functional entities for the business. If the addresses of at least two service discovery function entities are matched, it means that there are multiple available service discovery function entities in the current PLMN. These service discovery function entities may have other information to assist selection, such as DNN, S-NSSAI and/or FQDN, etc. , it can also be priority, etc. The UE continues to match the current function selection information according to the DNN corresponding to the current session, the S-NSSAI corresponding to the session, and/or the identifier of the service to be accessed, to determine the target service discovery function entity.
  • the other auxiliary selection information of at least two service discovery function entities may not include all items of DNN, S-NSSAI and FQDN set, for example If it only contains DNN and S-NSSAI, the UE will only perform matching based on the DNN corresponding to the current session and the S-NSSAI corresponding to the session, without determining the target service discovery function entity based on the identifier of the service to be accessed.
  • the UE can also match the accessed PLMN ID, the DNN corresponding to the current session, the S-NSSAI corresponding to the session, and the identifier of the service to be accessed with the service discovery function entity selection information. To determine the target business discovery functional entity.
  • S640 the UE performs PLMN switching.
  • S650 the UE re-determines the target service discovery function entity and sends a DNS query message to the target service discovery function entity.
  • the AMF determines and sends the service discovery function entity selection information to the UE, so that the UE determines the target service discovery function entity based on the service discovery function entity selection information, and sends a DNS query message to the target service discovery function entity to perform DNS Inquire.
  • the AMF determines the service discovery function entity selection information, and the UE can determine the service to be accessed by the UE among multiple service discovery function entities deployed in different PLMNs based on the service discovery function entity selection information.
  • the target service discovery functional entity avoids the problem of inability to properly resolve the DNS of the service and is conducive to reasonable service discovery, thus improving the user experience of accessing the service.
  • each embodiment of the present application involves some message names, such as service discovery function entity selection information or policy information, etc. It should be understood that the naming does not limit the protection scope of the embodiments of the present application.
  • the methods and operations implemented by the terminal device can also be implemented by components (such as chips or circuits) that can be implemented by the terminal device; in addition, the methods and operations implemented by the network device can also be implemented by the network device. It can be implemented by components (such as chips or circuits) of network equipment, without limitation.
  • embodiments of the present application also provide corresponding devices, and the devices include modules for executing corresponding modules in each of the above method embodiments.
  • the module can be software, hardware, or a combination of software and hardware. It can be understood that the technical features described in the above method embodiments are also applicable to the following device embodiments.
  • first SMF, AMF, terminal device, second SMF, data management network element and PCF can perform some or all of the steps in the above embodiments. These steps or operations are only examples. The embodiments of the present application can also perform other steps. Operations or variations of various operations. In addition, various steps may be performed in a different order than presented in the above-described embodiments, and it is possible that not all operations in the above-described embodiments are performed.
  • the communication method provided by the embodiment of the present application is introduced in detail above with reference to Figures 2 to 6.
  • the communication device provided by the embodiment of the present application is described in detail below with reference to Figures 7 to 9. It should be understood that the description of the device embodiments corresponds to the description of the method embodiments. Therefore, for content that is not described in detail, please refer to the above method embodiments. For the sake of brevity, some content will not be described again.
  • FIG. 7 is a schematic block diagram of a communication device provided by an embodiment of the present application.
  • the device 700 includes a transceiver unit 710, which may be used to implement corresponding communication functions.
  • the transceiver unit 710 may also be called a communication interface or a communication unit.
  • the device 700 may also include a processing unit 720, which may be used for data processing.
  • a processing unit 720 which may be used for data processing.
  • the device 700 also includes a storage unit, which can be used to store instructions and/or data, and the processing unit 720 can read the instructions and/or data in the storage unit, so that the device implements each of the foregoing method embodiments.
  • Actions of different terminal devices in the system such as the first SMF, AMF, terminal device, second SMF, data management network element or PCF action.
  • the device 800 can be used to perform the actions performed by the first SMF, AMF, terminal equipment, second SMF, data management network element or PCF in each of the above method embodiments.
  • the device 700 can be the first SMF, AMF, terminal device, second SMF, data management network element or PCF.
  • the transceiver unit 710 is used to implement the above method.
  • the processing unit 720 is used to perform operations related to the transceiver of the first SMF, AMF, terminal equipment, second SMF, data management network element or PCF in the above method embodiment. Operations related to processing of SMF, data management network element or PCF.
  • the device 700 here is embodied in the form of a functional unit.
  • the term "unit” as used herein may refer to an application specific integrated circuit (ASIC), an electronic circuit, a processor (such as a shared processor, a proprietary processor, or a group of processors) used to execute one or more software or firmware programs. processor, etc.) and memory, merged logic circuitry, and/or other suitable components to support the described functionality.
  • ASIC application specific integrated circuit
  • the device 700 can be specifically the first SMF, AMF, terminal device, second SMF, data management network element or PCF in the above embodiment, and can be used to perform the above steps.
  • Each process and/or step corresponding to the first SMF, AMF, terminal equipment, second SMF, data management network element or PCF in the method embodiment, or the device 700 can be specifically the first SMF, AMF in the above embodiment.
  • the terminal device, the second SMF, the data management network element or the PCF can be used to execute each process corresponding to the first SMF, the AMF, the terminal device, the second SMF, the data management network element or the PCF in the above method embodiments and /or steps, to avoid repetition, will not be repeated here.
  • the device 700 of each of the above solutions has the function of implementing the corresponding steps performed by the first SMF, AMF, terminal equipment, second SMF, data management network element or PCF in the above method, or the device 700 of each of the above solutions has the function of implementing the above method.
  • the functions described can be implemented by hardware, or can be implemented by hardware executing corresponding software.
  • the hardware or software includes one or more modules corresponding to the above functions; for example, the transceiver unit can be replaced by a transceiver (for example, the sending unit in the transceiver unit can be replaced by a transmitter, and the receiving unit in the transceiver unit can be replaced by a receiving unit. (machine replacement), other units, such as processing units, etc., can be replaced by processors to respectively perform the sending and receiving operations and related processing operations in each method embodiment.
  • transceiver unit 710 may also be a transceiver circuit (for example, it may include a receiving circuit and a transmitting circuit), and the processing unit may be a processing circuit.
  • the device in Figure 7 can be the network element or device in the aforementioned embodiment, or it can be a chip or a chip system, such as a system on chip (SoC).
  • the transceiver unit may be an input-output circuit or a communication interface; the processing unit may be a processor, microprocessor, or integrated circuit integrated on the chip. No limitation is made here.
  • an embodiment of the present application provides another communication device 800 .
  • the device 800 includes a processor 810 coupled to a memory 820 for storing computer programs or instructions and/or data.
  • the processor 810 is used for executing computer programs or instructions stored in the memory 820, or reading the memory 820.
  • the stored data is used to execute the methods in the above method embodiments.
  • processors 810 there are one or more processors 810 .
  • the memory 820 is integrated with the processor 810, or is provided separately.
  • the device 800 also includes a transceiver 830, which is used for receiving and/or transmitting signals.
  • the processor 810 is used to control the transceiver 830 to receive and/or transmit signals.
  • the device 800 is used to implement the operations performed by the first SMF, AMF, terminal device, second SMF, data management network element or PCF in each of the above method embodiments.
  • the processor 810 is used to execute the computer program or instructions stored in the memory 820 to implement the related operations of the first SMF in each of the above method embodiments.
  • the first SMF in any one of the embodiments shown in FIGS. 2 to 6
  • the first SMF method in any one of the embodiments shown in FIGS. 2 to 6 .
  • processors mentioned in the embodiments of this application may be a central processing unit (CPU), or other general-purpose processor, digital signal processor (DSP), or application-specific integrated circuit (ASIC).
  • ASIC application specific integrated circuit
  • FPGA field programmable gate array
  • a general-purpose processor may be a microprocessor or the processor may be any conventional processor, etc.
  • non-volatile memory can be read-only memory (ROM), programmable ROM (PROM), erasable programmable read-only memory (erasable PROM, EPROM), electrically removable memory. Erase electrically programmable read-only memory (EPROM, EEPROM) or flash memory. Volatile memory can be random access memory (RAM). For example, RAM can be used as an external cache.
  • RAM includes the following forms: static random access memory (static RAM, SRAM), dynamic random access memory (dynamic RAM, DRAM), synchronous dynamic random access memory (synchronous DRAM, SDRAM), Double data rate synchronous dynamic random access memory (double data rate SDRAM, DDR SDRAM), enhanced synchronous dynamic random access memory (enhanced SDRAM, ESDRAM), synchronous link dynamic random access memory (synchlink DRAM, SLDRAM) and direct Memory bus random access memory (direct rambus RAM, DR RAM).
  • the processor is a general-purpose processor, DSP, ASIC, FPGA or other programmable logic device, discrete gate or transistor logic device, or discrete hardware component
  • the memory storage module
  • memories described herein are intended to include, but are not limited to, these and any other suitable types of memories.
  • an embodiment of the present application provides a chip system 900.
  • the chip system 900 (or can also be called a processing system) includes a logic circuit 910 and an input/output interface 920.
  • the logic circuit 910 may be a processing circuit in the chip system 900 .
  • the logic circuit 910 can be coupled to the memory unit and call instructions in the memory unit, so that the chip system 900 can implement the methods and functions of various embodiments of the present application.
  • the input/output interface 920 can be an input/output circuit in the chip system 900, which outputs information processed by the chip system 700, or inputs data or signaling information to be processed into the chip system 19000 for processing.
  • the chip system 1000 is used to implement the operations performed by the first SMF, AMF, terminal device, second SMF, data management network element or PCF in each of the above method embodiments.
  • the logic circuit 910 is used to implement operations related to the processing of the first SMF in the above method embodiments, such as operations related to the processing of the first SMF in any of the embodiments shown in Figures 2 to 6; input/ The output interface 920 is used to implement operations related to the sending and/or receiving of the first LMF in the above method embodiment, as shown in any of Figures 2 to 6. Means transmission and/or reception related operations performed by the first SMF in one of the illustrated embodiments.
  • Embodiments of the present application also provide a computer-readable storage medium on which is stored the method for implementing the method executed by the first SMF, AMF, terminal device, second SMF, data management network element or PCF in each of the above method embodiments.
  • Computer instructions are stored on a computer-readable storage medium on which is stored the method for implementing the method executed by the first SMF, AMF, terminal device, second SMF, data management network element or PCF in each of the above method embodiments.
  • the computer when the computer program is executed by a computer, the computer can implement the method executed by the first SMF, AMF, terminal device, second SMF, data management network element or PCF in each embodiment of the above method.
  • Embodiments of the present application also provide a computer program product, which includes instructions. When executed by a computer, the instructions are executed by the first SMF, AMF, terminal device, second SMF, data management network element, or PCF in the above embodiments. Methods.
  • the disclosed devices and methods can be implemented in other ways.
  • the device embodiments described above are only illustrative.
  • the division of the units is only a logical function division. In actual implementation, there may be other division methods.
  • multiple units or components may be combined or can be integrated into another system, or some features can be ignored, or not implemented.
  • the coupling or direct coupling or communication connection between each other shown or discussed may be through some interfaces, and the indirect coupling or communication connection of the devices or units may be in electrical, mechanical or other forms.
  • the computer may be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device.
  • the computer may be a personal computer, a server, or a network device.
  • the computer instructions may be stored in or transmitted from one computer-readable storage medium to another, e.g., the computer instructions may be transferred from a website, computer, server, or data center Transmission to another website, computer, server or data center by wired (such as coaxial cable, optical fiber, digital subscriber line (DSL)) or wireless (such as infrared, wireless, microwave, etc.) means.
  • the computer-readable storage medium may be any available medium that can be accessed by a computer or a data storage device such as a server, data center, etc. that contains one or more available media integrated.
  • the available media may be magnetic media (such as floppy disks, hard disks, magnetic tapes), optical media (such as DVDs), or semiconductor media (such as solid state disks (SSD)), etc.
  • the aforementioned available media include but Not limited to: U disk, mobile hard disk, read-only memory (ROM), random access memory (RAM), magnetic disk or optical disk and other media that can store program code.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Computer Security & Cryptography (AREA)
  • Databases & Information Systems (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

Les modes de réalisation de la présente demande concernent un procédé de communication et un appareil de communication. Le procédé de communication comprend les étapes suivantes : un premier élément réseau de gestion de session obtient des informations de sélection d'entité de fonction de découverte de service, les informations de sélection d'entité de fonction de découverte de service comprenant les informations d'une première entité de fonction de découverte de service et les informations d'une seconde entité de fonction de découverte de service, la première entité de fonction de découverte de service étant déployée dans un réseau mobile terrestre public visité, et la seconde entité de fonction de découverte de service étant déployée dans un réseau mobile terrestre public domestique ; et le premier élément réseau de gestion de session envoie les informations de sélection d'entité de fonction de découverte de service à un dispositif terminal, les informations de sélection d'entité de fonction de découverte de service servant à déterminer une entité de fonction de découverte de service cible, l'entité de fonction de découverte de service cible étant utilisée pour découvrir un service auquel le dispositif terminal doit accéder. Par conséquent, un UE peut déterminer l'entité de fonction de découverte de service utilisée pour découvrir le service auquel accéder parmi la pluralité d'entités de fonction de découverte de service déployées dans différents réseaux, ce qui permet d'éviter le problème selon lequel un DNS d'un service ne peut pas être correctement analysé, et d'améliorer ainsi l'expérience d'accès au service de l'utilisateur.
PCT/CN2023/082937 2022-03-28 2023-03-22 Procédé de communication et appareil de communication WO2023185561A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN202210312907.6A CN116866892A (zh) 2022-03-28 2022-03-28 通信方法和通信装置
CN202210312907.6 2022-03-28

Publications (1)

Publication Number Publication Date
WO2023185561A1 true WO2023185561A1 (fr) 2023-10-05

Family

ID=88199276

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2023/082937 WO2023185561A1 (fr) 2022-03-28 2023-03-22 Procédé de communication et appareil de communication

Country Status (2)

Country Link
CN (1) CN116866892A (fr)
WO (1) WO2023185561A1 (fr)

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN111434151A (zh) * 2017-12-22 2020-07-17 联想（新加坡）私人有限公司 网络片选择辅助信息配置
CN113115480A (zh) * 2021-04-02 2021-07-13 腾讯科技（深圳）有限公司 地址信息发送方法、获取方法、装置、设备及介质
WO2021253301A1 (fr) * 2020-06-17 2021-12-23 Lenovo (Beijing) Limited Procédé et appareil de fourniture d'informations de découverte de serveur

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN111434151A (zh) * 2017-12-22 2020-07-17 联想（新加坡）私人有限公司 网络片选择辅助信息配置
WO2021253301A1 (fr) * 2020-06-17 2021-12-23 Lenovo (Beijing) Limited Procédé et appareil de fourniture d'informations de découverte de serveur
CN113115480A (zh) * 2021-04-02 2021-07-13 腾讯科技（深圳）有限公司 地址信息发送方法、获取方法、装置、设备及介质

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
INTERDIGITAL, EUROPE, LTD.: "ECS Address Configuration Information for multiple EECs", 3GPP TSG-SA2 MEETING #145-E, S2-2104045, 10 May 2021 (2021-05-10), XP052004379 *

Also Published As

Publication number Publication date
CN116866892A (zh) 2023-10-10

Similar Documents

Publication Publication Date Title
WO2023280121A1 (fr) Procédé et appareil d'obtention de service de périphérie
EP4027684A1 (fr) Procédé de configuration de service, dispositif de communication et système de communication
WO2020151584A1 (fr) Procédé de configuration de réseau et appareil de communication
EP4354770A1 (fr) Procédé et appareil de transmission de données
EP4027744A1 (fr) Procédé de communication, appareil de communication et support de stockage
WO2022199451A1 (fr) Procédé et appareil de commutation de session
US20240107417A1 (en) Communication method and apparatus
CN113747605B (zh) 通信方法和通信装置
WO2023051430A1 (fr) Procédé et appareil de communication
WO2023185561A1 (fr) Procédé de communication et appareil de communication
CN117136534A (zh) 第一ims节点、第一核心网络节点、第二ims节点和在其中执行的方法
JP2023521113A (ja) 時刻同期パケット処理方法および装置
WO2023185620A1 (fr) Procédé et appareil de communication
WO2023116556A1 (fr) Procédé et appareil de commutation de session
WO2023143212A1 (fr) Procédé et appareil de communication
WO2023051427A1 (fr) Procédé et appareil de communication
WO2023160394A1 (fr) Procédé et appareil de communication
WO2023051428A1 (fr) Procédé et appareil de transmission d'informations
WO2023051431A1 (fr) Procédé et appareil de communication
WO2023185657A1 (fr) Procédé de communication et appareil de communication
WO2023142717A1 (fr) Procédé et appareil pour déterminer une politique de sélection d'itinéraire d'équipement utilisateur
WO2023103575A1 (fr) Procédé de communication de diffusion/multidiffusion et appareil associé
WO2023216696A1 (fr) Procédé et appareil de traitement d'informations
WO2022205453A1 (fr) Procédé et appareil de sélection de réseau
WO2024032041A1 (fr) Procédé de communication et appareil de communication

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 23777933

Country of ref document: EP

Kind code of ref document: A1