WO2019100762A1 - 承载标识的确定方法及装置、存储介质 - Google Patents

承载标识的确定方法及装置、存储介质 Download PDF

Info

Publication number
WO2019100762A1
WO2019100762A1 PCT/CN2018/099997 CN2018099997W WO2019100762A1 WO 2019100762 A1 WO2019100762 A1 WO 2019100762A1 CN 2018099997 W CN2018099997 W CN 2018099997W WO 2019100762 A1 WO2019100762 A1 WO 2019100762A1
Authority
WO
WIPO (PCT)
Prior art keywords
session
function entity
request
control function
target access
Prior art date
Application number
PCT/CN2018/099997
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 JP2020527958A priority Critical patent/JP7307060B2/ja
Priority to ES18880243T priority patent/ES2959775T3/es
Priority to KR1020207017828A priority patent/KR102349656B1/ko
Priority to EP18880243.3A priority patent/EP3585100B1/en
Priority to SG11202004699VA priority patent/SG11202004699VA/en
Priority to EP23187540.2A priority patent/EP4284083A3/en
Publication of WO2019100762A1 publication Critical patent/WO2019100762A1/zh
Priority to US16/556,210 priority patent/US10986543B2/en

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/0011—Control or signalling for completing the hand-off for data sessions of end-to-end connection
    • H04W36/0022—Control or signalling for completing the hand-off for data sessions of end-to-end connection for transferring data sessions between adjacent core network technologies
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • 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/0011—Control or signalling for completing the hand-off for data sessions of end-to-end connection
    • H04W36/0016—Hand-off preparation specially adapted for end-to-end data sessions
    • 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/0011—Control or signalling for completing the hand-off for data sessions of end-to-end connection
    • H04W36/0033—Control or signalling for completing the hand-off for data sessions of end-to-end connection with transfer of context information
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/02—Buffering or recovering information during reselection ; Modification of the traffic flow during hand-off
    • 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
    • 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

Definitions

  • the present disclosure relates to the field of next generation wireless communication (5G), and in particular, to a method and apparatus for determining a bearer identifier, and a storage medium.
  • 5G next generation wireless communication
  • FIG. 1 is a network architecture diagram related art fourth generation mobile communication system, in which each network The function of the meta is as follows:
  • the user equipment accesses the 4G network through the wireless air interface and obtains the service.
  • the terminal exchanges information through the air interface and the base station, and communicates through the non-access stratum (NAS) signaling and the core network. Entity interaction information.
  • NAS non-access stratum
  • the base station (Radio Access Network, RAN, or eNB) is responsible for air interface resource scheduling and air interface connection management of the terminal accessing the network.
  • Mobility management entity The core network control plane entity is mainly responsible for authentication, authorization, and subscription checking of users, and functions for user mobility management, PDN connection and bearer maintenance, and paging in user IDLE state.
  • S-GW Serving Gateway
  • Packet Data Network Gateway (PDN GW or P-GW):
  • the core network user plane function entity is the access point of the terminal accessing the PDN network. It is responsible for allocating the user IP address and the network triggered bearer establishment, modification and deletion. It also has the functions of quality of service (QoS), control billing, etc. It is the anchor point of the user in the 3GPP system, thus ensuring the IP address unchanged and ensuring business continuity.
  • the P-GW is further divided into two parts, one is a packet data gateway control entity (PGW-Control, PGW-C), and the other is a packet data gateway user plane entity (PGW-User, PGW- U).
  • PGW-C is responsible for signaling control
  • PGW-U is responsible for IP forwarding.
  • HSS Home Subscription Server
  • the Policy and charging control function (PCRF) is responsible for the formulation of policy decisions and charging rules.
  • the PCRF provides network control rules based on traffic data flows, including traffic data flow detection, Gating Control, quality of service control, and data flow based charging rules.
  • the PCRF sends its formulated policies and charging rules to the P-GW for execution.
  • next-generation communication systems NextGen System, 5GS
  • Next-generation communication systems can support Evolved Mobile Broadband (eMBB), Massive Machine Type Communication (mMTC), and ultra-reliable machines.
  • eMBB Evolved Mobile Broadband
  • mMTC Massive Machine Type Communication
  • ultra-reliable machines There are three types of services (Ultra Reliable Machine Type Communication, uMTC), which have different network characteristics.
  • uMTC Ultra Reliable Machine Type Communication
  • the user equipment accesses the network and obtains services through the next-generation wireless air interface.
  • the terminal exchanges information through the air interface and the base station, and interacts with the common control plane function of the core network and the session control plane through the non-access layer signaling. information.
  • the NextGen Radio Access Network is responsible for air interface resource scheduling and air interface connection management of the terminal access network.
  • the next generation base station can apply a new radio access technology (gNB) or an enhanced LTE technology (eLTE).
  • gNB new radio access technology
  • eLTE enhanced LTE technology
  • Session Management Function used to interact with the terminal, and is mainly responsible for processing the establishment, modification, and deletion of the Packet Data Unit session (PDU Session), and selecting the user plane function ( User Plane function (UPF), establishes a user plane connection between the UE and the UPF, and determines a QoS parameter of the session together with a Policy Control Function (PCF).
  • PDU Session Management Function used to interact with the terminal, and is mainly responsible for processing the establishment, modification, and deletion of the Packet Data Unit session (PDU Session), and selecting the user plane function ( User Plane function (UPF), establishes a user plane connection between the UE and the UPF, and determines a QoS parameter of the session together with a Policy Control Function (PCF).
  • PCF Policy Control Function
  • Access and Mobility Control Function A common control plane function in the core network.
  • a user has only one AMF, which is responsible for user authentication, authorization, and subscription checking to ensure that the user is a legitimate user; user mobility management, including location registration and temporary identity allocation; when the user initiates a PDU connection establishment request, select the appropriate SMF; forwarding non-access stratum signaling between the UE and the SMF; forwarding access layer (AS) signaling between the base station and the SMF.
  • AMF Access and Mobility Control Function
  • UPF User Plane Function
  • UPF Provides user plane processing functions, including data forwarding and QoS execution.
  • UPF also provides user plane anchors when users move to ensure business continuity.
  • PCF Policy Control Function
  • Unified Data Management Stores user subscription data, which is very similar to HSS in the 4G era.
  • NextGen System NextGen System
  • 5GS NextGen System
  • FIG. 3 is a network architecture diagram of 4G and 5G bidirectional handover in the related art, and the core feature is that the architecture diagram is compatible with 4G and 5G architectures, and PGW-C and SMF are combined, PGW-U and UPF are combined, PCF and PCRF In one, the user plane of the UE is always anchored on the UPF/PGW-U. Between the AMF and the MME, an N26 interface is added, and an inter-system handover request is sent on the interface. In this way, when the UE switches between LTE and 5G, seamless handover can be guaranteed.
  • each PDN connection established by the UE and the network includes one default bearer and multiple dedicated bearers.
  • Each bearer contains the corresponding service flows and their QoS parameters.
  • Each bearer has a corresponding bearer ID (EBI).
  • EBI bearer ID
  • the EBI is allocated by the MME. The EBI is unique among all PDN Connections of the UE. EBI has 4 bits, theoretically there are 16 values, but some of them are reserved, and at most 11 values are available.
  • the UE and the network establish a PDU session, which contains a default QOS flow and multiple dedicated quality of service flows.
  • Each QoS flow includes corresponding service flows, and its QoS parameters, such as a QoS profile and a packet filter.
  • Each Qos flow also has a corresponding identifier: Qos Flow ID ( QFI).
  • QFI Qos Flow ID
  • the seamless mobility of the UE between 4G and 5G systems including 4G to 5G handover and 4G to 5G idle state mobility, where the UE's IP address is unchanged.
  • the PDU session established by the 5G system is converted into the PDN connection in the 4G system.
  • the quality of service flow in the PDU session is converted to a bearer after being transferred to the 4G system. vice versa.
  • the SMF/PGW-C needs to allocate the session parameters/bearer information of the QG flow corresponding to the 4G system, and send the session parameters/bearing information to the UE.
  • the PGW-C/SMF also allocates the PDU connection and carries the corresponding 5G PDU session and Qos flow information, and sends the information to the UE.
  • the EBI allocation by the SMF will result in an EBI collision, ie the two SMFs are assigned the same EBI value.
  • a PDU session is established for the UE in the 5G system, and when the 4G session parameter is allocated for the Qos flow, the allocation of the EBI is performed by the AMF, and the remaining parameters are allocated by the SMF.
  • Scenario 1 The idle state mobility across the AMF, the UE sends a registration request to the target AMF, how does the AMF know which EBIs have been assigned on the source AMF;
  • Scenario 2 Cross-AMF handover, the UE needs to switch to the target AMF, how does the AMF know which EBI has been allocated on the source AMF;
  • Scenario 3 4G to 5G idle state mobility, the UE sends a registration request to the target AMF in the 5G system, how does the AMF know which EBI has been allocated on the 4G MME;
  • Scenario 4 4G to 5G connection state switching. After the UE switches to 5G, how does the target AMF know which EBIs have been allocated on the source MME;
  • the EBI allocation situation is used as the mobility context of the AMF in the related art.
  • the source AMF is passed to the target AMF.
  • this solution can only solve scenes one and two, and cannot solve scenes three and four.
  • the MME is modified and the MME is passed the EBI allocation information, then the transformation of the MME will be very complicated.
  • the EBI allocation information includes not only a list of EBI values, but also 5G session information corresponding to each EBI value. However, in 4G, these 5G session information are all allocated by PGW-C/SMF, which the MME cannot know.
  • the embodiments of the present disclosure provide a method and a device for determining a bearer identifier, and a storage medium, to at least solve the mobility events in the related art, such as idle state mobility in 5G, 4G to 5G, and connection state switching of 4G to 5G. After that, how to determine the assigned EBI information has not yet raised an effective solution.
  • a method for determining a bearer identifier including:
  • the target access and mobility control function entity sends a session update request to the session control plane function entity, and receives a session update response that carries the bearer identity allocation information fed back by the session control plane function entity.
  • the bearer identity allocation information is used to notify the target access and mobility control function entity: the source access and the mobility control function entity or the assigned bearer identity on the mobility management entity.
  • the session update request carries an indication of requesting bearer identification information.
  • the bearer identifier allocation information includes a bearer identifier list, or the bearer identifier allocation information includes: a bearer identifier list and at least one of the following: a priority corresponding to the bearer identifier and a PDU session identifier.
  • the target access and mobility control function entity sends a session update request to the session control plane function entity, including:
  • the target access and mobility control function entity receives the registration request sent by the terminal;
  • the target access and mobility control function entity After receiving the registration request, the target access and mobility control function entity requests the context of the terminal from the first network element of the source network;
  • the target access and mobility control function entity receives the context of the terminal sent by the first network element of the source network, and sends a session update request to the session control plane function entity according to the context.
  • the registration request includes: a registration request sent by a terminal that has entered the idle state in the 5G network or a registration request that is sent after the terminal that has entered the idle state in the 4G network moves to the 5G network.
  • it also includes:
  • the target access and mobility control function entity initiates a location update process to the unified data management function entity, and the location update process is used by the unified data management function entity to initiate a location deletion process to the target access and mobility control function entity.
  • the method further includes:
  • the target access and mobility control function entity receives a handover preparation response message sent by the target base station.
  • it also includes:
  • the target access and mobility control function entity receives the handover preparation request sent by the first network element of the source network after receiving the handover request sent by the source base station, where the handover preparation request carries the target base station information and the current session information;
  • the target access and mobility control function entity sends a PDU session switching request to the session control plane function entity according to the handover preparation request;
  • the target access and mobility control function entity receives N2 session information of the PDU session to be switched sent by the session control plane function entity;
  • the target access and mobility control function entity sends a handover preparation request to the target base station according to the session information of the PDU session to be switched, where the handover preparation request is used to request resource reservation;
  • the handover preparation response message carries the reserved radio resource information, the N2 response information, and the N3 tunnel information allocated for each PDU session that is successfully reserved.
  • the session update request carries the handover preparation response information.
  • the method further includes: the target access and mobility control function entity returns a handover response to the first network element of the source network; the handover response is used by the first network element of the source network to send a handover command to the source base station, where the handover command is used for The terminal switches from the source base station to the target base station.
  • the method further includes: the target access and mobility control function entity receiving the handover completion notification sent by the target base station.
  • the first network element of the source network includes: a source access and mobility control function entity or a mobility management entity.
  • the session control plane function entity includes: a session control plane function SMF entity or a session control plane function SMF entity and a packet data gateway control entity PGW-C.
  • a method for determining a bearer identity including:
  • the session control plane function entity receives the session update request sent by the target access and mobility control function entity, and feeds back the session update response carrying the bearer identity allocation information to the target access and mobility control function entity.
  • a device for determining a bearer identity which is applied to a target access and mobility control function entity, and includes:
  • a first sending module configured to send a session update request to the session control plane function entity
  • the first receiving module is configured to receive a session update response that carries the bearer identifier allocation information fed back by the session control plane function entity.
  • the bearer identifier allocation information is used to notify the target access and mobility control function entity: the source access and the mobility control function entity or the assigned bearer identifier on the mobility management entity.
  • the first receiving module is further configured to receive a registration request sent by the terminal, and is further configured to receive a context of the terminal sent by the first network element of the source network;
  • the first sending module is further configured to request the context of the terminal from the first network element of the source network, and is further configured to send a session update request to the session control plane functional entity according to the context.
  • the first network element of the source network includes: a source access and mobility control function entity or a mobility management entity.
  • a device for determining a bearer identifier which is applied to a session control plane function entity, and includes:
  • a second receiving module configured to receive a session update request sent by the target access and the mobility control function entity
  • the second sending module is configured to feed back a session update response carrying the bearer identity allocation information to the target access and mobility control function entity.
  • a storage medium including a stored program, wherein the determining method of determining any one of the above-described bearer identifiers is executed while the program is running.
  • the target access and mobility control function entity receives the session update response carrying the bearer identity allocation information fed back by the session control plane function entity, the idle state movement in the 5G and 4G to 5G can be solved in the related art.
  • the mobility events such as the 4G to 5G connection state switching, how to determine the allocated EBI information, the problem of an effective solution has not been proposed, and there is no special requirement for the MME, so that the traditional network does not need to be upgraded and implemented. Compatible with traditional networks.
  • FIG. 1 is a network architecture diagram of a fourth generation mobile communication system in the related art
  • FIG. 2 is a schematic diagram of a next-generation mobile communication network architecture in the related art
  • 3 is a network architecture diagram of 4G and 5G bidirectional handover in the related art
  • FIG. 4 is a flowchart (1) of a method for determining a bearer identifier according to an embodiment of the present disclosure
  • FIG. 5 is a flowchart (2) of a method for determining a bearer identifier according to an embodiment of the present disclosure
  • FIG. 6 is a structural block diagram (1) of a device for determining a bearer identifier according to an embodiment of the present disclosure
  • FIG. 7 is a structural block diagram (2) of a device for determining a bearer identifier according to an embodiment of the present disclosure
  • FIG. 8 is a flowchart (1) of a method for determining a bearer flag according to a preferred embodiment of the present disclosure
  • FIG. 9 is a flowchart (2) of a method for determining a bearer flag according to a preferred embodiment of the present disclosure
  • FIG. 10 is a flowchart (3) of a method for determining a bearer flag according to a preferred embodiment of the present disclosure
  • FIG. 11 is a flowchart (4) of a method of determining a bearer flag in accordance with a preferred embodiment of the present disclosure.
  • FIG. 4 is a flowchart (1) of a method for determining a bearer identifier according to an embodiment of the present disclosure. As shown in FIG. 4, the flow includes the following steps:
  • Step S402 the target access and mobility control function entity sends a session update request to the session control plane function entity;
  • Step S404 receiving a session update response that carries the bearer identifier allocation information fed back by the session control plane function entity.
  • the target access and mobility control function entity sends a session update request to the session control plane function entity, and receives a session update response that carries the bearer identity allocation information fed back by the session control plane function entity.
  • the target access and mobility control function entity can receive the session update response carrying the bearer identifier allocation information fed back by the session control plane function entity, and can solve the idle state mobility and 4G in the 5G internal, 4G to 5G in the related technology.
  • the mobility event such as 5G connection state switching, how to determine the allocated EBI information, the problem of effective solution has not been proposed, and there is no special requirement for the MME, so that the traditional network does not need to be upgraded and the traditional network is implemented. Compatible.
  • the bearer identity allocation information is used to notify the target access and mobility control function entity: the source access and the mobility control function entity or the assigned bearer identity on the mobility management entity.
  • the session update request carries an indication of requesting bearer identification information.
  • the bearer identifier allocation information includes a bearer identifier list, or the bearer identifier allocation information includes: a bearer identifier list and at least one of the following: a priority corresponding to the bearer identifier and a PDU session identifier.
  • the target access and mobility control function entity sends a session update request to the session control plane function entity, including:
  • the target access and mobility control function entity receives the registration request sent by the terminal;
  • the target access and mobility control function entity After receiving the registration request, the target access and mobility control function entity requests the context of the terminal from the first network element of the source network;
  • the target access and mobility control function entity receives the context of the terminal sent by the first network element of the source network, and sends a session update request to the session control plane function entity according to the context.
  • the registration request includes: a registration request sent by a terminal that has entered the idle state in the 5G network or a registration request that is sent after the terminal that has entered the idle state in the 4G network moves to the 5G network.
  • it also includes:
  • the method further includes:
  • the target access and mobility control function entity receives a handover preparation response message sent by the target base station.
  • it also includes:
  • the target access and mobility control function entity receives the handover preparation request sent by the first network element of the source network after receiving the handover request sent by the source base station, where the handover preparation request carries the target base station information and the current session information;
  • the target access and mobility control function entity sends a PDU session switching request to the session control plane function entity according to the handover preparation request;
  • the target access and mobility control function entity receives N2 session information of the PDU session to be switched sent by the session control plane function entity;
  • the target access and mobility control function entity sends a handover preparation request to the target base station according to the session information of the PDU session to be switched, where the handover preparation request is used to request resource reservation;
  • the handover preparation response message carries the reserved radio resource information, the N2 response information, and the N3 tunnel information allocated for each PDU session that is successfully reserved.
  • the session update request carries the handover preparation response information.
  • the method further includes: the target access and mobility control function entity returns a handover response to the first network element of the source network; the handover response is used by the first network element of the source network to send a handover command to the source base station, where the handover command is used for The terminal switches from the source base station to the target base station.
  • the method further includes: the target access and mobility control function entity receiving the handover completion notification sent by the target base station.
  • the first network element of the source network includes: a source access and mobility control function entity or a mobility management entity.
  • the session control plane function entity includes: a session control plane function SMF entity or a session control plane function SMF entity and a packet data gateway control entity PGW-C.
  • FIG. 5 is a flowchart (2) of a method for determining a bearer identifier according to an embodiment of the present disclosure. As shown in FIG. 5, the flow includes the following steps:
  • Step S502 the session control plane function entity receives the session update request sent by the target access and mobility control function entity;
  • Step S504 feeding back to the target access and mobility control function entity a session update response carrying the bearer identity allocation information.
  • the session control plane function entity receives the session update request sent by the target access and mobility control function entity, and feeds back the session update response carrying the bearer identity allocation information to the target access and mobility control function entity. Since the session control plane function entity feeds back the session update response carrying the bearer identity allocation information to the target access and mobility control function entity, the idle state mobility and 4G to 5G in the 5G, 4G to 5G, and 4G to 5G can be solved in the related art. After the mobility event such as connection state switching, how to determine the allocated EBI information, the problem of an effective solution has not been proposed, and there is no special requirement for the MME, so that the traditional network does not need to be upgraded and the compatibility with the traditional network is realized. .
  • a device for determining a bearer identifier is further provided, which is applied to a target access and mobility control function entity, and the device is used to implement the foregoing embodiment and an optional implementation manner.
  • the term "module” may implement a combination of software and/or hardware of a predetermined function.
  • FIG. 6 is a structural block diagram (1) of a device for determining a bearer identifier according to an embodiment of the present disclosure. As shown in FIG. 6, the device includes:
  • the first sending module 601 is configured to send a session update request to the session control plane function entity;
  • the first receiving module 603 is configured to receive a session update response that carries the bearer identifier allocation information fed back by the session control plane function entity.
  • the first sending module 601 sends a session update request to the session control plane function entity, and the first receiving module 603 receives the session update response that carries the bearer identifier allocation information fed back by the session control plane function entity.
  • the first receiving module 603 can receive the session update response that carries the bearer identifier allocation information fed back by the session control plane function entity, and can solve the idle state mobility and the 4G to 5G connection in the 5G, 4G to 5G in the related art.
  • the mobility event such as state switching, how to determine the allocated EBI information, the problem of an effective solution has not been proposed, and there is no special requirement for the MME, so that the traditional network does not need to be upgraded and the compatibility with the traditional network is realized.
  • the bearer identifier allocation information is used to notify the target access and mobility control function entity: the source access and the mobility control function entity or the assigned bearer identifier on the mobility management entity.
  • the session update request carries an indication of requesting bearer identification information.
  • the bearer identifier allocation information includes a bearer identifier list, or the bearer identifier allocation information includes: a bearer identifier list and at least one of the following: a priority corresponding to the bearer identifier and a PDU session identifier.
  • the first receiving module 603 is further configured to receive a registration request sent by the terminal, and further configured to receive a context of the terminal sent by the first network element of the source network;
  • the first sending module 601 is further configured to request a context of the terminal from the first network element of the source network, and is further configured to send a session update request to the session control plane function entity according to the context.
  • the registration request includes: a registration request sent by a terminal that has entered the idle state in the 5G network, or a registration request sent after the terminal entering the idle state connects to the 5G network in the mobile.
  • the first sending module 601 is further configured to initiate a location update process to the unified data management function entity, where the location update process is used by the unified data management function entity to initiate a location deletion process to the target access and mobility control function entity.
  • the first receiving module 603 is further configured to receive a handover preparation response message sent by the target base station.
  • the first receiving module 603 is further configured to receive a handover preparation request sent by the first network element of the source network after receiving the handover request sent by the source base station, where the handover preparation request carries the target base station information and the current session. Information; and also for receiving N2 session information of the PDU session to be switched sent by the session control plane function entity;
  • the first sending module 601 is further configured to send a PDU session switching request to the session control plane function entity according to the handover preparation request, and is further configured to send a handover preparation request to the target base station according to the session information of the PDU session to be switched, where the handover preparation is performed.
  • the handover preparation response message carries the reserved radio resource information, the N2 response information, and the N3 tunnel information allocated for each PDU session that is successfully reserved.
  • the session update request carries the handover preparation response information.
  • the first sending module 601 is further configured to: return a handover response to the first network element of the source network; the handover response is used by the first network element of the source network to send a handover command to the source base station, where the handover command is used by the source from the source base station. Switch to the target base station.
  • the first receiving module 603 is further configured to receive a handover completion notification sent by the target base station.
  • the first network element of the source network includes: a source access and mobility control function entity or a mobility management entity.
  • the session control plane function entity includes: a session control plane function SMF entity or a session control plane function SMF entity and a packet data gateway control entity PGW-C.
  • each of the above modules may be implemented by software or hardware.
  • the foregoing may be implemented by, but not limited to, the foregoing modules are all located in the same processor; or, the above modules are in any combination.
  • the forms are located in different processors.
  • a device for determining a bearer identifier is further provided, which is applied to the session control plane function entity, and the device is used to implement the foregoing embodiment and the optional implementation manner, and details are not described herein.
  • the term "module” may implement a combination of software and/or hardware of a predetermined function.
  • FIG. 7 is a structural block diagram (2) of a device for determining a bearer identifier according to an embodiment of the present disclosure. As shown in FIG. 7, the device includes:
  • the second receiving module 701 is configured to receive a session update request sent by the target access and the mobility control function entity;
  • the second sending module 703 is configured to feed back, to the target access and mobility control function entity, a session update response that carries the bearer identity allocation information.
  • the second receiving module 701 receives the session update request sent by the target access and the mobility control function entity, and the second sending module 703 feeds back the session carrying the bearer identity allocation information to the target access and mobility control function entity. Update the response. Since the sending module 703 can feed back the session update response carrying the bearer identifier allocation information to the target access and mobility control function entity, the idle state mobility of 4G to 5G and 4G to 5G in the 5G can be solved in the related art. After the mobility event such as connection state switching, how to determine the allocated EBI information, the problem of an effective solution has not been proposed, and there is no special requirement for the MME, so that the traditional network does not need to be upgraded and the compatibility with the traditional network is realized.
  • the mobility event such as connection state switching, how to determine the allocated EBI information
  • each of the above modules may be implemented by software or hardware.
  • the foregoing may be implemented by, but not limited to, the foregoing modules are all located in the same processor; or, the above modules are in any combination.
  • the forms are located in different processors.
  • the SMF returns the EBI allocation information to the AMF in the update session request response when the idle state mobility/handover within 5G or the idle state mobility/handover of 4G to 5G;
  • the AMF may request the EBI information from the SMF in the update session request;
  • the UE When the idle state mobility is within 5G, the UE sets the PDU session to which 4G session information is assigned to be active.
  • the UE When the idle state mobility of the 4G to 5G is used, the UE sets the PDU session corresponding to the PDN connection to which the 5G session information is allocated to be active.
  • FIG. 8 is a flowchart (1) of a method for determining a bearer flag according to a preferred embodiment of the present disclosure.
  • the application scenario is a cross-AMF idle state mobility, where the terminal UE has accessed in the 5G system, and the AMF served for it is AMF1. , ie source AMF (sAMF). The UE enters the idle state, and the UE moves, and it moves out of the tracking area of the sAMF.
  • sAMF ie source AMF
  • the UE sends a registration request, and after receiving the request, the 5G base station sends the request to the AMF2, that is, the target AMF (tAMF).
  • the UE sets the PDU session to which the 4G corresponding parameter is assigned to be activated in the registration request.
  • S802 The tAMF requests the context of the UE from the SAMF.
  • S803 sAMF returns the context of the UE to the tAMF;
  • the tAMF initiates a session update request to the SMF according to the UE context, optionally, where the indication that the EBI information is requested is carried;
  • the SMF returns a session update response to the tAMF, where the EBI allocation information is carried;
  • the EBI allocation information includes an EBI list, and may also include information such as a PDU session ID and an EBI priority.
  • steps S806-S807 are performed once;
  • the application scenario is a cross-AMF handover within a 5G system, where the terminal UE has been accessed in the 5G system, and the AMF served as the source thereof AMF (sAMF), UE is in the connected state.
  • sAMF AMF served as the source thereof AMF
  • UE is in the connected state.
  • its current 5G serving base station RAN1 ie, the source base station in the above embodiment finds that the UE moves out of the signal coverage range.
  • the 5G base station RAN1 finds that the UE wants to move out of the coverage range (for example, the RAN1 finds that the signal of the UE is lower than the handover threshold according to the measurement report of the UE), and the RAN1 decides to switch the UE to the target base station RAN2.
  • the 5G base station RAN1 initiates a handover request to the sAMF, where the message carries the destination base station information and the current session information, and the session information includes the PDU session information.
  • the sAMF selects the destination AMF (tAMF) according to the destination base station information, and then initiates a handover preparation request to the tAMF, where the message carries the destination base station information and the current session information, and the current session information includes the SMF address and the PDU session information.
  • tAMF destination AMF
  • S903 The tAMF sends a PDU session switching request to the SMF according to the SMF information.
  • the SMF returns N2 session information of the PDU session to be switched, and includes information such as QoS.
  • the tAMF performs steps S903-S904 based on each PDU session to be switched;
  • the tAMF After receiving the SMF response of all PDU sessions to be switched, the tAMF requests resource reservation from the target base station 5G RAN2 according to the session information.
  • the 5G RAN2 base station reserves radio resources according to the PDU session information, and returns a handover response message, where the reserved radio resource information and the N2 response information are carried, and the response message also has the target base station succeeded for each reserved resource.
  • the PDU session allocates N3 tunnel information.
  • S907 The tAMF sends a session update request message to the SMF, where the N2 handover preparation response and the N3 tunnel information are carried. Optionally, carrying an EBI request indication;
  • S908 The SMF returns a session update request response to the tAMF. Which carries the EBI allocation information on the SMF;
  • the tAMF performs steps S907-S908 based on each PDU session to be switched;
  • the tAMF After waiting for all the SMF responses, the tAMF returns a handover request response to the sAMF, where the message carries the radio resource information reserved by the destination base station for the PDU session;
  • the sAMF determines, if the resource reservation of the PDU session is successful, sends a handover command to the 5G base station 5G RAN1, where the radio resource information reserved by the destination base station for the PDU session is included;
  • the base station 5G RAN1 initiates a handover command to the UE, with radio resource information reserved by the target base station;
  • the terminal accesses the base station 5G RAN2 according to the radio resource information reserved by the target base station;
  • S913 The base station 5G RAN2 initiates a handover notification message to the tAMF.
  • S914 The tAMF sends a session update request message to the SMF, where the handover completion notification is carried. Optionally, carrying an EBI request indication;
  • S915 The SMF returns a session update response to the tAMF, confirming that the handover is completed. Which carries the EBI allocation information on the SMF;
  • the tAMF performs steps S914-S917 based on each PDU session to be switched;
  • S916 The tAMF returns a handover complete message to the sAMF.
  • S917 The sAMF sends an N2 connection release request to the source base station 1.
  • the tAMF may request the EBI information in step S907, or may request the EBI information in step S914. Alternatively, the tAMF may explicitly indicate that the EBI information is requested in the request or not.
  • the EBI allocation information includes the EBI list, and may also include information such as the PDU session ID and the priority of the EBI.
  • the application scenario is 4G to 5G idle state mobility, where the terminal UE has been accessed in the 4G system, and the PDN has been established. Connection and bearer, and the UE and the network have interacted with the PDN connection and bear the corresponding 5G PDU session information. The UE enters an idle state, which is connected to the 5G system during UE mobility.
  • the UE sends a registration request, and after receiving the request, the 5G base station sends the request to the AMF.
  • the UE sets the PDU session to be activated in the registration request.
  • the AMF requests the context of the UE from the MME.
  • S1003 The MME returns the context of the UE to the AMF.
  • the AMF initiates a location update process to the UDM/HSS;
  • the AMF initiates a session update request to the SMF according to the UE context, optionally carrying an indication of requesting EBI information.
  • the SMF returns a session update response to the AMF, where the EBI allocation information is carried; the EBI allocation information includes an EBI list, and may also include information such as a PDU session ID and an EBI priority.
  • steps S1006-S1007 are performed once;
  • S1008 The AMF returns a registration accept message to the UE.
  • the application scenario is a 4G to 5G handover, where the terminal UE has accessed in the 4G system, and the PDN connection and the bearer have been established. The UE and the network have already interacted with the PDN connection and carried the corresponding 5G PDU session information.
  • the current 4G base station 4G RAN serving the UE finds that the UE moves out of the signal coverage.
  • the 4G base station RAN decides to handover the UE to the target 5G base station RAN (for example, when the 4G RAN finds that the UE wants to move out of the coverage according to the measurement report of the UE).
  • the 4G base station 4G RAN initiates a handover request to the MME, where the message carries the destination base station information.
  • the MME selects the destination AMF according to the destination base station information, and then sends a handover preparation request to the AMF, where the message carries the destination base station information and the current 4G session information.
  • the AMF sends a PDU session switching request to the SMF according to the session information, where the session information corresponding to the 4G is carried.
  • the SMF returns N2 session information of the PDU session to be switched, and includes information such as QoS;
  • the AMF performs S1103-S1104 based on each PDU session to be switched;
  • the AMF After receiving the SMF response of all PDU sessions to be switched, the AMF requests resource reservation from the target base station 5G RAN according to the session information.
  • the 5G RAN base station reserves radio resources according to the PDU session information, and returns a handover request response message, with reserved radio resource information, N2 response information, and the message also has the target base station succeeded for each reserved resource. Assigning N3 tunnel information to the PDU session;
  • S1107 The AMF sends a session update request message to the SMF, where the N2 handover preparation response and the N3 tunnel information are carried. Optionally, carrying an EBI request indication;
  • S1108 The SMF returns a session update request response to the AMF.
  • the EBI allocation information on the SMF and the 4G session information required for the handover response are carried.
  • the AMF performs steps S1107-S1108 based on each PDU session to be switched;
  • the AMF After waiting for all SMF responses, the AMF returns a handover request response to the MME, where the message carries radio resource information reserved by the target base station for the PDU session, and handover 4G session information received from all SMFs;
  • the MME determines that if the resource reservation of the PDN connection session is successful, the MME sends a handover command to the 4G eNB, where the radio resource information reserved by the destination base station is received.
  • the 4G RAN initiates a handover command to the UE, with radio resource information reserved by the target base station;
  • S1111 The terminal accesses the base station 5G RAN according to the radio resource information reserved by the target base station;
  • S1112 The base station 5G RAN initiates a handover notification message to the AMF.
  • S1113 The AMF sends a session update request message to the SMF, where the handover completion notification is carried. Optionally, carrying an EBI request indication;
  • S1114 The SMF returns a session update response to the AMF, confirming that the handover is completed. Which carries the EBI allocation information on the SMF;
  • the AMF performs steps S1113-S1114 based on each PDU session to be switched;
  • S1115 The AMF returns a handover complete message to the MME.
  • S1116 The MME sends an S1 connection release request to the source base station 1.
  • the AMF may request EBI information in step S1107, or may request EBI information in step S1113.
  • the AMF may explicitly indicate that the EBI information is requested in the request or not.
  • the EBI allocation information includes the EBI list, and may also include information such as the PDU session ID and the priority of the EBI.
  • steps S806-S807 (session update request, session update response), steps S1006-S1007 (session update request, session update response), and steps S903-S904, S907-S908, S914-S915, steps S1103-S1104, S1107-S1108, S1113-S1114 all adopt the service call function Nsmf_PDUSession_UpdateSMContext, wherein the requested parameter is the input of the service call, and the return response is serviced. The output of the call.
  • the AMF in the step of sending a session update request to the SMF by the AMF (or tAMF) (such as steps S806-S807, S1006-S1007), the AMF (or tAMF) may also send a session generation request to the SMF, SMF.
  • the EBI allocation information is returned to the AMF (or tAMF) in the session generation response, and the session generation request and the session generation response may adopt the serviced calling function Nsmf_PDUSession_CreateSMContext, wherein the requested parameter is the input of the serviced call, and the return response is a serviced call.
  • Nsmf_PDUSession_CreateSMContext wherein the requested parameter is the input of the serviced call, and the return response is a serviced call.
  • This patent may still use the above-mentioned serviced call, or may generate a new service call.
  • the requested parameter is the input of the service call
  • the return response is the output of the service call.
  • Embodiments of the present disclosure also provide a storage medium.
  • the foregoing storage medium may be configured to store program code for performing the following steps:
  • Step S1 sending a session update request to the session control plane function entity
  • Step S2 Receive a session update response that carries the bearer identifier allocation information fed back by the session control plane function entity.
  • the bearer identity allocation information is used to notify the target access and mobility control function entity: the source access and the mobility control function entity or the assigned bearer identity on the mobility management entity.
  • the session update request carries an indication of requesting bearer identification information.
  • the bearer identifier allocation information includes a bearer identifier list, or the bearer identifier allocation information includes: a bearer identifier list and at least one of the following: a priority corresponding to the bearer identifier and a PDU session identifier.
  • the storage medium is further arranged to store program code for performing the following steps:
  • the registration request includes: a registration request sent by a terminal that has entered the idle state in the 5G network, or a registration request sent after the terminal entering the idle state connects to the 5G network in the mobile.
  • the first network element of the source network includes: a source access and mobility control function entity or a mobility management entity.
  • the storage medium is further configured to store program code for performing a step of initiating a location update process for the unified data management function entity to the target access and mobility control function The entity initiates a location deletion process.
  • the storage medium is further arranged to store program code for performing the following steps:
  • the storage medium is further configured to store program code for: transmitting a handover preparation request to the target base station according to session information of the PDU session to be switched, wherein the handover preparation request is for requesting resource reservation;
  • the target base station And receiving, by the target base station, a handover preparation response message, where the handover preparation response message carries reserved radio resource information, N2 response information, and N3 tunnel information allocated for each PDU session that is successfully reserved for each reserved resource;
  • the switch preparation response information is not limited to:
  • the storage medium is further arranged to store program code for performing the step of returning a handover response to the first network element of the source network.
  • the source network first network element includes a source access and mobility control function entity
  • the handover response is used by the source access and mobility control function entity to send a handover command to the source base station, where the handover response carries the target base station
  • the handover command is used for the terminal to handover from the source base station to the target base station.
  • the source network first network element includes a mobility management entity, and the handover response is used by the mobility management entity to send a handover command to the source base station, where the handover command is used by the terminal to switch from the source base station to the target base station.
  • the storage medium is further arranged to store program code for performing the step of receiving a handover completion notification sent by the target base station.
  • the session control plane function entity includes: a session control plane function SMF entity or a session control plane function SMF entity and a packet data gateway control entity PGW-C.
  • the foregoing storage medium may include, but not limited to, a USB flash drive, a Read-Only Memory (ROM), a Random Access Memory (RAM), a mobile hard disk, and a magnetic memory.
  • ROM Read-Only Memory
  • RAM Random Access Memory
  • a mobile hard disk e.g., a hard disk
  • magnetic memory e.g., a hard disk
  • modules or steps of the present disclosure described above can be implemented by a general-purpose computing device that can be centralized on a single computing device or distributed across a network of multiple computing devices. Alternatively, they may be implemented by program code executable by the computing device such that they may be stored in the storage device by the computing device and, in some cases, may be different from the order herein.
  • the steps shown or described are performed, or they are separately fabricated into individual integrated circuit modules, or a plurality of modules or steps thereof are fabricated as a single integrated circuit module. As such, the disclosure is not limited to any specific combination of hardware and software.
  • the present disclosure is applicable to the field of next-generation wireless communication (5G) to solve the related art, how to determine the allocated after the 5G internal, 4G to 5G idle state mobility and 4G to 5G connection state switching and other mobility events.
  • 5G next-generation wireless communication
  • the EBI information has not yet raised an effective solution, and there are no special requirements for the MME, so there is no need to upgrade the traditional network and achieve compatibility with the traditional network.

Landscapes

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

Abstract

本公开提供了一种承载标识确定的方法及装置、存储介质，其中，上述承载标识确定的方法包括：目标接入与移动性控制功能实体向会话控制面功能实体发送会话更新请求，并接收所述会话控制面功能实体反馈的携带了承载标识分配信息的会话更新响应，通过上述技术方案，可以解决相关技术中，在5G内部、4G到5G的空闲态移动性以及4G到5G的连接态切换等移动性事件后，如何确定已分配的EBI信息，尚未提出有效的解决方案的问题。

Description

承载标识的确定方法及装置、存储介质 技术领域
本公开涉及下一代无线通信(5G)领域，具体而言，涉及一种承载标识的确定方法及装置、存储介质。
背景技术
3GPP(3 rd Generation Partnership Project)从R8开始制定第四代(或称长期演进Long Term Evolution，LTE)移动通信系统，图1是相关技术中第四代移动通信系统的网络架构图，其中各网元的功能如下：
终端(User Equipment，UE)，主要通过无线空口接入4G网络并获得服务，终端通过空口和基站交互信息，通过非接入层(non-Access Stratum，NAS)信令和核心网的移动性管理实体交互信息。
基站(Radio Access Network，RAN，或eNB)，负责终端接入网络的空口资源调度和以及空口的连接管理。
移动性管理实体：核心网控制面实体，主要负责对用户的鉴权、授权以及签约检查，和用于用户移动性管理，PDN连接以及承载的维护，用户IDLE状态下触发寻呼等功能。
服务网关(Serving Gateway，S-GW)：核心网用户面功能实体，主要负责漫游情况下和分组数据网关(Packet Data Network Gateway，PDN GW)的交互。
分组数据网关(Packet Data Network Gateway，PDN GW或P-GW)：核心网用户面功能实体，是终端接入PDN网络的接入点，负责分配用户IP地址以及网络触发的承载建立、修改和删除，还具有服务质量(Quality of Service，QoS)控制计费等功能，是用户在3GPP系统内的锚点，从而保证IP地址不变，保证业务连续性。在控制与转发分离架构中，P-GW又分为2个部分，一个是分组数据网关控制实体(PGW-Control，PGW-C)，一个是分组数据网关用户面实体(PGW-User，PGW-U)。PGW-C负责信令控制，PGW-U负责IP转发。
归属签约服务器(Home Subscription Server，HSS)：存储了用户的签约信息。
策略控制与计费规则功能实体(Policy and charging control function，PCRF)，负责策略决策和计费规则的制定。PCRF提供了基于业务数据流的网络控制规则，这些网络控制包括业务数据流的检测、门控(Gating Control)、服务质量控制以及基于数据流的计费规则等。PCRF将其制定的策略和计费规则发送给P-GW执行。
3GPP从R14开始研究下一代通讯系统(NextGen System，5GS)，下一代通讯系统能够支持演进的移动宽带(Evolved Mobile Broadband，eMBB)、超大连接机器通讯(Massive Machine Type Communication，mMTC)、超可靠机器通讯(Ultra Reliable Machine Type Communication，uMTC)三种业务类型，这三种业务类型具有不同的网络特性。图2是相关技术中下一代移动通信网络架构示意图，其中各网元的功能如下：
终端(User Equipment，UE)，主要通过下一代无线空口接入网络并获得服务，终端通过空口和基站交互信息，通过非接入层信令和核心网的公共控制面功能以及会话控制面功能交互信息。
下一代基站(NextGen Radio Access Network，NG RAN)，负责终端接入网络的空口资源调度和以及空口的连接管理。下一代基站可以应用新的无线接入技术(gNB)，也可以应用增强LTE技术(eLTE)。
会话控制面功能实体(Session Management Function，SMF)：用于和终端交互，并主要负责处理用户分组数据单元会话(Packet Data Unit session，PDU session)的建立、修改和删除请求，选择用户面功能(User Plane function，UPF)，建立UE到UPF之间的用户面连接，以及和策略控制功能实体(Policy Control Function，PCF)一起确定会话的QoS参数等功能。UE的每个PDU session都有一个对应的SMF，不同的PDU session可以有不同的SMF。
接入与移动性控制功能实体(Access and Mobility control Function，AMF)：是核心网内的公共控制面功能。一个用户只有一个AMF，其负责对用户鉴权、授权以及签约检查以保证用户是合法用户；用户移动性管理，包括位置注册和临时标识分配；当用户发起PDU连接建立请求的时候，选择合适的SMF；转发UE和SMF之间的非接入层信令；转发基站和SMF之间的接入层(Access Stratum，AS)信令。
用户面功能实体(User Plane Function，UPF)：提供用户面处理功能，包括数据转发、QoS执行。UPF还提供用户移动时候的用户面锚点，保证业务连续性。
策略控制功能实体(Policy Control Function，PCF)：提供资源的授权功能，其和4G网络中的PCRF功能类似。
统一数据管理功能实体(Unified Data Management，UDM，)：存储了用户的签约数据，其和4G时代的HSS非常类似。
下一代通讯系统(NextGen System，5GS)的部署，开始会在热点地区如市中心，商业中心等地区局部部署。当UE接入5G系统中，随着用户的移动，移出了5G系统的覆盖范围，用户UE被切换到4G系统中。
图3是相关技术中4G与5G双向切换的网络架构图，其核心特点是该架构图同时兼容4G和5G架构，以及PGW-C和SMF合一，PGW-U和UPF合一，PCF和PCRF合一，UE的用户面始终锚定在UPF/PGW-U上。在AMF和MME之间，增加N26接口，在该接口上发送跨系统间切换请求。这样UE在LTE和5G之间切换时，能够保证无缝切换。
当4G系统中，UE和网络建立的每个PDN connection，里面包含1个缺省承载(bearer)和多个专用承载。每个承载的信息包含了对应的业务流(Service flows)及其QoS参数，每个承载都有对应的承载标识(EPS Bearer ID，EBI)。在4G系统中，EBI是由MME分配。EBI在UE的所有PDN Connection之间唯一。EBI有4个bit，理论上有16个值，但其中某些值被预留，最多只有11个值可用。
在5G系统中，UE和网络建立PDU session，里面包含1个缺省的服务质量流(Qos flow)和多个专用服务质量流。每个QoS flow包括了对应的业务流(Service flows)，及其QoS参 数，如QoS配置集合(QoS profile)和分组过滤器(packet filter)，每个Qos flow也有对应的标识：Qos Flow ID(QFI)。在每个PDU session内部，QFI是唯一的。
UE在4G和5G系统之间的无缝移动性，包含4G到5G的切换与4G到5G的空闲态移动性，其中UE的IP地址不变。
当UE从5G系统向4G系统无缝移动时，将5G系统建立的PDU session转换为4G系统中的PDN connection。PDU session中的服务质量流，到4G系统后转化为承载。反之亦然。
为了保证上述无缝移动性，在5G系统中为UE建立PDU session的Qos flow时，SMF/PGW-C需要分配该Qos flow对应4G系统的会话参数/承载信息，并发送给UE。在4G系统中建立PDU connection及承载时，PGW-C/SMF也要分配该PDU connection及承载对应的5G PDU session和Qos flow信息，并发给UE。
由于对于一个UE，可能有多个SMF，由SMF分配EBI会导致EBI冲突，也就是两个SMF分配了相同的EBI值。相关技术中，在5G系统为UE建立PDU session，在为Qos flow时分配4G会话参数时，其中EBI的分配是由AMF完成的，其余参数则是由SMF分配。
然而在UE发生移动性时，目标AMF如何知道哪些EBI已经被分配了，其包含以下场景：
场景一：跨AMF的空闲态移动性，UE发送注册请求到目标AMF，AMF如何知道源AMF上，哪些EBI已经被分配了；
场景二：跨AMF的切换，UE需要切换到目标AMF，AMF如何知道源AMF上，哪些EBI已经被分配了；
场景三：4G到5G的空闲态移动性，UE在5G系统发送注册请求到目标AMF，AMF如何知道4G的MME上，哪些EBI已经被分配了；
场景四：4G到5G的连接态切换，UE切换到5G后，目标AMF如何知道源MME上，哪些EBI已经被分配了；
当5G网络和传统4G网络或LTE基站共存时，为了实现4G网络系统和5G网络系统间，以及5G网络系统内部的承载标志的确定，相关技术中将EBI分配情况作为AMF的移动性上下文，由源AMF传递给目标AMF。但是这个方案只能解决场景一和二，无法解决场景三和四。如果改造MME，使MME传递EBI分配信息，则改造MME将会非常复杂。此外，EBI分配信息不仅包含EBI值列表，还有每个EBI值对应的5G会话信息。然而，在4G中，这些5G会话信息都是由PGW-C/SMF分配的，MME无法知晓。
针对相关技术中，在5G内部、4G到5G的空闲态移动性以及4G到5G的连接态切换等移动性事件后，如何确定已分配的EBI信息，尚未提出有效的解决方案。
发明内容
本公开实施例提供了一种承载标识的确定方法及装置、存储介质，以至少解决相关技术中，在5G内部、4G到5G的空闲态移动性以及4G到5G的连接态切换等移动性事件后，如何确定已分配的EBI信息，尚未提出有效的解决方案的问题。
根据本公开的一个实施例，提供了一种承载标识的确定方法，包括：
目标接入与移动性控制功能实体向会话控制面功能实体发送会话更新请求，并接收会话控制面功能实体反馈的携带了承载标识分配信息的会话更新响应。
可选地，承载标识分配信息用于通知目标接入与移动性控制功能实体：源接入与移动性控制功能实体或移动性管理实体上已分配的承载标识。
可选地，会话更新请求中携带了请求承载标识信息的指示。
可选地，承载标识分配信息包括承载标识列表，或承载标识分配信息包括：承载标识列表以及以下信息至少之一：承载标识对应的优先级和PDU会话标识。
可选地，目标接入与移动性控制功能实体向会话控制面功能实体发送会话更新请求，包括：
目标接入与移动性控制功能实体接收终端发送的注册请求；
目标接入与移动性控制功能实体接收到注册请求后，向源网络第一网元请求终端的上下文；
目标接入与移动性控制功能实体接收源网络第一网元发送的终端的上下文，并根据上下文向会话控制面功能实体发送会话更新请求。
可选地，注册请求包括：由已接入5G网络中进入空闲态的终端发送的注册请求或已接入4G网络中进入空闲态的终端在移动到5G网络后发送的注册请求。
可选地，还包括：
目标接入与移动性控制功能实体向统一数据管理功能实体发起位置更新过程，位置更新过程用于统一数据管理功能实体向目标接入与移动性控制功能实体发起位置删除过程。
可选地，目标接入与移动性控制功能实体向会话控制面功能实体发送会话更新请求前，还包括：
目标接入与移动性控制功能实体接收目标基站发送的切换准备响应消息。
可选地，还包括：
目标接入与移动性控制功能实体接收由源网络第一网元在接收到源基站发送的切换请求后发送的切换准备请求，其中，切换准备请求中携带了目标基站信息和当前会话信息；
目标接入与移动性控制功能实体根据切换准备请求，向会话控制面功能实体发送PDU会话切换请求；
目标接入与移动性控制功能实体接收会话控制面功能实体发送的待切换的PDU会话的N2会话信息；
目标接入与移动性控制功能实体根据待切换的PDU会话的会话信息向目标基站发送切换准备请求，其中，切换准备请求用于请求资源预留；
其中，切换准备响应消息中携带了预留无线资源信息、N2响应信息以及为每个预留资源成功的PDU会话分配的N3隧道信息；会话更新请求中携带了切换准备响应信息。
可选地，还包括：目标接入与移动性控制功能实体向源网络第一网元返回切换响应；切换响应用于源网络第一网元向源基站发送切换命令，其中，切换命令用于终端从源基站切换 到目标基站。
可选地，目标接入与移动性控制功能实体向会话控制面功能实体发送会话更新请求前，还包括：目标接入与移动性控制功能实体接收目标基站发送的切换完成通知。
可选地，源网络第一网元包括：源接入与移动性控制功能实体或移动性管理实体。
可选地，会话控制面功能实体包括：会话控制面功能SMF实体或会话控制面功能SMF实体和分组数据网关控制实体PGW-C合一的实体。
根据本公开的一个实施例，提供了一种承载标识确定的方法，包括：
会话控制面功能实体接收目标接入与移动性控制功能实体发送的会话更新请求，并向目标接入与移动性控制功能实体反馈携带了承载标识分配信息的会话更新响应。
根据本公开的一个实施例，提供了一种承载标识确定的装置，应用于目标接入与移动性控制功能实体中，包括：
第一发送模块，设置为向会话控制面功能实体发送会话更新请求；
第一接收模块，设置为接收会话控制面功能实体反馈的携带了承载标识分配信息的会话更新响应。
可选地，其中承载标识分配信息用于通知目标接入与移动性控制功能实体：源接入与移动性控制功能实体或移动性管理实体上已分配的承载标识。
可选地，第一接收模块还设置为接收终端发送的注册请求，以及还设置为接收源网络第一网元发送的终端的上下文；
第一发送模块还设置为向源网络第一网元请求终端的上下文，以及还设置为根据上下文向会话控制面功能实体发送会话更新请求。
可选地，源网络第一网元包括：源接入与移动性控制功能实体或移动性管理实体。
根据本公开的一个实施例，提供了一种承载标识确定的装置，应用于会话控制面功能实体中，包括：
第二接收模块，设置为接收目标接入与移动性控制功能实体发送的会话更新请求；
第二发送模块，设置为向目标接入与移动性控制功能实体反馈携带了承载标识分配信息的会话更新响应。
根据本公开的一个实施例，提供了一种存储介质，存储介质包括存储的程序，其中，程序运行时执行上述任一项承载标识的确定方法。
通过本公开，由于目标接入与移动性控制功能实体接收会话控制面功能实体反馈的携带了承载标识分配信息的会话更新响应，可以解决相关技术中，在5G内部、4G到5G的空闲态移动性以及4G到5G的连接态切换等移动性事件后，如何确定已分配的EBI信息，尚未提出有效的解决方案的问题，并且对MME没有特殊要求，进而不需要对传统网络进行升级以及实现了与传统网络的兼容。
附图说明
此处所说明的附图用来提供对本公开的进一步理解，构成本申请的一部分，本公开的示 意性实施例及其说明用于解释本公开，并不构成对本公开的不当限定。在附图中：
图1是相关技术中第四代移动通信系统的网络架构图；
图2是相关技术中下一代移动通信网络架构示意图；
图3是相关技术中4G与5G双向切换的网络架构图；
图4是根据本公开实施例的承载标识的确定方法的流程图(一)；；
图5是根据本公开实施例的承载标识的确定方法的流程图(二)；
图6是根据本公开实施例的承载标识的确定装置的结构框图(一)；
图7是根据本公开实施例的承载标识的确定装置的结构框图(二)；
图8是根据本公开优选实施例的承载标志的确定方法的流程图(一)；
图9是根据本公开优选实施例的承载标志的确定方法的流程图(二)；
图10是根据本公开优选实施例的承载标志的确定方法的流程图(三)；
图11是根据本公开优选实施例的承载标志的确定方法的流程图(四)。
具体实施方式
下文中将参考附图并结合实施例来详细说明本公开。需要说明的是，在不冲突的情况下，本申请中的实施例及实施例中的特征可以相互组合。
需要说明的是，本公开的说明书和权利要求书及上述附图中的术语“第一”、“第二”等是用于区别类似的对象，而不必用于描述特定的顺序或先后次序。
实施例1
在本实施例中提供了一种承载标识的确定方法，图4是根据本公开实施例的承载标识的确定方法的流程图(一)，如图4所示，该流程包括如下步骤：
步骤S402，目标接入与移动性控制功能实体向会话控制面功能实体发送会话更新请求；
步骤S404，接收会话控制面功能实体反馈的携带了承载标识分配信息的会话更新响应。
通过上述步骤，目标接入与移动性控制功能实体向会话控制面功能实体发送会话更新请求，并接收会话控制面功能实体反馈的携带了承载标识分配信息的会话更新响应。由于目标接入与移动性控制功能实体可以接收会话控制面功能实体反馈的携带了承载标识分配信息的会话更新响应，可以解决相关技术中，在5G内部、4G到5G的空闲态移动性以及4G到5G的连接态切换等移动性事件后，如何确定已分配的EBI信息，尚未提出有效的解决方案的问题，并且对MME没有特殊要求，进而不需要对传统网络进行升级以及实现了与传统网络的兼容。
可选地，承载标识分配信息用于通知目标接入与移动性控制功能实体：源接入与移动性控制功能实体或移动性管理实体上已分配的承载标识。
可选地，会话更新请求中携带了请求承载标识信息的指示。
可选地，承载标识分配信息包括承载标识列表，或承载标识分配信息包括：承载标识列表以及以下信息至少之一：承载标识对应的优先级和PDU会话标识。
可选地，目标接入与移动性控制功能实体向会话控制面功能实体发送会话更新请求，包 括：
目标接入与移动性控制功能实体接收终端发送的注册请求；
目标接入与移动性控制功能实体接收到注册请求后，向源网络第一网元请求终端的上下文；
目标接入与移动性控制功能实体接收源网络第一网元发送的终端的上下文，并根据上下文向会话控制面功能实体发送会话更新请求。
可选地，注册请求包括：由已接入5G网络中进入空闲态的终端发送的注册请求或已接入4G网络中进入空闲态的终端在移动到5G网络后发送的注册请求。
可选地，还包括：
目标接入与移动性控制功能实体向统一数据管理功能实体发起位置更新过程，位置更新过程用于统一数据管理功能实体向目标接入与移动性控制功能实体发起位置删除过程。
可选地，目标接入与移动性控制功能实体向会话控制面功能实体发送会话更新请求前，还包括：
目标接入与移动性控制功能实体接收目标基站发送的切换准备响应消息。
可选地，还包括：
目标接入与移动性控制功能实体接收由源网络第一网元在接收到源基站发送的切换请求后发送的切换准备请求，其中，切换准备请求中携带了目标基站信息和当前会话信息；
目标接入与移动性控制功能实体根据切换准备请求，向会话控制面功能实体发送PDU会话切换请求；
目标接入与移动性控制功能实体接收会话控制面功能实体发送的待切换的PDU会话的N2会话信息；
目标接入与移动性控制功能实体根据待切换的PDU会话的会话信息向目标基站发送切换准备请求，其中，切换准备请求用于请求资源预留；
其中，切换准备响应消息中携带了预留无线资源信息、N2响应信息以及为每个预留资源成功的PDU会话分配的N3隧道信息；会话更新请求中携带了切换准备响应信息。
可选地，还包括：目标接入与移动性控制功能实体向源网络第一网元返回切换响应；切换响应用于源网络第一网元向源基站发送切换命令，其中，切换命令用于终端从源基站切换到目标基站。
可选地，目标接入与移动性控制功能实体向会话控制面功能实体发送会话更新请求前，还包括：目标接入与移动性控制功能实体接收目标基站发送的切换完成通知。
可选地，源网络第一网元包括：源接入与移动性控制功能实体或移动性管理实体。
可选地，会话控制面功能实体包括：会话控制面功能SMF实体或会话控制面功能SMF实体和分组数据网关控制实体PGW-C合一的实体。
通过以上的实施方式的描述，本领域的技术人员可以清楚地了解到根据上述实施例的方法可借助软件加必需的通用硬件平台的方式来实现，当然也可以通过硬件，但很多情况下前者是更佳的实施方式。基于这样的理解，本公开的技术方案本质上或者说对现有技术做出贡 献的部分可以以软件产品的形式体现出来，该计算机软件产品存储在一个存储介质(如ROM/RAM、磁碟、光盘)中，包括若干指令用以使得一台终端设备(可以是手机，计算机，服务器，或者网络设备等)执行本公开各个实施例所描述的方法。
实施例2
在本实施例中提供了一种承载标识的确定方法，图5是根据本公开实施例的承载标识的确定方法的流程图(二)，如图5所示，该流程包括如下步骤：
步骤S502，会话控制面功能实体接收目标接入与移动性控制功能实体发送的会话更新请求；
步骤S504，向目标接入与移动性控制功能实体反馈携带了承载标识分配信息的会话更新响应。
通过上述步骤，会话控制面功能实体接收目标接入与移动性控制功能实体发送的会话更新请求，并向目标接入与移动性控制功能实体反馈携带了承载标识分配信息的会话更新响应。由于会话控制面功能实体向目标接入与移动性控制功能实体反馈携带了承载标识分配信息的会话更新响应，可以解决相关技术中，在5G内部、4G到5G的空闲态移动性以及4G到5G的连接态切换等移动性事件后，如何确定已分配的EBI信息，尚未提出有效的解决方案的问题，并且对MME没有特殊要求，进而不需要对传统网络进行升级以及实现了与传统网络的兼容。
通过以上的实施方式的描述，本领域的技术人员可以清楚地了解到根据上述实施例的方法可借助软件加必需的通用硬件平台的方式来实现，当然也可以通过硬件，但很多情况下前者是更佳的实施方式。基于这样的理解，本公开的技术方案本质上或者说对现有技术做出贡献的部分可以以软件产品的形式体现出来，该计算机软件产品存储在一个存储介质(如ROM/RAM、磁碟、光盘)中，包括若干指令用以使得一台终端设备(可以是手机，计算机，服务器，或者网络设备等)执行本公开各个实施例所描述的方法。
实施例3
在本实施例中还提供了一种承载标识的确定装置，应用于目标接入与移动性控制功能实体中，该装置用于实现上述实施例及可选实施方式，已经进行过说明的不再赘述。如以下所使用的，术语“模块”可以实现预定功能的软件和/或硬件的组合。尽管以下实施例所描述的装置较佳地以软件来实现，但是硬件，或者软件和硬件的组合的实现也是可能并被构想的。
图6是根据本公开实施例的承载标识的确定装置的结构框图(一)，如图6所示，该装置包括：
第一发送模块601，用于向会话控制面功能实体发送会话更新请求；
第一接收模块603，用于接收会话控制面功能实体反馈的携带了承载标识分配信息的会话更新响应。
通过上述实施例，第一发送模块601向会话控制面功能实体发送会话更新请求，第一接收模块603接收会话控制面功能实体反馈的携带了承载标识分配信息的会话更新响应。由于第一接收模块603可以接收会话控制面功能实体反馈的携带了承载标识分配信息的会话更新 响应，可以解决相关技术中，在5G内部、4G到5G的空闲态移动性以及4G到5G的连接态切换等移动性事件后，如何确定已分配的EBI信息，尚未提出有效的解决方案的问题，并且对MME没有特殊要求，进而不需要对传统网络进行升级以及实现了与传统网络的兼容。
可选地，其中承载标识分配信息用于通知目标接入与移动性控制功能实体：源接入与移动性控制功能实体或移动性管理实体上已分配的承载标识。
可选地，会话更新请求中携带了请求承载标识信息的指示。
可选地，承载标识分配信息包括承载标识列表，或承载标识分配信息包括：承载标识列表以及以下信息至少之一：承载标识对应的优先级和PDU会话标识。
可选地，第一接收模块603还用于接收终端发送的注册请求，以及还用于接收源网络第一网元发送的终端的上下文；
第一发送模块601还用于向源网络第一网元请求终端的上下文，以及还用于根据上下文向会话控制面功能实体发送会话更新请求。
可选地，注册请求包括：由已接入5G网络中进入空闲态的终端发送的注册请求或进入空闲态的终端在移动中连接到5G网络后发送的注册请求。
可选地，第一发送模块601还用于向统一数据管理功能实体发起位置更新过程，位置更新过程用于统一数据管理功能实体向目标接入与移动性控制功能实体发起位置删除过程。
可选地，第一接收模块603还用于接收目标基站发送的切换准备响应消息。
可选地，第一接收模块603还用于接收由源网络第一网元在接收到源基站发送的切换请求后发送的切换准备请求，其中，切换准备请求中携带了目标基站信息和当前会话信息；以及还用于接收会话控制面功能实体发送的待切换的PDU会话的N2会话信息；
第一发送模块601还用于根据切换准备请求，向会话控制面功能实体发送PDU会话切换请求；以及还用于根据待切换的PDU会话的会话信息向目标基站发送切换准备请求，其中，切换准备请求用于请求资源预留；
其中，切换准备响应消息中携带了预留无线资源信息、N2响应信息以及为每个预留资源成功的PDU会话分配的N3隧道信息；会话更新请求中携带了切换准备响应信息。
可选地，第一发送模块601还用于向源网络第一网元返回切换响应；切换响应用于源网络第一网元向源基站发送切换命令，其中，切换命令用于终端从源基站切换到目标基站。
可选地，第一接收模块603还用于接收目标基站发送的切换完成通知。
可选地，源网络第一网元包括：源接入与移动性控制功能实体或移动性管理实体。
可选地，会话控制面功能实体包括：会话控制面功能SMF实体或会话控制面功能SMF实体和分组数据网关控制实体PGW-C合一的实体。
需要说明的是，上述各个模块是可以通过软件或硬件来实现的，对于后者，可以通过以下方式实现，但不限于此：上述模块均位于同一处理器中；或者，上述各个模块以任意组合的形式分别位于不同的处理器中。
实施例4
在本实施例中还提供了一种承载标识的确定装置，应用于会话控制面功能实体中，该装 置用于实现上述实施例及可选实施方式，已经进行过说明的不再赘述。如以下所使用的，术语“模块”可以实现预定功能的软件和/或硬件的组合。尽管以下实施例所描述的装置较佳地以软件来实现，但是硬件，或者软件和硬件的组合的实现也是可能并被构想的。
图7是根据本公开实施例的承载标识的确定装置的结构框图(二)，如图7所示，该装置包括：
第二接收模块701，用于接收目标接入与移动性控制功能实体发送的会话更新请求；
第二发送模块703，用于向目标接入与移动性控制功能实体反馈携带了承载标识分配信息的会话更新响应。
通过上述实施例，第二接收模块701接收目标接入与移动性控制功能实体发送的会话更新请求，第二发送模块703向目标接入与移动性控制功能实体反馈携带了承载标识分配信息的会话更新响应。由于发送模块703可以向目标接入与移动性控制功能实体反馈携带了承载标识分配信息的会话更新响应，可以解决相关技术中，在5G内部、4G到5G的空闲态移动性以及4G到5G的连接态切换等移动性事件后，如何确定已分配的EBI信息，尚未提出有效的解决方案的问题，并且对MME没有特殊要求，进而不需要对传统网络进行升级以及实现了与传统网络的兼容。
需要说明的是，上述各个模块是可以通过软件或硬件来实现的，对于后者，可以通过以下方式实现，但不限于此：上述模块均位于同一处理器中；或者，上述各个模块以任意组合的形式分别位于不同的处理器中。
以下结合优选实施例1-5对上述承载标志的确定方法进行说明，但不用于限定本公开实施例的保护范围。
优选实施例1
在5G内部的空闲态移动性/切换或在4G到5G的空闲态移动性/切换时，SMF在更新会话请求应答中，把EBI分配信息返回给AMF；
其中，AMF在更新会话请求中，可以向SMF请求EBI信息；
其中5G内部的空闲态移动性时，UE将分配了4G会话信息的PDU session设为激活(active)。
其中4G到5G的空闲态移动性时，UE将分配了5G会话信息的PDN connection对应的PDU session设为active。
优选实施例2
图8是根据本公开优选实施例的承载标志的确定方法的流程图(一)，应用场景是跨AMF空闲态移动性，其中终端UE已经在5G系统中接入，为其服务的AMF为AMF1，即源AMF(sAMF)。UE进入空闲态，UE在移动中，其移动出sAMF的跟踪区。
步骤如下：
S801：UE发送注册请求，5G基站收到该请求后，发给AMF2，即目标AMF(tAMF)。可选的，UE在注册请求中，将分配了4G对应参数的PDU会话设置为激活；
S802：tAMF向SAMF请求UE的上下文；
S803：sAMF向tAMF返回UE的上下文；
S804：tAMF向UDM发起位置更新过程；
S805：UDM向sAMF发起位置删除过程；
S806：tAMF根据UE上下文，向SMF发起会话更新请求，可选的，其中携带有请求EBI信息的指示；
S807：SMF向tAMF返回会话更新应答，其中携带了EBI分配信息；EBI分配信息包含EBI列表，还可能包含了PDU session ID，EBI对应的优先级等信息。
可选地，当UE有多个PDU session的时候，对应于每个PDU session，步骤S806-S807都要执行一遍；
S808：tAMF向UE返回注册接受消息。
优选实施例3
图9是根据本公开优选实施例的承载标志的确定方法的流程图(二)，应用场景是5G系统内部跨AMF切换，其中终端UE已经在5G系统中接入，为其服务的AMF为源AMF(sAMF)，UE在连接态。UE在移动中，其当前5G服务基站RAN1(即上述实施例中的源基站)发现UE移动出信号覆盖范围。
步骤如下：
S901：5G基站RAN1发现UE要移动出覆盖范围(比如RAN1根据UE的测量报告发现UE的信号低于切换阈值)，RAN1决定将UE切换到目标基站RAN2上。5G基站RAN1向sAMF发起切换请求，其中消息中带有目的基站信息和当前会话信息，会话信息中包括PDU会话信息。
S902：sAMF根据目的基站信息选择目的AMF(tAMF)，然后向tAMF发起切换准备请求，消息中带有目的基站信息和当前会话信息，当前会话信息包括SMF地址，PDU会话信息。
S903：tAMF根据SMF信息，向SMF发送PDU会话切换请求；
S904：SMF返回要切换的PDU会话的N2会话信息，包含QoS等信息。
可选地，当UE有多个PDU session需要切换的时候，tAMF会基于每个要切换的PDU session，执行步骤S903-S904；
S905：tAMF在收到所有要切换的PDU会话的SMF响应后，根据会话的信息向目标基站5G RAN2请求资源预留；
S906：5G RAN2基站根据PDU会话信息，预留无线资源，并返回切换响应消息，其中携带有预留的无线资源信息、N2响应信息，该响应消息还带有目标基站为每个预留资源成功的PDU会话分配N3隧道信息。
S907：tAMF向SMF发送会话更新请求消息，其中携带了N2切换准备响应、N3隧道信息。可选的，其中携带有EBI请求指示；
S908：SMF向tAMF返回会话更新请求响应。其中携带了该SMF上的EBI分配信息；
可选地，当UE有多个PDU session需要切换的时候，tAMF会基于每个要切换的PDU  session，执行步骤S907-S908；
S909：tAMF在等到所有的SMF应答后，向sAMF返回切换请求响应，其中，消息中带有目的基站为PDU会话预留的无线资源信息；
S910：sAMF判断如果有PDU会话的资源预留成功，则向5G基站5G RAN1发送切换命令，其中带有目的基站为这些PDU会话预留的无线资源信息；
S911：基站5G RAN1向UE发起切换命令，带有目标基站预留的无线资源信息；
S912：终端根据目标基站预留的无线资源信息，接入基站5G RAN2；
S913：基站5G RAN2向tAMF发起切换通知消息；
S914：tAMF向SMF发送会话更新请求消息，其中携带了切换完成通知。可选的，其中携带有EBI请求指示；
S915：SMF向tAMF返回会话更新响应，确认切换完成。其中携带了该SMF上的EBI分配信息；
可选地，当UE有多个PDU session切换的时候，tAMF会基于每个要切换的PDU session，执行步骤S914-S917；
S916：tAMF向sAMF返回切换完成消息。
S917：sAMF向源基站1发送N2连接释放请求。
上述步骤中提供了2中可选实施方式，即tAMF可以在步骤S907中请求EBI信息，也可以在步骤S914中请求EBI信息。可选地，tAMF可以在请求中明确指示要求EBI信息，也可以不给出该指示。EBI分配信息包含EBI列表，还可能包含了PDU session ID，EBI对应的优先级等信息。
优选实施例4
图10是根据本公开优选实施例的承载标志的确定方法的流程图(三)，应用场景是4G向5G空闲态移动性，其中，终端UE已经在4G系统中接入，其已经建立了PDN connection以及承载，并且UE和网络已经交互了PDN connection及承载对应的5G PDU session信息。UE进入空闲态，在UE移动中，其连接到5G系统中。
步骤如下：
S1001：UE发送注册请求，5G基站收到该请求后，发给AMF。可选的，UE在注册请求中，将PDU会话设置为激活。
S1002：AMF向MME请求UE的上下文；
S1003：MME向AMF返回UE的上下文；
S1004：AMF向UDM/HSS发起位置更新过程；
S1005：UDM/HSS向MME发起位置删除过程；
S1006：AMF根据UE上下文，向SMF发起会话更新请求，可选地，其中携带有请求EBI信息的指示；
S1007：SMF向AMF返回会话更新应答，其中携带了EBI分配信息；EBI分配信息包含EBI列表，还可能包含了PDU session ID，EBI对应的优先级等信息。
可选地，当UE有多个PDU session的时候，对应于每个PDU session，步骤S1006-S1007都要执行一遍；
S1008：AMF向UE返回注册接受消息。
优选实施例5
图11是根据本公开优选实施例的承载标志的确定方法的流程图(四)，应用场景是4G到5G切换，其中终端UE已经在4G系统中接入，其已经建立了PDN connection以及承载，并且UE和网络已经交互了PDN connection及承载对应的5G PDU session信息。UE在连接态在移动中，为其服务的当前4G基站4G RAN发现UE移动出信号覆盖范围。
步骤如下：
S1101：4G基站RAN决定将UE切换到目标5G基站RAN上(例如当4G RAN根据UE的测量报告发现UE要移动出覆盖范围时)。4G基站4G RAN向MME发起切换请求，其中消息中带有目的基站信息。
S1102：MME根据目的基站信息选择目的AMF，然后向AMF发送切换准备请求，消息中带有目的基站信息和当前4G会话信息。
S1103：AMF根据会话信息，向SMF发送PDU会话切换请求，其中携带了4G对应的会话信息；
S1104：SMF返回要切换的PDU会话的N2会话信息，包含QoS等信息；
可选地，当UE有多个PDU session需要切换的时候，AMF会基于每个要切换的PDU session，执行S1103-S1104；
S1105：AMF在收到所有要切换的PDU会话的SMF响应后，根据会话的信息向目标基站5G RAN请求资源预留；
S1106：5G RAN基站根据PDU会话信息，预留无线资源，并返回切换请求响应消息，带有预留的无线资源信息，N2响应信息，该消息还带有目标基站为每个预留资源成功的PDU会话分配N3隧道信息；
S1107：AMF向SMF发送会话更新请求消息，其中携带了N2切换准备响应，N3隧道信息。可选的，其中携带有EBI请求指示；
S1108：SMF向AMF返回会话更新请求响应。其中携带了该SMF上的EBI分配信息，以及切换应答所需4G会话信息；
可选地，当UE有多个PDU session需要切换的时候，AMF会基于每个要切换的PDU session，执行步骤S1107-S1108；
S1109：AMF在等到所有的SMF应答后，向MME返回切换请求响应，其中，消息中带有目的基站为PDU会话预留的无线资源信息，以及从所有SMF收到的切换4G会话信息；
S1110：MME判断如果有PDN connection会话的资源预留成功，则向4G基站4G RAN发送切换命令，其中带有目的基站预留的无线资源信息。4G RAN向UE发起切换命令，带有目标基站预留的无线资源信息；
S1111：终端根据目标基站预留的无线资源信息，接入基站5G RAN；
S1112：基站5G RAN向AMF发起切换通知消息。
S1113：AMF向SMF发送会话更新请求消息，其中携带了切换完成通知。可选的，其中携带有EBI请求指示；
S1114：SMF向AMF返回会话更新响应，确认切换完成。其中携带了该SMF上的EBI分配信息；
可选地，当UE有多个PDU session切换的时候，AMF会基于每个要切换的PDU session，执行步骤S1113-S1114；
S1115：AMF向MME返回切换完成消息；
S1116：MME向源基站1发送S1连接释放请求。
上述步骤中提供了2种实施方式，即AMF可以在步骤S1107中请求EBI信息，也可以在步骤S1113中请求EBI信息。可选地，AMF可以在请求中明确指示要求EBI信息，也可以不给出该指示。EBI分配信息包含EBI列表，还可能包含了PDU session ID，EBI对应的优先级等信息。
在5G网络中，控制面的交互已经实现了服务化，上述实施例中，步骤S806-S807(会话更新请求，会话更新响应)，步骤S1006-S1007(会话更新请求，会话更新响应)，以及步骤S903-S904，S907-S908,S914-S915，步骤S1103-S1104，S1107-S1108，S1113-S1114均采用了服务化调用函数Nsmf_PDUSession_UpdateSMContext，其中请求的参数就是该服务化调用的输入，返回响应就是服务化调用的输出。
上述各个实施例中，在AMF(或tAMF)向SMF发送会话更新请求的步骤(如步骤S806-S807，S1006-S1007)中，AMF(或tAMF)向SMF发送的也可以是会话生成请求，SMF在会话生成响应中把EBI分配信息返回给AMF(或tAMF)，会话生成请求和会话生成响应可以采用服务化调用函数Nsmf_PDUSession_CreateSMContext，其中请求的参数就是该服务化调用的输入，返回响应就是服务化调用的输出。
本专利可以仍旧沿用上述的服务化调用，也可以生成一个新的服务化调用，其中上述实施方式中，请求的参数就是该服务化调用的输入，返回响应就是该服务化调用的输出。
实施例5
本公开的实施例还提供了一种存储介质。可选地，在本实施例中，上述存储介质可以被设置为存储用于执行以下步骤的程序代码：
步骤S1，向会话控制面功能实体发送会话更新请求；
步骤S2，接收会话控制面功能实体反馈的携带了承载标识分配信息的会话更新响应。
可选地，承载标识分配信息用于通知目标接入与移动性控制功能实体：源接入与移动性控制功能实体或移动性管理实体上已分配的承载标识。
可选地，会话更新请求中携带了请求承载标识信息的指示。
可选地，承载标识分配信息包括承载标识列表，或承载标识分配信息包括：承载标识列表以及以下信息至少之一：承载标识对应的优先级和PDU会话标识。
可选地，存储介质还被设置为存储用于执行以下步骤的程序代码：
接收终端发送的注册请求；
接收到注册请求后，向源网络第一网元请求终端的上下文；
接收源网络第一网元发送的终端的上下文，并根据上下文向会话控制面功能实体发送会话更新请求。
可选地，注册请求包括：由已接入5G网络中进入空闲态的终端发送的注册请求或进入空闲态的终端在移动中连接到5G网络后发送的注册请求。
可选地，源网络第一网元包括：源接入与移动性控制功能实体或移动性管理实体。
可选地，存储介质还被设置为存储用于执行以下步骤的程序代码：向统一数据管理功能实体发起位置更新过程，位置更新过程用于统一数据管理功能实体向目标接入与移动性控制功能实体发起位置删除过程。
可选地，存储介质还被设置为存储用于执行以下步骤的程序代码：
接收由源网络第一网元在接收到源基站发送的切换请求后发送的切换准备请求，其中，切换准备请求中携带了目标基站信息和当前会话信息；
根据切换准备请求，向会话控制面功能实体发送PDU会话切换请求；
接收会话控制面功能实体发送的待切换的PDU会话的N2会话信息。
可选地，存储介质还被设置为存储用于执行以下步骤的程序代码：根据待切换的PDU会话的会话信息向目标基站发送切换准备请求，其中，切换准备请求用于请求资源预留；
接收目标基站发送的切换准备响应消息，其中，切换准备响应消息中携带了预留无线资源信息、N2响应信息以及为每个预留资源成功的PDU会话分配的N3隧道信息；会话更新请求中携带了切换准备响应信息。
可选地，存储介质还被设置为存储用于执行以下步骤的程序代码：向源网络第一网元返回切换响应。
可选地，源网络第一网元包括源接入与移动性控制功能实体，切换响应用于源接入与移动性控制功能实体向源基站发送切换命令，其中，切换响应中携带了目标基站为PDU会话预留的无线资源信息，切换命令用于终端从源基站切换到目标基站。
可选地，源网络第一网元包括移动性管理实体，切换响应用于移动性管理实体向源基站发送切换命令，其中，切换命令用于终端从源基站切换到目标基站。
可选地，存储介质还被设置为存储用于执行以下步骤的程序代码：接收目标基站发送的切换完成通知。
可选地，会话控制面功能实体包括：会话控制面功能SMF实体或会话控制面功能SMF实体和分组数据网关控制实体PGW-C合一的实体。
可选地，在本实施例中，上述存储介质可以包括但不限于：U盘、只读存储器(ROM，Read-Only Memory)、随机存取存储器(RAM，Random Access Memory)、移动硬盘、磁碟或者光盘等各种可以存储程序代码的介质。
可选地，本实施例中的具体示例可以参考上述实施例及可选实施方式中所描述的示例，本实施例在此不再赘述。
显然，本领域的技术人员应该明白，上述的本公开的各模块或各步骤可以用通用的计算装置来实现，它们可以集中在单个的计算装置上，或者分布在多个计算装置所组成的网络上，可选地，它们可以用计算装置可执行的程序代码来实现，从而，可以将它们存储在存储装置中由计算装置来执行，并且在某些情况下，可以以不同于此处的顺序执行所示出或描述的步骤，或者将它们分别制作成各个集成电路模块，或者将它们中的多个模块或步骤制作成单个集成电路模块来实现。这样，本公开不限制于任何特定的硬件和软件结合。
以上仅为本公开的优选实施例而已，并不用于限制本公开，对于本领域的技术人员来说，本公开可以有各种更改和变化。凡在本公开的精神和原则之内，所作的任何修改、等同替换、改进等，均应包含在本公开的保护范围之内。
工业实用性
本公开适用于下一代无线通信(5G)领域，用以解决相关技术中，在5G内部、4G到5G的空闲态移动性以及4G到5G的连接态切换等移动性事件后，如何确定已分配的EBI信息，尚未提出有效的解决方案的问题，并且对MME没有特殊要求，进而不需要对传统网络进行升级以及实现了与传统网络的兼容。

Claims (20)

  1. 一种承载标识的确定方法，包括：
    目标接入与移动性控制功能实体向会话控制面功能实体发送会话更新请求或会话生成请求，并接收所述会话控制面功能实体反馈的携带了承载标识分配信息的会话更新响应或会话生成响应。
  2. 根据权利要求1所述的方法，其中，所述承载标识分配信息用于通知所述目标接入与移动性控制功能实体：源接入与移动性控制功能实体或移动性管理实体上已分配的承载标识。
  3. 根据权利要求1所述的方法，其中，所述会话更新请求或会话生成请求中携带了请求承载标识信息的指示。
  4. 根据权利要求1所述的方法，其中，所述承载标识分配信息包括承载标识列表，或所述承载标识分配信息包括：承载标识列表以及以下信息至少之一：承载标识对应的优先级和PDU会话标识。
  5. 根据权利要求1所述的方法，其中，所述目标接入与移动性控制功能实体向会话控制面功能实体发送会话更新请求或会话生成请求，包括：
    所述目标接入与移动性控制功能实体接收终端发送的注册请求；
    所述目标接入与移动性控制功能实体接收到所述注册请求后，向源网络第一网元请求所述终端的上下文；
    所述目标接入与移动性控制功能实体接收所述源网络第一网元发送的所述终端的上下文，并根据所述上下文向所述会话控制面功能实体发送所述会话更新请求或会话生成请求。
  6. 根据权利要求5所述的方法，其中，所述注册请求包括：由已接入5G网络中进入空闲态的所述终端发送的注册请求或已接入4G网络中进入空闲态的所述终端在移动到5G网络后发送的注册请求。
  7. 根据权利要求5所述的方法，其中，所述方法还包括：
    所述目标接入与移动性控制功能实体向统一数据管理功能实体发起位置更新过程，所述位置更新过程用于所述统一数据管理功能实体向所述目标接入与移动性控制功能实体发起位置删除过程。
  8. 根据权利要求1所述的方法，其中，所述目标接入与移动性控制功能实体向会话控制面功能实体发送会话更新请求或会话生成请求前，所述方法还包括：
    所述目标接入与移动性控制功能实体接收目标基站发送的切换准备响应消息。
  9. 根据权利要求8所述的方法，其中，所述方法还包括：
    所述目标接入与移动性控制功能实体接收由源网络第一网元在接收到源基站发送的切换请求后发送的切换准备请求，其中，所述切换准备请求中携带了目标基站信息和当前会话信息；
    所述目标接入与移动性控制功能实体根据所述切换准备请求，向所述会话控制面功能实体发送PDU会话切换请求；
    所述目标接入与移动性控制功能实体接收所述会话控制面功能实体发送的待切换的PDU会话的N2会话信息；
    所述目标接入与移动性控制功能实体根据所述待切换的PDU会话的会话信息向所述目标基站发送切换准备请求，其中，所述切换准备请求用于请求资源预留；
    其中，所述切换准备响应消息中携带了预留无线资源信息、N2响应信息以及为每个预留资源成功的PDU会话分配的N3隧道信息；所述会话更新请求或会话生成请求中携带了所述切换准备响应信息。
  10. 根据权利要求8所述的方法，其中，所述方法还包括：所述目标接入与移动性控制功能实体向源网络第一网元返回切换响应；所述切换响应用于所述源网络第一网元向源基站发送切换命令，其中，所述切换命令用于终端从所述源基站切换到所述目标基站。
  11. 根据权利要求1所述的方法，其中，所述目标接入与移动性控制功能实体向会话控制面功能实体发送会话更新请求或会话生成请求前，所述方法还包括：所述目标接入与移动性控制功能实体接收目标基站发送的切换完成通知。
  12. 根据权利要求5、8、10中任一项所述的方法，其中，所述源网络第一网元包括：源接入与移动性控制功能实体或移动性管理实体。
  13. 根据权利要求1-11中任一项所述的方法，其中，所述会话控制面功能实体包括：会话控制面功能SMF实体或会话控制面功能SMF实体和分组数据网关控制实体PGW-C合一的实体。
  14. 一种承载标识的确定方法，包括：
    会话控制面功能实体接收目标接入与移动性控制功能实体发送的会话更新请求或会话生成请求，并向所述目标接入与移动性控制功能实体反馈携带了承载标识分配信息的会话更新响应或会话生成响应。
  15. 一种承载标识的确定装置，应用于目标接入与移动性控制功能实体中，包括：
    第一发送模块，设置为向会话控制面功能实体发送会话更新请求或会话生成请求；
    第一接收模块，设置为接收所述会话控制面功能实体反馈的携带了承载标识分配信息的会话更新响应或会话生成响应。
  16. 根据权利要求15所述的装置，其中，其中所述承载标识分配信息用于通知所述目标接入与移动性控制功能实体：源接入与移动性控制功能实体或移动性管理实体上已分配的承载标识。
  17. 根据权利要求15所述的装置，其中：
    所述第一接收模块还设置为接收终端发送的注册请求，以及还用于接收源网络第一网元发送的所述终端的上下文；
    所述第一发送模块还设置为向所述源网络第一网元请求所述终端的上下文，以及还用 于根据所述上下文向所述会话控制面功能实体发送所述会话更新请求或会话生成请求。
  18. 根据权利要求17所述的装置，其中，所述源网络第一网元包括：源接入与移动性控制功能实体或移动性管理实体。
  19. 一种承载标识的确定装置，应用于会话控制面功能实体中，包括：
    第二接收模块，设置为接收目标接入与移动性控制功能实体发送的会话更新请求或会话生成请求；
    第二发送模块，设置为向所述目标接入与移动性控制功能实体反馈携带了承载标识分配信息的会话更新响应或会话生成响应。
  20. 一种存储介质，其中，所述存储介质包括存储的程序，其中，所述程序运行时执行权利要求1至13，或权利要求14中任一项所述的方法。
PCT/CN2018/099997 2017-11-21 2018-08-10 承载标识的确定方法及装置、存储介质 WO2019100762A1 (zh)

Priority Applications (7)

Application Number Priority Date Filing Date Title
JP2020527958A JP7307060B2 (ja) 2017-11-21 2018-08-10 ベアラ識別子を決定する方法及び装置、並びに記憶媒体
ES18880243T ES2959775T3 (es) 2017-11-21 2018-08-10 Métodos y dispositivos para la determinación de identificador de portador y medio de almacenamiento correspondiente
KR1020207017828A KR102349656B1 (ko) 2017-11-21 2018-08-10 베어러 식별자를 결정하기 위한 방법 및 디바이스, 및 그를 위한 저장 매체
EP18880243.3A EP3585100B1 (en) 2017-11-21 2018-08-10 Methods and devices for bearer identifier determination and corresponding storage medium
SG11202004699VA SG11202004699VA (en) 2017-11-21 2018-08-10 Method and device for determining a bearer identifier, and storage medium therefor
EP23187540.2A EP4284083A3 (en) 2017-11-21 2018-08-10 Methods and devices for bearer identifier determination and corresponding storage medium
US16/556,210 US10986543B2 (en) 2017-11-21 2019-08-29 Method and device for determining a bearer identifier, and storage medium therefor

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201711178240.0 2017-11-21
CN201711178240.0A CN109819486B (zh) 2017-11-21 2017-11-21 承载标识的确定方法及装置、存储介质

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US16/556,210 Continuation US10986543B2 (en) 2017-11-21 2019-08-29 Method and device for determining a bearer identifier, and storage medium therefor

Publications (1)

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

Family

ID=66600142

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2018/099997 WO2019100762A1 (zh) 2017-11-21 2018-08-10 承载标识的确定方法及装置、存储介质

Country Status (8)

Country Link
US (1) US10986543B2 (zh)
EP (2) EP3585100B1 (zh)
JP (1) JP7307060B2 (zh)
KR (1) KR102349656B1 (zh)
CN (1) CN109819486B (zh)
ES (1) ES2959775T3 (zh)
SG (1) SG11202004699VA (zh)
WO (1) WO2019100762A1 (zh)

Families Citing this family (10)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN110461013A (zh) * 2018-05-08 2019-11-15 华为技术有限公司 一种网元选择方法及装置
CN113993143A (zh) * 2018-05-22 2022-01-28 华为技术有限公司 会话管理方法、装置和系统
WO2020204269A1 (ko) * 2019-03-29 2020-10-08 삼성전자 주식회사 엣지 컴퓨팅 서비스를 위한 방법 및 그의 전자 장치
US11452020B2 (en) * 2019-07-22 2022-09-20 Cisco Technology, Inc. Maintaining internet protocol address for network traffic during handover procedure
CN114208277B (zh) * 2019-08-08 2024-01-12 瑞典爱立信有限公司 用于5gs互通处理的方法和装置
CN112583619A (zh) * 2019-09-30 2021-03-30 中国移动通信有限公司研究院 一种服务调用方法及网络设备
WO2021093086A1 (en) * 2019-12-19 2021-05-20 Zte Corporation Communication method for requesting packet data network connection information
US11140574B1 (en) * 2020-03-18 2021-10-05 Sprint Spectrum L.P. Dynamic PDCP duplication with bearer modification, to help overcome reduced wireless quality
US11843978B2 (en) 2021-07-16 2023-12-12 Cisco Technology, Inc. Systems and methods to optimize non-3GPP untrusted Wi-Fi to new radio evolved packet system fallback handover
CN113573375B (zh) * 2021-07-23 2022-08-02 中国电信股份有限公司 融合网关的选择方法及装置、存储介质、电子设备

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20150065132A1 (en) * 2013-08-29 2015-03-05 Samsung Electronics Co., Ltd. Method and system for optimizing power consumption in multi-sim mobile device
WO2016122589A1 (en) * 2015-01-30 2016-08-04 Nokia Solutions And Networks Oy Improvements in handovers between different access networks
WO2016195735A1 (en) * 2015-05-29 2016-12-08 Yujian Zhang Seamless mobility for 5g and lte systems and devices
CN107018542A (zh) * 2017-03-27 2017-08-04 中兴通讯股份有限公司 网络系统中状态信息的处理方法、装置及存储介质

Family Cites Families (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2010086014A1 (en) * 2009-01-27 2010-08-05 Nokia Siemens Networks Oy Method and device for data processing in an access point supporting local breakout
CN102264054B (zh) * 2010-05-28 2014-03-12 中兴通讯股份有限公司 资源管理方法和系统
CN103491511B (zh) * 2013-09-22 2017-07-04 大唐移动通信设备有限公司 一种信息发送方法及装置
US9521679B2 (en) * 2014-03-06 2016-12-13 Cisco Technology, Inc. Systems and methods for implementing reflective EPS bearers to ensure uplink quality of service
EP4114065B1 (en) * 2017-01-09 2024-06-12 LG Electronics, Inc. Method for interworking between networks in wireless communication system and apparatus therefor
WO2019077011A1 (en) * 2017-10-17 2019-04-25 Telefonaktiebolaget Lm Ericsson (Publ) PDN AND PDU SESSION TYPE MAPPING, AND DISCOVERING CAPACITY

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20150065132A1 (en) * 2013-08-29 2015-03-05 Samsung Electronics Co., Ltd. Method and system for optimizing power consumption in multi-sim mobile device
WO2016122589A1 (en) * 2015-01-30 2016-08-04 Nokia Solutions And Networks Oy Improvements in handovers between different access networks
WO2016195735A1 (en) * 2015-05-29 2016-12-08 Yujian Zhang Seamless mobility for 5g and lte systems and devices
CN107018542A (zh) * 2017-03-27 2017-08-04 中兴通讯股份有限公司 网络系统中状态信息的处理方法、装置及存储介质

Non-Patent Citations (3)

* Cited by examiner, † Cited by third party
Title
ZTE: "23.502 P-CR Discussion and proposal on EBI management, exhaustion and", 3GPP SA WG2 MEETING #123 S 2-177112, 27 October 2017 (2017-10-27), XP051347068 *
ZTE: "TS 23.502 pCR on the EBI transfer after Idle or connected mode mobili- ty", 3GPP SA WG2 MEETING #124 S 2-178750, 1 December 2017 (2017-12-01), XP051379756 *
ZTE: "TS 23.502 pCR on the EBI transfer after Idle or connected mode mobili- ty", 3GPP SA WG2 MEETING #124 S 2-178964, 1 December 2017 (2017-12-01), XP051365588 *

Also Published As

Publication number Publication date
US20190394684A1 (en) 2019-12-26
SG11202004699VA (en) 2020-06-29
CN109819486B (zh) 2022-04-08
KR102349656B1 (ko) 2022-01-11
US10986543B2 (en) 2021-04-20
JP2021503857A (ja) 2021-02-12
EP4284083A2 (en) 2023-11-29
EP4284083A3 (en) 2024-02-28
ES2959775T3 (es) 2024-02-28
EP3585100A4 (en) 2020-06-17
KR20200088874A (ko) 2020-07-23
EP3585100B1 (en) 2023-09-06
JP7307060B2 (ja) 2023-07-11
EP3585100A1 (en) 2019-12-25
CN109819486A (zh) 2019-05-28

Similar Documents

Publication Publication Date Title
WO2019100762A1 (zh) 承载标识的确定方法及装置、存储介质
EP3764671B1 (en) Communication method and apparatus
WO2018177277A1 (zh) 网络系统中状态信息的处理方法、装置及存储介质
WO2018145671A1 (zh) 跨系统的切换方法和装置、计算机存储介质
CN110167082B (zh) 网络的切换方法、装置及系统，切换确定方法及装置
US20190373520A1 (en) Method and apparatus for complementary and equivalent network slice deployment in a network environment
CN109548093B (zh) 网络切换的方法、装置及系统
CN102387557B (zh) 反向单一无线语音呼叫连续性的处理方法、设备及系统
CN116406002A (zh) 通过无线网络进行无线设备寻呼
WO2019174505A1 (zh) 一种基于网络切片的通信方法及装置
CN109151929B (zh) 网络系统的切换处理方法、装置及系统、存储介质
CN109429370B (zh) 一种信息处理方法及装置
US11297542B2 (en) Base station handover method, system, and computer storage medium
JP2022511597A (ja) ネットワークサービス制御方法及び通信機器
EP3297333A1 (en) Access method and corresponding access node, terminal and communication network
WO2018059401A1 (zh) 网络切换方法、装置及系统，网络接入方法及装置
WO2017167153A1 (zh) 移动通讯系统及寻呼方法
CN113873443B (zh) 通信方法及装置
WO2018010583A1 (zh) 网络系统
WO2016192381A1 (zh) 承载创建、基站切换处理方法及装置
WO2019029228A1 (zh) 语音业务的处理方法及装置、存储介质
CN113973076B (zh) 一种多播切换方法及装置
CN108260097B (zh) 解决eSRVCC切换时误产生漫游计费的方法及eMSC
CN107277866B (zh) 一种数据业务切换方法、装置、基站和系统
KR20210017993A (ko) 무선통신 시스템에서 음성 서비스 품질을 높이는 방법 및 장치

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

Country of ref document: EP

Kind code of ref document: A1

ENP Entry into the national phase

Ref document number: 2018880243

Country of ref document: EP

Effective date: 20190920

ENP Entry into the national phase

Ref document number: 2020527958

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

Country of ref document: KR

Kind code of ref document: A