A method and device for allocating bearer identifiers

Abstract

The embodiments of the present application relate to the field of communication technology, and provide a bearer identifier allocation method and apparatus, which are used to solve the problem of abnormal node processing when the bearer identifier to be allocated and the bearer identifier to be withdrawn are the same. A first device receives a first request message from an access management node, the first request message is used to establish or update a first quality of service QoS flow, the first request message includes a first packet data unit PDU session identifier, a first QoS flow identifier corresponding to the first QoS flow, and a first evolved packet system bearer identifier EBI, the first device includes a terminal device and / or an access network device; if a second QoS flow has been established on the first device, and the second EBI corresponding to the second QoS flow is the same as the first EBI, the first device sends a first response message to the access management node, and the first response message is used to indicate that the allocation of the first EBI failed.

Description

Technical Field

[0001] The present application relates to the field of communication technology, and in particular to a method and device for allocating a bearer identifier. Background Art

[0002] In an evolved packet system (EPS) network, an EPS bearer identity (EBI) uniquely identifies an EPS bearer of a terminal device. A terminal device can have up to 11 or 15 EPS bearers. In a fifth-generation mobile communication technology (5G) network, a QoS flow identity (QFI) uniquely identifies the QoS flow of a packet data unit (PDU) session of a terminal device. A terminal device can have up to 15 PDU sessions, and each PDU session can have 64 QoS flows.

[0003] During mobility, a terminal device may switch from a 5G network to an EPS network. To ensure the service experience of the terminal device, the QoS flow of the terminal device can be mapped to an EPS bearer to ensure that the terminal device's service is not interrupted after switching to the EPS network. When the terminal device establishes a QoS flow on the 5G network, the access management node allocates the EBI corresponding to the QoS flow based on the request of the session node. However, since the number of QoS flows allowed to be established by the terminal device is much greater than the number of EPS bearers, the access management node may have already allocated the full EBI for the terminal device when a new EBI is requested. At this time, the access management node may withdraw the already allocated EBI and allocate the withdrawn EBI to the newly established QoS flow.

[0004] During the EBI allocation and revocation process, the EBI allocation message may be sent to the terminal device or access node before the EBI revocation message. If a QoS flow with the same EBI is already allocated on the terminal device or access node, the terminal device or access node will cause processing anomalies. Summary of the Invention

[0005] An embodiment of the present application provides a bearer identifier allocation method and device, which is used to solve the problem that when the bearer identifier allocation process is earlier than the bearer identifier withdrawal process, the same bearer identifier is allocated when the bearer identifier that needs to be withdrawn on the node has not been withdrawn, resulting in the same bearer identifier on the node corresponding to different QoS flows, causing node processing abnormalities.

[0006] In the first aspect, an embodiment of the present application provides a bearer identifier allocation method, the method comprising: a first device receives a first request message from an access management node, the first request message is used to establish or update a first quality of service QoS flow, the first request message includes a first packet data unit PDU session identifier, a first QoS flow identifier corresponding to the first QoS flow, and a first evolved packet system bearer identifier EBI, the first device includes a terminal device and / or an access network device; if a second QoS flow has been established on the first device, the second EBI corresponding to the second QoS flow is the same as the first EBI, the first device sends a first response message to the access management node, and the first response message is used to indicate that the allocation of the first EBI failed.

[0007] In an embodiment of the present application, because the bearer identifier allocation process is earlier than the bearer identifier withdrawal process, a QoS flow with the same EBI has been allocated on the first device, and the first device determines that the bearer identifier allocation has failed, which can avoid the situation where the same bearer identifier corresponds to different QoS flows, causing processing abnormalities in the first device.

[0008] In a possible implementation, the first device may further establish or update the first QoS flow, and the first response message is further used to indicate that the first QoS flow is successfully established or updated.

[0009] In one possible implementation, the first device further determines that the second PDU session identifier associated with the second EBI is different from the first PDU session identifier associated with the first EBI. In this way, the first device can determine that the PDU sessions corresponding to the same EBI are different. Since different PDU sessions are prone to the problem of the bearer identifier allocation process being earlier than the bearer identifier withdrawal process, the first device can avoid the same bearer identifier corresponding to different QoS flows by determining that the bearer identifier allocation has failed.

[0010] In one possible implementation, the first device may further receive a second request message from the access management node, the second request message being used to withdraw the second EBI corresponding to the second QoS flow, the second request message including a second PDU session identifier, a second QoS flow identifier corresponding to the second QoS flow, and the second EBI; the first device deletes the second EBI; and the first device sends a second response message to the access management node, the second response message being used to indicate successful withdrawal of the second EBI. By deleting the currently saved EBI, the first device can avoid conflicts caused by the currently saved EBI being the same as the allocated EBI, and can also avoid processing exceptions.

[0011] In second aspect, an embodiment of the present application provides a bearer identifier allocation method, the method comprising: a session node receives a first EBI associated with a first QoS flow from an access management node; the session node sends a third request message to the access management node, the third request message including a first PDU session identifier, a first QoS flow identifier corresponding to the first QoS flow, and the first EBI; the session node receives a third response message from the access management node, the third response message being used to indicate that the allocation of the first EBI has failed.

[0012] The session node can be considered as the second device.

[0013] In a possible implementation, the third response message is further used to indicate that the first QoS flow is established or updated successfully.

[0014] In one possible implementation, the session node may further notify the access management node to withdraw the first EBI corresponding to the first QoS flow; or the session node may further send the third request message to the access management node again. The session node may notify the access management node to withdraw the first EBI and retry allocating a bearer identifier.

[0015] In a third aspect, an embodiment of the present application provides a bearer identifier allocation method, the method comprising: an access management node sends a first evolved packet system bearer identifier EBI associated with a first quality of service QoS flow to a first session node; the access management node receives a third request message from the first session node, the third request message including a first packet data unit PDU session identifier, a first QoS flow identifier corresponding to the first QoS flow, and the first EBI; the access management node sends a first request message to a first device, the first request message being used to establish or update a first quality of service QoS flow, the first request message including the first PDU session identifier, the first QoS flow identifier, and the first EBI, the first device including a terminal device and / or an access network device; the access management node receives a first response message from the first device, the first response message being used to indicate that the allocation of the first EBI failed; the access management node sends a third response message to the first session node, the third response message being used to indicate that the allocation of the first EBI failed.

[0016] In a possible implementation, the first response message is further used to indicate that the first QoS flow is successfully established or updated; and / or the third response message is further used to indicate that the first QoS flow is successfully established or updated.

[0017] In one possible implementation, the access management node may also receive a second response message from the first device, where the second response message is used to indicate that the second EBI corresponding to the second QoS flow is successfully withdrawn, and the second QoS flow is a QoS flow that has been established on the first device; the access management node sends a fourth response message to the second session node, where the fourth response message is used to indicate that the second EBI is successfully withdrawn.

[0018] In a possible implementation, before receiving the second response information from the first device, the access management node may also send a second request message to notify the first device to withdraw the second EBI based on the indication information of withdrawing the second EBI contained in the fourth request message from the second session node.

[0019] In fourth aspect, an embodiment of the present application provides a bearer identifier allocation method, the method comprising: a first device receives a first request message from an access management node, the first request message is used to establish or update a first quality of service QoS flow, the first request message includes a first packet data unit PDU session identifier, a first QoS flow identifier corresponding to the first QoS flow, and a first evolved packet system bearer identifier EBI, the first device includes a terminal device and / or an access network device; if a second QoS flow has been established on the first device, the second EBI corresponding to the second QoS flow is the same as the first EBI, the first device deletes the second EBI; the first device sends a first response message to the access management node, the first response message is used to indicate that the first EBI allocation is successful.

[0020] In an embodiment of the present application, because the bearer identifier allocation process is earlier than the bearer identifier withdrawal process, a QoS flow with the same EBI has been allocated on the first device. The first device can directly delete the bearer identifier that needs to be withdrawn, thereby avoiding the situation where the same bearer identifier corresponds to different QoS flows, causing processing abnormalities in the first device.

[0021] In a possible implementation, the first device may further establish or update the first QoS flow, and the first response message is further used to indicate that the first QoS flow is successfully established or updated.

[0022] In a possible implementation, the first device may further determine that the second PDU session identifier associated with the second EBI is different from the first PDU session identifier associated with the first EBI.

[0023] In a fifth aspect, an embodiment of the present application provides a bearer identifier allocation method, the method comprising: an access management node sends a second request message to a second session node, the second request message being used to indicate the allocation of a first EBI for a first PDU session and the withdrawal of a second EBI for a second PDU session; the access management node sends a first EBI associated with a first QoS flow identifier to the first session node; the access management node receives a third request message from the first session node, the third request message being used to establish or update a first QoS flow, the third request message comprising a first PDU session identifier, a first QoS flow identifier corresponding to the first QoS flow, and a first EBI; the access management node sends a first request message to a first device, the first request message being used to establish or update a first QoS flow, the first request message comprising a first PDU session identifier, a first QoS flow identifier corresponding to the first QoS flow, and a first EBI, the first device comprising a terminal device and / or an access network device; the access management node receives a first response message, the first response message being used to indicate that the allocation of the first EBI is successful.

[0024] In a possible implementation, the first response message is further used to indicate that the first QoS flow is established or updated successfully.

[0025] In the sixth aspect, an embodiment of the present application provides a bearer identifier allocation method, the method including: an access management node receives a first request message from a first session node, the first request message is used to request allocation of EBI for the first QoS flow; the access management node sends a second request message to a second session node, the second request message is used to withdraw the first EBI of the second QoS flow, the second QoS flow belongs to a second PDU session; the access management node receives a first response message from the second session node, the first response message is used to notify that the withdrawal of the first EBI is successful; after the access management node waits for the withdrawal of the first EBI to be completed, the access management node sends a second response message to the first session node, the second response message includes the first EBI associated with the first QoS flow.

[0026] In an embodiment of the present application, the first device waits for the bearer identifier withdrawal process to be completed to ensure that the bearer identifier allocation process is later than the bearer identifier withdrawal process, which can avoid the situation where the same bearer identifier corresponds to different QoS flows, causing the first device to have processing abnormalities.

[0027] In a possible implementation, the access management node may further start a first timer after receiving the first response message, and when the first timer times out, the access management node determines that the withdrawal of the first EBI is completed; or

[0028] The access management node may also receive a third response message from the first device, where the first device includes a terminal device and / or an access network device. The third response message includes the second PDU session identifier. The access management node determines that the withdrawal of the first EBI is completed based on the third response message.

[0029] In the seventh aspect, an embodiment of the present application provides a bearer identifier allocation method, the method comprising: a session node sends a first request message to an access management node, the first request message being used to request allocation of an EBI for the first QoS flow; the session node receives a first response message, the first response message including the first EBI associated with the first QoS flow, and also including indication information for withdrawing the EBI; the session node starts a second timer based on the indication information included in the first response message, if the second timer times out, the session node sends a second request message, the second request message being used to establish or update the first QoS flow, the second request message including the first PDU session identifier, the first QoS flow identifier corresponding to the first QoS flow, and the first EBI.

[0030] In an embodiment of the present application, the bearer identifier is withdrawn first through the first response message to ensure that the bearer identifier allocation process is later than the bearer identifier withdrawal process, which can avoid the situation where the same bearer identifier corresponds to different QoS flows, causing processing abnormalities in the first device.

[0031] In the eighth aspect, an embodiment of the present application provides a bearer identifier allocation method, the method including: an access management node receives a first request message from a first session node, the first request message is used to request allocation of EBI for the first QoS flow; the access management node sends a third request message to the second session node, the third request message is used to withdraw the first EBI of the second QoS flow; the access management node sends a first response message to the first session node, the first response message includes the first EBI associated with the first QoS flow, and also includes indication information for withdrawing the EBI.

[0032] In a ninth aspect, embodiments of the present application provide a bearer identifier allocation device that implements the functions described in the aforementioned aspects. These functions can be implemented through hardware or through hardware executing corresponding software. The hardware or software includes one or more functional modules corresponding to the aforementioned functions.

[0033] In the tenth aspect, an embodiment of the present application provides a bearer identifier allocation device, which can be the first device in the above aspects (such as a terminal device and / or an access network device), or can be the access management node in the above aspects, the latter can be the session node in the above aspects, or a chip set in the first device or the access management node or the session node.

[0034] The device includes a transceiver and a processor, and optionally, a memory, wherein the memory is used to store computer programs or instructions, and the processor is coupled to the memory and the transceiver, respectively, and when the processor executes the computer program or instructions, the device executes the methods described in the above aspects through the transceiver.

[0035] In an eleventh aspect, an embodiment of the present application provides a computer program product, comprising: a computer program code, which, when executed on a computer, enables the computer to execute the methods described in the above aspects.

[0036] In the twelfth aspect, an embodiment of the present application provides a chip system, which includes a processor and a memory, and the processor and the memory are electrically coupled; the memory is used to store computer program instructions; the processor is used to execute part or all of the computer program instructions in the memory, and when the part or all of the computer program instructions are executed, it is used to implement the functions of the methods described in the above aspects.

[0037] In one possible design, the chip system may further include a transceiver configured to transmit signals processed by the processor or receive signals input to the processor. The chip system may be composed of a chip or may include a chip and other discrete components.

[0038] In a thirteenth aspect, an embodiment of the present application provides a computer-readable storage medium, which stores a computer program. When the computer program is run, the methods described in the above aspects are executed.

[0039] In a fourteenth aspect, an embodiment of the present application provides a communication system, the system comprising: a first device, an access management node and a session node.

[0040] The first device, the access management node, and the session node are respectively used to implement the methods described in the above aspects. BRIEF DESCRIPTION OF THE DRAWINGS

[0041] The following is a brief introduction to the drawings required for describing the embodiments.

[0042] Figure 1A schematic diagram of a communication system architecture provided in an embodiment of the present application;

[0043] Figure 2 A schematic diagram of a bearer identity allocation process;

[0044] Figure 3 、 Figure 4 、 Figure 5 、 Figure 6 、 Figure 7 、 Figure 8 、 Figure 9 、 Figure 10 A schematic diagram of a bearer identifier allocation process provided in an embodiment of the present application;

[0045] Figure 11 、 Figure 12 A schematic diagram of the structure of a bearer identifier allocation device provided in an embodiment of the present application. DETAILED DESCRIPTION

[0046] The present invention will be described in further detail below with reference to the accompanying drawings.

[0047] This application will present various aspects, embodiments, or features in the context of systems that may include multiple devices, components, modules, etc. It should be understood and appreciated that each system may include additional devices, components, modules, etc., and / or may not include all of the devices, components, modules, etc. discussed in conjunction with the figures. Furthermore, combinations of these aspects may also be used.

[0048] Additionally, in the embodiments of this application, the word "exemplary" is used to indicate an example, illustration, or description. Any embodiment or design described in this application as "exemplary" should not be construed as preferred or advantageous over other embodiments or designs. Rather, the use of the word "exemplary" is intended to present concepts in a concrete way.

[0049] The network architecture and business scenarios described in the embodiments of the present application are intended to more clearly illustrate the technical solutions of the embodiments of the present application, and do not constitute a limitation on the technical solutions provided in the embodiments of the present application. Ordinary technicians in this field will know that with the evolution of network architecture and the emergence of new business scenarios, the technical solutions provided in the embodiments of the present application are also applicable to similar technical problems.

[0050] The following explains some of the terms used in the embodiments of the present application to facilitate understanding by those skilled in the art.

[0051] 1) Terminal devices, including devices that provide voice and / or data connectivity to users. Specifically, these devices may provide voice, data, or both. Examples include handheld devices with wireless connectivity or processing devices connected to a wireless modem. These devices may communicate with the core network via a radio access network (RAN), exchanging voice or data with the RAN, or both. The terminal device may include user equipment (UE), wireless terminal device, mobile terminal device, device-to-device (D2D) terminal device, vehicle-to-everything (V2X) terminal device, machine-to-machine / machine-type communications (M2M / MTC) terminal device, Internet of Things (IoT) terminal device, subscriber unit, subscriber station, mobile station, remote station, access point (AP), remote terminal, access terminal, user terminal, user agent, or user device, etc. For example, it may include a mobile phone (or so-called "cellular" phone), a computer with a mobile terminal device, a portable, pocket-sized, handheld, or computer-built-in mobile device, etc. Examples include personal communication service (PCS) phones, cordless phones, session initiation protocol (SIP) phones, wireless local loop (WLL) stations, personal digital assistants (PDAs), and other devices. Also included are limited devices, such as those with low power consumption, limited storage capacity, or limited computing power. Examples include information sensing devices such as barcode scanners, radio frequency identification (RFID), sensors, global positioning systems (GPS), and laser scanners.

[0052] As an example and not a limitation, in the embodiments of the present application, the terminal device may also be a wearable device. Wearable devices may also be referred to as wearable smart devices or smart wearable devices, etc., which are a general term for wearable devices that are intelligently designed and developed using wearable technology for daily wear, such as glasses, gloves, watches, clothing, and shoes. A wearable device is a portable device that is worn directly on the body or integrated into the user's clothes or accessories. Wearable devices are not only hardware devices, but also achieve powerful functions through software support, data interaction, and cloud interaction. Broadly speaking, wearable smart devices include those that are fully functional, large in size, and can achieve complete or partial functions without relying on smartphones, such as smart watches or smart glasses, etc., as well as those that only focus on a certain type of application function and need to be used in conjunction with other devices such as smartphones, such as various smart bracelets, smart helmets, and smart jewelry for vital sign monitoring.

[0053] The various terminal devices introduced above, if located on a vehicle (eg, placed in or installed in a vehicle), can be considered as vehicle-mounted terminal devices, which are also called on-board units (OBUs).

[0054] In the embodiment of the present application, the terminal device may also include audio, image acquisition equipment (such as a camera), etc.

[0055] In the embodiment of the present application, the terminal device may further include a relay. Alternatively, it can be understood that anything that can communicate data with a base station can be considered a terminal device.

[0056] In the embodiments of the present application, the device for implementing the function of the terminal device can be a terminal device, or a device capable of supporting the terminal device to implement the function, such as a chip system, which can be installed in the terminal device. In the embodiments of the present application, the chip system can be composed of a chip, or it can include a chip and other discrete devices. In the technical solutions provided in the embodiments of the present application, the technical solutions provided in the embodiments of the present application are described by taking the terminal device as an example in which the device for implementing the function of the terminal is a terminal device.

[0057] 2) Network equipment, including, for example, access network (AN) equipment (also known as access nodes), such as base stations (e.g., access points), which can refer to equipment in an access network that communicates with wireless terminal devices over the air interface through one or more cells, or, for example, a network device in vehicle-to-everything (V2X) technology is a road side unit (RSU). The base station can be used to convert received air frames to and from IP packets, acting as a router between the terminal device and the rest of the access network, where the rest of the access network may include an IP network. The RSU can be a fixed infrastructure entity that supports V2X applications and can exchange messages with other entities that support V2X applications. The network equipment can also coordinate the attribute management of the air interface. For example, the network device may include an evolved base station (NodeB or eNB or e-NodeB, evolutionary Node B) in a long term evolution (LTE) system or long term evolution-advanced (LTE-A), or may also include a next generation node B (gNB) in a fifth generation mobile communication technology (5G) NR system (also referred to as an NR system) or may also include a centralized unit (CU) and a distributed unit (DU) in a cloud radio access network (Cloud RAN) system, but the embodiments of the present application are not limited thereto.

[0058] The network device may further include a core network (CN) device, which may include an access management node, an intermediate session node, and a session node. For example, the access management node may include an access and mobility management function (AMF) network element, the session node may include a session management function (SMF) network element, and the intermediate session node may include an intermediate session management function (I-SMF) or a visited session management function (V-SMF).

[0059] 3) EPS bearers are channels for forwarding service data between terminal devices and the packet data network (PDN). EPS bearers are configured with corresponding quality of service (QoS) parameters and packet filters to provide different QoS guarantees for packets corresponding to different service data flows, enabling more refined QoS control.

[0060] A terminal device can have a maximum of 11 or 15 EPS bearers. In an EPS network, to distinguish multiple EPS bearers of the same terminal device, an EBI can be used to uniquely identify an EPS bearer of the terminal device.

[0061] Each EPS bearer is associated with a QoS class identifier (QCI) and an allocation and retention priority (ARP). Different EPS bearers are configured with different QCI+ARP combinations. The QCI indicates the priority for data processing and forwarding, while the ARP indicates the priority for resource allocation and retention.

[0062] 4) QoS flows: Data flows with QoS features. QoS flow features include, but are not limited to, classification, marking, traffic conditioning, congestion management, and / or congestion avoidance. QoS flows are configured with corresponding QoS parameters and packet filters to provide different QoS guarantees for packets corresponding to different service data flows, enabling more refined QoS control.

[0063] A terminal device can have up to 15 packet data unit (PDU) sessions, and each PDU session can have 64 QoS flows. In 5G networks, to distinguish the QoS flows of a PDU session on the same terminal device, a QoS flow identity (QFI) can be used to uniquely identify the QoS flow of the PDU session.

[0064] In this application, "and / or" describes the relationship between associated objects, indicating that three possible relationships exist. For example, "A and / or B" can represent: A exists alone, A and B exist simultaneously, and B exists alone. The character " / " generally indicates that the associated objects are in an "or" relationship.

[0065] The term "plurality" in this application refers to two or more.

[0066] In addition, it should be understood that, in the description of this application, 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 implying order.

[0067] The technical solutions of the embodiments of the present application can be applied to various communication systems, such as: global system of mobile communication (GSM) system, code division multiple access (CDMA) system, WCDMA system, general packet radio service (GPRS), LTE system, LTE frequency division duplex (FDD) system, LTE time division duplex (TDD), universal mobile telecommunication system (UMTS), worldwide interoperability for microwave access (WiMAX) communication system, Multefire communication system, fixed communication system, 5G system or NR and future sixth generation communication system, etc.

[0068] In order to facilitate understanding of the embodiments of the present application, Figure 1 The network architecture shown illustrates the application scenarios used in the embodiments of the present application, and the network architecture can be applied to the various communication systems mentioned above. Figure 1 The network architecture shown may include terminal equipment, access network equipment, access management nodes, session nodes, user plane function network elements, policy function network elements, and data network (DN). The functions of some of these nodes / network elements are briefly introduced below.

[0069] Terminal devices can access the wireless network through the access network equipment at their current location. Access management nodes are responsible for device registration, security authentication, mobility management, and location management for terminal devices. Session nodes are responsible for establishing, updating, and deleting sessions for terminal devices. User plane functional network elements forward data packets between terminal devices and external data networks. Policy functional network elements control policies such as billing and quality of service for terminal devices. The data network includes application servers that provide application services (such as data and / or voice services) to terminal devices.

[0070] In the 5G network, the access management node can be an AMF network element, the session node can be an SMF network element, the user plane function network element can be a UPF network element, and the policy function network element can be a PCF network element.

[0071] Optionally, the 5G network may further include an intermediate session node, which may be an I-SMF or a V-SMF, etc. When a terminal device establishes different PDU sessions, it may correspond to different intermediate session nodes and session nodes.

[0072] based on Figure 1 In the network architecture shown, the terminal device may switch from the 5G network to the EPS network during mobility. In order to ensure the service experience of the terminal device, the QoS flow of the terminal device can be mapped to the EPS bearer, thereby ensuring that the service of the terminal device is not interrupted after switching from the 5G network to the EPS network. To this end, when the terminal device establishes a QoS flow in the 5G network, the access management node can allocate the EBI corresponding to the QoS flow. Since the number of QoS flows allowed to be established by the terminal device is much larger than the number of EPS bearers, it may result in the access management node having allocated the full-specification EBI to the terminal device when a new application is made for allocation of EBI (that is, the number of EBIs allocated by the access management node to the terminal device reaches the maximum number of EBIs allowed to be allocated by the terminal device). At this time, the access management node may withdraw the allocated EBI and allocate the withdrawn EBI to the newly established QoS flow, see Figure 2 , including the following processes:

[0073] S201: The policy function network element triggers a policy modification.

[0074] S202: Session node 1 receives the policy update and decides that a new QoS flow needs to be established for the terminal device. The new QoS flow is allowed to be switched to the EPS network, and an EBI needs to be allocated for the new QoS flow. Session node 1 triggers the PDU session update process and sends a PDU session update request (Nsmf_PDUSession_Update request) message to intermediate session node 1, which includes an EBI allocation request.

[0075] The session node 1 can be regarded as a session node that the terminal device accesses before switching, such as a session node in a 5G network. The session node 1 participates in the EBI allocation process.

[0076] S203: The intermediate session node 1 sends a communication EBI assignment request (Namf_Communication_EBIAssignment Request) message to the access management node. The message includes an EPS bearer identifier assignment request.

[0077] The intermediate session node 1 can be regarded as an intermediate session node that the terminal device accesses before switching, such as an intermediate session node in a 5G network. The intermediate session node 1 participates in the EBI allocation process.

[0078] S204: The access management node determines that the EBI allocated to a different PDU session (a different PDU session from S202) needs to be withdrawn. The access management node sends a PDU session context update request (Nsmf_PDUSession_UpdateSMContext request) message to the intermediate session node 2, the message including the withdrawn EBI.

[0079] The intermediate session node 2 can be regarded as an intermediate session node accessed before the terminal switches, such as an intermediate session node in a 5G network. The intermediate session node 2 participates in the EBI withdrawal process.

[0080] For example, the access management node may determine that all EBIs of the terminal device have been allocated and therefore need to revoke the allocated EBI. For another example, the access management node may determine that the terminal device has established a PDU session with the same data network name (DNN) but a different session node, and that an EBI has been allocated for the PDU session and therefore need to revoke the allocated EBI.

[0081] S205: The intermediate session node 2 sends an Nsmf_PDUSession_Update request message to the session node 2, where the message includes the withdrawn EBI.

[0082] The session node 2 can be regarded as the session node that the terminal device accesses before switching, such as the session node in the 5G network. The session node 2 participates in the withdrawal process of the EBI.

[0083] S206: Session node 2 replies with a PDU session update response (Nsmf_PDUSession_Update response) message to intermediate session node 2, indicating that the EBI withdrawal is successful.

[0084] S207: The intermediate session node 2 replies with a PDU session context update response (Nsmf_PDUSession_UpdateSMContext response) message to the access management node, indicating that the EBI withdrawal is successful.

[0085] S208: Session node 2 sends an Nsmf_PDUSession_Update request message to intermediate session node 2. The message includes the withdrawn EBI sent to the terminal device and the access node.

[0086] S209: The intermediate session node 2 sends a communication message transfer request (Namf_Communication_N1N2MessageTransfer request) message to the access management node. The message includes the withdrawn EBI sent to the terminal device and the access node.

[0087] S210: The access management node replies with a communication message transfer response (Namf_Communication_N1N2MessageTransfer Response) message to the intermediate session node 2.

[0088] S211: The access management node sends a PDU session modification command message to the terminal device. The message is forwarded by the access node. The message includes the withdrawn EBI sent by the session node 2 to the terminal device.

[0089] S212: The user terminal replies with a PDU Session Modification command ACK message, indicating that the EBI withdrawal is successful.

[0090] S213: The access management node sends an Nsmf_PDUSession_UpdateSMContext request message to the intermediate session node 2, indicating that the EBI withdrawal is successful.

[0091] S214: The intermediate session node 2 replies with an Nsmf_PDUSession_UpdateSMContext response message.

[0092] S215: The intermediate session node 2 replies with an Nsmf_PDUSession_Update response message to the session node 2, indicating that the EBI withdrawal is successful.

[0093] Among them, S204~S215 can be regarded as the withdrawal process of EBI.

[0094] S216: The access management node replies with a communication EBI assignment response (Namf_Communication_EBIAssignmentResponse) message to the intermediate session node 1. The message includes the EBI assigned by the access management node to the QoS flow.

[0095] S217: The intermediate session node 1 replies with an Nsmf_PDUSession_Update response message to the session node 1, which carries the EBI (allocated for the QoS flow).

[0096] S218: Session node 1 sends an Nsmf_PDUSession_Update request message to intermediate session node 1. The message includes the EBI allocated to the QoS flow and sent to the terminal device and the access node.

[0097] S219: The intermediate session node 1 sends a Namf_Communication_N1N2MessageTransfer request message to the access management node. The message includes the EBI allocated to the QoS flow and sent to the terminal device and the access node.

[0098] S220: The access management node replies with a Namf_Communication_N1N2MessageTransfer Response message to the intermediate session node 1.

[0099] S221: The access management node sends a PDU session resource update request (PDU SESSION RESOURCE MODIFYREQUEST) message to the access node. The message includes the EBI allocated to the QoS flow.

[0100] S222: The access node sends a PDU Session Modification command message to the user terminal. The message includes the EBI allocated to the QoS flow.

[0101] S223: The access node replies with a PDU session resource update response (PDU SESSION RESOURCE MODIFYRESPONSE) message to the access management node, indicating that the (EBI allocation) process is successful.

[0102] S224: The access management node sends an Nsmf_PDUSession_UpdateSMContext request message to the intermediate session node 1, notifying the access node side that the (EBI allocation) process is successful.

[0103] S225: The intermediate session node 1 replies with an Nsmf_PDUSession_UpdateSMContext response message.

[0104] S226: The user terminal replies with a PDU Session Modification command ACK message, indicating that the EBI allocation is successful.

[0105] S227: The access management node sends an Nsmf_PDUSession_UpdateSMContext request message to the intermediate session node 1, notifying the user terminal side of the success of the process.

[0106] S228: The intermediate session node 1 replies with an Nsmf_PDUSession_UpdateSMContext response message.

[0107] S229: The intermediate session node 1 replies with an Nsmf_PDUSession_Update response message to the session node 1, indicating that the EBI allocation is successful.

[0108] Among them, S216~S229 can be regarded as the allocation process of EBI.

[0109] It should be noted that there is no necessary order in which the access management node executes steps S204 and S216. For example, the access management node can send S204 Nsmf_PDUSession_UpdateSMContext request message to intermediate session node 2 to trigger the EBI withdrawal process, and at the same time send S216 Namf_Communication_EBIAssignmentResponse message to intermediate session node 1 to trigger the EBI allocation process.

[0110] During both the EBI allocation and EBI withdrawal processes, the session node interacts with the terminal device and access node. This can cause EBI allocation messages to be sent to the terminal device and access node before EBI withdrawal messages. QoS flows with the same EBI may already exist on the terminal device and access node, causing processing anomalies on the terminal device and access node, and impacting the terminal device's service experience.

[0111] Based on this, in order to avoid abnormal processing of terminal devices and access nodes and ensure the service experience of terminal devices, an embodiment of the present application proposes a bearer identifier allocation method. In this method, when the terminal device and the access node determine that there is a QoS flow that has been allocated with the same EBI, they can establish a new QoS flow and determine that the EBI allocation has failed; or when the terminal device and the access node determine that there is a QoS flow that has been allocated with the same EBI, they can establish a new QoS flow and delete the previously allocated EBI; or when the access management node receives a request to allocate an EBI and determines that the EBI needs to be withdrawn, it can wait for the EBI to be withdrawn before performing the EBI allocation process; or when the first session node receives an instruction to allocate an EBI and withdraw the EBI, it can wait for the second timer to expire before performing the EBI allocation process. In this way, it is ensured that the EBI withdrawal process is completed earlier than the EBI allocation process, avoiding the allocation of the same EBI when the EBI that the terminal device and the access node need to withdraw has not been withdrawn, that is, avoiding the same bearer identifier corresponding to different QoS flows, ensuring the accuracy of the processing of the terminal device and the access node, and improving the service experience of the terminal device.

[0112] The bearer identifier allocation method provided in the embodiment of the present application can be applied to Figure 1 In the network architecture shown, the bearer identifier allocation process of the embodiment of the present application is described below.

[0113] It is understood that any message involved in the embodiments of the present application can be an existing message, or a reused existing message, and the name of the message is only used as an example and not as a limitation. In addition, the execution sequence between the steps involved in the embodiments of the present application may not be limited if it does not affect the effect that the scheme can achieve.

[0114] Method 1: When the terminal device and the access node determine that a QoS flow with the same EBI has been allocated, they can establish a new QoS flow and determine that the EBI allocation has failed. Figure 3 , the bearer identity allocation process includes:

[0115] S301: The access management node sends a first EBI associated with a first QoS flow to a first session node, and the first session node receives the first EBI.

[0116] The first session node may be a session node accessed by the first device (including a terminal device and / or an access network device) before switching, such as a session node in a 5G network.

[0117] The first QoS flow is a QoS flow to be established / already established by the first device. The first EBI is an EBI to be allocated to the first QoS flow.

[0118] Optionally, the access management node may withdraw an already allocated EBI and allocate a first EBI to the first QoS flow. The first EBI may be the same as or different from the already allocated EBI.

[0119] In one example, the access management node may directly send the first EBI to the first session node.

[0120] In another example, the access management node may send the first EBI to a first intermediate session node, and the first intermediate session node may send the first EBI to the first session node.

[0121] For example, the message carrying the first EBI may be a Namf_Communication_EBIAssignmentResponse message and / or a Nsmf_PDUSession_Update response message.

[0122] S302: The first session node sends a third request message to the access management node. The access management node receives the third request message. The third request message includes a first PDU session identifier, a first QoS flow identifier corresponding to the first QoS flow, and the first EBI.

[0123] Optionally, the third request message may further include an EPS bearer context, where the EPS bearer context includes QoS parameters of the EPS bearer and / or user plane forwarding channel information associated with the EPS bearer, etc.

[0124] In an example, the first session node may directly send the third request message to the access management node.

[0125] In another example, the first session node may send the third request message to the first intermediate session node, and the first intermediate session node may send the third request message to the access management node.

[0126] For example, the third request message, or the message containing the third request message may be an Nsmf_PDUSession_Update request message, and / or a Namf_Communication_N1N2MessageTransferrequest message.

[0127] S303: The access management node sends a first request message to the first device, and the first device receives the first request message. The first request message is used to establish or update a first QoS flow. The first request message includes the first PDU session identifier, the first QoS flow identifier and the first EBI.

[0128] The first device includes a terminal device and / or an access network device.

[0129] For example, the first device includes an access network device, and the first request message, or the message including the first request message, may be a PDU SESSION RESOURCE MODIFY REQUEST message.

[0130] For another example, the first device includes a terminal device, and the first request message, or the message containing the first request message, may be a PDU Session Modification command message.

[0131] S304: If a second QoS flow has been established on the first device, and the second EBI corresponding to the second QoS flow is the same as the first EBI, the first device sends a first response message to the access management node, and the access management node receives the first response message, where the first response message is used to indicate that the allocation of the first EBI failed.

[0132] Generally, the second EBI corresponding to the second QoS flow is different from the EBI of the first QoS flow. If they are the same, it may cause processing abnormalities on the first device. The second QoS flow and the first QoS flow may belong to the same PDU session, or may belong to different PDU sessions.

[0133] Optionally, the first device may also determine that the second PDU session identifier associated with the second EBI is different from the first PDU session identifier associated with the first EBI. If the PDU session identifiers are different, the first device sends a first response message. Generally, when the second QoS flow and the first QoS flow belong to different PDU sessions, it is easy for the bearer identifier allocation process to be later than the bearer identifier withdrawal process, because different PDU sessions are established on different session nodes, one session node executes the bearer identifier allocation process, and the other session node executes the bearer identifier withdrawal process. When the second QoS flow and the first QoS flow belong to the same PDU session, the probability of the bearer identifier allocation process being later than the bearer identifier withdrawal process is small, because the bearer identifier allocation process and the bearer identifier withdrawal process are executed by the same session node, and the session node can ensure that the bearer identifier withdrawal process is earlier than or simultaneous with the bearer identifier allocation process.

[0134] In an example, the first device may directly send the first response message to the access management node.

[0135] In another example, when the first device is a terminal device, the first response message can be sent to the access network device, and the access network device sends the first response message to the access management node, that is, the first response message can be transparently transmitted to the access management node through the access network device.

[0136] For example, the first response message may be a PDU SESSION RESOURCE MODIFY RESPONSE message, or a PDU Session Modification command ACK message.

[0137] Optionally, the first device establishes or updates the first QoS flow, and the first response message is further used to indicate that the first QoS flow is successfully established or updated. That is, the first device may only establish or update the first QoS flow without accepting allocation of EBI for the first QoS flow.

[0138] S305: The access management node sends a third response message to the first session node, where the third response message is used to indicate that the first EBI allocation fails.

[0139] In an example, the access management node may directly send the third response message to the first session node.

[0140] In another example, the access management node may send the third response message to the first intermediate session node, and the first intermediate session node may send the third response message to the first session node.

[0141] For example, the third response message, or the message including the third response message may be an Nsmf_PDUSession_UpdateSMContext request message, and / or an Nsmf_PDUSession_Update response message.

[0142] Optionally, the third response message is also used to indicate that the first QoS flow is established or updated successfully.

[0143] In one possible implementation, the first device receives a second request message from the access management node, the second request message being used to withdraw the second EBI corresponding to the second QoS flow, the second request message including a second PDU session identifier, a second QoS flow identifier corresponding to the second QoS flow, and the second EBI; the first device deletes the second EBI; and the first device sends a second response message to the access management node, the second response message being used to indicate successful withdrawal of the second EBI. After the bearer identifier withdrawal process arrives later than the bearer identifier allocation process, the first device normally withdraws the second EBI. This further avoids conflicts caused by the same EBI for different QoS flows.

[0144] The access management node receives a second response message from the first device, where the second response message is used to indicate that the second EBI corresponding to the second QoS flow is successfully withdrawn, and the second QoS flow is a QoS flow that has been established on the first device; the access management node may also send a fourth response message to the second session node, where the fourth response message is used to indicate that the second EBI is successfully withdrawn.

[0145] Before receiving the second response information from the first device, the access management node may also send a second request message to notify the first device to withdraw the second EBI based on the indication information of withdrawing the second EBI contained in the fourth request message from the second session node.

[0146] For example, the second request message may be a PDU SESSION RESOURCE MODIFY REQUEST message and / or a PDU Session Modification command message. The second response message may be a PDU SESSION RESOURCE MODIFY RESPONSE message and / or a PDU Session Modification command ACK message. The fourth request message may be an Nsmf_PDUSession_Update request message and / or a Namf_Communication_N1N2MessageTransfer request message. The fourth response message may be an Nsmf_PDUSession_UpdateSMContext request message and / or an Nsmf_PDUSession_Update response message.

[0147] Since the first device did not allocate an EBI for the first QoS flow in S304, the first session node may further notify the access management node to withdraw the first EBI corresponding to the first QoS flow; or the first session node may further send the third request message to the access management node again to make multiple attempts to ensure that the first EBI is successfully allocated to the first QoS flow. The first session node may execute the EBI allocation process and retry the EBI allocation, or the first session node may carry the third request message in the signaling process, that is, the first device may piggyback the EBI allocation process in the signaling process.

[0148] The following describes the bearer identifier allocation process shown in the first method with a specific embodiment. Figure 4 As shown, the following process is included:

[0149] S401: The policy function network element triggers a policy modification.

[0150] Optionally, in addition to the triggering method shown in S401, the bearer identifier allocation process may also include the terminal device requesting PDU session establishment (creating a new QoS flow), the terminal device requesting PDU session update (creating or updating a QoS flow), the network device triggering PDU session update (creating or updating a QoS flow), and / or service request process, etc.

[0151] S402: Session node 1 receives the policy update and decides that a new QoS flow needs to be established for the terminal device. The new QoS flow is allowed to be handed over to the EPS network, and an EBI needs to be allocated for the new QoS flow. Session node 1 triggers the PDU session update process and sends an Nsmf_PDUSession_Update request message to intermediate session node 1, which contains an EBI allocation request.

[0152] The session node 1 is Figure 3 The first session node shown in .

[0153] Optionally, in S402, session node 1 determines that the ARP corresponding to the QoS flow established by the terminal device needs to be updated, triggering a quality of service update. The Nsmf_PDUSession_Update request message may carry the updated ARP. If the current QoS flow has been allocated EBI, the message may include EBI update information.

[0154] The EBI update information may include the EBI corresponding to the QoS flow and the updated ARP.

[0155] S403: The intermediate session node 1 sends a Namf_Communication_EBIAssignmentRequest message to the access management node. The message includes an EPS bearer identity assignment request.

[0156] Optionally, after the intermediate session node 1 receives the Nsmf_PDUSession_Update request message, if it is determined that the user plane channel between the user plane function network element corresponding to the PDU session associated with the QoS flow and the access node has been released, and the Nsmf_PDUSession_Update request message contains EBI update information, the intermediate session node 1 is triggered to execute S403, and the intermediate session node 1 sends a Namf_Communication_EBIAssignment Request message to the access management node, which contains EBI update information.

[0157] If the access management node allocates EBI based on ARP, the ARP update will affect the priority of EBI withdrawal. Therefore, after the ARP is updated, the session node 1 may also notify the access management node to update the stored ARP-EBI correspondence. The access management node updates the stored ARP-EBI correspondence. That is, the access management node uses the EBI-ARP correspondence corresponding to the QoS flow in the EBI update information to replace the ARP in the locally stored EBI-ARP correspondence.

[0158] S404: The access management node sends a Namf_Communication_EBIAssignment Response message to intermediate session node 1, which contains the EBI assigned by the access management node to the QoS flow. The access management node can assign an EBI to the QoS flow based on the EPS bearer identifier assignment request included in step S403 or reallocate an EBI to the QoS flow based on the included EBI update information.

[0159] S405: The intermediate session node 1 replies with an Nsmf_PDUSession_Update response message to the session node 1, where the message carries the allocated EBI.

[0160] S406: Session node 1 sends an Nsmf_PDUSession_Update request message to intermediate session node 1. The message includes the PDU session identifier, the QoS flow identifier, the EBI allocated to the QoS flow, and the EPS bearer context.

[0161] S407: The intermediate session node 1 sends a Namf_Communication_N1N2MessageTransfer request message to the access management node. The message includes the PDU session identifier, the QoS flow identifier, the EBI allocated to the QoS flow, and the EPS bearer context.

[0162] S408: The access management node replies with a Namf_Communication_N1N2MessageTransfer Response message to the intermediate session node 1.

[0163] S409: The access management node sends a PDU SESSION RESOURCE MODIFY REQUEST message to the access node. The message includes a PDU session identifier, a QoS flow identifier, and an EBI allocated to the QoS flow.

[0164] S410: The access node sends a PDU Session Modification command message to the user terminal. The message includes a PDU session identifier, a QoS flow identifier, an EBI allocated to the QoS flow, and an EPS bearer context.

[0165] exist Figure 4 The access node is a base station.

[0166] S411: The access node confirms that the same EBI already exists for the terminal device, and the PDU session identifier in S409 is different from the PDU session identifier corresponding to the existing EBI. The access node establishes or updates the QoS flow requested in S409 and replies with a PDU SESSION RESOURCE MODIFY RESPONSE message to the access management node, indicating that the QoS flow establishment or update is successful and the EBI allocation fails.

[0167] S412: The access management node sends an Nsmf_PDUSession_UpdateSMContext request message to the intermediate session node 1, indicating that the QoS flow on the access node side is established or updated successfully, and the EBI allocation fails.

[0168] S413: The intermediate session node 1 replies with an Nsmf_PDUSession_UpdateSMContext response message.

[0169] S414: The terminal device confirms that the same EBI already exists for the terminal device, and the PDU session identifier in S410 is different from the PDU session identifier corresponding to the existing EBI. The terminal device establishes or updates the QoS flow requested in S410 and replies with a PDU Session Modification command ACK message to the access management node, indicating that the QoS flow establishment or update is successful and the EBI allocation fails.

[0170] The message is transparently transmitted through the access node.

[0171] S415: The access management node sends an Nsmf_PDUSession_UpdateSMContext request message to the intermediate session node 1, indicating that the QoS flow on the terminal device side is successfully established or updated, and the EBI allocation fails.

[0172] S416: The intermediate session node 1 replies with an Nsmf_PDUSession_UpdateSMContext response message.

[0173] S417: The intermediate session node 1 replies with an Nsmf_PDUSession_Update response message to the session node 1, indicating that the QoS flow on the terminal device side and / or the access node side is successfully established or updated, and the EBI allocation fails.

[0174] S418 to S424 can refer to the above-mentioned S204 to S210.

[0175] S425: The access management node sends a PDU SESSION RESOURCE MODIFY REQUEST message to the access node. The message includes the withdrawn EBI sent by session node 2 to the access node.

[0176] S426: The access node sends a PDU Session Modification command message to the user terminal. The message is forwarded by the access node and includes the withdrawn EBI sent by session node 2 to the terminal device.

[0177] S427: The access node deletes the locally stored EBI and replies with a PDU SESSION RESOURCE MODIFYRESPONSE message to the access management node, indicating that the EBI withdrawal is successful.

[0178] S428: The access management node sends an Nsmf_PDUSession_UpdateSMContext request message to the intermediate session node 2, indicating that the EBI withdrawal is successful.

[0179] S429: The intermediate session node 2 replies with an Nsmf_PDUSession_UpdateSMContext response message.

[0180] S430: The terminal device deletes the locally stored EBI and the corresponding EPS bearer context, and replies with a PDUSession Modification command ACK message, indicating that the EBI withdrawal is successful.

[0181] S431: The access management node sends an Nsmf_PDUSession_UpdateSMContext request message to the intermediate session node 2, indicating that the EBI withdrawal is successful.

[0182] S432: The intermediate session node 2 replies with an Nsmf_PDUSession_UpdateSMContext response message.

[0183] S433: The intermediate session node 2 replies with an Nsmf_PDUSession_Update response message to the session node 2, indicating that the EBI withdrawal is successful.

[0184] It should be noted that there is no necessary order in which the access management node executes steps S404 and S418. For example, the access management node can send an S418 Nsmf_PDUSession_UpdateSMContext request message to the intermediate session node 2 to trigger the EBI withdrawal process, and at the same time send an S404 Namf_Communication_EBIAssignmentResponse message to the intermediate session node 1 to trigger the EBI allocation process.

[0185] Next, we will introduce a Figure 3 、 Figure 4 Corresponding bearer identity allocation process:

[0186] A first device receives a first request message from an access management node, the first request message being used to establish or update a first QoS flow, the first request message including a first PDU session identifier, a first QoS flow identifier corresponding to the first QoS flow, and a first EBI, and the first device including a terminal device and / or an access network device. The first request message may be the first request message shown in S303, or may be the PDU SESSION RESOURCE MODIFY REQUEST message shown in S409, or may be the PDU Session Modification command message shown in S410.

[0187] If a second QoS flow has been established on the first device, and the second EBI corresponding to the second QoS flow is the same as the first EBI, the first device sends a first response message to the access management node, where the first response message is used to indicate that the allocation of the first EBI has failed. The first response message may be the first response message shown in S304, or may be the PDU SESSION RESOURCE MODIFY RESPONSE message shown in S411, or may be the PDUSession Modification command ACK message shown in S414.

[0188] Furthermore, the first device may also establish or update the first QoS flow, and the first response message is further used to indicate that the first QoS flow is successfully established or updated.

[0189] Furthermore, the first device may also determine that the second PDU session identifier associated with the second EBI is different from the first PDU session identifier associated with the first EBI.

[0190] Furthermore, the first device may also receive a second request message from the access management node, where the second request message is used to withdraw the second EBI corresponding to the second QoS flow, and the second request message includes a second PDU session identifier, a second QoS flow identifier corresponding to the second QoS flow, and the second EBI. The second request message may be the second request message shown in S305, or may be the PDU SESSION RESOURCE MODIFYRESPONSE message shown in S425, or may be the PDU Session Modification command ACK message shown in S426.

[0191] The first device deletes the second EBI.

[0192] The first device sends a second response message to the access management node, where the second response message is used to indicate that the second EBI withdrawal is successful. The second response message may be the second response message shown in S305, or may be the PDU SESSION RESOURCE MODIFY RESPONSE message shown in S427, or may be the PDUSession Modification command ACK message shown in S430.

[0193] Next, we will introduce a bearer identity allocation process:

[0194] The first session node receives a first EBI associated with a first QoS flow from the access management node.

[0195] The first session node sends a third request message to the access management node, where the third request message includes the first PDU session identifier, the first QoS flow identifier corresponding to the first QoS flow, and the first EBI. The third request message may be the third request message shown in S302, or may be the Nsmf_PDUSession_Updaterequest message shown in S406, or may be the Namf_Communication_N1N2MessageTransferrequest message shown in S407.

[0196] The first session node receives a third response message from the access management node, where the third response message indicates that the first EBI allocation failed. The third response message may be the third response message shown in S305, or may be the Nsmf_PDUSession_UpdateSMContext request message shown in S412 or S415, or may be the Nsmf_PDUSession_Update response message shown in S417.

[0197] Furthermore, the third response message is also used to indicate that the first QoS flow is established or updated successfully.

[0198] Furthermore, the first session node may also notify the access management node to withdraw the first EBI corresponding to the first QoS flow; or the first session node may also send the third request message to the access management node again.

[0199] Next, we will introduce a bearer identity allocation process:

[0200] The access management node sends a first EBI associated with the first QoS flow to the first session node.

[0201] The access management node receives a third request message from the first session node, where the third request message includes the first PDU session identifier, the first QoS flow identifier corresponding to the first QoS flow, and the first EBI. The third request message may be the third request message shown in S302, or may be the Nsmf_PDUSession_Update request message shown in S406, or may be the Namf_Communication_N1N2MessageTransferrequest message shown in S407.

[0202] The access management node sends a first request message to a first device, where the first request message is used to establish or update a first QoS flow, and the first request message includes the first PDU session identifier, the first QoS flow identifier, and the first EBI. The first device includes a terminal device and / or an access network device. The first request message may be the first request message shown in S303, or may be the PDU SESSION RESOURCE MODIFY REQUEST message shown in S409, or may be the PDU Session Modification command message shown in S410.

[0203] The access management node receives a first response message from the first device, where the first response message indicates that the first EBI allocation failed. The first response message may be the first response message shown in S304, or may be the PDU SESSION RESOURCE MODIFY RESPONSE message shown in S411, or may be the PDU Session Modification command ACK message shown in S414.

[0204] The access management node sends a third response message to the first session node, where the third response message is used to indicate that the first EBI allocation failed. The third response message may be the third response message shown in S305, or may be the Nsmf_PDUSession_UpdateSMContext request message shown in S412 or S415, or may be the Nsmf_PDUSession_Update response message shown in S417.

[0205] Furthermore, the first response message is further used to indicate that the first QoS flow is successfully established or updated; and / or the third response message is further used to indicate that the first QoS flow is successfully established or updated.

[0206] Furthermore, the access management node may also receive a second response message from the first device, where the second response message is used to indicate that the second EBI corresponding to the second QoS flow has been successfully withdrawn, where the second QoS flow is a QoS flow already established on the first device. The second response message may be the second response message shown in S305, or may be the PDU SESSION RESOURCE MODIFY RESPONSE message shown in S427, or may be the PDUSession Modification command ACK message shown in S430.

[0207] The access management node sends a fourth response message to the second session node, the fourth response message being used to indicate that the second EBI withdrawal is successful. The fourth response message may be the Nsmf_PDUSession_UpdateSMContext request message shown in S428 or S431, or the Nsmf_PDUSession_Updateresponse message shown in S433.

[0208] Furthermore, before receiving the second response information from the first device, the access management node may also send a second request message to notify the first device to withdraw the second EBI based on the instruction information for withdrawing the second EBI contained in the fourth request message from the second session node. The fourth request message may be the Nsmf_PDUSession_Update request message shown in S422 or the Namf_Communication_N1N2MessageTransfer request message shown in S423. The second request message may be the PDU SESSIONRESOURCE MODIFY REQUEST message shown in S425, or may be the PDU Session Modificationcommand message shown in S426.

[0209] In this embodiment, when an EBI already exists, the terminal device or access network device accepts the operation of creating or updating a QoS flow, but refuses to accept the assigned EBI, ensuring that the QoS flow can be established or updated. This also avoids EPS bearer processing anomalies on the terminal device and access network device, and also prevents service continuity from being affected.

[0210] In the second method, when the terminal device and the access node determine that there is a QoS flow that has been allocated the same EBI, they can create or update a new QoS flow and delete the previously allocated EBI. Figure 5 , the bearer identity allocation process includes:

[0211] S501: The access management node sends a second request message to the second session node, where the second request message is used to instruct the allocation of a first EBI for a first PDU session and the withdrawal of a second EBI for a second PDU session.

[0212] The second request message may be an Nsmf_PDUSession_UpdateSMContext request message and / or an Nsmf_PDUSession_Update request message.

[0213] After receiving the second request message, the second session node may not perform the withdrawal process (such as Figure 4 S422-S433 shown in ).

[0214] S502: The access management node sends a first EBI associated with a first QoS flow identifier to a first session node, and the first session node receives the first EBI.

[0215] The implementation process of S502 is similar to that of S301 above, and will not be described in detail here.

[0216] S503: The first session node sends a third request message to the access management node, and the access management node receives the third request message. The third request message is used to establish or update a first QoS flow. The third request message includes a first PDU session identifier, a first QoS flow identifier corresponding to the first QoS flow, and a first EBI.

[0217] The implementation process of S503 is similar to that of the above S302 and will not be described in detail here.

[0218] S504: The access management node sends a first request message to the first device, and the first device receives the first request message. The first request message is used to establish or update a first QoS flow. The first request message includes a first PDU session identifier, a first QoS flow identifier corresponding to the first QoS flow, and a first EBI. The first device includes a terminal device and / or an access network device.

[0219] The implementation process of S504 is similar to that of the above S303 and will not be described in detail here.

[0220] S505: If a second QoS flow has been established on the first device, and a second EBI corresponding to the second QoS flow is the same as the first EBI, the first device deletes the second EBI.

[0221] Optionally, the first device may also determine that the second PDU session identifier associated with the second EBI is different from the first PDU session identifier associated with the first EBI.

[0222] S506: The first device sends a first response message to the access management node, and the access management node receives the first response message, where the first response message is used to indicate that the first EBI allocation is successful.

[0223] Optionally, the first device may also establish or update the first QoS flow, and the first response message is further used to indicate that the first QoS flow is successfully established or updated.

[0224] The first response message may be a PDU SESSION RESOURCE MODIFY RESPONSE message, or a PDUSession Modification command ACK message.

[0225] The following describes the bearer identifier allocation process shown in the second method with a specific embodiment. Figure 6 As shown, the following process is included:

[0226] S601 to S610 may refer to the above-mentioned S401 to S410.

[0227] S611: The access node confirms that the terminal device already has the same EBI, and the PDU session identifier in S609 is different from the PDU session identifier corresponding to the existing EBI, and the access node deletes the existing EBI.

[0228] The access node establishes or updates the QoS flow requested in S609, stores the mapping relationship between the QoS flow and the EBI, and replies a PDU SESSION RESOURCE MODIFY RESPONSE message to the access management node, indicating that the process is successful.

[0229] In this approach, the access node can proactively delete existing EBIs without having to wait for the access management node to trigger the EBI withdrawal process. This ensures that when the allocated EBI reaches the access node, the EBI to be withdrawn has already been deleted, avoiding conflicts when different QoS flows correspond to the same EBI.

[0230] S612: The access management node sends an Nsmf_PDUSession_UpdateSMContext request message to the intermediate session node 1, indicating that the process on the access node side is successful.

[0231] S613: The intermediate session node 1 replies with an Nsmf_PDUSession_UpdateSMContext response message.

[0232] S614: The terminal device confirms that the same EBI already exists in the terminal device, and the PDU session identifier in S610 is different from the PDU session identifier corresponding to the existing EBI, and the terminal device deletes the existing EBI.

[0233] The terminal establishes or updates the QoS flow requested in S610, stores the mapping relationship between the QoS flow and the EBI, and replies a PDU Session Modification command ACK message to the access management node, indicating that the process is successful.

[0234] S615: The access management node sends an Nsmf_PDUSession_UpdateSMContext request message to the intermediate session node 1, indicating that the process on the terminal device side is successful.

[0235] S616: The intermediate session node 1 replies with an Nsmf_PDUSession_UpdateSMContext response message.

[0236] S617: The intermediate session node 1 replies with an Nsmf_PDUSession_Update response message to the session node 1, indicating that the process on the terminal device side and / or the access node side is successful.

[0237] S618: The access management node determines that the EBI allocated to a different PDU session (a different PDU session from that in S602) needs to be withdrawn. The access management node sends an Nsmf_PDUSession_UpdateSMContext request message to the intermediate session node 2, which includes the withdrawn EBI and instructions for allocating a new EBI and withdrawing the allocated EBI.

[0238] S619: Intermediate session node 2 sends an Nsmf_PDUSession_Update request message to session node 2. The message includes the withdrawn EBI and the instruction information for allocating a new EBI and withdrawing the allocated EBI. After receiving the message, session node 2 determines not to perform the withdrawal process (e.g., Figure 4 S422-S433 shown in ).

[0239] S620~S621 can refer to the above S420~S421.

[0240] It should be noted that there is no necessary order in which the access management node executes steps S604 and S618. For example, the access management node can send an S618 Nsmf_PDUSession_UpdateSMContext request message to the intermediate session node 2 to notify the withdrawal of the EBI, and at the same time send an S604 Namf_Communication_EBIAssignment Response message to the intermediate session node 1 to trigger the EBI allocation process.

[0241] Next, we will introduce a Figure 5 、 Figure 6 Corresponding bearer identity allocation process:

[0242] A first device receives a first request message from an access management node, the first request message being used to establish or update a first QoS flow, the first request message including a first PDU session identifier, a first QoS flow identifier corresponding to the first QoS flow, and a first EBI, and the first device including a terminal device and / or an access network device. The first request message may be the first request message shown in S504, or may be the PDU SESSION RESOURCE MODIFY REQUEST message shown in S609, or may be the PDU Session Modification command message shown in S610.

[0243] If a second QoS flow has been established on the first device, and a second EBI corresponding to the second QoS flow is the same as the first EBI, the first device deletes the second EBI.

[0244] The first device sends a first response message to the access management node, where the first response message is used to indicate that the first EBI allocation is successful. The first response message may be the first response message shown in S506, or may be the PDU SESSION RESOURCE MODIFY RESPONSE message shown in S611, or may be the PDUSession Modification command ACK message shown in S614.

[0245] Furthermore, the first device may also establish or update the first QoS flow, and the first response message is further used to indicate that the first QoS flow is successfully established or updated.

[0246] Furthermore, the first device may also determine that the second PDU session identifier associated with the second EBI is different from the first PDU session identifier associated with the first EBI.

[0247] Next, we will introduce a bearer identity allocation process:

[0248] The access management node sends a second request message to the second session node, where the second request message is used to indicate the allocation of the first EBI of the first PDU session and the withdrawal of the second EBI of the second PDU session. The second request message may be the second request message shown in S501, or may be the Nsmf_PDUSession_UpdateSMContext request message shown in S618, or may be the Nsmf_PDUSession_Update request message shown in S619.

[0249] The access management node sends a first EBI associated with a first quality of service (QoS) flow identifier to the first session node.

[0250] The access management node receives a third request message from the first session node, where the third request message is used to establish or update a first QoS flow, and the third request message includes a first PDU session identifier, a first QoS flow identifier corresponding to the first QoS flow, and a first EBI. The third request message may be the third request message shown in S503, or may be the Nsmf_PDUSession_Update request message shown in S606, or may be the Namf_Communication_N1N2MessageTransfer request message shown in S607.

[0251] The access management node sends a first request message to a first device, where the first request message is used to establish or update a first quality of service (QoS) flow, and the first request message includes a first PDU session identifier, a first QoS flow identifier corresponding to the first QoS flow, and a first EBI. The first device includes a terminal device and / or an access network device. The first request message may be the first request message shown in S504, or may be the PDU SESSION RESOURCEMODIFY REQUEST message shown in S609, or may be the PDU Session Modification command message shown in S610.

[0252] The access management node receives a first response message, where the first response message is used to indicate that the first EBI allocation is successful. The first response message may be the first response message shown in S506, or may be the PDUSESSION RESOURCE MODIFY RESPONSE message shown in S611, or may be the PDU Session Modification command ACK message shown in S614.

[0253] Furthermore, the first response message is also used to indicate that the first QoS flow is established or updated successfully.

[0254] In this embodiment of the present application, when an EBI already exists, the terminal device or access network device deletes the existing EBI, accepts the creation or update operation for the QoS flow in the current process, and the allocated EBI, thereby successfully completing the EBI allocation process. The second session node, based on the access management node's notification of the allocation of the first EBI for the first PDU session and the withdrawal of the second EBI for the second PDU session, does not execute the EBI allocation process. This also avoids EPS bearer processing anomalies on the terminal device and access network device, and prevents impacts on service continuity.

[0255] Method 3: When the access management node receives a request to allocate EBI and determines that EBI needs to be withdrawn, it can wait until the EBI withdrawal is completed before performing the EBI allocation process. Figure 7 , the bearer identity allocation process includes:

[0256] S701: A first session node sends a first request message to an access management node, and the access management node receives the first request message, where the first request message is used to request allocation of an EBI for the first QoS flow.

[0257] Optionally, the first session node can be triggered to send the first request message by the following methods: the policy function network element triggers a policy update, the terminal device requests a PDU to be established (a new QoS flow), the terminal device requests a PDU session update (a new or updated QoS flow), the network device triggers a PDU session update (a new or updated QoS flow), and / or a service request process, etc.

[0258] In one example, the first session node may directly send the first request message to the access management node.

[0259] In another example, the first session node may send the first request message to a first intermediate session node, which sends the first request message to the access management node.

[0260] The first request message, or the message containing the first request message may be an Nsmf_PDUSession_Update request message, and / or a Namf_Communication_EBIAssignment Request.

[0261] S702: The access management node sends a second request message to the second session node, and the second session node receives the second request message, where the second request message is used to withdraw a first EBI of a second QoS flow, where the second QoS flow belongs to a second PDU session.

[0262] For example, the access management node may determine that all EBIs of the terminal device have been allocated and therefore need to revoke the allocated EBI. For another example, the access management node may determine that the terminal device has established a PDU session with the same data network name (DNN) but a different session node, and that an EBI has been allocated for the PDU session and therefore need to revoke the allocated EBI.

[0263] In one example, the access management node sends the second request message directly to the second session node.

[0264] In another example, the access management node sends a second request message to a second intermediate session node, and the second intermediate session node sends the second request message to the second session node.

[0265] The second request message or the message including the second request message may be an Nsmf_PDUSession_UpdateSMContext request message and / or an Nsmf_PDUSession_Update request message.

[0266] S703: The second session node sends a first response message to the access management node, and the access management node receives the first response message, where the first response message is used to notify that the first EBI is successfully withdrawn.

[0267] In one example, the second session node may directly send the first response message to the access management node.

[0268] In another example, the second session node may send the first response message to a second intermediate session node, and the second intermediate session node may send the first response message to the access management node.

[0269] The first response message or the message including the first response message may be an Nsmf_PDUSession_Update response message and / or an Nsmf_PDUSession_UpdateSMContext response message.

[0270] S704: After the access management node waits for the first EBI to be withdrawn, the access management node sends a second response message to the first session node. The first session node receives the second response message, where the second response message includes the first EBI associated with the first QoS flow.

[0271] In one example, the access management node directly sends a second response message to the first session node.

[0272] In another example, the access management node sends a second response message to the first intermediate session node, and the first intermediate session node sends the second response message to the first session node.

[0273] The second response message or the message including the second corresponding message may be a Namf_Communication_EBIAssignment Response message and / or a Nsmf_PDUSession_Update response message.

[0274] When the access management node waits for the first EBI withdrawal to be completed, the access management node may start a first timer after receiving the first response message, and when the first timer times out, the access management node determines that the first EBI withdrawal is completed; or the access management node may receive a third response message from a first device, the first device includes a terminal device and / or an access network device, the third response message includes the second PDU session identifier, and the access management node determines that the first EBI withdrawal is completed based on the third response message.

[0275] The following describes the bearer identifier allocation process shown in the third method with a specific embodiment. Figure 8 As shown, the following process is included:

[0276] S801 to S833 may refer to the above-mentioned S401 to S433.

[0277] It is worth noting that in the third method, after S818 or S821, the access management node starts a timer, and triggers S804 when the timer times out.

[0278] If the timer has not expired, and a response message is received from the terminal device and / or access node, the access management node triggers S804. If the response message from the terminal device and / or access node includes the second PDU session identifier, the access management node deems it a successful EBI withdrawal response of S827 or S830, i.e., the withdrawal of the first EBI is complete.

[0279] Next, we will introduce a Figure 7 、 Figure 8 Corresponding bearer identity allocation process:

[0280] The access management node receives a first request message from the first session node, where the first request message is used to request allocation of an EBI for the first QoS flow. The first request message is the first request message shown in S701, or the Nsmf_PDUSession_Update request message in S802, or the Namf_Communication_EBIAssignment Request message in S803.

[0281] The access management node sends a second request message to the second session node, where the second request message is used to withdraw the first EBI of a second QoS flow, where the second QoS flow belongs to a second PDU session. The second request message is the second request message shown in S702, or the Nsmf_PDUSession_UpdateSMContext request message in S818, or the Nsmf_PDUSession_Update request message in S819.

[0282] The access management node receives a first response message from the second session node, where the first response message is used to notify that the first EBI withdrawal is successful. The first response message is the first response message shown in S703, or the Nsmf_PDUSession_Update response message in S820, or the Nsmf_PDUSession_UpdateSMContext response message in S821.

[0283] After the access management node waits for the first EBI to be withdrawn, the access management node sends a second response message to the first session node, where the second response message includes the first EBI associated with the first QoS flow. The second response message is the second response message shown in S704, or the Namf_Communication_EBIAssignment Response message in S804, or the Nsmf_PDUSession_Updateresponse message in S805.

[0284] After receiving the first response message, the access management node starts a first timer. When the first timer times out, the access management node determines that the withdrawal of the first EBI is complete. Alternatively, the access management node receives a third response message from a first device, where the first device includes a terminal device and / or an access network device, and the third response message includes the second PDU session identifier. The access management node determines that the withdrawal of the first EBI is complete based on the third response message. The third response message is a PDU SESSION RESOURCE MODIFY RESPONSE message in S827 or a PDU Session Modification command ACK message in S830.

[0285] In an embodiment of the present application, when EBI already exists, the access management node delays triggering the EPS bearer allocation process to avoid the EPS bearer allocation process being earlier than the EPS bearer withdrawal process, which can avoid abnormal processing of EPS bearers of terminal devices and access network devices, and can also avoid affecting business continuity.

[0286] Mode 4: When the session node receives the instruction to allocate EBI and withdraw EBI, it can wait for the second timer to time out before performing the EBI allocation process. Figure 9 , the bearer identity allocation process includes:

[0287] S901: A first session node sends a first request message to an access management node, and the access management node receives the first request message, where the first request message is used to request allocation of an EBI for a first quality of service (QoS) flow.

[0288] The implementation process of S901 is similar to that of S701 and will not be described in detail here.

[0289] S902: The access management node sends a third request message to the second session node, and the second session node receives the third request message, where the third request message is used to withdraw the first EBI of the second QoS flow.

[0290] The implementation process of S902 is similar to that of S702 and will not be described in detail here.

[0291] S903: The access management node sends a first response message to the first session node. The first session node receives the first response message. The first response message includes the first EBI associated with the first QoS flow and indication information for withdrawing the EBI.

[0292] In one example, the access management device directly sends a first response message to the first session node.

[0293] In another example, the access management device sends the first response message to a first intermediate session node, and the first intermediate session node sends the first response message to the first session node.

[0294] The first response message or the message including the first response message may be a Namf_Communication_EBIAssignment Response message and / or a Nsmf_PDUSession_Update response message.

[0295] S904: The first session node starts a second timer according to the indication information contained in the first response message. If the second timer times out, the first session node sends a second request message. The second request message is used to establish or update the first QoS flow. The second request message includes the first PDU session identifier, the first QoS flow identifier corresponding to the first QoS flow, and the first EBI.

[0296] Optionally, the indication information included in the first response message may be indication information for prioritizing the withdrawal of the allocated EBI.

[0297] In an example, the first session node may directly send the second request message to the access management node.

[0298] In another example, the first session node may send the second request message to a first intermediate session node, which sends the second request message to the access management node.

[0299] For example, the second request message, or the message containing the second request message may be an Nsmf_PDUSession_Update request message, and / or a Namf_Communication_N1N2MessageTransferrequest message.

[0300] The following describes the bearer identifier allocation process shown in the fourth method with a specific embodiment. Figure 10 As shown, the following process is included:

[0301] S1001 to S1003 may refer to the above-mentioned S401 to S403.

[0302] S1004: The access management node replies with a Namf_Communication_EBIAssignment Response message to the intermediate session node 1. The message includes the EBI assigned by the access management node to the QoS flow and indication information of preferentially withdrawing the assigned EBI.

[0303] S1005: The intermediate session node 1 replies with an Nsmf_PDUSession_Update response message to the session node 1. The message carries the EBI to be allocated and indication information of preferentially withdrawing the allocated EBI.

[0304] The session node 1 starts a timer according to the message, and triggers S1006 to S1017 when the timer times out.

[0305] S1006 to S1017 can refer to the above-mentioned S406 to S417.

[0306] S1018~S1033 can refer to the above-mentioned S418~S833.

[0307] It should be noted that there is no necessary order in which the access management node executes steps S1004 and S1018. For example, the access management node can send S1018 Nsmf_PDUSession_UpdateSMContext request message to intermediate session node 2 to trigger the EBI withdrawal process, and at the same time send S1004 Namf_Communication_EBIAssignmentResponse message to intermediate session node 1 to trigger the EBI allocation process.

[0308] Next, we will introduce a Figure 9 、 Figure 10 Corresponding bearer identity allocation process:

[0309] The session node sends a first request message to the access management node, where the first request message is used to request allocation of an EBI for the first QoS flow. The first request message is the first request message shown in S901, or the Nsmf_PDUSession_Update request message in S1002, or the Namf_Communication_EBIAssignment Request message in S1003.

[0310] The session node receives a first response message, where the first response message includes the first EBI associated with the first QoS flow and an instruction to withdraw the EBI. The first response message is the first response message shown in S903, or the Namf_Communication_EBIAssignment Response message in S1004, or the Nsmf_PDUSession_Update response message in S1005.

[0311] The session node starts a second timer based on the indication information included in the first response message. If the second timer times out, the session node sends a second request message, where the second request message is used to establish or update the first QoS flow. The second request message includes the first PDU session identifier, the first QoS flow identifier corresponding to the first QoS flow, and the first EBI. The second request message is the second request message shown in S904, or the Nsmf_PDUSession_Update request message in S1006, or the Namf_Communication_N1N2MessageTransfer request message in S1007.

[0312] Next, we will introduce a bearer identity allocation process:

[0313] The access management node receives a first request message from the first session node, where the first request message is used to request allocation of an EBI for the first QoS flow.

[0314] The access management node sends a third request message to the second session node, where the third request message is used to withdraw the first EBI of the second QoS flow. The third request message is the third request message shown in S902, or the Nsmf_PDUSession_UpdateSMContext request message in S1018, or the Nsmf_PDUSession_Update request message in S1019.

[0315] The access management node sends a first response message to the first session node, where the first response message includes the first EBI associated with the first QoS flow and instruction information for withdrawing the EBI. The first response message is the first response message shown in S903, or the Namf_Communication_EBIAssignment Response message in S1004, or the Nsmf_PDUSession_Update response message in S1005.

[0316] In an embodiment of the present application, when EBI already exists, the first session node delays triggering the EPS bearer allocation process to avoid the EPS bearer allocation process being earlier than the EPS bearer withdrawal process, which can avoid abnormal processing of EPS bearers of terminal devices and access network devices, and can also avoid affecting business continuity.

[0317] The intermediate nodes shown in the various embodiments of the present application are optional nodes. If there is no intermediate session node, the interaction process performed by the intermediate session node can be completed by the session node.

[0318] The preceding text describes the bearer identifier allocation method according to an embodiment of the present application. The following text describes the bearer identifier allocation apparatus according to an embodiment of the present application. The method and apparatus are based on the same technical concept. Since the method and apparatus solve similar problems, the implementation of the apparatus and method can refer to each other, and any repetitions will not be repeated.

[0319] Based on the same technical concept as the above-mentioned bearer identity allocation method, Figure 11 As shown, a bearer identifier allocation device 1100 is provided, which includes a processing unit 1101 and a transceiver unit 1102. The device 1100 can be used to implement the method described in the above method embodiment applied to the first device or session node or access management node.

[0320] In one embodiment, the apparatus 1100 is applied to a first device, which includes a terminal device and / or an access network device.

[0321] Specifically, the processing unit 1101 is configured to receive a first request message from an access management node through the transceiver unit 1102, where the first request message is used to establish or update a first QoS flow, and the first request message includes a first PDU session identifier, a first QoS flow identifier corresponding to the first QoS flow, and a first EBI;

[0322] The processing unit 1101 is further configured to, if a second QoS flow has been established on the first device and the second EBI corresponding to the second QoS flow is the same as the first EBI, send a first response message to the access management node through the transceiver unit 1102, where the first response message is used to indicate that the allocation of the first EBI has failed.

[0323] In one implementation, the processing unit 1101 is further configured to establish or update the first QoS flow, and the first response message is further configured to indicate that the first QoS flow is successfully established or updated.

[0324] In one implementation, the processing unit 1101 is further configured to determine that the second PDU session identifier associated with the second EBI is different from the first PDU session identifier associated with the first EBI.

[0325] In one implementation, the transceiver unit 1102 is further configured to receive a second request message from the access management node, where the second request message is used to withdraw the second EBI corresponding to the second QoS flow, where the second request message includes a second PDU session identifier, a second QoS flow identifier corresponding to the second QoS flow, and the second EBI;

[0326] The processing unit 1101 is further configured to delete the second EBI;

[0327] The transceiver unit 1102 is further configured to send a second response message to the access management node, where the second response message is used to indicate that the second EBI is successfully withdrawn.

[0328] In another embodiment, the apparatus 1100 is applied to a session node.

[0329] Specifically, the processing unit 1101 is configured to receive, through the transceiver unit 1102, a first EBI associated with a first QoS flow from an access management node;

[0330] The processing unit 1101 is further configured to send a third request message to the access management node through the transceiver unit 1102, where the third request message includes the first PDU session identifier, the first QoS flow identifier corresponding to the first QoS flow, and the first EBI;

[0331] The processing unit 1101 is further configured to receive a third response message from the access management node through the transceiver unit 1102 , where the third response message is configured to indicate that the first EBI allocation has failed.

[0332] In one implementation, the third response message is further used to indicate that the first QoS flow is established or updated successfully.

[0333] In one implementation, the transceiver unit 1102 is further configured to notify the access management node to withdraw the first EBI corresponding to the first QoS flow; or to send the third request message to the access management node again.

[0334] In yet another embodiment, the apparatus 1100 is applied to an access management node.

[0335] Specifically, the processing unit 1101 is configured to send a first EBI associated with a first QoS flow to a first session node through the transceiver unit 1102;

[0336] The processing unit 1101 is further configured to receive a third request message from the first session node through the transceiver unit 1102, where the third request message includes the first unit PDU session identifier, the first QoS flow identifier corresponding to the first QoS flow, and the first EBI;

[0337] The processing unit 1101 is further configured to send a first request message to a first device through the transceiver unit 1102, where the first request message is used to establish or update a first QoS flow, the first request message including the first PDU session identifier, the first QoS flow identifier, and the first EBI, and the first device includes a terminal device and / or an access network device;

[0338] The processing unit 1101 is further configured to receive, through the transceiver unit 1102, a first response message from the first device, where the first response message is used to indicate that the first EBI allocation has failed;

[0339] The processing unit 1101 is further configured to send a third response message to the first session node through the transceiver unit 1102 , where the third response message is used to indicate that the first EBI allocation has failed.

[0340] In one implementation, the first response message is further used to indicate that the first QoS flow is successfully established or updated; and / or the third response message is further used to indicate that the first QoS flow is successfully established or updated.

[0341] In one implementation, the transceiver unit 1102 is further used to receive a second response message from the first device, where the second response message is used to indicate that the second EBI corresponding to the second QoS flow is successfully withdrawn, and the second QoS flow is a QoS flow that has been established on the first device; and send a fourth response message to the second session node, where the fourth response message is used to indicate that the second EBI is successfully withdrawn.

[0342] In one implementation, the transceiver unit 1102 is further configured to send a second request message to notify the first device to withdraw the second EBI based on the instruction information for withdrawing the second EBI included in the fourth request message from the second session node.

[0343] In one embodiment, the apparatus 1100 is applied to a first device, which includes a terminal device and / or an access network device.

[0344] Specifically, the transceiver unit 1102 is configured to receive a first request message from the access management node, where the first request message is used to establish or update a first QoS flow, and the first request message includes a first PDU session identifier, a first QoS flow identifier corresponding to the first QoS flow, and a first EBI;

[0345] The processing unit 1101 is configured to delete the second EBI if a second QoS flow has been established and the second EBI corresponding to the second QoS flow is the same as the first EBI;

[0346] The transceiver unit 1102 is further configured to send a first response message to the access management node, where the first response message is used to indicate that the first EBI allocation is successful.

[0347] In one implementation, the processing unit 1101 is further configured to establish or update the first QoS flow, and the first response message is further configured to indicate that the first QoS flow is successfully established or updated.

[0348] In one implementation, the processing unit 1101 is further configured to determine that the second PDU session identifier associated with the second EBI is different from the first PDU session identifier associated with the first EBI.

[0349] In another embodiment, the apparatus 1100 is applied to an access management node.

[0350] The processing unit 1101 is configured to send a second request message to the second session node through the transceiver unit 1102, where the second request message is used to instruct allocation of a first EBI for the first PDU session and withdrawal of a second EBI for the second PDU session;

[0351] The processing unit 1101 is further configured to send a first EBI associated with a first quality of service QoS flow identifier to the first session node through the transceiver unit 1102;

[0352] The processing unit 1101 is further configured to receive, through the transceiver unit 1102, a third request message from the first session node, where the third request message is used to establish or update a first QoS flow, and the third request message includes a first PDU session identifier, a first QoS flow identifier corresponding to the first QoS flow, and a first EBI;

[0353] The processing unit 1101 is further configured to send a first request message to a first device through the transceiver unit 1102, where the first request message is used to establish or update a first QoS flow, and the first request message includes a first PDU session identifier, a first QoS flow identifier corresponding to the first QoS flow, and a first EBI, where the first device includes a terminal device and / or an access network device;

[0354] The processing unit 1101 is further configured to receive a first response message through the transceiver unit 1102 , where the first response message is used to indicate that the first EBI allocation is successful.

[0355] In one implementation, the first response message is further used to indicate that the first QoS flow is established or updated successfully.

[0356] In one embodiment, the apparatus 1100 is applied to an access management node.

[0357] Specifically, the processing unit 1101 is configured to receive a first request message from a first session node through the transceiver unit 1102, where the first request message is used to request allocation of an EBI for the first QoS flow;

[0358] The processing unit 1101 is further configured to send a second request message to the second session node through the transceiver unit 1102, where the second request message is used to withdraw the first EBI of a second QoS flow, where the second QoS flow belongs to a second PDU session;

[0359] The processing unit 1101 is further configured to receive, through the transceiver unit 1102, a first response message from the second session node, where the first response message is used to notify that the first EBI is successfully withdrawn;

[0360] The processing unit 1101 is further configured to wait for the first EBI to be withdrawn and then send a second response message to the first session node through the transceiver unit 1102, where the second response message includes the first EBI associated with the first QoS flow.

[0361] In one implementation, the processing unit 1101 is further configured to start a first timer after receiving the first response message, and when the first timer times out, the access management node determines that the withdrawal of the first EBI is completed;

[0362] or

[0363] The transceiver unit 1102 is further configured to receive a third response message from a first device, where the first device includes a terminal device and / or an access network device, and the third response message includes the second PDU session identifier;

[0364] The processing unit 1101 is further configured to determine, according to the third response message, that the withdrawal of the first EBI is completed.

[0365] In one embodiment, the apparatus 1100 is applied to a session node.

[0366] Specifically, the transceiver unit 1102 is configured to send a first request message to the access management node, where the first request message is used to request allocation of an EBI for the first QoS flow; and receive a first response message, where the first response message includes the first EBI associated with the first QoS flow and also includes indication information for withdrawing the EBI.

[0367] The processing unit 1101 is configured to start a second timer according to the instruction information included in the first response message;

[0368] The transceiver unit 1102 is also used to send a second request message if the second timer times out. The second request message is used to establish or update the first QoS flow. The second request message includes the first PDU session identifier, the first QoS flow identifier corresponding to the first QoS flow, and the first EBI.

[0369] In another embodiment, the apparatus 1100 is applied to an access management node.

[0370] The processing unit 1101 is configured to receive a first request message from a first session node through the transceiver unit 1102, where the first request message is used to request allocation of an EBI for the first QoS flow;

[0371] The processing unit 1101 is further configured to send a third request message to the second session node through the transceiver unit 1102, where the third request message is used to withdraw the first EBI of the second QoS flow;

[0372] The processing unit 1101 is further configured to send a first response message to the first session node through the transceiver unit 1102 , where the first response message includes the first EBI associated with the first QoS flow and indication information for withdrawing the EBI.

[0373] It should be noted that the division of modules in the embodiments of the present application is illustrative and is merely a logical functional division. In actual implementation, other division methods may be used. Furthermore, the functional units in the various embodiments of the present application may be integrated into a single processing unit, or may exist physically separately, or two or more units may be integrated into a single unit. The aforementioned integrated units may be implemented in the form of hardware or software functional units.

[0374] If the integrated unit is implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present application is essentially or the part that contributes to the prior art or all or part of the technical solution can be embodied in the form of a software product, and the computer software product is stored in a storage medium, including a number of instructions for enabling a computer device (which can be a personal computer, server, or network device, etc.) or a processor to execute all or part of the steps of the method described in each embodiment of the present application. The aforementioned storage medium includes: various media that can store program codes, such as a USB flash drive, a mobile hard disk, a read-only memory (ROM), a random access memory (RAM), a magnetic disk or an optical disk.

[0375] Based on the same concept as the above-mentioned bearer identity allocation method, Figure 12 As shown, an embodiment of the present application also provides a schematic structural diagram of a bearer identity allocation apparatus 1200. Apparatus 1200 can be used to implement the method described in the above-mentioned method embodiment applied to a first device, session node, or access management node. For details, please refer to the description of the above-mentioned method embodiment. Apparatus 1200 can be located in or be the first device, session node, or access management node.

[0376] The device 1200 includes one or more processors 1201. The processor 1201 can be a general-purpose processor or a dedicated processor. For example, it can be a baseband processor or a central processing unit. The baseband processor can be used to process communication protocols and communication data, and the central processing unit can be used to control a communication device (such as a base station, terminal, or chip), execute software programs, and process data of the software programs. The communication device may include a transceiver unit to implement signal input (reception) and output (transmission). For example, the transceiver unit can be a transceiver, a radio frequency chip, etc.

[0377] The apparatus 1200 includes one or more processors 1201 , and the one or more processors 1201 can implement the method of the first device or session node or access management node in the above-mentioned embodiment.

[0378] Optionally, the processor 1201 may implement other functions in addition to implementing the method of the embodiment shown above.

[0379] Optionally, in one design, the processor 1201 may execute instructions to cause the apparatus 1200 to perform the method described in the above method embodiment. The instructions may be stored in whole or in part within the processor, such as instruction 1203, or may be stored in whole or in part in a memory 1202 coupled to the processor, such as instruction 1204. Instructions 1203 and 1204 may also be used together to cause the apparatus 1200 to perform the method described in the above method embodiment.

[0380] In another possible design, the communication device 1200 may also include a circuit, which can implement the functions of the first device or session node or access management node in the aforementioned method embodiment.

[0381] In another possible design, the device 1200 may include one or more memories 1202, on which instructions 1204 are stored. The instructions can be executed on the processor so that the device 1200 performs the method described in the above method embodiment. Optionally, data can also be stored in the memory. The optional processor can also store instructions and / or data. For example, the one or more memories 1202 can store the corresponding relationships described in the above embodiment, or the relevant parameters or tables involved in the above embodiment. The processor and memory can be provided separately or integrated together.

[0382] In another possible design, the apparatus 1200 may further include a transceiver 1205 and an antenna 1206. The processor 1201 may be referred to as a processing unit, which controls the apparatus (terminal or base station). The transceiver 1205 may be referred to as a transceiver, a transceiver circuit, or a transceiver unit, etc., which is configured to implement the transceiver functions of the apparatus via the antenna 1206.

[0383] It should be noted that the processor in the embodiments of the present application can be an integrated circuit chip with signal processing capabilities. During implementation, each step of the above-mentioned method embodiment can be completed by hardware integrated logic circuits in the processor or by software instructions. The above-mentioned processor can be a general-purpose processor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field programmable gate array (FPGA), or other programmable logic devices, discrete gate or transistor logic devices, or discrete hardware components. The various methods, steps, and logic block diagrams disclosed in the embodiments of the present application can be implemented or executed. The general-purpose processor can be a microprocessor or any conventional processor. The steps of the method disclosed in the embodiments of the present application can be directly implemented and executed by a hardware decoding processor, or by a combination of hardware and software modules in the decoding processor. The software module can be located in a storage medium well-known in the art, such as random access memory, flash memory, read-only memory, programmable read-only memory, electrically erasable programmable memory, registers, etc. The storage medium is located in the memory, and the processor reads the information in the memory and, in conjunction with its hardware, completes the steps of the above-mentioned method.

[0384] It is understood that the memory in the embodiments of the present application may be a volatile memory or a non-volatile memory, or may include both volatile and non-volatile memories. Among them, the non-volatile memory may be a read-only memory (ROM), a programmable read-only memory (PROM), an erasable programmable read-only memory (EPROM), an electrically erasable programmable read-only memory (EEPROM), or a flash memory. The volatile memory may be a random access memory (RAM), which is used as an external cache. By way of example and not limitation, many forms of RAM are available, such as static RAM (SRAM), dynamic RAM (DRAM), synchronous DRAM (SDRAM), double data rate SDRAM (DDR SDRAM), enhanced SDRAM (ESDRAM), synchronous link DRAM (SLDRAM), and direct RAM bus RAM (DR RAM). It should be noted that the memory of the systems and methods described herein is intended to include, but is not limited to, these and any other suitable types of memory.

[0385] An embodiment of the present application also provides a computer-readable medium having a computer program stored thereon, which, when executed by a computer, implements the bearer identifier allocation method described in any one of the above method embodiments applied to the first device, session node, or access management node.

[0386] An embodiment of the present application also provides a computer program product, which, when executed by a computer, implements the bearer identifier allocation method described in any one of the above method embodiments applied to the first device, session node, or access management node.

[0387] An embodiment of the present application further provides a communication system, which includes: a first device that executes the above-mentioned bearer identifier allocation method, an access management node, and a session node.

[0388] In the above embodiments, all or part of the embodiments may be implemented by software, hardware, firmware, or any combination thereof. When implemented using software, all or part of the embodiments may be implemented in the form of a computer program product. The computer program product includes one or more computer instructions. When the computer instructions are loaded and executed on a computer, all or part of the processes or functions described in the embodiments of the present application are generated. The computer may be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device. 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 one website, computer, server, or data center to another website, computer, server, or data center via a wired (e.g., coaxial cable, optical fiber, digital subscriber line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.) method. The computer-readable storage medium may be any available medium that a computer can access or a data storage device such as a server or data center that includes one or more available media integrated therein. The available medium may be a magnetic medium (eg, a floppy disk, a hard disk, a magnetic tape), an optical medium (eg, a high-density digital video disc (DVD)), or a semiconductor medium (eg, a solid state disk (SSD)).

[0389] An embodiment of the present application also provides a processing device, including a processor and an interface; the processor is used to execute the bearer identifier allocation method described in any method embodiment applied to the first device or session node or access management node.

[0390] It should be understood that the above-mentioned processing device can be a chip, and the processor can be implemented by hardware or by software. When implemented by hardware, the processor can be a logic circuit, an integrated circuit, etc.; when implemented by software, the processor can be a general-purpose processor, which is implemented by reading the software code stored in the memory. The memory can be integrated into the processor or can be located outside the processor and exist independently.

[0391] Those skilled in the art will appreciate that the units and algorithm steps of each example described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, computer software, or a combination of the two. In order to clearly illustrate the interchangeability of hardware and software, the composition and steps of each example have been generally described in terms of function in the above description. Whether these functions are performed in hardware or software depends on the specific application and design constraints of the technical solution. Professional and technical personnel can use different methods to implement the described functions for each specific application, but such implementation should not be considered to be beyond the scope of this application.

[0392] Those skilled in the art will clearly understand that, for the sake of convenience and brevity of description, the specific working processes of the systems, devices and units described above can refer to the corresponding processes in the aforementioned method embodiments and will not be repeated here.

[0393] In the several embodiments provided in this application, it should be understood that the disclosed systems, devices and methods can be implemented in other ways. For example, the device embodiments described above are merely schematic. For example, the division of units is merely a logical function division. In actual implementation, there may be other division methods, such as multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. In addition, the mutual coupling or direct coupling or communication connection shown or discussed can be an indirect coupling or communication connection through some interfaces, devices or units, or can be electrical, mechanical or other forms of connection.

[0394] The units described as separate components may or may not be physically separate, and the components shown as units may or may not be physical units, that is, they may be located in one place or distributed across multiple network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the embodiments of the present application.

[0395] In addition, the functional units in the various embodiments of the present application may be integrated into a single processing unit, or each unit may exist physically separately, or two or more units may be integrated into a single unit. The aforementioned integrated units may be implemented in the form of hardware or software functional units.

[0396] Through the description of the above embodiments, it will be clear to those skilled in the art that the present application can be implemented in hardware, firmware, or a combination thereof. When implemented using software, the above functions can be stored in a computer-readable medium or transmitted as one or more instructions or codes on a computer-readable medium. Computer-readable media include computer storage media and communication media, wherein communication media include any medium that facilitates the transmission of computer programs from one place to another. The storage medium can be any available medium that can be accessed by a computer. By way of example and not limitation, computer-readable media can include RAM, ROM, EEPROM, CD-ROM or other optical disk storage, magnetic disk storage media or other magnetic storage devices, or any other medium that can be used to carry or store desired program code in the form of instructions or data structures and can be accessed by a computer. In addition, any connection can appropriately become a computer-readable medium. For example, if the software is transmitted from a website, server, or other remote source using a coaxial cable, fiber optic cable, twisted pair, digital subscriber line (DSL), or wireless technologies such as infrared, radio, and microwaves, then the coaxial cable, fiber optic cable, twisted pair, DSL, or wireless technologies such as infrared, radio, and microwaves are included in the fixing of the medium. As used herein, the terms "disk" and "disc" include compact discs (CDs), laser discs, optical discs, digital versatile discs (DVDs), floppy disks, and Blu-ray discs. Disks typically reproduce data magnetically, while discs reproduce data optically using lasers. Combinations of the above should also be included within the scope of protection for computer-readable media.

[0397] In short, the above description is only a preferred embodiment of the technical solution of this application and is not intended to limit the scope of protection of this application. Any modifications, equivalent replacements, improvements, etc. made within the spirit and principles of this application shall be included in the scope of protection of this application.

Claims

1. A bearer identifier allocation method, characterized in that: include: A first device receives a first request message from an access management node, where the first request message is used to establish or update a first quality of service (QoS) flow, and the first request message includes a first packet data unit (PDU) session identifier, a first QoS flow identifier corresponding to the first QoS flow, and a first evolved packet system bearer identifier (EBI). The first device includes a terminal device and / or an access network device. If a second QoS flow has been established on the first device, and a second EBI corresponding to the second QoS flow is the same as the first EBI, the first device sends a first response message to the access management node, where the first response message is used to indicate that allocation of the first EBI fails.

2. The method according to claim 1, wherein Also includes: The first device establishes or updates the first QoS flow, and the first response message is further used to indicate that the first QoS flow is successfully established or updated.

3. The method according to claim 1 or 2, wherein: Also includes: The first device determines that the second PDU session identifier associated with the second EBI is different from the first PDU session identifier associated with the first EBI.

4. The method according to claim 1 or 2, wherein: Also includes: The first device receives a second request message from the access management node, where the second request message is used to withdraw the second EBI corresponding to the second QoS flow, and the second request message includes a second PDU session identifier, a second QoS flow identifier corresponding to the second QoS flow, and the second EBI; Deleting, by the first device, the second EBI; The first device sends a second response message to the access management node, where the second response message is used to indicate that the second EBI is withdrawn successfully.

5. A bearer identifier allocation method, characterized in that: include: The access management node sends a first request message to the first device, where the first request message is used to establish or update a first quality of service QoS flow, where the first request message includes a first packet data unit PDU session identifier, a first QoS flow identifier corresponding to the first QoS flow, and a first evolved packet system bearer identifier EBI, where the first device includes a terminal device and / or an access network device; The access management node receives a first response message from the first device, where the first response message is used to indicate that the first EBI allocation fails; The second EBI corresponding to the second QoS flow established on the first device is the same as the first EBI.

6. The method according to claim 5, wherein Before the access management node sends the first request message to the first device, the method further includes: The access management node sends a first evolved packet system bearer identifier EBI associated with a first quality of service QoS flow to the first session node; The access management node receives a third request message from the first session node, where the third request message includes the first packet data unit (PDU) session identifier, the first QoS flow identifier corresponding to the first QoS flow, and the first EBI.

7. The method according to claim 6, wherein Also includes: The access management node sends a third response message to the first session node, where the third response message is used to indicate that the first EBI allocation fails.

8. The method according to claim 7, wherein The first response message is further used to indicate that the first QoS flow is successfully established or updated; and / or; The third response message is also used to indicate that the first QoS flow is established or updated successfully.

9. The method according to claim 5 or 8, wherein Also includes: The access management node receives a second response message from the first device, where the second response message is used to indicate that a second EBI corresponding to a second QoS flow is successfully withdrawn, where the second QoS flow is a QoS flow that has been established on the first device; The access management node sends a fourth response message to the second session node, where the fourth response message is used to indicate that the second EBI is withdrawn successfully.

10. The method according to claim 9, wherein Before receiving the second response information from the first device, the method further includes: The access management node sends a second request message to notify the first device to withdraw the second EBI based on the instruction information for withdrawing the second EBI contained in the fourth request message from the second session node.

11. A bearer identifier allocation method, characterized in that: include: A first device receives a first request message from an access management node, where the first request message is used to establish or update a first quality of service (QoS) flow, and the first request message includes a first packet data unit (PDU) session identifier, a first QoS flow identifier corresponding to the first QoS flow, and a first evolved packet system bearer identifier (EBI). The first device includes a terminal device and / or an access network device. If a second QoS flow has been established on the first device, the second EBI corresponding to the second QoS flow is the same as the first EBI, and the second PDU session identifier associated with the second EBI is different from the first PDU session identifier associated with the first EBI, the first device deletes the second EBI; The first device sends a first response message to the access management node, where the first response message is used to indicate that the first EBI allocation is successful.

12. The method according to claim 11, wherein Also includes: The first device establishes or updates the first QoS flow, and the first response message is further used to indicate that the first QoS flow is successfully established or updated.

13. A bearer identifier allocation method, characterized in that: include: The access management node sends a first request message to the first device, where the first request message is used to establish or update a first quality of service QoS flow, where the first request message includes a first packet data unit PDU session identifier, a first QoS flow identifier corresponding to the first QoS flow, and a first evolved packet system bearer identifier EBI, where the first device includes a terminal device and / or an access network device; The access management node receives a first response message, which is used to indicate that the first EBI is allocated successfully; wherein, the second EBI corresponding to the second QoS flow established on the first device is the same as the first EBI, and the second PDU session identifier associated with the second EBI is different from the first PDU session identifier associated with the first EBI.

14. The method according to claim 13, wherein Before the access management node sends the first request message to the first device, the method further includes: The access management node sends a second request message to the second session node, where the second request message is used to instruct allocation of a first evolved packet system bearer identifier EBI for the first packet data unit PDU session and withdrawal of a second EBI for the second PDU session; The access management node sends a first EBI associated with a first quality of service QoS flow identifier to the first session node; The access management node receives a third request message from the first session node, where the third request message is used to establish or update a first QoS flow. The third request message includes a first PDU session identifier, a first QoS flow identifier corresponding to the first QoS flow, and a first EBI.

15. The method according to claim 13, wherein The first response message is also used to indicate that the first QoS flow is established or updated successfully.

16. A bearer identifier allocation device, characterized in that: The method comprises a processing unit and a transceiver unit, wherein the processing unit is coupled to the transceiver unit and is used to execute the method according to any one of claims 1 to 4, or to execute the method according to any one of claims 5 to 10, or to execute the method according to any one of claims 11 to 12, or to execute the method according to any one of claims 13 to 15.

17. A bearer identifier allocation device, characterized in that: The device includes: a processor and a memory; the processor and the memory are electrically coupled; The memory is used to store computer program instructions; The processor is used to execute part or all of the computer program instructions in the memory, and when the part or all of the computer program instructions are executed, to implement the method according to any one of claims 1 to 4, or to implement the method according to any one of claims 5 to 10, or to implement the method according to any one of claims 11 to 12, or to implement the method according to any one of claims 13 to 15.

18. A computer-readable storage medium, characterized in that The computer-readable storage medium stores computer-readable instructions. When a computer reads and executes the computer-readable instructions, the computer executes the method according to any one of claims 1 to 4, or the method according to any one of claims 5 to 10, or the method according to any one of claims 11 to 12, or the method according to any one of claims 13 to 15.

Images