[go: up one dir, main page]

WO2025167748A1 - Procédé et appareil de détermination d'élément de réseau de plan utilisateur, et dispositif - Google Patents

Procédé et appareil de détermination d'élément de réseau de plan utilisateur, et dispositif

Info

Publication number
WO2025167748A1
WO2025167748A1 PCT/CN2025/074790 CN2025074790W WO2025167748A1 WO 2025167748 A1 WO2025167748 A1 WO 2025167748A1 CN 2025074790 W CN2025074790 W CN 2025074790W WO 2025167748 A1 WO2025167748 A1 WO 2025167748A1
Authority
WO
WIPO (PCT)
Prior art keywords
terminal
network element
management network
session
user plane
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Pending
Application number
PCT/CN2025/074790
Other languages
English (en)
Chinese (zh)
Inventor
孙晓姬
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Huawei Technologies Co Ltd
Original Assignee
Huawei Technologies Co Ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Huawei Technologies Co Ltd filed Critical Huawei Technologies Co Ltd
Publication of WO2025167748A1 publication Critical patent/WO2025167748A1/fr
Pending legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Classifications

    • 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
    • H04W76/00—Connection management
    • H04W76/10—Connection setup
    • H04W76/11—Allocation or use of connection identifiers
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W8/00—Network data management
    • H04W8/18—Processing of user or subscriber data, e.g. subscribed services, user preferences or user profiles; Transfer of user or subscriber data

Definitions

  • the present application relates to the field of data processing technology, and in particular to a method, apparatus and device for determining a user plane network element.
  • dual-transmit selective reception can be achieved by connecting both terminals in a pair to the wireless side, establishing two concurrent data links.
  • the data transmitter duplicates the data and sends it over two links (this is "dual transmission").
  • the two terminals in the pair ultimately converge at the same processing point responsible for dual-transmit selective reception.
  • the data receiver prioritizes the first-arrived data and discards the redundant data that arrives later (this is "selective reception").
  • dual-transmit selective reception has the following advantages:
  • Dual transmission means that even if a single link loses packets or fails, data is still backed up, ensuring uninterrupted services.
  • Selective collection means first-come, first-served, preferentially utilizing resources from two links to ensure low latency for services.
  • the embodiments of the present application provide a method, apparatus and device for determining a user plane network element, which is used to select two terminals in a paired terminal to the same UPF when multiple UPFs supporting dual-transmission and selective reception services are deployed.
  • an embodiment of the present application provides a method for determining a user plane function network element, which can be performed by a first session management network element. In this method:
  • the first session management network element may establish a session for the first terminal, and during the process of establishing the session for the first terminal, may determine the user plane function network element of the first terminal. Specifically, when determining the user plane function network element of the first terminal, the first session management network element may first determine the user plane function network element previously determined by the network side for the second terminal. Wherein, the pairing identifier of the first terminal is the same as the pairing identifier of the second terminal, that is, the first terminal and the second terminal are two terminals in a pair of paired terminals. The first session management network element may directly determine the user plane function network element of the second terminal as the target user plane function network element for the first terminal.
  • the first session management network element can determine the user plane function network element previously determined by the network side for the second terminal as the user plane function network element of the first terminal, thereby achieving the purpose of selecting the two terminals in the paired terminals to the same user plane function network element.
  • the first session management network element may first obtain the correspondence between the pairing identifier of the second terminal and the identifier of the user plane function network element of the second terminal (a first correspondence), and determine the user plane function network element of the second terminal through this correspondence.
  • the first session management network element can accurately obtain the user plane function network element previously determined by the network side for the second terminal by obtaining the correspondence between the pairing identifier of the second terminal and the identifier of the user plane function network element, thereby achieving the purpose of selecting the two terminals in the paired terminals to the same user plane function network element.
  • the first session management network element when the first session management network element obtains the correspondence between the pairing identifier of the second terminal and the identifier of the user plane function network element of the second terminal (target user plane function network element), the first session management network element may obtain the correspondence through two approaches.
  • the first approach is to obtain the correspondence locally from the first session management network element;
  • the second approach is to obtain the correspondence from the data management network element by interacting with the data management network element.
  • the first session management network element may send a contract information acquisition message to the data management network element to obtain the first contract information of the first terminal, and the data management network element may return the first contract information of the first terminal to the first session management network element.
  • the first contract information may include the correspondence between the pairing identifier of the second terminal and the identifier of the user plane function network element of the second terminal.
  • the first session management network element can quickly and accurately obtain the correspondence between the pairing identifier of the second terminal and the identifier of the user plane function network element of the second terminal, so that based on the correspondence, it can accurately obtain the user plane function network element previously determined by the network side for the second terminal, thereby achieving the purpose of selecting the two terminals in the paired terminals to the same user plane function network element.
  • the first session management network element when the first session management network element locally stores the correspondence between the pairing identifier of the second terminal and the identifier of the user plane function network element of the second terminal, it may be that in the process of establishing a session for the second terminal, the first session management network element randomly selects a user plane function network element, determines the user plane function network element as the user plane function network element of the second terminal, and stores the correspondence between the pairing identifier of the second terminal and the identifier of the user plane function network element.
  • the first session management network element can quickly, flexibly and accurately obtain the correspondence between the pairing identifier of the second terminal and the identifier of the target user plane function network element, and save the correspondence locally.
  • the first session management network element may also send a first registration message to the data management network element.
  • the first registration message includes the correspondence between the pairing identifier of the second terminal and the identifier of the first session management network element.
  • the data management network element may save the correspondence between the pairing identifier of the second terminal and the identifier of the first session management network element.
  • the data management network element can save the correspondence between the pairing identifier of the second terminal and the identifier of the first session management network element. Later, when the first terminal goes online, the access management network element of the first terminal can obtain the correspondence from the data management network element, so that the first terminal can also be selected to the first session management network element, so that the first terminal and the second terminal are both selected to the same session management network element.
  • the session management network element (first session management network element) can also determine the target user plane function network element previously determined for the second terminal as the target user plane function network element of the first terminal, thereby achieving the purpose of selecting the two terminals in the paired terminals to the same target user plane function network element.
  • the first session management network element may further send the pairing identifier of the first terminal to the target user plane function network element. Furthermore, the pairing identifier of the second terminal may also be sent to the target user plane function network element via the first session management network element or the second session management network element.
  • the target user plane functional network element can perform dual transmission, selective reception and forwarding processes on the message of the first terminal and the message of the second terminal according to the pairing identifier of the first terminal and the pairing identifier of the second terminal.
  • an embodiment of the present application provides a method for determining a user plane function network element, which can be performed by a first access management network element. In this method:
  • the first access management network element may register the first terminal.
  • the first access management network element may first determine a session management network element for the first terminal.
  • the first access management network element may first determine a session management network element previously determined by the network side for the second terminal.
  • the pairing identifier of the first terminal is the same as the pairing identifier of the second terminal, i.e., the first terminal and the second terminal are two terminals in a pair of paired terminals.
  • the first access management network element may directly determine the session management network element of the second terminal as the session management network element of the first terminal, so that both the first terminal and the second terminal are selected to the same session management network element.
  • the first access management network element when the first access management network element determines the session management network element of the second terminal, the first access management network element can obtain the correspondence between the pairing identifier of the second terminal and the identifier of the session management network element of the second terminal from the data management network element, and can determine the session management network element of the second terminal based on the correspondence.
  • beneficial effects of the second aspect and its various possible implementations can refer to the beneficial effects of the first aspect and its various possible implementations, and will not be repeated here.
  • embodiments of the present application provide a method for determining a user plane function network element, which can be performed by a data management network element.
  • the data management network element upon receiving a second registration message sent by a second session management network element, can obtain a correspondence between a pairing identifier of a second terminal and an identifier of a target user plane function network element included in the second registration message, and save the correspondence.
  • the beneficial effects of the third aspect can refer to the beneficial effects of the first aspect and its various possible implementation methods, and will not be repeated here.
  • the present application provides a method for determining a user plane function network element, which can be performed by a data management network element, wherein:
  • the data management network element can send a terminal re-online indication to the first access management network element or to the first session management network element, and the terminal re-online indication can be used to instruct the first terminal to be put back online.
  • the purpose of selecting the first terminal and the second terminal to the same user plane function network element can be achieved when the first terminal comes back online.
  • the terminal back online indication may carry the terminal identifier and the pairing identifier of the first terminal.
  • the first terminal can be quickly and accurately taken offline and put back online, so that during the process of the first terminal coming back online, the two terminals in the paired terminals can be quickly and accurately selected to the same target user plane functional network element.
  • the first session management network element can achieve the purpose of selecting the same target user plane function network element for the two paired terminals by changing the user plane function network element of the first terminal to the user plane function network element of the second terminal.
  • the present application provides a communication device comprising one or more processors configured to execute the method as described in any one of the first to fifth aspects.
  • the present application provides a computer-readable storage medium, which stores a computer program or instruction.
  • the computer program or instruction When executed by a communication device, it implements the method described in any one of the first to fifth aspects.
  • the present application provides a chip system, comprising: a memory for storing a computer program; a processor; when the processor calls and runs the computer program from the memory, the communication device equipped with the chip system executes any method described in any one of the first to fifth aspects.
  • a computer program product which, when called by a computer, enables the computer to execute any of the methods described in any of the first to fifth aspects.
  • FIG1 is a schematic diagram of a 5G communication system architecture
  • FIG2 is a schematic diagram of a communication system architecture applicable to an embodiment of the present application.
  • FIG3 is a flow chart of a method for determining a user plane function network element provided by the present application
  • FIG4 is a flow chart of a method for resolving a conflict between a session management network element of a first terminal and a session management network element of a second terminal provided by the present application;
  • FIG5 is a flow chart of a method for resolving a conflict between a user plane function network element of a first terminal and a user plane function network element of a second terminal provided by the present application;
  • FIG6 is a flow chart of another method for resolving a conflict between a user plane function network element of a first terminal and a user plane function network element of a second terminal provided by the present application;
  • FIG7 is a flow chart of a method for determining a user plane function network element of a second terminal provided by the present application
  • FIG8 is a schematic flow chart of a method for determining a user plane function network element of a first terminal provided by the present application
  • FIG9 is a flow chart of a method for resolving a conflict between an SMF of a first terminal and an SMF of a second terminal provided by the present application;
  • FIG10 is a flow chart of another method for determining the UPF of a second terminal provided by the present application.
  • FIG11 is a flow chart of another method for determining the UPF of a first terminal provided by the present application.
  • FIG12 is a flow chart of a method for resolving a conflict between a UPF of a first terminal and a UPF of a second terminal provided by the present application;
  • FIG13 is a flow chart of a method for making a first terminal offline and back online provided by the present application.
  • FIG14 is a flow chart of a second method for making a first terminal offline and back online provided by the present application.
  • FIG15 is a flowchart of a third method for making a first terminal offline and back online provided by the present application.
  • LTE long term evolution
  • FDD frequency division duplex
  • TDD LTE time division duplex
  • UMTS universal mobile telecommunication system
  • WiMAX world-wide interoperability for microwave access
  • 5G fifth generation
  • NR new radio
  • FIG 1 shows a schematic diagram of a 5G network architecture based on a service-oriented architecture (SA) proposed by the 3rd Generation Partnership Project (3GPP).
  • SA service-oriented architecture
  • 3GPP 3rd Generation Partnership Project
  • This 5G network architecture includes access network equipment and core network equipment. Terminals access the data network (DN) through these devices.
  • DN data network
  • Wireless terminals can be used in communication devices, wearable devices, drones, robots, terminals in D2D, terminals in vehicle to everything (V2X), virtual reality (VR) terminal devices, augmented reality (AR) terminal devices, wireless terminals in industrial control, wireless terminals in self-driving, wireless terminals in remote medical, wireless terminals in smart grid, wireless terminals in transportation safety, wireless terminals in smart city, wireless terminals in smart home or terminal devices in future communication networks, etc.
  • V2X virtual reality
  • VR virtual reality
  • AR augmented reality
  • wireless terminals in industrial control wireless terminals in self-driving
  • wireless terminals in remote medical wireless terminals in smart grid, wireless terminals in transportation safety, wireless terminals in smart city, wireless terminals in smart home or terminal devices in future communication networks, etc.
  • AMF, SMF and PCF can be combined together as a management device to complete access control and mobility management functions such as access authentication, security encryption, and location registration of terminal devices, as well as session management functions such as establishment, release and change of user plane transmission paths, as well as the function of analyzing some slice-related data (such as congestion) and terminal device-related data.
  • N1 interface The interface between AMF and UE, which can be used to transmit non-access stratum (NAS) signaling (such as QoS rules from AMF) to UE.
  • NAS non-access stratum
  • N2 interface The interface between AMF and RAN, which can be used to transmit radio bearer control information from the core network side to the RAN.
  • N3 interface The interface between RAN and UPF, mainly used to transmit uplink and downlink user plane data between RAN and UPF.
  • N4 interface The interface between SMF and UPF, which can be used to transmit information between the control plane and the user plane, including controlling the issuance of forwarding rules, QoS rules, traffic statistics rules, etc. for the user plane and reporting information on the user plane.
  • N6 interface The interface between UPF and DN, used to transmit uplink and downlink user data flows between UPF and DN.
  • the part shown in Figure 1 is only an exemplary architecture diagram.
  • the network architecture can also include other network elements or functional entities, which is not limited in the embodiments of the present application.
  • interface names between network elements in this application are merely exemplary, and the interfaces between network elements may also have other names.
  • the embodiments of this application do not limit the names of the interfaces.
  • the embodiments of the present application can be applied to future communication systems, such as 6G systems.
  • future communication systems such as 6G systems.
  • the names of terminal devices, access network devices, core network devices with sensing functions, and devices with other functions may change, and the embodiments of the present application do not limit this.
  • the following text uses the application of the embodiments of the present application in a 5G system as an example to introduce specific solutions.
  • the access management network element of the second terminal is called the second access management network element.
  • the access management network element registered for the second terminal is the second access management network element
  • the second access management network element serves the second terminal
  • the access management network element serving the second terminal is the second access management network element
  • the access management network element connected to the second terminal is the second access management network element.
  • the first access management network element and the second access management network element can be the same or different, and this application does not make any specific limitations on this.
  • the session management network element of the first terminal is called the first session management network element.
  • the session management network element registered for the first terminal is the first session management network element
  • the first session management network element serves the first terminal the session management network element serving the first terminal is the first session management network element
  • the session management network element connected to the first terminal is the first session management network element.
  • the session management network element of the second terminal can be the first session management network element or the second session management network element.
  • the session management network element of the second terminal is the first session management network element
  • the session management network element of the first terminal and the session management network element of the second terminal are the same session management network element.
  • the session management network element of the second terminal is the second session management network element
  • the session management network element of the first terminal and the session management network element of the second terminal are two different session management network elements.
  • the user plane function network element of the terminal can also be called: a user plane function network element registered for the terminal, a user plane function network element serving the terminal, a user plane function network element serving the terminal, or a user plane function network element connected to the terminal.
  • the methods provided in the various embodiments of the present application can be applied to the network architecture shown in Figure 1 or other network architectures.
  • the methods provided in the various embodiments of the present application can also be applied to the network architecture shown in Figure 2 or other network architectures.
  • the paired terminals can be customer premises equipment (CPE).
  • the first terminal and the second terminal can be CPE1 and CPE2 respectively.
  • the end-side networking can be connected to CPE1 and CPE2 respectively through a dual-transmitter and selective receiver switch.
  • the redundant central processing unit (CPU) can be connected to each module in the dual module group through the built-in dual module group of the industrial gateway.
  • the dual module group can be considered as a paired terminal.
  • the 5G LAN module 1 in the dual module group can be considered as the first terminal
  • the 5G LAN module 2 in the dual module group can be considered as the second terminal.
  • the two terminals in a paired terminal pair can access the wireless side through different frequencies through static configuration or network-assisted frequency selection, establishing two links that can transmit data concurrently.
  • Multiple user plane function network elements that support dual transmission and selective reception can be deployed in 2B industrial parks, such as the first user plane function network element (UPF1) and the second user plane function network element (UPF2).
  • the two terminals in the same pair of paired terminals need to be registered (selected) with the same user plane function network element.
  • Different pairs of paired terminals can be registered with the same user plane function network element or with different user plane function network elements.
  • control plane network element may be an SMF, AMF, etc.
  • the user plane network element may be a UPF, etc.
  • the data service network element may be a UDR, UDM, NRF, USDF, etc.
  • the embodiments of the present application take the SMF as the session management network element, the AMF as the access management network element, the UPF as the user plane function network element, and the UDM as the data management network element as an example to explain the method for determining the user plane function network element provided in the present application.
  • Step 301 A first access management network element sends a session establishment request message to a first session management network element.
  • the session establishment request message may include a terminal identifier of a first terminal.
  • the session establishment request message is used to request establishment of a session for the first terminal.
  • the first terminal may initiate a registration request (Register Request) message, which may carry the terminal identifier of the first terminal (also referred to as the user identifier of the first terminal).
  • a registration request (Register Request) message, which may carry the terminal identifier of the first terminal (also referred to as the user identifier of the first terminal).
  • the first access management network element After receiving the first registration request message from the first terminal, the first access management network element registers the first terminal. When registering the first terminal, the first access management network element may first determine a session management network element for the first terminal. When determining the session management network element for the first terminal, the first access management network element may use the session management network element of the second terminal as the session management network element for the first terminal (applicable to the case where the second terminal registers before the first terminal), or may randomly determine a session management network element for the first terminal.
  • the first method is to use the session management network element of the second terminal as the session management network element of the first terminal.
  • the data management network element when any terminal initiates a registration request message, during the process of registering the terminal, the data management network element will save the correspondence between the pairing identifier of the terminal and the session management network element of the terminal. Therefore, the first access management network element can obtain the correspondence between the pairing identifier of the second terminal and the identifier of the first session management network element saved in the data management network element by interacting with the data management network element (for convenience of description, this correspondence is referred to as a second correspondence), and based on the second correspondence, obtain (learn) the session management network element previously determined by the network side for the second terminal.
  • the following describes a process in which the data management network element stores the correspondence between the pairing identifier of the terminal and the session management network element of the terminal, taking the second terminal as an example:
  • Step 0 The second terminal initiates a registration request message to the second access management network element.
  • Step 1 After receiving the registration request message, the second access management network element randomly determines a session management network element for the second terminal.
  • the session management network element of the second terminal saves the correspondence between the pairing identifier of the second terminal and the identifier of the user plane function network element of the second terminal (for convenience of description, this correspondence is referred to as a first correspondence).
  • Step 3 The session management network element of the second terminal initiates a first registration message to the data management network element.
  • the first registration message may include a second correspondence between the pairing identifier of the second terminal and the identifier of the first session management network element of the second terminal.
  • the first registration message can be used to notify the data management network element of the information of the first session management network element of the second terminal, so that the data management network element can save the second correspondence.
  • Step 4 After receiving the first registration message, the data management network element saves the second corresponding relationship.
  • the data management network element can save the second correspondence in the session of the second terminal.
  • the data management network element can also synchronously save the second correspondence in the session information of the first terminal, so that when the first terminal subsequently comes online, the second correspondence can be directly sent to the access management network element of the first terminal (the first access management network element).
  • the data management network element saves the second correspondence between the pairing identifier of the second terminal and the identifier of the first session management network element of the second terminal.
  • the first access management network element can initiate (send) a registration request message (hereinafter referred to as the second registration request message for the convenience of description) to the data management network element.
  • the second registration request message can carry the terminal identifier of the first terminal.
  • the second registration request message can be used to obtain the contract information of the first terminal (hereinafter referred to as the second contract information for the convenience of description), such as obtaining the contract information of the session of the first terminal.
  • the data management network element After the data management network element receives the second registration request message, it can first perform security authentication on the first terminal, such as determining whether the terminal identification of the first terminal is included in the pre-saved security terminal list. If it is included, the first terminal can be considered to be a safe device, and the security authentication result of the first terminal is passed. Otherwise, the first terminal can be considered not to be a safe device, and the security authentication result of the first terminal is failed.
  • the data management network element can then determine whether it has a second correspondence between the pairing identifier of the first terminal (which can also be understood as the pairing identifier of the second terminal) and the identifier of the first session management network element stored locally, such as determining whether there is a second correspondence in the locally stored session information of the first terminal. If so, it can be considered that the second terminal has been online, and the network side (such as the second access management network element) has previously determined a session management network element for the second terminal. The data management network element can then return the second subscription information containing the second correspondence to the first access management network element. Based on the second correspondence contained in the second subscription information, the first access management network element can obtain (learn) that the session management network element previously determined by the network side for the second terminal is the first session management network element.
  • the first access management network element may directly determine the first session management network element as the session management network element of the first terminal.
  • the above-mentioned method for the first access management network element to obtain the session management network element of the second terminal is only an example.
  • the first access management network element may also send an inquiry message to any other access management network element to inquire whether the session management network element has been determined for the terminal with the pairing identifier (the second terminal). If any other access management network element has previously determined the session management network element for the terminal with the pairing identifier, then the other access management network element may send the identifier of the session management network element determined for the terminal with the pairing identifier (the second terminal) to the first access management network element, and the first access management network element may obtain the session management network element of the second terminal based on this.
  • the embodiment of the present application does not limit the method for the first access management network element to obtain the session management network element of the second terminal.
  • the second method is to randomly determine a session management network element for the first terminal.
  • the first access management network element may randomly select a session management network element as the session management network element of the first terminal.
  • Step 302 After receiving the session establishment request message, the first session management network element can determine, based on the session establishment request, the user plane function network element (target user plane function network element) that serves the first terminal after the session is established.
  • the first session management network element can, when the pairing identifier of the first terminal is the same as the pairing identifier of the second terminal, determine the user plane function network element of the second terminal as the target user plane function network element of the first terminal, that is, the target user plane function network element of the first terminal is the same as the user plane function network element of the second terminal.
  • the first session management network element may determine a target user plane function network element for the first terminal.
  • the target user plane function network element for the first terminal in order to ensure that the user plane function network element of the first terminal and the user plane function network element of the second terminal are the same user plane function network element, that is, in order to select the first terminal and the second terminal to the same user plane function network element, the first session management network element may first determine (obtain) the user plane function network element of the second terminal.
  • the first session management network element may first obtain a first correspondence relationship that can represent the correspondence between the pairing identifier of the second terminal and the identifier of the user plane function network element of the second terminal, thereby quickly and accurately determining the user plane function network element of the second terminal based on the pairing identifier of the second terminal and the first correspondence relationship.
  • the first session management network element may obtain the first correspondence relationship in two ways, which are described below:
  • Method 1 The first session management network element obtains the first corresponding relationship stored (saved) locally.
  • the first session management network element has the function of storing the first correspondence.
  • the first session management network element can determine the user plane function network element of the second terminal and locally store the first correspondence between the pairing identifier of the second terminal and the identifier of the user plane function network element of the second terminal. Therefore, when the first session management network element determines the target user plane function network element for the first terminal that came online later, it can obtain the first correspondence from its own local machine.
  • the session management network element of the second terminal is the same as the session management network element of the first terminal (the first session management network element), that is, the session management network element of the first terminal and the session management network element of the second terminal are both the first session management network element.
  • the first session management network element can further select the first terminal and the second terminal to the same user plane function network element.
  • the first session management network element does not obtain the first corresponding relationship locally, it can be considered that either the second terminal has not yet come online, and the first terminal is the first terminal to go online among the paired terminals, so the first corresponding relationship has not yet been stored, or the session management network element of the second terminal is not the first session management network element, and the session management network element of the first terminal and the session management network element of the second terminal are not the same session management network element.
  • this situation is referred to as a conflict between the session management network element of the first terminal and the session management network element of the second terminal.
  • the session management network element determined for the first terminal is referred to as the first session management network element
  • the session management network element determined for the second terminal is referred to as the second session management network element.
  • the situation where the session management network element of the first terminal and the session management network element of the second terminal are found to conflict may be discovered by the data management network element.
  • the present application provides a method for resolving the conflict. Please refer to Figure 4, which is a flow chart of a method provided by the present application for resolving the conflict between the session management network element of the first terminal and the session management network element of the second terminal.
  • the process mainly includes the following steps:
  • Step 401 The first session management network element sends a registration message (first registration message) including a correspondence between a pairing identifier of a first terminal and an identifier of the first session management network element to a data management network element.
  • Step 402 The second session management network element also sends a registration message (third registration message) including the correspondence between the pairing identifier of the second terminal and the identifier of the second session management network element to the data management network element.
  • Step 403 The data management network element identifies, based on the contents of the first registration message and the third registration message, that the pairing identifier of the first terminal is the same as the pairing identifier of the second terminal, but the first session management network element of the first terminal is different from the second session management network element of the second terminal.
  • the data management network element may send a terminal re-online indication to the first access management network element or send a terminal re-online indication to the first session management network element.
  • the terminal re-online indication may be used to instruct the first terminal to be put back online.
  • the data management network element recognizes that the pairing identifier of the first terminal in the first registration message is the same as the pairing identifier of the second terminal in the third registration message, but the first session management network element and the second session management network element are different, it can be considered that the network side has connected (determined) the two terminals with the same pairing identifier to different session management network elements, and a conflict occurs between the session management network elements of the first terminal and the second terminal. To resolve this conflict, the first terminal and the second terminal are connected to the same session management network element.
  • the data management network element can send a terminal re-online indication to the access management network element of either the first terminal or the second terminal, or the data management network element can send a terminal re-online indication to the session management network element of either the first terminal or the second terminal.
  • the terminal re-online indication can be used to instruct the corresponding terminal to go back online. Therefore, during the terminal re-online process, the terminal can be treated as the terminal that comes online later.
  • the session management network element of the terminal that comes online earlier can be re-determined based on the session management network element of the terminal that comes online earlier, thereby connecting both terminals in the paired terminals to the same session management network element.
  • the data management network element sends a terminal re-online indication to the first access management network element or the first session management network element of the first terminal.
  • the terminal re-online indication can carry the terminal identifier and pairing identifier of the first terminal.
  • the first access management network element or the first session management network element After the first access management network element or the first session management network element receives the terminal re-online indication, it can initiate an offline operation of the session of the first terminal and instruct the first terminal to go back online.
  • the first session management network element randomly determines a user plane function network element for the first terminal and also randomly determines a user plane function network element for the second terminal.
  • the user plane function network element determined for the first terminal is different from the user plane function network element determined for the second terminal, then the first terminal and the second terminal are selected to different user plane function network elements.
  • this situation is referred to as a conflict between the user plane function network element of the first terminal and the user plane function network element of the second terminal.
  • the first terminal and the second terminal are selected to the same user plane function network element.
  • the embodiment of the present application provides the following solution. Please refer to Figure 5, which is a flow chart of a method provided by the present application for resolving a conflict between the user plane function network element of the first terminal and the user plane function network element of the second terminal. The process mainly includes the following steps:
  • Step 501 The first session management network element randomly determines a first user plane function network element as the user plane function network element of a first terminal.
  • the first session management network element randomly determines a second user plane function network element as the user plane function network element of a second terminal.
  • Step 502 The first session management network element recognizes that the user plane function network element determined for the first terminal (first user plane function network element) is different from the user plane function network element determined for the second terminal (second user plane function network element), and changes the user plane function network element of the first terminal to the user plane function network element of the second terminal.
  • the first session management network element identifies that the user plane function network element determined for the first terminal is different from the user plane function network element determined for the second terminal, it can be considered that the first terminal and the second terminal have been selected for different user plane function network elements, and the user plane function network element determined for the first terminal and the user plane function network element determined for the second terminal can be adjusted to the same user plane function network element.
  • the user plane function network element of the first terminal can be changed to the user plane function network element of the second terminal, that is, the user plane function network element of the first terminal and the user plane function network element of the second terminal both determine the second user plane function network element.
  • the second user plane function network element of the second terminal can also be changed to the user plane function network element of the first terminal, that is, the user plane function network element of the first terminal and the user plane function network element of the second terminal both determine the first user plane function network element.
  • This application does not specifically limit this.
  • the first terminal and the second terminal are both selected to the same session management network element (such as the first session management network element), in order to ensure to the greatest extent possible that the two terminals with the same pairing identifier can be selected to the same user plane function network element, when the first session management network element needs to determine the user plane function network element for any terminal (such as the first terminal), it can first determine whether the terminals for which the user plane function network element currently needs to be determined include a terminal with the same pairing identifier as the terminal (such as the second terminal). If so, the two terminals with the same pairing identifier can be selected to the same user plane function network element, thereby ensuring to the greatest extent possible that the two terminals with the same pairing identifier are selected to the same user plane function network element.
  • Method 2 The first session management network element obtains the first corresponding relationship from the data management network element by interacting with the data management network element.
  • the first session management network element may not have the function of storing (saving) the first corresponding relationship, while the data management network element has the function of storing the first corresponding relationship.
  • the data management network element can also synchronously save the first correspondence in the session information of the first terminal, so that when the first terminal goes online later, the first correspondence is sent to the access management network element (first access management network element) of the first terminal, so that the first access management network element can obtain the first correspondence.
  • the first session management network element when the first session management network element obtains the first corresponding relationship from the data management network element based on the second method, it can be considered that the first session management network element does not locally store the first corresponding relationship.
  • the first session management network element needs to obtain the first corresponding relationship from the data management network element, and then determine (obtain) the user plane function network element of the second terminal based on the first corresponding relationship and the pairing identifier of the second terminal, thereby determining the user plane function network element of the second terminal as the target user plane function network element of the first terminal, thereby selecting the first terminal and the second terminal to the same user plane function network element.
  • FIG. 6 is another method flow diagram provided by the present application for resolving the conflict between the user plane function network element of the first terminal and the user plane function network element of the second terminal.
  • the process mainly includes the following steps:
  • Step 602 The second session management network element sends a registration message (referred to as a fifth registration message for ease of description) including a correspondence between the pairing identifier of the second terminal and the identifier of the second user plane function network element to the data management network element.
  • a registration message (referred to as a fifth registration message for ease of description) including a correspondence between the pairing identifier of the second terminal and the identifier of the second user plane function network element to the data management network element.
  • Step 603 Based on the contents of the fourth registration message and the fifth registration message, the data management network element identifies that the pairing identifier of the first terminal is the same as the pairing identifier of the second terminal, but the user plane function network element of the first terminal (the first user plane function network element) is different from the user plane function network element of the second terminal (the second user plane function network element).
  • the data management network element sends a terminal re-online indication to the first access management network element or to the first session management network element.
  • the terminal re-online indication can be used to instruct the first terminal to be put back online.
  • the data management network element can send a terminal re-online indication to the access management network element of any one of the first terminal and the second terminal, or the data management network element can also send a terminal re-online indication to the session management network element of any one of the first terminal and the second terminal.
  • the terminal re-online indication can be used to instruct the corresponding terminal to be put back online, so that in the process of the terminal coming back online, the terminal can be used as the terminal that comes online later, and the user plane function network element of the terminal that comes online later can be re-determined according to the user plane function network element of the terminal that comes online first, so that the two terminals in the paired terminals are selected to the same user plane function network element.
  • the UPF determination method provided in this application is explained below using a specific embodiment.
  • This embodiment can be understood as determining the SMF of the first terminal based on the SMF previously determined for the second terminal. By selecting the first and second terminals to the same SMF, the SMF can select the first and second terminals to the same UPF.
  • Step 701 When a second terminal comes online, it initiates a Registration Request message.
  • This Registration Request message can be used to request that the second terminal itself be registered with the network.
  • the Registration Request message carries the second terminal's terminal identifier (also known as the second terminal's user identifier).
  • the wireless (base station) can randomly select an AMF (a second AMF) for the second terminal and send the Registration Request message to the second AMF.
  • Step 702 After receiving the registration request message, the second AMF can initiate a registration request message to the UDM.
  • This registration request message can be used to register the second AMF of the second terminal with the UDM, so that the UDM can store the correspondence between the identifiers of the second terminal and the second AMF.
  • the registration request message can also be used to obtain the contract information of the second terminal.
  • the registration request message carries the terminal identifier of the second terminal.
  • the UDM performs security authentication on the second terminal. The process of performing security authentication on the second terminal is similar to the security authentication process for the first terminal in the above embodiment and is not repeated here.
  • Step 703 When the UDM completes the security authentication of the second terminal and the security authentication result of the second terminal is passed, the UDM can determine whether the correspondence between the pairing identifier of the second terminal and the identifier of the SMF is stored locally. At this time, the second terminal is the first terminal to go online in the paired terminals, and the UDM has not yet saved the correspondence between the pairing identifier of the second terminal and the identifier of the SMF (first SMF). The UDM can return the contract information of the second terminal to the second AMF.
  • the contract information may include the pairing identifier of the second terminal.
  • the contract information does not include the correspondence between the pairing identifier of the second terminal and the identifier of the SMF (first SMF).
  • Step 704 After the second AMF receives the contract information of the second terminal returned by the UDM, it can be considered that the registration of the second terminal is completed, and a registration accept (Register Accept) message can be returned to the second terminal.
  • the registration accept message is used to respond to the registration request message initiated by the terminal.
  • Step 705 After the second terminal receives the registration acceptance message returned by the second AMF, it can return a registration completion message to the second AMF.
  • the registration completion message can be used to indicate that the terminal has completed registration.
  • Step 706 The second terminal may initiate a session establishment request message (such as a PDU Session Establishment Request).
  • the session establishment request message may be used to request the establishment of a session (PDU session) for the second terminal.
  • the session establishment request message may carry the terminal identifier of the second terminal.
  • the session establishment request message may also carry information related to the second terminal, such as DNN, S-NSSAI, and PDU type.
  • Step 707 After receiving the session establishment request message from the second terminal, the second AMF can query whether the second terminal's contract information received from the UDM contains SMF selection subscription data for the second terminal's pairing identifier. In other words, it queries whether the second terminal's contract information contains a correspondence between the second terminal's pairing identifier and the identifier of the SMF (the first SMF). Since the second terminal's contract information does not contain this correspondence, it can be assumed that the second terminal is the first of the paired terminals to go online.
  • the second AMF can randomly select (register) an SMF for the second terminal. For ease of description, the SMF selected for the second terminal is referred to as the first SMF.
  • Step 708 The second AMF sends (initiates) a session establishment request (Nsmf_PDUSession_CreateSMContext Request) message to the first SMF.
  • the session establishment request message can be used to instruct the first SMF to establish a session for the second terminal.
  • the session establishment request message can include the terminal identifier of the second terminal.
  • the session establishment request message can also carry information such as the DNN, S-NSSAI, and PDU type of the second terminal.
  • Step 710 After receiving the contract information acquisition message, the UDM may return the contract information of the second terminal's session to the first SMF.
  • the contract information may include the pairing identifier of the second terminal.
  • Step 711 After the first SMF receives the contract information of the second terminal returned by the UDM, it can return a session establishment response (Nsmf_PDUSession_CreateSMContext Response) message to the second AMF.
  • the session establishment response message is used to indicate that the session of the second terminal has been established.
  • Step 712 After the first SMF receives the contract information including the pairing identifier of the second terminal returned by the UDM, since the second terminal is the first terminal to go online in the paired terminals, the first SMF has not yet locally saved the first correspondence between the pairing identifier of the second terminal and the identifier of the UPF of the second terminal.
  • the first SMF can randomly select a UPF as the UPF of the second terminal.
  • the first SMF can save the first correspondence between the pairing identifier of the second terminal and the identifier of the UPF of the second terminal. That is, the first SMF can determine the UPF of the second terminal and save the first correspondence in the process of establishing a session for the second terminal. At this point, the first correspondence is saved in the first SMF.
  • the first SMF may send a Packet Forwarding Control Protocol (PFCP) session establishment request message to the target UPF via the N4 interface.
  • PFCP Packet Forwarding Control Protocol
  • the PFCP session establishment request message may be used to instruct the UPF to establish session resources for the second terminal.
  • the PFCP session establishment request message may carry the terminal identifier, pairing identifier, and session group identifier of the second terminal. Similar to the pairing identifier, the terminal's session group identifier may also be pre-assigned to the terminal by the network side, which will not be repeated here.
  • Step 714 After the UPF of the second terminal receives the PFCP session establishment request message sent by the first SMF, it can establish the session resources of the second terminal. After the session resources of the second terminal are established, the UPF of the second terminal can return a PFCP session establishment response message (Session Establishment Response) to the first SMF.
  • the PFCP session establishment response message can indicate that the session resources of the second terminal have been established.
  • the UPF of the second terminal can record the pairing identifier of the second terminal and session information such as the session and session group identifier of the second terminal. Subsequently, the UPF can perform dual-transmission selective forwarding on the session of the two terminals (the first terminal and the second terminal) in the pairing identifier based on the recorded pairing identifier and session information.
  • Step 715 The first SMF may return a transfer message (eg, Namf_Communication_N1N2_message_transfer) to the second AMF.
  • the transfer message may be used to indicate that the session of the second terminal has been established.
  • Step 716 After the second AMF receives the transmission message sent by the first SMF, it can return a session establishment acceptance message (such as a PDU session establishment accept message) to the second terminal.
  • the session establishment acceptance message is used to inform the terminal that the session has been established.
  • Step 717 The second AMF sends a session modification request message (such as Nsmf_PDUSession_UpdateSMContext Request message) to the first SMF.
  • the session modification request message can instruct the first SMF to update the base station side resources to the UPF.
  • Step 718 The first SMF sends a session modification request message to the UPF of the second terminal.
  • the session modification request message can be used to indicate the update of the tunnel information allocated by the UPF on the base station side.
  • Step 719 After the UPF of the second terminal updates the tunnel information allocated by the UPF on the base station side, it can return a session modification response message to the first SMF.
  • the session modification response message is used to indicate that the tunnel information allocated by the UPF on the base station side has been updated.
  • Step 720 After receiving the session modification response message returned by the UPF of the second terminal, the first SMF initiates a registration message (such as a Nudm_UECM_Registration message, referred to as a first registration message for ease of description) to the UDM.
  • the first registration message may include the correspondence between the second terminal's pairing identifier and the identifier of the first SMF (the second correspondence).
  • the first registration message can be used to notify the UDM of the information of the first SMF of the second terminal, so that the UDM can save the second correspondence.
  • the first registration message may also include the second terminal's user permanent identifier (SUPI), DNN, S-NSSAI, PDU session identifier (PDU session id), etc.
  • SUPI user permanent identifier
  • DNN DNN
  • S-NSSAI S-NSSAI
  • PDU session identifier PDU session identifier
  • Step 721 After receiving the first registration message, the UDM may save the second corresponding relationship.
  • the UDM can save the second correspondence to the session of the second terminal.
  • the UDM can also save the second correspondence to the session information of the first terminal, so that when the first terminal goes online later, the second correspondence can be sent to the AMF of the first terminal (the first AMF), so that the first AMF can determine the first SMF as the SMF of the first terminal, so that the SMF of the first terminal and the SMF of the second terminal can be selected as the same SMF, thereby ensuring that the first SMF can select the UPF of the first terminal and the UPF of the second terminal as the same UPF.
  • the second correspondence is saved in the UDM.
  • Step 722 The first SMF may return a session update response message (such as Nsmf_PDUSession_UpdateSMContext Response message) to the second AMF.
  • the session update response message may be used to indicate that the baseline side resources have been updated.
  • step 720-step 721 can be executed first, and then step 722 can be executed, or step 722 can be executed first, and then step 720-step 721 can be executed, or step 720 and step 722 can be executed simultaneously in parallel.
  • the process of determining the user plane function network element of the first terminal in FIG8 mainly includes the following steps:
  • Step 801 Similar to step 701, when a first terminal comes online, the first terminal initiates a registration request message (first registration request message).
  • This registration request message can be used to request that the first terminal itself be registered with the network.
  • the registration request message carries the terminal identifier of the first terminal.
  • the wireless (base station) receives the registration request message initiated by the first terminal, it can randomly select an AMF (first AMF) for the first terminal and send the registration request message to the first AMF.
  • first AMF AMF
  • Step 802 Similar to step 702, after receiving the registration request message, the first AMF can initiate a registration request message (a second registration request message) to the UDM.
  • This registration request message can be used to register the first AMF of the first terminal with the UDM, so that the UDM can store the correspondence between the identifiers of the first terminal and the first AMF.
  • the registration request message can also be used to obtain the contract information of the first terminal.
  • the registration request message carries the terminal identifier of the first terminal and can be used to obtain the contract information of the first terminal.
  • the UDM performs security authentication on the first terminal.
  • Step 803 When the UDM completes the security authentication of the first terminal and the security authentication result of the first terminal is passed, the UDM can determine whether it has locally saved the correspondence between the pairing identifier of the first terminal and the identifier of the SMF. Since the second terminal is already online, the second correspondence between the pairing identifier of the second terminal (that is, the pairing identifier of the first terminal) and the identifier of the first SMF saved by the UDM, the UDM can include the second correspondence in the contract information of the first terminal (the second contract information) and return it to the first AMF. Based on this, the first AMF can obtain the SMF of the second terminal based on the second correspondence and the pairing identifier of the second terminal.
  • Step 804 Similar to step 704, after the first AMF receives the subscription information of the first terminal returned by the UDM, it can be considered that the registration of the first terminal is completed, and a registration acceptance message can be returned to the first terminal.
  • the registration acceptance message is used to respond to the registration request message initiated by the terminal.
  • Step 805 Similar to step 705, after the first terminal receives the registration acceptance message returned by the first AMF, it can return a registration completion message to the first AMF.
  • the registration completion message can be used to indicate that the terminal has completed registration.
  • Step 806 Similar to step 706, the first terminal may initiate a session establishment request message, which may be used to request the establishment of a session (PDU session) for the first terminal.
  • the session establishment request message may carry the terminal identifier of the first terminal.
  • the session establishment request message may also carry information related to the first terminal, such as DNN, S-NSSAI, and PDU type.
  • Step 807 After the first AMF receives the session establishment request message from the first terminal, it can query whether the contract information (second contract information) of the first terminal received from the UDM contains the selected subscription data of the SMF of the pairing identifier of the first terminal, that is, query whether the contract information (second contract information) of the first terminal contains the second correspondence between the pairing identifier of the second terminal and the identifier of the SMF (first SMF).
  • the first AMF finds that the contract information of the first terminal contains the second correspondence, the first AMF can know that the SMF of the second terminal is the first SMF based on the second correspondence and the pairing identifier of the second terminal, and therefore can select the first SMF as the SMF of the first terminal.
  • Step 808 Similar to step 708, the first AMF sends (initiates) a session establishment request message to the first SMF.
  • the session establishment request message may include the terminal identifier of the first terminal.
  • the session establishment request message may also carry information such as the DNN, S-NSSAI, and PDU type of the first terminal.
  • the session establishment request message is used to instruct the first SMF to establish a session for the first terminal.
  • Step 809 Similar to step 709, after the first SMF receives the session establishment request message sent by the first AMF, it can interact with the UDM. For example, the first SMF sends a contract information acquisition message to the UDM.
  • the contract information acquisition message includes the terminal identifier of the first terminal.
  • the contract information acquisition message can be used to obtain the contract information of the session of the first terminal.
  • Step 810 Similar to step 710, after receiving the contract information acquisition message, the UDM may return the contract information (first contract information) of the session of the first terminal to the first SMF.
  • the contract information may include the pairing identifier of the first terminal.
  • Step 811 Similar to step 711, after the first SMF receives the contract information of the first terminal returned by the UDM, it can return a session establishment response message to the first AMF.
  • the session establishment response message is used to indicate that the session of the first terminal has been established.
  • Step 812 After the first SMF receives the signing information including the pairing identifier of the first terminal returned by the UDM, it can check whether the correspondence between the pairing identifier of the second terminal and the identifier of the UPF of the second terminal is stored locally. Since the first SMF has previously determined the UPF for the second terminal, the first SMF locally stores the correspondence between the pairing identifier of the second terminal and the identifier of the UPF of the second terminal (first correspondence). The first SMF can obtain (learn) the UPF of the second terminal based on the locally stored first correspondence and the pairing identifier of the second terminal, and can directly determine the UPF of the second terminal as the target UPF of the first terminal.
  • Step 813 Similar to step 713, the first SMF may send a PFCP session establishment request message to the UPF.
  • the PFCP session establishment request message may carry the terminal identifier, pairing identifier, and session group identifier of the first terminal.
  • Step 814 Similar to step 714, after the target UPF receives the PFCP session establishment request message sent by the first SMF, it can establish the session resources of the first terminal. After the session resources of the first terminal are established, the target UPF can return a PFCP session establishment response message to the first SMF. The PFCP session establishment response message can indicate that the session resources of the first terminal have been established.
  • the target UPF can record the pairing identifier of the first terminal and the session information of the first terminal, such as the session and session group identifier. Subsequently, the target UPF can perform dual-send selective forwarding on the session of the two terminals (the first terminal and the second terminal) in the pairing identifier based on the recorded pairing identifier and session information, which will not be repeated here.
  • Step 815 Similar to step 715, the first SMF may return a transfer message (eg, Namf_Communication_N1N2_message_transfer) to the first AMF.
  • the transfer message may be used to indicate that the session of the first terminal has been established.
  • Step 816 Similar to step 716, after receiving the transmission message, the first AMF may return a session establishment acceptance message to the first terminal.
  • the session establishment acceptance message is used to inform the terminal that the session has been established.
  • Step 817 Similar to step 717, the first AMF may send a session modification request message to the first SMF, which may instruct the first SMF to update the base station side resources to the target UPF.
  • Step 818 Similar to step 718, the first SMF sends a session modification request message to the target UPF.
  • the session modification request message can be used to indicate the update of the tunnel information allocated by the UPF on the base station side.
  • Step 819 Similar to step 719, after the target UPF updates the tunnel information allocated by the UPF on the base station side, it can return a session modification response message to the first SMF.
  • the session modification response message is used to indicate that the tunnel information allocated by the UPF on the base station side has been updated.
  • Step 820 Similar to step 720, after receiving the session modification response message from the target UPF, the first SMF initiates a registration message to the UDM.
  • This registration message may include the correspondence between the first terminal's pairing identifier and the identifier of the first SMF. This registration message can be used to notify the UDM of the information of the first terminal's first SMF, allowing the UDM to save the correspondence between the first terminal's pairing identifier and the identifier of the first SMF.
  • the registration message may also include the first terminal's SUPI, DNN, S-NSSAI, PDU session ID, etc. Since the second terminal came online earlier than the first terminal, the UDM had already saved the second correspondence when the second terminal came online (in step 720). Therefore, step 820 is optional.
  • Step 821 Similar to step 722, the first SMF may return a session update response message to the first AMF.
  • the two paired terminals, the first terminal and the second terminal can subsequently implement processes such as dual-transmission selective reception and forwarding based on the same UPF.
  • the first SMF has the function of saving the first correspondence between the pairing identifier of the second terminal and the identifier of the UPF of the second terminal, and in step 812, if the first SMF does not obtain the first correspondence locally, it can be considered that either the second terminal has not yet come online, and the first terminal is the first terminal to come online in the paired terminals, so the first correspondence has not yet been saved, or it is because the first terminal and the second terminal may have come online at the same time, resulting in the first terminal and the second terminal being regarded as the first terminal to come online (the first terminal), and their respective SMFs are randomly determined for the first terminal and the second terminal, respectively.
  • the SMF of the second terminal is not the first SMF, and the SMF of the first terminal and the SMF of the second terminal are not the same SMF, and a conflict occurs between the SMF of the first terminal and the SMF of the second terminal.
  • Figure 9 is a flow chart of a method provided by the present application for resolving the conflict between the SMF of the first terminal and the SMF of the second terminal. The process mainly includes the following steps:
  • Step 900 includes the online process of the second terminal described in steps 701 to 720 in Figure 7. Unlike Figure 7, the online process of the second terminal in Figure 9 can replace the first SMF in steps 701 to 720 in Figure 7 with the second SMF, and the first registration message with the third registration message. In addition, step 900 also includes the online process of the first terminal.
  • the online process of the first terminal can refer to steps 701 to 720 in Figure 7. Unlike Figure 7, the online process of the first terminal in step 900 replaces the second terminal in steps 701 to 720 in Figure 7 with the first terminal, and the second AMF with the first AMF.
  • Step 901 When the UDM recognizes that the pairing identifier of the first terminal in the first registration message is the same as the pairing identifier of the second terminal in the third registration message, but the first SMF is different from the second SMF, the UDM sends a terminal re-online indication to the first AMF or to the first SMF, and the terminal re-online indication carries the terminal identifier and pairing identifier of the first terminal.
  • Step 902 After receiving the terminal back-online indication, the first AMF or the first SMF may initiate a session offline operation for the first terminal and instruct the first terminal to come back online.
  • the process of determining the UPF for the first terminal may be repeated according to the process in Figure 8. That is, the process of determining the UPF for the second terminal may be repeated according to the process in Figure 7, and the process of determining the UPF for the first terminal may be repeated according to the process in Figure 8, thereby ensuring that the same UPF is selected for the first and second terminals. This will not be repeated here.
  • the UPF determination method provided in this application is explained below using a specific embodiment.
  • This embodiment can be understood as follows: even if the first terminal and the second terminal are not selected to the same SMF, the network side can also determine the UPF of the first terminal based on the UPF previously determined for the second terminal, thereby achieving the selection of the first terminal and the second terminal to the same UPF.
  • Figure 10 is a flowchart of another method for determining the UPF of a second terminal provided by this application
  • Figure 11 is a flowchart of another method for determining the UPF of a first terminal provided by this application.
  • the process of determining the UPF of the second terminal in Figure 10 mainly includes the following steps:
  • Step 1001 - Step 1002 Please refer to Step 701 - Step 702 in Figure 7 above, and no further details will be given here.
  • Step 1003 When the UDM completes the security authentication of the second terminal and the security authentication result of the second terminal is passed, the UDM may return the contract information of the second terminal to the second AMF.
  • the contract information may not include the pairing identifier of the second terminal.
  • Step 1004 - Step 1006 Please refer to Step 704 - Step 706 in FIG. 7 , which will not be described in detail here.
  • Step 1007-Step 1011 Similar to Step 707-711 in Figure 7, except that the first SMF in Step 707-711 needs to be replaced by the second SMF, which will not be repeated here.
  • Step 1012 is similar to step 712 in FIG. 7 , except that the first SMF in step 712 needs to be replaced by the second SMF, and the second SMF in step 1012 does not save the first correspondence, while the first SMF in step 712 saves the first correspondence.
  • Step 1013 to step 1019 are similar to step 713 to step 719 in FIG. 7 , except that the first SMF in step 713 to step 719 needs to be replaced by the second SMF.
  • Step 1020 The second SMF initiates a registration message to the UDM.
  • the registration message may include the first correspondence between the second terminal's pairing identifier and the identifier of the second terminal's UPF.
  • the registration message may be used to notify the UDM of the second terminal's UPF information so that the UDM can store the first correspondence.
  • the registration message may include the second terminal's SUPI, DNN, S-NSSAI, PDU session ID, and other information.
  • Step 1021 After receiving the registration message, the UDM saves the first correspondence.
  • the UDM can save the first correspondence in the session of the second terminal.
  • the UDM can also save the first correspondence in the session information of the first terminal, so that when the first terminal subsequently comes online, the first correspondence can be sent to the SMF of the first terminal (the first SMF), so that the first SMF can know the UPF of the second terminal and then select the UPF of the first terminal and the UPF of the second terminal as the same UPF.
  • Step 1022 is similar to step 722 in FIG. 7 , except that the first SMF in step 722 needs to be replaced by the second SMF.
  • the process of determining the user plane function network element of the first terminal in FIG11 mainly includes the following steps:
  • Step 1101 - Step 1102 Please refer to Step 801 - Step 802 in Figure 8 above, and no further details will be given here.
  • Step 1103 is similar to step 1003 in FIG10 , except that the second terminal in step 1003 needs to be replaced by the first terminal, which will not be described again here.
  • Step 1104 - Step 1106 Please refer to Step 804 - Step 806 in FIG. 8 , which will not be described in detail here.
  • Step 1107 The first AMF randomly selects an SMF for the first terminal.
  • the SMF selected for the first terminal is referred to as the first SMF.
  • Step 1108 - Step 1111 Please refer to Step 808 - Step 811 in the aforementioned FIG8 , which will not be repeated here.
  • Step 1112 The first SMF interacts with the UDM, and the first SMF obtains a first corresponding relationship from the UDM.
  • Step 1113 - Step 1119 Please refer to Step 813 - Step 819 in FIG. 8 , which will not be repeated here.
  • Step 1120 is similar to step 1020 in FIG10 , except that the second terminal in step 1020 needs to be replaced by the first terminal, and the second SMF needs to be replaced by the first SMF, which will not be repeated here.
  • step 1120 is an optional step.
  • Step 1121 Please refer to step 821 in Figure 8 above, which will not be repeated here.
  • the first terminal and the second terminal are respectively regarded as the terminals that go online first (first terminal), and their respective UPFs are randomly determined for the first terminal and the second terminal, and the UPF determined by the network side (such as the first SMF) for the first terminal is the first UPF, and the UPF determined by the network side (such as the second SMF) for the second terminal is the second UPF, when the first UPF and the second UPF are different, it can be considered that a conflict has occurred between the UPF of the first terminal and the UPF of the second terminal.
  • Figure 12 is a flow chart of a method provided by the present application for resolving the conflict between the UPF of the first terminal and the UPF of the second terminal. The process mainly includes the following steps:
  • Step 1200 includes the online process of the second terminal described in steps 1001 to 1020 in Figure 10. Unlike Figure 10, in the online process of the second terminal in Figure 12, the UPF in steps 1001 to 1020 in Figure 10 may be replaced with the second UPF, and the registration message in step 1020 may be replaced with the fifth registration message. Furthermore, step 900 also includes the online process of the first terminal. The online process of the first terminal may refer to steps 1001 to 1020 in Figure 10.
  • the second terminal in steps 1001 to 1020 in Figure 10 may be replaced with the first terminal, the second AMF may be replaced with the first AMF, the target UPF may be replaced with the first UPF, and the registration message in step 1020 may be replaced with the fourth registration message.
  • Step 1201 When the UDM recognizes that the pairing identifier of the first terminal in the fourth registration message is the same as the pairing identifier of the second terminal in the fifth registration message, but the first UPF in the fourth registration message is different from the second UPF in the fifth registration message, the UDM sends a terminal re-online indication to the first AMF or to the first SMF, and the terminal re-online indication carries the terminal identifier and pairing identifier of the first terminal.
  • Step 1202 After receiving the terminal back-online indication, the first AMF or the first SMF may initiate a session offline operation for the first terminal and instruct the first terminal to come back online.
  • the process of determining the UPF for the first terminal may be repeated according to the process in Figure 11. That is, the process of determining the UPF for the second terminal may be repeated according to the process in Figure 10, and the process of determining the UPF for the first terminal may be repeated according to the process in Figure 11, thereby ensuring that the same UPF is selected for the first and second terminals. This will not be repeated here.
  • the following describes how the first terminal can be put back online after the first AMF and the first SMF receive the terminal back online instruction.
  • the embodiment of the present application provides three ways to make the first terminal offline and back online.
  • the first method of making the first terminal offline and back online UDM sends a terminal back online instruction to the first SMF.
  • the process includes the following steps:
  • Step 1301 UDM sends a terminal re-online indication to the first SMF, and the terminal re-online indication includes a session release request, which is used to instruct the first SMF to release the session of the first terminal.
  • the terminal re-online indication may carry the terminal identifier, pairing identifier, etc. of the first terminal.
  • Step 1302 The first SMF selects the session of the first terminal according to the correspondence between the session and the terminal identifier and the pairing identifier, and sends (initiates) a session release request (Session Release Request) message to the first UPF corresponding to the first terminal determined previously.
  • the session release request message is used to indicate the release of the session of the first terminal.
  • Step 1303 After receiving the session release request message, the first UPF can perform the session release process for the first terminal. After releasing the session, the first UPF returns a session release response (Session Release Response) message to the first SMF.
  • the session release response message is used to indicate that the session of the first terminal has been released.
  • Step 1304 The first SMF sends a transfer message (e.g., Namf_Communication_N1N2_message_transfer) to the first AMF.
  • the transfer message is used to indicate the deletion (release) of the session of the first terminal.
  • the transfer message may also carry a reconnection instruction (Reattach indication), which may be used to instruct the first terminal to re-initiate a session establishment request message after releasing the corresponding session.
  • Step 1305 After receiving the transmission message, the first AMF initiates a session release request message (such as PDU session Release Request) to the first terminal.
  • the session release request message may carry the above-mentioned reconnection instruction.
  • the session release request is used to instruct the terminal to release the session, and the reconnection instruction is used to instruct the first terminal to re-initiate a session establishment request message after releasing the corresponding session.
  • Step 1306 After receiving the session release request message, the first terminal can delete the corresponding session and return a session release confirmation message (such as a PDU session Release Ack message) to the first AMF through the base station.
  • the session release confirmation message can be used to indicate (represent) that the corresponding session has been deleted.
  • Step 1307 The first terminal re-initiates a session establishment request message according to the reconnection instruction carried in the session release request message.
  • the first terminal can serve as the terminal that came online later in the paired terminal and go back online through the relevant steps in Figure 8 (e.g., steps 806-821), ensuring that the same UPF is selected as the second terminal.
  • the process of determining the UPF for the second terminal is performed according to the process in Figure 7, and the process of determining the UPF for the first terminal is performed according to the process in Figure 8, thereby ensuring that the first and second terminals are selected to the same UPF. This will not be repeated here.
  • UDM sends a terminal back online indication to the first AMF.
  • the process includes the following steps:
  • Step 1401 UDM sends a terminal re-online indication to the first AMF.
  • the terminal re-online indication may be a deregistration notification (such as DeregistrationNotification).
  • the deregistration reason (deregReason) in the deregistration notification may be, for example, re-registration (such as REREGISTRATION_REQUIRED).
  • the deregistration notification may be used to instruct the first AMF to re-initiate the registration (registration) process of the terminal.
  • Step 1402 The first AMF initiates a deregistration request message to the first terminal based on the deregistration notification received from the UDM.
  • the deregistration request message may carry a deregistration reason, such as reregistration (e.g., REREGISTRATION_REQUIRED).
  • Step 1403 The first AMF sends a resource deletion indication to the first SMF, which can be used to instruct the first SMF to delete resources such as the session corresponding to the first terminal.
  • Step 1404 The first terminal sends a Deregister Accept message to the first AMF.
  • the Deregister Accept message is used to indicate that the first terminal has completed the deregistration process.
  • Step 1405 The first terminal re-initiates a registration request message.
  • the first terminal can be the terminal that goes online later in the paired terminal, and can go online again through the relevant steps in Figure 8 (such as steps 801 to 821) or through the relevant steps in Figure 11 (such as steps 1101 to 1121) to achieve selection of the same UPF as the second terminal.
  • the process of determining the UPF for the second terminal is performed according to the process in Figure 7, and the process of determining the UPF for the first terminal is performed according to the process in Figure 8, thereby ensuring that the first terminal and the second terminal are selected to the same UPF.
  • the process of determining the UPF for the second terminal can be performed according to the process in Figure 10, and the process of determining the UPF for the first terminal can be performed according to the process in Figure 11, thereby ensuring that the first terminal and the second terminal are selected to the same UPF. This will not be repeated here.
  • the third method for taking the first terminal offline and back online is similar to the second method in that the UDM sends a terminal back online instruction to the first AMF. The difference is that:
  • the process includes the following steps:
  • Step 1501 The UDM sends a terminal re-online indication to the first AMF.
  • the terminal re-online indication may be a dual-send selective reception repair (Restoration) request message.
  • the dual-send selective reception repair request message carries the pairing identifier of the first terminal and the terminal identifier of the first terminal.
  • Step 1502 After the first AMF receives the dual-transmission selective reception repair request message initiated by the UDM, the first AMF sends a session release request (Namf_PDUSession_ReleaseSMContext Request) message to the first SMF.
  • the session release request message is used to instruct the SMF to release the terminal session.
  • the session release request message carries the pairing identifier of the first terminal and the terminal identifier of the first terminal.
  • Step 1503 After the first SMF receives the session release request message (also called the session deletion request message), it can select the session of the first terminal according to the pairing identifier and terminal identifier of the first terminal, and initiate a session release request (Session Release Request) message to the first UPF.
  • the session release request message is used to instruct the UPF to release the session of the first terminal.
  • Step 1504 After receiving the session release request message, the first UPF releases the session of the first terminal and returns a session release response (Session Release Response) message to the first SMF.
  • the session release response message is used to indicate that the session of the first terminal has been released.
  • Step 1505 The first SMF returns a session release response message (such as Namf_PDUSession_ReleaseSMContext Response message) to the first AMF.
  • the session release response message is used to indicate that the session of the first terminal has been released.
  • Step 1506 The first SMF sends a transfer message (e.g., Namf_Communication_N1N2_message_transfer) to the first AMF.
  • the transfer message can be used to instruct the first terminal to delete (release) the session.
  • the transfer message can carry a reconnection instruction (Reattach indication), which can be used to instruct the first terminal to release the corresponding session and then re-initiate session establishment.
  • Step 1507 The first AMF sends a session release request message (such as a PDU session Release Request message) to the first terminal.
  • the session release request message may carry the above-mentioned reconnection instruction.
  • the session release request is used to instruct the terminal to release the session, and the reconnection instruction is used to instruct the first terminal to re-initiate a session establishment request message after releasing the corresponding session.
  • Step 1508 After receiving the session release request message, the first terminal can delete the corresponding session and return a session release confirmation message (such as PDU session Release Ack message) to the first AMF through the base station.
  • the session release confirmation message can be used to indicate (represent) that the corresponding session has been deleted.
  • Step 1509 The first terminal re-initiates a registration request message according to the reconnection instruction carried in the session release request message.
  • the first terminal can be the terminal that goes online later in the paired terminal, and can go online again through the relevant steps in Figure 8 (such as steps 801 to 821) or through the relevant steps in Figure 11 (such as steps 1101 to 1121), so as to be selected to the same UPF as the second terminal.
  • the process of determining the UPF for the second terminal is performed according to the process in Figure 7, and the process of determining the UPF for the first terminal is performed according to the process in Figure 8, so as to ensure that the first terminal and the second terminal are selected to the same UPF.
  • the process of determining the UPF for the second terminal can be performed according to the process in Figure 10
  • the process of determining the UPF for the first terminal can be performed according to the process in Figure 11, so as to ensure that the first terminal and the second terminal are selected to the same UPF. No further details will be given here.
  • the terminal equipment, the control plane network element, and the data service network element include hardware structures and/or software modules corresponding to the execution of each function. It should be readily apparent to those skilled in the art that, in combination with the units and method steps of each example described in the embodiments disclosed in this application, the present application can be implemented in the form of hardware or a combination of hardware and computer software. Whether a function is executed in hardware or in a manner driven by computer software depends on the specific application scenario and design constraints of the technical solution.
  • Figures 16 and 17 are schematic diagrams of possible communication devices provided in embodiments of the present application. These communication devices can be used to implement the functions of the session management network element, access management network element, and data management network element in the method embodiments shown in any of Figures 3 to 15 above, thereby also achieving the beneficial effects of the above method embodiments.
  • the communication device 1600 includes a processing unit 1610 and a transceiver unit 1620.
  • the communication device 1600 is used to implement the functions of the first session management network element or the first access management network element in the method embodiment shown in Figure 3 above.
  • the communication device 600 is used to implement the functions of the second terminal, the second AMF, the UDM, the first SMF, and the UPF in the method embodiment shown in Figure 7 above.
  • the transceiver unit 1620 can execute the receiving and sending actions performed by each network element/device in the above method embodiment.
  • the processing module 1610 can execute other actions, except for the sending and receiving actions, among the actions performed by each network element/device in the above method embodiment.
  • the transceiver unit 1620 is used to receive a session establishment request message; the processing unit 1610 is used to determine the target user plane function network element for the first terminal based on the session establishment request message.
  • processing unit 1610 and the transceiver unit 1620 can be directly obtained by referring to the relevant description in the method embodiment shown in any of Figures 3 to 15, and will not be repeated here.
  • communication device 1700 includes a processor 1710 and an interface circuit 1720.
  • Processor 1710 and interface circuit 1720 are coupled to each other.
  • interface circuit 1720 can be a transceiver or an input/output interface.
  • communication device 1700 may also include a memory 1730 for storing instructions executed by processor 1710, input data required by processor 1710 to execute instructions, or data generated by processor 1710 after executing instructions.
  • the processor 1710 is used to implement the functions of the above-mentioned processing unit 1610, and the interface circuit 1720 is used to implement the functions of the above-mentioned transceiver unit 1620.
  • the chip When the communication device is a chip used in the first session management network element, the chip implements the functions of the first session management network element in the above method embodiment.
  • the chip receives information from other modules in the first session management network element; or the chip sends information to other modules in the first session management network element.
  • the module When the communication device is a module applied to the first terminal, the module implements the functions of the first terminal in the above method embodiment.
  • the module receives information from other modules in the first terminal; alternatively, the module sends information to other modules.
  • the module can be the baseband chip of the first terminal, or a DU or other module.
  • the DU can be a DU in an open radio access network (O-RAN) architecture.
  • OF-RAN open radio access network
  • processors in the embodiments of the present application may be a central processing unit (CPU), or may be other general-purpose processors, digital signal processors (DSP), application-specific integrated circuits (ASIC), field programmable gate arrays (FPGA), or other programmable logic devices, transistor logic devices, hardware components, or any combination thereof.
  • the general-purpose processor may be a microprocessor or any conventional processor.
  • a communication device which includes at least one processor and at least one memory, the at least one processor and the at least one memory being coupled together, the at least one memory being used to store instructions.
  • the communication device performs the method in the above-described embodiment.
  • a communication device 1700 includes a processor 1710 and a memory 1730. The processor 1710 and the memory 1730 are coupled together, and the memory 1730 stores instructions.
  • the communication device 1700 performs the method performed by the terminal device or network device in the above-described embodiment.
  • the method steps in the embodiments of the present application can be implemented in hardware or in software instructions that can be executed by a processor.
  • the software instructions can be composed of corresponding software modules, and the software modules can be stored in random access memory, flash memory, read-only memory, programmable read-only memory, erasable programmable read-only memory, electrically erasable programmable read-only memory, registers, hard disk, mobile hard disk, CD-ROM or any other form of storage medium well known in the art.
  • An exemplary storage medium is coupled to the processor so that the processor can read information from the storage medium and write information to the storage medium.
  • the storage medium can also be an integral part of the processor.
  • the processor and storage medium can be located in an ASIC.
  • the ASIC can be located in a network device or a terminal.
  • the processor and storage medium can also exist in a network device or a terminal as discrete components.
  • all or part of the embodiments may be implemented using software, hardware, firmware, or any combination thereof.
  • all or part of the embodiments may be implemented in the form of a computer program product.
  • the computer program product includes one or more computer programs or instructions. When the computer program or instructions are loaded and executed on a computer, the processes or functions described in the embodiments of the present application are performed in whole or in part.
  • the computer may be a general-purpose computer, a special-purpose computer, a computer network, a network device, a user device, or other programmable device.
  • the computer program or instructions may be stored in a computer-readable storage medium or transferred from one computer-readable storage medium to another.
  • the computer program or instructions may be transferred from one website, computer, server, or data center to another website, computer, server, or data center via wired or wireless means.
  • the computer-readable storage medium may be any available medium that can be accessed by a computer or a data storage device such as a server or data center that integrates one or more available media.
  • the available medium may be a magnetic medium, such as a floppy disk, hard disk, or magnetic tape; an optical medium, such as a digital video disk; or a semiconductor medium, such as a solid-state drive.
  • the computer-readable storage medium may be a volatile or nonvolatile storage medium, or may include both volatile and nonvolatile types of storage media.
  • At least one means one or more, and “more” means two or more.
  • “And/or” describes the association relationship of associated objects, indicating that three relationships may exist.
  • a and/or B can mean: A exists alone, A and B exist at the same time, and B exists alone, where A and B can be singular or plural.
  • the character “/” generally indicates that the previous and next associated objects are in an “or” relationship; in the formula of this application, the character “/” indicates that the previous and next associated objects are in a “division” relationship.
  • “Including at least one of A, B and C” can mean: including A; including B; including C; including A and B; including A and C; including B and C; including A, B and C.

Landscapes

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

Abstract

La présente demande concerne un procédé et un appareil de détermination d'élément de réseau de plan utilisateur, et un dispositif. Dans le procédé : lorsqu'un premier élément de réseau de gestion de session reçoit un message de demande d'établissement de session envoyé par un premier élément de réseau de gestion d'accès, le premier élément de réseau de gestion de session peut effectuer un processus d'établissement d'une session pour un premier terminal, et, dans le processus d'établissement de la session pour le premier terminal, peut déterminer une fonction de plan utilisateur cible du premier terminal. Lors de la détermination de la fonction de plan utilisateur du premier terminal, le premier élément de réseau de gestion de session peut apprendre une fonction de plan utilisateur déterminée précédemment pour un second terminal par un côté réseau. Un identifiant d'appariement du premier terminal est le même qu'un identifiant d'appariement du second terminal, c'est-à-dire que le premier terminal et le second terminal sont deux terminaux dans une paire de terminaux appariés, et le premier élément de réseau de gestion de session peut déterminer directement la fonction de plan utilisateur du second terminal en tant que fonction de plan utilisateur cible du premier terminal, de sorte que l'objectif d'amener les deux terminaux parmi les terminaux appariés à sélectionner une même fonction de plan utilisateur est atteint.
PCT/CN2025/074790 2024-02-09 2025-01-24 Procédé et appareil de détermination d'élément de réseau de plan utilisateur, et dispositif Pending WO2025167748A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN202410179162.X 2024-02-09
CN202410179162.XA CN120475549A (zh) 2024-02-09 2024-02-09 一种用户面网元确定方法、装置及设备

Publications (1)

Publication Number Publication Date
WO2025167748A1 true WO2025167748A1 (fr) 2025-08-14

Family

ID=96631022

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2025/074790 Pending WO2025167748A1 (fr) 2024-02-09 2025-01-24 Procédé et appareil de détermination d'élément de réseau de plan utilisateur, et dispositif

Country Status (2)

Country Link
CN (1) CN120475549A (fr)
WO (1) WO2025167748A1 (fr)

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN115209398A (zh) * 2021-04-13 2022-10-18 华为技术有限公司 一种报文传输方法及装置
WO2023042124A1 (fr) * 2021-09-15 2023-03-23 Telefonaktiebolaget Lm Ericsson (Publ) Redondance de plan utilisateur entre un équipement utilisateur et une fonction de plan utilisateur
CN116887420A (zh) * 2023-07-17 2023-10-13 中国电信股份有限公司技术创新中心 数据发送方法、装置、电子设备及计算机可读存储介质
WO2023247300A1 (fr) * 2022-06-24 2023-12-28 Robert Bosch Gmbh Système de communication, plus particulièrement système 5g

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN115209398A (zh) * 2021-04-13 2022-10-18 华为技术有限公司 一种报文传输方法及装置
WO2023042124A1 (fr) * 2021-09-15 2023-03-23 Telefonaktiebolaget Lm Ericsson (Publ) Redondance de plan utilisateur entre un équipement utilisateur et une fonction de plan utilisateur
WO2023247300A1 (fr) * 2022-06-24 2023-12-28 Robert Bosch Gmbh Système de communication, plus particulièrement système 5g
CN116887420A (zh) * 2023-07-17 2023-10-13 中国电信股份有限公司技术创新中心 数据发送方法、装置、电子设备及计算机可读存储介质

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
DAN WANG, CHINA MOBILE: "Support of Replication and elimination for redundancy transmission for FRER", 3GPP DRAFT; S2-2400171; TYPE DRAFTCR; TEI19, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. SA WG2, no. Online; 20240122 - 20240129, 12 January 2024 (2024-01-12), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France, XP052554008 *

Also Published As

Publication number Publication date
CN120475549A (zh) 2025-08-12

Similar Documents

Publication Publication Date Title
US11864103B2 (en) Network slicing method and device, and storage medium
JP7760698B2 (ja) 通信方法および装置
CN111586771B (zh) 网络节点选择方法及装置
CN110366216B (zh) 通信的方法和通信装置
WO2022017285A1 (fr) Procédé, appareil et système d'acheminement de paquets
US20240244107A1 (en) Method for determining application server
WO2023020046A1 (fr) Procédé de communication et appareil de communication
CN115884152A (zh) 通信的方法和装置
US20250048070A1 (en) Communication method and communication apparatus
CN115915091A (zh) 通信的方法和装置
CN111465034A (zh) 网络配置的方法和通信装置
CN115884153A (zh) 通信的方法和装置
CN116349293A (zh) Iab节点的移植方法及装置
WO2023143212A1 (fr) Procédé et appareil de communication
CN116390203A (zh) 选择网络的方法和装置
EP4539549A1 (fr) Procédé de communication, appareil de communication et système de communication
US12185422B2 (en) Communication method and apparatus
WO2025167748A1 (fr) Procédé et appareil de détermination d'élément de réseau de plan utilisateur, et dispositif
US20240388887A1 (en) Communication method and related apparatus
US12507290B2 (en) Authorization method, apparatus and system for authorizing relay service relationships between remote and relay terminals using policy control function devices
US20240381457A1 (en) Communication method and apparatus
US20230029714A1 (en) Authorization method, policy control function device, and access and mobility management function device
WO2024193166A1 (fr) Procédé et appareil de communication
WO2025065568A1 (fr) Procédé de gestion de tâche, appareil de communication et système de communication
WO2025166784A1 (fr) Procédé de communication sans fil, équipement terminal et dispositif de réseau cœur

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

Country of ref document: EP

Kind code of ref document: A1