WO2020225684A1 - Mise en oeuvre d'espace de service dans des réseaux de communication sans fil - Google Patents

Mise en oeuvre d'espace de service dans des réseaux de communication sans fil Download PDF

Info

Publication number
WO2020225684A1
WO2020225684A1 PCT/IB2020/054143 IB2020054143W WO2020225684A1 WO 2020225684 A1 WO2020225684 A1 WO 2020225684A1 IB 2020054143 W IB2020054143 W IB 2020054143W WO 2020225684 A1 WO2020225684 A1 WO 2020225684A1
Authority
WO
WIPO (PCT)
Prior art keywords
network node
payload container
wireless device
core network
message
Prior art date
Application number
PCT/IB2020/054143
Other languages
English (en)
Inventor
Kaj Johansson
Mikael Wass
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)
Publication of WO2020225684A1 publication Critical patent/WO2020225684A1/fr

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W48/00—Access restriction; Network selection; Access point selection
    • H04W48/02—Access restriction performed under specific conditions
    • H04W48/06—Access restriction performed under specific conditions based on traffic conditions
    • 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

  • the present description generally relates to wireless communications and wireless communication networks, and more particularly relates to signaling restriction management in wireless communication networks.
  • SGC service gap control
  • EPS Evolved Packet System
  • 5GS 5G System
  • the Mobility Management Entity may apply restrictions to signaling initiated by the UE when not allowed according to service gap limits.
  • Service Gap Control is modelled as a function in EPS Mobility Management where the logic is specified in the Mobility Management sublayer and related signaling is performed in the NAS EPS Mobility Management protocol layer.
  • the prevention of MO signaling and data transmissions is performed either by restricting Mobility Management procedures, or by preventing the UE to enter CM-CONNECTED mode where MO signaling and data transmissions can be performed without possibility to restrict or control in the Mobility Management layer.
  • the UE is not allowed to initiate MO signaling and data transmissions when a service gap timer, provided by the network to the UE and started upon the UE transitioning from the CM-CONNECTED mode to the CM-IDLE mode transition, is running in the UE.
  • the exceptions to this restriction are that the UE is allowed to perform tracking area updating and connectivity requests when needed for priority and emergency services.
  • These procedures belong to the Mobility Management sublayer and can be supervised for restrictions by the MME Mobility Management function.
  • the UE can attach to the network without packet data network (PDN) connectivity.
  • PDN packet data network
  • the UE will enter CM-CONNECTED mode and it will not be possible for Service Gap Control to supervise and restrict any MO signaling and data transmissions performed in a different layer than Mobility Management, e.g. EPS Session Management.
  • Mobility Management e.g. EPS Session Management
  • the Non-Access Stratum (NAS) protocol is designed in a slightly different manner.
  • signaling of 5GS NAS Session Management is not fully transparent to 5GS NAS Mobility Management in the AMF, but carried as containers in NAS Transport 5G Mobility Management (5GMM) messages.
  • Information in the 5GMM message indicates what type of data/message is included in the container.
  • SMS and LCS messages the same principle applies for other types of AMF routed data/messages, e.g. SMS and LCS messages.
  • Service Gap Control can evaluate any signaling and data routed via the AMF in NAS transport messages by checking other information in the message to determine the contents of the 5GMM transparent container and if not allowed according to Service Gap restrictions, take appropriate action.
  • a specific reject/notification at restricted forwarding due to Service Gap Control by specification of a cause value sent to the UE in a Downlink NAS Transport message.
  • a supporting UE can act on the provided reject/notification to avoid further attempts that will fail due to Service Gap Control.
  • the AMF can reject with a general 5GMM back-off timer or apply other measurements to stop/minimize impact from non-compliant or non-supporting UEs.
  • some embodiments include a method performed by a core network node.
  • the method generally comprises receiving an uplink message from a wireless device, the uplink message comprising a payload container to be forwarded toward a destination network node, obtaining information about a content of the payload container, determining that a service restriction for the wireless device is active, and upon determining that the service restriction for the wireless device is active, determining whether to forward the payload container toward the destination network node based, at least in part, on the information about the content of the payload container.
  • Determining that the service restriction for the wireless device is active may comprise determining that a service restriction timer associated with the wireless device is running.
  • the method may comprise, upon determining to forward the payload container toward the destination network node based, at least in part, on the information about the content of the payload container, forwarding the payload container toward the destination network node.
  • the method may comprise, upon determining to refrain from forwarding the payload container toward the destination network node based, at least in part, on the information about the content of the payload container, sending a downlink message to the wireless device, the downlink message comprising an information element indicating that the payload container was not forwarded toward the destination network node.
  • the information element indicating that the payload container was not forwarded toward the destination network node may comprise a value indicating congestion, a value indicating that the payload container was not forwarded toward the destination network node, a value indicating that service restriction for the wireless device is active, or a value indicating that the payload container was not forwarded toward the destination network node because service restriction for the wireless device is active.
  • the downlink message may comprise, or further comprise, a back-off timer value.
  • the back-off timer value may indicate to the wireless device for how long the wireless device should refrain from transmitting further uplink messages (e.g., further uplink messages comprising payload container to be forwarded toward a destination network node).
  • the downlink message may comprise, or further comprise, the payload container.
  • the information about the content of the payload container may comprise at least one of a payload container type, a request type, an identifier of a network slice, and an identifier of a data network.
  • the uplink message may be an uplink non-access stratum (NAS) transport message.
  • the downlink message may be a downlink NAS transport message.
  • the core network node may be a network node implementing an Access and Mobility Management Function (AMF).
  • AMF Access and Mobility Management Function
  • some embodiments include a core network node adapted, configured, enabled, or otherwise operable, to perform one or more of the described core network node functionalities (e.g. actions, operations, steps, etc.).
  • the core network node may comprise one or more communication interfaces and processing circuitry operatively connected to the one or more communication interfaces.
  • the one or more communication interfaces are configured to enable the core network node to communicate with one or more other core network nodes (e.g., via a core network communication interface), with one or more radio network nodes (e.g., via a radio access network communication interface), and/or with one or more other network nodes.
  • the processing circuitry is configured to enable the core network node to perform one or more of the described core network node functionalities.
  • the processing circuitry may comprise at least one processor and at least one memory, the memory storing instructions which, upon being executed by the processor, enable the core network node to perform one or more of the described core network node functionalities.
  • some embodiments include a computer program product.
  • the computer program product comprises computer-readable instructions stored in a non-transitory computer-readable storage medium of the computer program product.
  • processing circuitry e.g., at least one processor
  • the core network node When the instructions are executed by processing circuitry (e.g., at least one processor) of a core network node, they enable the core network node to perform one or more of the described core network node functionalities.
  • some embodiments include a method performed by a wireless device.
  • the method generally comprises sending an uplink message to a core network node, the uplink message comprising a payload container to be forwarded toward a destination network node, and receiving a downlink message from the core network node, the downlink message comprising an information element indicating that the payload container was not forwarded toward the destination network node.
  • the information element indicating that the payload container was not forwarded toward the destination network node may comprise a value indicating congestion, a value indicating that the payload container was not forwarded toward the destination network node, a value indicating that service restriction for the wireless device is active, or a value indicating that the payload container was not forwarded toward the destination network node because service restriction for the wireless device is active.
  • the downlink message may comprise, or further comprise, a back-off timer value.
  • the back-off timer value may indicate to the wireless device for how long the wireless device should refrain from transmitting further uplink messages (e.g., further uplink messages comprising payload container to be forwarded toward a destination network node).
  • the downlink message may comprise, or further comprise, the payload container.
  • the uplink message may be an uplink NAS transport message.
  • the downlink message may be a downlink NAS transport message.
  • the core network node may be a network node implementing an AMF.
  • some embodiments include a wireless device adapted, configured, enabled, or otherwise operable, to perform one or more of the described wireless device functionalities (e.g. actions, operations, steps, etc.).
  • the wireless device may comprise one or more transceivers and processing circuitry operatively connected to the one or more transceivers.
  • the one or more transceivers are configured to enable the wireless device to communicate with one or more radio network nodes over a radio interface.
  • the processing circuitry is configured to enable the wireless device to perform one or more of the described wireless device functionalities.
  • the processing circuitry may comprise at least one processor and at least one memory, the memory storing instructions which, upon being executed by the processor, enable the wireless device to perform one or more of the described wireless device functionalities.
  • some embodiments include a computer program product.
  • the computer program product comprises computer-readable instructions stored in a non-transitory computer-readable storage medium of the computer program product.
  • processing circuitry e.g., at least one processor
  • they enable the wireless device to perform one or more of the described wireless device functionalities.
  • Figure 1 is a simplified schematic diagram of the Non-Access Stratum (NAS) protocol stack according the Evolved Packet Core (EPC) architecture.
  • NAS Non-Access Stratum
  • EPC Evolved Packet Core
  • FIG. 2 is a simplified schematic diagram of the Non-Access Stratum (NAS) protocol stack according the 5G Core (5GC) architecture.
  • NAS Non-Access Stratum
  • 5GC 5G Core
  • Figure 3 is a schematic diagram of an example wireless communication network according to some embodiments.
  • Figure 4 is a schematic diagram of a portion of an example wireless communication network showing example signaling according to some embodiments.
  • Figure 5 is a schematic diagram of a portion of an example wireless communication network showing example core network nodes and related interfaces according to the 5GC architecture.
  • Figure 6 is a signaling and operating diagram according to some embodiments.
  • Figure 7 is a flow chart of operations of a wireless device according to some embodiments.
  • Figure 8 is a flow chart of operations of a core network node according to some embodiments.
  • Figure 9 is a block diagram of a wireless device according to some embodiments.
  • Figure 10 is a block diagram of a core network node according to some embodiments.
  • Figure 11 is another block diagram of a core network node according to some embodiments. DETAILED DESCRIPTION
  • the wireless communication network 100 generally enables wireless devices 110 to communicate with one or more external networks 400 via a radio access network 200 (also referred to as RAN) and a core network 300 (also referred to as CN).
  • RAN radio access network 200
  • CN core network 300
  • the radio access network 200 generally comprises a plurality of radio network nodes 210 (only two are shown for clarity) which are responsible for providing radio access, over a radio interface, to wireless devices 110 (only two are shown for clarity) via one or more cells 205.
  • Each cell 205 generally defines a geographical area associated to, and served by, a radio network node 210 where radio coverage is provided by the radio network node 210.
  • one radio network node 210 may serve more than one cell 205, each of these cells possibly covering different geographical areas.
  • the core network 300 which connects the radio access network 200 to one or more external networks 400, generally comprises various core network nodes 310. Though generically referred to as core network nodes 310, different core network nodes 310 may implement or host different core network entities, these different core network entities being responsible for providing one or more core network functions. Examples of core network functions include, but are not limited to, access management, address allocation, connectivity management, lawful interception, mobility management, packet marking, packet inspection, policy control, session management, etc.
  • a core network node 310 implementing a specific core network entity may be referred to by its specific name (e.g., an AMF 310).
  • AMF Access and Mobility Management Function
  • FIG. 4 additional details of the radio interface between a wireless device 110 and a radio network node 210 are shown. As illustrated, the radio interface generally enables the wireless device 110 and the radio network node 210 to exchange signals and messages in both a downlink direction, that is from the radio network node 210 to the wireless device 110, and in an uplink direction, that is from the wireless device 110 to the radio network node 210.
  • the radio interface between the wireless device 110 and the radio network node 210 typically enables the wireless device 110 to access various applications or services provided by one or more servers 410 (also referred to as application server or host computer) located in the external network(s) 400.
  • the connectivity between the wireless device 110 and the server 410, enabled at least in part by the radio interface between the wireless device 110 and the radio network node 210, may be described as an over-the-top (OTT) or application layer connection.
  • OTT over-the-top
  • the wireless device 110 and the server 410 are configured to exchange data and/or signaling via the OTT connection, using the radio access network 200, the core network 300, and possibly one or more intermediate networks (e.g., a transport network) (not shown).
  • the OTT connection may be transparent in the sense that the participating communication devices or nodes (e.g., the radio network node, one or more core network nodes, etc.) through which the OTT connection passes may be unaware of the actual OTT connection they enable and support.
  • the radio network node 210 may not or need not be informed about the previous handling (e.g., routing) of an incoming downlink communication with data originating from the server 410 to be forwarded or transmitted to the wireless device 110.
  • the radio network node 210 may not or need not be aware of the subsequent handling of an outgoing uplink communication originating from the wireless device 110 towards the server 410.
  • a core network 300 according to the 5GC network architecture comprises an Access and Mobility Management Function (AMF) connected to the wireless device 110 via the N 1 interface and to the RAN 200 via the N2 interface.
  • AMF Access and Mobility Management Function
  • the AMF 310 is also connected to a Session Management Function (SMF) 310 via a service-based architecture.
  • SMF Session Management Function
  • the SMF 310 is also connected to the User Plane Function (UPF) via the N4 interface.
  • the UPF is connected to the RAN 200 via the N3 interface and to the external network 400 via the N6 interface.
  • the UPF is part of the user plane while the AMF and SMF are part of the control plane. More details about the functions of the AMF, SMF and UPF can be found in section 6.2 of 3GPP TS 23.501 V16.0.2.
  • Service Gap Control is active for a Rel-16 UE and the service gap timer is running in the UE and the AMF
  • the UE is allowed to perform initial registration or mobility update registrations. This also applies to Rel-15 UEs that do not support Service Gap Control and hence do not maintain any service gap control timer.
  • the AMF still maintain service gap timers for those Rel-15 UEs.
  • Figure 6 illustrates a high-level signaling and operating diagram according to some embodiments.
  • a NAS signaling connection is established between a wireless device 110 (also referred to as a UE) and an AMF 310 (action S102).
  • a Service Gap timer e.g., timer T3547 or another timer used or reused for that purpose
  • the wireless device 110 should not originate signaling while the Service Gap timer is running.
  • the established NAS signaling connection between the wireless device 110 and the AMF 310 could be used by the wireless device which does not support Service Gap Control (e.g., a Rel-15 wireless device) or could be misused by a wireless device 110 which supports Service Gap Control (e.g., a Rel-16 wireless device) to send a MO 5GSM message, a MO SMS payload, or a MO FPP message piggybacked in an unacknowledged 5GMM message (UE NAS TRANSPORT message), which is not allowed unless there has been downlink signaling sent on the current NAS signaling connection (action SI 04).
  • Service Gap Control e.g., a Rel-15 wireless device
  • Service Gap Control e.g., a Rel-16 wireless device
  • the AMF 310 determines that Service Gap Control is active for the wireless device 110 (action SI 06).
  • the AMF 310 also obtains information about the content of the payload container carried by the UE NAS Transport message (action SI 08).
  • the AMF 310 may read or otherwise decode the Payload Container Type information element to obtain information about the content of the payload container.
  • the Payload Container Type information element present in the UE NAS Transport message indicates what type of content is present in the payload container.
  • the AMF 310 may obtain additional information about the content of the payload container by reading other information elements such as, but not limited to, the Request Type information element which may indicate, for example, whether the payload container is related to an emergency session.
  • the AMF 310 determines whether to forward the content of the payload container toward the appropriate destination network node or to refrain from forwarding the payload container (action SI 10).
  • the AMF 310 may reject the UL NAS Transport message by sending a DL NAS Transport message back to the wireless device 110 (action S112A).
  • the DL NAS Transport message may comprise an information element indicating that the payload container has not been forwarded toward the destination network node.
  • this information element may be a cause information element comprising a value indicating, to the wireless device, why the payload container has not been forwarded toward the destination network node.
  • the value may indicate: 1) congestion, 2) that the payload container was not forwarded toward the destination network node, 3) that Service Gap Control for the wireless device is active, or 4) that the payload container was not forwarded toward the destination network node because Service Gap Control for the wireless device is active.
  • the DL NAS Transport message may also comprise a back-off timer value which may indicate to the wireless device 110 for how long the wireless device 110 should refrain from transmitting further uplink messages.
  • the DL NAS Transport message may also comprise the original payload container.
  • the content of the DL NAS Transport message sent to the wireless device 110 by the AMF 310 may vary depending on whether the originating wireless device 110 is a wireless device 110 which does not support Service Gap Control (e.g., a Rel-15 wireless device) or is a wireless device 110 which supports Service Gap Control (e.g., a Rel-16 wireless device).
  • Service Gap Control e.g., a Rel-15 wireless device
  • Service Gap Control e.g., a Rel-16 wireless device
  • the AMF 310 may send a DL NAS Transport message in which the cause information element (referred to as 5GMM cause in section 8.2.11 of 3GPP TS 24.501 V16.0.2) indicates, e.g.,“Congestion” or“Payload was not forwarded”, and in which the back-off timer value indicates the remaining value of the Service Gap timer running at the AMF 310.
  • the cause information element referred to as 5GMM cause in section 8.2.11 of 3GPP TS 24.501 V16.0.2
  • the back-off timer value indicates the remaining value of the Service Gap timer running at the AMF 310.
  • the AMF 310 may send a DL NAS Transport message in which the cause information element indicates, e.g.,“Service Gap Control” or“Payload was not forwarded due to Service Gap Control” and in which the back-off timer value indicates the remaining value of the Service Gap timer running at the AMF 310. Understandably, the exact label of the cause encoded in the cause information element may vary. Notably, the AMF 310 can learn whether the wireless device 110 supports the Service Gap Control during the registration procedure (see section 4.2.2.2 of 3GPP TS 23.502 V16.0.2).
  • the AMF 310 forwards the payload container toward the destination network node using the appropriate message(s) and interface(s) (action SI 12B).
  • different payload container may be destined to different destination network node.
  • the destination network node may be an SMF 310 as shown in Figure 6.
  • the payload container carries a Short Message Service message, that is an SMS
  • the destination network node may be a Short Message Service Function (SMSF) (not shown).
  • SMSF Short Message Service Function
  • UFP UTE Positioning Protocol
  • GMUC Gateway Mobile Uocation Centre
  • Figure 7 is a flow chart illustrating a sequence of operations of the wireless device 110 according to some embodiments. Optional operations, if any, are indicated by dashed lines.
  • the wireless device 110 may initially establish a NAS signaling connection with a core network node 310 (e.g., an AMF) (action S202).
  • a core network node 310 e.g., an AMF
  • the wireless device 110 then sends an uplink message (e.g., an UU NAS Transport message) to the core network node 310, the uplink message comprising a payload container to be forwarded toward a destination network node (e.g., an SMF, an SMSF, a GMUC, etc.) (action S204).
  • an uplink message e.g., an UU NAS Transport message
  • the uplink message comprising a payload container to be forwarded toward a destination network node (e.g., an SMF, an SMSF, a GMUC, etc.)
  • a destination network node e.g., an SMF, an SMSF, a GMUC, etc.
  • the wireless device 110 receives a downlink message (e.g., a DU NAS Transport message) from the core network node 310 (action S206).
  • the downlink message comprises an information element indicating that the payload container was not forwarded toward the destination network node.
  • this information element may be a cause information element comprising a value indicating, to the wireless device 110, why the payload container has not been forwarded toward the destination network node.
  • the value may indicate: 1) congestion, 2) that the payload container was not forwarded toward the destination network node, 3) that Service Gap Control for the wireless device is active, or 4) that the payload container was not forwarded toward the destination network node because Service Gap Control for the wireless device is active.
  • the downlink message may also comprise a back-off timer value .
  • the back-off timer value may indicate to the wireless device 110 for how long the wireless device should refrain from transmitting further uplink messages (e.g., further uplink messages comprising a payload container to be forwarded toward a destination network node).
  • the downlink message may also comprise the original payload container.
  • the wireless device 110 may refrain from sending further uplink messages to the core network node (action S208).
  • the wireless device 110 may refrain from sending further uplink messages based, at least in part, on the content of the information element indicating that the payload container was not forwarded toward the destination network node, on the content of the back-off timer value information element, or on both.
  • Figure 8 is a flow chart illustrating a sequence of operations of a core network node 310 (e.g., an AMF) according to some embodiments. Optional operations, if any, are indicated by dashed lines.
  • a core network node 310 e.g., an AMF
  • the core network node 310 may initially establish a NAS signaling connection with a wireless device 110 (action S302).
  • a service restriction timer e.g., a Service Gap timer
  • a corresponding service restriction timer may or may not be running at the wireless device 110.
  • the core network node 310 then receives an uplink message (e.g., an UL NAS Transport message) from the wireless device 110, the uplink message comprising a payload container to be forwarded toward a destination network node (e.g., an SMF, an SMSF, a GMLC, etc.) (action S304).
  • an uplink message e.g., an UL NAS Transport message
  • the uplink message comprising a payload container to be forwarded toward a destination network node (e.g., an SMF, an SMSF, a GMLC, etc.) (action S304).
  • a destination network node e.g., an SMF, an SMSF, a GMLC, etc.
  • the core network node 310 determines that service restriction for the wireless device 110 is active (actions S306). In some embodiments, the core network node 310 may determine that service restriction for the wireless device 110 is active by determining that the service restriction timer for the wireless device 110 is running.
  • the core network node 310 also obtains information about the content of the payload container carried by the uplink message (action S308). As indicated above, the core network node 310 may read or otherwise decode one or more information elements present in the uplink message to obtain information about the content of the payload container. In embodiments where the uplink message is an UL NAS Transport message, the core network node 310 may read the Payload Container Type information element to obtain information about the content of the payload container. As per section 9.11.3.40 of 3GPP TS 24.501 V16.0.2, the Payload Container Type information element present in the UL NAS Transport message indicates what type of content is present in the payload container. The core network node 310 may obtain additional information about the content of the payload container by reading other information elements such as, but not limited to, the Request Type information element which may indicate, for example, whether the payload container is related to an emergency session.
  • the Request Type information element which may indicate, for example, whether the payload container is related to an emergency session.
  • the core network node 310 determines whether to forward the payload container toward the destination network node based, at least in part, on the information about the content of the payload container (action S310).
  • the core network node 310 determines to refrain from forwarding the payload container toward the destination network nodes, then the core network node 310 rejects the uplink message by sending a downlink message to the wireless device 110, the downlink message comprising an information element indicating that the payload container was not forwarded toward the destination network node (action S312A).
  • this information element may be a cause information element comprising a value indicating, to the wireless device 110, why the payload container has not been forwarded toward the destination network node.
  • the value may indicate: 1) congestion, 2) that the payload container was not forwarded toward the destination network node, 3) that Service Gap Control for the wireless device is active, or 4) that the payload container was not forwarded toward the destination network node because Service Gap Control for the wireless device is active.
  • the downlink message may also comprise a back-off timer value which may indicate to the wireless device 110 for how long the wireless device should refrain from transmitting further uplink messages.
  • the downlink message may also comprise the original payload container.
  • the core network node 310 determines to forward the payload container toward the destination network nodes, then the core network node 310 forwards the payload container toward the destination network node using the appropriate message and interface (action S312B).
  • a wireless device generally refers to a device arranged, capable, configured, and/or operable to communicate wirelessly with one or more radio network nodes or with one or more other wireless devices (e.g., via device-to-device (D2D) communication).
  • a wireless device is a device arranged, capable, configured, and/or operable to perform wireless communications.
  • a wireless device may be portable (or mobile) or may be stationary or fixed at a certain location.
  • a wireless device may be configured to transmit and/or receive information without direct human interaction.
  • Such a wireless device may be called a Machine Type Communication (MTC) device or a Machine-to- Machine (M2M) device.
  • MTC Machine Type Communication
  • M2M Machine-to- Machine
  • 3GPP uses the terms User Equipment (UE), Mobile Equipment (ME), and Mobile Terminal (MT).
  • 3GPP2 uses the terms Access Terminal (AT) and Mobile Station (MS).
  • IEEE 802.11 also known as WiFiTM
  • STA station
  • the generic expression“wireless device” encompasses these terms.
  • FIG 9 is a block diagram of an example of a wireless device 110 according to some embodiments.
  • Wireless device 110 includes processing circuitry 112, one or more transceivers 114, and usually additional analog and digital hardware 116.
  • the wireless device 110 may also comprise additional memory 118 and a power source 120 (e.g., a battery).
  • a power source 120 e.g., a battery
  • the processing circuitry 112 usually provides overall control of the wireless device 110. Hence, the processing circuitry 112 is generally responsible for the various functions of the wireless device 110, either directly or indirectly via one or more other components of the wireless device (e.g., sending or receiving messages via the transceiver 114).
  • the processing circuitry 112 may include any suitable combination of hardware to enable the wireless device 110 to perform the functions of wireless device 110 described above.
  • the processing circuitry 112 may comprise at least one processor 122 and at least one memory 124. Examples of processor 122 include, but are not limited to, a central processing unit (CPU), a graphical processing unit (GPU), and other forms of processing unit.
  • memory 124 examples include, but are not limited to, Random Access Memory (RAM) and Read Only Memory (ROM).
  • RAM Random Access Memory
  • ROM Read Only Memory
  • memory 124 is generally configured to store instructions or codes executable by processor 122, and possibly operational data.
  • Processor 122 is then configured to execute the stored instructions and possibly create, transform, or otherwise manipulate data to enable the wireless device 110 to perform the functions of wireless device 110 described above.
  • the processing circuity 112 may comprise one or more application-specific integrated circuits (ASICs), one or more complex programmable logic device (CPLDs), one or more field-programmable gate arrays (FPGAs), or other forms of application-specific and/or programmable circuitry.
  • ASICs application-specific integrated circuits
  • CPLDs complex programmable logic device
  • FPGAs field-programmable gate arrays
  • the wireless device 110 may perform one or more functions of wireless device 110 described above without the need for instructions or codes as the necessary instructions may already be hardwired or preprogrammed into the processing circuitry 112. Understandably, the processing circuitry 112 may comprise a combination of processor(s) 122, memory(ies) 124, and other application-specific and/or programmable circuitry.
  • the processing circuitry 112 may comprise a combination of processor(s) 122, memory(ies) 124, and other application-specific and/or programmable circuitry.
  • the transceiver 114 facilitates transmitting wireless signals to and receiving wireless signals from radio network node 210 and/or other wireless devices 110.
  • Transceiver 114 typically includes one or more transmitters (Tx) 126, and one or more receivers (Rx) 128, both the transmitter(s) 126 and the receiver(s) 128 connected to one or more antennas 130.
  • Transceiver 114 may also comprise signal processing circuitry 132 configured to process the data received from the processing circuitry 112 for transmission via the transmitter(s) 126 and antenna(s) 130, and to process the wireless signals received via the antenna(s) 130 and receiver(s) 128.
  • Signal processing circuitry 132 may comprise any suitable combination of analog signal processing hardware (e.g., amplifier, filter, etc.) and digital signal processing hardware (e.g., digital signal processor (DSP)).
  • analog signal processing hardware e.g., amplifier, filter, etc.
  • DSP digital signal processor
  • additional memory 118 may comprise any form of memory, including volatile and/or non-volatile memory, configured to store instructions and/or data that may be used by the processing circuitry 112 of the wireless device 110.
  • additional memory 118 include, but are not limited to, mass storage media (e.g., a hard disk), removable storage media (e.g., a Compact Disk (CD), a Digital Video Disk (DVD), a memory card).
  • Power source 120 may, in some embodiments, be in the form of a battery or battery pack. Other types of power sources, such as an external power source (e.g., an electricity outlet), photovoltaic devices or power cells, may also be used.
  • the wireless device 110 may comprise additional analog and digital hardware 116.
  • the additional analog and digital hardware 116 may comprise one or more input devices 134 for entry of data into wireless device 110.
  • input devices may include one or more microphones, one or more cameras, a touch screen, one or more sensors, etc.
  • Additional analog and digital hardware 116 may additionally or alternatively comprise one or more output devices 136 for outputting data from the wireless device 110.
  • output devices may include one or more speakers, a screen (which may be a touch screen), a vibrating mechanism, one or more actuators, etc.
  • Additional analog and digital hardware 116 may additional or alternatively comprise one or more interfaces 140 to connect the wireless device 110 to external peripherals. Examples of interfaces include, but are not limited to, an Ethernet port, HDMI port(s), USB port(s), etc.
  • wireless device 110 may include additional components beyond those shown in Figure 9 that may provide certain aspects of the wireless device functionalities, including the functionalities described above and/or any additional functionalities (including any functionality necessary to support the solution described above).
  • a core network node generally refers to a network node arranged, capable, configured, and/or operable to implement or host one or more core network entities and communicate with one or more radio network nodes, with one or more other core network nodes, and/or possibly with network nodes or servers in the external network(s) 400 to provide or enable one or more core network functions in the wireless communication network 100.
  • a core network entity can be implemented as a network element on a dedicated network node, as a software instance running on a dedicated network node, or as a virtualized network function (VNF) instantiated on a network node providing a virtualization environment.
  • a core network node is a network node implementing at least one core network entity (e.g. an AMF, an SFM, a UPF, etc.) responsible for at least one core network function.
  • the 3GPP Evolved Packet Core (EPC) architecture comprises Mobility Management Entity (MME), Serving Gateway (SGW), and Packet Data Network (PDN) Gateway (PGW), while the 3GPP 5G Core (5GC) architecture comprises Access and Mobility Management Function (AMF), Session Management Function (SMF), and User Plane Function (UPF).
  • MME Mobility Management Entity
  • SGW Serving Gateway
  • PGW Packet Data Network Gateway
  • 5GC 3GPP 5G Core
  • AMF Access and Mobility Management Function
  • SMF Session Management Function
  • UPF User Plane Function
  • FIG 10 is a block diagram of an example of a core network node 310 according to some embodiments.
  • the example of the core network node shown in Figure 10 may be referred to as a “dedicated” core network node 310 in which the core network entity is implemented as a network element or as a software instance on a dedicated network node.
  • a core network node 310 may alternatively be a generic network node (e.g., a server in a datacenter) hosting a virtualized instance of the core network entity.
  • Core network node 310 usually includes processing circuitry 312 and communication interface(s) 314. Core network 310 may also include external memory 316.
  • Processing circuitry 312 usually provides overall control of the core network node 310. Hence, processing circuitry 312 is generally responsible for the various functions of the core network node 310, either directly or indirectly via one or more other components of the core network node 310 (e.g., sending or receiving messages via the communication interface 314).
  • the processing circuitry 312 may include any suitable combination of hardware to enable the core network node 310 to perform the functions of the core network entity it implements.
  • the processing circuitry 312 may comprise at least one processor 318 and at least one memory 320.
  • processor 318 include, but are not limited to, a central processing unit (CPU), a graphical processing unit (GPU), and other forms of processing unit.
  • memory 320 include, but are not limited to, Random Access Memory (RAM) and Read Only Memory (ROM).
  • RAM Random Access Memory
  • ROM Read Only Memory
  • processing circuitry 312 comprises memory 320
  • memory 320 is generally configured to store instructions or codes executable by processor 318, and possibly operational data.
  • Processor 318 is then configured to execute the stored instructions and possibly create, transform, or otherwise manipulate data to enable the core network node 310 to perform the functions of the core network entity it implements.
  • the processing circuity 312 may comprise, or further comprise, one or more application-specific integrated circuits (ASICs), one or more complex programmable logic device (CPFDs), one or more field-programmable gate arrays (FPGAs), or other forms of application- specific and/or programmable circuitry.
  • ASICs application-specific integrated circuits
  • CPFDs complex programmable logic device
  • FPGAs field-programmable gate arrays
  • the core network node 310 may perform one or more functions of the core network entity it implements without the need for instructions or codes as the necessary instructions may already be hardwired or preprogrammed into processing circuitry 312. Understandably, processing circuitry 312 may comprise a combination of processor(s) 318, memory(ies) 320, and other application-specific and/or programmable circuitry.
  • additional memory 316 may comprise any form of memory, including volatile and/or non-volatile memory, configured to store instructions and/or data that may be used by the processing circuitry 312.
  • additional memory 316 include, but are not limited to, mass storage media (e.g., a hard disk), removable storage media (e.g., a Compact Disk (CD), a Digital Video Disk (DVD), a memory card).
  • the communication interface(s) 314 enable the core network node 310 to send messages to and receive messages from other network nodes (e.g., radio network nodes, other core network nodes, servers, etc.).
  • the communication interface 314 generally comprises the necessary hardware and software to process messages received from the processing circuitry 312 to be sent by the core network node 310 into a format appropriate for the underlying transport network and, conversely, to process messages received from other network nodes over the underlying transport network into a format appropriate for the processing circuitry 312.
  • communication interface 314 may comprise appropriate hardware (e.g., port, modem, network interface card, etc.) and software, including protocol conversion and data processing capabilities, to communicate with other network nodes.
  • Figure 11 is another block diagram of an example of a core network node 310 according to some embodiments.
  • the example of the core network node shown in Figure 11 may be referred to as a“virtualized” core network node 310 in which the core network entity is implemented as one or more virtual network functions (VNFs) running in virtual machines (VMs) in a virtualization environment provided by the core network node 310.
  • VNFs virtual network functions
  • VMs virtual machines
  • the virtualized core network node 310 generally comprises a hardware infrastructure 342 configured to provide and enable a virtualization environment 344.
  • the hardware infrastructure 342 generally comprises processing circuitry 332, communication interface(s) 334, and possibly additional memory 336.
  • Processing circuitry 332 usually provides overall control of the hardware infrastructure 342 of the virtualized core network node 310. Hence, processing circuitry 332 is generally responsible for the various functions of the hardware infrastructure 332 either directly or indirectly via one or more other components of the core network node 310 (e.g., sending or receiving messages via the communication interface 334). The processing circuitry 332 is also responsible for enabling, supporting and managing the virtualization environment 344 in which the various VNFs are instantiated and run. The processing circuitry 332 may include any suitable combination of hardware to enable the hardware infrastructure 332 of the virtualized core network node 310 to perform its functions.
  • the processing circuitry 336 may comprise at least one processor 338 and at least one memory 340.
  • processor 338 include, but are not limited to, a central processing unit (CPU), a graphical processing unit (GPU), and other forms of processing unit.
  • memory 340 include, but are not limited to, Random Access Memory (RAM) and Read Only Memory (ROM).
  • RAM Random Access Memory
  • ROM Read Only Memory
  • processing circuitry 332 comprises memory 340
  • memory 340 is generally configured to store instructions or codes executable by processor 338, and possibly operational data.
  • Processor 338 is then configured to execute the stored instructions and possibly create, transform, or otherwise manipulate data to enable the hardware infrastructure 342 of the virtualized core network node 310 to perform its functions.
  • the processing circuity 332 may comprise, or further comprise, one or more application-specific integrated circuits (ASICs), one or more complex programmable logic device (CPLDs), one or more field-programmable gate arrays (FPGAs), or other forms of application- specific and/or programmable circuitry.
  • ASICs application-specific integrated circuits
  • CPLDs complex programmable logic device
  • FPGAs field-programmable gate arrays
  • the processing circuitry 332 comprises application- specific and/or programmable circuitry (e.g., ASICs, FPGAs)
  • the hardware infrastructure 342 of the virtualized core network node 310 may perform its functions without the need for instructions or codes as the necessary instructions may already be hardwired or preprogrammed into processing circuitry 332.
  • processing circuitry 332 may comprise a combination of processor(s) 338, memory(ies) 340, and other application-specific and/or programmable circuitry.
  • additional memory 336 may comprise any form of memory, including volatile and/or non-volatile memory, configured to store instructions and/or data that may be used by the processing circuitry 332.
  • additional memory 336 include, but are not limited to, mass storage media (e.g., a hard disk), removable storage media (e.g., a Compact Disk (CD), a Digital Video Disk (DVD), a memory card).
  • the communication interface(s) 334 enable the virtualized core network node 310 to send messages to and receive messages from other network nodes (e.g., radio network nodes, other core network nodes, servers, etc.).
  • the communication interface 334 generally comprises the necessary hardware and software to process messages received from the processing circuitry 332 to be sent by the virtualized core network node 310 into a format appropriate for the underlying transport network and, conversely, to process messages received from other network nodes over the underlying transport network into a format appropriate for the processing circuitry 332.
  • communication interface 334 may comprise appropriate hardware (e.g., port, modem, network interface card, etc.) and software, including protocol conversion and data processing capabilities, to communicate with other network nodes.
  • the virtualization environment 344 is enabled by instructions or codes stored on memory 340 and/or additional memory 336.
  • the virtualization environment 344 generally comprises a virtualization layer 346 (also referred to as a hypervisor), at least one virtual machine 348, and at least one VNF 350.
  • the virtualization layer 346 presents an abstraction of the hardware resources comprised in the hardware infrastructure 342 to the virtual machines 348 in which the VNFs 350 are instantiated. The specific details of this abstraction will depend on the requirements of the VNFs 350.
  • a single virtualized core network node 310 can instantiate and run multiple VNFs 350, each VNF 350 being an instance of a core network entity (e.g., an AMF).
  • a core network entity e.g., an AMF
  • Some embodiments may be represented as a non-transitory software product stored in a machine -readable medium (also called a computer-readable medium, a processor-readable medium, or a computer usable medium having a computer-readable program code embodied therein).
  • the machine -readable medium may be any suitable tangible medium including a magnetic, optical, or electrical storage medium including a diskette, compact disk read only memory (CD-ROM), digital versatile disc read only memory (DVD-ROM) memory device (volatile or non-volatile), or similar storage mechanism.
  • the machine-readable medium may contain various sets of instructions, code sequences, configuration information, or other data, which, when executed, cause a processor to perform steps in a method according to one or more of the described embodiments.
  • Those of ordinary skill in the art will appreciate that other instructions and operations necessary to implement the described embodiments may also be stored on the machine -readable medium.
  • Software running from the machine-readable medium may interface with circuitry to perform the described tasks.
  • references in the specification to“one embodiment,”“an embodiment,”“an example embodiment,” etc. indicate that the embodiment described may include a particular feature or a particular combination of features (e.g., component(s), element(s), integer(s), structure(s), operation(s), and/or step(s)), but every embodiment may not necessarily include the particular feature or the particular combination of features. Such phrases are not necessarily referring to the same embodiment. Further, when a particular feature, or a particular combination of features, is described in connection with an embodiment, it is submitted that it is within the knowledge of one skilled in the art to implement such feature, or combination of features, in connection with other embodiments whether or not explicitly described.
  • E-UTRAN Evolved Universal Terrestrial Radio Access Network
  • gNB Next Generation Node B (a Node B supporting NR)
  • M2M Machine-to-Machine [0123] MME Mobility Management Entity

Landscapes

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

Abstract

L'invention concerne des techniques pour permettre à un noeud de réseau central (par exemple, une fonction de gestion d'accès et de mobilité (AMF)) de déterminer s'il faut acheminer un contenant de charge utile reçu en provenance d'un dispositif sans fil lorsque la restriction de service pour le dispositif sans fil est active. Selon certains aspects, lorsque le noeud de réseau central détermine de s'abstenir d'envoyer le contenant de charge utile reçu, le noeud de réseau central peut envoyer un message de liaison descendante au dispositif sans fil, le message de liaison descendante comprenant un élément d'informations indiquant que le contenant de charge utile n'a pas été transmis par le noeud de réseau central.
PCT/IB2020/054143 2019-05-03 2020-05-01 Mise en oeuvre d'espace de service dans des réseaux de communication sans fil WO2020225684A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
US201962842776P 2019-05-03 2019-05-03
US62/842,776 2019-05-03

Publications (1)

Publication Number Publication Date
WO2020225684A1 true WO2020225684A1 (fr) 2020-11-12

Family

ID=70614371

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/IB2020/054143 WO2020225684A1 (fr) 2019-05-03 2020-05-01 Mise en oeuvre d'espace de service dans des réseaux de communication sans fil

Country Status (1)

Country Link
WO (1) WO2020225684A1 (fr)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2023287254A1 (fr) * 2021-07-16 2023-01-19 Samsung Electronics Co., Ltd. Procédé et système pour fournir un temporisateur de repli à des ue pendant une commande d'admission de tranche de réseau

Citations (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2018174516A1 (fr) * 2017-03-20 2018-09-27 엘지전자(주) Procédé de traitement de message nas dans un système de communication sans fil et appareil correspondant

Patent Citations (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2018174516A1 (fr) * 2017-03-20 2018-09-27 엘지전자(주) Procédé de traitement de message nas dans un système de communication sans fil et appareil correspondant

Non-Patent Citations (3)

* Cited by examiner, † Cited by third party
Title
"3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; System Architecture for the 5G System; Stage 2 (Release 16)", 3GPP STANDARD; TECHNICAL SPECIFICATION; 3GPP TS 23.501, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. SA WG2, no. V16.0.2, 1 April 2019 (2019-04-01), pages 1 - 317, XP051723245 *
ERICSSON ET AL: "Service Gap control, attach without PDN connection and allow MO signalling", vol. CT WG1, no. Bratislava, Slovakia; 20190121 - 20190125, 11 March 2019 (2019-03-11), XP051688998, Retrieved from the Internet <URL:http://www.3gpp.org/ftp/tsg%5Fct/TSG%5FCT/TSGC%5F83%5FShenzhen/Docs/CP%2D190100%2Ezip> [retrieved on 20190311] *
QUALCOMM INCORPORATED ET AL: "Support for transmission of small data over NAS", vol. CT WG1, no. Xi'an, P.R. of China; 20190408 - 20190412, 12 April 2019 (2019-04-12), XP051698748, Retrieved from the Internet <URL:http://www.3gpp.org/ftp/Meetings%5F3GPP%5FSYNC/CT1/updates/update11/C1%2D192768%2Ezip> [retrieved on 20190412] *

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2023287254A1 (fr) * 2021-07-16 2023-01-19 Samsung Electronics Co., Ltd. Procédé et système pour fournir un temporisateur de repli à des ue pendant une commande d'admission de tranche de réseau

Similar Documents

Publication Publication Date Title
US11856652B2 (en) Efficient and reliable data transfer in 5G systems
US11877228B2 (en) Handling of user equipment coverage enhancement mode B radio capability mismatch due to change in user equipment usage setting
RU2653059C1 (ru) Передача малых объемов данных в беспроводной коммуникационной сети
US10892957B2 (en) Managing physical network function instances in a network service instance
US20190159277A1 (en) Enhancing f1 application protocol (f1-ap) interfaces in a multi-hop relay network with centralized unit (cu) and distributed unit (du)
US10887742B2 (en) CIoT architecture for efficient data transmission
US9674682B2 (en) Enabling D2D functionality for public safety applications
US20190182718A1 (en) Single radio voice call continuity handover
CN104205667B (zh) 用于触发多个无线设备的技术和配置
KR101645109B1 (ko) 무선 통신 네트워크 내의 스몰 데이터 기술 및 구성
CA2861483C (fr) Gestion de configurations a double priorite dans un reseau de communication sans fil
US20130203399A1 (en) Handling dual priority applications in a wireless communication network
US11038662B2 (en) Interruption for SCell activation and deactivation with short transmission time interval
US20210258275A1 (en) Low latency messaging service for the 5gc
CN113811021B (zh) 通信方法和装置
WO2020225684A1 (fr) Mise en oeuvre d&#39;espace de service dans des réseaux de communication sans fil
WO2022206393A1 (fr) Procédé et appareil de communication
TWI608714B (zh) 處理分離程序的裝置及方法
WO2023160624A1 (fr) Procédé et appareil de communication
GB2625548A (en) Logical network configuration
WO2020165793A1 (fr) Gestion de l&#39;ordre d&#39;unités de données de paquet de strate de non-accès dans des réseaux de communication sans fil
CN117561776A (zh) 小数据传输技术
WO2020070719A1 (fr) Gestion d&#39;informations de capacité de dispositif sans fil dans des réseaux de communication sans fil

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

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

Country of ref document: EP

Kind code of ref document: A1