WO2021000887A1 - Lcs和lpp程序的nas信令减少的方法 - Google Patents

Lcs和lpp程序的nas信令减少的方法 Download PDF

Info

Publication number
WO2021000887A1
WO2021000887A1 PCT/CN2020/099698 CN2020099698W WO2021000887A1 WO 2021000887 A1 WO2021000887 A1 WO 2021000887A1 CN 2020099698 W CN2020099698 W CN 2020099698W WO 2021000887 A1 WO2021000887 A1 WO 2021000887A1
Authority
WO
WIPO (PCT)
Prior art keywords
message
information element
nas
transmission method
positioning
Prior art date
Application number
PCT/CN2020/099698
Other languages
English (en)
French (fr)
Inventor
薛学儒
宁涛
纳耶米·马各
皇甫建君
Original Assignee
联发科技（新加坡）私人有限公司
薛学儒
宁涛
纳耶米·马各
皇甫建君
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 联发科技（新加坡）私人有限公司, 薛学儒, 宁涛, 纳耶米·马各, 皇甫建君 filed Critical 联发科技（新加坡）私人有限公司
Priority to CN202080038256.5A priority Critical patent/CN113875274B/zh
Priority to US17/623,739 priority patent/US20220256309A1/en
Priority to EP20835536.2A priority patent/EP3993464A4/en
Publication of WO2021000887A1 publication Critical patent/WO2021000887A1/zh

Links

Images

Classifications

    • 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]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/02—Services making use of location information
    • H04W4/029—Location-based management or tracking services
    • G—PHYSICS
    • G01—MEASURING; TESTING
    • G01S—RADIO DIRECTION-FINDING; RADIO NAVIGATION; DETERMINING DISTANCE OR VELOCITY BY USE OF RADIO WAVES; LOCATING OR PRESENCE-DETECTING BY USE OF THE REFLECTION OR RERADIATION OF RADIO WAVES; ANALOGOUS ARRANGEMENTS USING OTHER WAVES
    • G01S5/00—Position-fixing by co-ordinating two or more direction or position line determinations; Position-fixing by co-ordinating two or more distance determinations
    • G01S5/0009—Transmission of position information to remote stations
    • G01S5/0045—Transmission from base station to mobile station
    • G01S5/0063—Transmission from base station to mobile station of measured values, i.e. measurement on base station and position calculation on mobile
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00—Data switching networks
    • H04L12/28—Data switching networks characterised by path configuration, e.g. LAN [Local Area Networks] or WAN [Wide Area Networks]
    • H04L12/46—Interconnection of networks
    • H04L12/4633—Interconnection of networks using encapsulation techniques, e.g. tunneling
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L5/00—Arrangements affording multiple use of the transmission path
    • H04L5/003—Arrangements for allocating sub-channels of the transmission path
    • H04L5/0053—Allocation of signaling, i.e. of overhead other than pilot signals
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/01—Protocols
    • H04L67/12—Protocols specially adapted for proprietary or special-purpose networking environments, e.g. medical networks, sensor networks, networks in vehicles or remote metering networks
    • H04L67/125—Protocols specially adapted for proprietary or special-purpose networking environments, e.g. medical networks, sensor networks, networks in vehicles or remote metering networks involving control of end-device applications over a network
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/50—Network services
    • H04L67/52—Network services specially adapted for the location of the user terminal
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L69/00—Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass
    • H04L69/30—Definitions, standards or architectural aspects of layered protocol stacks
    • H04L69/32—Architecture of open systems interconnection [OSI] 7-layer type protocol stacks, e.g. the interfaces between the data link level and the physical level
    • H04L69/321—Interlayer communication protocols or service data unit [SDU] definitions; Interfaces between layers
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L69/00—Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass
    • H04L69/30—Definitions, standards or architectural aspects of layered protocol stacks
    • H04L69/32—Architecture of open systems interconnection [OSI] 7-layer type protocol stacks, e.g. the interfaces between the data link level and the physical level
    • H04L69/322—Intralayer communication protocols among peer entities or protocol data unit [PDU] definitions
    • H04L69/329—Intralayer communication protocols among peer entities or protocol data unit [PDU] definitions in the application layer [OSI layer 7]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/02—Services making use of location information
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/12—Messaging; Mailboxes; Announcements
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W64/00—Locating users or terminals or network equipment for network management purposes, e.g. mobility management
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/20—Manipulation of established connections
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/20—Manipulation of established connections
    • H04W76/27—Transitions between radio resource control [RRC] states
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L69/00—Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass
    • H04L69/22—Parsing or analysis of headers
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/12—Messaging; Mailboxes; Announcements
    • H04W4/14—Short messaging services, e.g. short message services [SMS] or unstructured supplementary service data [USSD]

Definitions

  • the present invention relates to signal transmission in the Narrowband Internet of Things (NB-IOT), especially to the non-access layer (NAS, non-access) of LCS (location services) and LPP (LTE Positioning Protocol, LTE positioning protocol) stratum) method of transmission.
  • NB-IOT Narrowband Internet of Things
  • NAS non-access layer
  • LPP LTE Positioning Protocol, LTE positioning protocol
  • Narrowband Internet of Things represents an important growth opportunity for the Third Generation Partnership Project (3GPP) ecosystem.
  • MTC Machine type communication
  • NB-IoT Narrowband Internet of Things
  • 3GPP Third Generation Partnership Project
  • NB-IoT In order to support IoT, 3GPP has designated NB-IoT as one of the new cellular radio technologies. It inherits LTE general functions and is simplified and optimized to provide lower power consumption, better coverage, and support A large number of low throughput devices with relaxed latency requirements.
  • the 3GPP work item CIoT-CT defines the phase 3 protocol aspects of CIoT based on the phase 2 standardization developed by SA2.
  • CIoT-CT introduces the control plane (control plane) CIoT EPS optimization function to support the efficient transmission of user data (IP, non-IP) or SMS messages on the control plane through MME (Mobility Management Entity) without Trigger data radio bearer establishment.
  • control plane control plane
  • MME Mobility Management Entity
  • control plane CIoT EPS optimization enables the UE to transmit a small amount of user data through the control plane service request, according to the current specification TS 24.301, since the control plane service request and the uplink general NAS transmission (which includes LPP or LCS messages) must go through the radio link Channels are sent separately, resulting in inefficient transmission of LPP/LCS messages during LPP/LCS procedures (such as location request service procedures).
  • the control plane service request only includes the ESM message container (message container) information element (information element, abbreviated as IE) and the NAS message container information element is used to transmit data.
  • the ESM message container IE is only allowed to include ESM Data transmission messages and NAS message container IE are used for SMS transmission.
  • the ESM message container is used for user data transmission (only ESM data transmission is allowed), and the NAS message container is used for SMS transmission.
  • the invention relates to a method for reducing NAS signaling of LPP and LCS procedures initiated by UE in EMM idle mode or EMM registration state.
  • the method of the present invention includes: starting the LPP or LCS program; encapsulating the LPP or LCS message in a specific IE; and using the specific IE to send the LPP or LCS message.
  • the LPP/LCS message is encapsulated into the IE in the content of the control plane service request message.
  • the specific IE is the EMM message container IE.
  • the EMM message container IE has an EMM message container type indication.
  • the specific IE is the uplink general NAS transmission message container IE.
  • the specific IE is the payload container IE.
  • the load container IE has a load container type indication.
  • the specific IE is the NAS message container IE.
  • the NAS message container IE has a NAS message container type indication.
  • the specific IE is the new NAS message container IE.
  • the specific IE is a new general message container IE.
  • the new general message container IE has a general message container type indication and/or additional information IE.
  • the present invention also provides a method for supporting a CIoT EPS optimized MME, which includes receiving an initial UE message with an LPP or LCS message included in a NAS PDU, extracting the LPP or LCS message from the NAS PDU, and sending it through the LCS-AP protocol LPP or LCS message.
  • the LPP or LCS message is a connection-oriented information message.
  • Figure 1 shows a block diagram of a wireless network.
  • Figure 2 shows the process of the UE initiating a location service request in idle mode.
  • Figure 3 shows the process in which the UE initiates a location service request in the connected mode.
  • Figure 4 shows a flow chart of the UE sending an LCS message to the network.
  • Figure 5 shows a flow chart of the MME sending the LCS message to the E-SMLC when the initial UE message is received.
  • Figure 6 shows a flow chart of the UE sending an LPP message to the network.
  • Figure 7 shows a flow chart of the MME sending the LPP message to the E-SMLC when the initial UE message is received.
  • the present invention relates to a method for reducing NAS signaling of LPP and LCS procedures initiated by UE in EMM idle mode and EMM registration state.
  • Idle mode means that the UE is in EMM idle mode and EMM registration state
  • connected mode means that the UE is in EMM connection mode and EMM registration state.
  • the disclosed method involves multiple methods of encapsulating LPP/LCS messages into control plane service requests.
  • LTE Long Term Evolution
  • E-UTRAN Evolved Universal Terrestrial Radio Access Network
  • EPS Evolved Packet System
  • Location service refers to any service based on or related to location information.
  • the location information may include any information related to the location of the UE, for example, location estimation, measurement, and so on.
  • Location services may include positioning, which refers to the function of determining the geographic location of a target UE.
  • the messages supporting location services can be carried as part of the signaling transmitted between various network entities, and various network entities generally have different protocols, interfaces, and interfaces depending on the network. And signaling messages.
  • LTE positioning protocol LTE positioning protocol
  • RRLP radio resource LCS protocol
  • RRC radio resource control
  • C.S0022 also known as IS-801
  • the positioning protocol can be used to coordinate and control the positioning of the UE.
  • FIG. 1 shows a block diagram of a wireless network, which can be an LTE network or some other wireless network.
  • the UE can communicate with an eNB in a radio access network (RAN) to obtain communication services.
  • the RAN may include other network entities not shown in FIG. 1 for simplification and may also be referred to as Evolved Universal Terrestrial Radio Access Network (E-UTRAN).
  • E-UTRAN Evolved Universal Terrestrial Radio Access Network
  • An eNB may also be called a base station, Node B, access point, and so on.
  • the UE may also be called a mobile station, terminal, access terminal, subscriber unit, station, and so on.
  • the UE may be a cell phone, a personal digital assistant (PDA), a wireless device, a wireless modem, a wireless router, a laptop computer, a telemetry device, a tracking device, and so on.
  • PDA personal digital assistant
  • the eNB can communicate with the MME, and the MME can perform various control functions, such as mobility management, gateway selection, authentication, and bearer management.
  • the MME and E-SMLC can be simplified into other network communication entities not shown in FIG. 1.
  • the E-SMLC may support UE-based, UE-assisted, network-based, and/or network-assisted positioning methods and may support one or more MMEs.
  • E-SMLC can perform various functions to support location services.
  • LTE Long Term Evolution
  • NAS MAC
  • RLC Radio Link Control
  • 3GPP TS 23.271 3GPP TS 24.301
  • 3GPP TS 36.321 3GPP TS 36.322
  • 3GPP TS 36.323 3GPP TS 36.331
  • 3GPP TS 36.413 RFC 2960, RFC 791 and 2460, respectively
  • PDCP RRC
  • S1-AP S1-AP
  • SCTP IP
  • the public can obtain the aforementioned 3GPP TS documents from 3GPP, and RFC documents from the Internet Engineering Task Force (IETF).
  • IETF Internet Engineering Task Force
  • the UE may exchange (e.g., send and/or receive) LPP/LCS messages about positioning services with the E-SMLC. These LPP/LCS messages are transmitted as efficiently as possible between UE and E-SMLC via network entities such as eNB and MME.
  • network entities such as eNB and MME.
  • the messages about location services (eg, LPP/LCS messages) exchanged between UE and E-SMLC can be encapsulated in NAS messages and transmitted via network entities such as eNB and MME .
  • NAS messages can be used to transmit EPS Mobility Management (EMM) messages and EPS Session Management (ESM) messages exchanged between MME and UE.
  • EMM EPS Mobility Management
  • ESM EPS Session Management
  • the functionality of NAS can be extended to support the transmission of LPP/LCS related messages.
  • LCS related messages can be exchanged between the UE and the E-SMLC.
  • LCS related messages can be encapsulated in NAS messages for transmission between UE and MME.
  • These NAS messages can be further encapsulated in RRC messages for transmission between the UE and the eNB using various protocols for the above entities.
  • These NAS messages can also be encapsulated in SlAP NAS transmission messages (which are messages about SlAP) for transmission between the eNB and the MME.
  • LCS related messages can also be encapsulated in LCS-AP messages for transmission between MME and E-SMLC.
  • LCS-related messages for example, LPP messages
  • NAS is used between MME and UE to transmit messages related to mobility management and session management. Extending NAS to transmit LCS-related messages will reuse existing protocols and may not require the definition, implementation, and testing of new protocols. In addition, the transmission of LCS-related messages within the NAS message will not add additional impact to the eNB (currently the impact of the transmission of EMM and ESM messages on the eNB).
  • Embodiment 1 UE starts location service request process in idle mode
  • Figure 2 shows the process of the UE initiating a location service request in idle mode.
  • the UE is in idle mode and needs to use location services. It has an LCS message to be sent and triggers a service request (SR) process. Random access and RRC connection establishment (Random Access and RRC Connection Establishment) are performed between the UE and the eNB.
  • SR service request
  • Random access and RRC connection establishment Random Access and RRC Connection Establishment
  • the UE sends an RRC Connection Setup Complete (RRC Connection Setup Complete) message carrying a NAS message to the eNB, where the NAS message contains LCS related messages.
  • LCS related messages can be exchanged between UE and E-SMLC.
  • the eNB After receiving the RRC message, the eNB sends an S1AP message INITIAL UE MESSAGE to the MME, and forwards the NAS message to the MME.
  • the LCS related messages can be encapsulated in the NAS message for transmission between the UE and the MME.
  • the NAS message may also be encapsulated in an SlAP NAS transmission message (which is a message about SlAP) for transmission between the eNB and the MME.
  • the MME After the MME receives the NAS message, it sends the LCS-AP message LOCATION REQUEST to the E-SMLC, where the LCS-related message can be encapsulated in the LCS-AP message for transmission between the MME and the E-SMLC, so that the E-SMLC SMLC understands that UE has a location service requirement.
  • the MME sends an S1AP message to the eNB in the downlink NAS transport (S1AP: Downlink NAS Transport) and forwards the NAS: Service Accept message to the eNB.
  • S1AP Downlink NAS Transport
  • the eNB transfers the NAS message Service Accept to the UE in the RRC DL Information Transfer (RRC DL Information Transfer) message.
  • RRC DL Information Transfer RRC DL Information Transfer
  • the exchange of positioning capabilities is realized between E-SMLC and UE through OTDOA positioning mode.
  • the E-SMLC when the E-SMLC needs to send an LPP message to the UE as part of the LPP positioning activity, the E-SMLC will send the LCS-AP carrying the LPP: Connection Oriented Information (Connection Oriented Information) to the MME.
  • MME includes session identifier (session identifier/Routing identifier), which is associated with the positioning session between MME and E-SMLC.
  • MME transmits NAS in S1AP: Downlink NAS Transport (S1AP: Downlink NAS Transport) message The message is forwarded to the eNB.
  • the eNB transfers the NAS message Downlink Generic NAS transport to the UE in the RRC DL Information Transfer (RRC DL Information Transfer) message.
  • RRC DL Information Transfer RRC DL Information Transfer
  • the UE receives assistance data from the E-SMLC for positioning measurement. Subsequently, the eNB sends an RRC Connection Release (RRC Connection Release) message to the UE. UE performs OTDOA measurement. The UE has the LPP message to be sent and triggers the CPSR. Random access and RRC connection establishment (Random Access and RRC Connection Establishment) are performed between the UE and the eNB.
  • RRC Connection Release RRC Connection Release
  • LPP related messages are exchanged again between the UE and the E-SMLC.
  • the UE sends an RRC Connection Setup Complete (RRC Connection Setup Complete) message carrying NAS to the eNB.
  • the NAS message carried at this time is a Control Panel Service Request.
  • LPP-related messages such as providing location information, are encapsulated in NAS message.
  • the eNB sends the S1AP: initial UE message to the MME.
  • LPP-related messages can be encapsulated in NAS messages so that they can be transmitted between UE and MME. In other embodiments, these NAS messages can also be encapsulated in SlAP NAS transmission messages (which are messages about SlAP). Used for transmission between eNB and MME.
  • the MME sends LCS-AP: Connection Oriented Information (Connection Oriented Information) to the E-SMLC.
  • LPP-related messages can be encapsulated in the LCS-AP message for transmission between the MME and the E-SMLC.
  • the MME forwards the NAS: Service Accept information to the eNB in the S1AP: Downlink NAS Transport (S1AP: Downlink NAS Transport) message.
  • S1AP Downlink NAS Transport
  • the eNB forwards the NAS message to the UE in the RRC DL Information Transfer (RRC DL Information Transfer) message.
  • RRC DL Information Transfer RRC DL Information Transfer
  • the E-SMLC may also transmit the LCS-AP: Location Response (LCS-AP: Location Response) message including the longitude and latitude to the UE via the MME and the eNB.
  • LCS-AP Location Response
  • Embodiment 2 UE starts location service request process in connected mode
  • Figure 3 shows the process in which the UE initiates a location service request in the connected mode.
  • the UE is in connected mode and has an LCS message to be sent.
  • the UE sends an RRC UL Information Transfer (RRC UL Information Transfer) message carrying NAS to the eNB.
  • LCS related messages can be exchanged between UE and E-SMLC, and LCS related messages can be encapsulated in NAS messages for transmission between UE and MME.
  • the eNB sends an S1AP: Uplink NAS Transport (S1AP: Uplink NAS Transport) message to the MME.
  • S1AP Uplink NAS Transport
  • SlAP Uplink NAS Transport
  • MME sends LCS-AP: location request to E-SMLC
  • LCS related messages can be encapsulated in LCS-AP message for transmission between MME and E-SMLC.
  • the exchange of positioning capabilities is realized between E-SMLC and UE through OTDOA positioning mode.
  • the E-SMLC When the E-SMLC needs to send an LPP message to the UE as part of the LPP positioning activity, the E-SMLC sends the LCS-AP connection-oriented information (LCS-AP: Connection Oriented Information) carrying the LPP to the MME.
  • MME includes session identifier (session identifier/Routing identifier), which is associated with the positioning session between MME and E-SMLC.
  • MME transmits NAS in S1AP: Downlink NAS Transport (S1AP: Downlink NAS Transport) message The message is forwarded to the eNB.
  • the eNB transfers the NAS transmission message to the UE in an RRC DL Information Transfer (RRC DL Information Transfer) message.
  • RRC DL Information Transfer RRC DL Information Transfer
  • the UE receives assistance data from the E-SMLC for positioning measurement. Subsequently, the eNB sends an RRC Connection Release (RRC Connection Release) message to the UE. Subsequently, the UE performs OTDOA measurement. The UE has an LPP message to be sent and triggers an SR. Random access and RRC connection establishment (Random Access and RRC Connection Establishment) are performed between the UE and the eNB.
  • LPP related messages are exchanged again between the UE and the E-SMLC.
  • the UE sends an RRC Connection Setup Complete (RRC Connection Setup Complete) message carrying the NAS to the eNB.
  • LPP related messages can be encapsulated in NAS messages for transmission between UE and MME.
  • the eNB sends the S1AP: initial UE message to the MME.
  • SlAP NAS transmission messages (which are messages about SlAP) for transmission between the eNB and the MME.
  • the MME sends LCS-AP: Connection Oriented Information (Connection Oriented Information) to the E-SMLC.
  • LPP-related messages can be encapsulated in the LCS-AP message for transmission between the MME and the E-SMLC.
  • the MME forwards the NAS: Service Accept information to the eNB in the S1AP: Downlink NAS Transport (S1AP: Downlink NAS Transport) message.
  • S1AP Downlink NAS Transport
  • the eNB transfers the NAS message to the UE in an RRC DL Information Transfer (RRC DL Information Transfer) message.
  • RRC DL Information Transfer RRC DL Information Transfer
  • the E-SMLC may also transmit an LCS-AP location response (LCS-AP: Location Response) message including the longitude and latitude to the UE via the MME and the eNB.
  • LCS-AP Location Response
  • the following exemplarily describes an embodiment of sending LCS/LPP messages performed by the UE/MME.
  • Embodiment 3 Method for UE to send LCS message/LPP message
  • FIG. 4 shows a flow chart of the UE sending the LCS message to the network. As shown in FIG. 4, in step 402, the UE has an LCS message to be sent. Subsequently, in step 404, it is determined whether the UE is in idle mode or connected mode.
  • step 406 If the UE is in idle mode, the process goes to step 406, and the LCS message is encapsulated into the control plane service request message. Subsequently, in step 408, a control plane service request message is sent.
  • step 410 the LCS message is encapsulated into an uplink generic NAS transport message (Uplink Generic NAS Transport Message). Subsequently, in step 412, the uplink general NAS transmission message is sent.
  • uplink generic NAS transport message Uplink Generic NAS Transport Message
  • Embodiment 3-2 shows a flow chart of the MME sending the LCS message to the E-SMLC when the initial UE message is received.
  • an initial UE message [NAS PDU (LCS message)] is received.
  • the LCS message is extracted from the NAS PDU.
  • the LCS message is sent through the LCS-AP protocol.
  • FIG. 6 shows a flow chart of the UE sending the LPP message to the network. As shown in FIG. 6, in step 602, the UE has an LPP message to be sent. Subsequently, in step 604, it is determined whether the UE is in idle mode or connected mode.
  • step 606 If the UE is in idle mode, the process goes to step 606, and the LPP message is encapsulated into the control plane service request message. Subsequently, in step 608, a control plane service request message is sent.
  • step 610 the LPP message is encapsulated into an uplink generic NAS transport message (Uplink Generic NAS Transport Message). Subsequently, in step 612, the uplink general NAS transmission message is sent.
  • uplink generic NAS transport message Uplink Generic NAS Transport Message
  • FIG. 7 shows a flow chart of the MME sending the LPP message to the E-SMLC when the initial UE message is received.
  • an initial UE message [NAS PDU (LPP message)] is received.
  • the LPP message is retrieved from the NAS PDU.
  • the LPP message is sent through the LCS-AP protocol.
  • Embodiment 4 Method of encapsulating LPP/LCS message into control plane service request
  • the following embodiments provide multiple methods for encapsulating LPP/LCS messages into control plane service requests, which will be discussed one by one below.
  • Embodiment 4-1 Adding the EMM message container IE to the control plane service request
  • the EMM message container may have an EMM message container type indication (EMM message container type indication).
  • EMM message container type indication EMM message container type indication
  • octet 4 to octet n are the contents of the EMM message container.
  • This IE may contain any EMM PDU defined in subclause 8.2.
  • Embodiment 4-2 Adding the uplink general NAS transport message container IE to the control plane service request
  • the optional IE "Uplink Generic NAS Transport message container” is added to the control plane service request, as shown in Table 4.
  • Uplink generic NAS transport message container can be used for, for example, LCS/LPP message transmission.
  • the information elements of the uplink general NAS transmission message container can refer to Table 5 and Table 6:
  • Table 6 The contents of the uplink general NAS transmission message container
  • Embodiment 4-3 Modify the usage of NAS message container IE in the control plane service request
  • Embodiment 4-3-1 LCS/LPP messages (in addition to SMS) are allowed to be encapsulated in the NAS message container, as shown in Table 7.
  • NAS message container type (NAS message container type)
  • the content of the row Xx in the IEI column represents the new information added.
  • the UE wants to send an ESM message to the network, the UE should include the information element ESM message container. If the UE is in EMM-IDLE mode and it wants to send application messages to the network, the UE should include the information element NAS message container type. If the UE wants to send a pending (pending) SMS message, the UE may include the information element NAS message container type.
  • the NAS message container information element is used not only for SMS transmission, but also for LPP/LCS message transmission. That is, the NAS message container information element may include SMS messages (ie, CP-DATA, CP-ACK, or CP-ERROR), or application messages that depend on specific applications.
  • NAS message container type (NAS message container type) is a new optional information element (IE) in the control plane service request, which allows the UE to notify the network of the piggy-backed message contained in the NAS message container Types of.
  • the NAS message container information element is used to specify the type of NAS message container content.
  • the NAS message container type information element is encoded as shown in the following table.
  • the EPS update result is the first type (type 1) information element:
  • Embodiment 4-3-2 It is allowed to encapsulate LCS/LPP messages in NAS Message Container 2 (NAS Message Container 2), as shown in Table 9.
  • NAS message container 2 (NAS message container 2) has been added. If the UE is in EMM-IDLE mode and has pending application messages to be sent, the UE should include this information element.
  • This IE is used to encapsulate the application message that is transferred between the UE and the network.
  • the IE may be, for example, a dedicated information element used for LCS/LPP messaging in CPSR.
  • the NAS message container information element is encoded as shown in the following table.
  • the NAS message container is a type 6 information element with a minimum length of 4octet and a maximum length of 65536octet:
  • Embodiment 4-3-3 It is allowed to encapsulate LCS/LPP messages in Generic message container (Generic message container) IE, as shown in Table 11.
  • Generic message container Generic message container
  • the new IEs are: Generic message container type, Generic message container, and additional Information (Additional information).
  • the UE may include a general message container type information element.
  • the UE may include a general message container information element.
  • the UE may include additional information information elements.
  • Embodiment 4-4 It is allowed to encapsulate LCS/LPP messages (in addition to SMS) in one or more Payload Container IEs, as shown in Table 12 and Table 13. This method can support multiple payloads to include multiple messages in one IE. For example, one or more SMS messages and one or more LCS/LPP messages.
  • the content in the row of the TBD in the IEI column represents the new information added, and the newly added IEs are: payload container type (Payload Container type) and payload container (Payload Container).
  • the UE can save uplink NPUSCH messages. In the absence of UL authorization, the UE can save random access procedures in the connected mode.
  • MOLR mobile terminal Location request initiated
  • MT-LR location request terminated by mobile terminal

Landscapes

  • Engineering & Computer Science (AREA)
  • Signal Processing (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Computer Security & Cryptography (AREA)
  • Remote Sensing (AREA)
  • Radar, Positioning & Navigation (AREA)
  • General Physics & Mathematics (AREA)
  • Physics & Mathematics (AREA)
  • Health & Medical Sciences (AREA)
  • Computing Systems (AREA)
  • General Health & Medical Sciences (AREA)
  • Medical Informatics (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

本发明涉及一种减少UE在EMM空闲模式和EMM注册状态下发起的LPP和LCS程序的NAS信令的方法。所公开的方法涉及将LPP/LCS消息封装到控制平面服务请求中的多种方法。这使得UE与eNB在RRC连接建立过程期间传输LPP/LCS消息成为可能，并且可以被视为控制平面EPS CIoT优化的扩展。

Description

LCS和LPP程序的NAS信令减少的方法 技术领域
本发明有关于窄带物联网(NB-IOT)中的信号传输，尤其有关于LCS(location services，定位服务)和LPP(LTE Positioning Protocol，LTE定位协议)的非接入层(NAS,non-access stratum)传输的方法。
背景技术
机器类型通信(Machine type communication，简写为MTC))，或者更具体地来说，窄带物联网(NB-IoT)代表了第三代合作伙伴计划(3GPP)生态系统的重要增长机遇。窄带物联网是由3GPP制定的低功率广域覆盖的无线电技术标准，以支援广泛的物联网应用与服务。
为支持IoT，3GPP已将NB-IoT指定为新的蜂窝无线电技术之一，其通过继承LTE通用功能，并经过简化和优化，以提供更低的功耗，更好地覆盖范围，并支持具有宽松延迟要求的大量低吞吐量设备。3GPP工作项CIoT-CT基于SA2开发的第2阶段标准化定义了CIoT的第3阶段协议方面。CIoT-CT引入了控制平面(control plane)CIoT EPS优化功能，以支持通过MME(Mobility Management Entity，移动性管理实体)在控制平面上高效传输用户数据(IP、非IP)或SMS消息，而无需触发数据无线承载建立(data radio bearer establishment)。
尽管控制平面CIoT EPS优化使UE能够通过控制平面服务请求传输少量用户数据，但是遵循当前规范TS 24.301，由于控制平面服务请求和上行链路通用NAS传输(其包括LPP或LCS消息)必须通过无线电链路单独发送，导致在LPP/LCS程序(procedure)(例如位置请求服务程序)期间LPP/LCS消息的低效传输。如下表表1所示，控制平面服务请求仅包括ESM消息容器(message container)信息元素(information element,简写为IE)和NAS消息容器信息元素用于传输数据，其中ESM消息容器IE仅允许包括ESM数据传输消息并且NAS消息容器IE用于SMS传输。
表1：控制平面服务请求消息内容
Figure PCTCN2020099698-appb-000001
其中，ESM消息容器用于用户数据传输(仅允许ESM数据传输)，NAS消息容器用于SMS传输。
目前，如何有效地传输更高层(高于NAS)应用协议数据的LPP/LCS消息尚未在TS 24.301中得到解决。这对于需要频繁调用位置服务的功耗敏感的IoT设备尤其重要，例如在跟踪应用程序中。
发明内容
本发明涉及一种减少UE在EMM空闲模式或EMM注册状态下发起的LPP和LCS程序的NAS信令的方法。
本发明的方法包括：启动LPP或LCS程序；在特定IE中封装该LPP或LCS消息；以及利用该特定IE发送LPP或LCS消息。
其中，将该LPP/LCS消息封装到控制平面服务请求消息内容中的IE中。
其中，该特定IE为EMM消息容器IE。
其中，该EMM消息容器IE具有EMM消息容器类型指示。
其中，该特定IE为上行通用NAS传输消息容器IE。
其中，该特定IE为载荷容器IE。
其中，该载荷容器IE具有载荷容器类型指示。
其中，该特定IE为NAS消息容器IE。
其中，该NAS消息容器IE具有NAS消息容器类型指示。
其中，该特定IE为新NAS消息容器IE。
其中，该特定IE为新的通用消息容器IE。
其中，该新的通用消息容器IE具有通用消息容器类型指示和/或附加信息IE。
本发明还提供一种支持CIoT EPS优化的MME的方法，包括接收具有包括在NAS PDU中的LPP或LCS消息的初始UE消息，从NAS PDU中提取LPP或LCS消息，以及通过LCS-AP协议发送LPP或LCS消息。
其中，该LPP或LCS消息为面向连接的信息消息。
附图说明
通过阅读以下的具体实施方式并参考附图，本发明可被完全理解，其中：
图1示出了无线网络的框图。
图2示出了UE在空闲模式下启动位置服务请求的过程。
图3示出了UE在连接模式下启动位置服务请求的过程。
图4示出了UE将LCS消息发送到网络的流程图。
图5示出了在接收到初始UE消息时，MME将LCS消息发送到E-SMLC的流程图。
图6示出了UE将LPP消息发送到网络的流程图。
图7示出了在接收到初始UE消息时，MME将LPP消息发送到E-SMLC的流程图。
具体实施方式
本发明涉及一种减少UE在EMM空闲模式和EMM注册状态下发起的LPP和LCS程序的NAS信令的方法。请注意，在下文中，“空闲模式”表示UE处于EMM空闲模式和EMM注册状态；“连接模式”表示UE处于EMM连接模式和 EMM注册状态。
所公开的方法涉及将LPP/LCS消息封装到控制平面服务请求中的多种方法。
这使得UE与eNB在RRC连接建立过程期间传输LPP/LCS消息成为可能，并且可以被视为控制平面EPS CIoT优化的扩展。
以下描述的实施例为本发明实施的较佳实施例，且实施例通过结合附图进行了说明。为了解决上述问题，本说明书提出以下解决方案。
本文中所描述的用于传输LCS和LPP相关消息的技术可被用于各种无线网络和无线电技术，包括由名为“第三代合作伙伴项目(3GPP)”和“第三代合作伙伴项目2(3GPP2)”的组织定义的那些技术。例如，这些技术可被用于实现由3GPP定义的演进通用地面无线电接入网(E-UTRAN)的长期演进(LTE)网络。LTE是3GPP演进分组系统(EPS)的一部分。在来自3GPP的文档中描述了LTE、E-UTRA和EPS。这些技术也可用于其他无线网络和其他无线电技术。
本文中所描述的技术也可被用于能支持位置服务的各种控制层面的位置解决方案或架构。位置服务指的是任何基于位置信息或与位置信息有关的服务。位置信息可包括与UE位置有关的任何信息，例如，位置估计、测量等。位置服务可包括定位，定位指的是确定目标UE的地理位置的功能。在控制层面的位置解决方案中，支持位置服务的消息可作为在各种网络实体之间传递的信令的一部分被携带，而各种网络实体一般情况下具有因网络而异的协议、接口、和信令消息。
在本文中所描述的技术还可被用于各种定位协议，诸如(i)由3GPP定义的LTE定位协议(LPP)、无线电资源LCS协议(RRLP)、以及无线电资源控制(RRC)和(ii)由3GPP2定义的C.S0022(也称为IS-801)。定位协议可被用于协调和控制对UE的定位。
为了清楚起见，LTE术语被用在以下大部分描述中。本领域技术人员了解各术语的含义以及各常用术语之间的关系，本说明书并不做进一步解释。
图1示出了无线网络的框图，它可以是LTE网络或者其他某种无线网络。UE可与无线电接入网(RAN)中的eNB通信以获得通信服务。RAN可包括为简单化而没有在图1中示出的其他网络实体并且也可被称为演进通用地面无线电接入网(E-UTRAN)。eNB也可被称为基站、B节点、接入点等等。UE也可 被称为移动站、终端、接入终端、订户单元，站等等。UE可以是蜂窝电话、个人数字助理(PDA)、无线设备、无线调制解调器、无线路由器、膝上型计算机、遥测设备、跟踪设备等等。
eNB可与MME通信，MME可执行各种控制功能，诸如移动性管理、网关选择、认证、承载方管理等。MME可与E-SMLC简化为没有在图1中示出的其他网络通信实体。E-SMLC可支持基于UE式、UE辅助式、基于网络式、和/或网络辅助式的定位方法并可支持一个或更多个MME。E-SMLC可执行各种功能以支持位置服务。
对于LTE，在3GPP TS 23.271、3GPP TS 24.301、3GPP TS 36.321、3GPP TS 36.322、3GPP TS 36.323、3GPP TS 36.331、3GPP TS 36.413、RFC 2960、RFC 791和2460中分别描述了LCS、NAS、MAC、RLC、PDCP、RRC、S1-AP、SCTP、IP。公众可从3GPP获取上述3GPP TS文档，可从因特网工程任务组(IETF)获取RFC文档。
UE可与E-SMLC交换(例如，发送和/或接收)关于定位服务的LPP/LCS消息。在UE与E-SMLC之间经由诸如eNB和MME之类的网络实体尽可能高效地传输这些LPP/LCS消息。
根据本发明的一方面，在UE与E-SMLC之间交换的关于位置服务的消息(例如，LPP/LCS消息)可被封装在NAS消息中并经由诸如eNB和MME之类的网络实体来传输。NAS消息可被用于传输在MME与UE之间交换的EPS移动性管理(EMM)消息和EPS会话管理(ESM)消息。NAS的功能性可被扩展到支持LPP/LCS相关消息的传输。
LCS相关消息(例如，LPP消息)可在UE与E-SMLC之间交换。LCS相关消息可被封装在NAS消息中以供在UE与MME之间传输。这些NAS消息可被进一步封装在RRC消息中，以便在UE与eNB之间使用用于以上实体的各种协议来进行传输。这些NAS消息也可被封装在SlAP NAS传输消息(其为关于SlAP的消息)中以供在eNB与MME之间进行传输。另外，LCS相关消息也可被封装在LCS-AP消息中以供在MME与E-SMLC之间进行传输。
在UE与MME之间传输包含于NAS消息内部的LCS相关消息(例如，LPP消息)会比使用一些替换协议更高效，例如，要求较少的实现、较少的测试、和/或较少的信令。在MME与UE之间使用NAS来传输与移动性管理和会话管 理有关的消息。扩展NAS以传输LCS相关消息将会重用现有协议并且可不要求定义、实现以及测试新协议。此外，传输处于NAS消息内部的LCS相关消息不会对eNB增添额外影响(目前传输EMM和ESM消息对eNB的影响)。
实施例1:UE在空闲模式下启动位置服务请求过程
(以MOLR OTDOA为例)
图2示出了UE在空闲模式下启动位置服务请求的过程。
如图2所示，UE处于空闲模式中，需要使用定位服务，其具有待发送的LCS消息，并触发服务请求(SR)过程。UE和eNB之间进行随机接入和RRC连接建立(Random Access and RRC Connection Establishment)。
在这之后，UE向eNB发送携带NAS消息的RRC连接建立完成(RRC Connection Setup Complete)消息，其中，NAS消息中包含LCS相关消息。LCS相关消息可在UE与E-SMLC之间交换。eNB接收到RRC消息后，向MME发送S1AP消息INITIAL UE MESSAGE，将NAS消息转发给MME，其中LCS相关消息可被封装在NAS消息中以供在UE与MME之间传输。在另一实施例中，NAS消息也可被封装在SlAP NAS传输消息(其为关于SlAP的消息)中以供在eNB与MME之间来进行传输。MME收到NAS消息之后，向E-SMLC发送LCS-AP消息LOCATION REQUEST，其中，LCS相关消息可被封装在LCS-AP消息中以供在MME与E-SMLC之间来进行传输，从而E-SMLC了解UE存在定位服务需求。
MME向eNB发送S1AP消息下行链路NAS传输(S1AP:Downlink NAS Transport)中将NAS：服务接受(Service Accept)消息转发到eNB。eNB在RRC DL信息传递(RRC DL Information Transfer)消息中将NAS消息Service Accept转给UE。
在E-SMLC和UE之间通过OTDOA定位方式来实现定位能力交换。
具体而言，当E-SMLC需要向UE发送LPP消息作为LPP定位活动的一部分时，E-SMLC将携带LPP的LCS-AP：面向连接的信息(Connection Oriented Information)发送到MME。MME包括会话标识符(session identifier/Routing identifier)，其与MME和E-SMLC之间的定位会话相关联，MME随后在S1AP：下行链路NAS传输(S1AP:Downlink NAS Transport)消息中将 NAS传输消息转发到eNB。eNB在RRC DL信息传递(RRC DL Information Transfer)消息中将NAS消息Downlink Generic NAS transport转给UE。
UE从E-SMLC接收辅助数据以便进行定位测量。随后，eNB向UE发送RRC连接释放(RRC Connection Release)消息。UE进行OTDOA量测。UE具有待发送的LPP消息，并触发CPSR。UE和eNB之间进行随机接入和RRC连接建立(Random Access and RRC Connection Establishment)。
在这之后，在UE与E-SMLC之间再次交换LPP相关消息。UE向eNB发送携带NAS的RRC连接建立完成(RRC Connection Setup Complete)消息，此时携带的NAS消息为控制平面服务请求(Control Panel Service Request)，LPP相关消息，例如，提供位置信息，被封装在NAS消息中。eNB向MME发送S1AP：初始UE消息(initial UE message)。LPP相关消息可被封装在NAS消息中，从而其可在UE与MME之间传输，在其他实施例中，这些NAS消息也可被封装在SlAP NAS传输消息(其为关于SlAP的消息)中以供在eNB与MME之间来进行传输。MME向E-SMLC发送LCS-AP：面向连接的信息(Connection Oriented Information)，LPP相关消息可被封装在LCS-AP消息中以供在MME与E-SMLC之间来进行传输。
MME在S1AP：下行链路NAS传输(S1AP:Downlink NAS Transport)消息中将NAS：服务接受(Service Accept)信息转发到eNB。eNB在RRC DL信息传递(RRC DL Information Transfer)消息中将此NAS消息转给UE。E-SMLC也可将包含经度和纬度的LCS-AP：定位响应(LCS-AP:Location Res ponse)消息经由MME、eNB传送至UE。
实施例2:UE在连接模式下启动位置服务请求过程
(以MOLR OTDOA为例)
图3示出了UE在连接模式下启动位置服务请求的过程。
如图3所示，UE处于连接模式中，具有待发送的LCS消息。
UE向eNB发送携带NAS的RRC UL信息传递(RRC UL Information Tran sfer)消息。LCS相关消息可在UE与E-SMLC之间交换，LCS相关消息可被封装在NAS消息中以供在UE与MME之间传输。eNB向MME发送S1AP:上行链路NAS传输(S1AP:Uplink NAS Transport)消息。这些NAS消息也可被封 装在SlAP上行链路NAS传输(其为关于SlAP的消息)中以供在eNB与MME之间来进行传输。MME向E-SMLC发送LCS-AP：定位请求(location request)，LCS相关消息可被封装在LCS-AP消息中以供在MME与E-SMLC之间来进行传输。
在E-SMLC和UE之间通过OTDOA定位方式来实现定位能力交换。
当E-SMLC需要向UE发送LPP消息作为LPP定位活动的一部分时，E-SMLC将携带LPP的LCS-AP面向连接的信息(LCS-AP:Connection Oriented Information)发送到MME。MME包括会话标识符(session identifier/Routing identifier)，其与MME和E-SMLC之间的定位会话相关联，MME随后在S1AP：下行链路NAS传输(S1AP:Downlink NAS Transport)消息中将NAS传输消息转发到eNB。eNB在RRC DL信息传递(RRC DL Information Transfer)消息中将NAS传输消息转给UE。
UE从E-SMLC接收辅助数据以便进行定位测量。随后，eNB向UE发送RRC连接释放(RRC Connection Release)消息。随后，UE进行OTDOA量测。UE具有待发送的LPP消息，并触发SR。UE和eNB之间进行随机接入和RRC连接建立(Random Access and RRC Connection Establishment)。
在这之后，在UE与E-SMLC之间再次交换LPP相关消息。UE向eNB发送携带NAS的RRC连接建立完成(RRC Connection Setup Complete)消息。LPP相关消息可被封装在NAS消息中以供在UE与MME之间传输。eNB向MME发送S1AP：初始UE消息(initial UE message)。这些NAS消息也可被封装在SlAP NAS传输消息(其为关于SlAP的消息)中以供在eNB与MME之间来进行传输。MME向E-SMLC发送LCS-AP：面向连接的信息(Connection Oriented Information)，LPP相关消息可被封装在LCS-AP消息中以供在MME与E-SMLC之间来进行传输。
MME在S1AP：下行链路NAS传输(S1AP:Downlink NAS Transport)消息中将NAS：服务接受(Service Accept)信息转发到eNB。eNB在RRC DL信息传递(RRC DL Information Transfer)消息中将NAS消息转给UE。
E-SMLC也可将包含经度和纬度的LCS-AP定位响应(LCS-AP:Location Response)消息经由MME、eNB传送至UE。
下面示例性地描述了UE/MME执行的发送LCS/LPP消息的实施例。
实施例3:UE发送LCS消息/LPP消息的方法
实施例3-1:图4示出了UE将LCS消息发送到网络的流程图。如图4所示，在步骤402中，UE具有待被发送的LCS消息。随后，在步骤404中，判断UE是处于空闲模式还是连接模式。
若UE处于空闲模式，流程转至步骤406，将LCS消息封装到控制平面服务请求消息中。随后，在步骤408中，发送控制平面服务请求消息。
若UE处于连接模式，在步骤410中，将LCS消息封装到上行链路通用NAS传输消息(Uplink Generic NAS Transport Message)中。随后，在步骤412，发送该上行链路通用NAS传输消息。
实施例3-2:图5示出了在接收到初始UE消息时，MME将LCS消息发送到E-SMLC的流程图。如图5所示，在步骤502中，接收初始UE消息[NAS PDU(LCS消息)]。随后，在步骤504中，从NAS PDU中撷取(extract)LCS消息。随后，在步骤506中，透过LCS-AP协议发送LCS消息。
实施例3-3:图6示出了UE将LPP消息发送到网络的流程图。如图6所示，在步骤602中，UE具有待被发送的LPP消息。随后，在步骤604中，判断UE是处于空闲模式还是连接模式。
若UE处于空闲模式，流程转至步骤606，将LPP消息封装到控制平面服务请求消息中。随后，在步骤608中，发送控制平面服务请求消息。
若UE处于连接模式，在步骤610中，将LPP消息封装到上行链路通用NAS传输消息(Uplink Generic NAS Transport Message)中。随后，在步骤612，发送该上行链路通用NAS传输消息。
实施例3-4:图7示出了在接收到初始UE消息时，MME将LPP消息发送到E-SMLC的流程图。如图7所示，在步骤702中，接收初始UE消息[NAS PDU(LPP消息)]。随后，在步骤704中，从NAS PDU中撷取LPP消息。随后，在步骤706中，透过LCS-AP协议发送LPP消息。
实施例4:将LPP/LCS消息封装到控制平面服务请求中的方法
以下实施例提供了多种将LPP/LCS消息封装到控制平面服务请求中的方法，以下逐一论述。
实施例4-1：将EMM消息容器IE添加至控制平面服务请求中
将可选IE“EMM消息容器(EMM message container)”添加至控制平面服务请求中，如表2所示。EMM消息容器可具有EMM消息容器类型指示(EMM message container type indication)。请注意，在TS 24.301中，UE可包含上行链路通用NAS传输消息。在一个实施例中，UE不应包含除上行链路通用NAS传输消息之外的任何EMM消息。
表2：控制平面服务请求消息内容
Figure PCTCN2020099698-appb-000002
其中，EMM消息容器的信息元素参考表3所示：
表3：EMM消息容器
Figure PCTCN2020099698-appb-000003
Figure PCTCN2020099698-appb-000004
其中octet 4至octet n(最大65535octet)为EMM消息容器内容。该IE可包含子条款8.2中定义的任意EMM PDU。
实施例4-2：将上行链路通用NAS传输消息容器IE添加至控制平面服务请求中
将可选IE“上行链路通用NAS传输消息容器(Uplink Generic NAS Transport message container)”添加至控制平面服务请求中，如表4所示。
表4：控制平面服务请求消息内容
Figure PCTCN2020099698-appb-000005
在上表中，增加了新的IE：上行链路通用NAS传输消息容器(Uplink generic NAS transport message container)。所添加的上行链路通用NAS传输消息容器可以用于，例如，LCS/LPP消息传输。其中，上行链路通用NAS 传输消息容器的信息元素可参考表5及表6所示：
表5：上行链路通用NAS传输消息容器
Figure PCTCN2020099698-appb-000006
表6：上行链路通用NAS传输消息容器内容
Figure PCTCN2020099698-appb-000007
其中，表5中的上行链路通用NAS传输消息容器内容可以参考表6。
实施例4-3：修改控制平面服务请求中NAS消息容器IE的使用情况
实施例4-3-1：允许将LCS/LPP消息(除SMS之外(in addition to SMS))封装在NAS消息容器中，如表7所示。
表7：控制平面服务请求消息内容
Figure PCTCN2020099698-appb-000008
在上表中，增加了新的IE：NAS消息容器类型(NAS message container type)，IEI栏Xx所在行的内容表示所增加的新的信息。若UE想要发送ESM消息给网络，则UE应包含信息元素ESM消息容器。若UE处于EMM-IDLE模式，且其想要发送应用消息至网络，则UE应当包含信息元素NAS消息容器类型。若UE想要发送未决的(pending)SMS消息，则UE可包含信息元素NAS消息容器类型。
同时，IEI栏67所在行(即NAS message container)的使用被改变。NAS消息容器信息元素不仅用于SMS传输，也用于LPP/LCS消息传输。即NAS消息容器信息元素可包含SMS消息(即，CP-DATA、CP-ACK或CP-ERROR)，或取决于特定应用的应用消息。
可选IE：NAS消息容器类型(NAS message container type)是控制平面服务请求中的新可选信息元素(IE)，其允许UE通知网络NAS消息容器中包含的捎带消息(piggy-backed message)的类型。NAS消息容器信息元素用于指定NAS消息容器内容的类型。NAS消息容器类型信息元素被编码为如下表所示。EPS更新结果是第一类(type 1)信息元素：
表8：EPS更新结果信息元素
Figure PCTCN2020099698-appb-000009
实施例4-3-2：允许将LCS/LPP消息封装在NAS消息容器2(NAS Message Container 2)中，如表9所示。
表9：控制平面服务请求消息内容
Figure PCTCN2020099698-appb-000010
在上表中，IEI栏xx所在行的内容表示所增加的新的信息，增加了新的 IE：NAS消息容器2(NAS message container 2)。若UE处于EMM-IDLE模式，且具有未决的应用消息待发送，则UE应当包含该信息元素。
该IE用于封装在UE和网络之间传递的应用消息。该IE可以是，例如，用于CPSR中的LCS/LPP消息传递的专用信息元素。NAS消息容器信息元素被编码为如下表所示。NAS消息容器是第6类(type 6)信息元素，最小长度为4octet，最大长度为65536octet：
表10：EPS更新结果信息元素
Figure PCTCN2020099698-appb-000011
实施例4-3-3：允许将LCS/LPP消息封装在通用消息容器(Generic message container)IE中，如表11所示。
表11：控制平面服务请求消息内容
Figure PCTCN2020099698-appb-000012
在上表中，IEI栏xx、xy、xz所在行的内容表示所增加的新的信息，新增IE为：通用消息容器类型(Generic message container type)、通用消息容器(Generic message container)、附加信息(Additional information)。
若UE处于EMM-IDLE模式，且具有未决的应用消息待发送，则UE可包含通用消息容器类型信息元素。
若UE处于EMM-IDLE模式，且具有未决的应用消息待发送，则UE可包含通用消息容器信息元素。
若UE想要发送任何附加信息，UE可包含附加信息信息元素。
实施例4-4：允许将LCS/LPP消息(除了SMS之外(in addition to SMS))封装在一个或多个载荷容器(Payload Container)IE中，如表12和表13所示。该方法可以支持多个载荷以在一个IE中包括多个消息。例如，一个或多个SMS 消息和一个或多个LCS/LPP消息。
表12：载荷容器信息元素
Figure PCTCN2020099698-appb-000013
表13：控制平面服务请求消息内容
Figure PCTCN2020099698-appb-000014
在上表中，IEI栏TBD所在行的内容表示所增加的新的信息，新增的IE为：载荷容器类型(Payload Container type)、载荷容器(Payload Container)。
应当注意，本说明书中，部分表格并非完整或者完全的形式。为了简洁起见，本说明书仅提供了与本发明的创新点相关的部分，本领域技术人员在 阅读完本说明书之后，完全了解该表格的含义，以及了解本发明所提供的实施方式，并可在本申请说明书的基础上，容易地修改本发明的实施例或结合本发明揭露的不同实施例。
此外，从RAN的角度来看，根据本发明所揭露的方法，UE可以节省(save)上行链路NPUSCH消息。在缺少UL授权的情况下，UE可以在连接模式下节省随机接入过程。此外，虽然本说明书中部分实施例是以MOLR为例来做出说明，但是，本发明的主要思想(即，允许LPP/LCS消息包括在控制平面服务请求中)适用于MO-LR(移动终端发起的定位请求)和MT-LR(移动终端终结的定位请求)。本领域技术人员在阅读完本说明书的情况下，可了解将本发明的精神用于MT-LR的具体实施，故本说明书不再赘言。
虽然本发明已就较佳实施例揭露如上，然其并非用以限制本发明。本发明所属技术领域中普通技术人员，在不脱离本发明的精神和范围内，当可作各种的变更和润饰。因此，本发明的保护范围当视权利要求书所界定的范围为准。

Claims (17)

  1. 一种消息传输方法，用于支持IoT的装置，该消息传输方法包括：
    启动定位程序；
    在特定信息元素中封装定位相关消息；以及
    利用该特定信息元素发送该定位相关消息。
  2. 如权利要求1所述的消息传输方法，其特征在于，该定位相关消息被封装到控制平面服务请求消息内容中的该特定信息元素中。
  3. 如权利要求2所述的消息传输方法，其特征在于，该特定信息元素为EMM消息容器信息元素。
  4. 如权利要求3所述的消息传输方法，其特征在于，该EMM消息容器信息元素具有EMM消息容器类型指示。
  5. 如权利要求2所述的消息传输方法，其特征在于，该特定信息元素为上行链路通用NAS传输消息容器信息元素。
  6. 如权利要求2所述的消息传输方法，其特征在于，该特定信息元素为载荷容器信息元素。
  7. 如权利要求6所述的消息传输方法，其特征在于，该载荷容器信息元素具有载荷容器类型指示。
  8. 如权利要求2所述的消息传输方法，其特征在于，该特定信息元素为NAS消息容器信息元素。
  9. 如权利要求8所述的消息传输方法，其特征在于，该NAS消息容器信息元素具有NAS消息容器类型指示。
  10. 如权利要求2所述的消息传输方法，其特征在于，该特定信息元素为用于封装该定位相关消息的新NAS消息容器信息元素。
  11. 如权利要求2所述的消息传输方法，其特征在于，该特定信息元素为新的通用消息容器信息元素。
  12. 如权利要求10所述的消息传输方法，其特征在于，该新的通用消息容器信息元素具有通用消息容器类型指示和/或附加信息信息元素。
  13. 如权利要求1所述的消息传输方法，其特征在于，该定位相关消息为LTE定位协议/定位服务消息。
  14. 如权利要求1所述的消息传输方法，其特征在于，该消息传输方法适用于移动终端终结的定位请求和/或移动终端发起的定位请求。
  15. 一种消息传输方法，包括：
    接收初始装置消息，其中该初始装置消息包含封装在特定信息元素中的定位相关消息；
    从该初始装置消息中撷取该定位相关消息；以及
    通过LCS-AP协议发送该定位相关消息。
  16. 如权利要求14所述的消息传输方法，其特征在于，该定位相关消息封装于控制平面服务请求消息内容中的信息元素中。
  17. 如权利要求14所述的消息传输方法，其特征在于，该定位相关消息为LTE定位协议/定位服务消息。
PCT/CN2020/099698 2019-07-01 2020-07-01 Lcs和lpp程序的nas信令减少的方法 WO2021000887A1 (zh)

Priority Applications (3)

Application Number Priority Date Filing Date Title
CN202080038256.5A CN113875274B (zh) 2019-07-01 2020-07-01 Lcs和lpp程序的nas信令减少的方法
US17/623,739 US20220256309A1 (en) 2019-07-01 2020-07-01 Method for reducing nas signaling of lcs and lpp procedures
EP20835536.2A EP3993464A4 (en) 2019-07-01 2020-07-01 Method for reducing nas signaling of lcs and lpp procedures

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201910585508.5A CN112188445A (zh) 2019-07-01 2019-07-01 Lcs和lpp程序的nas信令减少的方法
CN201910585508.5 2019-07-01

Publications (1)

Publication Number Publication Date
WO2021000887A1 true WO2021000887A1 (zh) 2021-01-07

Family

ID=73915454

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2020/099698 WO2021000887A1 (zh) 2019-07-01 2020-07-01 Lcs和lpp程序的nas信令减少的方法

Country Status (5)

Country Link
US (1) US20220256309A1 (zh)
EP (1) EP3993464A4 (zh)
CN (2) CN112188445A (zh)
TW (1) TW202106054A (zh)
WO (1) WO2021000887A1 (zh)

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN109076330A (zh) * 2016-03-23 2018-12-21 Lg 电子株式会社 无线通信系统中跟踪区域更新的方法及其装置
EP3419319A1 (en) * 2016-02-19 2018-12-26 LG Electronics Inc. -1- Service request transmission and user equipment, and service request reception and base station
CN109845172A (zh) * 2016-08-12 2019-06-04 创新技术实验室株式会社 用于发射/接收定位参考信号的方法和装置
US20190182873A1 (en) * 2016-05-16 2019-06-13 Telefonaktiebolaget Lm Ericsson (Publ) Evolved packet system (eps) bearer identity based active flag extension for cellular internet of things (ciot) devices

Family Cites Families (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US9743228B2 (en) * 2009-06-22 2017-08-22 Qualcomm Incorporated Transport of LCS-related messages for LTE access
JP6816257B2 (ja) * 2016-08-08 2021-01-20 エルジー エレクトロニクス インコーポレイティド Ｎｐｒｓ送信方法及びそのための装置
US10869315B2 (en) * 2018-03-02 2020-12-15 Qualcomm Incorporated Ranging based location services in wireless communication

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP3419319A1 (en) * 2016-02-19 2018-12-26 LG Electronics Inc. -1- Service request transmission and user equipment, and service request reception and base station
CN109076330A (zh) * 2016-03-23 2018-12-21 Lg 电子株式会社 无线通信系统中跟踪区域更新的方法及其装置
US20190182873A1 (en) * 2016-05-16 2019-06-13 Telefonaktiebolaget Lm Ericsson (Publ) Evolved packet system (eps) bearer identity based active flag extension for cellular internet of things (ciot) devices
CN109845172A (zh) * 2016-08-12 2019-06-04 创新技术实验室株式会社 用于发射/接收定位参考信号的方法和装置

Non-Patent Citations (8)

* Cited by examiner, † Cited by third party
Title
3GPP TS 23.271
3GPP TS 24.301
3GPP TS 36.321
3GPP TS 36.322
3GPP TS 36.323
3GPP TS 36.331
3GPP TS 36.413
See also references of EP3993464A4

Also Published As

Publication number Publication date
CN112188445A (zh) 2021-01-05
EP3993464A1 (en) 2022-05-04
EP3993464A4 (en) 2023-06-28
TW202106054A (zh) 2021-02-01
CN113875274B (zh) 2024-06-07
US20220256309A1 (en) 2022-08-11
CN113875274A (zh) 2021-12-31

Similar Documents

Publication Publication Date Title
US20230403533A1 (en) Systems and methods for 5g location support using service based interfaces
JP6422469B2 (ja) マシンタイプコミュニケーションのための装置及び方法
US11683738B2 (en) Systems and methods for handover of 5G location sessions for an NG-RAN location management component
US20190053010A1 (en) Systems and methods for 5g location support using service based interfaces
US9565530B2 (en) Methods and apparatus for identifying and authorizing location servers and location services
US10534932B2 (en) Enabling exchange of location and other status information between prose users
CN113169984B (zh) 传输协议选择方法及用户设备
US9137774B2 (en) Position measurement system, position information provision device, position information administration device, and position measurement method
JP2022536716A (ja) 制御プレーン最適化を使用したモバイルデバイスの低電力の周期的およびトリガされるロケーション
WO2021000887A1 (zh) Lcs和lpp程序的nas信令减少的方法
CN113474679A (zh) 获得和提供定位辅助数据
WO2023173875A1 (zh) 定位方式确定的方法及其装置
WO2024114965A1 (en) Overload handling for sidelink positioning in a wireless communication system
WO2024104628A1 (en) Supporting multiple sidelink positioning sessions in a wireless communication system

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

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

ENP Entry into the national phase

Ref document number: 2020835536

Country of ref document: EP

Effective date: 20220125