WO2022171131A1 - Procédé et appareil de sélection d'ancrage de session pour dispositif terminal - Google Patents

Procédé et appareil de sélection d'ancrage de session pour dispositif terminal Download PDF

Info

Publication number
WO2022171131A1
WO2022171131A1 PCT/CN2022/075684 CN2022075684W WO2022171131A1 WO 2022171131 A1 WO2022171131 A1 WO 2022171131A1 CN 2022075684 W CN2022075684 W CN 2022075684W WO 2022171131 A1 WO2022171131 A1 WO 2022171131A1
Authority
WO
WIPO (PCT)
Prior art keywords
dnn
network entity
smf
network
information
Prior art date
Application number
PCT/CN2022/075684
Other languages
English (en)
Inventor
Yingjiao HE
Yunjie Lu
Juying GAN
Wen Zhang
Jinyin Zhu
Juan Xu
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 WO2022171131A1 publication Critical patent/WO2022171131A1/fr

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W48/00—Access restriction; Network selection; Access point selection
    • H04W48/18—Selecting a network or a communication service
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/12—Reselecting a serving backbone network switching or routing node
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/10—Connection setup
    • H04W76/11—Allocation or use of connection identifiers

Definitions

  • the present disclosure relates generally to the technology of communication system, and in particular, to a method and an apparatus for selecting a session anchor for a terminal device.
  • a routing path (including such as a session anchor) for the session should be selected for serving the session of the terminal device. For example, for a protocol data unit (PDU) session, a specific PSA (PDU session anchor) should be selected.
  • PDU protocol data unit
  • PDU session anchor a specific PSA
  • a method or an apparatus is provided for selecting a session anchor for a terminal device in communication system.
  • a first aspect of the present disclosure provides a method performed by a first network entity.
  • the method may comprise: receiving information about a used data network name, DNN.
  • the used DNN may be determined by a second network entity for a terminal device.
  • the method may further comprise: selecting a session anchor for the terminal device, based at least on the used DNN.
  • the method may further comprise: storing the information about the used DNN.
  • the used DNN may be different with a DNN requested by the terminal device, and/or a DNN selected by an access and mobility management function, AMF.
  • the first network entity may further receive information about the selected DNN.
  • the information about the selected DNN may be received from a home session management function, H-SMF.
  • the information about the selected DNN may be received from an intermediate session management function, I-SMF.
  • the used DNN may be a full DNN comprising a network identifier and an operator identifier.
  • the used DNN may be a full DNN for a home routed protocol data unit, HR PDU, session. Additionally or alternatively, the used DNN may be a full DNN in local break out, LBO, and non-roaming scenarios.
  • a default value for the operator identifier may be a serving core network operator, when the operator identifier is absent.
  • the used DNN may comprise a mapped DNN.
  • the first network entity may comprise: an I-SMF.
  • the second network entity may comprise: a session management function, SMF.
  • the session anchor may comprise a protocol data unit session anchor, PSA.
  • the PSA may comprise a user plane function, UPF.
  • the information about the used DNN may be included in a response massage.
  • the information about the used DNN may be received from a H-SMF.
  • the information about the used DNN may be received from an I-SMF.
  • the first network entity may receive the information about the used DNN, during a procedure for session establishment, a procedure for registration due to mobility, a procedure for service request due to mobility, and/or a procedure for handover.
  • a second aspect of the present disclosure provides a method performed by a second network entity.
  • the method may comprise determining a DNN used by the second network entity for a terminal device. Then method may further comprise transmitting, to a first network entity, information about the used DNN.
  • the used DNN may be different with a DNN requested by the terminal device, and/or a DNN selected by an access and mobility management function, AMF.
  • the second network entity may further transmit information about the selected DNN.
  • the used DNN may be a full DNN comprising a network identifier and an operator identifier.
  • the used DNN may be a full DNN for a home routed protocol data unit, HR PDU, session. Additionally or alternatively, the used DNN may be a full DNN in local break out, LBO, and non-roaming scenarios.
  • a default value for the operator identifier may be a serving core network operator, when the operator identifier is absent.
  • the used DNN may comprise a mapped DNN.
  • the first network entity may comprise: an intermediate session management function, I-SMF.
  • the second network entity may comprise: a session management function, SMF.
  • the session anchor may comprise a protocol data unit session anchor, PSA.
  • the PSA may comprise a user plane function, UPF.
  • the information about the used DNN may be included in a response massage.
  • the first network entity may receive the information about the used DNN, during a procedure for session establishment, a procedure for registration due to mobility, a procedure for service request due to mobility, and/or a procedure for handover.
  • a third aspect of the present disclosure provides a first network entity.
  • the first network entity may comprise one or more processors and one or more memories comprising computer program codes.
  • the one or more memories and the computer program codes may be configured to, with the one or more processors, cause the first network entity at least to: receive, information about a used data network name, DNN.
  • the used DNN may be determined by a second network entity for a terminal device.
  • the first network entity may be further caused to select a session anchor for the terminal device, based at least on the used DNN.
  • the first network entity may be further caused to perform the method according to any of above mentioned embodiments.
  • a fourth aspect of the present disclosure provides second network entity.
  • the second network entity may comprise one or more processors and one or more memories comprising computer program codes.
  • the one or more memories and the computer program codes may be configured to, with the one or more processors, cause the second network entity at least to: determine a DNN used by the second network entity for a terminal device.
  • the second network entity may be further caused to transmit, to a first network entity, information about the used DNN.
  • the second network entity may be further caused to perform the method according to any of above mentioned embodiments.
  • a fifth aspect of the present disclosure provides a computer-readable medium having computer program codes embodied thereon for use with a network entity.
  • the computer program codes may comprise codes for performing the method according to any one of above mentioned embodiments.
  • a sixth aspect of the present disclosure provides a first network entity.
  • the first network entity may comprise a receiving unit, configured to receive information about a used data network name, DNN.
  • the used DNN may be determined by a second network entity for a terminal device.
  • the first network entity may further comprise: a selecting unit, configured to select a session anchor for the terminal device, based at least on the used DNN.
  • a seventh aspect of the present disclosure provides a second network entity.
  • the second network entity may comprise a determining unit, configured to determine a DNN used by the second network entity for a terminal device.
  • the second network entity may further comprise a transmitting unit, configured to transmit, to a first network entity, information about the used DNN.
  • a method implemented in a communication system which may include a host computer, a base station and a UE.
  • the method may comprise providing user data at the host computer.
  • the method may comprise, at the host computer, initiating a transmission carrying the user data to the UE via a cellular network comprising the base station.
  • a communication system including a host computer.
  • the host computer may comprise processing circuitry configured to provide user data, and a communication interface configured to forward the user data to a cellular network for transmission to a UE.
  • the cellular network may comprise a base station having a radio interface and processing circuitry.
  • a communication system including a host computer.
  • the host computer may comprise processing circuitry configured to provide user data, and a communication interface configured to forward user data to a cellular network for transmission to a UE.
  • the UE may comprise a radio interface and processing circuitry.
  • a method implemented in a communication system which may include a host computer, a base station and a UE.
  • the method may comprise, at the host computer, receiving user data transmitted to the base station from the UE.
  • a communication system including a host computer.
  • the host computer may comprise a communication interface configured to receive user data originating from a transmission from a UE to a base station.
  • the UE may comprise a radio interface and processing circuitry.
  • a method implemented in a communication system which may include a host computer, a base station and a UE.
  • the method may comprise, at the host computer, receiving, from the base station, user data originating from a transmission which the base station has received from the UE.
  • a communication system which may include a host computer.
  • the host computer may comprise a communication interface configured to receive user data originating from a transmission from a UE to a base station.
  • the base station may comprise a radio interface and processing circuitry.
  • a method or an apparatus for selecting a session anchor for a terminal device in a communication system.
  • the session anchor for the terminal device may be selected based at least on the used DNN, which is determined by a network entity. Therefore, an appropriate session anchor already associated to the terminal device may be selected.
  • FIG. 1 is a diagram showing a PDU Session Establishment Procedure without sending used DNN to I-SMF.
  • FIG. 2A is a flow chart showing a method performed by a first network entity, according to embodiments of the present disclosure.
  • FIG. 2B is a flow chart showing an additional step of the method performed by the first network entity, according to embodiments of the present disclosure.
  • FIG. 3 is a flow chart showing a method performed by a second network entity, according to embodiments of the present disclosure.
  • FIG. 4 is a diagram showing a procedure for an I-SMF to select local PSA based on used DNN from SMF, according to embodiments of the present disclosure.
  • FIG. 5 is a block diagram showing apparatuses for a first network entity, a second network entity, according to embodiments of the present disclosure.
  • FIG. 6 is a block diagram showing a computer readable storage medium, according to embodiments of the present disclosure.
  • FIG. 7 is a schematic showing units of the apparatus for a first network node, according to embodiments of the present disclosure.
  • FIG. 8 is a schematic showing units of the apparatus for a second network entity, according to embodiments of the present disclosure.
  • FIG. 9 is a block diagram illustrating a telecommunication network connected via an intermediate network to a host computer in accordance with some embodiments of the present disclosure.
  • FIG. 10 is a block diagram illustrating a host computer communicating via a base station with a UE over a partially wireless connection in accordance with some embodiments of the present disclosure.
  • FIG. 11 is a flowchart illustrating a method implemented in a communication system, in accordance with an embodiment of the present disclosure.
  • FIG. 12 is a flowchart illustrating a method implemented in a communication system, in accordance with an embodiment of the present disclosure.
  • FIG. 13 is a flowchart illustrating a method implemented in a communication system, in accordance with an embodiment of the present disclosure.
  • FIG. 14 is a flowchart illustrating a method implemented in a communication system, in accordance with an embodiment of the present disclosure.
  • the term “network” refers to a network/system following any suitable communication standards, such as new radio (NR) , long term evolution (LTE) , LTE-Advanced, wideband code division multiple access (WCDMA) , high-speed packet access (HSPA) , and so on.
  • NR new radio
  • LTE long term evolution
  • WCDMA wideband code division multiple access
  • HSPA high-speed packet access
  • the communications between a terminal device and a network node in the communication network may be performed according to any suitable generation communication protocols, including, but not limited to, the first generation (1G) , the second generation (2G) , 2.5G, 2.75G, the third generation (3G) , 4G, 4.5G, 5G communication protocols, and/or any other protocols either currently known or to be developed in the future.
  • the term “entity” refers to a device/apparatus/node/function with accessing capability in a communication system via which a terminal device accesses to the network or receives services therefrom.
  • the entity may include a base station (BS) , an access point (AP) , a multi-cell/multicast coordination entity (MCE) , a server node/function (such as a service capability server/application server, SCS/AS, group communication service application server, GCS AS, application function, AF) , an exposure node/function (such as a service capability exposure function, SCEF, network exposure function, NEF) , a unified data management, UDM, a home subscriber server, HSS, a session management function, SMF, an access and mobility management function, AMF, a mobility management entity, MME, a controller or any other suitable device in a wireless communication network.
  • BS base station
  • AP access point
  • MCE multi-cell/multicast coordination entity
  • server node/function such
  • the BS may be, for example, a node B (NodeB or NB) , an evolved NodeB (eNodeB or eNB) , a next generation NodeB (gNodeB or gNB) , a remote radio unit (RRU) , a radio header (RH) , a remote radio head (RRH) , a relay, a low power node such as a femto, a pico, and so forth.
  • NodeB or NB node B
  • eNodeB or eNB evolved NodeB
  • gNodeB or gNB next generation NodeB
  • RRU remote radio unit
  • RH radio header
  • RRH remote radio head
  • relay a low power node such as a femto, a pico, and so forth.
  • the network entity may comprise multi-standard radio (MSR) radio equipment such as MSR BSs, network controllers such as radio network controllers (RNCs) or base station controllers (BSCs) , base transceiver stations (BTSs) , transmission points, transmission nodes, positioning nodes and/or the like.
  • MSR multi-standard radio
  • RNCs radio network controllers
  • BSCs base station controllers
  • BTSs base transceiver stations
  • transmission points transmission nodes
  • positioning nodes positioning nodes and/or the like.
  • the network entity may represent any suitable device (or group of devices) capable, configured, arranged, and/or operable to enable and/or provide a terminal device access to a wireless communication network or to provide some service to a terminal device that has accessed to the wireless communication network.
  • such entity may be embodied in any kind of hardware and/or software of a standalone apparatus, a virtual machine, a cloud-implemented server, and/or a distributed server, etc.
  • terminal device encompasses a device which is able to communicate with a network entity/network function, such as a base station, or with another wireless device by transmitting and/or receiving wireless signals.
  • a network entity/network function such as a base station
  • terminal device encompasses, but is not limited to: a mobile phone, a stationary or mobile wireless device for machine-to-machine communication, an integrated or embedded wireless card, an externally plugged in wireless card, a vehicle, etc.
  • a terminal device may also be called an IoT device and represent a machine or other device that performs monitoring, sensing and/or measurements etc., and transmits the results of such monitoring, sensing and/or measurements etc. to another terminal device and/or a network equipment.
  • the terminal device may in this case be a machine-to-machine (M2M) device, which may in a 3rd generation partnership project (3GPP) context be referred to as a machine-type communication (MTC) device.
  • M2M machine-to-machine
  • 3GPP 3rd generation partnership project
  • the terminal device may be a UE implementing the 3GPP narrow band Internet of things (NB-IoT) standard.
  • NB-IoT 3GPP narrow band Internet of things
  • machines or devices are sensors, metering devices such as power meters, industrial machinery, or home or personal appliances, e.g. refrigerators, televisions, personal wearables such as watches etc.
  • a terminal device may represent a vehicle or other equipment, for example, a medical instrument that is capable of monitoring, sensing and/or reporting etc. on its operational status or other functions associated with its operation.
  • the terms “first” , “second” and so forth refer to different elements.
  • the singular forms “a” and “an” are intended to include the plural forms as well, unless the context clearly indicates otherwise.
  • the term “based on” is to be read as “based at least in part on” .
  • the term “one embodiment” and “an embodiment” are to be read as “at least one embodiment” .
  • the term “another embodiment” is to be read as “at least one other embodiment” .
  • Other definitions, explicit and implicit, may be included below.
  • a routing path (including such as a session anchor) for the session may be influenced by many conditions. For example, it may be influenced by an application function (AF) .
  • AF application function
  • DN data network
  • DNAI Access Identifier
  • AF application function
  • PCF policy control function
  • An AF may send requests to influence SMF (session management function) routing decisions for traffic of PDU Session.
  • the AF requests may influence UPF (user plane function) (re) selection and allow routing user traffic to a local access to a Data Network (identified by a DNAI) .
  • the DNAIs are related to the information considered by the SMF for UPF selection, e.g. for diverting (locally) some traffic matching traffic filters provided by the PCF.
  • the SMF may, based on local policies, take the information in the PCC rules into account to:
  • the SMF is responsible for handling the mapping between the UE (user equipment) location (TAI (tracking area identity) /Cell-Id) and DNAI (s) associated with UPF and applications and the selection of the UPF (s) that serve a PDU Session.
  • TAI tracking area identity
  • Cell-Id DNAI
  • the location area and application type meet the DNAI PCC rule condition: current location area belongs to the DNAI area defined in DNAI PCC rule; current application traffic meets the DNAI PCC rule application traffic definition.
  • the I-SMF will select a new UL CL (uplink Classifier) /BP (branching point) UPF and a new local PSA2 (PDU Session Anchor 2) for the PDU session, ULCL/BP is used to diverting the traffic to the PSA1 and PSA2, PSA2 is used to forwarding the DNAI defined traffic to the wanted local access network.
  • ULCL/BP is used to diverting the traffic to the PSA1 and PSA2
  • PSA2 is used to forwarding the DNAI defined traffic to the wanted local access network.
  • the I-SMF will select UPF based on DNAI information, while for the local PSA2 selection, the I-SMF will select UPF based on DNAI information and DNN name, DNN is needed for I-SMF selecting PSA2 for ULCL/BP case since accoriding to DNAI definition, DNAI may belong to multiple DNNs, while the PSA2 selection need have one specific DNN information as the input.
  • the I-SMF only has the requested/selected DNN information received from AMF during the PDU session establishment, but actually the final used DNN may not be the requested DNN or selected DNN, since instead of using the requested DNN from the AMF, some operators require to use the DNN provided by UDM (unified data management) , or Radius Server, or some mapped DNN.
  • UDM unified data management
  • Radius Server or some mapped DNN.
  • the selected/used DNN also need be passed between I-SMFs in session management context, “SmContext” .
  • FIG. 1 is a diagram showing a PDU Session Establishment Procedure without sending used DNN to I-SMF.
  • FIG. 1 is based on “ Figure 4.3.2.2.2-1: UE-requested PDU Session Establishment for home-routed roaming scenarios” in 3GPP TS 23.502 V16.7.1.
  • step 6 only “requested DNN” is included in the PduSessionCreateData, and in step 13, the PduSessionCreatedData does not include the “used DNN” either.
  • Example embodiments of the present disclosure provides improved solutions for such problems.
  • FIG. 2A is a flow chart showing a method performed by a first network entity, according to embodiments of the present disclosure.
  • the method may comprise: step S101, receiving information about a used data network name, DNN.
  • the used DNN may be determined by a second network entity for a terminal device.
  • the method may further comprise: step S102, selecting a session anchor for the terminal device, based at least on the used DNN.
  • a method or an apparatus for selecting a session anchor for a terminal device in a communication system.
  • the session anchor for the terminal device may be selected based at least on the used DNN, which is determined by a network entity. Therefore, an appropriate session anchor already associated to the terminal device may be selected.
  • FIG. 2B is a flow chart showing an additional step of the method performed by the first network entity, according to embodiments of the present disclosure.
  • the method may further comprise: step S103, storing the information about the used DNN.
  • the first network entity shall store the “Used DNN” and use it for local PSA selection later for ULCL/BP case.
  • the used DNN may be different with a DNN requested by the terminal device, and/or a DNN selected by an access and mobility management function, AMF.
  • the first network entity may further receive information about the selected DNN.
  • the used DNN may be the same with the requested DNN and/or the selected DNN, in some scenarios.
  • the information about the selected DNN may be received from a home session management function, H-SMF; or the information about the selected DNN may be received from an intermediate session management function, I-SMF.
  • H-SMF home session management function
  • I-SMF intermediate session management function
  • the used DNN may be a full DNN comprising a network identifier and an operator identifier.
  • the used DNN may be a full DNN for a home routed protocol data unit, HR PDU, session; and/or the used DNN may be a full DNN in local break out, LBO, and non-roaming scenarios.
  • a default value for the operator identifier may be a serving core network operator, when the operator identifier is absent.
  • the used DNN may comprise a mapped DNN.
  • the first network entity may comprise: an I-SMF.
  • the session anchor may comprise a protocol data unit session anchor, PSA.
  • the PSA may comprise a user plane function, UPF.
  • the information about the used DNN may be included in a response massage.
  • the information about the used DNN may be received from a H-SMF; or the information about the used DNN may be received from an I-SMF.
  • the first network entity may receive the information about the used DNN, during a procedure for session establishment, a procedure for registration due to mobility, a procedure for service request due to mobility, and/or a procedure for handover.
  • FIG. 3 is a flow chart showing a method performed by a second network entity, according to embodiments of the present disclosure.
  • the method may comprise: step S201, determining a DNN used by the second network entity for a terminal device; and step S202, transmitting, to a first network entity, information about the used DNN.
  • the used DNN may be different with a DNN requested by the terminal device, and/or a DNN selected by an access and mobility management function, AMF.
  • the second network entity may further transmit information about the selected DNN.
  • the second network entity may comprise: a session management function, SMF.
  • the AMF when DNN replacement is enforced, the AMF will pass both UE requested DNN and the selected DNN to SMF.
  • the SMF will apply the PDU session resource based on selected DNN.
  • ETSUN Endhancing Topology of SMF and UPF in 5G Networks
  • the I-SMF may trigger local PSA which should also be based on selected DNN (aligned with anchor SMF) .
  • the selected DNN shall be passed between I-SMFs in SmContext.
  • the SMF may select the final used DNN which is input from UDM, or Radius Server, or PCF.
  • the SMF will apply the PDU session resource based on the final used DNN.
  • the I-SMF may trigger local PSA which should also be based on the final used DNN (aligned with anchor SMF) .
  • the final used DNN shall be passed between I-SMFs in SmContext.
  • the SMF may use a mapped DNN (e.g. dynamically identify the target DNN from an AF during PDU session establishment) .
  • the SMF use this mapped DNN for PDU session resources.
  • this mapped DNN shall also be informed to I-SMF for possible local PSA.
  • the I-SMF when one new I-SMF is inserted due to the condition met, the I-SMF will send Nsmf_PDUSession_Create Request to the SMF, the SMF will send Nsmf_PDUSession_Create Response with a new IE (information element) “Used DNN” to I-SMF, the I-SMF shall store the “Used DNN” and use it for local PSA selection later for ULCL/BP case. During I-SMF change, the selected/used DNN shall be passed between I-SMFs in SmContext.
  • the AMF selects an I-SMF that serves the area where UE camps.
  • a new I-SMF inserting/chaging may happen in the following cases:
  • Case 3 UE Service Request procedure due to that the UE moves from SMF service area to new I-SMF service area; (refer to TS23.502, chapter 4.23.4.3 UE Triggered Service Request with I-SMF insertion/change/removal) ;
  • Case 11 PDU Session mobility from non-3GPP to 3GPP access with I-SMF insertion (because the TA associated with the UE location over 3GPP requires the AMF to insert an I-SMF, refer to chapter 4.23.15 PDU Session mobility between 3GPP and non-3GPP access) ;
  • Case 12 Handover of a PDU Session procedure from untrusted non-3GPP to 3GPP access (non-roaming and roaming with local breakout) with I-SMF insertion (refer to TS23.502, chapter 4.23.16.1 Handover of a PDU Session procedure from untrusted non-3GPP to 3GPP access (non-roaming and roaming with local breakout) .
  • FIG. 4 is a diagram showing a procedure for an I-SMF to select local PSA based on used DNN from SMF, according to embodiments of the present disclosure.
  • the (T) AMF target AMF selects I-SMF since the service area of the selected SMF does not include the current UE location and the UE does not request for a MA PDU Session, the AMF selects an I-SMF that serves the area where UE camps.
  • step 2 the (T) AMF sends Nsmf_PDUSession_CreateSMContext Request to the selected new I-SMF.
  • step 3 the I-SMF sends Nsmf_PDUSession_Create Request with the requested DNN/selected DNN to the Anchor SMF.
  • step 4 the Anchor SMF sends Nsmf_PDUSession_Context Response with “used DNN” to the I-SMF.
  • the I-SMF stores “used DNN” .
  • step 5 when the UE has some mobility and the (T) AMF selects a new I-SMF, the new I-SMF sends Nsmf_PDUSession_Context Request to the source I-SMF.
  • step 6 the source I-SMF sends Nsmf_PDUSession_Context Response with the “used DNN” and “selected DNN” to the new target I-SMF.
  • step 7 the I-SMF selects I-UPF based on UE location.
  • step 8 when later UE mobility and detected application trigger I-SMF inserting ULCL/BP and local PSA2.
  • step 9 the I-SMF selects ULCL/BP based on UE location.
  • step 10 the I-SMF selects local PSA2 based on UE location and stored used DNN.
  • S_RAN refers to source radio access network.
  • T_NG-RAN refers to target next generation radio access network.
  • Example embodiments of the present disclosure further provide a specific example definition (underlined) for the IE “used DNN” , which is added in the following tables.
  • example embodiments of the present disclosure provide improvement for related API (application program interface) .
  • Example embodiments further provide the following advantage for an I-SMF to select Local PSA based on the Used DNN from SMF.
  • the I-SMF can select the correct local PSA based on the used DNN from the SMF, instead of the requested DNN, in case the used DNN is not the requested DNN as required by the operator.
  • MEC function Mobile Edge Communicating
  • FIG. 5 is a block diagram showing apparatuses for a first network entity, a second network entity, according to embodiments of the present disclosure.
  • the first/second network entity 100/200 may comprise: one or more processors 101/201; and one or more memories 102/202 comprising computer program codes.
  • the one or more memories and the computer program codes may be configured to, with the one or more processors, cause the first/second network entity 100/200 at least to: perform the method according to any one of embodiments described above, such as shown in FIG. 2A, 2B, 3.
  • the first network entity may receive information about a used data network name, DNN.
  • the used DNN may be determined by a second network entity for a terminal device.
  • the first network entity may further select a session anchor for the terminal device, based at least on the used DNN.
  • the second network entity may determine a DNN used by the second network entity for a terminal device; and transmit, to a first network entity, information about the used DNN.
  • the processors 101, 201 may be any kind of processing component, such as one or more microprocessor or microcontrollers, as well as other digital hardware, which may include digital signal processors (DSPs) , special-purpose digital logic, and the like.
  • the memories 102, 202 may be any kind of storage component, such as read-only memory (ROM) , random-access memory, cache memory, flash memory devices, optical storage devices, etc.
  • FIG. 6 is a block diagram showing a computer readable storage medium, according to embodiments of the present disclosure.
  • a computer-readable medium 600 may have computer program codes 601 embodied thereon for use with a first network entity/second network entity/short message service function.
  • the computer program codes 601 may comprise codes for performing any of the methods above described, such as shown in FIG. 2A, 2B, 3.
  • the computer program codes 601 may comprise codes for a first network entity 100, second network entity 200.
  • the computer readable storage medium 600 may be configured to include memory such as RAM, ROM, programmable read-only memory (PROM) , erasable programmable read-only memory (EPROM) , electrically erasable programmable read-only memory (EEPROM) , magnetic disks, optical disks, floppy disks, hard disks, removable cartridges, or flash drives.
  • memory such as RAM, ROM, programmable read-only memory (PROM) , erasable programmable read-only memory (EPROM) , electrically erasable programmable read-only memory (EEPROM) , magnetic disks, optical disks, floppy disks, hard disks, removable cartridges, or flash drives.
  • FIG. 7 is a schematic showing units of the apparatus for a first network node, according to embodiments of the present disclosure.
  • the apparatus for a first network entity 100 may comprise: a receiving unit 1001, configured to receive information about a used data network name, DNN.
  • the used DNN may be determined by a second network entity for a terminal device.
  • the first network entity may further comprise: a selecting unit 1002, configured to select a session anchor for the terminal device, based at least on the used DNN.
  • FIG. 8 is a schematic showing units of the apparatus for a second network entity, according to embodiments of the present disclosure.
  • the apparatus for a second network entity 200 may comprise: a determining unit 2001, configured to determine a DNN used by the second network entity for a terminal device; and a transmitting unit 2002, configured to transmit, to a first network entity, information about the used DNN.
  • the term unit may have conventional meaning in the field of electronics, electrical devices and/or electronic devices and may include, for example, electrical and/or electronic circuitry, devices, modules, processors, memories, logic solid state and/or discrete devices, computer programs or instructions for carrying out respective tasks, procedures, computations, outputs, and/or displaying functions, and so on, as such as those that are described herein.
  • the first network entity 100, the second network entity 200 may not need a fixed processor or memory, any computing resource and storage resource may be arranged from at least one network node/device/entity/apparatus in the communication system.
  • the virtualization technology and network computing technology may be further introduced, so as to improve the usage efficiency of the network resources and the flexibility of the network.
  • Example embodiments of the present disclosure may further provide method implemented in a communication system.
  • a method implemented in a communication system which may include a host computer, a base station and a UE.
  • the method may comprise providing user data at the host computer.
  • the method may comprise, at the host computer, initiating a transmission carrying the user data to the UE via a cellular network comprising the base station.
  • a communication system including a host computer.
  • the host computer may comprise processing circuitry configured to provide user data, and a communication interface configured to forward the user data to a cellular network for transmission to a UE.
  • the cellular network may comprise a base station having a radio interface and processing circuitry.
  • a communication system including a host computer.
  • the host computer may comprise processing circuitry configured to provide user data, and a communication interface configured to forward user data to a cellular network for transmission to a UE.
  • the UE may comprise a radio interface and processing circuitry.
  • a method implemented in a communication system which may include a host computer, a base station and a UE.
  • the method may comprise, at the host computer, receiving user data transmitted to the base station from the UE.
  • a communication system including a host computer.
  • the host computer may comprise a communication interface configured to receive user data originating from a transmission from a UE to a base station.
  • the UE may comprise a radio interface and processing circuitry.
  • a method implemented in a communication system which may include a host computer, a base station and a UE.
  • the method may comprise, at the host computer, receiving, from the base station, user data originating from a transmission which the base station has received from the UE.
  • a communication system which may include a host computer.
  • the host computer may comprise a communication interface configured to receive user data originating from a transmission from a UE to a base station.
  • the base station may comprise a radio interface and processing circuitry.
  • FIG. 9 is a block diagram illustrating a telecommunication network connected via an intermediate network to a host computer in accordance with some embodiments of the present disclosure.
  • a communication system includes a telecommunication network 910, such as a 3GPP-type cellular network, which comprises an access network 911, such as a radio access network, and a core network 914.
  • the access network 911 comprises a plurality of base stations 912a, 912b, 912c, such as NBs, eNBs, gNBs or other types of wireless access points, each defining a corresponding coverage area 913a, 913b, 913c.
  • Each base station 912a, 912b, 912c is connectable to the core network 914 over a wired or wireless connection 915.
  • a first UE 991 located in a coverage area 913c is configured to wirelessly connect to, or be paged by, the corresponding base station 912c.
  • a second UE 992 in a coverage area 913a is wirelessly connectable to the corresponding base station 912a. While a plurality of UEs 991, 992 are illustrated in this example, the disclosed embodiments are equally applicable to a situation where a sole UE is in the coverage area or where a sole UE is connecting to the corresponding base station 912.
  • the telecommunication network 910 is itself connected to a host computer 930, which may be embodied in the hardware and/or software of a standalone server, a cloud-implemented server, a distributed server or as processing resources in a server farm.
  • the host computer 930 may be under the ownership or control of a service provider, or may be operated by the service provider or on behalf of the service provider.
  • Connections 921 and 922 between the telecommunication network 910 and the host computer 930 may extend directly from the core network 914 to the host computer 930 or may go via an optional intermediate network 920.
  • An intermediate network 920 may be one of, or a combination of more than one of, a public, private or hosted network; the intermediate network 920, if any, may be a backbone network or the Internet; in particular, the intermediate network 920 may comprise two or more sub-networks (not shown) .
  • the communication system of FIG. 9 as a whole enables connectivity between the connected UEs 991, 992 and the host computer 930.
  • the connectivity may be described as an over-the-top (OTT) connection 950.
  • the host computer 930 and the connected UEs 991, 992 are configured to communicate data and/or signaling via the OTT connection 950, using the access network 911, the core network 914, any intermediate network 920 and possible further infrastructure (not shown) as intermediaries.
  • the OTT connection 950 may be transparent in the sense that the participating communication devices through which the OTT connection 950 passes are unaware of routing of uplink and downlink communications.
  • the base station 912 may not or need not be informed about the past routing of an incoming downlink communication with data originating from the host computer 930 to be forwarded (e.g., handed over) to a connected UE 991. Similarly, the base station 912 need not be aware of the future routing of an outgoing uplink communication originating from the UE 991 towards the host computer 930.
  • FIG. 10 is a block diagram illustrating a host computer communicating via a base station with a UE over a partially wireless connection in accordance with some embodiments of the present disclosure.
  • a host computer 1010 comprises hardware 1015 including a communication interface 1016 configured to set up and maintain a wired or wireless connection with an interface of a different communication device of the communication system 1000.
  • the host computer 1010 further comprises a processing circuitry 1018, which may have storage and/or processing capabilities.
  • the processing circuitry 1018 may comprise one or more programmable processors, application-specific integrated circuits, field programmable gate arrays or combinations of these (not shown) adapted to execute instructions.
  • the host computer 1010 further comprises software 1011, which is stored in or accessible by the host computer 1010 and executable by the processing circuitry 1018.
  • the software 1011 includes a host application 1012.
  • the host application 1012 may be operable to provide a service to a remote user, such as UE 1030 connecting via an OTT connection 1050 terminating at the UE 1030 and the host computer 1010. In providing the service to the remote user, the host application 1012 may provide user data which is transmitted using the OTT connection 1050.
  • the communication system 1000 further includes a base station 1020 provided in a telecommunication system and comprising hardware 1025 enabling it to communicate with the host computer 1010 and with the UE 1030.
  • the hardware 1025 may include a communication interface 1026 for setting up and maintaining a wired or wireless connection with an interface of a different communication device of the communication system 1000, as well as a radio interface 1027 for setting up and maintaining at least a wireless connection 1070 with the UE 1030 located in a coverage area (not shown in FIG. 10) served by the base station 1020.
  • the communication interface 1026 may be configured to facilitate a connection 1060 to the host computer 1010.
  • the connection 1060 may be direct or it may pass through a core network (not shown in FIG.
  • the hardware 1025 of the base station 1020 further includes a processing circuitry 1028, which may comprise one or more programmable processors, application-specific integrated circuits, field programmable gate arrays or combinations of these (not shown) adapted to execute instructions.
  • the base station 1020 further has software 1021 stored internally or accessible via an external connection.
  • the communication system 1000 further includes the UE 1030 already referred to.
  • Its hardware 1035 may include a radio interface 1037 configured to set up and maintain a wireless connection 1070 with a base station serving a coverage area in which the UE 1030 is currently located.
  • the hardware 1035 of the UE 1030 further includes a processing circuitry 1038, which may comprise one or more programmable processors, application-specific integrated circuits, field programmable gate arrays or combinations of these (not shown) adapted to execute instructions.
  • the UE 1030 further comprises software 1031, which is stored in or accessible by the UE 1030 and executable by the processing circuitry 1038.
  • the software 1031 includes a client application 1032.
  • the client application 1032 may be operable to provide a service to a human or non-human user via the UE 1030, with the support of the host computer 1010.
  • an executing host application 1012 may communicate with the executing client application 1032 via the OTT connection 1050 terminating at the UE 1030 and the host computer 1010.
  • the client application 1032 may receive request data from the host application 1012 and provide user data in response to the request data.
  • the OTT connection 1050 may transfer both the request data and the user data.
  • the client application 1032 may interact with the user to generate the user data that it provides.
  • the host computer 1010, the base station 1020 and the UE 1030 illustrated in FIG. 10 may be similar or identical to the host computer 930, one of base stations 912a, 912b, 912c and one of UEs 991, 992 of FIG. 9, respectively.
  • the inner workings of these entities may be as shown in FIG. 10 and independently, the surrounding network topology may be that of FIG. 9.
  • the OTT connection 1050 has been drawn abstractly to illustrate the communication between the host computer 1010 and the UE 1030 via the base station 1020, without explicit reference to any intermediary devices and the precise routing of messages via these devices.
  • Network infrastructure may determine the routing, which it may be configured to hide from the UE 1030 or from the service provider operating the host computer 1010, or both. While the OTT connection 1050 is active, the network infrastructure may further take decisions by which it dynamically changes the routing (e.g., on the basis of load balancing consideration or reconfiguration of the network) .
  • Wireless connection 1070 between the UE 1030 and the base station 1020 is in accordance with the teachings of the embodiments described throughout this disclosure.
  • One or more of the various embodiments improve the performance of OTT services provided to the UE 1030 using the OTT connection 1050, in which the wireless connection 1070 forms the last segment. More precisely, the teachings of these embodiments may improve the latency and the power consumption, and thereby provide benefits such as lower complexity, reduced time required to access a cell, better responsiveness, extended battery lifetime, etc.
  • a measurement procedure may be provided for the purpose of monitoring data rate, latency and other factors on which the one or more embodiments improve.
  • the measurement procedure and/or the network functionality for reconfiguring the OTT connection 1050 may be implemented in software 1011 and hardware 1015 of the host computer 1010 or in software 1031 and hardware 1035 of the UE 1030, or both.
  • sensors may be deployed in or in association with communication devices through which the OTT connection 1050 passes; the sensors may participate in the measurement procedure by supplying values of the monitored quantities exemplified above, or supplying values of other physical quantities from which the software 1011, 1031 may compute or estimate the monitored quantities.
  • the reconfiguring of the OTT connection 1050 may include message format, retransmission settings, preferred routing etc.; the reconfiguring need not affect the base station 1020, and it may be unknown or imperceptible to the base station 1020. Such procedures and functionalities may be known and practiced in the art.
  • measurements may involve proprietary UE signaling facilitating the host computer 1010’s measurements of throughput, propagation times, latency and the like.
  • the measurements may be implemented in that the software 1011 and 1031 causes messages to be transmitted, in particular empty or ‘dummy’ messages, using the OTT connection 1050 while it monitors propagation times, errors etc.
  • FIG. 11 is a flowchart illustrating a method implemented in a communication system, in accordance with an embodiment.
  • the communication system includes a host computer, a base station and a UE which may be those described with reference to FIG. 9 and FIG. 10. For simplicity of the present disclosure, only drawing references to FIG. 11 will be included in this section.
  • the host computer provides user data.
  • substep 1111 (which may be optional) of step 1110, the host computer provides the user data by executing a host application.
  • the host computer initiates a transmission carrying the user data to the UE.
  • step 1130 the base station transmits to the UE the user data which was carried in the transmission that the host computer initiated, in accordance with the teachings of the embodiments described throughout this disclosure.
  • step 1140 the UE executes a client application associated with the host application executed by the host computer.
  • FIG. 12 is a flowchart illustrating a method implemented in a communication system, in accordance with an embodiment.
  • the communication system includes a host computer, a base station and a UE which may be those described with reference to FIG. 9 and FIG. 10. For simplicity of the present disclosure, only drawing references to FIG. 12 will be included in this section.
  • the host computer provides user data.
  • the host computer provides the user data by executing a host application.
  • the host computer initiates a transmission carrying the user data to the UE. The transmission may pass via the base station, in accordance with the teachings of the embodiments described throughout this disclosure.
  • step 1230 (which may be optional) , the UE receives the user data carried in the transmission.
  • FIG. 13 is a flowchart illustrating a method implemented in a communication system, in accordance with an embodiment.
  • the communication system includes a host computer, a base station and a UE which may be those described with reference to FIG. 9 and FIG. 10. For simplicity of the present disclosure, only drawing references to FIG. 13 will be included in this section.
  • step 1310 the UE receives input data provided by the host computer. Additionally or alternatively, in step 1320, the UE provides user data.
  • substep 1321 (which may be optional) of step 1320, the UE provides the user data by executing a client application.
  • substep 1311 (which may be optional) of step 1310, the UE executes a client application which provides the user data in reaction to the received input data provided by the host computer.
  • the executed client application may further consider user input received from the user.
  • the UE initiates, in substep 1330 (which may be optional) , transmission of the user data to the host computer.
  • step 1340 of the method the host computer receives the user data transmitted from the UE, in accordance with the teachings of the embodiments described throughout this disclosure.
  • FIG. 14 is a flowchart illustrating a method implemented in a communication system, in accordance with an embodiment.
  • the communication system includes a host computer, a base station and a UE which may be those described with reference to FIG. 9 and FIG. 10. For simplicity of the present disclosure, only drawing references to FIG. 14 will be included in this section.
  • the base station receives user data from the UE.
  • the base station initiates transmission of the received user data to the host computer.
  • the host computer receives the user data carried in the transmission initiated by the base station.
  • the various exemplary embodiments of the present disclosure may be implemented in hardware or special purpose circuits, software, logic or any combination thereof.
  • some aspects may be implemented in hardware, while other aspects may be implemented in firmware or software that may be executed by a controller, microprocessor or other computing device, although the disclosure is not limited thereto.
  • firmware or software may be executed by a controller, microprocessor or other computing device, although the disclosure is not limited thereto.
  • While various aspects of the exemplary embodiments of this disclosure may be illustrated and described as block diagrams, flow charts, or using some other pictorial representation, it is well understood that these blocks, apparatus, systems, techniques or methods described herein may be implemented in, as non-limiting examples, hardware, software, firmware, special purpose circuits or logic, general purpose hardware or controller or other computing devices, or some combination thereof.
  • the exemplary embodiments of the disclosure may be practiced in various components such as integrated circuit chips and modules. It should thus be appreciated that the exemplary embodiments of this disclosure may be realized in an apparatus that is embodied as an integrated circuit, where the integrated circuit may include circuitry (as well as possibly firmware) for embodying at least one or more of a data processor, a digital signal processor, baseband circuitry and radio frequency circuitry that are configurable so as to operate in accordance with the exemplary embodiments of this disclosure.
  • exemplary embodiments of the disclosure may be embodied in computer-executable instructions, such as in one or more program modules, executed by one or more computers or other devices.
  • program modules include routines, programs, objects, components, data structures, etc. that perform particular tasks or implement particular abstract data types when executed by a processor in a computer or other device.
  • the computer executable instructions may be stored on a computer readable medium such as a hard disk, optical disk, removable storage media, solid state memory, RAM, etc.
  • the functionality of the program modules may be combined or distributed as desired in various embodiments.
  • the functionality may be embodied in whole or in part in firmware or hardware equivalents such as integrated circuits, field programmable gate arrays (FPGA) , and the like.
  • FPGA field programmable gate arrays

Landscapes

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

Abstract

Des modes de réalisation de la présente divulgation concernent un procédé et un appareil de sélection d'ancrage de session pour un dispositif terminal. Un procédé mis en œuvre par une première entité de réseau peut faire appel aux étapes suivantes : réception (S101), d'informations concernant un nom de réseau de données, DNN, utilisé, le DNN utilisé étant déterminé par une seconde entité de réseau pour un dispositif terminal; et sélection (S102), d'un ancrage de session pour le dispositif terminal, sur la base, au moins, du DNN utilisé. Selon des modes de réalisation de la présente divulgation, un ancrage de session approprié déjà associé au dispositif terminal peut être sélectionné.
PCT/CN2022/075684 2021-02-15 2022-02-09 Procédé et appareil de sélection d'ancrage de session pour dispositif terminal WO2022171131A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CNPCT/CN2021/076662 2021-02-15
CN2021076662 2021-02-15

Publications (1)

Publication Number Publication Date
WO2022171131A1 true WO2022171131A1 (fr) 2022-08-18

Family

ID=82838197

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2022/075684 WO2022171131A1 (fr) 2021-02-15 2022-02-09 Procédé et appareil de sélection d'ancrage de session pour dispositif terminal

Country Status (1)

Country Link
WO (1) WO2022171131A1 (fr)

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN109548186A (zh) * 2017-07-28 2019-03-29 展讯通信（上海）有限公司 Pdu会话锚点的重定位方法及装置、可读存储介质及设备
CN110035562A (zh) * 2018-01-12 2019-07-19 华为技术有限公司 会话管理方法、设备及系统
CN110167195A (zh) * 2018-02-13 2019-08-23 华为技术有限公司 通信方法和通信装置
US20200351985A1 (en) * 2018-01-12 2020-11-05 Huawei Technologies Co., Ltd. Session Management Method, Device, and System

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN109548186A (zh) * 2017-07-28 2019-03-29 展讯通信（上海）有限公司 Pdu会话锚点的重定位方法及装置、可读存储介质及设备
CN110035562A (zh) * 2018-01-12 2019-07-19 华为技术有限公司 会话管理方法、设备及系统
US20200351985A1 (en) * 2018-01-12 2020-11-05 Huawei Technologies Co., Ltd. Session Management Method, Device, and System
CN110167195A (zh) * 2018-02-13 2019-08-23 华为技术有限公司 通信方法和通信装置

Similar Documents

Publication Publication Date Title
US10880792B2 (en) Nodes and method for determining target PLMN ID and target cell ID
US11398940B2 (en) Indication of subcarrier spacing numerology
US20200187092A1 (en) Access Category and Establishment Cause
US20220240173A1 (en) Method and apparatus for managing network slice for terminal device
US11968729B2 (en) Method and apparatus for allocating PDU session ID for terminal device
US11716739B2 (en) Method and apparatus for uplink transmission
US11337112B2 (en) Methods and devices for load balancing across band-width parts
WO2022171131A1 (fr) Procédé et appareil de sélection d'ancrage de session pour dispositif terminal
US20220322335A1 (en) Overheating configuration in (ng) en-dc
US20230403111A1 (en) Method and apparatus for dual connectivity
US20220191766A1 (en) Ue, network nodes for handling ue category information
KR20230053679A (ko) Rach-보고들을 핸들링하기 위한 ue, 네트워크 노드들 및 이들에 의해 수행되는 방법들
WO2020083070A1 (fr) Conception de largeur de bande de porteuse asymétrique pour un système de communication sans fil
WO2022095630A1 (fr) Procédé et appareil d'attribution de préfixe d'adresse réseau
WO2022199411A1 (fr) Procédé et appareil pour fournir une configuration pour servir un dispositif terminal
US20220225444A1 (en) Method and Apparatus for Network Function Managing NIDD Session
WO2022231505A1 (fr) Nœud de réseau radio, équipement utilisateur, nœud de réseau et procédés mis en œuvre dans ce cadre
CN118138457A (zh) 提供用于服务终端设备的配置的方法和装置

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

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

Country of ref document: EP

Kind code of ref document: A1