CN111132241B - Communication method, mobility management entity, user equipment and serving gateway - Google Patents

Communication method, mobility management entity, user equipment and serving gateway Download PDF

Info

Publication number
CN111132241B
CN111132241B CN201811278117.0A CN201811278117A CN111132241B CN 111132241 B CN111132241 B CN 111132241B CN 201811278117 A CN201811278117 A CN 201811278117A CN 111132241 B CN111132241 B CN 111132241B
Authority
CN
China
Prior art keywords
mme
bearer
channel
request
message
Prior art date
Legal status (The legal status 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 status listed.)
Active
Application number
CN201811278117.0A
Other languages
Chinese (zh)
Other versions
CN111132241A (en
Inventor
陈丽金
姜浩然
叶纶
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Huawei Technologies Co Ltd
Original Assignee
Huawei Technologies Co Ltd
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 Huawei Technologies Co Ltd filed Critical Huawei Technologies Co Ltd
Priority to CN201811278117.0A priority Critical patent/CN111132241B/en
Priority to PCT/CN2019/108887 priority patent/WO2020088177A1/en
Publication of CN111132241A publication Critical patent/CN111132241A/en
Application granted granted Critical
Publication of CN111132241B publication Critical patent/CN111132241B/en
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Images

Classifications

    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W36/00Hand-off or reselection arrangements
    • H04W36/24Reselection being triggered by specific parameters
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W36/00Hand-off or reselection arrangements
    • H04W36/0005Control or signalling for completing the hand-off
    • H04W36/0011Control or signalling for completing the hand-off for data sessions of end-to-end connection
    • H04W36/0016Hand-off preparation specially adapted for end-to-end data sessions
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W36/00Hand-off or reselection arrangements
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W76/00Connection management
    • H04W76/30Connection release
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W4/00Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/70Services for machine-to-machine communication [M2M] or machine type communication [MTC]

Landscapes

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

Abstract

A communication method, a mobility management entity, user equipment and a serving gateway are provided. The embodiment of the application discloses a communication method, which is used for reducing the packet loss probability of an uplink data packet sent by a UE through a CP channel when an MME triggers the UP bearer to be switched by the CP channel for data transmission. The method in the embodiment of the application comprises the following steps: when a mobility management entity MME triggers switching of user plane UP bearer by a control plane CP channel to perform data transmission, the MME acquires an indication message, wherein the indication message is used for indicating UE to stop sending uplink data packets through the CP channel; and the MME releases the CP channel according to the indication message.

Description

Communication method, mobility management entity, user equipment and serving gateway
Technical Field
The present application relates to the field of communications, and in particular, to a communication method, a mobility management entity, a user equipment, and a serving gateway.
Background
In the third Generation Partnership Project (3 GPP) protocol, two data transmission optimization schemes are proposed for the transmission characteristics of data in the narrowband internet of things (NB-IoT): control plane transmission optimization (control plane cellular internet of vertical evolved packet system optimization) and user plane transmission optimization (user plane cellular internet of vertical evolved packet system optimization). The CP transmission optimization, that is, a CP channel, refers to that a User Equipment (UE) transmits a packet to a Mobility Management Entity (MME) through a non-access-stratum (NAS) message, and the MME retransmits the packet to a Serving Gateway (SGW) through an S11_ U interface. In the process, because an air interface Data Radio Bearer (DRB) and an S1-U bearer do not need to be established, the total data transmission amount (including signaling) of an internet of things (IoT) terminal is reduced, so that the power consumption of the IoT terminal is reduced, and meanwhile, the signaling load on the network is also reduced.
In a CP transmission optimization scenario, when the UE actively triggers or the MME triggers the data transmission channel switching, the transmission of the data packet may be switched from CP channel transmission to UP bearer transmission, that is, a data radio bearer and an S1-U bearer need to be established. Furthermore, the UE may send the data packet to the base station through the data radio bearer, and the base station sends the data packet to the SGW through the S1-U bearer. In the current protocol, when the MME triggers the switching from the CP channel to the UP bearer for packet transmission, the MME first releases the S11_ U bearer with the SGW, and then establishes the UP bearer. Wherein the S11_ U bearer is part of the CP channel, and releasing the S11_ U bearer can be regarded as releasing the CP channel.
It should be noted that, when the MME triggers the data transmission channel switching, the UE does not sense the switching, and it takes a certain time to establish the data radio bearer, if the UE needs to send an uplink data packet in the process of establishing the data radio bearer, at this time, the uplink data packet is sent to the MME through the NAS message for transmission, at this time, the S11_ U bearer is released, and the uplink data packet may not be sent to the SGW, so that the uplink data packet is lost.
Disclosure of Invention
The embodiment of the application discloses a communication method, which is used for reducing the packet loss probability of an uplink data packet sent by a UE through a CP channel when an MME triggers the UP bearer to be switched by the CP channel for data transmission.
In view of this, a first aspect of an embodiment of the present application provides a communication method, which may include:
in an application scenario of a narrowband internet of things, when an MME meets a trigger condition for switching a data transmission channel, for example, when transmission data received by the MME is too large, the MME triggers switching of the data transmission channel from a CP channel to an UP bearer, and acquires an indication message. The indication message may be a message sent by the base station, or may be a message sent by the UE through the base station, where the indication message is used to indicate that the current UE has stopped sending the uplink data packet through the CP channel. And the MME releases the CP channel according to the indication message after determining that the UE does not send the uplink data packet through the CP channel any more according to the indication message.
In the embodiment of the present application, the MME is a CP channel released only after it is determined that the UE does not send an uplink data packet through the CP channel, that is, in the UP bearer switching process of the CP channel, when the UE needs to send an uplink data packet through the CP channel, the UE still can send the uplink data packet through the CP, so that the packet loss probability of the uplink data packet sent by the UE is reduced in the UP bearer switching process of the CP channel triggered by the MME.
Optionally, in some embodiments of the present application, the method may include: the MME sends an initial context establishment request to a base station, wherein the initial context establishment request is used for indicating the base station to establish the UP bearing; the MME obtaining indication message may include: the MME receives an initial context setup completion message sent by the base station. In the embodiment of the present application, it can be seen that, when the MME triggers switching of the UP bearer by the CP channel, the MME first sends an initial context setup request to the base station, and instructs the base station to setup the UP bearer. After receiving the initial context setup complete message sent by the base station, the MME determines that the UP bearer is established according to the initial context setup complete message, that is, the UE may send an uplink data packet through the UP bearer, and after the UE stops sending the uplink data packet through the CP channel, the CP channel is released. Compared with the prior art, the opportunity of the CP channel is modified, so that the UE can still send the uplink data packet through the CP channel before the UP bearer is not established in the switching process, and the packet loss probability of the uplink data packet sent by the UE in the switching process is reduced.
Optionally, in some embodiments of the present application, before the MME sends the initial context setup request to the base station, the method may further include: the MME sends a first request message to a Serving Gateway (SGW), wherein the first request message is used for indicating the SGW not to release the CP channel and stopping sending downlink data packets through the CP channel; the MME receives a first response message sent by the SGW. In the embodiment of the present application, the SGW is instructed to set the CP channel to the uplink capable and non-downlink state through the first request message, but the CP channel is not released. Therefore, the situation that when some downlink data packets sent by the SGW have packet returning requests, after the switching is completed, the uplink path (UP bearer) of the uplink data packet of the packet returning is different from the downlink path (CP channel) of the original downlink data packet, so that the UE is difficult to process is avoided.
Optionally, in some embodiments of the present application, the method may further include: the MME sends a second request message to the UE through the base station, wherein the second request message is used for indicating the UE to stop sending uplink data packets through the CP channel; the MME acquisition indication message may include: and the MME receives a second response message sent by the UE through the base station. In the embodiment of the application, the MME instructs the UE to stop sending the uplink data packet through the CP channel through the second request message, and releases the CP channel after receiving the second response message sent by the UE. Through the cooperation of the MME and the UE, the time for releasing the CP channel is adjusted, the packet loss probability of an uplink data packet sent by the UE is reduced, and the diversity of the scheme is increased.
Optionally, in some embodiments of the present application, after the MME receives the second response message sent by the UE through the base station, the method may further include: if the MME receives the uplink data packet sent by the UE through the CP channel, the MME sends a failure message to the UE through the base station, where the failure message is used to instruct the UE to send the uplink data packet through the UP bearer. In this embodiment of the application, for network reasons, it may be that after receiving the second response message, the MME still receives the uplink data packet sent by the UE through the CP, and at this time, the MME sends a failure message to the UE through the base station, where the failure message may be carried in an NAS message. The failure message prompts the UE to send the uplink data packet through the UP bearer, and the failure message can carry the original uplink data packet, so that the packet loss probability of the uplink data packet sent by the UE is further reduced.
Optionally, in some embodiments of the present application, the MME obtaining indication message may include: the MME receives the indication message sent by the UE through a base station. In this embodiment of the present application, in a handover process, an MME may receive an indication message sent by a UE, where the indication message indicates that the UE currently stops sending an uplink data packet through a CP channel, and the indication message may be an NAS message. Namely, in the embodiment of the present application, through cooperation of the MME and the UE, the packet loss probability of the uplink data packet sent by the UE is reduced, and the diversity of the scheme is increased.
Optionally, in some embodiments of the present application, the method may further include: the MME sends the initial context establishment request to a base station, wherein the initial context establishment request is used for indicating the base station to establish the UP bearing; the MME receives an initial context setup completion message sent by the base station. In the embodiment of the application, the description of the steps of the UP bearer establishment process is added, and the feasibility of the scheme is increased.
Optionally, in some embodiments of the present application, the MME releasing the CP channel according to the indication message may include: the MME generates a bearer modification request according to the indication message; the MME sending the modify bearer request to the SGW, the modify bearer request being used to instruct the SGW to release the CP channel and establish the UP bearer; the MME receives the modified bearer response sent by the SGW. In the embodiment of the present application, a method for releasing a CP channel is provided, which reduces two signaling of an access bearer release request and an access bearer release response, and saves signaling resources.
Optionally, in some embodiments of the present application, the MME releasing the CP channel according to the indication message may include: the MME generates a request for releasing the access bearer according to the indication message; the MME sending the release access bearer request to the SGW, the release access bearer request being used to instruct the SGW to release the CP channel; and the MME receives an access bearer release response sent by the SGW. In the embodiment of the application, another method for releasing the CP channel is provided, so that the diversity of the scheme is improved.
A second aspect of the embodiments of the present application provides a communication method, which may include:
in the UP bearer switching process of the CP channel, the SGW receives a bearer modification request sent by the MME through the S11_ U interface, where the bearer modification request carries a bearer address of the base station. After the SGW receives the bearer modification request, the CP channel is released according to the bearer modification request, that is, the local bearer of S11_ U is deleted, and an UP bearer corresponding to the bearer address of the base station is established. Thereafter, the SGW sends a modify bearer response to the MME instructing the MME to also delete the local S11_ U bearer.
In the embodiment of the application, the SGW releases the CP channel after receiving the request for modifying the bearer, and at this time, the UE stops sending the uplink data packet by using the CP channel and sends the uplink data packet through the UP bearer, so that the uplink data packet sent by the UE is not lost when the CP channel is released, and the packet loss probability of the uplink data packet sent by the UE is further reduced.
Optionally, in some embodiments of the present application, before the SGW receives the bearer modification request sent by the MME, the method may further include: the SGW receives a first request message sent by the MME; the SGW does not release the CP channel according to the first request message and stops sending downlink data packets through the CP channel; the SGW sends a first response message to the MME. In this embodiment of the application, the SGW sets the CP channel to be uplinkable but not downloadable according to the first request message, that is, the SGW may receive an uplink data packet sent by the UE through the CP channel, but does not send a downlink data packet to the UE through the CP channel, thereby avoiding a situation that if the SGW sends a downlink data packet with a packet return request, uplink and downlink channels of the SGW are different and processing pressure of the UE is increased (that is, when switching is not completed, a downlink path is the CP channel, and after switching is completed, a packet return request uplink path is changed into an UP bearer).
A third aspect of the embodiments of the present application provides a communication method, which may include:
when the UP bearer switching process is triggered by the MME in the CP channel, the UE acquires an indication message, where the indication message may be a message self-generated by the UE, or a message sent by the MME through the base station, or a message sent by the base station, and the indication message may be an NAS message. And after the UE acquires the indication message, stopping sending the uplink data packet through the CP channel according to the indication message, and caching the uplink data packet locally. When the UP bearer is established, that is, after the UE senses the establishment of the data radio bearer, the UE sends an uplink data packet through the UP bearer.
In the embodiment of the application, when the UP bearer is switched in the CP channel triggered by the MME, the UE acquires the indication message, and stops sending the uplink data packet through the CP channel according to the indication message. In the process of switching the UP bearer by the CP channel, after the UE receives the indication message, the UE does not send the uplink data packet through the CP channel any more, so that the situation that the uplink data packet is lost due to the release of the S11_ U is avoided, and the packet loss probability of the uplink data packet sent by the UE is reduced.
Optionally, in some embodiments of the present application, the acquiring, by the UE, the indication message may include: the UE receives a second request message sent by the MME through the base station; the method may further comprise: and the UE sends a second response message to the MME through the base station, wherein the second response message is used for indicating the MME to generate a request for releasing the access bearer. In the embodiment of the present application, the source of the indication message is described, that is, the packet loss probability of the uplink data packet sent by the UE is reduced through the cooperation between the MME and the UE, so that the diversity of the scheme is increased.
Optionally, in some embodiments of the present application, the method may further include: the UE receives a failure message sent by the MME through the base station; and the UE sends the uplink data packet through the UP bearer according to the failure message. In the embodiment of the present application, after the UE stops sending the uplink data packet through the CP channel, if a failure message sent by the MME through the base station is received, it indicates that the data packet corresponding to the failure message is not successfully sent. If the failure message carries the data packet, the UE stores the data packet locally, and sends the data packet through the UP bearer after the UP bearer is established. If the failure message does not carry the data packet, the UE determines the uplink data packet that is sent through the CP channel at the latest time, and caches the uplink data packet locally, and sends the uplink data packet through the UP bearer after waiting for the UP bearer to be established. And determining the data packet which is not successfully sent according to the failure message, and retransmitting the data packet through the UP bearer, so that the packet loss probability of the uplink data packet sent by the UE is reduced, and the stability of data sending is improved.
Optionally, in some embodiments of the present application, the acquiring, by the UE, the indication message may include: when the UE completes the establishment of the radio bearer with the base station, the UE generates the indication message; the method may further comprise: the UE sends the indication message to an MME through a base station, where the indication message is used to instruct the MME to release the CP channel. In the embodiment of the application, after the data radio bearer is established, the UE can send the uplink data packet through the UP bearer, and then stops sending the uplink data packet through the CP channel, so that the use efficiency of the channel is improved.
A fourth aspect of the present embodiment provides a mobility management entity, which may include:
a receiving and sending unit, configured to obtain an indication message when a CP channel is triggered to switch an UP bearer for data transmission, where the indication message is used to indicate the UE to stop sending an uplink data packet through the CP channel;
and the processing unit is used for releasing the CP channel according to the indication message.
Alternatively, in some embodiments of the present application,
the transceiver unit is further configured to send an initial context setup request to a base station, where the initial context setup request is used to instruct the base station to setup the UP bearer; and is specifically configured to receive an initial context setup complete message sent by the base station.
Alternatively, in some embodiments of the present application,
the sending and receiving unit is further configured to send a first request message to a serving gateway SGW, where the first request message is used to instruct the SGW not to release the CP channel and stop sending downlink data packets through the CP channel; and receiving a first response message sent by the SGW.
Alternatively, in some embodiments of the present application,
the transceiver unit is further configured to send a second request message to the UE through the base station, where the second request message is used to instruct the UE to stop sending the uplink data packet through the CP channel; and is specifically configured to receive a second response message sent by the UE through the base station.
Alternatively, in some embodiments of the present application,
the transceiver unit is further configured to send a failure message to the UE through the base station if the uplink data packet sent by the UE through the CP channel is received, where the failure message is used to instruct the UE to send the uplink data packet through the UP bearer.
Alternatively, in some embodiments of the present application,
the transceiver unit is specifically configured to receive the indication message sent by the UE through the base station.
Alternatively, in some embodiments of the present application,
the transceiver unit is further configured to send the initial context setup request to a base station, where the initial context setup request is used to instruct the base station to setup the UP bearer; and receiving an initial context establishment completion message sent by the base station.
Alternatively, in some embodiments of the present application,
the processing unit is specifically configured to generate a bearer modification request according to the indication message; sending the modify bearer request to the SGW, where the modify bearer request is used to instruct the SGW to release the CP channel and establish the UP bearer; and receiving the modified bearer response sent by the SGW.
Alternatively, in some embodiments of the present application,
the processing unit is specifically configured to generate a request for releasing an access bearer according to the indication message; sending the request for releasing the access bearer to the SGW, where the request for releasing the access bearer is used to instruct the SGW to release the CP channel; and receiving a response of releasing the access bearer sent by the SGW.
A fifth aspect of an embodiment of the present application provides a service gateway, which may include:
a receiving and sending unit, configured to receive a bearer modification request sent by an MME; sending a modify bearer response to the MME;
and the processing unit is used for releasing the CP channel according to the modification bearing request and establishing the UP bearing.
Alternatively, in some embodiments of the present application,
the receiving and sending unit is further configured to receive a first request message sent by the MME; sending a first response message to the MME;
the processing unit is further configured to not release the CP channel according to the first request message and stop sending the downlink data packet through the CP channel.
A sixth aspect of an embodiment of the present application provides a user equipment, which may include:
a receiving and sending unit, which is used for obtaining the indication message; when the UP bearing is established, sending an uplink data packet through the UP bearing;
and the processing unit is used for stopping sending the uplink data packet through the CP channel according to the indication message.
Alternatively, in some embodiments of the present application,
the receiving and sending unit is specifically configured to receive a second request message sent by the MME through the base station; and further configured to send, by the base station, a second response message to the MME, where the second response message is used to instruct the MME to generate a request to release the access bearer.
Alternatively, in some embodiments of the present application,
the receiving and sending unit is further configured to receive a failure message sent by the MME through the base station; and sending the uplink data packet through the UP bearer according to the failure message.
Alternatively, in some embodiments of the present application,
the transceiver unit is specifically configured to generate the indication message when the UE completes establishment of the radio bearer with the base station; and sending the indication message to an MME through the base station, where the indication message is used to instruct the MME to release the CP channel.
A seventh aspect of the present embodiment further provides a mobility management entity, which may include:
at least one processor, a memory, a transceiver and a bus, the processor, the memory, the transceiver coupled through the bus system, the mobility management entity communicating with a device other than the mobility management entity through the transceiver, the memory for storing program instructions, the at least one processor for executing the program instructions stored in the memory, cause the mobility management entity to perform the method as described in the first aspect and any one of the alternatives in the embodiments of the present application.
An eighth aspect of the present embodiment further provides a service gateway, which may include:
at least one processor, a memory, a transceiver and a bus, the processor, the memory, the transceiver coupled through the bus system, the serving gateway communicating with a device other than the mobility management entity through the transceiver, the memory for storing program instructions, the at least one processor for executing the program instructions stored in the memory, cause the serving gateway to perform the method as described in the second aspect and any one of the alternatives in the embodiments of the present application.
The ninth aspect of the embodiment of the present application further provides a user equipment, which may include:
at least one processor, a memory, a transceiver and a bus, the processor, the memory, the transceiver coupled through the bus system, the user equipment communicating with a device other than the mobility management entity through the transceiver, the memory for storing program instructions, the at least one processor for executing the program instructions stored in the memory, cause the user equipment to perform the method as described in the third aspect and any one of the alternatives in the embodiments of the present application.
A tenth aspect of embodiments of the present application further provides a computer storage medium, which includes instructions that, when executed on a computer, cause the computer to perform the method as described in the first aspect and any one of the alternatives.
An eleventh aspect of embodiments of the present application also provides a computer storage medium, which includes instructions that, when executed on a computer, cause the computer to perform the method as described in the foregoing second aspect and any optional manner.
A twelfth aspect of embodiments of the present application further provides a computer storage medium, which includes instructions that, when executed on a computer, cause the computer to perform the method as described in the foregoing third aspect and any optional manner.
A thirteenth aspect of embodiments of the present application also provides a computer program product containing instructions which, when run on a computer, cause the computer to perform the method as described in the first aspect and any of the alternatives.
A fourteenth aspect of embodiments of the present application also provides a computer program product containing instructions which, when run on a computer, cause the computer to perform the method as described in the second aspect and any of the alternatives.
A fifteenth aspect of embodiments of the present application also provides a computer program product containing instructions that, when executed on a computer, cause the computer to perform the method as described in the third and any of the alternatives.
According to the technical scheme, the embodiment of the application has the following advantages:
in the scheme, when the MME triggers that the UP bearer is switched by the CP channel to carry out data transmission, the MME acquires an indication message, wherein the indication message is used for indicating the UE to stop sending the uplink data packet through the CP channel, and after the MME acquires the indication message, the MME releases the CP channel according to the indication message. Because the MME determines that the UE stops sending the uplink data packet through the CP channel, and then releases the CP channel, that is, compared with the prior art, the timing for releasing the CP channel is adjusted, so that in the process of switching the UP bearer by the CP channel triggered by the MME, if the UE still needs to send the uplink data packet through the CP channel, that is, before the MME does not perceive that the UE stops sending the uplink data packet through the CP channel, the UE can still send the uplink data packet by using the CP channel, and the packet loss probability of the uplink data packet sent by the UE in the process of switching the UP bearer by the CP channel is reduced.
Drawings
FIG. 1 is a diagram of a system architecture as applied in an embodiment of the present application;
fig. 2 is a schematic diagram of a CP channel handover UP bearer triggered by an MME specified by a 3GPP protocol in an embodiment of the present application;
FIG. 3 is a schematic diagram of an embodiment of a communication method in an embodiment of the present application;
fig. 4 is a schematic diagram of another embodiment of the communication method in the embodiment of the present application;
fig. 5 is a schematic diagram of another embodiment of the communication method in the embodiment of the present application;
fig. 6 is a schematic diagram of another embodiment of the communication method in the embodiment of the present application;
fig. 7 is a schematic diagram of an embodiment of a mobility management entity in an embodiment of the present application;
FIG. 8 is a schematic diagram of an embodiment of a service gateway in an embodiment of the present application;
FIG. 9 is a schematic diagram of an embodiment of a user equipment in an embodiment of the present application;
fig. 10 is a schematic diagram of another embodiment of a mobility management entity in the embodiment of the present application;
FIG. 11 is a schematic diagram of another embodiment of a service gateway in the embodiment of the present application;
fig. 12 is a schematic diagram of another embodiment of a user equipment in the embodiment of the present application.
Detailed Description
The narrowband internet of things is an emerging technology in the field of internet of things, supports cellular data connection of low-power consumption equipment in a wide area network (wan), and is also called a Low Power Wide Area Network (LPWAN). The NB-IoT is built in a cellular network, and can be directly deployed in a Long Term Evolution (LTE) network. However, unlike the LTE network, the design goal of LTE is high rate and large traffic, and NB-IoT terminals are numerous and have high requirements for terminal energy saving, and data transmission is mainly intermittent transmission of small data (the network signaling overhead may be much larger than the size of data payload transmission itself). If the NB-IoT data interaction directly adopts the existing LTE signaling flow, it may cause too high energy consumption of the IoT terminal and also increase the signaling burden on the deployed network.
Based on the data transmission characteristics of the narrowband Internet of things, two data transmission optimization schemes are provided for the narrowband Internet of things in a 3GPP protocol: CP transmission optimization scheme and UP transmission optimization scheme. The CP-optimized transmission scheme is an efficient transmission method for transmitting small packets in NB-IoT, and the small packets may be transmitted on the control plane through the CP channel. Specifically, the UE and the MME are connected by an NAS layer, and the small data packet is carried on an NAS message to transmit data, and the MME transmits data with the SGW by an S11_ U interface. The CP channel is a bidirectional channel, i.e., uplink data and downlink data. According to the scheme, when data is transmitted, a data radio bearer and an S1-U connection do not need to be established, so that the signaling overhead of a control plane is reduced, and the power consumption of the terminal and the used frequency band are reduced.
The data transmission channel corresponding to the CP channel also has UP bearing, and the small data packet can be sent only through one of the CP channel and the UP bearing. The protocol provides that in some scenarios, the data transmission channel may also be switched from the CP channel to the UP bearer, and the switching process may be triggered by the MME or the UE. For example, when the uplink or downlink data packet received by the MME is too large, the CP channel can no longer meet the data transmission requirement, and the MME triggers switching of the current data transmission channel, that is, switching of the data transmission channel from the CP channel to the UP channel.
Fig. 1 is a system architecture diagram applied in the embodiment of the present application.
In the protocol, in a CP transmission optimization scenario, a flowchart of the UP bearer switching by the CP channel triggered by the MME is shown in fig. 2.
In fig. 2, after the MME triggers the transmission channel switching, step 201 is executed: and sending a request (release access bearers request) to the SGW, and indicating the SGW to release the S11_ U bearer. After the SGW releases S11_ U bearer, step 202 is executed: and sending a release access bearers response (release access bearers response) to the MME. After the MME determines S11_ U interface bearer release according to the access bearer release response, step 203 is executed: sending an initial context setup request (initial context setup request) to the base station, instructing the base station to setup UP bearer, that is, executing step 204: and establishing a radio bearer (setup) with the UE. After sensing the radio bearer establishment, the UE may execute step 205, that is, send uplink data (uplink data) through the UP bearer. After the UP bearer is established by the base station, step 206 is executed: an initial context setup complete message (initial context setup complete) is sent to the MME. After the MME receives the initial context setup complete message and determines that the UP bearer is setup, the MME executes step 207: a modify bearer request (modify bearer request) is sent to the SGW. The SGW establishes the S1-U bearer according to the setup modify bearer request and switches the data transmission channel to the UP bearer. Thereafter, the SGW performs step 208: and sending a modified bearer response (modified bearer response) to the MME, wherein the CP channel switching UP bearer is completed.
In the step shown in fig. 2, after the MME releases the S11_ U interface, i.e. releases the CP channel, the MME will perform the UP bearer establishment. Since the handover process is a handover process triggered by the MME, the UE does not perceive the handover when the MME triggers the handover, wherein the UE still selects to send uplink data through the CP channel in the data transmission channel handover process, i.e., the process from step 201 to step 204 shown in fig. 2. After the MME receives the uplink data packet sent by the UE, since the S11_ U bearer is released, the uplink data packet cannot be sent to the SGW any more, so that the uplink data packet is lost.
Based on this, an embodiment of the present application provides a communication method, which is used to reduce a packet loss probability of an uplink data packet sent by a UE in a process of switching an UP bearer by a CP channel triggered by an MME.
Referring to fig. 3 in detail, fig. 3 is a schematic diagram of an embodiment of a communication method in an embodiment of the present application, and the method may include:
301. and when the MME triggers the UP bearer to be switched by the CP channel for data transmission, the MME sends a first request message to the SGW.
In this embodiment, when the MME triggers handover, the MME sends a first request message to the SGW, where the first request message is a new addition message, and is used to notify the SGW to temporarily cache a downlink data packet but not release the S11_ U channel, and the SGW needs to control that an uplink data packet sent by the MME can be received from the S11_ U channel and a downlink data packet cannot be sent to the MME through the S11_ U channel, that is, the S11_ U channel may be uplink or non-downlink.
Optionally, in some possible implementations, the first request message may be an indication tag (indication flag) added in the request for releasing the access bearer, so that the first request message is carried in the request for releasing the access bearer. The SGW temporarily buffers the downstream packet according to the indication tag and sets the S11_ U channel to an uplinkable and non-downlinkable state.
302. And the SGW does not release the CP channel according to the first request message and stops sending the downlink data packet through the CP channel.
In this embodiment, after receiving the first request message, the SGW caches the downlink data packet according to the first request message, and sets the CP channel to an uplintable non-downlink state without releasing the CP channel. Specifically, the CP channel herein refers to an S11_ U bearer between the SGW and the MME.
304. The SGW sends a first response message to the MME.
In this embodiment, after the SGW is set, the SGW sends a first response message to the MME.
Optionally, in some possible implementations, the first response message may also be carried in the release access bearer response.
304. The MME sends an initial context setup request to the base station.
In this embodiment, after receiving the first response message sent by the SGW, the MME sends an initial context setup request to the base station through the S1-MME interface, where the initial context setup request is used to notify the base station to setup a data radio bearer with the UE and to locally perform configuration of an S1-U interface bearer.
305. The base station establishes a radio bearer with the UE.
In this embodiment, after receiving the initial context setup request, the base station establishes a radio bearer, that is, establishes an air interface connection, with the UE.
306. And when the radio bearer is established, the UE is switched to the UP bearer to send uplink data.
In this embodiment, after the UE detects that the data radio bearer is established, the UE stops sending the uplink data packet through the CP channel, switches the data transmission channel to the UP bearer, and then sends the uplink data through the UP bearer.
Optionally, in some possible implementation manners, after receiving the initial data radio bearer establishment request sent by the base station, the UE may select to stop sending the uplink data packet through the CP channel.
307. The base station sends an initial context setup complete message to the MME.
In this embodiment, when the base station determines that the radio bearer is established and the S1-U interface is configured locally, the base station sends an initial context establishment completion message to the MME.
308. The MME sends a modify bearer request to the SGW.
In this embodiment, when the MME receives the initial context completion request and determines that the UP bearer is established according to the initial context completion request, the MME sends a bearer modification request to the SGW, where the bearer modification request may carry a bearer address of the current base station of the UE.
309. And the SGW releases the CP channel according to the modified bearing request and establishes the UP bearing.
In this embodiment, after receiving the bearer modification request, the SGW releases the CP channel according to the bearer modification request, and establishes the UP bearer. Specifically, the SGW locally deletes the S11_ U bearer according to a modified bearer request, where the modified bearer request may carry an S11TF flag, the S11TF flag is a special message cell, and the SGW may switch the currently connected S11_ U bearer to the S1-U bearer according to the S11TF flag. Meanwhile, the SGW stores the bearer address carried in the message locally, and performs corresponding configuration of S1-U bearer locally according to the bearer address.
310. The SGW sends a modify bearer response to the MME.
In this embodiment, after the SGW is set, the SGW generates a modify bearer response, and sends the modify bearer request response message to the MME, where the modify bearer response is used to instruct the MME to delete the local S11_ U bearer, and release the resource corresponding to the S11_ U interface.
According to the technical scheme, the embodiment of the application has the following advantages:
when the MME triggers that the UP bearer is switched by the CP channel for data transmission, the MME sends a first request message to the SGW to indicate the SGW to set the CP channel to be in an uplink-capable and downlink-incapable state without releasing the CP channel. And after receiving the initial context establishment completion message sent by the base station, the MME determines that the UE does not send the uplink data packet through the CP channel any more according to the initial context establishment completion message. At this time, the MME releases the CP channel again, and completes other procedures for switching the UP bearer by the CP channel. Therefore, in the process of switching the UP bearer by the CP channel, when the UE needs to send the uplink data packet by using the CP channel, the UE can still send the uplink data packet through the CP channel, and the packet loss probability of the uplink data packet in the switching process is reduced. Meanwhile, the situation that the UE is difficult to process due to the fact that an uplink path (UP bearing) of an uplink data packet of a return packet is different from a downlink path (CP channel) of an original downlink data packet after switching is finished when some downlink data packets have the return packet requests is avoided.
Referring to fig. 4 in detail, fig. 4 is a schematic diagram of another embodiment of a communication method in an embodiment of the present application, and the method may include:
401. the MME sends an initial context setup request to the base station.
402. The base station establishes a radio bearer with the UE.
403. And when the radio bearer is established, the UE is switched to the UP bearer to send uplink data.
404. The base station sends an initial context setup complete message to the MME.
405. The MME sends a modify bearer request to the SGW.
406. And the SGW releases the CP channel according to the modified bearing request and establishes the UP bearing.
407. The SGW sends a modify bearer response to the MME.
It should be noted that steps 401 to 407 are similar to steps 304 to 310 shown in fig. 3, and are not described again here.
According to the technical scheme, the embodiment of the application has the following advantages:
when the MME triggers the UP bearer to be switched by the CP channel for data transmission, the MME firstly executes the process of establishing the UP bearer without releasing the CP channel. And after receiving the initial context establishment completion message sent by the base station, the MME determines that the UE does not send the uplink data packet through the CP channel any more according to the initial context establishment completion message. At this time, the MME releases the CP channel again, and completes other procedures for switching the UP bearer by the CP channel. And after the UP bearing is established, releasing the CP channel. Therefore, in the process of switching the UP bearer by the CP channel, when the UE needs to send the uplink data packet by using the CP channel, the UE can still send the uplink data packet through the CP channel, and the packet loss probability of the uplink data packet in the switching process is reduced.
Referring to fig. 5 in detail, fig. 5 is a schematic diagram of another embodiment of a communication method in an embodiment of the present application, and the method may include:
501. and when the MME triggers the UP bearer to be switched by the CP channel for data transmission, the MME sends a second request message to the UE through the base station.
In this embodiment, when the MME triggers the transmission channel switching, the MME sends, to the UE, a second request message through the base station, where the second request message may be an NAS message, and the second request message carries an identifier of the UE. The base station may identify the corresponding UE through the identifier, and forward the second request message to the UE.
Optionally, in a possible implementation manner, the second request message may also be carried in a downlink data packet sent by the MME.
502. And the UE stops sending the uplink data packet through the CP channel according to the second request message.
In this embodiment, after receiving the second request message, the UE may carry an end marker (end marker), and by identifying the identifier information, the UE stops sending the uplink data packet through the CP channel and caches the uplink data packet that needs to be uplink locally.
503. And the UE sends a second response message to the MME through the base station.
In this embodiment, after the UE completes the setting, the UE sends a second response message to the MME.
504. And the MME generates an access bearer releasing request according to the second response message.
In this embodiment, when the MME receives the second response message and determines that the UE does not send the uplink data packet through the CP channel according to the second response message, the MME generates a release access request message for instructing the SGW to release the S11_ U bearer.
Optionally, in some possible implementation manners, if there is a network jitter, there may be a case that the MME still receives an uplink data packet sent by the UE through the base station after receiving the second response message (the UE sends the uplink data packet before receiving the second request message, and the MME receives the uplink data packet after receiving the second response message because the uplink data packet is sent slowly). At this time, after receiving the uplink data packet, the MME may generate a corresponding failure message, and send the failure message to the UE through the base station. The failure message may carry the uplink data packet, and is used to notify the UE to send the uplink data packet through the UP bearer. The failure message may not carry the uplink data packet, and is used to notify the UE to send the uplink data packet, which is sent through the CP channel at the latest time from the current time, through the UP bearer.
505. The MME sends a request for releasing the access bearer to the SGW.
In this embodiment, the second request message is used to indicate that the UE no longer sends an uplink data packet through the CP channel, and after the MME receives the second response message, the MME generates an access bearer release request, where the access bearer release request is used to indicate the SGW to release the S11_ U bearer.
506. The SGW sends a release access bearer response to the MME.
In this embodiment, the SGW caches the downlink data packet according to the received request for releasing the access bearer, and locally deletes the S11_ U bearer. After releasing the S11_ U bearer, the SGW sends a release access bearer response to the MME, where the release access bearer response is used to indicate that the MME locally deletes the S11_ U bearer.
507. The MME sends an initial context setup request to the base station.
508. The base station establishes a radio bearer with the UE.
509. And when the radio bearer is established, the UE sends uplink data through the UP bearer.
510. The base station sends an initial context setup complete message to the MME.
It should be noted that steps 507 to 510 are similar to steps 304 to 307 shown in fig. 3, and are not described herein again.
511. The MME sends a modify bearer request to the SGW.
In this embodiment, when the SGW receives the bearer modification request, and after determining that the UP bearer is established according to the bearer modification request, the SGW generates a bearer modification request, where the bearer modification request may carry a bearer address of the current base station of the UE.
Optionally, in some possible implementations, the modified bearer request may also be used to notify the SGW to release the S11_ U bearer.
512. The SGW sends a modify bearer response to the MME.
In this embodiment, after receiving the bearer modification request, the SGW establishes an UP bearer according to the bearer modification request, and switches the CP channel to the UP bearer. Specifically, the modify bearer request may carry an S11TF flag, the S11TF flag is a special message cell, and the SGW may switch the currently connected S11_ U bearer to the S1-U bearer according to the S11TF flag. Meanwhile, the SGW stores the bearer address carried in the message locally, and performs corresponding configuration of S1-U bearer locally according to the bearer address.
Optionally, in some possible implementations, after receiving the bearer modification request, the SGW releases S11_ U bearer according to the bearer modification request.
According to the technical scheme, the embodiment of the application has the following advantages:
when the MME triggers the UP bearer to be switched by the CP channel for data transmission, the MME firstly sends a second request message to the UE through the base station to indicate the UE to stop sending the uplink data packet through the CP channel, and after the MME receives a second response message sent by the UE, the MME switches the data transmission channel and releases the CP channel. Therefore, the MME does not receive the uplink data packet sent by the UE through the CP channel any more in the switching process of the data transmission channel, and the packet loss probability of the uplink data packet in the switching process is reduced.
Referring to fig. 6 in detail, fig. 6 is a schematic diagram of another embodiment of a communication method in an embodiment of the present application, and the method may include:
601. when the MME triggers the UP load switched by the CP channel to carry out data transmission, the MME sends an initial context establishment request to the base station.
602. The base station establishes a radio bearer with the UE.
It should be noted that steps 601 to 602 are similar to steps 304 to 305 shown in fig. 3, and are not described again here.
603. And when the UE and the base station radio bearer are established, the UE generates an indication message.
In this embodiment, when the base station and the UE complete the establishment of the radio bearer, the UE stops sending the uplink data packet through the CP channel, and caches the uplink data packet to be uplinked locally. Thereafter, the UE generates an indication message.
Optionally, in some possible implementation manners, after receiving the initial radio bearer establishment request, the UE may stop sending the uplink data packet through the CP channel, and buffer the uplink data packet to be uplinked locally. Thereafter, the UE generates an indication message.
604. And the UE sends an indication message to the MME through the base station.
In this embodiment, after the UE is configured, the UE may send an indication message to the MME through the base station, where the indication message may be sent in an NAS message form through the NAS layer.
605. And the MME generates an access bearer releasing request according to the indication message.
In this embodiment, when the MME receives the indication message, and determines that the UE does not send the uplink data packet through the CP channel any more according to the indication message, the MME generates a release access request message, where the release access bearer request is used to instruct the SGW to release the CP bearer.
606. The MME sends a request for releasing the access bearer to the SGW.
607. The SGW sends a release access bearer response to the MME.
It should be noted that steps 606 to 607 are similar to steps 505 to 506 shown in fig. 5, and are not repeated here.
608. And when the radio bearer is established, the UE sends uplink data through the UP bearer.
609. The MME sends a modify bearer request to the SGW.
610. The SGW sends a modify bearer response to the MME.
611. The base station sends an initial context setup complete message to the MME.
It should be noted that steps 608 to 611 are similar to steps 509 to 512 shown in fig. 5, and are not described again here.
According to the technical scheme, the embodiment of the application has the following advantages:
when the MME triggers the UP bearing switched by the CP channel to carry out data transmission, the MME firstly indicates the base station to establish the UP bearing. In the process of establishing the radio bearer between the base station and the UE, after the MME receives an indication message of the UE, the CP channel is released, the indication message is used for indicating that the UE stops sending the uplink data packet through the CP channel at present, namely, the MME releases the CP channel after determining that the uplink data packet sent by the UE through the CP channel cannot be received any more, and therefore the packet loss probability of the uplink data packet in the switching process is reduced.
Referring to fig. 7 in detail, fig. 7 is a schematic diagram of an embodiment of a mobility management entity in an embodiment of the present application, where the schematic diagram may include:
a transceiving unit 701, configured to acquire an indication message when data transmission is triggered by switching UP bearer by a CP channel, where the indication message is used to indicate a UE to stop sending an uplink data packet through the CP channel;
a processing unit 702, configured to release the CP channel according to the indication message.
Alternatively, in some embodiments of the present application,
the transceiver unit 701 is further configured to send an initial context setup request to the base station, where the initial context setup request is used to instruct the base station to setup the UP bearer; and is specifically configured to receive an initial context setup complete message sent by the base station.
Alternatively, in some embodiments of the present application,
a transceiver 701, further configured to send a first request message to a serving gateway SGW, where the first request message is used to instruct the SGW not to release the CP channel and stop sending downlink data packets through the CP channel; and receiving a first response message sent by the SGW.
Alternatively, in some embodiments of the present application,
a transceiver unit 701, further configured to send a second request message to the UE through the base station, where the second request message is used to instruct the UE to stop sending the uplink data packet through the CP channel; and is specifically configured to receive a second response message sent by the UE through the base station.
Alternatively, in some embodiments of the present application,
the transceiving unit 701 is further configured to send a failure message to the UE through the base station if the uplink data packet sent by the UE through the CP channel is received, where the failure message is used to instruct the UE to send the uplink data packet through the UP bearer.
Alternatively, in some embodiments of the present application,
the transceiver 701 is specifically configured to receive the indication message sent by the UE through the base station.
Alternatively, in some embodiments of the present application,
a transceiver unit 701, further configured to send the initial context setup request to a base station, where the initial context setup request is used to instruct the base station to setup the UP bearer; and receiving an initial context establishment completion message sent by the base station.
Alternatively, in some embodiments of the present application,
a processing unit 702, specifically configured to generate a bearer modification request according to the indication message; sending the modify bearer request to the SGW, where the modify bearer request is used to instruct the SGW to release the CP channel and establish the UP bearer; and receiving the modified bearer response sent by the SGW.
Alternatively, in some embodiments of the present application,
a processing unit 702, specifically configured to generate a request for releasing access bearer according to the indication message; sending the request for releasing the access bearer to the SGW, where the request for releasing the access bearer is used to instruct the SGW to release the CP channel; and receiving a response of releasing the access bearer sent by the SGW.
Referring to fig. 8 in detail, fig. 8 is a schematic diagram of an embodiment of a service gateway in an embodiment of the present application, and the schematic diagram may include:
a transceiving unit 801, configured to receive a bearer modification request sent by an MME; sending a modify bearer response to the MME;
a processing unit 802, configured to release the CP channel according to the modified bearer request, and establish an UP bearer.
Alternatively, in some embodiments of the present application,
a transceiving unit 801, further configured to receive a first request message sent by the MME; sending a first response message to the MME;
the processing unit 802 is further configured to not release the CP channel according to the first request message and stop sending downlink data packets through the CP channel.
Referring to fig. 9 in detail, fig. 9 is a schematic diagram of an embodiment of a user equipment in an embodiment of the present application, and the schematic diagram may include:
a transceiving unit 901, configured to acquire an indication message; when the UP bearing is established, sending an uplink data packet through the UP bearing;
a processing unit 902, configured to stop sending the uplink data packet through the CP channel according to the indication message.
Alternatively, in some embodiments of the present application,
a transceiver 901, configured to specifically receive a second request message sent by the MME through the base station; and further configured to send, by the base station, a second response message to the MME, where the second response message is used to instruct the MME to generate a request to release the access bearer.
Alternatively, in some embodiments of the present application,
a transceiving unit 901, further configured to receive a failure message sent by the MME through the base station; and sending the uplink data packet through the UP bearer according to the failure message.
Alternatively, in some embodiments of the present application,
a transceiver 901, configured to generate the indication message when the UE completes establishing the radio bearer with the base station; and sending the indication message to an MME through the base station, where the indication message is used to instruct the MME to release the CP channel.
Referring to fig. 10 in detail, fig. 10 is a schematic diagram of another embodiment of a mobility management entity in an embodiment of the present application, where the schematic diagram may include:
at least one processor 1001, a memory 1002, a transceiver 1003 and a bus 1004, the processor 1001, the memory 1002 and the transceiver 1003 being coupled by the bus 1004 system, the mobility management entity communicating with devices other than the mobility management entity through the transceiver 1003, the memory 1002 being configured to store program instructions, the processor 1001 being configured to execute the program instructions stored in the memory, so that the mobility management entity performs the method as performed by the mobility management entity in the embodiments shown in fig. 3 to 6 and any alternative in the embodiments of the present application.
Referring to fig. 11 in detail, fig. 11 is a schematic view of another embodiment of a service gateway in an embodiment of the present application, which may include:
at least one processor 1101, a memory 1102, a transceiver 1103 and a bus 1104, wherein the processor 1101, the memory 1102 and the transceiver 1103 are coupled by the bus 1104 system, the serving gateway communicates with a device outside the mobility management entity through the transceiver 1103, the memory 1102 is used for storing program instructions, and the processor 1101 is used for executing the program instructions stored in the memory, so that the serving gateway performs the method performed by the serving gateway in the embodiments shown in fig. 3 to 6 and any optional manner in the embodiments of the present application.
Referring to fig. 12 in detail, fig. 12 is a schematic diagram of another embodiment of a user equipment in an embodiment of the present application, and the schematic diagram may include:
at least one processor 1201, a memory 1202, a transceiver 1203 and a bus 1204, the processor 1201, the memory 1202 and the transceiver 1203 are coupled by the bus 1204 system, the user equipment communicates with a device other than the mobility management entity through the transceiver 1203, the memory 1202 is used for storing program instructions, and the processor 1201 is used for executing the program instructions stored in the memory, so that the user equipment performs the method performed by the user equipment according to the embodiment shown in fig. 3 to fig. 6 and any optional manner in the embodiment of the present application.
An embodiment of the present application further provides a computer storage medium, which includes instructions, when executed on a computer, cause the computer to perform the method performed by the mobility management entity in the embodiments and any optional manner shown in fig. 3 to fig. 6.
The embodiment of the present application further provides a computer storage medium, which includes instructions, when executed on a computer, cause the computer to perform the method performed by the service gateway in the embodiments shown in fig. 3 to fig. 6 and any optional manner described above.
Embodiments of the present application further provide a computer storage medium, which includes instructions, when executed on a computer, cause the computer to perform the method performed by the user equipment according to the embodiments shown in fig. 3 to fig. 6 and any optional manner.
The present application also provides a computer program product containing instructions, which when run on a computer, causes the computer to execute the method performed by the mobility management entity in the embodiments and any optional manner shown in fig. 3 to fig. 6.
Embodiments of the present application further provide a computer program product containing instructions, which when run on a computer, cause the computer to perform the method as performed by the service gateway in the embodiments and any optional manner shown in fig. 3 to 6.
Embodiments of the present application further provide a computer program product containing instructions, which when executed on a computer, cause the computer to perform the method performed by the user equipment according to the embodiments shown in fig. 3 to 6 and any alternative manner.
In the above embodiments, the implementation may be wholly or partially realized by software, hardware, firmware, or any combination thereof. When implemented in software, may be implemented in whole or in part in the form of a computer program product. The computer program product includes one or more computer instructions. When loaded and executed on a computer, cause the processes or functions described in accordance with the embodiments of the application to occur, in whole or in part. The computer may be a general purpose computer, a special purpose computer, a network of computers, or other programmable device. The computer instructions may be stored in a computer readable storage medium or transmitted from one computer readable storage medium to another, for example, from one website site, computer, server, or data center to another website site, computer, server, or data center via wired (e.g., coaxial cable, fiber optic, Digital Subscriber Line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.). The computer-readable storage medium can be any available medium that can be accessed by a computer or a data storage device, such as a server, a data center, etc., that incorporates one or more of the available media. The usable medium may be a magnetic medium (e.g., floppy Disk, hard Disk, magnetic tape), an optical medium (e.g., DVD), or a semiconductor medium (e.g., Solid State Disk (SSD)), among others.
It is clear to those skilled in the art that, for convenience and brevity of description, the specific working processes of the above-described systems, apparatuses and units may refer to the corresponding processes in the foregoing method embodiments, and are not described herein again.
In the several embodiments provided in the present application, it should be understood that the disclosed system, apparatus and method may be implemented in other manners. For example, the above-described apparatus embodiments are merely illustrative, and for example, the division of the units is only one logical division, and other divisions may be realized in practice, for example, a plurality of units or components may be combined or integrated into another system, or some features may be omitted, or not executed. In addition, the shown or discussed mutual coupling or direct coupling or communication connection may be an indirect coupling or communication connection through some interfaces, devices or units, and may be in an electrical, mechanical or other form.
The units described as separate parts may or may not be physically separate, and parts displayed as units may or may not be physical units, may be located in one place, or may be distributed on a plurality of network units. Some or all of the units can be selected according to actual needs to achieve the purpose of the solution of the embodiment.
In addition, functional units in the embodiments of the present application may be integrated into one processing unit, or each unit may exist alone physically, or two or more units are integrated into one unit. The integrated unit can be realized in a form of hardware, and can also be realized in a form of a software functional unit.
The integrated unit, if implemented in the form of a software functional unit and sold or used as a stand-alone product, may be stored in a computer readable storage medium. Based on such understanding, the technical solution of the present application may be substantially implemented or contributed to by the prior art, or all or part of the technical solution may be embodied in a software product, which is stored in a storage medium and includes instructions for causing a computer device (which may be a personal computer, a server, or a network device) to execute all or part of the steps of the method according to the embodiments of the present application. And the aforementioned storage medium includes: a U-disk, a removable hard disk, a Read-Only Memory (ROM), a Random Access Memory (RAM), a magnetic disk or an optical disk, and other various media capable of storing program codes.
As described above, the above embodiments are only used for illustrating the technical solutions of the present application, and not for limiting the same; although the present application has been described in detail with reference to the foregoing embodiments, it should be understood by those of ordinary skill in the art that: the technical solutions described in the foregoing embodiments may still be modified, or some technical features may be equivalently replaced; and such modifications or substitutions do not depart from the spirit and scope of the corresponding technical solutions in the embodiments of the present application.

Claims (22)

1. A method of communication, comprising:
when a mobility management entity MME triggers that a control plane CP channel switches a user plane UP bearer to perform data transmission, the MME acquires an indication message, wherein the indication message is used for indicating user equipment UE to stop sending an uplink data packet through the CP channel, and the CP channel is not released in the process of switching to the UP bearer and is in an uplink-capable and downlink-incapable state;
and the MME releases the CP channel according to the indication message.
2. The method of claim 1, further comprising:
the MME sends an initial context establishment request to a base station, wherein the initial context establishment request is used for indicating the base station to establish the UP bearing;
the MME acquires the indication message, and comprises the following steps:
and the MME receives an initial context establishment completion message sent by the base station.
3. The method of claim 2, wherein before the MME sends an initial context setup request to a base station, the method further comprises:
the MME sends a first request message to a Serving Gateway (SGW), wherein the first request message is used for indicating the SGW not to release the CP channel and stopping sending downlink data packets through the CP channel;
the MME receives a first response message sent by the SGW.
4. The method of claim 1, further comprising:
the MME sends a second request message to the UE through a base station, wherein the second request message is used for indicating the UE to stop sending uplink data packets through the CP channel;
the MME acquires the indication message and comprises the following steps:
and the MME receives a second response message sent by the UE through the base station.
5. The method of claim 4, wherein after the MME receives a second response message sent by the UE through the base station, the method further comprises:
if the MME receives the uplink data packet sent by the UE through the CP channel, the MME sends a failure message to the UE through the base station, and the failure message is used for indicating the UE to send the uplink data packet through the UP bearer.
6. The method of claim 1, wherein the MME acquisition indication message comprises:
and the MME receives the indication message sent by the UE through a base station.
7. The method according to any one of claims 4-6, further comprising:
the MME sends an initial context establishment request to a base station, wherein the initial context establishment request is used for indicating the base station to establish the UP bearing;
and the MME receives an initial context establishment completion message sent by the base station.
8. The method according to any of claims 1-7, wherein the MME releases the CP channel according to the indication message, comprising:
the MME generates a bearer modification request according to the indication message;
the MME sends the bearer modification request to an SGW, wherein the bearer modification request is used for indicating the SGW to release the CP channel and establish the UP bearer;
and the MME receives a modified bearer response sent by the SGW.
9. The method according to any of claims 1-7, wherein the MME releasing the CP channel according to the indication message comprises:
the MME generates an access bearer releasing request according to the indication message;
the MME sends the access bearer releasing request to an SGW, wherein the access bearer releasing request is used for indicating the SGW to release the CP channel;
and the MME receives an access bearer release response sent by the SGW.
10. A method of communication, comprising:
a Service Gateway (SGW) receives a bearer modification request sent by a Mobility Management Entity (MME);
the SGW releases a Control Plane (CP) channel according to the modification bearing request and establishes a User Plane (UP) bearing, wherein the CP channel is not released in the process of switching to the UP bearing and is in an uplink-capable and downlink-incapable state;
the SGW sends a modify bearer response to the MME.
11. The method of claim 10, wherein before the SGW receives the modify bearer request sent by the MME, the method further comprises:
the SGW receives a first request message sent by the MME;
the SGW does not release the CP channel according to the first request message and stops sending downlink data packets through the CP channel;
the SGW sends a first response message to the MME.
12. A method of communication, comprising:
user Equipment (UE) acquires an indication message;
the UE stops sending uplink data packets through a control plane CP channel according to the indication message, wherein the CP channel is not released in the process of switching to UP bearing and is in an uplink-capable and downlink-incapable state;
and when a user plane UP bearer is established, the UE sends an uplink data packet through the UP bearer.
13. The method of claim 12, wherein the UE obtaining the indication message comprises:
the UE receives a second request message sent by a Mobility Management Entity (MME) through a base station;
the method further comprises the following steps:
and the UE sends a second response message to the MME through the base station, wherein the second response message is used for indicating the MME to generate a request for releasing the access bearer.
14. The method of claim 13, further comprising:
the UE receives a failure message sent by the MME through the base station;
and the UE sends the uplink data packet through the UP bearer according to the failure message.
15. The method of claim 12, wherein the UE obtaining the indication message comprises:
when the UE and the base station radio bearer are established, the UE generates the indication message;
the method further comprises the following steps:
and the UE sends the indication message to an MME through a base station, wherein the indication message is used for indicating the MME to release the CP channel.
16. A mobility management entity, comprising:
a receiving and sending unit, configured to acquire an indication message when a CP channel is triggered to switch an UP bearer for data transmission, where the indication message is used to indicate a UE to stop sending an uplink data packet through the CP channel, and the CP channel is not released in a process of switching to the UP bearer and is in an uplintable and non-downlinkable state;
and the processing unit is used for releasing the CP channel according to the indication message.
17. A serving gateway, comprising:
a receiving and sending unit, configured to receive a bearer modification request sent by an MME; sending a modify bearer response to the MME;
and the processing unit is used for releasing the CP channel according to the bearer modification request and establishing an UP bearer, wherein the CP channel is not released in the process of switching to the UP bearer and is in an uplink-capable and downlink-incapable state.
18. A user device, comprising:
a receiving and sending unit, which is used for obtaining the indication message; when the UP bearing is established, sending an uplink data packet through the UP bearing;
and the processing unit is used for stopping sending the uplink data packet through a CP channel according to the indication message, wherein the CP channel is not released in the process of switching to the UP bearer and is in an uplink available and downlink unavailable state.
19. A mobility management entity, comprising:
a processor, a memory, a bus, and a transceiver;
the memory, the transceiver, and the processor are connected by the bus;
the transceiver is configured to communicate with a device other than the mobility management entity;
the memory is used for storing operation instructions;
the processor is used for calling the operation instruction and executing the method according to any one of claims 1-9.
20. A serving gateway, comprising:
a processor, a memory, a bus, and a transceiver;
the memory, the transceiver, and the processor are connected by the bus;
the transceiver is configured to communicate with a device other than the mobility management entity;
the memory is used for storing operation instructions;
the processor is used for calling the operation instruction and executing the method according to any one of claims 10-11.
21. A user device, comprising:
a processor, a memory, a bus, and a transceiver;
the memory, the transceiver, and the processor are connected by the bus;
the transceiver is configured to communicate with a device other than a mobility management entity;
the memory is used for storing operation instructions;
the processor is used for calling the operation instruction and executing the method according to any one of claims 12-15.
22. A computer storage medium comprising instructions which, when run on a computer, cause the computer to perform the method of any of claims 1 to 9, or any of claims 10 to 11, or any of claims 12 to 15.
CN201811278117.0A 2018-10-30 2018-10-30 Communication method, mobility management entity, user equipment and serving gateway Active CN111132241B (en)

Priority Applications (2)

Application Number Priority Date Filing Date Title
CN201811278117.0A CN111132241B (en) 2018-10-30 2018-10-30 Communication method, mobility management entity, user equipment and serving gateway
PCT/CN2019/108887 WO2020088177A1 (en) 2018-10-30 2019-09-29 Communication method, mobility management entity, user equipment, and serving gateway

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN201811278117.0A CN111132241B (en) 2018-10-30 2018-10-30 Communication method, mobility management entity, user equipment and serving gateway

Publications (2)

Publication Number Publication Date
CN111132241A CN111132241A (en) 2020-05-08
CN111132241B true CN111132241B (en) 2021-06-08

Family

ID=70463452

Family Applications (1)

Application Number Title Priority Date Filing Date
CN201811278117.0A Active CN111132241B (en) 2018-10-30 2018-10-30 Communication method, mobility management entity, user equipment and serving gateway

Country Status (2)

Country Link
CN (1) CN111132241B (en)
WO (1) WO2020088177A1 (en)

Families Citing this family (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN116567657A (en) * 2022-01-28 2023-08-08 腾讯科技(深圳)有限公司 Data transmission method, data transmission device, computer readable medium and electronic equipment

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP2919520A1 (en) * 2012-11-08 2015-09-16 Ntt Docomo, Inc. Radio communication system and communication control method
CN107251601A (en) * 2015-04-17 2017-10-13 联发科技(新加坡)私人有限公司 The method multi-link for heterogeneous network and device
CN108235376A (en) * 2016-12-21 2018-06-29 电信科学技术研究院 A kind of user plane anchor point selection method and device
EP3346734A1 (en) * 2017-01-09 2018-07-11 Vodafone GmbH Providing information to a mobile device operated in a mobile radio network via a broadcast channel

Family Cites Families (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102833802B (en) * 2012-08-15 2015-09-23 电信科学技术研究院 A kind of data forwarding method and equipment
WO2018030826A1 (en) * 2016-08-12 2018-02-15 Samsung Electronics Co., Ltd. Method for controlling a user equipment

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP2919520A1 (en) * 2012-11-08 2015-09-16 Ntt Docomo, Inc. Radio communication system and communication control method
CN107251601A (en) * 2015-04-17 2017-10-13 联发科技(新加坡)私人有限公司 The method multi-link for heterogeneous network and device
CN108235376A (en) * 2016-12-21 2018-06-29 电信科学技术研究院 A kind of user plane anchor point selection method and device
EP3346734A1 (en) * 2017-01-09 2018-07-11 Vodafone GmbH Providing information to a mobile device operated in a mobile radio network via a broadcast channel

Non-Patent Citations (3)

* Cited by examiner, † Cited by third party
Title
Correction to S1-U bearer(s) establishment procedure during data transport using CP CIoT Optimisation;Huawei, HiSilicon;《3GPP TSG-SA WG2 Meeting #128bis S2-188172》;20180824;正文Reason for change部分,以及第5. 3. 4B. 4节 *
Data switching from CP to UP without sending a Release Access Bearers Request;Nokia, Alcatel-Lucent Shanghai Bell;《3GPP TSG CT4 Meeting #74 C4-164063》;20160712;全文 *
面向NB-IoT的核心网问题研究;马洪源、肖子玉等;《移动通信》;20171231;全文 *

Also Published As

Publication number Publication date
CN111132241A (en) 2020-05-08
WO2020088177A1 (en) 2020-05-07

Similar Documents

Publication Publication Date Title
US20220174759A1 (en) Method and apparatus for operating wireless communication system having separated mobility management and session management
CN108738086B (en) User plane reselection method and device
EP3562207B1 (en) Data transmission method, network device and terminal device
US10660006B2 (en) Bearer handover control device and control method
US10772146B2 (en) Multi-connectivity communication method, device, and terminal
CN110519807B (en) Communication method and device
CN110636535B (en) Data transmission method and device
US9801108B2 (en) Method for handover without default bearer and device
KR102390546B1 (en) User plane link establishment method, base station and mobility management device
CN109729549B (en) Communication method and device
JP2020524451A (en) Communication method and communication device
CN109151800B (en) Communication method and apparatus
CN110708720A (en) Switching method, distribution unit, terminal, central unit and computer storage medium
CN110447257B (en) Communication method, auxiliary network node and terminal
CN114026929B (en) F1 interface management method and device
CN114585034A (en) DAPS switching method, network equipment and user equipment
WO2020001256A1 (en) Data transmission method and device
WO2017121224A1 (en) Data transmission method, device and system
CN108391297B (en) Equipment switching method and equipment, bearer configuration method and equipment, and communication system
CN111132241B (en) Communication method, mobility management entity, user equipment and serving gateway
US10805968B2 (en) Bearer setup method, apparatus, and system
US20230067900A1 (en) Communication method and apparatus, and storage medium
CN110351785B (en) Communication method and device thereof
US20190082482A1 (en) Resource access method, apparatus, and system
WO2017166291A1 (en) Communication method, terminal, base station, and mobility management equipment

Legal Events

Date Code Title Description
PB01 Publication
PB01 Publication
SE01 Entry into force of request for substantive examination
SE01 Entry into force of request for substantive examination
GR01 Patent grant
GR01 Patent grant