WO2021243518A1 - Accès initial de dispositif distant via un relais - Google Patents

Accès initial de dispositif distant via un relais Download PDF

Info

Publication number
WO2021243518A1
WO2021243518A1 PCT/CN2020/093747 CN2020093747W WO2021243518A1 WO 2021243518 A1 WO2021243518 A1 WO 2021243518A1 CN 2020093747 W CN2020093747 W CN 2020093747W WO 2021243518 A1 WO2021243518 A1 WO 2021243518A1
Authority
WO
WIPO (PCT)
Prior art keywords
control plane
information
plane connection
connection
request
Prior art date
Application number
PCT/CN2020/093747
Other languages
English (en)
Inventor
Ling Yu
Vinh Van Phan
Xiang Xu
György WOLFNER
Original Assignee
Nokia Shanghai Bell Co., Ltd.
Nokia Solutions And Networks Oy
Nokia Technologies Oy
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 Nokia Shanghai Bell Co., Ltd., Nokia Solutions And Networks Oy, Nokia Technologies Oy filed Critical Nokia Shanghai Bell Co., Ltd.
Priority to PCT/CN2020/093747 priority Critical patent/WO2021243518A1/fr
Priority to CN202080099998.9A priority patent/CN115428578A/zh
Publication of WO2021243518A1 publication Critical patent/WO2021243518A1/fr

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/10—Connection setup
    • H04W76/12—Setup of transport tunnels
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/80—Services using short range communication, e.g. near-field communication [NFC], radio-frequency identification [RFID] or low energy communication
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W88/00—Devices specially adapted for wireless communication networks, e.g. terminals, base stations or access point devices
    • H04W88/02—Terminal devices
    • H04W88/04—Terminal devices adapted for relaying to or from another terminal or user

Definitions

  • Embodiments of the present disclosure generally relate to the field of telecommunication and in particular, to methods, devices, apparatuses and computer readable storage medium for initial access of a remote device via a relay.
  • a radio resource control (RRC) connection needs to be established between the terminal device and the radio access network (RAN) node first and then a control plane (CP) connection with a non-access stratum (NAS) level could be established upon successful authentication and authorization of the terminal device.
  • 5GC 5th generation core
  • AMF access and mobility management function
  • RRC radio resource control
  • a sidelink can be established between two devices (such as, terminal devices) to enable a direct communication or a relay communication. Therefore, a remote terminal device may access the service via a relay terminal device. Further, a work item was conducted in the third Generation Partnership Project (3GPP) for the SL-based relay solutions. It is desirable for an efficient initial access of the remote terminal device.
  • 3GPP Third Generation Partnership Project
  • example embodiments of the present disclosure provide a solution for initial access of remote device via relay. Embodiments that do not fall under the scope of the claims, if any, are to be interpreted as examples useful for understanding various embodiments of the disclosure.
  • a first device comprising at least one processor; and at least one memory including computer program code; where the at least one memory and the computer program code are configured to, with the at least one processor, cause the first device to transmit a connection request to a second device.
  • the connection request is used for establishing a CP, connection between the first device and a third device.
  • the connection request comprises information of the first device for establishing the CP connection between the first and third devices, such that the second device transmits a CP connection request to the third device based on the information.
  • the first device is further caused to receive a RRC message for establishing a RRC connection between the first device and a fourth device from the second device.
  • the RRC message is transmitted by the fourth device after receiving a CP connection accept message from the third device.
  • a second device comprising at least one processor; and at least one memory including computer program code; where the at least one memory and the computer program code are configured to, with the at least one processor, cause the second device to receive a connection request for establishing a CP connection between the first and third device from a first device.
  • the connection request comprises information of the first device for establishing a CP connection between the first and third devices.
  • the second device is further caused to transmit a CP connection request to the third device based on the information.
  • the second device is also caused to receive a RRC message for establishing a RRC connection between the first device and the fourth device from a fourth device.
  • the RRC message is transmitted after receiving a CP connection accept message from the third device.
  • the second device is also caused to transmit the RRC message to the first device.
  • a third device comprises at least one processor; and at least one memory including computer program code; where the at least one memory and the computer program code are configured to, with the at least one processor, cause the third device to receive a CP connection request from a second device.
  • the CP connection request is generated based on information of a first device for establishing a CP connection between the first and third devices.
  • the third device is further caused to transmit a CP connection accept message to a fourth device, such that the fourth device transmits a RRC message for establishing a RRC connection between the first device and the fourth device to the second device.
  • a fourth device comprises at least one processor; and at least one memory including computer program code; where the at least one memory and the computer program code are configured to, with the at least one processor, cause the fourth device to receive a CP connection accept message from a third device.
  • the CP connections accept message is transmitted after receiving a CP connection request for establishing a CP connection between a first device and the third device from a second device.
  • the third device is further caused to transmit a RRC message for establishing a RRC connection between the first device and the fourth device to the second device.
  • a method comprising transmitting, at a first device to a second device, a connection request for establishing a CP connection between the first device and a second device.
  • the connection request comprises information of the first device for establishing a CP connection between the first and third devices, such that the second device transmits a CP connection request to the third device based on the information.
  • the method further comprises receiving, from the second device, a RRC message for establishing a RRC connection between the first device and a fourth device.
  • the RRC message is transmitted by the fourth device after receiving a CP connection accept message from the third device.
  • a method comprising receiving, at a second device from a first device, a connection request for establishing a CP connection between the first device and a third device.
  • the connection request comprises information of the first device for establishing a CP connection between the first and third devices.
  • the method further comprises transmitting a CP connection request to the third device based on the information.
  • the method also comprises receiving, from a fourth device, a RRC message for establishing a RRC connection between the first device and the fourth device.
  • the RRC message is transmitted after receiving a CP connection accept message from the third device.
  • the method further comprises transmitting the RRC message to the first device.
  • a method comprising receiving, at a third device from a second device, a CP connection request from a second device.
  • the CP connection request is generated based on information of a first device for establishing a CP connection between the first and third devices.
  • the method comprises transmitting, to a fourth device, a CP connection accept message, such that the fourth device transmits, to the second device, a RRC message for establishing a RRC connection between the first device and the fourth device.
  • a method comprising receiving, at a fourth device from a third device a CP connection accept message from a third device.
  • the CP connection accept message is transmitted after receiving a CP connection request for establishing a CP connection between a first device and the third device from a second device.
  • the method comprises transmitting a RRC message for establishing a RRC connection between the first device and the fourth device to the second device.
  • a first apparatus comprises means for transmitting a connection request for establishing a CP connection between the first apparatus and a third apparatus to a second apparatus.
  • the connection request comprises information of the first apparatus for establishing the CP connection between the first and third apparatuses to enable the second apparatus to transmit a CP connection request to the third apparatus based on the information.
  • the first apparatus further comprises means for receiving, from the second device, a RRC message for establishing a RRC connection between the first device and a fourth device. The RRC message is transmitted by the fourth device after receiving a CP connection accept message from the third device.
  • a second apparatus comprising means for receiving a connection request for establishing a control plane connection between the first apparatus and a second apparatus from a first apparatus.
  • the connection request comprises information of the first apparatus for establishing the CP connection between the first apparatus and a third apparatus.
  • the second apparatus also comprises means for transmitting a CP connection request to the third apparatus based on the information.
  • the second apparatus also comprises means for receiving, from a fourth device, a RRC message for establishing a RRC connection between the first device and the fourth device.
  • the RRC message is transmitted after receiving a CP connection accept message from the third device.
  • the second apparatus also comprises means for transmitting the RRC message to the first device.
  • a third apparatus comprises means for receiving, a CP connection request from a second device.
  • the CP connection request is generated based on information of a first device for establishing a CP connection between the first and third devices.
  • the third apparatus also comprises means for transmitting a CP connection accept message to a fourth device, such that the fourth device transmits, to the second device, a RRC message for establishing a RRC connection between the first device and the fourth device.
  • a fourth apparatus comprises means for receiving, from a third device, a CP connection accept message.
  • the CP connection accept message is transmitted after receiving, from a second device, a CP connection request for establishing a CP connection between a first device and the third device.
  • the fourth apparatus also comprises means for transmitting a RRC message for establishing a RRC connection between the first device and the fourth device to the second device.
  • a computer readable medium comprises program instructions for causing an apparatus to perform at least the method according to the fifth aspect.
  • a fourteenth aspect there is provided a computer readable medium.
  • the computer readable medium comprises program instructions for causing an apparatus to perform at least the method according to the sixth aspect.
  • a computer readable medium comprises program instructions for causing an apparatus to perform at least the method according to the seventh aspect.
  • a computer readable medium comprises program instructions for causing an apparatus to perform at least the method according to the eighth aspect.
  • Fig. 1 illustrates an example communication environment in which example embodiments of the present disclosure can be implemented
  • Fig. 2 illustrates a conventional signaling flow of initial access for a terminal device without relay
  • Fig. 3 illustrates a conventional signaling flow of establishing a PC5 direct link between the remote terminal device and the relay terminal;
  • Fig. 4 illustrates a conventional signaling flow of initial access for a remote terminal device via a relay terminal device
  • Fig. 5 illustrates a signaling flow for initial access procedure according to some example embodiments of the present disclosure
  • Fig. 6 illustrates an example CP protocol stack for L2 relay according to some example embodiments of the present disclosure
  • Fig. 7 illustrates an example further CP protocol stack for L2 relay according to some example embodiments of the present disclosure
  • Fig. 8 illustrates an example CP protocol stack for L3 relay according to some example embodiments of the present disclosure
  • Fig. 9 illustrates a flowchart of a method implemented at a first device according to some other example embodiments of the present disclosure.
  • Fig. 10 illustrates a flowchart of a method implemented at a second device according to some other example embodiments of the present disclosure
  • Fig. 11 illustrates a flowchart of a method implemented at a third device according to some other example embodiments of the present disclosure
  • Fig. 12 illustrates a flowchart of a method implemented at a fourth device according to some other example embodiments of the present disclosure
  • Fig. 13 illustrates a simplified block diagram of an apparatus that is suitable for implementing example embodiments of the present disclosure.
  • Fig. 14 illustrates a block diagram of an example computer readable medium in accordance with some example embodiments of the present disclosure.
  • references in the present disclosure to “one embodiment, ” “an embodiment, ” “an example embodiment, ” and the like indicate that the embodiment described may include a particular feature, structure, or characteristic, but it is not necessary that every embodiment includes the particular feature, structure, or characteristic. Moreover, such phrases are not necessarily referring to the same embodiment. Further, when a particular feature, structure, or characteristic is described in connection with an embodiment, it is submitted that it is within the knowledge of one skilled in the art to affect such feature, structure, or characteristic in connection with other embodiments whether or not explicitly described.
  • first and second etc. may be used herein to describe various elements, these elements should not be limited by these terms. These terms are only used to distinguish one element from another. For example, a first element could be termed a second element, and similarly, a second element could be termed a first element, without departing from the scope of example embodiments.
  • the term “and/or” includes any and all combinations of one or more of the listed terms.
  • circuitry may refer to one or more or all of the following:
  • circuitry also covers an implementation of merely a hardware circuit or processor (or multiple processors) or portion of a hardware circuit or processor and its (or their) accompanying software and/or firmware.
  • circuitry also covers, for example and if applicable to the particular claim element, a baseband integrated circuit or processor integrated circuit for a mobile device or a similar integrated circuit in server, a cellular fourth device, or other computing or fourth device.
  • the term “communication network” refers to a network following any suitable communication standards, such as New Radio (NR) , Long Term Evolution (LTE) , LTE-Advanced (LTE-A) , Wideband Code Division Multiple Access (WCDMA) , High-Speed Packet Access (HSPA) , Narrow Band Internet of Things (NB-IoT) and so on.
  • NR New Radio
  • LTE Long Term Evolution
  • LTE-A LTE-Advanced
  • WCDMA Wideband Code Division Multiple Access
  • HSPA High-Speed Packet Access
  • NB-IoT Narrow Band Internet of Things
  • the communications between a first device and a fourth device 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) , the fourth generation (4G) , 4.5G, the future fifth generation (5G) communication protocols, and/or any other protocols either currently known or to be developed in the future.
  • 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) , the fourth generation (4G) , 4.5G, the future fifth generation (5G) communication protocols, and/or any other protocols either currently known or to be developed in the future.
  • Embodiments of the present disclosure may be applied in various communication systems. Given the rapid development in communications, there will of course also be future type communication technologies and systems with which the present disclosure may be embodied. It should not be seen as limiting the scope of the present disclosure to only the
  • core device refers to any device or entity that provides access and mobility management function, session management function (SMF) , user plane function (UPF) , etc.
  • SMF session management function
  • UPF user plane function
  • the core device may be an AMF, a SMF, a UPF, etc.
  • the core device may be any other suitable device or entity.
  • the term “network device” refers to a node in a communication network via which terminal devices accesses the network and receives services therefrom.
  • the network device may refer to a base station (BS) or an access point (AP) , for example, a node B (NodeB or NB) , an evolved NodeB (eNodeB or eNB) , a NR NB (also referred to as a gNB) , a Remote Radio Unit (RRU) , a radio header (RH) , a remote radio head (RRH) , a relay, an Integrated Access and Backhaul (IAB) node, a low power node such as a femto, a pico, a non-terrestrial network (NTN) or non-ground fourth device such as a satellite fourth device, a low earth orbit (LEO) satellite and a geosynchronous earth orbit (GEO) satellite, an aircraft fourth device, and so forth, depending on the applied terminology and technology.
  • terminal device refers to any end device that may be capable of wireless communication.
  • a terminal device may also be referred to as a communication device, user equipment (UE) , a Subscriber Station (SS) , a Portable Subscriber Station, a Mobile Station (MS) , or an Access Terminal (AT) .
  • UE user equipment
  • SS Subscriber Station
  • MS Mobile Station
  • AT Access Terminal
  • the terminal device may include, but not limited to, a mobile phone, a cellular phone, a smart phone, voice over IP (VoIP) phones, wireless local loop phones, a tablet, a wearable terminal device, a personal digital assistant (PDA) , portable computers, desktop computer, image capture terminal devices such as digital cameras, gaming terminal devices, music storage and playback appliances, vehicle-mounted wireless terminal devices, wireless endpoints, mobile stations, laptop-embedded equipment (LEE) , laptop-mounted equipment (LME) , USB dongles, smart devices, wireless customer-premises equipment (CPE) , an Internet of Things (loT) device, a watch or other wearable, a head-mounted display (HMD) , a vehicle, a drone, a medical device and applications (e.g., remote surgery) , an industrial device and applications (e.g., a robot and/or other wireless devices operating in an industrial and/or an automated processing chain contexts) , a consumer electronics device, a device operating on commercial and/
  • remote terminal device refers to a terminal device that communicates with the network device and the core device via a further device (i.e., the relay terminal device) because it is out of the coverage of the network device or the core device, or due to other reasons, for example, being blocked by obstacles, lacking capability to communicate with the network device and the core device, and the like.
  • relay terminal device refers to a terminal device that acts as a relay for a further device, for example, a remote terminal device, to enable the further device to communicate with the network device and/or the core device.
  • a user equipment apparatus such as a cell phone or tablet computer or laptop computer or desktop computer or mobile IOT device or fixed IOT device
  • This user equipment apparatus can, for example, be furnished with corresponding capabilities as described in connection with the fixed and/or the wireless network node (s) , as appropriate.
  • the user equipment apparatus may be the user equipment and/or or a control device, such as a chipset or processor, configured to control the user equipment when installed therein. Examples of such functionalities include the bootstrapping server function and/or the home subscriber server, which may be implemented in the user equipment apparatus by providing the user equipment apparatus with software configured to cause the user equipment apparatus to perform from the point of view of these functions/nodes.
  • sidelink refers to a direct communication link and/or discovery link between two or more terminal devices
  • PC5 refers to an interface which enables communication and/or discovery between two or more terminal devices without traversing any network node
  • PC5 direct link refers to the link established between two or more terminal devices over the PC5 interface.
  • sidelink and PC5 direct link described herein are equivalent to each other.
  • Fig. 1 shows an example communication environment 100 in which example embodiments of the present disclosure can be implemented.
  • a first device 110 can communicate with a second device 120 via physical communication channels or links
  • the second device 120 can communicate with a third device 130 and a fourth device 140 via physical communication channels or links
  • the third device 130 can communicate with the fourth device 140 via physical communication channels or links.
  • the first device 110 and the second device are illustrated as terminal devices, where the first device 110 is remote terminal device and the second device 120 is relay terminal device.
  • the third device 130 is illustrated as core device serving the terminal devices.
  • the fourth device 140 is illustrated as network device serving the terminal devices.
  • the first device 110 communicates with the third device 130 and the fourth device 140 via the second device 120.
  • the second device 120 communicates with the third device 130 via the fourth device 140.
  • first device second device, third device and fourth device are only for the purpose of illustration without suggesting any limitations.
  • the communication environment 100 may include any suitable numbers of first device, second device, third device and fourth device adapted for implementing embodiments of the present disclosure.
  • Fig. 2 is a conventional signaling flow 200 of initial access of a terminal device accessing the communication system directly without relay.
  • the terminal device initiates the random access channel (RACH) procedure to acquire uplink synchronization with the network device and then requests to establish the RRC connection with the network device.
  • RACH random access channel
  • registration or service request can be sent to the core device via established RRC connection in order to setup a CP connection e.g. Non-Access Stratum (NAS) connection between the terminal device and the core device.
  • NAS Non-Access Stratum
  • this initial access procedure cannot be reused for a remote terminal device due to the relayed communication between remote terminal device and the network device/core device, especially for the connection establishment between terminal device and network device using a RACH related procedure.
  • the remote terminal device Instead of initiating RACH procedure for RRC connection establishment between the terminal device and the network device, the remote terminal device needs to establish the PC5 direct link to the relay terminal device first as illustrated in Fig. 3.
  • Fig. 3 illustrates a conventional signaling flow 300 of establishing a PC5 direct link between the remote terminal device and the relay terminal.
  • this establishing procedure only establishes a connection between the remote terminal device and the relay terminal device.
  • the connections between the remote terminal device and the network device and/or the core device still need to be established so that the terminal device can communicate with the network device and/or the core device via the relay terminal device.
  • Fig. 4 illustrates a conventional signaling flow 400 of initial access for a remote terminal device via a relay terminal device.
  • the relay terminal device is activated, and the remote terminal device and the relay terminal device are connected with each other via PC5 link.
  • the remote terminal device needs to setup the RRC connection with the network device first by exchanging the RRC signalings with the network device via the relay terminal device and then send the registration or service request to the core device for further processing, for example, authentication.
  • a NAS connection of the remote terminal device can be established after the further processing, for example, a successful authentication.
  • a RRC connection between remote terminal device and network device has to be established first and then the CP (e.g. NAS) connection between remote terminal device and core device is established upon successful authentication.
  • the authorization is unsuccessful, a NAS connection will not be established and the pre-established RRC connection has to be released.
  • the signaling overheads exchanged between the network elements are complicated as all the signaling between remote terminal device and network device and/or core network device is relayed via relay terminal device, which results an undesirable latency.
  • a remote terminal device transmits a connection request to the relay terminal device for establishing a CP connection between the remote terminal device and the core device.
  • the connection request comprises information of the remote terminal device for establishing the CP connection between the remote terminal device and a core device.
  • the relay terminal device may transmit a registration request or service request for the remote terminal device to trigger the establishment of a CP connection between the remote terminal device and the core device.
  • the core device may send a message to trigger a network device to initiate a RRC connection between the remote terminal device and the network device.
  • the RRC connection may be triggered by the network side after a successful authentication and the core device accepts the registration or service request.
  • unnecessary establishment of RRC connections caused by unsuccessful authentication can be avoided.
  • the latency of the initial access is shortened and the signalling overhead is reduced.
  • Fig. 5 illustrates a flowchart 500 of a method according to some other example embodiments of the present disclosure.
  • the flowchart 500 may be implemented at any suitable devices. Only for the purpose of illustrations, the flowchart 500 is described to be implemented at the first device 110 (such as, a remote terminal device) , the second device 120 (such as, a relay terminal device) , the third device 130 (such as, a core device) and the fourth device 140 (such as, a network device) .
  • first device 110, second device 120, third device 130 and the fourth device 140 shown in Fig. 5 are given for the purpose of illustration without suggesting any limitations.
  • the flowchart 500 may include any suitable numbers of first device, second device 120, third device 130 and the fourth device 140.
  • the first device 110 transmits 502 a connection request for establishing a CP connection between the first device 110 and the third device 130 over PC5 interface to the second device 120 first.
  • the connection request comprising information of the first device 110 for establishing a CP connection between the first device 110 and the third device 130.
  • the information comprised in the connection request may be either the whole or part of an initiation NAS message that may be transmitted as an information element (IE) in the connection request.
  • the connection request over PC5 may be implemented as the extension of a current direct communication request.
  • the first device 110 may optionally include all or part of the IE in the conventional initiation NAS message (such as, a registration request, a service request, and the like) into the direct communication request message. It should be noticed that, the above messages are illustrated only for the purpose of illustration without suggesting any limitations. In other example embodiments, any suitable control message may be used.
  • the information comprised in the connection request may comprise the information, such as, a type indication of NAS connection to be established (such as, type of requested NAS procedure, and the like) , an identification (ID) of the first device 110 (such as, UE ID used for registration request or ProSe ID used in PC5 interface, and the like) and information of network slice (such as, network slice selection assistance information (NSSAI) , and the like) .
  • the first device 110 may only indicate the necessary information of the first device 110 for establishing the CP connection between the first device 110 and the third device 130.
  • a mutual authentication between the first device 110 and the second device 120 involving the third device 130 may be performed as illustrated in Fig. 3.
  • the third device 130 may provide the second device 120 assistant information about the first device 110.
  • the assistant information will assist the second device 120 to transmit the CP connection request for the first device 110 later.
  • the first device 110 provides authentication information of the first device 110 to the second device 120 to enable the second device 120 sends a request for assistant information to the third device 130.
  • the second device 120 transmits 504 a CP connection request for establishing a CP connection between the first device 110 and the third device 130 based on the information comprised in the connection request.
  • the CP connection request is transferred to the third device 130 via the fourth device 140.
  • the CP connection request is provided by the first device 110 directly.
  • the CP connection request is the NAS message comprised in the connection request transmitted at 502.
  • the second device 120 generates the CP connection request based on the connection request.
  • the second device 120 extracts the information of the first device 110 comprised in the connection request and generates the CP connection request based on the extracted information of the first device 110.
  • the CP connection request may contain a NAS registration request message, or a NAS service request message, or any other NAS message.
  • the information for establishing the CP connection between the first device 110 and the third device 130 may be provided to the third device 130, such that the third device 130 could perform an authentication procedure for the first device 110.
  • the CP connection request may be preferred to be transmitted over a CP connection of the second device 120.
  • the existing CP connection between the second device 120 and the third device 130/fourth device 140 can be utilized to exchange the necessary information of the first device 110.
  • the third device 130 is able to get information of first device 110 to authorize the first device 110 prior to establishing the RRC connection for the first device 110.
  • the third device 130 may performs an authenticate procedure for the first device 110 based on the information of the first device 110 comprised in the CP connection request.
  • the authentication information may be the parameters comprised in in the connection request.
  • the first device 110 may provide the authentication information by other signaling or messages exchanged between the first device 110 and the second device 120.
  • the authentication may be combined into the same authentication that is performed during the direct communication setup between the first device 110 and the second device 120, for example, during the mutual authentication as described in Fig. 3.
  • the third device 130 may perform a core device selecting procedure (such as, an existing AMF reselection function) for the first device 110 if the third device 130 is not suitable to be selected for the first device 110.
  • a core device selecting procedure such as, an existing AMF reselection function
  • the third device 130 may determine whether to accept the CP connection request or not by using the above discussed authentication procedure or other criteria such as network load, transport layer capability etc. If the third device 130 determines to accept the CP connection request, the third device 130 transmits 506 a request message to the fourth device 140 to initiate a RRC connection establishment procedure for the first device 110.
  • the request sent by the third device 130 may be a NG application protocol (NGAP) initial context setup request/UE context modification message to the fourth device 140, which includes a NAS message (for example, NAS registration accept message in case of receiving a registration message, or NAS service accept in case of receiving service request message, and the like) to the first device 110.
  • NGAP NG application protocol
  • NAS message for example, NAS registration accept message in case of receiving a registration message, or NAS service accept in case of receiving service request message, and the like
  • the third device 130 may support more than one relay solutions (e.g. L2 relay or L3 relay) for the first device 110.
  • relay solutions e.g. L2 relay or L3 relay
  • the third device 130 may support to perform a L2 relay for the first device 110.
  • Fig. 6 illustrates an example CP protocol stack 600 for L2 relay using 3GPP PC5 interface between the first device 110 and the second device 120 and
  • Fig. 7 illustrates a further example CP protocol stack 700 for L2 relay using non-3GPP interface between the first device 110 and the second device 120. Only for the purpose of illustration without suggesting any limitations, in Figs. 6 and 7, the first device 110 is remote terminal device, the second device 120 is relay device, the third device 130 is core device and the fourth device 140 is network device.
  • the first device 110 communicates with the second device 120 via PC5 interface as illustrated in Fig. 6 while the first device 110 communicates with the second device 120 via non-3GPP link (such as, WiFi or other short-range radio technologies) in Fig. 7.
  • the logical connections may be established between the first device 110 and the fourth device 140/the third device 130.
  • CP procedures for the first device 110 with connected mode are expected to be similar to that of a normal directly connected device at least from the perspective of the network device and core device.
  • the third device 130 may support to perform a L3 relay for the first device 110.
  • Fig. 8 illustrates a CP protocol stack 800 for L3 relay. Only for the purpose of illustration without suggesting any limitations, the first device 110 is remote terminal device, the second device 120 is relay device, the third device 130-1 a gateway or a user plane function or an AMF of the second device 120, the third device 130-2 is an AMF of the first device 110, and the fourth device 140 is network device.
  • the first device 110 and the second device 120 communicate each other with PC5-U protocols.
  • the second device 120 and the fourth device 140 communicate each other with LTE-Uu or NR-Uu protocols.
  • general packet radio service (GPRS) tunneling protocol (GTP) for the user plane (GTP-U) is used for the communication between the fourth device 140 and the third device 130-1 as well as between the third device 130-1 and t the third device 130-2.
  • the third device 130-1 and the fourth device 140 communicate each other with Internet Protocol (IP) , or using other intermediate device (s) which is not shown in Fig. 8
  • IP Internet Protocol
  • the third device 130 may determine 505 a relay solution for the first device 110 and then transmit the request message, for example, which may include a CP connection accept message comprising the determined relay solution to the fourth device 140 later.
  • the third device 130 may determine the relay solution based on a capability of the first device 110 on support for a relay solution. For example, if the first device 110 only supports L2 relay or L3 relay, the third device 130 may determine the relay solution for the first device 110 to be L2 relay or L3 relay accordingly
  • the third device 130 may determine the relay solution based on a capability of the second device 120 on support for a relay solution. For example, if the second device 120 only supports L2 relay or L3 relay, the third device 130 may determine the relay solution for the first device 110 to be L2 relay or L3 relay accordingly.
  • the third device 130 may determine the relay solution based on a capability of the fourth device 140 on support for a relay solution. For example, if the fourth device 140 only supports L2 relay or L3 relay, the third device 130 may determine the relay solution for the first device 110 to be L2 relay or L3 relay accordingly.
  • the third device 130 may determine the relay solution based on preference of the first device 110 for a relay solution. For example, if the first device 110 prefers L2 relay or L3 relay, the third device 130 may determine the relay solution for the first device 110 to be L2 relay or L3 relay accordingly.
  • the third device 130 may determine the relay solution based on preference of the second device 120 for a relay solution. For example, if the second device 120 prefers L2 relay or L3 relay, the third device 130 may determine the relay solution for the first device 110 to be L2 relay or L3 relay accordingly.
  • the third device 130 may determine the relay solution based on subscription information of the first device 110.
  • the information of relay solution for the first device 110 may as stored as a configuration in the subscription information.
  • the third device 130 may obtain the subscription information of the first device 110 and determine the relay solution for the first device 110 accordingly.
  • the third device 130 may determine the relay solution based on a type of the received a CP connection request (such as, the registration/NAS signaling type (for example, initial registration or registration update) ) .
  • a type of the received a CP connection request such as, the registration/NAS signaling type (for example, initial registration or registration update)
  • the third device 130 may determine the relay solution for the first device 110 to be L2 relay or L3 relay according to the criteria discussed above, and in case that the CP connection request is a registration update message, the third device 130 may determine the relay solution for the first device 110 to be L2 relay or L3 relay according to the determined relay solution of the same registration.
  • the third device 130 may determine the relay solution based on the priority information for a service of the first device 110. For example, some priority of the services may be associated with certain service requirement. Thus, if the information of the service includes the priority corresponds to a high requirement for service continuity, a L2 relay may be determined by the third device 130, and if the information of the service includes the priority corresponds to a low requirement for service continuity, a L3 relay may be determined by the third device 130.
  • the third device 130 may determine the relay solution based on a quality of service requirement for a service of the first device 110.
  • the L2 relay may correspond to a high quality of service requirement and the L3 relay may correspond to a low quality of service requirement or vice versa.
  • the third device 130 may determine the relay solution based on any combination of the criteria as described above, for example, a capability of the first device 110, a capability of the second device 120, a capability of the fourth device 140, a preference of the first device 110, a preference of the second device 120, a subscription information of the first device 110, a type of the received a CP connection request, a priority information for a service of the first device 110, a quality of service requirement for a service of the first device 110, etc.
  • the determined relay solution may be indicated explicitly as an indication, for example, the request to the fourth device may include an indication for L2 relay or L3 relay.
  • the NGAP message to the fourth device may include a new Information Element (IE) to indicate the determined relay solution.
  • IE Information Element
  • the determined relay solution may be indicated implicitly. For example, different NGAP procedure or messages may be used as an implicit indication on the determined relay solution. For example, NGAP UE context modification message may be used as an implicit indication as L3 relay.
  • the fourth device 140 triggers set up or the update the context of the second device 120 for relaying traffic of the first device 110 on a L2 level or L3 level relay based on the explicit indication or implicit indication received from the third device 130.
  • NGAP Initial context setup request message may be used an implicit indication as L2 relay.
  • the fourth device 140 Upon receiving the request, for example, NGAP initial context setup request message, the fourth device 140 is triggered to setup the first device 110’s context for L2 relay or L3 relay.
  • the third device 130 may determine a relay solution (such as, a L2 relay or L3 relay) . In this way, a more flexible initial access procedure is achieved.
  • the fourth device 140 After receiving the CP connection accept message from the third device 130, the fourth device 140 initiates a RRC establishment procedure for the first device 110 to establish the RRC connection between the first device and the fourth device and the established RRC connection is associated with the CP connection between the first device and the third device.
  • the fourth device 140 transmits 508 a RRC message (e.g. RRC connection setup message, or other RRC message (s) ) for establishing a RRC connection between the first device 110 and the fourth device 140 to the second device 120 and then the second device 120 forwards 510 the RRC message to the first device 110.
  • the first device 110 transmits 512 a RRC confirmation (e.g. RRC connection setup complete message, or other RRC message (s) ) to the second device 120 and then the second device 120 transmits 514 the RRC confirmation to the fourth device 140.
  • a RRC connection is established between the first device 110 and the fourth device 140.
  • a RRC connection establishment is triggered by the fourth device 140.
  • the initiation mechanism for RRC connection is more efficient as it is only initiated after the third device 130 determines the CP connection between the first device 110 and the third device 130 can be established.
  • the RRC connection setup message, or other RRC message may be extended to include a cell radio network temporary identifier (C-RNTI) of the first device 110 in addition to the relevant radio bearer information and related configurations.
  • C-RNTI cell radio network temporary identifier
  • a new RRC message may be introduced to enable the fourth device 140 to initiate a RRC connection establishment procedure.
  • the corresponding information about CP connection establishment message (e.g. registration accept message) between the first device 110 and the third device 130 may be also included into the RRC connection setup message or other RRC message (s) .
  • the fourth device 140 may initiate a special paging message comprising a C-RNTI of the first device 110 to the first device 110 via the second device 120.
  • the special paging message triggers the first device 110 to send the RRC connection establishment/re-establishment message.
  • the RRC message for connection setup message and the special paging message may be transmitted by using the existing signalling radio bearers (SRB) of the second device 120, specific RRC message of the second device 120 or new SRB dedicated for relaying RRC signaling messages.
  • SRB signalling radio bearers
  • the fourth device 140 Upon receiving the RRC confirmation from the second device 120, the fourth device 140 transmits 516 a CP connection confirmation message to the third device 130 to confirm the CP connection setup of the first device 110. In some example embodiments, the fourth device 140 transmits a NGAP initial context setup response/NGAP UE context modification response to the third device 130. It should be noticed that, the above messages are illustrated only for the purpose of illustration without suggesting any limitations. In other example embodiments, any suitable control message may be used.
  • the existing connection between the second device 120 and the third device 130/the fourth device 140 can be utilized to exchange the necessary information of the first device 110, such that the third device 130 may authenticate and authorize the first device 110 first and then trigger the CP connection setup procedure involving a RRC setup procedure.
  • the RRC initiation mechanism is more flexible and the unnecessary RRC connection due to unsuccessful authentication can be avoided.
  • the latency of the initial access is shortened and the signalling overhead is reduced.
  • the third device 130 may determine the relay solution. In this way, the relay level selection mechanism is more flexible.
  • the present disclosure can be also extended to support CN initiated NAS level CP connection establishment (e.g. triggered by AF function) after successful application authentication of the first device 110.
  • Fig. 9 shows a flowchart of an example method 900 implemented at a first device 110 in accordance with some example embodiments of the present disclosure.
  • the method 900 will be described from the perspective of the first device 110 with respect to Fig. 1. It is to be understood that the method 900 may include additional blocks not shown and/or may omit some shown blocks, and the scope of the present disclosure is not limited in this regard.
  • the first device 110 transmits a connection request to a second device 120.
  • the connection request is used for establishing a CP connection between the first device 110 and the third device 130.
  • the connection request comprises information of the first device 110 for establishing a CP connection between the first device 110 and the third device 130, such that the second device 120 transmits a CP connection request to the third device 130 based on the information.
  • the information comprises at least one of the following: a type indication of NAS connection to be established between the first device 110 and the third device 130, an identification of the first device 110, or information of network slice requested by the first device 110.
  • the information is an initiation NAS message included in the connection request.
  • connection request is a one of a direct communication request and a relay connection request
  • initiation NAS message is a registration request or a service request
  • the first device 110 receives a RRC message for establishing a RRC connection between the first device 110 and a fourth device 140 from the second device 120.
  • the RRC message comprises a C-RNTI of the first device 110.
  • the first device 110 and the second device 120 are terminal devices
  • the third device 130 is a core device
  • the fourth device 140 is a network device.
  • Fig. 10 shows a flowchart of an example method 1000 implemented at a second device 120 in accordance with some example embodiments of the present disclosure.
  • the method 1000 will be described from the perspective of the second device 120 with respect to Fig. 1. It is to be understood that the method 1000 may include additional blocks not shown and/or may omit some shown blocks, and the scope of the present disclosure is not limited in this regard.
  • the second device 120 receives, a connection request for establishing a CP connection between the first 110 and the third device 130 from a first device 110.
  • the connection request comprises information of the first device 110 for establishing the CP connection between the first device 110 and a third device 130.
  • the information comprises at least one of the following: a type indication of NAS connection to be established between the first device 110 and the third device 130; an identification of the first device 110; or information of network slice requested by the first device 110.
  • the information is an initiation NAS message included in the connection request.
  • connection request is one of a direct communication request and a relay connection request
  • initiation NAS message is registration request or service request
  • the second device 120 transmits a CP connection request to the third device 130 based on the information.
  • the second device 120 transmits the CP connection request by: obtaining authentication information of the first device 110 from the first device 110; sending a request to the third device 130 for assistant information to be used for transmitting the CP connection request based on the obtained authentication information; and transmitting, to the third device 130, the CP connection request based on the information received from the first device 110 and the assistant information.
  • the second device 120 receives a RRC message for establishing a RRC connection between the first device 110 and the fourth device 140 from a fourth device 140.
  • the RRC message is transmitted after receiving a CP connection accept message from the third device 130.
  • the RRC message comprises a C-RNTI of the first device 110.
  • the second device 120 transmits the RRC message to the first device 110.
  • the first device 110 and the second device 120 are terminal devices
  • the third device 130 is a core device
  • the fourth device 140 is a network device.
  • Fig. 11 shows a flowchart of an example method 1100 implemented at a third device 130 in accordance with some example embodiments of the present disclosure.
  • the method 1100 will be described from the perspective of the third device 130 with respect to Fig. 1. It is to be understood that the method 1100 may include additional blocks not shown and/or may omit some shown blocks, and the scope of the present disclosure is not limited in this regard.
  • the third device 130 receives a CP connection request from a second device 120.
  • the CP connection request is generated based on information of a first device 110 for establishing a CP connection between the first device 110 and the third device 130.
  • the third device 130 transmits a CP connection accept message to a fourth device 140, such that the fourth device 140 transmits a RRC message for establishing a RRC connection between the first device 110 and the fourth device 140 to the second device 120.
  • the third device 130 determine a relay solution for the first device 110 in accordance to at least one of following: a capability of the first device on support for a relay solution; a capability of the second device 120 on support for a relay solution; a capability of the fourth device 140 on support for a relay solution; preference of the first device 110 for a relay solution; preference of the second device 120 for a relay solution; subscription information of the first device 110; a type of the received a CP connection request; priority information for a service of the first device 110; or a quality of service requirement for a service of the first device 110.
  • the third device 130 provides assistant information of the first device 110 to the second device 120 in response to a request from the second device 120 to enable the second device 120 to transmit the CP connection request based on the provided assistant information.
  • the first device 110 and the second device 120 are terminal devices
  • the third device 130 is a core device
  • the fourth device 140 is a network device.
  • Fig. 12 shows a flowchart of an example method 1200 implemented at a fourth device 140 in accordance with some example embodiments of the present disclosure.
  • the method 1200 will be described from the perspective of the fourth device 140 with respect to Fig. 1. It is to be understood that the method 1200 may include additional blocks not shown and/or may omit some shown blocks, and the scope of the present disclosure is not limited in this regard.
  • the fourth device 140 receives a CP connection accept message from a third device 130.
  • the CP connection accept message is transmitted after receiving a CP connection request for establishing a CP connection between a first device 110 and the third device 130 from a second device 120.
  • the fourth device 140 transmits a CP connection accept message to a fourth device 140, such that the fourth device 140 a RRC message for establishing a RRC connection between the first device 110 and the fourth device 140 to the second device 120.
  • the fourth device 140 receives the CP connection accept message comprising an indication for a relay solution for the first device 110 and establishes a user plane (UP) connection between the fourth device 140 and the first device 110 based on the received relay solution for the first device 110.
  • CP connection accept message comprising an indication for a relay solution for the first device 110
  • UP user plane
  • the RRC message comprises a C-RNTI of the first device 110.
  • the first device 110 and the second device 120 are terminal devices
  • the third device 130 is a core device
  • the fourth device 140 is a network device.
  • a first apparatus capable of performing any of the method 900 may comprise means for performing the respective operations of the method 900.
  • the means may be implemented in any suitable form.
  • the means may be implemented in a circuitry or software module.
  • the first apparatus may be implemented as or included in the first device 110.
  • the first apparatus comprises means for transmitting a connection request for establishing a CP connection between the first and third apparatuses to a second apparatus.
  • the connection request comprises information of the first apparatus for establishing a CP connection between the first apparatus and the third apparatus to enable the second apparatus to transmit a CP connection request to the third apparatus based on the information.
  • the first apparatus further comprises means for receiving, from the second apparatus, a RRC message for establishing a RRC connection between the first apparatus and a fourth apparatus. The RRC message is transmitted by the fourth apparatus after receiving a CP connection accept message from the third apparatus.
  • the information comprises at least one of the following: a type indication of non-access stratum, NAS, connection to be established between the first apparatus and the third apparatus, an identification of the first apparatus, or information of network slice requested by the first apparatus.
  • NAS non-access stratum
  • the information is an initiation NAS message included in the connection request.
  • connection request is a one of a direct communication request and a relay connection request
  • initiation NAS message is a registration request or a service request
  • the first apparatus further comprises means for providing authentication information of the first apparatus to the second apparatus to enable the second apparatus to send to the third apparatus a request for assistant information for transmitting the CP connection request.
  • the RRC message comprises a C-RNTI of the first apparatus.
  • the first and second apparatuses are terminal apparatuses
  • the third apparatus is a core apparatus
  • the fourth apparatus is a network apparatus.
  • a second apparatus capable of performing any of the method 1000 may comprise means for performing the respective operations of the method 1000.
  • the means may be implemented in any suitable form.
  • the means may be implemented in a circuitry or software module.
  • the second apparatus may be implemented as or included in the second device 120.
  • the second apparatus comprises means for receiving a connection request for establishing a connection between the first and third apparatuses from a first apparatus.
  • the connection request comprises information of the first apparatus for establishing a CP connection between the first apparatus and a third apparatus.
  • the second apparatus also comprises means for transmitting a CP connection request to the third apparatus based on the information.
  • the second apparatus also comprises means for receiving, from a fourth apparatus, a RRC message for establishing a RRC connection between the first apparatus and the fourth apparatus.
  • the RRC message is transmitted after receiving a CP connection accept message from the third apparatus.
  • the second apparatus also comprises means for transmitting the RRC message to the first apparatus.
  • the information comprises at least one of the following: a type indication of non-access stratum, NAS, connection to be established between the first apparatus and the third apparatus; an identification of the first apparatus; or information of network slice requested by the first apparatus.
  • NAS non-access stratum
  • the information is an initiation NAS message included in the connection request.
  • connection request is one of a direct communication request and a relay connection request
  • initiation NAS message is registration request or service request
  • the second apparatus comprises means for obtaining authentication information of the first apparatus from the first apparatus; means for sending a request to the third apparatus for assistant information to be used for transmitting the CP connection request based on the obtained authentication information; and means for transmitting, to the third apparatus, the CP connection request based on the information received from the first apparatus and the assistant information.
  • the RRC message comprises a C-RNTI of the first apparatus.
  • the first and second apparatuses are terminal apparatuses
  • the third apparatus is a core apparatus
  • the fourth apparatus is a network apparatus.
  • a third apparatus capable of performing any of the method 1100 may comprise means for performing the respective operations of the method 1100.
  • the means may be implemented in any suitable form.
  • the means may be implemented in a circuitry or software module.
  • the third apparatus may be implemented as or included in the third device 130.
  • the third apparatus comprises means for receiving, a CP connection request from a second apparatus.
  • the CP connection request is generated based on information of a first apparatus for establishing a CP connection between the first apparatus and the third apparatus.
  • the third apparatus also comprises means for transmitting a CP connection accept message to a fourth apparatus, such that the fourth apparatus transmits, to the second apparatus, a RRC message for establishing a RRC connection between the first apparatus and the fourth apparatus.
  • the third apparatus further comprises means for determining a relay solution for the first apparatus; and means for transmitting, to the fourth apparatus, the CP connection accept message comprising an indication of the determined relay solution.
  • the third apparatus comprises means for, determining a relay solution for the first apparatus in accordance to at least one of following: a capability of the first device on support for a relay solution; a capability of the second apparatus on support for a relay solution; a capability of the fourth apparatus on support for a relay solution; preference of the first apparatus for a relay solution; preference of the second apparatus for a relay solution; subscription information of the first apparatus; a type of the received a CP connection request; priority information for a service of the first apparatus; or a quality of service requirement for a service of the first apparatus.
  • the third apparatus comprises means for providing assistant information of the first apparatus to the second apparatus in response to a request from the second apparatus to enable the second apparatus to transmit the CP connection request based on the provided assistant information.
  • the first and second apparatuses are terminal apparatuses
  • the third apparatus is a core apparatus
  • the fourth apparatus is a network apparatus.
  • a fourth apparatus capable of performing any of the method 1200 may comprise means for performing the respective operations of the method 1200.
  • the means may be implemented in any suitable form.
  • the means may be implemented in a circuitry or software module.
  • the fourth apparatus may be implemented as or included in the fourth device 140.
  • the fourth apparatus comprises means for receiving, from a third apparatus, a CP connection accept message.
  • the CP connection accept message is transmitted after receiving, from a second apparatus, a CP connection request for establishing a CP connection between a first apparatus and the third apparatus.
  • the fourth apparatus also comprises means for transmitting a RRC message for establishing a RRC connection between the first apparatus and the fourth apparatus to the second apparatus.
  • the fourth apparatus comprises means for receiving, from the third apparatus, the CP connection accept message comprising an indication of relay solution for the first apparatus; and means for establishing a user plane (UP) connection between the fourth apparatus and the first apparatus based on the received relay solution for the first apparatus.
  • the CP connection accept message comprising an indication of relay solution for the first apparatus
  • UP user plane
  • the RRC message comprises a C-RNTI of the first apparatus.
  • the first and second apparatuses are terminal apparatuses
  • the third apparatus is a core apparatus
  • the fourth apparatus is a network apparatus.
  • Fig. 13 is a simplified block diagram of a device 1300 that is suitable for implementing example embodiments of the present disclosure.
  • the device 1300 may be provided to implement a communication device, for example, the first device 110, the second device 120, the third device 130 or the fourth device 140 as shown in Fig. 1.
  • the device 1300 includes one or more processors 1310, one or more memories 1320 coupled to the processor 1310, and one or more communication modules 1340 coupled to the processor 1310.
  • the communication module 1340 is for bidirectional communications.
  • the communication module 1340 has one or more communication interfaces to facilitate communication with one or more other modules or devices.
  • the communication interfaces may represent any interface that is necessary for communication with other network elements.
  • the communication module 1340 may include at least one antenna.
  • the processor 1310 may be of any type suitable to the local technical network and may include one or more of the following: general purpose computers, special purpose computers, microprocessors, digital signal processors (DSPs) and processors based on multicore processor architecture, as non-limiting examples.
  • the device 1300 may have multiple processors, such as an application specific integrated circuit chip that is slaved in time to a clock which synchronizes the main processor.
  • the memory 1320 may include one or more non-volatile memories and one or more volatile memories.
  • the non-volatile memories include, but are not limited to, a Read Only Memory (ROM) 1324, an electrically programmable read only memory (EPROM) , a flash memory, a hard disk, a compact disc (CD) , a digital video disk (DVD) , an optical disk, a laser disk, and other magnetic storage and/or optical storage.
  • Examples of the volatile memories include, but are not limited to, a random access memory (RAM) 1322 and other volatile memories that will not last in the power-down duration.
  • a computer program 1330 includes computer executable instructions that are executed by the associated processor 1310.
  • the program 1330 may be stored in the memory, e.g., ROM 1324.
  • the processor 1310 may perform any suitable actions and processing by loading the program 1330 into the RAM 1322.
  • the example embodiments of the present disclosure may be implemented by means of the program 1330 so that the device 1300 may perform any process of the disclosure as discussed with reference to Figs. 9 to 12.
  • the example embodiments of the present disclosure may also be implemented by hardware or by a combination of software and hardware.
  • the program 1330 may be tangibly contained in a computer readable medium which may be included in the device 1300 (such as in the memory 1320) or other storage devices that are accessible by the device 1300.
  • the device 1300 may load the program 1330 from the computer readable medium to the RAM 1322 for execution.
  • the computer readable medium may include any types of tangible non-volatile storage, such as ROM, EPROM, a flash memory, a hard disk, CD, DVD, and the like.
  • Fig. 14 shows an example of the computer readable medium 1400 which may be in form of CD, DVD or other optical storage disk.
  • the computer readable medium has the program 1330 stored thereon.
  • various 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 which may be executed by a controller, microprocessor or other computing device. While various aspects of embodiments of the present disclosure are illustrated and described as block diagrams, flowcharts, or using some other pictorial representations, it is to be understood that the block, apparatus, system, technique or method 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 present disclosure also provides at least one computer program product tangibly stored on a non-transitory computer readable storage medium.
  • the computer program product includes computer-executable instructions, such as those included in program modules, being executed in a device on a target physical or virtual processor, to carry out any of the methods as described above with reference to Figs. 9 to 12.
  • program modules include routines, programs, libraries, objects, classes, components, data structures, or the like that perform particular tasks or implement particular abstract data types.
  • the functionality of the program modules may be combined or split between program modules as desired in various embodiments.
  • Machine-executable instructions for program modules may be executed within a local or distributed device. In a distributed device, program modules may be located in both local and remote storage media.
  • Program code for carrying out methods of the present disclosure may be written in any combination of one or more programming languages. These program codes may be provided to a processor or controller of a general purpose computer, special purpose computer, or other programmable data processing apparatus, such that the program codes, when executed by the processor or controller, cause the functions/operations specified in the flowcharts and/or block diagrams to be implemented.
  • the program code may execute entirely on a machine, partly on the machine, as a stand-alone software package, partly on the machine and partly on a remote machine or entirely on the remote machine or server.
  • the computer program code or related data may be carried by any suitable carrier to enable the device, apparatus or processor to perform various processes and operations as described above.
  • Examples of the carrier include a signal, computer readable medium, and the like.
  • the computer readable medium may be a computer readable signal medium or a computer readable storage medium.
  • a computer readable medium may include but not limited to an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any suitable combination of the foregoing. More specific examples of the computer readable storage medium would include an electrical connection having one or more wires, a portable computer diskette, a hard disk, a random access memory (RAM) , a read-only memory (ROM) , an erasable programmable read-only memory (EPROM or Flash memory) , an optical fiber, a portable compact disc read-only memory (CD-ROM) , an optical storage device, a magnetic storage device, or any suitable combination of the foregoing.

Landscapes

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

Abstract

Des modes de réalisation donnés à titre d'exemple de la présente invention concernent un accès initial d'un dispositif distant via un relais. Un premier dispositif transmet, à un deuxième dispositif, une demande de connexion pour établir une connexion de plan de commande entre le premier dispositif et un troisième dispositif, la demande de connexion comprenant des informations du premier dispositif pour établir une connexion de plan de commande entre le premier dispositif et le troisième dispositif afin de permettre au deuxième dispositif de transmettre une demande de connexion de plan de commande au troisième dispositif sur la base des informations. Le premier dispositif reçoit, du deuxième dispositif, un message de commande de ressources radioélectriques transmis par un quatrième dispositif en réponse à un message d'acceptation de connexion de plan de commande provenant du troisième dispositif. Cette solution permet de fournir un accès initial sécurisé, flexible et efficace du premier dispositif.
PCT/CN2020/093747 2020-06-01 2020-06-01 Accès initial de dispositif distant via un relais WO2021243518A1 (fr)

Priority Applications (2)

Application Number Priority Date Filing Date Title
PCT/CN2020/093747 WO2021243518A1 (fr) 2020-06-01 2020-06-01 Accès initial de dispositif distant via un relais
CN202080099998.9A CN115428578A (zh) 2020-06-01 2020-06-01 经由中继的远程设备的初始接入

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2020/093747 WO2021243518A1 (fr) 2020-06-01 2020-06-01 Accès initial de dispositif distant via un relais

Publications (1)

Publication Number Publication Date
WO2021243518A1 true WO2021243518A1 (fr) 2021-12-09

Family

ID=78830090

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2020/093747 WO2021243518A1 (fr) 2020-06-01 2020-06-01 Accès initial de dispositif distant via un relais

Country Status (2)

Country Link
CN (1) CN115428578A (fr)
WO (1) WO2021243518A1 (fr)

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2018031343A1 (fr) * 2016-08-12 2018-02-15 Intel IP Corporation Procédés d'optimisation d'opérations relais de couche 2
CN109892003A (zh) * 2016-11-07 2019-06-14 皇家Kpn公司 经由具有中继能力的用户装备ue在远程用户装备ue和电信网络之间建立连接的方法和系统
US20200100308A1 (en) * 2017-02-06 2020-03-26 Lg Electronics Inc. Method for handling of a rrc connection request message of a remote ue by a relay ue in wireless communication system and a device therefor

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2018031343A1 (fr) * 2016-08-12 2018-02-15 Intel IP Corporation Procédés d'optimisation d'opérations relais de couche 2
CN109892003A (zh) * 2016-11-07 2019-06-14 皇家Kpn公司 经由具有中继能力的用户装备ue在远程用户装备ue和电信网络之间建立连接的方法和系统
US20200100308A1 (en) * 2017-02-06 2020-03-26 Lg Electronics Inc. Method for handling of a rrc connection request message of a remote ue by a relay ue in wireless communication system and a device therefor

Non-Patent Citations (3)

* Cited by examiner, † Cited by third party
Title
INTEL: "Solution of 5GC Capable UE behind 5G-RG connected to 5GC via NG-RAN/W-5GAN", SA WG2 MEETING SA2#129，S2-1810426；, 19 October 2018 (2018-10-19), XP051539407 *
MEDIATEK INC.: "FS_5G_ProSe: Security aspects of L2 relay", SA WG2 MEETING #136AH，S2-2000785；, 17 January 2020 (2020-01-17), XP051842839 *
NOKIA ET AL.: "New Solution Layer-3 UE-to-Network Relay with support of N3IWF", SA WG2 MEETING #139E (E-MEETING)，S2-2004034；, 29 May 2020 (2020-05-29), XP051890041 *

Also Published As

Publication number Publication date
CN115428578A (zh) 2022-12-02

Similar Documents

Publication Publication Date Title
US10813021B2 (en) Method and device for resource configuration in handover
US20190007874A1 (en) Method and Apparatus for Cell Reselection in a Wireless Communication System
EP4188003A1 (fr) Procédé de transfert, dispositif terminal et dispositif réseau
EP4169349A1 (fr) Procédés, dispositifs et support de communication
WO2022056693A1 (fr) Procédé, dispositif et support de stockage informatique de communication
CN117480815A (zh) 用于非地面网络卫星切换的方法、终端设备及网络设备
WO2021243518A1 (fr) Accès initial de dispositif distant via un relais
US20240057203A1 (en) Method and apparatus for path switch in a wireless communication system
US20230189098A1 (en) Method and apparatus for wireless communication
EP4022977B1 (fr) Réduction de signalisation lors d'un transfert intercellulaire d'un noeud iab
WO2024065209A1 (fr) Transmission de données précoce à destination d'un mobile pour internet des objets
US11849497B2 (en) Methods, devices, and medium for handling of non-SDT data
US20240090063A1 (en) Data transmission with security configurations
WO2022120632A1 (fr) Procédé, dispositif et support de stockage informatique de communication
WO2023070511A1 (fr) Amélioration sur un réseau de liaison terrestre et d'accès intégré
US20230254866A1 (en) Methods, devices, and medium for communication
US20240015616A1 (en) Method, device and computer storage medium of communication
CN114467362B (zh) 用于主节点间切换的设备、方法、装置和计算机可读介质
US20240129989A1 (en) Method, device and computer storage medium of communication
WO2022027380A1 (fr) Dispositif, procédé, appareil et support lisible par ordinateur pour communication iab
US20230007541A1 (en) Cell switching method, terminal device, and storage medium
EP4364519A1 (fr) Transmission de petites données

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

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

Country of ref document: EP

Kind code of ref document: A1