EP4211932A1 - Procédé et mme permettant de prendre en charge la mobilité d'un équipement utilisateur - Google Patents

Procédé et mme permettant de prendre en charge la mobilité d'un équipement utilisateur

Info

Publication number
EP4211932A1
EP4211932A1 EP20768561.1A EP20768561A EP4211932A1 EP 4211932 A1 EP4211932 A1 EP 4211932A1 EP 20768561 A EP20768561 A EP 20768561A EP 4211932 A1 EP4211932 A1 EP 4211932A1
Authority
EP
European Patent Office
Prior art keywords
mme
communication network
move
eps
network
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Withdrawn
Application number
EP20768561.1A
Other languages
German (de)
English (en)
Inventor
Ann-Christine Sander
Lasse Olsson
Rikard Eriksson
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Telefonaktiebolaget LM Ericsson AB
Original Assignee
Telefonaktiebolaget LM Ericsson AB
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 Telefonaktiebolaget LM Ericsson AB filed Critical Telefonaktiebolaget LM Ericsson AB
Publication of EP4211932A1 publication Critical patent/EP4211932A1/fr
Withdrawn legal-status Critical Current

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/0005—Control or signalling for completing the hand-off
    • H04W36/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/0005—Control or signalling for completing the hand-off
    • H04W36/0055—Transmission or use of information for re-establishing the radio link
    • H04W36/0066—Transmission or use of information for re-establishing the radio link of control information between different types of networks in order to establish a new radio link in the target network

Definitions

  • the present disclosure relates generally to a Mobility Management Entity (MME) and a method performed by the MME.
  • MME Mobility Management Entity
  • UE User Equipment
  • UE on the market today support one or more different communication technologies such as for example one or more of Second Generation (2G), Third Generation (3G), Evolved Packet System (EPS) and Fifth Generation System (5GS).
  • 2G Second Generation
  • 3G Third Generation
  • EPS Evolved Packet System
  • 5GS Fifth Generation System
  • a UE may change from being connected to 3G to being connected to EPS etc.
  • Fig. 1 is a schematic block diagram illustrates that a 5G UE 101 may move a Next- Generation Radio Access Network (NG-RAN) 103 to an Evolved-Universal Terrestrial Radio Access Network (E-UTRAN) 105 and further to GSM EDGE Radio Access Network (GERAN) or Universal Terrestrial Radio Access Network (UTRAN) 108.
  • GSM is short for Global system for mobile communication and EDGE is short for Enhanced Data rates for GSM Evolution.
  • GERAN/UTRAN may be used herein when referring to any of the GERAN or UTRAN.
  • NG-RAN 103 is the access network of the 5GS and the reference number 103 may be used herein when referring to any of the NG-RAN and the 5GS.
  • E-UTRAN 105 is the access network of the EPS, and the reference number 105 may be used herein when referring to any of the E-UTRAN and the EPS.
  • GERAN is the access network of the 2G system and LITRAN is the access network of the 3G system.
  • the reference number 108 may be used herein when referring to any of the GERAN, 2G system, LITRAN and the 3G system.
  • the EPS may be referred to as a 4G system
  • the UE 101 may also be referred to simply as a device.
  • the UE 101 may be a wireless communication device which may also be known as e.g., a wireless device, a mobile terminal, wireless terminal and/or mobile station, a mobile telephone, cellular telephone, or laptop with wireless capability, just to mention some examples.
  • the UE 101 may be a device by which a subscriber may access services offered by an operator’s network and services outside operator’s network to which the operator’s radio access network and core network provide access, e.g. access to the Internet.
  • the UE 101 may be any device, mobile or stationary, enabled to communicate over a radio channel in the communications network, for instance but not limited to e.g.
  • M2M Machine to Machine
  • LoT Internet of Things
  • terminal device communication device or any type of consumer electronic, for instance but not limited to television, radio, lighting arrangements, tablet computer, laptop or Personal Computer (PC).
  • PC Personal Computer
  • the UE 105 may be portable, pocket storable, hand held, computer comprised, or vehicle mounted devices, enabled to communicate voice and/or data, via the radio access network, with another entity, such as another UE, a server, a laptop, a Personal Digital Assistant (PDA), or a tablet, Machine-to-Machine (M2M) device, device equipped with a wireless interface, such as a printer or a file storage device, modem, or any other radio network unit capable of communicating over a radio link in a communications system.
  • PDA Personal Digital Assistant
  • M2M Machine-to-Machine
  • the term UE 101 will be used herein for the sake of simplicity when referring to the 5G UE 101.
  • a 5G UE 101 may be described as a UE supporting 5G or being adapted to be connected to a 5G network.
  • Fig. 1 shows an Access and Mobility Management Function (AMF) 110 and a Mobility Management Entity (MME) 113 adapted to be connected to each other, and the MME 113 and a Serving Gateway (SGW) 115 are adapted to be connected to each other.
  • a SMF+PGW-C 118 is adapted to be connected to the SGW 115 and the AMF 110.
  • the AMF 110 may be an AMF node or a node implementing AMF.
  • the MME 113 may be a mobility node or an MME node.
  • the SMF+PGW-C 118 may be a node implementing SMF+PGW-C or a SMF+PGW-C node.
  • SMF+PGW-C is short for Session Management Function plus Packet Data Network Gateway-Control plane function.
  • the SMF+PGW-C may be a node implementing SMF+PGW-C or a SMF+PGW-C node.
  • Fig. 1 further shows a Packet Data Network Gateway (PGW) 119 and a Serving GPRS Support Node (SGSN) 120 adapted to be connected to each other, e.g. via a Gn/Gp interface, or via a Serving Gateway (SGW) using a S4 interface or any other suitable interface between the PGW 119 and the SGSN 120.
  • the SGSN 120 is adapted to be connected to the MME 113.
  • a Policy Charging Function (PCF) 121 is adapted to be connected to the SMF+PGW-C 118, and a Policy and Charging Rules Function (PCRF) 122 is adapted to be connected to the PGW 119.
  • PCF Policy Charging Function
  • PCRF Policy and Charging Rules Function
  • a UDM/HSS/HLR 125 is adapted to be connected to the SGSN 120, the AMF 110 and the MME 113.
  • UDM is short for Unified Data Management
  • HSS is short for Home subscriber server
  • HLR is short for Home Location Register.
  • the term UDM/HSS/HLR indicates UDM or HSS or HLR.
  • the UDM/HSS/HLR 125 is adapted to be connected to the MME 113.
  • the UDM, HSS and HLR are shown as examples, and any other suitable authentication server may be present in the architecture in fig. 1.
  • the SMF+PGW-C 118 is adapted to be connected to a UPF+PGW-U 128.
  • the abbreviation UPF+PGW-U is short for User Plane Function plus Packet Data Network Gateway-User plane function.
  • the UPF+PGW-U may be a node implementing UPF+PGW-U or a UPF+PGW-U node.
  • Fig. 1 shows that the UPF+PGW-U 125 is adapted to be connected to the E-UTRAN 105 and the SGW 115.
  • the E-UTRAN 105 is adapted to be connected to the SGW 115
  • the GERAN/UTRAN 108 is adapted to be connected to the SGSN 120
  • the NG-RAN 103 is adapted to be connected to the AMF 110 and the UPF+PGW-U 128.
  • the communication links in the communications network in fig. 1 may be of any suitable kind comprising either a wired or wireless link.
  • the link may use any suitable protocol depending on type and level of layer, e.g. as indicated by the Open Systems Interconnection (OSI) model, as understood by the person skilled in the art.
  • OSI Open Systems Interconnection
  • the UE 101 may move from NG-RAN 103 to E-UTRAN 105 with Internet Protocol (IP) session continuity and IP address preservation, since both the AMF 110 and the SGW 115 can communicate with the SMF+PGW-C 118.
  • IP Internet Protocol
  • the MME 113 indirectly communicates with the SMF+PGW-C 118 via the SGW 115.
  • the SGSN 120 will get an UE context from the MME 113, and will send an Update Packet Data Protocol (PDP) Context Request message to the SMF+PGW-C 118, using the IP address of the PGW-C part that it got from the MME 113. How the SMF+PGW-C 118 should behave is not currently defined in the 3GPP specification.
  • PDP Packet Data Protocol
  • the issues are that if a 5G capable UE 101 has a Packet Data Unit (PDU) session to an SMF+PGW-C 118, which do not have any Gn/Gp support for 2G/3G 108 according to 3GPP, and if the UE 101 moves to 2G/3G 108, the target SGSN 120 will try to setup a PDP Context towards the SMF+PGW-C 118 which it believes is a PGW 119 with Gn/Gp and GPRS Tunnelling Protocol version 1 (GTPvl) support.
  • GTPvl GPRS Tunnelling Protocol version 1
  • the PDU session is the 5GS equivalent to the Packet Data Network (PDN) connection in EPS 105 and equivalent to the Packet Data Protocol (PDP) context in 2G/3G 108.
  • PDN Packet Data Network
  • PDP Packet Data Protocol
  • the GTP message from the MME 113 to the SGSN 120 may be a SGSN Context Response, if Idle Mode mobility by Routing Area Update is used. Alternatively, if connected mode mobility is used, the message may be a Forward Relocation Request sent from the MME 113 to SGSN 120.
  • the GTP message e.g. a GTPvl message
  • the PDP Context i.e. the MME 113 behaves as an SGSN 120.
  • the IP address of the PGW-part of the SMF+PGW-C 118 is forwarded to the SGSN 120 inside the PDP Context record constructed by the MME 113, and the SGSN 120 will try to update the PDP Context towards this IP address. Since this setup will fail in some way, since it is not currently described in 3GPP, it might be that the SMF+PGW-C will silently discard any GTPvl message, or it will have some other behaviour and in worst case crash.
  • the PDU session will remain as a ghost PDU session on the SMF+PGW-C 118, and also in the PCF 121 if a PCF 121 is used.
  • the ghost PDU session may also be referred to as a hanging PDU session.
  • the issues with the hanging sessions in SMF+PGW-C 118 and in the PCF 121 , and GTPvl message will now be described in more detail.
  • the PCT 121 may be a node implementing PCF or a PCF node.
  • the UE 101 will in most cases have two PDU Sessions, one for Mobile Broadband (MBB) and one for the IP Multimedia Subsystem (IMS), where one or two SMF+PGW-C 118 as well as PCFs 121 are used.
  • MBB Mobile Broadband
  • IMS IP Multimedia Subsystem
  • the UE 101 will probably try to set up the PDP Context to the MBB Access Point Name (APN), which will be handled by a legacy PGW 119 and optionally a legacy PCRF 122. Both the PCF 121 and PCRF 122 may use the same Unified Data Repository
  • UE 101 returns to E-UTRAN 105 or NG-RAN 103 and uses the same SMF+PGW-C 118 and/or PCF 121.
  • the MBB APN will probably be set up in the legacy PGW 119, optionally using a legacy PCRF 122.
  • SMF+PGW-C 118 uses the IP address of the PGW-C part that it got from the MME 113.
  • One option may be that the SMF+PGW-C 118 answers with a GTPvl Update PDP Context Response message with the cause code "Non-existent”. This may cause the SGSN 120 to delete the PDP Context and to not try further.
  • a second option may be that the SMF+PGW-C 118 answers with a GTP Version Not Supported message. If a receiving node receives a GTP-C message of an unsupported version, that node shall return a GTP Version Not Supported message indicating in the Version field of the GTP header the latest GTP version that that node supports. The received GTP-PDU shall then be discarded. With this, there a risk that the SGSN 120 will fallback, discard the PDP context and try GTPvO in this case.
  • a third option may be that the SMF+PGW-C 118 silently discards the Update PDP Context Request message.
  • This SGSN 120 will re-send the message according to the T3 timer, the default in the SGSN 120 is 3 (seconds). Then it may consider it a path failure and act accordingly. The PDP Context is discarded. The risk might be if the SGSN 120 will set counters, alarms or KPIs indicating that GGSNs are down. One disadvantage is additional signalling due to the re-sendings.
  • a path counter shall be reset each time a response is received on the path and incremented when the T3-RESPONSE timer expires for any message sent on the path.
  • the path shall be considered to be down if the counter exceeds N3-REQUESTS.
  • the GPRS Support Node (GSN) or the Radio Network Controller (RNC) may notify the Operation and Maintenance (O&M) network element.
  • GTP shall also notify the upper layer of the path failure, so that PDP contexts associated with this path may be deleted.
  • An objective of embodiments herein is therefore to obviate at least one of the above disadvantages and to provide improved handling of mobility of the UE.
  • the object is achieved by a method performed by a MME for handling mobility of a UE.
  • the MME detects that a move of the UE from a 5GS to an EPS has been initiated.
  • the MME obtains UE related data from an AMF.
  • the UE related data does not comprise a parameter. Since the UE related data does not comprise the parameter, the MME indicates that a PDN connection of the UE in the EPS as originating from the 5GS.
  • the MME detects that a move of the UE from the EPS to a 2G communication network or a 3G communication network has been initiated.
  • the MME removes the PDN connection indicated as originating from the 5GS.
  • the object is achieved by a MME) adapted for handling mobility of a UE.
  • the MME is adapted to detect that a move of the UE from a 5GS to an EPS has been initiated.
  • the MME is adapted to, when the initiated move to the EPS is detected, obtain UE related data from an AMF.
  • the UE related data does not comprise a parameter.
  • the MME is adapted to, since the UE related data does not comprise the parameter, indicate that a PDN connection of the UE in the EPS as originating from the 5GS.
  • the MME is adapted to, when the move to the EPS is completed, detect that a move of the UE from the EPS to a 2G communication network or a 3G communication network has been initiated.
  • the MME is adapted to, when the initiated move to the 2G communication network or the 3G communication network has been detected, remove the PDN connection indicated as originating from the 5GS.
  • the UE related data does not comprise the parameter, it indicates that the PDN connection originates from the 5GS and is therefore removed when the UE moves further to the 2G communication network or the 3G communication network. Thus, the mobility of the UE is improved.
  • An advantage of the present disclosure is that removing the PDU session marked as coming from the 5GC avoids hanging sessions in the SMF+PGW-C, as well as in the PCF for a 5G UE with a PDN connection in EPS where the UE moves further to 2G/3G.
  • Another advantage of the present disclosure is that mobility between 5GS and 2G/3G is possible, since if the mobility results in hanging sessions are not wanted.
  • Fig. 1 is a schematic diagram illustrating a communications system.
  • Fig. 2 is a schematic diagram illustrating a communications system.
  • Fig. 3 is a signaling diagram illustrating a method.
  • Fig. 4 is a signaling diagram illustrating a method.
  • Fig. 5 is a flow chart illustrating a method.
  • Fig. 6a is a schematic drawing illustrating a MME.
  • Fig. 6b is a schematic drawing illustrating a MME.
  • Fig. 7 is a schematic block diagram illustrating a telecommunication network connected via an intermediate network to a host computer.
  • Fig. 8 is a schematic block diagram of a host computer communicating via a base station with a UE over a partially wireless connection.
  • Fig. 9 is a flowchart depicting a method in a communications system comprising a host computer, a base station and a UE.
  • Fig. 10 is a flowchart depicting a method in a communications system comprising a host computer, a base station and a UE.
  • Fig. 11 is a flowchart depicting a method in a communications system comprising a host computer, a base station and a UE.
  • Fig. 12 is a flowchart depicting a method in a communications system comprising a host computer, a base station and a UE.
  • Fig. 2 is a flow chart illustrating a method for handling mobility of a UE 101.
  • the UE 101 is connected to the 5GS 103, i.e. it has established a PDU session associated with the 5GS 103 and consequently has a PDU session in the 5GS 103.
  • the PDU session may be described as a logical connection or an association between the UE 101 and 5GS 103.
  • the PDU session is the 5GS equivalent to the PDN connection in EPS 105 and equivalent to the PDP context in in 2G/3G 108.
  • the method comprises at least one of the following steps, which steps may be performed in any suitable order than described below:
  • a move of the UE 101 from the 5GS 103 to the EPS 105 is initiated.
  • the move may be initiated by the UE 101 itself or by some other node. This may also be described as initiation of a move of the UE 101 from being connected to the NG-RAN 103 to the E- UTRAN 105.
  • the reason for the move may be that the UE 101 exits the coverage area of the 5GS and enters the coverage area of EPS 105, that the UE 101 decides to move from 5GS 103 to EPS 105 in order to optimize its functioning, to obtain services that are accessible in EPS 105 and not in E-5GS 103, for charging reasons or any other suitable reason.
  • the UE 101 may inform the MME 113 about the move, for example by executing a Tracking Area Update (TAU) procedure towards the MME 113.
  • TAU Tracking Area Update
  • the MME 113 may be an example of a first network node, a first core network node, a first core network function, an EPC node, a first mobility node, a first mobility entity, an EPC mobility node etc. Note that the MME 113 is used as an example, and that any of the above listed terms may be equally be applicable.
  • the MME 113 may be a physical node, it may be a virtual node, a cloud node in a cloud network etc.
  • the MME 113 detects the initiated move from the 5GS 103 to the EPS 105. The detection may be based on receipt of information indicating the move from the UE 101.
  • the MME 113 Based on the detection of the initiated move, the MME 113 obtains UE related data from the AMF 110.
  • the UE related data is associated with the UE’s connection to the 5GS.
  • the AMF 110 is a 5G core network node located in the core network of the 5GS 105. The obtaining may be performed by that the MME 113 sends a request for the UE related data to the AMF 110 and the AMF 110 sends a response to the MME 113 with the UE related data.
  • the AMF 110 may be an example of a second network node, a second core network node, a second core network function, a 5GC node, a second mobility node, a second mobility entity, a 5GC mobility node, a 5GC mobility function etc. Note that the AMF 110 is used as an example, and that any of the above listed terms may be equally be applicable.
  • the AMF 110 may be a physical node, it may be a virtual node, a cloud node in a cloud network etc.
  • the UE related data may comprise an UE context.
  • the UE related data may comprise Mobility Management (MM) context and Session Management (SM) context related to the UE 101 in 5GS 103.
  • the MM context comprises mobility management and security parameters etc. as defined in 3GPP.
  • the SM context may be created by the AMF 110 by getting the information from the SMF(s) that the UE 101 is connected to in the 5GS 103.
  • EPS 105 and 2G/3G 108 there may be parameters that exist in all systems or that only exist in some or one of the systems. Since the UE related data in step 202 is associated with the UE’s connection to the 5GS 103, it may comprise 5G specific parameters only known to functions and nodes in the 5GS 103, it may comprise parameters that are known in both 5GS 103, EPS 105 and 2G/3G 108. Similarly, there may be parameters used in EPS 105 and the 2G/3G 108 that are not known in 5GS 103.
  • the UE related data e.g. the SM context
  • the parameter is not sent from the AMF 110 to the MME 113 at mobility from 5GS 103 to the EPS 105.
  • the reason for this is that the AMF 110 is not aware of the concept of the parameter since it is not included in the 5GS specification, but known to one or more of the nodes comprised in 2G/3G 108 and EPS 105.
  • neither a Context Response message nor a Forward Relocation Request message comprises the parameter.
  • the MME 113 may search for the parameter in order to detect that it is not comprised in the UE related data.
  • the parameter is provided by and known to the MME 113 and which exists in 2G/3G 108and EPS 105.
  • the parameter does not exist in 5GS such that 5GC nodes, e.g. the AMF 110, do not understand this parameter. Consequently, The AMF 110 is not able to include the parameter in the UE related data sent in step 202.
  • the parameter may be an information element, information, an identifier, etc.
  • One example of the parameter may be a Transaction Identifier (Tl) or any other suitable parameter known to one or more of the 2G, 3G and EPS, but not known to the 5GS 103.
  • Tl Transaction Identifier
  • the MME 113 Since the UE related data did not comprise the parameter, the MME 113 indicates the UE’s PDN connection in the EPS 105 as coming from the 5GS 103, i.e. that it originated as an 5GS PDU session. Thus, the lack of the parameter is an indication of that the PDN connection comes from the 5GS 103. This may be described as the MME 113 knows that the UE 101 comes from 5GS 103 since the UE related data lacks the parameter.
  • a move of the UE 101 from the EPS 105 to the 2G/3G communication network 108 is initiated. This may also be described as an initiation of a move of the UE 101 from being connected to the E-UTRAN 105 to the GERAN/UTRAN 108.
  • the move may be initiated by the UE 101 or by some other node.
  • the reason for the move may be that the UE 101 exits the coverage area of the E-UTRAN 105 and enters the coverage area of GERAN/UTRAN 108, that the UE 101 decides to move from E-UTRAN 105 to GERAN/UTRAN 108 in order to optimize its functioning, to obtain services that are accessible in GERAN/UTRAN 108 and not in E-UTRAN 105, for charging reasons or any other suitable reason.
  • the UE 101 may inform the SGSN about the move, for example by executing a Routing Area Update (RAU) procedure towards the SGSN.
  • RAU Routing Area Update
  • the SGSN will check if it is a new and unknown UE, i.e. that the SGSN lacks information about the UE, and if so try to retrieve proper information (typically MM and SM context) from another node, which in this case is the MME.
  • RAU Routing Area Update
  • Step 204 is performed after the move to the EPS 105 is completed.
  • the MME 113 detects that the move of the UE 101 from the EPS 105 to the 2G/3G 108 has been initiated. The detection may be based on receipt of information indicating the move from the UE 101.
  • the MME 113 When the MME 113 has detected the initiated move to the 2G/3G communication network 108, the MME 113 removes the PDU connection which is indicated as coming from the 5GS 103. After the removal, there is no hanging PDU connection in the SMF+PGW-C 118 anymore, and any related data/context in a PCF 121 , if used, is also removed to avoid hanging sessions in the PCF 121 as well.
  • the MME 113 initiates the removal of the PDN connection because the identified PDN connection cannot continue, i.e. session continuity cannot be fulfilled, to become a 2G/3G PDP Context due to it originated as an 5GS PDU session, as identified by the lack of the parameter.
  • the removal may be performed directly after the detection in step 205, it may be performed at some other time between initiation and completion of the move, it may be performed after the move to the 2G/3G communication network 108 has been completed, or it may be performed before or at the same time as step 207 is performed.
  • the action by the MME 113 in all cases is to remove information about the PDN connection/PDP Context in its communication towards the SGSN 120.
  • the MME 113 Based on the detection of the initiated move, the MME 113 provides UE related data to the SGSN 120. Using other words, the SGSN 120 obtains UE related data from the MME 113. The UE related data is associated with the UE’s connection to the EPS 105.
  • the SGSN 120 is an Evolved Packet Core (EPC) node located in the core network of the EPS 105. The obtaining may be performed by that the SGSN 120 sends a request for the UE related data to the MME 113 and the MME 113 sends a response to the SGSN 120 with the UE related data, that the MME 13 sends the UE related data without being requested etc.
  • the UE related data may comprise the MM context and the SM context for the UE 101 in EPS 105.
  • the SGSN 120 may be an example of a third network node, a third core network node, a third core network function, a 2G/3G node, a third mobility node, a third mobility entity, an 2G/3G mobility node etc. Note that the SGSN 120 is used as an example, and that any of the above listed terms may be equally be applicable.
  • the SGSN 120 may be a physical node, it may be a virtual node, a cloud node in a cloud network etc.
  • the SGSN 120 may for example be a S4-SGSN or a Gn-SGSN.
  • the parameter known in 2G/3G 108 and EPS 105 may be a Tl.
  • the Tl may be coded as seen below in Table 1.
  • the “purpose of the Tl information element is to represent the corresponding PDP context in A/Gb mode or lu mode which is mapped from the EPS bearer context.
  • the Tl information element is coded as the Linked Tl information element”.
  • Tl flag shall avoid ambiguity.
  • the transaction identifier flag can take the values "0" or "1”.
  • the Tl flag is used to identify which side of the interface initiated the transaction.
  • a message has a Tl flag set to "0" when it belongs to transaction initiated by its sender, and to "1" otherwise.”
  • the Tl may be sent over S3/S10/S16 if the UE supports A/Gb and/or lu mode.
  • the Tl may be sent over S3/S10/S16 if the UE 101 supports A/Gb and/or lu mode.
  • the parameter is not sent from the AMF 110 to the MME 113 at mobility from the 5GS 103 to the EPS 105.
  • This is also illustrated in step 301 in fig. 3.
  • the AMF 110 is not aware about the concept of parameter so neither the Context Response message and Forward Relocation Request will contain the parameter. If the UE 101 moves from the EPS 105 to the 2G/3G communication network 108, the MME 113 will set the parameter to ”NW provided” and send it to the SGSN, see step 303 in fig. 3 . Since the UE 101 in 2G/3G communication network 108 expects the parameter to be ”UE provided”, it will not accept a message with parameter set to ”NW provided”.
  • the MME 113 marks any PDU sessions from the AMF 110 (without the parameter) as ’’Not for 2G/3G” or as coming from the 5GS 103, and the MME 113 removes them at mobility from the EPS 105 to the 2G/3G communication network 108.
  • Fig. 4 is a flow chart illustrating a method for handling mobility of a UE 101 in idle mode. The skilled person would understand how the method will look like when the UE 101 is in connected mode.
  • the method in fig. 4 comprises at least one of the following steps, which steps may be performed in any suitable order than described below:
  • An initial registration of the UE 101 with the AMF 110 is performed.
  • a PDU Session Establishment procedure is performed between the UE 101 and the SMF+PGW-C 118 of the 5GC.
  • the concept of the parameter is not present in 5GS 103, so no parameter is assigned by the SMF+PGW-C 118.
  • This step corresponds to step 200 and step 201 in fig. 2.
  • Moving of the UE 101 from the 5GS 103 to the EPC 103 starts.
  • the moving may comprise a TAU procedure performed between the UE 101 and the MME 113.
  • the move may be initiated by the UE 101 or by some other node.
  • the MME 113 fetches, e.g. obtains, all data from the 5GC, i.e. the AMF 110.
  • the data may comprise MM and SM contexts.
  • This step corresponds to step 203 in fig. 2.
  • the parameter is not comprised in the SM Context and the MME 113 indicates or marks this PDN connection as coming from 5GC.
  • An update of the PDN Connection is performed between the MME 113 and the SMF+PGW-C 118.
  • the MME 113 may send, to the UE 101, information indicating that the move to the EPS 105 has been completed.
  • This step corresponds to step 204 and step 205 in fig. 3.
  • the UE 101 starts moving to the 2G/3G communication network 108.
  • the move may comprise a RAU procedure performed between the UE 101 and the SGSN 120.
  • the SGSN 120 fetches, e.g. obtains, data from the MME 113, i.e. the MME 113 provides the data to the SGSN 120 in the EPC.
  • the data may be the MM and SM context for the UE 101 in the EPC 105.
  • the PDN is marked as 5GS, and is not comprised in the information sent to the SGSN 120.
  • the SGSN 120 in the EPC sends information to the UE 101 indicating that the move to the 2G/3G communication network 108 has been completed. Step 411
  • the MME 113 removes the PDN connection which is not transferred to the 2G/3G communication network 108, since it originates from a PDU session in 5GS 103. Removing the PDN connection may be referred to as deleting the PDN connection, releOasing the PDN connection etc.
  • Fig. 5 is a flowchart describing the present method in the MME 113, for handling mobility of the UE 101.
  • the method comprises at least one of the following steps to be performed by the MME 113, which steps may be performed in any suitable order than described below:
  • This step corresponds to step 201 in fig. 2 and step 403 in fig. 4.
  • the MME 113 detects that a move of the UE 101 from a 5GS 103 to an EPS 105 has been initiated.
  • the UE may be in idle mode or connected mode.
  • the UE 101 may be a 5G UE.
  • This step corresponds to step 202 in fig. 2 and step 404 in fig. 4.
  • the MME 113 obtains UE related data from an AMF 110.
  • the UE related data does not comprise a parameter.
  • the parameter may be a Tl or any other suitable parameter.
  • This step corresponds to step 203 in fig. 2 and step 405 in fig. 4. Since the UE related data does not comprise the parameter, the MME 113 indicates that a PDN connection of the UE 101 in the EPS 105 as originating from the 5GS 103. This step may also be described as the MME 113 determines that the PDN connection of the UE 101 in the PES 105 should be marked or set as originating from the 5GS 103.
  • the PDU connection may not be for the 2G communication network 108 or the 3G communication network 108 when it is indicated as originating from the 5GS 103.
  • step 504 This step corresponds to step 205 in fig. 2 and step 408 in fig. 4.
  • the MME 113 detects that a move of the UE 101 from the EPS 105 to a 2G communication network 108 or a 3G communication network 108 has been initiated.
  • This step corresponds to step 207 in fig. 2 and step 409 in fig. 4.
  • the MME 113 may provide the UE related data to a SGSN 120.
  • the information indicating the PDU connection may not be included in the UE related data.
  • This step corresponds to step 409 in fig. 4.
  • the MME 113 may set the parameter to be network provided, i.e. provided by a network node.
  • the MME 113 may send the parameter to the SGSN 120.
  • the sent parameter may be set to be network provided, as may be done in step 506.
  • Step 507 may be a substep of step 505, i.e. the parameter may be comprised in the UE related data.
  • This step corresponds to step 206 in fig. 2 and step 411 in fig. 4.
  • the MME 113 removes the PDN connection indicated as originating from the 5GS 103.
  • the MME 113 may comprises an arrangement as shown in fig. 6a and/or fig. 6b.
  • Fig. 6a and fig. 6b depict two different examples in panels a) and b), respectively, of the arrangement that the MME 113 may comprise.
  • the MME 113 may comprise the following arrangement depicted in fig 6a.
  • the present disclosure related to the MME 113 may be implemented through one or more processors, such as a processor 601 in the MME 113 depicted in fig. 6a, together with computer program code for performing the functions and actions described herein.
  • a processor, as used herein, may be understood to be a hardware component.
  • the program code mentioned above may also be provided as a computer program product, for instance in the form of a data carrier carrying computer program code for performing the present disclosure when being loaded into the MME 113.
  • a data carrier carrying computer program code for performing the present disclosure when being loaded into the MME 113.
  • One such carrier may be in the form of a CD ROM disc. It is however feasible with other data carriers such as a memory stick.
  • the computer program code may be provided as pure program code on a server and downloaded to the MME 113.
  • the MME 113 may comprise a memory 603 comprising one or more memory units.
  • the memory 1003 is arranged to be used to store obtained information, store data, configurations, schedulings, and applications etc. to perform the methods herein when being executed in the MME 113.
  • the MME 113 may receive information from, e.g. the UE 101, the AMF 110, the SGSN 120, through a receiving port 605.
  • the receiving port 605 may be, for example, connected to one or more antennas in MME 113.
  • the MME 113 may receive information from another structure in the communications system through the receiving port 605. Since the receiving port 605 may be in communication with the processor 601, the receiving port 605 may then send the received information to the processor 601.
  • the receiving port 605 may also be configured to receive other information.
  • the processor 601 in the MME 113 may be configured to transmit or send information to e.g. the AMF 110, the SGSN 120, the UE 101 or another structure in the communications system, through a sending port 608, which may be in communication with the processor 601 and the memory 603.
  • the MME 113 is adapted to, e.g. by means of a detecting unit 610, detect that a move of the UE 101 from a 5GS 103 to an EPS 105 has been initiated.
  • the UE 101 may be in idle mode or connected mode.
  • the UE 101 may be a 5G UE.
  • the detecting unit 610 may also be referred to as a detecting module, a detecting means, a detecting circuit, means for detecting etc.
  • the detecting unit 610 may be the processor 601 of the MME 113 or comprised in the processor 601 of the MME 113.
  • the MME 113 is adapted to, e.g.
  • an obtaining unit 613 when the initiated move to the EPS 105 is detected, obtain UE related data from the AMF 110.
  • the UE related data does not comprise a parameter.
  • the parameter may be a Tl.
  • the obtaining unit 613 may also be referred to as an obtaining module, an obtaining means, an obtaining circuit, means for obtaining etc.
  • the obtaining unit 613 may be the processor 601 of the MME 113 or comprised in the processor 601 of the MME 113.
  • the MME 113 is adapted to, e.g. by means of an indicating unit 615, since the UE related data does not comprise the parameter, indicate that a PDN connection of the UE 101 in the EPS 105 as originating from the 5GS 103.
  • the PDU connection may not be for the 2G communication network 108 or the 3G communication network 108 when it is indicated as originating from the 5GS 103.
  • the indicating unit 615 may also be referred to as an indicating module, an indicating means, an indicating circuit, means for indicating etc.
  • the indicating unit 615 may be the processor 601 of the MME 113 or comprised in the processor 601 of the MME 113.
  • the MME 113 is adapted to, e.g. by means of the detecting unit 610, when the move to the EPS 105 is completed, detect that a move of the UE 101 from the EPS 105 to a 2G communication network 108 or a 3G communication network 108 has been initiated.
  • the MME 113 is adapted to, e.g. by means of a removing unit 618, when the initiated move to the 2G communication network 108 or the 3G communication network 108 has been detected, remove the PDN connection indicated as originating from the 5GS 103.
  • the removing unit 618 may also be referred to as a removing module, a removing means, a removing circuit, means for removing etc.
  • the removing unit 618 may be the processor 601 of the MME 113 or comprised in the processor 601 of the MME 113.
  • the MME 113 may be adapted to, e.g. by means of a providing unit 620, when the move to the 2G communication network 108 or the 3G communication network 108 has been detected, provide the UE related data to a SGSN 120. Information indicating the PDU connection may not be comprised in the UE related data.
  • the providing unit 620 may also be referred to as a providing module, a providing means, a providing circuit, means for providing etc.
  • the providing unit 620 may be the processor 601 of the MME 113 or comprised in the processor 601 of the MME 113.
  • the MME 113 may be adapted to, e.g.
  • the setting unit 623 may also be referred to as a setting module, a setting means, a setting circuit, means for setting etc.
  • the setting unit 623 may be the processor 601 of the MME 113 or comprised in the processor 601 of the MME 113.
  • the MME 113 may be adapted to, e.g. by means of a sending unit 625, send the parameter to a SGSN 120.
  • the sending unit 625 may also be referred to as a sending module, a sending means, a sending circuit, means for sending etc.
  • the sending unit 625 may be a wireless transmitter of the MME 13 of a wireless or fixed communications system.
  • the detecting unit 610, the obtaining unit 613, the indicating unit 615, the removing unit 618, the providing unit 620, the setting unit 623, the sending unit 625 and other unit(s) 628 described above may refer to a combination of analog and digital circuits, and/or one or more processors configured with software and/or firmware, e.g., stored in memory, that, when executed by the one or more processors such as the processor 601, perform as described above.
  • processors may be comprised in a single Application-Specific Integrated Circuit (ASIC), or several processors and various digital hardware may be distributed among several separate components, whether individually packaged or assembled into a System-on-a-Chip (SoC).
  • ASIC Application-Specific Integrated Circuit
  • SoC System-on-a-Chip
  • the different units 613-628 described above may be implemented as one or more applications running on one or more processors such as the processor 601.
  • the methods described herein for the MME 113 may be respectively implemented by means of a computer program 630 product, comprising instructions, i.e. , software code portions, which, when executed on at least one processor 601, cause the at least one processor 601 to carry out the actions described herein, as performed by the MME 113.
  • the computer program 630 product may be stored on a computer-readable storage medium 631.
  • the computer-readable storage medium 631 having stored thereon the computer program 630, may comprise instructions which, when executed on at least one processor 601 , cause the at least one processor 601 to carry out the actions described herein, as performed by the MME 113.
  • the computer-readable storage medium 631 may be a non-transitory computer-readable storage medium, such as a CD ROM disc, or a memory stick.
  • the computer program 630 product may be stored on a carrier containing the computer program 630 just described, wherein the carrier is one of an electronic signal, optical signal, radio signal, or the first computer-readable storage medium 631, as described above.
  • the MME may comprise a communication interface configured to facilitate communications between the MME 113 and other nodes or devices, e.g., the UE 101, the AMF 110, the SGSN 120, or another structure.
  • the interface may comprise a transceiver configured to transmit and receive radio signals over an air interface in accordance with a suitable standard.
  • the MME 113 may comprise the following arrangement depicted in fig. 6b.
  • the MME 113 may comprise a processing circuitry 640, e.g., one or more processors such as the processor 601, in the MME 113 and the memory 603.
  • the MME 113 may also comprise a radio circuitry 643, which may comprise e.g., the receiving port 605 and the sending port 608.
  • the processing circuitry 640 may be configured to, or operable to, perform the method actions according to fig. 2, 4 and 6, in a similar manner as that described in relation to fig. 6a.
  • the radio circuitry 643 may be configured to set up and maintain at least a wireless connection with the MME 113. Circuitry may be understood herein as a hardware component.
  • the present disclosure also relate to the MME 113 operative to operate in the communications system.
  • the MME 113 may comprise the processing circuitry 640 and the memory 603.
  • the memory 603 comprises instructions executable by the processing circuitry 640.
  • the MME 113 is operative to perform the actions described herein in relation to the MME 113, e.g. in figs. 2, 4 and 6.
  • a telecommunication network may be connected via an intermediate network to a host computer.
  • the telecommunication network may be a virtual telecommunication network, a cloud telecommunication network, a hardware telecommunication network or any other type of telecommunication network.
  • a communication system comprises telecommunication network 3210 such as the communications system 100, for example, a 3GPP-type cellular network, which comprises access network 3211 , such as a radio access network, and core network 3214.
  • Access network 3211 comprises a plurality of network nodes 105.
  • base stations 3212a, 3212b, 3212c such as NBs, eNBs, gNBs or other types of wireless access points, each defining a corresponding coverage area 3213a, 3213b, 3213c.
  • Each base station 3212a, 3212b, 3212c is connectable to core network 3214 over a wired or wireless connection 3215.
  • a plurality of UEs such as the UE 101 may be comprised in the communications system 100.
  • a first UE 3291 located in coverage area 3213c is configured to wirelessly connect to, or be paged by, the corresponding base station 3212c.
  • a second UE 3292 in coverage area 3213a is wirelessly connectable to the corresponding base station 3212a. While a plurality of UEs 3291 , 3292 are illustrated in this example, it is equally applicable to a situation where a sole UE is in the coverage area or where a sole UE is connecting to the corresponding base station 3212. Any of the UEs 3291 , 3292 may be considered examples of the UE 101.
  • Telecommunication network 3210 is itself connected to host computer 3230, which may be embodied in the hardware and/or software of a standalone server, a cloud- implemented server, a distributed server or as processing resources in a server farm.
  • Host computer 3230 may be under the ownership or control of a service provider, or may be operated by the service provider or on behalf of the service provider.
  • Connections 3221 and 3222 between telecommunication network 3210 and host computer 3230 may extend directly from core network 3214 to host computer 3230 or may go via an optional intermediate network 3220.
  • Intermediate network 3220 may be one of, or a combination of more than one of, a public, private or hosted network; intermediate network 3220, if any, may be a backbone network or the Internet; in particular, intermediate network 3220 may comprise two or more sub-networks (not shown).
  • the communication system of fig. 7 as a whole enables connectivity between the connected UEs 3291 , 3292 and host computer 3230.
  • the connectivity may be described as an Over-The-Top (OTT) connection 3250.
  • Host computer 3230 and the connected UEs 3291 , 3292 are configured to communicate data and/or signaling via OTT connection 3250, using access network 3211, core network 3214, any intermediate network 3220 and possible further infrastructure (not shown) as intermediaries.
  • OTT connection 3250 may be transparent in the sense that the participating communication devices through which OTT connection 3250 passes are unaware of routing of uplink and downlink communications. For example, base station 3212 may not or need not be informed about the past routing of an incoming downlink communication with data originating from host computer 3230 to be forwarded (e.g., handed over) to a connected UE 3291. Similarly, base station 3212 need not be aware of the future routing of an outgoing uplink communication originating from the UE 3291 towards the host computer 3230.
  • the base station may be considered an example of a network node 13 of the NG-RAN 103, the E- UTRAN 105 or the GERAN/UTRAN 108.
  • Fig. 8 illustrates an example of host computer communicating via a network node with a UE 101 over a partially wireless connection.
  • host computer 3310 comprises hardware 3315 comprising communication interface 3316 configured to set up and maintain a wired or wireless connection with an interface of a different communication device of communication system 3300.
  • Host computer 3310 comprises processing circuitry 3318, which may have storage and/or processing capabilities.
  • processing circuitry 3318 may comprise one or more programmable processors, application-specific integrated circuits, field programmable gate arrays or combinations of these (not shown) adapted to execute instructions.
  • Host computer 3310 comprises software 3311, which is stored in or accessible by host computer 3310 and executable by processing circuitry 3318.
  • Software 3311 comprises host application 3312.
  • Host application 3312 may be operable to provide a service to a remote user, such as UE 3330 connecting via OTT connection 3350 terminating at UE 3330 and host computer 3310. In providing the service to the remote user, host application 3312 may provide user data which is transmitted using OTT connection 3350.
  • Communication system 3300 comprises the network node exemplified in fig. 8 as a base station 3320 provided in a telecommunication system and comprising hardware 3325 enabling it to communicate with host computer 3310 and with UE 3330.
  • Hardware 3325 may comprise communication interface 3326 for setting up and maintaining a wired or wireless connection with an interface of a different communication device of communication system 3300, as well as radio interface 3327 for setting up and maintaining at least wireless connection 3370 with the UE 101 , exemplified in fig. 8 as a UE 3330 located in a coverage area served by base station 3320.
  • Communication interface 3326 may be configured to facilitate connection 3360 to host computer 3310. Connection 3360 may be direct or it may pass through a core network (not shown in fig.
  • Hardware 3325 of base station 3320 comprises processing circuitry 3328, which may comprise one or more programmable processors, application-specific integrated circuits, field programmable gate arrays or combinations of these (not shown) adapted to execute instructions.
  • Base station 3320 has software 3321 stored internally or accessible via an external connection.
  • Communication system 3300 comprises UE 3330 already referred to. It’s hardware 3335 may comprise radio interface 3337 configured to set up and maintain wireless connection 3370 with a base station serving a coverage area in which UE 3330 is currently located.
  • Hardware 3335 of UE 3330 comprises processing circuitry 3338, which may comprise one or more programmable processors, application-specific integrated circuits, field programmable gate arrays or combinations of these (not shown) adapted to execute instructions.
  • UE 3330 comprises software 3331 , which is stored in or accessible by UE 3330 and executable by processing circuitry 3338.
  • Software 3331 comprises client application 3332. Client application 3332 may be operable to provide a service to a human or non-human user via UE 3330, with the support of host computer 3310.
  • an executing host application 3312 may communicate with the executing client application 3332 via OTT connection 3350 terminating at UE 3330 and host computer 3310.
  • client application 3332 may receive request data from host application 3312 and provide user data in response to the request data.
  • OTT connection 3350 may transfer both the request data and the user data.
  • Client application 3332 may interact with the user to generate the user data that it provides.
  • host computer 3310, base station 3320 and UE 3330 illustrated in fig. 8 may be similar or identical to host computer 3230, one of base stations 3212a, 3212b, 3212c and one of UEs 3291 , 3292 of fig. 320, respectively.
  • the inner workings of these entities may be as shown in fig. 330 and independently, the surrounding network topology may be that of fig. 7.
  • OTT connection 3350 has been drawn abstractly to illustrate the communication between host computer 3310 and UE 3330 via base station 3320, without explicit reference to any intermediary devices and the precise routing of messages via these devices.
  • Network infrastructure may determine the routing, which it may be configured to hide from UE 3330 or from the service provider operating host computer 3310, or both. While OTT connection 3350 is active, the network infrastructure may take decisions by which it dynamically changes the routing, e.g., on the basis of load balancing consideration or reconfiguration of the network.
  • wireless connection 3370 between UE 3330 and base station 3320.
  • the present disclosure improve the performance of OTT services provided to UE 3330 using OTT connection 3350, in which wireless connection 3370 forms the last segment.
  • the present disclosure may improve the spectrum efficiency, and latency, and thereby provide benefits such as reduced user waiting time, better responsiveness and extended battery lifetime.
  • a measurement procedure may be provided for the purpose of monitoring data rate, latency and other factors on which the present disclosure improve.
  • There may be an optional network functionality for reconfiguring OTT connection 3350 between host computer 3310 and UE 3330, in response to variations in the measurement results.
  • the measurement procedure and/or the network functionality for reconfiguring OTT connection 3350 may be implemented in software 3311 and hardware 3315 of host computer 3310 or in software 3331 and hardware 3335 of UE 3330, or both.
  • Sensors (not shown) may be deployed in or in association with communication devices through which OTT connection 3350 passes; the sensors may participate in the measurement procedure by supplying values of the monitored quantities exemplified above, or supplying values of other physical quantities from which software 3311, 3331 may compute or estimate the monitored quantities.
  • the reconfiguring of OTT connection 3350 may comprise message format, retransmission settings, preferred routing etc.; the reconfiguring need not affect base station 3320, and it may be unknown or imperceptible to base station 3320. Such procedures and functionalities may be known and practiced in the art. Measurements may involve proprietary UE signaling facilitating host computer 3310’s measurements of throughput, propagation times, latency and the like. The measurements may be implemented in that software 3311 and 3331 causes messages to be transmitted, in particular empty or ‘dummy’ messages, using OTT connection 3350 while it monitors propagation times, errors etc.
  • Fig. 9 illustrates an example of methods implemented in a communication system comprising a host computer, a base station and a UE.
  • Fig. 9 is a flowchart illustrating a method implemented in a communication system.
  • the communication system comprises a host computer, a base station and a UE which may be those described with reference to fig. 7 and fig. 8. For simplicity of the present disclosure, only drawing references to fig. 9 will be comprised in this section.
  • the host computer provides user data.
  • substep 3411 (which may be optional) of step 3410, the host computer provides the user data by executing a host application.
  • the host computer initiates a transmission carrying the user data to the UE.
  • step 3430 the base station transmits to the UE the user data which was carried in the transmission that the host computer initiated.
  • step 3440 (which may also be optional) the UE executes a client application associated with the host application executed by the host computer.
  • Fig. 10 illustrates methods implemented in a communication system comprising a host computer, a base station and a UE.
  • Fig. 10 is a flowchart illustrating a method implemented in a communication system.
  • the communication system comprises a host computer, a base station and a UE which may be those described with reference to fig. 7 and fig. 8. For simplicity of the present disclosure, only drawing references to fig. 10 will be comprised in this section.
  • the host computer provides user data.
  • the host computer provides the user data by executing a host application.
  • the host computer initiates a transmission carrying the user data to the UE. The transmission may pass via the base station.
  • step 3530 the UE receives the user data carried in the transmission.
  • Fig. 11 illustrates methods implemented in a communication system comprising a host computer, a base station and a user equipment.
  • Fig. 11 is a flowchart illustrating a method implemented in a communication system.
  • the communication system comprises a host computer, a network node and a UE 101 which may be those described with reference to fig. 7 and fig. 8. For simplicity of the present disclosure, only drawing references to fig. 11 will be comprised in this section.
  • step 3610 (which may be optional) the UE 101 receives input data provided by the host computer. Additionally or alternatively, in step 3620, the UE 101 provides user data.
  • substep 3621 (which may be optional) of step 3620, the UE provides the user data by executing a client application.
  • substep 3611 (which may be optional) of step 3610, the UE executes a client application which provides the user data in reaction to the received input data provided by the host computer. In providing the user data, the executed client application may consider user input received from the user. Regardless of the specific manner in which the user data was provided, the UE initiates, in substep 3630 (which may be optional), transmission of the user data to the host computer.
  • step 3640 of the method the host computer receives the user data transmitted from the UE.
  • Fig. 13 illustrates methods implemented in a communication system comprising a host computer, a base station and a user equipment.
  • Fig. 13 is a flowchart illustrating a method implemented in a communication system.
  • the communication system comprises a host computer, a base station and a UE which may be those described with reference to fig. 7 and fig. 8. For simplicity of the present disclosure, only drawing references to fig. 13 will be comprised in this section.
  • step 3710 (which may be optional)
  • the base station receives user data from the UE.
  • step 3720 which may be optional
  • the base station initiates transmission of the received user data to the host computer.
  • step 3730 (which may be optional)
  • the host computer receives the user data carried in the transmission initiated by the base station.
  • a network node configured to communicate with a UE 101 , the network node comprising a radio interface and processing circuitry configured to perform one or more of the actions described herein as performed by the network node.
  • a communication system 100 comprising a host computer comprising: • processing circuitry configured to provide user data; and
  • a communication interface configured to forward the user data to a cellular network for transmission to a UE 101
  • the communication system 100 comprises a network node having a radio interface and processing circuitry, the network nodes processing circuitry configured to perform one or more of the actions described herein as performed by the network node.
  • the communication system may comprise the network node.
  • the network node may be for example the MME 113.
  • the communication system may comprise the UE 101 , wherein the UE 101 is configured to communicate with the network node.
  • the processing circuitry of the host computer is configured to execute a host application, thereby providing the user data
  • the UE 101 comprises processing circuitry configured to execute a client application associated with the host application.
  • a method implemented in a network node comprising one or more of the actions described herein as performed by the network node.
  • a method implemented in a communication system 100 comprising a host computer, a network node and a UE 101 , the method comprising:
  • the network node • at the host computer, initiating a transmission carrying the user data to the UE 101 via a cellular network comprising the network node, wherein the network node performs one or more of the actions described herein as performed by the network node.
  • the method may comprise:
  • the user data may be provided at the host computer by executing a host application, and the method may comprise: at the UE 101, executing a client application associated with the host application.
  • a UE 101 configured to communicate with a network node, the UE 101 comprising a radio interface and processing circuitry configured to perform one or more of the actions described herein as performed by the UE 101.
  • a communication system 100 comprising a host computer comprising:
  • processing circuitry configured to provide user data
  • a communication interface configured to forward user data to a cellular network for transmission to a UE 101, wherein the UE comprises a radio interface and processing circuitry, the UE’s processing circuitry configured to perform one or more of the actions described herein as performed by the UE 101.
  • the communication system may comprise the UE 101.
  • the communication system 100 wherein the cellular network comprises a network node configured to communicate with the UE 101.
  • the communication system 100 wherein:
  • the processing circuitry of the host computer is configured to execute a host application, thereby providing the user data
  • the UE’s processing circuitry is configured to execute a client application associated with the host application.
  • a method implemented in a UE 101 comprising one or more of the actions described herein as performed by the UE 101.
  • a method implemented in a communication system 100 comprising a host computer, a network node and a UE 101 , the method comprising:
  • the method may comprise:
  • a UE 101 configured to communicate with a network node, the UE 101 comprising a radio interface and processing circuitry configured to perform one or more of the actions described herein as performed by the UE 101.
  • a communication system 100 comprising a host computer comprising:
  • a communication interface configured to receive user data originating from a transmission from a UE 101 to a network node
  • the UE 101 comprises a radio interface and processing circuitry, the UE’s processing circuitry configured to perform one or more of the actions described herein as performed by the UE 101.
  • the communication system 100 may comprise the UE 101.
  • the communication system 100 may comprise the network node.
  • the network node comprises a radio interface configured to communicate with the UE 101 and a communication interface configured to forward to the host computer the user data carried by a transmission from the UE 101 to the base station.
  • the communication system 100 wherein:
  • the processing circuitry of the host computer is configured to execute a host application
  • the UE’s processing circuitry is configured to execute a client application associated with the host application, thereby providing the user data.
  • the communication system 100 wherein:
  • the processing circuitry of the host computer is configured to execute a host application, thereby providing request data
  • the UE’s processing circuitry is configured to execute a client application associated with the host application, thereby providing the user data in response to the request data.
  • the method may comprise:
  • a method implemented in a communication system 100 comprising a host computer, a network node and a UE 101, the method comprising:
  • the method may comprise:
  • the method may comprise:
  • the method may comprise:
  • a network node configured to communicate with a UE 101 , the network node comprising a radio interface and processing circuitry configured to perform one or more of the actions described herein as performed by the network node.
  • a communication system 100 comprising a host computer comprising a communication interface configured to receive user data originating from a transmission from a UE 101 to a base station.
  • the network node comprises a radio interface and processing circuitry, the network node’s processing circuitry configured to perform one or more of the actions described herein as performed by the network node.
  • the communication system 100 may comprise the network node 10.
  • the communication system 100 may comprise the UE 101 , wherein the UE 101 is configured to communicate with the network node.
  • the communication system 100 wherein:
  • the processing circuitry of the host computer is configured to execute a host application
  • the UE 101 is configured to execute a client application associated with the host application, thereby providing the user data to be received by the host computer.
  • a method implemented in a network node comprising one or more of the actions described herein as performed by any of the network node.
  • a method implemented in a communication system comprising a host computer, a network node and a UE 101 , the method comprising:
  • the method may comprise:
  • the method may comprise:
  • first”, “second”, “third”, “fourth”, and/or “fifth” herein may be understood to be an arbitrary way to denote different elements or entities, and may be understood to not confer a cumulative or chronological character to the nouns they modify, unless otherwise noted, based on context.
  • a and B should be understood to mean “only A, only B, or both A and B.”, where A and B are any parameter, number, indication used herein etc.

Landscapes

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

Abstract

La présente divulgation concerne un procédé exécuté par une entité de gestion de la mobilité (MME) (113) permettant de gérer la mobilité d'un équipement utilisateur (UE) (101). La MME (113) détecte un passage de l'UE (101) d'un 5GS (103) à un EPS (105). Lorsque le passage à l'EPS (105) est détecté, la MME (113) obtient, d'une AMF (110), des données associées à l'UE. Les données associées à l'UE ne comprennent pas de paramètre donné. Étant donné que les données ne comprennent pas le paramètre, la MME (113) indique qu'une connexion à un réseau public de transmission de données de l'UE (101) dans l'EPS (105) provient du 5GS (103). Une fois le passage à l'EPS (105) achevé, la MME (113) détecte un passage de l'UE (101) de l'EPS (105) à un réseau de communication 2G ou 3G (108). Une fois le passage au réseau de communication 2G ou 3G (108) détecté, la MME (113) élimine la connexion au réseau public de transmission de données.
EP20768561.1A 2020-09-07 2020-09-07 Procédé et mme permettant de prendre en charge la mobilité d'un équipement utilisateur Withdrawn EP4211932A1 (fr)

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/EP2020/074983 WO2022048785A1 (fr) 2020-09-07 2020-09-07 Procédé et mme permettant de prendre en charge la mobilité d'un équipement utilisateur

Publications (1)

Publication Number Publication Date
EP4211932A1 true EP4211932A1 (fr) 2023-07-19

Family

ID=72432894

Family Applications (1)

Application Number Title Priority Date Filing Date
EP20768561.1A Withdrawn EP4211932A1 (fr) 2020-09-07 2020-09-07 Procédé et mme permettant de prendre en charge la mobilité d'un équipement utilisateur

Country Status (2)

Country Link
EP (1) EP4211932A1 (fr)
WO (1) WO2022048785A1 (fr)

Also Published As

Publication number Publication date
WO2022048785A1 (fr) 2022-03-10

Similar Documents

Publication Publication Date Title
US11375471B2 (en) Method for performing service request procedure and apparatus therefor in wireless communication system
US20230056728A1 (en) Communications Method and Apparatus
US20200322777A1 (en) Method for tracking area update in wireless communication system and apparatus therefor
US10993142B2 (en) Method and apparatus for CIoT device data transfer
US10999878B2 (en) Communication system and communication method for improving signal processing efficiency
EP3253083B1 (fr) Procédé et dispositif de commande sur la base de priorités multiples dans un système de communication sans fil
US10827394B2 (en) Triggering selective fallback based on user subscription information
WO2018145657A1 (fr) Procédé et appareil de transfert intercellulaire entre systèmes dans une communication sans fil
EP3619985A1 (fr) Différenciation de politique de radiomessagerie dans un système 5g
US11729686B2 (en) Transmission control method, apparatus, and system
US10623990B2 (en) User equipment and method for transmitting data, and network node and method for receiving data
US11696358B2 (en) Methods and nodes for handling bearers
WO2017135857A1 (fr) Nœud de réseau central, nœud de réseau radio, dispositif sans fil et procédés exécutés dans ceux-ci
CN110547006A (zh) 无线通信的方法、网络设备和终端设备
US20190132782A1 (en) Method and device for providing circuit switching service in wireless communication system
US20210385723A1 (en) Policy Management Method and Apparatus
JP2022549018A (ja) セッション管理のための方法および装置
US20240098148A1 (en) Restoration of a pdn connection at pgw failure
WO2016082222A1 (fr) Sgw, mme et procédé et système de radiomessagerie
EP3457639B1 (fr) Procédé, dispositif et système de communication
US20220191766A1 (en) Ue, network nodes for handling ue category information
WO2022048785A1 (fr) Procédé et mme permettant de prendre en charge la mobilité d'un équipement utilisateur
WO2022148571A1 (fr) Procédés et appareils de transfert entre différentes rat
CN114287169B (zh) 用于改进的分组检测规则提供的方法和装置
US20230403670A1 (en) Sip-deregistration by evolved packet core network

Legal Events

Date Code Title Description
STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: UNKNOWN

STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: THE INTERNATIONAL PUBLICATION HAS BEEN MADE

PUAI Public reference made under article 153(3) epc to a published international application that has entered the european phase

Free format text: ORIGINAL CODE: 0009012

STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: REQUEST FOR EXAMINATION WAS MADE

STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: THE APPLICATION HAS BEEN WITHDRAWN

17P Request for examination filed

Effective date: 20230110

AK Designated contracting states

Kind code of ref document: A1

Designated state(s): AL AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HR HU IE IS IT LI LT LU LV MC MK MT NL NO PL PT RO RS SE SI SK SM TR

18W Application withdrawn

Effective date: 20230622