WO2019100813A1 - 专用承载创建方法、移动性管理实体及分组数据网络网关 - Google Patents

专用承载创建方法、移动性管理实体及分组数据网络网关 Download PDF

Info

Publication number
WO2019100813A1
WO2019100813A1 PCT/CN2018/104821 CN2018104821W WO2019100813A1 WO 2019100813 A1 WO2019100813 A1 WO 2019100813A1 CN 2018104821 W CN2018104821 W CN 2018104821W WO 2019100813 A1 WO2019100813 A1 WO 2019100813A1
Authority
WO
WIPO (PCT)
Prior art keywords
dedicated bearer
terminal
request
create
bearer
Prior art date
Application number
PCT/CN2018/104821
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 JP2020528038A priority Critical patent/JP7039697B2/ja
Priority to KR1020207017630A priority patent/KR102344162B1/ko
Priority to US16/765,840 priority patent/US11076375B2/en
Priority to EP18880786.1A priority patent/EP3716680B1/en
Publication of WO2019100813A1 publication Critical patent/WO2019100813A1/zh

Links

Images

Classifications

    • 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
    • H04W60/04—Affiliation to network, e.g. registration; Terminating affiliation with the network, e.g. de-registration using triggered events
    • 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/0072—Transmission or use of information for re-establishing the radio link of resource information of target access point
    • 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/0083—Determination of parameters used for hand-off, e.g. generation or modification of neighbour cell lists
    • H04W36/00837—Determination of triggering parameters for hand-off
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/10—Connection setup
    • H04W76/19—Connection re-establishment
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/30—Connection release
    • H04W76/38—Connection release triggered by timers
    • 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/14—Backbone network devices
    • 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/16—Gateway arrangements
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/14—Reselecting a network or an air interface
    • H04W36/144—Reselecting a network or an air interface over a different radio air interface technology
    • H04W36/1446—Reselecting a network or an air interface over a different radio air interface technology wherein at least one of the networks is unlicensed

Definitions

  • the present disclosure relates to the field of communications technologies, and in particular, to a dedicated bearer creation method, a mobility management entity, and a packet data network gateway.
  • 3GPP proposes a packet data network gateway control plane function and session management function (PDN Gateway–Control Plane+Session Management Function, PGW-C+SMF) during 5G to 4G idle track area update (TAU) process.
  • PDN Gateway–Control Plane+Session Management Function PGW-C+SMF
  • PGW-C+SMF packet data network gateway control plane function and session management function
  • the establishment process of the dedicated bearer may be triggered after the TAU ends.
  • MME Mobility Management Entity
  • 3GPP proposes a method of using an Active flag to secure a NAS connection. This method requires the MME to always establish an air radio bearer (Data Radio Bearer (DRB) in the TAU process. Regardless of whether a dedicated bearer establishment process occurs in the future, the air interface resources may be wasted.
  • DRB Data Radio Bearer
  • Network architecture model supporting 5G network and LTE network (4G network) interoperability as shown in Figure 1, in the figure, MME and 5G system (5G System, 5GS) access control and mobility management functions (Access Control And Mobility
  • the N26 interface between the management function and the AMF is optional.
  • the network can support the handover between the 5G and the LTE network.
  • the context information of the terminal UE needs to be transmitted between the MME and the AMF. Includes the context of the mobility context and session connections.
  • the network may configure its registration mode to single registration mode, that is, single registration mode.
  • HSS+UDM indicates the home subscriber server + unified data management function
  • PCF+PCRF indicates the policy control function + policy and fee rule function
  • UPF+PGW-U indicates the user plane function + PDN gateway user plane function
  • E-UTRAN indicates Evolved UMTS terrestrial radio access network.
  • the Single registration mode UE moves from 5GS to EPS (Evolved Packet System) network. If the N26 interface is supported between 5GS and EPS, then:
  • an inter-RAT inter-RAT handover procedure is performed.
  • the UE For the idle state UE, if it is from 5GC to EPC, the UE performs the TAU procedure using the 5G-GUTI (5G globally unique temporary UE identifier, mapped from the 4G-GUTI), and the MME acquires the mobility management MM of the UE from the 5GC through the N26 interface. And session management SM context. If it is from the evolved packet core network EPC to 5GC, the UE uses 4G-GUTI (4G globally unique temporary UE identity, mapped from 5G-GUTI) to perform the registration process, access control and mobility management functions AMF and The session management function SMF obtains the MM and SM context of the UE from the EPC. The specific process is shown in Figure 2.
  • 5G-GUTI 5G globally unique temporary UE identifier, mapped from the 4G-GUTI
  • 4G-GUTI 4G globally unique temporary UE identity, mapped from 5G-GUTI
  • NG-RAN represents the next generation radio access network
  • PGW-U+UPF PDN gateway user plane function + user plane function
  • HSS+UDM HSS/UDM
  • the MME needs to keep the signaling connection not released after step 215 (otherwise, after receiving the TAU complete-TAU complete message, the MME will be in the period of time The S1 release-S1 release process is initiated to release the NAS signaling connection.
  • the MME receives the dedicated bearer setup request initiated by the PGW, the dedicated bearer setup procedure is initiated by using the existing NAS signaling connection.
  • the UE is required to send an active flag in the related art, which will cause the MME to request the base station eNB to create an air interface user plane bearer in the TAU process. If the subsequent PGW does not initiate the establishment process of the dedicated bearer, the eNB needs to wait for a period of time (timer control) to initiate the air interface bearer release process, which always leads to unnecessary air interface bearer setup and deletion processes.
  • the purpose of the disclosure is to provide a dedicated bearer creation method, a mobility management entity, and a packet data network gateway, which solves the problem of waste of air interface resources caused by a dedicated bearer creation scheme in the related art.
  • an embodiment of the present disclosure provides a dedicated bearer creation method, which is applied to a mobility management entity, including:
  • the terminal is determined to move from 5G to 4G according to the identifier information provided by the terminal;
  • a dedicated bearer request sent by the packet data network gateway is received, a dedicated bearer is created for the terminal by using the non-access stratum connection.
  • the step of maintaining the non-access stratum connection of the control plane includes:
  • the non-access stratum connection of the control plane is maintained within a preset time period (the non-access stratum connection is composed of an RRC connection of the air interface and an S1 connection between the base station and the MME);
  • the dedicated bearer request sent by the packet data network gateway is not received within the preset time period, the non-access stratum connection of the control plane is released.
  • the step of creating a dedicated bearer for the terminal by using the non-access stratum connection comprises:
  • the base station sends a request for creating a dedicated bearer to the terminal by using the non-access stratum connection at the same time as the base station creates the air interface user plane bearer for the terminal.
  • the request for creating a dedicated bearer is sent to the terminal by using the non-access stratum connection, before or at the same time: (by connecting with the S1 connection between the base stations), sending an initial terminal context setup request to the base station, triggering the base station to The terminal creates an air interface user plane bearer.
  • the identifier information provided by the terminal is a type of a global unique temporary terminal identifier.
  • the step of creating a dedicated bearer for the terminal by using the non-access stratum connection comprises:
  • the request for creating the dedicated bearer is sent to the terminal by using the maintained non-access stratum connection.
  • the step of creating a dedicated bearer for the terminal by using an existing non-access stratum connection comprises:
  • the embodiment of the present disclosure further provides a dedicated bearer creation method, which is applied to a packet data network gateway, and includes:
  • a dedicated bearer request is created and sent to the serving gateway, and the service gateway is triggered to create the session response by creating a session response.
  • a dedicated bearer request is brought to the mobility management entity.
  • the step of creating a dedicated bearer request in the modify bearer response message, and the sending to the serving gateway includes:
  • a dedicated bearer request is created and sent to the serving gateway.
  • Embodiments of the present disclosure also provide a mobility management entity, including: a transceiver, a memory, a processor, and a computer program stored on the memory and executable on the processor; the processor is configured to read The program in memory performs the following process:
  • the terminal is determined to move from 5G to 4G according to the identifier information provided by the terminal;
  • the transceiver creates a dedicated bearer request sent by the packet data network gateway, the non-access stratum connection is used to create a dedicated bearer for the terminal.
  • the processor is specifically configured to:
  • the non-access stratum connection of the control plane is maintained within a preset time period
  • the dedicated bearer request sent by the packet data network gateway is not received within the preset time period, the non-access stratum connection of the control plane is released.
  • the processor is specifically configured to:
  • the base station sends a request for creating a dedicated bearer to the terminal by using the non-access stratum connection at the same time as the base station creates the air interface user plane bearer for the terminal.
  • the processor is further configured to:
  • the identifier information provided by the terminal is a type of a global unique temporary terminal identifier.
  • the processor is specifically configured to:
  • the request for creating the dedicated bearer is sent to the terminal by using the maintained non-access stratum connection.
  • the processor is specifically configured to:
  • Embodiments of the present disclosure also provide a packet data network gateway, including: a transceiver, a memory, a processor, and a computer program stored on the memory and executable on the processor; the processor is configured to read The program in memory performs the following process:
  • a dedicated bearer request is created, and the transceiver is sent to the serving gateway to trigger the service gateway to create a session.
  • the response brings the create dedicated bearer request to the mobility management entity.
  • the processor is specifically configured to:
  • the transceiver After the transceiver receives the modified bearer request sent by the serving gateway, determining that the terminal moves from 5G to 4G, and needs to initiate a process of creating a dedicated bearer;
  • a dedicated bearer request is created and sent to the serving gateway through the transceiver.
  • the embodiment of the present disclosure further provides a computer readable storage medium having stored thereon a computer program, the program being executed by the processor to implement the step of the dedicated bearer creation method on the mobility management entity side.
  • the embodiment of the present disclosure further provides a computer readable storage medium having stored thereon a computer program, the program being executed by the processor to implement the step of the dedicated bearer creation method on the packet data network gateway side.
  • the embodiment of the present disclosure further provides a dedicated bearer creation device, which is applied to a mobility management entity, and includes:
  • a first processing module configured to determine, according to the identifier information provided by the terminal, that the terminal moves from 5G to 4G in the tracking area update process
  • a second processing module configured to create a dedicated bearer for the terminal by using the non-access stratum connection if receiving a dedicated bearer request sent by the packet data network gateway.
  • the first processing module includes:
  • a first processing submodule configured to maintain a non-access stratum connection of the control plane within a preset time period after the tracking area update is completed;
  • the second processing submodule is configured to release the non-access stratum connection of the control plane if the dedicated bearer request sent by the packet data network gateway is not received within the preset time period.
  • the second processing module includes:
  • a first sending submodule configured to: when receiving a request for creating a dedicated bearer sent by the packet data network gateway, connecting to the terminal by using the non-access stratum while the base station creates an air interface user plane bearer for the terminal Send a request to create a dedicated bearer.
  • the dedicated bearer creating device further includes:
  • the first sending module is configured to send a request for creating a dedicated bearer to the terminal by using the non-access stratum connection, and send an initial terminal context setup request to the base station before or at the same time, triggering the base station to create an air interface user plane bearer for the terminal .
  • the identifier information provided by the terminal is a type of a global unique temporary terminal identifier.
  • the second processing module includes:
  • a third processing submodule configured to: if the dedicated bearer request sent by the packet data network gateway is received after the tracking area update is completed, send a request for creating a dedicated bearer to the terminal by using the maintained non-access stratum connection.
  • the second processing module includes:
  • a fourth processing submodule configured to: if the creation session response is sent by the receiving service gateway, the creation session response carries a create dedicated bearer request sent by the packet data network gateway; Create a dedicated bearer request;
  • a fifth processing submodule configured to send, by using the non-access stratum connection, a request for creating a dedicated bearer to the terminal according to the creating a dedicated bearer request.
  • the embodiment of the present disclosure further provides a dedicated bearer creation device, which is applied to a packet data network gateway, and includes:
  • the third processing module is configured to: if it is determined that the terminal moves from 5G to 4G, and needs to initiate a process of creating a dedicated bearer; in the modify bearer response message, the piggybacking creates a dedicated bearer request, and sends the request to the serving gateway, triggering the serving gateway to pass
  • the create session response brings the create dedicated bearer request to the mobility management entity.
  • the third processing module includes:
  • a sixth processing submodule configured to: after receiving the modify bearer request sent by the serving gateway, determine that the terminal moves from 5G to 4G, and needs to initiate a process of creating a dedicated bearer;
  • the seventh processing submodule is configured to: in the modify bearer response message, create a dedicated bearer request and send the request to the serving gateway.
  • the dedicated bearer creation method determines that the terminal moves from 5G to 4G according to the identifier information provided by the terminal in the tracking area update process, and maintains the non-access stratum connection of the control plane after the tracking area update is completed. If the dedicated bearer request is sent by the packet data network gateway, the non-access stratum connection is used to create a dedicated bearer for the terminal; the bearer of the air interface can be established as needed according to actual requirements, thereby avoiding the MME in the TAU process. The requesting eNB creates an air interface user plane bearer, and the resulting air interface resource is wasted, which solves the problem of waste of air interface resources caused by the dedicated bearer creation scheme in the related art.
  • FIG. 1 is a schematic diagram of a network architecture in the related art
  • FIG. 2 is a schematic diagram of a process of moving a UE from a 5GS to an EPS network in the related art
  • FIG. 3 is a schematic flowchart of a method for creating a dedicated bearer according to an embodiment of the present disclosure
  • FIG. 4 is a second schematic flowchart of a method for creating a dedicated bearer according to an embodiment of the present disclosure
  • FIG. 5 is a schematic flowchart of a specific application method of a dedicated bearer creation method according to an embodiment of the present disclosure
  • FIG. 6 is a second schematic flowchart of a specific application method of a dedicated bearer creation method according to an embodiment of the present disclosure
  • FIG. 7 is a schematic structural diagram of a mobility management entity according to an embodiment of the present disclosure.
  • FIG. 8 is a schematic structural diagram of a packet data network gateway according to an embodiment of the present disclosure.
  • FIG. 9 is a schematic structural diagram of a dedicated bearer creation apparatus according to an embodiment of the present disclosure.
  • FIG. 10 is a second schematic structural diagram of a dedicated bearer creation apparatus according to an embodiment of the present disclosure.
  • the present disclosure is directed to the problem of the waste of the air interface resources caused by the dedicated bearer creation scheme in the related art, and provides a dedicated bearer creation method, which is applied to the mobility management entity, as shown in FIG. 3, and includes:
  • Step 31 If the tracking area is updated, the terminal is determined to move from 5G to 4G according to the identification information provided by the terminal;
  • Step 32 If a dedicated bearer request sent by the packet data network gateway is received, the dedicated bearer is created for the terminal by using the non-access stratum connection.
  • the dedicated bearer creation method determines that the terminal moves from 5G to 4G according to the identifier information provided by the terminal in the tracking area update process, and then keeps the control plane non-accessed after the tracking area update is completed.
  • Layer connection if a dedicated bearer request is sent by the packet data network gateway, the non-access stratum connection is used to create a dedicated bearer for the terminal; the bearer of the air interface can be established as needed according to actual requirements, thereby avoiding the MME being In the TAU process, the eNB is requested to create an air interface user plane bearer, and the resulting air interface resource is wasted, which solves the problem of waste of air interface resources caused by the dedicated bearer creation scheme in the related art.
  • the step of maintaining the non-access stratum connection of the control plane includes: maintaining the non-access stratum connection of the control plane within a preset time period after the tracking area update is completed (non-access)
  • the layer connection is composed of an RRC connection of the air interface and an S1 connection between the base station and the MME. If the dedicated bearer request sent by the packet data network gateway is not received within the preset time period, the non-access layer connection of the control plane is released. .
  • the preset time period is greater than a duration of the terminal triggering a local release of the connectionless layer connection.
  • the step of using the non-access stratum connection to create a dedicated bearer for the terminal includes: if the packet data network gateway receives the creation dedicated The bearer request is sent to the terminal by using the non-access stratum connection to send a request for creating a dedicated bearer (ACTIVATE DEDICATED EPS BEARER CONTEXT REQUEST message), while the base station creates an air interface user plane bearer for the terminal.
  • the request for creating a dedicated bearer is sent to the terminal by using the non-access stratum connection, before or at the same time: (by connecting with the S1 connection between the base stations), sending an initial terminal context establishment request to the base station, triggering the base station to The terminal creates an air interface user plane bearer.
  • the identifier information provided by the terminal is a type of the global unique temporary terminal identifier.
  • step 32 the embodiment of the present disclosure provides two specific implementation manners, as follows:
  • the step of creating a dedicated bearer for the terminal by using the non-access stratum connection comprises: receiving the packet after the tracking area update is completed.
  • the request for creating a dedicated bearer sent by the data network gateway sends a request for creating a dedicated bearer to the terminal by using the maintained non-access stratum connection.
  • the step of using the existing non-access stratum connection to create a dedicated bearer for the terminal includes: if the receiving service gateway sends the creation a session response, the create session response carrying a create dedicated bearer request sent by the packet data network gateway; parsing the create dedicated bearer request from the create session response; using the non-distribution according to the creating a dedicated bearer request
  • the access layer connection sends a request to the terminal to create a dedicated bearer.
  • the step of creating a session response sent by the receiving service gateway includes: receiving a modify bearer response that is sent by the serving gateway according to the PGW to create a dedicated bearer request, and creating a dedicated bearer request carried in the session response.
  • the dedicated bearer creation method further includes: releasing the existing non-access stratum connection if the create session response does not carry the create dedicated bearer request sent by the PGW.
  • the embodiment of the present disclosure further provides a dedicated bearer creation method, which is applied to a packet data network gateway, as shown in FIG. 4, and includes:
  • Step 41 If it is determined that the terminal moves from 5G to 4G, and needs to initiate a process of creating a dedicated bearer, in the modify bearer response message, a dedicated bearer request is created and sent to the serving gateway, and the service gateway is triggered to create a session response.
  • the create dedicated bearer request is brought to the mobility management entity.
  • the method for creating a dedicated bearer provided by the embodiment of the present disclosure, if it is determined that the terminal moves from 5G to 4G, and needs to initiate a process of creating a dedicated bearer, in the modify bearer response message, the dedicated bearer request is created and sent to the serving gateway.
  • the piggybacking creates a dedicated bearer request
  • the sending to the serving gateway includes: receiving the serving gateway to send After modifying the bearer request, it is determined that the terminal moves from 5G to 4G, and a process of creating a dedicated bearer needs to be initiated; in the modify bearer response message, a dedicated bearer request is created and sent to the serving gateway.
  • the dedicated bearer creation method provided by the embodiment of the present disclosure is further described below in conjunction with the two sides of the mobility management entity and the packet data network gateway.
  • the embodiment of the present disclosure provides a method for creating a dedicated bearer.
  • the following is a description of two specific examples.
  • the first one is based on the MME, and may be summarized as the MME determining that the UE moves from 5G to 4G. (According to the GUTI type), the NAS signaling connection is not released; after receiving the Create Private Bearer Request sent by the PGW, the MME sends an Initial UE Context Setup Request Initial UE context Setup message to the eNB, requesting the eNB to establish a user for the UE. Carrying.
  • the MME continues the dedicated bearer setup process. The details are as follows: According to the GUTI judgment, the NAS connection is maintained, as shown in FIG. 5:
  • Step 51 The UE initiates a TAU trigger (TAU trigger);
  • Step 52 The UE sends a TAU request (TAU request, carrying Old GUTI-old GUTI) to the MME;
  • Step 51-52 After the UE moves from the 5G network to the 4G network, the UE initiates a TAU process, and the message carries the 4G GUTI mapped from the 5G GUTI, that is, the Old GUTI (Mapped GUTI), and the UE can be in the GUTI type (GUTI). Indicates that the GUTI is mapped from the 5G GUTI. as follows:
  • the IEI is an Information element identifier and the spare is a reserved value.
  • Step 53 Context Request/Response (Context Request/Response) is exchanged between the MME and the AMF;
  • Step 54 The MME sends a Create Session Request to the SGW.
  • Step 55 The SGW sends a Modify Bearer Request to the PGW-C+SMF.
  • Step 56 The PGW-C+SMF returns a Modify Bearer Response to the SGW.
  • Step 57 The SGW returns a Create Session Response to the MME.
  • Step 53-57 The MME first acquires the context context of the UE from the AMF, and then updates the packet data network connection PDN connection of the UE to the PGW-C+SMF according to the UE context.
  • Step 58 The MME sends a TAU Accept (Tracking Area Update Accept) to the UE;
  • Step 59 The UE returns TAU Complete to the MME (tracking area update completion);
  • Step 510 The MME performs a Keep NAS signaling connection (maintaining a non-access stratum signaling connection);
  • Steps 58-510 After the MME sends the TAU Accept message to the UE or after receiving the TAU Complete message, since the MME recognizes that the UE is moving from 5G to 4G, the UE remains in the connected state, that is, the UE is maintained for a sufficient time.
  • the NAS connection (and the connection with the S1 interface of the eNB) is not released, and the duration should be greater than the duration of the UE locally releasing the NAS signaling connection (in the related art, the UE triggers the local release NAS signaling connection for 10 seconds).
  • Step 511 The PGW-C+SMF sends a Create bearer Request to the SGW.
  • Step 512 The SGW forwards a Create bearer Request to the MME.
  • Steps 511-512 After the PGW-C receives the Modify Bearer Request message sent by the serving gateway SGW in step 55, the establishment process of the dedicated bearer may be triggered. Therefore, after the Modify Bearer Response message is sent, the Create Bearer Request is sent to the SGW. To initiate the establishment of a dedicated bearer.
  • Step 513 The MME sends an Initial UE context Setup Request to the eNB.
  • the MME After the MME receives the Create Bearer Request, it will use the existing S1 connection to send an Initial UE context Setup message to the eNB to trigger the eNB to create the UE context and the air interface DRB.
  • the MME may simultaneously request the eNB to establish a dedicated bearer requested by the PGW in the Initial UE context Setup Request message, or may send a bearer setup request Bearer Setup Request message to the eNB to create a dedicated bearer after the Initial UE context Setup procedure is completed.
  • the MME sends a request for creating a dedicated bearer to the terminal by using the non-access stratum connection, and the terminal gives a response.
  • Step 514 Implementing a Radio Bearer Establishment between the UE and the eNB;
  • Step 515 The eNB returns an Initial UE context Setup Complete to the MME.
  • Step 516 The MME sends a Create bearer Response to the SGW.
  • Step 517 The SGW forwards a Create bearer Response to the PGW-C+SMF.
  • Steps 514-517 The eNB creates an air interface bearer according to the request of the MME, and then returns a response to the MME.
  • the MME returns a response to the PGW-C+SMF. Thereafter the UE enters the connected state.
  • the second type is based on the PGW side.
  • the modify bearer response Modify Bearer Response carries the Create Bearer Request, so that the MME can At the same time, the Modify Bearer Response message and the Create Bearer Request message are received, and the TAU process and the Initial UE context Setup process may be synchronously performed.
  • the TAU Accept message may be sent to the UE first, the TAU process is completed, and then the Initial UE context Setup process is initiated;
  • Figure 6 shows:
  • Step 61 The UE initiates a TAU trigger (TAU trigger);
  • Step 62 The UE sends a TAU request (TAU request, carrying Old GUTI-old GUTI) to the MME;
  • Steps 61-62 The MME receives the TAU request of the UE. For details, refer to the description of steps 51-52.
  • Step 63 Context Request/Response (Context Request/Response) is exchanged between the MME and the AMF;
  • Step 64 The MME sends a Create Session Request to the SGW.
  • Step 65 The SGW sends a Modify Bearer Request to the PGW-C+SMF.
  • Step 66 The PGW-C+SMF returns a Modify Bearer Response to the SGW, and carries a Create Bearer Request.
  • Step 67 The SGW returns a Create Session Response to the MME, and carries a Create Bearer Request.
  • Step 63-67 The MME first acquires the context of the UE from the AMF, and then updates the PDN connection of the UE to the PGW-C+SMF according to the UE context.
  • Step 66-67 After the PGW-C receives the Modify Bearer Request message sent by the SGW, the establishment process of the dedicated bearer may be triggered. Therefore, the PGW-C+SMF may use the relevant when the Modify Bearer Response message is sent.
  • the message piggybacking mechanism of the GTPv2 protocol in the technology carries the Create Bearer Request message for creating a dedicated bearer, so that the MME can simultaneously receive the Modify Bearer Response message and the Create Bearer Request message.
  • Step 68 The MME sends a TAU Accept to the UE (Tracking Area Update Accept);
  • Step 69 The UE returns TAU Complete to the MME (tracking area update completion);
  • Steps 68-69 After the MME receives the Create Bearer Request, the TAU process and the Initial UE context Setup process may be synchronously performed, or the TAU Accept message may be sent to the UE to complete the TAU process, and then the Initial UE context Setup process is initiated.
  • Step 610 The MME sends an Initial UE context Setup Request to the eNB.
  • the MME sends an Initial UE context Setup message to the eNB by using the existing S1 connection to trigger the eNB to create a UE context and an air interface DRB.
  • the MME may simultaneously request the eNB to establish a dedicated bearer requested by the PGW in the Initial UE context Setup Request message, or may send a Bearer Setup Request message to the eNB to create a dedicated bearer after the Initial UE context Setup procedure is completed.
  • the MME sends a request for creating a dedicated bearer to the terminal by using the non-access stratum connection, and the terminal gives a response.
  • Step 611 Implementing a Radio Bearer Establishment between the UE and the eNB;
  • Step 612 The eNB returns an Initial UE context Setup Complete to the MME.
  • Step 613 The MME sends a Create bearer Response to the SGW.
  • Step 614 The SGW forwards a Create bearer Response to the PGW-C+SMF.
  • Steps 611-614 The eNB creates an air interface bearer according to the request of the MME, and then returns a response to the MME.
  • the MME returns a response to the PGW-C+SMF. Thereafter the UE enters the connected state.
  • the MME After receiving the request to create a dedicated bearer from the PGW-C+SMF, the MME completes the dedicated bearer setup process by using the existing NAS connection.
  • the MME determines that the UE moves from 5G to 4G according to the type or display indication of the GUTI;
  • the MME maintains the established NAS connection, including issuing a TAU Accept message or receiving a TAU complete message, and maintaining the established NAS connection.
  • a request to create a dedicated bearer is received from the PGW-C+SMF, specifically after receiving the Create Session Response message.
  • the MME After the MME maintains the established NAS connection for a period of time, if the request for creating a dedicated bearer is not received, the MME is released.
  • the second example is mainly:
  • the MME receives a request for creating a dedicated bearer from the PGW-C+SMF, specifically, parsing out from the Create Session Response Create Session Response message.
  • the Create Bearer Request is encapsulated in the Modify Bearer Response message by the PGW-C+SMF, and then forwarded to the MME by the SGW through the Create Session Response message.
  • the solution provided by the embodiment of the present disclosure can obviously avoid unnecessary establishment and deletion of air interface bearers in the TAU process of 5G to 4G.
  • Embodiments of the present disclosure also provide a mobility management entity, including: a transceiver, a memory, a processor, and a computer program stored on the memory and executable on the processor; the processor is configured to read The program in memory performs the following process:
  • the terminal is determined to move from 5G to 4G according to the identifier information provided by the terminal;
  • the transceiver creates a dedicated bearer request sent by the packet data network gateway, the non-access stratum connection is used to create a dedicated bearer for the terminal.
  • the mobility management entity determines that the terminal moves from 5G to 4G according to the identifier information provided by the terminal in the tracking area update process, and then keeps the control plane non-accessed after the tracking area update is completed.
  • Layer connection if a dedicated bearer request is sent by the packet data network gateway, the non-access stratum connection is used to create a dedicated bearer for the terminal; the bearer of the air interface can be established as needed according to actual requirements, thereby avoiding the MME being In the TAU process, the eNB is requested to create an air interface user plane bearer, and the resulting air interface resource is wasted, which solves the problem of waste of air interface resources caused by the dedicated bearer creation scheme in the related art.
  • the mobility management entity of the embodiment of the present disclosure includes:
  • a processor 71 a processor 71; and a memory 73 connected to the processor 71 via a bus interface 72, the memory 73 for storing programs and data used by the processor 71 when performing operations, when the processor 71 calls and When executing the programs and data stored in the memory 73, the following process is performed:
  • the terminal is determined to move from 5G to 4G according to the identifier information provided by the terminal;
  • the transceiver establishes a dedicated bearer request sent by the packet data network gateway, the non-access stratum connection is used to create a dedicated bearer for the terminal.
  • the transceiver 74 is coupled to the bus interface 72 for receiving and transmitting data under the control of the processor 71.
  • the bus architecture may include any number of interconnected buses and bridges, specifically linked by one or more processors represented by processor 71 and various circuits of memory represented by memory 73.
  • the bus architecture can also link various other circuits such as peripherals, voltage regulators, and power management circuits, which are well known in the art and, therefore, will not be further described herein.
  • the bus interface provides an interface.
  • Transceiver 74 can be a plurality of components, including a transmitter and a transceiver, providing means for communicating with various other devices on a transmission medium.
  • the processor 71 is responsible for managing the bus architecture and general processing, and the memory 73 can store data used by the processor 71 in performing operations.
  • the processor is specifically configured to: after the update of the tracking area is completed, maintain a non-access stratum connection of the control plane within a preset time period; if the packet data network gateway does not receive the creation within a preset time period A dedicated bearer request releases the non-access stratum connection of the control plane.
  • the processor is specifically configured to: when receiving a dedicated bearer request sent by the packet data network gateway, using the non-access stratum after the base station creates an air interface user plane bearer for the terminal The connection sends a request to the terminal to create a dedicated bearer.
  • the processor is further configured to: use the non-access stratum connection to send a request for creating a dedicated bearer to the terminal, before or at the same time, send an initial terminal context setup request to the base station, triggering the base station to create the terminal Air interface user plane bearer.
  • the identifier information provided by the terminal is a type of the global unique temporary terminal identifier.
  • the embodiment of the present disclosure provides two specific implementation manners. as follows:
  • the processor is specifically configured to: if the dedicated bearer request sent by the packet data network gateway is received after the tracking area update is completed, send the dedicated bearer to the terminal by using the maintained non-access stratum connection. request.
  • the processor is specifically configured to: if the creation session response sent by the receiving service gateway is received by the transceiver, the creation session response carries a dedicated bearer request sent by the packet data network gateway; The creating a dedicated bearer request is parsed in the creating a session response; and the request for creating a dedicated bearer is sent to the terminal by using the non-access stratum connection according to the creating a dedicated bearer request.
  • the implementation embodiments of the dedicated bearer creation method on the mobility management entity side are applicable to the embodiment of the mobility management entity, and the same technical effects can be achieved.
  • Embodiments of the present disclosure also provide a packet data network gateway, including: a transceiver, a memory, a processor, and a computer program stored on the memory and executable on the processor; the processor is configured to read The program in memory performs the following process:
  • a dedicated bearer request is created, and the transceiver is sent to the serving gateway to trigger the service gateway to create a session.
  • the response brings the create dedicated bearer request to the mobility management entity.
  • the packet data network gateway provided by the embodiment of the present disclosure, if it is determined that the terminal moves from 5G to 4G, and needs to initiate a process of creating a dedicated bearer, in the modify bearer response message, a dedicated bearer request is created and sent to the serving gateway.
  • the packet data network gateway of the embodiment of the present disclosure includes:
  • a processor 81 a processor 81; and a memory 83 connected to the processor 81 via a bus interface 82, the memory 83 for storing programs and data used by the processor 81 when performing operations, when the processor 81 calls and When executing the programs and data stored in the memory 83, the following process is performed:
  • a dedicated bearer request is created, sent to the serving gateway by the transceiver 84, and the service gateway is triggered to be created.
  • the session response brings the create dedicated bearer request to the mobility management entity.
  • the transceiver 84 is coupled to the bus interface 82 for receiving and transmitting data under the control of the processor 81.
  • the bus architecture may include any number of interconnected buses and bridges, specifically linked by one or more processors represented by processor 81 and various circuits of memory represented by memory 83.
  • the bus architecture can also link various other circuits such as peripherals, voltage regulators, and power management circuits, which are well known in the art and, therefore, will not be further described herein.
  • the bus interface provides an interface.
  • Transceiver 84 can be a plurality of components, including a transmitter and a transceiver, providing means for communicating with various other devices on a transmission medium.
  • the processor 81 is responsible for managing the bus architecture and general processing, and the memory 83 can store data used by the processor 81 when performing operations.
  • the processor is specifically configured to: after the transceiver receives the modified bearer request sent by the serving gateway, determine that the terminal moves from 5G to 4G, and needs to initiate a process of creating a dedicated bearer; The device creates a dedicated bearer request and sends it to the serving gateway through the transceiver.
  • the implementation examples of the method for creating a dedicated bearer on the packet data network gateway side are applicable to the embodiment of the packet data network gateway, and the same technical effects can be achieved.
  • the embodiment of the present disclosure further provides a computer readable storage medium having stored thereon a computer program, the program being executed by the processor to implement the step of the dedicated bearer creation method on the mobility management entity side.
  • the implementation embodiments of the dedicated bearer creation method on the mobility management entity side are applicable to the embodiment of the computer readable storage medium, and the same technical effects can be achieved.
  • the embodiment of the present disclosure further provides a computer readable storage medium having stored thereon a computer program, the program being executed by the processor to implement the step of the dedicated bearer creation method on the packet data network gateway side.
  • the implementation examples of the dedicated bearer creation method on the packet data network gateway side are applicable to the embodiment of the computer readable storage medium, and the same technical effects can be achieved.
  • the embodiment of the present disclosure further provides a dedicated bearer creation device, which is applied to a mobility management entity, as shown in FIG. 9, and includes:
  • the first processing module 91 is configured to: when the tracking area is updated, determine, according to the identifier information provided by the terminal, that the terminal moves from 5G to 4G;
  • the second processing module 92 is configured to create a dedicated bearer for the terminal by using the non-access stratum connection if receiving a create dedicated bearer request sent by the packet data network gateway.
  • the dedicated bearer creating apparatus determines that the terminal moves from 5G to 4G according to the identifier information provided by the terminal in the tracking area update process, and then keeps the control plane non-accessed after the tracking area update is completed.
  • Layer connection if a dedicated bearer request is sent by the packet data network gateway, the non-access stratum connection is used to create a dedicated bearer for the terminal; the bearer of the air interface can be established as needed according to actual requirements, thereby avoiding the MME being In the TAU process, the eNB is requested to create an air interface user plane bearer, and the resulting air interface resource is wasted, which solves the problem of waste of air interface resources caused by the dedicated bearer creation scheme in the related art.
  • the first processing module includes: a first processing submodule, configured to maintain a non-access stratum connection of the control plane within a preset time period after the tracking area update is completed; and a second processing submodule, configured to: If the dedicated bearer request sent by the packet data network gateway is not received within the preset time period, the non-access stratum connection of the control plane is released.
  • the second processing module includes: a first sending submodule, configured to: when receiving a dedicated bearer request sent by the packet data network gateway, when the base station creates an air interface user plane bearer for the terminal, or after completion And transmitting, by using the non-access stratum connection, a request for creating a dedicated bearer to the terminal.
  • a first sending submodule configured to: when receiving a dedicated bearer request sent by the packet data network gateway, when the base station creates an air interface user plane bearer for the terminal, or after completion And transmitting, by using the non-access stratum connection, a request for creating a dedicated bearer to the terminal.
  • the dedicated bearer creating apparatus further includes: a first sending module, configured to send, by using the non-access stratum connection, a request for creating a dedicated bearer to the terminal, before or at the same time, sending an initial terminal context establishment request to the base station, triggering The base station creates an air interface user plane bearer for the terminal.
  • a first sending module configured to send, by using the non-access stratum connection, a request for creating a dedicated bearer to the terminal, before or at the same time, sending an initial terminal context establishment request to the base station, triggering The base station creates an air interface user plane bearer for the terminal.
  • the identifier information provided by the terminal is a type of the global unique temporary terminal identifier.
  • the embodiment of the present disclosure provides two specific implementation manners, as follows:
  • the second processing module includes: a third processing submodule, configured to: if the dedicated bearer request sent by the packet data network gateway is received after the tracking area update is completed, use the retained non-access stratum The connection sends a request to the terminal to create a dedicated bearer.
  • the second processing module includes: a fourth processing submodule, configured to: when the receiving session response is sent by the receiving service gateway, the creating session response carries a dedicated bearer request sent by the packet data network gateway; The request to create a dedicated bearer is parsed from the create session response.
  • the fifth processing submodule is configured to send a request for creating a dedicated bearer to the terminal by using the non-access stratum connection according to the creating a dedicated bearer request.
  • the implementation examples of the dedicated bearer creation method on the mobility management entity side are applicable to the embodiment of the dedicated bearer creation device, and the same technical effects can be achieved.
  • the embodiment of the present disclosure further provides a dedicated bearer creation device, which is applied to a packet data network gateway, as shown in FIG. 10, and includes:
  • the third processing module 101 is configured to: if it is determined that the terminal moves from 5G to 4G, and needs to initiate a process of creating a dedicated bearer; in the modify bearer response message, the piggybacking creates a dedicated bearer request, and sends the request to the serving gateway to trigger the serving gateway.
  • the create dedicated bearer request is brought to the mobility management entity by creating a session response.
  • the dedicated bearer creating apparatus provided by the embodiment of the present disclosure, by determining that the terminal moves from 5G to 4G, and needs to initiate a process of creating a dedicated bearer, in the modify bearer response message, the dedicated bearer request is created and sent to the serving gateway.
  • the third processing module includes: a sixth processing submodule, configured to: after receiving the modify bearer request sent by the serving gateway, determine that the terminal moves from 5G to 4G, and needs to initiate a process of creating a dedicated bearer;
  • the sub-module is configured to create a dedicated bearer request and send it to the serving gateway in the modify bearer response message.
  • the implementation examples of the dedicated bearer creation method on the packet data network gateway side are applicable to the embodiment of the dedicated bearer creation device, and the same technical effects can be achieved.
  • modules/sub-modules may be implemented in software for execution by various types of processors.
  • an identified executable code module can comprise one or more physical or logical blocks of computer instructions, which can be constructed, for example, as an object, procedure, or function. Nonetheless, the executable code of the identified modules need not be physically located together, but may include different instructions stored in different bits that, when logically combined, constitute a module and implement the provisions of the module. purpose.
  • the executable code module can be a single instruction or a plurality of instructions, and can even be distributed over a plurality of different code segments, distributed among different programs, and distributed across multiple memory devices.
  • operational data may be identified within the modules and may be implemented in any suitable form and organized within any suitable type of data structure. The operational data may be collected as a single data set, or may be distributed at different locations (including on different storage devices), and may at least partially exist as an electronic signal on a system or network.
  • the module can be implemented by software, considering the level of the hardware process in the related art, the module can be implemented in software, and the technician can construct the corresponding hardware circuit to realize the corresponding function without considering the cost.
  • the hardware circuit includes conventional Very Large Scale Integration (VLSI) circuits or gate arrays and semiconductors in related art such as logic chips, transistors, or other discrete components.
  • VLSI Very Large Scale Integration
  • the modules can also be implemented with programmable hardware devices such as field programmable gate arrays, programmable array logic, programmable logic devices, and the like.

Landscapes

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

Abstract

本公开提供了一种专用承载创建方法、移动性管理实体及分组数据网络网关，其中，专用承载创建方法包括：若在跟踪区更新过程中，根据终端提供的标识信息确定终端从5G移动到4G；则在跟踪区更新完成后，保持控制平面的非接入层连接；若接收到分组数据网络网关发送的创建专用承载请求，则利用所述非接入层连接为所述终端创建专用承载。本方案能够根据实际需求按需的建立空口的承载，避免了MME在TAU过程中请求eNB创建空口用户面承载，而导致的空口资源浪费，很好的解决了现有技术中专用承载创建方案造成空口资源浪费的问题。

Description

专用承载创建方法、移动性管理实体及分组数据网络网关
相关申请的交叉引用
本申请主张在2017年11月21日在中国提交的中国专利申请号No.201711168078.4的优先权，其全部内容通过引用包含于此。
技术领域
本公开涉及通信技术领域，特别是指一种专用承载创建方法、移动性管理实体及分组数据网络网关。
背景技术
3GPP提出在5G向4G的空闲态跟踪区更新(Tracking Area Update，TAU)过程中，分组数据网络网关控制平面功能及会话管理功能(PDN Gateway–Control Plane+Session Management Function，PGW-C+SMF)可能会在TAU结束后触发专用承载的建立过程，然而在相关技术中的TAU过程中，移动性管理实体(Mobility Management Entity，MME)发送TAU accept消息后就会释放非接入层NAS信令连接，因此，3GPP提出了使用Active flag(激活标识)来保证NAS连接的方法。这种方法要求MME在TAU过程中，总是建立空口的数据无线承载(Data Radio Bearer，DRB)，无论后续是否出现专用承载建立过程，可能会造成空口的资源浪费。
支持5G网络和LTE网络(4G网络)互操作的网络架构模型，如图1所示，在图中，MME和5G系统(5G System，5GS)接入控制与移动性管理功能(Access Control And Mobility Management Function，AMF)之间的N26接口是可选支持的，当网络支持N26接口时，网络可以支持5G和LTE网络之间的切换，此时MME和AMF之间需要传递终端UE的上下文信息，包括移动性上下文和会话连接的上下文。终端接入这种支持N26接口的网络时，网络可能将其注册模式配置为单注册模式，即single registration mode。图中HSS+UDM表示归属签约用户服务器+统一数据管理功能；PCF+PCRF表示策略控制功能+策略与费规则功能；UPF+PGW-U表示用户平面功能+PDN网关 用户面功能；E-UTRAN表示演进的UMTS陆地无线接入网。
Single registration模式UE从5GS移动到EPS(演进的分组系统)网络，若5GS和EPS之间支持N26接口，则：
对于连接态UE，如TS 23.502所述，执行接入技术间inter-RAT切换过程。
对于空闲态UE，如果是从5GC到EPC，UE使用5G-GUTI(5G全球唯一临时UE标识，从4G-GUTI映射而来)执行TAU过程，MME通过N26接口从5GC获取UE的移动性管理MM和会话管理SM上下文。如果是从演进的分组核心网EPC到5GC，UE使用4G-GUTI(4G全球唯一临时UE标识，从5G-GUTI映射而来)执行registration(注册)过程，接入控制与移动性管理功能AMF和会话管理功能SMF从EPC获取UE的MM和SM上下文。具体流程如图2所示。图中NG-RAN表示下一代无线接入网，PGW-U+UPF(P-GW-U/UPF)表示PDN网关用户面功能+用户平面功能，HSS+UDM(HSS/UDM)表示归属签约用户服务器+统一数据管理功能。
如果UE在TAU request(TAU请求)消息中携带了Active flag，那么在步骤215之后，MME需要保持信令连接不释放(否则，MME在收到TAU complete-TAU完成消息后，会在一段时间内发起S1release-S1释放过程释放NAS信令连接)，这样在步骤216时，如果MME收到PGW发起的专用承载建立请求，则利用已有的NAS信令连接发起专用承载建立过程。
由上可知，相关技术中要求UE发送active flag，这将导致MME在TAU过程中请求基站eNB创建空口用户面承载。如果后续PGW并没有发起专用承载的建立过程，那么eNB又需要等待一段时间后(定时器控制)发起空口承载释放过程，这样总会导致不必要的空口承载建立和删除过程。
发明内容
本公开的目的在于提供一种专用承载创建方法、移动性管理实体及分组数据网络网关，解决相关技术中专用承载创建方案造成空口资源浪费的问题。
为了解决上述技术问题，本公开实施例提供一种专用承载创建方法，应用于移动性管理实体，包括：
若在跟踪区更新过程中，根据终端提供的标识信息确定终端从5G移动到4G；
则在跟踪区更新完成后，保持控制平面的非接入层连接；
若接收到分组数据网络网关发送的创建专用承载请求，则利用所述非接入层连接为所述终端创建专用承载。
可选地，所述在跟踪区更新完成后，保持控制平面的非接入层连接的步骤包括：
在跟踪区更新完成后，在预设时间段内保持控制平面的非接入层连接(非接入层连接由空口的RRC连接和基站与MME之间的S1连接组成)；
若在预设时间段内未接收到分组数据网络网关发送的创建专用承载请求，则释放控制平面的非接入层连接。
可选地，所述若接收到分组数据网络网关发送的创建专用承载请求，则利用所述非接入层连接为所述终端创建专用承载的步骤包括：
若接收到分组数据网络网关发送的创建专用承载请求，则在基站为所述终端创建空口用户面承载的同时或者完成之后，利用所述非接入层连接向终端发送创建专用承载的请求。
可选地，利用所述非接入层连接向终端发送创建专用承载的请求，之前或者同时还包括：(通过与基站间的S1连接)向基站发送初始终端上下文建立请求，触发所述基站为所述终端创建空口用户面承载。
可选地，所述终端提供的标识信息为全球唯一临时终端标识的类型。
可选地，所述若接收到分组数据网络网关发送的创建专用承载请求，则利用所述非接入层连接为所述终端创建专用承载的步骤包括：
若在跟踪区更新完成后接收到分组数据网络网关发送的创建专用承载请求，则利用保持的所述非接入层连接向终端发送创建专用承载的请求。
可选地，所述若接收到分组数据网络网关发送的创建专用承载请求，则利用已有的非接入层连接为所述终端创建专用承载的步骤包括：
若接收到接收服务网关发送的创建会话响应，所述创建会话响应中携带分组数据网络网关发送的创建专用承载请求；则从所述创建会话响应中解析出所述创建专用承载请求；
根据所述创建专用承载请求，利用所述非接入层连接向终端发送创建专用承载的请求。
本公开实施例还提供了一种专用承载创建方法，应用于分组数据网络网关，包括：
若确定终端从5G移动到4G，且需要发起创建专用承载的过程；则在修改承载响应消息中，捎带创建专用承载请求，发送给服务网关，触发所述服务网关通过创建会话响应将所述创建专用承载请求捎带给移动性管理实体。
可选地，所述若确定终端从5G移动到4G，且需要发起创建专用承载的过程；则在修改承载响应消息中，捎带创建专用承载请求，发送给服务网关的步骤包括：
接收到服务网关发送的修改承载请求后，确定终端从5G移动到4G，且需要发起创建专用承载的过程；
在修改承载响应消息中，捎带创建专用承载请求，发送给服务网关。
本公开实施例还提供了一种移动性管理实体，包括：收发机、存储器、处理器及存储在所述存储器上并可在所述处理器上运行的计算机程序；所述处理器用于读取存储器中的程序，执行下列过程：
若在跟踪区更新过程中，根据终端提供的标识信息确定终端从5G移动到4G；
则在跟踪区更新完成后，保持控制平面的非接入层连接；
若通过所述收发机接收到分组数据网络网关发送的创建专用承载请求，则利用所述非接入层连接为所述终端创建专用承载。
可选地，所述处理器具体用于：
在跟踪区更新完成后，在预设时间段内保持控制平面的非接入层连接；
若在预设时间段内未接收到分组数据网络网关发送的创建专用承载请求，则释放控制平面的非接入层连接。
可选地，所述处理器具体用于：
若接收到分组数据网络网关发送的创建专用承载请求，则在基站为所述终端创建空口用户面承载的同时或者完成之后，利用所述非接入层连接向终端发送创建专用承载的请求。
可选地，所述处理器还用于：
利用所述非接入层连接向终端发送创建专用承载的请求，之前或者同时，向基站发送初始终端上下文建立请求，触发所述基站为所述终端创建空口用户面承载。
可选地，所述终端提供的标识信息为全球唯一临时终端标识的类型。
可选地，所述处理器具体用于：
若在跟踪区更新完成后接收到分组数据网络网关发送的创建专用承载请求，则利用保持的所述非接入层连接向终端发送创建专用承载的请求。
可选地，所述处理器具体用于：
若通过所述收发机接收到接收服务网关发送的创建会话响应，所述创建会话响应中携带分组数据网络网关发送的创建专用承载请求；则从所述创建会话响应中解析出所述创建专用承载请求；
根据所述创建专用承载请求，利用所述非接入层连接向终端发送创建专用承载的请求。
本公开实施例还提供了一种分组数据网络网关，包括：收发机、存储器、处理器及存储在所述存储器上并可在所述处理器上运行的计算机程序；所述处理器用于读取存储器中的程序，执行下列过程：
若确定终端从5G移动到4G，且需要发起创建专用承载的过程；则在修改承载响应消息中，捎带创建专用承载请求，通过所述收发机发送给服务网关，触发所述服务网关通过创建会话响应将所述创建专用承载请求捎带给移动性管理实体。
可选地，所述处理器具体用于：
通过所述收发机接收到服务网关发送的修改承载请求后，确定终端从5G移动到4G，且需要发起创建专用承载的过程；
在修改承载响应消息中，捎带创建专用承载请求，通过所述收发机发送给服务网关。
本公开实施例还提供了一种计算机可读存储介质，其上存储有计算机程序，该程序被处理器执行时实现上述移动性管理实体侧的专用承载创建方法的步骤。
本公开实施例还提供了一种计算机可读存储介质，其上存储有计算机程序，该程序被处理器执行时实现上述分组数据网络网关侧的专用承载创建方法的步骤。
本公开实施例还提供了一种专用承载创建装置，应用于移动性管理实体，包括：
第一处理模块，用于若在跟踪区更新过程中，根据终端提供的标识信息确定终端从5G移动到4G；
则在跟踪区更新完成后，保持控制平面的非接入层连接；
第二处理模块，用于若接收到分组数据网络网关发送的创建专用承载请求，则利用所述非接入层连接为所述终端创建专用承载。
可选地，所述在第一处理模块包括：
第一处理子模，用于在跟踪区更新完成后，在预设时间段内保持控制平面的非接入层连接；
第二处理子模块，用于若在预设时间段内未接收到分组数据网络网关发送的创建专用承载请求，则释放控制平面的非接入层连接。
可选地，所述第二处理模块包括：
第一发送子模块，用于若接收到分组数据网络网关发送的创建专用承载请求，则在基站为所述终端创建空口用户面承载的同时或者完成之后，利用所述非接入层连接向终端发送创建专用承载的请求。
可选地，所述专用承载创建装置还包括：
第一发送模块，用于利用所述非接入层连接向终端发送创建专用承载的请求，之前或者同时，向基站发送初始终端上下文建立请求，触发所述基站为所述终端创建空口用户面承载。
可选地，所述终端提供的标识信息为全球唯一临时终端标识的类型。
可选地，所述第二处理模块包括：
第三处理子模块，用于若在跟踪区更新完成后接收到分组数据网络网关发送的创建专用承载请求，则利用保持的所述非接入层连接向终端发送创建专用承载的请求。
可选地，所述第二处理模块包括：
第四处理子模块，用于若接收到接收服务网关发送的创建会话响应，所述创建会话响应中携带分组数据网络网关发送的创建专用承载请求；则从所述创建会话响应中解析出所述创建专用承载请求；
第五处理子模块，用于根据所述创建专用承载请求，利用所述非接入层连接向终端发送创建专用承载的请求。
本公开实施例还提供了一种专用承载创建装置，应用于分组数据网络网关，包括：
第三处理模块，用于若确定终端从5G移动到4G，且需要发起创建专用承载的过程；则在修改承载响应消息中，捎带创建专用承载请求，发送给服务网关，触发所述服务网关通过创建会话响应将所述创建专用承载请求捎带给移动性管理实体。
可选地，所述第三处理模块包括：
第六处理子模块，用于接收到服务网关发送的修改承载请求后，确定终端从5G移动到4G，且需要发起创建专用承载的过程；
第七处理子模块，用于在修改承载响应消息中，捎带创建专用承载请求，发送给服务网关。
本公开的上述技术方案的有益效果如下：
上述方案中，所述专用承载创建方法通过若在跟踪区更新过程中，根据终端提供的标识信息确定终端从5G移动到4G；则在跟踪区更新完成后，保持控制平面的非接入层连接；若接收到分组数据网络网关发送的创建专用承载请求，则利用所述非接入层连接为所述终端创建专用承载；能够根据实际需求按需的建立空口的承载，避免了MME在TAU过程中请求eNB创建空口用户面承载，而导致的空口资源浪费，很好的解决了相关技术中专用承载创建方案造成空口资源浪费的问题。
附图说明
为了更清楚地说明本公开实施例的技术方案，下面将对本公开实施例中所需要使用的附图作简单地介绍，显而易见地，下面描述中的附图仅仅是本公开的一些实施例，对于本领域普通技术人员来讲，在不付出创造性劳动性 的前提下，还可以根据这些附图获得其他的附图。
图1为相关技术中的网络架构示意图；
图2为相关技术中的UE从5GS移动到EPS网络流程示意图；
图3为本公开实施例的专用承载创建方法流程示意图之一；
图4为本公开实施例的专用承载创建方法流程示意图之二；
图5为本公开实施例的专用承载创建方法具体应用方法流程示意图之一；
图6为本公开实施例的专用承载创建方法具体应用方法流程示意图之二；
图7为本公开实施例的移动性管理实体结构示意图；
图8为本公开实施例的分组数据网络网关结构示意图；
图9为本公开实施例的专用承载创建装置结构示意图之一；
图10为本公开实施例的专用承载创建装置结构示意图之二。
具体实施方式
下面将结合本公开实施例中的附图，对本公开实施例中的技术方案进行清楚、完整地描述，显然，所描述的实施例是本公开一部分实施例，而不是全部的实施例。基于本公开中的实施例，本领域普通技术人员在没有作出创造性劳动前提下所获得的所有其他实施例，都属于本公开保护的范围。
本公开针对相关的技术中专用承载创建方案造成空口资源浪费的问题，提供一种专用承载创建方法，应用于移动性管理实体，如图3所示，包括：
步骤31：若在跟踪区更新过程中，根据终端提供的标识信息确定终端从5G移动到4G；
则在跟踪区更新完成后，保持控制平面的非接入层连接；
步骤32：若接收到分组数据网络网关发送的创建专用承载请求，则利用所述非接入层连接为所述终端创建专用承载。
本公开实施例提供的所述专用承载创建方法通过若在跟踪区更新过程中，根据终端提供的标识信息确定终端从5G移动到4G；则在跟踪区更新完成后，保持控制平面的非接入层连接；若接收到分组数据网络网关发送的创建专用承载请求，则利用所述非接入层连接为所述终端创建专用承载；能够根据实际需求按需的建立空口的承载，避免了MME在TAU过程中请求eNB创建空 口用户面承载，而导致的空口资源浪费，很好的解决了相关技术中专用承载创建方案造成空口资源浪费的问题。
其中，所述在跟踪区更新完成后，保持控制平面的非接入层连接的步骤包括：在跟踪区更新完成后，在预设时间段内保持控制平面的非接入层连接(非接入层连接由空口的RRC连接和基站与MME之间的S1连接组成)；若在预设时间段内未接收到分组数据网络网关发送的创建专用承载请求，则释放控制平面的非接入层连接。
优选的，所述预设时间段大于所述终端触发本地释放非连接层连接的时长。
具体的，所述若接收到分组数据网络网关发送的创建专用承载请求，则利用所述非接入层连接为所述终端创建专用承载的步骤包括：若接收到分组数据网络网关发送的创建专用承载请求，则在基站为所述终端创建空口用户面承载的同时或者完成之后，利用所述非接入层连接向终端发送创建专用承载的请求(ACTIVATE DEDICATED EPS BEARER CONTEXT REQUEST message)。
进一步的，利用所述非接入层连接向终端发送创建专用承载的请求，之前或者同时还包括：(通过与基站间的S1连接)向基站发送初始终端上下文建立请求，触发所述基站为所述终端创建空口用户面承载。
优选的，所述终端提供的标识信息为全球唯一临时终端标识的类型。
对于步骤32，本公开实施例提供两种具体实现方式，如下：
第一种，所述若接收到分组数据网络网关发送的创建专用承载请求，则利用所述非接入层连接为所述终端创建专用承载的步骤包括：若在跟踪区更新完成后接收到分组数据网络网关发送的创建专用承载请求，则利用保持的所述非接入层连接向终端发送创建专用承载的请求。
第二种，所述若接收到分组数据网络网关发送的创建专用承载请求，则利用已有的非接入层连接为所述终端创建专用承载的步骤包括：若接收到接收服务网关发送的创建会话响应，所述创建会话响应中携带分组数据网络网关发送的创建专用承载请求；则从所述创建会话响应中解析出所述创建专用承载请求；根据所述创建专用承载请求，利用所述非接入层连接向终端发送 创建专用承载的请求。
其中，所述接收服务网关发送的创建会话响应的步骤包括：接收服务网关根据PGW发送的携带创建专用承载请求的修改承载响应，在创建会话响应中携带的创建专用承载请求。
进一步的，所述专用承载创建方法还包括：若所述创建会话响应中未携带PGW发送的创建专用承载请求，则释放已有的非接入层连接。
本公开实施例还提供了一种专用承载创建方法，应用于分组数据网络网关，如图4所示，包括：
步骤41：若确定终端从5G移动到4G，且需要发起创建专用承载的过程；则在修改承载响应消息中，捎带创建专用承载请求，发送给服务网关，触发所述服务网关通过创建会话响应将所述创建专用承载请求捎带给移动性管理实体。
本公开实施例提供的所述专用承载创建方法通过若确定终端从5G移动到4G，且需要发起创建专用承载的过程；则在修改承载响应消息中，捎带创建专用承载请求，发送给服务网关，触发所述服务网关通过创建会话响应将所述创建专用承载请求捎带给移动性管理实体；进而使得移动性管理实体能够在跟踪区更新完成之前，接收到分组数据网络网关发送的创建专用承载请求，从而利用已有的非接入层连接为所述终端创建专用承载；实现了根据实际需求按需的建立空口的承载的目的，避免了MME在TAU过程中请求eNB创建空口用户面承载，而导致的空口资源浪费，很好的解决了相关技术中专用承载创建方案造成空口资源浪费的问题。
具体的，所述若确定终端从5G移动到4G，且需要发起创建专用承载的过程；则在修改承载响应消息中，捎带创建专用承载请求，发送给服务网关的步骤包括：接收到服务网关发送的修改承载请求后，确定终端从5G移动到4G，且需要发起创建专用承载的过程；在修改承载响应消息中，捎带创建专用承载请求，发送给服务网关。
下面结合移动性管理实体和分组数据网络网关两侧，对本公开实施例提供的所述专用承载创建方法进行进一步说明。
为了解决上述技术问题，本公开实施例提供了一种专用承载创建方法， 下面以两种具体实例进行说明，第一种以MME侧为主，可以概述为MME判断出UE从5G移动到4G后(可根据GUTI类型来判断)，保持NAS信令连接不释放；MME在收到PGW发出的创建专用承载请求后，发送初始终端上下文建立请求Initial UE context Setup消息到eNB，请求eNB为UE建立用户面承载。MME继续专用承载建立过程。具体如下：根据GUTI判断保持NAS连接，如图5所示：
步骤51：UE发起TAU trigger(TAU触发)；
步骤52：UE向MME发送TAU request(TAU请求，携带Old GUTI-旧的GUTI)；
步骤51-52.当UE从5G网络移动到4G网络后，UE发起TAU过程，消息中携带从5G GUTI映射而来的4G GUTI，即Old GUTI(Mapped GUTI)，另外UE可以在GUTI type(GUTI的类型)中指示该GUTI是从5G GUTI映射而来。如下：
Figure PCTCN2018104821-appb-000001
IEI为Information element identifier(信息元素标识符)，spare为保留值。
其中，GUTI type中，00，01的含义仍然和相关技术一致，10代表GUTI是从5G GUTI映射而来。
步骤53：MME与AMF之间交互Context Request/Response(上下文请求/响应)；
步骤54：MME向SGW发送Create Session Request(创建会话请求)；
步骤55：SGW向PGW-C+SMF发送Modify Bearer Request(修改承载请求)；
步骤56：PGW-C+SMF向SGW返回Modify Bearer Response(修改承载响应)；
步骤57：SGW向MME返回Create Session Response(创建会话响应)；
步骤53-57.MME先从AMF获取UE的上下文context，然后根据UE  context，向PGW-C+SMF更新UE的分组数据网络连接PDN connection。
步骤58：MME向UE发送TAU Accept(跟踪区更新接受)；
步骤59：UE向MME返回TAU Complete(跟踪区更新完成)；
步骤510：MME执行Keep NAS signaling connection(保持非接入层信令连接)；
步骤58-510.MME向UE发送TAU Accept消息后或者收到TAU Complete消息后，由于MME识别出UE是从5G移动到4G，因此仍然保持UE在连接态，即在足够长的时间内保持UE的NAS连接(以及与eNB的S1接口的连接)不释放，该时长应该大于UE本地释放NAS信令连接的时长(相关技术中UE触发本地释放NAS信令连接的时长为10秒)。
步骤511：PGW-C+SMF向SGW发送Create bearer Request(创建承载请求)；
步骤512：SGW向MME转发Create bearer Request(创建承载请求)；
步骤511-512.当PGW-C在步骤55收到服务网关SGW发来的Modify Bearer Request消息后，可能会触发专用承载的建立过程，因此在发送Modify Bearer Response消息后，向SGW发送Create Bearer Request来发起专用承载的建立。
步骤513：MME向eNB发送Initial UE context Setup Request(初始终端上下文建立请求)；
当MME收到Create Bearer Request后，将利用已有的S1连接，向eNB发送Initial UE context Setup消息来触发eNB创建UE context和空口DRB。MME可能在Initial UE context Setup Request消息中同时请求eNB建立PGW所请求的专用承载，也可能在Initial UE context Setup过程完成之后，向eNB发送承载建立请求Bearer Setup Request消息来创建专用承载。
进一步，可在基站为所述终端创建空口用户面承载的同时或者完成之后，MME利用所述非接入层连接向终端发送创建专用承载的请求，终端给予响应。
步骤514：UE与eNB之间实现了Radio Bearer Establishment(无线承载建立)；
步骤515：eNB向MME返回Initial UE context Setup Complete(初始终 端上下文建立完成)；
步骤516：MME向SGW发送Create bearer Response(创建承载响应)；
步骤517：SGW向PGW-C+SMF转发Create bearer Response(创建承载响应)；
步骤514-517.eNB根据MME的请求创建空口承载，然后向MME返回响应。MME向PGW-C+SMF返回响应。此后UE进入连接态。
第二种，以PGW侧为主，在PGW识别出UE从5G移动到4G后，若存在建立专用承载的需求，则在修改承载响应Modify Bearer Response中携带创建承载请求Create bearer Request，使得MME能够同时收到Modify Bearer Response消息和Create Bearer Request消息，可同步进行TAU过程和Initial UE context Setup过程，也可以先向UE发送TAU Accept消息，完成TAU过程，然后再发起Initial UE context Setup过程；具体如图6所示：
步骤61：UE发起TAU trigger(TAU触发)；
步骤62：UE向MME发送TAU request(TAU请求，携带Old GUTI-旧的GUTI)；
步骤61-62.MME接收UE的TAU请求，具体可参见步骤51-52的描述。
步骤63：MME与AMF之间交互Context Request/Response(上下文请求/响应)；
步骤64：MME向SGW发送Create Session Request(创建会话请求)；
步骤65：SGW向PGW-C+SMF发送Modify Bearer Request(修改承载请求)；
步骤66：PGW-C+SMF向SGW返回Modify Bearer Response(修改承载响应)，携带Create Bearer Request(创建承载请求)；
步骤67：SGW向MME返回Create Session Response(创建会话响应)，携带Create Bearer Request(创建承载请求)；
步骤63-67.MME先从AMF获取UE的context，然后根据UE context，向PGW-C+SMF更新UE的PDN connection。
其中，步骤66-67.当PGW-C收到SGW发来的Modify Bearer Request消息后，可能会触发专用承载的建立过程，因此PGW-C+SMF可以在发送 Modify Bearer Response消息时，可利用相关技术中的GTPv2协议的消息捎带机制(piggyback)，将用于创建专用承载的Create Bearer Request消息捎带在其中，使得MME能够同时收到Modify Bearer Response消息和Create Bearer Request消息。
步骤68：MME向UE发送TAU Accept(跟踪区更新接受)；
步骤69：UE向MME返回TAU Complete(跟踪区更新完成)；
步骤68-69.当MME收到Create Bearer Request后，可同步进行TAU过程和Initial UE context Setup过程，也可以先向UE发送TAU Accept消息，完成TAU过程，然后再发起Initial UE context Setup过程。
步骤610：MME向eNB发送Initial UE context Setup Request(初始终端上下文建立请求)；
MME利用已有的S1连接，向eNB发送Initial UE context Setup消息来触发eNB创建UE context和空口DRB。MME可能在Initial UE context Setup Request消息中同时请求eNB建立PGW所请求的专用承载，也可能在Initial UE context Setup过程完成之后，向eNB发送Bearer Setup Request消息来创建专用承载。
进一步，可在基站为所述终端创建空口用户面承载的同时或者完成之后，MME利用所述非接入层连接向终端发送创建专用承载的请求，终端给予响应。
步骤611：UE与eNB之间实现了Radio Bearer Establishment(无线承载建立)；
步骤612：eNB向MME返回Initial UE context Setup Complete(初始终端上下文建立完成)；
步骤613：MME向SGW发送Create bearer Response(创建承载响应)；
步骤614：SGW向PGW-C+SMF转发Create bearer Response(创建承载响应)；
步骤611-614.eNB根据MME的请求创建空口承载，然后向MME返回响应。MME向PGW-C+SMF返回响应。此后UE进入连接态。
由上可知，本公开实施例提供的所述专用承载创建方法的第一种实例主要是：
(1)若MME确定UE从5G移动到4G，则在TAU过程完成后保持建立的NAS连接；
MME从PGW-C+SMF收到创建专用承载的请求后，利用已有的NAS连接完成专用承载建立过程。
(2)MME在TAU过程中，根据GUTI的类型或显示指示确定UE从5G移动到4G；
(3)MME在TAU过程完成后，保持建立的NAS连接，包括发出TAU Accept消息或者收到TAU complete消息后，保持建立的NAS连接。
(4)从PGW-C+SMF收到创建专用承载的请求，具体为在收到Create Session Response消息之后收到。
(5)MME保持建立的NAS连接一段时间后，若没有收到创建专用承载的请求，则释放所述NAS连接。
第二种实例主要是：
(1)MME从PGW-C+SMF收到创建专用承载的请求，具体为从创建会话响应Create Session Response消息中解析出。
(2)所述Create Bearer Request是PGW-C+SMF封装在Modify Bearer Response消息中，然后由SGW通过Create Session Response消息转发到MME。
本公开实施例提供的方案很显然能够避免在5G到4G的TAU过程中，不必要的进行空口承载的建立和删除。
本公开实施例还提供了一种移动性管理实体，包括：收发机、存储器、处理器及存储在所述存储器上并可在所述处理器上运行的计算机程序；所述处理器用于读取存储器中的程序，执行下列过程：
若在跟踪区更新过程中，根据终端提供的标识信息确定终端从5G移动到4G；
则在跟踪区更新完成后，保持控制平面的非接入层连接；
若通过所述收发机接收到分组数据网络网关发送的创建专用承载请求，则利用所述非接入层连接为所述终端创建专用承载。
本公开实施例提供的所述移动性管理实体通过若在跟踪区更新过程中，根据终端提供的标识信息确定终端从5G移动到4G；则在跟踪区更新完成后， 保持控制平面的非接入层连接；若接收到分组数据网络网关发送的创建专用承载请求，则利用所述非接入层连接为所述终端创建专用承载；能够根据实际需求按需的建立空口的承载，避免了MME在TAU过程中请求eNB创建空口用户面承载，而导致的空口资源浪费，很好的解决了相关技术中专用承载创建方案造成空口资源浪费的问题。
具体可如图7所示，本公开实施例的移动性管理实体，包括：
处理器71；以及通过总线接口72与所述处理器71相连接的存储器73，所述存储器73用于存储所述处理器71在执行操作时所使用的程序和数据，当处理器71调用并执行所述存储器73中所存储的程序和数据时，执行下列过程：
若在跟踪区更新过程中，根据终端提供的标识信息确定终端从5G移动到4G；
则在跟踪区更新完成后，保持控制平面的非接入层连接；
若通过所述收发机74接收到分组数据网络网关发送的创建专用承载请求，则利用所述非接入层连接为所述终端创建专用承载。
其中，收发机74与总线接口72连接，用于在处理器71的控制下接收和发送数据。
需要说明的是，在图7中，总线架构可以包括任意数量的互联的总线和桥，具体由处理器71代表的一个或多个处理器和存储器73代表的存储器的各种电路链接在一起。总线架构还可以将诸如外围设备、稳压器和功率管理电路等之类的各种其他电路链接在一起，这些都是本领域所公知的，因此，本文不再对其进行进一步描述。总线接口提供接口。收发机74可以是多个元件，即包括发送机和收发机，提供用于在传输介质上与各种其他装置通信的单元。处理器71负责管理总线架构和通常的处理，存储器73可以存储处理器71在执行操作时所使用的数据。
本领域技术人员可以理解，实现上述实施例的全部或者部分步骤可以通过硬件来完成，也可以通过计算机程序来指示相关的硬件来完成，所述计算机程序包括执行上述方法的部分或者全部步骤的指令；且该计算机程序可以存储于一可读存储介质中，存储介质可以是任何形式的存储介质。
其中，所述处理器具体用于：在跟踪区更新完成后，在预设时间段内保持控制平面的非接入层连接；若在预设时间段内未接收到分组数据网络网关发送的创建专用承载请求，则释放控制平面的非接入层连接。
具体的，所述处理器具体用于：若接收到分组数据网络网关发送的创建专用承载请求，则在基站为所述终端创建空口用户面承载的同时或者完成之后，利用所述非接入层连接向终端发送创建专用承载的请求。
进一步的，所述处理器还用于：利用所述非接入层连接向终端发送创建专用承载的请求，之前或者同时，向基站发送初始终端上下文建立请求，触发所述基站为所述终端创建空口用户面承载。
优选的，所述终端提供的标识信息为全球唯一临时终端标识的类型。
对于若通过所述收发机接收到分组数据网络网关发送的创建专用承载请求，则利用所述非接入层连接为所述终端创建专用承载的操作，本公开实施例提供两种具体实现方式，如下：
第一种，所述处理器具体用于：若在跟踪区更新完成后接收到分组数据网络网关发送的创建专用承载请求，则利用保持的所述非接入层连接向终端发送创建专用承载的请求。
第二种，所述处理器具体用于：若通过所述收发机接收到接收服务网关发送的创建会话响应，所述创建会话响应中携带分组数据网络网关发送的创建专用承载请求；则从所述创建会话响应中解析出所述创建专用承载请求；根据所述创建专用承载请求，利用所述非接入层连接向终端发送创建专用承载的请求。
其中，上述移动性管理实体侧的专用承载创建方法的所述实现实施例均适用于该移动性管理实体的实施例中，也能达到相同的技术效果。
本公开实施例还提供了一种分组数据网络网关，包括：收发机、存储器、处理器及存储在所述存储器上并可在所述处理器上运行的计算机程序；所述处理器用于读取存储器中的程序，执行下列过程：
若确定终端从5G移动到4G，且需要发起创建专用承载的过程；则在修改承载响应消息中，捎带创建专用承载请求，通过所述收发机发送给服务网关，触发所述服务网关通过创建会话响应将所述创建专用承载请求捎带给移 动性管理实体。
本公开实施例提供的所述分组数据网络网关通过若确定终端从5G移动到4G，且需要发起创建专用承载的过程；则在修改承载响应消息中，捎带创建专用承载请求，发送给服务网关，触发所述服务网关通过创建会话响应将所述创建专用承载请求捎带给移动性管理实体；进而使得移动性管理实体能够在跟踪区更新完成之前，接收到分组数据网络网关发送的创建专用承载请求，从而利用已有的非接入层连接为所述终端创建专用承载；实现了根据实际需求按需的建立空口的承载的目的，避免了MME在TAU过程中请求eNB创建空口用户面承载，而导致的空口资源浪费，很好的解决了相关技术中专用承载创建方案造成空口资源浪费的问题。
具体可如图8所示，本公开实施例的分组数据网络网关，包括：
处理器81；以及通过总线接口82与所述处理器81相连接的存储器83，所述存储器83用于存储所述处理器81在执行操作时所使用的程序和数据，当处理器81调用并执行所述存储器83中所存储的程序和数据时，执行下列过程：
若确定终端从5G移动到4G，且需要发起创建专用承载的过程；则在修改承载响应消息中，捎带创建专用承载请求，通过所述收发机84发送给服务网关，触发所述服务网关通过创建会话响应将所述创建专用承载请求捎带给移动性管理实体。
其中，收发机84与总线接口82连接，用于在处理器81的控制下接收和发送数据。
需要说明的是，在图8中，总线架构可以包括任意数量的互联的总线和桥，具体由处理器81代表的一个或多个处理器和存储器83代表的存储器的各种电路链接在一起。总线架构还可以将诸如外围设备、稳压器和功率管理电路等之类的各种其他电路链接在一起，这些都是本领域所公知的，因此，本文不再对其进行进一步描述。总线接口提供接口。收发机84可以是多个元件，即包括发送机和收发机，提供用于在传输介质上与各种其他装置通信的单元。处理器81负责管理总线架构和通常的处理，存储器83可以存储处理器81在执行操作时所使用的数据。
本领域技术人员可以理解，实现上述实施例的全部或者部分步骤可以通过硬件来完成，也可以通过计算机程序来指示相关的硬件来完成，所述计算机程序包括执行上述方法的部分或者全部步骤的指令；且该计算机程序可以存储于一可读存储介质中，存储介质可以是任何形式的存储介质。
具体的，所述处理器具体用于：通过所述收发机接收到服务网关发送的修改承载请求后，确定终端从5G移动到4G，且需要发起创建专用承载的过程；在修改承载响应消息中，捎带创建专用承载请求，通过所述收发机发送给服务网关。
其中，上述分组数据网络网关侧的专用承载创建方法的所述实现实施例均适用于该分组数据网络网关的实施例中，也能达到相同的技术效果。
本公开实施例还提供了一种计算机可读存储介质，其上存储有计算机程序，该程序被处理器执行时实现上述移动性管理实体侧的专用承载创建方法的步骤。
其中，上述移动性管理实体侧的专用承载创建方法的所述实现实施例均适用于该计算机可读存储介质的实施例中，也能达到相同的技术效果。
本公开实施例还提供了一种计算机可读存储介质，其上存储有计算机程序，该程序被处理器执行时实现上述分组数据网络网关侧的专用承载创建方法的步骤。
其中，上述分组数据网络网关侧的专用承载创建方法的所述实现实施例均适用于该计算机可读存储介质的实施例中，也能达到相同的技术效果。
本公开实施例还提供了一种专用承载创建装置，应用于移动性管理实体，如图9所示，包括：
第一处理模块91，用于若在跟踪区更新过程中，根据终端提供的标识信息确定终端从5G移动到4G；
则在跟踪区更新完成后，保持控制平面的非接入层连接；
第二处理模块92，用于若接收到分组数据网络网关发送的创建专用承载请求，则利用所述非接入层连接为所述终端创建专用承载。
本公开实施例提供的所述专用承载创建装置通过若在跟踪区更新过程中，根据终端提供的标识信息确定终端从5G移动到4G；则在跟踪区更新完成后， 保持控制平面的非接入层连接；若接收到分组数据网络网关发送的创建专用承载请求，则利用所述非接入层连接为所述终端创建专用承载；能够根据实际需求按需的建立空口的承载，避免了MME在TAU过程中请求eNB创建空口用户面承载，而导致的空口资源浪费，很好的解决了相关技术中专用承载创建方案造成空口资源浪费的问题。
其中，所述在第一处理模块包括：第一处理子模，用于在跟踪区更新完成后，在预设时间段内保持控制平面的非接入层连接；第二处理子模块，用于若在预设时间段内未接收到分组数据网络网关发送的创建专用承载请求，则释放控制平面的非接入层连接。
具体的，所述第二处理模块包括：第一发送子模块，用于若接收到分组数据网络网关发送的创建专用承载请求，则在基站为所述终端创建空口用户面承载的同时或者完成之后，利用所述非接入层连接向终端发送创建专用承载的请求。
进一步的，所述专用承载创建装置还包括：第一发送模块，用于利用所述非接入层连接向终端发送创建专用承载的请求，之前或者同时，向基站发送初始终端上下文建立请求，触发所述基站为所述终端创建空口用户面承载。
优选的，所述终端提供的标识信息为全球唯一临时终端标识的类型。
对于第二处理模块，本公开实施例提供两种具体实现方式，如下：
第一种，所述第二处理模块包括：第三处理子模块，用于若在跟踪区更新完成后接收到分组数据网络网关发送的创建专用承载请求，则利用保持的所述非接入层连接向终端发送创建专用承载的请求。
第二种，所述第二处理模块包括：第四处理子模块，用于若接收到接收服务网关发送的创建会话响应，所述创建会话响应中携带分组数据网络网关发送的创建专用承载请求；则从所述创建会话响应中解析出所述创建专用承载请求；第五处理子模块，用于根据所述创建专用承载请求，利用所述非接入层连接向终端发送创建专用承载的请求。
其中，上述移动性管理实体侧的专用承载创建方法的所述实现实施例均适用于该专用承载创建装置的实施例中，也能达到相同的技术效果。
本公开实施例还提供了一种专用承载创建装置，应用于分组数据网络网 关，如图10所示，包括：
第三处理模块101，用于若确定终端从5G移动到4G，且需要发起创建专用承载的过程；则在修改承载响应消息中，捎带创建专用承载请求，发送给服务网关，触发所述服务网关通过创建会话响应将所述创建专用承载请求捎带给移动性管理实体。
本公开实施例提供的所述专用承载创建装置通过若确定终端从5G移动到4G，且需要发起创建专用承载的过程；则在修改承载响应消息中，捎带创建专用承载请求，发送给服务网关，触发所述服务网关通过创建会话响应将所述创建专用承载请求捎带给移动性管理实体；进而使得移动性管理实体能够在跟踪区更新完成之前，接收到分组数据网络网关发送的创建专用承载请求，从而利用已有的非接入层连接为所述终端创建专用承载；实现了根据实际需求按需的建立空口的承载的目的，避免了MME在TAU过程中请求eNB创建空口用户面承载，而导致的空口资源浪费，很好的解决了相关技术中专用承载创建方案造成空口资源浪费的问题。
具体的，所述第三处理模块包括：第六处理子模块，用于接收到服务网关发送的修改承载请求后，确定终端从5G移动到4G，且需要发起创建专用承载的过程；第七处理子模块，用于在修改承载响应消息中，捎带创建专用承载请求，发送给服务网关。
其中，上述分组数据网络网关侧的专用承载创建方法的所述实现实施例均适用于该专用承载创建装置的实施例中，也能达到相同的技术效果。
需要说明的是，此说明书中所描述的许多功能部件都被称为模块/子模块，以便更加特别地强调其实现方式的独立性。
本公开实施例中，模块/子模块可以用软件实现，以便由各种类型的处理器执行。举例来说，一个标识的可执行代码模块可以包括计算机指令的一个或多个物理或者逻辑块，举例来说，其可以被构建为对象、过程或函数。尽管如此，所标识模块的可执行代码无需物理地位于一起，而是可以包括存储在不同位里上的不同的指令，当这些指令逻辑上结合在一起时，其构成模块并且实现该模块的规定目的。
实际上，可执行代码模块可以是单条指令或者是许多条指令，并且甚至 可以分布在多个不同的代码段上，分布在不同程序当中，以及跨越多个存储器设备分布。同样地，操作数据可以在模块内被识别，并且可以依照任何适当的形式实现并且被组织在任何适当类型的数据结构内。所述操作数据可以作为单个数据集被收集，或者可以分布在不同位置上(包括在不同存储设备上)，并且至少部分地可以仅作为电子信号存在于系统或网络上。
在模块可以利用软件实现时，考虑到相关技术中硬件工艺的水平，所以可以以软件实现的模块，在不考虑成本的情况下，本领域技术人员都可以搭建对应的硬件电路来实现对应的功能，所述硬件电路包括常规的超大规模集成(VLSI)电路或者门阵列以及诸如逻辑芯片、晶体管之类的相关技术中的半导体或者是其它分立的元件。模块还可以用可编程硬件设备，诸如现场可编程门阵列、可编程阵列逻辑、可编程逻辑设备等实现。
以上所述的是本公开的优选实施方式，应当指出对于本技术领域的普通人员来说，在不脱离本公开所述原理前提下，还可以作出若干改进和润饰，这些改进和润饰也应视为本公开的保护范围。

Claims (22)

  1. 一种专用承载创建方法，应用于移动性管理实体，包括：
    若在跟踪区更新过程中，根据终端提供的标识信息确定终端从5G移动到4G；
    则在跟踪区更新完成后，保持控制平面的非接入层连接；
    若接收到分组数据网络网关发送的创建专用承载请求，则利用所述非接入层连接为所述终端创建专用承载。
  2. 根据权利要求1所述的专用承载创建方法，其中，所述在跟踪区更新完成后，保持控制平面的非接入层连接的步骤包括：
    在跟踪区更新完成后，在预设时间段内保持控制平面的非接入层连接；
    若在预设时间段内未接收到分组数据网络网关发送的创建专用承载请求，则释放控制平面的非接入层连接。
  3. 根据权利要求1所述的专用承载创建方法，其中，所述若接收到分组数据网络网关发送的创建专用承载请求，则利用所述非接入层连接为所述终端创建专用承载的步骤包括：
    若接收到分组数据网络网关发送的创建专用承载请求，则在基站为所述终端创建空口用户面承载的同时或者完成之后，利用所述非接入层连接向终端发送创建专用承载的请求。
  4. 根据权利要求3所述的专用承载创建方法，其中，利用所述非接入层连接向终端发送创建专用承载的请求，之前或者同时还包括：
    向基站发送初始终端上下文建立请求，触发所述基站为所述终端创建空口用户面承载。
  5. 根据权利要求1所述的专用承载创建方法，其中，所述终端提供的标识信息为全球唯一临时终端标识的类型。
  6. 根据权利要求1至5任一项所述的专用承载创建方法，其中，所述若接收到分组数据网络网关发送的创建专用承载请求，则利用所述非接入层连接为所述终端创建专用承载的步骤包括：
    若在跟踪区更新完成后接收到分组数据网络网关发送的创建专用承载请 求，则利用保持的所述非接入层连接向终端发送创建专用承载的请求。
  7. 根据权利要求1所述的专用承载创建方法，其中，所述若接收到分组数据网络网关发送的创建专用承载请求，则利用已有的非接入层连接为所述终端创建专用承载的步骤包括：
    若接收到接收服务网关发送的创建会话响应，所述创建会话响应中携带分组数据网络网关发送的创建专用承载请求；则从所述创建会话响应中解析出所述创建专用承载请求；
    根据所述创建专用承载请求，利用所述非接入层连接向终端发送创建专用承载的请求。
  8. 一种专用承载创建方法，应用于分组数据网络网关，包括：
    若确定终端从5G移动到4G，且需要发起创建专用承载的过程；则在修改承载响应消息中，捎带创建专用承载请求，发送给服务网关，触发所述服务网关通过创建会话响应将所述创建专用承载请求捎带给移动性管理实体。
  9. 根据权利要求8所述的专用承载创建方法，其中，所述若确定终端从5G移动到4G，且需要发起创建专用承载的过程；则在修改承载响应消息中，捎带创建专用承载请求，发送给服务网关的步骤包括：
    接收到服务网关发送的修改承载请求后，确定终端从5G移动到4G，且需要发起创建专用承载的过程；
    在修改承载响应消息中，捎带创建专用承载请求，发送给服务网关。
  10. 一种移动性管理实体，包括：收发机、存储器、处理器及存储在所述存储器上并可在所述处理器上运行的计算机程序；其中，所述处理器用于读取存储器中的程序，执行下列过程：
    若在跟踪区更新过程中，根据终端提供的标识信息确定终端从5G移动到4G；
    则在跟踪区更新完成后，保持控制平面的非接入层连接；
    若通过所述收发机接收到分组数据网络网关发送的创建专用承载请求，则利用所述非接入层连接为所述终端创建专用承载。
  11. 根据权利要求10所述的移动性管理实体，其中，所述处理器具体用于：
    在跟踪区更新完成后，在预设时间段内保持控制平面的非接入层连接；
    若在预设时间段内未接收到分组数据网络网关发送的创建专用承载请求，则释放控制平面的非接入层连接。
  12. 根据权利要求10所述的移动性管理实体，其中，所述处理器具体用于：
    若接收到分组数据网络网关发送的创建专用承载请求，则在基站为所述终端创建空口用户面承载的同时或者完成之后，利用所述非接入层连接向终端发送创建专用承载的请求。
  13. 根据权利要求12所述的移动性管理实体，其中，所述处理器还用于：
    利用所述非接入层连接向终端发送创建专用承载的请求，之前或者同时，向基站发送初始终端上下文建立请求，触发所述基站为所述终端创建空口用户面承载。
  14. 根据权利要求10所述的移动性管理实体，其中，所述终端提供的标识信息为全球唯一临时终端标识的类型。
  15. 根据权利要求10至14任一项所述的移动性管理实体，其中，所述处理器具体用于：
    若在跟踪区更新完成后接收到分组数据网络网关发送的创建专用承载请求，则利用保持的所述非接入层连接向终端发送创建专用承载的请求。
  16. 根据权利要求10所述的移动性管理实体，其中，所述处理器具体用于：
    若通过所述收发机接收到接收服务网关发送的创建会话响应，所述创建会话响应中携带分组数据网络网关发送的创建专用承载请求；则从所述创建会话响应中解析出所述创建专用承载请求；
    根据所述创建专用承载请求，利用所述非接入层连接向终端发送创建专用承载的请求。
  17. 一种分组数据网络网关，包括：收发机、存储器、处理器及存储在所述存储器上并可在所述处理器上运行的计算机程序；其中，所述处理器用于读取存储器中的程序，执行下列过程：
    若确定终端从5G移动到4G，且需要发起创建专用承载的过程；则在修 改承载响应消息中，捎带创建专用承载请求，通过所述收发机发送给服务网关，触发所述服务网关通过创建会话响应将所述创建专用承载请求捎带给移动性管理实体。
  18. 根据权利要求17所述的分组数据网络网关，其中，所述处理器具体用于：
    通过所述收发机接收到服务网关发送的修改承载请求后，确定终端从5G移动到4G，且需要发起创建专用承载的过程；
    在修改承载响应消息中，捎带创建专用承载请求，通过所述收发机发送给服务网关。
  19. 一种计算机可读存储介质，其上存储有计算机程序，该程序被处理器执行时实现如权利要求1至7任一项所述的专用承载创建方法的步骤。
  20. 一种计算机可读存储介质，其上存储有计算机程序，该程序被处理器执行时实现如权利要求8或9所述的专用承载创建方法的步骤。
  21. 一种专用承载创建装置，应用于移动性管理实体，包括：
    第一处理模块，用于若在跟踪区更新过程中，根据终端提供的标识信息确定终端从5G移动到4G；
    则在跟踪区更新完成后，保持控制平面的非接入层连接；
    第二处理模块，用于若接收到分组数据网络网关发送的创建专用承载请求，则利用所述非接入层连接为所述终端创建专用承载。
  22. 一种专用承载创建装置，应用于分组数据网络网关，其中，包括：
    第三处理模块，用于若确定终端从5G移动到4G，且需要发起创建专用承载的过程；则在修改承载响应消息中，捎带创建专用承载请求，发送给服务网关，触发所述服务网关通过创建会话响应将所述创建专用承载请求捎带给移动性管理实体。
PCT/CN2018/104821 2017-11-21 2018-09-10 专用承载创建方法、移动性管理实体及分组数据网络网关 WO2019100813A1 (zh)

Priority Applications (4)

Application Number Priority Date Filing Date Title
JP2020528038A JP7039697B2 (ja) 2017-11-21 2018-09-10 専用ベアラ作成方法、移動性管理エンティティおよびパケットデータネットワークゲートウェイ
KR1020207017630A KR102344162B1 (ko) 2017-11-21 2018-09-10 전용 베어러 구축 방법, 이동성 관리 개체 및 패킷 데이터 네트워크 게이트웨이
US16/765,840 US11076375B2 (en) 2017-11-21 2018-09-10 Dedicated bearer creation method, mobility management entity, and packet data network gateway
EP18880786.1A EP3716680B1 (en) 2017-11-21 2018-09-10 Dedicated bearer creation method and mobility management entity

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201711168078.4A CN109819483B (zh) 2017-11-21 2017-11-21 专用承载创建方法、移动性管理实体及分组数据网络网关
CN201711168078.4 2017-11-21

Publications (1)

Publication Number Publication Date
WO2019100813A1 true WO2019100813A1 (zh) 2019-05-31

Family

ID=66600594

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2018/104821 WO2019100813A1 (zh) 2017-11-21 2018-09-10 专用承载创建方法、移动性管理实体及分组数据网络网关

Country Status (6)

Country Link
US (1) US11076375B2 (zh)
EP (1) EP3716680B1 (zh)
JP (1) JP7039697B2 (zh)
KR (1) KR102344162B1 (zh)
CN (1) CN109819483B (zh)
WO (1) WO2019100813A1 (zh)

Families Citing this family (8)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
KR102371810B1 (ko) * 2017-10-20 2022-03-10 삼성전자주식회사 다중 무선 접속 기술(Multi-Radio Access Technology)을 지원하는 무선 접속 시스템에서 단말이 데이터를 송수신하기 위한 방법 및 장치.
EP4325926A3 (en) * 2019-06-14 2024-04-03 Honor Device Co., Ltd. Non-access stratum connection handling
CN112118606B (zh) * 2019-06-21 2022-04-29 华为技术有限公司 实现业务连续的方法、相关装置及系统
CN110944367B (zh) * 2019-12-20 2021-12-24 广东工业大学 一种4g与5g互操作的方法
CN113825186B (zh) * 2020-06-19 2023-08-01 维沃移动通信有限公司 离开网络的控制方法、装置和通信设备
CN112468981B (zh) * 2020-11-26 2022-03-01 北京紫光展锐通信技术有限公司 通信方法、装置及设备
US11483750B1 (en) 2021-04-07 2022-10-25 Cisco Technology, Inc. User equipment (UE) mobility between evolved packet system (EPS) and fifth generation (5G) system (5GS) using a simplified 3GPP core architecture for interworking
CN113923613B (zh) * 2021-10-14 2022-09-16 维沃移动通信有限公司 通话处理方法、装置、电子设备及存储介质

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101478743A (zh) * 2008-01-03 2009-07-08 大唐移动通信设备有限公司 一种eps承载管理的方法和装置
CN102111745A (zh) * 2010-10-15 2011-06-29 电信科学技术研究院 Eps系统的会话管理过程的重发起方法和设备
CN102281519A (zh) * 2010-06-12 2011-12-14 中兴通讯股份有限公司 一种承载修改方法及系统
CN103155688A (zh) * 2011-08-31 2013-06-12 华为技术有限公司 一种承载的处理方法、系统及装置

Family Cites Families (24)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP5138045B2 (ja) * 2007-11-16 2013-02-06 ノキア シーメンス ネットワークス オサケユキチュア システム間ハンドオーバのためのサービス品質のマッピング
WO2010078255A1 (en) * 2008-12-29 2010-07-08 Interdigital Patent Holdings, Inc. Method and apparatus for tracking area update procedure and eps bearer contexts representation
CN102714818B (zh) * 2009-10-30 2016-06-15 交互数字专利控股公司 用于无线通信的信令
EP2925077A1 (en) * 2010-02-12 2015-09-30 Interdigital Patent Holdings, Inc. Method and apparatus for supporting machine-type communications
EP2509345A1 (en) * 2011-04-05 2012-10-10 Panasonic Corporation Improved small data transmissions for machine-type-communication (MTC) devices
WO2013009892A1 (en) * 2011-07-11 2013-01-17 Interdigital Patent Holdings, Inc. Systems and methods for establishing and maintaining multiple cellular connections and/or interfaces
US9648173B2 (en) * 2012-03-01 2017-05-09 Cellco Partnership Method and system to provide network status information to a device
US9848322B2 (en) * 2013-01-17 2017-12-19 Intel IP Corporation Method, apparatus and system for managing bearers in a wireless communication system
AU2014219562B2 (en) * 2013-02-22 2017-09-21 Samsung Electronics Co., Ltd. Method and system for providing simultaneous connectivity between multiple E-NodeBs and user equipment
EP3183907A4 (en) * 2014-08-22 2018-08-29 Nokia Solutions and Networks Oy Low latency service connection setup in new service area
EP3195683A1 (en) * 2014-08-25 2017-07-26 Nokia Technologies Oy Methods and apparatus for wireless connection management
US9832719B2 (en) * 2014-10-17 2017-11-28 Qualcomm Incorporated Selection of a serving node in a wireless communication system
WO2016126238A1 (en) * 2015-02-03 2016-08-11 Nokia Solutions And Networks Oy Improvements in dual connectivity for different access networks
US9948519B2 (en) * 2015-08-14 2018-04-17 Telefonaktiebolaget Lm Ericsson (Publ) Systems and methods for establishing a packet data network connection for a wireless communication device
US10512001B2 (en) * 2015-08-17 2019-12-17 Lg Electronics Inc. Method for rearranging gateway and method for generating dedicated bearer
CN112996069A (zh) * 2015-10-06 2021-06-18 苹果公司 使用3gpp无线电接入技术的接入系统之间的双无线电操作
TWI738703B (zh) * 2016-01-05 2021-09-11 美商內數位專利控股公司 在傳訊平面上傳送小資料ｎａｓ協定之增強
CA3016750C (en) * 2016-03-07 2020-12-29 Telefonaktiebolaget Lm Ericsson (Publ) Method and nodes for handling bearers
WO2017200269A1 (ko) * 2016-05-16 2017-11-23 엘지전자(주) 무선 통신 시스템에서 착신 데이터 제어 방법 및 이를 위한 장치
JP6738908B2 (ja) * 2016-05-17 2020-08-12 コンヴィーダ ワイヤレス， エルエルシー 接続がｐｄｎゲートウェイとローカルゲートウェイとの間のデータのルーティングを有効にすることを指示する方法および装置
EP3469816A1 (en) * 2016-07-04 2019-04-17 Huawei Technologies Co., Ltd. Session management for massive machine type communication in 5g networks
KR102241996B1 (ko) * 2017-01-09 2021-04-19 엘지전자 주식회사 무선 통신 시스템에서 네트워크간 상호연동 방법 및 이를 위한 장치
CN110169160B (zh) * 2017-09-14 2022-07-29 Lg电子株式会社 用于在无线通信系统中执行v2x通信的方法及其设备
US10694427B2 (en) * 2017-09-27 2020-06-23 Intel IP Corporation Solution for vehicle-to-everything (V2X) communication authorization in 5G system

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101478743A (zh) * 2008-01-03 2009-07-08 大唐移动通信设备有限公司 一种eps承载管理的方法和装置
CN102281519A (zh) * 2010-06-12 2011-12-14 中兴通讯股份有限公司 一种承载修改方法及系统
CN102111745A (zh) * 2010-10-15 2011-06-29 电信科学技术研究院 Eps系统的会话管理过程的重发起方法和设备
CN103155688A (zh) * 2011-08-31 2013-06-12 华为技术有限公司 一种承载的处理方法、系统及装置

Non-Patent Citations (2)

* Cited by examiner, † Cited by third party
Title
"Technical Specification Group Services and System Aspects; System Architecture for the 5G System; Stage 2 (Release 15", 3GPP TS 23.501, 30 September 2017 (2017-09-30), XP051337398 *
See also references of EP3716680A4 *

Also Published As

Publication number Publication date
CN109819483A (zh) 2019-05-28
EP3716680A1 (en) 2020-09-30
JP7039697B2 (ja) 2022-03-22
KR20200087843A (ko) 2020-07-21
EP3716680A4 (en) 2021-02-24
US11076375B2 (en) 2021-07-27
CN109819483B (zh) 2020-09-11
EP3716680B1 (en) 2023-07-26
KR102344162B1 (ko) 2021-12-27
JP2021503859A (ja) 2021-02-12
US20200367190A1 (en) 2020-11-19

Similar Documents

Publication Publication Date Title
WO2019100813A1 (zh) 专用承载创建方法、移动性管理实体及分组数据网络网关
USRE49729E1 (en) Session information management method and apparatus
WO2018126535A1 (zh) 一种会话管理方法及装置
US20220046755A1 (en) Data Forwarding Method, Apparatus, and System
US10448297B2 (en) Network node, mobile terminal, base station and methods performed therein
WO2020156116A1 (zh) 上下文存储方法及装置
US20170195926A1 (en) Control node, network node, and methods performed therein
CN112840701A (zh) 在5g系统到演进分组系统切换期间的用户面建立
KR20170133793A (ko) 이동통신 코어 망에서의 시그널링 방법 및 그 시스템
US11044696B2 (en) Downlink data notification message sending method, and apparatus
KR20200097336A (ko) 세션 확립을 위한 방법 및 장치
JP2020524451A (ja) 通信方法および通信装置
EP3739918B1 (en) Method and apparatus for transmitting downlink data
CN110505662B (zh) 一种策略控制方法、装置及系统
JP7350066B2 (ja) 無線通信の方法及び機器
WO2018127231A1 (zh) 一种终端空闲态的处理方法及装置
WO2020034802A1 (zh) 一种激活pdu会话的方法及设备
EP3876599B1 (en) Data forwarding method and apparatus, and master base station and slave base station
WO2020173146A1 (zh) 一种切换处理的方法、相关设备、程序产品以及存储介质
WO2019140561A1 (zh) 一种切换方法及装置、计算机存储介质
US10390383B2 (en) Timer-based handling of multiple connection requests
EP4360401A1 (en) Notification of sgw change for one or more pdn connections when combined sgw/pgw/smf set is deployed
CN108093470B (zh) 一种终端与从基站之间上行同步信息的处理方法及装置
TW202320569A (zh) 用於無線通訊的方法及使用者設備
WO2008154856A1 (fr) Procédé, entité de passerelle et dispositif de réseau servant à libérer des ressources de réseau

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: 18880786

Country of ref document: EP

Kind code of ref document: A1

ENP Entry into the national phase

Ref document number: 2020528038

Country of ref document: JP

Kind code of ref document: A

NENP Non-entry into the national phase

Ref country code: DE

ENP Entry into the national phase

Ref document number: 20207017630

Country of ref document: KR

Kind code of ref document: A

ENP Entry into the national phase

Ref document number: 2018880786

Country of ref document: EP

Effective date: 20200622