WO2023116556A1 - Procédé et appareil de commutation de session - Google Patents

Procédé et appareil de commutation de session Download PDF

Info

Publication number
WO2023116556A1
WO2023116556A1 PCT/CN2022/139449 CN2022139449W WO2023116556A1 WO 2023116556 A1 WO2023116556 A1 WO 2023116556A1 CN 2022139449 W CN2022139449 W CN 2022139449W WO 2023116556 A1 WO2023116556 A1 WO 2023116556A1
Authority
WO
WIPO (PCT)
Prior art keywords
session
network element
access technology
identifier
address
Prior art date
Application number
PCT/CN2022/139449
Other languages
English (en)
Chinese (zh)
Inventor
汪洋
于游洋
宗在峰
Original Assignee
华为技术有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 华为技术有限公司 filed Critical 华为技术有限公司
Publication of WO2023116556A1 publication Critical patent/WO2023116556A1/fr

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/14—Session management
    • H04L67/141—Setup of application sessions
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W12/00—Security arrangements; Authentication; Protecting privacy or anonymity
    • H04W12/06—Authentication
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/14—Reselecting a network or an air interface

Definitions

  • the present application relates to the technical field of communications, and more specifically, to a method and device for session handover.
  • a terminal device establishes a session after connecting to the network, and accesses the external data network through the session, and interacts with the application server deployed in the data network.
  • session handover may occur, such as session handover from a 3rd generation partnership project (3rd generation partnership project, 3GPP) access technology to a non-3GPP access technology.
  • 3rd generation partnership project 3rd generation partnership project, 3GPP
  • wireless local area network wireless local access network
  • WLAN wireless local access network
  • N5CW Non-5G-Capable over WLAN
  • the present application provides a method and device for session switching, which can enable the session switching of a terminal device from a 3GPP access technology to a non-3GPP access technology.
  • a method for session handover is provided.
  • the method may be executed by a mobility management network element, or may also be executed by a component (such as a chip or a circuit) of the mobility management network element, which is not limited.
  • a component such as a chip or a circuit
  • the execution by the mobility management network element is taken as an example for description below.
  • the method may include: the mobility management network element receives a first message from the interoperability function network element, the first message is used to instruct to switch the session of the terminal device, and the session is a session established through the first access technology; the mobility management network element determines the session The associated session management network element; the mobility management network element sends a second message to the session management network element, and the second message is used to indicate that the session is switched from the first access technology to the second access technology; wherein, the terminal device is through Terminal equipment that does not support non-access stratum NAS signaling when the second access technology accesses the core network.
  • the mobility management network element when the mobility management network element receives the first message from the interoperability function network element, and learns that the session of the terminal device is switched, the mobility management network element determines the session management network element associated with the session, and reports to the session management network element associated with the session.
  • the network element sends a second message, which is used to instruct to switch the session from the first access technology to the second access technology, so that the session can be switched from the first access technology to the second access technology by the session management network element associated with the session.
  • Incoming technology switching such as updating the session ID by the session management network element associated with the session, or sending a message to update the session ID by the session management network element associated with the session, and so on.
  • the mobility management network element determines the session management network element associated with the session, and the session management network element associated with the session executes the handover of the session from the first access technology to the second access technology, which can realize cross- The session switching process of the access technology, that is, the switching of the session from the first access technology to the second access technology.
  • the mobility management network element determines the session management network element associated with the session according to the first identifier of the session.
  • the first message includes an address of the session, and the address is an address allocated when the session is established through the first access technology; the mobility management network element determines the session management network associated with the session The element includes: the mobile management network element obtains the first identifier of the session according to the address of the session, and the first identifier of the session is the session identifier when the session is established through the first access technology; the mobility management network element obtains the first identifier of the session according to the first identifier of the session, Determine the session management network element associated with the session.
  • the mobility management network element can obtain the session identifier when the session is established through the first access technology according to the address allocated for the session (or terminal device) when the session is established through the first access technology, and then according to This identifier determines the session management network element associated with the session.
  • the mobility management network element obtains the first identifier of the session according to the address of the session, including: the mobility management network element sends a query message, and the query message includes the address of the session; The management network element receives the response message, and the response message includes the first identifier of the session.
  • the mobility management network element can send information to other core network network elements (such as policy control network elements, or binding The specified support network element) queries the session identifier when the session is established through the first access technology.
  • core network network elements such as policy control network elements, or binding The specified support network element
  • the mobility management network element obtains the first identifier of the session according to the session address, including: the mobility management network element determines the session ID according to the session address and the first association relationship The first identifier of the session, wherein the first association relationship includes the relationship between the address of the session and the first identifier of the session.
  • the mobility management network element may combine the first association relationship (that is, the address of the session with the first identifier of the session) according to the address allocated to the session (or terminal device) when the session is established through the first access technology
  • the association relationship between the relationships determines the session identifier when the session is established through the first access technology.
  • the method further includes: when establishing a session through the first access technology, the mobility management network element receives the address of the session from the session management network element; the mobility management network element receives the address of the session according to The address of the session establishes a first association relationship in the context information of the terminal device.
  • the mobility management network element may receive from the session management network element the address assigned to the session (or terminal device) when the session is established through the first access technology during the session establishment process, and establish the first The association relationship, so that the session identifier when the session is established through the first access technology can be subsequently determined according to the association relationship.
  • the method before the mobility management network element establishes the first association relationship in the context information of the terminal device, the method further includes: the mobility management network element determines that the terminal device is Terminal equipment that does not support NAS signaling when the ingress technology accesses the core network.
  • the mobile management network element can establish the above-mentioned first association relationship after determining that the terminal device is a terminal device that does not support NAS signaling when accessing the core network through the second access technology, which can reduce the number of establishments for all terminal devices.
  • the overhead brought by the above-mentioned first association relationship can be established after determining that the terminal device is a terminal device that does not support NAS signaling when accessing the core network through the second access technology, which can reduce the number of establishments for all terminal devices.
  • the first message includes session-associated slice information and/or a data network name; the mobility management network element determines the session-associated session management network element, including: the mobility management network The element determines the session management network element associated with the session according to the slice information and/or data network name associated with the session.
  • the mobility management network element may determine the session management network element associated with the session according to the slice information and/or data network name associated with the session.
  • the first message includes the second identifier of the session;
  • the mobility management network element determining the session management network element associated with the session includes: the mobility management network element The identifier and the second association relationship determine the first identifier of the session, and the second association relationship includes the relationship between the first identifier of the session and the second identifier of the session;
  • the mobility management network element determines the session-associated A session management network element; wherein, the first identifier of the session is the session identifier when the session is established through the first access technology, and the second identifier of the session is the session identifier when the session is established through the second access technology.
  • the mobility management network element may combine the second association relationship (that is, the association relationship between the first identifier of the session and the second identifier of the session) according to the session identifier when the session is established through the second access technology, Determine the session identifier when the session is established through the first access technology, and then determine the session management network element associated with the session.
  • the second association relationship that is, the association relationship between the first identifier of the session and the second identifier of the session
  • the method further includes: when establishing a session through the first access technology, the mobility management network element receives the second identifier of the session from the session management network element; the mobility management network The element establishes a second association relationship in the context information of the terminal device according to the second identifier of the session.
  • the mobility management network element can receive the session identifier when the session is established through the second access technology from the session management network element, and establish the second association relationship, so that the subsequent association can be based on the association relationship
  • a session identifier is determined when the session is established via the first access technology.
  • the method before the mobility management network element establishes the second association relationship in the context information of the terminal device, the method further includes: the mobility management network element determines that the terminal device is Terminal equipment that does not support NAS signaling when the ingress technology accesses the core network.
  • the mobile management network element can establish the above-mentioned second association relationship after determining that the terminal device is a terminal device that does not support NAS signaling when accessing the core network through the second access technology, which can reduce the number of establishments for all terminal devices.
  • the second identifier of the session is a default value.
  • the second identifier of the session is 15.
  • the mobility management network element determines that the terminal device is a terminal device that does not support NAS signaling when accessing the core network through the second access technology, including: the mobility management network element Receive indication information from the terminal device, where the indication information is used to indicate that the terminal device is a terminal device that does not support NAS signaling when accessing the core network through the second access technology.
  • the mobility management network element may determine, according to the instruction of the terminal device, that the terminal device is a terminal device that does not support NAS signaling when accessing the core network through the second access technology.
  • the first message includes one or more of the following: request type, address of the session, and access type, where the address is that the session is established through the first access technology address assigned at the time.
  • the second message includes one or more of the following: request type, session address, access type, and access technology type, where the address is An address assigned when the access technology is established.
  • the interoperability function network element is a trusted wireless local area network interoperation function network element.
  • the first access technology is a 3GPP access technology
  • the second access technology is a non-3GPP access technology
  • a method for session switching is provided.
  • the method may be executed by a terminal device, or may also be executed by a chip or a circuit used for a terminal device.
  • This application does not limit this.
  • the following is described by The implementation of the terminal device is taken as an example for description.
  • the method may include: the terminal device establishes a session through the first access technology; the terminal device sends a request message to the network element of the interoperability function, the request message includes address information, and the address information is used to indicate switching the session; 2. Terminal equipment that does not support non-access stratum NAS signaling when the access technology accesses the core network.
  • the terminal device sends a request message to the network element with the interoperability function, and the address information included in the request message can be used to instruct switching the session.
  • the address information is an address of the session, and the address is an address allocated when the session is established through the first access technology.
  • the method further includes: the terminal device receives a response message of the request message from the interoperability function network element, the response message includes address information; the terminal device receives the response message according to the address information included in the response message The information is the same as the address information included in the request message, and it is determined that the session switching is successful.
  • the address information included in the response message of the request message sent by the network element with the interoperability function to the terminal device can be used to indicate that the session handover is successful.
  • the method further includes: the terminal device sends indication information to the session management network element and/or the mobility management network element , the indication information is used to indicate that the terminal device is a terminal device that does not support NAS signaling when accessing the core network through the second access technology.
  • the terminal device may indicate to the session management network element and/or the mobility management network element that the terminal device is a terminal device that does not support NAS signaling when accessing the core network through the second access technology.
  • the request message further includes slice information and/or a data network name associated with the session.
  • the interoperability function network element is a trusted wireless local area network interoperation function network element.
  • a method for session handover is provided.
  • the method may be executed by a session management network element, or may also be executed by a component (such as a chip or a circuit) of the session management network element, which is not limited thereto.
  • a component such as a chip or a circuit
  • the implementation by the session management network element is taken as an example for description below.
  • the method may include: the session management network element receives a second message from the mobility management network element, the second message is used to instruct to switch the session of the terminal device from the first access technology to the second access technology, the session is passed through the first A session established by an access technology; according to the second message, the session management network element sends a third message and/or the session management network element updates the first identifier of the session to the second identifier, wherein the third message includes the first identifier of the session and the second identifier of the session, the third message is used to update the first identifier of the session to the second identifier, wherein the first identifier of the session is the session identifier when the session is established through the first access technology, and the second identifier of the session is the session identifier when the session is established through the second access technology, and the terminal device is a terminal device that does not support non-access stratum NAS signaling when accessing the core network through the second access technology.
  • the session management network element after the session management network element receives the second message from the mobility management network element, it can switch the session from the first access technology to the second access technology, for example, the session management network element associated with the session updates the session In another example, the session management network element associated with the session sends a third message to other core network elements, and so on.
  • session switching from the first access technology to the second access technology can be performed by the session management network element associated with the session.
  • the session switching from the first access technology to the second access technology is performed by the session management network element associated with the session.
  • the switching of the second access technology can realize the session switching process across access technologies, that is, the switching of the session from the first access technology to the second access technology.
  • the method further includes: when establishing a session through the first access technology, the session management network element sends the address of the session to the mobility management network element, and the address is the session through the first access technology An address assigned when the access technology is established.
  • the session management network element before the session management network element sends the address of the session to the mobility management network element, it includes: the session management network element determines that the terminal device accesses the core through the second access technology A terminal device that does not support NAS signaling during network time.
  • the method further includes: when the session is established through the first access technology, the session management network element sends the second identifier of the session to the mobility management network element.
  • the method before the session management network element sends the second identifier of the session to the mobility management network element, the method further includes: the session management network element determines that the terminal device is accessed through the second A terminal device that does not support NAS signaling when the technology accesses the core network; or, the session management network element determines that the session can be switched from the first access technology to the second access technology.
  • the session management network element determining that the session can be switched from the first access technology to the second access technology includes: the session management network element according to the slice information associated with the session and and/or the data network name associated with the session determines that the session can be switched from the first access technology to the second access technology.
  • the session management network element determines that the terminal device is a terminal device that does not support NAS signaling when accessing the core network through the second access technology, including: the session management network element Receive indication information from the terminal device, where the indication information is used to indicate that the terminal device is a terminal device that does not support NAS signaling when accessing the core network through the second access technology.
  • the second identifier of the session is a default value.
  • the second message includes one or more of the following: request type, address of the session, access type, access technology type, and the address is The address assigned when entering the technology.
  • a method for session handover is provided.
  • the method may be executed by an interoperable function network element, or may also be executed by a component (such as a chip or a circuit) of the interoperable function network element, which is not limited thereto.
  • a component such as a chip or a circuit
  • the execution by the network element of the interoperability function is taken as an example for description below.
  • the method may include: the interoperability function network element receives a request message from the terminal device, and the request message includes address information; the interoperation function network element determines to switch the session of the terminal device according to the address information, and the session is established through the first access technology session; the interoperability function network element sends the first message to the mobility management network element, and the first message is used to indicate the switching session; wherein, when the terminal device accesses the core network through the second access technology, it does not support the non-access stratum NAS Signaling terminal equipment.
  • the operation function network element receives the request message from the terminal device, determines to switch the session of the terminal device according to the address information carried in the request message, and sends a first message to the mobility management network element, which is used to instruct the switch session, In this way, a session switching process across access technologies can be realized, that is, session switching from the first access technology to the second access technology.
  • the address information is an address of the session, and the address is an address allocated when the session is established through the first access technology.
  • the method further includes: the network element of the interoperability function receives a fourth message from the mobility management network element, and the fourth message is used to indicate that the session handover is successful; the network element of the interoperation function The element sends a response message to the request message to the terminal device, and the response message includes address information.
  • the interoperability function network element determines that the session handover is successful according to the fourth message from the mobility management network element, it can send a response message to the request message to the terminal device, and the address information included in the response message can be used to represent the session handover success.
  • the request message further includes slice information and/or a data network name associated with the session.
  • the first message includes one or more of the following information: request type, address of the session, and access type, where the address is that the session uses the first access technology Address assigned at build time.
  • the request message is a Dynamic Host Configuration Protocol DHCP request message
  • the interoperability function network element determines to switch the session of the terminal device according to the address information, including: the interoperation function network element According to the address information being a non-zero address, it is determined to switch the session of the terminal device.
  • the network element with the interoperability function can determine that the session is an existing session according to the address information being a non-zero address, and then determine that the purpose of the request message is session switching.
  • the interoperability function network element is a trusted wireless local area network interoperation function network element.
  • a session switching method is provided, which can be performed by a data management network element, or can also be performed by a chip or circuit used for a data management network element, which is not limited in this application, for the convenience of description , the following takes the implementation by the data management network element as an example for description.
  • the method may include: the data management network element receives request information from the session management network element, the request information is used to request the subscription information associated with the session of the terminal device, and the session is a session established through the first access technology; the data management network element sends The session management network element sends session-associated subscription information, which is used to indicate that the session can be switched from the first access technology to the second access technology; wherein, the terminal device accesses the core network through the second access technology Terminal devices that do not support non-access stratum NAS signaling.
  • the session-associated subscription information includes one or more of the following: indication information, slice information, data network name, and the indication information is used to indicate that the session can be accessed from the first connection.
  • the incoming technology is switched to the second access technology.
  • a method for session handover is provided, which can be performed by a policy control network element, or can also be performed by a chip or a circuit for a policy control network element, which is not limited in this application, for the convenience of description , and the following uses policy-controlled network elements as an example to illustrate.
  • the method may include: the policy control network element receives a query message from the network element of the core network, the query message includes the address of the session of the terminal device, the query message is used to query the first identifier of the session, and the session is established through the first access technology session, the first identifier of the session is the session identifier when the session is established through the first access technology; the policy control network element sends a response message to the network element of the core network, and the response message includes the first identifier of the session; 2. Terminal equipment that does not support non-access stratum NAS signaling when the access technology accesses the core network.
  • the network element of the core network is a mobility management network element or a binding support network element.
  • a communication device is provided, and the device is configured to execute the method in any possible implementation manner of the foregoing first aspect to the sixth aspect.
  • the apparatus may include a unit and/or module, such as a processing unit and/or a communication unit, for executing the method in any possible implementation manner of the first aspect to the sixth aspect.
  • the apparatus is a network device (such as a mobility management network element, such as a session management network element, or an interoperability function network element).
  • the communication unit may be a transceiver, or an input/output interface; the processing unit may be at least one processor.
  • the transceiver may be a transceiver circuit.
  • the input/output interface may be an input/output circuit.
  • the apparatus is a chip, a chip system or a circuit for a network device.
  • the communication unit may be an input/output interface, interface circuit, output circuit, input circuit, pin or related circuit on the chip, chip system or circuit, etc.
  • the processing unit may be at least one processor, processing circuit or logic circuit, etc.
  • a communication device which includes: at least one processor, configured to execute a computer program or instruction stored in a memory, so as to perform the method in any possible implementation manner of the first aspect to the sixth aspect above .
  • the apparatus further includes a memory for storing computer programs or instructions.
  • the device further includes a communication interface, through which the processor reads the computer program or instructions stored in the memory.
  • the apparatus is a network device (such as a mobility management network element, such as a session management network element, or an interoperability function network element).
  • a network device such as a mobility management network element, such as a session management network element, or an interoperability function network element.
  • the apparatus is a chip, a chip system or a circuit for a network device.
  • the present application provides a processor configured to execute the methods provided in the foregoing aspects.
  • the processor's output and reception, input and other operations can also be understood as the sending and receiving operations performed by the radio frequency circuit and the antenna, which is not limited in this application.
  • a computer-readable storage medium where the computer-readable medium stores program code for execution by a device, and the program code includes a method for executing any one of the possible implementation manners of the first aspect to the sixth aspect above. method.
  • a computer program product containing instructions is provided, and when the computer program product is run on a computer, the computer executes the method in any possible implementation manner of the first aspect to the sixth aspect above.
  • a communication system including one or more of the aforementioned mobility management network element, session management network element, interoperability function network element, and terminal device.
  • the communication system includes the aforementioned mobility management network element and a session management network element configured to communicate with the mobility management network element.
  • the communication system includes the foregoing session management network element and a network element configured to communicate with the session management network element.
  • the communication system includes the aforementioned network element with an interoperable function, and a network element and/or a terminal device configured to communicate with the network element with an interoperable function.
  • the communication system includes the foregoing terminal device and a network element configured to communicate with the terminal device.
  • FIG. 1 is a schematic diagram of a network architecture applicable to an embodiment of the present application.
  • FIG. 2 is another schematic diagram of a network architecture applicable to the embodiment of the present application.
  • Fig. 3 is another schematic diagram of a network architecture applicable to the embodiment of the present application.
  • Fig. 4 is another schematic diagram of a network architecture applicable to the embodiment of the present application.
  • Fig. 5 is a schematic diagram of a session switching method provided by an embodiment of the present application.
  • Fig. 6 is a schematic flowchart of a method for session switching provided by an embodiment of the present application.
  • Fig. 7 is a schematic flowchart of a method for session switching provided by another embodiment of the present application.
  • Fig. 8 is a schematic flowchart of session establishment provided by an embodiment of the present application.
  • Fig. 9 is a schematic flowchart of a method for session switching provided by another embodiment of the present application.
  • Fig. 10 is a schematic flowchart of a method for session switching provided by another embodiment of the present application.
  • Fig. 11 is a schematic flowchart of session establishment provided by another embodiment of the present application.
  • Fig. 12 is a schematic flow chart of registering and accessing the 5GC network of the N5CW device applicable to the embodiment of the present application.
  • Fig. 13 is a schematic block diagram of an apparatus for session switching according to an embodiment of the present application.
  • Fig. 14 is another schematic block diagram of an apparatus for session switching according to an embodiment of the present application.
  • FIG. 15 is a schematic diagram of a chip system provided according to an embodiment of the present application.
  • the technical solutions of the embodiments of the present application can be applied to various communication systems, such as: the fifth generation (5th generation, 5G) system or new radio (new radio, NR), long term evolution (long term evolution, LTE) system, LTE frequency Division duplex (frequency division duplex, FDD) system, LTE time division duplex (time division duplex, TDD), etc.
  • 5G fifth generation
  • NR new radio
  • long term evolution long term evolution
  • LTE frequency Division duplex frequency division duplex
  • FDD frequency division duplex
  • TDD time division duplex
  • the technical solution provided by this application can also be applied to future communication systems, such as the sixth generation mobile communication system.
  • the technical solution of the embodiment of the present application can also be applied to device to device (device to device, D2D) communication, vehicle-to-everything (V2X) communication, machine to machine (machine to machine, M2M) communication, machine Type communication (machine type communication, MTC), and Internet of things (internet of things, IoT) communication system or other communication systems.
  • D2D device to device
  • V2X vehicle-to-everything
  • M2M machine to machine
  • MTC machine Type communication
  • IoT Internet of things
  • FIG. 1 is a schematic diagram of a network architecture applicable to an embodiment of the present application.
  • the network architecture takes the 5G system (the 5th generation system, 5GS) as an example.
  • the network architecture may include but not limited to: network slice selection function (network slice selection function, NSSF), authentication server function (authentication server function, AUSF), unified data management (unified data management, UDM), network exposure function (network exposure function, NEF), network storage function (NF repository function, NRF), policy control function (policy control function, PCF), charging function (charging function, CHF), application function (application function, AF), access and mobile Access and mobility management function (AMF), session management function (SMF), user equipment (UE), wireless access network equipment, user plane function (UPF), Data network (data network, DN).
  • network slice selection function network slice selection function, NSSF
  • authentication server function authentication server function
  • unified data management unified data management
  • UDM network exposure function
  • network exposure function network exposure function
  • NRF network storage function
  • policy control function policy control function
  • PCF policy control function
  • charging function charging function
  • CHF application function
  • Each network element shown in FIG. 1 is briefly introduced below.
  • UE can be called terminal equipment, access terminal, subscriber unit, subscriber station, mobile station, mobile station, remote station, remote terminal, mobile device, user terminal, terminal, wireless communication device, user agent or user device.
  • a terminal device may be a device that provides voice/data to a user, for example, a handheld device with a wireless connection function, a vehicle-mounted device, and the like.
  • some terminals are: mobile phone (mobile phone), tablet computer, notebook computer, palmtop computer, mobile internet device (mobile internet device, MID), wearable device, virtual reality (virtual reality, VR) device, augmented reality (augmented reality, AR) equipment, wireless terminals in industrial control, wireless terminals in self driving, wireless terminals in remote medical surgery, smart grid Wireless terminals in transportation safety, wireless terminals in smart city, wireless terminals in smart home, cellular phones, cordless phones, session initiation protocol , SIP) telephones, wireless local loop (wireless local loop, WLL) stations, personal digital assistants (personal digital assistant, PDA), handheld devices with wireless communication capabilities, computing devices or other processing devices connected to wireless modems, Wearable devices, terminal devices in a 5G network, or terminal devices in a future evolving public land mobile network (PLMN), etc., are not limited in
  • the terminal device may also be a wearable device.
  • Wearable devices can also be called wearable smart devices, which is a general term for the application of wearable technology to intelligently design daily wear and develop wearable devices, such as glasses, gloves, watches, clothing and shoes.
  • a wearable device is a portable device that is worn directly on the body or integrated into the user's clothing or accessories. Wearable devices are not only a hardware device, but also achieve powerful functions through software support, data interaction, and cloud interaction.
  • Generalized wearable smart devices include full-featured, large-sized, complete or partial functions without relying on smart phones, such as smart watches or smart glasses, etc., and only focus on a certain type of application functions, and need to cooperate with other devices such as smart phones Use, such as various smart bracelets and smart jewelry for physical sign monitoring.
  • the terminal device can also be the terminal device in the IoT system.
  • IoT is an important part of the development of information technology in the future. Its main technical feature is to connect items to the network through communication technology, so as to realize Interconnection, an intelligent network that interconnects things.
  • a certain air interface technology such as NR or LTE technology
  • a certain air interface technology may also be used to communicate with each other between terminal devices.
  • the device for realizing the function of the terminal device may be the terminal device, or may be a device capable of supporting the terminal device to realize the function, such as a chip system or a chip, and the device may be installed in the terminal device.
  • the system-on-a-chip may be composed of chips, or may include chips and other discrete devices.
  • Access network The access network can provide network access functions for authorized users in a specific area. Terminal devices can use access networks with different access technologies to access the core network, for example: use the third generation partnership project (3rd generation partnership project, 3GPP) access technology and non-3GPP (non-3GPP) access technology to access Core Network.
  • 3GPP third generation partnership project
  • non-3GPP non-3GPP
  • the access technology may include NR, evolved universal mobile telecommunications system (universal mobile telecommunications system, UMTS) terrestrial radio access network (UMTS terrestrial radio access network, E-UTRAN), Multefire, 3GPP access technology, non- 3GPP access technology, 4G cellular access technology, 5G cellular access technology, trusted or untrusted wireless fidelity (WiFi) access technology, fixed network or wired access technology, etc.
  • NR evolved universal mobile telecommunications system
  • UMTS Universal mobile telecommunications system
  • E-UTRAN evolved universal mobile telecommunications system
  • Multefire 3GPP access technology
  • non- 3GPP access technology 4G cellular access technology
  • 5G cellular access technology 5G cellular access technology
  • WiFi wireless fidelity
  • the access network using non-3GPP access technology may include but not limited to: WiFi network, WLAN, MulteFire network, wired network (for example: wireless and wireline convergence (WWC) network), or home base station network.
  • the access network equipment using the non-3GPP technology may include, for example: an access point (access point, AP), a trusted WLAN interworking function (trusted WLAN interworking function, TWIF) network element, a trusted non-3GPP gateway function ( trusted non-3GPP gateway function, TNGF), wired access gateway function (wireline access gateway function, W-AGF), access gateway function (access gateway function, AGF), broadband network gateway (broadband network gateway, BNG), fixed Mobile interworking function (fixed-mobile interworking function, FMIF), non-3GPP interworking function (Non-3GPP interworking function, N3IWF), etc.
  • the access network adopting 3GPP access technology may include but not limited to: LTE network, NR network, 5G network, or a subsequent evolved mobile communication network.
  • the access network equipment using the 3GPP technology may include, for example, radio access network (radio access network, RAN) equipment, g-NodeB, e-NodeB, and home-NodeB.
  • radio access network radio access network
  • An access network that implements access network functions based on wireless communication technologies may be called a RAN.
  • the radio access network can be responsible for functions such as radio resource management, quality of service (QoS) management, data compression and encryption on the air interface side.
  • QoS quality of service
  • the wireless access network provides access services for terminal equipment, and then completes the forwarding of control signals and user data between the terminal and the core network.
  • Radio access network equipment may include, but not limited to, for example: a macro base station, a micro base station (also called a small cell), a radio network controller (radio network controller, RNC), a node B (Node B, NB), a base station controller ( base station controller, BSC), base transceiver station (base transceiver station, BTS), home base station (for example, home evolved NodeB, or home Node B, HNB), baseband unit (baseband unit, BBU), AP in the WiFi system, Wireless relay node, wireless backhaul node, transmission point (transmission point, TP) or transmission and reception point (transmission and reception point, TRP), etc., can also be gNB or transmission point (TRP) in the 5G (eg, NR) system or TP), one or a group (including multiple antenna panels) antenna panels of the base station in the 5G system, or, it can also be a network node that constitutes a gNB or a transmission point, such as a baseband
  • AMF mainly used for functions such as access control, mobility management, attachment and detachment.
  • SMF mainly used for user plane network element selection, user plane network element redirection, Internet protocol (internet protocol, IP) address allocation for terminal equipment, session establishment, modification and release, and QoS control.
  • IP Internet protocol
  • UPF mainly used for receiving and forwarding user plane data.
  • the UPF can receive user plane data from the DN, and send the user plane data to the terminal device through the AN device.
  • UPF can also receive user plane data from terminal equipment through AN equipment and forward it to DN.
  • NEF It is mainly used to safely open services and capabilities provided by 3GPP network functions to the outside.
  • PCF A unified policy framework mainly used to guide network behavior, and provide policy rule information for control plane network elements (such as AMF, SMF, etc.).
  • AF It is mainly used to provide services to the 3GPP network, such as interacting with the PCF for policy control.
  • Network slice selection function (network slice selection function, NSSF): mainly used for network slice selection.
  • UDM mainly used for UE subscription data management, including storage and management of UE ID, UE access authorization, etc.
  • DN mainly used for the operator network that provides data services for the UE.
  • the Internet Internet
  • a third-party service network IP multimedia service (IP multi-media service, IMS) network, and the like.
  • IP multimedia service IP multi-media service, IMS
  • AUSF mainly used for user authentication, etc.
  • NRF It is mainly used to save the description information of network functional entities and the services they provide.
  • CHF It is mainly used to issue charging parameters to SMF and collect user charging information provided by SMF.
  • network elements can communicate with each other through the interfaces shown in the figure, and some interfaces can be realized by means of service-oriented interfaces.
  • the UE and the AMF network element may interact through an N1 interface, and the interaction message may be called an N1 message (N1Message), for example.
  • N1Message N1 message
  • the RAN and AMF network elements can interact through the N2 interface, and the N2 interface can be used for sending non-access stratum (non-access stratum, NAS) messages, etc.
  • the RAN and UPF can interact through the N3 interface, and the N3 interface can be used to transmit user plane data, etc.
  • the SMF network element and the UPF can interact through the N4 interface, and the N4 interface can be used to transmit information such as the tunnel identification information of the N3 connection, data cache indication information, and downlink data notification messages.
  • the UPF and DN can interact through the N6 interface, and the N6 interface can be used to transmit data on the user plane.
  • the relationship between other interfaces and each network element is shown in FIG. 1 , and for the sake of brevity, details are not described here one by one.
  • some terminal devices such as 5G UE, support NAS signaling when accessing the core network through 3GPP access technology, and also support NAS signaling when accessing the core network through non-3GPP access technology.
  • Some terminal devices do not support NAS signaling when accessing the core network through non-3GPP access technologies, but support NAS signaling when accessing through 3GPP access technologies.
  • WLAN wireless local access network
  • N5CW device Non-5G-Capable over WLAN, N5CW device
  • N5CW device such as N5CW UE
  • a terminal device or UE is used to indicate a terminal device that does not support NAS signaling when accessing the core network through a certain access technology, such as when accessing the core network through a non-3GPP access technology Terminal devices that do not support NAS signaling.
  • FIG. 2 is another schematic diagram of a network architecture applicable to the embodiment of the present application.
  • a trusted non-3GPP access network includes a trusted non-3GPP access point (trusted non-3GPP access point, TNAP) and a trusted non-3GPP gateway Function (trusted non-3GPP gateway function, TNGF).
  • the trusted non-3GPP access point may be a trusted WLAN access point.
  • the interface between the UE and the TNGF is the NWt interface.
  • the TNAN architecture may be a point-to-point interface protocol as shown in FIG. 2 , or may also adopt a service interface architecture as shown in FIG. 1 , which is not limited.
  • Fig. 3 is another schematic diagram of a network architecture applicable to the embodiment of the present application.
  • a trusted WLAN access network (trusted WLAN access network, TWAN) includes a trusted WLAN access point (trusted WLAN access point, TWAP) and a trusted WLAN interworking function (trusted WLAN interworking function, TWIF) network Yuan.
  • TWAN trusted WLAN access network
  • TWAP trusted WLAN access point
  • TWIF trusted WLAN interworking function
  • the TWIF network element has a NAS protocol stack, which can support the N1 interface, and can construct NAS signaling for the N5CW device. Therefore, the TWIF network element can complete registration and session management processes on behalf of the N5CW device.
  • Fig. 4 is another schematic diagram of a network architecture applicable to the embodiment of the present application.
  • the network architecture may include but not limited to: N5CW UE, TNAP, RAN, AMF, SMF, PCF, UDM, DN, UPF, TWIF, TNAP.
  • N5CW UE N5CW UE
  • TNAP TNAP
  • AMF Access Management Function
  • SMF Packet Control Function
  • PCF Packet Control Function
  • the above-mentioned network architecture applied to the embodiment of the present application is only an illustrative architecture, and the network architecture applicable to the embodiment of the present application is not limited thereto. Any network architecture that can realize the functions of the above-mentioned network elements is applicable to this application.
  • the access network is a trusted WLAN
  • the terminal device is an N5CW device for illustration.
  • the functions or network elements in Figures 1 to 4 can be understood as network elements for implementing different functions, such as Network slices can be combined on demand.
  • These network elements can be independent devices, or can be integrated in the same device to achieve different functions, or can be network elements in hardware devices, or software functions running on dedicated hardware, or platforms (for example, cloud The virtualization function instantiated on the platform), this application does not limit the specific form of the above network elements.
  • the name of the interface between the various network elements in FIG. 1 to FIG. 4 is just an example, and the name of the interface in a specific implementation may be another name, which is not specifically limited in the present application.
  • the name of the message (or signaling) transmitted between the above network elements is only an example, and does not constitute any limitation on the function of the message itself.
  • the access technology is used to indicate the access technology used by the terminal device to access the communication device, or the access technology used by the terminal device to establish a communication connection with the communication device.
  • the first access technology and the second access technology are mentioned several times.
  • the first access technology when the terminal device accesses the core network through the first access technology, it supports NAS signaling
  • the second access technology when the terminal device accesses the core network through the second access technology, it does not support NAS signaling.
  • the first access technology is the 3GPP access technology, that is, the terminal device can communicate with other devices through the wireless interface of the 3GPP access technology, or the terminal device can use the access network of the 3GPP access technology to access Core network;
  • the second access technology is a non-3GPP access technology, that is, the terminal device and other devices can communicate through the interface of the non-3GPP access technology, or the terminal device can use the access network of the non-3GPP access technology Access to the core network.
  • the 3GPP access technology and the non-3GPP access technology reference may be made to the foregoing description, which will not be repeated here.
  • Session identifier (identifier, ID)
  • the first identifier of the session and the second identifier of the session are mentioned multiple times.
  • the first identifier of the session indicates the session identifier before handover, that is, the session identifier when the session is established through the first access technology.
  • the second identifier of the session indicates the session identifier after switching, that is, the session identifier when the session is established through the second access technology.
  • the second identifier of the session may be a default value (or called a special value or a fixed value).
  • the second identifier of the session is 15, for example.
  • the mobile management network element refers to a network element that can realize the mobile management function, for example, the mobile management network element is AMF;
  • the interoperable function network element refers to a network element that can realize the interoperable function, for example, the interoperable function network element is TWIF;
  • a session management network element indicates a network element that can implement a session management function, for example, a session management network element is an SMF.
  • FIG. 5 is a schematic diagram of a method 500 for session switching provided by an embodiment of the present application.
  • Method 500 may include the following steps.
  • a mobility management network element receives a first message from an interoperability function network element, where the first message is used to instruct switching of a session of a terminal device.
  • the first message is, for example, a session establishment request message.
  • the session indicates a session established through the first access technology, and the session may include one or more sessions established by the terminal device through the first access technology.
  • the terminal device is a terminal device that does not support NAS signaling when accessing the core network through the second access technology, for example, the terminal device is an N5CW device.
  • session switching or switching sessions are both used to indicate that the session is switched from the first access technology to the second access technology, or it may also indicate that the session identifier is changed from the session when the first access technology is established
  • the identifier (that is, the first identifier of the session) is updated to the session identifier (that is, the second identifier of the session) when it is established through the second access technology.
  • the session is a session established by the terminal device through the first access technology; after the handover, the session is a session established by the terminal device through the second access technology.
  • the session identifier is the session identifier when the session is established through the first access technology; after the handover, the session identifier is the session identifier when the session is established through the second access technology.
  • the session identifier is the session identifier when the session is established through the second access technology.
  • first identifier and the second identifier of the session as well as the first access technology and the second access technology, refer to the previous explanation of terms, and no more details are given here.
  • the first message is used to instruct to switch the session of the terminal device, and may include at least the following two implementation manners.
  • the information included in the first message may be used to instruct to switch the session of the terminal device.
  • the information included in the first message indicates that the session exists, and the information may be used to instruct switching of the session of the terminal device.
  • the information is a request type (request type), and the request type is an existing PDU session (existing PDU session) (or an existing PDU session).
  • the mobility management network element receives the first message from the interoperability function network element, according to the request type in the first message, it can be learned that the purpose of the first message is session handover.
  • the information is the address allocated to the terminal device when the session is established through the first access technology.
  • the mobility management network element receives the first message from the interoperability function network element, it can learn the first message according to the address assigned to the terminal device when the session carried in the first message is established through the first access technology
  • the purpose is session switching.
  • the first message itself may be used to instruct to switch the session of the terminal device.
  • the first message is a newly defined message, and the message itself can be used to instruct to switch the session of the terminal device.
  • the mobility management network element may determine that the purpose of the first message is session handover.
  • the first message includes one or more of the following: request type, session address, and access type.
  • the address of the session is the address allocated when the session is established through the first access technology, that is, the address is the address allocated by the 5GC to the terminal device when the session is established through the first access technology.
  • the first identifier of the session can be obtained, or it can also be determined that the session is an existing session.
  • the access type can be used to determine the type of session switching. If the access type is the second access technology, it means that the session is switched from the first access technology to the second access technology.
  • the request type can be used to determine whether it is an existing session, or can be used to determine whether the purpose of the first message is session switching or session establishment. If the request type is existing PDU session, the request type can be used to determine that the session is an existing session, or can be used to determine that the purpose of the first message is session switching.
  • the mobility management network element determines a session management network element associated with the session.
  • the mobility management network element After determining to switch the session of the terminal device according to the first message received in step 501, the mobility management network element determines (or selects) the session management network element associated with the session.
  • the mobility management network element determines the session management network element associated with the session, which may include at least the following two solutions.
  • the mobility management network element may determine the session management network element associated with the session according to the session association information.
  • the information associated with the session includes: slice information and/or a data network name (data network name, DNN).
  • the slice information includes, for example, single-network slice selection assistance information (single-network slice selection assistance information, S-NSSAI).
  • the first message includes session-associated slice information and/or DNN
  • the mobility management network element determines the session-associated session management network element according to the session-associated slice information and/or DNN.
  • the mobility management network element may determine the session management network element associated with the first identifier of the session according to the first identifier of the session.
  • the mobility management network element sends a second message to the session management network element, where the second message is used to instruct handover of the session from the first access technology to the second access technology.
  • the mobility management network element After determining the session management network element associated with the session, the mobility management network element sends a second message to the session management network element, where the second message is used to instruct switching of the session from the first access technology to the second access technology.
  • the second message is, for example, a session management (session management, SM) context modification request message.
  • the second message includes one or more of the following: request type, session address, access type, and access technology type. For information about each item, refer to the previous description.
  • the session management network element switches the session from the first access technology to the second access technology based on the second message.
  • Switching the session from the first access technology to the second access technology may mean performing some operations, such as replacing the identifier (that is, updating the first identifier of the session to the second identifier) and message transmission. Details below.
  • the session management network element switches the session from the first access technology to the second access technology, including: the session management network element sends a third message, and/or, the session management network element sends the first identifier of the session to Update (or modification, or replacement) is the second identifier.
  • the third message includes the first identifier of the session and the second identifier of the session, and the third message is used to update the first identifier of the session to the second identifier.
  • the session management network element may send a third message to other core network elements, so as to update the session identifier from the first identifier to the second identifier.
  • the network elements of the core network may include one or more of the following network elements: data management network elements (such as UDM), policy control network elements (such as PCF), and mobility management network elements (such as AMF).
  • the network element of the core network is a UMD.
  • the session management network element switching the session from the first access technology to the second access technology may include: the session management network element sends a registration information modification request message to the UDM. After receiving the registration information modification request message, the UDM updates the session identifier from the first identifier to the second identifier.
  • the network element of the core network is a PCF.
  • the session management network element switching the session from the first access technology to the second access technology may include: the session management network element initiates an N4 session modification procedure to the PCF. Through the N4 session modification procedure, the PCF updates the identifier of the session from the first identifier to the second identifier.
  • the network element of the core network is an AMF.
  • the session management network element switching the session from the first access technology to the second access technology may include: the session management network element sends an SM context modification response message to the PCF. After receiving the SM context modification response message, the AMF updates the identifier of the session from the first identifier to the second identifier.
  • the method 500 further includes: the interoperability function network element receives a request message from the terminal device, where the request message includes address information.
  • the address information may be used to indicate session switching. If the address information is a non-zero address, it indicates that the session is an existing session, and further indicates that the purpose of the request message is session switching. Wherein, the address information may be, for example, the address of the session, that is, the address allocated when the session is established through the first access technology.
  • the network element with the interoperability function may determine to switch the session of the terminal device according to the address information, for example, determine to switch the session of the terminal device according to the non-zero address of the address information.
  • the request message may be, for example, a message requesting address allocation, for example, the request message is a dynamic host configuration protocol (dynamic host configuration protocol, DHCP) message.
  • the operation function network element receives the request message from the terminal device, and after determining to switch the session of the terminal device, sends the above-mentioned first message to the mobility management network element.
  • the method 500 further includes: the interoperation function network element receives a fourth message from the mobility management network element, and the fourth message is used to indicate that the session handover is successful; the interoperation function network element sends a response message to the request message to the terminal device, The response message includes address information.
  • the mobility management network element may send a fourth message to the interoperability function network element, and the fourth message may be a response to the first message in step 501, such as A response message for establishing a session; after receiving the fourth message, the network element with the interoperability function can send a response message to the request message to the terminal device, and the address information included in the response message can be used to indicate that the session handover is successful.
  • the terminal device determines that the session switching is successful according to that the address information in the response message is the same as the address information in the request message.
  • the first message includes the address of the session, which is the address allocated when the session is established through the first access technology, that is, the address is allocated by the 5GC to the terminal device when the session is established through the first access technology the address of.
  • the mobility management network element may determine the first identifier of the session according to the address of the session, and then determine the session management network element associated with the first identifier.
  • the mobility management network element sends a query message, and the query message includes the address of the session; the mobility management network element receives a response message, and the response message includes the first identifier of the session.
  • the mobility management network element queries other core network elements for the first identifier of the session based on the address of the session.
  • the mobility management network element sends a query message to the PCF associated with the session, the query message includes the address of the session, and the query message can be used to query the first identifier of the session; the mobility management network element receives a response message from the PCF, the response The message includes a first identification of the session.
  • the address of the session can be used to identify the PCF session.
  • the mobile management network element sends a query message to the binding support function (binding support function, BSF), the query message includes the address of the session, and the query message can be used to query the PCF associated with the session, or the query message can be used to Query the first identifier of the session;
  • BSF identifies the session according to the address of the session, queries the PCF associated with the session, and inquires the first identifier of the session from the PCF;
  • the BSF sends a response message to the mobility management network element, and the response message includes information from the PCF.
  • the first identifier of the queried session can be used by the BSF and the PCF to identify the session.
  • the mobility management network element determines the first identifier of the session based on the address of the session and the first association relationship.
  • the mobility management network element determines the first identifier of the session based on the address of the session and the first association relationship.
  • the first association relationship includes the relationship between the address of the session and the first identifier of the session.
  • the form of the first association relationship is not limited in this embodiment of the present application.
  • the first association relationship includes the relationship between the address of the session and the first identifier of the session
  • the mobility management network element may directly determine the first identifier of the session according to the address of the session included in the first message and the first association relationship .
  • the first association relationship includes the relationship between the address of the session and the PCF associated with the session
  • the mobility management network element may determine the PCF associated with the session according to the address of the session included in the first message and the first association relationship;
  • the management network element may query the PCF for the first identifier of the session, and then determine the first identifier of the session.
  • the embodiment of the present application does not limit the storage method of the first association relationship.
  • the first association relationship may be stored locally by the mobility management network element, for example, the context information of the terminal device locally stored by the mobility management network element includes the first association relationship.
  • the first association relationship may be stored in other core network elements (such as UDM, or a unified data repository function (unified data repository, UDR)), after the mobile management network element receives the first message, from other core network The first association relationship is acquired at the element.
  • UDM unified data repository function
  • UDR unified data repository
  • the method 500 further includes: when establishing a session through the first access technology, the session management network element sends the address of the session to the mobility management network element; the mobility management network element adds the session address in the context information of the terminal device to Establish the first association relationship.
  • establishing the first association relationship means establishing an association between the address of the session and the first identifier of the session, so that the first identifier of the session can be determined according to the address of the session and the association.
  • the mobility management network element may directly establish the first association relationship in the context information of the terminal device, or may establish the first association relationship in the context information of the terminal device when a condition is met.
  • the mobility management network element determines that the terminal device is a terminal device that does not support NAS signaling when accessing the core network through the second access technology
  • the mobility management network element establishes the first association relationship in the context information of the terminal device.
  • the mobility management network element may determine that the terminal device is a terminal device that does not support NAS signaling when accessing the core network through the second access technology according to one or more of the following information: terminal device identifier, session number 2. Identification, identification of access network equipment, instruction information from terminal equipment.
  • the indication information is used to indicate that the terminal device is a terminal device that does not support NAS signaling when accessing the core network through the second access technology.
  • the access network device is an access network device corresponding to the second access technology.
  • the foregoing information may be acquired locally by the mobility management network element, or may also be received, which is not limited thereto.
  • the mobility management network element acquires (or searches for) the context information (such as session context information or session-related context information) of the terminal device according to the identifier of the terminal device, and according to the The second identifier (for example, a special value or a fixed value) determines that the terminal device is a terminal device that does not support NAS signaling when accessing the core network through the second access technology.
  • the context information such as session context information or session-related context information
  • the mobility management network element determines, according to the identifier of the access network device, that the terminal device is a terminal device that does not support NAS signaling when accessing the core network through the second access technology.
  • the mobility management network element receives the second identifier of the session (for example, a special value or a fixed value) (for example, the second identifier of the session is carried in the first message), and determines the terminal device according to the second identifier of the session. It is a terminal device that does not support NAS signaling when accessing the core network through the second access technology.
  • the mobility management network element receives indication information from the terminal device, where the indication information is used to indicate that the terminal device is a terminal device that does not support NAS signaling when accessing the core network through the second access technology; the mobility management network element according to The indication information determines that the terminal device is a terminal device that does not support NAS signaling when accessing the core network through the second access technology.
  • the first message includes the second identifier of the session (such as 15).
  • the mobility management network element may determine the first session identifier according to the second session identifier and the second association relationship, and then determine the session management network element associated with the first identifier.
  • the second association relationship includes a relationship between the first identifier of the session and the second identifier of the session.
  • the form of the second association relationship is not limited in this embodiment of the present application.
  • the first association relationship includes the relationship between the first identifier of the session and the second identifier of the session
  • the mobility management network element can directly determine the session according to the second identifier of the session included in the first message and the second association relationship the first identifier of .
  • the embodiment of the present application does not limit the storage method of the second association relationship.
  • the second association relationship may be stored locally by the mobility management network element, for example, the context information of the terminal device locally stored by the mobility management network element includes the second association relationship.
  • the second association relationship may be stored in other core network elements (such as UDM), and the mobility management network element obtains the second association relationship from other core network elements after receiving the first message.
  • the method 500 further includes: when establishing a session through the first access technology, the session management network element sends the second identifier of the session to the mobility management network element;
  • the second association relationship is established in the context information of .
  • establishing the second association relationship means establishing an association between the first identifier of the session and the second identifier of the session, so that the first identifier of the session can be determined according to the second identifier of the session and the association.
  • the mobility management network element may directly establish the second association relationship in the context information of the terminal device, or may establish the second association relationship in the context information of the terminal device when a condition is met. For example, when the mobility management network element determines that the terminal device is a terminal device that does not support NAS signaling when accessing the core network through the second access technology, the mobility management network element establishes the second association relationship in the context information of the terminal device. Regarding the manner in which the mobility management network element determines that the terminal device is a terminal device that does not support NAS signaling when accessing the core network through the second access technology, refer to the foregoing description, and details will not be repeated here.
  • session #A takes session #A as an example for switching from a 3GPP access technology to a non-3GPP access technology, where the mobility management network element is AMF, the interoperability function network element is TWIF, and the session management network element is SMF. It can be understood that the Session #A may consist of one or more sessions.
  • Fig. 6 is a schematic flowchart of a method for session switching provided by an embodiment of the present application.
  • the method 600 shown in FIG. 6 may be used in a scenario where the AMF queries the first identifier of the session #A based on the address of the session #A.
  • the method 600 shown in FIG. 6 may include the following steps.
  • the UE registers with the 5GC network through the TWIF.
  • step 601 reference may be made to the flow shown in FIG. 12 below.
  • the UE sends a DHCP request message to the TWIF.
  • the DHCP request message includes address information.
  • the address information is the IP address allocated by the 5GC for the session #A when the UE accesses through 3GPP (hereinafter for brevity, this address is recorded as address #A).
  • the TWIF determines that the UE initiates a session handover.
  • the address information in the DHCP request message is 0.0.0.0.
  • the TWIF judges that the UE initiates a session handover according to the fact that the address #A in the DHCP request message is not 0.0.0.0.
  • the TWIF sends a session establishment request message to the AMF.
  • the session establishment request message (such as the PDU session establishment request message) may include but not limited to: the identifier of the session #A (such as the PDU session ID), the request type (request type), the access type, and the DHCP request message Address #A.
  • the request type is "existing PDU session", which indicates that an existing session or an existing session is to be switched.
  • the identifier of the session #A is the second identifier of the session #A, that is, the dedicated ID of the session established by the TWIF for the UE.
  • the access type is non-3GPP.
  • the session establishment request message initiated by the TWIF to the AMF is only an exemplary description, and this embodiment of the present application is not limited thereto.
  • any N2 message may be used in this embodiment of the present application.
  • the AMF determines to switch session #A from the 3GPP access technology to the non-3GPP access technology.
  • the AMF can determine that the UE is an N5CW device according to the session establishment request message received from the TWIF. On the other hand, the AMF may determine to switch the session #A identified by the address #A from the 3GPP access technology to the non-3GPP access technology according to the session establishment request message.
  • the AMF determines to switch session #A identified by address #A from 3GPP access technology to non-3GPP access technology according to one or more of the following information included in the session establishment request message: request type, access Type, address #A.
  • the AMF determines to switch the session #A identified by the address #A from the 3GPP access technology to the non-3GPP access technology according to the request type.
  • the AMF determines to switch the session #A identified by the address #A from the 3GPP access technology to the non-3GPP access technology according to the access type .
  • the AMF determines the SMF according to the first identifier of the session #A.
  • the AMF After the AMF determines the first identifier of the session #A, it may determine the SMF associated with the first identifier.
  • the method 600 further includes: the AMF determines the first identifier of the session #A through solution (a) or solution (b).
  • solution (a) may include the following steps.
  • the AMF sends a discovery (discovery) request message to the BSF.
  • the discovery request message is used to query the PCF associated with session #A.
  • the discovery request message may include: UE's subscriber permanent identifier (subscription permanent identifier, SUPI) and address #A.
  • SUPI subscription permanent identifier
  • address #A can be used to identify the session #A.
  • the SUPI of the UE may be determined through a globally unique temporary identity (globally unique temporary identity, GUTI) of the UE.
  • GUTI globally unique temporary identity
  • the UE sends the network access identity (network access identity, NAI) to TWIF, wherein, the NAI may include when the UE accesses the 5GC through the 3GPP access technology, the core network ( Such as the GUTI allocated by the AMF; in step 604, the TWIF carries the GUTI when sending the session establishment request message to the AMF; the AMF can associate with the context of the UE according to the GUTI, and then determine the SUPI of the UE.
  • the AMF determines the SUPI of the UE, the foregoing is only an exemplary description, and this embodiment of the present application is not limited thereto.
  • the BSF sends the ID of the PCF associated with the session #A to the AMF.
  • the BSF After receiving the discovery request message sent by the AMF, the BSF determines the PCF associated with the session #A, and returns a discovery response message to the AMF, where the discovery response message includes the ID of the PCF associated with the session #A.
  • the AMF sends an inquiry message to the PCF identified by the PCF ID.
  • the AMF After receiving the ID of the PCF associated with the session #A, the AMF sends an inquiry message to the PCF identified by the PCF ID, where the inquiry message is used to inquire about the first identifier of the session #A.
  • the inquiry message includes UE's SUPI and address #A. Wherein, the SUPI of the UE can be used to identify the UE, and the address #A can be used to identify the session #A.
  • the PCF sends the first identifier of the session #A to the AMF.
  • the PCF returns a response message to the inquiry message to the AMF, and the response message includes the first identifier of the session #A.
  • the AMF can determine the first identifier of the session #A.
  • solution (b) may include the following steps.
  • the AMF sends a discovery request message to the BSF.
  • the discovery request message is used to query the PCF associated with session #A.
  • the discovery request message includes: UE's SUPI and address #A.
  • step b1 reference may be made to step a1 in solution (a), which will not be repeated here.
  • the BSF sends an inquiry message to the PCF associated with the session #A.
  • the BSF After receiving the discovery request message sent by the AMF, the BSF determines the PCF associated with the session #A, and sends an inquiry message to the PCF associated with the session #A, where the inquiry message is used to inquire about the first identifier of the session #A.
  • the inquiry message includes UE's SUPI and address #A. Wherein, the SUPI of the UE can be used to identify the UE, and the address #A can be used to identify the session #A.
  • the PCF sends the first identifier of the session #A to the BSF.
  • the PCF returns a response message to the inquiry message to the BSF, and the response message includes the first identifier of the session #A.
  • the BSF sends the first identifier of the session #A to the AMF.
  • the BSF returns a discovery response message to the AMF, where the discovery response message includes the first identifier of session #A.
  • the AMF can determine the first identifier of the session #A.
  • the AMF can learn the SMF ID and the SM context ID associated with the first identification, and the AMF sends the SM context modification request message to the SMF identified by the SMF ID.
  • the AMF sends an SM context modification request message to the SMF.
  • the SM context modification request message may include one or more of the following information: SM context ID (SM context ID), access type (ie non-3GPP), access technology type (RAT type).
  • SM context ID SM context ID
  • access type ie non-3GPP
  • RAT type access technology type
  • the SMF determines to switch the session #A from the 3GPP access technology to the non-3GPP access technology according to the access type and/or RAT type included in the SM context modification request message, and then the SMF executes the session #A from the 3GPP access technology to the non-3GPP access technology. Switching of non-3GPP access technology. As an example, the SMF performs the handover of the session #A from the 3GPP access technology to the non-3GPP access technology, including the SMF performing steps 608 to 610 .
  • the SMF sends an SM policy association update message to the PCF.
  • the SM policy association update message may include one or more of the following information: SM policy association ID, access type (ie, non-3GPP), and the second identifier of session #A (eg, 15).
  • a rule means a policy information element related to a session or a service data flow, for which reference may be made to the existing description, which is not limited here.
  • the SMF initiates an N4 session modification process to the UPF based on the PCC rule.
  • the SMF sends a registration information modification request message to the UDM.
  • the registration information modification request message may include one or more of the following information: SUPI, the first identifier of session #A, and the second identifier of session #A (for example, 15).
  • the UDM After receiving the registration information modification request message, the UDM modifies the session #A identifier in the registration information to the second identifier.
  • the SMF after the SMF sends the registration information modification request message to the UDM, the SMF also modifies the identifier of the session #A in the SM context to the second identifier.
  • the SMF sends an SM context modification response message to the AMF.
  • the AMF modifies the identifier of the session #A to the second identifier.
  • the AMF may also modify the identifier of session #A to the second identifier before step 611, such as in step 605 or step 606.
  • the AMF sends a session establishment response message to the TWIF.
  • AMF sends a session establishment response message to TWIF to notify TWIF to accept the session establishment.
  • the AMF sends a N2 message to the TWIF, and the N2 message includes a session establishment acceptance message.
  • the session establishment response message includes an N2 interface session management container (N2 SM container).
  • the TWIF sends a DHCP response message to the UE.
  • the DHCP response message includes address information, and the address information is the address information included in the DHCP request message in step 602 (that is, address #A). According to the unchanged address information, the UE determines that the handover of session #A is successful.
  • the SMF initiates a user plane resource release process on the 3GPP side.
  • the SMF can execute the user plane resource release process on the 3GPP side to release the 3GPP side resources.
  • the N5CW device can carry the IP address allocated by the 5GC for session #A in the DHCP address information, and the AMF will query the session # from other core network elements (such as BSF, or PCF) according to the IP address of session #A
  • BSF base station
  • PCF PCRF
  • the AMF initiates SM context modification to the SMF associated with the session #A, so that the SMF associated with the session #A performs the handover of the session #A from the 3GPP access technology to the non-3GPP access technology, so that the N5CW device can be connected to the 3GPP side
  • the established session #A is switched to the non-3GPP side.
  • Fig. 7 is a schematic flowchart of a method for session switching provided by another embodiment of the present application.
  • the method 700 shown in FIG. 7 may be used in a scenario where the AMF determines the first identifier of the session #A based on the address of the session #A and the first association relationship.
  • the method 700 shown in FIG. 7 may include the following steps.
  • the UE registers with the 5GC network through the TWIF.
  • the UE sends a DHCP request message to the TWIF.
  • the TWIF determines that the UE initiates a session handover.
  • the TWIF sends a session establishment request message to the AMF.
  • the AMF determines to switch session #A from the 3GPP access technology to the non-3GPP access technology.
  • steps 701-705 are similar to steps 601-605 and will not be repeated here.
  • the AMF determines the SMF according to the first identifier and the first association relationship of the session #A.
  • the first association relationship includes the relationship between the address of session #A and the first identifier of session #A.
  • the AMF may determine the first identifier of session #A according to the address of session #A received in step 704 and the first association relationship (such as the first association relationship stored in the UE context); further, The AMF can learn the SMF and the SM context ID associated with the session #A according to the first identifier of the session #A.
  • the AMF receives the address of the session #A (namely address #A) and the first identifier of the session #A from the SMF; the AMF can save the address # in the UE context information The relationship between A and the first identifier of session #A. Specifically, it will be described later with reference to FIG. 8 .
  • the AMF sends an SM context modification request message to the SMF.
  • the SMF sends an SM policy association update message to the PCF.
  • the SMF initiates an N4 session modification process to the UPF based on the PCC rule.
  • the SMF sends a registration information modification request message to the UDM.
  • the SMF sends an SM context modification response message to the AMF.
  • the AMF sends a session establishment response message to the TWIF.
  • the TWIF sends a DHCP response message to the UE.
  • the SMF initiates a user plane resource release process on the 3GPP side.
  • steps 707-714 are similar to steps 607-614, and will not be repeated here.
  • the N5CW device can carry the IP address allocated by the 5GC for the session #A in the DHCP address information, and the AMF determines the SMF associated with the session #A according to the IP address of the session #A and the locally saved first association relationship, Therefore, there is no need to query the SMF associated with the session #A from the BSF, which reduces the time delay caused by the query to the BSF.
  • the AMF initiates SM context modification to the SMF associated with the session #A, so that the SMF associated with the session #A performs the handover of the session #A from the 3GPP access technology to the non-3GPP access technology, so that the N5CW device can be connected to the 3GPP side
  • the established session #A is switched to the non-3GPP side.
  • Fig. 8 is a schematic flowchart of session establishment provided by an embodiment of the present application.
  • the method 800 shown in FIG. 8 may include the following steps.
  • the UE registers with the 5GC network through the 3GPP.
  • the UE sends a session establishment request message to the AMF.
  • the session establishment request message (such as PDU session establishment request message) is a NAS message.
  • the session establishment request message may include but not limited to: UE identifier (such as SUPI), identifier of session #A, first indication information, and N1 SM container.
  • UE identifier such as SUPI
  • identifier of session #A is the first identifier of the session #A.
  • the first indication information is used to indicate to the AMF that the session establishment request is initiated by the N5CW device.
  • the N1SM container includes the first indication information.
  • the first indication information is also used to indicate an address (such as address #A) where the session is stored in the UE context.
  • the AMF determines that the UE is an N5CW device according to the first indication information, and determines to store the address #A in the UE context.
  • the AMF determines that the UE is an N5CW device according to the first indication information; and according to the fact that the UE is an N5CW device, the address #A is stored in the UE context.
  • the UE may also send another indication information to the AMF, where the other indication information is used to indicate the address where the session is stored in the UE context.
  • the AMF sends an SM context establishment request message to the SMF.
  • the SM context establishment request message may include but not limited to: UE identifier (such as SUPI), session #A identifier (ie first identifier), first indication information, N1 SM container.
  • UE identifier such as SUPI
  • session #A identifier ie first identifier
  • first indication information N1 SM container.
  • the SM context establishment request message may not carry the first indication information; if the N1 SM container does not include the first indication information, then the SM context establishment request message may carry the first indication information 1. Instructions.
  • the SMF After receiving the SM context establishment request message, the SMF can perform the following operations: the SMF initiates policy association to the PCF, the SMF establishes an N4 session with the UPF, and the SMF registers the session in the UDM. Specifically, reference may be made to the prior art, which is not limited thereto.
  • the SMF sends an SM context establishment response message to the AMF.
  • the SM context establishment response message may include but not limited to: SM context ID, address #A, N1 SM container, N2 SM container.
  • the SMF determines that the session establishment process is initiated by the N5CW device, and carries address #A in the SM context establishment response message according to the first indication information. For example, according to the first indication information carried in the SM context establishment request message, or according to the first indication information carried in the N1 SM container, the SMF determines that the session establishment process is initiated by the N5CW device; according to the first indication information, the SMF sends The SM context establishment response message sent by the AMF carries the address #A.
  • the SMF determines that the session establishment process is initiated by the N5CW device, so the address #A is carried in the SM context establishment response message. For example, according to the first indication information carried in the SM context establishment request message, or according to the first indication information carried in the N1 SM container, the SMF determines that the session establishment process is initiated by the N5CW device; ), the SM context establishment response message sent by the SMF to the AMF carries the address #A.
  • the AMF saves the address #A in the context of the UE.
  • the AMF determines that the session establishment procedure is initiated by the N5CW device, and stores the address #A in the context of the UE according to the first indication information.
  • the AMF determines that the session establishment process is initiated by the N5CW device, so after receiving the address #A, it saves the address #A in the context of the UE.
  • the AMF can generate the first association relationship, and save the first association relationship in the context of the UE.
  • the first association relationship may include a relationship between the address #A and the first identifier of the session #A. Regarding the first association relationship, reference may be made to the foregoing description, which will not be repeated here.
  • the AMF sends a PDU session establishment acceptance message to the UE through the RAN.
  • the SMF can send the IP address assigned by the 5GC to the session #A to the AMF, and the AMF can store the IP address of the session #A in the UE context and generate the first association relation.
  • the AMF can determine the SMF associated with the session #A according to the locally saved IP address of the session #A and the first association relationship, and Initiate SM context modification to the SMF associated with the session #A, so that the SMF associated with the session #A performs the switching of the session #A from the 3GPP access technology to the non-3GPP access technology, so as to realize the establishment of the N5CW device on the 3GPP side session #A is handed over to the non-3GPP side.
  • Fig. 9 is a schematic flowchart of a method for session switching provided by another embodiment of the present application.
  • the method 900 shown in FIG. 9 can be used in a scenario where the AMF can determine the SMF associated with the session #A according to the subscription information associated with the session #A.
  • the method 900 shown in FIG. 9 may include the following steps.
  • the UE registers with the 5GC network through TWIF.
  • step 901 is similar to step 601 and will not be repeated here.
  • the UE sends a DHCP request message to the TWIF.
  • the DHCP request message includes address information and subscription information of session #A.
  • the address information is the IP address (namely address #A) allocated by the 5GC for session #A when the UE accesses through 3GPP.
  • the subscription information of session #A may be carried in the option field of the DHCP request message (for example, option 12: host name option defined in IETF RFC 2132).
  • the subscription information of session #A can be used by the AMF to find the SMF associated with session #A.
  • the subscription information of session #A may include but not limited to: data network name (DNN), slice information (such as S-NSSAI).
  • the TWIF determines that the UE initiates a session handover.
  • step 903 is similar to step 603 and will not be repeated here.
  • the TWIF sends a session establishment request message to the AMF.
  • the session establishment request message (such as the PDU session establishment request message) may include but not limited to: the identifier (such as the PDU session ID) of the session #A, the request type (request type), the access type, the address# in the DHCP request message A.
  • the subscription information of session #A is "existing PDU session", which indicates that an existing session or an existing session is to be switched.
  • the identifier of the session #A is the second identifier of the session #A, that is, the dedicated ID of the session established by the TWIF for the UE.
  • the access type is non-3GPP.
  • the session establishment request message initiated by the TWIF to the AMF is only an exemplary description, and this embodiment of the present application is not limited thereto.
  • any N2 message may be used in this embodiment of the present application.
  • the AMF determines the SMF according to the subscription information of the session #A.
  • the AMF associates with the SMF corresponding to the session #A according to the DNN and S-NSSAI carried in the session establishment request message.
  • the AMF sends an SM context modification request message to the SMF.
  • the SM context modification request message may include one or more of the following information: address #A, access type (that is, non-3GPP), and access technology type (RAT type).
  • address #A address #A
  • access type that is, non-3GPP
  • RAT type access technology type
  • the SMF can query the associated SM context according to the address #A. For example, the SMF can judge that the session #A already has an SM context according to the address #A carried in the SM context modification request message; the SMF can also judge that the session established on the 3GPP side is switched to the non-3GPP side by the N5CW device according to the RAT type; Further, the SMF can associate the SM context according to the address #A.
  • the SMF sends an SM policy association update message to the PCF.
  • the SMF initiates an N4 session modification process to the UPF based on the PCC rule.
  • the SMF sends a registration information modification request message to the UDM.
  • the SMF sends an SM context modification response message to the AMF.
  • the AMF sends a session establishment response message to the TWIF.
  • the TWIF sends a DHCP response message to the UE.
  • the SMF initiates a user plane resource release process on the 3GPP side.
  • steps 907-913 are similar to steps 608-614, and the difference is that in step 910, the following information can be carried in the SM context modification response message: SUPI, PDU session ID (value is 15), SM context ID, like this
  • SUPI Secure Digital
  • PDU session ID value is 15
  • SM context ID like this
  • the AMF can identify the session #A according to the above information, and modify the identifier of the session #A to the second identifier.
  • the UE can carry the IP address allocated by the 5GC for session #A and the subscription information of session #A in the DHCP address information, and the AMF can determine the SMF associated with the session #A according to the subscription information of session #A, and then The SMF queries the SM context of session #A, and performs the handover of session #A from 3GPP access technology to non-3GPP access technology, so as to implement the handover of session #A established by N5CW equipment on the 3GPP side to the non-3GPP side.
  • Fig. 10 is a schematic flowchart of a method for session switching provided by another embodiment of the present application.
  • the method 1000 shown in FIG. 10 may be used in a scenario where the AMF determines the SMF associated with the session #A based on the second identifier and the second association relationship of the session #A.
  • the method 1000 shown in FIG. 10 may include the following steps.
  • the UE registers with the 5GC network through the TWIF.
  • step 1001 is similar to step 601 and will not be repeated here.
  • the UE sends a DHCP request message to the TWIF.
  • the DHCP request message includes address information.
  • the address information may be any non-zero IP address.
  • the address information may be the IP address (i.e. address #A) allocated by the 5GC for session #A when the UE accesses through 3GPP; for another example, the address information may be the IP address allocated by the 5GC to any session of the UE when the UE accesses through 3GPP IP address.
  • address #B this address information is denoted as address #B hereinafter.
  • the TWIF determines that the UE initiates a session handover.
  • the TWIF sends a session establishment request message to the AMF.
  • the AMF determines to switch session #A from the 3GPP access technology to the non-3GPP access technology.
  • steps 1003-505 are similar to steps 603-105, and will not be repeated here.
  • the AMF determines the SMF according to the second identifier and the second association relationship of the session #A.
  • the second association relationship includes a relationship between the first identifier of the session #A and the second identifier of the session #A.
  • the second association relationship reference may be made to the foregoing description, which will not be repeated here.
  • the AMF may determine the first identifier of session #A according to the second identifier of session #A received in step 1004 and the second association relationship (such as the second association relationship stored in the UE context); further Specifically, the AMF can learn the SMF and the SM context ID associated with the session #A according to the first identifier of the session #A.
  • the AMF receives the first identifier of the session #A and the second identifier of the session #A from the SMF; the AMF may save the first identifier of the session #A in the UE context information.
  • the relationship between the ID and the second ID of session #A Specifically, it will be described later with reference to FIG. 11 .
  • the AMF sends an SM context modification request message to the SMF.
  • the SMF sends an SM policy association update message to the PCF.
  • the SMF initiates an N4 session modification process to the UPF based on the PCC rule.
  • the SMF sends a registration information modification request message to the UDM.
  • the SMF sends an SM context modification response message to the AMF.
  • the AMF sends a session establishment response message to the TWIF.
  • the TWIF sends a DHCP response message to the UE.
  • the SMF initiates a user plane resource release process on the 3GPP side.
  • steps 1007-1014 are similar to steps 607-614 and will not be repeated here.
  • the AMF can determine the SMF associated with the session #A according to the second identifier and the second association relationship of the session #A, and initiate an SM context modification to the SMF, and the SMF performs the session #A access from 3GPP Technology switching to non-3GPP access technology, so as to realize the switching of the session #A established by the N5CW device on the 3GPP side to the non-3GPP side.
  • Fig. 11 is a schematic flowchart of session establishment provided by another embodiment of the present application.
  • the method 1100 shown in FIG. 11 may include the following steps.
  • the UE registers with the 5GC network through the 3GPP.
  • step 1101 is similar to step 801 and will not be repeated here.
  • the UE sends a session establishment request message to the AMF.
  • the session establishment request message (such as PDU session establishment request message) is a NAS message.
  • the session establishment request message may include but not limited to: UE identifier (such as SUPI), identifier of session #A, first indication information, and N1 SM container.
  • UE identifier such as SUPI
  • identifier of session #A is the first identifier of the session #A.
  • the first indication information is used to indicate to the AMF that the session establishment request is initiated by the N5CW device.
  • the N1SM container includes the first indication information.
  • the first indication information is also used to indicate that the second identifier of the session #A is stored in the UE context.
  • the AMF determines that the UE is an N5CW device according to the first indication information, and determines to store the second identifier of the session #A in the UE context.
  • the second possible way is to pre-agree (such as predefined by the protocol) that for N5CW equipment, the second identifier of session #A is stored in the UE context. Based on this way, the AMF determines that the UE is an N5CW equipment according to the first indication information; and according to The UE is an N5CW device, so the second identifier of the session #A is stored in the UE context.
  • the UE may also send another indication information to the AMF, where the other indication information is used to indicate to store the second identifier of the session #A in the UE context.
  • the AMF sends an SM context establishment request message to the SMF.
  • step 1103 is similar to step 803 and will not be repeated here.
  • the SMF determines whether the session #A can be switched from the 3GPP side to the non-3GPP side according to the subscription information of the session #A.
  • the SMF stores the subscription information of the session #A, and the SMF determines whether the session #A can be handed over from the 3GPP side to the non-3GPP side according to the subscription information of the session #A.
  • SMF obtains the subscription information of session #A from UDM; UDM returns the subscription information of session #A to SMF; The subscription information of #A determines whether session #A can be handed over from the 3GPP side to the non-3GPP side.
  • the subscription information of session #A includes second indication information, and the second indication information is used to indicate whether session #A can be switched from the 3GPP side to the non-3GPP side; Determining whether the session #A can be switched from the 3GPP side to the non-3GPP side includes: the SMF determines whether the session #A can switch from the 3GPP side to the non-3GPP side according to the second indication information.
  • session #A can be switched from the 3GPP side to the non-3GPP side as an example.
  • the SMF can send a rejection message to the AMF, etc., without limitation.
  • the SMF sends an SM context establishment response message to the AMF.
  • the SMF determines that the session #A can be handed over from the 3GPP side to the non-3GPP side, then the SMF carries the second identifier of the session #A in the SM context establishment response message.
  • the SM context establishment response message may also include, but not limited to: SM context ID, and the first identifier of session #A.
  • the AMF saves the second identifier of the session #A in the context of the UE.
  • the AMF determines that the session establishment process is initiated by the N5CW device, and saves the second identifier of the session #A in the context of the UE according to the first indication information.
  • the AMF determines that the session establishment process is initiated by the N5CW device, so after receiving the address #A, it saves the second identifier of the session #A in the context of the UE.
  • the AMF sends a PDU session establishment acceptance message to the UE through the RAN.
  • the SMF can determine whether the session can be switched from the 3GPP access technology to the non-3GPP access technology according to the subscription information of the session.
  • the second identifier of the session #A is sent to the AMF, and the AMF may save the second identifier of the session #A in the UE context and generate a second association relationship.
  • the AMF can determine the SMF associated with the session #A according to the locally saved second identifier and the second association relationship of the session #A, And initiate SM context modification to the SMF associated with the session #A, so that the SMF associated with the session #A performs the switching of the session #A from the 3GPP access technology to the non-3GPP access technology, so as to implement the N5CW device on the 3GPP side
  • the established session #A is switched to the non-3GPP side.
  • the terminal device is used as the N5CW device to introduce a possible process for the N5CW device to register to the 5GC network through TWIF.
  • Fig. 12 is a schematic flow chart of registering and accessing the 5GC network of the N5CW device applicable to the embodiment of the present application.
  • the method 1200 shown in FIG. 12 may include the following steps.
  • Access network selection access network selection
  • the N5CW device selects a PLMN, which includes a trusted WLAN.
  • the N5CW device establishes a layer 2 connection (L2 connection) with the TWAP of the WLAN access network.
  • L2 connection layer 2 connection
  • the N5CW device associates with the selected trusted WLAN, and initiates an extensible authentication protocol (extensible authentication protocol, EAP) authentication process.
  • EAP extensible authentication protocol
  • the N5CW device sends a network access identity (network access identity, NAI) to the TWAP.
  • NAI network access identity
  • the N5CW sends the NAI to the TWAP.
  • the TWAP selects the TWIF, and sends an authentication authorization accounting (AAA) request message to the TWIF, and the request message includes the NAI.
  • AAA authentication authorization accounting
  • the TWAP may select the TWIF based on the NAI sent by the N5CW device.
  • the NAI includes the subscription concealed identifier (SUCI). If the N5CW device accesses the 5GC through the WLAN for the first time, the NAI includes the subscription concealed identifier (SUCI). If the N5CW device has connected to the 5GC through the 3GPP access technology before connecting to the 5GC through the WLAN, the NAI contains a 5G globally unique temporary identity (5G globally unique temporary identity, 5G-GUTI). The 5G-GUTI is allocated by the core network (such as AMF) when the N5CW device accesses the 5GC on the 3GPP side as a 5G UE. Regardless of whether the NAI contains SUCI or 5G-GUTI, the core network can map these two identifiers to the same subscription permanent identifier (SUPI). That is, whether the N5CW device first accesses the 5GC through a trusted WLAN, or accesses the 5GC as a 5G UE through the 3GPP access technology, the core network can recognize that they are the same terminal device.
  • SUPI subscription permanent identifier
  • the TWIF creates a 5GC registration request message instead of the N5CW device.
  • the parameters of the registration request are generally default parameters, that is, the parameters of the registration request message created by TWIF for all N5CW devices are the same.
  • the request type is "Initial Request”.
  • TWIF selects AMF.
  • the TWIF may select an AMF according to the NAI, and send an N2 message to the AMF.
  • the N2 message includes but not limited to: registration request, user location and access type.
  • the AMF sends an AAA key request (AAA key request) message to the AUSF.
  • AAA key request AAA key request
  • AMF triggers the authentication process, sends a request message to AUSF, and indicates the access type.
  • An EAP authentication process is initiated between the N5CW device and the AUSF.
  • the EAP message can be encapsulated in the NAS message and sent through the N2 interface.
  • the specific EAP authentication process is not limited in this embodiment of the application, for example, reference may be made to existing methods.
  • the AUSF sends an AAA key response (AAA key response) message to the AMF.
  • AAA key response AAA key response
  • the AUSF sends an EAP-success (EAP-success) message and the generated security anchor function (security anchor function, SEAF) key to the AMF.
  • EAP-success EAP-success
  • SEAF security anchor function
  • the AMF can obtain the access network (AN) key from the received SEAF key.
  • the AMF sends a NAS security mode command (security mode command, SMC) to the TWIF.
  • SMC security mode command
  • the selected full protection and encrypted NAS security algorithm can be set to empty.
  • TWIF sends NAS security mode completion (security mode complete) to AMF.
  • AMF After receiving the NAS security mode complete (security mode complete) message sent by TWIF, AMF can send a context request message to TWIF.
  • the AMF sends an N2 initial context setup request (N2 initial context setup request) message to the TWIF.
  • N2 initial context setup request N2 initial context setup request
  • AMF may also provide AN key to TWIF.
  • TWIF obtains the pairwise master key (pairwise master key, PMK) from the AN key, and sends PMK and EAP success message to TWAP, so that TWAP sends EAP success message to N5CW device.
  • the PMK key can be used to protect WLAN air interface communication.
  • a layer 2 or layer 3 connection is established between the TWAP and the TWIF, which is used to transmit the user plane data of the N5CW device to the TWIF.
  • the AMF sends a registration acceptance message to the TWIF.
  • the N5CW device has been connected to the WLAN access network and registered with the 5GC.
  • FIG. 6 to FIG. 12 in the embodiment of the present application are only for the convenience of those skilled in the art to understand the embodiment of the present application, and are not intended to limit the embodiment of the present application to the illustrated specific scenarios.
  • Those skilled in the art can obviously make various equivalent modifications or changes according to the examples in FIG. 6 to FIG. 12 , and such modifications or changes also fall within the scope of the embodiments of the present application.
  • session #A in the above-mentioned FIGS. 6 to 11 may be replaced with one or more sessions.
  • the aforementioned UE may be replaced by any device that does not support NAS signaling when accessed through a non-3GPP access technology.
  • the methods and operations implemented by the terminal device can also be implemented by components (such as chips or circuits) that can be implemented by the terminal device; in addition, the methods and operations implemented by the network device can also be implemented by It may be implemented by components (such as chips or circuits) that may be used in network equipment, and is not limited.
  • the embodiments of the present application further provide corresponding devices, and the device includes corresponding modules for executing the foregoing method embodiments.
  • the module can be software, or hardware, or a combination of software and hardware. It can be understood that the technical features described in the above method embodiments are also applicable to the following device embodiments.
  • Fig. 13 is a schematic block diagram of an apparatus for session switching provided by an embodiment of the present application.
  • the apparatus 1300 includes a transceiver unit 1310 and a processing unit 1320 .
  • the transceiver unit 1310 can implement a corresponding communication function, and the transceiver unit 1310 can also be a communication interface or a communication unit.
  • the processing unit 1320 can implement corresponding processing functions, such as processing instructions and/or data.
  • the device 1300 may further include a storage unit, which may be used to store instructions and/or data, and the processing unit 1320 may read the instructions and/or data in the storage unit, so that the device implements the aforementioned Method Example.
  • a storage unit which may be used to store instructions and/or data
  • the processing unit 1320 may read the instructions and/or data in the storage unit, so that the device implements the aforementioned Method Example.
  • the apparatus 1300 can be used to execute the actions performed by the terminal device in the above method embodiments.
  • the apparatus 1300 can be a terminal device or a component that can be configured in the terminal device, and the transceiver unit 1310 is used to execute the above method embodiments.
  • the processing unit 1320 is configured to perform operations related to processing on the terminal device side in the method embodiments above.
  • the apparatus 1300 can also be used to execute the actions performed by the network equipment (such as the mobility management network element, the session management network element, or the interoperability function network element) in the above method embodiments.
  • the apparatus 1300 can It is a network device or a component that can be configured on the network device.
  • the transceiver unit 1310 is used to perform operations related to sending and receiving on the network device side in the method embodiments above, and the processing unit 1320 is used to perform processing on the network device side in the method embodiments above. related operations.
  • the apparatus 1300 is configured to execute actions performed by a mobility management network element (such as an AMF) in the above method embodiments.
  • a mobility management network element such as an AMF
  • the transceiver unit 1310 is configured to receive a first message from an interoperable function network element, the first message is used to instruct switching of a session of the terminal device, and the session is a session established through a first access technology; the processing unit 1320, for determining the session management network element associated with the session; the transceiver unit 1310, for sending a second message to the session management network element, where the second message is used to indicate that the session is performed from the first access technology to the second access technology handover; wherein, the terminal device is a terminal device that does not support non-access stratum NAS signaling when accessing the core network through the second access technology.
  • the first message further includes the address of the session, and the address is the address allocated when the session is established through the first access technology; the processing unit 1320 is specifically configured to: obtain the first identifier of the session according to the address of the session, and the first identifier of the session The first identifier is the session identifier when the session is established through the first access technology; according to the first identifier of the session, the session management network element associated with the session is determined.
  • the transceiver unit 1310 is further configured to send a query message, where the query message includes the address of the session; and receive a response message, where the response message includes the first identifier of the session.
  • the processing unit 1320 is specifically configured to: determine the first identifier of the session according to the address of the session and the first association relationship, where the first association relationship includes a relationship between the address of the session and the first identifier of the session.
  • the transceiving unit 1310 is further configured to receive the address of the session from the session management network element when the session is established through the first access technology; the processing unit 1320 is further configured to add the context information of the terminal device according to the address of the session Establish the first association relationship in .
  • the processing unit 1320 is further configured to determine that the terminal device is a terminal device that does not support NAS signaling when accessing the core network through the second access technology.
  • the first message includes session-associated slice information and/or a data network name; the processing unit 1320 is specifically configured to determine a session-associated session management network element according to the session-associated slice information and/or a data network name.
  • the first message includes the second identifier of the session; the processing unit 1320 is specifically configured to: determine the first identifier of the session according to the second identifier of the session and the second association relationship, the second association relationship includes the first identifier of the session The relationship between the identifier and the second identifier of the session; according to the first identifier of the session, determine the session management network element associated with the session; wherein, the first identifier of the session is the session identifier when the session is established through the first access technology, and the session The second identifier of is the session identifier when the session is established through the second access technology.
  • the transceiving unit 1310 is further configured to receive the second identifier of the session from the session management network element when the session is established through the first access technology; the processing unit 1320 is further configured to, according to the second identifier of the session, perform The second association relationship is established in the context information of the device.
  • the processing unit 1320 is further configured to determine that the terminal device is a terminal device that does not support NAS signaling when accessing the core network through the second access technology.
  • the second identifier of the session is a default value.
  • the transceiving unit 1310 is further configured to receive indication information from the terminal device, where the indication information is used to indicate that the terminal device is a terminal device that does not support NAS signaling when accessing the core network through the second access technology.
  • the first message includes one or more of the following: request type, session address, and access type, where the address is an address allocated when the session is established through the first access technology.
  • the second message includes one or more of the following: request type, session address, access type, and access technology type, where the address is an address allocated when the session is established through the first access technology.
  • the first access technology is a Third Generation Partnership Project (3GPP) access technology
  • the second access technology is a non-3GPP access technology
  • the apparatus 1300 can implement the steps or processes corresponding to the execution of the mobility management network element (such as AMF) in the method embodiment according to the embodiment of the present application, and the apparatus 1300 can include the mobile management network A unit of method that is executed meta. Moreover, each unit in the apparatus 1300 and other operations and/or functions mentioned above are respectively for realizing the corresponding flow of the method embodiment in the mobility management network element in FIG. 5 to FIG. 12 .
  • the mobility management network element such as AMF
  • the apparatus 1300 is configured to perform the actions performed by the terminal device in the above method embodiments.
  • the processing unit 1320 is configured to establish a session through the first access technology; the transceiver unit 1310 is configured to send a request message to an interoperability function network element, the request message includes address information, and the address information is used to indicate switching sessions; wherein, the terminal device is a terminal device that does not support non-access stratum NAS signaling when accessing the core network through the second access technology.
  • the address information is an address of the session, and the address is an address allocated when the session is established through the first access technology.
  • the transceiver unit 1310 is further configured to receive a response message of the request message from the network element of the interoperability function, and the response message includes address information; the processing unit 1320 is further configured to receive an The address information is the same, and it is determined that the session switching is successful.
  • the transceiver unit 1310 is further configured to send indication information to a session management network element and/or a mobility management network element, where the indication information is used to indicate that the terminal device does not support NAS communication when accessing the core network through the second access technology. order terminal equipment.
  • the request message further includes slice information and/or a data network name associated with the session.
  • the apparatus 1300 may implement the steps or processes corresponding to the execution of the terminal device in the method embodiment according to the embodiment of the present application, and the apparatus 1300 may include a unit for executing the method executed by the terminal device in FIG. 5 to FIG. 12 . Moreover, each unit in the apparatus 1300 and the above-mentioned other operations and/or functions are respectively for realizing the corresponding flow of the method embodiment in the terminal device in FIG. 5 to FIG. 12 .
  • the device 1300 here is embodied in the form of functional units.
  • the term "unit” here may refer to an application specific integrated circuit (ASIC), an electronic circuit, a processor for executing one or more software or firmware programs (such as a shared processor, a dedicated processor, or a group processor, etc.) and memory, incorporated logic, and/or other suitable components to support the described functionality.
  • ASIC application specific integrated circuit
  • processor for executing one or more software or firmware programs (such as a shared processor, a dedicated processor, or a group processor, etc.) and memory, incorporated logic, and/or other suitable components to support the described functionality.
  • the apparatus 1300 may specifically be the terminal device in the above-mentioned embodiments, and may be used to execute various processes and/or steps corresponding to the terminal device in the above-mentioned method embodiments, or, Apparatus 1300 may specifically be the network device (such as AMF, SMF, TWIF, etc.) in the above-mentioned embodiments, and may be used to execute each process and/or step corresponding to the network device in the above-mentioned method embodiments. To avoid repetition, here No longer.
  • processing unit 1320 in the above embodiments may be implemented by at least one processor or processor-related circuits.
  • the transceiver unit 1310 may be implemented by a transceiver or transceiver-related circuits.
  • the storage unit can be realized by at least one memory.
  • the apparatus in FIG. 13 may be the network element or device in the foregoing embodiments, or may be a chip or a chip system, such as a system on chip (system on chip, SoC).
  • the transceiver unit may be an input-output circuit or a communication interface;
  • the processing unit is a processor or a microprocessor or an integrated circuit integrated on the chip. It is not limited here.
  • FIG. 14 is an apparatus 1400 for session handover provided by an embodiment of the present application.
  • the device 1400 includes a processor 1410, the processor 1410 is coupled with a memory 1420, the memory 1420 is used for storing computer programs or instructions and/or data, and the processor 1410 is used for executing the computer programs or instructions and/or data stored in the memory 1420, so that The methods in the above method embodiments are performed.
  • the apparatus 1400 includes one or more processors 1410 .
  • the apparatus 1400 may further include a memory 1420 .
  • the apparatus 1400 may include one or more memories 1420 .
  • the memory 1420 may be integrated with the processor 1410, or configured separately.
  • the apparatus 1400 may further include a transceiver 1430, and the transceiver 1430 is used for receiving and/or sending signals.
  • the processor 1410 is configured to control the transceiver 1430 to receive and/or send signals.
  • the apparatus 1400 is used to implement the operations performed by the terminal device in the above method embodiments.
  • the processor 1410 is configured to implement processing-related operations performed by the terminal device in the above method embodiments
  • the transceiver 1430 is configured to implement transceiving-related operations performed by the terminal device in the above method embodiments.
  • the apparatus 1400 is configured to implement the operations performed by the network device in the above method embodiments.
  • the processor 1410 is used to implement the processing-related operations performed by the mobility management network element (such as AMF) in the above method embodiments
  • the transceiver 1430 is used to implement the processing-related operations performed by the mobility management network element (such as AMF) in the above method embodiments. ) to perform sending and receiving related operations.
  • the processor 1410 is used to implement the processing-related operations performed by the session management network element (such as SMF) in the above method embodiment
  • the transceiver 1430 is used to implement the session management network element (such as SMF) in the above method embodiment.
  • SMF performs sending and receiving related operations.
  • the processor 1410 is used to implement the processing-related operations performed by the interoperable function network element (such as TWIF) in the above method embodiment
  • the transceiver 1430 is used to implement the processing-related operations performed by the interoperable function network element in the above method embodiment. (such as TWIF) to perform sending and receiving related operations.
  • FIG. 15 is a schematic diagram of a chip 1500 provided according to an embodiment of the present application.
  • the chip 1500 (or it may also be called a processing system, or it may also be called a chip system) includes a processor 1510, and the processor may be a processor integrated on the chip. Or a microprocessor or an integrated circuit.
  • the chip 1500 may further include a communication interface 1520, and the communication interface 1520 may also be an input/output circuit, or an input/output interface (input/output interface).
  • the device installed with the chip 1500 can implement the methods and functions of the embodiments of the present application.
  • the processor 1510 may be a processing circuit in a system-on-a-chip or a processing system, which controls a device installed with the system-on-a-chip or a processing system, and may also be coupled to a storage unit to invoke instructions in the storage unit, so that the device can implement
  • the communication interface 1520 can be the input and output circuit in the chip system or the processing system, output the information processed by the chip system, or input the data or signaling information to be processed into the chip system for processing .
  • the apparatus 1500 is used to implement the operations performed by the terminal device in the above method embodiments.
  • the processor 1510 is configured to implement processing-related operations performed by the terminal device in the above method embodiments
  • the communication interface 1520 is configured to implement transceiving-related operations performed by the terminal device in the above method embodiments.
  • the apparatus 1500 is configured to implement the operations performed by the network device in the above method embodiments.
  • the processor 1510 is used to implement the processing-related operations performed by the mobility management network element (such as AMF) in the above method embodiments
  • the communication interface 1520 is used to implement the processing related operations performed by the mobility management network element (such as AMF) in the above method embodiments. ) to perform sending and receiving related operations.
  • the processor 1510 is used to implement the processing-related operations performed by the session management network element (such as SMF) in the above method embodiment
  • the communication interface 1520 is used to implement the session management network element (such as SMF) in the above method embodiment.
  • SMF performs sending and receiving related operations.
  • the processor 1510 is used to implement the processing-related operations performed by the interoperable functional network element (such as TWIF) in the above method embodiment
  • the communication interface 1520 is used to implement the processing related operations performed by the interoperable functional network element in the above method embodiment. (such as TWIF) to perform sending and receiving related operations.
  • the embodiment of the present application also provides a computer-readable storage medium, on which computer instructions for implementing the method executed by the network device or the terminal device in the above method embodiments are stored.
  • the computer program when executed by a computer, the computer can implement the method performed by the network device in the foregoing method embodiments.
  • the computer when the computer program is executed by a computer, the computer can implement the method executed by the network terminal device in the above method embodiment.
  • the embodiments of the present application also provide a computer program product including instructions, which, when executed by a computer, enable the computer to implement the method performed by the network device or the terminal device in the above method embodiments.
  • An embodiment of the present application further provides a communication system, where the communication system includes the network device in the foregoing embodiments, or, the network device and a terminal device.
  • the communication system includes one or more of the mobility management network element (such as AMF), the session management network element (such as SMF), the interoperability function network element (such as TWIF), and the terminal device in the above embodiments.
  • the mobility management network element such as AMF
  • the session management network element such as SMF
  • the interoperability function network element such as TWIF
  • the terminal device in the above embodiments.
  • processors mentioned in the embodiment of the present application may be a central processing unit (central processing unit, CPU), and may also be other general purpose processors, digital signal processors (digital signal processor, DSP), application specific integrated circuits ( application specific integrated circuit (ASIC), off-the-shelf programmable gate array (field programmable gate array, FPGA) or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc.
  • a general-purpose processor may be a microprocessor, or the processor may be any conventional processor, or the like.
  • the memory mentioned in the embodiments of the present application may be a volatile memory and/or a nonvolatile memory.
  • the non-volatile memory can be read-only memory (read-only memory, ROM), programmable read-only memory (programmable ROM, PROM), erasable programmable read-only memory (erasable PROM, EPROM), electrically programmable Erases programmable read-only memory (electrically EPROM, EEPROM) or flash memory.
  • the volatile memory may be random access memory (RAM).
  • RAM random access memory
  • RAM can be used as an external cache.
  • RAM may include the following forms: static random access memory (static RAM, SRAM), dynamic random access memory (dynamic RAM, DRAM), synchronous dynamic random access memory (synchronous DRAM, SDRAM) , double data rate synchronous dynamic random access memory (double data rate SDRAM, DDR SDRAM), enhanced synchronous dynamic random access memory (enhanced SDRAM, ESDRAM), synchronous connection dynamic random access memory (synchlink DRAM, SLDRAM) and Direct memory bus random access memory (direct rambus RAM, DR RAM).
  • static random access memory static random access memory
  • dynamic RAM dynamic random access memory
  • DRAM synchronous dynamic random access memory
  • SDRAM synchronous DRAM
  • double data rate SDRAM double data rate SDRAM
  • DDR SDRAM double data rate SDRAM
  • ESDRAM enhanced synchronous dynamic random access memory
  • SLDRAM synchronous connection dynamic random access memory
  • Direct memory bus random access memory direct rambus RAM, DR RAM
  • the processor is a general-purpose processor, DSP, ASIC, FPGA or other programmable logic devices, discrete gate or transistor logic devices, or discrete hardware components
  • the memory storage module may be integrated in the processor.
  • memories described herein are intended to include, but are not limited to, these and any other suitable types of memories.
  • the disclosed devices and methods may be implemented in other ways.
  • the device embodiments described above are only illustrative.
  • the division of the units is only a logical function division. In actual implementation, there may be other division methods.
  • multiple units or components can be combined or May be integrated into another system, or some features may be ignored, or not implemented.
  • the mutual coupling or direct coupling or communication connection shown or discussed may be through some interfaces, and the indirect coupling or communication connection of devices or units may be in electrical, mechanical or other forms.
  • the units described as separate components may or may not be physically separated, and the components shown as units may or may not be physical units, that is, they may be located in one place, or may be distributed to multiple network units. Part or all of the units can be selected according to actual needs to implement the solutions provided in this application.
  • each functional unit in each embodiment of the present application may be integrated into one unit, each unit may exist separately physically, or two or more units may be integrated into one unit.
  • the computer can be a general purpose computer, a special purpose computer, a computer network, or other programmable devices.
  • the computer may be a personal computer, a server, or a network device.
  • the computer instructions may be stored in or transmitted from one computer-readable storage medium to another computer-readable storage medium, for example, the computer instructions may be transmitted from a website, computer, server or data center Transmission to another website site, computer, server, or data center by wired (eg, coaxial cable, optical fiber, digital subscriber line (DSL)) or wireless (eg, infrared, wireless, microwave, etc.).
  • 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 a data center integrated with one or more available media.
  • the available medium may be a magnetic medium (for example, a floppy disk, a hard disk, a magnetic tape), an optical medium (for example, DVD), or a semiconductor medium (for example, a solid state disk (solid state disk, SSD) etc.
  • the aforementioned available medium may include But not limited to: U disk, mobile hard disk, read-only memory (read-only memory, ROM), random access memory (random access memory, RAM), magnetic disk or optical disk and other media that can store program codes.

Landscapes

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

Abstract

La présente demande concerne un procédé et un appareil de commutation de session. Le procédé comprend les étapes suivantes : un élément de réseau de gestion de mobilité reçoit un premier message en provenance d'un élément de réseau à fonction d'interfonctionnement, le premier message étant utilisé pour ordonner la commutation d'une session d'un dispositif terminal, et la session étant une session établie au moyen d'une première technologie d'accès ; l'élément de réseau de gestion de mobilité détermine un élément de réseau de gestion de session associé à la session ; et l'élément de réseau de gestion de mobilité envoie un second message à l'élément de réseau de gestion de session, le second message étant utilisé pour ordonner la commutation de la session de la première technologie d'accès à une seconde technologie d'accès, le dispositif terminal étant un dispositif terminal qui ne prend pas en charge une signalisation de strate de non-accès (NAS) lors de l'accès à un réseau central au moyen de la seconde technologie d'accès. Au moyen du procédé, une session d'un dispositif terminal qui ne prend pas en charge l'accès de signalisation NAS à un réseau central peut être activée pour commuter d'une première technologie d'accès à une seconde technologie d'accès.
PCT/CN2022/139449 2021-12-20 2022-12-16 Procédé et appareil de commutation de session WO2023116556A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN202111560841.4A CN116321328A (zh) 2021-12-20 2021-12-20 会话切换的方法和装置
CN202111560841.4 2021-12-20

Publications (1)

Publication Number Publication Date
WO2023116556A1 true WO2023116556A1 (fr) 2023-06-29

Family

ID=86800044

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2022/139449 WO2023116556A1 (fr) 2021-12-20 2022-12-16 Procédé et appareil de commutation de session

Country Status (2)

Country Link
CN (1) CN116321328A (fr)
WO (1) WO2023116556A1 (fr)

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN110366215A (zh) * 2018-04-09 2019-10-22 华为技术有限公司 会话管理的方法、终端和核心网设备
CN111436087A (zh) * 2019-01-15 2020-07-21 电信科学技术研究院有限公司 一种pdu会话切换方法及其装置
WO2020149522A1 (fr) * 2019-01-15 2020-07-23 엘지전자 주식회사 Ue permettant l'établissement d'une session pdu et twif
CN115134875A (zh) * 2021-03-24 2022-09-30 华为技术有限公司 会话切换的方法和装置

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN110366215A (zh) * 2018-04-09 2019-10-22 华为技术有限公司 会话管理的方法、终端和核心网设备
CN111436087A (zh) * 2019-01-15 2020-07-21 电信科学技术研究院有限公司 一种pdu会话切换方法及其装置
WO2020149522A1 (fr) * 2019-01-15 2020-07-23 엘지전자 주식회사 Ue permettant l'établissement d'une session pdu et twif
CN115134875A (zh) * 2021-03-24 2022-09-30 华为技术有限公司 会话切换的方法和装置

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
ERICSSON: "Usage of PDU session identity for the PDU sessions requested by the TWIF", 3GPP DRAFT; C1-198760, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. CT WG1, no. Reno, NV (USA); 20191111 - 20191115, 14 November 2019 (2019-11-14), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France , XP051825181 *

Also Published As

Publication number Publication date
CN116321328A (zh) 2023-06-23

Similar Documents

Publication Publication Date Title
US11737045B2 (en) Connection processing method and apparatus in multi-access scenario
US20210076444A1 (en) Session Management Method, Apparatus, and System
WO2018161796A1 (fr) Procédé et appareil de traitement de connexion dans un scénario à accès multiple
WO2022199451A1 (fr) Procédé et appareil de commutation de session
CN113595911B (zh) 数据转发方法、装置、电子设备及存储介质
WO2021233340A1 (fr) Procédé et appareil d'enregistrement de réseau
US20240107417A1 (en) Communication method and apparatus
WO2023051430A1 (fr) Procédé et appareil de communication
US20220022023A1 (en) Method and Apparatus for Selecting Session Management Network Element
WO2023116556A1 (fr) Procédé et appareil de commutation de session
WO2023051427A1 (fr) Procédé et appareil de communication
WO2023051428A1 (fr) Procédé et appareil de transmission d'informations
WO2023185561A1 (fr) Procédé de communication et appareil de communication
WO2023185620A1 (fr) Procédé et appareil de communication
WO2023051431A1 (fr) Procédé et appareil de communication
WO2023142717A1 (fr) Procédé et appareil pour déterminer une politique de sélection d'itinéraire d'équipement utilisateur
WO2023160394A1 (fr) Procédé et appareil de communication
JP7473001B2 (ja) コアネットワークノード、端末、及びこれらの方法
WO2022205453A1 (fr) Procédé et appareil de sélection de réseau
WO2023160199A1 (fr) Procédé et appareil d'accès à un réseau de communication
US20240179661A1 (en) Deregistration Method and Communication Apparatus
WO2023185657A1 (fr) Procédé de communication et appareil de communication
TWI843376B (zh) 用於無線通訊的方法及使用者設備
WO2023071974A1 (fr) Système de communication, procédé de communication et dispositif de communication
WO2024027299A1 (fr) Procédé et dispositif de routage de message

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

Country of ref document: EP

Kind code of ref document: A1