WO2023207229A1 - 一种会话建立方法及装置 - Google Patents

一种会话建立方法及装置 Download PDF

Info

Publication number
WO2023207229A1
WO2023207229A1 PCT/CN2023/072705 CN2023072705W WO2023207229A1 WO 2023207229 A1 WO2023207229 A1 WO 2023207229A1 CN 2023072705 W CN2023072705 W CN 2023072705W WO 2023207229 A1 WO2023207229 A1 WO 2023207229A1
Authority
WO
WIPO (PCT)
Prior art keywords
protocol data
data unit
unit session
bearer context
pdu session
Prior art date
Application number
PCT/CN2023/072705
Other languages
English (en)
French (fr)
Inventor
朱迪
梁晓鸣
Original Assignee
华为技术有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 华为技术有限公司 filed Critical 华为技术有限公司
Publication of WO2023207229A1 publication Critical patent/WO2023207229A1/zh

Links

Classifications

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

Definitions

  • the present application relates to the field of communication technology, and in particular, to a session establishment method and device.
  • the wireless communication system formulated by the 3rd generation partnership project (3GPP) has developed to the fifth generation (the 5th generation, 5G), that is, the new radio (NR) system.
  • the protocol data unit (PDU) session in the NR system plays a similar role to the bearer in the 4G long term evolution (LTE) system. They are both channels for transmitting data for services.
  • LTE long term evolution
  • a PDU session can include multiple QoS flows.
  • QoS Flow is the minimum granularity of QoS differentiation for a PDU session. Different QoS flows adapt to different QoS.
  • a QoS flow in the PDU session can correspond to a mapped EPS bearer context.
  • the mapped EPS bearer context corresponding to the QoS flow may be deleted for some reason. Then, after the terminal device switches between different systems, normal bearer mapping cannot be performed, which may cause service failure. And other issues.
  • This application provides a session establishment method and device to solve the problem of service failure or discontinuity when the terminal device switches between different systems when the PDU session does not have a corresponding mapped 4G bearer context.
  • the present application provides a session establishment method, which can be used for functions on the terminal device side.
  • the embodiments of the present application are not limited to the specific execution subject of the method.
  • the terminal device sends a protocol data unit session release request message, and the protocol data
  • the unit session release request message is used to request the release of the first protocol data unit session; receives the protocol data unit session release command message, and the protocol data unit session release command message is used to indicate the release of the first protocol data unit session; sends Protocol data unit session establishment request message, the protocol data unit session establishment request message is used to request the establishment of a second protocol data unit session; wherein the first protocol data unit session and the second protocol data unit session correspond to the same business.
  • the terminal device when the terminal device determines that the first PDU session does not have a corresponding mapped EPS bearer context, it can actively deactivate the first PDU session, and then re-establish a new second PDU session for the services corresponding to the first PDU session.
  • PDU session thus ensuring that the terminal device performs inter-system switching (for example, switching from NR system to LTE system) process, the reliability and continuity of services can be avoided, and call failures, service interruptions, discontinuities, etc. can be avoided, improving the stability of the system.
  • the terminal device before sending the protocol data unit session release request message, the terminal device is in an idle state or an inactive state.
  • the terminal device Since the terminal device is in the idle state or inactive state, the terminal device does not need to transmit service data through the first PDU session. Therefore, the terminal device releases the first PDU session at this time, which will not affect the services corresponding to the first PDU session.
  • the method before sending the protocol data unit session release request message, the method further includes: no data packet of the service is transmitted through the first protocol data unit session within a preset time period.
  • the terminal device Since the terminal device has not transmitted service data through the first PDU session within the preset time period, it can be considered that there is currently no need to transmit service data. The terminal device releases the first PDU session at this time, which will not affect the services corresponding to the first PDU session. .
  • the method specifically includes: receiving a protocol data unit session modification command message, and the protocol data unit session modification command message
  • the message includes the mapped evolved packet system bearer context; when the mapped evolved packet system bearer context determines that there is an error, a protocol data unit session modification request message is sent, and the mapped evolved packet system bearer context is deleted, and the protocol
  • the data unit session modification request message includes the cause value corresponding to the error.
  • the terminal device can enable the network device to determine the cause of the error by sending the cause value to the network device.
  • the error includes one or more of the following: an operational semantic error in the mapping evolution packet system bearer context; an operational semantic error in the service flow template included in the mapping evolution packet system bearer context;
  • the service flow template operation syntax included in the mapping evolved packet system bearer context is wrong; the packet filter semantics included in the mapping evolved packet system bearer context are wrong; the packet filter syntax included in the mapping evolved packet system bearer context is wrong.
  • the method further includes: receiving a protocol data unit session establishment accept message, where the protocol data unit session establishment accept message includes a mapped Evolved Packet System bearer context corresponding to the second protocol data unit session.
  • the second protocol data unit session is re-established for the service, thereby maintaining continuity of data transmission of the service.
  • embodiments of the present application provide a communication device.
  • the communication device is equipped with the function of realizing the above-mentioned first aspect.
  • the communication device includes a module or unit or means for executing the steps involved in the above-mentioned first aspect.
  • the functions, units or means can be implemented by software, or by hardware, or by hardware executing corresponding software.
  • the communication device includes a processing unit and a communication unit, where the communication unit can be used to send and receive signals to implement communication between the communication device and other devices; the processing unit can be used to perform the communication Some internal operations of the device.
  • the communication device includes a processor and may also include a transceiver, the transceiver is used to send and receive signals, and the processor executes program instructions to complete any possible design in the first aspect or Methods in the implementation.
  • the communication device may further include one or more memories, the memories being used to process Coupled with a memory, the memory may store the necessary computer programs or instructions to implement the functions involved in the first aspect.
  • the processor can execute the computer program or instructions stored in the memory. When the computer program or instructions are executed, the communication device implements the method in any possible design or implementation manner in the above-mentioned first aspect.
  • the communication device includes a processor, and the processor can be coupled to a memory.
  • the memory may store necessary computer programs or instructions to implement the functions involved in the first aspect.
  • the processor can execute the computer program or instructions stored in the memory. When the computer program or instructions are executed, the communication device implements the method in any possible design or implementation manner in the above-mentioned first aspect.
  • the communication device includes a processor and an interface circuit, wherein the processor is configured to communicate with other devices through the interface circuit and perform any of the possible designs or implementations in the first aspect. method.
  • the processor can be implemented by hardware or software.
  • the processor can be a logic circuit, an integrated circuit, etc.; when implemented by software, the processor can be implemented by software.
  • the processor may be a general-purpose processor implemented by reading software code stored in memory.
  • the above processors may be one or more, and the memories may be one or more.
  • the memory can be integrated with the processor, or the memory can be provided separately from the processor. During the specific implementation process, the memory and the processor can be integrated on the same chip, or they can be respectively provided on different chips. The embodiments of this application do not limit the type of memory and the arrangement method of the memory and the processor.
  • a communication device including: an interface circuit and a processing circuit.
  • Interface circuits may include input circuits and output circuits.
  • the processing circuit is configured to receive signals through the input circuit and transmit signals through the output circuit, so that the method in the first aspect and any possible implementation manner of the first aspect is implemented.
  • the communication device can be a chip
  • the input circuit can be an input pin
  • the output circuit can be an output pin
  • the processing circuit can be a transistor, a gate circuit, a flip-flop, and various logic circuits.
  • the input signal received by the input circuit may be received and input by, for example, but not limited to, the receiver, and the signal output by the output circuit may be, for example, but not limited to, output to and transmitted by the transmitter, and the input circuit and the output A circuit may be the same circuit that functions as an input circuit and an output circuit at different times.
  • the embodiments of this application do not limit the specific implementation methods of the processor and various circuits.
  • the communication device may be a wireless communication device, that is, a computer device that supports wireless communication functions.
  • the wireless communication device may be a terminal device such as a smartphone, or a wireless access network device such as a base station.
  • System on chip can also be called system on chip (SoC), or simply SoC chip.
  • Communication chips may include baseband processing chips and radio frequency processing chips. Baseband processing chips are sometimes also called modems or baseband chips. Radio frequency processing chips are sometimes also called radio frequency transceivers (transceivers) or radio frequency chips.
  • some or all of the communication chips can be integrated inside the SoC chip.
  • the baseband processing chip is integrated into the SoC chip, and the radio frequency processing chip is not integrated with the SoC chip.
  • the interface circuit may be a radio frequency processing chip in the wireless communication device, and the processing circuit may be a baseband processing chip in the wireless communication device.
  • the communication device may be a part of a wireless communication device, such as an integrated circuit product such as a system chip or a communication chip.
  • the interface circuit may be an input/output interface, interface circuit, output circuit, input circuit, pin or related circuit on the chip or chip system, etc.
  • a processor may also be embodied as a processing circuit or logic circuit.
  • a fourth aspect provides a computer-readable storage medium for storing a computer program, the computer program including instructions for executing the method in the first aspect or any possible implementation of the first aspect.
  • a computer program product includes: computer program code, When the computer program code is run on the computer, the computer is caused to perform the method in the above first aspect or any possible implementation manner of the first aspect.
  • the present application provides a chip.
  • the chip includes a processor.
  • the processor is coupled to a memory and is used to read and execute a software program stored in the memory to implement the above first aspect or the first aspect. any possible design approach.
  • Figure 1 is a schematic diagram of a network architecture suitable for embodiments of this application.
  • Figure 2 is a schematic flowchart of a session establishment method provided by an embodiment of the present application.
  • FIG. 3 is a schematic diagram of session establishment provided by an embodiment of the present application.
  • Figure 4 is a schematic structural diagram of a communication device provided by an embodiment of the present application.
  • Figure 5 is a schematic structural diagram of a communication device provided by an embodiment of the present application.
  • the communication method provided by the embodiment of this application can be applied to the fourth generation (4th generation, 4G) communication system, such as long term evolution (long term evolution, LTE), and can also be applied to the fifth generation (5th generation, 5G) communication system.
  • 4G long term evolution
  • 5th generation, 5G 5th generation
  • 5G new radio NR
  • 6G sixth generation (6th generation, 6G) communication system.
  • the terminal device involved in the embodiment of the present application may be a wireless terminal device capable of receiving network device scheduling and indication information.
  • An end device may be a device that provides voice and/or data connectivity to a user, or a handheld device with wireless connectivity capabilities, or other processing device connected to a wireless modem.
  • Terminal equipment is also called user equipment (UE), mobile station (MS), mobile terminal (MT), etc.
  • An end device is a device that includes wireless communication capabilities (providing voice/data connectivity to the user).
  • handheld devices with wireless connection functions or vehicle-mounted devices.
  • some examples of terminal devices are: mobile phones, tablets, laptops, PDAs, mobile internet devices (MID), wearable devices, virtual reality (VR) devices, augmented reality devices Augmented reality (AR) equipment, wireless terminals in industrial control, wireless terminals in the Internet of Vehicles, wireless terminals in self-driving, and wireless terminals in remote medical surgery , wireless terminals in smart grid, wireless terminals in transportation safety, wireless terminals in smart city, or wireless terminals in smart home, etc.
  • wireless terminals in the Internet of Vehicles can be vehicle-mounted equipment, vehicle equipment, vehicle-mounted modules, vehicles, etc.
  • Wireless terminals in industrial control can be cameras, robots, etc.
  • Wireless terminals in smart homes can be TVs, air conditioners, sweepers, speakers, set-top boxes, etc.
  • the network devices involved in the embodiments of this application may be devices in a wireless network.
  • the network device may be a device deployed in a wireless access network to provide wireless communication functions for terminal devices.
  • network equipment can be used to connect terminals to A radio access network (RAN) node where a device is connected to a wireless network can also be called an access network device.
  • RAN radio access network
  • Network equipment includes but is not limited to: evolved Node B (eNB), radio network controller (RNC), Node B (Node B, NB), base station controller (BSC) , base transceiver station (BTS), home base station (e.g., home evolved NodeB, or home Node B, HNB), baseband unit (BBU), wireless fidelity (WIFI) system Access point (AP), wireless relay node, wireless backhaul node, transmission point (TP) or transmission and reception point (TRP), etc., can also be used in 5G mobile communication systems network equipment.
  • eNB evolved Node B
  • RNC radio network controller
  • Node B Node B
  • BSC base station controller
  • BTS base transceiver station
  • BTS home base station
  • BBU baseband unit
  • WIFI wireless fidelity
  • AP wireless relay node
  • TP transmission point
  • TRP transmission and reception point
  • next generation base station next generation NodeB, gNB
  • transmission reception point TRP
  • TP transmission reception point
  • the network device may also be a network node that constitutes a gNB or transmission point.
  • BBU BBU, or distributed unit (DU), etc.
  • gNB may include centralized units (CUs) and DUs.
  • the gNB may also include an active antenna unit (AAU).
  • CU implements some functions of gNB
  • DU implements some functions of gNB.
  • the CU is responsible for processing non-real-time protocols and services, implementing radio resource control (RRC), and packet data convergence protocol (PDCP) layer functions.
  • RRC radio resource control
  • PDCP packet data convergence protocol
  • DU is responsible for processing physical layer protocols and real-time services, and implementing the functions of the radio link control (RLC) layer, MAC layer and physical (physical, PHY) layer.
  • RLC radio link control
  • MAC MAC layer
  • PHY physical (physical, PHY) layer.
  • AAU implements some physical layer processing functions, radio frequency processing and active antenna related functions.
  • the network device may be a device including one or more of a CU node, a DU node, and an AAU node.
  • the CU can be divided into network equipment in the RAN, or the CU can be divided into network equipment in the core network (core network, CN), which is not limited in this application.
  • FIG. 1 shows a schematic diagram of a network architecture suitable for embodiments of this application.
  • terminal equipment can support LTE systems and NR systems.
  • LTE systems and NR systems the network transmits data in the form of Internet protocol (IP) packets and provides IP connections to terminal devices.
  • IP Internet protocol
  • the terminal device can initiate a PDU session establishment request to the network side, and the network side establishes a PDU session for the terminal device's service according to the request of the terminal device. After the PDU session is successfully established, data can be transmitted between the terminal device and the network side through the PDU session, where one PDU session includes one or more QoS flows.
  • QoS flow is the smallest granularity used for QoS management, which can achieve more flexible QoS control.
  • One QoS flow corresponds to one QoS flow identifier.
  • the terminal device can initiate an EPS bearer establishment request to the network side, and the network side establishes an EPS bearer for the terminal device's service according to the terminal device's request.
  • the EPS bearer is successfully established, data can be transmitted between the terminal device and the network side through the EPS bearer.
  • One EPS bearer corresponds to an EPS bearer identity (EBI).
  • EBI EPS bearer identity
  • a QoS flow in a PDU session can be associated with a mapped EPS bearer context.
  • the terminal device If the terminal device establishes a PDU session in the NR system and moves to the LTE system while in the connected state, the handover process will be triggered. If there is an N26 interface between the NR system and the LTE system, then when the terminal device switches from the NR system to the LTE system, the terminal device can switch the services transmitted through the PDU session in the NR system to the service associated with the PDU session according to the mapping EPS bearer context. Mapping transmission in EPS bearers to ensure smooth switching of services replacement to ensure business continuity.
  • the mapped EPS bearer context may include the following information: EPS bearer identity (EBI); the length of the mapped EPS bearer context; the operation code of the EPS bearer; the number of EPS parameters; the EPS parameter list, etc. This application is not limited to the specific content of mapping the EPS bearer context. For example, it may also include a traffic flow template (TFT), and one TFT may include one or more packet filters.
  • TFT traffic flow template
  • the PDU session established by the NR system for the terminal device includes two QoS flows (QoS flow 1 and QoS flow 2 respectively). Both QoS flow 1 and QoS flow 2 are the same as the EBI.
  • EBI 5 as an example. The value of EBI can be other values.
  • the terminal equipment performs inter-system transformation, for example, when switching from the NR system to the LTE system, both QoS flow 1 and QoS flow 2 are mapped to the EPS bearer with an EBI of 5.
  • the terminal device For a QoS flow in a PDU session, if the mapped EPS bearer context associated with the QoS flow is deleted or invalidated, the terminal device will not be able to perform normal bearer mapping after switching between different systems, resulting in service data transmission failure, etc. question.
  • the terminal device under the NR system, if the terminal device only has a PDU session corresponding to the IP multimedia subsystem (IMS) of a single voice call service, if the terminal device deletes the mapped EPS bearer context of the PDU session corresponding to the IMS Afterwards, the terminal device initiates a voice call service under the NR system, and the network side configures the terminal device to switch to the LTE system to perform an EPS fallback (FB) call. Since the current PDU session corresponding to IMS no longer has a corresponding mapped EPS bearer context, the terminal device Then the attach process will be initiated, which will cause the voice call service to fail.
  • IMS IP multimedia subsystem
  • the terminal device under the NR system, if the terminal device has a PDU session corresponding to the IMS of the voice call service and a PDU session corresponding to the data service, if the terminal device deletes the mapped EPS bearer context of the PDU session corresponding to the data service, the terminal When a device initiates a data service under the NR system and the terminal device switches to the LTE system, since the current data session no longer has a corresponding mapped EPS bearer context, the data service of the terminal device will be in a release and interrupted state for a period of time, resulting in service delays. becomes longer, resulting in poor user experience.
  • this application provides a method that can solve the above problems, which will be described in detail later.
  • the plurality involved in the embodiments of this application refers to two or more than two.
  • “And/or” describes the relationship between related objects, indicating that there can be three relationships.
  • a and/or B can mean: A exists alone, A and B exist simultaneously, and B exists alone.
  • the character "/” generally indicates that the related objects are in an "or” relationship.
  • words such as “first” and “second” are only used for the purpose of distinguishing the description, and cannot be understood as indicating or implying relative importance, nor can they be understood as indicating. Or suggestive order.
  • FIG. 2 it is a schematic flow chart of a session establishment method provided by an embodiment of the present application.
  • the method is explained by taking the interaction between a terminal device and a network device as an example.
  • the method includes:
  • S201 The network device sends a PDU session modification command message to the terminal device; accordingly, the terminal device receives the PDU session modification command message from the network device.
  • the PDU session modification command message is used to modify the first PDU session.
  • the PDU session modification command message includes information such as mapping EPS bearer context and QoS flow description of the QoS flow included in the first PDU session.
  • the EPS bearer context may include one or more TFTs, and one TFT may include one or more packet filters.
  • S202 The terminal device checks whether there is an error in the mapped EPS bearer context.
  • the terminal device can check whether there is one or more of the following errors in the mapped EPS bearer context:
  • Mapping EPS bearer context includes syntactical errors in TFT operations
  • Mapping EPS bearer context includes syntactical errors in packet filters.
  • mapping EPS bearer context operations For example, in case 1 or 2, there is a semantic error in mapping EPS bearer context operations:
  • Case 1 The operation code in the mapped EPS bearer context is: modify the existing EPS bearer, and there is no existing mapped EPS bearer context associated with the PDU session being modified with the same EPS bearer identifier.
  • Case 2 The operation code in the mapped EPS bearer context is: create a new EPS bearer, or modify an existing EPS bearer, and the generated mapped EPS bearer context has invalid or missing required parameters (for example, mapped EPS QoS parameters or Service flow template of proprietary EPS bearer context).
  • TFT operation indicated by the PDU session modification command message is: "Delete TFT” or "No TFT operation", and there is a non-empty packet filter list in the TFT.
  • Case six when there are other types of syntax errors in the encoding of the packet filter, such as the use of reserved values for the packet filter component identifier.
  • the terminal device if the selected PDU session type is "Unstructured", the terminal device supports inter-system switching from N1 mode to S1 mode, and the terminal device does not support setting to "Non-IP ( non-IP)" PDN type to establish a PDN connection, and the parameter list field of one or more authorized QoS flow descriptions received in the authorized QoS flow description resource element of the PDU session modification command message contains EBI, then the terminal device shall Locally remove the EBI from the parameter list field of the one or more authorized QoS flow descriptions. In this case, it may be determined that there is an error in mapping the EPS bearer context.
  • the terminal device supports inter-system switching from N1 mode to S1 mode, and the terminal device does not support setting to "non-IP (non-IP) mode" in S1 mode.
  • -IP)" PDN type to establish a PDN connection
  • the end device, the network, or both do not support the Ethernet PDN type in S1 mode, and one or more of the authorization QoS flow description resource elements received in the PDU session modification command message
  • the parameter list field of an authorized QoS flow description contains EBI, and the terminal device shall locally remove the EBI from the parameter list field of the one or more authorized QoS flow descriptions. In this case, it may be determined that there is an error in mapping the EPS bearer context.
  • the terminal device can also perform S203:
  • the terminal device sends a PDU session modification request message to the network device to delete the mapped EPS bearer context.
  • the PDU session modification request message includes the cause value corresponding to the error; accordingly, the network device receives the PDU session modification request message from the terminal device.
  • the PDU session modification request message includes a reason value of #85.
  • the reason value included in the PDU session modification request message is #41.
  • the reason value included in the PDU session modification request message is #42.
  • the PDU Session Modification Request message includes a reason value of #44.
  • the PDU Session Modification Request message includes a reason value of #45.
  • the reason value included in the PDU session modification request message is #85.
  • Each error may also correspond to other cause values, which can be determined based on the evolution of the protocol.
  • the PDU session release request message is used to request the release of the first PDU session.
  • the first PDU session does not have a corresponding mapped EPS bearer context, which may mean that the first PDU session does not exist or lacks a corresponding mapped EPS bearer context.
  • the terminal equipment when the terminal equipment performs inter-system conversion, such as switching from the NR system to the LTE system, the terminal equipment cannot determine the EPS bearer corresponding to the first PDU session in the LTE system, and data transmission will occur for the service corresponding to the first PDU session. Discontinuity or failure.
  • the terminal device may delete the mapping corresponding to the first PDU session.
  • EPS bearer context then the terminal device may determine that the first PDU session does not have a corresponding mapped EPS bearer context.
  • the above is just an example.
  • the first PDU session does not have a corresponding mapped EPS bearer.
  • the terminal device in order to reduce the impact of releasing services corresponding to the first PDU session, can release the first PDU session in the following two scenarios.
  • Scenario 1 When the terminal device is in the RRC idle state (referred to as idle state) or RRC inactive state (referred to as inactive state), it sends a PDU session release request message to the network device.
  • RRC idle state referred to as idle state
  • RRC inactive state referred to as inactive state
  • the terminal device Since the terminal device is in the idle state or inactive state, the terminal device does not need to transmit service data through the first PDU session. Therefore, the terminal device releases the first PDU session at this time, which will not affect the services corresponding to the first PDU session.
  • Scenario 2 If the terminal device does not transmit a service data packet through the first PDU session within a preset time period, the terminal device can send a PDU session release request message to the network device.
  • the specific value of the preset duration can be determined according to actual conditions, and is not limited in this application.
  • the preset duration can be configured by the network device, independently determined by the terminal device, or agreed upon by the protocol.
  • the terminal device Since the terminal device has not transmitted service data through the first PDU session within the preset time period, it can be considered that there is currently no need to transmit service data. The terminal device releases the first PDU session at this time, which will not affect the services corresponding to the first PDU session. .
  • the network device sends a PDU session release command message to the terminal device; accordingly, the terminal device receives the PDU session release command message from the network device, and the PDU session release command message is used to instruct the release of the first PDU session.
  • the PDU session release command message may be a response to the PDU session release request message, and the network device may send the PDU session release command message to the terminal device when releasing the first PDU session is completed.
  • the terminal device can also re-establish the PDU session for the service, that is, perform the following process:
  • the terminal device sends a PDU session establishment request message to the network device; accordingly, the network device receives the PDU session establishment request message from the terminal device.
  • the PDU session establishment request message is used to request the establishment of a second PDU session; the first PDU session and the second PDU session correspond to the same service.
  • the network device may send information such as the mapped EPS bearer context corresponding to the second PDU session to the terminal device.
  • information such as the mapped EPS bearer context corresponding to the second PDU session to the terminal device.
  • the network device sends a PDU session establishment accept message to the terminal device; accordingly, the terminal device receives the PDU session establishment accept message from the network device.
  • the PDU session establishment acceptance message includes information such as the mapped EPS bearer context corresponding to the second PDU session, and the QoS flow description of the QoS flow included in the second PDU session. That is to say, the established second PDU session has a corresponding mapped EPS bearer context and can be used for inter-system conversion.
  • the terminal device when the terminal device determines that the first PDU session does not have a corresponding mapped EPS bearer context, it can actively deactivate the first PDU session, and then re-establish a new second PDU session for the services corresponding to the first PDU session.
  • PDU session can ensure the reliability and continuity of services during terminal equipment switching between different systems (such as switching from NR system to LTE system), and can avoid call failures, service interruptions, discontinuities, etc.
  • the terminal device if the terminal device has a PDU session corresponding to the IMS service used for voice calls, if the network device modifies the PDU session corresponding to the IMS service through the PDU session modification command message, When the terminal device checks the mapped EPS bearer context of the PDU session corresponding to the IMS service and determines that there is an error, and thereby deletes the mapped EPS bearer context of the PDU session corresponding to the IMS service, the terminal device can re-establish the IMS service correspondence through the method provided by the embodiment of the present application.
  • the PDU session corresponding to the re-established IMS service has a corresponding mapped EPS bearer.
  • the terminal device when the terminal device has a PDU session corresponding to the IMS service and a PDU session corresponding to the non-IMS service, if there is no mapping bearer in the NR system, through the method provided by the embodiment of this application, the terminal device can re- A PDU session corresponding to the non-IMS service is established, and the re-established PDU session has a corresponding mapped EPS bearer.
  • the terminal device switches from the NR system to the LTE system, the service data can be transmitted without interruption, thereby reducing the switching delay, improving service reliability, and improving user experience.
  • FIG. 3 it is a schematic flow chart of a session establishment method provided by an embodiment of the present application.
  • S301 The network device sends a PDU session modification command message to the terminal device.
  • the PDU session modification command message is used to modify the first PDU session.
  • the PDU session modification command message includes information such as mapping EPS bearer context.
  • the terminal device sends a PDU session modification completion message to the network device.
  • This PDU session modification command completion message is a response message to the above message.
  • the terminal device determines that there is at least one error described in S201 in mapping the EPS bearer context, the following process is executed:
  • the terminal device sends a PDU session modification request message to the network device to delete the mapped EPS bearer context.
  • the PDU session modification request message includes a cause value corresponding to the error.
  • S304 The terminal device sends a PDU session release request message to the network device.
  • the PDU session release request message is used to request the release of the first PDU session.
  • S305 The network device sends a PDU session release command message to the terminal device.
  • the protocol data unit session release command message is used to indicate the completion of releasing the first PDU session, that is, the message indicates that the network device has deleted the first PDU session related information.
  • S306 The terminal device sends a PDU session release completion message to the network device.
  • This message is a message in response to the PDU session release command message.
  • the terminal device can send a PDU session release completion message after locally deleting the first PDU session related information.
  • the terminal device can also trigger the re-establishment of a PDU session for the service corresponding to the first PDU session, thereby ensuring the continuity of service data transmission corresponding to the first PDU session. Specifically, the following steps may be included:
  • the terminal device sends a PDU session establishment request message to the network device.
  • This message is used to request the establishment of a second PDU session for the service corresponding to the first PDU session.
  • S308 The network device sends a PDU session establishment acceptance message to the terminal device.
  • This message includes information such as the mapped EPS bearer context corresponding to the second PDU session.
  • the terminal device determines that the first PDU session corresponding to the service does not have a corresponding mapped EPS bearer context, it releases the first PDU session and establishes the second PDU session corresponding to the service.
  • the established second PDU session will There is a corresponding mapped EPS bearer context, which ensures continuous data transmission of the service when the terminal device performs inter-system conversion.
  • each step in the above-mentioned FIG. 2 to FIG. 3 is only an exemplary description and is not strictly limited.
  • the size of the serial numbers of the above-mentioned processes does not mean the order of execution.
  • the execution order of each process should be determined by its functions and internal logic, and should not constitute any limitation on the implementation process of the embodiment of the present application.
  • embodiments of the present application also provide corresponding devices, and the devices include modules for executing corresponding modules in each of the above method embodiments.
  • the module can be software, hardware, or a combination of software and hardware. It can be understood that the technical features described in the above method embodiments are also applicable to the following device embodiments.
  • FIG. 4 is a schematic structural diagram of a communication device provided by an embodiment of the present application.
  • the communication device 400 includes a communication unit 420 and a processing unit 410.
  • the communication unit 420 can implement corresponding communication functions, and the communication unit 420 can also be a communication interface or a communication unit.
  • the processing unit 410 can implement corresponding processing functions, such as processing instructions and/or data.
  • the communication device 400 may also include a storage unit, which may be used to store instructions and/or data, and the processing unit 410 may read the instructions and/or data in the storage unit, so that the device implements The aforementioned method embodiments.
  • the communication device 400 can be used to perform the actions performed by the terminal device in the above method embodiment.
  • the communication unit 420 in the communication device 400 is used to perform operations related to the sending and receiving of the terminal device in the above method embodiment.
  • the processing unit 410 is configured to perform operations related to processing of the terminal device in the above method embodiment.
  • the communication device 400 is used to perform the actions performed by the terminal device in the above method embodiment:
  • a processing unit configured to send a protocol data unit session release request message through the communication unit when the first protocol data unit session does not have a corresponding mapped evolved packet system bearer context, and the protocol data unit session release request message is used to request release The first protocol data unit session;
  • a communication unit configured to receive a protocol data unit session release command message, the protocol data unit session release command message being used to instruct release of the first protocol data unit session; and to send a protocol data unit session establishment request message, the protocol data unit session release command message being The session establishment request message is used to request the establishment of a second protocol data unit session; the first protocol data unit session and the second protocol data unit session correspond to the same service.
  • the communication device before the communication unit sends the protocol data unit session release request message, the communication device is in an idle state or an inactive state.
  • the communication unit is also used to:
  • Protocol data unit session modification command message including the mapped evolved packet system bearer context
  • the processing unit is also configured to delete the mapped Evolved Packet System bearer context.
  • the error includes one or more of the following:
  • the mapped evolved packet system carries context operation semantic errors
  • the mapping Evolved Packet System bearer context includes a packet filter syntax error.
  • the communication unit is also used to:
  • a protocol data unit session establishment accept message is received, where the protocol data unit session establishment accept message includes a mapped Evolved Packet System bearer context corresponding to the second protocol data unit session.
  • the processing unit 410 and the communication unit 420 can also perform other functions.
  • the processing unit 410 and the communication unit 420 can also perform other functions.
  • Figure 5 shows a communication device provided by an embodiment of the present application.
  • the communication device shown in Figure 5 can be an implementation of a hardware circuit of the communication device shown in Figure 4.
  • the communication device can be adapted to the flow chart shown above to perform the functions of the terminal device in the above method embodiment.
  • FIG. 5 shows only the main components of the communication device.
  • the communication device 500 includes a processor 510 and an interface circuit 520 .
  • the processor 510 and the interface circuit 520 are coupled to each other.
  • the interface circuit 520 can be a transceiver, a pin, or an input-output interface.
  • the communication device 500 may also include a memory 530 for storing instructions executed by the processor 510 or input data required for the processor 510 to run the instructions or data generated after the processor 510 executes the instructions.
  • some or all of memory 530 may be located in processor 510.
  • the processor 510 is used to implement the functions of the above-mentioned processing unit 410
  • the interface circuit 520 is used to implement the functions of the above-mentioned communication unit 420.
  • processor in the embodiment of the present application may be a central processing unit, or other general-purpose processor, digital signal processor, application-specific integrated circuit or other programmable logic device, transistor logic device, hardware component or any combination thereof.
  • a general-purpose processor can be a microprocessor or any conventional processor.
  • the memory in the embodiment of the present application may be random access memory, flash memory, read-only memory, programmable read-only memory, erasable programmable read-only memory, electrically erasable programmable read-only memory, register, hard disk, in a portable hard disk or any other form of storage media well known in the art.
  • the processor is a general-purpose processor or other programmable logic device, a discrete gate or transistor logic device, or a discrete hardware component
  • the memory storage module
  • memories described herein are intended to include, but are not limited to, these and any other suitable types of memories.
  • embodiments of the present application may be provided as methods, systems, or computer program products. Accordingly, the present application may take the form of an entirely hardware embodiment, an entirely software embodiment, or an embodiment that combines software and hardware aspects. Furthermore, the present application may take the form of a computer program product embodied on one or more computer-usable storage media (including, but not limited to, disk storage, optical storage, etc.) having computer-usable program code embodied therein.
  • a computer-usable storage media including, but not limited to, disk storage, optical storage, etc.
  • These computer program instructions may also be stored in a computer-readable memory that causes a computer or other programmable data processing apparatus to operate in a particular manner, such that the instructions stored in the computer-readable memory produce an article of manufacture including the instruction means, the instructions
  • the device implements the functions specified in a process or processes of the flowchart and/or a block or blocks of the block diagram.

Abstract

本申请提供一种会话建立方法及装置，可以应用于通信领域，其中方法包括：在第一PDU会话没有对应的映射演进分组系统承载上下文的情况下，发送PDU会话释放请求消息；接收PDU会话释放命令消息；发送PDU会话建立请求消息，PDU会话建立请求消息用于请求建立第二PDU会话；第一PDU会话与第二PDU会话对应同一个业务。通过该方法，终端设备确定第一PDU会话没有对应的映射EPS承载上下文时，主动将第一PDU会话去激活，再重新建立新的第二PDU会话，从而可以保证终端设备在进行异系统切换过程中，业务的可靠性与连续性，并且可避免通话失败、业务中断、不连续等情况。

Description

一种会话建立方法及装置
相关申请的交叉引用
本申请要求在2022年04月29日提交中国专利局、申请号为202210473226.8、申请名称为“一种会话建立方法及装置”的中国专利申请的优先权，其全部内容通过引用结合在本申请中。
技术领域
本申请涉及通信技术领域，尤其涉及一种会话建立方法及装置。
背景技术
由第三代伙伴计划(the 3rd generation partnership project，3GPP)制定的无线通信系统已经发展到第五代(the 5th generation，5G)，即新无线(new radio，NR)系统。NR系统中的协议数据单元(protocol data unit，PDU)会话和4G长期演进(long term evolution，LTE)系统中的承载(bearer)的作用类似，都是为业务传输数据的通道。但NR系统中为了更加精细化业务实现，其基本的业务通道细化到以服务质量(quality of service，QoS)流(flow)为基本业务传输单位，一个PDU会话可以包括多个QoS流，QoS流是一个PDU会话对QoS的最小区分粒度，不同的QoS流适配着不同的QoS。
目前，终端设备在NR系统中驻留后，会携带LTE系统中承载的相关映射信息，来保证异系统间业务的连续性。具体的，当PDU会话支持与演进分组系统(evolved packet system，EPS)互通时，PDU会话中的一个QoS流可以对应一个映射EPS承载上下文(mapped EPS bearer context)。对于一个PDU会话中的QoS流，可能会由于某种原因删除了该QoS流对应的映射EPS承载上下文，那么终端设备进行异系统之间的切换后，无法进行正常的承载映射，会导致业务失败等问题。
发明内容
本申请提供一种会话建立方法及装置，用以解决PDU会话没有对应的映射4G承载上下文的情况下，终端设备进行异系统之间的切换时，会出现业务失败或不连续的问题。
第一方面，本申请提供一种会话建立方法，该方法可以用于终端设备侧的功能，本申请实施例不限该方法的具体执行主体。以该方法应用于终端设备为例，在该方法中，在第一协议数据单元会话没有对应的映射演进分组系统承载上下文的情况下，终端设备发送协议数据单元会话释放请求消息，所述协议数据单元会话释放请求消息用于请求释放所述第一协议数据单元会话；接收协议数据单元会话释放命令消息，所述协议数据单元会话释放命令消息用于指示释放所述第一协议数据单元会话；发送协议数据单元会话建立请求消息，所述协议数据单元会话建立请求消息用于请求建立第二协议数据单元会话；其中，所述第一协议数据单元会话与所述第二协议数据单元会话对应同一个业务。
通过本申请实施例提供的方法，终端设备确定第一PDU会话没有对应的映射EPS承载上下文时，可以主动将第一PDU会话去激活，再重新为第一PDU会话对应的业务建立新的第二PDU会话，从而可以保证终端设备在进行异系统切换(例如从NR系统切换到 LTE系统)过程中，业务的可靠性与连续性，并且可避免通话失败、业务中断、不连续等情况，提高系统的稳定性。
在一种可能的设计中，所述发送协议数据单元会话释放请求消息之前，所述终端设备处于空闲态或者非激活态。
由于终端设备处于空闲态或者非激活态，终端设备不需要通过第一PDU会话传输业务数据，因此终端设备此时释放第一PDU会话，不会对第一PDU会话对应的业务造成影响。
在一种可能的设计中，所述发送协议数据单元会话释放请求消息之前，所述方法还包括：在预设时长内没有通过所述第一协议数据单元会话传输所述业务的数据包。
由于终端设备在预设时长内没有通过第一PDU会话传输业务数据，因此可以认为当前不需要传输业务数据，终端设备此时释放第一PDU会话，不会对第一PDU会话对应的业务造成影响。
在一种可能的设计中，所述在第一协议数据单元会话没有对应的映射演进分组系统承载上下文的情况下，具体包括：接收协议数据单元会话修改命令消息，所述协议数据单元会话修改命令消息包括所述映射演进分组系统承载上下文；在所述映射演进分组系统承载上下文确定存在错误的情况下，发送协议数据单元会话修改请求消息，并删除所述映射演进分组系统承载上下文，所述协议数据单元会话修改请求消息包括所述错误对应的原因值。
由于映射演进分组系统承载上下文存在错误，所以删除该映射演进分组系统承载上下文，可以避免根据错误的映射演进分组系统承载上下文进行业务传输。进一步的，终端设备通过向网络设备发送原因值，可以使得网络设备确定错误的原因。
在一种可能的设计中，所述错误包括以下一项或多项：所述映射演进分组系统承载上下文操作语义错误；所述映射演进分组系统承载上下文包括的业务流模板操作语义错误；
所述映射演进分组系统承载上下文包括的业务流模板操作语法错误；所述映射演进分组系统承载上下文包括的包过滤器语义错误；所述映射演进分组系统承载上下文包括的包过滤器语法错误。
在一种可能的设计中，所述方法还包括：接收协议数据单元会话建立接受消息，所述协议数据单元会话建立接受消息包括所述第二协议数据单元会话对应的映射演进分组系统承载上下文。
通过上述方法，完成重新为业务建立第二协议数据单元会话，从而使得业务的数据传输保持连续性。
第二方面，本申请实施例提供一种通信装置，所述通信装置具备实现上述第一方面的功能，比如，所述通信装置包括执行上述第一方面所涉及的步骤的模块或单元或手段，所述功能或单元或手段可以通过软件实现，或者通过硬件实现，也可以通过硬件执行相应的软件实现。
在一种可能的设计中，所述通信装置包括处理单元、通信单元，其中，通信单元可以用于收发信号，以实现该通信装置和其它装置之间的通信；处理单元可以用于执行该通信装置的一些内部操作。
在一种可能的设计中，所述通信装置包括处理器，还可以包括收发器，所述收发器用于收发信号，所述处理器执行程序指令，以完成上述第一方面中任意可能的设计或实现方式中的方法。其中，所述通信装置还可以包括一个或多个存储器，所述存储器用于与处理 器耦合，所述存储器可以保存实现上述第一方面涉及的功能的必要计算机程序或指令。所述处理器可执行所述存储器存储的计算机程序或指令，当所述计算机程序或指令被执行时，使得所述通信装置实现上述第一方面中任意可能的设计或实现方式中的方法。
在一种可能的设计中，所述通信装置包括处理器，处理器可以用于与存储器耦合。所述存储器可以保存实现上述第一方面涉及的功能的必要计算机程序或指令。所述处理器可执行所述存储器存储的计算机程序或指令，当所述计算机程序或指令被执行时，使得所述通信装置实现上述第一方面中任意可能的设计或实现方式中的方法。
在一种可能的设计中，所述通信装置包括处理器和接口电路，其中，处理器用于通过所述接口电路与其它装置通信，并执行上述第一方面中任意可能的设计或实现方式中的方法。
可以理解地，上述第二方面中，处理器可以通过硬件来实现也可以通过软件来实现，当通过硬件实现时，该处理器可以是逻辑电路、集成电路等；当通过软件来实现时，该处理器可以是一个通用处理器，通过读取存储器中存储的软件代码来实现。此外，以上处理器可以为一个或多个，存储器可以为一个或多个。存储器可以与处理器集成在一起，或者存储器与处理器分离设置。在具体实现过程中，存储器可以与处理器集成在同一块芯片上，也可以分别设置在不同的芯片上，本申请实施例对存储器的类型以及存储器与处理器的设置方式不做限定。
第三方面，提供了一种通信装置，包括：接口电路和处理电路。接口电路可以包括输入电路和输出电路。处理电路用于通过输入电路接收信号，并通过输出电路发射信号，使得第一方面以及第一方面中任一种可能实现方式中的方法被实现。
在具体实现过程中，通信装置可以为芯片，输入电路可以为输入管脚，输出电路可以为输出管脚，处理电路可以为晶体管、门电路、触发器和各种逻辑电路等。输入电路所接收的输入的信号可以是由例如但不限于接收器接收并输入的，输出电路所输出的信号可以是例如但不限于输出给发射器并由发射器发射的，且输入电路和输出电路可以是同一电路，该电路在不同的时刻分别用作输入电路和输出电路。本申请实施例对处理器及各种电路的具体实现方式不做限定。
在一种实现方式中，通信装置可以是无线通信设备，即支持无线通信功能的计算机设备。具体地，无线通信设备可以是诸如智能手机这样的终端设备，也可以是诸如基站这样的无线接入网设备。系统芯片也可称为片上系统(system on chip，SoC)，或简称为SoC芯片。通信芯片可包括基带处理芯片和射频处理芯片。基带处理芯片有时也被称为调制解调器(modem)或基带芯片。射频处理芯片有时也被称为射频收发机(transceiver)或射频芯片。在物理实现中，通信芯片中的部分芯片或者全部芯片可集成在SoC芯片内部。例如，基带处理芯片集成在SoC芯片中，射频处理芯片不与SoC芯片集成。接口电路可以为无线通信设备中的射频处理芯片，处理电路可以为无线通信设备中的基带处理芯片。
在又一种实现方式中，通信装置可以是无线通信设备中的部分器件，如系统芯片或通信芯片等集成电路产品。接口电路可以为该芯片或芯片系统上的输入/输出接口、接口电路、输出电路、输入电路、管脚或相关电路等。处理器也可以体现为处理电路或逻辑电路。
第四方面，提供了一种计算机可读存储介质，用于存储计算机程序，该计算机程序包括用于执行第一方面或第一方面中任一种可能实现方式中的方法的指令。
第五方面，提供了一种计算机程序产品，所述计算机程序产品包括：计算机程序代码， 当所述计算机程序代码在计算机上运行时，使得计算机执行上述第一方面或第一方面中任一种可能实现方式中的方法。
第六方面，本申请提供一种芯片，所述芯片包括处理器，所述处理器与存储器耦合，用于读取并执行所述存储器中存储的软件程序，以实现上述第一方面或第一方面中任一种可能的设计中的方法。
本申请的这些方面或其它方面在以下实施例的描述中会更加简明易懂。
附图说明
图1为适用于本申请实施例的网络架构示意图；
图2为本申请实施例提供的一种会话建立方法流程示意图；
图3为本申请实施例提供的一种会话建立示意图；
图4为本申请实施例提供的一种通信装置结构示意图；
图5为本申请实施例提供的一种通信装置结构示意图。
具体实施方式
下面结合说明书附图对本申请实施例做详细描述。
本申请实施例提供的通信方法可以应用于第四代(4th generation，4G)通信系统，例如长期演进(long term evolution，LTE)，也可以应用于第五代(5th generation，5G)通信系统，例如5G新空口(new radio，NR)，或应用于未来的各种通信系统，例如，第六代(6th generation，6G)通信系统。
本申请实施例提供的方法和装置是基于同一或相似技术构思的，由于方法及装置解决问题的原理相似，因此装置与方法的实施可以相互参见，重复之处不再赘述。
本申请实施例中涉及的终端设备,可以是能够接收网络设备调度和指示信息的无线终端设备。终端设备可以是指向用户提供语音和/或数据连通性的设备，或具有无线连接功能的手持式设备、或连接到无线调制解调器的其他处理设备。
终端设备，又称之为用户设备(user equipment，UE)、移动台(mobile station，MS)、移动终端(mobile terminal，MT)等。终端设备是包括无线通信功能(向用户提供语音/数据连通性)的设备。例如，具有无线连接功能的手持式设备、或车载设备等。目前，一些终端设备的举例为：手机(mobile phone)、平板电脑、笔记本电脑、掌上电脑、移动互联网设备(mobile internet device，MID)、可穿戴设备，虚拟现实(virtual reality，VR)设备、增强现实(augmented reality，AR)设备、工业控制(industrial control)中的无线终端、车联网中的无线终端、无人驾驶(self driving)中的无线终端、远程手术(remote medical surgery)中的无线终端、智能电网(smart grid)中的无线终端、运输安全(transportation safety)中的无线终端、智慧城市(smart city)中的无线终端、或智慧家庭(smart home)中的无线终端等。例如，车联网中的无线终端可以为车载设备、整车设备、车载模块、车辆等。工业控制中的无线终端可以为摄像头、机器人等。智慧家庭中的无线终端可以为电视、空调、扫地机、音箱、机顶盒等。
本申请实施例中涉及的网络设备，可以为无线网络中的设备。例如，网络设备可以是部署在无线接入网中为终端设备提供无线通信功能的设备。例如，网络设备可以为将终端 设备接入到无线网络的无线接入网(radio access network，RAN)节点，又可以称为接入网设备。
网络设备包括但不限于：演进型节点B(evolved Node B，eNB)、无线网络控制器(radio network controller，RNC)、节点B(Node B，NB)、基站控制器(base station controller，BSC)、基站收发台(base transceiver station，BTS)、家庭基站(例如，home evolved NodeB，或home Node B，HNB)、基带单元(baseband unit，BBU)，无线保真(wireless fidelity，WIFI)系统中的接入点(access point，AP)、无线中继节点、无线回传节点、传输点(transmission point，TP)或者发送接收点(transmission and reception point，TRP)等，还可以为5G移动通信系统中的网络设备。例如，NR系统中的下一代基站(next generation NodeB，gNB)，传输接收点(transmission reception point，TRP)，TP；或者，5G移动通信系统中的基站的一个或一组(包括多个天线面板)天线面板；或者，网络设备还可以为构成gNB或传输点的网络节点。例如，BBU，或，分布式单元(distributed unit，DU)等。
在一些部署中，gNB可以包括集中式单元(centralized unit，CU)和DU。gNB还可以包括有源天线单元(active antenna unit，AAU)。CU实现gNB的部分功能，DU实现gNB的部分功能。例如，CU负责处理非实时协议和服务，实现无线资源控制(radio resource control，RRC)，分组数据汇聚层协议(packet data convergence protocol，PDCP)层的功能。DU负责处理物理层协议和实时服务，实现无线链路控制(radio link control，RLC)层、MAC层和物理(physical，PHY)层的功能。AAU实现部分物理层处理功能、射频处理及有源天线的相关功能。RRC层的信息最终会变成PHY层的信息，或者，由PHY层的信息转变而来。因此在该架构下，高层信令(如RRC层信令)也可以认为是由DU发送的，或者，由DU和AAU发送的。可以理解的是，网络设备可以为包括CU节点、DU节点、AAU节点中一个或多个的设备。此外，可以将CU划分为RAN中的网络设备，也可以将CU划分为核心网(core network，CN)中的网络设备，本申请对此不做限定。
为便于理解本申请实施例，首先以图1中示出的通信系统为例说明适用于本申请实施例的通信系统。图1示出了适用于本申请实施例的网络架构示意图。如图1所示，终端设备可以支持LTE系统和NR系统。LTE系统和NR系统中，网络是以因特网协议(internet protocol，IP)分组的形式传输数据，并向终端设备提供IP连接。
NR系统中，终端设备可以向网络侧发起PDU会话建立请求，网络侧根据终端设备的请求为终端设备的业务建立PDU会话。当PDU会话建立成功之后，终端设备和网络侧之间可以通过PDU会话进行数据传输，其中一个PDU会话包括一个或多个QoS流。在NR系统中，QoS流是用于QoS管理的最小粒度，可实现更灵活的QoS控制，一个QoS流对应一个QoS流标识。
LTE系统中，终端设备可以向网络侧发起EPS承载建立请求，网络侧根据终端设备的请求为终端设备的业务建立EPS承载。当EPS承载建立成功之后，终端设备和网络侧之间可以通过EPS承载进行数据传输，其中一个EPS承载对应一个EPS承载标识(EPS bearer identity，EBI)。NR系统中，PDU会话中的一个QoS流可以关联一个映射EPS承载上下文。
如果终端设备在NR系统中建立了PDU会话，并且在处于连接态时移动到了LTE系统，将触发切换流程。如果NR系统与LTE系统之间有N26接口，那么终端设备从NR系统切换到LTE系统时，终端设备可以根据映射EPS承载上下文将在NR系统中通过PDU会话传输的业务切换到该PDU会话关联的映射EPS承载中传输，从而保证业务的平滑切 换，保证业务的连续性。其中，映射EPS承载上下文可以包括以下信息：EPS承载标识(EPS bearer identity，EBI)；映射EPS承载上下文的长度；EPS承载的操作码(operation code)；EPS参数的数量；EPS参数列表等。映射EPS承载上下文的具体内容，本申请对此并不限定，例如还可以包括业务流模板(traffic flow template，TFT)，一个TFT可以包括一个或多个包过滤器。
举例来说，图1中，以NR系统为终端设备建立的PDU会话包括两个QoS流(分别为QoS流1和QoS流2)为例进行描述，QoS流1和QoS流2都和EBI为5的EPS承载具有映射关系，这里只是以EBI＝5为例，EBI的取值可以为其它值。当终端设备需要从NR系统中切换到LTE系统中时，会触发使用N26接口的5G到4G切换流程。终端设备进行异系统变换，例如从NR系统切换到LTE系统中时，QoS流1和QoS流2都被映射到EBI为5的EPS承载。
对于一个PDU会话中的QoS流，如果该QoS流关联的映射EPS承载上下文被删除或失效，那么终端设备进行异系统之间的切换后，无法进行正常的承载映射，会导致业务数据传输失败等问题。例如，NR系统下，终端设备只存在单条语音呼叫业务的IP多媒体子系统(IP multimedia subsystem，IMS)对应的PDU会话的情况下，如果终端设备将该IMS对应的PDU会话的映射EPS承载上下文删除之后，终端设备在NR系统下发起语音呼叫业务，网络侧配置终端设备切换至LTE系统进行EPS回落(fallback，FB)呼叫，由于当前IMS对应的PDU会话已经没有对应的映射EPS承载上下文，终端设备则会发起附着(attach)流程，会使得语音呼叫业务失败。
再例如，NR系统下，终端设备存在语音呼叫业务的IMS对应的PDU会话和数据业务对应的PDU会话的情况下，如果终端设备将该数据业务对应的PDU会话的映射EPS承载上下文删除之后，终端设备在NR系统下发起数据业务，终端设备切换至LTE系统后，由于当前数据会话已经没有对应的映射EPS承载上下文，会使得终端设备的数据业务在一段时间内处于释放中断态，导致业务时延变长，用户体验不佳。
为此，本申请提供一种方法，可以解决上述问题，后面将详细描述。
本申请实施例中涉及的多个，是指两个或两个以上。“和/或”，描述关联对象的关联关系，表示可以存在三种关系，例如，A和/或B，可以表示：单独存在A，同时存在A和B，单独存在B这三种情况。字符“/”一般表示前后关联对象是一种“或”的关系。另外，需要理解的是，在本申请的描述中，“第一”、“第二”等词汇，仅用于区分描述的目的，而不能理解为指示或暗示相对重要性，也不能理解为指示或暗示顺序。
本申请实施例描述的网络架构以及业务场景是为了更加清楚的说明本申请实施例的技术方案，并不构成对于本申请实施例提供的技术方案的限定，本领域普通技术人员可知，随着网络架构的演变和新业务场景的出现，本申请实施例提供的技术方案对于类似的技术问题，同样适用。
如图2所示，为本申请实施例提供的一种会话建立方法流程示意图，该方法以终端设备与网络设备之间的交互为例进行说明，该方法包括：
可选地，S201：网络设备向终端设备发送PDU会话修改命令(PDU session modification command)消息；相应的，终端设备接收来自网络设备的PDU会话修改命令消息。
其中，该PDU会话修改命令消息用于修改第一PDU会话，该PDU会话修改命令消息包括映射EPS承载上下文，以及第一PDU会话包括的QoS流的QoS流描述等信息。映 射EPS承载上下文可以包括一个或多个TFT，一个TFT可以包括一个或多个包过滤器。
可选地，S202：终端设备检查映射EPS承载上下文是否存在错误。
本申请实施例中，终端设备可以检查映射EPS承载上下文是否存在以下一项或多项错误：
映射EPS承载上下文操作语义错误(semantic error in the mapped EPS bearer operation)；
映射EPS承载上下文包括的业务流模板操作语义错误(semantic errors in TFT operations)；
映射EPS承载上下文包括的业务流模板操作语法错误(syntactical errors in TFT operations)；
映射EPS承载上下文包括的包过滤器语义错误(semantic errors in packet filters)；
映射EPS承载上下文包括的包过滤器语法错误(syntactical errors in packet filters)。
举例来说，在情况一或情况二下，存在映射EPS承载上下文操作语义错误：
情况一，映射EPS承载上下文中的操作码为：修改现有EPS承载，并且不存在与正在修改的PDU会话关联的具有相同EPS承载标识的现有映射EPS承载上下文。
情况二，映射EPS承载上下文中的操作码为：创建新的EPS承载，或者修改现有EPS承载，并且生成的映射EPS承载上下文具有无效或缺失的必选参数(例如，映射的EPS QoS参数或专有EPS承载上下文的业务流模板)。
以上只是示例，映射EPS承载上下文操作语义错误还可以存在其他情况，在此不再逐一举例说明。
举例来说，若映射EPS承载上下文中包括TFT，在情况三下，存在业务流模板操作语义错误：
情况三，PDU会话修改命令消息指示TFT操作为：删除专有EPS承载上下文的现有TFT。
以上只是示例，业务流模板操作语义错误还可以存在其他情况，在此不再逐一举例说明。
举例来说，若映射EPS承载上下文中包括TFT，在情况四下，存在业务流模板操作语法错误：
情况四，PDU会话修改命令消息指示的TFT操作为：“删除TFT”或“无TFT操作”，并且TFT中有非空包过滤器列表。
以上只是示例，业务流模板操作语法错误还可以存在其他情况，在此不再逐一举例说明。
举例来说，若映射EPS承载上下文中包括TFT，在情况五下，存在包过滤器语义错误：
情况五，一个包过滤器由冲突的包过滤器组件组成时，这将会使包过滤器无效。
以上只是示例，包过滤器语义错误还可以存在其他情况，在此不再逐一举例说明。
举例来说，若映射EPS承载上下文中包括TFT，在情况六下，存在包过滤器语法错误：
情况六，当包过滤器的编码中存在其他类型的语法错误时，例如使用包过滤器组件标识符的保留值。
以上只是示例，包过滤器语法错误还可以存在其他情况，在此不再逐一举例说明。
本申请实施例中，除了上面描述的错误之外，还可能存在其他错误。例如，情况七，如果在PDU会话修改命令消息包括的映射EPS承载上下文中的操作码为“创建新EPS承 载”，并且在PDU会话修改命令消息中既没有对应的授权QoS流描述，也没有映射EPS承载上下文中包含的EPS承载标识对应的现有QoS流描述。在该情况下，可以确定映射EPS承载上下文存在错误。
再例如，情况八，如果选择的PDU会话类型为“非结构化(Unstructured)”，则终端设备支持系统间从N1模式切换到S1模式，终端设备不支持在S1模式下设置为“非IP(non-IP)”的PDN类型建立PDN连接，并且，在PDU会话修改命令消息的授权QoS流描述资源元素中接收的一个或多个授权QoS流描述的参数列表字段包含EBI，则终端设备应在本地从该一个或多个授权QoS流描述的参数列表字段中移除EBI。在该情况下，可以确定映射EPS承载上下文存在错误。
再例如，情况九，如果选择的PDU会话类型为“以太网(Ethernet)”，则终端设备支持系统间从N1模式切换到S1模式，终端设备不支持在S1模式下设置为“非IP(non-IP)”的PDN类型建立PDN连接，终端设备、网络或两者在S1模式下不支持以太网PDN类型，并且，在PDU会话修改命令消息的授权QoS流描述资源元素中接收的一个或多个授权QoS流描述的参数列表字段包含EBI，终端设备应在本地从该一个或多个授权QoS流描述的参数列表字段中移除EBI。在该情况下，可以确定映射EPS承载上下文存在错误。
本申请实施例中，映射EPS承载上下文存在以上任一错误时，终端设备还可以执行S203：
S203：终端设备向网络设备发送PDU会话修改请求消息，删除映射EPS承载上下文，PDU会话修改请求消息包括错误对应的原因值；相应的，网络设备接收来自终端设备的PDU会话修改请求消息。
举例来说，如果存在映射EPS承载上下文操作语义错误，那么PDU会话修改请求消息包括的原因值为#85。
如果存在业务流模板操作语义错误，那么PDU会话修改请求消息包括的原因值为#41。
如果存在业务流模板操作语法错误，那么PDU会话修改请求消息包括的原因值为#42。
如果存在包过滤器语义错误，那么PDU会话修改请求消息包括的原因值为#44。
如果存在包过滤器语法错误，那么PDU会话修改请求消息包括的原因值为#45。
如果存在情况七至情况九中的错误，那么PDU会话修改请求消息包括的原因值为#85。
上面只是示例，每种错误还可能对应其它原因值，具体可以根据协议的演进确定。
S204：在第一协议数据单元会话没有对应的映射演进分组系统承载上下文的情况下，终端设备向网络设备发送PDU会话释放请求消息；相应的，网络设备接收来自终端设备的PDU会话释放请求消息。
其中，该PDU会话释放请求消息用于请求释放第一PDU会话。
本申请实施例中，第一PDU会话没有对应的映射EPS承载上下文，可以是指第一PDU会话不存在或缺失对应的映射EPS承载上下文。在该情况下，终端设备进行异系统变换时，例如从NR系统切换到LTE系统，终端设备在LTE系统中无法确定第一PDU会话对应的EPS承载，第一PDU会话对应的业务会出现数据传输不连续或失败。
第一PDU会话没有对应的映射EPS承载上下文可能存在多种场景，例如在S201至S203的情况下，第一PDU会话对应的映射EPS承载上下文存在错误时，终端设备删除第一PDU会话对应的映射EPS承载上下文，那么终端设备可以确定第一PDU会话没有对应的映射EPS承载上下文。当然，以上只是示例，第一PDU会话没有对应的映射EPS承载 上下文还可能存在其他情况，本申请对此并不限定。
本申请实施例中，为了减少释放第一PDU会话对应的业务的影响，终端设备可以在以下两种场景下释放第一PDU会话。
场景一，终端设备处于RRC空闲态(简称空闲态)或者RRC非激活态(简称非激活态)时，向网络设备发送PDU会话释放请求消息。
由于终端设备处于空闲态或者非激活态，终端设备不需要通过第一PDU会话传输业务数据，因此终端设备此时释放第一PDU会话，不会对第一PDU会话对应的业务造成影响。
场景二，如果在预设时长内，终端设备没有通过第一PDU会话传输业务的数据包，那么终端设备可以向网络设备发送PDU会话释放请求消息。
其中，预设时长的具体取值可以根据实际情况确定，本申请对此并不限定。预设时长可以为网络设备配置的，也可以是终端设备自主确定的，还可以是协议约定的。
由于终端设备在预设时长内没有通过第一PDU会话传输业务数据，因此可以认为当前不需要传输业务数据，终端设备此时释放第一PDU会话，不会对第一PDU会话对应的业务造成影响。
S205：网络设备向终端设备发送PDU会话释放命令消息；相应的，终端设备接收来自网络设备的PDU会话释放命令消息，该PDU会话释放命令消息用于指示释放第一PDU会话。
其中，PDU会话释放命令消息可以是对PDU会话释放请求消息的响应，网络设备可以在释放第一PDU会话完成时，向终端设备发送PDU会话释放命令消息。
进一步的，终端设备将第一PDU会话释放之后，为了不影响第一PDU会话对应的业务，终端设备还可以为该业务重新建立PDU会话，即执行以下流程：
S206：终端设备向网络设备发送PDU会话建立请求消息；相应的，网络设备接收来自终端设备的PDU会话建立请求消息。
其中，PDU会话建立请求消息用于请求建立第二PDU会话；第一PDU会话与第二PDU会话对应同一个业务。
在建立第二PDU会话的过程中，网络设备可以向终端设备发送第二PDU会话对应的映射EPS承载上下文等信息，具体可以参考如下所述。
S207：网络设备向终端设备发送PDU会话建立接受(PDU session establishment accept)消息；相应的，终端设备接收来自网络设备的PDU会话建立接受消息。
PDU会话建立接受消息包括第二PDU会话对应的映射EPS承载上下文，以及第二PDU会话包括的QoS流的QoS流描述等信息。也就是说，建立的第二PDU会话具有对应的映射EPS承载上下文，可用作异系统变换。
通过本申请实施例提供的方法，终端设备确定第一PDU会话没有对应的映射EPS承载上下文时，可以主动将第一PDU会话去激活，再重新为第一PDU会话对应的业务建立新的第二PDU会话，从而可以保证终端设备在进行异系统切换(例如从NR系统切换到LTE系统)过程中，业务的可靠性与连续性，并且可避免通话失败、业务中断、不连续等情况。
举例来说，对于NR系统下，终端设备存在用于语音呼叫的IMS业务对应的PDU会话的情况下，如果网络设备通过PDU会话修改命令消息修改IMS业务对应的PDU会话， 终端设备检查IMS业务对应的PDU会话的映射EPS承载上下文确定存在错误，从而删除IMS业务对应的PDU会话的映射EPS承载上下文时，通过本申请实施例提供的方法，终端设备可以重新建立IMS业务对应的PDU会话，重新建立的IMS业务对应的PDU会话具有对应的映射EPS承载。当终端设备在NR系统中发起语音通话业务，网络侧配置终端设备切换到LTE系统进行EPS FB呼叫时，不会出现语音呼叫不连续或失败等情况的发生，提高业务的可靠性，提高用户体验。
再例如，NR系统下，终端设备存在IMS业务对应的PDU会话和非IMS业务对应的PDU会话的情况下，如果NR系统下无映射承载时，通过本申请实施例提供的方法，终端设备可以重新建立该非IMS业务对应的PDU会话，重新建立的PDU会话具有对应的映射EPS承载。此时终端设备从NR系统切换到LTE系统时，业务数据可以不中断地到传输，从而减少切换时延，提高业务的可靠性，提高用户体验。
下面通过一个具体的实施例描述前面的流程。如图3所示，为本申请实施例提供的一种会话建立方法流程示意图。
S301：网络设备向终端设备发送PDU会话修改命令消息。
该PDU会话修改命令消息用于修改第一PDU会话，该PDU会话修改命令消息包括映射EPS承载上下文等信息。
S302：终端设备向网络设备发送PDU会话修改完成消息。
该PDU会话修改命令完成消息是对上面的消息的响应消息。
如果终端设备确定映射EPS承载上下文存在S201中描述的至少一种错误，则执行以下流程：
S303：终端设备向网络设备发送PDU会话修改请求消息，删除映射EPS承载上下文，PDU会话修改请求消息包括错误对应的原因值。
当终端设备处于空闲态或者非激活态，或者终端设备在预设时长内没有通过第一PDU会话传输业务的数据包时，执行以下流程：
S304：终端设备向网络设备发送PDU会话释放请求消息。
该PDU会话释放请求消息用于请求将第一PDU会话释放。
S305：网络设备向终端设备发送PDU会话释放命令消息。
该协议数据单元会话释放命令消息用于指示完成释放第一PDU会话，即该消息表示网络设备已经将第一PDU会话相关信息删除。
S306：终端设备向网络设备发送PDU会话释放完成消息。
该消息是响应PDU会话释放命令消息的消息，终端设备可以在本地删除第一PDU会话相关信息后发送PDU会话释放完成消息。
进一步的，终端设备还可以触发为第一PDU会话对应的业务重新建立PDU会话，从而保证第一PDU会话对应的业务数据传输的连续性，具体可以包括以下步骤：
S307：终端设备向网络设备发送PDU会话建立请求消息。
该消息用于请求为第一PDU会话对应的业务建立第二PDU会话。
S308：网络设备向终端设备发送PDU会话建立接受消息。
该消息包括第二PDU会话对应的映射EPS承载上下文等信息。
通过上述流程，终端设备确定业务对应的第一PDU会话没有对应的映射EPS承载上下文时，释放第一PDU会话，并建立该业务对应的第二PDU会话，建立的第二PDU会 话存在对应的映射EPS承载上下文，从而可以在终端设备进行异系统变换时，保证该业务的数据传输连续。
可以理解，本申请实施例中的图2至图3中的例子仅仅是为了便于本领域技术人员理解本申请实施例，并非要将本申请实施例限于例示的具体场景。本领域技术人员根据图2至图3的例子，显然可以进行各种等价的修改或变化，这样的修改或变化也落入本申请实施例的范围内。
还可以理解，上述图2至图3中各个步骤仅是示例性说明，对此不作严格限定。此外，上述各过程的序号的大小并不意味着执行顺序的先后，各过程的执行顺序应以其功能和内在逻辑确定，而不应对本申请实施例的实施过程构成任何限定。
还可以理解，本申请的各实施例中的一些可选的特征，在某些场景下，可以不依赖于其他特征，也可以在某些场景下，与其他特征进行结合，不作限定。
还可以理解，本申请的各实施例中的方案可以进行合理的组合使用，并且实施例中出现的各个术语的解释或说明可以在各个实施例中互相参考或解释，对此不作限定。
还可以理解，在本申请的各实施例中的各种数字序号的大小并不意味着执行顺序的先后，仅为描述方便进行的区分，不应对本申请实施例的实施过程构成任何限定。
还可以理解，在本申请的各实施例中涉及到一些消息名称，如协议数据单元会话释放请求消息等，其命名不对本申请实施例的保护范围造成限定。
相应于上述各方法实施例给出的方法，本申请实施例还提供了相应的装置，所述装置包括用于执行上述各个方法实施例相应的模块。该模块可以是软件，也可以是硬件，或者是软件和硬件结合。可以理解的是，上述各方法实施例所描述的技术特征同样适用于以下装置实施例。
图4是本申请实施例提供的通信装置结构示意图。该通信装置400包括通信单元420和处理单元410。通信单元420可以实现相应的通信功能，通信单元420还可以为通信接口或通信单元。处理单元410可以实现相应的处理功能，如处理指令和/或数据。
一种可能的实现方式，该通信装置400还可以包括存储单元，该存储单元可以用于存储指令和/或数据，处理单元410可以读取存储单元中的指令和/或数据，以使得装置实现前述方法实施例。
该通信装置400可以用于执行上文方法实施例中终端设备所执行的动作，这时，该通信装置400中的通信单元420用于执行上文方法实施例中终端设备的收发相关的操作，处理单元410用于执行上文方法实施例中终端设备的处理相关的操作。
作为一种设计，该通信装置400用于执行上文方法实施例中终端设备所执行的动作：
处理单元，用于在第一协议数据单元会话没有对应的映射演进分组系统承载上下文的情况下，通过通信单元发送协议数据单元会话释放请求消息，所述协议数据单元会话释放请求消息用于请求释放所述第一协议数据单元会话；
通信单元，用于接收协议数据单元会话释放命令消息，所述协议数据单元会话释放命令消息用于指示释放所述第一协议数据单元会话；发送协议数据单元会话建立请求消息，所述协议数据单元会话建立请求消息用于请求建立第二协议数据单元会话；所述第一协议数据单元会话与所述第二协议数据单元会话对应同一个业务。
在一种可能的设计中，所述通信单元发送协议数据单元会话释放请求消息之前，所述通信装置处于空闲态或者非激活态。
在一种可能的设计中，所述通信单元发送协议数据单元会话释放请求消息之前，在预设时长内没有通过所述第一协议数据单元会话传输所述业务的数据包。
在一种可能的设计中，所述通信单元还用于：
接收协议数据单元会话修改命令消息，所述协议数据单元会话修改命令消息包括所述映射演进分组系统承载上下文；
在所述映射演进分组系统承载上下文存在错误的情况下，发送协议数据单元会话修改请求消息，所述协议数据单元会话修改请求消息包括所述错误对应的原因值；
所述处理单元还用于：删除所述映射演进分组系统承载上下文。
在一种可能的设计中，所述错误包括以下一项或多项：
所述映射演进分组系统承载上下文操作语义错误；
所述映射演进分组系统承载上下文包括的业务流模板操作语义错误；
所述映射演进分组系统承载上下文包括的业务流模板操作语法错误；
所述映射演进分组系统承载上下文包括的包过滤器语义错误；
所述映射演进分组系统承载上下文包括的包过滤器语法错误。
在一种可能的设计中，所述通信单元还用于：
接收协议数据单元会话建立接受消息，所述协议数据单元会话建立接受消息包括所述第二协议数据单元会话对应的映射演进分组系统承载上下文。
以上只是示例，处理单元410和通信单元420还可以执行其他功能，更详细的描述可以参考图2至图3所示的方法实施例中相关描述，这里不加赘述。
如图5所示为本申请实施例提供的一种通信装置，图5所示的通信装置可以为图4所示的通信装置的一种硬件电路的实现方式。该通信装置可适用于前面所示出的流程图中，执行上述方法实施例中终端设备的功能。为了便于说明，图5仅示出了该通信装置的主要部件。
如图5所示，通信装置500包括处理器510和接口电路520。处理器510和接口电路520之间相互耦合。可以理解的是，接口电路520可以为收发器、管脚或输入输出接口。可选的，通信装置500还可以包括存储器530，用于存储处理器510执行的指令或存储处理器510运行指令所需要的输入数据或存储处理器510运行指令后产生的数据。可选地，存储器530的部分或全部可以位于处理器510中。
当通信装置500用于实现图2至图3所示的方法时，处理器510用于实现上述处理单元410的功能，接口电路520用于实现上述通信单元420的功能。
可以理解的是，本申请的实施例中的处理器可以是中央处理单元，还可以是其它通用处理器、数字信号处理器、专用集成电路或者其它可编程逻辑器件、晶体管逻辑器件，硬件部件或者其任意组合。通用处理器可以是微处理器，也可以是任何常规的处理器。
本申请的实施例中的存储器可以是随机存取存储器、闪存、只读存储器、可编程只读存储器、可擦除可编程只读存储器、电可擦除可编程只读存储器、寄存器、硬盘、移动硬盘或者本领域熟知的任何其它形式的存储介质中。
需要说明的是，当处理器为通用处理器或者其他可编程逻辑器件、分立门或者晶体管逻辑器件、分立硬件组件时，存储器(存储模块)可以集成在处理器中。
还需要说明的是，本文描述的存储器旨在包括但不限于这些和任意其它适合类型的存储器。
本领域内的技术人员应明白，本申请的实施例可提供为方法、系统、或计算机程序产品。因此，本申请可采用完全硬件实施例、完全软件实施例、或结合软件和硬件方面的实施例的形式。而且，本申请可采用在一个或多个其中包含有计算机可用程序代码的计算机可用存储介质(包括但不限于磁盘存储器、光学存储器等)上实施的计算机程序产品的形式。
本申请是参照根据本申请的方法、设备(系统)、和计算机程序产品的流程图和/或方框图来描述的。应理解可由计算机程序指令实现流程图和/或方框图中的每一流程和/或方框、以及流程图和/或方框图中的流程和/或方框的结合。可提供这些计算机程序指令到通用计算机、专用计算机、嵌入式处理机或其他可编程数据处理设备的处理器以产生一个机器，使得通过计算机或其他可编程数据处理设备的处理器执行的指令产生用于实现在流程图一个流程或多个流程和/或方框图一个方框或多个方框中指定的功能的装置。
这些计算机程序指令也可存储在能引导计算机或其他可编程数据处理设备以特定方式工作的计算机可读存储器中，使得存储在该计算机可读存储器中的指令产生包括指令装置的制造品，该指令装置实现在流程图一个流程或多个流程和/或方框图一个方框或多个方框中指定的功能。
显然，本领域的技术人员可以对本申请进行各种改动和变型而不脱离本申请的范围。这样，倘若本申请的这些修改和变型属于本申请权利要求及其等同技术的范围之内，则本申请也意图包含这些改动和变型在内。

Claims (16)

  1. 一种会话建立方法，其特征在于，所述方法应用于终端设备，包括：
    在第一协议数据单元会话没有对应的映射演进分组系统承载上下文的情况下，发送协议数据单元会话释放请求消息，所述协议数据单元会话释放请求消息用于请求释放所述第一协议数据单元会话；
    接收协议数据单元会话释放命令消息，所述协议数据单元会话释放命令消息用于指示释放所述第一协议数据单元会话；
    发送协议数据单元会话建立请求消息，所述协议数据单元会话建立请求消息用于请求建立第二协议数据单元会话；
    其中，所述第一协议数据单元会话与所述第二协议数据单元会话对应同一个业务。
  2. 根据权利要求1所述的方法，其特征在于，所述发送协议数据单元会话释放请求消息之前，所述终端设备处于空闲态或者非激活态。
  3. 根据权利要求1所述的方法，其特征在于，所述发送协议数据单元会话释放请求消息之前，所述方法还包括：
    在预设时长内没有通过所述第一协议数据单元会话传输所述业务的数据包。
  4. 根据权利要求1至3任一所述的方法，其特征在于，所述在第一协议数据单元会话没有对应的映射演进分组系统承载上下文的情况下，具体包括：
    接收协议数据单元会话修改命令消息，所述协议数据单元会话修改命令消息包括所述映射演进分组系统承载上下文；
    在所述映射演进分组系统承载上下文存在错误的情况下，发送协议数据单元会话修改请求消息，并删除所述映射演进分组系统承载上下文，所述协议数据单元会话修改请求消息包括所述错误对应的原因值。
  5. 根据权利要求4所述的方法，其特征在于，所述错误包括以下一项或多项：
    所述映射演进分组系统承载上下文操作语义错误；
    所述映射演进分组系统承载上下文包括的业务流模板操作语义错误；
    所述映射演进分组系统承载上下文包括的业务流模板操作语法错误；
    所述映射演进分组系统承载上下文包括的包过滤器语义错误；
    所述映射演进分组系统承载上下文包括的包过滤器语法错误。
  6. 根据权利要求1至5任一所述的方法，其特征在于，所述方法还包括：
    接收协议数据单元会话建立接受消息，所述协议数据单元会话建立接受消息包括所述第二协议数据单元会话对应的映射演进分组系统承载上下文。
  7. 一种通信装置，其特征在于，包括：
    处理单元，用于在第一协议数据单元会话没有对应的映射演进分组系统承载上下文的情况下，通过通信单元发送协议数据单元会话释放请求消息，所述协议数据单元会话释放请求消息用于请求释放所述第一协议数据单元会话；
    通信单元，用于接收协议数据单元会话释放命令消息，所述协议数据单元会话释放命令消息用于指示完成释放所述第一协议数据单元会话；发送协议数据单元会话建立请求消息，所述协议数据单元会话建立请求消息用于请求建立第二协议数据单元会话；所述第一协议数据单元会话与所述第二协议数据单元会话对应同一个业务。
  8. 根据权利要求7所述的装置，其特征在于，所述通信单元发送协议数据单元会话释放请求消息之前，所述通信装置处于空闲态或者非激活态。
  9. 根据权利要求7所述的装置，其特征在于，所述通信单元发送协议数据单元会话释放请求消息之前，在预设时长内没有通过所述第一协议数据单元会话传输所述业务的数据包。
  10. 根据权利要求7至9任一所述的装置，其特征在于，所述通信单元还用于：
    接收协议数据单元会话修改命令消息，所述协议数据单元会话修改命令消息包括所述映射演进分组系统承载上下文；
    在所述映射演进分组系统承载上下文存在错误的情况下，发送协议数据单元会话修改请求消息，所述协议数据单元会话修改请求消息包括所述错误对应的原因值；
    所述处理单元还用于：删除所述映射演进分组系统承载上下文。
  11. 根据权利要求10所述的装置，其特征在于，所述错误包括以下一项或多项：
    所述映射演进分组系统承载上下文操作语义错误；
    所述映射演进分组系统承载上下文包括的业务流模板操作语义错误；
    所述映射演进分组系统承载上下文包括的业务流模板操作语法错误；
    所述映射演进分组系统承载上下文包括的包过滤器语义错误；
    所述映射演进分组系统承载上下文包括的包过滤器语法错误。
  12. 根据权利要求7至11任一所述的装置，其特征在于，所述通信单元还用于：
    接收协议数据单元会话建立接受消息，所述协议数据单元会话建立接受消息包括所述第二协议数据单元会话对应的映射演进分组系统承载上下文。
  13. 一种通信装置，其特征在于，包括处理器，所述处理器和存储器耦合，所述存储器中存储有计算机程序；所述处理器用于调用所述存储器中的计算机程序，使得所述通信装置执行如权利要求1至6任一所述的方法。
  14. 一种无线通信装置，其特征在于，包括：
    处理电路和接口电路；其中，
    所述接口电路用于与所述无线通信装置外部的存储器耦合，并为所述处理电路访问所述存储器提供通信接口；
    所述处理电路用于执行所述存储器中的程序指令，以实现如权利要求1至6中的任一所述方法。
  15. 一种计算机可读存储介质，其特征在于，所述存储介质中存储有计算机程序或指令，当所述计算机程序或指令被计算机执行时，实现如权利要求1至6中任一项所述的方法。
  16. 一种计算机程序产品，其特征在于：
    所述计算机程序产品包含的程序代码被处理器执行时，实现权利要求1至6中任一项所述的方法。
PCT/CN2023/072705 2022-04-29 2023-01-17 一种会话建立方法及装置 WO2023207229A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN202210473226.8 2022-04-29
CN202210473226.8A CN117014980A (zh) 2022-04-29 2022-04-29 一种会话建立方法及装置

Publications (1)

Publication Number Publication Date
WO2023207229A1 true WO2023207229A1 (zh) 2023-11-02

Family

ID=88517215

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2023/072705 WO2023207229A1 (zh) 2022-04-29 2023-01-17 一种会话建立方法及装置

Country Status (2)

Country Link
CN (1) CN117014980A (zh)
WO (1) WO2023207229A1 (zh)

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN109937590A (zh) * 2016-11-09 2019-06-25 Lg电子株式会社 切换方法和用户设备
CN111065133A (zh) * 2018-10-17 2020-04-24 华为技术有限公司 用于在不同通信系统间转移场景下的通信方法和装置
US20200162958A1 (en) * 2018-11-19 2020-05-21 Mediatek Inc. Insufficient Resources in the UE during PDU Session Establishment Procedure
CN114125952A (zh) * 2020-08-26 2022-03-01 华为技术有限公司 一种承载处理方法及装置

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN109937590A (zh) * 2016-11-09 2019-06-25 Lg电子株式会社 切换方法和用户设备
CN111065133A (zh) * 2018-10-17 2020-04-24 华为技术有限公司 用于在不同通信系统间转移场景下的通信方法和装置
US20200162958A1 (en) * 2018-11-19 2020-05-21 Mediatek Inc. Insufficient Resources in the UE during PDU Session Establishment Procedure
CN111466136A (zh) * 2018-11-19 2020-07-28 联发科技股份有限公司 用于无效服务质量流描述的映射演进分组系统承载上下文的处理技术
CN114125952A (zh) * 2020-08-26 2022-03-01 华为技术有限公司 一种承载处理方法及装置

Also Published As

Publication number Publication date
CN117014980A (zh) 2023-11-07

Similar Documents

Publication Publication Date Title
JP4318707B2 (ja) 無線通信システムにおける送信側の再確立時にタイマーを処理する方法及び装置
JP5537702B2 (ja) Ｒｒｃ接続プロセスを改善する方法及び通信装置
EP4017102A1 (en) Method, terminal device, and network device used for transmitting data
CN109246770B (zh) 一种切换的方法、终端设备及网络设备
US9357580B2 (en) Method for switching communication connection mode, communication system, base station, transmitter and receiver
WO2021238774A1 (zh) 通信方法及装置
US20210251032A1 (en) Communication method, apparatus, and system
AU2019272364A1 (en) Communication method and communications apparatus
WO2021164720A1 (zh) 重建立的方法和通信装置
WO2019062621A1 (zh) 一种进行重复传输的方法和设备
US20230262557A1 (en) Methods and devices for enhancing integrated access backhaul networks for new radio
WO2020001256A1 (zh) 一种数据传输方法及装置
WO2024037611A1 (zh) 注册信息同步方法、装置、设备及介质
US20230199600A1 (en) Method and communications apparatus for configuring assistance information
WO2023207229A1 (zh) 一种会话建立方法及装置
WO2022252874A1 (zh) 信令风暴抑制方法、移动终端、电子设备及存储介质
WO2021249425A1 (zh) 一种通信方法及相关装置
WO2021147672A1 (zh) 会话处理方法及通信装置
JP7206390B2 (ja) データの送信方法およびデバイス
WO2021114115A1 (zh) 通信方法及装置
WO2023011077A1 (zh) 通信方法及装置
US20230345323A1 (en) Data transmission method and apparatus
WO2023011612A1 (zh) 移动性管理的方法及通信装置
WO2023246746A1 (zh) 一种通信方法及相关设备
WO2021203249A1 (zh) 会话释放方法与装置

Legal Events

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

Ref document number: 23794665

Country of ref document: EP

Kind code of ref document: A1