WO2023185441A1 - 一种通信方法及装置 - Google Patents

一种通信方法及装置 Download PDF

Info

Publication number
WO2023185441A1
WO2023185441A1 PCT/CN2023/081154 CN2023081154W WO2023185441A1 WO 2023185441 A1 WO2023185441 A1 WO 2023185441A1 CN 2023081154 W CN2023081154 W CN 2023081154W WO 2023185441 A1 WO2023185441 A1 WO 2023185441A1
Authority
WO
WIPO (PCT)
Prior art keywords
network element
visited
policy control
management network
session management
Prior art date
Application number
PCT/CN2023/081154
Other languages
English (en)
French (fr)
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 WO2023185441A1 publication Critical patent/WO2023185441A1/zh

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L5/00—Arrangements affording multiple use of the transmission path
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/10—Connection setup
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W8/00—Network data management
    • H04W8/02—Processing of mobility data, e.g. registration information at HLR [Home Location Register] or VLR [Visitor Location Register]; Transfer of mobility data, e.g. between HLR, VLR or external networks
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W8/00—Network data management
    • H04W8/02—Processing of mobility data, e.g. registration information at HLR [Home Location Register] or VLR [Visitor Location Register]; Transfer of mobility data, e.g. between HLR, VLR or external networks
    • H04W8/08—Mobility data transfer
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W8/00—Network data management
    • H04W8/22—Processing or transfer of terminal data, e.g. status or physical capabilities
    • H04W8/24—Transfer of terminal data
    • 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 wireless communications, and in particular, to a communication method and device.
  • the 3rd generation partnership project (3GPP) defines the uplink classifier (UL CL) function for the data offloading of the 5th Generation Mobile Communication Technology (5G) user plane.
  • the classifier user plane network element uplink classifier user plane function, UL CL UPF
  • DL CL UPF uplink classifier user plane function
  • DN local data network
  • Internet Internet
  • the session management network element determines whether the data of the terminal device needs to be offloaded to the local DN. If offloading is required, the UL CL UPF and secondary anchor UPF are selected for the terminal device. Insert UL CL UPF and secondary anchor UPF into the current session, and issue corresponding offload rules to UL CL UPF to implement offload control of data from terminal devices.
  • the session management network element determines whether the data of the terminal device needs to be offloaded to the local DN, the session management network element needs to obtain the offloading information of the terminal device from the policy control network element.
  • This application provides a communication method and device to solve the problem that current roaming users cannot use the ULCL function to access local services in the place of visit.
  • this application provides a communication method.
  • the method includes: the access and mobility management network element receives a first message from a terminal device, the first message is used to request to establish a first message for the terminal device. session, the terminal device is a roaming user.
  • the access and mobility management network element selects a visited session management network element for the terminal device, and sends a second message to the visited session management network element, where the second message is used to request a visit to the terminal device.
  • the first session is established, and the second message includes the identity of the visited policy control network element.
  • the access and mobility management network element can provide the visited session management network element with the identity of the visited policy control network element, thereby enabling the visited session management network element to obtain the identity of the terminal device from the visited policy control network element. Offload information to enable roaming users to use the ULCL function to access local services at the place of visit.
  • the access and mobility management network element registers the terminal device During the process, the identity of the visited policy control network element is obtained.
  • the access and mobility management network element sends the identification of the terminal device to the network warehousing function network element to query the PCF information, and the network warehousing function network element sends the identification to the access and mobility management network element.
  • the visited location policy controls the identification of the network element.
  • the identifier of the visited policy control network element includes an identifier of an instance of the visited policy control network element, or a fully qualified domain name of the visited policy control network element.
  • this application provides a communication method, which method includes: the visited session management network element receives a second message from the access and mobility management network element, where the second message is used to request the establishment of a terminal device.
  • the second message includes the identity of the visited policy control network element, and the terminal device is a roaming user.
  • the visited session management network element sends a third message to the visited policy control network element according to the identification of the visited policy control network element, where the third message is used to request offload information of the terminal device;
  • the visited session management network element receives the offload information from the visited policy control network element.
  • the visited session management network element obtains the identity of the visited policy control network element, obtains the offloading information from the visited policy control network element, and then creates a ULCL session for the roaming user, thereby ensuring that the roaming user uses the ULCL function to access Local data network.
  • the visited session management network element when the visited session management network element sends the third message to the visited policy control network element according to the identifier of the visited policy control network element, the visited session management network The visited site session management network element obtains the IP address of the visited site policy control network element according to the identification of the visited site policy control network element, and the visited site session management network element sends the visited site policy control network element's IP address to the visited site based on the IP address of the visited site policy control network element. The policy controls the network element to send the third message.
  • the identifier of the visited location policy control network element includes an identifier of an instance of the visited location policy control network element; in the visited location session management network element, the visited location policy control network element is controlled according to the visited location policy control network element.
  • the visited session management network element sends the identifier of the instance of the visited policy control network element to the network warehousing function network element.
  • the visited session management The network element receives the IP address of the visited policy control network element from the network warehousing function network element.
  • the visited location policy control network element is a fully qualified domain name; the visited location session management network element obtains the visited location policy control network element according to the identifier of the visited location policy control network element.
  • the IP address is an IP address
  • the visited session management network element sends the fully qualified domain name of the visited policy control network element to the domain name system, and the visited session management network element receives the visited session management network element from the domain name system.
  • the policy controls the IP address of the network element.
  • the visited location session management network element can obtain the IP address of the visited location policy control network element in different ways according to different types of identifiers of the visited location policy control network element.
  • the offload information includes at least one of offload rules, application identifiers, data detection rules corresponding to the application identifiers, data forwarding rules, and bandwidth control rules.
  • the present application provides a communication method, which method includes: the visited policy control network element receives a third message from the visited session management network element, where the third message is used to request offload information of the terminal device, The terminal device is a roaming user, and the visited policy control network element sends the offload information to the visited session management network element.
  • the visited policy control network element sends offload information to the visited session management network element, thereby enabling the visited session management network element to create a ULCL session for the roaming user, thereby ensuring that the roaming user uses the ULCL function to access the local data network.
  • the method further includes: the visited policy control network element sending a request message to the home policy control network element, where the request message is used to request the offload information, and the visited policy control network element from said place of origin The policy control network element receives the offload information.
  • the visited policy control network element can obtain offload information from the home policy control network element.
  • the offload information includes at least one of offload rules, application identifiers, data detection rules corresponding to the application identifiers, data forwarding rules, and bandwidth control rules.
  • this application provides a communication method, which method includes: the access and mobility management network element receives a first message from a terminal device, the first message is used to request the establishment of a first message for the terminal device. session, the terminal device is a roaming user, the access and mobility management network element selects a visited session management network element for the terminal device, and the access and mobility management network element provides a policy control network element to the visited location. Send the identity of the visited session management network element and the identity of the terminal device.
  • the access and mobility management network element provides the visited session management network element's identification to the visited policy control network element, thereby enabling the offloading of terminal devices sent by the visited policy control network element to the visited session management network element.
  • the identifier of the visited session management network element includes an identifier of an instance of the visited session management network element or a fully qualified domain name of the visited session management network element.
  • the method further includes: the access and mobility management network element obtains the IP address of the terminal device, and the access and mobility management network element sends a message to the visited policy control network element.
  • the IP address of the terminal device is not limited to: the access and mobility management network element.
  • the present application provides a communication method, which method includes: the visited policy control network element receiving the identity of the visited session management network element and the identity of the terminal device from the access and mobility management network element, said The terminal device is a roaming user, and the visited policy control network element sends the offload information of the terminal device to the visited session management network element according to the identifier of the terminal device and the identifier of the visited session management network element.
  • the policy control network element in the visited location can obtain the identity of the session management network element in the visited location, and then can send the offload information of the terminal device to the session management network element in the visited location, so that roaming users can use the ULCL function to access local services in the visited location. .
  • the visited policy control network element sends the terminal device's information to the visited session management network element according to the identity of the terminal device and the identity of the visited session management network element.
  • the visited policy control network element obtains the IP address of the visited session management network element according to the identifier of the visited session management network element, and the visited policy control network element obtains the IP address of the visited session management network element based on the identification of the terminal device.
  • the identifier and the IP address of the visited session management network element are used to send the offload information of the terminal device to the visited session management network element.
  • the identifier of the visited session management network element is an identifier of an instance of the visited session management network element; in the visited policy control network element, the visited session management network element is When acquiring the IP address of the visited session management network element, the visited policy control network element sends the identifier of the instance of the visited session management network element to the network warehousing function network element. The visited policy control network element The network element receives the IP address of the visited session management network element from the network warehousing function.
  • the identifier of the visited session management network element is the fully qualified domain name of the visited session management network element; the visited policy control network element is based on the visited session management network element.
  • the visited policy control network element sends the fully qualified domain name of the visited session management network element to the domain name system, and the visited policy control network element sends the IP address of the visited session management network element to the domain name system.
  • the domain name system receives the IP address of the visited session management network element.
  • the visited location session management network element can obtain the IP address of the visited location policy control network element in different ways according to different types of identifiers of the visited location policy control network element.
  • the method further includes: the visited policy control network element sending a request message to the home policy control network element, where the request message is used to request the offload information, and the visited policy control network element The offload information is received from the home policy control network element.
  • the offload information includes at least one of offload rules, application identifiers, data detection rules corresponding to the application identifiers, data forwarding rules, and bandwidth control rules.
  • the method further includes: the visited location policy control network element receiving the IP address of the terminal device from the access and mobility management network element; and the visited location policy control network element sending the visited location policy control network element to the visited location.
  • the guidance service network element sends a registration message, where the registration message includes the identifier of the instance of the visited policy control network element and the IP address of the terminal device.
  • the guidance service network element determines the visited location policy corresponding to the IP address of the terminal device based on the IP address of the terminal device.
  • the identifier of the instance of the control network element and the identifier of the instance of the visited location policy control network element are sent to the capability opening function network element, so that the capability opening function network element can determine the visited location policy control network element corresponding to the terminal device.
  • the present application provides a communication device, which includes: a transceiver unit and a processing unit; the transceiver unit is used to receive a first message from a terminal device, where the first message is used to request the The terminal device establishes a first session, and the terminal device is a roaming user; the processing unit is used to select a visited session management network element for the terminal device; the transceiver unit is used to send a message to the visited session management network element; The second message is used to request the establishment of the first session for the terminal device, and the second message includes the identity of the visited policy control network element.
  • the processing unit is configured to obtain the identity of the visited policy control network element during the registration process of the terminal device.
  • the identifier of the visited policy control network element includes an identifier of an instance of the visited policy control network element, or a fully qualified domain name of the visited policy control network element.
  • this application provides a communication device, which includes: a transceiver unit and a processing unit; the processing unit calls the transceiver unit to receive a second message from an access and mobility management network element, The second message is used to request the establishment of a first session for a terminal device.
  • the second message includes the identity of the visited policy control network element, and the terminal device is a roaming user; according to the identity of the visited policy control network element Send a third message to the visited policy control network element, where the third message is used to request offload information of the terminal device, and receive the offload information from the visited policy control network element.
  • the processing unit is configured to, when sending a third message to the visited policy control network element according to the identity of the visited policy control network element, control the network according to the visited policy control network element.
  • the identifier of the element obtains the IP address of the visited policy control network element;
  • the transceiver unit is configured to send the third message to the visited policy control network element according to the IP address of the visited policy control network element.
  • the identifier of the visited location policy control network element includes an identifier of an instance of the visited location policy control network element; and the visited location policy is obtained according to the identifier of the visited location policy control network element.
  • the transceiver unit is used to send the identification of the instance of the visited location policy control network element to the network warehousing function network element, and receive the visited location from the network warehousing function network element.
  • the policy controls the IP address of the network element.
  • the visited location policy control network element is a fully qualified domain name; the transceiver unit is configured to obtain the visited location policy control network element's ID according to the identifier of the visited location policy control network element.
  • the fully qualified domain name of the visited location policy control network element is sent to the domain name system, and the IP address of the visited location policy control network element is received from the domain name system.
  • the offload information includes at least one of offload rules, application identifiers, data detection rules corresponding to the application identifiers, data forwarding rules, and bandwidth control rules.
  • the present application provides a communication device, which includes: a transceiver unit and a processing unit; the processing unit calls the transceiver unit to receive the third message from the visited session management network element, the The third message is used to request offload information of a terminal device, which is a roaming user, and to send the offload information to the visited session management network element.
  • the transceiver unit is configured to send a request message to a home policy control network element, where the request message is used to request the offload information, and to receive the offload information from the home policy control network element. Divert information.
  • the offload information includes at least one of offload rules, application identifiers, data detection rules corresponding to the application identifiers, data forwarding rules, and bandwidth control rules.
  • the present application provides a communication device, which includes: a transceiver unit and a processing unit; the transceiver unit is configured to receive a first message from a terminal device, where the first message is used to request the A terminal device establishes a first session, and the terminal device is a roaming user; the processing unit is used to select a visited session management network element for the terminal device; and the transceiver unit is used to send a message to a visited policy control network element.
  • the identifier of the visited session management network element includes an identifier of an instance of the visited session management network element or a fully qualified domain name of the visited session management network element.
  • the processing unit is configured to obtain the IP address of the terminal device; and the transceiver unit is configured to send the IP address of the terminal device to the visited policy control network element.
  • the present application provides a communication device, which includes: a transceiver unit and a processing unit; the processing unit calls the transceiver unit to receive the visited session management from the access and mobility management network element The identifier of the network element and the identifier of the terminal device.
  • the terminal device is a roaming user.
  • the terminal device is sent to the visited session management network element according to the identifier of the terminal device and the identifier of the visited session management network element. diversion information.
  • the processing unit is configured to send the offload of the terminal device to the visited session management network element according to the identifier of the terminal device and the identifier of the visited session management network element.
  • the transceiver unit is configured to obtain the IP address of the visited session management network element according to the identification of the terminal device and the visited session management network element.
  • the IP address of the terminal device is used to send the offload information of the terminal device to the visited session management network element.
  • the identifier of the visited session management network element is an identifier of an instance of the visited session management network element;
  • the IP address of the visited session management network element is acquired, the identifier of the instance of the visited session management network element is sent to the network warehousing function network element, and the visited session management network element is received from the network warehousing function. IP address.
  • the identifier of the visited session management network element is a fully qualified domain name of the visited session management network element;
  • the fully qualified domain name of the visited session management network element is sent to the domain name system, and the visited policy control network element receives the visited session management network element from the domain name system. IP address of the session management network element.
  • the transceiver unit is configured to send a request message to a home policy control network element, where the request message is used to request the offload information, and to receive the offload information from the home policy control network element. Divert information.
  • the offload information includes at least one of offload rules, application identifiers, data detection rules corresponding to the application identifiers, data forwarding rules, and bandwidth control rules.
  • the transceiver unit is configured to receive the IP address of the terminal device from the access and mobility management network element; and send a registration message to the visited guidance service network element.
  • the registration message It includes the identification of the instance of the visited policy control network element and the IP address of the terminal device.
  • the present application also provides a device.
  • the device can perform the above method design.
  • the device may be a chip or circuit capable of performing the functions corresponding to the above methods, or a device including the chip or circuit.
  • the device includes: a memory for storing computer executable program code; and a processor, the processor is coupled to the memory.
  • the program code stored in the memory includes instructions, and when the processor executes the instructions, the device or the device installed with the device executes the method in any of the above possible designs.
  • the device may further include a communication interface, which may be a transceiver, or, if the device is a chip or a circuit, the communication interface may be an input/output interface of the chip, such as an input/output pin, etc.
  • a communication interface which may be a transceiver, or, if the device is a chip or a circuit, the communication interface may be an input/output interface of the chip, such as an input/output pin, etc.
  • the device includes corresponding functional units, respectively used to implement the steps in the above method.
  • Functions can be implemented by hardware, or by hardware executing corresponding software.
  • Hardware or software includes one or more units corresponding to the above functions.
  • the present application provides a computer-readable storage medium.
  • the computer-readable storage medium stores a computer program.
  • the method in any of the above possible designs is executed. .
  • the present application provides a computer program product.
  • the computer program product includes a computer program.
  • the computer program When the computer program is run on a device, the method in any of the above possible designs is executed.
  • Figure 1 is an architectural diagram of the roaming scenario applied in this application.
  • Figure 2 is a schematic diagram of the network architecture of ULCL applied in this application.
  • Figure 3 is an overview flow chart of a communication method in this application.
  • FIG. 4 is an overview flow chart of another communication method in this application.
  • Figure 5 is a flow chart of creating a ULCL session in the session establishment process in this application.
  • Figure 6 is a flow chart of creating a ULCL session in the location update process in this application.
  • Figure 7 is a flow chart of creating a ULCL session in the service request process in this application.
  • Figure 8 is a flow chart of creating a ULCL session after the session establishment process in this application.
  • Figure 9 is a flow chart of creating a ULCL session after the location update process in this application.
  • Figure 10 is a flow chart of creating a ULCL session after the service request process in this application.
  • Figure 11 is a registration flow chart for the identification of the instance of the visited policy control network element and the IP address of the terminal device in this application;
  • Figure 12 is one of the structural schematic diagrams of a communication device in this application.
  • Figure 13 is the second structural schematic diagram of a communication device in this application.
  • At least one of a, b, or c can mean: a, b, c, a-b, a-c, b-c, or a-b-c, where a, b, c can be single or multiple .
  • Roaming is a term commonly used by mobile phone users. It refers to the function that the mobile communication system can still provide services to mobile users after they leave the service area where they are registered and move to another service area.
  • the functions here may include automatic tracking and positioning of roaming user locations through mobile communication networks.
  • domestic roaming refers to making or answering calls with domestic users when leaving the city where the number belongs
  • international roaming which means that you can also enjoy a series of services provided by domestic operators abroad. For example, phone calls, mobile Internet access, etc. It is understandable that roaming can only be carried out between domestic cities with compatible network standards and already connected to the Internet, or between regions or countries that have signed bilateral roaming agreements.
  • the roaming type of the terminal device is any one of local user, roaming user or visiting user.
  • the subscriber identity module (SIM) card of the terminal device stores the Home Public Land Mobile Network (HPLMN) to which the terminal belongs, and the terminal device can report the HPLMN to the core network device through the access network device. Specifically, after the terminal device enters the connected state, the terminal device can send the HPLMN to the core network device through the access network device.
  • SIM subscriber identity module
  • the core network device can determine the roaming type of the terminal device based on the HPLMN reported by the terminal device and the currently deployed PLMN stored by the core network device.
  • the core network device determines that the roaming type of the terminal device is a local user.
  • the core network device determines that the roaming type of the terminal device is a roaming user.
  • the core network provides roaming services for terminal devices.
  • the core network device determines that the roaming type of the terminal device is a visiting user.
  • the services obtained by the terminal device are limited.
  • the terminal device can only implement emergency calls.
  • the core network device may send the roaming type of the terminal device to the terminal device.
  • the terminal device can obtain the PLMN through the system information block (SIB) message broadcast by the current cell, and the terminal device can also determine the roaming type by itself. In the same way, if the terminal device determines that the HPLMN and PLMN are the same, it determines that its roaming type is a local user. The terminal device determines that HPLMN and PLMN are not If they are the same, determine your roaming type as a roaming user or a visiting user.
  • SIB system information block
  • HPLMN includes Mobile Country Code (MCC) and Mobile Network Code (Mobile Network Code, MNC), and PLMN includes MCC and MNC.
  • MCC Mobile Country Code
  • MNC Mobile Network Code
  • PLMN includes MCC and MNC.
  • MCC Mobile Country Code
  • MNC Mobile Network Code
  • MNC Mobile Network Code
  • HPLMN and PLMN are different means that the MCC included in HPLMN is the same as the MCC included in PLMN, the MNC included in HPLMN is different from the MNC included in PLMN, or the MCC included in HPLMN is different from the MCC included in PLMN, the MNC included in HPLMN is the same as the MNC included in PLMN, or The MCC included in HPLMN is different from the MCC included in PLMN, and the MNC included in HPLMN is different from the MNC included in PLMN.
  • the offload information may include at least one of offload rules, application identifiers, data detection rules corresponding to the application identifiers, data forwarding rules, and bandwidth control rules.
  • FIG 1 shows the architecture diagram of the roaming scenario. The functions of the equipment involved in Figure 1 are briefly described below.
  • the terminal device is the entrance for mobile users to interact with the network. It can provide basic computing capabilities and storage capabilities, display business windows to users, and receive user operation inputs.
  • Next-generation terminal equipment NextGen UE
  • NextGen UE can use new air interface technology to establish signal connections and data connections with the RAN, thereby transmitting control signals and business data to the mobile network.
  • Terminal devices can include various handheld devices with wireless communication functions, vehicle-mounted devices, wearable devices, computing devices or other processing devices connected to wireless modems, as well as various forms of terminals, mobile stations (MS), terminals (terminal), soft terminal, etc., such as water meters, electricity meters, sensors, etc.
  • Access network (AN) equipment or wireless access network (AN) equipment Deployed close to the terminal equipment, it provides network access functions for authorized users in a specific area, and can adjust the service level according to the user level. Requirements, etc. determine transmission tunnels of different qualities to transmit user data.
  • RAN can manage its own resources, utilize them rationally, provide access services to terminal devices on demand, and is responsible for forwarding control signals and user data between terminal devices and the core network.
  • Data network A data network that provides business services to users.
  • the client is located in the terminal device and the server is located in the data network.
  • the data network can be a private network, such as a local area network, or an external network that is not controlled by the operator, such as the Internet. It can also be a proprietary network deployed by operators, such as an IP multimedia network subsystem. core network subsystem, IMS) service network.
  • IMS IP multimedia network subsystem
  • the core network user plane includes user plane function (UPF); the core network control plane includes access and mobility management function (AMF), session management function (SMF) , unified data management (UDM), policy control function (PCF), application function (AF), authentication server function (AUSF), network slice selection function (network slice selection function (NSSF), network slice-specific authentication and authorization function (NSSAAF).
  • UPF user plane function
  • AMF access and mobility management function
  • SMF session management function
  • UDM unified data management
  • PCF policy control function
  • AF application function
  • AUSF authentication server function
  • NSSF network slice selection function
  • NSSAAF network slice-specific authentication and authorization function
  • the core network control plane adopts a service-oriented architecture, and the interaction between control plane network elements adopts service invocation to replace the point-to-point communication method in the traditional architecture.
  • control plane network elements will open services to other control plane network elements for calls by other control plane network elements; in point-to-point communication, the communication interfaces between control plane network elements will store a specific set of messages, only It can be used by the control plane network elements at both ends of the interface during communication.
  • Session management network element Mainly used for session management, IP address allocation and management of terminal equipment, selecting endpoints that can manage user equipment plane functions, policy control, or charging function interfaces, and downlink data notifications.
  • the session management network element can be an SMF network element.
  • the session management function network element can still be an SMF network element, or have other names. This application does not limit this.
  • Nsmf is a service-based interface provided by SMF. SMF can communicate with other network functions through Nsmf.
  • Access management network element It is mainly used for mobility management and access management.
  • it can be the mobility management entity (MME) function in the 4G communication network or the AMF network element in the 5G network.
  • MME mobility management entity
  • the access management network element can still be an AMF network element, or have other names, which is not limited in this application.
  • Namf is a service-based interface provided by AMF. AMF can communicate with other network functions through Namf.
  • Policy control network element A unified policy framework used to guide network behavior and provide policy rule information for control plane functional network elements (such as AMF, SMF, etc.).
  • the policy control network element can be a PCF network element.
  • future communications such as 6G communications, the policy control network element can still be a PCF network element, or have other names. This application does not limit this.
  • Npcf is a service-based interface provided by PCF. PCF can communicate with other network functions through Npcf.
  • Data management network element used to process user identification, subscription, access authentication, registration, or mobility management, etc.
  • the data management network element can be a UDM network element.
  • future communications such as 6G communication, the data management network element can still be a UDM network element, or have other names. This application does not limit this.
  • Nudm is a service-based interface provided by UDM. UDM can communicate with other network functions through Nudm.
  • Application network element used for data routing affected by applications, access to network open functions, or interaction with the policy framework for policy control, etc.
  • the application network element can be an AF network element.
  • future communications such as 6G communication, the application network element can still be an AF network element, or have other names. This application does not limit this.
  • Naf is a service-based interface provided by AF. AF can communicate with other network functions through Naf.
  • User plane network element used for packet routing and forwarding, or quality of service (QoS) processing of user plane data.
  • QoS quality of service
  • user plane network elements can be user plane function (UPF) network elements.
  • UPF user plane function
  • user plane network elements can still be UPF network elements, or have other names. This application There is no limit to this.
  • Authentication service network element mainly used for user authentication, etc.
  • the authentication service network element can be an AUSF network element.
  • future communications such as 6G communication, the authentication service network element can still be an AUSF network element, or have other names. This application does not limit this.
  • Nausf is a service-based interface provided by AUSF.
  • AUSF can communicate with other network functions through Nausf.
  • Network slicing selection function network element used to select network slices for terminal devices.
  • network slicing selection function network elements can be NSSF network elements.
  • future communications such as 6G communications, network slicing selection function network elements will still be used. It may be an NSSF network element or have other names, which is not limited in this application.
  • Authentication and authorization function network elements selected by network slicing used to perform slice authentication for terminal devices.
  • H-SMF, H-PCF and H-NSSF are home SMF, home PCF and home NSSF respectively, and V-SMF, V-PCF and V-NSSF are respectively They are the visit SMF, the visit PCF and the visit NSSF.
  • V-SMF and H-PCF can communicate through the N24 interface, and V-SMF and H-SMF can communicate through the N16 interface.
  • H-PCF can send user subscription policy data to V-SMF through H-SMF.
  • the policy data subscribed by the user includes information related to policy control and billing control of the data of the terminal device by the home UPF when the terminal device accesses the general data network (for example, the Internet) through the home UPF, such as bandwidth control information. , billing method information, etc.
  • the policy data of user signing does not include diversion information.
  • FIG. 2 shows a schematic diagram of the network architecture of ULCL.
  • UPF can have three forms: center UPF, edge UPF, and UL CL UPF. Table 1 below explains the three UPF forms.
  • UE1 wants to access the network outside the campus (i.e., the Internet).
  • UE1 sends uplink data to ULCLUPF through the RAN, and ULCLUPF diverts the uplink data to the central UPF based on the characteristics of the uplink data, and then the central UPF further forwards the uplink data to the Internet.
  • the central UPF receives downlink data from the Internet and forwards the downlink data to ULCLUPF, which forwards the downlink data to UE1 through the RAN.
  • UE2 wants to access the network within the campus (i.e. local DN).
  • UE2 sends uplink data to ULCLUPF through the RAN, and ULCLUPF offloads the uplink data to the edge UPF based on the characteristics of the uplink data, and further forwards the uplink data to the local DN by the edge UPF.
  • the edge UPF receives the downlink data from the local DN and forwards the downlink data to ULCLUPF, which forwards the downlink data to UE1 through the RAN.
  • Table 2 shows the description of the user plane related interfaces in Figure 2.
  • the following illustrates a scenario in which a terminal device uses the ULCL function to access local services (ie, an offload scenario). It can be understood that the following scenario is only an example and is not a limitation of this application.
  • the terminal device hopes to purchase and use a specific package in a specific area, that is, to access local services.
  • the specific area may refer to the area where the local DN is configured.
  • specific areas are venues for large-scale events, tourist attractions, large-scale exhibitions, university campuses, and corporate campuses.
  • Scenario 1 When the specific area is a venue for a large-scale event, the terminal device hopes to access the local DN through an application that broadcasts the event to watch without traffic. If the terminal device is a non-roaming user, the session management network element can determine the data for the terminal device based on the offloading information, select the UL CL UPF and secondary anchor UPF for the terminal device, and insert the UL CL UPF and secondary anchor UPF into the current In the session, the corresponding offload rules are issued to UL CL UPF to realize the offload control of the data of the terminal device, and then the terminal device can access the local DN to watch without traffic through the application that broadcasts the event.
  • the terminal device cannot access the local DN for free traffic viewing through the application that broadcasts the event.
  • Scenario 2 When the specific area is a tourist attraction, the terminal device hopes to access the local DN through the application of the tourist attraction to listen to the explanation of the attraction. Similar to scenario 1 above, if the terminal device is a roaming user, the terminal device cannot access the local DN through the application of the tourist attraction to listen to the attraction explanation.
  • Scenario 3 When the specific area is a large-scale exhibition, the terminal device hopes to access the local DN through the application of the exhibition to obtain the booth information of the exhibition. Similar to Scenario 1 and Scenario 2 above, if the terminal device is a roaming user, the terminal device cannot access the local DN through the application of the exhibition to obtain the booth information of the exhibition.
  • Scenario 4 when the specific area is an enterprise campus or a university campus, the terminal device hopes to access the local DN to obtain information through the corresponding application. Similar to the above scenario 1, scenario 2 and scenario 3, if the terminal device is a roaming user, the terminal device cannot access the local DN to obtain information through the corresponding application.
  • the session management network element cannot obtain the offload information of the terminal device, and the session management network element cannot determine whether it is needed.
  • the data of the terminal device is offloaded to the local DN, so the terminal device cannot use the ULCL function to access local services at the visited location.
  • embodiments of the present application provide a communication method to solve the problem that current roaming users cannot use the ULCL function to access local services in the place of visit.
  • the method includes:
  • Step 301 The access and mobility management network element receives the first message from the terminal device, and the terminal device is a roaming user.
  • the first message may include but is not limited to the following possible implementation methods:
  • Method 1 The first message is used to request the establishment of a first session for the terminal device.
  • the terminal device may send the first message to the access and mobility management network element through the access network device.
  • the first message may be a protocol data unit (Protocol data unit, PDU) session establishment request message.
  • PDU Protocol data unit
  • Method 2 The first message is used to request mobility registration.
  • the terminal device may send the first message to the access and mobility management network element through the access network device.
  • the first message may be a mobility registration request (mobilityregistrationrequest) message.
  • Method 3 The first message is used to request services.
  • the terminal device may send the first message to the access and mobility management network element through the access network device.
  • the first message may be a service request (servicerequest) message.
  • Step 302 The access and mobility management network element selects a visited session management network element for the terminal device.
  • the access and mobility management network element needs to select the visited session management network element for the terminal device.
  • the access and mobility management network element selects a visited session management network element for the terminal device to refer to the existing process, which will not be described again here.
  • step 302 is an optional step.
  • Step 303 The access and mobility management network element sends a second message to the visited session management network element, where the second message includes the identifier of the visited policy control network element.
  • the second message also needs to carry the identification of the terminal device.
  • the identification of the terminal device may include an international mobile subscriber identity (IMSI), a mobile subscriber number (mobile subscriber international ISDN/PSTN number, MSISDN), or a user permanent identifier (subscription permanent identifier, SUPI). ), or at least one of the generic public subscription identifier (GPSI), or the International Mobile Equipment Identity (IMEI).
  • IMSI international mobile subscriber identity
  • MSISDN mobile subscriber international ISDN/PSTN number
  • SUPI subscription permanent identifier
  • GSSI generic public subscription identifier
  • IMEI International Mobile Equipment Identity
  • the second message is used to request to establish a first session for the terminal device.
  • the second message may be a PDU session management context establishment request (Nsmf_PDUSession_CreateSMContext) message.
  • the second message is used to request mobility registration.
  • the second message may be a PDU session management context update request (Nsmf_PDUSession_UpdateSMContext) message.
  • the second message is used to request services.
  • the second message may be a PDU session management context update request (Nsmf_PDUSession_UpdateSMContext) message.
  • the access and mobility management network element obtains the identity of the visited policy control network element during the registration process of the terminal device. It can be understood that during the registration process of the terminal device, the access and mobility management network element needs to exchange information with the visited policy control network element to obtain the identity of the visited policy control network element. For example, during the registration process, the access and mobility management network element sends the identification of the terminal device, such as SUPI or GPSI, to the network repository function (NRF) network element to query the PCF information. The network repository function The network element sends the identity of the visited policy control network element to the access and mobility management network element.
  • the identification of the terminal device such as SUPI or GPSI
  • NRF network repository function
  • the network element sends the identity of the visited policy control network element to the access and mobility management network element.
  • the identifier of the visited policy control network element includes the identifier (PCF Instance ID) of the visited policy control network element, or the fully qualified domain name of the visited policy control network element.
  • Step 304 The visited session management network element receives the second message from the access and mobility management network element, and the visited session management network element sends a third message to the visited policy control network element according to the identifier of the visited policy control network element.
  • message, the third message is used to request offload information of the terminal device.
  • the third message may include the identification of the terminal device.
  • the third message is a session management policy control establishment (Npcf_SMPolicyControl_Create) message.
  • the visited session management network element can obtain the IP address of the visited policy control network element according to the identifier of the visited policy control network element. For example, the visited session management network element can save the visited session management network element. The correspondence between the identifier of the session management network element and the IP address of the visited policy control network element. Furthermore, the visited session management network element can query the IP address of the visited policy control network element according to the identity of the visited policy control network element, and send a third party message to the visited policy control network element based on the IP address of the visited policy control network element. information.
  • the visited session management network element can send the identifier of the instance of the visited policy control network element to the network repository function (NRF), and the network repository function network element can save the visited The corresponding relationship between the identifier of the instance of the local policy control network element and the IP address of the visited local policy control network element.
  • Network warehousing function network elements can query the IP of the visited policy control network element based on the identification of the instance of the visited policy control network element. address, and sends the IP address of the visited policy control network element to the visited session management network element.
  • the visited session management network element can send the fully qualified domain name of the visited policy control network element to the domain name system (DNS), and the domain name system can save the domain name of the visited policy control network element.
  • DNS domain name system
  • the domain name system can query the IP address of the visited policy control network element based on the fully qualified domain name of the visited policy control network element, and send the IP address of the visited policy control network element to the visited session management network element.
  • Step 305 The visited policy control network element receives the third message from the visited session management network element, and the visited policy control network element sends offload information to the visited session management network element.
  • the visited policy control network element sends a session management policy control establishment response message to the visited session management network element, and the session management policy control establishment response message carries the offloading information.
  • the visited location policy control network element can obtain offload information in but not limited to the following two ways:
  • the visited policy control network element can determine that the terminal device is a roaming user based on the identification of the terminal device in the third message, and further sends a request message to the home policy control network element.
  • the request message is used to request For offloading information, the visited policy control network element receives the offloading information from the home policy control network element.
  • the visited policy control network element can determine that the terminal device has purchased a service that requires offloading information based on the identification of the terminal device in the third message, and the visited policy control network element can sign a offloading contract for the roaming user. information. For example, if a user is located at tourist attraction A and downloads and logs in to the APP of tourist attraction A through a mobile phone, and the user purchases the tour package for tourist attraction A provided by the APP, the visiting place policy control network element will sign a diversion information for the mobile phone.
  • the visited session management network element can obtain offload information, thereby creating a ULCL session for the roaming user, thereby ensuring that the roaming user uses the ULCL function to access the local data network.
  • the embodiment of the present application also provides a communication method to solve the problem that current roaming users cannot use the ULCL function to access local services in the place of visit. As shown in Figure 4, the method includes:
  • steps 401 and 402 reference may be made to the relevant descriptions in the above steps 301 and 302, which will not be described again here.
  • Step 403 The access and mobility management network element sends the identity of the visiting session management network element and the identity of the terminal device to the visiting policy control network element.
  • the access and mobility management network element may send an access management policy control update request message to the visited policy control network element.
  • the access management policy control update request message includes the identity of the visited session management network element and the terminal device. logo.
  • the identification of the visited session management network element includes the identification of an instance of the visited session management network element (for example, V-SMF Instance ID), or the fully qualified domain name of the visited session management network element (for example, V-SMF FQDN).
  • the visited policy control network element can also send an access management policy control update response message to the access and mobility management network element.
  • the access management policy control update response message It can include access management policy.
  • the access management policy can include slice information of user affiliation, DNN, etc.
  • Step 404 The visited location policy control network element receives the identifier of the visited session management network element and the identifier of the terminal device from the access and mobility management network element, and sends a request to the visited location based on the identifier of the visited session management network element and the identifier of the terminal device. visit The local session management network element sends the offload information of the terminal device.
  • the visited location policy control network element when the visited location policy control network element sends the offload information of the terminal device to the visited location session management network element based on the identity of the terminal device and the identity of the visited location session management network element, the visited location policy control network element sends the offload information of the terminal device to the visited location session management network element based on the visited location session management network element.
  • the identity of the management network element obtains the IP address of the visited session management network element.
  • the visited policy control network element sends the offload information of the terminal device to the visited session management network element based on the identifier of the terminal device and the IP address of the visited session management network element.
  • the visited policy control network element sends the visited session management network element's identifier to the network function storage network element.
  • the network function storage network element queries the IP address of the visited session management network element based on the instance identifier of the visited session management network element according to the instance identifier, and sends the IP address of the visited session management network element to the visited policy control network element.
  • the visited location policy control network element sends the visited location to the domain name system (domain name system, DNS) The fully qualified domain name of the session management network element.
  • DNS domain name system
  • the domain name system queries the IP address of the visited session management network element based on the fully qualified domain name of the visited session management network element, and sends the IP address of the visited session management network element to the visited policy control network element. address.
  • step 305 Regarding the offload information and how the visited policy control network element obtains the offload information, please refer to the relevant description in step 305 above and will not be described again here.
  • Figure 5 shows the flow chart of creating a ULCL session in the session establishment process.
  • the initial registration process of the UE is omitted.
  • S501 The UE sends a PDU session establishment request message to the AMF through the RAN.
  • the message carries the identity of the UE, the data network name (data network name, DNN) and the location information of the UE.
  • the AMF selects V-SMF for the UE.
  • S503 AMF sends a PDU session management context establishment request message to V-SMF.
  • the message includes the identification of the V-PCF, such as the V-PCFInstanceID or the fully qualified domain name of the V-PCF.
  • the message also includes the UE's identity, DNN and UE's location information.
  • V-SMF and V-UPF interact to execute the N4 session establishment process.
  • V-SMF sends a session management policy establishment message to V-PCF.
  • the V-SMF determines the IP address of the V-PCF based on the identification of the V-PCF obtained in S502, and sends a session management policy establishment message to the V-PCF.
  • the session management policy establishment message is used to request the offloading information of the UE.
  • the message includes the identity of the UE.
  • V-SMF can determine that the identifier of V-PCF corresponds to the IP address of V-PCF according to local configuration, or V-SMF sends the identifier of V-PCF to NRF, and NRF sends the IP address of V-PCF to V-SMF.
  • the V-PCF sends a session management policy establishment response message to the V-SMF.
  • the message carries the offloading information of the UE.
  • the offloading information of the UE may be obtained by the V-PCF from the H-PCF, or allocated by the V-PCF to the UE.
  • V-SMF determines that the UE has signed up for offloading information. According to the DNN, the location information of the UE is determined to select UL CL UPF and PSA UPF for the UE.
  • the V-SMF determines whether to offload the service data flow of the UE according to whether the session management policy establishment response message received in S506 carries the offloading information of the UE. If the session management policy received in S506 is established If the response message does not carry the offloading information of the UE, there is no need to perform S507 and the following steps.
  • V-SMF needs to determine based on the local configuration that the UL CL offload function has been enabled for the DNN, and determine that the UE is in a specific area based on the location information of the UE and the applicable area range of the locally configured UL CL UPF. V-SMF can select UL CL UPF creates an offload session for the UE.
  • V-V-SMF does not need to create an offload session for the UE.
  • V-SMF sends an N4 Session Establishment Request (N4Session Establishment Request) message to ULCL UPF.
  • N4Session Establishment Request N4 Session Establishment Request
  • the N4 session establishment request carries the application identifier in the offload information, and ULCL UPF can obtain the corresponding data forwarding policy based on the application identifier.
  • V-SMF sends an N4 session establishment request message to PSA UPF.
  • the N4 session establishment request carries the application identifier in the offload information.
  • S509A ULCL UPF receives the N4 session establishment request message and sends the N4 Session Establishment Response (N4Session Establishment Response) message to V-SMF.
  • N4Session Establishment Response N4 Session Establishment Response
  • the N4 session establishment response message carries the uplink forwarding address of the N3 interface of UL CL UPF and the downlink forwarding address of the N9 interface of UL CL UPF.
  • the N3 interface uplink forwarding address of UL CL UPF is used when the UE sends uplink data.
  • the RAN forwards the uplink data received from the UE to this address.
  • UL CL UPF sends the address to V-SMF, and V-SMF forwards it to RAN via AMF.
  • RAN sends the N3 interface downlink forwarding address to V-SMF through AMF, and V-SMF notifies UL CL UPF of the N3 interface downlink forwarding address.
  • UL CL UPF forwards the received downlink data to this address.
  • V-UPF or PSAUPF forwards the downlink data sent to the UE to this address.
  • S509B PSA UPF receives the N4 session establishment request message and sends the N4 session establishment response message to V-SMF.
  • the N4 session establishment response message carries the N9 interface uplink forwarding address of PSAUPF.
  • the N9 interface uplink forwarding address of PSA UPF2 used by ULCL UPF to forward the uplink data received from the UE to this address.
  • V-SMF sends an N4 Session Modification Request (N4Session Modification Request) message to V-UPF.
  • N4Session Modification Request N4Session Modification Request
  • the N4 session modification request message includes the ULCL UPF N9 interface downlink forwarding address.
  • V-UPF updates the downlink data forwarding tunnel information.
  • V-UPF updates the downlink data forwarding tunnel information to the ULCL UPF N9 interface downlink forwarding address.
  • V-UPF sends an N4 Session Modification Response (N4Session Modification Response) message to V-SMF.
  • N4Session Modification Response N4Session Modification Response
  • the N4 session modification response message includes the N9 interface uplink data forwarding address of the V-UPF.
  • V-UPF's N9 interface uplink data forwarding address used by ULCL UPF to forward the uplink data received from the UE to this address.
  • V-SMF sends a packet forwarding control protocol session modification request (packet forwarding control protocol Session Modification Request) message.
  • the PFCP session modification request message includes the N9 interface upstream data forwarding address of V-UPF and the N9 interface upstream forwarding address of PSA UPF.
  • ULCL UPF updates the upstream data forwarding tunnel information to the N9 interface upstream data forwarding address of V-UPF and the N9 interface upstream forwarding address of PSA UPF.
  • S515A ULCL UPF sends a PFCP session modification response message to V-SMF.
  • V-SMF sends a PFCP session modification request message to PSA UPF.
  • the PFCP session modification request message includes the ULCL UPF N9 interface downlink forwarding address.
  • S514B PSA UPF updates the downlink data forwarding tunnel information.
  • PSA UPF updates the downlink data forwarding tunnel information to the ULCL UPF N9 interface downlink forwarding address.
  • S515B PSA UPF sends a PFCP session modification response message to V-SMF.
  • V-SMF sends a PDU session management context establishment response message to AMF.
  • the AMF sends a PDU session establishment response message to the UE through the RAN.
  • V-SMF determines that the UE has signed up for the offloading information, and can determine whether to create a ULCL session for the UE, so that roaming users can access the local data network.
  • Figure 6 shows the flow chart of creating a ULCL session in the location update process.
  • the UE's initial registration process and the UE's PDU session establishment process are omitted.
  • S601 The UE sends a mobility registration request message to the AMF through the RAN.
  • the message carries the UE's identity, DNN and UE's location information.
  • S602 AMF sends a PDU session management context update request message to V-SMF.
  • the message includes the identification of the V-PCF, such as the V-PCFInstanceID or the fully qualified domain name of the V-PCF.
  • the message also includes the UE's identity, DNN and UE's location information.
  • V-SMF and V-UPF interact to execute the N4 session modification process.
  • S604 to S614B may refer to the above-mentioned S505 to S515B, and will not be described again here.
  • V-SMF sends a PDU session management context update response message to AMF.
  • the AMF sends a mobility registration response message to the UE through the RAN.
  • the V-SMF determines that the UE has signed up for offloading information, and can determine whether to create a ULCL session for the UE, so that roaming users can access the local data network.
  • Figure 7 shows the flow chart of creating a ULCL session in the service request process.
  • the UE's initial registration process and the UE's PDU session establishment process are omitted.
  • S701 The UE sends a service request message to the AMF through the RAN.
  • the message carries the UE's identity, DNN and UE's location information.
  • S702 AMF sends a PDU session management context update request message to V-SMF.
  • the message includes the identification of the V-PCF, such as the V-PCFInstanceID or the fully qualified domain name of the V-PCF.
  • the message also includes the UE's identity, DNN and UE's location information.
  • V-SMF and V-UPF interact to execute the N4 session modification process.
  • S704 to S714B may refer to the above-mentioned S505 to S515B, and will not be described again here.
  • V-SMF sends a PDU session management context update response message to AMF.
  • the AMF sends a service acceptance message to the UE through the RAN.
  • V-SMF determines that the UE has signed up for offloading information, and can determine whether to create a ULCL session for the UE, so that roaming users can access the local data network.
  • Figure 8 shows the flow chart of creating a ULCL session after the session is established. Here, the initial registration process of the UE is omitted.
  • S801 The UE sends a PDU session establishment request message to the AMF through the RAN.
  • the message carries the UE's identity, DNN and UE's location information.
  • S802 The AMF selects V-SMF for the UE.
  • S803 AMF sends a PDU session management context establishment request message to V-SMF.
  • the message includes the UE's identity, DNN and UE's location information.
  • V-SMF and V-UPF interact to execute the N4 session establishment process.
  • V-SMF sends a PDU session management context establishment response message to AMF.
  • the AMF sends a PDU session establishment response message to the UE through the RAN.
  • S807 The AMF sends an access management policy control update request message to the V-PCF.
  • the AMF may send an access management policy control update request message to the V-PCF based on the local configuration after the session establishment is completed.
  • the access management policy control update request message includes the identity of the UE, the identity of the PDU session, and the identity of the V-SMF.
  • the identity of the V-SMF may be the Instance ID of the V-SMF or the FQDN of the V-SMF, etc.
  • the V-PCF sends the offload information of the UE to the V-SMF.
  • V-SMF For example, if the identifier of V-SMF is the Instance ID of V-SMF, V-PCF sends the Instance ID of V-SMF to NRF, and NRF sends the IP address of V-SMF to V-PCF.
  • V-PCF sends the FQDN of V-SMF to DNS, and DNS sends the IP address of V-SMF to V-PCF.
  • V-PCF sends an access management policy control update response message to the AMF.
  • S810 to S818B can refer to the above-mentioned S507 to S515B.
  • the V-PCF obtains the identification of the V-SMF and sends the offload information to the V-SMF.
  • the V-SMF determines that the UE has signed up for the offload information and can determine whether to create a ULCL session for the UE, thus achieving Roaming users access local data networks.
  • Figure 9 shows a flow chart of creating a ULCL session after the location update process.
  • the UE's initial registration process and the UE's PDU session establishment process are omitted.
  • S901 The UE sends a mobility registration request message to the AMF through the RAN.
  • the message carries the UE's identity, DNN and UE's location information.
  • S902 AMF sends a PDU session management context update request message to V-SMF.
  • the message includes the identification of the V-PCF, such as the V-PCFInstanceID or the fully qualified domain name of the V-PCF.
  • the message also includes the UE's identity, DNN and UE's location information.
  • V-SMF and V-UPF interact to execute the N4 session modification process.
  • V-SMF sends a PDU session management context update response message to AMF.
  • the AMF sends a mobility registration response message to the UE through the RAN.
  • S906 The AMF sends an access management policy control update request message to the V-PCF.
  • the AMF may send an access management policy control update request message to the V-PCF after the location update process based on the local configuration.
  • the access management policy control update request message includes the identity of the UE, the identity of the PDU session, and the identity of the V-SMF.
  • the identity of the V-SMF may be the Instance ID of the V-SMF or the FQDN of the V-SMF, etc.
  • S907 to S917B can refer to the above-mentioned S808 to S818B.
  • the V-PCF obtains the identification of the V-SMF and sends the offload information to the V-SMF.
  • the V-SMF determines that the UE has signed up for the offload information and can determine whether to create a ULCL session for the UE, so that it can Enable roaming users to access local data networks.
  • Figure 10 shows the flow chart of creating a ULCL session after the service request process.
  • the UE's initial registration process and the UE's PDU session establishment process are omitted.
  • S1001 The UE sends a service request message to the AMF through the RAN.
  • the message carries the UE's identity, DNN and UE's location information.
  • S1002 AMF sends a PDU session management context update request message to V-SMF.
  • the message includes the identification of the V-PCF, such as the V-PCFInstanceID or the fully qualified domain name of the V-PCF.
  • the message also includes the UE's identity, DNN and UE's location information.
  • V-SMF and V-UPF interact to execute the N4 session modification process.
  • V-SMF sends a PDU session management context update response message to AMF.
  • the AMF sends a service acceptance message to the UE through the RAN.
  • S1006 The AMF sends an access management policy control update request message to the V-PCF.
  • the AMF may send an access management policy control update request message to the V-PCF after the service request process based on the local configuration.
  • the access management policy control update request message includes the identity of the UE, the identity of the PDU session, and the identity of the V-SMF.
  • the identity of the V-SMF may be the Instance ID of the V-SMF or the FQDN of the V-SMF, etc.
  • S1007 to S1017B can refer to the above-mentioned S807 to S818B.
  • the V-PCF obtains the identification of the V-SMF and sends the offload information to the V-SMF.
  • the V-SMF determines that the UE has signed up for the offload information and can determine whether to create a ULCL session for the UE, so that it can Enable roaming users to access local data networks.
  • the access and mobility management network element can also obtain the terminal device Then the access and mobility management network element sends the IP address of the terminal device to the visiting policy control network element.
  • the visited policy control network element sends a registration message to the visited bootstrapping service (BFS) network element.
  • the registration message includes the identifier of the instance of the visited policy control network element and the IP address of the terminal device.
  • the capability exposure function network element can determine the visited policy control network element corresponding to the terminal device.
  • the guidance service network element sends a message, which message includes the IP address of the terminal device.
  • the guidance service network element determines the identity of the instance of the visited policy control network element corresponding to the IP address of the terminal device according to the IP address of the terminal device, that is, the identifier of the instance of the visited location policy control network element, which is the same as the terminal device.
  • the identification of the instance of the visited policy control network element registered together with the IP address guides the service network element to send the identifier of the instance of the visited policy control network element to the capability opening function network element, and then the capability opening function network element can determine the corresponding terminal device.
  • the visited location policy controls network elements.
  • V-SMF sends a request message to H-SMF.
  • the request message is used to request the IP address of the UE.
  • H-SMF sends a response message to V-SMF, where the response message includes the IP address of the UE.
  • V-SMF sends a PDU session context update request message to AMF.
  • the PDU session context update response message includes the UE's IP address.
  • the AMF can send a PDU session context establishment request message to the H-SMF through the V-SMF, which is used to request the establishment of a session context for the UE.
  • H-SMF sends a PDU session context establishment response message to V-SMF
  • V-SMF sends a PDU session context establishment response message to AMF.
  • the PDU session context establishment response message is used to notify AMF that the session context establishment is successful, where the PDU session context establishment response message
  • the message includes the UE's IP address.
  • AMF or V-SMF can also parse the PDU session context establishment response message to obtain the UE's IP address.
  • S1104 The AMF sends an access management policy control update request message to the V-PCF.
  • the access management policy control update request message includes the IP address of the UE.
  • V-PCF sends a registration message to BSF.
  • the registration message includes the identification of the V-PCF and the IP address of the UE.
  • the V-PCF sends an access management policy control update response message to the AMF.
  • FIG. 12 shows a possible exemplary block diagram of a communication device involved in the embodiment of the present application.
  • the device 1200 includes: a transceiver module 1220 and a processing module 1210.
  • the transceiver module 1220 may include a receiving unit and a sending unit.
  • the processing module 1210 is used to control and manage the actions of the device 1200 .
  • the transceiver module 1220 is used to support communication between the device 1200 and other network entities.
  • the device 1200 may further include a storage unit used to store program codes and data of the device 1200 .
  • each module in the device 1200 may be implemented by software.
  • the processing module 1210 may be a processor or a controller, such as a general-purpose central processing unit (CPU), a general-purpose processor, a digital signal processing (DSP), or an application-specific integrated circuit. specific integrated circuits (ASIC), field programmable gate array (FPGA) or other programmable logic devices, transistor logic devices, hardware components or any combination thereof. It may implement or execute various exemplary logical blocks, modules and circuits described in conjunction with the disclosure of the embodiments of this application.
  • the processor may also be a combination that implements computing functions, such as one or more microprocessors. Processor combinations, DSP and microprocessor combinations, etc.
  • the transceiver module 1220 may be a communication interface, a transceiver, or a transceiver circuit, etc., where the communication interface is a general term.
  • the communication interface may include multiple interfaces, and the storage unit may be a memory.
  • the processing module 1210 in the device 1200 can support the device 1200 to perform the access and mobility management in each of the above method examples.
  • the action of the network element may, for example, support the device 1200 to perform step 302 in FIG. 3 .
  • the transceiver module 1220 can support the device 1200 to communicate with the session management network element.
  • the transceiver module 1220 can support the device 1200 to perform steps 301 and 303 in Figure 3 .
  • the transceiver module 1220 is used to receive a first message from a terminal device, the first message is used to request the establishment of a first session for the terminal device, and the terminal device is a roaming user; the processing module 1210 is used to Select a visited session management network element for the terminal device; the transceiving module 1220 is configured to send a second message to the visited session management network element, where the second message is used to request the establishment of the third message for the terminal device.
  • a session, the second message includes the identification of the visited policy control network element.
  • the processing module 1210 is configured to obtain the identity of the visited policy control network element during the registration process of the terminal device.
  • the identifier of the visited policy control network element includes an identifier of an instance of the visited policy control network element, or a fully qualified domain name of the visited policy control network element.
  • the device 1200 may correspond to the access and mobility management network elements in the foregoing method embodiments, and the operations and/or functions of each module in the device 1200 are respectively to implement the access in the foregoing method embodiments. Therefore, the beneficial effects in the foregoing method embodiments can also be achieved. For the sake of brevity, they will not be described again here.
  • the processing module 1210 in the device 1200 can support the device 1200 to perform the actions of the visited session management network element in the above method examples.
  • the transceiver module 1220 can support the device 1200 to communicate with the network device.
  • the transceiver module 1220 can support the device 1200 to perform steps 303 and 304 in Figure 3 .
  • the processing module 1210 calls the transceiver module 1220 to receive a second message from the access and mobility management network element.
  • the second message is used to request the establishment of a first session for the terminal device.
  • the second message includes The identifier of the visited policy control network element, and the terminal device is a roaming user; sending a third message to the visited policy control network element according to the identifier of the visited policy control network element, where the third message is used to request
  • the offload information of the terminal device receives the offload information from the visited policy control network element.
  • the processing module 1210 is configured to: when sending a third message to the visited policy control network element according to the identity of the visited policy control network element, control the network element according to the visited policy The identifier obtains the IP address of the visited policy control network element; the transceiving module 1220 is configured to send the third message to the visited policy control network element according to the IP address of the visited policy control network element.
  • the identifier of the visited location policy control network element includes an identifier of an instance of the visited location policy control network element; and the visited location policy is obtained according to the identifier of the visited location policy control network element.
  • the transceiver module 1220 is configured to send the identification of the instance of the visited location policy control network element to the network warehousing function network element, and receive the visited location policy from the network warehousing function network element. Control the IP address of the network element.
  • the fully qualified domain name of the visited policy control network element is configured to obtain the IP of the visited policy control network element according to the identity of the visited policy control network element. address, to the domain name
  • the system sends the fully qualified domain name of the visited policy control network element and receives the IP address of the visited policy control network element from the domain name system.
  • the device 1200 may correspond to the visited session management network element in the foregoing method embodiment, and the operations and/or functions of each module in the device 1200 are respectively to implement the visited session in the foregoing method embodiment.
  • the corresponding steps of the method for managing network elements can also achieve the beneficial effects in the foregoing method embodiments. For the sake of simplicity, they will not be described again here.
  • the processing module 1210 in the device 1200 can support the device 1200 to perform the actions of the visited policy control network element in the above method examples.
  • the transceiver module 1220 can support the device 1200 to communicate with the network device.
  • the transceiver module 1220 can support the device 1200 to perform steps 304 and 305 in Figure 3 .
  • the processing module 1210 calls the transceiver module 1220 to receive a third message from the visited session management network element.
  • the third message is used to request the offload information of the terminal device.
  • the terminal device is a roaming user.
  • the visited session management network element sends the offload information.
  • the transceiver module 1220 is configured to send a request message to the home policy control network element, the request message is used to request the offload information, and receive the offload from the home policy control network element. information.
  • the device 1200 may correspond to the visited location policy control network element in the foregoing method embodiment, and the operations and/or functions of each module in the device 1200 are respectively to implement the visited location policy in the foregoing method embodiment.
  • the corresponding steps of the method of controlling network elements can also achieve the beneficial effects in the foregoing method embodiments. For the sake of simplicity, they will not be described again here.
  • the processing module 1210 in the device 1200 can support the device 1200 to perform the access and mobility management in each of the above method examples.
  • the action of the network element may, for example, support the device 1200 to perform step 402 in FIG. 4 .
  • the transceiver module 1220 can support the device 1200 to communicate with the session management network element.
  • the transceiver module 1220 can support the device 1200 to perform steps 401 and 403 in Figure 4 .
  • the transceiver module 1220 is configured to receive a first message from a terminal device, where the first message is used to request the establishment of a first session for the terminal device, and the terminal device is a roaming user; the processing unit is configured to To select the visited session management network element for the terminal device; the processing module 1210 is configured to send the identifier of the visited session management network element and the identifier of the terminal device to the visited policy control network element.
  • the processing module 1210 is configured to obtain the IP address of the terminal device; the transceiving module 1220 is configured to send the IP address of the terminal device to the visited policy control network element.
  • the device 1200 may correspond to the access and mobility management network elements in the foregoing method embodiments, and the operations and/or functions of each module in the device 1200 are respectively to implement the access in the foregoing method embodiments. Therefore, the beneficial effects in the foregoing method embodiments can also be achieved. For the sake of brevity, they will not be described again here.
  • the processing module 1210 in the device 1200 can support the device 1200 to perform the actions of the visited policy control network element in the above method examples.
  • the transceiver module 1220 can support the device 1200 to communicate with the network device.
  • the transceiver module 1220 can support the device 1200 to perform steps 403 and 404 in Figure 4 .
  • the processing module 1210 calls the transceiver module 1220 to receive the identity of the visited session management network element and the identity of the terminal device from the access and mobility management network element.
  • the terminal device is a roaming user.
  • the identifier of the device and the identifier of the visited session management network element send the offload information of the terminal device to the visited session management network element.
  • the processing module 1210 is configured to send the offload information of the terminal device to the visited session management network element according to the identifier of the terminal device and the identifier of the visited session management network element.
  • the address sends the offload information of the terminal device to the visited session management network element.
  • the identifier of the visited session management network element is an identifier of an instance of the visited session management network element; the transceiver module 1220 is configured to send a message according to the identifier of the visited session management network element.
  • the transceiver module 1220 is configured to send a message according to the identifier of the visited session management network element.
  • the identifier of the visited session management network element is the fully qualified domain name of the visited session management network element; the transceiver module 1220 is configured to send a message according to the identifier of the visited session management network element.
  • the fully qualified domain name of the visited session management network element is sent to the domain name system, and the visited policy control network element receives the visited session from the domain name system. IP address of the management network element.
  • the device 1200 may correspond to the visited location policy control network element in the foregoing method embodiment, and the operations and/or functions of each module in the device 1200 are respectively to implement the visited location policy in the foregoing method embodiment.
  • the corresponding steps of the method of controlling network elements can also achieve the beneficial effects in the foregoing method embodiments. For the sake of simplicity, they will not be described again here.
  • Figure 13 shows a schematic structural diagram of a communication device 1300 according to an embodiment of the present application.
  • the device 1300 includes: a processor 1301.
  • the processor 1301 when the device 1300 is an access and mobility management network element or a chip in an access and mobility management network element, in a possible implementation, when the processor 1301 is used to call an interface to perform the following actions: receive from A first message to a terminal device, the first message is used to request the establishment of a first session for the terminal device, and the terminal device is a roaming user; to select a visited session management network element for the terminal device; to the The visited session management network element sends a second message, the second message is used to request the establishment of the first session for the terminal device, and the second message includes the identification of the visited policy control network element.
  • the device 1300 can also be used to perform other steps and/or operations on the access and mobility management network element side in the previous embodiments, which will not be described again here for the sake of brevity.
  • the processor 1301 when the device 1300 is a visited session management network element or a chip in a visited session management network element, in a possible implementation, when the processor 1301 is used to call an interface to perform the following actions: receive from the access and A second message from the mobility management network element, the second message is used to request the establishment of a first session for a terminal device, the second message includes the identification of the visited policy control network element, and the terminal device is a roaming user; according to The identifier of the visited policy control network element sends a third message to the visited policy control network element. The third message is used to request the offload information of the terminal device and receives the information from the visited policy control network. The shunt information of the element.
  • the device 1300 can also be used to perform other steps and/or operations on the visited session management network element side in the previous embodiments. For the sake of brevity, they will not be described again here.
  • the processor 1301 when the device 1300 is a visited policy control network element or a chip in a visited policy control network element, in a possible implementation, when the processor 1301 is used to call an interface to perform the following actions: receive a session from the visited location The third message of the management network element, the third message is used to request the offload information of the terminal device, and the terminal device is used for roaming. The user sends the offload information to the visited session management network element.
  • the device 1300 can also be used to perform other steps and/or operations on the visited policy control network element side in the previous embodiments. For the sake of brevity, they will not be described again here.
  • the processor 1301 when the device 1300 is an access and mobility management network element or a chip in an access and mobility management network element, in a possible implementation, when the processor 1301 is used to call an interface to perform the following actions: receive from A first message to a terminal device, the first message is used to request the establishment of a first session for the terminal device, and the terminal device is a roaming user; the processing unit is used to select a visited session for the terminal device Management network element; sending the identifier of the visited session management network element and the identifier of the terminal device to the visited policy control network element.
  • the device 1300 can also be used to perform other steps and/or operations on the access and mobility management network element side in the previous embodiments, which will not be described again here for the sake of brevity.
  • the device 1300 is a visited policy control network element or a chip in a visited policy control network element
  • the processor 1301 when the processor 1301 is used to call an interface to perform the following actions: receive from the access and The identity of the visited session management network element and the identity of the terminal device of the mobility management network element.
  • the terminal device is a roaming user.
  • the visited session management network element According to the identity of the terminal device and the identity of the visited session management network element, the visited session management network element The local session management network element sends the offload information of the terminal device.
  • the device 1300 can also be used to perform other steps and/or operations on the visited policy control network element side in the previous embodiments. For the sake of brevity, they will not be described again here.
  • the processor 1301 can call an interface to perform the above transceiver action, where the called interface can be a logical interface or a physical interface, which is not limited.
  • the physical interface can be implemented via transceivers.
  • the device 1300 further includes a transceiver 1303.
  • the device 1300 also includes a memory 1302, in which the program code in the above method embodiment can be stored, so that the processor 1301 can call it.
  • the device 1300 includes a processor 1301, a memory 1302, and a transceiver 1303, the processor 1301, the memory 1302, and the transceiver 1303 communicate with each other through internal connection paths to transmit control and/or data signals.
  • the processor 1301, the memory 1302 and the transceiver 1303 can be implemented on a chip.
  • the processor 1301, the memory 1302 and the transceiver 1303 can be implemented in the same chip, or they can be implemented in different chips. Or any two functions can be combined in one chip.
  • the memory 1302 can store program codes, and the processor 1301 calls the program codes stored in the memory 1302 to implement corresponding functions of the device 1300 .
  • the methods disclosed in the above embodiments of the present application can be applied in a processor or implemented by the processor.
  • the processor may be an integrated circuit chip that has signal processing capabilities. During the implementation process, each step of the above method embodiment can be completed through an integrated logic circuit of hardware in the processor or instructions in the form of software.
  • the above-mentioned processor may be a general-purpose processor, a digital signal processor (DSP), an application specific integrated circuit (ASIC), an off-the-shelf programmable gate array (field programmable gate array, FPGA), or other available processors.
  • Programmable logic devices discrete gate or transistor logic devices, discrete hardware components, system on chip (SoC), central processor unit (CPU), or network processor (network processor) processor (NP), it can also be a digital signal processor (DSP), it can also be a microcontroller (micro controller unit, MCU), it can also be a programmable logic device (PLD) or other Integrated chip.
  • SoC system on chip
  • CPU central processor unit
  • NP network processor
  • DSP digital signal processor
  • MCU microcontroller
  • PLD programmable logic device
  • a general-purpose processor may be a microprocessor or the processor may be any conventional processor, etc.
  • the steps of the method disclosed in conjunction with the embodiments of this application can be directly embodied as hardware decoding processing.
  • the execution is completed by the processor, or the execution is completed by a combination of hardware and software modules in the decoding processor.
  • the software module can be located in random access memory, flash memory, read-only memory, programmable read-only memory or electrically erasable programmable memory, registers and other mature storage media in this field.
  • the storage medium is located in the memory, and the processor reads the information in the memory and completes the steps of the above method in combination with its hardware.
  • 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), which is used as an external cache.
  • RAM random access memory
  • RAM static random access memory
  • DRAM dynamic random access memory
  • SDRAM synchronous dynamic random access memory
  • double data rate SDRAM double data rate SDRAM
  • DDR SDRAM double data rate SDRAM
  • ESDRAM enhanced synchronous dynamic random access memory
  • SLDRAM synchronous link dynamic random access memory
  • direct rambus RAM direct rambus RAM
  • the size of the sequence numbers of the above-mentioned processes does not mean the order of execution.
  • the execution order of each process should be determined by its functions and internal logic.
  • the various numerical numbers or serial numbers involved in the above processes are only for convenience of description and should not constitute any limitation on the implementation process of the embodiments of the present application.
  • the above is an example of three elements A, B and C to illustrate the optional items of the project.
  • the disclosed systems, 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 units described as separate components may or may not be physically separated, and the components shown as units may or may not be physical units, that is, they may be located in one place, or they may be distributed to multiple network units. Some or all of the units can be selected according to actual needs to achieve the purpose of the solution of this embodiment.
  • each functional unit in each embodiment of the present application can be integrated into one processing unit, each unit can exist physically alone, or two or more units can be integrated into one unit.
  • the functions are implemented in the form of software functional units and sold or used as independent products, they can be stored in a computer-readable storage medium.
  • the technical solution of the present application is essentially or the part that contributes to the existing technology or the part of the technical solution can be embodied in the form of a software product.
  • the computer software product is stored in a storage medium, including Several instructions are used to cause a computer device (which may be a personal computer, a server, or a network device, etc.) to execute all or part of the steps of the methods described in various embodiments of this application.
  • the aforementioned storage media include: U disk, mobile hard disk, read-only memory ROM, random access memory RAM, magnetic disk or optical disk and other various media that can store program codes.

Abstract

一种通信方法及装置，该方法包括：接入和移动性管理网元接收来自于终端设备的第一消息，第一消息用于请求为终端设备建立第一会话，终端设备为漫游用户，接入和移动性管理网元为终端设备选择拜访地会话管理网元，接入和移动性管理网元向拜访地会话管理网元发送第二消息，第二消息用于请求为终端设备建立第一会话，第二消息包括拜访地策略控制网元的标识。采用上述设计，拜访地会话管理网元可以获得拜访地策略控制网元的标识，进而可以从拜访地策略控制网元获取终端设备的分流信息，以实现漫游用户在拜访地使用ULCL功能访问本地业务。

Description

一种通信方法及装置
相关申请的交叉引用
本申请要求在2022年3月29日提交中华人民共和国知识产权局、申请号为202210326193.4、发明名称为“一种通信方法及装置”的中国专利申请的优先权，其全部内容通过引用结合在本申请中。
技术领域
本申请实施例涉及无线通信领域，尤其涉及一种通信方法及装置。
背景技术
三代合作伙伴计划(3rd generation partnership project，3GPP)针对于第五代移动通信技术(5th Generation Mobile Communication Technology，5G)用户面的数据分流定义了上行分类器(uplink classifier，UL CL)功能，通过上行分类器用户面网元(uplink classifier user plane function，UL CL UPF)可以实现根据用户业务数据的特征将访问本地网络的数据分流到本地数据网络(data network，DN)，将访问因特网(Internet)的数据分流到公网，从而实现对用户业务数据的分流控制。
示例性地，当终端设备的会话激活或位置发生变化时，会话管理网元判断是否需要将终端设备的数据分流到本地DN，如需分流则为终端设备选择UL CL UPF和辅锚点UPF，将UL CL UPF和辅锚点UPF插入当前的会话中，并对UL CL UPF下发相应的分流规则来实现对终端设备的数据的分流控制。其中，在会话管理网元判断是否需要将终端设备的数据分流到本地DN时，会话管理网元需要从策略控制网元获取终端设备的分流信息。
但是，在漫游场景下，由于协议没有定义拜访地会话管理网元和拜访地策略控制网元的接口以及相应的交互流程，所以，当前漫游用户无法在拜访地使用ULCL功能访问本地业务。
发明内容
本申请提供一种通信方法及装置，用以解决当前漫游用户无法在拜访地使用ULCL功能访问本地业务的问题。
第一方面，本申请提供一种通信方法，该方法包括：接入和移动性管理网元接收来自于终端设备的第一消息，所述第一消息用于请求为所述终端设备建立第一会话，所述终端设备为漫游用户。所述接入和移动性管理网元为所述终端设备选择拜访地会话管理网元，向所述拜访地会话管理网元发送第二消息，所述第二消息用于请求为所述终端设备建立所述第一会话，所述第二消息包括拜访地策略控制网元的标识。
采用上述设计，接入和移动性管理网元可以向拜访地会话管理网元提供拜访地策略控制网元的标识，进而可以实现拜访地会话管理网元从拜访地策略控制网元获取终端设备的分流信息，以实现漫游用户在拜访地使用ULCL功能访问本地业务。
在一种可能的设计中，还包括：所述接入和移动性管理网元在所述终端设备的注册过 程中获取所述拜访地策略控制网元的标识。
示例性地，在注册流程，接入和移动性管理网元向网络仓储功能网元发送终端设备的标识，用以查询PCF的信息，网络仓储功能网元向接入和移动性管理网元发送拜访地策略控制网元的标识。
在一种可能的设计中，所述拜访地策略控制网元的标识包括所述拜访地策略控制网元的实例的标识，或者所述拜访地策略控制网元的全限定域名。
第二方面，本申请提供一种通信方法，该方法包括：拜访地会话管理网元接收来自于接入和移动性管理网元的第二消息，所述第二消息用于请求为终端设备建立第一会话，所述第二消息包括拜访地策略控制网元的标识，所述终端设备为漫游用户。所述拜访地会话管理网元根据所述拜访地策略控制网元的标识向所述拜访地策略控制网元发送第三消息，所述第三消息用于请求所述终端设备的分流信息；所述拜访地会话管理网元接收来自于所述拜访地策略控制网元的所述分流信息。
采用上述实施例，拜访地会话管理网元获得拜访地策略控制网元的标识，从拜访地策略控制网元获得分流信息，进而实现为漫游用户创建ULCL会话，从而可以保证漫游用户使用ULCL功能访问本地数据网络。
在一种可能的设计中，在所述拜访地会话管理网元根据所述拜访地策略控制网元的标识向所述拜访地策略控制网元发送第三消息时，所述拜访地会话管理网元根据所述拜访地策略控制网元的标识获取所述拜访地策略控制网元的IP地址，所述拜访地会话管理网元根据所述拜访地策略控制网元的IP地址向所述拜访地策略控制网元发送所述第三消息。
在一种可能的设计中，所述拜访地策略控制网元的标识包括所述拜访地策略控制网元的实例的标识；在所述拜访地会话管理网元根据所述拜访地策略控制网元的标识获取所述拜访地策略控制网元的IP地址时，所述拜访地会话管理网元向网络仓储功能网元发送所述拜访地策略控制网元的实例的标识，所述拜访地会话管理网元接收来自于所述网络仓储功能网元的所述拜访地策略控制网元的IP地址。
在一种可能的设计中，所述拜访地策略控制网元的全限定域名；在所述拜访地会话管理网元根据所述拜访地策略控制网元的标识获取所述拜访地策略控制网元的IP地址时，所述拜访地会话管理网元向域名系统发送所述拜访地策略控制网元的全限定域名，所述拜访地会话管理网元接收来自于所述域名系统的所述拜访地策略控制网元的IP地址。
采用上述设计，拜访地会话管理网元可以针对拜访地策略控制网元的标识的不同类型，采用不同方式获取拜访地策略控制网元的IP地址。
在一种可能的设计中，所述分流信息包括分流规则，应用标识，所述应用标识对应的数据探测规则，数据转发规则，带宽控制规则中的至少一项。
第三方面，本申请提供一种通信方法，该方法包括：拜访地策略控制网元接收来自于拜访地会话管理网元的第三消息，所述第三消息用于请求终端设备的分流信息，所述终端设备为漫游用户，所述拜访地策略控制网元向所述拜访地会话管理网元发送所述分流信息。
采用上述实施例，拜访地策略控制网元向拜访地会话管理网元发送分流信息，进而实现拜访地会话管理网元为漫游用户创建ULCL会话，从而可以保证漫游用户使用ULCL功能访问本地数据网络。
在一种可能的设计中，还包括：所述拜访地策略控制网元向归属地策略控制网元发送请求消息，所述请求消息用于请求所述分流信息，所述拜访地策略控制网元从所述归属地 策略控制网元接收所述分流信息。
采用上述设计，拜访地策略控制网元可以从归属地策略控制网元获得分流信息。
在一种可能的设计中，所述分流信息包括分流规则，应用标识，所述应用标识对应的数据探测规则，数据转发规则，带宽控制规则中的至少一项。
第四方面，本申请提供一种通信方法，该方法包括：接入和移动性管理网元接收来自于终端设备的第一消息，所述第一消息用于请求为所述终端设备建立第一会话，所述终端设备为漫游用户，所述接入和移动性管理网元为所述终端设备选择拜访地会话管理网元，所述接入和移动性管理网元向拜访地策略控制网元发送所述拜访地会话管理网元的标识和所述终端设备的标识。
采用上述设计，接入和移动性管理网元为拜访地策略控制网元提供拜访地会话管理网元的标识，进而可以实现拜访地策略控制网元向拜访地会话管理网元发送终端设备的分流信息，以实现漫游用户在拜访地使用ULCL功能访问本地业务。
在一种可能的设计中，所述拜访地会话管理网元的标识包括所述拜访地会话管理网元的实例的标识、或者所述拜访地会话管理网元的全限定域名。
在一种可能的设计中，还包括：所述接入和移动性管理网元获取所述终端设备的IP地址，所述接入和移动性管理网元向所述拜访地策略控制网元发送所述终端设备的IP地址。
第五方面，本申请提供一种通信方法，该方法包括：拜访地策略控制网元接收来自于接入和移动性管理网元的拜访地会话管理网元的标识和终端设备的标识，所述终端设备为漫游用户，所述拜访地策略控制网元根据所述终端设备的标识和所述拜访地会话管理网元的标识向所述拜访地会话管理网元发送所述终端设备的分流信息。
采用上述设计，拜访地策略控制网元可以获得拜访地会话管理网元的标识，进而可以向拜访地会话管理网元发送终端设备的分流信息，以实现漫游用户在拜访地使用ULCL功能访问本地业务。
在一种可能的设计中，在所述拜访地策略控制网元根据所述终端设备的标识和所述拜访地会话管理网元的标识向所述拜访地会话管理网元发送所述终端设备的分流信息时，所述拜访地策略控制网元根据所述拜访地会话管理网元的标识获取所述拜访地会话管理网元的IP地址，所述拜访地策略控制网元根据所述终端设备的标识和所述拜访地会话管理网元的IP地址向所述拜访地会话管理网元发送所述终端设备的分流信息。
在一种可能的设计中，所述拜访地会话管理网元的标识为所述拜访地会话管理网元的实例的标识；在所述拜访地策略控制网元根据所述拜访地会话管理网元的标识获取所述拜访地会话管理网元的IP地址时，所述拜访地策略控制网元向网络仓储功能网元发送所述拜访地会话管理网元的实例的标识，所述拜访地策略控制网元从所述网络仓储功能接收所述拜访地会话管理网元的IP地址。
在一种可能的设计中，所述拜访地会话管理网元的标识为所述拜访地会话管理网元的全限定域名；在所述拜访地策略控制网元根据所述拜访地会话管理网元的标识获取所述拜访地会话管理网元的IP地址时，所述拜访地策略控制网元向域名系统发送所述拜访地会话管理网元的全限定域名，所述拜访地策略控制网元从所述域名系统接收所述拜访地会话管理网元的IP地址。
采用上述设计，拜访地会话管理网元可以针对拜访地策略控制网元的标识的不同类型，采用不同方式获取拜访地策略控制网元的IP地址。
在一种可能的设计中，还包括：所述拜访地策略控制网元向归属地策略控制网元发送请求消息，所述请求消息用于请求所述分流信息，所述拜访地策略控制网元从所述归属地策略控制网元接收所述分流信息。
在一种可能的设计中，所述分流信息包括分流规则，应用标识，所述应用标识对应的数据探测规则，数据转发规则，带宽控制规则中的至少一项。
在一种可能的设计中，还包括：所述拜访地策略控制网元从所述接入和移动性管理网元接收所述终端设备的IP地址；所述拜访地策略控制网元向拜访地引导服务网元发送注册消息，所述注册消息包括所述拜访地策略控制网元的实例的标识和所述终端设备的IP地址。
采用上述设计，通过上述注册过程，当引导服务网元从能力开放功能网元接收终端设备的IP地址时，引导服务网元根据终端设备的IP地址确定与终端设备的IP地址对应的拜访地策略控制网元的实例的标识，以及向能力开放功能网元发送拜访地策略控制网元的实例的标识，进而能力开放功能网元可以确定终端设备对应的拜访地策略控制网元。
第六方面，本申请提供一种通信装置，该装置包括：收发单元和处理单元；所述收发单元，用于接收来自于终端设备的第一消息，所述第一消息用于请求为所述终端设备建立第一会话，所述终端设备为漫游用户；所述处理单元，用于为所述终端设备选择拜访地会话管理网元；所述收发单元，用于向所述拜访地会话管理网元发送第二消息，所述第二消息用于请求为所述终端设备建立所述第一会话，所述第二消息包括拜访地策略控制网元的标识。
在一种可能的设计中，所述处理单元，用于在所述终端设备的注册过程中获取所述拜访地策略控制网元的标识。
在一种可能的设计中，所述拜访地策略控制网元的标识包括所述拜访地策略控制网元的实例的标识，或者所述拜访地策略控制网元的全限定域名。
第七方面，本申请提供一种通信装置，该装置包括：收发单元和处理单元；所述处理单元调用所述收发单元，用于接收来自于接入和移动性管理网元的第二消息，所述第二消息用于请求为终端设备建立第一会话，所述第二消息包括拜访地策略控制网元的标识，所述终端设备为漫游用户；根据所述拜访地策略控制网元的标识向所述拜访地策略控制网元发送第三消息，所述第三消息用于请求所述终端设备的分流信息，接收来自于所述拜访地策略控制网元的所述分流信息。
在一种可能的设计中，所述处理单元，用于在根据所述拜访地策略控制网元的标识向所述拜访地策略控制网元发送第三消息时，根据所述拜访地策略控制网元的标识获取所述拜访地策略控制网元的IP地址；所述收发单元，用于根据所述拜访地策略控制网元的IP地址向所述拜访地策略控制网元发送所述第三消息。
在一种可能的设计中，所述拜访地策略控制网元的标识包括所述拜访地策略控制网元的实例的标识；在根据所述拜访地策略控制网元的标识获取所述拜访地策略控制网元的IP地址时，所述收发单元，用于向网络仓储功能网元发送所述拜访地策略控制网元的实例的标识，接收来自于所述网络仓储功能网元的所述拜访地策略控制网元的IP地址。
在一种可能的设计中，所述拜访地策略控制网元的全限定域名；所述收发单元，用于在根据所述拜访地策略控制网元的标识获取所述拜访地策略控制网元的IP地址时，向域名系统发送所述拜访地策略控制网元的全限定域名，接收来自于所述域名系统的所述拜访地策略控制网元的IP地址。
在一种可能的设计中，所述分流信息包括分流规则，应用标识，所述应用标识对应的数据探测规则，数据转发规则，带宽控制规则中的至少一项。
第八方面，本申请提供一种通信装置，该装置包括：收发单元和处理单元；所述处理单元调用所述收发单元，用于接收来自于拜访地会话管理网元的第三消息，所述第三消息用于请求终端设备的分流信息，所述终端设备为漫游用户，向所述拜访地会话管理网元发送所述分流信息。
在一种可能的设计中，所述收发单元，用于向归属地策略控制网元发送请求消息，所述请求消息用于请求所述分流信息，从所述归属地策略控制网元接收所述分流信息。
在一种可能的设计中，所述分流信息包括分流规则，应用标识，所述应用标识对应的数据探测规则，数据转发规则，带宽控制规则中的至少一项。
第九方面，本申请提供一种通信装置，该装置包括：收发单元和处理单元；所述收发单元，用于接收来自于终端设备的第一消息，所述第一消息用于请求为所述终端设备建立第一会话，所述终端设备为漫游用户；所述处理单元，用于为所述终端设备选择拜访地会话管理网元；所述收发单元，用于向拜访地策略控制网元发送所述拜访地会话管理网元的标识和所述终端设备的标识。
在一种可能的设计中，所述拜访地会话管理网元的标识包括所述拜访地会话管理网元的实例的标识、或者所述拜访地会话管理网元的全限定域名。
在一种可能的设计中，所述处理单元，用于获取所述终端设备的IP地址；所述收发单元，用于向所述拜访地策略控制网元发送所述终端设备的IP地址。
第十方面，本申请提供一种通信装置，该装置包括：收发单元和处理单元；所述处理单元调用所述收发单元，用于接收来自于接入和移动性管理网元的拜访地会话管理网元的标识和终端设备的标识，所述终端设备为漫游用户，根据所述终端设备的标识和所述拜访地会话管理网元的标识向所述拜访地会话管理网元发送所述终端设备的分流信息。
在一种可能的设计中，所述处理单元，用于在根据所述终端设备的标识和所述拜访地会话管理网元的标识向所述拜访地会话管理网元发送所述终端设备的分流信息时，根据所述拜访地会话管理网元的标识获取所述拜访地会话管理网元的IP地址；所述收发单元，用于根据所述终端设备的标识和所述拜访地会话管理网元的IP地址向所述拜访地会话管理网元发送所述终端设备的分流信息。
在一种可能的设计中，所述拜访地会话管理网元的标识为所述拜访地会话管理网元的实例的标识；所述收发单元，用于在根据所述拜访地会话管理网元的标识获取所述拜访地会话管理网元的IP地址时，向网络仓储功能网元发送所述拜访地会话管理网元的实例的标识，从所述网络仓储功能接收所述拜访地会话管理网元的IP地址。
在一种可能的设计中，所述拜访地会话管理网元的标识为所述拜访地会话管理网元的全限定域名；所述收发单元，用于在根据所述拜访地会话管理网元的标识获取所述拜访地会话管理网元的IP地址时，向域名系统发送所述拜访地会话管理网元的全限定域名，所述拜访地策略控制网元从所述域名系统接收所述拜访地会话管理网元的IP地址。
在一种可能的设计中，所述收发单元，用于向归属地策略控制网元发送请求消息，所述请求消息用于请求所述分流信息，从所述归属地策略控制网元接收所述分流信息。
在一种可能的设计中，所述分流信息包括分流规则，应用标识，所述应用标识对应的数据探测规则，数据转发规则，带宽控制规则中的至少一项。
在一种可能的设计中，所述收发单元，用于从所述接入和移动性管理网元接收所述终端设备的IP地址；向拜访地引导服务网元发送注册消息，所述注册消息包括所述拜访地策略控制网元的实例的标识和所述终端设备的IP地址。
第十一方面，本申请还提供一种装置。该装置可以执行上述方法设计。该装置可以是能够执行上述方法对应的功能的芯片或电路，或者是包括该芯片或电路的设备。
在一种可能的实现方式中，该装置包括：存储器，用于存储计算机可执行程序代码；以及处理器，处理器与存储器耦合。其中存储器所存储的程序代码包括指令，当处理器执行所述指令时，使该装置或者安装有该装置的设备执行上述任意一种可能的设计中的方法。
其中，该装置还可以包括通信接口，该通信接口可以是收发器，或者，如果该装置为芯片或电路，则通信接口可以是该芯片的输入/输出接口，例如输入/输出管脚等。
在一种可能的设计中，该装置包括相应的功能单元，分别用于实现以上方法中的步骤。功能可以通过硬件实现，也可以通过硬件执行相应的软件实现。硬件或软件包括一个或多个与上述功能相对应的单元。
第十二方面，本申请提供一种计算机可读存储介质，所述计算机可读存储介质存储有计算机程序，当所述计算机程序在装置上运行时，执行上述任意一种可能的设计中的方法。
第十三方面，本申请提供一种计算机程序产品，所述计算机程序产品包括计算机程序，当所述计算机程序在装置上运行时，执行上述任意一种可能的设计中的方法。
附图说明
图1为本申请应用的漫游场景的架构图；
图2为本申请应用的ULCL的网络架构示意图；
图3为本申请中一种通信方法的概述流程图；
图4为本申请中另一种通信方法的概述流程图；
图5为本申请中在会话建立流程中创建ULCL会话的流程图；
图6为本申请中在位置更新流程中创建ULCL会话的流程图；
图7为本申请中在服务请求流程中创建ULCL会话的流程图；
图8为本申请中在会话建立流程后创建ULCL会话的流程图；
图9为本申请中在位置更新流程后创建ULCL会话的流程图；
图10为本申请中在服务请求流程后创建ULCL会话的流程图；
图11为本申请中针对拜访地策略控制网元的实例的标识和终端设备的IP地址的注册流程图；
图12为本申请中一种通信装置的结构示意图之一；
图13为本申请中一种通信装置的结构示意图之二。
具体实施方式
下面将结合本申请实施例中的附图，对本申请实施例中的技术方案进行清楚、完整地描述。显然，所描述的实施例仅仅是本申请一部分实施例，而不是全部的实施例。本申请的说明书和权利要求书及上述附图中的术语“第一”、第二”以及相应术语标号等是用于区别类似的对象，而不必用于描述特定的顺序或先后次序。应该理解这样使用的术语在适当情 况下可以互换，这仅仅是描述本申请的实施例中对相同属性的对象在描述时所采用的区分方式。此外，术语“包括”和“具有”以及他们的任何变形，意图在于覆盖不排他的包含，以便包含一系列单元的过程、方法、系统、产品或设备不必限于那些单元，而是可包括没有清楚地列出的或对于这些过程、方法、产品或设备固有的其它单元。
在本申请的描述中，除非另有说明，“/”表示或的意思，例如，A/B可以表示A或B；本申请中的“和/或”仅仅是一种描述关联对象的关联关系，表示可以存在三种关系，例如，A和/或B，可以表示：单独存在A，同时存在A和B，单独存在B这三种情况。另外，在本申请的描述中，“至少一项”是指一项或者多项，“多项”是指两项或两项以上。“以下至少一项(个)”或其类似表达，是指的这些项中的任意组合，包括单项(个)或复数项(个)的任意组合。例如，a,b,或c中的至少一项(个)，可以表示：a,b,c,a-b,a-c,b-c,或a-b-c，其中a,b,c可以是单个，也可以是多个。
本申请实施例提供的技术方案可以应用于各种通信系统。例如：可以适用于LTE系统或5G系统，也可以适用于其它面向未来的新系统等。本申请实施例对此不作具体限定。此外，术语“系统”可以和“网络”相互替换。
为便于理解本申请实施例，对本申请实施例中涉及的几个基本概念做简单说明。
1.漫游
漫游是移动电话用户常用的一个术语，是指移动用户在离开自己注册登记的服务区域，移动到另一服务区后，移动通信系统仍可向其提供服务的功能。例如，这里的功能可以包括通过移动通信网络实现对漫游用户位置的自动跟踪、定位。
目前，漫游主要有两类：一是国内漫游，是指离开号码所属城市时与国内用户的电话拨打或接听；二是国际漫游，是指在国外也可以享受国内运营商提供的一系列服务，例如，通话、手机上网等。可以理解的是，漫游只能够在网络制式兼容且已经联网的国内城市间或已经签署双边漫游协议的地区或国家之间才能进行。
2.终端设备的漫游类型
终端设备的漫游类型为本地用户、漫游用户或拜访用户中的任意一种。
终端设备的用户身份识别模块(subscriber identity module，SIM)卡保存终端归属公共陆地移动网络(Home Public Land Mobile Network，HPLMN)，终端设备可以通过接入网设备将HPLMN上报给核心网设备。具体的，终端设备在进入连接态后，终端设备可以通过接入网设备向核心网设备发送HPLMN。
核心网设备可以根据终端设备上报的HPLMN和核心网设备存储的当前部署的PLMN判断终端设备的漫游类型。其中，当HPLMN与PLMN相同，核心网设备确定终端设备的漫游类型为本地用户。当HPLMN与PLMN不同，且核心网与HPLMN存在漫游协议，核心网设备确定终端设备的漫游类型为漫游用户。此时，核心网为终端设备提供漫游服务。当HPLMN与PLMN不同，且核心网与HPLMN不存在漫游协议，核心网设备确定终端设备的漫游类型为拜访用户。此时，终端设备获得的服务受限，例如，终端设备只能实现紧急呼叫。进一步地，当核心网设备确定终端设备的漫游类型为漫游用户或拜访用户时，核心网设备可以向终端设备发送终端设备的漫游类型。
此外，终端设备可以通过当前小区广播的系统消息块(system information block，SIB)消息获得PLMN，进而终端设备也可以自己确定漫游类型。同理，终端设备确定HPLMN和PLMN相同，则确定自身的漫游类型为本地用户。终端设备确定HPLMN和PLMN不 相同，则确定自身的漫游类型为漫游用户或拜访用户。
其中，HPLMN包括移动国家码(Mobile Country Code，MCC)和移动网络代码(Mobile Network Code，MNC)，PLMN包括MCC和MNC。PLMN包括MCC和MNC。HPLMN和PLMN相同是指HPLMN包括的MCC与PLMN包括MCC相同，HPLMN包括的MNC与PLMN包括的MNC相同。HPLMN和PLMN不同是指HPLMN包括的MCC与PLMN包括MCC相同，HPLMN包括的MNC与PLMN包括的MNC不同，或者HPLMN包括的MCC与PLMN包括MCC不同，HPLMN包括的MNC与PLMN包括的MNC相同，或者HPLMN包括的MCC与PLMN包括MCC不同，HPLMN包括的MNC与PLMN包括的MNC不同。
3.分流信息
示例性地，分流信息可以包括分流规则，应用标识，应用标识对应的数据探测规则，数据转发规则，带宽控制规则中的至少一项。
如图1所示为漫游场景的架构图。以下对图1中涉及的设备的功能进行简要说明。
其中，终端设备是移动用户与网络交互的入口，能够提供基本的计算能力，存储能力，向用户显示业务窗口，接收用户操作输入。下一代终端设备(NextGen UE)可以采用新空口技术，与RAN建立信号连接，数据连接，从而传输控制信号和业务数据到移动网络。终端设备可以包括各种具有无线通信功能的手持设备、车载设备、可穿戴设备、计算设备或连接到无线调制解调器的其它处理设备，以及各种形式的终端，移动台(mobile station，MS)，终端(terminal)，软终端等等，例如水表、电表、传感器等。
接入网(access network，AN)设备或无线接入网(radioaccess network，AN)设备：部署在靠近终端设备的位置，为特定区域的授权用户提供入网功能，并能够根据用户的级别，业务的需求等确定不同质量的传输隧道来传输用户数据。RAN能够管理自身的资源，合理利用，按需为终端设备提供接入服务，并负责把控制信号和用户数据在终端设备和核心网之间转发。
数据网络(data network，DN)：为用户提供业务服务的数据网络，一般客户端位于终端设备，服务端位于数据网络。数据网络可以是私有网络，如局域网，也可以是不受运营商管控的外部网络，例如互联网(Internet)，还可以是运营商共同部署的专有网络，例如提供IP多媒体网络子系统(IP multimedia core network subsystem，IMS)服务的网络。
其中，核心网用户面包括用户面功能(user plane function，UPF)；核心网控制面包括接入和移动性管理功能(access and mobility management function，AMF)，会话管理功能(session management function，SMF)，统一数据管理(unified data management，UDM)，策略控制功能(policy control function，PCF)，应用功能(application function，AF)，认证服务器功能(authentication server function，AUSF)，网络切片选择功能(network slice selection function，NSSF)，网络切片选择的认证和授权功能(network slice-specific authentication and authorization function,NSSAAF)。
核心网控制面采用服务化架构，控制面网元之间的交互采用服务调用的方式，来替换传统架构中的点对点通信方式。在服务化架构中，控制面网元会向其他控制面网元开放服务，供其他控制面网元调用；在点对点通信中，控制面网元之间通信接口会存储一套特定的消息，只能由接口两端的控制面网元在通信时使用。
以下对核心网中的功能实体的功能进行简单介绍：
1、会话管理网元：主要用于会话管理、终端设备的IP地址分配和管理、选择可管理用户设备平面功能、策略控制、或收费功能接口的终结点以及下行数据通知等。在5G通信中，会话管理网元可以是SMF网元，在未来通信如6G通信中，会话管理功能网元仍可以是SMF网元，或者有其它名称，本申请对此不作限定。Nsmf是SMF提供的基于服务的接口，SMF可以通过Nsmf与其他的网络功能通信。
2、接入管理网元：主要用于移动性管理和接入管理等，例如可以是4G通信网络中的移动性管理实体(mobility management entity，MME)功能或者5G网络中的AMF网元。在未来通信如6G通信中，接入管理网元仍可以是AMF网元，或者有其它名称，本申请对此不作限定。Namf是AMF提供的基于服务的接口，AMF可以通过Namf与其他的网络功能通信。
3、策略控制网元：用于指导网络行为的统一策略框架，为控制平面功能网元(例如AMF，SMF等)提供策略规则信息等。在5G通信中，策略控制网元可以是PCF网元，在未来通信如6G通信中，策略控制网元仍可以是PCF网元，或者有其它名称，本申请对此不作限定。其中Npcf是PCF提供的基于服务的接口，PCF可以通过Npcf与其他的网络功能通信。
4、数据管理网元：用于处理用户标识、签约、接入鉴权、注册、或移动性管理等。在5G通信中，数据管理网元可以是UDM网元，在未来通信如6G通信中，数据管理网元仍可以是UDM网元，或者有其它名称，本申请对此不作限定。其中Nudm是UDM提供的基于服务的接口，UDM可以通过Nudm与其他的网络功能通信。
5、应用网元：用于进行应用影响的数据路由，接入网络开放功能，或与策略框架交互进行策略控制等。在5G通信中，应用网元可以是AF网元，在未来通信如6G通信中，应用网元仍可以是AF网元，或者有其它名称，本申请对此不作限定。Naf是AF提供的基于服务的接口，AF可以通过Naf与其他的网络功能通信。
6、用户面网元：用于分组路由和转发、或用户面数据的服务质量(quality of service，QoS)处理等。在5G通信中，用户面网元可以是用户面功能(user plane function，UPF)网元，在未来通信如6G通信中，用户面网元仍可以是UPF网元，或者有其它名称，本申请对此不作限定。
7、认证服务网元：主要用于用户鉴权等。在5G通信中，认证服务网元可以是AUSF网元，在未来通信如6G通信中，认证服务网元仍可以是AUSF网元，或者有其它名称，本申请对此不作限定。Nausf是AUSF提供的基于服务的接口，AUSF可以通过Nausf与其他的网络功能通信。
8、网络切片选择功能网元：用于为终端设备选择网络切片，在5G通信中，网络切片选择功能网元可以是NSSF网元，在未来通信如6G通信中，网络切片选择功能网元仍可以是NSSF网元，或者有其它名称，本申请对此不作限定。
9、网络切片选择的认证和授权功能网元：用于为终端设备进行切片鉴权。
可以理解的是，在漫游场景下，H-SMF、H-PCF和H-NSSF分别为归属地(home)SMF、归属地PCF和归属地NSSF，V-SMF、V-PCF和V-NSSF分别为拜访地(visit)SMF、拜访地PCF和拜访地NSSF。
由图2可知，V-SMF和V-PCF之间没有通信接口，V-PCF和H-PCF之间可以通过N24接口进行通信，V-SMF和H-SMF之间可以通过N16接口进行通信。在漫游场景下，终端设备在拜访地建立PDU会话的流程中，H-PCF可以通过H-SMF向V-SMF发送用户签约的策略数据。其中，用户签约的策略数据包括终端设备在通过归属地UPF访问通用数据网络(例如，Internet)时，归属地UPF对该终端设备的数据进行策略控制和计费控制的相关信息，例如带宽控制信息、计费方法信息等。但是，用户签约的策略数据并不包括分流信息。
如图2所示为ULCL的网络架构示意图。在图2中，UPF的形态可以包含中心UPF、边缘UPF、UL CL UPF三种，如下表1对三种UPF的形态进行说明。
表1
在图2中，UE1希望访问园区外的网络(即Internet)。UE1通过RAN向ULCLUPF发送上行数据，ULCLUPF根据该上行数据的特征将该上行数据分流至中心UPF，则进一步由中心UPF转发至Internet。类似的，中心UPF接收到Internet的下行数据，并将下行数据转发至ULCLUPF，ULCLUPF通过RAN将下行数据转发至UE1。
UE2希望访问园区内的网络(即本地DN)。UE2通过RAN向ULCLUPF发送上行数据，ULCLUPF根据该上行数据的特征将该上行数据分流至边缘UPF，并进一步由边缘UPF转发至本地DN。类似的，边缘UPF接收到本地DN的下行数据，并将下行数据转发至ULCLUPF，ULCLUPF通过RAN将下行数据转发至UE1。
如表2所示为图2中用户面相关接口的说明。
表2
示例性地，以下对终端设备使用ULCL功能访问本地业务的场景(即分流场景)进行举例说明，可以理解的是，下述场景仅为举例，不作为本申请的限定。
示例性地，终端设备希望在特定区域购买和使用特定的套餐，即访问本地业务。需要说明的是，这里特定区域可以是指配置本地DN的区域。例如，这里的特定区域为大型赛事举办场馆、旅游景点，大型展览会，大学校园，企业园区。
场景1，当该特定区域为大型赛事举办场馆时，终端设备希望通过转播该赛事的应用访问本地DN免流量观看。若终端设备为非漫游用户，会话管理网元可以结合分流信息确定为终端设备的数据进行分流，为终端设备选择UL CL UPF和辅锚点UPF，将UL CL UPF和辅锚点UPF插入到当前的会话中，并对UL CL UPF下发相应的分流规则来实现对终端设备的数据的分流控制，进而能够实现终端设备通过该转播该赛事的应用访问本地DN免流量观看。但是，若终端设备为漫游用户，由于会话管理网元无法获得该终端设备的分流信息，则使得会话管理网元无法判断是否需要将终端设备的数据分流到本地DN，即无法使用ULCL功能，因此，终端设备不能实现通过该转播该赛事的应用访问本地DN免流量观看。
场景2，当该特定区域为旅游景点时，终端设备希望通过该旅游景点的应用访问本地DN收听景点讲解。与上述场景1类似，若终端设备为漫游用户，则终端设备不能实现通过该旅游景点的应用访问本地DN收听景点讲解。
场景3，当该特定区域为大型展览会时，终端设备希望通过该展览会的应用访问本地DN获取该展览会的展位信息。与上述场景1和场景2类似，若终端设备为漫游用户，则终端设备不能实现通过该展览会的应用访问本地DN获取该展览会的展位信息。
场景4，当该特定区域为企业园区或大学校园时，终端设备希望通过相应的应用访问本地DN获取信息。与上述场景1、场景2和场景3类似，若终端设备为漫游用户，则终端设备不能实现通过相应的应用访问本地DN获取信息。
由上述分析可知，在漫游场景下，由于协议没有定义拜访地SMF和拜访地PCF的接口和相应的交互流程，会话管理网元无法获得终端设备的分流信息，进而会话管理网元无法判断是否需要将终端设备的数据分流到本地DN，所以，终端设备无法在拜访地使用ULCL功能访问本地业务。
基于此，本申请实施例提供一种通信方法，用以解决当前漫游用户无法在拜访地使用ULCL功能访问本地业务的问题。如图3所示，该方法包括：
步骤301：接入和移动性管理网元接收来自于终端设备的第一消息，终端设备为漫游用户。
示例性地，第一消息可以包括但不限以下几种可能的实现方式：
方式1：第一消息用于请求为终端设备建立第一会话。
示例性地，在终端设备完成初始注册流程之后，终端设备可以通过接入网设备向接入和移动性管理网元发送第一消息。其中，第一消息可以为协议数据单元(protocol data unit，PDU)会话建立请求消息。
方式2：第一消息用于请求移动性注册。
示例性地，在终端设备完成PDU会话建立流程之后，终端设备可以通过接入网设备向接入和移动性管理网元发送第一消息。其中，第一消息可以为移动性注册请求(mobilityregistrationrequest)消息。
方式3：第一消息用于请求服务。
示例性地，在终端设备完成PDU会话建立流程之后，终端设备可以通过接入网设备向接入和移动性管理网元发送第一消息。其中，第一消息可以为服务请求(servicerequest)消息。
步骤302：接入和移动性管理网元为终端设备选择拜访地会话管理网元。
针对方式1，接入和移动性管理网元需要为终端设备选择拜访地会话管理网元。
其中，接入和移动性管理网元为终端设备选择拜访地会话管理网元可以参考现有流程，此处不再赘述。
针对上述方式2和方式3，接入和移动性管理网元已为终端设备选择拜访地会话管理网元，因此不需要再次选择。因此，对于方式2和方式3，步骤302为可选的步骤。
步骤303：接入和移动性管理网元向拜访地会话管理网元发送第二消息，第二消息包括拜访地策略控制网元的标识。
此外，第二消息还需要携带终端设备的标识。
示例性地，终端设备的标识可以包括国际移动用户识别码(international mobile subscriber identity，IMSI)，或移动用户号码(mobile subscriber international ISDN/PSTN number，MSISDN)，或用户永久标识(subscription permanent identifier,SUPI)，或通用公共用户标识(generic public subscription identifier，GPSI)，或国际移动设备标识码(International Mobile Equipment Identity，IMEI)中的至少一个。
示例性地，针对上述方式1，第二消息用于请求为终端设备建立第一会话。例如，第二消息可以为PDU会话管理上下文建立请求(Nsmf_PDUSession_CreateSMContext)消息。
针对上述方式2，第二消息用于请求移动性注册。例如，第二消息可以为PDU会话管理上下文更新请求(Nsmf_PDUSession_UpdateSMContext)消息。
针对上述方式3，第二消息用于请求服务。例如，第二消息可以为PDU会话管理上下文更新请求(Nsmf_PDUSession_UpdateSMContext)消息。
示例性地，接入和移动性管理网元在终端设备的注册过程中获取拜访地策略控制网元的标识。可以理解的是，在终端设备的注册流程中，接入和移动性管理网元需要与拜访地策略控制网元交互信息，进而获取拜访地策略控制网元的标识。示例性地，在注册流程，接入和移动性管理网元向网络仓储功能(network repository function,NRF)网元发送终端设备的标识，例如SUPI或者GPSI，用以查询PCF的信息，网络仓储功能网元向接入和移动性管理网元发送拜访地策略控制网元的标识。
示例性地，拜访地策略控制网元的标识包括拜访地策略控制网元的实例的标识(PCF Instance ID)，或者拜访地策略控制网元的全限定域名。
步骤304：拜访地会话管理网元接收来自于接入和移动性管理网元的第二消息，拜访地会话管理网元根据拜访地策略控制网元的标识向拜访地策略控制网元发送第三消息，第三消息用于请求终端设备的分流信息。其中，第三消息可以包括终端设备的标识。
示例性地，第三消息为会话管理策略控制建立(Npcf_SMPolicyControl_Create)消息。
在一种可能的实现方式中，拜访地会话管理网元可以根据拜访地策略控制网元的标识获取拜访地策略控制网元的IP地址，示例性地，拜访地会话管理网元可以保存拜访地会话管理网元的标识与拜访地策略控制网元的IP地址的对应关系。进而，拜访地会话管理网元可以根据拜访地策略控制网元的标识，查询拜访地策略控制网元的IP地址，根据拜访地策略控制网元的IP地址向拜访地策略控制网元发送第三消息。
在另一种可能的实现方式中，拜访地会话管理网元可以向网络功能仓储网元(network repository function,NRF)发送拜访地策略控制网元的实例的标识，网络仓储功能网元可以保存拜访地策略控制网元的实例的标识与拜访地策略控制网元的IP地址的对应关系。网络仓储功能网元可以根据拜访地策略控制网元的实例的标识，查询拜访地策略控制网元的IP 地址，并向拜访地会话管理网元发送拜访地策略控制网元的IP地址。
在另一种可能的实现方式中，拜访地会话管理网元可以向域名系统(domain name system，DNS)发送拜访地策略控制网元的全限定域名，域名系统可以保存拜访地策略控制网元的全限定域名与拜访地策略控制网元的IP地址的对应关系。域名系统可以根据拜访地策略控制网元的全限定域名，查询拜访地策略控制网元的IP地址，并向拜访地会话管理网元发送拜访地策略控制网元的IP地址。
步骤305：拜访地策略控制网元接收来自于拜访地会话管理网元的第三消息，拜访地策略控制网元向拜访地会话管理网元发送分流信息。
示例性地，拜访地策略控制网元向拜访地会话管理网元发送会话管理策略控制建立响应消息，会话管理策略控制建立响应消息携带分流信息。
拜访地策略控制网元可以采用但不限于以下两种方式获得分流信息：
在一种可能的设计中，拜访地策略控制网元根据第三消息中的终端设备的标识可以确定终端设备为漫游用户，并进一步向归属地策略控制网元发送请求消息，请求消息用于请求分流信息，拜访地策略控制网元从归属地策略控制网元接收分流信息。其中，拜访地策略控制网元确定终端设备为漫游用户可以参考上述关于终端设备的漫游类型的相关描述，此处不再赘述。
在另一种可能的设计中，拜访地策略控制网元根据第三消息中的终端设备的标识可以确定终端设备已购买需要分流信息的服务，拜访地策略控制网元可以为漫游用户签约一个分流信息。例如，用户位于旅游景点A，并通过手机下载并登陆旅游景点A的APP，用户购买该APP提供的旅游景点A的讲解套餐，则拜访地策略控制网元为该手机签约一个分流信息。
采用上述实施例，拜访地会话管理网元可以获得分流信息，进而实现为漫游用户创建ULCL会话，从而可以保证漫游用户使用ULCL功能访问本地数据网络。
本申请实施例还提供一种通信方法，用以解决当前漫游用户无法在拜访地使用ULCL功能访问本地业务的问题。如图4所示，该方法包括：
步骤401和步骤402可以参考上述步骤301和步骤302中的相关描述，此处不再赘述。
步骤403：接入和移动性管理网元向拜访地策略控制网元发送拜访地会话管理网元的标识和终端设备的标识。
示例性地，接入和移动性管理网元可以向拜访地策略控制网元发送接入管理策略控制更新请求消息，接入管理策略控制更新请求消息包括拜访地会话管理网元的标识和终端设备的标识。
示例性地，拜访地会话管理网元的标识包括拜访地会话管理网元的实例的标识(例如，V-SMF Instance ID)、或者拜访地会话管理网元的全限定域名(例如，V-SMF FQDN)。
此外，拜访地策略控制网元在接收到接入管理策略控制更新请求消息后，还可以向接入和移动性管理网元发送接入管理策略控制更新响应消息，接入管理策略控制更新响应消息可以包括接入管理策略(access management Policy)，接入管理策略可以包括用户归属的切片信息，DNN等。
步骤404：拜访地策略控制网元接收来自于接入和移动性管理网元的拜访地会话管理网元的标识和终端设备的标识，根据拜访地会话管理网元的标识和终端设备的标识向拜访 地会话管理网元发送终端设备的分流信息。
示例性地，在拜访地策略控制网元根据终端设备的标识和拜访地会话管理网元的标识向拜访地会话管理网元发送终端设备的分流信息时，拜访地策略控制网元根据拜访地会话管理网元的标识获取拜访地会话管理网元的IP地址，拜访地策略控制网元根据终端设备的标识和拜访地会话管理网元的IP地址向拜访地会话管理网元发送终端设备的分流信息。
在一种可能的实现方式中，若拜访地会话管理网元的标识为拜访地会话管理网元的实例的标识，拜访地策略控制网元向网络功能仓储网元发送拜访地会话管理网元的实例的标识，网络功能仓储网元根据拜访地会话管理网元的实例的标识查询拜访地会话管理网元的IP地址，并向拜访地策略控制网元发送拜访地会话管理网元的IP地址。
在另一种可能的实现方式中，若拜访地会话管理网元的标识为拜访地会话管理网元的全限定域名，拜访地策略控制网元向域名系统(domain name system，DNS)发送拜访地会话管理网元的全限定域名，域名系统根据拜访地会话管理网元的全限定域名查询拜访地会话管理网元的IP地址，并向拜访地策略控制网元发送拜访地会话管理网元的IP地址。
其中，关于分流信息以及拜访地策略控制网元如何获得分流信息，可以参考上述步骤305中的相关描述此处不再赘述。
以下结合具体实施例对上述图3所示的实施例进行举例说明：
如图5所示为在会话建立流程中创建ULCL会话的流程图。此处，省略UE的初始注册流程。
S501：UE通过RAN向AMF发送PDU会话建立请求消息。
示例性地，该消息携带UE的标识，数据网络名称(data network name，DNN)和UE的位置信息。
S502：AMF为UE选择V-SMF。
S503：AMF向V-SMF发送PDU会话管理上下文建立请求消息。
示例性地，该消息包括V-PCF的标识，例如V-PCFInstanceID或V-PCF的全限定域名等。
此外，该消息还包括UE的标识，DNN和UE的位置信息。
S504：V-SMF与V-UPF交互执行N4会话建立流程。
S505：V-SMF向V-PCF发送会话管理策略建立消息。
示例性地，V-SMF根据S502中获得的V-PCF的标识确定V-PCF的IP地址，向V-PCF发送会话管理策略建立消息，会话管理策略建立消息用于请求UE的分流信息，该消息包括UE的标识。
其中，V-SMF可以根据本地配置确定V-PCF的标识对应V-PCF的IP地址，或V-SMF向NRF发送V-PCF的标识，NRF向V-SMF发送V-PCF的IP地址。
S506：V-PCF向V-SMF发送会话管理策略建立响应消息，该消息携带UE的分流信息。
其中，UE的分流信息可以是V-PCF从H-PCF获取的，或者V-PCF为UE分配的。
S507：V-SMF确定UE已签约分流信息，根据DNN，UE的位置信息确定为UE选择UL CL UPF和PSA UPF。
示例性地，V-SMF根据S506中接收到的会话管理策略建立响应消息中是否携带UE的分流信息判断是否对UE的业务数据流进行分流。若S506中接收到的会话管理策略建立 响应消息未携带UE的分流信息，则不需要执行S507及下述步骤。
V-SMF需要根据本地配置判断已经针对该DNN开启了UL CL分流功能，并根据UE的位置信息和本地配置的UL CL UPF适用的区域范围判定UE已处于特定区域内，V-SMF可以选择UL CL UPF为UE创建分流会话。
可以理解的是，若该DNN未开启UL CL分流功能，和/或UE未处于特定区域内，V-V-SMF不需要为UE创建分流会话。
S508A：V-SMF向ULCL UPF发送N4会话建立请求(N4Session Establishment Request)消息。
示例性地，N4会话建立请求携带分流信息中的应用标识，进而ULCL UPF可以根据该应用标识获取相应的数据转发策略。
S508B：V-SMF向PSA UPF发送N4会话建立请求消息。
示例性地，N4会话建立请求携带分流信息中的应用标识。
S509A：ULCL UPF接收N4会话建立请求消息，向V-SMF发送N4会话建立响应(N4Session Establishment Response)消息。
示例性地，N4会话建立响应消息携带UL CL UPF的N3接口上行转发地址、UL CL UPF的N9接口下行转发地址。
其中，UL CL UPF的N3接口上行转发地址用于在UE发送上行数据时，RAN将从UE接收到的上行数据转发至该地址。其中，UL CL UPF将该地址发送至V-SMF，并由V-SMF经AMF转发至RAN。此外，RAN通过AMF向V-SMF发送N3接口下行转发地址，V-SMF将N3接口下行转发地址通知UL CL UPF。其中，N3接口下行转发地址用于在网络侧给UE发送的下行数据时，UL CL UPF将接收到的下行数据转发至该地址。
UL CL UPF的N9接口下行转发地址用于在网络侧给UE发送的下行数据时，V-UPF或者PSAUPF将发送给UE的下行数据转发至该地址。
S509B：PSA UPF接收N4会话建立请求消息，向V-SMF发送N4会话建立响应消息。
示例性地，N4会话建立响应消息携带PSAUPF的N9接口上行转发地址。
PSA UPF2的N9接口上行转发地址：用于ULCL UPF将接收到UE的上行数据转发至该地址。
需要说明的是，当ULCL UPF和PSA UPF分设时，上述S508A、S508B、S509A、S509B均需要执行。当ULCL UPF和PSA UPF合设时，上述S508B、S509B不需要执行。
S510：V-SMF向V-UPF发送N4会话修改请求(N4Session Modification Request)消息。
示例性地，N4会话修改请求消息包括ULCL UPF N9接口下行转发地址。
S511：V-UPF更新下行数据转发隧道信息。
示例性地，V-UPF将下行数据转发隧道信息更新为ULCL UPF N9接口下行转发地址。
S512：V-UPF向V-SMF发送N4会话修改响应(N4Session Modification Response)消息。
示例性地，N4会话修改响应消息包括V-UPF的N9接口上行数据转发地址。
V-UPF的N9接口上行数据转发地址：用于ULCL UPF将接收到UE的上行数据转发至该地址。
S513A：V-SMF向ULCL UPF发送报文转发控制协议会话修改请求(packet forwarding  control protocol Session Modification Request)消息。
示例性地，PFCP会话修改请求消息包括V-UPF的N9接口上行数据转发地址，PSA UPF的N9接口上行转发地址。
S514A：ULCL UPF更新上行数据转发隧道信息。
示例性地，ULCL UPF将上行数据转发隧道信息更新为V-UPF的N9接口上行数据转发地址，PSA UPF的N9接口上行转发地址。
S515A：ULCL UPF向V-SMF发送PFCP会话修改响应消息。
S513B：V-SMF向PSA UPF发送PFCP会话修改请求消息。
示例性地，PFCP会话修改请求消息包括ULCL UPF N9接口下行转发地址。
S514B：PSA UPF更新下行数据转发隧道信息。
示例性地，PSA UPF将下行数据转发隧道信息更新为ULCL UPF N9接口下行转发地址。
S515B：PSA UPF向V-SMF发送PFCP会话修改响应消息。
需要说明的是，当ULCL UPF和PSA UPF分设时，上述S513A、S514A、S515A、S513B、S514B、S515B均需要执行。当ULCL UPF和PSA UPF合设时，上述S513B、S514B、S515B不需要执行。且在S513A中PFCP会话修改请求消息不再包括V-UPF的N9接口上行数据转发地址，此时，在S514A中，ULCL UPF只需将上行数据转发隧道信息更新为V-UPF的N9接口上行数据转发地址。
S516：V-SMF向AMF发送PDU会话管理上下文建立响应消息。
S517：AMF通过RAN向UE发送PDU会话建立响应消息。
通过上述过程，在会话建立过程中，V-SMF确定UE已签约分流信息，可以判断是否为UE创建ULCL会话，从而可以实现漫游用户访问本地数据网络。
以下结合具体实施例对上述图3所示的实施例进行举例说明：
如图6所示为在位置更新流程中创建ULCL会话的流程图。此处，省略UE的初始注册流程和UE的PDU会话建立流程。
S601：UE通过RAN向AMF发送移动性注册请求消息。
示例性地，该消息携带UE的标识，DNN和UE的位置信息。
S602：AMF向V-SMF发送PDU会话管理上下文更新请求消息。
示例性地，该消息包括V-PCF的标识，例如V-PCFInstanceID或V-PCF的全限定域名等。
此外，该消息还包括UE的标识，DNN和UE的位置信息。
S603：V-SMF与V-UPF交互执行N4会话修改流程。
S604至S614B可以参考上述S505至S515B，此处不再赘述。
S615：V-SMF向AMF发送PDU会话管理上下文更新响应消息。
S616：AMF通过RAN向UE发送移动性注册响应消息。
通过上述过程，在位置更新流程中，V-SMF确定UE已签约分流信息，可以判断是否为UE创建ULCL会话，从而可以实现漫游用户访问本地数据网络。
如图7所示为在服务请求流程中创建ULCL会话的流程图。此处，省略UE的初始注册流程和UE的PDU会话建立流程。
S701：UE通过RAN向AMF发送服务请求消息。
示例性地，该消息携带UE的标识，DNN和UE的位置信息。
S702：AMF向V-SMF发送PDU会话管理上下文更新请求消息。
示例性地，该消息包括V-PCF的标识，例如V-PCFInstanceID或V-PCF的全限定域名等。
此外，该消息还包括UE的标识，DNN和UE的位置信息。
S703：V-SMF与V-UPF交互执行N4会话修改流程。
S704至S714B可以参考上述S505至S515B，此处不再赘述。
S715：V-SMF向AMF发送PDU会话管理上下文更新响应消息。
S716：AMF通过RAN向UE发送服务接受消息。
通过上述过程，在服务请求流程中，V-SMF确定UE已签约分流信息，可以判断是否为UE创建ULCL会话，从而可以实现漫游用户访问本地数据网络。
以下结合具体实施例对上述图4所示的实施例进行举例说明：
如图8所示在会话建立后创建ULCL会话的流程图。此处，省略UE的初始注册流程。
S801：UE通过RAN向AMF发送PDU会话建立请求消息。
示例性地，该消息携带UE的标识，DNN和UE的位置信息。
S802：AMF为UE选择V-SMF。
S803：AMF向V-SMF发送PDU会话管理上下文建立请求消息。
该消息包括UE的标识，DNN和UE的位置信息。
S804：V-SMF与V-UPF交互执行N4会话建立流程。
S805：V-SMF向AMF发送PDU会话管理上下文建立响应消息。
S806：AMF通过RAN向UE发送PDU会话建立响应消息。
S807：AMF向V-PCF发送接入管理策略控制更新请求消息。
示例性，AMF可以基于本地配置在会话建立完成后向V-PCF发送接入管理策略控制更新请求消息。
示例性地，接入管理策略控制更新请求消息包括UE的标识、PDU会话的标识和V-SMF的标识，V-SMF的标识可以为V-SMF的Instance ID或V-SMF的FQDN等。
S808：V-PCF向V-SMF发送UE的分流信息。
示例性地，若V-SMF的标识为V-SMF的Instance ID，V-PCF向NRF发送V-SMF的Instance ID，NRF向V-PCF发送V-SMF的IP地址。
若V-SMF的标识为V-SMF的FQDN，V-PCF向DNS发送V-SMF的FQDN，DNS向V-PCF发送V-SMF的IP地址。
S809：V-PCF向AMF发送接入管理策略控制更新响应消息。
S810至S818B可以参考上述S507至S515B。
通过上述过程，在会话建立后，V-PCF获得V-SMF的标识，并向V-SMF发送分流信息，V-SMF确定UE已签约分流信息，可以判断是否为UE创建ULCL会话，从而可以实现漫游用户访问本地数据网络。
以下结合具体实施例对上述图4所示的实施例进行举例说明：
如图9所示为在位置更新流程之后创建ULCL会话的流程图。此处，省略UE的初始注册流程和UE的PDU会话建立流程。
S901：UE通过RAN向AMF发送移动性注册请求消息。
示例性地，该消息携带UE的标识，DNN和UE的位置信息。
S902：AMF向V-SMF发送PDU会话管理上下文更新请求消息。
示例性地，该消息包括V-PCF的标识，例如V-PCFInstanceID或V-PCF的全限定域名等。
此外，该消息还包括UE的标识，DNN和UE的位置信息。
S903：V-SMF与V-UPF交互执行N4会话修改流程。
S904：V-SMF向AMF发送PDU会话管理上下文更新响应消息。
S905：AMF通过RAN向UE发送移动性注册响应消息。
S906：AMF向V-PCF发送接入管理策略控制更新请求消息。
示例性，AMF可以基于本地配置在位置更新流程之后向V-PCF发送接入管理策略控制更新请求消息。
示例性地，接入管理策略控制更新请求消息包括UE的标识、PDU会话的标识和V-SMF的标识，V-SMF的标识可以为V-SMF的Instance ID或V-SMF的FQDN等。
S907至S917B可以参考上述S808至S818B。
通过上述过程，在位置更新流程后，V-PCF获得V-SMF的标识，并向V-SMF发送分流信息，V-SMF确定UE已签约分流信息，可以判断是否为UE创建ULCL会话，从而可以实现漫游用户访问本地数据网络。
如图10所示为在服务请求流程之后创建ULCL会话的流程图。此处，省略UE的初始注册流程和UE的PDU会话建立流程。
S1001：UE通过RAN向AMF发送服务请求消息。
示例性地，该消息携带UE的标识，DNN和UE的位置信息。
S1002：AMF向V-SMF发送PDU会话管理上下文更新请求消息。
示例性地，该消息包括V-PCF的标识，例如V-PCFInstanceID或V-PCF的全限定域名等。
此外，该消息还包括UE的标识，DNN和UE的位置信息。
S1003：V-SMF与V-UPF交互执行N4会话修改流程。
S1004：V-SMF向AMF发送PDU会话管理上下文更新响应消息。
S1005：AMF通过RAN向UE发送服务接受消息。
S1006：AMF向V-PCF发送接入管理策略控制更新请求消息。
示例性，AMF可以基于本地配置在服务请求流程之后向V-PCF发送接入管理策略控制更新请求消息。
示例性地，接入管理策略控制更新请求消息包括UE的标识、PDU会话的标识和V-SMF的标识，V-SMF的标识可以为V-SMF的Instance ID或V-SMF的FQDN等。
S1007至S1017B可以参考上述S807至S818B。
通过上述过程，在服务请求流程后，V-PCF获得V-SMF的标识，并向V-SMF发送分流信息，V-SMF确定UE已签约分流信息，可以判断是否为UE创建ULCL会话，从而可以实现漫游用户访问本地数据网络。
此外，对于上述图3和图4所示的实施例，接入和移动性管理网元还可以获取终端设 备的IP地址，进而接入和移动性管理网元向拜访地策略控制网元发送终端设备的IP地址。拜访地策略控制网元向拜访地引导服务(bootstrapping service，BFS)网元发送注册消息，注册消息包括拜访地策略控制网元的实例的标识和终端设备的IP地址。进而，当终端设备通过能力开放功能(network exposure function，NEF)网元向拜访地策略控制网元修改分流信息时，能力开放功能网元为了确定终端设备对应的拜访地策略控制网元，可以向引导服务网元发送消息，该消息包括终端设备的IP地址，引导服务网元根据终端设备的IP地址确定与终端设备的IP地址对应的拜访地策略控制网元的实例的标识，即与终端设备的IP地址一同注册的拜访地策略控制网元的实例的标识，引导服务网元向能力开放功能网元发送拜访地策略控制网元的实例的标识，进而能力开放功能网元可以确定终端设备对应的拜访地策略控制网元。
以下结合图11对上述内容进行说明，需要说明的是，下述过程可以在会话建立完成后执行。
S1101：V-SMF向H-SMF发送请求消息，该请求消息用于请求UE的IP地址。
S1102：H-SMF向V-SMF发送响应消息，该响应消息包括UE的IP地址。
S1103：V-SMF向AMF发送PDU会话上下文更新请求消息。
PDU会话上下文更新响应消息包括UE的IP地址。
其中，S1101至S1103为可选的步骤。在一种可能的实现方式中，在会话建立过程中，AMF可以通过V-SMF向H-SMF发送PDU会话上下文建立请求消息，该消息用于请求为UE建立会话上下文。H-SMF向V-SMF发送PDU会话上下文建立响应消息，V-SMF向AMF发送PDU会话上下文建立响应消息，PDU会话上下文建立响应消息用于通知AMF会话上下文建立成功，其中，PDU会话上下文建立响应消息包括UE的IP地址。此时，AMF或者V-SMF也可以解析PDU会话上下文建立响应消息获取UE的IP地址。
S1104：AMF向V-PCF发送接入管理策略控制更新请求消息。
示例性地，接入管理策略控制更新请求消息包括UE的IP地址。
S1105：V-PCF向BSF发送注册消息。
该注册消息包括V-PCF的标识和UE的IP地址。
S1106：V-PCF向AMF发送接入管理策略控制更新响应消息。
图12示出了本申请实施例中所涉及的一种通信装置的可能的示例性框图，该装置1200包括：收发模块1220和处理模块1210，收发模块1220可以包括接收单元和发送单元。处理模块1210用于对装置1200的动作进行控制管理。收发模块1220用于支持装置1200与其他网络实体的通信。可选地，装置1200还可以包括存储单元，所述存储单元用于存储装置1200的程序代码和数据。
可选地，所述装置1200中各个模块可以是通过软件来实现。
可选地，处理模块1210可以是处理器或控制器，例如可以是通用中央处理器(central processing unit，CPU)，通用处理器，数字信号处理(digital signal processing，DSP)，专用集成电路(application specific integrated circuits，ASIC)，现场可编程门阵列(field programmable gate array，FPGA)或者其他可编程逻辑器件、晶体管逻辑器件、硬件部件或者其任意组合。其可以实现或执行结合本申请实施例公开内容所描述的各种示例性的逻辑方框，模块和电路。所述处理器也可以是实现计算功能的组合，例如包含一个或多个微 处理器组合，DSP和微处理器的组合等等。收发模块1220可以是通信接口、收发器或收发电路等，其中，该通信接口是统称，在具体实现中，该通信接口可以包括多个接口，存储单元可以是存储器。
当装置1200为接入和移动性管理网元或接入和移动性管理网元中的芯片时，装置1200中的处理模块1210可以支持装置1200执行上文中各方法示例中接入和移动性管理网元的动作，例如可以支持装置1200执行图3中的步骤302。
收发模块1220可以支持装置1200与会话管理网元进行通信，例如，收发模块1220可以支持装置1200执行图3中的步骤301和步骤303。
例如，收发模块1220，用于接收来自于终端设备的第一消息，所述第一消息用于请求为所述终端设备建立第一会话，所述终端设备为漫游用户；处理模块1210，用于为所述终端设备选择拜访地会话管理网元；收发模块1220，用于向所述拜访地会话管理网元发送第二消息，所述第二消息用于请求为所述终端设备建立所述第一会话，所述第二消息包括拜访地策略控制网元的标识。
在一种可能的设计中，处理模块1210，用于在所述终端设备的注册过程中获取所述拜访地策略控制网元的标识。
在一种可能的设计中，所述拜访地策略控制网元的标识包括所述拜访地策略控制网元的实例的标识，或者所述拜访地策略控制网元的全限定域名。
应理解，根据本申请实施例的装置1200可对应于前述方法实施例中接入和移动性管理网元，并且装置1200中的各个模块的操作和/或功能分别为了实现前述方法实施例中接入和移动性管理网元的方法的相应步骤，因此也可以实现前述方法实施例中的有益效果，为了简洁，这里不作赘述。
当装置1200为拜访地会话管理网元或拜访地会话管理网元中的芯片时，装置1200中的处理模块1210可以支持装置1200执行上文中各方法示例中拜访地会话管理网元的动作。
收发模块1220可以支持装置1200与网络设备进行通信，例如，收发模块1220可以支持装置1200执行图3中的步骤303和步骤304。
例如，处理模块1210调用收发模块1220，用于接收来自于接入和移动性管理网元的第二消息，所述第二消息用于请求为终端设备建立第一会话，所述第二消息包括拜访地策略控制网元的标识，所述终端设备为漫游用户；根据所述拜访地策略控制网元的标识向所述拜访地策略控制网元发送第三消息，所述第三消息用于请求所述终端设备的分流信息，接收来自于所述拜访地策略控制网元的所述分流信息。
在一种可能的设计中，处理模块1210，用于在根据所述拜访地策略控制网元的标识向所述拜访地策略控制网元发送第三消息时，根据所述拜访地策略控制网元的标识获取所述拜访地策略控制网元的IP地址；收发模块1220，用于根据所述拜访地策略控制网元的IP地址向所述拜访地策略控制网元发送所述第三消息。
在一种可能的设计中，所述拜访地策略控制网元的标识包括所述拜访地策略控制网元的实例的标识；在根据所述拜访地策略控制网元的标识获取所述拜访地策略控制网元的IP地址时，收发模块1220，用于向网络仓储功能网元发送所述拜访地策略控制网元的实例的标识，接收来自于所述网络仓储功能网元的所述拜访地策略控制网元的IP地址。
在一种可能的设计中，所述拜访地策略控制网元的全限定域名；收发模块1220，用于在根据所述拜访地策略控制网元的标识获取所述拜访地策略控制网元的IP地址时，向域名 系统发送所述拜访地策略控制网元的全限定域名，接收来自于所述域名系统的所述拜访地策略控制网元的IP地址。
应理解，根据本申请实施例的装置1200可对应于前述方法实施例中拜访地会话管理网元，并且装置1200中的各个模块的操作和/或功能分别为了实现前述方法实施例中拜访地会话管理网元的方法的相应步骤，因此也可以实现前述方法实施例中的有益效果，为了简洁，这里不作赘述。
当装置1200为拜访地策略控制网元或拜访地策略控制网元中的芯片时，装置1200中的处理模块1210可以支持装置1200执行上文中各方法示例中拜访地策略控制网元的动作。
收发模块1220可以支持装置1200与网络设备进行通信，例如，收发模块1220可以支持装置1200执行图3中的步骤304和步骤305。
例如，处理模块1210调用收发模块1220，用于接收来自于拜访地会话管理网元的第三消息，所述第三消息用于请求终端设备的分流信息，所述终端设备为漫游用户，向所述拜访地会话管理网元发送所述分流信息。
在一种可能的设计中，收发模块1220，用于向归属地策略控制网元发送请求消息，所述请求消息用于请求所述分流信息，从所述归属地策略控制网元接收所述分流信息。
应理解，根据本申请实施例的装置1200可对应于前述方法实施例中拜访地策略控制网元，并且装置1200中的各个模块的操作和/或功能分别为了实现前述方法实施例中拜访地策略控制网元的方法的相应步骤，因此也可以实现前述方法实施例中的有益效果，为了简洁，这里不作赘述。
当装置1200为接入和移动性管理网元或接入和移动性管理网元中的芯片时，装置1200中的处理模块1210可以支持装置1200执行上文中各方法示例中接入和移动性管理网元的动作，例如可以支持装置1200执行图4中的步骤402。
收发模块1220可以支持装置1200与会话管理网元进行通信，例如，收发模块1220可以支持装置1200执行图4中的步骤401和步骤403。
例如，收发模块1220，用于接收来自于终端设备的第一消息，所述第一消息用于请求为所述终端设备建立第一会话，所述终端设备为漫游用户；所述处理单元，用于为所述终端设备选择拜访地会话管理网元；处理模块1210，用于向拜访地策略控制网元发送所述拜访地会话管理网元的标识和所述终端设备的标识。
在一种可能的设计中，处理模块1210，用于获取所述终端设备的IP地址；收发模块1220，用于向所述拜访地策略控制网元发送所述终端设备的IP地址。
应理解，根据本申请实施例的装置1200可对应于前述方法实施例中接入和移动性管理网元，并且装置1200中的各个模块的操作和/或功能分别为了实现前述方法实施例中接入和移动性管理网元的方法的相应步骤，因此也可以实现前述方法实施例中的有益效果，为了简洁，这里不作赘述。
当装置1200为拜访地策略控制网元或拜访地策略控制网元中的芯片时，装置1200中的处理模块1210可以支持装置1200执行上文中各方法示例中拜访地策略控制网元的动作。
收发模块1220可以支持装置1200与网络设备进行通信，例如，收发模块1220可以支持装置1200执行图4中的步骤403和步骤404。
例如，处理模块1210调用收发模块1220，用于接收来自于接入和移动性管理网元的拜访地会话管理网元的标识和终端设备的标识，所述终端设备为漫游用户，根据所述终端 设备的标识和所述拜访地会话管理网元的标识向所述拜访地会话管理网元发送所述终端设备的分流信息。
在一种可能的设计中，处理模块1210，用于在根据所述终端设备的标识和所述拜访地会话管理网元的标识向所述拜访地会话管理网元发送所述终端设备的分流信息时，根据所述拜访地会话管理网元的标识获取所述拜访地会话管理网元的IP地址；收发模块1220，用于根据所述终端设备的标识和所述拜访地会话管理网元的IP地址向所述拜访地会话管理网元发送所述终端设备的分流信息。
在一种可能的设计中，所述拜访地会话管理网元的标识为所述拜访地会话管理网元的实例的标识；收发模块1220，用于在根据所述拜访地会话管理网元的标识获取所述拜访地会话管理网元的IP地址时，向网络仓储功能网元发送所述拜访地会话管理网元的实例的标识，从所述网络仓储功能接收所述拜访地会话管理网元的IP地址。
在一种可能的设计中，所述拜访地会话管理网元的标识为所述拜访地会话管理网元的全限定域名；收发模块1220，用于在根据所述拜访地会话管理网元的标识获取所述拜访地会话管理网元的IP地址时，向域名系统发送所述拜访地会话管理网元的全限定域名，所述拜访地策略控制网元从所述域名系统接收所述拜访地会话管理网元的IP地址。
应理解，根据本申请实施例的装置1200可对应于前述方法实施例中拜访地策略控制网元，并且装置1200中的各个模块的操作和/或功能分别为了实现前述方法实施例中拜访地策略控制网元的方法的相应步骤，因此也可以实现前述方法实施例中的有益效果，为了简洁，这里不作赘述。
图13示出了根据本申请实施例的通信装置1300的示意性结构图。如图13所示，所述装置1300包括：处理器1301。
当装置1300为接入和移动性管理网元或接入和移动性管理网元中的芯片时，一种可能的实现方式中，当所述处理器1301用于调用接口执行以下动作：接收来自于终端设备的第一消息，所述第一消息用于请求为所述终端设备建立第一会话，所述终端设备为漫游用户；为所述终端设备选择拜访地会话管理网元；向所述拜访地会话管理网元发送第二消息，所述第二消息用于请求为所述终端设备建立所述第一会话，所述第二消息包括拜访地策略控制网元的标识。
应理解，所述装置1300还可用于执行前文实施例中接入和移动性管理网元侧的其他步骤和/或操作，为了简洁，这里不作赘述。
当装置1300为拜访地会话管理网元或拜访地会话管理网元中的芯片时，一种可能的实现方式中，当所述处理器1301用于调用接口执行以下动作：接收来自于接入和移动性管理网元的第二消息，所述第二消息用于请求为终端设备建立第一会话，所述第二消息包括拜访地策略控制网元的标识，所述终端设备为漫游用户；根据所述拜访地策略控制网元的标识向所述拜访地策略控制网元发送第三消息，所述第三消息用于请求所述终端设备的分流信息，接收来自于所述拜访地策略控制网元的所述分流信息。
应理解，所述装置1300还可用于执行前文实施例中拜访地会话管理网元侧的其他步骤和/或操作，为了简洁，这里不作赘述。
当装置1300为拜访地策略控制网元或拜访地策略控制网元中的芯片时，一种可能的实现方式中，当所述处理器1301用于调用接口执行以下动作：接收来自于拜访地会话管理网元的第三消息，所述第三消息用于请求终端设备的分流信息，所述终端设备为漫游用 户，向所述拜访地会话管理网元发送所述分流信息。
应理解，所述装置1300还可用于执行前文实施例中拜访地策略控制网元侧的其他步骤和/或操作，为了简洁，这里不作赘述。
当装置1300为接入和移动性管理网元或接入和移动性管理网元中的芯片时，一种可能的实现方式中，当所述处理器1301用于调用接口执行以下动作：接收来自于终端设备的第一消息，所述第一消息用于请求为所述终端设备建立第一会话，所述终端设备为漫游用户；所述处理单元，用于为所述终端设备选择拜访地会话管理网元；向拜访地策略控制网元发送所述拜访地会话管理网元的标识和所述终端设备的标识。
应理解，所述装置1300还可用于执行前文实施例中接入和移动性管理网元侧的其他步骤和/或操作，为了简洁，这里不作赘述。
当装置1300为拜访地策略控制网元或拜访地策略控制网元中的芯片时，一种可能的实现方式中，当所述处理器1301用于调用接口执行以下动作：接收来自于接入和移动性管理网元的拜访地会话管理网元的标识和终端设备的标识，所述终端设备为漫游用户，根据所述终端设备的标识和所述拜访地会话管理网元的标识向所述拜访地会话管理网元发送所述终端设备的分流信息。
应理解，所述装置1300还可用于执行前文实施例中拜访地策略控制网元侧的其他步骤和/或操作，为了简洁，这里不作赘述。
应理解，所述处理器1301可以调用接口执行上述收发动作，其中，调用的接口可以是逻辑接口或物理接口，对此不作限定。可选地，物理接口可以通过收发器实现。可选地，所述装置1300还包括收发器1303。
可选地，所述装置1300还包括存储器1302，存储器1302中可以存储上述方法实施例中的程序代码，以便于处理器1301调用。
具体地，若所述装置1300包括处理器1301、存储器1302和收发器1303，则处理器1301、存储器1302和收发器1303之间通过内部连接通路互相通信，传递控制和/或数据信号。在一个可能的设计中，处理器1301、存储器1302和收发器1303可以通过芯片实现，处理器1301、存储器1302和收发器1303可以是在同一个芯片中实现，也可能分别在不同的芯片实现，或者其中任意两个功能组合在一个芯片中实现。该存储器1302可以存储程序代码，处理器1301调用存储器1302存储的程序代码，以实现装置1300的相应功能。
上述本申请实施例揭示的方法可以应用于处理器中，或者由处理器实现。处理器可能是一种集成电路芯片，具有信号的处理能力。在实现过程中，上述方法实施例的各步骤可以通过处理器中的硬件的集成逻辑电路或者软件形式的指令完成。上述的处理器可以是通用处理器、数字信号处理器(digital signal processor，DSP)、专用集成电路(application specific integrated circuit，ASIC)、现成可编程门阵列(field programmable gate array，FPGA)或者其他可编程逻辑器件、分立门或者晶体管逻辑器件、分立硬件组件，还可以是系统芯片(system on chip，SoC)，还可以是中央处理器(central processor unit，CPU)，还可以是网络处理器(network processor，NP)，还可以是数字信号处理电路(digital signal processor，DSP)，还可以是微控制器(micro controller unit，MCU)，还可以是可编程控制器(programmable logic device，PLD)或其他集成芯片。可以实现或者执行本申请实施例中的公开的各方法、步骤及逻辑框图。通用处理器可以是微处理器或者该处理器也可以是任何常规的处理器等。结合本申请实施例所公开的方法的步骤可以直接体现为硬件译码处理 器执行完成，或者用译码处理器中的硬件及软件模块组合执行完成。软件模块可以位于随机存储器，闪存、只读存储器，可编程只读存储器或者电可擦写可编程存储器、寄存器等本领域成熟的存储介质中。该存储介质位于存储器，处理器读取存储器中的信息，结合其硬件完成上述方法的步骤。
可以理解，本申请实施例中的存储器可以是易失性存储器或非易失性存储器，或可包括易失性和非易失性存储器两者。其中，非易失性存储器可以是只读存储器(read-only memory，ROM)、可编程只读存储器(programmable ROM，PROM)、可擦除可编程只读存储器(erasable PROM，EPROM)、电可擦除可编程只读存储器(electrically EPROM，EEPROM)或闪存。易失性存储器可以是随机存取存储器(random access memory，RAM)，其用作外部高速缓存。通过示例性但不是限制性说明，许多形式的RAM可用，例如静态随机存取存储器(static RAM，SRAM)、动态随机存取存储器(dynamic RAM，DRAM)、同步动态随机存取存储器(synchronous DRAM，SDRAM)、双倍数据速率同步动态随机存取存储器(double data rate SDRAM，DDR SDRAM)、增强型同步动态随机存取存储器(enhanced SDRAM，ESDRAM)、同步连接动态随机存取存储器(synchlink DRAM，SLDRAM)和直接内存总线随机存取存储器(direct rambus RAM，DR RAM)。应注意，本文描述的系统和方法的存储器旨在包括但不限于这些和任意其它适合类型的存储器。
应理解，在本申请实施例中，编号“第一”、“第二”…仅仅为了区分不同的对象，比如为了区分不同的参数信息或者消息，并不对本申请实施例的范围构成限制，本申请实施例并不限于此。
还应理解，在本申请的各种实施例中，上述各过程的序号的大小并不意味着执行顺序的先后，各过程的执行顺序应以其功能和内在逻辑确定。上述各个过程涉及的各种数字编号或序号仅为描述方便进行的区分，而不应对本申请实施例的实施过程构成任何限定。
还应理解，本文中术语“和/或”，仅仅是一种描述关联对象的关联关系，表示可以存在三种关系，例如，A和/或B，可以表示：单独存在A，同时存在A和B，单独存在B这三种情况。另外，本文中字符“/”，一般表示前后关联对象是一种“或”的关系。
本申请中出现的类似于“项目包括如下中的一项或多项：A，B，以及C”表述的含义，如无特别说明，通常是指该项目可以为如下中任一个：A；B；C；A和B；A和C；B和C；A，B和C；A和A；A，A和A；A，A和B；A，A和C，A，B和B；A，C和C；B和B，B，B和B，B，B和C，C和C；C，C和C，以及其他A，B和C的组合。以上是以A，B和C共3个元素进行举例来说明该项目的可选用条目，当表达为“项目包括如下中至少一种：A，B，……，以及X”时，即表达中具有更多元素时，那么该项目可以适用的条目也可以按照前述规则获得。
本领域普通技术人员可以意识到，结合本文中所公开的实施例描述的各示例的单元及算法步骤，能够以电子硬件、或者计算机软件和电子硬件的结合来实现。这些功能究竟以硬件还是软件方式来执行，取决于技术方案的特定应用和设计约束条件。专业技术人员可以对每个特定的应用来使用不同方法来实现所描述的功能，但是这种实现不应认为超出本申请的范围。
所属领域的技术人员可以清楚地了解到，为描述的方便和简洁，上述描述的系统、装置和单元的具体工作过程，可以参考前述方法实施例中的对应过程，在此不再赘述。
在本申请所提供的几个实施例中，应该理解到，所揭露的系统、装置和方法，可以通过其它的方式实现。例如，以上所描述的装置实施例仅仅是示意性的，例如，所述单元的划分，仅仅为一种逻辑功能划分，实际实现时可以有另外的划分方式，例如多个单元或组件可以结合或者可以集成到另一个系统，或一些特征可以忽略，或不执行。另一点，所显示或讨论的相互之间的耦合或直接耦合或通信连接可以是通过一些接口，装置或单元的间接耦合或通信连接，可以是电性，机械或其它的形式。
所述作为分离部件说明的单元可以是或者也可以不是物理上分开的，作为单元显示的部件可以是或者也可以不是物理单元，即可以位于一个地方，或者也可以分布到多个网络单元上。可以根据实际的需要选择其中的部分或者全部单元来实现本实施例方案的目的。
另外，在本申请各个实施例中的各功能单元可以集成在一个处理单元中，也可以是各个单元单独物理存在，也可以两个或两个以上单元集成在一个单元中。
所述功能如果以软件功能单元的形式实现并作为独立的产品销售或使用时，可以存储在一个计算机可读取存储介质中。基于这样的理解，本申请的技术方案本质上或者说对现有技术做出贡献的部分或者该技术方案的部分可以以软件产品的形式体现出来，该计算机软件产品存储在一个存储介质中，包括若干指令用以使得一台计算机设备(可以是个人计算机，服务器，或者网络设备等)执行本申请各个实施例所述方法的全部或部分步骤。而前述的存储介质包括：U盘、移动硬盘、只读存储器ROM、随机存取存储器RAM、磁碟或者光盘等各种可以存储程序代码的介质。

Claims (26)

  1. 一种通信方法，其特征在于，该方法包括：
    接入和移动性管理网元接收来自于终端设备的第一消息，所述第一消息用于请求为所述终端设备建立第一会话，所述终端设备为漫游用户；
    所述接入和移动性管理网元为所述终端设备选择拜访地会话管理网元；
    所述接入和移动性管理网元向所述拜访地会话管理网元发送第二消息，所述第二消息用于请求为所述终端设备建立所述第一会话，所述第二消息包括拜访地策略控制网元的标识。
  2. 如权利要求1所述的方法，其特征在于，还包括:
    所述接入和移动性管理网元在所述终端设备的注册过程中获取所述拜访地策略控制网元的标识。
  3. 如权利要求1或2所述的方法，其特征在于，所述拜访地策略控制网元的标识包括所述拜访地策略控制网元的实例的标识，或者所述拜访地策略控制网元的全限定域名。
  4. 一种通信方法，其特征在于，该方法包括：
    拜访地会话管理网元接收来自于接入和移动性管理网元的第二消息，所述第二消息用于请求为终端设备建立第一会话，所述第二消息包括拜访地策略控制网元的标识，所述终端设备为漫游用户；
    所述拜访地会话管理网元根据所述拜访地策略控制网元的标识向所述拜访地策略控制网元发送第三消息，所述第三消息用于请求所述终端设备的分流信息；
    所述拜访地会话管理网元接收来自于所述拜访地策略控制网元的所述分流信息。
  5. 如权利要求4所述的方法，其特征在于，所述拜访地会话管理网元根据所述拜访地策略控制网元的标识向所述拜访地策略控制网元发送第三消息，包括：
    所述拜访地会话管理网元根据所述拜访地策略控制网元的标识获取所述拜访地策略控制网元的IP地址；
    所述拜访地会话管理网元根据所述拜访地策略控制网元的IP地址向所述拜访地策略控制网元发送所述第三消息。
  6. 如权利要求5所述的方法，其特征在于，所述拜访地策略控制网元的标识包括所述拜访地策略控制网元的实例的标识；
    所述拜访地会话管理网元根据所述拜访地策略控制网元的标识获取所述拜访地策略控制网元的IP地址，包括：
    所述拜访地会话管理网元向网络仓储功能网元发送所述拜访地策略控制网元的实例的标识；
    所述拜访地会话管理网元接收来自于所述网络仓储功能网元的所述拜访地策略控制网元的IP地址。
  7. 如权利要求5所述的方法，其特征在于，所述拜访地策略控制网元的全限定域名；
    所述拜访地会话管理网元根据所述拜访地策略控制网元的标识获取所述拜访地策略控制网元的IP地址，包括：
    所述拜访地会话管理网元向域名系统发送所述拜访地策略控制网元的全限定域名；
    所述拜访地会话管理网元接收来自于所述域名系统的所述拜访地策略控制网元的IP 地址。
  8. 如权利要求4-7任一项所述的方法，其特征在于，所述分流信息包括分流规则，应用标识，所述应用标识对应的数据探测规则，数据转发规则，带宽控制规则中的至少一项。
  9. 一种通信方法，其特征在于，该方法包括：
    拜访地策略控制网元接收来自于拜访地会话管理网元的第三消息，所述第三消息用于请求终端设备的分流信息，所述终端设备为漫游用户；
    所述拜访地策略控制网元向所述拜访地会话管理网元发送所述分流信息。
  10. 如权利要求9所述的方法，其特征在于，还包括：
    所述拜访地策略控制网元向归属地策略控制网元发送请求消息，所述请求消息用于请求所述分流信息；
    所述拜访地策略控制网元从所述归属地策略控制网元接收所述分流信息。
  11. 如权利要求9或10所述的方法，其特征在于，所述分流信息包括分流规则，应用标识，所述应用标识对应的数据探测规则，数据转发规则，带宽控制规则中的至少一项。
  12. 一种通信方法，其特征在于，该方法包括：
    接入和移动性管理网元接收来自于终端设备的第一消息，所述第一消息用于请求为所述终端设备建立第一会话，所述终端设备为漫游用户；
    所述接入和移动性管理网元为所述终端设备选择拜访地会话管理网元；
    所述接入和移动性管理网元向拜访地策略控制网元发送所述拜访地会话管理网元的标识和所述终端设备的标识。
  13. 如权利要求12所述的方法，其特征在于，所述拜访地会话管理网元的标识包括所述拜访地会话管理网元的实例的标识、或者所述拜访地会话管理网元的全限定域名。
  14. 如权利要求12或13所述的方法，其特征在于，还包括：
    所述接入和移动性管理网元获取所述终端设备的IP地址；
    所述接入和移动性管理网元向所述拜访地策略控制网元发送所述终端设备的IP地址。
  15. 一种通信方法，其特征在于，该方法包括
    拜访地策略控制网元接收来自于接入和移动性管理网元的拜访地会话管理网元的标识和终端设备的标识，所述终端设备为漫游用户；
    所述拜访地策略控制网元根据所述终端设备的标识和所述拜访地会话管理网元的标识向所述拜访地会话管理网元发送所述终端设备的分流信息。
  16. 如权利要求15所述的方法，其特征在于，所述拜访地策略控制网元根据所述终端设备的标识和所述拜访地会话管理网元的标识向所述拜访地会话管理网元发送所述终端设备的分流信息，包括：
    所述拜访地策略控制网元根据所述拜访地会话管理网元的标识获取所述拜访地会话管理网元的IP地址；
    所述拜访地策略控制网元根据所述终端设备的标识和所述拜访地会话管理网元的IP地址向所述拜访地会话管理网元发送所述终端设备的分流信息。
  17. 如权利要求16所述的方法，其特征在于，所述拜访地会话管理网元的标识为所述拜访地会话管理网元的实例的标识；
    所述拜访地策略控制网元根据所述拜访地会话管理网元的标识获取所述拜访地会话管理网元的IP地址，包括：
    所述拜访地策略控制网元向网络仓储功能网元发送所述拜访地会话管理网元的实例的标识；
    所述拜访地策略控制网元从所述网络仓储功能网元接收所述拜访地会话管理网元的IP地址。
  18. 如权利要求16所述的方法，其特征在于，所述拜访地会话管理网元的标识为所述拜访地会话管理网元的全限定域名；
    所述拜访地策略控制网元根据所述拜访地会话管理网元的标识获取所述拜访地会话管理网元的IP地址，包括：
    所述拜访地策略控制网元向域名系统发送所述拜访地会话管理网元的全限定域名；
    所述拜访地策略控制网元从所述域名系统接收所述拜访地会话管理网元的IP地址。
  19. 如权利要求15-18任一项所述的方法，其特征在于，还包括：
    所述拜访地策略控制网元向归属地策略控制网元发送请求消息，所述请求消息用于请求所述分流信息；
    所述拜访地策略控制网元从所述归属地策略控制网元接收所述分流信息。
  20. 如权利要求15-19任一项所述的方法，其特征在于，所述分流信息包括分流规则，应用标识，所述应用标识对应的数据探测规则，数据转发规则，带宽控制规则中的至少一项。
  21. 如权利要求15-20任一项所述的方法，其特征在于，还包括：
    所述拜访地策略控制网元从所述接入和移动性管理网元接收所述终端设备的IP地址；
    所述方法还包括：
    所述拜访地策略控制网元向拜访地引导服务网元发送注册消息，所述注册消息包括所述拜访地策略控制网元的实例的标识和所述终端设备的IP地址。
  22. 一种通信装置，其特征在于，包括处理器，所述处理器与存储器耦合：
    所述处理器，用于执行所述存储器中存储的计算机指令，以使得所述通信装置执行如权利要求1至21任一项所述的方法。
  23. 一种通信装置，其特征在于，包括处理器和接口电路，所述接口电路用于接收来自所述通信装置之外的其它通信装置的信号并传输至所述处理器或将来自所述处理器的信号发送给所述通信装置之外的其它通信装置，所述处理器通过逻辑电路或执行代码指令用于实现如权利要求1至21中任一项所述的方法。
  24. 一种计算机可读存储介质，其特征在于，所述存储介质中存储有计算机程序或指令，当所述计算机程序或指令被通信装置执行时，实现如权利要求1至21中任一项所述的方法。
  25. 一种包含程序指令的计算机程序产品，其特征在于，当所述程序指令在计算机上运行时，使得如权利要求1至21中任一项所述的方法被实现。
  26. 一种系统，其特征在于，包括：接入和移动性管理网元、策略控制网元和会话管理网元；
    所述接入和移动性管理网元用于执行如权利要求1至3中任一项所述的方法，所述会话管理网元用于执行如权利要求4至8中任一项所述的方法，所述策略控制网元用于执行如权利要求9至11中任一项所述的方法；或者
    所述接入和移动性管理网元用于执行如权利要求12至14中任一项所述的方法，所述 策略控制网元用于执行如权利要求15至21中任一项所述的方法。
PCT/CN2023/081154 2022-03-29 2023-03-13 一种通信方法及装置 WO2023185441A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN202210326193.4A CN116939574A (zh) 2022-03-29 2022-03-29 一种通信方法及装置
CN202210326193.4 2022-03-29

Publications (1)

Publication Number Publication Date
WO2023185441A1 true WO2023185441A1 (zh) 2023-10-05

Family

ID=88199034

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2023/081154 WO2023185441A1 (zh) 2022-03-29 2023-03-13 一种通信方法及装置

Country Status (2)

Country Link
CN (1) CN116939574A (zh)
WO (1) WO2023185441A1 (zh)

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20180270778A1 (en) * 2017-03-17 2018-09-20 Samsung Electronics Co., Ltd. Af influenced pdu session management and subscription procedures
CN109246769A (zh) * 2017-05-05 2019-01-18 华为技术有限公司 一种pdu会话建立方法及装置
CN110650504A (zh) * 2018-06-26 2020-01-03 华为技术有限公司 一种会话处理方法及装置
CN113613233A (zh) * 2017-10-17 2021-11-05 华为技术有限公司 一种确定pcf的方法、装置及系统

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20180270778A1 (en) * 2017-03-17 2018-09-20 Samsung Electronics Co., Ltd. Af influenced pdu session management and subscription procedures
CN109246769A (zh) * 2017-05-05 2019-01-18 华为技术有限公司 一种pdu会话建立方法及装置
CN113613233A (zh) * 2017-10-17 2021-11-05 华为技术有限公司 一种确定pcf的方法、装置及系统
CN110650504A (zh) * 2018-06-26 2020-01-03 华为技术有限公司 一种会话处理方法及装置

Also Published As

Publication number Publication date
CN116939574A (zh) 2023-10-24

Similar Documents

Publication Publication Date Title
CN109997334B (zh) 具有用于3gpp网络中物联网应用的间接连接的中继和收费的会话管理
EP3753226B1 (en) Security management in communication systems between security edge protection proxy elements
US11863983B2 (en) Provisioning of VLAN IDs in 5G systems
WO2022257549A1 (zh) 网络切片方法、设备及存储介质
CN110366131A (zh) 传输数据的方法和装置
WO2023280121A1 (zh) 一种获取边缘服务的方法和装置
CN111615844B (zh) 用于选择服务无线通信设备的会话管理实体的方法和装置
US20220240089A1 (en) Authorization for network function sets in communication system
WO2018137152A1 (zh) 短消息传输方法、设备和系统
WO2023051287A1 (zh) 一种通信方法及装置
WO2023072054A1 (zh) 切片服务获取方法及相关装置
CN112672336B (zh) 实现外部认证的方法、通信装置及通信系统
WO2023124875A1 (zh) 一种通信方法及装置
WO2022222745A1 (zh) 一种通信方法及装置
WO2023185441A1 (zh) 一种通信方法及装置
KR20210023299A (ko) 무선통신 시스템에서 네트워크 서비스를 노출하는 방법 및 장치
US10057871B2 (en) Data transmission method and base station
KR20230137998A (ko) Af 세션에 대한 외부 매개변수 프로비저닝을 위한 새로운 방법
US20220191008A1 (en) Communication network-anchored cryptographic key sharing with third-party application
WO2023087988A1 (zh) 一种通信方法、装置及设备
WO2024032290A1 (zh) 会话建立方法、装置、网络设备及存储介质
WO2023213215A1 (zh) 一种通信方法及装置
WO2023134630A1 (zh) 配置策略的方法和装置
WO2023020046A1 (zh) 一种通信方法及通信装置
WO2023179397A1 (zh) 一种授权方法及装置

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: 23777818

Country of ref document: EP

Kind code of ref document: A1