WO2020228770A1 - 一种承载修改方法及接入网设备 - Google Patents

一种承载修改方法及接入网设备 Download PDF

Info

Publication number
WO2020228770A1
WO2020228770A1 PCT/CN2020/090225 CN2020090225W WO2020228770A1 WO 2020228770 A1 WO2020228770 A1 WO 2020228770A1 CN 2020090225 W CN2020090225 W CN 2020090225W WO 2020228770 A1 WO2020228770 A1 WO 2020228770A1
Authority
WO
WIPO (PCT)
Prior art keywords
access network
network device
terminal device
registration process
radio access
Prior art date
Application number
PCT/CN2020/090225
Other languages
English (en)
French (fr)
Inventor
银宇
戚彩霞
陶振宇
Original Assignee
华为技术有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 华为技术有限公司 filed Critical 华为技术有限公司
Priority to EP20806781.9A priority Critical patent/EP3962164B1/en
Publication of WO2020228770A1 publication Critical patent/WO2020228770A1/zh
Priority to US17/525,206 priority patent/US20220078677A1/en

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/0005—Control or signalling for completing the hand-off
    • H04W36/0055—Transmission or use of information for re-establishing the radio link
    • H04W36/0069—Transmission or use of information for re-establishing the radio link in case of dual connectivity, e.g. decoupled uplink/downlink
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W28/00—Network traffic management; Network resource management
    • H04W28/16—Central resource management; Negotiation of resources or communication parameters, e.g. negotiating bandwidth or QoS [Quality of Service]
    • H04W28/18—Negotiating wireless communication parameters
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W28/00—Network traffic management; Network resource management
    • H04W28/16—Central resource management; Negotiation of resources or communication parameters, e.g. negotiating bandwidth or QoS [Quality of Service]
    • H04W28/18—Negotiating wireless communication parameters
    • H04W28/20—Negotiating bandwidth
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W28/00—Network traffic management; Network resource management
    • H04W28/16—Central resource management; Negotiation of resources or communication parameters, e.g. negotiating bandwidth or QoS [Quality of Service]
    • H04W28/24—Negotiating SLA [Service Level Agreement]; Negotiating QoS [Quality of Service]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/06—Reselecting a communication resource in the serving access point
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/08—Reselecting an access point
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/16—Performing reselection for specific purposes
    • H04W36/165—Performing reselection for specific purposes for reducing network power consumption
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/10—Connection setup
    • H04W76/15—Setup of multiple wireless link connections
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/20—Manipulation of established connections
    • H04W76/22—Manipulation of transport tunnels
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W60/00—Affiliation to network, e.g. registration; Terminating affiliation with the network, e.g. de-registration
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/10—Connection setup
    • H04W76/11—Allocation or use of connection identifiers
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/10—Connection setup
    • H04W76/12—Setup of transport tunnels
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W88/00—Devices specially adapted for wireless communication networks, e.g. terminals, base stations or access point devices
    • H04W88/02—Terminal devices
    • H04W88/06—Terminal devices adapted for operation in multiple networks or having at least two operational modes, e.g. multi-mode terminals

Definitions

  • the embodiment of the present invention relates to the field of communication technology, and in particular to a bearer modification method and access network equipment.
  • the access network device can actively trigger the modification of the wireless access bearer of the terminal device. For example, when the access network device cannot meet the quality of service (QoS) of the wireless access bearer, the wireless access bearer can be modified. QoS parameters of the incoming bearer.
  • QoS quality of service
  • a terminal device can establish a connection with two access network devices at the same time, and the connection established by the two access network devices can be determined by the dual connection.
  • the network access device is called the master access network device, and the other access network device is called the second access network device or the slave access network device.
  • the service data packet may be sent to the terminal device through the main access network device or the second access network device, and the main access network device decides whether the service data packet is forwarded by the main access network device or the second access network device.
  • the main access network device can trigger the modification of the radio access bearer according to the network conditions, for example, the service data packet is forwarded and modified by the main access network device to be forwarded by the second access network device, and vice versa.
  • the terminal device executes the complete registration process to access the network.
  • the complete registration process includes the registration process and the second session establishment process.
  • the first session is created during the registration process, and the default bearer of the data service is established immediately.
  • the complete registration process includes a registration process, a first session establishment process, and a second session establishment process. After the terminal device registers to the network through the registration process, the first session is created immediately, and the default bearer of the data service is established. Create a second session and establish a default bearer for the voice service.
  • the access network device does not perceive the complete registration process, and the radio access bearer of the terminal device has been created on the access network device, and the current condition meets the modification condition of the radio access bearer, the access network device triggers the modification of the radio access bearer .
  • the access network equipment will transfer the data service of the terminal equipment to the second access network equipment for forwarding as soon as possible, which intensifies the communication with the terminal equipment.
  • Conflicts between the complete registration process This leads to a conflict between the complete registration process and the above-mentioned radio access bearer modification.
  • the process of creating the second session of the voice service conflicts with the above-mentioned radio access bearer modification, and the main access network equipment and core network equipment are locked to each other, and the signaling process cannot succeed.
  • the business of the terminal device cannot be performed normally, which seriously reduces the business experience of the terminal device.
  • the embodiment of the invention discloses a bearer modification method and an access network device, which are used to improve the service experience of the terminal device.
  • the first aspect discloses a bearer modification method.
  • the access network device determines that the terminal device completes the complete registration process, or determines that the terminal device has not completed the complete registration process, waits for the terminal device to complete the complete registration process, and then modifies the radio access bearer. It can be seen that since the modification of the wireless access bearer of the terminal device is performed after the terminal device is determined to complete the complete registration process or wait for the terminal device to complete the complete registration process, it will not conflict with the complete registration process of the terminal device, and will not affect The business of the terminal device is running normally, which can improve the business experience of the terminal device.
  • the access network device determines that the terminal device has completed the complete registration process, which may be determined that the terminal device has completed the complete registration process, or it may be determined that the terminal device has completed the complete registration process within the first time.
  • the completion of the complete registration process of the terminal device may include that the number of radio access bearers in the context of the terminal device is greater than or equal to the first threshold, and/or the context of the terminal device includes a parameter of a radio access bearer Is a specific value.
  • the access network device waiting for the terminal device to complete the complete registration process may include one or more of the following: the number of radio access bearers in the context of the terminal device is greater than or equal to the first threshold; the context of the terminal device The parameter containing a radio access bearer is a specific value; the waiting time of the access network device exceeds the first time.
  • the parameters of the radio access bearer may be quality of service (QoS) type, allocation and retention priority (ARP), and aggregate maximum bit rate, One or more of AMBR).
  • QoS quality of service
  • ARP allocation and retention priority
  • AMBR aggregate maximum bit rate
  • the QoS type may be a quality of service identifier (QoS class identifier, QCI), or may be a 5G quality of service identifier (5G QoS identifier, 5QI).
  • QCI quality of service identifier
  • 5G QoS identifier 5G QoS identifier
  • the radio access bearer modification process may include the addition of the second access network device , Modification of the second access network device, deletion of the second access network device, change of the second access network device, or QoS update.
  • the access network device may send to the core network device a wireless access carrying the network protocol (IP) address of the second access network device and the tunnel endpoint identifier (TEID)
  • IP network protocol
  • TEID tunnel endpoint identifier
  • the access network device may send a radio access bearer modification request message carrying QoS parameters of the radio access bearer to the core network device, and receive a radio access bearer modification response message from the core network device, To complete the modification of the radio access bearer.
  • the QoS parameter may be one or more of QCI, ARP, uplink and downlink bandwidth, QoS flow identifier (QoS flow identifier, QFI), and QoS satisfaction indication.
  • QoS satisfaction indication is used to notify the network that the QoS cannot be met, so that the network can adjust the QoS parameters.
  • a second aspect discloses an access network device, which includes a unit for executing the bearer modification method disclosed in the first aspect or any one of the embodiments of the first aspect.
  • a third aspect discloses an access network device.
  • the access network device may include a processor, the processor and a memory are coupled to each other, the memory is used for storing computer programs or instructions, and the processor is used for executing the computer programs or instructions stored in the memory,
  • the access network device is caused to execute the bearer modification method disclosed in the first aspect or any one of the embodiments of the first aspect.
  • a fourth aspect discloses a readable storage medium with a program stored on the readable storage medium, and when the program runs, the bearer modification method disclosed in the first aspect or any one of the first aspect is implemented.
  • Figure 1 is a schematic diagram of a network architecture disclosed in an embodiment of the present invention.
  • Figure 2 is a schematic diagram of a possible conflict flow in access network equipment
  • FIG. 3 is a schematic flowchart of a bearer modification method disclosed in an embodiment of the present invention.
  • FIG. 5 is a schematic flowchart of another bearer modification method disclosed in an embodiment of the present invention.
  • FIG. 6 is a schematic flowchart of another bearer modification method disclosed in an embodiment of the present invention.
  • FIG. 7 is a schematic flowchart of another bearer modification method disclosed in an embodiment of the present invention.
  • Figure 8 is a schematic structural diagram of an access network device disclosed in an embodiment of the present invention.
  • Fig. 9 is a schematic structural diagram of another access network device disclosed in an embodiment of the present invention.
  • the embodiment of the invention discloses a bearer modification method and an access network device, which are used to improve the service experience of the terminal device. Detailed descriptions are given below.
  • FIG. 1 is a schematic diagram of a network architecture disclosed in an embodiment of the present invention.
  • the network architecture may include terminal equipment, access network equipment, and core network equipment.
  • the terminal equipment accesses the core network through the access network equipment.
  • the core network equipment is responsible for terminal equipment location management, connection management, security authentication and other functions.
  • the DC architecture When applied to the DC architecture, there can be one or multiple access network devices. Only two access network devices are shown in Figure 1. There is at least one access network device among the one or more access network devices to determine dual connection establishment, and there is a signaling interface with the core network device, which can directly perform signaling interaction with the core network device.
  • This access network device can It is called the primary access network device, and is the first access network device as shown in Figure 1.
  • the access network device other than the primary access network device may be called the second access device or the slave access network device, as shown in FIG. 1 equipment.
  • the actual network corresponding to the above network architecture can be an evolved packet system (EPS) network.
  • EPS evolved packet system
  • the core network equipment can be mobile management Entity (mobility management entity, MME).
  • MME mobile management Entity
  • the EPS network may also include a serving gateway (S-GW), which is a local access gateway for terminal devices and is responsible for connection management and data forwarding related to access technologies.
  • S-GW serving gateway
  • PDN-GW packet data network gateway
  • the EPS network may also include a home subscriber server (home subscriber server, HSS), which is responsible for the management and maintenance of subscriber subscription information at the home location.
  • the EPS network may also include a policy and charging rules function (PCRF), which is responsible for policy control, charging, and QoS rule issuance.
  • PCRF policy and charging rules function
  • the foregoing network architecture corresponds to an actual network, and may also be a 5G network, and the core network equipment may be an access and mobility management function (AMF).
  • the 5G network may also include a session management function (session management function, SMF), which is responsible for session establishment/update/deletion of terminal devices.
  • SMF session management function
  • the 5G network may also include a user plane function (UPF), which is responsible for forwarding service data packets of terminal devices.
  • UDM unified data management
  • the 5G network may also include policy and charging rule functions, which may be a policy control function (PCF), which is responsible for policy control, charging, and QoS rule issuance.
  • PCF policy control function
  • the terminal equipment may be called a terminal (Terminal), user equipment (UE), mobile station (mobile station, MS), mobile terminal (mobile terminal, MT), and so on.
  • the terminal equipment can be a mobile phone, a tablet computer (Pad), a computer with wireless transceiver function, virtual reality (VR) terminal equipment, augmented reality (AR) terminal equipment, industrial control (industrial control) ), wireless terminals in self-driving (self-driving), wireless terminals in remote medical surgery, wireless terminals in smart grid, and wireless terminals in transportation safety (transportation safety) Terminal, wireless terminal in smart city, wireless terminal in smart home, etc.
  • the embodiment of the present application does not limit the specific technology and specific device form adopted by the terminal device.
  • Access network equipment is the access equipment for terminal equipment to access the core network. It can be a base station (NodeB), an evolved base station (evolved NodeB, eNB), a radio network controller (RNC), a transmitting and receiving point ( transmission reception point, TRP), next generation NodeB (gNB) in 5G mobile communication system, base station in future mobile communication system or access network equipment in WiFi system, etc.
  • NodeB base station
  • eNB evolved NodeB
  • RNC radio network controller
  • TRP transmission reception point
  • gNB next generation NodeB
  • the embodiment of the present application does not limit the specific technology and specific device form adopted by the radio access network device.
  • Figure 2 is a schematic diagram of a conflict flow that may occur in an access network device.
  • the terminal device triggers the complete registration process in order to access the mobile communication network for business.
  • the complete registration process corresponding to FIG. 2 includes an attachment process and a packet data network (packet data network, PDN) connection establishment process.
  • PDN packet data network
  • the terminal device may send an attach request to the mobility management network element through the first base station (that is, the first access network device in the aforementioned network architecture) to initiate the attach procedure to access the mobile communication network.
  • the mobility management network element can trigger an authentication process for the terminal device to ensure the security of the terminal device.
  • the mobile management network element may obtain the identification of the terminal device from the terminal device through the first base station, and the identification of the terminal device may be an international mobile subscriber identification number (IMSI).
  • IMSI international mobile subscriber identification number
  • the mobile management network element can register the information of the mobile management network element with the home user register, and obtain the subscription data of the terminal device from the home user register.
  • the mobility management network element can also request the establishment of the default bearer (first session) of the data service at the same time.
  • the default bearer of the data service can be established through the service gateway and the data gateway.
  • the charging rule function establishes a data service session to obtain the corresponding charging and policy rules for the data service.
  • the mobile management network element receives the subscription data from the terminal equipment of the home user register and the default bearer establishment response of the data service from the serving gateway, it sends the initial context establishment request message to the first base station, and the initial context establishment request message Carry the attach accept message and the radio access bearer (E-UTRAN radio access bearer, E-RAB) corresponding to the default bearer of the data service to be established.
  • E-UTRAN radio access bearer E-RAB
  • the first base station After receiving the initial context establishment request message from the mobility management network element, the first base station establishes the context of the terminal device, performs radio resource reconfiguration with the terminal device, and sends an initial context establishment response to the mobility management network element, and the initial context establishment The response carries the IP address and TEID of the first base station allocated to the E-RAB corresponding to the default bearer of the data service.
  • the terminal device After completing the radio bearer resource reconfiguration with the first base station, the terminal device sends an attachment completion message to the mobility management network element through the first base station.
  • the mobility management network element After receiving the initial context establishment response and the attachment completion message, the mobility management network element sends a bearer update request to the serving gateway, and the bearer update request carries the IP address and TEID of the first base station.
  • the serving gateway can send information such as the location of the terminal device to the data gateway.
  • the terminal device After the terminal device is attached, the terminal device is switched from the idle state to the connected state, and successfully accesses the core network, and the service data packet forwarded on the default bearer of the data service is forwarded by the first base station.
  • the terminal device After the attach procedure is completed, the terminal device immediately triggers the establishment of the second session and initiates the PDN connection establishment procedure to establish the default bearer of the voice service.
  • the terminal device may send a PDN connection establishment request to the mobility management network element through the first base station, initiate a PDN connection establishment process, and request the establishment of a default bearer for the voice service.
  • the mobile management network element establishes the default bearer of the voice service through the service gateway and the data gateway, and at the same time establishes a voice service session between the data network element and the policy and charging rule function, so as to obtain the corresponding charging and policy rules for the voice service.
  • the mobility management network element sends an E-RAB establishment request to the first base station.
  • the E-RAB establishment request carries a PDN connection establishment acceptance message, requesting the first base station to establish the E-RAB corresponding to the default bearer of the voice service, and then the mobility management network element Waiting for the first base station to reply the E-RAB establishment response message.
  • the first base station establishes the context of the terminal device through the initial context request message of the attach procedure, and after sending the initial context establishment response to the mobility management network element, when the current condition satisfies the trigger condition of the radio access bearer modification procedure, the first base station triggers the radio access Enter the bearer modification process.
  • the first base station in the above attachment and PDN connection establishment process is the primary base station.
  • the primary base station can determine whether the current condition meets the second base station addition condition according to the stored DC policy, and when it determines that the current condition meets the second base station In the case of adding conditions, the second base station adding procedure is triggered.
  • the DC strategy may be that when the signal strength of the second base station meets the requirement, the data service is forwarded by the second base station.
  • the primary base station initiates the second base station addition process, and switches the E-RAB corresponding to the default bearer of the data service to the second base station.
  • the radio resource reconfiguration is performed between the primary base station and the terminal device, and the radio bearer resource of the second base station is allocated to the default bearer of the data service.
  • the primary base station sends a reconfiguration complete message to the second base station to notify the second base station that the radio resource allocation is complete.
  • the primary base station modifies the radio access bearer and sends an E-RAB update indication message to the mobility management network element.
  • the E-RAB update indication message carries the IP address and TEID assigned by the second base station to the E-RAB corresponding to the default bearer of the data service. , So that the service data packet forwarded on the default bearer of the data service is forwarded through the second base station.
  • the primary base station waits for the E-RAB update indication confirmation message of the mobility management network element.
  • the interlock between the main base station and the mobility management network element makes the radio access bearer modification process and the voice service PDN connection establishment process unsuccessful, which severely reduces the service experience of the terminal equipment. What's more, the main base station and the terminal device will continue to retry after the process fails, and conflicts are generated during the retry process, resulting in interlocking, and finally the terminal device may fall back to the 2G/3G network.
  • Figure 3 is a schematic flow chart of a bearer modification method disclosed in an embodiment of the present invention, which is used to solve the wireless access bearer modification process of the terminal equipment in the access network equipment and Conflict in the registration process.
  • the bearer modification method may include the following steps.
  • the access network device determines that the terminal device has completed the complete registration process, or determines that the terminal device has not completed the complete registration process, and waits for the terminal device to complete the complete registration process.
  • the access network device may first determine whether the terminal device has completed the complete registration process, and in the case of determining that the terminal device has completed the complete registration process, it may determine that the terminal device has completed the complete registration process. In the case where it is determined that the terminal device has not completed the complete registration process, it can wait for the terminal device to complete the complete registration process.
  • the access network device can make judgments at any time, such as after the registration process is completed, or during the establishment of a voice service session, during the registration process, or during the establishment of a data service The judgment is made during the conversation, and it can also be judged at other times.
  • the access network devices here and later are the main access network devices in the DC network architecture.
  • the access network device determines that the terminal device completes the complete registration process, which may be that the terminal device has completed the complete registration process at the time of judgment, or the terminal device has completed the complete registration process within the first time after the judgment.
  • the complete registration process of the terminal device may be the attachment process and the PDN connection establishment process shown in FIG. 2 or other processes, which are not limited here.
  • the terminal device completing the complete registration process can be that the number of radio access bearers in the context of the terminal device is greater than or equal to (or greater than) the first threshold, or it can be that the context of the terminal device includes a parameter of a radio access bearer with a specific value.
  • the parameters of the radio access bearer can be one or more of QoS type, ARP and AMBR.
  • the QoS type can be QCI or 5QI.
  • the radio access bearer can have different names in different networks. For example, in a 5G network, the radio access bearer can be E-RAB or QoS flow. In a 4G network, the radio access bearer can be E-RAB.
  • the radio access bearer in the 3G network may be a radio access bearer (RAB), and may have other names in other networks, which is not limited in this embodiment.
  • the access network device may wait for the terminal device to complete the complete registration process.
  • the access network device can wait until the terminal device completes the complete registration process, that is, the number of radio access bearers in the context of the terminal device is greater than or equal to (or greater than) the first threshold, or it can be a terminal device
  • the parameter of a radio access bearer in the context of the terminal device is a specific value. It can also be that the number of radio access bearers in the context of the terminal device is greater than or equal to (or greater than) the first threshold, and the context of the terminal device includes a radio access bearer.
  • Incoming bearer parameters are specific values. In this way, the access network device only starts to modify the radio access bearer process after the terminal device completes the complete registration process, which can avoid conflicts.
  • the first time can be set as the waiting time for the access network device, that is, the access network device can wait for the first time if it determines that the terminal device has not completed the complete registration process. If the complete registration process is completed within the first time, the access network device determines that the terminal device completes the complete registration process. After the waiting time exceeds the first time, if the terminal device has not completed the complete registration process, the access network device may directly modify the radio access bearer of the terminal device without waiting.
  • a timer can be started. It is also possible to start a timer when the context of the terminal device is established on the access network device, or to start a timer when the first radio access bearer of the terminal device is established, and the access network device can also determine the current When the condition meets the trigger condition of the radio access bearer modification procedure, a timer is started. Afterwards, it can be detected in real time or periodically whether the terminal device has completed the complete registration process. In the case that the timer has not expired and the terminal device has completed the complete registration process, it can be determined that the terminal device has completed the complete registration process within the first time.
  • the radio access bearer of the terminal device can be directly modified, and the timer can be turned off at the same time, and no longer continues to count.
  • the radio access bearer of the terminal device can be directly modified, and the timer can be closed at the same time, and no longer counting and waiting.
  • the start time of the timer can be the first time. At this time, the timer expires, that is, the time of the timer is equal to zero.
  • the terminal device In the case that the terminal device must complete the complete registration process before it can modify the wireless access bearer of the terminal device, after judging that the terminal device has not completed the complete registration process, there is no need to start the timer, and the terminal can be detected in real time or periodically Whether the device completes the complete registration process, the wireless access bearer of the terminal device is not modified until it is detected that the terminal device completes the complete registration process.
  • the access network device modifies the radio access bearer.
  • the access network device determines that the terminal device completes the complete registration process, or determines that the terminal device has not completed the complete registration process, and waits for the terminal device to complete the complete registration process, and then can modify the wireless access bearer of the terminal device.
  • Modifying the radio access bearer of the terminal device can be sending a radio access bearer update indication message to the core network device, and receiving a radio access bearer update indication confirmation message from the core network device, so as to complete the radio access bearer of the terminal device modify.
  • the radio access bearer update indication message may carry the updated IP address and TEID of the access network device.
  • the updated access network device may be the second access network device, which indicates that the service data of the subsequent terminal device is forwarded through the second access network device.
  • the updated access network device may also be the access network device, indicating that the service data of the subsequent terminal device is forwarded through the access network device.
  • Modifying the radio access bearer of the terminal device can also be sending a radio access bearer update instruction message to the core network device and receiving a radio access bearer update instruction confirmation message from the core network device to complete the modification of the radio access bearer .
  • the radio access bearer update instruction message may carry the QoS parameters of the radio access bearer, so that the core network device can modify the QoS of the terminal device according to the QoS parameters.
  • FIG. 4 is a schematic flowchart of another bearer modification method disclosed in an embodiment of the present invention. As shown in Figure 4, the bearer modification method may include the following steps.
  • the access network device determines that the current condition satisfies the trigger condition of the radio access bearer modification procedure.
  • the access network device can determine whether the current condition meets the trigger condition of the radio access bearer modification process in real time or periodically. When it is determined that the current condition meets the trigger condition of the radio access bearer modification process, it can continue to determine whether the terminal device The complete registration process is completed, and the determination of whether the terminal device completes the complete registration process and related content can refer to the description of step 301, which will not be repeated here.
  • the access network equipment determines in real time whether the current conditions meet the triggering conditions of the radio access bearer modification process, the access network equipment can continue to determine the current Whether the condition meets the trigger condition of the radio access bearer modification process. If the access network device periodically determines whether the current condition meets the triggering condition of the radio access bearer modification process, the access network device can determine whether the current condition meets the triggering condition of the radio access bearer modification process after the next cycle arrives.
  • the radio access bearer modification process can be added for the second access network device.
  • the terminal device Before the second access network device is added, the terminal device only establishes a connection with the access network device, and the service data of the terminal device can only be forwarded through the access network device.
  • the terminal device After the second access network device is added, the terminal device establishes a connection with the access network device and the second access network device at the same time, and the service data of the terminal device can be forwarded through the access network device or through the second access network device. Forward. Specifically, whether one service data is forwarded through the access network device or the second access network device is determined by the access network device.
  • the radio access bearer modification process may also be modified for the second access network device. Before and after the modification of the second access network device, the terminal device and the access network device simultaneously establish a connection with the second access network device. After the second access network device is modified, part of the service data of the terminal device is forwarded and modified by the access network device to be forwarded through the second access network device, that is, the service data of the terminal device forwarded by the second access network device is added.
  • the radio access bearer modification process can also be deleted for the second access network device. Before the second access network device is deleted, the terminal device establishes a connection with the access network device and the second access network device at the same time. After the second access network device is deleted, the terminal device only establishes a connection with the access network device.
  • the radio access bearer modification process can also be changed for the second access network device.
  • the second access network device Before the second access network device is changed, the second access network device is the access network device 1. After the second access network device is changed, the second access network device is the access network device 2, and the access network device 1 and the access network device 2 are different access network devices. That is, the second access network device before and after the second access network device is changed is not the same access network device.
  • the network architecture shown in FIG. 1 includes at least three access network devices.
  • the radio access bearer modification process can also be QoS update.
  • the access network device cannot currently meet the QoS requirements of the radio access bearer, it triggers the radio access bearer modification process to modify the QoS parameters of the radio access bearer.
  • the current condition may be the current condition on the access network device.
  • the trigger condition can be that the load of the access network device is too heavy, it can also be that the load of the access network device is reduced, it can also be that the access network device cannot meet the QoS of the wireless access bearer, or it can be the signal of the second access network device
  • a specific service session can also be established for the terminal device, or the terminal device can be outside the coverage range of the current second access network device.
  • the access network device determines that the terminal device has completed the complete registration process, or determines that the terminal device has not completed the complete registration process, and waits for the terminal device to complete the complete registration process.
  • the access network device After the access network device determines that the current conditions meet the trigger conditions of the radio access bearer modification process, it can determine that the terminal device has completed the complete registration process, or that the terminal device has not completed the complete registration process, and wait for the terminal device to complete the complete registration process. Please describe in detail Refer to step 301, which will not be repeated here.
  • step 401 and step 402 may be relatively independent, and there is no necessary sequence. That is, step 401 and step 402 can be executed in parallel or successively.
  • Each time step 402 needs to be executed it can be directly determined whether step 402 has been executed by searching whether the mark information exists. If mark information is found, it indicates that step 402 has been executed and does not need to be executed again. If the tag information is not found, it indicates that step 402 is not performed, and step 402 is performed.
  • the access network device modifies the radio access bearer.
  • step 403 is the same as step 302.
  • step 302 which will not be repeated here.
  • the radio access bearer update instruction message may carry the second The IP address and TEID of the access network device.
  • the radio access bearer update instruction message may carry the IP address and TEID of the access network device.
  • the radio access bearer update indication message may carry QoS parameters of the radio access bearer.
  • the radio access bearer update indication message may also be carried by the IP address and TEID of the access network device.
  • FIG. 5 is a schematic flowchart of another bearer modification method disclosed in an embodiment of the present invention. As shown in Figure 5, the bearer modification method may include the following steps.
  • the access network device determines that the terminal device has completed the complete registration process, or determines that the terminal device has not completed the complete registration process, and waits for the terminal device to complete the complete registration process.
  • step 501 is the same as step 301.
  • step 301 For detailed description, please refer to step 301, which will not be repeated here.
  • the access network device determines that the current condition meets the trigger condition of the radio access bearer modification procedure.
  • the access network device After the access network device determines that the terminal device has completed the complete registration process, or determines that the terminal device has not completed the complete registration process, and waits for the terminal device to complete the complete registration process, it can determine whether the current conditions meet the trigger of the radio access bearer modification process in real time or periodically condition. In the case where it is determined that the current condition satisfies the trigger condition of the radio access bearer modification procedure, if it is determined that the current condition satisfies the trigger condition of the radio access bearer modification procedure, step 503 can be performed. For detailed description, please refer to the description of step 401. Add more details.
  • the access network equipment determines in real time whether the current conditions meet the triggering conditions of the radio access bearer modification process, the access network equipment can continue to determine the current Whether the condition meets the trigger condition of the radio access bearer modification process. If the access network device periodically determines whether the current condition meets the triggering condition of the radio access bearer modification process, the access network device can determine whether the current condition meets the triggering condition of the radio access bearer modification process after the next cycle arrives.
  • the access network device modifies the radio access bearer.
  • the access network device After the access network device determines that the current condition satisfies the trigger condition of the radio access bearer modification process, it modifies the radio access bearer. For a detailed description, please refer to the description of step 403, which will not be repeated here.
  • the conditions for the access network device to modify the radio access bearer are: the current condition meets the trigger condition of the radio access bearer modification process, and the terminal device is determined to complete the complete registration process, or the terminal device is determined The complete registration process is not completed and wait for the terminal device to complete the complete registration process. It can be seen that the modification of the radio access bearer by the access network device must be performed when the above two conditions are met, but the determination of the two conditions can be independent, and there is no inevitable sequence. There can also be a logical sequence, that is, one condition is met before another condition is determined.
  • FIG. 6 is a schematic flowchart of another bearer modification method disclosed in an embodiment of the present invention.
  • the bearer modification method shown in FIG. 6 is described using an EPS network as an example, and the mobility management network element is the core network device shown in FIG. 1.
  • the bearer modification method may include the following steps.
  • the terminal device triggers a complete registration process, and the complete registration process includes an attachment process and a PDN connection establishment process.
  • the terminal device sends an attach request to the mobility management network element through the first access network device.
  • the mobility management network element triggers an authentication process for the terminal device.
  • the mobility management network element obtains the identity of the terminal device, and the identity of the terminal device may be an IMSI.
  • the mobility management network element registers the information of the mobility management network element with the hometown user register, and obtains the subscription data on the hometown user register of the terminal device.
  • the terminal device requests the establishment of the first session, that is, the default bearer of the data service, the mobility management network element notifies the serving gateway and the data gateway to establish the default bearer of the data service, and the data gateway obtains the charging and policy rules corresponding to the data service.
  • the mobility management network element sends an initial context establishment request message to the first access network device to notify the first access network device to establish the context of the terminal device.
  • the message also carries the E corresponding to the default bearer of the data service to be established. -RAB.
  • the message also carries an attachment acceptance message that needs to be sent to the terminal device.
  • the first access network device replies with an initial context establishment response message to the mobility management network element, and the message carries the IP address and TEID allocated by the first access network device to the E-RAB corresponding to the default bearer of the data service.
  • the terminal device sends an attachment complete message to the mobility management network element.
  • the mobility management network element sends a bearer update request to the serving gateway, which is used to send the IP address and TEID of the access network device to the serving gateway.
  • the service gateway can optionally notify the data gateway of information such as the location of the terminal device.
  • the terminal device After the attachment process is completed, the terminal device triggers the PDN connection establishment process included in the complete registration process:
  • the terminal device sends a PDN connection establishment request to the mobility management network element, requesting to establish a second session, that is, the default bearer of the voice service.
  • the mobility management network element notifies the serving gateway and the data gateway to establish a default bearer for the voice service, and the data gateway obtains the charging and policy rules corresponding to the voice service.
  • the mobility management network element sends an E-RAB establishment request to the first access network device.
  • the E-RAB establishment request requests the first access network device to establish the E-RAB corresponding to the default bearer of the voice service.
  • the first access network device replies an E-RAB establishment response to the mobility management network element.
  • the E-RAB establishment response message carries the IP address and TEID allocated by the first access network device to the E-RAB corresponding to the default bearer of the voice service.
  • the mobility management network element notifies the serving gateway of the IP address and TEID of the E-RAB corresponding to the default bearer of the voice service for the first access network device, and that the default bearer of the voice service is successfully established.
  • the complete registration process may include an attachment process and a PDN connection establishment process.
  • the terminal device establishes the first session, that is, the default bearer of the voice service.
  • the terminal device establishes the second session, which is the default bearer of the data service.
  • the complete registration process may include a registration process, a first session establishment process, and a second session establishment process.
  • the first session establishment process is used to establish a voice service session
  • the second session establishment process is used to establish a data service. Conversation.
  • the complete registration process may include a registration process, a first session establishment process, and a second session establishment process.
  • the first session establishment process is used to establish a data service session
  • the second session establishment process is used to establish a voice service. Conversation.
  • the first access network device can execute 616 at any time after step 601, and 616 can be the following process:
  • the first access network device determines that the terminal device completes the complete registration process.
  • the first access network device may determine that the terminal device completes the complete registration process according to the number of E-RABs in the context of the terminal device established on the first access network device. When the number of E-RABs is greater than or equal to the threshold, the first access network device determines that the terminal device completes the complete registration process.
  • the threshold of the number of E-RABs is 2.
  • the first access network device considers that the terminal device has completed the complete registration process.
  • the first access network device may also determine that the terminal device completes the complete registration process according to the E-RAB parameter in the context of the terminal device established on the first access network device.
  • the E-RAB parameter is a specific value
  • the first access network device determines that the terminal device completes the complete registration process.
  • the context of the terminal device may include one or more E-RABs.
  • E-RAB parameters can include QoS type, ARP, AMBR or other characteristic parameters.
  • the QoS type is QCI in EPS networks and 5QI in 5G networks. For example, when one or more of the following conditions are met, the first access network device determines that the terminal device completes the complete registration process:
  • the context of the terminal device includes a session/PDN connection with an AMBR of 200Mbps-500Mbps;
  • the PDU session type is the IPv6 type.
  • the terminal device may have met the above conditions, and the complete registration process has been completed.
  • the first access network device can start a timer with a specific value, and within a specific period of time, the terminal device meets the above conditions to complete the complete registration process.
  • the first access network device determines that the terminal device has not completed the complete registration process, and waits for the terminal device to complete the complete registration process.
  • the first access network device waits for the number of E-RABs or parameters in the context of the local terminal device to satisfy the condition in step 616-a. Or the first access network device waits for more than a specific time period, for example, the timer in step 616-a expires.
  • the first access network device determines that the current condition meets the trigger condition of the E-RAB modification procedure.
  • the E-RAB modification process can be a QoS update process.
  • the first access network device can send an E-RAB modification indication message to the mobility management network element.
  • the message can carry the modified QoS parameters and receive the E-RAB returned by the mobility management network element.
  • -RAB modification indication confirmation message can be sent.
  • the E-RAB modification process can also be a process of adding a second access network device of the DC architecture, modifying a second access network device, deleting a second access network device, or changing a second access network device.
  • the device sends an E-RAB modification indication message to the mobility management network element, and the message carries the updated IP address and TEID of the access network device.
  • the updated IP address and TEID of the access network device may be the IP address and TEID of the first access network device or the second access network device.
  • the above-mentioned E-RAB modification indication message and E-RAB indication confirmation message are only examples, and the specific message name is not limited in this embodiment.
  • the message name when applied to a 5G network, the message name may be a packet data unit (packet data unit, PDU) session resource update indication message and a PDU session resource update confirmation message.
  • PDU packet data unit
  • the trigger condition can be that the load of the first access network device is too heavy, or the load of the first access network device is reduced, it can also be that the first access network device cannot meet the QoS of E-RAB, or it can be the second
  • the signal of the access network device meets the requirements, and a specific service session may also be established for the terminal device, and one or more combinations may also be such that the terminal device is outside the coverage of the current second access network device.
  • the QoS update process can be triggered to modify the QoS parameters of E-RAB; when the first access network device establishes a data service session Later, and when the signal strength of the second access network device meets the requirements, the process of adding or modifying the second access network device can be triggered to establish the forwarding channel of the service data packet to the second access network Device; when the signal strength of the second access network device does not meet the requirements, the first access network device can trigger the deletion process of the second access network device to establish the forwarding channel of the service data packet of the terminal device to the first access network device ; When the signal strength of the second access network device does not meet the requirements, and there is another second access network device whose signal strength meets the requirements, the second access network device can be triggered to change the process to transfer the service data packets of the terminal device The forwarding channel is established to another second access network device.
  • the first access network device's determination that the current condition satisfies the triggering condition of the E-RAB modification process may be executed before step 616, or may be executed after step 616, which is not limited in this embodiment.
  • the process of adding the second access network device, modifying the second access network device, deleting the second access network device, or changing the second access network device also involves the terminal device and the second access network device.
  • the access network device sends a second access network device addition request message to the second access network device, such as establishing an E-RAB corresponding to the default bearer of the data service to the second access network device.
  • the second access network device replies to the second access network device addition request confirmation message, which carries the IP address and TEID allocated by the second access network device for the E-RAB corresponding to the default bearer of the data service.
  • the first access network device notifies the second access network device that the wireless resource reconfiguration is complete.
  • the first access network device After the first access network device interacts with the second access network device, the first access network device initiates an E-RAB handover process to the mobility management network element.
  • the specific steps may be as follows:
  • the first access network device sends an E-RAB update instruction message to the mobility management network element, where the message carries the IP address and TEID allocated by the second access network device to the E-RAB corresponding to the default bearer of the data service.
  • the mobility management network element notifies the serving gateway to update the bearer.
  • the updated bearer may send the IP address and TEID assigned by the second access network device to the E-RAB corresponding to the default bearer of the data service to the serving gateway.
  • the mobility management network element sends an E-RAB update indication confirmation message to the first access network device.
  • the first access network device may not need to interact with the second access network device, but may directly perform steps 622-624 The E-RAB modification process shown.
  • step 622 that conflicts with the complete registration process of the terminal device. Therefore, in actual scenarios, the first access network device may perform steps 618-621 first, and the judgment of step 616 may be performed before step 622 is performed. The first access network device may also perform the judgment in step 616 before step 618, and trigger the entire process after the conditions are met. Step 616 may be performed at any time between step 608 and step 617. FIG. 6 illustrates an embodiment performed between step 610 and step 611.
  • Step 616 may be executed before step 617, may be executed after step 617, or may be executed simultaneously with step 617, and the execution time of step 616 and step 617 may not be limited.
  • Step 616 and step 617 are two conditions that must be met before modifying the radio access bearer in the embodiment corresponding to FIG. 4 and FIG. 5.
  • Steps 622 to 624 may be the steps of modifying the radio access bearer in the embodiment corresponding to FIG. 4 and FIG. 5, and it is only necessary to perform step 616 and step 617 before performing step 622.
  • the QoS update update process may be: the first access network device sends an E-RAB update indication message carrying QoS parameters to the mobility management network element; the mobility management network element notifies the serving gateway to update the bearer, and the updated bearer sends the updated QoS to the service Gateway: The mobility management network element sends an E-RAB update indication confirmation message to the first access network device.
  • FIG. 7 is a schematic flowchart of another bearer modification method disclosed in an embodiment of the present invention.
  • the bearer modification method shown in FIG. 7 is described using an EPS network as an example, and the mobility management network element is the core network device shown in FIG. 1.
  • the complete registration process in Figure 6 includes an attachment process and a PDN connection establishment process, while the complete registration process in Figure 7 only includes a service request process.
  • the bearer modification method may include the following steps.
  • the terminal device sends a service request message to the mobility management network element through the first access network device.
  • the mobility management network element triggers an authentication process for the terminal device.
  • the mobility management network element sends an initial context establishment request message to the first access network device.
  • the initial context request message also carries the E-RAB corresponding to the bearer of the terminal device to be established, and may include one or more E-RABs.
  • the initial context request message contains two E-RABs, namely the E-RAB for data services and the E-RAB for voice services.
  • the first access network device replies with an initial context establishment response message to the mobility management network element, and the message also carries the IP addresses allocated by the first access network device for the E-RAB of the data service and the E-RAB of the voice service. And TEID.
  • the mobility management network element notifies the serving gateway to update the bearer.
  • the mobility management network element sends a bearer update request to the serving gateway, which is used to send the IP address and TEID of the access network device corresponding to the bearer to the serving network element, and the serving gateway optionally notifies the data gateway of information such as the location of the user device.
  • the first access network device may trigger the modification of the E-RAB of the terminal device:
  • the first access network device determines that the terminal device completes the complete registration process.
  • the first access network device determines that the terminal device completes the complete registration process according to the number of E-RABs in the context of the terminal device that can be established on the first access network device. When the number of E-RABs is greater than or equal to the threshold, the first access network device determines that the terminal device completes the complete registration process.
  • the threshold of the number of E-RABs is 2.
  • the first access network device considers that the terminal device has completed the complete registration process.
  • the first access network device may also determine that the terminal device completes the complete registration process according to the E-RAB parameter in the context of the terminal device established on the first access network device.
  • the parameter including an E-RAB is a specific value
  • the first access network device determines that the terminal device completes the complete registration process.
  • E-RAB parameters can include QoS type, ARP, AMBR or other characteristic parameters.
  • the QoS type is QCI in EPS networks and 5QI in 5G networks. For example, when one or more of the following conditions are met, the first access network device determines that the terminal device completes the complete registration process:
  • the context of the terminal device includes a session/PDN connection with an AMBR of 200Mbps-500Mbps;
  • the PDU session type is the IPv6 type.
  • the terminal device has met the above conditions and the complete registration process has been completed.
  • step 708 to step 715 are the same as step 617 to step 624.
  • step 708 to step 715 are the same as step 617 to step 624.
  • the complete registration process can be a service request process, a tracking area update process, etc. Since in the service request process or the tracking area update process, the default bearer of the data service of the terminal device and the default bearer of the voice service have been established in the service request process or the tracking area update process, no PDN connection will be established Process, there is no conflict scenario.
  • the first access network device may determine that the terminal device meets the conditions for completing the complete registration process, and then directly modify the E-RAB.
  • Step 707 may correspond to step 402 in the embodiment corresponding to FIG. 4 or step 501 in the embodiment corresponding to FIG.
  • step 708 may correspond to step 401 in the embodiment corresponding to FIG. 4 or in the embodiment corresponding to FIG. Step 502, step 713-step 715 may correspond to step 403 in the embodiment corresponding to FIG. 4 or step 503 in the embodiment corresponding to FIG. 5. Since there is no conflicting process in the above process, as long as it is determined whether the terminal device has completed the complete registration process, it can be determined immediately that the terminal device satisfies the complete registration process without waiting.
  • FIG. 8 is a schematic structural diagram of an access network device disclosed in an embodiment of the present invention. Wherein, the access network device can be applied to the bearer modification methods shown in Figs. 3-7. As shown in Figure 8, the access network equipment may include:
  • the determining unit 801 is configured to determine that the terminal device has completed the complete registration process, or that the terminal device has not completed the complete registration process, and wait for the terminal device to complete the complete registration process; the modifying unit 802 is configured to modify the radio access bearer.
  • the determining unit 801 determining that the terminal device completes the complete registration process includes: determining that the terminal device has completed the complete registration process; or determining that the terminal device completes the complete registration process within the first time.
  • the terminal device completes the complete registration process including that the number of radio access bearers in the context of the terminal device is greater than or equal to the first threshold, and/or the context of the terminal device includes a parameter of a radio access bearer with a specific value .
  • the determining unit waits for the terminal device to complete the registration process.
  • the complete process includes that the number of radio access bearers in the context of the terminal device is greater than or equal to a first threshold, and the context of the terminal device includes a parameter of a radio access bearer with a specific value. , And one or more of the waiting time of the access network equipment exceeds the first time.
  • the parameters of the radio access bearer may be one or more of QoS type, ARP and AMBR.
  • the QoS type may be QCI or 5QI.
  • the determining unit 801 is further configured to determine that the current condition satisfies the trigger condition of the radio access bearer modification procedure before the modification unit 802 modifies the radio access bearer.
  • the radio access bearer modification procedure may include the second access network Device addition, second access network device modification, second access network device deletion, or second access network device change.
  • the modification unit is specifically configured to send a radio access bearer update instruction message to the mobility management network element, the radio access bearer update instruction message carries the IP address and TEID of the second access network device, and receives data from the mobile The radio access bearer update indication confirmation message of the management network element.
  • FIG. 9 is a schematic structural diagram of another access network device disclosed in an embodiment of the present invention.
  • the access network device can be applied to the bearer modification methods shown in Figs. 3-7.
  • the access network device may include a processor 901, a memory 902, a transceiver 903, and a connection line 904.
  • the memory 902 may exist independently, and the connection line 904 is connected to the processor 901.
  • the memory 902 may also be integrated with the processor 901.
  • the transceiver 903 is used to communicate with other devices, network elements or communication networks, such as Ethernet, radio access network (RAN), no WLAN, etc.
  • the connecting line 904 may include a path for transferring information between the above-mentioned components.
  • the memory 902 stores program instructions, and the processor 901 is configured to execute the program instructions stored in the memory 902. among them:
  • the processor 901 When the program instructions stored in the memory 902 are executed, the processor 901 is used to call the program instructions stored in the memory 902 to execute the operations performed by the determining unit 801 in the above-mentioned embodiment and the operations other than sending and receiving in the modification unit 802,
  • the device 903 is configured to perform the sending and receiving operations in the modification unit 802 in the foregoing embodiment.
  • the embodiment of the present invention also discloses a storage medium with a program stored on the storage medium, and when the program runs, the method for modifying the bearing as shown in FIGS. 3-7 is realized.
  • the processor in the embodiment of the present application may be a central processing unit (central processing unit, CPU), or other general-purpose processors, digital signal processors (digital signal processors, DSP), and application specific integrated circuits. (application specific integrated circuit, ASIC), field programmable gate array (field programmable gate array, FPGA) or other programmable logic devices, transistor logic devices, hardware components, or any combination thereof.
  • the general-purpose processor may be a microprocessor or any conventional processor.
  • the methods in the embodiments of the present application may be implemented in whole or in part by software, hardware, firmware, or any combination thereof.
  • software When implemented by software, it can be implemented in the form of a computer program product in whole or in part.
  • the computer program product includes one or more computer programs or instructions.
  • the computer may be a general-purpose computer, a special-purpose computer, a computer network, or other programmable devices.
  • the computer program or instruction may be stored in a computer-readable storage medium, or transmitted through the computer-readable storage medium.
  • the computer-readable storage medium may be any available medium that can be accessed by a computer or a data storage device such as a server integrating one or more available media.
  • the usable medium may be a magnetic medium, such as a floppy disk, a hard disk, or a magnetic tape; it may also be an optical medium, such as a compact disc read-only memory (CD-ROM), or a digital versatile disc (CD-ROM). DVD); it can also be a semiconductor medium, for example, solid state disk (SSD), random access memory (RAM), read-only memory (ROM), registers, etc.
  • An exemplary storage medium is coupled to the processor, so that the processor can read information from the storage medium and can write information to the storage medium.
  • the storage medium may also be an integral part of the processor.
  • the processor and the storage medium may be located in the ASIC.
  • the ASIC can be located in a network device or a terminal device.
  • the processor and the storage medium may also exist as discrete components in the sending device or the receiving device.
  • “at least one” refers to one or more, and “multiple” refers to two or more.
  • “And/or” describes the association relationship of the associated objects, indicating that there can be three relationships, for example, A and/or B, which can mean: A alone exists, A and B exist at the same time, and B exists alone, where A, B can be singular or plural.
  • the character “/” generally indicates that the associated objects before and after are an “or” relationship; in the formula of this application, the character “/” indicates that the associated objects before and after are a kind of "division” Relationship.

Landscapes

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

Abstract

本发明实施例公开一种承载修改方法及接入网设备，该方法中，当某些条件触发接入网设备修改终端设备的无线接入承载时，接入网设备需要确定终端设备完成注册完整流程，或者确定终端设备未完成注册完整流程，并等待终端设备完成注册完整流程之后，再修改无线接入承载。通过本申请实施例提供的方案，接入网设备对终端设备无线接入承载的修改不会与终端设备的注册完整流程发生冲突，不会影响终端设备的业务正常运行，从而可以提高终端设备的业务体验。

Description

一种承载修改方法及接入网设备 技术领域
本发明实施例涉及通信技术领域，尤其涉及一种承载修改方法及接入网设备。
背景技术
移动通信网络中，接入网设备可以主动触发对终端设备的无线接入承载的修改，如当接入网设备不能满足无线接入承载的服务质量(quality of service，QoS)时，修改无线接入承载的QoS参数。
还有一种典型场景是，双连接(dual connectivity，DC)组网架构中，终端设备可以同时与两个接入网设备建立连接，可以将这两个接入网设备中决策双连接建立的接入网设备称为主接入网设备，另一个接入网设备称为第二接入网设备或者从接入网设备。业务数据包可以通过主接入网设备或者第二接入网设备发送给终端设备，由主接入网设备决策业务数据包通过主接入网设备还是第二接入网设备转发。主接入网设备可以根据网络情况触发无线接入承载修改，如将业务数据包由主接入网设备转发修改为由第二接入网设备转发，反之亦然。
在现有网络中，终端设备执行注册完整流程接入网络，例如，注册完整流程包含注册流程和第二会话建立流程，在注册过程中创建第一会话，建立数据业务的缺省承载后，紧接着创建第二会话，建立语音业务的缺省承载。又例如，注册完整流程包含注册流程、第一会话建立流程和第二会话建立流程，终端设备通过注册流程注册到网络后，紧接着创建第一会话，建立数据业务的缺省承载后，紧接着创建第二会话，建立语音业务的缺省承载。
接入网设备不感知注册完整流程，在接入网设备上已经创建终端设备的无线接入承载，并且当前条件满足无线接入承载的修改条件时，接入网设备触发无线接入承载的修改。尤其为了尽快使终端设备能够享受5G高带宽和低时延的极致业务体验，接入网设备会尽早将终端设备的数据业务转移到第二接入网设备转发，这就加剧了和终端设备的注册完整流程之间的冲突矛盾。导致注册完整流程和上述无线接入承载修改冲突，如创建语音业务的第二会话的流程和上述无线接入承载修改冲突，主接入网设备和核心网设备互相锁死，信令流程无法成功，终端设备的业务无法正常进行，严重降低终端设备的业务体验。
发明内容
本发明实施例公开了一种承载修改方法及接入网设备，用于提高终端设备的业务体验。
第一方面公开一种承载修改方法，接入网设备确定终端设备完成注册完整流程，或者确定终端设备未完成注册完整流程，等待终端设备完成注册完整流程，之后修改无线接入承载。可见，由于终端设备的无线接入承载的修改是在确定终端设备完成注册完整流程或等待终端设备完成注册完整流程之后进行的，因此，不会与终端设备的注册完整流程发生冲突，不会影响终端设备的业务正常运行，从而可以提高终端设备的业务体验。
作为一种可能的实施方式，接入网设备确定终端设备完成注册完整流程，可以是确定 终端设备已经完成了注册完整流程，也可以是确定终端设备在第一时间内完成了注册完整流程。
作为一种可能的实施方式，终端设备完成注册完整流程可以包括终端设备的上下文中无线接入承载的数量大于或等于第一阈值，和/或终端设备的上下文中包含一个无线接入承载的参数为特定值。
作为一种可能的实施方式，接入网设备等待终端设备完成注册完整流程可以包括以下一项或者多项：终端设备的上下文中无线接入承载的数量大于或等于第一阈值；终端设备的上下文中包含一个无线接入承载的参数为特定值；接入网设备等待时间超过第一时间。
作为一种可能的实施方式，无线接入承载的参数可以为服务质量(quality of service，QoS)类型、分配和保留优先级(allocation and retention priority，ARP)和聚合最大带宽(aggregate maximum bit rate，AMBR)中的一种或多种。
作为一种可能的实施方式，QoS类型可以为服务质量分类标识(QoS class identifier，QCI)，也可以为5G服务质量标识(5G QoS identifier，5QI)。
作为一种可能的实施方式，接入网设备修改无线接入承载之前，还需要确定当前条件满足无线接入承载修改流程的触发条件，无线接入承载修改流程可以包括第二接入网设备添加、第二接入网设备修改、第二接入网设备删除、第二接入网设备改变或者QoS更新。
作为一种可能的实施方式，接入网设备可以向核心网设备发送携带第二接入网设备的网络协议(internet protocol，IP)地址和隧道端点标识(tunnel endpoint identifier，TEID)的无线接入承载更新指示消息，以及接收来自核心网设备的无线接入承载更新指示确认消息，以完成对无线接入承载的修改。
作为一种可能的实施方式，接入网设备可以向核心网设备发送携带无线接入承载的QoS参数的无线接入承载修改请求消息，以及接收来自核心网设备的无线接入承载修改响应消息，以完成对无线接入承载的修改。QoS参数可以为QCI、ARP、上下行带宽、QoS流标识(QoS flow identifier，QFI)、QoS满足与否指示等中的一个或者多个。QoS满足与否指示用于通知网络QoS没办法满足，以便网络调整QoS参数。
第二方面公开一种接入网设备，该接入网设备包括用于执行第一方面或第一方面的任一种实施例所公开的承载修改方法的单元。
第三方面公开一种接入网设备，该接入网设备可以包括处理器，处理器和存储器相互耦合，存储器用于存储计算机程序或指令，处理器用于执行存储器中存储的计算机程序或指令，使得接入网设备执行第一方面或第一方面的任一种实施例所公开的承载修改方法。
第四方面公开一种可读存储介质，该可读存储介质上存储有程序，当该程序运行时，实现如第一方面或第一方面的任一种实施例所公开的承载修改方法。
附图说明
图1是本发明实施例公开的一种网络架构示意图；
图2是接入网设备中可能出现的冲突流程示意图；
图3是本发明实施例公开的一种承载修改方法的流程示意图；
图4是本发明实施例公开的另一种承载修改方法的流程示意图；
图5是本发明实施例公开的又一种承载修改方法的流程示意图；
图6是本发明实施例公开的又一种承载修改方法的流程示意图；
图7是本发明实施例公开的又一种承载修改方法的流程示意图；
图8是本发明实施例公开的一种接入网设备的结构示意图；
图9是本发明实施例公开的另一种接入网设备的结构示意图。
具体实施方式
本发明实施例公开了一种承载修改方法及接入网设备，用于提高终端设备的业务体验。以下分别进行详细说明。
为了更好地理解本发明实施例公开的一种承载修改方法及接入网设备，下面先对本发明实施例使用的网络架构进行描述。请参阅图1，图1是本发明实施例公开的一种网络架构示意图。如图1所示，该网络架构可以包括终端设备、接入网设备、核心网设备。终端设备通过接入网设备接入核心网。核心网设备负责终端设备的位置管理、连接管理、安全认证等功能。
应用到DC架构，接入网设备可以为一个，也可以为多个，图1中只示意出了两个接入网设备。这一个或多个接入网设备中至少存在一个接入网设备决策双连接建立，与核心网设备之间存在信令接口，可以与核心网设备直接进行信令交互，这个接入网设备可以称为主接入网设备，如图1中所示的第一接入网设备。这一个或多个接入网设备中除主接入网设备之外的接入网设备可以称为第二接入设备或从接入网设备，如图1中所示的第二接入网设备。
上述网络架构对应的实际网络，可以是演进分组系统(evolved packet system，EPS)网络，对于演进通用陆地无线接入网(evolved universal terrestrial radio access network，E-UTRAN)，核心网设备可以是移动管理实体(mobility management entity，MME)。除此之外，EPS网络还可以包括服务网关(serving gateway，S-GW)，是终端设备的本地接入网关，负责接入技术相关的连接管理和数据转发。EPS网络还可以包括报文数据网络网关(packet data network gateway，PDN-GW)，是终端设备访问外部数据网络的网关。EPS网络还可以包括归属用户服务器(home subscriber server，HSS)，负责归属地用户签约信息的管理和维护。EPS网络还可以包括策略和计费规则功能(policy and charging rules function，PCRF)，负责策略控制、计费和QoS规则下发等。
上述网络架构对应实际网络，也可以是5G网络，核心网设备可以是接入和移动性管理功能(access and mobility management function，AMF)。除此之外，5G网络还可以包括会话管理功能(session management function，SMF)，负责终端设备的会话建立/更新/删除。5G网络还可以包括用户面功能(user plane function，UPF)，负责终端设备的业务数据包的转发。5G网络还可以包括统一数据管理(unified data management，UDM)，负责归属地用户签约信息的管理和维护。5G网络还可以包括策略和计费规则功能可以是策略控制功能(policy control function，PCF)，负责策略控制、计费和QoS规则下发等。
终端设备可以称为终端(Terminal)、用户设备(user equipment，UE)、移动台(mobile  station，MS)、移动终端(mobile terminal，MT)等。终端设备可以是手机(mobile phone)、平板电脑(Pad)、带无线收发功能的电脑、虚拟现实(virtual reality，VR)终端设备、增强现实(augmented reality，AR)终端设备、工业控制(industrial control)中的无线终端、无人驾驶(self driving)中的无线终端、远程手术(remote medical surgery)中的无线终端、智能电网(smart grid)中的无线终端、运输安全(transportation safety)中的无线终端、智慧城市(smart city)中的无线终端、智慧家庭(smart home)中的无线终端等等。本申请的实施例对终端设备所采用的具体技术和具体设备形态不做限定。
接入网设备是终端设备接入到核心网的接入设备，可以是基站(NodeB)、演进型基站(evolved NodeB，eNB)、无线网络控制器(radio network controller，RNC)、发送接收点(transmission reception point，TRP)、5G移动通信系统中的下一代基站(next generation NodeB，gNB)、未来移动通信系统中的基站或WiFi系统中的接入网设备等。本申请的实施例对无线接入网设备所采用的具体技术和具体设备形态不做限定。
为了更好地理解本发明实施例公开的一种承载修改方法及接入网设备，下面先对本发明实施例的应用场景进行描述。请参阅图2，图2是接入网设备中可能出现的冲突流程示意图。如图2所示，以EPS网络为例，终端设备触发注册完整流程，以便接入移动通信网络进行业务。图2对应的注册完整流程包括附着流程和报文数据网络(packet data network，PDN)连接建立流程。附着流程中，终端设备可以通过第一基站(即上述网络架构中的第一接入网设备)向移动管理网元发送附着请求，发起附着流程，以便接入移动通信网络。移动管理网元接收到附着请求之后，可以触发对终端设备的鉴权流程，确保终端设备的安全性。之后移动管理网元可以通过第一基站从终端设备获取终端设备的标识，终端设备的标识可以是国际移动用户识别码(international mobile subscriber identification number，IMSI)。之后移动管理网元可以向家乡用户寄存器注册移动管理网元的信息，以及从家乡用户寄存器获取终端设备的签约数据。移动管理网元接收到附着请求之后，还可以同时请求建立数据业务的缺省承载(第一会话)，可以通过服务网关和数据网关建立数据业务的缺省承载，同时数据网元与策略和计费规则功能之间建立数据业务的会话，以便获取数据业务对应的计费和策略规则。移动管理网元接收到来自家乡用户寄存器的终端设备的签约数据，以及接收到来自服务网关的数据业务的缺省承载建立响应之后，向第一基站发送初始上下文建立请求消息，初始上下文建立请求消息携带附着接受消息以及需要建立的数据业务的缺省承载对应的无线接入承载(E-UTRAN radio access bearer，E-RAB)。第一基站接收到来自移动管理网元的初始上下文建立请求消息之后，建立起终端设备的上下文，与终端设备之间进行无线资源重配置，向移动管理网元发送初始上下文建立响应，初始上下文建立响应携带为数据业务的缺省承载对应的E-RAB分配的第一基站的IP地址和TEID。终端设备与第一基站完成无线承载资源重配置之后，通过第一基站向移动管理网元发送附着完成消息。移动管理网元接收到初始上下文建立响应和附着完成消息之后，向服务网关发送更新承载请求，更新承载请求携带第一基站的IP地址和TEID。服务网关接收到来自移动管理网元的更新承载请求之后，可以向数据网关发送终端设备的位置等信息。之后终端设备附着完成，终端设备由空闲(idle)态切换为连接(connected)态，成功接入核心网，数据业务的缺省承载上转发的业务数据包由第一基站进行转发。
附着流程完成之后，终端设备紧接着触发第二会话的建立，发起PDN连接建立流程，用以建立语音业务的缺省承载。终端设备可以通过第一基站向移动管理网元发送PDN连接建立请求，发起PDN连接建立流程，请求建立语音业务的缺省承载。之后移动管理网元通过服务网关和数据网关建立语音业务的缺省承载，同时数据网元与策略和计费规则功能之间建立语音业务的会话，以便获取语音业务对应的计费和策略规则。之后移动管理网元向第一基站发送E-RAB建立请求，E-RAB建立请求携带PDN连接建立接受消息，请求第一基站建立语音业务的缺省承载对应的E-RAB，之后移动管理网元等待第一基站回复E-RAB建立响应消息。
第一基站通过附着流程的初始上下文请求消息建立终端设备的上下文，向移动管理网元发送初始上下文建立响应之后，在当前条件满足无线接入承载修改流程的触发条件时，第一基站触发无线接入承载修改流程。以DC架构为例，上述附着和PDN连接建立流程中的第一基站为主基站，主基站可以根据存储的DC策略判断当前条件是否满足第二基站添加条件，在判断出当前条件满足第二基站添加条件的情况下，触发第二基站添加流程。DC策略可以为第二基站信号强度满足要求时，数据业务由第二基站转发。主基站发起第二基站添加流程，将数据业务的缺省承载对应的E-RAB切换到第二基站。之后主基站与终端设备之间进行无线资源重配置，为数据业务的缺省承载分配第二基站的无线承载资源。之后主基站向第二基站发送重配置完成消息，通知第二基站，无线资源分配完成。之后主基站修改无线接入承载，向移动管理网元发送E-RAB更新指示消息，E-RAB更新指示消息携带第二基站为数据业务的缺省承载对应的E-RAB分配的IP地址和TEID，以便数据业务的缺省承载上转发的业务数据包通过第二基站转发。之后主基站等待移动管理网元的E-RAB更新指示确认消息。
可见，在注册完整流程中的无线接入承载修改流程，以及注册完整流程中终端设备发起的语音业务的PDN连接建立流程产生冲突的情况下，可能导致主基站等待移动管理网元回复E-RAB更新指示确认消息，主基站在收到移动管理网元发送的语音业务的缺省承载的E-RAB建立请求后，无法处理该消息。而移动管理网元等待主基站回复E-RAB建立响应消息，移动管理网元在收到主基站发送的E-RAB更新指示消息后，无法处理该消息。主基站和移动管理网元之间产生互锁，使得无线接入承载修改流程和语音业务的PDN连接建立流程都不能成功，以致严重降低了终端设备的业务体验。更甚至，主基站和终端设备在流程失败后会继续重试，而重试过程中又产生冲突导致互锁，最后终端设备可能回落到2G/3G网络。
基于图1所示的网络架构，请参阅图3，图3是本发明实施例公开的一种承载修改方法的流程示意图，用于解决接入网设备中终端设备的无线接入承载修改流程和注册流程的冲突。如图3所示，该承载修改方法可以包括以下步骤。
301、接入网设备确定终端设备完成注册完整流程，或者确定终端设备未完成注册完整流程，等待终端设备完成注册完整流程。
接入网设备可以先判断终端设备是否完成注册完整流程，在判断出终端设备完成注册完整流程的情况下，可以确定终端设备完成注册完整流程。在判断出终端设备未完成注册 完整流程的情况下，可以等待终端设备完成注册完整流程。接入网设备可以在任何时候进行判断，如可以在注册流程完成之后进行判断，也可以在建立语音业务的会话过程中进行判断，还可以在注册流程过程中进行判断，还可以在建立数据业务的会话过程中进行判断，还可以在其它时候进行判断。其中，此处以及后面的接入网设备即DC网络架构中的主接入网设备。
接入网设备确定终端设备完成注册完整流程，可以是在判断的时候终端设备已经完成了注册完整流程，也可以是在判断之后的第一时间内终端设备完成了注册完整流程。终端设备的注册完整流程可以为图2所示的附着流程和PDN连接建立流程，也可以为其它流程，在此不作限定。
终端设备完成注册完整流程可以为终端设备的上下文中无线接入承载的数量大于或等于(或者大于)第一阈值，也可以为终端设备的上下文中包含一个无线接入承载的参数为特定值。无线接入承载的参数可以为QoS类型、ARP和AMBR中的一种或多种。QoS类型可以为QCI，也可以为5QI。无线接入承载在不同的网络中可以具有不同的名称，比如在5G网络中，无线接入承载可以为E-RAB或者QoS流，在4G网络中，无线接入承载可以为E-RAB，在3G网络中无线接入承载可以为无线接入承载(radio access bearer，RAB)，在其它网络中可以具有其它名称，本实施例对此不作限定。
当接入网设备在判断的时候确认终端设备未完成注册完整流程，接入网设备可以等待终端设备完成注册完整流程。作为一种实现方式，接入网设备可以一直等待，直到终端设备完成注册完整流程，即终端设备的上下文中无线接入承载的数量大于或等于(或者大于)第一阈值，也可以为终端设备的上下文中包含一个无线接入承载的参数为特定值，还可以为终端设备的上下文中无线接入承载的数量大于或等于(或者大于)第一阈值，以及终端设备的上下文中包含一个无线接入承载的参数为特定值。这样，接入网设备只有等到终端设备完成注册完整流程之后，才启动修改无线接入承载流程，能够避免出现冲突。
上述一直等待，直到终端设备完成注册完整流程的实现方式虽然能有效避免冲突，但效率较低。作为另一种实现方式，可以为接入网设备设定第一时间作为等待时间，即接入网设备在判断出终端设备未完成注册完整流程的情况下，可以等待第一时间，若终端设备在第一时间内完成注册完整流程，则接入网设备确定终端设备完成注册完整流程。在等待时间超过第一时间之后，若终端设备还未完成注册完整流程，则接入网设备可以不继续等待，直接修改终端设备的无线接入承载。
在超过第一时间之后就不继续等待的情况下，在判断出终端设备未完成注册完整流程之后，可以启动一个定时器。也可以在接入网设备上建立终端设备的上下文时启动一个定时器，还可以在建立终端设备的第一个无线接入承载时就启动一个定时器，还可以在接入网设备判断出当前条件满足无线接入承载修改流程的触发条件的情况下，启动一个定时器。之后可以实时或周期性地检测终端设备是否完成注册完整流程，在定时器未超时，且检测到终端设备完成注册完整流程的情况下，可以确定在第一时间内终端设备完成了注册完整流程，可以直接修改终端设备的无线接入承载，同时可以关闭该计时器，并不再继续计时。在计时器超时，且还未检测到终端设备完成注册完整流程的情况下，可以直接修改终端设备的无线接入承载，同时可以关闭计时器，不再继续计时和等待。计时器的起始时间可以 为第一时间，此时，计时器超时即计时器的时间等于零。
在终端设备必须完成注册完整流程之后，才可以修改终端设备的无线接入承载的情况下，在判断出终端设备未完成注册完整流程之后，可以不必启动定时器，可以实时或周期性地检测终端设备是否完成注册完整流程，直到检测到终端设备完成注册完整流程，才修改终端设备的无线接入承载。
302、接入网设备修改无线接入承载。
接入网设备确定终端设备完成注册完整流程，或者确定终端设备未完成注册完整流程，等待终端设备完成注册完整流程之后，可以修改终端设备的无线接入承载。
修改终端设备的无线接入承载，可以为向核心网设备发送无线接入承载更新指示消息，接收来自核心网设备的无线接入承载更新指示确认消息，以便完成对终端设备的无线接入承载的修改。无线接入承载更新指示消息可以携带更新的接入网设备的IP地址和TEID。更新的接入网设备可以为第二接入网设备，表明后续终端设备的该业务数据通过第二接入网设备进行转发。更新的接入网设备也可以为该接入网设备，表明后续终端设备的该业务数据通过该接入网设备进行转发。
修改终端设备的无线接入承载，也可以为向核心网设备发送无线接入承载更新指示消息，以及接收来自核心网设备的无线接入承载更新指示确认消息，以完成对无线接入承载的修改。无线接入承载更新指示消息可以携带无线接入承载的QoS参数，以便核心网设备根据QoS参数对终端设备的QoS进行修改。
基于图1所示的网络架构，请参阅图4，图4是本发明实施例公开的另一种承载修改方法的流程示意图。如图4所示，该承载修改方法可以包括以下步骤。
401、接入网设备确定当前条件满足无线接入承载修改流程的触发条件。
接入网设备可以实时或周期性地判断当前条件是否满足无线接入承载修改流程的触发条件，在判断出当前条件满足无线接入承载修改流程的触发条件的情况下，可以继续判断终端设备是否完成注册完整流程，终端设备是否完成注册完整流程的判断以及相关的内容可以参考步骤301的描述，在此不加赘述。
在判断出当前条件不满足无线接入承载修改流程的触发条件的情况下，如果接入网设备实时判断当前条件是否满足无线接入承载修改流程的触发条件，则接入网设备可以继续判断当前条件是否满足无线接入承载修改流程的触发条件。如果接入网设备周期性地判断当前条件是否满足无线接入承载修改流程的触发条件，则接入网设备可以在下一个周期到达之后再判断当前条件是否满足无线接入承载修改流程的触发条件。
无线接入承载修改流程可以为第二接入网设备添加。第二接入网设备添加之前终端设备只与接入网设备建立连接，终端设备的业务数据只能通过接入网设备进行转发。第二接入网设备添加之后终端设备与接入网设备与第二接入网设备同时建立连接，终端设备的业务数据可以通过接入网设备进行转发，也可以通过第二接入网设备进行转发。具体地，一个业务数据通过接入网设备转发还是通过第二接入网设备转发，是由接入网设备决定的。
无线接入承载修改流程也可以为第二接入网设备修改，第二接入网设备修改前后终端设备与接入网设备与第二接入网设备同时建立连接。第二接入网设备修改之后，终端设备 的部分业务数据由接入网设备转发修改为通过第二接入网设备进行转发，即增加第二接入网设备转发的终端设备的业务数据。
无线接入承载修改流程还可以为第二接入网设备删除，第二接入网设备删除之前终端设备与接入网设备与第二接入网设备同时建立连接。第二接入网设备删除之后，终端设备只与接入网设备建立连接。
无线接入承载修改流程还可以为第二接入网设备改变。第二接入网设备改变之前，第二接入网设备为接入网设备1。第二接入网设备改变之后，第二接入网设备为接入网设备2，接入网设备1与接入网设备2是不同的接入网设备。即第二接入网设备改变前后的第二接入网设备不是同一个接入网设备。此时，图1所示的网络架构中至少包括三个接入网设备。
无线接入承载修改流程还可以为QoS更新。接入网设备在当前不能满足无线接入承载的QoS要求时，触发无线接入承载修改流程，用以修改无线接入承载的QoS参数。
当前条件可以为接入网设备上的当前条件。触发条件可以为接入网设备负载过重，也可以为接入网设备的负载变少，还可以为接入网设备无法满足无线接入承载的QoS，还可以为第二接入网设备信号满足要求，还可以为终端设备建立了特定业务的会话，还可以为终端设备处于当前第二接入网设备覆盖范围之外等。
402、接入网设备确定终端设备完成注册完整流程，或者确定终端设备未完成注册完整流程，等待终端设备完成注册完整流程。
在接入网设备确定当前条件满足无线接入承载修改流程的触发条件之后，可以确定终端设备完成注册完整流程，或者确定终端设备未完成注册完整流程，等待终端设备完成注册完整流程，详细描述请参考步骤301，在此不加赘述。
其中，步骤401与步骤402之间可以是相对独立的，没有必然的先后顺序。即步骤401与步骤402可以并行执行，也可以先后执行。
可以独立确定终端设备完成注册完整流程，或者确定终端设备未完成注册完整流程，等待终端设备完成注册完整流程，在确定出终端设备完成注册完整流程，或者确定出终端设备未完成注册完整流程，等待终端设备完成注册完整流程之后，可以使用一个标记位、标记标识等标记信息来表示已经确定出终端设备完成注册完整流程，或者已经确定出终端设备未完成注册完整流程，等待终端设备完成注册完整流程。在每次需要执行步骤402时，可以直接通过查找是否存在这个标记信息来确定步骤402是否已经执行，如果查找到标记信息，则表明步骤402已经执行完成，不需要再次执行。如果未查找到标记信息，则表明步骤402未执行，执行步骤402。
403、接入网设备修改无线接入承载。
其中，步骤403与步骤302相同，详细描述请参考步骤302，在此不加赘述。
此外，在无线接入承载修改流程为第二接入网设备添加、第二接入网设备修改或第二接入网设备改变的情况下，无线接入承载更新指示消息携带的可以是第二接入网设备的IP地址和TEID。在无线接入承载修改流程为第二接入网设备删除的情况下，无线接入承载更新指示消息携带的可以是接入网设备的IP地址和TEID。在无线接入承载修改流程为QoS更新的情况下，无线接入承载更新指示消息携带的可以是无线接入承载的QoS参数。在无线接入承载修改流程为第二接入网设备修改的情况下，无线接入承载更新指示消息携带的也 可以是接入网设备的IP地址和TEID。
基于图1所示的网络架构，请参阅图5，图5是本发明实施例公开的又一种承载修改方法的流程示意图。如图5所示，该承载修改方法可以包括以下步骤。
501、接入网设备确定终端设备完成注册完整流程，或者确定终端设备未完成注册完整流程，等待终端设备完成注册完整流程。
其中，步骤501与步骤301相同，详细描述请参考步骤301，在此不加赘述。
502、接入网设备确定当前条件满足无线接入承载修改流程的触发条件。
接入网设备确定终端设备完成注册完整流程，或者确定终端设备未完成注册完整流程，等待终端设备完成注册完整流程之后，可以实时或周期性地判断当前条件是否满足无线接入承载修改流程的触发条件。在判断出当前条件满足无线接入承载修改流程的触发条件的情况下，确定当前条件满足无线接入承载修改流程的触发条件，可以执行步骤503，详细描述可以参考步骤401的描述，在此不加赘述。
在判断出当前条件不满足无线接入承载修改流程的触发条件的情况下，如果接入网设备实时判断当前条件是否满足无线接入承载修改流程的触发条件，则接入网设备可以继续判断当前条件是否满足无线接入承载修改流程的触发条件。如果接入网设备周期性地判断当前条件是否满足无线接入承载修改流程的触发条件，则接入网设备可以在下一个周期到达之后再判断当前条件是否满足无线接入承载修改流程的触发条件。
503、接入网设备修改无线接入承载。
接入网设备确定当前条件满足无线接入承载修改流程的触发条件之后，修改无线接入承载，详细描述可以参考步骤403的描述，在此不加赘述。
通过图4和图5对应的描述可知，接入网设备修改无线接入承载的条件为：当前条件满足无线接入承载修改流程的触发条件，以及确定终端设备完成注册完整流程，或者确定终端设备未完成注册完整流程，等待终端设备完成注册完整流程。可见，接入网设备修改无线接入承载必须是在满足上述两个条件的情况下才进行的，但这两个条件的确定可以是独立的，没有必然的先后顺序。也可以是有逻辑顺序的，即在一个条件满足之后才确定另一个条件。
基于图1所示的网络架构，请参阅图6，图6是本发明实施例公开的又一种承载修改方法的流程示意图。其中，图6所示的承载修改方法是以EPS网络为例进行说明的，移动管理网元为图1中所示的核心网设备。如图6所示，该承载修改方法可以包括以下步骤。
601、终端设备触发注册完整流程，注册完整流程包含附着流程和PDN连接建立流程。在附着流程中，终端设备通过第一接入网设备向移动管理网元发送附着请求。
602、移动管理网元触发对终端设备的鉴权流程。
603、移动管理网元获取终端设备的标识，终端设备的标识可以为IMSI。
604、移动管理网元向家乡用户寄存器注册移动管理网元的信息，并且获取终端设备在家乡用户寄存器上的签约数据。
605、终端设备请求建立第一会话，即数据业务的缺省承载，移动管理网元通知服务网关和数据网关建立数据业务的缺省承载，数据网关获取数据业务对应的计费和策略规则。
606、移动管理网元发送初始上下文建立请求消息给第一接入网设备，通知第一接入网设备建立终端设备的上下文，该消息中还携带需要建立的数据业务的缺省承载对应的E-RAB。该消息中还携带需要发送给终端设备的附着接受消息。
607、第一接入网设备和终端设备之间进行无线资源重配置，分配该数据业务的缺省承载对应的无线承载资源。
608、第一接入网设备回复初始上下文建立响应消息给移动管理网元，该消息中携带第一接入网设备为数据业务的缺省承载对应的E-RAB分配的IP地址和TEID。
609、终端设备向移动管理网元发送附着完成消息。
610、移动管理网元向服务网关发送更新承载请求，用于将接入网设备的IP地址和TEID发送给服务网关。服务网关可选的将终端设备的位置等信息通知给数据网关。
附着流程完成后，终端设备触发注册完整流程中包含的PDN连接建立流程：
611、终端设备发送PDN连接建立请求给移动管理网元，请求建立第二会话，即语音业务的缺省承载。
612、移动管理网元通知服务网关和数据网关建立语音业务的缺省承载，数据网关获取语音业务对应的计费和策略规则。
613、移动管理网元向第一接入网设备发送E-RAB建立请求。
E-RAB建立请求请求第一接入网设备建立语音业务的缺省承载对应的E-RAB。
614、第一接入网设备和终端设备之间进行无线资源重配置，分配该语音业务的缺省承载对应的无线承载资源。
615、第一接入网设备向移动管理网元回复E-RAB建立响应。
E-RAB建立响应消息中携带第一接入网设备为语音业务的缺省承载对应的E-RAB分配的IP地址和TEID。移动管理网元通知服务网关第一接入网设备为语音业务的缺省承载对应的E-RAB的IP地址和TEID，语音业务的缺省承载建立成功。
需要说明的是，上述注册完整流程是针对EPS网络的一个例子，在实际网络中，注册完整流程有多种场景：
比如，注册完整流程可以包含附着流程和PDN连接建立流程，附着流程中终端设备建立第一会话，即语音业务的缺省承载。PDN连接建立流程中，终端设备建立第二会话，即数据业务的缺省承载。
又比如，针对5G网络，注册完整流程可以包含注册流程、第一会话建立流程和第二会话建立流程，第一会话建立流程用于建立语音业务的会话，第二会话建立流程用于建立数据业务的会话。
又比如，针对5G网络，注册完整流程可以包含注册流程、第一会话建立流程和第二会话建立流程，第一会话建立流程用于建立数据业务的会话，第二会话建立流程用于建立语音业务的会话。
第一接入网设备可以在步骤601之后的任一时间执行616，616可以为以下流程：
616-a、第一接入网设备确定终端设备完成注册完整流程。
第一接入网设备可以根据第一接入网设备上建立的终端设备的上下文中的E-RAB个数确定终端设备完成注册完整流程。当E-RAB个数大于或者等于阈值时，第一接入网设备确定终端设备完成注册完整流程。
如，E-RAB个数的阈值为2，当终端设备的上下文中的E-RAB个数大于或者等于2时，第一接入网设备认为终端设备完成注册完整流程。
第一接入网设备也可以根据第一接入网设备上建立的终端设备的上下文中的E-RAB的参数确定终端设备完成注册完整流程。当E-RAB的参数为特定值时，第一接入网设备确定终端设备完成注册完整流程。终端设备的上下文中可以包含一个或者多个E-RAB，当其中一个E-RAB的参数满足特定值时，则认为终端设备完成注册完整流程。E-RAB的参数可以包含QoS类型、ARP、AMBR或者其他特征参数，QoS类型在EPS网络为QCI，在5G网络为5QI。如当满足以下一种或者多种情况时，第一接入网设备确定终端设备完成注册完整流程：
当终端设备的上下文中包含QCI＝5(IMS Signalling)的E-RAB；或者
当终端设备的上下文中包含ARP的优先级为1-3的E-RAB；或者
当终端设备的上下文中包含AMBR为200Mbps-500Mbps的会话/PDN连接；或者
当终端设备的上下文中其他特征参数满足特定值，如PDU会话类型为IPv6类型。
具体地，终端设备可能已经满足上述条件，已经完成注册完整流程。或者第一接入网设备通过启动时长为特定值的定时器，在特定时长内，终端设备满足上述条件，完成注册完整流程。
616-b、第一接入网设备确定终端设备未完成注册完整流程，等待终端设备完成注册完整流程。
具体地，第一接入网设备等待本地的终端设备的上下文中的E-RAB个数或者参数满足步骤616-a中的条件。或者第一接入网设备等待超过特定时长，比如步骤616-a中的定时器超时。
617、第一接入网设备确定当前条件满足E-RAB修改流程的触发条件。
E-RAB修改流程可以为QoS更新流程，第一接入网设备可以向移动管理网元发送E-RAB修改指示消息，该消息中可以携带修改的QoS参数，以及接收移动管理网元返回的E-RAB修改指示确认消息。
E-RAB修改流程也可以为DC架构的第二接入网设备添加、第二接入网设备修改、第二接入网设备删除或第二接入网设备改变等流程，第一接入网设备向移动管理网元发送E-RAB修改指示消息，该消息中携带更新的接入网设备的IP地址和TEID。该更新的接入网设备的IP地址和TEID可以为第一接入网设备或第二接入网设备的IP地址和TEID。
进一步地，上述E-RAB修改指示消息和E-RAB指示确认消息只是示例，本实施例不限制具体消息名称。比如应用到5G网络时，该消息名称可以为分组数据单元(packet data unit，PDU)会话资源更新指示消息和PDU会话资源更新确认消息。
触发条件可以为第一接入网设备负载过重，也可以为第一接入网设备的负载变少，还可以为第一接入网设备无法满足E-RAB的QoS，还可以为第二接入网设备信号满足要求， 还可以为终端设备建立了特定业务的会话，还可以为终端设备处于当前第二接入网设备覆盖范围之外等一种或者多种组合。
举例来说，当第一接入网设备无法满足E-RAB的QoS要求时，可以触发QoS更新流程，用以修改E-RAB的QoS参数；当第一接入网设备建立了数据业务的会话后，并且第二接入网设备信号强度满足要求时，可以触发第二接入网设备增加或者第二接入网设备修改流程，用以将业务数据包的转发通道建立到第二接入网设备；当第二接入网设备信号强度不满足要求，第一接入网设备可以触发第二接入网设备删除流程，将终端设备的业务数据包的转发通道建立到第一接入网设备；当第二接入网设备信号强度不满足要求，且存在另一个第二接入网设备信号强度满足要求时，可以触发第二接入网设备改变流程，用以将终端设备的业务数据包的转发通道建立到另一个第二接入网设备。
需要说明的是第一接入网设备确定当前条件满足E-RAB修改流程的触发条件可以在步骤616之前执行，也可以在步骤616之后执行，本实施例对此不作限定。
需要说明的是，第二接入网设备添加、第二接入网设备修改、第二接入网设备删除或第二接入网设备改变等流程还涉及与终端设备和第二接入网设备的交互，E-RAB修改指示消息与移动管理网元交互的部分，具体以第二接入网设备增加流程为例：
618、接入网设备发送第二接入网设备添加请求消息给第二接入网设备，如将数据业务的缺省承载对应的E-RAB建立到第二接入网设备。
619、第二接入网设备回复第二接入网设备添加请求确认消息，该消息中携带第二接入网设备为数据业务的缺省承载对应的E-RAB分配的IP地址和TEID。
620、第一接入网设备和终端设备之间进行无线资源重配置，为该数据业务的缺省承载，分配到所述第二基站无线承载资源。
621、第一接入网设备通知第二接入网设备无线资源重配置完成。
第一接入网设备与第二接入网设备交互之后，第一接入网设备向移动管理网元发起E-RAB切换流程，具体步骤可以如下：
622、第一接入网设备向移动管理网元发送E-RAB更新指示消息，该消息中携带第二接入网设备为数据业务的缺省承载对应的E-RAB分配的IP地址和TEID。
623、移动管理网元通知服务网关更新承载。
该更新承载可以将第二接入网设备为数据业务的缺省承载对应的E-RAB分配的IP地址和TEID发送给服务网关。
624、移动管理网元发送E-RAB更新指示确认消息给第一接入网设备。
需要说明的是，若E-RAB修改流程的触发条件与第二接入网设备无关时，第一接入网设备可以不需要与第二接入网设备交互，而可以直接执行步骤622-624所示的E-RAB修改流程。
上述流程中，和终端设备的注册完整流程产生冲突的是步骤622，所以在实际场景中，第一接入网设备可以先执行步骤618-621，在执行步骤622之前可以进行步骤616的判断。第 一接入网设备也可以在步骤618之前进行步骤616的判断，满足条件后再触发整个流程。步骤616可以是在步骤608与步骤617之间的任何时候执行的，图6示意出了在步骤610与步骤611之间执行的一种实施例。
步骤616可以在步骤617之前执行，也可以在步骤617之后执行，也可以与步骤617同时执行，步骤616与步骤617的执行时间可以不作限定。步骤616和步骤617即图4和图5对应的实施例中的修改无线接入承载之前必须满足的两个条件。步骤622-步骤624可以是图4和图5对应的实施例中的修改无线接入承载的步骤，只需要在执行步骤622之前执行步骤616和步骤617即可。
QoS更新更新流程可以为：第一接入网设备向移动管理网元发送携带QoS参数的E-RAB更新指示消息；移动管理网元通知服务网关更新承载，该更新承载可以更新的QoS发送给服务网关；移动管理网元发送E-RAB更新指示确认消息给第一接入网设备。
其中，上述步骤的具体描述可以参考图2所示的描述，在此不加赘述。
基于图1所示的网络架构，请参阅图7，图7是本发明实施例公开的又一种承载修改方法的流程示意图。其中，图7所示的承载修改方法是以EPS网络为例进行说明的，移动管理网元为图1中所示的核心网设备。其中，图6中的注册完整流程包括附着流程和PDN连接建立流程，而图7中的注册完整流程只包括服务请求流程。如图7所示，该承载修改方法可以包括以下步骤。
701、终端设备通过第一接入网设备向移动管理网元发送服务请求消息。
702、移动管理网元触发对终端设备的鉴权流程。
703、移动管理网元发送初始上下文建立请求消息给第一接入网设备。
初始上下文请求消息还携带需要建立的终端设备的承载对应的E-RAB，可以包含一个或者多个E-RAB。比如初始上下文请求消息中包含2个E-RAB，分别为数据业务的E-RAB和语音业务的E-RAB。
704、第一接入网设备和终端设备之间进行无线资源重配置，分配该承载对应的无线承载资源。
705、第一接入网设备回复初始上下文建立响应消息给移动管理网元，该消息中还携带第一接入网设备为数据业务的E-RAB和语音业务的E-RAB各分配的IP地址和TEID。
706、移动管理网元通知服务网关更新承载。
移动管理网元向服务网关发送更新承载请求，用于将承载对应的接入网设备的IP地址和TEID发送给服务网元，服务网关可选的将用户设备的位置等信息通知给数据网关。
第一接入网设备可能触发对终端设备的E-RAB的修改：
707、第一接入网设备确定终端设备完成注册完整流程。
第一接入网设备根据可以第一接入网设备上建立的终端设备的上下文中的E-RAB个数确定终端设备完成注册完整流程。当E-RAB个数大于或者等于阈值时，第一接入网设备确定终端设备完成注册完整流程。
如，E-RAB个数的阈值为2，当终端设备的上下文中的E-RAB个数大于或者等于2时， 第一接入网设备认为终端设备完成注册完整流程。
第一接入网设备也可以根据第一接入网设备上建立的终端设备的上下文中的E-RAB的参数确定终端设备完成注册完整流程。当包含一个E-RAB的参数为特定值时，第一接入网设备确定终端设备完成注册完整流程。E-RAB的参数可以包含QoS类型、ARP、AMBR或者其他特征参数，QoS类型在EPS网络为QCI，在5G网络为5QI。如当满足以下一种或者多种情况时，第一接入网设备确定终端设备完成注册完整流程：
当终端设备的上下文中包含QCI＝5(IMS Signalling)的E-RAB；或者
当终端设备的上下文中包含ARP的优先级为1-3的E-RAB；或者
当终端设备的上下文中包含AMBR为200Mbps-500Mbps的会话/PDN连接；或者
当终端设备的上下文中其他特征参数满足特定值，如PDU会话类型为IPv6类型。
本实施例中，终端设备已经满足上述条件，已经完成注册完整流程。
其中，步骤708-步骤715与步骤617-步骤624相同，详细描述请参考图6对应的描述，在此不加赘述。
上述流程中，注册完整流程可以为服务请求流程、跟踪区域更新流程等。由于在服务请求流程或者跟踪区域更新流程中，终端设备的数据业务的缺省承载和语音业务的缺省承载在服务请求流程或跟踪区域更新流程中都已经建立，因此，不会有PDN连接建立流程，也就不存在冲突场景。第一接入网设备在确定当前条件满足E-RAB修改流程的触发条件之前、之后或同时，可以确定终端设备满足完成注册完整流程的条件，之后即可直接对E-RAB进行修改。步骤707可以对应于图4对应的实施例中的步骤402或者图5对应的实施例中的步骤501，步骤708可以对应于图4对应的实施例中的步骤401或者图5对应的实施例中的步骤502，步骤713-步骤715可以对应于图4对应的实施例中的步骤403或者图5对应的实施例中的步骤503。上述流程中由于不存在冲突流程，因此，只要一判断终端设备是否完成注册完整流程，就可以立刻确定出终端设备满足完成注册完整流程，不需要等待。
基于图1所示的网络架构，以及上述实施例中的承载修改方法的同一构思，请参阅图8，图8是本发明实施例公开的一种接入网设备的结构示意图。其中，该接入网设备可以应用于上述图3-图7所示的承载修改方法中。如图8所示，该接入网设备可以包括：
确定单元801，用于确定终端设备完成注册完整流程，或者确定终端设备未完成注册完整流程，等待终端设备完成注册完整流程；修改单元802，用于修改无线接入承载。
在一个实施例中，确定单元801确定终端设备完成注册完整流程包括：确定终端设备已经完成注册完整流程；或者确定终端设备在第一时间内完成注册完整流程。
在一个实施例中，终端设备完成注册完整流程包括终端设备的上下文中无线接入承载的数量大于或等于第一阈值，和/或终端设备的上下文中包含一个无线接入承载的参数为特定值。
在一个实施例中，确定单元等待终端设备完成注册完整流程包括终端设备的上下文中无线接入承载的数量大于或等于第一阈值，终端设备的上下文中包含一个无线接入承载的参数为特定值，以及接入网设备等待时间超过第一时间中的一项或者多项。
在一个实施例中，无线接入承载的参数可以为QoS类型、ARP和AMBR中的一种或多种。
在一个实施例中，QoS类型可以为QCI或5QI。
在一个实施例中，确定单元801，还用于修改单元802修改无线接入承载之前，确定当前条件满足无线接入承载修改流程的触发条件，无线接入承载修改流程可以包括第二接入网设备添加、第二接入网设备修改、第二接入网设备删除或者第二接入网设备改变。
在一个实施例中，修改单元，具体用于向移动管理网元发送无线接入承载更新指示消息，无线接入承载更新指示消息携带第二接入网设备的IP地址和TEID，以及接收来自移动管理网元的无线接入承载更新指示确认消息。
有关上述确定单元801和修改单元802更详细的描述可以直接参考上述图3-图7所示的方法实施例中接入网设备的相关描述直接得到，这里不加赘述。
基于图1所示的网络架构，请参阅图9，图9是本发明实施例公开的另一种接入网设备的结构示意图。其中，该接入网设备可以应用于上述图3-图7所示的承载修改方法中。如图9所示，该接入网设备可以包括处理器901、存储器902、收发器903和连接线904。存储器902可以是独立存在，连接线904与处理器901相连接。存储器902也可以和处理器901集成在一起。收发器903，用于与其他设备、网元或通信网络通信，如以太网，无线接入网(RAN)，无WLAN等。连接线904可包括一通路，在上述组件之间传送信息。其中，存储器902中存储程序指令，处理器901用于执行存储器902中存储的程序指令。其中：
存储器902中存储的程序指令被执行时，该处理器901用于调用存储器902存储的程序指令执行上述实施例中确定单元801执行的操作以及修改单元802中除发送和接收之外的操作，收发器903用于执行上述实施例中修改单元802中的发送和接收的操作。
本发明实施例还公开了一种存储介质，该存储介质上存储有程序，该程序运行时，实现如图3-图7所示的承载修改方法。
可以理解的是，本申请的实施例中的处理器可以是中央处理单元(central processing unit，CPU)，还可以是其他通用处理器、数字信号处理器(digital signal processor，DSP)、专用集成电路(application specific integrated circuit，ASIC)、现场可编程门阵列(field programmable gate array，FPGA)或者其他可编程逻辑器件、晶体管逻辑器件，硬件部件或者其任意组合。通用处理器可以是微处理器，也可以是任何常规的处理器。
本申请的实施例中的方法可以全部或部分地通过软件、硬件、固件或者其任意组合来实现。当使用软件实现时，可以全部或部分地以计算机程序产品的形式实现。所述计算机程序产品包括一个或多个计算机程序或指令。在计算机上加载和执行所述计算机程序或指令时，全部或部分地执行本申请实施例所述的流程或功能。所述计算机可以是通用计算机、专用计算机、计算机网络、或者其他可编程装置。所述计算机程序或指令可以存储在计算机可读存储介质中，或者通过所述计算机可读存储介质进行传输。所述计算机可读存储介质可以是计算机能够存取的任何可用介质或者是集成一个或多个可用介质的服务器等数据存储设备。所述可用介质可以是磁性介质，例如，软盘、硬盘、磁带；也可以是光介质，例如，光盘只读存储器(compact disc read-only memory，CD-ROM)，数字通用光盘(digital versatile disc，DVD)；还可以是半导体介质，例如，固态硬盘(solid state disk，SSD),随 机存取存储器(random access memory，RAM)、只读存储器(read-only memory，ROM)和寄存器等。
一种示例性的存储介质耦合至处理器，从而使处理器能够从该存储介质读取信息，且可向该存储介质写入信息。当然，存储介质也可以是处理器的组成部分。处理器和存储介质可以位于ASIC中。另外，该ASIC可以位于网络设备或终端设备中。当然，处理器和存储介质也可以作为分立组件存在于发送设备或接收设备中。
在本申请的各个实施例中，如果没有特殊说明以及逻辑冲突，不同的实施例之间的术语和/或描述具有一致性、且可以相互引用，不同的实施例中的技术特征根据其内在的逻辑关系可以组合形成新的实施例。
本申请中，“至少一个”是指一个或者多个，“多个”是指两个或两个以上。“和/或”，描述关联对象的关联关系，表示可以存在三种关系，例如，A和/或B，可以表示：单独存在A，同时存在A和B，单独存在B的情况，其中A,B可以是单数或者复数。在本申请的文字描述中，字符“/”，一般表示前后关联对象是一种“或”的关系；在本申请的公式中，字符“/”，表示前后关联对象是一种“相除”的关系。
可以理解的是，在本申请的实施例中涉及的各种数字编号仅为描述方便进行的区分，并不用来限制本申请的实施例的范围。上述各过程的序号的大小并不意味着执行顺序的先后，各过程的执行顺序应以其功能和内在逻辑确定。
以上所述的具体实施方式，对本申请的目的、技术方案和有益效果进行了进一步详细说明，所应理解的是，以上所述仅为本申请的具体实施方式而已，并不用于限定本申请的保护范围，凡在本申请的技术方案的基础之上，所做的任何修改、等同替换、改进等，均应包括在本申请的保护范围之内。

Claims (18)

  1. 一种承载修改方法，其特征在于，包括：
    接入网设备确定终端设备完成注册完整流程，或者确定所述终端设备未完成注册完整流程，等待所述终端设备完成注册完整流程；
    所述接入网设备修改所述终端设备的无线接入承载。
  2. 根据权利要求1所述的方法，其特征在于，所述接入网设备确定终端设备完成注册完整流程包括：
    所述接入网设备确定所述终端设备已经完成注册完整流程；或者，
    所述接入网设备确定所述终端设备在第一时间内完成注册完整流程。
  3. 根据权利要求2所述的方法，其特征在于，所述终端设备完成注册完整流程包括：
    所述终端设备的上下文中无线接入承载的数量大于或等于第一阈值；和/或
    所述终端设备的上下文中包含一个无线接入承载的参数为特定值。
  4. 根据权利要求1所述的方法，其特征在于，所述接入网设备等待所述终端设备完成注册完整流程包括以下一项或者多项：
    所述终端设备的上下文中无线接入承载的数量大于或等于第一阈值；
    所述终端设备的上下文中包含一个无线接入承载的参数为特定值；
    所述接入网设备等待时间超过第一时间。
  5. 根据权利要求3或4所述的方法，其特征在于，所述无线接入承载的参数为服务质量QoS类型、分配和保留优先级ARP和聚合最大带宽AMBR中的一种或多种。
  6. 根据权利要求5所述的方法，其特征在于，所述QoS类型为服务质量分类标识QCI或5G服务质量标识5QI。
  7. 根据权利要求1-6任一项所述的方法，其特征在于，所述接入网设备修改无线接入承载之前，所述方法还包括：
    所述接入网设备确定当前条件满足无线接入承载修改流程的触发条件，所述无线接入承载修改流程包括第二接入网设备添加、第二接入网设备修改、第二接入网设备删除或者第二接入网设备改变。
  8. 根据权利要求1-6任一项所述的方法，其特征在于，所述接入网设备修改无线接入承载包括：
    所述接入网设备向核心网设备发送无线接入承载更新指示消息，所述无线接入承载更新指示消息携带第二接入网设备的网络协议IP地址和隧道端点标识TEID；
    所述接入网设备接收来自所述核心网设备的无线接入承载更新指示确认消息。
  9. 一种接入网设备，其特征在于，包括：
    确定单元，用于确定终端设备完成注册完整流程，或者确定所述终端设备未完成注册完整流程，等待所述终端设备完成注册完整流程；
    修改单元，用于修改所述终端设备的无线接入承载。
  10. 根据权利要求9所述的接入网设备，其特征在于，所述确定单元确定终端设备完成注册完整流程包括：
    确定所述终端设备已经完成注册完整流程；或者，
    确定所述终端设备在第一时间内完成注册完整流程。
  11. 根据权利要求10所述的接入网设备，其特征在于，所述终端设备完成注册完整流程包括以下一项或多项：
    所述终端设备的上下文中无线接入承载的数量大于或等于第一阈值；
    所述终端设备的上下文中包含一个无线接入承载的参数为特定值。
  12. 根据权利要求9所述的接入网设备，其特征在于，所述确定单元等待所述终端设备完成注册完整流程包括以下一项或者多项：
    所述终端设备的上下文中无线接入承载的数量大于或等于第一阈值；
    所述终端设备的上下文中包含一个无线接入承载的参数为特定值；
    所述接入网设备等待时间超过第一时间。
  13. 根据权利要求11或12所述的接入网设备，其特征在于，所述无线接入承载的参数为QoS类型、ARP和AMBR中的一种或多种。
  14. 根据权利要求13所述的接入网设备，其特征在于，所述QoS类型为QCI或5QI。
  15. 根据权利要求9-14任一项所述的接入网设备，其特征在于，所述确定单元，还用于所述修改单元修改无线接入承载之前，确定当前条件满足无线接入承载修改流程的触发条件，所述无线接入承载修改流程包括第二接入网设备添加、第二接入网设备修改、第二接入网设备删除或者第二接入网设备改变。
  16. 根据权利要求9-14任一项所述的接入网设备，其特征在于，所述修改单元具体用于：
    向核心网设备发送无线接入承载更新指示消息，所述无线接入承载更新指示消息携带第二接入网设备的IP地址和TEID；
    接收来自所述核心网设备的无线接入承载更新指示确认消息。
  17. 一种接入网设备，其特征在于，包括处理器和接口电路，所述接口电路用于接收 来自所述接入网设备之外的其它通信设备的信号并传输至所述处理器或将来自所述处理器的信号发送给所述接入网设备之外的其它通信设备，所述处理器通过逻辑电路或执行代码指令实现如权利要求1-8任一项所述的方法。
  18. 一种计算机可读存储介质，其特征在于，所述存储介质中存储有程序或指令，当所述程序或指令被运行时，实现如权利要求1-8任一项所述的方法。
PCT/CN2020/090225 2019-05-15 2020-05-14 一种承载修改方法及接入网设备 WO2020228770A1 (zh)

Priority Applications (2)

Application Number Priority Date Filing Date Title
EP20806781.9A EP3962164B1 (en) 2019-05-15 2020-05-14 Bearer modification method and access network device
US17/525,206 US20220078677A1 (en) 2019-05-15 2021-11-12 Bearer Modification Method and Access Network Device

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201910406656.6A CN111954269B (zh) 2019-05-15 2019-05-15 一种承载修改方法及接入网设备
CN201910406656.6 2019-05-15

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US17/525,206 Continuation US20220078677A1 (en) 2019-05-15 2021-11-12 Bearer Modification Method and Access Network Device

Publications (1)

Publication Number Publication Date
WO2020228770A1 true WO2020228770A1 (zh) 2020-11-19

Family

ID=73288974

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2020/090225 WO2020228770A1 (zh) 2019-05-15 2020-05-14 一种承载修改方法及接入网设备

Country Status (4)

Country Link
US (1) US20220078677A1 (zh)
EP (1) EP3962164B1 (zh)
CN (1) CN111954269B (zh)
WO (1) WO2020228770A1 (zh)

Families Citing this family (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20220361046A1 (en) * 2019-07-25 2022-11-10 Telefonaktiebolaget Lm Ericsson (Publ) Connecting network agnostic devices
US20240146848A1 (en) * 2022-10-31 2024-05-02 Adtran, Inc. Systems and methods for monitoring voice services

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN103491602A (zh) * 2012-06-11 2014-01-01 苏州简约纳电子有限公司 一种优化会话管理流程的方法及终端设备
EP3133864A1 (en) * 2014-04-14 2017-02-22 ZTE Corporation Method and system for controlling access of csg in dual-connection architecture
CN108093473A (zh) * 2016-11-21 2018-05-29 大唐移动通信设备有限公司 一种注册方法及mme
CN108781391A (zh) * 2016-02-16 2018-11-09 夏普株式会社 终端装置、移动性管理实体mme以及通信控制方法
CN109412771A (zh) * 2018-04-04 2019-03-01 华为技术有限公司 通信方法和装置

Family Cites Families (17)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US8254364B2 (en) * 2007-04-25 2012-08-28 Qualcomm Incorporated Route protocol
US20130183971A1 (en) * 2011-08-11 2013-07-18 Interdigital Patent Holdings, Inc. Systems And/Or Methods For Providing Relay Mobility
WO2014110410A1 (en) * 2013-01-11 2014-07-17 Interdigital Patent Holdings, Inc. User-plane congestion management
US9444745B2 (en) * 2013-03-08 2016-09-13 Blackberry Limited Sending data rate information to a wireless access network node
WO2014166884A1 (en) * 2013-04-08 2014-10-16 Telefonaktiebolaget L M Ericsson (Publ) Congestion aware throughput targets
EP2984866B1 (en) * 2013-04-08 2019-12-18 Nokia Solutions and Networks Oy Control of offloading by the network
UA116025C2 (uk) * 2013-07-04 2018-01-25 Нек Корпорейшн Система, спосіб і пристрій зв'язку
KR20150048611A (ko) * 2013-10-28 2015-05-07 삼성전자주식회사 이동성에 강인한 그룹 통신을 위한 방법 및 장치
WO2015108291A1 (en) * 2014-01-17 2015-07-23 Lg Electronics Inc. Bearer setup method and apparatus in wierless communication system supporting dual connectivity
EP3235173B1 (en) * 2014-12-18 2020-06-17 Nokia Solutions and Networks Oy Policy and charging control for groups
CN106162705B (zh) * 2015-03-31 2020-02-04 电信科学技术研究院 一种控制用户面承载建立的方法及设备
US10560914B2 (en) * 2016-01-18 2020-02-11 Telefonaktiebolaget Lm Ericsson (Publ) Tracking area and user plane mapping for control plane/user plane split
WO2018006250A1 (zh) * 2016-07-04 2018-01-11 华为技术有限公司 覆盖增强ce功能的实现方法及设备
EP3952448B1 (en) * 2016-11-04 2023-04-05 Huawei Technologies Co., Ltd. Inter-network change method and terminal
CN110366270B (zh) * 2018-04-10 2021-08-13 华为技术有限公司 通信方法及装置
KR102452958B1 (ko) * 2018-04-23 2022-10-11 삼성전자 주식회사 X2 핸드오버 동안 베어러 관리 방법 및 장치
US11490291B2 (en) * 2019-03-28 2022-11-01 Ofinno, Llc Handover for closed access group

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN103491602A (zh) * 2012-06-11 2014-01-01 苏州简约纳电子有限公司 一种优化会话管理流程的方法及终端设备
EP3133864A1 (en) * 2014-04-14 2017-02-22 ZTE Corporation Method and system for controlling access of csg in dual-connection architecture
CN108781391A (zh) * 2016-02-16 2018-11-09 夏普株式会社 终端装置、移动性管理实体mme以及通信控制方法
CN108093473A (zh) * 2016-11-21 2018-05-29 大唐移动通信设备有限公司 一种注册方法及mme
CN109412771A (zh) * 2018-04-04 2019-03-01 华为技术有限公司 通信方法和装置

Non-Patent Citations (5)

* Cited by examiner, † Cited by third party
Title
ERICSSON ET AL.: "Secondary RAT related data usage reporting", SA WG2 MEETING #122-BIS, S2-176695, 25 August 2017 (2017-08-25), XP051336004, DOI: 20200803155435A *
ERICSSON: "Specifying handling of Race Condition between E-RAB Setup and intra-E-UTRAN EN-DC related procedures", 3GPP TSG-RAN WG3 MEETING #104, R3-193013, 4 May 2019 (2019-05-04), XP051713201, DOI: 20200803155207A *
ERICSSON: "Specifying handling of Race Condition between E-RAB Setup and intra-E-UTRAN EN-DC related procedures.", 3GPP TSG-RAN WG3 MEETING #104, R3-193094, 4 May 2019 (2019-05-04), XP051713281, DOI: 20200803155101A *
NEC: "Correction on E-RAB Release procedure during race condition between MME and eNB", 3GPP TSG-RAN WG3 #69, R3-102291, 27 August 2010 (2010-08-27), XP050453157, DOI: 20200803155304A *
See also references of EP3962164A4 *

Also Published As

Publication number Publication date
CN111954269B (zh) 2022-11-01
EP3962164A1 (en) 2022-03-02
EP3962164A4 (en) 2022-06-29
US20220078677A1 (en) 2022-03-10
CN111954269A (zh) 2020-11-17
EP3962164B1 (en) 2023-07-05

Similar Documents

Publication Publication Date Title
US11323942B2 (en) Handover method and apparatus
US10368275B2 (en) Method and apparatus for UE mobility in a small cell system
US20200383005A1 (en) QOS Flow Control Method and Apparatus
CN111629450B (zh) 一种数据传输方法、相关设备以及存储介质
TWI754074B (zh) 測量間隔配置方法、裝置、設備、終端及系統
US20220174575A1 (en) Data transmission method, terminal device, and network device
US10368268B2 (en) Methods, systems and devices for supporting local breakout in small cell architecture
JP2007536787A (ja) Ｉｐアドレス設定の遅延によるハンドオーバー実行方法
JP2022109906A (ja) 通信方法及び通信装置
WO2020001562A1 (zh) 一种通信方法及装置
WO2021233264A1 (zh) 一种通信方法、设备及系统
US10091761B2 (en) Apparatus and method for paging in wireless communication system
EP3445081B1 (en) Flow-based bearer management method and device
US11751096B2 (en) Congestion control method and device, and base station
WO2016015244A1 (zh) 多通信制式传输方法及装置
US20220078677A1 (en) Bearer Modification Method and Access Network Device
WO2015188357A1 (zh) 一种控制承载切换的设备和控制方法
WO2022017285A1 (zh) 报文转发方法、装置及系统
WO2019223639A1 (zh) 无线通信方法和设备
US20220150797A1 (en) Method for performing access control on user equipment, network system, and related device
KR20100053418A (ko) 무선통신 시스템에서 응급 통화를 위한 핸드오버의 수행방법
CN109429366B (zh) 一种pdu会话处理方法及设备
JP2017507605A (ja) ビデオ通話サービス品質の増進方法及び装置
US20240015593A1 (en) Traffic flow processing method, apparatus, and system
JP2022544761A (ja) 新しい無線（ｎｒ）の使用状況の表示をアプリケーション機能（ａｆ）に拡張するための方法、システム、およびコンピュータ読取可能媒体

Legal Events

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

Ref document number: 20806781

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

ENP Entry into the national phase

Ref document number: 2020806781

Country of ref document: EP

Effective date: 20211126