WO2019057307A1 - Gestion de paquets de données dans un réseau central - Google Patents

Gestion de paquets de données dans un réseau central Download PDF

Info

Publication number
WO2019057307A1
WO2019057307A1 PCT/EP2017/074186 EP2017074186W WO2019057307A1 WO 2019057307 A1 WO2019057307 A1 WO 2019057307A1 EP 2017074186 W EP2017074186 W EP 2017074186W WO 2019057307 A1 WO2019057307 A1 WO 2019057307A1
Authority
WO
WIPO (PCT)
Prior art keywords
data packet
core network
entity
downlink data
towards
Prior art date
Application number
PCT/EP2017/074186
Other languages
English (en)
Inventor
Hans Bertil RÖNNEKE
Peter Hedman
Original Assignee
Telefonaktiebolaget Lm Ericsson (Publ)
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 (Publ) filed Critical Telefonaktiebolaget Lm Ericsson (Publ)
Priority to PCT/EP2017/074186 priority Critical patent/WO2019057307A1/fr
Publication of WO2019057307A1 publication Critical patent/WO2019057307A1/fr

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/20—Services signaling; Auxiliary data signalling, i.e. transmitting data via a non-traffic channel
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/18—Information format or content conversion, e.g. adaptation by the network of the transmitted or received information for the purpose of wireless delivery to users or terminals
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/70—Services for machine-to-machine communication [M2M] or machine type communication [MTC]

Definitions

  • Embodiments presented herein relate to a method, a core network entity, a computer program, and a computer program product for data packet handling in a core network.
  • communications networks there may be a challenge to obtain good performance and capacity for a given communications protocol, its parameters and the physical environment in which the communications network is deployed.
  • Fig. l depicts a system architecture 100a for a fifth generation (5G) telecommunications system for a non-roaming user equipment (UE) 108 concurrently accessing a (e.g. local or central) data network (DN) 111 using a protocol data unit (PDU) sessions, using a reference point representation.
  • Fig. 1 shows the architecture for one PDU session where one Session
  • SMF Management Function
  • UPF User plane Function
  • the architecture allows the capability to control both a local and a central UPF within a PDU session.
  • Fig. 2 depicts a system architecture 100b for a fifth generation (5G) telecommunications system for a non-roaming UE 108 using the service based architecture representation for the control plane (e.g. N3 and N6) for the user plane and a service based representation for the control plane.
  • the service based interfaces are indicated by the letter "N" followed by the name of the network function (NF), e.g. Nsmf for the service based interface of the SMF etc.
  • NF network function
  • the system architectures 100a, 100b generally consists of the following NFs: Authentication Server Function (AUSF) 102, Core Access and Mobility Management Function (AMF) 104, Data network (DN) 111, e.g. operator services, Internet access or third party services, Unstructured Data Storage network function (UDSF), Network Exposure Function (NEF) 112, NF
  • AUSF Authentication Server Function
  • AMF Core Access and Mobility Management Function
  • DN Data network
  • UDSF Unstructured Data Storage network function
  • NEF Network Exposure Function
  • NEF Network Slice Selection Function
  • PCF Policy Control function
  • SMF Session Management Function
  • UDM Unified Data Management
  • URF Unified Data Repository
  • UPF User plane Function
  • AF Application Function
  • UE User Equipment
  • R Radio
  • UPF User Plane
  • SCEF Service Capability Exposure Function
  • NIDD Non-IP Data Delivery
  • Control Plane EPS CIoT Optimization also known as DoNAS; Data over NAS
  • the SCEF may e.g. be supported and/or implemented by the NEF, or similar.
  • NIDD Non-IP Data Delivery
  • DoNAS Data over NAS
  • the SCEF may e.g. be supported and/or implemented by the NEF, or similar.
  • user data is sent in the User Plane, which is optimized for sending data. When sent in the control plane there are no means for distinguishing signaling from data, so prioritized signaling may be congested when less prioritized data is sent in the control plane.
  • SCEF is primarily specified to expose data or meta-data about UEs connected to a mobile network. The SCEF is not intended to handle user data conveyed between the UE and external entities such as application servers.
  • An object of embodiments herein is to provide efficient handling of data packets in a core network.
  • a method for data packet handling in a core network is performed by a core network entity.
  • the method comprises receiving a downlink data packet originating from a data network and intended for a device.
  • the method comprises determining, based on at least one network property associated with the downlink data packet, whether to forward the downlink data packet towards a user plane function entity or towards a core network entity control plane function entity.
  • the method comprises sending the downlink data packet towards the selected function entity.
  • a core network entity for data packet handling in a core network.
  • the core network entity comprises processing circuitry.
  • the processing circuitry is configured to cause the core network entity to receive a downlink data packet originating from a data network and intended for a device.
  • the processing circuitry is configured to cause the core network entity to determine, based on at least one network property associated with the downlink data packet, whether to forward the downlink data packet towards a user plane function entity or towards a control plane function entity.
  • the processing circuitry is configured to cause the core network entity to send the downlink data packet towards the selected function entity.
  • a core network entity for data packet handling in a core network.
  • the core network entity comprises processing circuitry and a storage medium.
  • the storage medium stores instructions that, when executed by the processing circuitry, cause the core network entity to perform operations, or steps.
  • the operations, or steps, cause the core network entity to receive a downlink data packet originating from a data network and intended for a device.
  • the operations, or steps, cause the core network entity to determine, based on at least one network property associated with the downlink data packet, whether to forward the downlink data packet towards a user plane function entity or towards a control plane function entity.
  • the operations, or steps cause the core network entity to send the downlink data packet towards the selected function entity.
  • a core network entity for data packet handling in a core network.
  • the core network entity comprises a receive module configured to receive a downlink data packet originating from a data network and intended for a device.
  • the core network entity comprises a determine module configured to determine, based on at least one network property associated with the downlink data packet, whether to forward the downlink data packet towards a user plane function entity or towards a control plane function entity.
  • the core network entity comprises a send module configured to send the downlink data packet towards the selected function entity.
  • a computer program for data packet handling in a core network comprising computer program code which, when run on a core network entity, causes the core network entity to perform a method according to the first aspect.
  • a computer program product comprising a computer program according to the fifth aspect and a computer readable storage medium on which the computer program is stored.
  • the computer readable storage medium could be a non-transitory computer readable storage medium.
  • these core network node entities, this computer program, and this computer program product avoid the implementation of CIoT optimization for DoNAS in the core network for a 5G telecommunications system.
  • these core network node entities, this computer program, and this computer program product enable a separation of NIDD small data transmission functions and Exposure functions (i.e. separation of user data transmission (for IoT) between the device and external Application Servers (AS) or Service Capability Servers (SCS) and the exposure functions that are providing metadata about devices to external partners to the operator.
  • NIDD small data transmission functions and Exposure functions i.e. separation of user data transmission (for IoT) between the device and external Application Servers (AS) or Service Capability Servers (SCS) and the exposure functions that are providing metadata about devices to external partners to the operator.
  • FIGs. 1 and 2 are schematic diagrams illustrating system architectures of a telecommunications system
  • FIGS. 3 and 4 are schematic diagrams illustrating system architectures of a telecommunications system according to embodiments
  • Fig. 5 is a flowchart of methods according to embodiments
  • Fig. 6 is a schematic diagram showing functional units of a core network entity according to an embodiment
  • Fig. 7 is a schematic diagram showing functional modules of a core network entity according to an embodiment
  • Fig. 8 shows one example of a computer program product comprising computer readable storage medium according to an embodiment.
  • the embodiments disclosed herein relate to mechanisms for data packet handling in a core network.
  • a core network entity 200 a method performed by the core network entity 200, a computer program product comprising code, for example in the form of a computer program, that when run on a core network entity 200, causes the core network entity 200 to perform the method.
  • Some general definitions and context in which the herein disclosed embodiments could be implemented will now be given.
  • PtP Point-to-Point
  • IPv6 prefix allocation for PDU sessions are performed locally by the (H-)SMF without involving the UE.
  • the UPF(s) acts as a transparent forwarding node for the payload between the UE and the destination in the DN or in a Network IoT Function (NIF).
  • NIF Network IoT Function
  • the UPF forwards the received Unstructured PDU type data to the destination in the data network over the N6 PtP tunnel using UDP/IPv6 encapsulation or to the destination in the NIF over the N6 PtP tunnel using UDP/IPv6 encapsulation.
  • the destination in the data network or the NIF sends the Unstructured PDU type data using UDP/IPv6 encapsulation with the IPv6 address of the PDU Session and the 3GPP defined UDP port for Unstructured PDU type data.
  • the UPF acting as PDU Session Anchor decapsulates the received data (i.e. removes the UDP/IPv6 headers) and forwards the data identified by the IPv6 prefix of the PDU session for delivery to the UE.
  • the (H-)SMF performs the IPv6 related operations but the IPv6 prefix is not provided to the UE, i.e. Router
  • the SMF assigns an IPv6 Interface Identifier for the PDU session.
  • the allocated IPv6 prefix identifies the PDU session of the UE.
  • the NEF supports external exposure of capabilities of network functions. External exposure could, for example, be categorized as Monitoring capability, Provisioning capability, and Policy/Charging capability.
  • the Monitoring capability in some aspects is for monitoring of specific event for UE in 5G systems and making such monitoring events information available for external exposure via the NEF.
  • the Provisioning capability in some aspects is for allowing an external party to provision of information which can be used for the UE in 5G system.
  • the Policy/Charging capability in some aspects is for handling quality of service (QoS) and charging policy for the UE based on the request from external party.
  • QoS quality of service
  • the monitoring capability generally comprises mechanisms that allow the identification of the 5G network function suitable for configuring the specific monitoring events, detect the monitoring event, and report the monitoring event to the authorized external party.
  • Monitoring capability can be used for exposing UE's mobility management context such as UE location, reachability, roaming status, and loss of connectivity.
  • the provisioning capability generally comprises
  • Provisioning capability can be used for the mobility management and session management of the UE. For the mobility
  • Mobility Pattern can be provisioned.
  • communication pattern can be provisioned such as periodic communication time, communication duration time, and scheduled communication time.
  • Policy/Charging capability generally comprises
  • the external exposure functionality might inherit from the service and capability exposure functionality defined in 3GPP TS 23.682.
  • Fig. 3 illustrates a system architecture 100c for a 5G telecommunications system identical to that of Fig. 1 but with the difference that the system architecture 100c comprises a core network entity 200, e.g. such as a NIF or similar.
  • a core network entity 200 e.g. such as a NIF or similar.
  • Fig. 4 illustrates a system architecture lood for a 5G telecommunications system identical to that of Fig. 2 but with the difference that Fig. 4 comprises a core network entity 200, e.g. such as a NIF or similar.
  • Fig. 5 illustrating a method for data packet handling in a core network as performed by the core network entity 200 according to an embodiment.
  • S102 The core network entity 200 receives a downlink data packet originating from a data network and intended for a device. Examples of such a device will be provided below.
  • S104 The core network entity 200 determines, based on at least one network property associated with the downlink data packet, whether to forward the downlink data packet towards a user plane function entity or towards a control plane function entity.
  • S108 The core network entity 200 sends the downlink data packet towards the selected function entity. That is, the downlink data packet is sent towards either the user plane function entity or the control plane function entity, where the decision regarding to which of these functional entities to send the data packet towards is made based on the at least one network property associated with the downlink data packet.
  • the device might be a portable wireless device, mobile station, mobile phone, handset, wireless local loop phone, user equipment (UE), smartphone, laptop computer, tablet computer, sensor device, wireless modem, network equipped vehicle (such as a drone or autonomous car), etc.
  • the device is an Internet of Things (IoT) device.
  • IoT Internet of Things
  • the downlink data packet originates from an application server or a service capability server (e.g. an AF, see 3GPP TS 23.501 or 3GPP TS 23.203, or an SCS/AS, see 3GPP TS 23.682) in the data network.
  • an application server or a service capability server e.g. an AF, see 3GPP TS 23.501 or 3GPP TS 23.203, or an SCS/AS, see 3GPP TS 23.682
  • the at least one network property is defined by the format of the data packet, characteristics of communications between the data network and the device such as operation configuration, load factors, or weight factors, or capabilities of the device or data network, or a service licence agreement.
  • operation configuration could e.g. be that communication is configured in the NF to be treated in a specific way
  • Load factors e.g. to the load in the system or the load at a certain path, could be used to decide whether to route the data through a specific path or convert the data into a compressed form. Weight factors between different paths could be used to spread the load the data adds to the system.
  • Capabilities of the device for downlink data and of the entity in the data network (for uplink data) can be used to decide on how to convert the data.
  • Service licence (or level) agreements can be used to decide how to convert the data or which path to use for the data (e.g. use a more reliable path which implies more cost but is more reliable for a user who is willing to pay more for the service), etc..
  • the downlink data packet comprises so-called small data.
  • the downlink data packet might comprise control signalling, instructions, etc.
  • the downlink data packet comprises data representing application layer control signalling or instructions associated with the device.
  • the downlink data packet might comprise data representing payload for the device.
  • the downlink data packet might represent a short messaging service (SMS) for the device.
  • SMS short messaging service
  • the core network entity 200 is configured to determine whether to convert the downlink data.
  • the received downlink data packet is of a first data format and the core network entity 200 is configured to perform (optional) step S106:
  • the core network entity 200 determines, based on which type of data format the downlink data packet has, whether to convert the received downlink data packet to a second format before sending the downlink data packet towards the selected entity. If so the core network entity 200 also converts the received downlink data before sending the converted downlink data packet towards the selected entity. In some aspects the received downlink data packet is converted based on the first data format of the received downlink data packet. The core network entity 200 might convert the received downlink data packet into a format that the device is capable of handling. In some aspects the core network entity 200 is configured to convert uplink data. Thus, according to an embodiment the core network entity 200 is configured to perform (optional) steps S110, S112, S114:
  • S110 The core network entity 200 receives an uplink data packet originating from the device.
  • S112 The core network entity 200 determines, based on which type of data format the uplink data packet has, whether to convert the received uplink data packet to a second data format before sending the uplink data packet towards the data network. If so the core network entity 200 also converts the received uplink data packet.
  • S114 The core network entity 200 sends the uplink data packet towards the data network.
  • the core network entity 200 might convert the received uplink data packet into a format that the data network is capable of handling.
  • steps S110-S114 are performed independently of steps S102- S108.
  • steps S110-S114 provides an alternative definition to at least steps S102, S104, and S108 in terms of the inventive concept as herein disclosed.
  • a method for data packet handling in a core network as performed by the core network entity 200, where the method comprises steps S110-S114, and where any of steps S102- S108 are optional, and thus might be performed either before steps S110- S114, after steps S110-S114, or not performed at all.
  • the data formats are defined by which application protocol or which transport protocol is used for handling the data packet in the core network.
  • the uplink data packet comprises so-called small data.
  • the uplink data packet might comprise measurement data. The measurement data might have been collected, recorded, and/or sensed by the device and is reported from the device to the data network.
  • the core network entity 200 may be operatively connected to the data network, to the control plane function entity, and to the user plane function entity. Different embodiments relating thereto will now be described in turn.
  • T8 reference point is used for uplink
  • the core network entity 200 is operatively connected to the data network via a T8 interface or reference point, or a RESTful interface or reference point.
  • the T8 interface is as such specified in 3GPP TS 23.401 and in 3GPP TS 29.122.
  • connection to the user plane is at the N6 reference point (to a user plane function). In other aspects the connection to the user plane is at the N3 reference point (to a radio access network). In yet other aspects the connection to the user plane is at the SGi reference point (to an evolved packet core packet data network gateway (EPC PDN GW)). In yet other aspects the connection to the user plane is at the Si-U reference point (to a radio access network node, such as an evolved Node B). That is, according to an embodiment the core network entity 200 is operatively connected to the user plane function entity via an N6 interface or reference point, or an N3 interface or reference point, or an SGi interface or reference point, or an Si-U interface or reference point.
  • the core network entity 200 is connected to the control plane at the so-called N23 reference point. That is, according to an embodiment the core network entity 200 is operatively connected to the control plane function entity via an N23 interface or reference point.
  • the downlink data packet is sent towards the selected function entity by using evolved packet core (EPC) NIDD.
  • EPC evolved packet core
  • NIDD is used on the N23 interface or reference point.
  • the user plane is using the 5G Point-to-Point tunneling of Unstructured PDU session type on the N6 reference point (as defined in clause 5.6.10.3 of 3GPP TS 23.501 with changes applied as disclosed above). That is, according to an embodiment, Point-to-Point tunneling of PDU session type Unstructured is used on the N6 interface or reference point.
  • the IP-over-IP tunneling is used for IP based data. That is, according to an embodiment, IP-over-IP tunneling is used for IP based data on the N6 interface or reference point.
  • the user plane is using the 5G PDU session types Unstructured on the N3 reference point (as defined in in clause 5.6.1 of 3GPP TS 23.501. That is, according to an embodiment, PDU session type Unstructured is used on the N3 interface or reference point.
  • the user plane is using the EPC NIDD SGi based delivery. That is, according to an embodiment, NIDD is used on the SGi interface or reference point.
  • IP-over-IP tunneling is used for IP based data. That is, according to an embodiment, IP-over-IP tunneling is used for IP based data on the SGi interface or reference point.
  • the user plane is using the Si-U reference point (as defined in clause 4.2 of 3GPP TS 23.401) based on the GTP-U protocol tunneling (as defined in 3GPP TS 29.281). That is, according to an embodiment, GTP-U protocol tunneling is used on the Si-U interface or reference point.
  • the user plane is using any of the 5G PDU session types IPv4 or IPv6 or Ethernet (as defined in clause 5.6.1 of 3GPP TS 23.501). That is, according to an embodiment, a PDU session of type IPv4, IPv6, or Ethernet is used when sending data packets to, and receiving data packets from, the user plane function entity.
  • the user plane is using the PDN Type IPv4 or IPv6 or
  • IPv4lPv6 (as defined in clause 5.3.1 of 3GPP TS 23.401) based on the GTP-U protocol tunneling (as defined in 3GPP TS 29.281). That is, according to an embodiment, PDN Type IPv4, IPv6, or IPv4lPv6 based on GTP-U protocol tunneling is used when sending data packets to, and receiving data packets from, the user plane function entity.
  • the core network entity 200 provides Internet of Things services offered by the operator to external IoT service providers, external application servers (AS), external Service Capability Servers (SCS) or external IoT or Cellular IoT end users.
  • These services comprise T8 NIDD procedures (also known as T8 NIDD API, see 3GPP TS 29.122), a Mobile Terminated NIDD procedure, and a Mobile Originated NIDD procedure.
  • the core network entity 200 provides Internet of Things services offered by the operator to external IoT service providers, external ASs, external Service SCSs or external IoT end users. These services comprise vendor specific APIs for external IoT entities such as AppIoT services.
  • the core network entity 200 may also provide its service using other standardized or proprietary APIs or interface protocols.
  • southbound i.e. from the core network entity 200 in downlink direction
  • the core network entity 200 may terminate a PtP tunnel for Unstructured PDU type data (see clause 5.6.10.3 3GPP TS 23.501). The PtP tunnel is established between UPF(s) and the core network entity 200.
  • the UPF acts as a transparent forwarding node for the payload between the device and the core network entity 200.
  • the core network entity 200 forwards data to/from external AS/SCS using an API e.g. the T8 NIDD API, vendor specific API (e.g.
  • the core network entity 200 may terminate a T6a interface towards MME(s) for NIDD procedures (see, 3GPP TS 23.682) which comprises a Mobile Terminated NIDD procedure, and a Mobile Originated NIDD procedure.
  • the core network entity 200 may use the N6 interface towards the UPF to convey IPv4 data, IPv6 data, Ethernet Type data or Unstructured PDU type data to and from the device.
  • the core network entity 200 may translate or convert the data and convey the data to/from external AS/SCS using an API e.g. the T8 NIDD API, vendor specific API (e.g. AppIoT), or other standardized or proprietary API or protocol.
  • an API e.g. the T8 NIDD API, vendor specific API (e.g. AppIoT), or other standardized or proprietary API or protocol.
  • the core network entity 200 may provide services using an Open Mobile Alliance (OMA) Lightweight machine two machine (M2M) Server.
  • OMA Open Mobile Alliance
  • M2M Lightweight machine two machine
  • LWM2M lightweight machine to machine
  • the OMA lightweight machine to machine (LWM2M) protocol might then be used to communicate using any of the above mechanisms for southbound non-IP data and IP data with an OMA LWM2M client implemented in the device.
  • the core network entity 200 might use any of the above disclosed mechanisms for northbound services (NIDD services or APPIoT services) to offer IoT services to external entities, such as SCSs and/or ASs.
  • NIDD services or APPIoT services are a wireless low power long range technology.
  • the core network entity 200 might provide services using a LoRA Network Server.
  • the LoRA Network Server uses LoRA specific protocols to communicate with LoRA Clients in LoRA devices.
  • the core network entity 200 might use any of the above disclosed mechanisms for northbound services (NIDD services or APPIoT services) to offer IoT services to external entities, such as SCSs and/or ASs.
  • the core network entity 200 may provide protocol proxying services.
  • the proxy service may for example be a 6L0WPAN proxy i.e., a 6L0WPAN protocol on the southbound interface using any of the above mechanisms for southbound non-IP data and IP data is translated to an IPv6 protocol on the northbound interface.
  • the core network entity 200 may provide Application Layer Gateway (ALG) services.
  • ALG Application Layer Gateway
  • the ALG service generally translates from one application protocol on the southbound interface using any of the above mechanisms for southbound non-IP data and IP data to another application protocol on the northbound interface using e.g. IPv4, IPv6 or Ethernet protocol on the northbound interface.
  • the core network entity 200 supports at least the following functionality.
  • the core network entity 200 might implement the T8 NIDD API as specified in 3GPP TS 29.122.
  • the core network entity 200 might implement small data transmission (small data messaging) towards the device, which allows for transmission of Unstructured PDU session type data, transmission of PDN Type Non-IP data in a 4G telecommunications system, transmission of PDU session type data IPv4, IPv6, or Ethernet, and/or transmission of PDN Type PDN Type IPv4 or IPv6 or IPv4lPv6 in a 4G telecommunications system.
  • the core network entity 200 might implement a mapping or proxying between T8 NIDD API and the small data transmission. That is, the core network entity 200 might implement bidirectional forwarding of data according to the protocol options on the downlink interfaces of the data transmission and the protocol options on the uplink interfaces of the T8 NIDD API.
  • Fig. 6 schematically illustrates, in terms of a number of functional units, the components of a core network entity 200 according to an embodiment.
  • Processing circuitry 210 is provided using any combination of one or more of a suitable central processing unit (CPU), multiprocessor, microcontroller, digital signal processor (DSP), etc., capable of executing software instructions stored in a computer program product 810 (as in Fig. 8), e.g. in the form of a storage medium 230.
  • the processing circuitry 210 may further be provided as at least one application specific integrated circuit (ASIC), or field
  • FPGA programmable gate array
  • the processing circuitry 210 is configured to cause the core network entity 200 to perform a set of operations, or steps, S102-S114, as disclosed above.
  • the storage medium 230 may store the set of operations
  • the processing circuitry 210 may be configured to retrieve the set of operations from the storage medium 230 to cause the core network entity 200 to perform the set of operations.
  • the set of operations may be provided as a set of executable instructions.
  • the processing circuitry 210 is thereby arranged to execute methods as herein disclosed.
  • the storage medium 230 may also comprise persistent storage, which, for example, can be any single one or combination of magnetic memory, optical memory, solid state memory or even remotely mounted memory.
  • the core network entity 200 may further comprise a communications interface 220 at least configured for communications with other entities, functions, nodes, and devices. As such the communications interface 220 may comprise one or more transmitters and receivers, comprising analogue and digital components.
  • the processing circuitry 210 controls the general operation of the core network entity 200 e.g. by sending data and control signals to the communications interface 220 and the storage medium 230, by receiving data and reports from the communications interface 220, and by retrieving data and instructions from the storage l8 medium 230.
  • Other components, as well as the related functionality, of the core network entity 200 are omitted in order not to obscure the concepts presented herein.
  • Fig. 7 schematically illustrates, in terms of a number of functional modules, the components of a core network entity 200 according to an embodiment.
  • the core network entity 200 of Fig. 7 comprises a number of functional modules; a receive module 210a configured to perform step S102, a determine module 210b configured to perform step S104, and a send module 2iod configured to perform step S108.
  • the core network entity 200 of Fig. 7 may further comprise a number of optional functional modules, such as any of a determine module 210c configured to perform step S106, a receive module 2ioe configured to perform step S110, a determine module 2iof configured to perform step S112, and a send module 2iog configured to perform step S114.
  • each functional module 2ioa-2iog may in one embodiment be implemented only in hardware and in another embodiment with the help of software, i.e., the latter embodiment having computer program instructions stored on the storage medium 230 which when run on the processing circuitry makes the core network entity 200 perform the corresponding steps mentioned above in conjunction with Fig 7. It should also be mentioned that even though the modules correspond to parts of a computer program, they do not need to be separate modules therein, but the way in which they are implemented in software is dependent on the programming language used.
  • one or more or all functional modules 2ioa-2iog may be implemented by the processing circuitry 210, possibly in cooperation with the communications interface 220 and/or the storage medium 230.
  • the processing circuitry 210 may thus be configured to from the storage medium 230 fetch instructions as provided by a functional module 2ioa-2iog and to execute these instructions, thereby performing any steps as disclosed herein.
  • a functional module 2ioa-2iog There may be different ways to provide the core network entity 200. Different embodiments relating thereto will now be disclosed.
  • the core network entity 200 may be provided as a standalone device or as a part of at least one further device.
  • the core network entity 200 is a separate entity as in Figs. 3 or 4. Thus, according to an embodiment, the core network entity 200 is provided as a separate entity in the core network. In some aspects the core network entity 200 is part of a 5GC NEF (as defined in 3GPP TS 23.501). In some aspects the core network entity 200 is part of a SCEF (as defined in 3GPP TS 23.682). In some aspects the core network entity 200 is part of a 5GC UPF (as defined in 3GPP TS 23.501). In some aspects the core network entity 200 is part of a PDN GW (as defined in 3GPP TS 23.401). That is, according to an embodiment, the core network entity 200 is collocated with or an integral part of, another entity in the core network, such as any of: a NEF entity, a SCEF entity, a UPF entity, and a PDN GW entity.
  • a first portion of the instructions performed by the core network entity 200 may be executed in a first device, and a second portion of the of the instructions performed by the core network entity 200 may be executed in a second device; the herein disclosed embodiments are not limited to any particular number of devices on which the instructions performed by the core network entity 200 may be executed.
  • the methods according to the herein disclosed embodiments are suitable to be performed by a core network entity 200 residing in a cloud computational environment. Therefore, although a single processing circuitry 210 is illustrated in Fig. 6 the processing circuitry 210 may be distributed among a plurality of devices, or nodes. The same applies to the functional modules 2ioa-2iog of Fig. 7 and the computer program 820 of Fig. 8.
  • Fig. 8 shows one example of a computer program product 810 comprising computer readable storage medium 830.
  • a computer program 820 can be stored, which computer program 820 can cause the processing circuitry 210 and thereto operatively coupled entities and devices, such as the communications interface 220 and the storage medium 230, to execute methods according to embodiments described herein.
  • the computer program 820 and/or computer program product 810 may thus provide means for performing any steps as herein disclosed.
  • the computer program product 810 is illustrated as an optical disc, such as a CD (compact disc) or a DVD (digital versatile disc) or a Blu-Ray disc.
  • the computer program product 810 could also be embodied as a memory, such as a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM), or an electrically erasable programmable read-only memory (EEPROM) and more particularly as a non-volatile storage medium of a device in an external memory such as a USB (Universal Serial Bus) memory or a Flash memory, such as a compact Flash memory.
  • the computer program 820 is here schematically shown as a track on the depicted optical disk, the computer program 820 can be stored in any way which is suitable for the computer program product 810.

Abstract

L'invention concerne des mécanismes destinés à la gestion de paquets dans un réseau central. Un procédé est exécuté par une entité de réseau central. Le procédé consiste à recevoir un paquet de données de liaison descendante provenant d'un réseau de données et destiné à un dispositif. Le procédé consiste à déterminer, sur la base d'au moins une propriété de réseau associée au paquet de données de liaison descendante, s'il faut transférer le paquet de données de liaison descendante vers une entité de fonction de plan utilisateur ou vers une entité de fonction de plan de commande. Le procédé consiste à envoyer le paquet de données de liaison descendante vers l'entité de fonction sélectionnée.
PCT/EP2017/074186 2017-09-25 2017-09-25 Gestion de paquets de données dans un réseau central WO2019057307A1 (fr)

Priority Applications (1)

Application Number Priority Date Filing Date Title
PCT/EP2017/074186 WO2019057307A1 (fr) 2017-09-25 2017-09-25 Gestion de paquets de données dans un réseau central

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/EP2017/074186 WO2019057307A1 (fr) 2017-09-25 2017-09-25 Gestion de paquets de données dans un réseau central

Publications (1)

Publication Number Publication Date
WO2019057307A1 true WO2019057307A1 (fr) 2019-03-28

Family

ID=59974420

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/EP2017/074186 WO2019057307A1 (fr) 2017-09-25 2017-09-25 Gestion de paquets de données dans un réseau central

Country Status (1)

Country Link
WO (1) WO2019057307A1 (fr)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2021049871A1 (fr) * 2019-09-09 2021-03-18 Samsung Electronics Co., Ltd. Procédé d'établissement de canal, station de base et entité de coordination de multidiffusion multi-cellules, mce

Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP2509345A1 (fr) * 2011-04-05 2012-10-10 Panasonic Corporation Transmissions améliorées de petites données pour dispositifs de communication de type machine
WO2017141749A1 (fr) * 2016-02-17 2017-08-24 Nec Corporation Sélection d'un plan de commande et d'un plan d'utilisateur pour la transmission de données

Patent Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP2509345A1 (fr) * 2011-04-05 2012-10-10 Panasonic Corporation Transmissions améliorées de petites données pour dispositifs de communication de type machine
WO2017141749A1 (fr) * 2016-02-17 2017-08-24 Nec Corporation Sélection d'un plan de commande et d'un plan d'utilisateur pour la transmission de données

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2021049871A1 (fr) * 2019-09-09 2021-03-18 Samsung Electronics Co., Ltd. Procédé d'établissement de canal, station de base et entité de coordination de multidiffusion multi-cellules, mce

Similar Documents

Publication Publication Date Title
US11388776B2 (en) Control plane cellular internet-of-things (IoT) optimization indication
US10462828B2 (en) Policy and billing services in a cloud-based access solution for enterprise deployments
US10581747B2 (en) System and method for low-overhead interoperability between 4G and 5G networks
CN109314839B (zh) 服务层的业务导向
US9674746B2 (en) Application service platform with access to context data of remote access node
CN109792788A (zh) 用于在无线通信网络中涉及隧道的数据传输的方法和设备
WO2021000827A1 (fr) Procédé et appareil d'établissement de liaison de transmission de données, et support de stockage lisible par ordinateur
KR102567828B1 (ko) 사용자 장비에서 공급된 구성 파라미터들의 안전한 업데이트를 위한 시스템 및 방법
US10645613B2 (en) Method and apparatus for generating packet in mobile communication system
US11811650B2 (en) Systems and methods for user plane function (“UPF”) offload at configurable routing fabric
JP2021158664A (ja) 間接通信用のエラー処理のための方法、装置、およびコンピュータプログラム製品
WO2015120480A1 (fr) Extension de connectivité dans un système de communication machine à machine
US20230147409A1 (en) Apparatus and method for network automation in wireless communication system
CN111937365A (zh) 重定向处置
US11622025B2 (en) Techniques in retrieving cached content using information centric networking for protocol data unit sessions
WO2018167254A1 (fr) Plages uniques de marquage qos pour smf dans un réseau de communication 5g
EP4038846A1 (fr) Activation dynamique d'accès local lbo avec coordination entre domaine d'application et réseau mobile
WO2019057307A1 (fr) Gestion de paquets de données dans un réseau central
CN112449377A (zh) 一种网络数据的上报方法及装置
EP4301083A1 (fr) Procédé et dispositif de gestion de sessions sur la base d'informations de liaison d'amenée dans un système de communication sans fil
US20240073302A1 (en) Data Unit in Wireless System
US20240064494A1 (en) Systems and methods for device triggering for 5g devices
KR20200019072A (ko) 5G 네트워크에서 non-IP 데이터 전송 방법

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

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 17776994

Country of ref document: EP

Kind code of ref document: A1