WO2021203249A1 - Procédé et appareil de libération de session - Google Patents

Procédé et appareil de libération de session Download PDF

Info

Publication number
WO2021203249A1
WO2021203249A1 PCT/CN2020/083594 CN2020083594W WO2021203249A1 WO 2021203249 A1 WO2021203249 A1 WO 2021203249A1 CN 2020083594 W CN2020083594 W CN 2020083594W WO 2021203249 A1 WO2021203249 A1 WO 2021203249A1
Authority
WO
WIPO (PCT)
Prior art keywords
indication information
session
information
network slice
network
Prior art date
Application number
PCT/CN2020/083594
Other languages
English (en)
Chinese (zh)
Inventor
杨皓睿
付喆
Original Assignee
Oppo广东移动通信有限公司
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 Oppo广东移动通信有限公司 filed Critical Oppo广东移动通信有限公司
Priority to CN202080098378.3A priority Critical patent/CN115244980A/zh
Priority to PCT/CN2020/083594 priority patent/WO2021203249A1/fr
Publication of WO2021203249A1 publication Critical patent/WO2021203249A1/fr

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements

Definitions

  • This application relates to the field of communication technology, and in particular to a method and device for session release.
  • the protocol content considers an access and mobility management function (access and mobility management function, AMF) network element under the same tracking area list (Tracking Area). All access network devices in the List, TAL) support the same network slice scenario.
  • AMF access and mobility management function
  • TAL tracking area list
  • the Release17 standard protocol needs to study scenarios in which different access network devices in the same TAL under an AMF network element may support different network slices.
  • this scenario there may be situations in which only the access network device is replaced without replacing the AMF network element. Since the AMF network element cannot know which network slice established session needs to be released, how to release the session established on the network slice not supported by the access network device requires further research.
  • the embodiments of the present application provide a session release method and device, in order to achieve rapid release of a session established on a network slice that is not supported by an access network device, reduce signaling interaction in the session release process, and save signaling overhead.
  • an embodiment of the present application provides a session release method, including:
  • the terminal receives the first information from the access network device; the terminal determines according to the first information that the access network device does not support the first network slice; the terminal releases the first network slice established on the first network slice. Conversation.
  • the terminal receives signaling from the access network device to determine the network slice that the access network device does not support, which is beneficial to quickly release the session established on the network slice and reduce the number of sessions during the release process.
  • the signaling interaction saves signaling overhead.
  • an embodiment of the present application provides a session release method, including:
  • the access network device sends second information to the access and mobility management function AMF network element, where the second information includes fourth indication information and fifth indication information, and the fourth indication information is used to indicate the access network
  • the device does not support the first network slice, and the fifth indication information is used to indicate to release the protocol data unit session identifier of the first session established on the first network slice.
  • the access network device sends signaling to the AMF network element to notify that the network slice does not support and the session identifier established on the network slice, which is beneficial to quickly release the network slice that the access network device does not support.
  • the session established on the previous session reduces the signaling interaction during the session release process and saves signaling overhead.
  • an embodiment of the present application provides a session release method, including:
  • the access and mobility management function AMF network element receives second information from an access network device, where the second information includes fourth indication information and fifth indication information, and the fourth indication information is used to indicate the access The network device does not support the first network slice, and the fifth indication information is used to instruct to release the protocol data unit session identifier of the first session established on the first network slice.
  • the AMF network element receives the signaling from the access network device to learn that the network slice does not support and the session identifier established on the network slice, which is beneficial to quickly release the network that the access network device does not support. Sessions established on slices reduce signaling interaction during session release and save signaling overhead.
  • an embodiment of the present application provides a session release method, including:
  • the session management function SMF network element receives the sixth indication information and the seventh indication information from the access and mobility management function AMF network element, where the sixth indication information is used to indicate that the access network device does not support the first network slice, so The seventh indication information is used to indicate to release the protocol data unit session identifier of the first session established on the first network slice.
  • the SMF network element receives the indication information from the AMF network element to learn that the network slice does not support and the session identifier established on the network slice, which is beneficial to quickly release the network slice that the access network device does not support.
  • the session established on the previous session reduces the signaling interaction during the session release process and saves signaling overhead.
  • an embodiment of the present application provides a session release device, which is applied to a terminal.
  • the device includes a processing unit and a communication unit, and the processing unit is configured to: receive a first session from an access network device through the communication unit. Information; according to the first information, it is determined that the access network device does not support the first network slice; the first session established on the first network slice is released.
  • an embodiment of the present application provides a session release device, which is applied to an access network device.
  • the device includes a processing unit and a communication unit, and the processing unit is configured to communicate with access and mobility through the communication unit.
  • the management function AMF network element sends second information, where the second information includes fourth indication information and fifth indication information, and the fourth indication information is used to indicate that the access network device does not support the first network slice.
  • the fifth indication information is used to indicate to release the protocol data unit session identifier of the first session established on the first network slice.
  • an embodiment of the present application provides a session release device, which is applied to an access and mobility management function AMF network element.
  • the device includes a processing unit and a communication unit, and the processing unit is configured to: Receiving second information from an access network device, where the second information includes fourth indication information and fifth indication information, where the fourth indication information is used to indicate that the access network device does not support the first network slice, so The fifth indication information is used to instruct to release the protocol data unit session identifier of the first session established on the first network slice.
  • an embodiment of the present application provides a session release device, which is applied to a session management function SMF network element.
  • the device includes a processing unit and a communication unit, and the processing unit is configured to: And the sixth indication information and the seventh indication information of the mobility management function AMF network element, the sixth indication information is used to indicate that the access network device does not support the first network slice, and the seventh indication information is used to indicate the release of the The protocol data unit session identifier of the first session established on the first network slice.
  • an embodiment of the present application provides a terminal, including a processor, a memory, a communication interface, and one or more programs, wherein the one or more programs are stored in the memory and are configured by The processor executes, and the program includes instructions for executing the steps in any method of the first aspect of the embodiments of the present application.
  • an embodiment of the present application provides an access network device, including a processor, a memory, a communication interface, and one or more programs, wherein the one or more programs are stored in the memory and are The configuration is executed by the processor, and the program includes instructions for executing steps in any method in the second aspect of the embodiments of the present application.
  • an embodiment of the present application provides an access and mobility management function AMF network element, including a processor, a memory, a communication interface, and one or more programs, wherein the one or more programs are stored in In the memory and configured to be executed by the processor, the program includes instructions for executing steps in any method of the third aspect of the embodiments of the present application.
  • the embodiments of the present application provide a session management function SMF network element, including a processor, a memory, a communication interface, and one or more programs, wherein the one or more programs are stored in the memory , And configured to be executed by the processor, and the program includes instructions for executing steps in any method of the fourth aspect of the embodiments of the present application.
  • an embodiment of the present application provides a chip, including: a processor, configured to call and run a computer program from a memory, so that the device installed with the chip executes the same as the first aspect and the first aspect of the embodiment of the present application. Part or all of the steps described in any method of the second aspect, the third aspect, and the fourth aspect.
  • embodiments of the present application provide a computer-readable storage medium, wherein the computer-readable storage medium stores a computer program for electronic data exchange, wherein the computer program is operable to cause a computer to execute Part or all of the steps described in any method of the first aspect, second aspect, third aspect, and fourth aspect of the embodiments of the present application.
  • an embodiment of the present application provides a computer program, wherein the computer program is operable to cause a computer to execute any of the first, second, third, and fourth aspects of the embodiments of the present application. Some or all of the steps described in the method.
  • the computer program may be a software installation package.
  • FIG. 1 is a schematic diagram of the architecture of a communication system related to an embodiment of the present application
  • FIG. 2 is a schematic diagram of a network architecture based on network slicing provided by an embodiment of the present application
  • FIG. 3 is a schematic diagram of the architecture of a communication scenario provided by an embodiment of the present application.
  • FIG. 4 is a schematic flowchart of a session release method provided by an embodiment of the present application.
  • FIG. 5 is a schematic flowchart of another session release method provided by an embodiment of the present application.
  • FIG. 6 is a schematic flowchart of another session release method provided by an embodiment of the present application.
  • FIG. 7 is a schematic flowchart of another session release method provided by an embodiment of the present application.
  • FIG. 8 is a schematic flowchart of another session release method provided by an embodiment of the present application.
  • FIG. 9 is a block diagram of functional units of a session release device provided by an embodiment of the present application.
  • FIG. 10 is a block diagram of functional units of another session release device provided by an embodiment of the present application.
  • FIG. 11 is a block diagram of functional units of yet another session release device provided by an embodiment of the present application.
  • FIG. 12 is a block diagram of functional units of yet another session release device provided by an embodiment of the present application.
  • FIG. 13 is a schematic structural diagram of a terminal provided by an embodiment of the present application.
  • FIG. 14 is a schematic structural diagram of an access network device provided by an embodiment of the present application.
  • 15 is a schematic diagram of the structure of an access and mobility management function network element provided by an embodiment of the present application.
  • FIG. 16 is a schematic structural diagram of a network element with a session management function provided by an embodiment of the present application.
  • the technical solutions of the embodiments of the present application can be applied to a wireless communication system.
  • the wireless communication system can include a non-terrestrial network (NTN) system, a long term evolution (LTE) system, and an LTE frequency division dual system.
  • NTN non-terrestrial network
  • LTE long term evolution
  • LTE frequency division dual system Frequency division duplex (FDD) system, LTE time division duplex (TDD), fifth generation (5G) new radio (NR) communication system or future evolution communication system.
  • FDD Frequency division duplex
  • TDD LTE time division duplex
  • NR fifth generation
  • future evolution communication system for example, the wireless communication system is a 5G NR communication system, please refer to Figure 1.
  • the example communication system 100 includes a terminal 110, an access network device 120, an access and mobility management function (AMF) network element 130, and a session management function (SMF).
  • Network element 140 user plane function (UPF) network element 150, and network slice selection function (network slice selection function, NSSF) network element 160.
  • the AMF network element 130, the SMF network element 140, the UPF network element 150, and the NSSF network element 160 belong to the core network element (or called the network function network element).
  • the core network element or called the network function network element.
  • the connection between the above-mentioned various network elements can be a wireless connection or a wired connection.
  • Figure 1 uses a solid line to indicate that the interfaces between the various network elements are in the existing It has been described in detail in the technology, and this is not described in detail in the embodiments of the present application.
  • the terminal 110 in the embodiment of the present application may include user equipment (UE), user terminal, handheld terminal, notebook computer, subscriber unit, cellular phone, and smart phone. ), wireless data cards, personal digital assistant (PDA) computers, and can also include vehicle equipment, vehicle terminals, vehicle equipment, or automotive equipment.
  • the terminal 110 may also be a cellular phone, a cordless phone, a session initiation protocol (session initiation protocol, SIP) phone, a wireless local loop (WLL) station, a personal digital assistant (personal digital assistant, PDA), and wireless communication.
  • PLMN public land mobile network
  • the terminal 110 includes a hardware layer, an operating system layer running on the hardware layer, and an application layer running on the operating system layer.
  • the hardware layer includes hardware such as a central processing unit (CPU), a memory management unit (MMU), and memory (also referred to as main memory).
  • the operating system may be any one or more computer operating systems that implement business processing through processes, for example, Linux operating systems, Unix operating systems, Android operating systems, iOS operating systems, or Windows operating systems.
  • the application layer includes applications such as browsers, address books, word processing software, and instant messaging software.
  • the embodiments of the present application do not specifically limit the specific structure of the execution subject of the methods provided in the embodiments of the present application, as long as the programs that record the codes of the methods provided in the embodiments of the present application can be provided according to the embodiments of the present application.
  • the execution subject of the method provided in the embodiment of the present application may be the terminal 110, or a functional module in the terminal 110 that can call and execute the program.
  • the access network device 120 can be regarded as a radio access network (RAN) device or an access network (access network, AN) device, which is mainly responsible for radio resource management and quality of service on the air interface side. service, QoS) management, data compression and encryption.
  • the access network device 120 may include various forms of base stations, such as: macro base stations, micro base stations, relay stations, access points (access points, AP), and so on. In communication systems using different wireless access technologies, the names of devices with base station functions may be different.
  • next generation node B gNB
  • next generation evolved node B ng-eNB
  • LTE Long Term Evolution
  • eNB evolved NodeB
  • NodeB NodeB
  • the AMF network element 130 is distributed in the core network, and is mainly responsible for the signaling processing part, and can also provide control plane functions, such as access control, mobility management, attachment and detachment, and gateway selection.
  • control plane functions such as access control, mobility management, attachment and detachment, and gateway selection.
  • the AMF network element 130 provides services for the session in the terminal 110, the AMF network element provides control plane storage resources for the session to store the session identifier and the session management function associated with the session identifier. , SMF) network element identification, etc.
  • the SMF network element 140 may be used to be responsible for user plane network element selection, user plane network element redirection, IP address allocation, bearer establishment, modification and release, and QoS control.
  • the UPF network element 150 may be used to be responsible for forwarding and receiving user data in the terminal 110.
  • the UPF network element 150 receives user data from the data network and transmits it to the terminal 110 through the access network device 120; or, the UPF network element 150 receives user data from the terminal 110 through the access network device 120, and then forwards it to the data network.
  • the SMF network element 140 manages and controls the transmission resources and scheduling functions of the UPF network element 150 that provide services for the terminal 110.
  • the NSSF network element 160 may be used to select a network slice for the terminal 110, determine network slice selection assistance information (NSSAI), and determine the AMF network element 130 serving the terminal 110, and so on.
  • NSSAI network slice selection assistance information
  • Network slicing is a combination of network functions and resources required to complete certain or certain services, and is a complete logical network. Network slicing can flexibly allocate and redistribute resources according to user needs, which can be understood as meeting a variety of software-defined functions through the same set of hardware.
  • network slicing is defined in a PLMN, which may include network function network elements of the core network control plane and the user plane.
  • the NSSAI may include one or more single network slice selection assistance information (S-NSSAI), and the network slice may be identified by the S-NSSAI.
  • S-NSSAI single network slice selection assistance information
  • ID represents the S-NSSAI used to identify the network slice.
  • an S-NSSAI consists of a slice/service type (Slice/Serive Type, SST) and a slice differential (Slice Differentiator, SD). SST is used to identify the slice type. It is mandatory information in S-NSSAI.
  • the length is 8 bits and the value range is 0 to 255.
  • the standardized SST value provides a way to establish global interoperability of slices so that PLMN can more effectively support roaming for the most commonly used slices/service types.
  • the standardized SST value can indicate enhanced mobile broadband (eMBB), ultra-reliable low latency communications (URLLC), massive machine type communication (mMTC), and in-vehicle communications. Communication (vehicle to everything, V2X). SD can be used as a supplement to SST to distinguish multiple network slices under the same SST. It is optional information in S-NSSAI and has a length of 24 bits.
  • one network slice instance can be related to one or more S-NSSAIs, or one S-NSSAI can be related to one or more network slice instances.
  • S-NSSAI when an S-NSSAI is related to multiple network slice instances, one of the multiple network slice instances serves the terminal that is allowed to use this S-NSSAI, and the multiple network slice instances can Deploy in the same or different tracking areas (tracking areas, TA).
  • tracking areas TA
  • the AMF network element serving the terminal may logically belong to the multiple network slice instances related to the S-NSSAI, that is, the multiple networks
  • the slice instance may include the same AMF network element.
  • the network may use only one network slice instance related to the S-NSSAI to serve the terminal at any time, unless the network slice instance is no longer valid in a given registration area or the terminal stores the allowed NSSAI (allowed NSSAI) changes, etc.
  • the multiple network slice instances can be referred to as network slice instances included in the network slice marked by the S-NSSAI, that is, the multiple network slice instances belong to the Network slicing.
  • a network slice instance identifier network slice instance identifier, NSI ID
  • NSI ID network slice instance identifier
  • Each network slice instance may include a group of network function network elements, and different network slice instances usually include different groups of network function network elements.
  • the group of network function network elements may include the AMF network element 130, SMF network element 140, and UPF network element 150 in FIG. 1, and the different group of network function network elements may also include the same network function network element.
  • different network slice instances can correspond to the same AMF network element or SMF network element.
  • each network slice may include a group of network function network elements, and the group of network function network elements may be considered as a collection of network function network elements included in all network slice instances belonging to the network slice.
  • a network slice instance or network slice includes one network function network element, it can be considered that the network function network element supports the network slice instance or network slice.
  • a network slice instance includes an AMF network element
  • the AMF network element supports the network slice instance.
  • network slices or network slice instances supported by each network function network element can be deployed in advance.
  • a network slice or network slice instance supported by one or some network function network elements may be updated, which is not specifically limited in the embodiment of the present application.
  • the terminal 110 may access multiple network slices, and may also access the same network slice based on one or more network slice instances.
  • the terminal 110 may establish one or more protocol data unit (PDU) sessions in one network slice instance, that is, each PDU session is established based on one network slice instance.
  • PDU protocol data unit
  • the network slice instance on which a PDU session is established is referred to as a PDU session established on the network slice instance, or a network slice instance related to the PDU session.
  • the network slice to which the network slice instance belongs is referred to as the network slice on which the PDU session is established, or the network slice related to the PDU session.
  • the PDU session is a connection between the terminal 110 and a data network (data network, DU) for providing PDU connection services
  • the connection type between the terminal 110 and the DU can be a network protocol (Internet protocol, IP) connection, Ethernet connection or unstructured data connection, etc.
  • IP Internet protocol
  • the PDU connection service supported by the 5G core network it generally refers to a service that provides PDU exchange between the terminal 110 and a DN determined by a data network name (DNN).
  • the terminal 110 can establish one or more PDU sessions to connect to the same DN or different DNs, and the terminal 110 can establish PDU sessions served by different UPF network elements 150 to connect to the same DN. .
  • a major feature of the 5G network architecture is network slicing, that is, the core network is divided into multiple network slices to provide customized services.
  • the following embodiments of the present application provide a schematic diagram of a network architecture based on network slicing, please refer to FIG. 2.
  • the AMF network element 130 is connected to the access network device 120, and communication is established between the access network device 120 and the terminal 110.
  • network slice 1 is identified by an S-NSSAI, which is related to network slice instance 11, network slice instance 12, and network slice instance 13;
  • network slice 2 is identified by an S-NSSAI, and this S-NSSAI is related to network slice Instance 21 is associated.
  • each of the above-mentioned network slice instances includes the same AMF network element 130, and each network slice instance includes SMF network elements and UPF network elements are different. Then, PDU session 1 is established on network slice instance 11, PDU session 2 is established on network slice instance 12, PDU session 3 is established on network slice instance 13, that is, PDU session 1, PDU is established on network slice 1. Session 2 and PDU session 3; PDU session 4 is established on network slice instance 21, that is, PDU session 4 is established on network slice 2. It should be noted that FIG.
  • FIG. 2 illustrates AMF network elements, SMF network elements, and UPF network elements included in each network slice instance, and of course, it may also include other core network network elements.
  • one PDU session can be established on each network slice in FIG. 2, or multiple PDU sessions can be established, and there is no specific limitation.
  • the communication scenario involved in the embodiment of the present application may be a scenario in which the access network device is replaced, or may be a scenario in which the access network device is not replaced.
  • the registration process, service request process, configuration update or handover process, etc. can be performed, while in the scenario where the access network equipment is not replaced, the registration process, service request process, configuration update, etc. can be performed .
  • the communication scenario involved in the embodiment of the present application may be a scenario where the AMF network element is replaced, or may be a scenario where the AMF network element is not replaced.
  • the registration process, the service request process, the configuration update process, the switching process, the session release process, etc. can be executed.
  • a scenario where the access network device is replaced but the AMF network element is not replaced may be considered, and the access network device does not support network slicing. Please refer to FIG. 3.
  • the terminal 310 is the terminal 110 described in Figure 1 above
  • the access network device 320 is the access network device 120 described in Figure 1 above.
  • the core network 330 includes the AMF network element 130 and the SMF network described in Figure 1 above. Yuan 140, UPF network element 150, NSSF network element 160 and so on.
  • the access network device 320 includes a source access network device 320A and a target access network device 320B, and they are connected to the same AFM network element, that is, only the access network device is replaced but the AMF network element is not replaced.
  • the source access network device 320A supports network slices 1 and 2
  • the target access network device 320B supports network slices 2 and 3.
  • the target access network device 320B Since the terminal 310 moves from the source access network device 320A to the target access network device 320B, the target access network device 320B does not support the network slice 1 provided by the source access network device 320A. At this time, the AFM network element may not know that the target access network device 320B does not support network slice 1, and cannot know that the PDU session established on network slice 1 needs to be released.
  • a method of registering multiple tracking areas (Tracking Area, TA) is adopted, and multiple TAs are formed into a tracking area list (Tracking Area List, TAL).
  • the AMF network element When the terminal accesses the network through registration, the AMF network element will allocate the TAL to the terminal, and the terminal does not need to perform TA update when it moves in the area within the TAL.
  • each cell belongs to only one TA, and its broadcast message only needs to broadcast the information of one TA.
  • the 3GPP Release15 standard protocol assumes that all access network devices in the same TAL under an AMF network element support the same network slice, when the terminal moves to a new TAL, if the new AMF does not support a certain network slice , The new AMF network element triggers the old AMF network element to release the session established on the network slice.
  • the Release17 standard protocol needs to study scenarios in which different access network devices in the same TAL under an AMF network element may support different network slices.
  • this scenario there may be situations in which only the access network device is replaced without replacing the AMF network element. Since the AMF network element cannot know which network slice established session needs to be released, how to release the session established on the network slice not supported by the access network device requires further research.
  • FIG. 4 is a schematic flowchart of a session release method provided by an embodiment of the present application, and the method includes:
  • the access network device sends the first information to the terminal.
  • the first information may be newly added signaling in the 5G communication standard, and the newly added signaling may be used to indicate each network slice identification (indentify, ID) supported by the access network device, and each network slice The identification can be the S-NSSAI of each network slice.
  • the first information may also be messages or information specified in the prior art, such as system information, RRC messages, paging messages, RRC connection reconfiguration messages, handover commands, non-access stratum (NAS) messages , An access network (access network, AN) message, etc., and the message or information specified in the prior art may carry indication information for indicating the identifier of each network slice supported by the access network device.
  • the access network device in the embodiment of the present application can be determined according to different system processes and communication scenarios. For example, when the terminal moves to a new cell, if the embodiment of the application is applied to the registration process or the service request process, the access network device may be the access network device corresponding to the new cell; if the embodiment of the application is applied to the session release In the process, handover process, or configuration update process, the access network device may be the access network device corresponding to the old cell or the access network device corresponding to the new cell.
  • the first information may be determined by the current connection management status of the terminal.
  • the connection management may include establishing and releasing the signaling connection of the N1 interface between the terminal and the AMF, that is, the connection management may be used to establish and release the signaling between the terminal and the AMF network element.
  • the signaling connection can include the AN message connection between the terminal and the access network device, and the N2 message connection between the access network device and the AMF. That is, the signaling connection can be used between the terminal and the AMF network element. NAS message exchange.
  • the current connection management state of the terminal may include an idle state (CM-IDLE) and a connected state (CM-CONNECTED).
  • CM-IDLE an idle state
  • CM-CONNECTED a connected state
  • the terminal does not establish a NAS message connection with the AMF through the N1 interface.
  • the terminal can perform cell selection, cell reselection, and PLMN selection.
  • the terminal can establish a NAS message connection to the AMF by initiating a service request or registration process.
  • an AN message connection is established between the terminal and the access network device, the terminal can switch from the idle state to the connected state.
  • the transmission of the initial NAS message (registration request, service request or de-registration request) can also trigger the terminal to switch from the idle state to the connected state.
  • the first information can be determined by the current connection management status of the terminal. For example, when the terminal enters a new cell, if the terminal is currently in an idle state, the terminal can receive the system information broadcasted by the access network equipment corresponding to the new cell; if the terminal is currently in the connected state, the terminal can receive the corresponding information from the old cell. RRC messages, RRC connection reconfiguration messages or handover commands of the access network equipment.
  • the terminal After receiving the first information, the terminal determines, according to the first information, that the access network device does not support the first network slice.
  • the fact that the access network device does not support the first network slice can be understood as the first network slice or the first network slice identifier (identify, ID) currently not deployed on the access network device.
  • the first network slice may include one network slice or multiple network slices, and the first network slice identifier may be one or more S-NSSAIs of the first network slice.
  • the received signaling will be different, which also affects how the terminal determines the network slice supported by the access network device.
  • the situations in which the terminal is in the idle state and the connected state will be introduced respectively.
  • the first indication information is carried in system information.
  • the first allowed network slice identifier is notified by the AMF network element during the registration of the terminal to the network, and the first allowed network slice identifier may be an allowed NSSAI, or may be one or more of the network slices. S-NSSAI. That is to say, the first allowed network slice identifier can be used to indicate one or more network slices that the terminal is allowed to access, and the terminal can be served by the network slice corresponding to the first allowed network slice identifier, such as in the network One or more PDU sessions are established on the slice.
  • the terminal when the terminal is in an idle state, the terminal receives the system information broadcast by the access network device, and learns each network slice identifier supported by the access network device through the first indication information carried in the system information.
  • the network slice identifier may be the S-NSSAI of the network slice.
  • the RRC layer of the terminal sends the identifier of each network slice to the NAS layer of the terminal.
  • the NAS layer of the terminal compares the identifier of each network slice with the first allowed network slice identifier currently stored by the terminal. If the first network slice identifier is in the first allowed network slice identifier but not in each network slice identifier, the terminal learns that the access network device does not support the first network slice.
  • the NAS layer of the terminal compares the identifier of each network slice with the network slice identifier of the PDU session currently established by the terminal. If the first network slice identifier is in the network slice identifier of the currently established PDU session, but not in each network slice identifier, the terminal learns that the access network device does not support the first network slice.
  • one or more PDU sessions may or may not be established on the first network slice. Therefore, after the NAS layer of the terminal confirms that the access network device does not support the first network slice, the NAS layer of the terminal It can also be determined whether the first session is established on the first network slice. Wherein, the first session may include one or more PUD sessions.
  • the first session is not established on the first network slice, it means that the access network device and the core network element have not established the context and related resources of the first session.
  • the first session in the AMF network element does not occupy control plane resources.
  • the first session in the SMF network element does not occupy control plane resources, and the first session in the UPF network element does not occupy user plane transmission resources, which does not cause waste of the foregoing resources. Therefore, the terminal does not need to enter the connected state from the idle state, but only marks that the access network device does not support the first network slice, and there is no need to establish a PDU session on the first network slice in the subsequent process.
  • the terminal since the terminal may move to a new cell before entering the connected state next time, and the network slices that the access network device corresponding to the new cell may support may also change, the terminal does not need to return to the connected state. Only when the terminal has uplink data or signaling to be sent, the terminal enters the connected state again, and after entering the connected state, the AMF network element notifies the new second allowed network slice identifier.
  • a first session is established on the first network slice, since the terminal may still establish a connection with the DN through the first session, and the access network device does not support the first session, this will result in communication established by the first session Failed to send or receive business data on the connection.
  • the core network element may still establish the context and related network resources of the first session, for example, the control plane resources occupied by the first session in the AMF network element. It can be seen that not releasing the session established on the network slice that the access network device does not support will not only lead to the failure of service data transmission, but also the waste of network resources.
  • the terminal may switch from the idle state to the connected state and then release the first session. Therefore, the terminal can establish an AN signaling connection between the terminal and the access network device through the registration process or the service request process, so that the terminal enters the connected state, and the core network element performs the session release.
  • the terminal currently in the idle state needs to release the first session by the interaction of the access network device, the AMF network element, and the SMF network element.
  • the terminal sends a first RRC message to the access network device.
  • the first RRC message may carry a registration request.
  • the first registration request may carry indication information indicating that the access network device does not support the first network slice, and may carry the first network slice.
  • the network slice identifier of a network slice may also carry the PDU session identifier of the first session or a bitmap indicating the PDU session.
  • the registration request can carry the PDU session status (status) parameter, which can be used for the terminal and the AMF network element to synchronize the existing PDU session, and the parameter can be in the form of a bitmap, such as bit1-8, each A bit can correspond to a PDU session. If a PDU session exists, the corresponding bit of the PDU session is set to 1, otherwise it is set to 0. Then, the access network device receives the first RRC message, and sends a first N2 message to the AMF network element, where the first N2 message may carry the first registration request.
  • the PDU session status (status) parameter can be used for the terminal and the AMF network element to synchronize the existing PDU session
  • the parameter can be in the form of a bitmap, such as bit1-8, each A bit can correspond to a PDU session. If a PDU session exists, the corresponding bit of the PDU session is set to 1, otherwise it is set to 0. Then, the access network device receives the first RRC message, and sends
  • the AMF network element triggers a session release request, and sends a first session release request to the SMF network element, where the first session release request is used to request the release of the first session.
  • the SMF network element receives the first session release request, executes the PDU session release procedure to release the context and related resources of the first session on the terminal and the AMF network element, and sends a first session release response to the AMF network element. Then, the AMF network element receives the first session release response, releases the control plane resources of the first session, and sends a first NAS message to the terminal.
  • the first NAS message may be a registration acceptance (registration acceptance), and the registration agreement may carry
  • the new allowed network slice identifier may also carry indication information for instructing the terminal to release the first session, for example, use a bitmap indicating the PDU session.
  • the terminal receives the registration consent, obtains a new allowed network slice identifier, and releases the context of the first session.
  • the first session of the terminal that is currently in the idle state needs to release the first session is realized by the interaction of the access network device, the AMF network element, and the SMF network element.
  • the terminal sends a second RRC message to the access network device.
  • the second RRC message may carry a first service request.
  • the first service request may carry indication information indicating that the access network device does not support the first network slice.
  • the network slice identifier that carries the first network slice may also carry the PDU session identifier of the first session or a bitmap indicating the PDU session. It should be noted that the PDU session status parameter can be carried in the service request.
  • This parameter can be used for the terminal and the AMF network element to synchronize the existing PDU session, and the parameter can be in the form of bitmap, such as bit1-8, each bit can correspond to One PDU session. If a PDU session exists, the corresponding bit of the PDU session is set to 1, otherwise it is set to 0. Then, the access network device receives the second RRC message, and sends a second N2 message to the AMF network element, where the second N2 message may carry the first service request. Secondly, after receiving the second N2 message, the AMF network element triggers a session release request and sends a second session release request to the SMF network element. The second session release request is used to request the release of the first session.
  • bitmap such as bit1-8
  • the SMF network element receives the second session release request, executes the PDU session release procedure to release the context and related resources of the first session on the terminal and the AMF network element, and sends a second session release response to the AMF network element. Then, the AMF network element receives the second session release response, releases the control plane resources of the first session, and sends a second NAS message to the terminal.
  • the second NAS message may be a service acceptance message, and the service reception message may carry an instruction terminal Indication information of whether to release the first session.
  • the AMF network element sends a third NAS message to the terminal.
  • the third NAS message may be a configuration update command.
  • the configuration update command may carry indication information indicating a new allowed network slice identifier, or it may carry indication information indicating that the terminal releases the first Instructions for a session. Finally, the terminal receives the configuration update command, obtains the new allowed network slice identifier, and releases the context of the first session.
  • the flow chart of the session release method shown in FIG. 4 may also be as shown in FIG. 7.
  • the fourth information may be the aforementioned first RRC message or the second RRC message.
  • the fifth information may be the above-mentioned first NAS message
  • the third session release request may be the above-mentioned first session release request
  • the third session release response may be
  • the sixth information may be the foregoing first NAS message
  • the fourth information is the second RRC message
  • the fifth information may be the foregoing second N2 message.
  • the third session release request may be the above-mentioned second session release request
  • the third session release response may be the above-mentioned second session release response
  • the sixth information may be the above-mentioned second NAS message
  • the seventh message may be the above-mentioned The third NAS message.
  • the first information when the current connection management state of the terminal is the connected state, the first information may include second indication information and/or third indication information, and the second indication information may be used to indicate the access network device
  • the access network device may be the target access network device
  • the third indication information may be used to indicate the release of the PDU session identifier of the first session.
  • the second indication information may be a cause value, and the cause value indicates that the access network device does not support the first network slicing, and the access network device may be the target access network device.
  • the second indication information and/or the third indication information are carried in the RRC message.
  • the RRC message may be a handover command or an RRC connection reconfiguration message. It is understandable that after the terminal moves from the source access network device to the target access network device, a handover process is required. At this time, the terminal receives the handover command or the RRC connection reconfiguration message sent by the source access network device.
  • the RRC layer of the terminal receives the RRC message from the access network device, and learns the access through the second indication information and/or third indication information carried in the RRC message Network slices that are not supported by the network device, and the PDU session identifier that needs to be released, that is, the PDU session identifier of the first session. Then, the RRC layer of the terminal sends the second indication information and/or the third indication information to the NAS layer, and the NAS layer deletes the context of the first session.
  • the terminal releases the first session established on the first network slice.
  • the access network device sends signaling to the terminal, and the terminal determines the network slice that the access network device does not support according to the information, which is beneficial to quickly release the session established on the network slice. , Which is beneficial to reduce signaling interaction during the session release process and save signaling overhead.
  • FIG. 8 An embodiment of the present application provides a schematic flowchart of another session release method, please refer to FIG. 8.
  • the access network device sends the second information to the AMF network element.
  • the second information may include fourth indication information and fifth indication information
  • the fourth indication information may be used to indicate that the access network device does not support the first network slice
  • the fifth indication information may be used to indicate the release of the first network slice. PDU session identifier of the first session established.
  • the fourth indication information may be a cause value, and the cause value indicates that the access network device does not support the first network slice.
  • the second information may be newly added signaling in the 5G communication standard, and the newly added signaling may include fourth indication information and fifth indication information.
  • the first information may also be a message specified in the prior art, such as an N2 message, a session release request, etc., and the fourth indication information and fifth indication information are carried in the message specified in the prior art.
  • the access network device in the embodiment of the present application may include a source access network device and a target access network device. It is understandable that when the terminal moves from the source access network device to the target access network device, a handover procedure needs to be performed. Because the access network equipment is different, this also leads to different executive bodies that trigger the session release to the AMF network element. The following is a specific introduction.
  • the source access network device can send the second information to the AMF network element
  • the source access network device learns that the target access network device does not support the first network slice
  • the source access network device The device initiates a session release process to the AMF network element.
  • the fourth indication information carried in the second information may be used to indicate that the target access network device does not support the first network slice.
  • the source access network device knows that the target access network device does not support the first network slice may exist in the following situations: through the information pre-configured when the network is deployed; through the switching process between the source access network device and the target access network device
  • the interactive signaling such as the indication information carried in the handover request confirmation, etc.
  • the indication information carried in the interactive signaling between the source access network device and the target access network device can be used to indicate each PDU session identifier of the target access network device, and then the source access network device The first network slice can be determined according to each PDU session identifier of the local end and the indication information.
  • the source access network device can trigger the session release process to the AMF network element during or after the handover process, which is not specifically limited in this application.
  • the target access network device can send the second information to the AMF network element.
  • the target access network device learns that the first network slicing is not supported, the target access network device sends the second information to the AMF network element. Initiate the session release process.
  • the fourth indication information carried in the second information may be used to indicate that the target access network device does not support the first network slice.
  • the target access network device learns that it does not support the first network slice there may be the following situations: through the information pre-configured when the network is deployed; through the interactive signaling between the source access network device and the target access network device in the handover process, For example, the instruction information carried in the handover request.
  • the indication information carried in the interactive signaling between the source access network device and the target access network device can be used to indicate each PDU session identifier of the source access network device, and then the target access network device The first network slice can be determined according to each PDU session identifier of the local end and the indication information.
  • the target access network device can trigger the session release process to the AMF network element during or after the handover process, which is not specifically limited in this application.
  • the access network device may also send the first information to the terminal before or after the first information to the AMF network element, and there is no specific limitation.
  • the specific description of the first information is as described above, and will not be described in detail.
  • the AMF network element After receiving the second information, the AMF network element sends sixth indication information and seventh indication information to the SMF network element.
  • the sixth indication information may be used to indicate that the access network device does not support the first network slice, and the seventh indication information may be used to indicate the release of the PDU session identifier of the first session.
  • the sixth indication information may be the fourth indication information carried in the second information
  • the seventh indication information may be the fifth indication information carried in the second information.
  • the information of the connected device is directly forwarded to the SMF network element without reading the information.
  • the SMF network element After receiving the sixth indication information and the seventh indication information, the SMF network element sends the eighth indication information and/or the ninth indication information to the AMF network element.
  • the eighth indication information is used to instruct the AMF network element to release the first session, and the ninth indication information is used to indicate that the access network device does not support the first network slice.
  • whether the SMF network element sends the ninth indication information to the AMF network element can be determined according to whether the AMF network element knows that the access network device does not support the first network slice. If pre-configuration is used to ensure that the AMF network element learns that the access network device does not support the first network slice during network deployment, the SMF network element may not send the ninth indication information to the AMF network element; if there is no pre-configuration or the pre-configuration needs to be updated Since the AMF network element can only directly forward the information from the access network device without reading it, it may not be known that the access network device does not support the first network slice, so the SMF network element can send the ninth indication to the AMF network element information. When the AMF network element learns that the access network device does not support the first network slice, the AMF network element sends a NAS message carrying the new network slice identifier to the terminal.
  • the AMF network element After receiving the eighth indication information and/or the ninth indication information, the AMF network element sends third information to the access network device.
  • the third information may include tenth indication information and eleventh indication information.
  • the tenth indication information may be used to instruct the access network device to release the first session, and the eleventh indication information may be used to indicate the second allowed network slice. logo. It can be understood that after receiving the eighth indication information and/or the ninth indication information, the AMF network element can release the control plane resources of the first session, and send an N2 message to the access network device, or send a NAS message to the terminal, etc. .
  • the access network device receives the third information.
  • the access network device may send signaling to the terminal.
  • the signaling may be used to notify the terminal to release the context of the first session, and the information is carried to indicate The indication information of the new allowed network slice ID.
  • the access network device sends signaling to the AMF network element to notify that the network slice does not support the session identifier established on the network slice; secondly, the AMF network element receives the information from the access network device.
  • the SMF network element receives the instruction information from the AMF network element to learn that the network slice does not support the session identifier established on the network slice; finally, the SMF network element The meta execution releases the session and informs the AMF network element.
  • the access network Through the signaling interaction between the access network and the core network network elements, it is beneficial to quickly release the session established on the network slice that the access network device does not support, reduce signaling interaction during the session release process, and save signaling overhead. In addition, by releasing the control plane resources or context of the session in time, it is beneficial to reduce the waste of network resources.
  • the terminal, the access network device, and the core network element include hardware structures and/or software modules corresponding to each function.
  • the present application can be implemented in the form of hardware or a combination of hardware and computer software. Whether a certain function is executed by hardware or computer software-driven hardware depends on the specific application and design constraint conditions of the technical solution. Those skilled in the art can use different methods for each specific application to implement the described functions, but such implementation should not be considered beyond the scope of the present application.
  • the embodiments of this application can divide functional units of terminals, access network equipment, and core network elements according to the foregoing method examples.
  • each functional unit can be divided corresponding to each function, or two or more functions can be integrated.
  • a processing unit In a processing unit.
  • the above-mentioned integrated unit can be implemented in the form of hardware or in the form of software program modules. It should be noted that the division of units in the embodiments of the present application is illustrative, and is only a logical function division, and there may be other division methods in actual implementation.
  • FIG. 9 illustrates a block diagram of the functional unit composition of a session release device.
  • the session release device 900 is applied to a terminal, and specifically includes a processing unit 902 and a communication unit 903.
  • the processing unit 902 is used to control and manage the actions of the terminal.
  • the processing unit 902 is used to support the terminal to execute the steps in FIG. 4 and other processes used in the technology described herein.
  • the communication unit 903 is used to support communication between the terminal device and other devices.
  • the terminal may also include a storage unit 901 for storing program codes and data of the terminal.
  • the processing unit 902 may be a processor or a controller, for example, a central processing unit (CPU), a general-purpose processor, a digital signal processor (digital signal processor, DSP), and an application-specific integrated circuit (application-specific integrated circuit). integrated circuit, ASIC), field programmable gate array (FPGA), or other programmable logic devices, transistor logic devices, hardware components, or any combination thereof. It can implement or execute various exemplary logical blocks, modules, and circuits described in conjunction with the disclosure of this application.
  • the processor 902 may also be a combination for realizing computing functions, for example, including a combination of one or more microprocessors, a combination of a DSP and a microprocessor, and so on.
  • the communication unit 903 may be a communication interface, a transceiver, a transceiving circuit, etc., and the storage unit 901 may be a memory.
  • the processing unit 902 is a processor
  • the communication unit 903 is a communication interface
  • the storage unit 901 is a memory
  • the session release apparatus 900 involved in the embodiment of the present application may be the terminal shown in FIG. 13.
  • the processing unit 902 is configured to perform any step performed by the terminal in the foregoing method embodiment, and when performing data transmission such as sending, the communication unit 903 can be optionally invoked to complete the corresponding operation.
  • the communication unit 903 can be optionally invoked to complete the corresponding operation.
  • the processing unit 902 is configured to: receive the first information from the access network device through the communication unit 903; determine according to the first information that the access network device does not support the first network slice; and release the first session established on the first network slice.
  • the first information includes first indication information, and the first indication information is used to indicate a network slice supported by the access network device; according to the first information, it is determined that the access network device does not support the first network slice, and the processing unit 902 is configured to: determine according to the first indication information and the first allowed network slice identifier that the access network device does not support the first network slice; or, according to the first indication information and the network slice identifier of the currently established protocol data unit session It is determined that the access network device does not support the first network slice.
  • the first indication information is carried in system information.
  • the processing unit 902 is further configured to: in the case where it is determined that the first session is established on the first network slice, the current idle state is changed to the connected state through the registration process or the service request process to release the first session. .
  • the first information includes second indication information and/or third indication information
  • the second indication information is used to indicate that the access network device does not support the first network slice
  • the third indication information is used to indicate the release of the first network slice.
  • the second indication information and/or the third indication information are carried in the radio resource control message.
  • the first session established on the first network slice is released, and the processing unit 902 is configured to release the first session according to the radio resource control message.
  • FIG. 10 illustrates a block diagram of the functional unit composition of another session release device.
  • the session release apparatus 1000 is applied to an access network device, and specifically includes: a processing unit 1002 and a communication unit 1003.
  • the processing unit 1002 is used to control and manage the actions of the access network device.
  • the processing unit 1002 is used to support the access network device to perform the steps in FIG. 4 or FIG. 8 and/or other processes used in the technology described herein.
  • the communication unit 1003 is used to support communication between the access network device and other devices.
  • the access network device may also include a storage unit 1001 for storing program codes and data of the access network device.
  • the processing unit 1002 may be a processor or a controller, for example, a CPU, a general-purpose processor, a DSP, an ASIC, an FPGA, or other programmable logic devices, transistor logic devices, hardware components, or any combination thereof. It can implement or execute various exemplary logical blocks, modules, and circuits described in conjunction with the disclosure of this application.
  • the processor 1002 may also be a combination for realizing computing functions, for example, including one or more microprocessor combinations, DSP and microprocessor combinations, and so on.
  • the communication unit 1003 may be a communication interface, a transceiver, a transceiving circuit, etc., and the storage unit 1001 may be a memory.
  • the session release apparatus 1000 involved in the embodiment of the present application may be the access network device shown in FIG. 14.
  • the processing unit 1002 is configured to perform any step performed by the access network device in the foregoing method embodiment, and when performing data transmission such as sending, the communication unit 1003 can be optionally invoked to complete the corresponding operation.
  • the communication unit 1003 can be optionally invoked to complete the corresponding operation.
  • the processing unit 1002 is configured to send second information to the access and mobility management function AMF network element through the communication unit 1003, the second information includes fourth indication information and fifth indication information, and the fourth indication information is used to indicate the access network
  • the device does not support the first network slice, and the fifth indication information is used to indicate to release the protocol data unit session identifier of the first session established on the first network slice.
  • the processing unit 1002 is further configured to: send the first information to the terminal through the communication unit 1003, and the first information is used by the terminal to perform the following operations: according to the first information, it is determined that the access network device does not support the first information. Network slice; release the first session established on the first network slice.
  • the first information includes first indication information, and the first indication information is used to indicate a network slice identifier supported by the access network device.
  • the first indication information is carried in a system message.
  • the first information includes second indication information and/or third indication information
  • the second indication information is used to indicate that the access network device does not support the first network slice
  • the third indication information is used to indicate the release of the first network slice.
  • the second indication information and/or the third indication information are carried in the radio resource control message.
  • the processing unit 1002 is further configured to: receive third information from the AMF network element through the communication unit 1003, the third information includes tenth indication information and eleventh indication information, and the tenth indication information is used to indicate The access network device releases the first session, and the eleventh indication information is used to indicate the second allowed network slice identifier.
  • FIG. 11 illustrates a block diagram of the functional unit composition of another session release device.
  • the session release device 1100 is applied to the access and mobility management function AMF network element, and specifically includes: a processing unit 1102 and a communication unit 1103.
  • the processing unit 1102 is used to control and manage the actions of the AMF network element.
  • the processing unit 1102 is used to support the AMF network element to perform the steps in FIG. 8 and/or other processes used in the technology described herein.
  • the communication unit 1103 is used to support communication between the AMF network element and other devices.
  • the AMF network element may also include a storage unit 1101 for storing program codes and data of the AMF network element.
  • the processing unit 1102 may be a processor or a controller, for example, a CPU, a general-purpose processor, a DSP, an ASIC, an FPGA, or other programmable logic devices, transistor logic devices, hardware components, or any combination thereof. It can implement or execute various exemplary logical blocks, modules, and circuits described in conjunction with the disclosure of this application.
  • the processor 1102 may also be a combination that implements computing functions, for example, includes one or more microprocessor combinations, DSP and microprocessor combinations, and the like.
  • the communication unit 1103 may be a communication interface, a transceiver, a transceiving circuit, etc., and the storage unit 1101 may be a memory. When the processing unit 1102 is a processor, the communication unit 1103 is a communication interface, and the storage unit 1101 is a memory, the session release apparatus 1100 involved in the embodiment of the present application may be the AMF network element shown in FIG. 15.
  • the processing unit 1102 is configured to perform any step performed by the AMF network element in the foregoing method embodiment, and when performing data transmission such as sending, the communication unit 1103 can be optionally invoked to complete the corresponding operation.
  • the processing unit 1102 is configured to perform any step performed by the AMF network element in the foregoing method embodiment, and when performing data transmission such as sending, the communication unit 1103 can be optionally invoked to complete the corresponding operation.
  • the detailed description will be given below.
  • the processing unit 1102 is configured to: receive the second information from the access network device through the communication unit 1103, the second information includes fourth indication information and fifth indication information, and the fourth indication information is used to indicate that the access network device does not support the first For the network slice, the fifth indication information is used to instruct to release the protocol data unit session identifier of the first session established on the first network slice.
  • receiving signaling from the access network device to learn that the network slice does not support and the session identifier established on the network slice is beneficial to quickly release network slices that the access network device does not support.
  • the session established on the previous session reduces the signaling interaction during the session release process and saves signaling overhead.
  • the processing unit 1102 is further configured to send sixth indication information and seventh indication information to the session management function SMF network element through the communication unit 1103, and the sixth indication information is used to indicate that the access network device does not support the first For a network slice, the seventh indication information is used to indicate the protocol data unit session identifier of the first session to be released.
  • the processing unit 1102 is further configured to: receive the eighth indication information from the SMF network element through the communication unit 1103, where the eighth indication information is used to instruct the AMF network element to release the first session.
  • the processing unit 1102 is further configured to: receive the ninth indication information from the SMF network element through the communication unit 1103, where the ninth indication information is used to indicate that the access network device does not support the first network slice.
  • the processing unit 1102 is further configured to: send third information to the access end device through the communication unit 1103, the third information includes tenth indication information and eleventh indication information, and the tenth indication information is used to indicate The access network device releases the first session, and the eleventh indication information is used to indicate the second allowed network slice identifier.
  • FIG. 12 illustrates a block diagram of the functional unit composition of another session release device.
  • the session release device 1200 is applied to a session management function SMF network element, and specifically includes: a processing unit 1202 and a communication unit 1203.
  • the processing unit 1202 is used to control and manage the actions of the SMF network element.
  • the processing unit 1202 is used to support the SMF network element to perform the steps in FIG. 8 and/or other processes used in the technology described herein.
  • the communication unit 1203 is used to support communication between the SMF network element and other devices.
  • the SMF network element may also include a storage unit 1201 for storing program codes and data of the SMF network element.
  • the processing unit 1202 may be a processor or a controller, for example, a CPU, a general-purpose processor, a DSP, an ASIC, an FPGA, or other programmable logic devices, transistor logic devices, hardware components, or any combination thereof. It can implement or execute various exemplary logical blocks, modules, and circuits described in conjunction with the disclosure of this application.
  • the processor 1202 may also be a combination that implements computing functions, for example, including one or more microprocessor combinations, DSP and microprocessor combinations, and the like.
  • the communication unit 1203 may be a communication interface, a transceiver, a transceiving circuit, etc., and the storage unit 1201 may be a memory. When the processing unit 1202 is a processor, the communication unit 1203 is a communication interface, and the storage unit 1201 is a memory, the session release apparatus 1200 involved in the embodiment of the present application may be the AMF network element shown in FIG. 15.
  • the processing unit 1202 is configured to perform any step performed by the SMF network element in the foregoing method embodiment, and when performing data transmission such as sending, the communication unit 1203 can be optionally invoked to complete the corresponding operation.
  • the processing unit 1202 is configured to perform any step performed by the SMF network element in the foregoing method embodiment, and when performing data transmission such as sending, the communication unit 1203 can be optionally invoked to complete the corresponding operation.
  • the detailed description will be given below.
  • the processing unit 1202 is configured to receive the sixth indication information and the seventh indication information from the access and mobility management function AMF network element through the communication unit 1203, the sixth indication information is used to indicate that the access network device does not support the first network slicing , The seventh indication information is used to indicate the release of the protocol data unit session identifier of the first session established on the first network slice.
  • the processing unit 1202 is further configured to send eighth indication information to the AMF network element through the communication unit 1203, where the eighth indication information is used to instruct the AMF network element to release the first session.
  • the processing unit 1202 is further configured to send ninth indication information to the AMF network element through the communication unit 1203, where the ninth indication information is used to indicate that the access network device does not support the first network slice.
  • FIG. 13 is a schematic structural diagram of a terminal 1300 according to an embodiment of the present application.
  • the terminal 1300 includes a processor 1310, a memory 1320, a communication interface 1330, and at least one communication bus for connecting the processor 1310, the memory 1320, and the communication interface 1330.
  • the memory 1320 includes but is not limited to random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (erasable programmable read only memory, EPROM) or portable Read-only memory (compact disc read-only memory, CD-ROM), the memory 1320 is used for related instructions and data.
  • RAM random access memory
  • ROM read-only memory
  • EPROM erasable programmable read only memory
  • CD-ROM compact disc read-only memory
  • the communication interface 1330 is used to receive and send data.
  • the processor 1310 may be one or more CPUs.
  • the CPU may be a single-core CPU or a multi-core CPU.
  • processor 1310 in the terminal 1300 is used to read one or more program codes 1321 stored in the memory 1320, to execute the method in the method embodiment shown in FIG. 4, and the terminal 1300 can also be used to execute The method on the terminal side of the foregoing method embodiment of this application will not be repeated here.
  • FIG. 14 is a schematic structural diagram of an access network device 1400 according to an embodiment of the present application.
  • the access network device 1400 includes a processor 1410, a memory 1420, a communication interface 1430, and at least one communication bus for connecting the processor 1410, the memory 1420, and the communication interface 1430.
  • the memory 1420 includes, but is not limited to, a random storage memory, a read-only memory, an erasable programmable read-only memory, or a portable read-only memory, and the memory 620 is used for related instructions and data.
  • the communication interface 1430 is used to receive and send data.
  • the processor 1410 may be one or more CPUs.
  • the CPU may be a single-core CPU or a multi-core CPU.
  • the processor 1410 in the access network device 1400 is used to read one or more program codes 1421 stored in the memory 1420, execute the method in the method embodiment shown in FIG. 4 or FIG. 8, and connect
  • the network access device 1400 may also be used to execute the method on the access network device side of the foregoing method embodiment of the present application, and details are not described herein again.
  • FIG. 15 is a schematic structural diagram of an access and mobility management function network element 1500 according to an embodiment of the present application.
  • the access and mobility management function network element 1500 includes a processor 1510, a memory 1520, a communication interface 1530, and at least one communication bus for connecting the processor 1510, the memory 1520, and the communication interface 1530.
  • the memory 1520 includes, but is not limited to, a random storage memory, a read-only memory, an erasable programmable read-only memory, or a portable read-only memory.
  • the memory 1520 is used for related instructions and data.
  • the communication interface 1530 is used to receive and send data.
  • the processor 1510 may be one or more CPUs.
  • the CPU may be a single-core CPU or a multi-core CPU.
  • the processor 1510 in the access and mobility management function network element 1500 is used to read one or more program codes 1521 stored in the memory 1520, and execute the method embodiment shown in FIG. 4 or FIG.
  • the method and the access and mobility management function network element 1500 can also be used to execute the method on the AMF network element side of the foregoing method embodiment of the present application, which will not be repeated here.
  • FIG. 16 is a schematic structural diagram of a network element 1600 with a session management function according to an embodiment of the present application.
  • the session management function network element 1600 includes a processor 1610, a memory 1620, a communication interface 1630, and at least one communication bus for connecting the processor 1610, the memory 1620, and the communication interface 1630.
  • the memory 1620 includes, but is not limited to, a random storage memory, a read-only memory, an erasable programmable read-only memory, or a portable read-only memory.
  • the memory 1620 is used for related instructions and data.
  • the communication interface 1630 is used to receive and send data.
  • the processor 1610 may be one or more CPUs.
  • the CPU may be a single-core CPU or a multi-core CPU.
  • the processor 1610 in the session management function network element 1600 is used to read one or more program codes 1621 stored in the memory 1620, and execute the method in the method embodiment shown in FIG. 4 or FIG. 8, and
  • the session management function network element 1600 can also be used to execute the method on the SMF network element side of the foregoing method embodiment of the present application, which will not be repeated here.
  • the embodiment of the present application also provides a chip, wherein the chip includes a processor, which is used to call and run a computer program from the memory, so that the device installed with the chip executes the terminal and the access network device in the above method embodiment.
  • Access and mobility management function network element or session management function network element describes part or all of the steps.
  • the embodiment of the present application also provides a computer-readable storage medium, wherein the computer-readable storage medium stores a computer program for electronic data exchange, and the computer program is operable to make the computer execute the terminal in the above-mentioned method embodiment.
  • Access network equipment, access and mobility management function network element or session management function network element describes part or all of the steps.
  • the embodiments of the present application also provide a computer program product, wherein the computer program product includes a computer program, and the computer program is operable to make the computer execute the terminal, the access network device, the access and the mobile in the above method embodiment. Part or all of the steps described in the network element of the sexual management function or the network element of the session management function.
  • the computer program product may be a software installation package.
  • the steps of the method or algorithm described in the embodiments of the present application may be implemented in a hardware manner, or may be implemented in a manner in which a processor executes software instructions.
  • Software instructions can be composed of corresponding software modules, which can be stored in random access memory RAM, flash memory, ROM, EPROM, electrically erasable programmable read-only memory (ePROM, EEPROM), registers, hard disks, mobile hard disks, CD-ROM or any other form of storage medium known in the art.
  • An exemplary storage medium is coupled to the processor, so that the processor can read information from the storage medium and write information to the storage medium.
  • the storage medium may also be an integral part of the processor.
  • the processor and the storage medium may be located in an application specific integrated circuit (ASIC).
  • the ASIC may be located in an access network device, a network device, or a core network gateway.
  • the processor and the storage medium may also exist as discrete components in the access network device, network device, or core network gateway.
  • the functions described in the embodiments of the present application may be implemented in whole or in part by software, hardware, firmware, or any combination thereof.
  • software it can be implemented in the form of a computer program product in whole or in part.
  • the computer program product includes one or more computer instructions.
  • the computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable devices.
  • Computer instructions can be stored in a computer-readable storage medium, or transmitted from one computer-readable storage medium to another computer-readable storage medium.
  • 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 usable medium may be a magnetic medium (for example, a floppy disk, a hard disk, and a magnetic tape), an optical medium (for example, a digital video disc), or a semiconductor medium (for example, a solid state hard disk).

Landscapes

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

Abstract

Les modes de réalisation de la présente invention relèvent du domaine technique des communications. Sont divulgués un procédé et un appareil de libération de session. Le procédé comprend les étapes au cours desquelles : un terminal reçoit des premières informations provenant d'un dispositif de réseau d'accès; en fonction des premières informations, le terminal détermine que le dispositif de réseau d'accès ne prend pas en charge une première tranche de réseau; et le terminal libère une première session établie sur la première tranche de réseau. Par conséquent, d'après les modes de réalisation de la présente invention, le terminal reçoit une signalisation provenant du dispositif de réseau d'accès de façon à déterminer une tranche de réseau qui n'est pas prise en charge par le dispositif de réseau d'accès, ce qui facilite la libération rapide d'une session établie sur la tranche de réseau. Une interaction de signalisation au cours du processus de libération de la session s'en trouve réduite. De plus, le surdébit de signalisation et le gaspillage de ressources de réseau sont évités.
PCT/CN2020/083594 2020-04-07 2020-04-07 Procédé et appareil de libération de session WO2021203249A1 (fr)

Priority Applications (2)

Application Number Priority Date Filing Date Title
CN202080098378.3A CN115244980A (zh) 2020-04-07 2020-04-07 会话释放方法与装置
PCT/CN2020/083594 WO2021203249A1 (fr) 2020-04-07 2020-04-07 Procédé et appareil de libération de session

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2020/083594 WO2021203249A1 (fr) 2020-04-07 2020-04-07 Procédé et appareil de libération de session

Publications (1)

Publication Number Publication Date
WO2021203249A1 true WO2021203249A1 (fr) 2021-10-14

Family

ID=78022445

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2020/083594 WO2021203249A1 (fr) 2020-04-07 2020-04-07 Procédé et appareil de libération de session

Country Status (2)

Country Link
CN (1) CN115244980A (fr)
WO (1) WO2021203249A1 (fr)

Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2017098442A1 (fr) * 2015-12-08 2017-06-15 Huawei Technologies Co., Ltd. Système et procédé pour des configurations d'état d'équipement utilisateur pour de multiples services
WO2019001576A1 (fr) * 2017-06-30 2019-01-03 华为技术有限公司 Procédé et appareil de communication

Family Cites Families (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US11122470B2 (en) * 2017-05-04 2021-09-14 Ofinno, Llc Network slice information for handover procedure
US10820185B2 (en) * 2017-05-08 2020-10-27 Qualcomm Incorporated Mobility between areas with heterogeneous network slices
CN109548098B (zh) * 2017-08-15 2023-10-24 华为技术有限公司 会话处理方法及相关设备

Patent Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2017098442A1 (fr) * 2015-12-08 2017-06-15 Huawei Technologies Co., Ltd. Système et procédé pour des configurations d'état d'équipement utilisateur pour de multiples services
WO2019001576A1 (fr) * 2017-06-30 2019-01-03 华为技术有限公司 Procédé et appareil de communication

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
QUALCOMM INCORPORATED: "TS 23.502: handling of PDU sessions at slice unavailability", 3GPP DRAFT; S2-173106-23.502 - SLICING PDU SESSION HANDLING, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. SA WG2, no. Hangzhou; 20170515 - 20170519, 14 May 2017 (2017-05-14), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France , XP051281614 *

Also Published As

Publication number Publication date
CN115244980A (zh) 2022-10-25

Similar Documents

Publication Publication Date Title
WO2020200118A1 (fr) Procédé et appareil de transmission de données
US20210022063A1 (en) Data transmission method and apparatus
KR102394891B1 (ko) 무선 통신 방법 및 장치
US20200396652A1 (en) Method, apparatus, computer program product and computer program for conditional handover
US20220060935A1 (en) Communications Method and Apparatus
US20200287975A1 (en) Session Processing Method, Apparatus, And System
CN111601353B (zh) 应用程序的路由选择方法及相关装置
US20220386390A1 (en) Communication method between core network device and terminal in communication system
WO2019196643A1 (fr) Procédé de communication et appareil de communication
WO2020155021A1 (fr) Procédé d'établissement de session et dispositif terminal
WO2019033796A1 (fr) Procédé de traitement de session, et dispositif associé
CN110383939B (zh) 无线终端、基站及其方法和非暂时性计算机可读介质
WO2021232910A1 (fr) Procédé d'accès au réseau et appareil de communication
CN110049578B (zh) 无线连接修改方法、设备及系统
US11405965B2 (en) Signaling processing method and apparatus
CN114449577B (zh) 服务质量QoS参数配置方法及相关装置
WO2019192445A1 (fr) Procédé et dispositif de création et de jonction d'un groupe de multidiffusion
EP4037373A1 (fr) Procédé et dispositif de communication
US20230254922A1 (en) Multipath transmission method and communication apparatus
US20190239281A1 (en) Session management method and session management network element
EP4175404A1 (fr) Procédé de commutation d'état, procédé et appareil d'indication pour mtch à l'état connecté, support d'enregistrement et station de base
WO2022068771A1 (fr) Procédé de communication et appareil de communication
WO2018214762A1 (fr) Procédé et appareil d'acquisition d'un paramètre de radiomessagerie
WO2021088007A1 (fr) Procédé de communication sans fil, dispositif terminal et dispositif réseau
WO2023087965A1 (fr) Procédé et appareil de communication

Legal Events

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

Ref document number: 20930017

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 20930017

Country of ref document: EP

Kind code of ref document: A1