WO2020199620A1

WO2020199620A1 - Session processing method and apparatus

Info

Publication number: WO2020199620A1
Application number: PCT/CN2019/121360
Authority: WO
Inventors: 宗在峰; 朱奋勤; 姚琦
Original assignee: 华为技术有限公司
Priority date: 2019-03-29
Filing date: 2019-11-27
Publication date: 2020-10-08
Also published as: CN111757312A

Abstract

Provided are a session processing method and apparatus. The method comprises: a first session management network element receiving a session establishment request message from a mobility management network element, wherein the session establishment request message comprises an identifier of a session of a terminal device and an identifier of a second session management network element, and the session is a session to be activated or to be switched; the first session management network element acquiring, from the second session management network element, the context of the session; and the first session management network element determining, according to the context of the session, to reject the session. On the basis of the scheme, by means of the interaction between a plurality of session management network elements, the processing of a session to be activated or to be switched is realized.

Description

Method and device for processing conversation

Cross references to related applications

This application claims the priority of a Chinese patent application filed with the Chinese Patent Office on March 29, 2019, the application number is 201910251991.3, and the application name is "a conversation processing method and device", the entire content of which is incorporated into this application by reference in.

Technical field

This application relates to the field of mobile communication technology, and in particular to a method and device for processing a session.

Background technique

In the 5th generation (5G) network, due to the movement of the terminal device, the anchor point UPF in the session of the terminal device cannot be covered by the terminal device. Therefore, the intermediate session management function (SMF) is introduced. The intermediate SMF can select an intermediate user plane function (user plane function, UPF). In this way, the terminal device can connect to the anchor UPF through the intermediate UPF. Therefore, there will be multiple SMFs in the network, including one anchor SMF (that is, the SMF that manages the anchor UPF) and at least one intermediate SMF.

In the above scenario, when a terminal device moves to a new location and initiates an activation session or switches a session at the new location, if the network finds that the session cannot be used in the new location of the terminal device, how does the network side handle it? There is no solution for how to interact between SMFs.

Summary of the invention

The present application provides a session processing method and device, which implements the processing of a session to be activated or to be switched through interaction between multiple session management network elements.

In a first aspect, the present application provides a session processing method. The method includes: a first session management network element receives a session creation request message from a mobility management network element, and the session creation request message includes the session identifier and the first session of the terminal device. 2. The identifier of the session management network element, the session is a session to be activated or switched; the first session management network element obtains the context of the session from the second session management network element; the first session management network element determines to reject the session according to the context of the session . Based on this solution, through the interaction between multiple session management network elements (that is, the first session management network element and the second session management network element), the processing of the sessions to be activated or to be switched is realized.

In a possible implementation method, the context of the session includes the SSC mode of the session, and the SSC mode is to release the current session first and then create a new session; the first session management network element releases the current session first and then creates a new session according to the SSC mode of the session. Decline the session.

In yet another possible implementation method, the session creation request message also includes an indication that the terminal device can only use the supervised priority service, and the context of the session includes a session that is a non-supervised priority service or a non-emergency service; the first session management The network element determines to reject the session based on that the terminal device can only use the supervised priority service and the session is a non-supervised priority service session or a non-emergency service session.

In a possible implementation method, the first session management network element sends a response message to the mobility management network element, where the response message is used to indicate that the session activation fails.

In a possible implementation method, the response message includes the rejection reason value, and the rejection reason value is any of the following: the session is rejected, the terminal device can only use the supervised priority service, and the session is a non-supervised priority service session or non-emergency service The SSC mode of the session and session is to release the current session first and then create a new session.

In yet another possible implementation method, the first session management network element sends a response message to the mobility management network element, where the response message is used to indicate that the session activation fails but the first session management The session context of the network element is successfully established.

In a possible implementation method, the first session management network element selects the first user plane network element, and creates an N4 session between the first session management network element and the first user plane network element; the first session management network element Send a session context update request message to the anchor session management network element, the session context update request message includes the tunnel information of the first user plane network element, and the session context update request message is used to request the creation of the anchor point user managed by the session management network element A tunnel between the plane network element and the first user plane network element.

In a possible implementation method, the first session management network element is a first intermediate session management network element, and the second session management network element is a second intermediate session management network element; or, the first session management network element is an intermediate session The management network element, and the second session management network element is an anchor session management network element.

In a second aspect, this application provides a session processing method. The method includes: a first session management network element receives a session creation request message from a mobility management network element, and the session creation request message includes the session identifier and the first session of the terminal device. 2. The identifier of the session management network element, the session is the session to be activated or switched; the first session management network element selects the first user plane network element, and creates a connection between the first session management network element and the first user plane network element N4 session; the first session management network element sends a session context update request message to the anchor session management network element, the session context update request message includes the tunnel information of the first user plane network element, and the session context update request message is used to request the creation of an anchor point The tunnel between the anchor user plane network element and the first user plane network element managed by the session management network element; the first session management network element receives indication information from the anchor session management network element, and the indication information is used to indicate rejection of the session; The first session management network element sends a response message to the mobility management network element, where the response message is used to indicate that the session activation fails but the session context of the first session management network element is successfully established. Based on this solution, through the interaction between multiple session management network elements (that is, the first session management network element and the second session management network element), the processing of the sessions to be activated or to be switched is realized.

In a possible implementation method, the session context update request message also includes an indication that the terminal device can only use the supervised priority service.

In a possible implementation method, the first session management network element receives the rejection reason value from the anchor session management network element; the response message includes the rejection reason value, and the rejection reason value is any of the following: session rejected, terminal The device can only use the supervisory priority service and the session is a non-supervised priority service session or a non-emergency service session, and the SSC mode of the session is to release the current session first and then create a new session.

In a possible implementation method, the first session management network element obtains the context of the session from the second session management network element.

In a third aspect, the present application provides a session processing method, the method includes: an anchor session management network element receives a session context update request message from a first session management network element, and the session context update request message includes the first session management network element The tunnel information of the first user plane network element selected by the element, and the session context update request message is used to request the creation of an anchor point managed by the session management network element. A tunnel between the user plane network element and the first user plane network element; The session management network element obtains the context of the session and determines to reject the session according to the context of the session; the anchor session management network element sends indication information to the first session management network element, and the indication information is used to indicate the rejection of the session. Based on this solution, through the interaction between multiple session management network elements (that is, the first session management network element and the second session management network element), the processing of the sessions to be activated or to be switched is realized.

In a possible implementation method, the context of the session includes the SSC mode of the session, and the SSC mode is to release the current session and then create a new session; the anchor session management network element releases the current session and then creates a new session according to the SSC mode of the session. Decline the session.

In a possible implementation method, the session context update request message also includes an indication that the terminal device can only use the supervised priority service, and the context of the session includes a session with a non-supervised priority service or a conversation with a non-emergency service; anchor session management The network element determines to reject the session based on that the terminal device can only use the supervision priority service and the session is a non-supervised priority service session or a non-emergency service session.

In a possible implementation method, the anchor session management network element sends a rejection reason value to the first session management network element, and the rejection reason value is any of the following: the session is rejected, the terminal device can only use the supervisory priority service, and the session For non-supervised priority service sessions or non-emergency service sessions, the SSC mode of the session is to release the current session first and then create a new session.

In a possible implementation method, the anchor session management network element sends a notification message to the anchor user plane network element, the notification message includes tunnel information of the first user plane network element, and the notification message is used to notify the establishment of the anchor user plane network Downlink tunnel between the element and the first user plane network element.

In a fourth aspect, the present application provides a session processing method, the method includes: a mobility management network element receives a request message, the request message includes an identifier of the session of the terminal device, the session is a session to be activated or to be switched; mobility management The network element determines that the terminal device moves out of the service range of the second session management network element, and selects the first session management network element for the terminal device; the mobility management network element sends a session creation request message to the first session management network element, and the session creation request message Including the identifier of the session and the identifier of the second session management network element; the mobility management network element receives a response message from the first session management network element for the session creation request message, the response message is used to indicate that the session activation fails, Alternatively, the response message is used to indicate that the session activation fails, but the session context of the first session management network element is successfully established. The response message includes the rejection reason value, and the rejection reason value is any of the following: the session is rejected, the terminal device can only use the supervised priority service and the session is a non-supervised priority service session or a non-emergency service session, and the SSC mode of the session is first Release the current session and create a new session.

In a possible implementation method, in the service request process of the terminal device, the mobility management network element sends a failure notification message to the second session management network element, and the failure notification message includes a rejection reason value.

In a possible implementation method, in the Xn handover or X2 handover process, the mobility management network element sends a session update request message to the second session management network element. The session update request message includes the session identifier, and the session update request message uses On request to deactivate the session.

In a possible implementation method, the mobility management network element deletes the information of the first session management network element.

In a possible implementation method, the mobility management network element sends a session context release request message to the second session management network element, the session context release request message includes the session identifier, and the session context release request message is used to indicate the context of the session to be released .

In a fifth aspect, the present application provides a session processing device. The device may be a session management network element or a chip for the session management network element. The device has the function of realizing each embodiment of the first aspect described above. This function can be realized by hardware, or by hardware executing corresponding software. The hardware or software includes one or more modules corresponding to the above-mentioned functions.

In a sixth aspect, the present application provides a session processing device. The device may be a session management network element or a chip used for the session management network element. The device has the function of realizing each embodiment of the second aspect described above. This function can be realized by hardware, or by hardware executing corresponding software. The hardware or software includes one or more modules corresponding to the above-mentioned functions.

In a seventh aspect, the present application provides a session processing device. The device may be a session management network element, or a chip used for a session management network element. The device has the function of realizing each embodiment of the third aspect. This function can be realized by hardware, or by hardware executing corresponding software. The hardware or software includes one or more modules corresponding to the above-mentioned functions.

In an eighth aspect, the present application provides a session processing device. The device may be a mobility management network element or a chip used for the mobility management network element. The device has the function of realizing each embodiment of the fourth aspect described above. This function can be realized by hardware, or by hardware executing corresponding software. The hardware or software includes one or more modules corresponding to the above-mentioned functions.

In a ninth aspect, this application provides a session processing device, including: a processor and a memory; the memory is used to store computer execution instructions, and when the device is running, the processor executes the computer execution instructions stored in the memory to The device is caused to perform the methods described in the above aspects.

In a tenth aspect, the present application provides a session processing device, including: including units or means for executing each step of the foregoing aspects.

In an eleventh aspect, the present application provides a session processing device, including a processor and an interface circuit, where the processor is configured to communicate with other devices through the interface circuit and execute the methods described in the foregoing aspects. The processor includes one or more.

In a twelfth aspect, the present application provides a session processing device, including a processor, configured to be connected to a memory, and configured to call a program stored in the memory to execute the methods described in the foregoing aspects. The memory can be located inside the device or outside the device. And the processor includes one or more.

In a thirteenth aspect, the present application also provides a computer-readable storage medium that stores instructions in the computer-readable storage medium, which when run on a computer, causes a processor to execute the methods described in the foregoing aspects.

In a fourteenth aspect, the present application also provides a computer program product including instructions, which when run on a computer, cause the computer to execute the methods described in the foregoing aspects.

In a fifteenth aspect, the present application also provides a chip system, including a processor, configured to execute the methods described in the foregoing aspects.

In a sixteenth aspect, the present application also provides a session processing system, including: a session management network element for executing any of the methods described in the first aspect and a mobile device for executing any of the methods described in the fourth aspect. Sexual management network elements.

In a seventeenth aspect, the present application also provides a session processing system, including: a session management network element for executing any of the methods described in the second aspect and a mobile device for executing any of the methods described in the fourth aspect. Sexual management network elements.

In a possible implementation method, the session processing system further includes a session management network element for executing any of the methods described in the third aspect.

Description of the drawings

Figure 1 shows the R15 architecture in 5G;

Figure 2 shows the R16 architecture in 5G;

FIG. 3 is a schematic flowchart of a session processing method provided by this application;

FIG. 4 is a schematic flowchart of another session processing method provided by this application;

FIG. 5 is a schematic flowchart of another method for processing a session provided by this application;

FIG. 6 is a schematic flowchart of another method for processing a session provided by this application;

FIG. 7 is a schematic flowchart of another method for processing a session provided by this application;

FIG. 8 is a schematic flowchart of another session processing method provided by this application;

FIG. 9 is a schematic flowchart of another session processing method provided by this application;

FIG. 10 is a schematic flowchart of another method for processing a session provided by this application;

FIG. 11 is a schematic diagram of a session processing apparatus provided by this application;

FIG. 12 is a schematic diagram of another session processing apparatus provided by this application;

FIG. 13 is a schematic diagram of another session processing apparatus provided by this application.

detailed description

In order to make the purpose, technical solutions, and advantages of the present application clearer, the present application will be further described in detail below with reference to the accompanying drawings. The specific operation method in the method embodiment can also be applied to the device embodiment or the system embodiment. Wherein, in the description of the present application, unless otherwise specified, "multiple" means two or more.

As shown in Figure 1, it is the R15 architecture in 5G. The following briefly introduces some of the network elements included in the architecture and the functions of each network element.

Terminal equipment, also known as user equipment (UE), terminal (Terminal), mobile station (MS), mobile terminal (MT), etc., is a way to provide users with voice/data connectivity Sexual devices, for example, handheld devices with wireless connectivity, vehicle-mounted devices, etc. At present, some examples of terminal devices are: mobile phones (mobile phones), tablet computers, notebook computers, handheld computers, mobile internet devices (MID), wearable devices, virtual reality (VR) devices, augmented Augmented reality (AR) equipment, wireless terminals in industrial control (industrial control), wireless terminals in self-driving (self-driving), wireless terminals in remote medical surgery, and smart grid (smart grid) The wireless terminal in the transportation safety (transportation safety), the wireless terminal in the smart city (smart city), or the wireless terminal in the smart home (smart home), etc.

The access network equipment is a radio access network (RAN) node that connects terminal equipment to the wireless network. At present, some examples of RAN nodes are: next generation NodeB (gNB), transmission reception point (TRP), evolved Node B (eNB), radio network controller (radio network) controller, RNC), node B (Node B, NB), base station controller (BSC), base transceiver station (BTS), home base station (for example, home evolved NodeB, or home Node B, HNB), baseband unit (BBU), or wireless fidelity (wireless fidelity, WiFi) access point (AP), etc.

Access and mobility management function (AMF) network element: It belongs to the core network network element and is mainly responsible for the signaling processing part, such as access control, mobility management, registration and de-registration functions. When the AMF network element provides services for the session in the UE, it will provide storage resources of the control plane for the session to store the session identifier, the SMF network element identifier associated with the session identifier, and so on.

SMF network element: Responsible for user plane network element selection, user plane network element redirection, Internet Protocol (IP) address allocation for interconnection between networks, session establishment, modification and release, and Quality of Service (QoS) )control.

UPF network element: responsible for forwarding and receiving user data of terminal equipment. User data can be received from a data network (data network, DN) and transmitted to the terminal device through the access network device; the UPF network element can also receive user data from the terminal device through the access network device and forward it to the data network. The transmission resources and scheduling functions of UPF network elements that provide services for terminal devices are managed and controlled by SMF network elements.

Policy control function (PCF) network element: It mainly supports the provision of a unified policy framework to control network behavior, provides policy rules to the control layer network function, and is responsible for obtaining policy-related user subscription information.

Authentication server function (Authentication Server Function, AUSF) network element: mainly provides authentication function, supporting 3GPP access and non-3GPP (Non-3GPP) access authentication.

Network Exposure Function (NEF) network element: It mainly supports the secure interaction between 3GPP network and third-party applications. NEF can safely expose network capabilities and events to third parties to strengthen or improve application service quality. The same applies to 3GPP networks Relevant data can be safely obtained from a third party to enhance the intelligent decision-making of the network; at the same time, the network element supports the recovery of structured data from the unified database or the storage of structured data in the unified database.

Unified data management (UDM) network element: Mainly responsible for storing structured data. The stored content includes contracted data and policy data, structured data exposed to the outside world, and application-related data.

Application Function (AF) network element: It mainly supports interaction with the 3GPP core network to provide services, such as influencing data routing decisions, policy control functions or providing third-party services to the network side.

Among them, the interface between the UE and the AMF network element is called the N1 interface, the interface between the AMF network element and the RAN device is called the N2 interface, the interface between the RAN device and the UPF network element can be called the N3 interface, and the SMF network element The interface with UPF network element is called N4 interface, the interface between PCF network element and AF network element is called N5 interface, the interface between UPF network element and DN is called N6 interface, SMF network element and PCF network element The interface between is called N7 interface, the interface between AMF network element and UDM network element is called N8 interface, the interface between different UPF network elements is called N9 interface, the interface between UDM network element and SMF network element is called It is the N10 interface, the interface between the AMF network element and the SMF network element is called the N11 interface, the interface between the AUSF network element and the AMF network element is called the N12 interface, and the interface between the AUSF network element and the UDM network element is called the N13 Interface, the interface between different AMF network elements is called the N14 interface, and the interface between the AMF network element and the PCF network element is called the N15 interface.

As shown in Figure 2, it is the 5G R16 architecture. Compared with the R15 architecture shown in Figure 1, the main difference is that: the R16 architecture shown in Figure 2 supports multiple SMFs, that is, supports insertion of SMFs. Therefore, SMF can be divided into anchor SMF (anchor SMF, A-SMF) and intermediate SMF (Intermediate SMF, I-SMF), where I-SMF refers to inserted SMF.

A-SMF is the SMF of the service protocol data unit (protocol data unit, PDU) session. A-SMF controls the anchor UPF (anchor UPF, A-UPF), which can perform UE IP address allocation.

I-SMF is mainly responsible for the management of UPF (referred to as Intermediate UPF (Intermediate UPF, I-UPF)) in its jurisdiction, including UPF selection, load sharing between UPFs, session management functions (including the establishment of user plane tunnels, Configuration of UPF forwarding rules, etc.). I-SMF can manage I-UPF that is not controlled by A-SMF and has an N3 interface (ie, UPF between RAN and A-UPF). And, you can choose to insert, switch, or remove I-SMF as needed.

The mobility management network element, session management network element, and user plane network element in this application can be the AMF network element, SMF network element, and UPF network element shown in Fig. 2 respectively, or they can be the AMF network element in the future communication system. Network elements with functions of network elements, SMF network elements, and UPF network elements.

For the convenience of description, in the follow-up of this application, the mobility management network element, the session management network element, and the user plane network element are respectively the AMF network element, SMF network element, and UPF network element in FIG. 2 for description. Further, the AMF network element is abbreviated as AMF, the SMF network element is abbreviated as SMF, the UPF network element is abbreviated as UPF, and the terminal equipment is referred to as UE, and the access network device is referred to as RAN. The described AMF can be replaced with mobility management network elements, SMF can be replaced with session management network elements, UPF can be replaced with user plane network elements, UE can be replaced with terminal equipment, and RAN can be replaced with access network equipment. .

In order to solve the problems mentioned in the background art, this application provides a method for processing a session, which is described in detail below.

Before introducing the solution of this application, firstly, some communication terms involved in this application will be explained.

1. Session and Service Continuity Mode (SSC mode)

The SSC mode in the 5G system can meet the continuity requirements of different applications or services. Different SSC modes are supported in the 5G system, mainly including the following SSC modes:

1) SSC mode1: During the movement of the UE, regardless of the UE's access technology type and UE location, after the PDU session is established, the UPF serving as the PDU session anchor (PSA) remains unchanged.

2) SSC mode2: Based on the operator's strategy and other information, the network side can release the current PDU session and notify the UE to re-establish a new PDU session. In the newly created PDU session, the UPF as the PSA can be reselected.

3), SSC mode3: For the PDU session of SSC mode 3, the network side allows the DNN for the PDU session to establish a new PDU session, and after the establishment of the new PDU session, the previously established PDU can be released after a certain period of time Conversation. There are many conditions for the network side to allow the DNN of the PDU session to establish a new PDU session, such as due to the movement of the UE, or due to the load balancing of the equipment.

It should be noted that with the evolution of communication technology, the name of the above SSC mode may change. As long as the specific meaning of its SSC mode is the same as the meaning of the above SSC mode in this application, no matter how its name changes, it will fall into this Within the scope of protection applied for.

2. Emergency service (Emergency service)

Emergency services refer to emergency services provided by the service network when the network supports emergency services.

The UE may create a session to access emergency services, and the session may be referred to as an emergency service session. On the contrary, the session is a non-emergency service session, or the session is not used to access emergency services.

Three, regulatory priority service (regulatory prioritized service)

Regulatory priority services include emergency services, public safety services, and multimedia priority services (MPS).

The UE can create a session to access the supervisory priority service, which can be referred to as a supervisory priority service session. Conversely, the session is a non-supervised priority service session, or the session is not used to access the supervisory priority service.

The solution of this application can be applied to the following two application scenarios, which are explained separately below.

Scenario 1: There is one I-SMF and one A-SMF.

For example, referring to Figure 2, due to the movement of the UE, the UE requests to establish a session or switch a session at a new location. If the A-UPF cannot serve the UE in the new location of the UE, that is, the A-UPF cannot cover the new location of the UE. Then an I-SMF (also referred to as the first SMF in this application) can be inserted into the network, and then the I-SMF selects an I-UPF (also referred to as the first UPF in this application), and inserts the I-UPF into the UE In the session path of the UE, the session of the UE is connected to the A-UPF managed by the A-SMF (also referred to as the second SMF in this application) (also referred to as the second UPF in this application) through the I-UPF to realize the activation or switching of the session .

Scenario 2: There are two or more I-SMFs and one A-SMF.

On the basis of scenario 1, that is, there is already an I-UPF (also referred to as the second UPF in this application) and an I-SMF (also referred to as the second SMF in this application) in the UE session, and the second SMF manages The second UPF. Due to the movement of the UE, the UE initiates the establishment or handover session at a new location. If the second UPF cannot provide service to the UE at the new location of the UE, that is, the second UPF cannot cover the new location of the UE, it can be in the network Then insert an I-SMF (this application is also called the first SMF), and then the first SMF selects a new I-UPF (this application is also called the first UPF), and inserts the first UPF into the UE’s session In the path, that is, the session of the UE is connected to the A-UPF through the first UPF to realize the activation or switching of the session.

In summary, for the above scenario 1, call I-SMF as the first SMF, I-UPF as the first UPF, A-SMF as the second SMF, and A-UPF as the second UPF . For the second scenario above, the newly inserted I-SMF is called the first SMF, the newly inserted I-UPF is called the first UPF, the original I-SMF is called the second SMF, and the original I-UPF is called the second SMF. Called the second UPF.

As shown in FIG. 3, a method for processing a session is provided for this application. The method is described for the second scenario above, and in this method, the first SMF determines whether to reject the session. The method includes the following steps:

Step 301: The AMF receives a request message. The request message includes an identifier of the session, and the session is a session to be activated or to be switched.

For example, in a service request (service request) process, the request message may be a service request message sent by the UE to the AMF through the RAN, and the service request message includes the identifier of the PDU session to be activated, for example, the identifier of the PDU session to be activated When there is more than one, the service request message may include a list of PDU session identifiers, and the list of PDU session identifiers includes identifiers of PDU sessions to be activated.

For another example, in the Xn or N2 handover procedure, the request message may be a handover request message sent by the RAN to the AMF. The handover request message includes the identifier of the PDU session to be switched, for example, when the identifier of the PDU session to be activated is more than one At this time, the service request message may include a list of PDU session identifiers, and the list of PDU session identifiers includes identifiers of PDU sessions to be activated.

As an implementation method, the service request message may also include the location information of the UE.

For each session to be activated or to be switched, the following step 302 to step 305 are performed, and further step 306 to step 307 or step 308 to step 312 can be performed.

Step 302: The AMF determines that the UE moves out of the service range of the second SMF, and selects the first SMF for the UE.

The second SMF here is the SMF that serves the UE before the UE moves. For example, the AMF can determine that the UE has moved out of the service range of the second SMF according to the location information reported by the UE and the service range information of the second SMF, and then according to the location information of the UE, the service range information of the SMF in the network and the SMF in the network Select a new SMF for the UE, namely the first SMF.

In step 303, the AMF sends a session creation request message to the first SMF. Correspondingly, the first SMF may receive the session creation request message. The session creation request message includes the above-mentioned session identifier and the second SMF identifier.

The session creation request message is used to request the first SMF to create the context of the above-mentioned session.

Step 304: The first SMF obtains the context of the session from the second SMF.

For example, the first SMF sends a context request message to the second SMF, which carries the identifier of the session, and then the second SMF returns a context response message to the first SMF, which carries the context of the session.

Step 305: The first SMF determines to reject the session according to the context of the session.

In an implementation method, the context of the session acquired by the first SMF from the second SMF includes the SSC mode of the session, and the SSC mode is SSC mode 2, then the first SMF is SSC mode 2 according to the SSC mode of the session. Decline the conversation. Since SSC mode 2 can release the session first and then establish a new session, if the session is not rejected, the session may be released after the session is activated, wasting network resources. Therefore, the first SMF determines that the SSC mode of the session is SSC In mode2, the session is rejected.

In yet another implementation method, the context of the session acquired by the first SMF from the second SMF includes that the session is a non-supervised priority service session or a non-emergency service session, and the session creation request message in step 303 also includes Including the indication that the UE can only use the supervised priority service, the session is determined to be rejected. The indication that the UE can only use the supervised priority service can be generated when the AMF determines that the new location of the UE is in a non-allowed area according to the location information of the UE. That is, when the UE is in the non-allowed area, the UE only The supervisory priority service can be used. Therefore, when it is determined that the UE can only use the supervisory priority service and the session is a non-supervised priority service session or a non-emergency service session, the first SMF rejects the session.

Based on the above solution, through the interaction between multiple SMFs (that is, the first SMF and the second SMF), the processing of the session to be activated or to be switched is realized.

Further, after the above step 305, there may be the following two implementation methods, which will be described separately below.

Implementation method 1, do not insert the first SMF.

After the above step 305, the following step 306 to step 307 can also be performed.

Step 306: The first SMF sends a response message to the AMF. Correspondingly, the AMF can receive the response message.

The response message is used to reject the above-mentioned session creation request, or understood as the response message used to indicate rejection of the session, or understood as the response message used to indicate that the session activation fails. At this time, there is no end-to-end path for the session (including the N9 tunnel between the first UPF and A-UPF, the N3 tunnel between the first UPF and the RAN, and the wireless connection between the RAN and the UE).

It should be noted that the response message is used to indicate the failure of the session activation, and includes two scenarios: in the service request process, the UE requests to activate the session, at this time the response message is used to indicate the failure of the session activation; or, In the handover procedure, the RAN initiates a request to switch the session, and the response message used to indicate that the session activation fails should be understood as the response message used to indicate that the session switch fails. That is, in the handover scenario, if the first SMF determines to reject the session, the first SMF sends a response message to the AMF. The response message is used to indicate that the session has failed to be activated. It can be replaced with that the response message is used to indicate the session Switching failed. It should be noted that the specific explanations for session activation failures in different application scenarios are applicable to all positions in this application file, and a unified explanation is provided here, and the details are not repeated in the following. Optionally, the response message includes a rejection reason value, and the rejection reason value may be: the session is rejected, that is, the AMF is notified that the session is rejected. The rejection reason value can also be a specific rejection reason. For example, it can be: the UE can only use the supervisory priority service and the session is a non-supervised priority service session, or: the UE can only use the supervisory priority service and the session is a non-emergency service Session, or: SSC mode of the session is SSC mode 2.

Step 307: AMF deletes the information of the first SMF.

Optionally, if the above solution is applied to the service request process and the service request process is triggered by the second SMF receiving a downlink data notification (DDN, downlink data notification), then after step 307, the AMF may also send a notification to the second SMF A failure notification message is sent, and the failure notification message includes a rejection reason value. The implementation method of the rejection reason value is the same as the implementation method of the rejection reason value in the foregoing step 306, and the foregoing description can be referred to. Therefore, the second SMF may notify the second UPF to stop sending notifications of the arrival of downlink data to the second SMF. In this way, resource expenditure can be saved.

Optionally, if the above solution is applied to the Xn handover or X2 handover process, after step 307, the AMF may also send a session update request message to the second SMF. The session update request message includes the session identifier, and the session update request message is used for The session is requested to be deactivated, and the second SMF may notify the second UPF managed by the second SMF to delete the N3 tunnel corresponding to the session. Further, the AMF may also send a session switching failure notification message to the RAN, and the message may include the above rejection reason value, so that the RAN may delete the radio resource corresponding to the session. In this way, resources can be saved and resource utilization can be improved.

Based on the above solution of step 301 to step 307, the processing of the session to be activated or to be switched is realized through the interaction between multiple SMFs (ie, the first SMF, the second SMF, and the A-SMF).

Implementation method 2, insert the first SMF.

Step 308: The first SMF selects the first UPF, and creates an N4 session between the first SMF and the first UPF.

Step 309: The first SMF sends a session context update request message to the A-SMF. Accordingly, the A-SMF can receive the session context update request message. The session context update request message includes the tunnel information of the first UPF, and the session context update The request message is used to request the creation of a tunnel between the A-UPF managed by the A-SMF and the first UPF.

Step 310: The A-SMF sends a notification message to the A-UPF. The notification message includes tunnel information of the first UPF. The notification message is used to notify the establishment of a downlink tunnel between the A-UPF and the first UPF.

After the A-UPF receives the tunnel information of the first UPF, it records the tunnel information of the first UPF, thereby establishing a downlink tunnel from the A-UPF to the first UPF.

Further, the A-SMF may also send A-UPF tunnel information to the first SMF, and then the first SMF sends the A-UPF tunnel information to the first UPF, thereby establishing an uplink tunnel from the first UPF to the A-UPF.

Step 311: The first SMF sends a response message to the AMF. Correspondingly, the AMF can receive the response message.

The response message is used to indicate that the session activation fails, but the session context of the first SMF is successfully established. Or it can be understood that the response message is used to indicate that the end-to-end user plane path of the session (including the path between UE and RAN, RAN and first UPF, and first UPF and A-UPF) failed to activate, but the first Tunnel between UPF and A-UPF. Or it can be understood that the response message is used to indicate that the first SMF has successfully created the context of the session, and the tunnel between the first UPF and A-UPF (ie, the N9 tunnel) has been successfully established, but the first UPF and the RAN have not been established. The inter-tunnel (ie N3 tunnel), and the wireless connection between the RAN and the UE is not established.

Optionally, the response message includes a rejection reason value, and the rejection reason value may be: the session is rejected, that is, the AMF is notified that the session is rejected. The rejection reason value can also be a specific rejection reason. For example, it can be: the UE can only use the supervisory priority service and the session is a non-supervised priority service session, or: the UE can only use the supervisory priority service and the session is a non-emergency service Session, or: SSC mode of the session is SSC mode 2.

Step 312: The AMF sends a session context release request message to the second SMF. The session context release request message includes the identifier of the session, and the session context release request message is used to indicate the context of the session to be released.

Based on this step, the second SMF releases the stored context of the session.

Based on the above steps 301-305, and steps 308-312, even though the session is rejected, the first SMF and the first UPF are still inserted, and the context of the session is established on the first SMF, and the first UPF and A are established. -A tunnel between UPF, but no tunnel between the first UPF and RAN, that is, a session is established but the session is not activated. In this way, it helps that when the session is allowed (for example, the UE moves to a new location under the management of the first UPF, and the UE is in the allowed area), there is no need to insert the first SMF and the first UPF. The operation helps to improve the switching or activation speed of the session, which can improve efficiency.

As shown in FIG. 4, the present application provides yet another method for processing a session. The method is described for the second scenario above, and in this method, the A-SMF determines whether to reject the session. The method includes the following steps:

Step 401 to step 404 are the same as step 301 to step 304 in the embodiment of FIG. 3, and reference may be made to the foregoing description, which will not be repeated here.

Step 405: The first SMF selects the first UPF, and creates an N4 session between the first SMF and the first UPF.

Step 406: The first SMF sends a session context update request message to the A-SMF. Accordingly, the A-SMF may receive the session context update request message. The session context update request message includes the tunnel information of the first UPF, and the session context update The request message is used to request the creation of a tunnel between the A-UPF managed by the A-SMF and the first UPF.

Step 407: The A-SMF determines to reject the session according to the context of the session.

In an implementation method, the A-SMF can obtain the context of the session locally, the context of the session includes the SSC mode of the session, and the SSC mode is SSC mode 2, then the A-SMF is SSC according to the SSC mode of the session mode 2, confirm to reject the session. Since SSC mode 2 releases the session first and then establishes the session, if the session is not rejected, the session may be released after activating the session, which wastes network resources. Therefore, A-SMF determines that the SSC mode of the session is SSC mode 2 , It is determined to reject the conversation.

In another implementation method, the context of the session acquired locally by the A-SMF includes that the session is a non-supervised priority service session or a non-emergency service session, and the session creation request message in step 403 also includes the UE Only use the supervision priority service indication, the session context update request message in step 406 also includes an indication that the UE can only use the supervision priority service, then the A-SMF determines to reject the session, that is, it is determined not to create the session on the first SMF Context. The indication that the UE can only use the supervised priority service can be generated when the AMF determines that the new location of the UE is in a non-allowed area according to the location information of the UE. That is, when the UE is in the non-allowed area, the UE only The supervised priority service can be used. Therefore, the A-SMF determines that the UE can only use the supervised priority service, and the session is a non-supervised priority service session or a non-emergency service session, and the session is rejected.

Step 408: The A-SMF sends a notification message to the A-UPF. The notification message includes tunnel information of the first UPF, and the notification message is used to notify the establishment of a downlink tunnel between the A-UPF and the first UPF.

Further, the A-SMF may also send A-UPF tunnel information to the first SMF. For example, the A-UPF tunnel information may be sent to the first SMF in the following step 409, and then the first SMF may send A-UPF to the first UPF. UPF tunnel information, thereby establishing an uplink tunnel from the first UPF to the A-UPF.

It should be noted that there is no strict restriction on the execution order of step 408 in this application. It can be executed at any step after step 406, for example, it can be executed after step 407 and before step 409, or it can be executed after step 406 and step 407. The previous execution may also be executed after step 409 and before step 410, or may be executed after step 410 before step 411, and so on.

In step 409, the A-SMF sends instruction information to the first SMF. Accordingly, the first SMF can receive the instruction information, and the instruction information is used to indicate that the session is rejected.

Optionally, the A-SMF also sends a rejection reason value to the first SMF. The implementation method of the rejection reason value is the same as that in the embodiment of FIG. 3, and reference may be made to the foregoing description.

For example, the A-SMF sends a session context response message to the first SMF, and the message carries the foregoing indication information. Optionally, the message may also include tunnel information of the A-UPF. Optionally, the message may also include a rejection reason value.

Step 410: The first SMF sends a response message to the AMF. Correspondingly, the AMF can receive the response message.

This step 410 is the same as step 311 in the embodiment of FIG. 3, and reference may be made to the foregoing description.

Optionally, the following step 411 may also be included.

Step 411: The AMF sends a session context release request message to the second SMF. The session context release request message includes the identifier of the session, and the session context release request message is used to indicate the context of the session to be released.

Based on this step, the second SMF releases the stored context of the session.

Based on the above solution of steps 401 to 411, the interaction between multiple SMFs (ie, the first SMF, the second SMF, and the A-SMF) realizes the processing of the session to be activated or to be switched. The context of the session is established on the first SMF, and the tunnel between the first UPF and the A-UPF is established, but the tunnel between the first UPF and the RAN is not established, that is, the session is established but the session is not activated.

The solution of the embodiment shown in FIG. 3 or FIG. 4 will be specifically described below in conjunction with specific embodiments. Among them, in the following embodiments of Figures 5 to 10, the first SMF is referred to as a new I-SMF (or New I-SMF) or a target I-SMF (or Target I-SMF), and the first SMF The second SMF is called the old I-SMF (or Old I-SMF) or the source I-SMF (or Source I-SMF), and the first UPF is called the new I-UPF (or New I -UPF) or target I-UPF (or Target I-UPF), the second UPF is called the old I-UPF (or Old I-UPF) or the source I-UPF (or Source I -UPF).

It should be noted that in the following embodiments of Figures 5 to 10, the active session refers to the end-to-end user plane path of the active session, including the establishment of the N3 tunnel between the New I-UPF and the RAN, and the New I-UPF N9 tunnel with A-UPF and wireless connection between RAN and UE. Inactive session or session activation failure refers to the end-to-end user plane path of the inactive session, that is, the N3 tunnel between New I-UPF and RAN is not established, and/or, New I-UPF and A- are not established. The N9 tunnel between UPFs, and/or, the wireless connection between RAN and UE is not established.

As shown in FIG. 5, it is a schematic flowchart of another session processing method provided by this application. This embodiment is applied to the service request process. This process can be initiated by the UE side. For example, the UE wants to access a certain service or transmit data, or it can be initiated by the network side. For example, when Old I-SMF receives a downlink data notification, Old I-SMF notifies AMF to initiate a paging. After success, the UE initiates a service request.

Step 501-Step 502, Old I-UPF receives the downlink data packet, Old I-UPF sends a downlink data notification (DDN) to Old I-SMF, Old I-SMF receives the DDN and sends session related information (PDU session ID) , N2 SM container, etc.) are sent to AMF, and AMF pages the UE.

The above steps 501 to 502 are optional steps. When the service request process is initiated by the network side, the above steps 501 to 502 are executed.

In step 503, the UE sends a service request message to the AMF. Correspondingly, the AMF receives the service request message. The service request message includes information such as the PDU session ID(s) to be activated and the UE location (UE location). If the scenario is triggered by the network side, the PDU session ID(s) to be activated in the service request message includes the PDU session ID described in step 501.

For each PDU session ID to be activated, that is, for each session, perform the following steps 504-510:

Step 504: The AMF detects that the UE has moved out of the service range of the Old I-SMF, and the AMF reselects and inserts a New I-SMF.

Step 505: The AMF sends a session creation request message to the New I-SMF, and the message carries the PDU session ID and the identifier of the Old I-SMF.

Optionally, the message also carries an indication that the UE can only use the supervised priority service.

Step 506: The New I-SMF obtains the session context from the Old I-SMF.

The session context includes the SSC mode of the session, and/or whether the session is a non-emergency service session or a non-supervised priority service session and other information.

Step 507: The New I-SMF judges whether the session can be activated according to the session context.

For the specific judgment method, reference may be made to the related description in the embodiment in FIG. 3, which will not be repeated here.

Step 508: If the session cannot be activated, the New I-SMF does not create the session, and the New I-SMF sends a response message to the AMF.

The response message is used to indicate that the session activation failed. Specifically, the N3 tunnel between the New I-UPF and the RAN is not established, the N9 tunnel between the New I-UPF and the A-UPF is not established, and the wireless connection between the RAN and the UE is not established.

Optionally, the message includes a rejection reason value. After receiving the response message, the AMF deletes the New I-SMF information.

Step 509: If the AMF receives the response message and the service request process is triggered by the Old I-SMF, the AMF sends a failure notification message to the old I-SMF.

Optionally, the failure notification message includes a rejection reason value.

Step 510: The Old I-SMF notifies the Old I-UPF to stop sending the DNN according to the failure notification message.

Optionally, the Old I-SMF sends the rejection reason value to the A-SMF. If the session is SSC mode2 and the rejection session is caused by the insertion of the I-SMF, the SMF can notify the UE to reestablish the session.

Based on the above solution, the processing of the session to be activated is realized through the interaction between multiple SMFs. The establishment of the session is rejected, and the New I-SMF information can be deleted on the AMF.

As shown in FIG. 6, it is a schematic flowchart of another session processing method provided by this application. This embodiment is applied to the Xn handover procedure triggered by the movement of the UE. The method includes the following steps:

Step 601: The RAN sends a path switch (path switch) request message to the AMF, which carries the PDU session ID(s) to be switched.

For each PDU session ID to be switched, that is, for each session, perform the following steps:

Step 602 to step 605 are the same as step 504 to step 507 in the embodiment of FIG. 5.

Step 606: If the session cannot be activated, the New I-SMF does not create the session, and the New I-SMF sends a session response message to the AMF.

In addition, the New I-SMF also sends N2 session management (session management, SM) information to the AMF. The N2 SM information includes a rejection reason value and is used to notify the RAN of the reason for rejecting the session switch. Wherein, the N2 SM information is included in the response message.

In step 607, the AMF sends N2 SM information to the RAN, and the information contains the rejection reason value.

Step 608: The RAN deletes the radio resource corresponding to the session.

Step 609: The AMF sends a session update request message to the old I-SMF, where the message is used to instruct the old I-SMF to deactivate the session.

Optionally, the AMF may also include information that needs to be sent to the A-SMF (for example, a secondary (Secondary) radio access technology (radio access technology, RAT) usage report (usage report)) in this message.

Step 610: The Old I-SMF notifies the Old I-UPF to delete the N3 tunnel corresponding to the session.

Step 611: The Old I-SMF sends a session update request message to the A-SMF.

This step is optional. If the session update request message in step 609 includes information that needs to be sent to A-SMF, perform this step, and use the session update request message in step 611 to send the AMF information to the A-SMF Send to A-SMF.

Step 612: The Old I-SMF sends a response message to the AMF, where the response message is used to notify the success of the deactivation session.

Based on the above solution, the processing of the session to be switched is realized through the interaction between multiple SMFs. Reject the establishment of the session, and delete the New I-SMF information on the AMF.

As shown in FIG. 7, it is a schematic flowchart of another method for processing a session provided by this application. This embodiment is applied to the N2 handover procedure triggered by UE movement. The method includes the following steps:

Step 701: The source RAN (S-RAN) sends a path switch request message to the source AMF (S-AMF), and the message carries information such as the PDU session ID(s) to be switched.

Among them, the source RAN is the RAN that the UE is connected to before the handover, and the source AMF is the AMF that serves the UE before the handover.

Step 702, the S-AMF sends a path switch request message to the target AMF (T-AMF) selected by the S-AMF or the target RAN (T-RAN), creates a context on the T-AMF, and the message contains the PDU to be switched. session ID(s) and other information.

The target AMF is the AMF that serves the UE after the handover.

The target RAN is the RAN that provides services for the UE after the handover.

For each session ID of the PDU to be switched, that is, for each session, perform step 703 to step 713:

Steps 703 to 707 are the same as steps 602 to 606 in the embodiment of FIG. 6, and reference may be made to the foregoing description.

Step 708, switch the subsequent process.

Please refer to the description of the prior art, which will not be repeated here.

In step 709, the T-AMF sends a handover notification message to the S-AMF. The message is used to notify the RAN that the session switch fails, and the message contains the rejection reason value.

The message includes N2 SM information sent to the RAN, and the N2 SM information includes a rejection reason value, which is used to notify the RAN of the reason for rejecting session switching.

Optionally, the T-AMF may also send the rejected session information to the S-AMF, for example, a list of PDU Session IDs corresponding to the rejected sessions. The S-AMF informs the OldI-SMF corresponding to the rejected session that the session switch is rejected. Correspondingly, in step 710, in addition to the T-AMF notifying the Old I-SMF, the S-AMF may also notify the Old I-SMF to deactivate the rejected session.

Step 710 to step 713 are the same as step 609 to step 612 in the embodiment of FIG. 6, and refer to the foregoing description.

Based on the above solution, the processing of the session to be switched is realized through the interaction between multiple SMFs. Reject the establishment of the session, and delete the New I-SMF information on the T-AMF.

As shown in FIG. 8, it is a schematic flowchart of another method for processing a session provided by this application. This embodiment is applied to the service request process. The process can be initiated by the UE side. For example, the UE wants to access a certain service or transmit data, or it can be initiated by the network side. For example, when Old I-SMF receives a downlink data notification, Old I-SMF SMF notifies AMF to initiate paging, and the UE initiates a service request after successful paging.

The difference between the embodiment in FIG. 8 and the embodiment in FIG. 5 is that in this embodiment, although the session is rejected, the session is still established but the session is not activated. Specifically, New I-SMF and New I-UPF are inserted, and the N9 tunnel between New I-UPF and A-UPF is established, but the N3 tunnel between RAN and New I-UPF is not established.

The method includes the following steps:

Steps 801 to 806 are the same as steps 501 to 506 in the embodiment of FIG. 5, and reference may be made to the foregoing description.

Step 807, the session path between New I-SMF and A-SMF is updated, including New I-SMF selection and insertion of New I-UPF, creation of N4 session between New I-SMF and New I-UPF, New I-SMF SMF sends a session update request message to A-SMF, and sends the N9 tunnel information of New I-UPF to A-SMF, so that A-SMF can establish a tunnel between A-UPF and New I-UPF.

For the specific implementation process of this step, reference may be made to the related description of the embodiment in FIG. 3.

Step 808: New I-SMF determines that the session cannot be activated, and sends a response message to the AMF.

The response message in this step 808 has the same function and implementation method as the response message in step 311 in the embodiment of FIG. 3, and reference may be made to the foregoing description, which will not be repeated here.

Among them, there are two specific methods for New I-SMF to determine that the session cannot be activated. One is that New I-SMF determines that the session cannot be activated according to the context of the session. For details, refer to the description of the embodiment in FIG. 2 and the other is A-SMF. It is determined that the session cannot be activated and the indication information is sent to the New I-SMF. For details, refer to the description of the embodiment in FIG. 3.

Step 809: The AMF sends a session context release request message to the Old I-SMF, and the message instructs the Old I-SMF to delete the session context.

Step 810: The Old I-SMF notifies the Old I-UPF to delete the session.

Based on the above solution, the processing of the session to be switched is realized through the interaction between multiple SMFs. And establish the context of the session on the first SMF, establish a tunnel between New I-UPF and A-UPF, but not establish a tunnel between New I-UPF and RAN, that is, establish a session but not activate the session.

As shown in FIG. 9, it is a schematic flowchart of another method for processing a session provided by this application. This embodiment is applied to the Xn handover procedure triggered by the movement of the UE.

The difference between the embodiment in Fig. 9 and the embodiment in Fig. 6 is that in this embodiment, although the session is rejected, New I-SMF and New I-UPF are still inserted, and the N9 tunnel between New I-UPF and A-UPF is established. , But the N3 tunnel between RAN and New I-UPF is not established.

The method includes the following steps:

Steps 901 to 904 are the same as steps 601 to 604 in the embodiment of FIG. 6, and reference may be made to the foregoing description.

Step 905 to step 906 are the same as step 807 to step 808 in the embodiment of FIG. 8, and reference may be made to the foregoing description.

Step 907 to step 912 are the same as step 607 to step 612 in the embodiment of FIG. 6, and reference may be made to the foregoing description.

As shown in FIG. 10, it is a schematic flowchart of another session processing method provided by this application. This embodiment is applied to the X2 handover procedure triggered by the movement of the UE.

The difference between the embodiment in FIG. 10 and the embodiment in FIG. 7 is that in this embodiment, although the session is rejected, New I-SMF and New I-UPF are still inserted, and the N9 tunnel between New I-UPF and A-UPF is established. , But the N3 tunnel between RAN and New I-UPF is not established.

The method includes the following steps:

Step 1001 to step 1005 are the same as step 701 to step 705 in the embodiment of FIG. 7, and reference may be made to the foregoing description.

Steps 1006-step 1007 are the same as steps 807-808 in the embodiment of FIG. 8, and reference may be made to the foregoing description.

Step 1008 to step 1013 are the same as step 708 to step 713 in the embodiment of FIG. 7, and reference may be made to the foregoing description.

It should be noted that, in each of the above-mentioned embodiments of the present application, the above-described scenario two (that is, including at least two I-SMFs and one A-SMF) is taken as an example for description. For the foregoing scenario one (that is, including one The I-SMF and one A-SMF) can be implemented with reference to the solutions of the foregoing embodiments. Specifically, part or all of the operations for the second SMF in the foregoing embodiments may be combined into the A-SMF.

Therefore, the present invention discloses a session processing method. The method includes: a first session management network element receives a session creation request message from a mobility management network element, and the session creation request message includes a session identifier of the terminal device and a second The identifier of the session management network element, the session is the session to be activated or switched (refer to the description of step 303, step 505, step 603, step 704, step 805, step 903, step 1004); the first session management network element Obtain the context of the session from the second session management network element (refer to the description of step 304, step 506, step 604, step 705, step 806, step 904, and step 1005); the first session management network element according to the context of the session, Decide to reject the conversation (refer to the description of step 305, step 507, step 605, step 706, step 806, step 904, and step 1005).

In a possible implementation method, the first session management network element sends a response message to the mobility management network element, and the session response message is used to indicate that the session activation fails (refer to step 306, step 508, description of step 606, step 707).

In yet another possible implementation method, the first session management network element sends a response message to the mobility management network element, where the response message is used to indicate that the session is successfully established but the session activation fails ( (Refer to the description of step 311, step 808, step 912, and step 1013 above).

In a possible implementation method, the first session management network element selects the first user plane network element (refer to the description of step 308 above), and creates a connection between the first session management network element and the first user plane network element. N4 session; the first session management network element sends a session context update request message to the anchor session management network element (refer to the description of step 309 above), the session context update request message includes the tunnel information of the first user plane network element, and the session context The update request message is used to request the creation of a tunnel between the anchor user plane network element managed by the anchor session management network element and the first user plane network element.

Therefore, the present invention discloses a session processing method. The method includes: a first session management network element receives a session creation request message from a mobility management network element, and the session creation request message includes a session identifier of the terminal device and a second The identifier of the session management network element, the session is the session to be activated or switched (refer to the description of step 403, step 805, step 903, and step 1004 above); the first session management network element selects the first user plane network element (may be Refer to the description of step 405 above), and create an N4 session between the first session management network element and the first user plane network element; the first session management network element sends a session context update request message to the anchor session management network element, and the session The context update request message includes the tunnel information of the first user plane network element, and the session context update request message is used to request the creation of a tunnel between the anchor user plane network element managed by the anchor session management network element and the first user plane network element ( (Refer to the description of step 406 above); the first session management network element receives indication information from the anchor session management network element, and the indication information is used to indicate the rejection of the session (refer to the description of step 409 above); the first session management network element A response message is sent to the mobility management network element, where the response message is used to indicate that the session activation fails, but the session context of the first session management network element is successfully established (refer to the description of step 4104 above).

In a possible implementation method, the first session management network element obtains the context of the session from the second session management network element (refer to the description of step 404, step 806, step 904, and step 1005).

Therefore, the present invention discloses a session processing method. The method includes: an anchor session management network element receives a session context update request message from a first session management network element, and the session context update request message includes the first session management network element The selected tunnel information of the first user plane network element, the session context update request message is used to request the creation of a tunnel between the anchor user plane network element managed by the anchor session management network element and the first user plane network element (refer to the above Description of step 406); the anchor session management network element obtains the context of the session, and according to the context of the session, determines to reject the session (refer to the description of step 407 above); the anchor session management network element sends to the first session management network element Indication information, the indication information is used to indicate rejection of the session (refer to the description of step 409 above).

Therefore, the present invention discloses a session processing method. The method includes: the mobility management network element receives a request message, the request message includes the session identifier of the terminal device, and the session is a session to be activated or to be switched (refer to the above steps 301, step 401, step 503, step 601, step 702, step 803, step 901, step 1002); the mobility management network element determines that the terminal device moves out of the service range of the second session management network element, and selects the terminal device The first session management network element (refer to the description of step 302, step 402, step 504, step 602, step 703, step 804, step 902, step 1003); the mobility management network element sends to the first session management network element Session creation request message. The session creation request message includes the identifier of the session and the identifier of the second session management network element (refer to the above step 303, step 403, step 505, step 603, step 704, step 805, step 903, step 1004) Description); the mobility management network element receives a response message or a response message for the session creation request message from the first session management network element, the response message is used to indicate that the session activation fails, or the response message is used to indicate The session activation failed, but the session context of the first session management network element was successfully established (refer to step 306, step 311, step 410, step 508, step 606, step 707, step 808, step 906, step 1007). description of). The response message includes the rejection reason value, and the rejection reason value is any of the following: the session is rejected, the terminal device can only use the supervised priority service and the session is a non-supervised priority service session or a non-emergency service session, and the SSC mode of the session is first Release the current session and create a new session.

In a possible implementation method, in the service request process of the terminal device, the mobility management network element sends a failure notification message to the second session management network element, and the failure notification message includes the rejection reason value.

In a possible implementation method, the mobility management network element sends a session context release request message to the second session management network element, the session context release request message includes the session identifier, and the session context release request message is used to indicate the context of the session to be released (Refer to the description of step 411 and step 809 above).

It should be noted that, in the foregoing embodiments of the present application, if it is determined that a certain session or sessions can be activated, the context of the session is established on the first SMF and the session is activated. The specific implementation process can refer to the prior art. The related description of, this application will not repeat it.

It should be noted that the names of the above-mentioned messages are only examples. With the evolution of communication technology, any of the above-mentioned messages may change its name, but no matter how its name changes, as long as its meaning is the same as the meaning of the above-mentioned message in this application , All fall within the protection scope of this application.

The foregoing mainly introduces the solution provided by this application from the perspective of interaction between various network elements. It can be understood that, in order to realize the above-mentioned functions, each network element described above includes hardware structures and/or software modules corresponding to each function. Those skilled in the art should easily realize that in combination with the units and algorithm steps of the examples described in the embodiments disclosed herein, the present invention 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. Professionals and technicians can use different methods for each specific application to implement the described functions, but such implementation should not be considered as going beyond the scope of the present invention.

As shown in FIG. 11, it is a possible exemplary block diagram of a session processing apparatus involved in this application. The session processing apparatus 1100 may exist in the form of software or hardware. The session processing apparatus 1100 may include: a processing unit 1102 and a communication unit 1103. As an implementation manner, the communication unit 1103 may include a receiving unit and a sending unit. The processing unit 1102 is used to control and manage the actions of the session processing device 1100. The communication unit 1103 is used to support communication between the session processing device 1100 and other network entities. The session processing device 1100 may further include a storage unit 1101 for storing program codes and data of the session processing device 1100.

The processing unit 1102 may be a processor or a controller, for example, a general-purpose central processing unit (central processing unit, CPU), a general-purpose processor, a digital signal processing (digital signal processing, DSP), and an application specific integrated circuit (application specific integrated circuit). circuits, 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 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 storage unit 1101 may be a memory. The communication unit 1103 is an interface circuit of the device for receiving signals from other devices. For example, when the device is implemented as a chip, the communication unit 1103 is an interface circuit used by the chip to receive signals from other chips or devices, or an interface circuit used by the chip to send signals to other chips or devices.

The session processing device 1100 may be a session management network element (such as a first session management network element or an anchor session management network element) in any of the above embodiments, and may also be a chip for a session management network element. For example, when the session processing apparatus 1100 is a session management network element, the processing unit 1102 may be, for example, a processor, and the communication unit 1103 may be, for example, a transceiver. Optionally, the transceiver may include a radio frequency circuit, and the storage unit may be, for example, a memory. For example, when the session processing device 1100 is a chip for a session management network element, the processing unit 1102 may be, for example, a processor, and the communication unit 1103 may be, for example, an input/output interface, a pin, or a circuit. The processing unit 1102 can execute computer-executable instructions stored in the storage unit. Optionally, the storage unit is a storage unit in the chip, such as a register, a cache, etc., and the storage unit may also be a storage unit located in the session management network element. The storage unit outside the chip, such as read-only memory (ROM) or other types of static storage devices that can store static information and instructions, random access memory (RAM), etc.

In the first embodiment, the device 1100 for processing the session is the first session management network element in the above example, and the communication unit 1103 of the first session management network element includes a sending unit and a receiving unit. The receiving unit is configured to receive a session creation request message from the mobility management network element, the session creation request message includes the session identifier of the terminal device and the identifier of the second session management network element, and the session is a session to be activated or to be switched; processing; The unit is used to obtain the context of the session from the second session management network element; and, according to the context of the session, determine to reject the session.

In a possible implementation method, the context of the session includes the SSC mode of the session, and the SSC mode is to release the current session first and then create a new session; the processing unit is specifically used to release the current session and then create a new session according to the SSC mode of the session. Decline the session.

In a possible implementation method, the session creation request message also includes an indication that the terminal device can only use the supervised priority service, and the context of the conversation includes the session that is a non-supervised priority service or a non-emergency service; the processing unit is specifically used According to the terminal device can only use the supervised priority service and the session is a non-supervised priority service session or a non-emergency service session, the session is determined to be rejected.

In a possible implementation method, the sending unit is configured to send a response message to the mobility management network element, where the response message is used to indicate that the session activation fails.

In another possible implementation method, the sending unit is configured to send a response message to the mobility management network element, where the response message is used to indicate that the session activation fails but the first session management network element The session context was successfully established.

In a possible implementation method, the processing unit is also used to select the first user plane network element and create an N4 session between the first session management network element and the first user plane network element; the sending unit is also used to Send a session context update request message to the anchor session management network element, the session context update request message includes the tunnel information of the first user plane network element, and the session context update request message is used to request the creation of the anchor point user managed by the session management network element A tunnel between the plane network element and the first user plane network element.

In a possible implementation method, the device is a first intermediate session management network element, and the second session management network element is a second intermediate session management network element; or, the device is an intermediate session management network element, and the second session management network element The network element is an anchor session management network element.

In the second embodiment, the device 1100 for processing the session is the first session management network element in the above example, and the communication unit 1103 of the first session management network element includes a sending unit and a receiving unit. The receiving unit is configured to receive a session creation request message from the mobility management network element, the session creation request message includes the session identifier of the terminal device and the identifier of the second session management network element, and the session is a session to be activated or to be switched; processing; The unit is used to select the first user plane network element and create an N4 session between the first session management network element and the first user plane network element; the sending unit is used to send a session context update request to the anchor session management network element The session context update request message includes the tunnel information of the first user plane network element, and the session context update request message is used to request the creation of an anchor point between the anchor user plane network element managed by the session management network element and the first user plane network element The receiving unit is also used to receive indication information from the anchor session management network element, the indication information is used to indicate that the session is rejected; the sending unit is also used to send a response message to the mobility management network element, and the response message is used Indicates that the session is successfully established, but the session activation fails.

In a possible implementation method, the receiving unit is also used to receive the rejection reason value from the anchor session management network element; the response message includes the rejection reason value, and the rejection reason value is any of the following: session rejected, terminal The device can only use the supervisory priority service and the session is a non-supervised priority service session or a non-emergency service session, and the SSC mode of the session is to release the current session and then create a new session.

In a possible implementation method, the processing unit is further configured to obtain the context of the session from the second session management network element.

In a possible implementation method, the session processing device 1100 is a first intermediate session management network element, and the second session management network element is a second intermediate session management network element; or, the session processing device 1100 is an intermediate session The management network element, and the second session management network element is an anchor session management network element.

In the third embodiment, the device 1100 for processing the session is the anchor session management network element in the above example, and the communication unit 1103 of the anchor session management network element includes a sending unit and a receiving unit. The receiving unit is configured to receive a session context update request message from the first session management network element, the session context update request message includes tunnel information of the first user plane network element selected by the first session management network element, and the session context update request message is used When requesting to create a tunnel between the anchor user plane network element and the first user plane network element managed by the anchor session management network element; the processing unit is used to obtain the context of the session, and according to the context of the session, determines to reject the session; The unit is used to send instruction information to the first session management network element, where the instruction information is used to indicate rejection of the session.

In a possible implementation method, the session context update request message also includes an indication that the terminal device can only use the supervised priority service, and the context of the session includes the session for non-supervised priority service or non-emergency service; the processing unit, specifically It is used to determine the rejection of the session based on the terminal device can only use the supervision priority service and the session is a non-supervised priority service session or a non-emergency service session.

In a possible implementation method, the sending unit is further configured to send a rejection reason value to the first session management network element, and the rejection reason value is any one of the following: the session is rejected, the terminal device can only use the supervision priority service, and the session For non-supervised priority service sessions or non-emergency service sessions, the SSC mode of the session is to release the current session first and then create a new session.

In a possible implementation method, the sending unit is further configured to send a notification message to the anchor user plane network element, the notification message includes tunnel information of the first user plane network element, and the notification message is used to notify the establishment of the anchor user plane network. Downlink tunnel between the element and the first user plane network element.

It can be understood that, for the specific implementation process and corresponding beneficial effects when the device for processing the conversation is used in the processing method of the above-mentioned conversation, reference may be made to the relevant description in the foregoing method embodiment, which will not be repeated here.

As shown in FIG. 12, a possible exemplary block diagram of a session processing apparatus involved in this application. The session processing apparatus 1200 may exist in the form of software or hardware. The session processing apparatus 1200 may include: a processing unit 1202 and a communication unit 1203. As an implementation manner, the communication unit 1203 may include a receiving unit and a sending unit. The processing unit 1202 is used to control and manage the actions of the processing device 1200 of the session. The communication unit 1203 is used to support communication between the session processing device 1200 and other network entities. The session processing device 1200 may further include a storage unit 1201 for storing program codes and data of the session processing device 1200.

The processing unit 1202 may be a processor or a controller, for example, a CPU, a general-purpose processor, DSP, ASIC, 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 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 storage unit 1201 may be a memory. The communication unit 1203 is an interface circuit of the device for receiving signals from other devices. For example, when the device is implemented as a chip, the communication unit 1203 is an interface circuit for the chip to receive signals from other chips or devices, or an interface circuit for the chip to send signals to other chips or devices.

The apparatus 1200 for processing the session may be the mobility management network element in any of the foregoing embodiments, and may also be a chip for the mobility management network element. For example, when the processing apparatus 1200 of the session is a mobility management network element, the processing unit 1202 may be, for example, a processor, and the communication unit 1203 may be, for example, a transceiver. Optionally, the transceiver may include a radio frequency circuit, and the storage unit may be, for example, a memory. For example, when the session processing device 1200 is a chip for a mobility management network element, the processing unit 1202 may be a processor, for example, and the communication unit 1203 may be an input/output interface, a pin or a circuit, for example. The processing unit 1202 can execute computer-executable instructions stored in the storage unit. Optionally, the storage unit is a storage unit in the chip, such as a register, a cache, etc., and the storage unit may also be a storage unit located in the mobility management network element. The storage unit outside the chip, such as ROM or other types of static storage devices that can store static information and instructions, RAM, etc.

In an embodiment, the device 1200 for processing the session is a mobility management network element, and the communication unit 1203 includes a sending unit and a receiving unit. The receiving unit is used to receive a request message, the request message includes the session identifier of the terminal device, and the session is a session to be activated or to be switched; the processing unit is used to determine that the terminal device moves out of the service range of the second session management network element, and is The terminal device selects the first session management network element; the sending unit is configured to send a session creation request message to the first session management network element, the session creation request message includes the session identifier and the second session management network element identifier; the receiving unit uses For receiving a response message, a response message or a response message for a session creation request message from a first session management network element, the response message is used to indicate the session activation failure, and the response message is used to indicate the session activation failure , But the session context of the first session management network element is successfully established. The response message includes the rejection reason value, and the rejection reason value is any of the following: the session is rejected, the terminal device can only use the supervised priority service and the session is a non-supervised priority service session or a non-emergency service session, and the SSC mode of the session is first Release the current session and create a new session.

In a possible implementation method, the sending unit is further configured to send a failure notification message to the second session management network element in the service request process of the terminal device, and the failure notification message includes the rejection reason value.

In a possible implementation method, the sending unit is also used to send a session update request message to the second session management network element in the Xn handover or X2 handover process. The session update request message includes the session identifier, and the session update request message Used to request deactivation of the session.

In a possible implementation method, the processing unit is also used to delete the information of the first session management network element.

In a possible implementation method, the sending unit is also used to send a session context release request message to the second session management network element, the session context release request message includes the session identifier, and the session context release request message is used to indicate the release of the session. Context.

Referring to FIG. 13, a schematic diagram of a session processing device provided by this application. The session processing device may be the session management network element in the above embodiment (such as the first session management network element in the above example), or Mobility management network element. The device 1300 for processing the session includes a processor 1302, a communication interface 1303, and a memory 1301. Optionally, the apparatus 1300 for processing the session may further include a communication line 1304. Among them, the communication interface 1303, the processor 1302, and the memory 1301 may be connected to each other through a communication line 1304; the communication line 1304 may be a peripheral component interconnection standard (peripheral component interconnect, PCI for short) bus or an extended industry standard architecture (extended industry standard architecture) , Referred to as EISA) bus and so on. The communication line 1304 can be divided into an address bus, a data bus, a control bus, and so on. For ease of presentation, only one thick line is used in FIG. 13, but it does not mean that there is only one bus or one type of bus.

The processor 1302 may be a CPU, a microprocessor, an ASIC, or one or more integrated circuits used to control the execution of the program of the present application.

Communication interface 1303, using any device such as a transceiver to communicate with other equipment or communication networks, such as Ethernet, radio access network (RAN), wireless local area networks (WLAN), Wired access network, etc.

The memory 1301 can be ROM or other types of static storage devices that can store static information and instructions, RAM or other types of dynamic storage devices that can store information and instructions, or it can be an electrically erasable programmable read-only memory (electrically erasable programmable read-only memory). read-only memory, EEPROM), compact disc (read-only memory, CD-ROM) or other optical disc storage, optical disc storage (including compact discs, laser discs, optical discs, digital universal discs, Blu-ray discs, etc.), magnetic disks A storage medium or other magnetic storage device, or any other medium that can be used to carry or store desired program codes in the form of instructions or data structures and that can be accessed by a computer, but is not limited thereto. The memory can exist independently and is connected to the processor through a communication line 1304. The memory can also be integrated with the processor.

Among them, the memory 1301 is used to store computer-executable instructions for executing the solution of the present application, and the processor 1302 controls the execution. The processor 1302 is configured to execute computer-executable instructions stored in the memory 1301, so as to implement the session processing method provided in the foregoing embodiment of the present application.

Optionally, the computer-executable instructions in the embodiments of the present application may also be referred to as application program code, which is not specifically limited in the embodiments of the present application.

A person of ordinary skill in the art can understand that the various digital numbers such as first and second involved in the present application are only for easy distinction for description, and are not used to limit the scope of the embodiments of the present application, but also indicate a sequence. "And/or" describes the association relationship of the associated objects, indicating that there can be three types of relationships, for example, A and/or B, which can mean: A alone exists, A and B exist at the same time, and B exists alone. The character "/" generally indicates that the associated objects are in an "or" relationship. "At least one" means one or more. At least two means two or more. "At least one", "any one" or similar expressions refer to any combination of these items, including any combination of single item (a) or plural items (a). For example, at least one (piece, species) of a, b, or c can represent: a, b, c, ab, ac, bc, or abc, where a, b, and c can be single or Multiple. "Multiple" refers to two or more, and other measure words are similar. In addition, for elements in the singular form "a", "an" and "the", unless the context clearly dictates otherwise, it does not mean "one or only one", but means "one or more At one". For example, "a device" means to one or more such devices.

In the above embodiments, it may be implemented in whole or in part by software, hardware, firmware or any combination thereof. When implemented by 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. When the computer program instructions are loaded and executed on the computer, the processes or functions described in the embodiments of the present application are generated in whole or in part. The computer may be a general-purpose computer, a special-purpose computer, a computer network, or other programmable devices. The computer instructions may be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another computer-readable storage medium. For example, the computer instructions may be transmitted from a website, computer, server, or data center. Transmission to another website site, computer, server or data center via wired (such as coaxial cable, optical fiber, digital subscriber line (DSL)) or wireless (such as infrared, wireless, microwave, etc.). The computer-readable storage medium may be any available medium that can be accessed by a computer or a data storage device such as a server or a data center integrated with one or more available media. The usable medium may be a magnetic medium (for example, a floppy disk, a hard disk, a magnetic tape), an optical medium (for example, a DVD), or a semiconductor medium (for example, a solid state disk (SSD)), etc.

The various illustrative logic units and circuits described in the embodiments of this application can be implemented by general-purpose processors, digital signal processors, application-specific integrated circuits (ASIC), field programmable gate arrays (FPGA) or other programmable logic devices, Discrete gates or transistor logic, discrete hardware components, or any combination of the above are designed to implement or operate the described functions. The general-purpose processor may be a microprocessor, and optionally, the general-purpose processor may also be any traditional processor, controller, microcontroller, or state machine. The processor can also be implemented by a combination of computing devices, such as a digital signal processor and a microprocessor, multiple microprocessors, one or more microprocessors combined with a digital signal processor core, or any other similar configuration achieve.

The steps of the method or algorithm described in the embodiments of the present application can be directly embedded in hardware, a software unit executed by a processor, or a combination of the two. The software unit can be stored in RAM memory, flash memory, ROM memory, EPROM memory, EEPROM memory, registers, hard disk, removable disk, CD-ROM or any other storage medium in the field. Exemplarily, the storage medium may be connected to the processor, so that the processor can read information from the storage medium, and can store and write information to the storage medium. Optionally, the storage medium may also be integrated into the processor. The processor and the storage medium can be arranged in the ASIC.

These computer program instructions can also be loaded on a computer or other programmable data processing equipment, so that a series of operation steps are executed on the computer or other programmable equipment to produce computer-implemented processing, so as to execute on the computer or other programmable equipment. The instructions provide steps for implementing functions specified in a flow or multiple flows in the flowchart and/or a block or multiple blocks in the block diagram.

Although the application has been described in combination with specific features and embodiments, it is obvious that various modifications and combinations can be made without departing from the spirit and scope of the application. Accordingly, this specification and drawings are merely exemplary descriptions of the application defined by the appended claims, and are deemed to have covered any and all modifications, changes, combinations or equivalents within the scope of the application. Obviously, those skilled in the art can make various changes and modifications to the application without departing from the scope of the application. In this way, if these modifications and variations of this application fall within the scope of the claims of this application and their equivalent technologies, this application is also intended to include these modifications and variations.

Claims

A session processing method, characterized in that it includes:

The first session management network element receives a session creation request message from the mobility management network element, where the session creation request message includes the session identifier of the terminal device and the identifier of the second session management network element, and the session is to be activated or to be Switched session;

Acquiring, by the first session management network element, the context of the session from the second session management network element;

The first session management network element determines to reject the session according to the context of the session.
The method according to claim 1, wherein the context of the session includes the session and service continuity mode SSC mode of the session, and the SSC mode is to release the current session first and then create a new session;

The first session management network element determining to reject the session according to the context of the session includes:

The first session management network element determines to reject the session according to the SSC mode of the session to release the current session and then create a new session.
The method according to claim 1, wherein the session creation request message further includes an indication that the terminal device can only use supervised priority services, and the context of the conversation includes that the session is a non-supervised priority service session Or non-emergency service sessions;

The first session management network element determining to reject the session according to the context of the session includes:

The first session management network element determines to reject the session based on that the terminal device can only use the supervisory priority service and the session is a non-supervised priority service session or a non-emergency service session.
The method according to any one of claims 1-3, further comprising:

The first session management network element sends a response message to the mobility management network element, where the response message is used to indicate that the session activation fails.
The method according to any one of claims 1-3, further comprising:

The first session management network element sends a response message to the mobility management network element, where the response message is used to indicate that the session activation fails but the session context of the first session management network element is successfully established.
The method of claim 5, further comprising:

Selecting, by the first session management network element, a first user plane network element, and creating an N4 session between the first session management network element and the first user plane network element;

The first session management network element sends a session context update request message to the anchor session management network element, where the session context update request message includes tunnel information of the first user plane network element, and the session context update request message is used Upon request to create a tunnel between the anchor user plane network element managed by the anchor session management network element and the first user plane network element.
A session processing method, characterized in that it includes:

The first session management network element receives a session creation request message from the mobility management network element, where the session creation request message includes the session identifier of the terminal device and the identifier of the second session management network element, and the session is to be activated or to be Switched session;

Selecting, by the first session management network element, a first user plane network element, and creating an N4 session between the first session management network element and the first user plane network element;

The first session management network element sends a session context update request message to the anchor session management network element, where the session context update request message includes tunnel information of the first user plane network element, and the session context update request message is used Requesting to create a tunnel between the anchor user plane network element managed by the anchor session management network element and the first user plane network element;

Receiving, by the first session management network element, indication information from the anchor session management network element, where the indication information is used to indicate rejection of the session;

The first session management network element sends a response message to the mobility management network element, where the response message is used to indicate that the session activation fails but the session context of the first session management network element is successfully established.
The method according to claim 7, wherein the session context update request message further includes an indication that the terminal device can only use the supervised priority service.
The method according to claim 7 or 8, further comprising:

Receiving, by the first session management network element, the rejection reason value from the anchor session management network element;

Then the response message includes the rejection reason value, and the rejection reason value is any one of the following: the session is rejected, the terminal device can only use the supervised priority service, and the session is a non-supervised priority service session Or a non-emergency service session, the SSC mode of the session is to release the current session first and then create a new session.
The method according to any one of claims 7-9, further comprising:

The first session management network element obtains the context of the session from the second session management network element.
The method according to claim 10, wherein the first session management network element is a first intermediate session management network element, and the second session management network element is a second intermediate session management network element; or,

The first session management network element is an intermediate session management network element, and the second session management network element is the anchor session management network element.
A session processing method, characterized in that it includes:

The anchor session management network element receives a session context update request message from a first session management network element, where the session context update request message includes tunnel information of a first user plane network element selected by the first session management network element, and The session context update request message is used to request the creation of a tunnel between the anchor user plane network element managed by the anchor session management network element and the first user plane network element;

The anchor session management network element obtains the context of the session, and determines to reject the session according to the context of the session;

The anchor session management network element sends instruction information to the first session management network element, where the instruction information is used to indicate rejection of the session.
The method according to claim 12, wherein the context of the session includes the session and service continuity mode SSC mode of the session, and the SSC mode is to release the current session first and then create a new session;

The anchor session management network element determines to reject the session according to the context of the session, including:

The anchor session management network element determines to reject the session according to the SSC mode of the session to release the current session and then create a new session.
The method of claim 12, wherein the session context update request message further includes an indication that the terminal device can only use a supervised priority service, and the context of the session includes that the session is a non-supervised priority service Conversation or non-emergency service conversation;

The anchor session management network element determines to reject the session according to the context of the session, including:

The anchor session management network element determines to reject the session based on that the terminal device can only use the supervisory priority service and the session is a non-supervised priority service session or a non-emergency service session.
The method according to any one of claims 12-14, further comprising:

The anchor session management network element sends a rejection reason value to the first session management network element, where the rejection reason value is any one of the following: the session is rejected, the terminal device can only use the supervision priority service, and The session is a non-supervised priority service session or a non-emergency service session, and the SSC mode of the session is to release the current session first and then create a new session.
A device for processing a session, which is characterized by comprising a receiving unit and a processing unit;

The receiving unit is configured to receive a session creation request message from a mobility management network element, where the session creation request message includes the identifier of the session of the terminal device and the identifier of the second session management network element, and the session is to be activated or The session to be switched;

The processing unit is configured to obtain the context of the session from the second session management network element; and, according to the context of the session, determine to reject the session.
The device according to claim 16, wherein the context of the session includes the session and service continuity mode SSC mode of the session, and the SSC mode is to release the current session first and then create a new session;

The processing unit is specifically configured to determine to reject the session according to the SSC mode of the session to first release the current session and then create a new session.
The apparatus according to claim 16, wherein the session creation request message further includes an indication that the terminal device can only use supervised priority services, and the context of the conversation includes that the session is a non-supervised priority service session Or non-emergency service sessions;

The processing unit is specifically configured to determine to reject the session based on that the terminal device can only use the supervisory priority service and the session is a non-supervised priority service session or a non-emergency service session.
The device according to any one of claims 16-18, wherein the device further comprises a sending unit, configured to send a response message to the mobility management network element, the response message being used to indicate that the session is activated failure.
The device according to any one of claims 16-18, wherein the device further comprises a sending unit, configured to send a response message to the mobility management network element, the response message being used to indicate that the session is activated Failed, but the session context of the first session management network element was successfully established.
The apparatus according to claim 20, wherein the processing unit is further configured to select a first user plane network element and create an N4 between the first session management network element and the first user plane network element Conversation

The sending unit is further configured to send a session context update request message to the anchor session management network element, where the session context update request message includes tunnel information of the first user plane network element, and the session context update request message is used for Upon request to create a tunnel between the anchor user plane network element managed by the anchor session management network element and the first user plane network element.
A device for processing a session, which is characterized by comprising a receiving unit, a processing unit, and a sending unit;

The receiving unit is configured to receive a session creation request message from a mobility management network element, where the session creation request message includes the identifier of the session of the terminal device and the identifier of the second session management network element, and the session is to be activated or The session to be switched;

The processing unit is configured to select a first user plane network element and create an N4 session between the first session management network element and the first user plane network element;

The sending unit is configured to send a session context update request message to an anchor session management network element, where the session context update request message includes tunnel information of the first user plane network element, and the session context update request message is used for Request to create a tunnel between the anchor user plane network element managed by the anchor session management network element and the first user plane network element;

The receiving unit is further configured to receive indication information from the anchor session management network element, where the indication information is used to indicate rejection of the session;

The sending unit is further configured to send a response message to the mobility management network element, where the response message is used to indicate that the session is successfully established but the session activation fails.
The apparatus according to claim 22, wherein the session context update request message further includes an indication that the terminal device can only use the supervised priority service.
The device according to claim 22 or 23, wherein the receiving unit is further configured to receive a rejection reason value from the anchor session management network element;

Then the response message includes the rejection reason value, and the rejection reason value is any one of the following: the session is rejected, the terminal device can only use the supervised priority service, and the session is a non-supervised priority service session Or a non-emergency service session, the SSC mode of the session is to release the current session first and then create a new session.
The apparatus according to any one of claims 22-24, wherein the processing unit is further configured to obtain the context of the session from a second session management network element.
The device according to claim 25, wherein the device is a first intermediate session management network element, and the second session management network element is a second intermediate session management network element; or,

The device is an intermediate session management network element, and the second session management network element is the anchor session management network element.
A device for processing a session, which is characterized by comprising a receiving unit, a processing unit, and a sending unit;

The receiving unit is configured to receive a session context update request message from a first session management network element, where the session context update request message includes tunnel information of a first user plane network element selected by the first session management network element; The session context update request message is used to request the creation of a tunnel between the anchor user plane network element managed by the anchor session management network element and the first user plane network element;

The processing unit is configured to obtain the context of the conversation, and determine to reject the conversation according to the context of the conversation;

The sending unit is configured to send instruction information to the first session management network element, where the instruction information is used to indicate rejection of the session.
The apparatus according to claim 27, wherein the context of the session includes the session and service continuity mode SSC mode of the session, and the SSC mode is to release the current session first and then create a new session;

The processing unit is specifically configured to determine to reject the session according to the SSC mode of the session to first release the current session and then create a new session.
The apparatus according to claim 27, wherein the session context update request message further includes an indication that the terminal device can only use a supervised priority service, and the context of the session includes that the session is a non-supervised priority service Conversation or non-emergency service conversation;

The processing unit is specifically configured to determine to reject the session based on that the terminal device can only use the supervised priority service and the session is a non-supervised priority service session or a non-emergency service session.
The apparatus according to any one of claims 27-29, wherein the sending unit is further configured to send a rejection reason value to the first session management network element, and the rejection reason value is any one of the following: The session is rejected, the terminal device can only use the supervised priority service and the session is a non-supervised priority service session or a non-emergency service session, and the SSC mode of the session is to release the current session first and then create a new session.